RFP Document.pdf

REQUEST FOR PROPOSAL

South Dakota Department of Transportation

Intelligent Transportation Systems Program

Active Traffic Management System

RFP Number 26RFP19813

Project Number: ITS000S(1I) PCN: 08RP

PROPOSALS DUE: June 5, 2026, 3:00PM CDT

Primary Contact Information

Contact Name: Dave Huft

Telephone Number: 605-773-3358

Email: dave.huft@state.sd.us

Active Traffic Management System RFP 26RFP19813 ii Published May 6, 2026

The South Dakota Department of Transportation gives public notice of its policy to uphold and assure full compliance with the non-discrimination requirements of Title VI of the Civil Rights Act of 1964 and related Nondiscrimination authorities. Title VI and related Nondiscrimination authorities stipulate that no person in the United States of America shall on the grounds of race, color, national origin, religion, sex, age, disability, income level or Limited English Proficiency be excluded from the participation in, be denied the benefits of, or be otherwise subjected to discrimination under any program or activity receiving Federal financial assistance.

Any person who has questions concerning this policy or wishes to file a discrimination complaint should contact the Department’s Civil Rights Office at 605-773-3540.

Active Traffic Management System RFP 26RFP19813 iii Published May 6, 2026

TABLE OF CONTENTS

1 GENERAL INFORMATION

1.1 SPONSORING AGENCY

1.2 PURPOSE OF REQUEST FOR PROPOSAL

1.2.1 Overview

1.2.2 Detailed Work Definition

1.3 PERIOD OF PERFORMANCE

1.4 PROPOSER ELIGIBILITY

1.5 PROCUREMENT PROCESS

1.5.1 Request for Proposal

1.5.2 Letter of Intent

1.5.3 Proposer Inquiries

1.5.4 Proposal Submission

1.5.5 Proposal Format

1.5.6 Modification or Withdrawal of Proposals

1.6 PROPOSAL EVALUATION

1.6.1 State of South Dakota Conflict of Interest Policy

1.6.2 Comparative Assessment

1.7 SUPPLEMENTAL INFORMATION

1.7.1 Presentation/Demonstrations

1.7.2 Discussions

1.7.3 Technical Review

1.7.4 Financial Statement

1.8 NEGOTIATIONS AND AWARD

1.8.1 Best and Final Offers

1.8.2 Rejection, Waiver, and Award

1.9 CONTRACT

1.10 PROTEST PROCEDURES

1.11 STANDARD CONTRACT TERMS

1.12 REQUIRED CERTIFICATIONS

1.12.1 Certification Regarding Debarment, Suspension, Ineligibility and Voluntary Exclusion ... 5

1.12.2 Non-Discrimination Statement

1.12.3 Restriction of Boycott of Israel

1.12.4 Restriction of Prohibited Entity

1.12.5 Lobbying

2 PROPOSAL FORMAT

2.1 PROPRIETARY INFORMATION

2.2 USE OF THE SOUTH DAKOTA STATE SEAL

2.3 PROPOSAL CHECKLIST

2.4 TITLE PAGE

2.5 TABLE OF CONTENTS

2.6 EXECUTIVE SUMMARY

2.7 CORPORATE QUALIFICATIONS

2.8 RELEVANT PROJECT EXPERIENCE

Active Traffic Management System RFP 26RFP19813 iv Published May 6, 2026

2.9 SYSTEM DESCRIPTION

2.10 WORK PLAN

2.11 PROJECT SCHEDULE

2.12 DELIVERABLES

2.13 TESTING PLAN

2.14 TRAINING PLAN

2.15 GO LIVE PLAN

2.16 MAINTENANCE AND OPERATIONS PLAN

2.17 REQUIREMENTS TRACEABILITY MATRIX

2.18 STAFFING PLAN

2.19 SDDOT INVOLVEMENT

2.20 QUALITY MANAGEMENT PLAN

2.21 COST PROPOSAL

2.22 STANDARD CONTRACT TERMS

2.23 BUREAU OF INFORMATION AND TECHNOLOGY REQUIRED CONTRACT TERMS

2.24 IT REQUIREMENTS CONFORMANCE

2.24.1 Artificial Intelligence Use

2.24.2 Hosting and Data Access Requirements

2.24.3 Single Sign-On Requirements

2.24.4 SSO Logout Initiation Requirements

2.24.5 Session Timeout Requirements

2.24.6 Session Termination on Browser Close Requirement

2.24.7 Onboarding/Provisioning of Users Requirement

2.24.8 Interfaces and Integration Requirements

2.24.9 Web Application Vulnerability Scan Requirements

2.24.10 Test System Requirement

2.24.11 Internal Processes and Procedures Requirement

2.24.12 Email Domain Name Requirement

2.24.13 Banned Entity Requirement

2.24.14 Access Management Requirement

2.24.15 Website Requirements

2.24.16 Web Content Accessibility Guidelines Requirement

2.24.17 Browser Compatibility

2.24.18 State Hosted Solutions (On-Prem or State Cloud) Requirements

2.24.18.1 Virtualized Environment Requirement

2.24.18.2 Network Vulnerability Scan Requirement

2.24.18.3 Load Balancing Requirement

2.24.18.4 Use of Abstraction Technologies Requirement

2.24.18.5 Non-Standard Hardware and Software Requirement

2.24.19 Vendor to State Hosted Transition Requirement

2.24.20 Vendor Hosted Solution Requirements

2.24.21 General Vendor Hosted Requirements

2.24.22 Import and Export of Data Requirement

2.25 BUREAU OF INFORMATION AND TECHNOLOGY SECURITY AND VENDOR QUESTIONS

2.26 REQUIRED DIAGRAMS

