9037 - PSEE-RFI-Technical Environment.pdf

PDF 1021 KB Posted

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

About this file

This file is a supporting document for a Request for Information (RFI) issued by the Florida Department of Transportation (FDOT) regarding ProjectSuite Enterprise Edition (PSEE), the state's enterprise application for managing project-related information across the transportation project delivery lifecycle. The document provides a comprehensive technical overview of PSEE's current environment, including its system architecture, functional scope, integrations, and security framework. PSEE, in production since August 2010, serves FDOT's Central Office, seven Districts, and Florida's Turnpike Enterprise, and is used by FDOT staff, consultants, local agencies, and external utility agencies. The application manages work program financial projects and aggregates data from numerous Department systems while providing transactional modules for change requests, permits, environmental compliance, design approvals, scheduling, and utility coordination. The codebase comprises approximately 434,000 lines of C# across 3,000 source files, with 86 pages, 680 user-control views, approximately 190 Word-format reports, and 229 object-relational mappings.

PSEE operates as a Microsoft ASP.NET Web Forms application on Internet Information Services with an Oracle database backend, employing a three-tier architecture consisting of UI, service, and repository tiers. The system integrates with more than twenty-five Department and external systems through multiple protocols including REST/JSON, SOAP, direct database access, GIS services, and platform services for identity management, email, and telemetry. Authentication is provided through Windows Integrated Authentication for the intranet site and RACF or Internet Subscriber Account credentials for the external site, with authorization enforced at the service tier using an activity-based, district-scoped permission model. The application exposes ASMX SOAP web services for data export, import, and administration to other Department applications, and maintains ten scheduled batch jobs for data synchronization, reporting, and notifications. PSEE's reporting infrastructure includes approximately 190 Word-format module reports, 21 RDLC report definitions for forms and memoranda, Excel exports through the Open XML SDK, and nightly data extracts to SQL Server and Azure SQL Database. The system is deployed in four environments (workstation, unit test, system test, and production) and hosted on IIS Windows Server with in-process session state management and deployment through Octopus Deploy.

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

ProjectSuite Enterprise Edition (PSEE) — Information Technology Environment

Overview Supporting information for Request for Information respondents

September 2026

Table of Contents

1. Overview of ProjectSuite Enterprise Edition ProjectSuite Enterprise Edition (PSEE) is the Florida Department of Transportation’s (FDOT) enterprise application for requesting, reviewing, and managing project-related information across the project delivery life cycle. It is used statewide by Central Office and all seven Districts plus Florida’s Turnpike Enterprise, by FDOT staff, consultants, local agencies, and external Utility Agency/Owners (UAOs).

PSEE is organized around the Work Program financial project (Item / Item Segment). For each project it aggregates data from a large number of Department systems into a single project view and layers transactional modules on top: change requests and change management, commitments, permits, environmental compliance, design approval requests, phase reviews, resolution tracking, survey work orders, plans/specifications/estimates (PS&E) submittals, utility coordination, scheduling, and a project journal.

PSEE is developed and maintained in-house by the Office of Information Technology (OIT).

The application has been in production since August 2010 and has been continuously extended since; the current code base is approximately 434,000 lines of C# across 3,000 source files, with 86 pages, 680 user-control views, roughly 190 Word-format reports, 229 object-relational mappings, and ten production batch jobs scheduled in ActiveBatch.

2. Functional Scope PSEE presents each project as a set of modules. Modules are either view-only (data sourced from other Department systems) or transactional (data owned by PSEE).

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE) Information Technology Environment Overview

2.1 View modules (data sourced from other systems)

Module Source system(s)

Project header, location, work mix, phases, funding

Work Program Administration (WPA)

Contracts (professional services, construction, task work orders, invoices, encumbrances)

CITS, IEI, Financial Management (FM), Trns*port / SiteManager

Financial (estimates, long range estimates, trends, encumbrances, bill control)

ERTS (Estimates), CES, FM, CITS

Documents (enterprise document search) EDMS (OpenText eDOCS) Superfile index (Azure SQL)

Electronic Review Comments (ERC) ERC web service

GIS / Project Impacts (cities, counties, legislative districts, school zones, zip codes, as-built plans, straight-line diagrams, intergovernmental agreements)

FDOT Enterprise GIS (ArcGIS Server), RCI, EDMS

Item Segment Change History WPA history tables

Local Agency Program Grant Application Process (GAP) service, IEI; LAPIT web service (printed report only)

Project Scheduling (PSM) milestone dates PSM tables

Related Projects WPA

Right of Way commitments and parcels RWMS

