Release 6.0 Software Requirements Specification (SRS)

Release 6.0 Software Requirements Specification (SRS)
SunGuide®:
Software Requirements Specification
SunGuide-SRS-6.0
Prepared for:
Florida Department of Transportation
Traffic Engineering and Operations Office
605 Suwannee Street, M.S. 90
Tallahassee, Florida 32399-0450
(850) 410-5600
March 21, 2013
Software Requirements Specification
Document Control Panel
File Name:
File Location:
SunGuide SRS 6.0
SunGuide CM Repository
Name
Initial
Date
Created By:
Lynne Randolph, SwRI
LAR
12/01/03
Reviewed By:
Robert Heller, SwRI
Steve Dellenback, SwRI
Stephen Novosad SwRI
Steve Dellenback, SwRI
Stephen Novosad SwRI
Steve Dellenback, SwRI
Stephen Novosad SwRI
Robert Heller, SwRI
Stephen Novosad SwRI
Steve Dellenback, SwRI
Steve Dellenback, SwRI
Stephen Novosad SwRI
Steve Dellenback, SwRI
Stephen Novosad SwRI
Steve Dellenback, SwRI
Steve Dellenback, SwRI
Steve Dellenback, SwRI
Steve Dellenback, SwRI
Steve Dellenback, SwRI
Steve Dellenback, SwRI
Steve Dellenback, SwRI
Robert Heller,SwRI
RWH
SWD
SEN
SWD
SEN
SWD
SEN
RWH
SEN
SWD
SWD
SEN
SWD
SEN
SWD
SWD
SWD
SWD
SWD
SWD
SWD
RWH
12/01/03
12/15/03
12/22/03
01/27/04
01/27/04
03/10/04
03/11/04
04/02/04
04/05/04
08/27/04
10/28/04
10/28/04
4/19/05
4/25/05
9/12/05
4/12/06
11/17/06
12/04/06
04/25/07
05/29/07
12/16/07
2/20/12
Modified By:
Lynne Randolph, SwRI
Lynne Randolph, SwRI
Lynne Randolph, SwRI
Lynne Randolph, SwRI
Lynne Randolph, SwRI
Lynne Randolph, SwRI
Lynne Randolph, SwRI
Lynne Randolph, SwRI
Meredith Moczygemba, SwRI
Steve Dellenback, SwRI
Meredith Moczygemba, SwRI
Meredith Moczygemba, SwRI
Meredith Moczygemba, SwRI
Meredith Moczygemba, SwRI
Meredith Moczygemba, SwRI
Uma Goring, SwRI
Uma Goring, SwRI
Adam Clauss, SwRI
Uma Goring, SwRI
LAR
LAR
LAR
LAR
LAR
LAR
LAR
LAR
MRM
SWD
MRM
MRM
MRM
MRM
MRM
UMG
UMG
ASC
UMG
01/24/04
03/09/04
04/01/04
08/27/04
10/28/04
4/18/05
9/12/05
4/12/06
11/17/06
11/27/06
12/04/06
04/25/07
05/29/07
12/19/07
02/22/08
01/22/2010
03/05/2010
04/02/2010
06/15/2010
SunGuide-SRS-6.0
i
Software Requirements Specification
Tucker Brown, SwRI
Tucker Brown, SwRI
TJB
TJB
06/29/2010
02/16/2012
Tucker Brown, SwRI
TJB
02/15/2013
Tucker Brown, SwRI
TJB
03/21/2013
Completed By:
SunGuide-SRS-6.0
ii
Software Requirements Specification
Table of Contents
1. Scope .................................................................................................. 1 1.1 Document Identification .......................................................... 1 1.2 System Overview ..................................................................... 1 1.3 Related Documents ................................................................. 1 1.4 Contacts ................................................................................... 3 Appendix A: FEAT Requirements
Appendix B: SUB Requirements
SunGuide-SRS-6.0
iii
Software Requirements Specification
List of Acronyms
ATMS ........................Advanced Traffic Management System
AVL ...........................Automatic Vehicle Location
C2C ............................Center-to-Center
CCTV .........................Closed Circuit Television
CVS ............................Connected Vehicle Subsystem
DA ..............................Data Archiving
DD ..............................Data Distribution
DFS ............................Data Fusion System
DMS ...........................Dynamic Message Sign
DOT ...........................Department of Transportation
EG ..............................Evacuation Guidance
EH ..............................Executive Handler
EM..............................Event Management
EM/PM.......................Event Management / Performance Measures
EV ..............................Event Viewer
FDOT .........................Florida Department of Transportation
FEAT..........................Feature Requirement
HAR ...........................Highway Advisory Radio
IDS .............................Incident Detection System
IM ...............................Incident Management
IMS ............................Inventory Maintenance System
ITS..............................Intelligent Transportation Systems
ITN .............................Invitation to Negotiate
MAS ...........................Message Arbitration System
ODS............................Operational Data Store
PS ...............................Pricing System
RMF ...........................Ramp Metering Firmware
RMS ...........................Ramp Metering System
RPG ............................Response Plan Generator
RR ..............................Road Ranger
RS...............................Reporting System
RWIS..........................Road Weather Information System
SB...............................Safety Barrier
SPARR .......................Smart Phone Application for Road Rangers
SRS ............................Software Requirements Specification
SUB ............................Subsystem Requirement
SunGuide-SRS-6.0
iv
Software Requirements Specification
SwRI ..........................Southwest Research Institute
TMC ...........................Traffic Management Center
TSS.............................Transportation Sensor System
TV ..............................Toll Viewer
TVT ............................Travel Times
VSL ............................Variable Speed Limit
XML ...........................Extensible Markup Language
SunGuide-SRS-6.0
v
Software Requirements Specification
REVISION HISTORY
Revision
Date
1.0.0-Draft
December 22, 2003
1.0.1-Draft
January 27, 2004
Initial Release
Updated based on SRR input and discussion with ITS
Central Office
April 2, 2004
Incorporated FDOT comments.
August 27, 2004
Added requirements for systems in release 2 (EG, HAR,
WS, C2C and RMS)
2.0.0
May 4, 2005
Finalized with FDOT comments, new enhancements
(from ECO 1.1)
2.0.1
August 11, 2005
Finalized with ECO 1 changes
2.1.0
April 12, 2006
Updated with Release 2.1 requirements
2.2.0
November 17, 2006
Updated with Release 2.2 requirements
2.2.1
November 27, 2006
Updated architecture based on naming nomenclature
changes in the EM PM design and implementation
2.2.2
December 4, 2006
Added Ramp Metering firmware and CCTV Scheduler
requirements
3.0.0-Draft
April 25, 2007
Added Release 3.0 requirements
3.0.0
May 29, 2007
Requirements updated based on SWAM #11. Added
software release versioning information and requirements
traceability.
4.0.0-Draft
December 16, 2007
Added Release 3.1 and 4.0 requirements.
4.0.0
February 22, 2008
Updated Release 3.1 and 4.0 requirements based on
SWAM #15.
4.3
January 25, 2010
Updated Release 4.2 and 4.3 requirements based on
SWAM#20, SWAM#21, SWAM#22 and referenced
white papers
5.0
March 5, 2010
Added Release 5.0 requirements
5.1
February 16, 2012
Added Release 5.0.4, 5.0.5, and 5.1 requirements
6.0
February 15, 2013
Added Release 6.0 requirements
1.0.2
2.0.0-Draft
SunGuide-SRS-6.0
Changes
vi
Software Requirements Specification
1. Scope
1.1 Document Identification
The Software Requirements Specification (SRS) details the requirements for the Statewide
Transportation Management Center Software Library System. The requirements are separated
into two types; features (FEAT) that were specified in the Invitation to Negotiate (ITN) and new
subsystem (SUB) requirements determined during system design.
The requirements for the system are maintained in a database using Rational RequisitePro. This
document serves as a starting point for the requirements and discusses how to access, view, and
maintain the requirements database. This document is not intended to be a user manual for
RequisitePro. For information on using RequisitePro, refer to the hard copy documentation
accompanying the product, the RequisitePro online help, or the Rational web site at
http://www.rational.com.
1.2 System Overview
The Florida Department of Transportation (FDOT) is conducting a program that is developing
SunGuide software. The SunGuide software is a set of Intelligent Transportation System (ITS)
software that allows the control of roadway devices as well as information exchange across a
variety of transportation agencies. The goal of the SunGuide software is to have a common
software base that can be deployed throughout the state of Florida. The SunGuide software
development effort is based on ITS software available from the state of Texas; significant
customization of the software is being performed as well as the development of new software
modules. The following figure provides a graphical view of the software to be developed:
Figure 1-1 - High-Level Architectural Concept
1.3 Related Documents
The following documents were used to develop this document:
SunGuide-SRS-6.0
1
Software Requirements Specification

SwRI Qualification Response: Response to the Invitation to Negotiate (ITN): Statewide
Transportation Management Center Software Library System, Negotiation Number: ITNDOT-02/03-9025-RR, SwRI Proposal No. 10-35924, dated: November 18, 2002.

SwRI Technical Proposal: Technical Proposal for Invitation to Negotiate (ITN):
Statewide Transportation Management Center Software Library System, Negotiation
Number: ITN-DOT-02/03-9025-RR, SwRI Proposal No. 10-35924, dated: January 31,
2003.

SwRI Cost Proposal: Cost Proposal for Invitation to Negotiate (ITN): Statewide
Transportation Management Center Software Library System, Negotiation Number: ITNDOT-02/03-9025-RR, SwRI Proposal No. 10-35924, dated: January 31, 2003.

SwRI BAFO letter: Southwest Research Institute® Proposal No. 10-35924, “Invitation to
Negotiate (ITN): Statewide Transportation Management Center Software Library
System”, Reference: Negotiation Number: ITN-DOT-02/03-9025-RR, dated: May 5,
2003.

FDOT procurement document: Invitation To Negotiate (ITN), Negotiation Number: ITNDOT-02/03-9025-RR, Statewide Transportation Management Center Software Library
System, dated: October 21, 2002.

FDOT Scope of Services: Statewide Transportation Management Center Software
Library System: Scope of Services, September 22, 2003.

FDOT Requirements Document: Statewide Transportation Management Center Software
Library System: Requirements Specification, June 3, 2003.

Southwest Research Institute, TMC Software Study, November 15, 2001.

Southwest Research Institute, Introduction to an Operational Concept For the Florida
Statewide Library, FDOT – OCD – 1.0, March 31, 2002.

Standard Written Agreement Modification #21 for SunGuide® Software Release 4.3,
September 30, 2009

SunGuide V4.3 Software Requirements for Express Lanes Operations Version 3.13,
December 17, 2009.

Floodgate Multi-Set Interface Design Proposal, November 30, 2009

Floodgate Pre-Recorded Messages, June 23, 2009

Standard Written Agreement Modification #22 for SunGuide® Software Release 4.3,5.0
February 11, 2010

Standard Written Agreement Modification #23 for SunGuide® Software Release 5.0, May
7, 2010

Standard Written Agreement Modification #24 for SunGuide® Software Release 5.0, June
20, 2010

World Wide Web Consortium (W3) website: http://www.w3.org.

SunGuide Project website: http://sunguide.datasys.swri.edu.
SunGuide-SRS-6.0
2
Software Requirements Specification

FDOT Scope of Services: BDQ69, Standard Written Agreement for SunGuide Software
Support, Maintenance, and Development, Exhibit A: Scope of Services. July 1, 2010.

Notice to Proceed: Letter to Southwest Research Institute® (SwRI®) for BDQ69, July 1,
2010
Letter of Authorization 003: Letter to SwRI for BDQ69, August 19, 2010.
Letter of Authorization 004: Letter to SwRI for BDQ69, October 20, 2010.
Letter of Authorization 005: Letter to SwRI for BDQ69, November 9, 2010.
Letter of Authorization 007: Letter to SwRI for BDQ69, December 22, 2011.




1.4 Contacts
The following are contact persons for the SunGuide software project:


Elizabeth Birriel, ITS Section, Traffic Engineering and Operations Office Central Office,
[email protected], 850-410-5606
Arun Krishnamurthy, FDOT SunGuide Project Manager,
[email protected], 850-410-5615

Clay Packard, Atkins Project Manager,
[email protected], 850-410-5623.

David Chang, Atkins Project Advisor,
[email protected], 850-410-5622

Steve Dellenback, SwRI Management Advisor,
[email protected], 210-522-3914

Robert Heller, SwRI Project Manager,
[email protected], 210-522-3824

Tucker Brown, SwRI Software Project Manager,
[email protected], 210-522-3035
SunGuide-SRS-6.0
3
Software Requirements Specification
Appendix A:
FEAT REQUIREMENTS
SunGuide-SRS-6.0
FEAT
SunGuide ID
Name
FEAT1
General
FEAT1.1
Network security
FEAT1.1.1
S026
FEAT1.1.2
NW001
FEAT1.1.3
NW002
FEAT1.1.4
S012
FEAT1.1.5
WS001
Allow firewall usage
Requirement Text
General requirements not relating to particular subsystems or components.
Subsystem
1
1
The SunGuide system shall not prohibit the use of a firewall and the identification of what ports and hostnames are used to communicate between processes shall be provided so allowances can be made to pass through a firewall.
2
A firewall shall provide EAL‐4+ certification employing a "default deny" security policy. Both Firewall security policy
ASCII and binary logging shall be available and enabled on the firewall.
A multi‐layer DMZ model shall be used to segment traffic coming into the transaction DMZ model to segment LAN server(s) from public LAN connections (if any) by traffic being able to access the database layer.
Operating system workstation The SunGuide software shall use windows domain security
authentication for user login.
The workstation security function shall provide the capability to assign specific users and groups User and user group to categories that have specific access to levels of assignments
the software functionality.
FEAT1.1.6
WS002
Encrypted passwords FEAT1.1.7
WS003
User/group functionality
Version
The workstation security function shall use encrypted passwords to identify which users or groups can access what levels of software functionality.
Each user added to a group shall inherit the functionality of the group.
1
1
1
USER
1
USER
1
USER
1
5
FEAT1.1.8
WS004
In the event of a workstation failure, users shall be able to log into other workstations and have Workstations not user‐specific the same functionality as they would if they were at their own workstation.
FEAT1.1.9
WS005
System administrator access
FEAT1.1.10
WS006
Software module access
FEAT1.1.12
EX011
FEAT1.2
The SunGuide software shall not prevent system administrators from access to the security of the operating system and operating system functionality (access to disk drives, system configuration, etc.)
As the SunGuide GUI is browser‐based, no .EXE files shall be placed upon user workstations.
The ability to enter data into the SunGuide system Data controlled by individual or alter configuration settings shall be controlled privileges
by individual privileges.
Database and Databus
The databus shall be a modular abstraction layer Modular abstraction layer to allow subsystems to retrieve data.
The databus shall have an Interface Control Input and output separated Document (ICD) for client data exchange and an ICD for subsystem data exchange.
The SunGuide software shall not require third Non‐compliant SQL databases party subsystems to access an SQL database.
FEAT1.2.1
DB001
FEAT1.2.2
DB001A
FEAT1.2.3
DB002
FEAT1.2.4
DB002A
Data formats
FEAT1.2.5
DB003A
Database reports
1
eXtensible Markup Language (XML) shall be used to transmit data to and from the central data repository (databus).
Reports shall be generated by accessing data in the database directly.
1
1
EV
3
1
DD
1
DD
1
1
1
1
6
FEAT1.2.6
DB004
Historical data
FEAT1.2.7
S003
Databus architecture FEAT1.2.8
UT001
User and device tables
UT002
Database table update permission
FEAT1.2.10
UT003
Device communication database update
FEAT1.2.11
UT004
Device specification
FEAT1.2.9
FEAT1.2.12
UT005
Device status An option shall be provided for FDOT to store historical data for traffic management devices for a specified amount of time programmable at the system administrator level.
Each subsystem shall ensure the central data repository (databus) contains the most recent data, including equipment status.
Tables shall exist in the Oracle database for entry of GUI workstation users and parameters to set up, control and communicate with devices such as DMSs, CCTVs, cameras, loop controllers, and other devices.
The SunGuide system shall support the specification of field device parameters for the creation and control of field devices such as camera control, DMS message content, video wall control, ramp meters, and other devices.
Data collected from device communications software shall update the database tables as soon as data is received.
The SunGuide system shall support the specification of field device parameters for the creation and control of field devices such as camera control, DMS message content, video wall control, ramp meters, and other devices.
Table parameters shall provide for current status of such devices and allow for the creation of status lists based on device.
2
DD
1
1
1
1
1
1
7
FEAT1.2.13
S007
Database clustering
FEAT1.2.14
DB003
RPO shall be less than 0.1%
FEAT1.2.18
SS001B
Automated backup
FEAT1.2.19
FEAT1.2.20
S007
CR007
FEAT1.2.21
OD002D
FEAT1.2.22
DB022
FEAT1.2.23
DB023
Database parameters
The SunGuide software shall be capable of running in a clustered database configuration.
2
The SunGuide system shall have a recovery point objective of having less than one‐tenth percent (0.1%) difference between the master database and the recovery copy of the database at all times.
The system support function shall provide an automated backup component that can be programmed to perform one or more backups throughout the day at a specific clock time.
1
2
The SunGuide software shall use configurable parameters for connecting to the database.
1
The content made available by each application Same information source for for any period of time shall be derived concurrently from the same information source.
content
Any required ODBC drivers shall be from the same ODBC drivers and compliant product line as the ODBC‐compliant database database
application.
Database objects that have an ID within the software shall have an internal numeric identifier Database ID
that is not used for naming of objects by the users of the system
The software shall implement business logic (not sequences) within the Windows processes (not Business Logic
from within the Database itself)
3
3
USER
6
USER
6
8
FEAT1.2.23.1
DB023A
Business Logic Exceptions
FEAT1.2.24
DB024
Supported Databases
FEAT1.2.25
DB025
Database Model
FEAT1.2.26
DB026
FEAT1.2.27
DB027
FEAT1.2.27.1
DB027A
FEAT1.2.28
DB028
FEAT1.2.29
DB029
Exceptions will be made for sequences of primary key/IDs and for exceptionally performance intense operations upon approval by Central Office.
The software shall support the use of SQL Server 2012 Standard Edition and Oracle Database Server version 11.1.0.7.0.
The software shall have a database model from which a blank SQL Server and Oracle database can be created using ERWIN, a Commercial off the shelf database modeling tool
Static configuration data (such as subsystem Database Configuration Data permissions and system users) shall be included as a versioned data set.
The software shall be equipped with tools to import or export data from any SunGuide Database Management
database
The tool shall be configurable with the following optional parameters:
Configuable Options
1) Database schemas to include in the import or export
The software shall support the use of high availability and disaster recovery solutions for High Availability and Disaster both Oracle and SQL Server (i.e. Recovery
Failsafe/RAC/clustering, and DataGuard, respectively and the SQL Server equivalents)
Batch Inserts
Periodic data archiving shall use batch inserts to insert data into the database, where possible and appropriate.
USER
6
USER
6
USER
6
USER
6
USER
6
USER
6
USER
6
USER
6
9
FEAT1.2.30
DB030
FEAT1.2.31
DB031
FEAT1.2.32
DB032
Database Performance
When running against a system with 10,000 detector links configured, with appropriate hardware, the SQL Server database server shall archive TSS data to the database no later than two batch insert time periods following the distribution of the data from TSS.
A regression test of the software using Oracle will Regression Testing Oracle
be performed after a change to the software is made
A regression test of the software using SQL Server Regression Testing SQL Server will be performed after a change to the software is made
USER
6
USER
6
USER
6
10
A database object that can be deleted by a user shall include a flag that signifies the state of the object.
FEAT1.2.33
DB033
Ceased Use Flag
FEAT1.2.33.1
DB033A
Ceased Use Not Deleted
FEAT1.3
Test Plans
This requirement shall apply to the following tables:
COUNTY
EM_LANEMAP
RS_REPORT_MENU
RS_COST
EM_VEHICLETYPE
EM_VEHICLEMODEL
EM_REFERENCEPOINT
EM_OFFSETTYPE
EM_MAILLIST
EM_LOOKUP
EM_LOCATION
EM_LANETYPE
EM_INJURYTYPE
EM_EVENTTYPE
EM_EVENTSTATUS
EM_CONTACT
EM_CONDITION
EM_AGENCY
EM_ACTIVITY
Records no longer in use shall be flagged to indicate their usage as ceased, but they will not be deleted from the table
USER
6
USER
6
1
11
FEAT1.3.1
FEAT1.3.2
QA001
QA001P
Provide test plans and procedures
Test Plans contents
The SunGuide system shall be provided with test plans and test procedures for integration cases and the system acceptance test to ensure that each test is comprehensive and verifies all the features of the function to be tested.
The following information shall be included in the test plan:∙ An implementation plan and detailed schedule (PERT and GANTT Microsoft Word format);∙ Record‐keeping procedures and forms;∙ Procedures for monitoring, correcting, and retesting variances;∙Procedures for controlling and documenting all changes made to the SunGuide system after the start of testing;∙ Block diagram(s) of the hardware test configuration, including Contract Vendor and Department supplied equipment, external communication channels, and any test or simulation hardware;∙ A list of individual tests to be performed, the purpose of each test segment, and the appropriate functional design specification reference describing the feature being tested;∙Identification of special hardware or software tools or test equipment to be used during the test;∙ Techniques and scenarios used to simulate ultimate system sizings, especially during the peak loading tests;∙ Copies of any certified test data (i.e. environmental data) to be used in lieu of testing; and;∙Alpha and beta test plans (as appropriate);
1
1
12
FEAT1.3.3
FEAT1.3.4
QA002P
QA003P
Test procedure objective
Test procedures content
FEAT1.3.5
QA002
Test result formats
FEAT1.3.6
QA001R
Test records
Each test procedure shall list the objective of the testing and the specific SunGuide software system requirement(s) that are being verified along with pass/fail criteria for each.
Test procedures shall include the following items:∙ Function(s) to be tested;∙ Purpose of each test segment;∙ Set‐up and conditions for testing including ambient conditions;∙ Step‐by‐step procedures to be followed;∙ Pass/Fail criteria for each requirement tested including measurement tolerances;∙ All inputs and expected results outputs for each test segment; and∙ Descriptions of all simulation tools and techniques used during the test.
All SunGuide test results, notes, and observations shall be maintained in both hard copy and softcopy.
The test records shall be keyed to the steps enumerated in the test procedures and reported in the test report for each integration case.
1
1
1
1
13
FEAT1.3.7
FEAT1.3.8
QA002R
S025
FEAT1.4
Test record content
Requirement verification
The following items shall be included in the test records:∙ Test names and Paragraph numbers;∙ Dates;∙ Test locations;∙ Test specimen serial numbers or other identification;∙ Additional equipment used;∙ Test engineers name;∙ Start and stop times;∙ Log of events;∙ Observed test results, including specified computer printouts, photographs, and plots, as applicable, that will be attached to the data sheets;∙ Description of test anomalies (as applicable),∙ Recommendations for resolution of any test anomalies;∙ Provision for comments by FDOT's representative; and ∙ A copy of the master test procedure.
All hardware and software units, elements, components or subsystems shall be tested to verify they meet the specified requirements prior to statewide deployment.
Event Logging
FEAT1.4.1
EX001R
FEAT1.4.2
EX002R
FEAT1.4.3
EX007
Reporting functions shall include the ability to send event notifications via email and/or pager, Event notification
and/or telephone as well as visual and audio notifications at the user console.
All event notifications shall be stored in the Event notifications stored in central database and be tagged with the system database
time to the nearest second and date of occurrence.
The executive handler shall log error conditions as Executive Handler error logging
they are detected.
1
1
1
1
1
1
14
FEAT1.4.4
EX001L
Logging levels
FEAT1.4.5
EX002L
Separate log files
FEAT1.4.6
EX003L
Time and origin FEAT1.4.7
EX003R
Contact list
FEAT1.4.8
TM005R6
Logging messages
FEAT1.4.9
EX006L
Error log
FEAT1.4.10
EX006L1
Viewable errors list
FEAT1.4.11
EX006L2
Errors list
FEAT1.4.12
EX006L4
Review change logs
FEAT1.4.13
EX007L
Action log files
The amount of data logged for an error condition shall be able to be adjusted in real time by the user through the GUI without having to restart the application.
Separate log files shall be used for each application monitored.
Each log file message shall be time stamped and shall provide some indication as to the origin of the message (e.g. what process reported or detected the error).
Event notifications including alarms shall be sent to a configurable list of people through a primary and secondary contact medium including electronic‐mail, telephone, and pager. The contact list shall be tailored to the event or alarm.
All DMS/VSL/HAR messages shall be logged.
The error log shall describe any errors that occurred during the data import process (automated data gathered by sensors along the roadway links) with a time/date timestamp indicating when the error occurred.
All errors shall be included as part of a continuously viewable "errors list" in the form of an error log.
The error log shall provide for the "errors list" to be updated continuously.
The SunGuide software shall provide a tool to review DMS and VSL change logs (i.e., SunGuide log files).
Operator and supervisor actions shall be tracked in action log files.
1
1
1
1
3
3
3
3
3
3
15
FEAT1.4.14
EX007L1
FEAT1.4.15
EX003A
FEAT1.5
The SunGuide software shall provide a tool to review operator logs.
The administrator shall also be provided with the capability of managing system operation and Resolve issues via log analysis resolving system performance issues via the log tools
file analysis tools.
Review operator logs
TMC
FEAT1.5.1
S005
FEAT1.5.2
A024
FEAT1.5.3
A025
FEAT1.5.4
A026
Software reliability
FEAT1.5.5
S028
Monitor processes
FEAT1.5.6
A027
Unattended operation
FEAT1.5.7
A030
Traffic management
3
1
The SunGuide software shall support the collection, assessment and management of real‐
time traffic data and video for delivery of traffic management information to the motoring public and commercial vehicle operators.
The SunGuide software shall support the Management of freeway traffic management of traffic along the State freeway system.
The SunGuide software shall support the Exchange requests between exchange of traffic management requests among centers
centers running the SunGuide software.
Data exchange
3
2
1
2
The SunGuide software shall not require any regularly scheduled down time.
The SunGuide software shall provide a mechanism for monitoring the health and status of SunGuide software.
The SunGuide software shall be capable of running unattended for a minimum of eight hours.
1
The SunGuide software shall support the exchange of data using the center‐to‐center ICD.
2
1
1
16
FEAT1.5.8
A031
FEAT1.5.9
Work zone
TMC categories
FEAT1.5.9.1
A029
RTMC
FEAT1.5.9.2
A029
STMC
FEAT1.5.9.3
A029
VTMC
FEAT1.5.9.4
A029
PTMC
The SunGuide software shall support traffic management in a work zone via communication to wireless or wired devices.
The SunGuide software shall support running in multiple TMC configurations.
The SunGuide software shall support running in a regional TMC.
The SunGuide software shall support a secondary TMC sending command and control requests via center‐to‐center.
The SunGuide software shall support operating the center from a remote location.
The SunGuide software shall support deployment of the system on a laptop.
Software & Documentation Management
FEAT1.6
FEAT1.6.1
A013
FEAT1.6.2
S027
FEAT1.6.3
A014
TMC software monitoring
1
1
2
2
2
1
The SunGuide software shall log communication errors and ITS field device failures.
The SunGuide system shall adhere to open architecture standards.
A configuration management template shall be Configuration management of provided to capture information needed to devices control ITS devices.
Architecture standards
2
1
1
1
17
FEAT1.6.4
S029
FEAT1.6.5
S002
FEAT1.6.6
S024
FEAT1.6.7
S001
Baseline of software for configuration management Before any software development begins, off‐the‐
shelf software that will serve to be the foundation of the SunGuide system shall be documented to establish a baseline for configuration management of what software is developed specifically for the SunGuide project including what software is modified and to what degree it has been modified for the project.
The SunGuide system shall consist of public Public domain/sector software domain/public sector software (object and source code) wherever possible.
The SunGuide system shall be provided with a complete documentation package that shall include, but not be limited to, detailed functional and interface description, user/operator manuals, Documentation requirements software standards manuals, software test plans and procedures, and all other documentation required to complete the SunGuide project.
Software library modules
FEAT1.6.8
EX008
Recommended responses
FEAT1.6.9
A028
Future capabilities
The SunGuide system shall provide for a centrally managed set of software modules that completely support all functionality of the RTMCs.
The SunGuide system shall provide intelligent software that presents a list of recommended responses in time ordered sequence to different event conditions to the workstation operator.
The SunGuide software shall provide an ICD for the databus to allow additional subsystems to be added.
1
1
1
1
1
1
18
FEAT1.6.10
S004
FEAT1.6.11
S011
The SunGuide software shall provide ICDs for subsystem device drivers to be added.
The SunGuide software shall support the automation of system support tasks through the use of user modifiable scripts for the following Automation of system support functions:∙ System scheduler;∙ System backup;∙ tasks Data archiving;∙ Maintenance of system integrity; and∙ Data links to other FDOT computer systems.
Flexible and expandable
FEAT1.6.12
S006
Software function
FEAT1.6.13
A003
Limited access facilities
The SunGuide system shall provide each TMC with the software tools that can be used to reduce congestion and delays while responding to traffic incidents in a rapid, accurate, and effective manner.
The SunGuide software shall provide for the management and operations of limited‐access facilities during incident management, and peak demand periods and one‐way operations during evacuations including control of detour signage.
1
1
1
2
19
FEAT1.6.14
FEAT1.6.16
A004
A014
FEAT1.7
Traveler information
Software versions
The SunGuide software shall provide software for the collection and dissemination of traveler information using dynamic message signs (DMS), trail blazer signs, highway advisory radio (HAR), and advanced traveler information system (ATIS) services (511 telephone services, Internet, commercial radio, television, text messaging, etc.) for freeway operations and where available along other arterial routes independently or through an information service provider (ISP contractor) contract vendor for ATIS. The ATIS capability shall support disseminating information by the Amber Alert program.
The SunGuide software shall provide a mechanism to display the versions of the various SunGuide software applications.
System Misc.
FEAT1.7.1
S013
Video wall software
FEAT1.7.3
A017
Data reporting
FEAT1.7.4
A018
Traffic and delay prediction 2
1
1
The SunGuide system shall not preclude the operation of video wall control software from a workstation that also has the SunGuide software on it.
The SunGuide software shall provide for the reporting of data; data to be included in the reports shall be provided by FDOT.
The SunGuide software shall provide software for traffic and delay prediction to support incident management and performance monitoring (including travel times and travel speeds).
1
1
1
20
FEAT1.7.5
FEAT1.7.6
WS001A
WS002A
FEAT1.7.8
TB002
FEAT1.7.9
S030
FEAT1.7.10
S009
Action checklist
The operator workstation shall display a list of actions to be taken in response to specific events that require TMC operator response and can be checked off as they are completed.
The list of actions to be taken in response to a specific event detected by the SunGuide software shall be interactive and shall tailor itself to the specific situation. For example, if a major traffic incident is detected on a limited access facility, the operator at a workstation at the RTMC that Interactive response procedures has responsibility for that sector would be presented with a list in time ordered sequence of who to notify, the proper contact number(s) or other appropriate response. As each step is completed, the software shall highlight the next step.
The SunGuide system shall provide an interface to ITS devices that are used in the Amber Alert Interface to Amber Alert ITS program including portable dynamic message Devices
signs and the communications links to operate them.
The SunGuide system shall provide an interface to portable changeable message signs (CMSs) and Interface to portable DMS and CCTVs that support work zone management through a minimum of two drivers supporting:∙ CCTV.
Florida MIB (subset of the NTCIP standard);∙ Mark IV
The SunGuide system shall support the creation of Report creation reports by authorized users.
1
1
1
1
1
21
FEAT1.7.11
WS007
Print report utility
FEAT1.7.12
EX009
General device driver All reports shall be selected from a print menu on the operator's workstation and shall contain location parameters that indicate roadway segment links. The report will be printed with controls for page setup and for how many copies are printed.
Device drivers shall communicate to the field devices through FDOT networks and perform the following:∙ Set or check the date and time;∙ Poll the device on a periodic basis as specified in the database and retrieve device status;∙ Check the cyclic redundancy check of the device operating parameters and message library against the cyclic redundancy check parameters of the database;∙ Download operating parameters;∙ Upload the current operating parameters and display on user's workstation;∙ Display all database parameters and attributes on the user's workstation as appropriate to the device;∙ All uploaded information from the device shall be displayed at the user's workstation;∙ The operator, with proper security, shall be able to display/change database messages and parameters;∙ A log of all changes shall be maintained by time and operator identification;∙ Provide test mode set of commands;∙ Provide a method for restricted access to selected devices based upon incident management criteria;∙ Provide a log of all communication events to and from the device including the report of device errors; and∙ Provide the capability to stop and restart the device driver via operator control.
1
1
22
FEAT1.7.13
S033
FEAT1.7.14
TM023
FEAT1.7.15
S018
FEAT1.7.16
TD012D
FEAT1.7.17
DF100
FEAT1.7.18
DF101
FEAT1.7.19
FEAT1.7.20
CR005
DF102
SunGuide shall support the addition of new functionality by third party developers using an Open architecture
open architecture approach that conforms to the current SunGuide‐Software Architecture Guidelines document.
SunGuide shall utilize both an automated Interfaces for data input
interface and an Intranet‐oriented operator interface to facilitate data input.
The SunGuide Software System shall interface with ITS devices through the device drivers that Interface with ITS devices
are being developed as part of the SunGuide software.
SunGuide shall not degrade the accuracy of the data it receives and processes, except for desired Degradation of data accuracy
data synthesis functions that condense and summarize raw data imports.
Data sources shall include, but are not limited to: Data source inclusions
incident/event data, traffic sensor data, and weather data.
The SunGuide shall not degrade the accuracy of the data it receives and processes, except for Degradation of synthesis desired data synthesis functions that condense functions
and summarize raw data imports.
Single source for time
A SunGuide software installation shall utilize a single source for time and utilize that single source to provide consistent time base throughout the SunGuide software.
SunGuide shall synchronize all servers/workstations to a Master Clock signal Master clock synchronization
obtained from a universal time standard obtained through the internet.
3
3
2
3
3
3
3
3
23
FEAT1.7.21
FEAT1.7.22
FEAT1.7.23
CR006
CR008
CR009
Incorporated functions
User intervention
Continuance of operations
FEAT1.7.24
CR010
Publishing data
FEAT1.7.25
CR012
Availability
FEAT1.7.26
S036
Data available within one minute
FEAT1.7.27
S037
Software capable of 24‐7 operations
SunGuide shall incorporate the following functions: ‐an Automated (Data) Interface, ‐an Operator Interface that is a web‐based browser, and ‐software to interact with external applications.
When both the primary and redundant systems are operational, the redundant server shall not require any user intervention.
The SunGuide system shall continue to operate in the event that data sources (sensors, external data providers, etc.) fail and report that data as missing or unavailable.
The SunGuide system shall not publish to internal or external systems data from failed internal or external data sources.
The SunGuide Software shall have an availability of at least 99% of the time measured over a 24 hour period that source data systems are operating, measured annually. Operational is defined as that the system is running and not that no errors are occurring.
New data shall be available in SunGuide within one minute of being entered by an operator or received by an automated feed.
SunGuide shall be capable of operating data 24‐
hours per day, seven days per week, for any contiguous 365‐day period, excluding periods when modular or source data systems are down.
3
3
3
3
3
3
3
24
FEAT1.7.28
DB006
SunGuide event information shall be available at least 99% of the time, in whole or part, measured Event info available 99% of the annually, except for service anomalies that are time
beyond SunGuide control.
FEAT1.7.29
UT007
SG scaleable to incorporate other data sources
FEAT1.7.30
OD007R1
Traditional screen resolutions
FEAT1.8
A011
Coordination of agencies
FEAT1.9
FEAT1.9.1
SunGuide shall be scaleable such that it is capable of accepting data from additional data sources, including both data provided by the FDOT, as well as data from other agencies' facilities.
CR013
FEAT1.9.1.2
UT009
The SunGuide administrative editor shall allow the creation of at least 50 users, each user may have a Creation of users, permissions unique set of permissions to access different components of the SunGuide subsystems.
511 Reporting segments
3
Traditional screen resolutions are defined as a minimum: XGA, 1024x768 pixels, SXGA.
The SunGuide software shall provide software for coordination with all law enforcement, fire/rescue, and emergency management personnel, coordination with local traffic operation centers, and coordination with county emergency management centers and the State Emergency Operations Center (SEOC) when appropriate. The data will be either available through the Center‐to‐center interface or through the use of a remote interface terminal.
Administrative tools
Administrative Editor
FEAT1.9.1.1
3
SunGuide shall provide the ability to add, delete, and modify 511 Reporting Segments
3
2
GUI
GUI
1
1
GUI
3
GUI
3
25
FEAT1.9.1.3
UT010
FEAT1.9.1.4
UT003D
FEAT1.9.1.5
UT003D1
FEAT1.9.1.6
UT003D2
FEAT1.9.1.7
UT004D
FEAT1.9.1.8
UT004D1
FEAT1.9.1.9
UT004D3
FEAT1.9.1.10
UT005D
FEAT1.9.1.11
UT011
Configuration file abilities
Configuration files shall provide the ability to add, delete, or modify any road in the state of Florida.
SunGuide configuration files shall provide the ability to add, delete, and modify FIHS and Central Florida roadway links.
Performing reconfiguration of roadway link Reconfiguration of data
location data shall alter the roadway links displayed by Florida SunGuide.
Upon adding or modifying FIHS and Central Florida roadway links, the SunGuide shall initiate the Storing data after changes
storing of data, when available, on the new or modified road segments the next time a user logs in.
The roadway links specified by the FDOT shall be Default list of roadway links
the default list of road links.
Adding, deleting, or modifying Data Collection Programming modifications not roadway links shall not require any programming required
or database structure modifications.
Roadway links
Link location administrative restrictions
Editing or creating link locations shall be a SunGuide administrative function restricted to an operator with appropriate permissions
Roadway links shall be able to be dynamically subdivided.
The SunGuide shall allow for the periodic addition, reconfiguration, or redefinition of roadway links including the addition and/or deletion of roads, No loss of current or past data
transit, port facilities, and airport facilities without the loss of current or past data.
Links shall be subdivided
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
26
FEAT1.9.1.12
UT006
FEAT1.9.1.13
UT013
FEAT1.9.1.14
UT014
FEAT1.9.1.16
ML001A
FEAT1.9.1.17
The SunGuide Administrative Editor shall allow Devices added for any SunGuide new devices to be added to the system for any device type
device type that has an existing SunGuide subsystem.
The Admin Editor shall be able to set and display probe reader configuration parameters such as Probe reader configuration
the reader station IP address, status, and the data polling rate.
LPR health monitoring shall be configurable via a Configurable LPR health systems administration page within the Admin monitoring
GUI.
The Admin Editor shall support the creation, Rate schedule table support viewing and editing of the Rate Schedule Table.
Configuration abilities
FEAT1.9.1.17.1
TM005R10
Configure abbreviations
FEAT1.9.1.17.2
TM005R11
Configure device templates
FEAT1.9.2
FEAT1.9.2.1
The Administrative Editor shall provide the ability to add, edit and delete abbreviations
The Administrative Editor shall provide the ability to add, edit and delete device templates
Configuration Editor
S035
Configuration updates
FEAT1.9.2.2
UT001D
Configuration file changes
FEAT1.9.2.3
UT002D
Reconfiguration privileges
For each SunGuide Subsystem that may require configuration updates after initial installation of the subsystem in the database or an XML file, an Administrative Editor shall be available to facilitate configuration changes.
Additions, deletions, or modifications to the configuration file shall not require any database programming or database table structure modifications.
Editing or adding configuration files shall be restricted to a SunGuide administrator with reconfiguration privileges.
GUI
3
GUI
4
GUI
4
GUI
3.1
GUI
5
GUI
5
GUI
5
GUI
1
GUI
3
GUI
3
GUI
3
27
FEAT1.9.3
UT008
FEAT2
Administrator‐level user capabilities
Web Server (WS)
FEAT2.1
S020
Web server function
FEAT2.2
PA001
Video server
FEAT2.3
PA002
Access to camera system control functions PA004
Map elements: congestion, incidents, cameras, DMSs
FEAT2.4
Administrator‐level users shall have all the capabilities of operator‐level users, plus an ability to add, delete, and edit other users' accounts.
FEAT2.5
The SunGuide system shall provide a web server for private and public dissemination of TMC information.
The web server shall capture and publish video from analog and digital video devices within the system for private and public dissemination via LAN, WAN, and the World Wide Web. The video server shall refresh and update the image at a rate set via parameters by the workstation operator.
The web server shall provide secure access to system control functions of selected cameras as determined by the system administrator for users with high‐speed Internet access.
The web server shall provide a map showing traffic information and the location of certain FDOT ITS devices.
General
FEAT2.5.1
PA014
Client site processing times
FEAT2.5.2
PA006U
Home page display time
The web site shall not employ software that requires client site processing resulting in excessive wait times for the entire web site to appear.
The Web site home page shall be completely displayed within 15 seconds when using an ADSL connection and no other processes are running.
GUI
3
WS
1
WS
2
WS
1
WS
3
WS
2
WS
1
WS
3
WS
3
28
FEAT2.5.3
PA006U1
Hyperlinks use relative paths
FEAT2.5.4
PA005U2
Support adding URLs
FEAT2.5.5
PA016U5
Measurable traffic delays
FEAT2.5.6
FEAT2.5.7
PA016U6
PA016U8
The SunGuide website shall display the following data that is available from the SunGuide C2C interface: weather information, road closures, Display data from C2C interface
major events, or construction causing significant delays to travelers.
Legends on map
FEAT2.5.8
PA005
Dissemination of FIHS data
FEAT2.5.9
PA006
Comply with ADA
FEAT2.5.10
PA008
Help page link
FEAT2.5.11
PA014U
Hyperlinks on the website which direct users to other locations within the website shall use relative paths.
SunGuide shall support the SunGuide administrator adding URLs (and associated text) to the home page of the web site.
The iFlorida Web site shall include measurable traffic delays in the Central Florida region.
Webmaster e‐mail link
The web site shall contain a legend of all color‐
coding and traffic‐related icon descriptions on the same page as the map or at such other location specified by the FDOT.
The SunGuide FIHS data shall be disseminated via a FIHS Internet‐based traveler information Web site.
There shall be a text‐only version of the Web site such that it complies with Section 508 of the American Disabilities Act (ADA).
The iFlorida Web site shall provide a link to a Help Page offering information in text and/or graphic format on the basic use of the Internet Web site, and listing types of content available on the site.
The Web site shall have an e‐mail link that will enable users to send a message to the Webmaster (Customer Service).
WS
3
WS
3
WS
3
WS
3
WS
3
WS
3
WS
3
WS
3
WS
3
29
FEAT2.5.12
FEAT2.5.13
PA012U
PA012
From the Home Page, the user shall be able to access information for a requested event with no Access information within two more than two "clicks" of the mouse, unless one of these "clicks" takes them "out" to one of the mouse clicks
regional Web sites.
Delivery of understandable messages
FEAT2.5.14
PA005U1
Internal web site capable of displaying maps
FEAT2.5.15
PA020U
Links to state traveler information systems
FEAT2.6
FEAT2.6.1
FEAT2.6.2
Messages delivered through the Internet Web site shall be formatted in brief, non‐technical language that is readily understandable by a user with a minimum education level of 9th grade.
The Web site shall be an Internet Web site that is capable of displaying a map of the state and also has the capability to link to the metropolitan areas in Florida where regional Web sites are available.
iFlorida Website shall include links to all other metropolitan area traveler information systems in the state. Links to be provided by the FDOT.
Roadway data
PA003U1
PA003U2
Travel conditions link
No data indications
The Web site shall provide details on roadway link travel conditions, either through opening a pop‐
up window or by opening a new web page with the additional information, whenever a user clicks on a given event icon (generally including information on incidents, special events, construction, etc.).
The website shall report that no data is available on a specified roadway segment if the SunGuide operator or the automated traffic sensors are reporting no data.
WS
3
WS
3
WS
3
WS
3
WS
1
WS
3
WS
3
30
FEAT2.6.3
PA003U3
Roadway event naming
FEAT2.6.6
PA016U4
Web site inclusions
FEAT2.6.7
PA016U7
Included considitions
FEAT2.6.8
PA016U9
Display C2C travel time data
FEAT2.7
PA013U
Changing program code
FEAT2.7.2
PA016U
Adhere to color‐coding/icons
FEAT2.7.4
The web site shall display travel time data received from the Center‐to‐Center interface.
Icons
FEAT2.7.1
FEAT2.7.3
Roadway event naming shall use the roadway names configured in the SunGuide Administrative editor.
The Web site shall include planned construction/closing lanes, near‐term inclement weather conditions (e.g., within 60 minutes), slowing traffic, or any abnormal road conditions and/or alerts that do not qualify as an urgent event.
The website shall include current severe weather conditions (to include but not limited to tornadoes, severe thunderstorms, hurricanes) road closures, major incidents or construction.
PA016U2
PA016U3
Icon storage/modification
Urgent event icons
The website program code (HTML, ACTIVEX code) shall not be changed to modify icons with the exception of adding new icons associated with new functionality.
The Web site shall adhere to color‐coding schemes and/or icons specified by the FDOT.
The web site shall use icons stored as individual files on the web site so that colors and shape can be modified using an icon editor.
The iFlorida Web site shall include urgent event icon shapes and conspicuous color/shading to be specified by the FDOT.
WS
3
WS
3
WS
3
WS
3
WS
1
EV
3
WS
3
WS
3
WS
3
31
FEAT2.7.5
PA007U1
FEAT2.8
Pop‐up window capabilities
Maps
FEAT2.8.1
PA005U
Add URLs to links page
FEAT2.8.2
PA007U
Select FIHS event
FEAT2.8.3
PA009U
Clickable regions
FEAT2.8.4
PA009U1
Regions linked to traffic conditions
FEAT2.8.5
PA009U2
Metro area map
FEAT2.8.6
PA009U3
Access to event categories
FEAT2.8.7
PA013
Automatically update
FEAT2.9
Clicking on the icon on the Web site shall open a pop‐up window capable of displaying a variety of items, including text providing relevant information.
511 service
The SunGuide administrator shall be able to add URLs (and associated text) to the links page of the web site
The Web site shall have statewide maps that allow users to select a given FIHS event, by clicking on the event icon in order to view its current event report.
The map on the web server shall have a minimum of 6 clickable regions configurable by the system administrator.
The website shall present a map of Florida with clickable regions linked to traffic conditions in those regions.
For the Central Florida region, the web map shall present a metro area map so that users have the ability to select their desired region from a drop‐
down menu.
The Central Florida region map shall provide tabs that give access to different event categories, for example: critical incidents, traffic, weather, and roadwork.
The web site map, including the color‐coded segments, shall automatically update after configurable amounts of time with the default being 5 minutes.
WS
3
WS
1
WS
3
WS
3
WS
3
WS
3
WS
3
WS
3
WS
3
WS
1
32
FEAT2.9.1
PA009
Promote 511 service
FEAT2.9.2
PA011U
Information for 511 usage
FEAT2.10
The Web site shall promote use of the 511‐
telephone service by displaying the 511 logo on every page with the option to display additional text explaining or promoting the 511 telephone service.
The iFlorida Web site shall have a page that shall include information pertaining to the use of the 511‐telephone service, including, at a minimum, a listing of all commands (both voice and touch‐
tone) available to users for retrieving information from these services.
Banner
FEAT2.10.1
PA007
FEAT2.10.2
PA008U
FEAT3
The web site Home Page shall display a banner message above the state map, that provides emergency information and/or serious/major Display emergency information
conditions affecting the entire state or a large portion of Florida (e.g., hurricane, etc.).
Operator can modify banner
The SunGuide operator shall be capable of making, adding to, deleting, or otherwise modifying the statewide Web site banner.
Executive Handler (EH)
FEAT3.1
S008
Executive handler function FEAT3.2
EX001
Minimum functionality
The SunGuide system shall have an executive function that handles all monitoring and reporting of the status of external devices and internal processes.
As a minimum the executive handler shall provide:∙ Process initiation/termination;∙ Process status and monitoring;∙ Error logging.
WS
3
WS
3
WS
1
WS
3
WS
3
EH
1
EH
1
EH
1
33
FEAT3.3
EX002
Start, stop, and restart processes
FEAT3.4
EX003
Scheduled process control
FEAT3.5
EX004
Group dependencies
FEAT3.6
EX001F
Process start order FEAT3.7
EX002F
Restart safeguards
FEAT3.8
EX005
FEAT3.9
EX006
FEAT3.10
EX001D
The executive handler shall be capable of automatic and manual initiation, termination and re‐initiation of system processes.
The executive handler shall have the capability to add scheduled process control for subsystems and drivers
The executive handler shall notify personnel if an application fails or is restarted if the personnel have registered for notifications.
In the case of a failure, the executive handler shall start processes in the same order that they originally started.
In the case of a process failure due to unavailable resources, the executive handler shall have safeguards to prevent the unrestrained cyclical restart of failed applications.
The executive handler shall have the ability to Initialize individual components initialize individual components as well as subsystem groups.
The executive handler shall be capable of monitoring, reporting, and displaying the status of Monitor, report and display all subsystems, subsystem components, and status
network communications links and components.
Hierarchal view
The executive handler shall provide a hierarchical view of the system allowing the user to drill down from a subsystem level to an individual component level.
EH
1
EH
1
EH
1
EH
1
EH
1
EH
1
EH
1
EH
1
34
FEAT3.11
EX001M
Monitor key data
FEAT3.12
EX002M
Database storage of information
FEAT3.13
EX004L
FEAT3.14
EX005L
FEAT3.15
EX003F
FEAT3.16
FEAT3.17
EX010
EX001G
All information collected shall be capable of being stored in the database.
Status log viewer shall support queries across Status log query multiple files
multiple log files.
The system shall delete log files when they age Status log delete aged log files
beyond a configurable number of days.
It shall be possible to configure the maximum number of retries that the executive handler shall perform when attempting to restart a failed Configurable number of restarts application. It shall also be possible to configure the number of minutes over which the retry counter is maintained.
Use windows credentials
Internal status data
The executive handler application shall utilize windows credentials to verify rights to execute.
The SunGuide shall gather internal status data concerning its operation and make this information available to the user.
Inventory Management System (IMS)
System
FEAT4
FEAT4.1
FEAT4.1.1
Monitoring shall include pertinent system information such as the current system state, as well as historical information such as system performance, uptime, and error logs.
S022
The SunGuide system shall be provided with an interface to a software system that tracks the Interface to maintenance and inventory of all ITS equipment and the status of inventory tracking software equipment repair(s) and maintenance (i.e. life‐
cycle asset management software system).
EH
1
EH
2
EH
1
EH
1
EH
1
EH
1
EH
3
IMS
2
IMS
2
IMS
2
35
FEAT4.1.2
IM002
FEAT4.1.3
IM001D
FEAT4.1.4
IM001R
Index by equipment type Vendor name referenced by The vendor name shall be referenced by the equipment type ID. equipment type identification.
Reports shall be provided by type identification Reports provided by type ID for all equipment according to equipment status.
FEAT4.1.5
IM002D
View and print vendor table
FEAT4.1.6
IM003D
Location data
FEAT4.1.7
IM005D
Equipment status categories
FEAT4.1.8
IM004
Record status of equipment FEAT4.1.9
IM006D
The inventory/maintenance software database shall index by equipment type for the purpose of reporting and updating the inventory.
Equipment status tracking
The workstation operator shall be capable of viewing and printing the complete vendor table or the vendors according to a specific type identification.
The inventory/maintenance software shall maintain warehouse locations, repair shop locations, and installation locations, with a GUI screen to add/edit/delete such locations.
The equipment status shall be:∙ In inventory;∙ Installed; or∙ In repair/test.
The inventory/maintenance software shall provide the operator the capability to record the status of equipment that has failed and is in the process of being repaired.
The inventory/maintenance software shall support tracking the status of the equipment being tracked as follows:∙ Failed at site;∙ At repair depot;∙ In repair at depot;∙ In testing at depot; and∙ In inventory.
IMS
2
IMS
2
IMS
2
IMS
2
IMS
2
IMS
2
IMS
2
IMS
2
36
FEAT4.1.10
FEAT4.1.11
IM005
IM006
FEAT4.2
FEAT4.2.1
FEAT4.2.2
Save repair information
Repair history
The inventory/maintenance software shall contain repair information on the equipment to include the dates of failure and repair, the repair technician, the time to repair, parts utilized by part number and comments.
The inventory/maintenance software shall maintain a history of the equipment repairs and may be reported via GUI to the operator or may be printed.
GUI
IM001
IM003
The inventory/maintenance software shall provide a GUI display screen for the operator to add/edit/delete inventory equipment information. The equipment information shall at a minimum include:∙ Type identification and description;∙ Model identification and Add/edit/delete equipment GUI description;∙ Manufacturer information; ∙ Serial number;∙ Firmware version;∙ Location description;∙ Date installed;∙ Status (inventory/installed/repair);∙ Location geographic reference; and ∙ Quantity by type identification on hand.
Add/edit/delete vendor information GUI
The inventory/maintenance software shall provide a GUI for the operator to add/edit/delete vendor information. The vendor information shall at a minimum include the following:∙ Vendor name;∙ Vendor contact;∙ Address/ information including city, state, and zip code;∙ Telephone and facsimile numbers; and∙ Web address for purchase.
IMS
2
IMS
2
GUI
1
GUI
2
GUI
2
37
FEAT4.2.3
IM002R
Print reports GUI
FEAT4.2.4
IM004D
Equipment history GUI
FEAT4.2.5
ID001W
Displays
FEAT4.2.6
IM007
Repair status display
FEAT5
FEAT5.1
FEAT5.1.1
All printed reports of the inventory software shall be selected via a GUI menu.
History of the equipment transfer and its inventory status shall be maintained and reported via GUI to the workstation operator or printed.
The congestion report display shall result from a comparison between all possible sources of data derived from real‐time data, operator input or historical data as determined by the algorithm.
The repair status of a specific piece of equipment shall be displayed to the operator.
Incident Management (IM)
General
TM002
Minimum functionality
FEAT5.1.2
TM003W
Incident type
FEAT5.1.3
A009
Video verification
The incident management subsystem shall acquire data from the vehicle detection subsystem and include the following functionality at a minimum:∙ Incident verification;∙ Motorist information;∙ Response;∙ Site management;∙ Traffic management; and∙ Incident clearance.
The incident management function shall support operator entry of the incident type such as HAZMAT spills.
The SunGuide software shall provide software for video verification of messages posted on DMS to the extent possible due to physical configuration in the field of the camera and sign.
GUI
2
GUI
2
GUI
2
GUI
2
IM
IM
1
1
EM
1
EM
1
EM
1
38
FEAT5.1.4
TM001
Minimize keystrokes
FEAT5.1.5
DM008D
Limit to one phase messages
FEAT5.1.6
DM009D
Replacement words for messages
FEAT5.2
The SunGuide system's incident management function shall minimize the number of key strokes for the entry of traffic incidents while providing drop‐down menus, check boxes, and data interfaces with subsystems such as the road weather information systems (RWIS), vehicle detection, motorist aid, vehicle detection, motorist aid (AVI), DMSs, and CCTVs.
The system shall have a configuration setting that specifies only one phase messages will be generated.
Message library shall contain a prioritized list of words and replacements to be used in limiting messages to one phase messages.
Detect
FEAT5.2.1
A001
FEAT5.2.2
ID001
The SunGuide software shall provide software for incident detection along the limited‐access facilities.
The SunGuide system shall support the detection of incidents or congestion, via a software Automatic detection of incident algorithm, that determines occupancy, volume, or speed and makes a determination based on user‐
or congestion
defined thresholds.
Incident detection EM
1
EM
3
EM
2
IM
1
EM
1
IM
1
39
FEAT5.2.3
ID002
FEAT5.2.4
ID003
FEAT5.2.5
ID004
FEAT5.2.6
ID002W
View congestion report The SunGuide system shall provide the ability to view a congestion report for all roadway segments in the system. The congestion report shall include a graphical display and the following information for each roadway segment in the system:∙ Roadway segment identifications;∙ Source of the incident or congestion information;∙ Reported speeds [in miles per hour (MPH)]∙ Historic speeds (in MPH);∙ FDOT's LOS;∙ Congestion cases (i.e. closed, heavy, moderate, none, or free flow); and∙ Other recommended parameters.
The workstation operator shall have the ability to View incident or congestion raw view an incident or congestion raw data report for data all links in the system.
The workstation operator shall have the ability, via a menu and the selection of a link on a map, to enter manual incident or congestion information. The incident or congestion information the user may enter shall include:∙ Congestion case (i.e. Manual incident entry
closed, heavy, moderate, none, or free flow);∙ Incident types;∙ Roadway weather conditions; and∙ Incident duration (i.e., the amount of time incident the will last).
Graphical displays The congestion report shall include graphical displays and the following information for each roadway segment in the system∙ Roadway segment identifications;∙ Roadway segment geometries;∙ Source names (determined by the algorithms);∙ Reported speed, volume, and occupancy; and∙ Congestion case.
IM
1
IM
1
IM
1
IM
1
40
FEAT5.3
FEAT5.3.1
Manage
TM001R
FEAT5.3.2
TM002R
FEAT5.3.3
TM003R
FEAT5.3.4
TM005R
FEAT5.3.5
TM006R
FEAT5.3.6
TM007R
FEAT5.3.7
TM008R
Geographic personnel lists The personnel list shall be on a geographic basis and, at a minimum, shall include.∙ Response personnel/and contacts;∙ Geographic agency responsibilities;∙ Talk list (i.e., responders contact list);∙ Radio frequencies;∙ Phone/ and facsimiles numbers; and∙ Pager numbers.
The incident management software will provide the ability to redirect incident information to Messaging
standard message services (such as FAX, email, pagers).
The incident Management function shall support the cataloging of incident management teams and resources with a listing of equipment, material, Cataloging of incident management teams/resources and the available personnel who possess special skills.
Recommend DMS/HAR locations and messages
The incident management response function shall recommend a set of DMS locations and messages for the workstation operator to select. In addition, HAR messages shall be activated.
The incident management response function shall recommend a set of HAR messages to be activated.
The incident management response function shall recommend alternate routes in response to Recommend alternate routes
incidents that are blocking roadways.
Recommend a set of HAR messages
Select alternate maps
In response to incidents requiring alternate route(s), the workstation operator shall be able to select alternate maps via drop down menus.
IM
1
EM
1
EM
1
IM
1
EM
1
IM
2
EM
1
EM
1
41
FEAT5.3.8
TM009R
Communicate with detour message signs FEAT5.3.9
TM010R
Hierarchy of traffic management activities FEAT5.3.10
TM005
Personnel lists and contact numbers FEAT5.3.11
FEAT5.3.12
FEAT5.3.13
TM004
TM001I
TM004R
Distribute information
Format for dissemination
Quick click interface to GIS
When appropriate, the incident management response function shall communicate with detour message signs that are supported by the SunGuide software and TMC communications network capability indicating recommended alternate routes.
The incident management response function shall support a hierarchy of traffic management activities and display these activities for review by RTMC managers.
The incident management function shall provide the workstation operator with personnel lists and contact numbers as well as a catalog of agency resources via drop‐down menus.
The incident management function shall distribute video feeds, traffic flow, and incident information, and traffic event data until the incident is cleared and the traffic flow is back to normal.
The incident management function shall format information for distribution to the following dissemination media:∙ HAR;∙ Commercial radio broadcast;∙ Internet Web servers;∙ DMSs;∙ 511 Telephone systems;∙ Commercial and public televisions;∙ Facsimile machines and pagers; and∙ Additional dissemination mechanisms provided by the dissemination function.
The incident management function shall provide a quick click interface to the GIS maps for the display and location of resources, i.e. fire hydrants.
EM
2
EM
1
IM
1
EM
1
EM
1
IM
1
42
FEAT5.3.14
FEAT5.3.15
TM006
TM007
Incident status GUI
Traffic control procedures
FEAT5.3.16
TM008
Incident removal resources
FEAT5.3.17
TM011R
Catalog of FDOT resources FEAT5.3.18
A006
Construction work zones The incident management function shall provide the workstation operators with GUI screens that record accurate information regarding the incident's current status, the overall progress towards clearance and the equipment required to complete the process.
The incident management function shall support the RTMC with traffic control procedures that include, at a minimum, point traffic control at the scene, managing the roadway space, and deploying personnel to better manage the traffic by improving traffic flow past incident sites and on alternate routes.
The incident management function shall provide support to the incident clearance process by the cataloging of resources for the removal of the all types of incidents.
Included in the catalog shall be the resource, location, cost of service, and availability of related equipment and resources.
The SunGuide software shall provide for the identification of construction work zones and activities to support operations and management of these work zones and, where smart work zone management is provided, integration of the smart work zone management into freeway management systems (FMS) and incident management systems (IMS).
EM
1
EM
1
EM
1
EM
1
EM
1
43
FEAT5.3.19
ID005
FEAT5.3.20
A010
FEAT5.3.21
A012
FEAT5.3.22
FEAT5.3.23
A015
A022
Map display
The system shall have a map display of the current incident or congestion for each segment. The map shall change the color of the roadway segment based on the current condition. An algorithm will determine the congestion case.
The SunGuide software shall provide software for incident data archiving. The data archived Incident data archiving
currently includes;∙ Location∙ Start and end times∙ Response plan
The SunGuide software shall provide software for Management and dispatch of the management, dispatch, and coordination of RR Service Patrols
Road Rangers Service Patrols.
Coordination of freeway incident management team
Diversion routes The SunGuide software shall provide software for coordination with a freeway incident management team involving major stakeholders.
The SunGuide software shall provide software for the maintenance of a list of diversion routes for management of traffic during incidents and evacuations. The software shall tie in with construction updates to avoid detours into construction areas.
IM
1
EM
2
RR
3
EM
2
EM
1
44
FEAT5.3.24
A023
Lane or road closures
FEAT5.3.25
TM010R1
Severity levels
FEAT5.3.26
TM014R
Milepost entry
FEAT5.3.27
TM015R
Roadway association
FEAT5.3.28
TM005R1
Devices on roadways
FEAT5.3.29
TM012
Incident ID
The SunGuide software shall provide software for the management of lane or road closures during natural or manmade disasters or evacuations and integration with computer‐aided dispatch (CAD) systems for incident detection with regional communications centers (RCCs) and emergency operations centers (EOCs) through co‐location, Center to Center Communications or the provision of operator stations in the TMC.
The IM subsystem shall support three severity levels of incidents that will have a configurable distance (in miles) for which devices for messages will be selected: level 3 (most severe), level 2, level 1 (least severe).
An incident record shall contain a text field for entry of milepost location information.
Incidents shall always be associated with a roadway defined in the SunGuide network.
The incident response plan shall suggest all DMS/HAR devices on roadways leading to the incident location within the distance specified with the severity level of the incident.
When a new incident is created, it shall automatically be assigned a sequential incident ID number. This number shall appear along with the textual incident ID in every place that it appears. The ID shall roll over when it exceeds 4,294,967,296.
EM
2
EM
1
EM
3
EM
1
EM
1
EM
1
45
FEAT5.3.30
DM011M
Response plan priority levels
FEAT5.3.31
TM014
Cancel response plan
FEAT5.3.32
TM016R
Remove response plan messages
FEAT5.3.33
DM016M
Response plan C2C devices
FEAT5.3.34
TM001P
Fonts in response plan messages
FEAT5.3.35
DM005M6
Number of templates
FEAT5.4
FEAT5.4.1
SunGuide shall provide a mechanism for prioritizing messages placed by the IM subsystem based on distance from the incident, with messages on signs closer to the incident being given higher priority.
When an incident is closed, the response plan associated with the incident shall be cancelled.
When a response plan is cancelled, all messages that were part of the response plan shall be removed from the queues of the devices in which they were placed.
SunGuide shall provide a mechanism to include DMS devices from available list through C2C interface when generating an IM response plan.
The incident management function shall use each DMS' font characteristics to determine response plan messages.
SunGuide shall provide a minimum of one (1) and no more than thee (3) message templates for each DMS device in the District's inventory (not to exceed 512 signs).
Incident ownership
IM008
Ownership property
An incident, exclusive of construction or planned events, shall have ownership characteristic in that the person who is managing the incident shall be identified as the owner of the incident and the owner shall be displayed when incident status is displayed.
RPG
1
EM
1
EM
1
IM
2.1
RPG
2.1
RPG
2.1
IM
1
EM
1
46
FEAT5.4.2
IM007O
FEAT5.4.3
IM007O1
FEAT5.4.4
IM001O
FEAT5.4.5
IM003O
FEAT5.4.7
TM002B
FEAT6
FEAT6.1
FEAT6.2
FEAT6.3
Permission to modify event without ownership check
The incident management subsystem shall allow an operator with appropriate permissions to modify an event only after first obtaining ownership.
Data Distribution (DD)
S010
DD001
DD002
Distribute data in real time.
The SunGuide system shall provide a function to distribute data in real time. Data shall include but not be limited to:∙ Travel time data;∙ Speed data; ∙ Video images; and∙ Amber Alert data.
The data distribution function shall be capable of retrieving data from the database and updating Retrieving real time data from user workstations with the data as soon as it is the database
received into the database.
Data selection
The user shall be capable of selecting the data to be displayed by the data distribution function.
Graphical User Interface ‐ General (GUI)
FEAT7
FEAT7.1
When an operator logs off of SunGuide all Remove owner on logoff
incidents that are owned by the operator shall be marked as no owner.
All ownership changes need to be logged to the Log ownership changes
IM database.
Only the "owning" operator shall be able to make Only owner can modify incident
changes to an incident.
There shall be a "Take Ownership of Incident" privilege that allows an operator with this Take ownership of incident
privilege to take ownership of any incident.
TM003
Workstation GUI screens shall support the entry Entry of location and direction of the exact location and direction of travel data of travel data
as efficiently as possible.
EM
1
EM
1
IM
1
EM
1
EM
3
DD
1
DD
1
DD
1
DD
1
GUI
1
GUI
1
47
FEAT7.2
Map based
FEAT7.2.1
S014
FEAT7.2.2
GS001
FEAT7.2.3
GS002
FEAT7.2.4
GS003
FEAT7.2.5
GS004
The SunGuide system shall provide a GIS interface that displays shape files.
The SunGuide GIS function shall translate shape files containing GIS‐formatted data such as traffic GIS data
speed, incidents, message sign data, and device status.
Data such as traffic speed, incidents, message sign Viewable from PTMCs, VTMCs, data, device status, and other data shall be RTMCs and FDOT central office viewable from PTMCs, VTMCs, RTMCs and the FDOT Central Office.
The SunGuide graphical map shall display a graphic depicting a map of the selected Geographical map display
geographic area with associated roadways, device icons for supported devices and other geographic or ITS features.
The GIS function shall support remote viewing of data through a TCP/IP connection at a minimum Remote viewing
speed of 1.544 million bits per second.
GIS software interface
FEAT7.2.7
GS009C1
Color selection dialog
FEAT7.2.8
WS015
Map views
FEAT7.2.9
WS001M
Roadway links options
All color choices shall be made using a standard color selection dialog similar to what is provided by Microsoft Windows.
SunGuide shall provide two map views, one called the FIHS Conditions Map and the other called the Central Florida Conditions Map.
SunGuide shall provide a map option that will display all FIHS roadway links on the FIHS Conditions map and all Central Florida roadway links on Central Florida Conditions map.
GUI
1
GUI
1
GUI
1
GUI
2
GUI
1
GUI
1
GUI
2
GUI
3
GUI
3
48
FEAT7.2.10
WS001Z
Reporting map scale
FEAT7.2.11
WS002M
Conditions map
FEAT7.2.12
WS002Z
Largest scale selectable
FEAT7.3
The Operator Interface shall provide ability to increase the scale of the conditions reporting map (called zoom) by drawing a box with the mouse around the portion of that map that is to be displayed on the full workstation screen.
The FIHS Conditions map shall be similar to the statewide map provided on the statewide FIHS Web site.
The largest scale selectable shall include a statewide view that includes the entire FIHS incident/event data.
General
FEAT7.3.1
WS010
Behavior on duplicate login
FEAT7.3.2
WS009
Display login name
FEAT7.3.3
GS009C
Configurable colors for icons
FEAT7.3.4
WS008
Display error messages
FEAT7.3.5
GS010
Display color legend
A user who is already logged in on another workstation and tries to log in on another workstation shall be automatically logged off the first machine and a message shall be displayed explaining what happened.
The system shall display the currently logged on username somewhere in the browser window or in the title bar of the window.
The colors associated with device status icons shall be configurable.
If any device control commands issued by the operator fails, the failure shall be indicated by a "error" warning message in the status message window, this include errors caused by authorization failures.
The operator workstation display shall be able to display a legend indicating the color chosen for each color‐configurable item.
GUI
3
GUI
3
GUI
3
GUI
1
GUI
1
GUI
1
GUI
2
GUI
1
GUI
2
49
FEAT7.3.6
WS011
Display all driver data
FEAT7.3.7
AV007L3
Roadway display
FEAT7.3.8
TD009
Data inclusions
FEAT7.3.9
WS002M1
Conditions map displays
FEAT7.3.10
WS002M2
Event icons
FEAT7.3.11
S039
Collect, process, display data
FEAT7.3.12
DF104
Distribute raw/stored data
FEAT7.3.14
DF019G
GUI to define instrumented road segments
FEAT7.4
FEAT7.4.1
The GUI shall provide a way to display all data available from the device driver for each device.
GUI
2
Mousing over any roadway displayed on the SunGuide map shall display the street name.
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
4
GUI
1
GUI
1
SunGuide data shall include, but are not limited to: incident/event data, traffic sensor data, and weather data.
FIHS Conditions map shall be capable of displaying all available data, not simply the data that is available to the public via the FIHS Web site.
Event icons and/or color coded roadways shown on the SVG GUI SunGuide maps shall be color‐
coded and clickable.
SunGuide shall collect, process and display traffic data, center‐to‐center data, data from selected field devices, and operator‐entered incident/event data.
SunGuide shall be able to distribute raw and stored data to registered end‐users.
The GUI component shall support a SunGuide operator with appropriate permissions to define the instrumented road segments to be used to calculate travel times.
TSS
ID001A
Audible alerts
The GUI shall provide audible notification of congestion alerts for logged‐on operators.
50
FEAT7.4.2
FEAT7.4.3
FEAT7.4.4
FEAT7.4.5
GS009
Detector icons
GS008
Detector icons2
IM008O1
Flash unacknowledge lane alarms
WS016
Graying of icon or segment
FEAT7.4.6
WS017
View directional conditions differences
FEAT7.4.7
WS003M
Showing link based speeds
FEAT7.4.8
WS004M
Operator interface displays
The system map shall display icons at the location provided by FDOT of each detector sensor itself. The sensor icon shall change color to indicate the detector's operational status. The colors associated with "operational" and "failed" status shall be configurable.
The map shall display icons at the location of each detector station. The icon shall change color to indicate the detector station's operational status. The status colors shall be configurable.
Lane segments associated with unacknowledged alarms shall flash on the map.
The loop detector icon and/or road segment shall go "gray" when the system determines that no data are available at a loop detector station or a supervisor intentionally disables the data collection links for public dissemination purposes.
SunGuide GUI shall provide the capability to view the difference in directional conditions on instrumented roadways on the conditions map (FIHS and Central Florida).
SunGuide link based speeds shall be shown as link information, not as point data.
The operator interface shall display the most current traffic conditions for monitored roadways.
GUI
1
GUI
1
GUI
1
GUI
3
GUI
3
GUI
3
GUI
3
51
FEAT7.4.9
WS004M1
FEAT7.4.10
WS018
FEAT7.4.11
WS019
FEAT7.5
The SunGuide web site shall have an administrator configurable value that will allow Map refresh rate
the map refresh rate to be set in (measured in seconds).
All data shall be available on the SunGuide operator GUI through a single map so that an Data available through single operator would not have to access several maps map
to obtain information on a roadway segment.
Login screen
DMS
FEAT7.5.1
DM006D
Message library sorting
FEAT7.5.2
DM007D
Keystroke selection
FEAT7.5.3
FEAT7.5.4
The Operator Interface shall provide users with a login screen on which they will be required to enter their user name and password.
DM003D2
DM003D3
Display errors
Display extended status
Message library entries shall be sorted in alphanumeric order within a library.
When choosing a message from a message library, the system shall accept letters typed by the operator, and scroll the message list to the first message matching these letters.
If any errors (including but not limited to pixel, lamp, temperature or fan errors) are reported during the regular polling of a DMS device, the system shall: generate an operator alert, change the color of the icon for the DMS device on the map to a configurable color.
The DMS status form shall provide a way to request and display the following extended status information from the signs: fan status, pixel errors, sign temperatures, power supply status.
GUI
3
GUI
3
GUI
3
GUI
1
GUI
1
GUI
1
GUI
1
GUI
1
52
FEAT7.5.5
FEAT7.5.6
DM012M
DM005M5
Manual DMS message permission GUI characteristics
FEAT7.5.7
DM015
DMS Conflict Dialog
FEAT7.5.7.1
DM015A
DMS Conflict Approval
FEAT7.5.7.2
DM015B
FEAT7.6
FEAT7.6.1
FEAT7.6.2
FEAT7.6.3
DM008M
The system shall have a permission field (per user) for typing a manual message for a DMS.
The SunGuide GUI in all operator viewable screens shall show the correct number of characters per line but will not use proportional font spacing.
Conflicts arising from posting DMS messages will be handled in a single dialog regardless of the number of conflicts.
The DMS conflict dialog shall contain options to approve multiple messages at the same time.
The DMS conflict dialog shall contain an option to DMS Conflict Approved Word add non‐approved words to the approved words Addition
list, provided the operator has appropriate permission.
MAS
The system shall allow the operator to specify a Manual message priority
priority level when activating a message manually.
DM009M
Default manual message priority
DM010M
Default sequence message priority
The default priority level for manual message activation shall be the highest priority level.
The default priority level for messages included in an automatic sequence shall be the lowest priority level.
GUI
2
DMS
2.1
GUI
5
GUI
5
GUI
5
GUI
1
GUI
1
GUI
1
GUI
1
53
FEAT7.6.4
FEAT7.6.5
TM013R
DM014M
GUI functionality
The system shall have a permission field (per user) Edit MAS message permission for editing the message in a device queue.
FEAT7.6.6
Override Spelling Conflicts
FEAT7.6.6.1
MAS to tell DMS of Override
FEAT7.7
IM
FEAT7.7.1
TM009
The queue status screen shall provide the following: 1) a display of the contents of the message queue, including message, priority, and associated incident ID, if any, for each message in the queue. 2) the ability to remove individual messages from the message queue. 3) a "blank" button that removes all the messages from the queue 4) Ability to change priority of messages on the queue.
Response time
MAS shall allow for a configuration setting in the SunGuide configuration file to override all spelling conflicts
If MAS has been configured to override spelling conflicts, MAS shall add a flag to all requests made to DMS to post a message to indicate that DMS should override any spelling conflict if one exists.
It shall be possible to create an incident, enter required basic information (listed below) and select appropriate signs and/or HARs within 60 seconds of when the operator confirms the incident. Required basic information consists of:
∙Incident Description
∙Route
∙Direction
∙Cross Street
∙Lane Configuration
GUI
1
GUI
2
GUI
5
GUI
5
GUI
1
GUI
1
54
FEAT7.7.2
TM001W
Prefilled fields
When an incident is created from a congestion alert associated with a detector link, or when manually created by an operator clicking on a detector link, the following information in the incident form shall be filled in automatically: Route (main road), direction, cross street, lane configuration, milepost number.
When a data field in an incident form requires entry of a time and/or date, the current time Default date
and/or date shall appear as the default entry, if appropriate for the field.
It shall be possible to relocate incident icons using Relocate incidents
a drag‐and‐drop methodology.
Operators shall be able open incidents that they Read‐only access of incidents
do not own with read‐only access.
Ownership of each incident shall be displayed in Display of owner
the incident list.
It shall be possible to filter the incident list by Filter incidents by owner
owner.
The icons for incidents with no owners shall flash Audible alarm for unowned on the map and sound an audible alarm with the incidents
exception of construction or planned event incidents.
The system shall periodically sound an audible alarm at all logged‐on workstations if there is any Audible alarm on workstations
active incident without an owner.
FEAT7.7.3
TM001W1
FEAT7.7.4
GS007
FEAT7.7.5
IM002O
FEAT7.7.6
IM004O
FEAT7.7.7
IM005O
FEAT7.7.8
IM008O
FEAT7.7.9
IM008O1
FEAT7.7.10
IM006O
Alarm reoccurrence timer
FEAT7.7.11
TM004A1
Edit IM message permission
The audible alarm shall sound for 5 seconds and then shut off for a programmable period of time from 5 seconds to 2 minutes.
The system shall have a permission field (per user) for editing an incident generated message.
GUI
1
GUI
1
GUI
1
GUI
1
GUI
1
GUI
1
GUI
1
GUI
1
GUI
1
GUI
2
55
FEAT7.8
CCTV
FEAT7.8.1
TV003D1
Camera menu activation
FEAT7.8.2
TV001D2
Configurable joystick buttons
FEAT7.8.3
DF021G1
Block video from public dissemination
FEAT7.9
TM017R1
Display SB status
FEAT7.9.2
GS011
SB PLC location
FEAT7.9.3
GS011S
SB icon flashing
FEAT7.10
HAR
FEAT7.10.1
Manual HAR message permission
DM013M
FEAT7.11
SunGuide software operator shall be able to display the latest status from each safety barrier sensor.
SunGuide map shall display the location of the safety barrier PLCs .
The icon associated with the sensor reporting a breakaway switch activation shall flash until a user acknowledges the alarm.
The system shall have a permission field (per user) for typing a manual message for a HAR.
EM/PM
TM003B
FEAT7.12
FEAT7.12.1
The GUI shall allow user configuration of joystick button functions
The status of the "block video" flag for a CCTV device shall be included with the CCTV status data when transmitted over C2C.
SB
FEAT7.9.1
FEAT7.11.1
The CCTV GUI shall support activating and operating camera menus for NTCIP CCTV devices.
Login to subsystem type of "URL"
The SunGuide GUI shall permit a user to log into a non‐specific subsystem with a subsystem type of "URL" that is connected to the data bus when SunGuide is operating with a SMART software interface.
SAS
TV001G
CCTV icon color for applied schedule
The CCTV icon color shall change when the schedule activates and return to its normal color when the schedule no longer applies.
GUI
1
GUI
2
GUI
2
GUI
4
GUI
2
GUI
2
GUI
2
GUI
2
GUI
2
GUI
2
GUI
2
GUI
2
GUI
2
GUI
2.2.2
56
FEAT7.12.2
TV001G1
FEAT7.12.3
TV001G2
FEAT7.12.4
TV005C
FEAT7.12.5
TV007C3
FEAT7.13
FEAT7.13.1
An operator with appropriate permissions for the CCTV icon color for associated CCTV subsystem shall be able to designate a color schedule
for the CCTV icon when it is associated with a schedule.
The CCTV icon color shall remain the same when CCTV icon color same for locks an operator takes control of the camera (e.g. locks it).
An operator with appropriate permissions shall be Display currently active able to display the currently active sequences and sequences
schedules on the operator map GUI.
Suspend/resume schedule
The operator shall be able to suspend and resume the schedule for a specific camera or cameras through the use of the CCTV GUI.
AVL
EM018G1
Map position
FEAT7.13.2
EM010
Create new incident
FEAT7.13.3
AV002V
Use SVG icon
FEAT7.13.4
AV005V
Icon color
FEAT7.13.5
AV006V
Tooltip for summary
A "Find on map" option shall be provided from the list, which will re‐center the SunGuide map to the current position of the vehicle icon.
An operator shall be able to invoke the incident management window, with location information pre‐filled by right‐clicking on an AVL icon and choosing "create new incident at vehicle location".
The vehicle icon symbol for each vehicle shall be an SVG icon.
Vehicle icon color shall be configurable.
When an operator hovers the mouse cursor over an AVL icon on the SunGuide map, SunGuide shall display a "tooltip" like status box that shows the vehicle summary data.
GUI
2.2.2
GUI
2.2.2
GUI
2.2.2
GUI
2.2.2
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
57
FEAT7.13.6
FEAT7.13.7
AV010V
AV011V
Icon appearance
Show detailed status
FEAT7.13.8
AV011V1
Floating window display
FEAT7.13.9
AV011V3
Display vehicle information
FEAT7.13.10
AV001T
Viewing vehicle status
FEAT7.13.11
AV003T
Replay options
FEAT7.13.12
AV006
Vehicle icon relocation
FEAT7.13.13
AV008V
Refreshing vehicle display
The relevant AVL Icon shall appear different in shape and color, depending on the availability status reported by data feed from the vehicle.
An operator shall be able to bring up a detailed vehicle status window by right‐clicking on an AVL icon and selecting "show detailed status".
The "Detailed Vehicle Status" window shall be a floating window similar to other SunGuide Status windows.
The operator can display information about a different vehicle in the Detailed Vehicle Status window by clicking on any other visible AVL icon.
The operator shall be able to view the vehicle status via the SunGuide GUI Map.
The operator with appropriate permissions shall be able to right click on the SunGuide map in an area without any symbols and get a menu of "AVL Replay" options to generate a historical track of a selected vehicle.
The icon representing the vehicle on the GUI be relocated to show its new position when a position report is received for that vehicle.
The SunGuide display of vehicles shall be refreshed whenever a new position report is available for display.
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
58
FEAT7.13.14
AV008V1
Displaying new positions
FEAT7.13.15
AV008V2
Map positioning
FEAT7.13.16
AV007
Turn off display option
FEAT7.13.17
AV012V
Noticeable icon
FEAT7.14
A "find on map" option shall be provided in the Vehicle List window that will re‐center the SunGuide map to the position of the selected vehicle.
The operator shall be able to turn off the display of vehicle position information on the SunGuide map.
A "more noticeable" icon (e.g., flashing, larger, exclamation) shall be used when a vehicle stops or leaves the geo‐fenced area without justification (non‐patrolling status entered into the road ranger tablet).
EM
FEAT7.14.1
AV007L4
Road ranger assignment
FEAT7.14.2
EM010G2
Filter and sort
FEAT7.14.3
EM010G3
Save filter/sort
FEAT7.14.4
If a position report is not displayed on the SunGuide map before a new position is received, the newer position will be displayed but the older one will be maintained in the track history and available for replay.
Responder audit
A "pop up window" advising of Road Ranger Status shall appear on the GUI if the operator selects a Road Ranger vehicle that is already assigned to another incident.
The operator shall be able to filter/sort events by county, operator, district, roadway, type, Road Ranger beat(s), and any other data fields contained in the event list.
The operator shall have the option to save the filter/sort as a default associated with the operator login and ID.
GUI
3
GUI
3
GUI
3
GUI
3
EM
3
GUI
3
GUI
3
GUI
3
GUI
3
59
FEAT7.14.4.1
EM020G
FEAT7.14.4.2
EM020G2
FEAT7.14.4.3
EM020G6
FEAT7.14.4.4
FEAT7.14.4.5
FEAT7.14.4.6
EM020G7
EM020G9
A Responder Audit screen shall be incorporated into the existing audit feature of the SunGuide Use existing permissions and GUI, using the existing permissions scheme and user authentication methods of the SunGuide authentication methods
GUI.
The operator shall be able to leave any of the fields blank in case that information is not Operator can leave fields blank
available, except that a record must have at least one timestamp entered.
The software shall require the operator to enter the time that an activity was performed, however the software shall also require the timestamp to Enter time activity performed
fall within the arrival and departure timestamps for the vehicle record.
Timestamp warning
The GUI shall warn the user when a timestamp is entered which is earlier than the event start time or later than the event closed time.
The GUI shall display a summary of all the agency Summary of response times and response times, the detailed vehicle response activities
time records, and all the activities performed.
EM020G10
Display event information
FEAT7.14.4.7
EM020G11
Event chronology summary/report
FEAT7.14.4.8
EM021G
Enter free‐text data
The GUI shall display the event location, event number, and blockage history for an event.
The GUI shall provide an event chronology summary window with the ability to generate a report.
A comments field shall be provided for the operator to enter free‐text data.
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
GUI
3
60
FEAT7.14.5
EM004U
FEAT7.14.6
EM004U1
FEAT7.14.7
DF020G
FEAT7.14.9
DF004G1
FEAT7.14.10
DF004G2
FEAT7.14.11
FEAT7.14.12
DF004G3
DF005G
The operator shall have at least two ways to select an event: (1) selecting from the list of active Selecting an event
events, or (2) selecting from a filtered list of all events.
The operator shall be able to filter events by Filtering events
month, location, type, blockage, or responding agency involved.
The GUI shall alert the operator to potential Alert for potential conflicts conflicts when an alert is selected to be processed.
An event may be geographically located at a point Event located with road and location by selecting a main road and the nearest cross street
cross street from a drop down menu of covered roads.
A congestion event may be geographically located Event located as a section of as a section of roadway by selecting a starting EM roadway
location and an ending EM location.
An event may be geographically located in an area location by selecting an EM location from a drop Event located by geographic down list of configured EM locations. The area
comments field of the event shall be used to indicate a region wide event effecting traffic.
The icons for events that have been marked as "publishable as Traveler information" shall be Icons for traveler information modified to visually depict that the event is being events
publised to the traveler information providers.
GUI
3
GUI
3
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
61
FEAT7.14.13
DF006G
FEAT7.14.14
DF007G
FEAT7.14.16
DF010G
FEAT7.14.16.1
DF010G1
FEAT7.14.17
DF010G2
FEAT7.14.19
DF010G4
FEAT7.14.20
DF009G
FEAT7.14.20.1
DF009G1
FEAT7.14.21
DF021G
A window on the SunGuide GUI shall display the interpreted text of the traveler information Display interpreted text for message that will be sent to the IDS based on the SunGuide selected FDOT modified SAE J2540 traveler info message
codes and EM reference locations upon operator request.
An event created by the SunGuide operator for the traveler information shall have a field where Select duration field for traveler the operator can enter into a text box how long info event
the event is expected to last.
Same ownership rules for traveler information
Ownership rules shall apply to events created by the operator for the traveler information function.
The operator who created an event shall be Event creator identified in event identified in the event information available information
through the SunGuide GUI.
Any events owned by an operator when they log Events owned by logged‐in out shall continue to be owned by the operator SunGuide operators
after they log out.
Only event owner can Only the owner of an event can edit or delete the edit/delete event
event.
The Graphical User Interface component shall Operators may enter severity allow a SunGuide operator to enter the severity level
level for the event created for the Data Fusion Component.
Event severity shall be one of the following Event severity values
values: Severe, Moderate, Minor, or Unknown.
Events to be marked for selective dissemination
The GUI component shall allow an operator to mark events for selective dissemination to the public.
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
62
FEAT7.14.23
EM029
FEAT7.14.24
EM030
FEAT7.14.25
EM031
FEAT7.14.26
EM032
The Event Details dialog shall alert the operator if they attempt to close an event where one of the following conditions:
"Timestamps are not set
oTMC Notification
oTMC Verification
oFirst Responder Arrival
oLane Clearance Time
oLast Responder Departure
"Time Spans
oInitial notification 15 minutes after TMC Performance Measure Popup
notification
oTMC notification 15 minutes after TMC verification
oTMC verification 15 minutes after first responder arrival
oFirst responder arrival 15 minutes after lane clearance
oLane clearance 15 minutes after last responder departure
Responder arrived at an event but never departed.
SunGuide shall allow a user to include a DISTANCE “Distance” Template Tag
tag as part of a DMS response plan template
SunGuide shall allow a user to configure a standard suffix for use when displaying distances of one or more miles on a DMS
SunGuide shall allow a user to configure a Distance string for less than one standard text string for use when displaying mile
distances of less than one mile.
Distance Suffix
GUI
5
GUI
5
GUI
5
GUI
5
63
FEAT7.14.27
EM033
FEAT7.14.27.1
EM033A
FEAT7.14.27.2
EM033B
FEAT7.14.27.3
EM033C
Distance calculation
If the DMS is calculated to be less than one mile Distance string for less than one from the incident, SunGuide shall replace the mile usage
DISTANCE tag with the configurable less than one mile text string.
If the DMS is calculated to be one mile or more from the incident, SunGuide shall replace the DISTANCE tag with the integer portion of Distance calculation
calculated distance (the mathematical floor) followed by the configurable distance suffix text.
Invalid distance Calculation
FEAT7.14.28
DMS in Event Chronology
FEAT7.14.28.1
DMS Blanking in Event Chronology
FEAT7.14.29
EM040
When generating a response plan message for a DMS, SunGuide shall replace a DISTANCE tag in the template with text determined by the distance from the DMS to the incident the message relates to, as determined by the device linking configuration
Affected Area head/tail
If the distance between the DMS and the incident cannot be calculated, SunGuide shall remove the DISTANCE tag from the suggested message.
When a DMS message belonging to an event's response plan is posted to a DMS, EM shall enter a record of the message in the event's chronology
When a DMS message belonging to an event's response plan is removed from a DMS, EM shall enter a record of the message in the event's chronology.
When a Construction, Special Event, Bridge Work, Visibility, Weather or Flooding event is created, the user shall have the ability to set the head and tail of the affected area.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
6
64
FEAT7.14.30
EM041
FEAT7.14.31
EM042
FEAT7.14.31.1
EM042A
FEAT7.15
FEAT7.15.1
DF204R1
FEAT7.15.2
DF207G
FEAT7.15.3
ID203G3
When an event contact is selected and a phone Populate Event Contact Phone number for that contact has been configured, the Number
software shall automatically populate the contact phone number field
When an event location is selected, the Nearest Nearest CCTV Camera
CCTV Camera will be set to the geographically closest camera to the event.
When changing an event location, if the Nearest CCTV Camera is not the geographically closest Changing Nearest CCTV Camera
camera, the Nearest CCTV selection will not change.
511
SunGuide operator interface shall support the Record incident link reports recording of Incident Link Reports by SunGuide operators.
SunGuide Operator Interface shall display a list of 511 reporting routes defined as the entire table of Display of 511 routes
currently applicable routes that are shared by the Statewide 511 and SunGuide.
Alerts sent when WAV file creation exceeds 1 minute
SunGuide shall alert an operator who is recording or composing a WAV file when the duration of the WAV file exceeds 60 seconds indicating the WAV file will not be saved.
GUI
6
GUI
6
GUI
6
GUI
3
GUI
3
GUI
3
GUI
3
65
FEAT7.15.4
ID203G6
FEAT7.15.5
DF029G
FEAT7.15.6
DF028G
FEAT7.16
FEAT7.16.1
TM005R9
FEAT7.17
FEAT7.17.1
FEAT7.17.2
DM006V
DM009V
The SunGuide Operator Interface for recording WAV files shall provide the operator with an indication of how much time a WAV file recording is taking and alert the operator as the elapsed recording time approaches 60 seconds. An WAV file recording indication example would be to provide a 60 second count for time left
down clock display that turns yellow when the time remaining is 15 seconds or less and turns red when the time remaining is 5 seconds or less.
The SunGuide floodgate GUI shall allow the Select floodgate message from operator to select a Floodgate message to edit statewide naming convention based on the FDOT statewide Floodgate naming convention.
The SunGuide floodgate GUI shall support two Support two sound files and sound files and two banner messages for each banner messages
floodgate message.
RPG
SunGuide shall display on the operator's Display recommended workstation recommend messages for signs to messages for signs
manage traffic as part of a response plan.
VSL
The operator interface shall have the capability to display the current contents of all VSL and Display recommended VSL recommended changes to them and displaying changes
the current contents of all DMS.
Display for VSL Plan Group
SunGuide shall display an empty menu for the VSL Plan Group when no VSL group is selected. There is no VSL group selected when the VSL window is initially opened or after an new plan is set for a previously selected group.
GUI
3
GUI
4
GUI
4
GUI
3
GUI
3
GUI
3
GUI
3
GUI
4.2
66
FEAT7.18
TVT
FEAT7.18.1
TM001G
FEAT7.18.2
TM005G1
FEAT7.18.3
TM003G1
FEAT7.18.4
TM005G
FEAT7.18.5
TM006G
FEAT7.18.6
FEAT7.18.7
TM013T2
TM001G2
FEAT7.19
FEAT7.19.1
DF005
Travel times shall be displayed on the SunGuide Graphical User Interface.
Data shall be updated on the GUI at the same rate Data updated on GUI that it is generated by the travel time module/posted to the DMS Module.
The SunGuide operator shall be able to identify Identify devices associated to which DMS are associated with which routes or routes/segments
segments for which travel time is calculated for.
Display travel times
The SunGuide GUI shall enable viewing of current travel times for different segments in a tabular format.
The SunGuide GUI shall allow the operator to Display number of vehicles used display the number of vehicles used to calculate for travel time
the current probe travel time for a segment.
TVT segments displayed in tabular format
SunGuide shall be able to display on the SunGuide GUI, for comparison purposes, the multiple Travel Display multiple travel times for Times for each roadway segment if different data sources are used to calculate it and indicate what each segment
data source was used to calculate the travel time.
Data shall be updated on the GUI at the same rate Data updated at same rate as that it is generated by travel time function and availability for TVT display
available for display by a DMS.
DFS
SunGuide shall support the capability for the operator to validate or alter event data received Quality checks and ability to from external sources after the external event modify input
data is incorporated into a locally managed event.
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4.2
67
FEAT7.19.2
DF019
FEAT7.19.4
DF027
FEAT7.19.5
DF031
FEAT7.19.5.1
DF031A
FEAT7.19.5.2
DF031A1
FEAT7.19.5.3
DF031B
The Data Fusion subsystem shall be controlled DFS controlled/managed via and managed through the SunGuide graphical SunGuide GUI
user interface.
The Data Fusion subsystem shall allow an Selectively filter traveler info operator with appropriate permissions to going to the IDS
selectively filter traveler information going to the IDS.
The Operator shall be able to create a floodgate Create floodgate message via message using the SunGuide GUI which will be SunGuide GUI
distributed on the SunGuide C2C infrastructure.
SunGuide shall provide the ability for an operator Creation/storage of floodgate to create a floodgate message and store the message
floodgate message for later use.
SunGuide shall provide the ability for an operator Create unique name for to create a unique name for the message.
message
Activate message
SunGuide shall provide the ability for an operator to select a previously created and stored floodgate message and "activate" that message.
SunGuide shall display a tree display of previously stored floodgate messages, organized by teh defined folder structure, to the operator for selection.
SunGuide shall provide teh ability for an operator to organized stored floodgate messages
GUI
4
GUI
4
GUI
4
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
FEAT7.19.5.4
DF031B1
Display list of messages
FEAT7.19.5.5
DF031B2
Sort options for floodgage messages
FEAT7.19.5.6
DF031C
SunGuide shall provide the ability for an operator Delete options for floodgate to delete previously stored floodgate messages
messages
GUI
4.3
DF031D
SunGuide shall provide the ability for an operator to manage an organization folder structure for storing floodgates
GUI
4.3
FEAT7.19.5.7
Organize Messages
68
FEAT7.19.5.8
DF031D1
Manage Organization
FEAT7.19.5.9
DF031D2
Manage Messages ‐ Delete
FEAT7.19.5.10
DF031E
Floodgate Multi‐Set
FEAT7.19.5.11
DF031E1
Multi‐Set Display
FEAT7.19.5.12
DF031E2
Expand Floodgate
FEAT7.19.5.13
DF031E3
FEAT7.19.5.14
DF031E4
FEAT7.19.5.15
DF031E5
FEAT7.19.5.16
DF031E6
SunGuide shall allow an operator to create, rename, move, and delete folders.
SunGuide shall allow an opeator to move a previously stored floodgate message from one folder to another.
SunGuide shall allow a opeator to set an identical message to multiple Floodgates with a single operation.
SunGuide shall indicate to an operator which Floodgates share identical messages
SunGuide shall allow an operator to select a message which is currently on a single Floodgate slot and apply it to other Floodgates slots
SunGuide shall allow an operator to view the text of a Floodgate message or web banner as part of an overview.
SunGuide shall automatically select the first open slot number for each selected Floodgate when a Use first open slot for multiset
message is set to multiple Floodgates as a single action.
SunGuide shall abort any attempt to set a message to multiple Floodgates if one or more of Abort if no open slots
the selected Floodgates do not have any open slots.
SunGuide shall indicate to an operator who has selected multiple Floodgates to set a message to Notify operator if duplicate if the given message already exists in one of the slots of any of those Floodgates.
View Floodgate Text
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
69
FEAT7.19.5.17
DF031E7
FEAT7.19.7
DF001G1
FEAT7.19.8
DF025G
FEAT7.19.9
DF012G
FEAT7.19.10
DF015G
FEAT7.19.14
DF011G1
FEAT7.19.15
DF011G2
FEAT7.19.16
DF013G
SunGuide shall indicate to an operator who has selected multiple Floodgates to set a message to Notify operator no open slots if one or more of the selected Floodgates does not have an open slot for the message to use.
The GUI component shall allos a SunGuide operator with appropriate permissions to be able Block video from third parties
to set a "block video" flag for CCTV devices.
The Data Fusion component shall use Center‐to‐
Center configuration to regulate what data is available to third party users
The Graphical user interface shall allow a system administrator to indicate what data is to be Select data to archive
archived.
The Graphical User Interface component shall Support system configuration support the configuration and administration of and administration
the system.
The GUI shall alert the operator when the DTN Alert when wind gusts exceed weather data feed indicates a weather alert has threshold
occurred.
A response plan with an entry to publish to 511 View/edit weather information must be activated for a weather event before the received
weather event information shall be transmitted to the IDS.
The Graphical User interface map shall be configured to indicate operational boundaries to Indicate operational boundaries guide the operators in managing traveler on GUI map
information for their operational area.
Access designation to third party feeds
GUI
4.3
GUI
4
GUI
4.2
GUI
4
GUI
4
GUI
4
GUI
4
GUI
4
70
FEAT7.19.17
DF016G
FEAT7.19.18
DF016G1
FEAT7.19.19
DF011G
FEAT7.19.21
DF018G
FEAT7.19.22
DF019G1
FEAT7.19.23
DF022G
FEAT7.19.24
DF023G
FEAT7.19.24.1
DF023G1
Display current floodgate message
A monitoring display shall display the current Floodgate (or recorded message) status for each “slot”, allowing the operators to see which slots have messages and their status (barge‐in on/off) as well as any other parameters that they might be able to set.
SunGuide operator access to traveler information to manage the information shall be based on Access to traveler info based on permissions and level of access the same as SunGuide permissions
SunGuide Transportation Management Center software.
Weather information shall be included by operator verification of weather alerts and Weather info included by weather event creation and shall pertain to operator selection
specific counties/roadways in Florida and specific EM locations.
The GUI component shall allow an operator with Allow operators to edit location appropriate permissions to edit the District FDOT tables
location tables without having to stop the system.
Provide travel times and delays SunGuide shall provide travel times for Travel for travel time links
Time links
Users shall be able to select the reports to be Select reports to generate
generated based on a drop down list from a separate archive data page.
SunGuide shall display a list of nearby active Alert operator for data source events in a dialog to the operator when a new conflicts
external event is received.
The pop up box or similar mechanism shall Provide sufficient event conflict contain sufficient information about the event information
conflict to allow an operator to resolve the conflict.
GUI
4
GUI
4
GUI
4.2
GUI
4
GUI
4.2
GUI
4
GUI
4
GUI
4
71
FEAT7.19.26
DF028G
FEAT7.19.28
ATIS Severity
FEAT7.19.28.1
DF040
FEAT7.19.28.2
DF040S
FEAT7.19.28.3
DF040E
FEAT7.19.28.4
DF040E1
FEAT7.19.28.5
DF040E2
FEAT7.19.28.6
FEAT7.19.28.7
Floodgate sound files and banner messages DF040E3
DF040E4
The SunGuide floodgate GUI shall support two sound files and two banner messages for each floodgate message.
Sunguide shall allow the operator to create new incident severity criteria specially for FLATIS
The software shall allow an operator to set the ATIS Severity.
The software shall allow an operator to set the ATIS Severity Values
ATIS Severity to Unknown, Minor, Intermediate, or Major.
The software shall suggest a new ATIS Severity ATIS Severity Suggestion
level when an operator has changed the lane blockage for the event.
The software shall suggest an ATIS Severity level by calculating the total percentage of all travel ATIS Severity Calculation
lanes and off ramps blocked.
The software shall suggest an ATIS Severity level of Minor when the total percentage of all travel ATIS Severity Calculation Minor lanes and off ramps blocked is less than or equal to the configured Minor threshold.
ATIS Severity
ATIS Severity Calculation Intermediate
The software shall suggest an ATIS Severity level of Intermediate when the total percentage of all travel lanes and off ramps blocked is less than or equal to the Intermediate threshold and greater than the Minor threshold.
The software shall suggest an ATIS Severity level of Major when the total percentage of all travel ATIS Severity Calculation Major
lanes and off ramps blocked is greater than the Intermediate threshold.
GUI
4
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
72
FEAT7.19.28.8
DF041
FEAT7.19.28.9
DF042
FEAT7.19.28.10
DF043
FEAT7.19.28.11
DF044
FEAT7.19.28.12
DF045
FEAT7.19.28.13
DF045S
FEAT7.20
FEAT7.21
FEAT7.21.1
MA001
FEAT7.21.2
MA002
FEAT7.21.2.1
MA002A
FEAT7.21.2.2
MA002B
ATIS Severity Suggestion Change
The software shall provide visual clues to the operator if the ATIS Severity level suggested is different than the last saved ATIS Severity level.
The software shall track changes to the ATIS ATIS Severity Event Chronology Severity via the Event Chronology every time a changed ATIS Severity level is saved.
The software shall make the ATIS Severity level ATIS Severity Sent to ATIS
available to external clients via Center‐to‐Center.
The software shall default the ATIS Severity level to Minor for all new events.
The software shall allow an administrator to set the Severity threshold percentage for both Minor ATIS Limits Configuration
and Intermediate severity levels in the SunGuide configuration file.
The software shall default the Severity threshold percentages if those in the configuration file were ATIS Limit Configuration Default
invalid. Default values are Minor = 0; Intermediate = 25;
PS
Operator Map
The Operator Map shall display map tiles created by the SunGuide Map Tile Generation application Tile‐based map
that represent the state of Florida.
ATIS Severity Default
The Operator Map shall provide multiple zoom Multiple zoom levels supported levels with the level of detail increasing as the zoom increases.
The operator map shall provide a rubber‐band Rubber‐band zoom
zoom capability.
The operator map shall have a control that allows Select zoom level displayed
zoom level to be selected.
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
4.3
GUI
GUI
3.1
5
GUI
5
GUI
5
GUI
5
GUI
5
73
FEAT7.21.2.3
MA002C
FEAT7.21.3
MA003
FEAT7.21.4
MA004
FEAT7.21.5
MA005
FEAT7.21.5.1
MA005A
FEAT7.21.5.2
MA005B
FEAT7.21.6
MA006
FEAT7.21.6.1
MA006A
FEAT7.21.6.1.1
MA006A1
The operator map shall provide the ability to zoon Ability to zoom by mouse scroll the map by use of the mouse scroll wheel
wheel
The Operator Map shall provide the ability to pan the map in multiple directions.
On logging in, the Operator Map shall display the default map view of the operator, if one was Display default view
defined.
The Operator Map shall display the TSS links Display TSS Links
managed in the SunGuide Link Editor.
Links displayed with lane level The TSS links shall be drawn with lane level detail.
detail
The TSS lanes shall be color coded to indicate Links color coded
their current status.
The Operator Map shall display icons for Icons displayed
SunGuide devices at the latitude and longitude recorded for the devices.
The Operator Map shall display CCTV icons with their current status color coded for the CCTV Display CCTV status icons
devices configured in the SunGuide Admin Editor.
Pan in multiple directions
Locked CCTV icons
FEAT7.21.6.1.2
MA006A2
VisioPaD CCTV icons
FEAT7.21.6.2
MA006B
Display DMS status icons
The Operator Map shall display an icon overlay on CCTV icons when they are locked by a user.
The Operator Map shall display an icon overlay on CCTV icons when they are being used for VisioPaD event detection.
The Operator Map shall display DMS icons with their current status color coded for the DMS devices configured in the SunGuide Admin Editor. (Note This includes general purpose DMS, VSL, trailblazers, lane status DMS, toll rate DMS, and toll gantry DMS.)
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
74
FEAT7.21.6.3
MA006C
Display HAR status icons
FEAT7.21.6.4
MA006D
Display Ramp Meter status icons
FEAT7.21.6.5
MA006E
Display RWIS status icons
FEAT7.21.6.6
MA006F
Display Safety Barrier status icons
FEAT7.21.6.7
MA006G
Display TSS status icons
FEAT7.21.6.8
MA006H
Display Event status icons
FEAT7.21.6.8.1
MA006H1
Display Event overlay icons
FEAT7.21.6.8.2
MA006H2
Do not show Closed Event Icon
FEAT7.21.6.9
MA006I
Display C2C status icons
The Operator Map shall display HAR icons with their current status color coded for the HAR devices configured in the SunGuide Admin Editor.
The Operator Map shall display Ramp Metering icons with their current status color coded for the Ramp Metering devices configured in the SunGuide Admin Editor.
The Operator Map shall display RWIS icons with their current status color coded for the RWIS devices configured in the SunGuide Admin Editor.
The Operator Map shall display Safety Barrier icons with their current status color coded for the Safety Barrier devices configured in the SunGuide Admin Editor.
The Operator Map shall display TSS detector icons with their current status color coded for the detectors configured in the SunGuide Admin Editor.
The Operator Map shall display Event icons based on Event Type for the Events currently maintained in the Event Management subsystem.
The Operator Map shall display an icon overlay on Event icons which are published via FL511 ATIS.
The Operator Map shall not show icons for events that have been closed.
The Operator Map shall display C2C devices with their current status color coded for the C2C devices currently being received from a Center‐to‐
Center Extractor.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
75
FEAT7.21.6.10
MA006J
Display AVL status icons
FEAT7.21.6.11
MA006K
Display SAS overlay icons
FEAT7.21.6.12
MA006L
Selection of icons
FEAT7.21.6.12.1
MA006L1
Display CCTV Status GUI
FEAT7.21.6.12.2
MA006L2
Display DMS Status GUI
FEAT7.21.6.12.3
MA006L3
Display Event Details Status GUI
FEAT7.21.6.12.4
MA006L4
Display HAR Status GUI
FEAT7.21.6.12.5
MA006L5
Display C2C Status GUI
FEAT7.21.6.12.6
MA006L6
Display AVL/RR Status GUI
FEAT7.21.6.12.7
MA006L7
Display RWIS Status GUI
FEAT7.21.6.12.8
MA006L8
Display Safety Barrier Status GUI
FEAT7.21.6.12.9
MA006L9
Display VSL Status GUI
FEAT7.21.6.12.10
MA006L10
Display TSS Detector Status GUI
FEAT7.21.6.12.11
MA006L11
Display Link Speed Status GUI
FEAT7.21.6.12.12
MA007C9B
Select icon types in map view
The Operator Map shall display AVL vehicle icons with their current status color coded for the vehicles currently active.
The Operator Map shall display an overlay icon on devices which have scheduled activities through the SAS.
The Operator Map shall allow device icons to be selected.
The CCTV status GUI shall be displayed when a CCTV device is selected.
The DMS status GUI shall be displayed when a DMS device is selected.
The Event Details GUI shall be displayed when an event icon is selected.
The HAR status GUI shall be displayed when a HAR device is selected.
The C2C status GUI shall be displayed when a C2C device is selected.
The AVL/RR status GUI shall be displayed when a RR device is selected.
The RWIS status GUI shall be displayed when a RWIS device is selected.
The Safety Barrier status GUI shall be displayed when a SB device is selected.
The VSL status GUI shall be displayed when a VSL device is selected.
The TSS detector status GUI shall be displayed when a detector is selected.
The Link Speed GUI shall be displayed when a TSS lane is selected.
An operator shall be able to select which icon typs are visible in their map view
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
76
FEAT7.21.6.12.12.1
MA007C9B1
FEAT7.21.6.12.14
MA007CF
FEAT7.21.6.12.15
MA007CG
FEAT7.21.6.12.16
MA007C9C
FEAT7.21.6.12.16.1
MA007C9C1
FEAT7.21.7
MA007
FEAT7.21.7.1
MA007A
FEAT7.21.7.2
MA007B
FEAT7.21.7.3
MA007C
FEAT7.21.7.3.1
MA007C1
Customize icon
Each operator shall be able to customize which icons appear for their login credentials
The display of the abandoned vehicles icon shall Display of abandoned vehicle be an option that can be toggled in the icon icon
configuration menu
The display of the disabled vehicles icons shall be Display of disabled vehicle icon an option that can be toggled in the icon configuration menu
An operator shall be able to customize the Customize appearance of icons
appearance of icons.
Each operator shall be able to customize icon Customize icon colors
colors for their login credentials.
The Operator Map shall have a menu that changes Map Menu
context based on where the mouse right clicks.
Menu options which are not available because the Limit menu options based on user is not authenticated to the corresponding authentication
subsystem shall either appear but be disabled, or not appear at all.
Menu options which are not available because the user does not have sufficient permissions to Limit menu options based on perform the action of that menu option shall permissions
either appear but be disabled, or not appear at all.
A menu to access subsystems shall be displayed when the mouse right clicks on the map where no ITS devices are displayed; the menu will vary Display menu with mouse click
based on what subsystems the operator has authenticated to for data.
Camera submenu
The Operator Map main menu shall provide a "Cameras" submenu.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
77
FEAT7.21.7.3.1.1
MA007C1A
FEAT7.21.7.3.1.2
MA007C1B
FEAT7.21.7.3.1.3
MA007C1C
FEAT7.21.7.3.1.3.1
MA007C1C1
FEAT7.21.7.3.1.3.2
MA007C1C2
FEAT7.21.7.3.1.3.3
MA007C1C3
FEAT7.21.7.3.1.4
MA007C1D
FEAT7.21.7.3.2
MA007C2
FEAT7.21.7.3.2.1
MA007C2A
FEAT7.21.7.3.2.2
MA007C2B
FEAT7.21.7.3.2.3
MA007C2C
FEAT7.21.7.3.2.4
MA007C2D
The Cameras submenu shall provide a "Camera Camera submenu blocking
Blocking..." option to launch the combined cameras tabular display.
The Cameras submenu shall provide a "Camera Camera submenu control
Control..." option to launch the CCTV control dialog.
The Cameras submenu shall provide a "Scheduler" Camera submenu scheduler
submenu.
The Scheduler submenu shall provide a Camera submenu SAS launch "Schedules..." option to launch the SAS schedules dialog.
The Scheduler submenu shall provide a Camera submenu SAS scheduler "Schedules..." option to launch the SAS schedules dialog.
The Scheduler submenu shall provide a Camera submenu SAS "Sequences..." option to launch the SAS sequences
sequences dialog.
The Cameras submenu shall provide a "USB Camera submenu USB joystick Joystick Configuration..." option to launch the joystick configuration dialog.
The Operator Map main menu shall provide a C2C submenu
"Center‐to‐Center" submenu.
The Operator Map main menu shall provide a C2C submenu camera
"Center‐to‐Center" submenu.`
The Center‐to‐Center submenu shall provide a C2C submenu DMS
"DMS Status..." option to launch the C2C DMS dialog.
The Center‐to‐Center submenu shall provide a C2C submenu Event
"Event List..." option to launch the C2C event dialog.
The Center‐to‐Center submenu shall provide a C2C submenu Floodgate
"Floodgate Messages..." option to launch the C2C floodgate tabular display.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
78
FEAT7.21.7.3.2.5
MA007C2E
C2C submenu HAR
FEAT7.21.7.3.2.6
MA007C2F
C2C submenu RWIS
FEAT7.21.7.3.2.7
MA007C2G
C2C submenu approve messages
FEAT7.21.7.3.2.7.1
MA007C2G1
C2C submenu approve messages control
FEAT7.21.7.3.3
MA007C3
DMS submenu
FEAT7.21.7.3.3.1
MA007C3A
DMS submenu sequences
FEAT7.21.7.3.3.2
MA007C3B
DMS submenu device groups
FEAT7.21.7.3.3.3
MA007C3C
FEAT7.21.7.3.3.4
MA007C3D
FEAT7.21.7.3.3.5
MA007C3E
The Center‐to‐Center submenu shall provide a "HAR Status..." option to launch the C2C HAR dialog.
The Center‐to‐Center submenu shall provide a "RWIS Status..." option to launch the C2C RWIS dialog.
The Center‐to‐Center submenu shall provide an "Operator Approval of Remote Messages" submenu with options labeled "On" and "Off" to allow an operator to toggle the appropriate C2C setting.
The "On" or "Off" setting of the Operator Approval option shall be flagged with a checkmark according to the current state of the system.
The Operator Map main menu shall provide a "DMS" submenu.
The DMS submenu shall provide an "Active Sequences..." option to launch the DMS active sequences dialog.
The DMS submenu shall provide a "Device Groups..." option to launch the DMS group dialog.
The DMS submenu shall provide a "Device Status..." option to launch the full DMS status DMS submenu status GUI
dialog.
The DMS submenu shall provide a "Message DMS submenu MAS queue Queue Manager..." option to launch the MAS queue manager dialog.
The DMS submenu shall provide a "Message DMS submenu messages library Libraries..." option to launch the DMS message libraries dialog.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
79
FEAT7.21.7.3.3.6
MA007C3F
DMS submenu sequence library
FEAT7.21.7.3.3.7
MA007C3G
DMS submenu toll lane status
FEAT7.21.7.3.3.8
MA007C3H
DMS submenu toll rate status
FEAT7.21.7.3.3.9
MA007C3I
DMS submenu trailblazer status
FEAT7.21.7.3.3.10
MA007C3J
DMS submenu TvT messages control
FEAT7.21.7.3.3.10.1
MA007C3J1
DMS submenu TvT messages control status
FEAT7.21.7.3.3.11
MA007C3K
DMS submenu VSL status
FEAT7.21.7.3.4
MA007C4
Event submenu
FEAT7.21.7.3.4.1
MA007C4A
Event submenu add event
FEAT7.21.7.3.4.2
MA007C4B
Event submenu list events
The DMS submenu shall provide a "Sequence Libraries..." option to launch the DMS sequence libraries dialog.
The DMS submenu shall provide a "Toll Lane Status DMS..." option to launch the DMS status dialog for toll lane status signs.
The DMS submenu shall provide a "Toll Rate Sign Status..." option to launch the DMS status dialog for toll rate signs.
The DMS submenu shall provide a "Trailblazer DMS Status..." option to launch the DMS status dialog for trailblazers.
The DMS submenu shall provide a "Travel Time Messages" submenu with options labeled "On" and "Off" to allow an operator to toggle the appropriate TvT setting.
The "On" or "Off" setting of the Travel Time Messages option shall be flagged with a checkmark according to the current state of systemwide TvT message generation.
The DMS submenu shall provide a "Variable Speed Limit DMS Status..." option to launch the DMS status dialog for VSLs.
The Operator Map main menu shall provide an "Event Management" submenu.
The Event Management submenu shall provide an "Add New Event..." option to launch the EM add new event interface.
The Event Management submenu shall provide an "Event List..." option to launch the EM event list tabular display.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
80
FEAT7.21.7.3.4.3
FEAT7.21.7.3.4.4
FEAT7.21.7.3.4.5
MA007C4C
MA007C4D
MA007C4E
FEAT7.21.7.3.4.6
MA007C4F
FEAT7.21.7.3.4.7
MA007C4G
FEAT7.21.7.3.5
MA007C5
FEAT7.21.7.3.5.1
MA007C5A
FEAT7.21.7.3.5.2
MA007C5B
Event submenu predefined plans
The Event Management submenu shall provide a "Predefined Response Plans..." option to launch the RPG (EM) predefined plan manager dialog.
Event submenu remove 511 event
The Event Management submenu shall provide a "Remove Events from 511..." option to launch the FL‐ATIS event removal dialog.
The Event Management submenu shall provide a Event submenu republish 511 "Republish Events to 511..." option to launch the event
FL‐ATIS event republish dialog.
The display of the disabled vehicles icon shall be an option that can be toggled in the icon configuration menu.
The display of the disabled vehicles icon shall be Event submenu disabled an option that can be toggled in the icon vehicles
configuration menu.
The Operator Map main menu shall provide an Launch express Lanes submenu
"Express Lanes" submenu
The Express Lanes submenu shall provide and Launch Express Lanes dialog "Express Lanes... " option to launch the Express Lanes dialog.
The Express Lanes submenu shall provide a "Startup Status ..." option to launch the Express Launch Express Lane Startup Lanes Startup Status dialog if the Pricing Status Dialog
Subsystem is awaiting startup state approval.
Event submenu abandoned vehicles
FEAT7.21.7.3.5.3
MA007C5C
Launch Offline Toll Rates Synchronization dialog
FEAT7.21.7.3.6
MA007C6
HAR submenu
The Express Lanes submenu shall provide an "Offline Synchronization..." option to launch the Offline Toll Rate Synchronization dialog.
The Operator Map main menu shall provide a "HAR" submenu.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
81
FEAT7.21.7.3.6.1
MA007C6A
FEAT7.21.7.3.6.2
MA007C6B
FEAT7.21.7.3.7
MA007C7
FEAT7.21.7.3.7.1
MA007C7A
FEAT7.21.7.3.7.1.1
MA007C7A1
HAR submenu status
The HAR submenu shall provide a "HAR Status..." option to launch the HAR device status dialog.
The HAR submenu shall provide a "Message Queue Manager..." option to launch the MAS queue manager dialog.
The Operator Map main menu shall provide an Incident detection submenu
"Incident Detection" submenu.
The Incident Detection submenu shall provide a "Systemwide VisioPaD Detection" submenu with Incident detection submenu options labeled "On" and "Off" to allow an VisioPaD
operator to toggle the appropriate IDS setting.
HAR submenu MAS
The "On" or "Off" setting of the Systemwide VisioPaD Detection option shall be flagged with a Incident detection submenu checkmark according to the current state of VisioPaD status
systemwide IDS VisioPaD detection.
The Incident Detection submenu shall provide a Incident detection submenu "VisioPaD Camera Detection Status..." option to VisioPaD control
launch the combined cameras tabular display.
FEAT7.21.7.3.7.2
MA007C7B
FEAT7.21.7.3.8
MA007C8
IMS submenu
FEAT7.21.7.3.8.1
MA007C8A
IMS submenu Inventory GUI
FEAT7.21.7.3.8.2
MA007C8B
IMS submenu vendor GUI
FEAT7.21.7.3.9
MA007C9
Preferences submenu
The Operator Map main menu shall provide an "Inventory and Maintenance" submenu.
The Inventory and Maintenance submenu shall provide an "Inventory" option to launch the IMS inventory management dialog.
The Inventory and Maintenance submenu shall provide a "Vendor" option to launch the IMS vendor management dialog.
The Operator Map main menu shall provide a "Preferences" submenu.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
82
FEAT7.21.7.3.9.1
MA007C9A
Preferences submenu clear saved window
FEAT7.21.7.3.9.4
MA007C9D
Preferences submenu save current view
FEAT7.21.7.3.9.5
MA007C9E
Preferences submenu save current windows
FEAT7.21.7.3.9.6
MA007C9F
Preferences submenu subsystem selection
FEAT7.21.7.3.10
MA007C10
FEAT7.21.7.3.10.1
MA007C10A
FEAT7.21.7.3.10.2
MA007C10B
FEAT7.21.7.3.10.3
MA007C10C
FEAT7.21.7.3.10.4
MA007C10D
The Preferences submenu shall provide a "Clear Saved Window Positions" option to clear the user's saved window position information.
The Preferences submenu shall provide a "Save Current Map View" option to store the current map pan and zoom settings as the user's default view for future sessions.
The Preferences submenu shall provide a "Save Current Window Positions" option to store the current window location/size information as the user's default location/size for those windows which may have that information stored.
The Preferences submenu shall provide a "Subsystems..." option to launch the operator map subsystem status/selection dialog.
The Operator Map main menu shall provide a "Ramp Metering" submenu.
The Ramp Metering submenu shall provide an Ramp metering submenu "Alarms..." option to launch the RM RMC alarms alarms
dialog.
The Ramp Metering submenu shall provide a Ramp metering submenu "Control..." option to launch the RM RMC control control
dialog.
The Ramp Metering submenu shall provide a Ramp metering submenu reset "Reset Ramp Meters..." option to launch the RM RMC reset dialog.
The Ramp Metering submenu shall provide a Ramp metering submenu status "Status Overview..." option to launch the RM RMC status dialog.
Ramp metering submenu
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
83
FEAT7.21.7.3.11
MA007C11
FEAT7.21.7.3.12
MA007C12
FEAT7.21.7.3.12.1
MA007C12A
FEAT7.21.7.3.12.2
MA007C12B
FEAT7.21.7.3.13
MA007C13
FEAT7.21.7.3.14
MA007C14
FEAT7.21.7.3.15
MA007C15
FEAT7.21.7.3.15.1
MA007C15A
FEAT7.21.7.3.15.1.1
MA007C15A1
FEAT7.21.7.3.15.2
MA007C15B
FEAT7.21.7.3.15.3
MA007C15C
FEAT7.21.7.3.15.3.1
MA007C15C1
The Operator Map main menu shall provide a Launch reports display
"Reports..." option to launch the Reports tabular display.
The Operator Map main menu shall provide a Responders submenu
"Responders" submenu.
The Responders submenu shall provide a Responders submenu status "Responder Status..." option to launch the AVL/RR vehicle status tabular display.
The Responders submenu shall provide a "Vehicle Responders submenu vehicle Location Replay..." option to launch the AVL/RR location replay
historical track dialog.
The Operator Map main menu shall provide a Launch RWIS status
"Roadside Weather Systems..." option to launch the RWIS station status dialog.
The Operator Map main menu shall provide a Launch Safety Barrier status "Safety Barriers..." option to launch the SB station status dialog.
The Operator Map main menu shall provide a System submenu
"System" submenu.
System submenu logout The System submenu shall provide a "Logout" submenu
submenu.
The Logout submenu shall provide a "Logout" option to terminate the current user's operator System submenu logout submenu logout option
map session and return to the initial log in prompt.
The System submenu shall provide a "Change System submenu change Password..." option to launch the operator map password
password dialog.
The System submenu shall provide a "Log Level" System submenu log level
submenu.
The Log Level submenu shall provide "Info", System submenu log level "Debug", and "Detail" options to control the log selection
level used by the operator map.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
84
The appropriate submenu item shall be flagged with a checkmark based on the current log level of the operator map.
The System submenu shall provide a "Map Views..." option to launch the operator map System submenu map views
systemwide predefined map view definition dialog.
The System submenu shall provide a "System System submenu system alerts Alerts..." option to launch the operator map system alerts dialog.
The System submenu shall provide a "System System submenu system Messages..." option to launch the operator map messages
system messages dialog.
The System submenu shall provide a "System System submenu system Settings..." option to launch the operator map settings
general UI system settings dialog.
System submenu log level status
FEAT7.21.7.3.15.3.2
MA007C15C2
FEAT7.21.7.3.15.4
MA007C15D
FEAT7.21.7.3.15.5
MA007C15E
FEAT7.21.7.3.15.6
MA007C15F
FEAT7.21.7.3.15.7
MA007C15G
FEAT7.21.7.3.16
MA007C16
Traffic detection submenu
FEAT7.21.7.3.16.1
MA007C16A
Traffic detection submenu detector status
FEAT7.21.7.3.16.2
MA007C16B
Traffic detection submenu dynamic probe
FEAT7.21.7.3.16.2.1
MA007C16B1
Traffic detection submenu dynamic probe linking
FEAT7.21.7.3.17
MA007C17
Launch travel times GUI
The Operator Map main menu shall provide a "Traffic Detection" submenu.
The Traffic Detection submenu shall provide a "Detector Status..." option to launch the TSS detector status dialog.
The Traffic Detection submenu shall provide a "Dynamic Probe Linking" submenu with options labeled "On" and "Off" to allow an operator to toggle the appropriate TSS setting.
The "On" or "Off" setting of the Dynamic Probe Linking option shall be flagged with a checkmark according to the current state of systemwide TSS dynamic linking.
The Operator Map main menu shall provide a "Travel Times..." menu option to launch the Travel Times tabular display.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
85
FEAT7.21.7.3.18
MA007C18
FEAT7.21.7.3.18.1
MA007C18A
FEAT7.21.7.3.18.2
MA007C18B
FEAT7.21.7.3.18.3
MA007C18C
FEAT7.21.7.3.18.4
MA007C18D
FEAT7.21.7.3.19
MA007C19
FEAT7.21.7.7
MA007D
FEAT7.21.7.7.1
MA007D1
FEAT7.21.7.8
MA007E
The Operator Map main menu shall provide a "Video Switching" submenu.
The Video Switching submenu shall provide a Video switching submenu "Switching Control..." option to launch the VS control
switching control dialog.
The Video Switching submenu shall provide a Video switching submenu tours "Video Tours..." option to launch the VS video tours dialog.
The Video Switching submenu shall provide a Video switching submenu video "Video Wall Control..." option to launch the VWS wall
video wall dialog.
The Video Switching submenu shall provide a Video switching submenu "Virtual Wall Layout..." option to launch the VS virtual video wall layout
virtual wall dialog.
The Operator Map main menu shall provide a VSL submenu
"VSL Segment Status..." option to launch the VSL segment status tabular display.
The Operator Map shall display an AVL/RR context AVL/RR context menu
menu when the mouse right clicks over an AVL/RR vehicle.
The AVL/RR context menu shall allow an operator with sufficient permissions to add an event at the AVL/RR context menu add vehicle location, view details of the vehicle, or event
view replay data for the vehicle.
Video switching submenu
CCTV context menu
The Operator Map shall display a camera context menu when the mouse right clicks over a camera.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
86
FEAT7.21.7.8.1
MA007E1
FEAT7.21.7.9
MA007F
FEAT7.21.7.9.1
MA007F1
FEAT7.21.7.10
MA007G
FEAT7.21.7.10.1
MA007G1
FEAT7.21.7.11
FEAT7.21.7.11.1
MA007H
MA007H1
The camera context menu shall allow an operator with sufficient permissions to switch the camera video to a shared video destination, local video destination, or video wall destination; toggle the CCTV context menu share video
use of the camera in VisioPaD detection; launch a GUI to control the camera or switch its video; or handle a potential detected alarm.
The Operator Map shall display a C2C context C2C context menu
menu when the mouse right clicks over a C2C device.
The C2C context menu shall allow an operator C2C context menu send with sufficient permissions to view the status of command
the device or send a command to the device (if applicable).
The Operator Map shall display a DMS context menu when the mouse right clicks over a DMS, DMS context menu
trailblazer, lane status sign, toll rate sign, toll gantry sign, or VSL.
The DMS context menu shall allow an operator with sufficient permissions to toggle travel time message generation for the device or launch GUIs DMS context menu toggle TvT to view the device status, message queue, or messages
"short" status, or to send a message to the device (if applicable).
Event context menu
The Operator Map shall display an Event context menu when the mouse right clicks over an Event.
Event context menu event details
The Event context menu shall allow an operator with sufficient permissions to launch GUIs to view event details or response plan.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
87
FEAT7.21.7.12
FEAT7.21.7.12.1
MA007I
MA007I1
HAR context menu
HAR context menu status
FEAT7.21.7.13
MA007J
IMS context menu
FEAT7.21.7.13.1
MA007J1
IMS context menu status
FEAT7.21.7.14
MA007K
Ramp Meter context menu
FEAT7.21.7.14.1
MA007K1
Ramp Meter context menu status
FEAT7.21.7.15
MA007L
RWIS context menu
FEAT7.21.7.15.1
MA007L1
RWIS context menu status
The Operator Map shall display a HAR context menu when the mouse right clicks over a HAR.
The HAR context menu shall allow an operator with sufficient permissions to launch GUIs to view the HAR device status or message queue, or to send a message to the HAR.
The Operator Map shall also display an IMS context menu when the mouse right clicks over a device which is configured as part of the IMS system.
The additional IMS context menu shall allow an operator with sufficient permissions to launch GUIs to view details about the device in inventory or its maintenance history.
The Operator Map shall display a Ramp Meter context menu when the mouse right clicks over a Ramp Meter device.
The RM context menu shall allow an operator with sufficient permissions to launch GUIs to display Alarms, configure Time of Day settings, control the RMC, configure firmware parameters, and reset the RMC.
The Operator Map shall display an RWIS context menu when the mouse right clicks over an RWIS device.
The RWIS context menu shall allow an operator with sufficient permissions to launch a GUI to view the status of the detector.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
88
FEAT7.21.7.16
MA007M
FEAT7.21.7.16.1
MA007M1
FEAT7.21.7.17
MA007N
The Operator Map shall display a Safety Barrier Safety Barrier context menu context menu when the mouse right clicks over a Safety Barrier device.
The SB context menu shall allow an operator with Safety Barrier context menu sufficient permissions to launch a GUI to view the status
status of the barrier.
TSS Link context menu
The Operator Map shall display TSS link context menu when the mouse right clicks over a TSS link.
The TSS link context menu shall allow an operator with sufficient permissions to launch GUIs to view the status of the link's detector, view the speed TSS Link context menu control data of the link, and create an event from or dismiss an alarm if any lanes of the link currently have IDS alarms.
FEAT7.21.7.17.1
MA007N1
FEAT7.21.7.18
MA007O
TSS Detector context menu
FEAT7.21.7.18.1
MA007O1
TSS Detector context menu status
FEAT7.21.8
MA008
Map hover status
FEAT7.21.8.1
MA008A
Map hover status AVL/RR
The Operator Map shall display TSS detector context menu when the mouse right clicks over a TSS detector.
The TSS detector context menu shall allow an operator with sufficient permissions launch a GUI to view the detector's status.
The Operator Map shall display a concise summary of object information when an object is hovered over with the mouse.
When an AVL/RR vehicle is hovered over, the Operator Map shall display the vehicle's beat, driver, radio, phone, heading, speed, location, destination (with distance from), and current service status. (See AVL/RR requirements)
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
89
FEAT7.21.8.2
MA008B
FEAT7.21.8.3
MA008C
FEAT7.21.8.4
MA008D
FEAT7.21.8.5
MA008E
FEAT7.21.8.6
MA008F
FEAT7.21.8.7
MA008G
FEAT7.21.8.8
MA008H
When a C2C device is hovered over, the Operator Map hover status C2C
Map shall display the device's ID, center, and operational status.
When a camera is hovered over, the Operator Map hover status CCTV
Map shall display the camera's ID, status, and lock holder if locked.
When a DMS is hovered over, the Operator Map Map hover status DMS
shall display the DMS's ID and status.
When an event is hovered over, the Operator Map hover status event
Map shall display the event's ID, type, status, and location.
When a HAR is hovered over, the Operator Map Map hover status HAR
shall display the HAR's ID and status.
When a ramp meter is hovered over, the Map hover status Ramp Meter Operator Map shall display the ramp meter's ID and status.
When an RWIS is hovered over, the Operator Map Map hover status RWIS
shall display the RWIS's ID and status.
FEAT7.21.8.9
MA008I
Map hover status Safety Barrier
FEAT7.21.8.10
MA008J
Map hover status TSS
FEAT7.21.8.11
MA008K
Map hover status TSS link
FEAT7.21.9
MA009
Display components of response plan
When an SB is hovered over, the Operator Map shall display the SB's ID and status.
When a TSS detector is hovered over, the Operator Map shall display the detector's ID and status.
When a TSS link is hovered over, the Operator Map shall display the link's ID and the smoothed speed, occupancy, and volume of each of its lanes.
The operator map shall support visually displaying devices included in an Event Management Response Plan.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
90
FEAT7.21.10
FEAT7.21.11
FEAT7.21.12
MA010
MA011
MA012
FEAT7.21.13
MA013
FEAT7.21.14
MA015
FEAT7.21.14.1
MA015A
FEAT7.21.14.2
MA015B
FEAT7.21.15
MA014
Highlight potential incidents
Support map views
Review AVL/RR track history
The Operator Map shall support highlighting potential detected incidents by using flashing icons or flashing icon backgrounds or flashing links
The Operator Map shall allow an operator to switch to systemwide map views previously stored by an operator with sufficient permissions.
The Operator Map shall allow an operator with sufficient permissions to review AVL/RR vehicle historical track data via a breadcrumb display which hides all other devices while it is in use.
The Operator Map shall allow a user to select Select base map tile sets
from a configurable list of pre‐generated map tile sets.
The Operator Map shall display shields on the Display shields on map
map.
The Operator Map shall display shields at the Display shields on map at latitude and longitude specified when the shield is lat/long
created.
Shields shall only be displayed on the Operator Display shields on map based on Map at a minimum zoom level configurable by the zoom level
operator and higher zoom levels.
Map performance
The performance of the Operator Map shall be measured with workstations and servers meeting the minimum requirements specified in the SunGuide Computer Sizing Estimates document, version SunGuide‐CSE‐3.0.0 and all computers operating with less than a 25% CPU load and connected on a 100MB network.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
91
FEAT7.21.15.1
MA014A
FEAT7.21.15.2
MA014B
FEAT7.21.15.3
MA014C
FEAT7.21.15.4
MA014D
FEAT7.21.15.5
MA014E
FEAT7.21.15.6
MA014F
FEAT7.21.15.7
FEAT7.21.22
MA014G
The Operator Map shall load up to the login prompt in less than 20 seconds after either the Map performance login
map application is updated, IE's cache is cleared or if the workstation has never access the map previously.
The Operator Map shall load up to the login Map performance view change prompt in less than 10 seconds once the map has been previously accessed.
The Operator Map shall be available for operator Map performance available for input within 10 seconds of the operator providing input
valid user credentials.
The Operator Map with no ITS equipment Map performance pan
displayed shall allow for pan operations to be completed in less than one second.
The Operator Map with no ITS equipment Map performance zoom
displayed shall allow for zoom operations to be completed in less than two seconds.
The Operator Map with up to 500 pieces of ITS equipment and shields in the current field of view Map performance pan for 500 displayed shall allow for pan operations to be pieces of equipment
completed in less than two seconds.
The Operator Map with up to 500 pieces of ITS equipment and shields in the current field of view Map performance zoom for 500 displayed shall allow for zoom operations to be pieces of equipment
completed in less than three seconds.
The UI shall have a configurable value indicating whether the display of a new system message System Message Window Focus should cause the System Messages dialog to be brought to the front of the user's window stack
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
92
FEAT7.22
MA020
FEAT7.22.1
MA021
FEAT7.22.2
MA022
FEAT7.22.2.1
MA022A
FEAT7.22.2.2
MA022B
FEAT7.22.2.3
MA022C
FEAT7.23
MA030
FEAT7.23.1
MA030A
FEAT7.23.2
MA031
FEAT7.23.3
MA032A
FEAT7.23.4
MA031A
FEAT7.24
MA040
The Map Tile Generation tool shall use ESRI Shape Map tile generation
File formats for the map data used to render the tiles.
The Map Tile Generation tool shall produce Map tile generation images
graphical images of the Shape File data.
The Map Tile Generation tool shall create map Map tile generation map tiles tiles for display in the SunGuide Operator Map.
The map tiles shall be generated with multiple Map tile generation zoom layers resolutions to support additional detail as the map zoom is increased.
The Map Tile Generation tool shall allow road Map tile generation road colors
colors to be specified.
The Map Tile Generation shall allow the SunGuide Map tile generation feature Administrator to determine which features in the selection
Shape Files to include in the map tiles.
The Link Editor map displayed shall be the same map as the Operator Map.
The Link Editor shall be managed as a semi‐
Link Editor mode of operation
independent mode of the Operator Map.
The Link Editor shall allow an operator with Link Editor TSS link appropriate permissions to manage the display of management
TSS links.
The Link Editor shall allow links not based on TSS Link Editor TSS link links to be drawn on the map using a visual management link creation
drawing tool.
The Link Editor shall allow existing TSS links to be Link Editor TSS link drawn on the map using a visual drawing tool
management link display
Link Editor
Device Sequence Editor
The Device Sequencing Editor map displayed shall be the same map as the Operator Map.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
93
FEAT7.24.1
MA040A
FEAT7.24.2
MA041
FEAT7.24.3
MA042
FEAT7.24.4
MA043
FEAT7.24.5
MA044
FEAT7.24.6
MA045
FEAT7.24.7
MA045A
FEAT7.24.8
MA045B
The Device Sequencing Editor shall be managed as Device Sequence Editor mode a semi‐independent mode of the Operator Map.
of operation The Device Sequencing Editor shall display DMS Device Sequence Editor display devices configured in the system and received via DMS
Center‐to‐Center.
The Device Sequencing Editor shall allow an operator with appropriate permissions to add Device Sequence Editor add traversal nodes to more closely match the device nodes
sequence to the layout of the roadway.
The Device Sequencing Editor shall allow an Device Sequence Editor modify operator with appropriate permissions to move nodes
traversal nodes.
The Device Sequencing Editor shall allow an Device Sequence Editor delete operator with appropriate permissions to delete nodes
traversal nodes.
The Device Sequencing Editor shall allow an operator with appropriate permissions to visually Device Sequence Editor associate DMS devices and traversal nodes to associate nodes
establish a relationship that can be used when Response Plans are generated.
The DSE shall allow an operator with appropriate permissions to select a node or device and then Device Sequence Editor indicate which other nodes or devices are associate nodes select
upstream of the initial node or device.
Device Sequence Editor associate nodes display upstream
The DSE shall allow an operator with appropriate permissions to select a node or device and view its complete upstream device tree.
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
GUI
5
94
FEAT7.24.9
MA045C
Device Sequence Editor associate nodes excluded devices
FEAT7.25
MA050
Geofence Editor
FEAT7.25.1
MA050A
Geofence Editor operation
FEAT7.25.2
MA051
Geofence Editor manage geofences
FEAT7.25.3
MA051A
FEAT7.25.4
MA051B
FEAT7.25.5
MA051C
FEAT7.26
MA060
Shield Editor
FEAT7.26.1
MA060A
Shield Editor operation
FEAT7.26.2
MA061
FEAT7.26.3
MA061A
FEAT7.26.4
MA061B
FEAT7.26.5
MA061C
Geofence Editor manage geofences create
Geofence Editor manage geofences modify
Geofence Editor manage geofences delete
Shield Editor manage shields
Shield Editor manage shields create
Shield Editor manage shields modify
Shield Editor manage shields delete
The DSE shall allow an operator with appropriate permissions to view all upstream device associations at once, allowing the operator to detect any excluded devices.
GUI
5
The Geofence Editor map displayed shall be the same map as the Operator Map.
The Geofence Editor shall be managed as a semi‐
independent mode of the Operator Map.
GUI
5
GUI
5
The Geofence Editor shall allow an operator with appropriate permissions to manage geofences.
GUI
5
GUI
5
GUI
5
GUI
5
The Geofence Editor shall allow geofences to be created using a visual drawing tool
The Geofence Editor shall allow geofences to be modified.
The Geofence Editor shall allow geofences to be deleted.
The Shield Editor map displayed shall be the same map as the Operator Map.
The Shield Editor shall be managed as a semi‐
independent mode of the Operator Map.
GUI
5
GUI
5
The Shield Editor shall allow an operator with appropriate permissions to manage shields.
GUI
5
GUI
5
GUI
5
GUI
5
The Shield Editor shall allow shields to be created using a predefined set of shields.
The Shield Editor shall allow shields to be modified.
The Shield Editor shall allow shields to be deleted.
95
FEAT7.26.6
MA062
Shields place on map
FEAT7.26.6.1
MA062A
Drag and Drop shields
FEAT7.26.6.2
MA062B
FEAT7.26.6.3
MA062B1
FEAT7.27
VOD001
FEAT7.27.1
VOD002
FEAT7.27.2
VOD003
FEAT7.27.3
VOD004
FEAT7.27.4
VOD005
The Shield Editor shall allow shields to be placed on the Operator Map.
The Shield Editor shall allows shields to be dropped and dragged on to the Operator Map.
The Shield Editor shall provide a dialog that Display lat/long of shield.
displays the Latitude/Longitude of a selected shield.
The Shield Editor Latitude/Longitude dialog shall Enter lat/long of shield.
allow the operator to enter the Latitude/Longitude for a selected shield
The software shall provide Video on Desktop Video on Desktop capabilities
The operator shall be able to launch the Window from the context menu of the operator map, Launch Window from context closed‐circuit television (CCTV) camera device menus
icons, and the menu of another Window already open
The software shall provide drag and drop Drag and drop video sources operation of CCTV icons onto the Video on Desktop
When video is launched via context menu, the Launch to Viewer to last open user shall choose the Window in which the video Window should be displayed and the new Viewer shall be placed in the last position
When a Viewer is added to, removed from, or Auto‐arrange Viewers
moved within the Window, the Window will automatically arrange Viewers
GUI
5
GUI
5
GUI
5
GUI
5
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
96
FEAT7.27.5
VOD006
When a Viewer placement modification is made, the Window shall automatically rearrange Viewers by moving them on the right side of the placement modifications, filling positions in order Auto‐arrange Viewers in order
towards the right and continuing towards the lower rows of the modification in the same order as they were prior to the placement modification
FEAT7.27.6
VOD006
Auto‐arrange Viewers to maximize size
FEAT7.27.7
VOD007
Drag and drop tour creation
FEAT7.27.8
VOD008
Drag and drop indicator
FEAT7.27.9
FEAT7.27.10
VOD009
VOD010
The auto‐arrange behavior will resize and position the fewest number of Viewers on the same row and column as possible to maximize the area of each viewer
When a source is dragged and dropped on top of an existing Viewer within a Window, the source will combine with the source(s) already in the Viewer as an ad‐hoc tour where each source dwells for a default time of 5 seconds before switching. The user may change the dwell time as desired.
When a source is being dragged over the center area of a Window, the Window will visually indicate if the source would be placed inside another Viewer to create a tour or if the source would be added as a new Viewer
The center area of a Viewer used for a drag and drop location for combining sources in a tour will Viewer center area for drag and not consume the entire Viewer allowing room to drop
drag and drop Viewers between or on the outside of existing Viewer's' center areas
Move Viewers The Window will allow users to drag and drop Viewers into different positions and into different Windows
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
97
FEAT7.27.11
VOD011
Maintain Viewer aspect ratio
FEAT7.27.12
VOD012
Viewer source label
FEAT7.27.13
VOD013
Viewer sources in tour list
FEAT7.27.14
VOD014
FEAT7.27.15
VOD015
FEAT7.27.16
VOD016
FEAT7.27.17
FEAT7.27.18
FEAT7.27.19
VOD017
VOD018
VOD019
The Viewer will maintain the aspect ratio of the video source
The top portion within the Viewer will contain a one‐line label indicating the video source name or tour name
The Viewer shall provide a means for a Video on Desktop Viewer Tour List to appear listing the video sources that are in the tour
The list items in the Video on Desktop Viewer Reorder and remove sources Tour List will allow the user to reorder and from tour
remove items in the tour list
The Viewer tour list's name, viewer sources, and dwell time will be changeable from the Viewer Edit tour
tour list
The Video on Desktop Window Viewer Tour list shall contain save and cancel buttons that will either update or not update the name, the video Save and cancel tour sources, and the dwell times in the tour, modifications
respectively, and will both close the list
Store tours in database
Store Window layouts in SunGuide database
Window layout data
The Video on Desktop Window Viewer Tours, including their name, sources, and dwell times, shall be saved as a user‐specific preference when either the viewer tour list is saved or the Window configuration is saved
The Window shall allow the user to save the Window preset information in the SunGuide database as a user‐specific preference
The Window layout data shall include the Viewers and their positions, their video sources, and their saved or unsaved tours
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
98
FEAT7.27.20
VOD020
FEAT7.27.21
VOD021
FEAT7.27.22
VOD022
FEAT7.27.23
VOD023
FEAT7.27.24
VOD024
FEAT7.27.25
VOD025
FEAT7.27.26
VOD026
FEAT7.27.27
VOD027
Recall Window layout information
The Window shall allow the user to recall the Window preset information from the menu
The Operator Map context menu shall allow the user to launch a Window with any of the Launch layout Window from configured Window presets in addition to a no‐
Operator Map
preset option that launches an empty Window
Resize Window The Window shall be resizable by the user
The Window shall enter a full screen mode when Maximize Window as full screen maximized
The Window shall exit full‐screen mode when the Exit full‐screen mode of user presses the escape key or the restore Window
window size control
The Viewer shall have translucent command controls and translucent pan‐tilt‐zoom (PTZ) Translucent controls in Viewer controls that can be animated to fade in to be revealed and fade out to be hidden
Hide Viewer PTZ controls
Reveal Viewer PTZ controls
FEAT7.27.28
VOD028
Nudge controls
FEAT7.27.29
VOD029
PTZ visual indicator
The Viewer shall hide PTZ controls when the mouse pointer is not positioned over the Viewer.
The Viewer shall reveal PTZ controls when the mouse ponter is positioned over the Viewer and the user has a lock on the camera.
The Viewer PTZ controls shall include nudge buttons that command the camera to nudge in the selected direction
The Viewer shall reveal a PTZ control that is a visual indicator that the Viewer is in PTZ mode and shall hide the visual indicator when, and only when, the Viewer is no longer in PTZ mode
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
99
FEAT7.27.30
VOD030
FEAT7.27.31
VOD031
FEAT7.27.32
VOD032
FEAT7.27.33
VOD033
FEAT7.27.34
VOD034
FEAT7.27.35
VOD035
FEAT7.27.36
VOD036
FEAT7.27.37
VOD037
FEAT7.27.38
VOD038
Panning shall be engaged when the Viewer is in Engage panning in PTZ mode PTZ mode and the user drags the PTZ control in and left mouse down
the desired direction.
The Viewer PTZ controls shall allow the camera to be panned in a range of speeds, depending on how close to the center or the edge of the Viewer Pan using range of speeds
the mouse pointer is positioned
The Viewer's PTZ controls shall include zoom controls.
The Viewer's PTZ controls shall include preset PTZ controls contain camera buttons that command the camera to move to a preset buttons
stored preset
The Viewer's PTZ controls shall include a save to preset control that, when clicked, allows the user PTZ controls allows save presets
to save to existing or new camera presets
Viewer zoom controls
Launch CCTV details The Viewer's command controls shall include a method of launching the CCTV detail status dialog
The Viewer shall prompt the user with a warning and request for confirmation when attempting to Video on Desktop performance launch additional viewers and the workstation warning
resource utilization is high
All user interface responses of adding video Performance of non‐local user streams shall occur within 1 second of the interface response
completion of the user's command
While the software is processing a user command, it shall not prevent the user from further Non‐blocking user interface
interactions with the software while a previous command is being processed.
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
GUI
6
100
FEAT7.27.39
VOD039
All local user interface responses that do not Performance of user interface require adding video streams shall occur within response
100 milliseconds of the completion of the user's command.
FEAT8
Closed Circuit Television (CCTV)
FEAT8.1
General
FEAT8.1.1
A002
Video surveillance FEAT8.1.2
S015
Interface with CCTV cameras
FEAT8.1.4
TV003S
Lock CCTV FEAT8.1.5
PA001U
Camera menu FEAT8.1.6
TV003
Interface to portable CCTV
A008
Real‐time video display and control
FEAT8.1.7
The SunGuide software shall provide software for video surveillance along the limited‐access facilities and the interchange areas (along the mainline and crossroads).
The SunGuide software shall interface with CCTV used for traffic surveillance.
The CCTV function shall incorporate software logic to allow only one workstation at a time to control a particular CCTV unit.
A selectable menu of cameras shall be provided to the user.
The SunGuide system shall provide an interface to portable CCTVs that support work zone management through drivers with the following protocols:∙ NTCIP, Florida MIB
The SunGuide software shall provide software for real‐time video display and real‐time video control.
GUI
6
CCTV
1
CCTV
1
CCTV
1
CCTV
1
CCTV
1
CCTV
1
CCTV
1
CCTV
1
101
FEAT8.1.8
TV006S
Video switch device drivers
FEAT8.1.9
TV003S1
Automatic locking
FEAT8.1.10
TV001D3
Supported keyboard
FEAT8.1.11
TV001D4
Keyboard control functions
FEAT8.1.12
TV003S2
Automatic locking 2
FEAT8.1.13
TV003S3
FEAT8.2
FEAT8.2.1
Lock timeout
At a minimum, the CCTV video switch function shall provide device drivers for the following switch types:
‐ IP video devices, including:
‐ iMPath
‐ VBrick
‐ Teleste
‐ Cortec
A "lock" shall be acquired when a camera is selected if no other user holds a "lock".
SunGuide shall interface with an AMERICAN DYNAMICS M300 external CCTV keyboard/joystick device connected to serial port on a TCP/IP accessible terminal server.
The external Joystick shall control:
‐ CCTV Pan Tilt and Zoom
‐ Video switching
‐ Video wall control
‐ Create and edit camera presets.
Operator activation of any camera motion control shall automatically request a lock on the camera.
The automatically‐requested camera lock shall automatically time out after a configurable amount of time.
Camera types
TV001D
Pan/Tilt/Zoom (PTZ) systems
The device drivers shall be capable of controlling pan/tilt/zoom camera systems manufactured by a number of different manufacturers.
CCTV
1
CCTV
1
CCTV
1
CCTV
1
CCTV
1
CCTV
1
CCTV
1
CCTV
1
102
FEAT8.2.2
TV002D
Camera system types
FEAT8.2.3
TV017D
IP based controls
FEAT8.2.4
TV002
Technologies supported
FEAT8.2.5
TV001
FEAT8.2.6
TV003D
FEAT8.2.8
TV005D
FEAT8.2.9
TV001D5
Device driver types
The CCTV function shall be capable of controlling cameras (e.g., pan/tilt/zoom). The following protocols will be used to issue command/control requests to the cameras.∙ NTCIP∙ SunGuide
The CCTV driver shall also support cameras with IP based controls.
The CCTV function shall provide an interface that supports the following technologies for the transmission of video and data between field hardware, subsystems, TMCs and additional remote locations∙ Fiber optic transceivers;∙ Fiber optic video/data multiplexers;∙ MPEG encoders/decoders; and∙ Wireless.
At a minimum the CCTV function shall provide device drivers for the following camera types:∙ NTCIP compliant cameras∙ Sunguide protocol
Whenever possible, the NTCIP protocol standard shall be utilized for camera control and communication.
Manufacturer‐specific drivers shall, at a minimum, provide functionality equal to that provided via Functionality equal to NTCIP NTCIP mandatory objects provided the manufacturer's protocol supports the functionality.
The SunGuide software shall provide the capability to control (e.g. pan, tilt, zoom, focus, Support for American Dynamics iris) the American Dynamics Model #RAS917‐OPC camera driver
(Speed Dome ultra 7 ver 11), i.e. an American Dynamics Camera Driver.
NTCIP standard
CCTV
1
CCTV
1
CCTV
1
CCTV
1
CCTV
1
CCTV
1
CCTV
3
103
FEAT8.2.10
TV001D6
FEAT8.3
FEAT8.3.1
FEAT8.3.2
FEAT8.3.3
TV007D
TV008D
TV009D
The American Dynamics camera driver for the Responses not required for AD Speed Dome ultra 7 ver 11 shall not require driver
responses from the camera.
Functionality will be provided if the protocol Functionality
supports the particular function.
The CCTV range objects shall be implemented in the device drivers and at a minimum shall include:∙ A maximum number of presets parameters;∙ Pan left limit parameters;∙ Pan right limit parameters;∙ Pan home position parameters;∙ True north offset parameters;∙ Tilt Range objects up limit parameters;∙ Tilt down limit parameters;∙ Zoom limit parameters;∙ Focus limit parameters;∙ Iris limit parameters;∙ Maximum pan step angle parameters; and∙ Maximum tilt step angle parameters.
Timeout objects Preset objects
The device drivers shall contain the CCTV timeout objects and shall include the following parameters at a minimum∙ Pan timeout parameter;∙ Tilt timeout parameter;∙ Zoom timeout parameter; ∙ Focus timeout parameter; and∙ Iris timeout parameter.
The device driver shall contain CCTV preset objects and shall include the following parameters at a minimum:∙ Go to preset position parameters;∙ Store preset position parameters;∙ Pan position parameters;∙ Tilt position parameters;∙ Lens zoom position parameter; ∙ Lens focus position parameter; and∙ Lens iris position parameter.
CCTV
3
CCTV
1
CCTV
1
CCTV
1
CCTV
1
104
FEAT8.3.4
FEAT8.3.5
TV010D
TV011D
The device drivers shall contain CCTV system feature control objects and shall contain the following parameters and characteristics:∙ System camera feature control parameter;∙ System camera feature status;∙ System camera System feature control objects equipment availability parameter;∙ System lens feature control parameter;∙ System lens feature status parameter; and∙ System lens equipment availability parameter.
Alarm objects
FEAT8.3.6
TV012D
Discrete input objects:
FEAT8.3.7
TV013D
Discrete output objects:
The device driver shall contain the following CCTV alarm objects:∙ Alarm status parameters;∙ Alarm latch status parameters;∙ Alarm latch clear parameters;∙ Temperature alarm high‐low threshold;∙ Temperature alarm current value parameters;∙ Pressure alarm high‐low threshold parameters;∙ Pressure alarm current value; ∙ Washer fluid alarm high‐low threshold parameters;∙ Washer fluid alarm current value parameters; and∙ Alarm label index parameter.
The device driver shall contain the following CCTV discrete input objects:∙ Discrete input status parameters;∙ Discrete input latch status parameters;∙ Discrete input latch clear parameters; and ∙ Discrete input label index parameters.
The device driver shall contain the following CCTV discrete output objects:∙ Discrete output status parameters;∙ Discrete output control parameters; and∙ Discrete output label indexes.
CCTV
1
CCTV
2
CCTV
2
CCTV
2
105
FEAT8.3.8
FEAT8.3.9
FEAT8.3.10
TV014D
TV015D
Label objects
TV016D
On‐Screen camera menu objects
FEAT8.4
FEAT8.4.1
FEAT8.4.2
Zone parameters:
The device driver shall contain the following CCTV zone parameters:∙ Maximum number of zones parameter; and∙ Zone tables.
The device driver shall contain the following CCTV label objects:∙ Maximum number of labels parameters; ∙ Label tables; ∙ Label location parameters; and ∙ Enable label text displays.
The device driver shall contain CCTV On‐Screen Camera Menu Objects to the extent supported by NTCIP:∙ Activate menu parameters;∙ Menu control parameters.
Display
TV001S
TV002S
The CCTV function shall support the switching of video signals to any video monitor or desktop workstation that is connected with a similar technology and has physical connectivity. MPEG2 displayed on monitors
Protocols to be supported by the software include:∙ VBrick MPEG‐2, Teleste MPEG‐2, Cortec MPEG‐2 iMPath MPEG‐2
The CCTV switching function shall support the switching of video signals to multiple workstations View image multiple locations
if the underlying video hardware provides the functionality.
CCTV
2
CCTV
2
CCTV
2
CCTV
1
CCTV
1
CCTV
1
106
FEAT8.4.3
FEAT8.4.4
FEAT8.4.5
TV004S
TV005S
PA003
FEAT8.4.6
Multiple video images from multiple sources on single monitor
The SunGuide system shall provide the capability for a single workstation monitor to display multiple video images from multiple sources to the extent possible provided by availability of digital video images on the network or the control capabilities of the video switch if the necessary switching, display, conversion and connectivity functionality is supported in the TMC video system.
The SunGuide system shall be capable of routing the maximum number of video frames per second Route video frames to FDOT over the FDOT network to the FDOT Central Office that can be supported by the hardware video Central Office. switch or the network.
Control video
A browser‐based control mechanism shall allow an authorized user to control and view video from any video device so long as the user has a high‐
speed Internet connection defined as an upstream connection speed greater than 256 thousand (256,000) bits per second (user to device).
Video Switching
FEAT8.4.6.1
TV007S
FEAT8.4.6.2
TV008S
The SunGuide Operator Map shall allow a user with appropriate privileges to define, store and Graphical layout management
edit the graphical layout of shared displays in the Video Switching subsystem.
The SungGuide Operator Map shall present shared displays to users as specified by the Shared displays
graphical layout stored in the Video Switching subsystem.
CCTV
1
CCTV
1
CCTV
1
CCTV
4
CCTV
4
CCTV
4
107
FEAT8.4.7
FEAT8.4.7.1
FEAT8.4.7.2
VW001
VW002
VW003
FEAT8.4.7.3
VW004
FEAT8.4.7.4
VW005
FEAT8.4.7.4.1
VW005A
FEAT8.4.7.4.2
VW005B
FEAT8.4.7.4.2.1
VW005B1
FEAT8.4.7.4.2.2
VW005B2
Video Wall
Video Wall Controller Error Reporting
Video Wall Controller Permissions
The SunGuide software shall manage the display of a video wall controller following the SunGuide ICD document, SunGuide‐VW‐ICD‐1.0.2, and the manaufacturer's specified protocol.
The SunGuide software shall report errors in performing management functions of the video wall controller by presenting a description of the error to the user and in the Status Logger.
The SunGuide software shall support the management of user permissions to manage which users can perform management functions of the video wall controller
The SunGuide software shall connect to one or more video wall controllers at a configured host and port
The SunGuide software shall provide management Video Wall Controller functions of the video wall controller to approved Management
users
The SunGuide software shall allow the selection of Video Wall Controller Selection a configured video wall controller to manage
Video Wall Controller Connection
The SunGuide software shall present to the user the configured names of the configured layouts Video Wall Controller Layouts
available from selected video wall controller
The SunGuide software shall allow the activation Video Wall Controller Layout of the selected layout on the selected video wall Activation
controller
The SunGuide software shall allow the Video Wall Controller Layout deactivation of the selected layout on the Deactivation
selected video wall controller
VW
5.1.1
VW
5.1.1
VW
5.1.1
VW
5.1.1
VW
5.1.1
VW
5.1.1
VW
5.1.1
VW
5.1.1
VW
5.1.1
108
FEAT8.4.7.4.3
FEAT8.4.7.4.3.1
FEAT8.4.7.4.3.2
FEAT8.4.7.4.4
VW005C
VW005C1
VW005C2
VW005D
FEAT8.4.7.5
VW006
FEAT8.4.7.6
VW007
The SunGuide software shall present the video wall geometry of the video wall controller that graphically depicts the display viewers currently Video Wall Controller Geometry
active on the selected video wall controller that are used for display on the video wall
The SunGuide software shall allow the user to Video Wall Controller Geometry request an update of the video wall geometry Update Request
from the selected video wall controller
The SunGuide software shall broadcast updated video wall geometry information via the SunGuide Video Wall Controller Geometry databus when updated video wall geometry is Update
provided by the video wall controller
The SunGuide software shall present to the user the configured names of the display sources Video Wall Controller Sources configured in the video wall controller that are used for display on the video wall
The SunGuide software shall allow users to manually switch a display source configured in the Video Wall Controller Switching selected video wall controller to a display viewer used for display in the selected video wall controller
The SunGuide software shall allow users to select a Video Switching configured tour for display in a display viewer of the selected video wall controller. The touring function will automatically Video Wall Controller Touring switch a source by source name, if a source with that name exists, at the configured interval of the tour until another source or tour is selected for display on the same display viewer.
VW
5.1.1
VW
5.1.1
VW
5.1.1
VW
5.1.1
VW
5.1.1
VW
5.1.1
109
FEAT9
FEAT9.1
FEAT9.2
Dynamic Message Signs (DMS)
S019
DM003D
DMS drivers
DMS control
The SunGuide system shall provide an interface to dynamic message signs (DMSs) through a minimum of three drivers supporting:∙ NTCIP protocol (Florida MIB) and∙ Mark IV (I95 protocol).
The DMS device driver shall communicate to the DMS and perform the following:∙ Set or check date and time;∙ Poll the DMS on a periodic basis as specified in the database and retrieve DMS status.∙ Check the cyclic redundancy check of the DMS operating parameters and message library against the cyclic redundancy check parameters of the database;∙ Download operating parameters and DMS command messages;∙ Upload the current operating parameters and display on user's workstation;∙ Download all message text and its attributes;∙ Display all message text, database parameters and attributes on the user's workstation(s);∙ Command the particular DMS message be stored in the message library;∙ All uploaded information from the DMS shall be displayed at the user's workstation(s);∙ The operator, with proper security, shall be able to display/change database messages and parameters. A log of all changes shall be maintained by time and operator identification;∙ Provide a DMS test mode set of commands;∙ Provide a method for restricting overwriting an essential (e.g., incident related) message on a DMS;∙ Provide a log of all communication events to and from the DMS including the report of device errors; and∙ Provide the capability to stop d
h
d
d
DMS
1
DMS
1
DMS
1
110
FEAT9.3
DM001
Sending database messages
FEAT9.4
DM002
Save messages
FEAT9.4.1
DM002A
DMS Priority
The DMS software device driver shall be capable of sending all messages as defined in the DMS message database.
The DMS software shall implement a database of standard messages.
When creating a DMS library message, the user shall be able to configure a message priority.
FEAT9.5
DM001D
Acceptable words/messages
FEAT9.6
DM002D
System configuration
The DMS database shall contain a list of acceptable messages and words/or messages that are unacceptable.
The DMS database shall contain DMS internal operating parameters and internal messages.
FEAT9.7
TB001
Trail blazer signs
The SunGuide system shall provide an interface to the dynamic and blank‐out trail blazer signs.
FEAT9.8
DM003D1
Status information
FEAT9.9
DM004D
DMS driver default page times
FEAT9.10
DM005D
Approved word conflict
FEAT9.11
Fonts
The information requested in the regular periodic poll of DMS devices shall include basic error information from the device, including but not limited to pixel, lamp, temperature and fan errors. For NTCIP devices, this shall be accomplished by utilizing the "short error status" object.
Each DMS device driver shall have configurable default page on and off times.
If DMS detects a word list conflict in a message being activated as part of a sequence, the system shall alert the operator of the conflict and prompt for a decision, just as if the message had been activated manually.
DMS
1
DMS
1
DMS
6
DMS
1
DMS
1
DMS
2
DMS
1
DMS
1
DMS
1
DMS
2.1
111
FEAT9.11.1
DM005MA
DMS fonts
FEAT9.11.2
DM005M1
Assign DMS fonts
FEAT9.11.3
DM005M2
Mark IV centering
FEAT9.11.4
DM005M3
Define font
FEAT9.11.5
DM005M4
Verify message
FEAT9.12
DM007
Travel time default message
FEAT9.13
DM018M
Unavailability of travel times
SunGuide software shall be able to configure a font to use with a SunGuide defined DMS device to either use proportional fonts that are user specified for each type of DMS or to use fixed width font. This requirement applies to Mark IV and NTCIP compliant DMS devices.
SunGuide shall require that a font be assigned to each DMS device.
SunGuide shall horizontally all lines on the sign with respect to the pixel length of the message line versus the pixel width of the sign on the non‐
NTCIP compliant Mark IV signs.
SunGuide shall allow a user to define a font for each type of DMS in use using the following characteristics:
‐ Name of font;
‐ Character height in pixels;
‐ Default character width in pixels; and
‐ Width in pixels for any characters whose width differs from the default.
DMS shall use each device's font characteristics to determine whether a message can be displayed.
On select DMS, the travel time shall be the default message, appearing 24 hours a day, 7 days a week, except when it is overridden by a higher‐
priority message.
When travel times are unavailable for a particular segment, the default message on the associated DMS shall be blank until the data are restored.
DMS
2.1
DMS
2.1
DMS
2.1
DMS
2.1
DMS
2.1
DMS
3
DMS
3
112
FEAT9.14
TM008A
FEAT9.15
EX008L
FEAT9.16
DM016
DMS message types shall be prioritized such that message types with a lower priority will outrank Prioritized DMS message types those with a higher priority value (e.g., incident messages always replace any other type of message).
The log file shall list each newly posted DMS Log posted DMS messages
message, the corresponding DMS' involved, and a time/date timestamp.
The software shall support the use of color DMSs.
Color DMS
DM017
The software shall support the transmission of the color DMS status via Center to Center.
FEAT9.17
FEAT9.18
DM018
Color DMS through C2C
Archival of Color DMS
Transportation Sensor System (TSS)
FEAT10
FEAT10.1
A007
Data collection
FEAT10.2
S016
Predict traffic conditions
FEAT10.3
The software shall support the archival of the transmission of color DMS messages in the database
TD001
Data sources
The SunGuide software shall provide software for traffic data collection and support incident detection.
The SunGuide system shall utilize real‐time and archived data from a variety of sources to determine and report current and predicted traffic conditions for any segment of roadway within the scope of system coverage.
The SunGuide system shall be capable of collecting traffic data from a variety of in‐ground and above‐ground traffic NTCIP compliant detection technologies including, but not limited to, inductive loop systems, radar systems, and video detection systems.
DMS
3
DMS
3
DMS
6
SAS
6
SAS
6
TSS
1
TSS
1
TSS
1
TSS
1
113
FEAT10.4
FEAT10.5
FEAT10.6
FEAT10.7
FEAT10.8
TD002
TD003
TD004
TD005
TD006
Data time intervals The SunGuide system shall be able to receive and process traffic data in time intervals including but not limited to:∙ Ten (10) seconds;∙ Twenty (20) seconds;∙ Thirty (30) seconds;∙ One (1) minute;∙ Five (5) minutes;∙ Ten (10) minutes;. Fifteen (15) minutes;∙ Thirty (30) minutes; and∙ Sixty (60) minutes.
To the maximum extent possible, the Bitrans WashDOT standard for transportation sensor Bitrans WashDOT standard systems shall be utilized for traffic detector communications.
Serial connections
Non NTCIP drivers
Data element categories
The SunGuide system shall provide protocol software to communicate with the Bitrans 238I‐95 traffic detection unit using serial and/or Ethernet connections over a variety of transmission media (i.e. fiber optic, copper, and wireless) that are capable of baud rates equal to or greater than 1200 bits per second.
For traffic detectors within the system that do not support NTCIP, control of these devices shall be supported through device drivers that can be selectively loaded and unloaded by the system's traffic detector application on an as‐needed basis.
The device driver for vehicle detectors shall contain the following categories of data elements:∙ System setup data elements;∙ Control data elements; and∙ Inductive loop detector data elements.
TSS
1
TSS
1
TSS
1
TSS
1
TSS
1
114
FEAT10.9
TD001D
The transportation sensor system setup data elements shall at a minimum contain the following:∙ Sensor system reset parameters;∙ Sensor system status parameters;∙ Sensor system System setup data elements occupancy type parameters;∙ Maximum number of sensor zones parameters;∙ Sensor zone tables;∙ Clock available parameters.
FEAT10.10
TD002D
Control Data elements
FEAT10.11
TD003D
Loop detector data elements
FEAT10.12
TD004D
3M Traffic Sensors
FEAT10.13
TD005D
WaveTronix SmartSensor
FEAT10.14
TD006D
EIS RTMS Sensor
FEAT10.15
DF103
Maintain raw data values
The transportation sensor system control data element shall at a minimum contain the following:∙ Maximum number of outputs parameters;∙ Output configuration tables;∙ Maximum number of output groups parameters;∙ Output group tables;∙ Data collection tables;∙ Data buffer tables.
The transportation sensor system inductive loop detector data element shall at a minimum contain the following data elements∙ Loop system setup tables;∙ Loop output conditioning tables; and∙ Loop system status tables.
The SunGuide system shall be capable of collecting traffic data from 3M Traffic Sensing Series TMC900E and TMC900 vehicle detection devices.
The SunGuide system shall be capable of collecting traffic data from the WaveTronix SmartSensor.
The SunGuide system shall be capable of collecting traffic data from the Electronic Integrated Systems (EIS) RTMS sensor.
SunGuide shall maintain the raw data values read from traffic sensors in their original precision.
TSS
1
TSS
1
TSS
1
TSS
2
TSS
1
TSS
1
TSS
3
115
FEAT10.16
FEAT10.16.1
FEAT10.16.1.1
FEAT10.16.1.2
Probe sensors
General
TM001S
TM003P
FEAT10.16.1.3
TM004P
FEAT10.16.1.4
TM004P1
FEAT10.16.1.5
TM005S5
FEAT10.16.1.6
TM006P
FEAT10.16.1.7
TM007S1
FEAT10.16.2
Latency of no more than 2 minutes
Interface with AVI and LPR equipment
Processing associated with collection, fusion, and dissemination of real‐time toll tag data feeds shall introduce a latency of no more than two (2) minutes from the time the data was acquired by SunGuide to when the data is presented to the travel time module for use in calculating travel time.
SunGuide shall interface with Toll Tag Reader (AVI) equipment and License Plate Reader (LPR) equipment to obtain data on Probe Vehicles.
SunGuide shall poll all LPR and AVI reader stations Poll readers at a configurable not marked as inactive at a SunGuide operator rate
with appropriate permissions configurable rate.
Use interface compatible with SunGuide shall use an interface compatible with readers
the LPR and AVI reader stations.
The SunGuide system shall interface with Data Use of FDOT‐approved, Collection modules using a standardized interface that is documented and approved by FDOT.
standardized interface
SunGuide shall calculate average speeds for Average speeds based on probe segments based on the measured travel time of vehicles
individual probe vehicles.
SunGuide shall process AVI tag ids in the form Keep toll tag customers provided by the tag readers, i.e. will not anonymous
reconstruct the original tag or identifying information.
LPR data collection
TSS
TSS
4
4
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
116
FEAT10.16.2.1
FEAT10.16.2.2
TM001X
TM002X
FEAT10.16.2.3
TM003X
FEAT10.16.2.4
TM004X
FEAT10.16.2.5
TM004X1
The SunGuide Software shall collect the following data from License Plate readers (LPR): ‐ Individual license plate numbers that have been made anonymous by the LPR readers. ‐ A timestamp for when each license plate number was collected ‐ Data Collection Station id Data to collect from LPR readers ‐ Lane of travel from which data was collected ‐ Quality/likely accuracy of each plate read (as assessed by LPR system) ‐ Information concerning system health ‐ license plate readers, power, communications, etc.
SunGuide shall monitor system health of the LPRs to include as a minimum: power, and Monitor system health of LPRs
communication (i.e., system health) status.
SunGuide shall synchronize the LPR's internal clock if supported by the reader station Synchronize internal clock for equipment with the SunGuide system time clock LPR readers
that is used by SunGuide to time stamp reader data.
The SunGuide LPR data collection function shall communicate with the existing LPR protocols used Communicate with existing LPR for travel time data collection applications in the protocols
State of Florida: PIPS and Inex Zamir Zap.
Support PIPS and Zap LPR protocols
The SunGuide LPR data collection function shall be able to process data from Inex Zamir Zap LPR readers used for traffic conditions data collection applications.
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
117
FEAT10.16.2.6
TM007G
FEAT10.16.2.8
FEAT10.16.2.8.1
TM005X
FEAT10.16.2.8.2
TM005X1
FEAT10.16.2.8.3
TM005X2
FEAT10.16.2.8.4
TM005X3
FEAT10.16.2.8.5
TM005X4
FEAT10.16.2.8.6
TM006X
FEAT10.16.2.8.7
TM007X
FEAT10.16.3
SunGuide shall notify SunGuide operators of reported failures by the LPR equipment.
SunGuide shall provide separate configurable Configurable parameters for parameters for adminstrating license plates
license plates Alert operators upon failures
Administering license plate length
SunGuide shall provide separate configurable parameters for administrator for minimum license plate length and maximum license plate length to perform license plate matching to calculate travel time.
Default value for minimum length
Default value for maximum length
SunGuide shall provide the default value 3 for minimum license plate length.
SunGuide shall provide the default value 5 for maximum license plate length.
SunGuide shall not use any license plate reads Minimum length for licesnse which have length shorter than minimum license plate reads
plate length for travel time calculation.
Maximum length for license plate reads
SunGuide shall not use any license plate reads which have length longer than maximum license plate length for travel time calculation.
SunGuide shall not include any license plate reads Character/digits read by license which contain non‐alphanumeric characters to plate reads
perform license plate matching to calculate travel time.
SunGuide shall not store license plate read data in Storage or license plate reads
the database
AVI data collection
TSS
4
TSS
4.3
TSS
4.2
TSS
4.2
TSS
4.2
TSS
4.2
TSS
4.2
TSS
4.2
TSS
4.3
TSS
4
118
FEAT10.16.3.1
TM002S
FEAT10.16.3.2
TM003S
FEAT10.16.3.3
TM003S1
FEAT10.16.3.4
TM005P
FEAT10.16.3.5
TM005S
FEAT10.16.3.6
TM005S1
SunGuide shall allow users to perform system configuration activities without introducing latency greater than 2 minutes in the real‐time processing of the toll tag with the exception of the System config activities without addition, removal, or modifications to AVI introducing latency
collection (The system can be reconfigured while it is running without increasing the current latency.)
The SunGuide Toll Tag reader function shall be Operational 99.9% the time, operational 99.9% the time, measured annually annually
over a 24 hour period.
Operational shall be defined as that the system is Operational definition
running and that no internal errors have occurred.
SunGuide shall synchronize the reader stations' internal clock if supported by the reader station Synchronize internal clock for equipment with the SunGuide system time clock AVI readers
that is used by SunGuide to time stamp reader data.
The Toll Tag reader function shall include an AVI data collected for probe interface with AVI data collection equipment to TVT calculations
collect data to be used for probe travel time calculations.
The AVI data collection system shall communicate with the existing AVI protocols used for travel Support Allegro and Flex AVI time data collection applications in the State of protocols
Florida: TransCore Allegro and SIRIT Flex.
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
119
FEAT10.16.3.7
FEAT10.16.3.8
FEAT10.16.3.9
FEAT10.16.3.10
FEAT10.16.3.11
TM005S2
TM005S3
TM005S4
TM005S6
TM005S7
AVI configurable poll cycle
Add AVI sensors to system
Modify AVI sensors in the system
Raw data collected
Support IT2020 and Sirit Identity Flex AVI protocols
The AVI data collection system shall receive AVI Tag data from the toll collection agency AVI Data Collection Sensors, or alternatively poll the Data Collection Sensors within a configurable amount of time of when the data is polled by SunGuide.
Users shall be able to add AVI Data Collection Sensors to the SunGuide system and changes will take effect when the system is restarted.
Users shall be able to modify AVI Data Collection Sensors that have already been added to the SunGuide system. Changes will take effect when the system is restarted.
Raw AVI data collected by SunGuide shall include the following: Transponder ID ‐ unique AVI tag identifier, Reader ID ‐ Data collection sensor that made, the tag read, Lane ID ‐ lane in which the tag was read, Time stamp ‐ time when the tag was read, Fault Information ‐ fault information from the data source.
The AVI data collection function shall be able to process AVI tag data from the existing AVI readers used for travel time data collection applications in the State of Florida: TransCore IT2020 (via UDP and TCP) and Sirit Identity Flex.
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
120
FEAT10.16.3.12
TM005S8
Alert sent if no data received
FEAT10.16.3.13
TM006S2
Report device errors
FEAT10.16.3.14
TM007S2
Archive AVI transponder IDs
FEAT10.16.3.15
TM009S
FEAT10.16.3.17
TM009S2
Archive AVI tag read data
Raw AVI data archived as received
Dynamic linking
FEAT10.16.4
FEAT10.16.4.1
TM006T1
Initiate dynamic link re‐
definition
FEAT10.16.4.2
TM006T3
Linking across the system
FEAT10.16.4.3
TM006T4
FEAT10.16.5
FEAT10.16.5.1
TM008S
An alert shall be generated to the SunGuide operator if no data is received from an AVI or LPR device after a configurable amount of time that can be established the by the SunGuide Administrator. This configured time is the same time designated as the polling cycle for detector devices.
The AVI data collection system shall report errors in AVI Data Collection devices.
The SunGuide system shall archive AVI transponder IDs.
SunGuide shall archive AVI Tag read data.
Raw AVI Tag read data shall be archived in the same format in which it was received.
The Travel Time function shall have the ability to initiate dynamic link re‐definition to compensate for loss of data collection stations that would otherwise result in the loss of segment travel times.
The SunGuide GUI shall allow an operator to suspend and resume dynamic linking for associated probe TSS links across the system.
The SunGuide GUI shall allow an operator to Linking for associated probe TSS suspend and resume dynamic linking for links
associated probe TSS links.
Probe fusion
The Data Server shall filter out duplicate tag reads (i.e. reads of the same AVI transponder, at the Filter duplicate tag reads
same data collection site, in a given time.)
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
TSS
4
121
FEAT10.16.5.2
TM009S3
Retain toll tag data for one month
FEAT10.16.6
TM025
Probe‐based travel time calculation Toll tag data shall be retained on line for one month and be able to be exported for long term storage.
The probe‐based travel time calculation algorithm shall utilize several user configurable parameters in its calculation on a per probe (TSS) link basis
SunGuide shall not include the zero speed value in its calculations for smoothed speed, but shall Discard zero speed in smoothed include the zero occupancy and zero volume data
values in calculations for smoothed occupancy and volume.
Adding a "Recovery Threshold" to TSS alrams, which will prevent SunGuide from generating a large number of alerts when the traffic data is TSS Alarms
oscillating around the alarm threshold
FEAT10.17
FEAT10.18
FEAT10.18.1
TD009T
FEAT10.18.2
TD009T1
FEAT10.18.3
TD009T2
FEAT10.18.4
TD009T3
FEAT10.18.5
TD009T4
Generate TSS alarms
SunGuide shall generate TSS alarms
A TSS alarm shall be configurable to generate alarms for speed or occupancy, or for speed and Configure TSS alarm
occupancy. This will be configurable at the link level
A TSS alarm shall not be triggered when TSS TSS alarm triggering
reports no traffic. (i.e. speed, volume and occupancy = 0.)
Once a TSS alarm has been triggered, it shall not be retriggered until simultaneously speed is above TSS Alarm retriggering
its recovery threshold and occupancy is below its recovery threshold.
TSS alarms that have not been addressed by an operator shall be removed when the traffic data Removal criteria for TSS alarms that triggered the alarm subsequently crosses the Recovery Threshold.
TSS
4
TSS
5.1.1
TSS
4
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
122
FEAT10.18.6
TD009T5
TSS Alarm Configuration
FEAT10.18.7
TD009T6
TSS Link Data Screen
FEAT10.18.8
TD009T7
TSS Alarm Operator map view
FEAT10.18.9
TD009T8
TSS Alarm triggering speed or occcupancy
FEAT10.18.10
TD009T9
TSS Alarm triggering on spped and occupancy
FEAT10.18.11
TD009T10
TSS Alarm triggering on speed only
FEAT10.18.12
TD009S
FEAT10.18.12.1
TD009S1
FEAT10.18.12.2
TD009S2
The Recovery Threshold shall be configurable per link in the Admin Editor.
The Operator Map shall represent the data region between the threshold and recovery threshold with yellow in the 'TSS Link Data' screen.
A link where the traffic data currently falls between the Recovery Threshold and the Alarm Threshold shall be displayed in yellow on the Operator Map.
If configured for speed or occupancy, a TSS alarm shall be triggered when the speed or occupancy values cross the Alarm Thresholds configured for that link.
If configured for speed and occupancy, a TSS alarm shall be triggered when the speed and occupancy values cross the Alarm Thresholds configured for that link.
TSS alarms shall be based on speed only by setting occupancy alarm threshold to 100% and the occupancy recovery threshold to 100%.
When a TSS detector status transitions to "ACTIVE" from either "FAILURE" or "OUT OF TSS Stabilization Hold‐off
SERVICE", SunGuide shall not generate alarms the detector has stabilized.
A detector is stable if it reports data for a Stable detector
configurable period of time.
The stabilization period is configurable at the Configuration of stabilization driver level within the system configuration file.
period
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
123
FEAT10.19
FEAT10.19.1
Polling Failed Devices
TD014E
Polls a TSS detector
FEAT10.19.2
TD014A
Device is in "ERROR" and Sunguide successfully polls device
FEAT10.19.3
TD014F
Device in "ERROR" and Sunguide unsuccessfully polls device
FEAT10.19.4
TD014O
FEAT10.19.4.1
TD014O1
FEAT10.19.5
TD015F
Poll device at a "slow poll" rate
FEAT10.19.5.1
TD015F1
Slow poll rates are configurable
FEAT10.19.5.2
TD015F2
FEAT10.19.6
TD015S
FEAT10.19.6.1
TD015S1
Device placed "OUT OF SERVICE"
Device "OUT OF SERVICE" not polled
Allows dirvers to periodically attempt to reconnect to failed devices. THis will allow SunGuide drivers to continue to poll failed devices(at a reduced rate) and bring them back into operation
When SunGuide polls a TSS detector and the poll is unsuccessful, SunGuide shall report the device in "ERROR" status.
If a device is in "ERROR" and SunGuide successfully polls the device then the device status is reported as "ACTIVE" state.
If a TSS device is in "ERROR" and SunGuide unsuccessfully polls the device a configurable number of times, the device is placed in "FAILURE" state.
SunGuide shall allow an operator to place a device in "OUT OF SERVICE."
SunGuide shall not poll a device with status "OUT OF SERVICE."
When a traffic detection device is in "FAILURE" mode, SunGuide shall poll the device at a "slow poll" rate.
Slow poll rates shall be configurable at the driver level within the system configuration file.
When a device is successfully polled at the slow poll rate, the device will be placed in "ACTIVE" status.
SunGuide shall store traffic detection device state Store traffic detection device transitions as "Online" (active) or "Offline" (error state transitions
and failure).
State transitions have date and Traffic detection device state transitions shall time
have date and time of the transition.
Device successfully polled
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
TSS
4.3
124
FEAT10.19.6.2
TD015S2
FEAT10.19.6.4
TD015S4
FEAT10.20
TD016
FEAT10.21
TD017
FEAT10.22
FEAT10.23
TD019
FEAT10.25
TD020
Traffic detection device state transitions shall State transitions have transition have indication of transition reason, (poll failure, reason
operator forced, operator who performed the operation, etc.)
SunGuide shall write messages to the Status Write messages to Status Logger when traffic detector device operational Logger
state transitions.
The software shall be able to send Traffic Detector Traffic Detector Failure Alerts
Failure alerts.
System‐wide Traffic Detector The software shall be able to send System‐wide Alerts
Traffic Detector Failure alerts.
The software shall be able to send Invalid Invalid Detector Data Alerts
Detector Data alerts.
Traffic Detector Failure, System‐wide Traffic Alert Generation Delay Detector Failure, and Invalid Detector Data alerts Threshold
shall delay generation of the alert based on a delay threshold.
The software shall allow the user to configure a EIS G4
detector to use the EIS G4 protocol
FEAT10.25.1
TD020A
Data Collection
FEAT10.26
TD021
Volume Weighted Average
FEAT10.26.1
TD021A
Lane Average
FEAT10.26.2
TD021B
Link Average
The software shall support communicating to the detector using the EIS G4 protocol including receiving speed, volume, occupancy, and classification data.
TSS shall produce the average speed based on a volume weighted averaging method.
The rolling average for a lane shall weight the speed on each vehicle in the rolling average period equally.
For a given poll cycle, the TSS link speed average shall weight the speed of each vehicle in each lane equally.
TSS
4.3
TSS
4.3
GUI
5
GUI
5
GUI
5
GUI
5
TSS
6
TSS
6
TSS
6
TSS
6
TSS
6
125
The rolling average for a TSS link shall weight the speed on each vehicle in the rolling average period equally.
For a given poll cycle, if the volume reported 0, the lane shall not report a speed for that period
FEAT10.26.3
TD021C
Link Rolling Average
FEAT10.26.4
TD021D
No Volume Condition
FEAT10.26.5
TD021E
Types of Link Averages
FEAT10.26.5.1
TD021E1
Discard Lane Average for 0 Volume
FEAT10.26.5.2
TD021E2
Discard Link Average for 0 Volume
TSS links shall provide an average link speed based on raw data and an average based on a rolling average.
For a given poll cycle, if the volume reported 0, the lane shall not be included in the raw data link average
For the rolling data link average, if the link reports 0 volume for a given poll cycle, that cycle shall not be include in the rolling data link average.
No Data Condition
If no data is available for the link average, the link average shall not report a speed for that period
FEAT10.26.5.3
FEAT10.27
FEAT10.27.1
TD021E3
TD022
TD022A
FEAT11
FEAT11.1
The software shall have a configuration parameter Minimum Volume Threshold for specifying the minimum volume needed for a lane alert generation
in order to produce an alert.
Non‐alert Conditions
The software shall not generate an alert if the poll cycle reports a volume less than the minimum volume needed to produce an alert.
Evacuation Coordination (EC)
S023
Definition
The SunGuide system shall provide an evacuation coordination subsystem to provide for management of traffic during evacuations.
TSS
6
TSS
6
TSS
6
TSS
6
TSS
6
TSS
6
TSS
6
TSS
6
EC
2
EC
2
126
FEAT11.2
FEAT11.3
EC001
EC002
FEAT11.4
Manage evacuation
Functionality
The evacuation coordination subsystem shall provide the capability to provide evacuees with information they need during the evacuation, as well as the reentry.
The evacuation coordination subsystem shall consist of five (5) major functions: (1) evacuation guidance, (2) evacuation travel information, (3) evacuation traffic management, (4) evacuation planning support and, (5) resource sharing.
Evacuation Guidance (EG)
FEAT11.4.1
EC001G
FEAT11.4.2
EC002G
FEAT11.4.3
EC003G
FEAT11.4.4
EC004G
FEAT11.4.5
EC005G
The evacuation guidance component shall provide the capability to determine and display those Determine evacuation necessity evacuation zones under specific government orders to evacuate during an emergency condition.
The evacuation guidance component shall be Multiple distributed locations accessible to users who access the Internet through a browser application.
The evacuation guidance component shall provide Shelter‐in‐place information for shelter‐in‐place information for evacuation zones non‐evacuation
where local governments have not issued specific orders to evacuate.
The evacuation guidance component shall provide List and graphical depiction of a means to obtain evacuation zone locations and evacuation zones status.
The evacuation guidance component shall provide a list of alternative evacuation destinations on Alternative evacuation demand as appropriate based on the emergency destinations
condition requiring evacuation.
EC
2
EC
2
EC
2
EC
2
EC
2
EC
2
EC
2
EC
2
127
FEAT11.4.7
EC007G
FEAT11.4.8
EC008G
FEAT11.4.9
EC009G
The evacuation guidance component shall provide a display of actual traffic conditions on Recommended evacuation and instrumented evacuation routes. This information shall include at a minimum:∙Travel times and reentry start time
speeds.∙Current construction and detours information.
The evacuation guidance component shall provide information regarding evacuation shelters in areas specified by users. The information shall provide:∙ Locations of evacuation shelters;∙ Time during which evacuation shelters are in operation;∙ Evacuation shelters Occupancy levels at evacuation shelters; and∙ Available facilities at evacuation shelters, including those shelters that will accommodate people with special needs, such as pets, disabilities, and the elderly.
Zones and categories
The EG shall provide a means of determining evacuation zone and category information.
Evacuation Travel Information (ETI)
FEAT11.5
FEAT11.5.1
EC003
FEAT11.5.2
EC001E
The evacuation coordination subsystem shall Evacuation travel information provide an evacuation travel information function.
The evacuation travel information function shall provide the capability for users to access Multiple distributed locations
information via the Internet using a browser to view a web application.
EC
2
EC
2
EC
2
EC
2
EC
2
EC
2
128
FEAT11.5.3
EC002E
FEAT11.5.4
EC003E
FEAT11.5.5
EC004E
FEAT11.5.6
EC005E
Information about traffic conditions
The evacuation travel information function shall provide information about traffic conditions on evacuation routes and shall provide:∙ Current speed/travel time on evacuation routes.∙ An estimate of future speed/travel time on evacuation routes, taking into consideration current evacuation decisions and traveler behavior.∙ Information regarding incident conditions on evacuation routes. ∙ Real‐time road, bridge and lane closure information.∙ A list of roads that should be avoided due to hazardous conditions, such as flooding, malfunctioning traffic signals, debris and falling objects.
The evacuation travel information function shall Current and forecast weather provide the current and forecast weather conditions
conditions for evacuation origins, destinations and routes.
The evacuation travel information function shall provide information regarding transportation modes including buses, airlines, trains and ships. Specifically, ETI shall provide:∙ Information regarding the availability of transportation mode Transportation modes services;∙ Arrival and departure information, including location, for those services available.
Evacuation guidance information The evacuation travel information function shall provide general evacuation guidance information to travelers, including guidance/tips for trip preparation, trip duration and trip return.
EC
2
EC
2
EC
2
EC
2
129
FEAT11.5.7
EC006E
FEAT11.6
FEAT11.6.1
FEAT11.6.2
FEAT11.6.5
FEAT11.6.6
FEAT11.6.7
FEAT11.7
Lodging availability
The evacuation travel information function shall provide information regarding lodging available along evacuation routes and at evacuation destinations.
Evacuation Traffic Management
EC004
EC001M
EC004M
EC005M
EC006M
The evacuation coordination subsystem shall use the SunGuide subsystems (e.g. DMS, CCTV, TSS, Evacuation traffic management Incident Management) to provide an evacuation traffic management function.
Real‐time data collection Control of devices Manual override Incident management for evacuation routes.
Evacuation Planning Support
The evacuation traffic management function shall use the SunGuide subsystems (e.g. DMS, CCTV, TSS, Incident Management) to assist in the selection of evacuation strategies and to monitor the operations of the strategies selected.
The evacuation traffic management function shall utilize the SunGuide device control subsystems (e.g, DMS, CCTV) to provide the control of devices as required by the evacuation management plan.
The evacuation traffic management function shall utilize the SunGuide device control subsystems (e.g, DMS, CCTV) to provide the capability to control, change and confirm device changes.
The evacuation traffic management function shall utilize the SunGuide Incident Management subsystem to perform the incident management function for evacuation routes.
EC
2
EC
2
EC
2
EC
2
EC
2
EC
2
EC
2
EC
2
130
FEAT11.8
Resource Sharing
Road Weather Information System (RWIS)
FEAT12
FEAT12.1
A005
Detection of road weather conditions
FEAT12.2
S017
Standards consistency
FEAT12.3
RW004
NTCIP protocol
FEAT12.4
RW001D
Physical communication
FEAT12.5
RW002D
Object definitions
EC
2
RWIS
The SunGuide software shall provide software for detection of road weather conditions that may impact operations.
The FL‐ATIS shall be network‐based using Transmission Control Protocol/Internet Protocol (TCP/IP) connectivity, the Hypertext Transfer Protocol (HTTP), and XML data format based shall be consistent with TMDD 2.1 (and NTCIP 2306) and the emerging TMDD 3.0 (and NTCIP 2306). FDOT modified SAE J2540 IITS codes shall be used to capture event information.
The RWIS interface shall use the NTCIP protocol.
The RWIS interface function shall implement SNMP over UDP/IP to communicate with NTCIP RWIS devices.
The RWIS interface function shall implement the NTCIP OIDs necessary to implement the functionality that is to be provided through the GUI (see RW0002U or FEAT12.6).
RWIS
2
RWIS
2
RWIS
2
RWIS
2
RWIS
2
131
FEAT12.6
RW002U
Data fields FEAT12.7
RW001
NTCIP protocol standard FEAT12.8
RW002
RWIS Interface
FEAT12.9
RW005
User interface display
FEAT12.10
RW001U
Statewide data display
FEAT13
FEAT13.1
The user interface shall provide the following data fields relative to each RWIS field unit:∙ Name;∙ Location;∙ Data age;∙ Air temperature;∙ Dew point temperature;∙ Relative humidity;∙ Precipitation type∙ Precipitation intensity;∙ Precipitation rate;∙ Precipitation accumulation;∙ Visibility;∙ Average wind speed;∙ Wind gust speed;∙ Wind direction;∙ Surface sensor name;∙ Surface temperature;∙ Freeze point;∙ Chemical factor;∙ Chemical percent; and∙ Ice thickness.
The NTCIP standard for environmental sensor stations (ESS) shall be utilized for the RWIS interface communications.
The RWIS interface function shall provide protocol software to communicate with RWIS field units using NTCIP.
The RWIS user interface shall be a software application within the SunGuide system that displays the required RWIS data fields.
It shall be possible for any workstation within the SunGuide system to access the RWIS user interface and the data from all RWIS system components statewide.
Center to Center (C2C)
A020
Center‐to‐center communications The SunGuide software shall provide software for center‐to‐center communications to support major incidents that affect multiple jurisdictions including evacuation.
RWIS
2
RWIS
2
RWIS
2
RWIS
2
RWIS
2
C2C
1
C2C
2
132
FEAT13.2
FEAT13.3
A021
S021
Coordination and delegation
Center‐to‐Center functions
The SunGuide software shall support the coordination and delegation of control of operations and management during natural or man‐made disasters or evacuations. Information exchanged currently includes:∙ Description∙ Special staging area∙ Number of people affected∙ Source∙ Contact ∙ Start and end times
The SunGuide system shall support center‐to‐
center communications through the normal command/control functions, the status update of field devices, web server switching to another RTMC, incident data review as an output from the Data Distributor, and the GUI display from the ARCView software or Map Objects.
If SunGuide receives a DMS request from another center, a configurable parameter shall be provided as to whether or not an operator has to Message approval parameter
approve the posting of DMS request to the Message Arbitration System (MAS) subsystem.
FEAT13.5
DM010D
FEAT13.6
DM001M
Validate device requests
FEAT13.7
DM016M1
DMS configuration
FEAT13.8
TM020
Support data exchanging
Device requests received via the C2C interface shall be validated.
SunGuide shall publish the number of characters per line for each DMS in the inventory information sent through C2C. No proportional font information will be sent over the C2C interface.
SunGuide shall support exchanging of data through C2C with the FHP.
C2C
2
C2C
2
C2C
2.1
C2C
2.1
C2C
2.1
C2C
3
133
FEAT13.9
FEAT13.10
TM002V
TM002V1
FEAT13.11
CR002
FEAT13.12
CR003
FEAT13.13
OD001T
FEAT13.14
DF005C
FEAT13.15
DF005C
Automated interface
Configured to support data sources
SunGuide automated interface shall consist of C2C XML Interfaces through which each of the participating systems and organizations will transmit their respective data to SunGuide.
The SunGuide software shall be capable of being configured to accommodate supported data sources as they become available.
The SunGuide software shall be capable of processing all required data sources and providing Processing and providing data
this data to other centers through a center‐to‐
center interface.
SunGuide shall be capable of storing information Storing multiple source from multiple automated and manual sources, information
including weather.
The SunGuide data available via the center‐to‐
Time stamping of data
center interface will be time stamped.
The SunGuide Center‐to‐Center interface shall Support exchange of floodgate support the exchange of the floodgate information
information entered by an operator via the GUI.
Exchange of floodgate information
The SunGuide Center‐to‐Center interface shall support exchange of floodgate information entered by an operator via the GUI.
Filter out TvT Links, CCTV and DMS from FL‐ATIS
FEAT13.17
FEAT13.17.1
CC001
CCTV configuration data
FEAT13.17.2
CC002
DMS Configuration Data
CCTV configuration data published to C2C shall have an attribute indicating whether the device should be visible to the public
DMS configuration data published to C2C shall have an attribute indicating whether the device should be visible to the public
C2C
3
C2C
3
C2C
3
C2C
3
C2C
3
C2C
4
C2C
4
PS
4.3
C2C
4.2
C2C
4.2
134
FEAT13.17.3
CC003
Travel Time configuration data published to C2C shall have an attribute indicating whether the link Travel Time Configuration Data
should be visible to the public.
FEAT13.18
CC004
EM Location Publish Flag through C2C
FEAT13.19
CC005
Soft Messaging
FEAT13.20
CC006
FEAT14
FEAT14.1
Head/Tail Location sent to FLATIS
When an EM location is published via C2C, it shall contain the setting indicating whether or not the locations should be published.
Events should be published via C2C only if the event status is "Active" or "Unconfirmed"
When an "aafected area" event is selected and the user has set the head and tail of the event, the head of the event shall be sent as the primary event location and the tail of the event shall be sent as the secondary event location
Data Archiving (DA)
A019
Data warehousing
FEAT14.2
SS001A
Automated archiving FEAT14.3
SS002A
Archive data minimums
The SunGuide software shall provide software for storing and regionally sharing traffic data so it can be archived in a data warehouse.
The system support archiving component shall provide automated archiving of data to a common file usable by external databases for reporting purposes.
At a minimum, the system support archiving component shall archive the following information:∙ Incident history data;∙ Device status logs;∙ Detector data; and ∙ System logs.
C2C
4.2
C2C
5
C2C
5
C2C
6
DA
2
DA
2
DA
2
DA
2
135
FEAT14.4
SS003A
Format standards
FEAT14.5
SS004A
Export form
FEAT14.6
TM014D
Time‐stamped data archive information FEAT15
FEAT15.1
The format of the archived data shall comply with standards set by FDOT's TranStat Office that are required for performance monitoring and deployment evaluation, including data input to the HPMS. This applies only to SunGuide collected data.
The system support archiving function shall support archiving as an export to comma delimited form.
The SunGuide data available in the Data Archive will be time stamped.
Ramp Metering System (RMS)
TM001M
Ramp meter configuration
FEAT15.1.1
TM001M1
Download parameters
FEAT15.1.2
TM001M2
Online status
FEAT15.1.3
TM001M3
Associate detectors
FEAT15.1.4
TM001M4
Modify vehicle release mode
The system shall allow operational parameters to be downloaded to one or more ramp meter controllers. These parameters currently include:∙ Metering rate table∙ Mode control∙ Time of day table
The system shall allow ramp meter controllers operational status to be manually changed to inactive/active.
The system shall allow mainline and on‐ramp traffic detectors to be associated with a ramp meter controller.
The system shall allow the vehicle release mode of a ramp meter controller to be modified. Release modes currently include:∙ Single car∙ 2‐car tandem∙ 2‐car platoon∙ 2‐car staggered∙ HOV bypass
DA
2
DA
2
DA
3
RMS
2
RMS
2
RMS
2
RMS
2
RMS
2
RMS
2
136
FEAT15.1.5
TM001M5
Responsive mode
FEAT15.1.6
TM001M6
Manual override
FEAT15.2
TM002M
System
FEAT15.2.1
TM002M1
The system shall allow the central operating parameters to be modified. These parameters currently include:∙ Ramp Metering(demand‐
System operating parameters responsive) Algorithm∙ Time of day (for selecting mode of operation and for selecting times to activate or deactivate ramp metering).
FEAT15.2.2
TM002M2
Controller groups
FEAT15.2.3
TM002M3
Central overrides
FEAT15.2.4
TM002M4
The system shall allow demand‐responsive mode parameters to be modified for a ramp meter controller. Responsive mode parameters currently include:∙ Mainline occupancy∙ Queue length
The system shall allow a user with appropriate permissions to override the automatic control of a ramp meter.
Monitoring status
The system shall allow groups of ramp meter controllers to be defined. Groups of groups may also be defined.
The system shall allow a local time of day (TOD) ramp metering control table to be defined for each ramp meter. The local TOD table is downloaded to the controller to control ramp metering in the case of communication failure.
The system shall monitor ramp meter controller status and change the operator display to indicate failed or marginal to reflect the current ramp meter controller status.
RMS
2
RMS
2
RMS
2
RMS
2
RMS
2
RMS
2
RMS
2
137
FEAT15.2.5
TM002M5
Metering on/off
FEAT15.2.6
TM002M6
Logging
FEAT15.3
TM003M
Ramp meter communication
FEAT15.3.1
TM003M1
Automatic polls
FEAT15.3.2
TM003M2
Manual poll
FEAT15.3.3
TM003M3
Synchronize clock
The system shall turn ramp metering operations on or off based on the WSDOT/UW algorithm using traffic conditions input from mainline and on‐ramp detectors associated with ramp metering.
The system shall log the following events:
Communication errors with ramp meter controllers∙ Manual overrides of ramp meter control∙ Changes between modes of operation (on/off, TOD, etc.).
The system shall poll ramp meter controllers for their current status periodically at a rate that is configurable by a user who has appropriate permissions.
The system shall allow ramp meters to be manually polled for their current status.
The system shall allow the clocks on a ramp meter controller to be synchronized with the current system date and time.
Message Arbitration System (MAS)
General
FEAT16
FEAT16.1
FEAT16.1.1
DM004
Message queue
FEAT16.1.2
DM005M
Number of priority levels
The SunGuide system shall support a priority‐
based queue for messages.
The system shall support 256 message priority levels.
RMS
2
RMS
2
RMS
2
RMS
2
RMS
2
RMS
2
MAS
1
MAS
1
MAS
1
MAS
1
138
FEAT16.1.3
TM014T2
FEAT16.1.4
TM014T3
FEAT16.1.5
TM014T4
FEAT16.2
Manual pages with TvT messages
If the operator elects for the manual page to coexist with the travel time message, the travel TvT pages update automatically time page(s) shall continue to update automatically, without disturbing or removing the manual page.
At any time, the operator shall be able to remove Manual pages removed without the manual page from sign without disrupting the disrupting TvT pages
updating of the travel time page(s).
Device control
FEAT16.2.1
DM006M
Priority display
FEAT16.2.2
DM007M
Remove message
FEAT16.2.3
DM007M2
Same priority
FEAT16.2.4
DM007M1
Blank queue
FEAT17
Manual pages can replace or coexist with travel time messages. (For example, as the system posts "To SR 528, 5 MILES, 10 minutes," an operator can add "Roadwork Ahead" as a second or third, alternating page, to the message. Alternatively, the operator can completely replace the automated message with a single "Roadwork Ahead" page.)
Safety Barrier (SB)
If a message is placed in the queue with a higher priority than the currently active message, the higher‐priority message shall be displayed on the device.
When a message is removed from the queue, the message with the next highest priority shall be activated.
If two messages of the same priority are on the queue the message received first will be displayed first.
If the queue for a device becomes empty, the device shall blank.
MAS
3
MAS
3
MAS
3
MAS
1
MAS
1
MAS
1
MAS
1
MAS
1
SB
1
139
FEAT17.1
EX005L
FEAT17.2
FEAT17.2.1
FEAT17.2.2
SB protocol
SB Status
TM017R
TM017R2
FEAT17.3
Monitor SB status
SB status information
SunGuide software shall monitor the status of each safety barrier device. Status information includes:∙ Lamp status,∙ switch status
Barrier sensor status shall include but not be limited to:Data byte 1: Lamp status: ∙ Hex 0 ‐ normal position∙ Hex 1 ‐ barrier event in progress∙ Hex 2 ‐Failed∙ Data byte 2: Switch status:∙Hex 0 ‐ normal position∙Hex 1 ‐ barrier event in progress∙ Hex 2 ‐Failed∙Data bytes 3‐66: ASCII text string
SB Detection
FEAT17.3.1
TM014
Detect SB incidents
FEAT17.3.2
TM001S
SB switch alert
FEAT17.3.3
EX004L
Log timestamp of switch activation
FEAT17.3.4
EX004L1
Log timestamp of switch restoration
FEAT18
FEAT18.1
The SunGuide Safety Barrier Interface Protocol shall be used to communicate with safety barrier devices.
Travel Times (TvT)
General
SunGuide software shall detect and react to incidents associated with vehicles impacting sensor equipped safety barriers along the roadway.
SunGuide software shall alert the operator in the event a message is received indicating one or more breakaway switches are tripped and the associated strobe light is activated.
Events associated with safety barrier breakaway switch activations shall be logged with a date time stamp.
Restoration of the breakaway switch (closure) shall be logged with a date time stamp.
SB
1
SB
1
SB
2
SB
2
SB
1
SB
2
SB
2
SB
1
SB
2
TVT
TVT
2
2
140
FEAT18.1.1
S031
FEAT18.1.2
DF200R3
FEAT18.1.3
DM019M
FEAT18.1.4
TM004T
FEAT18.1.5
TM004S
FEAT18.1.6
TM004T2
FEAT18.1.7
TM006T
SunGuide shall compose and be capable of sending messages to DMS that inform travelers of Compose and send travel time the average travel time between two points on the instrumented and monitored roadway system messages
defined by each District.
Once configured, SunGuide shall calculate the total travel time along the summary drive‐time comparisons by summing the travel times along each roadway link.
Travel time messages can have one or two DMS One or two DMS phases
phases.
SunGuide shall ensure that travel time links shall TVT links greater than zero
be greater than zero.
The Toll Tag reader function shall report and archive average speed in miles per hour and travel Units for archived toll tag data
time calculations (not raw data) in terms of seconds.
Travel time computations shall use speed values Speed values greater than zero
greater than zero (0).
The Travel Time function shall have the ability to dynamically resolve missing travel speed reports (when they are single individual links but not for Dynamically resolve missing multiple contiguous links, along a given segment) reports
based on data that can logically be used to determine roadway link travel speeds.
Travel times for drive‐time comparisons
TVT
2
TVT
3
TVT
3
TVT
4
TVT
4
TVT
4
TVT
4
141
FEAT18.1.8
TM006T2
SunGuide shall utilize the following meta‐rules and apply them in sequence to dynamically resolve missing link data: (1) If only partial link data is available, then use existing link data to Meta‐rules to resolve missing extract a travel time; (2) If all link data is not available, then utilize dynamic linking to link data
determine a travel time; and (3) If dynamic linking does not prove adequate or reliable, then use (as a last resort) a "no data available" condition.
FEAT18.1.9
TM007T
Automatic link report updates
FEAT18.1.10
TM008P
Monitor number of vehicles used for computations
FEAT18.1.11
TM009T2
Less than a minute latency for display
FEAT18.1.12
TM012T
Calculate delay time for each segment
FEAT18.1.13
TM012T1
Delay time calculation definition
Travel time report updating shall be fully automatic, without operator validation, unless a supervisor decides to suspend an event detection link travel time segment.
The SunGuide GUI shall monitor number of vehicles being used to compute travel times for each segment during the current and past 4 hour time periods and associate the number of vehicles with the segment.
The Travel Time calculations shall not add more than 1 minute of data latency prior to data being queued for display.
SunGuide shall calculate a delay time for each travel time segment based on the speed limit for the segment.
Delay time shall be calculated by subtracting free flow travel time from current travel time; where free flow travel time is link traversal time calculated using the speed limit, current travel time is link traversal time calculated using currently measured speeds while not exceeding the speed limit.
TVT
4
TSS
4
TVT
4
TVT
4
TVT
4
TVT
4
142
FEAT18.1.14
TM013D
FEAT18.1.15
FEAT18.2
FEAT18.2.1
TM002T
Archive travel time and speed SunGuide shall have the ability to archive all travel data
time and speed data for later use.
test
test
Configuration
SunGuide shall include a "Travel Time Message template” that is editable by operators with Travel time message template SunGuide Administrator privileges.
FEAT18.2.2
TM003T
Travel time message priority
FEAT18.2.3
TM017
Travel time link setup
FEAT18.2.4
UT012
FEAT18.2.5
TM002G
FEAT18.2.6
FEAT18.2.7
FEAT18.2.8
TM004T1
TM008G
TM008T1
Travel time messages shall have a SunGuide Administrator configurable priority that can be modified by operators with appropriate SunGuide privileges.
SunGuide shall provide an editor for each district to specify which links in their instrumented roadways will be used for travel time calculations.
It shall be possible to alter the initial 511 reporting segments.
The SunGuide operator shall have the ability to Ability to turn off travel time turn off the travel time messages to the DMS.
messages
Alter 511 segments
Different Travel Time link lengths shall be able to TVT link lengths for one or more be associated with one or more TSS links.
TSS links
The SunGuide Operator shall have the ability to specify an upper bound for the travel time and a Specify upper and lower bounds lower bound for the travel time for each segment defined to have a travel time calculation.
Allow for multiple routes
SunGuide Travel Time function shall allow more than one route for an origin/destination pair to be configured by an operator that Travel Time will be computed for.
TVT
4
RR
TVT
4
2
TVT
2
TVT
2
TVT
2
TVT
3
TVT
4
TVT
4
TVT
4
TVT
4
143
FEAT18.2.9
TM010T
FEAT18.2.10
TM010T5
FEAT18.2.11
TM013T
FEAT18.2.12
TM013T1
FEAT18.3
FEAT18.3.1
TM001T
FEAT18.3.2
TM016
FEAT18.3.3
FEAT18.3.4
TM005T
TM005T1
The SunGuide Travel Time function shall require that for each segment defined that will have Lower/upper bound for each travel times calculated for it that there be a minimum travel time defined called a lower segment
bound and a maximum travel time defined called an upper bound.
The "lower bound," and "travel time upper Lower/upper bounds per bound" values shall be able to be defined reporting segment
separately for each travel time link segment.
SunGuide shall be able to create multiple travel time links from different data sources on the same roadway segment.
A travel time link shall be allowed to contain TSS TVT link may contain TSS links links of varied types (i.e., AVI, LPR, roadway of varied types
Sensor Types).
Generation
Travel time messages shall be automatically Generate travel time messages
generated.
Travel time computations shall be based on the Texas Department of Transportation TransGuide Travel time generation method
Travel Time computation method.
Multiple TVT links from different data sources
Group travel time tags
Insufficient data alert
SunGuide shall provide the ability to group the travel time tags in such a way that portions of the travel time message can be automatically removed if data is not available.
If insufficient data is available to calculate travel time then no travel time shall be provided to the DMS and the operator shall be alerted.
TVT
4
TVT
4
TVT
4
TVT
4
TVT
2
TVT
2
TVT
2
TVT
4
TVT
4
144
FEAT18.3.5
FEAT18.3.6
FEAT18.3.7
FEAT18.3.8
TM005T2
TM007P
TM009T1
TM010T4
FEAT18.3.9
TMT039
FEAT18.3.10
TMT0310
FEAT18.3.11
TMT040
FEAT18.4
When there are two or more travel links (a two phase TVT message) and there is insufficient data available to calculate one of the travel times, then Revert to single phase message
the message reverts to a single phase message exhibiting only one of the travel times.
Filter outlier travel times
Times computed on configurable interval
SunGuide shall have the ability to filter out travel times that are outside a normal distribution for the travel time for the segment. e.g., travel times/speeds that don't make sense given current conditions or are way in excess of the speed limit ‐ e.g., 120 mph).
Travel times shall be computed on an interval specified by a system configuration parameter (e.g., 1 minute, 2 minutes, 5 minutes, etc.).
If a DMS does not provide the ability to present a 3 line (row) message, the message will be Display of messages over 3 lines
displayed sequentially on the available rows.
The software shall accept a command from a user Enable/Disable Systemwide that will enable or disable travel time message generation on a system‐wide basis
The software shall accept a command from a user Enable/Disable for a single DMS that will enable or disable travel time message generation for a specified DMS
The software shall have a configuration parameter No Units
that will allow travel times to be posted to DMS without including the units.
Vehicle travel times
TVT
4
TVT
4
TVT
4
TVT
4
TVT
6
TVT
6
TVT
6
TVT
4
145
FEAT18.4.1
TM018
FEAT18.4.2
TM024
FEAT18.4.3
FEAT18.4.4
TM002P
TM009T
FEAT18.5
Accept data from toll tag readers
SunGuide shall accept data from toll tag readers and use that data to calculate the elapsed time of travel between the geographic location where the tag was initially read and the geographic location where the tag was read again.
SunGuide shall provide vehicle travel times and Travel times and delays with delays using probe vehicle technologies.
probe data
SunGuide shall have an algorithm to compute probe vehicle‐based travel times based on data Compute probe vehicle‐based received from probe vehicles or by road based travel times
sensors that track a probe vehicle.
Calculations from different detection technologies
SunGuide shall calculate travel times using data obtained from a combination of data from point‐
based and probe‐based detection technologies.
Alternate routes
FEAT18.5.1
TM003G
FEAT18.5.2
TM008T
FEAT18.5.3
TM008T2
The SunGuide operator shall be able to select Specify up to 2 diversion roads either a primary or a secondary alternative road for each EM location.
The SunGuide travel time process shall include the Compute travel times for capability of computing travel times for alternate alternate routes
routes and conditionally presenting the alternatives on DMSs.
Display of alternate route travel time messages Display of alternate routes
shall be based on the calculated travel times and current traffic conditions.
TVT
4
TVT
4
TVT
4
TVT
4
TVT
4
TVT
4
TVT
4
TVT
4
146
FEAT18.5.4
TM011T
Post diversion messages to signs
SunGuide shall automatically post alternate routes messages to operator specified dynamic message signs when the travel time savings on the alternative route exceeds an operator specified time in minutes. The default travel time savings shall be 10 minutes over the main route.
TVT
4
TVT
4
EMPM
2
EMPM
2
EM
3
EMPM
2
Diversion messages shall be formatted into one of the two following templates. SunGuide shall attempt to use the first substitution, if that does not fit on a selected sign attempt the second. If that does not fit, then it should not make any alternate route message substitutions. FEAT18.5.5
TM011T1
Diversion message template Line 1: TO <Destination> format
Line 2: VIA <Alternate Route> Line 3: <Distance> <Travel Time>
or Line 1: TO <Destination>
Line 2: VIA <Alternate Route> <Distance>
Line 3: <Travel Time>
Event Management / Performance Measures (EM/PM)
GUI
FEAT19
FEAT19.1
FEAT19.1.1
EM001G
FEAT19.1.2
EM001G1
The Event Manager tabular screen shall be User interface for new event opened automatically upon operator login based records
on operator preferences.
The EM/PM GUI shall open automatically Opening GUI automatically whenever the operator completes a log in to SunGuide.
147
FEAT19.1.3
EM001G2
FEAT19.1.4
EM003G2
FEAT19.1.5
EM003R
FEAT19.1.6
EM003R1
FEAT19.1.7
EM003R2
FEAT19.1.8
EM007G
FEAT19.1.9
EM007G1
FEAT19.1.10
EM007G2
FEAT19.1.11
EM011G
SunGuide map GUI screen shall open and be ready Opening screens within 60 for use within 60 seconds from when the seconds
SunGuide URL is selected exclusive of operator log‐
in process.
The EM Subsystem GUI element shall represent unresolved events differently than; unconfirmed Represent unresolved events events, active with lane blockage events, and differently
active without lane blockage events on the display.
Support editing for PM data The SunGuide PM subsystem shall support data fields
editing.
Changes to the data shall be able to be made in Data entry form editing
the data entry form and in the data editing component.
It shall be possible to edit agency timeline data in Agency timeline data
real‐time using the data entry form.
The SunGuide GUI component shall provide a Graphical lane blockage data graphical display to the operator, allowing lane blockage information to be entered using point‐
entry
and‐click methods.
The SunGuide GUI element shall use predefined lane mappings to determine the number of lanes, Predefined lane mappings
shoulders, and exit ramp lanes to display to the operator.
The SunGuide GUI element shall allow the operator to change the lane configuration (i.e. number of lanes, shoulders, exit ramp lanes) at Changing lane configuration
the event location. Changes shall only apply to the current event (the lane mapping adjustments shall not be saved).
The SunGuide GUI shall have a free text field for Free text fields for event each event record that the operator can enter records
comments.
GUI
3
EM
3
RS
3
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
148
FEAT19.1.12
EM011G1
FEAT19.1.13
EM017G1
FEAT19.1.14
EM017G2
FEAT19.1.15
EM017G3
Maximum of 512 ASCII characters
The free text field shall accommodate a maximum of 512 ASCII characters.
The SunGuide GUI shall use a popup alert to Popup alerts for blocked CCTVs remind the operator that one or more CCTV are blocked at the video switch subsystem.
The popup alert shall be visible to all operators logged on to the SunGuide system.
Visible popup alerts
Confirming blocked camera alerts
FEAT19.1.16
EM017G4
Unblocking blocked cameras
FEAT19.1.17
TM006W
Interface to annotate an incident record
FEAT19.2
FEAT19.2.1
The popup alert shall remain visible on the SunGuide operator's display until at least one operator confirms the blocked camera status by clicking on a button on the popup that will cause the popup to disappear for a configurable amount of time after which it will reassert itself until an operator again acknowledges it.
The SunGuide GUI shall allow any operator with appropriate permissions to unblock a blocked camera.
SunGuide graphical operator interface shall provide the ability for the operator to annotate an incident record with date/time information related to incident management and performance measures calculation.
Reports
EM001R
Weekly and monthly reports
The Performance Measures subsystems reporting component shall generate weekly, monthly, quarterly and yearly reports, providing both summary and detailed performance measures when requested by a manager.
EM
3
GUI
3
GUI
3
GUI
3
GUI
3
EM
3
EMPM
2
RS
3
149
EM001R1
Based on Cambridge Systematics' final report
FEAT19.2.3
EM001R2
Daily chronology report of incidents
FEAT19.2.4
EM002R
Viewable report within 30 seconds
FEAT19.2.2
FEAT19.2.5
EM001D2
FEAT19.2.6
EM001P
FEAT19.2.7
TM004D
FEAT19.2.8
TM005D
FEAT19.2.9
TM007D
The performance measures compiled shall be based on the FDOT Office of Traffic Operations Refinement of Florida Statewide Operations Performance Measures and Data Collection Methodology, May 2006.
The PM reporting component shall be able to generate a daily chronology report of incidents based on time and day parameters entered by the operator.
The SunGuide PM subsystem shall be able to generate a report and display it on the operator’s screen within 30 seconds of the last key stroke command that requests the report.
The SunGuide GUI element shall provide a link to Viewing reports for events with view a report on an event that had an associated associated tag data vehicle license tag.
The performance measures component shall Generating statistics and generate statistics and reports based on data reports
entered via SunGuide data entry screens.
SunGuide shall support the compilation and report generation weekly, monthly, quarterly and annually.
SunGuide shall store the road ranger data for a minimum of 12 months and have it available for Minimum of 12 months road review and report generation within 120 seconds ranger data
of when a specific piece of data is requested.
Support quarterly report generation
SunGuide shall calculate and be able to display Calculate, display, and export and export TMC performance measures.
TMC performance measures
RS
3
RS
3
RS
3
EM
3
RS
3
RS
3
RS
3
RS
3
150
FEAT19.2.10
TM006W4
FEAT19.3
The SunGuide Graphical User Interface shall allow a SunGuide operator with appropriate Calculating average response permissions to specify the date/time period or the incident IDs or range of IDs for SunGuide to time
calculate the average response time.
Manage events
FEAT19.3.1
EM002G
FEAT19.3.2
EM002G1
FEAT19.3.3
EM003G
FEAT19.3.4
EM003G1
FEAT19.3.5
EM003G3
FEAT19.3.6
EM004G
FEAT19.3.7
EM004G1
FEAT19.3.8
EM005G
FEAT19.3.9
EM006G
The EM/PM GUI component shall allow an Specify event verification
operator to specify that the event has been verified.
At the time an event is created in SunGuide, the Current time as verification current time shall be recorded by the EM time
subsystem as the notification time.
The EM subsystem shall allow an operator to Specify event status
specify the status of the event.
Status shall include that the event is unresolved indicating passive management, such as waiting Unresolved event status
for debris cleanup on the shoulder or towing an abandoned vehicle.
The EM Subsystem GUI element shall allow an Specify event closure
operator to specify when an event has been closed.
The EM GUI component shall allow an operator to Specify false/invalid information specify that the information provided was false and the record is voided.
Records flagged as invalid shall not be deleted by Records flagged as invalid
the database element.
The SunGuide GUI component shall allow an Specify events as 'false alarm' operator to specify that the event was a 'false alarm'.
The SunGuide GUI component shall allow an Lane blockage data
operator to enter lane blockage data for any event.
EM
3
EMPM
2
EMPM
2
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
151
FEAT19.3.10
EM006G1
FEAT19.3.11
EM008G
FEAT19.3.12
EM010G
FEAT19.3.13
EM012G
FEAT19.3.14
EM012G1
FEAT19.3.15
EM013G
FEAT19.3.16
EM014G
FEAT19.3.17
EM015G
FEAT19.3.18
EM016G
FEAT19.3.19
EM009G
Timestamps for lane blockage All lane blockage entries shall be recorded with entries
timestamps by the database element.
The SunGuide GUI component shall allow an operator to enter at least 10 vehicle descriptions Multiple vehicle descriptions for any event, with the following descriptive data: make, model, color, state, and tag.
The SunGuide GUI component shall allow an Event types from predefined list operator to select the event type from a predefined list for each event record.
The EM/PM GUI component shall allow the Specifying event location operator to specify the location of an event, using graphically
a graphical interface.
Events shall be geo‐located using latitude and Micro‐degrees event longitude coordinates in micro‐degrees.
coordinates
Specifying event data
The SunGuide GUI component shall allow the operator to specify the event: county, roadway, direction, relation to exit, nearest exit, and distance to exit, lane configuration.
The SunGuide GUI component shall allow the Point location along roadway operator to define a point location along a roadway.
The SunGuide GUI component shall allow the operator to specify congestion queues for an Congestion queues
event, using a similar interface as is used to define the event location.
The SunGuide GUI component shall allow the Weather conditions
operator to specify weather conditions for the event.
The SunGuide GUI component shall provide an Alerts for license plate matches alert message to the operator if an event record matches a license plate number.
EM
3
EM
3
EM
3
EMPM
2
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
152
FEAT19.3.20
EM003
FEAT19.3.21
EM002D
FEAT19.3.22
EM017G
FEAT19.3.23
EM017G5
FEAT19.3.24
EM005T
FEAT19.3.25
FEAT19.3.26
FEAT19.3.27
EM005T1
EM005T2
EM007T1
The EM subsystem shall be able to record free‐
Recording free‐text comments text comments entered by the operator.
The operator entered free text comments shall be Storing free text comments in stored in the database associated with the related database
event.
An operator with appropriate permissions shall be able to command the SunGuide to block one or Blocking video camera displays
more video camera displays through the video switch subsystem.
There shall be no timeout feature to unblock the Manually unblocking cameras cameras; the camera must be unblocked manually by an operator.
The tracking component shall allow an operator to identify an agency that was notified and enter a timestamp indicating when an agency has been Identifying and notifying first notified about an event or has detected an agencies
event and three more date/time fields for repeated notifications.
The operator shall be able to indicate whether it Indicate if TMC notified agency was the TMC that notified a specific agency.
Entering responder times
Tracking queue lengths
For agencies that are configured as responders (FHP, Fire, etc.) SunGuide shall allow the operator to enter the time when they arrived on‐scene, and the time when they departed.
SunGuide 2.2 shall be able to track queue lengths based on operator data entry being driven by CCTV images or VDS detector data.
EM
3
EM
3
GUI
3
GUI
3
EM
3
EM
3
EM
3
EMPM
2
153
FEAT19.3.28
EM005
FEAT19.3.29
EM006
The PM subsystem shall automatically enter the notification time, on‐scene time, and departure time for the road ranger agency.
The EM subsystem shall record DMS message status changes from the DMS and MAS modules Recording DMS message status and maintain a log of posted message changes changes
and the timestamp of the changes.
Notification, on‐scene, and departure times
FEAT19.3.30
EM007
Email alerts for event subscribers
FEAT19.3.31
EM001E
Email template
FEAT19.3.32
FEAT19.3.33
EM002E
EM003E
The EM subsystem shall allow operators to send email alerts to subscribers with summary information about an event.
The EM subsystem E‐mail component shall create the e‐mail template with at least the following information: a subject, event type, event location, lane blockage and last status date and time.
The SunGuide E‐mail component shall allow the Entering free‐text changes to operator to enter free‐text changes to the email.
emails
Pre‐defined email groups
FEAT19.3.34
EM008
Entering sensitive email information
FEAT19.3.35
EM002P
Logging audit changes
The SunGuide E‐mail component shall allow the operator to choose from one or more pre‐defined email groups for sending e‐mails.
The SunGuide shall provide a mechanism through which the system and operator may enter "sensitive" information that shall only be sent to a pre‐defined and privileged group of subscribers using E‐mail.
All audit changes shall be logged in the system, including the previous values, the operator who changed them, and the date/time it was changed.
RS
3
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
154
FEAT19.3.36
TM005B
FEAT19.3.37
TM005B1
FEAT19.3.38
TM005B3
FEAT19.3.39
TM005B5
FEAT19.4
FEAT19.4.1
EM013G1
FEAT19.4.2
EM003D
FEAT19.4.3
EM006T
FEAT19.4.4
EM009
FEAT19.5
FEAT19.5.1
EM002
FEAT19.5.2
EM001D
SunGuide shall support the creation or Creation/modification of an modification of an incident by a standalone incident by standalone software
software module (the EM/PM Subsystems).
SunGuide shall identify the incident as having Identification of incident been created or changed by the EM/PM created by EM/PM
Subsystems.
Possible incidents detected through SunGuide TSS TSS dectected incidents shown shall show up in the EM/PM GUI.
in EM/PM
An event created or modified by the EM/PM Event owner as person logged Subsystems shall identify the owner as the person into RRPM module
logged into the RRPM module that created or changed the incident.
Data synchronization
Any lane configuration changes in any data entry Display of lane configuration screen will be reflected in any other data entry changes
screen that display lane configuration.
The EM/PM event records shall be synchronized with IM event records.
The EM/PM data entry screens shall populate IM EM/PM data populates IM data
data entry screens.
The EM/PM subsystems shall synchronize its Synchronizing event data via IM event data with the IM subsystem using the ICD
SunGuide Incident Manager Subsystem ICD.
Synchronizing event records
System
SunGuide Oracle database access
The SunGuide Oracle database shall support Event Manager functions.
When a vehicle license plate number is entered, the Event Manager database component shall Vehicle license plate numbers search the database to look for an event record with a matching tag number.
EMPM
2
EMPM
2
EMPM
2
EMPM
2
EMPM
2
EM
3
EMPM
2
EMPM
2
EMPM
2
EMPM
2
EM
3
EM
3
155
FEAT19.5.3
EM006T1
FEAT19.6
Road ranger vehicles
FEAT19.6.1
EM004
FEAT19.6.2
EM001T
FEAT19.6.3
FEAT19.6.4
FEAT19.6.5
FEAT19.6.6
EM/PM subsystem shall calculate Calculating latitude/longitude latitude/longitude coordinates in the background coordinates
and provide them to the IM subsystem.
EM002T
EM003T
EM004T
EM004T1
The EM subsystem shall allow an operator to track Tracking status of road ranger the status of each road ranger vehicle (truck) in vehicles
the fleet.
The EM tracking component shall track road ranger vehicle status conditions that shall include as a minimum: patrolling, assist‐motorist, meal, Minimum vehicle status inspection, out of service, Base, Assist FHP, Assist conditions
Other Road Ranger, Mechanical.
Billable/non‐billable and available/unavailable status
The EM tracking component shall automatically track the billable/non‐billable and available/unavailable for dispatch status of a truck based on its current status.
The EM tracking component shall allow the Changing radio number, beat, operator to change the status, radio number, and driver status
beat, and driver for any given truck.
The EM tracking component shall allow the operator to record when a specific road ranger truck was dispatched to an event, arrived on‐
Recording truck dispatch data
scene to an event, departed from an event, or had their dispatch order cancelled.
Responding to same event multiple times
A road ranger vehicle may respond to the same event multiple times, and each response shall have its own notification/arrival/departure/cancel times.
EMPM
2
EMPM
2
RR
3
RR
3
RR
3
RR
3
RR
3
EM
3
156
FEAT19.6.7
EM004T2
FEAT19.6.8
TM001D
FEAT19.6.9
TM002D
The EM tracking element shall allow an operator to record activities performed, along with Recording performed activities
timestamps for each activity, for each road ranger response on‐scene.
SunGuide shall acquire and store the following data that is collected at the beginning of the Road Ranger Service Patrol Vehicle Operator's shift:
A.Date
B.Shift start time
C.Operator name
Storing Road Ranger data to D.Truck number
support report generation
E.Route
F.Beginning vehicle mileage
This data shall be available to support the generation of reports concerning Road Ranger operations.
Data collected at each stop
The following data collected at each stop shall be stored by SunGuide and made available for report generation and reviewing through the SunGuide GUI:
A.Dispatch time
B.Arrival time
C.License number
D.State
E.Vehicle type
F.Direction of travel (NB, SB, EB, WB)
G.Mile marker
H.How discovered
I.Lanes/Shoulder blocked
J.Cause for stop
K.Services provided
L.Depart time
M.Comment card (Y/N)
EM
3
RR
3
EM
3
157
FEAT19.6.10
TM002D1
FEAT19.6.11
TM002D2
FEAT19.6.12
TM002D3
The following data collected about the vehicle type at each stop shall be stored and linked to the road ranger report containing the data:
a.Passenger
b.Pickup or van
Vehicle type data collected at c.RV or bus
each stop
d.Single‐unit truck
e.Tractor trailer
f.Motorcycle
g.Not Applicable (N/A)
The following data collected by the Road Ranger about how it was discovered at each stop shall be stored and linked to the road ranger report containing the data:
Data collected when Road a.Drive up
Ranger discovers event
b.Saw and changed route
c.Road Ranger dispatch
d.FHP dispatch/officer
e.Other
The following data collected about the cause for the stop shall be stored and linked to the road ranger report containing the data::
a.Accident (crash) include FHP Crash Number
b.Vehicle fire Data collected about the cause c.Disabled
for the stop
d.Abandoned
e.Debris
f.Other
EM
3
EM
3
EM
3
158
FEAT19.6.13
FEAT19.6.14
FEAT19.6.15
TM002D4
TM002D5
TM003D
The list of services that were provided at each stop shall be stored and linked to the road ranger report containing some of the following data:
a.Extinguish fire
b.Absorbent
c.Remove debris
d.Relocate (to safer location)
e.Tire
f.Fuel
g.Fluids
h.Mechanical
Services provided at each stop i.Jump start
j.Called wrecker
k.Secure Load
l.Mobile phone call
m.Directions
n.Transported
o.Blocked lane/traffic control
p.Tagged abandoned vehicle
u.Other ‐ describe
v.No service ‐ occupied
w.No service ‐ abandoned
Data collected at the end of each road ranger shift
Road ranger operator data collected monthly
The following data collected at the end of each road ranger shift shall be stored by SunGuide and linked to the road ranger reporting the data.
A.Shift end time
B.Ending vehicle mileage
The road ranger operator data shall be collected weekly and monthly and be able to be exported to Microsoft Excel or other compatible format.
EM
3
RR
3
RS
3
159
FEAT19.6.16
TM006D
FEAT19.6.17
TM012D
FEAT19.6.18
TM012D1
FEAT19.6.19
TM019
FEAT19.6.20
S032
FEAT19.6.21
TM006W6
FEAT19.7
FEAT19.7.1
TM009D
FEAT19.7.2
TM009D1
SunGuide shall interface with and be able to receive road ranger data using a file or document that is in XML format.
SunGuide shall provide a driver to interface with Driver interface with service different service vehicle collection data streams in vehicle collection data streams accordance with published SunGuide Interface Control Documents.
SunGuide shall provide a driver to interface with the Xplore’s iX104C2 tablet PC through a local area connection (LAN) to upload performance Driver for D4 RR PC Tablet ICD
measures data recorded by the device in accordance with the District 4 RR PC Tablet Interface Control Document.
SunGuide shall support an interface with a Interface to D4 RR data software subsystem that will interface with collection equipment
District 4 road ranger data collection equipment.
Receive road ranger data in XML
The SunGuide software shall support the Performance measures data performance measures data collection of Road collection
Rangers Service Patrols.
Service patrol data downloaded after the event shall not overwrite the operator entered Downloaded service patrol data
date/time for road ranger initial notification but shall fill in any missing data.
Performance measures
SunGuide shall calculate and save the Response Calculate and save incident Time for each incident confirmed by the SunGuide response time
operator.
The date and time that law enforcement or road Recording date and time upon ranger service was initially notified of a confirmed initial notification
SunGuide incident shall be recorded and associated with the incident.
RS
3
RR
3
RR
3
RR
3
RS
3
EM
3
EMPM
2
EM
3
EM
3
160
FEAT19.7.3
FEAT19.7.4
TM009D2
TM009D3
Recording arrival time
Response time calculation
FEAT19.7.5
TM009D4
Average response time
FEAT19.7.6
TM010D
Incident clearance time
FEAT19.7.7
TM010D1
Date and time when traffic lanes are cleared
FEAT19.7.8
FEAT19.7.9
TM010D2
TM010D3
Incident clearance time calculation
For each incident confirmed by the SunGuide operator, the arrival time of law enforcement or the road ranger vehicle shall be recorded and associated with the incident.
SunGuide shall calculate the Response Time for each confirmed incident by subtracting the date/time of initial SunGuide notification of the incident from the date/time that law enforcement or road ranger arrives on scene. Response Timeincident ID = tLE/RR Arrives ‐ tinitialnotification.
SunGuide shall calculate the Average Response Time for a period of time or for a group of incidents specified by the SunGuide operator.
SunGuide shall calculate and save the Incident Clearance time for each incident confirmed by the SunGuide operator .
The date and time when the SunGuide operator decides that all traffic lanes are cleared shall be recorded and associated with the incident.
SunGuide shall calculate the Incident Clearance Time (ICT) by subtracting the date/time that law enforcement or road ranger vehicle arrive on scene from the time that the lanes are cleared. ICT = tlanescleared ‐ tLE/RR Arrives
SunGuide shall calculate the Average Incident Clearance Time for a period of time or for a group Average incident clearance time
of incidents specified by the SunGuide operator.
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
161
FEAT19.7.10
TM006W1
FEAT19.7.11
TM006W2
FEAT19.7.12
FEAT19.7.13
TM006W3
TM006W5
FEAT19.8
FEAT19.8.1
FEAT20
SunGuide graphical operator interface shall provide the ability for the operator to enter the date and time that law enforcement or road Entering initial notification time ranger was notified of a confirmed SunGuide incident and by what agency by name. This is called Initial Incident Notification Time (tinitialnotification).
The initial notification time for road ranger service Initial notification time shall be associated with each incident if the data is associated with incidents
available from the road ranger service.
Entering arrival time
Entering lanes cleared time
SunGuide graphical operator interface shall provide the ability for the operator to enter the date and time that a law enforcement or road ranger vehicle arrived on the scene of a SunGuide confirmed incident. This is called the Arrival Time of Law Enforcement/Road Ranger vehicle (tLE/RR Arrives).
The SunGuide Graphical User Interface shall allow a SunGuide operator with appropriate permissions to specify the date/time that all traffic lanes resumed free flow operation following the confirmation of an incident by the SunGuide operator. This is called "tlanescleared".
General
EM001
Road ranger performance measures module
Scheduled Action System (SAS)
The SunGuide software shall include a road ranger performance measures module that interfaces with District service patrol data collection and reporting devices.
EM
3
EM
3
EM
3
EM
3
EMPM
2
RS
3
SAS
2.2.2
162
FEAT20.4
SAS004
Travel Time Message Scheduling
FEAT20.4.1
SAS004A
Scope of Enable/Disable
FEAT20.5
SAS005
Schedules
FEAT20.5.1
SAS005A
Schedule Parameters
The software shall allow the scheduling of the enabling and disabling of travel time messages.
The travel time message scheduling shall allow for the invocation of a disable travel times messaging command and an enable travel times messaging command on a per DMS basis as well as a system wide basis.
The software shall allow the user to schedule a series of predefined actions within the system.
The schedule shall have the following parameters:
1. The start and end time of the schedule shall be a date and time of day
2. The default value of the start time shall be the clock time ending in 0 or 30 minutes immediately after the current system time and the end time will default to one hour after the start time
3. When the start time is adjusted, the end time shall preserve the current duration of the event
4. The duration shall be displayed as a non‐
editable value near the end time
5. An all day event button shall be displayed near the start time and when clicked shall set the start time to 12:00:00 AM and the end time to 11:59:59 PM
6. The schedule shall allow the user to select the days on the week the schedule should execute when the schedule is active.
SAS
6
SAS
6
SAS
6
SAS
6
163
FEAT20.6
SAS006
Sequences
FEAT20.6.1
SAS006A
Available Camera Actions
The software shall allow for sequences, or a set of actions, to be configured within the schedule configuration
The software shall support the following actions against a user selected camera: pan for a user specified amount of time, tilt for a user specified amount of time, zoom for a user specified amount of time, and move to a user specified preset.
The software shall support the following actions for travel time message generation:
Available options for travel time 1. Enabling or disabling travel time message generation for a single DMS
scheduling
2. Enabling or disabling travel time message generation for all DMS signs
The software shall support an action of invoking Enable/Disable Schedule within an enable command and a disable command on a a Schedule
user selected schedule, not including the schedule itself
The software shall support an action of pausing Pausing schedule during for a specified number of hours, minutes and execution of next item
seconds before performing the next action.
FEAT20.6.2
SAS006B
FEAT20.6.3
SAS006C
FEAT20.6.4
SAS006D
FEAT20.7
SAS007
Schedule Naming
FEAT20.7.1
SAS007A
Unique Name
FEAT20.7.2
SAS007B
Storing Schedule Name
FEAT20.7.3
SAS007C
Default Name
The software shall allow the user to specify a name for the schedule
The name shall be required to be unique
The name shall be able to be modified and not be used as a primary key
The name shall initially default to "New Schedule"
SAS
6
SAS
6
SAS
6
SAS
6
SAS
6
SAS
6
SAS
6
SAS
6
SAS
6
164
FEAT20.7.3.1
SAS007C1
If default name is in use
FEAT20.8
SAS008
Schedule Copying
FEAT20.8.1
SAS008A
Copied Schedule Default Naming
FEAT20.8.1.1
SAS008A1
If default name is in use
FEAT20.9
SAS009
Enable/Disable Schedule
FEAT21
Ramp Meter Firmware (RMF)
FEAT21.1
General
FEAT21.1.1
TM021
Provide ramp metering firmware
FEAT21.1.2
TM001H
Model 170 equipment FEAT21.1.3
TM002H
68HC11 processor
FEAT21.1.4
TM003H
Controller firmware support
If the name "New Schedule" is in use, a space and the number one or the next available whole number will be appending to the default schedule name in order to make the name unique
The software shall allow the user to copy a schedule from an existing schedule
The name shall default to the exiting schedule's name appended with a space and the text "Copy"
If the default name is in use, a space and the number one or the next available whole number will be appending to the default schedule name in order to make the name unique
The software shall allow the schedule to be enabled or disabled by the user
SAS
6
SAS
6
SAS
6
SAS
6
SAS
6
RMF
RMF
The SunGuide system shall provide a ramp metering firmware for controlling traffic flow onto a roadway from an on‐ramp.
The Ramp Meter controller firmware shall control equipment consisting of standard transportation management hardware equivalent to the Model 170 controller.
The Ramp Meter controller firmware shall be developed for the 68HC11 processor.
The Ramp Meter controller firmware shall support Model 170 controller keypad, LED display, indicators, communications input and output functionality.
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
165
FEAT21.1.5
FEAT21.1.6
TM001C
The Ramp Meter controller shall provide standardized communications that conform to the Standardized communications WSDOT ramp metering protocol as described in "170 Communications Protocol:VAX‐170‐DOC05".
TM001O
Common access keypad
FEAT21.1.7
TM004O
WsDOT firmware implementation
FEAT21.1.8
TM001L
Surveillance functions
FEAT21.1.9
TM002L
Meter traffic flow
FEAT21.2
The Ramp Meter controller front panel shall provide controller metering and data collection status in a manner consistent with the WsDOT Firmware implementation.
The Ramp Meter controller shall provide Surveillance functions.
The Ramp Meter controller shall meter traffic flow.
Configuration
FEAT21.2.1
TM002C
FEAT21.2.2
TM002O
FEAT21.2.3
TM005O
FEAT21.2.4
TM002L1
FEAT21.3
FEAT21.3.1
The Ramp Meter controller shall allow use of a common access keypad for manual access to firmware parameters and controller operation.
Data collection and RM algorithms
RMF 1
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
RMF
The source for input to the Ramp Meter controller Input source
shall be configurable.
Pre‐defined configurable The Ramp Meter controller shall accept pre‐
parameters
defined configurable firmware parameters.
The Ramp Meter controller shall provide a Clock and calendar function manually configurable Clock and calendar function.
The Ramp Meter controller shall meter a Configurable number of lanes configurable number of lanes up to three lanes.
Firmware parameters
TM002O1
RMF
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
RMF
Firmware parameters shall be utilized for data collection and ramp metering algorithms.
RMF
RMF 1
166
FEAT21.3.2
TM003O
The Ramp Meter controller shall allow firmware Downloaded or manually set parameters to be downloaded from a central parameters system or manually input from the keypad.
FEAT21.4
Controller mode
FEAT21.4.1
TM001L1
Data collection surveillance services
FEAT21.4.2
TM002L2
Local or central command modes
FEAT21.4.3
TM002L3
Local mode operation
FEAT21.4.4
TM002L4
Central command mode
FEAT21.4.5
TM003L
Local mode implementation
FEAT21.4.6
TM004L
Metering rates
FEAT21.4.7
TM005L
Central command mode operation
FEAT21.4.8
TM006L
Ramp meter controller
FEAT22
FEAT22.1
Event Viewer (EV)
General
RMF
RMF 1
RMF
The Ramp Meter controller shall provide data collection surveillance services in a local mode.
The Ramp Meter controller shall operate in a local or central command mode.
The Ramp Meter controller local mode shall operate based on local traffic conditions and firmware parameters consistent with the WsDOT implementation.
The Ramp Meter controller central command mode shall operate based on algorithms defined by the central system.
The Ramp Meter controller metering algorithms shall be defined for local mode consistent with the WsDOT firmware implementation.
While in central mode, the Ramp Meter controller shall implement the metering rates sent from the SunGuide software.
The Ramp Meter controller shall allow for manual starting, stopping and modifying the metering from central command.
The Ramp Meter controller shall meter in local mode when active and disconnected from central command.
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
RMF
RMF 1
EV
EV
3
3
167
FEAT22.1.1
FEAT22.1.2
SV001
SV001B
FEAT22.1.3
SV002B
FEAT22.1.4
SV004
FEAT22.1.5
SV005
Limited restricted data to authorized users
The SunGuide Event Viewer Web site shall not display identified sensitive data to restricted users (e.g. license plate information, crash data, etc).
Event Viewer web site access
Secure access to the SunGuide Event Viewer Web site shall be through the SunGuide Web site.
The SunGuide Event Viewer Web site shall be Web site accessible through accessible through at least the following browsers
browsers: Internet Explorer 6 and 7, Firefox, Opera, Netscape, and AOL.
The SunGuide Event Viewer Web site session shall Session termination
only be terminated through the use of a logout button.
The SunGuide Event Viewer Web site shall make SunGuide data available for access within 30 Data availability
seconds of when it was entered into SunGuide.
FEAT22.1.6
SV006
Refresh intervals
FEAT22.1.7
SV001E2
Inactive period
FEAT22.1.8
SV007E
Web site refresh
FEAT22.1.9
SV008
Operator accounts
FEAT22.2
Security
The SunGuide Event Viewer Web site shall refresh automatically at a system configurable interval, with the default set to 60 seconds.
This recently inactive period shall be configurable, with 30 minutes set as the system default.
The SunGuide Event Viewer Web site shall take no more than 2 seconds to refresh the "event list" or "event details" pages.
An administrative application shall be provided to set‐up operator accounts for the SunGuide Event Viewer Web page application.
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
168
FEAT22.2.1
SV002
Cryptographic protocol FEAT22.2.2
SV001S
Authenticate based on IP address
FEAT22.2.3
SV002S
Operator accounts
FEAT22.2.4
SV003
Operator access
FEAT22.3
The SunGuide Event Viewer Web site shall be secure employing the Secure Sockets Layer cryptographic protocol or the Transport Layer Security cryptographic protocol.
The SunGuide Event Viewer Web site shall be capable of authenticating operators based on their originating IP address.
Passwords associated with the operator accounts shall be stored in an encrypted format.
The SunGuide Event Viewer Web site shall prompt the operator for a username and password to gain access to the application.
Event list
FEAT22.3.1
SV007
Web site opening page
FEAT22.3.2
SV001E1
Inactive events
FEAT22.3.3
SV001E
Event list sections
FEAT22.3.4
SV002E
Active events
The opening page after secure login of the SunGuide Event Viewer Web Site shall be an event list page.
The recently inactive events section shall display all the events that were active in the recent past that is a configurable amount of time.
The "event list" page shall have three sections: active events with a lane blockage, active events without a lane blockage, and recently inactive events.
The active events section shall display the following information: Record Number / Identifier, the login name of the operator managing the event, creation timestamp, road rangers dispatched and on‐scene, event type, location description, and description of blocked lanes.
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
169
FEAT22.3.5
SV003E
Inactive events information
FEAT22.3.6
SV004E
Event list page
FEAT22.3.7
SV005E
Event list record
FEAT22.4
FEAT22.4.1
FEAT22.4.2
The inactive events section shall display the following information: Record Number / Identifier, the login name of the operator managing the event, creation timestamp, road rangers dispatched and on‐scene, event type, location description, and current status (unresolved, closed, voided, etc.)
Each section of the events list page shall use a different background color to easily differentiate the lists.
For each event list record, the operator shall have the ability to select the record and view the "Event Details" page.
Event details
SV005E1
SV005E2
Event viewer web site
Event details page
The SunGuide Event Viewer Web site shall provide an "Event Details" page that will display details about a specific event record.
The "event details" page shall display the following information if available: event record number / identifier, current event status, record creation time, TMC managing the event, notifying agency, ID of the primary event if the current record is a secondary event, event type, hazmat, fire, rollover, injuries, a list of vehicles involved including color/make/model/state and tag, estimated clearance time, alternate roads, event location, event congestion, lane blockage description, and roadway conditions.
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
170
FEAT22.4.3
FEAT22.4.4
SV005E3
SV005E4
Road ranger information
The "event details" page shall display agency response information if available, including the name of the agency, whether or not they were Agency response information
notified by the TMC, and the notification, on‐
scene, and departed timestamps.
FEAT22.4.5
SV005E5
Chronology summary
FEAT22.4.6
SV006E
Navigation link
FEAT22.5
SV008E
Primary event association
FEAT22.5.2
SV008E1
Secondary event link
FEAT23
Incident Detection System (IDS)
FEAT23.1
CitiLog data
FEAT23.2
The "event details" page shall include a chronology summary section, that will display in chronological order the status, responder, road ranger, location, blockage, congestion, and DMS usage data entries.
A navigation link to the "event list" page shall be provided on the "event details" page.
Secondary Events
FEAT22.5.1
FEAT23.1.1
The "event details" page shall display road ranger related information if available that at a minimum includes if available an indication that road ranger was dispatched, on‐scene arrival time, departure time, and activities performed.
TD008
Display traffic data
Alert notification
Secondary events shall be associated with a primary event.
A secondary event shall have a link to the "event details" screen of the primary event that the secondary event is associated with.
SunGuide shall be able to log and display traffic data collected by CitiLog Video Detection Equipment devices.
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
EV
3
IDS
3
IDS
3
IDS
3
IDS
3
171
FEAT23.2.1
TD013D
Alert notification
FEAT23.2.2
TM007D7
Alarm/incident log
FEAT23.2.3
SB001
Safety Barrier Alerts
FEAT23.2.3.1
SB001A
Alert Triggered
FEAT23.2.3.2
SB001B
Alert information
FEAT23.2.3.3
SB001C
Alert resolution
FEAT23.2.3.4
SB001D
Safety Barrier Event Details
SunGuide shall supply alert notification for Safety Barrier Alerts indicating the Safety Barrier triggered.
The alert shall provide a control to access status information for the safety barrier reporting the alert.
The alert shall provide a method for the user to resolve the Safety Barrier Alert.
Events generated through this process shall be assigned a notifying contact specified in the system configuration, shall be assigned a default event type specified in the system configuration, and shall be assigned the nearest Event Management location to the configured safety barrier location.
Automatic Vehicle Location (AVL)
General
FEAT24
FEAT24.1
FEAT24.1.1
SunGuide shall supply alert notification for VisioPaD/Citilog data collected indicating the CCTV that detected the incident, and the timestamp when it was detected.
SunGuide shall log the time an alarm is generated by TSS or the operator elects to create a new incident.
SunGuide shall allow an operator to generate an event from a Safety Barrier alert.
AV006L
The source location of the AVL data source shall Source location configuration be configurable using the SunGuide Administration function.
IDS
3
IDS
3
IDS
5.1.1
IDS
5.1.1
IDS
5.1.1
IDS
5.1.1
IDS
5.1.1
AVL
3
AVL
3
AVL
3
172
FEAT24.1.3
AV004
Stored position data
FEAT24.1.4
AV009T
Maintaining position data
FEAT24.1.5
AV009T2
Logging location data
FEAT24.1.6
AV004T2
External reporting function
FEAT24.1.7
AV008
FEAT24.1.8
S034
FEAT24.2
FEAT24.2.1
EM018G
FEAT24.2.2
EM018G2
FEAT24.3
The AVL subsystem shall store vehicle position data by vehicle so that the vehicle's track can be replayed on the SunGuide map.
Chronological position data shall be maintained for each vehicle reporting position for a configurable number of days subject to data storage capacity on the hard disk(s).
All vehicle location status data received from the AVL subsystem shall be logged to the database for reporting purposes.
SunGuide shall make available the report data selected by the operator so that a reporting function external to SunGuide can generate the desired reports and print them.
Admin Editor functions shall be provided to allow administrators to add and remove vehicles from the AVL tracking system.
The SunGuide software shall support the acquisition of AVL data and the display of an AVL data displayed in icon form
analysis of the data in the form of icons on the SunGuide map.
Vehicle list
A Vehicle List window shall be provided that Tabular listing
displays a tabular listing of all the AVL‐enabled vehicles.
The tabular list shall include the following information for each vehicle: vehicle ID, status, List information
location, speed, driver, beat, stopped time, incident ID (if available).
Vehicle information
Adding/removing vehicles
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
173
FEAT24.3.1
FEAT24.3.2
AV001
AV004L
Position coordinates
Required information
FEAT24.3.3
AV002
Vehicle position display
FEAT24.3.4
AV009V
Vehicle map representation
FEAT24.3.5
AV003
Vehicle status display
FEAT24.3.6
AV006V1
Summary data information
FEAT24.3.7
AV007V
Vehicle status
The AVL subsystem shall acquire vehicle information containing position coordinates in XML format originated external to SunGuide.
As a minimum, the XML data file shall contain the following information: vehicle ID; latitude in decimal degrees; longitude in decimal degrees; vehicle heading; vehicle speed in mph; type of event vehicle is responding to; event data (classification) location the vehicle is traveling to; area of responsibility for the vehicle (zone ID or area ID); date‐time stamp.
The AVL subsystem shall display vehicle position for vehicles logged on using icons on the SunGuide Map.
Each vehicle shall be represented on the map with an icon, with the icon placed at the last reported geo‐coordinate location.
AVL subsystem shall display vehicle status that is provided by the AVL data feed.
The summary data shall consist of truck number, beat, driver, radio/telephone number, truck position (roadway, direction, reference location, proximity to reference location), speed and status (availability).
Vehicle status shall be provided to the extent provided by the received vehicle data file.
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
174
FEAT24.3.8
AV007V1
Vehicle status information
FEAT24.3.9
AV010V1
Minimum status values
FEAT24.3.10
AV010V2
FEAT24.3.11
AV011V2
Vehicle Status shall include at a minimum: vehicle ID, heading, speed, destination, event type, location in lat/long coordinates, stopped time, amount of time moving since last stop, and the last date‐timestamp that position data was received.
SunGuide shall support at a minimum the following four vehicle status values: patrolling, dispatched, assisting, and out‐of‐service.
SunGuide shall allow at least four values to be defined for "Availability Status".
The Detailed Vehicle Status window shall display the following information about the most recently selected AVL vehicle icon: Vehicle ID, speed, heading, location, status, stopped time, amount of time moving since last stop, operator, beat, nearest reference location (milepost), distance to Displayed vehicle information
nearest reference location, and, if available, the following information about the incident the vehicle is responding to: Incident ID, incident severity, incident type, incident description.
Defined values
FEAT24.3.12
AV002T4
Vehicle stop time
FEAT24.3.13
AV002T5
Vehicle moving time
FEAT24.3.14
AV009T3
Logging related data
If vehicle is stopped, displayed status data shall include the amount of time that the truck has been stopped.
If vehicle is moving, displayed status data shall include the amount of time that the truck has been moving.
The following related data shall be logged, if available: Beat, Driver, reference location, proximity to reference location, status, responding incident ID.
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
175
FEAT24.3.15
AV008T
Storing location and history
FEAT24.3.16
AV009
New status updates
FEAT24.3.17
AV007T
Non‐active status icon
FEAT24.3.18
AV002T6
Historical position tracks
FEAT24.3.19
AV002T7
Hide track display
FEAT24.4
FEAT24.4.1
FEAT24.4.2
FEAT24.4.3
The AVL subsystem shall store vehicle location and speed history in the SunGuide Oracle database.
The AVL subsystem shall update the vehicle status each time a new status is reported for the vehicle.
If a non‐active status (gas, meal, inspection, etc.) is received in the AVL feed, the AVL icon shall remain normal.
Historical vehicle positions (tracks) shall be indicated by "+" symbols or similar leading away from the current vehicle position.
There shall be an option to hide track display that applies to the track of the vehicle.
Data acquisition component
AV001L
AV002L
AV003L
Data file
Vehicle position
Data format
The AVL data acquisition component shall be able to acquire a data file in XML format either from a URL or in a shared directory or by FTP pull.
If multiple files are acquired containing more than one position for a vehicle, the acquisition component shall order the position reports by vehicle chronologically so the most currently reported position is last in the list.
If necessary, the acquisition component shall format the received data in accordance with the AVL Data Interface Specification.
AVL
3
AVL
3
AVL
3
AVL
4
AVL
4
AVL
3
AVL
3
AVL
3
AVL
3
176
FEAT24.4.4
AV004L1
FEAT24.5
Geocoordinate reporting
Interfaces
FEAT24.5.1
AV001L1
Tablet application
FEAT24.5.2
AV001L2
PC tablet devices
FEAT24.6
The AVL subsystem shall interface with the road ranger tablet application developed by District 4, and use the reported status as an input in decision points where required.
The AVL system shall be compatible with the PC tablet devices used by the District 4 road ranger tablet application.
Position reports
FEAT24.6.1
AV004L2
Corrected reports
FEAT24.6.2
AV005L
Updates
FEAT24.6.3
AV003V
Vehicle icon
FEAT24.6.5
AV007V2
No reported data
FEAT24.6.6
AV014A
Bulk Updates
FEAT24.7
Geocoordinates are expected to be reported to 3 decimal places at a minimum, if they are not, the acquisition component shall locate the closest road to the reported position and fill in the coordinates accordingly.
Geospatial data
Position reports that are corrected by SunGuide shall be flagged in the data log and indicated to the operator.
The icon status and position shall be updated upon receipt of new data.
The icon assigned by the administrator shall be used to represent vehicles for which position reports are received.
When there is no data in the position or status report for a particular field, a blank for the missing field will be displayed.
AVL shall log vehicle positions messages sent in bulk directly to the database without generating updates to the Operator Map.
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
6
AVL
3
177
FEAT24.7.1
AV007L2
FEAT24.8
Coordinate conversion
Historical track
FEAT24.8.1
AV002T
Display of past positions
FEAT24.8.2
AV002T1
Trail feature enabling
FEAT24.8.3
AV002T2
Display track feature
FEAT24.8.4
AV002T3
Vehicle speed
FEAT24.8.5
AV003T1
Replay options
FEAT24.8.6
AV003T2
Replay rates
FEAT24.8.7
AV003T3
Deleting historical tracks
FEAT24.9
The AVL subsystem shall convert Latitude and Longitude coordinates into a text description of the Road the vehicle is on and if within 50 yards of a cross street, provide the name of the cross street as well.
Geo‐fences
The operator shall be able to turn on a "breadcrumb trail" display on the main SunGuide map which displays a system wide configurable number of past positions of the vehicle.
It shall be possible to enable and disable the trail feature on a per‐vehicle basis.
If the operator leaves "display track" on for a particular vehicle, the number of symbols representing the track shall follow the vehicle's position on the map with the oldest track symbol being erased as the next to current one is displayed.
If a vehicle speed is "stopped" or "0", no more than one track icon shall be displayed.
The operator may designate a vehicle ID, a span of time in date and time, and a replay rate when replaying vehicle track information.
The operator may select to replay the vehicle's position in real time or faster than real time at a rate specified by the operator.
The operator shall have the ability to delete from the display all of the historical tracks for a particular vehicle.
AVL
3
AVL
3
AVL
4.2
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
AVL
3
178
FEAT24.9.1
AV011
Manage assets
FEAT24.9.2
AV001V
Managing contract responsibilities
FEAT24.9.3
AV001V1
Leaving area notification
FEAT24.9.4
AV012V1
Specified beat
FEAT24.9.5
AV013V
Defining geo‐fences
FEAT24.10
AV014B
FEAT24.11
AV014C
FEAT25
FEAT25.1
FEAT25.1.1
DF200F
The AVL subsystem shall provide the capability to manage road ranger assets according to geographic areas that define their patrol areas called geo‐fences.
SunGuide AVL subsystem shall support management of road ranger contract responsibilities through geo‐fences using the SunGuide map and vehicle position reports.
If a vehicle leaves the Geo‐fenced area without justification, the system shall provide a visual notification to the operator
If a vehicle is assigned to a beat which has beat‐
specific geo‐fences defined, then the AVL system shall use only the geo‐fences for the specified beat to assess whether or not a given vehicle has left its beat zone.
The AVL system shall provide a Graphical User Interface to define the geo‐fences, both system wide geo‐fences and beat specific geo‐fences.
The RRXML driver will support a method for Bulk Update for RRXML Driver sending multiple position updates as a single request.
The software shall log stop alerts and geofence Logging Alerts
alerts including operator responses to the database
511
General
SunGuide shall have the ability to manage a minimum of 100 Central Florida 511 reporting Reporting routes
routes and 150 FIHS 511 reporting routes.
AVL
3
AVL
3
AVL
4.2
AVL
3
AVL
3
AVL
6
AVL
6
511
511
3
3
511
3
179
FEAT25.1.2
DF204R6
Changes
FEAT25.1.3
DF208R
Editing summations
FEAT25.1.5
ID207G
Adding new roads
FEAT25.1.6
ID228
Adding reporting segments
FEAT25.1.7
ID210G
Map of routes
FEAT25.1.8
ID203
Voice recording formats
FEAT25.1.9
ID201V
CF and FIHS recordings
Changes to any portion of a Link Report, Link Summary, or Drive‐Time Summary shall cause a new composite file to be sent to the 511 telephone system.
The SunGuide shall allow editing a Reporting Segment's logical segment summations.
If the newly added or modified locations exist on a road that was not originally listed in the FIHS and Central Florida 511 routes, then the SunGuide shall automatically add the new road to the 511 route list and inform the operator that it has done so.
Upon adding to or modifying 511 reporting segments, the SunGuide shall make available pre‐
recorded data on the new or modified 511 Reporting Segments within one minute after the system has been restarted.
The Operator Interface shall provide a map of the Central Florida area that visually depicts the 511 reporting routes.
All voice recordings, whether pre‐recorded or custom‐made, shall be recorded via SunGuide ‐
511 and stored in .WAV file format via the Operator Interface.
The SunGuide shall treat Central Florida 511 reporting roadways and FIHS 511 reporting roadways similarly, being able to provide one recording at any given time for both Central Florida 511 routes and for FIHS 511 routes.
511
3
511
3
511
3
511
3
511
3
511
3
511
3
180
FEAT25.1.10
ID201V1
FEAT25.2
Human voice messages
Scenarios
FEAT25.2.1
DF207
Data evaluation
FEAT25.2.2
ID205G
Display of scenarios
FEAT25.2.3
ID212G
Operator override messages
FEAT25.2.4
ID201
Scenario minimums
FEAT25.2.5
ID200V
Pre‐recorded file selection
FEAT25.2.6
ID206G1
Display event details
FEAT25.2.7
ID200V1
Definition of scenario
FEAT25.3
The system shall disseminate a recorded human voice that will report current traffic conditions using complete sentences.
.WAV files
SunGuide shall be able to evaluate data collected from both directions of travel as part of a single Scenario.
The Operator Interface shall display a list of current pre‐recorded Scenarios that can be selected and associated with a roadway segment or other FIHS defined facility.
At any time, an operator shall have the ability to disable reporting of the automatically selected scenario(s) for a 511 link report or link summary report and to record an "override" message using the Incident Link Report recording feature.
The SunGuide shall allow a minimum of 30 pre‐
recorded Scenarios for Central Florida 511 Reporting Segments.
When the SunGuide determines that the conditions fit a particular scenario, then the system shall select the pre‐recorded .WAV file associated with that scenario.
The 511 Operator Interface will display the event details that make the selected 511 Scenario appropriate.
A Scenario shall be defined as an unique combination of locations, delays and/or conditions for specific Central Florida limited‐
access or principal arterial roadways.
511
3
511
3
511
3
511
3
511
3
511
3
511
3
511
3
511
3
511
3
181
FEAT25.3.1
FEAT25.3.2
FEAT25.3.3
WS014
ID205G1
ID205G2
FEAT25.3.4
ID201G
FEAT25.3.5
ID202V
FEAT25.3.7
ID222
FEAT25.3.8
ID209G
Operator interface
Event report approval
The SunGuide Operator Interface shall be capable of recording and previewing .WAV files.
When an event report is entered or updated in SunGuide and associated with a pre‐recorded 511 scenario .WAV file, the SunGuide shall display the .WAV file text to the operator for review and approval before the .WAV file is sent to the 511 telephone system.
If the operator rejects the selected recording, the automatically selected scenario .wav files for the Option to record incident link reporting segment shall be disabled, and the operator shall have an option to record an report
Incident Link Report describing current conditions.
If no pre‐recorded .WAV file is associated with a given scenario, then the operator shall be alerted No pre‐recorded file
via the Operator Interface to record a message in a .WAV file format.
When the SunGuide selects a prerecorded Scenario for a given Reporting Segment, the Pre‐recorded scenario .WAV file associated .WAV file shall be shared with the Statewide 511‐telephone services, and therein associated with that 511 location.
The SunGuide's interface with the Statewide 511‐
telephone service shall adhere to an ICD for .WAV file sharing
sharing selected .WAV files that the 511‐
telephone services will use to report current road conditions.
SunGuide shall allow the SunGuide operator to record and preview wav files recorded for the 511 Operator wav files
system, whether pre‐recorded (canned) or custom‐made.
511
3
511
3
511
3
511
3
511
3
511
3
511
3
182
FEAT25.3.9
ID201V2
.WAV file selection
FEAT25.3.10
ID203G
Floodgate messages
FEAT25.3.11
ID203G1
Special floodgate message
FEAT25.3.12
ID203G4
FEAT25.3.13
ID203G5
FEAT25.3.14
ID204G
.WAV file availability
SunGuide shall provide selected .WAV files to the Statewide 511 service within one minute of their being recorded.
The Operator Interface shall provide the ability to add, remove, and preview Floodgate Messages (.WAV files).
SunGuide shall insert the floodgate voice recording into the 511 reports table of .WAV files, designating it as a special floodgate message.
If a .WAV file has been recorded by an operator using the Operator Interface, a second level of the 511‐telephone recording .WAV file hierarchy shall be available to the operator for the entry of a Special Floodgate Message relevant to a roadway facility, section of roadway facility, or specific 511 Reporting Segment.
The Operator Interface shall also provide the ability to add/modify, remove, and preview floodgate messages (.WAV files) relevant to an entire roadway facility (played to all users Operator interface abilities interested in 511 event reports along the facility). As described above, these messages will be played to appropriate users after they have selected the roadway in which they are interested.
A SunGuide operator with appropriate permissions shall be able to record a 511 Scenario Operator scenario recordings in a .WAV file format and associate the sound file with a 511 Reporting Segment.
511
3
511
3
511
3
511
3
511
3
511
3
183
FEAT25.3.15
FEAT25.3.16
ID204G1
ID204G2
FEAT25.4
FEAT25.4.1
Ability to listen
The SunGuide shall have the ability to manage at least 1000 pre‐recorded Scenario .WAV files.
The Operator Interface shall provide the ability to listen to the pre‐recorded .WAV file associated with the selected 511 Scenario.
Messages
DF206
FEAT25.4.2
ID202G
FEAT25.4.3
ID214G
FEAT25.4.4
Managing pre‐recorded scenarios
ID211G1
Traveler information
The traveler information contained in the 511 messages may include, but shall not be limited to: generalized conditions and/or traffic flows, travel time information, specific information about non‐
recurring events (accidents, constructions, etc.), and possible alternative route information (when appropriate). Speed reduction events shall not be carried on the 511 system.
The Operator Interface shall provide a list of selected 511 messages that the operator can Selected message availability
select from, as well as the "triggers" for each of these messages.
If an incident/event, significant weather condition, or any other abnormal traffic‐related conditions occurs on a particular FIHS 511 Operating recording prompts Reporting Segment then the operator shall be prompted via the Operator Interface to record a custom message for the reporting segment.
Operator messages
No message shall be associated with such a 511 Reporting Segment until the operator creates a message.
511
3
511
3
511
3
511
3
511
3
511
3
511
3
184
FEAT25.4.5
FEAT25.4.6
ID211G
ID215
Operator alerts
If an incident/event, significant weather condition, or any other abnormal traffic‐related conditions occurs on a particular Central Florida Operator outgoing recording 511 Reporting Segment Route, the operator shall prompts
be prompted via the Operator Interface to record a custom outgoing message.
FEAT25.4.7
ID200G
Override message ability
FEAT25.4.9
ID203G2
Maximum length
FEAT25.4.10
ID203V
Specially recorded messages
FEAT25.4.11
FEAT25.4.12
ID204G3
ID204G4
If no 511 scenario message is found and the SunGuide operator does not create either the appropriate pre‐recorded scenario message or a custom Incident Link Report message, SunGuide shall send additional alerts to operators until a message is recorded.
Indicating override messages
The operator interface shall provide the ability to disable reporting of automatically‐selected scenario messages, and to record "override" messages using the Incident Link Report recording feature.
The maximum length for an event report or WAV file shall be 60 seconds.
SunGuide shall replace the default message with a specially recorded message when it is available.
If a 511 Reporting Segment has been "overriden" by disabling reporting of automatically‐selected scenarios, the Operator Interface shall indicate that the 511 Scenario report has been disabled.
For 511 Reporting Segments with an "override" Incident Link Report message, the Operator Hear or read incident link report Interface shall provide the ability to either hear or read a text version of the Incident Link Report message.
511
3
511
3
511
3
511
3
511
3
511
3
511
3
185
FEAT25.4.13
ID206G
FEAT25.5
Display message name
Reports
FEAT25.5.1
DF200R4
Event reports
FEAT25.5.2
DF201R
Travel time reports
FEAT25.5.3
The 511 Operator Interface shall display the name of the message that is currently in use for each 511 Reporting Segment. Each of the 511 Reporting Segments shall display the name of the 511 message that is currently in use.
DF201R1
FEAT25.5.4
DF202R5
FEAT25.5.5
DF204R
FEAT25.5.6
DF204R2
Announcements
Travel time information shall be provided to the 511‐telephone services as event reports, when unusual conditions exist.
SunGuide shall generate three types of travel time reports for Central Florida roads covered by the 511 system: Link Reports, Link Summaries, and Drive‐Time Comparisons.
In Link Reports, travel times in the northbound or eastbound direction shall be announced first (depending on the bearing of the route), followed by the southbound or the westbound direction.
Point‐to‐Point travel time reports shall be pre‐
Pre‐recorded message storage recorded and stored in a library for selection by the SunGuide operator.
Incident Link Reports shall be utilized in the Link Reports and Link Summaries, but not Drive‐Time Utilization
Summaries.
Except for one "default" Incident Link reports per 511 reporting segment, operator‐recorded Incident Link Reports shall be saved for Management review
management review but shall not be "reusable" once they are removed from the 511 telephone system.
511
3
511
3
511
3
511
3
511
3
511
3
511
3
511
3
186
FEAT25.5.7
DF204R3
Optional inclusion
FEAT25.5.8
DF204R4
Creation
FEAT25.5.9
DF204R5
.WAV file creation
FEAT25.5.10
ID208G
Entering incidents
FEAT25.5.11
ID208G1
Reporting links
FEAT25.5.12
DF227
Link report breakdown
FEAT25.5.13
DF205R
Travel time inclusion
FEAT25.5.14
DF205R1
Road segments
FEAT25.5.15
DF205R2
Select roads
FEAT25.5.16
DF206R
Link summaries
Incident Link Reports shall be optionally included in the Central Florida 511 messages.
Upon operator approval, Incident Link Reports shall be created and sent to the 511 telephone system.
For each Link Report and Link Summary SunGuide shall assemble and fuse the applicable Incident Link Reports and travel time reports to create a single .WAV file for sending to the 511 telephone system.
When an incident that will be sent to the 511 telephone system is entered into SunGuide, operators shall be prompted to describe an Incident Link Report or update the Incident Link Report for the link in question.
There shall be only one associated Incident Link Report for each reporting link, describing all high‐
priority incidents in both directions of travel.
Roads in Central Florida shall be broken down into between one (e.g., SR 520) and four (e.g., I‐4) Link Reports for the purpose of reporting travel times.
Link Reports shall include travel times for both directions of traffic.
Link Reports shall have a mid point in the road segment for reporting travel times.
Link Reports for select roads designated by FDOT shall not have mid‐points.
Link summaries shall report current travel times for in one direction for links within central Florida that do not have midpoints.
511
3
511
3
511
3
511
3
511
3
511
3
511
3
511
3
511
3
511
3
187
FEAT25.5.17
DF206R1
No incident announcements
FEAT25.5.18
DF206R2
Announcement directions
FEAT25.5.19
DF207R
Up to 42 reports between 7 points
FEAT25.5.20
DF207R1
Select road reporting
FEAT25.5.22
DF207R3
FEAT25.5.24
ID202G1
FEAT25.6
If there are no incidents on the segment, Link Summaries shall be announced as follows:[Incident Link Report], Going [North | South | East | West],Estimated travel time from Start Point to End Point is X minutes.
For each road, Incident Link Reports shall be announced from south to north or from west to east. Note that each Incident Link Report describes incidents in both directions of travel.
There shall be up to 42 (forty‐two) Drive‐Time Comparison reports on the 511 system, between 7 configurable points (for example, between Downtown Orlando and the Orlando International Airport).
The Drive‐Time Comparison reports will report travel times on select roads in Central Florida.
A Drive‐Time Comparison report shall be announced as follows:
Current travel time on [Alternate Route 1 Description] to [Destination Point] is X minutes, Drive‐time comparison report On [Alternate Route 2 Description] to [Destination structure
Point]
is Y minutes, .... On [Alternate Route N Description] to [Destination Point] is Z minutes."
The pre‐recorded reports shall only contain Pre‐recorded report generalized conditions and/or traffic flows and information
travel times.
Drive‐time comparisons
511
3
511
3
511
3
511
3
511
3
511
3
511
3
188
FEAT25.6.1
DF226
Applicability
FEAT25.6.2
DF200R
Comparison report
FEAT25.6.3
DF200R1
Comparison information
FEAT25.6.4
ID213G
Drive time comparisons (presenting drive times for two or more routes between the same two points) shall apply only to Central Florida road segments.
A summary comparison report shall be able to compare a travel corridor, including multiple roadway links, and more than one roadway in the comparison.
Summary drive‐time comparisons shall include information concerning one direction of travel ‐ from a common origin (i.e. "From" point) to a common destination (i.e. "To" point).
The operator interface shall allow an operator with appropriate permissions to flag or other wise indicate whether travel time scenarios are to be Indicate availability of travel made available to the 511 telephone service for a time scenarios
Link Report, Link Summary, or Drive‐Time Comparison Route.
FEAT25.6.5
DF208R1
Configuration changes
FEAT25.6.6
ID224
Summary report minimums
FEAT25.6.7
DF200R2
Comparisons available with appropriate permissions
Only a system administrator with appropriate permissions shall have the ability to change the configuration to create, edit, or delete drive‐time comparison routes.
The SunGuide shall have the capability to provide reports on up to a minimum of 42 (forty‐two) drive‐time comparisons.
Summary drive‐time comparison and selected segments shall be available using the 511 telephone service as designated by the SunGuide operator with appropriate permissions.
511
3
511
3
511
3
511
3
511
3
511
3
511
3
189
FEAT25.6.8
DF201R5
FEAT25.7
FEAT25.7.1
FEAT25.7.2
FEAT25.7.3
Report times for alternate routes
Drive‐Time Comparisons(a.k.a drive‐time summaries, a.k.a summary drive‐time comparisons) shall report travel times for two or more alternate routes between a common origin (i.e. "From" point) to a common destination (i.e. "To" point) on multiple roadways.
Travel times
DF201R2
DF201R4
DF202R
Reporting increments
Changing messages
Report posting
All travel times reported on 511 shall be rounded to 5‐minute increments (e.g., 5 minutes, 10 minutes, 15 minutes) for reporting on 511.
Travel time messages shall not change until they cross the next five minute threshold for a minimum detection period, n (default = three) minutes. This shall ensure that the travel times do not change more than once per n minutes.
Travel time reports shall be formulated and posted automatically to the live 511 system, without operator intervention.
511
3
511
3
511
3
511
3
511
3
190
FEAT25.7.4
DF202R1
Upper Bound time
FEAT25.7.5
DF202R3
Unavailability messages
FEAT25.7.6
DF202R4
Automatic updates
FEAT25.7.7
DF205R3
No mid point no incident announcements
On all reports that include a travel time, an "upper bound" travel time shall be enforced. When the forecast average travel time exceeds the upper bound, the system shall continue to create travel times, but the travel time message shall indicate that estimated travel times are in excess of [upper bound travel time] minutes. For example:
Going [North | East],Estimated travel time from Route A to Route B is in excess of X minutes, Going [South | West], Estimated travel time from Route B to Route A is in excess of Y minutes.
When the travel time is unknown or unavailable, the system shall play a message announcing that no travel times are available for the segment in question.
Travel time reports shall always update themselves automatically as conditions change.
If a Link Report has a mid point and there are no incidents on the segment, travel times shall be announced as follows:
Going [North | East], Estimated travel time from Start Point to Mid Point is X minutes from Mid Point to End Point is Y minutes, Going [South | West], Estimated travel time from End Point to Mid Point is X minutes from Mid Point to Start Point is Y minutes.
511
3
511
3
511
3
511
3
191
FEAT25.7.8
DF205R4
Mid point no incident announcement
FEAT25.7.9
DF205R5
Mid point incident announcements
FEAT25.7.10
DF205R6
No mid point incident announcements
If a Link Report does not have a mid point and there are no incidents on the segment, travel times shall be announced as follows:
Going [North | East], Estimated travel time from Start Point to End Point is X minute. Going [South | West], Estimated travel time from End Point to Start Point is Y minutes.
If a Link Report has a mid point and there is one or more incidents on the segment, travel times shall be announced as follows.
[Incident Link Report]
Going [North | East],
Estimated travel time from Start Point to Mid Point is X minutes from Mid Point to End Point is Y minutes.
Going [South | West],
Estimated travel time from End Point to Mid Point is X minutes
from Mid Point to Start Point is Y minutes.
If a Link Report does not have a mid point and there is one or more incidents on the segment, travel times shall be announced as follows:
[Incident Link Report]
Going [North | East],
Estimated travel time from Start Point to End Point is X minutes Going [South | West],
Estimated travel time from End Point to Start Point is Y minutes.
511
3
511
3
511
3
192
FEAT25.7.11
DF202R2
FEAT26
FEAT26.1
FEAT26.1.1
FEAT26.1.2
Lower bound travel times
On all travel time reports, a "lower bound" travel time shall be enforced for each segment reported. No lower travel times shall be reported for that segment. If the current travel time falls short of the lower bound, then the lower bound shall be reported as the travel time for that segment.
Event Management (EM)
General
TM009W
EM006G2
Event entry screen
Lane designation
FEAT26.1.3
EM010G1
Change event type
FEAT26.1.4
EM007T
Track queue length
The SunGuide GUI incident management event entry screen shall provide a field for the operator to enter the ID of an event that is currently open or has been closed within the last hour that is considered to be a primary event causing the event being created or edited.
It shall be possible to designate a lane type as:
Mainlane
HOV
On Ramp
Off Ramp
On Off Lane
Shoulder
C/D
HOT (High Occupancy Toll).
Operator shall be able to change event type at any time and the change will be time and date stamped in database.
SunGuide shall be able to track queue lengths based on operator data entry being driven by CCTV images or VDS detector data.
511
3
EM
EM
3
3
EM
3
EM
3
EM
3
EM
3
193
FEAT26.1.5
WS004A
FEAT26.1.6
EM028
FEAT26.1.6.1
EM028A
FEAT26.1.6.2
EM028B
FEAT26.2
FEAT26.2.1
EM001D1
Operator permissions shall include a Quality Assurance category for operators designated to Quality assurance permissions
be able to edit data fields for quality control purposes.
Every EM locations shall have a configurable EM Location Publish Flag
setting indicating whether or not the location should be published.
When an event is placed at a location that cannot Not Publishable Notification in be published, the operator shall be notified
Event
When a response plan is created for an event that Not Publishable Notification in is assigned a location that cannot be published, Response Plan
the operator shall be notified
Manage events
SunGuide shall retain event information that had Retain information
an associated vehicle license tag.
EM
3
EM
5
GUI
5
GUI
5
EM
3
EM
3
194
FEAT26.2.2
FEAT26.2.3
FEAT26.2.4
EM004T3
EM005T3
AV007L
The tracking element shall allow the operator to indicate the following activities performed for each service call and the time performed:
a.Extinguish fire
b.Absorbent
c.Remove debris
d.Relocate (to safer location)
e.Tire
f.Fuel
g.Fluids
h.Mechanical
Indicating activities performed i.Jump start
j.Called wrecker
k.Secure load
l.Mobile phone call
m.Directions
n.Transported
o.Blocked lane/traffic control
p.Tagged abandoned vehicle
q.Other ‐ describe
r.No service ‐ occupied
s.No service ‐ abandoned
Agency personnel list
Vehicle dispatch
A drop down box or a pop‐up window shall be available that provides a list of agency personnel that is editable by an operator with appropriate permission to allow the SunGuide operator to select the name of the person they spoke with.
An operator shall be able to right‐click on a vehicle to dispatch it to a new or existing event.
EM
3
EM
3
EM
3
195
FEAT26.2.5
AV007L1
New events
FEAT26.2.6
EM030A
Construction Event Type
FEAT26.2.7
EM030B
Amber Alert Event Type
FEAT26.2.8
FEAT26.2.9
FEAT26.3
EM030C
EM030D
Leo Alert Event Type
Silver Alert Event Type
Incident data
FEAT26.3.1
EM005D
FEAT26.3.2
EM005D1
FEAT26.3.3
TM007D12
FEAT26.3.4
FEAT26.3.5
TM007D13
TM007D8
In the case of new events, the operator will be prompted to enter the required information for the new event.
EM shall have an event type of "Construction"
EM shall have an event type of "Amber Alert"
EM shall have an event type of "Leo Alert"
EM shall have an event type of "Silver Alert"
Incident data shall be received from mobile units and entered into the database.
Incident data shall include items such as types of Data inclusion
vehicles involved, assistances rendered, Method notified, etc.
SunGuide shall log the time when the first event participant is notified and subtract it from the Notification/confirmation logs
time the event was first confirmed.
Received/entered data
Time stamps
Event log
FEAT26.3.6
TM007D9
Calculated response time
FEAT26.3.7
TB001A
Amber alert
SunGuide shall time stamp whenever a participant is notified as indicated by the operator in the Event Participants Dialog menu selection.
SunGuide shall log the time an event was either confirmed or it was indicated to be a false alarm.
SunGuide shall calculate the response time for each event by subtracting the time an event was confirmed or indicated as false alarm from the time it was generated.
SunGuide shall provide an incident type called "Amber Alert" that will be associated with a DMS message template for the Amber Alert Message.
EM
3
EM
6
EM
6
EM
EM
EM
6
6
3
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
196
FEAT26.3.8
DF006F3
FEAT26.4
Location has optional city, county, and metro area
Lane configuration
FEAT26.4.1
EM007G3
Adding lanes
FEAT26.4.2
EM007G4
Editable sequence
FEAT26.5
TM007D10
Requests and activation
FEAT26.5.2
TM007D11
Confirmation/activation logs
FEAT26.5.3
TM005R12
Configure Response Plans
FEAT26.6
FEAT26.6.2
FEAT26.6.3
The SunGuide GUI shall allow the operator to add a lane anywhere in the existing lane configuration.
The sequence in which the lane types appear shall be editable by the operator.
Response plans
FEAT26.5.1
FEAT26.6.1
SunGuide Event Location shall include the optional entry of city, county and metro area.
SunGuide shall record the time a Response Plan was requested for an event and the time a response plan was activated for the event.
SunGuide shall log the time from when an event was confirmed to when a Response Plan was activated.
SunGuide shall provide the ability to edit, define, and remove predefined response plans
Responder audit
EM011
EM001U
EM020G1
Capability to edit data
Logging operator changes
Modify agency notification
The responder audit function shall provide the capability to add, delete, or edit responder agency timeline, vehicle response timeline, and responder activity data in the SunGuide database.
All operator changes shall be logged in the database for traceability, including the new value, previous value, the user who made the change, and the time the change was made.
The operator shall be able to add, delete, or edit agency notification, on‐scene, and departure times.
EM
4
EM
3
EM
3
EM
3
EM
3
EM
3
EM
3
EM
5
EM
3
EM
3
EM
3
EM
3
197
FEAT26.6.4
FEAT26.6.5
EM020G3
EM020G4
FEAT26.6.6
EM020G5
FEAT26.6.7
EM020G8
FEAT26.6.8
EM012
FEAT26.7
FEAT26.7.1
FEAT26.7.1.1
EM022G
FEAT26.7.1.2
EM022G1
FEAT26.7.1.3
EM022G2
Modify response records
Provide notification time
The operator shall be able to add, delete, or edit vehicle response records for agencies with responding vehicles (Road Ranger, SIRV, etc.).
The operator shall be required to provide the notification time and either the arrival and departure times or the cancellation time.
The operator shall be able to add, edit, and delete activity records associated with vehicle response Modify activity records
records.
The operator shall have the option to enter a Enter quantity for quantifiable quantity associated with an activity, such as gas, activity
when the activity is configured as "quantifiable".
Activities shall be classified in the software as quantifiable or not.
Describes the behavior of the EM event details Allow Congestion Cross Country dialog in restricting congestion head and tail Lines
locations to the same county as teh actual event location
Congestion Head
Rules for congestion head of an event
SunGuide shall allow an operator to configure the Configure congestion head
congestion head of an event.
SunGuide shall default the congestion head to be the event location (county, road, direction, Default Congestion Head
reference point, relationship to exit, offset).
Classify as quantifiable or not
Changes to congestion head
When an operator makes changes to the event location, SunGuide shall change the congestion head to match those changes.
EM
3
EM
3
EM
3
EM
3
EM
3
EM
4.3
EM
4.3
EM
4.3
EM
4.3
EM
4.3
198
FEAT26.7.1.4
EM022G3
Modify congestion head
FEAT26.7.1.6
EM022G4
Display upstream locations
FEAT26.7.2
Congestion Tail
FEAT26.7.2.1
EM023G
FEAT26.7.2.2
EM023G1
FEAT26.7.2.3
EM023G3
FEAT26.7.2.4
EM023G4
FEAT26.7.2.5
EM024G
FEAT26.7.2.6
EM025G
SunGuide shall allow an operator to modify the congestion head default value by selecting Reference Point, Location and offset to the location.
SunGuide shall display only those reference points and relationships to exit for congestion head which are "upstream" of those for event location
Rules for congestion tail of an event
SunGuide shall allow an operator to configure the Configure congestion tail congestion tail of an event.
SunGuide shall allow an operator to modify the Modify Congestion Tail Default congestion tail default value by selecting County, Value
Reference Point, Location and offset to the location.
SunGuide shall apply a default value for Default value for congestion tail congestion tail when the operator initially checks the congestion box.
SunGuide shall apply a default value for congestion tail when the congestion dialog is Default value based on open and the operator changes any event location congestion dialog
values. (Changes and change‐backs count as changes.)
When an operator initially selects the Default attributes for "congestion" box, SunGuide will default the congestion tail
County, Road, Direction values for the Congestion Tail.
Default value for congestion tail reference point and relationship to exit shall be the reference Default Value for congestion tail point and relationship to exit with the smallest reference point
sort value which matches the congestion tail values for county, roadway and direction.
EM
4.3
EM
4.3
EM
4.3
EM
4.3
EM
4.3
EM
4.3
EM
4.3
EM
4.3
EM
4.3
199
FEAT26.7.2.7
EM023G2
Congestion Tail configure roadway direction
SunGuide shall provide a configuration checkbox to enable (if selected) or disable (if not selected) and operator from changing the roadway direction in the congestion tail.
Display of referince points and relationships
FEAT26.7.3
FEAT26.7.3.1
EM027G
FEAT26.7.3.2
EM026G
If congestion head and congestion tail are in different counties, SunGuide shall display all Congestion head and tail in reference points and relationships to exit for different country
congestion tail which match congestion tail county, road and direction.
If congestion head and congestion tail are in the same county, SunGuide shall display only those Congestion head and tail in the reference points and relationships to exit for same county
congestion tail which are "upstream" of those for congestion head.
EM
4.3
EM
4.3
EM
4.3
EM
4.3
FEAT27
Response Plan Generator (RPG)
RPG
3
FEAT27.1
FEAT27.2
General
Response plan messages
RPG
RPG
3
3
RPG
3
RPG
3
FEAT27.2.1
TM005R2
FEAT27.2.2
TM005R7
When the operator selects a sign to add to an existing response plan, the Incident management subsystem shall automatically generate the Generate message for new sign
appropriate response plan message for the new sign relative to the location and details of the incident.
Each DMS message recommendation in the Message recommendation
response plan shall clearly indicate the DMS sign(s) to which the message applies.
200
FEAT27.2.3
TM005R8
Automatic Abbreviations
FEAT27.2.4
TM005R9
Proximity Wording
FEAT27.2.5
TM005R10
Populating Event Type
FEAT27.2.6
EM026
Abbreviating Messages
FEAT27.2.6.1
EM026A
Multi Word Abbreviations
FEAT27.2.6.2
EM026B
Abbreviation Priority Precedence
FEAT27.2.7
EM031A
Device Message Ownership
FEAT27.3
FEAT27.3.1
When evaluating abbreviation substitutions for a DMS message, EM shall replace any instances of the words "NORTHBOUND", "SOUTHBOUND", "EASTBOUND", and "WESTBOUND" with "NB", "SB", "EB", and "WB", respectively
When generating response plan messages based on a message template, if the proximity is "RAMPTO" or "RAMPFROM", EM shall populate the proximity field with "RAMP TO" or "RAMP FROM" respectively
When generating response plan messages based on a message template, EM shall populate an event type field using the Event Type Classification of the event's type, except where the event's type is "Crash", in which case EM shall populate the field as "CRASH"
The software shall support the abbreviation of phrases when automatically generating messages for a response plan
The software shall allow the user to configure a multiple word abbreviations
If two abbreviations have the same priority, abbreviations with multiple words shall take precedence over abbreviations consisting of a single word
If an operator activates a response plan, the operator shall be the owner of any device messages posted due to the response plan
Alert messaging
TM005R3
E‐mail alert
SunGuide response plan feature shall include e‐
mail alert messaging capabilities.
RPG
5.1
RPG
5.1
RPG
5.1
EM
6
EM
6
EM
6
EM
6
RPG
3
RPG
3
201
FEAT27.3.2
TM005R4
FEAT27.4
Editing alert messages
Response plans shall provide alert message content that can be edited by an operator with appropriate permissions to be sent to the recipients.
Message templates
FEAT27.4.1
TB001A1
FEAT27.4.2
TB001A2
The Amber Alert Message template shall contain fields for the operator to fill in for specific Template information
information related to the amber alerts such as vehicle make/model, vehicle color and license tag number.
When generating response plan messages based on a message template, EM shall populate a cross Response Plan uses Long Name street field using the long name of the reference point of the event's location head
FEAT27.4.3
EM032A
Amber Alert template
FEAT27.4.4
EM032B
Leo Alert Template
FEAT27.4.5
EM032C
Silver Alert Template
FEAT28
FEAT28.1
When configuring a device template or a default device template, the user shall be able to configure a template for events with the event type of "Amber Alert"
When configuring a device template or a default device template, the user shall be able to configure a template for events with the event type of "Leo Alert"
When configuring a device template or a default device template, the user shall be able to configure a template for events with the event type of "Silver Alert"
Reporting System (RS)
General
FEAT28.1.1
EM007R
Filters
FEAT28.1.2
EM009R
Saving reports
Reports shall be able to be filtered on any of the event properties.
SunGuide shall be able to save a report as a Microsoft Word document or an Excel spreadsheet or an PDF file.
RPG
3
RPG
3
RPG
3
RPG
5.1
EM
6
EM
6
EM
6
RS
RS
3
3
RS
3
RS
3
202
FEAT28.2
Performance measures
FEAT28.2.1
EM001P1
Generate statistics/reports
FEAT28.2.2
TM007D3
Supporting documents
The performance measures component shall generate statistics and reports based on HOV and HOT lane types.
As a minimum, the following information shall be maintained by the SunGuide software as supporting documentation for the Monthly Performance Measures Report: "Device Location "Device Number "Device Type "Manufacturer "Description of failure or issue "Date & Time Down "Date & Time Up "Uptime Percentage
RS
3
RS
3
RS
3
RS
3
RS
3
RS
3
Deviation request: Remove the requirement to collect manufacturer data for device of type: Ramp Meter, RWIS, and Safety Barrier.
FEAT28.2.3
TM008D
FEAT28.2.4
TM010D4
FEAT28.2.5
TM007D15
SunGuide calculated TMC performance measures Accessibility of calculations shall be accessible through the Center‐to‐Center interface.
SunGuide shall calculate the total incident duration time defined as the difference in time Definition for incident duration from when FDOT or FHP is notified until the travel time
lanes are cleared. and associate it with the incident.
SunGuide shall calculate and store a notification time performance measure for each event by Notification time calculation taking the time that the TMC was notified and subtracting from it the time the FHP or FDOT is notified.
203
FEAT28.2.6
TM007D16
Verification time calculation
FEAT28.2.7
TM017D
Rate of occurrence for secondary incidents
FEAT28.2.8
TM017D1
FEAT28.2.9
TM018D
FEAT28.2.10
TM018D1
FEAT28.2.11
TM018D2
FEAT28.2.12
TM018D3
SunGuide shall calculate and store a verification time performance measure for each event by subtracting the time when an incident is confirmed from the time when the TMC was notified.
SunGuide shall calculate the rate that secondary incidents occur over a date‐time period specified by the SunGuide operator for specified roadway segments or for the entire District.
The reduction in rate of secondary crashes performance measure shall be: Rate of Secondary Reduction in rate of secondary Crashes = (Number of Secondary Crashes for a Date‐Time period X 1,000,000) / (Total Vehicle crashes
Volume for a Date‐Time period X Road Segment Length in miles).
SunGuide shall track the primary way in which an incident was detected and associate that Track incident detection
information with the incident for performance measure reporting.
Detection methods to be recorded by SunGuide Recorded incident detection are: by surveillance camera (CCTV), speed methods
detector (by type), Road Ranger stop, FHP notification.
SunGuide shall be able to generate a report listing Report listing number of the number of incident detections by device type incident detections
over a SunGuide operator specified date‐time period.
SunGuide shall be able to sort the incidents by Sort incidents by severity level
level of incident severity.
RS
3
RS
3
RS
3
RS
3
RS
3
RS
3
RS
3
204
FEAT28.2.13
FEAT28.2.14
TM019D
TM019D1
FEAT28.3
Vehicle miles traveled calculation
For performance measures purposes, SunGuide shall calculate Vehicle Miles Traveled (VMT) expressed as million vehicle miles for any date‐
time period specified by the person requesting a performance measures report from SunGuide that deals with VMT.
For the volumes needed to calculate vehicle miles traveled (VMT) for presenting crash statistics, SunGuide shall use either TSO data provided in tabular form to calculate VMT or VMT shall be Data used for VMT calculations
calculated by SunGuide off‐line using the volume from detectors multiplied by the segment length.
Road ranger status report
FEAT28.3.1
EM004R
Capabilities
FEAT28.3.2
EM004R1
Date/time range
FEAT28.3.3
EM004R2
Retrieved data
FEAT28.3.4
EM004R3
Data filters
FEAT28.3.5
EM005R
Activity summary report
A Road Ranger Vehicle status report shall be capable of being produced using SunGuide data.
The Road Ranger Vehicle status report shall allow the operator to specify a date/time range to retrieve data to support the report.
The retrieved data shall list all activity for the Road Ranger Vehicle(s) for the selected date/ time range including; all stops, logon information (including driver name), and logoff information.
The Road Ranger Vehicle status data shall be able to be filtered by event type and/or disposition.
SunGuide shall provide data to support the generation of an activity summary report.
RS
3
RS
3
RS
3
RS
3
RS
3
RS
3
RS
3
RS
3
205
FEAT28.3.6
EM005R1
Track truck number
FEAT28.3.7
EM005R2
Activity summary data
FEAT28.3.8
EM005R3
Summary filters
FEAT28.3.9
EM002T2
FEAT28.4
FEAT28.5
FEAT28.5.1
FEAT28.7
The activity summary data shall contain the information necessary to summarize all activities for the given data range specified.
The activity summary data shall be able to be filtered by event type and/or disposition.
SunGuide shall be able to generate a report that summarizes beat coverage (truck‐hours) for any particular time range specified by the operator.
Truck location report
Camera usage report
EM008R
FEAT28.6
FEAT28.6.1
Beat coverage summary
The operator shall be able to select a specific truck number or all trucks, and a date/time range to retrieve the necessary data to generate the activity summary report.
TM007D1
SunGuide shall be able to create a Camera Usage Usage report for camera locks report to show when cameras were locked and by whom.
Device status report
The system shall keep track of equipment as available from the SunGuide Software ICD (NTCIP protocol, etc.) ‐ downtime and uptime of ITS equipment that includes:
Tracking equipment
CCTVs;
DMSs;
Non‐intrusive detectors; and
RWIS
Traffic flow monthly report
RS
3
RS
3
RS
3
RS
3
RS
RS
3
3
RS
3
RS
3
RS
3
RS
3
206
FEAT28.7.1
TM007D5
FEAT28.8
FEAT28.8.1
FEAT28.9
FEAT28.10
Collected data
SunGuide software shall collect the following data to support the generation of the Traffic Flow Monthly Report:
o Average speed ‐ the average speed of vehicles passing through each detection zone in 15 minute increments.
o Average volume ‐ the average number of vehicles. o Average occupancy ‐ the average percentage of time, during the sample period, that the detector sensed a vehicle. o Average density ‐ the average number of vehicles that occupy one mile of road space.
Software reliability
TM007D2
Tracking
Traveler information
Incident management
SunGuide shall track software reliability including at a minimum downtime, uptime, and upgrade/repair time of ITS software for the following software systems:
Central Computer system
RS
3
RS
3
RS
3
RS
RS
3
3
207
FEAT28.10.1
TM007D6
FEAT28.11
FEAT28.11.1
Monthly report information
Position reports
AV005
Time line reports
SunGuide shall collect the following data to support the generation of the Incident Management Monthly Report:
o Total number of incidents by county, by roadway segment and level (i.e., Traffic Impact Levels ‐ Level 1, 2 & 3 Incidents). o Total number of incidents by county, by notifying agency. o Incident detection method ‐ system by which the RTMC was notified. o Total incident duration ‐ incident duration is the time between when an incident occurs and when traffic returns to normal flow. The following component time increments of incident duration shall be graphically depicted: ‐RTMC detection time ‐RTMC verification time ‐RTMC response time ‐Incident clearance time period ‐Traffic queue clearance time o Number of secondary incidents. o Road Ranger dispatch time period ‐ the difference between initial RTMC notification and when a Road Ranger is contacted for dispatch to an incident. o Road Ranger response time period ‐ the difference between when a Road Ranger is d
h d d h
h
d
The AVL subsystem shall support the generation of a report about vehicle position time line with vehicle status information that was associated with the date‐time of each position report.
RS
3
EV
3
RS
3
208
FEAT28.11.2
AV004T
Designating information
FEAT28.11.3
AV004T1
Sorting data
FEAT28.11.4
AV005T
Displaying reports
FEAT28.11.5
AV005T1
Saving report formats
FEAT28.11.6
AV005T2
Report options
FEAT28.11.7
AV006T
Retrieving data
FEAT28.11.8
AV006T1
Identification criteria
FEAT28.12
FEAT28.12.1
The operator shall be able to designate a vehicle or a group of vehicles and enter a date‐time and time span that position reports are generated for.
SunGuide shall provide the option for the operator to:
‐ Sort report data by vehicle or by area of operation or by date and time period.
‐ Filter report data by event type or event data codes.
Position reports shall be displayed on the SunGuide workstation when requested by the operator.
The operator shall have the option to save the report format thereby preserving the order in which the data is grouped to use as a template for future reports.
The operator shall have the option to save, delete or export a report.
The reporting function shall retrieve AVL data based on a date/time range and a particular vehicle.
At a minimum the identification criteria shall be able to be identified as: truck number, beat, driver, radio/telephone number, truck position (roadway, direction, reference location, proximity to reference location), speed and status (availability).
Chronology report
EM002U
Display operator changes
All operator changes shall be displayed in the chronology report with an indication that specific information has been changed.
RS
3
RS
3
RS
3
RS
3
RS
3
RS
3
RS
3
RS
3
RS
3
209
FEAT28.12.2
EM003U
FEAT28.13
Report for viewing changes
ODS reports
RS
3
Content format for display
Viewing of all archived data page content shall be formatted to fit a traditional display.
RS
3
RR
RR
3
3
RR
3
RR
3
RR
3
RR
3
RR
3
RR
3
OD002R
FEAT29.1.2
Road Ranger (RR)
General
TM001D1
EM002T1
FEAT29.2
FEAT29.2.1
Radio/district data
Assigning beats to trucks
SunGuide shall attach the Radio Number and District number to the data that is collected at the beginning of the Road Ranger Service Patrol Vehicle Operator's shift.
SunGuide shall provide the ability for an operator to assign a beat on an in‐service truck.
Road Ranger status
EM004D
3
Report drop down lists
FEAT28.13.2
FEAT29.1.1
ODS
3
Report content and format
FEAT29
FEAT29.1
3
RS
OD001R
OD007R
RS
The content and format of these reports shall be coordinated with FDOT.
Users shall be able to select one of the standard reports to view/extract via drop down lists.
FEAT28.13.1
FEAT28.13.3
The operator shall be able to run a report using the SunGuide report function to review changes made and logged by the audit function.
Mobile unit data
FEAT29.2.2
EM004D1
Data items
FEAT29.2.3
EM008T
Road Ranger vehicle status
Event data from mobile units shall be received and automatically stored in the database.
Event data shall be items such as Enroute, At Scene, Cleared Scene, On Break, Assisting Others, etc.
TMC Operators shall be able to change road ranger vehicle status.
210
FEAT29.2.4
AV010
FEAT29.3
FEAT29.3.1
Stopped vehicles
Drivers
TM001V
FEAT29.4
Driver interface
SunGuide shall provide a driver to interface with different service vehicle collection data streams in accordance with published SunGuide Interface Control Documents.
AVL/RR Interface
System shall be able to determine likely Determine comm‐related data duplicated data during audit which was caused by duplication
communications loss, then recovery.
FEAT29.4.1
AV018
FEAT29.4.2
AV020
Initiate incidents
FEAT29.4.3
AV020M
Close incidents initiated by unit
FEAT29.4.4
AV020M1
Depart incidents and leave unresolved
FEAT29.4.5
AV009T4
Data collected for involved vehicle
FEAT29.4.6
If a driver is stopped for a configurable length of time without accounting for the stop the system shall notify the operator.
AV006V2
Vehicle summary data
Mobile operator shall be able to initiate incident.
Mobile operator shall be able to close incident which was initiated by that unit.
Mobile operator shall be able to depart incident and leave it unresolved in SunGuide (i.e., abandoned vehicles).
Data for an involved vehicle shall include: color, make, model, license state, and license tag.
The AVL software shall provide summary data when an operator "mouses‐over" the vehicle icon. The summary data shall consist of truck number, beat, driver, adio/telephone number, truck position (roadway, direction, reference location, proximity to reference location), speed and status (availability).
RR
3
RR
3
RR
3
RR
4
RR
4
RR
4
RR
4
RR
4
RR
4
RR
4
211
FEAT29.4.7
AV007L5
Dispatch vehicle to new or existing event
FEAT29.4.8
AV017
Road ranger position data
FEAT29.4.9
AV005T3
Display list of trucks and status
FEAT29.4.10
AV005T4
Truck activity report
FEAT29.4.11
FEAT29.4.12
AV005T5
AV005T6
Activity summary report
Location report information
An operator shall be able to right‐click on a vehicle to dispatch it to a new or existing event. In the case of new events, the operator will be prompted to enter the required information for the new event.
The list of Road Rangers, part of the EM GUI, shall be augmented to include current truck position (roadway, direction, reference location, proximity to reference location), speed and status (availability) from the AVL software. A "Find on map" option will be provided from the list, which will 'zoom' the SunGuide map to the current position of the vehicle icon.
A list of currently logged on trucks and their current dispatch status shall be displayed.
A Road Ranger Activity Report shall be available. This report shall list all activities for a road ranger for a given date and time range. The report shall be filterable by truck number (or all), event types, road ranger activities and Driver ID
A Road Ranger Activity Summary report shall be available. This report shall summarize all activity for a given date and time range. The report shall be filterable by truck number (or all), event types, road ranger activity and Driver ID
A Location report shall be available. This report shall list each GPS update for a given date and time, and the geo‐referenced location for that report. It shall be filterable by truck (or all), and Driver ID.
RR
4
RR
4
RR
4
RR
4.2
RR
4.2
RR
4
212
FEAT29.4.12.1
AV005T7
Location report column headings
FEAT29.4.13
AV019
Change unit status
FEAT30
FEAT30.1
Variable Speed Limit (VSL)
General
FEAT30.1.1
DM006
Manage VSL signs
FEAT30.1.2
DM003V
Monitor roadway conditions
FEAT30.1.3
FEAT30.1.4
Roadway and location long name shall both be displayed in the Location column header of the "Vehicle GPS Location Report."
TMC Operators shall be able to change unit status in the event of mobile electronics or communications malfunction.
DM004V
DM005V
Interfacing with DMS
Implementation of recommendation
FEAT30.1.5
DM007V
Log posted VSL data
FEAT30.1.6
VSLXXX
Turn VSL beacons on and off
FEAT30.2
FEAT30.2.1
TM005R8
Recommendations
Recommendation logs
SunGuide shall be able to manage Variable Speed limit (VSL) signs.
SunGuide shall continuously monitor roadway conditions and require changed conditions to be present for a user‐selectable period before making a recommendation.
SunGuide VSL functionality shall interface and communicate with existing DMS control software.
Only a SunGuide operator with appropriate permissions can authorize the implementation of a VSL reduced speed limit recommendation resulting in a reduction of the posted speed limit on VSL signs.
The DMS log file (i.e. the system log file) shall list each newly posted speed limit, the corresponding variable speed limit sign(s) involved, and a time/date timestamp.
SunGuide shall allow an operator to turn VSL beacons on and off.
All VSL recommendations shall be logged.
RR
4.2
RR
4
VSL
VSL
3
3
VSL
3
VSL
3
VSL
3
VSL
3
VSL
3
VSL
4
VSL
VSL
3
3
213
FEAT30.2.2
DM001V
Speed limit values
FEAT30.2.3
DM001V1
Alert to recommend changes
FEAT30.2.4
DM001V2
FEAT30.2.5
DM001V3
FEAT30.2.6
DM002V
FEAT30.2.7
DM005V1
FEAT30.2.8
DM005V2
SunGuide shall provide Variable Speed Limit (VSL) software to recommend speed limit values for I‐4 segments furnished with Variable Speed Limit signs.
SunGuide shall alert the operator in order to recommend changes in speed limit values for each of the 22 VSL signs deployed as part of the I‐
4 VSL Trial within one minute of determining changes are necessary.
SunGuide shall log all recommended changes in speed limit.
Recommended speed limit values shall be Determining speed limit values determined using real‐time information available in SunGuide.
SunGuide shall be able to alert the operator to recommend changes to the VSL within one Alert operator
minute of determining that such a change is needed.
Recommended speed limit values to be stored in Storing recommended values the SunGuide VSL application shall be specified by the FDOT.
Speed limit recommendations shall be made available to operators within two minutes of Recommendations available to reduced speed limit criteria having been met and operator
require acknowledgement.
Speed limit changes
VSL
3
VSL
3
VSL
3
VSL
3
VSL
3
VSL
3
VSL
3
FEAT31
Operational Data Store (ODS)
ODS
3
FEAT31.1
General
ODS
3
ODS
3
FEAT31.1.1
OD001
SunGuide shall accommodate 100% growth in the Accommodate growth in data amount of data being collected, archived, and collected
disseminated based on the size of the system at project initiation.
214
FEAT31.1.2
OD001D
Flexibility for data addition, reconfiguration, redefinition
FEAT31.1.3
OD001E
Generating error messages
FEAT31.1.4
OD007D
Data formats
FEAT31.1.5
OD003D
FEAT31.1.6
OD003
FEAT31.1.7
OD005
SunGuide shall be flexible to allow for the periodic addition, reconfiguration, or redefinition of data provided by the SunGuide, without the loss of current or past data.
The Direct Information Feed (Data Archive) shall be capable of generating error messages in cases where the data slated for delivery is currently unavailable.
Data available from the ODS via the Direct Information Feed shall be available in an ITS standards based XML or other commonly used and approved format, capable of being imported into an ITS products‐based application.
No degradation in data quality, accuracy, or granularity shall occur between reception of data Degradation in data quality
by the ODS and output of that data to licensed users.
The reporting function shall be capable of Accept data from data bus
accepting data from the SunGuide Data Bus.
SunGuide shall provide a Direct Information Feed Provide feed to external users using center‐to‐center to external users.
FEAT31.1.8
OD006
Forecast traffic volumes
FEAT31.1.9
OD008R
Data stored with timestamp
FEAT31.1.10
OD007
Use of master clock
SunGuide shall provide an on‐line capability to select and display a date/time range of archived traffic volumes in order to forecast traffic volumes with a growth factor.
The data processed by the ODS will be stored with a timestamp.
SunGuide Software shall use a Network Time Protocol Time Server as the system master clock to ensure uniform timestamps.
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
215
FEAT31.1.11
OD008
Availability for ODS
FEAT31.1.12
OD011
Preformatted reports
FEAT31.1.13
OD015
FEAT31.1.14
OD013
FEAT31.1.15
DW001
FEAT31.1.16
DW003D
The Direct Database Feed shall be available for use by the ODS at least 98% of the time measured annually, except for service disruptions beyond the Contractor's control, excluding scheduled maintenance, during any contiguous 365‐day period.
Users shall be able to view/extract archived data using fifteen (15) preformatted reports.
Travel times for instrumented The ODS shall include travel times for the roadways
instrumented roadways.
The ODS shall include data collection links and Include links and 511 segments
selected 511 reporting segments.
SunGuide data shall be provided to the Data provided via direct Operational Data Store using a direct database database connection
connection called a Direct Database Feed.
Interface Control Document specification
FEAT31.1.17
DW005D
Data structure capable of import into database
FEAT31.1.18
DW003
Error messages when SG is experiencing problems
FEAT31.1.19
DW005
No unintended data degradation
How to implement the Direct Database Feed shall be specified in an Interface Control Document.
The Direct Database Feed shall be available in a common data structure capable of being imported into a standard database product for use by the ODS.
In instances when SunGuide is experiencing problems, a message shall be provided to inform both the SunGuide operator and the SunGuide error log that the system is not currently operating.
No unintended degradation of data shall occur between SunGuide's database and the transfer of that data by the direct database feed.
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
216
FEAT31.1.20
DW004
FEAT31.1.21
OD014
FEAT31.2
FEAT31.2.1
OD001S
FEAT31.2.2
OD004
FEAT31.2.3
DW002D
FEAT31.2.4
DW004D
FEAT31.2.5
OD012
FEAT31.3
FEAT31.3.1
OD002
FEAT31.3.2
OD002T
FEAT31.3.3
DW006D
The content provided to the ODS via the direct ODS content derived from Data database connection shall be derived directly Bus
from SunGuide's databus.
SunGuide RWIS events included The ODS shall include events from the SunGuide in ODS
RWIS subsystem.
Data storage
SunGuide shall store raw detector data for 2 weeks and shall store roll ups of speeds, Data storage times
occupancy, and drive times in 15 minute roll ups for 3 years.
SunGuide shall store data for a configurable Configurable amount of time
amount of time.
The Direct Database Feed shall be accessible by the ODS through the use of standard database ODS accessible via standard tool sets for storing data, such as database database tool sets
triggers that support periodic data transfers.
SunGuide shall archive link data, travel times, raw weather, raw traffic data, and operator‐entered event data.
All databases included in the ODS shall be Open ODBC compliant databases with Data Base Connectivity (ODBC) compliant and SQL support
support Structured Query Language (SQL) database queries.
Published data
SunGuide shall introduce no more than two Loading records latency
minutes latency when loading records from the source data system.
Updates of the Direct Information Feed shall be Publication of updates
published for licensed users at least once every five minutes.
SunGuide shall make data available to the Data Make data available in one Archive or ODS in one minute or less of it being minute or less available.
Archived data for ODS
ODS
3
ODS
3
ODS
3
ODS
4.2
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
217
FEAT31.4
FEAT31.4.1
Viewing archived data
OD003R
Archived data drop down list
FEAT31.4.2
OD004R
Data field drop down lists
FEAT31.4.3
OD005R
Time slice drop down lists
FEAT31.4.4
OD006R
FEAT31.4.5
WS012
FEAT31.4.6
WS013
Users shall be able to select the type of archived data to view/extract via a drop down list (e.g., speed, occupancy, and times).
Users shall be able to select the data fields to view/extract via drop down lists (e.g., date range, time).
Users shall be able to select the time slices of data to view/extract via drop down lists for dates and times (e.g., 1 minute, 15 minute).
Viewing/extraction of archived data shall not Keep normal performance
prevent the normal performance of ODS functions.
A SunGuide supervisor with appropriate permissions shall have the capability of viewing Viewing detector counts
detector counts by detector station for the last 48 hours.
The Operator Interface shall provide the ability for the operator to select the time period range (time of day and date) and the type of data (i.e., raw, Select time range and data type smooth, or forecast) pertaining to the displayed traffic conditions from Central Florida and statewide traffic sensors.
FEAT31.5
Message logs
FEAT31.5.1
OD010
Included logs and sign recommendations
FEAT31.5.2
OD001M
Indicate data unavailable
The ODS shall include DMS Message Logs (SunGuide and OOCEA), 511 message logs and VSL sign recommendations.
These messages shall indicate whether all data slated for delivery is unavailable, or only a portion of the data is unavailable.
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
ODS
3
218
FEAT31.5.3
DW001D
FEAT31.5.4
DW004D1
FEAT31.5.5
DW001E
FEAT31.5.6
OD009
FEAT32
FEAT32.1
FEAT32.1.1
DF001
The standard tool sets used to carry out the Direct Database Feed shall be capable of generating Standard tool sets capable of error messages in cases where the data slated for generating error messages
delivery is currently unavailable.
Consistent format for error messages
SunGuide shall use a consistent format for error messages across all applications.
These messages shall indicate whether all data Messages indicate data slated for delivery is unavailable, or only a portion availability
of the data is unavailable.
Error messages shall indicate whether all data Error messages indicate data slated for delivery is unavailable, or only a portion availability
of the data is unavailable.
Data Fusion System (DFS)
General
The Data Fusion subsystem shall have the ability to extract data from data streams and present Abilities of DFS
alerts to the SunGuide operator for approval.
FEAT32.1.2
DF007
Use of metadata for interpretation
FEAT32.1.3
DF008
DFS to not degrade data accuracy
FEAT32.1.4
DF015
Allow for periodic reconfiguration
FEAT32.1.6
DF025
The Data Fusion subsystem shall contain metadata necessary to interpret the data and shall have an identifier of the source of the data.
The Data Fusion subsystem shall not degrade the accuracy of the received data.
The Data Fusion subsystem shall allow periodic addition, reconfiguration or redefinition of roadway segments and ITS devices without any loss of current or past data.
The Data Fusion Subsystem shall be synchronized Synchronized to universal time to a universal time standard obtained through the standard
internet.
ODS
3
ODS
3
ODS
3
ODS
3
DFS
DFS
4
4
DFS
4.2
DFS
4
DFS
4
DFS
4
DFS
4
219
FEAT32.1.8
DF022F
FEAT32.1.8.2
DF022F2
FEAT32.1.8.3
DF022F3
FEAT32.1.8.4
DF022F4
FEAT32.1.8.5
DF022F5
FEAT32.1.8.6
DF022F6
FEAT32.1.8.7
DF022F7
FEAT32.1.8.8
DF022F8
FEAT32.1.8.9
DF022F9
SunGuide Data Fusion shall automatically select Select FDOT modified SAE codes FDOT modified SAE J‐2540 codes that describe an event.
The system shall present the message 'On‐ramp SAE Code 2980 Message
lanes blocked' for events which are identified as SAE Code 2980.
The system shall identify an event with more than one contiguous lanes blocked on the left of an on SAE Code 2981 Identify
ramp as SAE Code 2981.
The system shall present the message 'On‐ramp SAE Code 2981 Message
left lanes blocked' for events which are identified as SAE Code 2981.
The system shall identify an event with more than one contiguous lanes blocked on the right of an SAE Code 2983 Identify
on ramp as SAE Code 2983.
The system shall present the message 'On‐ramp SAE Code 2983 Message
right lanes blocked' for events which are identified as SAE Code 2983.
The system shall identify an event with more than one contiguous lanes blocked in the center of an SAE Code 2982 Identify
on ramp as SAE Code 2982.
The system shall present the message 'On‐ramp SAE Code 2982 Message
center lanes blocked' for events which are identified as SAE Code 2982.
The system shall identify an event which blocks the left shoulder of an on ramp as SAE Code 2984.
SAE Code 2984 Identify
FEAT32.1.8.10
DF022F10
SAE Code 2984 Message
FEAT32.1.8.11
DF022F11
SAE Code 2985 Identify
The system shall present the message 'On‐ramp left shoulder blocked' for events which are identified as SAE Code 2984.
The system shall identify an event which blocks the right shoulder of an on ramp as SAE Code 2985.
DFS
4
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
220
FEAT32.1.8.12
DF022F12
SAE Code 2985 Message
FEAT32.1.8.13
DF022F13
SAE Code 2986 Identify
FEAT32.1.8.14
DF022F15
SAE Code 2987 Identify
FEAT32.1.8.15
DF022F16
SAE Code 2987 Message
FEAT32.1.8.16
DF022F17
SAE Code 2988 Identify
FEAT32.1.8.17
DF022F18
SAE Code 2988 Message
FEAT32.1.8.18
DF022F19
SAE Code 2989 Identify
FEAT32.1.8.19
DF022F20
SAE Code 2989 Message
FEAT32.1.8.20
DF022F21
SAE Code 2990 Identify
FEAT32.1.8.21
DF022F22
SAE Code 2990 Message
FEAT32.1.8.22
DF022F23
SAE Code 2991 Identify
The system shall present the message 'On‐ramp right shoulder blocked' for events which are identified as SAE Code 2985.
The system shall identify an event with more than one noncontiguous lane blocked of an off ramp as SAE Code 2986.
The system shall identify an event with more than one contiguous lanes blocked on the left of an off ramp as SAE Code 2987.
The system shall present the message 'Off‐ramp ‐
left lanes blocked' for events which are identified as SAE Code 2987.
The system shall identify an event with more than one contiguous lanes blocked in the center of an off ramp as SAE Code 2988.
The system shall present the message 'Off‐ramp center lanes blocked' for events which are identified as SAE Code 2988.
The system shall identify an event which blocks the right lanes of an off ramp as SAE Code 2989.
The system shall present the message 'Off‐ramp right lanes blocked' for events which are identified as SAE Code 2989.
The system shall identify an event which blocks the left shoulder of an off ramp as SAE Code 2990.
The system shall present the message 'Off‐ramp left shoulder blocked' for events which are identified as SAE Code 2990.
The system shall identify an event which blocks the right shoulder of an off ramp as SAE Code 2991.
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
221
FEAT32.1.8.23
DF022F24
SAE Code 2991 Message
FEAT32.1.8.24
DF022F25
SAE Code 2992 Identify
FEAT32.1.8.25
DF022F26
SAE Code 2992 Message
FEAT32.1.8.26
DF022F27
SAE Code 2993 Identify
FEAT32.1.8.27
DF022F28
SAE Code 2993 Message
FEAT32.1.8.28
DF022F29
SAE Code 2994 Identify
FEAT32.1.8.29
FEAT32.1.8.30
DF022F30
DF022F31
SAE Code 2994 Message
SAE Code 2995 Identify
The system shall present the message 'Off‐ramp right shoulder blocked' for events which are identified as SAE Code 2991.
The system shall identify an event which blocks more than one noncontiguous express lane as SAE Code 2992.
The system shall present the message 'X Express lanes blocked' for events which are identified as SAE Code 2992, where X is the number of lanes which are blocked.
The system shall identify an event with more than one contiguous lanes blocked on the left of an express lanes segment as SAE Code 2993.
The system shall present the message 'X Left express lanes blocked' for events which are identified as SAE Code 2993, where X is the number of lanes which are blocked.
The system shall identify an event with more than one contiguous lanes blocked in the center of an express lanes segment as SAE Code 2994.
The system shall present the message 'X Center express lanes blocked' for events which are identified as SAE Code 2994, where X is the number of lanes which are blocked.
The system shall identify an event with more than one contiguous lanes blocked on the right of an express lanes segment as SAE Code 2995.
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
DFS
4.3
222
FEAT32.1.8.31
FEAT32.1.8.32
DF022F32
DF022F14
FEAT32.2
SAE Code 2995 Message
SAE Code 2986 Message
The system shall present the message 'X Right express lanes blocked' for events which are identified as SAE Code 2995, where X is the number of lanes which are blocked.
The system shall present the message 'Off‐ramp lanes blocked' for events which are identified as SAE Code 2986.
Database
FEAT32.2.1
DF001D
FEAT32.2.2
DF002D
FEAT32.2.3
DF003D
FEAT32.2.6
DF007D
FEAT32.3
FEAT32.3.2
DF004
FEAT32.3.3
DF013
The Database Component shall maintain a log of all events.
The Database Component shall save only the data Archive only operator designated by the SunGuide Administrator as designated data
archive data.
The database component shall contain a Repository for data collected or repository for all data collected by or generated generated
by the data fusion system.
The database component shall be a relational Relational database
database.
Data Output
The Data Fusion subsystem shall provide a third Third party feed for party feed that supports both public‐ and private‐
public/private sectors
sector services.
The Data Fusion subsystem shall use a modified SunGuide Center‐to‐Center Plug‐in component to Use modified C2C plug‐in to make fused traveler information available to the provide fused data
Information Dissemination Subsystem.
Maintain log of all events
DFS
4.3
DFS
4.3
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
223
FEAT32.3.5
DF006F
FEAT32.3.6
DF006F1
FEAT32.3.7
DF007F
FEAT32.3.8
DF011F
FEAT32.3.9
DF017F
FEAT32.3.10
DF019F
For events, SunGuide shall include a Location ID, The location referenced by the Location ID will have the following fields as a minimum: ‐ a City; ‐ a County; Fields to include in data fusion ‐ a Metro Area
output
Otherwise null data shall be provided in the fields. SunGuide shall not require these fields to be populated at the time the location is configured.
The information shall be passed to the IDS using Information passed to IDS use FDOT Modified SAE J2540 codes, EM Location standard codes
references and other standard traveler information codes.
The data provided by the DFS shall be DFS data documented in C2C documented in a Center‐to‐Center Interface ICD
Control Document (ICD).
Provide travel times and delays The Data Fusion component shall provide travel to the IDS
times and travel delays to the IDS.
The Data Fusion Subsystem shall incorporate Incorporate received weather weather conditions received through an conditions
automatic feed provided by DTN.
Provide secure data to third parties
The Data Fusion component shall provide data to third parties that are secure behind a firewall that prohibits unauthorized access and manipulation of the information.
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
224
FEAT32.3.11
DF001C
FEAT32.3.12
DF002C
FEAT32.3.13
DF003C
FEAT32.3.14
DF004C
FEAT32.3.15
DF018F
FEAT32.4
FEAT32.4.2
DF026
FEAT32.4.4
DF001F
Use TMDD standard
The Data Fusion subsystem shall use Transmission Control Protocol/Internet Protocol (TCP/IP) connectivity, the Hypertext Transfer Protocol (HTTP), and XML data format based shall be consistent with TMDD 2.1 (and NTCIP 2306) and the emerging TMDD 3.0 (and NTCIP 2306) using FDOT modified SAE J2540 IITS codes to capture event information for transmission to the IDS.
Fused events associated with Each fused traveler information event shall be latitude and longitude
associated with a latitude and longitude.
Fused traveler information shall be formatted and Fused traveler information transmitted in accordance with NTCIP 2306 standards
protocol and the J2540‐1 July 2002 Tables 2 and 11 message set.
The Center‐to‐Center interface shall provide the Provide FDOT location tables to FDOT location table to be used for a District by be used by IDS
the Information Dissemination Subsystem.
A SunGuide Administrator shall be able to Designate data accessible to designate what data will be accessible as a limited third parties
data feed to third parties.
Engine
The Data Fusion Subsystem shall calculate travel Calculate travel time and time and speeds along instrumented roadways for speeds
FDOT defined links.
SunGuide shall provide a list of active events Associate real‐time info for within a configurable number of tenths of a mile. current event
If no data is available, an empty list shall be provided.
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
225
FEAT32.4.5
FEAT32.4.6
DF003F
FEAT32.4.7
DF004F
FEAT32.4.8
DF005F
FEAT32.4.9
DF006F2
FEAT32.4.11
DF011F2
FEAT32.4.13
DF013F
FEAT32.4.14
DF016F
The Data Fusion component shall associate real‐
time information within 200 feet of a road Associate info within 200 feet of construction event with the road construction construction event
event, if no data is available, a null value or blank shall be provided.
Travel time information for dissemination shall never be less than the travel time computed using Travel times never less than the posted speed limit, if no data is available, a speed limit
null value or blank shall be provided.
SunGuide shall allow the operator to associate external events (e.g. FHP events) that are within Associate real‐time emergency configurable number of tenths of a mile to active events
events. If no data is available, an empty list shall be provided.
SunGuide shall provide a list of nearby active Identify conflicting event events within a configurable number of tenths of reports
a mile to the operator when an external event is received.
If the information for a field is not available, a null Blank values for unavailable value or blank shall be provided.
fields
The Data Fusion Component shall calculate delay Calculate delay times based on times based on posted speed limits for the speed limits
defined road segments.
The Data Fusion component shall receive data External sources documented in from external sources documented in an ICD.
an ICD
Alert operator for conflict between sources
SunGuide shall provide a list of nearby active events to the operator when external events are received.
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
226
FEAT32.4.15
FEAT32.4.16
DF016F1
DF016F2
FEAT32.5
FEAT32.5.1
Calculate flat earth distance between events
Alert operator for event conflicts
The Data Fusion component shall compare the latitude and longitude of an event with other event latitude and longitudes and calculate a flat earth straight line distance between the events.
The Data Fusion component shall alert the operator to a possible duplication or conflict of events if two or more events are within a configurable distance of each other.
Performance
DF002
FEAT32.5.4
DF017
FEAT32.5.8
DF005D
FEAT32.6
Fuse data within 1 minute
The Data Fusion subsystem shall assemble and fuse traveler information within 1 minute of receipt of applicable data from external sources including operator entered events.
The Data Fusion Subsystem shall be able to monitor system performance, status of interfaces Monitor system performance
and alert the operator and designated personnel to system problems.
Information from the database shall be retrieved Information available within 12 and presented to the operator within 12 seconds seconds
of the submission of the request for data.
Data Sources
FEAT32.6.1
DF006
FEAT32.6.2
DF011
The Data Fusion subsystem shall provide Provide synchronous data from synchronous data from various sources having no various sources
duplicate information within a single status report on a segment.
The Data Fusion subsystem shall provide the Latest info on current latest information on the current status of FDOT‐
transporation status
designated transportation services.
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4.2
227
FEAT32.6.3
DF016
FEAT32.6.4
DF020
FEAT32.6.5
DF024
FEAT32.6.7
DF011F4
FEAT32.6.8
DF023F
FEAT32.7
FEAT32.7.1
DF012
FEAT32.7.2
DF014
FEAT32.7.3
DF029
FEAT32.7.4
DF009F
The Data Fusion subsystem shall be able to Support automated and data support automated and manual data entry for all entry for events
event types.
SunGuide shall receive weather alerts from DTN Receive weather alerts from and provide operators with an alert that can be DTN
used to create an event.
The Data Fusion Subsystem shall use location Use FDOT‐specified location tables specified by FDOT that can be redefined or tables
added to while the system is operating.
For sites that are SunGuide equipped, the DFS Obtain travel time and speeds shall obtain travel time and speeds from from SunGuide
SunGuide.
SunGuide shall access the DTN automated feed Access the DTN
using a "web method" that connects to a DTN server via the public Internet.
Reporting
The Data Fusion Subsystem shall locally archive Locally archive selected data
selected data and messages.
The Data Fusion subsystem shall be able to Generate reports with selected generate reports according to parameters parameters
selected by the system administrator.
Generate reports based on data The Data Fusion subsystem shall be able to saved
generate reports based on data saved.
The system administrator shall be able to Generate report using any generate a report using any of the database fields, database fields
or combination of fields, as filters.
DFS
4
DFS
4.2
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
228
FEAT32.7.5
DF012F
FEAT32.7.5.1
DF012F1
FEAT32.7.6
DF014F
FEAT32.7.7
DF015F
FEAT32.8
FEAT32.8.1
DF002E2
FEAT32.8.2
DF001E
FEAT32.8.3
DF002E
FEAT32.8.4
DF020F1
FEAT33
FEAT33.1
The Data Fusion component shall generate a minimum of fifteen standard reports to view archived data. Note: Based on negotiations it has been agreed that the DFS contractor (i.e. SwRI) Generate minimum of fifteen has included a “level of effort” to discuss and standard reports
review reports with FDOT but that the actual generation of the reports is not assigned to the DFS Contractor (i.e. SwRI).
Content and format specified by The content and format of the reports shall be FDOT
specified by FDOT.
Users shall be able to generate custom reports Generate custom reports with using an SQL interface embedded within the SQL interface
archived data page.
Reports generated in PDF, All reports shall be generated in PDF, Word and Word, and Excel format
Excel format.
Alternate Roads
When an alternative road is presented for Alternate road description
operator selection a description shall be displayed if available.
The SunGuide Administrative Editor shall allow Alternate roads from EM primary and secondary alternate roads (along locations
with descriptions) to be maintained for each EM Location.
A SunGuide operator shall be able to select either Select primary/secondary a primary or a secondary alternative road if alternate roads
configured for the location of the event that the operator selected.
Send weather events to IDS via The Data Fusion component shall send weather C2C
events to the IDS using the C2C.
Pricing System (PS)
General
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
DFS
4
PS
PS
3.1
3.1
229
FEAT33.1.1
FEAT33.1.1.2
ML012P
ML013P
FEAT33.1.2
ML007D
FEAT33.1.2.1
ML007D1
FEAT33.1.3
ML008A
FEAT33.1.4
FEAT33.1.6
ML011S
If the Express Lanes module goes down, starts for Restart state in open/time‐of‐ the first time, or needs to be restarted, it shall day rate mode
start/restart in Open/Time‐Of‐Day Rate mode.
If the approved toll rate for a segment upon restart is known to be greater than the currently posted rate, the software shall use the default Delay used for starts/restarts Maximum Transit Time for Toll Rate DMS and in other cases the software shall use the default Minimum Transit Time.
DMS interface as direct communications path
The managed lanes module shall use the most direct communications path available to update the Toll Rate DMS and Lane Status DMS.
Bypass message arbitration for Toll Rate DMS and Lane Status DMS shall not use toll rate DMS signs
message arbitration.
The software shall be designed to support all segments of Phase 1 and 1B at a minimum. All segments currently in operation shall be available Included segments
in configuration, operations screens and displays wherever segments are utilized.
Timestamp XML communications
Data Storage
The Pricing subsystem shall record and timestamp all incoming and outgoing XML communications between Pricing subsystem and Data Bus to the database.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
3.1
PS
4.3
PS
4.3
230
FEAT33.1.6.1
ML017S
FEAT33.1.6.2
ML018S
FEAT33.1.6.3
ML019S
FEAT33.1.6.4
ML020S
Data stored for successful rate/mode requests shall include:
oSegment ID
oUser ID
oMode (or Middleware Rate Adjustment)
oRate
Data stored for successful oRequest Time
rate/mode
oEffective Time
oEnding Time (if provided)
oTransit Times (if provided)
oEvent ID (if provided)
oComments (if provided)
oSunGuideID
Data stored for pricing alerts shall include:
oClient‐unique ID if available
Data stored for pricing alerts oSunGuide Alert ID
oDate/Time
oAlert Details (text presented to user)
Data stored for alert acknowledgements shall include:
oSunGuide Alert ID
Data stored for alert oUser ID
acknowledgements
oTime Acknowledged (time received/stored by SunGuide)
Data stored for a successful rate acknowledgement (from middleware) shall Data stored for successful rate include:
oSunGuide ID
acknowledgements
oSunpass ID
oDate/Time of acknowledgement
PS
4.3
PS
4.3
PS
4.3
PS
4.3
231
FEAT33.1.6.5
ML021S
FEAT33.1.6.6
ML032U2
FEAT33.1.7
FEAT33.1.7.1
FEAT33.1.7.2
ML028A
ML029A
Data stored for a middleware interface error shall include:
Data stored for a middleware oSegment ID
oSunGuide ID of message to middleware
interface
oError Details (error string returned by middleware)
Data stored by the software for Express Lanes Data stored for Express Lanes Alerts Acknowledgements shall include the unique Alters Acknowledgments
alert ID and the User ID supplied in the acknowledgement.
When Sunpass imports rates using an offline rate file exported from SunGuide, Sunpass will provide a file that specifies which of these rates have been Offline Update Synchronization successfully imported into Sunpass so that SunGuide can import this information and record these as successfully delivered.
Import file
Record File Information
The SunGuide software shall provide a means for a user to select a file and for SunGuide to import the specified file containing the SunGuide ID, Sunpass ID, rate, effective time and status for each rate that was imported into Sunpass via an offline file.
For each rate reported in this file that was not successfully transferred prior to the loss of communications, SunGuide shall then record this information as if it had been transferred via the normal communications channel, except that a status indication shall be included to indicate that this was an offline update.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
232
FEAT33.1.7.3
FEAT33.1.8
FEAT33.1.9
FEAT33.2
ML035A
ML012M
File Creation
The software shall create a file on a daily basis with all rates not delivered to the Middleware, except rate messages that were rejected by the middleware with unrecoverable errors and those previously successfully exported, formatted the same as those sent when connected to the Middleware.
Communications between the software and Communication between the Express Lanes clients shall be in XML, including software and Express Lanes requests and responses for configuration data, alerts, status messages and commands.
clients
The software shall use the following decision sequence for selecting the Transit Time parameters when the parameters have not been provided by a client request:
1.If there is no pending rate (posted on at least one toll rate DMS, but not yet on gantry) or there is a pending rate and the new rate is equal to the pending rate, use the default Minimum Transit Sequence for selecting Transit Times if the new rate is less than or equal to the Time parameters
active rate on the gantry and use the default Maximum Transit Times if the new rate is greater than the active rate on the gantry.
2.Else if there is a pending rate use the default Minimum Transit Times if the new rate is less than the pending rate and use the default Maximum Transit Times if the new rate is greater than the pending rate.
Configuration
PS
4.3
PS
4.3
PS
4.3
PS
3.1
233
FEAT33.2.1
ML003A
FEAT33.2.1.2
ML015P
FEAT33.2.1.3
ML003A1
Authorized users shall be able to edit the maximum and minimum Toll Rate Transit Time Delay parameter configuration
Parameters for each Toll Rate DMS, in seconds, using the Administrative Editor.
The software shall use the new default Toll Rate Transit Time parameters for rate changes that occur (i.e. initial DMS posting is scheduled to Effective time of changes to occur) after the new default parameter value is delays
set and shall not apply the change to a pending rate update (i.e. one already in the process of being posted).
The Administrative Editor shall not permit a change to a maximum or minimum transit time Change to maximum or that would result in the maximum transit time minimum transit time
being less than the minimum transit time.
FEAT33.2.2
ML009A
Daily rate schedule configuration
FEAT33.2.2.1
ML004P2
Time configuration
FEAT33.2.2.2
ML010A
Toll rate configuration
FEAT33.2.2.3
ML011A
Daily rate schedule lock
FEAT33.2.3
ML004P3
Segment rate schedule configuration
Authorized users shall be able to create and maintain a 24‐hour Daily Rate Schedule using the Administrative Editor.
For a Daily Rate Schedule, the user shall be able to enter the time a rate begins in at least 15 minute increments, starting at midnight, for the entire 24 hour period (HH:00, HH:15, HH:30, HH:45).
For a Daily Rate Schedule, the user shall be able to enter the toll rate charged for each period in dollars and cents.
The user shall not be allowed to change a Daily Rate Schedule once this table has been used (i.e. used to generate a toll rate sent to the middleware).
The user shall be able to create and edit a Segment Rate Schedule for a week.
PS
4.3
PS
4.3
PS
4.3
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
234
FEAT33.2.3.1
ML002A
Selection of the segments and start date
FEAT33.2.3.2
ML004P4
Table rows for days of the week
FEAT33.2.3.3
ML012A
Segment rate schedule locking
FEAT33.2.4
ML013A
Viewing and editing TOD assignments
FEAT33.2.4.1
ML014A
Treatment of past dates
FEAT33.2.4.2
ML015A
Menu for TOD selection
FEAT33.2.5
ML016A
Notification for start date/time in the past
FEAT33.2.6
ML017A
Express lanes DMS configuration
When creating/editing a Segment Rate Schedule, the user shall be able to set the Segment(s) the toll rates apply to and Start Date for the rates in the table.
For each day of the week, the user shall be required to select a Daily Rate Schedule to use with the following day or table types for that day of the week: Normal, Holiday/Special Event, Observed Holiday
The user shall not be allowed to change a Segment Rate Schedule once this table has been used (i.e. used to generate a toll rate sent to the middleware).
The software shall provide a means for a user to view and edit Type‐of‐Day assignments (Holiday/Special Event or Observed Holiday) for current and future dates via the Administrator Editor.
The software shall not allow a user to edit assignments for past dates.
When the user selects a date to change the Type‐
of‐Day, the software shall provide a menu, set of radio buttons, or similar means that restricts the user to selecting Holiday or Observed Holiday values.
If the user creates or modifies an entry with a start date and time that is prior to the current date and time, the software shall not save the entry and shall notify the user that the entry shall not be allowed.
Authorized users shall be able to configure DMS for the Express Lanes facility using the Administrative Editor or Configuration files.
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
235
FEAT33.2.6.1
ML007A
FEAT33.2.6.2
ML002D
FEAT33.2.6.3
ML018A
FEAT33.2.6.4
ML019A
FEAT33.2.6.5
ML020A
FEAT33.2.6.6
ML021A
FEAT33.2.6.7
ML022A
FEAT33.2.6.7.1
ML022A1
DMS type selection
The user shall be able to select if a DMS displays standard DMS messages (Lane Status DMS), if it displays toll rates and is mounted on an approach (Toll Rate DMS), or if it displays toll rates and is mounted on the toll gantry (Toll Gantry DMS).
The software shall support the association of Association of multiple DMS multiple DMS, whether Lane Status, Toll Rate or signs per segment
Toll Gantry, with a segment.
The user shall be able to select the segment(s) Toll rate DMS segment whose rate (or combined rate) is displayed on a association
Toll Rate DMS.
The user shall be able to enter and edit the text Toll rate/gantry DMS static text that is on the static sign associated with each Toll Rate DMS or Toll Gantry DMS.
A user with permissions to configure Express Lanes shall be able to configure mode‐specific one‐
line messages via the Administrative Editor that will be posted for Toll Rate DMS and Toll Gantry Toll rate/gantry DMS default for Closed and Zero Rate, and for Lane Status DMS messages
for Closed, Zero Rate and Operating/Tolling (Time‐
of‐Day, Dynamic and Manual modes shall share one message).
The software shall prevent the user from entering Default message validation default messages longer than 6 characters for a Toll Rate DMS.
The software shall allow DMS to be added and Addition and removal of DMS removed from operating with the express lanes signs
module using the Administrative Editor.
The removal of a DMS from the express lanes Sign removal affects for pending module shall affect future and current pending rate messages
rate messages.
PS
3.1
PS
4.3
PS
3.1
PS
3.1
PS
4.3
PS
3.1
PS
3.1
PS
3.1
236
FEAT33.2.6.8
ML027A
FEAT33.2.7
ML023A
FEAT33.2.7.1
ML005A
FEAT33.2.7.2
ML005A1
FEAT33.2.7.3
ML006A
FEAT33.2.7.4
FEAT33.2.7.5
FEAT33.2.8
ML023A1
The software shall prevent the user from entering Entering default message for default messages longer than 18 characters for a Lane Status DMS
Lane Status DMS.
Authorized users shall be able to configure Operator interface parameters parameters related to the Operator Interface and permissions
using the Administrative Editor or configuration file.
The user shall be able to assign permissions to users or user classes to place Express Lanes into TOD pricing permissions
an mode via buttons on the Express Lanes Tab.
The user shall be able to assign permissions to users or user classes to receive and acknowledge Express lanes alert permissions
alerts for the express lanes as defined in requirement ML010U.
The user shall be able to set a flag on whether a Closed or Open/Zero Rate Override is required to Require event association flag
be associated to an event.
Non‐TOD alert frequency
ML023A2
Maximum effective time adjustment
ML024A
Toll systems interface parameters and permissions
The user shall be able to set the frequency, in seconds, in which a TMC Operator is alerted when the express lanes are not operating in TOD mode.
The user shall be able configure the maximum amount of time, in minutes, that the effective time of an override can be adjusted. The initial value shall be 10 minutes.
Authorized users shall be able to configure parameters related to the Toll System Interface using the Administrative Editor or configuration file.
PS
4.3
PS
3.1
PS
4.3
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
237
FEAT33.2.8.1
ML007I
Middleware response alert period
FEAT33.2.8.4
ML024A2
Middleware heartbeat rate
FEAT33.2.9
ML025A
Segment configuration
FEAT33.2.9.1
ML025A1
Segment start point
The user shall be able to set the minimum time in minutes and seconds before the Middleware Response Alert is activated.
The user shall be able to set the time in minutes and seconds between attempts by the software to request a heartbeat message from the Middleware.
The user shall be able to configure parameters related to the configuration of the Express Lanes segments using the Administrative Editor or configuration file.
The user shall be able to define the start location of the segment based on latitude/longitude.
FEAT33.2.9.2
ML025A2
Segment end point
The user shall be able to define the end location of the segment based on latitude/longitude.
FEAT33.2.10
ML003D
FEAT33.2.11
FEAT33.2.11.1
ML003M
SunGuide shall support the association of multiple Association of multiple toll rate Toll Rate signs where a single physical sign houses signs
two Toll Rate DMS.
Configuring Requests for Express Lanes
The software shall allow an authenticated Express Lanes client to retrieve the configuration of the express lanes. The response shall include segment‐
specific configuration data for each segment and Retrieval of configuration
segment‐independent configuration data for the Express Lanes.
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
4.3
PS
4.3
238
FEAT33.2.11.2
FEAT33.2.11.3
FEAT33.2.11.4
ML003M1
ML003M2
ML006M
The Express Lanes configuration data provided in response to a request for the configuration of the express lanes configuration shall include the default text used for Closed, Zero Rate and Operating/Tolling modes for Toll Rate DMS and for Lane Status DMS, the value of the Require Express Lane Configuration Data Event Association flag, the Retroactive Adjustment Limit, the Maximum Rate Update Interval, the Suppress Rate Change Alerts flag and a list of Express Lane Segment IDs and associated segment names.
The segment data provided in response to a request for the configuration of the express lanes configuration shall include for each segment the Segment Maximum Toll Rate and a list of Toll Rate Signs (including Toll Gantry Sign(s)) and Lane Status Signs, including name and function for each in the order specified in the segment Data provided in response to configuration; and including for each Toll Rate request for configuration
Sign and Gantry Sign, a list of DMS IDs and associated static text in the order specified in the configuration, and for each DMS, the associated segment ID(s) along with the Minimum Transit Time, Maximum Transit Time and distance to gantry (in feet).
The software shall support a request for segment Time‐of‐Day table and shall respond with each Request segment Time‐of‐Day segment and the rate and time for each scheduled rate for that segment and date.
PS
4.3
PS
4.3
PS
4.3
239
FEAT33.2.12
ML038A
FEAT33.2.13
ML039A
FEAT33.2.14
ML031A
FEAT33.2.15
ML040A
FEAT33.3
ML001
FEAT33.3.1
ML016P
FEAT33.3.1.1
ML001I
FEAT33.3.1.1.1
ML021P
An authorized user shall be able to select in Lane Status DMS selection
Adminstrative Editor the Lane Status DMS associated with a segment.
A user with permissions to configure Express Lanes shall be able to configure the Maximum Configure Maximum Rate Rate Update Interval, which shall be specified in Update Interval
minutes and shall have a default value of 15 minutes.
A configurable "Suppress Rate Change Alerts" flag shall be provided that a user with permission to Configure "Suppress Rate Change Alerts"
configure Express Lanes can set via Administrative Editor.
The software shall provide a Distance to Gantry for each Toll Rate DMS that specifies the distance Specify distance to Gantry for to the associated gantry in feet that is Toll Rate DMS
configurable via the Administrative Editor by users with permissions to configure Express Lanes.
SunGuide shall be responsible for managing rate Rate selection
schedules and coordinating Toll Rate DMS rate display and rate selection.
Rate selection and The software shall select a toll rate and dissemination
disseminate to DMS.
The software shall select the toll rate for the time‐
of‐day for each segment using the rules in Rate selection for open/normal requirements ML017P, ML018P, ML019P, rate mode
ML020P, and ML021P when that segment is in the Open/Time of Day mode.
For each segment operating in Time‐of‐Day mode, Segment selection
the software shall use rate entries that are for that particular segment.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
3.1
PS
3.1
PS
3.1
PS
4.3
240
FEAT33.3.1.1.2
ML017P
Time‐of‐day rate entry
FEAT33.3.1.1.3
ML018P
Type‐of‐day rate entry
FEAT33.3.1.1.4
ML019P
Start date selection
FEAT33.3.1.1.5
FEAT33.3.1.2
ML020P
ML009D
Table type selection
DMS message dissemination
When the segment is in the Open/Time of Day Rate mode: The software shall use the rate entry with the most recent Time‐of‐Day on or before the current time.
When the segment is in the Open/Time‐of‐Day Rate mode: If the current date has been configured to be a Holiday or Observed Holiday, the software shall use the corresponding Holiday or Observed Holiday rate table. Otherwise, the software shall use the rate table for that day of the week.
When the segment is in the Open/Time‐of‐Day Rate mode: The software shall use the rate table of the correct type with the most recent start date on or before the current date.
When the segment is in the Open/Time of Day Rate mode: The software shall use the Time of Day Table Type unless the operator has placed the segment into an override mode, in which case the software shall use the rate entered or otherwise selected according to the override mode selected by the operator.
The software shall communicate the toll rates in time for them to be displayed on DMS as described in the following subrequirements.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
3.1
241
FEAT33.3.1.2.1
FEAT33.3.1.2.1.1
FEAT33.3.1.2.2
FEAT33.3.1.2.3
ML009D1
ML009D2
ML009D4
ML009D5
At every time that is a whole multiple of fifteen minutes (:00, :15, :30 and :45), the software shall update each Toll Rate DMS, the Gantry DMS and Lane State DMS and send the rate to the Communication of rate to toll Middleware, even if the rate is not changing, rate DMS
except if there is a pending rate, using the current rate in effect, except when in Time of Day mode, in which the rate shall be based on the Time of Day rate table.
If a Toll Gantry DMS is configured for a segment, the software shall communicate an increased rate Communication of increased to a segment's Toll Gantry DMS at a time equal to rate to toll gantry signs
the applicable Maximum Toll Rate Change Delay added to the applied time of the toll rate change.
The software shall resend a toll rate or lane status message at a configurable rate defined by the DMS Resend Rate until the Toll Rate DMS, Toll Toll rate DMS and toll gantry Gantry DMS or Lane Status DMS acknowledges rate message retry
receipt, a new toll rate/mode is submitted, or the Maximum DMS Resends is reached whichever comes first.
If the software suspends sending a message to a Toll Rate DMS, Toll Gantry DMS or Lane Status DMS because of a new toll rate or operating Actions when rate superseded
mode, the software shall clear the old message in pricing module buffers/queues and record the failure.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
242
FEAT33.3.1.2.4
ML009D6
FEAT33.3.1.2.5
ML007P
FEAT33.3.2
ML005P
FEAT33.3.3
ML011P3
FEAT33.4
When a new rate is selected for display on a Toll Rate DMS, Toll Gantry DMS or Lane Status DMS Override of manual message by currently displaying a manually‐selected message, the software shall replace the manual message new rate message
with the new rate message.
When in Time‐of‐Day mode, SunGuide shall update the Toll Rate DMS associated with a segment having the greatest Toll Rate Transit Updates to toll rate signs
Time at the scheduled time of each rate change, then update the other Toll Rate DMS associated with that segment at times specified by ML009D10.
The rate schedule time, in rate schedule table, Rate schedule time definition shall be the time the toll rate is first sent to a Toll Rate DMS.
The default Maximum and Minimum Transit Max/min time parameters
Times parameters shall not vary by time‐of‐day.
Incident management
FEAT33.4.1
ML013E
FEAT33.4.1.1
ML014E
FEAT33.4.1.1.1
ML015E
FEAT33.4.1.1.1.1
ML015E1
The software shall provide a means to manage Events with express and general the facility in response to Express Lanes and purpose lanes
general purpose lanes events.
The software shall respond to events in the Event response
Express Lanes and general purpose lanes.
Toll Rate and Toll Gantry DMS shall perform Toll rate/gantry sign functions special functions as decribed in the following subrequirements.
Toll Rate and Toll Gantry DMS shall treat Manual Manual control and Control Messages and TOD/Override messages as TOD/override messages
of equal priority (the last message posted will be displayed).
PS
4.3
PS
4.3
PS
3.1
PS
4.3
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
243
FEAT33.4.1.1.1.2
ML015E2
FEAT33.4.1.1.1.3
ML015E3
FEAT33.4.1.1.4
ML002E1
FEAT33.4.1.2
ML018E
FEAT33.4.1.2.1
ML018E1
FEAT33.4.1.2.2
FEAT33.4.1.3
FEAT33.4.1.3.1
ML018E2
ML019E
ML019E1
Toll Rate and Toll Gantry DMS shall not be sent TOD messages when a segment Override Message is in effect.
Toll Rate and Toll Gantry DMS shall not be sent Event messages not sent
Event Messages.
When an event is declared blocking Express Lanes, the software shall treat the Express Lanes as if they are part of the General Purpose lanes and General purpose DMS and other include General Purpose DMS and other devices device response
and means of dissemination in the suggested response plan following standard SunGuide rules.
TOD messages not sent for overrides
When a client changes the segment's mode and/or rate or issues or discontinues a General handling of overrides
Middleware Rate Adjustment, other segments shall remain unaffected.
When a segment is placed in an override mode, the software shall not communicate any toll rate Suspension of TOD rate changes for that segment from Open/Normal Rate communication to Middleware
mode while the segment remains in override.
Segment independence for overrides/return to normal
Resuming TOD operation
Rate selection
When a segment is placed into or taken out of an Override mode, all other segments shall remain in their current operating mode.
When an Operator returns a segment to Open/Time of Day Rate mode, the software shall perform the following actions: (subrequirements)
The software shall select and implement the rate that is in effect for the time the previous mode is ended.
PS
3.1
PS
3.1
PS
3.1
PS
4.3
PS
3.1
PS
3.1
PS
4.3
PS
4.3
244
FEAT33.4.1.3.2
ML019E2
FEAT33.4.1.4
ML004E
FEAT33.4.1.4.1
ML004E2
FEAT33.4.1.4.2
ML004E1
FEAT33.4.1.4.3
ML004E4
FEAT33.4.1.4.4
ML020E
FEAT33.4.1.4.5
ML021E
Middleware communication
The software shall communicate to the Middleware the new rate with an effective time as specified by requirement ML010P depending on if the new toll rate is higher or lower than the previous mode toll rate for the segment.
The software shall operate the Express Lanes in Open/closed override specific response to a segment being placed into Closed or actions
Open/Zero Toll mode.
When a segment is in Closed or Zero Rate mode, the software shall automatically post the Toll rate/gantry DMS message appropriate Toll Rate DMS, Toll Gantry DMS and Lane Status DMS default message to Toll Rate on open/closed segment
DMS, Toll Gantry DMS and Lane Status DMS associated with a segment.
The software shall set the toll rate to $0.00 for the Open/closed mode toll rate
duration of the override.
When a segment is placed in Closed or Open/Zero Toll mode, the software shall default the effective Open/closed mode toll rate time of the Override Toll Rate to the time the default effective time
Operator applies the override or as specified by the TMC Operator.
When a segment is placed in Closed or Open/Zero mode, the software shall send the Middleware Open/closed mode toll rate the rate message for the mode toll rate within 5 Middleware dissemination
minutes of the Operator entering the segment override.
The software shall send the messages for Toll Rate DMS, Toll Gantry DMS and Lane Status DMS to Open/closed toll rate/gantry associated Toll Rate DMS, Toll Gantry DMS and Lane Status DMS within 30 seconds of the TMC DMS dissemination
operator approving Closed and Zero Rate modes.
PS
4.3
PS
3.1
PS
4.3
PS
3.1
PS
3.1
PS
4.3
PS
4.3
245
FEAT33.4.1.5.1
ML022E1
FEAT33.4.1.5.2
ML022E2
FEAT33.4.1.5.3
ML022E3
FEAT33.4.1.5.5
ML024E
FEAT33.4.1.5.6
ML022E5
Send toll rate to client
The software shall send the toll rate provided by the client to the Middleware for a Middleware Rate Adjustment upon its creation.
When a segment is placed in Open/Manual Toll mode, the software shall default the effective Open/manual rate mode toll time of the Override Toll Rate to the time the rate default effective time
Operator applies the override or as specified by the TMC Operator.
The software shall not update the Toll Rate DMS Toll rate/gantry DMS operation and Toll Gantry DMS for when entering Open/Manual Rate.
When a segment is changed into Time‐of‐Day, Dynamic or Manual Rate mode, the software shall Time‐of‐Day/Dynamic/manual automatically post the Operation/Tolling Lane rate mode
Status DMS default message to the Lane Status DMS associated with the segment.
Toll Rate/Ganry DMS not updateable
The software shall not update the Toll Rate DMS and Toll Gantry DMS upon the creation of a Middleware Rate Adjustment.
PS
4.3
PS
4.3
PS
3.1
PS
4.3
PS
4.3
246
FEAT33.4.1.5.7
ML038U
FEAT33.4.1.6
ML023E
FEAT33.4.1.6.1
ML023E1
FEAT33.4.1.6.3
ML023E3
FEAT33.4.1.6.4
ML023E4
Active Middleware Rate Adjustment for a segment
If a Middleware Rate Adjustment is active for a segment when an operator or Client changes the rate/mode or the software sends a periodic (15 minute) rate update to the middleware, the new rate shall be submitted to the middleware (even if the same as the previous rate or the current adjusted rate) and the software shall pop up an alert and send an alert message to Express Lanes authorized clients to inform the operator that a rate/mode change/update was implemented with a Middleware Rate Adjustment in effect and to ask whether the Adjustment should continue or end unless for a periodic rate, the previous rate was submitted within the prior 15 minutes and the periodic rate is the same as the previous rate, in which case the Adjustment shall automatically continue without generating an alert or requiring confirmation.
The software shall meet the following requirements while entering, maintaining or exiting the Open/Manual Rate mode.
Open/congested rate mode toll The software shall use the toll rate selected by the rate
operator.
The software shall update the Toll Rate DMS and Toll Gantry DMS with the High Congestion toll Toll rate/gantry DMS operation
rates following the rules of requirement ML009D.
Open/manual rate mode specific actions
Selct Time‐of‐Day rates
When a client changes the mode to Time‐of‐Day mode, the software shall select the current Time‐
of‐Day rate within 30 seconds and disseminate to DMS and Middleware.
PS
4.3
PS
4.3
PS
3.1
PS
3.1
PS
4.3
247
FEAT33.4.1.7
ML030E
FEAT33.5
Rate/Mode change
Tabbed GUI
FEAT33.5.1
ML001U
TMC GUI
FEAT33.5.1.1
ML006U
Current rate display
FEAT33.5.1.2
ML007U
Current DMS display
FEAT33.5.1.3
ML015U
Express lanes event data
FEAT33.5.1.4
ML021U
Express lanes alert box
ML022U
Toll rate/gantry DMS static display
FEAT33.5.1.5
When a rate/mode change occurs the Lane Status DMS shall be updated at the time that the first Toll Rate sign is updated.
The SunGuide Tabbed GUI shall provide an Express Lanes Tab containing controls and real‐
time status information to allow TMC operators to operate the Express Lanes.
The Express Lanes Tab shall include the toll rate and historical or projected effective times for the current and next projected toll rates for each segment, if known; operating mode for the rate; and an indication if a Middleware Rate Adjustment is in progress.
The Express lanes Tab will include the current message displayed on each Toll Rate and Toll Gantry as determined by sign status update messages.
Data on active event associated with an express lanes override to include event id and short event description.
The Express Lanes Tab shall include an Alert Box capable of displaying alerts from the Express Lanes module as defined in requirement ML010U.
The graphic for Toll Rate DMS and Toll Gantry DMS shall include the static text configured in the system for the Toll Rate Sign housing the DMS.
PS
4.3
PS
3.1
PS
3.1
PS
4.3
PS
3.1
PS
3.1
PS
3.1
PS
3.1
248
FEAT33.5.1.6
ML023U
FEAT33.5.2
ML003U
FEAT33.5.2.1
ML003U1
FEAT33.5.2.2
ML024U
FEAT33.5.2.2.1
ML007E
FEAT33.5.2.2.2
ML024U1
FEAT33.5.2.2.3
ML004E6
FEAT33.5.2.2.4
ML005U
Tab information update
The software shall update the data displayed in the Express Lanes tab with current data within 5 seconds of change (or of confirmation of change by a field device or remote interface) without interrupting any operation the Operator is performing or causing loss of operator entered data, so long as adequate machine and network resources are available.
The Tabbed GUI shall provide tools in the Express Lanes Tab allowing the user to place a segment Segment override
into Time‐of‐Day, Closed, Zero Rate, or Manual Rate mode.
The Mode controls shall either be not visible or Mode permissions
should be inactive to users not authorized to use them.
When an Operator changes an Express Lanes segment's mode, the Tabbed GUI shall allow the Override prompt
user to enter additional parameters related to the change in mode.
The Express Lanes Mode Selection shall allow the Select effective time
user to edit the Effective Time for Closed and Zero Rate modes.
The Override Prompt shall not allow the user to No effective time editing for edit the Override Effective Time for the open/manualrate mode
Open/Manual Rate mode.
As the default for the Override Time Prompt, the Override default time
software shall use the system time when the prompt was created.
The mode functionality shall allow the Operator Mode text field
to enter text that is stored as part of the record for a segment mode.
PS
3.1
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
3.1
PS
4.3
249
FEAT33.5.2.2.5
ML004U
Event association capability
FEAT33.5.2.2.5.1
ML004U1
When event association is required
FEAT33.5.3
FEAT33.5.3.1
FEAT33.5.3.2
ML010U
ML010U1
ML010U2
Alerts
No DMS update
Unsuccessful Middleware communication
The Mode Selection and Middleware Rate Adjustment functionality shall allow the Operator to associate the mode or adjustment with an active event by selection from a list of current open events.
If the Event Association flag has been set in the configuration, the Operator Prompt shall require the Operator to associate the Closed and Zero Rate modes with an active event before the mode can be applied. Event Association shall remain optional for Manual Rate, Time‐of‐Day, and Dynamic modes, and the Middleware Rate Adjustment process.
The Tabbed GUI shall alert all Operators granted Express Lanes Alert Permission by generating an alert via the Alert Bar and Alert Box(s) for the scenarios in requirements ML010U1, ML010U2, and ML012U.
If a Toll Rate DMS or Lane Status DMS has not updated successfully after Maximum DMS Resends retries, a DMS Update Failure Alert shall be sent to subscribed Express Lanes clients.
When the Middleware has not responded to a rate change message, not including retries of that message, within the time period specified by the Middleware Response Alert.
PS
4.3
PS
4.3
PS
3.1
PS
4.3
PS
3.1
250
FEAT33.5.3.3
ML011U
Non‐open/normal rate operation
FEAT33.5.3.4
ML012U
Associated event closed
FEAT33.5.3.5
ML031A1
FEAT33.5.3.6
ML010U3
FEAT33.5.3.7
FEAT33.5.3.8
ML010U4
ML010U5
The software shall provide a pop‐up operator alert when an Express Lanes segment is not operating in Open/Normal Rate or Dynamic mode. The alert shall have a period of the Non‐
TOD Alert Frequency.
The software shall provide an alert to subscribed Express Lanes clients if a segment's operating mode is associated with an event and that event is closed while the segment is still in that mode or if the segment state associated with an event is CLOSED and has not been changed within 5 minutes after all travel lane blockages have been removed from the associated event.
If the "Suppress Rate Change Alerts" flag is set, Rate Change Alerts not visible if Rate Change Alerts shall no longer be presented flag set
to users in the Tabbed GUI.
The software shall generate an alert message if Alert for middleware rate middleware rate transmission fails.
transmission
The software shall send the middleware rate transmission failure alert messages to subscribed Express Lanes clients; the message shall include a unique alert ID, segment ID, SunGuide ID, Sunpass Send tranmission failure alert message ID (if error reported by Sunpass), error messages to clients
message (if provided), rate, effective time, failure type (SunGuide‐reported or Sunpass‐reported) and time last attempted.
Details of failure in message
The middleware rate transmission failure alert messages shall provide details of middleware failure if provided by the middleware.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
251
FEAT33.5.3.9
ML034U
Suport alert for an incorrect DMS message
FEAT33.5.4
ML013U1
Express lanes DMS
The software shall support an alert for an incorrect DMS Message message from an authenticated Express Lanes client; the alert shall include client‐generated unique alert ID, a DMS ID, the currently posted message and suggested DMS message.
The Tabbed GUI shall provide tools in the Express Lanes Tab and/or elsewhere for controlling the Toll Rate and Toll Gantry DMS.
Toll Rate DMS, Toll Gantry DMS and Lane Status DMS shall only be controllable by operators with a Toll rate/gantry DMS availability combination of DMS permissions and additional Express Lanes or Express Lanes DMS permissions.
FEAT33.5.4.1
ML025U
FEAT33.5.4.2
ML026U
Current rates displayed
FEAT33.5.5
ML009U
Other tabbed GUI elements
The Tabbed GUI shall provide a means to set the toll rate message displayed on the DMS.
The software shall have the following (subrequirements) other elements to support TMC Operator management of the Express Lanes.
The display of the lane layout in all Event Management GUI screens shall include a double white line delineation between the Express Lanes and General Purpose Lanes.
The Tabbed GUI shall allow operators to create events in the Express Lanes in accordance to existing SunGuide rules for event creation.
FEAT33.5.5.1
ML009U1
Lane layout display
FEAT33.5.5.2
ML009U2
Express lanes event creation
ML037U
The Tabbed GUI shall provide tools in the Express Middleware Rate Adjustment Lanes Tab allowing the user to manage a Middleware Rate Adjustment.
FEAT33.5.6
PS
4.3
PS
3.1
PS
4.3
PS
3.1
PS
3.1
GUI
3.1
PS
3.1
PS
4.3
252
FEAT33.5.6.1
ML037U1
Middleware Rate Override permissions
FEAT33.5.6.2
ML037U2
User Edit
FEAT33.5.7
FEAT33.5.7.1
FEAT33.5.7.2
The Middleware Rate Adjustment controls shall either be hidden or inactive for users not authorized to use them.
In the Middleware Rate Adjustment dialog, the software shall allow a user to edit the rate, Effective Time, and comment and to associate the Adjustment with an event.
Express Lanes Tabbed GUI
ML002I
ML044U
User send messages
Current Rate and Date/Time
FEAT33.5.7.3
Ml046U
Include DMS message
FEAT33.6
ML002
Toll system interface
FEAT33.6.1
ML004I
FEAT33.6.2
ML006I
Except for startup configuration, the Express Lanes tabbed GUI shall not allow a user to send messages including rates whose effective time is earlier than the current time minus the Retroactive Adjustment Limit parameter.
The Express Lanes Tab shall show the current rate and its effective date and time as well as the next rate expected to go into effect (if one is available), whether a pending or scheduled rate, along with its effective date and time.
The Express Lanes Tab will include the DMS message sent by the Pricing Subsystem and the time that DMS message was sent for each Toll Rate DMS.
The software shall communicate toll rate changes to Turnpike systems via Turnpike's Middleware.
The software shall send and receive messages Turnpike WSDL conformance that conform to the WSDL specification provided by the Turnpike.
SunGuide shall process the receipt or non receipt Confirming receipt of variable of a SunGuide Response Message from the rate messages
Middleware confirming receipt of the VariableRate message.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
3.1
PS
3.1
PS
3.1
253
FEAT33.6.3
ML010I
FEAT33.6.3.1
ML002I
FEAT33.6.4
ML010P
FEAT33.6.4.1
ML011P5
FEAT33.6.4.4
ML012I
FEAT33.6.4.5
ML013I
FEAT33.6.4.6
ML014I
Latest send time of toll rate messages
The software shall begin sending a new toll rate to the Middleware no later than 1 minute after the calculation or setting of the effective time.
The software shall only send messages whose Maximum delay in sending rate effective time is no earlier than the current time minus the Middleware Maximum Time After messages
parameter.
The software shall determine the effective time of Toll rate effective time a toll rate prior to sending to the Middleware.
determination
The effective time for a toll rate change on a segment in Time‐of‐Day, Dynamic and Manual Rate modes shall be the greatest Minimum Transit Time or greatest Maximum Transit Time, Effective time for rate increases
as appropriate (as specified by client or per ML009D7), for Toll Rate DMS associated with the segment added to the current time.
If a Toll Rate DMS or Toll Gantry DMS is under manual control, the software shall not send a rate Manual DMS override handling
change message to the Middleware with the manual rate.
When the express lanes are placed into the Closed or Zero Rate modes, the software shall send a rate Effective time for closed and message to the Middleware with an effective time open/zero rate modes
that is the time the mode was entered or otherwise adjusted by the operator.
The effective time for a rate change during Effective time for open/manual Open/Manual Rate mode shall follow the rate mode
requirements for rate changes during Open/Time‐
of‐Day Rate mode.
PS
3.1
PS
3.1
PS
3.1
PS
4.3
PS
3.1
PS
4.3
PS
4.3
254
FEAT33.6.4.7
FEAT33.6.5
FEAT33.7
ML003E
ML015I
ML004S
FEAT33.7.1
ML005S
FEAT33.7.2
ML006S
FEAT33.7.2.1
ML001S
FEAT33.7.2.2
ML003S
FEAT33.7.2.3
ML007S
The Toll Rate DMS, Lane Status DMS and the toll rates communicated to the Turnpike Middleware Rates follow normal operation shall continue to follow normal operational rules rules
regardless of the event entered by an operator.
Middleware heartbeat
Reporting
Crystal reports accessibility
The software shall verify that communications with the Middleware is still active at the Middleware Heartbeat Rate.
The software shall store in the SunGuide database information ‐ as described in the following requirements‐ to enable system personnel to review changes to configuration items, Express Lane status and DMS usage and to produce reports if desired.
The data shall be stored in the SunGuide database and accessible with Crystal Reports.
The software shall track activities related to the Express Lanes.
The software shall store current and expired rate Rate table change tracking
tables.
The software shall store any change attempts to toll rates via the Middleware to include new toll Effective toll rate change rate, segment, effective time, response or lack tracking
thereof from the Middleware, and time of the response.
The software shall store any occasions where the software could not send or ceased to send rate Cessation of change attempts messages to the Middleware due to exceeding the number of retries or a rate message being too old.
Activity tracking
PS
4.3
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
PS
3.1
255
FEAT33.7.2.4
FEAT33.7.2.5
FEAT33.7.2.6
ML002S
ML008S
ML009S
FEAT33.8
FEAT33.8.1
ML032A
FEAT33.8.2
ML033A
FEAT33.8.3
ML045U
The software shall store any change attempts to Express Lanes DMS to include, message content, DMS ID, success in displaying new message or lack Effective DMS change tracking thereof, effective time of the DMS display, and error messages related to changing a DMS message.
Store changes in mode, rate
The software shall store changes in mode, rate, Middleware Rate Adjustments or end of Middleware Rate Adjustment in the database, including the User ID who submitted the request, the request time, rate, effective time, ending time (if provided), Comments Field, segment affected, and event associations.s.
The software shall keep a record of failed Middleware heartbeat tracking Middleware Heartbeats to include time attempted.
Maximum Rate Support
An authorized user will be able to set the Segment Setting maximum toll rate
Maximum Toll Rate for each segment in Administrative Editor.
For a Segment Rate Schedule, the user shall only be able to select Daily Rate Schedules in which no Selecting of Daily Rate Schedule
rate exceeds the Segment Maximum Toll Rate.
Express Lane Tab's Mode Selection functionality
The Express Lanes Tab's Mode Selection functionality shall only apply a mode change if the rate is less than or equal to the Segment Maximum Toll Rate for the selected segment and shall notify a user who attempts to submit a rate that exceeds the limit.
PS
3.1
PS
4.3
PS
3.1
PS
4.3
PS
4.3
PS
4.3
PS
4.3
256
FEAT33.8.4
ML034A
FEAT33.9
FEAT33.9.1
Setting Maximum Toll Rate Parameter
If an attempt is made to set the Segment Maximum Toll Rate parameter for a segment and current or future Segment Rate Schedules associated with that segment include a rate that exceeds the new Segment Maximum Toll Rate, the software shall not implement the change and shall notify the user of the conflict, specifying the Segment Rate Schedule(s) with conflicts and the Daily Rate Schedule(s) used by those Segment Rate Schedule(s) that contain the conflicting rates.
Restart Handling
Ml039U
Display starting state
For each segment upon restart, the software shall display the starting state to the user and allow the user to modify and approve the starting state. The starting state of a segment is defined to be the operating mode, toll rate, effective time, rate history, whether a Middleware Rate Adjustment process is active for the segment and, if so, the rate and effective time.
PS
4.3
PS
4.3
PS
4.3
257
FEAT33.9.1.1
FEAT33.9.1.2
ML039U1
ML039U2
Upon restart, if the last known mode for a segment was Time of Day and the current rates posted on the Toll Rate DMS for a segment are the same, match the last known rate posted and match the Time Of Day rate that would have been in effect for that segment at that time and the Lane Status DMS for that segment matches the text specified for "Operating/Tolling", the Last known Mode Time of Day suggested mode for that segment shall be Time of Day and the suggested rate shall be the rate shown in the Time of Day tables for the current time and the rate actually posted shall be the rate in effect at the time the operator approves the recommendation, which may be different from what was recommended.
Upon restart, if the last known mode for a segment was either Manual or Dynamic and the current rates posted on the configured Toll Rate DMS for a segment are the same and match the last known rate posted for that segment and the Last knwon Mode Manual or Lane Status DMS for that segment matches the Dynamic
text specified for "Operating/Tolling", the suggested mode for that segment shall be Manual and the suggested rate shall be the rate currently posted on the Toll Rate DMS.
PS
4.3
PS
4.3
258
FEAT33.9.1.3
FEAT33.9.1.4
ML039U3
ML039U4
Last Known Mode Closed Suggested Mode Zero Rate Upon restart, if the current rates posted on the configured Toll Rate DMS for a segment match the text specified for Closed mode and the Lane Status DMS message for that segment matches the text specified for Closed mode and either the last known mode was Closed or the text specified for Closed mode differs from that for Zero Rate mode, the recommended mode shall be Closed and the recommended Toll Rate and Lane Status messages shall be those specified for Closed mode.
Upon restart, if the current rates posted on the configured Toll Rate DMS for a segment match the text specified for Zero Rate mode and the Lane Status DMS message matches the text specified for Zero Rate mode for that segment and either the last known mode for that segment was Zero Rate mode or the text specified for Zero Rate mode differs from that for Closed mode, the recommended mode shall be Zero Rate and the recommended Toll Rate and Lane Status messages shall be those specified for Zero Rate mode.
PS
4.3
PS
4.3
259
FEAT33.9.1.5
FEAT33.9.1.6
FEAT33.9.1.7
ML039U5
ML039U6
ML039U7
Time‐of‐Day mode
Upon restart, if the current rates posted on the configured Toll Rate DMS for a segment are the same and do not match the last known rates posted but do match the current rate for Time‐of‐
Day mode, the suggested mode will be Time‐of‐
Day mode with the suggested rate being the rate in the Time‐of‐Day table for the time when activated, which may be different than the rate shown to the operator due to the time required to review and approve the recommended starting state.
Upon restart, if the current rates posted on the configured Toll Rate DMS for a segment are the same, but neither match the last known rates Suggested Mode Manual Mode posted nor the current rate for Time‐of‐Day mode, the suggested mode will be Manual mode with the suggested rate being the posted rate.
Upon restart, if a current message posted on a Toll Rate DMS for a segment cannot be interpreted as a valid rate or if the rates on the configured Toll Rate DMS for that segment are No suggestion for Operating not the same or if the Lane Status DMS is not consistent with the text associated with the mode mode
indicated by the rate comparisons, the software shall make no suggestion to the user for the operating mode or the rate to enter.
PS
4.3
PS
4.3
PS
4.3
260
FEAT33.9.1.8
ML039U8
Upon restart, if the last known state of a segment had a Middleware Rate Adjustment active and a rate update message had been delivered or queued for delivery after the last Middleware Rate Adjustment was delivered or queued for delivery, a Middleware Rate Adjustment will be recommended as the first entry in the rate Recommend Middleware Rate history, independent of the mode and rate, with Adjustment
the last known Middleware Rate Adjustment rate and an effective time set to the effective time of the oldest rate delivered or queued for delivery to the Middleware after the last Middleware Rate Adjustment that was delivered or queued for delivery to the Middleware.
FEAT33.9.1.9
ML039U9
Middleware Rate Override
FEAT33.9.2
ML039U10
User selected Modes
If a middleware rate adjustment was active in the last known state of the segment prior to restart, a middleware rate override recommendation will be inserted immediately after each rate change with an effective time one second prior to the associated rate update and having a rate matching that of the last known middleware rate override.
Upon restart, the user shall only be able to select modes that can be manually selected through the Express Lanes Tab.
PS
4.3
PS
4.3
PS
4.3
261
FEAT33.9.3
FEAT33.9.4
FEAT33.9.5
FEAT33.9.6
ML039U11
ML039U12
ML039U13
ML021I
User specifies mode and rate
Before starting, the user will be required to specify the mode and whether a Middleware Rate Adjustment is in effect and, if so, its rate and effective time. If Manual mode is specified, the user will also be required to specify the rate for the mode. If Closed or Zero Rate mode is specified, the user will also be required to specify the effective time for the mode.
Upon restart, and prior to the start of tolling, the Express Lanes GUI shall display the state of the Assist operator in establishing Toll Rate, Toll Gantry and Lane Status signs as it initial status
does in normal operation, to assist the operator in establishing the initial status.
Prevent operations if middelware rate override
Send message after user approval
The software shall produce an error and prevent submission of the rate history and prevent starting of operations for a segment if the history contains a middleware rate override that would override a rate that was previously successfully delivered or queued for delivery to the middleware and an intervening rate message exists whose effective time is at least 2 hours later than the effective time of the middleware rate adjustment.
Upon restart, the software shall not send a new rate to the Middleware or message to Toll Rate, Toll Gantry or Lane Status DMS until the user has approved the restart mode.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
262
FEAT33.9.7
ML020I
FEAT33.9.8
ML015S
FEAT33.9.9
FEAT33.9.10
ML019I
ML019I
FEAT33.10
FEAT33.10.1
Upon user approval of the restart mode, rate, and middleware rate adjustment data for a segment, Begin approved mode for including edits performed by the operator, the segment
software shall begin the approved mode for that segment.
Upon user approval and start of operations, the user ID and user selections shall be stored in the Store user ID and selection in database in the same way that they would be stored if issued as "Set Mode/Rate" and database
Middleware Rate Adjustment requests.
Prevent start of operations based on rate
Prevent submission of rate history
Data Consistency
Ml016I
Unique SunGuide IDs
The software shall produce an error and prevent submission of the rate history and prevent starting of operations for a segment if a rate in the rate history has an effective time less than or equal to the effective time of the last rate successfully delivered or queued for delivery to the Middleware.
The software shall produce an error and prevent submission of the rate history and prevent starting of operations for a segment if a rate in the rate history has an effective time less than or equal to the effective time of the last rate successfully delivered or queued for delivery to the Middleware.
Maintain data consistency posted to toll rate and gantry dynamic message signe (DMS) and the SunPass Patron system
The Express Lanes module shall use unique sequentially assigned SunGuide IDs with each toll rate message.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.2
263
FEAT33.10.2
ML017I
FEAT33.10.3
ML017I1
FEAT33.10.4
ML017I2
If the Express Lanes module goes down or is restarted, it shall resume trying to send to the Seding rate requests
Middleware all rate requests pending prior to the restart.
Pending rate requests shall be stored in non‐
Storage of pending rate volatile memory, i.e. table(s) in the current requests
SunGuide database.
Upon restart, Express Lanes module shall start up in the Open/Normal mode according to the Start up mode of Express Lanes referenced requirements ML012P, ML017P, ML018P, ML019P and ML020P.
Encounter Error Communication
FEAT33.10.6
FEAT33.10.6.1
ML018I
FEAT33.10.6.2
ML018I1
FEAT33.10.6.3
ML018I2
Speicifies what is recorded when SunGuide encounters and error communication
When SunGuide encounters an error communicating a rate message to the Record rate request details middleware, SunGuide shall record in the database with the rate request details regarding the error.
When SunGuide encounters an error communicating a rate message to the Record rate message
middleware, SunGuide shall record in the database the rate message.
When SunGuide encounters an error communicating a rate message to the Record indication of cause of middleware, SunGuide shall record in the database an indication of the cause of the failure failure
(e.g. sending of message or Middleware processing of the message).
PS
4.2
PS
4.2
PS
4.2
PS
4.3
PS
4.2
PS
4.2
PS
4.2
264
FEAT33.10.6.4
FEAT33.10.6.5
ML018I3
ML018I4
Record error string
When SunGuide encounters an error communicating a rate message to the middleware due to middleware processing failure, SunGuide shall record in the database with the rate request the error string returned by the Middleware.
When SunGuide encounters an error communicating a rate message to the middleware due to communications failure, SunGuide shall Record rate request information record in the database with the rate request information available regarding possible cause of the communications error.
FEAT33.10.7
ML016R
Record SunPass Rate ID
FEAT33.10.8
ML016R1
Display SunPass Rate ID
FEAT33.10.9
ML026A
Configure toll rates FEAT33.10.9.1
ML026A1
Format summary
FEAT33.10.9.2
ML026A2
Run Frequency
FEAT33.10.9.3
ML026A3
Process Data
FEAT33.10.9.4
ML026A4
Configurable Email List
FEAT33.10.9.5
Ml026A5
Email Content
SunGuide shall record the returned SunPass Rate ID with SunGuide rate requests when a rate request succeeds.
SunGuide Toll Viewer shall display the SunPass Rate ID with the SunGuide Rate ID in the Toll Viewer when in detail mode.
The Express Lanes module shall automatically verify at defined configurable frequency for a configurable period that toll rates used by the Middleware match those recorded by Express Lanes module.
This module shall format a summary of the comparison to be sent by email.
The comparison shall run at a configurable frequency.
The comparison shall process data from a configurable period.
The email shall be sent to a configurable email list.
The email shall contain a list of discrepancies found.
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.3
PS
4.2
PS
4.2
PS
4.2
265
FEAT33.10.9.6
ML026A6
FEAT33.10.9.7
ML026A7
FEAT33.10.9.8
ML026A8
FEAT33.10.10
ML017R
FEAT33.10.10.1
ML017R1
FEAT33.10.10.2
ML017R2
If no discrepancies found the summary shall so state.
The email shall state when the comparison Comparison content in email occurred and what period the comparison processed.
The summary shall be divided into sections, each Summary sections
section shall provide the summary for an individual toll segment.
An additional view of the Toll Viewer shall provide Additional view of toll viewer the rates in effect with starting and ending date and time.
The ending time shall be subsequent starting time Defintion of ending time
minus one second.
This view shall be an additional choice added to Additional choices for Toll the Toll Viewer labeled appropriately.
Viewer
Summary content
FEAT33.10.10.3
ML017R3
Time Period display
FEAT33.10.10.4
ML017R4
"Reason" for the toll
FEAT33.10.11
ML010S
Logging to a text file
FEAT33.10.11.1
ML010S1
Frequency of logging
FEAT33.10.11.2
ML010S2
Log file content
Consecutive time periods during which the rate and reason do not change shall appear as a single entry with the beginning time from the first period for that rate and the ending time from the last period with that rate.
The view shall include a "reason" for the toll.
SunGuide shall output all logged DMS messages, toll rate messages, override, and applicable event data to a formatted text file.
This process shall run daily (The use of the word process is not meant to imply this is a separate Windows process.)
Each file produced shall contain 24 hours of data, beginning at 00:00:00 and ending with 23:59:59.
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.2
266
FEAT33.10.11.3
ML010S3
Output data
FEAT33.10.11.4
ML010S4
Output file format
FEAT33.10.11.5
ML010S5
Generation of files
FEAT33.10.11.6
ML010S6
Option to execute logging process
FEAT33.10.11.7
ML010S7
FEAT33.11
FEAT33.11.1
FEAT33.11.2
Order in Log file At the time the process runs it shall output data for all previously missed data runs.
The file format shall be XML of the same format generated by the Toll Viewer Web Service for inclusion in its SOAP messages.
The process shall generate one file per segment per data period.
There shall be an option to cause SunGuide to execute this process on demand and specify the starting date, segment identifier, file name and "destination of the file."
File contents shall be chronologically ordered by the time sent for toll rates and sign messages, time the override was entered by the operator, and event creation time.
Set Mode/Rate Request
ML001M
ML001M6
Allow client to set the mode/rate of segment
The software shall allow an authorized client to set the mode / rate of a segment to include specifying Toll Rate Transit Times for each toll rate DMS and a unique client ID in the DataBus ICD‐
specified refID message field.
The software shall reject a request to set the Reject request to set mode/rate mode / rate of a segment whose rate exceeds the of a segment
Segment Maximum Toll Rate for the submitted segment.
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.2
PS
4.3
PS
4.3
PS
4.3
267
FEAT33.11.3
FEAT33.11.4
FEAT33.11.5
FEAT33.11.6
ML001M7
ML001M8
ML001M9
ML001M10
The software shall require requests to set the mode of a segment to dynamic rate to have Toll Rate Transit Time parameters for Toll Rate DMS Parameter required to set the associated with the segment. In requests to set the mode of a segment to other modes, the mode of segment
request may have all, some or none of these parameters provided.
When a request to set the mode / rate of a segment does not contain Transit Time Request to set mode doesn not parameters, the Minimum Transit Time or contain Transit Time Maximum Transit Time default values for each parameters
Toll Rate DMS shall be used per ML009D7.
Response for each Toll Rate DMS
Receipt of a valid request
While performing the operations directed by an accepted request to set mode/rate of a segment, the software shall provide an individual response for each Toll Rate DMS (including the Gantry DMS) indicating the SunGuide ID associated with the mode/rate request, DMS ID, success or failure to post the rate and the posting time or, if unsuccessful, the last attempted posting time and error message if provided, at the time of such success or failure.
Upon receipt of a valid request to set mode/rate of a segment, the software shall provide a response containing the client‐unique ID provided with the request and the SunGuide ID associated with the mode/rate request.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
268
FEAT33.11.7
FEAT33.11.8
FEAT33.11.8.1
FEAT33.11.8.2
ML001M11
ML002M
ML002M1
ML002M3
The software shall send messages to subscribed express lanes clients indicating success or failure of rate attempts to the middleware. These messages shall include the SunGuide ID, and the Send messages to subscribed time sent or, if unsuccessful, time last attempted, express laness clients
error message (if provided) and identification of source of error report (SunGuide or Sunpass).
The software shall support a request for a middleware rate adjustment for a segment from an Express‐Lanes approved user, regardless of the current operating mode of that segment, which Support request for middleware includes the user ID, a client‐unique ID, segment rate adjustment
ID, rate, effective time and, optionally, ending time, comment and event ID. The event ID shall be required if the Require Event Association Flag is set.
Upon receipt of a valid request for a middleware rate adjustment for a segment, the software shall automatically perform the appropriate actions to Actions performed upon receipt send the appropriate rate message(s) to the of a valid request
middleware without user approval or intervention.
Upon receipt of a valid request for a middleware rate adjustment for a segment, the software shall Provide response containing provide a response containing the client‐unique ID unique ID
and the SunGuide ID associated with the request.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
269
FEAT33.11.9
FEAT33.11.10
FEAT33.11.11
ML025E
ML009D9
Ml009D10
SendRequest for mode/rate change
If a client sends a request for a mode/rate change or a Middleware Rate Adjustment, and specifies an effective time that is in the future or is earlier than the current time minus the number of minutes specified as the Retroactive Adjustment Limit, the software shall reject the request with an “Invalid Effective Time”.
If a valid rate request is submitted, the software shall immediately post the submitted rate on the Post submitted rate on the Toll Toll Rate DMS associated with a segment with the greatest Toll Rate Transit Time for the Time‐of‐
Rate DMS
Day, Dynamic and Manual Rate modes.
Posing Time for toll rate
The posting time for a toll rate on a Toll Rate DMS in Time‐of‐Day, Dynamic and Manual Rate modes shall be the effective time minus that DMS' appropriate (as specified by client or per ML009D7) Transit Time.
PS
4.3
PS
4.3
PS
4.3
FEAT33.12
Alerts
PS
4.3
FEAT33.12.1
Suppress Rate Change Alerts
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
FEAT33.12.1.1
ML031A2
FEAT33.12.1.2
ML031A3
FEAT33.12.2
FEAT33.12.2.1
ML040U
If the "Suppress Rate Change Alerts" flag is set, the software shall automatically acknowledge Pending rate change alert
pending rate change alerts for a segment when a new rate change alert is generated for that segment.
The software shall store whether a pending rate Store pending rate change alert change alert was automatically or manually acknowledged.
Express Lanes alerts
The software shall send Express Lanes alerts to Send alerts to subscribed clients
subscribed Express Lanes clients.
270
FEAT33.12.2.2
ML035U
FEAT33.12.2.3
ML032U
FEAT33.12.2.4
ML032U1
FEAT33.12.2.5
ML033U
FEAT33.12.2.6
FEAT33.12.3
FEAT33.12.4
ML036U
ML042U
Generate alerts
Acknowledge alerts
Upon receipt of an Express Lanes alert from a subscribed Express Lanes client, the software shall generate an alert in the Alert Bar and Alert Box with the data from the alert message.
The software shall allow authorized express lanes clients to acknowledge express lanes alerts.
Express Lanes Alert acknowledgements shall be stored by the software.
The software shall provide a means for an authorized Express Lanes client to request unacknowledged alerts for the Express Lanes and shall send the alert content exactly as it was sent Request Unacknowledged alerts
at the time it was created, including the original unique alert ID, the time at which the alert was generated and associated data.
Software stores alerts
Upon user acknowledgment of an alert from an authenticated express lanes client the software shall send an acknowledgment to subscribed User acknowledgment of alert Express Lanes clients; the acknowledgement shall include the alert originator‐generated unique alert ID and user ID.
Dynamic Mode Failure Alert
Middleware Rate Adjustment alert
When in Dynamic mode and the software does not receive an updated rate from the Express Lanes client sometime within a fifteen minute time‐of‐day interval (i.e. :00‐:15, :15‐:30, :30‐:45 or :45‐:00), the software shall send a Dynamic Mode Failure Alert to subscribed Express Lanes clients.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
271
FEAT33.12.4.1
FEAT33.12.4.2
FEAT33.12.4.3
FEAT33.12.5
FEAT33.13
ML027E
ML028E
ML016S
ML027U
Choose adjustment continue
End of Adjustment Rate
Archive resolution
When a user receives a Middleware Rate Adjustment alert and chooses to have the Adjustment continue, the software shall issue a new rate message to the Middleware, using the Middleware Adjustment rate from the continued adjustment, with an effective time of the previously sent toll rate (the toll rate that triggered the alert), overriding that rate in the middleware.
When a user receives a Middleware Rate Adjustment alert and chooses to have the Adjustment continue, the software shall issue a new rate message to the Middleware, using the Middleware Adjustment rate from the continued adjustment, with an effective time of the previously sent toll rate (the toll rate that triggered the alert), overriding that rate in the middleware.
The software shall archive the creation and resolution of Middleware Rate Adjustment alerts.
The software shall support a subscription request for DMS status changes that provides the Support subscription request following data:
for DMS status changes
oMessage ref ID
oDMS ID
oNew status
Current State Requests
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
272
FEAT33.13.1
ML011M
FEAT33.13.1.1
ML011M2
FEAT33.13.1.2
FEAT33.13.1.3
ML011M1
ML011M3
FEAT33.14
FEAT33.14.1
ML029E
The software shall support a request for express lanes states from Express Lanes clients and shall respond with all configured segments, their Support request for express current operating state, pending (in progress) lane states
state and and whether a Middleware Rate Adjustment is in effect and, if so, the associated rate..
The pending state of each segment reported in response to a request for express lanes state shall include pending modes, rates & effective times, Pending state of each segment DMS IDs and scheduled update times for each associated Toll Rate DMS and associated Event IDs.
Current state of segment
The current state of each segment reported in response to a request for express lanes state shall include current mode, rate & effective time, associated Event IDs, DMS IDs, and messages and posting times for associated DMS (Toll Rate, Toll Gantry, Lane Status), as provided by the Pricing Subsystem.
The Middleware Rate Adjustment of each segment reported in response to a request for Middleware Rate Adjustment of express lanes state shall include whether a Middleware Rate Adjustment is in effect for the each segment
segment, and if so, the rate and effective time and associated Event IDs.
Dynamic Mode
The software shall support a Dynamic operating Support Dynamic Operating mode for each segment that can be entered from Mode
other modes or exited to other modes.
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
PS
4.3
273
FEAT33.14.1.1
ML029E1
Use toll rate
FEAT34
ML001R2
Toll Viewer (TV)
FEAT34.1
ML002R
Detail levels
FEAT34.2
ML003R
Browser support
FEAT34.3
ML002R1
Summary view
FEAT34.3.1
ML004R
Segment selection
FEAT34.3.2
ML001R3
Date selection
FEAT34.3.3
ML001R5
The software shall use the toll rate sent by the valid client request upon entering or maintaining Dynamic mode.
A web based browser application shall be available for users to view data related to the Express Lanes.
The browser shall provide two levels of informational detail: Summary and Detailed
The Toll Viewer shall support Internet Explorer 7.
The Summary View shall provide information for a Customer Service Representative (CSR) to confirm the customer experience during facility usage.
The user (of the Toll Viewer) shall be able to select one or all configured segments (or Toll Gantry) to view data for.
The user shall be able to select a transaction date and time and time range to view data for.
The Toll Viewer Detail Report shall contain DMS message changes only, including the initial request to change, even if it did not succeed, and actual changes (such as when operation is restored); listing the posted message, starting time (time at which that toll rate DMS was requested to change when an update fails and the Toll rate/gantry DMS messages actual update time when an update succeeds) and ending time (1 second prior to next successful posting time), which may be beyond the end of the reporting period or may be blank if the message is still active at the current time.
PS
4.3
TV
3.1
TV
3.1
TV
3.1
TV
3.1
TV
3.1
TV
3.1
TV
4.3
274
FEAT34.3.4
ML005R
Historical rates charged
FEAT34.3.5
ML015R
Event data
FEAT34.3.5.1
ML015R1
Event type
FEAT34.3.5.2
ML015R2
Event start and end time
FEAT34.3.5.3
FEAT34.3.5.4
ML015R3
ML015R4
Event location
Lanes blocked
For the selected segment, the software (the Toll Viewer) shall display the most recent toll rate update, prior to the selected transaction time, communicated to the Middleware (not including retries), the effective time of the toll rate, and the time acknowledged by the Middleware.
For the selected segment, the software will display the following information (subrequirements) for events on both Express and general purpose lanes during the selected time period.
For the selected segment, the software will display the type of event for events on both Express and general purpose lanes during the selected time period.
For the selected segment, the software will display the start and end time of the event for events on both Express and general purpose lanes during the selected time period.
For the selected segment, the software will display the EM event location of the event described for events on both Express and general purpose lanes during the selected time period.
For the selected segment, the software will display data for any lanes that are blocked to include the maximum lane blockage for events on both Express and general purpose lanes during the selected time period.
TV
3.1
TV
3.1
TV
3.1
TV
3.1
TV
3.1
TV
3.1
275
FEAT34.3.5.5
ML006R
Overrides
FEAT34.3.5.6
ML007R
Event geographical range
FEAT34.3.6
ML008R
Ordering of viewed data
FEAT34.3.7
ML009R
DMS name displayed
FEAT34.4
ML010R
Detailed view
FEAT34.4.1
ML010R1
Summary view as basis
FEAT34.4.2
ML011R
Additional DMS data
For the selected segment, the software (the Toll Viewer) shall display information for overrides during the selected time period.
The software (the Toll Viewer) shall include all events located between the configurable segment start and end points, and on parallel pieces of roadway in the opposite direction, both Express and general purpose lanes. The event must have been active during the selected time range.
The data in the Toll Viewer shall be presented in chronological order by gantry.
The software (the Toll Viewer) shall use the DMS Name for CSRs for each DMS displayed in the Basic View.
The Detailed View of the Toll Viewer shall provide information to perform detailed, historical operations reviews
The Detailed View of the Toll Viewer shall include meeting all requirements of the Summary View in addition to these subrequirements unless an explicitly stated otherwise.
In addition to the basic data, the user of the Toll Viewer shall be able to view all DMS message requests, whether they were successful; if unsuccessful, the reason and time as can best be determined; the time of the request; and the time of message posting, if successful.
TV
3.1
TV
3.1
TV
3.1
TV
3.1
TV
3.1
TV
3.1
TV
3.1
276
FEAT34.4.3
ML012R
Additional toll rates data
FEAT34.4.4
ML001R6
Additional override data
FEAT34.4.5
ML013R
Toll viewer access
FEAT34.4.6
ML014R
Toll viewer web service
FEAT34.4.7
ML001R0
Data in detail view
FEAT34.4.8
ML001R14
FEAT34.4.9
ML001R11
FEAT34.4.10
ML001R12
Highlight DMS Rows
The user of the Toll Viewer shall be able to view all toll rates sent to the Middleware, if they were communicated successfully, time of communication, number of retries and confirmation, and time they took effect.
The Toll Viewer Detail Report shall contain who entered the mode, who ended the mode, associated events, and changes to the mode's effective time.
The Toll Viewer application shall be able to be installed on a server located in the SunGuide DMZ.
SunGuide shall provide a web service to access SunGuide and provide data to the Toll Viewer application.
The Toll Viewer Detail Report shall present data in the following order: Effective rates; Rate messages to the Middleware; Mode Changes; Toll Rate DMS messages; Event data
The Toll Viewer Detail Report shall highlight DMS rows in which the message on the sign does not match the scheduled message based on the time at which the message should have been posted.
The Toll Viewer Detail Report shall contain the rate on the sign at the beginning of the requested Posting Time display
reporting period, and shall show its actual posting time.
The Toll Viewer shall allow a user to change the date and time period selection criteria from the Changing data/time selection
data results webpage for the report.
TV
3.1
TV
4.3
TV
3.1
TV
3.1
PS
4.3
PS
4.3
PS
4.3
PS
4.3
277
FEAT34.4.11
ML001R13
Florida Highway Patrol / Computer Aided Dispatch (FHP/CAD)
General
System
FEAT35
FEAT35.1
FEAT35.2
FEAT35.2.1
CA001
FEAT35.2.2
CA002
FEAT35.2.3
CA003
FEAT35.2.4
CA004
FEAT35.2.5
CA005
FEAT35.2.6
Date Entry
The Toll Viewer shall provide a combined date/time text box for entry of the date and time to support pasting a date/time copied from other applications and calendar/dropdown selection controls to support manual entry with the Toll Viewer automatically updating the values in one if the other is changed by the user. This text box shall allow entry of a date formatted as 'M/D/YYYY H:MM:SS AM'.
CA006
An external event alert shall be presented to the SunGuide operator within 60 seconds of a traffic External event alert
incident for a requested location being placed on the FHP CAD FTP server.
The system shall support filtering of FHP traffic Filter FHP incidents by county
incidents by county.
The system shall support filtering of FHP traffic Filter FHP incidents by roadway incidents by a configurable list of FDOT‐covered roadways.
FHP CAD communication failure A SunGuide operator shall be notified of FHP CAD notifications
interface communication failures.
SunGuide operator shall be notified if RCC updates are not received at the FHP CAD server RCC update notifications
within a configurable amount of time.
Consistency with 4.0 functionality
Notifications and data entry related to the handling of FHP CAD incidents shall be consistent with SunGuide Release 4.0.0 functionality.
PS
4.3
FHPCAD
4
FHPCAD
FHPCAD
4
4
FHPCAD
4
FHPCAD
4
FHPCAD
4
FHPCAD
4
FHPCAD
4
FHPCAD
4
278
FEAT35.3
Interface
FEAT35.3.1
CA007
FEAT35.3.2
CA008
FEAT35.3.3
CA009
FEAT35.3.4
CA003F
FEAT35.4
FEAT35.4.1
Traffic incidents shall be accessed from a single Incidents accessed from single configurable location, consisting of separate files location
from each FHP CAD RCC.
Traffic incidents shall be accessed from the FHP Incidents to use existing XML CAD server using the existing XML format.
format
Incident data shall be provided to SunGuide in a format consistent with the SunGuide External Events XML schema.
The FHP CAD interface roadway filter shall utilize the Roadway and the Crosstree information within the messages when applying its roadway Utilize Roadway and Crosstree filter. E.g. if filtering on "I‐95" then messages that information
contain "I‐95 at Commercial" and "Commercial at I‐95" will both match the filter criteria.
Incidents provided via consistent external events format
SunGuide
CA005A
Incidents update/replace existing alerts
Updated FHP CAD incidents shall update/replace existing unacknowledged alerts.
FHPCAD
4
FHPCAD
4
FHPCAD
4
FHPCAD
4
FHPCAD
4.2
FHPCAD
4
FHPCAD
4
279
FEAT35.4.2
CA005A1
External event alert fields
FEAT35.4.3
CA005A2
External event alert action choices
External event alerts from FHP CAD incidents shall include the following fields from the FHP CAD incident, subject to availability in the incoming incident data:
‐ FHP CAD Incident ID
‐ FHP CAD Incident Type
‐ FHP CAD Incident Description and Details (if provided)
‐ Route Designator
‐ Route Direction
‐ Linear Reference, Cross Street, or Mile Marker (if provided)
‐ County
‐ Latitude and Longitude (if provided)
‐ Incident Creation Timestamp
‐ Incident Update Timestamp (if update)
‐ Trooper Dispatch Timestamp (if provided)
‐ Trooper Arrival Timestamp (if provided)
‐ Originating RCC of the Incident
External event alerts with no prior association to SunGuide events shall provide the SunGuide operator with the following action choices:
‐ Create New Event (creates association)
‐ Create Secondary Event (creates association)
‐ Associate with existing SunGuide event
‐ Acknowledge, take no action
‐ Dismiss (providing a reason, e.g. False Alarm)
FHPCAD
4
FHPCAD
4
280
FEAT35.4.4
FEAT35.4.5
FEAT35.4.6
FEAT35.4.7
CA003N
CA003N1
CA002D
CA002D1
FEAT35.4.8
CA002D2
FEAT35.4.9
CA003G
FEAT35.4.10
CA006A
If the FHP CAD incident has not been associated with a SunGuide event, a list of active SunGuide Provide list of active SunGuide events within a configurable radius shall be events within radius
presented to the operator.
A SunGuide event created from an acknowledged Prepopulate event created from FHP CAD incident shall be populated initially from FHP CAD incident
the FHP incident alert data.
All FHP CAD incident data received by SunGuide will be stored in the SunGuide database with appropriate timestamps, preserving the original data received including maintaining Incident data stored in database
latitude/longitude data in micro degrees, updates to the data and operator responses to alerts generated by SunGuide.
Incident alert data stored in database
If an operator dismisses an alert from an FHP CAD incident, the alert and reason for dismissal will be stored in the SunGuide database.
No new alerts created for dismissed incident
If an FHP CAD incident has been dismissed (i.e. as a false alarm), the SunGuide will not create new alerts from the updates to the FHP CAD incident.
SunGuide events created from FHP CAD incidents Display FHP CAD events on map shall be displayed on the SunGuide operator map.
When SunGuide receives updates to alerts that Generate alert upon received have been acknowledged (only) it will generate an updates
alert as if it had not been previously received.
FHPCAD
4
FHPCAD
4
FHPCAD
4
FHPCAD
4
FHPCAD
4
FHPCAD
4
FHPCAD
4
281
FEAT35.4.11
CA005A3
FEAT35.4.12
CA005A4
FEAT35.4.13
CA005A5
Edits to existing SunGuide events shall be performed without obtaining further permission using the following rules: ‐ If the event is owned by the operator handling the alert, the event edits shall be performed Edit to Existing Events without without further operator action. obtaining permission
‐ If the event is (a) un‐owned, (b) owned by a "system" user, or (c) owned by a user that is not logged in, event ownership shall be obtained and event edits shall be performed without further operator action.
Edits to existing SunGuide events shall be performed after obtaining permission using the following rule and exception: ‐ If the event is owned by a logged‐in user other than the user handling the FHP alert, the owning user shall be presented a dialog containing a description of the requested event change and the following three action choices: Edit to Existing Event after + Perform the requested edit while retaining obtaining permission
ownership + Relinquish ownership to the requesting user + Deny the action by the requesting user ‐ If the event‐owning user logs out before selecting an option, event ownership shall be relinquished to the requesting user.
Change requested by one operator to another
When a change requested by one operator to another fails, an alert shall be displayed to the requesting operator, and the dialog from which the request was initiated will be redisplayed if it was previously closed.
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
282
FEAT35.4.14
CA005B
FEAT35.4.15
CA005B1
The Alert Box shall allow users to selectively Alert Box Display Choices
display or hide any combination of individual classes of alerts
Alert classes in the alert box shall be broken out based on the source of the alert. (If multiple types Compositiion of Alert classes in of alerts are received from one subsystem, each alert box
type shall be an independent class)
FEAT35.4.16
CA005C
Response to an FHP event
FEAT35.4.16.1
CA005C1
Archive alert
FEAT35.4.16.2
CA005C2
FEAT35.4.16.3
CA005C3
FEAT35.4.16.4
CA005C4
FEAT35.4.16.5
CA005C5
FEAT35.4.22
CA005E
When SunGuide detects that an FHP event correspondign to a non‐dismissed FHP CAD Alert was in the "previous stream," but not in the current stream, SugGuide shall generate an alert indicating the event was closed.
This alert shall be archived in SunGuide.
This alert shall be part of the event chrono Alert chronology
indicating the FHP CAD closed the event
This alert shall include an option to set the FHP departure time unless the FHP departure time has Alert option to set FHP departure time
already been set or the FHP arrival time has not been set
If this alert includes an FHP arrival time then the Alert option to set FHP arrival alert shall have an option to set FHP arrival and and departure
departure
Sunguide shall not perform the alert checks upon Checks upon receiving the first receiving the first FHP CAD stream after FHP CAD stream
subsystem startup
When an FHP CAD alert is processed by an operator to create or update a SunGuide event Alert processed by an operator
the alert shall become part of the event chrono.
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
283
FEAT35.4.23
FEAT35.4.24
CA005S1
CA005S2
FEAT35.4.25
CA005S3
FEAT35.4.26
CA005S4
FEAT35.4.27
CA0006D
FEAT35.4.27.1
CA006D1
FEAT35.4.27.2
CA006D2
FEAT35.4.27.3
CA006D3
FEAT35.4.27.4
CA006D4
FEAT35.5
FEAT35.5.1
US001
When setting a responder arrival timestamp based on an FHP alert, if the reported trooper Recording of responder arrival arrival time is available and is prior to the current time based on reported arrival system time, the reported trooper arrival time time
shall be recorded as the responder arrival time
When setting a responder arrival timestamp based on an FHP alert, if the reported trooper Recording of responder arrival arrival time is not available or is later than the time based on current system current system time, the current system time time
shall be recorded as the responder arrival time
When setting a responder arrival time for an FHP Setting reponder arrival time for Alert, SunGuide shall use FHP as the arriving FHP alert
agency
When an operator creates an event from an FHP alert and the "trooper arrival time" is in the FHP Setting FHP arrival time
CAD data, then SunGuide shall set the FHP arrival time in the event.
Archiving alerts from FHP CAD SunGuide shall archive alerts from the FHP CAD system
system
SunGuide shall archibe generated timestamps Archive timestamp
associated with those alerts.
SunGuide shall archive the first received alert with Archive first received alert
its timestamp.
SunGuide shall archive changes to the alerts with Archive alert changes
their timestamps.
SunGuide shall archive the "last alert" with its generated timestamp which corresponds to the Archive "last alert"
time that SunGuide detected it was not in the FHP CAD data.
Operator Interaction
THe GUI Preference Manager shall maintain a list Logged‐in users
of currently logged‐in users.
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.3
FHPCAD
4.2
284
FEAT35.5.2
US001P
FEAT35.5.3
US001R
FEAT35.5.4
US001S
FEAT35.5.5
US002
FEAT35.5.5.1
US002H
FEAT35.5.5.2
US002S
FEAT35.5.8
US003
FEAT35.5.9
FEAT35.5.10
US003P
FEAT35.5.11
US003R
FEAT35.5.12
US003S
The GUI Preference Manager shall define a user permission which allows a user with that User permission
permission to retrieve and subscribe to the list of currently logged‐in users.
The list of currently logged‐in users shall be Retrieving logged‐in user
retrievable by a logged‐in user, provided that user has the appropriate permission
The GUI Preference Manager shall allow a logged‐
in user to subscribe to updates of currently logged‐
Subscribing for user updates
in users, provided that user has the appropriate permission.
SunGuide users shall have a User Type attribute User Type attribute
associated to their user record.
The User Type attribute shall allow a user record User Type attribute "belonging to be identified as "belonging to" a human.
to" a human
The User Type attribute shall allow a user record User Type attribute "belonging to be identified as "belonging to" a system to" a system
application
The GUI Preference Manager shall maintain a list Maintain list of users
of all defined users.
The list of all defined users shall include the User List all defined users
Type attribute of each user.
The GUI Preference Manager shall define a user permission which allows a user with that Definition of user Permission
permission to retrieve and subscribe to the list of all defined users.
The list of all defined users shall be retrievable by Retrieval of users based on a logged‐in user, provided that user has the permission
appropriate permission.
The GUI Preference Manager shall allow a logged‐
in user to subscribe to updates of all defined Subscribing to user updates
users, provided that user has the appropriate permission.
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.3
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
285
FEAT35.5.13
US004
FEAT35.5.14
US004D
FEAT35.5.15
US004R
FEAT35.5.16
US004R1
FEAT35.5.17
US004R2
FEAT35.5.18
US004T
FEAT35.5.19
US005
FEAT35.5.20
US005P
FEAT35.5.21
US005R
FEAT35.5.22
US006
The GUI Preference Manager shall provide a Request Action on another user method for a user to request an action of another user.
The GUI Preference Manager shall record all user to user requests and any selected responses to Record user requests
those requests in the database.
A user request to another user shall include some Requesting from one user to number of possible responses the receiver of the another with responses
request may choose from.
A possible response shall include a text Possible response of request description of the action selecting that response with text description
will invoke.
A possible response shall allow for the inclusion of Possible response with XML one or more XML messages that could be sent to messages
one or more SunGuide processes by the receiver of the request.
A user request to another user shall include a text Request from one user to description of the requested action.
another with text description
The GUI shall indicate to a user when an action is awaiting another user's response.
When a user causes a user request to another user to be sent, the GUI shall indicate to the Indication of request pending
originating user that a request is pending.
User's action awaiting response
When a response to a previously‐issued user Indicating result of request to request to another user is received, the GUI shall user
indicate the result of that request to the originating user.
The GUI shall manage a request from another user Display dialog to receiver
by displaying a pop‐up dialog to the receiver of the request.
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
286
FEAT35.5.23
FEAT35.5.24
FEAT35.5.25
US006U
US006C
US006F
FEAT47
FEAT47.1
CV001
FEAT47.3
CV002
FEAT47.4
CV003
FEAT47.5
CV004
When the recipient of a user request to another user confirms a response option which contains one or more messages to send to one or more Sending updated messges to SunGuide subsystems, the GUI shall update those the appropriate subsystems messages with appropriate credentials and send the updated messages to the appropriate subsystems.
Confirmation of message response
When the recipient of a user request to another user confirms a response option, a message shall be sent to the original requestor indicating the response that was selected.
When a user request to another user is received by the other user, a dialog shall be displayed Display available options for containing the text description of the requested handling the request
action and the available options for handling the request.
The software shall implement "Connected Connected Vehicles (CVS)
Vehicle" functionality.
The software shall provide the capability to Configure RSEs
configure roadside equipment (RSE).
The SunGuide configuration file will include a parameter specifying a maximum distance RSE Radius Configuration
between an RSE and a presentation region such that the RSE will automatically be included when selecting RSEs for TAMs.
The software shall provide the ability to configure RSEs as Detectors
TSS detectors to use RSE probe data as the data source.
The software shall provide the ability to associate Zone Id to TSS Link
an RSE Zone Id to a TSS link
FHPCAD
4.2
FHPCAD
4.2
FHPCAD
4.2
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
287
FEAT47.6
CV005
FEAT47.7
CV006
FEAT47.8
CV007
FEAT47.9
CV008
FEAT47.10
CV009
FEAT47.11
CV010
FEAT47.12
CV011
FEAT47.13
CV012
FEAT47.14
CV015
FEAT47.15
CV013
FEAT47.16
CV014
FEAT47.17
CV015
FEAT53
TD007
The software shall provide the ability to configure CV in Response Plans
"Connected Vehicle" messages used by response plans
The software shall be capable of receiving Receive CV data
"Connected Vehicle" data
The software shall transmit generated traveler Traveler Information
information
The SunGuide configuration file will include a parameter specifying a presentation region offset Presentation Region Offset
used when automatically generating a presentation region
The software shall archive "Connected Vehicle" Archive CV Data
data
The software's Graphical User Interface (GUI) shall CV in the GUI
support the ability to display "Connected Vehicle" data
The software shall provide operators the ability to Traveler Advisory Messages generate and manage Traveler Advisory Messages (TAM)
The software shall provide the user the ability to User may Configure RSEs
configure RSEs
The software shall provide a method to review Review RSE Configuration Errors possible errors of configuration of Connected Vehicle TSS integration
The software shall provide the ability to add a Add TAM to Response Plan
TAM to a response plan
The software shall broadcast "Connected Vehicle" CV in C2C
data via Center‐to‐Center (C2C)
The software shall support the ability to Connected Vehicle SDN communicate with a Service Delivery Node (SDN).
Connectivity
INRIX
SunGuide shall support the use of INRIX traffic data.
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
GUI
5.1
288
FEAT53.1
TD007I
Interface Document
FEAT53.1.1
TD007I1
Publish INRIX Data
FEAT53.1.2
TD007I2
County List
FEAT53.1.3
TD007I3
Traffic Condition Data
FEAT53.1.4
TD007I4
Speed Data
FEAT53.1.5
TD007I5
Link and Node Data
FEAT53.1.6
TD007I6
FEAT53.1.7
TD007I7
FEAT53.2
TD007O
FEAT53.2.1
TD007O1
FEAT53.2.2
TD007O2
SunGuide shall provide an interface to INRIX traffic data source that conforms to ITN‐DOT‐
07/08‐9013‐JP Probe‐based Data Collection Concept Test Project Interface Guide Version 1.2 October 17, 2008.
An INRIX C2C Publisher component shall publish INRIX traffic data to the C2C infrastructure, thus making it available to SunGuide and FL‐ATIS.
The INRIX C2C Publisher component shall only publish data from links within a configurable list of counties.
The INRIX C2C Publisher component shall publish C2C Traffic Condition data.
The INRIX C2C Publisher component shall publish C2C Speed data.
The INRIX C2C Publisher component shall publish C2C Link and Node data relevant to the Traffic Condition and Speed links being published.
The INRIX C2C Publisher component shall publish NAVTEQ Source Data
link midpoints based on known map information in a NAVTEQ map source.
The INRIX C2C Publisher component shall notify SunGuide of INRIX data source communication Comm Failures
failures.
The SunGuide Operator Map shall support the INRIX GUI
display of C2C Traffic Condition data.
The SunGuide Operator Map shall display C2C Display Traffic Condition Data Traffic Condition data using on‐map link diagrams.
Selected Networks
The SunGuide Operator Map shall only display C2C Traffic Condition data from networks selected by the operator.
GUI
5.1
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
289
FEAT53.3
TD007O3
INRIX Access
FEAT53.3.1
TD007O4
CSV Writing
FEAT53.3.2
FEAT53.3.3
TD007O5
TD007O6
FEAT57
FEAT59
FEAT59.1
ODS Data to show Centers
C2C Mark Restricted Data
SPARR
DAR001
DAR002
SunGuide shall support limiting access of INRIX traffic data to authorized users.
The SunGuide Data Archive component shall block the writing of restricted data to the TSS CSV files.
The SunGuide Data Archive component shall include data in the ODS tables that will specify the centers from which the data was gathered.
The SunGuide C2C Publisher component shall mark data which was gathered or derived from a restricted source as not for redistribution to third parties.
SunGuide shall support a Road Ranger Application on a smart phone.
DAR
TSS Archive Data
The software shall archive configuration and operational data from TSS.
1.AddDetectorResp
2.ModifyDetectorResp
3.DeleteDetectorResp
4.MapDetectorResp
5.retrieveDataResp (initial data from Databus)
6.statusUpdateInfo (link)
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
SPARR
5.0.5
DAR
5.1.1
DAR
5.1.1
290
FEAT59.2
DAR003
Event Archive Data
FEAT59.3
DAR004
Configurable Time Interval
FEAT59.4
DAR005
UTC in Filename
The software shall archive configuration and operational data from EM.
1.AddActivityResp
2.ModifyActivityResp
3.RemoveActivityResp
4.AddAgencyResp
5.ModifyAgencyResp
6.RemoveAgencyResp
7.AddAgencyContactResp
8.ModifyAgencyContactResp
9.RemoveAgencyContactResp
10.AddColorResp
11.ModifyColorResp
12.RemoveColorResp
13.AddCountyResp
14.ModifyCountyResp
15.RemoveCountyResp
16.AddEventStatusResp
17.ModifyEventStatusResp
18.RemoveEventStatusResp
19.AddCommentTypeResp
20.ModifyCommentTypeResp
21.RemoveCommentTypeResp
22.AddInjuryTypeResp
23.ModifyInjuryTypeResp
24.RemoveInjuryTypeResp
25.AddOrganizationResp
df
The software shall compress the archive on a configurable time interval.
The software shall use a UTC time stamp as part of the filename for of each of the archive files and compressed file
DAR
5.1.1
DAR
5.1.1
DAR
5.1.1
291
FEAT59.5
DAR006
FEAT59.5.1
DAR006A
FEAT59.5.2
DAR006B
FEAT62
FTP Disconnection
In the event the FTP is unavailable, the software shall write the archive files to the local file system.
When the FTP becomes available, the local archive files that were not uploaded, will be sent to the FTP site.
When the local archive files are successfully sent Remove temporary archive files to the FTP site they will be removed from the local file system
Not used yet
FTP reconnection
DAR
5.1.1
DAR
5.1.1
DAR
5.1.1
292
Software Requirements Specification
Appendix B:
SUB REQUIREMENTS
SunGuide-SRS-6.0
SUB
SunGuide ID
SUB1
SUB1.1
SUB1.1.1
SUB1.1.2
SUB1.2
SUB1.2.1
Name
EH ‐ Executive Handler
General
The following shall be configurable Configurable parameters parameters of the EH process:∙ Host name∙ TCP port number
The system shall allow the logging level to Log level
be modified.
EH process
The system shall be able to stop and start processes running on machines reachable Control processes
on the local network.
SUB1.2.2
Heartbeat
SUB1.3
EH viewer
SUB1.3.1
SUB1.3.2
Visibility of processes
Process health
SUB3
IMS ‐ Inventory Management System
IM ‐ Incident SUB3.1
Associate events
SUB3.2
Response plans
SUB2
Requirement Text
Requirements for the EH system.
The system shall be capable of receiving a heartbeat from the system processes.
The system viewer shall be capable of viewing the status of processes for computers on the local network.
The system viewer shall display the health of the various processes in a configurable manner.
The system shall allow an operator to associate a new incident with another, existing incident.
Traced‐from
Subsystem
EH
EH
Version
1
1
FEAT3.2
EH
1
FEAT3.11
EH
1
EH
1
FEAT3.3
EH
1
FEAT3.9
EH
1
EH
1
FEAT3.9
EH
1
FEAT3.9
EH
1
IMS
1
IM
1
IM
1
IM
1
FEAT5.3.14
284
SUB3.2.1
SUB3.2.2
SUB3.2.3
SUB3.3
SUB3.3.1
The IM subsystem shall recommend a Recommend response response plan based on incident location plans
and incident severity.
Predefined response plans
The IM subsystem shall recommend a predefined response plan if one is defined that matches incident location (roadway and direction).
If no predefined response plan exists, then the IM subsystem shall recommend a set of Generated response plan DMS and HAR equipment and messages for each.
FEAT5.3.4
IM
1
FEAT5.3.4
IM
1
FEAT5.3.4
IM
1
IM
1
IM
1
Message formats
Message fields
IM recommended messages shall consist of fields that indicate lane or roadway blockage, proximity to reference location and reference location (cross street).
FEAT5.3.4
285
SUB3.3.2
SUB3.3.3
Lane nomenclature
Single lane blockages
Within an IM recommended message, roadway blockage shall indicate lanes using standard lane nomenclature. If all lanes are blocked the message will use the verb 'CLOSED'.
From innermost lane:
‐ If the lane is ever an HOV lane, then lane is named "HOV LANE'.
‐ The leftmost lane which is not an HOV lane shall be named 'LEFT LANE'.
‐ A lane which begins at an on ramp and ends at an off ramp shall be named 'ON/OFF LANE'.
‐ The rightmost lane which is not an ON/OFF LANE shall be named 'RIGHT LANE'.
‐ Lanes between the LEFT LANE and RIGHT LANE shall be named CENTER LANE.
Messages which describe single lane blockages shall indicate which lane is blocked (i.e., HOV LANE BLOCKED, LEFT LANE BLOCKED).
FEAT5.3.4
IM
1
FEAT5.3.4
IM
1
286
SUB3.3.4
SUB3.3.5
Multi‐lane blockages
Signs off incident roadway
SUB3.3.6
Exit ramp blockage
SUB4
DD ‐ Data Distribution
Messages which describe multi‐lane blockages shall include the number of lanes blocked (as a word: TWO, THREE, etc) and whether the blockage is on the LEFT, CENTER, or RIGHT. All blockages around which traffic may flow in travel lanes are CENTER lane blockages.
Messages for signs not on the roadway with the incident shall include the roadway on which the incident is located and the direction.
Messages which refer to exit ramp blockage shall begin with the phrase EXIT RAMP followed by the destination roadway and the lane configuration.
‐ Full closure of the exit ramp shall state the ramp is CLOSED.
‐ Closure of a mulit‐lane exit ramp shall use standard lane configuration nomenclature (LEFT, RIGHT).
‐ Messages posted on roadways other than that where the incident occurs shall include direction and roadway from which traffic is exiting.
FEAT5.3.4
IM
1
FEAT5.3.4
IM
1
FEAT5.3.4
IM
1
DD
1
287
SUB4.1
SUB4.2
SUB4.3
SUB4.4
Subsystem requests
Route requests to subsystems
Subscribe
ICD
SUB4.5
Provider template
SUB4.6
Status request
SUB5
SUB5.1
SUB5.1.1
The client shall be able to send subsystem requests to the data distribution function and receive subsystem responses.
The data distribution function shall distribute requests from clients to the appropriate subsystems.
The data distribution function shall enable the client to subscribe to status update notifications.
The data distribution function shall provide a published Interface Control Document for client connections.
The data distribution function shall require subsystem ICDs to conform to a provider template.
The client shall be able to request status information from all provider subsystems currently in the system.
FEAT1.7.12
DD
1
FEAT1.7.12
DD
1
FEAT6.3
DD
1
FEAT6.1
DD
1
FEAT1.7.12
DD
1
FEAT6.2
DD
1
GUI
1
GUI
1
GUI
1
GUI ‐ Graphical User Interface (General)
General
Modify system configuration
The system shall provide a configuration editor component to allow authorized users to modify system configuration, including user permissions, equipment setup and device communication.
FEAT1.2.11
288
SUB5.1.2
Reports
SUB5.1.3
Security Levels
SUB5.1.4
Configuration Editor
SUB5.1.4.1
SUB5.1.5
SUB5.1.5.1
The following security levels will be allowed for the various subsystems: Administrator, Manager, Operator, Guest (local), and Guest (remote).
The system shall allow the editing of Editing configurable items configurable items in the configuration file.
FEAT1.7.10
GUI
1
FEAT1.1.7
GUI
1
GUI
1
GUI
1
GUI
1
FEAT1.9.2.1
GUI
1
FEAT1.9.2.1
GUI
1
GUI
1
GUI
1
FEAT1.9.2.1
Administrative editor
Administrative Editor Event Management subsystem pages shall be provided for the configuration of roadways, cross streets, Event management pages relevant lane configurations and Road Ranger activities.
SUB5.1.5.2
Reporting subsystem pages
SUB5.2
Map
SUB5.2.1
The system shall provide authorized users a method of selecting and customizing data reports.
Administrative Editor Reporting Subsystem Pages shall be added for the configuration of Performance Measures.
A Scalable Vector Graphics (SVG) map shall serve as the primary user interface for Map‐based primary GUI operators' daily traffic management activities.
FEAT7.2.4
289
SUB5.2.2
SUB5.2.3
Map icons
Device status
SUB5.2.4
Device control
SUB5.3
CCTV
SUB5.3.1
SUB5.3.2
CCTV icon colors
CCTV error messages
SUB5.3.3
CCTV display all data
SUB5.4
DMS
SUB5.4.1
SUB5.4.2
SUB5.4.3
DMS icon colors
DMS error messages
DMS display all data
The map shall display icons for roadway devices, incidents, and other resources (e.g., fire hydrants).
The map shall provide a method for displaying the current status of any roadway device displayed on the map.
The map shall provide a method for sending appropriate commands to any roadway device displayed on the map.
The colors associated with cctv status icons shall be configurable.
If an error occurs communicating with CCTV, the error message shall be displayed in the status message window.
The GUI shall provide a way to display all data from the CCTV driver for each device.
The colors associated with dms status icons shall be configurable.
If an error occurs communicating with DMS, the error message shall be displayed in the status message window.
The GUI shall provide a way to display all data from the DMS driver for each device.
FEAT5.1.4
GUI
1
FEAT1.7.12
GUI
1
FEAT1.7.12
GUI
1
GUI
2
FEAT7.3.3
GUI
2
FEAT7.3.4
GUI
2
FEAT7.3.6
GUI
2
GUI
2
FEAT7.3.3
GUI
2
FEAT7.3.4
GUI
2
FEAT7.3.6
GUI
2
290
SUB5.4.4
TM013R1
SUB5.4.5
TM013R2
SUB5.4.6
SUB5.5
SUB5.5.1
SUB5.5.2
TM013R3
The User Interface shall provide a method Blank a queue
allowing the MAS queue of a DMS to be blanked
SunGuide shall allow an operator to set the reported message of a DMS to blank if the Blank a non‐Active sign
DMS is not in an Active state.
Operator notification
HAR icon colors
HAR error messages
HAR display all data
SUB5.6
RWIS
SUB5.6.2
SUB5.6.3
GUI
5.1.1
FEAT7.5.6
GUI
5.1.1
FEAT7.5.6
GUI
5.1.1
GUI
2
FEAT7.3.3
GUI
2
FEAT7.3.4
GUI
2
FEAT7.3.6
GUI
2
GUI
2
FEAT7.3.3
GUI
2
FEAT7.3.4
GUI
2
FEAT7.3.6
GUI
2
HAR
SUB5.5.3
SUB5.6.1
If the DMS is not in an Active operational state, the users will be warned that a message will not be sent to the DMS and only the status of the sign shall blank.
FEAT7.5.6
RWIS icon colors
RWIS error messages
RWIS display all data
The colors associated with har status icons shall be configurable.
If an error occurs communicating with HAR, the error message shall be displayed in the status message window.
The GUI shall provide a way to display all data from the HAR driver for each device.
The colors associated with rwis status icons shall be configurable.
If an error occurs communicating with RWIS, the error message shall be displayed in the status message window.
The GUI shall provide a way to display all data from the RWIS driver for each device.
291
SUB5.7
RMS
SUB5.7.1
RMS icon colors
SUB5.7.2
RMS error messages
SUB5.7.3
RMS display all data
SUB5.8
SB
SUB5.8.1
SB icon colors
SUB5.8.2
SB error messages
SUB5.8.3
SB display all data
SUB5.9
TSS
SUB5.9.1
TSS icon colors
SUB5.9.2
TSS error messages
SUB5.9.3
TSS display all data
The colors associated with rms status icons shall be configurable.
If an error occurs communicating with RMS, the error message shall be displayed in the status message window.
The GUI shall provide a way to display all data from the RMS driver for each device.
The colors associated with sb status icons shall be configurable.
If an error occurs communicating with SB, the error message shall be displayed in the status message window.
The GUI shall provide a way to display all data from the SB driver for each device.
The colors associated with tss status icons shall be configurable.
If an error occurs communicating with TSS, the error message shall be displayed in the status message window.
The GUI shall provide a way to display all data from the TSS driver for each device.
GUI
2
FEAT7.3.3
GUI
2
FEAT7.3.4
GUI
2
FEAT7.3.6
GUI
2
GUI
2
FEAT7.3.3
GUI
2
FEAT7.3.4
GUI
2
FEAT7.3.6
GUI
2
GUI
2
FEAT7.3.3
GUI
2
FEAT7.3.4
GUI
2
FEAT7.3.6
GUI
2
292
SUB6.1
CCTV ‐ Closed Circuit Television
Resource arbitration
SUB6.1.1
Lock camera
SUB6.1.2
Unlock camera
SUB6.1.3
Breaking locks
SUB6.2
Control camera
SUB6.2.1
Camera accessibility
SUB6.2.2
Blackout button
SUB6.3
Camera presets
SUB6
SUB6.3.1
Set preset
SUB6.3.2
Select preset
SUB6.4
Video tours
SUB6.4.1
Configure video tours
Requirements for the CCTV system.
The system shall allow a client to request locking of a camera for sole usage.
The system shall allow a client to request unlocking of a camera.
A lock shall be broken by a user with a higher security level requesting the camera or by a timeout from last use of the camera.
The system shall allow a camera to be placed online (accessible) or offline (inaccessible).
The system shall allow an operator to block a camera from being assigned to a predetermined list of outputs.
The system shall allow a preset to be saved for a camera containing the pan, tilt, and zoom positions.
The system shall allow saved preset position information to be sent to a particular camera.
The system shall allow a video tour to be created, modified or deleted.
CCTV
1
CCTV
1
FEAT8.1.4
CCTV
1
FEAT8.1.4
CCTV
1
FEAT8.1.4
CCTV
1
CCTV
1
FEAT8.1.2
CCTV
1
FEAT8.4.5
CCTV
1
CCTV
1
FEAT5.1.4
CCTV
1
FEAT5.1.4
CCTV
1
CCTV
1
CCTV
1
FEAT8.4.5
293
SUB6.4.2
Video tour parameters
SUB6.5
System
SUB6.5.1
SUB7
SUB7.1
SUB7.1.1
SUB7.1.2
SUB7.1.3
Logging
The system shall allow a video tour to be created of a set of cameras in sequence with a dwell time.
The system shall log events and actions including the user name, camera (if applicable), and the status of the event.
DMS ‐ Dynamic Message Requirements for the DMS system.
Signs
Control DMS
The system shall be able to send a message containing MULTI text, display duration, Send message
owner and priority of the message to one or more DMSs.
Terminate message
Set operational status
SUB7.1.4
Set brightness
SUB7.1.5
Control mode
SUB7.1.6
Exercise shutters
The system shall be able to terminate the message on one or more DMSs.
The system shall be able to set the operational status of one or more DMSs to "Active" or "Out of Service".
The system shall be able to set the brightness mode of a DMS to "Auto", "Day" or "Night".
The system shall be able to set the control mode for one or more DMSs.
The system shall be able to exercise the shutters of a DMS.
FEAT8.4.5
CCTV
1
CCTV
1
CCTV
1
DMS
1
DMS
1
FEAT9.3
DMS
1
FEAT9.3
DMS
1
FEAT9.2
DMS
1
FEAT9.2
DMS
1
FEAT9.2
DMS
1
FEAT9.2
DMS
1
FEAT1.7.12
294
SUB7.1.7
Reset controller
SUB7.1.8
SUB7.1.9
SUB7.2
SUB7.2.1
SUB7.2.2
SUB7.2.3
Synchronize clock
DM023
Blanking a sign (blank queue)
The system shall be able to reset the controller of one or more DMSs.
The system shall be able to synchronize the clock on one or more DMSs with the current system time.
FEAT9.2
DMS
1
FEAT9.2
DMS
1
DMS
5.1.1
DMS
1
FEAT9.2
DMS
1
FEAT9.2
DMS
1
FEAT9.2
DMS
1
When a MAS Blank Queue command is executed for a DMS, if the DMS is not out of service, SunGuide shall send a blank sign message to the target DMS.
Query DMS
Status poll
Echo message
Fan status
The system shall be able to query one or more DMSs for their current status. Current status includes operational status, power status, control mode, short lamp status, short pixel status, fan status, brightness mode, temperature (if supported) and the current display.
The system shall be able to query a DMS for the current message display including the MULTI text, the remaining display duration, owner, and priority of the message.
The system shall be able to query a DMS for the status of the fans.
295
SUB7.2.4
Lamp status SUB7.2.5
Pixel status
SUB7.3
System
SUB7.3.1
Configure messages
SUB7.3.2
SUB7.3.3
SUB7.3.4
SUB7.3.5
SUB7.3.6
Approved words
System defaults
Automatic polls
Logging
Timed messages
The system shall be able to query a DMS for the current lamp status including stuck on and stuck off lamps.
The system shall be able to query a DMS for the current status of the pixels on the display.
The system shall allow messages to be composed and saved in the database.
The system shall check messages contain only approved words before saving to the database or sending to a DMS.
The system shall maintain system defaults including a default message and poll cycle times.
The system shall poll DMSs for their current status information on a cyclic basis.
The system shall log events and actions including the user name, DMS (if applicable), message (if applicable), and the status of the event.
The system shall allow specific messages to be identified with specific DMSs. A set of such messages can be activated to run on specific DMSs at specific days of the week and times.
FEAT9.2
DMS
1
FEAT9.2
DMS
1
DMS
1
FEAT9.4
DMS
1
FEAT9.5
DMS
1
FEAT9.6
DMS
1
FEAT9.2
DMS
1
FEAT1.7.12
DMS
1
FEAT9.3
DMS
1
296
SUB7.3.7
SUB7.3.8
SUB7.3.9
DM020
DM020A
DM021
SUB7.3.10
DM022
SUB7.4
DMS04
SUB7.4.1
SUB7.4.2
SUB7.4.2.1
DMS041
DMS042
DMS042A
DMS Polling Interval
DMS Slow Poll
The DMS subsystem shall poll each device at the interval specified for that device.
The DMS subsystem shall increase the polling interval for a device which has failed to respond to a configurable number of commands.
The DMS subsystem shall include the following timestamps for DMS status: last successful poll, last successful send DMS Polling Data Fields
message, and last communication attempt.
Upon receipt of a blank status request from a user with permissions for a non‐Active sign, the DMS subsystem shall send an update to clients reporting a blank message Update clients with blank as the status for the sign until a successful message
poll indicating a different message is received.
Color DMS
NTCIPv2 Support
Color DMS Templates
Standard DMS layout
The software shall additionally support the NTCIP version 2 protocol
The software shall have a standard color DMS layout for creating color DMS messages and templates
The standard color DMS layout shall include one graphic and one text message per phase
DMS
DMS
DMS
DMS
5.1.1
DMS
6
DMS
6
DMS
6
DMS
6
297
SUB7.4.2.2
DMS042B
Graphic Height
SUB7.4.2.3
DMS042C
Graphic Aspect Ratio
SUB7.4.2.4
DMS042D
Graphic Left Justified
SUB7.4.2.5
DMS042E
DMS Text Area
SUB7.4.2.6
DMS042F
Centered Text
SUB7.4.2.7
DMS042G
Text Too Large
SUB7.4.2.8
SUB7.4.2.8.1
SUB7.4.3
DMS042H
DMS042H1
DMS043
Removing the Graphic
The graphic shall occupy the entire height of the sign
The graphic shall maintain its aspect ratio
The graphic shall be left justified within the layout
The text area shall be the remaining portion of the layout not occupied by the graphic
The text message shall be centered within the text area
In the event that the text is too large to fit in the text area, text will be placed on the next phase on the DMS message.
When generating a response plan, if the text is too large to fit in the text area after abbreviations are applied a response plan shall remove the image and the text area will occupy the entire layout.
If a message generated using templates within a response plan is unable to fit on the DMS sign, the user shall have the Adding sign to a response option of adding the sign to the response plan
plan and manually specifying the message.
Graphics Library
The software shall have a graphics library with add and delete functionality for color DMS images to be used in the messages or templates.
DMS
6
DMS
6
DMS
6
DMS
6
DMS
6
DMS
6
DMS
6
DMS
6
DMS
6
298
SUB7.4.3.1
SUB7.4.3.2
DMS043A
DMS043B
SUB7.4.3.3
DMS043C
SUB7.4.3.3.1
DMS043C1
SUB7.4.3.3.3.1
DMS043C3A
SUB7.4.3.3.4
DMS043C4
Icon type
The graphics shall have information stored with them to indicate if they are a shield of a roadway, an icon associated with an event type, or just an image with no association.
The software shall verify images and messages each time a message is activated Content of message to on the sign using a cyclic redundancy check sign
on the message and on each image
The software shall handle the scenario of a user attempting to delete a graphic that is Deleting graphics in use associated to one or more stored or active messages.
The user will be notified of the list of messages that have the graphic associated to them.
If a subsystem which uses DMS graphics is not running when a user attempts to delete Unable to Disassociate a graphic, the user shall be notified this check cannot be performed.
Notification
User Notification
If the graphic is in use in a stored or active message at the time the user tries to delete the graphic, the user shall be unable to Notification of graphic delete the graphic and be notified of the use
locations where the graphic is in use.
DMS
6
DMS
6
DMS
6
DMS
6
DMS
6
DMS
6
299
SUB7.4.4
DMS044
Color DMS message template generation
SUB7.4.4.1
DMS044A
Background and Text Color
SUB7.4.4.1.1
DMS044A1
MUTCD Colors
SUB7.4.4.1.1.1
DMS044A1A
Text Color Options
SUB7.4.4.1.1.2
DMS044A1B
Background Color Options
SUB7.4.4.1.2
DMS044A2
Default Colors for EM templates
SUB7.4.4.1.3
SUB7.4.4.1.4
DMS044A3
DMS044A4
The software shall support color DMS message and color DMS message template generation
The software shall allow the user to change the default background and default text color of messages and message templates.
For user defined color schemes, the software shall present the user with options of color that are allowed by the MUTCD.
Text color options are red, white, yellow, orange, fluorescent yellow‐green, fluorescent pink, and amber.
Background color options are black, blue, green
The software shall provide a default background color of black and default text color of yellow for event management templates.
The software shall provide a default background color of black and default text Background Colors other color of amber for all templates other than event management templates.
than EM
Using graphics in templates
The software shall generate color DMS messages from templates for events using graphics available in the graphic library
DMS
6
DMS
6
DMS
6
DMS
6
DMS
6
DMS
6
DMS
6
DMS
6
300
SUB7.4.4.1.4.1
DMS044A4A
Using Event Type Graphic
SUB7.4.4.1.4.2
DMS044A4B
Using Shield Graphic
SUB7.4.4.1.5
SUB7.4.5
DMS044A5
DMS045
SUB8.1
SUB8.1.2
Color DMS Display
TSS ‐ Transportation Sensor System
SUB8
SUB8.1.1
Travel time template shield graphic
Raw data
TD020
TD021
If the event type graphic is available, it shall be used
If the event type graphic is not available and the shield corresponding to the incident's location is available, the shield graphic shall be used
The software shall allow the user to select the appropriate shield graphic for a device's travel time template.
The software shall support color DMS message status display showing a visual representation of each pixel of the sign that shall appear in the short status, detailed status, and hover over of the DMS sign from the operator map.
Requirements for the TSS system.
The system traffic flow information output shall include raw data.
FEAT10.8
DMS
6
DMS
6
DMS
6
DMS
6
TSS
1
TSS
1
The software shall support the reporting of speed, volume, and occupancy by lane, Possible Reporting Lanes when available, for at least 10 lanes from a single detector.
Link Status Dialog Content
The TSS Link Data status dialog shall support the reporting of speed, volume, and occupancy for at least 10 lanes of travel from a single TSS link.
301
SUB8.1.3
TD022
SUB8.2
Archiving Lane Status
Smoothed data
SUB8.3
Smoothing algorithm
SUB8.4
Automatic polls
SUB8.5
Logging
SUB8.6
Traffic Detector Failure Alerts
SUB8.6.1
TD016A
Email Alerts
SunGuide shall support archive speed, volume, and occupancy by lane for at least 10 lanes of a TSS link.
The system output shall include smoothed traffic flow information.
The system shall support a smoothing algorithm that takes a simple average of raw traffic flow data over a given sampling period.
The system shall poll TSSs for their current status information on a cyclic basis.
The system shall log events and actions including the user name, TSS (if applicable), message (if applicable), and the status of the event.
When a traffic detector's operational status changes to the failed state and remains there at least as long as the Traffic Detector Failure alert delay period, the software shall send a Traffic Detector Failure alert via email to users with permission to receive these alerts.
FEAT10.8
TSS
1
FEAT10.8
TSS
1
FEAT1.7.12
TSS
1
FEAT1.7.12
TSS
1
TSS
5.1
302
SUB8.6.2
SUB8.6.3
TD016B
TD016C
SUB8.7.2
Status Logger Alerts
Traffic Detector Failure alerts shall be logged in the Status Logger
System‐wide Traffic Detector Alerts
SUB8.7
SUB8.7.1
Email alert content
Traffic Detector Failure alerts shall contain the detector and the time the detector entered the failed state
TD017A
TD017B
The SunGuide Admin Editor shall contain configurable value for the threshold of a System Wide System‐wide Traffic Detector Failure alert, Configurable Threshold
stored as a percentage.
Email Alert
When the percentage of traffic detectors with a failed operational state exceeds the threshold configured in the SunGuide Admin Editor and remains above the threshold at least as long as the System‐
wide Traffic Detector Failure alert delay period, the software shall send a System‐
wide Traffic Detector Failure alert email to users with permission to receive these alerts
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
303
SUB8.7.3
SUB8.7.4
SUB8.7.5
SUB8.7.6
SUB8.8
TD017C
TD017D
TD017E
TD017F
System‐wide alert permission
When the percentage of traffic detectors with a failed operational state exceeds the threshold configured in the SunGuide Admin Editor and remains above the threshold at least as long as the System‐
wide Traffic Detector Failure alert delay period, the software shall send a System‐
wide Traffic Detector Failure alert to logged‐
in users with permission to receive these alerts
When determining the percentage of traffic detectors with a failed operational state, the number of detectors in the failed operational state shall be compared to the Percentage Calculation total number of detectors, excluding detectors with an out of service operational status
System Message
Status Log Message
Invalid Detector Data Alerts
The System‐wide Traffic Detector Failure alert shall be presented to users in the System Messages dialog
System‐wide Traffic Detector Failure alerts shall be logged in the Status Logger
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
304
SUB8.8.1
SUB8.8.2
SUB8.8.3
SUB8.8.4
SUB8.8.5
TD018A
TD018A1
TD018A2
TD018B
TD018B1
Detector Thresholds
Detector Threshold
From the SunGuide Admin Editor, an authorized user will be able to configure a set of timed thresholds for all detectors for generating Invalid Detector Data alerts.
An Invalid Detector Data alert threshold shall consist of a start time of day, an end time of day, and minimum and maximum Speed, Occupancy, and Volume values
The software shall not allow a user to create or modify an Invalid Detector Data Threshold Configuration alert threshold if it would overlap with the time range defined by another existing Overlap
threshold
The software shall generate an Invalid Detector Data alert when it detects an invalid detector data condition that remains Alert Initial Generation there at least as long as the Invalid Detector Criteria
Data alert delay period
A threshold shall be considered in effect if the current time of day is greater than or equal to the start time of the threshold and Threshold Effective Times
is less than the end time of the threshold
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
305
SUB8.8.6
TD018B2
A lane shall be considered to be reporting invalid data if that lane’s reported speed, occupancy, or volume are outside the Alert Generation Criteria bounds of the effective threshold for the current time of day
SUB8.8.7
TD018B3
Email Alert
SUB8.8.8
TD018C
Email Alert Content
SUB8.8.9
TD018D
Status Log Message
SUB8.9.2
SUB8.9.3
Invalid Detector Data alerts shall contain the detector, link, and lane that generated the alert
Invalid Detector Data alerts shall be logged in the Status Logger
Alert Generation Delay Threshold
SUB8.9
SUB8.9.1
If a lane reports invalid data for at least as long as the Invalid Detector Data alert delay period, the software shall send an Invalid Detector Data alert via email to users with permission to receive these alerts
TD019A
The delay threshold shall be the number of minutes the conditions generating the alert Delay Threshold Content shall be present before and alert is generated.
TD019A1
Delay Threshold Configuration
A delay threshold for Traffic Detector Failure alerts shall be configurable in the SunGuide Configuration File
TD019A2
Delay Threshold Configuration
A delay threshold for System‐wide Traffic Detector Failure alerts shall be configurable in the SunGuide Configuration File
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
306
SUB8.9.4
SUB8.9.5
TD019A3
TD019B
SUB8.10
Delay Threshold Configuration
Resend Conditions
A delay threshold for Invalid Detector Data alerts shall be configurable in the SunGuide Configuration File
The software shall not send a new Traffic Detector Failure, System‐wide Traffic Detector Failure, or Invalid Traffic Detector Data alerts until the conditions that caused the alert no longer exist for a period of time equal to the delay threshold corresponding to the alert type
Classification Data
SUB8.10.1
TD023
Classification Data Collection
SUB8.10.2
TD024
Archive Classification Data
SUB8.10.3
TD025
SUB8.10.4
TD026
The software shall support the reporting of up to 8 different vehicle classifications from a single detector.
The software shall archive up to 8 different vehicle classifications for a single detector.
The software shall average the classification Rollup Classification Data data on 15 minute, 1 hour, and 24 hour intervals
The software shall purge raw classification data from the database at a configurable Purge Classification Data
interval
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
TSS
5.1
307
SUB8.11
TM025A
SUB8.12
TM025B
SUB8.13
TM025C
SUB8.14
SUB8.14.1
TM025D
TM025D1
Tag Discard Horizon
TAG_DISCARD_HORIZON [seconds]: The software will store non‐discarded matches and previously read tags in volatile memory for both matching and duplicate detection purposes until the match or tag has been stored for the amount of time specified by this value, at which time they will be discarded.
SPEED_ANOMALY_TH [MPH]: The software will discard matches that calculate to a Speed Anomaly Threshold
speed higher than the SPEED_ANOMALY_TH.
MAXIMUM_SPEED_TH [MPH]: The software will change the value of the speed in a match to the MAXIMUM_SPEED_TH if the raw speed value is greater than the Maximum Speed MAXIMUM_SPEED_TH and less than or Threshold
equal to the SPEED_ANOMALY_TH
Storing matches
Filtered matches
The algorithm will independently store the non‐discarded matches as filtered matches as well as unfiltered matches.
Filtered matches are the set of non‐
discarded matches that also passed through the filter condition and are averaged for the final speed output
TSS
5.1.1
TSS
5.1.1
TSS
5.1.1
TSS
5.1.1
TSS
5.1.1
308
SUB8.14.2
SUB8.15
SUB8.16
SUB8.17
TM025D2
TM025E
TM025F
TM025H
Unfiltered matches
Sample size
Unfiltered matches are the set of the non‐
discarded matches regardless if they were filtered and will be used as the set of matches to average for the current conditions for which to use in the filtering stage of the algorithm
SAMPLE_SIZE [number of matches]: The software shall not calculate a speed average unless the amount of samples available is greater than the SAMPLE_SIZE parameter.
SPEED_TH [delta MPH]: The software will filter any matches from being used in the final output value if the speed value of the Speed Threshold (delta) match differs from the current conditions by more than the SPEED_TH value
Final Speed output
The average of the speed values from the filtered matches will be used as the final speed output and the average of the speed values from the unfiltered matches will be used as the unfiltered speed value, which is used for comparison between incoming matches and current conditions.
TSS
5.1.1
TSS
5.1.1
TSS
5.1.1
TSS
5.1.1
309
SUB8.17.1
SUB8.17.2
SUB8.17.3
SUB8.17.4
TM025H1
TM025H2
TM025H3
TM025H4
Sample Size usage (filtered avg)
If the number of filtered matches available in volatile memory is less than the SAMPLE_SIZE, then the speed average will not be produced
If the number of filtered matches available in volatile memory within a speed calculation period is less than the SAMPLE_SIZE, then the most recent filtered Using historical filtered matches will be used until the sample size is matches
equal to the SAMPLE_SIZE parameter
If the number of filtered matches available within a speed calculation period is greater than or equal to the SAMPLE_SIZE, then the filtered matches within the speed Speed output calculation calculation period will be averaged to criteria
calculate the average speed value
Limited sample size behavior
If the number of unfiltered matches available in volatile memory is less than the SAMPLE_SIZE, then the average speed will not be calculated
TSS
5.1.1
TSS
5.1.1
TSS
5.1.1
TSS
5.1.1
310
SUB8.17.5
SUB8.17.6
SUB9
SUB9.1
SUB9.1.1
SUB9.1.1.1
SUB9.1.1.2
TM025H5
TM025H6
Sample Size usage (unfiltered average)
Unifiltered average calculation
If the number of unfiltered matches available within a speed calculation period is less than the SAMPLE_SIZE, then the most recent unfiltered matches in volatile memory will be used until the sample size is equal to the SAMPLE_SIZE parameter. The average of this data set will be the unfiltered speed value.
TSS
5.1.1
TSS
5.1.1
EC
1
EC
EC
1
1
FEAT11.4.1
EC
1
FEAT11.4.4
EC
1
If the number of unfiltered matches available within a speed calculation period is greater than or equal to the SAMPLE_SIZE, then the unfiltered matches within the speed calculation period will be averaged to calculate the unfiltered speed value
EC ‐ Evacuation Coordination
EG ‐ Evacuation Guidance
General
Distinguish between evacuation zones
Ability to define geoboundaries
SunGuide shall distinguish between evacuation zones that are currently under government orders to evacuate and those that are not.
EG shall provide a means for the operator to specify boundaries based on describable features and landmarks that will be used to define evacuation zones.
311
SUB9.1.1.3
EG shall provide the ability for the user to specify up to N number of evacuation Categories of evacuees categories and allocate the categories to each evacuation zone.
SUB9.1.1.4
EOC priority
SUB9.1.2
Inputs
SUB9.1.2.1
SUB9.1.2.2
SUB9.1.2.3
SUB9.1.2.4
Shelter‐in‐place input
Destinations input
EC
Priority is given to SERT/SEOC for access to and control of ITS devices at all SunGuide TMCs when a state of emergency has been declared.
Information relevant to the evacuation zones shall include boundaries of the Determine evacuation evacuation zones and their extent on the zone input
GUI map display.
Evacuation zone input
FEAT11.4.4
EG shall provide a graphical tool for the marking of evacuation zones using pre‐
determined boundaries tied to describable features and identifiable landmarks.
Information relevant to the need to shelter‐
in‐place shall be entered into the system via manual data entry forms.
Manual data entry forms shall be provided for the user to enter information relative to the alternate evacuation destination.
1
1
EC
1
FEAT11.4.1
EC
1
FEAT11.4.4
EC
1
FEAT11.4.3
EC
1
FEAT11.4.5
EC
1
312
SUB9.1.2.5
SUB9.1.2.6
SUB9.1.2.7
SUB9.1.2.8
SUB9.1.2.9
SUB9.1.2.10
SUB9.1.3
SUB9.1.3.1
SUB9.1.3.2
Information relevant to evacuation shelters shall be entered into the system via manual Evacuation shelter input
data entry forms.
Hazardous conditions input
Information relevant to hazardous conditions shall be entered into the system via manual data entry forms.
Information relevant to weather conditions shall be entered into the system via manual Weather conditions input
data entry forms.
Information relevant to transportation Transportation modes modes shall be entered into the system via input
manual data entry forms.
Evacuation guidance input
Information relevant to evacuation guidance shall be entered into the system via manual data entry forms.
Information relevant to lodging availability shall be entered into the system via manual Lodging availability input
data entry forms.
FEAT11.4.8
EC
1
FEAT11.5.3
EC
1
FEAT11.5.4
EC
1
FEAT11.5.5
EC
1
FEAT11.5.6
EC
1
FEAT11.5.7
EC
1
EC
1
FEAT11.4.4
EC
1
FEAT11.4.3
EC
1
Displays
Evacuation zone information shall be provided to potential evacuees via a static Display evacuation zones web page accessible through the Internet.
Shelter‐in‐place information shall be available through the Internet via a static Shelter‐in‐place display
web page accessible through the Internet.
313
SUB9.1.3.3
SUB9.1.3.4
SUB9.1.3.5
SUB9.1.3.6
SUB9.1.3.7
Alternative evacuation destinations information shall be provided via a static Evacuation destinations web page accessible through the Internet.
display
Information fields
Shelter display
Weather conditions display
The EG shall, at a minimum, provide a free text field that can contain up to 255 alpha‐
numeric characters.
Evacuation shelters information shall be provided via a static web page accessible through the Internet.
Weather conditions information shall be provided via a static web page accessible through the Internet.
Transportation modes information shall be provided to potential evacuees via a static Transportation modes web page accessible through the Internet.
display
Evacuation guidance display
Evacuation guidance information shall be provided via a static web page accessible through the Internet.
SUB9.1.3.9
Lodging availability display
Lodging availability information shall be provided via a static web page accessible through the Internet.
SUB10
RWIS ‐ Road Weather Information System SUB11
C2C ‐ Center to Center
SUB9.1.3.8
Requirements for the C2C system.
FEAT11.4.5
EC
1
FEAT11.4.5
EC
1
FEAT11.4.8
EC
1
FEAT11.5.4
EC
1
FEAT11.5.5
EC
1
FEAT11.5.6
EC
1
FEAT11.5.7
EC
1
RWIS
2
C2C
2
314
SUB11.1
SUB11.1.1
System
Network ID
SUB11.1.2
Retrieve data
SUB11.1.3
Incidents
SUB11.1.4
Traffic data
SUB11.1.5
Roadway segments
SUB11.2
Status
SUB11.2.1
SUB11.2.2
SUB11.2.3
DMS
HAR
CCTV
The SunGuide system shall require each connection (i.e., TMC or remote user) to supply a network identifier.
The system shall allow a network to retrieve device status information from another network.
The system shall allow a network to send incident information to another network.
The system shall allow a network to send traffic data including speed, volume, occupancy and travel times to another network.
Roadway segments shall be designated by two nodes and a link as defined in the ICD.
The system shall maintain the most current DMS status information for DMSs in the connected networks.
The system shall maintain the most current HAR status information for HARs in the connected networks.
The system shall maintain the most current CCTV status information for CCTVs in the connected networks.
C2C
2
FEAT13.3
C2C
2
FEAT13.3
C2C
2
FEAT13.3
C2C
2
FEAT13.3
C2C
2
FEAT13.3
C2C
2
C2C
2
FEAT13.3
C2C
2
FEAT13.3
C2C
2
FEAT13.3
C2C
2
315
SUB11.2.5
RWIS
SUB11.3
Control
SUB11.3.1
SUB11.3.2
DMS
HAR
SUB11.3.3
CCTV
SUB12
SUB12.1
DA ‐ Data Archiving
General
The system shall maintain the most current RWIS status information for RWISs in the connected networks.
The system shall allow a network to send a command request to a DMS in another network.
The system shall allow a network to send a command request to a HAR in another network.
The system shall allow a network to send a command request to a CCTV in another network.
The Data Archive shall be tunable to archive each data type in the range of 0 minute to 60 minutes (a 0 indicates no logging is to occur for the data type).
FEAT13.3
C2C
2
C2C
2
FEAT13.3
C2C
2
FEAT13.3
C2C
2
FEAT13.3
C2C
2
DA
DA
2
2
FEAT14.2
DA
2
SUB12.1.1
Archive frequency
SUB12.1.2
Missing data
If data is not available, an entry of "n/a" shall be included in the detailed data line.
FEAT14.2
DA
2
SUB12.1.3
Organization
Each subsystem's data that is archived shall be in a separate data file.
FEAT14.2
DA
2
316
SUB12.1.4
Formatting
SUB12.2
Archive files
SUB12.2.1
File duration
SunGuide archived data shall be in comma separated values (CSV) format that can be converted to fixed field length data by the FDOT.
DA
2
DA
2
FEAT14.2
DA
2
FEAT14.2
DA
2
FEAT14.2
DA
2
File header contents
The first line (header line) of each data file shall contain comma separated descriptive names for the detailed data to be logged.
FEAT14.5
DA
2
SUB12.2.5
File detailed contents
Each detail line of the archive file shall contain comma separated fields.
FEAT14.5
DA
2
SUB12.3
Types of archives
DA
2
SUB12.3.1
System log archives
DA
2
SUB12.2.2
SUB12.2.3
SUB12.2.4
Archive files shall contain 24 hours of data (midnight to midnight).
The location of the archive files shall be configurable.
The archive file name shall be in the following format:
<subsystem name>‐<date>‐<log interval>
Where: <subsystem> acronym for subsystem (e.g. TSS, or RWIS)∙ <date> is the Filename specifications
date in MMDDYYYY format∙ <log interval> is in an integer in the range of 1 min to 60 min.
File location
The status of the SunGuide processes shall be maintained in the SunGuide Status Logger files.
FEAT14.4
FEAT14.3
317
SUB12.3.2
Device status archives
SUB12.3.3
Incident archives
SUB12.3.4
SUB12.3.4.1
SUB12.3.5
DA03D
DA03D1
Detector data archives
The status of SunGuide devices shall be maintained in the SunGuide Status Logger files.
For each SunGuide incident, the following detailed information shall be archived:∙ Timestamp (HH:MM:SS 24 hour format)∙ Incident ID∙ User∙ Event details∙ History of event
For each TSS detector defined in the SunGuide software, the following detailed information shall be archived:∙ Timestamp (HH:MM:SS 24 hour format)∙ Detector identifier∙ Speed (MPH, range 0 to 65535, in 1 MPH increments)∙ Occupancy (0 to 100 % in 1% increments)∙ Volume (raw counts, 0 to 65535), and Classification data in up to 8 bins
FEAT14.3
DA
2
FEAT14.3
DA
2
FEAT14.3(s)
DA
5.1.1
DA
6
DA
2
The rollup average for a TSS link shall Rollup ‐ Volume weight the speed on each vehicle in the Weighted Speed Average rollup interval equally.
Travel time archives
For each travel time link defined in the SunGuide software, the following detailed information shall be archived:∙ Timestamp (HH:MM:SS 24 hour format)∙ Travel time link identifier∙ Travel time (in minutes)
FEAT14.3
318
SUB12.3.6
SUB12.3.7
SUB12.3.8
RWIS archives
HAR archives
DMS archives
For each RWIS detector defined in the SunGuide software, the following detailed information shall be archived:
‐Timestamp (HH:MM:SS 24 hour format)∙ RWIS identifier∙ Air temperature ∙ Dew point temperature ∙ Relative humidity ∙ Precipitation type∙ Precipitation intensity ∙ Precipitation rate ∙ Air pressure ∙ Visibility∙ Average wind speed∙ Wind gust speed ∙ ‐
Wind direction ∙ Surface sensor index ∙ Surface temperature ∙ Freeze point ∙ Chemical factor ∙ Ice thickness
For each HAR device defined in the SunGuide software, the following detailed information shall be provided through the status logger files:∙ Timestamp∙ HAR identifier∙ User issuing command∙ Message (in text format)∙ Message duration
For each DMS device defined in the SunGuide software, the following detailed information shall be provided through the status logger files:∙ Timestamp∙ DMS identifier∙ User issuing command∙ Message (in text format)∙ Message duration
FEAT14.3
DA
2
FEAT14.3
DA
2
FEAT14.3
DA
2
319
SUB12.3.9
SUB13
SUB13.1
Ramp meter archives
For each Ramp Meter device defined in the SunGuide software, the following detailed information shall be provided through the status logger files:∙ Timestamp∙ Ramp meter identifier∙ User issuing command∙ Command settings (in text format, i.e., override of metering plan, change of mode, turn on ramp meter)∙ Metering rate∙ Mode control (local vs remote) ∙ Communications archive (short term weekly archive, e.g., record of communications with ramp meter)
FEAT14.3
DA
2
HAR
2
HAR
2
FEAT1.7.12
HAR
2
FEAT1.7.12
HAR
2
FEAT1.7.12
HAR
2
HAR
2
HAR ‐ Highway Advisory Radio
System
SUB13.1.1
Automatic polls
SUB13.1.2
Logging
SUB13.1.3
HAR Interface
SUB13.2
Control HAR
The system shall maintain HARs current status information.
The system shall log events and actions including the user name, HAR (if applicable), text of the message (if applicable), and the status of the event.
The HAR subsystem shall interface to the Highway Information System DR2000 using the DR2000 Software Interface Module.
320
SUB13.2.1
SUB13.2.2
SUB13.2.3
Send message
Terminate message
Set operational status
SUB13.2.4
Activate/deactivate beacon
SUB14
SUB14.1
SL ‐ Status Logging
General
SUB14.1.1
SUB14.1.2
The system shall allow a text message to be sent to a HAR or multiple HARs.
The system shall allow the message currently being broadcast on a HAR to be terminated.
The system shall be able to set the operational status of one or more HARs to "Active" or "Out of Service".
The system shall allow the beacons to be activated or deactivated independently of broadcasting a message or as part of a message.
The following shall be configurable parameters of the logging process:∙ Host name∙ TCP port number∙ File directory Configurable parameters
location ∙ Log rollover interval∙ File reuse.
Message level
The status logger shall support the following four message types:∙ SLINFO: Informational message∙ SLWARN: Warning message∙ SLERROR: Error message∙ SLDEBUG: Debugging message
FEAT5.3.5
HAR
2
FEAT5.3.5
HAR
2
FEAT1.7.12
HAR
2
FEAT1.7.12
HAR
2
SL
SL
1
1
FEAT1.7.12
SL
1
FEAT1.7.12
SL
1
321
SUB14.1.3
Log fields
SUB14.2
Logging process
SUB14.2.1
Connect
SUB14.2.2
Multiple clients
SUB14.3
Log viewer
SUB14.3.1
SUB14.3.2
SUB14.3.3
View files
Filter messages
ASCII export
The status logger shall support the following message fields from clients:∙ Process Name∙ Host Name∙ User ID∙ Event Code∙ Event ID∙ Event Description∙ Message.
The logging process shall allow a client to connect and disconnect from a TCP/IP TCP socket.
The logging process shall support multiple simultaneous client connections.
The log viewer shall be capable of viewing in a scrollable window any of the log files generated by the logging process.
The log viewer shall allow the user to filter the view of messages displayed based on the following parameters:∙ Time logged∙ Message type∙ Process name∙ Host name∙ User ID∙ Event code∙ Event ID∙ Event description∙ Message.
The log viewer shall be capable of exporting a log file to an American National Standard Code for Information Interchange (ASCII), tab‐delimited file.
FEAT1.7.12
SL
1
SL
1
FEAT1.7.12
SL
1
FEAT1.7.12
SL
1
SL
1
FEAT1.7.12
SL
1
FEAT1.7.12
SL
1
FEAT3.12
SL
1
322
SUB14.3.4
Refresh
SUB15
USER ‐ User Management
SUB15.1
SUB15.2
Default group levels
The log viewer shall support manual and periodic log file display refresh.
The system shall have five default groups to which users may be assigned: Administrator, Manager, Operator, Local Guest, and Remote Guest.
The system shall allow individual user Modify individual user privileges to be modified without affecting privileges
the default group levels.
SUB15.3
Modify default group levels
SUB16
SUB16.1
WS ‐ Web Server
General
SUB16.1.1
Operating system
SUB16.1.2
HTML content
SUB16.1.3
Data source
SUB16.2
Video server
The system shall allow the default group permissions to be modified.
The web server subsystem shall run as a Windows IIS application so that if a user has internet access to the host computer the web server application may be executed.
The web server shall be implemented using HTML.
The source for the data displayed on the Web Server shall be SunGuide Center‐to‐
Center Interface.
FEAT1.7.12
SL
1
USER
1
FEAT1.1.5
USER
1
FEAT1.1.7
USER
1
FEAT1.1.7
USER
1
WS
WS
1
1
FEAT2.1
WS
1
FEAT2.1
WS
1
FEAT2.1
WS
1
WS
1
323
SUB16.2.1
The SunGuide system administrator shall be able to configure which digital video Snapshot configuration streams shall be accessible to capture and view snapshots.
SUB16.2.2
Snapshot availability
SUB16.3
CCTV control
SUB16.3.1
SUB16.3.2
SUB16.4
SUB16.4.1
SUB16.4.2
Web CCTV control
Video snapshots (still images) shall be published to the SunGuide Data Bus for dissemination.
The SunGuide CCTV Control GUI shall be used to perform camera operations.
Users utilizing the SunGuide CCTV Control GUI shall need web browser access to the Web access to SunGuide SunGuide server hosting the SunGuide GUI application.
FEAT2.2
WS
1
FEAT2.2
WS
1
WS
2
FEAT2.3
WS
2
FEAT2.3
WS
2
WS
2
FEAT2.4
WS
2
FEAT2.4
WS
2
Map
Map GIS source
SunGuide web data
The source of the graphical map shall be shape files provided by FDOT and shall be the same shape files utilized by the SunGuide Map application.
The map shall be capable of displaying the following types of information through icons and information boxes (these are termed SunGuide Web Data):∙ Incident data∙ DMS∙ RWIS∙ Travel times∙ Link speeds (lanes aggregated to a single value)∙ Video snapshots
324
SUB16.4.3
SUB16.4.4
Map icons
Map configuration
SUB16.4.5
Data updates
SUB16.4.6
Types of data
SUB16.4.6.1
DMS
SUB16.4.6.2
RWIS
Icons shall be used to locate the following SunGuide Web Data:∙ Incident data∙ DMS∙ RWIS∙ Video snapshots
The web server shall provide a configuration parameter that allows the administrator to select which maps are displayed on the web site.
SunGuide Web Data shall be automatically refreshed according to a time parameter set by the system administrator. The time will be selectable from every 1 minute to every 15 minutes in increments of 1 whole minute.
DMS data shall be displayed so that the viewer can see what is displayed on the roadway.
Detailed RWIS data shall be displayed when a RWIS detector is selected on the map display.
FEAT2.4
WS
2
FEAT2.4
WS
2
FEAT2.4
WS
2
WS
2
FEAT2.4
WS
2
FEAT2.4
WS
2
325
SUB16.4.6.3
Speeds
SUB16.4.6.4
Incident data
SUB16.4.6.5
Video snapshots
SUB17
SUB17.1
EM ‐ Event Management
General
SUB17.1.1
SUB17.1.2
SUB17.2
EV access permission
Highway speeds shall be displayed as one of the following three categories:∙ Normal (displayed as green)∙ Moderate slowing (displayed as yellow)∙ Slow (displayed as red)
The SunGuide administrator shall be able to set a threshold for each of the categories (a single threshold applies to all links).
Detailed incident data shall be displayed when an incident icon is selected on the map display.
Video snapshots shall be labeled with the local time and date that the snapshot was gathered when displayed.
Event Management subsystem permissions will include a permission for Event Viewer access.
The Event Management GUI shall allow Notification, on‐scene operators to enter Road Ranger and departure times notification, on‐scene, and departure times.
Response plans
FEAT2.4
WS
2
FEAT2.4
WS
2
FEAT2.4
WS
2
EM
EM
3
3
FEAT22.1.9
EM
3
FEAT19.3.28
EM
3
EM
3
326
SUB17.2.1
SUB17.2.2
SUB17.3
SUB17.3.1
SUB17.3.2
EM to use the RPG
The Event Management GUI shall make use of the Response Plan Generation subsystem to regenerate the relevant response plan using the additional sign.
The Event Management subsystem shall record suggested Response Plans, activated Record response plans Response Plans, and associated date and time stamps.
and timestamps
FEAT27.2.1
EM
3
FEAT26.5.1
EM
3
EM
3
FEAT19.3.30
EM
3
FEAT19.3.30
EM
3
Email alert messages
EM to use RPG to generate email alerts
Email alert sensitive information
The Event Management GUI shall make use of the Response Plan Generation subsystem to generate email alert messages that the Event Management subsystem will send to operator selected subscriber groups.
The Event Management GUI shall allow an operator to add sensitive information to the email alert message; this sensitive alert information will only be sent to those selected subscriber groups that are permitted to receive sensitive information (based on subscriber group configuration).
327
SUB17.3.3
SUB17.4
SUB17.4.1
SUB18
SUB18.1
SUB18.1.1
SUB18.1.2
SUB18.2
SUB18.2.1
The Event Management GUI shall provide the Response Plan Generation Subsystem Required email alert data with all data required to generate an email alert message.
FEAT19.3.31
EM
3
EM
3
EM
3
RS
RS
3
3
FEAT19.1.5
RS
3
FEAT26.1.5
RS
3
RS
3
RS
3
Event data entry
An operator shall be able to invoke the Event Management GUI's event data entry page with location information pre‐filled by Invoke event data entry right‐clicking on an AVL icon and selecting page
"create new incident at vehicle location."
FEAT7.13.2
RS ‐ Reporting System
General
The Reporting GUI data editing page shall Data editing page and include the audit functionality currently audit functionality
provided by the EMPM GUI Audit tab.
Access to the Reporting GUI data editing page will be restricted to users with data Data editing permissions
editing permissions.
Reports
RR and performance measures reports
The reporting GUI reports page shall include both Road Ranger and Performance Measures reports. Performance Measures reports shall be weekly, monthly, quarterly and yearly, providing both summary and detailed data.
FEAT19.8.1
328
The reporting GUI reports page, shall include Event Chronology, and Daily Chronology Reports (combining multiple event chronology reports).
SUB18.2.2
Chronology reports
SUB18.2.3
Road ranger vehicle status report
SUB18.2.4
Vehicle location report
The Reporting GUI reports page shall include a Road Ranger Vehicle status report.
The Reporting GUI reports page shall include a Vehicle Location Report.
SUB18.2.5
Camera usage report
The Reporting GUI reports page shall include a Camera Usage Report.
SUB18.2.6
SUB18.2.7
SUB18.2.8
Event list report
Beat/Route coverage summary report
DMS message report
The Reporting GUI reports page shall include an Event List Report that shall accept as an operator entered input, a vehicle license tag. The resulting Event List Report shall contain only those events that are associated with the relevant vehicle license tag.
The Reporting GUI reports page shall include a Beat/Route Coverage Summary Report (truck hours per beat/route per time period).
The Reporting GUI reports page shall include a DMS Message report.
FEAT19.2.3
RS
3
FEAT28.3.1(s)
RS
3
FEAT28.4.1
RS
3
FEAT28.5.1
RS
3
FEAT19.2.5
RS
3
FEAT28.3.9
RS
3
FEAT19.3.29
RS
3
329
SUB18.2.9
SUB18.2.10
SUB18.2.11
SUB18.2.12
SUB18.2.13
SUB18.2.14
SUB18.2.16
SUB19
The Reporting GUI performance measures page shall allow an operator with appropriate permissions to calculate, re‐
calculate, and store the performance Performance measures measures statistics used in the generation of the Performance Measures reports statistics
provided by the Reporting GUI reports page.
All reports in the Reporting GUI reports page, with the exception of Performance Measures reports, shall allow an operator Calendar date/time range to select a calendar Date/Time range of interest (where applicable).
Traffic flow monthly report
The Reporting GUI reports page shall include a Traffic Flow Monthly Report.
The Reporting GUI reports page shall include a Central Software Reliability Report.
The Reporting GUI reports page, shall ITS device status history include an ITS Device Status History Report.
report
Central software reliability report
The Reporting GUI reports page shall include a Traveler Information Monthly Report.
The Reporting GUI reports page shall Incident management include an Incident Management Monthly monthly report
Report.
MAS ‐ Message Arbitration System
Traveler information monthly report
FEAT28.2.1
RS
3
FEAT19.2.7
RS
3
FEAT28.7.1(s)
RS
3
FEAT28.8.1(s)
RS
3
FEAT28.2.2(s)
RS
3
FEAT28.9.1(s)
RS
3
FEAT28.10.1
RS
3
MAS
3
330
SUB19.1
General
The MAS Subsystem shall maintain a log of posted DMS messages, which links posted Maintain log of posted DMS messages to associated events.
DMS messages
SUB19.1.1
SUB19.2
SUB19.3
SUB19.4
SUB19.5
SUB19.6
DM007M3
DM007M4
DM007M5
DM007M6
DM007M7
Message consistentcy
Send top of queue on Active state change
MAS shall attempt to keep the message reported for a DMS consistent with the top message on the MAS queue
When a DMS transitions to the Active state from any other state, the top message on the MAS queue shall be sent to the DMS.
When a DMS status update reports a DMS message has changed and the message reported does not match the top message Resend top message on on the MAS queue, the software shall status change
resend the top message on the queue
If there are no messages in the MAS queue, MAS shall send a message to blank the DMS when the DMS transitions to the Active Send blank when active state and the DMS status reports a non‐
blank message present on the sign.
MAS shall store the current list of queues MAS queues persist in and their contents in the database when database on status any part of the MAS queue status changes.
change
FEAT19.3.29
MAS
3
MAS
3
MAS
5.1.1
MAS
5.1.1
MAS
5.1.1
MAS
5.1.1
MAS
5.1.1
331
SUB19.7
SUB20
SUB20.1
SUB20.1.1
SUB20.1.2
SUB20.2
SUB20.2.1
SUB21
SUB21.1
SUB21.1.1
SUB21.1.2
SUB21.2
DM007M8
MAS shall retrieve the current list of queues MAS queues retrieved from the database upon startup
from database on startup
MAS
5.1.1
EV
EV
3
3
EV
3
EV
3
EV
3
EV
3
511
511
3
3
FEAT25.5.10
511
3
FEAT25.4.10
511
3
511
3
EV ‐ Event Viewer
General
Event Viewer shall be accessible through the web server component of the SunGuide Accessible via web server
FEAT22.1.2(s)
website.
Terminate session with A user can terminate their session with the logout button
logout button.
Configuration
When IIS is configured with appropriate IP security restrictions, the SunGuide Event IIS configuration with IP Viewer Web site shall not be accessible to clients outside the specified IP addresses security restrictions
within IIS.
FEAT22.1.4(s)
FEAT22.2.2(s)
511
General
An incident/event shall be considered to be associated with the closest 511 reporting Incident association to segment(s) that are on the same roadway segments
as the incident/event.
A specially recorded message shall be Recorded messages considered available after it has been available after approval
approved.
Reports
332
SUB21.2.1
SUB21.2.2
Link Reports shall report travel times, and applicable Incident Link Reports, for a single 511 reporting segment in both directions of Link report contents with travel. There may be from one to four 511 one to four segments reporting segments per roadway.
Link Summary Reports shall report travel times, and applicable Incident Link Reports, Summary reports with for an entire roadway. Link Summary segments on same Reports may include multiple 511 reporting roadway
segments on the same roadway.
SUB21.2.4
Support recording of incident reports
SunGuide shall support the recording of incident (a.k.a event) reports for 511 reporting segments.
SUB21.2.5
Reports saved for configurable time
Incident Link Reports shall be saved for management review for up to a configurable amount of days.
SUB21.2.6
SUB21.2.7
Incident link report playback functionality
The SunGuide operator interface shall allow operators with appropriate permissions to play back current and saved Incident Link Reports for a 511 reporting segment.
At most one (1) Incident Link Report shall One incident report per be associated with a 511 reporting segment
segment.
FEAT25.5.2
511
3
FEAT25.5.2
511
3
FEAT25.5.1
511
3
FEAT25.5.6
511
3
FEAT25.5.6
511
3
FEAT25.5.9
511
3
333
SUB21.2.8
SUB21.2.9
SUB21.2.11
SUB21.3
SUB21.3.1
SUB21.3.2
SUB21.4
If an Incident Link Report exists for a 511 reporting segment, it shall be considered Incident reports applicable to the Link Report for the 511 applicable to link report
reporting segment.
Incident reports applicable to link summaries
If an Incident Link Report exists for a 511 reporting segment, it shall be considered applicable to a Link Summary report that includes the 511 reporting segment.
If there are no Incident Link Reports for the 511 reporting segments included in a Link Summary Report, the Incident Link Report Summaries state no section of the Link Summary shall state that incidents if appropriate
there are no incidents.
FEAT25.5.9
511
3
FEAT25.5.9
511
3
FEAT25.5.17
511
3
511
3
FEAT25.7.1
511
3
FEAT25.7.1
511
3
511
3
Travel times
Travel time rounding to 5‐minute increments shall be peformed on the total Round times to 5‐minute travel time for a Link Report, Link Summary, or Drive Time Summary.
increments
Travel times for reporting on 511 shall be Rounding for increasing rounded up if the travel time is increasing and decreasing times and down if the travel time is decreasing.
Scenarios
334
SUB21.4.1
SUB21.4.2
SUB21.4.3
A pre‐recorded Scenario will consist of a description of a 511 reporting segment (or portion of a 511 reporting segment, such as between the start point and mid point of Pre‐recorded scenario the segment), and a travel time. For contents
example "I4 Southbound from SR 436 to SR 50."
The SunGuide Administrative Editor shall allow one pre‐recorded Scenario .wav file to be associated with a given travel time (5 mins, 10 min, 15 min, etc) and given Scenario WAV files portion of a 511 reporting segment (start associated with travel point to mid point, mid point to end point, times
end point to mid point, and mid point to start point).
Pre‐recorded scenario .Wav files shall be Scenario WAV files based selected based on current 511 reporting on current times
segment travel times.
FEAT25.2.2
511
3
FEAT25.2.2
511
3
FEAT25.3.2
511
3
335
The text associated with a pre‐recorded scenario .Wav file shall be generated by SunGuide based on the 511 reporting segment and travel time to which the scenario .wav file is associated. For example, if a scenario .wav file is associated WAV files generation with I4 going southbound from start point based on segments and SR436 to mid point SR50 for a 5 minute times
travel time, the text would be "I4 Southbound from SR 436 to SR 50 is 5 mins."
SUB21.4.4
AVL ‐ Automatic Vehicle Location
General
CVS ‐ Connected Vehicle System
Configuration
SUB22
SUB22.1
SUB23
SUB23.2
SUB23.2.1
SUB23.2.2
SUB23.2.3
CV001A
CV001B
CV001C
Name RSEs
The software shall provide the capability to specify the name of an RSE.
The software shall provide the capability to configure a host and port numbers for TAM communication via the J2735 2009‐11 and Host and Port Numbers
J2735 VIIPOC standards
Location
The software shall provide the capability to specify the physical location of an RSE using latitude, longitude, roadway, direction, and description
FEAT25.3.2
511
3
AVL
3
AVL
3
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
336
SUB23.2.4
CV001D
SUB23.2.5
CV001D1
SUB23.2.6
SUB23.2.7
CVS
5.1
CVS
5.1
CV001E
RSE Database Storage
Configuration information for an RSE shall be stored in the SunGuide database.
CVS
5.1
CV004A
If probe data is received for a zone, the probe data shall be used by the TSS link to RSE data as Probe data determine the speed over the given link.
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
SUB23.2.8
CV005A
SUB23.2.9
CV005B
SUB23.3
SUB23.3.1
SUB23.3.2
The software shall provide the capability to Specify Detection Zones specify one or more detection zones for each RSE
For a detection zone, the software shall provide the capability to specify a name, Detection Zone start angle, and end angle for a detection Parameters
zone.
CV006A
CV006A
RSE Default Message Template
Default Template Configuration Amber Alert
Data Acquisition
Support Standards
Receiving BSM
The software shall provide the capability to specify a default message template for an RSE.
The software shall provide the capability to specify a message template for amber alert events
The software shall be capable of receiving messages from "Connected Vehicle" based on SAE J2735 2009‐11 and J2735 VIIPOC standards.
The software shall be capable of receiving and reporting the "Connected Vehicle" Basic Safety Messages (BSM)
337
SUB23.3.3
SUB23.3.4
CV006A1A
CV006A2
BSM Data
Receiving PVDM
SUB23.3.5
CV006A2A
PVDM Data
SUB23.3.6
CV007A
Sending TAMs
SUB23.3.7
CV007B
TAM Formatting Standards
SUB23.4
SUB23.4.1
The software shall retrieve latitude, longitude, elevation, speed, and heading from the reported BSM, as available
The software shall be capable of receiving and reporting aggregated Probe Vehicle Data message (PVDM)
The software shall retrieve latitude, longitude, elevation, speed, heading from the reported PVDM using the SAE J2735 2009‐11 and J2735 VIIPOC standards, as available
The software shall provide the ability to send TAMs to RSE devices connected to SunGuide.
The message formats of the TAMs shall be based on SAE J2735 2009‐11 and J2735 VIIPOC standards.
GUI
CV010A
RSE Icon
SUB23.4.2
CV010A1
RSE Icon Presentation
SUB23.4.3
CV010A2
RSE Icon displays Operational Status
The software's GUI shall display an icon representing RSEs on the Operator Map.
The software shall display the RSE icons consistent with presentation of other field equipment (e.g. signs, cameras, detectors, radios, etc.) icons.
The software shall modify the display of RSE icons in response to operational status changes.
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
338
SUB23.4.4
SUB23.4.5
SUB23.4.6
CV010A3
CV010A4
CV010B
SUB23.4.7
CV010C
SUB23.4.8
CV011A
SUB23.4.9
SUB23.4.10
CV011A1
CV011A1A
RSE Icon navigate to Status Dialog
RSE Status Content
RSE Detection Zone Status Content
When an operator clicks on an RSE icon, a dialog will be shown containing RSE data.
The software’s GUI shall display “Connected Vehicle” data derived from the data reported in the BSM and PVDM.
The “Connected Vehicle” data displayed on the GUI shall include each detection zone configured for the RSE
The “Connected Vehicle” data displayed on the GUI shall include the speed of the detection zone that is the most in violation RSE Detection Zone or closest to violation of the speed Status Content (Speed) threshold and indicate if that speed is in violation of the speed threshold.
TAM Creation
TAM Data Fields
The software shall provide operators the ability to manually construct a TAM.
The software shall allow the user to specify the start time, end time, priority, presentation regions, text of message, and RSEs
The software shall allow the user to specify a presentation region including a polygon made up of latitude/longitude points and TAM Presentation Region
directions of travel that the message should be applicable
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
339
SUB23.4.11
SUB23.4.11.1
SUB23.4.11.2
CV011B
CV011B1
CV011B2
TAM Status Dialog
Hyper‐linked Event Ids
Event Ids (if available) will be hyperlinked to the existing event.
Show Presentation Regions
When a presentation region is selected, the defined polygon for that region will be shown on the Operator Map.
SUB23.4.13
CV011C
Modify TAMs
SUB23.4.14
CV011D
Delete TAMs
SUB23.4.15
CV011E
Filter TAMs
SUB23.4.16
CV011F
The software shall provide the ability to view current TAMs including the text of the message, priority, event id, start time, end time, number, presentation regions, and the selected RSEs.
The software shall provide the ability to modify current TAMs including start time, end time, priority, presentation regions, text of message, and RSEs
The software shall provide the ability to delete current TAMs
The software shall provide the ability to filter the list of current TAMs based on RSE id and whether or not the TAM has an associated event.
The software shall provide the ability to automatically select applicable RSEs based Automatically select RSEs on the currently selected presentation for TAM
region.
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
340
SUB23.4.17
SUB23.4.18
SUB23.4.19
SUB23.4.20
SUB23.4.21
CV012A
CV012B
CV012C
CV012C1
CV012C2
RSE Data Fields
RSE Detection Zone Configuration
The software shall provide the ability for a user to configure the name, host, port for TAM (VIIPOC) messages, port for TAM (2009‐11) messages, latitude, longitude, roadway, direction, location description, and detection zones.
For each RSE, the software shall allow the user to configure one or more detection zones, each consisting of a description, start and end angles for the applicable direction of travel
When an RSE is configured, the software shall attempt to automatically configure RSE to TSS Configuration
TSS to support incoming probe data.
Convert RSE to TSS Detectors
If TSS is available when an RSE is configured, the software shall attempt to configure a TSS detector with the same name as the RSE
If a TSS detector is successfully configured, the software shall attempt to create TSS Convert RSE Detection links using the configured detection zones along with the alarm and recovery Zones to TSS Links
thresholds
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
341
SUB23.4.22
SUB23.4.23
SUB23.4.24
SUB23.4.25
SUB23.4.26
SUB23.4.27
CV013A
CV013B
CV013B1
CV013C
CV013D
CV015A
The software shall automatically generate one or more presentation regions for the TAM based on the device linking file and Automatically Generated the radius specified by the user for the area Presentation Regions
affected by the event
The software shall automatically specify Automatically selected which RSEs should receive an automatically RSEs Response Plan TAMs generated TAM
RSE selection criteria
RSEs will be selected if the distance between the RSE and any part of the presentation region is less than the configured inclusion distance
The software shall provide operators the Add, Modify, or Delete ability to add, modify, or delete TAMs from Response Plan TAMs a response plan
Default messages for TAMs
The software shall set a default message for a TAM to a predefined template in response plans, if such a template is configured.
The software shall allow a user to view a list of RSEs with detection zones for which no Configuration Inspection TSS detectors on a CV driver are defined
(Detectors)
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
342
SUB23.4.28
SUB23.4.29
SUB23.4.30
SUB23.4.31
CV015B
CV015C
CV015D
CV015E
SUB23.5
SUB23.5.1
The software shall allow a user to view a list of TSS detectors on a CV driver for which no Configuration Inspection RSEs with detection zones are defined
(Detectors)
The software shall allow a user to view a list Configuration Inspection of CVS detection zones for which no TSS (Detectors)
lane is defined
The software shall allow a user to view a list Configuration Inspection of TSS lanes for which no CVS detection (Detectors)
zone is defined
The software shall allow a user to view a list of CVS detection zones, TSS links, and TSS Configuration Inspection lanes which are mapped together but which (Detectors)
have dissimilar names
Archive
CV009A
Archive BSM Data
SUB23.5.2
CV009A1
Archived BSM Fields
SUB23.5.3
CV009B
Archive PVDM Data
The software shall archive BSM data.
For a BSM, the software shall archive the received timestamp, latitude, longitude, elevation, speed, and heading, where available for each message to be archived
The software shall archive PVDM data.
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
343
SUB23.5.4
CV009B1
Archived PVDM Fields
SUB23.5.5
CV009C
Archive TAM Data
SUB23.5.6
SUB23.5.7
SUB23.5.8
CV009C1
CV009C2
CV009C3
Archived TAM Fields
Archived TAM Presentation Regions
Archive TAM Modifications
For the PVDM, the software shall archive the received timestamp, latitude, longitude, elevation, speed, and heading where available for each message to be archived
The software shall archive TAM data.
For the TAM, the software shall archive the id of the message, start time, end time, priority, presentation region, text of message, operator, event id, RSEs the message was sent to, time the message was added to the system, and time the message was removed from the system, where the values are available
For a TAM presentation region, the software shall archive the TAM associated with the region, the directions applicable to the region, and the latitude and longitude of the points that make up the region
When a TAM is modified by an operator, the software shall update the end time for the current message to the current time and archive a new TAM.
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
344
SUB23.5.9
SUB23.5.10
CV009C4
CV009D
SUB23.6
CV014A
SUB23.6.2
CV014A1
SUB23.6.3
CV014B
SUB23.6.4
CV014B1
SUB23.7
SUB23.7.2
Optional Archiving of BSM and PVDM Data
The SunGuide configuration file will include a parameter specifying if the raw BSM and PVDM data should be archived.
C2C
SUB23.6.1
SUB23.7.1
When a TAM is deleted by an operator, the software shall modify the archived end time Archive TAM End Times of the TAM to reflect when the message was ended
The software shall be capable of Publish PVDM Data
broadcasting PVDMs via C2C
The C2C PVDM shall contain the data in the SAE J2735 2009‐11 and J2735 VIIPOC Published PVDM Format
standards, as available
The software shall be capable of broadcasting TAM messages
The C2C TAM shall contain the data in the SAE J2735 2009‐11 and J2735 VIIPOC Published TAM Format
standards, as available
Publish TAM Data
SDN
CV015A
CV015A
The software shall support an outgoing connection that will send J2735 encoded Data Standard for SDN Probe data using the SAE J2735 VIIPOC Data
standard.
The software will support configurable parameters for both host and port to SDN Configuration Data
configure the SDN connection.
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
CVS
5.1
345
SUB23.7.3
CV015A
SUB26
SUB26.1
SUB26.1.1
SUB26.1.2
SUB26.1.3
SUB26.1.4
SDN Data Transfer Protocol
The software shall support sending TAMs to the SDN using the interface defined in the “Advisory Message Distribution Service Users Guide Version 1.1” dated October 22, 2007
CVS
5.1
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
Interface
TD007I101
TD007I102
TD007I103
TD007I104
When publishing TSS traffic condition data records, the INRIX C2C Publisher Mark INRIX data with Non‐
component shall mark such data records as distribution
not for redistribution to third parties.
Network and Center Id
Confidence Level
Configurable Interval
The INRIX C2C Publisher component shall include as the network or center ID of each record a configurable value specified in the SunGuide configuration file.
If the confidence value received from the INRIX data source for a C2C link is below a minimum confidence level specified in the SunGuide configuration file, the INRIX C2C Publisher will not publish a update for that C2C link.
The INRIX C2C Publisher component shall retrieve data from the INRIX traffic data source at a configurable interval determined in the SunGuide configuration file.
346
SUB26.1.5
SUB26.1.6
SUB26.1.7
SUB26.1.8
SUB26.1.9
TD007I201
TD007I202
TD007I301
TD007I401
TD007I501
Retrieve County List
Publish Configured Counties
Publish Most Recent Mean Speed
The INRIX C2C Publisher component shall retrieve the list of counties from which to publish data from the SunGuide configuration file.
The INRIX C2C Publisher component shall publish link data for each link provided by the INRIX traffic data source which is identified as belonging to a county included in the list of counties from which to publish data.
While the connection to the INRIX traffic data source is established, the INRIX C2C Publisher component shall publish the most recently provided mean speed data from the INRIX traffic data source for each published link.
While the connection to the INRIX traffic data source is established, the INRIX C2C Publisher component shall periodically publish the averaged speed data from the Periodic Publish of Data
INRIX traffic data source for each published link.
Publish C2C Nodes
The INRIX C2C Publisher component shall publish a list of C2C Nodes containing the start and end locations of each INRIX link being published.
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
347
SUB26.1.10
SUB26.1.11
SUB26.1.12
SUB26.1.13
SUB26.1.14
TD007I502
TD007I503
TD007I504
TD007I505
TD007I506
Unique Node Ids
Publish Lat Lon Information
Link Identifier
Required Link Data
Midpoint Data
The INRIX C2C Publisher component shall assign each published node an identifier unique to that instance of the Publisher.
The INRIX C2C Publisher component shall publish the most recently provided latitude and longitude from the INRIX traffic data source for each published node.
The INRIX C2C Publisher component shall assign each published link a unique identifier based on the INRIX link identifier, roadway, direction, county, or other identifying information.
The INRIX C2C Publisher component shall publish the most recently provided roadway name, direction, county, distance, start node, and end node from the INRIX traffic data source for each published link.
The INRIX C2C Publisher component shall publish link midpoints for each published link where midpoints could be determined.
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
348
SUB26.1.15
SUB26.1.16
SUB26.1.17
SUB26.1.18
TD007I601
TD007I602
TD007I603
TD007I604
Matching TMC Ids
Minimum Midpoint Spacing
The INRIX C2C Publisher component shall publish midpoints for any published links which have a TMC Path ID that can be accurately matched to a link in the SunGuide map source.
The INRIX C2C Publisher component shall read a minimum midpoint spacing parameter from the SunGuide configuration file.
When publishing midpoints for a published link, the INRIX C2C Publisher shall publish each midpoint defined by the SunGuide map source for the link, unless that Publishing all Midpoints midpoint violates the spacing requirements of TD007I604 and TD007I605.
Sequential Midpoint evaluation
When determining which midpoints may be published, the INRIX C2C Publisher shall sequentially evaluate each midpoint, beginning with the midpoint nearest the start node of the link.
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
349
SUB26.1.19
SUB26.1.20
SUB26.1.21
SUB26.1.22
SUB26.1.23
TD007I605
TD007I701
TD007I702
TD007I703
TD007I704
Midpoint Exclusion Criteria
Databus Connection
INRIX Permissions
Disconnection Alert
Alert Frequency
When determining which midpoints may be published, the INRIX C2C Publisher shall publish the midpoint if and only if it is at least the minimum midpoint spacing parameter from the start node, the end node, and all other midpoints already selected for publication.
The INRIX C2C Publisher component shall connect to Databus as other SunGuide providers do.
The INRIX C2C Publisher shall allow a client with appropriate permissions to subscribe to communication alert notifications.
If the connection to the INRIX data source is determined to be lost, the INRIX C2C Publisher shall send an alert message to all subscribed clients indicating a loss of communication to the INRIX data source.
While the connection to the INRIX data source is lost, the INRIX C2C Publisher shall send additional alert messages to all subscribed clients indicating the ongoing loss of communication at a frequency specified in the SunGuide configuration file.
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
350
SUB26.1.24
TD007I705
SUB26.2
SUB26.2.1
SUB26.2.2
SUB26.2.3
SUB26.2.4
Alerts in Alert Box
If a communication loss alert is received from the INRIX C2C Publisher, the SunGuide Operator Map shall display the alert in the System Messages dialog.
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
GUI
TD007O101
TD007O102
TD007O103
TD007O104
C2C Links on Map
Lane Defination
Number of Lanes
The map shall display a C2C link in the same manner as it displays local TSS links.
The map shall display a C2C link using the number of lanes specified by that link's C2C definition if provided, or showing a single lane if the number of lanes is not provided.
The map shall display all lanes of a single C2C link in the same color.
The map shall allow a user with permission to set systemwide map settings to specify a single C2C traffic speed "Congested" threshold as a percentage of the speed limit Systemwide Congestion on the roadway that the C2C link is Threshold
representing, as defined by the SunGuide map source.
351
SUB26.2.5
SUB26.2.6
SUB26.2.7
SUB26.2.8
SUB26.2.9
TD007O105
TD007O106
TD007O107
TD007O108
TD007O109
Systemwide Near‐
Congestion Threshold
Congestion Coloring
The map shall allow a user with permission to set systemwide map settings to specify a single C2C traffic speed "Near Congested" threshold as a percentage of the speed limit on the roadway that the C2C link is representing, as defined by the SunGuide map source.
If the current speed of a C2C link is below the Congested threshold, the map shall display the link using the color used for local TSS lanes in an alarm condition.
If the current speed of a C2C link is below the Near Congested threshold, but not below the Congested threshold, the map Near‐Congestion Coloring shall display the link using the color used for local TSS lanes in a near‐alarm condition.
Freeflow Coloring
Zero Data Coloring
If the current speed of a C2C link is above the Near Congested and Congested thresholds, the map shall display the link using the color used for local TSS lanes in a normal (freeflow) condition.
If the current speed of a C2C link is zero or is unavailable, the map shall display the link using the color used for local TSS lanes in a zero data condition.
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
352
SUB26.2.10
SUB26.2.11
SUB26.2.12
SUB26.2.13
SUB26.2.14
SUB26.2.15
TD007O1010
TD007O1014
TD007O1012
TD007O1013
TD007O1014
TD007O201
Speed Limit Coloring
Display Link Status
Right Click Behavior
If a speed limit is unavailable for a C2C link, the map shall display the link using the color used for local TSS lanes in a normal (freeflow) condition.
When an operator left clicks on a C2C link, the SunGuide Operator Map shall display the C2C Traffic Conditions dialog.
When an operator right clicks on a C2C link, the SunGuide Operator Map shall display a context menu containing "C2C Traffic Conditions".
When an operator selects the "C2C Traffic Conditions" item from a context menu, the SunGuide Operator Map shall display the Display Traffic Conditions C2C Traffic Conditions dialog, showing Dialog from Context information from the link which was right Menu
clicked on.
The C2C Traffic Conditions dialog shall display the identifier and center of the C2C link it was launched from, along with the Status Dialog Information
current link speed and delay time, if available.
If the operator selects C2C | Select Networks... from the context menu, the Select Networks Dialog map shall display the C2C Network Selection dialog.
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
353
SUB26.2.16
SUB26.2.17
SUB26.2.18
SUB26.2.19
SUB26.2.20
TD007O202
TD007O203
TD007O204
TD007O2015
TD007O2016
The C2C Network Selection dialog shall display a list of C2C networks which are currently providing data available to the operator and C2C networks for which the Display Current Networks
operator has previously made data display selections.
Save Operator Preferences
When opened, the C2C Network Selection dialog shall present the operator's last saved display preferences as the currently selected options.
The C2C Network Selection dialog shall allow an operator to select whether data Show Certain Networks from a center should be displayed or hidden.
Persist Operator Selection
The C2C Network Selection dialog shall allow an operator to save network data display preferences for use on subsequent sessions.
The C2C Network Selection dialog shall allow an operator to specify whether data from C2C networks which are not currently listed but which may later appear should be Selection for Undetermined Networks displayed or hidden until an explicit decision is made.
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
354
SUB26.2.21
SUB26.2.22
TD007O207
TD007O208
SUB26.3
SUB26.3.1
SUB26.3.2
Display Center on Map
Live Update Center Selection on Map
The Operator Map shall display C2C data only from centers which the operator has specified should have data displayed and, if the operator has selected that data from unspecified centers should be displayed, from centers for which the operator has not specified a preference.
If an operator changes the setting regarding whether data for a center should be displayed during a session, the Operator Map shall update its display to reflect those settings without requiring a restart.
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
INRIX
5.0.4
Access
TD007A101
TD007A201
The SunGuide Data Archive component shall not write data records to a TSS CSV file if those records include a flag indicating the data was gathered or derived from a Exclude Restricted from restricted source and cannot be CSV
redistributed to third parties, or are based on a record which includes that flag.
The SunGuide Data Archive component shall include a record in the ODS Travel Time Info table consisting of a comma delimited list of centers which have TSS Record Center Id in ODS
links as part of the travel time link at the time the record was received.
355
SUB26.3.3
SUB26.3.4
TD007A301
TD007A302
SUB27
SUB27.1
SUB27.1.1
SUB27.1.2
SUB27.1.3
Flag Restricted TvT
Flag Restricted in C2C
If a published travel time link report includes speed data from a restricted source not for redistribution to third parties, the Travel Times Subsystem shall flag the travel time link report as not for redistribution to third parties.
If a travel time link published by the SunGuide C2C Publisher is marked as not for redistribution to third parties, the SunGuide C2C Publisher shall flag that link as not for redistribution to third parties when publishing it via C2C.
SPARR
SPARR (Phone)
SPARR001
SPARR002
SPARR003
Authentication
Intial Required Fields
End Session
The SPARR shall require a Road Ranger to authenticate to the system using credentials defined by the AVL/RR subsystem.
The SPARR shall require a Road Ranger to select the vehicle, radio, and beat for use in a shift prior to beginning a session
If a Road Ranger is logged in and not dispatched to or arrived at any events, the SPARR shall allow the Road Ranger to end the session
INRIX
5.0.4
INRIX
5.0.4
SPARR
SPARR
5.0.5
5.0.5
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
356
SUB27.1.4
SUB27.1.5
SUB27.1.6
SUB27.1.7
SUB27.1.8
SPARR004
SPARR005
SPARR006
SPARR007
SPARR008
Location Updates
Queue Updates
Event Notification
Arrival Notification
Required Activity
The SPARR shall provide location updates to the Traffic Management Center at a configurable interval
While the SPARR is not connected to the SPARR Driver, the SPARR shall maintain a queue of location updates that would have been sent and retransmit those updates when the connection to the SPARR Driver is reestablished
If a Road Ranger using the SPARR is dispatched to an event while the SPARR is connected to the SPARR Driver, the SPARR shall display a notification to the Road Ranger.
If the Road Ranger is not currently arrived at an event, the SPARR shall allow the Road Ranger to notify the Traffic Management Center when they have arrived at an event
If the Road Ranger has at least one activity recorded for an event at which they are arrived, the SPARR shall allow the Road Ranger to notify the Traffic Management Center when they have departed an event.
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
357
SUB27.1.9
SUB27.1.10
SUB27.1.11
SUB27.1.12
SUB27.1.13
SUB27.1.14
SUB27.1.15
SPARR009
SPARR010
SPARR011
SPARR012
SPARR013
SPARR014
SPARR015
Calling to TMC
The SPARR shall support phone calls to the Traffic Management Center using the cellular network
SPARR
5.0.5
SPARR
5.0.5
Add Activity
The SPARR shall allow a Road Ranger to add activities (services rendered) to an event
SPARR
5.0.5
Involved Vehicles
The SPARR shall allow a Road Ranger to add involved vehicles to an event
SPARR
5.0.5
The SPARR shall allow a Road Ranger to modify their dispatch status
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
Create Event
Dispatch Status
Only Assisting Status while at Event
If the Road Ranger is not currently arrived at an event, the SPARR shall allow the Road Ranger to create a SunGuide event with event type and location by a Road Ranger
If a Road Ranger is arrived at an event, the SPARR shall only allow the Road Ranger to set their dispatch status to one which is flagged as an Assisting status
If a Road Ranger is not arrived at any event, but is dispatched to an event, the SPARR shall only allow the Road Ranger to set their Can Be Dispatch Status dispatch status to one which is flagged as Changes
Can Be Dispatched and is not flagged as Assisting
358
SUB27.1.16
SPARR016
If a Road Ranger is not arrived at or dispatched to any event, the SPARR shall only allow the Road Ranger to set their General Status Changes
dispatch status to one which is not flagged as Assisting.
SUB27.1.17
SPARR017
Unallowed Status Changes
SUB27.1.18
SPARR018
Driver Communication
SUB27.1.19
SUB27.1.20
SUB27.1.21
SUB27.2
SPARR019
SPARR020
SPARR021
Send Current Time
Reconnect Behavior
The SPARR shall not allow the Road Ranger to manually change to any dispatch status flagged as Default Start Shift or Default End Shift.
The SPARR shall communicate with SunGuide through the SPARR Driver
When the SPARR sends a message to the SPARR Driver, the SPARR shall include the current time of the device
While the SPARR is not connected to the SPARR Driver, the SPARR shall periodically attempt to reconnect to the SPARR Driver
While the SPARR is not connected to the SPARR Driver, the SPARR shall maintain a queue of commands issued by the user and Queue Commands and Re‐ retransmit those commands when the connection to the SPARR Driver is transmit
reestablished
SPARR Driver
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
359
SUB27.2.1
SPARR022
SUB27.2.2
SPARR023
SUB27.2.3
SPARR024
SUB27.2.4
SUB27.2.5
SUB27.2.6
SPARR025
SPARR026
SPARR027
Subsystem Connection
The SPARR Driver shall only require a single connection to the SunGuide AVL Subsystem
The SPARR Driver shall support connections Connection with Phones with multiple smart phones running the SPARR
The SPARR Driver shall pass data between Data Pass Through
the SPARR to the SunGuide AVL Subsystem
Time Sync
Default Start Shift
Default End Shift
When reporting to SunGuide timestamp data provided by the SPARR, the SPARR Driver shall adjust the reported timestamp to correct for any difference between the Application Server’s time and the current time reported by the device
When a SPARR user successfully reports the start of a shift and the vehicle either has no current dispatch status or is in a dispatch status flagged as Default End Shift, the SPARR driver shall set the vehicle's dispatch status to a dispatch status flagged as Default Start Shift
When a SPARR user successfully reports the end of a shift, the SPARR driver shall set the vehicle's dispatch status to a dispatch status flagged as Default End Shift
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.0.5
360
SUB27.2.7
SPARR028
Default Assisting
SUB27.2.8
SPARR029
Default Patrolling
SUB27.2.9
SPARR030
Close an Event
SUB27.2.9.1
SPARR030A
Closure criteria
SUB27.2.10
SPARR031
Bulk Update
When a SPARR user successfully reports that they have arrived at an event, the SPARR driver shall set the vehicle's dispatch status to a dispatch status flagged as Default Assisting
When a SPARR user successfully reports that they have departed from an event, the SPARR driver shall set the vehicle's dispatch status to a dispatch status flagged as Default Patrolling
SunGuide shall allow a SPARR client to close an open event
The SPARR interface shall reject a request to close an event that is already closed, has responder vehicles currently arrived, or has any non‐open lanes.
The driver will support a web service method for sending multiple position updates as a single request.
SPARR
5.0.5
SPARR
5.0.5
SPARR
5.1.1
SPARR
5.1.1
SPARR
6
361
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement