AP233 applied to the SOA/PDIF framework

1. AP233 applied to the SOA/PDIF framework Eva Schwer SWG/PLM Solutions June 2007

2. Agenda • The IBM PLM Vision 2007 • Innovation Enablers • PLM Processes Transformation (SE) • IT Solutions & Architecture Transformation (SOA) • Open Standards for PLM supporting PDIF • PLM Standards • SE Standards • Conclusion

3. Agenda • The IBM PLM Vision 2007 • Innovation Enablers • PLM Processes Transformation (SE) • IT Solutions & Architecture Transformation (SOA) • Open Standards for PLM supporting PDIF • PLM Standards • SE Standards • Conclusion

4. Product Lifecycle Management Product Lifecycle Management covers a broad set of vital business processes Portfolio Planning Concept Development Production & Testing Maintenance & Support Retirement & Disposal Design Program Management Marketing, Sales and Distribution Program Management Mechanical Product Design & Development Electrical Product Design & Development Software Design & Development Finance, Business Controls and Reporting • Software for managing a Product Lifecycle as a sequence of iterative processes performed across many teams & suppliers Product Data Management Systems Engineering Real Virtual

5. Moderate 22% A lot Little or no 65% 13% CEO’s acknowledge that the world is constantly moving Rapidly evolving market forces drive theneed for innovation 87% of CEOs believechange is needed to drive innovation • Drivers for change • Intensified competition • Escalating clients expectations • Technological advances • Regulatory concerns • Market shifts • Globalization Industry Challenges Extent of fundamentalchange needed over next two years Source: 2006 IBM Global CEO Survey

6. IBM PLM Vision 2007:Enabling the Expanded Scope of PLM Customer Needs Management Customers Maintenance and Support Product portfolio Management Distributors/Retailers OEMs Production and Test Requirements Management Manufacturers Development Partners Manufacturing Process Planning Concept Development Suppliers Simulation and Analysis Collaborative Design Sourcing

7. Finance, business controls and reporting Sales and Marketing Program Management Materials Management IBM PLM Vision 2007:Enabling the Expanded Scope of PLM Customer Needs Management Customers Maintenance and Support Product portfolio Management Distributors/Retailers OEMs Production and Test Requirements Management The Product Development Cycle Manufacturers Development Partners Manufacturing Process Planning Concept Development …and the real scope of PLM Suppliers Simulation and Analysis Collaborative Design Sourcing

8. Agenda • The IBM PLM Vision 2007 • Innovation Enablers • PLM Processes Transformation (SE) • IT Solutions & Architecture Transformation (SOA) • Open Standards for PLM supporting PDIF • PLM Standards • SE Standards • Conclusion

9. Expanding the .. Shrinking the .. VIRTUAL PHYSICAL Integrated Systems Design and Mock-up Lean Production PLM Process Transformations • PLM is transforming from design-centric, disparate software tools to an end-to-end, product lifecycle business solution • PLM to shift towards Systems Engineering: Virtual realistic real-time simulation of all the engineering processes for any industrial systems

10. Product Needs Test Compliance Matrix RequirementsManagement Validation FunctionalAnalysis Integration OEM Global SystemArchitecture design LogicalDesign Test Req. Management Validation Fluidic FunctionalAnalysis Integration Disciplines/Suppliers Electrical LogicalDesign Test Equipments ArchitectureAnd Design Electronic PhysicalDesign Software Mechanical PLM Process Transformation: Collaborative Systems Engineering Program & Project Mgt / Configuration Mgt / Supply Chain Mgt / Collaborative Engineering

11. Systems Engineers Manufacturing Manufacturing Engineering Engineering Engineering Life support Life support Enterprise Enterprise - The Integrated Systems Engineering Approach CollaborativeProduct Engineering CollaborativeSystems Engineering Distant site Distant site Desktop Supplier Systems Supplier Systems Systems Discipline specific - - PLM Collaboration Systems Desktop Discipline specific PLM Collaboration Systems Systems Systems • Systems Engineering and discipline Engineering in the same “desktop” • “whole System abstraction” shared by all disciplines • Systems Engineering not efficiently « connected » to Discipline Engineering • Isolated systems engineering “desktop” … bring collaboration towards system level

12. Agenda • The IBM PLM Vision 2007 • Innovation Enablers • PLM Processes Transformation (SE) • IT Solutions & Architecture Transformation (SOA) • Open Standards for PLM supporting PDIF • PLM Standards • SE Standards • Conclusion