Bridges BMS

Video Log (disabled; not required in a future solution)

Video Log application (embedded viewer)

STIP vendors TVI vendor tables

2.2 Transactional modules (data owned by PSEE)

Transaction Modules:

• Address Book (internal and external contacts)

• Approved Scope

• Commitments

• Design Approval Requests

• Design Development Documentation

• Environment (environmental compliance and ETDM)

• External Agency

• Permits, Phase Review

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

• Project Fact Sheet

• Project Status

• PS&E Package (submittals, revisions, transmittal memos, certifications, wage rates)

• Resolution Tracking (RTM)

• Survey Work Orders

• Utilities (Utility Permit Coordination, UPC)

• Change Requests (Change Management, Initial Project Request, Scheduling, Estimate, Scope, WP Data, and WP Funding change requests with change-request packages and workflow)

• Resilience tracker

• Safety Countermeasures

• Push Button work orders

• Project Journal

• Project Alerts.

PSEE also provides an administration area for managing modules, privileges, code tables, project manager assignments, and delegation (“work as”) relationships; a My Assignments dashboard; advanced project search with Excel export; and a printing facility that assembles selected modules into a Word document.

• 3. Current System Architecture

3.1 Application architecture

PSEE is a Microsoft ASP.NET Web Forms application running on Internet Information Services (IIS) on Windows Server, with an Oracle database. The solution follows a decoupled three-tier design:

• UI tier — the ASP.NET Web Forms site (ProjectSuiteWeb), a set of ASMX and WCF web services, and a set of console applications that run unattended on the Department’s batch job server under ActiveBatch scheduling (ten in the production plan). The web site follows a single-page-application pattern in which server-rendered user controls are requested through web services and injected into the page; input controls are generated dynamically from business object metadata.

• Service tier — a single ServiceProvider class (partial class, ~24 files) that defines every business action. Each action is attributed with a Business Module Activity key that ties it to the authorization model, validates the affected business objects, returns an operation context carrying business-rule results, and raises notifications and journal entries on successful commit.

• Repository tier — NHibernate object-relational mapping over Oracle with classic XML mappings (229 mapping files, 24 session-factory configurations), plus a limited amount of native SQL through NHibernate and raw ADO.NET.

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

Supporting projects include a shared FDOT ORM framework (FDOT.Application.Model:

unit-of-work provider, repository base classes, custom Oracle dialect and driver), reusable Web Forms controls, GIS data contracts, and MSTest integration test projects that run against a live Oracle unit-test database.

There is no dependency-injection container; object construction is explicit. Session state is in-process. Configuration values that vary by environment are injected at deployment time by Octopus Deploy variable substitution, and secrets (connection strings, API keys, service credentials) are resolved at run time by the FDOT Enterprise Library (FEL5) rather than stored in configuration files.

3.2 Software, languages, and platforms

Category Technology

Language / runtime C#, Microsoft .NET Framework 4.5.2 (web application and most projects); 4.7.2 (reporting export jobs); one .NET 5 loader outside the main solution

Web framework ASP.NET Web Forms (.aspx / .ascx), ASP.NET AJAX, ASMX (SOAP 1.1) and WCF web services, HTTP handlers

UI component libraries Telerik UI for ASP.NET AJAX 2021.1, AJAX Control Toolkit 3.5, jQuery 1.4 / 1.7 and jQuery UI 1.8, Karamasoft UltimateSpell 3.6; legacy Silverlight multi-file-upload control (retired technology, still present in the code base)

Object-relational mapping NHibernate 3.3.5 with SysCache second-level cache, Castle proxy factory

Database access Oracle Data Provider for .NET (ODP.NET, unmanaged Oracle.DataAccess 12c client); System.Data.SqlClient for SQL Server targets; CA-Gen generated COM component for Work Program updates

Reporting / document generation Open XML SDK (Word and Excel generation), Microsoft ReportViewer 2012 (RDLC, local processing mode, PDF rendering), EPPlus

Enterprise libraries FDOT Enterprise Library FEL5 (Core, DBConnect, ISA, SRS, Active Directory clients), FDOT.Enterprise 4.x (Staff, OrgCodes, EmailRelay clients), EO

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

Category Technology framework (Core, Graph client), GAP service client

Logging / telemetry log4net (rolling file), Azure Application Insights 2.21 (web tracking, dependency and performance-counter collection), e-mail and Windows Event Log error sinks

Serialization / HTTP Newtonsoft.Json 12, HttpClient / HttpWebRequest, ASP.NET Web API client formatting

