Demonstration of Product Data Sharing The industrial context

1. Demonstration of Product Data SharingThe industrial context • Collaborative Product Development • Product Data Management • Through Change Management Process • Configuration Management • All along the lifecycle of the industrial project • Within a networked organization • OEM • Risk sharing partners • Equipment suppliers • Sub-Contractors (for Product design to Product Manufacturing)

2. FEASABILITY SERIES CONCEPT DEFINITION DEVELOPMENT SERIES Stress Design Reference Base Master Geometry Space Allocation Mock-up Equipment Installation Requirement Dossier Early involvement of down stream activities using the virtual aircraft Airbus Feasibility Concept Definition Development Series Concurrent Engineering Support Concept System Installation Requirement Dossier Definition Model Definition Production Industrial context

3. Pilot : the industrial context • The problems • Heterogeneity between members of the network • Enterprise organization • Enterprise processes • Applications • Software Products (Commercial of the shelves) • Can’t be solved by homogenization inside the enterprise • Who will drive? • One enterprise can belong to several network • Needs • Reduce time, resource and efforts to quickly and efficiently allow an enterprise to • Join the networked enterprise • Collaborate within the network enterprise • Leave the virtual enterprise • By • interconnecting business process • Interconnecting workflows derived from business process • Interconnecting applications and workflow systems • Support information flow and coherency of configured distributed product data

4. Pilot : the industrial context • Requirements for the to-be situation • Definition of a collaboration space (with supporting organization – Network Collaborative Development Platform Organization _ NCDPO) • Shared by all the enterprise of the network • Based on Manufacturing and ICT open standards • Methodology and tools to allow • Collaboration Space Organization models, Infrastructure definition, development, exploitation and evolution • Process to join the network: interconnect the organization and plug internal application to the network through collaboration space facilities • Process to establish collaboration between two or more partners for each set of supported process (here the change and configuration processes but it can be some other processes covered by the Network Collaboration Centre) • Process to leave the network • Addressing it at different levels • Governance (by Urbanism of collaboration networked infrastructure) • Organizational (by enterprise models, that are application independent – for non IT people) • Application level – by software engineering methodology and application modeling in the context of the enterprise model • ICT level – by usage of technology that allows communication on runtime between • Several operational application • Operational applications, Software engineering software and enterprise modeling tools • Vertical federation of models/applications • From ICT to Application • From Application Models to Enterprise Models • And the reverse

5. Pilot : the processes • Establishment of the Collaborative space • Definition and design • Who : Networked Organization Collaboration Space Architect and Consortium behind the network • Tools : Enterprise Modeling tools • Development • Who : ICT people • Tools : standards, software engineering tools, Commercial of the shelve software • Exploitation, maintenance and evolution of the collaborative space • Who : Networked Organization Managers, ICT people

6. Pilot : the processes • Joining the networked organization • Identification of B2B processes to be plugged on the collaboration space • Business people • Mapping (process, roles, actors, tasks, stakeholders, objectives…) • Business+disciplines experts • Tools : modeling-mapping tools at enterprise/business level. Includes enterprise modeling tools and software engineering tools • Implementation of the mapping • Developers (not traditional, those using, parametering and controlling execution of services provided by ATHENA for transformation, negotiation…)

7. Pilot : the processes • Participating the networked organization • Launching instance of collaboration process • External Change Management Process • Actors • Virtual SpaceCraft Program • Integrator (EADS) • Design Office • Engineer E • Engine Provider • Design Office • Landing Gear Provider • Design Office • Engineer F • Tools • local PDM system- as workflow enactment service, connected to the Collaboration Space tool

8. Pilot : the processes • Leaving the networked organization • Disconnecting the organization from the collaborative space • To update information concerning the leaving partner in the networked space to indicate that he is no more part of the network

9. Establishment of the Collaborative Space Piloting Conceptual and technical Infrastructure

