Response to Offeror Questions document 2.pdf

South Dakota Department of Transportation RFP 26RFP19813 Inquiries and Responses #2 Intelligent Transportation Systems Program May 20, 2026

As of May 20, 2026, the following additional inquiries have been submitted regarding RFP 26RFP19813.

Answers are being provided to all potential bidders who have submitted a Letter of Intent to propose.

Inquiry SDDOT Response

1. Your work plan references Scope of Work as Section

4, which is titled "Functional Requirements".

APPENDIX C STANDARD CONTRACT TERMS AND

CONDITIONS states "The Contractor will perform those services described in the Scope of Work, included as Section 3 of this RFP." What is the scope of work?

The language in APPENDIX C is incorrect. It should more broadly reference the work that will be described in your complete proposal.

2. Table 3 states three environments – Test/QA/Production- while Section XXXII. Security Scanning discusses scans and tests initially applied to “development and test environments.” What are the environments SDDOT would like?

SDDOT would like development, test, and production environments to be established.

3. Section 2.24.15 refers to BIT Web Standards, which provide requirements for any service-side scripting for web applications to be coded in C# ASP.NET. The Web Standards state that the language requirement applies to State-hosted solutions and not Vendor-hosted solutions. Appendix E BIT Required IT Contract Terms Section XXVIII states that all applications in this agreement will be written in C#.

We have an off-the-shelf product that does not use these languages. South Dakota has written an RFP for COTS that may not use C# ASP.NET. Please confirm that this does not apply to already-developed COTS products.

For COTS solutions, the C# ASP.NET requirement does not apply.

4. Section XXVIII of Appendix E BIT Required IT Contract Terms Section XXX item E states that "State access to the source code will be allowed to ensure State security standards, policies, and best practices […]”. Please confirm if the state is requiring that the software being provided should be put in escrow.

This would be negotiated with the winning bidder at the time of award and contract negotiations.

5. Please detail what work needs to be completed by the Go Live Date. Is it required to have interfaces for all of the devices (e.g. RWIS, AVL detectors etc.) and 3rd party systems (e.g. CAD, 511, etc.) completed and operational by this date?

SDDOT desires as many devices and systems as possible to be operation on the Go Live Date. The highest device priorities are DMS, VSL, RWIS, CCTV, and AVL.

Proposers should clearly explain what can be operational at Go Live and how long other devices and systems will take to become operational.

South Dakota Department of Transportation RFP 26RFP19813 Inquiries and Responses #2 Intelligent Transportation Systems Program May 20, 2026

Inquiry SDDOT Response

6. This project involves the integration of a number of legacy devices and systems. So that firms can properly estimate the integration efforts please provide contact information and interface control documents for all devices and external systems that need to be integrated with the ATMS?

SDDOT recognizes that more detailed information would be helpful, but assembling the information would take considerable time. Proposers must rely on information provided in Section 3 of the

RFP.

7. Has the Department worked with the manufacturers and suppliers of the devices and third-party systems to confirm that they will cooperate and provide support to proposers to assist in the integration with their devices/platforms.

Providers of other systems are aware that SDDOT is procuring an active traffic management system that will interface with their systems. SDDOT will require cooperation and support under their contractual requirements to SDDOT.

8. Given the number of devices and 3rd party systems will the Department extend the due date for proposals until at least July 3rd, 2026 or 30 days after the Department provides the documentation requested above, whichever is later? This will give proposers adequate time to assess the work associated with interfacing to the different devices/platforms and develop appropriate estimates of the work.

The proposal due date will not change.

9. Regarding Section 2.17: Building and finalizing a Requirements Traceability Matrix (RTM) is typically performed after award, once the project team has met with stakeholders. For this solicitation, are offerors expected to:

1. Submit a complete RTM with the proposal, or

2. Provide a description of the proposed process for developing and maintaining the RTM to ensure it meets the requirements in Sections 4 and 5?

Proposers may provide a description of the proposed process for developing and maintaining the RTM to ensure it meets the requirements in Sections 4 and 5.

For additional inquiries, please contact:

Dave Huft, ITS Program Manager dave.huft@state.sd.us Subject: RFP Number 26RFP19813