### Validate B2MML XML using AllSchemas.xsd with xmllint

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

This command-line example shows how to validate a B2MML XML file against the `AllSchemas.xsd` using the `xmllint` tool. This ensures the XML document conforms to the complete B2MML schema.

```bash
xmllint --schema Schema/AllSchemas.xsd my-sync-equipment.xml --noout
```

--------------------------------

### Example B2MML JSON Structure for EquipmentInformation

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

This JSON snippet illustrates the structure of an `EquipmentInformation` object in B2MML's JSON format. It includes standard elements and properties, demonstrating how data is represented in JSON.

```json
{
  "EquipmentInformation": {
    "ID": { "_value": "EQUIP-INFO-SITE-A" },
    "Equipment": [
      {
        "ID": { "_value": "REACTOR-101", "schemeID": "ERP" },
        "Description": [{ "_value": "Batch Mixing Reactor", "languageID": "en" }],
        "EquipmentLevel": { "_value": "ProcessCell" },
        "EquipmentProperty": [
          {
            "ID": { "_value": "MaxTemperature" },
            "Value": [
              { "ValueString": { "_value": "180" }, "DataType": { "_value": "double" } }
            ]
          }
        ]
      }
    ]
  }
}
```

--------------------------------

### Generate Java Code from AllSchemas.xsd using JAXB

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

This command-line example demonstrates how to generate Java classes from the `AllSchemas.xsd` file using the `xjc` tool from JAXB. This is useful for creating Java objects that represent B2MML structures.

```bash
xjc -d src/generated -p com.example.b2mml Schema/AllSchemas.xsd
```

--------------------------------

### B2MML Core Primitive Types Examples

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

Examples of core primitive XML types used in B2MML. These include AmountType, BinaryObjectType, CodeType, DateTimeType, IdentifierType, MeasureType, QuantityType, and TextType.

```xml
<!-- AmountType: decimal with optional currency -->
<Amount currencyID="USD">1500.00</Amount>
```

```xml
<!-- BinaryObjectType: base64-encoded file with metadata -->
<AttachedDocument mimeCode="application/pdf" filename="spec.pdf">
  JVBERi0xLjQK...
</AttachedDocument>
```

```xml
<!-- CodeType: normalized string with list metadata -->
<EquipmentLevel listID="ISA-95" listAgencyID="ISA">ProcessCell</EquipmentLevel>
```

```xml
<!-- DateTimeType: ISO 8601 datetime with optional format hint -->
<EffectiveStartDate format="ISO8601">2024-01-15T08:00:00</EffectiveStartDate>
```

```xml
<!-- IdentifierType: string identifier with scheme metadata -->
<ID schemeID="ERP" schemeAgencyID="SAP">EQUIP-REACTOR-001</ID>
```

```xml
<!-- MeasureType: decimal with unit of measure -->
<Quantity unitCode="KGM">250.5</Quantity>
```

```xml
<!-- QuantityType: counted units with list agency -->
<BatchSize unitCode="L" unitCodeListAgencyID="UNECE">5000</BatchSize>
```

```xml
<!-- TextType: string with optional language tag -->
<Description languageID="en">Primary mixing reactor, stainless steel</Description>
```

--------------------------------

### B2MML Common Shared Types Examples

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

Examples of common shared XML types from B2MML-Common.xsd. These include HierarchyScopeType for scoping, ValueType for generic properties, AssemblyRelationshipType, CapabilityTypeType, and SpatialDefinitionType.

```xml
<!-- HierarchyScopeType: scopes data to a specific site/area/process cell -->
<HierarchyScope>
  <EquipmentID>Site-A</EquipmentID>
  <EquipmentElementLevel>Site</EquipmentElementLevel>
</HierarchyScope>
```

```xml
<!-- ValueType: generic property value with data type and unit -->
<Value>
  <ValueString>250</ValueString>
  <DataType>double</DataType>
  <UnitOfMeasure unitCode="degC">Celsius</UnitOfMeasure>
  <Key>MaxTemperature</Key>
</Value>
```

```xml
<!-- AssemblyRelationshipType: Permanent | Transient | Other -->
<AssemblyRelationship OtherValue="">Permanent</AssemblyRelationship>
```

```xml
<!-- CapabilityTypeType: Used | Unused | Total | Committed | Available | Other -->
<CapabilityType>Available</CapabilityType>
```

```xml
<!-- SpatialDefinitionType: WKT or custom geometry string -->
<SpatialDefinition>POLYGON((0 0, 10 0, 10 5, 0 5, 0 0))</SpatialDefinition>
```

--------------------------------

### Publish General Recipe using BatchML-GeneralRecipe.xsd

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

This XML snippet demonstrates publishing a general recipe to a batch execution system using the BatchML-GeneralRecipe.xsd schema. It includes recipe details, versioning, and status.

```xml
<!-- ProcessGRecipeInformation: publish a general recipe to batch execution system -->
<ProcessGRecipeInformation releaseID="V0701">
  <ApplicationArea>
    <Sender><LogicalID>RECIPE-MGMT-SYSTEM</LogicalID></Sender>
    <CreationDateTime>2024-03-10T08:00:00</CreationDateTime>
    <BODID>RECIPE-20240310-001</BODID>
  </ApplicationArea>
  <DataArea>
    <Process><ActionCriteria><ActionExpression actionCode="Add"/></ActionCriteria></Process>
    <GRecipeInformation>
      <ID>GRECIPE-INFO-001</ID>
      <GRecipe>
        <ID>GR-PRODUCT-A-V2</ID>
        <Description languageID="en">General Recipe for Product A, Version 2</Description>
        <Version>2.0</Version>
        <Status>Active</Status>
        <BatchSize unitCode="KGM">200</BatchSize>
        <Header>
          <ProductID>PRODUCT-A</ProductID>
          <RecipeStatus>Approved</RecipeStatus>
          <ApprovalHistory>
            <FinalApprovalDate>2024-02-01T00:00:00</FinalApprovalDate>
            <Version>2.0</Version>
          </ApprovalHistory>
        </Header>
      </GRecipe>
    </GRecipeInformation>
  </DataArea>
</ProcessGRecipeInformation>
```

--------------------------------

### Synchronize Material Master and Lot Data (XML)

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

Use this XML structure to synchronize material master data and lot information. Ensure all required fields like IDs, descriptions, quantities, and statuses are accurately populated.

```xml
<!-- SyncMaterialInformation: synchronize material master and lot data -->
<SyncMaterialInformation releaseID="V0701">
  <ApplicationArea>
    <Sender><LogicalID>ERP-SYSTEM</LogicalID></Sender>
    <CreationDateTime>2024-03-10T11:00:00</CreationDateTime>
    <BODID>SYNC-MAT-20240310-001</BODID>
  </ApplicationArea>
  <DataArea>
    <Sync><ActionCriteria><ActionExpression actionCode="Change"/></ActionCriteria></Sync>
    <MaterialInformation>
      <ID>MAT-INFO-001</ID>
      <MaterialDefinition>
        <ID>CHEMICAL-A-DEF</ID>
        <Description languageID="en">Reagent Grade Chemical A</Description>
        <MaterialDefinitionProperty>
          <ID>Purity</ID>
          <Value><ValueString>99.5</ValueString><DataType>double</DataType>
            <UnitOfMeasure unitCode="P1">Percent</UnitOfMeasure>
          </Value>
        </MaterialDefinitionProperty>
        <MaterialClassID>RAW-CHEMICALS</MaterialClassID>
      </MaterialDefinition>
      <MaterialLot>
        <ID>LOT-2024-00123</ID>
        <Description languageID="en">Received batch March 2024</Description>
        <ExpirationDate>2025-03-01T00:00:00</ExpirationDate>
        <Quantity unitCode="KGM">500</Quantity>
        <Status>Approved</Status>
        <MaterialDefinitionID>CHEMICAL-A-DEF</MaterialDefinitionID>
      </MaterialLot>
    </MaterialInformation>
  </DataArea>
</SyncMaterialInformation>
```

--------------------------------

### Dispatch Job Orders to Shop Floor Control (XML)

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

This XML structure is used to dispatch detailed work instructions, such as job orders, from a scheduling system to shop floor control. It includes work definitions, priorities, and timeframes.

```xml
<!-- SyncWorkSchedule: dispatch job orders to shop floor control -->
<SyncWorkSchedule releaseID="V0701">
  <ApplicationArea>
    <Sender><LogicalID>MES-DISPATCH</LogicalID></Sender>
    <CreationDateTime>2024-03-11T05:30:00</CreationDateTime>
    <BODID>WORK-SCHED-20240311-001</BODID>
  </ApplicationArea>
  <DataArea>
    <Sync><ActionCriteria><ActionExpression actionCode="Add"/></ActionCriteria></Sync>
    <WorkSchedule>
      <ID>WS-2024-03-11</ID>
      <WorkRequest>
        <ID>WR-20240311-001</ID>
        <WorkDefinitionID>BATCH-PROD-A</WorkDefinitionID>
        <JobList>
          <ID>JL-20240311-001</ID>
          <JobOrder>
            <ID>JO-20240311-001</ID>
            <Description languageID="en">Produce 200kg Product A, Reactor 101</Description>
            <WorkType>Production</WorkType>
            <Priority>1</Priority>
            <StartTime>2024-03-11T06:00:00</StartTime>
            <EndTime>2024-03-11T14:00:00</EndTime>
            <WorkMasterID>BATCH-PROD-A-MASTER</WorkMasterID>
          </JobOrder>
        </JobList>
      </WorkRequest>
    </WorkSchedule>
  </DataArea>
</SyncWorkSchedule>
```

--------------------------------

### Use Custom Equipment Extensions in a B2MML Instance Document

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

This XML snippet demonstrates how to use the custom 'MaintenanceDueDate' and 'AssetRiskScore' elements within an Equipment instance document. The custom elements are prefixed with the namespace for the extensions.

```xml
<SyncEquipmentInformation releaseID="V0701"
    xmlns="http://www.mesa.org/xml/B2MML"
    xmlns:Extended="http://www.mesa.org/xml/B2MML-AllExtensions">
  <ApplicationArea>
    <Sender><LogicalID>ERP-SAP</LogicalID></Sender>
    <CreationDateTime>2024-03-10T09:00:00</CreationDateTime>
    <BODID>SYNC-EQUIP-EXT-001</BODID>
  </ApplicationArea>
  <DataArea>
    <Sync><ActionCriteria><ActionExpression actionCode="Replace"/></ActionCriteria></Sync>
    <EquipmentInformation>
      <ID>EQUIP-INFO-SITE-A</ID>
      <Equipment>
        <ID>REACTOR-101</ID>
        <Description>Batch Mixing Reactor</Description>
        <!-- Standard B2MML element -->
        <EquipmentLevel>ProcessCell</EquipmentLevel>
        <!-- Custom extension elements via Extended group -->
        <Extended:MaintenanceDueDate>2024-06-01T00:00:00</Extended:MaintenanceDueDate>
        <Extended:AssetRiskScore format="0-100">42</Extended:AssetRiskScore>
      </Equipment>
    </EquipmentInformation>
  </DataArea>
</SyncEquipmentInformation>
```

--------------------------------

### Advertise Supported Transactions using B2MML-TransactionProfile.xsd

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

This XML snippet defines a system's supported transactions using the B2MML-TransactionProfile.xsd schema. It allows for dynamic discovery of integration capabilities between systems.

```xml
<!-- ShowTransactionProfile: advertise supported transactions -->
<ShowTransactionProfile releaseID="V0701">
  <ApplicationArea>
    <Sender><LogicalID>MES-SYSTEM-A</LogicalID></Sender>
    <CreationDateTime>2024-03-10T09:00:00</CreationDateTime>
    <BODID>TXPROFILE-20240310-001</BODID>
  </ApplicationArea>
  <DataArea>
    <Show/>
    <TransactionProfile releaseID="V0701">
      <ID>MES-SYSTEM-A-PROFILE</ID>
      <Description languageID="en">MES System A Supported Transactions</Description>
      <SupportedAction releaseID="V0701">
        <ID>SA-001</ID>
        <TransactionVerb>SYNC ADD</TransactionVerb>
        <TransactionNoun>EQUIPMENT INFORMATION</TransactionNoun>
        <InformationReceiver>true</InformationReceiver>
        <InformationProvider>false</InformationProvider>
        <ObjectWildcardSupported>false</ObjectWildcardSupported>
        <PropertyWildcardSupported>false</PropertyWildcardSupported>
      </SupportedAction>
      <SupportedAction releaseID="V0701">
        <ID>SA-002</ID>
        <TransactionVerb>NOTIFY</TransactionVerb>
        <TransactionNoun>OPERATIONS PERFORMANCE</TransactionNoun>
        <InformationProvider>true</InformationProvider>
        <InformationReceiver>false</InformationReceiver>
      </SupportedAction>
    </TransactionProfile>
  </DataArea>
</ShowTransactionProfile>
```

