© 2005-2006 the athena consortium. ci2: the athena interoperability framework module 3:...

© 2005-2006 The ATHENA Consortium.

CI2: The ATHENA Interoperability

Framework

Module 3: Collaborative Product Development Scenario

Aeronautics and Aerospace Sector

2© 2005-2006 The ATHENA Consortium.

• Scenario Description• Interoperability Issues• Architecture of Solutions

Collaborative Product Development

This unit is structured as follows:


Scenario Description

• Business context

• Involved actors

• Process

Engineers Person responsiblefor data package

Operational dataexchange team

2

Operational Exchange

Team member

EAIPDF

Manuf.

PDFAirbu

s


Team member

11

1

12

13

6

7

3

10

5

8

4

9


Aeronautics and Aerospace Sector

• The aeronautics sector is a vitalasset for Europe’s economic and social prosperity.

• Providesemploymentfor 3.1 millionpeople.


EADS Group

This scenario is based on the experience of

EADS Group business units, including:

•Airbus•EADS Space Transportation•ASTRIUM and •Eurocopter


Collaborative Product Development Scenario

L.T.Archiving

InternationalProduct Data

Standards

M

SE

OEM PRODUCT

DATA

Manufacturing

SupportEngineering

EquipmentsSupplier

EngineSupplier

EngineSupplier

GlobalSupplier

EngineSupplier

EquipmentsSupplier

GlobalSupplier

EngineSuppliers

EquipmentsSupplier

GlobalSupplier

Risk-Sharing Partner

ServiceSuppliers

Level 1 Level 2 Level 3

Supplier

Supplier

Supplier

Supplier

Military Agencies

Civil Airlines

Mil. Agency Manuf.

Supplier

Mil. Agency Manuf.

Supplier

Airlines Manuf.

Supplier

Airlines Manuf.

Supplier

Airlines Manuf.

Supplier

Configured & Controlled Product Data for:

> Design

> Simulation

> Manufacturing &

> Support


Product Data Management (PDM)

Product Data Management (PDM) are software applications that are enhancing Product Data Sharing between all the actors involved in the design, manufacturing and support process.

Early involvementof down streamactivities using

the virtual aircraftConcept

Definition Production

Support

CONCEPT DEFINITION DEVELOPMENT SERIESFEASABILITY


Organisations

Within this scenario we consider the PDM Coupling

process of two organisations:

•The industrial integrator (AIRBUS)•Manufacturer


Actors

We will consider three different participants:

Operational dataexchange team

Person responsiblefor data package

Engineers


“As-is” and “To-be” Process

• “As-is” process reflects the current situation with its interoperability problems.

• “To-be” process reflects the envisaged ideal situation in which Interoperability problems don’t exist.


PDM Coupling: “As-is” Process

PDMAIRBUS

PDMManufacturer

1

3

5 6

7

10

Engineer

Data Packageresponsible


Team member


Team member

2

8

114

9


PDM Coupling: “To-be” Process

PDMAIRBUS

PDMManufacturer

1

2

3

4

5 6

7

8

9

10

Engineer

Data Packageresponsible

Systems are integrated/coupledEnterprise Application Integration (EAI)


Team member

12


Team member

13

11

EAI



1

2

6

7

“To-be” ProcessEnd-user point of view

11



PDMAIRBUS

PDMManufacturer

3

4

5

8

9

10

“To-be” Process Operational Exchange Team Point of View

12


Team member

13


Team member

EAI



PDMAIRBUS

PDMManufacturer

3

4

5

8

9

10

“To-be” Process IT Department Point of View

14

ITDepartment

EAI


Interoperability Issues

• Interoperability issues are problems concerning interoperability extracted from analysis of business scenarios.


Business Category Interoperability Issues

• Neutral standards to prepare negotiation between the different actors

• Integration of heterogeneoustools (cost control, systemengineering, etc.)

• Linking programme,product and enterpriseviewpoints


Knowledge Category Interoperability Issues

• Knowledge capture, assimilation and management• Product-related knowledge sharing between product life

cycle phases• Integration of the relevant

industrial sector, ICT,and enterprise-modellingmodels

• Establishment ofknowledge managementstandards and best practices


Software Category Interoperability Issues (1)

• Independence between business logic and technical solutions

• Easy customisation of the software product and technicalinterfaces

• Auto-descriptiveapplications


Software Category Interoperability Issues (2)

• Internal information model of software products based on standards

• Application interfaces and service description according tostandards

• Coherent supportof the maintechnical softwareplatform


Architecture of Solutions

Data

Enterprise

Processes

Services

Data

CM II

Executable Cooperative Configuration Management Processes

CBPS

Wfmc

Published PLM Services

OASIS PLCS

OMG Mantis

Information Repositories STEP

Enterprise

Processes

Services

Data


This course has been developed under the funding of the EC with the support of the EC ATHENA-IP Project.

Disclaimer and Copyright Notice: Permission is granted without fee for personal or educational (non-profit) use, previous notification is needed. For notification purposes, please, address to the ATHENA Training Programme Chair at [email protected]. In other cases please, contact at the same e_mail address for use conditions. Some of the figures presented in this course are freely inspired by others reported in referenced works/sources. For such figures copyright and all rights therein are maintained by the original authors or by other copyright holders. It is understood that all persons copying these figures will adhere to the terms and constraints invoked by each copyright holder.

© 2005-2006 the athena consortium. ci2: the athena interoperability framework module 3:...

Documents

athena consortium

product data sharing

controlled product data

supplier airlines

pdm coupling process

eurocopter slide

data package engineers

aerospace sector slide