Rollout stages
Survey
Processes, sites, existing infrastructure, external systems, master data owners.
Design decision
Module scope, deployment mode, and the split between standard functions, options, integrations and development.
Pilot
A limited scope covering the full right lifecycle and the denial scenarios.
Scale-up
Incremental onboarding of sites and modules without interrupting current processes.
Operation
Support procedures, policy updates and incident review.
What the pilot scenario must cover
A pilot is conclusive only if every state has been exercised — including the abnormal ones.
- Successful execution of a right at a control point.
- A denial for each of the defined reasons.
- A manual decision by an authorised operator with a stated reason.
- Automatic revocation on expiry or on a change of grounds.
- A WAN outage and offline operation of the control point.
- Restoration of the link.
- Synchronisation of offline events without duplication.
- Review of the results against the audit journal.
Business case
The business case is calculated on the customer's own data: volume of requests and approvals, effort spent by the security service and the pass office, number of sites and control points, share of manual operations, losses from downtime and from incident investigations.
Let us agree a pilot scenario
Describe the site and the process — we will propose a limited scenario that can be verified end to end, including denials and loss of connectivity.
Related pages
- For partners and integratorsWorking with designers and system integrators on IDMATIC NET: design support, scope boundaries, integration interfaces and joint pilots.
- MaterialsIDMATIC NET White Paper, platform presentation and overview video. Materials are being prepared for publication and can be requested by email.
- ContactsContacts for the IDMATIC NET platform: demonstration requests, pilot scenarios, partner and project enquiries. Manufactured by JSC "MTT Control".