A Workflow That Starts From an Alarm System

Friday, March 18, 2011
The Workflow for Procedures in Emergencies was a general flow for emergencies that started with identifying and confirming damages to announcing a state of emergency. But companies that have an alarm system or an information system that can identify crises, this portion of the workflow should be automatic to a certain extent, so they should be able to make faster decisions about whether it is an emergency or not.

Related workflows

<Tasks>
1. Instruct to Check Damage (& Announce Emergency), 2. Announce Emergency, 3. On-time Instruction, 3abc. Start, 4abc. Report, 5. Confirm Report, 6. Decide to Gather Involved Parties


[Contingency Plan <Auto Send>: "1. Instruct to Check Damage (& Announce Emergency)" screen]



In this workflow, the manager in charge of confirming damages receives a notification from the alarm system, and can either request employees to make further investigations or request directors to announce a state of emergency. If a director is the one who receives the initial notification, he/she can make the announcement. (Task 1. Instruct to Check Damage (& Announce Emergency)

Announcing a state of emergency means the company will be putting together an emergency system and team. Therefore, all of this information should be handed over to other workflows, such as those for controlling damages or restoring the organization. The below workflow automatically sends such data to other workflows before ending.

<Tasks>
1. Instruct to Check Damage (& Announce Emergency), 2. Announce Emergency, 3. On-time Instruction, 3abc. Start, 4abc. Report, 5. Confirm Report, 6. Decide to Gather Involved Parties


Label: , ,