Diverse, outdated and full of legacy issues: the file management in the RSZ urgently needed to be modernized in 2015. Smals opted for a modular approach with software reuse high on the agenda. The result is an optimized software environment that can serve as a basis for future projects.

The relationship between an individual or employer on the one hand and the National Social Security Office (NSSO) on the other was not entirely clear from a digital perspective in 2015. A large number of systems that were not synchronized resulted in cumbersome processes. More than 1,000 employees in the RSZ worked anything but optimally. For example, they sometimes had to switch applications multiple times to complete a single task and solve a specific question. That cost time, but also (tax) money.

On to the better. In 2015, Smals, the joint ICT organization of public social insurance institutions, launched a major digitization project. Various processes and systems, some of which were based on legacy, were not allowed to put a damper on the plan. Right from the start, Smals decided on a new and state-of-the-art IT architecture. The vision was clear: the RSZ needed to be able to manage files across the different services from a system that puts the customer and user at the center.

Not a big stone, but lots of small stones

The solution would not be a monolith. In 2015, Smals decided on a vision based on modular and reusable building blocks. With these building blocks, the IT specialist created a system that is now referred to as “Wave”, a holistic digital working environment. It’s a comprehensive environment where users have access to all the features that matter to them from a central dashboard. Relevant applications are integrated into this dashboard via APIs.

The components, with their own functionality, work for the entire user – but in reality they are web components and microservices maintained by different teams. “These microservices run in containers in the G-Cloud,” explains project manager Joost Cammaert. “That brings scalability.”

The microservices run in containers in the G-Cloud.”

Joost Cammaert, Smals project manager

This scalability is a huge advantage. In the past, if the RSZ had to complete a large task, such as contacting thousands of companies, this had to be planned in batches. Today, the infrastructure simply scales to handle such temporary high demand on the IT system.

agile

Development is also more modern with this approach. Since the beginning, Smals has worked in an agile framework in which different teams work together on a product. For Wave itself, there are four development teams and a support team, each consisting of five to ten people. They form the main structure.

The business applications then fit in. These can be teams at Smals itself or at Wave customers. In total, another ten teams are working on this modular functionality for the work environment.

The components themselves are flexible, customizable and, above all, reusable. At Smals, the focus is on reusability and for new projects we always check whether something already exists, whether new functionalities need to be developed and, if so, whether they can serve more than one purpose.

The RVA is participating

In the case of Wave, Smals actually developed a blueprint for a digital dashboard for file management. Thanks to its architecture based on microservices and APIs, Smals’ work can also be recovered from other government services, social security or otherwise.

Smals himself is preparing for such a future. Wave also includes one board with stakeholders. In this case those are Smals, the RSZ and the NEO. Wave is now also in production at the latter. Other institutions can join in immediately and become partners. This means everyone involved can influence the further development of the functionality of the work environment.

Smals does SaaS?

Will Smals suddenly become a SaaS specialist? It doesn’t happen that quickly, but the model surrounding the reuse of software modules certainly has similarities. Finally, the software developed by Smals can be deployed to various “customers” (government agencies). The architecture allows for adaptability so that each party has its own work environment with relevant applications integrated.

For example, RSZ and NEO operate in an environment based on the same components, but not effectively on the same platform. Both Wave environments run separately and are adapted to the organization. Feel free to make a comparison with Salesforce or SAP implementations at different companies: the same base developed once, another separate implementation.

Better and cheaper

Smals wants to take absolute leadership on reuse within the government. After all, it’s crazy (and too expensive) to develop something like file management five times for multiple institutions with the same needs. With “Wave” Smals proves that this is possible.

This editorial collaboration was achieved in collaboration with Smals. The article takes no position on Smals’ name. Are you interested in helping build digital government? Then take a look current job offer at the organization.