Active Traffic Management System RFP 26RFP19813 v Published May 6, 2026

2.26.1 System Diagram

2.26.2 Solution Diagram

3 CURRENT SDDOT ITS DEVICES AND SYSTEMS

3.1 TRAFFIC OPERATIONS CENTER

3.2 CURRENT ITS DEVICES

3.2.1 Highway CCTV

3.2.2 Environmental Sensor Stations (ESS)

3.2.3 Highway CCTV

3.2.4 Permanent and Portable Dynamic Message Signs (DMS and PMS)

3.2.5 Variable Speed Limits (VSL)

3.2.6 Traffic Detectors

3.2.7 Gates and Beacons

3.2.8 Remote Power Management

3.2.9 Automatic Vehicle Location (AVL)

3.2.10 Intelligent Work Zone Devices

3.2.11 Traffic Signals

3.2.12 V2X (Vehicle to Everything)

3.3 CURRENT ITS SYSTEMS

3.3.1 Geographic Information Systems

3.3.2 SD511 Traveler Information System

3.3.3 Maintenance Decision Support System Maintenance Decision Support System (MDSS)

3.3.4 Computer Aided Dispatch (CAD)

3.3.5 Rest Area and Division of Criminal Investigation (DCI) CCTV

3.3.6 Truck Parking Information System

3.3.7 Wind Warning System

3.3.8 Situation Data Exchange (SDX)

4 FUNCTIONAL REQUIREMENTS

4.1 GENERAL REQUIREMENTS

4.2 TRAFFIC OPERATIONS FUNCTIONS

4.2.1 Communication

4.2.2 Map Interface

4.2.3 Device Status Monitoring and Control

4.2.4 Highway & Traffic Conditions Monitoring

4.2.5 Event Management

4.2.6 Configuration

4.2.7 User Administration

4.2.8 Analysis & Reporting

4.2.9 Data Governance

4.3 ITS DEVICE AND SYSTEM INTEGRATION

4.4 ITS DEVICE INTEGRATION

4.4.1 Highway CCTV

4.4.2 Environmental Sensor Stations (ESS)

4.4.3 Dynamic Message Signs (DMS)

4.4.4 Variable Speed Limits (VSL)

4.4.5 Vehicle Detection Devices (VDD)

Active Traffic Management System RFP 26RFP19813 vi Published May 6, 2026

4.4.6 Gates and Beacons

4.4.7 Remote Power Management

4.4.8 Automatic Vehicle Location (AVL)

4.4.9 Intelligent Work Zone Devices

4.4.10 Traffic Signals

4.4.11 V2X (Vehicle to Everything)

4.5 SYSTEM INTEGRATION

4.5.1 Geographic Information Systems

4.5.2 SD511 Traveler Information System

4.5.3 Maintenance Decision Support System (MDSS)

4.5.4 Computer-Aided Dispatch

4.5.5 Rest Area and Division of Criminal Investigation (DCI) CCTV

4.5.6 Truck Parking Information System

4.5.7 Wind Warning System

4.5.8 Situation Data Exchange (SDX)

5 OPERATIONAL SCENARIOS

5.1 ROUTINE MONITORING AND INCIDENT RESPONSE SCENARIO

5.2 MAJOR INCIDENT SCENARIO

5.3 SPECIAL EVENT SCENARIO (STURGIS MOTORCYCLE RALLY)

5.4 EMERGENCY WEATHER EVENT SCENARIO

5.5 PLANNED CONSTRUCTION SCENARIO

APPENDIX A PROPOSAL TITLE PAGE TEMPLATE

APPENDIX B ITS DEVICE INVENTORY

B.1 HIGHWAY CAMERAS

B.2 CELLULAR ROUTERS

B.3 ROUTERS

B.4 DYNAMIC MESSAGE SIGNS (DMS)

B.5 PORTABLE DYNAMIC MESSAGE SIGNS (PDMS)

B.6 VARIABLE SPEED LIMIT (VSL) SIGNS

B.7 WEATHER SENSORS

B.8 ENVIRONMENTAL SENSOR STATION CONTROLLERS

B.9 ROAD WEATHER INFORMATION SYSTEM RWIS

B.10 TRAFFIC SENSORS

B.11 TRAFFIC SENSORS (VARIABLE SPEED LIMIT)

B.12 NETWORKED POWER SWITCHES

B.13 POWER DISTRIBUTION UNITS (PDU)

B.14 UNINTERRUPTIBLE POWER SUPPLIES (UPS)

B.15 WEB RELAY DEVICES

B.16 MOBILE DATA COLLECTORS (MDC)

APPENDIX C STANDARD CONTRACT TERMS AND CONDITIONS

APPENDIX D STANDARD TITLE VI / NONDISCRIMINATION ASSURANCES

APPENDIX E BUREAU OF INFORMATION AND TECHNOLOGY REQUIRED IT CONTRACT TERMS

Active Traffic Management System RFP 26RFP19813 vii Published May 6, 2026

APPENDIX F SECURITY ACKNOWLEDGEMENT FORM

APPENDIX G BUREAU OF INFORMATION AND TECHNOLOGY SECURITY AND VENDOR QUESTIONNAIRE

LIST OF FIGURES

Figure 1 – Current ITS Systems

LIST OF TABLES

Table 1: Procurement Schedule Table 2: Proposal Checklist Table 3: Milestones and Deliverables Table 4: Project Team Roles Table 5: Example Budget Table Table 6: ITS Device and System Integration

Active Traffic Management System RFP 26RFP19813 1 Published May 6, 2026

1 GENERAL INFORMATION

1.1 SPONSORING AGENCY

