Skip to main content

Playing with Time Zone in Maximo - Time Zone Rules

 

IBM Maximo 7.6.0.8 onwards provides a new application – “Time Zone Rules”. This application can be accessed from Administration > Time Zone Rules.



In the Time Zone Rules application, users can create rules on different processes on which time zone shall be applied from the process rule. Records will show the local date and time of the user who is accessing the record even if the record was created in a different time zone. Time zone rules can be associated with a process at the system, organization, or site level.

Let us see how time zone rules work in Maximo with the example of PM Work Order generation. Following are the steps to be followed in this example-

1.First create a rule for PM Work Order Generation where Time Zone will be picked from the Asset record on the PM.



2.The current user that I am using has Time Zone set to Asia/Kolkata as shown below-



3.Maximo Application Servers are in EST time zones in the US.

Now, let’s select an asset and associate Time Zone to America/Los Angeles (PST).



4.Next create a PM record against this asset with time-based frequency of each day and generated work order against this PM.



5.Open this work order in Work Order Tracking and check for Target Start Date and Target Finish Date which has date time as 4/20/21 12:30 PM.



6.Go back to this asset and remove the time zone by again accessing select action – Associate Time Zone and select check box – Remove Time Zone as shown below before pressing OK button.



7.In next step generate a Work Order from PM# 1191. Once work order is generated, go to Work Order Tracing and check for Target Start Date and Finish Date.

As shown in screen shot, you will be able to see the Target Start Date and Target Finish Date has been switched back to server’s time zone and equivalent time as per the logged in user’s profile.



Hopefully, this helps to understand the functionality of how Time Zone Rules can be used effectively for tracking the crucial transactional aspects like Maintenance Window, etc., even when a record is created in a different time zone.

Comments

Popular posts from this blog

Maximo OSLC Integration with External System- Get data in JSON format

Greetings! If you have noticed recent version of Maximo, couple new application in Integration module has been added which are OSLC Resources and OSLC Provider.These modules gives us ability to integrate with external system in JSON. OSLC is an open community that creates specifications for the integration of products and/or tools.  IBM is a leading contributor to this community and many software products within the IBM Software Group are implementing OSLC in order to enable cross-product integrations. An OSLC integration requires 2 players-  1. OSLC Consumer application 2. OSLC Provider application.   An OSLC provider application makes containers of associated resources(data) available for integration through service providers. Consumer applications then use these service providers to query resources and to create, update, and delete resource data.  The consumer application sends a query to the service provider for resource data. The service provider provides a link

Power of Maximo Formulas - Build logic w/o Custom Java code or Automation Script

Greetings! Maximo 7.6 has lot of additional capabilities added in Tivoli Automation Engine as compared to older versions of Maximo which aim to allow users to make change in applications for small requirements without actually going to customization route. Automation scripts is one of such tool given for users and technical developers to change the behavior of Maximo in case where functionalities can't be changed only via use of configuration. If we have a requirement to populate some field on basis of other fields , we can easily do that with automation script but in order to do that you still need to have knowledge of Jython or Javascript to write the logic. Maximo formula is one the tool given by IBM which can be used for such business requirements and user can make changes to Maximo logic via configuration without getting into difficulties of coding. Formulas are available from Maximo version 7603. With release of Maximo version 7606, there has been addition of new capabil

Call publish channel w/o enabling Event Listener in Maximo

Greetings! Generally if we have to send data to external system via MIF, we create Publish Channel and enable Event Listener on publish channel. Once event listener is enabled, Maximo listens for event and send data to end point via publish channel for each Save of related MBO . But t here are many scenarios where we need to send data to external system using publish channel on specific event and not for every save. In order  to send to external system on specific event, for example - sent data to Ariba when PO status in Maximo is changed to APPR, we can use automation script or java code to call publish channel on the go. Below code can be used in automation script - server = MXServer.getMXServer() userInfo = mbo.getUserInfo() whereClause = <CONDITION> server.lookup("MIC").exportData("<Publish Channel Name>", "<External System Name>", whereClause, userInfo, 1000) Via Java class - MXServer server = MXServer.getMXServer();