--------------------------------

### Sync Equipment Information with MES

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

Use this XML structure to push equipment master data to the MES. Ensure the releaseID and BODID are correctly set for tracking.

```xml
<!-- SyncEquipmentInformation: push equipment master data to MES -->
<SyncEquipmentInformation releaseID="V0701">
  <ApplicationArea>
    <Sender><LogicalID>ERP-SAP</LogicalID></Sender>
    <CreationDateTime>2024-03-10T09:00:00</CreationDateTime>
    <BODID>SYNC-EQUIP-20240310-001</BODID>
  </ApplicationArea>
  <DataArea>
    <Sync><ActionCriteria><ActionExpression actionCode="Replace"/></ActionCriteria></Sync>
    <EquipmentInformation>
      <ID>EQUIP-INFO-SITE-A</ID>
      <HierarchyScope>
        <EquipmentID>Site-A</EquipmentID>
        <EquipmentElementLevel>Site</EquipmentElementLevel>
      </HierarchyScope>
      <Equipment>
        <ID schemeID="ERP">REACTOR-101</ID>
        <Description languageID="en">Batch Mixing Reactor</Description>
        <EffectiveStartDate>2024-01-01T00:00:00</EffectiveStartDate>
        <EquipmentLevel>ProcessCell</EquipmentLevel>
        <EquipmentProperty>
          <ID>MaxTemperature</ID>
          <Value>
            <ValueString>180</ValueString>
            <DataType>double</DataType>
            <UnitOfMeasure unitCode="degC">Celsius</UnitOfMeasure>
          </Value>
        </EquipmentProperty>
        <EquipmentClassID>MIXING-REACTOR-CLASS</EquipmentClassID>
      </Equipment>
    </EquipmentInformation>
  </DataArea>
</SyncEquipmentInformation>
```

--------------------------------

### Define Custom Equipment Extensions in B2MML-Extensions.xsd

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

This XML snippet shows how to define custom elements like 'MaintenanceDueDate' and 'AssetRiskScore' within the 'Equipment' group in `B2MML-Extensions.xsd`. These extensions can then be used in B2MML documents.

```xml
<xsd:group name="Equipment">
  <xsd:sequence>
    <xsd:element name="MaintenanceDueDate" type="b2mml:DateTimeType" minOccurs="0"/>
    <xsd:element name="AssetRiskScore"     type="b2mml:NumericType"  minOccurs="0"/>
  </xsd:sequence>
</xsd:group>
```

--------------------------------

### Synchronize Batch Information using BatchML-BatchInformation.xsd

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

This XML snippet shows how to synchronize active batch records to a historian using the BatchML-BatchInformation.xsd schema. It includes batch identifiers, recipe references, and operational status.

```xml
<!-- SyncBatchInformation: synchronize active batch records to historian -->
<SyncBatchInformation releaseID="V0701">
  <ApplicationArea>
    <Sender><LogicalID>BATCH-EXECUTION-SYSTEM</LogicalID></Sender>
    <CreationDateTime>2024-03-11T07:00:00</CreationDateTime>
    <BODID>BATCH-SYNC-20240311-001</BODID>
  </ApplicationArea>
  <DataArea>
    <Sync><ActionCriteria><ActionExpression actionCode="Add"/></ActionCriteria></Sync>
    <BatchInformation>
      <ID>BATCH-INFO-20240311</ID>
      <BatchList>
        <ID>BATCH-20240311-001</ID>
        <BatchID>BATCH-A-20240311-001</BatchID>
        <RecipeID>GR-PRODUCT-A-V2</RecipeID>
        <ScheduledStartTime>2024-03-11T06:00:00</ScheduledStartTime>
        <ActualStartTime>2024-03-11T06:05:00</ActualStartTime>
        <BatchStatus>Running</BatchStatus>
        <ActualBatchSize>200</ActualBatchSize>
        <EquipmentID>REACTOR-101</EquipmentID>
      </BatchList>
    </BatchInformation>
  </DataArea>
</SyncBatchInformation>
```

--------------------------------

### Process Production Schedule (XML)

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

This XML is used to send production schedules from an ERP system to an MES. It defines the overall schedule and individual operations requests with their material and equipment requirements.