The Intelligent Transportation Systems Program of the South Dakota Department of Transportation (SDDOT) is the issuing office for this document and all subsequent addenda relating to it. Unless the names of specific agencies are needed for clarity, the term “State” in this Request for Proposal (RFP) refers to the SDDOT, other selected State of South Dakota agencies, or South Dakota state government collectively.

SDDOT will be the coordinating agency for all matters related to any agreement resulting from this RFP.

1.2 PURPOSE OF REQUEST FOR PROPOSAL

1.2.1 Overview

SDDOT seeks vendors with the necessary experience, knowledge, and capability to furnish, and operationally deploy a statewide Active Traffic Management System (ATMS). The ATMS will monitor, control, and coordinate all intelligent transportation system assets on SDDOT’s network of Interstate, US, and SD highways.

1.2.2 Detailed Work Definition

Detailed definition of the work is provided in Section 4 Functional Requirements (page 29).

1.3 PERIOD OF PERFORMANCE

The work will begin upon execution of an agreement between SDDOT and the successful vendor, estimated to be July 1, 2026. Deployment of an operational ATMS, as described in the Scope of Work, is required by January 31, 2027. Refinement, operational support, and maintenance of the ATMS will extend through January 31, 2028. The period of performance may be optionally extended through January 31, 2031.

1.4 PROPOSER ELIGIBILITY

SDDOT solicits proposals from people, firms, or corporations with demonstrated capability and experience developing, deploying, and operating statewide Active Traffic Management Systems.

No proposal will be accepted from, and no contract will be awarded to any person, firm, or corporation that is in arrears upon any obligations to the State of South Dakota or that otherwise may be deemed irresponsible or unreliable by the State of South Dakota.

The Proposer must be registered with the South Dakota Secretary of State to conduct business within the State of South Dakota prior to execution of a contract.

1.5 PROCUREMENT PROCESS

The procurement schedule is defined in Table 1.

Active Traffic Management System RFP 26RFP19813 2 Published May 6, 2026

TTable 11:: Procurement Schedule Activity End Date & Time RFP Section

RFP Publication May 6, 2026 1.5.1 Deadline for letter of intent May 15, 2026 1.5.2 Deadline for submission of written inquiries May 22, 2026 1.5.3 SDDOT responses to questions May 26, 2026

Proposal submission to SDDOT June 5, 2026, 3:00PM

CDT 1.5.4

Evaluation of proposals to determine short list (if required) June 19, 2026 1.6 Demonstrations, presentations, discussions (if required) June 26, 2026 1.7 Proposal revisions (if required) June 31, 2026 1.8 Award decision July 10, 2026 1.8 Agreement execution, notice to proceed July 15, 2026 1.9

1.5.1 Request for Proposal

This document constitutes the complete Request for Proposal for this project. All proposals, correspondence, and documentation relating to this RFP must refer to its reference number 26RFP19813.

Proposers will be notified on the state’s procurement system regarding any modifications to this RFP.

Proposers may not rely on any other statements, either written or verbal, that alter any specification, term, or condition of this RFP.

1.5.2 Letter of Intent

All interested Proposers must submit a Letter of Intent to respond to this RFP by May 15, 2026.

The Letter of Intent must be submitted to SDDOT via email to dave.huft@state.sd.us. Please place “Letter of Intent for RFP Number 26RFP19813” in the email subject line.

1.5.3 Proposer Inquiries

Proposers and their agents (including subcontractors, employees, consultants, or anyone acting on their behalf) may email inquiries concerning this RFP to obtain clarification of requirements. No inquiries will be accepted after May 22, 2026. Questions must be sent to dave.huft@state.sd.us by e-mail with the subject line “RFP Number 26RFP19813”.

The questions and their answers will be sent to all Proposers that submitted Letters of Intent, submitted questions, or requested the questions and answers via email before the proposal submittal date and will be sent by May 26, 2026.

Proposers will be notified in the same manner regarding any modifications to this RFP.

Proposers may not rely on any other statements, either of a written or oral nature, that alter any specification or other term or condition of this RFP that have not originated from the SD RFP Project Contact. Proposers and their agents may not otherwise contact SDDOT regarding this RFP during the solicitation and evaluation process. Unauthorized contact is grounds for exclusion from this procurement.

1.5.4 Proposal Submission

The Proposer must submit an electronic copy of the proposal via email to dave.huft@state.sd.us with the subject line “RFP Number 26RFP19813”. Total file size may not exceed 24MB.

All proposals must be received by the SDDOT by June 5, 2026, 3:00PM CDT. Proposals received after the deadline will be ineligible for consideration.

Active Traffic Management System RFP 26RFP19813 3 Published May 6, 2026

Proposals must be signed by an individual legally authorized to bind the Proposer to the proposal.

Proposals that are not properly signed may be rejected.

All materials submitted become the property of the State of South Dakota and may be returned only at the State's option.

1.5.5 Proposal Format

The proposal must conform to the format prescribed in Section 2, Proposal Format.

1.5.6 Modification or Withdrawal of Proposals

Proposals may be modified or withdrawn by e-mail to dave.huft@state.sd.us prior to the submission deadline. No oral, telephonic, or facsimile modifications or withdrawals will be considered.

1.6 PROPOSAL EVALUATION

Proposals will be evaluated by staff of SDDOT’s Intelligent Transportation Systems Program and an evaluation team knowledgeable of the subject drawn from other SDDOT offices and the South Dakota Bureau of Information and Technology. Proposals may be reviewed and evaluated by any person at the discretion of SDDOT.

1.6.1 State of South Dakota Conflict of Interest Policy

The State of South Dakota’s conflict of interest policy prohibits any employee, officer, or agent of the State of South Dakota or approved third party applicant from participating in the selection, award, or administration of a procurement supported by federal funds, if, to his or her knowledge, any of the following has a financial or other interest in suppliers considered for award:

the employee, officer, or agent any member of his or her immediate family his or her domestic partner any organization that employs or is about to employ any of the above

1.6.2 Comparative Assessment

After determining that a proposal satisfies the requirements stated in the Request for Proposal, the evaluation team will assess the proposal by considering:

the Proposer’s commitment and ability to accomplish the work within prescribed time and budget experience and reliability of the Proposer’s organization qualifications of the personnel proposed to perform the work, whether from the proposing organization or from a subcontractor specialized expertise, capability, and technical competence to meet the project requirements, as demonstrated by the proposed approach and methodology resources, including any specialized services, available to perform the work record of past performance, including price and cost data from previous projects, quality of work, ability to meet schedules, cost control, and contract administration availability to the project locale familiarity with the project locale proposed project management techniques ability and proven history in handling special project constraints

Active Traffic Management System RFP 26RFP19813 4 Published May 6, 2026 conformance to standard contract terms Appendix C Standard Contract Terms and Conditions (page 46) conformance to information technology requirements specified in Appendix E Bureau of Information and Technology Required IT Contract Terms (page 53) and approval by the SD Bureau of Information and Technology cost

It is the Proposer's sole responsibility to submit information related to the evaluation categories. The State of South Dakota is under no obligation to solicit information missing from the proposal. The Proposer 's failure to submit information requested in the RFP may adversely affect the evaluation of the proposal.

1.7 SUPPLEMENTAL INFORMATION

The State may invite or require additional information after proposals are submitted.

1.7.1 Presentation/Demonstrations

The State may require a presentation or demonstration by a Proposer to clarify a proposal. However, the State may award a contract based on the initial proposals received without a presentation or demonstration. If presentations or demonstrations are required, they will be scheduled after submission of proposals and made at the Proposer’s expense.

1.7.2 Discussions

The State may invite Proposers to engage in discussions before or after proposals have been submitted.

Discussions will be held at the Proposer’s expense.

1.7.3 Technical Review

The State may require a technical review based on the proposal and response to Appendix G Security Acknowledgement Form (page 73).

1.7.4 Financial Statement

The State may require a Proposer to submit a copy of its most recently audited financial statement.

1.8 NEGOTIATIONS AND AWARD

This procurement is a Request for Proposal and Competitive Negotiation process. Each proposal will be evaluated, and each Proposer must be available for negotiation discussions and meetings at SDDOT’s request. SDDOT reserves the right to negotiate any component of any proposal submitted. From the time the proposals are submitted until formal award of a contract, all proposals and negotiation discussions will be considered confidential.

SDDOT and the highest ranked Proposer will mutually discuss and refine the scope of work and negotiate terms, including compensation and performance schedule. If the agency and the highest ranked Proposer are unable to negotiate a contract at a fair and reasonable price, SDDOT will, either orally or in writing, terminate negotiations with the Proposer. SDDOT may then negotiate with the next highest ranked Proposer. The process may continue through successive Proposers, according to proposal ranking, until an agreement is reached, or the contracting process terminates.

1.8.1 Best and Final Offers

The State reserves the right to request best and final offers. The State will initiate the request for best and final offers; requests may not be initiated by a Proposer. Best and final offers may not be necessary if the State is satisfied with the proposals received.

Active Traffic Management System RFP 26RFP19813 5 Published May 6, 2026

The State will select the Proposers to be notified and ask them to submit their best and final offers.

Requests will identify specific areas to be covered and the response deadline. Conditions, terms, or price of the proposal may be altered, provided the changes are within the scope of this Request for Proposal and the instructions contained in the request for best and final offer. If a Proposer does not submit a best and final offer or a notice of withdrawal, the Proposer’s latest proposal will be considered its best and final offer. After best and final offers are received, final evaluations will be conducted.

1.8.2 Rejection, Waiver, and Award

The State reserves the right to reject any or all proposals, waive technicalities, and make awards deemed to be in the best interest of the State of South Dakota.

1.9 CONTRACT

Upon successful negotiation, the selected Proposer and the State of South Dakota will execute a formal agreement for services incorporating the final proposal by reference. SDDOT prefers a fixed-price-for-deliverables agreement.

1.10 PROTEST PROCEDURES

Any party who is aggrieved in connection with the solicitation or award of this contract may protest to the Secretary of the South Dakota Department of Transportation at 700 East Broadway Avenue, Pierre, South Dakota 57501, or Joel.Jundt@state.sd.us. The protest must be submitted in writing within ten (10) business days after the aggrieved interested party knows, or should have known, of the facts giving rise thereto. Protests received after ten business days will not be considered. The written protest will include, at a minimum:

the name and address of the protestor appropriate identification of the procurement by RFP title and number a statement of the reasons for the protest any available exhibits, evidence, or documents substantiating the protest

SDDOT will respond, in detail, to each substantive issue raised in the protest. The Secretary of the SDDOT has the authority to make the final determination on the protest. A request for reconsideration of the decision regarding the protest may be allowed by the Secretary of the SDDOT if information becomes available that was previously unknown, or if an error of law or regulation occurred.

1.11 STANDARD CONTRACT TERMS

Any contract or agreement resulting from this RFP will include the provisions listed in Appendix C Standard Contract Terms and Conditions (page 46), along with any additional terms and conditions negotiated by the State and the Contractor.

1.12 REQUIRED CERTIFICATIONS

By signing and submitting its proposal, the Proposer certifies its compliance with the following administrative requirements of the State of South Dakota.

1.12.1 Certification Regarding Debarment, Suspension, Ineligibility and Voluntary Exclusion

