Bypass operations
A bypass operation, also known as an inhibit, temporarily stops the functioning of a component of a system, or of the entire system. A bypass operation record describes the reasons for the bypass operation, the scope, and the actions to take that relate to the bypass operation.
Bypass operations are conducted on safety-related systems, such as emergency shutdown systems, fire and gas systems, and alarm systems. Sometimes it's necessary to bypass a safety control system. For example, maintenance might be needed on a component of a system. The safety control system is bypassed and replaced by a specific set of actions that are done by highly skilled personnel.
The hazards that are inherent in bypassing a system must be assessed before you proceed with the bypass operation. The appropriate precautions must be in place.
Bypass operations might be reviewed and approved multiple times because of the high risks that might be involved with some of the tasks.
When a bypass is removed, and the system is returned to operation, the system must be verified to ensure that normal functioning is restored.
Bypass operations and work orders
A bypass operation is frequently used with one or more work orders. In the Work Order Tracking application, you can create a work order to associate with the bypass operation. You can also generate a bypass operation record based on a work order.
In the Bypass Management application, you can relate bypass operations with work orders and with tickets.
Templates for frequently used bypass management records
When you use the same types of bypass management records, a template ensures a consistent process and format.
You can create a template from an existing bypass management record. Using the List tab, search for a bypass management record that corresponds to your current goals, and specify the record as a template. You can also create a bypass management record from an existing template using the More Actions > Create Bypass from Template option.
When you create a record from an existing bypass management record, only certain fields and their values are duplicated. Those fields and their values are copied from the originating record to the new record. Templates remain in Draft status.
Bypass operations and standard actions
Standard actions can be associated with bypass operations. Actions can occur either before the start of the work activities or after the work activities begin. You might decide that a bypass operation is not ready to be implemented until certain actions are taken. You can specify that actions are repeatable. That is, you can specify the same action multiple times.
You can also assign an action group to do the actions.
Bypass operations and service level agreements
When you create a service level agreement, you specify the commitments that you agreed to fulfill for external or internal customers. A commitment is a level of service that is agreed upon between the service provider and the customer that can be measured in a qualitative or quantitative way.
You can create a service level agreement and apply it to a bypass operation to ensure that the level of service complies with the agreement.
Bypass operations and workflow processes
You can create workflow processes that reflect your business processes. A workflow process defines the actions and the notifications that can occur at different points in a business process. You can manage the movement of a record through a process from start to finish. You can instruct individuals to act on records, ensure that individuals act in a timely manner, and ensure that an audit trail exists for each record and process. You use the Workflow application to plan, design, build, test, implement, and manage workflow processes.
For example, for bypass operations, you can create a workflow process to route the bypass operation record through the review and approval stages. You can have the workflow process notify you when the bypass operation record is reviewed and approved.