02.seance LDP DEVELOPPEMENT V3P - ENV1

XX PROJECT
"Development" information session

Vehicle Pre Contract (VPC) – Tooling Go Ahead (TGA)
DPMI/DDSCR
"Development" session
Process and development
logic
DD/MM/YYY CONFIDENTIAL c
Phase launch information sessions
V3P logic
Kick-Off Concept Vehicle Pre- Tooling Go Manufacturing

Project Freeze Contract Ahead Approval (MA)
(KOP) (CF) (VPC) (TGA)
GUIDELINES OPTIMISATON DEVELOPMENT INDUSTRIALISATION
TIME axis
 4 information sessions co-ordinated by the CVEa preparing

for each major project phase
 For operation participants (IST, PFE, PPC, etc.)
 Based on the unifying processes (expectations, tools,
documents, etc.)
DPMI/DDSCR
logic
Contents
 Introduction
 Project progress
 Schedule and development logic
 Quality expectations
 Convergence activities
 Product-process convergence of design requirements
 Geometry
 Requirements
 Electronic circuitry
 Diagnosis
 Technical documentation
 Validation supports
 Tools
 Design Quality Control
 Management of externally worked parts
 Regulation/certification
 Industrial system
 Process and documentation methods
 Conclusion
DPMI/DDSCR
logic
Introduction
Message of the assistant CVE
x
Assistant CVE
DPMI/DDSCR
logic
t C VE
i stan
s
e as
BY th
D
L E TE
OMP
BEC
T O
DPMI/DDSCR
logic
Project progress
Schedule and development logic
X
IPP
DPMI/DDSCR
logic
Activities and milestones of "Development" phase
Vehicle Pre Contract Tooling Go
Contract (VPC) (CO) Ahead
Confirm the Master schedule IPP
Co-ordinate the lead-time IPP
tion ra
Commit to
ee
a
Co-ordinate IPP
Prep
engin
RO launch
r
Update the activities in development phase Co-ordinate the lead-time IPM
to consolidate the master schedule managers
Technical de
Analyse and sign the master schedule => managers
Objective of this process in this phase:
• Remove the reservations and the critical points resulting from VPC
• Ensure consistency between metier schedule and Master-schedule
• Finalise the schedule
DPMI/DDSCR (TGA-MA phase)
"Development" for Contract milestone
session
logic
• Remove the reservations and the critical points resulting from
DD/MM/YYY c
contract
CONFIDENTIAL
hase
r ned p
once
t hec
r only nes
d u le o ilesto
s c he ure m
let e e f ut in ts
p t h o
e com ts on itical p
es th men r cr
t
as d com ents o
y p
c op e an ant ev
IPP is slid mport
in th ell as i
as w
DPMI/DDSCR
logic
Project progress
Manage project quality assurance
X
Project quality
engineer
DPMI/DDSCR
logic

Synchro Consistency Completion
Quality milestone convergence ( IAQ)
Animation of the risk control on the perimeter CVE( IQP)
Project dashboard (including synthesis LUP PRO)( IQP)
"Development" phase
Design requirements product process convergence with the suppliers & tool-
makers
DPMI/DDSCR
logic
Activities of "Development" phase process
Expectations and participants
CO/TGA quality milestone convergence Quality assurance engineer
 Co-ordination of JQPV convergence for quality milestones (GW1, GW2, VPC)

[Specify the quality project progress review meetings (frequency, co-
ordination, content) ]
 Refer to the key points [ to be refined as per the JQPV V3P contennt
progress]
Technical synchronisation milestone convergence Project quality engineer

 Technical synchronisation milestone convergence co-ordination (Synchro,
Consistency, Completion)
[Specify the quality project progress review meetings (frequency, co-ordination,
content) ]
 Refer to the key points [ to be refined as per the JQPV V3P contennt
progress]
DPMI/DDSCR
logic
IAQ / IQP opinion or agreement for each V3P milestone
Level 1 Milestones : GW1E VPC Contract Launching Life

#1 gives the agreement Cycle
IAQ gives an opinion
Level 2 Milestones :
#2 DGA D3P gives the agreement
IAQ gives an opinion
ConceptGW1I
Intentions Pre-Concept Freeze
Solution Design Theme
proposal proposal Freeze Level 3 Milestones:
Customer Concept USP
#3 DP gives the agreement
Proposal Proposal Check Model IAQ gives an opinion
Freeze
Level 3 Milestones:
IAQ gives the agreement TGA ABPT1 PPC DA CPPM
ABPT2 MA AM
Level 4 Milestones: AB DLot Cy AB EIPFC

#4 gives the agreement
IQP gives an opinion AB DLot VPC
AB DLot Cp
DPMI/DDSCR AB VC
"Development" session DRefCp
logic
DD/MM/YYY CONFIDENTIAL c 12
Processus de convergence au jalons VPC
Contract
(CO) TGA
Jalonnement de la convergence
Jalon Written
- 8 à -6 S - 4 à -3 S -1S
report
Diffusion de la
DGTa Référence produit-process-Design Revue de
Et décisions restantes à prendre passage
Diffusion
IAQ/IQP JQPV et de la Liste des points durs et
raison d’être conditions de réussite &
Emission EQM &
EQGT initialisé EQGT provisoire
24h
Diffusion Recensement des Réduction des

Livrables livrables et écarts et
Métiers/ métiers identification des Construction des
attendus écarts plans d’action Written report si
IQM demandé
Liste des écarts EQM et EQGT
actés -Consolidé (-48h)
-Validé (-24h)
DPMI/DDSCR
logic
Activités du processus phase « Développement »
Attendus et Acteurs
Animation Qualité Projet sur périmètre DGT IQP
 Accompagner le projet et les métiers dans la maîtrise des risques (GRP) et des problèmes (LUP)
 Réaliser le reporting qualité du projet à travers le tableau de bord projet
Faits marquants :
Indicateurs en forte progression : LUP, REVS,
nominations fournisseurs
Project xxx Dashboard
Indicateurs Projet Commentaires DIAM DICAP DIEC DIESC DIESE DPC DIPV Achats
Plans d'actions Jalons précédents r 3 plans d'actions sans solution R V O V O V R V

Maîtrise des risques o retard sur l'avancement des PA. A surveiller O V V O R O V O
Coûts (PRF, TE, Invest) r O O R O O O O V
Planning v R O V O V R R R
Masse r O O O O O O R
Projets transverses (Innovations,
Modules, ...)
v O O V O O V O O
SGP o O O O O O R O
Points durs métiers o O O O O O O O O
78% Soldé (+5% vs s1234) : Il reste 58 k1&k2
Résolution des Ki (LUP) o actifs dont 1 sans nouveau plan d'actions décidé R O O O O O R
+11% P/t s1234 - Plans en execution : 259
Plans de validation (REVS) v Les tests de validation sont à renseigner O V R O O O
ANPQP o R O V O O O
RO pièces r V R O O O O
+6% P/t s1234 - SP : 79% pièces nouvelles
Sourcing plan o Des fournisseurs nommés post contrat => Impacts
IV en cours de consolidation
V O R V O O
Pilotage de la doc v v V V V O O
STR o O O O O V R O
DPMI/DDSCR
logic
Activités du processus phase « optimisation » VPC
Contract
(CO) TGA
Gestion des maitrises des risques IAQ [Atelier 3 et 4 à planifier]
Pre- Concept VPC Launching Life

Concept Freeze Contract
Jalons
GW1 SOS Cycle

Kick-off CF Kick-off C Kick-off L
8 6 10 26
mois mois mois mois
suivi des risques majeurs
Atelier 1
Détection , mise à jour et
Atelier 3 Atelier 4
Atelier 2
Revues Qualité assurent la liaison entre

2
0
programme, projet et métiers lors de
l’apparition de nouveaux risques en cours
de projet (inter-métier)
suivi des risques métiers
Détection , mise à jour et
> Mise à jour des risques DAISI et avancement des

500
contremesures (attendus JQPV)
DAISI / SDF
….
DPMI/DDSCR
logic
Contract milestone (CO)
Purpose and quality macro expectations
Purpose Overall result

Contractualize the quality, cost, The program involves project profitability based on the
schedule, revenue and profitability QCD objectives which are contractualised by the technical
commitment departments
1. Product scenario is contractual

2. The design provided by the support which represents the vehicle maturity
3. Industrial strategy is frozen
4. Schedule is contractualised
5. Project costs are contractualised
6. Commerce is involved in the revenue
7. Profitability is demonstrated
8. Customer requirements technical specifications, the targets and customer
satisfaction commitment are contractual
9. Company's strategy in CO2 is deployed
10. Technical definition is shared
11. Product/Proces validation plans are confirmed
12. The project is organised and the trainings are planned
DPMI/DDSCR
logic
Tooling Go Ahead
Purpose and quality macro expectations
Confirm that the definition level

"Right for RO" technical definition is feasible in compliance
authorised tooling definition release
with the contract commitments
and methods
Key points:
 Technical definition is feasible

 The results of the product/process validation plan comply with the expectations
 Feasibility and projected product/process matrix is demonstrated
 The definition of manufacturing methods is validated
 The project is organised
DPMI/DDSCR
logic
Technical synchronisation milestone
Synchro / Consistency (Cy)/Completion (Cp)

Ensure design robustness and capacity to D Lot and QCDP results are satisfactory and
clear the next milestone consistent
I AM
Key points:
it hD
w
i n ed
 ref
Synchro  Consistency of PlatForm, Vehicle ande powertrainPPDstudies
b CP
 To
Consistency  Robust "contract" preparation
 Completion  Robust "Tooling Go Ahead" preparation
 All the Ki technical problems resulting from D Lot reviews have decided solutions
(LUP PRO)
 Safety kits are ready
DPMI/DDSCR
logic
Convergence activities
Product process convergence of design requirments
X
DIAM chief technical
engineer
DPMI/DDSCR
logic
Ensure Design requirements Product Process convergence
Two big PPPD convergence phase
Development Industrialisation
DOC contrat
VPC TGA Mass production Doc MA
Digital Physical
convergence Mass-production
convergence
Joint Check
Architecture freeze Joint Check PP
Joint Check PT2
Digital Lot Cp Joint Check
PT1
VC
Digital Lot Cy
Synchro
1. Development phase is regulated by Synchro, Consistency (Cy) and Completion (Cp)

architecture milestone
2. It ends in architecture freeze in TGA which marks the end of design

DPMI/DDSCR
logic
Vehicle Pre Cost contract Tooling Go

Contract (VPC) (CC) Ahead
Digitally converge with Digital-Lot
Physical design with PMDR
Shared milestone process (V3P)
Freeze the architecture !

Objective of the process in this phase:
DPMI/DDSCR
logic
Creation and exploitation of Digital Lots
1 Engineer 2 GFE: 3 DGTa 4 DGTa 5/1 Engineer
The interface contract (Interface Self Certification by each The interface contract (Interface
sheets and typical sections) is GFE partcipant that the Compliance level allows sheets and typical sections) is
clear and based on 100% of the part complies with the The expectations in clear and based on 100% of the
to escalate a digital
solved Kis (LUP >2) interface and requirements the milestone are solved Kis (LUP >2)
prototype which can be
Design digitisation is compliant contract (25 evaluation compliant Design digitisation is compliant
used
criteria)
1 Design
Synchronized Engin. 3 Digital – lot : 4 Ki Solving 5/1
GFE
11 weeks 9 weeks 3 weeks 4 weeks
Synchro DP / DT Coherency Product
Product
Evaluation
Unique list
of problems
Design RDS or PDF Design
Coherency
2 Evaluation
Technical Technical
Approval to Built Digital Lot

TOOL? GFE technical reception
GFE
GFE
Suppliers QCDP Suppliers
Milestone Approval
Purchase/ DCV
Design Reference
Purchase/ DCV Evaluation
Design Reference
TOOL? “All
Process Process Process
Evaluation
Evaluation Together”
Engineering
Requirements PPC / QP
PPC / QP
Evaluation
DPMI/DDSCR
logic
Synchro milestone
Synchro milestone objectives

The engineering is commited to digital prototype robustness which will
be assembled in Cy :
 Architecture consistency
 DIV DDI convergence
 Validation announcement
TED
L E
M P
C O
BE
TO
DPMI/DDSCR
logic
Digital Lot Consistency (Cy)
Objective and definition of Digital Lot Cy Engineer
PFE
Design requirements product Process convergence in CAMI

design phase is feasible
PPC
Weight leader
 Digital mock-up is formalized

 100% supplier digitisations , toolmakers are validated for feasiblity validation
 Reference plan confirmed by DIAM chief technical engineer
 P/P convergence mock-ups are completed based on the engineer's requests
 Circulated DL Cy report and open LUP for the identified problems
 Centre of gravity and inertia are updated
 Weight table is updated
DPMI/DDSCR
logic
Digital Lot Completion (Cp)
Objective and definition of Digital Lot Proposal Engineer
PFE
Design requirements product Process convergence in CAMI

design phase is feasible
PPC
Weight leader
 Digital mock-up is formalized

 V3PCONVPPPD - 100% supplier/toomaker detailed technical digitisations for reliability
commitment (Cp)
 Reference plan confirmed by DIAM chief technical engineer
 V3PCONVPPPD - Delivery of parts in trajectory for PMDR
 P/P convergence mock-ups are completed based on the engineer's requests
 Circulated DL Cy report and open LUPs for the identified problems
 Centre of gravity and inertia are updated
 Weight table is updated
DPMI/DDSCR
logic
Architecture freeze
RO part archi approval of the engineer contractualizes

the end of design requirements product process convergence in the design phase:
It formalizes the Architecture freeze of each parts in its environment in ROP
Parts digitisation consistency with its environement in digital:

1. Compliance in interface contracts (FI and typical sections)
2. Validation of operating clearance and interference (geometric file)
3. Digital RCC associated with the complies parts or signed derogations (Compliance of
architecture/assembly metier rules)
4. LUP: Design requirements product process convergence OK (especially integration of PPC feedback
including QP)
5. Specified assembly process: FOP assembly is validated by the GFE
Parts digitisation consistency with its environment in physical:

- Physical RCC of the associated clearance in the complies part or signed exemptions or convered by
a decided digitised kit (Architecture technical rules compliance/assembly)
- DIAM DIESE rating (compliance of DIESE technical rules)
- Fittability (Compliance in metier evaluation standards/DIAM validation plan)
- After-sales repairability( compliance of project objectives)
- After-sales repairability( compliance of project objectives)
Simplification: Clearing a sheet according to the part to a sheet according to the Top
DPMI/DDSCR serie type project
logic is possible as it isDD/MM/YYY
ROP consistency which guarantees RO part consistency
CONFIDENTIAL c
Architecture freeze
"Make a fil rouge archi approval"

Of product process convergence of design requirements in the design phase:
-> Group the part by part evaluation in the unique table
in Top Serie model
1. An expectation in each milestone in a unique format is initialised in FC:

- J2a; "GW2"/ upstream synchro; OPF; VPC; Synchro; CY; CP; ROP (table update)
- Part by part table update and a defined expectation for each milestone
- More efficient sharing of convergence between archi and GFE in all the formulated
criteria
3. Transparent evaluation:
- Each PFE can quickly identify the convergence level of each part in each criteria (2 X 5
criteria)
4. Management according to the architecture zone:

- Rating according to the architecture zone to be shared by the PFE
Comments:
- Expected gain as we move from one sheet per part to a line in an overall table
- We see several "Part by part"table requirements in our V3P reviews
DPMI/DDSCR
logic
Requirements kit
Requirement kit corresponds to a deviation risk coverage in an expectation identifed in the
design phase by optional solution specification.
Option being noted and industrialised before CPP
Objectives of requirements kits
100% of RCC / RTC origin LUPs and design plans in physical are covered by a decided
solution (in database or in option) during TGA
V3P milestone Milestone expectations
The list of kits in V1 V2 AVES "PPC" and forecated reccurrent problems

OPF (VPC) is initialised by ISP and consolidated by DIAM chief technical engineer
Synchro "PPC" kits are decided
"PPC" and "metier" origin kits list is created by PPC and metier and consolidated by DIAM chief
technical engineer
Consistency
Each Kit is characterised by: the customer effect; requestor; decision date which is consistent with
the validation fedback
 Complete list of kits specified is known for the decision in indus phase by each IST / ISP –
Completion Consolidation in the vehicle by DIAM chief technical engineer and launching detailed studies of each
kit
Kits list forzen for eradication in industrialisation phase
TGA 100% of the identified kits are compatible with the projected validation plan in the vehicle
The listed kits weight is compatible with the vehicle approval
DPMI/DDSCR
DLotand
Process OPF 
development
"Development"Risk
session
managementor kits opportunity in QCDP
logic According to which they are "in database" cor "in option"
TGA DD/MM/YYY CONFIDENTIAL
Requirements kits/decision matrix management
K1
Probability Intrusivene
of Kit ss of the Duration of the or
Kit : confirmation kit in the kit parts indus
K2 K3 / K4
cost EICPS
or problem database
rule
Recommende
Base High Low High Long Imposed d
Possible
Not
Short/standa
Option Low High Low Prohibited recommende Possible
rd part d
DPMI/DDSCR
logic
Geometry
X
Geometry leader
DPMI/DDSCR
logic
Vehicle Pre Cost contract Tooling Go

Contract (VPC) (CC) Ahead
GW1 DRVh Synchro Cy DRCp Cp
Carry-out the interior and exterior

gap drawings
Complete the installation functional analysis
Demonstrate the feasibility of vehicle dimension conditions
Control the parts design
Complete the geometry synthesis

Complete the vehicle measurement plan
Demonstrate the industrial
DPMI/DDSCR feasibility of all the vehicle dimension conditions
(platform and bodywork)
logic
Perform the interior and exterior gap drawings DIAM geometry leader
 Defined Interior and exterior pdj feasiblity (Synchro)
 Contractualized inter and exter Pdj (DRCp)
Complete the installation functional analysis Engineer
 Cote table circulated to the project participants (DRCy)
Demonstrate the feasibility of vehicle dimension conditions

Architecture
 80% specifications completed and circulated to the technical departments (Synchro)

 100% specifications completed and circulated to the technical departments (Synchro)
 100% of red specifications processed and the tryout sheets are signed (DRCp)