By signing and submitting its proposal, the Proposer certifies that neither it nor its principals are presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from participation by any Federal department or agency from transactions involving the use of Federal funds.

Active Traffic Management System RFP 26RFP19813 6 Published May 6, 2026

If the Proposer is unable to certify any of the statements in this certification, the Proposer will attach an explanation to its proposal.

1.12.2 Non-Discrimination Statement

The State of South Dakota requires that all contractors, vendors, and suppliers doing business with the State provide a statement of non-discrimination. By signing and submitting their proposal, the Proposer certifies they do not discriminate in their employment practices with regard to race, color, creed, religion, age, sex, ancestry, national origin, or disability.

Requirements are fully described in SDDOT’s Standard Title VI / Nondiscrimination Assurances (page 51).

1.12.3 Restriction of Boycott of Israel

By submitting a response to this solicitation, contractors, vendors, suppliers, or subcontractors with five

(5) or more employees who enter into a contract with the State of South Dakota involving the expenditure of one hundred thousand dollars ($100,000) or more, certify and agree that:

The bidder or vendor, in preparing its response or offer or in considering proposals submitted from qualified, potential vendors, suppliers, and subcontractors, or in the solicitation, selection, or commercial treatment of any vendor, supplier, or subcontractor, has not refused to transact business activities, has not terminated business activities, and has not taken other similar actions intended to limit its commercial relations, related to the subject matter of the bid or offer, with a person or entity on the basis of Israeli national origin or residence or incorporation in Israel or its territories, with the specific intent to accomplish a boycott or divestment of Israel in a discriminatory manner. It is understood and agreed that, if this certification is false, such false certification will constitute grounds for the State to reject the bid or response submitted by the bidder or vendor on this project and terminate any contract awarded based on the bid or response. The successful bidder or vendor further agrees to provide immediate written notice to the contracting executive branch agency if, during the term of the contract, it no longer complies with this certification and agrees such noncompliance may be grounds for contract termination.

1.12.4 Restriction of Prohibited Entity

By submitting a response to this solicitation or agreeing to contract with the State, the Proposer certifies and agrees that:

The bidder or Proposer, in preparing its response or offer or in considering proposals submitted from qualified, potential vendors, suppliers, and subcontractors, or in the solicitation, selection, or commercial treatment of any vendor, supplier, or subcontractor, is not a prohibited entity, regardless of its principal place of business, that is ultimately owned or controlled, directly or indirectly, by a foreign national, a foreign parent entity, or foreign government from China, Iran, North Korea, Russia, Cuba, or Venezuela, as defined by South Dakota Codified Law § 5-18A. It is understood and agreed that, if this certification is false, such false certification will constitute grounds for the State to reject the bid or response submitted by the bidder or Proposer on this project and terminate any contract awarded based on the bid or response. The successful bidder or Proposer further agrees to provide immediate written notice to the contracting executive branch agency if during the term of the contract it no longer complies with this certification and agrees such noncompliance may be grounds for contract termination and would be cause to suspend and debar a business under SDCL § 5-18D-12.

Active Traffic Management System RFP 26RFP19813 7 Published May 6, 2026

1.12.5 Lobbying

By submitting a response to this solicitation or agreeing to contract with the State, the Proposer certifies and agrees that:

No Federal appropriated funds have been paid or will be paid, by or on behalf of the Proposer, to any person for influencing or attempting to influence an officer or employee of any agency, a member of Congress, an officer or employee of Congress, or an employee of a member of Congress in connection with the awarding of any Federal contract, the making of any Federal grant, the making of any Federal loan, the entering into of any cooperative agreement, and the extension, continuation, renewal, amendment, or modification of a Federal contract, grant, loan, or cooperative agreement. If any funds other than Federal appropriated funds have been paid or will be paid to any of the above-mentioned parties, the undersigned shall complete and submit Standard Form LLL, “Disclosure Form to Report Lobbying,” in accordance with its instructions.

The Proposer shall require that the language of this certification be included in the award documents for all subawards at all tiers (including subcontracts, subgrants, and contracts under grants, loans, and cooperative agreements) and that all subrecipients shall certify and disclose accordingly. This certification is a material representation of fact upon which reliance was placed when this transaction was made or entered into. Submission of this certification is a prerequisite for making or entering into this transaction imposed by section 1352, title 31, U.S. Code. Any person who fails to file the required certification shall be subject to a civil penalty or not less than $10,000 and not more than $100,000 for each such failure.

Active Traffic Management System RFP 26RFP19813 8 Published May 6, 2026

2 PROPOSAL FORMAT

The Proposal should clearly and concisely demonstrate the Proposer’s ability to satisfy the requirements of the RFP. Elaborate brochures, sales literature, and other material unnecessary to an effective proposal should not be submitted.

2.1 PROPRIETARY INFORMATION

The proposal of the successful Proposer will become public information, but proprietary information such as client lists and nonpublic financial statements can be protected under limited circumstances. Proposers must clearly identify in the Executive Summary (Section 2.6, page 9) specific information requested to be protected from disclosure and justify why it to be protected. The entire proposal may not be marked proprietary.

2.2 USE OF THE SOUTH DAKOTA STATE SEAL

Use of the South Dakota State Seal in any of the Proposer’s documents is illegal under South Dakota Codified Law § 1-6-3.1. No person may reproduce, duplicate, or otherwise use the official seal of the State of South Dakota or its facsimile for any for-profit commercial purpose without specific authorization from the Secretary of State. A violation of this section is a Class 1 misdemeanor.

2.3 PROPOSAL CHECKLIST

The proposal must include every item listed in the order shown in Table 2.

TTable 22:: Proposal Checklist

