COHBE Implementation Plan Overview August 13 2012 1
COHBE Implementation Plan Overview August 13, 2012 1
Agenda • • • Core Team High Level Schedule Status Key Risks Questions?
Core Team Role COHBE Delivery Partners COHBE CGI OIT HCPF Executive Sponsor Patty Fontneau Heidi Green Kristen Russell Sue Birch Project Manager Gary Schneider Kristine Johnson Dave Coren Megan Woods Adele Work Cameron Holm N/A Jed Summerton Steve Papke Sherri Hammons N/A Business Operations / Policy Lindy Hinman Richard Curley N/A Antoinette Taranto Functional Lead John Barela / Jessica Dunbar Kelli Kangas TBD Maureen Dove-Yuhas System Architect Gary Schneider Rick Sammartino TBD Mike Mc. Kethon Bill Jenkins (Revision Consulting) Robert Yu PMO Technical Lead Test Lead Security Lead
COHBE High Level Schedule Activity Q 2 2012 Q 3 2012 System Test Starts January 2013 Q 4 2012 Q 1 2013 Live 10/1/2013 Q 2 2013 Q 3 2014 Q 4 2014 CMS Reviews Planning RVDRVD Requirements Validation UI TECHNOLOGY IMPLEMENTATION Sizing Estimates Dev Infrastructure Test Incremental Build Design and Test Prod Development Iterations Testing Build Test Cases Individual Pilot 7/1/2013 SHOP/ Individual System Test Performance / Security Test Deployment Interface Development Planning/Analysis Design/Build/Unit Test BUSINESS IMPLEMENTATION Training & Documentation Planning Policy Development Planning Outreach Planning Business Operations Plan Management Call Center SHOP Create Material Individual Training Execution Policy Development Execution Planning Align with DOI SHOP Pilot 5/1/2013 Test Hiring / Process Development Develop Processes Carrier Alignment Load Test Plans Certify and Load Plans Develop Call Center Tools and Processes Call Center SOW As of Today Open Enroll
Current COHBE Status Dashboard
Key Implementation Risks Time (potential to delay launch) 6 1 2 3 5 4 Low Medium High Scope / Quality (potential to impact functionality / usefulness of Exchange) # Risk Description 1 Availability of External Eligibility Service 2 Availability of standardized tool for carriers to load and DOI to certify plans (SERFF) 3 Functionality gaps in base system require additional development effort 4 Carrier alignment and system integration 5 Time for CMS to develop policies 6 Availability of Federal Data Hub *Size of bubble indicates relative impact relative
Questions ?
- Slides: 7