Mail Simple Mail Transfer Protocol (SMTP) through the FDOT enterprise e-mail relay

Directory / identity Microsoft Active Directory (Windows Integrated Authentication), RACF membership provider, FDOT Internet Subscriber Account (ISA), Microsoft Graph

Source control and build Git; Visual Studio 2019 / MSBuild; NuGet (packages.config) with a number of Department and vendor assemblies checked into the repository; no automated build pipeline in the repository

Deployment Octopus Deploy variable substitution into web.config / app.config

3.3 Database platforms

Platform Use

Oracle Database (primary) PSEE application schema (PSEDBA, ~155 tables and 20 sequences); read-only access to the schemas of other Department systems hosted in the same Oracle environment (Work Program, CITS, FM, IEI, RWMS, TVI, RCI, BMS, BSS, DOT

Codes history, CES); eight Primavera P6 district schemas; mainframe-sourced staff tables exposed in the Oracle environment (OTG4DB2DBA schema)

Microsoft SQL Server District Primavera reporting tables (p3ecmain, Districts 2, 3, 6 and Turnpike) loaded nightly

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

Platform Use

Azure SQL Database EDMS Superfile document index (EDMSDBA.EDCV001_REC, migrated from Oracle in July 2025); consolidated Primavera schedule reporting table (PrimaveraStProjectActivities) loaded nightly

DB2 (mainframe) No direct connection from PSEE.

Mainframe-hosted staff data is consumed through the Oracle environment; the DB2 client remains a deployment prerequisite for the enterprise libraries

Connection strings are identified in configuration by label (for example PSENET_U, PSEBJS_U, PSEEPM_R, PSEEDC_R, PSMTABS_U) and resolved to credentials at run time by FEL5.

The web application and the batch jobs use separate Oracle accounts.

3.4 Protocols

HTTP/HTTPS, SOAP 1.1 (ASMX and WCF basicHttpBinding), REST/JSON, multipart chunked file upload, Oracle Net (SQL*Net), TDS (SQL Server), SMTP, NTLM/Kerberos (Windows Integrated Authentication), OAuth 2.0 client credentials (Microsoft Graph), COM interop (Work Program update component), and the Esri ArcGIS REST API.

4. Integrations PSEE integrates with more than twenty-five Department and external systems. Integrations fall into five categories: FDOT enterprise (Arculus / Azure API Management) services, application web services, direct database access to other systems’ schemas, GIS services, and platform services (identity, e-mail, telemetry). A consolidated inventory with direction, protocol, and authentication method for every integration is provided in Appendix A.

4.1 Enterprise services (Arculus / Azure API Management)

FDOT’s enterprise RESTful services are consumed through the Arculus API gateway, authenticated with an Azure API Management subscription key. PSEE uses the current REST versions of these services:

• Staff Service — every user, staff, and contact lookup in PSEE (login resolution by RACF ID, address book, contact pickers, notification recipients, consultant lists).

Staff attributes (name, e-mail, district, organization, position, status) are not stored in PSEE; they are read from the Staff Service. Staff signatures are written back through the FDOT.Enterprise Staff client.

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

• DOT Codes Service — all enterprise code tables and related-code lookups used by the application’s drop-down lists. Historical (inactive) codes are additionally read from the DOT Codes history table in Oracle.

• Org Code Service — organizational code decoding for staff records.

• EDMS Service — document management through OpenText eDOCS. PSEE uses a

PSEE-owned REST client against the Arculus EDMS API for document creation (chunked upload), versioning, metadata update, deletion, and download. All PSEE documents are stored in EDMS under the PSEE business area; PSEE stores only document metadata and EDMS identifiers. Document viewing is delegated to the per-library EDocumentServer viewers (Central Office, Districts 1–7, Turnpike).

Enterprise-wide document search uses the EDMS Superfile index.

• Grant Application Process (GAP) Service — local agency agreements, organizations, vendors, and contracts shown in the Local Agency Program module, and the local agency filter in project search.

• Arculus Configuration API — issues and validates the key required by the readiness health-check endpoint.

• Internet Subscriber Account (ISA) and FEL5 Active Directory services — external user accounts and Active Directory group membership (see Section 8).

• Construction SIM (SiteManager) service — consumed by a stand-alone loader that pulls construction change orders into PSEE.

4.2 Application web services (SOAP)

System Purpose in PSEE Notes

Electronic Review Comments (ERC)

Submittals and comment threads by financial project ID or submittal ID; linked from ERC, Design Approval Request, and Phase Review modules

ASMX SOAP, anonymous

ERTS / MyEstimates (Enterprise Information Assets)

Construction and right-of-way estimate trends in the Financial module

ASMX SOAP, Windows

(NTLM)

LAPIT (Local Agency Program Information Tool;

legacy, replaced by GAP)

Local agencies and their agreements in the Local Agency Program section of the printed Word reports.

The on-screen module reads from the GAP service (Section 4.1)

ASMX SOAP, Windows

(NTLM)

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

System Purpose in PSEE Notes

ETDM / Environmental Screening Tool (fla-etat.org, external)

Validation of ETDM project identifiers entered in the Environment module

SOAP over HTTPS through the Department’s outbound proxy

Oracle Primavera P6 EPPM web services

Read projects, activities, and codes; write activity dates, project descriptions, project and activity codes, and code assignments. One P6 instance per District and Turnpike

P6 SOAP services with username/password login per district

Work Program (CA-Gen component)

Writes the external agency assignment on Item Segment Locations back into Work Program

CA-Gen generated COM component (Wpaps047)

4.3 Direct database access to other Department systems

PSEE reads the following systems’ tables and views directly through NHibernate mappings in the Oracle environment. This direct database access is read-only. Where PSEE updates another system’s data, it does so through that system’s own interface rather than its tables: the external agency assignment on Item Segment Locations is written to Work Program through the CA-Gen component, and activity dates, descriptions, and codes are written to Primavera P6 through the P6 web services (Section 4.2; Appendix A, items 18 and 21).

System Data used

Work Program Administration (WPA / FM) Item segments, locations, groups, work mix, phases, cost estimates, super-file, change history, related projects; PSEE-owned search view

Project Scheduling / Milestones (PSM) Activity and milestone dates

CITS (Consultant Invoice / Contract Tracking)

Contracts, project contracts, work orders, invoices, encumbrances, compensation elements

Financial Management (FM) Encumbrance lines, financial project bill control

IEI Contracts, projects, contract-project links, vendors

Trns*port / AASHTOWare SiteManager Construction contracts, change orders, change-order items, key dates

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

System Data used

CES (Trns*port Estimator) Estimate jobs and snapshots

CCTS (construction change orders) Change orders and line items feeding Resolution Tracking issues

RWMS (Right of Way Management System) Parcels, real-estate interests, resource addresses and phones, construction commitments

TVI (Vendor information) Outside accounts, account addresses, address purposes

RCI (Roadway Characteristics Inventory) Roadway sections, features, extracts

BMS (Bridge Management System) Public bridge inventory

BSS (Business Support System) Invoice reviewers, system users

Mainframe staff data (Business Support System)

Staff members and staff connectors

DOT Codes (ISS) Code and code-history tables

Location reference Airports and seaports

Primavera P6 (eight district schemas) Projects, WBS, activities, activity codes and types, project codes, calendars, OBS, users, profiles

EDMS Superfile (Azure SQL Database) Enterprise document index for search and straight-line diagrams

4.4 GIS

PSEE has adopted the Esri platform through FDOT’s Enterprise GIS (GEV) ArcGIS Server REST services at gis.fdot.gov: the Work Program Current, Administrative Boundaries, RCI Layers, and Transportation map services, and the Geometry service (buffering). The GIS module renders project maps, performs spatial impact queries (cities, counties, congressional, Florida House and Senate districts, school zones, zip codes), and produces map images for the printed reports. The Esri ArcGIS Online World Street Map is used as the base map. District 4 contributes an additional local map service. Esri resource proxies are hosted in the application for the UPC and permit map views.

4.5 Identity, e-mail, and telemetry platforms

• Microsoft Active Directory — Windows Integrated Authentication for the intranet site against the consolidated DOT domain; Active Directory security groups define PSEE administrative roles and group-based privileges. Group membership is resolved through Microsoft Graph (Azure AD, OAuth 2.0 client credentials) and the FEL5 Active Directory service.

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

• RACF / ISA — the FDOT common login control on the external site supports RACF credentials and Internet Subscriber Accounts.

• SMTP — all notifications, reminders, and error alerts are sent through the FDOT enterprise e-mail relay from a no-reply address.

• Azure Application Insights — request, dependency, and exception telemetry.

• Health probes — /health/live and /health/ready endpoints in the FDOT health-check format; readiness probes the PSEE database, the EDMS Superfile database, and the eight Primavera databases and web services.

4.6 Hyperlink integrations

