Design in Context: Instruction Issue

Instruction
AP5243
Issue: B

AIRBUS S.A.S. 2010. ALL RIGHTS RESERVED. CONFIDENTIAL AND PROPRIETARY DOCUMENT.

Q10_Procedure & Instruction_FM0400690_v3.2 Printed Copies are not controlled. Confirm this is the latest issue available through the Portal. Page 1 of 11

Design in Context
<SUMMARY_BEGIN>SUMMARY :
PURPOSE:
The purpose of this Instruction is to provide the detailed steps for Designing in Context, which shall
contribute to delivering a robust design that is fit for purpose.

SCOPE:
This Instruction is applicable to all existing and future programmes using the Design in Context.
This Instruction concerns Airbus, RSP and Suppliers.

It concerns Designers dealing with CAD design.

<SUMMARY_END>
Owner's Approval:

Name: MARTIN Nathalie
Function: Design Policy & Development - EDSBIM

Authorization:

Name: DUPONT Michel
Function: Head of Digit A/C Integration - EDSBI

EIectronicaIIy vaIidated - ReIeased on 21 May 2010

Design in Context
AP5243
Issue: B


Printed Copies are not controlled. Confirm this is the latest issue available through the Portal.
Page 2 of 11
TABLE OF CONTENTS
1 About this Document ........................................................................................................... 3
1.1 Background ......................................................................................................................... 3
1.2 Detailed Purpose ................................................................................................................. 3
1.3 Detailed Scope .................................................................................................................... 3
2 General Description of the Process ..................................................................................... 4
3 Flow Chart ........................................................................................................................... 5
3.1 Specific Process for RSP and Suppliers ............................................................................. 5
3.2 General Process .................................................................................................................. 6
4 Detailed Activities ................................................................................................................ 7
5 Actors .................................................................................................................................. 9
6 Reference Documents ....................................................................................................... 10
7 Glossary ............................................................................................................................ 10
Contributors ..................................................................................................................................... 11
Record of Revisions ........................................................................................................................ 11


Design in Context
AP5243
Issue: B


Page 3 of 11
1 About this Document
1.1 Background
This Instruction describes the process for Designing Assemblies and Parts in Context (Design-
in-Context). It is an enabler of the Design Structures & Systems Installation process (A2240) in
all phases of Design.
This Instruction invokes a number of AMs and APs that are referred to throughout the text.
1.2 Detailed Purpose
The purpose of this Instruction is to ensure the DMU is used in the best manner to achieve a
robust 3D Design appropriate to the aircraft Configuration.
It provides the Designers with the definition of the Design in Context, the steps and activities to
be performed in order to design or modify the design of a component in a configured and up-
to-date context.
1.3 Detailed Scope
Design in context is an activity performed throughout the lifecycle of the aircraft.
This process is applicable to all Designers e.g. those providing:
the definition dossier for primary and secondary structure, Mechanical and Electrical
Systems Installation, Cabin & Cargo Installation and Configured Product Structure to
their customers (Manufacturing, Program Management, Customer Services...),
the definition of design principles, System Installation Requirements, etc.
This process is also applicable to suppliers:
design & build Risk-Sharing-Partners (RSP): suppliers developing and
manufacturing Aircraft components on behalf of Airbus (Risk-Sharing Partners
contractually share development risks with Airbus),
(when relevant) design & build systems & equipment suppliers: Suppliers
developing and manufacturing System's Aircraft components including Equipment,
design only suppliers: suppliers, designing smaller airframe components on behalf
of Airbus, but not manufacturing them,
Jigs & Tools specific suppliers: suppliers designing or/and manufacturing Jigs and
Tools for manufacturing the Aircraft.


Design in Context
AP5243
Issue: B


Page 4 of 11
2 General Description of the Process
Design in context is a 3D discipline in Concurrent Engineering, which is key for
designing a 3D model in the installation/assembly environment. It is a Design activity
performed to create a component or assembly with an up-to-date, complete and
configured environment.
The process is broken down into 3 steps:

Step 1: define working environment or context,
Step 2: design in 3D with configured context,
Step 3: design context check.
The actors in this process are the Design Engineering team members (e.g. Structure
Designer, System Installation Designer). They are accountable for developing a technical
solution using a complete and up-to-date configured working environment.
Design in context presents a number of advantages:
enables the designer to create and re-use a 3D working context on up-to-date data,
enhances the 3D design quality by embodying some aspects of interface
management into the design process (reduction of collision during design e.g. clash
and clearance detection),
reinforces the reliability of the CAD design.
Output:
Configured
Context

Define Working
Environment

Design

Design Context
Check
Step 1 Step 3 Step 2
Output:
3D data
Input:
Configuration
Output:
Parts and Assemblies
Designed in Context

Design in Context
AP5243
Issue: B


Page 5 of 11
3 Flow Chart
Airbus on-site users shall directly use the General Process described in chapter 3.2.
3.1 Specific Process for RSP and Suppliers
The following flowchart describes the Specific Process for RSP and Suppliers, which embeds
the "General Process" for Design-in-Context as outlined in chapter 3.2. The actors described
below are commonly used by this process but may differ due to contractual obligations - in this
case the contract is always the master definition.
Basic Data Exchange: There is regular exchange of 3D data between the Airbus and Supplier
Data Exchange teams.
Remote Access: The Supplier is granted limited remote access to the Airbus PDM for creation
and modification of components.
Input
(Documents)
Activities Output
(Documents)
Actors References
WP
X.Y.Z
RSP/
Suppliers
Airbus
RSP/
Suppliers
3D data request
Identify 3D data needed
(Only for Basic Data
Exchange)
A
3D data
3D data Share 3D data
3D data request
Data base
Data base
General Process
3D data
Send/Share 3D data RSP/
Suppliers
3D data checked
3D data 3D data checked
End
M2971
AM2037.6
M2816
AM2221
M2971
M2971
Data exchange/Remote
Access of 3D data
Prepare 3D data
(Only for Basic Data
Exchange)
Data base
M2971
AM2037.6
M2816
AM2221
B
C
D
E
1 to 9

Figure 1: Specific Flow Chart for RSP and Suppliers

Design in Context
AP5243
Issue: B


Page 6 of 11
3.2 General Process
The following flowchart describes the "General Process" for Design-in-Context, it is applicable
to Airbus and RSP/Suppliers.
Before following the "General Process" shown below, RSP and Suppliers shall perform some
preliminary steps, described in Chapter 3.1.
Designer
Designer
Designer
Designer
S
t
e
p

1
:

D
e
f
i
n
e

w
o
r
k
i
n
g
c
o
n
t
e
x
t

S
t
e
p

2
:

D
e
s
i
g
n

S
t
e
p

3
:

D
e
s
i
g
n

C
o
n
t
e
x
t

C
h
e
c
k
Input
(Documents)
Activities Output
(Documents)
Actors References
X.Y.Z.
WP (for RSP mainly)
MSN(s) (not for RSP)
Scenario(s) (not for RSP)
Query saved
Define context
Save query
Update context
Check 3D data
Store & share
checked 3D data
Release Process
End
Context
Context
3D data
Context
Product structure
3D data
Drawing sheet
Create and follow-
up Mock-Up Issue
DMU trouble
Change note/
request
Context
Data base
3D data checked
Data base
Context
Query saved
3D data
Context
3D data checked
Data base
Create
COMPONENT
Modify
COMPONENT
3D data
compilant
with Airbus
rules?
Decision to
Release?
Parts and Assemblies
Designed in Context
1
2
3
4
8
5
6
7
This task is mandatory and must always
be performed regularly with an update
context and before delivery, on MSN
range corresponding to the effectivity of
the impacted LO
Designer
Designer
No
Yes
9
AM2037.5
AM2211.4
M2971
AP2641
AP2266
M2971
AM2259
AP2615
AM2037.4
AP2604.1
AP2604.2
AP2078
AM2037.5
AM2211.4
M2971
AM2037
M2269
M2832
M2971
AP2604.0
M2971
AP2763
AP2766
No
Yes

Figure 2: General Process Flow Chart

Design in Context
AP5243
Issue: B


