ATTACHMENT A1_S-DASOBO-00010624_Scope of Services.docx

RFP ATTACHMENT A1

SBM SCOPE OF SERVICES

I. Platform Description

1. Related RFP Attachments.

a. Detailed Platform requirements are set forth in RFP Attachment H.

b. Maps showing the current integration with FDSH and the future Platform integration with FDSH are provided in RFP Attachment I.

Many of the deliverables and documentation related to the Services will be shared, wholly or in part, with CMS, IRS Safeguards and other entities responsible for federal and state oversight of the Solution. Contractor shall be available upon Agency’s request to answer questions from regulatory authorities as needed and to revise deliverables as appropriate to meet the expectations of those entities.

2. Marketplace Production Environment.

By Platform Operational Readiness, the Contractor shall configure and deploy a public-facing Marketplace Production Environment that meets Requirements in accordance with Contract terms and conditions, and that is populated with the resultant data from the executed Data Conversion and Migration Plan.

Contractor shall ensure the continuous and ongoing availability and functionality of the Marketplace Production Environment to support users for Plan Year 2027 OEP following Platform Operational Readiness. Contractor shall make certified plan data available in the Marketplace Production Environment to facilitate anonymous plan comparison by consumers. The Platform must support users with the re-verification of migrated consumer accounts as defined in the Consumer Messaging Plan. Activities will be conducted according to the Eligibility Re-Verification Plan, Auto Re-Enrollment Plan, and the Consumer Messaging Plan.

3. Platform Deliverables.

Agency anticipates that Implementation Services will include the following Deliverables:

a. Functional Design Document – Contractor shall deliver detailed functional design for the Platform. This document will also contain details regarding the security of the Platform at a functional level. This deliverable may need periodic refreshes during the period of performance through at least Final Acceptance.

b. Technical Design Document – Contractor shall deliver a detailed technical design of the Platform. This document will also contain details regarding the security of the system at a more technical level. This deliverable may need periodic refreshes during the period of performance.

c. Interface Documentation – Contractor shall deliver documents that detail all batch and real-time interfaces. For Implementation, Contractor must specifically document gaps, and any recommended changes to ensure connection to systems to which the SBM Solution must connect. The preference is the use of Application Programming Interfaces (“API”s). This deliverable may need periodic refreshes during the life of the Contract. Contractor shall provide documentation specific to each Platform interface as a discrete deliverable that describes functionality and processing, for at least:

i. Data validations and business rules;

ii. Transactional rules;

iii. Event and error handling;

iv. Interface design elements;

v. Interface design assumptions and constraints;

vi. General processing steps;

vii. Interface format(s);

viii. Data mapping and transformation; and

ix. Interface relationships and dependencies.

d. Data Dictionary – Contractor shall deliver a data dictionary, entity-relationship diagram and a database schema diagram. This document must also address elements that will be part of any data conversion efforts performed by Contractor. This Deliverable may need periodic refreshes during the period of performance.

e. Transition Plan – Contractor shall deliver a Transition Plan to support the Agencies to close out the project implementation activities and transition to M&O activities. This document must identify Contractor’s and the State’s responsibilities, including changes in the management processes.

f. Platform Status Reports – Before Platform Operational Readiness, Contractor shall deliver a weekly Platform status report. At a minimum the Platform status report must include an overall project status, status of the agreed upon functional areas of the project, and an update to an integrated project schedule. Status reports can also include areas of concern for the Contractor and commentary about potential risks that might impact the timeline. After Platform Operational Readiness, Contractor shall deliver a similar monthly Platform status report. As requested by OHA, Contractor shall deliver such Platform status reports more frequently.

g. Requirement Elaboration and Specification Sessions – Contractor shall facilitate requirement elaboration and specification activities including but not limited to design sessions/workshops with OHA and other State personnel and business partners. This will require the discovery and documentation of current business practices, including mapping and workflows for all aspects of the project identified in this RFP. This work will include eliciting and documenting input from stakeholders to gain an understanding of detailed user requirements and needs, working across teams to identify new workflows, and determining the user priorities of the system. Contractor shall engage in analysis of current-state processes and recommendations regarding changes to these processes or the engineering of entirely new processes with the goals of facilitating implementation and enabling improvements in organizational performance, work processes and related outcomes, and customer service.

h. Requirements Traceability Matrix (“RTM”) – Contractor shall support requirement revisions throughout the period of performance. Prior to Final Acceptance, Contractor shall provide test results documentation to demonstrate that the Platform complies with all requirements. In addition, the RTM must reflect structure/elements identified in the requirement elaboration and specification sessions and confirm clear mapping from requirements to design documentation, and accurate gap analysis identification between design and Platform functionality. Contractor shall update the RTM as necessary to reflect the state of the Platform throughout the phases of the Project, and changes made during the operations and maintenance (“O&M”) period. Contractor shall configure, deliver, and maintain the RTM which must include original requirements, updated requirements, and any agreed-upon change requests.

i. Gap Analysis Documentation – Upon conclusion of the Requirement Elaboration and Specification Sessions, Contractor shall deliver Gap Analysis Documentation highlighting the differences and distinctions between current practices and Solution features and functions, and solutions to those gaps. The starting point should be functional requirements from a state where the Platform has been implemented.

j. Regulatory Cooperation and Documentation – Contractor shall provide content and expert input to OHA as necessary for OHA to receive State and federal approvals to proceed with the project, including completion of the CMS Blueprint.

k. Cooperation with iQMS – Contractor shall cooperate with OHA and OHA’s project management team, Independent Quality Management Services (“iQMS”) vendor, and Enterprise Information Services (“EIS”) to ensure processes, methods, and artifacts comply with oversight requirements and industry best practices.

l. Turnover Plan – Contractor shall deliver a detailed description of the proposed approach to provide turnover planning in the event of Contract expiration or termination for any reason, including the following:

i. A summary of the support Contractor will provide for turnover activities and required coordination with OHA and/or another contractor assuming responsibilities.

ii. Approach to identifying and submitting all documentation, records, files, methodologies, and data necessary for Agency to continue the program.

iii. Resources and training that OHA or another contractor will need to take over required operations.

iv. Methods for tracking and reporting turnover results, including documentation of completion of tasks at each step of the turnover.

v. Document and verify the approach to securely transferring data during a turnover to ensure data integrity. Maintain data confidentiality, integrity, and availability.

m. Contractor shall ensure that Deliverables meet project management standards and best practices as described within the 6th edition of the Project Management Institute’s Project Management Body of Knowledge and will adhere to established oversight requirements outlined in the Contract. See:

Oregon Oversight Requirements at:

https://www.oregon.gov/das/OSCIO/Pages/StrategyStageGate.aspx Quality Standards from DAS policy 107-004-030 at:

https://www.oregon.gov/das/Policies/107-004-030.pdf

4. Maintenance and Operations (M&O).

Contractor shall provide M&O Services to ensure the continuous and ongoing availability and functionality of the Marketplace Production Environment, which includes at least:

a. Continuous and ongoing availability and functionality of the Marketplace Training Environment.

b. Availability of the Marketplace Testing Environment, as needed to validate and authorize changes to the Platform’s configuration (including change orders).

c. Ongoing compliance with responsibilities outlined in the Platform Annual Work Cycle Plan.

d. Maintenance and updates to the Platform, as needed, and performing any requested upgrades or changes required by OHA.

e. Compliance with contractual change management processes for any upgrade or other change to the Platform. Minimum expectations for change orders are in Section 7.1 of the Sample Contract.

f. Release Testing Plan and Release Testing, to include Contractor-performed load testing prior to each major release and up to two additional load tests, upon OHA’s written request (e.g., prior to Open Enrollment).

g. Help Desk Support Services to include incident response, defect resolution, incident triage, ticket management, and 24-hour availability for Agency staff to enter trouble tickets, incidents, defects, availability issues, data processing or reporting errors, escalation and other Agency requests, related to the Services.

h. Documentation Updates. Contractor shall ensure that all Platform documents are in alignment with then-current Platform functionality.

II. Consumer Assistance Center (CAC) Description

1. Detailed CAC Requirements. Detailed CAC Requirements are set forth in RFP Attachment H.

2. Contractor shall provide any information, reports, or documentation related to the Services as needed to comply with CMS requirements described in 45 CFR 155.105 and 155.106, including the Exchange Blueprint application.

3. The Solution must comply with the CMS technical requirements set forth in the Exchange Blueprint application and as required to meet the CMS operational readiness assessment prior to implementation.

4. Operational CAC.

a. By CAC Operational Readiness. Contractor shall prepare the CAC for operational readiness to support consumers and CAC personnel for Plan Year 2027 OEP, including any required hardware, software, furniture, equipment, construction, hiring and training of staff.

b. After CAC Operational Readiness. Contractor shall ensure a fully staffed and operational call center. These Services include support for re-verification of migrated consumer accounts as defined in the Consumer Messaging Plan and consumer education to support the anonymous plan comparison process. Contractor shall conduct CAC activities in accordance with the CAC Standard Operating Procedures Manual and Mailroom Standard Operating Procedures Manual (See RFP Section 3.3.3)

5. Maintenance and Operations (M&O). Contractor shall ensure the continuous and ongoing availability and functionality of the CAC, to include, at a minimum, the following:

a. Ongoing provision of consumer assistance in accordance with the terms of CAC Standard Operating Procedures Manual.

b. Ongoing compliance with the responsibilities outlined in the CAC Annual Work Cycle Plan.

c. Ongoing provision of mailroom services in accordance with the terms of the Mailroom Standard Operating Procedures Manual.

d. Ongoing compliance with the responsibilities outlined in the Mailroom Operations Plan (See RFP Section 3.3.3).

6. Additional Management Support Services. Additional management support services include, at a minimum, the following:

a. Weekly CAC Status Reports – Before CAC Operational Readiness, Contractor shall deliver a weekly CAC status report to OHA. At a minimum the CAC status report must include:

i. An overall project status,

ii. Status of the agreed upon functional areas of the project, and

iii. An update to an integrated project schedule.

Status reports can also include areas of concern for the Contractor and commentary about potential risks that might impact the timeline.

b. Monthly CAC Status Reports – After CAC Operational Readiness, Contractor shall deliver a similar monthly CAC status report to OHA. As requested by OHA, Contractor shall deliver such CAC status reports more frequently.

III. Key Person Requirements and Background Check Requirements

1. Proposer’s Key Person(s) must include:

a. Project Manager,

b. Security Architect,

c. ETL/Data Engineer,

d. Data Architect, and

e. Report Developer (or equivalent).

2. Contractor’s Key Persons must undergo appropriate background checks prior to commencing work under the Contract in accordance with Section 9.5 of RFP Attachment A, Sample Contract. Any changes to proposed staff will require OHA approval.