Runbook Structure
Every Runbook consists of a suite of tasks, grouped into stages and positioned within a phase. Tasks can be bound by various types of dependency. The only phase mandatory for any Runbook within ICEFLO system is the Implementation Phase: the basic structure is depicted below.
Runbook - Most Basic Form (one Implementation Phase)
Pre-Implementation and Post-Implementation phases are optional, as is a Backout, however every backout will have a mandatory Implementation Phase, i.e. the core of the back-out work to execute total or partial unwind.
Runbook - Pre-Imp-Post Phase Structured Runbook (but no Backout)
This Runbook has the full suite of three phases. Each phase can have one or more stages.
STP - All Phases Plus Backout (with Implementation and Post-Implementation Phases)
The most complex Runbook will also have the optional Pre-Implementation and Post Implementation phases complete with a complementary Backout Phase and Backout Post-Implementation Phase.