DPMI/DDSCR
logic
omplete the interior/exterior vehicle measurement plan DIAM geometry leader
Plan the initialised vehicle measurements: measurement sections (Cy)

Validated vehicle mesurement plans (DRCp)
 Finalised 1 TCM measurement plans: measurement points + specifications (TGA + 2
months)
Control the parts design PFE
 50% circulated specifications have a feasibility feedback (métier or HCPP)

(Synchro)
 100% circulated specifications have a feasibility feedback which is 80%
demonstrated (metier or HCPP) (Synchro)
100% identified action plans (non feasible dimensions) (DRCp)
Pdj signed without reservations (DRCp)
List of validated major dimensions DIAM geometry leader
Perform geometry(Cp)
synthesis
 Geometry synthesis (DRCy, Synchro, Cy, DRCp, Cp)
 List of major dimensions created and circulated to the technical
deparments (DRCp)
List of validated
DPMI/DDSCR major dimensions (Cp)
logic
Deploy and validate the requirements
X
ISP
DPMI/DDSCR
logic
Where are we in Design V ?
What does the

What does the
Customer want
Customer want Customer
Customer
satisfaction
subjectiv
What satisfaction
Whatdoes
doesthe
theCompany
Company
want for the Customer
want for the Customer
Requirement validation by the
Requirement validation by the
Functional Company
FunctionalRequirements Company
e
Requirements
n
Specifications
R
io
Specifications (vehicle
(vehiclesummary)
ol
summary)
at
lo
lid
ut
Va
Validation/Specificatio
Quantified Validation/Specificatio
QuantifiedRequirements
Requirements ns of Quantified
Specifications ns of Quantified
Specifications Requirements
Requirements
Technical Specifications of Validation/Technical
Technical Specifications of Validation/Technical
quantifie
Functions/Units specifications of
Functions/Units specifications of
Functions/Units
Functions/Units
d
Characteristics of Validation/Characteristics of
Characteristics of Validation/Characteristics of
Components X,Y, Z Components X,Y, Z
Components X,Y, Z Components X,Y, Z
DPMI/DDSCR
logic

GW1 Synchro Cy Cp
Evaluate and co-ordinate the requirements convergence
Control the study logic (DLots, Calculation, design mules) in the defined
lead-time and update the REVS
Confirm the kits list (base or option) to be developped
Update the expression of requirements in

validation supports (Systems, PT1, PT2)

"Right for RO" technical definition enables to acheive the requirements
contract
DPMI/DDSCR
logic
Evaluate and co-ordinate the requirements convergence
 As per the evolution of parts definition and their impact  PPC of

 Co-ordinate the requirement convergence and solution of identified which
critical points in RPT (calculations, tests, kits ...) reliability
 Perform the synthesis forecast in the use requirements and alert

Betwee
on the inter-requirements crictical points
n  Orients and arbitrates the compromise in the cost-value interedt for
 ISV
each the customer
Digital  Create synthesis in requirements convergence and inter-
Lot requirements consistency
 ISP
 Arbitrate the compromise and the required actions plans (RPP5-
RPP4)
 Analyse the technical definition of the vehicle

 Formalise the inventory and create the Requirements forecast in  PPC
AF, in the reference technical definition database and the results of
During the validation plan
 ISV
Mark all the critical points (LUP) and develop a solution in 4 weeks
Digital
Lot  Identify the topics to be arbitrated
 Creates and circulated the requirements synthesis forecase in eahc  ISP
DPMI/DDSCR milestone "Development" session
logic
Requirements convergenc in RO parts
Date de comité RO: - Fiche standard de validation du lancement RO pièce -
Direction: n°+libellé GFE: Nom du PFE:
Référence pièce: Désignation pièce: Fournisseur: Localisation:
Zone archi.: Cas d’emploi: Réoutillage: Carry-over technique d’un autre véh.? Oui Véhicule: Non
Planning (Rappel : IOD pour anneaux d’analyse : s.837, pour Slot caisse: s.835, pour S-lot: s.842)
Catégorie de Durée de RO: Date Date Spécif. Date RO pièce Pièce Date IOD prévue Prévision
pièce fabricatiuon + map + Spécif. avec plan au plus tard demandée (avec rapport de date PSW
(XXL XL L M transport sans plan (jj/mm/aa) (jj/mm/aa) pour anneaux contrôle fournisseur) K0
S) (no. of weeks) (jj/mm/aa) (oui/non) (jj/mm/aa) (dd/mm/yy)
Plan de validation : Le planning permet-il de respecter le déroulement du plan de validations prévu ? Oui Non
Si non, précisez les validations qui ne seront pas réalisées et le plan de rattrapage prévu:
Procès vérbal CAPRO / DFO: Accepté Accepté conditionnellement Refusé
Agrément DIAM (archi + montage): OK OK conditionnel Non OK => fiche d’agrément DIAM exigée.
Réoutillage à partir de numérisations existantes
Dossier de fixation n°: Nécessaire: Oui Non
Version + Indice de la Num pour RO pièce :
Réserves si OK conditionnel Plans d’actions
Obligatoire
Accord fournisseur ? PPC
Accord outilleur? PFE
Gel Design : OK OK conditionnel (réserves incluses dans la num RO: Oui Non ) Non OK Non applicable
=> fiche d’agrément Design exigée (si applicable).
Réserves si OK conditionnel Plans d’actions Accord fournisseur ?
Accord outilleur?
Major requirements : OK OK with conditions No OK Not applicable
Prestations majeures : OK OK conditionnel Non OK Reservation if Ok with
Non applicable conditions Action plans t Deviation risks
Réserves si OK conditionnel Plans d’actions Risques d’écart
Avancement LUP: OK (Application des Solutions: Oui Non =>justification) Non OK

Dérogations RTC: Non Oui => joindre les fiches de dérogations signées.
Avancement ANPQP Ph1&2: Accepté Accepté conditionnellement Refusé =>Nombre de K50 :
Réserves si OK conditionnel (Liste des K10) Plans d’actions et date de levée des K10
=> La feuille de synthèse ANPQP doit être jointe.
n° de DEVO (Création dossier d’évolution SIGNE):

Achats:
Forecasts and action plans of the requirements affecting
Exigé même pour une spécification sans plans.
Approbation logistique si emballages spécifiques: OK

OPEP à jour: Oui
Outilleur Nommé : Oui
Non
Non => refus.
OK conditionnel
Nom:
the parts are considered for each Top RO part
Non OK
Localisation:
Non applicable
Faisabilité approuvée par l’outilleur: OK OK conditionnel Non OK

Réserves si OK conditionnel Plans d’actions Accord fournisseur ?
Accord outilleur?
PRF=<Budget: Oui Non PRF: Invest.=<Budget: Oui Non Montant: Risques:

Commentaires et plans d’actions si risques:
CdS Métier IST IST DIAM IQP IPP CP Achats
Signatures
Décision DGTa : Accord Refus Name of DGTa : Signature of DGTa :
Motif du refus Plan d’actions demandé
DPMI/DDSCR
logic
Manage the study logic (DLots, Calculation, design mules)

in the defined lead-time and update the REVS
Update the expression of requirments in the validation supports

(Systems, PT1, PT2)
 Ensure standardisation in REVS of the validation plan results

according to the defined schedule
 Define and validate the required actions plans  PPC
 Express the requirements optimised in the validation system
(Systems, PT1, PT2)  ISV
 Guarantee test support update (units, design mules, shells, seating
buck etc)
 Identify and place the critical paths of the validation plan under control
 Guarantee adequacy of validation plan and resources with the
identified project risks
 Consolidate the requirements in validation support (Systems, PT1,  ISP
PT2) for multi-PPC synthesis, safety, reliability-Durability
DPMI/DDSCR
logic
Confirm the kits list to be developped
 Confirm the kits for its requirements by complying with the following milestones:
 Synchro milestone: Recommendation on "in base" kits of XL and L

parts
 Cy milestone: List of kits "in option" is created

 PPC
 Cp milestone: 100% of the kits are feasible and decided
(base or option)
 TGA milestone: 100% of the kits are specified
 Recap: in OPF milestone, definition of the generic list of kits of its requirements
was adapted to its project
 Ensure consistency of kits requested in Inter- requirements  ISP
DPMI/DDSCR
logic
Electrical electronic Convergence
X
EE engineer
DPMI/DDSCR
logic
VPC CO (Contract) TGA
SDE/SDM Cy SDE/SDM
MSG 2 Synchro Cp
PIE B PIE C
CO-ORDINATE THE ARCHITECTURE CONVERGENCE
ENSURE CONVERGENCE OF REQUIREMENTS INTEGRATION
COMPLETE THE ARCHITECTURE FILES
APPLY THE COMMUNICATION NETWORK STANDARDS
PREPARE AND CO-ORDINATE THE PIVs
COMPLETE THE SFA ARCHITECTURE, SDE AND SDM
PREPARE AND CO-ORDINATE THE PIEs
ELECTRICAL CONSUMPTION REQUIREMENTS MUST BE MET
SFIS REQUIREMENTS MUST BE MET
Objective of the process during this phase:

Confirm and validate the vehicle EE architecture
DPMI/DDSCR
logic
"Development" phase process activities
CO-ORDINATE THE ARCHITECTURE CONVERGENCE
Vehicle EE engineer
 Expectations in Synchro milestone – 100 % of the specifications to be validated

 Documentation of the sheet in the milestone, milestone is announced
 Input deliverables: Connecting list feedback: frozen connector definition
 Expectations in Cy milestone – 100 % of the specifications delivered to the suppliers/the parts are
received
 Sheet documentation in milestone, announced milestone
 Closed OPF / VPC ref EE review – Report drafted and presented
 ST2 specifications resulting from PIV are circulated to the suppliers
 Expectations in Cp milestone – EE architecture freeze/100 % SW received/completed HW design

 Documentation of the sheet in the milestone, milestone is announced
DPMI/DDSCR
logic
"Development" phase process activities »
ENSURE CONVERGENCE OF REQUIREMENTS INTEGRATION
EE requirements
integration leader
 Expectations in Synchro milestone – 100 % of the specifications in the process of validation
 Input deliverable (DPC) : ST1 specification judgement report
 Output deliverable:
 ST2 contract sheets (BUIC documentation)
 Drafted BUIC ST2
 Expectations in Cy milestone – 100 % of the specifications delivered to the suppliers/the parts are received
 Input deliverable (DPC) : ST1 specification judegement report
 Electric requirement convergence : No K3

 Input deliverable (DPC) : Functional requirements specifications updated
 Output deliverables:
 DTPE update
 BUIC update
DPMI/DDSCR
logic
COMPLETE THE ARCHITECTURE FILES
Vehicle EE engineer
 Expectations in Synchro milestone – 100 % of

the specifications in the process of validation
 Output deliverable : 100% of the architecture sheets
are drafted and updated
(The architecture sheets are EE architecture file

elements)
DPMI/DDSCR
logic
APPLY THE COMMUNICATION NETWORK STANDARDS

Network telecom
 Expectations in MSG 2 milestone - MSG 2 delivery for RFQ technical specialist
 Input deliverables:
 Network architecture synopsis (CAN and LIN)
 List of ISRs 65690 validated with the defined EE architecture solution
 CAN and LIN V2 messaging
 Network specification of each ECU (milestone + 2 weeks)
 Expectations in Cy milestone – 100 % of the specifications delivered to the suppliers/the parts
are received
 PI wiring dimensions corrresponding to v1.0 topology
 Output deliverable :
 CAN V2.0 topology for PIE C
 HW test results for all the ECUs (CAN, LIN, KWP2000)
 HW compliance of ECUs – expectations: HW network 100% compliant for all the ECUs
DPMI/DDSCR
logic
PREPARE AND CO-ORDINATE THE PIVs

Integration platform
test leader

 Input deliverable (Component leaders/PDE) : Full model for ST2 are delivered in PIV
 ST1 specification checking report (checking trajectory and RA closure)
 MADC PIV ST2
 Expectations in Cy milestone – 100 % of the specifications delivered to the suppliers/the parts are
received
 Output deliverable : ST1 specification checking report (checking trajectory and RA closure)

 Output deliverable : ST1 specification checking report (checking trajectory and RA closure)
DPMI/DDSCR
logic
"Development" phase process activities »
COMPLETE THE SFA ARCHITECTURE, SDE AND SDM
Concepteur Fonction
Schéma Electrique
 Expectations in SDE/SDM PIE B milestone – Closed DSE/SDM PIE B loop Transversal
 Output deliverable : SFA PIE B vehicle reminder (Milestone – 10 weeks)
 Input deliverable (Component leaders/PDE) :
 (PDE/component leaders) Electronic interface sheet (FIE) for QCDP1 PF (milestone – 6 weeks)
 (AEES) SFA function for vehicle PIE B (milestone – 3 weeks)
 SFA architecture for PIE B
 SDE/SDM for PIE B
 Expectations in SDE/SDM PIE C milestone – Closed SDE/SDM PIE C loop
 Output deliverable : SFA QCDP1 PF reminder (Milestone – 13 weeks)
 Input deliverable:
 (PDE/component leaders) Electronic interface sheet (FIE) for PIE C (milestone – 6 weeks)
 (AEES) SFA function for PIE C (milestone – 3 weeks)
 Output deliverables: Milestone
 SFA architecture for PIE C SDE/SDM XXX
 SDE/SDM for PIE C
4 to 6 weeks* SDE
SFA 3 weeks SFA 2-3 weeks
FIE reminder FIE function
SFA archi
SDM
* , according to the project
complexity
DPMI/DDSCR
logic
PREPARE AND CO-ORDINATE THE PIEs

Integration platform
test leader
 The suppliers make the first delivery of B parts to GFE for test in test bench
 Input deliverables: reception of wiring for PIE assembly and the parts in SW1 before MADC PIE B
 Output deliverable : MADC PIE B (milestone – 8 weeks)
 The suppliers make a second delivery of the B parts in SW2 which are 100% operational in GFE
 Input deliverables: realignment of parts in SW2 within three weeks based in the milestone
DPMI/DDSCR
logic
ELECTRICAL CONSUMPTION REQUIREMENTS MUST BE MET

Electrical consumption synthesis
system engineering leader

 Input deliverable (Component leader/ PDE) :100% of the parts electrical consumption commitment of lot 3 are received
 Output deliverable: Synthesis and recommendation on lot 3 parts consumption
 Input deliverable (Component leader/ PDE) :100% of the parts electrical consumption commitment of lot 3 are received
 Synthesis and recommendation in consumption for the contract (CO)
 Update the guidelines if a target modification was ratified

 Output deliverable : Electrical consumption targets are frozen
DPMI/DDSCR
logic
SFIS REQUIREMENTS MUST BE MET
Operational dependability
functioning
 Input deliverable (Component leaders/PDE) : First version of the part by part reactivity table (TdR) especially
CAN and subsidiary
TdR for the subsidiary inputs
DPMI/DDSCR
logic
Diagnosis convergence
Diagnosis
X
Diagnosis IS
DPMI/DDSCR
logic
Plant diagnosis (PEV) and after-sales functions
• After-sales :
 Diagonise the electrical/electronic systems
- At the plant:
 assembly: make certain electronic  Configure, reprogram the ECUs
functions to be operational (calibration,
configuration, programming)
 Check Assembly value (link between

the connectors)
 Enrich the database for after-sales

(example : Worldwide vehicle database)
DPMI/DDSCR
logic
Vehicle Pre Tooling Go

CO (Contract)
Contract (VPC) Ahead (TGA)
Doc Synchro Cy Doc Contrat Cp
DPDSA : Manage the on-board diagnosis resources and the diagnosis specifications
Systems: Specify the system diagnosis methods and deploy their on-board diagnosis resources
PDE : Specify the on-board diagnosis resources
Create electrical study diagram in all the project diversities
Specify the configuration files and programming and calibration files
DPDSA : Manage the plant methods

To perform and validate the diagnosis specifications
To carry-out the validation plan and the first tests
DPMI/DDSCR
To top the off-board diagnosis
logic
DD/MM/YYYmethods and the plant rangesc
CONFIDENTIAL
"Development" phase
 After-sales Daig PFE

Manage the on-board diagnosis resources and the diagnosis
specifications  ISD
 Manage diagnosis file progress

 Create the diagnosis multi-flap contract (CO)
 Manage to obtain the DED, DFS, DDT database, DC, SEE covering the
after-sales and Plant PEV requirements.
 In DPDSA internal, design the after-sales methods and the plant ranges
for preparing the production (TGA)
Manage the plant methods  PFI PEV
 Create the PEV section of the industrial contract
DPMI/DDSCR
logic
"Development" phase
Systems: Specify the system diagnosis methods and  LIS for VE

deploy their on-board diagnosis resources
 PSV for
powertrain
engineering
 Finalise the diagnosis method specifications
 For VE: Delivery of fixed DFS (Cy) then frozen (Cp)
 For powertrain engineering: Delivery of elementary sheets of the
frozen innovations (Cy), then fixed DED/DFS/DDT database (Cp)
 List the reservations
Create electrical study diagram in all the project diversities  PFE wiring
 Deliver the electrical studies diagrams which enables range design and
after-sales diagnosis methods (Cy, Cp)
DPMI/DDSCR
logic
"Development" phase
 PFE DIEC, DIESC,

PFE, TDE : Specify the configuration files DIESE, DIM
and reprogramming and calibration software
 their TDE
 In link with Documentation, in Synchro doc :

 100% of the "ECU" functions identified are:
 Physical parts: ECUs, electronic cards
 Virtual parts: software, calibration, configuration
 In Doc Contrat :
 100% of the specificatison and "ECU" diversities identified are:
 Physical parts: ECUs, electronic cards
 Virtual pars: software, calibration, configuration
 The specifications are planned.
DPMI/DDSCR
 100% of DPDSA_reprogrammation
logic
DD/MM/YYY
in Contract CONFIDENTIAL
e-rooms c
Convergence diagnosis
Technical Documentation
X
Technical
documentation leader
DPMI/DDSCR
logic
“DEVELOPMENT” PHASE OBJECTIVE
OBJECTIVE OF THE “DEVELOPMENT” PHASE

GW1/VPC Contract TGA
Framing Optimization Development Industrialization
Doc Doc TD
Cy Cp MVMM
 The BOM enables to assemble the different prototype waves

(MVMM).
 The BOM structure is frozen with the commercial diversity in
NewPDM.
 The schedule of specifications is contractualized.
DPMI/DDSCR
logic
“DEVELOPMENT” PHASE ACTIVITIES & ACTORS
ACTIVITIES & ACTORS OF THE “DEVELOPMENT” PHASE

GW1/VPC Contract TGA
Framing Optimization Development Industrialization
Doc Doc TD
Cy Cp MVMM
 Manage the project Technical Definition and the “Doc” reviews IST DIAM
 Circulate the COCA indicator
 Build the TCS PDT
 Manage the documentary production of the project

 Manage the documentation process IDG
 Contribute to the documentary production and validate it PFE

(or LI)
 Build the documentation TDE
DOCUMENTATION
 Manage the prototype documentation PREPARATION
TECHNICIAN
 Give go-ahead to pass the documentation milestones

DPMI/DDSCR
logic
“DEVELOPMENT” PHASE EXPECTED OUTPUTS
EXPECTED OUTPUTS OF THE “DEVELOPMENT” PHASE

 Manage the project Technical Definition and the “Doc” reviews
IST DIAM
DOC CY
 “Cy” Technical Definition
 “Doc Cy” review passed
DOC CP
 “Cp” Technical Definition
 “Doc Cp” review passed
 Circulate the COCA indicator

IST DIAM
DOC CY & DOC CP
 COCA indicator
DPMI/DDSCR
logic

 Build the TCS
PDT
DOC CY
 TCS updated + T&S TCS created + TCS note
DOC CP
 TCS updated + T&S TCS updated + TCS note
DPMI/DDSCR
logic

 Manage the documentary production of the project
PDT
DOC CY
 XPM breakdown updated
DOC CP
 XPM breakdown updated
 Quality defects corrected
TOP DOC MVMM

 100 % of the BOM for the launch of validation mules (MVMM)
DPMI/DDSCR
logic

 Manage the documentation process
IDG
DOC CY
 Translation of the base lot into MTC updated (note de cadrage, framework note)
 “Doc Cy” EQM
DOC CP
 Translation of the base lot into MTC frozen (note de cadrage, framework note)
 “Doc Cp” EQM
DPMI/DDSCR
logic

 Contribute to the documentary production and validate it or
PFE
LI
DOC CY
 BOM at ET level (design) with at least one technical variant
(BOM complying with the Technical Definition)
DOC CP
 BOM at ET level (design) with the whole technical diversity
(BOM complying with the Technical Definition)
 Schedule of specifications
DPMI/DDSCR
logic

 Build the documentation
TDE
DOC CY
 BOM at ET level (design) with at least one technical variant
DOC CP
 BOM at ET level (design) with the whole technical diversity
DPMI/DDSCR
logic

 Manage the prototype documentation
DPT
TOP DOC MVMM

 LUPs concerning the wave closed
 “Top Doc MVMM” review passed
DPMI/DDSCR
logic
Validation supports
X
DIPV IST
DPMI/DDSCR
logic
Objective of each phase
OPTIMISATION Implement the cost/value commitment of the project and define the technical
OPTIMISATION Implement the cost/value commitment of the project and define the technical
solutions designs
solutions designs
DEVELOPMENT Converge the project to a robust ROP which enables to not make any
DEVELOPMENT Converge the project to a robust ROP which enables to not make any
modifications after this milestone
modifications after this milestone
Who to DIPV ?
PROTO milestones
Defines
Defines
Plans
Contractualizes
Contractualizes
IST Protos
Prepares
Prepares
Supplies
CM
Logistics
engineer
PROTO batches
MVMM
MVVS Performs
Evaluates
VC
GEOM VC
Manufacture
Geom PT1
rs
V
V PT1
PT1
CUK
CUK PT1
PT1 Quality
V PT2 analysts
DPMI/DDSCR
logic
DESIGN MULES (MC)
 SCOPE
Supports for system validations:
 GMP DPC (Engine heat & fuel/chipping/sealing)
 GMP DIM (DCMAP)
 ESP & MAP chassis (braking+ steering assy noise + driving noise)
 LAS + brake silence + NVH
 Shocks
 DIESC requirements in the test benches
Vehicle project Technical Documentatio MADC 1st
typology Definition. n milestone Date * vehicle Parts Responsability
First
industrialisation
OPF TD Top Doc OPF Prototype - DIPV :
 Number of supports
 Production place
 Bodywork: prototype workshop
 Mock-ups: prototype workshop
 Assembly: prototype workshop
DPMI/DDSCR
logic
DESIGN MULES (MC)
 MCs are physical validation supports which replaces the PF-Lot

for a Mother vehicle (evolutions of an existing platform).
 Two body definitions as per the validation requirements
 Modifications of mass production body: requested project parts interfaces which are
representative comply with the geometry but not guaranteed in stiffness
• MC GMP DIM & DPC = GMP+ SMO + air inlet + cooling + carburetion + exhaust
+ associated electronic
• MC LAS = suspension + steering + braking
• MC ESP = LAS + ESP + powertrain evolution
 Proto Bodywork: representative in geometry and in stiffness
• MC Crash = Front/rear unit
 The supports are assembled with
 proto VE parts which are compliant with OPF TD
 Representativeness of the vehicle inertia is requested (ineria
process to be defined)
DPMI/DDSCR
logic
DESIGN MULES (MC)
Define, plan and Contractualise the MC batch
Tasks to be
Who provides What When By whom to DIPV ? To provide what To whom? When
completed
DIAM chief TD Launch of the DIPV IST Proto plan according to the
technical engineer Master schedule Expression of deparment
IPP requirements
CG Project Project engineering outlay RPSV guidelines DIPV IST Validated proto plan DGTa
ISV, ISP Proto plan to be optimised Participants: DIPV project budget CG
DIPV numbering Costing department / No. of powertrains DCRPM
cell DPC / DGTa / CG
DIPV CG Validated DIPV engineering IV / ISTs / ISVs /
outlay ISP / IST DCRPM
range
DIPV IST CR RPSV guidelines Pre Note Program DIPV IST Info about MC batch (no., IST Projet,
schedule, place of completion ISP,
Cellule planif. DIPV Programming committee etc) DCRPM
DIAM TCS MC definition DIPV definition cell MC forum sheet DIPV
DIPV IST PNP forum MTCs logistics
preparation
DIPV definition cell MTCs Definition freeze DIPV IST Circulation of batch MTCs for DIPV
top doc preparation logistics
engineer
IST DIPV + def cell PNP, Forum, capacitaire DIPV Macro- Schedule DIPV schedule cell Validated batch schedule
and DIPV schedule (customer release)
DICAP chief DICAP schedule
technical engineer DCRPM capacity
DCRPM
ISV, ISP Proto plan to be optimised RPSV Launch DIPV IST Launched proto plan DGTa
DIPV numbering Costing Participants: idem project budget CG
cell RPSV Cadrage Powertrain contract DCRPM
DIPV chief CR RPSV Launch Program note DIPV IST Batch contractualization Customers/
technical Forum, schedule, MTC, QFQ DIPV/DIESE
Definition cell/DIPV /DIAMnote
MC program
schedule Powertrain contract
DPMI/DDSCR
DCRPM
logic
DESIGN MULES (MC)
MC program note
Prepare and supply the MC batch
Who provides To
Who provides What When Tasks to be completed By whom to DIPV ? When
what whom?
DIPV chief technical Program note Launch of the MC batch DIPV / DIAM preparation
engineer completion engineers
Purchase Bodywork unique RTF1bodywork Bodywork engineer Supplier pre-approval on
PFEs list (Purchase, PFE, suppliers) delivery/price
Bodywork engineer
DICAP DT MC Bodywork composition Bodywork engineer List of parts/Required amount
DIPV chief technical DIPV IST in the batch
engineer
Bodywork engineer Order launch RTF2 bodywork Bodywork engineer 100% of the deadlines are
date (Purchase, PFE, suppliers) signed by the supplier
DIAM Top Doc OPF RTF1 assembly Bodywork engineer Supplier pre-approval on
DIPV chief technical NP MC (Purchase, PFE, suppliers) delivery/price
engineer Pre compo
Log DIPV supplier list
Purchase
DIAM Top Doc OPF Batch contractualization Prépa Montage List of parts/Required amount
DIPV chief technical NP MC in the batch
engineer Pre compo
Assembly engineer
Assembly engineer Order launch RTF1 assembly Bodywork engineer 100% of the deadlines DATE
are * MC
Peform and evaluate date the MC batch (Purchase, PFE, suppliers) signed by the supplier
To
Who provides What When Tasks to be completed By whom to DIPV ? To provide what When
whom?
DIPV metiers Bodywork top ABMC AQDM DIPV DIPV recommendation on DGTa
Assembly top ABMC
DIPV manufacturing CM Reception of MCs for MADC DIPV quality reception MC + PV of reception Custom
ers
DIPV chief technical Program note
Accepted SV
engineer
DPMI/DDSCR
logic
ENGINE TRYOUT VALIDATION MULE (MVMM)
 SCOPE
 Supports for powertrain validations
 Supports for DIESE
Vehicle project Technical Documentatio Star MADC 1st

