9037 - RFI Document.pdf

PDF 1 MB Posted

Attached to
ProjectSuite Enterprise Edition (PSEE)
Solicitation number
RFI-17358
Issued by
Leon County, Florida

About this file

This is a Request for Information (RFI) issued by the Florida Department of Transportation (FDOT) Office of Forecasting and Performance regarding modernization and enhancement strategies for the Project Suite Enterprise Edition (PSEE) system. FDOT is seeking vendor recommendations and solutions to support system capabilities, data migration approaches, and technology strategies for this centralized enterprise project management platform. The RFI is not a solicitation and does not constitute an offer to award a contract; responses will be reviewed for informational purposes only to inform future procurement decisions. The deadline for submitting questions is November 11, 2026, at 5:00 PM EST, with responses due on or before November 30, 2026, at 5:00 PM EST. FDOT is conducting a virtual Vendor Forum on November 4, 2026, from 1:00 to 3:00 PM EST via Microsoft Teams to demonstrate existing system functionality. Vendors are not excluded from participating in any resulting solicitation based on their RFI response.

Vendors are required to provide comprehensive information addressing company background and references, solution descriptions with platform type and deployment timelines, technology and security considerations including hosting models and integration methodologies, and responses to a detailed Capabilities Questionnaire. The RFI specifically requires vendors to address PSEE's integration with over twenty-five Department and external systems, authentication and authorization models, data migration practices from Oracle databases, reporting capabilities compatible with Power BI, document management through the Electronic Document Management System (EDMS), and compliance with Florida Administrative Code standards. Responses must be submitted in PDF format with a maximum file size of 25MB to Sherill Johnson, Procurement Agent, at CO.Purch@dot.state.fl.us, with the subject line formatted as "DOT-RFI-27-9037-SJ - (Insert Vendor's Name)." All information provided through the RFI process is subject to public disclosure under Florida Statutes Chapter 119 and may be used to develop scope and solicitation documents for future procurements.

View the file

Other files

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

FDOT PSEE RFI Page 1 of 6

State of Florida

Department of Transportation

Central Procurement Office

605 Suwannee Street, Mail Station 20

Tallahassee, Florida 32399-0450

REQUEST FOR INFORMATION

RFI Number: DOT-RFI-27-9037-SJ

Title: ProjectSuite Enterprise Edition (PSEE)

Deadline for Questions: November 11, 2026, at 5:00 PM EST

Response Due Date & Time (On or Before): November 30, 2026, at 5:00 PM EST

REQUEST FOR INFORMATION (RFI) from the Florida Department of Transportation

REQUEST FOR INFORMATION (RFI)

Florida Department of Transportation

Office of Forecasting and Performance

Introduction The Florida Department of Transportation (FDOT, Department) is seeking information/recommendations from experienced industry leaders (vendor, company) on specific solutions to best fit the Project Suite Enterprise Edition (PSEE) components and key features. FDOT is looking for vendors that can provide a solution to accommodate the system capabilities provided in this Request for Information (RFI).

The Department is asking for information on possible strategies and solutions to assist with modernization and enhancements for the Office of Forecasting and Performance (F&P) project management system which is the PSEE owned by the Office of Forecasting and Performance. To better communicate the existing functionality of this system, the Department will be conducting virtual demonstrations of the system during a Vendor Forum, on Wednesday, November 4, 2026, 1:00 – 3:00 PM EST. The Vendor Forum will be a Microsoft Teams meeting; you can join using your computer or mobile app, Click here to join the Vendor Forum.

Purpose of an RFI Rule 60A-1.042, Florida Administrative Code (F.A.C.), provides that an agency may request information by issuing a written Request for Information (RFI). Agencies are authorized to use an RFI for research to determine any or all the following: whether to competitively procure commodities or contractual services, what solicitation processes are recommended by Vendors to meet this need or general, special, and/or technical specifications to be included in future solicitation.

An RFI is not a solicitation. The Department is not required to utilize any information gathered through the RFI process, nor is a Vendor who responds to an RFI excluded from participating in any resulting solicitation. A Vendor’s response to an RFI is not an offer (Rule 60A-1.042, F.A.C) and the agency may not use the Vendor’s submission to justify a

DOT-RFI-27-9037-SJ

https://teams.microsoft.com/meet/217095593727808?p=iBN73WMUuKKgJbJw0R https://www.flrules.org/gateway/ruleNo.asp?id=60A-1.042 https://www.flrules.org/gateway/ruleNo.asp?id=60A-1.042

