This refers to the management of any events across different functionalities for instance Safety, Health, Environmental, Security, Maintenance, Operations and Contracts.

Event definition can be defined as the set up of default event templates regarding any instance or occurrence of anything that can be a planned or added as an adhoc event. Events can be a specified condition/action that triggers or suppress a demand and the commencement of default proceedings.

An Event Template definition determines the generic composition for a maintenance task/action to be performed on an object and contains information about required resources, activities and organisations that can perform the actions/tasks. Once created, the templates can be used instead of the registration of every single task as and when required. The source for an event template can be documentation such as maintenance manuals, technical instructions or service/modification information. Standard Maintenance Tasks must be defined for every event template. These defined tasks are used as standard templates to facilitate uniform tasks execution and task history analysis. It is also a means to do life cycle planning.

Use this form to create and maintain a register of all generic events templates that can be defined with a class of planned, adhoc or administration.

Note

Adhoc is used in an unplanned/unexpected event, refers to management of problems re-actively without reference to a strategic plan.

Create a calendar event

Event templates can be set up to schedule tasks at calendar intervals, meter intervals or a combination of both. The procedure below describes the set up for calendar tasks.

1.      Click Setup > Event > Event Definition (Event definition form open).

OR

Click Periodic > Event Definition (Event definition list page open).

2.      Click New button (From the FORM view).

3.      The following is an example for Event Definition form view.

 

4.      Click in the Event code field and add an event code, click Event Description field, add a description for the event.

5.      Click in the General, Setup FastTab, in the Type field, select 'Maintenance'.

Click in the Class, field, select 'Planned'.

This will indicate that the event type/class is for preventative/planned maintenance.

6.      The Contract type and Execution type fields will not be selected and is not mandatory.

NOTE: Select the type that specifies the contract. If event type is of type 'contract' this field is selected, OR select the type that defines the execution type. If event type is of any type except 'contract' this field is selected.

7.      The Forced indicator will not be selected at this stage because this field is used for the forecasting to decide if a task is scheduled for a non-work day.

8.      The Fixed indicator will not be selected at this stage because if this field is selected the frequency cycle is fixed.

9.      Add Duration (hours) to indicate what the planned duration for this event object task is. Always add a duration as the schedule function requires this for calculating planned start and end dates.

10.  The Planned no of occurrence will always default to '0' and means that this occurrence will repeat itself for as long as the Specific is used/in commission. Any other value in this field will indicate how many times an event should be repeated.

11.  Save the record by pressing CTRL+S.

12.  Click the Event object button to add objects for which this event will be scheduled. Multiple objects can be added.

13.  Delete button if you want to delete a selected record. Important note to remember is that an event record cannot be deleted if it is linked to an event object. The event object and all related records and history must be deleted.

Create a event object

1.      Click Event object from the Event definition form.

2.      The following is an example for Event Object form view.

 

3.      Click Event Object New button.

4.      Click in the Identification, Identification FastTab, in the Object code field and add an object, from the list of available objects. Structure code and Object description will be automatically added from the object table. Event description and Event code will be added from the Event definition form.

5.      The Planned no of occurrence will always default to '0' and means that this occurrence will repeat itself for as long as the Specific is used/in commission. Any other value in this field will indicate how many times an event should be repeated.

6.      Add Duration (hours) to indicate what the planned duration for this event object task is. Always add a duration as the schedule function requires this for calculating planned start and end dates.

7.      The Forced indicator will not be selected at this stage because this field is used for the forecasting to decide if a task is scheduled for a non-work day.

8.      The Fixed indicator will not be selected at this stage because if this field is selected the frequency cycle is fixed.

9.      Save the record by pressing CTRL+S.

10.  Click the Event budget button. This function allows you to add all resources that may be required to do the task. The budget resources can later be edited when the forecast event is transferred to an Execution order.

11.  Delete button if you want to delete a selected record. Important note to remember is that an event record cannot be deleted if it is linked to an event object. The event object and all related records and history must be deleted.

Create Event Budget

1.      Click Event budget from the action pane on Event object form.

2.      The following is an example for Event budget form view.

 

3.      Click New button to create a new event budget record.

4.      Add Resource type by selecting a type from the available drop down list.

Add Resource code by selecting a type from the available drop down list. The Resource codes that are displayed on the drop down list will be only from the 'Type' that was selected previously.

Description will be automatically added from the resource table.

5.      Click in the Setup, FastTab, in the Billing indicator field and tick indicator if this resource will be billable. Bill recurrence, In advance and Pricing model will only be available if the event type is type 'contract'.

6.      The Delete allowed indicator defines if the operational record (Execution or Contract) may be deleted. Tick for the record to be deleted.

7.      The Disclosed indicator field will be ticked when the record detail will be disclosed on the invoice to the customer.

8.      Add Roll up resource type by selecting the resource type with which this resource record must be rolled up to when invoices are displayed.

9.      Add Roll up resource code by selecting resource code with which this resource record must be rolled up to when invoices are displayed.

10.  Click in the Values, Duration FastTab, in the Duration UOM field and select the unit of measure for the duration or time the resource is required for. This is only used for resources of type service, trade and support equipment. Add in the Default duration the default time the resource will be allocated to the work order, and Duration is the expected time the resource will be allocated to the work order.

11.  Click in the Values, Quantity FastTab, in the Qty UOM field and select the type of Unit of Measure to define the quantity. Describes the unit in which resource quantities will be required to perform the task. Add in the Default QTY field typical where a resource type is a trade or a service, and Budget QTY is a numerical value to indicate quantity of resource required.

NOTE: Depending on the type of resources, different values may be required e.g. if it is of type “Item”, only the “Quantity” section under “Values” are required. If type “Trade” was selected, then both the “Duration” and “Quantity” values are required. The reason for the latter is that you need to tell how many people of a specific trade are required to do the job and how many hours they will spend to do the task etc.

12.  Save the record by pressing CTRL+S and Close the Event budget form.

13.  Click Event object > Setup > Event Characteristics menu button. This is an optional function to enable users to add additional characteristics, tasks lists, functions etc. to a template.

Create Event Characteristics

1.      Click Event object > Setup > Event Characteristics menu button. This is an optional function to enable users to add additional characteristics, tasks lists, functions etc. to a template.

2.      The following is an example for Event characteristic form view.

 

3.      Click New button to create a new event characteristic record.

4.      The values from the drop down list will be a result of the related Characteristics that was created in base characteristic function. Depending on the Variables that was set up in the Characteristics, users may have to add values such as dates, numbers, free text etc.

The Indicators will impact future actions. If Print Indicator was selected, the Characteristics will be printed on the work order card. Mandatory indicator will force users to add data. History indicator will be adding the changes/detail of the characteristic to history etc.

NOTE: Add multiple Characteristics where OR if applicable.

5.      Save the record by pressing CTRL+S and Close the Event characteristics form.

Create Event Actions

1.      Click Event object > Setup > Event Actions menu button. This function is optional and will allow users to add actions required to do this job. This may include actions and sequences to describe individual tasks e.g. "01-Drain Oil", "02-Remove Oil filter", "03-Add new filter", "04-Add new oil" etc.

2.      The following is an example for Event Actions form view.

 

3.      Click New button to create a new event actions record.

4.      The values from the drop down list will be a result of the related Characteristics that was created in base characteristic function. Depending on the Variables that was set up in the Characteristics, users may have to add values such as dates, numbers, free text etc.

The Indicators will impact future actions. If Print Indicator was selected, the Characteristics will be printed on the work order card. Mandatory indicator will force users to add data. History indicator will be adding the changes/detail of the characteristic to history etc.

NOTE: Add multiple Characteristics where OR if applicable.

5.      Save the record by pressing CTRL+S and Close the Event characteristics form.

Create an Event Permit

This form is used to define specific permits or certificates for an event. If permits are specified for an event, the system will validate that the required permits are issued and linked to a job before the job may be executed.

1.      Click Event Permit from the action pane on Event object form.

2.      The following is an example for Event permit form view.

 

3.      Click New button to create a new event permit record.

4.      Add permit code by selecting from the available pre-definable list.

Description will be automatically added from the permit table.

5.      Add Valid duration (days) by adding the number of days that the permit is valid.

6.      Save the record by pressing CTRL+S and Close the Event permit form.

Create a Related Event

Use this form to create and maintain a hierarchy of events by defining the relationship between events. Typically a parent event will be linked to a child event to form the master event template. The relationship between the events can be defined by hierarchy, suppression or triggers.

Hierarchy: Event hierarchies are applicable to a complex scenario where a network of tasks exists, i.e. the remove and install tasks are not performed one after another but a number of tasks are performed between the remove and install.

Suppression: Event Suppressions are defined for a scenario where the occurrence of a maintenance event also includes the occurrence of another planned maintenance event. It therefore contains the same maintenance actions as planned as a separate event and should therefore suppress the contained event.

Triggers: Event triggers are defined for specific maintenance actions where the occurrence of a maintenance event also needs the occurrence of another maintenance event after the first. The creation of such an event on the maintenance plan automatically triggers the other maintenance event to occur as well. It also includes the settings for the triggering of condition based events.

1.      Click Related Event from the action pane on Event object form.

2.      The following is an example for Related Event form view.

 

3.      Click New button to create a new related event record.

4.      Add child event by selecting from the available pre-definable list.

Object code child will be automatically added from the event table.

5.      Structure code child field will be added from the child event information.

6.      Event relationship field will define the type of relationship between events, and will be added automatically, e.g. Hierarchy, suppression or triggers.

7.      Save the record by pressing CTRL+S and click on event related age button.

Create a Related Event Age

Use this form to create and maintain the suppression/triggers of events by defining the event related age between events. Use this to define the ageing parameters for the related event. Ageing parameters are used to measure and record the age of object, for scheduling of maintenance or administration of warranties.

Task Suppressions are defined for a scenario where the occurrence of a maintenance event also includes the occurrence of another planned maintenance event. It therefore contains the same maintenance actions as planned as a separate event and should therefore suppress the contained event.

Task triggers are defined for specific maintenance actions where the occurrence of a maintenance event also needs the occurrence of another maintenance event. The creation of such an event on the maintenance plan automatically triggers the other maintenance event to occur as well. It also includes the settings for the triggering of condition based events.

1.      Click Event Related Age from the action pane on Related Event form.

2.      The following is an example for Event Related Age form view.

 

3.      Click New button to create a new event related ageing record.

4.      Object code parent, Parent Event, Parent structure code, Object code child, Child event, Structure code child, will be automatically added from the event object record.

5.      Select the UOM field from the available list. Available values are METER, CALENDAR and QUANTITY.

6.      Add UOM code field that will be display available values from the UOM that was selected.

7.      Add Lag field that define lag or time/meter lapse between the main event and the triggered event.

8.      Add Negative variance value as number of days. (If the suppressed event is scheduled to occur within the defined variances from the occurrence of the main event it will be suppressed. If it is scheduled to occur outside the defined variances from the main event, it will not be suppressed by the occurrence of the main event. Note that suppression variance is always expressed in days, regardless of UOM’s.)

9.      Add Positive variance value as number of days. (If the suppressed event is scheduled to occur within the defined variances from the occurrence of the main event it will be suppressed. If it is scheduled to occur outside the defined variances from the main event, it will not be suppressed by the occurrence of the main event. Note that suppression variance is always expressed in days, regardless of UOM’s.)

10.  Save the record by pressing CTRL+S and click on close button.

Create an Event interval

This form is used to define the interval/s for programmable events. Multiple intervals may be defined per event. The forecasting function will forecast a planned occurrence for the unit of measure that will cause the earliest occurrence. Maintenance events are performed according to prescribed criteria at pre-determined intervals.

1.      Click Event Interval from the action pane on Event Object form under Setup.

2.      The following is an example for Event Interval form view.

 

3.      Click New button to create a new event interval record.

4.      Description, Event code, Object code, Structure code, UOM, UOM code, will be automatically added from the event object record.

5.      Add Firm interval field that indicates the interval between two events expressed in terms of the selected UOM. This frequency is used where the events that are scheduled will be used in the scheduled maintenance of the object. i.e. Scheduled events based on the prescribed frequency of the event on the object.

6.      Add Budget interval field that indicates the budgeted interval between two events expressed in terms of the selected UOM. This frequency is used where the events that are scheduled will be used in the budgeted maintenance of the object only, i.e. adhoc events (predicted failures), based on the MTBF (Mean-Time Between Failures) of the object.

7.      Add First occurrence that is the first meter reading on which the event must occur. If left 0 the first occurrence of the event will be forecast as the interval defined for the event.

8.      Add Final occurrence that is the final meter reading for a programmable event. This field should be left blank if the event must be scheduled indefinitely. If a value is supplied, the event will be scheduled up to the value supplied and never again.

9.      Add Positive latitude that defines the number of units for which the event may be legally performed earlier than planned.

10.  Add Negative latitude that defines the number of units for which the event may be legally performed later than planned.

11.  Save the record by pressing CTRL+S and click on close button.

Create a responsible organisation

1.      Click Responsible organisation from the action pane on Event object form.

2.      The following is an example for responsible organisation form view.

 

3.      Click New button to create a new responsible organisation record.

4.      Add Type by selecting between Maintenance Plan and Maintenance Execution.

Object code and Structure code will be automatically added from the event table.

5.      Add Organisation by selecting the responsible organisation from the drop down available list of organisations.

Organisation structure will be added by lookup information from the organisation.

6.      Add Preference by selecting a value to indicate if one organisation is preferred. The smallest value is most preferred.

7.      Save the record by pressing CTRL+S and Close the form.