Model Systems Engineering Documents for Adaptive Signal Control Technology (ASCT) Systems

Appendix D. System Requirements Table of Sample Requirements

4.2.0-1

The system operator needs to eventually adaptively control up to XXX signals, up to XXX miles from the TMC (or specified location).

4.2.0-2

The system operator needs to be able to adaptively control up to XX independent groups of signals

4.2.0-3

The system operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.

4.2.0-2

The system operator needs to be able to adaptively control up to XX independent groups of signals

4.2.0-2

The system operator needs to be able to adaptively control up to XX independent groups of signals

4.2.0-3

The system operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.

4.2.0-2

The system operator needs to be able to adaptively control up to XX independent groups of signals

4.2.0-3

The system operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.

4.2.0-3

The system operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.

4.2.0-3

The system operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.

4.2.0-3

The system operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.

4.7.0-1

The system 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.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.7.0-3

The system operator needs to over-ride adaptive operation.

4.7.0-3

The system operator needs to over-ride adaptive operation.

4.7.0-2

The system operator needs to schedule pre-determined operation by time of day.

4.7.0-3

The system operator needs to over-ride adaptive operation.

4.17.0-2

The system 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).

4.1.0-1.0-1

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-3

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-3

The system operator needs to change the operational strategy (for example, from smooth flow to maximizing throughput or managing queues) based on changing traffic conditions.

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-3

The system operator needs to change the operational strategy (for example, from smooth flow to maximizing throughput or managing queues) based on changing traffic conditions.

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-3

The system operator needs to change the operational strategy (for example, from smooth flow to maximizing throughput or managing queues) based on changing traffic conditions.

4.1.0-1.0-3

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-3

The system operator needs to change the operational strategy (for example, from smooth flow to maximizing throughput or managing queues) based on changing traffic conditions.

4.1.0-1.0-2

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-3

The system operator needs to change the operational strategy (for example, from smooth flow to maximizing throughput or managing queues) based on changing traffic conditions.

4.1.0-1.0-3

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-6

• At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).

4.1.0-1.0-3

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-6

• At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).

4.1.0-1.0-3

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-6

• At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).

4.1.0-1.0-3

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-6

• At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).

4.1.0-1.0-3

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-6

• At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).

4.1.0-4

The system operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The 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 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.1.0-1.0-5.

4.1.0-4

The system operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The 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 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.1.0-1.0-5.

4.1.0-1.0-1

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-2

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-4

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-8

The system operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.

4.1.0-8

The system operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.

4.1.0-8

The system operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.

4.1.0-8

The system operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.

4.1.0-8

The system operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.

4.1.0-8

The system operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.

4.1.0-8

The system operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.

4.1.0-8

The system operator needs to designate the coordinated route based on traffic conditions and the selected operational strategy.

4.1.0-9

The system operator needs to set signal timing parameters (such as minimum green, maximum green and extension time) to comply with agency policies.

4.9.0-1.0-14

• Protected/permissive phasing and alternate left turn phase sequences.

4.9.0-1.0-14

• Protected/permissive phasing and alternate left turn phase sequences.

4.9.0-1.0-6

• Prevent one or more phases being skipped under certain traffic conditions or signal states.

4.9.0-1.0-6

• Prevent one or more phases being skipped under certain traffic conditions or signal states.

4.17.0-2

The system 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).

4.9.0-1.0-6

• Prevent one or more phases being skipped under certain traffic conditions or signal states.

4.9.0-1.0-5

• Allow one or more phases to be omitted (disabled) under certain traffic conditions or signal states.

4.9.0-1.0-5

• Allow one or more phases to be omitted (disabled) under certain traffic conditions or signal states.

4.9.0-1.0-5

• Allow one or more phases to be omitted (disabled) under certain traffic conditions or signal states.

4.17.0-2

The system 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).

4.9.0-1.0-5

• Allow one or more phases to be omitted (disabled) under certain traffic conditions or signal states.

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.9.0-1.0-10

• Allow the operator to specify which phase receives unused time from a preceding phase

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.

• Allow the operator to specify which phase receives unused time from a preceding phase

4.1.0-7

The system 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.

4.1.0-1.0-4

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-5

• Manage the locations of queues within the network

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-4

The system operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The 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 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.1.0-1.0-5.

4.5.0-1

The system operator needs to detect queues from outside the system and modify the ASCT operation to accommodate the queuing.

4.5.0-2

The system operator needs to detect queues within the system's boundaries and modify the ASCT operation to accommodate the queuing.

4.5.0-3

The system operator needs to detect queues propagating outside its boundaries from within the ASCT boundaries, and modify its operation to accommodate the queuing.

4.5.0-4

The system operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.

4.5.0-5

The system operator needs to prevent queues forming at user-specified locations.

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-5

• Manage the locations of queues within the network

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-4

The system operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The 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 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.1.0-1.0-5.

4.5.0-1

The system operator needs to detect queues from outside the system and modify the ASCT operation to accommodate the queuing.

4.5.0-2

The system operator needs to detect queues within the system's boundaries and modify the ASCT operation to accommodate the queuing.

4.5.0-3

The system operator needs to detect queues propagating outside its boundaries from within the ASCT boundaries, and modify its operation to accommodate the queuing.

4.5.0-4

The system operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.

4.5.0-5

The system operator needs to prevent queues forming at user-specified locations.

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-5

• Manage the locations of queues within the network

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-4

The system operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The 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 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.1.0-1.0-5.

4.5.0-1

The system operator needs to detect queues from outside the system and modify the ASCT operation to accommodate the queuing.

4.5.0-2

The system operator needs to detect queues within the system's boundaries and modify the ASCT operation to accommodate the queuing.

4.5.0-3

The system operator needs to detect queues propagating outside its boundaries from within the ASCT boundaries, and modify its operation to accommodate the queuing.

4.5.0-4

The system operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.

4.5.0-5

The system operator needs to prevent queues forming at user-specified locations.

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-5

• Manage the locations of queues within the network

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-4

The system operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The 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 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.1.0-1.0-5.

4.5.0-4

The system operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.

4.5.0-5

The system operator needs to prevent queues forming at user-specified locations.

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-5

• Manage the locations of queues within the network

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.5.0-4

The system operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.

4.5.0-5

The system operator needs to prevent queues forming at user-specified locations.

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-5

• Manage the locations of queues within the network

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.5.0-4

The system operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.

4.5.0-5

The system operator needs to prevent queues forming at user-specified locations.

4.5.0-4

The system operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.

4.5.0-5

The system operator needs to prevent queues forming at user-specified locations.

• Manage the locations of queues within the network

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-2

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-3

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)4.1.0-1.0-4

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-5

• Manage the locations of queues within the network

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-4

The system operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The 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 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.1.0-1.0-5.

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-2

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-4

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

The system 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 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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 2.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 both groups when the vendor is given the choice of supplying one type of adaptive operation or the other.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Maximize the throughput on coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Provide smooth flow along coordinated routes

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

• Manage the lengths of queues

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-5

The system 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 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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 2.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.)

4.1.0-1.0-6

• At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-6

• At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).

4.1.0-1.0-3

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-6

• At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).

• Distribute phase times in an equitable fashion

Note to user when selecting these requirements:

Select from requirements in the 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-1.0-6

• At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).

4.1.0-1.0-6

• At an isolated intersection, optimize operation with a minimum of phase failures (based on the optimization objectives).

4.1.0-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 that phase-based systems do not explicitly calculate cycle, offset and split at all intersections.

4.1.0-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 that phase-based systems do not explicitly calculate cycle, offset and split at all intersections.

4.1.0-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 that phase-based systems do not explicitly calculate cycle, offset and split at all intersections.

4.1.0-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 that phase-based systems do not explicitly calculate cycle, offset and split at all intersections.

4.1.0-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 that phase-based systems do not explicitly calculate cycle, offset and split at all intersections.

The system 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 2.2 group when sequence-based systems are allowed (sequence-based systems explicitly calculate cycle, offset, and split).

