My Oracle Support Banner

Stormman / JMService Ignores a Crew's First Available Shift If it Has a Future Start Time (Doc ID 2578899.1)

Last updated on AUGUST 20, 2019

Applies to:

Oracle Utilities Network Management System - Version 2.3.0.2.0 to 2.4.0.0.0 [Release 2.3 to 2.4]
Oracle Network Management for Utilities - DMS - Version 2.3.0.2.0 to 2.4.0.0.0 [Release 2.3 to 2.4]
Information in this document applies to any platform.

Symptoms

On : 2.3.0.2.0 version, Storm Management

JMService / StormMan is not considering a crew in the current day if its start time is after the server time.


When the crew start time in the storm management crew information section is 5th July 5:00 and if it is after the server time 5th July (4:57)
 Here, while running the simulation there are no crews available so it should take crew start time, but it should calculate from 5th July rather than 6th July.
Why it is calculating from 6th even though the crew is available from 5th?
PFA for screenshots and more info

If a crew's shift starts after the beginning of a storm, Stormman should still use it on the current day.


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.