FDOT PSEE RFI Page 2 of 6 contract with that Vendor without otherwise complying with Chapter 287, Florida Statutes (F.S.). Vendor responses to this RFI will be reviewed for informational purposes only and will not result in an award of a contract.

Background The FDOT F&P office is exploring solutions from vendors which will assist the Department in determining future modernization and enhancement strategies for the following legacy system. The solution submitted during this RFI response must include strategies that will satisfy the capabilities of the PSEE system.

Project Suite Enterprise Edition (PSEE) – Provides FDOT project managers a formal centralized enterprise system, with real-time access to project data and multi-module support for viewing, changing and managing project information stored within the application and across other FDOT systems.

System Capabilities Refer to the Components and Key Features for details identified in the PSEE RFI Questionnaire Matrix.

Request for Information The Department is seeking information in support of solutions to assist with a determination on future modernization and enhancements of the PSEE system. Specifically, the Department is seeking the following information. Please answer each question below, in order by question number and subsection identifier.

1. Company Information: Provide the company information and proposed partner(s), as well as the following information related to customers that have benefited from this proposed solution(s):

a. Provide a list and contact information of other states, jurisdictions, and companies currently utilizing the solution(s).

b. Provide a complete list of the State Term Contracts or Alternate Contract Sources the Company is qualified for in the State of Florida.

c. Please include State of Florida Contract information on past or current deployment of the solutions being recommended to FDOT.

2. Solution Description: Describe the solution(s) and the recommended strategy for the modernization, data migration and enhancements of this system.

a. Identify the type of platform, Commercial-off-the-shelf (COTS), Software-as-a-Service (SaaS), Custom Design- Build, Framework, or a hybrid approach.

b. Provide a Gantt Chart (including duration) of the milestones and tasks typically executed with the deployment of the solution(s).

c. Identify the level of customizations over configuration required by the solution(s) that are needed to fulfill the system capabilities as outlined in Capabilities Questionnaire.

d. Describe the data migration strategy for the solution.

e. Provide the initial startup costs for the recommended solution, as well as the estimated yearly recurring cost for each submitted solution.

3. Technology and Security: Responses are required for the technology and security inquiries below.

a. Technology environment. The attached document, "Project Suite Enterprise Edition (PSEE) – Information Technology Environment Overview", describes the current PSEE architecture, technology stack, databases, integrations, reporting, security, and hosting, and must be a consideration within the submitted solution.

Provide a written response as to how your solution would work within this environment and which existing Department components it would continue to use. If the solution is not capable of working with an existing component, explain why, describe the changes or additions required, and explain how those changes would benefit the Department.

b. Hosting and operations. Describe the hosting model for the solution (Department-hosted, vendor-hosted, or cloud), the environments provided (development, test, and production), and how the solution is deployed, DOT-RFI-27-9037-SJ https://www.flsenate.gov/Laws/Statutes/2019/Chapter287

FDOT PSEE RFI Page 3 of 6 monitored, scaled, and recovered. Describe how your company would ensure that all data is stored in the United States.

c. Integration. PSEE integrates with more than twenty-five Department and external systems (Overview Section 4 and Appendix A) and exposes web services that other Department applications use (Overview Section 5). Describe your integration methodology, including real-time integration, for each of the following:

i. FDOT enterprise REST services consumed through the Arculus API gateway.

ii. Legacy SOAP web services.

iii. Data that PSEE reads directly from other Department systems' Oracle schemas. State whether the solution would preserve these read paths or require them to be moved to services.

iv. Updates that PSEE makes to Work Program and to Oracle Primavera P6.

v. Esri GIS services (FDOT Enterprise GIS).

vi. Interfaces the solution would provide so that other Department applications can export data from and import data into the solution.

d. Document management. All PSEE documents are stored in the Department's Electronic Document Management System (EDMS, OpenText eDOCS); PSEE holds only document metadata and EDMS identifiers.

Describe how the solution would continue to use EDMS as the document repository for upload, versioning, retrieval, and search.

e. Data migration. Describe your company's methods and practices for ensuring a successful migration of data from the PSEE Oracle database, including history and journal records and the links between PSEE records and the documents stored in EDMS.

f. Authentication. PSEE currently authenticates internal users with Windows Integrated Authentication (Active Directory) and external users with RACF and Internet Subscriber Account (ISA) credentials. The Department's preference for new solutions is Azure AD with OpenID Connect / OAuth 2.0 for internal users and Azure AD B2C for external users. Describe how the solution supports this.

g. Authorization. PSEE authorization is activity-based and district-scope, with privileges granted to individual users, Active Directory groups, and roles, and with delegation of work between users (Overview Section 8.2).

Describe how the solution would reproduce this model and identify what would be achieved through configuration and what would require customization.

h. Reporting and data access. PSEE generates Word, Excel, and PDF output and publishes nightly data extracts;

it has no business-intelligence or data-warehouse layer (Overview Section 7). The Department has a strong preference for a solution that exposes its data to self-service reporting tools such as Power BI. Describe the reporting capabilities of the solution and how its data would be made available to these tools.

i. Scheduled processing and notifications. PSEE runs scheduled batch jobs for data synchronization, reminders, and notifications (Overview Section 6). Describe how the solution handles scheduled and background processing and e-mail notifications.

j. Data protection and auditing. How will the solution address Personally Identifiable Information (PII) and exempt data (i.e., data considered sensitive or confidential)? Include how data is encrypted in transit and at rest, how credentials and other secrets are managed, and what audit logging of user activity and privilege changes the solution provides.

k. Maintenance. What is the typical maintenance that is anticipated for this solution, and what is the process for enhancements and configuration during a typical maintenance cycle?

l. Product roadmap. Please describe enhancements currently under development and any future planned enhancements and provide a product roadmap for the next three (3) years.

m. Technology and Standards compliance. Can the company comply with the Technology and Security Standards, and other obligations as outlined in Florida Administrative Code, Rule Chapter 60GG-1 - 60GG-5?

4. Miscellaneous Information: Please provide any additional information that you feel would be helpful to the Department concerning your proposed solution.

5. Capabilities Questionnaire: Please complete the questions identified in the workbook Capabilities Questionnaire and provide comments when additional information is necessary.

FDOT PSEE RFI Page 4 of 6

The Department may exercise the option to invite any prime Vendor that fully responds to the questions above to meet and discuss the information provided in more detail and a demonstration of the solution may be requested by the Department. Any information provided via this RFI and during the meetings will be subject to public disclosure.

Contacts for Questions/Clarifications

Sherill Johnson, Procurement Agent at CO.Purch@dot.state.fl.us

The requested package submissions must be received by November 30, 2026, at 5:00 PM EST .

E-mail to: CO.Purch@dot.state.fl.us

NOTE: Responses to this Request for Information (RFI) will be reviewed by the Department for informational purposes and will not be considered as offers to be accepted by the Department to form a binding contract. Advertisements of any subsequent competitive solicitation that may result from this RFI will be posted on the Florida Vendor Information

Portal.

Information obtained by the Department in response to this RFI is subject to Chapter 119, Florida Statutes. Further, in accordance with Chapter 287, Florida Statutes, information obtained in response to this RFI may be used to develop scope and solicitation documents for future procurements at the discretion of the Department. Respondents to this RFI are not excluded from participating in any resulting solicitation.

INSTRUCTIONS FOR ELECTRONIC SUBMISSION OF REPLIES

Please follow the instructions below:

• Replies shall be submitted to: Sherill Johnson, Procurement Agent at CO.Purch@dot.state.fl.us

• The subject line must show: DOT-RFI-27-9037-SJ – (Insert Vendor’s Name)

• All replies submitted electronically shall contain file attachments and be marked as follows:

RFI – (Insert Vendor’s Name)

Include all required information.

NOTES:

• Documents shall be submitted in portable document format (PDF) and have a size limit of 25MB.

• The body of the email shall not contain any information.

• It is the Respondent's responsibility to assure that the reply is delivered to the proper place or via email on or before November 30, 2026, at 5:00 PM EST.

• A confirmation notice will be sent to each Respondent when the Response is received. Do not copy anyone on your submittal email.

mailto:CO.Purch@dot.state.fl.us mailto:CO.Purch@dot.state.fl.us

FDOT PSEE RFI Page 5 of 6

Appendix A: Important terms and abbreviations

• Activity Code: Used as an identifier for each scheduled activity in a project schedule. Ex. 280000000 means letting.

• Contract File Index (CFI): All certifications that are required for advertising a construction project for a bid.

• Construction Estimate: An estimate FDOT prepares based on expectations of parts and labor required to perform the tasks necessary to bring a Project (defined below) to completion.

• Countermeasures: A set of measures and design features proven to reduce safety risk.

