Commission events in the TrustStack.
In supply chains, it’s common to record the moment when something is first created, introduced or made traceable - this could be:
In EPCIS, these creation moments are usually modeled using an ObjectEvent
with:
action
set to ADD
epcList
or quantityList
containing the identifier of the products that were created.bizStep
like commissioning
or receiving
depending on context.At the end of a commissioning event, we need unique identifiers for the products that were created. The TrustStack supports master data concepts such as Trade Items. As a refresh, a Trade Item is anything that can be priced in sold in a supply chain.
We can reference a TradeItem
when creating a Event
to generate a unique identifier for the product.
Let’s say we are building a grain farm management application, and we need users to be able commission a batch of wheat.
Such as, the farmer has harvested a paddock of wheat, and we need to create a unique identifier for the batch wheat.
Let’s use the TrustStack SDK to create a new Farm
and Paddock
for our example.
We now have a Farm
and Paddock
in the TrustStack for this farming enterprise.
This farmer is harvesting Wheat, this can be priced and sold in the supply chain, so it is a TradeItem
.
Let’s create a TradeItem
for Wheat.
Now, the farmer has harvested the wheat from the paddock, and we need to create an event to record this.
The output of this event will be:
An event has now been created:
readPoint
is the paddock that the wheat was harvested from.quantityList
contains a batch/lot level identifier of the Wheat TradeItem
that was harvested, and the quantity harvested.eventTime
is the date and time the harvest event occurred.bizStep
is the business step of the harvest event, in this case COMMISSIONING
.disposition
is the disposition of the event, in this case ACTIVE
.Commission events in the TrustStack.
In supply chains, it’s common to record the moment when something is first created, introduced or made traceable - this could be:
In EPCIS, these creation moments are usually modeled using an ObjectEvent
with:
action
set to ADD
epcList
or quantityList
containing the identifier of the products that were created.bizStep
like commissioning
or receiving
depending on context.At the end of a commissioning event, we need unique identifiers for the products that were created. The TrustStack supports master data concepts such as Trade Items. As a refresh, a Trade Item is anything that can be priced in sold in a supply chain.
We can reference a TradeItem
when creating a Event
to generate a unique identifier for the product.
Let’s say we are building a grain farm management application, and we need users to be able commission a batch of wheat.
Such as, the farmer has harvested a paddock of wheat, and we need to create a unique identifier for the batch wheat.
Let’s use the TrustStack SDK to create a new Farm
and Paddock
for our example.
We now have a Farm
and Paddock
in the TrustStack for this farming enterprise.
This farmer is harvesting Wheat, this can be priced and sold in the supply chain, so it is a TradeItem
.
Let’s create a TradeItem
for Wheat.
Now, the farmer has harvested the wheat from the paddock, and we need to create an event to record this.
The output of this event will be:
An event has now been created:
readPoint
is the paddock that the wheat was harvested from.quantityList
contains a batch/lot level identifier of the Wheat TradeItem
that was harvested, and the quantity harvested.eventTime
is the date and time the harvest event occurred.bizStep
is the business step of the harvest event, in this case COMMISSIONING
.disposition
is the disposition of the event, in this case ACTIVE
.