Exhibit B System Requirements.pdf

Portland Bureau of Transportation 1 Signals, Street Lighting, and ITS

SYSTEM REQUIREMENTS

FOR THE

Portland Tra�ic Signal Performance Measures Development and Evaluation

AND

Portland Bureau of Transportation

Federal Project No: 5900(333)

Date Approved: February 4, 2026

Prepared by: Portland Bureau of Transportation

Alison Tanaka

ODOT Project No: K22531

PBOT Project No: T01189

Version: 2.1

Date Issued: February 4, 2026

Req.

# Requirement R e q u ir e d

D s ir a b le

Con

Ops # ConOps Statement

1 DATA COLLECTION

1.1 The system shall retrieve high-resolution

data from Advanced Transportation

Controllers (ATCs) operating Q-Free

MAXTIME (or equivalent) firmware, including those documented in the

Indiana Hi Resolution Data Logger

Enumerations and any proprietary vendor enumerations.

X

5.4 The software needs to be capable of

uploading data from the ATCs, roadside tra5ic signal detection sensors, and external data sources (including transit data from the TriMet API, probe data from

RITIS, and speed and red-light-running data from the safety cameras) every 15 minutes automatically without requiring an operator to be logged into the system.

1.2 The system shall be capable of collecting

data from a minimum of 2,000 Advanced

Transportation Controllers (ATCs) operating Q-Free MAXTIME (or equivalent) firmware.

connecting to 2,000 ATCs running Q-Free

MaxTime (or equivalent) firmware and 250 roadside tra5ic signal detection sensors

(e.g., radar and LiDAR).

1.3 The system shall retrieve speed data from

Wavetronix SmartSensor Advance radar detection units.

tra5ic signal detection sensors, and external data sources (including transit data from the TriMet API, probe data from

RITIS, and speed and red-light-running data from the safety cameras) every 15 minutes automatically without requiring an operator to be logged into the system.

1.4 The system shall retrieve data from LiDAR

detection units.

1.5 The system shall be capable of collecting

data from a minimum of 250 roadside tra5ic signal detection sensors (e.g., radar and LiDAR).

connecting to 2,000 ATCs running Q-Free

MaxTime (or equivalent) firmware and 250 roadside tra5ic signal detection sensors

(e.g., radar and LiDAR).

Portland Tra5ic Signal Performance Measures Development and Evaluation System Requirements

Portland Bureau of Transportation 2 Signals, Street Lighting, and ITS

Req.

# Requirement R e q u ir s ir a

1.6 The system shall retrieve transit data from

the TriMet API.

X 5.4 The software needs to be capable of connecting to external data sources, including transit data from the TriMet API, probe data from RITIS, and speed and red-light-running data from the safety cameras.

1.7 The system shall retrieve probe data from

the Regional Integrated Transportation

Information System (RITIS).

1.8 The system shall retrieve speed and red-

light-running data from the safety cameras.

1.9 The system shall be capable of collecting

data from additional Advanced

Transportation Controllers (ATCs), roadside tra5ic signal detection sensors, and external data sources in the future.

X 5.4 The software needs to be planned such that it could connect to additional ATCs and roadside tra5ic signal detection sensors in the future.

The software needs to be planned such that it could connect to additional external data sources in the future.

1.10 The system shall initiate data collection

from a central location behind the PBOT firewall. No communication shall be initiated by field devices.

5.1 Connections to field devices and the

cloud need to be one-way (i.e., read only) and encrypted.

1.11 The system shall support connections via

Ethernet over a variety of media including fiber, copper, wireless, and cellular.

5.4 The software needs to support

connections via Ethernet over a variety of media including fiber, copper, wireless, and cellular. 1.12 The system shall work with the existing communications architecture.

1.13 The system shall retrieve data using

secure encrypted protocols.

X 5.1 Connections to field devices and the and encrypted.

1.14 The system shall retrieve data from the

Advanced Transportation Controllers

(ATCs), roadside tra5ic signal detection sensors, and external data sources

(including transit data from the TriMet API, probe data from RITIS, and speed and red-light-running data from the safety cameras) every 15 minutes automatically without requiring an operator to be logged into the system.

tra5ic signal detection sensors, and external data sources (including transit data from the TriMet API, probe data from

RITIS, and speed and red-light-running data from the safety cameras) every 15 minutes automatically without requiring an operator to be logged into the system.

1.15 If there is an interruption in

communication, the system shall retrieve all available data stored on the Advanced

