BMV Electronic Title Services (ETS) Solution

Location: Ohio
Posted: Nov 4, 2025
Due: Dec 1, 2025
Agency: State Government of Ohio
Type of Government: State & Local
Category:
  • R - Professional, Administrative and Management Support Services
Solicitation No: SRC0000034998
Publication URL: To access bid details, please log in.
Solicitation ID: SRC0000034998
Solicitation Name: BMV Electronic Title Services (ETS) Solution
Original Begin Date: 11/4/2025 12:00:00 AM
Begin Date: 11/4/2025 12:00:00 AM
End Date: 12/1/2025 1:00:00 PM
Inquiry End Date: 11/26/2025 3:00:00 PM
Commodity: Systems integration design
MBE Set Aside: MBE Set Aside
Agency: DPS600000 Bureau of Motor Vehicles CDSB
DPS714000 PROCUREMENT SERVICES CDSB
Solicitation Status: Open for Bidding
Solicitation Type: Request For Proposal (RFP) (Double Envelope)

Solicitation General Information
In an MBE set-aside solicitation, only those bidders/suppliers with an active MBE certification at the time the solicitation closes can submit a response
Solicitation ID
SRC0000034998
Solicitation Name
BMV Electronic Title Services (ETS) Solution
RFx Type
Request For Proposal (RFP) (Double Envelope)
Lot #
1
Solicitation Status
Open for Bidding
Round #
1
MBE Set Aside
Begin Date
11/4/2025 12:00:00 AM (ET)
Amendment?
End Date
12/1/2025 1:00:00 PM (ET)
Inquiry End Date
11/26/2025 3:00:00 PM
Summary
BACKGROUND.
The Ohio Department of Public Safety (ODPS), through its Bureau of Motor Vehicles (BMV), administers the State’s motor vehicle title and registration programs.
To comply with recent legislation and enhance the efficiency of title processing, ODPS seeks to implement an Electronic Title Services (ETS) solution. The ETS will enable licensed motor vehicle dealers to submit title applications electronically from their Dealer Management Systems (DMS) directly to the Clerk of Courts via the BMV’s Automated Title Processing System (ATPS) — the official system used statewide for title issuance.
This solicitation is intended to identify a qualified Contractor to develop, host, and maintain an interface solution that connects DMS platforms with the ATPS, ensuring secure, timely, and accurate electronic title transactions across all 88 Ohio counties.
OVERVIEW.
ODPS is seeking proposals from qualified Offerors to provide a comprehensive Electronic Title Service (ETS) that will:
• Integrate diverse Dealer Management Systems (DMS) with the BMV’s ATPS.
• Enable electronic submission of title transactions by motor vehicle dealers to Clerks of Courts.
• Ensure compliance with all State technical and security requirements.
• Operate on a per-transaction fee basis with no cost to the State.
The ETS solution must be designed, tested, and fully operational in production by June 30, 2026, with ongoing maintenance, updates, and support provided throughout the contract term.
OBJECTIVES.
ODPS has established the following objectives for this solicitation:
1. Establish a secure, reliable electronic title transaction interface between DMS providers and the BMV ATPS.
2. Reduce paper processing, manual data entry, and turnaround time for title issuance.
3. Ensure full compliance with all statutory and data security requirements.
4. Provide a scalable and flexible platform that accommodates future title transaction types.
5. Promote a standardized and efficient process for dealers, clerks, and the BMV.
6. Ensure contractors have qualified staff, proven experience, and technical capacity to deliver all required functionality on time.
Predecessor Contract
Process

Request for Proposal (RFP) :  Offerors must review the attached "SRC0000034998 BMV ETS RFP" document. Each Offeror must submit a Technical Proposal and a Cost Proposal as part of its Proposal package. Proposals must be submitted as two separate components (Technical Proposal and Cost Proposal) in separate electronic envelopes.
Technical Proposal : The Technical Proposal is to be submitted as a single searchable PDF document indexed as required in Attachment Two.
Cost Proposal : The Offeror must submit a separate cost section of its Proposal in the required format described in Attachment Two and as appears in OhioBuys Item grid.

Each section must be submitted in its own separate, electronic submission as indicated by the solicitation questionnaire. The submission with the Technical Proposal will be electronically sealed and contain a signed Technical Proposal, and the submission with the Cost Proposal also will be electronically sealed.

OHIOBUYS TRAINING MATERIALS
OhioBuys training materials can be located at this site https://procure.ohio.gov/bidders-and-suppliers/resources/03_Using+OhioBuys
To participate or submit an inquiry for this RFx, you need to be registered in the OhioBuys Supplier Portal. Suppliers are not required at this time to be registered in OAKS. If you have a need to seek technical support, clearly specify you need access to an active Ohio Buys solicitation.
Technical Support 1-877-644-6771
If there is a need for technical support during your proposal submission in the last 48 hours prior to the submissions, contact 614-466-5090.  This number is for OhioBuys solicitation technical questions only; there will not be any questions answered regarding the solicitation.
Note:
Chrome is the preferred browser for OhioBuys.
Only have a single window open that is logged into OhioBuys, having multiple windows opened to a single user can create an error when trying to submit your proposal.

Ship To
Contracting Entity
DPS600000 Bureau of Motor Vehicles CDSB
1 Record(s)
Participating Agencies
DPS714000 PROCUREMENT SERVICES CDSB
1 Record(s)
Solicitation Documents
Keywords
Search Reset
Title Type Att. Validity End Date Validity End Date
Supplement B - Data Security and Privacy Terms RFx Technical Documents (Approved)
Supplement A - State IT Policy Standard and Service Requirements RFx Technical Documents (Approved)
SRC0000034998 BMV ETS RFP Ad-hoc Solicitation Document (Approved)
3 Record(s)

Attachment Preview

