1 © athena consortium 2006 athena m30 intermediate audit 4.-5. october 2006 brussels, belgium

1© ATHENA Consortium 2006

ATHENA M30 Intermediate Audit4.-5. October 2006Brussels, Belgium

2

ATHENA M30 Intermediate Audit, September 2006, Brussels

© ATHENA Consortium 2006

Pilot introduction

● Participating in the networked organisation through a collaborative process: launching an external change request

● Actors:● EADS (OEM) - Aerospace● Landing Gear Provider (supplier)

● Scenario:● An engineer at EADS discovers that the braking system of the

spacecraft has to be changed● This change impacts the wheels provided by LGP

4



Tools and services used

EADS NCPDO LGP

NCPDO: Network Collaboration Product Development Organisation

Shared PLM Repository

Maestro

Nehemiah Gabriel

Johnson

Local PDM

Maestro

Nehemiah Gabriel

Johnson

Local PDM

EADS PP

EADS VP

LGP PP

LGP VPEADS VP - LGP VP

CBP

EADS and LGP service

interfaces

Process modeling

Process enactement

Services management

Tasks management

PLM server of reference as shared repository

PP: Private Process

VP: View Process

CBP: Cross Business Process

5



Modeling steps (1)

● Model the private process in Maestro (PP)

6



Modeling steps (2)

● Model the private process in Maestro (PP)

● Create the public view of the process (VP)

7



Modeling steps (3)

● Model the private process in Maestro (PP)● Create the public view of the process (VP)● Share this public view with our partner● Create together the Cross Business Process

8



Modeling steps (4)

● Model the private process in Maestro (PP)● Create the public view of your process (VP)● Share this public view with our partner● Create together the Cross Business Process● Generate the final public views

9



Service definition

● Call an external web services from Private Processes● Message exchange between the processes (collaboration)

● Done using Johnson and Gabriel

● Mapping is done in Maestro: Workflow Relevant Data to services

10



Next steps

● Run it in a distributed environment (each partner is running Maestro + Nehemiah + Gabriel + Johnson) with partners exchanging messages between senders and receivers nodes

currently not possible due to a bug in Gabriel

● Call web services to store and upload data in the PLM repository

currently not possible due to limitation of accepted format of exchanged messages (XML arrays of elements are not supported)

11



Feedback

• Some integration and design issues:• Interconnection with legacy engines?• Call to other than web services (legacy integration, API calls)• Better and easier integration of the tools• Ability to go from a shared CBP on the NCPPD to PP

• From Business point of view, it really responds to an important need to hide private processes and to interconnect several enactment services with distributed activities

• From innovative point of view, it is really something new which is not addressed by current tools and standards


Questions and demonstration


Drawback slides

14



Collaborative Process: Change managementDesign Time Demonstration: Maestro, Nehemiah, Gabriel, Jonhson

LGPEADS

15



Private process modelisation in Maestro (LGP)

16



Modeling steps

17



Partners definition in Nehemiah from Maestro

18



Interconnection between Gabriel and Maestro through parametrisation

19



Service interfaces definition for collaboration

● WSDL files for the collaboration:● Definition of operation for receivers and format of message● Workflow information

● Registration in Johnson● Your interface should be configured as server and use Gabriel’s

notification● Your partner’s interface should be configured as a client

● Creation of tasks in Gabriel (visible by Maestro):● For senders● For receivers

20



Services and schema definition

Defined by creating WSDL and schemas by hand.WSDL is mapped with Workflow relevant data in Maestro=> Long task requiring expertise in WSDL and XML schemas

21



Endpoints creation in Johnson

22



Interface tasks definition in Gabriel (LGP)

23



Modeling steps - Mapping

● Define the Workflow Relevant Data (XML file):● Choices conditions● Content of messages exchanged between the instances of

processes (senders and receivers nodes)● Workflow information (CoalitionWorkflowInstanceId and

CoalitionWorkflowModelId)

● In Maestro on the CBP Model:● Assign Service interface to senders and receivers● Map the WRD to the Service Interfaces

24



Web service call

● Should be defined during the modeling of Private Process

● Creation of the corresponding endpoints in Johnson● Creation of private service tasks profiles in Gabriel● Mapping between WRD and content of SOAP message in

Maestro

25



Service assignement to a receiver in Maestro

26



Map service to schema (1)(workflow relevant data to message exchanged and defined in wsdl)

27



Map service to schema (2)(workflow relevant data to message exchanged and defined in wsdl)

1 © athena consortium 2006 athena m30 intermediate audit 4.-5. october 2006 brussels, belgium

Documents