SDDOT_HNAR_25RFP12707_Requirements.xlsx

Requirement Checklist

SDDOT needs the Highway Needs and Analysis Report (Needs Book) Software to be an Internet-based system, accessible from any Internet browser, but configurable with access restrictions based on State of South Dakota LDAP credentials.

The Offeror will be required to provide a solution necessary to meet all system functions and requirements described in this RFP and the resulting contract, to include at a minimum:

Updates should be made in consultation with DOT so that we are never caught unaware by updates.

The State’s specific system requirements and specifications for the Needs Book Software are in Attachment 1.

The requirements were developed by the SDDOT Needs Book Team to document the functions that the Needs Book Software must perform to meet all the end users’ needs, but not to dictate ‘how’ they must be performed; the requirements are intentionally defined at high levels. Nonetheless, SDDOT is interested in all features and functions of a fully functional Needs Book software, regardless of whether the functions are mentioned in the requirements.

The Offeror will be responsible for performing the tasks outlined / described in this section.

3.4.6. Deliverable: Sample Web-based Needs Book

Presentation that shows capability of software to Display a GIS map and the corresponding tabular data of selected multiple Pavement Management segments together in an organized and navigable web-based format.

3.4.5.7. Deliverable - Needs Book Page rendering module.

Presentation that shows the capability of a module that will generate a set of .pdf or similar files to create a printed book of all data provided by the dTims pavement management system.

3.4.5.8. Deliverable - System Integration

A description of how you will integrate with existing data sources. This should be in the form of both

This guidance should clearly define the testing strategy and responsibilities. For example, the connections to the external business systems or services provided that contain the Needs Book data elements, performing data validations, coding data items, data formatting, and generating reports must be described. Test Scripts must be developed and supplied by the Offeror to aid in testing. Electronic Test Plans, Cases, and Scripts are acceptable.

The Offeror must be available for consultation and/or assistance during testing, at no additional cost to the State, until the SDDOT Project Manager has signed the Letter of Acceptance for the Needs Book System. It is anticipated that testing may take 14 days however, the actual length of testing may vary.

The Needs Book System must perform all aspects of system functionality as described in the RFP and resulting contract.

Manuals will be provided electronically to the Project Director in Microsoft Word (MS Word) and PDF format.

3.4.10.4. All travel for training will be reimbursed at actual expenses.

Either way, we expect the Offeror to perform technical support to maintain the operations of the Needs Book Software. the software will be installed in a SDDOT provided environment.

The Offeror will remain responsible for software maintenance, upgrades as needed, troubleshooting outages, and restoring operations that are not related to the hosting environment.

In addition, the Offeror will be responsible for performing all operations of the system, maintaining regular back-ups, and any database administration needed, perform back-ups of the system data, and deliver backups to SDDOT at a regular planned cycle to be agreed during system development.

The proposal should include a narrative describing how you will meet this deliverable.

If no data is stored with in the vendor system respond to 3.5.1 and 3.5.2 with N/A

3.6.2. The SSO supports the industry standard OAuth 2.0 protocol. This identity management will handle password recovery and multi-factor authentication (MFA). MFA is required for all application Administrators and may be required for other users. Microsoft’s official documentation on the identity provider the State has implemented can be found https://learn.microsoft.com/en-us/azure/active-directory/architecture/auth-oauth2 and https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-protocols-oidc for state employees, businesses, partners, providers, etc. (Azure Active Directory).

3.6.3. If the offeror is not able to fulfill this identity management standard, they will be excluded from the list.

3.7. Interfaces and Integration

3.7.1. The offeror must describe how the system can adapt to business necessary interfaces using widely adopted open APIs and standards. Additionally, SDDOT expects that the offeror will make available/expose software services and publish documentation for those software services that would enable third party developers to interface other business applications. A detailed description of system capability must be included in the proposal.

3.8. Solution Diagram

3.8.1. The offeror must provide a solution diagram providing specific details of how the entire solution will meet the requirements of the RFP. This will include integration with the State’s infrastructure, existing systems that will integrate with the proposed solution, how data would flow between systems, the technology stack of the solution including any dependencies, and include, but not be limited to, user onboarding/provision and SSO.