Item Required in Proposal Section Page Title Page 2.4 9 Table of Contents 2.5 9 Executive Summary 2.6 9 Corporate Qualifications 2.7 9 Relevant Project Experience 2.8 9 System Description 2.9 9 Work Plan 2.10 10 Project Schedule 2.11 10 Testing Plan 2.13 12 Training Plan 2.14 13 Go Live Plan 2.15 13 Maintenance and Operations Plan 2.16 13 Requirements Traceability Matrix 2.17 14 Staffing Plan 2.18 14 SDDOT Involvement 2.19 16 Quality Management Plan 2.20 16 Cost Proposal 2.21 16 Standard Contract Terms 2.22 16 Bureau of Information and Technology Required Contract Terms 2.23 16 IT Requirements Conformance 2.24 17 Bureau of Information and Technology Security and Vendor Questions 2.25 22 Required Diagrams 2.26 22

Active Traffic Management System RFP 26RFP19813 9 Published May 6, 2026

2.4 TITLE PAGE

The proposal title page must conform to the example shown in Appendix A Proposal Title Page (page 42).

By signing the title page, the Proposer:

certifies compliance with the provisions of Section 1.12, Required Certifications (page 5) acknowledges the provisions of Appendix C Standard Contract Terms and Conditions (page 46) acknowledges the provisions of Appendix E Bureau of Information and Technology Required IT

Contract Terms (page 53)

2.5 TABLE OF CONTENTS

The proposal must include a Table of Contents citing page numbers of all sections and subsections. All pages of the proposal must be numbered.

2.6 EXECUTIVE SUMMARY

The two- or three-page Executive Summary must describe the Proposer’s understanding of the purpose and scope of the project, identify critical success factors, and assess potential problems. It must identify any requirements that cannot be met by the Proposer. A reader should be able to ascertain the essence of the proposal by reading the Executive Summary.

2.7 CORPORATE QUALIFICATIONS

This section must describe the qualifications of the organizations proposed to perform the work. The section should identify corporate resources, including any specialized services, available to accomplish the work within the project timeline. Other factors, such as availability to and familiarity with the project locale, corporate knowledge of the subject and experience in similar projects, organizational capacity and stability, and experience in government-sponsored work should be described.

2.8 RELEVANT PROJECT EXPERIENCE

This section must summarize the Proposer’s corporate experience in developing, deploying, and operationally supporting Active Traffic Management Systems.

This section must also describe up to four recent projects that the Proposer has recently completed. For each project, the scope of work, project scale, starting and completion dates, and particular challenges and constraints should be identified. Each project’s principal sponsor must be listed, including company name, project manager, and contact address, phone number, and e-mail address.

The Proposer’s technical and managerial roles and responsibilities for each project must be described, as must be the outcome of the work, in terms of successfully accomplishing the work on time and within budget. Litigation or adverse contract action regarding contract performance must be reported.

2.9 SYSTEM DESCRIPTION

This section must describe in appropriate detail software and other elements that will be supplied and describe their suitability for the project. The system description must include:

the ATMS and associated software that will be deployed hosting configuration (on-premises, cloud, etc.)

server provisioning requirements and system resiliency approach integration with systems described in Sections 4.4 and 4.5

Active Traffic Management System RFP 26RFP19813 10 Published May 6, 2026 systems or devices described in Sections 4.4 and 4.5 that will not be supported in the initial deployment approach to connection and server security

The response should be in narrative form with explanatory graphics where appropriate. A detailed listing of specification conformance with the Scope of Work described in Section 4.0 is not required in this section.

2.10 WORK PLAN

The Work Plan must cite each element of Section 4 Scope of Work (page 33) and describe in appropriate detail how the Contractor will accomplish it. Proposers may wish to organize responses in tabular form listing a response for each element. For each element, the Contractor should indicate:

whether the element is supported in the initial deployment for each supported element, a concise description of the method of support (such as a supported device protocol, etc.) and any known limits of support in cases where an element is not supported by the ATMS solution, a statement of whether the element could be added through system customization with an estimate of time and expense.

in cases where an alternative approach to achieving the functionality described in Section 4.0 will be used, a concise explanation of the alternative and how it will meet the needs of SDDOT

In addition to the functional description of the solution described above, the Proposer must clearly describe how each milestone and deliverable will be completed in a structured Work Plan. The Work Plan must describe the methods to be employed, anticipated technical challenges, and the means to overcome them.

2.11 PROJECT SCHEDULE

The Project Schedule section must describe when each task of the project will be performed and completed. Planned start and end dates, in terms of elapsed time from project inception, must be listed and depicted in a Gantt chart. The information must be presented in a form that can be converted to actual dates when the project is started.

The milestones listed in Table 3 are required at a minimum. Proposers may reorder or add milestones.

The project will begin with a Notice to Proceed (NTP). The project Go Live date should occur no later than six months after Notice to Proceed (NTP).

2.12 DELIVERABLES

The Documentation section must describe the content and format of each document the Proposer will create and deliver during the work. At a minimum, documentation must include the deliverables listed in in Table 3.

Each required deliverable must be submitted, reviewed by SDDOT, and approved before the associated milestone is considered complete. Payments to the Contractor will be upon acceptance of completed milestones.

Active Traffic Management System RFP 26RFP19813 11 Published May 6, 2026

TTable 33:: MMilestones and DDeliverabless Milestone Activities Deliverables Timing

Project Initiation

Notice to Proceed Kickoff Meeting Ongoing Project Mgt Reporting

Project Management Plan (PMP)—Integrated plan covering schedule, staffing, risk management, communications, quality, change control, and meeting cadence, updated throughout the project Meeting notes

Kickoff within 14 days of

NTP

System Design Systems Engineering