• Current Approved Scope (CAS): All activities required within a Project (defined below).

• Design Approval Request (DAR): An approval process for varying from standardized designs.

• Design Development Documentation (DDD): Supports compliance with Chapter 111.7 of the FDOT Design Manual and ensures proper documentation throughout the design process by organizing and retrieving documents used for developing construction plans.

• Errors & Omissions (E&O): The recouping of money for obstacles found during construction which result in premium construction costs.

• Enterprise Information Portal (EIP): A searchable information portal which allows internal users to access select information from internal databases.

• Electronic Document Management System (EDMS): An FDOT product used for document storage, retrieval, and versioning control.

• Electronic Review Comments (ERC): An FDOT product used by contractors to ask questions, make comments, and receive answers on documents.

• Environmental Documents: Project documents specific to the environmental impacts of a construction project.

• Environmental Report: An electronic output of environmental information provided in standardized report format.

• Engineer of Record (EOR): The Professional Engineer or Engineering Firm registered in the State of Florida that develops the criteria and concept for the project, performs the analysis, and is responsible for the preparation of the Plans and Specifications.

• Estimate: see Construction Estimate.

• Float: Scheduling terms for the amount of flexibility given a series of activities and their expected durations used in project management.

• For Your Information (FYI): A person designated to be informed of changes.

• GIS Enterprise View (GEV): A customized ESRI Product used to view GIS information.

• Internet Subscriber Account (ISA): An account used by non-FDOT users to access limited PSEE functionality.

Outdated technology is to be replaced by B2C and similar technologies.

• One-Stop Permitting (OSP): A separate FDOT product used by FDOT customers to request permits.

• Plans, Specifications, and Estimates (PS&E): The PS&E Package module allows the submittal of the PS&E Package to be entered and routed electronically from the Engineer of Record through the various review levels at the District and Central Office all the way to the Contract Office for Advertisement. The module was created to ensure the timely submittal and review, along with the improvement to the storage and availability of the associated documents.

• Project: A clearly defined work request put forth by FDOT.

• Phase: In PS&E, it refers to lifecycle development milestones (Ex. Biddability or constructability). Under Change Management, it refers to specific financial phase types (Ex. 32 means money allocated for design).

• Phase Review: A formal milestone in the design process (e.g. 30%, 60%, 90%, etc.) where FDOT reviews the plans and other required deliverables submitted in ERC, to make sure the project meets criteria, is constructable, ready for bidding, and technically correct. Each phase review focuses on different goals and levels of completion.

• Primavera: The software that FDOT uses to track the working day-to-day activities for each project.

FDOT PSEE RFI Page 6 of 6

• Project Fact Sheet: A report which serves as a communication tool for the public and contractor community, providing essential project details in a standardized format. Commonly single page.

• Project Manager (PM): The staff member(s) responsible for a given project.

• Project Scheduling and Maintenance (PSM): An FDOT application that tracks the project schedule.

• Project Suite Enterprise Edition (PSEE): An FDOT application for project management and project research.

• Push Button Work Order: A task assignment issued under a specific type of contract (push‑button contract) for projects that require quick, efficient, on‑demand work. FDOT provides the scope for the type of work under the contract, and issues specific work orders when and where the work is needed.

• Right of Way Management System (RWMS): An FDOT application for the management of Right of Way.

• Submittal: Any documents, files, plans, reports or other required project items delivered to FDOT (at required milestones like Phase Reviews) so FDOT can review progress and assure quality.

• Transportation Vendor Information (TVI): An FDOT application that stores vendor information.

• Utility Agency Owner (UAO): Any person, business, or government agency that owns utility lines—like power, water, gas, or communication—located within FDOT right of way.

• Work Program (WP): The rolling 5-year list of projects that FDOT is responsible for delivering.

• Work Program Update Cycle (WPUC): The portion of time in each fiscal year that FDOT staff works to update the construction cost estimate for projects.

State of Florida
Department of Transportation
Central Procurement Office
605 Suwannee Street, Mail Station 20 Tallahassee, Florida 32399-0450
REQUEST FOR INFORMATION
REQUEST FOR INFORMATION (RFI)
Introduction
Purpose of an RFI
Background
System Capabilities
Request for Information
Contacts for Questions/Clarifications
INSTRUCTIONS FOR ELECTRONIC SUBMISSION OF REPLIES
Appendix A: Important terms and abbreviations

File details come from the government source that posted it. Updated .