STATE 0000000391SL,4 TMS Maintenance and Support Services.docx

State of Missouri Office of Administration, Division of Purchasing

Request for Proposal (RFP) for Transportation Management System (TMS) Maintenance and Support Services

PROPOSAL DUE NO LATER THAN: July 27, 2026 AT 2:00 PM CENTRAL TIME Proposal response must be submitted electronically through MissouriBUYS, powered by MOVERS, at https://missouribuys.mo.gov.

E-mailed, mailed, courier, or hand-delivered proposal responses will not be accepted.

RFP CONTACT INFORMATION:

BUYER: Kelly Miller

PHONE NO.: (573) 751-4885

EMAIL: Kelly.Miller@oa.mo.gov See “RFP Questions” in Section 1 for appropriate communications during the procurement process.

DELIVER SUPPLIES/SERVICES FREE ON BOARD (FOB) DESTINATION TO THE FOLLOWING ADDRESS:

MISSOURI DEPARTMENT OF TRANSPORTATION (MODOT)

INFORMATION SERVICES, APPLICATION TECHNOLOGY—FINANCE

P. O. BOX 270, 601 W. MAIN

JEFFERSON CITY, MO 65102

ATTENTION:

1. After reviewing the Request for Proposal (RFP), the vendor must complete and return Exhibit A, Proposal Signature Page and all other necessary exhibits.

2. Due to lead times for obtaining the information needed to complete the various Business Compliance Exhibits herein as explained in the RFP’s Vendor Response Exhibits, vendors are encouraged to IMMEDIATELY begin securing these verifications.

3. The vendor must be registered in MissouriBUYS, powered by MOVERS in a “Prospective” or “Spend Authorized” registration status to submit a proposal. The vendor must achieve “Approved” registration status in MissouriBUYS (WebProcure/Proactis) and “Spend Authorized” registration status in MissouriBUYS, powered by MOVERS to be considered for a contract award. Reference Section 5.

AMENDMENT #04 to STATE 0000000391SL

TITLE: Transportation Management System (TMS) Maintenance and Support Services

CONTRACT PERIOD: Effective Date of Contract Through Three (3) Years

PLEASE BE ADVISED OF THE FOLLOWING CHANGES AND CLARIFICATIONS:

1. The Proposal Due Date is REVISED. The Proposal Due Date changed from 07/23/2026 at 2:00 pm Central Time to 07/27/2026 at 2:00 pm Central Time.

2. RFP Organization Table is REVISED

3. Paragraph 1.2.2 a. is ADDED

4. Paragraph 1.2.2 b. is ADDED

5. Paragraph 1.2.2 c. is ADDED

6. Paragraph 1.2.2 d. is ADDED

7. Paragraph 1.2.2 e. is ADDED

8. Paragraph 1.2.3 is REVISED

9. Paragraph 1.2.6 a. is ADDED

10. Paragraph 1.2.8 a. is ADDED

11. Paragraph 1.2.8 b. is ADDED

12. Paragraph 1.2.8 c. is ADDED

13. Paragraph 1.2.9 is REVISED

14. Paragraph 1.2.9 a. is ADDED

15. Paragraph 1.2.13 and subparagraphs are ADDED

16. Paragraph 1.2.14 and subparagraphs are ADDED

17. Paragraph 1.2.15 and subparagraphs are ADDED

18. Paragraph 1.2.16 is ADDED

19. Paragraph 1.2.17 is ADDED

20. Paragraph 1.2.18 and subparagraphs are ADDED

21. Paragraph 1.2.19 and subparagraphs are ADDED

22. Paragraph 1.2.20 and subparagraphs are ADDED

23. Paragraph 1.2.21 is ADDED

24. Paragraph 1.2.22 is ADDED

25. Paragraph 1.2.23 is ADDED

26. Paragraph 1.2.24 is ADDED

27. Paragraph 1.2.25 is ADDED

28. Paragraph 1.2.26 is ADDED

29. Paragraph 2.3.2 b. is ADDED

30. Paragraph 2.3.11 n. 1) is REVISED

31. Attachment 3 is ADDED

Vendors may review the revision(s) to the MissouriBUYS, powered by MOVERS electronic solicitation and the amendment document(s) at https://MissouriBUYS.mo.gov. You may be required to acknowledge the electronic amendment.

ATTENTION: IF YOU HAVE ALREADY SUBMITTED A RESPONSE TO THE SOLICITATION, ACCEPTANCE OF THE AMENDMENT AND RESUBMISSION YOUR SOLICITATION RESPONSE IS NECESSARY TO ENSURE THE STATE OF MISSOURI SUCCESSFULLY RECEIVES YOUR SOLICITATION RESPONSE.

Follow the instructions in the Reference Guide for How to Submit Response Online (https://missouribuys.mo.gov/media/pdf/movers-bid-response-instructions ) and outlined below if previously responded to the solicitation prior to the amendment issuance.

1) Log into MissouriBUYS, powered by MOVERS (https://missouribuys.mo.gov/).

2) Under Tasks click View Negotiations below Solicitations.

3) The Active Solicitations page will appear. Utilize the search filters and click on the Solicitation Number to open.

4) The Overview page will display. Click Create Response.

5) A Warning pop-up box will open. The supplier must click Yes to continue to view and acknowledge amendments.

6) The supplier should highlight the Amendment(s) and view the changes made via the amendment(s). Once the review is complete, select the Acknowledgement checkbox for each amendment and click Submit at the top right-hand corner of the page. NOTE: A Warning pop-up box will open if all amendments have not been acknowledged. Click Yes to continue.

