7 3 iyer

PLM for the US Army : PLM for the US Army Dr. Raj Iyer Team Lead, PLM Technologies US Army Tank Automotive RDE Center, Warren, MI Presented at the 7th NASA-ESA Workshop on Product Data Exchange (PDE 2005) April 22, 2005


Slide2 : Combat Vehicles • Tactical Vehicles Trailers • Construction Equipment Materiel Handling Equipment • Tactical Bridges Fuel & Water Dist Equipment • Sets, Kits & Outfits Chemical Defense Equipment • Shop Equipment Howitzers • Large Caliber Guns Mortars • Rifles Machine Guns • Ammunition Aircraft Armaments • Demolitions & Explosives Rail • Watercraft Fuel & Lubricant Products • Non-Tactical Vehicles Plus Technology Development for the Objective Force Capital Value of TACOM Equipment $81.7B 141 Allied Countries own TACOM Equipment All Army Parent UICs Contain TACOM Supported Equip 2993 Fielded Systems Supported > 26,000 Components Systems Supporting Army Readiness


Driving Factors : Driving Factors Product data is distributed among RDECs, PMs, LCMCs and OEMs Product data formats and systems to manage product data are not standardized – CAD and PDM interoperability issues Data exchange and collaboration among organizations is inefficient and time consuming Fundamental requirement towards a true Army Product Lifecycle Management (PLM) strategy (SALE) Need for integrated product data throughout the product’s lifecycle spanning both engineering and logistics Conceptual models, 2D drawings, 3D solid models, modeling & simulation data, analysis models, test data, repair & maintenance history, IETMs, assembly instructions Need for a single set of logically unified product data


Challenges : Challenges Heterogeneous systems and formats for product data Extended lifecycle Legacy data Systems of systems integration Spiral development Performance Based Logistics (PBL) Contractor Logistics Support (CLS) Parts obsolescence Disposal issues


Standards vs. Point-to-point Solutions : Standards vs. Point-to-point Solutions  


The Need for Standards : The Need for Standards No guarantee that any of these commercial systems will last as long as the Army’s product lines Version independence and upward compatibility Variety of commercial middleware solutions are available Point to point solutions Expensive to maintain and upgrade DoD mandate for open architecture standards-based systems leveraging best commercial practices


The Solution : The Solution Use of international standards ISO 10303 – also known as STEP PDM Schema STEP is a neutral format not just for 2D/3D product data but also for PDM interoperability Specific STEP Application Protocols are already widely used in private industry STEP is well supported by most of the major PDM/ CAD vendors – PTC, SAP, UGS, MatrixOne, Dassault STEP is starting to be standardized for 3D solid models at the DoD (Navy and Air Force have mandated it already) Enormous potential for long term retention and archival of product data STEP has the potential to save $928 million (2001$) per year by reducing interoperability problems in the automotive, aerospace, and shipbuilding industries alone


Architecture for the TACOM Lifecycle Management Command : Architecture for the TACOM Lifecycle Management Command STEP – STandard for Exchange of Product data ACMS – Automated Configuration Management System ACE – Advanced Collaborative Environment PLM+ - Product Lifecycle Management Plus SALE – Single Army Logistics Enterprise


Vision : Vision Federated system of systems approach to product data management Web-based access Product data on demand Product-centric data management Single access and control point Improved real-time data collaboration Implement open data standards and best practices Manage heterogeneous data formats Automate CM/DM functions with workflows Manage product structures/ BOMs Maintain “as-designed”, “as-built”, “as-maintained” BOMs Manage serialized parts Access OEM controlled product data Integration to ERP and logistics systems


Slide10 : Data Exchange Workflow


STEP for the DoD Acquisition Cycle : STEP for the DoD Acquisition Cycle


STEP Data Management APs : STEP Data Management APs STEP AP 214 CC6 – PDM Schema STEP AP 232 – Technical Data Packaging STEP AP 239 – Product Lifecycle Support (PLCS)


PDM Schema : PDM Schema Life-cycle


EXPRESS Data Manager Software : EXPRESS Data Manager Software


Implementation Methodology : Implementation Methodology Import PDM Object Model into EPM Model Migrator software Map objects and attributes between PDM and STEP Where one-one mapping is not possible, write code in EXPRESS-X Package software as a translator Web enabled links inside PDM callable by user screen or callable as batch process


EPM Model Migrator Mapping Software : EPM Model Migrator Mapping Software


Federation-based Product Data Synchronization : Federation-based Product Data Synchronization


For more details : For more details Dr. Raj G. Iyer Team Lead, PLM Technologies Engineering Business Group TARDEC E-mail: raj.iyer@us.army.mil COM: (586) 574-7186