J-2_Schedule_of_Deliverables_4-29-14.pdf

RFP-CMS-2015-8A-00209

Attachment J-2

SCHEDULE OF DELIVERABLES

The contractor shall utilize the CDS/Dimensions on-line software for recording the deliverables in the schedule. Further instructions will be provided upon award.

The Contractor shall produce all deliverables in the current version used by CMS for Microsoft Office software as appropriate (unless otherwise directed). The typical file types anticipated are listed below:

a. Text Microsoft Word

b. Spreadsheets Microsoft Excel

c. Briefings Microsoft PowerPoint

d. Drawings Microsoft Visio

e. Schedules Microsoft Project

Other file formats (example: .pdf) may be acceptable as mutually agreed and coordinated with the Government.

All files submitted by the Contractor shall be editable by the Government, unless otherwise approved by the CMS GTL/COR/PM. An accompanying red-lined document shall be included with each deliverable.

Submission Instructions

Satisfactory performance of the contract shall be deemed to occur upon delivery and acceptance by the Contracting Officer, or the duly authorized representative, of the items listed below in accordance with the stated delivery schedule. Deliverables shall be submitted to the Contract Officer, or the duly authorized representative, as listed on the Schedule of Deliverable Tables below.

All deliverables shall be addressed and delivered electronically or in hard copy to CMS (unless otherwise indicated) at:

Centers for Medicare & Medicaid Services Attn: <Name> 7500 Security Blvd.

Baltimore, MD 21244 Email address: <email>

In addition, a copy of the transmittal letter for all deliverables shall be forwarded electronically or in hard copy to the Contracting Officer listed in the SoW.

Notes:

a. All electronic files shall be submitted in a format compatible with Microsoft Office PC-based software. This is subject to change; the Contractor shall adapt to any new CMS standard, if necessary, in order to submit deliverables.

b. Unless specifically denoted as workday(s), all timeframes are in calendar weeks, calendar months, etc. after the effective date of the contract.

c. All deliverable due dates shall be interpreted to be COB on the due date unless specifically noted otherwise.

d. All deliverable due dates shall be for electronic copies unless specifically noted otherwise with hard copies to be delivered on next business day only for deliverables and work products specifically requested by CMS.

e. If the deliverable due date falls on a non-business day, the deliverable shall be due on the SOB first business day after the scheduled due date.

The following abbreviations and definitions apply:

SoW = Statement of Work NLT = not later than WP = Work Product OTH = Other Output Business Day = weekday except for regularly scheduled Federal holiday Week = defined as 5 business days Month(ly) = defined as calendar month

The contractor shall furnish the deliverables required under this contract in accordance with the Delivery Schedule instructions as set forth below:

Task Description

COR

GTL

ISSO

PM

Due Date(s)

C.2.1.1 Program Management

Program Management Plan COR GTL 30 Days after the contract award

Master Program Schedule COR GTL 30 Days after the contract award

Subcontractor Management Plan COR

GTL

180 Days after award and as directed by CMS

Managers’ Program Status Briefing COR GTL Monthly on recurring basis

C.2.1.2 Project Management

Project Status Report COR GTL Every Thursday by 5 PM EDT

Project Management Plan COR GTL 30 Days after the contract award

Project Plan and Schedule COR

GTL

30 Days after the contract award and weekly thereafter

Task Description

COR

GTL

ISSO

PM

Due Date(s)

Project Weekly Status Meeting Agenda COR GTL Two business days prior to meetings

Project Weekly Status Meeting COR GTL Weekly on a recurring basis

Project Weekly Status Meeting Minutes COR GTL Two business days after meetings

C.2.1.2.1 Risk and Issue Management

Risk Management Plan COR

GTL

30 Days after contract award and as directed by CMS

