10.1.9 Scope of Work Deliverables Table.xlsx
XLSX spreadsheet 33 KB Posted
- Attached to
- Centralized Credentialing
- Solicitation number
- 40DHHS-S2377
- Issued by
- Churchill County, Nevada
About this file
This document is a Scope of Work (SOW) and Deliverables Table related to a state and local contract opportunity for the centralized credentialing service in Nevada, involving the jurisdictions of Carson City.
The SOW outlines numerous deliverables required for the project, including a Business Continuity/Disaster Recovery Plan, Change Management Plan, Communications Management Plan, Contract Administration Plan, Customer Care Plan, Data Conversion Plan, Data Management Plan, End-to-End Test Plan and Results, External Communication Plan, Final Certification, Implementation Plan, Interface Control Documents, JAD Session, Kickoff Presentation, Knowledge Transfer Plan, Lessons Learned, Master Test Plan, Operational Change Management Plan, Organizational Change Management, Parallel Test Plan and Results, Performance Test Plan and Results, Project/Change Management Tool, Project Management Plan, Project Plan/Schedule, Quality Management Plan, Regression Test Plan and Results, Release Management Plan, Reporting User Guide, Requirements Traceability Matrix, Resource Management Plan, Risk Management Plan, Scope of Work, Security Audit/Security Operations Center Report, Security Plan, System Design Document, Systems Test Plan and Results, Test Results Dashboard/Report, Training and Outreach Materials and Plan, Transition and Closeout, UAT Test Plan and Results, and User Manual. The deliverables have various due dates, ranging from 30 to 90 days from contract start or end of project phases.
View the file
Other files
Show all 25
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Instructions
| # | Instructions |
| 1 | The SOW and Deliverables attachment are used together to complete the SOW tasks. |
2 Deliverables in the Deliverables attachment are required for the project.
3 Deliverables have definitions associated with them to clarify their purpose.
4 If a deliverable contains a numeric value in the ORIGINAL indicator, its submission is required within that value of the start of the contract. For example, if the initial version of the deliverable contains a 60, this means that deliverable is due within 60 days of the start of the contract.
5 If a deliverable contains a numeric value an UPDATE indicator, its submission is required within that value of the end of the phase. For example, if an update of a deliverable contains a 30, its submission is required within 30 days of the end of that SOW stage.
6 If a deliverable contains a numeric value in the ANNUAL indicator, this means an annual review and update is due within that number of days of the end of the contract year. For example, if a deliverable has a value of 30 in the annual column, an update for that deliverable must be submitted WITHIN that number of days of the annual contract date, either before or after the annual date.
Definitions Focus Area Definition / Purpose Subsidiary Document Required?
Y/N
| Business Continuity / Disaster Recovery Plan | Created to document the vendor's business recovery and ongoing processing in the event of a catastrophic event. Must acknowledge compliance with HIPAA, describe strategy for disaster recovery and business continuity, contain recovery performance points, describe protocols and testing. An annual disaster recovery test is required. |
| Change Management Plan | Created to outline the process by which design, development or other changes during implementation are managed and followed through to completion, including documentation updates. Includes roles and responsibilities, approach, change categories, change control process (change request and change control board) and change request lifecycle tracking. |
| Communications Management Plan | Created to identify what is to be communicated about the project, who will receive communications, how and when information will be shared (meetings, reports, dashboards, etc.), how communications will be tracked and analyzed. Additionally includes a high level identification of any external / public communication needed for the project along with the generation, documentation, storage, transmission and disposal of all project information. |
| Contract Administration Plan (M&O) | Created to ensure that the design professional and contractor performs in accordance with all the terms and conditions of the contractual agreement. May include work performance, progress as it relates to the schdule. Makes sure both parties understand their responsibilities to one another, facilitates communication between parties, makes sure contract meets official requirements, protects both entities. Includes but is not limited to points of contact, roles and responsibilities, critical contract milestones, payment procedures, service level agreements, issue resolution process, grievance process and plan for documenting, and reviewing and reporting on the effectiveness of these processes. |
| Customer Care Plan | Created to outline how customer support works within the Vendor environment, requires incident tracking with date and time stamp, access and functionality of the ticketing system, filtering and reporting options, how inquiries are prioritized and given severity level identification, may contain detailed service level agreements, reporting to the State, quality monitoring, call center statistics, analyses and trends. Also includes roles, responsibilities, hours of operation. |
| Data Conversion Plan | Created to identify how data from the previous / existing system will be converted to the new system. Must include scope, roles and responsibilities, conversion procedures, approach to mock conversions, validation reporting and timeline. |
| Data Management Plan | Created to identify how data will be described, stored, secured, transmitted, what standards will be used during implementation and maintenance & operations, also includes data retention plan that complies with DHCFP record retention policies. |
| End-to-End Test Plan | Created to test the application workflow from beginning to end to validate the system for integration and data integrity. Includes test cases. |
| End-to-End Test Results | Created to report the results of end-to-end testing. |
| External Communication Plan | Created to identify how the vendor will communicate with consumers of the system, provides detailed information regarding all stakeholder and consumer-facing communications, system and upgrade notifications, and resources available to consumers. Includes review process for all communications materials. |
| Final Certification - Evidence and Presentation | Created to demonstrate to CMS that the systems functionality and consumer support are intact and functioning. Satisfies the appropriate metrics based on current CMS guidance. |
| Implementation Plan | Created to identify vendor transfer tasks, data conversion, call center setup, command center setup, OR checklist, promotion / rollback plan, commmand center plans. |
| Interface Control Documents | Created to identify all interface files that will be developed and scheduled for the project, includes owner, direction, schedule, characteristics and standards. Must be developed based on industry standards and include components as recommended by PMBOK and CMS. |
| JAD Session | Created to facilitate a joint revei wof RFP requirements with the State and designated policy stakeholders resulting in an approved baseline system RTM. Vendor shal demonstrate their solution to show how it satisfies the requiremetns within the RFP, identify configurable features and functions, and identify gaps wihtin the system to be addressed. |
| Kickoff Presentation | Created to introduce the respective teams, state objectives, roles and responsibilities, and a high level timeline. |
| Knowledge Transfer Plan | Created to transfer information to everyone would could benefit from it. Includes identification, capture and documentation of critical information from experts across the business. Also includes a dedicated contact who specifically facilitates knowledge sharing. Includes storage of information. |
| Lessons Learned | Created throughout the project to gather incidents and events that impacted the project (mostly negatively). Lessons learned are gathered, summarized and reported at the end of the project for the team to review. The purpose is to help similar projects avoid these roadblocks in the future. |
| Master Test Plan | Created to document testing strategy and acceptance criteria for the project; identifies potential need for parallel, systems, end-to-end, UAT, performance, regression testing. Separate plans for each may be required. |
| Operational Change Management Plan | To identify the process by which system changes are identified, tracked, approved and completed during the operations and maintenance period. Addresses the systems side of change management, includes release management. |
| Operational Readiness Review - Certification Evidence and Presentation | Created to show CMS that system is ready for implementation based on current CMS guidance. |
| Organizational Change Management | To provide a framework for managing the effect of new business processes, changes in organizational structure, or cultural changes within an enterprise. Addresses the people side of change management. Both State and customer environments may need planning in this area. |
| Parallel Test Plan | Created to test different system applications, i.e. a legacy vs a new application. Includes test cases. |
| Parallel Test Results | Created to report the results of parallel testing. |
| Performance Test Plan | Created to document how the system performance will be tested per the requirements . Includes test cases. |
| Performance Test Results | Created to report the results of performance testing. |
| Project / Change Management Tool | A tool that can be used for tracking projects, risks and issues, and defect resolution. Includes Change Management, enhancements, and configuration changes and associated documentation. Operational Change Management should include plan for training new users. |
| Promotion / Backout / Rollback Plan | Created to document the process for backing out code promotions and rolling back to previous code versions. Must include scope, roles and responsibilitites, strategy, entrance and exit criteria, risks, authority, procedures and verification. |
| Project Management Plan | Created to identify the process by which a project and related components are managed, covers communications, risks, quality control, project schedule, testing, documentation, deliverables management, facilitation. Also serves to identify within the RFP what components are required of a specific project. Foundation of the project. Includes any project management requirements for projects in ongoing operations. Must include entrance and exit criteria for all project tasks/phases, Configuration, Deployment, Operations, Closout. |
| Project Plan / Schedule | Created to identify the tasks, activities, deliverables, schedule, dependencies, resources and milestones of a project. |
| Quality Management Plan | Created to identify the necessary information required to effectively manage project quality from planning to delivery. Defines a project's quality policies, criteria for and areas of application, roles, responsibilities and authorities. May include quality of code, workmanship, project schedules and subcontractor activities. |
| Regression Test Plan | Created to identify areas that may need repeat testing due to the impacts of previous defect corrections in the testing process. Includes test cases. |
| Regression Test Results | Created to report the results of regression testing. |
| Release Management Plan | Created to incorporate industry best practices for system updates and changes. Must include release schedule and details on how Vendor shall schedule and manage relesaes across system environments to ensure appropriate tracking and notification to DHCFP and other stakeholders. |
| Reporting User Guide | Created to provide system users with instructions for how to create reports from a vendor system. |
| Requirements Traceability Matrix (RTM) | Created in order to trace project requirements back to the detailed RFP responses, used to review and validate RFP requirements, identify gaps and solutions prior to the start of configuration and development. |
| Resource Management Plan | Created to identify how resources (human, workspace, tools, equipment) will be applied within the project and ongoing operations, outlines how they'll be categorized, allocated, managed and released. |
| Risk Management Plan | Created to identify the risks and issues within the project, along with mitigation strategies and escalation procedures. Addresses identification, analysis of risks and issues impacting the project. |
| Scope of Work | Created to identify and document the work that is to be completed within the contractual agreement, covers implementation through contract expiration. |
| Security Audit / Security Operations Center (SOC) Report | Created to summarize and communicate security findings (key findings, monitoring, incident and threat reporting) during M&O for a specific period of time; required by CMS for certification. |
| Security Plan | Created to identify security methods and mechanisms to be used throughout implementation and M&O. |
| System Design Document | Created to identify how the system will function in order to meet the specified requirements. Must comply with industry standards and include components as recommended by PMBOK and CMS. |
| Systems Test Plan | Created to identify the specific testing requirements to ensure the system is functioning as expected. Includes test cases. |
| Systems Test Results | Created to report the results of system testing. |
| Test Results Dashboard / Report | Created to report various testing results in a compact, convenient location. |
| Training and Outreach Materials | Created to provide new system users with information and resources for how the new system or process works. Materials must be delivered within 60 days of the contract start date. |
| Training and Outreach Plan | Created to identify training and outreach needs, includes scope and audience, training and outreach activities, approved materials, roles and responsibilities, training and outreach schedules, and delivery of training and outreach to new or revalidated users. Plan must include ongoing training and outreach throughout the life of the contract and adhere to state and federal language requirements. |
| Transition and Closeout | Created to assess the project, ensure completion, derive any lessons learned and best practices to be applied to future projects. Additionally, to transition system enhancements to operations / monitoring to ensure all stakeholders are trained and understand their role in supporting the new system features. Includes but not limited to closeout / transition approach, roles and responsibilities, asset identification and ownership, knowledge transfer, operations resources needed, referential integrity of all assets, transition risks and proprosed mitigation strategies, transition and closeout lessons learned. |
| UAT Test Plan | Created to identify scenarios for user acceptance (UAT) testing and acceptance criteria, includes test cases. |
| UAT Test Results | Created to report the results of UAT testing |
| User Manual | Created by the vendor to provide documentation and information that supports users of the system. |
ProjectDeliverables
| SOW TASKS | |||||||||
| Deliverable Description | Kickoff | Planning & Administration | Design & Configuration | Development & Deployment | Maintenance & Operations | CMS Certification | Transition & Closeout | Annual | Legend |
| Business Continuity / Disaster Recovery Plan | 30 | 60 | 30 | Original | |||||
| Change Management Plan | 60 | 30 | Update | ||||||
| Communications Management Plan | 60 | 30 | Annual | ||||||
| Contract Administration Plan (M&O) | 60 | 30 | |||||||
| Customer Care Plan | 30 | 60 | 30 | ||||||
| Data Conversion Plan | 90 | ||||||||
| Data Management Plan | 90 | 60 | 30 | ||||||
| End-to-End Test Plan | |||||||||
| End-to-End Test Results | |||||||||
| External Communication Plan | 60 | 30 | |||||||
| Final Certification Review - Evidence and Presentation | |||||||||
| Implementation Plan | |||||||||
| Interface Control Documents | 30 | ||||||||
| JAD Session | |||||||||
| Kickoff Presentation | |||||||||
| Lessons Learned | |||||||||
| Master Test Plan | 30 | ||||||||
| Operational Change Management Plan | 60 | 30 | |||||||
| Operational Readiness Review - Certification Evidence and Presentation | |||||||||
| Organizational Change Management | 30 | ||||||||
| Performance Test Plan | |||||||||
| Performance Test Results | |||||||||
| Project / Change Management Tool | |||||||||
| Project Management Plan | |||||||||
| Project Plan/Schedule | |||||||||
| Quality Management Plan (DDI) | |||||||||
| Regression Test Plan | |||||||||
| Regression Test Results | |||||||||
| Release Management Plan | 60 | 30 | |||||||
| Reporting User Guide | |||||||||
| Requirements Traceability Matrix (RTM) | |||||||||
| Resource Management Plan | |||||||||
| Risk Management Plan | 60 | 30 | |||||||
| Scope of Work | |||||||||
| Security Audit / Security Operations Center (SOC) Report | |||||||||
| Security Plan | 60 | ||||||||
| System Design Document | 60 | ||||||||
| Systems Test Plan | |||||||||
| Systems Test Results | |||||||||
| Test Results Dashboard / Report | |||||||||
| Training and Outreach Materials | 60 | 30 | |||||||
| Training and Outreach Plan | 45 | 60 | 30 | ||||||
| Transition and Closeout | |||||||||
| UAT Test Plan | |||||||||
| UAT Test Results | |||||||||
| User Manual |
CertificationDeliverables
| Certification Deliverable | Definition |
| Operational Readiness / pre-Go-Live Certification Evidence | See current CMS guidance for latest details. |
| Operational Readiness / pre-Go-Live Certification Artifacts and Presentations | See current CMS guidance for latest details. |
| Operational Readiness / pre-Go-Live Certification Lessons Learned | See current CMS guidance for latest details. |
| Operational Readiness / post-Go-Live Certification Evidence | See current CMS guidance for latest details. |
| Operational Readiness / post-Go-Live Certification Artifacts and Presentations | See current CMS guidance for latest details. |
| Operational Readiness / post-Go-Live Certification Lessons Learned | See current CMS guidance for latest details. |
| Ongoing Performance Standards Reporting | See current CMS guidance for latest details. |
File details come from the government source that posted it. Updated .