typology Definition. n milestone date: vehicle Parts Responsibility
First Completion
industrialisation TD DOC contrat Prototype - DIPV
star date and MADC which cna be completed DIPV /in misunderstanding with guidelines
DPMI/DDSCR
logic
 MVMM are system validation supports

 The body is a mass production body which is modified based on
the design mule studies. The parts are prototypes.
 VE parts comply with the completion TD
 Powertrain parts: Only the parts in interface (number 14) comply with completion TD
 MVMMs for DCMAP replaces the loop 2 and 3 powertrain miles

and Slot DCMAP (no VC DCMAP)
  strong representative level of these mules in terms of electronics etc.
 MVMM for ESP tryout replaces the Slot DPC/DIESC of ESP tryout
  Vehicle inertia representativity request (introducing the inertia process in
progress)
DPMI/DDSCR
logic
Define, plan and Contractualise the MVMM batch
Tasks to be
completed
DIAM chief TD Launching the DIPV IST Proto plan according to
technical engineer Master schedule Expression of the deparment
IPP requirements
CG Project Project engineering RPSV Cadrage DIPV IST Validated proto plan DGTa
ISV, ISP outlay MVMM Participants: DIPV project budget CG
DIPV costing cell Proto plan to be department / DPC / No. of powertrains DCRPM
DIPV CG optimised DGTa / CG IV / ISTs /
Costing ISVs / ISP / DCRPM
range chief technical
Valiafted DIPV TEI engineer
DIPV chief CR RPSV Cadrage Pre Note Program DIPV chief technical Info about MC batch IST Projet,
technical engineer Programming committee MVMM engineer (no., schedule, place of ISP, DCRPM,
completion etc) …
DIPV schedule
celle
DIAM TCS MVMM definition DIPV definition cell MVMM forum sheet DIPV
DIPV IST PNP forum MTCs logistics
engineer
DIPV definition cell MTCs Definition gel DIPV chief technical Circulation of batch DIPV
engineer MTCs for top doc logistics
preparation engineer
IST DIPV + def cell PNP, Forum, capacitaire Macro- Schedule DIPV schedule cell Validated batch
and DIPV schedule DIPV schedule (customer
DICAP chief Planning DICAP release)
technical engineer Capacitaire DCRPM
DCRPM
ISV, ISP Proto plan to be RPSV launch MVMM DIPV chief technical Launched proto plan DGTa
DIPV costing cell optimised engineer project budget CG
Costing Participants: idem RPSV Powertrain contract DCRPM
guidelines MVMM program note
DIPV IST CR RPSV Launch MVMM program note DIPV chief technical Batch contractualization Customers/DI
DPMI/DDSCR
Definition cell/DIPV Forum, schedule, MTC, "Development" session engineer PV/DIESE/DI
schedule
logic QFQ AM
DCRPM DD/MM/YYY CONFIDENTIAL c
MVMM program note
Prepare and supply the MVMM batch
Who provides What When Tasks to be completed By whom to DIPV ? To provide what To whom? When
DIPV chief Program note Launch of the MVMM DIPV / DIAM preparation
technical engineer batch completion engineers
Purchase Bodywork unique list RTF1bodywork Bodywork engineer Supplier pre-approval on
PFEs (Purchase, PFE, delivery/price
Bodywork suppliers)
engineer
DICAP DT Cpl Bodywork composition Bodywork engineer List of part/Required
DIPV chief DIPV IST amount in the batch
technical engineer
Bodywork Order launch RTF2 bodywork Bodywork engineer 100% of the deadlines
engineer date (Purchase, PFE, are signed by the
suppliers) supplier
DIAM Top DOC Contract RTF1 assembly Bodywork engineer Supplier pre-approval on
DIPV chief NP MVMM (Purchase, PFE, delivery/price
technical engineer Pre compo suppliers)
Purchase
DIAM Top DOC Contract Batch Prépa Montage List of part/Required
DIPV chief NP MVMM contractualisation amount in the batch
technical engineer Pre compo
Assembly engineer
Assembly engineer Order launch RTF1 assembly Bodywork engineer 100% of the deadlines
date (Purchase, PFE, are signed by the
suppliers) supplier
Slide 11 : Prototype workhop completion =>
why is there no "Complete/Evaluate" part in
slide 2 and slide 14 ?
DPMI/DDSCR
logic
SYSTEM VALIDATION MULE SYSTEM (MVVS)
 SCOPE
 Vehicles for validations :
 SMO/Exhaust
 Perfo/conso test bench
 Chassis
 Diagnosis
 Braking tryout (VC risk)
 Clim acoustics heat (VC risk)
 Vehicles for validations :
 B3V mud/Clim
 Steer
Vehicle project Technical Documentatio MADC 1st
typology Definition. n milestone Date * vehicle Parts Responsability
IOD (off-tool
Mass parts)
First Completion production (except for
industrialisation TD Doc powertrain) - DIPV :
DPMI/DDSCR
logic
 MVVS are system validation supports which replaces some S-lot.
 The body is a mass production body which is modified based on

the design mule studies.
 Powertrain parts in interface (number 14) compliant with DT
Completion (prototype completion or IOD according to the
requirements)
 Mostly, 2 MVVS will be completed in VC to make use of this project body.
DPMI/DDSCR
logic
Define, plan and Contractualise the MC batch
Tasks to be
completed
DIAM chief TD Launching the DIPV IST Proto plan according to
technical engineer Master schedule Expression of the deparment
IPP requirements
CG Project Project TEI RPSV Cadrage MVVS DIPV chief technical Validated proto plan DGTa
ISV, ISP Proto plan to be engineer project budget CG
DIPV numbering optimised Participants: DIPV / No. of powertrains DCRPM
cell Costing DPC / DGTa / CG IV /
DIPV CG chief technical engineers
Valiafted DIPV TEI / ISVs / ISP / chief
technical engineer
department DCRPM
range
DIPV chief CR RPSV Cadrage Pre Note Program DIPV chief technical Info about MC batch chief
technical engineer MVVS MVVS engineer (no., schedule, place of technical
Programming committee completion etc) engineer
Cellule planif. DIPV Projet, ISP,
DCRPM,…
DIAM TCS MVMM definition DIPV definition cell Fichier forum MVVS DIPV logchief
DIPV chief PNP MVVS forum MTCs technical
technical engineer engineerics
preparation
DIPV definition cell MTCs Definition gel DIPV chief technical Circulation of batch DIPV logchief
engineer MTCs for top doc technical
preparation engineerics
preparation
chief technical PNP, Forum, capacitaire Macro- Schedule DIPV schedule cell Validated batch
engineer DIPV + DIPV schedule (customer
cellule Def et Planif Planning DICAP release)
DIPV Capacitaire DCRPM Note Programme MVVS
chief technical
engineer DICAP
DCRPM
DPMI/DDSCR
ISV, ISP Proto plan to be "Development"RPSV Lancement
session DIPV chief technical Lanuched proto plan DGTa
DIPV numbering
logic
optimised MVVS engineer project budget CG
cell Costing DD/MM/YYY CONFIDENTIAL c
Participants: idem RPSV Powertrain contract DCRPM
Cadrage
Note Programme MVVS
Prepare and supply the MC batch
Who provides What When Tasks to be completed By whom to DIPV ? To provide what To whom? When
DIPV chief Program note Launch of the MVMM batch DIPV / DIAM preparation
technical engineer completion engineers
Purchase Bodywork unique list RTF1bodywork Bodywork engineer Supplier pre-approval on
PFEs (Purchase, PFE, delivery/price
Bodywork suppliers)
engineer
DICAP DT Cpl Bodywork composition Bodywork engineer List of part/Required
DIPV chief DIPV chief technical amount in the batch
technical engineer engineer
Bodywork Order launch RTF2 bodywork Bodywork engineer 100% of the deadlines
engineer date (Purchase, PFE, are signed by the
suppliers) supplier
DIAM Top Doc Serie RTF1 assembly Bodywork engineer Supplier pre-approval on
DIPV chief NP MVVS (Purchase, PFE, delivery/price
technical engineer Pre compo suppliers)
Purchasing
DIAM Top Doc Serie Batch contractualisation Prépa Montage List of part/Required
DIPV chief NP MVMM amount in the batch
technical engineer Pre compo
Assembly engineer
Assembly engineer Order launch RTF1 assembly Bodywork engineer 100% of the deadlines
date (Purchase, PFE, are signed by the
Slide 15 : Prototype workhop completion =>suppliers) supplier
why is there no "Complete/Evaluate" part in

slide 2 and slide 18 ?
DPMI/DDSCR
logic
VEHICLE CHECK (VC)
 SCOPE
 Validate certain systems
 Evaluate and tryout the geometry and product process convergence of the vehicle
 Prepare the vehicle's entry in the plant

typology Definition. n milestone date: vehicle Parts Responsability
Mass - DIPV :
First Completion production Bodywork to be
industrialisation TD Doc IOD (off tool) defined
 Bodywork: body and sub-assemblies in the plant in the manufacturing capacity limit,
remaining to be in prototype workshop (to be defined)
DPMI/DDSCR
logic
VEHICLE CHECK (VC)
Which does not change/Slot :
 These are supports which are assembled with the IOD parts. Their maturity can
be compared with the one of Slot V1. They complete the disassociated supports
and the analysis loops
 They are subject to measurements and evaluation which will be used as

