1. 7 Aug 2008 1 Integrated Shipbuilding Environment (ISE) ISE-6 Phase 2 DDG 1000 TDWG Collaboration Data Module Code (DMC) Naming Overview

2. 7 Aug 2008 2 Overview DMC naming effort is related to the following S1000D Use Cases –Develop S1000D Technical Publications and Training Modules –Manage Changes to S1000D Technical Publications and Training Modules Provide approach and status of effort to define an acceptable DMC naming convention –Near term focus on DDG 1000 program –Goal is to recommend something that can also be applied to other Navy programs

3. 7 Aug 2008 3 Approach Develop set of use cases that need to be supported by the DMC naming convention Analyze the current DMC naming recommendation against the use cases and determine gaps Recommend alternate approaches to DMC naming to satisfy as many use cases as possible Document use cases that are not satisfied (or only partially satisfied) and present to DDG 1000 TDWG and USSWG for their consideration

4. 7 Aug 2008 4 Status Created a preliminary set of use cases or scenarios which the DMC should support Reviewed current DDG 1000 DMC naming convention recommendations Need to evaluate current recommendation against use cases and determine gaps and/or alternate recommendations

5. 7 Aug 2008 5 Preliminary Use Cases Define DMC structure Create DMC for specific data module based on defined DMC structure Search for a specific data module, or set of data modules, in a CSDB –Update technical documentation –Reuse existing data module –Given a DM Find where it is used within a specific technical document Find where it is used across multiple technical documents and/or training modules Find related data modules Identify data modules affected by a design change

6. 7 Aug 2008 6 Reuse Scenario Overview Same amplifier can be used multiple times within the same system as well as in different systems Same systems can be deployed on multiple ships and ship classes Amplifier data module (DM) can be supplied by vendor, contractor, or government Amplifier can be tracked by vendor part number, RIC, HSC System, amplifier, and amplifier sub-components can be revised independently

7. 7 Aug 2008 7 Reuse Scenario Overview Fundamental Issues –DM is reusable only if it represents the same logistics support content –DM cannot be reused if DMC is constrained to be unique per ship, system, or equipment breakdown Conclusions –If DM are reused, the context where it is used must be maintained separately in a PM, not in the DMC DMC should only minimally identify the DM DM usage changes over time and cannot be predicted, it is separate from the identity of a DM Users should search PM to find appropriate DM

8. 7 Aug 2008 8 System Level Reuse Scenarios Constraints –Specific instance of an amplifier is uniquely identified by HSC in the system in a ship class –HSC assignments may vary between ship classes –Systems are uniquely identified by ESWBS in a specific ship class

9. 7 Aug 2008 9 System Level Reuse Scenario 1 Same amplifiers within the same system on the same ship (single DM used for different amplifiers in the same system) –Each amplifier has the same ESWBS but a different HSC –If SNS is based on HSC, author cannot effectively find amplifier DM by searching on amplifier HSC

10. 7 Aug 2008 10 System Level Reuse Scenario 2 Same amplifiers in different systems on same ship (single DM used for same amplifier in two different systems) –Each amplifier has a different ESWBS and HSC –If SNS is based on ESWBS and HSC, then author cannot effectively find amplifier DM by searching on either amplifier ESWBS or HSC

11. 7 Aug 2008 11 System Level Reuse Scenario 3 Same amplifiers within the same system on different ship classes (single DM used for different amplifiers on multiple ship classes) –Each ship class may use a slightly different HSC –If DMC is based on HSC, author cannot effectively find amplifier DM by searching on amplifier HSC

12. 7 Aug 2008 12 System Level Reuse Scenario 4 Same amplifiers in different systems on different ships (single DM used for same amplifier in two different systems on multiple ships) –Each amplifier has a different ESWBS and HSC –If DMC is based on HSC, author cannot effectively find amplifier DM by searching on amplifier HSC

13. 7 Aug 2008 13 Equipment Level Reuse Scenarios Constraints –Navy manages supply via RIC which can encompass a number of different parts from different vendors (different CAGE and part numbers) –Vendors can revise or change part numbers, using components from other part numbers –The same equipment is used on multiple systems Subcomponents

14. 7 Aug 2008 14 Equipment Level Reuse Scenario 1 Vendor supplies DM, uses their naming convention –Will not follow DDG 1000 naming convention

15. 7 Aug 2008 15 Equipment Level Reuse Scenario 2 Same subcomponent in same part (e.g. same switch used multiple times in an amplifier) –If both have same disassembly code, reuse is supported

16. 7 Aug 2008 16 Equipment Level Reuse Scenario 3 Same subcomponent in different parts with same RIC (e.g. same switch used in two different amplifiers) –If SNS is based on CAGE, reuse is not supported –If Disassembly code is based on part number, reuse is not supported –If Disassembly code is based on RIC, reuse is supported

17. 7 Aug 2008 17 Equipment Level Reuse Scenario 4 Same subcomponent in different parts with different RIC (e.g. same switch used in two different amplifiers) –If SNS is based on CAGE, reuse is not supported –If Disassembly code is based on part number, reuse is not supported

18. 7 Aug 2008 18 Equipment Level Reuse Scenario 5 Same subcomponent used in different parts with different functional use (e.g. same switch used in electrical equipment and in a pump, which is hydro equipment) –If DMC is based on functional use, reuse is not supported