Configuration Management - Accessibility Description of Image An inverted equilateral triangle with its point resting on...

Transcribed Image Text:

Configuration Management - Accessibility Description of Image An inverted equilateral triangle with its point resting on top of a rectangular box labelled Technical Management Processes. Resting on top of the triangle is the phrase Systems Engineering Process. Below the label of the rectangular box are the processes Decision Analysis, Technical Planning, Technical Assessment, Requirements Management, Risk Management, Configuration Management, Technical Data Management, and Interface Management. There is a rectangular box around Configuration Management. Resting on top of the Technical Management Processes rectangular box on either side of the inverted triangle are two boxes labelled Technical Processes. The box on the left contains, from top to bottom, Stakeholder Requirements Definition, Requirements Analysis, and Architecture Design. The word Decomposition is above and to the right of this box inside of a downward-pointing arrow along the side of the inverted triangle. Inside the inverted triangle along the right side of the arrow are, from top to bottom, Operational Need, Requirements, and Design. The other Technical Processes box to the right of the triangle contains, from bottom to top, Implementation, Integration, Verification, Validation, and Transition. The word Realization is above and to the left of this box inside of an upward-pointing arrow along the side of the inverted triangle. Inside the inverted triangle to the left of the arrow are, from bottom to top, Product, Validated Solution, and Delivered Capability. Outside the inverted triangle to the right of the arrow are, from bottom to top, DT&E, OT&E, and IOC/FOC. Inside the inverted triangle are double-headed arrows between pairs of words, from top to bottom, Operational Need and Delivered Capability, Requirements and Validated Solution, and Design and Product. Learning Objectives Given a scenario, identify system configuration items (CIs) in a way which enhances logistics capability and sustainment. CM Plan Example How does this CMP define a CI? 2.1.1 Identifying Configuration Items (CIs) Each program can set its own rules and definitions! Reference the program CM Plan. 2.1.1.1 Every item of the system is controlled at some level through controlling specs, interface control documents, etc. 2.1.1.2 A Cl is documented separately from its parent Cls while non-Cls fall under parent CI documentation. 2.1.1.3 Separate configuration allows for separate logistical control, separate contracting actions and separate suppliers. 2.1.1.4 Items will be separately configured if: 2.1.1.4.1 They are a Line-replaceable Unit (LRU). 2.1.1.4.2 The logistics system identifies them separately. 2.1.1.4.3 They are a software item. 2.1.1.4.4 2.1.1.4.5 They are tracked separately with any measure. Tracking them separately is desired for any other reason. What are the rules for designating an item as a CI? How important is it that this plan can be read and understood? ICM Exercise Background In response to a new requirement, the Program Office has established another program (temporarily within the JAPV's program office) to acquire an electric launcher for glide vehicles. A solution has been found, but the new program is still under-staffed and they have asked for help identifying Configuration Items (CI) for the new launch system. This is a highly mature system and the developer has supplied a video with assembly instructions and the current physical architecture. ICM CM Exercise Tasking - (30 mins) 1. Following the provided JAPV Configuration Management Plan, use the information from the developer to identify three (3) Cls. 2. Identify one item which should not be a Cl. 3. Justify why each item should be (or should not be separately configured. ICI Identification 1 2 3 CI Justification Not a Cl Justification Configuration Management - Accessibility Description of Image An inverted equilateral triangle with its point resting on top of a rectangular box labelled Technical Management Processes. Resting on top of the triangle is the phrase Systems Engineering Process. Below the label of the rectangular box are the processes Decision Analysis, Technical Planning, Technical Assessment, Requirements Management, Risk Management, Configuration Management, Technical Data Management, and Interface Management. There is a rectangular box around Configuration Management. Resting on top of the Technical Management Processes rectangular box on either side of the inverted triangle are two boxes labelled Technical Processes. The box on the left contains, from top to bottom, Stakeholder Requirements Definition, Requirements Analysis, and Architecture Design. The word Decomposition is above and to the right of this box inside of a downward-pointing arrow along the side of the inverted triangle. Inside the inverted triangle along the right side of the arrow are, from top to bottom, Operational Need, Requirements, and Design. The other Technical Processes box to the right of the triangle contains, from bottom to top, Implementation, Integration, Verification, Validation, and Transition. The word Realization is above and to the left of this box inside of an upward-pointing arrow along the side of the inverted triangle. Inside the inverted triangle to the left of the arrow are, from bottom to top, Product, Validated Solution, and Delivered Capability. Outside the inverted triangle to the right of the arrow are, from bottom to top, DT&E, OT&E, and IOC/FOC. Inside the inverted triangle are double-headed arrows between pairs of words, from top to bottom, Operational Need and Delivered Capability, Requirements and Validated Solution, and Design and Product. Learning Objectives Given a scenario, identify system configuration items (CIs) in a way which enhances logistics capability and sustainment. CM Plan Example How does this CMP define a CI? 2.1.1 Identifying Configuration Items (CIs) Each program can set its own rules and definitions! Reference the program CM Plan. 2.1.1.1 Every item of the system is controlled at some level through controlling specs, interface control documents, etc. 2.1.1.2 A Cl is documented separately from its parent Cls while non-Cls fall under parent CI documentation. 2.1.1.3 Separate configuration allows for separate logistical control, separate contracting actions and separate suppliers. 2.1.1.4 Items will be separately configured if: 2.1.1.4.1 They are a Line-replaceable Unit (LRU). 2.1.1.4.2 The logistics system identifies them separately. 2.1.1.4.3 They are a software item. 2.1.1.4.4 2.1.1.4.5 They are tracked separately with any measure. Tracking them separately is desired for any other reason. What are the rules for designating an item as a CI? How important is it that this plan can be read and understood? ICM Exercise Background In response to a new requirement, the Program Office has established another program (temporarily within the JAPV's program office) to acquire an electric launcher for glide vehicles. A solution has been found, but the new program is still under-staffed and they have asked for help identifying Configuration Items (CI) for the new launch system. This is a highly mature system and the developer has supplied a video with assembly instructions and the current physical architecture. ICM CM Exercise Tasking - (30 mins) 1. Following the provided JAPV Configuration Management Plan, use the information from the developer to identify three (3) Cls. 2. Identify one item which should not be a Cl. 3. Justify why each item should be (or should not be separately configured. ICI Identification 1 2 3 CI Justification Not a Cl Justification