Monthly Risk Management Meeting COR GTL `Monthly on a recurring basis

Monthly Risk Management Report COR

GTL

Monthly, two days prior to risk management meeting

C.2.1.2.2 Communications Management

Communication Management Plan COR GTL 30 Days after contract award

C.2.1.3 Quality and Process Management

Quality Assurance Plan COR

GTL

Delivered 30 Days from contract award; annually thereafter.

C.2.1.4 Earned Value Management

(EVM)

System Description for their Program Management Control System (PMCS)

COR

GTL

Delivered 30 Days from contract award

C.2.1.4.1 EVM SYSTEM REVIEW

Integrated Baseline Review (IBR) GTL

COR

Annually at the start of each option year and as requested by CMS

Variance Analysis Reports COR Monthly Due on 15th of following month

C.2.1.4.3 Earned Value Contract Performance Report

Earn Value Contract Performance Report (CPR) Formats 1-5

GTL

COR

Monthly Due on the 15th following the end of the month.

C.2.1.4.4 Management Review

Bi-Annual Financial report COR Due 6 months after award and every 6 months thereafter, and as requested by CMS

Monthly Financial Overview Meeting COR Monthly on a recurring basis Monthly Financial Overview Meeting Minutes COR Monthly two business days after meeting

GTL

ISSO

PM

Due Date(s)

C.2.1.5 Incoming Transition Plan

Transition Approach and Strategy Plan COR GTL 4 weeks from contract award date

Detailed Transition Plan COR GTL 8 weeks from contract award date

C.2.1.6 JOINT OPERATING

AGREEMENT

Joint Operation Agreement (JOA) COR GTL 14 Days after contract award

C.2.2.1 Enterprise-Wide Engineering Design and Engineering artifacts as required by CMS IT Governance

COR

GTL Per CMS approved Project Plan

C.2.2.3 Server Engineering Monthly Unscheduled Production System Downtime Report

COR

GTL COB Last Friday of every month

C.2.2.6 Physical Facility Design & Engineering

Physical Facility Plan COR GTL 30 days after contract award

C.2.3.3 Capacity and Performance Management

Capacity Plan COR GTL 60 days after contract award

Capacity Report COR GTL COB Last Friday of every month

C.2.3.4 Procurement of HCQIS IT

ASSETS

Updated J-2 documenting material purchases

COR

GTL

As required and within 10 days after request

C.2.3.6 HCQIS Applications and Services Inventory Management

An inventory of all IT Systems and Services

GTL

COR

60 Days after award date and as requested thereafter

C.2.4.1 Configuration Management Identify and document all HCQIS hardware, software, and documentation

COR

GTL

60 Days after contract award and as required thereafter

C.2.4.4.3 PERFORMANCE and Stress Testing

ITF Lab Test Final Report for each test COR GTL 5 days after conclusion

Final Test Report and Summary COR 5 days after conclusion

GTL

ISSO

PM

Due Date(s)

GTL

Monthly Testing Project Plans and Schedules

COR

GTL COB Last Friday of every month

C.2.5.3.2 Application Environment Build Defining and creating VM templates for standard components

COR

GTL

Delivered per CMS Direction

C.2.5.4 Network Operations and Maintenance

Monthly Data Center Status report containing information as needed by CMS

COR

GTL COB Last Friday of every month

C.2.5.6 Server Operations and Maintenance

Disaster Recovery plan and provide the test results

COR

GTL

Annually

Updated Testing recovery plan COR

GTL

Annually

C.2.5.7 Database & Storage Management

Testing Disaster Recovery plan and provide the test results

COR

GTL Annually

Updated Testing recovery plan COR GTL Annually

C.2.5.7.3 Storage Area Network (SAN) Administration

Testing Disaster Recovery plan and provide the test results

COR

GTL Annually and when changes occur

Updated Testing recovery plan COR GTL Annually

C.2.5.8 Security Management

HCQIS Security Strategy COR

ISSO

30 Days from contract award and annually thereafter

HCQIS Security Operations Executive Summary

COR

ISSO Monthly

POA&M Monthly updates COR ISSO Monthly on a recurring basis

HCQIS System Security Plan and Risk Assessments (SSP)

ISSO

60 days after contract award date;

and 180 days after first delivery thereafter

Business Continuity and Contingency Plan (BCCP)

COR

ISSO

60 days after contract award and annually thereafter and when changes occur

GTL

ISSO

PM

Due Date(s)

Disaster Recovery Test Plan (Formally known at CMS as a Tabletop Test)

COR

ISSO

Annually thereafter and when changes occur; Updated 90 days prior to a Test

HCQIS Tabletop Test Report COR

ISSO

Annually and 10 business days after Business Continuity Exercise

HCQIS Corrective Action (CAP) Report COR

ISSO

Monthly, 3rd business day of each month

HCQIS Security Scans COR

ISSO

Monthly, 3rd business day of each month

Quarterly Security Reports GTL

COR

Within 10 days of end of each calendar quarter

C.2.5.8.3 Security Planning

Updated SSP Plan/Risk Assessments COR

GTL

Annually

Updated QIO Admin Policy COR

ISSO

Annually

Updated QIO Operations Manual COR

ISSO

Annually

C.2.5.9 Help Desk

Quarterly Executive Summary Report COR

GTL

Quarterly from contract award and every quarter thereafter

C.2.5.9.3 SERVICE REQUEST

MANAGEMENT

Monthly report of service request by category

COR

GTL COB last Friday each month

C.2.5.10 WEB CONFERENCING

SUPPORT

Monthly Executive Report COR GTL COB last Friday each month

C.2.5.11.2 Production Data Management Develop run and recovery procedure manual.

COR

C.2.5.12 Event Management Event Management standards and procedures document initial and update

COR

C.2.5.15 QIO and ESRD Site Administration

Provide topology and production environment updates

COR

GTL

Six months from contract award and every six months thereafter

C.2.5.16 QIO & ESRD Transition (startup/shutdown)

GTL

ISSO

PM

Due Date(s)

Project Plan for QIO & ESRD Transition Startup/Shutdown

COR

GTL Delivered per CMS direction

C.2.6.1 Governance Enterprise Program Management Plan and Approach PM Delivered 30 days after contract award. Annually thereafter.

C.2.6.2 Technology Innovations

Tactical Plan PM Six months post award and quarterly thereafter

Strategic Plan PM Twelve months post award and annually thereafter

C.4.7 HCQIS Conference Support

Perform facility site survey COR GTL 15 days after site selection

OTHER

Provide Service Level Agreements COR GTL As Required

Three year analysis report including documentation as requested by CMS on the QNET infrastructure and technologies based from year one of contract to current state.

GTL Three years from contract award

SCHEDULE OF DELIVERABLES