13. Case Study: Payments Processing Customer Bank Shared Service Bank 2 – “Supplier” Outsourced IT Solutions & Architecture Transformation • SOA (architecture) • = Reuse, Flexibility SOA An architecture (and a set of principles and best practices) where business functions are built as services (or components) exposed and orchestrated For providing interoperability and increasing IT flexibility • Web Services (standard) • = Interoperability

14. 3. Enterprise Collaboration - Portals and dashboards to Applications 2. Enterprise Process Management – Cross-application processes 1. Enterprise Integration - Management of PLM and Enterprise Information Servers Software Storage Integrated PLM SOA Environment Project/Business Management (OEM &/or Suppliers) Engineers(OEM &/or Suppliers) Quality Operations Sales Service Product Development Integration Framework IBM SOA Foundation Decision point—mandate system commonality (“rip & replace”) or integrated existing systems (“best of breed”) through SOA! PLM Application Systems Enterprise Application Systems ERP Other Enterprise Applications EAM Requirements Management Data Management Data Management Data Management Data Management Program and Portfolio Management Enterprise PDM Software Authoring Analysis & Simulation Mechanical Authoring Electrical Authoring 14

15. Agenda • The IBM PLM Vision 2007 • Innovation Enablers • PLM Processes Transformation (SE) • IT Solutions & Architecture Transformation (SOA) • Open Standards for PLM supporting PDIF • PLM Standards • SE Standards • Conclusion

16. IBM: influencing and shaping open standards for PLM • 1980s -1990s • Java and ebXML • ISO STEP • OMG UML and XML • OpenGL • SQL • AIAG • IEEE • VRML • ANSI • RosettaNet • 2000 - 2005 • Web Services / Interoperability • Eclipse to Open • UDDI • SOAP • W3C XML • SOAP4J to Open • Open Systems • 2006 - 2007 • OMG PLM Services 1.0-3.0 • STEP AP 214, 210, 219, 233, 239.. • ProSTEP • PDES Inc • SASIG, AutoSAR, JAMA other industry groups • IBM Enterprise Interoperability Center • IBM Services Oriented Architecture • BPEL • WSBPEL • WS-TX • WS-TC • OASIS Over 160 business integration technology patents First integrated private UDDI directory First Web Services Gateway

17. Standards across PLM Lifecycle (Ministry of Defense)

18. Using Standards for PLM SOA • The integrated PLM SOA environment defines a set of well-defined architectural principles, paradigms and best practices to enable loosely coupled interaction between applications. • It promotes loosely coupled interaction between participating applications, based on well-defined interfaces, using open standards. • The Product Lifecycle Support – PLCS (based on AP239) is an international standard for product support information, covering the complete product lifecycle

19. About Product Lifecycle Support (PLCS) • The purpose of the OASIS Product Life Cycle Support Technical Committee (TC) is to establish structured data exchange and sharing to support complex engineered assets throughout their total life cycle. • These Data Exchange Specifications (DEX’s) are based upon ISO 10303 (STEP) • Application Protocol 239 (Product Life Cycle Support). • The OASIS PLCS TC is responsible for defining, developing, • testing and publishing of OASIS PLCS DEX’s, and for liaison with ISO TC

20. Product Life Cycle Support (PLCS)PLCS will enable cost effective information exchanges 3. Stock Mgmt 5. Requirements Management 1. Support Data 2. Maintainers Viewing Tool 4. Maintenance Management 6. LSAR 7. FMECA LSA Data Maintenance Mgmt Data FMECA Results Maintenance Mgmt Data Support data Part data Functional Req. PLM SOA (PDIF) - compliant with PLCS (AP239) PLCS compliant information exchanges Tech Pub Data Maintenance Mgt Data Defects& Failures Design Data Design data Distribution Data Parts Data 9. Product Data 13. Distribution, Transportation 8. CAD 10 IETM 11 Parts Supplier Database 14 Defects & Failure Reporting 12 Depot Maint Mgmt In future, support system integration will be easier to implement

21. Agenda • The IBM PLM Vision 2007 • Innovation Enablers • PLM Processes Transformation (SE) • IT Solutions & Architecture Transformation (SOA) • Open Standards for PLM supporting PDIF • PLM Standards • SE Standards • Conclusion