geometric and product process convergence: AVES static, perceived quality,
RCC, 1D and 3D measurements, monitoring plan
 They give a sufficient maturity level to the project for entry in the plant:
 Detecte, analyse, process the fittability problems
 Complete the drafting and implement the FOP and FOS
 Initiate the plant operator's training
DPMI/DDSCR
logic
VEHICLE CHECK (VC)
What changes/Slot :
 VC vehicles are not meant for synthesis validations No AVES dynamic. They
are a part of the system loop.
 VC vehicles contain only Brother or Child child powertrains resulting directly

from the powetrain plants. They are assembled with IOD parts.
 CMO units are assembled simultaneously with Mother engines which do not
function and the interface3s comply with DT completion
 Bodywork is completed in the plant alonwith a prototype workshop. Plant body

compliance is the responsibility of DICAP,the bodies and units produced by
DIPV under the responsibility of DIPV.
 All the results in VC are not expected for PT1 product tryout  implementation
of temporary solutions for PT1 if required
DPMI/DDSCR
 The number of supports

logic
is around 10 times lesser,
DD/MM/YYY c
the duration
CONFIDENTIAL of the batch
VEHICLE CHECK (VC)
Define, plan and Contractualise the VC batch
Tasks to be
completed
DIAM chief TD Launch of the DIPV chief technical Proto plan according to
technical engineer Master schedule Expression of engineer the deparment
IPP requirements
CG Project Project engineering RPSV Cadrage VC DIPV chief technical Validated proto plan DGTa, CG
ISV, ISP outlay engineer project budget
DIPV numbering Plan proto Participants: DIPV / No. of powertrains DCRPM
cell Costing DPC / DGTa / CG IV /
DIPV CG Valiafted DIPV chief technical engineers
engineering outlay / ISVs / ISP / chief
technical engineer
department DCRPM
range
DIPV chief CR RPSV1 VC VC Pre Note Program DIPV chief technical Info about MC batch Project chief
technical engineer engineer (no., schedule, place of technical
Programming committee completion etc) engineer,
DIPV schedule cell ISP, DCRPM
etc
DIAM TCS MVMM definition DIPV definition cell VC forum sheet DIPV
DIPV chief PNP VC forum MTCs logistics
technical engineer
DIPV definition cell MTCs Definition gel DIPV chief technical Circulation of batch DIPV
engineer MTCs for top doc logisitics
preparation
chief technical PNP, Forum, capacity Macro- Schedule DIPV schedule cell Validated batch
engineer DIPV + DIPV schedule (customer
Def cell and DIPV release)
schedule DICAP schedule
chief technical DCRPM capacity
engineer DICAP
DCRPM
ISV, ISP Proto plan to be RPSV Lancement VC DIPV chief technical Launched proto plan DGTa
DIPV numbering optimised engineer project budget CG
DPMI/DDSCR
cellProcess and development
Costing "Development" session Participants: idem RPSV Powertrain contract DCRPM
logic Cadrage
DIPV chief CR RPSV Launch VC program note DIPV chief technical Batch contractualization Customers/
GEOM VEHICLE CHECK (Geom VC)
DPMI/DDSCR
logic
GEOM VEHICLE CHECK (Geom VC)
Define, plan and Contractualize the VC batch

Tasks to be
completed
DPMI/DDSCR
logic
GEOM PLANT TRIAL 1 (Geom PT1)
DPMI/DDSCR
logic
GEOM PLANT TRIAL 1 (Geom PT1)
Define, plan and Contractualize the VC batch

Tasks to be
completed
DPMI/DDSCR
logic
PLANT TRIAL 1 (PT1)
 SCOPE
 Validate the requirements and inter-systems
 Monitor the geometry and product process convergence tryout

typology Definition. n milestone date: vehicle Parts Responsability
Off tool and Plant except for CUK
Completion grained at the end management and DIPV
Any project TD Doc Série of PT1 vehicle transport
 Number of DGAIQ supports
 Vehicles in the plant, CUK to be defined
DPMI/DDSCR
logic
PLANT TRIAL 1 (PT1)
Define, plan and Contractualize the MC batch

Tasks to be
completed
DPMI/DDSCR
logic
PLANT TRIAL 2 (PT1)
 SCOPE
 Confirm the requirements and inter-system validations
 Complete the geometry and product process convergence tryout
Vehicle project Technical Documentati MADC 1st

typology Definition on milestone Star date vehicle Parts Responsibility
Plant except for DIPV
Completion Grained Off tool vehicle transport
Any project TD Doc Série off process management
 Number of DGAIQ supports
 Production place: Plant
DPMI/DDSCR
logic
PLANT TRIAL 2 (PT1)
Define, plan and Contractualize the MC batch

Tasks to be
completed
DPMI/DDSCR
logic
Tools
Control the design quality
X
??
DPMI/DDSCR
logic
Direction des Méthodes d’Ingénierie
Design and validate parts in the development phase

Design Quality Control
DPMI/DDSCR
logic
Methods and Tools
 At VPC, the feasibility of selected Technical Solution (TS) has
been demonstrated for the envelope defined by the project.
 From VPC to CY: this TS will be implemented in the project:
 If the TS is renewed as is or with minor modifications (DAISI level 1 or 2):
 Technical Dept.'s rules are applied,
 The design is based on preexisting documents specifying the TS: Technical Functional
Analysis, technical drawings, chains of dimensions, FMEA ...
 If the TS is innovative (DAISI level 3 or more):
 The design is based on Technical Functional Analysis, design, dimensioning, dependability
analyses (Preliminary Risk Analysis, Failure Tree, FMEA ...)… performed during the
Optimization Phase.
 The arbitrations at VPC are handled.
 Action plans for cleaning of risks decided during the optimization phase as well as
the Validation Plan continue according to schedule.
 The "tuning parameters" and the characteristics of the TS are finely suited to the
specificities and constraints of the project, within the working condition limits of the
TS.
 The industrial feasibility of the characteristics of the parts is finely validated (HCPP
procedure).
DPMI/DDSCR
logic
Methods and Tools
 After CY et before TGA :

 Design activities must be limited to "fine tuning"
 Technical Functional Analysis, chains of dimensions, FMEA (particularly Design

FMEA), HCPP are updated according to the adjustments made on the project.
 Functional dimensioning complying with the GPS ISO standards is finalized on the
drawings.
 Based on the validation results obtained during this phase, the necessary corrections
are performed in the design of the TS
DPMI/DDSCR
logic
Methodological Support and Training:
B. COMPIN +33 1 76 83 44 14 Expert Leader SGP (General Product Safety) – SDF (Dependability Analysis)
L. CAQUEZ +33 1 76 83 44 14 Dependability Analysis Specialist
L. DIDIEZ +33 1 76 85 28 49 Head of Transverse Design Methods Department
L. VERDIN +33 1 76 85 69 82 CTL Parts Characterisation Process
A. LECUYER +33 1 76 85 83 70 CTL Conformity Insurance
M. DAVIDOU +33 1 76 85 03 56 CTL Measurement Process
Find our design methods and tools in the SCR gate
 Type “SCR” in the search

engine in DECLIC
 Or use this link:
http://ing.sharepoint.renault.fr/
en/sxrpages/homepage.aspx
DPMI/DDSCR
logic
Tools
Manage the externally worked parts by the ANPQP
X
??
DPMI/DDSCR
logic
 IN THE PROCESS OF DRAFTING
DPMI/DDSCR
logic
Regulation/certification
X
Regulation leader
DPMI/DDSCR
logic
Guarantee regulatory compliance of vehicles in design and in production (O25
DRTH manager
unifying process) Metier manager
Steps: Certification and production compliance regulation Project
manager
AUTHORITIES
Regulation/country Vehicle certification
(Registration condition)
Text
Text
Checking by the authorities for complaince
Text of vehicle/regulations
NER of the country of sales with COP,IC device
DRTH DRTH
R
Identification of Checking compliance of
R
regulatory characteristics R characteristics R
Validation of R characteristics
by country of
marketing. (DER*, GSCR**) internally and
based on and in the supplier's premises
RRSH*** IST opinion in the milestones (including certified parts
AQDM approval)
PFE
R
Integration of R characteristics in
the technical standards Application of standards R
product-process, bid and therefore R characteristics

files (specifications, plans etc,) internally and in the supplier's
premises
including COp monitoring
Upstream engineering PFE
* DPMI/DDSCR
Statement of regulatory requirements"Development" session
**logic
Regulatory compliance monitoring grid
*** Regulation-safety-certification managers
Vehicle Pre Tooling Go

Contract (C)
Contract (VPC) Ahead
Spe1 Spe2 Spe3
Define the certification strategy

and create the certification schedule for the contract
NOTE : certification activity takes place mainly between ABPT1 and PPC.
Freeze the certification schedule, number of SE (test supports) and CTD

(Certification Test Deadline – old BFEH) for Europe and internationally (functiona of the
communicated country of sales)
DPMI/DDSCR
logic
Define the certification strategy

DGTa
and create the certification schedule for the contract
When : in Contract
Why, for whom : for
 freeze the number of test supports to be provided to DRTH-certification, to certify all
the vehicle version in europe and internationally
 freeze the certification schedule:
 delivery of test supports in certification activity launch in ABPT1,
delivery of certification file elements to be provided to DRTH at the earliest to
CTD (old BEH).
How : based on the list of :

 country of sales communicated and the project schedule
 bodies/powertrains and confirmed technical definition
 future partners and cross-badging (not concerned a priori X87)
DPMI/DDSCR
logic
Industrial system
Industrial facilities
X
IST Process
DPMI/DDSCR
logic

Contract (VPC) (CO) Ahead (TGA)
GW1 DFO
Validate the process feasibility
Tooling study
Contract file Completion

launch
Progress in CPI and CPI

- Complete the detailed tooling studies
DPMI/DDSCR
logic
Validate the process feasibility CAMI
 Write and validate the DFPP

 Approval in geometric feasibility
 Process approval
CAMI
Tooling study Process chief technical
engineer
 ATFE (End of study technical approval)
Study monitoring Process dashboard
CAMI
Completion launch Process chief technical
engineer
 DFO = Num Consistency
 Ki solution monitoring
 Completion monitoring  Process dashboard
DPMI/DDSCR
logic
Contract file IST Process
 Refer to "Vehicle contract" standard file
CPI ISTA Process
 Request for progress in CPI for

previous activities in the contract
 Draft and ensure CPI signature
DPMI/DDSCR
logic
Industrial system
Industrial facilities
X
IST Process
DPMI/DDSCR
logic

Contract (VPC) (CO) Ahead (TGA)
CAMI
Drafting and delivery of FOP for VC assembly !
Preparation engineer
! CAMI
Drafting and signature of CPI !
Preparation engineer

- Ensure Product/Process convergence for robust TGA clearing
- Preparation of VC completion
DPMI/DDSCR
logic
What is a FOP and a FOS?
FOP is A support which enables VE for specifying the technical expectations

of our process to the manufacturer:
 Process to be carried-out (screwing, clipping etc)
 Technical data: Torque and tightening grade etc.
 Assembly recommendations (order of tightening, some important technical rules, "OFF
THE ROAD VEHICLE " alerts.
 All the CSR characteristics.
It is important to agree upon the product specifications before

circulating the FOPs to the manufacturer: Each PFE must sign the
FOPs in his scope (RT GFE expectation before DL Completion)
E-Learning « Assembly FOP viewing» n° 33696 : Tout savoir sur les FOP en 30 minutes !
Go to SYFORM http://lft.intra.renault.fr/lft/jsp/public/login.jsp then search for "FOP"
DPMI/DDSCR
logic
Different FOP zones
DRAWING
enables transfer of an information which is clear and Specifications

illustrative at the first sight and which can be
understood by all whatever be the language or the and
person's qualification. Maximum information must be
sent in this zone. Notes
"Not contractual" image
Buffers
DPMI/DDSCR
logic
FOP management
CONFIDENTIAL c
DD/MM/YYY
FOP Pictogram
New FOPs of the new projects are "illustrated":
Verb+part
Name of the parts
A pictogram (operations and quality points)
A block (the last FOP is a double circled)
DPMI/DDSCR
logic
Pitogram dictionary
Liste des principaux pictogrammes pour FOP avec nombre de notes induites.
Le fabricant doit s'assurer que les notes induites aux pictogrammes se retrouvent dans la FOS sous forme de point clé.
Opérations Opérations Notes
Nb notes Nb notes Nb notes
Référence Transcription Pictogramme Référence Transcription Pictogramme Référence Transcription Pictogramme
induites induites induites
Visser Devisser Serrage

Op1 Op19 At1
Screw Unscrew Screw specification
0 0 1
Prévisser Regler Clic

Op2 Op20 At2
Pre-screw Adjust Click
1 1 1
Aligner Pression
Op3 Clipser Op21 At3
Align Pressure
0 0 1
Riveter Zipper T°
Op4 Op22 At4
Revet Scan Temperature
2 0 1
Serrer un collier Décoller Temps

Op5 Op23 At5
Tight a clamp Unstick Time
1 0 1
Emmancher /
A dictionary for each pictogram

Vérifier / Voir Outil spécifique
Op6 Raccorder Op24 Mo1
Check / Watch Specified tool
Connect pipe 1 0 1
Enfiler Couper Consommable

Op7 Op25 Mo2
Pass through Cut Consumable
4 1 1
Symétrie de
Connecter Tourner
Op8 Op26 LO1 l'opération
Connect Turn
1 0 Symmetry
Risque de panne
Verrouiller Jeter
Op9 Op27 AL1 Immobilisante
Lock Throw away
1 0 Break done 1
Lisser Prendre
Op10 Op28 AL2 CSR
Smooth Hold
0 0
Attention note associée
Chausser Notes
Op11 AL3 Pay attention quality
Fit a joint note
3
Respecter l'ordre
Produit chimique
Positionner spécifié
Op12 No1 1 2 3… AL4 dangereux
Locate Follow mounting
Dangerous chemical
0 order 1
Raccordement
Indexer Tirer - pousser
Op13 No2 de cosses AL5
Index Check connexion
1 Joining lugs 3 2
Même opérateur
Activer
Op14 No3 Same operator or
Operation pictos
Wipe work place
2 1
Connecter un
Coller
Op15 No4 connecteur à
Stick
3 levier 3
Connecter un
Enlever
Op16 No5 connecteur à
Take away
0 étrier 2
Op17
Remplir
Fill in
3
No6
Connecter un
connecteur Squib
2
Pictos notes
Graisser / Huiler Propreté
Op18 No7
Lubricate Cleanness
0 4
DPMI/DDSCR
logic
DRAWING ZONE – buffers
Specification buffers:
Tightening
Informations only from SIGNE
I.T. M grade
 Tighetening torques must be declared in
Nominal : 21 N.m
SIGNE
Monitoring method: SM VIS 000
Consumable Specific tool:

Name L. FREIN TY4 Nom PINCE COLLIER
Ref R100239476 Ref R100237676
Quantity 600 M Monitoring method:
Monitoring method SM REM 300
Informations from SACIM
Informations fromSIGNE and/or from
SACIM
Note, no automatic update if SIGNE/SACIM is modified
DPMI/DDSCR
logic
Clearance from FOP to FOS
Operating mode is not
in FOP
It is in the
manufacturer's FOS
DPMI/DDSCR
logic

02.seance LDP DEVELOPPEMENT V3P - ENV1

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

02.seance LDP DEVELOPPEMENT V3P - ENV1

Uploaded by

Copyright:

Available Formats

XX PROJECT

"Development" information session

Kick-Off Concept Vehicle Pre- Tooling Go Manufacturing

GUIDELINES OPTIMISATON DEVELOPMENT INDUSTRIALISATION

 4 information sessions co-ordinated by the CVEa preparing

Confirm the Master schedule IPP

Co-ordinate the lead-time IPP

Vehicle Pre Contract Tooling Go

Synchro Consistency Completion

Quality milestone convergence ( IAQ)

Animation of the risk control on the perimeter CVE( IQP)

Project dashboard (including synthesis LUP PRO)( IQP)

CO/TGA quality milestone convergence Quality assurance engineer

 Co-ordination of JQPV convergence for quality milestones (GW1, GW2, VPC)

Technical synchronisation milestone convergence Project quality engineer

Level 1 Milestones : GW1E VPC Contract Launching Life

Level 4 Milestones: AB DLot Cy AB EIPFC

Synchro Consistency Completion

Diffusion Recensement des Réduction des

Animation Qualité Projet sur périmètre DGT IQP

Plans d'actions Jalons précédents r 3 plans d'actions sans solution R V O V O V R V

Synchro Consistency Completion

Gestion des maitrises des risques IAQ [Atelier 3 et 4 à planifier]

Pre- Concept VPC Launching Life

GW1 SOS Cycle

Revues Qualité assurent la liaison entre

> Mise à jour des risques DAISI et avancement des

Purpose Overall result

1. Product scenario is contractual

Purpose Overall result

Confirm that the definition level

 Technical definition is feasible

Purpose Overall result

1. Development phase is regulated by Synchro, Consistency (Cy) and Completion (Cp)

2. It ends in architecture freeze in TGA which marks the end of design

Vehicle Pre Cost contract Tooling Go

Synchro Consistency Completion

Digitally converge with Digital-Lot

Physical design with PMDR

Shared milestone process (V3P)

Freeze the architecture !

Approval to Built Digital Lot

Purchase/ DCV Evaluation

Synchro milestone objectives

Objective and definition of Digital Lot Cy Engineer

Design requirements product Process convergence in CAMI

 Digital mock-up is formalized

Objective and definition of Digital Lot Proposal Engineer

Design requirements product Process convergence in CAMI

 Digital mock-up is formalized

RO part archi approval of the engineer contractualizes

Parts digitisation consistency with its environement in digital:

Parts digitisation consistency with its environment in physical:

"Make a fil rouge archi approval"

1. An expectation in each milestone in a unique format is initialised in FC:

4. Management according to the architecture zone:

V3P milestone Milestone expectations

The list of kits in V1 V2 AVES "PPC" and forecated reccurrent problems

Synchro "PPC" kits are decided

Vehicle Pre Cost contract Tooling Go

GW1 DRVh Synchro Cy DRCp Cp

Carry-out the interior and exterior