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]: SIS Shopfloor Information Model: SISReturn #230

Closed
5 tasks done
wehrstedt-jan opened this issue Jul 6, 2023 · 2 comments · Fixed by #259
Closed
5 tasks done

[New Model]: SIS Shopfloor Information Model: SISReturn #230

wehrstedt-jan opened this issue Jul 6, 2023 · 2 comments · Fixed by #259
Labels
MS1_Approved Checklist "MS1 Request for Model Developement" is approved.

Comments

@wehrstedt-jan
Copy link
Contributor

wehrstedt-jan commented Jul 6, 2023

Model Description

The shopfloor information results contains the forecasting information exchanged between the Modular Production and a second party (customer, logistical etc.).
The forecasting information gives an overview about the current processing state of a product and the estimated production date.
This information will be exchanged between the partners either on request, cyclic with a fixed cycle or on notification, if a forecast is changing.

Relevant Standards

Example Data

SMC Property mand./opt. Semantic ID Remark
header RequestID mandatory
CommunicationMode mandatory enum (synchronous, cyclic, notification)
body ListOfForecastItems mandatory List of ForecastItems list containing all order items
ForecastItem*
ProductionForecast mandatory datetime Date of Production
ProductionStatus mandatory enum(orderReceived, orderPlanned, orderInProduction, orderCompleted, orderPostponed, orderCancelled)
ForecastDate mandatory datetime Date of forecast calculation
ForecastCertainty mandatory Certainty for the forecast date 0,0 .. 0,33 / 0.34 .. 0,6 / …
Reason4Delay optional enum(maschineFailure, supplyProblems) not every factory will provide too many information
IterationNo optional int this parameter is only required in the case of the notification mode. It continiously counts the number of updates to gurantee that the notifications are in the correct order.

MS1 Criteria (already done in #180)

  • 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
@wehrstedt-jan
Copy link
Contributor Author

modeling_team

@bs-jokri
Copy link
Contributor

bs-jokri commented Jul 6, 2023

MS1 already done in #180 separate ticket required track both models separately.

@bs-jokri bs-jokri added the MS1_Approved Checklist "MS1 Request for Model Developement" is approved. label Jul 6, 2023
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
2 participants