RFQ 27-05787 CIW Modernization Final 11.16.26.docx

DOCX document 117 KB Posted

Attached to
RFQ 27-05787 for CIW Modernization Roadmap Implementation
Solicitation number
BD-27-1060-ITD00-ITD00-135449
Issued by
Suffolk County, Massachusetts

About this file

This Request for Quotation (RFQ) is issued by the Commonwealth of Massachusetts Executive Office of Technology Services and Security (EOTSS) for CIW Modernization Roadmap Implementation services. EOTSS seeks qualified vendors to provide technical architecture, data engineering, development, and implementation support for modernizing the Commonwealth Information Warehouse (CIW), a centralized data platform serving over 1,500 users across Commonwealth agencies. The CIW modernization effort aims to improve data integration architecture, processing efficiency, operational reliability, and maintainability following the platform's migration to Snowflake, with a central objective of achieving end-to-end data latency of less than 24 hours for critical data flows. Services include modernization of Mosaic and Massachusetts Management Information System (MMIS) data pipelines, consolidation of staging and processing responsibilities, documentation of existing workloads, establishment of DataOps and DevOps foundations with data freshness monitoring, and planning and execution of an initial agency modernization effort. The RFQ was posted on November 16, 2026 at 3:00 PM, with bidder questions due by November 30, 2026 at 3:00 PM, Commonwealth responses estimated by December 2, 2026, and RFQ responses due by December 14, 2026 at 3:00 PM. Bidder demonstrations are scheduled for a date to be determined, with the Notice of Apparent Successful Bidder(s) estimated for January 8, 2027 at 3:00 PM. The RFQ is restricted to bidders on the statewide contracts ITS81 Professional Services and GIS Event Calendar. The specific contract term and renewal options are not detailed in the provided portion of the document.

The RFQ does not commit the Commonwealth to approve any Statement of Work, pay bidder preparation costs, or procure any services; the Agency reserves the right to accept or reject any bids, contract for some or all services offered, negotiate with qualified bidders, or cancel the RFQ in whole or in part. Pricing terms, set-asides, incumbent information, funding requirements, and specific contract amounts are not provided in the available document excerpt. The file notes that the resulting contract may be made available to other Executive Department entities at EOTSS's option with its prior approval. All RFQ responses and bids shall become public record under Massachusetts General Laws Chapter 66 and Chapter 4, Section 7(26), notwithstanding any confidentiality designations by bidders. Responses must be submitted through the Commonwealth's online procurement system, COMMBUYS.

View the file

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

Commonwealth of Massachusetts The Executive Office of Technology Services and Security

Commonwealth of Massachusetts Executive Office of Technology Services and Security

Request for Quotation EOTSS RFQ 27-05787 for CIW Modernization Roadmap Implementation COMMBUYS Bid Number: BD-27-1060-ITD00-ITD00-135449

November 16, 2026

IN ACCORDANCE WITH M.G.L. C. 66 AND M.G.L. C. 4, § 7 (26), THIS RFQ AND ALL RESPONSES HERETO INCLUDING THE WINNING BID SHALL BECOME PUBLIC RECORD, AND CAN BE OBTAINED FROM THE EXECUTIVE OFFICE OF TECHNOLOGY SERVICES AND SECURITY BY SUBMITTING A REQUEST AT https://www.mass.gov/executive-office-of-technology-services-and-security-prr. ANY PORTIONS OF A RESPONSE THAT ARE LABELED AS CONFIDENTIAL WILL STILL BE CONSIDERED PUBLIC RECORD.

General Procurement Information

General Information

Purchasing Entity: Executive Office of Technology Services and Security (“EOTSS”) or (“Agency”)

Address: One Ashburton Place, Eighth Floor, Boston, MA 02108

Procurement Contact: Shawn Johnson

Telephone: 617-406-8329

E-Mail Address: shawn.johnson@mass.gov

RFQ File Number and Title: EOTSS RFQ 27-05787 for CIW Modernization Roadmap Implementation

Attachments:Attachment A – COMMBUYS Instructions
Attachment B – Gap Alignment Table
Forms:Form 1 – RFQ Response Form
Form 2 – Statement of Work Template

This Request for Quotes (“RFQ”) does not commit the Commonwealth of Massachusetts (“Commonwealth”) or Agency to approve a Statement of Work, pay any costs incurred in the preparation of a Bidder’s response to this RFQ or to procure or contract for products or services. The Agency may: (i) accept or reject any and all bids received as a result of this RFQ; (ii) contract for some, all, or none of the products and services offered by Bidders in response to this RFQ; (iii) negotiate with one or more qualified Bidders; or (iv) cancel, in part or in its entirety, this RFQ if it is in the best interest of the Commonwealth to do so.

The Agency may amend this RFQ at any time prior to the date the responses are due. Any such amendment will be posted to the Commonwealth’s procurement website, COMMBUYS (www.commbuys.com).

Bidders must submit their bids through the Commonwealth’s online procurement system, COMMBUYS, as detailed in Attachment A. Bidders are advised to check this site regularly, as this will be the sole method used for notification of changes.

Eligible Bidders

This RFQ is restricted to Bidders on the following Statewide Contracts:

· ITS81 Professional Services and GIS

Event Calendar

All times in this RFQ are in prevailing Eastern Time. Responses must be received no later than the response due date and time indicated below or they will not be evaluated. Bidders must have their responses fully loaded and accepted in COMMBUYS prior to the RFQ Response Due date and time listed below. Bidders are urged to allow sufficient time to upload their entire response.

Procurement Step
Due Date
Time
RFQ Posted
11/16/2026
3:00PM
Bidder Questions Due
11/30/2026
3:00PM
Commonwealth Responses posted to COMMBUYS (estimated date)
12/2/2026
3:00PM
RFQ Response Due
12/14/2026
3:00PM
Bidder Demonstrations Scheduled (estimated date)
TBD*
Bidder Demonstrations (estimated date)
TBD*
Notice of Apparent Successful Bidder(s) posted (estimated date)
1/8/2027
3:00PM

Purchasing Agency

The Executive Office of Technology Services and Security is responsible for the development of IT policy and implementation and oversight of all information technology investments for the Commonwealth and its respective agencies. EOTSS has broad statutory authority to effectuate the goals prompting IT consolidation in Chapter 64 of the Acts of 2017, as memorialized and articulated in M.G.L. c. 6A, s. 7A and M.G.L. c. 7D. As the lead enterprise IT and cybersecurity organization for the Executive Branch, EOTSS provides responsive digital and security services, and oversees and manages the enterprise technology and digital infrastructure and services for over 125 state agencies and over 43,000 state employees. EOTSS provides Enterprise Cybersecurity and Risk Management services, Infrastructure and Network services, End-User Support and IT services, Digital and Data services, Strategy Management and Consulting services, and additional IT-focused services to the Executive Branch and other Commonwealth users.

☐ If checked, the contract resulting from this RFQ will be made available to other Executive Department entities for the purchase of products or services. EOTSS may, in its option, require its prior approval for such entities to purchase products or services.

Description and Purpose of Procurement

Background The Commonwealth of Massachusetts is undertaking a modernization of the Commonwealth Information Warehouse (CIW), a centralized data platform that provides more than 1,500 users across Commonwealth agencies with access to financial, budgetary, human resources, payroll, and other operational data for reporting, analysis, and decision-making. Following the migration of CIW to Snowflake, opportunities have been identified to improve the platform's data integration architecture, processing efficiency, operational reliability, and maintainability. This modernization effort will focus on strengthening the existing CIW environment, including improving Mosaic, the Commonwealth’s financial application that replaced the Massachusetts Management Accounting & Reporting System (MMARS) in 2026, and Massachusetts Management Information System (MMIS) data delivery, consolidating staging and processing responsibilities, and establishing more consistent data engineering and operational practices. A central objective is to achieve end-to-end data latency of less than 24 hours for critical in-scope data flows, measured from when data becomes available at its authoritative source to when it is accessible to CIW users.

As part of these efforts, the Commonwealth previously engaged a vendor to conduct a gap analysis, which will inform its priorities for the CIW Modernization project. The 19 gaps below are drawn from that previously completed gap analysis. Each gap has a stable ID used in the workstream response tables and the traceability matrix. Gap IDs denote traceability, not a commitment that every gap is fully closed under this RFQ.

GAP ID
GAP AREA
IDENTIFIED GAP
CURRENT-STATE GAP / NEED
G01 | Area 1
Source delivery path

1 - Sourcing and Delivery

Source delivery path
Extra handoffs and copies before CIW; delivery ownership not controlled by CIW.
G02 | Area 1
Source footprint

1 - Sourcing and Delivery

Source footprint
Ingested data exceeds demonstrated downstream use; reduction lacks dependency evidence.
G03 | Area 1
Change capture

1 - Sourcing and Delivery

Change capture
Wholesale reloads and unreliable change signals limit incremental processing.
G04 | Area 2
Data model and consumer contract

2 - Architecture and Processing

Data model and consumer contract
Mosaic 4.0 data conformed to legacy 3.9, discarding newer source detail.
G05 | Area 2
Processing separation

2 - Architecture and Processing

Processing separation
Landing, conformance and transformation are intertwined and cannot recover independently.
G06 | Area 2
Technology fit

2 - Architecture and Processing

Technology fit
Legacy tools carried forward without reassessing Snowflake-native fit.
G07 | Area 3
Operational controls

3 - Governance and Trust

Operational controls
Limited boundary controls; issues are often found first by consumers.
G08 | Area 3
Data quality

3 - Governance and Trust

Data quality
Quality rules and thresholds vary; no common publication gate.
G09 | Area 3
Data freshness

3 - Governance and Trust

Data freshness
Business date and freshness not published; consumers cannot confirm currency.
G10 | Area 3
Metadata and lineage

3 - Governance and Trust

Metadata and lineage
No enterprise metadata backbone or dependable lineage and usage visibility.
G11 | Area 3
Security and entitlements

3 - Governance and Trust

Security and entitlements
Access logic repeated in views; sensitive data inconsistently classified.
G12 | Area 4
Interface standards

4 - Consumption

Interface standards
Inconsistent distribution patterns and no preferred interface standard.
G13 | Area 4
Downstream copies

4 - Consumption

Downstream copies
Data copied into agency/desktop tools without validated need.
G14 | Area 4
Consumer visibility

4 - Consumption

Consumer visibility
CIW lacks consistent visibility into downstream users and dependencies.
G15 | Area 5
Operating model

5 - Operations and Continuity

Operating model
Accountability across organizations; decision rights and escalation not defined.
G16 | Area 5
Continuity and recovery

5 - Operations and Continuity

Continuity and recovery
Recovery is person-dependent; no tested continuity model for critical data.
G17 | Area 5
DataOps automation

5 - Operations and Continuity

DataOps automation
Uneven automation; monolithic procedures limit restart points.
G18 | Area 5
Release management

5 - Operations and Continuity

Release management
Promotion, release evidence and rollback are manual and inconsistent.
G19 | Area 5
Operational knowledge

5 - Operations and Continuity

Operational knowledge
Incomplete runbooks and inconsistent escalation; reliance on individuals.

The Executive Office of Technology Services and Security (EOTSS), through its Office of Data Innovation and Analytics (ODIA), is seeking a qualified vendor to provide technical architecture, data engineering, development, and implementation support for the CIW modernization effort. The selected vendor will work closely with the CIW team, the Office of the Comptroller, relevant source-system owners, and agency stakeholders to assess existing data flows, identify and address processing bottlenecks and upstream dependencies, and implement improvements to data ingestion, transformation, and delivery. Services will include modernization of Mosaic and MMIS data pipelines; consolidation of staging and processing responsibilities; documentation of existing workloads; establishment of DataOps and DevOps foundations, including data freshness monitoring and exception reporting; and planning and execution of an initial agency modernization effort. The engagement will prioritize near-term operational improvements while establishing a scalable, maintainable Snowflake-native architecture that supports incremental modernization and the Commonwealth's evolving data needs.

Description of Services

Project Phase
Tasks
Deliverables
Metrics of Acceptance
Proposed Completion Date
1 - Mobilization & Governance
1. Conduct kickoff with Commonwealth stakeholders and providers.

2. Confirm objectives, scope, schedule, priorities and dependencies.

3. Establish governance, decision rights, escalation and RACI.

4. Assign accountable service owners and reporting cadence.

5. Define latency baseline, critical data flows, measurement boundaries, exceptions and verification method for the <24-hour goal.

6. Create methods for establishing showback/chargeback monitoring via Snowflake.

1. Approved project management plan and schedule.

2. RACI, stakeholder communications plan and risk/dependency register.

3. In-scope critical-feed list and agreed latency baseline / measurement plan.

4. Create showback/chargeback dashboard that shows utilization by appropriate groupings to understand consumption.

• Scope, milestones and RACI approved by the Commonwealth.

• Accountability assigned for each workstream and critical feed.

• Documented source-to-consumer latency calculation and acceptance test plan approved.

February 2027

2 — Mosaic Direct Share Enablement
1. Assess Mosaic 4.0 delivery path, existing handoffs, data usage and dependencies.

2. Agree source ownership and secure-share design with Mosaic provider.

3. Implement direct Snowflake sharing of only required source objects.

4. Assess change tracking, delta capture, retention and incremental synchronization.

5. Reconcile outputs, document lineage and plan controlled cutover.

6. Demonstrate impact on end-to-end data freshness.

1. Mosaic secure-sharing design and required-object inventory.

2. Configured direct data share and change capture approach.

3. Reconciliation, latency-test and cutover evidence.

4. Source lineage and operational runbooks.

• Authorized CIW processes can access all agreed Mosaic objects.

• Reconciliation meets jointly approved tolerances before cutover.

• Measured latency for scoped Mosaic flows is <24 hours during agreed validation period, or documented and approved provider-side exceptions remain.

• Commonwealth approves production cutover.

April 2027

3 — MMIS Share Enablement
1. Assess current MMIS database connection and downstream needs.

2. Confirm provider participation and supported secure-share topology and objects.

3. Design and deliver a controlled Snowflake data-share pilot.

4. Validate availability, security, change tracking and processing compatibility.

5. Measure freshness and recommend phased production implementation and rollback.

1. MMIS sharing requirements and architecture.

2. Working secure-share pilot and documented test results.

3. Latency assessment, risks and production cutover recommendation.

• Pilot provides authorized access to agreed MMIS objects.

• Security and completeness tests pass approved criteria.

• Pilot demonstrates <24-hour source-availability-to-CIW latency for the scoped data, or identifies specific remediations and approved exceptions.

• Commonwealth accepts implementation recommendation.

March 2027

4 — Mosaic Staging and Processing Integration
1. Inventory Mosaic staging, transformation, ownership and cross-account dependencies.

2. Sequence transition after direct sharing dependencies are satisfied.

3. Move agreed processing into the EOTSS account and CIW operating model.

4. Validate migrated workflows and outputs through parallel runs.

5. Define monitoring, restart, recovery, documentation and handoff.

6. Optimize critical-path processing to support the <24-hour target.

1. Current-state assessment and target-state architecture.

2. Migration plan, implemented processing workflows and test report.

3. Updated runbooks, responsibility assignments and knowledge transfer.

• Approved workflows operate in designated CIW environment.

• Parallel processing outputs meet agreed reconciliation criteria.

• End-to-end latency for scoped Mosaic pipelines meets <24 hours during agreed test window, subject to approved exceptions.

• CIW operational owners accept handoff.

May 2027

5 — Legacy Process Documentation and Dependency Mapping
1. Inventory in-scope production jobs, including non-Mosaic and one-off processes.

2. Document source-to-target maps, lineage and legacy consumption views using Commonwealth-approved tools.3. Identify downstream consumers, business dates, schedules and dependencies.

4. Record operational procedures, exceptions, recovery and owners.

5. Document latency baseline, arrival windows and bottlenecks per critical flow.

6. Assess unused feeds and unnecessary duplication using telemetry.

1. Production process inventory and source-to-target mappings.

2. Lineage, consumer, usage and dependency registers as well as relevant metadata documentation for consumption views and source tables.

3. Operational runbooks and documentation maintenance plan.

4. Current-state freshness and latency baseline by critical flow.

• All agreed in-scope critical workflows documented and owner-reviewed.

• Consumer/dependency register supports impact analysis.

• Baseline includes measured current latency, evidence source and remediation candidates for the <24-hour target.

• Documentation repository accepted by Commonwealth.

May 2027

6 — DataOps and DevOps Foundations
Modern best practices that enable rapid iteration and safety nets such as trunk based branching with main branch protected and prod grade and feature/hot fix branches short lived;

PR gates where commit triggers unit tests, linting, static security, infra checks, data quality tests and automated container builds. Only PRs with 'x' configurable approvals and passing gates can merge to main promoted via GitHub actions and Jira workflow Testing Pyramid- unit tests->integration tests->data quality tests that is shift-left and modular and automated in CI/CD Infrastructure as code (IaC) automation: All environment configurations (Dev, Test, UAT, Prod) defined in code — not manual clicks

1. Assess release, testing, monitoring, version control and operations.

2. Implement initial Git-based asset control and CI/CD for a pilot workload.

3. Define validation gates, release verification and rollback procedures.

4. Implement freshness monitoring, event logging and exception alerting for critical flows.

5. Set up reusable automated testing, deployment and recovery patterns.

6. Document standards and transfer knowledge to CIW staff.

1. DataOps standards, repository conventions and initial CI/CD pipeline.

1a. Multi environment setup with clearly defined purpose, access, data, deployment and promotion gates where what tests and actions are automated in each environment.

1b. Should support modular development, modular deployment with shift-left testing

2. Testing/quality-gate pattern, release and rollback runbooks.

3. Data Observability dashboard/report for schema profiling, query latency, pipeline failures, data freshness and alerting approach.

4. Knowledge transfer artifacts.

• Pilot deploys and validates through approved CI/CD workflow.

• Checks and rollback are demonstrated in a test environment.

• Critical pilot feed publishes trustworthy source and consumer timestamps; automated breach detection identifies latency >=24 hours.

• Commonwealth accepts procedures and knowledge transfer.

April 2027

7 — Initial Agency Discovery and Future-State Modernization Planning. Contingent on FY28 Funding
1. Support Commonwealth selection of first agency based on readiness.

2. Interview business and technical stakeholders and map key usage.

3. Define in-scope source data, CIW core boundary and consumption requirements.

4. Inventory bridge/legacy views and design initial certified semantic views.

5. Agree enterprise versus agency governance and phased coexistence plan.

6. Prepare implementation proposal, resource estimate and <24-hour latency design and test plan for first agency.

1. Agency readiness and selection assessment.

2. Discovery requirements, boundary, consumption and dependency inventory.

3. Preliminary semantic-layer, governance and migration design.

4. First-agency implementation proposal and level-of-effort estimate including latency objectives.

• Commonwealth selects initial agency and reviews discovery.

• Data boundary and critical consumers confirmed.

• Proposal includes source-to-consumer <24-hour freshness architecture, instrumentation, baseline gaps, test plan and assumptions.

• Proposal accepted as planning deliverable (not production deployment).

October 2027

Vendor Qualifications and Project Resources

Vendors shall demonstrate applicable experience in enterprise data platforms, Snowflake Secure Data Sharing, change capture, ELT, metadata and lineage, quality controls, access policies, CI/CD, production operations and knowledge transfer. Public-sector delivery experience is preferred.

RESOURCE ROLE
RESPONSIBILITY
Project Manager
Schedule, stakeholder coordination, risks, RACI and escalation.
Solution Architect
Platform architecture, account topology, security and release governance.
Snowflake / DataOps Architect
Snowflake implementation, data processing and technical operational design.
Data Engineers
Sharing, migration, transformation, quality instrumentation and documentation.
Data and Technical Analysts
Inventory, mappings, consumer lineage and requirements.
Governance SME
Metadata, catalog, lineage, ownership and usage telemetry.

Bid Preparation Requirements:

· Propose a firm fixed price for all services with milestone payments by completion of Project Phase

· Price Project Phae 7 (Initial Agency Discovery and Future-State Modernization Planning) as a separate, optional Phase.

Clearly demonstrate the Bidder's relevant experience and qualifications performing services of similar scope and complexity, as well as its capacity to complete all required Project Phases by their respective Planned Completion Dates.

Identify all assumptions, risks, and dependencies associated with the proposed pricing, performance of the Services, and successful completion of the Project Phases within the specified timeframes.

EOTSS reserves the right to contract with the selected Bidder for additional, related services on a Fixed-Price or Time & Materials basis.

Estimated Term

The estimated term of any contract entered into under this RFQ shall consist of an initial 36-month term and may be renewed or extended upon written agreement by the awarded Bidder and the Agency. The initial term and all renewals or extensions shall be referred to collectively as the “Term.” The maximum Term length will be governed by the applicable Statewide Contract.

Order of Precedence

The agreement resulting from this RFQ shall consist of the following documents in the following order of precedence:

(1)the Commonwealth Terms and Conditions or the Commonwealth Terms and Conditions for Information Technology Contracts, as applicable;
(2)the Commonwealth Standard Contract Form;
(3)the applicable Statewide Contract RFR;
(4)the Bidder’s response thereto;
(5)this RFQ 27-05787 for CIW Modernization Roadmap Implementation (including all amendments, and clarifications hereto);
(6)any agreement negotiated between and executed by the parties; and
(7)the Bidder’s response to this RFQ (including all amendments, clarifications, and best and final offers)

Data Classification and the Use of Generative Artificial Intelligence (GenAI)

Data Classification

The Commonwealth of Massachusetts collects, manages, and stores information to support its business operations. The Commonwealth is committed to preserving the confidentiality, integrity, and availability of its information assets. Such information assets may include, without limitation, personal information, confidential information, and information protected under applicable law. Bidder agrees and acknowledges that its access, or potential access, to certain information assets may require certifications, background checks, or other additional requirements. Agency anticipates that the awarded Bidder will have access, or potential access, to the following data types as a result of providing services/products to Agency under this RFQ.

Data Type
Applicable Laws and Regulations
Additional Requirements
X
Personally Identifiable Information
M.G.L. c. 93H

M. G. L. c. 66A

☐
Payment Card Information
PCI Standards
☐
Family Educational Rights and Privacy Act data
Family Educational Rights and Privacy Act
☐
Protected Health Information
Health Insurance Portability and Accountability Act of 1996
-Commonwealth of Massachusetts Data Management and Confidentiality Agreement
☐
Federal Tax Return Information
Publication 1075
-Publication 1075 Exhibit 7

