Evidence

None of these is a service desk.

They all run on the same engine that is certified for service management. That is the proof of versatility: the anatomy of a process — intake, classification, validation against sources, meeting a deadline, auditable evidence — is the same in a support ticket and in the audit of a taxpayer.

Tax administrationProcess orchestration (BOAT)

Taxpayer audit and enforcement at national scale

The problem

Enforcement depended on manual cross-referencing between sources that did not talk to each other. The auditor's judgement was sound; the process feeding it was not.

The architecture

A governed process consuming 120 information sources, applying explicit selection rules and leaving evidence for every action taken. Data are objects of the model, not attachments.

The result

Traceable case selection: why each file was opened, on what data and under which rule — and a three-year backlog of pending cross-checks, eliminated.

1 billion records per day · 120 sources

HealthcareIntelligent document processing

Medical claims audit

The problem

Auditing medical claims requires more than 700 validations per case against external sources. Doing it entirely by hand condemns you to sampling — and to spending expensive judgement on the trivial.

The architecture

Automatic document classification and reading, validation against nine external sources and rule-based routing. The process defines what gets automated and what escalates to human judgement.

The result

70% of items audited automatically · 90% less onboarding time for a new auditor · document classification more accurate than manual.

120 million documents per month · 19 sources

Government — educationProcess orchestration (BOAT)

Citizen services for a capital city

The problem

Two million parents, 2,100 schools and 50,000 teachers filing requests through every available channel, with legal deadlines to meet and no way to demonstrate compliance.

The architecture

Multichannel intake with automatic classification and routing, deadlines measured against real operations, and evidence per request. Each type of procedure is a catalogue offering with its process behind it.

The result

99.5% of service agreements met · 98% satisfaction · 120 staff redeployed to mission work. Nobody was let go: they were reassigned.

8,000 requests per day · peaks of 80,000

Energy — critical infrastructureStrategy execution management

Nuclear power plant indicators

The problem

Operating indicators had to be consolidated from the reactors and reported to an international body, with integrity requirements that tolerate no intermediate spreadsheet.

The architecture

Continuous ingestion from plant systems, indicators calculated on governed data, and the report generated as the output of a process with owners and evidence.

The result

A regulatory report produced by an auditable process, not by manual consolidation.

1 TB per day from the reactors

Financial servicesStrategy execution management

Managing a bank's strategic plan

The problem

Strategy lived in slide decks and tracking in spreadsheets. Nobody could answer, at any given moment, whether an initiative was on track.

The architecture

Seventy indicators consolidated from six systems, each tied to the objective it verifies. It is the full traceability chain, applied to the strategic layer.

The result

Strategy execution as a measured process, not a quarterly report.

70 indicators · 6 source systems

Government — central administrationStrategy execution management

Budget execution and supplier payments for a national government

The problem

A presidential directive ordered an end to late supplier payments — and demanded visibility over budget execution. Neither could be answered: payment ran on paper trails and budget availability was known weeks after the fact.

The architecture

Budget planning, programming and execution modelled as governed processes, with the payment cycle measured end to end and budget availability visible in real time — across every institution of the central administration.

The result

Payment times cut from 120 to 11 days · 96% of invoices paid within 30 days. A directive from the top, executed as a measured process.

128 institutions tracked · payment cycle measured end to end

Government — sector regulatorProcess orchestration (BOAT)

An entire public entity operating on BPM

The problem

Every process — strategic, mission and support — ran manually. Tracking happened verbally between offices, and management reports were assembled by hand.

The architecture

The entity's full process map implemented on one platform, with the sector's regulatory requirements built into the processes and management indicators computed from the operation itself.

The result

Not one automated process but a public entity governed, measured and audit-ready on a single platform.

18 processes · 53 subprocesses — the whole entity

Government — national authorityIDP & document management

Records management under archival law

The problem

The entity could not demonstrate compliance with archival law, the zero-paper policy or ISO records standards. Document processes left no trace, and the same file could exist in several inconsistent versions.

The architecture

The full document lifecycle integrated into the processes: retention and appraisal schedules applied by the system, a single filing window for everything that enters, and internal and external correspondence automated with evidence per document.

The result

Archival compliance demonstrated from the system itself: retention, filing and correspondence leave evidence a records auditor can verify.

Entire document lifecycle · single filing window

Energy — state utilityITSM platform

IT asset management across 80,000 workstations

The problem

A national utility had no automatic control over its IT estate: inventory was stale the day it was compiled, and preventive maintenance meant sending technicians across a country.

The architecture

Centralised asset management with remote administration: live inventory, remote preventive and corrective maintenance, and service levels measured on the actual operation.

The result

Support times and travel costs down, service levels and infrastructure availability up — from one point of control.

80,000 workstations across one country

Retail — listed companyITSM platform

SOX compliance over the IT estate

The problem

A listed company was obliged to demonstrate SOX compliance and could not: its network topology made version control and device management impossible to evidence.

The architecture

Asset management with controlled release of updates and versions, automatic management of mobile devices, and monitoring of the availability and capacity of security equipment at every site.

The result

SOX compliance demonstrated from the asset platform: release control, device inventory and equipment availability, with evidence.

280 stores and sites nationwide

Verifiable in public procurement

Regulated organizations that renew, year after year

The hardest evidence in these cases is not a metric — it is continuity. In public procurement every renewal is a competed, published process. Several of the organizations behind these cases have renewed this platform for more than a decade; the record is public, and in an evaluation we will show you where to verify it.

19 years
the longest continuous relationship — a justice-system entity, from 2005 to today
2006
a financial regulator has operated the platform since
12+ years
of renewals managing the IT estate of a capital city's public schools

About these cases

We present them by sector, not by brand

Naming a client in published material requires their authorisation, and several of these organizations operate under confidentiality restrictions we respect. In an evaluation conversation we share the names, the implementation detail and — where the account authorises it — the contact so you can verify it directly.

Request the detail of a case