Calculation explained of -Estimated Next Due Date (PMMETER.DATEOFNEXTWO)- field in Maximo Base Services?

Technote (FAQ)


Question

How is the -Estimated Next Due Date (PMMETER.DATEOFNEXTWO)- calculated in Maximo Base Services?

Answer

This calculation is done on the 'Meter Based Frequency' tab.
When any of the following are updated:

PM - LastStartDate
PM - UseTargetDate
PM - LastCompDate
PMMeter - Frequency
PMMeter - LastPMWogenRead

The dateofnextwo is updated with the following case.

It finds the next generation date for a PMMeter.
If no date can be generated for this PMMeter, null will be returned.

It finds the earliest meter based due date considering all meters listed on the PM for:

- ASSETMETER - lastreadingdate
- ASSETMETER - average

In addition, it also sets the earliest next due date in PM.


Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management IBM SmartCloud Control Desk Not Applicable AIX, HP-UX, Linux, Solaris, Windows 7.5, 7.5.1
Systems and Asset Management Tivoli Asset Management for IT Not Applicable AIX, HP-UX, Linux, Solaris, Windows 6.2.8, 7.1.1, 7.1.2, 7.5
Systems and Asset Management Tivoli Service Request Manager Not Applicable AIX, Linux, Solaris, Windows 2003 server 6.2.8, 7.1, 7.1.2, 7.5
Systems and Asset Management Tivoli Change and Configuration Management Database AIX, Linux, Windows, Solaris, HP-UX 6.2.8, 7.1.1, 7.1.2, 7.5

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Maximo Asset Management
Assets

Software version:

6.2.8, 7.1.1, 7.1.2, 7.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1625139

Modified date:

2014-01-07

Translate my page

Machine Translation

Content navigation