00 RFP 2027-1600-0043 - SUPRT - 8-18-26.pdf

STATE OF ALASKA

REQUEST FOR PROPOSALS

SUBSTANCE ABUSE AND MENTAL HEALTH SERVICES

ADMINISTRATION (SAMHSA) UNIFIED PERFORMANCE

REPORTING TOOL (SUPRT)

RFP 2027-1600-0043

ISSUED JULY 21, 2026

The Department of Health (DOH), Division of Behavioral Health (DBH), is soliciting proposals for a secure Software as a Service (SaaS) solution to support the statewide collection, management, quality review, and reporting of client-level Substance Abuse and Mental Health Services Administration (SAMHSA) Unified Performance Reporting Tool (SUPRT) data.

ISSUED BY:

DEPARTMENT OF HEALTH

DIVISION OF BEHAVIORAL HEALTH

PRIMARY CONTACT:

ANNALISA HAYNIE

PROCUREMENT OFFICER

ANNALISA.HAYNIE@ALASKA.GOV

OFFERORS ARE NOT REQUIRED TO RETURN THIS FORM.

IMPORTANT NOTICE: IF YOU RECEIVED THIS SOLICITATION FROM THE STATE OF ALASKA’S “ONLINE PUBLIC NOTICE” WEB SITE, YOU MUST REGISTER WITH THE PROCUREMENT OFFICER LISTED IN THIS DOCUMENT TO RECEIVE

NOTIFICATION OF SUBSEQUENT AMENDMENTS. FAILURE TO CONTACT THE PROCUREMENT OFFICER MAY RESULT

IN THE REJECTION OF YOUR OFFER.

Rev. 02/20 mailto:annalisa.haynie@alaska.gov

STATE OF ALASKA – REQUEST FOR PROPOSALS SAMHSA UNIFIED PERFORMANCE REPORTING TOOL

RFP 2027-1600-0043

Table of Contents

SECTION 1. INTRODUCTION & INSTRUCTIONS

SEC. 1.01 PURPOSE OF THE RFP

SEC. 1.02 BUDGET

SEC. 1.03 DEADLINE FOR RECEIPT OF PROPOSALS

SEC. 1.04 MANDATORY REQUIREMENTS

SEC. 1.05 REQUIRED REVIEW

SEC. 1.06 QUESTIONS PRIOR TO DEADLINE FOR RECEIPT OF PROPOSALS

SEC. 1.07 RETURN INSTRUCTIONS

SEC. 1.08 ASSISTANCE TO OFFERORS WITH DISABILITY

SEC. 1.09 AMENDMENTS TO PROPOSALS

SEC. 1.10 AMENDMENTS TO THE RFP

SEC. 1.11 RFP SCHEDULE

SEC. 1.12 ALTERNATE PROPOSALS

SEC. 1.13 NEWS RELEASES

SECTION 2. BACKGROUND INFORMATION

SEC. 2.01 BACKGROUND INFORMATION

SECTION 3. SCOPE OF WORK & CONTRACT INFORMATION

SEC. 3.01 GOALS AND OBJECTIVES

SEC. 3.02 SCOPE OF WORK

SEC. 3.03 DELIVERABLES

SEC. 3.04 SPECIFIC DELIVERABLES TO BE PROVIDED BY THE CONTRACTOR TO THE STATE

SEC. 3.05 HIPAA SECURITY ASSESSMENT REQUIREMENTS

SEC. 3.06 INTENT TO PROPOSE AND NON-DISCLOSURE AGREEEMENT (NDA)

SEC. 3.07 INFORMATION TECHNOLOGY (IT) RELATED CONTRACTUAL REQUIREMENTS

SEC. 3.08 CONTRACT TERM AND WORK SCHEDULE

SEC. 3.09 CONTRACT TYPE

SEC. 3.10 PAYMENT PROCEDURES

SEC. 3.11 CONTRACT PAYMENT

SEC. 3.12 ELECTRONIC PAYMENTS

SEC. 3.13 LOCATION OF WORK

SEC. 3.14 SUBCONTRACTORS

SEC. 3.15 JOINT VENTURES

SEC. 3.16 RIGHT TO INSPECT PLACE OF BUSINESS

SEC. 3.17 CONTRACT PERSONNEL

SEC. 3.18 INSPECTION & MODIFICATION - REIMBURSEMENT FOR UNACCEPTABLE DELIVERABLES

SEC. 3.19 CONTRACT CHANGES - UNANTICIPATED AMENDMENTS

SEC. 3.20 NONDISCLOSURE AND CONFIDENTIALITY

SEC. 3.21 INDEMNIFICATION

SEC. 3.22 INSURANCE REQUIREMENTS

SEC. 3.23 TERMINATION FOR DEFAULT

SECTION 4. PROPOSAL FORMAT AND CONTENT

SEC. 4.01 RFP SUBMITTAL FORMS

SEC. 4.02 SPECIAL FORMATTING REQUIREMENTS

SEC. 4.03 OFFEROR INFORMATION AND CERTIFICATIONS (SUBMITTAL FORM A)

SEC. 4.04 EXPERIENCE AND QUALIFICATIONS (SUBMITTAL FORM B)

SEC. 4.05 UNDERSTANDING OF THE PROJECT (SUBMITTAL FORM C)

SEC. 4.06 METHODOLOGY USED FOR THE PROJECT (SUBMITTAL FORM D)

SEC. 4.07 MANAGEMENT PLAN FOR THE PROJECT (SUBMITTAL FORM E)

SEC. 4.08 MANDATORY REQUIREMENTS (SUBMITTAL FORM F)

SEC. 4.09 DOH IT CONTRACTUAL REQUIREMENTS (SUBMITTAL FORM G)

