Process Fields

The specification for Process has these fields:

name

Required-string
Short name to identify the Process

Example

Pressure drop for the injection in hall 3

description

Required-string
Short description of the scope of the Process (human readable)

Example

Effectiveness of the mold closing process

version

Required-string
Version number of the Process, defined by the provider

Example

0.21.0

ip_instance

Required-string
Identifier of the IP Instance the Process is valid for (NB: Entity for IP Instance is referenced)

Example

ip_instance_123e4567-e89b-12d3

ma_pair

Required-string
Identifier of the Behaviour (MA Pair) associated to the Process

Example

MAID_MYMA

deployments

Required-Deployment
Mapping of characteristics of the Deployment (i.e. Cloud or Edge infrastructure) for every Microservice associated to the Process

data_assets_mapping

Optional-DataAssetsMapping
Mapping required Data assets to Microservices specified in the Behaviour (MA Pair). Not every Microservice needs a Data asset.

namespace

Optional-string
Context to interpret the associated information

Example

namespace_123e4567-e89b-12d3

payload

Optional-string (JSON)
User-defined key-value pairs with additional information

Example

{"injectionMold": "Circuit Case"}

schedule

Optional-string
Days and hours the Process will be active

Example

R90/2021-05-01T00:00:00Z/PT48H