Technology and digital systems
Process knowledge transferred into an independently tested digital core process.
Software developed in-house for a public authority – from preserving long-standing experience through independent testing.
Starting point
Critical process knowledge could not be lost with the generational handover.
Contribution rates and total contributions were derived from numerous data sources, processing steps, special cases and controls. A substantial part of the process logic rested in the experience of the person who had carried primary responsibility for many years.
Before that person left, the knowledge had to be captured in full, clarified with the specialist team and transferred into a standardised, traceable digital process. Four-eyes control, documented changes and an immutable record after the final decision mattered just as much as automation.
PERCEL role
Made specialist law, software, testing and the legacy system work together.
- coordinated requirements, priorities and releases
- translated the business process into testable software requirements
- structured import, correction, logging, control and export logic
- maintained change records, release notes and approved versions
- supported locking logic with archive and integrity checks
- developed legacy exports further and integrated them into the annual process
- clarified testing, audit and security questions between the parties
Software background
In-house development rooted in direct process responsibility.
PERCEL developed the procedure itself, bringing specialist knowledge, process logic, data processing, controls and legacy integration together in a productive application.
That operational experience now provides the foundation for capturing complex business logic precisely, structuring it technically and assessing its quality on a sound basis.
Result
A standardised core process with independently confirmed procedural assurance.
The productive procedure guides users through eight specialist stages, documents changes, supports four-eyes control, generates legacy exports and records completed contribution years traceably. Knowledge previously held by one person was transferred into a process that could be used and handed on permanently.
An external auditor tested the software procedure under IDW PS 880 revised and issued the corresponding attestation. Documented annual releases and a later security review kept the procedure open to controlled further development after the original knowledge transfer.
Critical public-sector process?