PSEE links users in context to the EDMS EDocumentServer viewers, the Contract Information Monitoring (CIM) system, the Enterprise Information Portal vendor search, the GIS Enterprise Viewer, the ISA account portal, the ETDM public site, the ERC web site, Video Log viewer (embedded, URL configured per module; module currently disabled), and help and training content hosted on SharePoint and the FDOT web site.

5. Interfaces Exposed by PSEE PSEE exposes ASMX SOAP web services that other Department applications and PSEE’s own batch jobs consume. They are protected by the site’s Windows authentication and are not available on the Internet-facing deployment.

Service Purpose

ExportDataService.asmx (54 methods) Read-only, paged export of projects, Primavera projects and activities, PSM activities, project statuses, contacts and staff, permits, fees and mitigations, documents, change requests, commitments, environmental data, design approval requests, survey work orders, journals, and resolution tracking issues

ImportDataService.asmx (52 methods) Creation of project statuses, contacts, permits and permit details, estimate / scope / WP data / WP funding change requests, and design approval requests, with documents. Requires the Import Data privilege for the target district

ProjectStatusService.asmx Project statuses and document metadata for a financial project

AdminDataService.asmx (23 methods) Business area, module, activity, and code-table administration

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

Service Purpose PSEEConfigService.asmx Run-time configuration feed for the batch jobs

StaffPickerService.asmx, ExternalContactPickerService.asmx

AJAX services supporting the user interface

6. Scheduled Batch Jobs Batch jobs are .NET console applications defined in the ActiveBatch “PSEE” plan and executed on the Department’s batch job server under a dedicated batch service account.

Each job is wrapped by a common harness that logs to the console, sends failure e-mail to the PSEE error mailbox, and returns a non-zero exit code to ActiveBatch on error. Jobs read run-time configuration from the PSEE web site’s configuration service. All production schedules run Monday through Friday unless noted; ActiveBatch retries a failed job once and retains logs and history for one year.

Job Production schedule Function Systems touched

PSEE Primavera Load

05:00 Synchronizes PSEE project attributes (work mix, county, status, contract class, managers, letting data) into Primavera P6 project codes for every district;

maintains PSEE-to- P6 project links

Primavera P6 databases and web services

PSEE RTM Load 05:25, Monday through Saturday

Creates Resolution Tracking issues from new construction change orders and line items; removes obsolete issues

CCTS / SiteManager tables

PSEE Export Reporting Data

03:00 Extracts Primavera schedule and activity data into the District SQL Server reporting tables

Primavera P6, SQL Server

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

Job Production schedule Function Systems touched

PSEE Export Reporting Data New

02:00 Extracts the same Primavera schedule data into the consolidated Azure SQL reporting table

Primavera P6, Azure

SQL

ProjectSuite.Chang ePackageHoldRelea se

05:45 and 12:00 Resumes change-request packages whose hold date has expired

PSEE, e-mail

ProjectSuite.SendDr aftChangeRequestP ackageReminders

05:45 E-mails project managers with draft change packages

PSEE, e-mail

PSEE Send Wpa Hold Reminder

05:45 E-mails reminders for packages on Work Program hold

PSEE, e-mail

PSEE Yearly Update List Candidate

03:15 Regenerates the yearly update candidate list for the Work Program Update Cycle modules, which are no longer used; the job is still scheduled

PSEE

PSEE Send Pending Summary Notification

07:30 and 12:30 (job currently disabled)

Sends digest e-mails of pending notifications

PSEE, e-mail

PSEE Utility Assignment Reminders

07:00 (job currently disabled)

E-mails internal reviewers and external utility company users about utility assignments due, due today, past due, and utility work

PSEE, e-mail (external recipients)

The solution also contains four console jobs that are not scheduled in production: an Inactive Users check (notifies project managers of open assignments held by inactive staff), a Project Alerts evaluator, a one-time EDMS document description update, and a SiteManager change-order loader that reads the Construction SIM service.

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

7. Reports PSEE reporting is delivered inside the application; PSEE does not use WebFOCUS, Managed Reporting Environments, or a business-intelligence platform.

• Printed module reports (Word) — approximately 190 report classes generate Office Open XML (.docx) documents from the business objects using a metadata-driven engine. Users select the modules to include for a project, a change-request package, or a search result and receive a Word document. A Project Status Book and Project Impacts report are produced the same way.

• RDLC reports (ReportViewer, local mode) — 21 report definitions for forms and memoranda: Project Fact Sheet, Front Desk report, Environmental report, Utility Plan report, permit transmittal memoranda, PS&E transmittal and revision memoranda, CFI forms, quantity summaries, commitment records, UPC invoice and work-schedule status. PDF output is rendered from these definitions.

