RFP 202510141 Traffic Count SaaS_Final (1).docx
DOCX document 724 KB Posted
- Attached to
- Traffic Count Software as a Service (SaaS) State and local contract opportunity
- Solicitation number
- RFP - 17A - 202510141
- Issued by
- Maine
About this file
This is a Request for Proposals (RFP) issued by the Maine Department of Transportation's Traffic Engineering Division-Traffic Monitoring Section seeking a Traffic Count Software as a Service (SaaS) solution to support statewide traffic data collection and analysis. The Department operates approximately 130 Continuous Count Sites (CCS), 16 Weigh in Motion (WIM) sites, and currently processes 5,000-7,000 portable Short Duration Counts (SDCs) annually, with potential expansion to 12,000 portable counts. The solution must support data collection, processing, quality control, scheduling, and reporting for multiple equipment types including Gridsmart, Miovision, Rekor, Currux, ECM HERA, ECM HESTIA, and Kistler Data Logger devices. The Department also plans to add 400-500 additional CCS sites and up to 500 Continuous Turning Movement Sites (CTMs). Questions must be submitted by November 17, 2025 at 11:59 p.m. local time, and proposals are due by December 3, 2025 at 11:59 p.m. local time via the Vendor Self Service (VSS) portal. The contract term includes an initial period from January 10, 2026 through March 9, 2029, with two optional three-year renewal periods extending potential contract duration through March 9, 2035. The Department anticipates making one award.
The cost proposal will be scored using a mathematical formula whereby the lowest bid receives 30 points with subsequent bids scored proportionately lower. Payment terms are net 30 upon receipt of accurate invoices. The incumbent vendor is Drakewell Inc., which currently provides traffic data analysis and asset management software. The solution must include hosting services, implementation services (including configuration, data conversion, training, and deployment support), and data export services at contract termination at no additional charge. The vendor must convert current and up to ten years of historical traffic count data into the new system and support federal reporting requirements including Highway Performance Monitoring System (HPMS) and Traffic Monitoring Analysis System (TMAS) submissions. The contract is subject to Federal Funding Contract Rider D due to federal funding sources. Proposal evaluation is based on a 100-point scale: 20 points for organizational qualifications and experience, 50 points for proposed services and technical assessment, and 30 points for cost proposal. The Department reserves the right to request vendor demonstrations of the top-scoring proposals prior to final award determination.
View the file
Other files for this state and local contract opportunity
Show all 50
Traffic Count Software as a Service (SaaS) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
STATE OF MAINE
Department of Transportation Traffic Engineering Division-Traffic Monitoring Section
RFP# 202510141
Traffic Count Software as a Service (SaaS)
RFP Coordinator
| NAME: |
| Robert Dwyer |
| TITLE: |
| Contract Grant Specialist |
| EMAIL: |
| Robert.Dwyer@maine.gov |
Submitted Questions Due Date
November 17, 2025, no later than 11:59 p.m., local time
| Proposal Submission Deadline |
| DATE: |
| December 3, 2025, no later than 11:59 p.m., local time. |
| TO: |
| Vendor Self Service System |
TABLE OF CONTENTS
Page
| PUBLIC NOTICE |
| 3 |
| RFP DEFINITIONS/ACRONYMS |
| 4 |
| PART I INTRODUCTION |
| 8 |
A. PURPOSE AND BACKGROUND
B. GENERAL PROVISIONS
C. CONTRACT TERM
D. NUMBER OF AWARDS
| PART II SCOPE OF SERVICES TO BE PROVIDED |
| 11 |
| PART III KEY RFP EVENTS |
| 12 |
A. VENDOR SELF SERVICE SYSTEM (VSS)
B. QUESTIONS
C. AMENDMENTS
D. PROPOSAL SUBMISSION
| PART IV PROPOSAL SUBMISSION REQUIREMENTS |
| 14 |
| PART V PROPOSAL EVALUATION AND SELECTION |
| 17 |
A. EVALUATION PROCESS – GENERAL INFORMATION
B. SCORING WEIGHTS AND PROCESS
C. NEGOTIATIONS
D. SELECTION AND AWARD
E. APPEAL OF CONTRACT AWARDS
| PART VI CONTRACT ADMINISTRATION AND CONDITIONS |
| 19 |
A. CONTRACT DOCUMENT
B. STANDARD STATE CONTRACT PROVISIONS
| PART VII RFP APPENDICES AND RELATED DOCUMENTS |
| 21 |
APPENDIX A – PROPOSAL COVER PAGE
APPENDIX B – RESPONSIBLE BIDDER CERTIFICATION
APPENDIX C – QUALIFICATIONS and EXPERIENCE FORM
APPENDIX D – SUBCONTRACTORS FORM
APPENDIX E – TECHNICAL ASSESSMENT FORM
APPENDIX F – PROPOSED SERVICES FORM
APPENDIX G – PROPOSED SERVICES REQUIREMENTS WORKSHEET
APPENDIX H – COST PROPOSAL FORM
APPENDIX I – DATA CONVERSION DATA SETS
APPENDIX J – LRS METADATA FOR STATIONS
APPENDIX K – FACTOR GROUP AND TYPES
APPENDIX L – HPMS VALIDATION RULES
APPENDIX M – HPMS VEHICLE MIX SUMMARY
APPENDIX N – FEDERAL FUNDING CONTRACT RIDER D
APPENDIX O – RFP SUPPLEMENTAL FILES
PUBLIC NOTICE
State of Maine Department of Transportation
RFP# 202510141
Traffic Count Software as a Service (SaaS)
The State of Maine is seeking proposals for Traffic Count Software as a Service.
A copy of the RFP and all related documents can be obtained through Vendor Self Service (VSS): https://mevss.hostams.com/PRDVSS1X1/AltSelfService
Proposals must be submitted to the Office of State Procurement Services, via Vendor Self Service (VSS). Proposal submissions must be received no later than 11:59 p.m., local time, on December 3, 2025. Proposals will be opened the following business day.
RFP TERMS/ACRONYMS with DEFINITIONS
The following terms and acronyms, as referenced in the RFP, have the meanings indicated below:
| Term/Acronym |
| Definition |
| AADT |
| Annual Average Daily Traffic- The total yearly traffic volume on a given highway segment divided by the number of days in the year. AADTs are expressed in vehicles per day (VPD) and are calculated to compare year-to-year counts. |
| AASHTO |
| American Association of Highway and Transportation Officials- Liaison between State DOTs and the Federal government. |
| Axle Correction Factors |
| Calculation based on classification data to factor volume counts. |
| CCS |
| Continuous Count Site – Count Stations where traffic volumes and/or classification data are collected on a continuous, year-round basis. |
| Confidentiality |
| Preserving authorized restrictions on information access and disclosure, including means for protecting confidential or sensitive information. A loss of confidentiality is the unauthorized disclosure of information. |
| Count Station |
| A location for which traffic counts are, or have been, recorded. This may be a Continuous Count Site (CCS) or the location of a Short Duration count (SDC). These are represented by 12-digit identifiers. |
| CTM |
| Continuous Turning Movement Site – Count Station where traffic volumes and/or classification movements at an intersection are monitored on a continuous, year-round basis. |
| Data Classification |
| The process of risk assessment of data. Refer to Appendix E (Technical Assessment Form) for the Data Classification process (see also “PII Confidentiality Impact Level”). |
| Design Hour Volume (K-factor) |
| The Peak hour or the hour during the day when traffic is busiest. |
| Directional Factor |
| The percentage of vehicles traveling in the peak direction during the high hour. |
| Department |
| Department of Transportation. |
| Drakewell |
| Traffic data analysis and asset management software. |
| Factor Groups |
| Seasonal factors derived from CCS applied to sections of road to create AADT. |
| FFC |
| Federal Functional Class- The process by which rural and urban streets and highways are grouped into classes, such as arterials, collectors, and local roads, according to the character of the service they provide in the regional network of roads. |
| FHWA |
| Federal Highway Administration |
| HPMS |
| Highway Performance Monitoring System- The HPMS is a federal program designed to collect information on the nation’s highway system, administered by the FHWA. |
| LRS (METRANS) |
| Linear Reference System- The Department’s system for maintaining its transportation network locations and location relationships as well as related asset information. The Department currently utilizes Bentley AssetWise Asset Lifecycle Information Management (ALIM) and refers to the system as METRANS. |
| OIT |
| The State of Maine Office of Information Technology, also known as MaineIT. |
| Peak Directional Distribution (D-Factor) |
| The directional distribution factor. It is the proportion of traffic traveling in the peak direction during a selected hour, usually expressed as a percentage. Generated using traffic count data. |
| Peak Hour Percent of AADT (K-Factor) |
| Percentage of AADT occurring in the peak hour of traffic flow. Generated using traffic count data. |
| Percent SU during peak hour |
| Percentage of AADT for Single Unit Trucks during peak hour of flow. Generated using traffic count data. |
| Percent Combinations |
| Percentage of AADT that is Combination Unit Trucks. Generated using traffic count data. |
| PII (Personally Identifiable Information) |
| Data that is maintained by an agency that could potentially identify a specific individual and needs to be protected in accordance with state and/or federal law, including (1) any information that can be used to distinguish or trace an individual‘s identity, such as name, social security number, date and place of birth, mother‘s maiden name, or biometric records; and (2) any other information that is linked or linkable to an individual, such as medical, educational, financial, and employment information. Refer to Appendix E (Technical Assessment Form). The Vendor will not be required to retain any PII for this RFP. |
| PII Confidentiality Impact Level |
| The PII confidentiality impact level—low, moderate, or high—indicates the potential harm that could result to the subject individuals and/or the organization if PII were inappropriately accessed, used, or disclosed. (NIST SP 800-122). Refer to Appendix E (Technical Assessment Form). PII is evaluated to determine its confidentiality impact levels, so that appropriate safeguards can be applied to the PII. |
| RFP |
| Request for Proposals |
| RPO |
| Recovery Point Objective- The amount of data the system can afford to lose following an outage without causing significant harm to the operations. |
| RTO |
| Recovery Time Objective- The amount of time within which the system must be restored following an outage to prevent a significant loss of data. |
| SaaS |
| Software as a Service - A software distribution model in which a third-party vendor hosts an application and makes the application available to customers via the Internet. |
| Schedule ID |
| Schedule ID is a unique identifier given to each scheduled count instance. |
| SDC |
| Short Duration Counts- Short term traffic counts performed within 96 hours or less. These are portable coverage counts collected each year (April to November) by both State count crews and external consulting firms for a specific road segment to develop AADT. |
Short Duration Counts include the following: Vehicle volume, classification (axle or length), speed, weight, lane occupancy, turning movements, bike and pedestrian counts or combination of any of these.
| Special Studies Counts |
| These are Short Duration Counts collected when the Traffic Monitoring Section of the Department receives special studies requests from other sections/units each year. While these counts are performed for various purposes, the data collect is the same as Coverage Counts. The number of requests can vary each year. |
| State |
| State of Maine |
| State Data |
| Any information originating with the State, regardless of form or medium of disclosure (e.g., verbal, observed, hard copy, or electronic) or source of information. It includes any information concerning the State’s information technology infrastructure, systems and software and procedures; and information originating with the State in the course of using and configuring the Services provided under the contract. It includes any sensitive information held by the State that may be protected from disclosure pursuant to a federal or state statutory or regulatory scheme intended to protect that information, or pursuant to an order, resolution or determination of a court or administrative board or other administrative body. |
| TMAS |
| Traffic Monitoring Analysis System- FHWA reporting software for CCS data. |
| Traffic Count Database |
| The Department’s MS ACCESS database containing selected traffic data products, current and historical. |
| Traffic Counters/Recorders |
| A device for the automatic collection of traffic data via vehicle sensors. Data types may include traffic volume, vehicle classification, speed, weight, gap, and headway. Vehicle sensors may include pneumatic tubes, radar, video, inductive loops, and piezoelectric sensors. This RFP uses the terms Traffic Counters and Traffic Recorders interchangeably. |
| UI |
| User Interface- An application space that allows human users to interact with systems to make the user’s experience simple and intuitive. |
| Vendor Self Service System (VSS) |
| The Vendor Self Service System (VSS) web portal provides vendors with a single-entry point to register, identify the commodities/services that their company provides, look for business opportunities, and respond to solicitations. |
| WIM |
| Weigh In Motion Site – Count Stations where traffic weights and classification are monitored on a continuous, year-round basis. |
State of Maine Department of Transportation Traffic Engineering-Traffic Monitoring Section
RFP# 202510141
Traffic Count Software as a Service (SaaS)
PART I INTRODUCTION
A. Purpose and Background
The Maine Department of Transportation (Department) is seeking proposals for Traffic Count Software as a Service (SaaS) as defined in this Request for Proposals (RFP) to support the Department’s Traffic Monitoring Section annual gathering of traffic count data to monitor traffic flow and changes in traffic patterns. The Section operates Continues Count Sites (CCS) and Short Duration Count (SDC) programs. The CCS program gathers count data on a continuous, year-round basis. The SDC program collects count data during the count season between April and November each year as well as some additional SDC requests collected during the off season. For the 2025 count season, the Department’s Traffic Monitoring Section utilized Drakewell Inc.’s traffic count solution under an existing contract. The Awarded Bidder for this RFP will provide these services between 2026 and 2035 under a multi-year agreement, as detailed in Part I, Section C.
This RFP provides instructions for submitting proposals, the procedure and criteria by which the awarded Bidder will be selected, and the contractual terms which will govern the relationship between the State of Maine (State) and the awarded Bidder. This RFP also includes reports and other supplemental information referenced in Appendix O.
The Department is responsible for the collection of all types of traffic data and maintenance of a statewide traffic volume database. The Department manages two types of count programs: a.) Continuous Count Program and b.) Short Duration Count Program. The Continuous Count Program monitors traffic volume and/or classification data on a continuous, year-round basis. The Department has permanently installed network-enabled equipment at selected Continuous Count Sites (CCSs) around the State of Maine for long-term traffic pattern monitoring. In addition to CCS, the Department handles approximately 5000-7000 portable Short Duration Counts (SDCs) collected each year between April and November by both State count crews and external consulting firms. These counts are collected within 96 hours or less for a specific road segment. The State is currently undertaking a new strategic plan which could result in up to 12,000 portable counts per year. Additionally, the Department intends to collect micromobility data as well as vehicle data from various sources including but not limited to Intelligent Transportation Systems (ITS) equipment.
Statewide, the Department currently operates Sixteen (16) Weigh in Motion (WIM) sites and approximately 130 CCS sites collecting data on more than a million vehicles per day. Twenty-two (22) CCS sites collect traffic data from multiple locations. The remaining CCS sites (108) collect traffic data related to volume (34), axle-based classification (19), and radar (55). The Department plans to add an additional 400 – 500 CCS sites from signalized intersections, and up to 500 Continuous Turning Movement Sites (CTMs).
Traffic data, current and historical, is critical to the management of the Department’s highway system to ensure appropriate infrastructure design, for traveler safety, to prioritize investments, and to meet Federal Reporting requirements. It is a factor in determining federal funding of the Department. Traffic data is also of great interest to the public, such as reporting on various public trends, performing regional/municipal planning, and locating commercial enterprises.
The Award resulting from this RFP, will include a SaaS hosted software solution which will support the Department’s Traffic Monitoring Section’s needs as defined in the RFP requirements, outlined in Appendix G. This functionality includes supporting traffic count polling (collect and storage of raw traffic count data), processing, quality control, traffic count scheduling, and the generation of required Federal and Departmental reports.
B. General Provisions
1. From the time the RFP is issued until award notification is made, all contact with the State regarding the RFP must be made through the RFP Coordinator. No other person/ State employee is empowered to make binding statements regarding the RFP. Violation of this provision may lead to disqualification from the bidding process, at the State’s discretion.
2. Issuance of the RFP does not commit the Department to issue an award or to pay expenses incurred by a Bidder in the preparation of a response to the RFP. This includes attendance at personal interviews or other meetings and software or system demonstrations, where applicable.
3. All proposals must adhere to the instructions and format requirements outlined in the RFP and all written supplements and amendments (such as the Summary of Questions and Answers), issued by the Department. Proposals are to follow the format and respond to all questions and instructions specified below in the “Proposal Submission Requirements” section of the RFP.
4. Bidders will take careful note that in evaluating a proposal submitted in response to the RFP, the Department will consider materials provided in the proposal, information obtained through interviews/presentations (if any), and internal Departmental information of previous contract history with the Bidder (if any). The Department also reserves the right to consider other reliable references and publicly available information in evaluating a Bidder’s experience and capabilities.
5. The proposal must be signed by a person authorized to legally bind the Bidder and must contain a statement that the proposal and the pricing contained therein will remain valid and binding for a period of 180 days from the date and time of the bid opening.
6. The RFP and the awarded Bidder’s proposal, including all appendices or attachments, will be the basis for the final contract, as determined by the Department.
7. Following announcement of an award decision, all submissions in response to this RFP will be public records, available for public inspection pursuant to the State of Maine Freedom of Access Act (FOAA) (1 M.R.S. § 401 et seq.). State contracts and information related to contracts, including bid submissions, are generally public records per FOAA.
8. In the event that a Bidder believes any information that it submits in response to this RFP is confidential, it must mark that information accordingly, and include citation to legal authority in support of the Bidder’s claim of confidentiality. In the event that the Department receives a FOAA request that includes submissions marked as confidential, the Department shall evaluate the information and any legal authority from the Bidder to determine whether the information is an exception to FOAA’s definition of public record. If the Department determines to release information that a Bidder has marked confidential, it shall provide advance notice to the Bidder to allow for them to seek legal relief.
9. The Department, at its sole discretion, reserves the right to recognize and waive minor informalities and irregularities found in proposals received in response to the RFP.
10. If awarded a contract resulting from this RFP, vendors shall be required to disclose, in writing and in accordance with applicable Maine law, any actual or potential conflicts of interest. Such disclosure must include any financial, professional, or personal relationships that could give rise to a conflict of interest or the appearance of a conflict of interest. Failure to disclose a known conflict or appearance of conflict may result in disqualification, contract termination, or other remedies as provided by law.
11. All applicable laws, whether or not herein contained, are included by this reference. It is the Bidder’s responsibility to determine the applicability and requirements of any such laws and to abide by them.
C. Contract Term
The Department is seeking cost-efficient proposals to provide services, as defined in this RFP, for the anticipated contract period defined in the table below. The dates below are estimated and may be adjusted, as necessary, in order to comply with all procedural requirements associated with the RFP and the contracting process. The actual contract start date will be established by a completed and approved contract.
Contract Renewal: Following the initial term of the contract, the Department may opt to renew the contract for two (2) renewal periods renewal periods, as shown in the table below, and subject to continued availability of funding and satisfactory performance.
The term of the anticipated contract, resulting from the RFP, is defined as follows:
| Period |
| Start Date |
| End Date |
| Initial Period of Performance (Setup + 3 Years) |
| 01/10/2026 |
| 03/09/2029 |
| Renewal Period #1 (3 Years, 3 count seasons) |
| 03/10/2029 |
| 03/09/2032 |
| Renewal Period #2 (3 Years, 3 count seasons) |
| 03/10/2032 |
| 03/09/2035 |
D. Number of Awards
The Department anticipates making one (1) award as a result of this RFP process.
PART II SCOPE OF SERVICES TO BE PROVIDED
A. Overview The scope of services for this RFP includes:
1. Support the Department’s Short Duration Count and Continuous Count Programs.
2. Obtain traffic count data to monitor traffic growth.
3. Support the Department’s monthly and annual reporting needs (e.g. TMAS and HPMS reporting to the FHWA).
4. Support other Departmental reporting as needed (e.g. generate ADT Monthly Comparison Report, generate Annual Count Book by location with AADTs).
5. Support historical record keeping, tracking of equipment/work, and quality control.
B. Deliverables The scope of services for this RFP includes the following deliverables for the Traffic Count Software as a Service (SaaS):
1. Hosting Services - The software licenses, maintenance, and hosting services to support the Department’s annual gathering of traffic count data and ongoing customer support as detailed in Appendix F (Proposed Services Form) and Appendix G (Proposed Services Requirements Worksheet).
2. Implementation Services - All configuration, data conversion, support of Departmental deployment testing, remediation of testing issues, training, systems integration, and related services as appropriate to ensure the Department’s effective use and administration of the service as detailed in Appendix G (Proposed Services Requirements Worksheet).
3. Data Export Services - Upon termination of the contract, or in preparation for contract termination, and at no additional charge regardless of the reason for termination, provide all Departmental data in usable formats for archiving or loading into the replacement system as outlined in Appendix G (Proposed Services Requirements Worksheet). Refer to Requirement 2.12 (Data Export at Termination of Contract).
Requirements for Deliverables B. 1 through 3 are defined in the following sections:
· APPENDIX E – TECHNICAL ASSESSMENT FORM
· APPENDIX F – PROPOSED SERVICES FORM
· APPENDIX G – PROPOSED SERVICES REQUIREMENTS WORKSHEET
PART III KEY RFP EVENTS
Vendor Self Service System (VSS) The Office of State Procurement Services Vendor Self Service System website is found at the link below: https://www.maine.gov/dafs/bbm/procurementservices/vendors/vendor-self-service-system A copy of the RFP and all associated documents will be published in VSS.
Only documents published in VSS will be considered binding.
Any interested party may view open solicitations in VSS using the Public Access feature.
Vendors must have an active User ID and password in VSS to submit questions and respond to solicitations, including this RFP.
Vendor registration instructions and User Guide may be found at the link above, which include steps for searching for an existing account/User ID, or registering for a new account/User ID.
Vendors interested in responding to a solicitation are encouraged to obtain a User ID and password for VSS as soon as possible.
Vendors must have an active Vendor Code (VC or VS) to contract with the department.
Questions
General Instructions: It is the responsibility of all Bidders and other interested parties to examine the entire RFP and to seek clarification, in writing, if they do not understand any information or instructions.
Questions must be submitted in VSS as soon as possible but no later than the date and time published in VSS.
Questions should be clearly stated and reference the applicable section and/or page number of the RFP.
The Department assumes no liability for assuring accurate/complete/on time transmission and receipt.
Question & Answer Summary: Responses to all questions will be compiled in writing and published in VSS no later than seven (7) calendar days prior to the Proposal Submission Deadline. It is the responsibility of all interested parties to go to VSS to obtain a copy of the Question & Answer Summary. Only those answers issued in writing in VSS will be considered binding.
Amendments
All amendments released in regard to the RFP will be published in VSS. It is the responsibility of all interested parties to go to VSS to obtain amendments. Only those amendments published in VSS are considered binding.
Proposal Submission
Proposals Due Proposal submissions must be received no later than the Proposal Submission Deadline (closing date) published in VSS.
Any proposal submissions or any additional or revised proposal files received after the Proposal Submission Deadline will be rejected without exception.
Delivery Instructions Proposal submissions must be submitted to the Office of State Procurement Services via VSS.
Only proposal submissions received via VSS will be considered. The Department assumes no liability for assuring accurate/complete receipt.
Submissions containing links to file sharing sites or online file repositories will not be accepted as submissions. Only proposal submissions that have the actual requested files attached will be accepted.
Encrypted submissions received which require opening attachments and logging into a proprietary system will not be accepted. Bidders should work with their Information Technology team to ensure that the proposal submission will not be encrypted due to any security settings.
File size limits are 15MB per file. Bidders may separate their submissions into multiple files, as necessary, due to file size concerns.
Submission Format:
Bidders must submit multiple files, with each file named and containing the required information as defined below:
· File 1 [Bidder’s Name] – Preliminary Information:
PDF format preferred, and must include all required information and attachments stated in PART IV, Section I:
· Appendix A (Proposal Cover Page)
· Appendix B (Responsible Bidder Certification)
· File 2 [Bidder’s Name] – Organization Qualifications and Experience:
PDF format preferred, and must include all required information and attachments stated in PART IV, Section II:
· Appendix C (Organization Qualifications and Experience Form)
· Appendix D (Subcontractors Form)
· Overview of the Organization
· Organization Chart
· Litigation
· Financial Viability
· Licensure/Certification
· Certificate of Insurance
· File 3 [Bidder’s Name] – Proposed Services:
PDF format preferred, and must include all required information and attachments stated in PART IV, Section III:
· Appendix E (Technical Assessment Form)
· Appendix F (Proposed Services Form) Response to Narrative Questions
· Appendix G (Proposed Services Requirements Worksheet)
· Attachment 1 Implementation Schedule for Initial Period of Performance
· Attachment 2 Proposed Technical Architecture
· Attachment 3 SaaS Service Level Agreement (SLA)
· File 4 [Bidder’s Name] – Cost Proposal:
Excel format preferred, and must include all required information and attachments stated in PART IV, Section IV:
· Appendix H (Cost Proposal Form)
PART IV PROPOSAL SUBMISSION REQUIREMENTS
This section contains instructions for Bidders to use in preparing their proposals. The Department seeks detailed yet succinct responses that demonstrate the Bidder’s qualifications, experience, and ability to perform the requirements specified throughout the RFP.
Bidders’ proposals must follow the outline used below, including the numbering, section, and sub-section headings. Failure to use the outline specified in PART IV, or failure to respond to all questions and instructions throughout the RFP, may result in the proposal being disqualified as non-responsive or receiving a reduced score. The Department, and its evaluation team, has sole discretion to determine whether a variance from the RFP specifications will result either in disqualification or reduction in scoring of a proposal. Rephrasing of the content provided in the RFP will, at best, be considered minimally responsive.
Bidders are not to provide additional attachments beyond those specified in the RFP for the purpose of extending their response. Additional materials not requested will not be considered part of the proposal and will not be evaluated. Bidders must include any forms provided in the submission package or reproduce those forms as closely as possible. All information must be presented in the same order and format as described in the RFP.
Proposal Format and Contents
Section I Preliminary Information (File #1)
1. Proposal Cover Page Bidders must complete Appendix A (Proposal Cover Page). It is critical that the cover page show the specific information requested, including Bidder address(es) and other details listed. The Proposal Cover Page must be dated and signed by a person authorized to enter into contracts on behalf of the Bidder.
2. Responsible Bidder Certification Bidders must complete Appendix B (Responsible Bidder Certification). The Responsible Bidder Certification must be dated and signed by a person authorized to enter into contracts on behalf of the Bidder.
Section II Organization Qualifications and Experience (File #2)
1. Overview of the Organization Bidders must complete Appendix C (Qualifications and Experience Form) describing their qualifications and skills to provide the requested services in the RFP. Bidders must include three (3) examples of projects which demonstrate their experience and expertise in performing these services, as well as highlighting the Bidder’s stated qualifications and skills.
2. Subcontractors Bidders must complete Appendix D (Subcontractors Form) to provide a list that specifies the name, address, phone number, contact person, and a brief description of organizational capacity and qualifications for any subcontractors to be used. If no subcontractors will be used, indicate as such on the form.
3. Organizational Chart Bidders must provide an organizational chart. The organizational chart must include the project being proposed. Each position must be identified by position title and corresponding to the personnel job descriptions.
4. Litigation Bidders must attach a list of all current litigation in which the Bidder is named and a list of all closed cases that have closed within the past five (5) years in which the Bidder paid the claimant either as part of a settlement or by decree. For each, list the entity bringing suit, the complaint, the accusation, amount, and outcome.
5. Financial Viability Bidders must provide a current copy of their Dun & Bradstreet Business Information Report Snapshot.
6. Licensure/Certification Bidders may provide documentation of any applicable licensure/certification or specific credentials that are related to providing the proposed services of the RFP.
7. Certificate of Insurance Bidders must provide a certificate of insurance on a standard ACORD form (or the equivalent) evidencing the Bidder’s general liability, professional liability and any other relevant liability insurance policies that might be associated with the proposed services.
Section III Proposed Services (File #3)
Bidders must describe their proposal for the Scope of Services described in this RFP, by completing the following:
1. Technical Assessment Bidders must complete Appendix E (Technical Assessment Form) to describe the Bidder’s capability to meet the stated requirements and policies identified in this RFP.
2. Response to Narrative Questions Bidders must provide response to Narrative Questions in Appendix F (Proposed Services Form).
3. Proposed Services Requirements Worksheet Bidders must complete Appendix G (Proposed Services Requirements Worksheet) as detailed in the appendix.
4. Implementation Schedule for Initial Period of Performance Bidders must provide an Implementation Schedule for the Initial Period of Performance covering the 2026 and 2027 and 2028 count seasons using the Start Date and End Dates stated in PART I, C of this RFP. If subcontractors are involved, Bidders must clearly identify the work each will perform.
[NOTE: The Implementation Schedule may be represented as a Gantt chart or similar depiction of key project milestone dates and project activities. Responses such as “will be determined after contract signing” will not be acceptable.]
5. Proposed Technical Architecture Bidders must provide a diagram depicting the Proposed Technical Architecture. Diagram must identify a.) all hosted software components, b.) Cloud environment they are hosted in (e.g. Microsoft Azure, AWS, etc.), c.) connectivity for supported CCS and SDC sites, d.) connected mobile devices, and e.) any locally installed components.
Refer to Appendix G, Requirement 1.7 Technical Architecture.
6. SaaS Service Level Agreement (SLA) Bidders must provide a Service Level Agreement for the proposed solution that includes (at a minimum) a description of:
a.) how the Department can contact customer support (email, website, phone), b.) average response times to be provided for the Department’s requests, and c.) issue escalation procedures if needed for priority support requests.
Section IV Cost Proposal (File #4)
1. Cost Proposal Form Bidders must complete Appendix H (Cost Proposal Form).
2. General Instructions
a. The cost proposal must include the costs necessary for the Bidder to fully comply with the contract terms, conditions, and RFP requirements.
No costs related to the preparation of the proposal for the RFP, or to the negotiation of the contract with the Department, may be included in the proposal. Only costs to be incurred after the contract effective date that are specifically related to the implementation or operation of contracted services may be included
PART V PROPOSAL EVALUATION AND SELECTION
Evaluation of the submitted proposals will be accomplished as follows:
A. Evaluation Process – General Information
1. An evaluation team, composed of qualified reviewers, will judge the merits of the proposals received in accordance with the criteria defined in the RFP.
2. Officials responsible for making decisions on the award selection will ensure that the selection process accords equal opportunity and appropriate consideration to all who are capable of meeting the specifications. The goals of the evaluation process are to ensure fairness and objectivity in review of the proposals and to ensure that the contract is awarded to the Bidder whose proposal provides the best value to the State of Maine.
3. The Department reserves the right to communicate and/or schedule interviews/presentations with Bidders, if needed, to obtain clarification of information contained in the proposals received. The Department may revise the scores assigned in the initial evaluation to reflect those communications and/or interviews/presentations.
4. Changes to proposals, including updating or adding information, will not be permitted during any portion of the evaluation process. Therefore, Bidders must submit proposals that present their rates and other requested information as clearly and completely as possible.
B. Scoring Weights and Process
1. Scoring Weights: Proposal scores will be based on a 100-point scale and will measure the degree to which each proposal meets the following criteria. The proposal materials that will be evaluated under each section below are identified in Part IV of the RFP.
| Section I. |
| Preliminary Information |
| (No Points) |
| Section II. |
| Organization Qualifications and Experience |
| (20 Points) |
| Section III. |
| Proposed Services |
| (50 Points) |
| Section IV. |
| Cost Proposal |
| (30 Points) |
| Total |
| 100 |
2. Scoring Process: For proposals that demonstrate meeting the eligibility requirements in Section I, if applicable, the evaluation team will use a consensus approach to evaluate and score Sections II & III above. Members of the evaluation team will not score those sections individually but, instead, will arrive at a consensus as to assignment of points for each of those sections. Section IV, the Cost Proposal, will be scored as described below.
3. Demonstrations: Following the evaluation of Sections I, II and III, the evaluation team, via the RFP Coordinator, may contact highest scoring Bidders to request, at their own expense, a webinar demonstration and to arrange the details of the demonstration. Demonstrations will be limited to ninety (90) minutes and shall include a demonstration of the solutions functions in this RFP and allow for the evaluation team to ask questions and receive answers. The Department will contact the highest scoring bidders to schedule the demonstrations and will provide further guidance at that time regarding specific functionality to be demonstrated.
The score for Section III Proposed Services and Technical Assessment may be adjusted (upward or downward) based on the demonstrations and according to the scoring weights described in Part V.B. of the RFP.
4. Scoring the Cost Proposal: The total cost proposed for conducting all the functions specified in the RFP will be assigned a score according to a mathematical formula. The lowest bid will be awarded 30 points. Proposals with higher bid values will be awarded proportionately fewer points calculated in comparison with the lowest bid.
The scoring formula is:
(Lowest submitted cost proposal / Cost of proposal being scored) x 30 = pro-rated score No Best and Final Offers: The State of Maine will not seek or accept a best and final offer (BAFO) from any Bidder in this procurement process. All Bidders are expected to provide their best value pricing with the submission of their proposal.
C. Negotiations
1. The Department reserves the right to negotiate with the awarded Bidder(s) to finalize a contract. Such negotiations may not significantly vary the content, nature, or requirements of the proposal or the Department’s Request for Proposal to an extent that may affect the price of goods or services requested.
2. The Department reserves the right to terminate contract negotiations with an awarded Bidder who submits a proposed contract significantly different from the proposal they submitted in response to the advertised RFP.
3. In the event that an acceptable contract cannot be negotiated with the highest ranked Bidder, the Department may withdraw its award and negotiate with the next-highest ranked Bidder, and so on, until an acceptable contract has been finalized. Alternatively, the Department may cancel the RFP, at its sole discretion.
D. Selection and Award
1. The final decision regarding the award of the contract will be made by representatives of the Department subject to approval by the State Procurement Review Committee.
2. Notification of conditional award selection or non-selection will be made in writing by the Department.
3. Issuance of the RFP in no way constitutes a commitment by the State of Maine to award a contract, to pay costs incurred in the preparation of a response to the RFP, or to pay costs incurred in procuring or contracting for services, supplies, physical space, personnel or any other costs incurred by the Bidder.
4. The Department reserves the right to reject any and all proposals or to make multiple awards.
E. Appeal of Contract Awards
Any person aggrieved by the award decision that results from the RFP may appeal the decision to the Director of the Bureau of General Services in the manner prescribed in 5 M.R.S.A. § 1825-E and 18-554 Code of Maine Rules Chapter 120. The appeal must be in writing and filed with the Director of the Bureau of General Services, 9 State House Station, Augusta, Maine, 04333-0009 within 15 calendar days of receipt of notification of conditional contract award.
PART VI CONTRACT ADMINISTRATION AND CONDITIONS
A. Contract Document
1. The awarded Bidder will be required to execute an IT Service Contract (IT-SC) with Confidentiality and Non-Disclosure Agreement (NDA) including appropriate riders as determined by the issuing department. Bidders shall carefully review the IT-SC.
All exceptions will be negotiated between the awarded Bidder(s) and the State. The State will not accept any proposed exceptions as part of this RFP process. The State is not obligated to accept, negotiate, or compromise of any proposed exceptions.
The complete set of standard State of Maine Service Contract documents, along with other forms and contract documents commonly used by the State, may be found on the Office of State Procurement Services’ website at the following link: Office of .
2. Due to the use of Federal funds, the contract language included in Appendix N (Federal Funding Contract Rider D) will be included in the contract as Rider D.
3. Allocation of funds is final upon successful negotiation and execution of the contract, subject to the review and approval of the State Procurement Review Committee. Contracts are not considered fully executed and valid until approved by the State Procurement Review Committee and funds are encumbered. No contract will be approved based on an RFP which has an effective date less than fourteen (14) calendar days after award notification to Bidders. (Referenced in the regulations of the Department of Administrative and Financial Services, Chapter 110, § 3(B)(i).)
This provision means that a contract cannot be effective until at least 14 calendar days after award notification.
4. The State recognizes that the actual contract effective date depends upon completion of the RFP process, date of formal award notification, length of contract negotiation, and preparation and approval by the State Procurement Review Committee. Any appeals to the Department’s award decision(s) may further postpone the actual contract effective date, depending upon the outcome. The contract effective date listed in the RFP may need to be adjusted, if necessary, to comply with mandated requirements.
5. In providing services and performing under the contract, the awarded Bidder must act as an independent contractor and not as an agent of the State of Maine.
B. Standard State Contract Provisions
1. Contract Administration Following the award, a Contract Administrator from the Department will be appointed to assist with the development and administration of the contract and to act as administrator during the entire contract period. Department staff will be available after the award to consult with the awarded Bidder in the finalization of the contract.
2. Payments and Other Provisions The State anticipates paying the Contractor on the basis of net 30 payment terms, upon the receipt of an accurate and acceptable invoice. An invoice will be considered accurate and acceptable if it contains a reference to the State of Maine contract number, contains correct pricing information relative to the contract, and provides any required supporting documents, as applicable, and any other specific and agreed-upon requirements listed within the contract that results from the RFP.
PART VII LIST OF RFP APPENDICES AND RELATED DOCUMENTS
Appendix A – Proposal Cover Page
Appendix B – Responsible Bidder Certification
Appendix C – Qualifications and Experience Form
Appendix D – Subcontractors Form
Appendix E – Technical Assessment Form
Appendix F – Proposed Services Form
Appendix G – Proposed Services Requirements Worksheet
Appendix H – Cost Proposal Form
Appendix I – Data Conversion Data Sets
Appendix J – LRS Meta Data for Stations
Appendix K – Factor Groups and Types
Appendix L – HPMS Validation Rules
Appendix M – HPMS Vehicle Mix Summary
Appendix N – Federal Funding Contract Rider D
Appendix O – RFP Supplemental Files
APPENDIX A
Department of Transportation
PROPOSAL COVER PAGE
RFP# 202510141
Bidder Name:
Chief Executive - Name/Title:
Tel:
E-mail:
Headquarters Street Address:
Headquarters City/State/Zip:
(Provide information requested below if different from above)
Lead Point of Contact for Proposal - Name/Title:
Tel:
E-mail:
Headquarters Street Address:
Headquarters City/State/Zip:
· This proposal and the pricing structure contained herein will remain firm for a period of 180 days from the date and time of the bid opening.
· No personnel currently employed by the Department, either directly or indirectly, in any activities relating to the preparation of the Bidder’s proposal.
· No attempt has been made, or will be made, by the Bidder to induce any other person or firm to submit or not to submit a proposal.
· The above-named organization is the legal entity entering into the resulting contract with the Department if they are awarded the contract.
· The undersigned is authorized to enter contractual obligations on behalf of the above-named organization.
To the best of my knowledge, all information provided in the enclosed proposal, both programmatic and financial, is complete and accurate at the time of submission.
Name (Print):
Title:
Authorized Signature:
Date:
State of Maine RFP# 202510141 Rev. 10/1/2025 – DAFS/Office of State Procurement Services
APPENDIX B
State of Maine Department of Transportation
RESPONSIBLE BIDDER CERTIFICATION
RFP# 202510141
Bidder Name:
By signing this document, I certify to the best of my knowledge and belief that the aforementioned organization, its principals and any subcontractors named in this proposal:
a. Are not presently debarred, suspended, proposed for debarment, and declared ineligible or voluntarily excluded from bidding or working on contracts issued by any governmental agency.
b. Have not within three years of submitting the proposal for this contract been convicted of or had a civil judgment rendered against them for:
i. Fraud or a criminal offense in connection with obtaining, attempting to obtain, or performing a federal, state, or local government transaction or contract.
ii. Violating Federal or State antitrust statutes or committing embezzlement, theft, forgery, bribery, falsification or destruction of records, making false statements, or receiving stolen property.
c. Are not presently indicted for or otherwise criminally or civilly charged by a governmental entity (Federal, State or Local) with commission of any of the offenses enumerated in paragraph (b) of this certification.
d. Have not within a three (3) year period preceding this proposal had one or more federal, state, or local government transactions terminated for cause or default.
e. Have not entered into a prior understanding, agreement, or connection with any corporation, firm, or person submitting a response for the same materials, supplies, equipment, or services and this proposal is in all respects fair and without collusion or fraud. The above-mentioned entities understand and agree that collusive bidding is a violation of state and federal law and can result in fines, prison sentences, and civil damage awards.
f. Is not a foreign adversary business entity (https://www.maine.gov/oit/prohibited-technologies).
g. Is not on the list of prohibited companies (https://www.maine.gov/oit/prohibited-technologies) or does not obtain or purchase any information or communications technology or services included on the list of prohibited information and communications technology and services https://www.maine.gov/oit/prohibited-technologies (Title 5 §2030-B).
Name (Print):
Title:
Authorized Signature:
Date:
APPENDIX C
Department of Transportation QUALIFICATIONS and EXPERIENCE FORM
RFP# 202510141
Bidder’s Organization Name:
Present a brief statement of qualifications. Describe the history of the Bidder’s organization, especially regarding skills pertinent to the specific work required by the RFP and any special or unique characteristics of the organization which would make it especially qualified to perform the required work activities. You may expand this form and use additional pages to provide this information.
Provide a description of projects that occurred within the past five (5) years which reflect experience and expertise needed in performing the functions described in Part II – Scope of Services to be Provided of the RFP.
Please identify whether the project involved spatial integration, including the ability to display the location of count stations on a digital map. For each project involving spatial integration, select “Yes” where prompted, otherwise select “No”. For projects that included spatial integration, describe the data interface between Traffic Count solution and client’s internal GIS data and any challenges, recommendations or lessons learned.
Contract history with the State of Maine, whether positive or negative, may be considered in evaluating proposals even if not provided by the Bidder.
If the Bidder has not provided similar services, note this, and describe experience with projects that highlight the Bidder’s general capabilities.
Project One
Client Name:
Client Contact Person:
Telephone:
E-Mail:
| Spatial Integration |
| [ ] Yes [ ] No (select one) |
Brief Description of Project
Project Two
Client Name:
Client Contact Person:
Telephone:
E-Mail:
| Spatial Integration |
| [ ] Yes [ ] No (select one) |
Brief Description of Project
Project Three
Client Name:
Client Contact Person:
Telephone:
E-Mail:
| Spatial Integration |
| [ ] Yes [ ] No (select one) |
Brief Description of Project
APPENDIX D
Department of Transportation
SUBCONTRACTORS FORM
RFP# 202510141
Bidder Name:
Subcontractors If subcontractors are to be used, Bidders must use the tables below to describe the name, address, phone number, contact person, and a brief description of the subcontractors’ organizational capacity and qualifications.
Subcontractor 1
Subcontractor Name:
Contact Person:
Telephone:
E-Mail:
Brief Description of Anticipated Role and Qualifications
Subcontractor 2
Subcontractor Name:
Contact Person:
Telephone:
E-Mail:
Brief Description of Anticipated Role and Qualifications
Subcontractor 3
Subcontractor Name:
Contact Person:
Telephone:
E-Mail:
Brief Description of Anticipated Role and Qualifications
APPENDIX E
Department of Transportation
TECHNICAL ASSESSMENT FORM
RFP# 202510141
Traffic Count Software as a Service (SaaS)
Bidders must complete the Technical Assessment Form embedded below.
The Technical Assessment Form may be obtained by double-clicking the Excel (.xlsx) icon below.
APPENDIX F
Department of Transportation
PROPOSED SERVICES FORM
RFP# 202510141
Proposer Name:
Instructions: Describe the proposed services by responding to the narrative questions within this appendix. Questions are grouped into the following categories:
Narrative Question Categories
1. Implementation Plan
2. Proposed Solution
Responses to the narrative questions in Appendix F (Proposed Services Form) must align with Bidder’s responses in Appendix G (Proposed Services Requirements Worksheet); and must demonstrate Bidder’s understanding of the RFP requirements. Please do not repeat the same information in both appendices.
For APPENDIX F, use as much space as necessary for a concise and meaningful response. Attachments or images should be inserted into Appendix F where reasonable. Information provided as separate documents must be titled clearly and reference to the question number (e.g., Question 2.1 - Solution Overview) and must be included in File 3 of the proposal submission. Refer to Part III for proposal submission instructions.
Do not describe functionality or implementation activities that are NOT offered as part of this proposal. Do not include cost information in Appendix F. Costs and price lists must ONLY be included in Appendix H (Cost Proposal).
Prior to completing the form on the following pages, please review all Appendix G instructions above.
Category 1 - Implementation Plan
QUESTION 1.1 - Implementation alignment with Count Season: For…
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 .