Configuration control answers which exact product—with which components, software and settings—was tested. It supports repeatability, repair and partner trust.
Mission context
Prototypes change quickly. Without version records, images, specifications and tests may describe different machines, while repair can silently create another configuration.
Engineering approach
HARDY connects platform version, key components, changes, test reports and technical data sheets. Partner payloads receive their own compatible versions.
What must be demonstrated
The system should provide traceability without unnecessary bureaucracy.
- unique configuration identifier;
- change record and decision reason;
- linkage between test, repair and technical data sheet.
Limits and responsible claims
Public traceability does not reveal suppliers, volumes or sensitive components. Detailed structure belongs in the protected partner environment.