[New Model]: Material Demand DCM/PURIS

[nhaenis]

Model Description

PURIS and DCM would like to harmonize their data models in the future in order to use one common data model and not create redundancies. Most of DCMs data model week_based_material_demand can be reused.

Relevant Standards

DCM Material Demand

Example Data

--- JSON only payload suggestion ---

{
  "demandRate": {
    "demandRateCode": "cw"                                                      # cw = calendar week
  },
  "unitOfMeasure": "H87",
  "materialDescriptionCustomer": "Spark Plug",
  "materialDemandId": "0157ba42-d2a8-4e28-8565-7b07830c1110",
  "materialNumberSupplier": "MNR-8101-ID146955.001",                            # translated into name
  "supplier": "BPNL6666666666YY",
  "changedAt": "2023-03-10T12:27:11.320Z",
  "materialNumberCatenaX": "urn:uuid:48878d48-6f1d-47f5-8ded-a441d0d879df",     # not visible in screen
  "demandSeries": [
    {
      "expectedSupplierLocation": "BPNS8888888888XX",                           # translated into nameHelsinki
      "demands": [
        {
          "demand": 100,
          "pointInTime": "2022-03-07T01:00:52.173-07:00"
        }
      ],
      "customerLocation": "BPNS7777777777XX",                                   # demand location, Berlin
      "demandCategory": {
        "demandCategoryCode": "SR99"                                            # Series
      }
    },
    {
      "expectedSupplierLocation": "BPNS8888888888XX",                           # translated into nameHelsinki
      "demands": [
        {
          "demand": 100,
          "pointInTime": "2022-03-07T01:00:52.173-07:00"
        }
      ],
      "customerLocation": "BPNS7777777777XX",                                   # demand location, Berlin
      "demandCategory": {
        "demandCategoryCode": "A1S1"                                            # After-Sales
      }
    }
  ],
  "materialNumberCustomer": "500009086",
  "customer": "BPNL8888888888XX"
}

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

[nhaenis]

@modeling_team

[agg3fe]

duplicate of #262
Still tracking this issue.