Module set-up and configuration:Change Management

1. Maximo Oil and
Gas
Maximo HSE
Manager
Module set-up
and
configuration
Change

2. This presentation covers set up and
configuration for the following two
applications
MOC
Improvements
2

3. Management of
Change – Edit Rules
3

4. Management of
Change – Additional
Options
4
MOC Review/Approval/Authorised
Person Requires Authorised Person –
Check this box if you want to allow
only Persons who are authorized in
People (Oil) Details tab to be added
on Review, Approval, Authorize table
windows. If this is the case go to
People (Oil) Details tab and check the
Authorised for MOC
Review/Approval/Authorization box
for each Person with authorization.
MOC Review/Approval/Authorised
Person Requires Authorised Person –
Check this box if you want to allow
only Persons who are authorized in
People (Oil) Details tab to be added
on Review, Approval, Authorize table
windows. If this is the case go to
People (Oil) Details tab and check the
Authorised for MOC
Review/Approval/Authorization box
for each Person with authorization.

5. Improvements –
Edit Rules
5

6. Improvements –
Additional Options
6

7. Oil and Gas Options
- History Period
7
This sets the default history period
used in the ‘View Failures and
Deferrals’ dialog box. Default is
365 (days), this can be adjusted as
required.
This sets the default history period
used in the ‘View Failures and
Deferrals’ dialog box. Default is
365 (days), this can be adjusted as
required.

8. MOC Request
Business rules
1.If Temporary? field is checked then Temporary Until
date becomes mandatory.
8

9. MOC business rules
1. Edit rules follow standard Maximo edit rules
for change in status. In addition MOC cannot be
changed to Closed status, unless all pre and
post MOC actions have been completed and all
Reviewers, Approvers and Authorizers listed
have completed their work.
2. Person records must be Active to be applied to
MOC on Review and Approve and Authorize tabs.
This also works in conjunction with optional
authorized person setting in People (Oil).
3. The same person cannot be listed as a
Reviewer, Approver or Authorizer more than
once on each table window.
4. The same person cannot be a Reviewer and
Approver.
5. Only Standard Actions with Timing field set to
Pre-MOC can be added to Pre MOC Actions tab.
6. Only Standard Actions with Timing field set to
Post-MOC can be added to Post MOC Actions tab.
7. If Temporary? field is checked then Temporary
Until date becomes mandatory.
8. All Post-Start actions must be completed
before MOC status can be changed to closed.
9

10. Notes on set up and
configuration of
MOC
The following slides provide notes on set-
up and configuration of MOC
10

11. Domains
The standard domains that come with Maximo Oil
and Gas provide examples of the type of values a
customer may wish to use. These domains are
normally updated by the customer to add their own
specific terminology.
1. Domain PLUSGMOCTYPE – This domain is applied to the
MOC Type field. It’s a Synonym Domain so values can
be only be modified using synonyms
2. Domain PLUSGMOCCAT – This is an ALN domain applied to
the Category field. It can be edited for customer
specific values
To add synonyms or edit existing values Go To
System Configuration > Platform Configuration >
Domains. Oil and Gas Domains are all prefixed with
PLUSG
11

12. Owner Groups and
Communication
Templates
Owner Groups
You may want to set up MOC specific Owner Groups for
use on MOC Request and MOC applications. Review existing
Owner Groups to determine if new groups are needed.
Owner Groups and the Owner field are helpful in
clarifying ownership of a record and can be used in
conjunction with Maximo Workflow to provide a greater
level of process automation. In particular you might
want an MOCADMIN group or similar. Go To Administration >
Resources > Person Groups to set these up.
Communication Templates
The Create Communication action on the Select Action
menu for MOC Request (Oil) and MOC (Oil) can be used to
distribute these records for review, approval and
authorisation. Standard communication templates
facilitate this process by allowing the user to apply
the template rather than create a completely new
communication each time a record is distributed to other
users. Go To Administration > Communication Templates to
set up the templates.
12

13. Standard Actions and
Standard Action
Groups
Standard Action Groups
Standard Actions are used in MOC (Oil) to add a list of
‘standard actions’ to the MOC Pre-Start Actions and MOC
Post-Start Actions and Closure tabs. These tabs are
used to identify actions associated with the MOC and
allocate clear responsibility for those actions.
Standard Actions should be set up prior to use of the
MOC (Oil) application using the Standard Actions (Oil)
application. This application is a System/Org/Site design
such that records can be created at System,
Organization or Site level. MOC records are at Site level
so if you want a Standard Action to be used by all
Maximo Organizations and Sites, create at System level
(default). Add Site or Organization to restrict use of an
action to a specific Organisation or Site.
Standard Actions of type review action can be used to
populate the Pre Start Safety Review tab using a
question and answer format that can also be acored.
Some typical Standard Actions are provided for guidance.
To set up your own Standard Actions Go To Planning >
Standard Actions (Oil). The Type Category and Timing field
all have Domains which can be set up with
synonyms/values to correspond with customers’
terminology. Set Timing field to Pre-MOC or Post-MOC (or
equivalent synonym) to determine whether a Standard
Action is used only on Pre or Post-MOC Action tab, set to
Default to use on both
A group of Standard Actions can be set up in Standard
Actions to allow a user to add a related group of
Standard Actions to the MOC record. 13

14. Workflow and SLAs
The MOC Request (Oil) and MOC (Oil) applications are
both set up to use Maximo Workflow and SLA Manager. It
is not necessary to have either Workflow or SLAs in
place to use the MOC Request (Oil) or MOC (Oil)
applications but we anticipate that customers may want
to the option to automate certain regularly used
processes through workflow. For example, initiating
review of an MOC through change of status.
SLA Manager could also be used to define an SLA
that requires response to the MOC Request or MOC within
pre-defined parameters and can then be used, in
conjunction with Escalations and Actions, to provide an
automated response if the pre-defined parameters are
not met.
A good approach may be to introduce workflow and
SLAs as a second phase of the implementation when
regularly used roles and processes are well defined
and the benefits of automating part of the process can
be evaluated.
14