Maximo Oil and Gas 7.6.1 HSE: Incident Management overview

  • View
    424

  • Download
    17

  • Category

    Software

Preview:

Citation preview

Maximo Oil and Gas 7.6.1Maximo HSE Manager 7.6.1OverviewIncident ManagementNote: Screenshots taken from Maximo Oil and Gas, HSE Manager screenshots are identical

Applications coveredThis 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.

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.

Incident Investigation is covered in a

separate presentation.

2

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

Incident Management Process

4

Zoom to view in detail

List View

5

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

Incidents tab – Incident Details

7

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

Person impacted by Incident Details

9

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

Incidents Actions

24

Search Solutions

Search for existing Solutions by

Classification or description

Search for existing Solutions by

Classification or description

Incidents Actions

25

View History

View Costs

Incidents Actions

26

Create Actions

Apply Incident Template

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

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

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

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

Incidents Details report

31

Incident List report

32

Log of Work Related Injuries and Illnesses report

33

OSHA300 style

Summary of Work-related Injuries and Illnesses report

34

OSHA300A style

Injury and Illness Incident Report

35

OSHA301 style

Create Incident Self-Service applicationCreate 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

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

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

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

Ticket Templates

Example use cases:

1.Incident Template

2.Service Request Template

3.Investigation Template

40

Templates tab

41

Template tab

42

Specifications

43

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

Log in screen

45

Incident Category domain

Safety Observation Type domainIncident Type

domain

Create New Incident, What Happened? screen

Domains are configurable

and automatically loaded from

Maximo

Domains are configurable

and automatically loaded from

Maximo

Attachment Details screen

State domain

Where did it happen? screen

Person Role domain

Who was involved? screen

Action Taken

Action taken screen

51

Action to allow a user to add photo from gallery

Pick from Gallery Action

52

My Incidents screen

Recommended