ISE6 Demo

1. ISE6 Demo 1/9/2008 Virginia Beach Meeting Discussion

2. The Demo LEAPS (Navy Lifecycle) ShipConstructor TWR FOT Sys AP214 + ISE6 PLCSXML – Create part, Attach HSC AP 227 CAD files CATIA ShipConstructor AP 214 Equip files Small pipe system KSSI (Data Mgmt / QA) ISE6 PLCS XML eINTEROP (LPD 17 IPDE) ISE6 PLCS XML Modify Logistics Data – HSC Link AP 214 file Show structure DDG 1000 IPDE ISE6 Demo Scenario View structure & related docs

3. AP 214 file • Purpose • Neutral format 3D model for viewing in other systems • Also demonstrate exchange with OEM vendor • Export from ShipConstructor generates tessellated surfaces • Pipes have polygonal cross-section • Equipment (originally modeled in Inventor), apparently smooth surface • Update ShipConstructor model attributes (only if PatR uses) • CPC Catalog part number, valve number, description / nomenclature, system name • AP 214 file for pump • Product.id is GUID • AP 214 for Fuel Oil System (for evaluation intially) ISE6 Demo Scenario

4. AP 227 Exchange • CATIA – ShipConstructor • Import small pipe system into ShipConstructor • Modify, export • View modified system in STEP viewer • ShipConstructor – ShipConstructor • Fuel Oil transfer System • Show attributes for piping or fitting (not sending equipment) • Talk about generating AP 214 STEP file (not real time) ISE6 Demo Scenario

5. LPD 17 IDE • Show Fuel Oil System • Show pump • Logistics data, documents • Design occurrence has GUID for pump • Export PLCS file • Documents pre-exchanged ISE6 Demo Scenario

6. ShipConstructor - KSS • Option 1 • ShipConstructor export pump file • Option 2 • (if feasible to covert tessellated geom. Epistree primitives) • ShipConstructor export system • KSS imports AP 214 system (logically) • Show system geometry • Generate AP 214 for selected equipment • Show Pump data and geometry • Link equipment STP file to PLCS data • Epistree updates HSC based on rules • Change HSC prefix • Generate new PLCS file ISE6 Demo Scenario

7. LEAPS • Import AP 214 file for pump • Create library part for equipment (or preload if problems) • Import PLCS file • Attach HSC/RIN value to specified GUID ISE6 Demo Scenario

8. DDG 1000 IDE • Import PLCS file • Documents preloaded • AP 214 file preloaded (convert AP 214 to JT or other) • Show resulting data • Including logistics data, documents, AP 214 files ISE6 Demo Scenario

9. Storyboard (Old) • CATIA -> ShipConstructor • Demonstrate AP 227 exchange of piping details • Export isolated pipes from NNS CATIA into ShipConstructor • Export TWR model from ShipConstructor 8 and import into ShipConstructor 5 • ShipConstructor (Mechanical Desktop) -> AP 214 file • Generate graphical view of system • LPD 17 IPDE -> ISE6 XMLfile • Export • system with attached documents • Components with SCLSIS data and some Eng. Data • Epistree • View, edit and link ISE6 XMLfile • Import ISE6 XMLfile, create system/logistics structure • Modify HSC to fit DD 1000 structure • Import AP 214 file • Move valve?? (Some grpahical change if possible) • Link logistics data and AP 214 file ISE6 Demo Scenario

10. Storyboard (Old cont) • Epistree -> ISE6 XMLfile • Export ISE6 XMLfile • LEAPS • Demonstrate tying logistics data to LEAPS • Import AP 214 file • Create components & assemblies • Import ISE6 XMLfile • Create product structure (FOT system structure) • From AP 214 or PLCS • Attach HSC (or RIN), RIC to components • (May need to modify Focus model) • LCB • Import ISE6 XMLfile • View system and logistics structure & documents • View system graphics as JT file (converted from AP 214) • ISE6 XMLfile – only talk to use of PLCS • Details after the demo ISE6 Demo Scenario

11. Issues – resolved in following slides • AP 214 File (Generated by NSWC CD) • Issues • Component identification, GUID (tag numbers must match) • Possible to generate assembly structure for system • Generation of file through Mechanical Desktop • Tessellated model geometry – need to find right command line options • Need to coordinate with Pat Rourke • Test Data • Need to define test case for import into LCB • NGIT – working out how to populate LCB • Documents • Treat as exchange package of ISE6 XMLfile + documents • Work out final details in Jan • Also include URN as proposed in SCIM (not for demo) ISE6 Demo Scenario

12. Demo Data - Documents • Fuel Oil Transfer System (HSC 2611+ 5412) • Tech Manuals (Ben) • Create separate TM for Fuel Oil system from BIB • Add index to Boat Info Book (BIB) • System Diagram (Complete) • 2 sheets • Materials List (ties to SCLSIS data, ) • Generate to match the drawings • Drawing (Ben) • 8 sheets • NAVSEA drawing number and title • Create 1 PDF file • VFI (Complete) • Product sheet, quote • AP 214 File () • Provisioning Package (Larry??) • Discuss whether possible or practical • Logistics analysis reports (David or Larry or Ted??) • Examples: R&M, environmental hazard, TOC, safety • Discuss whether possible or practical ISE6 Demo Scenario

13. Demo Data – SCLSIS Data • Fuel Oil Transfer System (HSC 2611 + ) • Send core SCLSIS data • System and part-related attributes • Need to send instance data, but most attributes will be changed to fit the new intended usage. • CFF attributes: HSC, EFD, SAC, ESD, MEC, • Type 2 attributes: RIN, PRID, EIN, RIC, LOC • HSC breakdown of components and logistics • System -> subsystem ->valve / pump -> repair kit ISE6 Demo Scenario