SEC. 4.10 COST PROPOSAL (SUBMITTAL FORM H)

SECTION 5. EVALUATION CRITERIA AND CONTRACTOR SELECTION

SEC. 5.01 SUMMARY OF EVALUATION PROCESS

SEC. 5.02 EVALUATION CRITERIA

SEC. 5.03 SCORING METHOD AND CALCULATION

SEC. 5.04 EXPERIENCE AND QUALIFICATIONS

SEC. 5.05 UNDERSTANDING OF THE PROJECT

SEC. 5.06 METHODOLOGY USED FOR THE PROJECT

SEC. 5.07 MANAGEMENT PLAN FOR THE PROJECT

SEC. 5.08 CONTRACT COST (COST PROPOSAL)

SEC. 5.09 APPLICATION OF PREFERENCES

SEC. 5.10 ALASKA BIDDER PREFERENCE

SEC. 5.11 ALASKA VETERAN PREFERENCE

SEC. 5.12 ALASKA MILITARY SKILLS PROGRAM PREFERENCE

SEC. 5.13 ALASKA OFFEROR PREFERENCE

SEC. 5.14 COST REASONABLENESS

SEC. 5.16 CONTRACT NEGOTIATIONS

SEC. 5.17 OFFEROR NOTIFICATION OF SELECTION

SECTION 6. GENERAL PROCESS AND LEGAL INFORMATION

SEC. 6.01 ALASKA BUSINESS LICENSE AND OTHER REQUIRED LICENSES

SEC. 6.02 STANDARD CONTRACT PROVISIONS

SEC. 6.03 BUSINESS ASSOCIATE AGREEMENT (BAA)

SEC. 6.04 QUALIFIED OFFERORS

SEC. 6.05 PROPOSAL AS PART OF THE CONTRACT

SEC. 6.06 ADDITIONAL TERMS AND CONDITIONS

SEC. 6.07 HUMAN TRAFFICKING

SEC. 6.08 RIGHT OF REJECTION

SEC. 6.09 STATE NOT RESPONSIBLE FOR PREPARATION COSTS

SEC. 6.10 DISCLOSURE OF PROPOSAL CONTENTS

SEC. 6.11 ASSIGNMENT

SEC. 6.12 SEVERABILITY

SEC. 6.13 SUPPLEMENTAL TERMS AND CONDITIONS

SEC. 6.14 SOLICITATION ADVERTISING

SEC. 6.15 SITE INSPECTION

SEC. 6.16 CLARIFICATION OF OFFERS

SEC. 6.17 DISCUSSIONS WITH OFFERORS

SEC. 6.18 FEDERALLY IMPOSED TARIFFS

SEC. 6.19 PROTEST

SECTION 7. ATTACHMENTS

SEC. 7.01 ATTACHED FILES

SECTION 1. INTRODUCTION & INSTRUCTIONS

SEC. 1.01 PURPOSE OF THE RFP

The Department of Health (DOH), Division of Behavioral Health (DBH), is soliciting proposals for a secure Software as a Service (SaaS) solution to support the statewide collection, management, quality review, and reporting of client-level Substance Abuse and Mental Health Services Administration (SAMHSA) Unified Performance Reporting Tool (SUPRT) data. The solution will enable subrecipient grantees to collect required SUPRT information and facilitate submission of those data to SAMHSA's Performance Accountability and Reporting System (SPARS) using currently available batch upload functionality.

The proposed SUPRT SaaS solution will provide secure, role-based access that allows authorized provider organizations to collect, manage, and maintain only the client records associated with their organization.

The system will support all required SUPRT assessment events, including baseline assessment, six-month reassessment, annual follow-up (when applicable), and close-out assessment.

The State recognizes that SPARS functionality may continue to evolve during the contract period. Offerors may propose in their narrative, a phased implementation approach that accommodates current SPARS capabilities while positioning the solution for future automation as additional functionality becomes available.

The contractor will provide implementation, hosting, ongoing maintenance, technical support, system enhancements, and operational reporting necessary to maintain a reliable SUPRT SaaS solution throughout the contract term. The solution will remain aligned with evolving SAMHSA reporting requirements and any State-approved modifications implemented during the life of the contract.

Subrecipient grantees will have the option of entering SUPRT information directly into the hosted solution or submitting data through contractor-developed import specifications approved by the Department. Where a subrecipient administers multiple SAMHSA-funded programs requiring SUPRT reporting, the solution will support association of each client record with the appropriate SAMHSA Grant Identifier to ensure accurate reporting to SPARS.

SEC. 1.02 BUDGET

The Department of Health, Division of Behavioral Health, estimates a total budget of up to $1,250,000.00 for the completion of all five (5) contract years, including renewal options. Cost proposals that exceed this amount may be determined as non-responsive.

Approval, continuation, renewal, or extension of any contract awarded under this RFP is contingent upon the availability of legislative appropriations and federal funding.

SEC. 1.03 DEADLINE FOR RECEIPT OF PROPOSALS

Proposals must be received no later than 5:00PM prevailing Alaska Time on August 28, 2026. Late proposals or amendments will be disqualified and not opened or accepted for evaluation.

SEC. 1.04 MANDATORY REQUIREMENTS

To be considered responsive for this RFP, an offeror must meet the mandatory experience requirements that are provided in Submittal Form F – Mandatory Requirements. Failure to meet these requirements will result in immediate disqualification.

SEC. 1.05 REQUIRED REVIEW

Offerors should carefully review this solicitation for defects and questionable or objectionable material. Comments concerning defects and questionable or objectionable material should be made in writing and received by the procurement officer at least ten days before the deadline for receipt of proposals. This will allow time for the issuance of any necessary amendments. It will also help prevent the opening of a defective proposal and exposure of offeror's proposals upon which award could not be made.

SEC. 1.06 QUESTIONS PRIOR TO DEADLINE FOR RECEIPT OF PROPOSALS

All questions must be in writing and directed to the procurement officer at least ten days before the deadline for receipt of proposals. The interested party must confirm telephone conversations in writing.

Two types of questions generally arise. One may be answered by directing the questioner to a specific section of the RFP. These questions may be answered via email. Other questions may be more complex and may require a written amendment to the RFP. The procurement officer will make that decision.

SEC. 1.07 RETURN INSTRUCTIONS

Offerors must submit their proposals via email. The technical proposal and cost proposal must be saved as separate documents and emailed to doh.procurement.proposals@alaska.gov as separate, clearly labeled attachments. The email must contain the RFP number in the subject line.

The maximum size of a single email (including all text and attachments) that can be received by the state is 25mb (megabytes). If the email containing the proposal exceeds this size, the proposal must be sent in multiple emails that are each less than 25 megabytes.

Please note that email transmission is not instantaneous. Similar to sending a hard copy proposal, if you are emailing your proposal, the state recommends sending it with enough lead time to ensure the email is delivered by the deadline for receipt of proposals.

It is the offeror’s responsibility to contact the above email address to confirm that the proposal has been received. The state is not responsible for unreadable, corrupt, or missing attachments.

SEC. 1.08 ASSISTANCE TO OFFERORS WITH DISABILITY

Offerors with a disability may receive accommodation regarding the means of communicating this RFP or participating in the procurement process. For more information, contact the procurement officer no later than ten days prior to the deadline for receipt of proposals.

SEC. 1.09 AMENDMENTS TO PROPOSALS

Amendments to or withdrawals of proposals will only be allowed if acceptable requests are received prior to the deadline that is set for receipt of proposals. No amendments or withdrawals will be accepted after the deadline unless they are in response to the state's request in accordance with 2 AAC 12.290.

mailto:doh.procurement.proposals@alaska.gov

SEC. 1.10 AMENDMENTS TO THE RFP

If an amendment is issued before the deadline for receipt of proposals, it will be provided to all who were notified of the RFP and to those who have registered with the procurement officer after receiving the RFP from the State of Alaska Online Public Notice website.

After receiving proposals, if there is a need for any substantial clarification or material change in the RFP, an amendment will be issued. The amendment will incorporate the clarification or change, and a new date and time established for new or amended proposals. Evaluations may be adjusted as a result of receiving new or amended proposals.

SEC. 1.11 RFP SCHEDULE

The RFP schedule set out herein represents the state’s best estimate of the schedule that will be followed. If a component of this schedule, such as the deadline for receipt of proposals, is delayed, the rest of the schedule may be shifted accordingly. All times are Alaska Time.

ACTIVITY TIME DATE

Issue Date / RFP Released July 21, 2026 Deadline to Submit Questions August 18, 2026 Deadline for Receipt of Proposals / Proposal Due Date 5:00PM August 28, 2026 Proposal Evaluations Complete September 11, 2026 Notice of Intent to Award September 18, 2026 Contract Issued for Review and Signature September 25, 2026 Contract Start Date October 2, 2026

This RFP does not, by itself, obligate the state. The state's obligation will commence when the contract is approved by the Commissioner of the Department of Health, or the Commissioner's designee. Upon written notice to the contractor, the state may set a different starting date for the contract. The state will not be responsible for any work done by the contractor, even work done in good faith, if it occurs prior to the contract start date set by the state.

SEC. 1.12 ALTERNATE PROPOSALS

Offerors may only submit one proposal for evaluation. In accordance with 2 AAC 12.830 alternate proposals (proposals that offer something different than what is asked for) will be rejected.

SEC. 1.13 NEWS RELEASES

News releases related to this RFP will not be made without prior approval of the project director.

SECTION 2. BACKGROUND INFORMATION

SEC. 2.01 BACKGROUND INFORMATION

The Department of Health (DOH), Division of Behavioral Health (DBH), administers multiple Substance Abuse and Mental Health Services Administration (SAMHSA) grant programs that require collection and reporting of client-level data through SAMHSA's Unified Performance Reporting Tool (SUPRT).

Currently, portions of the SUPRT data collection and reporting process require significant manual effort by DBH staff and subrecipient grantees. Following contract award and implementation, the contractor will provide and maintain a secure SUPRT SaaS Solution that supports statewide data collection, data management, operational reporting, and submission of required SUPRT data to SAMHSA's Performance Accountability and Reporting System (SPARS) using available batch upload functionality.

The contractor's solution will provide secure access for authorized subrecipient organizations to collect, manage, validate, and maintain required SUPRT data while supporting DBH oversight and quality review activities. The solution will improve reporting consistency, reduce manual processing, and support timely submission of required federal reporting information.

SUPRT data collection is required at multiple points during participation in applicable SAMHSA-funded programs, including:

1. Baseline Assessment

2. Six-Month Reassessment

3. Annual Follow-Up (when applicable)

4. Close-Out Assessment

The solution will support collection and reporting of client-level information required by SAMHSA, including, but not limited to:

• Demographic characteristics

• Substance use

• Diagnoses

• Services received

• Medications for Opioid Use Disorder (MOUD)

• Length of stay in treatment

• Employment status

• Criminal justice involvement

• Housing status

• Basic health information

DBH recognizes that federal SUPRT reporting requirements may change during the contract period. The contractor will maintain the solution as necessary to support approved changes to SAMHSA reporting requirements throughout the life of the contract.

SECTION 3. SCOPE OF WORK & CONTRACT INFORMATION

SEC. 3.01 GOALS AND OBJECTIVES

The goals and objectives of this contract are to provide, implement, operate, and maintain a secure SUPRT SaaS solution that supports statewide collection, management, quality review, reporting, and submission of client-level SAMHSA Unified Performance Reporting Tool (SUPRT) data.

The solution will:

• Provide a secure provider portal supporting SUPRT data collection and management.

• Support batch upload of SUPRT data to SAMHSA's Performance Accountability and Reporting System (SPARS).

• Provide operational and program evaluation reporting based on SUPRT-collected data.

Support baseline, six-month follow-up, annual follow-up (when applicable), and close out assessments.

• Include ongoing maintenance, technical support, system enhancements, and operational reporting throughout the contract term.

DBH recognizes that SAMHSA reporting requirements and SPARS functionality may evolve during the contract period. The contractor will maintain the solution as necessary to support approved federal reporting changes throughout the life of the contract.

SEC. 3.02 SCOPE OF WORK

The Department of Health (DOH), Division of Behavioral Health (DBH), seeks a contractor to provide, implement, host, and maintain a secure Software as a Service (SaaS) SUPRT solution that supports the statewide collection, management, validation, reporting, and submission of client-level Substance Abuse and Mental Health Services Administration (SAMHSA) Unified Performance Reporting Tool (SUPRT) data. The solution will enable subrecipient grantees to collect required SUPRT information and facilitate submission of those data to SAMHSA's Performance Accountability and Reporting System (SPARS) using current batch upload functionality while remaining adaptable to future federal reporting enhancements.

The State recognizes that certain SPARS functionality may continue to evolve during the contract period. Offerors may propose a phased implementation strategy in their proposal narrative that accommodates current SPARS capabilities while preparing for future automated functionality anticipated by SAMHSA.

SUPRT data collection and reporting are required for applicable SAMHSA-funded programs and will support baseline assessment, six-month reassessment, annual follow-up (when applicable), and close-out assessment activities. The SUPRT reporting process replaced the Government Performance and Results Act (GPRA) reporting requirements in October 2025.

The contractor will provide ongoing maintenance and updates to the SUPRT SaaS solution and associated SPARS batch upload functionality as required by DBH and SAMHSA. The solution will also provide feedback reporting for unsuccessful batch uploads, including identification of record-specific errors and systematic issues requiring correction.

SEC. 3.03 DELIVERABLES

The contractor will be required to provide the following deliverables:

Provide online data submission portal with integrated rules to support accurate and complete SUPRT data collection, as defined by DOH and SAMHSA, with batch upload capabilities for SAMHSA’s Performance Accountability and Reporting System (SPARS). The development of this customized portal project site will be based on system specifications. This SUPRT system build out will require maintenance, data management, and development of operational reporting, and technical assistance for providers. The contractor will develop reports that agencies can review to make corrections to existing records that do not pass the batch upload process.

The system will require ongoing maintenance and updates to both the project site and batch upload code, based on DOH’s or SAMSHA’s requirements. The batch upload system will also require feedback reporting of surveys that do not transfer, with error identification of idiosyncratic errors and identification of systematic errors for follow-up resolution.

At a minimum, the SUPRT SaaS solution will provide the following operational reporting and quality assurance capabilities:

• Reports that identify assessments that were started but not completed.

• Reports identifying follow-up assessments due during the upcoming month.

• Reports identifying follow-up assessments that are currently due or past due.

• Discharge or close-out assessment reports, as applicable.

• Confirmation reports that identify SUPRT records were successfully uploaded to SPARS.

• Exception reports that identify SUPRT records that failed the automated batch upload process, including the applicable error message and fields requiring correction.

• Summary reports identifying successfully submitted SUPRT records by grant, report type, and reporting period.

• Up to eight (8) analytical reports, jointly designed by DBH and the contractor, using SUPRT data to support program oversight and evaluation.

SEC. 3.04 SPECIFIC DELIVERABLES TO BE PROVIDED BY THE CONTRACTOR TO THE

STATE

This includes the following:

1. One-Time Security Assessment - Contractor will work in collaboration with Department of Health Security Office to complete a full DOH/Health Insurance and Portability Act (HIPAA) Security Assessment for the proposed software or system solution(s) until Authority To Operate (ATO) is granted. This is a one-time cost. See RFP SEC 3.05 - HIPAA Security Assessment Requirements.

2. Host Online HIPAA-Compliant Solution – The solution will be rules-based data submission platform for DBH subrecipient agency grantee and/or contracted vendor to enter client-level SUPRT data for SAMHSA-funded program participants.

3. Data Management - Manage collected SUPRT data and format for batch upload to SPARS interface to DBH’s grant workspace.

4. Maintenance and Licensing - Perform ongoing maintenance and updates of the platform and batch upload code to align with federally mandated changes, DBH business needs, and any formal revisions issued by SAMHSA to the SUPRT reporting instrument.

5. Report Development - Develop feedback reporting of success and failure of batch upload, with error identification of idiosyncratic errors and identification of systematic errors for follow-up resolution.

6. Compliance Reporting and Quality Review - Develop operational and program evaluation reporting using SUPRT-collected data. Reporting will support DBH quality review and monitoring of SUPRT reporting requirements, including baseline intake, six-month follow-up, annual follow-up, and discharge assessments.

7. Technical Assistance and Provider Support - Develop and maintain a provider technical assistance resource website and documentation that provides access to the SUPRT data collection platform, training resources, technical assistance materials, and other relevant resources approved by DBH.

The desired solution will be operational within three months of contract award, after final system configuration and operational considerations. The activities in support of the deliverables are outlined below.

• Integrated provider portal go-live with SPARS batch upload capability

• Customization and testing of data collection portal and SPARS batch upload solution, as per SPARS-SUPRT and DOH requirements.

Operations and Maintenance

• Ongoing maintenance and updates of the portal project site and batch upload code, based on DOH/provider's needs.

• Data management which includes developing site-specific operational reporting pages and managing Alaska requests for survey modifications.

• Batch upload notification and error resolution for rejected/failed Alaska SUPRT data to SPARS and includes correction of idiosyncratic errors and identification of systematic errors for correction.

Technical Assistance and Training

• Kick-off training for DOH/providers and regular peer learning opportunities delivered through calls, and webinars.

• Email updates/communication to grantees regarding SUPRT submission progress and upcoming six-month follow-ups.

• Management of a monitored helpdesk for site support and/or individualized technical assistance, including 1:1 TA calls.

• Development of grantee and client-facing resources and documentation for SUPTR.

Project Management

• Project management support through project site development, testing, and go-live to facilitate calls, agenda development, and deliverable tracking.

TABLE 1. TIMELINE AND ACTIVITIES – MONTHS 1 AND 2

Contractor has 45 days from receipt of the email requesting the start of the Security Assessment and the submission of all the initial paperwork requested by the Department Security Office.

Customization and testing of data collection portal and SPARS batch upload solution, as per SPARS-SUPTR and DOH requirements.

Production launch of customized data collection portal.

Production launch of batch upload interface for DOH SPARS submission.

Data management (includes developing site-specific operational reporting pages and implementing survey modifications only when formally required by SAMHSA revisions to the SUPRT instrument).

Batch upload notification and error resolution for rejected/failed Alaska SUPTR data to SPARS (includes correction of idiosyncratic errors and identification of systematic errors for correction).

Develop training materials for Alaska DOH staff.

Develop Alaska SUPRT grantee/program resource website.

MONTH 3 AND ONGOING TIMELINE AND ACTIVITIES

Ongoing maintenance and updates for the portal project site and batch upload code, based on DOH/Provider’s needs.

Maintains portal functionality supporting management of SUPRT survey deletion and return codes associated with client records that fail during the batch upload process.

Conducts weekly batch upload and error correction or identification.

Email updates/communications to grantees regarding SUPRT submission progress and upcoming six-month follow-ups.

Provides technical assistance, as needed.

Maintains Alaska SUPRT grantee/program resource website.

Provides individualized TA for Alaska SUPRT grantees, as needed.

Provides ongoing project management support.

Conduct training webinar(s) for Alaska SUPRT grantees.

Contractor will be required to complete a security assessment (see Section 3.05 below).

SEC. 3.05 HIPAA SECURITY ASSESSMENT REQUIREMENTS

Once the contract is executed and prior to beginning any other work under the contract, the contractor will work with the Department of Health (DOH) Security Office to complete a full security assessment of the proposed software or system solution(s). This may include, but not be limited to:

• Articulating the components of the system which DOH staff are expected to configure and administer and, likewise, which components of the system the contractor will configure and administer.

• Information System/Data Flow Diagram outlining all major components of the system (system type and technologies employed) and their interconnections (protocols and payloads).

• Interconnection Risk Assessment Worksheet (IRAW) for each outbound or inbound interconnection outlined in the Information System/Data Flow Diagram and any ancillary Application Programming Interface (API) or data transfers.

• A code scanning attestation which confirms the offeror performs MITRE conformant code scanning for Common Weakness Enumeration (CWE) against each deployable version of the code base and remediates CWE flaws of medium, or higher, technical impact.

• A server vulnerability scanning attestation confirming that the offeror performs regular vulnerability scanning against all in-scope servers and remediates identified vulnerabilities in a timely manner.

• Completion of the DOH NIST CSF Assessment Questions (see RFP Section SEC. 3.06).

Follow up clarification questions from the DOH’s Security Assessor may be required. The software or system solution(s) must receive an Authority to Operate (ATO) from the Security Assessor prior to being deployed. If the ATO is not issued, the State is not responsible for any additional costs and reserves the right to terminate the contract immediately.

This security assessment may also be performed every three years during the contract. All contractor costs for the security assessment must be included in the offeror’s cost proposal. Those costs will be paid only upon completion of the security assessment and issuance of the ATO from the Security Assessor.

SEC. 3.06 INTENT TO PROPOSE AND NON-DISCLOSURE AGREEEMENT (NDA)

Offerors may request access to the NIST CSF Assessment Questions List to better understand the scope and effort associated with the required security assessment.

Execution of the Intent to Propose and Non-Disclosure Agreement (NDA) is optional and only required for offerors wishing to review the NIST CSF Assessment Questions List before proposal submissions. It is intended to further determine the level of effort and cost for the security assessment. To obtain the NIST CSF Assessment Questions List, the offeror must complete and submit an intent to propose and non-disclosure agreement, provided as an attachment to this RFP. The signed agreement must be emailed to the procurement officer as an attachment and the offeror must also provide the phone number and email address of the person who is to receive the file. The file will then be provided by the procurement officer to the offeror.

The procurement officer will not provide the file until receipt of the completed and signed intent to propose and non-disclosure agreement. The state reserves the right to clarify and verify any offeror’s ability to perform the services required under this solicitation prior to granting access to the file. The state is not responsible for an offeror’s failure to obtain the NIST CSF Assessment Questions List; the total costs identified for the security assessment on the offeror’s cost proposal will be the total costs paid by the state. No additional charges will be allowed.

SEC. 3.07 INFORMATION TECHNOLOGY (IT) RELATED CONTRACTUAL REQUIREMENTS

Other specific DOH IT-related contractual requirements are provided as Attachment 02 – Submittal Form G. The offeror must complete this form in accordance with the provided instructions; space is provided to provide both choose a response (see the drop-down list) and provide further explanation.

Note that in some cases, certain initial elements of the HIPAA Security Assessment indicated in Section 3.05 may be completed during the negotiation phase based on the offeror’s response to these contractual requirements.

SEC. 3.08 CONTRACT TERM AND WORK SCHEDULE

The total length of the contract will be for approximately five years. The initial term will be a one-year term, followed by four (4) one-year optional renewals. Each renewal will be exercised at the sole discretion of the State.

Any extension of the contract beyond the exercised renewal options will be made upon mutual agreement between the State and the contractor and effected by a contract amendment processed by the procurement officer and signed by both parties. All other terms and conditions of the contract, including those previously amended, will remain in full force and effect. Unless otherwise agreed to by both parties, the procurement officer will provide written notice to the contractor with the intent to cancel an extension at least 30 days before the desired date of cancellation.

SEC. 3.09 CONTRACT TYPE

This contract is a firm fixed price contract.

SEC. 3.10 PAYMENT PROCEDURES

The state will make payments based on a negotiated payment schedule. Each billing must consist of an invoice and progress report. No payment will be made until the progress report, and invoice has been approved by the project director.

SEC. 3.11 CONTRACT PAYMENT

No payment will be made until the contract is approved by the Commissioner of the Department of Health or the Commissioner's designee. The state is not responsible for and will not pay local, state, or federal taxes. All costs associated with the contract must be stated in U.S. currency.

For agreements over $500,000, under no conditions will the state be liable for the payment of any interest charges associated with the cost of the contract. Payment for agreements under $500,000 for the undisputed purchase of goods or services provided to a state agency will be made within 30 days of the receipt of a proper billing or the delivery of the goods or services to the location(s) specified in the agreement, whichever is later. Late payment is subject to 1.5% interest per month on the unpaid balance. Interest will not be paid if there is a dispute or if there is an agreement that establishes a lower interest rate or precludes the charging of interest.

SEC. 3.12 ELECTRONIC PAYMENTS

The State of Alaska prefers vendors to receive payment via Electronic Funds Transfer (EFT). The contractor may review information concerning the EFT process and access the Electronic Payment Agreement Form for Vendors at the following link: https://doa.alaska.gov/dof/vendor.html.

Any single contract payment of $1 million or higher must be accepted by the contractor via Electronic Funds Transfer (EFT).

SEC. 3.13 LOCATION OF WORK

The location(s) the work is to be performed, completed and managed is at the awarded contractors place of business.

The state will not provide workspace for the contractor. The contractor must provide its own workspace.

By signature on their proposal, the offeror certifies that all services provided under this contract by the contractor and all subcontractors will be performed in the United States.

If the offeror cannot certify that all work will be performed in the United States, the offeror must submit a request, set out in a separate document in their proposal, that provides a detailed description of the portion of work that will be performed outside the United States, where, by whom, and the reason that is necessary.

The offeror must also provide this information when completing the DOH IT Contractual Requirements Submittal Form G.

Failure to comply with these requirements may cause the state to reject the proposal as non-responsive or cancel the contract.

SEC. 3.14 SUBCONTRACTORS

Subcontractors will be allowed.

SEC. 3.15 JOINT VENTURES

Joint ventures will not be allowed.

SEC. 3.16 RIGHT TO INSPECT PLACE OF BUSINESS

At reasonable times, the state may inspect those areas of the contractor's place of business that are related to the performance of a contract. If the state makes such an inspection, the contractor must provide reasonable assistance.

SEC. 3.17 CONTRACT PERSONNEL

Any change of project team members or subcontractors named in the proposal must be approved, in advance and in writing, by the project director or procurement officer. Changes that are not approved by the state may be grounds for the state to terminate the contract.

https://doa.alaska.gov/dof/vendor.html

SEC. 3.18 INSPECTION & MODIFICATION - REIMBURSEMENT FOR UNACCEPTABLE

DELIVERABLES

The contractor is responsible for the completion of all work set out in the contract. All work is subject to inspection, evaluation, and approval by the project director. The state may employ all reasonable means to ensure that the work is progressing and being performed in compliance with the contract. The project director or procurement officer may instruct the contractor to make corrections or modifications if needed to accomplish the contract’s intent. The contractor will not unreasonably withhold such changes.

Substantial failure of the contractor to perform the contract may cause the state to terminate the contract. In this event, the state may require the contractor to reimburse monies paid (based on the identified portion of unacceptable work received) and may seek associated damages.

SEC. 3.19 CONTRACT CHANGES - UNANTICIPATED AMENDMENTS

During the course of this contract, the contractor may be required to perform additional work. That work will be within the general scope of the initial contract. When additional work is required, the project director will provide the contractor with a written description of the additional work and request the contractor to submit a firm time schedule for accomplishing the additional work and a firm price for the additional work. Cost and pricing data must be provided to justify the cost of such amendments per AS 36.30.400.

The contractor will not commence additional work until the procurement officer has secured any required state approvals necessary for the amendment and issued a written contract amendment, approved by the Commissioner of the Department of Health or the Commissioner's designee.

SEC. 3.20 NONDISCLOSURE AND CONFIDENTIALITY

Contractor agrees that all confidential information will be used only for purposes of providing the deliverables and performing the services specified herein and will not disseminate or allow dissemination of confidential information except as provided for in this section. The contractor will hold as confidential and will use reasonable care (including both facility physical security and electronic security) to prevent unauthorized access by, storage, disclosure, publication, dissemination to and/or use by third parties of, the confidential information. “Reasonable care” means compliance by the contractor with all applicable federal and state law, including the Social Security Act and HIPAA.

The contractor must promptly notify the state in writing if it becomes aware of any storage, disclosure, loss, unauthorized access to or use of the confidential information.

Confidential information, as used herein, means any data, files, software, information or materials (whether prepared by the state or its agents or advisors) in oral, electronic, tangible or intangible form and however stored, compiled or memorialized that is classified confidential as defined by State of Alaska classification and categorization guidelines provided by the state to the contractor or a contractor agent or otherwise made available to the contractor or a contractor agent in connection with this contract, or acquired, obtained or learned by the contractor or a contractor agent in the performance of this contract. Examples of confidential information include, but are not limited to:

technology infrastructure, architecture, financial data, trade secrets, equipment specifications, user lists, passwords, research data, and technology data (infrastructure, architecture, operating systems, security tools, IP addresses, etc.).

Additional information that the contractor will hold as confidential during the performance of services under this contract include:

• DEPARTMENT’S SECURITY ASSESSMENT PROCESS AND DOCUMENTS.

• SUPRT DATA FROM GRANTEES IS CONFIDENTIAL AND THE SUPRT PORTAL MUST BE HIPAA-COMPLIANT AND ALIGN WITH ANY ADDITIONAL PROTECTIONS DESCRIBED UNDER 42 CFR PART 2 THAT GOVERN SUBSTANCE USE DISORDER

TREATEMNT RECORDS.

If confidential information is requested to be disclosed by the contractor pursuant to a request received by a third party and such disclosure of the confidential information is required under applicable state or federal law, regulation, governmental or regulatory authority, the contractor may disclose the confidential information after providing the state with written notice of the requested disclosure (to the extent such notice to the state is permitted by applicable law) and giving the state opportunity to review the request. If the contractor receives no objection from the state, it may release confidential information within 30 days. Notice of the requested disclosure of confidential information by the contractor must be provided to the state within a reasonable time after the contractor’s receipt of notice of the requested disclosure and, upon request of the state, will seek to obtain legal protection from the release of the confidential information.

The following information will not be considered confidential information: information previously known to be public information when received from the other party; information freely available to the general public; information which now is or hereafter becomes publicly known by other than a breach of confidentiality hereof; or information which is disclosed by a party pursuant to subpoena or other legal process and which as a result becomes lawfully obtainable by the general public.

SEC. 3.21 INDEMNIFICATION

The contractor shall indemnify, hold harmless, and defend the contracting agency from and against any third-party claim of, or liability for error, omission or negligent act of the contractor under this agreement. The contractor shall not be required to indemnify the contracting agency for a claim of, or liability for, the independent negligence of the contracting agency. If there is a claim of, or liability for, the joint negligent error or omission of the contractor and the independent negligence of the contracting agency, the indemnification and hold harmless obligation shall be apportioned on a comparative fault basis. “Contractor” and “contracting agency”, as used within this and the following article, include the employees, agents and other contractors who are directly responsible, respectively, to each. The term “independent negligence” is negligence other than in the contracting agency’s selection, administration, monitoring, or controlling of the contractor and in approving or accepting the contractor’s work.

SEC. 3.22 INSURANCE REQUIREMENTS

Without limiting contractor's indemnification, it is agreed that contractor shall purchase at its own expense and maintain in force at all times during the performance of services under this agreement the following policies of insurance. Where specific limits are shown, it is understood that they shall be the minimum acceptable limits. If the contractor's policy contains higher limits, the state shall be entitled to coverage to the extent of such higher limits.

Certificates of Insurance must be furnished to the procurement officer prior to beginning work and must provide for a notice of cancellation, non-renewal, or material change of conditions in accordance with policy provisions. Failure to furnish satisfactory evidence of insurance or lapse of the policy is a material breach of this contract and shall be grounds for termination of the contractor's services. All insurance policies shall comply with and be issued by insurers licensed to transact the business of insurance under AS 21.

Workers' Compensation Insurance: The contractor shall provide and maintain, for all employees engaged in work under this contract, coverage as required by AS 23.30.045, and; where applicable, any other statutory obligations including but not limited to Federal U.S.L. & H. and Jones Act requirements. The policy must waive subrogation against the State.

Commercial General Liability Insurance: covering all business premises and operations used by the Contractor in the performance of services under this agreement with minimum coverage limits of $300,000 combined single limit per claim.

Commercial Automobile Liability Insurance: covering all vehicles used by the contractor in the performance of services under this agreement with minimum coverage limits of $300,000 combined single limit per claim.

SEC. 3.23 TERMINATION FOR DEFAULT

If the project director or procurement officer determines that the contractor has refused to perform the work or has failed to perform the work with such diligence as to ensure its timely and accurate completion, the state may, by providing written notice to the contractor, terminate the contractor's right to proceed with part or all of the remaining work.

The procurement officer may also, by written notice, terminate the contract under Administrative Order 352 if the contractor supports or participates in a boycott of the State of Israel.

This clause does not restrict the state's termination rights under the contract provisions of Appendix A or Appendix E, attached in SECTION 7. ATTACHMENTS.

SECTION 4. PROPOSAL FORMAT AND CONTENT

SEC. 4.01 RFP SUBMITTAL FORMS

This RFP contains Submittal Forms, which must be completed by the offeror and submitted as their proposal. An electronic copy of the forms is posted along with this RFP. Offerors shall not re-create these forms, create their own forms, or edit the format structure of the forms unless permitted to do so.

Unless otherwise specified in this RFP, the Submittal Forms shall be the offeror’s entire proposal. Do not include any links or marketing information in the proposal or it may be removed by the procurement officer prior to the proposals being sent to the proposal evaluation committee (PEC).

Any proposal that does not follow these requirements may be deemed non-responsive and rejected.

SEC. 4.02 SPECIAL FORMATTING REQUIREMENTS

The offeror must ensure that their proposal meets all special formatting requirements identified in this section.

