1. Defense Acquisition University LOG 204 Configuration Management Course Migration Mr. Bob Cartwright LOG 204 Course Manager October 29, 2004

2. 1 Current LOG 204 CM Course Content LessonLesson TitleClassroom Hours 1CM Introduction1.0 2CM Contribution to SE1.0 3CM Requirements during life cycle1.0 4Configuration Identification3.0 Q 1Quiz on Lessons 1-40.5 5Data Management2.0 6Configuration Status Accounting1.5 7Audit and Verification3.0 Q 2Quiz on Lessons 5-70.5 8Configuration Control6.5 Q 3Quiz on Lesson 80.5 9Software Configuration Management2.5 10Performance Metrics1.0 11CM Planning3.0 Q 4Quiz on Lessons 9-110.5 12Managing a CM Program3.0 Total30.5

3. 2 LOG 204 Course Objectives Apply Configuration Management oversight as a tool in the Integrated Process and Product Development effort for System Management. Given a scenario, utilize Integrated Process & Product Development approach to manage configuration for a system during its life cycle.

4. 3 LOG 204 Terminal Learning Objectives (TLO) Lesson 1: CM Introduction - Given a specific situation, correctly relate the role and interrelationships of the key elements of Configuration Management (CM) (e.g. CM Planning, Identification, Status Accounting, Audits, Control, and Data Management) Lesson 2: CM Contribution to SE - Provided a scenario, distinguish the role of CM in the SE Process Lesson 3: CM Requirements During a Life Cycle - Given a case exercise, explain how CM concepts, definitions, principles, and applications are applied within the system life cycle. Lesson 4: Configuration Identification - Given a scenario, identify Configuration Items and interfaces for a proposed system. Lesson 5: Data Management - Given a scenario, identify, determine, and analyze CM data requirements. Lesson 6: Configuration Status Accounting (CSA) - Given a scenario, build a status accounting system Lesson 7: Audits / Verification - Given a set of alternatives, differentiate among Functional & Physical Configuration Audits (FCA / PCA) & technical reviews

5. 4 LOG 204 Terminal Learning Objectives (TLO) Lesson 8: Configuration Control - Given a scenario, control the configuration of a system throughout its life cycle, including: –Develop, assess and justify an Engineering Change Proposal (ECP) / Request for Deviation (RFD) –Review an ECP/RFD and recommend actions for the configuration manager –Determine the implementation method for a change Lesson 9: Software Configuration Management (SCM) - Given a scenario, prepare / review SCM documentation Lesson 10: Managing CM Programs - Performance Metrics - Given a scenario, select performance metrics to manage a CM program Lesson 11: CM Planning - Given a scenario, develop & review a CM plan for a Contractor & a Government program office Lesson 12: Managing CM Programs - Given a scenario, develop a structure for a CM program

6. 5 LOG 204 Enrollment Trends Fewest students of any DAU Life Cycle Logistics Course Except for FY 03 upswing (in anticipation of LOG 235 fielding and possible LOG 204 deactivation), student throughput essentially flat/ trending downward OrganizationFY01FY02FY03FY04FY05 (Est) Air Force602510743107 Army54691954449 Navy/USMC185892446519 Coast Guard11120 Other DoD151228727 Industry15850 TOTALS316201583166202

7. 6 LOG 204 FY04 Student Demographics

8. 7 LOG 204 FY05 Migration Planning Assumptions: –CM is an important logistics competency –Interest remains, and students see value –Need for government life cycle logistician insight continues in PBL environment –LOG 204 course material has broader applicability than just life cycle logisticians, including SPRDE professionals & program managers –Migration to DL offers greater potential for increased student participation  Mitigates reduced travel budgets for in-residence courses  Precludes problems with personnel being out of the office for course Course Manager Assessment: –LOG 204 course material should continue to be available to DoD workforce –Current course content is solid, with modifications required to maintain currency –Existing course material will serve as foundation of a future distance learning version of this course

