MAS Mobile APIs to Create, Retrieve, Update, and Delete Package Applications in MAS 9.1 and Later

MAS Mobile applications interact with Maximo Manage through REST APIs. In MAS 9.1 and later, these APIs can be used to perform Create, Retrieve, Update, and Delete (CRUD) operations on Graphite package applications such as TECHMOBILE, SRMOBILE, INCMOBILE, etc., Access to these operations requires System or Workspace Administrator privileges.

By leveraging these APIs, Mobile Application deployments can be automated as part of a DevOps pipeline.

To use these APIs, a few configuration values must be obtained from the MAS environment.

The Workspace ID, Instance ID and Domain values can be derived from the MAS Application Suite URL :  https://<workspaceId>.home.<mas-instance-id>.<mas.domain>/

For example, if you access your MAS UI via  https://main.home.dev.iam.np.maximo.com/

where 

<workspaceId>	main
<mas-instance-id>	dev.iam.np
<mas.domain>	maximo.com
<manage-url>	<workspaceId>.manage.<mas-instance-id>.<mas.domain>
SuperUser Credentials	Stored in OpenShift Cluster
Authentication Token	Retrieve using Super User Credentials

Super User credentials Super User credentials are available

in the OpenShift cluster under the MAS Core project's Secrets

configuration. The Username and password from this resource

will be used as Basic Auth for getting the authentication token.

Authentication Token:

Almost of all the REST APIs for performing Suite administration operations use token based authentication. The token is provided via the x-access-token header of each request. An exception is the v1/authenticate endpoint which uses HTTP Basic Authentication.

To obtain a JWT (JSON Web Token) for authenticating MAS Admin REST APIs, we must use Super User credentials available from Open Shift console via GET request to endpoint v1/authenticate. It will issue a time limited token in the response which can be used in the x-access-token header when interacting with other APIs.

URL:https://api.{mas-instance-id}.{mas.domain}/v1/authenticate

<GET> https://api.dev.iam.np.maximo.com/v1/authenticate

      

Once all the required values have been collected, the MAS Admin and Maximo Manage APIs can be used to create, update, or delete Mobile Application packages.  

Create a new package ( using duplicate action )
This API creates a custom Mobile application package by duplicating an existing OOB (out of the box) application.

 

URL:https://api.{mas-instance-id}.{mas.domain}/graphite/configtool/packages/?workspaceId=<frommasurl> 

<POST>https://api.dev.iam.np.maximo.com/graphite/configtool/packages?workspaceId=main

In Request Body, choose raw and select JSON format with below sample input for duplicating mobile application.

Sample JSON Request Payload 

  {
  "packageid": "customtechmobile",
  "originalpackageid": "techmobile",
  "version": "9.1.22.0",
  "name": "Custom Technician",
  "appid": "manage",
  "description": "Custom Technician",
  "ismobile": "true"
  }  

Once the API response is successful, the custom application will be created in Application Configuration application. 

The application must be published from the Application Configuration UI before downloading the package. Publishing generates the build artifacts required for deployment.

Retrieve package list 

This API will list all the available mobile applications in MAS. 

URL:https://api.{mas-instance-id}.{mas.domain}/graphite/configtool/packages/?workspaceId=<frommasurl> 

<GET>https://api.dev.iam.np.maximo.com/graphite/configtool/packages?workspaceId=main

No Request Body is needed for this API.

Update a package

MAS Admin API for update package is not supported by IBM, even though it's published in IBM API documentation. So, we are using manage URL upload action.

We can download the app source code from the Application Administrator -> Application Configuration Mobile application. 

The downloaded ZIP file contains the complete application source code, configuration files, and the build directory with compiled artifacts. This package includes everything required to deploy the application to another environment.

Extract the zip file and locate the deployment package APPNAME__ver-version.zip in this <AppName>/build/app/build/ directory.

If build folder is missing in the downloaded ZIP file, ensure that the application is published before downloading. 

Upload the compressed file using Object Structure OSLCMAFAPPDATA Manage API. 

URL:https://{workspaceId}.manage.{mas-instance-id}.{mas.domain}/maximo/api/os/OSLCMAFAPPDATA?appid=<packageName>&action=wsmethod:uploadFile&version=<versionno>&apikey=<apikey>

<POST>https://main.manage.dev.iam.np.maximo.com/maximo/api/os/OSLCMAFAPPDATA?appid=CUSTOMTECHMOBILE&action=wsmethod:uploadFile&version=9.1.22.0&apikey=sg38w0fpli2fqdpi86fl2s6p3hdunqt724itim8h

In Request Body, choose binary and select the compressed zip downloaded from MAS UI.

After uploading the compressed file, refresh the application using Redownload option to view the latest code.

Delete a package

This API deletes a specific Mobile package application from the workspace. 

URL:https://api.{mas-instance-id}.{mas.domain}/graphite/configtool/packages/<packageName>?workspaceId=<frommasurl> 

<DELETE>https://api.dev.iam.np.maximo.com/graphite/configtool/packages/CUSTOMMOBILE?workspaceId=main&appid=manage

No Request Body is needed for this API. 

Courtesy: Majd-Naddour

References: 
ibm-apis/mas9.1/API--maximomobile 
envs-migrating-apps-in-mas-appconfig-91

Adding a Static Image as an Encoded Base64 String in Maximo Communication Templates

Adding a static image as an Encoded Base64 String in Maximo Communication Templates.

For static images that don't change frequently and where additional compression is not required, images can be embedded directly into a Maximo Communication Template as a Base64-encoded string, instead of hosting them from a server. 

The HTML <img> tag supports two methods for displaying images:

Using a Hosted image URL

<img src="https://unsplash.com/photos/a-puffin-peeks-out-from-white-flowers-V7KIXbMOuJw" / >

Using an Embedded Base64 Image

<img src="data:image/jpg;base64,iVBORw0KGgoAAAANSUhEUgAAApsAAAC4CAYAAACsNSfVAAAAAXNSR0IAr...." / >

<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAApsAAAC4CAYAAACsNSfVAAAAAXNSR0IAr...." />

By embedding images directly into the communication template, the image becomes self-contained and no longer depends on an external hosting location.

Converting an Image to Base64

An image can be converted into a Base64 string using various free online conversion tools.

• Download the image from its source URL or local location
• Upload the downloaded image to a Base64 conversion website
• Click the Encode button to generate the Base64-encoded string
• Copy the generated string and use it within the HTML img tag

                  

Adding a Static Image in Maximo Communication Templates

A static image can be added to a Communication Template either through the MAS UI or by updating the database directly. 

Using MAS UI
Open the Communication template and insert an image using the Insert Image Icon. 

Click "View HTML Source" to modify the underlying HTML and add a static image using a Base64-encoded string.

Manually add the img tag with src attribute containing the Base64 string.

Click on "View HTML source" icon again to return to rendered view and preview the static image in the Message section. 

It shows the differentiation between Images loaded from a hosted URL vs Images embedded directly as Base64 String. 

Updating the Database Directly using SQL

Alternatively, the existing hosted image URL in the communication template can be replaced with a Base64-encoded string directly in the database.

update commtemplate
set message = replace (    
    message,   
   'http://hostname/images/logo.jpg',
   'data:image/jpg;base64,/9j/4QC8RXhpZgAASUkqAAgAAAAGABIBAwABAAAAAQAAABoBBQABAAAAVgAAABsBBQABAAAAXgAAACgBAwABAAAAAgAAABMCAwABAAAAAQAAAGmHBAABAAAAZgAAAAAAAABgAAAAAQAAAGAiQnm=' )
where status ='ACTIVE';  

This approach is useful when updating multiple communication templates or replacing existing hosted images in bulk.

