Asset Management Administration Training Course

Duration 5 days 10 modules · 33 contact hours
Level Intermediate Certificate on completion
Who attends Maximo Administrators, Maintenance Systems Analysts and others
Fee from USD 1,100 KSh 95,000 for Kenyan organisations
Where 52 cities + online See dates by city
Next start 16 Nov 2026 Course code SD-ME-111

Before you join: Participants should understand core maintenance concepts such as work orders, preventive maintenance, assets, locations, labour and spare parts.

Dates & prices

Two start dates a month in every city, and live online on weekdays or weekends. Fees are per participant; classroom fees include tuition, materials, lunch and refreshments, and the certificate.

Suggest a date or city

Showing the next six months. Later dates, other cities and private deliveries for your team are available on request.

Course overview

Asset management systems fail to deliver value when master data, security, workflows, preventive maintenance rules and inventory transactions are poorly administered. Maintenance teams then face duplicate records, inaccurate work histories, unplanned stock shortages, weak approval controls and reports that cannot be trusted. Administrators need to translate maintenance policy into controlled IBM Maximo configurations while protecting data quality, system performance and auditability.

This course develops the administrative skills required to configure and support IBM Maximo Manage for maintenance and engineering operations. Participants work through the application architecture, organisations and sites, security groups, domains, classifications, assets, locations, work management, job plans, preventive maintenance, inventory, purchasing, integrations and reporting. They learn how configuration choices affect planners, supervisors, technicians, storeroom teams, procurement staff and operational managers. The course also addresses configuration governance, migration between environments, incident triage and routine system health checks.

Instruction combines concise technical briefings with guided configuration scenarios, maintenance cases, group analysis and system administration simulations. Cases reflect asset-intensive settings such as utilities, transport fleets, manufacturing plants, public infrastructure and facilities portfolios. Participants produce a practical Maximo administration pack containing security, data, workflow, reporting and change-control artefacts that can be adapted for their own system. The five-day programme runs from 08:30 to 16:30 each day, providing approximately 6.5 contact hours daily. Participants receive a certificate of completion.

The course suits professionals responsible for maintaining Maximo configuration and data, as well as maintenance leaders who need to govern how the system supports operational control.

What you will be able to do

  • Configure Maximo organisations, sites, sets, domains and classifications for controlled master data.
  • Administer security groups, conditional expressions and signature options using least-privilege principles.
  • Design work order lifecycles, job plans and workflows aligned with maintenance control points.
  • Set up preventive maintenance records, meter rules and forecast settings for planned maintenance.
  • Manage inventory, purchasing and rotating-item controls linked to maintenance work orders.
  • Configure Maximo Integration Framework components for controlled inbound and outbound data exchanges.
  • Produce KPI, BIRT and query-based reporting specifications for maintenance performance monitoring.
  • Apply configuration governance, migration controls and administration health-check routines.

Benefits of attending

For you

  • Builds confidence administering Maximo configuration without relying on undocumented local practices
  • Improves ability to diagnose whether incidents arise from data, configuration or system faults
  • Provides a structured method for protecting master-data quality and maintenance history
  • Strengthens credibility when translating maintenance requirements into controlled system changes
  • Creates reusable administration artefacts for future releases, audits and support requests

For your organisation

  • Improves consistency of asset, location, failure-code and spare-parts master data
  • Reduces unauthorised record changes through role-based access and signature controls
  • Raises preventive maintenance reliability through better PM, meter and forecast configuration
  • Improves maintenance reporting accuracy through controlled statuses, actuals and KPI definitions
  • Reduces change-related disruption through documented testing, migration and release controls

Course modules

10 modules over 5 days

Participants can explain Maximo configuration scope, record relationships and core administrative responsibilities.

  • Maximo application architecture: databases, application server, cron tasks and integrations
  • Record ownership through organization, site, set and system-level configuration scopes
  • Core records linked across assets, locations, work orders and inventory
  • Status-driven processes and signature options controlling authorised record changes
  • Start Center portlets configured for administrator monitoring and exception queues
  • Administrative roles distinguished from planner, supervisor, storeroom and requester responsibilities

