Life Cycle of a Standard
This short note summarizes the Standardization Logic along REPOSIT. Engineering, Standardization and Certification are tightly coupled:- Engineering Outputs at System's Level: It stands for a set of Top System and subsystem Specifications giving birth to REPOSIT standards.
- System requirements Defs & Breakdown Structure.
- Subsystems requirements Defs.
- Interfaces & Specs. (ICD)
- Selection of Specifications to be transformed into standards and identification of Domains of already existing standards and bodies.
- Optimization of REPOSIT is a cycling process going beyond of current REPOSIT system study. Future optimisations are addressed along results document.
The lack of e-safety standards for defining service levels to vehicular applications lead the field open to investigation on new trends, however, only best potential targets should be investigated according with existing technologies. In REPOSIT we establish some frontiers between the achievable right now for e-safety applications using RGNSS (Link to RGNSS). This is the cornerstone to future certification of REPOSIT systems.
- Not yet issued e-safety standards for Drivers Assistance Systems (DAS) may be design drivers and also critical for certification. The risk of Certification failure of a DAS (e.g. REPOSIT) due to non compliance to lately issued mandatory Standard forces us to draft interim Standard containing the best possible guess requirements on time for proper engineering. consideration.
Awaiting for the setting up of a European Road Safety Authority due to approve such standard and application rules, an interim procedure with CEN, called CEN Workshop would gather comments and blessing of most concerned entities and ensure a reasonable maturity of the interim standards
