Skip to main content

FieldLogs

Adding a Trigger and Action Counter

A Counter helps to combine the information between an Event Trigger and the Actions.

The Counter contains information about the Event Trigger and the corresponding Action. When an Event takes place Action is triggered. The Action is made up of instances of one or more Templates.

For example, if a daily inspection needs to be performed on all the Equipments and the Battery Circuit at 16:00 hours, the Event Trigger will be at (16:00 hours). An instance of the Battery Circuit Template and multiple instances of the Equipment inspection Template comprise the Action.

OP-Counter.png

To add a Counter to a Operation Plan:

  • Click Add Counter in the dropdown list near the name of the Operation Plan as shown.

    You can also use the dropdown list in the General Settings tab as indicated below.

    Add_counter_dropdown.png

    A new Counter is created under the Operation Plan as shown below. It is given a generic name Counter Name as highlighted below.

    Counter_name.png

There are five tabs to define the Counter. They are:

  1. General Settings

  2. Event Triggers

  3. Action

  4. JS Script

  5. Variables

On every Tab, there are three buttons Delete, Revert and Save as seen below.

Three_options.png
  • Delete: Deletes the Counter.

  • Save: Commits all the changes done so far to the Counter.

  • Revert: Undoes all unsaved changes.

You can customize the name of the Counter in this section. Edit the placeholder text Counter Name to enter an appropriate name for your Counter.

General_settings_tab.png

The following fields can be configured:

  • Type: Select the Counter Type- Trigger and Action from the dropdown list.

  • Name: Enter a name for the Counter. You can also use the auto-naming option. The auto-name format can be configured using the options highlighted below.

    In the following example, the Text Wing repairs have been used to create the auto naming format for the Counter.

    Auto_naming.png
  • Description: Description of the purpose of the Counter.

  • Maximum Task Created: This sets the maximum number of tasks that this Counter can create.

  • Functional Types: It is used only to visually highlight the Counter. It has no impact on the Tasks generated from the Operation Plan.

    You can also use the Link to Variable option to link to a Functional Type Variable.

Visible from Planning: If this option is enabled, the Tasks generated are visible from Planning and Inbox sections.

Mark as Favorite: This option enables you to bookmark an Operation Plan.

A sample Counter with its fields set is shown below.

Added_all_the_fields.png

This counter can also be seen in Planning and Inbox when you select Visible from Planning.

If this option is selected, then the Tasks generated by this Counter are listed under the Counter in the Planning and Inbox sections.

In the below example, the Visible from Planning option is enabled on the Leakage Check counter.

Visible_from_planning.png
Instantiated.png

The Tasks generated by the Leakage Check Counter are grouped under the counter name in the Inbox and Planning sections as seen below.

Inbox.png
Planning.png

You can re-use this Counter by marking it as a favorite.

You can mark a Counter as a Favorite if you would like to re-use it in other Operation Plans.

Click the OP-StarFavorite.png to mark the Counter as a Favorite as shown below.

Mark_as_Favorite.png

The Counter is marked as a Favorite as indicated by the coloured star OP-StarFavoritefilled.png. Click Save to save the changes.

Mark_as_favorite_and_save_button.png

This Counter can now be re-used in other Operation Plans.

To re-use this Counter in a different Operation Plan:

  1. Select Add Counter from Favorites in the Operation Plan as shown below.

    Add_counter_from_favorites.png

    The list of Counters that have been marked as Favorite are displayed.

    list_of_add_counter_to_favorite.png
  2. Select the desired Counter to add to your Operation Plan and click Create.

    create_and_favorite_counter.png

    The selected Counter is added to the Operation Plan.

    restored_the_favorite_counter.png

An Event Trigger is the Event whose occurrence triggers the Action.

Event_triggers.png

To create an Event Trigger to a Counter:

  1. Click Add New Trigger.

    Add_new_trigger.png

    A new Event Trigger is created.

    New_trigger.png

    The new Event Triggers have the automatic naming convention Trigger n, where n=1,2,3..... as shown below.

    AddCountertoGOP-ET3.png
  2. You can change the name of the Event Trigger by editing the Name text field as shown below.

    Quarterly_trigger.png
  3. You can add a description to the Event Trigger as shown below.

    Trigger_description.png
  4. Choose the Type of your Event Trigger from the Type dropdown list as shown.

    event_triggers_type.png

    There are eight types of Event Triggers. Based on the Type of Event Trigger selected, relevant fields appear on the page.

    The Types of Event Triggers are discussed in detail here.

  5. Click Save to save the Event Trigger.

    Save_button.png

The Action (Create a Task, Update a Task and Email notification) is made up of instances of one or more Templates.

To add an Action to a Counter:

  1. Click Add New Action in the Action Tab as shown below.

    AddGenCounter-Action1.png

    A new Action appears with an auto-generated ID as shown below.

    Action_id.png

    The details of the selected Action appear.

    result_of_action_id.png
  2. Select the required Action type from the dropdown list as shown below.

    Action_types.png

    The three action types are as follows:

JS Script can be used to define the execution logic for complex scenarios where multiple Event Triggers and Actions are involved. To know more, see Scripts in a Generic Operation Plan.

You can link several fields in the Action of an Operation Plan to variables. These variables allow the re-use of saved values instead of typing them every time.

Variables are discussed in detail here.

A Counter can in turn have sub counters as shown below. In the following example, by clicking Add Counter, you can add sub-counters as required.

Adding_counters_.png

In the below example, Line Maintenance is the Operation Plan .

The Minor repairs is a Counter level 1 which is created under the Line Maintenance Operation Plan. Tire changes is a Counter level 2 which is created under Minor changes. Troubleshooting is a Counter level 3 which is created under Tire changes.

Multiple_counters.png