uniqueProduct

UniqueProduct messages are sent whenever a unique product was produced or modified.

2 minute read

Topic

MQTT: ia/<customerID>/<location>/<AssetID>/uniqueProduct

For Kafka just switch the / character with a .

Usage

A message is sent here each time a product has been produced or modified. A modification can take place, for example, due to a downstream quality control.

There are two cases of when to send a message under the uniqueProduct topic:

The exact product doesn’t already have a UID (-> This is the case, if it has not been produced at an asset incorporated in the digital shadow). Specify a space holder asset = “storage” in the MQTT message for the uniqueProduct topic.
The product was produced at the current asset (it is now different from before, e.g. after machining or after something was screwed in). The newly produced product is always the “child” of the process. Products it was made out of are called the “parents”.

Content

key	data type	description
`begin_timestamp_ms`	`int64`	unix timestamp of start time
`end_timestamp_ms`	`int64`	unix timestamp of completion time
`product_id`	`string`	product ID of the currently produced product
`isScrap`	`bool`	optional information whether the current product is of poor quality and will be sorted out. Is considered `false` if not specified.
`uniqueProductAlternativeID`	`string`	alternative ID of the product

JSON

Example

The processing of product “Beilinger 30x15” with the AID 216381 started and ended at the designated timestamps. It is of low quality and due to be scrapped.

{
  "begin_timestamp_ms":1589788888888,
  "end_timestamp_ms":1589788893729,
  "product_id":"Beilinger 30x15",
  "isScrap":"true",
  "uniqueProductAlternativeID":"216381"
}

Producers

Typically Node-RED

Consumers

kafka-to-postgresql

Last modified February 17, 2023: update (#208) (ea731fc)