1. Department of Information Technology Billing System (TUAM) Project Close Eric Aragon 22 April 2013

2. 2 DoIT Billing System Project Objectives: Laws of 2011, Ch. 179, Section 4, Department of Information Technology (3) Equipment Replacement Revolving Funds and FY12 Operating Funds (20310) The DoIT Billing System project is in response to a the Department of Information Technologies (DoIT) need to: Ensure timely delivery of accurate invoices, Replace an unsupported mission critical application (CIMS), Provide secure, online detailed invoice information for DoIT customers and Streamline internal billing processes.

3. DoIT Billing System Project PCC Approved Funding History: Laws of 2011, Ch. 179, Section 4, Department of Information Technology (3) Equipment Replacement Revolving Funds and FY12 Operating Funds (20310) $417K Project Implementation  $100K certified on 10/26/2011 for project planning, license support and reinstatement  $210K certified on 2/22/12 for project implementation (Mainline Contract)  $107K certified on 6/20/12 for ODBC Driver and Project Manager services. 3

4. DoIT Billing System Project Schedule Performance: Completed Project On Time  Initiation Phase Cert. – Dec 15, 2010  Planning Phase Cert. – Oct 26, 2011  Implementation Phase Cert. - Feb 22, 2012  Mainline and ACRO on site May – Nov 2012  Cut-over to Production – Nov 9, 2012  Training (~150 agencies) – Nov thru Jan 2013 411/30/12

5. DoIT Billing System Project Budget Performance: Exceeded Budget by $3K  Actual Professional Services$311K  Planned Professional Services$310K Difference$1K  Actual Software Cost$109K  Planned Software Cost$107K Difference$2K 511/30/12

6. DoIT Billing System Project Transition to Operations: DoIT Billing System Sustainment Plan  Billing Team will own TUAM software, data integrity and renewal of software and maintenance license.  System Services (Unix Team) identified Mike Owens as the Systems Admin to support upgrades and technical support. 611/30/12

7. DoIT Billing System Project Lessons Learned: Include technical resources in Planning and gathering requirements:  Ensure Development and Production licenses are purchased upfront.  Better forecast user load and allocate enough disk storage upfront.  Understand the implications of selected software platform, OS, etc. e.g. Unix vs. Windows Involve customer to understand how many user Id’s are needed up front. 711/30/12

8. DoIT Billing System Project Lessons Learned: Weekly project team meetings was effective:  Tracking Action Items  Up to date project schedule  Monitoring risks and issues All stakeholders were engaged throughout the project and completed action items on time. ESC was engaged and helped resolve issues as needed. 811/30/12

9. 9 Thank You……. Questions?