Reversibility
A supplier you cannot replace is not a partner, it is a dependency. Reversibility is prepared during the project: documented formats, established ownership of the code, skills transferred.
Written into the contract
The following are settled during framing and appear in the contract, before the first delivery.
- Ownership of the code produced and of the documentary deliverables.
- Export formats for data and configurations.
- Time to return and the form the return takes.
- Support to the incoming supplier, its duration and its scope.
Skills transfer
Architecture documentation, operating procedures and team training are part of the scope, on the same footing as commissioning. A client team unable to operate what it has been given has not received what it paid for.
Shared at pre-qualification
This material is provided to an identified organisation once the request has been qualified.
- Reversibility policy and template exit plan.
- List of export formats by type of system.
- Template handover file delivered at the end of an engagement.
The other areas
- SecuritySecurity is built into the system lifecycle, from design to decommissioning.
- Data and sovereigntyData entrusted to us remains the property of the client organisation.
- ContinuityContinuity is proven by a restoration exercise, not by a document.
- ComplianceNo certification is displayed until it is obtained and verifiable.
- TransparencyWhat is public, what is shared, what never leaves.
Consultations · Pre-qualifications · Partnerships
Let’s discuss your project.
Describe your priority, its operating context and the intended outcome. We will route the enquiry to the right person.