Executive Steering Committee Medicaid Eligibility System

Transcription

1 Project June 7,

2 Project Federal Regulations and CMS Enterprise Life Cycle Gate Reviews -2-

3 Purpose The ELC Reviews (gate reviews) will be used by the Centers for Medicare and Medicaid Services (CMS) to: Monitor the State s system development progress Provide technical assistance Determine if and when the release of federal financing participation (FFP) should occur (go/no decisions), and Ensure the system meets the CMS Seven Standards and Conditions for enhanced funding -3-

4 Framework Includes four formal gate reviews: Architectural Review (Plan Phase) Completed October 2012 Project Baseline Review (Plan Phase) Completed October 2012 Final Detailed Design Review (Design Phase) Target Date Early September 2013 Operational Readiness Review (Implementation Phase) Target Date December 2013 Interim consultations occur periodically prior to formal reviews There will also be an Annual Operational Analysis Review (OAR) which occurs annually during the Operations and Maintenance Phase after the implementation of Release

5 Upcoming ELC Gate Consults and Reviews Key Project Activities April May June July August September October November December Release 1 Inception Initiate the Project Plan the Project Initiate Plan Detailed Design Consult Elaboration Define Requirements Design Solution Define Requirements Design Solution Preliminary Operational Readiness Consult Construction Develop Solution Develop Solution Test Solution Test Solution Transition User Acceptance Testing Train Deploy Final Detailed Design Review Operational Readiness Review UAT Train Deploy -5-

6 ESC Role with CMS Gate Review Process Through the course of the project, the ESC will be reviewing the same project deliverables which will be presented during the CMS Gate Reviews Project Management Team will provide updates at the ESC meetings regarding upcoming reviews and results from past reviews Your staff will be invited to participate in the CMS gate review sessions (AHCA, FHK, DOH) -6-

7 Project Deloitte Solution Update -7-

8 Purpose of Requirements Validation Requirements Validation activities are performed project in order to: Review previously identified business requirements and understand where changes are needed to existing business functionality Clarify business requirements to define both functional and nonfunctional (technical) system requirements Identify functionality the system will enable as a part of Release 1 of the Requirements Validation activities are performed to formalize what is wanted from the system. Design activities are then performed to determine how to implement the functionality within the system.

9 Results of Requirements Validation Session Topics Week 1: Self-Service Portal Replacement Week 2: Self-Service Portal Affordable Care Act Enhancements Week 3: Worker Portal Modifications Week 4: Standard Filing Unit and Eligibility Determination Modules Week 5: Interfaces Week 6: No Touch Functions Week 7: Reporting & Analytics and Non-Functional Requirements By the Numbers 31 of 32 sessions completed Last session scheduled for Monday, June unique participants Including DCF, FHK, AHCA, call centers, and field operations Over 670 business requirements validated and elaborated Including over 210 business requirements for the Self-Service Web Portal Including over 25 business requirements for Interfaces Requirements Validation activities provide the primary inputs to the Requirements Definition Document and the Requirements Traceability Matrix deliverables. -9-

10 Hardware and Software Purchases Hardware Purchase #1 April 29 VCE vblock System 320 for the Self-Service Web Portal Software Purchase #1 April 30 IBM products including rules engine and Enterprise Service Bus (ESB) Software Purchase #2 May 24 Application tools including developer workbench and data modeling software Software Purchase #3 May 29 Oracle database software and SAP Business Objects reporting software Software Purchase #4 In-Process Remaining products including performance testing and system monitoring software All hardware and software purchases have been performed on-time and on-budget.

11 Key SI Focus Areas for June and July 2013 Complete Planning Phase & Conduct Planning Phase Gate Review Complete Requirements Validation Activities Produce Requirements Definition Document & Requirements Traceability Matrix Deliverables Continue Application Design & Reporting Design Develop Functional Design Specifications & Technical Design Specifications Participate in the CMS Detailed Design Consult (DDC) Enterprise Life-Cycle Review Receive and Install Hardware and Software Commence Development Phase Develop Master Test Plan Design To-Be Process Models -11-

12 Current SI Project Schedule Planning Phase Deliverables Project Management Plan Deliverable Expectation Documents Emergency Preparedness Plan -12-

13 Project Project Status June 7, 2013

14 Project Summary Is the project on schedule? Do we expect the project to complete on schedule? Are there any scope changes? Are there any risks or issues that are not being successfully managed? Is the project currently within budget? Is the project expected to stay within budget? Yes Yes No No (w/concerns) Yes Yes (FY 13 savings) 14

15 Project Progress Release 1 MAGI Major Project Tasks & Activities this Reporting Period Task/Activity Item & Description Requirements Validation Sessions being held with a variety of stakeholders from each of the agencies Software procurement approved and ordered Analysis of the current state of business processes CMS Enterprise Life Cycle Gate Reviews Detailed Design Review Consult with project artifacts Planned Completion Date Actual Completion Date 06/10/13 On target Status/Variance Explanation/Comment 06/14/13 Three of four software purchases have been approved and ordered. The fourth is anticipated in the coming week. 06/30/13 On target 07/12/13 Project Team preparation and updates of artifacts are underway. Consult tentatively scheduled for week ending 07/12/13 Application Design and Reporting Design 07/23/13 On target 15

16 Project Progress Release 1 MAGI continued Major Project Tasks & Activities this Reporting Period Task/Activity Item & Description Planned Completion Date Actual Completion Date Status/Variance Explanation/Comment Development of Master Test Plan 08/26/13 On target Development of Functional Design Specifications and Technical Design Specifications 09/17/13 On target System Development Phase 12/04/13 On target Release 1 - (Medicaid Rules Engine, MAGI Rules, Web Portal, Interfaces) Interagency policy planning and regulatory review 01/01/14 On target Ongoing Ongoing Workgroup meets biweekly 16

17 Project Issues Issues Factors to Consider and Resolution Approach Contingency Plan Pending CMS Approval Follow-up meeting scheduled as part of ongoing communication with CMS to discuss alternative strategies (6/12/13). Project Director Resignation DCF in collaboration with PMO vendor is working to fill this position quickly. 17

18 Project Risk ( Very High Certainty Risk Rating) Risks The federal deadline for implementation of a functioning Medicaid Eligibility System is January 1, Because requirements are being defined at a variety of levels and inconsistent requirement details may negatively affect prioritization decisions or leave gaps in functionality within the finalized system. Mitigation Strategy The project is closely managed and monitored with a process to escalate and resolve risks quickly in order to stay on the compressed schedule. Additionally, the Project Team communicates with CMS regarding pending regulations that may have an impact on the project. Stakeholder Subject Matter Experts will continue to work with the Systems Integrator to validate and prioritize business requirements during the Requirement Validation Sessions. Weekly debriefings are held to ensure "effective" requirements are produced. Additionally, the Systems Integrator and Subject Matter Experts will work closely to trace the defined and prioritized requirements to the original documents to validate inclusion of all requirements. 18