Basic Concept

Structure

To help you get started with eAlarm emergency and to ensure that alerts are triggered both optimally and effectively, we recommend that you outline your company’s alerting and mobilisation structure before you begin.

These questions could help you with the process:

• Which superordinate/subordinate organisational units / deployment units exist?
• Which special units are there?
• Which alerting scenarios do you expect and which alerting and mobilisation processes will result?
• Which users should receive access permission, i.e. who should be able to manage or modify these in the future? Who should be able to trigger alerts?

Use “roots”, “groups” and “subscribers” to clearly map your organisation’s structure in eAlarm emergency. These categories follow a logical hierarchy and can be flexibly designed.

1. Create higher-level roots for higher-level alerting and mobilisation units. Map subject areas, divisions, corporate groups, etc.

2. Create folders or groups assigned to a root. One root can have multiple groups and groups themselves can be assigned to a group (subgroups). Map teams, jobs, deployment units.

3. Create and add subscribers who map the members of your organisation. Subscribers are provided with specific records and permissions and can be assigned to multiple roots and/or groups.

Structures can be adapted or modified at any time.

Configuration

eAlarm emergency is ready to use after only a few steps. To ensure effective alerting, it is a good idea to configure the system in a specific sequence.

Sequence of an eAlarm emergency configuration

1. Define the media designations: Define the available alert media.

2. Define optional free fields for subscribers: Enables a broader range of information to be entered for subscribers.

3. Open root.

4. Create and assign groups.

5. Assign subscribers to the groups.

6. If necessary, create alert templates, scenarios and conference templates.

7. Adapt registry entries: Adapt eAlarm emergency to your needs.