System Architecture Design Document (ADD)— Technical architecture of the proposed ATMS, including the system architecture diagram, component descriptions, hosting model, and failover and recovery design Data Dictionary and Entity Relationship Diagram (DD/ERD)—Combined document describing all ATMS data entities, attributes, relationships, data types, and retention rules Integration Design Document—Design for each integration in Section 4.5, defining authentication, APIs, data flows, error handling, and failure modes System Security Plan (SSP)—Security controls, access management and user roles, encryption at rest and in transit, logging and audit approach, and compliance posture

Proposer to define

System Build

Deployment of core system in test environment Successful connection to some SDDOT ITS devices in test environment

Device Connection Report--Evidence of successful connection to a representative set of SDDOT ITS devices (CCTV, DMS, ESS/RWIS, VDD, VSL) in a designated test environment

Proposer to define

System Testing

Performance & Load Testing Security Testing Business Continuity & Disaster Recovery (BCDR) Testing User Acceptance Testing

Acceptance Test Plan—Contractor’s plan for acceptance testing Test Cases & Scripts—The cases and scripts that will demonstrate system functionality in accordance with the Requirements in Section 4 Functional Requirements and Section 5 Operational Scenarios Test reports documenting test results

Proposer to define

Training Training

Training Plan—Covers the training of System Operators, System Administrators, and SDDOT and SDBIT staff supporting the technical infrastructure Training Materials—Materials used during the training and referenceable afterward Training Delivery—Delivery of training to SDDOT and BIT staff

Proposer to define

Active Traffic Management System RFP 26RFP19813 12 Published May 6, 2026

TTable 33:: MMilestones and DDeliverabless Milestone Activities Deliverables Timing

Go Live

Deployment to Test/QA/Production Go Live SDDOT Acceptance

Application Support Document—Describes ATMS, including system architecture, deployment topology, operations reference, integration interfaces Support Plan—Contractor’s commercial & operational commitment to severity classifications, hours of coverage & escalation, support team staffing, issue management & reporting, security & compliance in accordance with SSP, and governance (roadmap, quarterly reviews, reporting)

Go Live no more than 7 months after NTP

Data Migration

Migration of any historical data

Documentation of migrated data. Proposer to define

Year 1 Operation

Operation & Maintenance

Demonstrated and documented performance through 12/31/2026

Year 2 Operation

Operation & Maintenance

Demonstrated and documented performance through 12/31/2027

2.13 TESTING PLAN

This section must describe a combination of factory and on-site testing, to be performed by the Contractor, to demonstrate required functionality and conformance with performance standards and specifications. Anticipated test documentation must be adequately described.

The following testing may be required:

Regression Testing – Regression testing is the process of testing changes to computer programs to ensure the older programming still works with the new changes.

Integration Testing – Integration testing is a software development process in which program units are combined and tested as groups in multiple ways. In this context, a unit is defined as the smallest testable part of an application. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution.

Functional Testing – Functional testing is primarily used to verify that software meets the business requirements of the end user. Typically, functional testing involves evaluating and comparing each software function with the business requirements. Software is tested by providing it with some related input so the output can be evaluated to see how it conforms, relates, or varies compared to its base requirements. Functional testing also checks the software for usability, such as ensuring that navigational functions work as required. Functional testing techniques typically include smoke testing, white box testing, black box testing, and unit testing.

Performance Testing – Performance testing determines the speed or throughput of an application. This process can involve quantitative tests such as measuring the response time or the number of instructions per second at which a system functions. Qualitative attributes such as reliability, scalability and interoperability may also be evaluated. Performance testing is often done in conjunction with load testing.

Load Testing – Load testing is the process of determining the ability of an application to maintain a certain level of effectiveness under unfavorable conditions. The process can involve tests such

Active Traffic Management System RFP 26RFP19813 13 Published May 6, 2026 as ramping up the number of users and transactions until the breaking point is reached or measuring the frequency of errors at required load. The term also refers to qualitative evaluation of factors such as availability or resistance to denial-of-service (DoS) attacks. Load testing is often done in conjunction with the more general process of performance testing. Load testing is also known as stress testing.

User Acceptance Testing – User acceptance testing (UAT) is the last phase of the software testing process. During UAT, actual software users test the software to make sure it can perform required tasks in real-world scenarios, according to specifications. UAT is one of the final and critical software project procedures that must occur before newly developed or customized software is deployed. UAT is also known as beta testing, application testing, or end user testing. In some cases, UAT may include piloting the software.

2.14 TRAINING PLAN

The Training Plan must describe the Proposer’s plan to deliver role-based training suited for administrators, end users, and technical support staff. Training will combine live virtual sessions, recorded on-demand modules, and written quick-reference guides tailored to each user role. A train-the-trainer program will equip State personnel to support ongoing onboarding after Go Live. All materials, including session recordings and documentation, will be delivered for the State’s unrestricted internal use.

2.15 GO LIVE PLAN

The Go Live Plan must describe the Proposer’s phased deployment approach, beginning with a limited pilot group before expanding to full production rollout.

The Contractor must coordinate a detailed launch runbook covering environment readiness, configuration validation, user access provisioning, and contingency procedures. A command center model must be staffed during the launch window, with vendor and State personnel monitoring system health, user activity, and support channels in real time. This support will extend for at least 30 days after launch, with defined escalation paths, periodic status briefings, and rapid response to incidents or change requests.

2.16 MAINTENANCE AND OPERATIONS PLAN

The Warranty section must describe the terms of an initial service warranty covering at least two years after acceptance of the work, as well as options for extended warranty throughout the expected life of the ATMS. Each description must address factors such as:

level of support days and hours of service availability response time service agent resolution time cost (for extended warranty only) licensing

