eclipse-tractusx / eclipse-tractusx/sig-release
ECU Certificate Signing Requests
- Dominant language
- Go
- Stars
- 12
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Feature/Standard Name: **ECU Certificate Signing Requests**
**Introduction**
• Brief Overview: Available Aspect Model needs standardization and additional process definition: standardized data transmission approach applicable for all OEMs and Suppliers.
**Key Benefits**
• Implementation and maintenance costs reduction
• Standardized data exchange channel via Catena-X allows to cut-off custom solutions
• Scalability
• Quick rollout
**Problem Statement**
• Current Challenges: Since no standardized data transmission approach is currently available, there is a need to develop individual endpoints for each customer/supplier. This generates additional implementation and maintenance costs and minimizes the positive effect of Catena-X implementation.
**Proposed Solution**
• Standardization of the Aspect Model and ECU Data Transmission process.
**Implementation Plan**
Steps to Implementation/Work packages:
• Standardize ECU CSR Aspekt Model
• Establish ECU data transmission process.
Requested by Kharkhan Olga SBR EZDB .
Feature created by Jochen Fischer
Contributor guide
Research direction
Start with the issue's proposed solution and implementation work packages: standardize the ECU CSR Aspect Model and establish the ECU data transmission process. Done means these two areas have a defined standardized approach applicable to OEMs and suppliers; the payload names no files, tests, or entry points.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100