All learning series · Manage add-on · Part 1
Health, Safety and Environment
Connect a hazard, its assessment, required controls and corrective work.
Start here
Confirm this product is ready, then use the lesson. The readiness checks are the gate for configuration, for a first journey and for production.
- Are you ready to use Health, Safety and Environment? Licensing and AppPoints, the records that must exist, and three checklists.
- Basics
- Configuration
- Practical example
- Practice and verify
- Advanced concepts
Are you ready to use Health, Safety and Environment?
HSE records the incident, the risk and the action. Oil and Gas uses a different set of modules for a similar shape of work. Entitle and configure HSE on its own.
Before configuration
HSE is a Manage add-on at Premium or Limited. Create Incident, Review Incidents and a view-only management-of-change request are self-service at 0 AppPoints. Investigators and administrators are not on that list.
Before the first successful journey
A site and a location, a risk matrix the process owner accepts, and three roles: reporter, reviewer, action owner.
Before production use
Classifications, the matrix and the action workflow have owners. A training incident is not a regulatory filing.
Licensing, entitlement and AppPoints
HSE is a Maximo Manage add-on. The MAS 9.2 licensing guidance prices it at Premium, or at Limited when the three selected modules include the HSE modules. The modules page lists Change (HSE), Operations (HSE) and Safety and Quality Management (HSE). There is no HSE install quantity on the install table. Self-service at 0 AppPoints covers creating an incident, reviewing incidents, and creating a management-of-change request with view-only access to related artifacts. Oil and Gas has its own self-service lines and its own modules. Do not use an Oil and Gas entitlement as the HSE entitlement.
Keep four facts separate for Health, Safety and Environment. Entitlement is the proof of entitlement and the License Information for IBM Maximo Application Suite. The MAS 9.2 licensing guidance supplements that agreement. Available AppPoints are the pool shown on the AppPoints Usage dashboard: Suite administration, then Suite, then Administration, then AppPoints Usage. Assigned access is the security group together with the user type on the person: Limited, Base or Premium, and Authorized or Concurrent. Consumption is what that assignment draws. Authorized users and administrators reserve AppPoints continuously. Concurrent users draw AppPoints while they are signed in. Install AppPoints stay reserved for the life of that environment. A non-production install of a component draws no install AppPoints when the same component is already installed in production. Administrators and User Management users open the dashboard. Other people need the LICENSEUSAGE security group. Compliance enforcement and idle timeout sit on the dashboard Configuration tab and are suite-administrator settings.
The same guidance publishes these user conversion ratios: Limited is 5 AppPoints for one concurrent user and 2 for one authorized user; Base is 10 concurrent and 3 authorized; Premium is 15 concurrent and 5 authorized; an administrative Base user is 10 AppPoints and an administrative Premium user is 15, both as authorized users. A Base administrator who already reserves 10 AppPoints can be given Premium application access with no further AppPoints. Those ratios were read from the MAS 9.2 licensing guidance on 18 October 2026. Your agreement sets how many AppPoints you purchased. An application that opens shows that the component is deployed. Read the proof of entitlement and the dashboard as well.
Installed and enabled applications
Confirm the HSE applications open and the component version is the one you intend to configure. Oil and Gas can be installed on the same Manage workspace. Opening an Oil and Gas change application does not configure HSE.
Foundation configuration
You need the organization, the site and the location where the event happened. People for the reporter, the reviewer and the action owner. A classification for the incident type. The risk matrix is HSE configuration, not a foundation asset hierarchy. Permits and oil-and-gas operating procedures belong to the Oil and Gas course unless this site uses them as HSE records.
Product configuration
Set the classification and the risk matrix with the process owner. Grant the reporter the self-service incident applications if they only report. Grant the reviewer and the action owner the HSE modules their work needs, inside the Limited three-module rule or on Premium. Review the default matrix before the first real incident so the scores match the scale the site uses.
Infrastructure and integration
HSE runs in Manage. A separate incident hotline, document system or regulatory portal is an external system with its own access. No GIS or optimization service is required to record an incident.
Data and operational readiness
The first journey needs one location, one fictional incident, and the three people. The reporter creates it, the reviewer scores it, the action owner receives an action. A missing location is data. A reporter who can edit the investigation is security. A missing HSE application is the add-on or the group.
Setup order for an incident
- 1. HSE entitlement, separate from Oil and Gas Premium or Limited. Self-service covers reporting, not investigation.
- 2. Site, location, people and classification The event has a place and a type.
- 3. Risk matrix The reviewer uses the agreed scale.
- 4. Report, review, action Three roles on one training incident.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| HSE add-on entitlement at Premium or Limited | Investigators need the add-on tier. Reporting can be the 0-AppPoint self-service row. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type. | Reviewer and action owner on Premium, or Limited with the HSE modules inside the three. Reporter on the self-service incident applications only. | Read each person’s tier after the groups are applied. | A reporter is given the full HSE modules and counted as self-service, or an investigator is left on Base. | Split the groups. Base excludes the add-on. | Licensing in Maximo Application Suite 9.2 |
| HSE modules, not the Oil and Gas modules | The modules page lists Change, Operations, and Safety and Quality Management separately for HSE and for Oil and Gas. | Mandatory | Suite administration → Catalog, Manage workspace. The HSE application list. | The HSE incident and action applications open. The Oil and Gas change application is a different menu. | Open one HSE application and confirm the title is the HSE product. | The team configures Oil and Gas screens and believes HSE is done. | Use the HSE menus for this course. Configure Oil and Gas in its own course. | Modules and applications in Maximo Application Suite 9.2 |
| A location in a site | The incident needs a place. | Mandatory | Locations, in the site. | Location YARD-1 in the training site. | Create the incident against YARD-1 and read the location back. | The incident saves with no place, so the review has no context. | Create the location first. | Modules and applications in Maximo Application Suite 9.2 |
| A risk matrix the process owner has accepted | The score is only meaningful on the scale you agreed. | Mandatory | The HSE risk configuration for the installed build. | A 5-by-5 matrix with the labels the process owner uses. | Score one training incident and read the same score back as the reviewer. | Everyone types a severity in free text. | Enter the matrix before the first reviewed incident. | Modules and applications in Maximo Application Suite 9.2 |
| Reporter, reviewer and action owner as different people | One person playing every role hides an authorization gap. | Mandatory | People and the three security groups. | REP-1 reports, REV-1 scores, ACT-1 owns the action. | Sign in as each person and perform only their step. | The reporter can close the investigation. | Narrow the reporter to the self-service create and review applications. | User access and entitlements in MAS 9.1 and later |
| An action that lands on the action owner | The journey ends when someone is accountable for the follow-up, not when the form is saved. | Mandatory | The HSE action or investigation application. | One corrective action assigned to ACT-1. | Sign in as ACT-1 and open that action from their list. | The incident is stored and nobody is assigned. | Assign the action before you call the journey finished. | Modules and applications in Maximo Application Suite 9.2 |
A. Ready to configure
- HSE is on the entitlement at Premium or Limited, and Oil and Gas is not being used as a substitute.
- The HSE applications open.
- The site, one location and three people exist.
- The process owner has named the risk scale.
B. Ready for the first end-to-end journey
- REP-1 creates an incident at the location.
- REV-1 scores it on the matrix.
- ACT-1 sees the action.
- REP-1 cannot close the investigation.
C. Ready for production operation
- The matrix, classifications and workflow have owners.
- Self-service accounts are only the reporting and view-only management-of-change use the guidance lists.
- A real incident’s retention and regulatory path is agreed outside the training record.
- HSE and Oil and Gas security groups are reviewed separately when both products are installed.
Sources for this readiness check
Licence statements come from the IBM topic named on the row. Installation of a component is a separate check from entitlement.
- Licensing in Maximo Application Suite 9.2 — MAS 9.2 licensing guidance, verified 2026-10-18
- User access and entitlements in MAS 9.1 and later — MAS 9.1 and later, verified 2026-10-18
- Accessing the AppPoints Usage Dashboard — MAS 9.2, verified 2026-10-18
- Modules and applications in Maximo Application Suite 9.2 — MAS 9.2, verified 2026-10-18
Before you start
MAS learning path. Match the component documentation to your installed release and maintenance build before configuring it.
- HSE installed and a training location.
- An agreed example risk matrix and test roles for reporter, reviewer and action owner.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
HSE extends Manage with processes for risk, incident handling, permits and management of change. The starting point is a shared vocabulary for the event, the hazard and the action that addresses it.
A risk assessment records the evaluation. An action records work to do. Completing an action and accepting the remaining risk are separate decisions.
Topics in this series
- Risk and incident vocabulary
- Risk matrices and classifications
- Incidents and investigations
- Corrective actions
- Permits and management of change
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- Describe a fictional incident or near miss against a training location; record what occurred rather than an assumed root cause.
- Review the configured classification and risk matrix with the process owner.
- Create the appropriate training incident and assessment records using the installed HSE applications.
- Record one corrective action with an owner and due date; link follow-up work where the configured process requires it.
- Route the example for review and inspect its history and outstanding actions before closing it.
03 · Practical example
Fictional teaching example
At a fictional depot a leaking fitting creates a slippery access route. The example separates immediate containment, a maintenance repair, investigation and the reviewer's decision on residual risk.
04 · Practice and verify
Trace one training event through assessment, action assignment, work completion and review. Keep a record of each owner and state change.
Expected result
The repair has completion evidence and the review has its own decision. An unfinished corrective action remains visible.
Common mistakes
- Treating a calculated risk score as an authorization to work.
- Closing the incident because the work order was completed.
05 · Advanced concepts
Extend the scenario to management of change, permit dependencies and overdue actions. Map what the software enforces and what the organization's approved process requires.
IBM references
Product explanations link to IBM sources. Scenarios and exercises are original Assetize teaching material. Reviewed 2026-10-01.
Maximo ecosystem overview · Manage learning paths · Practice data in Workbench