Skip to main content

FieldLogs

Using Operation Plans

Note

The term Operation Plan is a customizable label in FieldLogs. It might be referred to differently in your organization.

The equivalent term for Operation Plan in your organization is the term used instead of the highlighted menu item below in your interface.

OP-Label.png

Operation Plans are used to execute a set of Tasks in response to certain Events in the system.

They can be configured to respond to a set of Event Triggers - time-based / event-based.

Time based triggers enable a set of Tasks to be run at periodic intervals.

The table below details the differences between an Operation Plan and a Custom Operation Plan.

Type of Plans

Description

Operation Plan

  • Triggered automatically when the configured Event Trigger occurs in the system.

  • The Event Triggers can be time based or event based.

  • It must be defined, instantiated and activated to execute the configured Tasks in response to the Event Trigger.

Custom Operation Plan

  • They are executed manually and not automatically triggered.

  • They are merely a set of tasks that are encapsulated into a single unit for ease of execution.

  • They just need to be defined. They need not be instantiated or activated.

Operation Plans can be used to carry out periodic audits or run quality control checks on the system. They are discussed in detail here.

GOP_usecases.png

Custom Operation Plans can be used to encapsulate a set of tasks that the user needs to execute as a batch, for example, a set of reports that need to be printed. They are discussed in detail here.

COP_usecases.png
In this section: