Model Systems Engineering Documents for Central Traffic Signal Systems

Appendix B: System Requirements Table of Sample Statements

Requirements Document Reference Number	System Requirements Sample Statements	Need Statement (ConOps)
3	Requirements
3.1	Functional System Requirements
3.1.1	Access Control
3.1.1.1	The system shall provide monitoring and control access from the following locations. Agency TMC Agency LAN or WAN Other agency TMC (SPECIFY) Local controller cabinets (hard wire) Local controller cabinets (wireless) Remote location via internet	4.1.4.1 The TSS Operator needs to manage the system database from the following locations: (EDIT TO SUIT YOUR SITUATION) Multiple workstations in the TMC Multiple networked workstations on the City's LAN or WAN located at (USER SPECIFY) Workstations at other Agencies' TMC (USER SPECIFY) At the local controller cabinet using a hard wire connection At the local controller cabinet using a wireless connection Remote locations connected to the internet (USER SPECIFY, such as employee's home, maintenance vehicle, etc.)
3.1.1.2	The system shall allow remote access using a secure Virtual Private Network (VPN).	4.1.4.1 The TSS Operator needs to manage the system database from the following locations: (EDIT TO SUIT YOUR SITUATION) Multiple workstations in the TMC Multiple networked workstations on the City's LAN or WAN located at (USER SPECIFY) Workstations at other Agencies' TMC (USER SPECIFY) At the local controller cabinet using a hard wire connection At the local controller cabinet using a wireless connection Remote locations connected to the internet (USER SPECIFY, such as employee's home, maintenance vehicle, etc.)
3.1.1.3	The system shall allow operators from different agencies to view/edit traffic signal databases owned by other agencies, subject to assigned privilege level.	4.1.4.2 Multiple system TSS Operators need to log on to the system simultaneously in order to do independent functions at different intersections or to view the same intersection.
3.1.1.3	The system shall allow operators from different agencies to view/edit traffic signal databases owned by other agencies, subject to assigned privilege level.	4.1.4.4 The TSS Operator needs to view the status of an intersection or group of intersections even when another TSS Operator is editing the intersection database.
3.1.1.3	The system shall allow operators from different agencies to view/edit traffic signal databases owned by other agencies, subject to assigned privilege level.	4.1.4.5 The TSS Operator needs to view the status of multiple agency signals, edit the intersection databases, and/or create reports, as allowed by permission.
3.1.1.4	The system shall allow XX number of users to log on to the system simultaneously.	4.1.4.2 Multiple system TSS Operators need to log on to the system simultaneously in order to do independent functions at different intersections or to view the same intersection.
3.1.1.4	The system shall allow XX number of users to log on to the system simultaneously.	4.1.4.3 The TSS Operator needs to make changes to an intersection database, disabling the ability of other TSS Operators to simultaneously make changes to the same intersection database.
3.1.1.4	The system shall allow XX number of users to log on to the system simultaneously.	4.1.4.4 The TSS Operator needs to view the status of an intersection or group of intersections even when another TSS Operator is editing the intersection database.
3.1.1.5	The system shall allow multiple operators to access an intersection database simultaneously.	4.1.4.2 Multiple system TSS Operators need to log on to the system simultaneously in order to do independent functions at different intersections or to view the same intersection.
3.1.1.5	The system shall allow multiple operators to access an intersection database simultaneously.	4.1.4.4 The TSS Operator needs to view the status of an intersection or group of intersections even when another TSS Operator is editing the intersection database.
3.1.1.6	The system shall allow multiple TSS Operators to view the status of an intersection or group of intersections simultaneously.	4.1.4.2 Multiple system TSS Operators need to log on to the system simultaneously in order to do independent functions at different intersections or to view the same intersection.
3.1.1.6	The system shall allow multiple TSS Operators to view the status of an intersection or group of intersections simultaneously.	4.1.4.4 The TSS Operator needs to view the status of an intersection or group of intersections even when another TSS Operator is editing the intersection database.
3.1.1.6	The system shall allow multiple TSS Operators to view the status of an intersection or group of intersections simultaneously.	4.5.7.1.2 The TSS Operator needs to select a predetermined group of intersections to monitor.
3.1.1.7	The system shall restrict control of each intersection database to a single user at a time.	4.1.4.2 Multiple system TSS Operators need to log on to the system simultaneously in order to do independent functions at different intersections or to view the same intersection.
3.1.1.7	The system shall restrict control of each intersection database to a single user at a time.	4.1.4.3 The TSS Operator needs to make changes to an intersection database, disabling the ability of other TSS Operators to simultaneously make changes to the same intersection database.
3.1.1.7	The system shall restrict control of each intersection database to a single user at a time.	4.1.4.4 The TSS Operator needs to view the status of an intersection or group of intersections even when another TSS Operator is editing the intersection database.
3.1.1.7.1	The system shall release lock of intersection database after a user-specified period of inactivity.	4.1.4.2 Multiple system TSS Operators need to log on to the system simultaneously in order to do independent functions at different intersections or to view the same intersection.
3.1.1.7.1	The system shall release lock of intersection database after a user-specified period of inactivity.	4.1.4.3 The TSS Operator needs to make changes to an intersection database, disabling the ability of other TSS Operators to simultaneously make changes to the same intersection database.
3.1.1.7.2	The system shall allow access to a traffic signal database on a first come, first served basis.	4.1.4.2 Multiple system TSS Operators need to log on to the system simultaneously in order to do independent functions at different intersections or to view the same intersection.
3.1.1.7.2	The system shall allow access to a traffic signal database on a first come, first served basis.	4.1.4.4 The TSS Operator needs to view the status of an intersection or group of intersections even when another TSS Operator is editing the intersection database.
3.1.1.7.3	The system shall allow administrator to terminate intersection control by other users with lesser user rights.	4.1.4.2 Multiple system TSS Operators need to log on to the system simultaneously in order to do independent functions at different intersections or to view the same intersection.
3.1.1.7.3	The system shall allow administrator to terminate intersection control by other users with lesser user rights.	4.1.4.3 The TSS Operator needs to make changes to an intersection database, disabling the ability of other TSS Operators to simultaneously make changes to the same intersection database.
3.1.1.7.3	The system shall allow administrator to terminate intersection control by other users with lesser user rights.	4.1.4.4 The TSS Operator needs to view the status of an intersection or group of intersections even when another TSS Operator is editing the intersection database.
3.1.1.8	The system shall allow access to a traffic signal database based on user privileges.	4.1.4.2 Multiple system TSS Operators need to log on to the system simultaneously in order to do independent functions at different intersections or to view the same intersection.
3.1.1.8	The system shall allow access to a traffic signal database based on user privileges.	4.1.4.4 The TSS Operator needs to view the status of an intersection or group of intersections even when another TSS Operator is editing the intersection database.
3.1.2	Security
3.1.2.1	The system shall provide the ability to control and limit user access via user privileges (allowing for different levels of user access to system features and functions). Local access to the system Remote access to the system System monitoring System manual override Database Administration of the system Signal controller group access Access to classes of equipment Access to equipment by jurisdiction System parameters Report generation Configuration Security alerts	4.1.4.5 The TSS Operator needs to view the status of multiple agency signals, edit the intersection databases, and/or create reports, as allowed by permission.
3.1.2.2	The system shall provide user privileges definable for the following:	4.1.4.7 The TSS Manager needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by a TSS Manager, and conform to the agency's access and network infrastructure security policies.
3.1.2.2.1	Geographic area	4.1.4.7 The TSS Manager needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by a TSS Manager, and conform to the agency's access and network infrastructure security policies.
3.1.2.2.2	Time of Day	4.1.4.7 The TSS Manager needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by a TSS Manager, and conform to the agency's access and network infrastructure security policies.
3.1.2.2.3	Device ownership	4.1.4.7 The TSS Manager needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by a TSS Manager, and conform to the agency's access and network infrastructure security policies.
3.1.2.3	The system shall provide user privileges definable on a functional level:	4.1.4.7 The TSS Manager needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by a TSS Manager, and conform to the agency's access and network infrastructure security policies.
3.1.2.3.1	TSS Manager	4.1.4.7 The TSS Manager needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by a TSS Manager, and conform to the agency's access and network infrastructure security policies.
3.1.2.3.2	TSS Operator	4.1.4.7 The TSS Manager needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by a TSS Manager, and conform to the agency's access and network infrastructure security policies.
3.1.2.3.3	External System	4.1.4.7 The TSS Manager needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by a TSS Manager, and conform to the agency's access and network infrastructure security policies.
3.1.2.3.4	TSS Maintainer	4.1.4.7 The TSS Manager needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by a TSS Manager, and conform to the agency's access and network infrastructure security policies.
3.1.2.4	The system shall comply with the agency's security policy as described in (specify appropriate policy document)	4.1.4.6 The TSS Operator needs secure access to the system consistent with the existing agency network policies.
3.1.2.4	The system shall comply with the agency's security policy as described in (specify appropriate policy document)	4.7.1.2 The TSS Designer needs to use equipment and software acceptable under current agency IT policies and procedures (USER TO SPECIFY)
3.1.2.5	The system shall provide full access to the administrator.	4.1.4.5 The TSS Operator needs to view the status of multiple agency signals, edit the intersection databases, and/or create reports, as allowed by permission.
3.1.2.5	The system shall provide full access to the administrator.	4.1.4.6 The TSS Operator needs secure access to the system consistent with the existing agency network policies.
3.1.2.6	The system shall show operators/administrator who is logged in to the system at a given time.	4.1.4.2 Multiple system TSS Operators need to log on to the system simultaneously in order to do independent functions at different intersections or to view the same intersection.
3.1.2.7	For Adaptive Systems, the ASCT shall be implemented with a security policy that addresses the following selected elements: Local access to the ASCT Remote access to the ASCT System monitoring System manual override Development Operations User login User password Administration of the system Signal controller group access Access to classes of equipment Access to equipment by jurisdiction Output activation System parameters Report generation Configuration Security alerts Security logging Security reporting Database Signal controller	4.1.4.7 The TSS Manager needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by a TSS Manager, and conform to the agency's access and network infrastructure security policies.
3.1.2.8	The ASCT shall provide monitoring and control access at the following locations:	4.4.2.1 The TSS Operator needs to monitor and control all required features of adaptive operation from the following locations: (Edit and select as appropriate to suit your situation.)
3.1.2.8.1	Agency TMC	4.4.2.1.1 Agency TMC
3.1.2.8.2	Agency LAN or WAN	4.4.2.1.2 Maintenance facility
3.1.2.8.2	Agency LAN or WAN	4.4.2.1.3 Workstations on agency LAN or WAN located at (specify)
3.1.2.8.3	Other agency TMC (Specify)	4.4.2.1.3 Workstations on agency LAN or WAN located at (specify)
3.1.2.8.3	Other agency TMC (Specify)	4.4.2.1.4 Other agency's TMC (specify)
3.1.2.8.4	Other agency TMC (Specify)	4.4.2.1.4 Other agency's TMC (specify)
3.1.2.8.5	Local controller cabinets (wireless)	4.4.2.1.5 Local controller cabinets
3.1.2.8.6	Local controller cabinets (hard wire)	4.4.2.1.5 Local controller cabinets
3.1.2.8.7	Remote locations via internet	4.4.2.1.6 Maintenance vehicles
3.1.2.8.8	Remote locations via internet	4.4.2.1.7 Remote locations (specify)
3.1.2.9	The ASCT shall comply with the agency's security policy as described in (specify appropriate policy document).	4.1.4.7 The TSS Manager needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by a TSS Manager, and conform to the agency's access and network infrastructure security policies.
3.1.2.10	The ASCT shall not prevent access to the local signal controller database, monitoring or reporting functions by any installed signal management system.	4.4.2.2 The operator needs to access to the database management, monitoring and reporting features and functions of the signal controllers and any related signal management system from the access points defined for those system components.
3.1.3	System Configuration
3.1.3.1	Network Characteristics
3.1.3.1.1	The system shall control a minimum of XXX local signal controllers	4.1.1.1 The TSS Operator needs to view and control up to XXX traffic signal controllers, at various locations within the (agency).
3.1.3.1.2	The system shall allow intersections to be included in a group.	4.1.1.2 The TSS Operator needs to organize the traffic signals in two (or more) groups for coordination purposes.
3.1.3.1.2	The system shall allow intersections to be included in a group.	4.1.1.3 The TSS Operator needs to change intersection grouping by time of day or other trigger.
3.1.3.1.2	The system shall allow intersections to be included in a group.	4.1.1.5 The TSS Operator needs to coordinate traffic signals managed by another system. Note: Cross-jurisdictional heading.
3.1.3.1.2	The system shall allow intersections to be included in a group.	4.5.7.1.2 The TSS Operator needs to select a predetermined group of intersections to monitor.
3.1.3.1.2.1	A group shall support up to XX signals.	4.1.1.2 The TSS Operator needs to organize the traffic signals in two (or more) groups for coordination purposes.
3.1.3.1.2.1	A group shall support up to XX signals.	4.5.7.1.2 The TSS Operator needs to select a predetermined group of intersections to monitor.
3.1.3.1.3	The system shall allow an intersection to be included in two or more groups.	4.1.1.2 The TSS Operator needs to organize the traffic signals in two (or more) groups for coordination purposes.
3.1.3.1.3	The system shall allow an intersection to be included in two or more groups.	4.1.1.3 The TSS Operator needs to change intersection grouping by time of day or other trigger.
3.1.3.1.3	The system shall allow an intersection to be included in two or more groups.	4.1.1.5 The TSS Operator needs to coordinate traffic signals managed by another system. Note: Cross-jurisdictional heading.
3.1.3.1.3	The system shall allow an intersection to be included in two or more groups.	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.3.1.3	The system shall allow an intersection to be included in two or more groups.	4.5.7.1.2 The TSS Operator needs to select a predetermined group of intersections to monitor.
3.1.3.1.3.1	The system shall allow intersections to change grouping by time of day schedule.	4.1.1.2 The TSS Operator needs to organize the traffic signals in two (or more) groups for coordination purposes.
3.1.3.1.3.1	The system shall allow intersections to change grouping by time of day schedule.	4.1.1.3 The TSS Operator needs to change intersection grouping by time of day or other trigger.
3.1.3.1.3.1	The system shall allow intersections to change grouping by time of day schedule.	4.1.1.5 The TSS Operator needs to coordinate traffic signals managed by another system. Note: Cross-jurisdictional heading.
3.1.3.1.3.1	The system shall allow intersections to change grouping by time of day schedule.	4.5.7.1.2 The TSS Operator needs to select a predetermined group of intersections to monitor.
3.1.3.1.3.2	The system shall allow intersections to change grouping by manual command.	4.1.1.2 The TSS Operator needs to organize the traffic signals in two (or more) groups for coordination purposes.
3.1.3.1.3.2	The system shall allow intersections to change grouping by manual command.	4.1.1.3 The TSS Operator needs to change intersection grouping by time of day or other trigger.
3.1.3.1.3.2	The system shall allow intersections to change grouping by manual command.	4.1.1.5 The TSS Operator needs to coordinate traffic signals managed by another system. Note: Cross-jurisdictional heading.
3.1.3.1.3.2	The system shall allow intersections to change grouping by manual command.	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.3.1.3.3	The system shall allow intersections to change grouping by (enter trigger).	4.1.1.2 The TSS Operator needs to organize the traffic signals in two (or more) groups for coordination purposes.
3.1.3.1.3.3	The system shall allow intersections to change grouping by (enter trigger).	4.1.1.3 The TSS Operator needs to change intersection grouping by time of day or other trigger.
3.1.3.2	Adaptive Network Characteristics
3.1.3.2.1	The ASCT shall control a minimum of XX signals concurrently. Note: communications network characteristics based on mileage distance.	4.1.2.1 The TSS Operator needs to adaptively control up to XXX signals, up to XXX miles from the TMC (or specified location).
3.1.3.2.2	The ASCT shall support groups of signals.	4.1.2.2 The TSS Operator needs to be able to adaptively control up to XX independent groups of signals
3.1.3.2.2	The ASCT shall support groups of signals.	4.1.2.3 The TSS Operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.
3.1.3.2.2.1	The boundaries surrounding signal controllers that operate in a coordinated fashion shall be defined by the user.	4.1.2.2 The TSS Operator needs to be able to adaptively control up to XX independent groups of signals
3.1.3.2.2.2	The ASCT shall control a minimum of XX groups of signals.	4.1.2.2 The TSS Operator needs to be able to adaptively control up to XX independent groups of signals
3.1.3.2.2.3	The size of a group shall range from 1 to XX signals.	4.1.2.3 The TSS Operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.
3.1.3.2.2.4	Each group shall operate independently	4.1.2.2 The TSS Operator needs to be able to adaptively control up to XX independent groups of signals
3.1.3.2.2.5	The boundaries surrounding signal controllers that operate in a coordinated fashion shall be altered by the ASCT system according to configured parameters.	4.1.2.3 The TSS Operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.
3.1.3.2.2.5.1	The boundaries surrounding signal controllers that operate in a coordinated fashion shall be altered by the system according to a time of day schedule. (For example: this may be achieved by assigning signals to different groups or by combining groups.)	4.1.2.3 The TSS Operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.
3.1.3.2.2.5.2	The boundaries surrounding signal controllers that operate in a coordinated fashion shall be altered by the system according to traffic conditions. (For example: this may be achieved by assigning signals to different groups or by combining groups.)	4.1.2.3 The TSS Operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.
3.1.3.2.2.5.3	The boundaries surrounding signal controllers that operate in a coordinated fashion shall be altered by the system when commanded by the user.	4.1.2.3 The TSS Operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.
3.1.3.3	Traffic Performance Measurement Characteristics
3.1.3.3.1	The Performance Measurement Server shall configure how the high-resolution data is handled from local traffic signal controllers. [This requires the agency to provide traffic signal controllers that store the high-resolution data, which are not covered by these Model Documents.]	4.1.3.1 The TSS Operator needs to configure performance measurement operations.
3.1.3.3.1.1	High-resolution data shall include all enumerated events as described in Sturdevant, et. al., Indiana High Resolution Data Logger Enumerations, November, 2012, or later document as developed under Pooled Fund Study TPF-5(377).	4.1.3.1 The TSS Operator needs to configure performance measurement operations.
3.1.3.3.1.2	High-resolution data interface is defined by (Specify latest interface control document, if available—Pooled Fund Study TPF-5(377), currently underway, will: Update the data logger specification to provide secure file transfer, incorporate new enumerations that have emerged, and logging new connected vehicle messages.	4.1.3.1 The TSS Operator needs to configure performance measurement operations.
3.1.3.3.1.3	The Performance Measurement Server shall be a separate server, independent of the TSS or ASCT.	4.1.3.1 The TSS Operator needs to configure performance measurement operations.
3.1.3.3.1.3.1	The Performance Measurement Server shall run ATSPM version 4.0 (or more recent version) available from the FHWA Open Source Application Development Portal.	4.1.3.1 The TSS Operator needs to configure performance measurement operations.
3.1.3.3.1.3.2	The Performance Measurement Server shall be co-located with the TSS. (In such cases, it shall be owned by the TSS System Manager.) [This requirement is exclusive of 3.1.3.3.1.3.3—choose one or the other]	4.1.3.1 The TSS Operator needs to configure performance measurement operations.
3.1.3.3.1.3.3	The Performance Measurement Server shall be located at an alternative location [specify] and managed and maintained by a separate entity [specify]. [This requirement allows the server to be shared by multiple agencies but managed by one of them, or provided as a service by a private-sector provider. Please specify in this requirement. This requirement is exclusive of 3.1.3.3.1.3.2]	4.1.3.1 The TSS Operator needs to configure performance measurement operations.
3.1.3.3.1.3.4	The Performance Measurement Server shall be integrated into the TSS (ASCT).	4.1.3.1 The TSS Operator needs to configure performance measurement operations.
3.1.3.3.1.3.4.1	The Performance Measurement Server shall run ATSPM version 4.0 (or more recent version) available from the FHWA Open Source Application Development Portal. The open-source software may be revised to facilitate integration, or to extend to additional features that may be required herein.	4.1.3.1 The TSS Operator needs to configure performance measurement operations.
3.1.3.4	Overall Architecture
3.1.3.4.1	The system shall fully satisfy all requirements when connected to XX local controllers (SPECIFY local controller type)	4.1.5.3 The TSS Operator needs to fully operate the system within a communications bandwidth limit of XXX Mbps. (SPECIFY APPLICABLE LIMITS)
3.1.3.4.1	The system shall fully satisfy all requirements when connected to XX local controllers (SPECIFY local controller type)	4.7.1.1 The TSS Designer is constrained to using the following equipment: - Controller type (list acceptable equipment) - Controller firmware (list acceptable firmware) - Communication system (list acceptable equipment) - Cabinet type and size (list acceptable equipment) - Signal management system (list acceptable systems)
3.1.3.4.1	The system shall fully satisfy all requirements when connected to XX local controllers (SPECIFY local controller type)	4.7.1.3 The TSS Designer needs to use specific communications protocols (specify AB3418E, NTCIP, or other) to all existing and future traffic signal controllers connected to the system.
3.1.3.4.1.1	Controller type (list applicable equipment)	4.7.1.1 The TSS Designer is constrained to using the following equipment: - Controller type (list acceptable equipment) - Controller firmware (list acceptable firmware) - Communication system (list acceptable equipment) - Cabinet type and size (list acceptable equipment) - Signal management system (list acceptable systems)
3.1.3.4.1.2	Local firmware (list applicable firmware)	4.7.1.1 The TSS Designer is constrained to using the following equipment: - Controller type (list acceptable equipment) - Controller firmware (list acceptable firmware) - Communication system (list acceptable equipment) - Cabinet type and size (list acceptable equipment) - Signal management system (list acceptable systems)
3.1.3.4.1.3	Communications media and protocols (list applicable equipment)	4.1.5.3 The TSS Operator needs to fully operate the system within a communications bandwidth limit of XXX Mbps. (SPECIFY APPLICABLE LIMITS)
3.1.3.4.1.3	Communications media and protocols (list applicable equipment)	4.7.1.1 The TSS Designer is constrained to using the following equipment: - Controller type (list acceptable equipment) - Controller firmware (list acceptable firmware) - Communication system (list acceptable equipment) - Cabinet type and size (list acceptable equipment) - Signal management system (list acceptable systems)
3.1.3.4.1.3	Communications media and protocols (list applicable equipment)	4.7.1.3 The TSS Designer needs to use specific communications protocols (specify AB3418E, NTCIP, or other) to all existing and future traffic signal controllers connected to the system.
3.1.3.4.1.3.1	AB3418E	4.1.5.3 The TSS Operator needs to fully operate the system within a communications bandwidth limit of XXX Mbps. (SPECIFY APPLICABLE LIMITS)
3.1.3.4.1.3.1	AB3418E	4.7.1.3 The TSS Designer needs to use specific communications protocols (specify AB3418E, NTCIP, or other) to all existing and future traffic signal controllers connected to the system.
3.1.3.4.1.3.2	NTCIP (SPECIFY relevant items)	4.1.5.3 The TSS Operator needs to fully operate the system within a communications bandwidth limit of XXX Mbps. (SPECIFY APPLICABLE LIMITS)
3.1.3.4.1.3.2	NTCIP (SPECIFY relevant items)	4.7.1.3 The TSS Designer needs to use specific communications protocols (specify AB3418E, NTCIP, or other) to all existing and future traffic signal controllers connected to the system.
3.1.3.4.2	The system shall fulfill all requirements when connected to XX local controller firmware (SPECIFY local controller firmware)	4.7.1.1 The TSS Designer is constrained to using the following equipment: - Controller type (list acceptable equipment) - Controller firmware (list acceptable firmware) - Communication system (list acceptable equipment) - Cabinet type and size (list acceptable equipment) - Signal management system (list acceptable systems)
3.1.3.4.3	The system shall fully satisfy all requirements when connected to the existing communications network	4.7.1.3 The TSS Designer needs to use specific communications protocols (specify AB3418E, NTCIP, or other) to all existing and future traffic signal controllers connected to the system.
3.1.3.4.3	The system shall fully satisfy all requirements when connected to the existing communications network	4.7.1.4 The TSS Designer needs to communicate to traffic signal controllers using Ethernet protocol (OR SERIAL OR OTHER. USER TO SPECIFY).
3.1.3.4.4	The system shall fulfill requirements within a communications bandwidth limit of XX Mbps (specify applicable limits).	4.1.5.3 The TSS Operator needs to fully operate the system within a communications bandwidth limit of XXX Mbps. (SPECIFY APPLICABLE LIMITS)
3.1.3.4.5	The system shall work with the existing communications architecture (DEFINE characteristics, specifications and layout of system).	4.1.5.1 The TSS Operator needs to operate the system with the following architecture (EDIT TO SUIT YOUR SITUATION): Standalone server located at XX Virtual server On-street masters Center to center (multiple servers) Integrated with an Advanced Traffic Management System Cloud based Note: These interfaces are beyond the scope of the Model Systems Engineering documents, and responding to these needs will require additional systems engineering activities to develop needs and requirements related to these interfaces.
3.1.3.4.5.1	The system shall operate on a stand alone server located at (SPECIFY LOCATION)	4.1.5.1 The TSS Operator needs to operate the system with the following architecture (EDIT TO SUIT YOUR SITUATION): Standalone server located at XX Virtual server On-street masters Center to center (multiple servers) Integrated with an Advanced Traffic Management System Cloud based Note: These interfaces are beyond the scope of the Model Systems Engineering documents, and responding to these needs will require additional systems engineering activities to develop needs and requirements related to these interfaces.
3.1.3.4.5.2	The system shall operate as cloud based.	4.1.5.1 The TSS Operator needs to operate the system with the following architecture (EDIT TO SUIT YOUR SITUATION): Standalone server located at XX Virtual server On-street masters Center to center (multiple servers) Integrated with an Advanced Traffic Management System Cloud based Note: These interfaces are beyond the scope of the Model Systems Engineering documents, and responding to these needs will require additional systems engineering activities to develop needs and requirements related to these interfaces.
3.1.3.4.5.3	The system shall operate with center to center capabilities.	4.1.5.1 The TSS Operator needs to operate the system with the following architecture (EDIT TO SUIT YOUR SITUATION): Standalone server located at XX Virtual server On-street masters Center to center (multiple servers) Integrated with an Advanced Traffic Management System Cloud based Note: These interfaces are beyond the scope of the Model Systems Engineering documents, and responding to these needs will require additional systems engineering activities to develop needs and requirements related to these interfaces.
3.1.3.4.5.4	The system shall be integrated with an Advance Traffic Management System (SPECIFY)	4.1.5.1 The TSS Operator needs to operate the system with the following architecture (EDIT TO SUIT YOUR SITUATION): Standalone server located at XX Virtual server On-street masters Center to center (multiple servers) Integrated with an Advanced Traffic Management System Cloud based Note: These interfaces are beyond the scope of the Model Systems Engineering documents, and responding to these needs will require additional systems engineering activities to develop needs and requirements related to these interfaces.
3.1.3.4.5.5	The system shall operate with on-street masters.	4.1.5.1 The TSS Operator needs to operate the system with the following architecture (EDIT TO SUIT YOUR SITUATION): Standalone server located at XX Virtual server On-street masters Center to center (multiple servers) Integrated with an Advanced Traffic Management System Cloud based Note: These interfaces are beyond the scope of the Model Systems Engineering documents, and responding to these needs will require additional systems engineering activities to develop needs and requirements related to these interfaces.
3.1.3.4.6	The system shall use the following communications protocols with traffic signal controllers (SPECIFY as appropriate)	4.1.5.3 The TSS Operator needs to fully operate the system within a communications bandwidth limit of XXX Mbps. (SPECIFY APPLICABLE LIMITS)
3.1.3.4.6	The system shall use the following communications protocols with traffic signal controllers (SPECIFY as appropriate)	4.7.1.4 The TSS Designer needs to communicate to traffic signal controllers using Ethernet protocol (OR SERIAL OR OTHER. USER TO SPECIFY).
3.1.3.4.6.1	Ethernet	4.1.5.3 The TSS Operator needs to fully operate the system within a communications bandwidth limit of XXX Mbps. (SPECIFY APPLICABLE LIMITS)
3.1.3.4.6.1	Ethernet	4.7.1.4 The TSS Designer needs to communicate to traffic signal controllers using Ethernet protocol (OR SERIAL OR OTHER. USER TO SPECIFY).
3.1.3.4.6.2	Serial	4.1.5.3 The TSS Operator needs to fully operate the system within a communications bandwidth limit of XXX Mbps. (SPECIFY APPLICABLE LIMITS)
3.1.3.4.6.2	Serial	4.7.1.4 The TSS Designer needs to communicate to traffic signal controllers using Ethernet protocol (OR SERIAL OR OTHER. USER TO SPECIFY).
3.1.3.4.6.3	Other [Specify]	4.1.5.3 The TSS Operator needs to fully operate the system within a communications bandwidth limit of XXX Mbps. (SPECIFY APPLICABLE LIMITS)
3.1.3.4.6.3	Other [Specify]	4.7.1.4 The TSS Designer needs to communicate to traffic signal controllers using Ethernet protocol (OR SERIAL OR OTHER. USER TO SPECIFY).
3.1.3.4.7	Any field device installed as part of the TSS shall fulfill NEMA TS-2 environmental requirements.	4.7.1.6 The TSS Operator needs access to and operation of the system in all environmental conditions.
3.1.3.4.8	The system shall be fully implemented within the available budget of $[Specify]. (or included in procurement documents but not in system requirements)	4.7.1.7 The TSS Designer needs to fully implement the system with full capability within the available budget of $(USER TO SPECIFY). (or included in procurement documents but not in system requirements)
3.1.3.6	The system shall download timing parameters to two or more controllers with one command.	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.4	Database Development
3.1.4.1	The system shall create a timing database that includes all settable signal timing parameters for a given intersection local controller based on TSS Operator input and appropriate look up tables (SPECIFY controller and firmware version).	4.2.1.1 The TSS Operator needs to quickly and efficiently configure local and coordinated signal timing parameters, by entering the values manually or copying and editing values. The database needs to be a complete and accurate representation of the local controller database.
3.1.4.1	The system shall create a timing database that includes all settable signal timing parameters for a given intersection local controller based on TSS Operator input and appropriate look up tables (SPECIFY controller and firmware version).	4.2.1.5 The TSS Operator needs to develop, save and access timing parameters for a temporary condition (such as modifying phases during construction) or a new condition (such as new coordinated timings) without losing information in the original database.
3.1.4.2	The system shall allow TSS Operator to enter all settable timing parameter values manually.	4.2.1.1 The TSS Operator needs to quickly and efficiently configure local and coordinated signal timing parameters, by entering the values manually or copying and editing values. The database needs to be a complete and accurate representation of the local controller database.
3.1.4.3	The system shall provide default intersection timing database templates containing the following data (SPECIFY others if needed): Min green, Max green, walk, flashing don't walk, yellow, red Emergency Vehicle Preemption data Flashing yellow left turn arrow	4.2.1.1 The TSS Operator needs to quickly and efficiently configure local and coordinated signal timing parameters, by entering the values manually or copying and editing values. The database needs to be a complete and accurate representation of the local controller database.
3.1.4.4	The system shall create a copy of an entire intersection timing database.	4.2.1.1 The TSS Operator needs to quickly and efficiently configure local and coordinated signal timing parameters, by entering the values manually or copying and editing values. The database needs to be a complete and accurate representation of the local controller database.
3.1.4.5	The system shall copy parts of one intersection timing database and paste to another intersection timing database (e.g., time of day schedule)	4.2.1.1 The TSS Operator needs to quickly and efficiently configure local and coordinated signal timing parameters, by entering the values manually or copying and editing values. The database needs to be a complete and accurate representation of the local controller database.
3.1.4.6	The system stall copy parts of an intersection timing database and paste within the same database (e.g., timing pattern data)	4.2.1.1 The TSS Operator needs to quickly and efficiently configure local and coordinated signal timing parameters, by entering the values manually or copying and editing values. The database needs to be a complete and accurate representation of the local controller database.
3.1.4.7	The system shall create up to (X) versions of an intersection timing database.	4.2.1.5 The TSS Operator needs to develop, save and access timing parameters for a temporary condition (such as modifying phases during construction) or a new condition (such as new coordinated timings) without losing information in the original database.
3.1.4.8	The system shall provide safeguards when developing new signal databases, including: Range checking Timing plan verification Conflicting phases	4.2.1.2 The TSS Operator needs to verify the validity of all parameters in the controller database, check for errors, and alert the TSS Operator before downloading it to the field controller.
3.1.4.9	The system shall create a timing sheet that includes: All timing parameters relevant for operating a traffic signal. Phase rotation diagram with north arrow User selected parts of the timing database Modified timings User specified Only non-zero timing parameters	4.2.1.4 The TSS Operator needs to view and print timing sheets that include all the operational timing parameters, including phase diagrams. The timing sheets should be user customizable.
3.1.4.10	The system shall transfer the following signal timing data to and from Optimization Software (SPECIFY TYPE and Version ): Node number Phase number and direction Phase minimum green Phase vehicle yellow clearance Phase pedestrian walk Phase vehicle all red Phase pedestrian clearance Cycle length Offset Coordination splits	4.2.1.3 The TSS Operator needs to interface with Optimization Software (SPECIFY TYPE and VERSION) in order to develop and update coordinated timing plans.
3.1.5	Database Management
3.1.5.1	The system shall upload/download the intersection database to a controller: By manual TSS Operator command By time of day schedule	4.2.2.1 The TSS Operator needs to quickly and efficiently upload and download timing parameters between the system and local controllers with no risk of data corruption or errors.
3.1.5.2	The system shall download the entire intersection database to a controller.	4.2.2.1 The TSS Operator needs to quickly and efficiently upload and download timing parameters between the system and local controllers with no risk of data corruption or errors.
3.1.5.2	The system shall download the entire intersection database to a controller.	4.2.2.3 The TSS Operator needs to upload and download timings to a single intersection or a group of intersections, such as to download a command for a special incident timing plan along a corridor or to change the offset at multiple intersections while fine tuning the coordinated timings.
3.1.5.3	The system shall upload the entire intersection database from a controller.	4.2.2.1 The TSS Operator needs to quickly and efficiently upload and download timing parameters between the system and local controllers with no risk of data corruption or errors.
3.1.5.3	The system shall upload the entire intersection database from a controller.	4.2.2.3 The TSS Operator needs to upload and download timings to a single intersection or a group of intersections, such as to download a command for a special incident timing plan along a corridor or to change the offset at multiple intersections while fine tuning the coordinated timings.
3.1.5.4	The system shall download select parts of an intersection database to a controller.	4.2.2.1 The TSS Operator needs to quickly and efficiently upload and download timing parameters between the system and local controllers with no risk of data corruption or errors.
3.1.5.4	The system shall download select parts of an intersection database to a controller.	4.2.2.3 The TSS Operator needs to upload and download timings to a single intersection or a group of intersections, such as to download a command for a special incident timing plan along a corridor or to change the offset at multiple intersections while fine tuning the coordinated timings.
3.1.5.5	The system shall upload select parts of an intersection database from a controller.	4.2.2.1 The TSS Operator needs to quickly and efficiently upload and download timing parameters between the system and local controllers with no risk of data corruption or errors.
3.1.5.5	The system shall upload select parts of an intersection database from a controller.	4.2.2.3 The TSS Operator needs to upload and download timings to a single intersection or a group of intersections, such as to download a command for a special incident timing plan along a corridor or to change the offset at multiple intersections while fine tuning the coordinated timings.
3.1.5.6	The system shall download timing parameters to two or more controllers with one command.	4.2.2.3 The TSS Operator needs to upload and download timings to a single intersection or a group of intersections, such as to download a command for a special incident timing plan along a corridor or to change the offset at multiple intersections while fine tuning the coordinated timings.
3.1.5.6	The system shall download timing parameters to two or more controllers with one command.	4.4.9 Adaptive Complex Coordination and Controller Features
3.1.5.7	The system shall upload timing parameters from two or more controllers with one command.	4.2.2.3 The TSS Operator needs to upload and download timings to a single intersection or a group of intersections, such as to download a command for a special incident timing plan along a corridor or to change the offset at multiple intersections while fine tuning the coordinated timings.
3.1.5.8	The system shall request user confirmation of command prior to downloading data from the central database to a controller.	4.2.2.1 The TSS Operator needs to quickly and efficiently upload and download timing parameters between the system and local controllers with no risk of data corruption or errors.
3.1.5.8	The system shall request user confirmation of command prior to downloading data from the central database to a controller.	4.2.2.3 The TSS Operator needs to upload and download timings to a single intersection or a group of intersections, such as to download a command for a special incident timing plan along a corridor or to change the offset at multiple intersections while fine tuning the coordinated timings.
3.1.5.9	The system shall request user confirmation of command prior to saving uploaded data from a controller in the central database.	4.2.2.1 The TSS Operator needs to quickly and efficiently upload and download timing parameters between the system and local controllers with no risk of data corruption or errors.
3.1.5.9	The system shall request user confirmation of command prior to saving uploaded data from a controller in the central database.	4.2.2.3 The TSS Operator needs to upload and download timings to a single intersection or a group of intersections, such as to download a command for a special incident timing plan along a corridor or to change the offset at multiple intersections while fine tuning the coordinated timings.
3.1.5.10	The system shall archive all intersection databases when commanded by user.	4.2.2.4 The TSS Operator needs to have a full and permanent record, created automatically, of any changes to data entered directly into a local controller, including a record of the date and time at which the each change is entered.
3.1.5.11	The system shall cancel upload/download if any interruptions occur during the process.	4.2.2.1 The TSS Operator needs to quickly and efficiently upload and download timing parameters between the system and local controllers with no risk of data corruption or errors.
3.1.5.11	The system shall cancel upload/download if any interruptions occur during the process.	4.2.2.3 The TSS Operator needs to upload and download timings to a single intersection or a group of intersections, such as to download a command for a special incident timing plan along a corridor or to change the offset at multiple intersections while fine tuning the coordinated timings.
3.1.5.12	The system shall revert to previous version of the database at the request of the user.	4.2.2.1 The TSS Operator needs to quickly and efficiently upload and download timing parameters between the system and local controllers with no risk of data corruption or errors.
3.1.5.13	The system shall log any changes made to the database, including: What was changed Who made the change When the change occurred	4.2.2.4 The TSS Operator needs to have a full and permanent record, created automatically, of any changes to data entered directly into a local controller, including a record of the date and time at which the each change is entered.
3.1.5.13	The system shall log any changes made to the database, including: What was changed Who made the change When the change occurred	4.5.1.3 The TSS Operator needs a time-stamped record of who accesses the system, all manual commands, and data changes made during a session.
3.1.5.13	The system shall log any changes made to the database, including: What was changed Who made the change When the change occurred	4.5.1.4 The TSS Operator needs a log of all software functions executed by the central system and local controllers.
3.1.5.14	The system shall compare two intersection databases (central and local) and highlight the differences.	4.2.2.2 The TSS Operator needs to compare the field controller database with the central database and save all or part of the local controller database to the central database.
3.1.5.15	The system shall save the entire uploaded intersection database.	4.2.2.1 The TSS Operator needs to quickly and efficiently upload and download timing parameters between the system and local controllers with no risk of data corruption or errors.
3.1.5.15	The system shall save the entire uploaded intersection database.	4.2.2.2 The TSS Operator needs to compare the field controller database with the central database and save all or part of the local controller database to the central database.
3.1.5.15	The system shall save the entire uploaded intersection database.	4.2.2.4 The TSS Operator needs to have a full and permanent record, created automatically, of any changes to data entered directly into a local controller, including a record of the date and time at which the each change is entered.
3.1.5.16	The system shall save selected parts of an uploaded intersection database.	4.2.2.1 The TSS Operator needs to quickly and efficiently upload and download timing parameters between the system and local controllers with no risk of data corruption or errors.
3.1.5.16	The system shall save selected parts of an uploaded intersection database.	4.2.2.2 The TSS Operator needs to compare the field controller database with the central database and save all or part of the local controller database to the central database.
3.1.5.16	The system shall save selected parts of an uploaded intersection database.	4.2.2.4 The TSS Operator needs to have a full and permanent record, created automatically, of any changes to data entered directly into a local controller, including a record of the date and time at which the each change is entered.
3.1.5.17	The system shall clearly identify the official version of the timing database.	4.2.1.5 The TSS Operator needs to develop, save and access timing parameters for a temporary condition (such as modifying phases during construction) or a new condition (such as new coordinated timings) without losing information in the original database.
3.1.5.18	The system shall provide multiple methods to open an intersection database: Dynamically select intersection on map Search feature that uses intersection name and partial name Search feature that uses intersection ID number	4.2.2.5 The TSS Operator needs to search the system for each intersection database by using the intersection name or number or using the system map to point to and select the intersection.
3.1.5.19	The ASCT shall log the following events: (edit as appropriate)	4.5.1.5 The TSS Operator needs to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.
3.1.5.19.1	Time-stamped vehicle phase calls	4.5.1.5 The TSS Operator needs to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.
3.1.5.19.2	Time-stamped pedestrian phase calls	4.5.1.5 The TSS Operator needs to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.
3.1.5.19.3	Time-stamped emergency vehicle preemption calls	4.5.1.5 The TSS Operator needs to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.
3.1.5.19.4	Time-stamped transit priority calls	4.5.1.5 The TSS Operator needs to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.
3.1.5.19.5	Time-stamped railroad preemption calls	4.5.1.5 The TSS Operator needs to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.
3.1.5.19.6	Time-stamped start and end of each phase	4.5.1.5 The TSS Operator needs to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.
3.1.5.19.7	Time-stamped controller interval changes	4.5.1.5 The TSS Operator needs to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.
3.1.5.19.8	Time-stamped start and end of each transition to a new timing plan.	4.5.1.5 The TSS Operator needs to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.
3.1.5.20	The ASCT shall export its systems log in the following formats: (edit as appropriate) MS Excel Text CVS Open source SQL database	4.5.2.4 The TSS Operator needs to store all operational data and signal timing parameters calculated by the adaptive system, and export selected data to (specify appropriate external system).
3.1.5.21	The ASCT shall store the event log for a minimum of XX days	4.5.2.4 The TSS Operator needs to store all operational data and signal timing parameters calculated by the adaptive system, and export selected data to (specify appropriate external system).
3.1.5.22	The TSS shall store results of all signal timing parameter calculations for a minimum of XX days.	4.5.2.2 The TSS Operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.
3.1.5.22	The TSS shall store results of all signal timing parameter calculations for a minimum of XX days.	4.5.2.3 The TSS Operator needs to store and report data that can be used to measure traffic performance under adaptive control.
3.1.5.23	The ASCT shall store the following measured data in the form used as input to the adaptive algorithm for a minimum of XX days: (edit as appropriate) volume occupancy queue length phase utilization arrivals in green green band efficiency	4.5.2.2 The TSS Operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.
3.1.5.23	The ASCT shall store the following measured data in the form used as input to the adaptive algorithm for a minimum of XX days: (edit as appropriate) volume occupancy queue length phase utilization arrivals in green green band efficiency	4.5.2.3 The TSS Operator needs to store and report data that can be used to measure traffic performance under adaptive control.
3.1.5.23	The ASCT shall store the following measured data in the form used as input to the adaptive algorithm for a minimum of XX days: (edit as appropriate) volume occupancy queue length phase utilization arrivals in green green band efficiency	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.5.24	The ASCT system shall archive all data automatically after a user-specified period not less than XX days.	4.5.2.4 The TSS Operator needs to store all operational data and signal timing parameters calculated by the adaptive system, and export selected data to (specify appropriate external system).
3.1.5.25	The ASCT shall provide data storage for a system size of XX signal controllers. The data to be stored shall include the following: (edit as appropriate) Controller state data Reports Log data Security data ASCT parameters Detector status data	4.5.2.4 The TSS Operator needs to store all operational data and signal timing parameters calculated by the adaptive system, and export selected data to (specify appropriate external system).
3.1.5.26	The ASCT shall calculate and report relative data quality including: The extent data is affected by detector faults Other applicable items	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.5.27	The ASCT shall report comparisons of logged data when requested by the user: Day to day, Hour to hour Hour of day to hour of day Hour of week to hour of week Day of week to day week Day of year to day of year	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.5.28	The ASCT shall store data logs in a standard database (specify as appropriate).	4.5.2.4 The TSS Operator needs to store all operational data and signal timing parameters calculated by the adaptive system, and export selected data to (specify appropriate external system).
3.1.5.29	The ASCT shall report stored data in a form suitable to provide explanations of system behavior to public and politicians and to troubleshoot the system.	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.5.30	The ASCT shall store the following data in XX minute increments: (edit as appropriate) volume occupancy queue length	4.5.2.2 The TSS Operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.
3.1.5.30	The ASCT shall store the following data in XX minute increments: (edit as appropriate) volume occupancy queue length	4.5.2.3 The TSS Operator needs to store and report data that can be used to measure traffic performance under adaptive control.
3.1.6	Failure Events and Fallback
3.1.6.1	Detector Failure
3.1.6.1.1	The ASCT shall take user-specified action in the absence of valid detector data from XX vehicle detectors within a group. (SELECT THE APPROPRIATE ACTION.)	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.1.1.1	The ASCT shall release control to central system control.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.1.1.2	The ASCT shall release control to local operations to operate under its own time-of-day schedule.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.1.2	The ASCT shall use the following alternate data sources for operations in the absence of the real-time data from a detector:	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.1.2.1	Data from a user-specified alternate detector.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.1.2.2	Stored historical data from the failed detector.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.1.2.3	The ASCT shall switch to the alternate source in real time without operator intervention.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.1.3	In the event of a detector failure, the ASCT shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance management system.	4.4.10.1 The TSS Operator needs to immediately notify maintenance and operations staff of alarms and alerts.
3.1.6.1.3	In the event of a detector failure, the ASCT shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance management system.	4.4.10.2 The TSS Operator needs to immediately and automatically pass alarms and alerts to the (specify external system).
3.1.6.1.4	In the event of a failure, the TSS/ASCT shall log details of the failure in a permanent log.	4.1.6.2 The TSS Operator needs to maintain a complete log of alarms and failure events.
3.1.6.1.5	The permanent failure log shall be searchable, archivable and exportable.	4.1.6.2 The TSS Operator needs to maintain a complete log of alarms and failure events.
3.1.6.2	Communications Failure
3.1.6.2.1	The TSS shall execute user-specified actions when communications to one or more signal controllers fails within a group. (SELECT THE APPROPRIATE ACTION)	4.1.6.1 The TSS Operator needs the local traffic signal controllers to fall back to local control without causing disruption to traffic flow, in the event of equipment, communications, or software failure.
3.1.6.2.1.1	In the event of loss of communication to a user-specified signal controller, the TSS shall release control of all signal controllers within a user-specified group to local control.	4.1.6.1 The TSS Operator needs the local traffic signal controllers to fall back to local control without causing disruption to traffic flow, in the event of equipment, communications, or software failure.
3.1.6.2.1.2	The TSS shall switch to the alternate operation in real time without operator intervention.	4.1.6.1 The TSS Operator needs the local traffic signal controllers to fall back to local control without causing disruption to traffic flow, in the event of equipment, communications, or software failure.
3.1.6.2.2	In the event of communications failure, the TSS shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance management system.	4.5.6.3 The TSS Operator needs to immediately notify maintenance and operations staff of alarms and alerts.
3.1.6.2.2	In the event of communications failure, the TSS shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance management system.	4.5.6.4 The TSS Operator needs to immediately and automatically pass alarms and alerts to the (specify external system).
3.1.6.2.3	The TSS shall issue an alarm within XX minutes of detection of a failure.	4.5.6.3 The TSS Operator needs to immediately notify maintenance and operations staff of alarms and alerts.
3.1.6.2.3	The TSS shall issue an alarm within XX minutes of detection of a failure.	4.5.6.4 The TSS Operator needs to immediately and automatically pass alarms and alerts to the (specify external system).
3.1.6.2.4	The ASCT shall execute user-specified actions when communications to one or more signal controllers fails within a group. (SELECT THE APPROPRIATE ACTION)	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.2.4.1	In the event of loss of communication to a user-specified signal controller, the ASCT shall release control of all signal controllers within a user-specified group to local control.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.2.4.2	The ASCT shall switch to the alternate operation in real time without operator intervention.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.2.5	In the event of communications failure, the ASCT shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance management system.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.2.5	In the event of communications failure, the ASCT shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance management system.	4.4.10.1 The TSS Operator needs to immediately notify maintenance and operations staff of alarms and alerts.
3.1.6.2.5	In the event of communications failure, the ASCT shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance management system.	4.4.10.2 The TSS Operator needs to immediately and automatically pass alarms and alerts to the (specify external system).
3.1.6.2.6	The ASCT shall issue an alarm within XX minutes of detection of a failure.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.2.6	The ASCT shall issue an alarm within XX minutes of detection of a failure.	4.4.10.1 The TSS Operator needs to immediately notify maintenance and operations staff of alarms and alerts.
3.1.6.2.6	The ASCT shall issue an alarm within XX minutes of detection of a failure.	4.4.10.2 The TSS Operator needs to immediately and automatically pass alarms and alerts to the (specify external system).
3.1.6.2.7	In the event of a communications failure, the TSS/ASCT shall log details of the failure in a permanent log.	4.1.6.2 The TSS Operator needs to maintain a complete log of alarms and failure events.
3.1.6.2.8	The permanent failure log shall be searchable, archivable and exportable.	4.1.6.2 The TSS Operator needs to maintain a complete log of alarms and failure events.
3.1.6.3	Adaptive Processor Failure
3.1.6.3.1	The ASCT shall execute user-specified actions when adaptive control fails:	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.3.1.1	The ASCT shall release control to central system control.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.3.1.2	The ASCT shall release control to local operations to operate under its own time-of-day schedule.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.3.2	In the event of adaptive processor failure, the ASCT shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.6.3.2	In the event of adaptive processor failure, the ASCT shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance	4.4.10.1 The TSS Operator needs to immediately notify maintenance and operations staff of alarms and alerts.
3.1.6.3.2	In the event of adaptive processor failure, the ASCT shall issue an alarm to user-specified recipients. (This requirement may be fulfilled by sending the alarm to a designated list of recipients by a designated means, or by using an external maintenance	4.4.10.2 The TSS Operator needs to immediately and automatically pass alarms and alerts to the (specify external system).
3.1.6.3.3	The permanent failure log shall be searchable, archivable and exportable.
3.1.6.3.4	During adaptive processor failure, the ASCT shall provide all local detector inputs to the local controller.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.7	Monitoring
3.1.7.1	Mapping
3.1.7.1.1	The system shall update the status of all traffic signal controller connected to the system every (XX) seconds.	4.1.5.2 The TSS Operator needs to access the system at all times to view status or manage the system.
3.1.7.1.2	The system shall update the status of all traffic signal controllers connected to the system 24 hours a day, 7 days a week.	4.1.5.2 The TSS Operator needs to access the system at all times to view status or manage the system.
3.1.7.1.3	The system shall provide a map that displays different levels of information: Statewide Area-wide Corridor Intersection	4.5.7.1 The TSS Operator needs to observe the operation of traffic signal field equipment.
3.1.7.1.3	The system shall provide a map that displays different levels of information: Statewide Area-wide Corridor Intersection	4.5.7.1.2 The TSS Operator needs to select a predetermined group of intersections to monitor.
3.1.7.1.3	The system shall provide a map that displays different levels of information: Statewide Area-wide Corridor Intersection	4.5.7.1.3 The TSS Operator needs to quickly and efficiently set up the intersection status display on the map, including all inputs and outputs at the intersection.
3.1.7.1.3	The system shall provide a map that displays different levels of information: Statewide Area-wide Corridor Intersection	4.5.7.1.4 The TSS Operator needs to view real time communications status, operational status and equipment status for all equipment connected to the signal system. The status should be color coded to quickly see issues.
3.1.7.1.4	The system shall provide a display that uses a cloud based system map (SPECIFY DETAILS)	4.5.7.1.3 The TSS Operator needs to quickly and efficiently set up the intersection status display on the map, including all inputs and outputs at the intersection.
3.1.7.1.5	The system shall provide a display that uses an existing agency map as background (Autocad, GIS, JPEG, etc.)	4.5.7.1.3 The TSS Operator needs to quickly and efficiently set up the intersection status display on the map, including all inputs and outputs at the intersection.
3.1.7.1.6	The system shall move between levels seamlessly, without having to open new files or windows.	4.5.7.1 The TSS Operator needs to observe the operation of traffic signal field equipment.
3.1.7.1.6	The system shall move between levels seamlessly, without having to open new files or windows.	4.5.7.1.4 The TSS Operator needs to view real time communications status, operational status and equipment status for all equipment connected to the signal system. The status should be color coded to quickly see issues.
3.1.7.1.7	The system shall have pan and zoom capabilities.	4.5.7.1 The TSS Operator needs to observe the operation of traffic signal field equipment.
3.1.7.1.7	The system shall have pan and zoom capabilities.	4.5.7.1.4 The TSS Operator needs to view real time communications status, operational status and equipment status for all equipment connected to the signal system. The status should be color coded to quickly see issues.
3.1.7.1.8	The system shall automatically adjust the display depending on the 'zoom level'.	4.5.7.1 The TSS Operator needs to observe the operation of traffic signal field equipment.
3.1.7.1.8	The system shall automatically adjust the display depending on the 'zoom level'.	4.5.7.1.4 The TSS Operator needs to view real time communications status, operational status and equipment status for all equipment connected to the signal system. The status should be color coded to quickly see issues.
3.1.7.1.9	At the state wide and area-wide level map, the system shall display a color coded status of the following systems: Communication Coordination Intersection flash mode Preemption	4.5.7.1.4 The TSS Operator needs to view real time communications status, operational status and equipment status for all equipment connected to the signal system. The status should be color coded to quickly see issues.
3.1.7.1.10	At the corridor level map, the system shall display the following timing related information: Real time or other measurable period [Specify period length(s)] time-space-diagrams Split times Phase status Detector status (vehicle and pedestrian) Local cycle lengths/timer Background cycle length/timer Offset Intersection identifier	4.5.7.2 The TSS Operator needs to view a real-time time-space-diagram of user defined intersection group, including real time splits, offsets and coordinated phase detector actuations of each intersection in group.
3.1.7.1.11	The system shall provide a library of intersection drawings (e.g., standard four-legged intersections, standard tee intersection, five-legged intersection, six legged intersection, etc.) to develop intersection level graphics that are geometrically correct diagrams.	4.5.7.1.3 The TSS Operator needs to quickly and efficiently set up the intersection status display on the map, including all inputs and outputs at the intersection.
3.1.7.1.12	The system shall provide a library of symbols for inputs and outputs to help construct the intersection display.	4.5.7.1.3 The TSS Operator needs to quickly and efficiently set up the intersection status display on the map, including all inputs and outputs at the intersection.
3.1.7.1.13	The system shall allow the TSS Operator to import customized graphical icons to the map icon library.	4.5.7.1.3 The TSS Operator needs to quickly and efficiently set up the intersection status display on the map, including all inputs and outputs at the intersection.
3.1.7.1.14	The system shall display multiple individual intersection-level views simultaneously as separate displays or tiled windows (SPECIFY minimum and maximum numbers).	4.5.7.1 The TSS Operator needs to observe the operation of traffic signal field equipment.
3.1.7.1.14	The system shall display multiple individual intersection-level views simultaneously as separate displays or tiled windows (SPECIFY minimum and maximum numbers).	4.5.7.1.2 The TSS Operator needs to select a predetermined group of intersections to monitor.
3.1.7.2	Intersection Status
3.1.7.2.1	The system shall open the intersection display when the intersection on the main map is clicked on.	4.5.7.1.1 The TSS Operator needs to view real time display of an intersection and typical controller front panel information status of operating mode, phases, and detectors.
3.1.7.2.2	The system shall show the current phase status of an intersection upon operator selection of the associated intersection icon on the map display.	4.5.7.1.1 The TSS Operator needs to view real time display of an intersection and typical controller front panel information status of operating mode, phases, and detectors.
3.1.7.2.3	The system shall display the following traffic signal controller information: Intersection name/number Controller type Firmware and version IP address	4.5.7.1.1 The TSS Operator needs to view real time display of an intersection and typical controller front panel information status of operating mode, phases, and detectors.
3.1.7.2.4	The system shall have the capability to display all controller outputs in real-time, including: Vehicle phases (including overlaps) Pedestrian phases Bicycle phases Signs controlled by the signal controller	4.5.7.1.1 The TSS Operator needs to view real time display of an intersection and typical controller front panel information status of operating mode, phases, and detectors.
3.1.7.2.5	The system shall have the capability to display all controller inputs in real time, including: Vehicle detector actuations Pedestrian detector actuations Bicycle detector actuations Transit signal priority Railroad preemption Emergency vehicle preemption	4.5.7.1.1 The TSS Operator needs to view real time display of an intersection and typical controller front panel information status of operating mode, phases, and detectors.
3.1.7.2.6	The system shall display the data shown on the virtual controller front panel based on a user-selected intersection.	4.5.7.1.1 The TSS Operator needs to view real time display of an intersection and typical controller front panel information status of operating mode, phases, and detectors.
3.1.8	Control
3.1.8.1	Time Management
3.1.8.1.1	The system shall receive the current time from a source: WWV radio Network Time Protocol server GPS time source Neighboring traffic signal network	4.1.1.4 The TSS operator needs to receive current time from a source to ensure time synchronization between signals.
3.1.8.1.2	The system shall re-sync the local controller time clock through a manual command.	4.1.1.5 The TSS Operator needs to coordinate traffic signals managed by another system. Note: Cross-jurisdictional heading.
3.1.8.1.2	The system shall re-sync the local controller time clock through a manual command.	4.3.7 The TSS Operator needs to keep local intersection controllers in synch with each other to operate coordinated timings and other operations that require a common time.
3.1.8.1.3	The system shall re-sync the local controller’s time clock automatically [Specify conditions for triggering automatic re-sync].	4.3.7 The TSS Operator needs to keep local intersection controllers in synch with each other to operate coordinated timings and other operations that require a common time.
3.1.8.1.3	The system shall re-sync the local controller’s time clock automatically [Specify conditions for triggering automatic re-sync].	4.3.13 The TSS Operator needs to configure when local controllers time clocks are automatically re-synced from an external time source. [Specify conditions for triggering automatic re-sync]
3.1.8.1.4	The system shall provide a time synch to each controller using: WWV radio Network Time Protocol server GPS time source Neighboring traffic signal network	4.1.1.5 The TSS Operator needs to coordinate traffic signals managed by another system. Note: Cross-jurisdictional heading.
3.1.8.1.4	The system shall provide a time synch to each controller using: WWV radio Network Time Protocol server GPS time source Neighboring traffic signal network	4.3.3 The TSS Operator needs to send and receive data from another system that would allow the two systems to be coordinated.
3.1.8.1.4	The system shall provide a time synch to each controller using: WWV radio Network Time Protocol server GPS time source Neighboring traffic signal network	4.3.7 The TSS Operator needs to keep local intersection controllers in synch with each other to operate coordinated timings and other operations that require a common time.
3.1.8.2	System Management
3.1.8.2.1	The system shall allow the traffic signals to operate in coordinated mode.	4.3.1 The TSS Operator needs to operate all signals attached to the system based on their local time of day schedule.
3.1.8.2.1	The system shall allow the traffic signals to operate in coordinated mode.	4.3.7 The TSS Operator needs to keep local intersection controllers in synch with each other to operate coordinated timings and other operations that require a common time.
3.1.8.2.2	The system shall allow the traffic signals to operate according to local control in case of communications failure.	4.1.6.1 The TSS Operator needs the local traffic signal controllers to fall back to local control without causing disruption to traffic flow, in the event of equipment, communications, or software failure.
3.1.8.2.3	The system shall allow the traffic signals to operate according to local control in case of TSS failure.	4.1.6.1 The TSS Operator needs the local traffic signal controllers to fall back to local control without causing disruption to traffic flow, in the event of equipment, communications, or software failure.
3.1.8.2.4	The system shall download manual command to the local controller to change intersection operations to free.	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.8.2.5	The system shall download manual command to the local controller to change intersection operations to flash.	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.8.2.6	The system shall download manual command to the local controller to implement a timing plan	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.8.2.7	The system shall operate manual selection of timing plans as a higher priority over all other modes of plan selection.	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.8.2.8	The system shall request confirmation from the TSS Operator before a manual command is implemented.	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.8.2.9	The system shall provide a start and end time for manual commands.	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.8.2.10	The system shall provide a duration for manual commands.	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.8.2.11	The system shall revert to time of day operation after the manual command ends.	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.8.2.12	The system shall time-stamp a log of all manual commands.	4.3.4 The TSS Operator needs to override time of day, with a manual command, at an intersection or group of intersections at any time until manually set back to scheduled operation, or expiration of a timer to cancel the override.
3.1.8.2.12	The system shall time-stamp a log of all manual commands.	4.3.8 The TSS Operator needs to send manual commands to simulate vehicle and pedestrian detection and preemption calls.
3.1.8.2.12	The system shall time-stamp a log of all manual commands.	4.5.1.3 The TSS Operator needs a time-stamped record of who accesses the system, all manual commands, and data changes made during a session.
3.1.8.2.12	The system shall time-stamp a log of all manual commands.	4.5.1.4 The TSS Operator needs a log of all software functions executed by the central system and local controllers.
3.1.8.2.13	The system shall place non-locking demand on user specified pedestrian and vehicle phases, at a user specified intersection, from the central.	4.3.8 The TSS Operator needs to send manual commands to simulate vehicle and pedestrian detection and preemption calls.
3.1.8.2.14	The system shall place a locking demand on user specified pedestrian and vehicle phases, at a user specified intersection, from the central.	4.3.8 The TSS Operator needs to send manual commands to simulate vehicle and pedestrian detection and preemption calls.
3.1.8.2.15	The system shall place a non-locking call replicating an emergency vehicle preemption call on a user specified preemption channel at a user specified intersection.	4.3.8 The TSS Operator needs to send manual commands to simulate vehicle and pedestrian detection and preemption calls.
3.1.8.2.16	The system shall receive data from another system (SPECIFY DETAILS).	4.3.8 The TSS Operator needs to send manual commands to simulate vehicle and pedestrian detection and preemption calls.
3.1.8.2.16	The system shall receive data from another system (SPECIFY DETAILS).	4.3.10 The TSS Operator needs to accommodate centrally directed emergency vehicle preemption based on an external input from the emergency system.
3.1.8.2.17	The system shall receive data from another system (SPECIFY DETAILS).	4.3.3 The TSS Operator needs to send and receive data from another system that would allow the two systems to be coordinated.
3.1.8.2.17	The system shall receive data from another system (SPECIFY DETAILS).	4.3.10 The TSS Operator needs to accommodate centrally directed emergency vehicle preemption based on an external input from the emergency system.
3.1.8.2.17	The system shall receive data from another system (SPECIFY DETAILS).	4.3.11 The TSS Operator needs to accommodate bus and light rail transit signal priority (USER SPECIFY FOR NECESSARY DETAILS).
3.1.8.2.17	The system shall receive data from another system (SPECIFY DETAILS).	4.3.12 The TSS Operator needs to accommodate rail preemption based on an external input from the railroad.
3.1.8.2.18	In the presence of external input, the system shall direct user-configured local controllers or groups to engage a user-defined emergency vehicle preemption.	4.3.10 The TSS Operator needs to accommodate centrally directed emergency vehicle preemption based on an external input from the emergency system.
3.1.8.2.19	In the presence of external input, the system shall direct user-configured local controllers or groups to engage a user-defined railroad preemption.	4.3.12 The TSS Operator needs to accommodate rail preemption based on an external input from the railroad.
3.1.8.2.20	The system shall send data to another system (SPECIFY DETAILS).	4.3.3 The TSS Operator needs to send and receive data from another system that would allow the two systems to be coordinated.
3.1.8.2.20	The system shall send data to another system (SPECIFY DETAILS).	4.3.10 The TSS Operator needs to accommodate centrally directed emergency vehicle preemption based on an external input from the emergency system.
3.1.8.2.20	The system shall send data to another system (SPECIFY DETAILS).	4.3.11 The TSS Operator needs to accommodate bus and light rail transit signal priority (USER SPECIFY FOR NECESSARY DETAILS).
3.1.8.2.20	The system shall send data to another system (SPECIFY DETAILS).	4.3.12 The TSS Operator needs to accommodate rail preemption based on an external input from the railroad.
3.1.8.2.21	The system shall turn on and turn off message signs from a manual command.	4.3.9 The TSS Operator needs to turn on and off external devices, such as message signs, by manual command, by time of day, or based on a user defined trigger (such as volume).
3.1.8.2.22	The system shall turn on and turn off message signs based on a user specified trigger (SPECIFY).	4.3.9 The TSS Operator needs to turn on and off external devices, such as message signs, by manual command, by time of day, or based on a user defined trigger (such as volume).
3.1.8.2.23	The system shall interface with external rail preemption system. (explain the external system and refer to other interfaces as appropriate)	4.3.12 The TSS Operator needs to accommodate rail preemption based on an external input from the railroad.
3.1.8.2.24	The system shall interface with external emergency vehicle preemption system. (explain the external system and refer to other interfaces as appropriate)	4.3.10 The TSS Operator needs to accommodate centrally directed emergency vehicle preemption based on an external input from the emergency system.
3.1.8.2.25	The system shall interface with external light rail transit. (explain the external system and refer to other interfaces as appropriate)	4.3.11 The TSS Operator needs to accommodate bus and light rail transit signal priority (USER SPECIFY FOR NECESSARY DETAILS).
3.1.8.2.26	The system shall interface with external bus priority system. (explain the external system and refer to other interfaces as appropriate)	4.3.11 The TSS Operator needs to accommodate bus and light rail transit signal priority (USER SPECIFY FOR NECESSARY DETAILS).
3.1.8.3	Control Modes
3.1.8.3.1	The system shall operate in the following control modes:	4.3.1 The TSS Operator needs to operate all signals attached to the system based on their local time of day schedule.
3.1.8.3.1	The system shall operate in the following control modes:	4.3.2 The TSS Operator needs to program commands for local operation based on central time of day schedule.
3.1.8.3.1	The system shall operate in the following control modes:	4.3.5 The TSS Operator needs to accommodate traffic in a network that displays predictable traffic patterns during variable periods. For example, the traffic pattern for the afternoon peak may be predictable enough to be served by a defined timing plan, but the time of day in which the condition appears may be variable from one day to the next. (Note: For operations not consistent with this need statement, consider using adaptive.) [When selecting this need, select one of the two child needs below. If you have no preference for the pattern selection method, select both, but include this text here: The Vendor may fulfill the requirements traced to either one of the child needs below.]
3.1.8.3.1	The system shall operate in the following control modes:	4.3.6 The TSS Operator needs to enable a diversion plan in case of an incident (or other activities). The TSS Operator needs to be enabled at an intersection or a group of intersections and select the appropriate operating plan based on: Time of day schedule Manual command Command from an external system (USER SPECIFY) Traffic responsive pattern selection
3.1.8.3.1.1	Time of day schedule	4.3.1 The TSS Operator needs to operate all signals attached to the system based on their local time of day schedule.
3.1.8.3.1.1	Time of day schedule	4.3.5 The TSS Operator needs to accommodate traffic in a network that displays predictable traffic patterns during variable periods. For example, the traffic pattern for the afternoon peak may be predictable enough to be served by a defined timing plan, but the time of day in which the condition appears may be variable from one day to the next. (Note: For operations not consistent with this need statement, consider using adaptive.) [When selecting this need, select one of the two child needs below. If you have no preference for the pattern selection method, select both, but include this text here: The Vendor may fulfill the requirements traced to either one of the child needs below.]
3.1.8.3.1.1	Time of day schedule	4.3.6 The TSS Operator needs to enable a diversion plan in case of an incident (or other activities). The TSS Operator needs to be enabled at an intersection or a group of intersections and select the appropriate operating plan based on: Time of day schedule Manual command Command from an external system (USER SPECIFY) Traffic responsive pattern selection
3.1.8.3.1.2	Manual control	4.3.6 The TSS Operator needs to enable a diversion plan in case of an incident (or other activities). The TSS Operator needs to be enabled at an intersection or a group of intersections and select the appropriate operating plan based on: Time of day schedule Manual command Command from an external system (USER SPECIFY) Traffic responsive pattern selection
3.1.8.3.1.3	Traffic responsive	4.3.5 The TSS Operator needs to accommodate traffic in a network that displays predictable traffic patterns during variable periods. For example, the traffic pattern for the afternoon peak may be predictable enough to be served by a defined timing plan, but the time of day in which the condition appears may be variable from one day to the next. (Note: For operations not consistent with this need statement, consider using adaptive.) [When selecting this need, select one of the two child needs below. If you have no preference for the pattern selection method, select both, but include this text here: The Vendor may fulfill the requirements traced to either one of the child needs below.]
3.1.8.3.1.3	Traffic responsive	4.3.6 The TSS Operator needs to enable a diversion plan in case of an incident (or other activities). The TSS Operator needs to be enabled at an intersection or a group of intersections and select the appropriate operating plan based on: Time of day schedule Manual command Command from an external system (USER SPECIFY) Traffic responsive pattern selection
3.1.8.3.1.4	External command	4.3.6 The TSS Operator needs to enable a diversion plan in case of an incident (or other activities). The TSS Operator needs to be enabled at an intersection or a group of intersections and select the appropriate operating plan based on: Time of day schedule Manual command Command from an external system (USER SPECIFY) Traffic responsive pattern selection
3.1.8.3.1.5	Local control mode	4.3.1 The TSS Operator needs to operate all signals attached to the system based on their local time of day schedule.
3.1.8.3.1.6	Central control mode	4.3.2 The TSS Operator needs to program commands for local operation based on central time of day schedule.
3.1.8.4	Time of Day Operation
3.1.8.4.1	The system shall implement the following user-specified actions according to a time of day schedule:	4.3.2 The TSS Operator needs to program commands for local operation based on central time of day schedule.
3.1.8.4.1	The system shall implement the following user-specified actions according to a time of day schedule:	4.3.7 The TSS Operator needs to keep local intersection controllers in synch with each other to operate coordinated timings and other operations that require a common time.
3.1.8.4.1	The system shall implement the following user-specified actions according to a time of day schedule:	4.3.9 The TSS Operator needs to turn on and off external devices, such as message signs, by manual command, by time of day, or based on a user defined trigger (such as volume).
3.1.8.4.1.1	Re-synch the local controller time clock	4.3.2 The TSS Operator needs to program commands for local operation based on central time of day schedule.
3.1.8.4.1.1	Re-synch the local controller time clock	4.3.7 The TSS Operator needs to keep local intersection controllers in synch with each other to operate coordinated timings and other operations that require a common time.
3.1.8.4.1.2	.Activate a coordination pattern	4.3.2 The TSS Operator needs to program commands for local operation based on central time of day schedule.
3.1.8.4.1.3	.Activate an external output	4.3.2 The TSS Operator needs to program commands for local operation based on central time of day schedule.
3.1.8.4.1.3	.Activate an external output	4.3.9 The TSS Operator needs to turn on and off external devices, such as message signs, by manual command, by time of day, or based on a user defined trigger (such as volume).
3.1.8.4.1.4	.Deactivate an external output	4.3.2 The TSS Operator needs to program commands for local operation based on central time of day schedule.
3.1.8.4.1.4	.Deactivate an external output	4.3.9 The TSS Operator needs to turn on and off external devices, such as message signs, by manual command, by time of day, or based on a user defined trigger (such as volume).
3.1.8.5	Traffic Responsive Operation
3.1.8.5.1	The system shall operate in traffic responsive mode when commanded: By manual TSS Operator command By time of day schedule By external input command	4.3.5 The TSS Operator needs to accommodate traffic in a network that displays predictable traffic patterns during variable periods. For example, the traffic pattern for the afternoon peak may be predictable enough to be served by a defined timing plan, but the time of day in which the condition appears may be variable from one day to the next. (Note: For operations not consistent with this need statement, consider using adaptive.) [When selecting this need, select one of the two child needs below. If you have no preference for the pattern selection method, select both, but include this text here: The Vendor may fulfill the requirements traced to either one of the child needs below.]
3.1.8.5.1	The system shall operate in traffic responsive mode when commanded: By manual TSS Operator command By time of day schedule By external input command	4.3.6 The TSS Operator needs to enable a diversion plan in case of an incident (or other activities). The TSS Operator needs to be enabled at an intersection or a group of intersections and select the appropriate operating plan based on: Time of day schedule Manual command Command from an external system (USER SPECIFY) Traffic responsive pattern selection
3.1.8.5.1.1	The TSS shall accept a user-defined assignment of intersection detectors as system detectors.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.1	The TSS shall accept a user-defined assignment of intersection detectors as system detectors.	4.3.5.2 The network is not linear and does not display pronounced inbound and outbound traffic patterns, such that the TSS Operator needs to select patterns based on which pattern most closely matches the demand conditions, without regard to inbound or outbound emphasis. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the pattern-matching selection method.)
3.1.8.5.1.2	The TSS shall accept a user-defined occupancy weighting factor for each system detector.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.2	The TSS shall accept a user-defined occupancy weighting factor for each system detector.	4.3.5.2 The network is not linear and does not display pronounced inbound and outbound traffic patterns, such that the TSS Operator needs to select patterns based on which pattern most closely matches the demand conditions, without regard to inbound or outbound emphasis. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the pattern-matching selection method.)
3.1.8.5.1.3	The TSS shall accept a user-defined traffic-responsive control period.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.3	The TSS shall accept a user-defined traffic-responsive control period.	4.3.5.2 The network is not linear and does not display pronounced inbound and outbound traffic patterns, such that the TSS Operator needs to select patterns based on which pattern most closely matches the demand conditions, without regard to inbound or outbound emphasis. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the pattern-matching selection method.)
3.1.8.5.1.4	The TSS shall sum volume plus weighted occupancy for each system detector over the duration of the control period (volume comprises distinct detection of on and off events, and weighted occupancy is the percentage of time the detector is occupied by a vehicle multiplied by the occupancy weighting factor)	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.4	The TSS shall sum volume plus weighted occupancy for each system detector over the duration of the control period (volume comprises distinct detection of on and off events, and weighted occupancy is the percentage of time the detector is occupied by a vehicle multiplied by the occupancy weighting factor)	4.3.5.2 The network is not linear and does not display pronounced inbound and outbound traffic patterns, such that the TSS Operator needs to select patterns based on which pattern most closely matches the demand conditions, without regard to inbound or outbound emphasis. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the pattern-matching selection method.)
3.1.8.5.1.5	The TSS shall accept a user-defined detector weighting factor to be applied to each system detector volume plus weighted occupancy.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.5	The TSS shall accept a user-defined detector weighting factor to be applied to each system detector volume plus weighted occupancy.	4.3.5.2 The network is not linear and does not display pronounced inbound and outbound traffic patterns, such that the TSS Operator needs to select patterns based on which pattern most closely matches the demand conditions, without regard to inbound or outbound emphasis. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the pattern-matching selection method.)
3.1.8.5.1.6	The TSS shall multiply the volume plus weighted occupancy by the detector weighting factor.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.6	The TSS shall multiply the volume plus weighted occupancy by the detector weighting factor.	4.3.5.2 The network is not linear and does not display pronounced inbound and outbound traffic patterns, such that the TSS Operator needs to select patterns based on which pattern most closely matches the demand conditions, without regard to inbound or outbound emphasis. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the pattern-matching selection method.)
3.1.8.5.1.7	The TSS shall select coordination patterns based on threshold levels (this is an alternative to the pattern recognition method).	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.7.1	The TSS shall accept a user-defined selection of system detectors designated as inbound detectors.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.7.2	The TSS shall accept a user-defined selection of system detectors designated as outbound detectors.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.7.3	The TSS shall total the weighted volume plus weighted occupancy for inbound detectors within each intersection group over the control period.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.7.4	The TSS shall total the weighted volume plus weighted occupancy for outbound detectors within each intersection group over the control period.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.7.5	The TSS shall accept user-defined thresholds for inbound pattern selection.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.7.6	The TSS shall accept user-defined thresholds for outbound pattern selection.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.7.7	The TSS shall accept different thresholds for increasing weighted volume plus weighted occupancy totals than for decreasing weighted volume plus weighted occupancy totals (this provides the ability to incorporate hysteresis).	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.7.8	The TSS shall accept user-defined coordination pattern designations for each level of total weighted volume plus weighted occupancy bounded by thresholds.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.7.9	The TSS shall compare the weighted volume plus weighted occupancy totals against the defined thresholds.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.7.10	The TSS shall engage the inbound or outbound coordination pattern defined for the weighted volume plus weighted occupancy totals.	4.3.5.1 The network is linear and displays inbound and outbound traffic patterns such that the TSS Operator needs to select patterns using an inbound and outbound threshold selection scheme. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the threshold level selection method.)
3.1.8.5.1.8	The TSS shall select coordination patterns based on pattern recognition (this is an alternative to the threshold method).	4.3.5.2 The network is not linear and does not display pronounced inbound and outbound traffic patterns, such that the TSS Operator needs to select patterns based on which pattern most closely matches the demand conditions, without regard to inbound or outbound emphasis. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the pattern-matching selection method.)
3.1.8.5.1.8.1	The TSS shall accept a table of coordination pattern designations coupled to user-defined “signature” total weighted volume plus weighted occupancy values (totals over the duration of the control period).	4.3.5.2 The network is not linear and does not display pronounced inbound and outbound traffic patterns, such that the TSS Operator needs to select patterns based on which pattern most closely matches the demand conditions, without regard to inbound or outbound emphasis. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the pattern-matching selection method.)
3.1.8.5.1.8.2	The TSS shall compare the total weighted volume plus weighted occupancy for each intersection group over the duration of the control period against the user-defined “signature” values.	4.3.5.2 The network is not linear and does not display pronounced inbound and outbound traffic patterns, such that the TSS Operator needs to select patterns based on which pattern most closely matches the demand conditions, without regard to inbound or outbound emphasis. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the pattern-matching selection method.)
3.1.8.5.1.8.3	The TSS shall engage the coordination pattern with the signature value that comes closest to the total weighted volume plus weighted occupancy for the intersection group.	4.3.5.2 The network is not linear and does not display pronounced inbound and outbound traffic patterns, such that the TSS Operator needs to select patterns based on which pattern most closely matches the demand conditions, without regard to inbound or outbound emphasis. (This need is appropriate for agencies that have already decided to use traffic-responsive selection of coordination patterns using the pattern-matching selection method.)
3.1.9	Adaptive Operations
3.1.9.1	General
3.1.9.1.1	Mode of Operation
3.1.9.1.1.1	The ASCT shall operate non-adaptively during the presence of a defined condition.	4.4.7 Non-Adaptive Situations
3.1.9.1.1.1	The ASCT shall operate non-adaptively during the presence of a defined condition.	4.4.7.1 The TSS Operator needs to detect traffic conditions during which adaptive control is not the preferred operation, and implement some pre-defined operation while that condition is present.
3.1.9.1.1.2	The ASCT shall operate non-adaptively when adaptive control equipment fails.	4.1.6.1 The TSS Operator needs the local traffic signal controllers to fall back to local control without causing disruption to traffic flow, in the event of equipment, communications, or software failure.
3.1.9.1.1.2	The ASCT shall operate non-adaptively when adaptive control equipment fails.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.9.1.1.2.1	The ASCT shall operate non-adaptively when a user-specified detector fails.	4.1.6.1 The TSS Operator needs the local traffic signal controllers to fall back to local control without causing disruption to traffic flow, in the event of equipment, communications, or software failure.
3.1.9.1.1.2.1	The ASCT shall operate non-adaptively when a user-specified detector fails.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.9.1.1.2.2	The ASCT shall operate non-adaptively when the number of failed detectors connected to a signal controller exceeds a user-defined value.	4.1.6.1 The TSS Operator needs the local traffic signal controllers to fall back to local control without causing disruption to traffic flow, in the event of equipment, communications, or software failure.
3.1.9.1.1.2.2	The ASCT shall operate non-adaptively when the number of failed detectors connected to a signal controller exceeds a user-defined value.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.9.1.1.2.3	The ASCT shall operate non-adaptively when the number of failed detectors in a group exceeds a user-defined value.	4.1.6.1 The TSS Operator needs the local traffic signal controllers to fall back to local control without causing disruption to traffic flow, in the event of equipment, communications, or software failure.
3.1.9.1.1.2.3	The ASCT shall operate non-adaptively when the number of failed detectors in a group exceeds a user-defined value.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.9.1.1.2.4	The ASCT shall operate non-adaptively when a user-defined communications link fails.	4.1.6.1 The TSS Operator needs the local traffic signal controllers to fall back to local control without causing disruption to traffic flow, in the event of equipment, communications, or software failure.
3.1.9.1.1.2.4	The ASCT shall operate non-adaptively when a user-defined communications link fails.	4.1.7.1 The TSS Operator needs to fall back to non-adaptive operation as defined in section 4.3, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure. Non-adaptive operation is defined in the TSS needs and requirements.
3.1.9.1.1.3	The ASCT shall operate non-adaptively when a user manually commands the ASCT to cease adaptively controlling a group of signals.	4.4.7.3 The TSS Operator needs to over-ride adaptive operation.
3.1.9.1.1.4	The ASCT shall operate non-adaptively when a user manually commands the ASCT to cease adaptive operation.	4.4.7.3 The TSS Operator needs to over-ride adaptive operation.
3.1.9.1.1.5	The ASCT shall operate non-adaptively in accordance with a user-defined time-of-day schedule.	4.4.7.2 The TSS Operator needs to schedule pre-determined operation by time of day.
3.1.9.1.1.5	The ASCT shall operate non-adaptively in accordance with a user-defined time-of-day schedule.	4.4.7.3 The TSS Operator needs to over-ride adaptive operation.
3.1.9.1.1.6	The ASCT shall operate non-adaptively when commanded by an external system process.	4.9.6 The TSS Operator needs to react to commands issued by (specify an external control or decision support system, such as an ICM system or another signal system).
3.1.9.1.1.7	The ASCT shall alter the adaptive operation to achieve required objectives in user-specified conditions. (The required objectives are specified in Needs Statement 4.1.1)	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.7	The ASCT shall alter the adaptive operation to achieve required objectives in user-specified conditions. (The required objectives are specified in Needs Statement 4.1.1)	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.7	The ASCT shall alter the adaptive operation to achieve required objectives in user-specified conditions. (The required objectives are specified in Needs Statement 4.1.1)	4.4.1.3 The TSS Operator needs to change the operational strategy (for example, from smooth flow to maximizing throughput or managing queues) based on changing traffic conditions.
3.1.9.1.1.7.1	When current measured traffic conditions meet user-specified criteria, the ASCT shall alter the state of the signal controllers, maximizing the throughput of the coordinated route.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.7.1	When current measured traffic conditions meet user-specified criteria, the ASCT shall alter the state of the signal controllers, maximizing the throughput of the coordinated route.	4.4.1.3 The TSS Operator needs to change the operational strategy (for example, from smooth flow to maximizing throughput or managing queues) based on changing traffic conditions.
3.1.9.1.1.7.2	When current measured traffic conditions meet user-specified criteria, the ASCT shall alter the state of signal controllers, preventing queues from exceeding the storage capacity at user-specified locations.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.7.2	When current measured traffic conditions meet user-specified criteria, the ASCT shall alter the state of signal controllers, preventing queues from exceeding the storage capacity at user-specified locations.	4.4.1.3 The TSS Operator needs to change the operational strategy (for example, from smooth flow to maximizing throughput or managing queues) based on changing traffic conditions.
3.1.9.1.1.7.3	When current measured traffic conditions meet user-specified criteria, the ASCT shall alter the state of signal controllers providing equitable distribution of green times.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.7.3	When current measured traffic conditions meet user-specified criteria, the ASCT shall alter the state of signal controllers providing equitable distribution of green times.	4.4.1.3 The TSS Operator needs to change the operational strategy (for example, from smooth flow to maximizing throughput or managing queues) based on changing traffic conditions.
3.1.9.1.1.7.4	When current measured traffic conditions meet user-defined criteria, the ASCT shall alter the state of signal controllers providing two-way progression on a coordinated route.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.7.4	When current measured traffic conditions meet user-defined criteria, the ASCT shall alter the state of signal controllers providing two-way progression on a coordinated route.	4.4.1.3 The TSS Operator needs to change the operational strategy (for example, from smooth flow to maximizing throughput or managing queues) based on changing traffic conditions.
3.1.9.1.1.8	The ASCT shall provide maximum and minimum phase times.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.8	The ASCT shall provide maximum and minimum phase times.	4.4.1.1.6 At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).
3.1.9.1.1.8.1	The ASCT shall provide a user-specified maximum value for each phase at each signal controller.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.8.1	The ASCT shall provide a user-specified maximum value for each phase at each signal controller.	4.4.1.1.6 At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).
3.1.9.1.1.8.1.1	The ASCT shall not provide a phase length longer that the maximum value.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.8.1.1	The ASCT shall not provide a phase length longer that the maximum value.	4.4.1.1.6 At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).
3.1.9.1.1.8.2	The ASCT shall provide a user-specified minimum value for each phase at each signal controller.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.8.2	The ASCT shall provide a user-specified minimum value for each phase at each signal controller.	4.4.1.1.6 At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).
3.1.9.1.1.8.2.1	The ASCT shall not provide a phase length shorter than the minimum value.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.8.2.1	The ASCT shall not provide a phase length shorter than the minimum value.	4.4.1.1.6 At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).
3.1.9.1.1.9	The ASCT shall detect repeated phases that do not serve all waiting vehicles. (These phase failures may be inferred, such as by detecting repeated max-out.)	4.4.1.4 The TSS Operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The TSS Operator in this case is trying to prevent a routine queue from forming where it will block another movement in the cycle unnecessarily. For example, the TSS Operator may need to prevent a queue resulting from the trailing end of the through green from blocking the storage needed by an entering side-street left turn in the subsequent phase. An overall queue management strategy, particularly when congestion is present, is covered under 4.4.1.5.
3.1.9.1.1.9.1	The ASCT shall alter operations, to minimize repeated phase failures.	4.4.1.4 The TSS Operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The TSS Operator in this case is trying to prevent a routine queue from forming where it will block another movement in the cycle unnecessarily. For example, the TSS Operator may need to prevent a queue resulting from the trailing end of the through green from blocking the storage needed by an entering side-street left turn in the subsequent phase. An overall queue management strategy, particularly when congestion is present, is covered under 4.4.1.5.
3.1.9.1.1.10	The ASCT shall determine the order of phases at a user-specified intersection. (The calculation will be based on the optimization function.)	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.10	The ASCT shall determine the order of phases at a user-specified intersection. (The calculation will be based on the optimization function.)	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.10	The ASCT shall determine the order of phases at a user-specified intersection. (The calculation will be based on the optimization function.)	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.1.11	The ASCT shall provide coordination along a route.	4.4.1.8 The TSS Operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.
3.1.9.1.1.11.1	The ASCT shall coordinate along a user-defined route.	4.4.1.8 The TSS Operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.
3.1.9.1.1.11.2	The ASCT shall determine the coordinated route based on traffic conditions.	4.4.1.8 The TSS Operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.
3.1.9.1.1.11.3	The ASCT shall determine the coordinated route based on a user-defined schedule.	4.4.1.8 The TSS Operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.
3.1.9.1.1.11.4	The ASCT shall store XX user-defined coordination routes.	4.4.1.8 The TSS Operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.
3.1.9.1.1.11.4.1	The ASCT shall implement a stored coordinated route by operator command.	4.4.1.8 The TSS Operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.
3.1.9.1.1.11.4.2	The ASCT shall implement a stored coordinated route based on traffic conditions.	4.4.1.8 The TSS Operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.
3.1.9.1.1.11.4.3	The ASCT shall implement a stored coordinated route based on a user-defined schedule.	4.4.1.8 The TSS Operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.
3.1.9.1.1.12	The ASCT shall not prevent the use of phase timings in the local controller set by agency policy.	4.4.1.9 The TSS Operator needs to set signal timing parameters (such as minimum green, maximum green and extension time) to comply with agency policies.
3.1.9.1.2	Allowable Phases
3.1.9.1.2.1	The ASCT shall not prevent protected/permissive left turn phase operation.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.9.1.2.1	The ASCT shall not prevent protected/permissive left turn phase operation.	4.4.9.1.14 Protected/permissive phasing and alternate left turn phase sequences.
3.1.9.1.2.2	The ASCT shall not prevent the protected left turn phase to lead or lag the opposing through phase based upon user-specified conditions.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.9.1.2.2	The ASCT shall not prevent the protected left turn phase to lead or lag the opposing through phase based upon user-specified conditions.	4.4.9.1.14 Protected/permissive phasing and alternate left turn phase sequences.
3.1.9.1.2.3	The ASCT shall prevent skipping a user-specified phase when the user-specified phase sequence is operating.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.9.1.2.3	The ASCT shall prevent skipping a user-specified phase when the user-specified phase sequence is operating.	4.4.9.1.6 Prevent one or more phases being skipped under certain traffic conditions or signal states.
3.1.9.1.2.4	The ASCT shall prevent skipping a user-specified phase based on the state of a user-specified external input.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.9.1.2.4	The ASCT shall prevent skipping a user-specified phase based on the state of a user-specified external input.	4.4.9.1.6 Prevent one or more phases being skipped under certain traffic conditions or signal states.
3.1.9.1.2.4	The ASCT shall prevent skipping a user-specified phase based on the state of a user-specified external input.	4.9.6 The TSS Operator needs to react to commands issued by (specify an external control or decision support system, such as an ICM system or another signal system).
3.1.9.1.2.5	The ASCT shall prevent skipping a user-specified phase according to a time of day schedule.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.9.1.2.5	The ASCT shall prevent skipping a user-specified phase according to a time of day schedule.	4.4.9.1.6 Prevent one or more phases being skipped under certain traffic conditions or signal states.
3.1.9.1.2.6	The ASCT shall omit a user-specified phase when the cycle length is below a user-specified value.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.9.1.2.6	The ASCT shall omit a user-specified phase when the cycle length is below a user-specified value.	4.4.9.1.5 Allow one or more phases to be omitted (disabled) under certain traffic conditions or signal states.
3.1.9.1.2.7	The ASCT shall omit a user-specified phase based on measured traffic conditions.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.9.1.2.7	The ASCT shall omit a user-specified phase based on measured traffic conditions.	4.4.9.1.5 Allow one or more phases to be omitted (disabled) under certain traffic conditions or signal states.
3.1.9.1.2.8	The ASCT shall omit a user-specified phase based on the state of a user-specified external input.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.9.1.2.8	The ASCT shall omit a user-specified phase based on the state of a user-specified external input.	4.4.9.1.5 Allow one or more phases to be omitted (disabled) under certain traffic conditions or signal states.
3.1.9.1.2.8	The ASCT shall omit a user-specified phase based on the state of a user-specified external input.	4.9.6 The TSS Operator needs to react to commands issued by (specify an external control or decision support system, such as an ICM system or another signal system).
3.1.9.1.2.9	The ASCT shall omit a user-specified phase according to a time of day schedule	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.9.1.2.9	The ASCT shall omit a user-specified phase according to a time of day schedule	4.4.9.1.5 Allow one or more phases to be omitted (disabled) under certain traffic conditions or signal states.
3.1.9.1.2.10	The ASCT shall assign unused time from a preceding phase that terminates early to a user-specified phase as follows: next phase; next coordinated phase;user-specified phase.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.9.1.2.10	The ASCT shall assign unused time from a preceding phase that terminates early to a user-specified phase as follows: next phase; next coordinated phase;user-specified phase.	4.4.9.1.10 Allow the operator to specify which phase receives unused time from a preceding phase
3.1.9.1.2.11	The ASCT shall assign unused time from a preceding phase that is skipped to a user-specified phase as follows: previous phase; next phase; next coordinated phase; user-specified phase.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.9.1.2.11	The ASCT shall assign unused time from a preceding phase that is skipped to a user-specified phase as follows: previous phase; next phase; next coordinated phase; user-specified phase.	4.4.9.1.10 Allow the operator to specify which phase receives unused time from a preceding phase
3.1.9.1.2.12	The ASCT shall not alter the order of phases at a user-specified intersection.	4.4.1.7 The TSS Operator needs to fix the sequence of phases at any specified location. For example, the operator may need to fix the phase order at a diamond interchange.
3.1.9.1.3	Oversaturation
3.1.9.1.3.1	The ASCT shall detect the presence of queues at pre-configured locations.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.1	The ASCT shall detect the presence of queues at pre-configured locations.	4.4.1.1.5 Manage the locations of queues within the network Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.1	The ASCT shall detect the presence of queues at pre-configured locations.	4.4.1.4 The TSS Operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The TSS Operator in this case is trying to prevent a routine queue from forming where it will block another movement in the cycle unnecessarily. For example, the TSS Operator may need to prevent a queue resulting from the trailing end of the through green from blocking the storage needed by an entering side-street left turn in the subsequent phase. An overall queue management strategy, particularly when congestion is present, is covered under 4.4.1.5.
3.1.9.1.3.1	The ASCT shall detect the presence of queues at pre-configured locations.	4.4.4.1 The TSS Operator needs to detect queues from outside the system and modify the ASCT operation to accommodate the queuing.
3.1.9.1.3.1	The ASCT shall detect the presence of queues at pre-configured locations.	4.4.4.2 The TSS Operator needs to detect queues within the system's boundaries and modify the ASCT operation to accommodate the queuing.
3.1.9.1.3.1	The ASCT shall detect the presence of queues at pre-configured locations.	4.4.4.3 The TSS Operator needs to detect queues propagating outside its boundaries from within the ASCT boundaries, and modify its operation to accommodate the queuing.
3.1.9.1.3.1	The ASCT shall detect the presence of queues at pre-configured locations.	4.4.4.4 The TSS Operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.
3.1.9.1.3.1	The ASCT shall detect the presence of queues at pre-configured locations.	4.4.4.5 The TSS Operator needs to prevent queues forming at user-specified locations.
3.1.9.1.3.2	When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.2	When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.	4.4.1.1.5 Manage the locations of queues within the network Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.2	When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.	4.4.1.4 The TSS Operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The TSS Operator in this case is trying to prevent a routine queue from forming where it will block another movement in the cycle unnecessarily. For example, the TSS Operator may need to prevent a queue resulting from the trailing end of the through green from blocking the storage needed by an entering side-street left turn in the subsequent phase. An overall queue management strategy, particularly when congestion is present, is covered under 4.4.1.5.
3.1.9.1.3.2	When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.	4.4.4.1 The TSS Operator needs to detect queues from outside the system and modify the ASCT operation to accommodate the queuing.
3.1.9.1.3.2	When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.	4.4.4.2 The TSS Operator needs to detect queues within the system's boundaries and modify the ASCT operation to accommodate the queuing.
3.1.9.1.3.2	When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.	4.4.4.3 The TSS Operator needs to detect queues propagating outside its boundaries from within the ASCT boundaries, and modify its operation to accommodate the queuing.
3.1.9.1.3.2	When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.	4.4.4.4 The TSS Operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.
3.1.9.1.3.2	When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.	4.4.4.5 The TSS Operator needs to prevent queues forming at user-specified locations.
3.1.9.1.3.3	When queues are detected at user-specified locations, the ASCT shall execute user-specified adaptive operation strategy.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.3	When queues are detected at user-specified locations, the ASCT shall execute user-specified adaptive operation strategy.	4.4.1.1.5 Manage the locations of queues within the network Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.3	When queues are detected at user-specified locations, the ASCT shall execute user-specified adaptive operation strategy.	4.4.1.4 The TSS Operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The TSS Operator in this case is trying to prevent a routine queue from forming where it will block another movement in the cycle unnecessarily. For example, the TSS Operator may need to prevent a queue resulting from the trailing end of the through green from blocking the storage needed by an entering side-street left turn in the subsequent phase. An overall queue management strategy, particularly when congestion is present, is covered under 4.4.1.5.
3.1.9.1.3.3	When queues are detected at user-specified locations, the ASCT shall execute user-specified adaptive operation strategy.	4.4.4.1 The TSS Operator needs to detect queues from outside the system and modify the ASCT operation to accommodate the queuing.
3.1.9.1.3.3	When queues are detected at user-specified locations, the ASCT shall execute user-specified adaptive operation strategy.	4.4.4.2 The TSS Operator needs to detect queues within the system's boundaries and modify the ASCT operation to accommodate the queuing.
3.1.9.1.3.3	When queues are detected at user-specified locations, the ASCT shall execute user-specified adaptive operation strategy.	4.4.4.3 The TSS Operator needs to detect queues propagating outside its boundaries from within the ASCT boundaries, and modify its operation to accommodate the queuing.
3.1.9.1.3.3	When queues are detected at user-specified locations, the ASCT shall execute user-specified adaptive operation strategy.	4.4.4.4 The TSS Operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.
3.1.9.1.3.3	When queues are detected at user-specified locations, the ASCT shall execute user-specified adaptive operation strategy.	4.4.4.5 The TSS Operator needs to prevent queues forming at user-specified locations.
3.1.9.1.3.4	When queues are detected at user-specified locations, the ASCT shall omit a user-specified phase at a user-specified signal controller.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.4	When queues are detected at user-specified locations, the ASCT shall omit a user-specified phase at a user-specified signal controller.	4.4.1.1.5 Manage the locations of queues within the network Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.4	When queues are detected at user-specified locations, the ASCT shall omit a user-specified phase at a user-specified signal controller.	4.4.1.4 The TSS Operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The TSS Operator in this case is trying to prevent a routine queue from forming where it will block another movement in the cycle unnecessarily. For example, the TSS Operator may need to prevent a queue resulting from the trailing end of the through green from blocking the storage needed by an entering side-street left turn in the subsequent phase. An overall queue management strategy, particularly when congestion is present, is covered under 4.4.1.5.
3.1.9.1.3.4	When queues are detected at user-specified locations, the ASCT shall omit a user-specified phase at a user-specified signal controller.	4.4.4.4 The TSS Operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.
3.1.9.1.3.4	When queues are detected at user-specified locations, the ASCT shall omit a user-specified phase at a user-specified signal controller.	4.4.4.5 The TSS Operator needs to prevent queues forming at user-specified locations.
3.1.9.1.3.5	The ASCT shall meter traffic into user-specified bottlenecks by storing queues at user-specified locations.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.5	The ASCT shall meter traffic into user-specified bottlenecks by storing queues at user-specified locations.	4.4.1.1.5 Manage the locations of queues within the network Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.5	The ASCT shall meter traffic into user-specified bottlenecks by storing queues at user-specified locations.	4.4.4.4 The TSS Operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.
3.1.9.1.3.5	The ASCT shall meter traffic into user-specified bottlenecks by storing queues at user-specified locations.	4.4.4.5 The TSS Operator needs to prevent queues forming at user-specified locations.
3.1.9.1.3.6	The ASCT shall store queues at user-specified locations.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.6	The ASCT shall store queues at user-specified locations.	4.4.1.1.5 Manage the locations of queues within the network Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.1.3.6	The ASCT shall store queues at user-specified locations.	4.4.4.4 The TSS Operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.
3.1.9.1.3.6	The ASCT shall store queues at user-specified locations.	4.4.4.5 The TSS Operator needs to prevent queues forming at user-specified locations.
3.1.9.1.3.7	The ASCT shall maintain capacity flow through user-specified bottlenecks.	4.4.4.4 The TSS Operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.
3.1.9.1.3.7	The ASCT shall maintain capacity flow through user-specified bottlenecks.	4.4.4.5 The TSS Operator needs to prevent queues forming at user-specified locations.
3.1.9.1.3.8	When queues are detected at user-specified locations, the ASCT shall limit the cycle length of the group to a user-specified value.	4.4.1.1.5 Manage the locations of queues within the network Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2	Sequence-based Adaptive Coordination
3.1.9.2.1	Use this section if sequence-based adaptive coordination is likely to provide acceptable operation in your situation.
3.1.9.2.2	(Sequence-based only) The ASCT shall select cycle length based on a time of day schedule.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.2	(Sequence-based only) The ASCT shall select cycle length based on a time of day schedule.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.2	(Sequence-based only) The ASCT shall select cycle length based on a time of day schedule.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.2	(Sequence-based only) The ASCT shall select cycle length based on a time of day schedule.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.3	(Sequence-based only) The ASCT shall calculate phase lengths for all phases at each signal controller to suit the current coordination strategy.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.3	(Sequence-based only) The ASCT shall calculate phase lengths for all phases at each signal controller to suit the current coordination strategy.	4.4.1.1.5 Manage the locations of queues within the network Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.3	(Sequence-based only) The ASCT shall calculate phase lengths for all phases at each signal controller to suit the current coordination strategy.	4.4.1.4 The TSS Operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The TSS Operator in this case is trying to prevent a routine queue from forming where it will block another movement in the cycle unnecessarily. For example, the TSS Operator may need to prevent a queue resulting from the trailing end of the through green from blocking the storage needed by an entering side-street left turn in the subsequent phase. An overall queue management strategy, particularly when congestion is present, is covered under 4.4.1.5.
3.1.9.2.4	(Sequence-based only) The ASCT shall calculate offsets to suit the current coordination strategy for the user-specified reference point for each signal controller along a coordinated route within a group.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.4	(Sequence-based only) The ASCT shall calculate offsets to suit the current coordination strategy for the user-specified reference point for each signal controller along a coordinated route within a group.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.4	(Sequence-based only) The ASCT shall calculate offsets to suit the current coordination strategy for the user-specified reference point for each signal controller along a coordinated route within a group.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.4.1	(Sequence-based only) The ASCT shall apply offsets for the user-specified reference point of each signal controller along a coordinated route.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.4.1	(Sequence-based only) The ASCT shall apply offsets for the user-specified reference point of each signal controller along a coordinated route.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.4.1	(Sequence-based only) The ASCT shall apply offsets for the user-specified reference point of each signal controller along a coordinated route.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5	(Sequence-based only) The ASCT shall calculate a cycle length for each cycle based on its optimization objectives (as required elsewhere, e.g., progression, queue management, equitable distribution of green).	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5	(Sequence-based only) The ASCT shall calculate a cycle length for each cycle based on its optimization objectives (as required elsewhere, e.g., progression, queue management, equitable distribution of green).	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5	(Sequence-based only) The ASCT shall calculate a cycle length for each cycle based on its optimization objectives (as required elsewhere, e.g., progression, queue management, equitable distribution of green).	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5	(Sequence-based only) The ASCT shall calculate a cycle length for each cycle based on its optimization objectives (as required elsewhere, e.g., progression, queue management, equitable distribution of green).	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.1	(Sequence-based only) The ASCT shall limit cycle lengths to user-specified values.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.1	(Sequence-based only) The ASCT shall limit cycle lengths to user-specified values.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.1	(Sequence-based only) The ASCT shall limit cycle lengths to user-specified values.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.1	(Sequence-based only) The ASCT shall limit cycle lengths to user-specified values.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.2	(Sequence-based only) The ASCT shall limit cycle lengths to a user-specified range.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.2	(Sequence-based only) The ASCT shall limit cycle lengths to a user-specified range.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.2	(Sequence-based only) The ASCT shall limit cycle lengths to a user-specified range.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.2	(Sequence-based only) The ASCT shall limit cycle lengths to a user-specified range.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.3	(Sequence-based only) The ASCT shall calculate optimum cycle length according to the user-specified coordination strategy.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.3	(Sequence-based only) The ASCT shall calculate optimum cycle length according to the user-specified coordination strategy.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.3	(Sequence-based only) The ASCT shall calculate optimum cycle length according to the user-specified coordination strategy.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.3	(Sequence-based only) The ASCT shall calculate optimum cycle length according to the user-specified coordination strategy.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4	(Sequence-based only) The ASCT shall limit changes in cycle length to not exceed a user-specified value.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4	(Sequence-based only) The ASCT shall limit changes in cycle length to not exceed a user-specified value.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4	(Sequence-based only) The ASCT shall limit changes in cycle length to not exceed a user-specified value.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4	(Sequence-based only) The ASCT shall limit changes in cycle length to not exceed a user-specified value.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1	(Sequence-based only) The ASCT shall increase the limit for the following XX cycles based on a change in conditions.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1	(Sequence-based only) The ASCT shall increase the limit for the following XX cycles based on a change in conditions.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1	(Sequence-based only) The ASCT shall increase the limit for the following XX cycles based on a change in conditions.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1	(Sequence-based only) The ASCT shall increase the limit for the following XX cycles based on a change in conditions.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1.1	(Sequence-based only) The change in conditions shall be defined by XX successive adaptive increases in cycle length at the maximum rate.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1.1	(Sequence-based only) The change in conditions shall be defined by XX successive adaptive increases in cycle length at the maximum rate.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1.1	(Sequence-based only) The change in conditions shall be defined by XX successive adaptive increases in cycle length at the maximum rate.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1.1	(Sequence-based only) The change in conditions shall be defined by XX successive adaptive increases in cycle length at the maximum rate.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1.2	(Sequence-based only) The increased limit shall be user-defined.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1.2	(Sequence-based only) The increased limit shall be user-defined.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1.2	(Sequence-based only) The increased limit shall be user-defined.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.4.1.2	(Sequence-based only) The increased limit shall be user-defined.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.2.5.5	(Sequence-based only) The ASCT shall adjust offsets to minimize the chance of stopping vehicles approaching a signal that have been served by a user-specified phase at an upstream signal.	4.4.1.5 The TSS Operator needs to minimize the chance that a queue forms at a specified location. Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.5 group when phase-based systems are allowed (phase-based systems do not explicitly calculate cycle, offset and split at all intersections). (Select requirements from two or all three groups when the vendor is given the choice of supplying the type of adaptive operation.)
3.1.9.3	Non-sequence-based adaptive coordination
3.1.9.3.1	Use this section if non-sequence-based adaptive coordination is likely to provide acceptable operation in your situation.
3.1.9.3.2	(Non-sequence-based only) The ASCT shall calculate the appropriate state of the signal to suit the current coordination strategy at the critical signal controller. (A critical signal controller is defined by the user.)	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.2	(Non-sequence-based only) The ASCT shall calculate the appropriate state of the signal to suit the current coordination strategy at the critical signal controller. (A critical signal controller is defined by the user.)	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.2	(Non-sequence-based only) The ASCT shall calculate the appropriate state of the signal to suit the current coordination strategy at the critical signal controller. (A critical signal controller is defined by the user.)	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.2	(Non-sequence-based only) The ASCT shall calculate the appropriate state of the signal to suit the current coordination strategy at the critical signal controller. (A critical signal controller is defined by the user.)	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.3	(Non-sequence-based only) At non-critical intersections within a group, the ASCT shall calculate the time at which a user-specified phase shall be green, relative to a reference point at the critical intersection, to suit the current coordination strategy.	4.4.1.1. Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.3	(Non-sequence-based only) At non-critical intersections within a group, the ASCT shall calculate the time at which a user-specified phase shall be green, relative to a reference point at the critical intersection, to suit the current coordination strategy.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.3	(Non-sequence-based only) At non-critical intersections within a group, the ASCT shall calculate the time at which a user-specified phase shall be green, relative to a reference point at the critical intersection, to suit the current coordination strategy.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.3	(Non-sequence-based only) At non-critical intersections within a group, the ASCT shall calculate the time at which a user-specified phase shall be green, relative to a reference point at the critical intersection, to suit the current coordination strategy.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.4	(Non-sequence-based only) When demand is present, the ASCT shall implement a user-specified maximum time between successive displays of each phase at each intersection.	4.4.1.1.1 Maximize the throughput on coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.4	(Non-sequence-based only) When demand is present, the ASCT shall implement a user-specified maximum time between successive displays of each phase at each intersection.	4.4.1.1.2 Provide smooth flow along coordinated routes Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.4	(Non-sequence-based only) When demand is present, the ASCT shall implement a user-specified maximum time between successive displays of each phase at each intersection.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.4	(Non-sequence-based only) When demand is present, the ASCT shall implement a user-specified maximum time between successive displays of each phase at each intersection.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.3.5	(Non-sequence-based only) The ASCT shall adjust signal timing so that vehicles approaching a signal that have been served during a user-specified phase at an upstream signal do not stop.	4.4.1.5 The TSS Operator needs to minimize the chance that a queue forms at a specified location. Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.5 group when phase-based systems are allowed (phase-based systems do not explicitly calculate cycle, offset and split at all intersections). (Select requirements from two or all three groups when the vendor is given the choice of supplying the type of adaptive operation.)
3.1.9.4	Single intersection adaptive operation
3.1.9.4.1	Use this section if non-coordinated adaptive coordination is likely to provide acceptable operation in your situation.
3.1.9.4.2	The ASCT shall calculate a cycle length of a single intersection, based on current measured traffic conditions. (The calculation is based on the optimization objectives.)	4.4.1.1.6 At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).
3.1.9.4.3	The ASCT shall calculate optimum phase lengths, based on current measured traffic conditions. (The calculation is based on the optimization objectives.)	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.4.3	The ASCT shall calculate optimum phase lengths, based on current measured traffic conditions. (The calculation is based on the optimization objectives.)	4.4.1.1.6 At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).
3.1.9.4.3.1	The ASCT shall limit the difference between the length of a given phase and the length of the same phase during its next service to a user-specified value.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.4.3.1	The ASCT shall limit the difference between the length of a given phase and the length of the same phase during its next service to a user-specified value.	4.4.1.1.6 At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).
3.1.9.4.3.2	When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.	4.4.1.1.3 Distribute phase times in an equitable fashion Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.9.4.3.2	When queues are detected at user-specified locations, the ASCT shall execute user-specified timing plan/operational mode.	4.4.1.1.6 At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).
3.1.9.4.4	The ASCT shall calculate phase order, based on current measured traffic conditions. (The calculation is based on the optimization objectives.)	4.4.1.1.6 At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).
3.1.9.5	Phase-based adaptive coordination
3.1.9.5.1	Use this section if phase-based adaptive coordination is likely to provide acceptable operation in your situation.
3.1.9.5.2	(Phase-based only) The ASCT shall alter the state of the signal controller for all phases at the user-specified intersection.	4.4.1.2 The system operator needs to manage the coordination in small groups of signals to link phase service at some intersections with phase service at adjacent intersections. Note: Phase-based systems do not explicitly calculate cycle, offset and split at all intersections.
3.1.9.5.3	(Phase-based only) The ASCT shall calculate the time at which a user-specified phase shall be green at an intersection.	4.4.1.2 The system operator needs to manage the coordination in small groups of signals to link phase service at some intersections with phase service at adjacent intersections. Note: Phase-based systems do not explicitly calculate cycle, offset and split at all intersections.
3.1.9.5.4	(Phase-based only) When demand is present, the ASCT shall implement a user-specified maximum time between successive displays of each phase at each intersection.	4.4.1.2 The system operator needs to manage the coordination in small groups of signals to link phase service at some intersections with phase service at adjacent intersections. Note: Phase-based systems do not explicitly calculate cycle, offset and split at all intersections.
3.1.9.5.5	(Phase-based only) The ASCT shall alter the operation of the non-critical intersections to minimize stopping of traffic released from user-specified phases at the user-specified critical intersection.	4.4.1.2 The system operator needs to manage the coordination in small groups of signals to link phase service at some intersections with phase service at adjacent intersections. Note: Phase-based systems do not explicitly calculate cycle, offset and split at all intersections.
3.1.9.5.6	(Phase-based only) The ASCT shall alter the operation of the non-critical intersections to minimize stopping of traffic arriving at user-specified phases at the user-specified critical intersection.	4.4.1.2 The system operator needs to manage the coordination in small groups of signals to link phase service at some intersections with phase service at adjacent intersections. Note: Phase-based systems do not explicitly calculate cycle, offset and split at all intersections.
3.1.9.5.7	(Phase-based only) The ASCT shall adjust the state of the signal controller so that vehicles approaching a signal that have been served during a user-specified phase at an upstream signal do not stop.	4.4.1.2 The system operator needs to manage the coordination in small groups of signals to link phase service at some intersections with phase service at adjacent intersections. Note: Phase-based systems do not explicitly calculate cycle, offset and split at all intersections.
3.1.9.5.7	(Phase-based only) The ASCT shall adjust the state of the signal controller so that vehicles approaching a signal that have been served during a user-specified phase at an upstream signal do not stop.	4.4.1.5 The TSS Operator needs to minimize the chance that a queue forms at a specified location. Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.5 group when phase-based systems are allowed (phase-based systems do not explicitly calculate cycle, offset and split at all intersections). (Select requirements from two or all three groups when the vendor is given the choice of supplying the type of adaptive operation.)
3.1.9.6	Responsiveness
3.1.9.6.1	The ASCT shall limit the change in consecutive cycle lengths to be less than a user-specified value.	4.4.8.1 The TSS Operator needs to modify the ASCT operation to closely follow changes in traffic conditions.
3.1.9.6.2	The ASCT shall limit the change in phase times between consecutive cycles to be less than a user-specified value. (This does not apply to early gap-out or actuated phase skipping.)	4.4.8.1 The TSS Operator needs to modify the ASCT operation to closely follow changes in traffic conditions.
3.1.9.6.3	The ASCT shall limit the changes in the direction of primary coordination to a user-specified frequency.	4.4.8.1 The TSS Operator needs to modify the ASCT operation to closely follow changes in traffic conditions.
3.1.9.6.3	The ASCT shall limit the changes in the direction of primary coordination to a user-specified frequency.	4.4.8.2 The TSS Operator needs to constrain the selection of cycle lengths to those that provide acceptable operations, such as when resonant progression solutions are desired.
3.1.9.6.4	When a large change in traffic demand is detected, the ASCT shall respond more quickly than normal operation, subject to user-specified limits. (DEFINE 'MORE QUICKLY')	4.4.8.3 The TSS Operator needs to respond quickly to sudden large shifts in traffic conditions.
3.1.9.6.5	The ASCT shall select cycle length from a list of user-defined cycle lengths.	4.4.8.2 The TSS Operator needs to constrain the selection of cycle lengths to those that provide acceptable operations, such as when resonant progression solutions are desired.
3.1.10	Adaptive Advanced Controller Operation
3.1.10.1	When specified by the user, the ASCT shall serve a vehicle phase more than once for each time the coordinated phase is served.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.1	When specified by the user, the ASCT shall serve a vehicle phase more than once for each time the coordinated phase is served.	4.4.9.1.1 Service a phase more than once per cycle
3.1.10.2	The ASCT shall provide a minimum of XX phase overlaps.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.2	The ASCT shall provide a minimum of XX phase overlaps.	4.4.9.1.2 Operate at least XX overlap phases
3.1.10.3	The ASCT shall accommodate a minimum of XX phases at each signal	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.3	The ASCT shall accommodate a minimum of XX phases at each signal	4.4.9.1.3 Operate four rings, 16 phases and up to three phases per ring (Edit to suit your needs).
3.1.10.4	The ASCT shall accommodate a minimum of XX rings at each signal.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.4	The ASCT shall accommodate a minimum of XX rings at each signal.	4.4.9.1.3 Operate four rings, 16 phases and up to three phases per ring (Edit to suit your needs).
3.1.10.5	The ASCT shall accommodate a minimum of XX phases per ring	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.5	The ASCT shall accommodate a minimum of XX phases per ring	4.4.9.1.3 Operate four rings, 16 phases and up to three phases per ring (Edit to suit your needs).
3.1.10.6	The ASCT shall provide a minimum of XX different user-defined phase sequences for each signal.	4.4.1.6 The TSS Operator needs to modify the sequence of phases to support the various operational strategies.
3.1.10.6	The ASCT shall provide a minimum of XX different user-defined phase sequences for each signal.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.6	The ASCT shall provide a minimum of XX different user-defined phase sequences for each signal.	4.4.9.1.4 Permit different phase sequences under different traffic conditions
3.1.10.6.1	Each permissible phase sequence shall be user-assignable to any signal timing plan.	4.4.1.6 The TSS Operator needs to modify the sequence of phases to support the various operational strategies.
3.1.10.6.1	Each permissible phase sequence shall be user-assignable to any signal timing plan.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.6.1	Each permissible phase sequence shall be user-assignable to any signal timing plan.	4.4.9.1.4 Permit different phase sequences under different traffic conditions
3.1.10.6.2	Each permissible phase sequence shall be executable by a time of day schedule.	4.4.1.6 The TSS Operator needs to modify the sequence of phases to support the various operational strategies.
3.1.10.6.2	Each permissible phase sequence shall be executable by a time of day schedule.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.6.2	Each permissible phase sequence shall be executable by a time of day schedule.	4.4.9.1.4 Permit different phase sequences under different traffic conditions
3.1.10.6.3	Each permissible phase sequence shall be executable based on measured traffic conditions	4.4.1.6 The TSS Operator needs to modify the sequence of phases to support the various operational strategies.
3.1.10.6.3	Each permissible phase sequence shall be executable based on measured traffic conditions	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.6.3	Each permissible phase sequence shall be executable based on measured traffic conditions	4.4.9.1.4 Permit different phase sequences under different traffic conditions
3.1.10.7	The ASCT shall not prevent a phase/overlap output by time-of-day.	4.4.1.6 The TSS Operator needs to modify the sequence of phases to support the various operational strategies.
3.1.10.8	The ASCT shall not prevent a phase/overlap output based on an external input.	4.4.1.6 The TSS Operator needs to modify the sequence of phases to support the various operational strategies.
3.1.10.8	The ASCT shall not prevent a phase/overlap output based on an external input.	4.9.6 The TSS Operator needs to react to commands issued by (specify an external control or decision support system, such as an ICM system or another signal system).
3.1.10.9	The ASCT shall not prevent the following phases to be designated as coordinated phases. (User to list all required phases.)	4.4.1.6 The TSS Operator needs to modify the sequence of phases to support the various operational strategies.
3.1.10.9	The ASCT shall not prevent the following phases to be designated as coordinated phases. (User to list all required phases.)	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.9	The ASCT shall not prevent the following phases to be designated as coordinated phases. (User to list all required phases.)	4.4.9.1.9 Allow any phase to be designated as the coordinated phase
3.1.10.10	The ASCT shall have the option for a coordinated phase to be released early based on a user-definable point in the phase or cycle. (User select phase or cycle.)	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.10	The ASCT shall have the option for a coordinated phase to be released early based on a user-definable point in the phase or cycle. (User select phase or cycle.)	4.4.9.1.12 Allow the coordinated phase to terminate early under prescribed traffic conditions
3.1.10.11	The ASCT shall not prevent the controller from displaying flashing yellow arrow left turn or right turn. (SELECT AS APPLICABLE)	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.11	The ASCT shall not prevent the controller from displaying flashing yellow arrow left turn or right turn. (SELECT AS APPLICABLE)	4.4.9.1.15 Use flashing yellow arrow to control permissive left turns and right turns.
3.1.10.12	The ASCT shall not prevent the local signal controller from performing actuated phase control using XX extension/passage timers as assigned to user-specified vehicle detector input channels in the local controller.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.12	The ASCT shall not prevent the local signal controller from performing actuated phase control using XX extension/passage timers as assigned to user-specified vehicle detector input channels in the local controller.	4.4.9.1.11 Allow the controller to respond independently to individual lanes of an approach. This may be implemented in the signal controller using XX extension/passage timers, which may be assignable to each vehicle detector input channel. This may allow the adaptive operation to be based on data from a specific detector, or by excluding specific detectors.
3.1.10.12.1	The ASCT shall operate adaptively using user-specified detector channels.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.12.1	The ASCT shall operate adaptively using user-specified detector channels.	4.4.9.1.11 Allow the controller to respond independently to individual lanes of an approach. This may be implemented in the signal controller using XX extension/passage timers, which may be assignable to each vehicle detector input channel. This may allow the adaptive operation to be based on data from a specific detector, or by excluding specific detectors.
3.1.10.13	When adaptive operation is used in conjunction with normal coordination, the ASCT shall not prevent a controller serving a cycle length different from the cycles used at adjacent intersections.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.13	When adaptive operation is used in conjunction with normal coordination, the ASCT shall not prevent a controller serving a cycle length different from the cycles used at adjacent intersections.	4.4.9.1.16 Service side streets and pedestrian phases at minor locations more often than at adjacent signals when this can be done without compromising the quality of the coordination. (E.g., double-cycle mid-block pedestrian crossing signals.)
3.1.10.14	(Describe requirements to suit other custom controller features that must be accommodated.)	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.14	(Describe requirements to suit other custom controller features that must be accommodated.)	4.4.9.1.8 Accommodate the following custom features used by this agency (describe the features)
3.1.10.15	The ASCT shall operate adaptively with the following detector logic. (DESCRIBE THE CUSTOM LOGIC)	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.10.15	The ASCT shall operate adaptively with the following detector logic. (DESCRIBE THE CUSTOM LOGIC)	4.4.9.1.7 Allow detector logic at an intersection to be varied depending on local signal states
3.1.11	Adaptive Pedestrians
3.1.11.1	When a pedestrian phase is called, the ASCT shall execute pedestrian phases up to XX seconds before the vehicle green of the related vehicle phase.	4.4.5.5 The TSS Operator needs to accommodate early start of walk and exclusive pedestrian phases.
3.1.11.2	When a pedestrian phase is called, the ASCT shall accommodate pedestrian crossing times during adaptive operations.	4.4.5.2 The TSS Operator needs to accommodate infrequent pedestrian operation while maintaining adaptive operation. (This is appropriate for pedestrian calls that are common but not so frequent that they drive the operational needs.)
3.1.11.2	When a pedestrian phase is called, the ASCT shall accommodate pedestrian crossing times during adaptive operations.	4.4.5.3 The TSS Operator needs to incorporate frequent pedestrian operation into routine adaptive operation. (This is appropriate when pedestrians are frequent enough that they must be assumed to be present every cycle or nearly every cycle.)
3.1.11.3	When a pedestrian phase is called, the ASCT shall accommodate pedestrian crossing times then resume adaptive operation.	4.4.5.1 The TSS Operator needs to accommodate infrequent pedestrian operation and then adaptively recover. (This is appropriate for rare pedestrian calls.)
3.1.11.4	The ASCT shall execute user-specified exclusive pedestrian phases during adaptive operation.	4.4.5.5 The TSS Operator needs to accommodate early start of walk and exclusive pedestrian phases.
3.1.11.5	The ASCT shall execute pedestrian recall on user-defined phases in accordance with a time of day schedule.	4.4.5.3 The TSS Operator needs to incorporate frequent pedestrian operation into routine adaptive operation. (This is appropriate when pedestrians are frequent enough that they must be assumed to be present every cycle or nearly every cycle.)
3.1.11.6	The ASCT shall begin a non-coordinated phase later than its normal starting point within the cycle when all of the following conditions exist: The user enables this feature Sufficient time in the cycle remains to serve the minimum green times for the phase and the subsequent non-coordinated phases before the beginning of the coordinated phase The phase is called after its normal start time The associated pedestrian phase is not called	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.11.6	The ASCT shall begin a non-coordinated phase later than its normal starting point within the cycle when all of the following conditions exist: The user enables this feature Sufficient time in the cycle remains to serve the minimum green times for the phase and the subsequent non-coordinated phases before the beginning of the coordinated phase The phase is called after its normal start time The associated pedestrian phase is not called	4.4.9.1.13 Allow flexible timing of non-coordinated phases (such as late start of a phase) while maintaining coordination
3.1.11.7	When specified by the user, the ASCT shall execute pedestrian recall on pedestrian phase adjacent to coordinated phases.	4.4.5.3 The TSS Operator needs to incorporate frequent pedestrian operation into routine adaptive operation. (This is appropriate when pedestrians are frequent enough that they must be assumed to be present every cycle or nearly every cycle.)
3.1.11.8	When the pedestrian phases are on recall, the ASCT shall accommodate pedestrian timing during adaptive operation.	4.4.5.3 The TSS Operator needs to incorporate frequent pedestrian operation into routine adaptive operation. (This is appropriate when pedestrians are frequent enough that they must be assumed to be present every cycle or nearly every cycle.)
3.1.11.9	The ASCT shall not inhibit negative vehicle and pedestrian phase timing.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.11.9	The ASCT shall not inhibit negative vehicle and pedestrian phase timing.	4.4.9.1.17 Use negative pedestrian phasing to prevent an overlap conflicting with a pedestrian walk/don't walk
3.1.11.10	The ASCT shall accommodate the following custom pedestrian features. (Specify the requirements in conjunction with their corresponding need.)	4.4.5.4 The TSS Operator needs to accommodate the following custom pedestrian features. (Describe custom features in this need and then create appropriate requirements.)
3.1.12	Adaptive Special Functions
3.1.12.1	The ASCT shall set a specific state for each special function output based on the occupancy on a user-specified detector.	4.4.9.1 The TSS Operator needs to implement the following advanced controller features while maintaining adaptive operation:
3.1.12.1	The ASCT shall set a specific state for each special function output based on the occupancy on a user-specified detector.	4.4.9.1.11 Allow the controller to respond independently to individual lanes of an approach. This may be implemented in the signal controller using XX extension/passage timers, which may be assignable to each vehicle detector input channel. This may allow the adaptive operation to be based on data from a specific detector, or by excluding specific detectors.
3.1.12.1	The ASCT shall set a specific state for each special function output based on the occupancy on a user-specified detector.	4.9.5 The TSS Operator needs to be able to turn on signs that control traffic or provide driver information when specific traffic conditions occur, when needed to support the adaptive operation, when congestion is detected at critical locations or according to a time-of-day schedule.
3.1.12.2	The ASCT shall set a specific state for each special function output based on the current cycle length.	4.9.5 The TSS Operator needs to be able to turn on signs that control traffic or provide driver information when specific traffic conditions occur, when needed to support the adaptive operation, when congestion is detected at critical locations or according to a time-of-day schedule.
3.1.12.3	The ASCT shall set a specific state for each special function output based on a time-of-day schedule.	4.9.5 The TSS Operator needs to be able to turn on signs that control traffic or provide driver information when specific traffic conditions occur, when needed to support the adaptive operation, when congestion is detected at critical locations or according to a time-of-day schedule.
3.1.13	Adaptive Detection
3.1.13.1	The ASCT shall be compatible with the following detector technologies (agency to specify): Detector type A Detector type B Detector type C	4.7.2.1.2 Detector type (list acceptable equipment)
3.1.13.2	The ASCT vendor shall specify detector requirements.	4.7.2.1.2 Detector type (list acceptable equipment)
3.1.13.2.1	Vendor shall specify required detector accuracy	4.7.2.1.2 Detector type (list acceptable equipment)
3.1.13.2.2	Vendor shall specify required detector output latency	4.7.2.1.2 Detector type (list acceptable equipment)
3.1.13.2.3	Vendor shall specify detection zone coverage	4.7.2.1.2 Detector type (list acceptable equipment)
3.1.13.2.4	Vendor shall specify mounting requirements	4.7.2.1.2 Detector type (list acceptable equipment)
3.1.13.2.5	Vendor shall specify installation requirements	4.7.2.1.2 Detector type (list acceptable equipment)
3.1.13.2.6	Detectors verified against the provided requirements shall be deemed acceptable by the ASCT Vendor.	4.7.2.1.2 Detector type (list acceptable equipment)
3.1.13.2.7	The Vendor shall be responsible to provide expected functionality using verified detectors.	4.7.2.1.2 Detector type (list acceptable equipment)
3.1.13.3	The ASCT shall measure the length of queues to support the adaptive algorithm	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.13.3	The ASCT shall measure the length of queues to support the adaptive algorithm	4.4.4.1 The TSS Operator needs to detect queues from outside the system and modify the ASCT operation to accommodate the queuing.
3.1.13.3	The ASCT shall measure the length of queues to support the adaptive algorithm	4.4.4.2 The TSS Operator needs to detect queues within the system's boundaries and modify the ASCT operation to accommodate the queuing.
3.1.13.3	The ASCT shall measure the length of queues to support the adaptive algorithm	4.4.4.3 The TSS Operator needs to detect queues propagating outside its boundaries from within the ASCT boundaries, and modify its operation to accommodate the queuing.
3.1.13.3	The ASCT shall measure the length of queues to support the adaptive algorithm	4.4.4.4 The TSS Operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.
3.1.13.3	The ASCT shall measure the length of queues to support the adaptive algorithm	4.4.4.5 The TSS Operator needs to prevent queues forming at user-specified locations.
3.1.13.3.1	The measurement shall be made with sufficient precision to support the adaptive algorithm.	4.4.1.1.4 Manage the lengths of queues Note to user when selecting these requirements: Select from requirements in the 3.1.9.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split). Select from requirements in the 3.1.9.3 group when non-sequence-based systems are allowed (non-sequence-based systems do not explicitly calculate cycle, offset, and split). (Select requirements from both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)
3.1.13.3.1	The measurement shall be made with sufficient precision to support the adaptive algorithm.	4.4.4.1 The TSS Operator needs to detect queues from outside the system and modify the ASCT operation to accommodate the queuing.
3.1.13.3.1	The measurement shall be made with sufficient precision to support the adaptive algorithm.	4.4.4.2 The TSS Operator needs to detect queues within the system's boundaries and modify the ASCT operation to accommodate the queuing.
3.1.13.3.1	The measurement shall be made with sufficient precision to support the adaptive algorithm.	4.4.4.3 The TSS Operator needs to detect queues propagating outside its boundaries from within the ASCT boundaries, and modify its operation to accommodate the queuing.
3.1.13.3.1	The measurement shall be made with sufficient precision to support the adaptive algorithm.	4.4.4.4 The TSS Operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.
3.1.13.3.1	The measurement shall be made with sufficient precision to support the adaptive algorithm.	4.4.4.5 The TSS Operator needs to prevent queues forming at user-specified locations.
3.1.14	Adaptive Railroad and Emergency Vehicle Preemption
3.1.14.1	The ASCT shall maintain adaptive operation at non-preempted intersections during railroad preemption.	4.4.6.1 The TSS Operator needs to adaptively accommodate railroad and light rail preemption (explain further)
3.1.14.2	The ASCT shall maintain adaptive operation at non-preempted intersections during emergency vehicle preemption.	4.4.6.2 The TSS Operator needs to adaptively accommodate emergency vehicle preemption (explain further)
3.1.14.3	The ASCT shall maintain adaptive operation at non-preempted intersections during Light Rail Transit preemption.	4.4.6.1 The TSS Operator needs to adaptively accommodate railroad and light rail preemption (explain further)
3.1.14.4	The ASCT shall resume adaptive control of signal controllers when preemptions are released.	4.4.6.1 The TSS Operator needs to adaptively accommodate railroad and light rail preemption (explain further)
3.1.14.4	The ASCT shall resume adaptive control of signal controllers when preemptions are released.	4.4.6.2 The TSS Operator needs to adaptively accommodate emergency vehicle preemption (explain further)
3.1.14.5	The ASCT shall execute user-specified actions at non-preempted signal controllers during preemption. (E.g., inhibit a phase, activate a sign, display a message on a DMS)	4.4.6.1 The TSS Operator needs to adaptively accommodate railroad and light rail preemption (explain further)
3.1.14.5	The ASCT shall execute user-specified actions at non-preempted signal controllers during preemption. (E.g., inhibit a phase, activate a sign, display a message on a DMS)	4.4.6.2 The TSS Operator needs to adaptively accommodate emergency vehicle preemption (explain further)
3.1.14.6	The ASCT shall operate normally at non-preempted signal controllers when special functions are engaged by a preemption event. (Examples of such special functions are a phase omit, a phase maximum recall or a fire route.)	4.4.6.1 The TSS Operator needs to adaptively accommodate railroad and light rail preemption (explain further)
3.1.14.6	The ASCT shall operate normally at non-preempted signal controllers when special functions are engaged by a preemption event. (Examples of such special functions are a phase omit, a phase maximum recall or a fire route.)	4.4.6.2 The TSS Operator needs to adaptively accommodate emergency vehicle preemption (explain further)
3.1.14.7	The ASCT shall release user-specified signal controllers to local control when one signal in a group is preempted.	4.4.6.1 The TSS Operator needs to adaptively accommodate railroad and light rail preemption (explain further)
3.1.14.7	The ASCT shall release user-specified signal controllers to local control when one signal in a group is preempted.	4.4.6.2 The TSS Operator needs to adaptively accommodate emergency vehicle preemption (explain further)
3.1.14.8	The ASCT shall not prevent the local signal controller from operating in normally detected limited-service actuated mode during preemption.	4.4.6.1 The TSS Operator needs to adaptively accommodate railroad and light rail preemption (explain further)
3.1.14.8	The ASCT shall not prevent the local signal controller from operating in normally detected limited-service actuated mode during preemption.	4.4.6.2 The TSS Operator needs to adaptively accommodate emergency vehicle preemption (explain further)
3.1.15	Adaptive Transit Priority
3.1.15.1	The ASCT shall continue adaptive operations of a group when one of its signal controllers has a transit priority call.	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.2	The ASCT shall advance the start of a user-specified green phase in response to a transit priority call.	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.2.1	The advance of start of green phase shall be user-defined.	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.2.2	Adaptive operations shall continue during the advance of the start of green phase.	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.3	The ASCT shall delay the end of a green phase, in response to a priority call.	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.3.1	The delay of end of green phase shall be user-defined.	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.3.2	Adaptive operations shall continue during the delay of the end of green phase.	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.4	The ASCT shall permit at least XX exclusive transit phases.	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.4.1	Adaptive operations shall continue when there is an exclusive transit phase call.	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.5	The ASCT shall control vehicle phases independently of the following:	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.5.1	LRT only phases	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.5.2	Bus only phases	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.6	The ASCT shall interface with external bus transit priority system in the following fashion… (explain the external system and refer to other interfaces as appropriate)	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.7	The ASCT shall interface with external light rail transit priority system in the following fashion… (explain the external system and refer to other interfaces as appropriate)	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.15.8	The ASCT shall accept a transit priority call from: a signal controller/transit vehicle detector; an external system.	4.4.6.3 The TSS Operator needs to adaptively accommodate bus and light rail transit signal priority (explain further)
3.1.16	Traffic and Operational Performance Measurement, Monitoring and Reporting
3.1.16.1	TSS Collection and Storage
3.1.16.1.1	The system shall collect and store volume data for each detector.	4.5.1.4 The TSS Operator needs a log of all software functions executed by the central system and local controllers.
3.1.16.1.2	The system shall collect and store occupancy data for each detector.	4.5.1.4 The TSS Operator needs a log of all software functions executed by the central system and local controllers.
3.1.16.1.3	The system shall time stamp each detector actuation.	4.5.1.4 The TSS Operator needs a log of all software functions executed by the central system and local controllers.
3.1.16.1.4	The system shall upload local controller logs by TSS Operator manual command.	4.5.1.4 The TSS Operator needs a log of all software functions executed by the central system and local controllers.
3.1.16.1.5	The system shall upload local controller logs according to a time of day schedule.	4.5.1.4 The TSS Operator needs a log of all software functions executed by the central system and local controllers.
3.1.16.1.6	The TSS shall collect and store phase data for every permitted phase, including the length of the phase split [This requirement may be superfluous in systems supported by high-resolution data. This requirement is intended to support legacy approaches to providing a split monitoring capability within traffic signal systems.]	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.7	The system shall collect and store the following logs in user-definable format:	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.7	The system shall collect and store the following logs in user-definable format:	4.5.1.2 The TSS Operator needs a permanent record of each detected fault.
3.1.16.1.7	The system shall collect and store the following logs in user-definable format:	4.5.1.3 The TSS Operator needs a time-stamped record of who accesses the system, all manual commands, and data changes made during a session.
3.1.16.1.7	The system shall collect and store the following logs in user-definable format:	4.5.3.1 The TSS Operator needs to collect and store high resolution data from traffic signal controllers.
3.1.16.1.7.1	Timing plan change	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.7.2	Signal phase change	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.7.3	Special function change	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.7.4	Coordination status change	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.7.5	Operating mode change	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.7.6	Equipment failure	4.5.1.2 The TSS Operator needs a permanent record of each detected fault.
3.1.16.1.7.7	Communications failure	4.5.1.2 The TSS Operator needs a permanent record of each detected fault.
3.1.16.1.7.8	Manual commands	4.5.1.3 The TSS Operator needs a time-stamped record of who accesses the system, all manual commands, and data changes made during a session.
3.1.16.1.7.9	Operator log-on	4.5.1.3 The TSS Operator needs a time-stamped record of who accesses the system, all manual commands, and data changes made during a session.
3.1.16.1.7.10	Operator log-off	4.5.1.3 The TSS Operator needs a time-stamped record of who accesses the system, all manual commands, and data changes made during a session.
3.1.16.1.7.11	Emergency vehicle preemption on-off	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.7.12	Transit priority request, on-off	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.7.13	Action sets	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.7.14	Database changes	4.5.1.3 The TSS Operator needs a time-stamped record of who accesses the system, all manual commands, and data changes made during a session.
3.1.16.1.8	The system shall store the logs, alarms, and reports for a user defined amount of time (at least (X) years) where they are easily accessible. [User specify]	4.5.1.2 The TSS Operator needs a permanent record of each detected fault.
3.1.16.1.8	The system shall store the logs, alarms, and reports for a user defined amount of time (at least (X) years) where they are easily accessible. [User specify]	4.6.1 The TSS Operator needs to access the data on the system for (XX) months after which it will be archived.
3.1.16.1.9	The system shall automatically transfer all logs, alarms, and reports to an archive system.	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.9	The system shall automatically transfer all logs, alarms, and reports to an archive system.	4.5.1.2 The TSS Operator needs a permanent record of each detected fault.
3.1.16.1.9	The system shall automatically transfer all logs, alarms, and reports to an archive system.	4.6.1 The TSS Operator needs to access the data on the system for (XX) months after which it will be archived.
3.1.16.1.10	The archive system shall store each log, alarm and report for a minimum of (X) years (USER SPECIFY).	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.1.10	The archive system shall store each log, alarm and report for a minimum of (X) years (USER SPECIFY).	4.5.1.2 The TSS Operator needs a permanent record of each detected fault.
3.1.16.1.10	The archive system shall store each log, alarm and report for a minimum of (X) years (USER SPECIFY).	4.6.1 The TSS Operator needs to access the data on the system for (XX) months after which it will be archived.
3.1.16.2	TSS Alerts
3.1.16.2.1	The system shall create alerts of the following events: Detector fault/failure Communication fault/failure Flash mode Preemption fault/failure Transit signal priority fault/failure Cabinet flash Cabinet door open Temperature out of range Adaptive Processor and Algorithms (Note: Only with adaptive operations)	4.5.6.2 The TSS Operator needs to immediately know when a hardware or software fault occurs at a local intersection.
3.1.16.2.2	The system shall provide an alert of any discrepancies between the central controller database and the infield database for each controller.	4.5.6.2 The TSS Operator needs to immediately know when a hardware or software fault occurs at a local intersection.
3.1.16.2.3	The system shall classify every alerts as critical, warning, and informational only, based user-specified rules.	4.5.6.2 The TSS Operator needs to immediately know when a hardware or software fault occurs at a local intersection.
3.1.16.2.3.1	The system shall alert TSS Operator via text message.	4.5.6.2 The TSS Operator needs to immediately know when a hardware or software fault occurs at a local intersection.
3.1.16.2.3.2	The system shall alert TSS Operator via email.	4.5.6.2 The TSS Operator needs to immediately know when a hardware or software fault occurs at a local intersection.
3.1.16.2.3.3	The system shall alert TSS Operator by message on TSS Operator's desktop.	4.5.6.2 The TSS Operator needs to immediately know when a hardware or software fault occurs at a local intersection.
3.1.16.3	TSS Performance Measurement Reporting
3.1.16.3.1	The system shall create performance measure reports from the data in the controller logs, including the following: Split logs (average split times, percent max out and force offs, percent gap outs, percent skips) Detector health Coordination plans Pedestrian actuations Transit signal priority actuations Emergency vehicle preemption actuations Real time split reports (showing programmed and actual splits)	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.3.2	The system shall create standard reports [specify].	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.3.3	The system shall create user customizable reports.	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.3.3	The system shall create user customizable reports.	4.5.3.1 The TSS Operator needs to collect and store high resolution data from traffic signal controllers.
3.1.16.3.4	The system shall create the reports for a user-specified period.	4.5.1.1 The TSS Operator needs to generate historical and real time reports that describe TSS operation.
3.1.16.3.4	The system shall create the reports for a user-specified period.	4.5.3.1 The TSS Operator needs to collect and store high resolution data from traffic signal controllers.
3.1.16.3.5	The system shall collect detector data consistent with the Indiana Traffic Signal High Resolution Data Logger Enumerations.	4.5.4.1 The TSS Operator needs the system to accept high resolution controller data in order to calculate and report intersection and system performance measurements that support operational objectives.
3.1.16.3.6	The system shall collect signal phase data consistent with the Indiana Traffic Signal High Resolution Data Logger Enumerations.	4.5.4.1 The TSS Operator needs the system to accept high resolution controller data in order to calculate and report intersection and system performance measurements that support operational objectives.
3.1.16.3.7	The system shall produce performance reports consistent with: Attached performance report document (USER SPECIFIED - attach) Purdue Pooled Fund Study	4.5.3.1 The TSS Operator needs to collect and store high resolution data from traffic signal controllers.
3.1.16.3.7	The system shall produce performance reports consistent with: Attached performance report document (USER SPECIFIED - attach) Purdue Pooled Fund Study	4.5.4.1 The TSS Operator needs the system to accept high resolution controller data in order to calculate and report intersection and system performance measurements that support operational objectives.
3.1.16.4	Adaptive Collection and Storage
3.1.16.4.1	The ASCT shall report measures of current traffic conditions on which it bases signal state alterations.	4.5.2.2 The TSS Operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.
3.1.16.4.2	The ASCT shall report all intermediate calculated values that are affected by calibration parameters.	4.5.2.2 The TSS Operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.
3.1.16.4.3	The ASCT shall maintain a log of all signal state alterations directed by the ASCT.	4.5.2.2 The TSS Operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.
3.1.16.4.3	The ASCT shall maintain a log of all signal state alterations directed by the ASCT.	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.16.4.3.1	The ASCT log shall include all events directed by the external inputs.	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.16.4.3.2	The ASCT log shall include all external output state changes.	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.16.4.3.3	The ASCT log shall include all actual parameter values that are subject to user-specified values.	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.16.4.3.4	The ASCT shall maintain the records in this ASCT log for XX period.	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.16.4.3.5	The ASCT shall archive the ASCT log in the following manner: (Specify format, frequency, etc., to suit your needs.)	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.16.5	High Resolution Traffic Performance Measurement Collection and Storage
3.1.16.5.1	The Performance Measurement Server shall retrieve and store high-resolution data from local traffic signal controllers. [This requires the agency to provide traffic signal controllers that store the high-resolution data, which are not covered by these Model Documents.	4.5.3.1 The TSS Operator needs to collect and store high resolution data from traffic signal controllers.
3.1.16.5.1.1	High-resolution data are defined by (specify details).	4.5.3.1 The TSS Operator needs to collect and store high resolution data from traffic signal controllers.
3.1.16.5.1.2	The Performance Measurement Server shall store uploaded high-resolution data for [specify timeframe].	4.5.3.1 The TSS Operator needs to collect and store high resolution data from traffic signal controllers.
3.1.16.5.1.3	The TSS shall not prevent the local controller from accessing local devices as needed to store high-resolution data.	4.5.3.1 The TSS Operator needs to collect and store high resolution data from traffic signal controllers.
3.1.16.6	High Resolution Traffic Performance Measurement Processing
3.1.16.6.1	The Performance Measurement Server shall process the collected and stored high resolution data to produce the following reports: Signal Measures Charts: Approach Delay Approach Speed Approach Volume Arrivals on Red Pedestrian Delay Preemption Details Purdue Coordination Diagram Purdue Link Pivot Purdue Phase Termination Purdue Split Failures Split Monitor Turning Mover Red Actuations Reports: Usage	4.5.4.1 The TSS Operator needs the system to accept high resolution controller data in order to calculate and report intersection and system performance measurements that support operational objectives.
3.1.16.7	High Resolution Traffic Performance Measurement Reports
3.1.16.7.1	The TSS shall provide predefined reports of stored data for non-technical recipients in accordance with user-specified formats. (Specify report formats to accompany this requirement.)	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.16.7.2	The TSS shall display stored data that illustrate adaptive input data and output decisions. (This display will be used by the TSS Operator.)	4.5.2.2 The TSS Operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.
3.1.16.7.2	The TSS shall display stored data that illustrate adaptive input data and output decisions. (This display will be used by the TSS Operator.)	4.5.2.6 The TSS Operator needs to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.
3.1.16.7.3	The Performance Measurement Server shall provide the following reports: Signal Measures Charts: Approach Delay Approach Speed Approach Volume Arrivals on Red Pedestrian Delay Preemption Details Purdue Coordination Diagram Purdue Link Pivot Purdue Phase Termination Purdue Split Failures Split Monitor Turning Movement Yellow and Red Actuations Reports: Usage	4.5.5.1 The TSS Operator needs to view reports showing traffic operational performance.
3.1.16.7.3.1	Performance measurement reports shall be consistent with descriptions in ATSPM version 4.0 (or later) documentation.	4.5.5.1 The TSS Operator needs to view reports showing traffic operational performance.
3.1.16.7.4	The TSS (ASCT) shall provide traffic performance measurement using probe vehicle reports provided by an external service [specify].	4.5.5.1 The TSS Operator needs to view reports showing traffic operational performance.
3.1.16.7.5	The TSS (ASCT) shall provide traffic performance measurement using [specify alternative approaches not covered in other requirements].	4.5.5.1 The TSS Operator needs to view reports showing traffic operational performance.
3.1.16.8	High Resolution Traffic Performance Measurement Alerts
3.1.16.8.1	The TSS shall provide configurable alerts to the TSS Operator based on traffic operational performance. (Specify alerts to accompany this requirement.)	4.5.6.1 The TSS Operator needs to receive alerts about traffic operational performance.
3.1.17	External Interfaces
3.1.17.1	The TSS (ASCT) shall support external interfaces according to the referenced interface control documents and the following detailed requirements. (Insert appropriate requirements that suit your needs. Interface data flows should be documented in your ITS Information layer protocol Application layer protocol Lower layer protocol Data aggregation Frequency of storage Frequency of reporting Duration of storage)	4.4.3.1 The TSS Operator needs to adaptively control signals operated by (specify jurisdictions).
3.1.17.1	The TSS (ASCT) shall support external interfaces according to the referenced interface control documents and the following detailed requirements. (Insert appropriate requirements that suit your needs. Interface data flows should be documented in your ITS Information layer protocol Application layer protocol Lower layer protocol Data aggregation Frequency of storage Frequency of reporting Duration of storage)	4.4.3.2 The TSS Operator needs to send data to another system that would allow the other system to coordinate with the ASCT system.
3.1.17.1	The TSS (ASCT) shall support external interfaces according to the referenced interface control documents and the following detailed requirements. (Insert appropriate requirements that suit your needs. Interface data flows should be documented in your ITS Information layer protocol Application layer protocol Lower layer protocol Data aggregation Frequency of storage Frequency of reporting Duration of storage)	4.4.3.4 The TSS Operator needs to receive data from another system that will allow the ASCT system to coordinate its operation with the adjacent system.
3.1.17.1	The TSS (ASCT) shall support external interfaces according to the referenced interface control documents and the following detailed requirements. (Insert appropriate requirements that suit your needs. Interface data flows should be documented in your ITS Information layer protocol Application layer protocol Lower layer protocol Data aggregation Frequency of storage Frequency of reporting Duration of storage)	4.5.2.5 The TSS Operator needs to report performance data in real time to (specify external system).
3.1.17.1	The TSS (ASCT) shall support external interfaces according to the referenced interface control documents and the following detailed requirements. (Insert appropriate requirements that suit your needs. Interface data flows should be documented in your ITS Information layer protocol Application layer protocol Lower layer protocol Data aggregation Frequency of storage Frequency of reporting Duration of storage)	4.9.1 The TSS Operator needs to align coordinated traffic signals in the system in question with coordinated traffic signals in an adjacent system. (The intent of this need is to maintain cycle-offset-split signal coordination across system boundaries. Basic coordination can be provided by using timings that are compatible in both systems, following compatible time-of-day schedules, and maintaining synchronization of the time-of-day clocks. Under this need, the system is responsible only for the clock synchronization, and the user is responsible for compatible timings and schedules.)
3.1.17.1	The TSS (ASCT) shall support external interfaces according to the referenced interface control documents and the following detailed requirements. (Insert appropriate requirements that suit your needs. Interface data flows should be documented in your ITS Information layer protocol Application layer protocol Lower layer protocol Data aggregation Frequency of storage Frequency of reporting Duration of storage)	4.9.2 The TSS Operator needs to select coordinated signal timing patterns (including cycle, offset, split, special functions, and phase sequence) based on the timing patterns in current operation in an adjacent system. (This user need addresses both time-of-day and traffic responsive coordination modes. In addition to the clock synchronization provided in 4.9.1, this user need also requires the system to align its timing pattern in use with an adjacent system automatically. This user need does not mean the system will create signal timings that are compatible—that is assumed to be the responsibility of the user.)
3.1.17.1	The TSS (ASCT) shall support external interfaces according to the referenced interface control documents and the following detailed requirements. (Insert appropriate requirements that suit your needs. Interface data flows should be documented in your ITS Information layer protocol Application layer protocol Lower layer protocol Data aggregation Frequency of storage Frequency of reporting Duration of storage)	4.9.3 The TSS Operator needs to provide signal operational data to an external display service, which may be a regional display map at another traffic management center.
3.1.17.1	The TSS (ASCT) shall support external interfaces according to the referenced interface control documents and the following detailed requirements. (Insert appropriate requirements that suit your needs. Interface data flows should be documented in your ITS Information layer protocol Application layer protocol Lower layer protocol Data aggregation Frequency of storage Frequency of reporting Duration of storage)	4.9.4 The TSS Operator needs to allow control of the system by the operator of an external system. (The envisioned scenario is a freeway management operator engaging a particular coordinated signal timing pattern to carry traffic diverting around a freeway incident or bottleneck on appropriate arterial streets. This engagement may need to be done through the traffic management system in use by the freeway management operator.)
3.1.17.1	The TSS (ASCT) shall support external interfaces according to the referenced interface control documents and the following detailed requirements. (Insert appropriate requirements that suit your needs. Interface data flows should be documented in your ITS Information layer protocol Application layer protocol Lower layer protocol Data aggregation Frequency of storage Frequency of reporting Duration of storage)	4.9.6 The TSS Operator needs to react to commands issued by (specify an external control or decision support system, such as an ICM system or another signal system).
3.1.17.1.1	The ASCT shall send operational data to XX external system. (Insert appropriate requirements that suit your needs.)	4.4.3.2 The TSS Operator needs to send data to another system that would allow the other system to coordinate with the ASCT system.
3.1.17.1.1	The ASCT shall send operational data to XX external system. (Insert appropriate requirements that suit your needs.)	4.5.2.5 The TSS Operator needs to report performance data in real time to (specify external system).
3.1.17.1.1	The ASCT shall send operational data to XX external system. (Insert appropriate requirements that suit your needs.)	4.9.1 The TSS Operator needs to align coordinated traffic signals in the system in question with coordinated traffic signals in an adjacent system. (The intent of this need is to maintain cycle-offset-split signal coordination across system boundaries. Basic coordination can be provided by using timings that are compatible in both systems, following compatible time-of-day schedules, and maintaining synchronization of the time-of-day clocks. Under this need, the system is responsible only for the clock synchronization, and the user is responsible for compatible timings and schedules.)
3.1.17.1.2	The ASCT shall send control data to the XX external system. (Insert appropriate requirements that suit your needs.)	4.4.3.2 The TSS Operator needs to send data to another system that would allow the other system to coordinate with the ASCT system.
3.1.17.1.2	The ASCT shall send control data to the XX external system. (Insert appropriate requirements that suit your needs.)	4.9.2 The TSS Operator needs to select coordinated signal timing patterns (including cycle, offset, split, special functions, and phase sequence) based on the timing patterns in current operation in an adjacent system. (This user need addresses both time-of-day and traffic responsive coordination modes. In addition to the clock synchronization provided in 4.9.1, this user need also requires the system to align its timing pattern in use with an adjacent system automatically. This user need does not mean the system will create signal timings that are compatible—that is assumed to be the responsibility of the user.)
3.1.17.1.3	The ASCT shall send monitoring data to the XX external system. (Insert appropriate requirements that suit your needs.)	4.5.2.1 The agency needs the (specify external decision support system) to be able to monitor the ASCT system automatically.
3.1.17.1.3	The ASCT shall send monitoring data to the XX external system. (Insert appropriate requirements that suit your needs.)	4.9.3 The TSS Operator needs to provide signal operational data to an external display service, which may be a regional display map at another traffic management center.
3.1.17.1.4	The ASCT shall send coordination data to the XX external system. (Insert appropriate requirements that suit your needs.)	4.4.3.2 The TSS Operator needs to send data to another system that would allow the other system to coordinate with the ASCT system.
3.1.17.1.4	The ASCT shall send coordination data to the XX external system. (Insert appropriate requirements that suit your needs.)	4.9.4 The TSS Operator needs to allow control of the system by the operator of an external system. (The envisioned scenario is a freeway management operator engaging a particular coordinated signal timing pattern to carry traffic diverting around a freeway incident or bottleneck on appropriate arterial streets. This engagement may need to be done through the traffic management system in use by the freeway management operator.)
3.1.17.1.5	The ASCT shall send performance data to the XX external system. (Insert appropriate requirements that suit your needs.)	4.4.3.2 The TSS Operator needs to send data to another system that would allow the other system to coordinate with the ASCT system.
3.1.17.1.5	The ASCT shall send performance data to the XX external system. (Insert appropriate requirements that suit your needs.)	4.5.2.5 The TSS Operator needs to report performance data in real time to (specify external system).
3.1.17.1.6	The ASCT shall receive commands from the XX external system.	4.4.3.2 The TSS Operator needs to send data to another system that would allow the other system to coordinate with the ASCT system.
3.1.17.1.6	The ASCT shall receive commands from the XX external system.	4.9.6 The TSS Operator needs to react to commands issued by (specify an external control or decision support system, such as an ICM system or another signal system).
3.1.17.1.7	The ASCT shall implement the following commands from the XX external system when commanded: (Edit as appropriate for your situation) Specified cycle length Specified direction of progression Specified adaptive strategy	4.5.2.1 The agency needs the (specify external decision support system) to be able to monitor the ASCT system automatically.
3.1.17.1.7	The ASCT shall implement the following commands from the XX external system when commanded: (Edit as appropriate for your situation) Specified cycle length Specified direction of progression Specified adaptive strategy	4.9.6 The TSS Operator needs to react to commands issued by (specify an external control or decision support system, such as an ICM system or another signal system).
3.1.17.1.8	The ASCT shall conform its operation to an external system's operation.	4.4.3.2 The TSS Operator needs to send data to another system that would allow the other system to coordinate with the ASCT system.
3.1.17.1.8	The ASCT shall conform its operation to an external system's operation.	4.4.3.4 The TSS Operator needs to receive data from another system that will allow the ASCT system to coordinate its operation with the adjacent system.
3.1.17.1.8	The ASCT shall conform its operation to an external system's operation.	4.4.3.6 The TSS Operator needs to detect traffic approaching from a neighboring system and coordinate the ASCT operation with the adjacent system.
3.1.17.1.8	The ASCT shall conform its operation to an external system's operation.	4.9.6 The TSS Operator needs to react to commands issued by (specify an external control or decision support system, such as an ICM system or another signal system).
3.1.17.1.8.1	The ASCT shall alter its operation to minimize interruption of traffic entering the system. (This may be achieved via detection, with no direct connection to the other system.)	4.4.3.4 The TSS Operator needs to receive data from another system that will allow the ASCT system to coordinate its operation with the adjacent system.
3.1.17.1.8.1	The ASCT shall alter its operation to minimize interruption of traffic entering the system. (This may be achieved via detection, with no direct connection to the other system.)	4.4.3.6 The TSS Operator needs to detect traffic approaching from a neighboring system and coordinate the ASCT operation with the adjacent system.
3.1.17.1.8.2	The ASCT shall operate a fixed cycle length to match the cycle length of an adjacent system.	4.4.3.5 The TSS Operator needs to constrain the adaptive system to operate a cycle length compatible with the crossing arterial.
3.1.17.1.8.3	The ASCT shall alter its operation based on data received from another system.	4.4.3.4 The TSS Operator needs to receive data from another system that will allow the ASCT system to coordinate its operation with the adjacent system.
3.1.17.1.8.4	The ASCT shall support adaptive coordination on crossing routes.	4.4.3.3 The TSS Operator needs to adaptively coordinate signals on two crossing routes simultaneously. (Include signals on crossing arterials within the boundaries of the adaptive systems mapped in Chapter 3.)
3.1.17.1.9	The ASCT shall set the state of external input/output states according to a time-of-day schedule.	4.5.2.5 The TSS Operator needs to report performance data in real time to (specify external system).
3.1.17.1.9	The ASCT shall set the state of external input/output states according to a time-of-day schedule.	4.9.5 The TSS Operator needs to be able to turn on signs that control traffic or provide driver information when specific traffic conditions occur, when needed to support the adaptive operation, when congestion is detected at critical locations or according to a time-of-day schedule.
3.1.17.1.10	The ASCT output states shall be settable according to a time-of-day schedule.	4.9.5 The TSS Operator needs to be able to turn on signs that control traffic or provide driver information when specific traffic conditions occur, when needed to support the adaptive operation, when congestion is detected at critical locations or according to a time-of-day schedule.
3.1.17.1.10	The ASCT output states shall be settable according to a time-of-day schedule.	4.9.6 The TSS Operator needs to react to commands issued by (specify an external control or decision support system, such as an ICM system or another signal system).
3.1.17.1.11	The ASCT shall implement the following commands from the XX external system when commanded: (Edit as appropriate for your situation) Specified cycle length	4.9.6 The TSS Operator needs to react to commands issued by (specify an external control or decision support system, such as an ICM system or another signal system).
3.1.17.1.12	The ASCT shall conform its operation to an external system's operation.	4.4.3.4 The TSS Operator needs to receive data from another system that will allow the ASCT system to coordinate its operation with the adjacent system.
3.1.17.1.12	The ASCT shall conform its operation to an external system's operation.	4.4.3.6 The TSS Operator needs to detect traffic approaching from a neighboring system and coordinate the ASCT operation with the adjacent system.
3.1.17.1.12	The ASCT shall conform its operation to an external system's operation.	4.9.6 The TSS Operator needs to react to commands issued by (specify an external control or decision support system, such as an ICM system or another signal system).
3.1.18	Software
3.1.18.1	The vendor's software shall be fully operational within the following platform: (edit as appropriate) Windows-PC, Linux, Mac-OS, Unix.	4.7.1.5 The TSS Designer needs to use equipment and software acceptable under current agency IT policies and procedures.
3.1.18.2	The ASCT shall fully satisfy all requirements when connected with detectors from manufacturer XX (specify required detector types).	4.7.2.1.2 Detector type (list acceptable equipment)
3.1.18.3	The ASCT shall fully satisfy all requirements when connected with XX controllers (specify controller types).	4.7.2.1.1 Controller type (list acceptable equipment)
3.1.19	Training
3.1.19.1	The vendor shall provide training on all the operations of the system.	4.8.1.1 The TSS Manager needs all staff involved in operations and maintenance to receive appropriate training.
3.1.19.2	The vendor shall provide a minimum of XX hours of training to a minimum of XX staff. (SPECIFY)	4.8.1.1 The TSS Manager needs all staff involved in operations and maintenance to receive appropriate training.
3.1.19.3	The vendor shall provide a minimum of XX training >sessions (specify how many sessions over what period).	4.8.1.1 The TSS Manager needs all staff involved in operations and maintenance to receive appropriate training.
3.1.19.4	The vendor shall provide the following training (edit as appropriate).	4.8.1.1 The TSS Manager needs all staff involved in operations and maintenance to receive appropriate training.
3.1.19.4.1	The vendor shall provide training on troubleshooting the system.	4.8.1.1 The TSS Manager needs all staff involved in operations and maintenance to receive appropriate training.
3.1.19.4.2	The vendor shall provide training on system configuration.	4.8.1.1 The TSS Manager needs all staff involved in operations and maintenance to receive appropriate training.
3.1.19.4.3	The vendor shall provide training on administration of the system.	4.8.1.1 The TSS Manager needs all staff involved in operations and maintenance to receive appropriate training.
3.1.19.4.4	The vendor shall provide training on the operations of the adaptive system.	4.8.2.1 The TSS Manager needs [Specify staff] involved in operations and maintenance of the adaptive system to receive appropriate training.
3.1.19.4.5	The vendor shall provide training on the operations of the automated traffic signal performance measurement and monitoring.	4.8.3.1 The TSS Manager needs [Specify staff] involved in operations and maintenance of the automated signal performance measurement system to receive appropriate training.
3.1.19.4.6	The vendor shall provide training on system calibration.	4.8.1.1 The TSS Manager needs all staff involved in operations and maintenance to receive appropriate training.
3.1.19.4.7	The vendor's training delivery shall include: printed course materials and references, electronic copies of presentations and references.	4.8.1.1 The TSS Manager needs all staff involved in operations and maintenance to receive appropriate training.
3.1.19.4.8	The vendor's training shall be delivered at (SPECIFY location for training).	4.8.1.1 The TSS Manager needs all staff involved in operations and maintenance to receive appropriate training.
3.1.20	Maintenance, Support and Warranty
3.1.20.1	The Maintenance Vendor shall provide maintenance according to a separate maintenance contract. That contract should identify repairs necessary to preserve requirements fulfillment, responsiveness in effecting those repairs, and all requirements on the maintenance provider while performing the repairs.	4.10.1 The TSS Manager needs the system to fulfill all the requirements for the life of the system. The agency therefore needs the system to be maintained to repair faults that are not defects in materials and workmanship.
3.1.20.2	The Vendor shall provide routine updates to the software and software environment necessary to preserve the fulfillment of requirements for a period of XX years. Preservation of requirements fulfillment especially includes all IT management requirements as previously identified.	4.10.2 The agency needs the system to fulfill all requirements for the life of the system. The agency therefore needs support to keep software and software environment updated as necessary to prevent requirements no longer being fulfilled.
3.1.20.3	The Vendor shall warrant the system to be free of defects in materials and workmanship for a period of XX years. Warranty is defined as correcting defects in materials and workmanship (subject to other language included in the purchase documents). Defect is defined as any circumstance in which the material does not perform according to its specification.	4.10.3 The agency needs the system to fulfill all requirements for the life of the system. The agency therefore needs the system to remain free of defects in materials and workmanship that result in requirements no longer being fulfilled.

Previous | Next