Skip to content

Upload product scenarios

The IBM Food Trust™ Product scenarios builder enables your supply chain experts to create and save XML templates for your supply chain data. Your data integration experts will use these XML templates to configure and capture real, variable data (such as Lot #) for each instance of a scenario.

A key step is to ensure that your systems are configured to complete the templates with real values before uploading data to IBM Food Trust. Once you have configured your systems to update your XML templates with real data, you can configure them for automated data upload to IBM Food Trust.

To download the XML templates for your product scenario, click Download XML files:

Figure 1. Baby Spinach product scenario XML download
Product scenarios XML

For a Commission Event, you will make the following changes to the XML template file:

  1. Time of event
  2. UUID of event
  3. Lot number
  4. Quantity

Figure 2. Baby Spinach Commission Event XML template
Product scenarios commission XML

For an Observation Event, you will make the following changes to the XML template file:

  1. Time of event
  2. UUID of event
  3. Lot number
  4. Quantity

Figure 3. Baby Spinach Observation Event XML Template Product scenarios observation XML

For a Transformation Event, you will make the following changes to the XML template file:

  1. Time of event
  2. UUID of event
  3. Lot number of input product
  4. Quantity of input product
  5. Lot number of output product
  6. Quantity of output product

Figure 4. Baby Spinach Transformation Event XML template Product scenario transformation

For an Aggregation Event, you will make the following changes to the XML template file:

  1. Time of event
  2. UUID of event
  3. Pallet number
  4. Lot number shipment
  5. Quantity
  6. Destination facility

Figure 5. Baby Spinach Aggregation Event XML Template Product scenarios aggregation

Attention:

  1. You can use copies of your templates for multiple facilities by updating the <bizLocation><id> identifier for each location.
  2. Always generate a new UUID (Universal Unique Identifier) for each event that you upload.