10. Virtual SpaceCraft Program Organization of views PROCESS SERVICE INFORMATION Dictionary Thesaurus Relationships (Natural Language) CONCEPTUAL BUSINESS PROCESS (Natural Language) BUSINESS SERVICE (Natural Language) Should be shared by Enterprise modeling tools & application modeling tools But not always the case LOGICAL BUSINESS PROCESS With Formal Language (Modeling) BUSINESS Service With Formal Language (UML Profile, other) Information Model With Formal Language (Modeling) Heterogeneous And fractioned Metal models PHYSICAL BUSINESS EXECUTABLE PROCESS With Formal Language (Executable) BUSINESS Services (accessible at runtime) Data Models With different accurate formats (DB, Files, Variables) Heterogeneous Programming languages And Technical platforms (WEB services, CORBA, AS)

11. Virtual SpaceCraft Program Business Service View Standards Based (Reference Models) (Setting Up the NECPO - pilot 4 – related on A4 and A1 results for conceptual phase) Shared Business Process repository Business Workflow Modeling & simulation IHM Product Information Shared Configured Product Information Shared Configured Product Data Collaborative Shared Space Worklist Handler Services IHM client Registry Participants Services Shared workflow Process repository PDM shared repository Shared Configured Product Information Product Data Upload Download Product Metadata Display IHM Client Shared Configured Process Model PLM and PDM SERVICES Service Query Lookup Service Application Access Services Business Worflow Enactment Service Transformation & Quality Checking Services Workflow Administration Monitoring service IHM Client Enterprise A (kind:OEM) Enterprise xxx (kind: any) Enterprise B (kind: Supplier) Supplier PDM Services Workflow Engine Of PDM Supplier PDM Services Workflow Engine Of PDM Supplier PDM Services Workflow Engine Of PDM PDM System PDM System PDM System Private Configured Information Private Configured Information Private Configured Information

12. Workflow Relevant Information Participants Actors Application Person & organization Information related To single activity Workflow Relevant Information Workflow Relevant Information Workflow Relevant Information Participants Actors Participants Actors Participants Actors Application Person & organization Application Person & organization Application Person & organization Information related To single activity Information related To single activity Information related To single activity Business Process View (Setting up the Networked Enterprise – pilot 4 related to A1) (Participating the Networked Enterprise – pilot 2 and pilot6 related on A2-A5-A6 inception and evaluation) Standards Based (Reference Models) Virtual SpaceCraft Program Collaborative Shared Space Enterprise A (kind: OEM) Enterprise B (kind: Supplier)

13. Workflow Relevant Information Participants Actors Application Person & organization Information related To single activity Workflow Relevant Information Workflow Relevant Information Workflow Relevant Information Participants Actors Participants Actors Participants Actors Application Person & organization Application Person & organization Application Person & organization Information related To single activity Information related To single activity Information related To single activity Business Process View (Participating the Networked Enterprise – pilot 2 and pilot6 related on A2-A5-A6 inception and evaluation) Standards Based (Reference Models) Virtual SpaceCraft Program Collaborative Shared Space EADS Landing Gear Provider

14. Virtual SpaceCraft Program Pilots PDM repositroy Collaborative Shared Space STEP Application Protocols PLM SERVICES AP214 WSDL Workflow Engine XPDL/WSDL BPEL Engine BPEL Pilot 2 Collaborative Change Management Process Joining & participating Pilot 4 MDA approach & projection on Open Technical framework Pilot 5 Virtual Space Craft Integrative Pilot 1 Setting Up and Entering the network Pilot 3 PLM Semantic Annotation One Supplier OEM Supplier PDM Services Workflow Engine Windchill Supplier PDM Services Workflow Engine Windchill PDM System PDM System Windchill Windchill

15. Pilot 1 • Setting up the network • The external change management process and the different public views of the internal change management process are defined using Enterprise modeling tools. Then they are used to generate the CBP public process within modeling tools (Maestro, Jawe) of the NCPDO, that is used to deployed the process on execution platforms (Nehemiah, Shark) of the NCPDO.

16. Relationships with enterprise modeling • Model of collaboration infrastructure, actors/stakeholders of the network, objectives and process of the network for • Governance • Reference model for integration/federation • Are to be entered in the enterprise modeling tool • The model should be based/compliant with POP* (Product Organisation People Model of reference) • Used Enterprise Modeling tool should allow import/export with • Maestro (model of reference?) • XPDL compliant tools (eventually) • And in the near future (i.e. the review) PIM4SOA (including BPDM - when available) (note : XPDL next version target to be aligned with BPDM)