Participants can configure role-based access controls and test user permissions against operational responsibilities.

  • Security groups built with application access, data restrictions and authorisations
  • Conditional expressions restrict fields, tabs, actions and application visibility
  • Person records, user records and labour records maintained without duplication
  • Authentication options compared: native security, LDAP directories and single sign-on
  • Signature options mapped to controlled status changes and sensitive actions
  • Security testing uses representative personas and least-privilege access matrices

Participants can establish governed asset master data structures that support maintenance execution and analysis.

  • Asset, location and classification hierarchies designed for maintainable reporting structures
  • Classifications, attributes and specifications standardise technical asset data capture
  • Domains control valid values, crossovers and conditional field behaviour
  • Failure classes, problem codes and cause-remedy codes support reliability analysis
  • Meter definitions, units and readings establish condition-monitoring data quality
  • Asset moves, swaps and rotations retain ownership and maintenance history

Participants can configure controlled work management processes from request intake to work order closure.

  • Work order lifecycle configured from request through approval, completion and closure
  • Job plans combine tasks, labour, materials, tools and safety information
  • Plans, routes and work packages support repeatable field execution
  • Workflow assignments, escalations and approvals control maintenance decision points
  • Service requests and work orders separated through triage and conversion rules
  • Status synonyms aligned with local governance without breaking reporting logic

Participants can configure preventive maintenance strategies and generation rules for planned maintenance work.

  • Time-based, meter-based and condition-based PM strategies selected by failure mode
  • PM records generate forecast dates, work orders and seasonal maintenance schedules
  • Frequency, lead time and active days tuned against resource capacity
  • Meter-based forecasting handles average calculations, rollover values and thresholds
  • Condition monitoring records initiate corrective work from inspection results
  • PM hierarchy and associated locations coordinate multi-asset maintenance campaigns

Participants can maintain planning and labour data that supports credible maintenance schedules and performance measures.

  • Work order plans estimate labour, craft, duration, materials and tools
  • Craft, skill, crew and calendar records establish available maintenance capacity
  • Graphical scheduling concepts balance backlog, priorities, constraints and weekly commitments
  • Assignment Manager rules match qualified labour to planned work requirements
  • Criticality and priority matrices sequence corrective work against operational risk
  • Actuals capture feeds wrench-time, backlog and schedule-compliance performance measures

Participants can administer maintenance inventory and purchasing controls linked to work execution.

  • Item masters, rotating assets and condition codes govern spare-parts control
  • Storerooms, bins, reorder points and safety stock support availability
  • Inventory issues, returns, transfers and physical counts preserve transaction accuracy
  • Purchase requisitions, purchase orders and receipts connect maintenance demand to supply
  • Direct issue materials and planned items link costs to work orders
  • Vendor records, contracts and item specifications support controlled purchasing decisions

Participants can administer core Maximo integration components and diagnose common interface failures.

  • Maximo Integration Framework components: object structures, publish channels and enterprise services
  • Integration controls manage external ERP, GIS, condition-monitoring and identity data
  • Object structures define fields, relationships, processing rules and data ownership
  • Enterprise services and publish channels route inbound and outbound transactions
  • Error queues, message tracking and reprocessing resolve failed interface records
  • Data migration mapping protects identifiers, relationships, history and auditability

Participants can define operational reporting controls and identify data-quality issues affecting maintenance decisions.

  • KPI Manager targets track backlog, PM compliance, stockouts and work execution
  • BIRT report designs present grouped operational data, parameters and drilldowns
  • Query-based reporting uses where clauses, saved queries and security filters
  • Key performance measures distinguish leading indicators from lagging maintenance results
  • Data-quality checks identify incomplete actuals, invalid statuses and duplicate masters
  • Audit trails and electronic signatures support controlled administrative changes

Participants can govern Maximo changes, support production operations and prioritise administration improvements.

  • Configuration management records changes, approvals, test evidence and deployment decisions
  • Migration packages promote configurations through development, test and production environments
  • Administrative health checks review cron tasks, queues, logs and integrations
  • Incident triage separates configuration defects, data errors and system faults
  • Release plans coordinate stakeholder communications, training and post-deployment support
  • Thirty-day administration action plan prioritises controls, data fixes and ownership

Exercises and examples are adapted to each cohort's sectors and roles.

What you take back to work

  1. Maximo security-role matrix
  2. Asset master-data governance checklist
  3. Work management workflow specification
  4. Preventive maintenance configuration template
  5. Integration error-triage checklist
  6. Configuration change-control plan

Who should attend

  • Maximo Administrators — responsible for configuration, user access, data controls and support
  • Maintenance Systems Analysts — translate maintenance requirements into Maximo records and workflows
  • EAM Product Owners — govern system priorities, change requests and operational adoption
  • Maintenance Planners — need reliable job plans, PM generation and scheduling data
  • Asset Information Managers — maintain asset hierarchies, classifications and technical records
  • IT Application Support Specialists — support Maximo security, integrations, releases and incidents

Skills and tools covered

Maximo administrationMaintenance master dataSecurity configurationWork management designIntegration managementConfiguration governance

Tools and standards

IBM Maximo Manage, IBM Maximo Application Suite, ISO 55000, ITIL 4

How the course runs

Training methodology

The course uses short instructor briefings to establish Maximo concepts and configuration dependencies. Participants analyse maintenance administration cases, configure representative records, review security and workflow decisions, and diagnose data and integration faults. Group exercises compare alternative settings for work management, PM, inventory and reporting. Simulations use realistic administrator tasks such as tracing a failed interface, reviewing access restrictions and preparing a migration package. Each participant develops an application plan for priority controls and improvements in their own Maximo environment.

Requirements and prerequisites

Participants should understand core maintenance concepts such as work orders, preventive maintenance, assets, locations, labour and spare parts. Experience using IBM Maximo as a planner, supervisor, technician, analyst or support specialist is expected, preferably including basic record searches and status changes. Familiarity with the participant's maintenance processes and asset data is useful. Prior Maximo administration experience is not required. Programming, database administration, Java, SQL development and prior integration development knowledge are not required, although technically experienced participants will benefit from the configuration detail.

A typical training day

08:30 – 10:30First session
10:30 – 10:45Refreshment break
10:45 – 12:30Second session
12:30 – 13:30Lunch and networking
13:30 – 15:00Third session
15:00 – 15:15Refreshment break
15:15 – 16:30Workshop and daily review

Live online deliveries follow the same structure in East Africa Time, with shorter screen blocks and longer breaks.

What the fee includes

  • Instruction by a practitioner facilitator
  • Full course workbook and materials
  • Exercise files, templates and case studies
  • Refreshments and lunch on classroom deliveries
  • Certificate of completion
  • Post-course application plan

Frequently asked questions

Participants should already understand maintenance work orders, assets, preventive maintenance and spare parts. Basic experience using Maximo is expected, but prior system administration or technical development experience is not required.

Bring a laptop if attending in person, together with examples of local Maximo issues, reports, workflows or data problems where permitted by employer policy. Do not bring confidential production data or passwords.

The course is designed primarily for Maximo administrators, maintenance systems analysts, EAM product owners and application support specialists. Maintenance planners and asset information managers also benefit where they maintain configuration or master data.

User training concentrates on completing daily transactions such as raising work orders or issuing stock. This course focuses on the configuration, governance, security, data structures and support controls behind those transactions.

Participants can use the templates and checklists to review access controls, master data, PM rules, workflows and change processes. The final application plan helps identify immediate improvements for their own Maximo environment.

Each day runs from 08:30 to 16:30 and provides about 6.5 contact hours. Time is divided across technical briefings, configuration scenarios, case analysis, group work, simulations and individual application planning.

Questions about this course?

Ask about dates, fees, group bookings or running it for your team. Our training team replies by email.