e-business and partner integration bmw group 25.04.07 seite 1 ca/pdm partner integration in vehicle...
TRANSCRIPT
E-Business andPartner Integration
BMW Group25.04.07Seite 1
CA/PDM Partner Integration in Vehicle Cooperations.ProSTEP iViP Symposium 2007.
Holger Brückner, BMW AGApril 25th, 2007
E-Business andPartner Integration
BMW Group25.04.07Seite 2
CA/PDM Partner Integration in Vehicle Cooperations. Agenda.
1 Supplier Integration vs. Partner Integration
2 Cooperation Setup
3 MINI Cooperation with IDG
E-Business andPartner Integration
BMW Group25.04.07Seite 3
CA/PDM Partner Integration in Vehicle Cooperations.Agenda.
1 Supplier Integration vs. Partner Integration
2 Cooperation Setup
3 MINI Cooperation with IDG
E-Business andPartner Integration
BMW Group25.04.07Seite 4
low to medium complexity
Design & Integration OEM-driven
Only OEM Technology
medium to high complexity
Design supplier-driven, Integration OEM-driven
OEM-compatible technology
Design and Inte-gration supplier-driven
Highly interoperablesystems
very high complexity
CA/PDM Partner Integrationin Vehicle Cooperations.Supplier Integration vs. Partner Integration.
E-Business andPartner Integration
BMW Group25.04.07Seite 5
Characteristics of supplier integration.
– Integration of suppliers for individual parts, modules and vehicle systems is a well established process
– Standardized approaches and tools are available for the partners
– Access via the „Partner Portal of theBMW Group“:
– More than 70 Applications directlyavailable
– All required Information is covered orcan be downloaded
– CA, PDM, E/E and other Dataexchange via the Partner Portal or OFTP
– Geometrical and functional integration of the complete car, including supplier input, and the downstream processes are handled at the BMW Group
E-Business andPartner Integration
BMW Group25.04.07Seite 6
Characteristics of partner integration.
– Engine or vehicle development projects demand a higher degree of integration for the development partner
– The development partner also carries out integration and/or downstream processes and/or manufacturing, depending on the agreed scope of cooperation
– Internal processes established at the BMW Group may be split and interfaces have to be provided
– The development partner works with his tools and according to his processes. Contents and quality of the data transferred at synchronization points have to be agreed between both partners
E-Business andPartner Integration
BMW Group25.04.07Seite 7
Partner Integration Network.Different standards and processes apply.
Partner Processes
Partner Product Development Process
Partner Suppliers
Partner Supplier Integration
BMW Group Processes
BMW Group Product Development Process
BMW Group Suppliers
BMW Group Supplier Integration
„Interpreter“BMW Group Partner
E-Business andPartner Integration
BMW Group25.04.07Seite 8
Partner Integration Network.Different standards and processes apply.
Partner Product Development Process
BMW Group Product Development Process
PDM System Integration and automated data interfacesare the challenge!
„Interpreter“BMW Group Partner
E-Business andPartner Integration
BMW Group25.04.07Seite 9
CA/PDM Partner Integration in Vehicle Cooperations. Agenda.
1 Supplier Integration vs. Partner Integration
2 Cooperation Setup
3 MINI Cooperation with IDG
E-Business andPartner Integration
BMW Group25.04.07Seite 10
Establishing Partnerships.
Setup
– After a partner has been chosen, the collaboration is being planned on several levels in succession:
– Business Case– Processes– IT Systems and resulting IT-Projects
Work– The project work will commence as soon as the
necessary ties have been made
– The goal is to find the most suitable partner regarding strategy, realization and infrastructureSelection
Evaluation– Before a new partnership is established, the
overall business and project scenario is evaluated
– Termination of automated connection– Security aspects have to be followedEnd of
Project
E-Business andPartner Integration
BMW Group25.04.07Seite 11
IT Projects
Business Model
IT System Model
Process Model
Code Title Internal (my)
Budget (k€)
Capital (k€)
Internal (my/y)
Budget (k€/y)
Capital (k€/y)
Begin (Year)
Assumed timing milestons:08/02 start of period under consideration09/06 start of production09/13 end of production
Difficult governance process Programme Leader 4,5 2002
Org. structure comparable with E83
Pgr. Administration, Pgr. Office 4 2002
Overhead for communication process with P2
Reporting, Tool support 2002
Use of BMW tools; E83 tools to be improved
Pgr. Mgmt. Tools
Change-/Issue-/Risk-Mgmt. 2002
E83 and Prince IT models are suitable to set a basis for a generelised IT model for car cooperations
Planning/development of an improved IT model 1,5 480 2002
10 990 150 0 0 0
none Process definitions 1 300 10 2002Covisint Collaboration Manager
Process to be implemented 0,2 50 0 0,2 200 30 2002
Document exchange will be made through a Marketplace (Covisint) DMS
Process to be implemented 0,2 100 200 0,2 20 0 2002
Alias Design datawill not be transfered to P2 ALIAS None 0 0 0 0 0 0 2002
Exchange through Covisint ASCET Process to be implemented 0 0 0 0,1 20 0 2002
Plant design data will be transfered on DXF Basis AUTOCAD
Process to be implemented 0,2 200 0 0,1 30 20 2002Interface between the
Environments must be developed for platform transfer P2 Environment at P1 must be provided CATIA V4
Process to be implemented 0,5 500 100 0,3 150 0 2002
CATIA V4 Development of Interface 0,5 300 20 0 0 0 2002
CATIA V5 Harmonisation of environment 0,5 300 20 2002
CP1Product Development
EB-2
General FZ-D
Assumptions Expenditure for additional operating and maintanance
150
P1 Expenditure for adaption/development of IT Systems/Interfaces and Project-/Programme Management
Responsible BMW IT Function
Major P1 IT Systems involved
IT Measures for adaption/development of involved P1 IT Systems or Interfaces
510
P1 Core Processes
Sub Total General
Project Office Assistence. Expenditure cumulated over 2,5 years. General assumption: For the CP1 project activities 2 Job Cards will be approved for a period of 2 year
Res
ourc
e Pl
anni
ng
Description of the required IT systems at each partner. Definition of the main interfaces that have to be created. Rough sketch of the dataflow between the two partners.
Documentation of all relevant core processes at both partners, as well as the communication, transformation und synchronization processes between the two partners.
Outline for the division of work between the two partners, i.e. which services have to be provided by one partner to the other. Basic principles for work and cost sharing.
Planning of the individual projects, including due dates. Assessment of required efforts. Specification of the resulting requirements concerning information security and joint system agreements.
Scope and objectives of the Planning Models.
E-Business andPartner Integration
BMW Group25.04.07Seite 12
Partner Integration Interface.Summary.
– The BMW Group offers a pre-defined set of interfaces such as the “Partner Portal” to all its partners. These are also used in the individual projects.
– Systems and processes for partner integration are designed for reusability and sustainability if possible.
– Wherever possible standardized neutral formats, such as STEP AP214 for PDM data, are used to transfer information.
– If individual adaptations become necessary, they are implemented based on clearly defined processes.
E-Business andPartner Integration
BMW Group25.04.07Seite 13
CA/PDM Partner Integration in Vehicle Cooperations. Agenda.
1 Supplier Integration vs. Partner Integration
2 Cooperation Setup
3 MINI Cooperation with IDG