Tima version: 2022-3



LHS version: 5.0


DeltaTima version:


GeometryServer version:


FMS type:


Client: 



NOTE: The following image was modified to simulate the situation!:


Diagnosis and Solution: Depending on the KPI you want to review, you should check KPI table values, cycles, equipments states and/or GPS from the FMS database to discard to be just an operational issue and then focus the problem to the connector. 

This may occur because KPI connector is not processing the data to retrieve it temporarily serialized. Synker needs to receive every KPI temporarily ordered, taking from the first value (oldest) to the final value (current time). 


For example, if you are retrieving the data directly from a query, it should be similar to this (ordering the time attributes ascending):


In other cases, for example, the use of a dataframe, dictionary, tuple or list to store the data, the procedure is similar. It is required to give the queried data sorted ascending by its time atribute.