• Excel exports — advanced search, dashboards, and project impacts export to .xlsx through the Open XML SDK.

• Map images — project maps are composed from Enterprise GIS map services for inclusion in reports.

• Reporting data extracts — a nightly job publishes Primavera schedule data to district SQL Server tables and to an Azure SQL Database table that District and Central Office staff use with their own reporting tools.

• Data services — the export web service (Section 5) provides paged, read-only access to PSEE data for other systems.

There is a strong preference for a future solution to expose PSEE data to self-service reporting tools such as Power BI.

8. Security

8.1 Authentication

PSEE is deployed as two sites:

• Intranet site (projectsuite.dot.state.fl.us) — Windows Integrated Authentication against FDOT’s on-premise Active Directory. The Department has consolidated its former per-district domains into a single DOT domain. Anonymous access is denied. The user’s RACF identifier (Active Directory account name) is resolved to an FDOT staff record through the Staff Service, and a PSEE user record is created automatically on first use.

• Internet site (psee.fdot.gov) — the FDOT common login control with two credential types: RACF credentials for FDOT staff and consultants who hold an FDOT RACF ID (RACF membership provider), and Internet Subscriber Account (ISA) credentials

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE) for external Utility Agency/Owner users who do not. ISA users are provisioned automatically, assigned the limited PSEE application role in ISA, and directed to the Utility Permit Coordination dashboard.

The application does not currently use Azure Active Directory as an identity provider (no OpenID Connect or SAML integration). Azure AD is used only as a service credential for Microsoft Graph group lookups. Batch jobs authenticate as the Windows service account they run under.

8.2 Authorization

Authorization is activity-based and district-scoped, and is enforced in the service tier on every business action.

• Permission catalog — a hierarchy of Business Areas, Business Modules, and Business Activities stored in the PSEE schema and administered in the application.

Each service-tier action is bound to an activity key. Modules can be enabled per district and flagged for external (Internet) use.

• User privileges — activities are granted to individual users per managing district (or Statewide).

• Active Directory group privileges — activities may also be granted to an Active Directory group per district; membership is resolved through Microsoft Graph and cached.

• Roles — System Administrator, Statewide Administrator, District Administrator, per-district Project Manager Assignment Administrators, and statewide/district reviewer roles are defined by membership in named Active Directory security groups (for example CO-PSEE-SystemAdmin, FDOT-PSEE-DistrictAdmin). Utility, PS&E, and Resilience administrators are defined by privileges. Access requests are made through the Department’s access request (AARF) process.

• Project Manager — the Work Program project manager of record has implicit privileges on their own projects, subject to a defined exclusion list and business rules.

• Delegation (“work as”) — a user may delegate to other staff, who then act with the delegator’s privileges; delegations are stored in PSEE and re-validated on every request.

• Guests — authenticated users without a staff record are treated as guests with read-only access to non-privileged modules.

• Business rules — beyond privilege checks, many activities have state-based rules (for example, an issue may be added only when the project has construction contracts).

Privilege grants generate e-mail notification to the grantee. Privileges held by inactive staff are removed automatically.

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

8.3 Secrets and transport

Secrets are not stored in source control or in deployed configuration files. Configuration files contain Octopus Deploy placeholders; connection strings, API subscription keys, EDMS service credentials, Graph client credentials, and the Application Insights key are supplied at deployment time and resolved at run time by FEL5. Developer workstations use local secrets files outside the repository. Enterprise service calls (Arculus, EDMS, Primavera, GIS, ISA) use HTTPS; several legacy internal SOAP services (ERC, ERTS, LAPIT) remain on HTTP inside the Department network.

8.4 Auditing and logging

PSEE records module usage per user, creating-user and last-updated-user information on its transactional tables, and a business journal (project log) of module activity driven by each module’s notification settings. Application and error logging is written to rolling log files, the Windows Event Log, the PSEE error mailbox, and Application Insights.

9. Hosting, Environments, and Operations Aspect Current state

Web hosting IIS on Windows Server, integrated pipeline, .NET Framework 4.x; separate internal and external-facing web servers

Environments Workstation, Unit (development), System Test, and Production, selected at run time by the FEL5 environment level, with per-environment endpoints and keys for every integration. Site addresses are listed below

Session and scale-out In-process ASP.NET session state with a 20-minute timeout; the current configuration assumes a single web server or session affinity

Batch ActiveBatch “PSEE” plan on the Department’s batch job server; jobs run under a dedicated batch service account, retry once on failure, and keep logs and history for one year

Deployment Octopus Deploy variable substitution;

builds produced with Visual Studio / MSBuild

Monitoring Application Insights; FDOT health-check endpoints (/health/live, /health/ready)

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

Aspect Current state with key authentication and rate limiting; e-mail error alerts to the PSEE errors mailbox

Test banner and impersonation Non-production environments show a test banner and allow designated tester groups to impersonate district administrators; role override is disabled in production

Database environments Oracle unit-test and system-test instances (D9UT31, D9TST31, D9UT34, D9TST34) with corresponding production instances

Environment Internal (intranet) site External (Internet) site

Development https://projectsuitedev.dot.

state.fl.us https://pseedev.fdot.gov

Test https://projectsuitetest.dot.

state.fl.us https://pseetest.fdot.gov

Production https://projectsuite.dot.stat e.fl.us https://psee.fdot.gov

10. Technology Considerations for Respondents The following characteristics of the current system are relevant to any modernization, replacement, or integration proposal:

• The user interface is ASP.NET Web Forms with server-generated user controls, Telerik AJAX controls, and jQuery 1.x. Retired Silverlight upload controls and a WCF binary upload service remain in the code base alongside an HTML5 replacement.

• Data access is NHibernate 3.3 over the unmanaged ODP.NET provider, with mappings that read directly from a large number of other systems’ Oracle schemas.

Any replacement must either preserve those read paths or move them to services.

• The business layer is a single service class with activity-level authorization; the authorization model (business area, module, activity, district scope, group privileges, roles, delegation) is a core requirement that a replacement must reproduce.

• Documents are stored exclusively in OpenText eDOCS through the Arculus EDMS API; PSEE holds metadata only.

• Reporting is application-generated Word, Excel, and PDF output, with nightly extracts to SQL Server and Azure SQL; there is no BI or data-warehouse layer today.

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

• Identity is Windows Integrated / RACF / ISA today; the Department’s preference for new integrations is Azure AD with OpenID Connect / OAuth 2.0, and Azure AD B2C for external public users.

Appendix A. Integration Inventory Direction is from PSEE’s perspective. “Key” means an Azure API Management subscription key presented through the Arculus gateway.

# System Direction Protocol / technology

Authenticati on PSEE feature

1 FDOT Staff Service (Arculus)

Read;

signature write via Staff client

REST/JSON Key All user, staff, and contact lookups

2 FDOT DOT Codes Service (Arculus)

Read REST/JSON Key Code tables application-wide

3 FDOT Org Code Service (Arculus)

Read REST/JSON Key Organization decoding

4 EDMS Service (Arculus / OpenText eDOCS 16.x)

Read / Write REST/JSON, chunked multipart upload

Key + EDMS library credentials (token)

All document upload, versioning, download

5 EDMS

EDocumentServer viewers (CO, D1–D7, TP)

Link HTTPS User session Document viewing

6 EDMS Superfile index Read Azure SQL Database (NHibernate;

Oracle until July 2025)

Database account

Enterprise document search, straight-line diagrams

7 Grant Application Process (GAP) Service

Read REST/JSON Key Local Agency Program module, local agency search filter

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

# System Direction Protocol / technology

Authenticati on PSEE feature

8 Arculus Configuration

API

Read REST/JSON API key Health-check key validation

9 Internet Subscriber Account (ISA)

Read FEL5 client FEL5 API key External user login and lookup

10 FEL5 Active Directory Service

Read FEL5 client FEL5 API key User group membership

11 Microsoft Graph (Azure AD)

Read REST/JSON OAuth 2.0 client credentials

Security group membership for roles and group privileges

12 Active Directory (on-premise, consolidated DOT domain)

Read Windows Integrated Authenticati on

Kerberos/NT

LM

Intranet login

13 RACF (mainframe security)

Read FDOT RACF membership provider

RACF

credentials

External site login for staff and consultants

14 Electronic Review Comments (ERC)

Read ASMX SOAP over HTTP

None ERC, Design Approval Request, Phase Review modules

15 ERTS / MyEstimates Read ASMX SOAP over HTTP

Windows

(NTLM)

Financial estimate trends

16 LAPIT (legacy, replaced by GAP)

Read ASMX SOAP over HTTP

Windows

(NTLM)

Local Agency Program section of the printed Word reports

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE) technology

Authenticati on PSEE feature

17 ETDM Environmental Screening Tool (external)

Read SOAP over HTTPS via outbound proxy

None ETDM ID validation

18 Oracle Primavera P6 web services (8 instances)

Read / Write P6 SOAP web services

Per-district service accounts

Scheduling module, Primavera Load job

19 Oracle Primavera P6 databases (8 schemas)

Read Oracle (NHibernate

Database account

Scheduling module, export jobs, readiness probe

20 Work Program Administration (WPA)

Read Oracle tables and views

Database account

Project header and all Work Program data

21 Work Program update component (CA-Gen)

Write COM interop Component credentials

External agency on item segment locations

22 Project Scheduling / Milestones (PSM)

Read Oracle Database account

PSM module

23 CITS Read Oracle Database account

Contracts, invoices, encumbranc es

24 Financial Management

(FM)

Read Oracle Database account

Encumbranc e lines, bill control

25 IEI Read Oracle Database account

Contracts and vendors

26 Trns*port / AASHTOWare SiteManager

Read Oracle Database account

Constructio n contracts, change orders, key dates

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE) technology

Authenticati on PSEE feature

27 Trns*port CES Read Oracle Database account

Estimate jobs and snapshots

28 CCTS change orders Read Oracle Database account

Resolution Tracking issues (RTM Load job)

29 Construction SIM (SiteManager) service

Read REST via FEL5 client

FEL5 API key SiteManager loader

30 RWMS Read Oracle Database account

Right of way parcels and commitmen ts

31 TVI vendor tables Read Oracle Database account

External contacts, STIP vendors

32 RCI Read Oracle Database account

Roadway sections and features

33 BMS Read Oracle Database account

Bridge inventory

34 BSS Read Oracle Database account

Invoice reviewers, system users

35 Mainframe staff data (Business Support System)

Read Oracle

(OTG4DB2DBA

schema)

Database account

Staff records

36 DOT Codes tables

(ISS)

Read Oracle Database account

Code history

37 Location reference (airports, seaports)

Read Oracle Database account

Project location impacts

38 FDOT Enterprise GIS (ArcGIS Server)

Read Esri ArcGIS

REST/JSON

None GIS and Project Impacts modules, report maps

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE) technology

Authenticati on PSEE feature

39 Esri ArcGIS Online World Street Map

Read ArcGIS REST None Base map

40 District 4 ArcGIS Server

Read ArcGIS REST None District 4 map layers

41 One Stop Permitting

(OSP) API

Read REST/JSON Bearer token UPC utility permit list

42 District Primavera reporting databases

(D2, D3, D6, TP)

Write SQL Server Database account

Nightly schedule extract

43 PSM reporting database (Azure SQL)

Write SQL Server

(TDS)

Database account

Nightly consolidate d schedule extract

44 FDOT e-mail relay Write SMTP through FEL

Relay trust Notifications , reminders, error alerts

45 Azure Application Insights

Write HTTPS Instrumenta tion key

Telemetry

46 Contract Information Monitoring (CIM)

Link HTTPS User session Resolution Tracking

47 Enterprise Information Portal vendor search

Link HTTP User session Vendor lookup

48 Video Log viewer Embedded (iframe)

HTTPS User session Video Log module (disabled)

49 Document upload staging share

Write / Read File system Service account

Temporary staging before

EDMS

upload

Appendix B. Inbound Consumers Consumer Interface

Other Department applications ProjectStatusService.asmx, ExportDataService.asmx, ImportDataService.asmx

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

Consumer Interface

PSEE batch jobs PSEEConfigService.asmx

FDOT monitoring /health/live, /health/ready

PSEE user interface (AJAX) StaffPickerService.asmx, ExternalContactPickerService.asmx, AdminDataService.asmx, upload handlers, Esri proxies

DOT-RFI-27-9037-SJ

ProjectSuite Enterprise Edition (PSEE)

1. Overview of ProjectSuite Enterprise Edition
2. Functional Scope
2.1 View modules (data sourced from other systems)
2.2 Transactional modules (data owned by PSEE)
• 3. Current System Architecture
3.1 Application architecture
3.2 Software, languages, and platforms
3.3 Database platforms
3.4 Protocols
4. Integrations
4.1 Enterprise services (Arculus / Azure API Management)
4.2 Application web services (SOAP)
4.3 Direct database access to other Department systems
4.4 GIS
4.5 Identity, e-mail, and telemetry platforms
4.6 Hyperlink integrations
5. Interfaces Exposed by PSEE
6. Scheduled Batch Jobs
7. Reports
8. Security
8.1 Authentication
8.2 Authorization
8.3 Secrets and transport
8.4 Auditing and logging
9. Hosting, Environments, and Operations
10. Technology Considerations for Respondents
Appendix A. Integration Inventory
Appendix B. Inbound Consumers

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