[PURIS FOSS] FOSS include Days of Supply implementation

[Clemens-L-Schwarz]

Overview

The PURIS FOSS Reference-Implementation, initially released with standards including ItemStock, DemandExchange, ProductionOutput, and DeliveryInformation.

We want to add now the Days Of Supply Standard (CX-0145).

Explain the topic in 2 sentences

Customers and suppliers may share days of supply information. These are partner specific projections for a time horizion of multiple days.

What's the benefit?

Implementation of an existing PURIS Standard as a new feature to the PURIS Reference Implementation (Dashboard). Supply chain partners are able to share information of their days of supply of a specific item with each other. The information can be e.g. used to check, indicate and evaluate a supply situation.

What are the Risks/Dependencies ?

• No dependencies, except EDC / DTR
• No risks

Detailed explanation

• Include the the Days Of Supply Standard (CX-0145) to the PURIS FOSS reference implementation
• Finish and test the backend functunalities for exchanging the Days of Supply data
• Implement and test the frontend visualization of incoming and outgoing (Roles: Supplier and Customer) Days of Supply Values

Current implementation

• currently only the backend integration is in place and was not tested

Proposed improvements

implementation of

• frontend integration
• EDC data exchange
• DTR registration

Feature Team

Contributor

@ReneSchroederLJ

Committer

@tom-rm-meyer-ISST

User Stories

• Days of Supply - Dashboard integration puris#311
• Days of Supply - EDC integration puris#312
• Create Test Cases for Days of Supply puris#454

Acceptance Criteria

• Days of Supply values can be send to a partner, eather in the role as supplier or as customer
• Days of Supply values can be received by a partner, eather in the role as supplier or as customer
• Incoming Days Of Supply values are displayed in the frontend, in both roles: as customer or as supplier
• C-X Styleguide is respected for the frontend implementation

Test Cases

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented:

• This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
    • CX-0010 Business Partner Number
    • CX-0013 Identity of Member Companies
    • CX-0018 Data Space Connectivity (EDC)
    • CX-0049 DID Document Schema
    • CX-0050 Framework Agreement Credential
    • CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
    • CX-0001 EDC Discovery API
    • CX-0002 Digital Twins in Catena-X
    • CX-0018 Data Space Connectivity (EDC)
  • Data Format:
    • The data model is based on a published Semantic Model
• The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• Potential risks or conflicts with existing architecture has been assessed

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

• I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)