Transcript Document

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 McKethon
Bill Jenkins (Revision
Consulting)
Robert Yu
PMO
Technical Lead
Test Lead
Security Lead
System Test Starts
January 2013
COHBE High Level Schedule
Activity
Q2 2012
Q3 2012
Q4 2012
Q1 2013
Live
10/1/2013
Q2 2013
Q3 2014
Q4 2014
CMS Reviews
Planning
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
Prior
Week
This
Week
Trending Green
Comments
Holding Steady
Trending Red
Return to Green Plan
Target
Date
Budget
Overall
Funding Available
Current grant funding is exhausted in October 2012.
COHBE aggressively pursuing additional grant
funding
Oct 2012
Resources are spread thin, but hiring has been ramped up.
COHBE developed staff plan and is hiring resources
to fill key resource gaps
Oct 2012
Senior development resources have been acquired. Focusing on midlevel development resources.
CGI aggressively pursuing technical resources both
locally and nationally
Aug 2012
Schedule planning is still ongoing.
COHBE PMO developing overall plan to align with
critical CMS and CGI milestones
Aug 2012
Actuals to Date
Schedule
Staffing
Tracking to Forecast
COHBE
CGI
COHBE
CGI
Scope
Completed initial pass of increment planning based on the use case list.
CGI PMO finalizing schedule
Will baseline the plan after reviewing impact of changes to requirements
identified during RV sessions
Additional requirements and/or changes to critical assumptions about
requirements continue to be identified during requirements sessions.
Established a gap assessment process; continue to
assess impacts and priorities; may result in CR or
deferred functionality
Aug 2012
Aug 2012
External Dependencies
Quality
State Interfaces
Carriers
Plan Loading
Have not been able to confirm schedule/timeline for key external
projects (EES, MDM/SSO, State gateway). Need to engage with
development teams in August to start design activities so that COHBE can
meet aggessive development timeline.
COHBE and carriers have established an interface working group (which
has been meeting regularly for the past two months) and are
systematically reviewing each interface in preparation for the design
phase. All carriers are participating.
COHBE is assuming that plan loading and certification activities will be
supported by nationally-available tools developed by NAIC (SERFF).
High level executive oversight reviews have been
established to align priorities and determine which
Aug 2012
option(s) to resolve should be initiated. OIT PM to
be on-boarded this week
Key Implementation Risks
Time (potential to delay launch)
6
1
2
#
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
3
5
4
Low
Medium
High
Scope / Quality (potential to impact functionality / usefulness of Exchange)
*Size of bubble indicates relative
impact relative
Questions ?