Transportation Controllers (ATCs), roadside tra5ic signal detection sensors, and external data sources (including transit data from the TriMet API, probe data from RITIS, and speed and red-light-running data from the safety cameras) to backfill missing data.

backfilling data available on the ATCs, roadside tra5ic signal detection sensors, and external data sources (including transit data from the TriMet API, probe data from RITIS, and speed and red-light-running data from the safety cameras) if there is an interruption in communications.

Portland Bureau of Transportation 3 Signals, Street Lighting, and ITS

Req.

# Requirement R e q u ir s ir a

2 DATA STORAGE

2.1 The software and data shall be stored on

a server, either physical or in the cloud.

5.1 The software and data need to be stored

on a server, either physical or in the cloud.

2.2 The server shall be a separate server

independent of any other systems, including the central tra5ic signal system.

X 5.1 The server needs to be independent of any other servers, including the central tra5ic signal system server.

2.3 The system shall have enough storage for

13 months of raw data from a minimum of

2,000 Advanced Transportation

Controllers (ATCs) and 200 radar detection sensors and 13 months of aggregated data from a minimum of 50

LiDAR detection sensors and external data sources (including transit data from the TriMet API, probe data from RITIS, and speed and red-light-running data from the safety cameras).

5.1 The server needs to have enough storage

for 13 months of raw data from the ATCs and radar detection sensors and 13 months of aggregated data from LiDAR detection sensors and external data sources (including transit data from the

TriMet API, probe data from the Regional

Integrated Transportation Information

System (RITIS), and speed and red-light-running data from the safety cameras).

2.4 The system shall archive data

automatically after a user-specified period.

X 5.2 The software needs to be capable of archiving data for a configurable amount of time.

2.5 Any physical server shall be compatible

with existing PBOT equipment.

5.1 Any physical server needs to be

compatible with existing PBOT equipment.

2.6 Any cloud server shall be approved by the

Bureau of Technology Services (BTS)

Information Security (InfoSec) team.

5.1 Any cloud server needs to be approved by

the Bureau of Technology Services (BTS)

Information Security (InfoSec) team.

2.7 A cloud-based system shall include an

intermediary physical server at PBOT.

5.1 A cloud-based system will require an

intermediary physical server at PBOT.

2.8 The system shall initiate communication

with the cloud from the intermediary physical server behind the BTS firewall.

No communication shall be initiated by the cloud.

and encrypted.

2.9 The system shall use secure encrypted

protocols for communication with the cloud.

and encrypted.

2.10 The system shall store data in a SQL

database.

5.2 Data needs to be stored in a SQL

database that is independent of any other databases, including the central tra5ic signal system database.

2.11 The system database shall be

independent of any other database, including the central tra5ic signal system database.

X 5.2 Data needs to be stored in a SQL database that is independent of any other databases, including the central tra5ic signal system database.

2.12 Data from di5erent sources shall be

compiled into one database.

X 5.2 Di5erent data sources need to be compiled into one platform. Users should not need to log into multiple interfaces to access di5erent reports, charts, and maps.

2.13 The system shall be capable of packaging

data to send to external parties, such as

PORTAL.

5.2 The software needs to be capable of

packaging data to send to external parties, such as PORTAL.

Portland Bureau of Transportation 4 Signals, Street Lighting, and ITS

Req.

# Requirement R e q u ir s ir a

2.14 The system database shall be

transferable to a shared regional system in the future.

X 5.1 Data storage needs to be planned such that data can be migrated to a shared regional system in the future.

Portland Bureau of Transportation 5 Signals, Street Lighting, and ITS

Req.

# Requirement R e q u ir s ir a

3 SOFTWARE

3.1 The software shall be fully operational

within a Windows operating system.

5.1

5.2

The server needs to use a Windows operating system.

The software needs to be compatible with a Windows operating system.

3.2 The software shall utilize open-source

code so that custom methodologies can be shared.

5.2 The software needs to utilize open-source

code so that methodologies for customizations can be shared.

3.3 The vendor shall provide routine updates

to the software and software environment for a minimum of two (2) years following system acceptance.

X 5.2 The software and software environment needs to be updated regularly.

3.4 The software shall operate 24 hours a day, seven days a week.

5.2 The software needs to operate 24 hours a

day, seven days a week.

3.5 The vendor shall respond to outages, failures, and software not functioning as expected within 24 hours and apply fixes within three (3) business days.

5.2 The software needs to be repaired

