[New Model]: Create Short-Term Material Demand Model based on Material Demand

[tom-rm-meyer-ISST]

Model Description

During discussion on using the MaterialDemand for the PURIS UC based on AAS / Digital Twins, we realized that we need a distinct Semantic ID.

Thus I would like to create a subclass / specialization of the demand.

Relevant Standards

• CX-0120 Short-Term Material Demand Exchange
• CX-0128 DCM Standard

Example Data

{
  "unitOfMeasureIsOmitted" : false,
  "demandRate" : {
    "demandRateCode" : "WKS"
  },
  "unitOfMeasure" : "unit:piece",
  "materialDescriptionCustomer" : "Spark Plug",
  "materialGlobalAssetId" : "urn:uuid:48878d48-6f1d-47f5-8ded-a441d0d879df",
  "materialDemandId" : "0157ba42-d2a8-4e28-8565-7b07830c1110",
  "materialNumberSupplier" : "MNR-8101-ID146955.001",
  "supplier" : "BPNL6666666666YY",
  "changedAt" : "2023-11-05T08:15:30.123-05:00",
  "demandSeries" : [ {
    "expectedSupplierLocation" : "BPNS8888888888XX",
    "demands" : [ {
      "demand" : 1000,
      "pointInTime" : "2023-10-09"
    } ],
    "customerLocation" : "BPNS8888888888XX",
    "demandCategory" : {
      "demandCategoryCode" : "0001"
    }
  } ],
  "materialNumberCustomer" : "MNR-7307-AU340474.002",
  "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
• A modeling steward has been assigned

[tom-rm-meyer-ISST]

Modeling_Team

[tom-rm-meyer-ISST]

After discussion with DCM team, we won't create shared aspect models for common things. We just do things common. Closed the issues