New Jersey Statewide ITS Architecture
Menu
Region Home
Stakeholders
Inventory by Stakeholder
Inventory by Entity
Sausage Diagram
Market Packages by Functional Area
Market Packages by Stakeholder
Market Package Descriptions
Equipment Package Descriptions
Architecture Flow Descriptions
Project Documents
Send Your Comments

 

Equipment Package: TMC Incident Detection

Description: This equipment package provides the capability to traffic managers to detect and verify incidents. This capability includes analyzing and reducing the collected data from traffic surveillance equipment, monitoring external alerting and advisory and incident reporting systems, collecting special event information, and monitoring for incidents and hazardous conditions through available sensor and surveillance systems.
Included In: Atlantic City Area Joint Operations Center
DRJTBC Facility Operations Center
National Park Service Management Center
NJDOT STOC
NJDOT TEOC
NJDOT TOC Central
NJDOT TOC North
NJDOT TOC South
NJSP/NJDOT Statewide Dispatch Center
NJTA Parkway Division TOC
NJTA Turnpike TOC
PANYNJ Port Commerce Operations Centers
RIMIS IEN
SJTA TOC
TRANSCOM Communications Center Servers
Processes: 1.1.4.1 - Retrieve Traffic Data
1.1.4.2 - Provide Traffic Operations Personnel Traffic Data Interface
1.3.1.1 - Analyze Traffic Data for Incidents
1.3.1.2 - Maintain Static Data for Incident Management
1.3.2.1 - Store Possible Incident Data
1.3.2.2 - Review and Classify Possible Incidents
1.3.2.3 - Review and Classify Planned Events
1.3.2.4 - Provide Planned Events Store Interface
1.3.2.5 - Provide Current Incidents Store Interface
1.3.4.2 - Provide Traffic Operations Personnel Incident Data Interface
User Service Requirements: 1.0 - TRAVEL AND TRAFFIC MANAGEMENT
1.6 - TRAFFIC CONTROL
1.6.0 - ITS shall include a Traffic Control (TC) function. Traffic Control provides the capability to efficiently manage the movement of traffic on streets and highways. Four functions are provided, which are, (1) Traffic Flow Optimization, (2) Traffic Surveillance, (3) Control, and (4) Provide Information. This will also include control of network signal systems with eventual integration of freeway control.
1.6.1 - TC shall include a Traffic Flow Optimization function to provide the capability to optimize traffic flow.
1.6.1.7 - Implementation of the Control function shall include strategies that account for at least the following:
1.6.1.7(a) - Human factors.
1.6.3 - TC shall include a Device Control function.
1.6.3.4 - Device Control shall communicate control data to the following devices.
1.6.3.4(e) - Human operator support.
1.6.3.4.1 - Traffic Surveillance shall include a data process function to process the traffic data which are acquired.
1.6.4 - Device Control shall provide traffic control information to other elements of the ITS, including but not limited to the following:
1.6.4(a) - In-vehicle navigation.
1.6.4(b) - Trip planning.
1.6.4(c) - Routing systems.
1.6.4(d) - Fleet management systems.
1.7 - INCIDENT MANAGEMENT
1.7.0 - ITS shall include an Incident Management (IM) function. Incident Management will identify incidents, formulate response actions, and support initiation and ongoing coordination of those response actions. Four major functions are provided, which are, (1) Incidents Identification, (2) Response Formulation, (3) Response Implementation, and (4) Predict Hazardous Conditions.
1.7.1 - Incident Management shall provide an Incident Identification function to identify incidents.
1.7.1.1 - The Incident Identification function shall include the capability to identify predicted incidents.
1.7.1.1.1 - The Incident Identification function shall use information from the following types of sources, where available, to identify predicted incidents:
1.7.1.1.1(a) - Traffic flow sensors.
1.7.1.1.1(b) - Environmental sensors.
1.7.1.1.1(c) - Public safety sources.
1.7.1.1.1(d) - Media sources.
1.7.1.1.1(e) - Weather information sources.
1.7.1.1.1(f) - Transportation providers.
1.7.1.1.1(g) - Sponsors of special events.
1.7.1.1.1(h) - Hazardous condition prediction algorithms.
1.7.1.1.2 - The Incident Identification function shall determine at least the following characteristics of each predicted incident:
1.7.1.1.2(a) - Type (including Terrain Hazards).
1.7.1.1.2(b) - Extent.
1.7.1.1.2(c) - Severity.
1.7.1.1.2(d) - Location.
1.7.1.1.2(e) - Expected duration.
1.7.1.1.3 - The Incident Identification function shall determine the expected traffic flow impact of each predicted incident.
1.7.1.2 - The Incident Identification function shall include the capability to identify existing (both planned and unplanned) incidents.
1.7.1.2.1 - The Incident Identification function shall use information from the following types of sources, where available, to identify existing incidents:
1.7.1.2.1(a) - Traffic flow sensors.
1.7.1.2.1(b) - Environmental sensors.
1.7.1.2.1(c) - Public safety sources.
1.7.1.2.1(d) - Media sources.
1.7.1.2.1(e) - Weather information sources.
1.7.1.2.1(f) - Transportation providers.
1.7.1.2.1(g) - Travelers.
1.7.1.2.2 - The Incident Identification function shall determine and continuously monitor at least the following characteristics of each existing incident:
1.7.1.2.2(a) - Type (including Terrain Hazards).
1.7.1.2.2(b) - Extent.
1.7.1.2.2(c) - Severity.
1.7.1.2.2(d) - Location.
1.7.1.2.3 - The Incident Identification function shall determine and continuously monitor the current and expected traffic flow impact of each existing incident.
1.7.2 - IM shall provide a Response Formulation function to formulate appropriate response actions to each identified incident and revise those actions when necessary.
1.7.2.1 - The Response Formulation function shall propose and facilitate the appropriate scheduling of those predicted incidents that can be scheduled to minimize incident potential, incident impacts, and/or the resources required for incident management.
1.7.3 - IM shall include a Response Implementation function to provide the services to implement a response coordinated with all appropriate agencies.
1.7.3.2 - The Response Implementation function shall provide a link between Incident Management and all other user services necessary to implement incident response actions.
1.7.4 - IM shall provide the capability to Predict Hazardous Conditions, including the time and location of hazardous conditions that may cause an incident.
5.0 - EMERGENCY MANAGEMENT
5.1 - EMERGENCY NOTIFICATION AND PERSONAL SECURITY
5.1.3 - ENPS shall include a Remote Security and Emergency Monitoring (RSEM) function to create an environment of safety in secure areas.
5.1.3.4 - RSEM shall include a Monitor Alert Levels (MAL) function.
5.1.3.4.3 - MAL shall increase system preparedness as the likelihood of an incident increases, including:
5.1.3.5 - RSEM shall include a Physical Security System (PSS) function.
5.1.3.5.2 - PSS shall allow system operators to monitor and control operation of the physical security system devices, including operator override.
5.1.3.5.3 - PSS shall provide current status of the system including readiness and activation to operators.
5.1.5 - ENPS shall include a Protect Sensitive Traveler Information (PSTI) function to inhibit distribution of traveler information that is deemed to be sensitive.
5.1.5.1 - PSTI shall notify transportation operators and information providers when access to information from ITS surveillance and sensor systems must be restricted.
5.1.5.2 - The PSTI notification shall identify the geographic area, time, specific devices, and/or other information necessary to determine the traveler information that must be protected.
5.1.5.3 - PSTI shall restrict access to traveler information for the affected area until access restrictions are removed.
5.1.5.4 - PSTI shall notify transportation operators and information providers when traveler information access restrictions are removed.
5.3 - DISASTER RESPONSE AND EVACUATION
5.3.0 - ITS shall provide a Disaster Response and Evacuation (DRE) function that provides for effective, coordinated management of the surface transportation system during all types of disasters including natural disasters (hurricanes, earthquakes, floods, severe winter storms, tsunamis, etc.), terrorist acts, and other catastrophic events (e.g., nuclear power plant disasters). Two primary subservices are provided: (1) Disaster Response and (2) Evacuation Coordination. The Disaster Response Subservice provides support for planning, transportation management, resource sharing, and information coordination between transportation agencies and principal responding agencies (emergency management, public safety, and other allied agencies) to improve the effectiveness and safety of a disaster response. The Disaster Response Subservice consists of eight major functions: 1) Coordinate Response Plans, 2) Monitor Alert Levels, 3) Detect and Verify Emergency, 4) Assess Infrastructure Status, 5) Coordinate Response, 6) Critical Service Restoration, 7) Manage Area Transportation, and 8) Disaster Traveler Information. The Evacuation Coordination (EC) Subservice efficiently manages an evacuation and provides evacuees with the information they need during evacuation and subsequent reentry to the evacuated area. The Evacuation Coordination (EC) subservice includes four additional major functions: 9) Evacuation Planning Support, 10) Evacuation Traveler Information, 11) Evacuation Transportation Management, and 12) Evacuation Resource Sharing.
5.3.2 - Disaster Response shall provide a Monitor Alert Levels (MAL) function.
5.3.2.2 - MAL shall increase system preparedness as the alert level or the likelihood of a disaster increases, taking actions including:
5.3.2.2(c) - Review and update resource inventories
8.0 - MAINTENANCE AND CONSTRUCTION MANAGEMENT
8.1 - MAINTENANCE AND CONSTRUCTION OPERATIONS
8.1.0 - ITS shall provide Maintenance and Construction Operations (MCO) functions to support monitoring, operating, maintaining, improving and managing the physical condition of roadways, the associated infrastructure equipment, and the required resources. MCO shall focus on four major functions: 1) the Maintenance Vehicle Fleet Management function, to monitor and track locations and conditions of fleets of maintenance, construction, and specialized service vehicles; 2) the Roadway Management function, to monitor and forecast conditions and manage treatment of roadways during various travel conditions; 3) the Work Zone Management and Safety function, to support effective and efficient roadway operations during work zone activities; and 4) the Roadway Maintenance Conditions and Work Plan Dissemination function, to coordinate work plans and to communicate conditions. This User Service will utilize ITS systems and processes to support interchange of information among diverse groups of users, to improve efficiency and effectiveness of operational, maintenance, and managerial activities.
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.6 - MVFM shall be capable of providing dispatchers and operators of maintenance, construction, and specialized service vehicles with information regarding potential and actual roadway problems.
8.1.1.6.1 - MVFM shall provide information to dispatchers and vehicle operators, including but not limited to:
8.1.1.6.1(a) - Congestion
8.1.1.6.1(b) - Incidents
8.1.3 - Maintenance and Construction Operations shall provide a Work Zone Management and Safety (WZMS) function, which provides support for the effectiveness, safety, and efficiency of roadway operations during all work zone activities. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Public Safety Organizations, Information Service Providers, and Travelers.
8.1.3.2 - WZMS shall support the management of data about work zones.
8.1.3.2.4 - WZMS shall provide information on work zone activities to other agencies, including but not limited to:
8.1.3.2.4(e) - Traffic management systems
8.1.4 - Maintenance and Construction Operations shall provide a Roadway Maintenance Conditions and Work Plan Dissemination (RMCWPD) function to provide Intra- and Inter-agency coordination of work plans. This function includes interactions among Traffic Managers, Supervisors, Planning Agencies, Public Safety Organizations, and Information Service Providers.
8.1.4.1 - RMCWPD shall coordinate information on planned maintenance and construction activities, including work zone information, and unplanned remediation activities, such as inclement weather responses, so that routing, scheduling, and resource allocation can be accomplished.
8.1.4.2 - RMCWP shall support inter-agency coordination of response and scheduling of resources for significant events with broad impact, like natural disasters, major incidents, and large planned or seasonal events.
8.1.4.3 - RMCWPD shall coordinate information with other transportation agencies, including but not limited to:
8.1.4.3(d) - Traffic Management

Last updated: 02-11-05