-Commonwealth of Massachusetts Dept. of Revenue background check

☐
Criminal Offender Record Information
FBI Security Addendum

NCIC 2000 Operating Manual CJIS Security Policy Title 28, CFR Part 20 -Dept. of Criminal Justice Information certification -background check

☐
Criminal Justice Information
FBI Security Addendum

NCIC 2000 Operating Manual CJIS Security Policy Title 28, CFR Part 20 -Dept. of Criminal Justice Information certification -background check

☐
Social Security Administration Data
Privacy Act

5 U.S.C. 552a s. 1106 -background check

☐
Other
☐
None/Not Applicable

Bidder certifies that its products or services, as offered in its RFQ response, meet all applicable legal and regulatory requirements pertaining to the identified data types indicated above. Bidder also agrees to enter into additional agreement(s), as reasonably requested by the Commonwealth prior to gaining access, or potential access, to Commonwealth information assets. Bidder acknowledges that the list above is not exhaustive, and Agency may designate additional data types, applicable laws and regulations, and additional required documentation in the contract resulting from this RFQ or any amendment thereto.

Use of Generative AI

The following provisions apply both to Generative AI (“GenAI”) that the Contractor proposes to use or will use to fulfill its obligations under a contract, and to GenAI tools that Contractor will provide directly to the Agency for its own use.

Use of GenAI Conditioned on Compliance with these Terms

Contractor shall not use GenAI to fulfill any obligations under the contract with the Agency or provide any GenAI tools to the Agency unless the contract includes terms consistent with this section, “Use of Generative AI”.

Use and Deletion of Agency Data

Contractor shall not use Agency Data (defined as data provided by Agency and any data derived therefrom, including metadata (collectively, the “Agency Data”) for training, tuning, or testing the GenAI model unless required for the performance of Services and where the Agency has provided written consent for both the use of the GenAI tool and the Agency Data. Any permitted Agency Data inputs will be strictly limited to the data and inputs provided under this Agreement and will not extend to other Agency intellectual property. If the GenAI system/solution or Contractor’s provision of other services under the Contract require the use of Agency Data as GenAI training data, Contractor shall only use Agency Data as strictly necessary to provide the Services. Both the Contractor and Agency shall retain control over their data and have the ability to delete their data. Contractor shall delete all Agency Data within 30 days of receiving written notification from the Agency and shall confirm in writing that all Agency Data has been deleted.

Intellectual Property, Accuracy, Bias, Discrimination, Mitigation and Quality Control of GenAI

Contractor’s use of GenAI will be specifically limited to the automated creation of the material expressly defined in this Agreement’s scope. All GenAI usage will be configured to strictly align with the Agency’s brand guidelines. Contractor will implement robust quality control measures to review and approve, through non-automated means, all content generated by the GenAI tool before it is published, distributed or used in any business context. The review process must occur prior to any content being deployed or utilized in business operations, and every month thereafter, and must ensure that the content aligns with all the relevant policies, regulations and quality expectations. Additionally, the Contractor must identify, document and mitigate any biases, discrimination or otherwise unlawful outcomes based on race, color, religion, sex, national origin, disability, age, genetic information, or any other protected characteristic under applicable law in the AI solution or services.

Breach and Termination

Notwithstanding any other terms to the contrary in the Solicitation, or any contract entered by Contractor, Contractor’s failure to meet any of the obligations set forth in this provision “Use of Generative AI” will constitute a breach of the contract entitling the Commonwealth to terminate the contract for cause and without penalty and to pursue damages and any other legal or equitable remedies to which it may be entitled.

Amendments to GenAI Terms

The Commonwealth reserves the right to negotiate an amendment incorporating additional GenAI contract provisions into the contract or terminate in whole or in part any contract that, in the sole determination of the Commonwealth, presents an unacceptable level of risk to the Commonwealth with respect to GenAI.

Provision of Evaluative Information

Contractor shall regularly monitor the performance of the GenAI system to detect and rectify system behavior that violates any of these provisions. Contractor shall promptly communicate the discovery of system behavior that violates any of the requirements in this ‘Use of Generative AI’ section to the Commonwealth, including the potential impact to the services.

Order of Precedence

This section “Use of Generative AI” will take precedence over any conflicting GenAI contract terms provided by the Contractor to the Agency.

Updates to the Model/Platform

Contractor shall provide reasonable notice to the Agency of any updates to the GenAI model/platform that substantially impact the services prior to the updates taking place.

Audit

Contractor certifies that on an annual basis, or upon request of the Agency, its GenAI systems, models, or platforms, and related processes, training materials, training data sets, and its use and management of synthetic data, comply with the requirements of the Agreement. Contractor further certifies that it retains GenAI audit logs consistent with the terms of Schedule F of the Commonwealth’s Records in Common Schedule. Such certification shall be made in writing by an authorized officer of the Contractor and shall be subject to the same confidentiality protections as set forth in the Agreement, except as disclosure is required by law.

Control

For GenAI solutions/systems/models developed for the Agency, Contractor shall provide mechanisms through which the Agency can oversee the development and testing of the GenAI and where necessary override its functionality through human intervention.

Disentanglement

As of the termination date of the contract, or other date agreed upon by the Parties or determined by the Commonwealth, the Contractor shall cease the use of Generative AI in service delivery to the Agency; disengage Generative AI components; and comply with the transition/termination assistance obligations set forth in the contract.

Right to Use

During the term of the contract, Contractor shall ensure that the Agency has access to the full functionality offered by the GenAI systems/solutions used in the scope of services, including without limitation the ability to use the system, develop and test solutions, and make copies (with appropriate commercial mechanisms) without any limitations or restrictions. This clause shall survive the term of the contract if, in the contract, the Agency identifies the use of the Generative AI system as of strategic importance.

Localization

GenAI systems/solutions and data shall be hosted and stored in a cloud location controlled or approved by the Agency.

Representations

Each representation and warranty set forth in the contract applicable to information technology shall apply with equal force to GenAI solutions/systems. In addition, Contractor warrants that the GenAI that is part of the system/solution shall be accurate and generate unbiased results and, should Contractor fail to deliver on this warranty, it shall remedy, at no cost to the Agency, any such defects in the GenAI system/solution.

Additional Requirements

Enterprise Information Security Standards and Policies

All products and services provided to the Commonwealth must comply with all applicable policies adopted by the Agency, which shall be made available to Bidder prior to contract execution. At a minimum, all goods and services provided to the Commonwealth must comply with the Enterprise Information Security Standards and Policies (https://www.mass.gov/handbook/enterprise-information-security-policies-and-standards). Bidders shall provide information that demonstrates that their security practices meet the requirements detailed in these policies.

Accessibility for IT Solutions Contract Language

The Commonwealth of Massachusetts’ Enterprise Digital Accessibility Policy drives ongoing efforts to make Massachusetts’ Digital Assets, including those delivered by a third-party, accessible and usable by all persons as required by state and federal laws. Where a Deliverable includes a Digital Asset, such Deliverable must meet the Commonwealth’s Digital Accessibility Standards.

The Commonwealth’s Digital Accessibility Standards include the Web Content Accessibility Guidelines (WCAG) version 2.1 level A and AA developed by the World Wide Web Consortium (W3C). Bidder must comply with the digital accessibility obligations set forth in the Vendor Digital Accessibility Contract Language and Vendor Digital Accessibility Testing Obligations and any subsequent versions or amendments.

During the bidding process and upon request, Bidder shall cooperate and provide the Commonwealth, or any third-party digital accessibility service provider procured by the Commonwealth, access to test its digital products for accessibility at no additional cost to the Commonwealth. The digital products must be available to the Commonwealth for evaluation prior to purchase and on an ongoing basis.

Contract Negotiation and Amendments

The Agency may negotiate changes to the original performance measures, quantities, Term length, and requirements identified in this RFQ at any time, provided that such changes are consistent with the scope of this RFQ. The Agency may negotiate and execute contract amendments with the awarded Bidder(s) which the Agency reasonably determines are within the scope of this RFQ and necessary to result in best value to the Commonwealth.

Promotional Materials

Bidder must not reference the Agency or the Commonwealth in any promotional or marketing materials, including but not limited to use of the Agency’s or the Commonwealth’s name or logo, without first obtaining the Agency’s prior written approval for such use. Bidder must not use the Commonwealth’s seal in any promotional or marketing materials.

Bidders are discouraged from including extraneous promotional or marketing materials in their responses to this RFQ and excessive promotional or marketing materials may detract from the Bidders’ overall score.

Pending Litigation

Bidder must affirm that there is no pending litigation involving the Bidder, Provider, or the services provided in the response, that may impair or interfere with the Agency’s right to use the services. Bidder must warrant that there are no actual or threatened actions arising from, or alleged under, any intellectual property rights of any third party.

Oral Presentations and Demonstrations

In its discretion, the Agency may invite one or more Bidders whose responses have been judged competitive and responsive in the course of the evaluation to participate in a facilitated oral presentation, including a demonstration of the proposed services. The Agency may use these demonstrations and oral presentations to clarify aspects of the Bidder’s response or to inquire as to the Bidder’s approach, recommendations, and experience. The Agency may adjust its scoring of a prospective Bidder based on the Bidder’s performance during production demonstration and/or oral presentation.

The Agency reserves the right to apply restrictions to the structure and content of Bidder’s product demonstrations and oral presentations. Demonstrations and oral presentations shall not be open to the public nor to any competitors. The schedule of the demonstrations and oral presentations will be arranged directly with the Bidders selected by the Agency. Failure of a Bidder to agree to a date and time may result in rejection of the Bidder’s response.

Review Rights

Responses to this RFQ may be reviewed and evaluated by any person(s) at the discretion of the Agency including non-allied and independent consultants retained by the Agency for the sole purpose of evaluating and analyzing responses.

Permitted Copies

If applicable, Bidders must authorize the Agency to make, keep and retain a reasonable number of machine-readable copies of all licensed, core software components included in the deliverables for testing, backup or archival purposes (the “Permitted Copies”). Such authorization shall be provided to the Agency at no additional cost.

Risk Management

Bidder must indicate the types of system audits or assessments (e.g. SOC 2) it conducts or engages third parties to conduct on its behalf, pertaining to the quoted products or services, and the frequency of such audits or assessments. Any time after submitting its Bid, upon Agency's request, Bidder shall provide audit or assessment reports to the Agency.

Warranties

Bidder shall provide all warranties listed below. Additional warranties may be agreed to in the contract resulting from this RFQ.

Bidder must provide all warranties required by the applicable Statewide Contract.

Bidder and its subcontractors will be sufficiently staffed and equipped to fulfill Bidder’s obligations under any SOW or engagement resulting from this RFQ. Bidder warrants that it shall be responsible for the actions and omissions of all subcontractors and shall ensure all subcontractors’ compliance with the terms of an agreement resulting from this RFQ.

Bidder’s services will be performed: (a) by appropriately qualified and trained personnel; (b) with due care and diligence and to a high standard of quality as is customary in the industry; (c) in compliance with the Milestone Schedule and the terms and conditions of this RFQ and any contract hereunder; and (d) in accordance with all applicable professional standards for the field of expertise.

The Deliverables will substantially conform with the Deliverable descriptions set forth in any SOW or engagement resulting from this RFQ.

All media on which the Bidder provides any software shall be free from defects.

All software delivered by the Bidder under the applicable Statewide Contract or this RFQ shall be free of Trojan horses, back doors, and other malicious code.

Bidder will obtain all rights, grants, assignments, conveyances, licenses, permissions and authorizations necessary or incidental to any materials owned by third parties, including data to train Generative AI models, supplied or specified by the Bidder for incorporation in the Deliverables to be developed under the applicable Statewide Contract.

Documentation to be provided by the Bidder shall be in sufficient detail so as to allow suitably skilled, trained, and educated Agency personnel to understand the operation of the Deliverables. Bidder agrees to promptly, at no additional cost to the Agency, make corrections to any documentation that does not conform to this warranty.

Bidder warrants that any systems that Bidder creates or modifies will operate in conformance with the Specifications for the system or modifications for six (6) months after acceptance (“Warranty Period”). As used in this RFQ, “Specifications” means (i) the requirements set forth in this RFQ, (ii) the functional, performance, and interoperability requirements set forth in any agreement entered hereunder; and (iii) the functionality and description provided in Bidder’s response to this RFQ. If EOTSS discovers a non-conformity during the Warranty Period, then the Bidder shall use commercially reasonable efforts to correct the non-conformity or provide a work around that is acceptable to the Agency (a “Fix”). If Bidder is unable to remedy a non-conformity or to provide a Fix that is acceptable to the Agency within a reasonable period of time, then the Agency may terminate any agreement effective immediately upon written notice to Bidder. Any replacement or error correction will not extend the original Warranty Period. During the Warranty Period, Bidder will not charge the Agency for services, parts, labor, or transportation

All content that may be created by GenAI is a work made for hire under U.S. Copyright law. To the extent any GenAI content may not be considered a work made for hire under applicable law, as part of the Contract, Contractor assigns to Agency, in perpetuity, all right and interest to such GenAI content without the need for further consideration. In addition, content created from the Commonwealth provided prompt is not a derivative work of the GenAI training data. Notwithstanding the preceding sentence, in the event a court of competent jurisdiction determines that content created from a Commonwealth-provided prompt constitutes a derivative work of the GenAI training data, Contractor agrees to grant the Commonwealth unlimited, irrevocable, worldwide, perpetual, royalty-free, non-exclusive right, and license to use, modify, reproduce, perform, release, display, create derivative works from, and disclose the content for any Commonwealth business.

EOTSS GenAI Policy

The Commonwealth consistently seeks to realize the benefits of new technology, in particular generative artificial intelligence (AI). Contractor must comply with the Enterprise Use and Development of Generative Artificial Intelligence Policy issued by EOTSS on January 31, 2025, as it may be amended from time to time. Please follow this link to the policy: www.mass.gov/doc/enterprise-use-and-development-of-generative-artificial-intelligence-policy/download.

Post-Quantum Cryptography (PQC)

Contractor solutions should support migration to post-quantum cryptographic standards approved or recommended by NIST or other recognized industry, governmental, or international standards bodies, and maintain cryptographic agility without requiring complete system replacement. If complete system replacement is necessary to support such migration, the transition shall be performed at no additional cost to the Commonwealth.

Bidder Responses

Bidders must complete the attached RFQ Response Form (Form 1) and a Template Statement of Work (Form 2).

The responses to this RFQ will be evaluated based on the criteria listed below, in descending order of importance with the most important criteria listed first. The procurement management team may remove from further consideration non-responsive bids and bids that do not include all required items listed in Section VII (Bidder Responses). Prior to such an exclusion, the Agency may request one or more clarification(s) from Bidder. A Bidder’s response may be excluded for failure to meet the Agency’s budgetary thresholds. Should this RFQ result in a contract with an annual spend amount of less than $250,000, bids from certified small businesses are highly desired, in accordance with ReOrg Plan S.2937 “An Act to Elevate the Supplier Diversity Office to Ensure Equal Opportunity in State Contracting,” and Agency will follow guidance provided by the Supplier Diversity Office in evaluating Bidder responses.

Any remaining responses will be evaluated based upon:

1. Responsiveness to the Requirements of the RFQ

2. Quality and Approach to Service Delivery

3. Proposed Timeline for Commencement and Delivery of Services

4. Price, as provided in the Cost Table

ATTACHMENT A – COMMBUYS Instructions

Interested Bidders must submit their response using COMMBUYS.

Useful links:

1. Job aid on how to submit a quote: https://www.mass.gov/doc/how-to-create-a-quote-in-commbuys/download

1. Webcast: How to Locate and Respond to a Bid in CommBuys, which will familiarize bidders with CommBuys terminology, basic navigation, and provide guidance for locating bid opportunities in CommBuys and submitting an online quote.

1. Bidders MUST have their complete bid fully loaded and submitted prior to the time and date listed in the calendar. COMMBUYS will not allow for bids to be submitted after the posted time.

Bidder may contact the CommBuys Help Desk at CommBuys@state.ma.us or call during normal business hours (8AM – 5PM, Monday – Friday) at 1-888-627-8283 or 617-720-3197.

Written questions via the Bid Q&A on COMMBUYS

The “Bid Q&A” provides the opportunity for Bidders to ask written questions and receive written answers from the Strategic Sourcing Team (SST) regarding this Bid. All Bidders’ questions must be submitted through the Bid Q&A found on COMMBUYS (see below for instructions). Questions may be asked only prior to the Deadline for Submission of Questions stated in the Procurement Calendar. The issuing department reserves the right not to respond to questions submitted after this date. It is the Bidder’s responsibility to verify receipt of questions.

Please note that any questions submitted to the SST using any other medium (including those that are sent by mail, fax, email or voicemail, etc.) will not be answered. To reduce the number of redundant or duplicate questions, Bidders are asked to review all questions previously submitted to determine whether the Bidder’s question has already been posted.

Bidders are responsible for entering content suitable for public viewing, since all of the questions are accessible to the public. Bidders must not include any information that could be considered personal, security sensitive, inflammatory, incorrect, collusory, or otherwise objectionable, including information about the Bidder’s company or other companies. The PMT reserves the right to edit or delete any submitted questions that raise any of these issues or that are not in the best interest of the Commonwealth or this Bid.

All answers are final when posted. Any subsequent revisions to previously provided answers will be dated.

It is the responsibility of the prospective Bidder and awarded Bidder to maintain an active registration in COMMBUYS and to keep current the email address of the Bidder’s contact person and prospective contract manager, if awarded a contract, and to monitor that email inbox for communications from the Purchasing Department, including requests for clarification. The Purchasing Department and the Commonwealth assume no responsibility if a prospective Bidder’s/awarded Bidder’s designated email address is not current, or if technical problems, including those with the prospective Bidder’s/awarded Bidder’s computer, network or internet service provider (ISP) cause email communications sent to/from the prospective Bidder/Awarded Bidder and the Purchasing Department to be lost or rejected by any means including email or spam filtering.

Locating Bid Q&A

Log into COMMBUYS, locate the Bid, acknowledge receipt of the Bid, and scroll down to the bottom of the Bid Header page. The “Bid Q&A” button allows Bidders access to the Bid Q&A page.

ATTACHMENT B – Gap Alignment Table

Gap Register | Identified Gaps and Reference IDs The 19 gaps below are drawn from a previously collected Gap document. Each gap has a stable ID used in the workstream response tables and the traceability matrix. Gap IDs denote traceability, not a commitment that every gap is fully closed under the base RFQ.

GAP ID
GAP AREA
IDENTIFIED GAP
CURRENT-STATE GAP / NEED
G01 | Area 1
Source delivery path

1 - Sourcing and Delivery

Source delivery path
Extra handoffs and copies before CIW; delivery ownership not controlled by CIW.
G02 | Area 1
Source footprint

1 - Sourcing and Delivery

Source footprint
Ingested data exceeds demonstrated downstream use; reduction lacks dependency evidence.
G03 | Area 1
Change capture

1 - Sourcing and Delivery

Change capture
Wholesale reloads and unreliable change signals limit incremental processing.
G04 | Area 2
Data model and consumer contract

2 - Architecture and Processing

Data model and consumer contract
Mosaic 4.0 data conformed to legacy 3.9, discarding newer source detail.
G05 | Area 2
Processing separation

2 - Architecture and Processing

Processing separation
Landing, conformance and transformation are intertwined and cannot recover independently.
G06 | Area 2
Technology fit

2 - Architecture and Processing

Technology fit
Legacy tools carried forward without reassessing Snowflake-native fit.
G07 | Area 3
Operational controls

3 - Governance and Trust

Operational controls
Limited boundary controls; issues are often found first by consumers.
G08 | Area 3
Data quality

3 - Governance and Trust

Data quality
Quality rules and thresholds vary; no common publication gate.
G09 | Area 3
Data freshness

3 - Governance and Trust

Data freshness
Business date and freshness not published; consumers cannot confirm currency.
G10 | Area 3
Metadata and lineage

3 - Governance and Trust

Metadata and lineage
No enterprise metadata backbone or dependable lineage and usage visibility.
G11 | Area 3
Security and entitlements

3 - Governance and Trust

Security and entitlements
Access logic repeated in views; sensitive data inconsistently classified.
G12 | Area 4
Interface standards

4 - Consumption

Interface standards
Inconsistent distribution patterns and no preferred interface standard.
G13 | Area 4
Downstream copies

4 - Consumption

Downstream copies
Data copied into agency/desktop tools without validated need.
G14 | Area 4
Consumer visibility

4 - Consumption

Consumer visibility
CIW lacks consistent visibility into downstream users and dependencies.
G15 | Area 5
Operating model

5 - Operations and Continuity

Operating model
Accountability across organizations; decision rights and escalation not defined.
G16 | Area 5
Continuity and recovery

5 - Operations and Continuity

Continuity and recovery
Recovery is person-dependent; no tested continuity model for critical data.
G17 | Area 5
DataOps automation

5 - Operations and Continuity

DataOps automation
Uneven automation; monolithic procedures limit restart points.
G18 | Area 5
Release management

5 - Operations and Continuity

Release management
Promotion, release evidence and rollback are manual and inconsistent.
G19 | Area 5
Operational knowledge

5 - Operations and Continuity

Operational knowledge
Incomplete runbooks and inconsistent escalation; reliance on individuals.

Gap-to-Workstream Traceability The following crosswalk uses gap IDs G01-G19 defined in the header gap register, identifies the responding workstreams, and distinguishes near-term implementation from partial or future-state coverage.

GAP AREA / SOURCE
SPECIFIC GAP / OWNER WORKSTREAM
RFQ RESPONSE
SCOPE COVERAGE
Area 1 - Sourcing & delivery
Source delivery path

WS 2, 3

Direct Mosaic share and MMIS sharing pilot; source/provider decisions gate go-live.
Near-term scoped

Source footprint

WS 2, 5

Inventory use, map dependencies, narrow Mosaic intake; defer other feed retirement pending validation.
Near-term / partial

Change capture

WS 2, 3, 4

Assess source change signals and implement deltas when supported; reconcile incremental processing.
Partial / dependent
Area 2 - Architecture & processing
Data model and consumer contract

WS 5, 7

Inventory views and draft agency certified-view contract; native 4.0 / semantic layer not built in base RFQ.
Planning only

Processing separation

WS 4, 6, 7

Consolidate Mosaic staging, create patterns and future CIW-core plan.
Partial / future

Technology fit

WS 6, 7

Assess Snowflake native capabilities and migration trade-offs; no full tool retirement.
Assessment only

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .