FlightConnect™ Office Setup and Operation Aviation Fueling System FlightConnect Office Liquid Controls Group An IDEX Fluid & Metering Business Operation: EM200-17
Table of Contents Appendix Introduction Software License Agreement...............................3 FlightConnect Office Software Overview.............4 Installation & Setup Software Installation.............................................5 FlightConnect Database Population.....................6 Setup & operation FlightConnect Read.............................................7 FlightConnect Edit................................................8 Database Management . .........................................
Software License Agreement Read this license carefully. You agree that by using the fieldized software package, you have agreed to the software license terms and conditions. This agreement constitutes complete and entire agreement between you and Liquid Controls with respect to this product. 1. Liquid Controls hereby grants to Licensee a nonexclusive license to use, FlightConnect Office Software (hereinafter referred to as “Licensed Software”) 2.
Introduction FlightConnect Office Software Overview FlightConnect Office is a software package for office computers used in FlightConnect Fueling Systems. Software in the package is used in conjunction with FlightConnect fueling software (installed on DMS and LCR 600 units in the FlightConnect network) and DBManager software (installed on the office computer). FlightConnect DMS and FlightConnect LCR 600 are automated data capture and data management systems for into-plane fueling operations.
Installation & Setup Software Installation To install FlightConnect Office software, insert the FlightConnect Office CD-ROM into your office PC (or click on the the setup.exe file supplied by Liquid Controls). Installation should begin automatically. Follow the FlightConnect Office installation wizard directions until installation is complete. If the installation does not begin automatically, use your browser to locate the setup.exe application file on the CD-ROM and click on it to begin the installation.
Installation & Setup FlightConnect Database Population After the FlightConnect Office software is installed, the next step is to populate the FlightConnect database with all the pertinent data from your company’s operations. There are two methods for populating the FlightConnect database. Data can be keyed in manually, in the file tabs on FlightConnect Office’s user interface, FlightConnect Edit.
Setup & Operation FlightConnect Read FlightConnect Read converts transaction files (CR501xxx.trn), sent from DMS and LCR 600 units in the network, into files (.txt or .xml) for use in third-party accounting or spreadsheet software. It is a service application designed, in conjunction with DBManager, to run in the background of the computer. FlightConnect Read (and DBManager) must be open to receive and convert transaction files.
Setup & Operation FlightConnect Edit FlightConnect Edit is a user interface where users can manage FlightConnect database files, change settings to FlightConnect fueling software (DMS and LCR 600 units in the network), and convert FlightConnect files into text files (and text files into FlightConnect files). At the top of the FlightConnect Edit window, there are eleven tabs. Tabs are opened with a mouse click.
Setup & Operation Select Database The Select Database window allows user to switch to another database, while FlightConnect Edit is open. The Select Database window will open (after an application is setup in DBManager) regardless of the number of databases are open. Select Database Multiple databases are often necessary when multiple sites are managed by one office. Multiple databases are setup in DBManager.
Setup & Operation File Tabs With the exception of the Database Management tab, all of the tabs in the FlightConnect Edit tool are FlightConnect file tabs. File tabs display the records saved to that file. A record is a unit of the file. For example, one record in the customer file represents one customer, and one record in the fueler file represents one fueler. One row in the table represents one record. The columns in the table represent the record’s fields.
Setup & Operation ACode (Airport Code) The ACode (Airport Code) tab is FlightConnect Edit’s user interface for viewing, creating, editing, or deleting airport codes saved in FlightConnect’s ACode database file. Code: The letter code for the airport. This is a required field. Name: The name of the airport. City: ACode (Aiport Code) The city where the airport is located. State: The state or region where the airport is located. Country: The country where the airport is located. .
Setup & Operation Customer The Customer tab is FlightConnect Edit’s user interface for viewing, creating, editing, or deleting customer information saved in FlightConnect’s Customer database file. This file includes anyone who can receive fuel. Name: The customer’s name. Account: The customer’s account number. Code: A user-defined code assigned to the customer.
Setup & Operation FuelLoc (Fuel Location) The FuelLoc (Fuel Location) tab is FlightConnect Edit’s user interface for viewing, creating, editing, or deleting fueling locations saved in FlightConnect’s FuelLoc database file. Each record in the FuelLoc file represents a location where an aircraft can be fueled. Name: The fueling location’s name. FuelLoc (Fuel Location) Number: A user-defined number assigned to the fueling location.
Setup & Operation SysDefs (Systems Definitions) The SysDefs (Systems Definitions) tab is FlightConnect Edit’s user interface for viewing, creating, or editing FlightConnect system settings and information saved in FlightConnect’s SysDefs database file and applied to the operation of DMS and LCR 600 units. Base ID: A user-defined ID assigned to the fueling operation. Code: Typically, the three or four letter airport code for the airport where the fueling operation is located.
Setup & Operation SysDefs (Systems Definitions) cont’d Enable Options (Cont’D) Enable Options (Cont’D) FuelLoc Tail # FuelType Simultaneous A list box prompt of fueling locations (from the FuelLoc file). The fueler must make a selection before fuelings. A list box prompt of fuel types (from the FuelLoc file). The fueler must make a selection before fueling. MeterSelect A list box prompt of meters (on the refueler). The fueler must make a selection before fueling.
Setup & Operation Truck The Truck tab is FlightConnect Edit’s user interface for viewing, creating, editing, or deleting fueling truck data saved in FlightConnect’s Truck database file. Unit ID: The unit ID code of the LectroCount register on the truck. The LCR Unit ID field in the Truck File of the FlightConnect database must match the LCR Unit ID field in LCRHost’s General Setup (1/5) screen on the DMS and the Unit ID: in the General Setup 1 screen on the LCR 600. Name: Truck The truck’s name.
Setup & Operation FlightConnect Dispatch FlightConnect Dispatch is a user interface where fueling assignments (dispatches) can be configured and dispatched to LCR 600 units in the FlightConnect network. Dispatch can also be configured to send email and SMS alerts to notify fuelers and other personnel that a fueling dispatch has been sent to the LCR 600. FlightConnect Dispatch will not function unless DBManager and FlightConnect Dispatch are both open.
Setup & Operation Email & SMS Dispatch Notification FlightConnect Dispatch includes an email and SMS notification feature that sends notifications to fuelers’ mobile devices alerting them of a pending dispatch. Notifications can be setup to automatically prompt the FlightConnect Dispatch user, upon sending the dispatch, to select the fueler(s) to send the dispatch alert to. Notifications can also be sent manually.
Setup & Operation Automatic Dispatch Notification Configuration FlightConnect Dispatch can be setup to automatically prompt the FlightConnect Dispatch user, upon sending the dispatch, to select the fueler(s) to send the dispatch alert to. When configured, FlightConnect dispatch will automatically open the Choose Email Recipients window, and the dispatch alert will be sent when the OK button is clicked.
Appendix Data Files Overview The first section of the appendix includes examples of ASCII text files (.txt) and tables describing each field. The text file name and the DMS file name are noted in parantheses. Numeric fields must contain a value. If the field does not have a value, use a “0”. If an alphanumeric fields does not have a value, use a blank space “ ”. Field Types The number in the Field Type column represents the maximum number of characters allowed in the field.
Appendix Data Files Fueler File (Fueler.txt - Fueler.slf) “7777”,”1947”,”Richard John MacReady”,”Richard John”,”MacReady”,” rmacready@hrt.
Appendix Data Files System Definitions File (SyesDefs.txt - SysDefs.501) “001”,”ORD”,”O’Hare Airport”,”- - -”,”- - -”,”Chicago”,”IL”,”60000”,”312-654-9632”,”- - -”,”0”,”2”,”2”,”0”,”49”,”0”,”0”,”2”,”0”, ”0”,”0”,”0”,”1”,”0”,”1”,”1”,”0”,”1”,”0”,”0”,”0”,”0”,”0”,”0”, “1”,”0”,”- - -”,”Jet A”,”- - -”,”ORD”,”- - -”,”- - -”,”- - -”,”- - -”,”- - -”,”- - -” Field # Field Name Description Field Type Example 1 baseID ID of the fueling operation. A4 001 2 baseCode Airport code of the fueling operation.
Appendix Data Files System Definitions File (SyesDefs.txt - SysDefs.501) Field # Field Name Description Field Type Example 35 enableRequestVolume Enables the requested volume prompt. N (0-1) 1 36 enableTailNumber Enables the tail number prompt. 0=No or 1=Yes N (0-1) 0 37 defaultComment Default comment to be printed on ticket. A35 --- 38 defaultFuelType Default fuel type being delivered.
Appendix Data Files Completed Transactions File (CompTran.txt - COMP501.trn - CR501201.trn) COMP501.trn - FlightConnect DMS Transaction File - includes edit records CR501201.trn - FlightConnect LCR 600 Transaction File - no edit Records Completed Transactions File (CompTran.txt) Each record in the CompTran.txt file includes the first five field numbers listed in the table. The 5th field signifies the record type. Fields after the 5th field consist of the fields of the record type signified in field 5.
Appendix Data Files DMS Completed Transactions File (COMP501.trn) Field # Field Name Description Field Type Example 1 meter1GrossStart Gross total on meter 1 at the start of the delivery. N ±10 --- 2 meter1GrossEnd Gross total on meter 1 at the end of the delivery. N ±10 --- recordType = 3 (Aircraft Fill) 3 meter1NetStart Net total on meter 1 at the start of the delivery. N ±10 --- 4 meter1Net End Net total on meter 1 at the end of the delivery.
Appendix Data Files DMS Completed Transactions File (COMP501.trn) recordType = 4 (DOT Information) 1 odometer Odometer reading at the time of the DOT inspection. A11 --- 2 engine Yes/No indicating whether or not the engine was checked. N (0-1) --- 3 transmission Yes/No indicating whether or not the transmission was checked. N (0-1) --- 4 clutch Yes/No indicating whether or not the clutch was checked.
Appendix Data Files LCR 600 Completed Transactions File (CR501201.trn) Field # Field Name Description Field Type Example 1 dateTime Date and time record was written. yy/mm/dd hh:mm:ss. A17 --- 2 truck Name of the truck. N16 --- 3 fueler Fueler number. A16 --- 4 baseID ID of the fueling operation’s base. A4 --- 5 recordType Type of record. (See record types in shaded boxes below.) N1 --- 2 unaccounted Unaccounted fuel at the time of the logon.
Appendix Data Files LCR 600 Completed Transactions File (CR501201.trn) Field # Field Name Description Field Type Example 1 averageTemp Average temperature of product during delivery. F5 --- 2 maxPressure Maximum dP during delivery. F5 --- 3 deliveryTotal Sum of totals from all three meters at the end of the delivery. If temperature compensated, will use net; otherwise, gross. N ±10 --- 4 maxPressureRate Flow rate when maximum dP was read.
Appendix Data Files LCR 600 Completed Transactions File (CR501201.trn) Field # Field Name Description Field Type Example 1 odometer Odometer reading at the time of the DOT inspection. A11 --- 2 engine Yes/No indicating whether or not the engine was checked. N (0-1) --- recordType = 4 (DOT Information) 3 transmission Yes/No indicating whether or not the transmission was checked. N (0-1) --- 4 clutch Yes/No indicating whether or not the clutch was checked.
Appendix Data Files Dispatch File (Dispatch.501) 5151”,”10/09/09 12:14:52”,”500”,”5000”,”0”,”0”,”4”,”A310”,”- - -”,”Big Air”,”LAX”,”877”,”Jet A”,”Gate B33”,”ORD”,”N408P”,”Fuel”,”A16 Field # Field Name Description Field Type Example 1 ID Dispatch ID from office computer. N (1-65535) 5151 2 deliveryDue Date and time the delivery is due. A17 10/09/09 12:14:52 3 totalVolume Total volume requested by the aircraft. N ±10 500 4 truckVolume Volume dispatched to the truck.
Appendix Data Files Completed Transactions File (CompTran.xml - COMP501.TRN) yy/mm/dd hh:mm:ss xxxx”xxxxx xxxxxxxxxxxxxxxx xxxx x xxxxxxxx.x xxxxxxxxx.x
Appendix Data Files Completed Transactions File (COMP501.TRN - CompTran.xml) xxxxxxxxx.x xxxxxxxxx.x xxxxxxxxx.x xxxxxxxxx.x xxxxxxxxx.x xxxxxxxxx.x xxxxxxxxx.x xxxxxxxxx.
Appendix Verify SMTP Server Communication To specify a specific SMTP server, the user must provide the SMTP server URL and an allowed sender’s email address. The Dispatch application will then connect directly to the SMTP server using TCP and relay the message using the SMTP protocol.
Appendix Verify SMTP Server Communication (Cont’d) 8) Type a period (.) at the next blank line, and then press ENTER. The server responds: 250 OK 9) Close the connection by typing the following command: QUIT The server responds: 221 closing connection 10) Verify that the recipient received the message. If error event messages appear in the application event log, or if there are problems receiving the message, check the configuration or the communication to the host.
Appendix Establishing Settings and Directories After installing the software, certain FlightConnect Read settings and directories can be adjusted to best suit your operations. • File Conversion Format Determines which file format FlightConnect Read will convert the transaction files into. • Edit Record Validation Setting Sets FlightConnect’s Record Validation feature.
Liquid Controls 105 Albrecht Drive Lake Bluff, IL 60044 (847) 295-1050 SAMPI Via Amerigo Vespucci 1 55011 Altopascio (Lucca), Italy +39 0583 24751 IDEX Fluid and Metering Pvt. Ltd. Survey No. 256, Alindra Savli GIDC, Manjusar Dist. Vadodara 391 770 Gujarat, India +91 2667 662001 Toptech Systems 1124 Florida Central Parkway Longwood, FL 32750 (407) 332-1774 Nateus Business Park Nieuwe Weg 1-Haven 1053 B-2070 Zwijndrecht (Antwerp), Belguim +32 (0)3 250 60 60 Faure Herman Route de Bonnetable B.P.
