- Each ICT contract is linked to its provider and to the applications it covers, with its due date and its automatic renewal flagged.
- The exposure analysis follows an application or a provider up to the critical or important functions that depend on it.
- The Board keeps the decision and its rationale with the reviewed dossier. Authorized readers can find the evidence behind the choice.
Start with the function. Find the provider.
In ArchiLU: Payments → Payment Engine → Maelis Paiements. Four screens in the same application, connected through the same objects.
Identify what must keep running.
The function catalogue shows criticality, ownership and documented links. Critical or important functions are distinguished from supporting functions.
Understand why it is critical and what supports it.
The Payments record explains the impact of an interruption, names its owner and links to the Payment Engine application. Missing relationships remain visible.
Identify the provider: Maelis Paiements.
The actor registry opens the Maelis Paiements provider record, with its identity, status and role. The dependency chain links this same provider to the Payment Engine application and the ICT maintenance service.
See the dependency. Spot what is missing.
The dedicated view links Payments to its application, ICT services and documented providers. Contracts appear when they cover these services; missing links are identified for each object.
Enterprise Architecture · From €24,900 per year and organization, excluding VAT. Unlimited users.