Académique Documents
Professionnel Documents
Culture Documents
CONFIDENT
REFERENCE IND DATE
IALITE
SOFTWARE REQUIREMENT NOTEBOOK
USAGE
DAE CMP 01552_14_01306 8.0 30/06/2017
INTERNE
CE DOCUMENT EST LA PROPRIETE DU GROUPE PSA PEUGEOT CITROEN ET NE PEUT ETRE REPRODUIT OU COMMUNIQUE SANS SON AUTORISATION
1 SCOPE OF APPLICATION
1.1 DEVELOPMENT CONTEXT
The EPS Software is expected to be used for multiple vehicles on the CMP plate-form.
Deliveries Date:
- SW Level 3: 19/02/2017
- SW Injection Fault 19/04/2017
2 MENTIONED DOCUMENTS
2.1 REFERENCE DOCUMENTS
The documents listed below helped elaborating the present one. They are not communicated
systematically.
Lien Title Reference Date Diffusion
3.2 ACRONYMS
Abréviation Signification
ACCP Advanced Common Rail Combustion Process
AD A Définir
ADC Anti Démarrage Codé
APC APrès Contact
API Application Programm Interface
APV APrès-Vente
MCD pour Measurement, Calibration and Diagnostics
ASAM-MCD 1MC ou - ASAP 1 relève du protocole
ASAP 1
- ASAP 2 relève du format de description des données. ex : fichier A2L
ASAM-MCD 2MC ou
- ASAP 3 relève d’une interface logicielle.
ASAP 2
ASAM-MCD 3MC ou
ASAP 3
AQMPP Assurance Qualité par la Maîtrise du Produit et du Processus
BSI Boîtier de Servitude Intelligent
CAN Controller Area Network
CCP Can Calibration Protocol : protocole de calibration utilisant le bus CAN
comme vecteur de transmission
CDC Cahier Des Charges
CMM Contrôle Moteur Multifonction
CPPR Clauses Particulières et Planning de Résultat
CRCPP Can Rapid Control Prototyping Protocol. Protocole de communication basé
sur le CCP pour bypass développé par Ford.
CPU Central Processing Unit
CRQ Change Request (demande d’évolution)
DMS DéMarrage Série
E/S Entrées / Sorties
ECCS Extreme Conventional Combustion System
ECU Electronic Control Unit
EOBD European On Board Diagnostic
ETK Emulator TastKopf (ETAS) : interface de mesure/calibration et prototypage
rapide de la société ETAS.
Abbreviation Meaning
ADC Immobilizer
API Application Program Interface
AQMPP PSA quality assurance methodology in the development phase (Assurance
Qualité par la Maîtrise du Produit et du Processus)
CAN Controller Area Network
CDC Specification notebook (Cahier Des Charges)
CMM Engine Control Unit (Contrôle Moteur Multifonction)
CMQ Quality Management Clauses
CPU Central Processing Unit
CRQ Change Request
DMS SOP (DéMarrage Série)
I/O Input/Output
ECU Electronic Control Unit
GAP Smart Alternator management (Gestion d'Alternateur Piloté)
HW HardWare
MPO Mule vehicle (Mulet Porte Organe)
PRSEL PRototype Série En Ligne
PRSHL PRototype Série Hors Ligne
SOP Start Of Production
SRU First functionally representative prototype (Stade Représentatif Unique)
TBD To Be Defined
AZ Authentication Zone
IZ Identification Zone
The applicable specifications list that is communicated in this chapter is contractual. Each
applicable document must be seen as a requirement.
DOCUMENT REFERENCE
DOCUMENT TITLE VC2
(DOCINFO)
EPS BMPV Software Requirement Notebook - CDC SW 01552_14_01306 7.0
[801] RIF_Supplier_View
The software shall be designed to have the possibility to add new functionalities or to tune its
parameters before & after the first DMS.
GEN_SW-ORG_CDC_5.2_20 (1.1)
PSA diagnostic tools should be able to read the CPU load rate computed over 1 second
/GEN_SW-ORG_CDC_5.2_20
GEN_SW-ORG_CDC_5.2_40 (1.1)
For the functional content described in §5.1, the first SOP software shall not use more than
70 % CPU load.
/GEN_SW-ORG_CDC_5.2_40
GEN_SW-ORG_CDC_5.2_50 (1.1)
For any product phase (development, serial production, maintenance), the maximum CPU
load used by any software delivered to PSA shall not be above 90 %.
/GEN_SW-ORG_CDC_5.2_50
GEN_SW-ORG_CDC_5.2_112 (2.2)
For the first SOP and for the functional content that is described in §5.1, the software shall
not use more than 70 % of the RAM memory.
/GEN_SW-ORG_CDC_5.2_112
GEN_SW-ORG_CDC_5.2_113 (2.2)
The software shall never use more than 95% of ECU RAM in any phase of the product life
(development, production, maintenance).
/GEN_SW-ORG_CDC_5.2_113
GEN_SW-ORG_CDC_5.2_115 (2.2)
The software shall never use more than 95% of ECU NVM in any phase of the product life
(development, production, maintenance).
/GEN_SW-ORG_CDC_5.2_115
GEN_SW-ORG_CDC_5.2_116 (2.1)
The software shall not use more than 70% of ECU ROM at first DMS, for the overall
functional content described in §5.1.
/GEN_SW-ORG_CDC_5.2_116
GEN_SW-ORG_CDC_5.2_117 (2.2)
The software shall never use more than 95% of ECU ROM in any phase of the product life
(development, production, maintenance).
/GEN_SW-ORG_CDC_5.2_117
The EPS must also ensure some vehicle functions allocated on several calculators.
Overview without Angle Sensor (AVA function) or with CAV Virtual (Optional):
4.3.2.1 Protocols
The requirements related to communication are expressed in the list of functional
specifications available in §5.1.
GEN_SW-ORG_CDC_5.3_05 (1.1)
Removed
/GEN_SW-ORG_CDC_5.3_05
4.3.3.2 K line
GEN_SW-ORG_CDC_5.3_10 (1.1)
Removed
/GEN_SW-ORG_CDC_5.3_10
GEN_SW-ORG_CDC_5.3_20 (1.1)
Removed
/GEN_SW-ORG_CDC_5.3_20
4.3.3.3 Protocols
The requirements concerning communication protocols are described in the functional
specifications (see §5.1).
EPS_1V5_SW-ORG_CDC_5.4_10 (1.0)
The PSA download procedure should be used from the beginning of the program.
If not, the supplier must provide the downloading procedure (scenario, tool, Guideline,).
The procedure must be approved by PSA.
/EPS_1V5_SW-ORG_CDC _5.4_10
EPS_1V5_SW-ORG_CDC_5.4_20 (1.0)
In its offer, the supplier will suggest its scenario. The scenario must be approved by PSA.
/EPS_1V5_SW-ORG_CDC _5.4_20
The “customer use” phase, where the software is used within vehicles by Peugeot or Citroën
customers.
The after-sales phase, where the software is diagnosed and updated.
The software phases (boot, wake-up, download, diagnostics…) are described in § 5.1.
4.4.3 Ergonomics
Sans objet / Not applicable
GEN_SW-ORG_CDC_5.4_30 (1.1)
Transferred to CPPR...
/GEN_SW-ORG_CDC_5.4_30
GEN_SW-ORG_CDC_5.5_50 (1.1)
Removed. /
/GEN_SW-ORG_CDC_5.5_50
EPS_1V5_ORG_CDC_5.5_20 (1.0)
The Supplier must communicate its Autosar ICC level conformity, if used for its software
architecture.
/EPS_1V5_SW-ORG_CDC_5.5_20
EPS_1V5_SW-ORG_CDC_5.5_30 (1.0)
The supplier must deliver unique software compatible with all the program applications.
/EPS_1V5_SW-ORG_CDC_5.5_30
EPS_1V5_SW-ORG_CDC_5.5_40 (1.0)
The supplier will present its strategy for the software diversity to be compatible with all the
applications. (Compilation, End of Line configuration, calibration, Variant coding, others.).
/EPS_1V5_SW-ORG_CDC_5.5_40
EPS_1V5_SW-ORG_CDC_5.5_50 (1.0)
The supplier must identify all the HW-SW interactions impacted by the diversity.
/EPS_1V5_SW-ORG_CDC_5.5_50
EPS_1V5_SW-ORG_CDC_5.5_70 (1.0)
For each function, the supplier delivers the modular decomposition (Invariant and variant
parts).
Invariant part: Not impacted by the vehicle diversity.
Variant part: Parameters/strategies to adapt the software for the Vehicle applications.
/EPS_1V5_SW-ORG_CDC_5.5_70
EPS_1V5_SW-ORG_CDC_5.5_80 (1.0)
For each function, the supplier indicates its maturity.
/EPS_1V5_SW-ORG_CDC_5.5_80
EPS_1V5_SW-ORG_CDC_5.5_90 (1.0)
The supplier should privilege the parameters calibration by variant coding and/or
downloading to support the applications diversity.
/EPS_1V5_SW-ORG_CDC_5.5_90
EPS_1V5_SW-ORG_CDC_5.5_100 (1.0)
The supplier delivers the list of all the function calibration parameters. The list must be
approved by PSA for each function. (Refer also to [007])
/EPS_1V5_SW-ORG_CDC_5.5_100
GEN_SW-ORG_CDC_5.5_180 (1.1)
To generate the software release, the supplier shall only use the coding tools and languages
described in the development plan.
/GEN_SW-ORG_CDC_5.5_180
GEN_SW-ORG_CDC_5.5_340 (1.1)
Each calibration parameter has to be set in priority:
- either to a specific value communicated by PSA project team,
- or to a failure value indicated in PSA specifications, if no specific value has been
indicated.
/GEN_SW-ORG_CDC_5.5_340
GEN_SW-ORG_CDC_5.5_370 (1.1)
NA
/GEN_SW-ORG_CDC_5.5_370
GEN_SW-ORG_CDC_5.5_380 (1.1)
With each software version, the supplier has to deliver generic software with a calibration
that allows testing the new implemented functions.
/GEN_SW-ORG_CDC_5.5_380
EPS_1V5_SW-ORG_CDC_5.5_310 (1.0)
During development phase, all the tuning parameters shall be tunable.
The tuning parameters are indicated within specifications.
/EPS_1V5_SW-ORG_CDC_5.5_310
EPS_1V5_SW-ORG_CDC_5.5_320 (1.0)
The Software/Calibration parameters mapping must be approved by PSA at each software
freeze review.
The list of all calibration parameters must be shared at each freeze review and must respect
the requirement GEN-SWORG-CPPR.701 (1.0) in CPPR [007].
/EPS_1V5_SW-ORG_CDC_5.5_320
EPS_1V5_SW-ORG_CDC_5.5_340 (1.0)
The Tuning methods and tools are suggested by the supplier and must be approved by PSA.
The Tuning method shouldn’t change during all the project life. Any modification must be
approved by PSA.
/EPS_1V5_SW-ORG_CDC_5.5_340
EPS_1V5_SW-ORG_CDC_5.5_350 (1.0)
The Tuning methods and tools must permit to memorize the tuned values in the ECU
memory and to generate a parameter file readable by PSA tools.
PSA should be able to memorize the value following a tool request or by an action on APC
signal.
/EPS_1V5_SW-ORG_CDC_5.5_350
EPS_1V5_SW-ORG_CDC_5.5_360 (1.0)
The supplier shall deliver the calibration methods for the functions under its responsibility
in order to identify the constraints on PSA (planning, Deliverable, Impact on PSA functions
and parameters
/EPS_1V5_SW-ORG_CDC_5.5_360
EPS_1V5_SW-ORG_CDC_5.5_370 (1.0)
During the tuning phase, PSA should be able to read the PSA data values in the EPS
memory using the Tuning tool.
/EPS_1V5_SW-ORG_CDC_5.5_370
GEN_SW-ORG_CDC_5.5_400 (1.1)
The Generic software shall be identified by the supplier with a unique reference.
/GEN_SW-ORG_CDC_5.5_400
GEN_SW-ORG_CDC_5.5_410 (1.1)
The unique reference of the generic software shall appear on/with the delivery.
/GEN_SW-ORG_CDC_5.5_410
GEN_SW-ORG_CDC_5.5_450 (1.1)
Master software and calibration has to be identified using the reference communicated to
the supplier via an officialisation sheet.
/GEN_SW-ORG_CDC_5.5_450
GEN_SW-ORG_CDC_5.5_460 (1.1)
The unique reference of the master software shall appear on/with the delivery.
/GEN_SW-ORG_CDC_5.5_460
GEN_SW-ORG_CDC_5.5_440 (1.1)
Code UCE to use in the S0 frame of the .ULP/CAL files.
/GEN_SW-ORG_CDC_5.5_440
Part number
#3 #4 #5 #06 #7 (= equipment ref. number $xx$xx$xx$xx$xx B.C.D Part number
including HW+Boot)
$XX XX
#17 #18 Indice d’évolution des calibrations $xx $xx HEXA
(CAL Nexteer TBD)
GEN_SW-ORG_CDC_5.5_590 (1.1)
Each requirement of each supplier specification shall be identified by a unique reference.
/GEN_SW-ORG_CDC_5.5_590
GEN_SW-ORG_CDC_5.5_730 (1.1)
If the software is delivered via email, it is mandatory to deliver it also on a physical
support, to be defined together with the supplier and PSA project during RFQ phase.
/GEN_SW-ORG_CDC_5.5_730
GEN_SW-ORG_CDC_5.5_750 (1.1)
Removed
/GEN_SW-ORG_CDC_5.5_750
EPS_1V5_SW-ORG_CDC_5.5.760 (1.1)
The generic and Master software file must have the “.ULP” format (defined in [301] [302])
It must be possible to download the “.ULP” by using the PSA plant and After-sale tools.
/EPS_1V5_SW-ORG_CDC_5.5.760
4.5.10 Planning
GEN_SW-ORG_CDC_5.5_810 (1.1)
The software development shall be consistent with the overall project schedule, which major
milestones are given in the document “Special Clauses and Results Schedule”.
/GEN_SW-ORG_CDC_5.5_810