Office of Operations
21st Century Operations Using 21st Century Technologies

Model Systems Engineering Documents for Central Traffic Signal Systems

Appendix C: Suggested Requirements Verification Methods

Requirements Document Reference Number

System Requirements Sample Statements

Verification Method

3.1.1.1

The system shall provide monitoring and control access from the following locations.

  • Agency TMC
  • Agency LAN or WAN
  • Other agency TMC (SPECIFY)
  • Local controller cabinets (hard wire)
  • Local controller cabinets (wireless)
  • Remote location via internet

Demonstration

3.1.1.2

The system shall allow remote access using a secure Virtual Private Network (VPN).

Demonstration

3.1.1.3

The system shall allow operators from different agencies to view/edit traffic signal databases owned by other agencies, subject to assigned privilege level.

Demonstration

3.1.1.4

The system shall allow XX number of users to log on to the system simultaneously.

Demonstration

3.1.1.5

The system shall allow multiple operators to access an intersection database simultaneously.

Demonstration

3.1.1.6

The system shall allow multiple TSS Operators to view the status of an intersection or group of intersections simultaneously.

Demonstration

3.1.1.7

The system shall restrict control of each intersection database to a single user at a time.

Demonstration

3.1.1.7.1

The system shall release lock of intersection database after a user-specified period of inactivity.

Demonstration

3.1.1.7.2

The system shall allow access to a traffic signal database on a first come, first served basis.

Demonstration

3.1.1.7.3

The system shall allow administrator to terminate intersection control by other users with lesser user rights.

Demonstration

3.1.1.8

The system shall allow access to a traffic signal database based on user privileges.

Demonstration

3.1.2.1

The system shall provide the ability to control and limit user access via user privileges (allowing for different levels of user access to system features and functions).

  • Local access to the system
  • Remote access to the system
  • System monitoring
  • System manual override
  • Database
  • Administration of the system
  • Signal controller group access
  • Access to classes of equipment
  • Access to equipment by jurisdiction
  • System parameters
  • Report generation
  • Configuration
  • Security alerts

Demonstration

3.1.2.2

The system shall provide user privileges definable for the following:

Demonstration

3.1.2.2.1

Geographic area

Demonstration

3.1.2.2.2

Time of Day

Demonstration

3.1.2.2.3

Device ownership

Demonstration

3.1.2.3

The system shall provide user privileges definable on a functional level:

Demonstration

3.1.2.3.1

TSS Manager

Demonstration

3.1.2.3.2

TSS Operator

Demonstration

3.1.2.3.3

External System

Demonstration

3.1.2.3.4

TSS Maintainer

Demonstration

3.1.2.4

The system shall comply with the agency's security policy as described in (specify appropriate policy document)

Analysis

3.1.2.5

The system shall provide full access to the administrator.

Demonstration

3.1.2.6

The system shall show operators/administrator who is logged in to the system at a given time.

Demonstration

3.1.2.7

For Adaptive Systems, the ASCT shall be implemented with a security policy that addresses the following selected elements:

  • Local access to the ASCT
  • Remote access to the ASCT
  • System monitoring
  • System manual override
  • Development
  • Operations
  • User login
  • User password
  • Administration of the system
  • Signal controller group access
  • Access to classes of equipment
  • Access to equipment by jurisdiction
  • Output activation
  • System parameters
  • Report generation
  • Configuration
  • Security alerts
  • Security logging
  • Security reporting
  • Database
  • Signal controller

Analysis

3.1.2.8

The ASCT shall provide monitoring and control access at the following locations:

Demonstration

3.1.2.8.1

Agency TMC

Demonstration

3.1.2.8.2

Agency LAN or WAN

Demonstration

3.1.2.8.3

Other agency TMC (Specify)

Demonstration

3.1.2.8.4

Other agency TMC (Specify)

Demonstration

3.1.2.8.5

Local controller cabinets (wireless)

Demonstration

3.1.2.8.6

Local controller cabinets (hard wire)

Demonstration

3.1.2.8.7

Remote locations via internet

Demonstration

3.1.2.8.8

Remote locations via internet

Demonstration

3.1.2.9

The ASCT shall comply with the agency's security policy as described in (specify appropriate policy document).

Analysis

3.1.2.10

The ASCT shall not prevent access to the local signal controller database, monitoring or reporting functions by any installed signal management system.

Demonstration

3.1.3.1.1

The system shall control a minimum of XXX local signal controllers

Demonstration

3.1.3.1.2

The system shall allow intersections to be included in a group.

Demonstration

3.1.3.1.2.1

A group shall support up to XX signals.

Demonstration

3.1.3.1.3

The system shall allow an intersection to be included in two or more groups.

Demonstration

3.1.3.1.3.1

The system shall allow intersections to change grouping by time of day schedule.

Demonstration

3.1.3.1.3.2

The system shall allow intersections to change grouping by manual command.

Demonstration

3.1.3.1.3.3

The system shall allow intersections to change grouping by (enter trigger).

Demonstration

3.1.3.2.1

The ASCT shall control a minimum of XX signals concurrently. Note: communications network characteristics based on mileage distance.

Demonstration

3.1.3.2.2

The ASCT shall support groups of signals.

Demonstration

3.1.3.2.2.1

The boundaries surrounding signal controllers that operate in a coordinated fashion shall be defined by the user.

Demonstration

3.1.3.2.2.2

The ASCT shall control a minimum of XX groups of signals.

Demonstration

3.1.3.2.2.3

The size of a group shall range from 1 to XX signals.

Demonstration

3.1.3.2.2.4

Each group shall operate independently

Demonstration

3.1.3.2.2.5

The boundaries surrounding signal controllers that operate in a coordinated fashion shall be altered by the ASCT system according to configured parameters.

Demonstration

3.1.3.2.2.5.1

The boundaries surrounding signal controllers that operate in a coordinated fashion shall be altered by the system according to a time of day schedule. (For example: this may be achieved by assigning signals to different groups or by combining groups.)

Demonstration

3.1.3.2.2.5.2

The boundaries surrounding signal controllers that operate in a coordinated fashion shall be altered by the system according to traffic conditions. (For example: this may be achieved by assigning signals to different groups or by combining groups.)

Demonstration

3.1.3.2.2.5.3

The boundaries surrounding signal controllers that operate in a coordinated fashion shall be altered by the system when commanded by the user.

Demonstration

3.1.3.3.1

The Performance Measurement Server shall configure how the high-resolution data is handled from local traffic signal controllers. [This requires the agency to provide traffic signal controllers that store the high-resolution data, which are not covered by these Model Documents.]

Demonstration

3.1.3.3.1.1

High-resolution data shall include all enumerated events as described in Sturdevant, et. al., Indiana High Resolution Data Logger Enumerations, November, 2012, or later document as developed under Pooled Fund Study TPF-5(377).

Demonstration

3.1.3.3.1.2

