UNMS/NVSM is one of the main Healthcare Insurers Organizations (Mutualités/Mutualiteiten) of Belgium. In order to make their application independent of its local federations, UNMS/NVSM decided to reengineer completely its IBM Mainframe applications (> 12 Mio lines of code), helped by NRB in this complex project. The content will be of value for all IT decision takers confronted with a major Software reengineering project.

1. UNMS
Direction Informatique
NRB Mainframe Day
UNMS : Code Discovery and Reengineering
Union Nationale des Mutualités Socialistes
Christophe Danhier – IT Director
NRB
Frédéric Van de Weerdt – Project Manager

2. Agenda
1. Introduction UNMS
2. Scope of the project
3. Initial project planning
4. Situation of the project
5. Conclusions : UNMS and NRB

3. 1. Introduction UNMS
2. Scope of the project
3. Initial project planning
4. Situation of the project
5. Conclusions : UNMS and NRB

4. L’Union Nationale des Mutualités Socialistes
A few words
Our missions :
- Manage, on behalf of the Belgian State, the mandatory sickness and
invalidity insurance and defend its affiliates under negotiations with
health providers.
- Grant benefits to its affiliates under the supplementary insurance.
- Provide its members with information and services linked to health,
social rights and have legal ability to defend its members.
UNMS today :
- 3,033,982 members. That positions us as number 1 in Wallonia,
number 2 in Belgium.
- 4,664 collaborators .
- 880 branches and more than 6 million contacts through agencies.
- 14,550 million reimbursements
- 131 million euros additional allowances.

5. 1. Introduction UNMS
2. Scope of the project
3. Initial project planning
4. Situation of the project
5. Conclusions : UNMS and NRB

6. Scope of the Chrysalide project
The ‘Mutualités Libérales (400)’ have decided to use, with clear agreement
from the ‘Mutualités Socialistes’ (300), the Business Applications used
internally by ‘Mutualités Socialistes’. The objective is to use the same
environment 300-400 regarding the applications, data structures, and
databases, but on separate Logical Partitions (fully independent and secured
from each other)
Two major initiatives were required :
• Stream 1 : Adapt and re-engineer IT applications of UNMS and make them
independent of the insurer using it. Stream 1 has been won by NRB.
• Stream 2 : Migrate production data (including history) from the ‘Mutualités
Libérales’ to the Mutualités Socialistes. Stream 2 has been won by another
third party.
The aim being to ensure that the ‘Mutualités Libérales’ can use in production
their new IT environment no later than January 1st, 2015.

7. 1. Introduction UNMS
2. Scope of the project
3. Initial project planning
4. Situation of the project
5. Conclusions : UNMS and NRB

8. Stream 1
Adaptation of UNMS programs as described in the RFP

9. High Level planning ( final validation after discovery phase )

10. Joint UNMS/NVSM - NRB Project Team
UNMS – NVSM
Project Director: René Lamproye
Project Teamleaders
UNMS - NVSM
Business Analysts
Experts / testers
Project Management:
Philippe Juszczak - Marc Peeters
Project Manager:
Frédéric Van de Weerdt
Business Analyst Team
End to End Technical Manager
Build Manager
Test Manager
Technical analyst Developpers PL1Reviewers
UNMS – NVSM

11. 1. Introduction UNMS
2. Scope of the project
3. Initial project planning
4. Situation of the project
5. Conclusions : UNMS and NRB

12. Chrysalide Project
Status today

13. Chrysalide Project
Discovery and Execution
Discovery
• Define scope
• Inventory applications + “Trashing”
• Define process, roles and responsibilities
• Define Cookbook (conversions rules / pattern)
• Tuning Tool
• Training NRB Team
Execution
• Analysis
• Development
• Testing
• Reviewing
• Cookbook upgrading
• Tuning Tool, Process
• Training NRB Team

14. Chrysalide Project
Status as of 13 May 2014
Discovery
2013 2014
08 09 10 11 12 01 02 03 04 05 06 07 08 09 10
Execution

15. Chrysalide Project
Cookbook
Reference document
Standardisation
Quality
Cookbook = Work in Progress
=> Continuous improvements

16. 1. Introduction UNMS
2. Scope of the project
3. Initial project planning
4. Situation of the project
5. Conclusions : UNMS and NRB

17. UNMS – NVSM Conclusion
Key points of our collaboration with NRB
• Planning and budget respected through the project.
• Flexibility of the NRB team (100% local team based in Belgium)
• The project allowed us to improve some weaknesses in terms of
governance and methodology within our organization.
• The discovery phase detected about a million obsolete code lines
allowing a cleaning to be performed.
• On these points and many other aspects, we will benefit from our
collaboration on a long term :
• Status and library of ALL codes developped at UNMS
• Code Cleansing
• Cookbook
• …….
And all of this thanks to a close and excellent collaboration between the
UNMS and NRB Teams with the common goal of 1/1/2015 !

18. NRB Conclusion
A long experience in migration projects of > 25 years
(Point NRB – Suivi du projet)
Date Migration type Migration
1989 Application Credit Communal / Implementation Mega and Mega into Ethias
applications
1990 Application-Data CILE / ReBuild
1991 Application-Data SWDE / Rebuild
2002 Application-Data ALG / ReBuild
2004 – 2005 Application ALG Negoce / ALG => ALG Negoce
2006 – 2008 Application-Data Sibelga / Clearing House (MIG 3.53)
2008 Application-Data Resa Gaz / Clearing House (MIG 3.53)
2008 Application-Data MRW – MET / Merger Budget accounting MET and MRW
2009 – 2010 Application SPW - SEPA
2009 – 2010 Application-Data Sibelga – Resa Gaz / Clearing House (MIG 4.0)
2010 Application Ethias – Belfius / IBAN
2009 -2012 Application Ethias – Ame - Ame Life Lux – Belfius /
IBM PL/I for MVS & VM => IBM(R) Enterprise PL/I for z/OS

20. 20 NRB Mainframe Day
#mainframeday