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]: SimulationScenario #316

Closed
6 tasks done
dominikoeh opened this issue Sep 22, 2023 · 1 comment · Fixed by #330
Closed
6 tasks done

[New Model]: SimulationScenario #316

dominikoeh opened this issue Sep 22, 2023 · 1 comment · Fixed by #330
Labels
MS1_Approved Checklist "MS1 Request for Model Developement" is approved.

Comments

@dominikoeh
Copy link
Contributor

dominikoeh commented Sep 22, 2023

Model Description

Resiliency Kit/OSIM Team:

The "Partner Interface for scenario management" enables the exchange of scenario requests and the resulting simulation results between two OSim Manager instances. In addition, the interface enables the exchange of commands for the synchronisation of the scenario statuses.

In terms of content, it offers the possibility to exchange the following information:

  • Request for feedback on a scenario → requestScenarioFeedback() → is a request from a direct OSim partner (can go in both directions in the supply chain, depending on the scenario role) for feedback on the possible fulfilment of the described scenario. For more on the evaluation process at the requested party, see here.
  • Feedback → receiveScenarioFeedback() → enables the requester to transmit the result of his scenario-based evaluation to the requester.
  • Send a scenario state → pushScenarioState() → enables distribution of a new scenario state and a communication on the procedure and the binding nature.
    The following sketch represents the principle call sequence using the example "Supplier is the Scenario Owner". The other data flows are described below, but the procedure is identical.

Relevant Standards

  • BPNS
  • MaterialFlowSimulationResult

Example Data

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

@agg3fe agg3fe added the MS1_Approved Checklist "MS1 Request for Model Developement" is approved. label Sep 25, 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
Development

Successfully merging a pull request may close this issue.

2 participants