jjeroch
commented
3 months ago Attention @rybtim : Upcoming PI Planning Preparation
As we gear up for the forthcoming PI Planning session, it is crucial that all features under consideration align with our established Feature Quality Standards and Definition of Done (DoD) guidelines. To ensure your feature is thoroughly prepared and stands a strong chance of being prioritized, please provide comprehensive documentation that includes the following components:
- Feature Summary: An executive overview that encapsulates the essence and objectives of the feature.
- Change Description:
- High-Level Overview: A succinct synopsis of the proposed changes and their overarching impact.
- Detailed Analysis: An in-depth exploration of the specific alterations, including a clear exposition of the anticipated impact on existing systems.
- Impacted Components: A list identifying all system components that will be affected by the feature implementation, accompanied by a brief explanation of the nature of the impact.
- Acceptance Criteria: A set of clearly defined conditions that must be met for the feature to be considered complete and acceptable.
- Test Scenarios: A detailed outline of test cases that cover all functional paths of the feature to ensure robust validation and verification.
- Risks/Dependencies
Please note that any feature submissions lacking these essential elements will not be eligible for consideration in the upcoming PI Planning. It is imperative that your documentation is both thorough and precise to facilitate a smooth and effective planning process.
Please let me know in case you have any questions
Grand-Thibault
rybtim
stephanbcbauer
Description
BPDM sharing members need to have the possibility of assigning multiple BPNLs to one overall BPNL in the portal as well as providing this information in the sharing process. This will serve as representation of the connection of a holding company and its subsidiaries. The knowledge of the relations between legal Entities (BPNL) enables the system to assign specific information or documents to several related BPNLs simultaneously. Additionally, it can be used for reliable and comprehensive reporting. This reduces manual errors and increases process efficiency.
The Catena-X portal needs to receive the information regarding connection of BPNLs from the BPDM Pool. This is relevant for setting the correct roles and rights for the onboarding process. As an example, for certificate management there should be one master user who is allowed to upload the certificates for several BPNLs. The portal needs to have the functionality to maintain certificates (different feature) and to maintain user roles on a master admin level (different feature).
Different types of BPNL relations should be considered. The willingness to share this information and validity of information regarding claimed BPNL relations need to be ensured in the process. Business needs and requirements for Legal-to-Legal Hierarchies: • Re-supply to the backends of the individual companies (e.g. MDGs) must be feasible • Making hierarchies visible, even for SMEs • The compatibility of the data model is guaranteed • Hierarchies are not publicly available data and must be editable for the individual sharing members; data sovereignty lies with the data owner • To do this, IaaS providers must be able to change/create the hierarchies (Upsert API) • MVP minimal requirement, 1:n hierarchy level for the authorization concept in the portal with one link level (Muster AG: Muster Technology) BPNL-BPNL --> evaluate m:n relationships
• currently "only" >50% shareholder shares represent n:1 relationships • Risk management can create correct risk assessments • Reduction of administrative effort in user management via an authorization concept in the portal • Contracts are concluded with the correct supplier (important in the event of insolvency) • Correct reports on, for example, sales with the supplier
Goals:
• Short-term goal, quick solution as PoC, simple visualization of single-level hierarchies à Eventually to be transferred into an app in the portal • Simultaneous start of evaluation of data model adaptation and process observation (proof that L is part of the company's own group) • Concept and first Mockups for visualization and own/existing BPDM data model • Implemented as a separate feature
Final conception for the topic of company hierarchies that takes into account all requirements of Portal, BPDM and EDC -> deriving necessary developments and adapting existing or creating new standards.
Impact
Additional information