> Syntax independent - MCIs - Messages > Details
SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
|
> Syntax independent - MCIs - Messages > Details
|
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : EVTROD001 - - (Evénement - objet de risque - données véhicule)-
- Approved
, and is part of release 201501
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) |
Sender : Any
Receiver : Any
Status : 2 - Version : 1
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
||
Indicator |
Identifier |
Version |
|||||
| 10 |
Risk object - type : véhicule automoteur
|
No
|
-
|
-
|
Mand.
|
||
| 20 |
Risk object véhicule - Instance ID at insurer
|
No
|
-
|
-
|
Option.
|
||
| 30 |
Risk object véhicule - Instance ID at intermediary
|
No
|
-
|
-
|
Option.
|
||
| 40 |
Risk object véhicule - Marque / modèle / type
|
No
|
-
|
-
|
Option.
|
||
| 50 |
Risk object véhicule - Numéro plaque d'immatriculation
|
No
|
-
|
-
|
Option.
|
||
| 60 |
Risk object véhicule - Numéro de chassis
|
No
|
-
|
-
|
Option.
|
||
| 70 |
Risk object véhicule - Type de véhicule codification DIV
|
Yes
|
6
|
Option.
|
|||
| 80 |
Risk object véhicule - Usage du véhicule
|
Yes
|
6
|
Option.
|
|||
| 90 |
Risk object véhicule - Type de valeur couverte (véhicule)
|
Yes
|
5
|
Option.
|
|||
| 100 |
Risk object véhicule - Financement
|
No
|
-
|
-
|
Option.
|
||
| 110 |
Risk object véhicule - Valeur catalogue hors TVA
|
No
|
-
|
-
|
Option.
|
||
| 120 |
Risk object véhicule - Valeur assurée (compagnie)
|
No
|
-
|
-
|
Option.
|
||
| 130 |
Risk object véhicule - Conducteur
|
No
|
-
|
-
|
Option.
|
||
| 140 |
Risk object véhicule - Conducteur - Identifiant chez l'assureur
|
No
|
-
|
-
|
Option.
|
||
| 150 |
Risk object véhicule - Conducteur - Identifiant chez l'intermédiaire
|
No
|
-
|
-
|
Option.
|
||
| 160 |
Risk object véhicule - Conducteur - Nom officiel
|
No
|
-
|
-
|
Mand.
|
||
| 170 |
Risk object véhicule - Conducteur - Adresse
|
No
|
-
|
-
|
Option.
|
||
| 180 |
Risk object véhicule - Conducteur - Date de naissance
|
No
|
-
|
-
|
Option.
|
||
| 190 |
Risk object véhicule - Conducteur - Alcootest effectué
|
No
|
-
|
-
|
Option.
|
||
| 200 |
Risk object véhicule - Guarantee
|
No
|
-
|
-
|
Mand.
|
Multiple presencies possible
|
|
| 210 |
Risk object véhicule - Guarantee - Montant franchise
|
No
|
-
|
-
|
Option.
|
||
| 220 |
Risk object véhicule - Guarantee - Cover
|
No
|
-
|
-
|
Option.
|
Multiple presencies possible
|
|
(*) n u d : new / updated / deleted since previous version.
(*bis) u : updated : this can be a codelist-version incrementing.
Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...
(**) Usage: The indications Mandatory / Conditional / Optional are to be understood in respect of the actual level of the Data element:
example given; some party data-set as a whole can be optional, while, if present, the party's name within that party data-set can be mandatory.
Remark: in UN/Edifact, "Mandatory / Conditional" are notions used within the standard.
And within edi-guides (a refinement of a standard) the "Conditional" can become "Required / Optional / Dependent / Advised / Not used".
Ideally we should implement the same ideas.