My Oracle Support Banner

Automated Vehicle Location (AVL) Vehicles Intermittently Appear at Wrong Locations (Doc ID 2933529.1)

Last updated on MARCH 03, 2025

Applies to:

Oracle Network Management for Utilities - DMS - Version 2.5.0.1.0 to 2.6.0.0.0 [Release 2.5 to 2.6]
Oracle Utilities Network Management System - Version 2.5.0.1.0 to 2.6.0.0.0 [Release 2.5 to 2.6]
Information in this document applies to any platform.

Symptoms

On : 2.5.0.1.0 version, NMS Infrastructure

ACTUAL BEHAVIOR
---------------
AVL vehicles showing up in wrong location at times

There have been instances where AVL vehicles are showing up in wrong location at times on the NMS viewer.  Operators are noticing strange behavior where they will jump from correct location to incorrect location when our AVL gateway processes an update through MultiSpeak. They have verified that the coordinates being passed through on AVL vehicles are correct in the source database table for AVL gateway to pick up.

AVL Crews should always appear at the correct locations

The issue can be reproduced at will with the following steps:

Submit an update for multiple crews to MultiSpeak AVL adapter where some crews are unknown to NMS.

Example,

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ver="http://www.multispeak.org/Version_4.1_Release" xmlns:cpsm="cpsm">
   <soapenv:Header>
      <ver:MultiSpeakMsgHeader UserID="nms1" Pwd="systems"/>
   </soapenv:Header>
   <soapenv:Body>
      <ver:AVLChangedNotification>
         <ver:events>
            <ver:AVLLog>
               <ver:AVLID>Mobile Crew 0</ver:AVLID>
               <ver:AVLStateList>
                  <ver:AVLState>
                     <ver:GMTTime>2023-03-07T02:07:52.454-06:00</ver:GMTTime>

                     <ver:GPS> <!-- T10808 -->
                        <ver:latitude>40.9771</ver:latitude>
                        <ver:longitude>-81.39763</ver:longitude>
                     </ver:GPS>
                     <ver:telemetry>
                        <ver:speed units="mph">53</ver:speed>
                        <ver:heading>120</ver:heading>
                     </ver:telemetry>
                  </ver:AVLState>
               </ver:AVLStateList>
            </ver:AVLLog>
            <ver:AVLLog>
               <ver:AVLID>Mobile Crew 3</ver:AVLID>
               <ver:AVLStateList>
                  <ver:AVLState>
                     <ver:GMTTime>2023-03-07T02:07:52.454-06:00</ver:GMTTime>

                     <ver:GPS> <!-- F1115 -->
                        <ver:latitude>40.97968</ver:latitude>
                        <ver:longitude>-81.40192</ver:longitude>
                     </ver:GPS>
                     <ver:telemetry>
                        <ver:speed units="mph">63</ver:speed>
                        <ver:heading>240</ver:heading>
                     </ver:telemetry>
                  </ver:AVLState>
               </ver:AVLStateList>
            </ver:AVLLog>
         </ver:events>
      </ver:AVLChangedNotification>
   </soapenv:Body>
</soapenv:Envelope>

Expected result: crews that are known to NMS are displayed in the
                 Viewer at the positions specified in the message.
                 In the above example crew 'Mobile Crew 3' should be
                 displayed next to device F1115.

 

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
 Fix Description
 Migration
References


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