The proposal must describe how ongoing maintenance and operations will be governed by a documented Service Level Agreement (SLA) covering system availability, incident response times, and routine maintenance windows.

The Contractor will provide tiered support (Level 1 through Level 3), proactive monitoring, regular security patching, and scheduled platform upgrades coordinated with the State. Quarterly operational reviews will track performance against SLA targets, identify improvement opportunities and align the roadmap with State priorities. Disaster recovery, backup integrity testing, and documentation updates must be performed on a published cadence, with all operational runbooks maintained in a shared repository accessible to authorized State staff.

Active Traffic Management System RFP 26RFP19813 14 Published May 6, 2026

2.17 REQUIREMENTS TRACEABILITY MATRIX

The Contractor will develop a Requirements Traceability Matrix mapping its implementation to the requirements of Section 4, Functional Requirements (page 29) and Section 5 Operational Scenarios (page 36).

2.18 STAFFING PLAN

The proposal must provide a Staffing Plan identifying key individuals, including subcontractor leads, who will be responsible for completing one or more major deliverables or managing the project or project elements. Resumé details should include:

name title phone numbers e-mail address work address proposed project role and responsibilities percentage of time proposed for this project relevant technical background project management experience education technical knowledge relevant certifications brief listing of work experience in reverse chronological order over the last five years, including company name, job titles, dates started and ended for each position, concise description of job duties, responsibilities, and significant accomplishments three professional references (name, telephone number, company name, relationship to employee)

The most successful projects typically use a team of consultant staff, agency staff, and IT staff with roles listed in Table 4. The Proposer may staff additional roles as needed for successful completion of the project. Changes to staff in any named role will require written SDDOT approval with equivalent qualifications. SDDOT’s Intelligent Transportation Systems Program Manager will be the Agency Project Manager.

2.19 SDDOT INVOLVEMENT

This section must describe assistance required from the South Dakota Department of Transportation, such as access to transportation facilities and information systems, technical information, or technical assistance. The required level of effort should be quantified as well as possible.

Active Traffic Management System RFP 26RFP19813 15 Published May 6, 2026

TTable 44:: Project Team Roles

Contractor Project Manager plan, organize, and execute the tasks needed to meet project requirements identify and document project goals and scope plan and document project tasks and schedule plan project kickoff meeting ensure deliverables and documentation are delivered on time manage project resources communicate effectively with stakeholders eliminate obstacles and potential risks document progress using various project management tools ensure project success define test and training strategies, system integration testing, and user acceptance testing develop cutover and transition plans ensure effective change management

Contractor Security Lead certify the security of each deliverable ensure the security of application development and management throughout the contract period

Contractor O&M Lead point of contact after the system is deployed

Agency Project Manager chief advocate for the project resolve agency resource and priority conflicts approve the project charter or plan hold the project team accountable for planning and executing the project approve changes affecting project scope, schedule, and budget provide day-to-day oversight of the project update the agency with new information plan, organize, and execute the Agency’s tasks needed to meet project requirements approve consultant payments based on contract language direct Agency employees and the Project Steering Team

Project Steering Team monitor work progress and accomplishments monitor expenditures recommend beneficial changes to project scope, schedule, or cost

BIT Project Manager plan, organize, and execute the BIT tasks needed to meet project requirements coordinate or collaborate with the Agency and Consultant Project Managers to develop a project plan and schedule for the BIT project deliverables manage and report on BIT project deliverables work with BIT management to ensure necessary BIT resources are available to execute the project develop a project communication plan to project stakeholders for BIT project deliverables be in close communication with Agency stakeholders and, when applicable, the Agency and Consultant Project Managers to ensure that all deliverables are met document and communicate BIT project risks, issues, decisions, actions, and change requests with project stakeholders

Active Traffic Management System RFP 26RFP19813 16 Published May 6, 2026

2.20 QUALITY MANAGEMENT PLAN

The Quality Management Plan must describe how the project will be managed to ensure the quality of work and deliverables. It must identify management responsibilities of team members and the processes that will be used to prevent, detect, and resolve quality problems.

Regular meetings between the Contractor, SDDOT, and SDBIT may be critical to the success of the project.

Meeting frequency may vary throughout the project. For budgeting purposes, Proposers should assume:

in-person meetings at SDDOT headquarters in Pierre at project kickoff and at least two other times weekly virtual meetings monthly written status reports

2.21 COST PROPOSAL

The Cost Proposal must confirm the Proposer’s willingness and ability to perform the work described in this RFP for the price being offered, as shown in Table 5. Payment will be made upon completion of milestones identified in the Project Schedule (Section 2.11). The total proposed cost must be clearly indicated. All costs related to the provision of the required work must be included. Proposers must identify any concerns and propose an alternative basis of payment if necessary.

TTable 55:: Example Budget Table Description Unit Quantity Unit Cost Price

Project Initiation & Management Monthly 7 System Design Each 1 System Build Each 1 System Testing Each 1 Training Each 1 Go Live Each 1 Data Migration Each 1 Year 1 Operation Each 1 Year 2 Operation Each 1 ATMS Software License – Year One Each 1 ATMS Software License – Year Two Each 1 ATMS Software License – Year Three Each 1 ATMS Software License – Year Four Each 1 ATMS Software License – Year Five Each 1 Support & Maintenance – Year One Each 1 Support & Maintenance – Year Two Each 1 Support & Maintenance – Year Three Each 1 Support & Maintenance – Year Four Each 1 Support & Maintenance – Year Five Each 1

2.22 STANDARD CONTRACT TERMS

The proposal must acknowledge acceptance of the provisions of Appendix C Standard Contract Terms and Conditions (page 46).