Situation Awareness Use Case    (2RUS)

It is important to note that this use case is ficitional and does not represent the position of any agency. This use case should not be considered to represent any more than the exposition of a possible use scenario, in pretty complete form, to demonstrate to GeoSpatialCommunityofPractice members how complex use cases are best expressed. There is, at least, one more level of detail to this use case that actually addresses the geospatial aspect more directly. If this use case is selected for the EA Profile documentation, then that level of detail will be included.    (2RUT)

Name: Situation Awareness Use Case    (2RUU)

Description:    (2RUV)

This use case uses an idealized structure of the incident command structure from the National Incident Management System and the National Response Plan to outline the operation of a equally idealized Situation Awareness (SA) system. This SA system is intended to provide situation awareness to all levels of the incident command and coordination structure as syncronously as possible.    (2RUW)

Actors:    (2RUX)

SA Client Node - an element of the SA system that acts as a user's view into the common operational picture and that is specific to the role of the user. SA client nodes can be connected to the Internet by wireless or wired communications and SA Client software may be installed an operate on many hardware platforms including, cellular phone, PDA, laptop computers, or desktop computers.    (2RUY)

SA Server Node - an element of the SA system that acts as a server of information to SA Clients or other SA Server Nodes.    (2RUZ)

SA Catalog - an elemet of the SA system that catalogs information related to the incident as it appears in the system and acts as an information clearinghouse. The SA Catalog houses metadata records that confrom to the SA Metadata schema.    (2RV0)

SA Metadata Schema - a metadata schema (NIEMS?) that provides a template for metadata about information provided into the SA system and that allows for the proper categorization and classification of incoming information such that it can be properly dispatched or otherwise provided to elements / roles within the incident command and coordination structures. furthermore, the SA metadata schema provides the ability to tag all information with its geospatial and temporal context so that it can be mapped and tracked, if applicable.    (2RV1)

Incident Command Post (ICP) - The tactical-level, on-scene incident command and management organization is located at the ICP. It is typically comprised of designated incident management officials and responders from Federal, State, local, and tribal agencies, as well as private-sector and nongovernmental organizations. When multiple command authorities are involved, the ICP may be led by a Unified Command, comprised of officials who have jurisdictional authority or functional responsibility for the incident under an appropriate law, ordinance, or agreement. The Unified Command provides direct, on-scene control of tactical operations and utilizes a NIMS ICS incident management team organization, typically including Operations, Planning, Logistics, and Finance/Administration Sections. The ICP is usually located at or in the immediate vicinity of the incident site. The location is selected by the agency having primary jurisdictional authority for managing the incident at this level. Generally, there is one ICP established for each incident. Depending on the number and location of incidents, there may be multiple ICPs managed by an Area Command.    (2RV2)

Area Command (AC) - An Area Command is established to oversee the management of multiple incidents that are each being handled by a separate ICS organization or to oversee the management of a very large or complex incident that has multiple incident management teams engaged. The Area Command has the responsibility to set overall strategy and priorities, allocate critical resources according to priorities, ensure that incidents are properly managed, and ensure that objectives are met and strategies followed. Area Command becomes Unified Area Command when incidents are multijurisdictional.    (2RV3)

Local,County, and State Emergency Operations Centers (EOC) - State, county, and local EOCs represent the physical location at which the coordination of information and resources to support incident management activities ormally takes place. EOCs are typically organized by major functional discipline (fire, law enforcement, medical services, and so on); by jurisdiction (city, county, region, and so on); or, more likely, by some combination thereof.    (2RV4)

Joint Field Office (JFO) - a temporary Federal facility established locally to coordinate operational Federal assistance activities to the affected jurisdiction(s) during Incidents of National Significance.    (2RV5)

Regional Response Coordination Center (RRCC) - coordinates regional response efforts, establishes Federal priorities, and implements local Federal program support until a JFO is established.    (2RV6)

Homeland Security Operations Center (HSOC) - the primary national hub for domestic incident management operational coordination and situation awareness. The HSOC is a standing 24/7 interagency organization fusing law enforcement, national intelligence, emergency response, and private sector reporting. The HSOC facilitates homeland security information-sharing and operational coordination with other Federal, State, local, tribal, and nongovernmental EOCs. For purposes of this use case, we will focus on the following role/responsibility of the HSOC:    (2RV7)

Preconditions:    (2RVB)

  1. First responders and their apparatus are instrumented and tracked by GPS, RFID and/or other location-based technology and take part in the SA system as resources complete with metadata describing their roles and capabilities.    (2RVC)
  2. Second responders and their apparatus are instrumented and tracked by GPS, RFID and/or other location-based technology and take part in the SA system as resources complete with metadata describing their roles and capabilities.    (2RVD)
  3. Responders in specific roles a) have SA Client nodes on their person and b) are capable of providing informational updates to the system via specialized and automated interfaces.    (2RVE)
  4. ICP, AC, EOCs, JFO, and HSOC staff in specific roles a) have SA Client nodes available to them/on their person, b) via these nodes are capable of receiving information relevant to their role in a situation awareness display(s) that are designed to meet the needs of their role, and c) via these nodes are capable of providing informational updates to the system via specialized and, potentially, automated interfaces.    (2RVF)
  5. EOCs, JFO, and HSOC all a) have SA Server node(s) available, b) via these nodes are capable of accessing and updating information relevant to their role in a situation awareness display(s) that are designed to meet the needs of their role, and c) via these nodes are capable of providing informational updates to the system via specialized and, potentially, automated interfaces.    (2RVG)
  6. A replicated SA Catalog exists that accepts SA metadata schema conforming metadata records.    (2RVH)

Flow of Events - Basic Path:    (2RVI)

  1. Use Case 1 - Initialize SA system with basic information, such as geospatial data, base orthoimagery, critical infrastructure information, key asset information, and resources and capabilities (where resources provided reflect the resource-typing categories identified in the NIMS and are related to the Emergency Support Function from which they are provided),    (2RVJ)
  2. Use Case 2 - Operate SA system based on operational requirement resultng from an Incident of National Significance.    (2RVK)
  3. Use Case 3 - Utilize the SA system to obtain situational awareness for a particular role and emergency support function.    (2RVL)
  4. Use Case 4 - Populate the SA system with information via an automated interface designed to support a particular role and emergency support function.    (2RVM)
  5. Use Case 5 - Playback SA system activity log corresponding to events, actions, or other information obtained during an incident for various purposes (after action reporting, lessons learned, etc.).    (2RVN)

Flow of Events - Alternative Paths:    (2RVO)

None.    (2RVP)

Postcondition:    (2RVQ)

  1. A well-managed incident, where all elements of the response command and control elements are completely aware of the situation as required by their role and where coordination elements are able to make decisions that positively support the conduct of the mission resulting in lives saved.    (2RVR)
  2. An SA system with a populated activity log corresponding to events, actions, or other information obtained during an incident.    (2RVS)