22. High SLP tubing COM.9 COM.2 COM.7 COM.4 Specific Reagent Common Reagent Sample store Liquid waste store store store Component Component Component Component Tubing substrate aspiration Wash waste tubing Needle sample aspiration Needle SR aspiration COM.6 COM.10 COM.8 COM.11 Substrate Reagenter station Sampler station Wash station dispenser Component Component Component Component Needle substrate dispensing Needle sample dispensing Needle SR dispensing SR store cable COM.1 COM.5 Optomechanic link Wash needle aspiration Bowl handler Photomultiplier RU.1 Wash needle dispensing Operator Component Wash station cable Component request Bowl holder Hand+button Operator AND AND Circulation mechanism Component run list Nb of Changes SR station cable System COM.3 Cycle 11s • As designed Embedded controler Component RU.4 Store Waste No sample & restart stop BC sampling sampling RU.2 RU.3 RU.5 RU.7 LP AND AND OR LP Store run list Add samples Treat samples End of run ? RLU last sample treated LE run list RU.6 stored Store RLU • As built RLU buffered • As maintained Disciplines Engineering PDM ERP Enterprise PDM Low Time System Engineering within the Product Lifecycle • As operationally • required and • architected System Engineering PDM Concept Development Production Operation & Maintenance Systems Engineering overlaps a significant portion of Product Lifecycle Management. Both PLM and SE are concerned with managing the multiple views and interrelationships of product informations to maintain coherence between time and place.

23. Systems Engineering Standards Process Standards Ex: EAI 632, ISO 15288, CMMI,… Architecture Frameworks Ex: DoDAF, MoDAF, … Modeling Methods Ex: SADT, OOSE,… Implemented by tools Modeling & Simulation Standards Ex: UML/SysML (modeling), HLA (Simulation) Interchange Standards Ex: MOF/XMI , STEP/AP233, CADM,…

24. The INCOSE Systems Engineering Vision 2020:Model Based Systems Engineering (MBSE) • MBSE is the formalized application of modeling to support the SE process • MBSE is part of a long-term trend towards model-centric approach that has evolved in other engineering disciplines • MBSE is expected to replace the document-centric approach and to become fully integrated into the SE process

25. Model Based Systems Engineering (MBSE)Essential characteristics • « Domain-specific languages and visualisation that enable the systems engineer to focus on abstract modeling of the user domain » • « Modeling standards based on a firm mathematical foundation that support high fidelity simulation and real world representation » • « Extensive reuse of model libraries, taxonomies, and design patterns » • « Standards that support integration and management across a distributed model repository » • « Highly reliable and secure data exchange via published interfaces »

26. Standards for Model-Based Systems Engineering • Data and Model Interchange • AP233 - The ISO standard for exchanging systems engineering data • DoDAF – DoD Architecture Framework • Defines standardized view of systems information • CADM = Core Architecture Data Model • SysML – Systems Modeling Language • Standard modeling language and notation for systems engineers These standards are highly complementary.

27. Data and Model Interchange – AP233 • The industry is pursuing a neutral exchange format for systems • engineering data because: • Systems are more complex (nr of interfaces and multi-discipline) • Tools are proliferating and they are more complex • Multi-company collaboration is increasing • Data exchange between systems engineering applications/organizations is not simple

28. AP233 Concept Model

29. AP233 • AP 233 defines a vendor-neutral, structured format for exchanging • and sharing systems engineering data. The scope of AP233 includes: • Systems behaviour • System structure • System modelling • Decision support • Requirements • Analysis • Trade studies • Program & Project Management • Verification & Validation • Risk management • Issue management

30. rules (moved to AP210) AP233 Scope - Readiness breakdowns requirements PDM product structure config control static structure system sub-system text-based person & org functional breakdown WBS security property-based behaviour link to analysis state-based verification & validation model presentation function-based measurement risk Legend Complete Edition 2

31. They share a common core! AP233/PLCS Relationship AP233 PLCS Classification V & V Maintenance Product Structure State Machines Change Management Support Tasks Function Diagrams Approvals, Security, Status APSI Requirements Management Risk Management Support History Schedule Activities Link to Analysis Organizations Messaging Property

32. Agenda • The IBM PLM Vision 2007 • Innovation Enablers • PLM Processes Transformation (SE) • IT Solutions & Architecture Transformation (SOA) • Open Standards for PLM supporting PDIF • PLM Standards • SE Standards • Conclusion

33. Conclusion • Innovation Enablers: • Business Process Transformation: Systemic approach, Model based systems engineering • IT Transformation: Product Development Integration Framework based on SOA • SOA Technology Enabler: • Web Services based on Normes and Standards

34. Current PDIF focus Conclusion Next major areas of PDIF focus to address SE