PHM module is responsible mostly for car fueling, petrol stations and related things.

Common terms:

• AVP - device for refueling (diesel, oil …). There are two types of AVPs - old one AVP31, new one AVPs - AVP41
• Fuel stations - can have more AVPs

Data flow:

• Synchronization - fuel stations, vehicles.
• Mostly synchronization writes into PHMTransaction table.
• Import is from many places e.g. KupsonView etc.
• These transactions are then processed via TransactionManager into transaction data store - PHMTransactionDataStore table. This is done via service thread PHMTransaction.

Most of data on web application are from table PHMTransactionDataStore. When some data from this one are deleted, these are again recalculated via PHMTransaction service. See bug for more information.

Processing in TransactionManager

• reads amount of transaction from PHMTransaction process these amount in loop
• process vehicles, drivers
• process nozzles from transaction: save record from transactions into PHMNozzleHistory table

Synchronization:

On some customers with AVPs, method KupsonManager.SynchronizeAllDevices - there is both direction synchronization:

• information about AVP devices into our db - PHMTransaction
• information back to AVPs - mostly chip numbers, cards.

Time intervals for synchronizations are newly defined in db - PR

Photos:

Transactions has photos made by some cameras on fuel stations. These photos are synced via rsync to APL_Service server (name in Terminals) in shared directory \\192.168.148.15\avp\AGROFERT\201801\overphoto\cam_R691_8.jpg. These are then synced with some service into db - table PHMTransactionPhoto.

Vehicles:

Vehicles are synchronized mostly from customers external data e.g. SAP for SD customer into some tables. Best usage for search vehicles is view PHMIdentityVehicleView. Column IdentityTextValue is value external customer car identifier for PHM.