7) A Confirmation pop-up box will open confirming amendments have been acknowledged. It will also warn that resubmission of the previously submitted response is necessary prior to response to the amendment. Click OK.

8) Supplier will need to click Create Response again and respond to the amended solicitation. NOTE: The Create Response step includes attaching the supplier’s response again.

Request for Proposal (RFP) for Transportation Management System (TMS) Maintenance and Support Services

PROPOSAL DUE NO LATER THAN: July 23, 2026 AT 2:00 PM CENTRAL TIME Proposal response must be submitted electronically through MissouriBUYS, powered by MOVERS, at https://missouribuys.mo.gov.

E-mailed, mailed, courier, or hand-delivered proposal responses will not be accepted.

RFP CONTACT INFORMATION:

BUYER: Kelly Miller

PHONE NO.: (573) 751-4885

EMAIL: Kelly.Miller@oa.mo.gov See “RFP Questions” in Section 1 for appropriate communications during the procurement process.

DELIVER SUPPLIES/SERVICES FREE ON BOARD (FOB) DESTINATION TO THE FOLLOWING ADDRESS:

MISSOURI DEPARTMENT OF TRANSPORTATION (MODOT)

INFORMATION SERVICES, APPLICATION TECHNOLOGY—FINANCE

P. O. BOX 270, 601 W. MAIN

JEFFERSON CITY, MO 65102

ATTENTION:

4. After reviewing the Request for Proposal (RFP), the vendor must complete and return Exhibit A, Proposal Signature Page and all other necessary exhibits.

5. Due to lead times for obtaining the information needed to complete the various Business Compliance Exhibits herein as explained in the RFP’s Vendor Response Exhibits, vendors are encouraged to IMMEDIATELY begin securing these verifications.

6. The vendor must be registered in MissouriBUYS, powered by MOVERS in a “Prospective” or “Spend Authorized” registration status to submit a proposal. The vendor must achieve “Approved” registration status in MissouriBUYS (WebProcure/Proactis) and “Spend Authorized” registration status in MissouriBUYS, powered by MOVERS to be considered for a contract award. Reference Section 5.

AMENDMENT #03 to STATE 0000000391SL

TITLE: Transportation Management System (TMS) Maintenance and Support Services

CONTRACT PERIOD: Effective Date of Contract Through Three (3) Years

1. The Proposal Due Date is REVISED. The Proposal Due Date changed from 07/15/2026 at 2:00 pm Central Time to 07/23/2026 at 2:00 pm Central Time.

An additional RFP amendment to address vendor questions will be forthcoming.

Vendors may review the revision(s) to the MissouriBUYS, powered by MOVERS electronic solicitation and the amendment document(s) at https://MissouriBUYS.mo.gov. You may be required to acknowledge the electronic amendment.

ATTENTION: IF YOU HAVE ALREADY SUBMITTED A RESPONSE TO THE SOLICITATION, ACCEPTANCE OF THE AMENDMENT AND RESUBMISSION YOUR SOLICITATION RESPONSE IS NECESSARY TO ENSURE THE STATE OF MISSOURI SUCCESSFULLY RECEIVES YOUR SOLICITATION RESPONSE.

Follow the instructions in the Reference Guide for How to Submit Response Online (https://missouribuys.mo.gov/media/pdf/movers-bid-response-instructions ) and outlined below if previously responded to the solicitation prior to the amendment issuance.

1) Log into MissouriBUYS, powered by MOVERS (https://missouribuys.mo.gov/).

2) Under Tasks click View Negotiations below Solicitations.

3) The Active Solicitations page will appear. Utilize the search filters and click on the Solicitation Number to open.

4) The Overview page will display. Click Create Response.

5) A Warning pop-up box will open. The supplier must click Yes to continue to view and acknowledge amendments.

6) The supplier should highlight the Amendment(s) and view the changes made via the amendment(s). Once the review is complete, select the Acknowledgement checkbox for each amendment and click Submit at the top right-hand corner of the page. NOTE: A Warning pop-up box will open if all amendments have not been acknowledged. Click Yes to continue.

7) A Confirmation pop-up box will open confirming amendments have been acknowledged. It will also warn that resubmission of the previously submitted response is necessary prior to response to the amendment. Click OK.

8) Supplier will need to click Create Response again and respond to the amended solicitation. NOTE: The Create Response step includes attaching the supplier’s response again.

Request for Proposal (RFP) for Transportation Management System (TMS) Maintenance and Support Services

PROPOSAL DUE NO LATER THAN: July 15, 2026 AT 2:00 PM CENTRAL TIME Proposal response must be submitted electronically through MissouriBUYS, powered by MOVERS, at https://missouribuys.mo.gov.

E-mailed, mailed, courier, or hand-delivered proposal responses will not be accepted.

RFP CONTACT INFORMATION:

BUYER: Kelly Miller

PHONE NO.: (573) 751-4885

EMAIL: Kelly.Miller@oa.mo.gov See “RFP Questions” in Section 1 for appropriate communications during the procurement process.

DELIVER SUPPLIES/SERVICES FREE ON BOARD (FOB) DESTINATION TO THE FOLLOWING ADDRESS:

MISSOURI DEPARTMENT OF TRANSPORTATION (MODOT)

INFORMATION SERVICES, APPLICATION TECHNOLOGY—FINANCE

