If we then relate the discussion on decision domains to system le-
vels, we can identify three types of decision domains. We can then
for each of these describe the responsibilities of the individual re-
ceiving the authority. It is also through the decision domains that
we link the command system with the individuals that manage
the system. For the individual (commander) the decision domain
entails a degree of authority, tied to time and space.
The decision domain at the system level to provide municipal
emergency services is referred to as system command. The decision
domain associated with the system level to execute emergency re-
sponse operations is referred to as operational command and the de-
cision domain at the system level to execute tasks, task command.
It must be possible to manage all the decision domains. And,
moreover, system command must be administered continually, 24
hours a day, 365 days a year. Operational command arises when
a response operation is initiated, and task command comes into
play when tasks are going to be applied, within the framework
of the response operation. Decision domains form parts of each
other and cannot be lifted out of their context. Task command
is a part of operational command and operational command is
a part of system command. Note that this refers to the grouping
of decision domains. If several response operations are being ex-
ecuted simultan eously, each response operation is managed by its
respect ive decision domain, operational command. These are then
parts of the decision domain, system command. In a correspon-
ding way several tasks can be carried out simultaneously within
the framework of a single response operation. These will then beDecision domains,
defined by the scope of
authority.
The scope of authority of
the decision domains
covers the actual
engagement, in terms of:- Available time
- Available space
- Issues at hand
- Problems
- Information
- Direct or indirect influence
- etc