Hi Rajiba,
Can I make a recommendation?
The Maximo Secrets version 7.6.x.x series in the links below is a foundation for understanding your unique business case. For the HSE (Health, Safety, and Environment) Industry Add-on's deployment on MAS Manage 9.1, you should anticipate a notable shift in database overhead. Using Maximo Secrets' archived series, the response below is structured to provide context based on the archive's documentation. I've included an attachment with the underlying ERD.
Assumptions Based on Archived Maximo Secrets HSE Series (Maximo v.7.6.x.x)
HSE is not an isolated layer; it tightly interweaves into your baseline schema, adding 31 entirely new applications and modifying 20 core application clones (such as a heavily extended LOCATION and ASSET infrastructure).
Below is an architectural assessment template that you can use to drive your unique use cases' performance impacts and root cause analysis. The framework is designed to help you address root causes and mandatory database tuning blueprints based on the product's core entity relationship diagram (ERD). Your unique business case will drive your decisions.
1. Observed Performance Impacts & Schema Root Causes
- Transactional Degradation in Core Modules (
WOTRACK, ASSET, JOBPLAN)
- Symptom: Increased page load times and timeouts when querying, saving, or shifting statuses on work orders.
- Logical Root Cause: Activating HSE introduces a massive, multi-table transactional matrix directly inside the Work Order Tracking user interface. When a safety plan is applied, a core transactional record triggers automated cascading writes and deep joins across an 8-table data subsystem (
WOSAFETYLINK, WOHAZARD, WOPRECAUTION, WOHAZARDPREC, WOTAGOUT, WOLOCKOUT, WOTAGLOCK, and WOSAFETYPLAN). Manage must continually execute outer joins against WOSAFETYLINK to cross-reference hazards or lockout tasks against primary work locations and assets.
- Massive Index Fragmentation during
UpdateDB
- Symptom: Severe database CPU and I/O utilization spikes, leading to log-full errors or execution hangs during the automated deployment phase.
- Logical Root Cause: Because HSE introduces dozens of new objects, the underlying structural table modifications alter the physical layout of your core database tables. This rapid schema expansion results in massive index fragmentation across core transactional disk space.
- Lookup Latency via Cloned Applications
- Symptom: High latency when utilizing selection dialogs (e.g., Select Safety Hazards or Select Value radio paths).
- Logical Root Cause: Cloned HSE modules rely on extensive cross-table scanning. For example, standard lookups drive evaluation logic checking through structural fields across custom organizational lines (
ORGID fields inside the HAZARDS table are defined at the Organization level, whereas almost all other associated mapping tables like HAZARDPREC or SAFETYLEXICON are isolated strictly at the SITEID level).
2. Database Tuning Blueprint
To mitigate these systemic issues and preserve your operational baseline, your DBA team must execute targeted optimizations mapped directly to the HSE relational design:
| Target Component / Table |
Required Optimization Action |
Technical Justification |
| Global Post-Install |
Execute a full table REORG followed immediately by a targeted RUNSTATS across all newly created and extended tables. |
Cleans up index page fragmentation left over by UpdateDB and updates the DB2 optimizer paths. |
WOSAFETYLINK Table |
Create custom composite, non-unique indexes on: (WONUM, SITEID, HAZARDID) and (WONUM, SITEID, TAGOUTID). |
Bypasses slow table scans when the UI queries work order safety records, optimizing user fetch loops. |
WOHAZARD Table |
Create an explicit index on foreign lookup keys: (HAZARDID, ORGID). |
Directly matches organizational security cross-references without sorting the dataset in volatile memory. |
WOTAGOUT & WOLOCKOUT |
Index composite pairing keys: WOTAGOUT(TAGOUTID, WONUM) and WOLOCKOUT(LOCKOUTID, WONUM). |
Speeds up isolation procedural lookups when managing sequential isolation safety steps. |
| System Identity Sequences |
Increase sequence object caching allocations (such as maxsequence) to a minimum value of 50. |
Prevents high block-locking contention when multiple shifts log parallel operator logs or incidents concurrently. |
| DB2 Instance Level |
Verify and lock down row-organized tables globally: db2 update db cfg using DFT_TABLE_ORG ROW. |
MAS Manage entirely relies on row organization; accidental column inheritance will break query outputs. |
3. Architecture Recommendations
- Isolate Safety Cron Processes: Separate your background processing workloads. Allocate dedicated server pods inside your OpenShift environment strictly to isolate safety escalations, regulatory compliance loops, or background LOTO calculations so they never drain memory away from user interactive pods.
- Automate Regular Index Rebuilds: Ensure regular maintenance windows are scheduled to target high-frequency mapping tables like
WOSAFETYLINK and WOHAZARDPREC, as transactional volume will spike as your team adopts hazard tracking.
- Deploy Pre-Install Baselines: Prior to launching HSE, leverage the Maximo Cluster Performance Insights (Maximo CPI) utility to record a true infrastructure benchmark. Re-run the tool immediately after deployment to intercept anomalous table scans right away.
Summary Conclusion: HSE introduces measurable transactional database overhead because it weaves complex, deeply structural relationships throughout core Maximo components. However, by proactively deploying targeted indexes on the 8 core work order safety objects and conducting disciplined table reorganizations post-upgrade, your team can deploy HSE securely without losing core transactional speed.
Máximo Secret References:
Table of Contents (Archive)
- Condition for Work (HSE), Prioritization Matrix (HSE)
- Service Requests (HSE)
- Incidents (HSE)
- Defects (HSE)
- Solutions (HSE)
- Standard Actions (HSE), Standard Actions Groups (HSE)
- Risk Assessment (HSE), Risk Matrix (HSE)
- Hazards (HSE), Precautions (HSE), Lock Out / Tag Out Plans (HSE)
- Investigations (HSE)
- Regulatory Compliance (HSE)
- Operating Policies (HSE), Operating Procedures (HSE)
- People (HSE), Qualifications (HSE)
- Benefits and Losses (HSE), Location Profiles (HSE)
- Improvements (HSE)
- Locations (HSE)
- Permit to Work (HSE)
- Permit and Certificate Types (HSE), Certifications (HSE)
- MOC Requests (HSE), MOC (HSE)
- Audit and Survey (HSE)
- Job Plans (HSE)
- Preventive Maintenance (HSE), Routes (HSE)
- Work Order Tracking (HSE)
- Log Book (HSE), Operator Log (HSE)
- Operator Tasks (HSE)
- Operational Actions (HSE), Action Tracking (HSE), Asset List (HSE)
- Assets (HSE)
- Isolation Management (HSE)
- Bypass Management (HSE)
- Item Master (HSE)
- Purchase Requisitions (HSE), Purchase Orders (HSE)
------------------------------
Fredrick Ndwaru
Perpetual Ignition
------------------------------