P. O. BOX 270, 601 W. MAIN

JEFFERSON CITY, MO 65102

ATTENTION:

1. After reviewing the Request for Proposal (RFP), the vendor must complete and return Exhibit A, Proposal Signature Page and all other necessary exhibits.

2. Due to lead times for obtaining the information needed to complete the various Business Compliance Exhibits herein as explained in the RFP’s Vendor Response Exhibits, vendors are encouraged to IMMEDIATELY begin securing these verifications.

3. The vendor must be registered in MissouriBUYS, powered by MOVERS in a “Prospective” or “Spend Authorized” registration status to submit a proposal. The vendor must achieve “Approved” registration status in MissouriBUYS (WebProcure/Proactis) and “Spend Authorized” registration status in MissouriBUYS, powered by MOVERS to be considered for a contract award. Reference Section 5.

AMENDMENT #02 to STATE 0000000391SL

TITLE: Transportation Management System (TMS) Maintenance and Support Services

CONTRACT PERIOD: Effective Date of Contract Through Three (3) Years

1. The Proposal Due Date is REVISED. The Proposal Due Date changed from 07/07/2026 at 2:00 pm Central Time to 07/15/2026 at 2:00 pm Central Time.

Vendors may review the revision(s) to the MissouriBUYS, powered by MOVERS electronic solicitation and the amendment document(s) at https://MissouriBUYS.mo.gov. You may be required to acknowledge the electronic amendment.

ATTENTION: IF YOU HAVE ALREADY SUBMITTED A RESPONSE TO THE SOLICITATION, ACCEPTANCE OF THE AMENDMENT AND RESUBMISSION YOUR SOLICITATION RESPONSE IS NECESSARY TO ENSURE THE STATE OF MISSOURI SUCCESSFULLY RECEIVES YOUR SOLICITATION RESPONSE.

Follow the instructions in the Reference Guide for How to Submit Response Online (https://missouribuys.mo.gov/media/pdf/movers-bid-response-instructions ) and outlined below if previously responded to the solicitation prior to the amendment issuance.

1) Log into MissouriBUYS, powered by MOVERS (https://missouribuys.mo.gov/).

2) Under Tasks click View Negotiations below Solicitations.

3) The Active Solicitations page will appear. Utilize the search filters and click on the Solicitation Number to open.

4) The Overview page will display. Click Create Response.

5) A Warning pop-up box will open. The supplier must click Yes to continue to view and acknowledge amendments.

6) The supplier should highlight the Amendment(s) and view the changes made via the amendment(s). Once the review is complete, select the Acknowledgement checkbox for each amendment and click Submit at the top right-hand corner of the page. NOTE: A Warning pop-up box will open if all amendments have not been acknowledged. Click Yes to continue.

7) A Confirmation pop-up box will open confirming amendments have been acknowledged. It will also warn that resubmission of the previously submitted response is necessary prior to response to the amendment. Click OK.

8) Supplier will need to click Create Response again and respond to the amended solicitation. NOTE: The Create Response step includes attaching the supplier’s response again.

Request for Proposal (RFP) for Transportation Management System (TMS) Maintenance and Support Services

PROPOSAL DUE NO LATER THAN: July 7, 2026 AT 2:00 PM CENTRAL TIME Proposal response must be submitted electronically through MissouriBUYS, powered by MOVERS, at https://missouribuys.mo.gov.

E-mailed, mailed, courier, or hand-delivered proposal responses will not be accepted.

RFP CONTACT INFORMATION:

BUYER: Kelly Miller

PHONE NO.: (573) 751-4885

EMAIL: Kelly.Miller@oa.mo.gov See “RFP Questions” in Section 1 for appropriate communications during the procurement process.

DELIVER SUPPLIES/SERVICES FREE ON BOARD (FOB) DESTINATION TO THE FOLLOWING ADDRESS:

MISSOURI DEPARTMENT OF TRANSPORTATION (MODOT)

INFORMATION SERVICES, APPLICATION TECHNOLOGY—FINANCE

P. O. BOX 270, 601 W. MAIN

JEFFERSON CITY, MO 65102

ATTENTION:

1. After reviewing the Request for Proposal (RFP), the vendor must complete and return Exhibit A, Proposal Signature Page and all other necessary exhibits.

2. Due to lead times for obtaining the information needed to complete the various Business Compliance Exhibits herein as explained in the RFP’s Vendor Response Exhibits, vendors are encouraged to IMMEDIATELY begin securing these verifications.

3. The vendor must be registered in MissouriBUYS, powered by MOVERS in a “Prospective” or “Spend Authorized” registration status to submit a proposal. The vendor must achieve “Approved” registration status in MissouriBUYS (WebProcure/Proactis) and “Spend Authorized” registration status in MissouriBUYS, powered by MOVERS to be considered for a contract award. Reference Section 5.

AMENDMENT #01 to STATE 0000000391SL

TITLE: Transportation Management System (TMS) Maintenance and Support Services

CONTRACT PERIOD: Effective Date of Contract Through Three (3) Years

1. The Proposal Due Date is REVISED. The Proposal Due Date changed from 06/30/2026 at 2:00 pm Central Time to 07/07/2026 at 2:00 pm Central Time.

Vendors may review the revision(s) to the MissouriBUYS, powered by MOVERS electronic solicitation and the amendment document(s) at https://MissouriBUYS.mo.gov. You may be required to acknowledge the electronic amendment.

