Introduction to Assets

Assets can be any kind of resource or entity that is of interest to your organization.  
Assets are classified in the system by three main categories/domains:

  • People - any person of interest 
  • Objects - Physical entities (i.e. cameras, sensors, equipment etc.)
  • Data - Virtual entities (i.e. documents, footage, blueprints etc.). 

Under each of the three domains, Admin can create sub-categories called Asset Types. For each Asset Type Admin can define dedicated icon, form. 

Asset Relationships

Note: the term Assets usually refers to entities not allocated an actual licensed User in the system. However, the relationships feature described here in detail, can also be applied to licensed Users in the User Manager.

The most significant Assets feature is the ability to define relationships between Assets and other entities in the system (i.e. POIs, Geofences, Incident Types, Groups). These predefined relationships trigger real-time linkages between various attributes of incidents and corresponding relevant Assets .

Thus, organizations can maximize the system's operational potential by creating and maintaining an Assets bank in the system. Having an up-to-date Assets database can play an important role in incidents by adding another operational layer of Assets and associated functions to the incident (i.e. sources of data and information, people or objects that need to be attended or transported etc.). 

When implemented and maintained, this feature can add substantial value by enriching the system with contextual situational awareness for both Dispatchers and Responders. Furthermore, the mobile app has an Asset Lookup module allowing mobile users (with appropriate permission) to search for nearby Assets, add an entry to their log and even create an incident linked to the Asset's location and details.    

Assets Management

The system has several features that engage with Assets:

  • Asset Types Admin page - this is where the Admin defines the Asset Types and their behavior in the system
  • Assets Panel - this is where permitted Dispatchers create and manage the Assets. For more information on managing Assets - click here
  • Dispatcher Incident Manager Assets tab - this is the focus of this article (see later).
  • Asset Lookup - mobile Responders with permission can access valuable information on Assets and perform actions on those assets. 
  • Assets tab in the Incident Responder - Responders can view the specific Assets that have links to the incident. 

The focus of this article isn't the Assets main panel but rather ways to utilize the Assets within a specific Incident. Assets in Incident are managed in the Assets tab within the Incident Manager.

A Typical Scenario

In order to illustrate the Asset in Incident features - we will use the following example:

Take a look at the map below of JFK airport:

  • The blue area marked on the map is a polygon/geofence of JFK's Terminal 8
  • The running man icon is a POI (point of interest), known as the terminal's "Exit Door"

Our scenario:

  • Standing by the exit door of Terminal 8 is a suspicious looking individual, who has been reported by a local official to central dispatch.
  • Once reported, the dispatch operator/dispatcher can create a Suspect incident.
  • The location of the incident is the "Exit Door" POI.
  • Once the basic information of the incident is inserted and location is set to "Exit Door" POI, move on to the Assets tab.
    Note:  The assets are divided into three different categories: People, Objects, Data, Geotags, and Control.
  • We can see that "Jenny" from airport security is in the asset list and we can call or send her a text message (SMS). If necessary, we can also edit her information by clicking the edit button. 
  • To understand Jenny's relevance to this particular incident, we can look at the Relevance column. In this case, Jenny is associated directly with the type of incident Suspect (the incident icon appears ) in her organization. This means that whenever a Suspect incident is created in this particular organization, Jenny's details will appear in the assets list both in Dispatcher and in the Responder app. 

Asset Information

The following information appears in the 'People', 'Objects' and 'Data' lists:

  • Asset Type (i.e. People)
  • Asset Name (i.e. Jenny)
  • Status (only for People Assets): Online/Offline/Static
  • Distance (only for Assets with preset location): How far the asset is from the location of the incident
  • Comments: textual notes 
  • Relevance: The relevance (relationship) of the asset to the incident. An Asset can be linked to the incident via their location (geofence/area/POI), via the incident type, or to the specific incident (i.e. caller)
  • Actions: The types of actions that can be taken with this asset at this given point in time
  • Log: Any information recorded in a log in reference to the asset
  • Edit: This button is available to users with the permission to edit the assets information.

By switching to the 'Objects' tab in the asset list, we see that there is a camera associated with the 'Exit Door' asset. Note that there is a link in the 'Actions' column, which in this example will take the dispatcher to a live streaming video of the exit door.

When linking an Asset to an incident there are typically two scenarios - both are supported in the Link Asset to Incident Wizard:

  1. Creating a new Asset in the system that is linked to the Incident
  2. Linking an Asset that is already defined in the system to the incident. 

To add an asset to the incident, open the Link Asset Wizard by 

  1. Click on the Plus icon, located at the top right corner of the asset list.

2. Type the Asset's name - 

  • if the asset already exists in the system, an autocomplete list will be displayed - click the relevant asset, and its information will populate the fields below
  • if the Asset does not exist - enter its name, choose its category (people/object/ data), enter other information below and then click Create Asset.

4. Pick one of the following link types that describe the relationship between the Asset and the incident:

  • Geofence/Polygon surrounding Incident - this link type will ask you to pick from a list of geofences surrounding the incident location. The geofence you pick will be added to the relationships of the Asset. Any future incident which is located in this geofence will display this Asset. 
  • POI - this link type will ask you to pick from a list of POIs surrounding the incident location. The POI you pick will be added to the relationships of the Asset. Any future incident which is located near this POI will display this Asset. 
  • Incident Type - this link type will link the Asset to the specific Incident Type of this incident. Any future incident of this type will display this Asset. 
  • Caller - this link type will link the Asset to the specific incident without any implication on other incidents in the future. 


The dispatcher can also view and utilize the geographically tagged assets closely located to the incident by clicking on the 'Geo-Tag' tab, as seen below:

The type of information provided in the 'Geo-Tag' tabs include:

  • Type: POI / Geofence
  • Name
  • Distance: The distance between the geo-tag and the incident
  • Comments: Any comments associated with that geo-tag
  • Actions: Actions that can be taken with the geo-tags, such as zooming the map into the geo-tag

The dispatch operator can center the map on the specific geo-tagged asset by clicking on the Zoom Map icon

Users with the correct permissions can configure the maximum distance between an asset and an incident for it to appear in the list. 

Did this answer your question?