Documents and Text: All attachment documents must be written in the English language, be single sided, and be single spaced with a minimum font size of 10. Pictures or graphics may be used if the offeror feels it is necessary to communicate their information, however, be aware of the below requirements for page limits.

Page Limits: Some Submittal Forms listed below have maximum page limit requirements. Offerors must not exceed the maximum page limits. Note, the page limit applies to the front side of a page only (for example, ‘1 Page’ implies that the offeror can only provide a response on one side of a piece of paper).

Screenshots: Offerors may include screenshots of the proposed solution as supplemental materials in a separate attachment to the applicable submittal forms and these pages will not be counted against the maximum page limits identified below.

Submittal Form Anonymous

Document

Maximum Page Limits

Submittal Form A – Offeror Information and Certifications N/A Submittal Form B – Experience and Qualifications NO 5 Submittal Form C – Understanding of the Project NO 5 Submittal Form D – Methodology Used for the Project NO 5 Submittal Form E – Management Plan for the Project NO 5 Submittal Form F – Mandatory Requirements N/A Submittal Form G – IT Contractual Requirements N/A Submittal Form H – Cost Proposal N/A

Any Submittal Form that is being evaluated and does not follow these instructions may receive a ‘1’ score for the evaluated Submittal Form, or the entire response may be deemed non-responsive and rejected. Failure to submit any of the Submittal Forms will result in the proposal being deemed non-responsive and rejected.

SEC. 4.03 OFFEROR INFORMATION AND CERTIFICATIONS (SUBMITTAL FORM A)

The offeror must complete and submit this Submittal Form. The form must be signed by an individual authorized to bind the offeror to the provisions of the RFP.

By signature on the form, the offeror certifies they comply with the items listed in the Certifications section of the Submittal Form. If the offeror fails to comply with these items, the state reserves the right to disregard the proposal, consider the contractor in default, or terminate the contract.

The Submittal Form also requests the following information:

a) The complete name and address of offeror’s firm along with the offeror’s Tax ID.

b) Information on the person the state should contact regarding the proposal.

c) Names of critical team members/personnel.

d) Addenda acknowledgement.

e) Conflict of interest statement.

f) Alaska preference qualifications.

An offeror's failure to provide this information may cause the proposal to be determined non-responsive and be rejected.

SEC. 4.04 EXPERIENCE AND QUALIFICATIONS (SUBMITTAL FORM B)

1. Offerors must provide detail on their specific experience in providing platform technical assistance and training to users throughout any state in the USA.

2. Offerors must also provide details on the primary project manager’s specific experience in projects of a similar nature along with the directly related experience of the overall project team identified in Submittal Form A.

3. For both above, this can include other specific areas of expertise, including experience in developing and supporting SUPRT administration, technical assistance resources and developing and providing operational reporting for SUPRT activities.

4. Offerors should elaborate on their experience with SAMHSA Unified Performance Reporting Tool (SUPRT), Government Performance and Results Act (GPRA), or similar federal reporting system. The offeror will identify the applicable contract period(s), indicate whether the work is ongoing, and identify the state(s) or organizations served.

5. Finally, offerors must provide a description of the organization of the project team and the individuals responsible and accountable for the completion of each component and deliverable of the RFP.

SPECIAL NOTE: The offeror shall not disclose their costs in this Submittal Form and cannot exceed the page limit (as described in Section 4.02).

SEC. 4.05 UNDERSTANDING OF THE PROJECT (SUBMITTAL FORM C)

1. Offerors must provide details that demonstrate their understanding of the requirements of the project and how to meet the state’s needs.

SPECIAL NOTE: The offeror shall not disclose their costs in this Submittal Form and cannot exceed the page limit (as described in Section 4.02).

SEC. 4.06 METHODOLOGY USED FOR THE PROJECT (SUBMITTAL FORM D)

1. Offerors must provide details that demonstrate the methodology they will employ and how the methodology will serve to accomplish the work and meet the state’s needs.

2. The State recognizes that SPARS functionality may continue to evolve during the contract period. Offerors may propose in their narrative, a phased implementation approach that accommodates current SPARS capabilities while positioning the solution for future automation as additional functionality becomes available.

Offerors must also identify and potential issues, risks, or problems they foresee with this project and how they will address them.

SPECIAL NOTE: The offeror shall not disclose their costs in this Submittal Form and cannot exceed the page limit (as described in Section 4.02).

SEC. 4.07 MANAGEMENT PLAN FOR THE PROJECT (SUBMITTAL FORM E)

Offerors must provide detail that demonstrates the management plan they intend to follow and how the plan will serve to accomplish the work and meet the state's needs.

Offerors must also identify any potential issues, risks, or problems they foresee with this project and how they will address them.

SPECIAL NOTE: The offeror shall not disclose their costs in this Submittal Form and cannot exceed the page limit (as described in Section 4.02).

SEC. 4.08 MANDATORY REQUIREMENTS (SUBMITTAL FORM F)

Offerors must complete all sections of this Submittal Form, including explanations of whether and how they meet each mandatory requirement. Failure to do so may result in rejection of the proposal as non-responsive.

SEC. 4.09 DOH IT CONTRACTUAL REQUIREMENTS (SUBMITTAL FORM G)

Offerors must complete and submit this Submittal Form.

For purposes of this procurement, Requirement IT25 (Master Client Index Integration) may be identified as "Not Applicable" and will not be considered a deficiency.

SEC. 4.10 COST PROPOSAL (SUBMITTAL FORM H)

Offerors must complete and submit this Submittal Form.

Offerors should assume twelve (12) months for each contract year.

Proposed costs must be all-inclusive and include all direct and indirect expenses associated with performance of the contract, including personnel costs, fringe benefits, materials, supplies,…