promptly if there are outages, failures, or the software is not functioning as expected.

3.6 The system shall allow intersections to be

included in a group.

X 5.6 Privileges need to be assignable by intersection group (e.g., jurisdictions).

3.7 The software shall be capable of storing

multiple detection scenarios for a single intersection.

storing multiple detection scenarios for a single intersection

3.8 The system shall be capable of

configuring the following detector types at a minimum:

5.3 The new system needs to be capable of

using high-resolution data from the following detectors at a minimum:

advance count, advance speed, advance presence, stop bar count, stop bar yellow/red actuation, stop bar presence, bicycle, and pedestrian push buttons.

3.8.1 Advance Count X

3.8.2 Advance Speed X

3.8.3 Advance Presence X

3.8.4 Stop Bar Count X

3.8.5 Stop Bar Yellow/Red Actuation X

3.8.6 Stop Bar Presence X

3.8.7 Bicycle X

3.8.8 Pedestrian Push Button X

Portland Bureau of Transportation 6 Signals, Street Lighting, and ITS

Req.

# Requirement R e q u ir s ir a

4 MEASUREMENT PROCESSING

4.1 The system shall process the collected

and stored data to produce the following standard metrics available in the most recent version of ATSPM Open Source

Code (currently version 5.0):

5.3 The new system needs to include existing

ATSPM metrics currently available to

PBOT sta5 (see Table 1).

4.1.1 Purdue Phase Termination X

5.3 The new system needs to include existing

ATSPM metrics currently available to

PBOT sta5 (see Table 1).

4.1.2 Split Monitor X

4.1.3 Pedestrian Delay X

4.1.4 Preemption Details X

4.1.5 Timing and Actuation X

4.1.6 Purdue Split Failure X

4.1.7 Yellow and Red Actuations X

4.1.8 Turning Movement Counts X

4.1.9 Approach Volume X

4.1.10 Approach Delay X

4.1.11 Arrivals on Red X

4.1.12 Purdue Coordination Diagram X

4.1.13 Approach Speed X

4.1.14 Left Turn Gap Analysis X

4.1.15 Purdue Link Pivot X

4.1.16 Green Time Utilization X

4.1.17 Wait Time (for Vehicles) X

4.1.18 Time-Space Diagrams X

4.1.19 Transit Signal Priority X

4.2 Calculations for existing metrics (listed in

4.1) shall follow the methodologies in

Automated Tra�ic Signal Performance

Measure Methods and Assumptions

Manual.

5.3 Calculations for the existing metrics need

to match the methodologies in

Automated Tra�ic Signal Performance

Measure Methods and Assumptions

Manual (UDOT 2022).

Portland Bureau of Transportation 7 Signals, Street Lighting, and ITS

Req.

# Requirement R e q u ir s ir a

4.3 The system shall process the collected

and stored data to produce a minimum of

10 custom operational, safety, and maintenance metrics for transit, pedestrians, and bicyclists:

5.3 The new system needs to be customized

with PBOT-specific metrics for transit, pedestrians, and bicyclists based on the

Operational Scenarios.

4.3.1 TSP requests and service along transit

routes and bus delay at signalized intersections

4.3.2 Pedestrian actuations and intervals, when

in the cycle pedestrians arrived, and pedestrian delay

4.3.3 Bicycle actuations, if the bicyclist arrived

on green or red, if the bicyclist experienced a split failure, and bicyclist delay

4.3.4 Delay anomalies by type of user X

4.3.5 Speed distributions X

4.3.6 Red-light-running occurrences X

4.3.7 Speeding opportunities X

4.3.8 Near-miss occurrences

4.3.9 Conflicting crossings on walk

4.3.10 Pedestrian non-compliance

4.3.11 Belated pedestrians

4.3.12 Bicyclist non-compliance

4.3.13 Frequency of red flash events X

4.3.14 Communication failure X

4.3.15 Stuck preemption X

4.3.16 Skipped phase(s) X

4.3.17 Stuck all-red X

4.3.18 Failed detection (pedestrian) X

4.3.19 Failed detection (vehicle or bicycle) X

4.3.20 Failed detection (LRT or streetcar) X

4.3.21 TSP not operating X

4.3.22 Phases gapping out or maxing out/forcing

o5 more than usual

4.3.23 Transitioning more than usual X

4.4 Metrics shall be refreshed as frequently

as new data is uploaded from the

Advanced Transportation Controllers

(ATCs), roadside tra5ic signal detection sensors, and external data sources

(including transit data from the TriMet API, probe data from RITIS, and speed and red-light-running data from the safety cameras).

5.4 Reports, charts, and maps need to be

refreshed as frequently as new data is uploaded from the ATCs, roadside tra5ic signal detection sensors, and external data sources (including transit data from the TriMet API, probe data from RITIS, and speed and red-light-running data from the safety cameras).

Portland Bureau of Transportation 8 Signals, Street Lighting, and ITS

Req.

# Requirement R e q u ir s ir a

5 MEASUREMENT REPORTS

5.1 The system shall include a dashboard

that displays aggregated metrics.

5.3 The new system needs to include a

dashboard and mapping that aggregates data up from the signalized intersection level.

5.2 The system shall allow users to customize

the dashboard with user-selected metrics.

X 5.3 It is desirable for the new system to allow users to customize the dashboard with user-selected metrics.

5.3 The dashboard shall be planned such that

it can be shared publicly in the future.

X 5.5 The dashboard needs to be planned such that it could be shared publicly in the future.

5.4 The system shall include a map that

displays aggregated metrics.

5.3 The new system needs to include a

dashboard and mapping that aggregates data up from the signalized intersection level.

5.5 The system shall allow metrics to be

overlaid in reports, charts, and maps.

X 5.3 The new system needs to allow metrics to be overlaid.

5.6 Reports, charts, and maps shall be

dynamic so that a user can zoom, pan, and select layers to turn on/o5.

5.2 Reports, charts, and maps need to be

dynamic so that a user can zoom, pan, and select layers to turn on/o5.

5.7 Reports, charts, and maps shall be

customizable by timeframe (e.g., dates and times).

5.2 Reports, charts, and maps need to be

customizable by time frame (e.g., dates and times) and data interval (e.g., bin size). 5.8 Reports, charts, and maps shall be customizable by data interval (e.g., bin size).

5.9 Raw data shall be downloadable (e.g., as

a CSV file).

5.2 Raw data needs to be downloadable (e.g., as a CSV file).

Portland Bureau of Transportation 9 Signals, Street Lighting, and ITS

Req.

# Requirement R e q u ir s ir a

6 USER INTERFACE

6.1 The system shall have a web-based user

interface.

5.5 The software needs to have a web-based

user interface.

6.2 The system shall allow access at City

facilities.

5.5 The software needs to be accessible to

PBOT SSL Leadership, Engineering, and

Maintenance sta5, as well as other groups within PBOT such as Safety, Planning, Design, and Operations, at their

City desks and over VPN.

6.3 The system shall allow remote access

using a secure Virtual Private Network

(VPN).

6.4 The system shall allow operators from

di5erent agencies access, subject to assigned privilege levels, using either the

ITS Network if the server is on-prem or through a secure connection to the cloud.

X 5.5 The software needs to be accessible to

Regional Partners, either over the ITS

Network if the server is on-prem (i.e., similar to the existing connection to the central tra5ic signal system) or through a secure connection to the cloud.

6.5 The system shall allow 25 users to log on

to the system simultaneously.

5.5 A minimum of 25 users need to be able to

access the system simultaneously.

6.6 The system shall allow multiple operators

to query reports for the same intersection simultaneously.

5.5 Multiple users need to be able to query

reports for the same intersection simultaneously.

6.7 The system shall provide the ability to

control and limit user access via user privileges (i.e., allowing for di5erent levels of user access to system features and functions).

5.6 User categories need to include

administrator (full rights with the ability to configure user accounts, set privilege levels, and manage passwords), operator

(read/write access), and guest (read-only access).

6.8 The system shall provide user privileges

definable by functional level:

5.6 User categories need to include

administrator (full rights with the ability to configure user accounts, set privilege levels, and manage passwords), operator

(read/write access), and guest (read-only access).

6.8.1 Administrator with full rights including the

ability to configure user accounts, set privilege levels, and manage passwords

6.8.2 Operator with read/write access X

6.8.3 Guest with read-only access X

6.9 The system shall require a username and

password to login.

5.6 The software needs to have a login that

requires a username and password.

6.10 Passwords shall be encrypted. X

5.6 Passwords need to be encrypted.

6.11 Passwords shall be resettable by the user.

X 5.6 Passwords need to be resettable by the user.

6.12 The system shall comply with the security

policy as described in BTS-2.01 -

Information Security Administrative Rule.

5.6 The system needs to comply with BTS

InfoSec policies.