1 / 36

TWR-49: Long Term Retention of Product Model Data

This project aims to research and evaluate the long-term retention of product model data for weapon systems, ensuring accessibility and interpretability for future generations. It includes the transition to 3-D geometry, aggregation of product models, and the retention of various types of data. Stakeholders include NARA, JEDMICS/NESDR, DLA, and NAVSEA.

byan
Download Presentation

TWR-49: Long Term Retention of Product Model Data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Paul J. Rakow Naval Surface Warfare Center Carderock Division TWR-49: Long Term Retention of Product Model Data

  2. Agenda Project Description Project accomplishments 2009-2011 Objectives Group Discussion Close-out

  3. Why product model information? • As DOD acquisition contracts transition from electronic drawing based archive data sets to digital product model data, the respective agencies need to ensure that future users have access to the required data to support the lifecycle of their weapon system. • This includes the requirements and issues involved with the: • Transition to 3-D geometry in numerous forms and quantities. • Aggregation of product models and related data from individual components to complete weapons systems • Long-term accessibility and interpretability of the archived digital data by future generations.

  4. Origination of the data The design spiral is actually a convoluted path Shipbuilder involvement Concept Design & Construction Core data Commissioning Evaluations & applications of core data 30-70 years In-service Retirement

  5. What types of data? Long Term Data Retention of Weapon System • 3-D Geometry • engineering properties • associative relations • analysis data • process definition • logistics definition • manufacturing data • work breakdown structure • product structure • links to M&S • links to documentation • drawings • models • photographs • manuals

  6. Product model data: Multiple data types Piping Images 2D Drawings

  7. Product model data: Multiple data types Piping 3D model

  8. What will we do with it? Research and evaluate through objective measurement, issues related to long-term data retention of large amounts of structured weapons system product data in native and neutral formats.

  9. Stakeholders Primary Interest • National Archives and Records Administration(NARA) R&D - Long Term Knowledge retention of product model data for historical data retrieval and governmental reconstitution • JEDMICS / NESDR Storage and retrieval of engineering drawings and product model data • Defense Logistics Agency (DLA) Use of product model data for weapons system support • NAVSEA use of product model data for ships and ships systems evaluation and support

  10. Navy Uses for Long Term Retention of Data • New Ship Designs Even when revolutionary, large portions are based upon extension of existing designs • In-service Operational and Logistical support • Repairs USS Cole, USS Intrepid, USS New Orleans and SSN Hartford, etc • Decommissioning: Identification of hazardous materials if scrapped, Live Fire Test & Evaluation (LFT & E) analysis and documentation, National Defense Reserve Fleet

  11. Use Cases Assist in the definition of data requirements

  12. Why the TWR 841? This ship was selected for our project because it is in-service, has a complete set of drawings available for distribution, and is: Approved for Public Release: Distribution Unlimited. This ship is used to assist in sonar tests & locate and retrieve torpedoes and missile drones.

  13. Length overall 120 ft 8,700 gal. Fuel Capacity Potable Water Capacity  1,300 gal. Beam, Max 25 ft. Missile Washdown Water Capacity Draft (full load) 7 ft. 5 in. 1,100 gal. Displacement (full load) 248 LT 1700 nm Range Electrical Displacement (minimum operating load) 221.75 LT 450 VAC three phase 60 Hz. 120 VAC single phase 60Hz. 24 VDC. 14.7 knots. Speed Power 1140 shp at 1800 rpm. Crew 18 Engines Two (2) Caterpillar Model 3512 V12 Construction Welded steel construction with plates welded over transverse and longitudinal bulkheads and transverse frames Propellers Two (2) manganese bronze, 54 in diameter, 46.8 in pitch, 4 blade What is the TWR 841? Torpedo Weapons Retriever Characteristics 120 Foot Torpedo Weapons Retriever The Torpedo Weapons Retriever is utilized in support of underwater acoustic submarine operations and torpedo exercises. It is designed to launch and retrieve acoustic devices as well as retrieve missiles and torpedoes in the ocean. The TWR 841 is based out of the Naval Undersea Warfare Center located in Newport Rhode Island.

  14. Path to TWR-49 CM controlled native source data Navy Common Product Model Archived TWR Hull/molded forms Rhino Deckhouse Structure SolidWorks Ship LEAPS Archived Ship Product Model LEAP STEP Native Sensors/Antennas SolidWorks Hull Structure/ER Machinery ShipConstructor Data content Data format Supplies data Attributes/Analysis results/ requirements Project IDE / Native DB References data

  15. Common Product Model Data Environment as directed by COMNAVSEA on 04 Feb 2008

  16. Leading Edge Architecture for Prototyping Systems (LEAPS) • LEAPS is a framework developed to support virtual prototyping in the context of conceptual and preliminary ship design and analysis. • Navy Common Product Model

  17. One Program, Many CAD systems DDG 1000 O & S activities Feasibility study /Concept Design Preliminary Design Contract Design Detail Design & Construction (DD & C) Design AutoCAD- FASTship, Rhino, UGS, Pro-E, CATIA V4 & 5,(CAD) AutoCAD, CATIA & UGS (CAD) CATIA V5 & ShipConstructor (CAD) AutoCAD? CATIA? (CAD) CAD Tools UC4 UC1 UC2 UC5 Use case UC3 UC7 UC6 UC8 UC9 UC10 Tools usage from DDG-1000 program DDG-1000 image from http://www.globalsecurity.org/military/systems/ship/dd-x-schem.htm

  18. Data Sources : TWR 841 Native systems ShipConstructor • AutoCAD based • Equipment below main deck • Structure below main deck • Distribution Systems below main deck SolidWorks • Deckhouse Structure RhinoCAD • Molded Forms • Compartmentation • Equipment LEAPS • NAVSEA Product Model Repository • Integration tool

  19. Modeling Tool ShipConstructor ShipConstructor was selected as our product modeling tool as it is relevant to NARA, NAVAIR and DLA because it is AutoCAD based. It is also relevant to NAVSEA due to the following shipbuilding projects. • Deepwater – National Security Cutter (NGSS Avondale) • LCS – both variants (Gibbs & Cox on Lockheed Martin program, Austal on General Dynamics program) • CVN – 21 deckhouse (NGSS Avondale for Newport News) • ONR E-Craft (Guido Perla for Alaska Ship & Drydock) • ONR X-Craft (Sea Fighter) – Nichols Brothers

  20. SoldiWorks was chosen due to current Navy Ship Design program usage • Rhinoceros CAD: Used for Hullform, molded surfaces, compartmentation, HVAC. • LEAPS (Leading Edge Architecture for Prototyping Systems). Secondary Modeling Tools Tool Selection

  21. TWR 841 : Test Data Compartmentation/ Rhino

  22. TWR 841 : Test case HVAC / Rhino

  23. TWR 841 : Test case Ships Structure / ShipConstructor

  24. TWR 841 : Test case Ship’s Piping / ShipConstructor

  25. TWR 841 : Test case Ship’s Piping / ShipConstructor

  26. Test Data : TWR 841 ShipConstructor Product Model

  27. Test Data : TWR 841 SolidWorks Geometry

  28. Test Data : TWR 841 LEAPS Product Model

  29. Retention of Data : TWR 841 Construction Units Life cycle support requires • production hierarchy (interim products) • and design hierarchy (system) 2310 2210 ASSY_003 ASSY_004 ASSY_002 ASSY_001 ASSY_002 3110 ASSY_001 ASSY_002 ASSY_001 ASSY_003 1110 2110 ASSY_003

  30. Product Structure Product Model Based

  31. Functional System Weapon System Subassembly Part Product structures are related Production / Design hierarchy A collection of parts & sub-assemblies that operate together to accomplish a specific task A fully operational weapon system that is comprised of multiple functional systems to complete the intended mission A single component that is fabricated or purchased A collection of parts that are used together as portion of a functional system

  32. Files stored on Data Grid TWR Builders Drawings

  33. Data stored on Data Grid Transverse Bulkhead at Frame 11

  34. Accomplishments • Created product model • Research and Development of required Product Model Data to support engineering analysis • Implemented a second native product modeling environment • Developed, implemented, and testing STEP AP203 / AP214 for use in archiving Ship Product Model Data • Transitioned the SolidWorks model to LEAPS • Initiate the use of the Data Grid for storing native CAD models, STEP files, and the TWR source drawings.

  35. Ongoing activities • Developing, implementing, and testing additional STEP AP’s for use in archiving Ship Product Model Data • Transitioning ShipConstructor model to LEAPS • Transitioning the SolidWorks model to LEAPS • Develop the product model repository architecture incorporating native CAD, the NAVSEA product modeling system, STEP, and ad-hoc neutral file formats using the Data Grid. • Develop more automated methods for increasing our efficiency in populating the Data Grid. • Develop a structural model of the engine room having enough detail to perform a stress analysis so that we can demonstrate the relationship between CAD models, FEM, analysis data, results, and documentation. • Perform a topside analysis of the C4N equipment on the TWR and relate the LEAPS data, analysis data, results, and documentation. • Perform intact and damage stability analyses using SHCP and capture results

  36. QUESTIONS? COMMENTS

More Related