Last Updated on November 19, 2022 by maximosecrets
The Maximo Health, Safety & Environment (HSE) product includes 31 new applications and 20 application clones some of which have considerable additional functionality, e.g. Locations (HSE). This document provides a brief description of each new application, those which are unique to the HSE product. For the other applications see the posts called Maximo Applications, there are five of them.
Assets Module
| Application | Description |
| LocationA physical place where assets exist and where work can be performed. More Profile (HSE) | This application is used to create a profile over time of Production, Persons on Board or Working Time. The data can then be used with actual data collected in Maximo. For example, the allowable Persons on Board might be used as a constraint when performing maintenance work in a work area or a platform. |
Change (HSE) Module
| Application | Description |
| Improvements (HSE) | An improvement is often a project with planned work that is used to show the benefits of the work to be undertaken. It can also be used to show the benefits of an improvement in a business process. Actuals can be recorded to see whether the benefits were realised. |
| MOC Requests (HSE) | The MOC Request application is used to initiate a change, the Management Of Change (MOC) process. This application is a subset of the functionality in the MOC application and is used up to the point when the MOC Request is approved. |
| MOC (HSE) | The Management Of Change (MOC) application handles the full lifecycle of a change from creation to review and approval, authorisation and then closure. Some client sites will use this application to create the request for change instead of the MOC Requests application. |
Operations Module
| Application | Description |
| Operator Log (HSE) | Operator Logs may be used for Shift Logs to aid shift handovers, Commissioning Logs and Monthly Engineering Logs. They are discreet records but may exist as part of a Log Book. They may contain details of production losses, equipment changes or near misses that occurred during the shift. |
| Operator Tasks (HSE) | Operator Tasks are activities set by Maintenance which are performed by operators rather than maintenance personnel. These are discreet Activities and Tasks and are created from various ticket and work order based applications, records cannot be created directly in this application. |
| Operating Policies (HSE) | Operating Policies may be created for Regulatory Compliance reasons, as a result of a Risk Assessment or due to asset failure. They are then implemented on a work order by associating them with a PM or Job Plan, Asset or Location. |
| Operating Procedures (HSE) | The Operating Procedures application might be used to record a maintenance, permit or operating procedure, or a performance standard. There could be various categories, design, commissioning, a test procedure, a startup/shutdown procedure or a procedure used during inspection. Operating Procedures are used in many HSE applications. |
| Bypass Management (HSE) | Bypass Management is the process of evaluating and mitigating the risks associated with bypassing safety critical assets in order to perform maintenance or repair. For example welding in the area of a fire detector might set off the fire alarm, therefore the fire alarm panel may need to be bypassed for a period. |
| Log Book (HSE) | Operator Logs can be grouped together into a Log Book around a particular common work location and/or shift. A Log Book exists for a period of time, for example a calendar year. |
| Operational Actions (HSE) | Operational Actions is a simple application used to pull together all Standard Actions into one place and to provide navigation to the originating application. |
Planning Module
| Application | Description |
| Asset List (HSE) | An Asset List is a set of Locations and/or Assets and is stored in the same tables as a Route. They are used for Inspections and Campaigns and are used in conjunction with the Action Tracking application. |
| Condition for Work (HSE) | The Condition for Work is a simple application. The Condition for Work records are often used in conjunction with the Reason for Work which is entered in the Prioritization Matrix application. Together they are used on a work order. The Condition for Work may also be referenced on a Permit to Work or in Isolation Management. |
| Regulatory Compliance (HSE) | The Regulatory Compliance application is used to record external and internal regulations, performance standards and their certifying authorities. A regulation can be used or referenced in many HSE applications. |
| Prioritization Matrix (HSE) | The Prioritization Matrix is based on the Reason for Work and the criticality of the Location or Asset to derive a priority which is used on a work order. The Reason for Work is often used in conjunction with the Condition for Work but is not used in a Permit to Work or in Isolation Management. |
| Benefits and Losses (HSE) | The Benefits and Losses application is used to support both benefit identification and loss reporting. |
| Standard Actions (HSE) | Standard Actions are used in many HSE applications. There are two styles, a checklist or a question/answer style called Review Actions. For example, work order preparation activity checklist, or a Risk Assessment hazard review. |
| Standard Action Groups (HSE) | A Standard Action Group is a set of Standard Actions and can be applied wherever Standard Actions are applied. |
Safety Sub Module of Planning Module
| Application | Description |
| Permits and Certificate Types (HSE) | This application is used to define a type of certificate or permit. In conjunction with Certificates these records are used widely across the HSE applications. For example; asset commissioning certificates, test certificates, material inspections, environmental permits, hot work permits, working at height permits, etc. |
| Permit to Work (HSE) | Permit to Work (PtW) are created in order to perform work safely. They have a life cycle from creation through review and approval, issue and acceptance, handback and cancellation. Various hazards, hazardous materials and required isolations will be identified as part of the PtW. There may also be required gas tests to be performed. |
| Risk Assessments (HSE) | Risk Assessments can be used for assessments of job safety, operational risk, environmental impact or an assessment of business risk. Risk Assessments are referenced in many HSE applications. The Risk Assessment may reference Hazards, Precautions and Tagout/Lockout rules. |
| Risk Matrix (HSE) | A Risk Matrix is a matrix of consequence, severity and likelihood values to derive a risk priority and ranking. The Risk Matrix is used in assessing the risk of a hazard as part of a Risk Assessment. |
| Isolation Management (HSE) | Isolation Management is used for mechanical, electrical and process isolations of assets and operating locationsA location with a location type of OPERATING. More. They are similar to Permits to Work and the records are stored in the same tables, but with the focus on the creation and life cycle processing of the isolation certificate. |
Safety & Quality Module
| Application | Description |
| Certifications (HSE) | Certifications are used for both certificates and permits. They are used widely across the HSE applications; equipment, material, person, inspections, acceptance tests, regulatory permits, environmental consents, construction and commissioning certificates, etc. The certification record is generally linked to a Permit and Certificate Type. |
| Audit and Survey (HSE) | An audit is used to verify that external or internal regulation, operating policies and operating procedures are being complied with, for example a safety, process or vendor audit. Surveys can be used for various reasons, for example a Condition Survey. They are more likely to be performed in the context of a location, asset or person (self assessment). |
| Defects (HSE) | A Defect is used for recording issues with assets that may either need to be investigated, corrected by creating a work order or which remain unresolved until a time when multiple defects are corrected perhaps as part of an outage or shutdown. A Defect uses the Incident view. |
| Incidents (HSE) | This application is used for incidents with a Health, Safety or Environment impact. An Incident may be an injury/illness, a safety, environmental or security incident, a near miss, a spillage, a safety observation or a failure in a safety process. |
| Investigations (HSE) | Investigations are used for determining the root cause of an Incident or Defect and whether a change is needed in order to prevent or minimise the impact of a reoccurrence. It uses the Problem view of a Ticket. |
Self-Service Module
Self-Service Incidents Sub-Module
| Application | Description |
| Create Incident (HSE) | A self-service application for creating an Incident. Add details about what happened, where it happened, who was involved and what actions were taken. Documents can be attached to the Incident. The details of the Incident can accept rich text formatting, url links and embedded images. |
| Review Incidents (HSE) | Self-service users can search for and review the Incidents that they created or which were created on their behalf. |
Work Orders Module
| Application | Description |
| Action Tracking (HSE) | The Action Tracking application is used for tracking the status of actions between different parties. For example, manage safety bulletins, safety meeting actions, compliance actions, etc. Action Tracking can also be used for managing campaigns on multiple similar assets. |
Leave a Reply