Technical Documentation – Art. 11
Requirement
The technical documentation must be drawn up before placing on the market and kept up to date. It serves to demonstrate conformity to authorities.
Content According to Annex IV
The technical documentation must include at least:
General Description
- Intended purpose of the AI system
- Name and contact details of the provider
- Interaction with hardware or other software
- Versions of relevant software and firmware
- Description of interfaces (API, UI)
Design and Development
- Design specifications (architecture, algorithms, model structure)
- Design decisions and assumptions (including risk assessment)
- Description of the training, validation and testing process
- Training data documentation (origin, scope, characteristics)
- Metrics and thresholds used
Monitoring and Testing
- Test plans and results
- Validation methodology
- Cybersecurity measures (→ CRA synergies)
- Explainability/interpretability measures
Change Management
- Documentation of all material changes after placing on the market
- Versioning and change history
BAUER GROUP Implementation
The technical documentation is drawn up as an extension of the existing CRA technical documentation. Shared sections (product description, security architecture, update mechanism) are referenced, not duplicated.
Template: Provided on a product-specific basis.