Before using Base64 images in communication templates, consider the following:

• Base64 images increase the overall HTML message size and performance.
• This method is best suited for small static images (icons, banners etc.,) which don't change often.
• If the image changes frequently or is large in size, hosting it externally may be a better option.

References
https://base64.guru/converter/encode/image/jpg

MAS 9.1 Configuration for SMTP with Office 365 using OAuth 2.0 for sending emails

MAS 9.1 configuration for SMTP server with Office 365 using OAuth 2.0 for sending emails from Maximo.

Microsoft plans to retire Basic Authentication for client connection. So, we need to know the OAuth configuration for sending emails.

Before configuring MAS, gather the following details from Office 365

Parameter	Value
Tenant ID	Used in Token URL 51624263-3eg2-2371-871c-d2176f17d56c
Token URL	https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token for example, https://login.microsoftonline.com/51624263-3eg2-2371-871c-d2176f17d56c/oauth2/v2.0/token
Scope	"offline_access https://outlook.office365.com/IMAP.AccessAsUser.All"
Client ID	Used in OAuth Handler gc2ec841-b89c-3f29-9853-17d034c434f9
Client Secret	Used in OAuth Handler Eow8Q~_jUB3NfevPmA_hhWpWUricBFtDzhaubcCa
Grant Type	refresh_token
Refresh Token	Used in OAuth Handler 1.AUEApSSkgQMdy0ukCtEC8h412ktCgSNmRCJOvKDhF1
redirect_uri	https://hostname/maximo
Email address	Email address having client authorization. It will appear as "Sent from" in Emails.

Configuration steps in MAS 9.1 are as follows. 

OAuth Client

• Open End Points Application, Click on Add/Modify OAuth Clients.
• Add a new End point OAuth Client, using the above information.
• Don't select Access Token persistent? check box - as it will store the data in MAXOAUTHCLIENT table and throw error if the refresh token generated by Microsoft is more than ACCESSTOKEN column length. 

By default, the length of ACCESSTOKEN & REFRESHTOKEN columns are 2000. In real time scenarios, the token of Microsoft and other applications for smtp mail server or E-mail Listenser mailbox configuration is more than 2000 characters. If you plan to use persistent token values, please increase the length of these fields. 

Office365 OAuth Refresh Token Generation 

If the refresh token is expired, we can follow the below link to generate a new one. 

Office365 OAuth Generating a Refresh Token

It's recommended to consult email service provider to know the refresh token lifespan and expiration after inactivity. 

As per the instructions, we need to store the files in the path c:\dev\ps

Output File with refresh token

SMTP System Properties

In MAS 9.1, a new system property mxe.mail.oauth.clientName is introduced to set the OAuth client name for mail server. 

System Property	Value
mxe.mail.oauth.clientName	OAuth Client MAILOAUTH
mail.smtp.host	smtp.office365.com
mail.smtp.port	587
mxe.smtp.user	no-reply-mas@ibm.com

To disable OAuth for sending emails, please set the mxe.mail.oauth.clientName property value to null. 

Import Certificates 

Navigate to MAS Suite -> Administration -> Configuration

Import the certificates for SMTP 

Courtesy Rethima Gali

References

Importing certificates in Maximo Application Suite - IBM Documentation
mas/maximo-manage/sending-emails-oauth
Microsoft to retire Basic auth for SMTP Auth
MAS Increase REFRESHTOKEN ACCESSTOKEN length for MAXOAUTHCLIENT

Maximo Database Table Data Purging

Maximo Database Table Data Purging involves removing unused data, indexes, and attachments that can slow down database read operations and consume unnecessary storage. 

Performing regular data purging helps improve database performance and reduce the storage cost of owning the cloud database service for clients.

Prerequisite: Always take a full Database backup before running purge scripts, especially in Production environment.

Common Data Cleanup Activities 

• Removing non-critical business data from out-of-the-box Maximo tables 

      Certain Maximo tables store operational or historical data that may no longer be required after a period of time. for example, CRONTASKHISTORY, ESCREPEATTRACK etc., Below are some sample scripts that can be used to purge old records.

-- delete crontask history records that are more than 2 years old based on start time
delete from crontaskhistory 
where starttime < dateadd(YEAR,-2,GETDATE());

-- delete communication log (includes escalation) 
-- that are more than 8 years old based on created date
delete from commlog 
where createdate < dateadd (YEAR,-8,GETDATE());
-- delete escalation repeat tracking records that have records in historyflag
delete from escrepeattrack 
where escalation='POCLOSE' and ownerid in (select poid from po where historyflag=1);
delete from escrepeattrack 
where escalation='SRCLOSED' and ownerid in (select ticketuid from sr where historyflag=1);
delete from escrepeattrack 
where escalation='ESCBLTNEXP' and ownerid in (select BULLETINBOARDuid from BULLETINBOARD where expiredate < dateadd(DAY,-1,GETDATE()));
delete from escrepeattrack 
where escalation in ('WOCAN','WOCLOSE') and ownerid in (select workorderid from workorder where historyflag = 1);
delete from escrepeattrack 
where escalation in (select escalation from escalation where active = 0);

• Delete child records first before parent records to avoid orphan records and maintain referential integrity in the database.

-- delete Message Tracking records 
-- that are more than 3 months old based on initial date time
delete from maxintmsgtrkdtl 
where  meamsgid in (select meamsgid from MAXINTMSGTRK where initialdatetime < dateadd(DAY,-90,GETDATE()));
delete from maxintmsgtrk 
where initialdatetime < dateadd(DAY,-90,GETDATE());   

-- delete Integration Error Messages 
-- that are more than 2 years old based on statusdate
delete from maxinterrormsg 
where messageid in (select messageid from maxinterror where statusdate < dateadd(YEAR,-2,GETDATE()));
delete from maxinterror 
where statusdate < dateadd(YEAR,-2,GETDATE());

• Batch Deletions 

        Deleting large volume of data in a single transaction can fill up transaction log and impact database performance. So, it's recommended to perform the delete operation in batches.

-- SQL Server Script
SET NOCOUNT ON;
 
    DECLARE @DeletedRows INT = 0;
    DECLARE @TotalDeleted BIGINT = 0;
    DECLARE @BatchStart DATETIME;
    DECLARE @StartTime DATETIME = GETDATE();
 
    PRINT CONCAT('Cleanup started at ', CONVERT(VARCHAR(19), @StartTime, 120), '.');
 
    WHILE 1 = 1
    BEGIN
        SET @BatchStart = GETDATE();
 
       delete top (50000) from escrepeattrack 
       where escalation='WOCLOSE' and objectname = 'WORKORDER' 
       and not exists (select 1 from workorder (nolock) 
       where escrepeattrack.ownerid = workorderid); 
 
        SET @DeletedRows = @@ROWCOUNT;
        SET @TotalDeleted += @DeletedRows;
        
        PRINT CONCAT('Deleted ', @DeletedRows, ' rows in this batch (started at ', 
                     CONVERT(VARCHAR(19), @BatchStart, 120), 
                     '). Total deleted so far: ', @TotalDeleted, '.');
         
        IF @DeletedRows = 0
            BREAK;
        
        -- Checkpoint after each batch to flush data and logs
        CHECKPOINT;
 
        -- Optional pause to reduce load
        WAITFOR DELAY '00:00:04';
    END;

• Reclaim Unused Data After Large Deletions - Database dependent
• When a large number of records are deleted from a table, unused space may still remain allocated.
• For MS SQL Server, rebuild the clustered indexes on the table after cleanup process to reclaim unused data pages and improves overall database storage efficiency. 
• This approach varies for other databases like DB2 or Oracle.  

