J_Non-Functional RTM Narrative.docx

State of Washington | RFP No. 24-DCYF-CW-081 Department of Children, Youth, and Families (DCYF) Attachment J: Implementation and Performance Non-Functional RTM Narrative Response Template

Attachment J:

Implementation and Performance Non-Functional Requirements Traceability Matrix (RTM) Narrative Response Template

Unless otherwise directed, DCYF requires that Vendors use the provided mandatory response templates to prepare responses included in the proposal. DCYF requires that Vendors enter responses directly into templates, and not to insert “see attached file” (or similar statements) in the templates or worksheet to reference separate documents. Proposals not using the mandatory response templates will not be reviewed. Figures and tables must be numbered and referenced in the text of the proposal by that number. DCYF requests that Vendors do not submit marketing materials, product sheets, brochures, customer testimonials, or other pre-printed materials.

Table of Contents

Project Management Approach Project Management Approach Instructions: The Vendor must describe its approach to addressing the Project Management Services Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM), including the below areas. The response to this question is limited to a maximum of three (3) pages.

Deliverables Management Change Management Staff/Resource Management Document Management Oversight Review: State of Washington IT Gated Funding Oversight

< Insert Vendor Response >

Deliverable Approach Instructions: The Vendor must describe its approach to managing project deliverables included in the Deliverable List Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM). Specifically, DCYF requests Vendors to describe their approach to developing, delivering, seeking DCYF’s approval of deliverables, then managing revisions to those deliverables over the duration of the project. The response to this question is limited to a maximum of three (3) pages.

< Insert Vendor Response >

Project Schedule Instructions: The Vendor must describe their approach to developing and managing a Project Schedule to monitor and control project activities over the duration of the project.

Note: In addition to this narrative response document, the Vendor must provide a Project Schedule for the initial five-year contract period that demonstrates the Vendor’s understanding of the services and products requested in this RFP. The work plan must include:

Proposed phases, tasks, and subtasks Start and end dates of tasks and subtasks Dependencies between tasks The Project Schedule must be provided in a separate Microsoft Project file format. For more details, refer to the RFP Section C.17. In the response box below, Vendors must attest that a Project Schedule is included as part of the submission package.

< Insert Vendor Response >

Communication Plan Instructions: The Vendor must describe their approach to developing and managing a communication plan and communication matrix. The response to this question is limited to a maximum of five (5) pages.

< Insert Vendor Response >

Risk Management Plan Instructions: The Vendor must describe their approach to developing and managing a risk management plan that includes identification of common risks and mitigation strategies. The response to this question is limited to a maximum of five (5) pages.

< Insert Vendor Response >

Quality Assurance Plan Instructions: The Vendor must describe their approach to developing and managing the quality assurance approach. The response to this question is limited to a maximum of five (5) pages.

< Insert Vendor Response >

Organizational Change Management (OCM) Plan Instructions: The Vendor must describe their approach to developing and managing the OCM approach. The response to this question is limited to a maximum of five (5) pages.

< Insert Vendor Response >

Testing Plan Instructions: The Vendor must describe their approach to developing and managing the testing approach. The response to this question is limited to a maximum of five (5) pages.

< Insert Vendor Response >

Training Plan Instructions: The Vendor must describe their approach to developing and managing the training approach. The response to this question is limited to a maximum of five (5) pages.

< Insert Vendor Response >

Implementation / Deployment Plan Instructions: The Vendor must describe their approach to developing and managing implementation / deployment approach. The response to this question is limited to a maximum of ten (10) pages.

< Insert Vendor Response >

Knowledge Transfer Plan Instructions: The Vendor must describe their approach to developing and managing the knowledge transfer plan. The response to this question is limited to a maximum of five (5) pages.

< Insert Vendor Response >

Quality Control and Compliance Instructions: The Vendor must describe procedures to ensure product meets quality and how the project will adhere to relevant regulations and standards including security and privacy standards. The response to this question is limited to a maximum of five (5) pages.

< Insert Vendor Response >

Data Management Plan Instructions: The Vendor must describe how data will be handled, stored, and secured through the project. The response to this question is limited to a maximum of ten (10) pages.

< Insert Vendor Response >

Project Management Services Non-Functional Requirements Approach Assumptions Instructions: The Vendor must document the assumptions related to this Response Template in Table 1. Add rows as necessary. Do not change any of the completed cells.