ATTENTION: IF YOU HAVE ALREADY SUBMITTED A RESPONSE TO THE SOLICITATION, ACCEPTANCE OF THE AMENDMENT AND RESUBMISSION YOUR SOLICITATION RESPONSE IS NECESSARY TO ENSURE THE STATE OF MISSOURI SUCCESSFULLY RECEIVES YOUR SOLICITATION RESPONSE.

Follow the instructions in the Reference Guide for How to Submit Response Online (https://missouribuys.mo.gov/media/pdf/movers-bid-response-instructions ) and outlined below if previously responded to the solicitation prior to the amendment issuance.

1) Log into MissouriBUYS, powered by MOVERS (https://missouribuys.mo.gov/).

2) Under Tasks click View Negotiations below Solicitations.

3) The Active Solicitations page will appear. Utilize the search filters and click on the Solicitation Number to open.

4) The Overview page will display. Click Create Response.

5) A Warning pop-up box will open. The supplier must click Yes to continue to view and acknowledge amendments.

6) The supplier should highlight the Amendment(s) and view the changes made via the amendment(s). Once the review is complete, select the Acknowledgement checkbox for each amendment and click Submit at the top right-hand corner of the page. NOTE: A Warning pop-up box will open if all amendments have not been acknowledged. Click Yes to continue.

7) A Confirmation pop-up box will open confirming amendments have been acknowledged. It will also warn that resubmission of the previously submitted response is necessary prior to response to the amendment. Click OK.

8) Supplier will need to click Create Response again and respond to the amended solicitation. NOTE: The Create Response step includes attaching the supplier’s response again.

Request for Proposal (RFP) for Transportation Management System (TMS) Maintenance and Support Services

PROPOSAL DUE NO LATER THAN: June 30,2026 AT 2:00 PM CENTRAL TIME Proposal response must be submitted electronically through MissouriBUYS, powered by MOVERS, at https://missouribuys.mo.gov.

E-mailed, mailed, courier, or hand-delivered proposal responses will not be accepted.

RFP CONTACT INFORMATION:

BUYER: Kelly Miller

PHONE NO.: (573) 751-4885

EMAIL: Kelly.Miller@oa.mo.gov See “RFP Questions” in Section 1 for appropriate communications during the procurement process.

DELIVER SUPPLIES/SERVICES FREE ON BOARD (FOB) DESTINATION TO THE FOLLOWING ADDRESS:

MISSOURI DEPARTMENT OF TRANSPORTATION (MODOT)

INFORMATION SERVICES, APPLICATION TECHNOLOGY—FINANCE

P. O. BOX 270, 601 W. MAIN

JEFFERSON CITY, MO 65102

ATTENTION:

1. After reviewing the Request for Proposal (RFP), the vendor must complete and return Exhibit A, Proposal Signature Page and all other necessary exhibits.

2. Due to lead times for obtaining the information needed to complete the various Business Compliance Exhibits herein as explained in the RFP’s Vendor Response Exhibits, vendors are encouraged to IMMEDIATELY begin securing these verifications.

3. The vendor must be registered in MissouriBUYS, powered by MOVERS in a “Prospective” or “Spend Authorized” registration status to submit a proposal. The vendor must achieve “Approved” registration status in MissouriBUYS (WebProcure/Proactis) and “Spend Authorized” registration status in MissouriBUYS, powered by MOVERS to be considered for a contract award. Reference Section 5.

RFP Organization:

TABLE REVISED PER RFP AMENDMENT 04

RFP Vendor Response Exhibits (Return these exhibits with the proposal)

BUSINESS COMPLIANCE EXHIBITS

Separate Documents: The vendor is advised that the separate documents to this document referenced above provide additional requirements, information, and/or instruction. The separate documents must be downloaded from the Division of Purchasing’s MissouriBUYS, powered by MOVERS, website at: https://missouribuys.mo.gov/. The separate documents are downloadable from the same web page where the solicitation document is downloadable. It shall be the sole responsibility of the vendor to obtain each of the separate documents. The vendor shall not be relieved of any responsibility for performance under the subsequent contract due to the failure of the vendor to obtain a copy of the separate documents.

INTRODUCTION AND BACKGROUND INFORMATION SECTION

Introduction:

Purpose: This document constitutes a request for competitive, sealed proposals for the provision of maintenance and support services for the existing Transportation Management System (TMS), including the MoDOT Management System, as set forth herein as set forth herein for the Missouri Department of Transportation (MoDOT) (hereinafter referred to as “state agency”).

Titles: Titles of paragraphs used herein are for the purpose of facilitating reference only and shall not be construed to infer a contractual construction of language.

Background and Historical Usage Information:

The Missouri Department of Transportation (MoDOT) requires complete support services including complete problem diagnosis resolution and repair of its Transportation Management System (TMS). Maintenance is based on the premise of multi-platform support, including support for applications running in either .NET or .NET Framework, written in C# using WinForms, ASP.NET MVC, Console applications, Windows Communication Foundation (WCF), and Windows.

TMS is comprised of several business systems made up of many applications/components including but not limited to: Adopt-A-Highway (Adopt a Highway, Adopt a Highway Map, Litter Pickup, NO MOre Trash, Sponsor a Highway), Asset Management Associative (Scenic Byway Inventories), Bridge Management System (Bridge Inventory and Inspections, Bridge Media Loader, NB Submittal), Design (Cultural Resource Management, Cultural Sites Maps, GPS Upload, Realty Asset Inventory, Right of Way Parcel Acquisition), Design RWPA (Right of Way Spatial Parcel Editing Program, Right of Way 1099 IRS Tax Processing Program), Intelligent Transportation Systems, Inventory Validation, MoDOT Management System (MMS), Outdoor Advertising (Billboard, Billboard Media Loader, GPS Upload, Junkyard, Junkyard Media Loader, Permit Invoicing, Permit Transfer), Railroad Management System, Routine Maintenance, Safety Management System (Crash Browser, Crash Summary, Intersection Expected Value Display, Statewide Average Crash Rates), SharePoint Document Management System, Security (TMS Historical Security, TMS Security), State of the System, STIP Management System (SIMS), Stormwater (BMP Inspection, BMP Inventory, Outfall, Outfall Inspection, Temporary BMP) Striping Inventory System (Striping Actuals, Striping Inventory, Striping Parameters, Striping Plan, Template Map), TMS Media, Traffic Management System (Flasher, Lighting, Signal, District Defined Types, Highway Capacity Interface, Permitting Site ID Maintenance, Traffic Segment, Hourly Volume, Traffic Information Segment Maintenance, Derived Traffic Information), Traveler Information System (Work Zone, OSOW), Travelway Features (Oversize Overweight Travelway, Curfews Inventory System), Travelway Lane, Travelway Asset Inventories (Rumble Strips, Guard Cables, Concrete Barriers, Highway Performance Monitoring, Soundwalls, Emergency Roadway Markers, Sign Structures), Travelway Management System (LRS, Travelway Overlapping Browser), and methods of integration with external systems (such as MoCARS, Financial Services, etc.).

PARAGRAPH ADDED PER RFP AMENDMENT 04

MoDOT’s most critical applications/components are SIMS, Bypass routes, MMS. None are public facing.

PARAGRAPH ADDED PER RFP AMENDMENT 04

The applications share the same database and deployments between applications can impact others.

PARAGRAPH ADDED PER RFP AMENDMENT 04

Data ownership is defined across applications sharing the same database in the following manner: different divisions are partners within TMS and own their data for their applications.

PARAGRAPH ADDED PER RFP AMENDMENT 04

Applications can be categorized by functional domains such as safety, electronic permitting, media, reporting, asset management, security, traffic, bridge, maintenance, and routine maintenance, and documentation is available for each of these domains.

PARAGRAPH ADDED PER RFP AMENDMENT 04

No application specific SLA's exist.

PARAGRAPH REVISED PER RFP AMENDMENT 04

Analysis and design of TMS began in 1995 as an effort to automate and consolidate many sources of data and applications into one integrated application with the core being the Location Referencing System (LRS). Once the LRS was established, a peripheral of applications was developed utilizing the LRS as its hub. Key business areas of Safety, Pavement, Bridge, Planning, Design, Right of Way, and Construction now had the ability of being logically linked to give the users an unparalleled capability of data integration and reporting. Development has progressed to the point where there are more than sixty (60) specific applications that comprise TMS. TMS is built as a highly modular system with components that are tightly coupled.

Document Management is another key area of TMS that has flourished, with more than 4,000,000 media items stored in its Oracle databases, users now have the ability to edit and associate images of various types with specific MoDOT assets.

TMS technical specifications:

Number of objects in each of four (4) transaction databases:

Tables – 3026 (Number of Oracle tables in the TMS database) Indexes – 3831 (Number of indexes used in the TMS database) Views – 1065 (Views of data group together to facilitate processing, faster access), eight (8) of which are materialized.

Functions - 269 (Pieces of code that may create a view, based on users input for specific data. Functions are used to boost performance and response time) Procedures – 123 Triggers – 94 Packages – 163 Sequences – 3462 Types – 10 Jobs – 80

Approximate number of TMS reports:

Crystal Reports - 420 COGNOS Reports –97

Support Metrics: The table below shows the majority of the current source code models and the results of a Visual Studio Code Metrics report. The report provides standard key metrics that will allow you to assess the code and the support that might be needed for the module.

Approximately 5,000 user profiles are in the TMS system.

PARAGRAPH ADDED PER RFP AMENDMENT 04

TMS is available to roughly 4,500 employees, with more than half of those staff rarely accessing the system.

The total hours of maintenance and support services has not exceeded 17,000 hours per year during the term of contract CT160408001. Additional work was required in the past five (5) years through the Statement of Work (SOW) process, formerly known as the Project Assessment Quotation (PAQ) process.

The average number of tickets varies based on the issue, project, or break-fix.

PARAGRAPH ADDED PER RFP AMENDMENT 04

Historical ticket volumes are identified in Attachment 3 – Historical Ticket Volumes. The TMS system is relatively stable and does not see high volumes of tickets. New application enhancements and rewrites of modules typically cause the most break/fix issues.

PARAGRAPH ADDED PER RFP AMENDMENT 04

Increase in demand for TMS support can occur due to weather events and ticket urgency can be expected close to calendar and fiscal year ends. Additionally, Statewide Transportation Improvement Program (STIP) can involve mandated work due prior to fiscal year end.

PARAGRAPH ADDED PER RFP AMENDMENT 04

MoDOT defines severity/priority levels for TMS tickets as follows: Development SLA's align with the Service Management Office as Priority 1 - Application is down and immediate response is needed. Priority 2 - The system is having problems, but most functions are still available (response should be urgent). Priority 3 - The system is working but a minor bug has been found, research and response are needed as time allows. Priority 4 - Work Efforts - This is the bulk of MoDOT’s efforts generally viewed as enhancements and updates. Priority 4 do not have a sense of urgency but may have agreed upon timelines based on contractor needs and availability.

