10. April 2008
Effective Configuration Management through
Standardisation
Presented by
Matthias HOFMANN
Configuration Management Consultant
AIRBUS CIMPA
Frank MÜLLER
Head Of Configuration Management
EADS Defence Electronics
PLM characteristic with a standard tool with specific
interfaces to design –
Managing CM in a
Overview
Configuration Management for A400M Programme
System Level
• Company CIMPA & CIMPAs role in Project
• Managing CM in a complex international project
CM in the scope of the EADS PLM Harmonization program
• PHENIX
• What is Configuration Management for EADS
• How EADS Defence Electronics use Configuration Management
• CM from design to product
CIMPA Portfolio
PLM services covering the whole life cycle
Our service-clusters improve:
Processes
Configuration
Application & Methods
Software Products
Simulations & Visualisation
Supplier Collaboration
In-Service Operations
CIMPA offers Consulting, Solutions & Support
Role of CIMPA in the Project
CIMPA delivered services for EADS DE
Manage Interface between System Level
(EADS), Supplier and Customer (Airbus)
Definition of a common change process
Project plan and project management of
change process
Ensures the consistency of your product
performance
Manage customer requirements efficiently
Drive corrective actions to a minimum
CIMPA is the EADS service company for
Product Lifecycle Management (PLM)
Library Management
Document Management
Data Management
Definition Configuration Management
Our understanding:
“Configuration Management ... is a
management process for establishing and
maintaining consistency of a product's
performance, its functional and physical
attributes, with its requirements, design and
operational information, throughout its life.”
(ANSI)
Change Process
Release Process
Requirements Management
Knowledge Management
Structure
Task of EADS DE in the A400M Programme:
System Responsibility
Suppliers
Requirements
Changes
Requirements
Changes
Change
Change
The quality of Configuration Management
Process
Culture
IT-Solution
Product
Project Goals
The Change Process as a Core Process
A common problem of the Change Process
…is that it is often
heavy & inflexible
Goal is to
define
an
The General Change Process
Problem
Report
Cost estimation
Categorization
(CM)
Technical
Review
Management
Decision
Implementation
Planning
Execute
(CM)
Change
Notice
Request
Documents
Validation
Formal Check
(CM)
Work
Order
Released
Information
Start
Change
Request
Usage of released Items
Up-Date/Creation
Rules
The CM II Standard proposes a Change Process
Problem
Report
Cost estimation
Change
Request
Change
Specialist I
Technisches
Review
Management
Decision
(CRB)
Implementation
Planning
(Author)
(CIB)
(Author)
(TRB)
(Author)
simple?
Change
Specialist II
Change
Notice
Change
Notice
Validierung
By User
Change
Specialist III
Work
Order
Accellerated Path
75 – 85%
released
Infomation
Start
Usage of released Items
Up-Date/Creation
of Items
Request
Documents
The Challenge of the Supply Chain :
The Multiplied Loop of the Change Process
AIRBUS
(Aircraft)
EADS DE
(System)
Supplier
(Equipment)
The Glue of the Supply Chain: Interfaces
Prerequisite of smooth functioning interfaces are again
…clear definition of
the interface processes and
roles & responsibilities.
For example
single point of contact:
Handover from CM to CM or
defined forms for Exchange
.A .S . A ll ri g h ts re s e rv e d . C o n fi d e n ti a l a n d p ro p ri e ta ry d o c u m e n t.