Operator Log Application

Overview

Shift log records contain details about shift changeovers, equipment changes, production
losses, and near misses that occur during a shift.

In the Operator Log application, one can perform the following activities:

 Record individual log entries and details about shift teams

 Use templates to quickly populate shift log records with frequently used data

 Record production parameters that are based on the classification of production activities

 Record manual meter readings

 Generate / follow-up defect and incident tickets and service requests

Status of log records

Shift logs can have a status of Draft, Active, or Inactive.

DRAFT: The log record is being developed or reviewed. This status is the default status of a
new log. You can change the record. You can create incidents, defects, service requests, and
communications, and you can record meter readings. You can delete the record if it is not
associated with other records.

ACTIVE: The log is available to other records and applications. You can change some, but not
all, fields on the record. You cannot delete the record. You can create incidents, defects, service
requests, and communications, and you can record meter readings.

INACTIVE: The log is not available to open records. You cannot change the record. You can
delete the record if it is not associated with other records.

Log templates

User can quickly populate shift logs records by using templates, which contain frequently used
details. User can create a template from a shift log or run log of any status. (Template format -
Excel?)

User can perform the following actions to create and use templates:

Action Use
After user add details and team information to a shift log, use the Template >
Generate action to create a template that contains that information. User can modify
Generate the template before you save it.
Edit Use the Template > Edit action to add, modify, or delete the information that is in a
 log template. User can delete a log template that has not been applied to any shift log
or run log record.
After you create a shift log or run log, use the Template > Apply action to select a
template and populate the shift log or run log with the information that is on that
template. The template overwrites any corresponding values that are in the shift log
Apply or run log. The status of the shift log or run log must be Draft or Active.

Types of tickets

The terms ticket refer to different types of records. The various ticket records are used for
different purposes.

Ticket records

Defect: Document a deviation from perfect operation. Defects do not have a health, safety, or
environmental impact and they do not necessarily require intervention or maintenance.

Incident: Document a deviation from an expected standard of operation. Incidents have a

health, safety or environmental impact and they require tracking and reporting from a regulatory
or compliance perspective.

Investigation: Address an unresolved incident or defect. Record results of an after-action

review, a root cause failure analysis, or a failure mode effect and criticality analysis.

Problem: Capture an unknown, underlying cause of one or more incidents. Problem records
are generally used in service desk applications that relate to information technology.

Service request: Document service requests from customers or requesters.

Types of record relationships

Tickets can have different types of relationships.

Originating & Follow-up

A pair of tickets can consist of an originating record and a follow-up record. A follow-up
relationship associates records for information purposes only. For example, you might create a
follow-up ticket when you complete a job, but notice that additional work is needed on the same
asset or location.

The original record has a relationship type of ORIGINATOR and the new record has a
relationship type of FOLLOWUP.

Related

One can relate the current record to one or more tickets in a related record relationship.

A RELATED record relationship is for information. Related record relationships can be one to
many, and they do not represent record hierarchies.