PARAGRAPH REVISED PER RFP AMENDMENT 04

The first level of support is provided by MoDOT’s TMS Help Desk or IS (Information Services) Help Desk. State agency staff traditionally work M-F 7:30-4:30 and are rarely required to work outside those hours.

PARAGRAPH ADDED PER RFP AMENDMENT 04

After-hours work is generally for deployments during non-business hours. Regular deployments occur bi-weekly with 1-2 hours for deployment and testing. After hours calls for incidents average 45 minutes per call per month.

Approximately seventeen (17) team members from the current contractor manage the TMS under contract CT212017001.

MoDOT anticipates, but does not guarantee, the following system upgrades may occur within the next three (3) years.

The Travelways app may be updated to improve data collection, reporting, and updates.

Continued conversion of Web Applications to MVC framework.

Creation and integration of Power BI dashboards Integration into the new statewide ERP system.

The percentage of onsite services performed under the current contract, CT212017001, are estimated to be less than one percent (1%) for the entire length of the contract.

PARAGRAPH and SUBPARAGRAPHS ADDED PER RFP AMENDMENT 04 The Missouri State Data Center maintains the application servers, network, and storage required for the application environments.

MoDOT developers build the code locally, then use Azure DevOps pipelines to promote to Dev, SIT, UAT and finally Prod environments. Database changes are moved along with work requests through the pipeline in Azure DevOps by the database group.

Both the release pipelines for scheduled tasks and web applications running in a .NET environment include steps for transforming configuration files for settings specific to the environment. These steps vary between web vs console and .NET vs framework. Scheduled task release pipelines usually contain a step for inserting database passwords into configuration files. The passwords are stored in the pipeline as a secure variable put in by the middleware group.

PARAGRAPH and SUBPARAGRAPHS ADDED PER RFP AMENDMENT 04 MoDOT’s current deployment/release process for TMS changes is as follows: MoDOT developers work with the application owner to determine the best solution, establish a timeframe, and then build the solution in the DEV environment. The developer tests the solution and then deploys it to SIT. Once deployed in SIT, the developer informs the partner that the update is ready for testing and makes sure the partner has access. The application owner thoroughly tests the update and requests changes if necessary. The partner tests and approve changes prior to implementation in PROD. Application owners are ultimately responsible for deciding what changes are necessary, but application developers take the role of advisor to ensure the change does not cause unwanted or unsupported results. In the case of Windows updates and security updates, the developer works with the application owner to understand the impact and coordinate the change occurring with the least possible impact on users.

Standard Change Routine change that is operational in nature and occurs frequently.

May have an agreed upon standard maintenance window weekly/monthly.

Tasks are well known, communicated, and verified.

Involves limited configuration and implementation changes.

Overall risk is low and well understood with extensive testing and approval.

Requires short amount of time to accomplish.

May not include an outage, or the outage is brief.

A rollback plan is well known and reliable.

Hot Fix (Emergency) Needed to prevent an impending critical incident.

Used to resolve an active critical incident.

An incident is considered critical if the system is down, or degraded so severely that it is not usable, users can’t log in, or a high security vulnerability issue is present. This aligns with the Help Desk designation of a priority 1 incident.

These are higher risk and may not be fully tested but should be approved when practical.

A rollback plan is well known but may not be reliable as the previous code may have issues causing the incident.

These changes are considered critical bugs and should be rare with proper planning and testing during development.

Batch jobs and services are scheduled and deployments occur in MoDOT’s maintenance window(s) established with the current contractor.

PARAGRAPH and SUBPARAGRAPHS ADDED PER RFP AMENDMENT 04 TMS applications currently use Microsoft .NET Framework 4.8 or higher and .NET 8, with the system built using a combination of WebForms and ASP.Net Core Model View Controller (MVC) and incorporating DevExpress (DevEx) controls.

TMS is primarily using Webforms and DevEx controls for the application languages, but MoDOT has begun transitioning to MVC with several modules including Bridge and portions of the MoDOT Maintenance System. Separate branches for MVC modules have been created and integration between Webforms and MVC is currently seamless.

Webforms and various .net versions are the legacy technologies still in active use by MoDOT.

PARAGRAPH ADDED PER RFP AMENDMENT 04

MoDOT’s standards are documented in MoDOT’s best practices and application management plan. As applications are being modernized, updates to meet those standards are expected. When applications undergo major rewrites, standards are expected to be implemented, otherwise, as maintenance hours are available.

PARAGRAPH ADDED PER RFP AMENDMENT 04

The TMS application runs on Windows. Linux servers are used for Oracle DB and WebSphere. Middleware team at MoDOT is responsible for updating OS and middleware software to the most current version. There are no constraints identified. TMS currently has six (6) Dev servers, seven (7) SIT servers, and seven (7) Production servers.

PARAGRAPH AND SUBPARAGRAPHS ADDED PER RFP AMENDMENT 04

Background components such as WCF services, Windows Services, or batch processes are managed and monitored in production in the following manner:

Only two (2) services are being monitored with SolarWinds.

SolarWinds monitors server level metrics, Dynatrace is being made available but not active.

Logging is done directly through log directories, SolarWinds is used for diagnostics.

