Working with Blocks
Blocks are used to organize steps based on stages of execution. A block is a series of contiguous steps that can include both single (ungrouped) steps and groups of steps. Note the following when working with blocks:
When you create a new sheet, the system creates an empty block named "Default." When you add steps, they are added to this block by default. You can delete this block and create a new top-level block if you wish.
The system provides several pre-configured block headers (Isolate, Maintenance, Restore, and Construction); or you can create a custom header. The header is simply the block name that is displayed in the Steps list.
To expand a block and display its steps, click the + symbol to the left of the block name.
To collapse a block and hide its steps, click the - symbol.
All steps within a block must be completed before a step within another block can be completed, unless the block names are the same and the blocks are adjacent (not separated by any blocks of different names). See the “Parallel Step Execution” for more information about parallel execution of block steps.
Adding a New Block Header
To add a new block header to the steps list:
1. From the Steps tab, right-click the step after which you want to insert a block. An option menu appears.
2. Select Add New Block Header, then select a block header type: Isolate, Fault Location, Maintenance, Restore, Construction, or Custom.
Notes:
If you choose Custom, you are prompted to enter the block header name.
If the only step row in the steps list is the Default block header row and you add a new block header, then the Default block header row will be replaced with the newly added block header row. This is only the case if there are no other steps in the switching sheet.
A new block header row is added to the steps list.
Renaming a Block Header
To rename a block header in the steps list:
1. From the Steps tab, right-click the block step that you want to rename. An option menu appears.
2. Select Rename Block Header, then select a block header type: Isolate, Fault Location, Maintenance, Restore, Construction, or Custom.
Note: If you choose Custom, you are prompted to enter a new block header name.
The selected block header row is renamed.
Understanding Alerts When Interdependent Blocks are Modified
Switching sheets can be configured to have different block types that are interdependent with one block type being defined as primary and another block type defined as secondary. For example, in the product configuration, Isolate is defined as a primary block type and Restore is its secondary block type. When a sheet is being transitioned to a new state (for example, going from New to Prepared), the system checks to see if the primary block was modified after its secondary block was modified.
Note: Modifications could include actions such as adding, deleting, editing (by changing field data), or moving steps. The fields that are checked for modifications can be configured.
If a primary block was modified after a secondary block, the system will warn you that the primary block was edited after the last saved edit to the secondary block. If you click OK, the sheet will transition states; if you click Cancel, the state transition will not occur and you can review and edit the secondary block steps, as necessary.
Example
You have a new sheet with an Isolate primary block and its corresponding Restore secondary block. You have created steps to isolate and restore (using Copy as Go‑Backs). You save the sheet. You add a tag in the isolate block, save the sheet, select the Tracking/Audit Log tab, and click Prepared. The dialog box will tell you that you modified the isolate block after saving the restore block. Click Cancel and add the corresponding remove tag in the restore block. Save the sheet. You can now transition the sheet to Prepared without being warned.
Parallel Step Execution
Parallel execution allows an operator to direct one crew through a set of steps in one block and another crew through a set of steps in another block. This provides the operator more flexibility when executing switching steps and more closely correlates with their actual business process.
Blocks of steps with the same block names can be executed in parallel when in order step execution rules are enabled (see “Step Order Execution Rules” for details). The blocks must be sequentially listed and cannot be separated by different blocks of steps. For example, parallel execution is allowed when blocks are ordered (for example, Isolate, Isolate, Restore, Restore); parallel execution is not allowed if blocks are separated by different block names, such as Isolate, Restore, Isolate, Restore.
When executing switching steps, the system checks to see if the previous block step has the same name as the current block step. If it does, the system ignores any incomplete steps within these blocks, but requires that you complete the steps within each block in order. If steps are grouped within a block, normal grouping rules apply (see “Grouping and Ungrouping Steps”).
The example that follows describes how you might create and execute a plan using parallel step execution:
1. Create a Planned switching sheet.
2. From the Steps list, right-click on the Default block step. Select Add New Block Header and then select the Isolate option.
3. Record one or more steps into the Isolate block for a single pressure zone.
4. Add another Isolate block at the end of the first block.
5. Record one or more steps into the second Isolate block for a different pressure zone.
6. Create two Restore blocks after the second Isolate block.
7. Create go-back steps for the first of the Isolate blocks. Paste the go-back steps into the first Restore block.
8. Repeat the previous steps to create and paste go-back steps into the second Restore block.
9. In Study mode, complete the first step in the first Isolate block. The step is completed.
10. Complete the first step in the second Isolate block. The step is completed.
11. Continue executing steps in parallel for both Isolate blocks and then both Restore blocks.
Note: Parallel execution is not required in this situation; it is simply available as an option.