INFCON Infrastructure condition

TBG1 Supply Chain

The Infrastructure condition message is sent by a responsible party to other interested parties regarding the condition of a component in a commercial services or utilities infrastructure.

Send feedback Share via email

Header

Position
Segment
Name
Max use

  1. A 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 0052 D 0054 17A 0051 UN

    1. Data element S009/0057 is retained for upward compatibility. The use of
    S016 and/or S017 is encouraged in preference.
    2. The combination of the values carried in data elements 0062 and S009 shall
    be used to identify uniquely the message within its group (if used) or if
    not used, within its interchange, for the purpose of acknowledgement.

  2. A segment by which the sender uniquely identifies the Infrastructure condition message by means of its name and number and when necessary its function.

  3. A 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.

  4. A 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.

  5. Segment group 1
    Repeat 9

    1. A segment identifying a reference by its type and number.

    2. A segment specifying the date/time related to the referenced information.

  6. Segment group 2
    Repeat 99

    1. A 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.

    2. Segment group 3
      Repeat 9

      1. A segment to identify a person and/or department, and their function, to whom communications should be directed.

      2. A segment to identify a communication type and number for the contact specified.

Detail

Position
Segment
Name
Max use
  1. Segment group 4
    Repeat 999

    1. A 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.

    2. A segment to specify dates associated with the downtime, availability or occurrence of an event connected to the component.

    3. A segment to identify parties and/or addresses related to the component, such as installation address.

    4. A 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.

    5. Segment group 5
      Repeat 9

      1. A segment to identify characteristic and/or the characteristic name and characteristic relevance for the component.

      2. A segment to specify characteristic of the component, by value in either coded form or in free format.

    6. Segment group 6
      Repeat 9

      1. A segment to specify quantities related to the component.

      2. A segment indicating date or time details relating to the quantity, for example indication of capacity within a given period.

    7. Segment group 7
      Repeat 9

      1. A 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.

      2. A segment indicating the date/time details relevant to the schedule details. This segment may be used to indicate date/time ranges.

  2. A 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.

    1. 0062, the value shall be identical to the value in 0062 in the
    corresponding UNH segment.
Stedi.comDocumentationContact us

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.