Applying Open Standards for PLM System Interoperability William C. Burkett Eurostep America, Inc May 2007
Purpose Present the application of open PLM standards in the implementation of open interoperability solution. Case Study: Volvo Case Study: US Army s Falcon program Presentation PLM, PLCS, & Open Standards Share-A-space Volvo Falcon Summary & Conclusions
PLM, PLCS, & Open Standards ISO 10303-239 (PLCS)
The Product Life-cycle Life-cycle Phases: Use Validation Maintenance/ Repair Scrapping/ disassembly Verification Production planning Production Product Individual Product Individual Product Individual Design Requirement analysis
PLCS: Extended Enterprise enabled by Internet technology Internet-based architecture and federated data models make possible implementations involving thousands of users across many sites Extended Enterprise Integration Tier 2 Suppliers Tier 1 Suppliers Dept Enterprise Customers Partners Extended Enterprise of OEM s, Customer, Partners and Suppliers Product Lifecycle Management (PLM) Enterprise Integration through dedicated networks Domain specific information systems (e.g. CAD, MRPII, Planning) Concept Assessment Demonstration Manufacture In-Service Disposal Product Life Cycle
PLCS: Extended Enterprise enabled by Internet technology Internet-based architecture and federated data models make possible implementations involving thousands of users across many sites Extended Enterprise Integration Tier 2 Suppliers Tier 1 Suppliers Dept Enterprise Customers Partners Extended Enterprise of OEM s, Customer, Partners and Suppliers Product Lifecycle Management (PLM) Enterprise Integration through dedicated networks Domain specific information systems Capture product info for support use (e.g. CAD, MRPII, Planning) Develop the support solution PLCS Domain Maintain product Provide feedback Concept Assessment Demonstration Manufacture In-Service Disposal Product Life Cycle
Product Life Cycle Support (PLCS) Extended Enterprise Importance of PLCS When set against a timeline the picture looks more like this! Extended Enterprise Integration Tier 2 Suppliers Tier 1 Suppliers Dept Enterprise Customers Partners 5 10 years Design for Supportability Typically 25 50 years Operational Life PLCS Domain In Service Support and Operational Feedback C A D M In-Service D
Challenge background Kinds of Information and Interdependencies Influence On Product Design Designs Type of Things Design Engineering Product Design Support Item Design In-Service Real Things Product Individual Operational Features Embedded Support Features Requirements For Support Elements Infrastructure Design Support Engineering Impact on Design Support System Support Items Support System Design Support Data Support Activities HR Requirements Support Infrastructure
Interoperability in Product Support Manufacturing Manufacturing Design Design Concept Concept In service phase In service phase Disposal Disposal OEM Design In-Service Real Things Service Contractors Service Contractors Service Contractors www and VPN Prime
Life-cycle Change Management Maintenance Requirements Types Maintenance Analysis Maintenance Plan LSAR Fault state definitions Maintenance Task Usage Maintenance Task Planning Change Management Maintenance Schedule Maintenance Task perfomance Actual Fault states Individuals Spare Parts Configuration Design Design Configuration Requirements Manufacturing BOM Design Analysis Domain Definitions (CAD, etc) Definition As-built Individual Configuration As-maintained Location Management
All PLCS ISO 10303-239
So what does full PLCS model cover? Requirements management Document and File management Through life Configuration Management Configuration Management of Design of product Configuration Management of individual products Definition of any kind of support task relating to a product Definition, location and quantification of support resources History of individual product configuration, use and state/condition History of work done and resources used Integration of the above over a complete life cycle.with optional complexity to meet user needs
Implementing PLCS: Share-A-space
Interoperability Solutions Prime Responsibility/ OEM Responsibility KLU SL SL Analysis Engg S SL P1 SL P2 P3 Design Operation SL SL SL SL ETL KLU Maint Repair P1 P2 P1 P3 P3 P4 S Sales ETL P1 P3 P4 Service
Share-A-space in short Share-A-space provides an outof-the-box information integration tool using open standards Share-A-space provides an information value increase by information consolidation in heterogeneous system and organizational environments Share-A-space integrates product information across the product life cycle Share-A-space decouples information from business process
Share-A-space architecture System Data import/export Data mapper Web access API integration Business process logic XML & STEP Part 21/28 HTML SSL WebService Import/ export logic ASP WebService Share-A-space Application Server COM Business Object Layer MTS Persistent objects handling and Database binding Information logic TCP/IP Oracle Information representation
Case study: Volvo Extended Enterprise & Consolidation of Information
Volvo sharing of engine product structure data Volvo often had outdated product data, leading to inefficient information management Difficult and time consuming to get the right data High percentage of the spare parts where erroneously returned High risk of design errors due to outdated third party information Time consuming to produce a correct parts catalogue
Volvo Responsibility Deutz Responsibility Bus Penta S KLU SL SL SL P1 SL P2 P3 Design PT SL SL SL SL ETL KLU CE Truck P1 P2 P1 P3 P4 S ETL Sales P1 P3 P4 Renault etc. Service
Design Dwg Spare Part Breakdown ETL Picture Design Breakdown
Case Study: FALCON US Army Federated Army Lifecycle Collaborative e-nterprise
FALCON Architecture (Process-centric view) Design/BOM Mapper 2a (AP214) Mapper 1 (Import) Design/BOM SAP (XML/CXV) Serial+ Config. SAP (XML/CSV) Rules#1 Mapper 2b Export/Report (AP214) Mapper 1 (export) AP214.p21 Design/BOM ECO SAP R/3 AP214.p21 Rules#2 Rules#3 Notification on create CR/WR Notification on? <WS> Ind.Conf LCN Struct SAs GUI WS Client Notification on? LCNStruct 1388-2B Mapper UID Mapper Serial 1388-2B Export/Report UID file Rules#4 Share-A-space Server
Scoped FALCON Architecture 3D Solid Models AM General PLM TDP records ACMS Design Change Ser Part PLCS Viewer 5 Design Change UID Registry 7 PLCS Master Data Integrator (PLCS-MDI) PLCS services
AMG SAP -> PLCS MDI -> TARDEC ACMS Windchill V2 As Designed Version Release PLCS MDI Design Change Release V1 V2 ACMS US Army Design View V2
AM General powerlog -> PLCS MDI LSAR PLCS MDI Design View LCN Breakdown LCN Breakdown
Plugin Structure Browser PLCS MDI LCN Breakdown Design View ACMS US Army Design View X As-built View PLCS Master Data Integrator (PLCS-MDI) Import/ Import/ export export logic logic Share-A-space Application Server PLCS Web Srvs COM SAs GUI Business Object Layer MTS Persistent objects handling and Database binding ASP.NET TCP/IP Oracle
Plugin Structure Browser PLCS MDI LCN Breakdown Design View ACMS US Army Design View X Windchill Plugin As-built View PLCS Master Data Integrator (PLCS-MDI) Import/ Import/ export export logic logic Share-A-space Application Server PLCS Web Srvs COM SAs GUI Business Object Layer MTS Persistent objects handling and Database binding ASP.NET TCP/IP Oracle
Summary & Conclusions Use of PLCS (an open standard) as the mediation format provides: Better system positioning for future system interoperability Reconciliation of product data cross-application Configuration control of lifecycle views Transparent interoperability services Systems are better positioned for improved product support