Maximo Asset Management 7.6.0.7 Interim Fix 005 released

The Interim Fix (IFIX) is available at Fix Central.

As with all IFIXes, MAM 7607 IFIX 005 is cumulative and includes all fixes provided with Maximo Asset Management 7.6.0.7 Interim Fix 004, with these additions:

APAR	Application Name	Description
IV89431	Security Groups	Access is required to create work orders and tasks.
IV95332	Assets	In the Assets application, for multiple assets, you cannot change the status in the background.
IV98279	Conditional Monitoring	In the Conditional Monitoring application, when you add a job plan to a condition, the prioirty does not populate.
IV94406	Graphical Scheduling	In the Graphical Scheduling application, when you use Microsoft Internet Explorer 11, the Gantt view does not render.
IV94978	Job Plans	In the Job Plans application, when auto-number functionality is enabled, job plan predecessors are not recorded correctly in the database.
IV92471	Purchase Orders	In the Purchase Orders application, when you use the Go To function on a purchase order line and the work order site is different that the main purchase order site, records are not returned.
IV93059	Automation Scripts	When you change the status of an asset, an automation script causes an exception.
IV97336	System Object	When you install one or more secondary languages, some messages in the browser are incorrectly translated.
IV95258	System Object	Maximo searches on the SQL server are adding additional brackets that cause the search to fail.
IV90039	Inventory Usage	In the Inventory Usage application, you cannot update an inventory usage document if it has an associated reservation that is canceled.

To install the IFIX, see Installing an Interim Fix in Maximo 7.6.

MxLoader now supports attachments

MxLoader now supports attachments

I have just implemented the capability to upload attachments straight from MxLoader. This is in response to some requests on my blog and MxLoader support forum.

Starting from Maximo 7.1.1.6 it is possible to import attachments to an object through MIF using Base64 encoding.
MxLoader has the capability to read files from the filesystem, encode them in Base64 and upload them on Maximo. This can be done on any Maximo object that supports attachments but the integration object structure has to be modified to include the DOCLINK object.

In this example the MYASSET object structure has been created with the DOCLINKS child object.

To specify a file to be uploaded you have to prefix the full path of the file with the ‘file:///’ string. Look at the screenshot below for an example of how to add two attachments to an asset.

Maximo Work Center Performance

Question

How can I improve the performance of the Work Centers introduced in Maximo Version 7.6.0.5?

Answer

Starting with Maximo 7.6.0.5, new Work Centers display role-based activities in an innovative, responsive User Interface.
To improve the load time of the content within the various work centers and containers, insert the following indexes in your database utilizing Maximo's Database Configuration application. If you do not add the indexes in the Database Configuration application, Maximo will not recognize the indexes, and will not re-add the indexes if the table needs to be created.

Note: The index names are suggested values. Update them to meet your unique business and identification requirements.

For DB2 Databases
CREATE INDEX "MAXIMO"."WORKORDER_WC_NDX01" ON "MAXIMO"."WORKORDER" ( "STATUS" ASC, "HISTORYFLAG" ASC, "ISTASK" ASC, "WORKORDERID" ASC, "SUPERVISOR" ASC ) ALLOW REVERSE SCANS COLLECT STATISTICS;

CREATE INDEX "MAXIMO"."WORKORDER_WC_NDX02" ON "MAXIMO"."WORKORDER" ( "STATUS" ASC, "WOCLASS" ASC, "ISTASK" ASC, "WORKORDERID" ASC, "SITEID" ASC ) ALLOW REVERSE SCANS COLLECT STATISTICS;

CREATE INDEX "MAXIMO"."WORKORDER_WC_NDX03" ON "MAXIMO"."WORKORDER" ( "STATUS" ASC, "HISTORYFLAG" ASC, "ISTASK" ASC, "WORKORDERID" ASC, "WORKTYPE" ASC ) ALLOW REVERSE SCANS COLLECT STATISTICS;