Page 7 of 11
4 Detailed Activities
No. Name of Activity Description of Activities

A Identify 3D data
needed (only for
Basic Data
Exchange)
Basic Data Exchange: The RSP/Suppliers make a request to Airbus for
the delivery of the required 3D data, corresponding to their WP in order to
create a working environment.
Remote Access: Refer directly to Activity No. C.
B Prepare 3D data
(only for Basic Data
Exchange)
Basic Data Exchange: Airbus is responsible for providing 3D data to
RSP/Suppliers. Airbus validates the data request and prepares the 3D
data transfer.
Remote access: Refer directly to Activity No. C.
C Send/Access 3D data Basic Data Exchange: Airbus sends/transfers the requested 3D data to
RSP/Suppliers, at an agreed time/interval.
Remote access: Airbus provides the RSP/Suppliers access to the 3D
data.
D Share 3D data The RSP/Suppliers share and use 3D data with the Basic Data Exchange
or remote access method to create a working environment as detailed in
the General Process.
1 Define context The Designer creates and runs a query to obtain the required configured
context.
2 Save query The Designer shall save the query in order to re-use the same context.
3 Create component Design the 3D Component in a Configured Context:
the responsible for the specific design completes their design work
applying the appropriate skill/techno processes and methods for the
programme,
finally the design data is stored in the PDM tool. The PDM tool
manages the Design maturity, status, effectivity, etc.
Note: During Development (DnA)/Definition (DARE) phase the Drawing
Set (with associated Bill Of Material) has to be created.
For skill/techno processes and methods refer to: Electrics: AP2997,
Kinematics: AP2268, Mechanical Systems: AP5240, Equipment
Integration: AP5239
4 Modify component When required modify, the existing 3D component in a configured context.
This step is mandatory if the 3D data does not pass the design checks.
Note: In development/definition phase the drawing set (with associated
Bill Of Material) has to be updated accordingly.
5 Update context Regularly update the context in order to take into account the
modifications that may have occurred within the environment.
6 Check 3D data The Designer shall perform 3D checks in order to ensure the compliance
of the design with Airbus modelling rules:
visual inspection,
clash free design (Structure and Systems Installation),
design compliant with all clearance and segregation requirements
(Systems Installation),
system installation shall be secured (brackets).
Before the check-in to the PDM the checks described in the M2269 shall
be performed.

Design in Context
AP5243
Issue: B


Page 8 of 11
No. Name of Activity Description of Activities

7 Store & share
checked 3D data
The Designer shall store and share the checked 3D data regularly in the
corporate PDM tool.
Details defined in M2971.
8 Create and follow-up
Mock-Up Issue
When the checking process indicates problems with 3D data, these shall
be documented following the DMU Trouble process.
Note:
Change Note (CN) to be used for definition/concept phase.
Change Identification Number (CIN-Mod/MP pair) to be used for
development/definition phase.
E Send/Access 3D data Basic Data Exchange: Supplier DEX team to provide Airbus DEX team
updated 3D data on a regular basis.
Remote Access: 3D data is regularly stored in the PDM tool.
9 Decision to release The impact depends on the phase and the maturity of the design:
Definition/Concept Phase:
The Design Solution is incorporated into the current baseline
design.
Development/Definition Phase:
The component is released and the manufacturing can start.
If the maturity is not sufficient the design work continues.


Design in Context
AP5243
Issue: B


Page 9 of 11
5 Actors
General Process

Actors Activity per actors

Designer
Define and Update context
Save query
Create and Modify COMPONENT
Store & share checked 3D data

Specific Process for RSP and Suppliers

Actors Activity per actors

RSP/Suppliers
Identify 3D data needed (only for Basic Data Exchange)
Define context
Save query
Create and Modify components
Update context
Check 3D data
Store & share checked 3D data
Send/Access 3D data
Airbus
Provide complete cDMU environment and update it on delta mode (No complete
update)

Design in Context
AP5243
Issue: B


Page 10 of 11
6 Reference Documents
Doc Reference Title
A2240 Design Structure & System Installation
AM2037 Standardization of Inspection Process and Test Methods
AM2037.4 DMU Trouble and Review Management
AM2037.5 Data Preparation for Design in Context with Trend
AM2037.6 DMU Design Review with Dvise
AM2211 As-Defined Product Structure Concept and Rules
AM2211.4 PRIMES SSI Configured Digital Mock-Up
AM2221 Collaboration Methods for Suppliers Industrial Partners on Sub-Contractors
AM2259 3D Modelling Rules for CATIA V5
AP2078 Change Process During Concept/Def Phase
AP2266 Digital Mockup Rules and Life Cycle
AP2604.0 Management of Design Reviews
AP2604.1 DMU Clashes & Troubles Process and Integration Reviews
AP2604.2 DMU Troubles Management in the Aircraft Integration Context
AP2615 Creating Digital Drawing
AP2641 Product Structure
AP2766 Create and Validate Product Definition with Configured DMU
M2269 Design Quality Assurance Checking Rules
M2816 DMU Exchange Conversion for Suppliers
M2832 cDMU Overall Checking Process, Roles and Responsibilities
M2971 Design in Context General Rules
7 Glossary
Always refer to AP2080 - LEXINET
Assembly Assemblies are types of Component node that can recursively contain
further Component nodes in a hierarchy. Usually, they only contain position
information of the child hierarchy or manage inter-dependencies and
relationships between the child Components
Component Elementary data stored in a database with associated attributes (Number,
Name, Level-Type). Components can link to Components or Models
Configured Data Components applicable to a specific Scenario/MSN or a range of
Scenarios/MSN
Context or
Environment
A hierarchy of Configured Data bounding/surrounding the data to be
updated, extracted from the Product Structure.
Model A parameterised elementary CAD definition for manufacture

Design in Context
AP5243
Issue: B


Page 11 of 11
Contributors
Name Function

HORLER Christopher Integrated Backbone Processes - DMU
BLANKE Matthias Integrated Backbone Processes - DMU
ASH Stephen Head of DARE EiSD WP3 - cDMU
PARNAUD Jean-Marie Head of EMSBD - Integrated Backbone Processes - DMU
MARTIN Nathalie Head of Design Policy & Development
CAIN Philippe Architecture & Integration - EDSBIM
TESTAS Pascal Equipment Integration Expert - EDS
Record of Revisions
Issue

Date Reasons for Revision
A Apr 2009 Initial issue.
B May 2010 AP2660 cancellation, some smaller corrections, List of
Actors added.

If you have a query concerning the implementation or updating of this document, please
contact the Owner on page 1

For general queries or information contact:
airbus.documentation-office@airbus.com

This document and all information contained herein is the sole property of AIRBUS S.A.S. No intellectual property
rights are granted by the delivery of this document or the disclosure of its content. This document shall not be
reproduced or disclosed to a third party without the express written consent of AIRBUS S.A.S. This document and
its content shall not be used for any purpose other than that for which it is supplied. The statements made herein do
not constitute an offer. They are based on the mentioned assumptions and are expressed in good faith. Where the
supporting grounds for these statements are not shown, AIRBUS S.A.S. will be pleased to explain the basis
thereof.

REFERENCE AP5243
Validation Report
ISSUE B DATE 30 Avr 2010
Design in Context
Validation Report
APPROVAL
Name [Siglum] Date
PARNAUD JEAN-MARIE [EMSBD] 06 Mai 2010 Electronically validated
Ash Stephen [EDSI] 07 Mai 2010 Electronically validated
THIEBAULT ROMAIN [KESI] 10 Mai 2010 Electronically validated
LEDOUX SEBASTIEN [EDCI] 12 Mai 2010 Electronically validated
Brodersen Christian [TBCED3] 19 Mai 2010 Electronically validated
AUTHORIZATION
Name [Siglum] Date
MARTIN NATHALIE [EDSBIM] 20 Mai 2010 Electronically validated
AUTHORIZATION FOR APPLICATION
Name [Siglum] Date
DUPONT MICHEL [EDSBI] 21 Mai 2010 Electronically validated

Design in Context: Instruction Issue

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Design in Context: Instruction Issue

Uploaded by

Copyright:

Available Formats

Instruction

You might also like