```xml
<!-- ProcessOperationsSchedule: send production schedule from ERP to MES -->
<ProcessOperationsSchedule releaseID="V0701">
  <ApplicationArea>
    <Sender><LogicalID>ERP-SCHEDULER</LogicalID></Sender>
    <CreationDateTime>2024-03-10T06:00:00</CreationDateTime>
    <BODID>SCHED-20240310-001</BODID>
  </ApplicationArea>
  <DataArea>
    <Process><ActionCriteria><ActionExpression actionCode="Add"/></ActionCriteria></Process>
    <OperationsSchedule>
      <ID>SCHED-2024-WEEK11</ID>
      <Description languageID="en">Week 11 Production Schedule</Description>
      <StartTime>2024-03-11T06:00:00</StartTime>
      <EndTime>2024-03-15T18:00:00</EndTime>
      <OperationsRequest>
        <ID>REQ-20240311-001</ID>
        <OperationsDefinitionID>BATCH-PROD-A</OperationsDefinitionID>
        <StartTime>2024-03-11T06:00:00</StartTime>
        <EndTime>2024-03-11T14:00:00</EndTime>
        <SegmentRequirement>
          <ID>SEG-REQ-001</ID>
          <MaterialProducedRequirement>
            <MaterialDefinitionID>PRODUCT-A</MaterialDefinitionID>
            <Quantity unitCode="KGM">200</Quantity>
          </MaterialProducedRequirement>
          <EquipmentRequirement>
            <EquipmentID>REACTOR-101</EquipmentID>
          </EquipmentRequirement>
        </SegmentRequirement>
      </OperationsRequest>
    </OperationsSchedule>
  </DataArea>
</ProcessOperationsSchedule>
```

--------------------------------

### Process Personnel Information and Qualifications

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

Send personnel qualifications and data to the MES using this XML structure. The ActionCriteria can specify 'Add', 'Replace', or 'Delete' operations.

```xml
<!-- ProcessPersonnelInformation: send personnel qualifications to MES -->
<ProcessPersonnelInformation releaseID="V0701">
  <ApplicationArea>
    <Sender><LogicalID>HR-SYSTEM</LogicalID></Sender>
    <CreationDateTime>2024-03-10T10:00:00</CreationDateTime>
    <BODID>PROC-PERS-20240310-001</BODID>
  </ApplicationArea>
  <DataArea>
    <Process><ActionCriteria><ActionExpression actionCode="Add"/></ActionCriteria></Process>
    <PersonnelInformation>
      <ID>PERS-INFO-001</ID>
      <PersonnelClass>
        <ID>QUALIFIED-OPERATOR</ID>
        <Description languageID="en">Certified reactor operators</Description>
        <PersonnelClassProperty>
          <ID>Certification</ID>
          <Value><ValueString>ISO-9001</ValueString><DataType>string</DataType></Value>
        </PersonnelClassProperty>
      </PersonnelClass>
      <Person>
        <ID schemeID="HR">EMP-00421</ID>
        <Description languageID="en">Jane Smith</Description>
        <PersonProperty>
          <ID>ShiftRole</ID>
          <Value><ValueString>Lead Operator</ValueString><DataType>string</DataType></Value>
        </PersonProperty>
        <PersonnelClassID>QUALIFIED-OPERATOR</PersonnelClassID>
      </Person>
    </PersonnelInformation>
  </DataArea>
</ProcessPersonnelInformation>
```

--------------------------------

### Request Equipment Data from MES

Source: https://context7.com/mesainternational/b2mml-batchml/llms.txt

Use this XML to request specific equipment data from the MES. The Expression element allows for filtering based on equipment ID or other criteria.

```xml
<!-- GetEquipmentInformation: request equipment data from MES -->
<GetEquipmentInformation releaseID="V0701">
  <ApplicationArea>
    <Sender><LogicalID>ERP-SAP</LogicalID></Sender>
    <CreationDateTime>2024-03-10T09:00:00</CreationDateTime>
    <BODID>GET-EQUIP-20240310-001</BODID>
  </ApplicationArea>
  <DataArea>
    <Get><Expression expressionLanguage="XPath">ID='REACTOR-101'</Expression></Get>
    <EquipmentInformation><ID>EQUIP-INFO-SITE-A</ID></EquipmentInformation>
  </DataArea>
</GetEquipmentInformation>
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.