17. Common Services Modeling Platform JaWE Business Process Modelling&Simulation (XPDL) OpenLDAP (LDAP) Execution Platform Apache Tomcat Axis WEB Server (JSP,HTTP,SOAP) PDM shared repositroy STEP Application Protocols SOAP SHARK Application access service WAPI agents JAVA CORBA jUDDI (UDDI,SOAP) XPDI PDM PLM SERVICES (AP214, WSDL) SHARK Worklist Client Service (Wfmc Interf 1) MAIL SHARK Workflow Engine Wf-XML services (XPDL/WSDL/LDAP Wf Facilities/CORBA) SHARK Administration Monitoring service (wfmc Interf 4) Active BPEL Service Composition (BPEL) Software components and products Standards Based (Reference Models) Option One: with standards and Open Source tools For modeling and execution platform Collaborative Shared Space

18. Software components and products Standards Based (Reference Models) Option Two: with specific solutions of ATHENA For Modeling and execution platform Modeling Platform Enterprise Modelling (MO2GO/ARIS/METIS/GRAI) POP*, PIM4SOA Maestro CBP Modelling Collaborative Shared Space Common Services OpenLDAP (LDAP) Jonhson Processing Chain Definition SOAP Gabriel Application access jUDDI (UDDI,SOAP) Execution Platform Jonhson SOAP messages Monitor Jonhson Processing Chain Execution Lindon WSDL processor PDM shared repositroy STEP Application Protocols Nehemiah Worklist Client Service Apache Tomcat Axis WEB Server (JSP,HTTP,SOAP) Nehemia/Jonhson Process exec. Engine (BPEL, Maestro...) Active BPEL Service Composition (BPEL) XPDI PDM PLM SERVICES (AP214, WSDL) Nehemiah Administration Monitoring service

19. Pilot 1 • Joining the networked organization • Identification of B2B processes to be plugged on the collaboration space • Business people • Mapping (process, roles, actors, tasks, stakeholders, objectives…) • Business + disciplines experts • Tools : modeling-mapping tools at enterprise/business level. Includes enterprise modeling tools and software engineering tools • Implementation of the mapping for interconnection of process enactment service and monitoring tools • Developers (not traditional, those using, parametering and controlling execution of services provided by ATHENA for transformation, negotiation…)

20. Common Services Modeling Platform JaWE Business Process Modelling&Simulation (XPDL) OpenLDAP (LDAP) Execution Platform Apache Tomcat Axis WEB Server (JSP,HTTP,SOAP) PDM shared repositroy STEP Application Protocols SOAP SHARK Application access service WAPI agents JAVA CORBA jUDDI (UDDI,SOAP) XPDI PDM PLM SERVICES (AP214, WSDL) SHARK Worklist Client Service (Wfmc Interf 1) MAIL SHARK Workflow Engine Wf-XML services (XPDL/WSDL/LDAP Wf Facilities/CORBA) SHARK Administration Monitoring service (wfmc Interf 4) Active BPEL Service Composition (BPEL) Software components and products Standards Based (Reference Models) Option Two: with solutions based on standards and open source Design and execution platform Enterprise Collaborative Shared Space Modeling Platform Enterprise Modelling (Mega – System Architect – Susie MO2GO ARIS METIS GRAI) POP*, PIM4SOA? Rational Rose CBP Modelling (Windchill) POP*, PIM4SOA? Execution Platform PDM system Workflow exec engine Product Data Repository PDM services (Windchill) Windchill Worklist Client Service Windchill Administration Monitoring service

21. Software components and products Standards Based (Reference Models) Option Two: with solutions coming from ATHENA Design and execution platform Enterprise Collaborative Shared Space Modeling Platform Enterprise Modelling (MO2GO/ARIS/METIS/GRAI) POP*, PIM4SOA Modeling Platform Enterprise Modelling (Mega – System Architect – Susie MO2GO ARIS METIS GRAI) POP*, PIM4SOA? Rational Rose Enterprise Maestro CBP Modelling CBP Modelling (Windchill) POP*, PIM4SOA? Jonhson Processing Chain Definition CBP Information Execution Platform Jonhson SOAP messages Monitor Execution Platform ICT Jonhson Processing Chain Execution PDM shared repositroy STEP Application Protocols Nehemiah Worklist Client Service PDM system Workflow exec engine Product Data Repository PDM services (Windchill) Windchill Worklist Client Service Nehemia/Jonhson Process exec. Engine (BPEL, Maestro...) Active BPEL Service Composition (BPEL) XPDI PDM PLM SERVICES (AP214, WSDL) Nehemiah Administration Monitoring service Windchill Administration Monitoring service

22. Pilot 2 • Participating the networked organization • Launching instance of collaboration process • External Change Management Process • Actor : Engineer of the design office • Tools : local PDM system- as workflow enactment service, connected to the Collaboration Space tool • Prerequisite : Networked Collaboration Space is set up and the EADS and Equipment suppliers have joined the network (c.f.pilot 1) • Pilot environment was provides with • Real accessible applications through web services • Real workflow models, that can be made available in the XPDL format • Real data set • Script for operational change management process instance in CPD context

23. Pilot Infrastructure Components Provided by EADS CCR 1 2 3 4 3 1 2 4 END USER INTERNAL DEVELOMENT

24. Software components and products Standards Based (Reference Models) Option One: with solutions based on standards and open source JaWE Business Process Modelling&Simulation (XPDL) PDM shared repositroy STEP Application Protocols Collaborative Shared Space SHARK Worklist Client Service (Wfmc Interf 1) SOAP SHARK Application access service WAPI agents SHARK Workflow Engine Wf-XML services (XPDL/WSDL/LDAP Wf Facilities/CORBA) XPDI PDM PLM SERVICES (AP214, WSDL) JAVA CORBA SHARK Administration Monitoring service (wfmc Interf 4) MAIL Active BPEL Service Composition (BPEL) Apache Tomcat Axis WEB Server (JSP,HTTP,SOAP) jUDDI (UDDI,SOAP) EADS Landing Gear Provider Supplier PDM Services Workflow Engine Windchill Supplier PDM Services Workflow Engine Windchill PDM System PDM System Windchill Windchill

25. Software components and products Standards Based (Reference Models) Option Two: with generic solutions from ATHENA PDM shared repositroy Collaborative Shared Space STEP Application Protocols Nehemia Worklist Client Service Apache Tomcat Axis WEB Server XPDI PDM PLM SERVICES (AP214, WSDL) Nehemia Administration Monitoring service Nehemia + Johnson Process Enactment And Service execution (BPEL) OEM One Supplier Supplier PDM Services Workflow Engine Windchill Supplier PDM Services Workflow Engine Windchill PDM System PDM System Windchill Windchill

26. Software components and products Standards Based (Reference Models) Option Two: with specific solutions of ATHENA For Modeling and execution platform Modeling Platform ATHOS, ASTAR, ARGOS Maestro CBP Modelling Collaborative Shared Space Common Services OpenLDAP (LDAP) Jonhson Processing Chain Definition SOAP Gabriel Application access jUDDI (UDDI,SOAP) Execution Platform Jonhson SOAP messages Monitor Jonhson Processing Chain Execution ARES Lindon WSDL processor PDM shared repositroy STEP Application Protocols Nehemiah Worklist Client Service Apache Tomcat Axis WEB Server (JSP,HTTP,SOAP) Nehemia/Jonhson Process exec. Engine (BPEL, Maestro...) XPDI PDM PLM SERVICES (AP214, WSDL) Nehemiah Administration Monitoring service

27. Software components and products Standards Based (Reference Models) Option One: with specific solutions out of ATHENA For Modeling and execution platform Modeling Platform EXPRESS XSLT XMI (tools from AIDIMA scenario) Maestro CBP Modelling Collaborative Shared Space Common Services OpenLDAP (LDAP) Jonhson Processing Chain Definition SOAP Gabriel Application access jUDDI (UDDI,SOAP) Execution Platform Jonhson SOAP messages Monitor Jonhson Processing Chain Execution Xerces Lindon WSDL processor PDM shared repositroy STEP Application Protocols Nehemiah Worklist Client Service Apache Tomcat Axis WEB Server (JSP,HTTP,SOAP) Nehemia/Jonhson Process exec. Engine (BPEL, Maestro...) XPDI PDM PLM SERVICES (AP214, WSDL) Nehemiah Administration Monitoring service

28. Pilot 3 : MDA approach & projection on Open Technical framework • The scenario will cover • Establishment of the Collaborative space • Definition and design • Who : Networked Organization Collaboration Space Architect and Consortium behind the network • Tools : Enterprise Modeling tools • Development • Who : ICT people • Tools : standards, software engineering tools, Commercial of the shelve software • The idea is to be able to implement some services and repository from PIM models, based on model of reference (manufacturing and ICT standards) • What is available for piloting • Definition of PLM services from OMG Mantis • A PLM services implementation: XPDI (deployed on the Aerospace pilot environment) • Service composition platform based on Workflow definition (Shark, Maestro…) • Services to expose PLM services from an existing legacy application system, based on MDA/MOF approach : axis and Windchill that is written in Java

29. PLM services specification* PIM Services Pre defined Use cases Information view PSM Universal Client Presentation Business Logic Data Web navigator Web Server DataBase Application Server Apache Jboss Hypersonic Portal Layer 1 Layer 2 Layer 4 Layer 3 * From OMG MANTIS Based on MDA Based on ISO STEP (AP214) Idea of the test case

30. Drawback slides Test Case and Business Process Standards positionning

31. Example of scenario : Virtual SpaceBird A shared CBP for Change Management • But different • Workflow engines, Workflow clients for worklist and Workflow applications clients ... within the different enterprises (for each internal actor) and within the collaborative environment, based on heterogeneous solutions • e.g. Enhydra Shark for the collaborative space • PTC Windchill for Design Office of EADS • Dassault Systèmes (DS) Enovia for Design office of Engine Alliance • SAP for Production of EADS production • BAAN for Production of Engine Alliance Where internal Change & Configuration Management processes are enacted

32. Plan of Content • Description of the Business Test Scenario • Establishing a collaboration • Change Management Process • Standards for Business Process Management • Process Models for Business Test Case • The different provided packages

33. Establishing a collaborationPre-existing Processes and Workflows and possible sequencing 3 possible different Business Processes and workflows development sequences when considering collaboration • BP within Enterprise 1 • BP within Enterprise 2 • Collaborative BP (CBP) CBP can be built • from BP1 or BP2 • from Standard CBP BP1 and BP2 can pre-exist or be derived from CBP reference model. Cooperation can consequently be established through • top down distribution • bottom up composition

34. Establishing a collaborationDistribution of one Collaborative Process Instanciation at Runtime 2(ICT Independant)

35. PTC Windchill : Design Office SAP : Production DS Enovia : Design Office Enhydra Shark BAAN : Production Establishing a collaborationDistribution of one Collaborative Process Instanciation at Runtime 2Workflow enactment is ICT legacy solutions dependant

36. Establishing a collaborationHierachy of Organisational Boundaries, with escalation process Virtual SpaceBird Program Escalation EADS Others... LG EADS Design Office EADS Production Escalation LG Design Office LG Production

37. Change Management Process Top Down Distribution • Based on Reference Change Process Model (based on CMII) • Shared by each Boundary as shared public external view • Mapping to be down within each boundary Modelling Tool for Process • User Friendly, simple for Business Process Modelling experts and Workflow service users (not IT people) • Based on a workflow standard to be enact by different workflow engines • Technology framework independent • Supported by Vendors • Existing mature enough and simple tools for demonstration and prototyping

