Components installed with Critical Event Management

Release version: Xanadu

Updated July 31, 2025

2 minutes to read

Summarize

Summarized using AI

Summary of Components installed with Critical Event Management

The Critical Event Management (CEM) application installs several integral components, including store applications, user roles, tables, and plugins. These components collectively enable efficient management, communication, and resolution of critical events within ServiceNow. Understanding these components helps customers configure and utilize CEM effectively for health, safety, and emergency response scenarios.

Show full answer Show less

Store Applications Installed

Health and Safety Core: Provides the foundational data model for health and safety, including user profiles and actions used across Health and Safety applications.
Workplace Core [snwsdcore]: Enables workplace location management for Health and Safety. Note that installation does not include location demo data by default; demo data can be loaded by repairing the Workplace Core plugin with the Load demo data option.
Health and Safety: Supports incident reporting specific to Health and Safety.
Task Communications Management UI Components for Configurable Workspace: Supplies UI components necessary for leveraging Task Communications Management features within workspaces.

User Roles Installed

The application installs specific roles tailored to various responsibilities in critical event workflows:

Critical Event Admin [sncritical.admin]: Administrators who configure application properties and manage the system.
Critical Event Agent [sncritical.agent]: Users managing critical event records from start to finish.
Critical Event Manager [sncritical.manager]: Supervisors who oversee critical events and guide agents and responders.
Critical Event Reader [sncritical.read]: Users with read-only access to critical event records.
On-site Responder [sncritical.responder]: Personnel assisting on-site during critical events, with read access.
Critical Event User [sncritical.user]: Employees who report emergencies; this role does not contain additional permissions.

Tables Installed

CEM extends core ServiceNow tables to capture detailed information related to critical events:

Critical Event Communication Plan [sncriticalcommplan]: Stores detailed communication strategies; extends Communication Plan table.
Critical Event Communication Task [sncriticalcommtask]: Tracks individual communication tasks; extends Communication Task table.
Critical Event [sncriticalevent]: Records of critical events; extends Task table.
Impacted People [sncriticalimpactedpeople]: Lists individuals affected by critical events.
On-site Responder Mapping [sncriticalonsiterespondermapping]: Maps responders to specific on-site locations during events.
Critical Event Task [sncriticaltask]: Stores tasks related to critical event management; extends Task table.

Plugins Installed

Notify [com.snc.notify]: Enables SMS preferences and message delivery from multiple providers.
Task Communication Management [com.snc.taskcommunicationmanagement]: Activates base system features, including demo data and related plugins.

Optional Applications

To enhance CEM functionalities, optional apps can be installed:

Geo Map Component [sngeomap]: Adds map visualization capabilities to the Critical Event Management dashboard.

Practical Implications for ServiceNow Customers

By installing Critical Event Management, customers gain a comprehensive solution to manage health, safety, and emergency incidents with structured roles, dedicated tables for event tracking, communication plans, and tasks. The integration of core Health and Safety store applications ensures a robust data model, while optional components like the Geo Map enhance situational awareness. Proper role assignment ensures secure and efficient handling of critical events, and plugins like Notify facilitate timely communication through SMS. Understanding these components allows customers to configure CEM effectively to meet their organizational emergency management needs.

Several types of components are installed with the Critical Event Management application, including tables and user roles.

Store applications installed

Table 1. Store apps installed with Health and Safety Risk Management
Store application	Description
Health and Safety Core	Installs core data model for Health and Safety. This data model includes common components such as Health and Safety user profile and actions that are used in the Health and Safety applications. For more information on store applications, roles, and tables installed with Health and Safety Core, see Components installed with Health and Safety Core.
Workplace Core [sn_wsd_core]	Enables workplace locations for Health and Safety applications. Important: The application installation doesn’t install the location demo data for the Workplace Core location model. As a workaround, repair the Workplace Core plugin with the Load demo data option.

Roles installed

Table 2. Roles installed with Critical Event Management
Role title [name]	Description	Contains roles
Critical event admin [sn_critical.admin]	Administrator role. Configures the Critical Event Management application properties.	sn_critical.agent sn_critical.responder sn_comm_management.comm_plan_admin sn_critical.user sn_critical.manager
Critical event agent [sn_critical.agent]	Works on critical event records from initiation to resolution.	sn_comm_management.comm_plan_manager task_editor canvas_user sn_ohs_im.workspace_user sn_critical.read
Critical event manager [sn_critical.manager]	Oversees all critical events and guides agents and responders to resolve them.	sn_critical.agent
Critical event reader [sn_critical.read]	Has read-only access to critical event records.	sn_comm_management.comm_plan_viewer
On-site responder [sn_critical.responder]	Assists on-site personnel during critical events.	sn_critical.read
Critical event user [sn_critical.user]	Reports emergency as an employee.	None

Tables installed

Table 3. Tables installed with Critical Event Management
Table	Description
Critical event communication plan [sn_critical_comm_plan]	Stores information about detailed communication strategies during critical events. This table is an extension to the Communication Plan [comm_plan] table.
Critical event communication task [sn_critical_comm_task]	Tracks individual tasks related to the communication plan for critical events. This table is an extension to the Communication Task [comm_task] table.
Critical event [sn_critical_event]	Contains records of critical events. This table is an extension to the Task [task] table.
Impacted people [sn_critical_impacted_people]	Lists individuals impacted by critical events.
On-site responder mapping [sn_critical_on_site_responder_mapping]	Maps responders to on-site locations during critical events.
Critical event task [sn_critical_task]	Stores tasks related to Critical Event Management. This table is an extension to the Task [task] table.

Plugins installed

Table 4. Plugins installed with Critical Event Management
Plugins	Description
Notify [com.snc.notify]	Provides the ability to set SMS preferences to receive messages from different providers.
Task Communication Management [com.snc.task_communication_management]	Activates the base system. Includes demo data and activates related plugins if they aren’t already active.

Store applications installed

Table 5. Store applications installed with Critical Event Management
Store applications	Description
Health and Safety	Allows you to report Health and Safety incidents.
Task Communications Management UI Components for Configurable Workspace	Stores bundle of UI components required to leverage Task Communications Management core capabilities in workspaces.

Optional applications

Table 6. Optional applications for additional features in Critical Event Management
Application	Description
Geo Map component sn_geo_map	Enables the map component on the Critical Event Management dashboard.