Project Management Services Non-Functional Requirements Assumptions

(Section, Page, Paragraph)

Maintenance and Operations (M&O) Maintenance and Operations (M&O) Approach Instructions: The Vendor must describe its approach to addressing the Maintenance and Operations (M&O) Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM), including the below areas. The response to this question is limited to a maximum of three (3) pages.

Interface Management Service Desk Release Management Security and Privacy

< Insert Vendor Response >

Knowledge Transfer Approach Instructions: The Vendor must describe its approach to addressing the Knowledge Transfer Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM), including the below areas. The response to this question is limited to a maximum of three (3) pages.

Knowledge Transfer Exit Transition

< Insert Vendor Response >

M&O Services Non-Functional Requirements Approach Assumptions Instructions: The Vendor must document the assumptions related to this Response Template in Table 1. Add rows as necessary. Do not change any of the completed cells.

M&O Services Non-Functional Requirements Assumptions

(Section, Page, Paragraph)

Legacy Systems Decommissioning Decommissioning Approach Instructions: The Vendor must describe its approach to decommissioning all legacy systems that are in scope as described in Attachment I: Non-Functional Requirements Traceability Matrix (RTM), including the below areas. The response to this question is limited to a maximum of ten (10) pages.

Proposed approach to decommissioning legacy systems in scope (see RFP Appendix C: Legacy Systems to be Decommissioned) Development of a Legacy Systems Decommission Plan Perform deployment and support activities as agreed in the plan

< Insert Vendor Response >

Legacy Systems Decommissioning Services Non-Functional Requirements Approach Assumptions Instructions: The Vendor must document the assumptions related to this Response Template in Table 1. Add rows as necessary. Do not change any of the completed cells.

Legacy Systems Decommissioning Services Non-Functional Requirements Assumptions

(Section, Page, Paragraph)

Design, Development, and Implementation (DDI) Implementation Approach Instructions: As noted in the RFP (Section A.8), DCYF anticipates an incremental roll-out of DEPS but is interested in understanding the approaches Vendors will propose, and requests that Vendors describe their recommended implementation approach, methodology and schedule in their response. The response to this question is limited to a maximum of three (3) pages.

In this response section, DCYF requests that Vendors share their experience working with other state or territory agencies to implement an enterprise payment solution and use the following to inform their response:

DCYF’s Notional Project Schedule, as described in the RFP Section A.9

Note: There are no specific implementation requirements in the DDI Requirements Traceability Matrix.

< Insert Vendor Response >

Requirements Validation Approach Instructions: The Vendor must describe its approach to addressing the Requirements Validation Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM). The response to this question is limited to a maximum of three (3) pages.

< Insert Vendor Response >

Solution Design and Development Approach Instructions: The Vendor must describe its approach to addressing the Solution Design and Development Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM). The response to this question is limited to a maximum of three (3) pages.

< Insert Vendor Response >

Testing Approach Instructions: The Vendor must describe its approach to addressing the Testing Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM). The response to this question is limited to a maximum of three (3) pages.

< Insert Vendor Response >

User Training Approach Instructions: The Vendor must describe its approach to addressing the User Training Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM). The response to this question is limited to a maximum of three (3) pages.

< Insert Vendor Response >

Solution Services Provisioning Instructions: The Vendor must describe its approach to addressing the solution services provisioning Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM). The response to this question is limited to a maximum of three (3) pages.

< Insert Vendor Response >

Data Migration Approach Instructions: The Vendor must describe its approach to addressing the Data Migration Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM). The response to this question is limited to a maximum of three (3) pages.

< Insert Vendor Response >

Cutover Approach Instructions: The Vendor must describe its approach to addressing the Cutover Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM). The response to this question is limited to a maximum of three (3) pages.

< Insert Vendor Response >

Hypercare Approach Instructions: The Vendor must describe its approach to addressing the Hypercare (post-implementation accelerated triage, resolution, and support) Non-Functional Requirements as listed in Attachment I: Non-Functional Requirements Traceability Matrix (RTM). The response to this question is limited to a maximum of three (3) pages.

< Insert Vendor Response >

DDI Services Non-Functional Requirements Approach Assumptions Instructions: The Vendor must document the assumptions related to this Response Template in Table 1. Add rows as necessary. Do not change any of the completed cells.

DDI Services Non-Functional Requirements Assumptions

(Section, Page, Paragraph)

image1.jpeg