210 likes | 222 Views
This review discusses activities performed for the implementation, evaluation, and bug reporting of the ATHENA Collaborative Process. It also covers the refinement and validation of the NCPD infrastructure, identification and evaluation of existing components, and validation of framework principles.
E N D
B5 EADS piloting Nicolas Figay, EADS Flora Robin, EADS ATHENA Intermediate Review 27-29 March 2007 Funchal, Portugal
Activities performed since last review Inception, Evaluation, Test, Bug report for execution and interconnection of various solutions of ATHENA Collaborative Process => the last version of Maestro/Nehemiah and XPDI PLM server of reference Definition and partial running of the integrative pilot Implementation of the Networked Collaborative Product Development Process Set up the Networked Collaborative Product Infrastructure and service Join the networked organization Participate the networked organization Leave the networked organization Definition of NCPD infrastructure refined and validated Validation of concrete components Architecture refined Identification and evaluation of existing components to use From ATHENA From the outside
Activities performed since last review • Special focus on validation of framework principles and integration of the legacy • Evaluation of concrete solutions to fulfill ATHENA vision for Aerospace pilot • Analysis of results and feedback for A4 (profiles) • Feedback for B6 (Tutorial – PLM standards used on the scenarios demonstrated and explained) • Feedback to B4 providing requirements fulfillment status • ATHENA Aerospace WEB Site • Exploitation plan implementation started on top of B5 pilot
Networked Collaborative Product DevelopmentReminder of the industrial context • Interoperability • Numerous stakeholders • Numerous Actors • A Network of Enterprises • Network Collaborative Product Development Hub • Organization • Collaboration infrastructure • Services • Ontology • Processes • Basis: ATHENA approach • Enterprise • Knowledge • ICT • Ontology
Networked Collaborative Product DevelopmentReminder of the industrial context – organisational layer
Networked Collaborative Product DevelopmentReminder of the industrial context – individual layer Shared NCPDS
Cross Organizational Change Management ProcessDesign Time Business Demonstration [A2/A5/A4] Maestro, Nehemiah, Johnson, Gabriel Jane Doe - LGP Dominique Dupond - EADS NCPD 2-LGP 1-Airbus Workflow engine For Local private Process and CBP Workflow engine For Local private Process and CBP Message Monitoring tool Message Monitoring tool 3- Airbus 4- LGP
Cross Organizational Change Management ProcessRun Time -EnactmentOrganization integration [A4/A2/A5] Nemehiah, Gabriel and Johnson / OpenLDAP, Liferay and Jawe/Shark Mapping Roles And relation with legacy Enterprise Repository Mapping Roles And relation with legacy Enterprise Repository Collaboration Portal Enterprise Repository- LDAP Mapping Messages Relevant Workflow Data Documents EADS Roles NCPD Roles LGP Roles CBP- Nehemiah Mapping Endpoints And relation with legacy Enterprise Repository (UDDI?) NCPD Modeled Process NCPD Enacted Process New Requirements For CBP Endpoint Mapping- Johnson
Cross Organizational Change Management ProcessAlternative solution and legacy integration [A4/A2/A5] Nemehiah, Gabriel, ActiveBPEL, XPDI Server of reference Business Collaboration through External Change Management Process Nehemiah/Gabriel Private Business Change Management Process Active BPEL Technical Process XPDI Server of Reference • Published PLM Services (Standardized) • OMG Mantis PLM Services V1.0 NCPD PLM Services for shared repository
Collaborative Process: Change managementFeedback Runtime usage achieve but numerous problem of integration with external components: • Administration of the web services • Invocation of pre-existing PLM WEB services (no support of array, abstract types, complex queries, SOAP Header) Business Demonstration (movie): • Real Interest from the Manufacturing community • Implementation within real software product and commodities? Some integration and design issues • Business: Business Collaboration Processes against Technical Operational Processes • Business: Mapping of Roles, Document Flow, Relevant Data • Business: links to Enterprise repositories for person and services Maturity Issues • WEB services technologies stack not yet supporting complex collaboration for NCPD • XPDI Server of Reference • Methodology and Strategy for SOA (Business versus ICT) • Big Issues for Architects and Integrators (not a seamless collaboration for architects, ,integrators and administrators!)
Aerospace Pilot: Networked Collaborative Product Development Model generated Service Oriented NCPD Platform including cross Organizational Workflow based on standards • Runtime usage achieve for several ATHENA and non ATHENA components • Demonstrators for Business Validation of CBP • Validation of AIF approach and Model Generated Space on top of Service Oriented Execution Platform • but numerous problem of integration and administration of components: • Administration of the web services • Invocation of pre-existing PLM WEB services Some integration and design open issues for NCPD • Business: Business Collaboration Processes against Technical Operational Processes • Business: Mapping of Roles, Document Flow, Relevant Data • Business: links to Enterprise repositories for person and services • Business: availability of robust component commodities as part of enabling infrastructure Maturity Issues • WEB services and MDA technologies stacks not yet supporting complex collaboration for NCPD • XPDI Server of Reference and PLM services specification • Methodology and Strategy for SOA (Business versus ICT) • Big Issues for Architects and Integrators (not a seamless collaboration for architects, ,integrators and administrators!)
Model Driven Engineering of the NCPDIBusiness Models=> Application Model=>Execution platformSTEP Mapper, AndroMDA, JBOSS, Web servers 1: STEP Mapper Express to PIM Profile for WEB Enterprise Application 2: AndroMDA Generation of code for the targeted execution platform 3: Generated Product Data repository STRUTS+WEB Server+ Application Server + Database All the CRUD operations generated 100%
Model Driven Engineering of the NCPDIBusiness Models=> Application Model=>Execution platformUML cleaning scripts, AndroMDA, JBOSS, Web servers (Information Model with UML Technologies) Cleaning Perl Script UML Modeler Fully compliant with UML 1.4 AndroMDA PLM Service Normative UML Information Model in XMI UML 1.3 SOA EXECUTION PLATFORM based on Open Standards for Application Server and Portal
Model Driven Engineering of the NCPDIBusiness Models=> Application Model=>Execution platform UML cleaning scripts, AndroMDA, JBOSS, Web servers (Information Model with UML Technologies) • UML Issues • For transformation from XMI 1.1 and UML 1.3 to XMI 1.2 and UML 1.4 (add some required fields • To automatically tag the entities as ‘Entity’ and ‘Manageable’ • Technologies assessment • UML technologies not mature enough, no interoperability with XMI! • Impedance mismatch during transformation between the different languages • EXPRESS more appropriate than UML for specifying standardized information models and to be computed for application generation • PLM Standards Assessment • OMG Mantis PLM 1.0 services not yet mature • STEP AP associated with STEP Technologies appears as the most robust way to deal with Model Transformation based on robust standards supporting industrial needs for PLM • Numbers • Number of classes: 187 • Number of packages: 14 • Number of interfaces: 33 • Number of attributes: 184 • Number of associations: 438 • Number of Aggregation of type "composite": 252 • Number of clientDependency attribute: 77 • Number of ‘Abstraction’: 334
Federated Knowledge ModelFor Governance and Dynamic Requirement Engineering DRD KB (in OWL) File Resource Publication Service Publication Collaboration Portal KB Editor (XML browser) (pOWL) KB Editor KB Querying (SparQL) KB Visualization (Jambalaya GML) KB Querying (SparQL- Virtuoso)
Model Driven Engineering of the NCPDI Feedback To be extended to integrate PIM4SOA/CBP profile – horizontal extension To integrate complementary transformations from A6 • Enterprise to Application (POP* to PIM4SOA, POP* to CBP) • Application to Execution level • STEP 2XSD and STEP2UML from UNINOVA Numerous integration issues • Interchange format and profiles: versions, functional coverage, conformance and certification of tools • Generic solution architecture and identification of concrete components in order to obtain a full configured solution • Standards overlapping and lack of interoperability • Existence of a formal architecture From Business point of view, it really respond to an important need to disconnect business viewpoint from technical viewpoint, and allowing to be software solutions independent. Should be support and drive by a strong community
Liferay Struts+Tomcat+Apache JBoss BPEL Engine ActiveBPEL Shark Workflow Enactment System ATHENA A2 CBP Engine MySQL ATHENA A3 Semantic Mediation ATHENA A5 Service HUB NCPD Execution Platform Architecture