PARAGRAPH AND SUBPARAGRAPHS ADDED PER RFP AMENDMENT 04

Data Layer Interaction:

Individual applications primarily use their own dedicated Oracle schemas. However, some schema users are granted access to objects in other schemas when required for application functionality. For example, TMS and MMS each maintain their own dedicated schemas but have cross schema access where needed. Regarding “common Oracle tables,” the term can be a bit vague. Historically, TMS used the Secure schema and still relies on DataMart HR data. Whether these fall under “common Oracle tables” depends on how that term is being defined, but they do represent shared data sources that multiple applications may consume.

Access to data is controlled through user specific grants and environment-based permissions. MoDOT also uses a PL/SQL script that provides read only access to TMS where appropriate. In addition, an internal process governs how developers request and receive access, and MoDOT maintains oversight of the generic accounts used by applications. Each of these groups follows established standards to ensure consistent and secure data access practices.

Database changes are managed through the dedicated MoDOT database team, which follows its own established standards and procedures. All code deployments or database modifications are submitted as Azure DevOps work requests or SDP tickets and follow the MoDOT DB team’s review and approval process. Historically, developers also maintained their own versioning process with scripts for Oracle object creation (DDL), though details of that process may vary.

PARAGRAPH AND SUBPARAGRAPHS ADDED PER RFP AMENDMENT 04

Location Referencing System (LRS) Interaction:

MoDOT’s location referencing system (LRS) is a Geospatial Information Systems (GIS) based route system that is utilized to locate information. Technically MoDOT’s base LRS is not an actual Route Network in the true sense of a Network. MoDOT’s Transportation Management System (TMS) uses this singular route system as a basis of locating, referencing and associating data across all TMS sub-systems. The purpose of a singular LRS is so that any TMS data can be combined, segmented, tabulated and compared with any and all other TMS data. A Travelway is a unique integer that represents a unique route. This is used because name, route designation and direction are not unique. Different from many systems MoDOT has a Travelway for each direction of travel legally possible on a roadway (piece of pavement). For an undivided east-west facility, such as a route C, there is a travelway for the east direction and a different travelway for west. For each travelway MoDOT calculates continuous log miles (mileage) along each direction of travel, for the entire route. Interstate 70 East starts at the Kansas line a log mile 0 and continues to the Illinois state line to approximately logmile 2XX.XXX. Accordingly, Interstate 70 West begins at the Illinois state line at log mile 0 and continues to the Kansas state line to approximately log mile 2xx.xxx. And since 70 is divided these two lengths are not equal. At the time of writing 70 east is 250.172 and 70 west is 250.028 miles long. This type of mileage calculation is done for both divided and undivided routes alike.

MoDOT has standardized REST API's for LRS interaction but SOAP still exists. The transition from partial to full REST API is part of ongoing modernization.

TMS is based on a LRS System using logmiles but also has components with GPS calculations based on logmiles.

The current contractor has established a process via quarterly Travelway maintenance. In addition, an inventory validation tool exists with the expectation that users will correct data impacted by TWAY maintenance.

PARAGRAPH ADDED PER RFP AMENDMENT 04

Within TMS several applications share data used across applications using API's between systems and within the database. MoDOT is not aware of application-to-application dependencies.

PARAGRAPH ADDED PER RFP AMENDMENT 04

TMS has synchronous components for some data and hourly, nightly, and weekly batch processes for other data.

PARAGRAPH ADDED PER RFP AMENDMENT 04

Integration with TMS is handled through traditional request/response interactions and scheduled batch processes. There are currently no event‑driven or streaming‑based integration mechanisms in use.

PARAGRAPH ADDED PER RFP AMENDMENT 04

Quarterly Travelway maintenance has dependencies that are completed before other processes can be completed. Multiple daily processes to move data between applications occur to update application data.

PARAGRAPH ADDED PER RFP AMENDMENT 04

External system integrations that currently exist in TMS include ETL processes, batch jobs, API's into Fleet Focus, Time Reporting System, Aashtoware, MoCARS, Regis, SAM2, Lexus/Nexus, High Desert (Traffic data), ATMS (at the TMC level).

PARAGRAPH ADDED PER RFP AMENDMENT 04

There are no integrations outside of the MoDOT domain.

Current Contract Information:

A current contract exists for the products and/or services being obtained via this RFP. A copy of the contract can be viewed and printed from the Division of Purchasing Awarded Bid & Contract Document Search System located on the Internet at: https://purch.oa.mo.gov/bidding-contracts/awarded-bid-contract-document-search. In addition, all proposal and evaluation documentation leading to the award of that contract may also be viewed and printed from the Division of Purchasing’s Awarded Bid & Contract Document Search System. Please reference the Bid number RFPT30034902102017 or the contract number(s) CT212017001 when searching for these documents.

State Expenditures: The Missouri Accountability Portal (MAP) located on the Internet at: http://mapyourtaxes.mo.gov/MAP/Expenditures/ provides financial data related to the purchase of the services under the contract. Be sure to read the information provided in the site information and disclaimer links: https://mapyourtaxes.mo.gov/MAP/Help/MapExpendituresHelp.htm and https://mapyourtaxes.mo.gov/MAP/Help/MapExpendituresHelp.htm#disclaimer. Then search by the contract numbers shown above when searching for the financial information.

RFP Questions:

Buyer is Single Point of Contact for Solicitation: Vendors and their agents (including subcontractors, employees, consultants, or anyone else acting on their behalf) must direct all of their questions or comments regarding the RFP, the evaluation, etc., to the buyer indicated on the first page of this RFP. It is preferred that questions be emailed to the buyer.

Except as noted herein, vendors and their agents are instructed not to contact any other state employee regarding any of these matters during the solicitation and evaluation process. Inappropriate contacts are grounds for suspension and/or exclusion from specific procurements. Vendors can be sanctioned for unauthorized contact with any evaluator under 1 Code of State Regulation (CSR) 40-1.060(8)(G) and (H) available at http://www.sos.mo.gov/adrules/csr/csr.asp.

Minority Business Enterprise/Women Business Enterprise (MBE/WBE) and Service-Disabled Veteran Enterprise certification or subcontract questions should be directed to the Office of Equal Opportunity (OEO) at http://oeo.mo.gov.

Vendor is Responsible for Asking Questions About the RFP: It is the vendor’s responsibility to ask questions, request changes or clarifications, or otherwise advise the Division of Purchasing if the vendor believes that any language, specifications, or requirements are: (1) ambiguous, (2) contradictory or arbitrary, (3) violate any state or federal law or regulation, (4) restrict or limit the requirements to a single source, or (5) restrict or limit the vendor’s ability to submit a proposal.

Vendor Question Deadline: Every attempt shall be made to ensure that the vendor receives an adequate and prompt response. However, in order to maintain a fair and equitable procurement process, all vendors will be advised, via the issuance of an amendment to the RFP, of any relevant or pertinent information related to the procurement. All questions and issues should be submitted no later than ten (10) calendar days prior to the proposal closing date and time of the proposals. If not received prior to ten (10) calendar days before the proposal closing date and time, the Division of Purchasing may not be able to fully research and consider the respective questions or issues.

State’s Response to Vendor Questions: Upon the Division of Purchasing’s consideration of questions and issues, if the Division of Purchasing determines that changes are necessary, the resulting changes will be included in a subsequently issued RFP amendment(s); absence of such response indicates that the questions and issues were considered but deemed unnecessary for an RFP amendment. All vendors will be advised of any change to the RFP’s language, specifications, or requirements by a formal amendment to the RFP. There will be no posted written records of the questions/communications (i.e., formal question/answer document).

RFP is State’s Only Official Position: The only official position of the State of Missouri shall be that which is contained in the RFP and any amendments thereto.

Amendments:

If the Division of Purchasing determines that changes to the RFP are necessary, the resulting changes will be included in a subsequently issued RFP amendment(s) prior to the proposal closing date and time.

Glossary of Terms and Acronyms:

Whenever the following terms and acronyms appear in the RFP document or any amendment thereto, the definitions or meanings described below shall apply.

General Glossary, Acronyms, and Abbreviations:

Agency and/or State Agency means the statutory unit of state government in the State of Missouri for which the equipment, supplies, and/or services are being purchased by the Division of Purchasing (Purchasing). The agency is also responsible for payment, unless otherwise specified herein.

Amendment means a written, official modification to a solicitation or contract.

Attachment applies to all documents which are included with an RFP to incorporate any informational data or requirements related to the performance requirements and/or specifications.

Buyer means the procurement staff member of Purchasing.

Code of State Regulation (CSR) contains the current administrative rules of executive agencies of Missouri government. The regulations are arranged by agency rather than by subject.

Contract means a legal and binding agreement between two or more competent parties, for a consideration for the procurement of equipment, supplies, and/or services.

Contractor means a supplier, offeror, person, or organization who is a successful vendor as a result of an RFP and who enters into a contract.

Exhibit applies to forms which are included with an RFP for the vendor to complete and submit with their proposal prior to the specified closing date and time.

May means that a certain feature, component, or action is permissible, but not required.

Must means that a certain feature, component, or action is a mandatory condition.

Party refers to either the State of Missouri or the contractor as an entity that may enter into a contract pursuant to the terms herein.

Pricing Page(s) applies to the form(s) on which the vendor must state the price(s) applicable for the equipment, supplies, and/or services required in the RFP. The pricing pages must be completed and submitted by the vendor with the proposal prior to the specified proposal closing date and time.

Proposal Closing Date and Time and similar expressions mean the exact deadline required by the RFP for the receipt of sealed proposals.

Purchase Order means the authorized document issued by the state agency to the contractor indicating descriptions, quantities, and agreed prices for products and/or services.

Reasonable, Necessary or Proper as used herein shall be interpreted solely by the State of Missouri.

Request for Proposal (RFP) means the solicitation document issued by Purchasing to potential vendors for the purchase of equipment, supplies, and/or services as described in the document. The definition includes the following sections: Introduction and Background Information; Scope of Work; Terms and Conditions (“terms and conditions” and “Terms and Conditions” are used interchangeably throughout the RFP); General Contractual Requirements; and Vendor Submission, Evaluation, and Award Information; and the RFP Vendor Response Exhibits, Attachments, and Amendments of the RFP.

RSMo (Revised Statutes of Missouri) refers to the body of laws enacted by the Legislature which govern the operations of all agencies of the State of Missouri. Chapter 34 of the statutes is the primary chapter governing the operations of Purchasing.

Shall has the same meaning as the word must.

Should means that a certain feature, component and/or action is desirable but not mandatory.

State collectively referring to the state government and/or the agencies thereof.

Supplier has the same meaning as the word, vendor.

Vendor means the supplier, offeror, person, or organization that responds to an RFP by submitting a proposal with prices to provide the equipment,…