Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

MAS9.1 MULTIASSETLOC with List and Map view in Maximo Mobile Technician App

By Ravi Shah posted 5 days ago

  

Title: MAS9.1 MULTIASSETLOC with List and Map view in Maximo Mobile Technician App

This blog will walk you through the steps to accurate Understanding MULTIASSETLOCCI in IBM Maximo: A Powerful Way to Manage Multiple Assets and Locations in One Ticket

In the world of enterprise asset management, it’s not uncommon for a single maintenance activity or incident to involve more than one asset or location. Whether it’s a faulty power circuit affecting multiple rooms, or preventive maintenance applied to several identical machines in different areas, managing such cases efficiently is critical.

That’s where MULTIASSETLOCCI in IBM Maximo comes into play.


What is MULTIASSETLOCCI?

MULTIASSETLOCCI is an underlying database table in IBM Maximo that stores multiple asset, location, and configuration item (CI) records for a single Service Request (SR), Work Order (WO)/ Technician and Approval App, or other ticket types.

Maximo typically allows you to associate one asset or location at the header level of a ticket. But in real-world operations, you may need to track and work on multiple assets or locations within the same ticket—without duplicating effort.

The MULTIASSETLOCCI table makes this possible.


How It Works

  1. Primary Record
    • The asset or location linked at the header level of your SR or WO is stored in MULTIASSETLOCCI with ISPRIMARY = 1.
  2. Additional Records
    • Any other asset/location/CI entries you add in the Multi Asset/Location table section of the ticket are also stored here, but with ISPRIMARY = 0.
  3. Single Ticket, Multiple References
    • All these records stay tied to the same ticket, allowing you to manage them collectively.

Why MULTIASSETLOCCI Matters

Without MULTIASSETLOCCI, you’d have to:

  • Create separate work orders or service requests for each affected asset/location.
  • Duplicate instructions, approvals, and status tracking across multiple records.

This would lead to inefficiency, data fragmentation, and higher administrative overhead.

With MULTIASSETLOCCI:

  • You can keep a single source of truth for the work.
  • Reduce time spent on creating and closing multiple tickets.
  • Ensure consistent work instructions across all affected assets/locations.

When to Use MULTIASSETLOCCI

The feature shines in scenarios like:

  • Facility Maintenance: Replacing lighting fixtures in 10 classrooms as part of the same maintenance task.
  • Incident Response: A power outage affecting multiple assets across different buildings.
  • Preventive Maintenance: Applying the same inspection checklist to several pumps in different locations.
  • Safety Inspections: Fire extinguisher checks across multiple office areas.

Best Practices

  • Use for uniform work: MULTIASSETLOCCI is ideal when the same job applies to all listed assets/locations. If the work differs significantly, use child work orders or tasks instead.
  • Be aware of reporting impacts: Since MULTIASSETLOCCI is a separate table, your reports and KPIs need to account for these records.
  • Control via security: Not all users may need access to add multiple assets/locations. Use Maximo’s security groups to manage permissions.

MULTIASSETLOCCI vs. Child Work Orders

Feature

MULTIASSETLOCCI

Child Work Orders

Work Instructions

Same for all assets/locations

Can differ per child WO

Status Updates

Single ticket status

Independent statuses

Use Case

Uniform tasks for multiple assets/locations

Complex workflows with varied tasks

Effort to Manage

Low – fewer records

Higher – more records to create/track


Real-World Example

Imagine a university maintenance team planning an air conditioner filter replacement across 15 classrooms in one building:

  • Instead of raising 15 separate work orders, the planner creates one work order with the main asset/location at the header level.
  • The remaining 14 classrooms are added to the Multi Asset/Location table.
  • The technician sees one set of work instructions and can record results for each location under the same ticket.
The work order is closed once all assets/locations have been serviced—saving time, effort, and paperwork.

Step: 

Maximo Manage -> Work Order Tracking -> Create a Work Order and add multiple Assets and Locations.

Let’s open Maximo Mobile application in web view and navigate to technician Work Order details page and see tab “Multiple assets and locations” with badge counts.

Maximo Mobile View of “Multiple assets and locations” list view. Along with assets locations list contains facility to enter Meters reading for assets and locations, Follow up Work Order with MultiAssetLoc, Service Address, Inspection, redirect to Asset details page and Mark Complete. List view had Search, Filter, Sorting features.
Maximo Mobile View of “Multiple assets and locations” Map view - Assets and Locations is displayed in Map view.

Conclusion

The MULTIASSETLOCCI table is one of those behind-the-scenes features in IBM Maximo that quietly delivers major productivity benefits. It allows organizations to scale their maintenance operations efficiently while keeping data consistent and easy to manage.

When used correctly—especially for uniform tasks—it can simplify work management, reduce duplication, and ensure teams focus on doing the job rather than managing tickets.


#MaximoMobile #Technician #Mobile #WorkExecution

0 comments
17 views

Permalink