Select from requirements in the 2.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.)

4.1.0-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 that phase-based systems do not explicitly calculate cycle, offset and split at all intersections.

4.8.0-1

The system operator needs to modify the ASCT operation to closely follow changes in traffic conditions.

4.8.0-1

The system operator needs to modify the ASCT operation to closely follow changes in traffic conditions.

4.8.0-1

The system operator needs to modify the ASCT operation to closely follow changes in traffic conditions.

4.8.0-2

The system operator needs to constrain the selection of cycle lengths to those that provide acceptable operations, such as when resonant progression solutions are desired.

4.8.0-3

4.8.0-2

The system operator needs to constrain the selection of cycle lengths to those that provide acceptable operations, such as when resonant progression solutions are desired.

4.8.0-2

The system operator needs to constrain the selection of cycle lengths to those that provide acceptable operations, such as when resonant progression solutions are desired.

The 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 architecture. Interface requirements include:

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

4.3.0-1

The system operator needs to adaptively control signals operated by (specify jurisdictions).

4.3.0-2

The system operator needs to send data to another system that would allow the other system to coordinate with the ASCT system.

4.3.0-4

The system operator needs to receive data from another system that will allow the ASCT system to coordinate its operation with the adjacent system.

4.11.0-5

The system operator needs to report performance data in real time to (specify external system).

4.17.0-2

The system 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).

4.3.0-2

The system operator needs to send data to another system that would allow the other system to coordinate with the ASCT system.

4.11.0-5

The system operator needs to report performance data in real time to (specify external system).

4.3.0-2

The system operator needs to send data to another system that would allow the other system to coordinate with the ASCT system.

4.11.0-1

The agency needs the (specify external decision support system) to be able to monitor the ASCT system automatically.

4.3.0-2

The system operator needs to send data to another system that would allow the other system to coordinate with the ASCT system.

4.11.0-5

The system operator needs to report performance data in real time to (specify external system).

4.17.0-2

The system 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).

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.17.0-2

The system 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).

4.3.0-4

The system operator needs to receive data from another system that will allow the ASCT system to coordinate its operation with the adjacent system.

4.3.0-6

The system operator needs to detect traffic approaching from a neighboring system and coordinate the ASCT operation with the adjacent system.

4.17.0-2

The system 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).

4.3.0-4

The system operator needs to receive data from another system that will allow the ASCT system to coordinate its operation with the adjacent system.

4.3.0-6

The system operator needs to detect traffic approaching from a neighboring system and coordinate the ASCT operation with the adjacent system.

4.3.0-5

The system operator needs to constrain the adaptive system to operate a cycle length compatible with the crossing arterial.

4.3.0-4

The system operator needs to receive data from another system that will allow the ASCT system to coordinate its operation with the adjacent system.

4.3.0-3

The system 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.)

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Local access to the ASCT.

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Remote access to the ASCT.

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• System monitoring.

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• System manual override.

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Development

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Operations

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• User login

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• User password

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Administration of the system

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Signal controller group access

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Access to classes of equipment

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Access to equipment by jurisdiction

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Output activation

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• System parameters

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Report generation

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Configuration

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Security alerts

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Security logging

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Security reporting

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Database

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Signal controller

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

4.10.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

• Agency TMC

4.10.0-1.0-1

• Agency TMC

• Maintenance facility

4.10.0-1.0-2

• Maintenance facility

• Agency LAN or WAN

4.10.0-1.0-3

• Workstations on agency LAN or WAN located at (specify)

• Other agency TMC

4.10.0-1.0-4

• Other agency's TMC (specify)

• Local controller cabinets

4.10.0-1.0-5

• Local controller cabinets

• Maintenance vehicles

4.10.0-1.0-6

• Maintenance vehicles

• Remote locations via internet

4.10.0-1.0-7

• Remote locations (specify)

4.4.0-1

The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

4.10.0-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.

4.11.0-6

The system operator needs to be able to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.

4.11.0-6

The system operator needs to be able to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.

4.11.0-6

The system operator needs to be able to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.

4.11.0-6

The system operator needs to be able to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.

4.11.0-6

The system operator needs to be able to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.

4.11.0-6

The system operator needs to be able to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.

4.11.0-6

The system operator needs to be able to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.

4.11.0-6

The system operator needs to be able to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.

4.11.0-6

The system operator needs to be able to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.

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

4.11.0-4

The system 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).

4.11.0-4

The system 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).

4.11.0-2

The system operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.

4.11.0-3

The system operator needs to store and report data that can be used to measure traffic performance under adaptive control.

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.11.0-7

Have the ability to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.

4.11.0-2

The system operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.

4.11.0-3

The system operator needs to store and report data that can be used to measure traffic performance under adaptive control.

4.11.0-4

The system 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).

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

4.11.0-4

The system 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).

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

4.11.0-7

Have the ability to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.

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

Have the ability to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.

4.11.0-4

The system 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).

4.11.0-7

Have the ability to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.

• volume
• occupancy
• queue length

4.11.0-2

The system operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.

4.11.0-3

The system operator needs to store and report data that can be used to measure traffic performance under adaptive control.

4.9.0-1.0-1

• Service a phase more than once per cycle

4.9.0-1.0-2

• Operate at least XX overlap phases

4.9.0-1.0-3

• Operate four rings, 16 phases and up to three phases per ring (Edit to suit your needs).

4.9.0-1.0-3

• Operate four rings, 16 phases and up to three phases per ring (Edit to suit your needs).

4.9.0-1.0-3

• Operate four rings, 16 phases and up to three phases per ring (Edit to suit your needs).

4.1.0-6

The system operator needs to modify the sequence of phases to support the various operational strategies.

4.9.0-1.0-4

• Permit different phase sequences under different traffic conditions

4.1.0-6

The system operator needs to modify the sequence of phases to support the various operational strategies.

4.9.0-1.0-4

• Permit different phase sequences under different traffic conditions

4.1.0-6

The system operator needs to modify the sequence of phases to support the various operational strategies.

4.9.0-1.0-4

• Permit different phase sequences under different traffic conditions

4.1.0-6

The system operator needs to modify the sequence of phases to support the various operational strategies.

4.9.0-1.0-4

• Permit different phase sequences under different traffic conditions

4.1.0-6

The system operator needs to modify the sequence of phases to support the various operational strategies.

4.1.0-6

The system operator needs to modify the sequence of phases to support the various operational strategies.

4.17.0-2

The system 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).

4.1.0-6

The system operator needs to modify the sequence of phases to support the various operational strategies.

4.9.0-1.0-9

• Allow any phase to be designated as the coordinated phase

4.9.0-1.0-12

Allow the coordinated phase to terminate early under prescribed traffic conditions

4.9.0-1.0-15

Use flashing yellow arrow to control permissive left turns and right turns.

4.9.0-1.0-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.

4.9.0-1.0-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.

4.9.0-1.0-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.)

• Accommodate the following custom features used by this agency (describe the features)

• Allow detector logic at an intersection to be varied depending on local signal states

4.6.0-5

The system operator needs to accommodate early start of walk and exclusive pedestrian phases.

4.6.0-2

The system 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.)

4.6.0-3

The system 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.)

4.6.0-1

The system operator needs to accommodate infrequent pedestrian operation and then adaptively recover. (This is appropriate for rare pedestrian calls.)

4.6.0-5

The system operator needs to accommodate early start of walk and exclusive pedestrian phases.

4.6.0-3

The system 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.)

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

• Allow flexible timing of non-coordinated phases (such as late start of a phase) while maintaining coordination

4.6.0-3

The system 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.)

4.6.0-3

The system 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.)

4.9.0-1.0-17

• Use negative pedestrian phasing to prevent an overlap conflicting with a pedestrian walk/don't walk

• 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.

4.17.0-1

The system 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

4.17.0-1

The system 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

4.17.0-1

The system 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

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

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

4.13.0-1

The system operator needs to accommodate railroad and light rail preemption (explain further)

4.13.0-2

