Opioid Settlement Reporting Platform

The Vendor is required to provide opioid settlement reporting platform for include:
1. Digital accessibility
•    Specifically agrees that all web pages, forms, documents, and services provided under this engagement shall conform to the state’s assistive technology standard, align with the state’s information security framework, and meet WCAG 2.1 level AA accessibility. 
•    Any deviation from these requirements must be approved in writing by IOT in advance
2. Artificial intelligence (AI)
•    Adopted an enterprise policy governing the use of AI. 
•    Any proposed solution or project activities must support the state’s AI policy and follow the AI readiness assessment process administered by the office of the chief data officer in coordination with mph. 
•    If AI capabilities are used or planned, the contractor must disclose such use, provide controls to enable and disable AI features, and document impacts when AI is disabled.
3. Independent verification and validation (IV&V)
•    If the state decides to add IV&V services, the contractor shall copy department IV&V team members on all project communications and grant access to all documents and deliverables throughout the term. 
•    For contracts entered into, renewed, or amended after June 30, 2026, IV&V shall serve as an approving authority for deliverables; no payment shall be issued unless and until IV&V approval is provided.
4. Equipment requirements
•    If equipment is needed to access the state’s network, the contractor must use state-issued machines meeting all security requirements and shall reimburse the state for equipment and access-related costs, per the fy26 IOT services catalog (e.g., seat and maintenance charge, security support fee, user account access fee). 
•    Rates are subject to annual adjustment on July 1 each fiscal year.
5. Solution configurability and customization preference
•    The state prefers requirements to be met in the following priority: out-of-the-box; configuration; customization only as a last resort. 
•    Must document configuration-first analysis before proposing custom code and obtain steering committee approval for any customization, including impact analysis, test and rollback plans, and source code and license terms for custom components.
6. Post go-live support and SLAs
•    Provide post go-live “hyper-care” support with defined duration and SLAs for incident response, uptime, maintenance windows, and escalation tiers; furnish historical uptime for last 12–24 months for the proposed platform; and describe the process to halt a release if testing reveals a critical issue.