Public institutions and utilities rarely lack systems. What they lack is something else: one coherent path that data travels between them. A national registry answers over one API, the financial ERP over a completely different one, SCADA controllers speak an industrial protocol, and the document archive keeps its own format. The result is manual retyping, data that drifts apart, and processes that grind to a halt on a single spreadsheet.
In our experience, the problem is not any one technology but joining worlds that were never designed to cooperate. Even without pointing to a named case study here, we supply the people who connect such systems every day: integration engineers, architects and specialists who understand critical infrastructure. We build the layer that ties registries, ERP, SCADA and archives into one predictable flow of data.
Why are public sector and utility integrations so hard?
Because an institution is usually layers of technology from different eras that nobody can switch off. A system built fifteen years ago runs a critical process and still works, so it stays, and new solutions pile up beside it. Over time you get an architecture where every component lives a life of its own.
Three things conspire at once:
- data silos - each department has its own system and its own version of the truth about the same citizen or metering point,
- legacy - older applications with no modern API, often undocumented and without an author left to ask,
- security and regulation - personal data, critical infrastructure and rules that forbid “just exposing an endpoint to the world”.
That is why you cannot treat an institutional integration like an ordinary project of wiring two apps together. You have to reconcile old with new without interrupting services that people rely on every single day.
What does integrating with national registries look like?
National registries are a species of their own. They impose their own exchange standards, access procedures and maintenance windows that you have no control over. So national registry integration is less about writing an API client and more about wrapping it so the rest of your systems never feel that a third-party, occasionally temperamental service sits on the other side.
In practice we build a mediating layer that translates registry formats into the institution’s data model, caches responses, handles authentication and signatures, and logs every request for audit. When the registry is unavailable, the system does not fall over; it queues the requests and retries them under agreed rules. The clerk or process inside the institution gets one stable interface instead of a raw connection to the outside world.
How do you connect ERP and financial systems to the rest of the organisation?
The ERP is often the heart of an institution, yet it is rarely open. We tie it to document workflow, line-of-business systems and registries so that financial data stops travelling by hand and flows through a controlled channel instead.
Most often we deliver this through:
- integration via APIs and a bus (ESB, API gateway) rather than brittle point-to-point links,
- synchronisation of reference data (counterparties, dictionaries, chart of accounts) between the ERP and line-of-business systems,
- automation of invoice and payment flows while preserving the approval path and the audit trail,
- reporting and statutory returns fed by data from several systems at once.
Consistency is the key here: if the same counterparty carries three different IDs in three systems, no automation will hold. So before we connect anything, we put the data model in order.
How do you integrate SCADA and metering without disturbing the OT world?
At a utility, the hardest boundary runs between IT and OT, between the world of business applications and the world of process control. SCADA, PLCs and metering systems live on an industrial network where uninterrupted operation and safety outrank integration convenience.
SCADA integration demands caution, because a mistake here does not mean an error on a screen but a real effect on the infrastructure. So we collect OT data through dedicated gateways and industrial protocols (such as OPC UA, Modbus, MQTT), buffer it, and only then expose the cleaned stream to business apps, analytics or billing. We let traffic run one controlled way, keeping networks separated, so the business side can read telemetry without ever gaining the ability to touch control. That split of responsibility is a foundation, not an option.
How do you fold document workflow and archives into one flow?
Electronic records management, repositories and digital archives are where a process most often stalls. We connect them to registries and the ERP so a document is created, circulates and reaches the archive without manual export and import.
In this area we usually:
- link records management with line-of-business systems, so the case and the document form one flow rather than two separate ones,
- automate metadata and classification based on data already held in other systems,
- wire in the archive in line with retention requirements and long-term preservation formats.
A well-connected document flow stops being a bottleneck and becomes a natural stage of the process, where data entered once never has to be typed again.
How do you make integrations reliable and secure?
An institutional integration has to keep working even when one of the systems briefly goes quiet. So we design it to be fault tolerant, not as a chain that snaps at the first broken link.
We rest it on a few pillars:
- message queues (such as Kafka, RabbitMQ) that decouple systems and absorb traffic spikes,
- retries and idempotency, so repeating a request never duplicates an operation,
- encryption in transit and at rest, plus access control aligned with the institution’s requirements,
- monitoring and a full audit trail showing who exchanged what data and when.
With this architecture, a registry briefly going dark or an ERP under load becomes an event the system handles on its own, not an incident that calls for a manual fix at dawn.
Which skills do we bring to an integration project?
For projects like these we shape the team around the specific architecture, not “just in case”. Most often we staff the roles of:
- an integration architect who designs the whole flow and sets the standards,
- backend and integration engineers (Java, .NET, Python) building connectors, APIs and the bus,
- DevOps and security specialists owning queues, infrastructure and hardening,
- OT / industrial specialists wherever SCADA and metering come into play.
We have real experience in projects for public administration and in systems integration, as well as in critical infrastructure, so we understand both the regulatory rigour and the realities of working with the OT world. We do not pin that to a single deployment, because here we are talking about the competence we bring into the client’s team.
How do we do it at RITS?
We work as a nearshore partner from Poland that adds the missing skills to an institution’s or a utility’s team. On integration projects that means we:
- staff the roles of architect and integration engineers trained to work with legacy and regulatory rigour,
- verify skills before the start and match the team to the specific architecture and protocols,
- join the client’s existing rhythm, code reviews and security procedures without a long ramp-up,
- bridge IT and OT while respecting network separation and critical-infrastructure requirements.
Most often we do this through team augmentation or a dedicated team, and where an institution builds a new integration layer from the ground up, as custom software created by our team.
Where to start with integrating systems in an institution?
Start from the single most painful flow - for instance the place where someone retypes data between a registry and the ERP every day. Describing that one path end to end reveals which connectors, which security layer and which roles you actually need, before you take on the whole architecture. We covered the differences between engagement models in our article on IT engagement models.
Tying national registries, ERP, SCADA or archives together in one institution? Let’s talk - we’ll match a team and an architecture to your system landscape.