ra:phm
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ra:phm [2018/09/04 12:04] koubel |
ra:phm [2018/10/05 18:49] (current) koubel |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| * Fuel stations - can have more AVPs | * Fuel stations - can have more AVPs | ||
| - | Data flow: | + | ====== Data and relations ====== |
| - | * 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 | + | * FuelStation - important is FSCode |
| - | are deleted, these are again recalculated via ''PHMTransaction'' service. See [[https://protank.visualstudio.com/PD/_workitems/edit/14409|bug]] for more information. | + | * PHMIdentity - some identity for fueling, mosty by some RFID card, chip card etc. determines the car of vehicle or some external entity for fueling. Important is ChipNumber. |
| + | * PHMFuelStationIdentity - if some identity can fueling on fuel station. Important is also ValidFrom | ||
| + | * PHMAVP - which AVP is presented od some FuelStation. Important is ID_FUELSTATION | ||
| + | Identity makes the transactions - PhmTransaction table. Important are | ||
| + | * StandNumber - FuelStation.FSCode | ||
| + | * IdentityDriver, IdentityVehicle - identity which made transaction - PhmIdentity.ChipNumber | ||
| + | * ID_AVP - AVP which was used for transaction PHMAVP.ID_AVP | ||
| + | * TransactionStart - when the transaction was made | ||
| - | Processing in ''TransactionManager'' | ||
| - | * reads amount of transaction from ''PHMTransaction'' process these amount in loop | + | ====== Data Flow, Processing ====== |
| - | * process vehicles, drivers | + | |
| - | * process nozzles from transaction: save record from transactions into ''PHMNozzleHistory'' table | + | |
| + | Synchronization: fuel stations, vehicles, chip numbers, fuel station FSCodes. | ||
| - | Synchronization: | + | 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. Same for Drivers with ''PHMIdentityDriverView''. |
| + | |||
| + | Transaction processing: | ||
| + | |||
| + | * Filling transaction - fill ''PHMTransaction'' table mostly from GSI software (our software) via KupsonManager. Some times from excel etc. | ||
| + | * These transactions are then processed via ''TransactionManager'' into transaction data store - ''PHMTransactionDataStore'' table. This is done via service thread ''PHMTransaction''. | ||
| + | * Web application show data from table ''PHMTransactionDataStore''. | ||
| + | |||
| + | When some data from PHMTransactionDataStore are deleted, these can be again recalculated via ''PHMTransaction'' service with TransactionManager. See [[https://protank.visualstudio.com/PD/_workitems/edit/14409|bug]] for more information. | ||
| + | |||
| + | Filling transactions | ||
| On some customers with AVPs, method ''KupsonManager.SynchronizeAllDevices'' - there is both direction synchronization: | On some customers with AVPs, method ''KupsonManager.SynchronizeAllDevices'' - there is both direction synchronization: | ||
| Line 33: | Line 44: | ||
| Time intervals for synchronizations are newly defined in db - [[https://protank.visualstudio.com/_git/PD/pullrequest/1409|PR]] | Time intervals for synchronizations are newly defined in db - [[https://protank.visualstudio.com/_git/PD/pullrequest/1409|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''. | + | Processing with ''TransactionManager'' |
| - | Vehicles: | + | * reads amount of transaction from ''PHMTransaction'' process these amount in loop |
| + | * process vehicles, drivers, identities | ||
| + | * process nozzles from transaction: save record from transactions into ''PHMNozzleHistory'' table | ||
| - | 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. | + | Process identities in ''TransactionManager'' |
| + | |||
| + | Identity with chip number must be determined if is for vehicle, driver or external identy. There are view | ||
| + | ''PHMIdentityVehicleView'', ''PHMIdentityDriverView'', ''PHMIdentityStandAloneView'' which are helpful for find | ||
| + | which is source of identity of the transaction. | ||
| + | |||
| + | 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''. | ||
ra/phm.1536055467.txt.gz · Last modified: 2018/09/04 12:04 by koubel
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
