Mainframe Migration Project Kickoff

1
Mainframe MigrationProject Kickoff

• A Partnership for Success
• North Dakota Information Technology Department
• Software AG

November 8, 2005
2
Agenda

• Welcome Linda Weigel
• Introduction Mike Ressler
• Project History Dean Glatt
• Assessment results Dennis DeBruin
• Next steps Linda Weigel
• Q and A Everyone

3
Introduction
Mike Ressler Deputy CIO Director of ITD
4

Monthly CPU Revenue Generated by Agency 12 Month
Average
5
Project Organization
6
Project Organization
7
Project History
Dean Glatt Project Sponsor Director of Computer
Systems Division
8
Project Scope

• Migrate existing systems from a mainframe to a
  Linux platform.
• Phased approach
• First agencies during spring of 2006
• Complete by summer of 2007

9
Project Objective

• Deliver a like-for-like migration of mainframe
  systems.
• No changes will be made with respect to the
  functionality of the system
• Minimize impact to the business and end users of
  the system
• Providing more options in the future as business
  needs change

10
Assessment
Dennis DeBruin Project Manager Software AG
11
Migration Inventory

• Natural Objects 31,800
• Cobol Objects (including copybooks/CICS
  maps) 5,200
• Fortran Programs 250
• Assembler Programs 220
• TSO/REXX Programs 500
• Dyl280 Programs 4,770
• JCL (control cards, processes, includes) 31,000
• Total Objects 73,740

12
Recommended Project Approach

• Divide applications into 4 groups
• Why did we divide them into 4 groups?
• Complexity
• Interfaces with other agencies
• Agency input
• Install new development tools (Natural and Cobol)
• Perform Proof of Concept for OVM solution
• Perform Proof of Concept for printing and address
  validation solution

13
Testing Expectations

• Develop business use cases
• Ensure that business functionality is the same
• Develop expected scenarios
• Same results from screens
• Same results from batch programs
• Benchmarking systems
• Ensuring that new system operates efficiently

14
Training Expectations

• End-user training
• Any new features or changes in business process
• Platform training
• Terminal Emulators at the client end
• Linux familiarity training will also be made
  available
• Process training
• Some internal IT processes will change
• Monitoring, change management and others
• IT Training
• System Administration Training
• Database (DBA) Training
• Developer Training

15
Project Control

• Strong Change Management
• Strong North Dakota management involvement
• Consistent Communications Plan
• Develop clear benchmarks and standards for the
  new Linux environment
• Adhere to North Dakota Project Management
  Standards and Practices

16
Next Steps
Linda Weigel Project Manager ITD
17
Next Steps

• Prepare Final Migration Plan
• Review Proposed Groupings
• Create Training Plan
• Schedule Meeting With Agencies Personnel
• Finalize Project Schedule

18
Next Steps

• Begin Implementation Phases
• Determine Key Personnel
• Create Testing Plan
• Configure Server
• Migrate Data
• Implement Test Plan
• Compile Results Acceptance
• Go Live

19
Communication Plan

• Web Site --- www.nd.gov/itd
• Status Reports will be completed weekly and
  posted on website
• Bi-Weekly face to face meetings between Project
  Managers and key resources
• A post-phase review for the end of each phase
• Regular communication to Executive Committee
• Issue Risk Tracking will be done via North
  Dakota Project Management system (WMS)

20
Q and A