Payload Structure for RouteReleased Events

Route Released Event Schema Version 0

This is the original version.

JSON RouteReleased Schema Version 0

{
  "routeDefinitionID": 40500,
  "name": "TestRoute",
  "revision": 2,
  "producedMaterialName": "Prod1",
  "plannedLineName": "Line1",
  "createdOn": "2022-02-05T13:05:29.929Z",
  "lastModifiedOn": "2022-02-05T13:08:06.940Z",
  "publishedDate": "2022-02-05T13:08:07Z",
  "kafkaConsumerId": "0000017ec9ffbaa1-0242ac1200250000"
}
Note: The content in mes.erp.outbound.messages, route release message has been modified in Plant Applications 2022. It is recommended to subscribe to mes.route.releasedRoutes and then use the routeID to leverage the route service to obtain data about the route. Within the route service you can use:
  • GET /routes/{routeID} to get information about the route (e.g., name, revision, last modified on, last modified by, etc.)
  • GET /routes/{routeID}/exportSegments to retrieve the route definition, including:
    • Produced material
    • Production line
    • Route behaviors
    • Operations sequences, names and descriptions
    • BOM item names, quantity, precision, etc.
    • Documents
    • Property names and values
    • Operation behaviors

B2MML RouteReleased Schema Version 0

<ProductInformation
    xmlns:Extended="http://www.wbf.org/xml/B2MML-V0401-AllExtensions"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:inp2="http://www.wbf.org/xml/B2MML-V0401"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:erp="http://sample.data"
    xmlns="http://www.wbf.org/xml/B2MML-V0401">
    <ID>0000017ed4c81220-0242ac1200250000</ID>
    <Description>ERP Export Service</Description>
    <Location>
        <EquipmentID/>
        <EquipmentElementLevel>Site</EquipmentElementLevel>
    </Location>
    <PublishedDate>2022-02-07T15:23:10Z</PublishedDate>
    <ProductDefinition>
        <ID>TestRoute</ID>
        <Version>2</Version>
        <Description/>
        <Location>
            <EquipmentID/>
            <EquipmentElementLevel>Site</EquipmentElementLevel>
            <Location>
                <EquipmentID>Line1</EquipmentID>
                <EquipmentElementLevel>ProductionLine</EquipmentElementLevel>
            </Location>
        </Location>
        <ProductSegment>
            <ID/>
            <Description/>
            <Parameter>
                <ID>RouteDefinitionID</ID>
                <Value>
                    <ValueString>40500</ValueString>
                    <DataType>integer</DataType>
                    <UnitOfMeasure/>
                </Value>
            </Parameter>
            <Parameter>
                <ID>CreatedOn</ID>
                <Value>
                    <ValueString>2022-02-05T13:05:29.929Z</ValueString>
                    <DataType>string</DataType>
                    <UnitOfMeasure/>
                </Value>
            </Parameter>
            <Parameter>
                <ID>LastModifiedOn</ID>
                <Value>
                    <ValueString>2022-02-05T13:08:06.940Z</ValueString>
                    <DataType>string</DataType>
                    <UnitOfMeasure/>
                </Value>
            </Parameter>
            <MaterialSpecification>
                <MaterialClassID/>
Note: The content in mes.erp.outbound.messages, route release message has been modified in Plant Applications 2022. It is recommended to subscribe to mes.route.releasedRoutes and then use the routeID to leverage the route service to obtain data about the route. Within the route service you can use:
  • GET /routes/{routeID} to get information about the route (e.g., name, revision, last modified on, last modified by, etc.)
  • GET /routes/{routeID}/exportSegments to retrieve the route definition, including:
    • Produced material
    • Production line
    • Route behaviors
    • Operations sequences, names and descriptions
    • BOM item names, quantity, precision, etc.
    • Documents
    • Property names and values
    • Operation behaviors