> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : EVTROD010 - - (Evénement - objet de risque - données bâtiment)
- Approved , and is part of release 201501 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
Version : 1
Status : 2
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2-UN/EDIFACT representation (including comments)
Indicator
Identifier
Version
10  
Risk object - type : bâtiment
No
-
-
Mand.
 
ROD+010 
20  
Risk object bâtiment - Instance ID at insurer
No
-
-
Option.
 
ROD+010+x--x:002 
30  
Risk object bâtiment - Instance ID at intermediary
No
-
-
Option.
 
ROD+010++x--x:003 
40  
Risk object bâtiment - Situation du risque est adresse du preneur
Yes
1
Option.
 
ROD+010 - GIS+3011+x--x 
50  
Risk object bâtiment - Situation du risque
No
-
-
Option.
 
ROD+010 - ADR+001+x--x:x--x:x--x::x--x:x--x:x--x+x--x+x--x+x--x+x--x 
60  
Risk object bâtiment - Usage de l'immeuble
Yes
3
Option.
 
ROD+010 - ATT+3100+x--x 
70  
Risk object bâtiment - Qualité du preneur d'assurance
Yes
5
Option.
 
ROD+010 - ATT+3110+x--x 
80  
Risk object bâtiment - Description de l'usage du risque assuré
No
-
-
Option.
 
ROD+010 - FTX+008+x--x:x--x:x--x:x--x:x--x 
90  
Risk object bâtiment - Créancier
No
-
-
Option.
 
ROD+010 - PTY+001 
100  
Risk object bâtiment - Créancier - Identifiant chez l'assureur
No
-
-
Option.
 
ROD+010 - PTY+001+x--x:002 
110  
Risk object bâtiment - Créancier - Identifiant chez l'intermédiaire
No
-
-
Option.
 
ROD+010 - PTY+001++x--x:003 
120  
Risk object bâtiment - Créancier - Nom officiel
No
-
-
Mand.
 
ROD+010 - PTY+001 - NME+001+x--x::::x--x 
130  
Risk object bâtiment - Créancier - Type de créancier
Yes
1
Option.
 
ROD+010 - PTY+001 - ATT+3130+x--x 
140  
Risk object bâtiment - Guarantee
No
-
-
Mand.
Multiple presencies possible 
ROD+010 - ICD+xxx 
150  
Risk object bâtiment - Guarantee - Montant franchise
No
-
-
Option.
 
ROD+010 - ICD+xxx - MOA+033:9--9:EUR:2 
160  
Risk object bâtiment - Guarantee - Cover
No
-
-
Option.
Multiple presencies possible 
ROD+010 - ICD+xxx - IDD+xxx 
170  
Risk object bâtiment - Subobject - type : contenu
No
-
-
Option.
Multiple presencies possible 
ROD+010 - SRO+042 
180  
Risk object bâtiment - Subobject contenu - Identifiant chez l'assureur / l'intermédiaire
No
-
-
Option.
 
ROD+010 - SRO+042+x--x:002/003 
190  
Risk object bâtiment - Subobject contenu - Unité du capital
Yes
2
Option.
 
ROD+010 - SRO+042 - ATT+331N+x--x 
200  
Risk object bâtiment - Subobject contenu - Montant capital
No
-
-
Option.
 
ROD+010 - SRO+042 - MOA+004:9--9:EUR:2+x--x:x--x:x--x+x--x:x--x 

(*) 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.