1

4th of October, 2006

© ATHENA Consortium 2006

B5 EADS CCR pilotingNicolas Figay, EADSFlora Robin, EADS

ATHENA Intermediate Review04-05 October 2006Brussels, Belgium

2

4th of october, 2006

© ATHENA Consortium 2006

Activities performed since last reviewInception, Evaluation, Test, Bug report for execution and interconnection of various solutions

of ATHENA Semantic reconciliation pilot => A3 tools Collaborative Process => the last versions of Maestro/Nehemiah and XPDI PLM server of reference

Definition and partial running of the integrative pilotImplementation 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 Generic components Architecture Identification and evaluation of existing components to use

From ATHENA From the outside

Identification of components to develop Development of components

Identification of important results and gaps to fulfill ATHENA vision for Aerospace pilot

3

4th of october, 2006

© ATHENA Consortium 2006

Networked Collaborative Product DevelopmentReminder of the industrial context

• Interoperability– Numerous stakeholders– Numerous Actors

• A Network of Enterprises

• Network Collaborative Product Development Hub– Organisation– Collaboration infrastructure

• Services• Ontology• Process

• Basis: ATHENA approach– Enterprise– Knowledge– ICT– Ontology

4

4th of october, 2006

© ATHENA Consortium 2006

Networked Collaborative Product DevelopmentReminder of the industrial context – organisational layer

SupplierLev. 2

AirlinesManuf.

Supplier

CivilAirlines

AirlinesManuf.

Supplier

Mil. agencyManuf.

Supplier

SupplierLev. 1

Engine Supplier

Lev. 3

EquipmentsSupplier

Lev. 3

Global Supplier

Lev. 3

Mil. agencyManuf.

Supplier

SupplierLev. 2

E

M

S

AirlinesManuf.

Supplier L2Engine Supplier

Lev. 3

Configured & Controlled Product Data for:- Design, - Simulation, - Manufacturing,- & Support

Military Agencies

Engine Suppliers

Global Supplier

Risk-SharingPartner

Engine Supplier

Lev. 2

EquipmentsSupplier

Lev. 2

Global Supplier

Lev. 2

EquipmentSupplier L.1 Supplier

Lev. 1

L.-T.Archiving

International Product Data

Standards

ServiceSuppliers

OEM PRODUCT

DATA

E

M

SEngineering

Manufacturing

SupportSupplier

Lev. 2

AirlinesManuf.

Supplier

CivilAirlines

AirlinesManuf.

Supplier

Mil. agencyManuf.

Supplier

SupplierLev. 1

Engine Supplier

Lev. 3

EquipmentsSupplier

Lev. 3

Global Supplier

Lev. 3

Mil. agencyManuf.

Supplier

SupplierLev. 2

E

M

S

AirlinesManuf.

Supplier L2Engine Supplier

Lev. 3

Configured & Controlled Product Data for:- Design, - Simulation, - Manufacturing,- & Support

Military Agencies

Engine Suppliers

Global Supplier

Risk-SharingPartner

Engine Supplier

Lev. 2

EquipmentsSupplier

Lev. 2

Global Supplier

Lev. 2

EquipmentSupplier L.1 Supplier

Lev. 1

L.-T.Archiving

International Product Data

Standards

ServiceSuppliers

OEM PRODUCT

DATA

E

M

SEngineering

Manufacturing

Support

FEASABILITY CONCEPT DEFINITION DEVELOPMENT SERIESSERIES

Early involvement

of down stream

activities using the

virtual aircraft

Support

ProductionDefinition

Concept

FEASABILITY CONCEPT DEFINITION DEVELOPMENT SERIESSERIESFEASABILITY CONCEPT DEFINITION DEVELOPMENT SERIESSERIES

Early involvement

of down stream

activities using the

virtual aircraft

Early involvement

of down stream

activities using the

virtual aircraft

Early involvement

of down stream

activities using the

virtual aircraft

Support

Production

Support

ProductionDefinition

Concept

Definition

Concept

5

4th of october, 2006

© ATHENA Consortium 2006

Networked Collaborative Product DevelopmentReminder of the industrial context – individual layer

Dominique Dupont

Drawing

CAD SoftwareApplication

On you Unix Station

Drawing

CAD SoftwareApplication

On you Unix Station

SharedProduct and documentsStructure

Configured Product Data repository(Vault)

ChangeManagement

Process

Jane Doe

Shared services for Aerospace Network modeling and governanceShared services for Business Process interconnection

Shared services for integration and transformation/ Shared repositories

SharedNCPDS

6

4th of october, 2006

© ATHENA Consortium 2006

Definition of NCPD infrastructure

7

4th of october, 2006

© ATHENA Consortium 2006

Collaborative Process: Change managementDesign Time Demonstration [A2/A5/A4]: Maestro, Nehemiah, Jonhson, Gabriel

LGPEADS

8

4th of october, 2006

© ATHENA Consortium 2006

Collaborative Process: Change managementFeedback

Still some bugs to fix (ongoing) to be able to address runtime (target for last review)

Some integration and design issuesNeed for CBP documented XML format or UML profile ( deriving from existing standards)What about legacy engines?Need for facilities to defined messages/services between Receiving and Sending points, and to perform mapping with relevant workflow dataWhat about calling services other than WEB services?Easier integration between Maestro/Nehemiah/Gabriel/Johnson

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 not addressed by current tools and standards.

9

4th of october, 2006

© ATHENA Consortium 2006

Model Driven Engineering of the NCPDI Business Models=> Application Model=>Execution platformSTEP Mapper, AndroMDA, JBOSS, Web servers

1: STEP MapperExpress to PIM Profile for WEB Enterprise Application

2: AndroMDAGeneration of code for the targeted execution platform

3: Generated Product Data repositorySTRUTS+WEB Server+ Application Server + DatabaseAll the CRUD operations generated 100%

10

4th of october, 2006

© ATHENA Consortium 2006

Model Driven Engineering of the NCPDI Business Models=> Application Model=>Execution platformSTEP Mapper, AndroMDA, JBOSS, Web servers

STEP MapperSTEP Mapper ArgoUMLArgoUML

STEP APExpress

STEP APUML

(XMI1.3)

ENTITY interfaced_itemABSTRACT SUPERTYPE OF

(ONEOF (explicit_item_id, implicit_item_id));foreign_schema_id :

express_id;END_ENTITY;

Identification ofExpress

Construct

Creationof theConstructwithArgoUML0.14

ResultSavedin XML 1.3

<Foundation.Core.Classxmi.id="xmi.92" xmi.uuid="127-0-0-1-ebcdbb:1014ff15aa6:-7fdf">

<Foundation.Core.ModelElement.name>interfaced_item</Foundation.Core.ModelElement.name>

<Foundation.Core.ModelElement.visibilityxmi.value="public"/><Foundation.Core.ModelElement.isSpecificationxmi.value="false"/><Foundation.Core.GeneralizableElement.isRootxmi.value="false"/><Foundation.Core.GeneralizableElement.isLeafxmi.value="false"/><Foundation.Core.GeneralizableElement.isAbstractxmi.value="false"/><Foundation.Core.Class.isActivexmi.value="false"/><Foundation.Core.ModelElement.namespace><Foundation.Core.Namespacexmi.idref="xmi.20"/>

</Foundation.Core.ModelElement.namespace><Foundation.Core.GeneralizableElement.specialization><Foundation.Core.Generalizationxmi.idref="xmi.93"/><Foundation.Core.Generalizationxmi.idref="xmi.94"/><Foundation.Core.Generalizationxmi.idref="xmi.95"/><Foundation.Core.Generalizationxmi.idref="xmi.96"/>

</Foundation.Core.GeneralizableElement.specialization>EstablishmentOf themapping

TransformationProgrammation

1 2 3

45

STEP MapperSTEP Mapper ArgoUMLArgoUML

STEP APExpress

STEP APUML

(XMI1.3)

ENTITY interfaced_itemABSTRACT SUPERTYPE OF

(ONEOF (explicit_item_id, implicit_item_id));foreign_schema_id :

express_id;END_ENTITY;

Identification ofExpress

Construct

Creationof theConstructwithArgoUML0.14

ResultSavedin XML 1.3

<Foundation.Core.Classxmi.id="xmi.92" xmi.uuid="127-0-0-1-ebcdbb:1014ff15aa6:-7fdf">

<Foundation.Core.ModelElement.name>interfaced_item</Foundation.Core.ModelElement.name>

<Foundation.Core.ModelElement.visibilityxmi.value="public"/><Foundation.Core.ModelElement.isSpecificationxmi.value="false"/><Foundation.Core.GeneralizableElement.isRootxmi.value="false"/><Foundation.Core.GeneralizableElement.isLeafxmi.value="false"/><Foundation.Core.GeneralizableElement.isAbstractxmi.value="false"/><Foundation.Core.Class.isActivexmi.value="false"/><Foundation.Core.ModelElement.namespace><Foundation.Core.Namespacexmi.idref="xmi.20"/>

</Foundation.Core.ModelElement.namespace><Foundation.Core.GeneralizableElement.specialization><Foundation.Core.Generalizationxmi.idref="xmi.93"/><Foundation.Core.Generalizationxmi.idref="xmi.94"/><Foundation.Core.Generalizationxmi.idref="xmi.95"/><Foundation.Core.Generalizationxmi.idref="xmi.96"/>

</Foundation.Core.GeneralizableElement.specialization>EstablishmentOf themapping

TransformationProgrammation

1 2 3

45

11

4th of october, 2006

© ATHENA Consortium 2006

Model Driven Engineering of the NCPDI Feedback

To be extended to integrate PIM4SOA/CBP profile – horizontal extension

To integrate complementary transformations from A6Enterprise to Application (POP* to PIM4SOA, POP* to CBP)Application to Execution levelSTEP 2XSD and STEP2UML from UNINOVA

Numerous integration issuesInterchange format and profiles: versions, functional coverage, conformance and certification of toolsGeneric solution architecture and identification of concrete components in order to obtain a full configured solution Standards overlapping and lack of interoperabilityExistence 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