CREATE INDEX "MAXIMO"." PO_WC_NDX01" ON "MAXIMO"."PO" ( "REQUIREDDATE" ASC, "VENDOR" ASC, "STATUS" ASC ) ALLOW REVERSE SCANS COLLECT STATISTICS;

CREATE INDEX "MAXIMO"."MAXINTOBJECT_WC_NDX01" ON "MAXIMO"."MAXINTOBJECT" ( "USEWITH" ASC, "DESCRIPTION" ASC) ALLOW REVERSE SCANS COLLECT STATISTICS;

For Oracle and Sql Server Databases
CREATE INDEX "MAXIMO"."WORKORDER_WC_NDX01" ON "MAXIMO"."WORKORDER" ( "STATUS" ASC, "HISTORYFLAG" ASC, "ISTASK" ASC, "WORKORDERID" ASC, "SUPERVISOR" ASC );

CREATE INDEX "MAXIMO"."WORKORDER_WC_NDX02" ON "MAXIMO"."WORKORDER" ( "STATUS" ASC, "WOCLASS" ASC, "ISTASK" ASC, "WORKORDERID" ASC, "SITEID" ASC );

CREATE INDEX "MAXIMO"." WORKORDER_WC_NDX03" ON "MAXIMO"."WORKORDER" ( "STATUS" ASC, "HISTORYFLAG" ASC, "ISTASK" ASC, "WORKORDERID" ASC, "WORKTYPE" ASC );

CREATE INDEX "MAXIMO"."PO_WC_NDX01" ON "MAXIMO"."PO" ( "REQUIREDDATE" ASC, "VENDOR" ASC, "STATUS" ASC );

CREATE INDEX "MAXIMO"."MAXINTOBJECT_WC_NDX01" ON "MAXIMO"."MAXINTOBJECT" ( "USEWITH" ASC, "DESCRIPTION" ASC);


For additional details on the new Maximo Work Centers, access this page

Collecting Data: Maximo Work Centers

Problem(Abstract)

Collecting data for Maximo Work Center's. Gathering this information before calling IBM support will help you with the troubleshooting process and save time analyzing the data.
You may need to review General information, Please see General Collecting Data document 1313647 and include that information.

Resolving the problem

a. Check the exact version information of Maximo, Integration Framework, Work Centers installed in your environment. Please include a snapshot of the System information similar to the one below:

b. The System Information should include the App Server and database.

1. Verify the following Maximo properties:
-  mxe.oslc.restwebappurl - http://<ipaddress>:<port>/maxrest/oslc
-  mxe.oslc.webappurl - http://<ipaddress>:<port>/maximo/oslc/
-  weatherapi.apikey - Does a valid weather api key exist

2. Verify the Object Structures used in Work Centers.

      Verify the following Object Structure Authorization Names:

          - MXAPIWODETAIL-                                            - MXAPIASSIGNMENT -
Authorization Name: MXAPIWODETAIL              Authorization Name: MXAPIASSIGNMENT

- MXAPIKPIMAIN -                                             - MXAPIWMASSIGNMENT -
    Authorization Name: MXAPIKPIMAIN                      Authorization Name: MXAPIWMASSIGNMENT


- MXAPILABOR -                                                    - MXAPIPERUSER -
      Authorization Name: MXAPILABOR                           Authorization Name:  MXAPIPERUSER

For the following Work Centers, verify the following access permissions are set on the specified Object Structures:




 3. Weather

•  weatherapi.apikey - Does a valid weather api key exist in System Properties?
• What is the City, State, Postal Code / Zipcode, Country defined for the person attempting to login to the Work Center?

4. Which device are you using to access the work center?
     - Mobile Device: Android / iOS / Windows - Which browser/version on device?
     - Desktop: MAC/PC and which browser and version?

5. Check the Network and console tabs within the browsers development tool and check to see if any errors obviously appear. If so, please attach.

6.  KPI CronTask
     - Verify "KPICronTask" is Active and has a frequency defined.

7. KPI Manager
   - Verify each user has their own KPI's defined:  
Example:    'KPINAME'+<USERID>

8. In the Security Groups application, what is the Work Center defined for the group your user is attempting to access?

9. Does your user belong to multiple Security Groups that contain Work Centers?

10. In the KPIManager application do you have the following KPI's defined for your user you are logging in with?

Supervisor Work Center
- EMWOSUP<userid>
- PMPERFSUP<userid>
- PMWOSUP<userid>

Technician Work Center
- AVGEMCOMPTIME<userid>
- WOOVERDUE<userid>

* Verify the where clause for each KPI has the userid defined as the value for the laborcode.

11. Were there any errors in the Maximo system log? If so, please attach the log.

Business Analyst Work Center 

1. Is there a registered Watson account (and is it a free or pro account) with a callback uri set to the Maximo WATSONOAUTH endpoint?

2. Is the client id/secret from the Watson account above set in the WATSONOAUTH endpoint?

3. Does the user exporting a dataset have their own Watson account?

4. Is the api_file cron task enabled?  If so, what is its schedule set to?  When was it last run? 

Giving users access to the Service Request Work Center and Data Set Designer in Maximo Asset Management 7.6.0.6

Problem(Abstract)

The object structure requirements for the Service Request Work Center and the Data Set Designer were documented incorrectly for Maximo Asset Management 7.6.0.6.

Resolving the problem

The following website provides details on how to give users access to Work Centers and the Data Set Designer:

https://www.ibm.com/support/knowledgecenter/SSLKT6_7.6.0.6/com.ibm.mbs.doc/workcntr/r_obj_str_wrk_cntr.html

In addition to the object structures listed for the Service Request Work Center, the following object structures are required: MXNOTIFICATION, MXAPILOCATION, MXAPILOCANCESTOR, MXAPIASSET, and MXAPIPERUSER.

The complete list of object structures for the Service Request work center is:
MXAPISR (Read, Save, Delete, Insert)
MXAPIWORKLOG (Read, Save)
MXAPIBOOKMARK (Read, Delete)
MXAPITKCLASS (Read)
MXAPITKTEMPLATE (Read)
MXAPIPERUSER (Read)
MXNOTIFICATION (Read, Save)
MXAPILOCATION (Read)
MXAPILOCANCESTOR (Read)
MXAPIASSET (Read)

In addition to the object structures listed for the Data Set Designer, the MXAPIENDPOINT object structure is required with read access. Additionally, the MXAPIANALYTICDATASET object structure requires read, save, change status, and delete access.

Setting up Password Expiration in Maximo

Security; Password Expiration; Groups; TPAESECURITY

How to set up password expiration in Maximo.

Answer

Password Expiration can be set in a few places in Maximo. The default setting is set In the Security Groups application, in the Select Action menu, using the Security Controls option.
All new groups created after this setting is made will inherit this value, however any groups that existed prior to this setting being in place will not get updated.
This value only gets referenced when a new group is created.
If a group is created and has inherited the value, then the value is changed in the Security Controls option, the groups that existed prior to this change will not be updated.
For this reason, when setting up Maximo for the first time, it may be better to decide on a default password expiration value and have that value in place prior to creating your groups.
Once the value for a group has been set, or if no value has been set prior to creating the group, you can update the password expiration setting by using the Override Password Duration option in the Select Action menu of Security Groups.
This also allows you set a specific password duration at a group level different from the default.
Here is a breakdown of how the password expiration is handled by Maximo:
Each group has a password expiration value.
If a user belongs to more than one group, the longest expiration period is the one inherited.
For example, if a user belongs to one group that has a setting of 90 days and another that has a value of 30 days, the user inherits a 90 day expiration setting.
In the case of a user belonging to any groups not containing a password expiration, the user's password will never expire.
You would need to use the Override Password Duration option to set an expiration value for each group the user belongs to.
Once the password expiration settings are set, the clock starts to count down after the password is changed with the expiration settings in place.
NOTE:
If the user existed before the password expiration is set, the password will not expire because the timer does not start until the next password change after the password expiration has been set.
The remedy is to change the user's password after setting the password expiration.
Removing the user from the group the expiration date is set on and adding them back will also work.

Creating summary or detail Query-Based Reports in cloned (duplicated) applications

Question

From Maximo 7.1.1.6 onwards, you can create Summary or Detail Query-Based-Report (QBR). But in cloned applications, the option to select the type of QBR is disabled. How can you enable that option?

Answer

The steps below will show how to create the Summary or Detail QBR in cloned applications with an example:

1. Go to Application Designer - Open the WOTRACK application.

2. Select Action - Duplicate Application Definition - Create WOTRACK2 application with the description 'Work Order Tracking 2'.

3. Go to Security Group - Give adequate privileges for the WOTRACK2 application to the security group, for example MAXADMIN.

4. Login again and open the WOTRACK2 application.

5. Click on the 'Create Report' toolbar button to create the Query-Based-Report.

As you can see below, the option to be able to select the style of report ( Summary or Detail Report) is not enabled.

By default, all cloned (duplicated) applications have the same problem.

In order to enable the option above, please follow the steps below:

When the WOTRACK2 application is cloned from WOTRACK , the WOTRACK2 application has the same report object as the original application WOTRACK.

For example:

1. Create the report object for the cloned application (WOTRACK2).

Go to the Integration / Object Structures application - Find 'REP_WORKORDER' .

Based on 'REP_WORKORDER', create the new report object for WOTRACK2 called 'REP_WO2' (you can also duplicate 'REP_WORKORDER' to create 'REP_WO2' )

-- Object Structure : REP_WO2

-- Description : Work Order Details 2

-- Consumed By : REPORTING

-- Application : WOTRACK2

2. Save the record.

3. Go to the Report Administration application.

4. Run Select Action / Set Report Object Structure Security.

5. Filter application with the value 'Work Order Tracking 2' . You can see the newly-created report object 'REP_WO2' for WOTRACK2 application.

P.S. : the WOTRACK2 application's description is 'Work Order Tracking 2'.

The REP_WO2 report object's description is 'Work Order Details 2'.

6. Now you need to define any security groups who can access the newly-created report object .

- Click New Row

- Add the 'MAXADMIN' group.

7. Go to the 'Work Order Tracking 2' application (WOTRACK2)

Try to run 'Create Report'. Now you can select the style for the QBR report (Summary or Detail).

Why am I unable to create a new inspection form in the Work Center? Most likely, you are not granting access to integration objects that are related to the Work Center Yes, in order to use the Work Center, specific integration objects must be created (by default when Maximo is installed) or you must manually create them yourself If it is the first time the Work Center is being used, it is necessary to check if all integration objects related to it are created and if they have access grant But back to the specific problem of not being able to create a new inspection form, please take a look at the steps below: (Detail: You must be logged in as MAXADMIN to perform these steps) 1) Go to Integration > Object Structures application and make sure you have the following objects: MXAPIINSPFORM MXAPIINSPFORMSTATUS MXAPIINSPRESULT 2) Go to Security Groups application and bring up the group for work center - To manager the Inspection Forms, I believe that the user is in the BIZANALYST - Business Analyst group 3) Go to Applications tab > seach for Manage Inspection Forms (in the Description column) Give the grant access Access to Manage Inspection Forms -> Grant Access? checked 4) Go to Object Structures tab > search for MXAPIINSPFORM and give the grant access for all options bellow: Delete MXAPIINSPFORM Insert MXAPIINSPFORM Read MXAPIINSPFORM Save MXAPIINSPFORM Please perform the same steps to MXAPIINSPFORMSTATUS and MXAPIINSPRESULT objects Save and try to create the new form in the Work Center. I hope this tip helps you

Maximo Asset Management 7.6.0.7 Interim Fix 004 released The Interim Fix (IFIX) is available at Fix Central. As with all IFIXes, MAM 7607 IFIX 004 is cumulative and includes all fixes provided with Maximo Asset Management 7.6.0.7 Interim Fix 003, with these additions: APAR Application Name Description IV94884 System User Interface After you change the vertical label value to 0, radio buttons shift. IV97283 Application Designer In the Application Designer, in the Create Work Order with Appointment window, an invalid binding occurs. IV97448 Work Order Tracking In the Assets application, when an asset meter has a datetime value and you enter an identical value in the field, the meter has varying results. IV96894 Assignment Manager In the Assignment Manager, availability is displayed after vacation hours have been allocated. IV96610 Invoices In the Invoices application, when you use large currency exchanges, an error occurs. IV91405 Receiving In the Receiving application, when a vendor on a purchase order has a different exchange rate than the purchase order, you cannot return a rotating asset. IV97236 Receiving In the Receiving application, you cannot return rotating assets. To install the IFIX, see Installing an Interim Fix in Maximo 7.6.

Maximo Asset Management 7.6.0.8 Interim Fix 001 released The Interim Fix (IFIX) is available at Fix Central. APAR Application Name Description IV95250 Work Order Tracking After you attach a job plan to a work order, the scheduled started and finish dates are read-only. IV96829 System Object Security Scans See CVE-2017-5644, CVSS Base Score: 5.3 and IBM X-Force Exchange: CVE-2017-5644 for the current CVSS Temporal Score. IV97448 Work Order Tracking In the Assets application, when an asset meter has a datetime value and you enter an identical value in the field, the meter has varying results. IV97391 Assets In the Assets application, when you create a duplicate asset, spare parts are not duplicated. IV97196 Graphical Assignment In the Graphical Assignment application, when you execute the Run Optimization action, an exception occurs. IV96724 Graphical Scheduling In the Graphical Scheduling application, when you assign work, a null pointer exception occurs. IV97261 Graphical Scheduling In the Graphical Scheduling application, when you create a schedule, constraints disappear after you commit the schedule. IV97261 Graphical Scheduling In the Graphical Scheduling application, when you create a schedule, constraints disappear after you commit the schedule. IV97237 Graphical Scheduling In the Graphical Scheduling application, when you duplicate a work order, the duration in the schedule is incorrect. IV97132 Graphical Scheduling In the Graphical Scheduling application, when you hide the navigation menu, the Resource section is no longer in sync. IV97416 Graphical Scheduling - Large Project In the Graphical Scheduling-Large Project application, on the GANTT View tab, no data is loaded. IV95428 Invoices In the Invoices application, you cannot approve a multi-line invoice that is associated to a repair if a rotating asset is in the repair location. IV96609 KPI Manager In the KPI Manager application, when you duplicate a record, the Created By field retains the ID of the user who created the original record. IV97453 Labor Reporting In the Labor Reporting application, when a Labor record has multiple crafts associated to it and you create a new row on the Labor record, the Craft field is not populated. IV96188 Work Order Tracking In the Work Order Tracking application, the Actual Material Cost attribute on the work order table is calculated incorrectly. IV96965 Work Order Tracking In the Work Order Tracking application, you can create constraints that allow circular values to be entered. IV97026 Work Order Tracking The map persistence is not kept in either the Work Order or Location application. IV94523 Work Order Tracking When a work order has multiple activities and you change the status of one of the activities to completed, the status' for all activities are changed to complete. IV95042 System Properties When creating a new change record, you attempt to select a value from a field. Instead of retrieving the record, you receive the following message: BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code 1795.  The record could not be retrieved from the database. IV97583 Integration Modules When you delete an application authorization record with the Maximo Integration Framework, an error occurs. IV96511 System User Interface You can attach files files that do not have file extension types. IV96781 Graphical Scheduling In the Graphical Scheduling application, when you create a new schedule or work list, an error occurs. IV96422 Communication Template Security defect To install the IFIX, see Installing an Interim Fix in Maximo 7.6.