Digital twins
Aplark Twin
Model the system before changing the system.
Aplark Twin is a direction, not a product: modelling the system and its operating environment closely enough to predict what a proposed change would do to the assurance argument before the change is made.
The problem
Change is the expensive part
On a certified system the cost of a change is dominated not by the engineering but by the re-evidencing: which claims does this touch, which evidence does it invalidate, what has to be re-run. That question is usually answered by a meeting.
Answering it from a model of the system — before committing to the change — is the point of a twin in this context.
How it works
How it is intended to work
The direction under consideration is to model the system, its ODD and its assurance argument together, so that a proposed modification can be evaluated for its effect on the evidence base rather than only on behaviour.
This is early. It is on the platform architecture because the evidence and argument schema are being designed now to hold it later.
Capabilities
What it does
Change impact on the argument
Intended to identify which claims and evidence a proposed change would invalidate, before the change is made.
Environment and system modelling
Under consideration: representing the system and its operating environment jointly, so that ODD-affecting changes are visible as such.
Who it is for
- Programmes maintaining certified systems through modification cycles