1 / 27

ATHENA M30 Intermediate Audit 4.-5. October 2006 Brussels, Belgium

ATHENA M30 Intermediate Audit 4.-5. October 2006 Brussels, Belgium. 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:

kinsey
Télécharger la présentation

ATHENA M30 Intermediate Audit 4.-5. October 2006 Brussels, Belgium

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ATHENA M30 Intermediate Audit 4.-5. October 2006 Brussels, Belgium

  2. 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

  3. Tasks management Services management Process enactement Process modeling PLM server of reference as shared repository EADS VP - LGP VP CBP EADS and LGP service interfaces Nehemiah Maestro Nehemiah Johnson Maestro Gabriel Johnson Gabriel Shared PLM Repository Local PDM Local PDM Tools and services used LGP EADS NCPDO EADS PP EADS VP LGP PP LGP VP PP: Private Process VP: View Process CBP: Cross Business Process NCPDO: Network Collaboration Product Development Organisation

  4. Modeling steps (1) • Model the private process in Maestro (PP)

  5. Modeling steps (2) • Model the private process in Maestro (PP) • Create the public view of the process (VP)

  6. 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

  7. 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

  8. 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

  9. 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)

  10. 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

  11. Questions and demonstration

  12. Drawback slides

  13. Collaborative Process: Change managementDesign Time Demonstration: Maestro, Nehemiah, Gabriel, Jonhson EADS LGP

  14. Private process modelisation in Maestro (LGP)

  15. Modeling steps

  16. Partners definition in Nehemiah from Maestro

  17. Interconnection between Gabriel and Maestro through parametrisation

  18. 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

  19. 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

  20. Endpoints creation in Johnson

  21. Interface tasks definition in Gabriel (LGP)

  22. 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

  23. 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

  24. Service assignement to a receiver in Maestro

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

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

More Related