STATE 0000000391SL TMS Maintenance and Support Services.docx
DOCX document 261 KB Posted
- Solicitation number
- 300000264476331
- Issued by
- Missouri
About this file
This Request for Proposal (RFP) is issued by the State of Missouri Office of Administration, Division of Purchasing on behalf of the Missouri Department of Transportation (MoDOT) for maintenance and support services for the Transportation Management System (TMS). MoDOT seeks a qualified contractor to provide comprehensive maintenance and support services including problem diagnosis, software problem resolution and repair, technical support, minor enhancements, and programming services for the existing TMS, which comprises over 60 integrated applications managing transportation-related data across multiple business areas such as bridge management, safety, pavement, planning, design, right-of-way, and construction. The TMS infrastructure consists of four transaction databases containing 3,026 Oracle tables, 3,831 indexes, 1,065 views, and approximately 517 reports across Crystal Reports and COGNOS platforms. The proposal submission deadline is June 30, 2026 at 2:00 PM Central Time through the MissouriBUYS online portal. The contract period is three years effective from the notification to proceed, with the potential for two additional one-year renewal options. Proposals must be submitted electronically and include completed exhibits addressing technical qualifications, experience, methodology, pricing, and business compliance certifications.
The contractor shall provide all maintenance and support services at firm, fixed hourly rates specified in Exhibit C, with total maintenance and support hours not to exceed 17,000 hours per year. The contractor must have a minimum of two years of experience providing maintenance and support services for transportation-related applications and possess specific technical expertise in Oracle spatial databases, ESRI ArcGIS, PL/SQL, .NET development, Web Services, REST/SOAP APIs, Crystal Reports, and Power BI. The contractor is required to provide 24/7 on-call support, maintain background check compliance per MoDOT's requirements, and establish a dedicated leadership team with a minimum one-year leadership experience and support staff with one year of relevant technical experience. On-site services may be required at no additional charge beyond the stated pricing, with MoDOT providing necessary equipment, software, and network access. Additional programming services outside standard maintenance shall be procured through a Statement of Work (SOW) process with separate pricing. The incumbent contractor currently manages the TMS under contract CT212017001 with approximately 17 team members. All state data shall remain the property of Missouri and be stored exclusively within the United States, with the contractor obligated to maintain strict confidentiality and security protocols including 90-day security code scans for critical and external-facing applications and corrective action for high-threat vulnerabilities within 10 business days.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| STATE 0000000391SL,4 TMS Maintenance and Support Services.docx | DOCX document | |
| Attachment 3 - Historical Ticket Volumes.xlsx | XLSX spreadsheet | |
| STATE 0000000391SL,2 TMS Maintenance and Support Services.docx | DOCX document | |
| Attachment 1 - SOW Requirements.docx | DOCX document | |
| Attachment 2 - Federal Funds Requirements.docx | DOCX document | |
| STATE 0000000391SL,1 TMS Maintenance and Support Services.docx | DOCX document | |
| STATE 0000000391SL,3 TMS Maintenance and Support Services.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
State of Missouri Office of Administration, Division of Purchasing
Request for Proposal (RFP) for Transportation Management System (TMS) Maintenance and Support Services
| SOLICITATION NO.: |
| STATE 0000000391SL |
| SOLICITATION ISSUED ON BEHALF OF: |
| Missouri Department of Transportation |
| ISSUE DATE: |
| May 29, 2026 |
| CONTRACT PERIOD: |
| Effective Date of Contract Through Three (3) Years |
| REQUISITION NO.: |
| RR012600960 |
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:
| RFP Sections |
| Section 1 |
| Introduction and Background Information Section |
| Section 2 |
| Scope of Work Section |
| Section 3 |
| Terms and Conditions Section |
| Section 4 |
| General Contractual Requirements Section |
| Section 5 |
| Vendor Submission, Evaluation, and Award Information Section |
RFP Vendor Response Exhibits (Return these exhibits with the proposal)
| Exhibit A |
| Proposal Signature Page |
| Exhibit B |
| Proposal Submittal Checklist |
| Exhibit C |
| Pricing Page |
| Exhibit D |
| Technical Proposal – Experience of Organization and Past Performance |
| Exhibit E |
| Technical Proposal – Team Qualifications |
| Exhibit F |
| Technical Proposal – Methodology, Approach, and Work Plan |
| Exhibit G |
| Participation Commitment |
| Exhibit H |
| Documentation of Intent to Participate |
BUSINESS COMPLIANCE EXHIBITS
| Exhibit I |
| State of Missouri Tax Compliance |
| Exhibit J |
| Registration of Business Name with the Missouri Secretary of State |
| Exhibit K |
| Business Entity Certification, Enrollment Documentation, and Affidavit of Work Authorization |
| Exhibit L |
| Anti-Discrimination Against Israel Act Certification |
| Exhibit M |
| Services Outside the United States |
| Exhibit N |
| Employee/Conflict of Interest |
| Exhibit O |
| Federal Funding Unique Identity ID |
| RFP Attachments |
| Attachments (Separate Documents) (Do not return these documents with response) |
| Attachment 1 |
| Statement of Work (SOW) Process Requirements |
| Attachment 2 |
| Federal Funds Requirements |
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.).
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.
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.
| Maintainability Index |
| Cyclomatic Complexity |
| Depth of Inheritance |
| Class Coupling |
| Lines of Source Code |
| Lines of Executable Code |
| Number of CSHTML |
| AssetManagement |
| 70 |
| 525 |
| 1 |
| 128 |
| 7,227 |
| 1,671 |
| Bridge (BridgeInventory) |
| 70 |
| 10,375 |
| 5 |
| 454 |
| 81,699 |
| 23,318 |
| BridgeMVC |
| 74 |
| 10,454 |
| 4 |
| 513 |
| 124,237 |
| 25,091 |
| 121 |
| CodeTables |
| 75 |
| 2,614 |
| 5 |
| 273 |
| 22,657 |
| 5,971 |
| Common |
| 86 |
| 7,093 |
| 6 |
| 546 |
| 56,000 |
| 17,389 |
| CulturalSites |
| 70 |
| 407 |
| 5 |
| 173 |
| 5,623 |
| 1,187 |
| ElectronicPermitting |
| 66 |
| 472 |
| 1 |
| 166 |
| 10,787 |
| 3,348 |
| ElectronicPermittingExternal |
| 65 |
| 571 |
| 7 |
| 296 |
| 11,281 |
| 4,023 |
| ElectronicPermittingExternalLibrary |
| 88 |
| 56 |
| 3 |
| 12 |
| 291 |
| 63 |
| ElementReportUploads |
| 87 |
| 144 |
| 9 |
| 76 |
| 1,104 |
| 236 |
| Emailer |
| 68 |
| 112 |
| 1 |
| 43 |
| 760 |
| 319 |
| Features |
| 70 |
| 3,412 |
| 1 |
| 391 |
| 43,907 |
| 12,070 |
| Fleet |
| 74 |
| 1,594 |
| 5 |
| 220 |
| 14,174 |
| 3,664 |
| HP-1964 HPCommon |
| 74 |
| 9,798 |
| 4 |
| 276 |
| 52,584 |
| 16,305 |
| HP-1964 HPWeb |
| 92 |
| 8,960 |
| 5 |
| 870 |
| 56,577 |
| 15,023 |
| HP-1964 AccidentImport |
| 74 |
| 1,647 |
| 6 |
| 196 |
| 12,589 |
| 3,534 |
| HP-1964 HPWebservices |
| 69 |
| 548 |
| 3 |
| 128 |
| 6,032 |
| 2,296 |
| HP-1964 ImagesInterface |
| 73 |
| 51 |
| 1 |
| 28 |
| 823 |
| 281 |
| HP-1964 LocalAgenciesInterface |
| 72 |
| 48 |
| 1 |
| 50 |
| 467 |
| 119 |
| HP-1964 HPCommonTest |
| 69 |
| 36 |
| 1 |
| 26 |
| 301 |
| 132 |
| InventoryValidation |
| 68 |
| 249 |
| 5 |
| 132 |
| 4,173 |
| 999 |
| LRS |
| 75 |
| 1,692 |
| 5 |
| 238 |
| 15,040 |
| 3,996 |
| Maintenance |
| 77 |
| 5,611 |
| 5 |
| 314 |
| 7,550 |
| 9,883 |
| Media |
| 89 |
| 3,034 |
| 6 |
| 283 |
| 23,113 |
| 5,952 |
| MediaExtractor |
| 84 |
| 53 |
| 4 |
| 57 |
| 494 |
| 160 |
| MediaNightly_AsBuilt |
| 59 |
| 101 |
| 1 |
| 52 |
| 1,435 |
| 577 |
| MediaNightly_Global |
| 43 |
| 39 |
| 1 |
| 51 |
| 559 |
| 285 |
| MediaNightlyJob |
| 79 |
| 1,257 |
| 1 |
| 73 |
| 8,536 |
| 2,079 |
| MMSBusLayer |
| 81 |
| 24,339 |
| 4 |
| 617 |
| 146,673 |
| 38,625 |
| MMSWebApp |
| 73 |
| 16,688 |
| 7 |
| 1,153 |
| 135,402 |
| 54,152 |
| MMS (MVC) |
| 76 |
| 22,170 |
| 7 |
| 975 |
| 184,315 |
| 46,217 |
| 124 |
| RAI |
| 76 |
| 836 |
| 5 |
| 194 |
| 9,312 |
| 2,360 |
| RAICommon |
| 80 |
| 3,989 |
| 1 |
| 150 |
| 25,187 |
| 6,400 |
| Railroad |
| 74 |
| 7,175 |
| 5 |
| 261 |
| 54,538 |
| 13,710 |
| Reporting |
| 73 |
| 1,527 |
| 5 |
| 189 |
| 14,607 |
| 2,892 |
| RWPA |
| 68 |
| 1,219 |
| 1 |
| 197 |
| 17,021 |
| 3,761 |
| Safety |
| 75 |
| 1,124 |
| 5 |
| 193 |
| 11,194 |
| 2,465 |
| SecurityMaint |
| 77 |
| 775 |
| 1 |
| 145 |
| 8,599 |
| 2,099 |
| SIMS |
| 76 |
| 7,959 |
| 5 |
| 334 |
| 58,565 |
| 15,262 |
| STIPProjectLoad |
| 56 |
| 108 |
| 1 |
| 43 |
| 697 |
| 304 |
| Striping |
| 79 |
| 3,583 |
| 1 |
| 269 |
| 28,809 |
| 7,121 |
| TMSMedia |
| 79 |
| 293 |
| 5 |
| 159 |
| 2,691 |
| 546 |
| TMSMediaIndex |
| 68 |
| 68 |
| 3 |
| 53 |
| 588 |
| 238 |
| TMSModel |
| 80 |
| 23,459 |
| 3 |
| 359 |
| 150,147 |
| 35,507 |
| Traffic |
| 72 |
| 3,248 |
| 1 |
| 219 |
| 29,324 |
| 6,349 |
| TravelerInfo |
| 75 |
| 2,121 |
| 5 |
| 195 |
| 17,491 |
| 4,584 |
| TWAYMaintenance |
| 79 |
| 1,796 |
| 4 |
| 214 |
| 17,421 |
| 3,662 |
| 1,482,601 |
| 406,225 |
Approximately 5,000 user profiles are in the TMS 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.
The first level of support is provided by MoDOT’s TMS Help Desk or IS (Information Services) Help Desk.
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.
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, supplies, and/or services as required in the RFP document.
Accuracy of Background Information:
Although an attempt has been made to provide accurate and up-to-date information, the State of Missouri does not warrant or represent that the background information provided herein reflects all relationships or existing conditions related to this RFP.
****END OF INTRODUCTION AND BACKGROUND INFORMATION SECTION****
SCOPE OF WORK SECTION
General Requirements:
The contractor shall provide maintenance and support services including, problem diagnosis (troubleshooting), software problem resolution and repair, maintenance, other technical support services such as minor enhancements or modifications to the application, and reporting needs and other programming services, including application development work upon request by the Missouri Department of Transportation (hereinafter referred to as “MoDOT”, “agency”, or “state agency”) in accordance with the provisions and requirements stated herein and to the sole satisfaction of the state agency.
The contractor shall understand and agree that the contract shall not be construed as an exclusive agreement and further agrees that the State of Missouri may secure identical and/or similar services from other sources at any time in conjunction with or in replacement of the contractor's services.
Maintenance is based on the premise of multi-platform support; including support for .Net Framework Webforms application and .NET v8.0 or higher.
The contractor must provide the support personnel and be able to begin the performance of all services required by the contract within thirty (30) days after receiving notification to proceed from MoDOT.
The contractor shall understand and agree that when requesting services under the contract MoDOT reserves the right to accept or reject any of the contractor's consultant(s) if deemed to be in the best interest of MoDOT.
The contractor’s consultants must adhere to MoDOT and State of Missouri policies pertaining to acceptable use (Internet and electronic mail), facility and data security, press releases, and public relations.
After receiving notification to proceed from MoDOT, the contractor shall review the policies pertaining to acceptable use (Internet and email), facility and data security, press releases, and public relations with MoDOT’s IT Director or their designee.
Any work performed by the contractor that results in an application development solution that will be utilized by employees of the State, or the general public must be compatible with applicable provisions of the Americans with Disabilities Act and Federal Section 508 Accessibility regulations as specified by the state agency. Specific recommendations to attain compatibility must be documented and reviewed with the state contracting agency prior to any development activity being performed.
The contractor shall promptly respond to any complaint brought to its attention regarding the accessibility of the application solution programmed by the contractor pursuant to this contract agreement. The contractor shall resolve such complaints by bringing the developed application into compliance with the applicable Federal Section 508 Accessibility Standards and Regulations at no additional cost to the State.
The contractor may provide maintenance and support services and programming services required by the contract, on-site at MoDOT’s facility or off-site at the contractor’s facility, which must be located within the continental United States of America. However, the contractor must provide on-site services when determined necessary by MoDOT to meet any of the contract requirements. There shall be no additional charge for on-site services performed by the contractor, other than the fees stated in Exhibit A – Pricing Pages.
For any on-site work performed, MoDOT shall be responsible for providing necessary office equipment, access to a telephone, necessary computer/communications access, and project-specific software and desktop suite software if specified by MoDOT as a project requirement. If available and necessary, MoDOT may provide limited clerical support and supplies and printing facilities.
The state agency will be responsible for all MoDOT network components and computer hardware platforms. When MoDOT upgrades their software/hardware technical infrastructure to the next evolution/version of the software/hardware operating system or component (i.e., such as upgrading To the latest Windows iteration ), the contractor shall be required to provide any system modifications or additions necessary to enable the system to operate according to all mandatory technical and performance specifications as part of the maintenance and support services required herein. MoDOT will provide, at a minimum, a thirty (30) calendar day advance notice to the contractor of any technical infrastructure changes being implemented by the agency. MoDOT’s current computer technical architecture is as follows:
Oracle 19c and higher database Windows 11 Microsoft Office 365 Microsoft Windows Server 2024 Microsoft Visual Studio Current release Microsoft Visual Studio Team Services (VSTS), Azure DevOps GIT source repository DevExpress Version 24.2 or higher Crystal reports
Development Software:
Cognos 10.2 or higher, Crystal 25, Microsoft .Net Framework 4.8 and above, language C# v12, ESRI ArcGIS mapping, SQL Developer 23.1, ASP.Net Core, SQL Server Management Studio v20.2, ESRI ArcGIS Tools 10.6.1 and higher.
MoDOT will provide the contractor with remote access to the TMS via LogMeIn.
Contractor’s Obligation: Unless otherwise specified herein, the contractor shall furnish all material, labor, facilities, equipment, and supplies necessary to perform the services required herein.
Contractor and Contractor Team Requirements:
The contractor should have a minimum of two (2) years of experience providing maintenance and support services and computer programming for transportation-related applications.
The contractor must provide a leadership team to oversee the maintenance and support services and computer programming as required herein.
The leadership team members should have a minimum of one (1) year of experience in leadership roles.
The contractor must provide a working team made up of support staff, including developers. The support staff should have a minimum of one (1) year of experience similar to MoDOT’s current computer technical architecture. In addition, the contractor’s support staff must possess a minimum of one (1) year of experience in the following:
Business experience relevant to maintaining systems utilizing location referencing applications and data.
Experience with Oracle spatial database.
Experience with ESRI's ArcGIS Server, ArcGIS Portal and ArcGIS Pro;
Experience with PL/SQL Experience with Webforms, MVC web development in a .Net environment Experience with Web Services (SOA) Experience with REST/SOAP APIs.
Experience with Crystal Reports and Microsoft Power BI Experience with transportation related applications.
The contractor and the contractor’s personnel must follow all MoDOT Best Practices standards and procedures, including code and architecture walkthroughs.
The contractor must provide a dedicated Lead Analyst or similar position for all project work awarded via the Statement of Work (SOW) process.
Background Checks: Prior to providing services under the contract, the contractor must comply with MoDOT’s background check process:
Initiating an IT Consultant/Contractor Background Check:
HR emails the consultant/contractor and provides them with a MoDOT Consultant/Contractor Background Check Authorization Form and instructions to fill it out (see example below). The consultant/contractor is responsible for filling out the form and submitting it directly to the Senior HR Technician in the Human Resources Division’s Employment Section. In addition, the consultant/contractor will need to visit the MSHP website and conduct a name-based background check through their Missouri Automated Criminal History System (MACHS), and then return the results to the HR Employment Section. The consultant/contractor is responsible for paying for the MSHP background check. As of 12/31/2025, the processing fee is $15.
Example email sent by HR: Consultants will need to fill out the attached Consultant Background Check Authorization Form as well as provide us with a name-based background check. Contractors are responsible for providing MoDOT with their background check results. Please go here to run your name-based background check. You will receive the results in your personal email, and they will need to be sent to me at the following email address matthew.fick@modot.mo.gov. Once you have completed the authorization form as well as your name search background check, please forward both documents to me. Please let me know if you have any questions.
NOTE: Plan for this process in your project timeline. It is fully dependent on the responsiveness of the contractor/consultant and the MSHP. A background check will typically take 5-7 business days for MSHP to process AFTER it is received from the contractor. HR will usually follow up within 2 weeks if the contractor does not forward the MoDOT Consultant/Contractor Background Check Authorization Form and the MSHP background form.
Step 3: The HR Employment Section will email the IS-Help Desk, the Project Manager, and the responsible IS Supervisor when the individual passes the background check and marks the consultant/contractor eligible for hire. This email should include a personal or vendor-related email address for the individual being hired. If the individual DOES NOT pass the background check, the HR Employment Section will notify the Project Manager and IS Supervisor, as well. This would require MoDOT to select a new consultant/contractor and begin the background check process again.
TMS Maintenance and Support Requirements:
The contractor shall provide maintenance and support services for all existing TMS components (e.g. the Travelways System, the Roadway Striping Program, etc.) as required herein. In the event new TMS components are added and when features are added, functionality is modified, or improvements are made to existing components, the contractor shall provide maintenance and support services for such added components, features, functionality, and improvements.
The contractor shall provide maintenance and support services included in the TMS Maintenance and support Requirements for actual hours worked per month detailed in Section A.1 of Exhibit A.
The hours worked by the contractor’s staff shall be tracked via MoDOT’s Service Desk Plus ticketing system; therefore, the contractor’s staff must enter time worked at the end of every week. Thus, allowing MoDOT to know the balance of work hours available.
The total hours for maintenance and support services shall not exceed 17,000 hours per year.
MoDOT reserves the right to restrict the hours consumed per month with prior notification.
The TMS maintenance and support hours will be used for operational support and break/fix changes.
The contractor will develop and maintain a current software development lifecycle for the TMS with recommendations for implementation sent to MoDOT quarterly.
The contractor’s maintenance and support services must include on-call (i.e., telephone, electronic support, etc.) support services twenty-four (24) hours per day, seven (7) days per week, and provide Problem Diagnosis Resolution and Repair of the TMS with the appropriate personnel responsible for specific areas of TMS.
Onsite support services may be required in emergency situations and as otherwise required by MoDOT.
Maintenance and support services including problems, diagnosis, resolution, and repair entries shall be managed and prioritized via a MoDOT-supported tracking system.
The contractor’s support staff for the TMS maintenance shall provide support services on demand as required by TMS management activities, which include but are not limited to:
Validate changes made to the Roadway Network Coverage.
Resend tables to Oracle.
Execute Travelway Maintenance Interface to apply ArcGIS updates to the Oracle database.
The contractor shall produce and maintain during the term of the contract, and for a period of five (5) years thereafter, detailed technical records with respect to all maintenance services performed under the contract, including but not limited to engineering notebooks, development commentary, flow charts, logic diagrams and other materials related to the system (the “Technical Records”). The contractor shall provide MoDOT with copies of the Technical Records.
The contractor shall not allow any person or entity to have remote access to the TMS other than those individuals whom MoDOT has consented in writing to allow access to (“Authorized Personnel”). The contractor shall take appropriate steps to ensure that all Authorized Personnel who have access to the TMS shall use such access only for the purpose of correcting defects in the system or providing updates or enhancements to the system. The contractor shall take appropriate steps to ensure that all Authorized Personnel comply with this restriction, including but not limited to having such persons execute a written agreement to that effect.
The contractor shall take such steps as are necessary to ensure that only Authorized Personnel have access to the TMS.
The contractor shall provide support services for reporting errors and malfunctions and troubleshooting problems with the TMS. The contractor’s support services shall, at a minimum, include the following services:
Assistance related to questions on the use of the subject software.
Assistance in identifying and determining the causes of suspected errors or malfunctions in the software.
Advice and programming services on fixes or workarounds for identified errors or malfunctions, where reasonably available.
Information on errors previously identified by MoDOT and reported to the contractor.
Advice and services on the completion and authorization of help desk tickets describing the problem with the software for the contractor.
Error and Malfunction Service: Within two (2) business days of receiving oral or written notification by MoDOT of identified errors or malfunctions in the software, the contractor shall either:
Provide MoDOT with code correction to the software error or malfunctions. Each code correction shall be made available in the form of either a written correction notice or machine-readable media and shall be accompanied by a level of documentation adequate to inform MoDOT of the problem resolved and any significant operational differences resulting from the correction that is known by contractor, or
Provide MoDOT with a written response describing the contractor’s then-existing diagnosis of the error or malfunction and generally outlining the contractor’s then-existing plan and timetable, subject to MoDOT’s approval, for correcting or working around the error or malfunction.
Maintenance Release Services: The contractor shall provide error corrections and maintenance releases to the TMS that have been developed by the contractor at no additional cost to MoDOT. Such releases shall be licensed to and owned by MoDOT, excluding any 3rd Party software tools or copyrighted 3rd party software, pursuant to the terms and conditions of this contract. Each maintenance release shall consist of a set of programs and files made available in the form of machine-readable media and shall be accompanied by a level of documentation adequate to inform MoDOT of the problem(s) resolved including any significant differences resulting from the release that are known by the contractor. The contractor agrees and shall provide each maintenance release of the software that shall be compatible with the then-current MoDOT’s computer system on which the production TMS is installed.
The support services provided by the contractor for Problem Diagnosis and Repair shall at a minimum include the following:
Research of problems and error messages.
Resolution of problems within a reasonable amount of time for size and complexity of task as determined by project manager.
Restoration of original functionality.
Logging of problems and documentation of solutions.
Documentation updates.
Preventive maintenance shall include:
Small modifications to retain or restore original functionality.
Production monitoring to detect errors as required.
Regular updates to TMS for security and modernization including 3rd party dependencies used within TMS, such as DevEx, ESRI products, and code languages.
Coordination with other IS groups if other services are required.
Current status reports as requested.
Research performed as requested.
Impact Analysis on data dependent systems to determine the effect of TMS modifications on other dependent systems.
Security Code scans must be ran every 90 days for all critical and external facing web applications. Corrective action must be taken for all High Threat vulnerabilities within 10 business days. The system must maintain an overall security scan score of at least 90 using the static scan action.
At a minimum, the following TMS applications require support:
Adopt A Highway, Sponsor A Highway, No MOre Trash, and Litter Pickup programs.
Maintains data related to the MoDOT Adopt a Highway program where a group or individual can adopt a section of roadway in Missouri for the purpose of picking up litter next to the roadway. It also includes data related to the MoDOT Sponsor a Highway program where groups, organizations and businesses can sponsor a highway in the Kansas City and St. Louis areas and pay a private company, Adopt-A-Highway Litter Removal Service of America, Inc., to clean up litter and complete other activities on their behalf.
Traveler Information System, including Work Zones, Over Size Overweight Restrictions (OSOW), and Unreported Work Zones.
Maintains work zone information displayed on the Traveler Information Map. This includes physical work that is performed on a roadway that is maintained by MoDOT that will result in no delays to traffic, possible delays to traffic, the expectation of delays in traffic, or will cause all lanes to be closed on the travelway.
TMS Media Provides the ability to upload and maintain photos, PDF files, Word documents, and Excel files related to a specific TMS inventory. These files are mostly stored in an Oracle database and can be stored in SharePoint or a file server. Metadata that describes these files, called tags, are also stored such as the document type, media date, district, county, and travelway. Provides the ability to search media documents that have been entered in various TMS inventories and search based on the media's related tag data.
Safety Data Management Program Lists of accidents that have been entered by the Highway Patrol by travelway, begin and end dates, crash number, intersection number, etc. Allows the ability to view the crash images, display them on a map, etc. Displays totals of various criteria of accidents that have been entered by the Highway Patrol such as fatal, serious injury, minor injury, property damage only, type of accident, etc.
Striping Management Program Highlights and maintains travelways that will be striped for a given year. As an example, major routes are striped every year and others are striped every other year. These can be modified as needed. Maintains the data related to the process used to plan and manage the annual Striping Program. Identifies the travelways that are planned to be striped for the year. Maintains the paint striping inventory on MoDOT travelways. This includes solid lines, skip lines, paint color, type of paint used, date last striped, etc.
TMS Security Application used to manage users, user access, roles and applications functions in TMS.
TMS Outdoor Advertising Maintains data related to the billboards, billboard permits, inspections and bond tracking in Missouri including the transfer of billboard permits between owners.
TMS Cultural Resource Management System Maintains data to track archaeological sites, significant cemeteries/grave sites, and similar properties that are within (or in some instances immediately adjacent) to MoDOT right of way.
TMS Stormwater MoDOT is regulated under a National Pollutant Discharge Elimination System (NPDES) storm water permit that requires MoDOT to develop and implement a comprehensive program to prevent pollution of surface waters resulting from storm water runoff from MoDOT’s system. The Stormwater system maintains data related to the Best Management Practices (BMPs) used to treat stormwater entering the storm sewer system. An example is a basin.
TMS Traffic Permitting Provides Permit Application entry and maintenance for work on MoDOT's Right of Way from entities external to MoDOT, such as a utility company. Examples of permits include construction of driveways, landscaping, irrigation installation, tree removal, traffic control, utility installation.
TMS Travelway Features System Generic application that allows setup and maintenance of Features along MoDOT’s roadways. provides maintenance for 12 data inventories within the asset management application including Concrete Barrier, Guard Cable, Rumble strips, and Soundwall.
TMS RMS - Railroad Management System Maintains data related to Railroad Crossings on both MoDOT and non-MoDOT maintained travelways, Projects related to Railroads, Line Segments, Complaints, Incidents, Inspections, and FRA Submissions.
TMS Bridge Management System Maintains an inventory of bridges within the State of Missouri. Information regarding ratings, postings, and inspection data is collected and maintained
TMS SIMS (STIP (Statewide Transportation Improvement Program) Information Management System) SIMS supports the Statewide Transportation Improvement Program (STIP) which is prepared annually. The STIP identifies construction, scoping and Right of Way projects MoDOT will undertake in the next five years.
TMS Traffic Management System Maintains data related to flashing traffic lights, traffic signals, and traffic lights. The data includes the travelway, log mile, flasher color, who maintains the traffic light, etc. Provides an interface to input data into the Federal Highway Administration's Highway Capacity Software using an XML file.
TMS Travelways Management System Provides a method in TMS applications to search/add/update the associated data inventory by travelway and log miles using various methods such as travelway name, travelway number, city, planning org, GPS, intersecting travelway, bridges, county lines, etc.
Realty Asset Inventory Program Maintains data related to MoDOT's Reality Assets including parcels and leases.
Right of Way Parcel Acquisition Program Maintains data related to the acquisition of parcels of land such as easements, deeds, appraisals, and condemnation. Provides the ability to mass load media items related to As Built plans. This allows the partner to upload plans from a spreadsheet.
Right of Way Spatial Parcel Editing Program Application that allows the creation of a shape that depicts the boundaries of a land parcel.
MoDOT Management System The MoDOT Management System (MMS) was designed as a web-based program for capturing, locating, and reporting data related to all maintenance activities, including winter operations, materials, equipment, and labor. It also serves as safety incident reporting software and contains the following modules: Daily Journal, Work Plan, Budget, My Area, Fleet, Results, Ladder/License/Leave, Reports, and Safety Management.
The contractor support staff for all TMS system development shall provide the following support services on demand as required by TMS management activities.
Analyze, estimate, confirm requirements, code, test, stage for system test, all fixes, and Service Desk Plus items that are deemed support.
Maintain and update existing reports in Crystal Report, Cognos reports and Power BI reports.
Maintain and update ESRI GIS services on existing tables as needed for mapping purposes.
Maintain and update online and batch applications as needed.
Maintain and update production data as needed.
The contractor’s support staff for the Travelways System shall provide support services on demand as required by TMS management activities, which shall include but not be limited to:
Execute the nightly refresh.
Support Travelway Associative Maintenance online application including Data Quality Assurance (This application is used to maintain Functional Class, Federal System Class, State System Class, Speed limit and related items).
Support Lane Maintenance application.
Support Travelway maintenance.
Location Referencing Point and Click applications and maps.
The contractor’s support staff for the Bridge Program shall provide Problem Diagnosis Resolution and/or Repair support services on demand as required by TMS management activities, which shall include but not be limited to:
National Bridge Inventory (NBI) Submittal Process – (Approximately 1 client and 1 server applications).
BridgeKey Interface - to input load rating and truck route information into TMS.
MOBIS - Missouri Bridge Inspection System.
Bridge Key Report Management.
The contractor’s support staff for the Outdoor Advertising (Billboard, Junkyard and Scenic Byway Inventories) System shall provide Problem Diagnosis Resolution and/or Repair support services on demand as required by TMS management activities, which shall include but not be limited to:
ODA Junkyard Year End (Yearly) ODA Monthly SQL data reset as needed ODA Crystal Report correspondence templates modified as needed ODA imaging production SharePoint folders and data modified as needed ODA media loaders modified as needed ODA customer invoicing / mass mailing applications modified as needed
The contractor’s support staff for the Oversize Overweight Travelway Curfews Inventory System shall provide Problem Diagnosis Resolution and/or Repair support services on demand as required by TMS management activities, which shall include but not be limited to:
Biannual (Memorial & Labor Day) SQL data reset.
The contractor’s support staff for the Right of Way 1099 IRS Tax Processing Program shall provide Problem Diagnosis Resolution and/or Repair support services on demand as required by TMS management activities, which shall include but not be limited to:
Produce and export 1099 data files for the Office of Administration tax forms.
The contractor’s support staff for the Safety Management System shall provide Problem Diagnosis Resolution and/or Repair support services on demand as required by TMS management activities, which shall include but not be limited to:
Each month there are certain safety processes and applications that need to be executed, the monthly accident conversion processes Missouri State Highway Patrol (MSHP) accidents and locates them in TMS.
Programs are executed after each Travelway Maintenance to ensure accident data integrity as well as accident locations.
Creating Statewide Average Accident Rates batch (Annual).
Intersection Accident Expected Values batch (Annual).
Accident Statistics Manual batch (Annual).
Maintain Safety online and batch applications, including the Missouri Crash Analysis Reporting System (MoCARS) application used by MoDOT personnel.
Collision Diagram applications.
The contractor’s support staff for the Traffic section shall provide Problem Diagnosis Resolution and/or Repair support services on demand as required by TMS management activities, which shall include but not be limited to:
Annual Average Daily Traffic (AADT) projections batch (Annual).
Maintain the interface with FMS for utility costs for Traffic Signals, Flashers and Lighting inventory.
Maintain Work Zone hourly volume application for the hourly counts.
The contractor’s support staff for the Nightly Refresh System shall provide Problem Diagnosis Resolution and/or Repair support services on demand as required by TMS management activities, which shall include but not be limited to:
Applications, packages, procedures, and views modified as needed.
Maintenance of database trigger objects.
History creation and Safety updates (Annual).
The contractor’s support staff for the TMS Reporting System shall provide Problem Diagnosis Resolution and/or Repair support services on demand as required by TMS management activities for all existing TMS reports, which shall include but not be limited to:
Expose spatial data from an ArcGIS server as needed.
Web Location Book.
Create MXDs/MSDs as needed.
The contractor’s support staff for SIMS shall provide Problem Diagnosis Resolution and/or Repair support services on demand as required by TMS management activities, which shall include but not be limited to:
Maintain the SIMS draft and final annual save down process.
Programming Services Requirements:
When required by MoDOT, the contractor shall provide programming services for customization and new functionality development of the TMS application outside of the contract requirements included herein.
Programming services, when required by MoDOT, shall be accomplished through the Statement of Work (SOW) process as described in the Statement of Work (SOW) Requirements section of the RFP, or by using remaining maintenance hours. The contractor should have the following processes in place to manage and control the project:
Project tracking and reporting the progress of the project;
Scope control mechanisms;
Strategies for staying on track with the project schedule especially when there is a risk of potentially not meeting agreed upon deadlines.
Milestone completion reporting/acceptance sign off procedures;
Issue resolution;
Quality assurance procedures and how often or when QA is performed during a project;
Staff performance monitoring;
Project staff transition or replacement; and Measures taken to ensure security and confidentiality of all data.
The programming services may be performed off-site at the contractor’s facility within the continental United States of America.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .