Section B: System Requirements
System requirements for EVP and TP fall into the following major categories: accountability, interoperability, flexibility/adaptability, maintainability, and control of operations. This section should be completed first for EVP and then a second time for TP, on the assumption that both EVP and TP will co-exist in a single system. If only EVP is being considered and TP is not of interest (or vice versa), then this section only needs to be completed once for the preferential signal strategy being considered.
Accountability
Some system planners and implementers claim that system users should be held accountable for their use of the system.
1) Will a detailed record be kept and easily accessible that could be used to determine which specific individual or vehicle triggered the system in a specific instance?
2) Will there be technical “interlocks” that will determine whether the system can be used (e.g. linking use of the system to emergency backup plans)?
⋄Yes (Can you list specific interlocks that will be used?)
|
⋄No
|
3) Do you have a clear written or proposed policy on WHO can use the system (e.g if EVP is being considered, do only fire and EMS personnel have the authority to use the system, and in the case of TP do only selected routes at certain times of day have the authority to use the system)
4) Do you have a clear written policy or proposed policy on under what situations the system can be triggered)?
5) Do you have a clear written policy or proposed policy governing installation of the system at a specific intersection?
NOTE: It is not always appropriate to have these policies in place prior to approaching stakeholders, however, if you have answered NO to any of the above some thought should be given to these matters before approaching other stakeholders.
Dostları ilə paylaş: |