38. Wfmc StandardsSome Interoperability features already available. • XPDL • Neutral XML format for exchange of process models between modelling tools and workflow engines (Interface type 1) • On going Alignement with BPMN • Should be one of the schema an Enterprise Modelling tool can import or export for local boundaries (Organisational, Development, Execution) • Supported by numerous modelling products (list available on Wfmc WEB site) and several workflow engines • Implementations of reference that are Open Source • JaWE • Shark, wfOpen

39. Wfmc StandardsSome Interoperability features already availables • Usage scenario • Modeling with JaWE • Import of XPDL file containing the process on Shark Process Repository • Loading on Shark • Parameterisation (Users-Participants and Applications-Agents mappings) • Process Instance creation

40. Wfmc StandardsSome Interoperability features already availables • WAPI Usage scenario • Modeling with JaWE • Imp • Parameterisation (Users-Participants and Applications-Agents mappings) • Process Instance creation • Execution of work- item received in Users Worklists and indication of completion of the work (with optionnally information providing) • Monitoring and Administration of Process Instances

41. Wfmc StandardsSome Interoperability features already availables • Usage scenario • Swithching of the Administration Client • Launching of 2 Worklist Handler client and login for two different concerned person • Based on CORBA, on a remote machine • Local Client made available through WEB Server • Execution of work- item received in Users Worklists and indication of completion of the work (with optionnally information providing) • Launching of a remote Administration Client • Execution of applications using different kind of agents • Executable • Script • Corba • Web Service

42. Wfmc StandardsSome Interoperability features already availables • WAPI • Workflow Application Programming Interface • Generic description plus technology specific implementation based on • CORBA (in accordance with OMG Worflow Management Facilities) • Interface 2 (worklist-engine) • Interface 3 (application-engine) - WAPI Agents • Interface 5 (administration-engine) • Implementation of reference that are Open Source • Shark – propose WAPI agents for WEB services

43. Wfmc StandardsSome Interoperability features already availables • wf-XML • XML messaging for Worflow • Extends ASAP from OAGIS • Generic description plus technology specific implementation based on • WEB services technologies • Interface 1 (modeler-engine) • Interface 4 (engine-engine) – suitable for federation of process fragments • Implementation of reference that are Open Source • Shark – propose WAPI agents for WEB services

44. Wfmc StandardsSome Interoperability features already availables • Usage scenario • A server is running with a CBP • To launch Enterprise Modelling tool (One partner withModelling tool supporting wf-XML) • To connect through wf-XML • http://localhost:8080/axis/services/wfxmlRegistryBinding?wsdl • To import and visualize the CBP • To create the external view of the partner for the CBP • To upload on Worflow engine

45. 2- Launch JaWE and wf-XML connection 3- Registry Binding and OK Process is imported 1- Shark Axis Service running

46. Process Models for Business Test CaseThe different provided packages and top down approach ConfigurationManagement Process and Change Management process of reference => Top Down approach Virtual SpaceBird Space Bird Package Virtual SpaceBird LG Package Virtual SpaceBird EADS Package Virtual SpaceBird EADS Design Office Package Virtual SpaceBird EADS Production Package Virtual SpaceBird LG Design Office Package Virtual SpaceBird LG Production Package

47. Process Models for Business Test CaseThe different provided processes, for different organisational boundaries Virtual SpaceBird Space Bird Package Each organization and sub-organization have its own representation of the process, more or less detailed, according their viewpoint, with private and public informations Virtual SpaceBird EADS Package Virtual SpaceBird EA Package Virtual SpaceBird EADS Design Office Package Virtual SpaceBird EADS Production Package Virtual SpaceBird EA Design Office Package Virtual SpaceBird EA Production Package

48. Process Models for Business Test Case Several models of the same Process for the different organisational boundaries CBP Model within Cooperation Space CBP within EADS CBP within DO, EADS Internal

49. Process Models for Business Test CaseEnactment of Business Models : supported by Shark or other XPDL compliant engines, or by other engines after translation of XPDL

50. Wf Engine 1 Wf Engine 2 Wf Engine 3 Process Models for Business Test CaseWhich CBP process model to be enacted? Where? Interconnections?Need of interfaces of type 4 Interface type 4 CBP CBP proxy EADS External Proxy EADS External Interface Type 4 EADS DO external