Type: Mobility
Groups:- Public Safety
Incident Scene Pre-Arrival Staging Guidance for Emergency Responders
The Incident Scene Pre-Arrival Staging Guidance for Emergency Responders application will provide situational awareness to and coordination among emergency responders - upon dispatch, while en route to establish incident scene work zones, upon initial arrival and staging of assets, and afterward if circumstances require additional dispatch and staging. The application collects a variety of data from emergency, traffic, and maintenance centers. The application includes a vehicle and equipment staging function that supplies the en-route responders with additional information about the scene of an incident that they can use to determine where to stage personnel and equipment prior to their arrival on-scene. The application also includes a dynamic routing function which provides emergency responders with real-time navigation instructions to travel from their base to the incident scene, accounting for traffic conditions, road closures, and snowplow reports if needed. In addition the application includes an emergency responder status reporting function which continuously monitors the location of the en-route responder vehicles as well as the vehicles already on-scene. The function develops and maintains the current position of the responder's vehicles and provides updates for estimated time of arrival (ETA) to other applications.
Enterprise
This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
The enterprise diagram can be viewed in SVG or PNG format and the current format is SVG. SVG Diagrams: Installation Operations Maintenance Certification
PNG Diagrams: Installation Operations Maintenance Certification
Business Interaction Matrix:
| Incident Scene Pre-Arrival Staging Guidance for Emergency Responders Operations Stage | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Fleet-Freight Manager | Commercial Vehicle Owner | Commercial Vehicle Driver | Traffic Manager | Maint and Constr Manager | Emergency Fleet Manager | EV On-Board En Route Support Provider | Emergency Manager | Emergency Response Personnel | EV On-Board Incident Management Communication Provider | Care Facility Manager | |
| Fleet-Freight Manager | Information Provision Agreement | ||||||||||
| Commercial Vehicle Owner | Vehicle Operating Agreement | Expectation of Data Provision | Expectation of Data Provision | ||||||||
| Commercial Vehicle Driver | Vehicle Operating Agreement | ||||||||||
| Traffic Manager | Information Exchange and Action Agreement | ||||||||||
| Maint and Constr Manager | Information Provision Agreement | ||||||||||
| Emergency Fleet Manager | Application Usage Agreement | Vehicle Usage Agreement | Application Usage Agreement | Information Exchange Agreement | |||||||
| EV On-Board En Route Support Provider | Application Usage Agreement | ||||||||||
| Emergency Manager | Information Provision Agreement | Expectation of Data Provision | Information Exchange and Action Agreement | Information Provision Agreement | Information Exchange Agreement | ||||||
| Emergency Response Personnel | Expectation of Data Provision | Vehicle Usage Agreement | |||||||||
| EV On-Board Incident Management Communication Provider | Application Usage Agreement | ||||||||||
| Care Facility Manager | Information Exchange Agreement | Information Exchange Agreement | |||||||||
Includes Enterprise Objects:
| Enterprise Object | Description |
|---|---|
| Application Certification Entity | The body that determines whether an application may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with application type. For example, applications with human safety component (crash avoidance, movement assistance etc.) may have stringent requirements and extensive testing in a variety of conditions, while applications that provide strictly mobility functionality may have far less testing requirements; possibly as little as just making sure the application doesn't interfere with any other applications. |
| Care Facility Manager | The entity responsible for managing the operations of a care facility; ultimately responsible for all functions performed by that facility. |
| Commercial Vehicle Driver | The 'Commercial Vehicle Driver' represents the people that operate vehicles transporting goods, including both long haul trucks and local pick-up and delivery vans. This physical object is complementary to the Driver physical object in that it represents those interactions which are unique to Commercial Vehicle Operations. Information flowing from the Commercial Vehicle Driver includes those system inputs specific to Commercial Vehicle Operations. |
| Commercial Vehicle Manufacturer | The entity which builds commercial vehicles, including long haul trucks and local pick up and delivery vehicles. This entity is complementary to the Vehicle Manufacturer entity in that it represents those aspects of vehicle manufacture which are unique to commercial vehicles. |
| Commercial Vehicle OBE Manufacturer | The Commercial Vehicle OBE Manufacturer is the provider of the commercial vehicle on-board equipment. This entity may design and build the OBE, or may integrate other components to form the OBE, or may use some combination of approaches to provide the on-board equipment. Since the OBE could be aftermarket, retrofit, built-in or nomadic, this entity is the one that builds whatever that-is. In some cases it may be a smart phone manufacturer, or in others a top tier parts supplier, or any other entity in the production chain, depending on the device and commercial vehicle in question. |
| Commercial Vehicle Owner | The entity that owns the commercial vehicle. This entity is complementary to the Vehicle Owner in that it represents those aspects of ownership which are unique to commercial vehicles. |
| CV On-Board Cargo Monitoring Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| CV On-Board Cargo Monitoring Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| CV On-Board Cargo Monitoring Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Device Certification Entity | The body that determines whether a device may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device type. |
| Emergency Commercial Vehicle Response Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Emergency Commercial Vehicle Response Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Emergency Commercial Vehicle Response Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Emergency Dispatch Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Emergency Dispatch Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Emergency Dispatch Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Emergency Environmental Monitoring Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Emergency Environmental Monitoring Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Emergency Environmental Monitoring Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Emergency Fleet Manager | The entity that controls emergency vehicles and provides them for use in incident response. |
| Emergency Incident Command Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Emergency Incident Command Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Emergency Incident Command Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Emergency Manager | The "Emergency Manager" represents agencies charged with incident management, disaster response, and transportation environment security. |
| Emergency Response Personnel | "Emergency Personnel" represents personnel that are responsible for police, fire, emergency medical services, towing, service patrols, and other special response team (e.g., hazardous material clean-up) activities at an incident site. These personnel are associated with the Emergency Vehicle during dispatch to the incident site, but often work independently of the Emergency Vehicle while providing their incident response services. Emergency personnel may include an Officer in Charge (OIC) and a crew. When managing an incident following standard Incident Command System practices, the on-site emergency personnel form an organizational structure under the auspices of an Incident Commander. |
| Emergency Routing Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Emergency Routing Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Emergency Routing Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Emergency Vehicle Manufacturer | The entity that builds, assembles, verifies and validates the Emergency Vehicle in which the Emergency Vehicle OBE will eventually operate. |
| Emergency Vehicle OBE Manufacturer | The entity that builds, assembles, verifies and validates the Emergency Vehicle OBE. This can be an OEM-equipped OBE, retrofit or aftermarket equipment. |
| EV On-Board En Route Support Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| EV On-Board En Route Support Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| EV On-Board En Route Support Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| EV On-Board Incident Management Communication Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| EV On-Board Incident Management Communication Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| EV On-Board Incident Management Communication Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Federal Regulatory | Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation. |
| Fleet-Freight Manager | The 'Fleet-Freight Manager' represents the people that are responsible for the dispatching and management of Commercial Vehicle fleets (e.g. traditional Fleet Managers) and Freight Equipment assets. It may be many people in a large tracking organization or a single person (owner driver) in the case of single vehicle fleets. The Fleet-Freight Manager provides instructions and coordination for Commercial Vehicles and Freight Equipment and receives the status of the vehicles and freight equipment in the fleet that they manage. |
| Maint and Constr Manager | The organization responsible for maintenance and construction activities. |
| MCM Environmental Information Processing Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| MCM Environmental Information Processing Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| MCM Environmental Information Processing Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| MCM Incident Management Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| MCM Incident Management Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| MCM Incident Management Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| MCM Work Activity Coordination Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| MCM Work Activity Coordination Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| MCM Work Activity Coordination Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| State Regulatory | State regulatory bodies that have legal authority to control and/or provide input to policies regulating vehicles, transportation infrastructure and operations. This includes entities like Departments of Motor Vehicles, property tax authorities and tolling agencies. |
| TMC Incident Dispatch Coordination/Communication Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| TMC Incident Dispatch Coordination/Communication Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| TMC Incident Dispatch Coordination/Communication Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Traffic Manager | The entity responsible for the management of traffic, both freeway and arterial. |
| Vehicle Owner | The individual, group of individuals or corporate entity that is identified as the registered owner of the Vehicle under state law. |
Includes Resources:
| Resource | Description |
|---|---|
| Application Component Certification Requirements | The requirements that define the functionality, performance and operational environment of an application component. Certification Requirements must be met in order for an application to be installed in the CVE. |
| Backoffice Service Development System | The systems used to develop backoffice (center) hardware and software components of applications. |
| Backoffice Service Installation System | The systems used to install and configure backoffice (center) hardware and software components. |
| Backoffice Service Maintenance System | The systems used to maintain and upgrade backoffice (center) hardware and software components. |
| Care Facility | The 'Care Facility' represents a hospital or another emergency care facility. It may also represent a third party quality of care information provider. |
| Commercial Vehicle | The commercial vehicle includes the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It includes two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials, and provides HAZMAT response teams with timely and accurate cargo contents information after a vehicle incident. It can collect and process vehicle, cargo information from the attached freight equipment, and driver safety data and status and alert the driver whenever there is a potential safety or security problem. Basic identification, security and safety status data are supplied to inspection facilities at mainline speeds. In addition, it can automatically collect and record mileage, fuel usage, and border crossings. |
| Commercial Vehicle OBE | The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general capabilities with capabilities that are specific to commercial vehicles. |
| CV On-Board Cargo Monitoring | "CV On-Board Cargo Monitoring" monitors the location and status of the commercial vehicle and its cargo. It sends the collected data to appropriate centers and roadside facilities, including emergency management in the case of HAZMAT incidents. Depending on the nature of the cargo, it may include sensors that measure temperature, pressure, load leveling, acceleration, and other attributes of the cargo. |
| Device Certification Requirements | The requirements that define the functionality, performance and operational environment of a connected vehicle device. Certification Requirements must be met in order for the device to be granted the credentials necessary to operate in the Connected Vehicle Environment. |
| Emergency Commercial Vehicle Response | "Emergency Commercial Vehicle Response" identifies and initiates a response to commercial vehicle and freight equipment related emergencies. These emergencies may include incidents involving hazardous materials as well as the detection of non-permitted transport of security sensitive hazmat. It identifies the location of the vehicle, the nature of the incident, the route information, and information concerning the freight itself. The information supports the determination of the response and identifies the responding agencies to notify. |
| Emergency Dispatch | "Emergency Dispatch" tracks the location and status of emergency vehicles and dispatches these vehicles to incidents. Pertinent incident information is gathered from the public and other public safety agencies and relayed to the responding units. Incident status and the status of the responding units is tracked so that additional units can be dispatched and/or unit status can be returned to available when the incident is cleared and closed. |
| Emergency Environmental Monitoring | "Emergency Environmental Monitoring" collects current and forecast road conditions and surface weather information from a variety of sources. The collected environmental information is monitored and presented to the operator and used to more effectively manage incidents. |
| Emergency Incident Command | "Emergency Incident Command" provides tactical decision support, resource coordination, and communications integration for Incident Commands that are established by first responders at or near the incident scene to support local management of an incident. It supports communications with public safety, emergency management, transportation, and other allied response agency centers, tracks and maintains resource information, action plans, and the incident command organization itself. Information is shared with agency centers including resource deployment status, hazardous material information, traffic, road, and weather conditions, evacuation advice, and other information that enables emergency or maintenance personnel in the field to implement an effective, safe incident response. It supports the functions and interfaces commonly supported by a mobile command center. |
| Emergency Management Center | The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers. It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system. It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted. It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency. |
| Emergency Routing | "Emergency Routing" supports routing of emergency vehicles and enlists support from the Traffic Management Center to facilitate travel along these routes. Routes may be determined based on real-time traffic information and road conditions or routes may be provided by the Traffic Management Center on request. Vehicles are tracked and routes are based on current vehicle location. It may coordinate with the Traffic Management Center to provide preemption or otherwise adapt the traffic control strategy along the selected route. |
| Emergency Vehicle | The "Emergency Vehicle" represents a range of vehicles including those operated by police, fire, and emergency medical services, as well as incident response vehicles including towing and recovery vehicles and freeway service patrols. |
| Emergency Vehicle OBE | The Emergency Vehicle On-Board Equipment (OBE) resides in an emergency vehicle and provides the processing, storage, and communications functions that support public safety-related connected vehicle applications. It represents a range of vehicles including those operated by police, fire, and emergency medical services. In addition, it represents other incident response vehicles including towing and recovery vehicles and freeway service patrols. It includes two-way communications to support coordinated response to emergencies. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles. |
| EV On-Board En Route Support | "EV On-board En Route Support" provides communications functions to responding emergency vehicles that reduce response times and improve safety of responding public safety personnel and the general public. It supports traffic signal preemption via short range communication directly with signal control equipment and sends alert messages to surrounding vehicles. |
| EV On-Board Incident Management Communication | "EV On-board Incident Management Communication" provides communications support to first responders. Information about the incident, information on dispatched resources, and ancillary information such as road and weather conditions are provided to emergency personnel. Emergency personnel transmit information about the incident such as identification of vehicles and people involved, the extent of injuries, hazardous material, resources on site, site management strategies in effect, and current clearance status. Emergency personnel may also send in-vehicle signing messages to approaching traffic using short range communications. |
| Fleet and Freight Management Center | The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet. |
| Maint and Constr Management Center | The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities. |
| MCM Environmental Information Processing | "MCM Environmental Information Processing" processes current and forecast weather data, road condition information, local environmental data, and uses internal models to develop specialized detailed forecasts of local weather and surface conditions. The processed environmental information products are presented to center personnel and disseminated to other centers. |
| MCM Incident Management | "MCM Incident Management" supports maintenance and construction participation in coordinated incident response. Incident notifications are shared, incident response resources are managed, and the overall incident situation and incident response status is coordinated among allied response organizations. |
| MCM Work Activity Coordination | "MCM Work Activity Coordination" disseminates work activity schedules and current asset restrictions to other agencies. Work schedules are coordinated with operating agencies, factoring in the needs and activities of other agencies and adjacent jurisdictions. Work schedules are also distributed to Transportation Information Centers for dissemination to the traveling public. |
| Mobile Component Development System | The system used in a backoffice environment to develop and test the mobile component of the application. |
| Mobile Component Installation System | The system that interacts with the Vehicle OBE other mobile device and installs the mobile component of the application. |
| Mobile Component Maintenance System | The system used to configure changes and updates to the mobile component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance. |
| Remote EV | Another Emergency Vehicle, typically one equipped with an OBE, with which the Emergency Vehicle interacts. The term "Remote" is synonymous with the term "Other" in the CVRIA. Remote is used with regard to vehicles to be consistent with other information sources, particularly standards, that use this term. |
| Remote EV OBEs | This represents on-board equipment on remote emergency (e.g., law enforcement, fire, EMS, towing and recovery) vehicles. It provides a source and destination for ITS information transfers between emergency vehicles. These information transfers allow information to be shared between emergency vehicles arriving, or involved at, an incident. Vehicle to vehicle communications at incident locations facilitates incident coordination and personal safety. |
| TMC Incident Dispatch Coordination/Communication | "TMC Incident Dispatch Coordination/Communication" formulates and manages an incident response that takes into account the incident potential, incident impacts, and resources required for incident management. It supports dispatch of emergency response and service vehicles as well as coordination with other cooperating agencies. It provides access to traffic management resources that provide surveillance of the incident, traffic control in the surrounding area, and support for the incident response. It monitors the incident response and collects performance measures such as incident response and clearance times. |
| Traffic Management Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
Includes Roles:
| Role | Description |
|---|---|
| Certifies | An Enterprise verifies that a target Resource meets relevant performance, functional, environmental and quality requirements. |
| Constrains | A Resource or Enterprise applies requirements, constraints and associated tests to another Resource. |
| Installs | An Enterprise performs the initial delivery, integration and configuration of the target Resource. |
| Maintains | An Enterprise administers the hardware and software that comprise the target Resource. |
| Member | An Enterprise is part of another larger, target Enterprise. |
| Operates | An Enterprise controls the functionality and state of the target Resource. An Enterprise that Operates a resource is considered Responsible. |
| Owns | An Enterprise has financial ownership and control over the Resource. An Enterprise that Owns a resource is considered Accountable. |
Includes Coordination:
| Coordination | Type | Description |
|---|---|---|
| Application Installation Data | Information Sharing | Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow. |
| Application Interface Specification | Agreement | The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question. |
| Application Maintenance Data | Information Sharing | Data used to facilitate the upgrade, patching and general health maintenance of an application component. |
| Application Performance Data | Information Sharing | Data used to characterize application performance, including such measures as availability, known errors and known uses. |
| Application Procurement Agreement | Agreement | An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process. |
| Application Usage Agreement | Agreement | An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
| Backoffice Component Installation Agreement | Agreement | An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party. |
| Backoffice Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the backoffice component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
| Expectation of Data Provision | Expectation | An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data. |
| Includes | Includes | Indicates that one component is entirely contained within another component. |
| Information Exchange Agreement | Agreement | An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. |
| Information Exchange and Action Agreement | Agreement | An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information. |
| Information Provision Agreement | Agreement | An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. |
| Interface Description | Agreement | Documentation of the interface between two systems, where one system does not have an application component that is part of the application, but does provide and/or receive data and/or information that is used by or sourced from the application. In many cases this is an existing interface used by the application, so the description of the interface already exists and is imposed by the terminator. |
| Maintenance Data Exchange Agreement | Agreement | An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
| Mobile Component Installation Agreement | Agreement | An agreement whereupon the controller of OBE gives another party permission to install, configure and make operational a component that enables the mobile portion of an application. |
| Mobile Component License Agreement | Agreement | An end-user license agreement allowing the operator of the mobile device to use the mobile application component that is part of the application in question. |
| Mobile Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the mobile component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
| Vehicle Data Access Agreement | Agreement | An agreement whereby the party that controls access to on-board vehicle data grants another party the right and ability to access that data. Includes the conditions under which data may be accessed, and specifies the mechanisms, including physical and functional access methods, data formats and any other considerations necessary for the accessing party to acquire data. May also include caveats regarding responsibility for data quality and responsibility for use of the data. |
| Vehicle Operating Agreement | Agreement | An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle. |
| Vehicle Procurement Agreement | Agreement | The exchange of a vehicle for compensation. One entity purchases the vehicle from the other. |
| Vehicle Usage Agreement | Agreement | An agreement between the owner of a vehicle and a prospective operator, whereupon the owner allows the operator to use the vehicle. |
| Warranty | Agreement | A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance over time of an application component. |
Functional
Includes Processes:
Includes Data Flows:
Physical
This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
The physical diagram can be viewed in SVG or PNG format and the current format is SVG. SVG Diagram
PNG Diagram
Includes Physical Objects:
| Physical Object | Class | Description |
|---|---|---|
| Care Facility | Center | The 'Care Facility' represents a hospital or another emergency care facility. It may also represent a third party quality of care information provider. |
| Commercial Vehicle OBE | Vehicle | The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general capabilities with capabilities that are specific to commercial vehicles. |
| Emergency Management Center | Center | The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers. It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system. It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted. It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency. |
| Emergency Personnel | Vehicle | 'Emergency Personnel' represents personnel that are responsible for police, fire, emergency medical services, towing, service patrols, and other special response team (e.g., hazardous material clean-up) activities at an incident site. These personnel are associated with the Emergency Vehicle during dispatch to the incident site, but often work independently of the Emergency Vehicle while providing their incident response services. |
| Emergency Vehicle Databus | Vehicle | The 'Emergency Vehicle Databus' represents the vehicle databus that interfaces with on-board equipment on a public safety vehicle. It is a specialized and extended form of the Vehicle Databus that may be subject to different vehicle databus standards and hosts a broad range of components that are specific to emergency vehicles including the lightbar/siren and on-board apparatus that supports law enforcement, firefighting, and emergency medical services. As a specialized form of the Vehicle Databus, it also provides access to the general-purpose sensors (e.g., radars, cameras), GPS, drive train monitoring and control systems, and vehicle safety features that support connected vehicle applications. In CVRIA, the 'Emergency Vehicle Databus' is used to represent the onboard interactions between the Emergency Vehicle OBE and the other systems included in a host emergency vehicle. |
| Emergency Vehicle OBE | Vehicle | The Emergency Vehicle On-Board Equipment (OBE) resides in an emergency vehicle and provides the processing, storage, and communications functions that support public safety-related connected vehicle applications. It represents a range of vehicles including those operated by police, fire, and emergency medical services. In addition, it represents other incident response vehicles including towing and recovery vehicles and freeway service patrols. It includes two-way communications to support coordinated response to emergencies. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles. |
| Fleet and Freight Management Center | Center | The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet. |
| Maint and Constr Management Center | Center | The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities. |
| Remote EV OBEs | Vehicle | This represents on-board equipment on remote emergency (e.g., law enforcement, fire, EMS, towing and recovery) vehicles. It provides a source and destination for ITS information transfers between emergency vehicles. These information transfers allow information to be shared between emergency vehicles arriving, or involved at, an incident. Vehicle to vehicle communications at incident locations facilitates incident coordination and personal safety. |
| Traffic Management Center | Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
Includes Application Objects:
| Application Object | Description | Physical Object |
|---|---|---|
| CV On-Board Cargo Monitoring | "CV On-Board Cargo Monitoring" monitors the location and status of the commercial vehicle and its cargo. It sends the collected data to appropriate centers and roadside facilities, including emergency management in the case of HAZMAT incidents. Depending on the nature of the cargo, it may include sensors that measure temperature, pressure, load leveling, acceleration, and other attributes of the cargo. | Commercial Vehicle OBE |
| Emergency Commercial Vehicle Response | "Emergency Commercial Vehicle Response" identifies and initiates a response to commercial vehicle and freight equipment related emergencies. These emergencies may include incidents involving hazardous materials as well as the detection of non-permitted transport of security sensitive hazmat. It identifies the location of the vehicle, the nature of the incident, the route information, and information concerning the freight itself. The information supports the determination of the response and identifies the responding agencies to notify. | Emergency Management Center |
| Emergency Dispatch | "Emergency Dispatch" tracks the location and status of emergency vehicles and dispatches these vehicles to incidents. Pertinent incident information is gathered from the public and other public safety agencies and relayed to the responding units. Incident status and the status of the responding units is tracked so that additional units can be dispatched and/or unit status can be returned to available when the incident is cleared and closed. | Emergency Management Center |
| Emergency Environmental Monitoring | "Emergency Environmental Monitoring" collects current and forecast road conditions and surface weather information from a variety of sources. The collected environmental information is monitored and presented to the operator and used to more effectively manage incidents. | Emergency Management Center |
| Emergency Incident Command | "Emergency Incident Command" provides tactical decision support, resource coordination, and communications integration for Incident Commands that are established by first responders at or near the incident scene to support local management of an incident. It supports communications with public safety, emergency management, transportation, and other allied response agency centers, tracks and maintains resource information, action plans, and the incident command organization itself. Information is shared with agency centers including resource deployment status, hazardous material information, traffic, road, and weather conditions, evacuation advice, and other information that enables emergency or maintenance personnel in the field to implement an effective, safe incident response. It supports the functions and interfaces commonly supported by a mobile command center. | Emergency Management Center |
| Emergency Routing | "Emergency Routing" supports routing of emergency vehicles and enlists support from the Traffic Management Center to facilitate travel along these routes. Routes may be determined based on real-time traffic information and road conditions or routes may be provided by the Traffic Management Center on request. Vehicles are tracked and routes are based on current vehicle location. It may coordinate with the Traffic Management Center to provide preemption or otherwise adapt the traffic control strategy along the selected route. | Emergency Management Center |
| EV On-Board En Route Support | "EV On-Board En Route Support" provides communications functions to responding emergency vehicles that reduce response times and improve safety of responding public safety personnel and the general public. It supports traffic signal preemption via short range communication directly with signal control equipment and sends alert messages to surrounding vehicles. | Emergency Vehicle OBE |
| EV On-Board Incident Management Communication | "EV On-board Incident Management Communication" provides communications support to first responders. Information about the incident, information on dispatched resources, and ancillary information such as road and weather conditions are provided to emergency personnel. Emergency personnel transmit information about the incident such as identification of vehicles and people involved, the extent of injuries, hazardous material, resources on site, site management strategies in effect, and current clearance status. Emergency personnel may also send in-vehicle signing messages to approaching traffic using short range communications. | Emergency Vehicle OBE |
| MCM Environmental Information Processing | "MCM Environmental Information Processing" processes current and forecast weather data, road condition information, local environmental data, and uses internal models to develop specialized detailed forecasts of local weather and surface conditions. The processed environmental information products are presented to center personnel and disseminated to other centers. | Maint and Constr Management Center |
| MCM Incident Management | "MCM Incident Management" supports maintenance and construction participation in coordinated incident response. Incident notifications are shared, incident response resources are managed, and the overall incident situation and incident response status is coordinated among allied response organizations. | Maint and Constr Management Center |
| MCM Work Activity Coordination | "MCM Work Activity Coordination" disseminates work activity schedules and current asset restrictions to other agencies. Work schedules are coordinated with operating agencies, factoring in the needs and activities of other agencies and adjacent jurisdictions. Work schedules are also distributed to Transportation Information Centers for dissemination to the traveling public. | Maint and Constr Management Center |
| TMC Incident Dispatch Coordination/Communication | "TMC Incident Dispatch Coordination/Communication" formulates and manages an incident response that takes into account the incident potential, incident impacts, and resources required for incident management. It supports dispatch of emergency response and service vehicles as well as coordination with other cooperating agencies. It provides access to traffic management resources that provide surveillance of the incident, traffic control in the surrounding area, and support for the incident response. It monitors the incident response and collects performance measures such as incident response and clearance times. | Traffic Management Center |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| care facility status | Information regarding facility type and capabilities, facility status, and its ability to admit new patients. |
| care facility status request | Request for information regarding care facility availability and status. |
| decision support information | Information provided to support effective and safe incident response, including local traffic, road, and weather conditions, hazardous material information, and the current status of resources (including vehicles, other equipment, supplies) that have been allocated to an incident. |
| emergency dispatch requests | Emergency vehicle dispatch instructions including incident location and available information concerning the incident. |
| emergency dispatch response | Request for additional emergency dispatch information and provision of en route status. |
| emergency personnel information presentation | Presentation of information to emergency personnel in the field including dispatch information, incident information, current road network conditions, device status, and other supporting information. |
| emergency personnel input | User input from emergency personnel in the field including dispatch coordination, incident status information, and remote device control requests. |
| emergency route request | Request for access routes for emergency response vehicles and equipment. This may be a request for ingress or egress routes or other emergency routes. |
| emergency routes | Suggested ingress and egress routes for access to and between the scene and staging areas or other specialized emergency access routes. |
| emergency vehicle tracking data | The current location and operating status of the emergency vehicle. |
| hazmat information | Information about a particular hazmat load including nature of the load and unloading instructions. May also include hazmat vehicle route and route update information. |
| hazmat spill notification | Information provided to emergency response organizations when cargo sensors detect a release of hazardous material. This information will include sensor information, vehicle location and identification, and carrier identification. |
| host emergency vehicle status | Information provided to the Connected Vehicle on-board equipment from other systems on the Emergency Vehicle Platform. |
| incident information | Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system. |
| incident status | Information gathered at the incident site that more completely characterizes the incident and provides current incident response status. This includes notification of medical facility transport and details about the vehicle occupants being transported. |
| medical records | Electronic medical records accessed to support incident response. |
| medical records request | Request for electronic medical records to support incident response. |
| occupant information | Identification of significant medical conditions of each occupant that would influence critical care decisions made by emergency responders |
| patient status | Information that supports assessment of the incident victim's (patient's) status. Information could include general categorization of their status, vital signs, pertinent medical history, and emergency care information. |
| road network conditions | Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included. |
| road network status assessment | Assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery. |
| road weather information | Road conditions and weather information that are made available by road maintenance operations to other transportation system operators. |
| roadway maintenance status | Summary of maintenance fleet operations affecting the road network. This includes the status of winter maintenance (snow plow schedule and current status). |
| suggested route | Suggested route for a dispatched emergency or maintenance vehicle that may reflect current network conditions and the additional routing options available to en route emergency or maintenance vehicles that are not available to the general public. |
Application Interconnect Diagram
This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
The application interconnect diagram can be viewed in SVG or PNG format and the current format is SVG. SVG Diagram
PNG Diagram
Application Triples
Requirements
| Need | Requirement | ||
|---|---|---|---|
| N2.126 | Incident Scene Pre-Arrival Staging Guidance for Emergency Responders (RESP-STG) needs to collect information about an incident to support staging of emergency responder personnel and their equipment. | 2.274 | The Incident Scene Pre-Arrival Staging Guidance for Emergency Responders (RESP-STG) system shall provide emergency personnel with appropriate route guidance and current status information about the incident as they approach the scene. |
| 2.275 | RESP-STG shall collect imagery information to support emergency dispatch and staging of personnel and equipment, including: still photographs of the scene, satellite imagery, Geographic Information System (GIS) overlays, and video feeds. | ||
| 2.278 | RESP-STG shall collect data from Advanced Automatic Crash Notification Relay systems to support emergency dispatch and staging of personnel and equipment. | ||
| 2.279 | RESP-STG shall collect vehicle occupants' electronic medical records to support emergency dispatch and staging of personnel and equipment. | ||
| 2.280 | RESP-STG shall collect on-scene reports to support emergency dispatch and staging of personnel and equipment. | ||
| N2.127 | Incident Scene Pre-Arrival Staging Guidance for Emergency Responders (RESP-STG) needs to collect information external to the incident scene to support staging of emergency responder personnel and their equipment. | 2.276 | RESP-STG shall collect modeling program outputs to support emergency dispatch and staging of personnel and equipment, e.g. predicted HAZMAT plumes or crash severity predictions. |
| 2.277 | The Incident Scene Pre-Arrival Staging Guidance for Emergency Responders (RESP-STG) shall collect information about freight or cargo to support emergency dispatch and staging of personnel and equipment, e.g. cargo manifest or HAZMAT information. | ||
| 2.281 | RESP-STG shall collect weather and maintenance activity data, e.g., which roads have been plowed to support emergency dispatch and staging of personnel and equipment. | ||
| 2.282 | RESP-STG shall collect medical care facility capabilities and availability, e.g., trauma level supported to support emergency dispatch and staging of personnel and equipment. | ||
| 2.283 | RESP-STG shall collect road and traffic conditions information, including current traffic conditions en-route, current traffic conditions on-scene, and road weather conditions (e.g. wet, icy, snow-covered). | ||
| 2.284 | RESP-STG shall collect road and traffic conditions information from multiple sources including: traffic management centers, probe vehicle data, including traffic data and environmental conditions, and other private traffic data sources, e.g. private distributors that integrate connected (probe) vehicle data with cellular or surveillance device inputs. | ||
| N2.128 | RESP-STG needs to provide situational awareness information to emergency responders about an incident to support decisions of how to stage the personnel and their equipment. | 2.285 | RESP-STG shall provide situational awareness information to emergency responders about an incident, both en-route and while they are on-scene. |
| N2.129 | RESP-STG needs to provide emergency responders with real-time navigation instructions that use all available data sources to quickly and efficiently route the responder. | 2.286 | RESP-STG shall provide routing instructions for a dispatched emergency vehicle that may reflect current network conditions and the additional routing options available to en route emergency that are not available to the general public. |
| N2.130 | RESP-STG needs to maintain location and situational information about the emergency vehicles responding to or on the scene of an incident to be able to provide a complete picture of the response and share the status with other responding vehicles en-route. | 2.287 | RESP-STG shall collect location and situational information about the emergency vehicles responding to or on the scene of an incident. |
Related Sources
- Prototype Development and Demonstration for R.E.S.C.U.M.E. Final Functional and Performance Requirements, Final, 1/10/2014
- R.E.S.C.U.M.E. (Response, Emergency Staging and Communications, Uniform Management, and Evacuation) ConOps, Final, 11/19/2012
- R.E.S.C.U.M.E. Report on Functional and Performance Requirements, and High-Level Data and Communication Needs, Final, 2/7/2013
Security
In order to participate in this application, each physical object should meet or exceed the following security levels.
| Physical Object Security | ||||
|---|---|---|---|---|
| Physical Object | Confidentiality | Integrity | Availability | Security Class |
| Security levels have not been defined yet. | ||||
In order to participate in this application, each information flow triple should meet or exceed the following security levels.
| Information Flow Security | |||||
|---|---|---|---|---|---|
| Source | Destination | Information Flow | Confidentiality | Integrity | Availability |
| Basis | Basis | Basis | |||
| Security levels have not been defined yet. | |||||