10. April 2008 Presented by Matthias HOFMANN Configuration Management Consultant AIRBUS CIMPA Frank MÜLLER Head Of Configuration Management EADS Defence Electronics Effective Configuration Management through Standardisation PLM characteristic with a standard tool with specific interfaces to design Managing CM in a Complex International Project AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation
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 AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 2
CIMPA Portfolio Our service-clusters improve: Processes Configuration Application & Methods PLM services covering the whole life cycle Software Products Simulations & Visualisation CM Supplier Collaboration In-Service Operations CIMPA offers Consulting, Solutions & Support AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 3
Role of CIMPA in the Project CIMPA is the EADS service company for Product Lifecycle Management (PLM) 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 270 Ensures the consistency of your product performance Manage customer requirements efficiently Drive corrective actions to a minimum AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 4
Definition Configuration Management Structure Our understanding: Library Management Knowledge Management Data Management 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) Document Management Change Process Release Process Requirements Management AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 5
Task of EADS DE in the A400M Programme: System Responsibility Changes Requirements Change Changes Requirements Suppliers Change AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 6
The quality of Configuration Management The Quality of CM is (mainly) determined by three factors Product Process Culture IT-Solution Project Goals AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 7
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 efficient Change Process AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 8
The General Change Process Released Information Formal Check (CM) Validation Start Problem Change Report Request Work Order Up-Date/Creation of Items Usage of released Items Request Documents Implementation Planning Categorization (CM) Cost estimation Technical Review Management Decision Change Notice Execute (CM) AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 9
The CM II Standard proposes a Change Process released Infomation Change Specialist III Validierung By User Start Work Order Request Documents Problem Report Change Request Up-Date/Creation of Items (CIB) Implementation Planning (Author) Change Specialist I Cost estimation Usage of released Items (CRB) Change Notice Change Specialist II Change Notice Rules simple? (TRB) Technisches Review (Author) 75 85% Management Decision (Author) Accellerated Path AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 10
The Challenge of the Supply Chain : The Multiplied Loop of the Change Process AIRBUS (Aircraft) EADS DE (System) Supplier (Equipment) AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 11
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 Data and Information AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 12
Overcome A400M Strategic the Borderlines Work share The necessity to organise interaction of several company in different countries face the problem of cultural borderlines to be overcome. France Germany Spain UK Belgium.A.S. All rights reserved. Confidential and proprietary document. Turkey The answer is again standardisation, especially the definition of a common language and Common understanding of processes. AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 13
IT Landscape In the ideal case all stakeholder in the project use the same IT solution for CM, but in reality this is usually not the case AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 14
The Quality of CM in a Complex Project The Quality of CM in a complex project is (mainly) determined by only two factors Product Process Culture IT-Solution Project Goals AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 15
EADS PHENIX Program CM in the scope of EADS PLM Harmonization Program PLM Harmonization for ENhanced Integration & excellence Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
Table of Contents Current EADS initiative PHENIX What is CM for EADS and in PHENIX? Areas of interest with respect to CM How we use CMII Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
Why PHENIX? PHENIX is the acronym for PLM Harmonization ENhanced Integration and excellence To improve EADS Group integration and excellence through Product Life Cycle harmonization It is one of 11 EADS top priorities, directly launched in 2007 and driven at EADS CEOs level => Develop and implement a common policy for Product Lifecycle Management (PLM), methods and tools EADS-wide, build common IT infrastructures Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
What is the PHENIX Program for EADS? Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
PHENIX Program Objectives EADS PLM Harmonization Cost reduction Ability to operate as a worldwide Ext. Ent. Avoidance of non quality & dramatic consequences Golden rules, lessons learnt, support to Governance (KPIs ),... Excellence in WorldWide Extended Enterprise collaboration Global virtual enterprise with common standards, shared tools & processes including with partners Cooperation and mutual support between BUs and different sectors: Military and Civilian Transfer of workload, expertise, Sharing of common services Common training, technical support, Stronger driving of PLM solutions Providers Excellence & Agility Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC Agility and flexibility in front of customers vs. competition Readiness of high level skills & capabilities Influence on PLM standards
PHENIX Program Organisation Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
PHENIX Programme priority domains Engineering & Manufacturing Design Improve usage of DS tools and build EADS strategy towards DS/IBM Master Product Definition Enable to manage all relevant product data through all the phases of a Programme in a context of EE Configuration Management Enable efficient cooperation internally and with suppliers and partners Extended Enterprise Integrate EADS as a Group in a context of EE and enable cooperation between Divisions/BUs Requirements Management Get common understanding and better management of requirements / specification with customers and partners Digital Mock-Up Operations Operate DMU as 3D reference for Physical Product Definition Link with Program Management Make programme managers use the PLM as a control panel for programme progress and efficiency Simulation Tools Improve interfaces of simulation with other product development activities and build common strategy towards tools providers Integrated Technology Processes Enable efficient and integrated management of technological processes from Design to Manufacturing phases Electrical Design Elaborate a common Electrical design tool and database Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
Table of Contents Current EADS initiative PHENIX What is CM for EADS and in PHENIX? Areas of interest with respect to CM How we use CMII Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
List of Divisions / BUs Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
Importance of CM to EADS CM as a process insures consistency between requirements raised or changed to a product and its definition/realisation Vision of the CM team is to develop a set of CM processes, which can be applied as an industrial standard (internally and extended enterprise) For EADS CM is a core process to define, produce and operate complex high-tech products => CM enables the management of complexity which can not be handled by human intelligence. CM is an excellent platform and major prerequisite to avoid non quality issues and related costs (=> in CMII called cost for corrective actions). A robust and practical CM process is a prerequisite to unleash benefits of state-of-the art PLM technologies, e.g. configured digital mock-up. Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
What is CM for EADS? CM is a leading process to enable cooperation, harmonisation and identity at EADS group level and by this CM is a key enabler for world-wide extended enterprise. Definition from ANSI: A management process for establishing and maintaining consistency of a product s performance, functional and physical attributes of the product with the requirement, the design and operational information throughout the entire life cycle. Embedded in the EADS product life cycle management framework, CM aims at a continous improvement of the value chain by reducing corrective actions by establishing a EADS industrial standard process for CM to be applied for future programs. Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
Why CM? 3 Can I justify what I intend to build to fulfil my contract? 5 1 Do I understand the contract that I have to fulfil? Can I justify what I have built to fulfil my contract? Justification Requirements Definition 4 Do I know what I have built to fulfil my contract? 2 Do I understand what I have to build to fulfil my contract? Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
Table of Contents Current EADS initiative PHENIX What is CM for EADS and in PHENIX? Areas of interest with respect to CM How we may use CMII Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
Work approach CMII as basis of future processes for CM Each point will be handled in 2 steps: Consideration of CMII solution/principles Adopted proposal for EADS process / template etc. Followed by plenary discussion and collective acceptance / amendments / adaption We started defining the most complex processes, defining all process steps, decision points, associated data and required analysis steps etc. Based on this, we will define further options and light process. Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
ENC Configuration Management List of use cases 1. Change management 2. Baseline management 3. Product structure 4. Customization 5. Status accounting 6. Effectivity management 7. Conformity and attestation 8. In service configuration 9. Release management 10. CM plan & CM policy 11. Contract Management 12. Configuration Management of Software Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
Table of Contents Current EADS initiative PHENIX What is CM for EADS and in PHENIX? Areas of interest with respect to CM How we use CMII Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
Application of CMII - examples 1. Change management CM II Principles: applicable EADS Requirements: Extension/Adaptation of CM II change process for different purposes (full change process / fast track) 2. Baseline Management CM II Principles: applicable EADS Requirements: Adaptations / extension of CM II definition 3. Product structure CM II Principles: not directly applicable EADS Requirements: very complex requirements in PLM frame, use case definition in cooperation with Phenix Task Forces 4. Customization: CM II Principles: not covered EADS Requirements: very complex requirements in PLM frame, use case definition in cooperation with Phenix Task Forces 5. Effectivity management CM II Principles: not directly applicable EADS Requirements: very complex requirements in PLM frame, use case definition in cooperation with Phenix Task Forces Frank Müller (TF CM) (PHENIX Programme) ProStep ivip Symposium 2008 PUBLIC
Contact Matthias HOFMANN Configuration Management Consultant CIMPA GMBH GASSTRASSE 6 22761 HAMBURG, GERMANY EMAIL: MATTHIAS.HOFMANN@AIRBUS.COM www.cimpa.com Frank MÜLLER Head of Configuration Management EADS Defence Electronics EADS PLM HP TF CONFIGURATION MANAGEMENT EADS DEUTSCHLAND GMBH WÖRTHSTRASSE 85 89077 ULM, GERMANY EMAIL: FRANK.A.MUELLER@EADS.COM TEL: +49 731 392 5842, FAX +49 731 392 205842 www.eads.net Thank you for your attention! AIRBUS CIMPA, ProSTEP Symposium 2008, Effective CM through Standardisation, 10.4.2008 Page 16
This document and all information contained herein is the sole property of CIMPA GmbH. 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 CIMPA GmbH. 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, CIMPA GmbH will be pleased to explain the basis thereof.