The system operator needs to accommodate emergency vehicle preemption (explain further)

4.13.0-1

The system operator needs to accommodate railroad and light rail preemption (explain further)

4.13.0-1

The system operator needs to accommodate railroad and light rail preemption (explain further)

4.13.0-2

The system operator needs to accommodate emergency vehicle preemption (explain further)

4.13.0-1

The system operator needs to accommodate railroad and light rail preemption (explain further)

4.13.0-2

The system operator needs to accommodate emergency vehicle preemption (explain further)

4.13.0-1

The system operator needs to accommodate railroad and light rail preemption (explain further)

4.13.0-2

The system operator needs to accommodate emergency vehicle preemption (explain further)

4.13.0-1

The system operator needs to accommodate railroad and light rail preemption (explain further)

4.13.0-2

4.13.0-1

The system operator needs to accommodate railroad and light rail preemption (explain further)

4.13.0-2

The system operator needs to accommodate emergency vehicle preemption (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

• LRT only phases

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

• Bus only phases

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

The ASCT shall accept a transit priority call from:

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

4.13.0-3

The system operator needs to accommodate bus and light rail transit signal priority (explain further)

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

• Data from a user-specified alternate detector.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

• Stored historical data from the failed detector.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.12.0-1

The system operator needs to immediately notify maintenance and operations staff of alarms and alerts.

4.12.0-2

The system operator needs to immediately and automatically pass alarms and alerts to the (specify external system).

4.12.0-3

The system operator needs to maintain a complete log of alarms and failure events.

4.12.0-3

The system operator needs to maintain a complete log of alarms and failure events.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.12.0-1

The system operator needs to immediately notify maintenance and operations staff of alarms and alerts.

4.12.0-2

The system operator needs to immediately and automatically pass alarms and alerts to the (specify external system).

4.12.0-1

The system operator needs to immediately notify maintenance and operations staff of alarms and alerts.

4.12.0-2

The system operator needs to immediately and automatically pass alarms and alerts to the (specify external system).

4.12.0-3

The system operator needs to maintain a complete log of alarms and failure events.

4.12.0-3

The system operator needs to maintain a complete log of alarms and failure events.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

4.12.0-1

The system operator needs to immediately notify maintenance and operations staff of alarms and alerts.

4.12.0-2

The system operator needs to immediately and automatically pass alarms and alerts to the (specify external system).

4.14.0-1

The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and software failure.

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

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

4.15.0-1.0-2

• Detector type (list acceptable equipment)

4.15.0-1.0-1

• Controller type (list acceptable equipment)

4.16.0-1

The agency needs all staff involved in operation and maintenance to receive appropriate training.

4.16.0-1

The agency needs all staff involved in operation and maintenance to receive appropriate training.

4.16.0-1

The agency needs all staff involved in operation and maintenance to receive appropriate training.

4.16.0-1

The agency needs all staff involved in operation and maintenance to receive appropriate training.

4.16.0-1

The agency needs all staff involved in operation and maintenance to receive appropriate training.

4.16.0-1

The agency needs all staff involved in operation and maintenance to receive appropriate training.

4.16.0-1

The agency needs all staff involved in operation and maintenance to receive appropriate training.

4.16.0-1

The agency needs all staff involved in operation and maintenance to receive appropriate training.

4.16.0-1

The agency needs all staff involved in operation and maintenance to receive appropriate training.

4.16.0-1

The agency needs all staff involved in operation and maintenance to receive appropriate training.

4.16.0-1

The agency needs all staff involved in operation and maintenance to receive appropriate training.

4.16.0-2

The agency needs the system to fulfill all 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.

4.16.0-4

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.

4.16.0-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.

4.17.0-1

The system 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

4.17.0-1

The system 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

4.11.0-2

The system operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.

4.11.0-2

The system operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.

4.11.0-7

Have the ability to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.

4.11.0-2

The system operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.

4.11.0-7

Have the ability to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.

4.11.0-7

Have the ability to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.

4.11.0-7

Have the ability to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.

4.11.0-7

Have the ability to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.

4.11.0-7

Have the ability to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.