When a PM Task is generated from a Standard Task the Planned Start Date on the WO Task is the calendar date required at 12:00:00 AM. When the task is printed the Planned Start date that is printed is the above start date plus/minus the hours different than the time zone of the Assetwise server. This is having the effect of a PM being a day off.
Is there a way to add or subtract hours to the PM generation?
It would also be nice to have the Planned Start Date and Time be generated to reflect the true start time such as a morning job starting at 7:30 AM or an afternoon job starting at 1:00 PM.
This is acheivable using multiple PM Generation profiles to selectively trigger jobs at the time of day that you want set as the start time.
PM profiles have reoccurrence pattern settings that you could use to pinpoint the desired time and they have a wide array of filter criteria (enhanced in 7.4) to ensure that you can hone in on the jobs that would be controlled by the PM profile.
The Generate PM Work Orders scheduled action will scan the PM Profiles to see which ones need to be run every time it executes. So you would set the Scheduled frequency for this action to multiple times per day, spaced out so that you are assured your Morning jobs Profile is picked up as close to 7:30am as possible, and that your Afternoon jobs Profile is picked up as close to 1pm as possible. You can add Profiles to cover Evening jobs and Night jobs also. If you schedule the Generate PM Work Orders action to run every 1/2 hour, you should be able to achieve what you are looking for.
Perhaps this could also be setup to compensate for the time differences? Or it might require some customization in the report? I am not sure about this, we would have to consider/analyze a specific scenario.
Currently, the way the time works is that the data in the database is set to the time of the Server hosting the database. The time is then 'regionalized' by the APM server that a client connects to. Perhaps knowing this will help in setting things up.
I think that your challenge can be resolved with strategically timed execution of selective PM profiles, however, I would be remiss if I did not mention that we are currently working on migrating to use UTC time( R7.7 era). Not sure when it is coming, as it is a large project which has extended multiple releases already. The general ambition is to have the time be a function of the client time, not too much different in concept as we have now, but more flexible. It is more a change in the underlying mechanics of it that make it a big project for us. I would chance to say that it will likely have minimal impact on the work to be done with respect to PM Profile schedules, but the scheduling willl certainly will require review when the time comes.
PM Profiles in APM Help