© 2018 ProgM

Nachricht INFCON: D

NameINFCON
VersionD
Release18B
BeschreibungInfrastructure condition message

Elemente

SegmentEbeneBeschreibungOpt/Mand.
UNH0A service segment starting and uniquely identifying a message. The message type code for the Infrastructure condition message is INFCON. Note: Infrastructure condition messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 INFCON D B UNMandatory
BGM0A segment by which the sender uniquely identifies the Infrastructure condition message by means of its name and number and when necessary its function.Mandatory
DTM0A segment specifying general dates and, when relevant, times related to the whole message. The segment must be specified at least once to specify the message date as allocated by the sender.Mandatory
FTX0A segment with free text information, in coded or clear form, used when additional information is needed, which is relevant for all components described in the actual message but cannot be accommodated within other segments.Optional
SG10SG1Optional
RFF1A segment identifying a reference by its type and number.Mandatory
DTM1A segment specifying the date/time related to the referenced information.Optional
SG20SG2Optional
NAD1A segment identifying names and addresses of the parties, in coded or clear form, and their functions relevant to the message. At least one occurrence of the segment is required. This will normally be the party responsible for the component(s) described. It is recommended that, if possible, only the coded form of the party ID should be specified.Mandatory
SG31SG3Mandatory
CTA2A segment to identify a person and/or department, and their function, to whom communications should be directed.Mandatory
COM2A segment to identify a communication type and number for the contact specified.Optional
SG40SG4Optional
LOC1A segment to identify the location of the component being reported. It is recommended that, where possible, codes should be used to identify the component to facilitate automatic processing.Mandatory
DTM1A segment to specify dates associated with the downtime, availability or occurrence of an event connected to the component.Optional
NAD1A segment to identify parties and/or addresses related to the component, such as installation address.Optional
FTX1A segment with free text information, in coded or clear form, used when additional information on the downtime, availability or occurrence of an event connected to the component is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.Optional
SG51SG5Optional
CCI2A segment to identify characteristic and/or the characteristic name and characteristic relevance for the component.Mandatory
CAV2A segment to specify characteristic of the component, by value in either coded form or in free format.Optional
SG61SG6Optional
QTY2A segment to specify quantities related to the component.Mandatory
DTM2A segment indicating date or time details relating to the quantity, for example indication of capacity within a given period.Optional
SG71SG7Optional
SCC2A segment specifying the type and status of the schedule being given, and optionally defining a pattern to be established, such as estimated schedule for the downtime, availability or occurrence of an event connected to the component.Mandatory
DTM2A segment indicating the date/time details relevant to the schedule details. This segment may be used to indicate date/time ranges.Optional
UNT0A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.Mandatory