All learning series · Industry solution · Part 1
Maximo Oil & Gas
Connect operating risk, controlled change and maintenance 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 Maximo Oil & Gas? 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 Maximo Oil and Gas?
Oil and Gas manages change, operations, and safety and quality on oil and gas assets. HSE has a similar shape and its own modules. Use the Oil and Gas modules for this course.
Before configuration
Oil and Gas is Premium or Limited, with no install quantity on the 9.2 table. Create Incident, Review Incidents and a view-only management-of-change request are self-service at 0 AppPoints.
Before the first successful journey
A location or asset, a change that is not like-for-like maintenance, and the reviewers the classification requires.
Before production use
Change classifications and the approval path have owners. An HSE incident record is not an Oil and Gas change.
Licensing, entitlement and AppPoints
Oil and Gas is a Maximo Manage industry solution priced at Premium, or at Limited when the three modules include the Oil and Gas modules. The modules page lists Change (Oil), Operations (Oil) and Safety and Quality Management (Oil). The install table does not list an Oil and Gas install quantity. 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. HSE has its own copy of those self-service lines and its own modules. Grant the product you are configuring.
Keep four facts separate for Maximo Oil and Gas. 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 Oil and Gas applications open and note the version. HSE can be installed beside it. Opening an HSE application does not configure Oil and Gas. Installed means the Oil and Gas menu is present. Configured means a change classification and its reviewers exist. Usable means a change record follows that path.
Foundation configuration
You need the site, the asset or location, and the people who request and review. Operating procedures, permits and bypasses are Oil and Gas operations records when the journey needs them. The first change needs the classification more than it needs the full operations suite. Shared technical tables with HSE do not merge the two products’ security or entitlement.
Product configuration
Create the change classification and the required reviewers. Separate like-for-like maintenance from a change. Grant requesters the self-service path if they only raise the request. Grant reviewers the Change (Oil) module. Review the default classification so a training change is not approved by the production board.
Infrastructure and integration
Oil and Gas runs in Manage. A process-safety system or a document store is an external system with its own licence and route. No map is required for the first change.
Data and operational readiness
The first journey needs one asset, one change request, and a reviewer who must act before the change is approved. A missing reviewer is configuration. A missing asset is data. An HSE screen is the wrong product. A requester who approves the change is security.
Setup order for a change
- 1. Oil and Gas entitlement Premium or Limited. Separate from HSE.
- 2. Asset, classification, reviewers The change path.
- 3. A change that is not like-for-like work The distinction the journey is teaching.
- 4. Review before approval The requester does not approve their own change.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| Oil and Gas entitlement at Premium or Limited | Industry users are Premium or Limited. Self-service covers the incident and view-only change actions the guidance lists. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type. | A reviewer on Premium or qualifying Limited. A requester on the self-service incident and change-request actions only. | Read both tiers on the dashboard. | HSE entitlement is used as the Oil and Gas licence. | Grant the Oil and Gas modules on their own. | Licensing in Maximo Application Suite 9.2 |
| Oil and Gas modules | Change (Oil), Operations (Oil) and Safety and Quality Management (Oil) are the modules page entries. | Mandatory | Suite administration → Catalog, Manage workspace | The Oil and Gas change application opens. | Confirm the application title and the product version. | The HSE change screen is used for this journey. | Switch to the Oil and Gas application before you configure the classification. | Modules and applications in Maximo Application Suite 9.2 |
| An asset or location and a change classification | The change needs a target and a type that selects the reviewers. | Mandatory | Assets or locations, and the change classification. | Asset PUMP-OG, classification instrument range change. | The classification lists the reviewers it requires. | Any description is accepted with no reviewer. | Set the classification and the reviewer list. | Modules and applications in Maximo Application Suite 9.2 |
| A requester and a reviewer as different people | The requester’s self-service path is view-only on related artifacts. | Mandatory | Manage → Security → Security Groups, and the suite user type | REQ-OG creates the request. REV-OG reviews it. | Each person performs only their step. | The requester approves the change. | Remove approval from the requester group. | User access and entitlements in MAS 9.1 and later |
| A change that is distinct from like-for-like maintenance | The journey is a change record, not an ordinary work order. | Mandatory | The Oil and Gas change application, linked to the asset. | One training change describing a setpoint move, not a filter replacement. | The record type is the change object, and the work order, if any, is linked from it. | The team stores the change as a work-order description. | Create the change record and link work from it. | Modules and applications in Maximo Application Suite 9.2 |
| Approval only after the required review | The classification’s reviewers are the gate. | Mandatory | The change workflow or status for the installed build. | The change stays unapproved until REV-OG acts. | Attempt approval as REQ-OG and as REV-OG. | The status moves to approved with no review. | Put the reviewer on the path before production use. | Modules and applications in Maximo Application Suite 9.2 |
A. Ready to configure
- Oil and Gas is entitled separately from HSE, at Premium or Limited.
- The Oil and Gas change application opens.
- An asset and two people exist.
- The classification and its reviewers are named.
B. Ready for the first end-to-end journey
- The change record saves against the asset.
- The requester cannot approve it.
- The reviewer can complete their step.
- The record stays a change, with any maintenance work linked underneath.
C. Ready for production operation
- Classifications and reviewer lists have a process owner.
- Self-service users match the incident and view-only change actions in the guidance.
- HSE groups are reviewed on their own when both products are installed.
- External process-safety systems have an owner and a tested path.
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.
- Oil & Gas installed and a fictional asset/process context.
- A training change classification and agreed review roles.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
Oil & Gas supports safety, reliability and operational processes, including management of change and action tracking. A change proposal has different review needs from routine corrective maintenance.
A change can affect documents, training, equipment and procedures. The work order is one part of implementing that change.
Topics in this series
- Operating context
- Change classification
- Assessment and review
- Implementation actions
- Closeout and audit history
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- Describe a proposed change and distinguish it from like-for-like maintenance.
- Create the appropriate training management-of-change record using the installed application process.
- Record the affected assets, operating assumptions, assessments and reviewers.
- Assign implementation actions including document and training updates where applicable.
- Review the evidence for each action before following the configured closeout process.
03 · Practical example
Fictional teaching example
A fictional plant proposes changing a pump's operating duty. Mechanical work is only one action; operating limits, maintenance tasks and instructions may also need review.
04 · Practice and verify
Build a change-impact matrix and trace three different actions through ownership, implementation and verification.
Expected result
Closure accounts for every required action, not just the physical installation.
Common mistakes
- Using an equipment description change as the entire change record.
- Leaving document or training actions outside the closeout review.
05 · Advanced concepts
Extend the scenario to permits, simultaneous work and temporary changes. Identify which controls are configured and which remain procedural responsibilities.
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