Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[New Model]: Bill of Process (BoP) #511

Closed
6 tasks done
dominikoeh opened this issue Dec 18, 2023 · 2 comments · Fixed by #569
Closed
6 tasks done

[New Model]: Bill of Process (BoP) #511

dominikoeh opened this issue Dec 18, 2023 · 2 comments · Fixed by #569
Labels
MS1_Approved Checklist "MS1 Request for Model Developement" is approved.

Comments

@dominikoeh
Copy link
Contributor

dominikoeh commented Dec 18, 2023

Resiliency Domain / Modular Production

Model Description

A Bill of Process (BoP) describes the best-practice approach for the production of a product. Detailed information about the processes, process precedence, and process parameters are required to manufacture the product. The exchange of process information between actors requires a standardized representation of the processes, as currently there are often separate, actor-specific forms of process representation.

This standardization effort aims to ease the understanding of process representations from other partners along the value chain by providing a shared model.
The scope of this model is a BoP that exists before actual production starts, therefore named "BoP as planned".
This model is meant to be flexible enough to accommodate a wide range of use cases and is relevant for both: information exchange (external) and internal workflows.

Example Data

{
  "productVersion": "1.4",
  "versionDataModel": "1.0",
  "billOfProcessIdentification": "https://www.example.com/bop/examplebop",
  "productName": "Barhocker",
  "processSteps": [
    {
      "processStepIdentifier": "Drehen",
      "capabilityReference": "urn:uuid:b5844423-92ac-4527-9b02-bbc64a58d193",
      "childProcessSteps": ["Pick and Place"],
      "inputMaterial": ["Sitzschale, Beine"],
      "outputMaterial": ["Barhocker"],
      "inputParameter": [
        {
          "name": "torque",
          "unit": "Nm",
          "semanticReference": "0173-1#02-AAZ808#001",
          "value": "8",
          "parameterized": "HasValue"
        }
      ],
      "outputParameter": [
        {
          "name": "weight",
          "unit": "kg",
          "semanticReference": "E-Class",
          "value": "2",
          "parameterized": "HasValue"
        }
      ],
      "precedenceRelation": [
        {
          "precedenceElements": [
            {
              "successor": ["Pick and Place"]
            }
          ]
        }
      ]
    },
    {
      "processStepIdentifier": "Pick and Place",
      "capabilityReference": "urn:uuid:a3843423-92ac-4567-1a02-bbc62a56d193",
      "inputMaterial": ["Barhocker"],
      "outputMaterial": ["Barhocker"],
      "inputParameter": [
        {
          "name": "Location",
          "parameterized": "HasNoValue"
        }
      ],
      "outputParameter": [
        {
          "name": "Location",
          "parameterized": "HasNoValue"
        }
      ]
    }
  ]
}

MS1 Criteria

  • The proposed aspect model does not exist already
  • The proposed aspect model does not extend an existing aspect but introduces completely new functionality
  • The proposal references a Catena-X use case
  • Relevant standards are mentioned/linked
  • A first draft of the data structure is provided in an example
  • A modeling steward has been assigned
@dominikoeh
Copy link
Contributor Author

Modeling_Team

@tom-rm-meyer-ISST tom-rm-meyer-ISST added the MS1_Approved Checklist "MS1 Request for Model Developement" is approved. label Dec 18, 2023
@jacewski-bosch
Copy link
Contributor

@agg3fe has been assigned as modeling steward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MS1_Approved Checklist "MS1 Request for Model Developement" is approved.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants