The Incidents application has a full service capability for use by supervisory personnel and HSE professionals. Create Incident and View Incident can be used by less frequent users who want to simply enter an incident. The Incident Reporter supports a disconnected mobile environment with a simple user interface to report any type of incident using a mobile device. Ticket Template supports the creation of Incident templates.

1. Maximo Oil and
Gas 7.6.1
Maximo HSE
Manager 7.6.1
Overview
Incident
ManagementNote: Screenshots taken from Maximo Oil and Gas, HSE Manager screenshots are identical

2. Applications
covered
This overview covers the following
applications:
•Incidents
•View Incidents
•Create Incident
•Incident Reporter
•Ticket Template
Each application is described in more detail in
the following slides. Process flow charts
used in this presentation are extracted from
Blueworks Live.
The Incidents application has a full service
capability for use by supervisory personnel
and HSE professionals. Create Incident and
View Incident can be used by less frequent
users who want to simply enter an incident.
2

3. Incidents
Example use cases:
1.Injury and Illness reporting
2.Process safety incident reporting
3.Hazard and near miss reporting
4.Safety observation reporting
5.Environmental incident reporting
6.Security incident reporting
3

4. Incident
Management
Process
4
Zoom to view in detail

5. List View
5

6. Incident tab –
Address
Information and
User Information
6
This section can be
minimised or
hidden if service
address is not
used
This section can be
minimised or
hidden if service
address is not
used

7. Incidents tab –
Incident Details
7

8. Incidents tab –
Action Taken,
Persons Impacted
by Incident,
Attachments
8
Can add multiple
persons impacted
including external
persons not in
Maximo
Can add multiple
persons impacted
including external
persons not in
Maximo

9. Person impacted by
Incident Details
9

10. Incidents tab –
Injury and Illness
details
10
This section is dynamically configured to only show when the Incident Type is Injury or Illness
and the Person’s role is Injured/Illness. A user must have specific security access to view this
section.
This is the section
that is dynamically
configured based
on Role and Type
This is the section
that is dynamically
configured based
on Role and Type

11. Incidents tab –
Injury and Illness
Details
11
Injury and Illness
fields are used to
enter the
information
required by safety
authorities when
reporting
incidents
Injury and Illness
fields are used to
enter the
information
required by safety
authorities when
reporting
incidents

12. Incidents tab –
Injury and Illness
Details, Incident
Follow-up
12
Can define follow-
up actions for each
person impacted
by the incident.
Can define follow-
up actions for each
person impacted
by the incident.

13. Incidents tab, Risk
and Consequence,
Multiple Assets,
Locations and CIs,
Dates
13
Global Issue is used
to create a Master
Incident for a group
of incident reports
that are related to
one another. These
incidents can then
be managed
together through
the master incident
if required
Global Issue is used
to create a Master
Incident for a group
of incident reports
that are related to
one another. These
incidents can then
be managed
together through
the master incident
if required

14. Sequence of Events
14
Sequence of
events associated
with incident can
be recorded by
date and time.
With witnesses
and fields for
notes if required in
the Detail section
Sequence of
events associated
with incident can
be recorded by
date and time.
With witnesses
and fields for
notes if required in
the Detail section

15. Activities
15
Can track time on
Activities associated
with the Incident if
required
Can track time on
Activities associated
with the Incident if
required
Activities created
to manage work
associated with
the Incident
Activities created
to manage work
associated with
the Incident

16. Related Records
16
Link to follow-
up Investigation
record
Link to follow-
up Investigation
record
Link to Operator
Log record if the
record is created
by an Operator
Link to Operator
Log record if the
record is created
by an Operator
Link to Work Order if Incident
is associated with
maintenance work or follow
up work is associated with
the Incident
Link to Work Order if Incident
is associated with
maintenance work or follow
up work is associated with
the Incident

17. Solution Details
17
You can call up a known solution
or add solution details directly on
the incident in the fields below
You can call up a known solution
or add solution details directly on
the incident in the fields below

18. Log
18
Manually
created Incident
log entries
Manually
created Incident
log entries
Automatic log entries
from Create
Communication
action or Workflow
Automatic log entries
from Create
Communication
action or Workflow

19. Failure Reporting
19
Initial details of a
failure associated
with an incident
can be recorded
here and will be
copied over to any
Investigation
record associated
with the Incident
where more detail
can be entered
Initial details of a
failure associated
with an incident
can be recorded
here and will be
copied over to any
Investigation
record associated
with the Incident
where more detail
can be entered

20. Specifications
20
The specification
capability can be
used to add
additional
parameters
associated with a
specific
classification of
incident. These
are editable on
the Incident
The specification
capability can be
used to add
additional
parameters
associated with a
specific
classification of
incident. These
are editable on
the Incident

21. Service Address
21
Service address
can be used to
identify the
position of an
incident on the
map tab when
using that
capability
Service address
can be used to
identify the
position of an
incident on the
map tab when
using that
capability

22. High Context
22
The High Context
tab can be used to
enter additional
behavioural
information
associated with an
incident. This can
then be used to
support an analysis
method such as
Critical Incident
Technique
The High Context
tab can be used to
enter additional
behavioural
information
associated with an
incident. This can
then be used to
support an analysis
method such as
Critical Incident
Technique

23. Map
23
When the map
functionality is
enabled this tab can
be used to display a
map of the location
of the incident
When the map
functionality is
enabled this tab can
be used to display a
map of the location
of the incident

24. Incidents Actions
24
Search Solutions
Search for existing
Solutions by
Classification or
description
Search for existing
Solutions by
Classification or
description

25. Incidents Actions
25
View History
View Costs

26. Incidents Actions
26
Create Actions
Apply Incident Template

27. Incidents Actions
27
Show Similar Tickets
Use this action to
quickly find
Incidents with the
same Classification
Use this action to
quickly find
Incidents with the
same Classification

28. Global Incidents
Actions
28
Show Similar Tickets – For a master incident
This provides a quick way of finding incidents related to a
master incident (Global Issue). They can then be related if
required. If the status of the master incident is changed the
child incident status will also change
This provides a quick way of finding incidents related to a
master incident (Global Issue). They can then be related if
required. If the status of the master incident is changed the
child incident status will also change

29. Incidents Actions
29
SLAs
Workflow
SLAs, used in
conjunction with
Escalations provide a
powerful way of
defining response times
and escalation path for
an incident.
Notifications can be
automatically sent and
actions created if a
response time is
approaching or is
missed
SLAs, used in
conjunction with
Escalations provide a
powerful way of
defining response times
and escalation path for
an incident.
Notifications can be
automatically sent and
actions created if a
response time is
approaching or is
missed
Workflow can be
configured to
automate progress
of an incident
Workflow can be
configured to
automate progress
of an incident

30. Incident Reports
The following BIRT reports are provided
with the Incidents application:
1.Incident Details
2.Incident List
3.Log of Work Related Injuries and
Illnesses
4.Summary of Work Related Injuries and
Illnesses
5.Injury and Illness Incident Report
30

31. Incidents Details
report
31

32. Incident List
report
32

33. Log of Work Related
Injuries and Illnesses
report
33
OSHA300 style

34. Summary of Work-
related Injuries and
Illnesses report
34
OSHA300A style

35. Injury and Illness
Incident Report
35
OSHA301 style

36. Create Incident
Self-Service
application
Create Incident use cases
1.Hazards reporting
2.Safety observation reporting
3.General incident reporting
This self-service application is designed to
be used by users who are not regularly
using Maximo and need to be able to
report an incident without having to use
the main Incidents application.
36

37. 37
Create Incident Self-Service application
The self-service Create Incident
application is provided to allow
a user not regularly using
Maximo to quickly create an
Incident
The self-service Create Incident
application is provided to allow
a user not regularly using
Maximo to quickly create an
Incident

38. 38
View Incident Self-Service application
The View Incidents app
provides a self-service style
user interface to allow a user to
quickly review incidents that
they have created
The View Incidents app
provides a self-service style
user interface to allow a user to
quickly review incidents that
they have created

39. Example Self-
Service User Start
Center
39
Created using Ticket Templates and Quick Insert capability with Start Center Portlets
The Self-Service Create and View
Incident apps are allow the customer
the ability to create a self-service HSE
Start Center. It could include any
metrics that are important to the
company as well as quick inserts for
reporting safety observations, hazards,
accidents, injuries or illnesses
The Self-Service Create and View
Incident apps are allow the customer
the ability to create a self-service HSE
Start Center. It could include any
metrics that are important to the
company as well as quick inserts for
reporting safety observations, hazards,
accidents, injuries or illnesses

40. Ticket Templates
Example use cases:
1.Incident Template
2.Service Request Template
3.Investigation Template
40

41. Templates tab
41

42. Template tab
42

43. Specifications
43

44. Incident Reporter
Example use cases:
1.Hazard reporting
2.Safety observation reporting
3.General incident reporting
This Maximo Anywhere app supports both
connected and disconnected operation. It
is supported on IoS, Android and Windows
operating systems. All data maps to the
Incidents application and is automatically
populated when an Incident is created
44

45. Log in screen
45

46. Incident Category
domain
Safety Observation
Type domain
Incident Type
domain
Create New Incident, What Happened? screen
Domains are
configurable
and
automatically
loaded from
Maximo
Domains are
configurable
and
automatically
loaded from
Maximo

47. Attachment Details screen

48. State domain
Where did it happen? screen

49. Person Role domain
Who was involved? screen

50. Action Taken
Action taken screen

51. 51
Action to allow a user to add photo from gallery
Pick from Gallery Action

52. 52
My Incidents
screen