Skip to content

Data access control example - manufacturer

The following data access control example describes data sharing by a manufacturer that receives leafy greens from a farm, produces and packages a mixed salad, and ships the finished product to a retail seller.

The example can be applied to any manufacturer with the same input and output scenario—three organizations, one location each, for a source-to-destination supply chain.

Data sharing

The focus organization for this data sharing example is the manufacturer of mixed salad. For the manufacturer, the three critical supply chain events in this example are receiving (salad ingredient), manufacturing (mixed salad), and shipping (packaged mixed salad) events. The manufacturer wants to share all its data for all three events with both of its supply chain partners—the farm and the retail store.

Data access control policy

For this example, the manufacturer has selected the IBM Food Trust source-to-destination transparency data access control policy. This policy enables the manufacturer to automatically share their events data for this product instance, with all organizations (farm and retail store) on this supply chain, by setting event data permissions to Linked.

Attention: A longer (more than three organizations) supply chain introduces dependencies on the data access control policies of other organizations when implementing end-to-end source-to-destination supply chain data sharing.

Prerequisites

The following prerequisites apply to this example:

  1. All three organizations are members of IBM Food Trust.
  2. All three organizations have defined their products and/or facilities (Master Data) on IBM Food Trust.
  3. The manufacturer has selected the source-to-destination transparency data access control policy.

Required tasks

To complete this example, the manufacturer must complete the tasks below. Completing these tasks shares event data for manufacturing the mixed salad product (as described by a lot, pallet, or product serial number) with the two supply chain partners (farm and retail store):

Upload receiving event

As the receiver of the mixed salad ingredient from the farm, the manufacturer must upload an XML document that describes this receiving event. On IBM Food Trust, receiving a shipment at a registered facility is an Observation Event. This Observation Event must identify the Facility ID of the sending farm location (SourceList XML tag), the Product ID of the received ingredient, and the Facility ID of the receiving location (BizLocation XML tag).

To complete this step, the manufacturer either completes and uploads a spreadsheet file (.xls) for the Observation Event type, or uses a direct API call to create and upload the event XML.

Note: Refer to the Observation Event XML structure.

Upload manufacturing event

As the producer of mixed salad, the manufacturer must upload an XML document that describes the manufacturing event. On IBM Food Trust, manufacturing a product from input ingredients is a Transformation Event. This Transformation Event document must identify the Product ID of the input ingredients, the Facility ID of the manufacturing location, and the Product ID of the output mixed salad.

To complete this step, the manufacturer either completes and uploads a spreadsheet file (.xls) for the Transformation Event type, or uses a direct API call to create and upload the event XML.

Note: Refer to the Transformation Event XML structure.

Upload shipping event

As the shipper of the mixed salad to the retail store, the manufacturer must upload an XML document that describes this shipping event. On IBM Food Trust, sending a shipment from a registered facility is an Observation event. This Observation event document must identify the Facility ID of the shipping location (in the Biz Location XML tag), the Product ID of the shipped product, and the Facility ID of the destination retail store (in the Destination List XML tag).

To complete this step, the manufacturer either completes and uploads a spreadsheet file (.xls) for the Observation Event type, or uses a direct API call to create and upload the event XML.

Note: Refer to the Observation Event XML structure.

Results and explanations

It is the combination of cross-referenced XML documents uploaded by the manufacturer that enables the viewing of the data assets (JSON) by the farm and the retail store. This enablement occurs through the linkage of the input and output Product IDs (specified in the Transformation Event XML and the respective Shipping Event XML) with the Facility IDs (referenced in the respective Shipping Event XML). The data entitlement status of these event documents as Linked (as defined by the source-to-destination data access control policy) completes the full farm-to-store supply chain view in this example. Without uploading all of these event XML documents as Linked, the data sharing permissions would not be enabled.

Data sharing by document

The data sharing results for each event XML document uploaded by the manufacturer in this scenario are explained below:

  1. Receiving (Observation) Event document uploaded by the manufacturer—The farm can view this data because its Facility ID is specified in the document as a Source. The retail store can view this data because the Transformation Event document (which it can view) specifies the input Product ID from the farm and links it to the Facility ID of the farm.

  2. Transformation Event document uploaded by the manufacturer—The farm can view this data because the Product ID of the input ingredient from the farm is specified in the document and also in the Receiving Event document. The retail store can view this data because the Product ID of the output mixed salad from the manufacturer is specified in the document and also in the Shipping Event document. In other words, the Product IDs in the document create links to the Facility IDs in the Shipping and Receiving Events documents to complete the full supply chain view for both farm and retail store.

  3. Shipping (Observation) Event document uploaded by the manufacturer—The retail store can view this data because its Facility ID is specified in the document as a Destination. The farm can view this data because the Transformation Event document (which it can view) specifies the output Product ID from the Manufacturer and links it to the Facility ID of the farm.