14. Data Development Schedule • Unify system diagram materials list & SCLSIS data (Ted & Ben - Nov 30) • Work out document metadata – (today -Ted, Ken, Tom & Rick – Nov 30) • XML Context Schema Demo File (Ted - Jan meeting) • SCLSIS data (Ted - Nov 30) • System diagram (Ben - Nov 30) • Isometric Drawing (from 3D model) • Photo • VFI, Quote • Tech Manual • ShipConstructor 3D model file (Ben) • Generate AP 214 File – system, pump (Ben) • Work out details of Mechanical Desktop export (Ben, Pat – Jan meeting) • Provisioning Packages, Analysis Reports (Larry – Jan meeting) • Jan meeting – review all data ISE6 Demo Scenario

15. Demo Test Data (Documents) Ship Info Book Ship System Diagram FOT System Tech Manual FOT SubSystem 3D Drawing FOT SubSystem Photo VFI Product Sheet Pump VFI Quote AP 214 File Logistics Reports ISE6 Demo Scenario

16. DDG 1000 IPDE Processing • Relationships not created during load time • Created later in the background based on foreign key attributes • PLCS XML file has explicit relationship, not foreign keys • DDG 1000 translator must generate foreign key attributes from PLCS XML relationships • May be able to link ship level document (SIB) to system ISE6 Demo Scenario

17. Demo Test Data (Documents) Ship Info Book Ship TMINS number FOT System System Diagram Drawing #, rev TMINS number Or ESWBS Tech Manual FOT SubSystem 3D Drawing Drawing #, rev FOT SubSystem VFI Photo Catalog part number VFI Product Sheet Catalog part number Pump VFI Quote Catalog part number AP 214 File Catalog part number Logistics Reports ISE6 Demo Scenario RIC

18. PLCS – IPDE Object Mapping ISE6 Demo Scenario

19. DDG 1000 Cat Part Assembly Drawing LCB Tech Manuals VFI Doc ISE6 Demo Scenario

20. SCLSIS Data • System • HSC 541, Fuel Oil Transfer Pumps • HSC 261 Fuel Oil Transfer Piping • Pump • HSC 54121201 • Encompass the pump, motor, starter • Could be higher level • Attributes • HSC, EFD, SAC, MCC, ESD • RIN (not processed on import), EIN, PRID, LOCATION, RIC ISE6 Demo Scenario

21. Data Action Items • Ted • Define Product data and document metadata • Send screen shots to NGIT, KSSI for review • Re-draw Test Case to show relationships • Create XML Test Files • Ben • Generate AP 214 file for pump and FOT system • Send to KSSI & NGIT • Issues • Subtypes for documents • Need slightly different sets of attributes ISE6 Demo Scenario

22. Template Expansion Schedule • Nov 30 – XSL file, given consensus on context schema • Nov 30 - round trip, • Start testing for 1st test case • Jan –round trip for 1st test case completed ISE6 Demo Scenario

23. Demo Planning • Jan meeting • Define site and date • Have all data developed (even if hand generated) • More participants • Talk with Tim Turner (Ted) • Atlantec demonstrating CPC Part Design Class (Ted & Bryan) • Tie to another event • ASNE Maintenance Symposium? • NPDI • DMC (Defense Manufacturing Conference) – next month • Bob to discuss with attendees • Potential Stakeholders / Audience • Input from logisticians (and PEO IWS) attending Jan meeting • NLSC, SPAWAR • People responsible for CDMD, ATIS, SKED? • Jim Mays contacts • PMS 400, Planning yards, Navy Shipyards, NAVSUP, NAVICP, Defense Supply Centers • MMA? (presentation at meeting?, annual meeting was in Oct) • Defense Sustainment Consortium • Rick Self, ATI (Ron to discuss demo) • Bryan to discuss with members ISE6 Demo Scenario

24. Original System Diagram Equipment of interest E1 Pump, Fuel Oil Transfer Positive Type E2 Pump, Fuel Tank Stripping E4 Water / Filter Separator F94 1” Simplex Strainer ISE6 Demo Scenario

25. Updated System Diagram ISE6 Demo Scenario

26. Fuel Oil Pump Detail ISE6 Demo Scenario

27. Materials List ISE6 Demo Scenario

28. Fuel Oil Transfer components Current SCLSIS Data ISE6 Demo Scenario

29. Preparation of Logistics Data • Validate against system diagram • Update local SCLSIS data • Add missing information • Add additional logistical breakdown • Validate with ILS for consistency, accuracy • Immediate need to develop detailed test case for one component to test PLCS translator ISE6 Demo Scenario

30. Methodology • Post data to isetools\Test Cases • Subscribe to BB notification • Send out notice when posting data ISE6 Demo Scenario

31. Test Cases • Test Cases • 1. Pump with minimal system structure, document references • 2. Pump and selected valves • 3. Full FOT system ISE6 Demo Scenario

32. The Navy-Centric Demo LEAPS (Navy Lifecycle) CAD Navy Support Lifecycle AP 227 CAD files PLCS PLCS OEM 1 OEM 2 Contractual Deliverable - 1388 data as PLCS ISEA / PARM Ship Program PLCS PLCS Ship Program ISE6 Demo Scenario View structure & graphics in JT

33. Related • Pull environment for ISEA getting tech data from OEM • Not OEM pushing all data at once • Access multiple revisions of related data ISE6 Demo Scenario