9. 8 Potential LOG 204 Expansion Areas Implement USMC Dec 02 Logistics FIPT Recommendation to “assign dual labeling status (i.e. SYS 204) in addition to LOG 204.” Expand: –Configuration Management “basics” –Software Configuration Management –Private Sector best practices/processes –Integrated configuration management of software and hardware issues –Interaction of MIL HDBK 61A, EIA 836, EIA 649A and EIA 859. –PBL/PSI configuration management & data management relationship/interaction –Integrated product data environment (vice separate management of CM data & other technical data) Update current verbiage from: –Defense Acquisition Guidebook – SE (4.2.3.6) & Life Cycle Logistics Chapters (5.2.1.4) –Chapter 4 Draft “Performance Based Logistics: Program Manager’s Product Support Guide” –ANSI/EIA 649A, Configuration Management (and HDBK 649, Configuration Management under development) –ISO 10007, Quality Management – Guidelines for configuration management –EIA 836, Configuration Management Data Exchange and Interoperability Other Areas? FIPT Guidance or inputs?

10. 9 Summary & Recommendations LOG 204 Update & DL Migration Planning Underway Road Ahead –Brief Status to Logistics FIPT 29 Oct –LOG 204 Course Manager & DAU Logistics/SPRDE Program Directors Meet with OSD Systems Engineering & Logistics Staffs 8-9 Nov 04 –Discussions with Service and GEIA subject matter experts –Develop Course Migration Strategy and POA&M with Late-2005 Target Migration Date, depending on funding Recommendations –DAU Proceed with FY05 migration from classroom to distance learning –Pursue joint LOG-SYS designation to broaden target audience –Logistics FIPT Approve Approach and Provide Course Content Inputs –Strong FIPT/DACM endorsement of course to workforce after migration

11. 10

12. 11 BACKUP SLIDES

13. 12 Current LOG 204 Course Objectives Apply Configuration Management oversight as a tool in the Integrated Process and Product Development effort for System Management. Given a scenario, utilize Integrated Process & Product Development approach to manage configuration for a system during its life cycle. Lesson 1: CM Introduction - Given a specific situation, correctly relate the role and interrelationships of the key elements of Configuration Management (CM) (e.g. CM Planning, Identification, Status Accounting, Audits, Control, and Data Management) –Define elements of CM –Distinguish from among: Configuration of Product, Configuration Item, Configuration Documentation, and Configuration Management, –Identify the objectives, necessity, and benefits of CM –Distinguish who performs and uses CM –Describe relationships of CM references

14. 13 Current LOG 204 Course Objectives Lesson 2: CM Contribution to SE - Provided a scenario, distinguish the role of CM in the SE Process –Define a System Engineering Process –Describe how CM interfaces with the Systems Engineering Process (SEP). –Compare the purpose, development, evolution and use of the various types of program-unique specifications and how they contribute to the establishment of CM functional, allocated, and product configuration documentation. Lesson 3: CM Requirements During a Life Cycle - Given a case exercise, explain how CM concepts, definitions, principles, and applications are applied within the system life cycle. –List CM requirements during successive phases of the life cycle. –Relate impact of on-going acquisition reform initiatives to life cycle and CM. –Recognize and determine impact of CM on supportability

15. 14 Current LOG 204 Course Objectives Lesson 4: Configuration Identification - Given a scenario, identify Configuration Items and interfaces for a proposed system. –Define the Configuration Identification process. –Define the role and function of Interface Management –Relate the interrelationships of Configuration Identification, Interface Management, and Data Management. –Select criteria for Configuration Identification of items. –Compare and contrast the impact of Configuration Identification on supportability. –Relate Configuration Identification to the product structure. –Select Configuration Items (CIs). –Select methods for documentation of CIs and Interfaces –Establish CM baseline(s).