ALTER INDEX [indexname] ON [dbo].[tablename] 
REBUILD PARTITION = ALL WITH (PAD_INDEX = OFF, 
STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, 
IGNORE_DUP_KEY = OFF, ONLINE = ON (WAIT_AT_LOW_PRIORITY (MAX_DURATION = 0 MINUTES, ABORT_AFTER_WAIT = NONE)), ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = OFF, DATA_COMPRESSION = PAGE)

• Create a procedure with all delete scripts if you plan to run same set of scripts against multiple databases and schedule to run in fixed intervals.

• Identifying Unused Tables and Indexes 
• Identify indexes and tables that aren't being used with help of DBA
• Disable the Indexes and drop the tables
• Always review the list with customer or business stakeholders before taking any action           

• Cleaning Up Unlinked Attachments

          Attachments from doclinks table may not be linked to valid records. 

select * from doclinks a 
where a.doclinksid in (select doclinksid from doclinks 
where ownertable='WORKORDER' and ownerid not in
 (select workorderid  from workorder) ) ;

Best practices

• Automate purge scripts using stored procedure if you plan to run same set of scripts against multiple databases
• Schedule cleanup jobs during off-peak hours 
• Test scripts in lower environments before production
• Monitor performance impact

Git DatabasePurgeScript.sql

Courtesy: Nausheel Patadia

Refresh Maximo Caches without Restart using Automation Script

A cache is a temporary storage layer in software systems that keeps frequently used data in memory, so it can be retrieved faster when needed again, without re-fetching it from the original slower source (e.g., a database or file system). This avoids repeated database calls, disk I/O, and expensive computations.

In MAS and Maximo 7.6.x version, caching is used to enhance performance and reduce system load. Maximo manages the caches using custom, Java-based, local in-memory caches within a JVM.

Each cache is local to the JVM within a WAS Liberty instance. It's non-persistent; the cache data will be cleared on server restart.

There are many types of caches used to improve performance. These caches store data such as metadata, application definitions, maxvars, system properties, security group, Object Structure Authorization and domain values to avoid repeated database queries. 

There are 75+ Caches available in MAS 9.0.x version, some of the known ones are listed in the below image. 

* complete list of cache is listed in this file CacheList.csv

A common requirement in production systems is to refresh cache without restarting servers to avoid outages and downtime. Fortunately, Maximo provides a method to reload caches programmatically, and we can do it with an automation script.

How to refresh Maximo Cache using Automation Script?

• Create an Automation Script without launch point that accepts a parameter "cachename". 
• It refreshes a specific cache or all caches in all servers 

from psdi.util import MXException
from psdi.server import MXServer

cache  = request.getQueryParam("cachename");
notvalid= True;

# Refresh a specific Maximo cache in all servers
if (cache != 'all' and cache is not None):
    notvalid = False;
    try:
        ALL_SERVERS = True
        MXServer.getMXServer().reloadMaximoCache(cache, ALL_SERVERS)
        
        bodyMessage = "\"" + cache + " Refreshed in all Servers\""
        responseBody =  '{' + "\"response\"" + ": "  + bodyMessage + '}';

    except MXException, err: 
        print "---| CACHEREFRESH ::: refreshcache  : "+str(err);
        responseBody =  '{"response": "error", "error": "'+str(err)+'"}';

#  Refresh All Maximo Caches in all servers
if (cache=='all' and cache is not None):
    notvalid = False;
    try:
        ALL_SERVERS = True
        server = MXServer.getMXServer()
        cacheNames = server.getMaximoCacheNames()
        
        for cacheName in cacheNames:
            server.reloadMaximoCache(cacheName,ALL_SERVERS)
        
        responseBody =  '{"response": "All Maximo Caches Refreshed"}';

    except MXException, err: 
        print "---| CACHEREFRESH ::: refreshcache  : "+str(err);
        responseBody =  '{"response": "error", "error": "'+str(err)+'"}';

