GENERAL SYSTEM FUNCTIONS
| System version | B A S I C
|
S T A N D A R D
|
O P T I M U M |
P R O F E S S I O N A L |
E N T E R P R I S E |
| Keeping of warehouse stocks tanks (handling of low level alarms and level of pump blockage) |  |
|
|
|
|
| Recipient and vehicle limit (total) | 150 | none | |||
| Operator limit | none | ||||
| Operation within one company | |
|
|
|
 |
| Operation within many companies (version for wholesalers or companies with independent branches) | |
|
|
|
|
| Possibility of assigning many companies to one tank + module of accumulating liquid for companies | |
|
|
|
|
| Double identification (vehicle AND recipient) chosen generally for the whole company |
|
|
|
|
|
| Single identification (vehicle OR recipient) chosen generally for the whole company |
|
|
|
|
|
| Single identification + entering the second information on the keyboard during authorization chosen generally for the whole company |
|
|
|
|
|
| Possibility of individual authorization method settings for specific vehicles/recipients (sposoby: pojedyncza/ podwójna/ pojedyncza+nazwa) |
|
|
|
|
|
| It is possible to require entering the vehicle odometer value during authorization | |
|
|
|
|
| Function of checking the continuity of the vehicle’s odometer (the system will not allow to enter a lower value of the odometer reading than at the previous refueling) | |
|
|
|
|
| The function of controlling the maximum increase in the odometer status (the system will not allow to enter the value of the odometer reading with an increase greater than that specified for the vehicle) | |
|
|
|
|
| Possibility of individual required settings and meter reading for specific vehicles | |
|
|
|
|
| Liquid dispensing limits for individual recipients and vehicles (you can choose one of: daily, weekly, monthly) | |
1) |
|
|
|
| Liquid dispensing limits for individual recipients and vehicles (any configuration of many limits among: non renewable, daily, weekly, monthly, annual) | |
|
|
|
+ company |
| Data exchange between controllers on the use of limits | |
1) |
|
|
|
| Vehicle fuel tank capacity limit (for one-time refueling) | |
|
|
|
|
| Possibility to assign several dispenser controllers to one tank | |
|
|
|
|
| Analysis of average consumption – l / 100 km | |
|
|
|
|
| Analysis of average consumption – l / 1 h | |
|
|
|
|
| Parameterization of selected “Full” refueling for consumption analysis + module for automatic detection of additional refueling | |
|
|
|
|
| The ability to hide the amount of refilled liquid for individual recipients | |
|
|
|
|
| The ability to hide the amount of refilled liquid for individual vehicles | |
|
|
|
|
| Possibility of cooperation with the system for measuring the actual amount of liquid in the tank and detection of inter-shell space (SKP) | |
|
|
|
|
| Possibility of temperature compensation of the Diesel fuel dispensed up to 15°C (temperature probe mounted in the distribution system)2) | |
|
 |
|
|
| Possibility of system migration to higher versions | |
|
|
|
not applicable |
| Operation in different languages (Polish, English, German, Russian, Lithuanian, Czech) | |
|
|
|
|
1) Limits supported only by online communication.
2) Only when operating the distribution point via the internal KDP driver extension – not possible with MDP extensions.
PC SOFTWARE
| Program version | B A S I C
|
S T A N D A R D
|
O P T I M U M |
P R O F E S S I O N A L |
E N T E R P R I S E |
| REQUIREMENTS | |||||
| Software working environment | Windows (XP, VISTA, 7, 8, 10, Serwer 2008, Serwer 2012, Serwer 2016) – 32-bit and 64-bit versions | ||||
| Application Type | Virtual WWW server + MySQL database (unlimited number of end stations) | ||||
| Recommended browser to operate the program | Google Chrome or Mozilla Firefox | ||||
| Internet connection required | only for the needs of GPRS communication, recommended for program activation | ||||
| RAM memory | Minimum 2GB, Recomended 4GB | ||||
| Disk space (depends on the number of supported controllers and the number of operations) | 1,5GB-5GB | 2,5GB-10GB | |||
| FUNCTIONS | |||||
| Logging into the program using a login and password | |
|
|
|
|
| Logging into the program using an electronic identifier | |
|
|
|
|
| A clear way to show liquid levels in all tanks | |
|
|
|
|
| Presentation of tanks on a map | |
|
|
|
|
| Configuring company and device settings | |
|
|
|
|
| Module for creating standard reports according to your needs (unlimited possibilities of customizing the report) | |
|
|
|
|
| Analytical and graphical module for creating reports extended by calculating the distance and average liquid consumption per workhour | |
|
|
|
|
| Creating and saving individual report templates for each operator | |
|
|
|
|
| Export of reports to spreadsheet and PDF | |
|
|
|
|
| EIID variables for integration with external programs | |
|
|
|
|
| Adding recipients / vehicles / operators by yourself | |
|
|
|
|
| Possibility of assigning recipients and vehicles to freely defined groups | |
|
|
|
|
| Selection of recipients/vehicles for which an additional transaction description must be entered before refueling | |
|
|
|
|
| Independent adding of system operators with specific access levels (to choose from: serviceman, administrator, operator, report, supplier) | |
|
|
|
|
| Independent adding of system operators with the function of selecting specific, freely selected from the list of permissions to perform operations in the system | |
|
|
|
|
| Assigning specific tanks to be viewed by operators | |
|
|
|
|
| Performing loading and correction of tank levels | |
|
|
|
|
| Adding external refueling | |
|
|
|
|
| MANUAL REFUELING function | |
|
|
|
|
| EMERGENCY REFUELING function | |
|
|
|
|
| Remote controller software update (only for CAN, LAN, Wi-Fi, GPRS connections) | |
|
|
|
|
| One-time / scheduled backup module | |
|
|
|
|
DISPENSER CONTROLLERS
| KDP100 controller version | B A S I C
|
S T A N D A R D
|
O P T I M U M |
P R O F E S S I O N A L |
E N T E R P R I S E |
| B/BG | S/SG | O/OG/OF/OGF | P/PG/PF/PGF | E/EG/EF/EGF | |
| Built-in GSM modem |  |
|
 |
|
|
| Built-in module for measuring the real amount of liquid and inter-shell tank detection |  |
|
 |
|
|
| Number of dispensing points supported by the controller | 1 | 1 | 1 | 1 | 1 |
| Possibility of extending the number of supported media by the controller (by using MDP220 and MDP250 expansion modules) | |
|
 |
 |
|
| Possibility to connect the module for automatic switching of tanks forming a battery | |
|
|
|
|
| Limit of controllers working under one license | 3 | 3 | 5 | none | none |
| SPECIFICATION | |||||
| Power supply | 230V/50Hz | ||||
| Power supply (optional) | |
15V DC | |||
| Number of displays | 1 | 2 | |||
| Dimensions (H x W x D [cm])) | 20 x 15 x 9 | 25,5 x 18 x 10 | |||
| Degree of housing protection | IP65 | ||||
| Operating temperature range | -30°C ÷ 50°C | ||||
| CONTROLLER COMMUNICATION WITH THE SERVER | |||||
| Bidirectional data transfer with identifiers COD200 with memory |  |
|
|
|
|
| CAN connection (via MIK200) | |
|
|
|
|
| LAN connetion (via NetBox) | |
|
|
|
|
| Wi-Fi connection (via NetBox and Access Point Client) | |
|
|
|
|
| ONLINE GPRS transmission | |
|
|
|
|
| AUTHORIZATION METHODS | |||||
| COD100 contactless card support | |
|
|
|
|
| COD110 and COD200 identifiers support | |
|
|
|
|
| COD112 (Mifare) identifiers support | |
|
(instead of COD100/COD110/COD200) |
||
| Login using PIN codes | |
|
|
|
|
| Possibility to require confirmation of the authorization by an identifier with a PIN code | |
|
|
|
|
| DATA SAFETY | |||||
| Event record in the event of a power outage | |
|
|
|
|
| Saving the entire controller history on the SD card (encrypted data) | |
|
|
|
|
| ADDITIONAL FUNCTIONS | |||||
| Calibration by a change of a factor | |
|
|
|
|
| Measurement calibration (according to reference vessel) | |
|
|
|
|
| Remote calibration factor change from the program | |
|
|
|
|
| Question about entering the amount for refueling before refueling (it is possible to program any value or, if you want to refuel to the full, just press ENTER without entering the value) | |
|
|
|
|
| Option to disable the question about the amount to be refueled for the entire company | |
|
|
|
|
| Option to turn off the enquiry about the amount to be refueled for specific recipients and vehicles | |
|
|
|
|
| Controller work in loading mode | |
|
|
|
|
| Quick preview of the last refueling after pressing ↑ (refueling status with invisible quantity is not displayed) | |
|
|
|
|
| Manual software update in the controller (by uploading the update file to the controller SD card) | |
|
|
|
|
Legenda: 
(available) , (optionally available), 
(unavailable)