16. 15 Current LOG 204 Course Objectives Lesson 5: Data Management - Given a scenario, identify, determine, and analyze CM data requirements. –Define common data elements. –Distinguish among concepts of originator, owner, and user of data. –Define types of data rights. –List examples of technical data. –Distinguish between configuration data and other technical data –List alternatives to buying data. –List current data formats and media. Lesson 6: Configuration Status Accounting (CSA) - Given a scenario, build a status accounting system. –List common elements of a CSA. –Relate the purpose, responsibility and need for status accounting records and how the CSA system should be tailored to the needs of managing organizations. –Describe how data elements are selected, utilized and incorporated into CSA reports as data requirements. –Compare and contrast the purpose/capabilities of the Configuration Management Information System (CMIS) to status accounting function

17. 16 Current LOG 204 Course Objectives Lesson 7: Audits / Verification - Given a set of alternatives, differentiate among Functional and Physical Configuration Audits (FCA / PCA) and technical reviews. –Compare and contrast audits to validation / verification in the system engineering process. –Define the purpose and process for a functional configuration audit –Relate the functional configuration audit to the configuration baselines –Identify the activities performed during the FCA and how the government prepares for each activity. –Recognize how the FCA demonstrates achieved performance. –Define the purpose and process for a physical configuration audit –Relate the physical configuration audit to the configuration baselines –Identify the activities performed during the PCA and how the government prepares for each activity. –Recognize how the PCA demonstrates documented design.

18. 17 Current LOG 204 Course Objectives Lesson 8: Configuration Control - Given a scenario, control the configuration of a system throughout its life cycle, including: –Develop, assess and justify an Engineering Change Proposal (ECP) / Request for Deviation (RFD) –Review an ECP/RFD and recommend actions for the configuration manager –Determine the implementation method for a change —Identify the engineering change process —Relate the engineering change process to the acquisition reform initiatives. —List baseline documentation subject to change control —Distinguish among the functions of requesting, reviewing, and approving a change.

19. 18 Current LOG 204 Course Objectives Lesson 8: Configuration Control (Continued) —List reasons for ECP —Distinguish between an ECP and RFD —Compare & contrast impact of ECP/RFD on the technical baseline —Describe how and when ECPs are used to control changes —Recognize the need for Configuration Control Boards (CCBs) —List the technical and program disciplines commonly on a CCB —Compare and contrast the types of changes reviewed and approval authority —Distinguish between technical approval and contractual approval of a change —Recognize design, manufacturing, and supportability concerns associated with implementing a change. —Identify stakeholders in the change process. —Compare and contrast alternative methods of implementation

20. 19 Current LOG 204 Course Objectives Lesson 9: Software Configuration Management (SCM) - Given a scenario, prepare / review SCM documentation –Recognize the need for SCM. –List references for SCM and software development models –List the process steps for Software Configuration Management –Distinguish among: Computer Software Configuration Item, Version, Release, Source code, Object code, –Component, Build –Compare and contrast hardware CM and software CM processes –Compare and contrast impact of differing development models on SCM

21. 20 Current LOG 204 Course Objectives Lesson 10: Managing CM Programs - Performance Metrics - Given a scenario, select performance metrics to manage a CM program –List common metrics to manage a CM program –Identify performance metrics based on a given system / situation Lesson 11: CM Planning - Given a scenario, develop & review a CM plan for a Contractor & a Government program office –Compare and contrast roles of the Government and contractors in CM –Identify the interface of management among the Government, contractors, and subcontractors –Evaluate the impact of Commercial & Non-Developmental Items on CM –Recognize the special CM requirements of the Open Systems approach –List common elements of CM planning –Relate a CMP in terms of the importance, content, who develops it, when it is developed, and how it is maintained

22. 21 Current LOG 204 Course Objectives Lesson 12: Managing CM Programs - Given a scenario, develop a structure for a CM program. –Compare and contrast commercial processes for CM –Recognize impact of information technology and business models on CM –Explain the current status and future trends of critical CM functions