# input param is not valid
if (notvalid):
   responseBody =  '{"response": "noactionpresent"}';
 

Code - cacherefresh.py

How to use this Script?

• Invoke the automation script via https REST API GET call with query parameter "cachename"

If cachename = all, it will refresh all caches in all servers.

https://hostname/maximo/oslc/script/CACHEREFRESH?lean=1&cachename=all

Output: {"response": "All Maximo Caches Refreshed"}

If cachename=<AnyValidCacheName>, it will refresh a specific cache in all servers.

https://hostname/maximo/oslc/script/CACHEREFRESH?lean=1&cachename=MAXPROP

Output: {"response": "MAXPROP Maximo Cache Refreshed"}

If cachename is null, it will throw an error message.

https://hostname/maximo/oslc/script/CACHEREFRESH?lean=1

Output: {"response": "noactionpresent"}

On a few cases, such as the Integration Cache (MAXEXTIFACEOUT), refreshing during normal business hours is not recommended. Doing so can disrupt live transactions coming from middleware, as they may not receive the latest cache data. It’s best to schedule these cache refresh operations during off-peak or after-hours periods when transaction volumes are minimal.

MAS 9.1 offers an out of box API to clear Profile Cache in all pods.

https://hostname/maximo/api/service/security?action=wsmethod:clearProfileCache&lean=1

JSON Body for this API:
{ "userID": "MAXADMIN" }

References:

Custom REST API using Automation Script

How to use Maximo HTTP Handler Exit Automation Script for Endpoint Customization

IBM Maximo's Integration Framework allows us to customize HTTP Endpoints using Automation Script Call Back Exit methods.

An HTTP Handler Exit is a script-based customization hook that lets us to intercept and modify HTTP requests or responses for Maximo Endpoints.

Below are the supported callback functions and their use cases:

Call Back Function	Use Case
getUrl(req)	Dynamically modify the target URL based on environment for example, if you want to append a resource id in the existing URL
urlProps(req)	Set URL parameters such as access key from System property or any record ID like WONUM for query
headerProps(req)	Set authentication token as header param from an external URL
processResponse(resp)	Set Maximo error for any response code or response body message Read an Unique ID from response and update it in MBO

req object is implemented by psdi.iface.router.ScriptHTTPReq

resp object is implemented by psdi.iface.router.ScriptHTTPResp

How to Configure the HTTPEXIT Property:

• Create an End point for HTTP handler
• Set HTTPEXIT property to the value script:{script name}, for example, script:HTTPEXIT where HTTPEXIT is an automation script name

• Ensure the script exists as an Automation Script without a launch point.
• Enable the flag "Allow Invoking Script Functions?" to enable call back functions to work in Automation Script. It's editable only at the time of creation. 

from psdi.iface.mic import MicUtil
from psdi.util import MXApplicationException
from com.ibm.json.java import JSON
from java.lang import String

def urlProps(req):
    propertyValue = MicUtil.getProperty('mxe.int.customkey')
    req.addUrlProp('Access-Key',propertyValue)
	
def headerProps(req):
    req.addHeader('Content-Type','application/json')
	
def getUrl(req):
    customURL = req.getURL()
    customURL = customURL + "uniqueID"
    req.setUrl(customURL)
	
def processResponse(resp):
    if resp.getResponseCode() > 201:
        stringData = String(resp.getData(), "UTF-8")
        respjson = JSON.parse(stringData)
        params = [respjson["message"]]
        resp.setError(MXApplicationException('iface','customerrmsg',params))
        # iface, customerrmsg maxmessage must be available with {0} as content 

code: httpexitmethods.py

Courtesy: Wasim Tobal | LinkedIn

References: IBM Maximo Autoscripting Guide – Endpoint script

Maximo ACM - Asset Configuration Manager Add-On

Maximo ACM (Asset Configuration Manager) is an Add-On  for MAS Manage & Maximo 7.6.x earlier versions.

What is ACM used for ? 

Maximo ACM is designed to help manage the configurations of high-value, complex, and regulated assets such as aircraft, rail vehicles, engines, and weapon systems by tracking their configuration throughout their lifecycle.

Purpose of ACM

ACM helps ensure that assets remain compliant with their original design and maintenance requirements. It is essential in industries where safety, compliance, and traceability are critical.

 

Core Components of ACM

ACM is built with three key components:

1) Reference Data  

When we receive an Asset (Train/Locomotives/Aircraft) and its components, we must create engineering reference data (as designed) for it. The reference data specifies the configurations allowed for the asset and how it is maintained.

This defines the "as-designed" configuration of the asset, including:

• Models
• Positions
• Items/Parts
• Maintenance Programs
• Meters
• Configuration Rules
• Variants 

2) Operational Data 

It refers to the data about production assets as they are maintained to perform their day-to-day operations.  

The "as-maintained" data includes:

• Asset creation and tracking of sub-assemblies and serialized components
• Installation/removal of components
• Scheduled and unscheduled maintenance
• Meter-based overhauls
• Design modifications and upgrades
• Maintenance history

3) Build Data Interpreter (BDI) 

BDI validates any operational changes to Configuration Managed (CM) Assets. It checks each position against the reference data and its configuration rules that are defined for the associated Model. 

It reports the status of non-compliant assets in the Assets (CM) application through color-coded data.  

Some key features of Maximo ACM:

Models (CM) 

A model can represent a top-level asset (aircraft or train), or an equipment assembly, such as an engine or HVAC sub-system. 

• Installable? flag can denote whether this Model can be installed on another Model hierarchy. An Installable Model of a coach or car can be used in many other models like Train.

• A Build Item is a part or an assembly of parts. In an aircraft model, a build item for an engine will contain a CM Item assembly that forms a hierarchy for engine.

BDI Cron Tasks 

BDI runs scheduled jobs via the Cron task PlusABDIAsyncImmediateJobCron to automate actions such as: 

•  Change PM Status
•  Generate PM records from Master PM 
•  Create WO from PM using alert point
•  Create PM records when Assets are created

Meter Readings For CM Assets

For CM-Managed Assets, Maximo don't support an "Accept Rolldown From" = ASSET or LOCATION for child assets/locations. It must be set to NONE. 

It's the default value when new ASSETMETER records are created for CM-Managed Assets. 

ACM uses a dynamic meter calculation for CM-Managed assets based on asset configuration history. As such

there is no need to roll down (duplicate) the meter readings on the sub-assembly assets.

This enables meter readings to be more easily altered or corrected and also if the configuration history is modified, for example, a child Asset is removed/installed, the dynamic calculation ensures the meter totals for these child Assets are accurate.

If you set "Accept Rolldown From" to ASSET or LOCATION, Maximo will record incorrect values by multiplying the Asset meter totals.

Work Types that resets Meters

ACM related Work Types: OVHL (Over Haul) , REP (Repair) & INSP (Inspection) when used in Work Order for an Asset will reset the Time Since (Over Haul, Repair & Inspection) Meter Reading to 0 on moving the Work Order status to Complete.

Technical Records

Technical Records (CM) application is used for upgrade or modifications campaigns, such as: 

• Software Updates
• Safety driven modifications
• Part replacement

You can define: 

• Narratives describing the change
• Compliance status (mandatory or optional)
• Associated models and variants
• A CM Item to be upgraded and its position in the model hierarchy
• An Inoperative Date that indicates when BDI should apply the upgrade
• A Superseding CM Item, representing the new upgraded part

The "Apply Multiple Upgrades?" option allows grouping multiple asset upgrades into one Work Order. 

 

Technical Records do not perform automatic installation/removal of an Asset in the build hierarchy—it only updates the part number.

Courtesy: Nausheel

References: 

MAS-ACM-BDI

IBM-documentation/ACM