Mainframe modernization of a pension administrator

Views in this map

1. 1
   TodayEvery channel calls the mainframe directly: CICS by day, COBOL batch by night.
2. 2
   Facade in frontAn API facade takes every call, the dashboards first. Nothing has moved yet.
3. 3
   First sliceMembers who joined since 2021 move to the member service; the rest stay on CICS.
4. 4
   Half and halfContributions, quotes and statements move. Only the pensioner payroll stays behind.
5. 5
   TargetThe mainframe is switched off. The facade is the API gateway; DB2 is archived.

Today ‹ › Facade in front ‹ › First slice ‹ › Half and half ‹ › Target

Flows to play

• ▷
  A contribution fileOne employer’s March file, from upload to money in members’ accounts: about 16 hours today, under an hour in 2028. In the Today and Half and half views, so the nightly wait disappears.
• ▷
  A dashboards find requestA member asks a pensions dashboard to find their pensions, answered from live records through the facade. In the Facade in front view.
• ▷
  One address changeThe same request from two members: one in the first cohort goes to the new member service, the other to CICS. In the First slice view.

The model behind it

53 records of 9 types. Every box on the map is one of them, so the filters and the record panel read the same data.

• Mainframe parts 17
• New services 8
• Data stores 6
• Phases 5
• Outputs 5
• Channels 4
• Cohorts 3
• 2 more types 5

Filters

Runs on and Moved in: pick a value and everything else fades.