|
On-board EV En Route Support Equipment Package
|
![Architecture Geographic Scope](../../images/lufkin.jpg) |
Description:
|
On-board systems for gathering of dispatch and routing information for emergency vehicle personnel, vehicle tracking, communications with care facilities, and signal preemption via short range communication directly with traffic control equipment at the roadside.
|
Included in:
|
City of Livingston Fire/EMS Vehicles
City of Lufkin Fire/EMS Vehicles
City of Lufkin Police Vehicles
City of Nacogdoches Fire Vehicles
Private Ambulance Vehicle
|
Functional Requirements:
|
1 | The emergency vehicle, including roadway service patrols, shall compute the location of the emergency vehicle based on inputs from a vehicle location determination function. |
2 | The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the center for emergency management and dispatch. |
3 | The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when dispatched to a scene. |
4 | The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for emergency dispatch updates. |
5 | The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal. |
6 | The emergency vehicle shall provide the personnel on-board with dispatch information, including incident type and location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene. |
7 | The emergency vehicle shall send patient status information to the care facility along with a request for further information. |
8 | The emergency vehicle shall forward care facility status information to emergency vehicle personnel, including the location, specialized services, quality of care, waiting time, number of rooms available, and emergency room status of hospitals or emergency care providers. |
| |
|
User Service Requirements (fully or partially addressed):
|
1.5 | TRAVELER SERVICES INFORMATION |
1.5.2 | TSI shall include an Information Access function that allows travelers to access the available information. |
1.5.2.2 | Information Access shall provide the capability for travelers and centers to request and receive information about the location of facilities and the quality of specific services provided in an area to include but, not be limited to, the following: |
1.5.2.2(i) | Local care facility information. |
5.0 | EMERGENCY MANAGEMENT |
5.2 | EMERGENCY VEHICLE MANAGEMENT |
5.2.1 | EVM Service shall include an Emergency Vehicle Fleet Management System. |
5.2.1.1 | Emergency Vehicle Fleet Management System shall maintain the availability status of relevant emergency vehicles. |
5.2.2 | EVM Service shall include a Route Guidance System. |
5.2.2.2 | Route Guidance System shall advise emergency response vehicles of appropriate routes. |
8.0 | MAINTENANCE AND CONSTRUCTION MANAGEMENT |
8.1 | MAINTENANCE AND CONSTRUCTION OPERATIONS |
8.1.1 | Maintenance and Construction Operations shall provide a Maintenance Vehicle Fleet Management (MVFM) function to schedule and dispatch, monitor and track location, and monitor operational condition and maintenance requirements of public and contracted fleets of maintenance, construction, and specialized service vehicles. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Vehicle Maintenance Crews, Equipment Maintenance Crews, Weather Services Organizations, and Information Service Providers. |
8.1.1.1 | MVFM shall be capable of monitoring and tracking the locations of public and contracted fleets of maintenance, construction, and specialized service vehicles to provide current location and status information. |
8.1.1.1.1 | MVFM shall be capable of monitoring and tracking the locations of fleets of maintenance, construction, and specialized service vehicles, including but not limited to: |
8.1.1.1.1(e) | Roadway service patrols |
| |
|
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture.
Consult the National
ITS Architecture web site for more information.
|
|