High-resolution data interface is defined by (Specify latest interface control document, if available—Pooled Fund Study TPF-5(377), currently underway, will: Update the data logger specification to provide secure file transfer, incorporate new enumerations that have emerged, and logging new connected vehicle messages.

Test

3.1.3.3.1.3

The Performance Measurement Server shall be a separate server, independent of the TSS or ASCT.

Inspection

3.1.3.3.1.3.1

The Performance Measurement Server shall run ATSPM version 4.0 (or more recent version) available from the FHWA Open Source Application Development Portal.

Demonstration

3.1.3.3.1.3.2

The Performance Measurement Server shall be co-located with the TSS. (In such cases, it shall be owned by the TSS System Manager.) [This requirement is exclusive of 3.1.3.3.1.3.3—choose one or the other]

Inspection

3.1.3.3.1.3.3

The Performance Measurement Server shall be located at an alternative location [specify] and managed and maintained by a separate entity [specify]. [This requirement allows the server to be shared by multiple agencies but managed by one of them, or provided as a service by a private-sector provider. Please specify in this requirement. This requirement is exclusive of 3.1.3.3.1.3.2]

Inspection

3.1.3.3.1.3.4

The Performance Measurement Server shall be integrated into the TSS (ASCT).

Inspection

3.1.3.3.1.3.4.1

The Performance Measurement Server shall run ATSPM version 4.0 (or more recent version) available from the FHWA Open Source Application Development Portal. The open-source software may be revised to facilitate integration, or to extend to additional features that may be required herein.

Demonstration

3.1.3.4.1

The system shall fully satisfy all requirements when connected to XX local controllers (SPECIFY local controller type)

Demonstration

3.1.3.4.1.1

Controller type (list applicable equipment)

Inspection

3.1.3.4.1.2

Local firmware (list applicable firmware)

Inspection

3.1.3.4.1.3

Communications media and protocols (list applicable equipment)

Demonstration

3.1.3.4.1.3.1

AB3418E

Demonstration

3.1.3.4.1.3.2

NTCIP (SPECIFY relevant items)

Demonstration

3.1.3.4.2

The system shall fulfill all requirements when connected to XX local controller firmware (SPECIFY local controller firmware)

Demonstration

3.1.3.4.3

The system shall fully satisfy all requirements when connected to the existing communications network

Demonstration

3.1.3.4.4

The system shall fulfill requirements within a communications bandwidth limit of XX Mbps (specify applicable limits).

Test

3.1.3.4.5

The system shall work with the existing communications architecture (DEFINE characteristics, specifications and layout of system).

Demonstration

3.1.3.4.5.1

The system shall operate on a stand alone server located at (SPECIFY LOCATION)

Inspection

3.1.3.4.5.2

The system shall operate as cloud based.

Demonstration

3.1.3.4.5.3

The system shall operate with center to center capabilities.

Demonstration

3.1.3.4.5.4

The system shall be integrated with an Advance Traffic Management System (SPECIFY)

Demonstration

3.1.3.4.5.5

The system shall operate with on-street masters.

Demonstration

3.1.3.4.6

The system shall use the following communications protocols with traffic signal controllers (SPECIFY as appropriate)

Demonstration

3.1.3.4.6.1

Ethernet

Demonstration

3.1.3.4.6.2

Serial

Demonstration

3.1.3.4.6.3

Other [Specify]

Demonstration

3.1.3.4.7

Any field device installed as part of the TSS shall fulfill NEMA TS-2 environmental requirements.

Test

3.1.3.4.8

The system shall be fully implemented within the available budget of $[Specify]. (or included in procurement documents but not in system requirements)

Analysis

3.1.3.6

The system shall download timing parameters to two or more controllers with one command.

Demonstration

3.1.4.1

The system shall create a timing database that includes all settable signal timing parameters for a given intersection local controller based on TSS Operator input and appropriate look up tables (SPECIFY controller and firmware version).

Demonstration

3.1.4.2

The system shall allow TSS Operator to enter all settable timing parameter values manually.

Demonstration

3.1.4.3

The system shall provide default intersection timing database templates containing the following data (SPECIFY others if needed):

  • Min green, Max green, walk, flashing don't walk, yellow, red
  • Emergency Vehicle Preemption data
  • Flashing yellow left turn arrow

Demonstration

3.1.4.4

The system shall create a copy of an entire intersection timing database.

Demonstration

3.1.4.5

The system shall copy parts of one intersection timing database and paste to another intersection timing database (e.g., time of day schedule)

Demonstration

3.1.4.6

The system stall copy parts of an intersection timing database and paste within the same database (e.g., timing pattern data)

Demonstration

3.1.4.7

The system shall create up to (X) versions of an intersection timing database.

Demonstration

3.1.4.8

The system shall provide safeguards when developing new signal databases, including:

  • Range checking
  • Timing plan verification
  • Conflicting phases

Demonstration

3.1.4.9

The system shall create a timing sheet that includes:

  • All timing parameters relevant for operating a traffic signal.
  • Phase rotation diagram with north arrow
  • User selected parts of the timing database
  • Modified timings
  • User specified
  • Only non-zero timing parameters

Demonstration

3.1.4.10

The system shall transfer the following signal timing data to and from Optimization Software (SPECIFY TYPE and Version ):

  • Node number
  • Phase number and direction
  • Phase minimum green
  • Phase vehicle yellow clearance
  • Phase pedestrian walk
  • Phase vehicle all red
  • Phase pedestrian clearance
  • Cycle length
  • Offset
  • Coordination splits

Demonstration

3.1.5.1

The system shall upload/download the intersection database to a controller:

  • By manual TSS Operator command
  • By time of day schedule

Demonstration

3.1.5.2

The system shall download the entire intersection database to a controller.

Demonstration

3.1.5.3

The system shall upload the entire intersection database from a controller.

Demonstration

3.1.5.4

The system shall download select parts of an intersection database to a controller.

Demonstration

3.1.5.5

The system shall upload select parts of an intersection database from a controller.

Demonstration

3.1.5.6

The system shall download timing parameters to two or more controllers with one command.

Demonstration

3.1.5.7

The system shall upload timing parameters from two or more controllers with one command.

Demonstration

3.1.5.8

The system shall request user confirmation of command prior to downloading data from the central database to a controller.

Demonstration

3.1.5.9

The system shall request user confirmation of command prior to saving uploaded data from a controller in the central database.

Demonstration

3.1.5.10

The system shall archive all intersection databases when commanded by user.

Demonstration

3.1.5.11

The system shall cancel upload/download if any interruptions occur during the process.

Demonstration

3.1.5.12

The system shall revert to previous version of the database at the request of the user.

Demonstration

3.1.5.13

The system shall log any changes made to the database, including:

  • What was changed
  • Who made the change
  • When the change occurred

Demonstration

3.1.5.14

The system shall compare two intersection databases (central and local) and highlight the differences.

Demonstration

3.1.5.15

The system shall save the entire uploaded intersection database.

Demonstration

3.1.5.16

The system shall save selected parts of an uploaded intersection database.

Demonstration

3.1.5.17

The system shall clearly identify the official version of the timing database.

Demonstration

3.1.5.18

The system shall provide multiple methods to open an intersection database:

  • Dynamically select intersection on map
  • Search feature that uses intersection name and partial name
  • Search feature that uses intersection ID number

Demonstration

3.1.5.19

The ASCT shall log the following events: (edit as appropriate)

Demonstration

3.1.5.19.1

Time-stamped vehicle phase calls

Demonstration

3.1.5.19.2

Time-stamped pedestrian phase calls

Demonstration

3.1.5.19.3

Time-stamped emergency vehicle preemption calls

Demonstration

3.1.5.19.4

Time-stamped transit priority calls

Demonstration

3.1.5.19.5

Time-stamped railroad preemption calls

Demonstration

3.1.5.19.6

Time-stamped start and end of each phase

Demonstration

3.1.5.19.7

Time-stamped controller interval changes

Demonstration

3.1.5.19.8

Time-stamped start and end of each transition to a new timing plan.

Demonstration

3.1.5.20

The ASCT shall export its systems log in the following formats: (edit as appropriate)

  • MS Excel
  • Text
  • CVS
  • Open source SQL database

Demonstration

3.1.5.21

The ASCT shall store the event log for a minimum of XX days

Demonstration

3.1.5.22

The TSS shall store results of all signal timing parameter calculations for a minimum of XX days.

Demonstration

3.1.5.23

The ASCT shall store the following measured data in the form used as input to the adaptive algorithm for a minimum of XX days: (edit as appropriate)

  • volume
  • occupancy
  • queue length
  • phase utilization
  • arrivals in green
  • green band efficiency

Demonstration

3.1.5.24

The ASCT system shall archive all data automatically after a user-specified period not less than XX days.

Demonstration

3.1.5.25

The ASCT shall provide data storage for a system size of XX signal controllers. The data to be stored shall include the following: (edit as appropriate)

  • Controller state data
  • Reports
  • Log data
  • Security data
  • ASCT parameters
  • Detector status data

Demonstration

3.1.5.26

The ASCT shall calculate and report relative data quality including:

  • The extent data is affected by detector faults
  • Other applicable items

Demonstration

3.1.5.27

The ASCT shall report comparisons of logged data when requested by the user:

  • Day to day,
  • Hour to hour
  • Hour of day to hour of day
  • Hour of week to hour of week
  • Day of week to day week
  • Day of year to day of year

Demonstration

3.1.5.28

The ASCT shall store data logs in a standard database (specify as appropriate).

Demonstration

3.1.5.29

The ASCT shall report stored data in a form suitable to provide explanations of system behavior to public and politicians and to troubleshoot the system.

Analysis

3.1.5.30

The ASCT shall store the following data in XX minute increments: (edit as appropriate)

  • volume
  • occupancy
  • queue length

Demonstration

3.1.6.1.1

The ASCT shall take user-specified action in the absence of valid detector data from XX vehicle detectors within a group. (SELECT THE APPROPRIATE ACTION.)

Test

3.1.6.1.1.1

The ASCT shall release control to central system control.

Test

3.1.6.1.1.2

The ASCT shall release control to local operations to operate under its own time-of-day schedule.

Test

3.1.6.1.2

The ASCT shall use the following alternate data sources for operations in the absence of the real-time data from a detector:

Test

3.1.6.1.2.1

  • Data from a user-specified alternate detector.

Test

3.1.6.1.2.2

  • Stored historical data from the failed detector.

Test

3.1.6.1.2.3

The ASCT shall switch to the alternate source in real time without operator intervention.

Test

3.1.6.1.3

In the event of a detector failure, the ASCT shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance management system.

Test

3.1.6.1.4

In the event of a failure, the TSS/ASCT shall log details of the failure in a permanent log.

Test

3.1.6.1.5

The permanent failure log shall be searchable, archivable and exportable.

Demonstration

3.1.6.2.1

The TSS shall execute user-specified actions when communications to one or more signal controllers fails within a group. (SELECT THE APPROPRIATE ACTION)

Test

3.1.6.2.1.1

In the event of loss of communication to a user-specified signal controller, the TSS shall release control of all signal controllers within a user-specified group to local control.

Test

3.1.6.2.1.2

The TSS shall switch to the alternate operation in real time without operator intervention.

Test

3.1.6.2.2

In the event of communications failure, the TSS shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance management system.

Test

3.1.6.2.3

The TSS shall issue an alarm within XX minutes of detection of a failure.

Test

3.1.6.2.4

The ASCT shall execute user-specified actions when communications to one or more signal controllers fails within a group. (SELECT THE APPROPRIATE ACTION)

Test

3.1.6.2.4.1

In the event of loss of communication to a user-specified signal controller, the ASCT shall release control of all signal controllers within a user-specified group to local control.

Test

3.1.6.2.4.2

The ASCT shall switch to the alternate operation in real time without operator intervention.

Test

3.1.6.2.5

In the event of communications failure, the ASCT shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance management system.

Test

3.1.6.2.6

The ASCT shall issue an alarm within XX minutes of detection of a failure.

Test

3.1.6.2.7

In the event of a communications failure, the TSS/ASCT shall log details of the failure in a permanent log.

Test

3.1.6.2.8

The permanent failure log shall be searchable, archivable and exportable.

Demonstration

3.1.6.3.1

The ASCT shall execute user-specified actions when adaptive control fails:

Demonstration

3.1.6.3.1.1

The ASCT shall release control to central system control.

Demonstration

3.1.6.3.1.2

The ASCT shall release control to local operations to operate under its own time-of-day schedule.

Demonstration

3.1.6.3.2

In the event of adaptive processor failure, the ASCT shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance

Test

3.1.6.3.3

The permanent failure log shall be searchable, archivable and exportable.

Demonstration

3.1.6.3.4

During adaptive processor failure, the ASCT shall provide all local detector inputs to the local controller.

Test

3.1.7.1.1

The system shall update the status of all traffic signal controller connected to the system every (XX) seconds.

Demonstration

3.1.7.1.2

The system shall update the status of all traffic signal controllers connected to the system 24 hours a day, 7 days a week.

Demonstration

3.1.7.1.3

The system shall provide a map that displays different levels of information:

  • Statewide
  • Area-wide
  • Corridor
  • Intersection

Demonstration

3.1.7.1.4

The system shall provide a display that uses a cloud based system map (SPECIFY DETAILS)

Demonstration

3.1.7.1.5

The system shall provide a display that uses an existing agency map as background (Autocad, GIS, JPEG, etc.)

Demonstration

3.1.7.1.6

The system shall move between levels seamlessly, without having to open new files or windows.

Demonstration

3.1.7.1.7

The system shall have pan and zoom capabilities.

Demonstration

3.1.7.1.8

The system shall automatically adjust the display depending on the 'zoom level'.

Demonstration

3.1.7.1.9

At the state wide and area-wide level map, the system shall display a color coded status of the following systems:

  • Communication
  • Coordination
  • Intersection flash mode
  • Preemption

Demonstration

3.1.7.1.10

At the corridor level map, the system shall display the following timing related information:

  • Real time or other measurable period [Specify period length(s)] time-space-diagrams
  • Split times
  • Phase status
  • Detector status (vehicle and pedestrian)
  • Local cycle lengths/timer
  • Background cycle length/timer
  • Offset
  • Intersection identifier

Demonstration

3.1.7.1.11

The system shall provide a library of intersection drawings (e.g., standard four-legged intersections, standard tee intersection, five-legged intersection, six legged intersection, etc.) to develop intersection level graphics that are geometrically correct diagrams.

Demonstration

3.1.7.1.12

The system shall provide a library of symbols for inputs and outputs to help construct the intersection display.

Demonstration

3.1.7.1.13

The system shall allow the TSS Operator to import customized graphical icons to the map icon library.

Demonstration

3.1.7.1.14

The system shall display multiple individual intersection-level views simultaneously as separate displays or tiled windows (SPECIFY minimum and maximum numbers).

Demonstration

3.1.7.2.1

The system shall open the intersection display when the intersection on the main map is clicked on.

Demonstration

3.1.7.2.2

The system shall show the current phase status of an intersection upon operator selection of the associated intersection icon on the map display.

Demonstration

3.1.7.2.3

The system shall display the following traffic signal controller information:

  • Intersection name/number
  • Controller type
  • Firmware and version
  • IP address

Demonstration

3.1.7.2.4

The system shall have the capability to display all controller outputs in real-time, including:

  • Vehicle phases (including overlaps)
  • Pedestrian phases
  • Bicycle phases
  • Signs controlled by the signal controller

Demonstration

3.1.7.2.5

The system shall have the capability to display all controller inputs in real time, including:

  • Vehicle detector actuations
  • Pedestrian detector actuations
  • Bicycle detector actuations
  • Transit signal priority
  • Railroad preemption
  • Emergency vehicle preemption

Demonstration

3.1.7.2.6

The system shall display the data shown on the virtual controller front panel based on a user-selected intersection.

Demonstration

3.1.8.1.1

The system shall receive the current time from a source:

  • WWV radio
  • Network Time Protocol server
  • GPS time source
  • Neighboring traffic signal network

Demonstration

3.1.8.1.2

The system shall re-sync the local controller time clock through a manual command.

Demonstration

3.1.8.1.3

The system shall re-sync the local controller's time clock automatically [Specify conditions for triggering automatic re-sync].

Demonstration

3.1.8.1.4

The system shall provide a time synch to each controller using:

  • WWV radio
  • Network Time Protocol server
  • GPS time source
  • Neighboring traffic signal network

Demonstration

3.1.8.2.1

The system shall allow the traffic signals to operate in coordinated mode.

Demonstration

3.1.8.2.2

The system shall allow the traffic signals to operate according to local control in case of communications failure.

Test

3.1.8.2.3

The system shall allow the traffic signals to operate according to local control in case of TSS failure.

Test

3.1.8.2.4

The system shall download manual command to the local controller to change intersection operations to free.

Demonstration

3.1.8.2.5

The system shall download manual command to the local controller to change intersection operations to flash.

Demonstration

3.1.8.2.6

The system shall download manual command to the local controller to implement a timing plan

Demonstration

3.1.8.2.7

The system shall operate manual selection of timing plans as a higher priority over all other modes of plan selection.

Demonstration

3.1.8.2.8

The system shall request confirmation from the TSS Operator before a manual command is implemented.

Demonstration

3.1.8.2.9

The system shall provide a start and end time for manual commands.

Demonstration

3.1.8.2.10

The system shall provide a duration for manual commands.

Demonstration

3.1.8.2.11

The system shall revert to time of day operation after the manual command ends.

Demonstration

3.1.8.2.12

The system shall time-stamp a log of all manual commands.

Demonstration

3.1.8.2.13

The system shall place non-locking demand on user specified pedestrian and vehicle phases, at a user specified intersection, from the central.

Demonstration

3.1.8.2.14

The system shall place a locking demand on user specified pedestrian and vehicle phases, at a user specified intersection, from the central.

Demonstration

3.1.8.2.15

The system shall place a non-locking call replicating an emergency vehicle preemption call on a user specified preemption channel at a user specified intersection.

Demonstration

3.1.8.2.16

The system shall receive data from another system (SPECIFY DETAILS).

Demonstration

3.1.8.2.17

The system shall receive data from another system (SPECIFY DETAILS).

Demonstration

3.1.8.2.18

In the presence of external input, the system shall direct user-configured local controllers or groups to engage a user-defined emergency vehicle preemption.

Demonstration

3.1.8.2.19

In the presence of external input, the system shall direct user-configured local controllers or groups to engage a user-defined railroad preemption.

Demonstration

3.1.8.2.20

The system shall send data to another system (SPECIFY DETAILS).

Demonstration

3.1.8.2.21

The system shall turn on and turn off message signs from a manual command.

Demonstration

3.1.8.2.22

The system shall turn on and turn off message signs based on a user specified trigger (SPECIFY).

Demonstration

3.1.8.2.23

The system shall interface with external rail preemption system. (explain the external system and refer to other interfaces as appropriate)

Demonstration

3.1.8.2.24

The system shall interface with external emergency vehicle preemption system. (explain the external system and refer to other interfaces as appropriate)

Demonstration

3.1.8.2.25

The system shall interface with external light rail transit. (explain the external system and refer to other interfaces as appropriate)

Demonstration

3.1.8.2.26

The system shall interface with external bus priority system. (explain the external system and refer to other interfaces as appropriate)

Demonstration

3.1.8.3.1

The system shall operate in the following control modes:

Demonstration

3.1.8.3.1.1

Time of day schedule

Demonstration

3.1.8.3.1.2

Manual control

Demonstration

3.1.8.3.1.3

Traffic responsive

Demonstration

3.1.8.3.1.4

External command

Demonstration

3.1.8.3.1.5

Local control mode

Demonstration

3.1.8.3.1.6

Central control mode

Demonstration

3.1.8.4.1

The system shall implement the following user-specified actions according to a time of day schedule:

Demonstration

3.1.8.4.1.1

Re-synch the local controller time clock

Demonstration

3.1.8.4.1.2

.Activate a coordination pattern

Demonstration

3.1.8.4.1.3

Activate an external output

Demonstration

3.1.8.4.1.4

Deactivate an external output

Demonstration

3.1.8.5.1

The system shall operate in traffic responsive mode when commanded:

  • By manual TSS Operator command
  • By time of day schedule
  • By external input command

Demonstration

3.1.8.5.1.1

The TSS shall accept a user-defined assignment of intersection detectors as system detectors.

Demonstration

3.1.8.5.1.2

The TSS shall accept a user-defined occupancy weighting factor for each system detector.

Demonstration

3.1.8.5.1.3

The TSS shall accept a user-defined traffic-responsive control period.

Demonstration

3.1.8.5.1.4

The TSS shall sum volume plus weighted occupancy for each system detector over the duration of the control period (volume comprises distinct detection of on and off events, and weighted occupancy is the percentage of time the detector is occupied by a vehicle multiplied by the occupancy weighting factor)

Inspection/Analysis

3.1.8.5.1.5

The TSS shall accept a user-defined detector weighting factor to be applied to each system detector volume plus weighted occupancy.

Demonstration

3.1.8.5.1.6

The TSS shall multiply the volume plus weighted occupancy by the detector weighting factor.

Inspection/Analysis

3.1.8.5.1.7

The TSS shall select coordination patterns based on threshold levels (this is an alternative to the pattern recognition method).

Test

3.1.8.5.1.7.1

The TSS shall accept a user-defined selection of system detectors designated as inbound detectors.

Demonstration

3.1.8.5.1.7.2

The TSS shall accept a user-defined selection of system detectors designated as outbound detectors.

Demonstration

3.1.8.5.1.7.3

The TSS shall total the weighted volume plus weighted occupancy for inbound detectors within each intersection group over the control period.

Inspection/Analysis

3.1.8.5.1.7.4

The TSS shall total the weighted volume plus weighted occupancy for outbound detectors within each intersection group over the control period.

Inspection/Analysis

3.1.8.5.1.7.5

The TSS shall accept user-defined thresholds for inbound pattern selection.

Demonstration

3.1.8.5.1.7.6

The TSS shall accept user-defined thresholds for outbound pattern selection.

Demonstration

3.1.8.5.1.7.7

The TSS shall accept different thresholds for increasing weighted volume plus weighted occupancy totals than for decreasing weighted volume plus weighted occupancy totals (this provides the ability to incorporate hysteresis).

Demonstration

3.1.8.5.1.7.8

The TSS shall accept user-defined coordination pattern designations for each level of total weighted volume plus weighted occupancy bounded by thresholds.

Demonstration

3.1.8.5.1.7.9

The TSS shall compare the weighted volume plus weighted occupancy totals against the defined thresholds.

Inspection/Analysis

3.1.8.5.1.7.10

The TSS shall engage the inbound or outbound coordination pattern defined for the weighted volume plus weighted occupancy totals.

Test

3.1.8.5.1.8

The TSS shall select coordination patterns based on pattern recognition (this is an alternative to the threshold method).

Test

3.1.8.5.1.8.1

The TSS shall accept a table of coordination pattern designations coupled to user-defined "signature" total weighted volume plus weighted occupancy values (totals over the duration of the control period).

Demonstration

3.1.8.5.1.8.2

The TSS shall compare the total weighted volume plus weighted occupancy for each intersection group over the duration of the control period against the user-defined "signature" values.

Inspection/Analysis

3.1.8.5.1.8.3

The TSS shall engage the coordination pattern with the signature value that comes closest to the total weighted volume plus weighted occupancy for the intersection group.

Test

3.1.9.1.1.1

The ASCT shall operate non-adaptively during the presence of a defined condition.

Test

3.1.9.1.1.2

The ASCT shall operate non-adaptively when adaptive control equipment fails.

Test

3.1.9.1.1.2.1

The ASCT shall operate non-adaptively when a user-specified detector fails.

Test

3.1.9.1.1.2.2

The ASCT shall operate non-adaptively when the number of failed detectors connected to a signal controller exceeds a user-defined value.

Test

3.1.9.1.1.2.3

The ASCT shall operate non-adaptively when the number of failed detectors in a group exceeds a user-defined value.

Test

3.1.9.1.1.2.4

The ASCT shall operate non-adaptively when a user-defined communications link fails.

Test

3.1.9.1.1.3

The ASCT shall operate non-adaptively when a user manually commands the ASCT to cease adaptively controlling a group of signals.

Demonstration

3.1.9.1.1.4

The ASCT shall operate non-adaptively when a user manually commands the ASCT to cease adaptive operation.

Demonstration

3.1.9.1.1.5

The ASCT shall operate non-adaptively in accordance with a user-defined time-of-day schedule.

Demonstration

3.1.9.1.1.6

The ASCT shall operate non-adaptively when commanded by an external system process.

Demonstration

3.1.9.1.1.7

The ASCT shall alter the adaptive operation to achieve required objectives in user-specified conditions. (The required objectives are specified in Needs Statement 4.1.1)

Analysis

3.1.9.1.1.7.1

When current measured traffic conditions meet user-specified criteria, the ASCT shall alter the state of the signal controllers, maximizing the throughput of the coordinated route.

Demonstration

3.1.9.1.1.7.2

When current measured traffic conditions meet user-specified criteria, the ASCT shall alter the state of signal controllers, preventing queues from exceeding the storage capacity at user-specified locations.

Demonstration

3.1.9.1.1.7.3

When current measured traffic conditions meet user-specified criteria, the ASCT shall alter the state of signal controllers providing equitable distribution of green times.

Demonstration

3.1.9.1.1.7.4

When current measured traffic conditions meet user-defined criteria, the ASCT shall alter the state of signal controllers providing two-way progression on a coordinated route.

Demonstration

3.1.9.1.1.8

The ASCT shall provide maximum and minimum phase times.

Demonstration

3.1.9.1.1.8.1

The ASCT shall provide a user-specified maximum value for each phase at each signal controller.

Demonstration

3.1.9.1.1.8.1.1

The ASCT shall not provide a phase length longer that the maximum value.

Demonstration

3.1.9.1.1.8.2

The ASCT shall provide a user-specified minimum value for each phase at each signal controller.

Demonstration

3.1.9.1.1.8.2.1

The ASCT shall not provide a phase length shorter than the minimum value.

Demonstration

3.1.9.1.1.9

The ASCT shall detect repeated phases that do not serve all waiting vehicles. (These phase failures may be inferred, such as by detecting repeated max-out.)

Demonstration

3.1.9.1.1.9.1

The ASCT shall alter operations, to minimize repeated phase failures.

Demonstration

3.1.9.1.1.10

The ASCT shall determine the order of phases at a user-specified intersection. (The calculation will be based on the optimization function.)

Demonstration

3.1.9.1.1.11

The ASCT shall provide coordination along a route.

Demonstration

3.1.9.1.1.11.1

The ASCT shall coordinate along a user-defined route.

Demonstration

3.1.9.1.1.11.2

The ASCT shall determine the coordinated route based on traffic conditions.

Demonstration

3.1.9.1.1.11.3

The ASCT shall determine the coordinated route based on a user-defined schedule.

Demonstration

3.1.9.1.1.11.4

The ASCT shall store XX user-defined coordination routes.

Demonstration

3.1.9.1.1.11.4.1

The ASCT shall implement a stored coordinated route by operator command.

Demonstration

3.1.9.1.1.11.4.2

The ASCT shall implement a stored coordinated route based on traffic conditions.

Demonstration

3.1.9.1.1.11.4.3

The ASCT shall implement a stored coordinated route based on a user-defined schedule.

Demonstration

3.1.9.1.1.12

The ASCT shall not prevent the use of phase timings in the local controller set by agency policy.

Demonstration

3.1.9.1.2.1

The ASCT shall not prevent protected/permissive left turn phase operation.

Demonstration

3.1.9.1.2.2

The ASCT shall not prevent the protected left turn phase to lead or lag the opposing through phase based upon user-specified conditions.

Demonstration

3.1.9.1.2.3

The ASCT shall prevent skipping a user-specified phase when the user-specified phase sequence is operating.

Demonstration

3.1.9.1.2.4

The ASCT shall prevent skipping a user-specified phase based on the state of a user-specified external input.

Demonstration

3.1.9.1.2.5

The ASCT shall prevent skipping a user-specified phase according to a time of day schedule.

Demonstration

3.1.9.1.2.6

The ASCT shall omit a user-specified phase when the cycle length is below a user-specified value.

Demonstration

3.1.9.1.2.7

The ASCT shall omit a user-specified phase based on measured traffic conditions.

Demonstration

3.1.9.1.2.8

The ASCT shall omit a user-specified phase based on the state of a user-specified external input.

Demonstration

3.1.9.1.2.9

The ASCT shall omit a user-specified phase according to a time of day schedule

Demonstration

3.1.9.1.2.10

The ASCT shall assign unused time from a preceding phase that terminates early to a user-specified phase as follows:

  • next phase;
  • next coordinated phase; user-specified phase.

Demonstration

3.1.9.1.2.11

The ASCT shall assign unused time from a preceding phase that is skipped to a user-specified phase as follows:

  • previous phase;
  • next phase;
  • next coordinated phase;
  • user-specified phase.

Demonstration

3.1.9.1.2.12

The ASCT shall not alter the order of phases at a user-specified intersection.

Demonstration

3.1.9.1.3.1

The ASCT shall detect the presence of queues at pre-configured locations.

Demonstration

3.1.9.1.3.2

When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.

Demonstration

3.1.9.1.3.3

When queues are detected at user-specified locations, the ASCT shall execute user-specified adaptive operation strategy.

Demonstration

3.1.9.1.3.4

When queues are detected at user-specified locations, the ASCT shall omit a user-specified phase at a user-specified signal controller.

Demonstration

3.1.9.1.3.5

The ASCT shall meter traffic into user-specified bottlenecks by storing queues at user-specified locations.

Demonstration

3.1.9.1.3.6

The ASCT shall store queues at user-specified locations.

Demonstration

3.1.9.1.3.7

The ASCT shall maintain capacity flow through user-specified bottlenecks.

Demonstration

3.1.9.1.3.8

When queues are detected at user-specified locations, the ASCT shall limit the cycle length of the group to a user-specified value.

Demonstration

3.1.9.2.2

(Sequence-based only) The ASCT shall select cycle length based on a time of day schedule.

Demonstration

3.1.9.2.3

(Sequence-based only) The ASCT shall calculate phase lengths for all phases at each signal controller to suit the current coordination strategy.

Demonstration

3.1.9.2.4

(Sequence-based only) The ASCT shall calculate offsets to suit the current coordination strategy for the user-specified reference point for each signal controller along a coordinated route within a group.

Demonstration

3.1.9.2.4.1

(Sequence-based only) The ASCT shall apply offsets for the user-specified reference point of each signal controller along a coordinated route.

Demonstration

3.1.9.2.5

(Sequence-based only) The ASCT shall calculate a cycle length for each cycle based on its optimization objectives (as required elsewhere, e.g., progression, queue management, equitable distribution of green).

Demonstration

3.1.9.2.5.1

(Sequence-based only) The ASCT shall limit cycle lengths to user-specified values.

Demonstration

3.1.9.2.5.2

(Sequence-based only) The ASCT shall limit cycle lengths to a user-specified range.

Demonstration

3.1.9.2.5.3

(Sequence-based only) The ASCT shall calculate optimum cycle length according to the user-specified coordination strategy.

Demonstration

3.1.9.2.5.4

(Sequence-based only) The ASCT shall limit changes in cycle length to not exceed a user-specified value.

Demonstration

3.1.9.2.5.4.1

(Sequence-based only) The ASCT shall increase the limit for the following XX cycles based on a change in conditions.

Demonstration

3.1.9.2.5.4.1.1

(Sequence-based only) The change in conditions shall be defined by XX successive adaptive increases in cycle length at the maximum rate.

Demonstration

3.1.9.2.5.4.1.2

(Sequence-based only) The increased limit shall be user-defined.

Demonstration

3.1.9.2.5.5

(Sequence-based only) The ASCT shall adjust offsets to minimize the chance of stopping vehicles approaching a signal that have been served by a user-specified phase at an upstream signal.

Demonstration

3.1.9.3.2

(Non-sequence-based only) The ASCT shall calculate the appropriate state of the signal to suit the current coordination strategy at the critical signal controller. (A critical signal controller is defined by the user.)

Demonstration

3.1.9.3.3

(Non-sequence-based only) At non-critical intersections within a group, the ASCT shall calculate the time at which a user-specified phase shall be green, relative to a reference point at the critical intersection, to suit the current coordination strategy.

Demonstration

3.1.9.3.4

(Non-sequence-based only) When demand is present, the ASCT shall implement a user-specified maximum time between successive displays of each phase at each intersection.

Demonstration

3.1.9.3.5

(Non-sequence-based only) The ASCT shall adjust signal timing so that vehicles approaching a signal that have been served during a user-specified phase at an upstream signal do not stop.

Demonstration

3.1.9.4.2

The ASCT shall calculate a cycle length of a single intersection, based on current measured traffic conditions. (The calculation is based on the optimization objectives.)

Demonstration

3.1.9.4.3

The ASCT shall calculate optimum phase lengths, based on current measured traffic conditions. (The calculation is based on the optimization objectives.)

Demonstration

3.1.9.4.3.1

The ASCT shall limit the difference between the length of a given phase and the length of the same phase during its next service to a user-specified value.

Demonstration

3.1.9.4.3.2

When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.

Demonstration

3.1.9.4.4

The ASCT shall calculate phase order, based on current measured traffic conditions. (The calculation is based on the optimization objectives.)

Demonstration

3.1.9.5.2

(Phase-based only) The ASCT shall alter the state of the signal controller for all phases at the user-specified intersection.

Demonstration

3.1.9.5.3

(Phase-based only) The ASCT shall calculate the time at which a user-specified phase shall be green at an intersection.

Demonstration

3.1.9.5.4

(Phase-based only) When demand is present, the ASCT shall implement a user-specified maximum time between successive displays of each phase at each intersection.

Demonstration

3.1.9.5.5

(Phase-based only) The ASCT shall alter the operation of the non-critical intersections to minimize stopping of traffic released from user-specified phases at the user-specified critical intersection.

Demonstration

3.1.9.5.6

(Phase-based only) The ASCT shall alter the operation of the non-critical intersections to minimize stopping of traffic arriving at user-specified phases at the user-specified critical intersection.

Demonstration

3.1.9.5.7

(Phase-based only) The ASCT shall adjust the state of the signal controller so that vehicles approaching a signal that have been served during a user-specified phase at an upstream signal do not stop.

Demonstration

3.1.9.6.1

The ASCT shall limit the change in consecutive cycle lengths to be less than a user-specified value.

Demonstration

3.1.9.6.2

The ASCT shall limit the change in phase times between consecutive cycles to be less than a user-specified value. (This does not apply to early gap-out or actuated phase skipping.)

Demonstration

3.1.9.6.3

The ASCT shall limit the changes in the direction of primary coordination to a user-specified frequency.

Demonstration

3.1.9.6.4

When a large change in traffic demand is detected, the ASCT shall respond more quickly than normal operation, subject to user-specified limits. (DEFINE 'MORE QUICKLY')

Demonstration

3.1.9.6.5

The ASCT shall select cycle length from a list of user-defined cycle lengths.

Demonstration

3.1.10.1

When specified by the user, the ASCT shall serve a vehicle phase more than once for each time the coordinated phase is served.

Demonstration

3.1.10.2

The ASCT shall provide a minimum of XX phase overlaps.

Demonstration

3.1.10.3

The ASCT shall accommodate a minimum of XX phases at each signal

Demonstration

3.1.10.4

The ASCT shall accommodate a minimum of XX rings at each signal.

Demonstration

3.1.10.5

The ASCT shall accommodate a minimum of XX phases per ring

Demonstration

3.1.10.6

The ASCT shall provide a minimum of XX different user-defined phase sequences for each signal.

Demonstration

3.1.10.6.1

Each permissible phase sequence shall be user-assignable to any signal timing plan.

Demonstration

3.1.10.6.2

Each permissible phase sequence shall be executable by a time of day schedule.

Demonstration

3.1.10.6.3

Each permissible phase sequence shall be executable based on measured traffic conditions

Demonstration

3.1.10.7

The ASCT shall not prevent a phase/overlap output by time-of-day.

Demonstration

3.1.10.8

The ASCT shall not prevent a phase/overlap output based on an external input.

Demonstration

3.1.10.9

The ASCT shall not prevent the following phases to be designated as coordinated phases. (User to list all required phases.)

Demonstration

3.1.10.10

The ASCT shall have the option for a coordinated phase to be released early based on a user-definable point in the phase or cycle. (User select phase or cycle.)

Demonstration

3.1.10.11

The ASCT shall not prevent the controller from displaying flashing yellow arrow left turn or right turn. (SELECT AS APPLICABLE)

Demonstration

3.1.10.12

The ASCT shall not prevent the local signal controller from performing actuated phase control using XX extension/passage timers as assigned to user-specified vehicle detector input channels in the local controller.

Demonstration

3.1.10.12.1

The ASCT shall operate adaptively using user-specified detector channels.

Demonstration

3.1.10.13

When adaptive operation is used in conjunction with normal coordination, the ASCT shall not prevent a controller serving a cycle length different from the cycles used at adjacent intersections.

Demonstration

3.1.10.14

(Describe requirements to suit other custom controller features that must be accommodated.)

Demonstration

3.1.10.15

The ASCT shall operate adaptively with the following detector logic. (DESCRIBE THE CUSTOM LOGIC)

Demonstration

3.1.11.1

When a pedestrian phase is called, the ASCT shall execute pedestrian phases up to XX seconds before the vehicle green of the related vehicle phase.

Demonstration

3.1.11.2

When a pedestrian phase is called, the ASCT shall accommodate pedestrian crossing times during adaptive operations.

Demonstration

3.1.11.3

When a pedestrian phase is called, the ASCT shall accommodate pedestrian crossing times then resume adaptive operation.

Demonstration

3.1.11.4

The ASCT shall execute user-specified exclusive pedestrian phases during adaptive operation.

Demonstration

3.1.11.5

The ASCT shall execute pedestrian recall on user-defined phases in accordance with a time of day schedule.

Demonstration

3.1.11.6

The ASCT shall begin a non-coordinated phase later than its normal starting point within the cycle when all of the following conditions exist:

  • The user enables this feature
  • Sufficient time in the cycle remains to serve the minimum green times for the phase and the subsequent non-coordinated phases before the beginning of the coordinated phase
  • The phase is called after its normal start time
  • The associated pedestrian phase is not called

Demonstration

3.1.11.7

When specified by the user, the ASCT shall execute pedestrian recall on pedestrian phase adjacent to coordinated phases.

Demonstration

3.1.11.8

When the pedestrian phases are on recall, the ASCT shall accommodate pedestrian timing during adaptive operation.

Demonstration

3.1.11.9

The ASCT shall not inhibit negative vehicle and pedestrian phase timing.

Demonstration

3.1.11.10

The ASCT shall accommodate the following custom pedestrian features. (Specify the requirements in conjunction with their corresponding need.)

Demonstration

3.1.12.1

The ASCT shall set a specific state for each special function output based on the occupancy on a user-specified detector.

Demonstration

3.1.12.2

The ASCT shall set a specific state for each special function output based on the current cycle length.

Demonstration

3.1.12.3

The ASCT shall set a specific state for each special function output based on a time-of-day schedule.

Demonstration

3.1.13.1

The ASCT shall be compatible with the following detector technologies (agency to specify):

  • Detector type A
  • Detector type B
  • Detector type C

Analysis

3.1.13.2

The ASCT vendor shall specify detector requirements.

Inspection/Analysis

3.1.13.2.1

Vendor shall specify required detector accuracy

Inspection/Analysis

3.1.13.2.2

Vendor shall specify required detector output latency

Inspection/Analysis

3.1.13.2.3

Vendor shall specify detection zone coverage

Inspection/Analysis

3.1.13.2.4

Vendor shall specify mounting requirements

Inspection/Analysis

3.1.13.2.5

Vendor shall specify installation requirements

Inspection/Analysis

3.1.13.2.6

Detectors verified against the provided requirements shall be deemed acceptable by the ASCT Vendor.

Inspection/Analysis

3.1.13.2.7

The Vendor shall be responsible to provide expected functionality using verified detectors.

Demonstration

3.1.13.3

The ASCT shall measure the length of queues to support the adaptive algorithm

Test

3.1.13.3.1

The measurement shall be made with sufficient precision to support the adaptive algorithm.

Test

3.1.14.1

The ASCT shall maintain adaptive operation at non-preempted intersections during railroad preemption.

Demonstration

3.1.14.2

The ASCT shall maintain adaptive operation at non-preempted intersections during emergency vehicle preemption.

Demonstration

3.1.14.3

The ASCT shall maintain adaptive operation at non-preempted intersections during Light Rail Transit preemption.

Demonstration

3.1.14.4

The ASCT shall resume adaptive control of signal controllers when preemptions are released.

Demonstration

3.1.14.5

The ASCT shall execute user-specified actions at non-preempted signal controllers during preemption. (E.g., inhibit a phase, activate a sign, display a message on a DMS)

Demonstration

3.1.14.6

The ASCT shall operate normally at non-preempted signal controllers when special functions are engaged by a preemption event. (Examples of such special functions are a phase omit, a phase maximum recall or a fire route.)

Demonstration

3.1.14.7

The ASCT shall release user-specified signal controllers to local control when one signal in a group is preempted.

Demonstration

3.1.14.8

The ASCT shall not prevent the local signal controller from operating in normally detected limited-service actuated mode during preemption.

Demonstration

3.1.15.1

The ASCT shall continue adaptive operations of a group when one of its signal controllers has a transit priority call.

Demonstration

3.1.15.2

The ASCT shall advance the start of a user-specified green phase in response to a transit priority call.

Demonstration

3.1.15.2.1

The advance of start of green phase shall be user-defined.

Demonstration

3.1.15.2.2

Adaptive operations shall continue during the advance of the start of green phase.

Demonstration

3.1.15.3

The ASCT shall delay the end of a green phase, in response to a priority call.

Demonstration

3.1.15.3.1

The delay of end of green phase shall be user-defined.

Demonstration

3.1.15.3.2

Adaptive operations shall continue during the delay of the end of green phase.

Demonstration

3.1.15.4

The ASCT shall permit at least XX exclusive transit phases.

Demonstration

3.1.15.4.1

Adaptive operations shall continue when there is an exclusive transit phase call.

Demonstration

3.1.15.5

The ASCT shall control vehicle phases independently of the following:

Demonstration

3.1.15.5.1

  • LRT only phases

Demonstration

3.1.15.5.2

  • Bus only phases

Demonstration

3.1.15.6

The ASCT shall interface with external bus transit priority system in the following fashion..... (explain the external system and refer to other interfaces as appropriate)

Demonstration

3.1.15.7

The ASCT shall interface with external light rail transit priority system in the following fashion..... (explain the external system and refer to other interfaces as appropriate)

Demonstration

3.1.15.8

The ASCT shall accept a transit priority call from:

  • a signal controller/transit vehicle detector;
  • an external system.

Demonstration

3.1.16.1.1

The system shall collect and store volume data for each detector.

Demonstration

3.1.16.1.2

The system shall collect and store occupancy data for each detector.

Demonstration

3.1.16.1.3

The system shall time stamp each detector actuation.

Demonstration

3.1.16.1.4

The system shall upload local controller logs by TSS Operator manual command.

Demonstration

3.1.16.1.5

The system shall upload local controller logs according to a time of day schedule.

Demonstration

3.1.16.1.6

The TSS shall collect and store phase data for every permitted phase, including the length of the phase split [This requirement may be superfluous in systems supported by high-resolution data. This requirement is intended to support legacy approaches to providing a split monitoring capability within traffic signal systems.]

Demonstration

3.1.16.1.7

The system shall collect and store the following logs in user-definable format:

Demonstration

3.1.16.1.7.1

Timing plan change

Demonstration

3.1.16.1.7.2

Signal phase change

Demonstration

3.1.16.1.7.3

Special function change

Demonstration

3.1.16.1.7.4

Coordination status change

Demonstration

3.1.16.1.7.5

Operating mode change

Demonstration

3.1.16.1.7.6

Equipment failure

Demonstration

3.1.16.1.7.7

Communications failure

Demonstration

3.1.16.1.7.8

Manual commands

Demonstration

3.1.16.1.7.9

Operator log-on

Demonstration

3.1.16.1.7.10

Operator log-off

Demonstration

3.1.16.1.7.11

Emergency vehicle preemption on-off

Demonstration

3.1.16.1.7.12

Transit priority request, on-off

Demonstration

3.1.16.1.7.13

Action sets

Demonstration

3.1.16.1.7.14

Database changes

Demonstration

3.1.16.1.8

The system shall store the logs, alarms, and reports for a user defined amount of time (at least (X) years) where they are easily accessible. [User specify]

Demonstration

3.1.16.1.9

The system shall automatically transfer all logs, alarms, and reports to an archive system.

Demonstration

3.1.16.1.10

The archive system shall store each log, alarm and report for a minimum of (X) years (USER SPECIFY).

Inspection

3.1.16.2.1

The system shall create alerts of the following events:

  • Detector fault/failure
  • Communication fault/failure
  • Flash mode
  • Preemption fault/failure
  • Transit signal priority fault/failure
  • Cabinet flash
  • Cabinet door open
  • Temperature out of range
  • Adaptive Processor and Algorithms (Note: Only with adaptive operations)

Test

3.1.16.2.2

The system shall provide an alert of any discrepancies between the central controller database and the infield database for each controller.

Test

3.1.16.2.3

The system shall classify every alerts as critical, warning, and informational only, based user-specified rules.

Demonstration

3.1.16.2.3.1

The system shall alert TSS Operator via text message.

Demonstration

3.1.16.2.3.2

The system shall alert TSS Operator via email.

Demonstration

3.1.16.2.3.3

The system shall alert TSS Operator by message on TSS Operator's desktop.

Demonstration

3.1.16.3.1

The system shall create performance measure reports from the data in the controller logs, including the following:

  • Split logs (average split times, percent max out and force offs, percent gap outs, percent skips)
  • Detector health
  • Coordination plans
  • Pedestrian actuations
  • Transit signal priority actuations
  • Emergency vehicle preemption actuations
  • Real time split reports (showing programmed and actual splits)

Demonstration

3.1.16.3.2

The system shall create standard reports [specify].

Demonstration

3.1.16.3.3

The system shall create user customizable reports.

Demonstration

3.1.16.3.4

The system shall create the reports for a user-specified period.

Demonstration

3.1.16.3.5

The system shall collect detector data consistent with the Indiana Traffic Signal High Resolution Data Logger Enumerations.

Demonstration

3.1.16.3.6

The system shall collect signal phase data consistent with the Indiana Traffic Signal High Resolution Data Logger Enumerations.

Demonstration

3.1.16.3.7

The system shall produce performance reports consistent with:

  • Attached performance report document (USER SPECIFIED - attach)
  • Purdue Pooled Fund Study

Demonstration

3.1.16.4.1

The ASCT shall report measures of current traffic conditions on which it bases signal state alterations.

Demonstration

3.1.16.4.2

The ASCT shall report all intermediate calculated values that are affected by calibration parameters.

Demonstration

3.1.16.4.3

The ASCT shall maintain a log of all signal state alterations directed by the ASCT.

Demonstration

3.1.16.4.3.1

The ASCT log shall include all events directed by the external inputs.

Demonstration

3.1.16.4.3.2

The ASCT log shall include all external output state changes.

Demonstration

3.1.16.4.3.3

The ASCT log shall include all actual parameter values that are subject to user-specified values.

Demonstration

3.1.16.4.3.4

The ASCT shall maintain the records in this ASCT log for XX period.

Demonstration

3.1.16.4.3.5

The ASCT shall archive the ASCT log in the following manner: (Specify format, frequency, etc., to suit your needs.)

Demonstration

3.1.16.5.1

The Performance Measurement Server shall retrieve and store high-resolution data from local traffic signal controllers. [This requires the agency to provide traffic signal controllers that store the high-resolution data, which are not covered by these Model Documents.

Demonstration

3.1.16.5.1.1

High-resolution data are defined by (specify details).

Demonstration

3.1.16.5.1.2

The Performance Measurement Server shall store uploaded high-resolution data for [specify timeframe].

Demonstration

3.1.16.5.1.3

The TSS shall not prevent the local controller from accessing local devices as needed to store high-resolution data.

Demonstration

3.1.16.6.1

The Performance Measurement Server shall process the collected and stored high resolution data to produce the following reports:

  • Signal Measures Charts:
    • Approach Delay
    • Approach Speed
    • Approach Volume
    • Arrivals on Red
    • Pedestrian Delay
    • Preemption Details
    • Purdue Coordination Diagram
    • Purdue Link Pivot
    • Purdue Phase Termination
    • Purdue Split Failures
    • Split Monitor
    • Turning Movement
    • Yellow and Red Actuations
  • Reports:
    • Usage

Demonstration

3.1.16.7.1

The TSS shall provide predefined reports of stored data for non-technical recipients in accordance with user-specified formats. (Specify report formats to accompany this requirement.)

Demonstration

3.1.16.7.2

The TSS shall display stored data that illustrate adaptive input data and output decisions. (This display will be used by the TSS Operator.)

Demonstration

3.1.16.7.3

The Performance Measurement Server shall provide the following reports:

  • Signal Measures Charts:
    • Approach Delay
    • Approach Speed
    • Approach Volume
    • Arrivals on Red
    • Pedestrian Delay
    • Preemption Details
    • Purdue Coordination Diagram
    • Purdue Link Pivot
    • Purdue Phase Termination
    • Purdue Split Failures
    • Split Monitor
    • Turning Movement
    • Yellow and Red Actuations
  • Reports:
    • Usage

Demonstration

3.1.16.7.3.1

Performance measurement reports shall be consistent with descriptions in ATSPM version 4.0 (or later) documentation.

Demonstration

3.1.16.7.4

The TSS (ASCT) shall provide traffic performance measurement using probe vehicle reports provided by an external service [specify].

Demonstration

3.1.16.7.5

The TSS (ASCT) shall provide traffic performance measurement using [specify alternative approaches not covered in other requirements].

Demonstration

3.1.16.8.1

The TSS shall provide configurable alerts to the TSS Operator based on traffic operational performance. (Specify alerts to accompany this requirement.)

Demonstration

3.1.17.1

The TSS (ASCT) shall support external interfaces according to the referenced interface control documents and the following detailed requirements. (Insert appropriate requirements that suit your needs. Interface data flows should be documented in your ITS

  • Information layer protocol
  • Application layer protocol
  • Lower layer protocol
  • Data aggregation
  • Frequency of storage
  • Frequency of reporting
  • Duration of storage)

Analysis

3.1.17.1.1

The ASCT shall send operational data to XX external system. (Insert appropriate requirements that suit your needs.)

Demonstration

3.1.17.1.2

The ASCT shall send control data to the XX external system. (Insert appropriate requirements that suit your needs.)

Demonstration

3.1.17.1.3

The ASCT shall send monitoring data to the XX external system. (Insert appropriate requirements that suit your needs.)

Demonstration

3.1.17.1.4

The ASCT shall send coordination data to the XX external system. (Insert appropriate requirements that suit your needs.)

Demonstration

3.1.17.1.5

The ASCT shall send performance data to the XX external system. (Insert appropriate requirements that suit your needs.)

Demonstration

3.1.17.1.6

The ASCT shall receive commands from the XX external system.

Demonstration

3.1.17.1.7

The ASCT shall implement the following commands from the XX external system when commanded: (Edit as appropriate for your situation)

  • Specified cycle length
  • Specified direction of progression
  • Specified adaptive strategy

Demonstration

3.1.17.1.8

The ASCT shall conform its operation to an external system's operation.

Demonstration

3.1.17.1.8.1

The ASCT shall alter its operation to minimize interruption of traffic entering the system. (This may be achieved via detection, with no direct connection to the other system.)

Demonstration

3.1.17.1.8.2

The ASCT shall operate a fixed cycle length to match the cycle length of an adjacent system.

Demonstration

3.1.17.1.8.3

The ASCT shall alter its operation based on data received from another system.

Demonstration

3.1.17.1.8.4

The ASCT shall support adaptive coordination on crossing routes.

Demonstration

3.1.17.1.9

The ASCT shall set the state of external input/output states according to a time-of-day schedule.

Demonstration

3.1.17.1.10

The ASCT output states shall be settable according to a time-of-day schedule.

Demonstration

3.1.17.1.11

The ASCT shall implement the following commands from the XX external system when commanded: (Edit as appropriate for your situation)

  • Specified cycle length

Demonstration

3.1.17.1.12

The ASCT shall conform its operation to an external system's operation.

Demonstration

3.1.18.1

The vendor's software shall be fully operational within the following platform: (edit as appropriate)

  • Windows-PC,
  • Linux,
  • Mac-OS,
  • Unix.

Demonstration

3.1.18.2

The ASCT shall fully satisfy all requirements when connected with detectors from manufacturer XX (specify required detector types).

Demonstration

3.1.18.3

The ASCT shall fully satisfy all requirements when connected with XX controllers (specify controller types).

Demonstration

3.1.19.1

The vendor shall provide training on all the operations of the system.

Demonstration

3.1.19.2

The vendor shall provide a minimum of XX hours of training to a minimum of XX staff. (SPECIFY)

Demonstration

3.1.19.3

The vendor shall provide a minimum of XX training sessions (specify how many sessions over what period).

Demonstration

3.1.19.4

The vendor shall provide the following training (edit as appropriate).

Demonstration

3.1.19.4.1

The vendor shall provide training on troubleshooting the system.

Demonstration

3.1.19.4.2

The vendor shall provide training on system configuration.

Demonstration

3.1.19.4.3

The vendor shall provide training on administration of the system.

Demonstration

3.1.19.4.4

The vendor shall provide training on the operations of the adaptive system.

Demonstration

3.1.19.4.5

The vendor shall provide training on the operations of the automated traffic signal performance measurement and monitoring.

Demonstration

3.1.19.4.6

The vendor shall provide training on system calibration.

Demonstration

3.1.19.4.7

The vendor's training delivery shall include: printed course materials and references, electronic copies of presentations and references.

Inspection

3.1.19.4.8

The vendor's training shall be delivered at (SPECIFY location for training).

Demonstration

3.1.20.1

The Maintenance Vendor shall provide maintenance according to a separate maintenance contract. That contract should identify repairs necessary to preserve requirements fulfillment, responsiveness in effecting those repairs, and all requirements on the maintenance provider while performing the repairs.

Inspection

3.1.20.2

The Vendor shall provide routine updates to the software and software environment necessary to preserve the fulfillment of requirements for a period of XX years. Preservation of requirements fulfillment especially includes all IT management requirements as previously identified.

Inspection

3.1.20.3

The Vendor shall warrant the system to be free of defects in materials and workmanship for a period of XX years. Warranty is defined as correcting defects in materials and workmanship (subject to other language included in the purchase documents). Defect is defined as any circumstance in which the material does not perform according to its specification.

Inspection

Office of Operations