IBM Maximo administrators balance technical system management with direct support for operations teams. Whether you’re managing Maximo 7.6 on-premise or Maximo Application Suite (MAS) in the cloud, small configuration improvements consistently yield large operational gains.
These 20 tips cover the practical day-to-day and strategic longer-term actions that distinguish a well-administered Maximo environment from one that merely functions. Each tip is actionable — no vague advice, only specific guidance for Maximo 7.6 and MAS administrators.
1. Master Cron Task Scheduling for System Automation
Cron tasks drive Maximo’s automated processes: PMWOGEN (PM work order generation), ESCALATION, INTEGRATION, and others. Review the Cron Task Setup application regularly to disable unused tasks, tune frequencies, and prevent scheduled tasks from overlapping during peak hours.
For PM generation: if your PM cycles are monthly or quarterly, running PMWOGEN weekly rather than daily reduces unnecessary processing. Monitor execution times in the CRONTASKLOG table — any task consistently exceeding 10 minutes deserves investigation for query optimization.
2. Build a Role-Based Security Group Architecture
The Maximo Security Configuration guide covers this in detail, but the core principle bears repeating: design security groups around roles, not individuals. Create tiers — Technician, Planner, Supervisor, Inventory, Procurement, Administrator — and assign users to role groups rather than configuring access user by user.
Use data restrictions to enforce site-level or organization-level access boundaries. Audit group memberships quarterly using the Security Groups application or the GROUPUSER table. Remove inactive users immediately upon separation from the organization.
3. Customize Start Center Layouts by Role
Start Centers are the first screen most users see. A well-designed Start Center surfaces the right information immediately — overdue work orders for technicians, pending approvals for supervisors, and reorder alerts for inventory personnel.
Configure role-specific templates using the Start Center Templates functionality. Include portlets for: work queues (filtered by role), KPI charts (PM compliance, open emergency WOs), and recent records. Survey your user groups annually and update layouts based on feedback. A Start Center that saves users 5 minutes per day yields 20+ hours saved per year per person.
4. Clean Up Signature Options to Reduce UI Clutter
Signature options (action buttons and menu items in Maximo applications) accumulate over time, especially after upgrades and workflow changes. Unused signature options create confusion and slow down application loads.
Audit signature options in the Security Groups application and in the Application Designer. Disable signature options tied to deprecated workflows, retired applications, or actions no longer used in your business processes. Document each removal in your change log to maintain upgrade traceability.
5. Tune MAXVARS for Your Environment
The MAXVARS system properties table stores configuration values that control Maximo behavior: session timeouts, maximum record fetch counts, login attempt limits. Review critical values after upgrades and when performance issues arise.
Key variables to check: MAXSESSTIME (session timeout), UIROWLIMIT (records displayed in results sets), MXJMSQUEUEDN (JMS queue configuration). Test changes in your staging environment first — incorrect MAXVARS values can cause authentication failures or application instability.
6. Govern Automation Scripts with a Central Registry
Automation scripts (Jython or JavaScript) extend Maximo without code changes. They’re powerful and easy to create — which means they proliferate quickly without governance. Without a registry, you end up with hundreds of undocumented scripts, some overlapping, some broken, some orphaned.
Maintain a script catalog documenting: script name, purpose, trigger event, author, last modified date, and dependencies. Follow a naming convention (e.g., WO_VALIDATE_PRIORITY for a work order validation script). Test all scripts in a sandbox before promoting to production. Delete unused scripts promptly.
7. Manage System Properties Through Controlled Change
System Properties govern Maximo behavior across all applications — email server settings, integration thread pools, UI configuration. Changes to properties should go through the same change management process as code changes: documented request, test environment validation, scheduled production change window.
Export your current System Properties configuration using the export function and store it in version control. Set up a comparison baseline before each upgrade so you can identify properties that changed during the upgrade process.
8. Optimize BIRT Reports for Performance
BIRT reports are Maximo’s primary ad hoc reporting engine. Poorly written BIRT queries are one of the most common causes of Maximo performance problems. The Maximo Reporting Guide covers report design in depth, but key optimization rules are: always filter by indexed columns (SITEID, ORGID, STATUS, ASSETNUM), avoid SELECT * in data sets, and limit date ranges.
Schedule large reports — asset inventory, work order history — to run during off-peak hours using the Report Scheduler. For interactive reports that users run ad hoc, enforce parameter-based filtering so no query can return the entire WORKORDER table.
9. Use Application Designer for Configuration, Not Code
Application Designer lets you customize Maximo screens, add tabs, hide fields, reorder sections, and create conditional UI behavior — without writing Java code. This capability is powerful but often underused.
Common high-value Application Designer customizations:
- Hide unused fields on Work Order Tracking to simplify technician screens
- Add a custom tab on Asset to show related open work orders
- Make classification required before certain work order status transitions
- Configure section visibility based on work type or asset class
Always copy the base application before modifying it. Create customization documentation so upgrade teams know which screens have been modified.
10. Standardize Communication Templates
Maximo’s Communication Templates drive automated emails for work order assignments, approvals, escalations, and PO status changes. Inconsistent or poorly formatted emails reduce user trust in the system.
Create templates for every automated notification type. Include dynamic placeholders (${workorder.wonum}, ${asset.description}) to personalize emails without manual intervention. Test templates across email clients (Outlook, mobile). Assign ownership to each template — someone is accountable for keeping it current and accurate.
11. Maintain Classification Data Integrity
Classifications drive asset reporting, PM targeting, and failure analysis. Over time, classifications accumulate duplicates, obsolete values, and inconsistent hierarchies. A quarterly classification audit prevents data quality degradation.
Use Synonym Domains to handle terminology variations across sites or regions (e.g., “HVAC” vs “Heating & Ventilation”). Align Maximo classification structures with your ERP or enterprise asset registry where possible. Before adding new classification values, check for existing equivalents — classification sprawl is a major reporting problem in long-running Maximo deployments.
12. Rationalize the Job Plan Library
Job Plans are the backbone of planned maintenance. Like automation scripts, they accumulate over time — outdated plans, duplicates, and plans that no longer match actual equipment. A bloated job plan library makes it harder for planners to find the right template.
Conduct an annual job plan review: identify plans not used in the past 12 months, consolidate duplicates, and archive plans for decommissioned asset classes. Use the Job Plan History report to identify usage frequency. A clean job plan library with 50 well-maintained plans is more valuable than 500 plans of unknown quality.
13. Configure Escalations with Precision and Monitoring
Escalations automate responses to time-based conditions — work orders sitting in WAPPR for more than 48 hours, emergency work orders not assigned within 1 hour, purchase requisitions not approved within the SLA window.
The Maximo Workflow Configuration guide explains how escalations interact with approval workflows. When configuring escalations: define clear trigger criteria, use cascading actions (email first, then supervisor notification, then department head), and set up a suppression rule to prevent repeat notifications for the same condition.
Monitor escalation logs monthly. Escalations that fire frequently on the same records may indicate a process problem (e.g., planners not processing approvals) rather than a configuration issue.
14. Implement Integration Error Monitoring
Integration failures are silent — a failed outbound message to SAP may not cause any visible error in Maximo, but purchase orders never flow to procurement. Integration errors that go undetected for days create expensive reconciliation work.
Set up proactive integration error monitoring:
- Configure Integration Framework email alerts for queue depth exceeding thresholds
- Review the JMS queue depth report daily
- Check the integration error log in the External Systems application at least twice per week
- Maintain a runbook for the 5 most common integration error types with resolution steps
15. Audit Lookup Tables and Domain Values Regularly
Maximo dropdowns and validation lists are populated from Domains and Synonym Domains. Over time, these accumulate test values, legacy entries, and regional variations that clutter user interfaces and introduce inconsistency.
Quarterly, review the key domain tables used in work order creation: WORKTYPE, WOPRIORITY, FAILURECODE, COMMODITYGROUP, CLASSSTRUCTURE. Remove values that are no longer in use. Standardize terminology across sites where global reporting is expected.
16. Build and Maintain an Upgrade Preparation Checklist
Maximo upgrades are complex projects that benefit enormously from a pre-built checklist. Organizations that upgrade without a checklist consistently miss something — a customization that breaks, an integration that fails silently, a report that no longer runs.
Your upgrade checklist should include:
- Database backup and restore verification
- Customization inventory (Application Designer mods, automation scripts, workflow changes)
- Integration test plan (test all publish channels and enterprise services with representative data)
- Report validation list (run and verify top 20 most-used reports)
- User acceptance test scripts for core business processes
- Rollback procedure and decision criteria
Keep the checklist in your change management system and update it after every upgrade based on lessons learned.
17. Use MX Analyzer for Performance Investigation
MX Analyzer (available in Maximo 7.6) provides real-time performance diagnostics: slow SQL queries, application response times, JVM heap usage, and user session counts. It’s the first tool to reach for when users report slowdowns.
Set up performance baselines by running MX Analyzer during normal business hours and capturing typical response times. Any application or query consistently exceeding 3 seconds deserves investigation. Share findings with your DBA for query tuning and index optimization.
Enterprise technology trends tracked by publications like i-actu.fr indicate that performance expectations for EAM systems are rising as organizations compare them to modern cloud software — your Maximo performance baseline should be reviewed annually against user experience standards.
18. Rationalize Domains and Synonym Domains
Domains define valid values for Maximo fields — the dropdown options users see when selecting work type, asset condition, or vendor classification. Synonym domains support multiple descriptions for the same internal value (e.g., “COMPLETE” displayed as “Done,” “Finished,” or “Completed” in different site languages).
Poorly governed domains create inconsistent data that breaks reporting. A value entered in 12 different ways across 12 sites cannot be aggregated into a meaningful enterprise report. Enforce domain usage through application validation rules and assign a data steward for each business-critical domain.
19. Implement Verified Backup and Recovery Procedures
Backup Maximo databases daily (full) with transaction logs backed up hourly. But backup verification is where many organizations fail — they assume backups are working until a recovery event proves they aren’t. Recovery procedures should also cover your Maximo Inventory and Storeroom data — storeroom balances and item master records that are critical for maintenance continuity.
Test your Maximo database recovery quarterly by restoring a backup to an isolated test environment and validating that the system starts, users can log in, and data from the backup date is accessible. Include Maximo application server configurations, automation scripts, and attached documents in your backup scope. Document recovery time objectives (RTO) and verify you can meet them.
20. Drive User Adoption with Measurement and Recognition
User adoption determines whether your Maximo investment delivers its intended value. High adoption means accurate data — work orders created promptly, actuals entered consistently, failure codes applied correctly. Low adoption means expensive software used as a paper log.
Measure adoption using Maximo’s built-in metrics:
- Login frequency per user per week
- Work orders created vs. completed ratio per technician
- Actuals entry rate (% of closed WOs with labor hours)
- Failure code completion rate on corrective work orders
Recognize and reward high performers. Build peer networks — identify power users who can support their colleagues. Address adoption barriers immediately rather than attributing them to “change resistance.” If users aren’t entering data, find out why — it’s usually a workflow friction problem, not a training problem.
Consistent Maximo administration isn’t glamorous, but it’s the difference between a CMMS that delivers ROI and one that becomes an expensive data entry burden. These 20 practices, applied systematically, compound over time into measurable improvements in data quality, system performance, and operational results.