Home

GIR Titan-Hyperion User manual

1. Level Access 1 2 3 Consultation Reading Writing Standard Reading Wrting Yes Workshop Reading Writing Yes Yes Local manager Reading Writing Yes Yes Yes summary of the access rights for each user is available in the user sheet Summary tab 1 8 2 Advanced mode Each user is assigned one of the following access levels e Installer Full access to the application Only one installer account can be defined The installer mode application connection is protected by dongle e Manager Full access to the application except for hardware configuration which is only available for reading e Standard Restricted access to the application according to the autho rizations specified in the Authorizations tab e Inherited Identical to the Standard level with the additionnal possibil ity to specify an authorization profile at login time when using intranet integration A standard account can allow from a limited consultation to authorizations close to those of a manager Authorizations are defined by specifying explicitely which operations are allowed to a user on sites and departments Departments can be merged into directions and sites can be merged into regions See 1 9 page 34 Authorizations on sites and regions The operations allowed are e Consultation Access to the consultation states history sums for transactio
2. 0215 55599 GIR Titan Hyperion User manual www gir fr en infoOgir fr Version 1 4 1b july 2007 Copyright C 2004 2007 klervi All rights reserved Any reproduction or translation of part or totality of this manual is forbidden without any prior written authorization from klervi The contents of this document are given for information only Klervi is in no way liable for any mistake that could have slipped into the text Contents I Instructions for use 11 1 Data entry 13 ll Vehicles pU 13 1 1 1 General information 13 L13 Identification eR RR e an io ee ed 13 1 1 3 Entry of a GIR proximity badge 14 Teles M te Si a eere oe eS es he odia 15 1 1 5 OPTIONS 3 2 nnd uuo NIE De 15 ELG MeSsages 22 Acie ts ded de a Tet RU S de efe ae 17 1 1 7 17 1 1 8 Tanks 2a eld PR ey a Se 18 ELO Other informiation 3 ox xaxd Ra RS 19 1 1 10 Scrapping a 19 1 1 11 Short term 1 20 L2 Drnwenuseage4 ARR a 21 1 2 1 General information 21 E2 2 Identification ovorum LL nos cho Ud 21 12 3 Options Roda o eR Eos 21 1 24 Messages UTR Re 22 1 2 5 Authorization x3 f
3. Identification Without the C Sc option With the C Sc option Badge Yes Yes Code Yes 8 characters Yes 6 characters Badge Secret code Yes Code field Yes Secret code field Code Secret code No Yes Secret code field 1 1 6 Messages Only one message can appear on the terminal for each vehicle If a vehicle has several messages the one with top priority will appear following this priority 1 Maintenance message 2 Message attached to the vehicle Message field 3 Message attached to the vehicle s department only if the vehicle is au thorized on the CPU The attachment of a message to a vehicle is done by clicking on Modif in the vehicle sheet General tab 1 1 7 Authorization In addition to the Forbidden option two criteria determine a vehicle access rights Zone defines the zones in which the vehicle is authorized See 1 6 page 25 Expiry allows to define a time limited authorization if a vehicle s expiry is set to 31 12 2004 it won t be able to use the CPU from January 1 2005 at midnight The vehicle sheet General tab allows to quickly visualize the access rights Green square The vehicle is authorized summary of the authorized zones and sets is displayed Red square The vehicle is forbidden and the reason is displayed A vehicle may be forbidden for the following reasons e Forbidden the Forbidden option is enabled 18 CHAPTER 1 DATA ENTRY e Expired the de
4. A fueling is made on the CPU B for the vehicle V and the meter entered is 50800 mi The situation is now the following GIR Titan Hyperion CPU CPU Vehicle V 50000 mi Vehicle V 50800 mi Vehicle V 50000 mi 61 62 CHAPTER 3 CPU COMMUNICATION If the vehicle V later comes to the B2 CPU with a meter of 51500 mi and that no dialogue was made to synchronise data the new meter will be refused Indeed on the Bz CPU the last known meter for this vehicle is still 50000 mi Given the defined range the maximum meter value is 51000 mi If a dialogue occurs between the two fuelings of the vehicle V the situation would be the following GIR Titan Hyperion CPU CPU Vehicle V 50800 mi Vehicle V 50800 mi Vehicle V 50800 mi new 51500 milometer would then be accepted on both CPUs avoid such issues it is recommended to regularly synchronize data so that there is always at least one synchronization between two fuelings of the same vehicle The best solution is to define an automatic dialogue See 1 7 page 28 Generally scheduling a dialogue once every 24 hours is sufficient this should be adapted if the same vehicle is likely to make several fuelings per day 3 2 Manual dialogue The gt CPU comm menu allows to launch a communication between GIR Titan Hyperion and one or several CPUs To start a dialogue click on Launch after selecting the
5. If several pumps are defined Mo 11 10 04 10 30 00 SEL PUMP 1 2 Press 0 The identification of the vehicle or driver depending on the configuration accessing the attendant menu is then asked Mo 11 10 04 10 30 00 of Mo 11 10 04 10 30 00 ID VEHICLE ID DRIVER 2 5 ATTENDANT MENU TIP1 PABBAY CPUS 53 A vehicle or driver is authorized to accesss the attendant menu when the option Attendant menu is enabled See 1 1 5 page 15 and 1 2 3 page 21 Oth erwise the MENU ACCESS DENIED message appears The attendant menu content depends on the CPU type 2 5 Attendant menu TIP1 Pabbay CPUs The attendant menu on TIP1 Pabbay CPUs appears as follows Tanks Pumps Clock Gauges Instal badGes submenu is accessed by pressing the corresponding number Tanks key 1 Consultation of tank s theoretical stocks entry of supplies Pumps key 2 Consultation of totalizers pump blocking or unblocking Clock key 3 Modification of the CPU date and time Gauges key 4 Consultation of gauging information Instal key 5 N A Badges key 6 Proximity badges initialization 2 5 1 Tanks submenu C1 GOI 1500 g Supply Upd First line e Tank number from 1 to 16 Use the or 9 and or 7 keys to go from one tank to another e Product name e Tank theoretical stock Second line e Supply key 1 Tank supply entry e Upd key 2 Tank stock upda
6. GI Entry dormi b eese yes bb doses e 1 1 3 Fuel suction 00 666 A RV SU 7 1 4 Remote transaction Tanksupply entry owe E XR GA ad Gee X 7 21 New unit price computing 7 2 2 Tank supply cancellation 7 2 3 Transactions Fuel transaction modification 8 Access management 8 1 8 2 DUPERVISIONY E LR E eo ae a Ee 8 1 1 Punctual and forced control 0 0 8 1 2 Supervision screen DUALS eta KP a ee ei nes Bae 9 Maintenances 9 1 9 2 9 3 9 4 Maintenance definition 000 00 000 2 ee QEL Examples 44 be A ere eS EE EGS ee ER Y RH Maintenance entry Estimation of maintenances todo 2 Maintenance recomputing 73 73 73 74 76 77 77 78 78 79 80 80 81 82 82 82 83 83 84 84 85 85 87 87 87 87 88 88 89 89 90 90 91 93 93 93 93 94 6 CONTENTS 10 Credits 101 OVERVIEW ER ee A asas 101 10 2 Cr dit periods icr m be Se ee 1A 102 10 3 Monetary credits 102 J0 8 T Unit price 4 549 EUIS tree Rae EE 103 10 3 2 Credits history wa ati aede a PAA 103 10 4 Examples e s 4028 a Ret READER ES 104 10 5 Credits recomputing
7. 104 11 Invoicing 107 11 1 Configuration 5 2 nage Xem wwe Y e 107 11 1 1 General parameters 107 T1 1 2 Products 2 ua doh aed RP Dh SEEDER EES 108 11 1 3 Customers and providers 108 11 2 Invoices generation 108 WA Del FOr csc oh etn RA ate A oP IES 109 11 2 2 Result aeu IRURE ce 2 8 Gos Pees 109 12 Data import and export 111 12 1 Oil disks import 646 39 TRE 111 12 1 Configuration o RR Sex aa 111 12 1 2 Products resolution 112 12 1 3 Vehicles and drivers resolution 112 12 1 4 Manualimport lees 113 12 1 5 Automatic import 114 12 1 6 114 12 2 Trachent exports 122258 GEA AAA UELLE Rm Ron ime pne s 114 12 32 TranscodiBgso a odo o b dn rco ee ER e 115 13 Exceptional operations 117 1321 Purge oy uva we eee uis a iu RE 117 13 2 Table update amp BO AA Rem RR Remo om roe 117 19 2 T Examples 2 2 AIR PRU Seda 118 A Licence agreement 121 B Traclient files format 125 C Text e mails format 141 C 1 Alert messages 142 42 Report messages o vx err et 142 D CPU CSV file format 143 DL Fuel transactions 2 icm RR Gees bohoh ne eue Ee e a 144 D 2 Ev nements carburant 145
8. method p Pa Va Pe Ve Va Ve with P supply unit price Va supply volume 90 CHAPTER 7 OPERATIONS ENTRY P tank stock unit price V tank stock at the supply date V is computed by adding to the current stock the volume of the transac tions realized between the supply date and the current date The result of this calculation may be viewed in the Previous tanks state page For this computing to be valid all the transactions carried out before the supply must have been retrieved in GIR Titan Hyperion 7 2 2 Tank supply cancellation To cancel a supply click on Cancel in the supply sheet Only the last supply of each tank can be cancelled 7 2 3 Transactions valuation When a fuel transaction is retrieved from a CPU by GIR Titan Hyperion it is valuated with the tank stock unit price at the time of the processing Hence to correctly valuate all transactions it is important to keep a correct chronology when entering tank supplies When entering a supply all the transactions occuring before this supply must have been retrieved If not the stock used to compute the new unit price is wrong and this price is wrong too correct transaction valuation requires to conform to those two rules e Do a Retr Send dialogue before entering a supply e Enter a supply just after it has been made ie before retrieving any transaction realized after If the second rule is not respected and that transactions made
9. 1 GOI 1500 g T 14 H20 1300D 2 6 ATTENDANT MENU TIP2 VATERSAY CPUS 55 First line e Tank number from 1 to 16 Use the or 9 and or 7 keys to go from one tank to another e Product name e Tank stock measured by gauging Second line e T temperature in Celsius degrees e H20 water volume e D gauging status 0 indicates a correct gauging or any other value indicates a gauging error 2 5 4 Badges submenu The following procedure assigns a proximity badge to a vehicle or driver 1 Vehicle Enter the vehicle code U or 2 allows to initialize a driver badge V or 1 returns to a vehicle badge 2 Badge initialization Present your badge The possible messages are e BADGE PROGRAMMED The badge of this vehicle has already been ini tialized e INEXISTENT CODE The code entered does not correspond to any ve hicle e BADGE ALR ASSIGNED The badge has already been assigned to an other vehicle e BADGE ACCEPTED The badge has been correctly initialized It is then possible to enter a new vehicle code to intialize another badge 2 6 Attendant menu TIP2 Vatersay CPUs The attendant menu on TIP2 Vatersay CPUs appears as follows 1 PUMPS 2 TANKS 4 T BADGE 5 I BADGE 3 MODE 8 6 TICKET gi submenu is accessed by pressing the corresponding number Depending on the configuration some elements might not be available Pumps key 1 Consultation of totalizer
10. Spec code READY FOR DELIVERY E 2 FIRST ID DRIVER E 2 First id driver UNKNOWN BADGE UNKNOWN CODE i NO VEHICLE f UNKNOWN BADGE UNKNOWN CODE ive XR ACTU ree 2 i INVALID CODE RICE EN ID DRIVER lt poen PIN CODE SEL PUMP 123 PUMP 1 DIESEL Validate your choice PIN code N Vehicle id DRIVER CODE ne Y necs mtt ID VEHICLE PIN code VEHICLE CODE Odometer 7 N Y Y READY FOR DELIVERY 149
11. 07 Badge type 08 Badge number 09 Badge code 10 Code 11 Secret code 12 Transaction type T internal external 13 Product ref 14 Transactions count 15 Volume cL 16 Total price cents 17 Total covered distance km 18 Distance consumption volume cL 19 Last odometer km 20 Total covered hours 1 100 h 21 Hour consumption volume cL 22 Last hour meter 1 100 h 23 32 10 Unused reserved for future use See the M1 format for more information on the file content 136 APPENDIX B TRACLIENT FILES FORMAT W1 version Access transactions Position Length Description 000 018 19 Date format dd mm yyyy hh nn ss 019 038 20 Vehicle ref 039 068 30 Registration 069 088 20 Vehicle type ref 089 108 20 Vehicle direction ref 109 128 20 Vehicle department ref 129 148 20 Driver ref 149 178 30 Driver name 179 198 20 Driver direction ref 199 218 20 Driver department ref 219 219 01 Access result see X1 format 220 239 20 Site ref 240 259 20 CPU ref 260 279 20 Access set ref 280 299 20 Access type ref 300 315 16 Options see the options field of the X1 format 137 X1 version Access transactions Position Description 01 Date format dd mm yyyyhh nn ss 02 Vehicle ref 03 Registration 04 Vehicle type ref 05 Vehicle type name 06 Vehicle direction ref 07 Vehicle direction name 08 Vehicle department ref 09 Vehicle department name 10 Driver ref
12. E a Bookmarks A Location http Localhost 8080 cgi bin twcgibin p 474T amp sid 10606223418 cnd Printable version GUR DT Maintenancesito do CSV file V1 V2 yperion Lr ceci appscnd ntn todo amp View amp page J amp date 05 20 2005 amp r Prediction valuation To do before 05 20 2005 Reference period 06 01 2004 06 30 2004 State Alert Blocking Modify D01 Internal fleet VSC Commercial vehicles Date Meter mi Fre Current Alert fre Current Alert Freq Current Alert State 9 Predi d Blocking 4 Predicted Blocking months Predicted Blocking 0 00 47521 47 400 Meter h Vehicle Maintenance i 07 28 2004 2248XRE3 Drain 15000 47 521 48 900 8 Alert 87 250 0 00 07 28 2004 07 25 2004 52631892 TC 2400 05 20 2005 09 24 2004 Ml Blocking 0 00 104 176 07 28 2004 09 20 2004 9738 5 TC 2400 05 20 2005 11 20 2004 Wi Blocking E 9 4 Maintenance recomputing Recomputing a maintenance means determinating its new state using the new meters of a vehicle or the elapsed time for maintenances based on a date Therefore if a maintenance reaches its alert limit on 18 05 2005 it will only be in an Alert state after the first recomputing made after 18 05 2005 at midnight Maintenances are recomputed e For each vehicle or driver each time a fuel transaction is processed for this element 100 CHAPTER 9
13. Fuel Access Fuel sums Defines the format of daily traclient files Leave to N A to generate no traclient file 40 CHAPTER 1 DATA ENTRY Monthly traclient export Generation day Defines the day in the month when exports should be gen erated e g if this field is set to 10 the sum concerning March 2005 will be generated on April 10th This allows to leave a small time range to regularize transactions Fuel options Same meaning as for live export Fuel Access Fuel sums Defines the format of monthly traclient files Leave to N A to generate no traclient file Traclient options These options affect all traclient exports Vehicle name Defines the field to use as registration number for vehicles in all traclient formats Traclient delimiter Compatibility setting for F1 ref and F2 ref formats Options e Trans num unchanged on modif Don t increment the transaction number on modification e Trans num per CPU Generates a per CPU transaction number instead of a global one e Live export per CPU Generates a live traclient file for each CPU in addition to the main file 1 9 7 Invoices This section defines general invoicing configuration See 11 page 107 Geometric coordinates Those numerical values allow to configure the header of generated invoices by defining the header total height and the coordi nates of the rectangles containing customer and provider addresses Traclient format Defines th
14. The attendant is a particular vehicle or driver who is allowed to enter transac tions for other vehicles or drivers It allows to Vehicle attendant e identify a vehicle without its badge e force the fueling for a forbidden vehicle e force a meter value Driver attendant e identify a driver without its badge e force the fueling for a forbidden driver The identification process for an attendant is the same as for a normal vehicle or driver See 2 2 2 page 49 Once the attendant is identified the code of the vehicle or driver to which the transaction must be assigned is asked 52 CHAPTER 2 CPU USAGE Pump 1 GOI ae Pump 1 GOI CODE VEHIC CODE DRIVER Enter the code and validate with VAL The transaction continues as if the vehicle or driver was normally identified with two additional possibilities e If the vehicle or driver is forbidden it is still possible to make the trans action VEHICULE FORBIDDEN dn DRIVER FORBIDDEN OVERRIDE OVERRIDE Validate with VAL to bypass the ban e If a range control encounters an incorrect meter value it is possible to force the value Pump 1 GOI ae Pump i GOI force Mi to force H to Validate with VAL to force the meter 2 4 Attendant menu access To access the attendant menu press the 0 key when the CPU is idle If only one pump is defined Mo 11 10 04 10 30 00 ID VEHICLE Press 0 then VAL
15. 1 Identification B badge C code initialization P code via attendant 102 111 10 Badge type 112 121 10 Badge number 122 131 10 Badge code 132 141 10 Code 142 151 10 Secret code 152 152 1 Transaction type T internal E external 153 172 20 Product ref 173 180 8 Transactions count 181 196 16 Volume cL 197 212 16 Total price cents 213 222 10 Total covered distance km 223 238 16 Distance consumption volume cL 239 248 10 Last odometer km 249 258 10 Total covered hours 1 100 h 259 274 16 Hour consumption volume cL 275 285 10 Last hour meter 1 100 h 286 385 100 Unused reserved for future use The file contains vehicles then drivers sorted alphabetically For each vehicle there is at least one line per product authorized to the vehicle Each product can potentially have two lines when external transactions have been made Thus a vehicle authorized on products GOT and FUE that has made internal fuelings on both products as well as an external GOI fueling will be on 3 lines in this file For each driver this file contains at least one line per product defined in the software 135 N1 version Position Description 01 Type V vehicle U driver 02 Registration vehicles only 03 Name drivers only 04 First name drivers only 05 Ref 06 Identification B badge C code initialization P code via attendant
16. 11 Driver name 12 Driver first name 13 Driver direction ref 14 Driver direction name 15 Driver department ref 16 Driver department name 17 Access result 1 ascii character A authorized R denied Z denied zone 18 Site ref 19 Site name 20 CPU ref 21 CPU name 22 Access set ref 23 Access set name 24 Access type ref 25 Access type name 26 Options 16 characters string where each character is space when the option is not set or the character below when it is set 1 G remote transaction 2 to 16 unused 138 APPENDIX B TRACLIENT FILES FORMAT Version W2 Transactions acc s Position Length Description 000 018 19 Date format dd mm yyyy hh nn ss 019 038 20 Vehicle ref 039 068 30 Registration 069 088 20 Vehicle type ref 089 108 20 Vehicle direction ref 109 128 20 Vehicle department ref 129 148 20 Driver ref 149 178 30 Driver name 179 198 20 Driver direction ref 199 218 20 Driver department ref 219 219 01 Access result see X2 format 220 239 20 Site ref 240 259 20 CPU ref 260 279 20 Access set ref 280 299 20 Access type ref 300 315 16 Options see the options field of the X2 format 316 324 09 Transaction number 325 424 100 Unused reserved for future use 139 Version X2 Transactions acc s Position Description 01 Date format dd mm yyyyhh nn ss 02 Vehicle ref 03 Registration 04 Vehicle type re
17. 2 2 4 Additional entries s 50 2 215 Delivery so oo 4 OI dd 50 2 3 Attendant s cece Y y Rey 51 2 4 Attendant menu 52 2 5 Attendant menu TIP1 Pabbay CPUs 53 2 5 1 Tanks submenu 22e 53 2 5 2 Pumps submenu 54 2 5 3 Gauges submenu 54 2 5 4 Badges submenu 55 2 6 Attendant menu TIP2 Vatersay CPUs 55 2 6 1 Pumps submenu 56 2 6 2 Tanks submen scesk GAMA RR EEE SSS BAS a 56 2 6 3 57 2 6 4 Badge test submenu 57 2 6 5 Init 58 2 0 Tacho download o iv APR NH eg 58 2 9 ee ee AES e D D dod ewe els 59 2 8 1 uade eee Seeds 59 2 8 2 Ticket printing 4 23 4 00860 60 CPU communication 61 3 1 JPriBciplea s teo ERR EATER es RR moribus 61 2 1 1 Multiple CPUs 322 02 5 LATUR rr RENS 61 3 2 iManualdial gue A tete 62 3 9 ASUDpeLvislOlic de e gd ete S S av estas 63 3 3 1 Pump blocking 544 4 65 3 3 2 Remote transaction 65 3 4 Resolving 66 3 4 1 Modified module 66 3 4 2 Modified config a eer rm gon
18. 2 2 5 Delivery Once everything has been entered the delivery starts and the CPU displays READY FOR DELIVERY The fueling then depends on the pump configuration based on the following variables Tstart Beginning of the delivery time 2 8 ATTENDANT 51 Tena End of the delivery time Tafter Post delivery period Tstart and Tena are defined in the pump configuration and can be viewed in gt Tanks state by clicking on Detail for the selected pump Tafter is fixed to 2 seconds A fueling conforms to the following rules e If nothing is delivered for T sta seconds the delivery stops e Once a first output has occured if no other ouput is made for Teng seconds the delivery stops e Ifa hangup is managed the delivery stops when the pump nozzle is hanged up the two above time periods remain valid e Once the delivery has been stopped the volume output is still counted for Tafter Seconds This allows to take into account compressing phenomena in the delivery pipe Null volumes Two other values are defined in the pump configuration and may be consulted in the tanks state screen To mininum transaction length to count it as a null volume No number of consecutive null volumes before blocking the pump A fueling is considered as null when it doesn t carry out any debit and that its length is longer than When No unsucessful fuelings successively occur on the same pump it is automatically blocked 2 3 Attendant
19. 2 Invoices generation Management Invoices 11 2 INVOICES GENERATION 109 11 2 1 Form The invoices generation form contains the following fields e First screen Start num Invoice number When multiple invoices are generated this number is incresased for each new invoice Period Time range to invoice Customer Filter on a specific customer Provider Filter on a specific provider e Second screen for each product invoiced unit price settings Multiple choices are available depending on the configuration For each one an increase can be defined either with a percentage or with a fixed value Exact Uses the U P at which each transaction was valued as shown in the transactions history Average by cust Computes the average valued U P for each cus tomer on the selected period this will give the same U P to all the transactions on a given customer Global average Computes the average valued U P on the selected period same U P for all customers Weighted average Computes the average U P of all the supplies on the selected period weighted by the volume of each supply Max value Uses the maximum U P of all the supplies on the selected period Last purchase Uses the last supply U P for each provider Forced to Specifies entirely the U P value to use 11 2 2 Result Once all desired parameters have been entered in the form click on Next to display the result page It
20. Assignment operation 2 Select the department D1 in filter criterions 3 Select the field Department as the field to assign 4 Select the department D2 as assignment value e Define a meter range for all the vehicles of type Truck 1 Select the Vehicles table and the Assignment operation 2 Select the type Truck in filter criterions 3 Select the field Range km as the field to assign 4 Enter the new range value e Change the fuel credit of all hybrid cars i e that can use either Super or GPL 1 Select the Tanks table and the Assignment operation 13 2 TABLE UPDATE 119 2 Select the GPL product in vehicles filter criterions this will select all vehicles that can use GPL Select the Super product in tanks filter criterions This will select the tanks using Super among all the tanks of the vehicles previously selected 3 Select the nitial credit field as the field to assign 4 Enter the new credit value e Convert all drivers names to uppercase 1 Select the Drivers table and the String edition operation 2 Click on Next without selecting any filter criterion to modify all drivers 3 Select the Uppercase operation and validate 120 CHAPTER 13 EXCEPTIONAL OPERATIONS Appendix A Licence agreement End User License Agreement for Hyperion software IMPORTANT READ CAREFULLY This End User License Agreement the EULA constitutes a legal contract between you physical or moral
21. Blocking delta Alert delta Blocking delta lt gt lt gt A A Next Alert limit Blocking limit A maintenance state may be consulted via the Maintenances tab of the vehicle or driver sheet The various possible states are e Alert The maintenance has reached its alert limit e Blocking The maintenance has reached its blocking limit e Invalid The maintenance is invalid no alert or blocking limit has been defined e Waiting The maintenance is valid and has not reached any limit yet This is the most common maintenance state e Disabled The maintenance is disabled Alert blocking and invalid maintenances appear in red in the General tab 9 1 MAINTENANCE DEFINITION 97 9 1 1 Examples e On 01 09 2004 vehicle V meter is 54 000 mi and it has to be drained off every 10 000 mi Its last oil change was done on 01 06 2004 at 52 000 mi We would like to be warned 500 mi before the term but not to block the vehicle if the maintenance has not been made in time We would declare the following maintenance Next meter 62 000 Frequency mi 10 000 Alert delta mi 500 Blocking delta mi Empty Should we wish in addition to the mileage criteria that the oil change would be done at leat every year we would add the following parameters Next date 01 06 2005 Frequency month 12 Alert delta month 0 5 Blocking delta month 2 The Alert delta of 0 5 means th
22. Chapter 2 CPU usage 2 1 States When a CPU is not used for data entry it may display various messages ac cording to its state Mo 11 10 04 10 30 00 SEL PUMP 123 Mo 11 10 04 10 30 00 PUMP 2 AVAILABLE Mo 11 10 04 10 30 00 DELIVERY IN PROGRESS Mo 11 10 04 10 30 00 OUT OF ZONE Mo 11 10 04 10 30 00 OUT OF ORDER A detailed pump state can be viewed in GIR Titan Hyperion using the su pervision mode See 3 3 page 63 or on the CPU using the attendant menu See 2 4 page 52 Several pumps are available to re fuel Pumps for which numbers are not displayed are either in use or un available Only one pump is available The others are either in use or unavail able All available pumps are currently in use No pump is available according to the defined time slots No pump is available 47 48 2 2 Fueling Fueling steps on the CPU Pump choice Identification Entry of meters Entry of optional data Distribution CHAPTER 2 CPU USAGE The transaction may be cancelled by the EFF key at any time during data entry The TRANSACTION CANCELLED message appears and the CPU returns to the idle state The detailled scenario of a fueling is available in appendix to this document See E page 147 2 2 1 Pump selection Mo 11 10 04 10 30 00 PUMP 1 AVAILABLE
23. D 3 Transactions oo ca sla uu a iia a da 145 D 4 Ev nements 145 E Fueling scenario 147 First idy ek i te he Be ee RR Re RE oes 148 E 2 First id driver 149 Introduction Overview GIR Titan Hyperion is a fleet management software It covers fuel delivery assignment of vehicles to drivers vehicles maintenances access to the station or to buildings vehicles keys delivery 10 CONTENTS Part I Instructions for use Chapter 1 Data entry 1 1 Vehicles gt Vehicles 1 1 1 General information Num number automatically assigned to each vehicle by GIR Titan Hyperion This number is unique to each vehicle When a ticket is printed after fueling this number may be used to identify the vehicle See 2 8 page 59 Registration registration of the vehicle It is used to refer to a vehicle in the software and must be unique to each vehicle Ref Value used to refer to a vehicle in specific exports 1 1 2 Identification Fields Badge num Badge type Badge code Code Identification A vehicle may be identified on the CPU by three different ways e Identification by code Identification Code Badge num Optional Badge type N A Badge code Empty Filled e Identification by a GIR proximity badge Identif
24. Identification Fields Badge num Badge type Badge code Code Identification The definition of identification settings for a driver is the same as the one described for vehicles See 1 1 2 page 13 1 2 8 Options Options e Forbidden The driver cannot refuel e Secret code The entry of a secret code is required after the identi fication This code is defined in the Code field This option is not available if Code Secret code drivers is enabled in Installer config See 1 1 5 page 15 for more details about this option Options fuel e Id vehicle A vehicle identification is required after the driver iden tification e Attendant The driver is an attendant See 2 3 page 51 e Attendant menu The driver can access the attendant menu See 2 4 page 52 e Activity code An activity code is asked after the identification See 1 4 page 24 e Specific code specific code is asked after the identification See 1 5 page 25 e Auth on mutu When vehicles authorization by driver is enabled See 1 9 page 34 this option allows the driver to use mutualized vehicles e Inhib ext vehic When the Vehicle ext feature is enabled in the Manager config this option cancels it for this driver CPU lang Defines the language to use on the CPU after the driver has been identified TIP2 Vatersay only This field is only available if the corre sponding feature has been enabled in the Manager config 22 CHAPTE
25. MAINTENANCES e For all vehicles and drivers in the first hour after GIR Titan Hyperion startup then every 24 hours Recomputing can also be launched manually via the menu gt Config Trans actions management Recomputing Maintenances recomputing This operation is available to the manager only Chapter 10 Credits 10 1 Overview GIR Titan Hyperion allows to manage various credits types e Credits by vehicle defined in gt Vehicles Tanks e Credits by department defined in gt Misc Departments credits For TIP2 Vatersay CPUs they can be either standard fuel credits or monetary cred its e Credits by activity defined in gt Misc Activities credits For every type a credit is defined by the following data Product Product for which the credit is deducted Initial credit Initial credit value Credit Current credit value Period Credit reset period defined in gt Misc Credit periods Credit type Blocking or non blocking credit For blocking credits it becomes impossible to take fuel when the credit value reaches zero On the contrary non blocking credits are decreased indefinitely without preventing fueling Credits are deducted when processing a transaction with the corresponding product and when the following condition is true e Credits by vehicle The Vehicle option is enabled in the Credit options field of the vehicle s tank e Credits by department The Department option is enabled in the Credit
26. Mo 11 10 04 10 30 00 E SEL PUMP 12 Select the pump number you wish Pump 1 GOI Validate your choice The pump and the product name appear validate with VAL Single pump When only a single pump is defined on the CPU pump selection is skipped and identification is directly asked Mo 11 10 04 10 30 00 ID VEHICLE or Mo 11 10 04 10 30 00 ID DRIVER 2 2 FUELING 49 2 2 2 Identification e When identifying the vehicle first Pump 1 GOI ID VEHICLE When identifying the driver first Pump 1 GOI ID DRIVER Identification is processed by presenting the badge to the reader or by en tering the code and validating with VAL For a double identification vehicle with Driver id option or driver with Vehicle id option both identifications will be successively requested Possible error messages BADGE NOT RECOGN UNKNOWN BADGE The badge is not defined UNKOWN CODE The code is not defined BADGE EXPECTED The code entered resolves to a vehicle or driver which must be identified by badge BADGE OUT OF CONTEXT CODE OUT OF CONTEXT The badge or code iden tifies a vehicle when a driver is expected or a driver when a vehicle is expected VEHICLE FORBIDDEN DRIVER FORBIDDEN The identified vehicle or driver is forbidden PRODUCT NOT AUTHOR The pump product is not authorized to this ve hicle VEHI NOT AUTHORIZED The vehicle is not authorized to th
27. after the supply are processed before its entry those transactions will be valued with the tank stock unit price that was before the supply Transactions revaluation Transactions valuation can be changed after their creation This can be useful for the following cases e To fix an erroneous supply e To change the unit price of a tank stock Transactions revaluation can be done via gt Config Transactions management Recomputing Transactions revaluation Select a tank a unit price and a time range All the transactions done during the selected time range on the selected tank will then be revaluated with the indicated price This form is preset with the current unit price of the stock and a time range going from the last supply to the current date 7 3 FUEL TRANSACTION MODIFICATION 91 Example Fixing an erroneous meter On 10 10 2004 a 0 8 euro gal 500 gal supply was entered for tank 1 whereas the real value was 5000 gal The error is detected three days later All the transactions retrieved between the 10 10 2004 and the 13 10 2004 have been valuated with an invalid unit price computed from an erroneous supply The correction requires two steps 1 Cancel the erroneous meter then enter a new one with the correct values The unit price of the tank stock is now correct 2 Click on Transactions revaluation and select tank 1 The default values correspond to the required revaluation all the transactions retrieved since t
28. config This table defines the general settings of the application 1 9 1 Identification Default type Default identification method when creating a new vehicle or driver Default identifier Default badge type when creating a new vehicle or driver Default range Default milometer or hour meter range when creating a new vehicle Options e Strict proxi file Automatically assigns badges using the proximity files without prompting for confirmation e Hide id badge code Hides the fields Identifier and Badge code in the vehicle sheet resp driver This option can be used with Strict proxi file to handle badges assignement totally automatically e Set vehicle id resp driver Sets the Vehicle id resp Driver id option when creating a new driver resp vehicle e Hide vehicle id resp driver Hides the Vehicle id resp Driver id option in the driver creation form resp vehicle e Hide badge num Hides the Badge num field in the drivers and vehicles list e Hide code Hides the Code field in the drivers and vehicles list The code will still be visible in the detailled sheet General tab and in the modification form e Hide secret code Hides the Secret code field in the General tab of a vehicle or driver sheet e Conceal Code Conceal Secret code Activates the concealed mode entry for codes resp secret codes In this modes codes are never displayed clearly on the screen e Mandatory expiry Make
29. contains the following elements e Modify button goes back to the form to modify the selected parameters e View all button view all generated invoices on the same page e Printable version button printable version of all the generated invoices each invoice on a separate page e Generate all files button generates one file per invoice in data dto NV invoices For traclient files the file name has the pattern invP NNNNNN YYYYMMDD where P is the invoice profile N the invoice number and YYYYMMDD the current date For transcodings the transcoding name is added before the invoice number e For each customer provider couple 110 CHAPTER 11 INVOICING View button consult the invoice generated for this customer provider couple Printable version button printable version of this invoice Download button download the traclient or transcoding file contain ing all the transactions used for the invoice Chapter 12 Data import and export 12 1 Oil disks import Oil disks import is configured in gt Misc Oil cos which defines the various data formats to import Once this configuration is done import may be e Launched manually in gt Management Oil disks import e Scheduled to run automatically in gt Misc Auto prog 12 1 1 Configuration The Oil cos table contains the following fields Short name Full name Names used to refer to an oil co in the software File Id String identifying the
30. day and that we would like to be warned after two days without any retrieval a limit of 4 should be define When this limit is zero alerts on dialogue errors are never issued Modules alert TIP CPUs only TIP CPUs are made of multiple modules terminal badge reader pump connected to a management unit MU The dialogue alert described above allows to detect connection issues between the MU and the PC Based on the same principle modules alert allows to detect connections issues between the MU and modules This field defines how many MU modules link errors are allowed before an alert is issued Only the errors occuring during an auto matic dialogue for which the Modules test option has been selected are counted When this limit is zero alerts on modules link errors are never issued Real time alert For real time CPUs it defines the maximum interruption length in minutes after which an alert is issued When this limit is zero alerts on real time connections are never issued Products settings e Sale unit volume value and name of the sale unit for this product When these fields are set an additionnal column is displayed in the tanks state See 5 2 1 page 77 44 CHAPTER 1 DATA ENTRY e Options Type Product type Fuel Washing Other used to filter transac tions in the history Options Disable traclient Ignores transactions with this product dur ing traclient exports e Temperature Only w
31. department vehicles Maint entry Declaration of maintenances done for the department vehi cles Manual trans Manual transaction entry for the department vehicles Access int tr mod Allows to modify internal transactions done by the department vehicles Assign tr mod Allows to reassign the department vehicles when modify ing transaction Remote trans Remote transactions control for the department vehicles 1 8 USERS 33 e Short term rental Allows to start or end rental periods for the department vehicles e Authorizations v d Assignment of the direction or department and of the department vehicles in vehicles authorized to a driver Op rations sur les usagers e Consultation Access to the consultation states history sums for transactions involving a department driver e Add Mod Modification of all the department drivers and addition of drivers to that department e Mod id Modification of identification data badge code on the depart ment drivers e Maint mod Modification of maintenances defined on the department drivers e Maint entry Declaration of maintenances done for the department drivers e Manual trans Manual transaction entry for the department drivers e Access int tr mod Allows to modify internal transactions done by the department drivers e Assign tr mod Allows to reassign the department drivers when modifying a transaction e Remote trans Rem
32. destination In application to the L 122 6 1 article of the intellectual property code the klervi company keeps the right to correct mistakes and to establish the particular modalities to which will be submitted the actions defined above The reproduction of the Software code or the translation of the code form are forbidden even when they are essential to obtain the necessary information to the interoperability of the Software with other ones the klervi company keeps this information available to the user We remind you that the violation of one of the Software Authors rights is a counterfeiting crime and that any counterfeiting is punished in France by the L 335 2 article of the intellectual property code and is liable to a 2 years penalty and a 150 000 EUR fine UPDATES Should you have installed an updated version of the Software it constitutes an only one and unique product with the Software that you put up to date You can use or transfer the new Software version only according to the Licence Agreement dispositions Any new version of the Software comes to take over from the previous version and remains submitted to the present Licence Agreement with modification reserve of this Agreement NOMINATIVE INFORMATION 123 The Software possesses a data base which can constitute an automatized nominative information treatment according to articles 16 and 17 of the dated 6th January 1978 Law concerning the information techn
33. directions and departments can be defined conforming to the following rules e If no site is defined the user has access to all sites e If at least one site is defined the user has access to data related to the de fined sites e g dialogue with a site s CPUs site tanks state transactions realized on a site e If no direction nor any department is defined the user has access to all directions e If at least one direction or department is defined the user has access to data related to the defined directions and or departments e g vehi cles and drivers from a department transactions realized by drivers of a direction The value N A for the Access field means that the element is only defined to configure e mails sending See 6 page 83 and has no effect on authorizations Therefore to define a user that has no access limits and who receives alerts for a given site we would declare this site with a N A access For departments and directions access may be defined as reading or writing With a reading access the user is limited to data consulting With a writing access he may realize different operations on data The table below indicates the different operations categories and their authorization status for each access level 1 Vehicles and drivers entry 1 8 USERS 31 2 Maintenances definition 3 Manual transactions transactions modification maintenance declaration message attachment
34. graphical sums See 5 1 3 page 76 Features fuel Gauges manual entry Enables the entry of manual gaugings in gt Tanks state See 5 2 1 page 77 Totalizers manual entry Enables the entry of manual totalizers in Tanks state See 5 2 1 page 77 Temperature corr Enables temperature correction When products have been configured See 1 11 page 44 this allows to automatically correct the volume according to the measured temperature during a tank supply See 7 2 page 89 Set U P at Tref When temperature correction is enabled this op tion allows to interpret by default the unit price entered as price at the reference temperature instead of price at the supply temperature See 7 2 page 89 Hide U P at Tref hides the checkbox in the tank supply form Prod providers Enables entry of a provider and a comment in tank supplies See 7 2 page 89 Temperature mandatory Makes the temperature entry mandatory in tank supplies Provider mandatory Makes the provider entry mandatory in tank supplies Fuel activity code Fuel spec code Shows activity and specific codes in the fuel transactions history 38 CHAPTER 1 DATA ENTRY e Hide credits Hide all data related to credits management in the user interface e Ext vehicle Sets the corresponding option on the fuel transactions for which the vehicle department differs from the driver department except when the vehicle or driver has the nhib ext vehic optio
35. ie between midnight and 1 a m For yearly period reinitialization is made during the first hour of the first day of the selected month If GIR Titan Hyperion is not running when a credit must be reinitialized the reinitialization will occur during the next recomputing during the first hour after the application startup or during a manually launched recomputing Should the application not be runned during several periods in which a credit should have been reinitialized only one reinitialization will occur for the first recalculation Example A credit is defined to be reinitialized every day at 6 a m with an Unlimited carrying over method and an initial value of 50 gal The vehicle doesn t make any fueling during two days On 10 10 2004 at 8 p m the credit is 10 gal and GIR Titan Hyperion is stopped The application is restarted on 12 10 2004 at 8 a m In the following hour a credit recomputing is launched and the credit is reinitialized to 60 10 50 gallons If the application had been runned at least once between the 11 10 2004 at 6 a m and the 12 10 2004 at 6 a m or if it had continued to run during all this time range the credit would have been reinitialized to 60 gal on 11 10 2004 then to 110 gal on 12 10 2004 106 CHAPTER 10 CREDITS Chapter 11 Invoicing 11 1 Configuration gt Misc Invoices An invoice profile is made of the following elements e General profile configuration Parameters tab e Pro
36. is only visible when the Default spec code feature has been enabled in the Manager config See 1 9 page 34 Options Forbidden The vehicle cannot refuel Secret code The entry of a secret code is required after the identi fication This code is defined in the Code field This option is not available if Code Secret code vehicles is enabled in Installer config See below for more details about this option Options fuel Id driver A driver identification is required after having identified the vehicle Attendant The vehicle is an attendant See 2 3 page 51 Attendant menu The vehicle can access the attendant menu See 2 4 page 52 Activity code An activity code is asked after the identification See 1 4 page 24 Specific code A specific code is asked after the identification See 1 5 page 25 Ticket Enables ticket printing at the end of this vehicle s transac tions only with a ticket printer Disable cons comput Disables covered miles and consumption com puting for this vehicle Mutualized When vehicles authorization by driver is enabled See 1 9 page 34 this option sets the vehicle as Mutualized This makes the vehicle available to all drivers with the Auth on mutu option in addition to standard authorizations Inhib ext vehic When the Vehicle ext feature is enabled in the Manager config this option cancels it for this vehicle Forceable meter When this option is enabl
37. module Tot tolerance Tolerance limit beyond which alerts are generated on to talizer reports See 5 2 5 page 80 If this field is zero no alert is issued Ref The Ref fields are used to refer to an element in the specific exports This menu allows to define the Ref field as well a the name for some configuration elements sites CPUs tanks products Zones Zones define the vehicles users authorizations on the CPUs See 1 6 page 25 This menu allows to configure zones on the fuel and access management sets It is possible to define up to 8 zones per CPU Fuel sets Options e Show last meter Displays the last known meter when prompting for a new meter e Log auth failures Creates transactions on access denied errors unknown badge forbidden vehicle e Ignore blocking maintenances When enabled the vehicles that are forbidden because of a maintenance undone won t be blocked on this CPU The other forbidding causes manual fobidding expiry remain applicable For TIP1 Pabbay CPUS this option must have the same value either set or unset for all the fuel sets of a given CPU e Print codes Prints codes on live and ticket printers even when they are used for identification e Display vehicles codes resp driver Shows clear test codes on the terminal during an entry TIP2 Vatersay only 46 Access sets Options CHAPTER 1 DATA ENTRY Force vehicle id by code resp driver A
38. options field of the vehicle s tank e Credits by activity The activity code has been entered in the transaction 101 102 CHAPTER 10 CREDITS 10 2 Credit periods gt Misc Credit periods Credit periods allow to define how and when credits are recomputed Short name Full name Names used to refer to a credit period in the software Period Time unit according to which the Day Hour and Frequency fields will be interpreted It can be Daily Weekly Monthly or Yearly Day Hour Numerical value interpreted according to the defined period Period Day Hour meaning Daily Reinitialization hour from 0 to 23 Weekly Reinitialization day in the week from 1 for Monday to 7 for Sunday Monthly Reinitialization day in the month from 1 to 31 Yearly Reinitialization month from 1 for January to 12 for December Carry The carrying over method to use when a credit is reinitialized The various methos are e None The credit is always reinitialized to the initial credit e Unlimited The credit is increased by the amount of the initial credit without any upper limit e Max 2 init credit The credit is increased by the amount of the initial credit up to twice this value Frequency Allows to define the time limit between two credit reinitializations It depends on the selected period The table below shows the time between two reinitializations for a frequency value F Period Time betw
39. person and the klervi company regarding the Hyperion software product Software as well as any document software and documentation that deals with it INSTALLING COPYING OR USING THIS SOFTWARE IN ANY OTHER WAY MEANS THAT YOU ACCEPT TO CONFORM TO ALL THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT Should you not accept the terms and conditions of this Licence Agreement you will not be authorized to install or use the Software Should you accept the terms and conditions of this Licence Agreement and should you have bought the Software the klervi company allows you to use the Software in the way described below LICENSE CONCESSION The present Software remains the exclusive property of the klervi company It is distributed by the GIR company and usable with Windows 9x 2000 or XP on compatible PC The present E U L A authorizes you to install and use the Software program RIGHTS AND LIMITATIONS The present Software and its documentation as well as any copy remain the exclusive property of the klervi company In France the Software is protected by the Intellectual Property Code and abroad by the international conventions on the author s rights In consequence you should act towards this Software as if it was any other material submitted to the author s rights as a book for instance with only one difference that you are allowed to make a copy of this Software but only for backup or filing purposes You are lia
40. to vehicles field of the desired department This message may not appear on the CPU if there is a message with a superior priority See 1 1 6 page 17 and 1 2 4 page 22 e Definition of credits by department See 10 page 101 e Definition of users rights See 1 8 page 29 e Definition of transactions closure see below Transactions closure Transaction closure can be enabled by defining a Closure day in gt Misc Manager config then ticking the Closure option in the desired directions or departments Once this configuration has been done the gt Management Closures menu allows to close completed months for all selected departments When a period is closed on a given department it becomes impossible to modify or to create new transactions in this department during this period Transaction closure is available to standard users who have the closure right enabled see 1 8 page 29 advanced mode The main manager can also reopen a period that has been closed 24 CHAPTER 1 DATA ENTRY When a period is not closed and that the closure day has been reached an alert is generated Example the closure day is set to 10 From the first to the tenth day of the month a closure to do message is displayed on the dashboard as long a the closure is not done If it is still not done on the 10th an alert is generated and the dashboard message is updated to closure not done Note a period can only be closed when all transactions
41. vehicle The scrapped vehicle is no longer recognized on the CPU and its badge may be assigned to another vehicle This method allows to not erase the scrapped vehicle in order to keep a trace of its transactions If we sum up a period with both the transactions of 20 CHAPTER 1 DATA ENTRY the scrapped vehicle and the transactions of the new vehicle both vehicles will appear on separate lines 1 1 11 Short term rental Short term rental management allows to use a single vehicle in the database to handle several real vehicles that are rented successively during short periods This feature is enabled by the Short term rental option in the Manager con fig When it is so the Rental option becomes visible in the vehicles options Generally the Default spec code feature will also be used to distinguish between multiple rental vehicles A vehicle with the Rental option has the following attributes e A button is available in the General tab to start or to stop a rental period The bouton Start short term rental button shows a form where infor mation on the new vehicle specific code meters can be entered When this form is validated the new data is stored into the vehicle a transaction is created to initialise meters and the vehicle becomes authorized The button End short term rental terminates the rental period the vehicle becomes forbidden until the next start When an expiry date is defined the rental is auto
42. with a 01 01 2005 31 01 2005 period and select it as a Validity calendar in the time slots that are to be limited A vehicle or driver is authorized on a set Fuel or Access at the T time when the following condition is true There is at least one active zone at T which is present both in the vehicle resp driver and in the fuel set resp access set 1 6 ZONES AND TIME SLOTS 27 Access and fuel sets zones are editable in the gt Config CPU tanks tresholds ref and zones management menu See 1 11 page 41 A global summary of the different zones may be consulted in the gt Misc Zones report menu Moreover zones for which a user is authorized are displayed in his sheet Configuration example We consider a petrol station defined with a fuel set We want some of the vehicles to be able to refuel only during working days and the other part to refuel at any time 1 In gt Misc Zones we define the two following zones Zone code Zone name Time slots A 24 24 00 00 24 00 every day B Week 06 00 20 00 from Monday to Friday 2 In the Config then CPU tanks tresholds ref and zones management then Fuel sets we tick A and B zones in the Zone field of the appropriate fuel set 3 In Vehicles we tick the A zone for all vehicles that should be able to refuel at any time and the B zone for all vehicles that should only refuel during working days Note In this case tic
43. 18 20 Driver department ref 219 238 10 Odometer km 239 248 10 Covered distance km 249 258 06 Instant consomption cL 100 km 259 264 06 Reference consumption cL 100 km 265 270 10 Hour meter 1 100 H 271 280 10 Covered hours 1 100 281 286 06 Instant consumption cL H 287 292 06 Reference consumption cL H 293 312 20 Site ref 313 332 20 Tank 1 ref 333 338 06 Tank 1 ratio percentage 100 339 348 20 Tank 2 ref 349 354 06 Tank 2 ratio percentage 100 355 374 20 CPU ref 375 394 20 Pump ref 395 414 20 Product ref 415 424 10 External volume cL 425 434 10 External price cents 435 444 10 Internal volume cL 445 454 10 Internal price cents 455 464 10 Unit price cents 100 465 470 06 Duration seconds 471 490 20 Activity ref 491 500 10 Specific code 501 516 16 Options see the options fields for format C3 fuel 517 525 09 Transaction number 526 535 10 Oil co id version 1 4 13 and above 536 555 20 Driver type ref version 1 4 15 and above 556 625 70 Unused reserved for future use 130 APPENDIX B TRACLIENT FILES FORMAT C3 version Fuel transactions Position Description 01 Date format dd mm yyyyuhh nn ss 02 Vehicle ref 03 Registration 04 Vehicle type ref 05 Vehicle type name 06 Vehicle direction ref 07 Vehicle direction name 08 Vehicle department ref 09 Vehicle department name 10 Driver ref 11 Driver name 12 Driver first name 13 Driver di
44. 2 Click on 96 to access the transaction sheet 92 CHAPTER 7 OPERATIONS ENTRY Click on Modify Click on near the Meter mi field Enter the new meter in our example 72600 Click on Validate Ct A C GIR Titan Hyperion does the following processing e Transaction is Cancelled e Covered distances consumptions and meters are recomputed to cre 2 4 ate a transaction Ti e Transaction is added to the history 8 The sheet of the fixed transaction is displayed The transactions history now contains an additional transaction Date Vehicle Volume Meter Covered Options T 02 04 2004 12347769 59 00 gal 72600 mi 900 mi Ti 02 04 2004 12347769 59 00 gal 72800 mi 1100 mi Cancelled Chapter 8 Access management 8 1 Supervision 8 1 1 Punctual and forced control Access points may be controlled from two different ways e Punctually the access point is opened for a few seconds after having identified a driver e Under forced control the access point is opened for a specified period at a fix hour The definition of the time slots during which the access will be opened is specified by forced zones Forced zones and access point control mode are defined by the installer of Titan Hyperion 8 1 2 Supervision screen The gt Supervision menu allows to visualize the state of access management CPUs This screen displays the various access po
45. 65 42 PROBLEM WHEN ENTERING A METER 71 3 Fix the invalid meter in the last transaction See 7 3 page 91 send fixed data to the CPU then continue the transaction normally Methods 1 and 2 allow to perform the transaction immediately without having to send data back to the CPU But when the problem comes from an invalid meter in a previous transaction they must be completed by the cor rection of this meter Indeed without this correction covered distances and consumptions will be erroneous Example Vehicle V possesses a milometer with a 2000 mi tolerance range The meter entered during its last transaction was 11500 mi It makes a first fueling on 12 05 2004 and enters by error a meter of 13000 mi instead of 12000 As this value is in the tolerance range it is accepted and the following transaction is created Date Vehicle Meter Covered Ti 12 05 2004 V 13000 mi 1500 mi The day after the vehicle comes back to the CPU and enters its new meter 12500 mi The message INCORRECT VALUE appears since the last known meter is 13000 mi Once the error is notified the meter is forced to 12500 mi using the method 1 or 2 A new transaction is created Date Vehicle Meter Covered 13 05 2004 V 12500 mi 500 mi Ti 12 05 2004 V 13000 mi 1500 mi The value of covered distance and the associated consumption is wrong for transactions and 7 It
46. CPUs the operation and the desired options The dialogue report screen is then displayed It allows to control the operation progress on the selected CPUs Operation e Retr Send This is the most common operation It allows to syn chronize data between GIR Titan Hyperion and the CPUs Retr Send Gauge Makes a synchronization then performs a gauging to retrieve the tanks stocks only with a gauge module Gauging data is stored in a history Retr Send Totalizers Makes a synchronization then retrieves the internal totalizers of the pump modules for which a report is enabled Retr Send Totalizers Gauge Makes a synchronization retrieves to talizers and performs a gauging e Retr Config Send Retrieves transactions sends configuration and performs a full data sending Retr Init Config Send Initializes a CPU with a new sequence after retrieving the transactions Init Config Send Initializes CPU with a new sequence Caution this operation erases the transactions stored on the CPU e Retr Wait Init Config Send Initializes a CPU with a new sequence after making sure that the CPU is unused If fuelings or entries are in progress GIR Titan Hyperion waits for them to be finished before initializing the CPU e Memory dump Copies the CPU memory into a file 3 8 SUPERVISION 63 e Reboot Reboots the CPU e Linktest Checks the link between the CPU and GIR Titan Hyperion and shows a r
47. E NN SUP 000 000 000 Tu 7 omomo 0 7 2901BB49 SUP 4790 3880 08100 4981 036 0 00 Total 38 80 0 8100 4981 000 SUP 4700 3807 08100 80 8807 08100 EZ 9738PTO5 DIE 000 000 00000 Total 0 00 0 0000 811 0 00 Total SUP 9490 76 87 0 8100 5781 154 ooo 0 00 DIE 30430 211 87 0 6962 6 485 459 ooo 0 00 Total 288 740 7233 12266 0 00 Average consumption computing There may be a difference between the displayed average consumption and the one obtained from the volume and the covered distance This is normal and the result of a precision concern as shown in the example below We consider a vehicle which realized 3 transactions with an unknown meter for the most recent transaction Date Volume Meter Covered 15 04 2004 57 00 gal N A N A 08 04 2004 55 00 gal 73300 mi 500 mi 02 04 2004 59 00 gal 72800 mi 600 mi Should we calculate a sum of these three transactions we would obtain a 171 gal volume and a 1100 mi covered distance Computing consumption from these two values by saying that 171 gal were used to cover 1100 mi is wrong the last transaction doesn t have a meter and its 57 gal volume must be ignored to compute the average consumption The correct value is then 114 gal for 1100 mi i e 10 36 gal 100mi 5 1 3 Charts Management Fuel transaction charts This screen allows to display fuel transaction sums as histograms Orientation Vertical or hor
48. KS MANAGEMENT 79 allows to take into account the consumption difference between working days and week ends Example The average consumption on a tank is 500 gallons per day dur ing working days and nothing on Saturday and Sunday A stock prediction is launched on Friday evening with 800 gallons left before reaching the alert treshold Then the estimated date to reach the alert will be the next Tuesday The correct choice of the reference period is very important to obtain an accurate estimation It is advised to select a period long enough during which the station activity has been significant Moreover all transactions realized during the period must have been retrieved Reference period Reference period used to compute the estimation Type D fines the limits to display e Zero stock indicates when the stock will go below zero e Blocking and Alert indicate when the stock will go below the corre sponding limits specific to each tank Mode Display mode e In the List mode tanks are displayed in a table with for each tank the number of days before reaching the limits e In the Calendar mode a 5 weeks calendar shows when the limits will be reached Clicking on shows the predicted stocks values for the selected week Autonomy In the List mode using the Capacity gives an estimation of the autonomy of a fuel station Options e Group by site In the Calendar mode displays only once a site name when several tanks o
49. R 1 DATA ENTRY Download freq Defines the frequency in days between two tachograph card downloads TIP2 Vatersay only N A means that card download is dis abled for this driver This field is only available when CPUs are configured to download tachograph cards 1 2 4 Messages Only one message can appear on the CPU for each driver If a driver has several messages the one with top priority will appear following this priority 1 Maintenance message 2 Message attached to the driver Message field 3 Message attached to the driver s department only if the driver is autho rized on the CPU To attach a message to a driver click on Mod in the user sheet s General tab 1 2 5 Authorization In addition to the Forbidden option two criteria determine a user access rights Zone defines zones in which the user is authorized See 1 6 page 25 Expiry allows to define a time limited authorization if a driver s expiry is set to 31 12 2004 it won t be able to use the CPU from January 1 2005 at midnight The driver sheet General tab allows to quickly visualize the access rights Green square The driver is authorized summary of the authorized zones and sets is displayed Red square The driver is forbidden and the reason is displayed A driver may be forbidden for the following reasons e Forbidden the Forbidden option is enabled e Expired the deadline has expired e No zone the driver is not authorized on any z
50. This part describes what to do when a meter is refused with an INCORRECT VALUE message whereas the entered value really corresponds to the vehicle meter 1 Make sure that all CPUs have been synchronized since the vehicle s last fueling This is particularly important when using several CPUs See 3 1 1 page 61 2 Check the value of the meter and the associated range in GIR Titan Hyperion Various cases are possible e The defined range is too low the range value must be higher than the maximum distance that a vehicle may cover with a fueling In this case fix the range value and perform a synchronization dialogue with the CPUs e The vehicle has made fuelings that have not been entered enter these fuelings with a manual transaction See 7 1 page 87 then launch a dialogue or force the meter using method 1 or 2 below e The meter entered during the last transaction is wrong use one of the three methods below Three methods are available to perform a fueling when the value of a meter is invalid Meter refused INVALID VALUE 1 2 3 Force the meter Force the meter Fix with an attendant transaction with a remote transaction old meter Ready for Send data delivery on CPU i y Fix Ready for old meter delivery 1 Force the new meter with an attendant transaction See 2 3 page 51 2 Force the new meter with a remote transaction See 3 3 2 page
51. This test tool is also available in gt Config Verifications Test e mail sending To send e mails to a user without allowing him to connect to GIR Titan Hyperion just define a user account with a blank password The definition of messages to send and addresses is then the same as for a normal user Chapter 7 Operations entry 7 1 Manual transaction 7 1 1 Manual entry and regulation A manual transaction can be created for the following cases e Entering an off site fueling e Totally manual management with a fictive CPU e Regulation after a failure in automatic management The two first points can be used under normal system behaviour They are available via the gt Manual trans menu The Pump field contains a list with the various products available for off site fuelings as well as pumps declared on a fictive CPU The third case is intended to overcome a temporary problem for instance an hardware defect which requires the delivery to operate manually for some days It can be accessed by gt Misc Manual regul trans fuel By default only the manager is entitled to enter regulation transactions in order to avoid innoportune manual transactions on automatically managed pumps This can be made available to all users by ticking the corresponding option in Manager config See 1 9 page 34 Both entry forms are strictly identical except for available pumps A pump is displayed in the menu gt Manual trans if the asso
52. U when the USB storage option is enabled for a fuel set or access set Each transaction is a line containing multiple fields delimited by and terminated with CRLF Text fields are delimited by a double quote 143 144 APPENDIX D CPU CSV FILE FORMAT D 1 Fuel transactions File name girgcalf csv Position Header Description 01 Date Date and hour of the transaction 02 Id Id number of the transaction 03 Fs Fuel set number 04 P Pump number 05 V Num Vehicle number 06 V Code Vehicle code 07 V Badge Vehicle badge 08 D Num Driver number 09 D Code Driver code 10 D Badge Driver badge 11 AttVeh Vehicle attendant 12 AttDrv Driver attendant 13 Activity Activity code 14 Dur Duration in seconds 15 Volume Volume in cL 16 K Meter Milometer in km or mi 17 H Meter Hour meter in 1 100H 18 Sp Code Specific code 19 Options 8 characters string where each character is space when the option is not set and the character below otherwise 1 G remote transaction 2 F forced meter 3 max volume 4 8 unused 20 29 10 unused fields reserved for future use D 4 EV NEMENTS ACC S D 2 Ev nements carburant File name girgcalg csv Position Header Description 01 Date Date and time of the transaction 02 Id Id number of the transaction 03 Fs Fuel set number 04 P Pump number 05 Event Event text D 3 Transactio
53. Volume Supply volume with two decimal digits Purchasing U P Purchasing unit price Options Regulation Indicates that the supply is a regulation This sets the Regulation option in the supply which will allow to distin guish it from real supplies in the history e With the temperature correction feature See 1 9 page 34 a Tempera ture field is also available When it is set the volume entered is considered as the volume at the measured temperature and the software automati cally computes the volume at the reference temperature using the defined settings See 1 11 page 44 This corrected volume will be the one added to the tank stock Its value can be checked on the supply confirmation page In this case the Purchasing U P applies to the entered volume enter directly the volume at the reference temperature tick the option U P at 15 C e With the Product providers feature See 1 9 page 34 two additional fields can be set during the entry Provider Provider of the supply Commentary Free text field to enter various notes about the supply All the supply information is summed up at the end of the entry on a confirmation page A warning appears if the tank stock after the supply is not between the mininum limit and the tank capacity Tank supplies must be entered in chronological order 7 21 New unit price computing The unit price after a supply is computed using the weighted average price
54. adline has expired e Blocked maintenance not done one of the vehicle s maintenance has reached the blocking limit See 9 page 95 e No zone the vehicle is not authorized on any zone e Insufficient credit the vehicle no longer has any credit 1 1 8 Tanks Generalities Tanks specify which products a vehicle is entitled for They may be consulted via the vehicle sheet s Tanks tab The Capacity field specifies the maximum fuel quantity that can be taken during a fueling If the Capacity value is N A this quantity is not limited A tank Options specify which meters are asked at the CPU when a vehicle is fueling Meter miles to enter a milometer Meter hours to enter an hour meter The Fuel option is only useful for vehicles with several fuel products Super GPL In this case we would tick the fuel option for fuel products and would keep it disabled for other products oil windscreen The Fuel option is useful when computing the consumption and the covered miles during the processing of a fuel transaction Capacity credit The Capacity credit option allows to restrict the fuel quantity that a vehicle can take on short periods TIP2 Vatersay only When at least one product has the Capacity credit option a field named N hours shows up in the Tanks tab It defines the minimum duration during which the capacity can be delivered Ex A vehicle is defined with a 100L gasoil tank The Capacity credit option is
55. al price cents 41 Internal volume cL 42 Internal price cents 43 Unit price cents 44 Duration secondes 45 Activity ref 46 Activity name 128 47 48 APPENDIX B TRACLIENT FILES FORMAT Specific code Options 16 characters string where each character is space when the option is not set or the character below when it is set 9 10 11 12 13 14 over consumption under consumption T imported transaction V manual transaction P attendant G remote E external cancelled replacement of a cancelled transaction renewed meter O partial version 1 4 9 and above forced meter version 1 4 9 and above max volume version 1 4 9 and above to 16 unused Example Over consuming attendant transaction UUW LILILILILILILILILILILI For transactions with the A option the volume exported is the opposite of the volume of the original transaction A and N options can be set only in live exports In that case the transactions are successive in the file F5 version Fuel transactions 129 Position Length Description 000 018 19 Date format dd mm yyyy hh nn ss 019 038 20 Vehicle ref 039 068 30 Registration 069 088 20 Vehicle type ref 089 108 20 Direction ref 109 128 20 Department ref 129 148 20 Driver ref 149 178 30 Driver name 179 198 20 Driver direction ref 199 2
56. al stock real stock difference exceeds this limit Max water Water volume beyond which an alert is issued For com partmented tank the water volume used is the sum of water volumes in each compartment Alert on error Number of consecutive gauging errors beyond which an alert is issued Auto regul Auto regul When those values are not zero a tank supply is automatically created when the difference between theoret ical and real stocks is beyond the defined limit Manual entry Defines how manual gaugings are entered by volume or by height For the latter abacuses must be defined on the tank 1 11 CONFIGURATION 45 Options e Gauge disabled Allows to temporarily disable gauging manage ment for this tank e Ignore probe err Stores gaugings even when a probe error is signaled e Temperature corr Enables temperature correction on automatic gaugings for this tank e Alert on manual gauging Enables alerts generation when entering manual gaugings for this tank The fields Variation Variation Max water and Alert on error are only relevant for tanks with gauging management Each of them may remain at zero to never generate any alert An alert generation creates an event See 5 3 page 80 displays a message on the home page and optionally sends an e mail See 6 page 83 Pumps tresholds Tot options e Totalizer reading Enables automatic report of the internal total izer for this pump
57. ance is made only if distance criteria are defined for this maintenance Meter h Value of the vehicle hour meter when the maintenance is made only if hour criteria are defined for this maintenance The value to enter is in hours with a two digits decimal precision When a new maintenance is entered the Next mi Next H and Next date values are automatically recomputed from the defined frequencies The Last maintenances tab allows to view the last 10 maintenances of a vehicle or driver A complete history of the maintenances carried out may be consulted in gt Management Maintenances hist 9 3 Estimation of maintenances to do The maintenances of a given vehicle or driver may easily be consulted in the various tabs of the element sheet GIR Titan Hyperion also allows to visualize all maintenances to be done on the fleet in the menus gt Management Maintenances to do Vehicles and gt Management Maintenances to do Drivers This screen allows to view the maintenances to do from three different ways Currently Maintenances to do currently Prediction estimation Maintenances to do before a given date using an es timation of the vehicle activity during a reference period GIR Titan Hyperion estimates what will be the future meter of a vehicle by the following formula K future Aref Ttuture E Teurrent gt M Ti Keurrent with date to which the maintenances are predicted Teurrent curre
58. at we want to receive an alert about 2 weeks 0 5 month before the term and the Blocking delta of 2 means that the vehicle must be blocked if the oil change has not been made two months after the term e For a new vehicle bought on 15 07 2004 we would like to define a MOT test with a reminder one month before and a blocking at the term The MOT test must be realized the first time 4 years after the purchasing date then every two years We would then choose 15 07 2008 as Next date and 24 as frequency Next date 15 07 2008 Frequency month 24 Alert delta month 1 Blocking delta month 0 e It is possible to define a maintenance to be realized only once by ticking the Only once option For instance to define the 50 000 mi next major service with a reminder 1000 mi before the term and a blocking 2000 mi after we would declare the following maintenance ticking the Only once option Next meter 50000 Frequency mi Vide Alert delta mi 1000 Blocking delta mi 2000 98 CHAPTER 9 MAINTENANCES 9 2 Maintenance entry In GIR Titan Hyperion maintenance entry is the act of declaring that a main tenance has been realized To enter a maintenance click on Enter in the Main tenances tab of the vehicle or driver sheet According to the maintenance up to three parameters may be required Date Date to which the maintenance has been made Meter mi Value of the vehicle milometer when the mainten
59. ation on how to set up this feature contact the GIR com pany 12 1 6 Note on meters Meters entered during an oil card fueling are not always controled contrary to those entered on CPU See 4 1 page 69 Therefore computing covered distance and consumption using such meters is not reliable and it might be interesting to disable it To do so just check the Add on option for all the Oil products defined in this import Transactions imported under this configuration will be considered as add ons for which consumption is reported on the next fueling Moreover updating the vehicle meter on oil disk import can be configured in the Manager config See 1 9 page 34 12 2 Traclient export The traclient file registers transactions processed by GIR Titan Hyperion It is meant to be used in other applications There are two ways to generate a traclient file Automatically by selecting the desired format in gt Misc Manager config Several automatic exports are available e Live transactions are added to the file as they are processed File name data dto traclien dat e Daily a file containing all transactions done on the eve is generated at the hour defined in the Manager config File name data dto traclien AAAAMMJJ dat e Monthly a file containing all transactions done during the last month is generated at the day defined in the Manager config File name data dto traclien AAAAMM dat In formats anterior to C2 and F4 the
60. ayed on the first line is replaced by one of the following messages e TACHO DOWNL xx Indicates a download in progress with the progress percentage e TACHO NO DOWNLOAD Indicates that a card has been detected but that no download is occuring event indicating the detailled cause is recorded ex unknown card download already done recently e TACHO DOWNL OK Indicates that the download completed successfully download generally lasts 3 to 5 minutes 2 8 PRINTING 59 e TACHO DOWNL ERROR Indicates that an error occured during the down load The downloaded files are stored in data dto tacho In gt Config CPUs Fuelsets it is possible to defined a directory to which downloaded files will be copied The default file name is tacho CCCCCCCCCCCCCCCC YYYYMMDD dat where CCC is the card number and YYYYMMDD the download date If a card is downloaded several times on the same day a N suffix is appended before the dat extension In the same menu the Renaming field allows to select another naming con vention which will be used when copying the file to the external directory 2 8 Printing 2 8 1 Live printing Live printing allows to keep on paper an history of all the transactions registered on a CPU Fuel transactions are printed using the following format Date Time P Prd Volume Vehicle Meter Cov Cons Driver Act Sp Att 21 03 17 55 2 DIE 143 50 VVVVV 175689 950 15 1 DDDDD A 7788 Fields desc
61. ble for the physical security of this copy 121 122 APPENDIX A LICENCE AGREEMENT You can only yield the Software and its documentation to another person if you have the previous written agreement of the klervi company and on a permanent way on the condition that you do not keep any copy and that the beneficiary accepts the stipulations of the Licence Agreement To the exception of the cases expressly previewed in the Licence Agreement the transfer renting hire purchase loaning copying modification translation sub licence part time sharing transmission or electronic reception of the Software of its base or its concerned documentation are not authorized You acknowledge that the Software under the source code form remains a commercial secret of the klervi company and for this reason you accept to not modify the Software nor try to take it to pieces nor discompile or disassemble this Software except and only when such activity is expressly authorized by the applicable legislation despite of this restraint You commit yourself to not develop or commercialize the Software object of the present contract or products that could be in competition with it and or based on one or more elements that have been extracted from it It is forbidden to reproduce translate adapt fix or modify the Software as well as its documentation even when it should be necessary in order to allow the use of this Software in conformity with its
62. bles Global alerts e Application General alert messages e Oil import Report on automatic oil data imports Alerts available for sites e Tanks Alerts on tanks levels and totalizers reports e Pumps Alerts on pumps states e Watch Alerts when a vehicle or driver carries out a transaction in a watched zone Alerts available for directions and departments e Maintenances Alert whens maintenance reaches the alert or block ing limit e Overcons Alerts when a vehicle is overconsumming e Expiries Alerts when a vehicle or driver authorization expires or when a credit is depleted The latter only appears when an associated event is generated See 10 2 page 102 e Closures Alert on closures not done e CPU Alerts on CPU link error see 1 11 page 41 for detailed condi tions to trigger this alert 6 8 ADDRESSES 85 e Invalid badge AlertsO when an unknown badge is used on a CPU Options e Groupe expiries Group maintenances default an e mail is sent for each new event For maintenances and authorizations expiries this can lead to a lot of messages in a short time When those options are enabled maintenances and expiries that oc cured on the same day are sent in a single message 6 2 2 Periodical reports Each report may be sent daily weekly or monthly When no period is chosen report sending is disabled For some reports it is possible to chose the content type fuel access or both info
63. cations Check proxi file It is possible to consult the available proximity files as well as their content On the CPU The initialization of GIR proximity badges may be directly realized on the CPU via the attendant menu The vehicle must have the following parameters Badge num Optional Badge type N A Badge code Empty Code Filled in Identification Badge init The initialization is done by typing the vehicle code before using the badge The detailled procedure is available in the attendant menu description See 2 5 4 page 55 The vehicle Badge code field in GIR Titan Hyperion will automatically be assigned during the first transactions retrieval which will follow the initialization This can involve difficulties when several CPUs are being used at the same time See 3 1 1 page 61 1 1 4 Meters Each vehicle possesses milometer and an hour meter It is not possible to directly modify the value of a meter a fuel transaction must be carried out There is a range of tolerance for each meter which allows to check the value entered by someone while fueling For more details see 4 1 page 69 The meters and ranges defined for a vehicle are displayed under the General tab 1 1 5 Options Spec code Defines a default specific code that will be automatically assigned to this vehicle s transactions when no specific code has been explicitly 16 CHAPTER 1 DATA ENTRY entered This field
64. ciated CPU is disabled otherwise it is displayed in the regulation menu For more details on enabling and disabling CPUs see 1 11 page 41 7 1 2 Entry form e First screen Date Hour Date and time of the fueling Vehicle or Driver Depending on the first configured identifier Pump Pump on which the fueling was realized or Product Ext for an off site fueling 87 88 CHAPTER 7 OPERATIONS ENTRY Volume Volume of the transaction with 2 decimal digits e Second screen depends on config Vehicle or Driver If second identifier is required U P Price Unit or total price of the transaction off site fuelings only Oil co Oil company for external fuelings e Third screen depends on config Meter mi Milometer Meter H Hour meter in hours with 2 decimal digits Activity Activity code Spec code Specific code Options Renewed meter Indicates a meter renewal transaction This disables the computing of covered distance and consumption for this transaction Generally such a transaction will be entered with a null volume Add on Indicates that the transaction is a fuel add on and not a total fueling This disables the computing of covered distance and consumption for this transaction At the end of the entry all the transaction information is summed up on a confirmation page Any validy control on meters entered on CPU is also realized when entering a manual transaction an invalid meter a
65. d Driver word Same principle as for vehicles Preprocessing e Adjust tabs When a tab character is found in the input file the position counter is increased up to the next multiple of 8 This allows to process a file where fields are separated with tabs as if it were a fixed format Options e Ignore leading zeroes Ignores leading zeroes in the registration num ber When this option is enabled 1237769 and 01237769 are processed the same way To be valid a configuration must define at least a date a vehicle a product and a volume Common oil disks formats are available in appendix to this document 12 1 2 Products resolution When importing oil disks the conversion from the product code read in the file to a product defined in GIR Titan Hyperion is done using the Oil products subtable available in the tab of the same name in the oil co sheet Number defines the product code and Product or Pump defines the product or pump to assign to the transaction when the code is read in the file If both the product and the pump are set the pump is used Finally the Options field indicates which options should be set in the im ported transaction 12 1 3 Vehicles and drivers resolution Vehicles and drivers can be resolved either by oil card or by using a specific field in the database Oil cards can be defined e In the gt Misc Oil cards menu e In the General tab of vehicles or drivers sheets An oil card is
66. d to assign it to the selected vehicle or driver Example We would like to use CSV parameters different from those defined in the Manager config for all the users who connect from the example com domain except for the A user To do so we would then define the following profiles Priority User IP address mask CSV parameters 0 A Empty All N A to use Manager config settings 1 N A example com Specific settings 1 11 Configuration The following tables define CPUs configuration They are set by GIR Titan Hyperion s installer and available to the manager for reading only under the gt Config menu Installer config Products Sites Tanks CPUs Badges formats Badges types Access types 42 CHAPTER 1 DATA ENTRY Some of these tables values are editable by the manager using the t Config CPU tanks tresholds ref and zones management menu They are classified into several categories Installer config Caution modifying some of these settings can cause all CPUs to be set to the Modified config state CPU options General CPUs options e Force driver id by code Force vehicle id by code Ignores the identification mode defined in vehicles and drivers and forces to use code identification e Per driver language Shows the CPU language field in drivers to change the CPU language when a driver is identified TIP2 Vatersay only Real time tempo Defines real tim
67. defined by the following fields Oil co Format for which the card is defined Number Card number This field is compared to the card number read in the import field to do the resolution Vehicle Vehicle assigned to this card Driver Driver assigned to this card 12 1 OIL DISKS IMPORT 113 Options e Hour meter Invert the milometer and hour meter fields for this ve hicle in the import format When importing a format resolution is attempted in the following order 1 Search among oil cards defined for this format 2 If badge type is associated to the format search the Badge code field in vehicles or drivers with a matching badge type 3 Search the field defined in Vehicle field or Driver field By default vehicles are searched on the Registration field and drivers are searched on the Ref field 12 1 4 Manual import When the configuration of an oil format is completed select it in the menu gt Management Oil disks import then click on Next In the file list that appears select a file by clicking on 96 A first analysis of the file is then displayed It allows to view what will be imported At this point no transaction has been imported in the database The file analysis simulates an import and classifies input lines into various categories e Processed Number of lines that will be imported as a fuel transaction e Filtered Number of lines ignored because of filtering settings e Doubles Number of line
68. des option is enabled in the Manager config See 1 9 page 34 Grouping specific codes allows to make connections between transactions particularly in sums See 5 1 2 page 74 1 6 Zones and time slots gt Misc Zones 1 6 1 Overview GIR Titan Hyperion allows to define up to 26 zones where each one is coded by a letter from to 7 Zone Zone code Name Zone name used with the code to refer to zone in the software Options e Watch This option allows to be notified when a driver is making a transaction in the zone The notification must have been configured in e mails settings Each zone is associated to a set of time slots which defines when the zone is active The time slots fields are Begin hour Hour when the validity begins End hour Hour when the validity ends 24 00 means Valid until the end of the day Days Days of validity Validity calendar Allows to limit the time slot validity to the specified days Exception calendar Allows to exclude the specified days from the time slot Options 26 CHAPTER 1 DATA ENTRY e Vigilance When this option is enabled in a time slot all the trans actions made in this slot have the Vigilance option The transactions containing this option will be included in the noteworthy transactions list See 5 1 1 page 73 which allows to easily obtain the list of the transactions made in a given period by night for instance Calendars are defined in the gt Misc Cal
69. dge in the Badge num field while cre ating or modifying a vehicle After the validation GIR Titan Hyperion automatically looks for an associated chip code If such code is encoun tered message allowing to automatically update the Badge code field appears click on Yes validates the update This procedure can be made totally transparent by enabling the Strict proxi file and Hide id badge code options in the Manager config e Click on Read proxi file in the General tab Then enter the number which is written and validate For GIR proximity badges delivered since 2005 the number to enter in the Badge num field is composed of the 8 numbers written on the badge and begins with 2 or 3 ex 23450000 1 1 VEHICLES 15 Proximity files must be placed in the data dti directory These are text files containing on each line a badge number and the associated chip code GIR Titan Hyperion provies several tools to check that proximity files are correctly used e n gt Misc Proxi files consistency Vehicles Fuel and Drivers show the list of vehicles or drivers for which Badge num and Badge code fields don t match proximity files Badges shows a list of all badge numbers defined in proximity files and vehicles or drivers to which they are assigned A badge assigned to several vehicles or drivers is shown in red The manager can au tomatically create vehicles or drivers for unassigned badges e In gt Config Verifi
70. dical report Not implemented no subtype The next lines depend on the message type they are of the form Field Value where Field is the field name on 4 characters and Value a variable length text 141 142 APPENDIX C TEXT E MAILS FORMAT C 1 Alert messages Field Description Tphr lt Type name gt lt Subtype name gt Type name fixed length 10 characters Subtype name fixed length 20 characters Date Date under the format dd mm yyyy_hh nn ss Site lt Ref gt lt Short name gt lt Full name gt Ref fixed length 20 characters Short name fixed length 10 characters Full name variable length at most 30 characters Dire lt Ref gt lt Short name gt lt Full name gt Ref fixed length 20 characters Short name fixed length 10 characters Full name variable length at most 30 characters Serv lt Ref gt lt Short name gt lt Full name gt Ref fixed length 20 characters Short name fixed length 10 characters Full name variable length at most 30 characters Afct Assignement at most 21 characters For sites Short name of the site For directions Short name of the direction For departments Short names of the direction and department Mesg Text message at most 80 characters C 2 Report messages Field Description Mesg Not implemented Appendix D CPU CSV file format Those files are saved on a USB key plugged to the CP
71. dit depletion An event is generated for credit depletion only when the corresponding option is checked in the credit period See 10 2 page 102 e Overcons Vehicle overconsumption Tacho Tachograph card downloads 5 3 EVENTS 81 e Rental Short rental start or end See 1 1 11 page 20 e Tank stock Tank stock warning e Transaction Warnings generated during a transaction processing The transaction can be identified by the CPU and the ld number between brackets in the warning text e Transac not processed Transaction data could not be processed 5 3 1 CPU reboot events The following events allow to understand the electrical supply of TIP1 Pabbay CPUs e Start With Retr Startup with RAM restoration e Start No Retr Startup without RAM restoration The meters stored on CPU are then to zero which disables the controls during the first meter entry See 4 1 page 69 It is advised to launch a synchronization between CPU and PC after such an event e Network supplied Module supply e Reboot Sequence Sequence startup e Register Retr RAM backup during a tension drop Appearance order of these events in various real cases e on power cut without any battery 1 Start No Retr when the supply comes back 2 Network supplied some seconds later which period is lower than the battery s autonomy 1 Register Retr when the cut occurs 2 Network supplied some seconds later which period is bigger t
72. ducts to invoice Parameters tab e Providers definition Providers tab e Customers definition Customers tab 11 1 1 General parameters Name Profile name Label Text to display on the final document ex Invoice Comp mode Defines how values are rounded in the generated invoice e Floating Full floating computing values rounded only on display Total Price 5 U P x Volume This can cause differences between total price and intermediate values on the final document e Round U P Guarantees that the total volume multiplied by the av erage U P is equal to the total price Total Price 5 Round U P 4 x Volume e Round total price Guarantees that the sum of total prices for each vehicle is equal to the total price Total Price p Round Round U P 4 Volume 2 107 108 CHAPTER 11 INVOICING Options e Transactions detail Adds a transactions history to the generated doc ument e Disable auto num Disables invoice number auto generation This forces to manually enter a invoice number before the document gen eration e Mandatory provider Makes the provider selection mandatory in the invoice generation form e Disable global customer Disable global provider Hides the global cus tomer or provider in the generated documents e Protected products By default prices to use for products to invoice can be defined by any user allowed to generated an invoice This option rest
73. e dialogues frequency The higher the frequency is the faster the transactions are retrieved However when transactions are very frequent the application can become less avail able for users TIP CPU messages Customizes some messages on TIP CPUs Regional parameters Defines regional parameters to use dates format decimal delimiter units Dates format and decimal delimiter are used on both display and data entry controls Options e Alt meter Shows an additionnal option in the Options fuel fields of vehicles allowing to enter milometer on those vehi cles with a different unit km or mi The converted meter is also displayed in the General tab of the vehicle sheet and in transactions sheets This option only affects data entry and display meters stored in the database still use the unit defined in regional param eters CPUs settings State CPU state Enabled or Disabled Enabling or disabling a CPU is done by clicking on the corresponding button When a cpu is dis abled it is no longer usable in automatic or manual dialogues En tering manual transactions on this CPU remains possible Disabling a CPU can be useful in two cases e Managing a fictive CPU e Temporarily disabling dialogues during a CPU failure Link type Type of the link between the CPU and the PC network tcp serial or modem Link param Link parameters Their parsing by GIR Titan Hyperion depends on the link type e TCP lt host gt lt po
74. e format to use when generating downloadable in voicing files Options e Multiple profiles Enables multiple invoicing profiles A B C Each profile has its own configuration 1 10 Profiles gt Misc Profiles The users profiles allow to adapt some settings according to the connected user 1 11 CONFIGURATION 41 Priority User IP address mask Those fields define the attachment of a profile to one or more users profile is associated to a user when both User and IP address mask criteria are compatible to the connected user The User field is compatible if it is N A or if it is equal to the user The IP address mask field is compatible if it is empty or if the address from where the user is connected matches this mask It is possible to specify a DNS name or an IP address with the and joker characters e g example com 192 168 1 The Priority field defines the order in which the profiles will be tested 0 is the highest priority and 254 is the lowest Dates format Decimal delimiter Field delimiter Defines the format of down loadable CSV files If parameter is set to N A the value defined in Manager config is used Reader address Reader type Address of a badge reader in a host port format If this field is filled in a Read badge button will be available in the vehicles and users sheets for users having this profile This button allows to directly read a badge on the defined reader an
75. e must be between the last known value and the last known value added to the range When a meter is equal to zero no control is made on the entered value Examples Meter Range Authorized values 76000 mi 2000 mi From 76000 to 78000 mi 182000 mi 15000 mi From 182000 to 197000 mi 49000 mi N A No control N A 5000 mi No control the first time When a vehicle is created its meter is set to zero The first meter entry defines its current meter It is possible to initialize a meter e On CPU by typing the meter value as for normal fueling e In GIR Titan Hyperion by creating a manual transaction with zero as volume See 7 1 page 87 It is not advised to define a null range when the associated meter is manually entered Indeed no control is then made and a small error when entering the number e g 5500 instead of 55000 will not be detected The values of covered distances and consumptions will then be wrong and require a manual correction See 7 3 page 91 It is better to always define a range even very big e g 10000 mi An exception can be made for emergency intervention vehicles for which a null range may be defined so that they won t be blocked when fueling When several CPUs are used simultaneously the meters value must be up dated on the various CPUs so that the range control operates correctly See 69 70 CHAPTER 4 METERS 3 1 1 page 61 4 2 Problem when entering a meter
76. each section of the sum on a separate page when printing Show last known meter When the sum is computed on vehicles this option displays an additional column containing the last meter of each vehicle on the selected period Hide milometers Hide hour meters Hide columns related to the cor responding meters Hide prices Hide price related data Total and unit price Show elements with no transactions This option allows to display all the elements on which the sum is realized e g all the vehicles even those that made no fueling during the selected period Show transac count Diplays a column with the transaction count for each element of the sum Split by month Shows a separated sum for each month in the selected period Show reference cons When the sum is computed on vehicles displays a column with the normal consumption range for each vehicle under the form Min cons Max cons Over consumption is indicated by a red max consumption Under consumption is indicated by a red min consumption Filtr cons anomalies Only show vehicles that are over or under consuming Product detail No Displays only one line per element summing the values for each product Ext Int together Displays one line by product for each element sum ming on site and off site fuelings for the same product 5 1 FUEL TRANSACTIONS 75 e Ext Int distinct Displays one or two lines by product for each ele ment separating the on
77. eased after a couple of minutes As for an attendant transaction See 2 3 page 51 it is possible to bypass certain limitations on a remote transaction In this case a warning will appear with the nature of the forced limitation The following controls can be bypassed e Explicit ban e Expiry date 66 CHAPTER 3 CPU COMMUNICATION e Zone based authorization e Blocking because of a maintenance not done e Blocking because of an insufficient credit 3 4 Resolving errors In addition to simple communication errors there are also various dialogue errors which require an human intervention to be solved 3 4 1 Modified module Cause Each time configuration is sent GIR Titan Hyperion generates a cookie random number which is stored on both the CPU and the PC During each dialogue the cookie is read from the CPU and compared to the one on the PC It they are different the dialogue fails with a Modified module error Solution 1 Ifthe CPU contains transactions that should be retrieved but that the cookie differs for instance because an old backup was restored perform a Retr Config Send dialogue ticking the Force retr modified module option Solution 2 If the CPU comes from a standard exchange and that the data it may contain can be discarded perform a nit Config Send dialogue 3 4 2 Modified config Cause After a change in a CPU configuration GIR Titan Hyperion refuses to dialogue with it until the new configuratio
78. ed meter range control can be bypassed when entering a meter on the CPU TIP2 Vatersay only This requires to enter the same meter twice then to confirm that the value must be forced Show cons Enables the display of instantaneous consumption on the CPU at the end of a transaction TIP2 Vatersay only Rental Enables short term rental management on this vehicle See 1 1 11 page 20 when the feature is enabled in the Manager config Option Code 4 Secret code By default vehicles only have one Code field which is used to identify the vehicle directly or via the attendant and to serve as a secret code if the Secret code option described above is activated 1 1 VEHICLES 17 Should we wish that the vehicles could be identified by code then confirm their identification with an additional secret code the Code Secret code ve hicles option in the Installer config table should be activated This option can only be activated by GIR Titan Hyperion installer When this option is enabled a new Secret code field appears in the vehicle modification form and the existing Code field length is reduced by 2 The Secret code is numerical and composed of 4 figures The zero value means secret code The following table sums up the different available identification modes as well as the field which will be used as a secret code The identification method of a vehicle may be consulted in the vehicle sheet General tab
79. een two reinitializations Daily F days Weekly F weeks Monthly F months Yearly F years Options e Event on depleted Generates an event See 5 3 page 80 when the credit is depleted 10 3 Monetary credits Monetary credits can be handled in two ways depending on the settings in the Manager config 10 3 MONETARY CREDITS 103 e Without history Same principle as volume credits with an initial credit and reinitialization period e With history Credits must be reloaded manually using a dedicated form The credit value can t be modified directly Each reloading is kept in an history In both cases monetary credits required a unit price to be defined for the required products 10 3 1 Unit price This price defined manually is totally independant from the tank stock unit price For department credits a product unit price is defined under the Products tab in the gt Misc Departments credits menu The unit price value for a given product and a given department is as follows e If the product department couple is explicitly defined under the Products tab use the value defined in the U P field correspondant e Else use the value defined in the default U P field for this product A default unit price should always be defined for products on which a mon etary credit is declared The Margin field in default products settings allows to stop the fuel delivery before the credit reache
80. enabled and the N hours field is set to 4 Then the vehicle can take at most 100L of gasoil every 4 hours The other fields in the Credits section will be explained in the credits chapter Chapter 10 page 101 If credits are not managed leave these fields to N A Consumption management Consumption criteria can be defined e Specifically for each vehicle under the Tanks tab in the vehicle sheet e For each vehicle model in gt Misc Vehicles models when this feature has been enabled in the Manager config The Cons miles and Cons hours fields represent the reference consump tions for a given product They are used to determine if a vehicle over or underconsumes If those values are N A there won t be any over or under consumption indicator The tolerance limit for the reference consumptions is defined in the Manager config See 1 9 page 34 1 1 VEHICLES 19 It is also possible to define customized values for these limits via the Min cons miles and Max cons miles fields repectively Min cons hours and Max cons hours for hour meters If those two fields are N A the limit defined in the Manager config is used If at least one of those two is defined customized values are used Leaving one of those two limits to N A allows to disable the over or underconsumptions for a given vehicle Tolerance ranges are displayed in the tanks list The table below emphasizes the different possibilities Re
81. endars menu They are made of a days list if only the Date field is filled or of a periods list if both the Date and Final date fields are filled On TIP CPUs the calendar is limited to the current week it is then nec essary to make a synchronization between the PC and the CPU at least every week if calendars are defined The Calendar tab in zone sheet displays a summary of the authorizations When only one month appears a click on the day allows to have the detail of the time slots concerning this day A click on the year shows a summary of all the months of this year Examples e define a zone which is valid at any time we would create the following time slot Begin hour End hour Days 00 00 24 00 Mon Tue Wed Thu Fri Sat Sun Conventions Name of a zone which is valid at any time A11 24 24 e To define zone which is valid from 6a m to 8p m during the working days and from 6a m to 12a m on Saturday we would create two time slots Begin hour End hour Days 06 00 20 00 Mon Tue Wed Thu Fri 06 00 12 00 Sat To exclude public holidays from this zone we would define a calendar called Public holidays containing the days to exclude and select it as an Exception calendar for both time slots of this zone To create a zone in which access is limited to the month of January 2005 for instance for a temporary visitor we would define calendar
82. ending on the pump state one of the following operations is available e Block e Unblock e Cancel blocking e Cancel unblocking Blocking or unblocking a pump requires to launch a Retr Send operation on the CPU Hence after clicking on Block or Unblock a confirmation screen appears and allows either to launch the operation immediately or to postpone it When the operation is postponed the request can be cancelled by Cancel blocking or Cancel unblocking As the Retr Send operation may be quite long postponing it may be inter esting when several pumps must be changed at the same time In this case we would chose Later for all the pumps and Immediate for the last one 3 3 2 Remote transaction When a pump is available it is possible to remotely start a transaction by clicking on Transaction GIR Titan Hyperion then tries to reserve the pump On success the message Pump pump name gt reserved appears When a pump is reserved it is no longer available for a fueling on the CPU The reservation can be cancelled at any time by clicking on Cancel reservation Enter a transaction allows to define the various transaction parameters vehi cle driver meters in a form similar to the one used for manual transaction See 7 1 page 87 After entering all the required information the transaction is started on the CPU and the fueling may begin When a pump is remotely reserved but that no transaction is entered it is automatically rel
83. entage 100 329 348 20 Tank 2 ref 349 354 06 Tank 2 ratio percentage 100 355 374 20 CPU ref 375 394 20 Pump ref 395 414 20 Product ref 415 424 10 External volume cL 425 434 10 External price cents 435 444 10 Internal volume cL 445 454 10 Internal price cents 455 464 10 Unit price cents 465 470 06 Duration seconds 471 490 20 Activity ref 491 500 10 Specific code 501 516 16 Options see the options fields for format C2 fuel 127 C2 version Fuel transactions Position Description 01 Date format dd mm yyyyuhh nn ss 02 Vehicle ref 03 Registration 04 Vehicle type ref 05 Vehicle type name 06 Vehicle direction ref 07 Vehicle direction name 08 Vehicle department ref 09 Vehicle department name 10 Driver ref 11 Driver name 12 Driver first name 13 Driver direction ref 14 Driver direction name 15 Driver department ref 16 Driver department name 17 Odometer km 18 Covered distance km 19 Instant consomption cL 100 km 20 Reference consomption cL 100 km 21 Hour meter 1 100 H 22 Covered hours 1 100 H 23 Instant consumption cL H 24 Reference consumption cL H 25 Site ref 26 Site name 27 Tank 1 ref 28 Tank 1 name 29 Tank 1 ratio 30 Tank 2 ref 31 Tank 2 name 32 Tank 2 ratio 33 CPU ref 34 CPU name 35 Pump ref 36 Pump name CPU name pump name 37 Product ref 38 Product name 39 External volume cL 40 Extern
84. eport on the modules status e Modules update Link test Resets all modules then makes a link test as above These operations cause a temporary interruption on the CPU and must not be launched if a transaction is pending Options e Detailed log Generates a detailed file about the exchanges between the CPU an GIR Titan Hyperion These files can be very large e Force retr Allows to force transactions retrieval when it fails indi cating a Modified module error Sending Sending mode selection Delta only sends the necessary data to the terminal Complete sends all the data Thus should we possess a synchro nized base and should we attach a message to a vehicle the De ta sending will only send one vehicle to the CPU whereas the complete sending will send 3000 vehicles Address Leave to Normal The default settings disabled Detailed log and Force retr Delta sending and Normal address fit for a normal use of the software and should not be modified unless there is a problem Disconnect By default the connection to a CPU is established at the beginning of an operation and closed at the end of the operation After operation However it may be interesting to keep the connection during a certain period should we wish to carry out several successive operations on the same CPU This is particularly true when the opening phase takes a long time for instance for a modem connection Two disconnection modes are availab
85. ew dialogue will be attempted This parameter is only valid if an ending hour is specified The N A value indicates to not realize a new dialogue in case of error Options e Disabled Allows to temporarily disable a CPU in the automatic dialogues Caution the CPU will no longer be updated 1 8 USERS 29 e Modules test Performs a modules test during the operation This may generate an alert depending on the settings defined in the CPU TIP CPUs only see 1 11 page 41 1 8 Users gt Misc Users GIR Titan Hyperion can be used simultaneously by multiple users where each user has specific access rights A user is defined by a name User field and a Password to enter on the connection screen According to the application configuration e g for an intranet integration users may also connect without having to enter their password In this case an Options field is also available and allows to specify if a user s identification is to be done automatically or not Each user can be limited to specific operations according to the value defined in the Level field and the criteria in the Authorizations tab Two definition modes are available for authorizations classic and advanced The mode can be chosen in the Manager Config See 1 9 page 34 1 8 1 Classic mode Remarque This mode is kept for compatibility To set up a new installation it is better to use the advanced mode Each user is given an access Level The dif
86. f 05 Vehicle type name 06 Vehicle direction ref 07 Vehicle direction name 08 Vehicle department ref 09 Vehicle department name 10 Driver ref 11 Driver name 12 Driver first name 13 Driver direction ref 14 Driver direction name 15 Driver department ref 16 Driver department name 17 Access result 1 ascii character A authorized R denied Z denied zone 18 Site ref 19 Site name 20 CPU ref 21 CPU name 22 Access set ref 23 Access set name 24 Access type ref 25 Access type name 26 Options 16 characters string where each character is space when the option is not set or the character below when it is set 1 G remote transaction 2 to 16 unused 27 Transaction number 28 37 10 unused fields reserved for future use 140 APPENDIX B TRACLIENT FILES FORMAT Appendix C Text e mails format The first four lines are the same for all messages the following lines depend on the message type Line Description 1 Application name and version e g GIR Titan Hyperion 1 2 10 2 Customer name 3 Empty line 4 Message type of the form Type Type Subtype Messages types and their associated subtypes are e ALRT Alert STOC CONS PUMP MTNC EXPR WTCH LINK IBDG Tank stock Over consuming Pump blocking or unblocking Maintenance Authorization expiry or credit depleted Zone watch CPU link error Invalid badge e REPT Perio
87. f the same site are displayed on the same day Product Product type Site Region Filter on the selected element 5 2 4 Gauging When gauges are installed GIR Titan Hyperion allows to perform a gauging and to consult the obtained information A gauging can be done through two ways e Via the supervision screen See 3 3 page 63 to consult the gauging values from time to time e Via a Retr Send Gauge dialogue to store gauging values in an history Management gt Gaugings history This dialogue can be launched either manually gt CPU comm or automatically See 1 7 page 28 The latter allows to regularly fill the gauging history so that it is possible to generate warnings on the measured values In the gauging sheet the Correction supply button allows to enter a supply where the difference between the theoretical stock and the real stock is already set 80 CHAPTER 5 STATES CONSULTATION In TIP2 Vatersay a gauging is also done after each transaction The gauged height can be viewed in the transaction sheet Several gauging management states are available in gt Management Previous tanks state See 5 2 2 page 78 5 2 5 Totalizers Pump modules have an internal totalizer which increases when a fueling is detected GIR Titan Hyperion allows to automatically read this totalizer in order to check its consistency compared to the stored transactions To enable the totalizer report on a pump tick the Totalizer repor
88. ference Min and Max respectively refer to the reference consumption and the customized limit values defined in the vehicle s tank Undercons tol and Overcons tol refer to the limits defined in the Manager config Reference Min Max Undercons tol Overcons tol Range N A ignored ignored ignored ignored N A 10 00 N A N A 30 00 20 00 96 1 00 12 00 10 00 N A N A N A 25 00 96 N A 12 50 10 00 5 00 14 00 ignored ignored 5 00 14 00 10 00 N A 14 00 ignored ignored N A 14 00 1 1 9 Other information The Maintenances and Last maintenances tabs concern maintenances and will be detailled in the corresponding chapter Chapter 9 page 95 The Last transactions tab allows to access the last 10 transactions of the vehicle If vehicles authorization by driver is enabled See 1 9 page 34 the Auth drivers tab shows the drivers who are entitled to use this vehicle 1 1 10 Scrapping a vehicle This paragraph describes how to scrap a vehicle in GIR Titan Hyperion 1 Edit the vehicle by clicking on Modif 2 In the Badge num field add a just before the number 3 In the Badge code and Code fields delete the current value and leave the fields empty 4 Tick the Forbidden option 5 Save the changes by clicking on Validate 6 Go to the Maintenances tab and tick the Disabled option for each mainte nance of the
89. ferent access levels are described below from the most restrictive to the most permissive Each access level gives a set of operations as well as operations authorized at inferior levels e g a Manager can make all the operations authorized to Standard and Consultation levels The following sums up which operations are authorized on access levels e Consultation Data tables reading e Standard Manual transactions and supplies entry Maintenance declaration for maintenances already defined Fuel transactions correction vehicle driver meters activity and spe cific code Messages attachment to vehicles and drivers Dialogues Link test Retrieve Send Gauges and totalizers Super vision e Workshop Maintenances editing 30 CHAPTER 1 DATA ENTRY e Local manager Configuration tables reading Vehicles and drivers tables editing Dialogues all operations e Manager Users definition Price and volume correction on fuel transactions Data tables editing menu gt Misc Management operations menu gt Config Data imports exports e Installer Configuration tables editing ransactions reprocessing Manager and Installer levels can access the whole database For other levels it is possible to restrict access to some sites directions or departments This can be done using the Authorizations tab in each user s sheet For each user a list of sites
90. g elements On the top left the tank and product names On the top right the navigation symbol same usage as for the pumps submenu On the bottom left the theoretical stock value On the bottom right the list of available operations between brackets 2 6 ATTENDANT MENU TIP2 VATERSAY CPUS 57 Keys 5 and 6 Stock regulation by entering a positive key 5 or negative key 6 supply Confirm the operation with VAL then enter the supply volume and validate Key 8 When a gauge is defined on this tank it is automatically gauged while this screen is displayed The 8 key scrolls between the gauging values which are identified by the letters on the bottom left of the screen Jvc Fuel volume Jhc Fuel height Jve Water volume Jhe Water height Jt Temperature The symbol means that an error occured during the last gauging 2 6 3 Mode submenu This menu shows the fuel set operating mode RESTRICTED MODE DISABLED 5 Press 5 to enable or disable the restricted mode When this mode is enabled is displayed next to the hour Depending on the configuration the restricted mode allows to forbid some pumps or to limit transactions maximum duration 2 6 4 Badge test submenu This menu allows to test one or several badges for which assignment is unknown It has two modes e The first mode tests whether a badge is assigned or not T BADGE A VEHIC 1934 8 Badge assigned to the
91. han the battery s autonomy 1 Register Retr when the cut occurs 2 Start With Retr when the supply comes back 3 Network supplied some seconds later e on a reboot requested from the PC 1 Register Retr when processing the request 2 Start With Retr 30 seconds later 3 Network supplied some seconds later e on initialization or sequence crash 1 Reboot Sequence at the sequence reboot date 82 CHAPTER 5 STATES CONSULTATION 5 3 2 CPU Logs TIP2 Vatersay CPUs have their own messages history available in gt Management CPU Logs Lines beginning with BOOT indicate an electrical reboot Other infor mation in this table is meant to be used by the support staff 5 4 Transactions Id Management Transactions Id The Transactions Id table allows to control transaction retrieval on CPUs Each time a transaction is created on a CPU it is assigned an Id number which is then increased When GIR Titan Hyperion processes a transaction it is stored in both the dedicated history fuel access event and in the Transactions ld table Further consultation of this table can ensure that no transaction has been lost A record in the Transactions ld table where the Id number is zero and for which no transaction type is set indicates CPU initialization 5 5 Other states These states may be consulted via the gt Management menu Tank supplies hist History of supplies made on tanks Pumps blockings history H
92. have been retrieved Thus closing April will only be possible if a transaction retrieval has been done after May 1st at midnight 1 3 2 Types and models gt Misc Vehicles types gt Misc Vehicles models gt Misc Drivers types A Type B Vehicle 1 Vehicle 2 Vehicle 3 Vehicle 4 Vehicle 5 Vehicles and drivers types are used in transactions sums See 5 1 2 page 74 Vehicles models are used in the following operations e Transactions sums computing See 5 1 2 page 74 e Definition of reference consumptions See 1 1 8 page 18 1 4 Activities gt Misc Activities Code Activity code entered on the CPU Short name Full name Name of the activity used to refer to an activity in the software Ref Value used to refer to an activity in specific exports Options e Forbidden Disables the entry of this activity on the CPU 1 5 SPECIFIC CODES 25 e Add on Sets the Add on option on the transactions for which this activity is declared The activities allow to make connections between fuel transactions and may be used for the credit management See 10 page 101 1 5 Specific codes gt Misc Specific codes Code Specific code entered on the CPU Name Name of the specific code used to refer to a specific code in the software The specific codes table is automatically filled in by GIR Titan Hyperion when the Group spec co
93. he following data in the Tanks tab of the desired vehicle for the GOI product Initial credit 100 gal Credit Current credit value e g 100 gal if data is entered the first day of the month 50 gal if it is in the middle of the month Period The period 1 defined above Credit options Vehicle e Definition of a department 10 000 gallons per year gas credit Enter the following data in gt Misc Department credits Initial credit 10 000 gal Credit Current credit value Period The period 2 defined above Moreover the Department option will have to be enabled in the gas tank of all the department s vehicles on which the credit should be deducted 10 5 Credits recomputing Credits recomputing checks all the credits defined in GIR Titan Hyperion for a possible reinitialization This process is launched during the first hour af ter the application startup then every hour It is also possible to launch it manually manager only using the menu gt Config Transactions management Recomputing Credits recomputing 10 5 CREDITS RECOMPUTING 105 Thus if a credit is defined to be reinitialized every morning at 6 a m GIR Titan Hyperion guarantees that it will be reinitialized between 6 a m and 7 a m To ensure that all CPUs will be updated with the new values an automatic dialogue should be defined every morning at 7 a m For daily and weekly periods reinitialization is made during the first hour of the selected day
94. he 10 10 2004 will be revaluated with the new unit price of tank 1 stock 7 3 Fuel transaction modification Fuel transaction modification allows to fix a possible error on a transaction This screen can by accessed by clicking on Modify in a transaction sheet The following data can be modified Il est possible de modifier les donn es suivantes e Volume U P Manager only e Vehicle Driver Milometer Hour meter Oil co Activity Spec code Man ager and standard user To modify a value 1 Select the field to modify by clicking on near this field 2 Enter the new value 3 Click on Validate The transaction modification being an exceptional operation only one field may be changed at a time Moreover a trace of the change is always kept in the transactions history the original transaction appears with the Cancelled option When a meter value is not known it is possible to delete this meter by letting the entry zone empty The meter will then be set to N A and consumption computing will be transfered to the next transaction Covered distances consumptions and meters are automatically recomputed when a modification is made Example modifying a meter We want to change the transaction to set its meter to 72600 mi Date Vehicle Volume Meter Covered Options T 02 04 2004 12347769 59 00 gal 72800 mi 1100 mi 1 Search transaction in the transactions history
95. he application e Show vehicle driver num Shows the Num field for vehicles and drivers This number is automatically assigned by GIR Titan Hyperion and is unique for each vehicle resp driver This number may also be used to identify a vehicle or driver on the ticket printed after a transaction See 2 8 page 59 1 9 MANAGER CONFIG 37 Manual trans regul for all Allows all users to enter regularization transactions See 7 1 page 87 Hide vehicles maintenances Hide drivers maintenances Hide all data related to maintenances management in the user interface Auto vehicles maintenances Shows automatic maintenances configu ration fields in vehicles maintenances Hide Ids Hides the ld field in the multiple histories Vehicles models Enables the Model field in vehicles as well as the Vehicles models table in the gt Misc menu Vehicles models are sim ilar to vehicles types they allow to group vehicle on an additionnal criterion that can then be used in sums Vehicles models can also be used to define general consumption set tings See 1 1 8 page 18 Default spec code Shows the Spec code field in vehicles Hist menu Displays a link to the fuel transactions history in the main menu Regions Enables assignment of sites to regions Explicit zones Simplifies zones management by only displaying the defined zones in the modification forms Charts on 100 elts Increases the number of elements displayed in
96. hen the temperature correction feature has been enabled see 1 9 page 34 These two fields are optional when one of them is not set the tem perature correction is disabled for the associated product This allows to limit temperature correction to specific products Reference temp Reference temperature Tres in Celsius degrees The coefficient at this temperature is 1 Coef Coefficient to apply when the temperature is 10 Temperature correction is computed using a linear interpolation with the two specified values if the reference temperature is 15 and that the coefficient at 25 is 0 9 the coefficient applied at 20 will be 0 95 Tanks tresholds Blocking treshold Stock below which the pumps using this tank are au tomatically blocked Leave this field empty to never block any pump whatever the tank stock is Alert treshold Stock below which an alert is issued Capacity Tank capacity When using multiple gauged compartments it is also possible to modify the capacity of each compartment Tanker When the selected vehicle takes fuel in another tank a supply with the same volume as the transaction is automatically created on the current tank Variation Generates an alert when the real stock theoretical stock difference exceeds this limit For compartmented tank the real stock is the sum of the fuel volumes in each compartment Variation Generates an alert when the theoretic
97. hs 66 3 1 9 Invalid 5 oc mm RR RnB ete 66 3 4 4 Config in 67 Meters 69 4 1 Tolerance ranges i223 9 RR RS RU 69 4 2 Problem when 70 CONTENTS 5 States consultation 5 1 5 2 5 3 5 4 5 5 Fuel transactions s i 4 eese RI RU ee s Dell oe mom nube RIS DURER SUUS 5 1 2 SUMS sese sede ht oe gid ote n uem e e DI Charts oes WIRES SAC ipte er Etha mrs Tanks stocks management 5 2 Tanks State n6 ques te goes ee ERR 5 2 2 Previous tanks state 5 2 3 Stock prediction llle 5 2 4 Gauging s Lo woe eed aod KAY RG ard t ER 52 5 TotalizZers iR Goa puedas RA aah SEVA Rue woe dence en REESE 5 3 1 CPU 5 5 38 27 EOS os eeu Ged Transactions 4 Other states uode ds RUE BA Th ao uA 6 E mails 6 1 6 2 6 3 Global parameters s go ee ee hd er we qe Be SS ew Messages 6 21 Alerts o i aed Baad d 6 2 2 Periodical reports e Addresses X cod RR AK SS voe rA ted 0 en 7 Operations entry 7 1 7 2 7 3 Manualitr nsaction s c e a ahr Se ee a A 7 1 1 Manual entry and regulation
98. ication Badge Badge num Number written on the proximity badge Badge type N A Badge code Chip code of the proximity badge Code Advised 13 14 CHAPTER 1 DATA ENTRY e Identification by a specific badge Identification Badge Badge num Optional Badge type Specific badge type Badge code Chip code of the specific badge Code Advised When identifying by badge entering a code is not neccessary nonetheless it is advised If no code is defined the vehicle will only be identified by its badge If a code comes along with a badge it may be used to identify the vehicle through the help of the pump attendant See 2 3 page 51 This can be useful if someone has lost or forgotten his badge The code is also used to identify a vehicle in the printed transactions from the live printer Each vehicle should be identified with a unique code hence it is forbidden to define several vehicles with the same code A code can be numerical or alphanumerical 1 1 3 Entry of a GIR proximity badge 01234567 GIR LYON 0123 4567 The above picture shows two examples of GIR proximity badges which num ber is 01234567 Several methods are available to facilitate the entry of such badges Via a proximity file The initialization of GIR proximity badges may automatically occur from prox imity files supplied during the installation Two methods exist e Enter the number written on the ba
99. ield is set to N a vehicle with a rental period started on day D will be assigned an expiry date of D When this field is N A the vehicle won t have an expiry date Closure day Enables fuel transactions closure When this field is zero the feature is disabled Otherwise it defines the day in the month after which transactions made the month before must be closed See 1 3 1 page 23 Options e Group spec codes If this option is set when a specific code has been entered in a transaction GIR Titan Hyperion searches this code in the Specific codes table If the code is found the transaction is attached to this code Otherwise the code is created When this option is not set specific codes are only stored as strings in the transactions and the Specific codes table is not used Grouping specific codes allows to compute sums on the transactions sharing an identical code 1 9 MANAGER CONFIG 39 e Conceal users pwd Enables the entry of users passwords in concealed mode Short lists Shows only the first elements in large dropdown lists to reduce web pages size When the element to selected isn t in the list clicking on gt gt gt downloads the full list Launch dial event if another is running Allows to start a dialogue when an other one is in progress The new dialogue will start when the current on completes Auto retry on dblock Automatically reloads a page on Tables in use error Quick hist consultati
100. in gt Misc Maintenance types Maintenances types are separated for vehicles and drivers but they share the same definition Short name Full name used to refer to a maintenance type in the software Alert message Message displayed on the terminal when this maintenance type reaches its alert limit 95 96 CHAPTER 9 MAINTENANCES Blocking message Message displayed on the terminal when this maintenance type reaches its blocking limit Nb reminders Number of reminders on the terminal before blocking Options e Maintenance done on tacho downl For drivers maintenances allows to automatically declare the maintenance as done when a tachograph card is downloaded on the CPU Once a maintenance type has been defined maintenance can be created under the Maintenances tab in the vehicle or driver sheet maintenance is composed of four parameters for each criteria milometer hour meter date Next Next maintenance term Frequency Maintenance theoretical frequency Alert delta Difference between the value defined in Next and the alert limit Blocking delta Difference between the value defined in Next and the blocking limit Alert delta and Blocking delta may be positive or negative When a delta is negative the associated limit will be situated before the term When a delta is positive the associated limit will be situated after the term The picture below shows a maintenance with a negative Alert delta and a positive
101. ints defined on the CPU and their state at the time of the supervision e Available The access point is available for vehicles or drivers identification e Out of zone The access point is currently in no valid zone and is inactive e Forced The access point is currently in a forced zone access is opened e Forced manager The access point is opened because of a remote trans action from GIR Titan Hyperion e Forced stop manager The access point is in a forced zone but opening has been stopped by a remote transaction from GIR Titan Hyperion De pending on the active zones access remains available for the vehicles or drivers identification 93 94 CHAPTER 8 ACCESS MANAGEMENT According to the configuration defined by the installer of GIR Titan Hyperion it may be possible to remotely control the access points using the software When remote control is enabled a Remote button appears near the access point picture Clicking on this button shows the operation selection screen The various operations are Punctual Forced Forced stop operations availability may differ according to the configuration Any remote control by GIR Titan Hyperion generates a transaction which can be assigned on this screen to a vehicle or driver The Validate button launches the remote transaction and Cancel goes back to the supervision screen 8 2 States Access management states are available by the gt Management menu Access transactions h
102. is driver INSUFFICIENT CREDIT The fuel credit is depleted It is possible to ask for a secret code in addition to the badge identification Secret code option for vehicles and drivers The entry of such a code is asked by the following message Pump 1 GOI PIN CODE Enter the code and validate with VAL 2 2 3 Meters entry Meters are asked by the following messages 50 CHAPTER 2 CPU USAGE Pump 1 GOI Meter mi Enter the milometer and validate with VAL Pump 1 GOI Mtr 1 100 H Enter the hour meter and validate with VAL Example for 120 75 hours enter 12075 Error message e INCORRECT VALUE The meter entered is out of the validity range See 4 2 page 70 for problems related to meters entry A meter can be forced even when it is out of the validity range in the following cases e Transaction via attendant See 2 3 page 51 The confirmation message appears after the first meter entry e Vehicle with the Forceable meter option TIP2 Vatersay only The con firmation message appears when the same value is entered twice in a row 2 2 4 Additional entries Some additional entries may be asked depending on the vehicle and driver configurations Pump i GOI Activity Enter the activity code and validate with VAL Pump i GOI Spec code Enter the specific code and validate with VAL Error message e UNKNOWN CODE Undefined activity code
103. is necessary to fix the meter in transaction T so that GIR Titan Hyperion recomputes covered distance and consumptions Date Vehicle Meter Covered 13 05 2004 V 12500 mi 500 mi T 12 05 2004 V 12000 mi 500 mi The transactions stored in history are then correct Method 3 allows to obtain exactly the same result without having to force a meter but it requires to fix the erroneous meter and to launch a dialogue before the beginning of the fueling If the meter real value is not known it is possible to erase it In this case the transaction T would have meter and covered fields to N A and its volume will be reported on transaction 75 consumption 72 CHAPTER 4 METERS Chapter 5 States consultation 5 1 Fuel transactions 5 1 1 History Management Fuel transactions hist This screen allows to visualize all fuel transactions stored in GIR Titan Hyperion By default transactions are ordered by decreasing date antichrono logical Two links in the gt Management menu allow to access directly to transactions of the current and the previous month The Options field notably allows to find the origin of a transaction e Manual Transaction manually entered in GIR Titan Hyperion See 7 1 page 87 e Remote Transaction remotely launched on CPU from a PC See 3 3 2 page 65 e Imported Transaction imported from oil disks data See 12 1 page 111 e Install Test transacti
104. ist History of all access transactions allowed or denied retrieved after a dialogue The Not link allows to access directly to an history filtered on notewor thy transactions The following access transactions are considered as noteworthy e Access denied e Access remotely launched e Remotely forced stop e Access realized in a vigilance zone See 1 6 page 25 Access transactions charts Graphical visualization of access transactions shown as histograms This screen is similar to the one available for fuel transac tions See 5 1 3 page 76 Chapter 9 Maintenances 9 1 Maintenance definition GIR Titan Hyperion allows to manage vehicles and drivers maintenances Vehicles maintenances can use three parameters e Milometer value e Hour meter value e Date Drivers maintenances can use one parameter e Date For each parameter two limits can be defined e Alert limit a message appears on the terminal when the vehicle or driver is fueling e Blocking limit the vehicle or driver can t refuel as long as the maintenance has not been done Blocking only occurs on fuel delivery CPUs the vehicle or driver is still authorized on access management CPUs According to the configuration it may also remain authorized on maintenance CPUs e g oil delivery GIR Titan Hyperion generates an event when a maintenance reaches the alert or blocking limit Before creating a maintenance it is required to define its type
105. istory of pumps state changes Products moves Displays a daily balance of the fuel volumes in and out of a site Chapter 6 E mails GIR Titan Hyperion can send e mails either as alerts ex pump blocked main tenance to do overconsuming vehicle or as periodical reports daily weekly or monthly Configuring e mails in GIR Titan Hyperion is done through 3 steps e Global parameters configuration e Definition of the message to send e Definition of addresses 6 1 Global parameters Global parameters for e mail sending are defined in gt Misc Manager config Sending hour Hour in the day when periodical reports are sent Days Days in the week when the daily and weekly periodical reports are sent For weekly reports the sending day is the first day activated in this field from Monday Sending day Day from when monthly periodical reports are sent SMTP server SMTP server address If this field is not set e mail sending is disabled Sender address Address used in the sender field for messages sent by GIR Titan Hyperion It notably allows to receive a failure notification when a message could not be sent The Sending hour Days and Sending day fields allow to adjust sending so that data is up to date Indeed because of the transactions retrieval mechanism See 3 page 61 the database may not be up to date when a period finishes Example We consider a CPU on which transactions are retrieved every morning a
106. izontal histogram Type 5 2 TANKS STOCKS MANAGEMENT 77 e History Transactions history on the selected period e Average per day Average per week Average usage of the station during the selected period reduced to a day or a week e Dispersion Dispersion of the station usage according to the selected criteria For instance Dispersion per vehicle with the Volume value will display the 10 vehicles which took the most fuel during the se lected period Date Hour Period selection When the chart is displayed navigation buttons allow to move to the previous and next periods or to change the scale The available scales are day week month and year Filtering elements Type of the elements available in the Value fields Value 1 to 3 Type of value to display transactions count volume is also possible to filter on a specific element For instance to compare the evolution of two departments consumptions on a year select Departments as the filtering element then the two desired departments as Value 1 and Value 2 5 2 Tanks stocks management 5 2 1 Tanks state gt Tanks state This screen allows to graphically visualize the tanks state of a given site as well as pumps related to each tank Information on tanks e Current stock indicates the tank theoretical stock according to the trans actions and supplies processed by GIR Titan Hyperion It appears in red if it is below the blocking limit defined for this
107. k supply Detail Detail Detail Detail Detail Tank 2 A suP root Cpu 1 Cpu2 Cpu2 na Current stock 9 686 34 gal Pump3SUP Pump 3 SUP Pump 4 SUP gema Tank supply Detail Detail Detail Detail Cpu 1 Pump 4 GPL Detail Current stock 2 500 00 gal Tank supply Detail LA Tank 4 E 5 2 2 Previous tanks state Management Previous tanks state This screen is an entry point for several states on tanks stocks history The value of a stock at a given date is computed using the current tank stock fuel transactions history and supplies history e Previous stocks Computes the theoretical stock of a tank at a given date e Gaugings and tank supplies hist Compared histoty of gauings and supplies with the evolution of the difference between real and theoretical stocks e Gaugings and transactions hist History of gaugings done after each trans action e Stocks charts Graphical view of a tank stock evolution Each state can be consulted by selecting a tank and a time period then by clicking on View 5 2 3 Stock prediction Management Tanks stocks prediction This screen allows to estimate when a tank will need to be supplied The estimation is based on all the transactions made on each tank during the selected reference period This estimation is done by computing the average volume removed from a tank during the reference period for each day of the week This notably 5 2 TANKS STOC
108. king both A and B for a vehicle is strictly equivalent to tick only A since the A zone contains the B zone We consider a two access sets the Barrier set which controls the main entry and the Washing set which controls access to the washing station area We want to limit the access to the station to some vehicles 1 In gt Misc Zones we define both following zones Zone code Zone name Time slots A Barrier 00 00 24 00 every day B Washing 00 00 24 00 every day 2 In the menu gt Config then CPU tanks tresholds ref and zones manage ment then Access set we tick the A zone in the Zone field of the access set Barrier and the B zone in the Zone field of the access set Washing 3 In gt Vehicles we tick the A zone for all the vehicles and the B zone for those we wish to authorize on the washing area 1 6 2 Advanced management For a large scale zones management in a multi sites context GIR Titan Hyperion allows to define zones that are local to a site Local zones are enabled by GIR Titan Hyperion installer in the Installer config The authorization condition for 28 CHAPTER 1 DATA ENTRY a vehicle or a driver to a fuel or access set is the same as the one described above an authorization is valid when an active zone is present both in the user and in the set The assignment of zones to drivers can be limited to the managers of the site See 1 8 page 29 1 7 Au
109. le for this purpose e Interactive The connection is closed after 6 minutes of inactivity e Stay connected until The connection is closed at the specified hour It is possible to launch a dialogue in one of those two modes only when a single CPU is selected 3 3 Supervision gt Supervision In addition to the dialogue operations seen above GIR Titan Hyperion al lows to interact directly with a CPU thanks to the supervision mode The supervision screen shows the tanks relating to the selected CPU and the pumps associated to each tank It allows to e view tanks stocks 64 CHAPTER 3 CPU COMMUNICATION perform tanks gauging e view pumps states and totalizers e view pending transactions e start a remote transaction Click on Update data to launch a connection on CPU and update the dis played data CPU state displays the CPU status allowing to detect a potential system failure The Last update date indicates when the displayed information has been retrieved The connection to the CPU is realized using the interactive mode See Dis connect page 63 Tanks data e Theo stock Tank theoretical stock updated according to supplies and transactions e Real stock Tank stock read by gauging only with a gauge module De tailed gauging information may be consulted by clicking on Real stock A gauging is automatically launched for each fueling A gauging can be launched on all tanks by clicking on the Force gauging butt
110. llows code identification for vehicles that are configured with a badge identification TIP2 Vatersay only Force pump selection Shows the pump selection screen even when the fuel set has only one pump TIP2 Vatersay only This mode is required to use tachograph card download on fuel sets with only one pump USB storage Records fuel transactions to a csv file on a USB key plugged to the CPU TIP2 Vatersay only Two files are generated one for normal transactions and one for other events unknown badge The format of these files are detailled in appendix to this document Tacho download Enables data download on tachograph cards TIP2 Vatersay only see 2 7 page 58 Force tacho download tests Download tachograph cards what ever the card date is This option is only useful for testing pur pose TIP2 Vatersay seulement Log auth failure Creates transactions on access denied errors unknown badge forbidden vehicle Access forbidden on full memory Forbids the access when no more transaction can be stored Force code id Allows code identification even for vehicles or drivers configured with a badge identification TIP2 Vatersay only USB storage Records access transactions to a csv file on a USB key plugged to the CPU TIP2 Vatersay only Two files are generated one for normal transactions and one for other events unknown badge The format of these files are detailled in appendix to this document
111. matically terminated when the expiry date is reached e The specific code is displayed between brackets in the vehicle name In selection lists default spec code of the vehicle n the transactions history transaction spec code When a rental period is started a transaction is created with the Renewed meter option which guarantees that consumptions will be correctly computed for the different rental periods See 7 1 page 87 Example vehicle is defined with Rent1 in its Registration field A rental is started with the specific code 1111ZZ69 After several transactions the rental is terminated and another one is started with the specific code 22227769 The transactions history will contain the following data Vehicle Meter mi Covered mi Options Rent1 11112269 53 000 N A Renewed meter Rent1 11112269 53 700 700 Rent1 11112269 54 500 800 Rent1 22227769 27 300 N A Renewed meter Rent1 22227769 27 900 600 1 2 DRIVERS 21 1 2 Drivers gt Drivers 1 2 1 General information Num number automatically assigned to each driver by GIR Titan Hyperion This number is unique to each driver When a ticket is printed after a fueling this number may be used to identify the driver See 2 8 page 59 Name Firstname Name and firstname of a driver It is used to refer to a driver in the software Ref Value used to refer to a driver in specific exports 1 2 2
112. n e Vehicles auth by driver Enables per driver vehicles authorizations This involves an additionnal tab in the vehicle sheet showing whom drivers are authorized for this vehicle and in the driver sheet al lowing to define which vehicles are authorized to this driver e Ask spec code on ext tr Enables specific code entry for external transactions e Hide prices Hides all price related data in fuel transactions e Fuel products Shows the Fuel options in vehicles tanks to enable con sumption computing on multiple fuel products ex Super GPL e Short term rental Enables short term rental management for vehicles See 1 1 11 page 20 e Hide hour meters Hides all data related to hour meters in fuel trans actions e Clear message on transac Clears the message assigned to a vehicle or driver when a transaction is retrieved This allows to display a message only once on the terminal e Show totalizer Shows the internal totalizer value in fuel transactions sheet TIP2 Vatersay only The value is taken at the start of the transaction e Disable W A U P Disables fuel transactions valuation using the weighted average unit price of the tank stock Date fields Defines how dates should be entered text input or dropdown lists Monetary credits Enables monetary credits management See 10 page 101 Short term rental expiry Defines the maximum number of days before expiry when starting a rental period When this f
113. n has not been sent Retr Config Send or Retr Init Config Send Caution a CPU can be set to Modified config in two other cases 1 After an application update when there is a change in the way data is sent 2 After restoring a TWB backup since the CPU data may be completely incompatible Solution Perform a Retr Config Send or Retr Init Config Send dialogue 3 4 3 Invalid state Cause When the CPU contains inconsistent information about the size of transactions stored the retrieval fails with an Invalid state error For security purpose GIR Titan Hyperion doesn t automatically retrieve data when a CPU is in such a state Solution Perform a Retr Send dialogue ticking the Force retr invalid state option 3 4 RESOLVING ERRORS 67 3 4 4 Config in progress Cause Dialogue with TIP2 Vatersay CPUs is not possible while the configu ration application is being used Solution Exit the configuration application on CPU to perform a dialogue 68 CHAPTER 3 CPU COMMUNICATION Chapter 4 Meters A vehicle possesses two meters one for the miles and another for the hours The prompt for a meter during a fueling can be configured for each product through the Tanks tab in the vehicle sheet See 1 1 8 page 18 4 1 Tolerance ranges Tolerance ranges allow to check the consistency of meters entered during a fueling When a meter is entered if the associated range is higher than zero the entered valu
114. name of files to import data dti petro lt id gt txt or any file in the directory data dti petro lt id gt The other fields define the position and the length of the various values to read in the file The Length filter allows to only read lines of a given length the Type filter and Client filter allow to only read lines for which the type or client field matches the specified value Some options are dedicated to drivers and vehicles assignment Vehicle badge type When this field is not N A a resolution is attempted between the card number read in the import file and the Badge code field of vehicles that have this badge type This avoids the need to redefine oil cards when they are already use for CPU identification Vehicle field Select the field to use in vehicles resolution Vehicle word Position of the registration number in the field selected above Words are separated by one or more spaces and first word is numbered as 1 When this value is zero the whole field is used Ex Registrations were entered in GIR Titan Hyperion in the form ABCD 12342269 where ABCD is a fleet code and 1234ZZ69 the registration 111 112 CHAPTER 12 DATA IMPORT AND EXPORT number of the vehicle To import an oil file in which vehicles are refered by this number we would define Registration as Vehicle field and 2 as Vehicle word to use the second word in the Registration field during the import Driver badge type Driver fiel
115. nce Contrat will be governed and interpreted in conformity with the French Law In case of dispute both litigants commit themselves to look for an amicable solution By default only the French Court will be entitled to resolve this dispute The klervi company reserves its rights on every non expressly granted rights The klervi company also reserves the right to modify this Agreement without any previous notification If one of the stipulations of the Agreement is considered null and void or unfounded it will be qualified as non written and will not involve the nullity of the other stipulations 124 APPENDIX A LICENCE AGREEMENT Appendix B Traclient files format 126 APPENDIX B TRACLIENT FILES FORMAT F4 version Fuel transactions Position Length Description 000 018 19 Date format dd mm yyyyhh nn ss 019 038 20 Vehicle ref 039 068 30 Registration 069 088 20 Vehicle type ref 089 108 20 Direction ref 109 128 20 Department ref 129 148 20 Driver ref 149 178 30 Driver name 179 198 20 Driver direction ref 199 218 20 Driver department ref 219 228 10 Odometer km 229 238 10 Covered distance km 239 244 06 Instant consomption cL 100 km 245 250 06 Reference consumption cL 100 km 251 260 10 Hour meter 1 100 H 261 270 10 Covered hours 1 100 H 271 276 06 Instant consumption cL H 277 282 06 Reference consumption cL H 283 302 20 Site ref 303 322 20 Tank 1 ref 323 328 06 Tank 1 ratio perc
116. ns acc s File name girgcala csv Position Header Description 01 Date Date and time of the transaction 02 Id Id number of the transaction 03 As Access set number 04 V Num Vehicle number 05 V Code Vehicle code 06 V Badge Vehicle badge 07 D Num Driver number 08 D Code Driver code 09 D Badge Driver badge 10 19 10 unused fields reserved for future use 0 4 Ev nements acc s File name girgcalb csv Position Header Description 01 Date Date and time of the transaction 02 Id Id number of the transaction 03 As Access set number 04 Event Event text 145 146 APPENDIX D CPU CSV FILE FORMAT Appendix E Fueling scenario 147 148 APPENDIX E FUELING SCENARIO E 1 First id vehicle One pump SEL PUMP 123 PUMP 1 DIESEL Validate your choice UNKNOWN BADGE sd ID VEHICLE UNKNOWNCODE PIN code VEHICLE FORBIDDEN VEHICLE OUT OF ZONE Y VEHICLE ODE PRODUCT FORBIDDEN N D I ECCLE d Driver id N Y UNKNOWNBADGE IDDBIVER UNKNOWNCODE PIN code N Y ES Ear qr DIE rus i INVALID CODE PIN CODE 1 DRIVER FORBIDDEN 1 Attendant y DRIVER OUT OF ZONE lt gt DRIVER CODE PIE Cep PECORA N Odometer N Y GP dvd are e 5 INVALID VALUE 2 ool Meter mi Hour meter d N Y Activity Y UNKNOWN CODE j2 Activity Spec code Y
117. ns and supplies realized on the site e Dialogues 1 Basic dialogue operations on the site s CPUs Link test liai son Retr Send Supervision 32 CHAPTER 1 DATA ENTRY Dialogues 2 Advanced dialogue operations on the site s CPUs Manual trans Entry of manual transactions on the site s CPUs Access trans mod Modification of the transactions done on the site Zones Only with local zones management Local zones assignment to vehicles and drivers Tank supply Entry of supplies on the site s tanks Totalizer Entry of manual totalizers on the site s pumps Gauging Entry of manual gaugings on the site s tanks Autorizations on departments and directions Operations on directions and departments Add Mod departments Directions only Creation and modification of departments inside the direction Access int tr mod Modification of internal transactions assigned to the department Access ext tr mod Modification of external transactions assigned to the department Closure Allows transactions closure See 1 3 1 page 23 Operations on vehicles Consultation Access to the consultation states history sums for transactions involving a department vehicle Add Mod Modification of all the department vehicles and addition of vehicles to that department Mod id Modification of identification data badge code on the depart ment vehicles Maint mod Modification of maintenances defined on the
118. nt date Aref distance covered during the reference period T T dates defining the reference period Keurrent current meter value The result of this calculation appears in the Predicted column below the current meter value 9 4 MAINTENANCE RECOMPUTING 99 The Order by term option displays the date to which the vehicle will reach the alert or blocking limit according to the estimation above Mainte nances are then sorted using this date Note the accuracy of the prediction greatly depends on the choice of the reference period It is advised to choose a period long enough at least one month during which the vehicle activity has been significant Prediction range Maintenance reaching their term in a given range The Group by fields defines if elements should be grouped by direction de partment or type or displayed in a single liste in the result screen Several filters are available The State filter allows to display only alert blocking or other maintenances When all boxes are checked all the mainte nances defined in the software are displayed Other filters allow to limit the result to a maintenance type a direction a department The result screen shows vehicles or drivers for which a maintenance to do has been found with the alert and blocking limits values 012 Netscape GIR Titan Hyperion Demo File Edit View Go Window Help Jae 2 Aa Back Forward Reload Home Search Print Security Stop
119. of two fields e Copy Copy a field to another e String edition Modify a string field e Add Add records in subtables e Delete Delete records 117 118 CHAPTER 13 EXCEPTIONAL OPERATIONS The second step defines on which records the operation will be performed It is a filtering screen similar to the one available after clicking on Filter in a table consultation screen When the operation is performed on a subtable e g Departments is a subtable of Directions filter criterions are available for both the main table and the subtable The selected filter is first applied to the main table then to the subtables of the remaining records The following steps depend on the selected operation e Assignment Select the field to modify then the value to assign e Swap Select the two fields to swap e Copy Select the copy source and destination fields e String edition Select the modifications to perform on the string among the following operations Remove prefix Removed suffix Removes N characters at the begin ning or at the end of the string Add prefix Add suffix Appends a text at the beginning or at the end of the string Operation Converts the string to uppercase or lowercase e Add Define the new records in a form similar to the standard record creation form e Delete No additionnal step 13 2 1 Examples e Move all drivers form a department D1 to another D2 1 Select the Drivers table and the
120. ology files and liberties and which should be the object of a declaration In consequence we remind you that you are liable for your data file and that you are compelled to declare it to the National Commission for Information Technology and Civil Liberties before creating it RESPONSIBILITY LIMIT Up to the maximal evaluation authorized by the applicable legislation the klervi company can in no way be responsible for any special accidental indirect or consecutive damage of any nature like an explotation loss a data loss or any other financial loss resulting from the use or from the impossibility to use the product or from the material or the impossibility to supply support services even if the klervi company has been expressly informed of the possibility of such damages HIGH RISKS ACTIVITIES The Software does not admit mistakes and is not designed or manufactured for real time control gears that work in dangerous environments and which require a breakdown resistance as for nuclear sites aerial navigation or communication systems of air traffic control life assistance appliances or arms systems for which a Software defect could involve death important injuries or important physical or environmental damages Hish risks activities The klervi company does not commit itself in anything particularly in no explicit or implicit guarantee conformity or in High Risks Activities adequation GENERAL DISPOSITIONS The present Lice
121. on Only shows the first ten pages in large histories Protected zones Defines the zones that only the main manager is entitled to attach to vehicles and drivers By default the vehicles and drivers zones can be modified by local managers 1 9 6 Traclient export This section defines automatic traclient exports configuration See 12 2 page 114 Live traclient export Fuel options e Manual tr Imported tr Tank supplies Defines which transactions should be used in live export By default only transactions retrieved from CPUs are exported By setting those options it is also possible to export manual and imported transactions as well as tank supplies e Disable mod tr export When this option is set only the original transaction is exported live If modifications are made after that they won t be exported Fuel Access Fuel sums Defines the format of the live traclient files Leave to N A to generate no traclient file Daily traclient export Generation hour Defines the hour in the day when exports should be gener ated This value should be set so that all the transactions done the day before are retrieved when generating the export Lag Defines a duration in days between the export period and the traclient file creation When this field is N transactions made on day D will be exported on day D 1 N This allows to leave a time range to regularize transactions Fuel options Same meaning as for live export
122. on The gauging information retrieved using this method is intended for temporary consul tation only To carry out a gauging which result is kept in an history use a Retr Send Gauge dialogue Pumps data e Pump state Manual mode Pump in manual mode Blocked Pump blocked the cause of the blocking is displayed just after manager Pump blocked by the manager via the supervision screen attendant Pump blocked by the manager via the attendant menu counting error Pump automatically blocked after a counting er N null volumes Pump automatically blocked after several con secutive unsuccessful fuelings See 2 2 5 page 51 module error Pump automatically blocked after a module failure config error Pump automatically blocked because of configu ration error Comm error Pump module communication error Delivery Fuel delivery in progress Entry in progress A driver is entering a transaction on this pump 3 8 SUPERVISION 65 Tank blocked Pump blocked because the tank stock is below the blocking stock Out of zone Pump out of zone Available Pump available Detailed information on a possible pending transaction as well as the to talizer value are available by clicking on Detail below the selected pump The totalizer displayed is the internal totalizer of the pump module and not the totalizer of another counting device 3 3 1 Pump blocking Dep
123. on done during a CPU installation If there is no pump on a manual transaction it means that an off site fueling has been realized The Attendant option indicates that the transaction was done via an attendant The attendant identity can be viewed in the transaction sheet When a filter is enabled a sum appears at the bottom of the page It is computed on all the transactions matching the current filter Noteworthy transactions The Not link in the gt Management menu allows to directly view an history filtered on noteworthy transactions The following transactions are considered as noteworthy e Overconsuming or underconsuming transactions e Remote and attendant transactions e Manual transactions 73 74 CHAPTER 5 STATES CONSULTATION e Transactions realized in a vigilance zone See 1 6 page 25 A periodical report of noteworthy transactions can be sent by e mail See 6 page 83 5 1 2 Sums Management Fuel transactions sums This screen allows to compute sums of fuel transactions according to various criteria The first criteria group defines the result presentation Sum type Sums types have a section element form For instance a Depart ment Vehicle sum will show for each department a table which elements are the vehicles of this department The most common sum types are predefined A click on gt gt gt allows to select custom sum types Options Page break between tables Allows to show
124. one 1 2 6 Other information Maintenances and Last maintenances tabs refer to maintenances management and will be detailled in the corresponding chapter Chapter 9 page 95 If vehicles authorization by driver is enabled See 1 9 page 34 the Auth vehicles tab allows to define which vehicles the driver is authorized to use By default driver is entitled to use all vehicles Authorizations can be defined e By department direction or department group depending on the config uration e On particular vehicles 1 3 ASSIGNMENT OF VEHICLES AND DRIVERS 23 The Last transactions tab allows to access the last 10 transactions of the driver 1 8 Assignment of vehicles and drivers 1 3 1 Directions and departments gt Misc Directions Direction A Direction B Department 1 Department 2 Department 3 Vehicle 4 Vehicle 5 Vehicle 6 L Driver 1 Driver 2 Driver 3 Driver 4 Driver 5 The field Department in vehicles and drivers refers to the department to which they are assigned Each department is itself connected to a direction Direction and department assignemnt is use in the following operations Vehicle 2 Vehicle 3 Vehicle 1 J e Transactions sums computing See 5 1 2 page 74 e Assignment of a given message to all vehicles or drivers of a department using the Message to drivers or Message
125. ote transactions control for the department drivers e Authorizations v d Modification of vehicles authorized to the department drivers Notes There are default authorizations and specific authorizations for sites as well as for directions and departments The default authorization applies for all the sites resp directions departments which are not explicitely mentionned in the specific authorizations Example There are 3 sites A B and C We would like to define a user that could launch dialogues on the B site and that could only consult data of the A and C sites To do so we would tick Consultation in the default authorizations and then add the B site in the specific authorizations ticking Consultation and Dialogues 1 A user is authorized to consult a state when he has at least one element for which consultation is enabled For instance a transaction will be visible in a user s history if consultation is enabled for the vehicle the user or the site The other operations that realize data modifications are only possible when all the elements are authorized For example a user will be allowed to enter manual transaction related to a user a vehicle and a site only if he is authorized to do the Manual trans operation for those three elements 34 CHAPTER 1 DATA ENTRY As for the classic mode the Summary tab allows to view the authorizations applied by the system for a given user 1 9 Manager config Misc Manager
126. pe C F supclient dat Supplies M N fsmclient AAAAMM dat Monthly fuel sums M N fsmclient AAAAMMJJ dat Daily fuel sums W X accclient dat Access transactions 12 3 Transcodings Transcodings are an extension of traclient files meant to adapt the ouput file format to an existing format Each transcoding is identified by a specific name and has the same features as traclient formats The detailled description of transcoding formats is available in another doc ument 116 CHAPTER 12 DATA IMPORT AND EXPORT Chapter 13 Exceptional operations An automatic backup is automatically performed before any exceptionnal op eration that can delete or modify data The backup can always be disabled by ticking the Disable backup checkbox This option should be used with caution as data may be lost 13 1 Purge gt Config Transactions management Recomputing Purge The purge deletes records according to the selected criterions The criterions are as follows e History tables a record is deleted when its date is in the selected period e Vehicles and Drivers tables a record is deleted when it is forbidden and that it has no transactions 13 2 Table update gt Config Table update This operation is usefull to modify multiple records at the same time In the first step select the table to modify and the operation to perform Available operations e Assignment Assign a value to a field e Swap Swap the values
127. ppears in red with the out of range label on the confirmation page This is only a warning and does not prevent from validating the transaction It is then possible to force meter values via a manual transaction It is also possible to enter a manual transaction with a forbidden vehicle or driver A warning message will appear after having selected this particular vehicle or driver Finally any message that would appear on CPU for the driver or the vehicle is also displayed during a manual transaction 7 1 3 Fuel suction When a vehicle is removed from the fleet a fuel suction can be done to put its fuel back into a tank The best way to declare such an operation in GIR Titan Hyperion is to enter a manual transaction for the concerned vehicle on a pump related to the tank where the fuel is put back The volume of this transaction should be negative e g 40 if 40 gallons of fuel were retrieved to remove this volume from the vehicle consumption and add it back to the tank stock 7 1 4 Remote transaction When a remote transaction is launched See 3 3 2 page 65 parameters are entered in a form similar to the manual transaction form with pump and date already set 7 2 TANK SUPPLY ENTRY 89 7 2 Tank supply entry To enter a tank supply click on Tank supply near the selected tank in the gt Tanks state menu e First screen Date Hour Date and time of the supply Tank Tank on which the supply is made e Second screen
128. rection ref 14 Driver direction name 15 Driver department ref 16 Driver department name 17 Odometer km 18 Covered distance km 19 Instant consomption cL 100 km 20 Reference consomption cL 100 km 21 Hour meter 1 100 H 22 Covered hours 1 100 H 23 Instant consumption cL H 24 Reference consumption cL H 25 Site ref 26 Site name 27 Tank 1 ref 28 Tank 1 name 29 Tank 1 ratio 30 Tank 2 ref 3l Tank 2 name 32 Tank 2 ratio 33 CPU ref 34 CPU name 35 Pump ref 36 Pump name CPU name pump name 37 Product ref 38 Product name 39 External volume cL 40 External price cents 41 Internal volume cL 42 Internal price cents 43 Unit price cents 100 44 Duration secondes 45 Activity ref 46 Activity name 131 47 Specific code 48 Options 16 characters string where each character is space when the option is not set or the character below when it is set 4E over consumption under consumption T imported transaction M manual transaction P attendant G remote E external cancelled N replacement of a cancelled transaction CK renewed meter O partial F forced meter 13 V max volume 14 to 16 unused ek N Example Over consuming attendant transaction LILILILILILILILILILILI 49 Transaction number 50 Oil co id version 1 4 13 and above 51 Driver type ref version 1 4 15 and above 52 59 8
129. ricts prices definition to the manager only 11 1 2 Products Product Product to invoice U P charged Defines how the invoiced unit price will be computed e Transaction Uses the U P at which transactions were valued e Purchase Uses the U P of tank supplies V A T V A T rate Coef disp Unit disp Coefficient and unit to use to display volumes By default the coefficient is 1 and the unit is the same as in the application Coef eq Unit eq Coefficient and unit to use to display an equivalent vol ume on the Total row 11 1 3 Customers and providers These tabs define customers and providers addresses to use when generating invoices Addresses positions on the document are defined by the geometric parameters in the Manager config provider can be a site or a region and customer can be a department or a direction The global provider regroups all the sites that are not explicitly defined in the invoice profile Thus if three sites A B and C are declared in the software with only the B site defined under the Providers tab the global provider is the union of and C sites Similarly the global customer regroups all the departments that are not explicitly defined under the Customers tab Those two special elements can be disabled using the dedicated options under the Parameters tab When generating invoices GIR Titan Hyperion uses all customer provider couples for which transactions are found 11
130. ription e Date Time Date and hour of the transaction e P Pump number e Prd Product name e Volume Fuel volume e Vehicle Code or record number of the vehicle e Meter K plus milometer H plus hour meter e Cov Covered distance or time e Cons Consumption e Driver Code or record number of the driver e Act Sp Pmp One of the following optional information by decreasing priority A Activity code S Specific code Vehicle attendant Code or record number U Driver attendant Code or record number Other events are printed with an explicit message ex pump blocked un known badge A blank line followed by the full date is printed on each new day and on the CPU boot 60 CHAPTER 2 CPU USAGE 2 8 2 Ticket printing Ticket printing allows to deliver a receipt at the end of each fueling A ticket has the following format GIR Titan Hyperion www gir fr 21 03 2005 17 55 34 Station CPU 1 Pump 1 DIE Vol 143 50 L V VVVVV U DDDDD K 175689 km A 7788 Description Two lines customizable in the Installer config Transaction date When the CPU is not in the same time zone as GIR Titan Hyperion local and UTC hours are also indicated Site and cpu names Pump and product names Fuel volume Vehicle letter V Driver letter U Milometer letter K Hour meter letter H Activity code letter A Specific code letter S When using credi
131. rmation types For transactions histories it is possible to receive either a complete history or an history with only noteworthy transactions See 5 1 1 page 73 Reports available for sites e Stocks Tanks stocks last gaugings and sum by CPU pump e Transactions Supplies and transactions made on the site Fuel Tank supplies history Fuel transactions history Access Access transactions history Reports available for directions and departments e Transactions Transactions made by members of the direction or de partment Fuel Fuel transactions history Access Access transactions history e Sums Sums on transactions of the direction or department Fuel Fuel transactions sum by department vehicle 6 3 Addresses A user s addresses are defined in the E Mails tab of the user sheet gt Misc Users When a user must be informed GIR Titan Hyperion sends a message with the same content to each of these addresses Three formats are available e HTML HTML format similar to the one used in the application e Printable HTML H TML format intended for black and white printing e Text Simple text format only for alerts This format is intended for an automatic process 86 CHAPTER 6 E MAILS E mail sending and addresses validity can be tested by clicking on Test in the E Mails tab GIR Titan Hyperion will then send a text format message to the selected address
132. rt gt The host name may be an IP address or a DNS name e g 192 168 0 123 6001 e Serial lt comX gt where X is a serial port number e g com1 1 11 CONFIGURATION 43 e Modem lt comX gt lt tel gt lt atdt gt lt at amp f gt where X is the se rial port on which the modem is connected and tel is the phone number to dial e g com2 0478741234 The successive com mands sent to the modem are 1 atz 2 Command specified in the fourth parameter at amp f by de fault 3 Command specified in the third parameter followed by the phone number atdt by default Mode Synchronisation mode between GIR Titan Hyperion and the CPU TIP CPUs only e Autonomous Connection with the CPU is temporarily estab lished during dialogues which can be manually or automatically launched See 3 page 61 e Real time Connection with the CPU is permanent Transactions are retrieved in real time by the software and data is regularly synchronized e Autonomous without auto conn Identical to autonomous mode except for the supervision screen where the user must explicitely ask for the connection to the CPU Dialogue alert For autonomous CPU it defines how many consecutive dialogue errors are allowed before an alert is issued Only errors occuring during an automatic dialogue are counted Generally this limit will be defined according to the number of auto matic retrievals scheduled Thus if two retrievals are scheduled each
133. s pump blocking or unblocking Tanks key 2 Consultation of tanks theoretical stocks entry of supplies gaug ing Mode key 3 Restricted mode configuration 56 T Badge key 4 Badge test Badge key 5 Badge initialization Ticket key 6 Print a test ticket Key 8 Go to the next screen CHAPTER 2 CPU USAGE In all this section any scrolling using the and keys is also available with the 7 and 9 keys on numerical keyboards 2 6 1 Pumps submenu This menu shows the pumps status Pump i GOI ENABLED 58 The screen contains the following elements On the top left the pump and product names On the top right the navigation symbol It indicates whether there are pumps before or after the current one When applicable the and keys allow to scroll between the different pumps On the bottom left the pump state ENABLED when the pump is available or DISABLED followed by the blocking cause when it is blocked On the bottom right the list of available operations between brackets Key 5 blocks or unblocks the pump When pressing this key a confirmation message shows up ENABLE or DISABLE The VAL key confirms the operation EFF cancels it Key 8 shows the totalizer value Press 8 again to go back to the first screen 2 6 2 Tanks submenu This menu shows the tanks status Tank 1 GOI T 18006L 568 The screen contains the followin
134. s that define an already imported fuel transaction e Not processed Number of lines that cannot be imported The right column indicates the causes of these errors e Warnings Warning messages generally corresponding to pieces of infor mation in the input file which could not be decoded without preventing an import For instance an activity code for which no assignment was found will appear here The total of the first four categories is the number of non empty lines in the file Below this table the dates of the first and last transactions that will be imported are displayed To import the transactions into the database click on Yes If an error occurs it is possible to erase the transactions imported in a given time range in order to launch a new import This feature can be accessed in the lower part of the screen in the Management Oil disks import menu 114 CHAPTER 12 DATA IMPORT AND EXPORT 12 1 5 Automatic import Oil data import can be configured to run automatically at given times See 1 7 page 28 This feature requires an Internet access for GIR Titan Hyperion In that case a synchronisation is made between files located on a remote web server and the local directory data dti petro lt id gt where id is the string defined in the File id oil format After that new files are automatically downloaded and imported A report is sent by e mail to users configured to receive it See 6 page 83 For more inform
135. s the Expiry field entry mandatory in the vehicle resp driver sheet e Set Forceable meter Set Show cons Sets the corresponding option when creating a new vehicle e Show spec code Shows the default specific code in the vehicles list Only when the feature is enabled Display Display opt Defines the fields to use to display a vehicle or driver 1 9 MANAGER CONFIG 35 Code prefix Nb char code autogen Defines the value of the Code field when creating a new vehicle or driver The code is made of a common prefix followed by N automatically generated digits to create a unique code Download freq Defines the default download frequency for tachograph cards when creating a new driver 1 9 2 Fuel Overcons tolerance Defines the consumption beyond which a transaction is considered as overconsuming For instance if the reference consumption is 10 00 gal 100miles and that the tolerance is 2096 a transaction will be considered as overconsuming if its instantaneous consumption exceeds 12 00 gal 100miles Undercons tolerance Defines the consumption below which a transaction is considered as underconsuming Min covered distance for cons Defines the mininum covered mileage that should have a transaction to compute the instantaneous consumption This al lows to avoid generating overconsuming transactions when the covered distance is too low to compute a relevant consumption Min covered time for cons Same thing for
136. s zero This allows to be sure that a credit will never become negative Indeed it is common that some fuel continues to flow just after the delivery has been stopped 10 3 2 Credits history When credits history is enabled monetary credits are no longer reloaded auto matically They must be reloaded manually using the following steps e Go to gt Misc Departments credits e Go to the Monetary credits tab Click on Reload on the desired credit Enter the reloading price Check the new balance and confirm the operation The gt Management Credits reload hist menu shows an history of all credits reloadings entered The gt Management Credits moves hist menu shows a compared history of credits reloading and transactions for a given department This allows to follow the evolution of a balance 104 CHAPTER 10 CREDITS 10 4 Examples Periods e 1 Credit reinitialized every month on the first day of the month Period Monthly Day Hour 1 Frequency 1 e Credit reinitialized every three months on the 15th day of the month Period Monthly Day Hour 15 Frequency 3 e Credit reinitialized every two weeks on Monday Period Weekly Day Hour 1 Frequency 2 e 2 Credit reinitialized every year in June Period Yearly Day Hour 6 Frequency 1 e Credit reinitialized every morning at 6 a m Period Daily Day Hour 6 Frequency 1 Credits definition e Definition of a vehicle 100 gallons per month gasoil credit Enter t
137. se exports do not take into account the possible modifications on transactions after their processing Types of transactions to export are defined in gt Misc Manager config The export can also be limited to specific products in gt Config CPU tanks tresholds ref and zones management See 1 11 page 41 12 8 TRANSCODINGS 115 On demand in gt Management Traclient export Data is written in data dto traclient dat It is possible to filter transactions on a given time range on their origin on CPU manual or imported and on their site direction or department There are several formats of traclient files e Fl Fl Ref Fixed length text format with 2 figures year e F2 F2 Ref Fixed length text format with 4 figures year e F3 F4 F5 Fixed length text format e C1 C2 C3 CSV format Formats F1 F1 Ref F2 F2 Ref are present for compatibility with existing software To develop a new application it is better to use the most recent formats In fixed length formats each transaction is a fixed length line terminated with CRLF In CSV formats each transaction is a line containing multiple fields separated by and terminated by CRLF Text fields are delimited by double quotes The various traclient formats are detailed in appendix to this document In addition to fuel transactions traclient export can be used for the following data Files are always created in the data dto directory Format File Data ty
138. site and off site fuelings Off site fuelings are labelled with Ext after the product name The filter criteria allow to limit the sum to a time range a product with on site and or off site fuelings a site etc The selection of a period is mandatory Once all the parameters are selected click on Compute to display the sum result Selected parameters are shown in the upper part of the screen The Modify button allows to change selected parameters to make new sum 76 CHAPTER 5 STATES CONSULTATION Netscape GIR Titan Hyperion Demo Ei File Edit View Go Window Help gt 3 4 2 dX wd Back Forward Reload Home Search Print Security Stop 2 uf Bookmarks A Location http 1oca1host 8080 cgi bin twcgibin p 474T8 18 10606223415 cmd app amp cnd sums amp Compute amp sum type amp detsil 2 amp t beg Printable version GIR Sums CSV file V1 V2 jp Hyperion Sum by department vehicle from 06 01 2004 00 00 00 to 06 30 2004 23 59 59 Product detail Ext Int distinct Department D01 Internal fleet VSC Commercial vehicles Transactions used 13 Modify D01 Internal fleet VSC Commercial vehicles Volume Price U P Odometer Hour meter UR Covered Cons Covered Cons ga EUR EUR imi h galih DIE 17220 12006 0692 3468 497 000 Vehicle Product HERI IEEE ERES IEEE ERUNT 2210GCB8 DIE 13210 9181 08950 2206 0 00 Total 91 81 0 6950 2 REL
139. sition Length Description 000 018 019 038 039 058 059 078 079 098 099 108 109 118 119 128 129 146 147 155 156 255 19 Date format dd mm yyyy hh nn ss 20 Tank ref 20 Product ref 20 Site ref 20 CPU ref 10 Supply volume cL 10 Total price cents 10 Unit price cents 100 16 Options see the options fields of the C3 Supplies format 09 Transaction number 100 Unused reserved for future use C3 version Supplies Position Description 01 Date format dd mm yyyyhh nn ss 02 Tank ref 03 Tank name 04 Product ref 05 Product name 06 Site ref 07 Site name 08 CPU ref 09 CPU name 10 Supply volume cL 11 Total price cents 12 Unit price cents 100 13 Options 16 characters string where each character is space when the option is not set or the character below when it is set 1 B on cpu 2 A cancelled 3 R regularization 4 T tanker 5 to 16 unused 14 Transaction number 15 24 10 unused fields reserved for future use A cancelled supply is identical to the original one with an opposite volume The A option can be set only for live exports 134 APPENDIX B TRACLIENT FILES FORMAT M1 version Position Length Description 000 000 1 V vehicle U driver 001 030 30 Registration vehicles only 031 060 30 Name drivers only 061 080 20 First name drivers only 081 100 20 Ref 101 101
140. t 6 a m by an automatic dialogue We want to receive an e mail every day with all the transactions made during the day If this e mail is sent between midnight 83 84 CHAPTER 6 E MAILS and 6 a m transactions retrieval won t be done yet so the database won t be up to date and transactions history will be incomplete To avoid this we can define 8 a m as Sending hour so that all transactions will be retrieved before sending the message On the same principle if automatic retrievals are scheduled on an every day basis but Sunday Saturday should be unchecked in the Days field to avoid sending an incomplete report on Sunday morning For monthly reports the Sending day field allows to delay sending at the beginning of each month for instance to regulate some transactions When sending a report GIR Titan Hyperion checks whereas all the transac tions have been retrieved on the various CPUs If not the message will contain a warning as well as the Incomplete label in the subject field Moreover the message will be sent again once all retrievals are done 6 2 Messages to send Messages to send to a user can be defined either in the Authorizations tab or in the E mails tab in the user sheet depending on the configuration See 1 8 page 29 It allows to define which alerts and periodical reports will be sent to a user 6 2 1 Alerts Any alert sent as e mail may also be consulted in the Events and Pumps blockings hist ta
141. t management Remaining credit For monetary credits unit price and total price of the transaction Chapter 3 CPU communication 3 1 Principle Each CPU operates in an autonomous way it possesses a copy of the vehicles and users data in memory and registers the transactions It is then necessary to regularly synchronize data between GIR Titan Hyperion and the CPUs This synchronization operates in two distinct steps 1 Retrieval and processing in GIR Titan Hyperion of the transactions stored on the CPUs TIP CPUs can store up to 2500 transactions 2 Update of the CPUs data from GIR Titan Hyperion database meters blocking etc Any change realized in GIR Titan Hyperion message assignment ban will really be active on the CPU only after having made a dialogue with it 3 1 1 Multiple CPUs Synchronization between GIR Titan Hyperion and the different CPUs is es pecially important when multiple CPUs are being used Indeed each CPU possesses its own copy of the database When entering a new meter this copy is updated with the new meter and the other CPUs remain with the previous value Example with a two CPUs system The vehicle V has a milometer which value is 50000 mi Its tolerance range See 4 1 page 69 is 1000 mi This information stored by GIR Titan Hyperion and sent to CPUs and GIR Titan Hyperion CPU CPU Vehicle V 50000 mi Vehicle V 50000 mi Vehicle V 50000 mi
142. t option in the selected pump module gt Config CPU tanks tresholds ref and zones management When a Retr Send Totalizers dialogue is launched the totalizers of the se lected pump modules are stored in the Totalizers history table GIR Titan Hyperion computes the difference with the previous report Difference tot field in the history as well as the total volume of transactions that have been retrieved between the two reports Difference trans field in the history The difference between these two values is displayed in the Variation field It must be close to zero An alert can be triggered when the Variation value reaches a given limit The alert stays on the dashboard until it is acknowledged To acknowledge an alert go to the totalizer report sheet then click on Ack and confirm the operation 5 3 Events gt Management Events The events table keeps an history of messages generated by GIR Titan Hyperion The various elements types are e Warning Miscellaneous warnings e Invalid badge An unknown or invalid badge was read e Badge init Transaction created when initializing a proximity badge e CPU Transaction created when rebooting a CPU or installing pump mod ules TIP1 Pabbay only e Closure Transaction closure See 1 3 1 page 23 e Login User connection to GIR Titan Hyperion e Maintenances A maintenance reached the alert or blocking limit e Expiry Vehicles or drivers authorization expiry and cre
143. tank and in orange if it is below the alert limit e Detail allows to view detailed information on a tank stock price limits capacity last supplies e Tank supply allows to enter a new supply for this tank e Manual gauging allows to enter a gauging which will be stored in an history gt Management Gaugings history This feature is only available when the corresponding option has been enabled in the Manager config Information on pumps e Detail allows to view detailed information on a pump time delays hangup type last transactions e Totalizer allows to enter a new totalizer report which will be stored in an history gt Management Totalizers hist This feature is only available when the corresponding option has been enabled in the Manager config 78 Netscape GIR Titan Hyperion Demo CHAPTER 5 STATES CONSULTATION EN File Edit View Go Window 4 w 3 4 2 Back Forward Reload Home Search dox Print Security 8 Stop Bookmarks Location http Locathost 8080 egi bin twcgibin p 47478 amp sid 10606223418 cnd spp amp cmd tkstate amp site D Tanks state Site Lyon Lyon Cpu 1 N A Lyon Cpu 2 N A Printable version CSV file V1 V2 Recap Prev Next Back to list Legend Blocking treshold Alert treshold Capacity A 3 _ 1 Cpul Cpu 2 Cpu2 Current stock 15 060 71 gal Pump 1 DIE Pump2DIE Pump DIE Pump 2 DIE Tan
144. te regulation Supply entry 1 Suppl gal Price Euros 54 CHAPTER 2 CPU USAGE Enter the volume of the supply and validate with VAL then enter total price in euros it is possible to enter a decimal number for instace 150 85 and validate with VAL Stock update C1 GOI 1500 g Corr gal Enter the volume to add to the stock and validate with VAL It is possible to decrease the tank stock by entering a negative volume e g 10 to remove 10 gallons 2 5 2 Pumps submenu 1 GOI T 002902 On First line e Pump number from 1 to 16 Use the or 9 and or 7 keys to go from one tank to another e Product name e Value of the pump module internal totalizer Second line Pump state The following states are possible On Pump available Blocked CPU Pump blocked by the attendant via the attendant menu Blocked PC Pump blocked by the manager via the supervision screen See 3 3 page 63 Counting Error Pump automatically blocked after a counting error Volume error Pump automatically blocked after several consecutive un successful fuelings See 2 2 5 page 51 Module error Pump automatically blocked because of a module failure Config error Pump automatically blocked because of a configuration er Blocking or unblocking a pump is done by pressing the keys B M D or 0 2 5 3 Gauges submenu gauging is automatically done when accessing this menu
145. the number of covered hours Merge consecutive meters When two identical fuel transactions are made within the defined time meters and consumptions are assigned to the most recent one Fuel trans dept When processing a fuel transaction this setting defines to which department the transaction will be assigned It may be either the vehicle department or the driver department The department assigned to a transaction is used in the sums See 5 1 2 page 74 Imported trans meter Defines how to handle milometers and hour meters when importing transactions See 12 1 page 111 e Always The transaction meter is used to update the vehicle e Except add on The transaction meter is used to update the vehicle except for add on transactions e Never The transaction meter is never used to update the vehicle Fuel options e Set Undercons on negative covered When this option is set fuel transactions having a covered mileage equal to or under zero are indi cated as underconsuming This allows to include those transactions among the noteworthy transactions See 5 1 1 page 73 1 9 3 Miscellaneous settings CSV section Defines the format of downloadable CSV files 36 CHAPTER 1 DATA ENTRY Spreadsheet Date format Decimal delimiter Field delimiter Excel mm jj aaaa Dot Semicolon HTTP proxy section Defines the proxy server settings for the internet access used by software support E Mails sec
146. tion Defines how and when to send e mails See 6 page 83 Expiries pre alerts By default authorization expiries on vehicles and drivers only generate an alert when the expiry occurs When this field is not zero an alert will also be generated N days before a vehicle or driver expires 1 9 4 Users authorizations Auth settings Defines the mode used to set users authorizations See 1 8 page 29 e Classic Historical setting grouped with e mails definition e Advanced This setting brings a greater flexibility when defining which operations are permitted to each user It is separated for e mails management and more adapted to a large scale application e Advanced detailled This setting is similar to the advanced mode but offers the additionnal possibility to define independant autho rizations on drivers and on vehicles Options e Prevent force manual tr Prevents entry of manual transaction in the following cases Vehicle forbidden for any reason expired out of zone Driver forbidden for any reason expired out of zone Vehicle not authorized to the driver Forcing meters remains possible e Prevent force modif Prevents assignment of forbidden vehicles or drivers in transaction modification e Prevent force remote tr Prevents launching remote transactions for forbidden vehicles or drivers 1 9 5 General parameters Features Those options enable or hide specific features in t
147. tomatic programmings gt Misc Auto prog Automatic programmings allow to plan operations so that they could be automatically runned by GIR Titan Hyperion at a given day and hour Name Programming name use to refer to a programming in the software Operation Operation to run e Retrieve Send Retrieve Send Gauge Performs a synchronization dialogue with the different programmed CPUs See 3 page 61 e Oil import Performs an automatic import of oil data for the defined formats See 12 1 page 111 e Backup Performs a backup of the database in a TWB file e Real time suspension Disables all the real time communications with CPUs during the time range specified by the beginning and ending hours Begin hour Hour when the operation will be launched End hour For the Retr Send operation it keeps the connection on until the indicated hour For the Real time suspension operation it indicates when communications will start again Days Days when the operation should be launched Options e Disabled Allows to temporarily disable an automatic operation exe cution As for Retr Send automatic operations type it is necessary to define the CPUs with which the dialogue must be carried out This is done in the Pro grammed CPUs subtable CPU CPU with which the dialogue must be launched Retry on error If an error occurs on this CPU during the dialogue it allows to define the time in seconds at the end of which a n
148. ue oae dor b Ger 22 1 2 6 Otherinformation 22 1 3 Assignment of vehicles and drivers 23 1 3 1 Directions and departments 23 1 3 2 Types models 24 Activities Y vocum e S 24 l 5 Specific codeso i2 kd 4 amp 9 ae VA 25 1 6 Zones and time slots 25 1 6 OVeEVIewW 2o dro aie ele ae og RUM a 4 25 1 6 2 Advanced management 22s ess 27 1 7 Automatic programmings eA 28 1 85 USCrS vue S UNIES dene SNAM Ede 29 LS GClassiciinode 2 2 seme Ro UO RR 29 1 8 2 31 19 Manager config u s ees 34 PEO Identificatioi s i i e nim a SS ARR RT 34 1 9 2 Fuel hz Lena Ei entre roc net TN Ru aad dd dla 35 1 9 8 Miscellaneous settings 35 1 9 4 Users authorizations 36 CONTENTS 1 9 5 General parameters 36 1 9 6 Traclient export 39 1 971 INVOICES 40 CIO Profiles xe bested osx ees 40 ll Configuration oy ym odo a 41 CPU usage 47 47 2 2 I P eliBEs ea we RE eee aan RO 48 2 2 1 Pumpselection llle 48 2 2 2 Identification Cx 49 2 2 3 i RR EQ Yu EA 49
149. unused fields reserved for future use For transactions with the A option the volume exported is the opposite of the volume of the original transaction A and N options can be set only in live exports In that case the transactions are successive in the file 132 APPENDIX B TRACLIENT FILES FORMAT F4 version Supplies Position Length Description 000 018 019 038 039 058 059 078 079 098 099 108 109 118 119 128 129 146 19 Date format dd mm yyyyuhh nn ss 20 Tank ref 20 Product ref 20 Site ref 20 CPU ref 10 Supply volume cL 10 Total price cents 10 Unit price cents 16 Options see the options fields of the C2 Supplies format C2 version Supplies Position Description 01 Date format dd mm yyyyuhh nn ss 02 Tank ref 03 Tank name 04 Product ref 05 Product name 06 Site ref 07 Site name 08 CPU ref 09 CPU name 10 Supply volume cL 11 Total price cents 12 Unit price cents 13 Options 16 characters string where each character is space when the option is not set or the character below when it is set 1 B on cpu 2 A cancelled 3 EU regularization version 1 4 9 and above 4 T tanker version 1 4 9 and above 5 to 16 unused A cancelled supply is identical to the original one with an opposite volume The A option can be set only for live exports 133 F5 version Supplies Po
150. vehicle 1234 T BADGE A UNKNOWN 8 Badge not assigned Press 8 to go to the second mode e The second mode shows the chip code of a badge and can store a trans action for further processing in GIR Titan Hyperion T BADGE B 12345678 58 58 CHAPTER 2 CPU USAGE Press 5 to store a transaction with this chip code The transaction will be available in the events table See 5 3 page 80 A short description can be entered to identify multiple badges in case several transactions are stored Press 8 to go back to the first mode 2 6 5 Init badge submenu This menu allows to assign a badge to a vehicle or driver It has the following Steps e Select the assignment type Press 1 for a vehicle badge or 2 for a driver badge I BADGE 1 VEHICLE 2 DRIVER e Enter the vehicle or driver code If badge is already assigned to the selected element confirmation is asked I BADGE VEHICLE CODE e Use the badge The assignement in GIR Titan Hyperion will only be complete after transactions are retrieved I BADGE VEHICLE BADGE 2 7 Tacho download TIP2 Vatersay CPUs with a smartcard reader can be used to download tacho graph cards data The file is first downloaded to the CPU then to the PC during transactions retrieval On the CPU card download automatically starts when a card is inserted on the idle state In that case the hour normally displ

GIR Titan-Hyperion User manual

Contents

Download Pdf Manuals

Related Search

Related Contents