Custom B2MML Process Order Import Document (POID)

Instead of a JSON format, you can send a POID in one of the following XML formats:
  • Standard B2MML
  • Custom B2MML

When you use a custom B2MML, you must first provide an XSL file that contains the mapping information. This topic provides custom B2MML samples of a POID for each schema version. Refer to XSL File to Map a Process Order for a sample XSL file to map the B2MML samples. If, however, you want to use a standard B2MML format for the POID, refer to Standard B2MML Process Order Import Document (POID).

Note: When an XML file is processed, some of the special characters are omitted. To prevent this issue, use the escape strings as specified in the following table.
Special CharacterEscape String
&&
<&lt;
>&gt;
&quot;
&apos;

Custom B2MML POID Schema Version 2

Using schema version 2, you can override values of the process order properties. In addition, providing the production line is not mandatory, and you can include production lines with multiple execution paths. When a production line has multiple execution paths, the process order becomes an unbound process order. You can associate a production line with an execution path using Plant Applications Administrator or Plant Applications Web Client; or you can leave it as is.
<?xml version="1.0" encoding="UTF-8"?>

-<ProductionSchedule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns3="http://www.wbf.org/xml/B2MML-V0401" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:Extended="http://www.wbf.org/xml/B2MML-V0401-AllExtensions">

<ID>0000000112841171</ID>


-<ProductionRequest>

<ProductProductionRuleID>REG_JUICE_FORMULA</ProductProductionRuleID>

<ID>POIDXML-100-2020</ID>


-<SegmentRequirement>

<LatestEndTime>2020-12-09T09:22:17.825Z</LatestEndTime>

<EarliestStartTime>2020-12-08T09:22:17.825Z</EarliestStartTime>


-<MaterialProducedRequirement>


-<Quantity>

<UnitOfMeasure></UnitOfMeasure>

<DataType>float</DataType>

<QuantityString>234.89</QuantityString>

</Quantity>

<MaterialDefinitionID>PulpyJuice</MaterialDefinitionID>

</MaterialProducedRequirement>


-<ProductionParameter>


-<Parameter>

<ID>Process_Prop_Int</ID>


-<Value>

<ValueString>123</ValueString>

<DataType>integer</DataType>

</Value>

<Description>Process_Prop2_Int is int param</Description>

</Parameter>

</ProductionParameter>


-<ProductionParameter>


-<Parameter>

<ID>Process_Prop_String</ID>


-<Value>

<ValueString>someliteral</ValueString>

<DataType>string</DataType>

</Value>

<Description>Process_Prop1 is string param</Description>

</Parameter>

</ProductionParameter>

</SegmentRequirement>

</ProductionRequest>

<Extended:SchemaVersion>2</Extended:SchemaVersion>

</ProductionSchedule>

Custom B2MML POID Schema Version 1

Using schema version 1, you can import process orders containing information about the planned quantity, material, production line, and planned start and end dates.
<?xml version="1.0" encoding="UTF-8"?>

-<ProductionSchedule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns3="http://www.wbf.org/xml/B2MML-V0401" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:Extended="http://www.wbf.org/xml/B2MML-V0401-AllExtensions">

<ID>0000000112841171</ID>


-<ProductionRequest>

<ProductProductionRuleID>REG_JUICE_FORMULA</ProductProductionRuleID>

<ID>POIDXML-100-2020</ID>


-<SegmentRequirement>

<LatestEndTime>2020-12-09T09:22:17.825Z</LatestEndTime>

<EarliestStartTime>2020-12-08T09:22:17.825Z</EarliestStartTime>


-<EquipmentRequirement>

<EquipmentID>JiuceLine</EquipmentID>

</EquipmentRequirement>


-<MaterialProducedRequirement>


-<Quantity>

<UnitOfMeasure></UnitOfMeasure>

<DataType>float</DataType>

<QuantityString>10.5</QuantityString>

</Quantity>

<MaterialDefinitionID>PulpyJuice</MaterialDefinitionID>

</MaterialProducedRequirement>

<ID>1</ID>


-<EquipmentRequirement>

<EquipmentID>Test Line1</EquipmentID>

</EquipmentRequirement>


-<EquipmentRequirement>

<EquipmentID>Test Line1</EquipmentID>

</EquipmentRequirement>

</SegmentRequirement>

</ProductionRequest>


-<Location>

<EquipmentElementLevel>Site</EquipmentElementLevel>

<EquipmentID>0288</EquipmentID>


-<Location>

<EquipmentElementLevel>Area</EquipmentElementLevel>

<EquipmentID>193</EquipmentID>

</Location>

</Location>

<Extended:SchemaVersion>1</Extended:SchemaVersion>

</ProductionSchedule>