REQUEST FOR PROPOSALS
RFP No. SRC0000034998
RFP NUMBER:
UNSPSC CATEGORY:
SRC0000034998
81111503
The State of Ohio, through the Department of Public Safety, Fiscal/Procurement Services,
for the Bureau of Motor Vehicles, is requesting proposals for:
Electronic Title Services (ETS) Solution
Those submitting proposals (Offerors) must note that all proposals and other material submitted will become the property of
the State and may be returned only at the State's option. Proprietary information should not be included in a proposal or
supporting materials because the State will have the right to use any materials or ideas submitted in any proposal without
compensation to the Offeror. Additionally, all proposals will be open to the public after the award of the contract has been
posted on the State Procurement Web site. Refer to the Ohio Administrative Code, Rule 123:5-1-08 (E).
This RFP consists of five parts, nine attachments, and two supplements, totaling 56 consecutively
numbered pages. Please verify that you have a complete copy.
RFP No. SRC0000034998
PART ONE: EXECUTIVE SUMMARY
PURPOSE. This is a Request for Competitive Sealed Proposals (RFP) under Section 125.071 of the Ohio Revised Code
(ORC) and Rule 123:5-1-08 of the Ohio Administrative Code (OAC). The Ohio Department of Public Safety (ODPS),
Fiscal/Procurement Services on behalf of the Bureau of Motor Vehicles (the Division or BMV), is soliciting competitive sealed
proposals (Proposals) for Electronic Title Services (ETS) Solution and this RFP is the result of that request. If a suitable
Proposal is made in response to this RFP, the State of Ohio (State), through ODPS, may enter into a contract (the Contract) to
have the selected Offeror (the Contractor) perform all or part of the project (the Project or the Work). This RFP provides
details on what is required to submit a Proposal for the Work, how ODPS will evaluate the Proposals, and what will be required
of the Contractor in performing the Work.
This RFP also gives the estimated dates for the various events in the submission process, selection process, and performance
of the Work. While these dates are subject to change, prospective Offerors must be prepared to meet them as they currently
stand.
Once awarded, the term of the Contract will be from the award date through June 30, 2027. ODPS also may solely renew this
Contract at the discretion of ODPS for a period of one month; this unilateral renewal may be completed by ODPS at any time
during the term of the Contract. Any other renewals will be by mutual agreement between the Contractor and ODPS for any
number of times and for any period of time. The cumulative time of all mutual renewals may not exceed two (2) years, unless
ODPS determines that additional renewal is necessary, and are subject to and contingent upon the discretionary decision of
the Ohio General Assembly to appropriate funds for this Contract in each new biennium. ODPS may renew all or part of this
Contract subject to the satisfactory performance of the Contractor and the needs of the Division.
Any failure to meet a deadline in the submission or evaluation phases and any objection to the dates for performance of the
Project may result in ODPS refusing to consider the Proposal of the Offeror.
BACKGROUND.
The Ohio Department of Public Safety (ODPS), through its Bureau of Motor Vehicles (BMV), administers the State’s motor
vehicle title and registration programs.
To comply with recent legislation and enhance the efficiency of title processing, ODPS seeks to implement an Electronic Title
Services (ETS) solution. The ETS will enable licensed motor vehicle dealers to submit title applications electronically from their
Dealer Management Systems (DMS) directly to the Clerk of Courts via the BMV’s Automated Title Processing System (ATPS)
— the official system used statewide for title issuance.
This solicitation is intended to identify a qualified Contractor to develop, host, and maintain an interface solution that connects
DMS platforms with the ATPS, ensuring secure, timely, and accurate electronic title transactions across all 88 Ohio counties.
OVERVIEW.
ODPS is seeking proposals from qualified Offerors to provide a comprehensive Electronic Title Service (ETS) that will:
Integrate diverse Dealer Management Systems (DMS) with the BMV’s ATPS.
Enable electronic submission of title transactions by motor vehicle dealers to Clerks of Courts.
Ensure compliance with all State technical and security requirements.
Operate on a per-transaction fee basis with no cost to the State.
The ETS solution must be designed, tested, and fully operational in production by June 30, 2026, with ongoing maintenance,
updates, and support provided throughout the contract term.
OBJECTIVES.
ODPS has established the following objectives for this solicitation:
1. Establish a secure, reliable electronic title transaction interface between DMS providers and the BMV ATPS.
2. Reduce paper processing, manual data entry, and turnaround time for title issuance.
3. Ensure full compliance with all statutory and data security requirements.
4. Provide a scalable and flexible platform that accommodates future title transaction types.
5. Promote a standardized and efficient process for dealers, clerks, and the BMV.
6. Ensure contractors have qualified staff, proven experience, and technical capacity to deliver all required
functionality on time.
RFP No. SRC0000034998
CALENDAR OF EVENTS. The schedule for the Project is given in OhioBuys and is subject to change. ODPS may change
this schedule at any time. If ODPS changes the schedule before the Proposal due date, it will do so through an amendment in
OhioBuys and posted to the public portal page for this RFP. After the Proposal due date and before the award of the Contract,
ODPS will make scheduled changes through the RFP amendment process. ODPS will make changes in the Project schedule
after the Contract award through the change order provisions located in Attachment Three, General Terms and Conditions of
the Contract. It is each Offeror’s responsibility to check the public portal question and answer area for this RFP for current
information regarding this RFP and its calendar of events through award of the Contract. No contact shall be made with
Division/Program staff until the Contract award is announced.
There are references in this RFP to the Proposal due date. Offerors must assume, unless it is clearly stated to the contrary,
that any such reference means the date and time (Columbus, OH local time) that the Proposals are due.
PART TWO: STRUCTURE OF THIS RFP
ORGANIZATION. This RFP is organized into five parts, nine attachments and tow supplements. The parts and attachments
are listed below.
PARTS:
Part One
Part Two
Part Three
Part Four
Part Five
Executive Summary
Structure of this RFP
General Instructions
Evaluation of Proposals
Award of the Contract
A.
B.
ATTACHMENTS:
Attachment One
Part One
Part Two
Attachment Two
Attachment Three
Part One
Part Two
Part Three
Part Four
Part Five
Part Six
Part Seven
Attachment Four
Attachment Five
5-A
5-B
5-C
5-D
Attachment Six
Attachment Seven
7-A
7-B
7-C
Attachment Eight
Attachment Nine
Work Requirements and Special Provisions
Work Requirements
Special Provisions
Requirements for Proposals
General Terms and Conditions
Performance and Payment
Work & Contract Administration
Ownership & Handling of Intellectual Property & Confidential Information
Representations, Warranties, and Liabilities
Acceptance and Maintenance
Construction
Law & Courts
Contract
Offeror Profile Summary
Offeror Profile Form
Offeror Prior Project Form
Offeror Prior Project Form
Offeror Prior Project Form
Offeror References
Offeror’s Candidate Summary
Offeror’s Candidate References
Offeror’s Candidate Education, Training, Licensure, and Certifications
Offeror’s Candidate Experience
Offeror Performance Form
Cost Summary Form
Supplement A
Supplement B
Architectural Compliance, Standards and Service Requirements
State IT Policy, Standard Service Requirements
RFP No. SRC0000034998
PART THREE: GENERAL INSTRUCTIONS
The following sections provide details on how to get more information about this RFP and how to respond to this RFP. All
responses must be complete and in the prescribed format.
STATE OF OHIO ONLINE PURCHASING SOLUTION. OhioBuys provides the primary platform for Supplier partners to
engage in procurement activities with the State of Ohio. For additional information on submitting proposals see the “Viewing
and Responding to Solicitations” Learner Guide or the “Viewing and Responding to Solicitations” Supplier Training Video
linked below.
Learner Guide
https://procure.ohio.gov/about/03_supplier-training/03_supplier-training
Viewing and Responding to Solicitations
https://www.youtube.com/watch?v=K6iE32BUMJ0&feature=youtu.be
INQUIRIES. Offerors may make inquiries regarding this RFP any time during the inquiry period listed on the OhioBuys Public
Solicitations page. To make an inquiry, Offerors must login to OhioBuys, navigate to the solicitation, open the Inquiry tab and
submit their inquiry.
Offerors will not receive a personalized e-mail response to their question, nor will they receive notification when the question
has been answered.
Offerors may view inquiries and responses on the OhioBuys Public Solicitations page by opening the Solicitation Overview
and navigating to the inquiries section of that page. ODPS will try to respond to all inquiries within forty-eight (48) hours of
receipt, excluding weekends and State holidays. ODPS will not respond to any inquiries received after the inquiry period.
Offerors are to base their Proposals on the requirements and performance expectations established in this RFP for the
Contract, not on details of any other potentially related contract or project. If Offerors ask questions about existing or past
contracts using the OhioBuys Inquiry process, ODPS will use its discretion in deciding whether to provide answers as part of
this RFP process.
ODPS is under no obligation to acknowledge questions submitted through the OhioBuys Inquiry process if those questions are
not in accordance with these instructions or deadlines.
PROTESTS. Any Offeror that objects to the award of a Contract resulting from the issuance of this RFP may file a protest of
the award of the Contract, or any other matter relating to the process of soliciting the Proposals. Such protest must comply
with the following information:
1. The protest must be filed by a prospective or actual offeror objecting to the award of a Contract resulting from the RFP.
The protest must be in writing and contain the following information:
a. The name, address, and telephone number of the protester;
b. The name and number of the RFP being protested;
c. A detailed statement of the legal and factual grounds for the protest, including copies of any relevant documents;
d. A request for a ruling by ODPS;
e. A statement as to the form of relief requested from ODPS; and
f. Any other information the protester believes to be essential to the determination of the factual and legal questions at
issue in the written request.
2. A timely protest will be considered by ODPS, on behalf of the division, if it is received within the following periods:
a. A protest based on alleged improprieties in the issuance of the RFP, or any other event preceding the closing date for
receipt of Proposals that are apparent or should be apparent prior to the closing date for receipt of Proposals, must
be filed no later than five business days prior to the Proposal due date.
b. If the protest relates to the recommendation of the evaluation committee for an award of the Contract, the protest
must be filed as soon as practicable after the Offeror is notified of the decision by ODPS regarding the Offeror’s
Proposal.
3. An untimely protest may be considered by ODPS at the discretion of ODPS. An untimely protest is one received by the
ODPS after the time periods set in paragraph 2 above. In addition to the information listed in paragraph 1, untimely
protests must include an explanation of why the protest was not made within the required time frame.
4. All protests must be filed at the following location:
RFP No. SRC0000034998
Department of Public Safety
Fiscal/Procurement Services
1970 West Broad Street
Columbus, OH 43223
SUBJECT: SRC0000034998 Electronic Title Services (ETS) Solution
This protest language only pertains to this RFP offering.
AMENDMENT TO THE RFP. If ODPS decides to revise this RFP before the Proposal due date, an amendment will be issued
in OhioBuys as a new round. If an Offeror has submitted a Proposal prior to an amendment being issued and wishes to be
considered, the Offeror must resubmit their Proposal in response to the latest round of the RFP. Proposals submitted in
response to amended RFPs prior to the most recent amendment will not be opened or evaluated.
When a modification to this RFP is necessary, ODPS will execute an RFP amendment by creating a new round. ODPS may
issue amendments any time before Proposals are due, and it is each Offeror’s responsibility to check for amendments and
other current information regarding this RFP.
After the submission of Proposals, amendments will be distributed only to those Offerors whose submissions are under active
consideration. When ODPS issues an amendment to the RFP after Proposals have been submitted, ODPS will permit
Offerors to withdraw their Proposals.
This withdrawal option will allow any Offeror to remove its Proposal from active consideration should the Offeror feel that the
amendment changes the nature of the transaction to the extent that the Offeror’s Proposal is no longer in its interests.
Alternatively, ODPS may allow Offerors that have Proposals under active consideration to modify their Proposals in response
to the amendment, as described below.
Whenever ODPS issues an amendment after the Proposal due date, ODPS will tell all Offerors whose Proposals are under
active consideration whether they have the option to modify their Proposals in response to the amendment. Any time ODPS
amends the RFP after the Proposal due date, an Offeror will have the option to withdraw its Proposal even if ODPS permits
modifications to the Proposals. If the Offerors are allowed to modify their Proposals, ODPS may limit the nature and scope of
the modifications. Unless otherwise stated in the notice by ODPS, modifications and withdrawals must be made in writing and
must be submitted within ten business days after the amendment is issued. If this RFP provides for a negotiation phase, this
procedure will not apply to changes negotiated during that phase. Withdrawals and modifications must be made in writing and
submitted to ODPS at the address and in the same manner required for the submission of the original Proposals. Any
modification that is broader in scope than ODPS has authorized may be rejected and treated as a withdrawal of the Offeror’s
Proposal.
PROPOSAL SUBMITTAL. Each Offeror must submit a Technical Proposal and a Cost Proposal as part of its Proposal
package. Proposals must be submitted as two separate components (Technical Proposal and Cost Proposal) in separate
electronic envelopes.
Technical Proposal: The Technical Proposal is to be submitted as a single searchable PDF document indexed as
required in Attachment Two.
Cost Proposal: The Offeror must submit a separate cost section of its Proposal in the required format described in
Attachment Two.
Each section must be submitted in its own separate, electronic submission as indicated by the solicitation questionnaire. The
submission with the Technical Proposal will be electronically sealed and contain a signed Technical Proposal, and the
submission with the Cost Proposal also will be electronically sealed.
If an Offeror includes in its Proposal information it considers confidential, proprietary, or trade secret exempt from disclosure in
a public records request, it must submit a redacted version of any document containing such information, as further described
in this paragraph. Offerors must only redact (black out) the specific language that is exempt from disclosure pursuant to the
Ohio Public Records Act, R.C. section 149.43. The following are not acceptable actions for the protection of trade secret or
confidential information in an Offeror’s response: 1) redaction of sections in their entirety simply because they may contain
some confidential information; 2) inclusion of a blanket confidentiality or copyright notice anywhere in an Offeror’s response or
redacted documents; and 3) redaction of the Cost Proposal in its entirety. In addition to the redacted document(s), Offerors
must submit a list of each redaction with a detailed legal explanation for each redaction to demonstrate that the redacted
information is protected under the Ohio Public Records Act. A blanket statement that all redactions are exempt from
disclosure pursuant to the Ohio Public Records Act and/or the Uniform Trade Secrets Act is not a sufficient explanation. The
redacted version(s) must be submitted as an electronic copy in a searchable PDF format. The redacted version(s) and
accompanying explanation, as submitted, will be available for inspection and released in response to public records requests.
If redacted version(s) with the accompanying explanation are not submitted, or if an improperly redacted version or insufficient
explanation is submitted, the original submission of the Proposal may be provided in response to public records requests. By
not submitting a redacted version of the Proposal with accompanying explanation, an Offeror consents to the release of the
original Proposal submission in response to a public records request.
This is the opportunity summary page. It provides an overview of this opportunity and a preview of the attached documentation.
Daily notification on new contract opportunities

With GovernmentContracts, you can:

  • Find more opportunities and win more business
  • Receive daily alerts for all new bid opportunities
  • Get contract opportunities matched to your business
ONE WEEK FREE TRIAL
* Disclaimer: Information regarding bids, requests for proposals (RFPs), or requests for qualifications (RFQs) is provided on this website only for convenience and does not constitute official public notice. Persons wishing to respond to or inquire about bids, RFPs, or RFQs should contact the appropriate government department.