Access Official Technical PDF

Share Summary:LinkedInEmail

Robotic process automation can help organizations handle repetitive, rule-driven work without waiting for every underlying system to be replaced. KLP, Norway’s largest pension company, described using software robots in pension case handling in its 2017 annual report. Its experience offers a useful example for industrial automation leaders assessing how to automate administrative processes alongside established IT systems.

The context matters: KLP administered public-sector occupational pensions, an area shaped by extensive regulation and detailed processing rules. The company reported that it had automated 16 processes in the pensions area during 2017. It also noted good delivery quality and shorter lead times for putting new processes into operation than with traditional IT development. These are reported outcomes for KLP’s work at that time, not a guarantee that automation will produce the same results in other settings.

Robotic process automation for rule-based workflows

In this context, “robots” meant software automation, not physical machines on a production line. KLP distinguished between cognitive robots, which learn, and automation that follows defined rules. Its work focused on the latter: automating tasks where the steps and decisions could be specified in advance.

That distinction is important when evaluating a workflow. A process is a stronger candidate for rule-based automation when its inputs, decision criteria, and expected outputs are sufficiently defined. When a case requires interpretation or judgment, automation may be better suited to handling routine steps while leaving the decision to a qualified employee.

KLP’s pension processes were heavily regulated and rule-driven, which the company identified as a good starting point for robot technology. The broader lesson for automation teams is to assess process characteristics before selecting a tool. A task being repetitive is not, by itself, enough: teams also need to understand how exceptions are handled and where human judgment is required.

How software robots can support case handling

KLP said that, while its systems took time to replace, robots could handle rule-driven case management faster and more accurately than a person. The company’s stated aim was not to remove the role of case handlers, but to let them spend less time on routine work and more time on tasks requiring judgment and customer service.

This division of work is relevant beyond pension administration. In industrial organizations, office and support workflows can sit alongside production systems and involve repeated data handling, checks, or routing steps. Where a process can be clearly defined, software automation may offer a way to streamline those steps while preserving human oversight for ambiguous cases. The value depends on matching the automation to the work, rather than assuming every activity should be automated.

KLP also linked its automation efforts to rising demand for individual pension guidance and digital self-service. The company was developing a digital pension guide intended to help members understand the consequences of different choices. This shows how process automation and customer-facing digital services can form part of a wider transformation effort, rather than being isolated technology projects.

Automation is not a substitute for IT modernization

KLP explicitly cautioned that automation should not stand in the way of long-term development work. The company was also working to establish a forward-looking pension platform, adapt systems for new pension arrangements, and improve digital services. Software robots could help bridge the gap while existing systems remained in use, but they were not presented as a replacement for platform development.

For technical decision-makers, this is a central planning consideration. Automation can address selected tasks within an existing environment, but organizations still need a roadmap for the systems and processes beneath them. Without that wider view, a short-term automation project can become disconnected from platform modernization, process redesign, or changing business requirements.

A practical assessment can begin with a few questions:

  • Is the process rule-driven? Identify the steps and decisions that can be expressed clearly.
  • Where are exceptions handled? Define when a case must be routed to a person for review.
  • How will quality be assessed? Establish how the organization will check that automated work meets its requirements.
  • What is the long-term system plan? Consider how automation fits with platform changes and other digital initiatives.

These questions reflect the issues raised by KLP’s account; they are not a detailed implementation specification. Each organization will need to evaluate its own process, controls, and technology landscape.

Lessons for automation leaders

KLP’s 2017 experience illustrates a measured approach: begin with processes suited to explicit rules, use automation to take on routine work, and retain people for activities that need judgment. The company reported positive early experience across 16 automated pension processes, including good delivery quality and shorter implementation lead times compared with traditional IT development.

For industrial automation engineers, system integrators, and operations leaders, the wider implication is that digital automation extends beyond equipment and production lines. Administrative workflows can also be assessed systematically, particularly where work is repetitive and governed by clear rules. The strongest approach is to treat robotic process automation as one component of a broader digital strategy—supporting employees and service delivery while remaining aligned with long-term IT modernization.

Access Official Technical PDF

About The Author