5. Operating Policy
tab – Upper half
5
Identify what drives
the policy, how it is
implemented, how
performance is
monitored and who
approved the policy
Identify what drives
the policy, how it is
implemented, how
performance is
monitored and who
approved the policy
6. Operating Policy
tab – Policy
Established By
section
6
Provides a
reference point
for who
established the
policy
Provides a
reference point
for who
established the
policy
7. Where Used
7
Where used sub tabs
show where the
policy is applied and
how it is applied
using Job Plans and
PMs
Where used sub tabs
show where the
policy is applied and
how it is applied
using Job Plans and
PMs
10. Log tab
10
Communication Log generated automatically
from Create Communication or Workflow
actions
Communication Log generated automatically
from Create Communication or Workflow
actions
Manually
generated log
entries
Manually
generated log
entries
13. Operating Policy
Statuses
•Draft – All fields editable
•Active – All fields read only (other than
Log tab), must be in this status to be
associated to another application
•Inactive – All fields read only, in this
status cannot be associated to another
application
13
14. Job Plan –
Operating Policy
and Assurance
Activity fields
14
If an Operating Policy
that has Assurance
Activity checked is added
to a Job Plan then
Assurance Activity on the
Job Plan is automatically
checked but can be
edited
If an Operating Policy
that has Assurance
Activity checked is added
to a Job Plan then
Assurance Activity on the
Job Plan is automatically
checked but can be
edited
17. Operating
Procedures
The Operating Procedures application
provides a means to incorporate key
operating procedures into Maximo. In many
cases this may be summary information or
elements of the procedure which may be
helpful to be seen directly in Maximo. The
detailed operating procedures will
usually be held in separate documents,
often in document management systems.
These can be linked to a Maximo Operating
Procedure as attached documents where
required.
17
21. Procedure Lines
tab
21
Use Details section if
further details are
required using Long
Description or Details
mult-line text field
Use Details section if
further details are
required using Long
Description or Details
mult-line text field
22. Log tab
22
Manually
generated log
entries
Manually
generated log
entries
Communication Log generated automatically
from Create Communication or Workflow
actions
Communication Log generated automatically
from Create Communication or Workflow
actions
25. Operating
Procedure
Statuses
Draft – All fields editable
Active – All fields read only (other than
Log tab), must be in this status to be
associated to another application
Inactive – All fields read only, in this
status cannot be associated to another
application
25
34. Operator Tasks
•Operator Tasks is a version of the Tasks
and Activities application with additional
Oil and Gas/HSE specific fields designed
for use by Operators carrying out work on
behalf of other departments including
maintenance and HSE
•Manages operator tasks which originate
from 1/Work Order Tasks or 2/Activities
on Ticket based applications
•Designed for single specific task use case
•Often used in conjunction with workflow
34
35. Creation of
Operator Tasks
•Operator Tasks are created using other
applications outside of the Operator Task
application:
• Work Order Tracking
• Ticket based applications with Activities
tabs
• Tasks are created using Work Order
Tracking and have a Task extension
number (-XX)
• Activities are created in the Activities
tab of Ticket based applications and
have a prefix ‘T’ and no extension number
• Activities and Tasks are Work Orders of
35
36. Note on difference
between records
originating from a
Work Order and
records originating
from Ticket based
applications
•On an Operator Task record originating
from a Work Order a resource tab is
displayed and you cannot add a new task.
This is because you cannot have a task
below a task as the first task would
become a child WO and would be filtered
from operator tasks
•For an Operator Task record originating
from a Ticket based application the Plans
and Actuals tabs are displayed as you are
allowed to create a task because you
cannot have a parent/child relationship in
this case
36
46. Log tab
46
Communication Log generated automatically
from Create Communication or Workflow
actions
Communication Log generated automatically
from Create Communication or Workflow
actions
Manually
generated log
entries
Manually
generated log
entries
50. Footnote to
Operator Tasks
The Operator Task application that is available is a
subset of Work Order Tracking
functionality to support the single task specific use
case.
For example, a user is assigned Task 20 on a work order.
This task is asking an
Operator to check for steam leaks on a boiler. When this
assignment appears in their
inbox, they can click on that assignment and be brought
to the Task application.
At that point, they may simply select the “start” timer
to indicate that they have
now commenced work on the task assigned to them.
Similarly, when the task is
complete, they may select the task in the same manner,
choose the “stop” timer,
and have the system automatically post their elapsed
time against the work
order, including the extended cost of their labour. This
entire booking will be
visible within the Resources tab. All screens within this
application have
been pared down to maintain simplicity.
50