Phoenix SQL Fuel Management Software

Phoenix SQL Fuel Management Software Phoenix SQL is OPW Fuel Management System s next generation of FSC card management and tank gauge inventory monitoring software. Phoenix SQL provides a Web-based multi-user browser interface with controlled user access by utilizing Microsoft SQL Server Database. 1

Agenda!! Features & Benefits!! Application Interface Capabilities!! System Architecture!! PC or Server Requirements!! Migration Utility!! Product Activation!! Phoenix SQL Home Page / Modules!! Access Levels!! Reconciliation Report 2

Features!! Browser enabled; supported browsers include Internet Explorer 7 & 8, Mozilla Firefox 3.5 & 3.6!! Server-based and SQL-enabled!! Provides simultaneous multi-user access!! Centralized card database for multiple sites!! Provides communications through modem, Ethernet or direct connection!! Compatible with multiple Operating Systems Windows XP, 2003 Server, Vista and Windows 7!! Export transactions in Excel, CSV and XML!! Multi-level access and security features!! Allows for the creation of Fuel Zones to limit where fleet cards can fuel!! Audit Trail Phoenix SQL administrators can track any actions being performed within the application by any Phoenix SQL user 3

Benefits!! Operates over a server and the content is delivered to users via their browser!! Designed to poll multiple TCP/IP based fuel control systems and tank gauges simultaneously, dramatically reducing data collection times for multiple fuel sites!! Based on OPW Fuel Management Systems Phoenix Premier software package, Phoenix SQL provides all the existing features that exist for Windows!! Migration Utility allows existing Phoenix for Windows users to migrate their existing database into the Phoenix SQL application!! Features an intuitive user interface that allows users to easily navigate between account, card and transaction data screens!! Utilizes back-up and restore, terminal emulation and on-demand transaction polling!! Uses a Microsoft SQL Server Database for storing and managing transaction data, including SQL Server 2005 Express, which ships with the new software 4

Application Interface Capabilities!! Interfaces directly (via RS-232 serial port, modem, or Ethernet connections) with Petro Vend FSC3000 fuel site controllers equipped with R/W Chipkey or Multi-Trucking firmware, and also with System2 fuel site controllers equipped with Standard Card Record, R/W Chipkey, Multi-Trucking, and FleetLink firmware!! Interfaces directly (via RS-232 serial port, modem, Ethernet, or pass-through port connection) between an FSC3000 or System2 FSC to any of the following OPW tank gauges: isite, itouch, SiteSentinel 1, SiteSentinel 2, SiteSentinel 3, EECO 1500 and EECO 2000 series 5

System Architecture!! Phoenix SQL is designed to meet the needs of all our fuel control and tank gauge users. It can be used with a single site with one (or two) PC(s) and can be installed on a single machine and used locally on the same machine or installed on any machine on the same local network. It can also be designed in a way to meet Corporate needs with an architecture that demands separation of the Phoenix SQL components, as shown here: Business User (Remote) Business User (Local) Business User (Remote) Fuel Site Controllers Service Engine Win 2003 Server, Win XP, Windows 7, Win Vista, SQL Server 2005/2008, IIS 6.0, 7.0 Business User (local) HTTP / S 6

PC or Server Requirements!! Runs on multiple Microsoft operating systems: Windows XP, 2003 Server, Vista and Windows 7!! A Windows PC with 1.8 GHz or faster 32-bit (x86) or 64-bit (x64) processor!! At least 2 GB Ram (32-bit) / 3 GB of Ram (64 bit), CD-Rom drive, 4 GB of hard disk space!! Available Ethernet, modem, or communication port for remote or local access to the Fuel Site Controller(s) 7

Component Considerations!! Before performing the actual Phoenix SQL installation, you must first decide where the Phoenix database will reside. Install a free version of Microsoft s SQL Server Express 2005 (provided on the Phoenix SQL installation CD) on the same machine the Phoenix Web services will be installed, or point Phoenix at an existing installation of Microsoft s SQL Server (Standard or Enterprise versions 2005/2008) already installed on a machine within the company network. 8

Component Considerations (continued)!! Next, decide where the Phoenix Service Engine component will be installed. This component must not only have direct access to the SQL Server for database management, but must also have connection-point access to each fuel site that will be managed. This can be done using a serial COM port if direct connections are required; an installed Windows modem for dial-up access; or TCP/IP connectivity using the company LAN. (Due to security issues, public Internet access to fuel site controllers and tank gauges is not recommended).!! Finally, because Phoenix SQL is a Web-enabled application, the PC chosen for Phoenix Installation must have IIS (Internet Information Services) enabled and must be securely managed behind a corporate firewall. 9

Component Considerations (continued)!! Note for Current Phoenix for Windows Users: After installing Phoenix SQL, there is a database migration utility that will import existing Phoenix for Windows data. Once complete, depending on how Phoenix is used, some modifications may need to be made to the imported data with respect to Accounts and their associated cards. 10

Installation Prerequisites Follow these step to install Phoenix SQL on your machine(s): 1.! Exit all other open applications 2.! Insert the Phoenix SQL Installation CD 3.! The Phoenix Installation Wizard should auto-run 4.! Click Next to allow Phoenix to install the prerequisites need to operate 5.! Click Next and follow the Phoenix SQL Installation Wizard process 11

Installation Prerequisites (continued) 6.! At the Select SQL Server Option page, the following options are presented:! Install SQL Server 2005 Express Edition: Select this option if access to a remote installation of SQL Server Standard or Enterprise Edition is not available.! Select SQL Server: Select this option if an existing installation of SQL Server 2005 Express Edition was installed on this machine, or if a remote version is available on the company network. Select the server name from the populated list, enter the appropriate User Name and Password by providing the administrator credentials that give rights to allow a Database to be created. 7.! Click Next, and setup will auto-run the SQL Server install. After all third-party applications have finished installing, click Next to continue. 12

Installing Phoenix SQL Installation of the different options of PhoenixSQL begins at the Software Setup screen. 1.! Start at the top of the list and select Phoenix SQL and click Install 2.! Accept the End-User License Agreement, the click Next 3.! The Installation Type options are as follows: Select one and click Next! Typical: (Recommended) Allow this to be the default installation type.! Custom: For advanced users, if chosen, enter the Website Name/Virtual Directory Name and determine the Destination Path using the Browser button on the right. 4.! Enter the Phoenix Database Name. Click Next. 13

Installing Phoenix SQL (continued) 5.! Create a password (minimum six characters) for the Sysadmin user of Phoenix SQL. Remember this password! Whenlogging into Phoenix SQL for the first time, the user name Sysadmin and the password created must be used 6.! Click Next and follow the prompts to move forward with the installation 7.! The next prompt will ask for the SMTP Configuration From Address. The is the email address that will be seen when the Service Engine and/or Phoenix SQL sends an email.! Configure SMTP using IP Address: Recommended by default if using an operating system older than Vista! Install SMTP Server for Vista or higher version of OS: Recommended by default if using a Vista or Windows 7 operating system! Configure SMTP using Mail Server (any OS): If selected, a Mail Server name is required 8.! 9.! Phoenix SQL has successfully installed! A Phoenix SQL desktop icon will appear Click Close and proceed with the Phoenix SQL Service Engine installation 14

Installing Phoenix SQL Service Engine 1.! If Installing the ServiceEngine component on the same machine, select ServiceEngine and click Install. If Installing Service Engine on a secondary machine, exit the installation and move to that machine, restarting the installation again. 2.! The Installation Type options are as follows: Select one and click Next! Typical: (Recommended) Allow this to be the default installation type.! Custom: For advanced users, if chosen, enter the Website Name/Virtual Directory Name and determine the Destination Path using the Browser button on the right. 3.! The next screen displays/requires the following Database details: Server Name, User Name, Password, and Phoenix Database Name. You must provide this information if you are installing the Service Engine on a separate machine. Click Next. 15

Installing Phoenix SQL Service Engine (continued) 4.! The Email Configuration setup determines who will receive notification when the Service Engine fails or shuts down To: (required field) CC: BC: Subject: Body: 1.!Click Next to install 2.!Service Engine has successfully installed. Click Close. 16

Phoenix SQL Product Activation!! Follow the installation instructions in the Start-Up Guide to install your Phoenix SQL DEMO Disk.!! Whenever Phoenix SQL is installed, it first opens as a DEMO version providing a 60-day, two-site configurable version.!! At any point during your 60-day trial, you may call OPW-FMS Customer Service to purchase Phoenix SQL.!! Once purchased, you can then Activate Phoenix SQL to use with your purchased features. 17

Phoenix SQL Migration Utility!! This utility allows existing P4W application users to migrate their existing Phoenix for Windows (P4W) data into the Phoenix SQL database. Both the P4W and Phoenix SQL databases have to be on the same machine or same network!! User should have access rights to the P4W database!! User will need to create Scheduler events!! User will need to create an address book of the employee information and assign them to the Sites and Accounts as managers!! User should reassign all the Single Global Cards to a new account 18

Running Migration Utility!! Before proceeding with the Migration Utility process, first log into Phoenix SQL and activate the purchased serial number. Without a purchased copy of Phoenix SQL, it is not possible to migrate the existing P4W database. To purchase, login as Sysadmin and go to My Account page to activate. Click Account on the bottom toolbar. 1.! In order to migrate an existing Phoenix for Window database, run the Phoenix SQL installation. At the Software Setup screen, select Phoenix SQL Migration Utility and click Install Note: The P4W database must be located on the Phoenix SQL machine before migrating 2.! Once a database has been migrated in Phoenix SQL, the following changes should be made to ensure correct card management and site setup:! Account/Site Contact Managers: Under this version of Phoenix, an Account Contact and Site Manager must be assigned to each Account and Site respectively from an Address Book that is now available. This data does not exist in the P4W database. Therefore, Phoenix assigns the only available entry of "Tech Support" to each Account and Site configured within the database. It is recommended that Address Book entries be created for these contacts so they can be associated to their respective Accounts and Sites. 19

Running Migration Utility (continued)!! R/W ChipKey Users: If using a System2 or FSC3000 with ChipKey Mileage Reasonability, all defined cards that are R/ W ChipKeys must be edited and the checkbox Is R/W ChipKey is enabled. Maintenance Card Account Users: If the built-in Maintenance Cards account was used to manage cards in Phoenix for Windows and that account contained Single cards, these Single cards must be re-assigned to a new or existing Phoenix SQL account. 1.! Log in to Phoenix SQL. If it is desired to place these Single cards in a new Account, click on the Accounts menu on the left to add a new account. 2.! Once the location that the Single cards will be re-assigned to is decided, select the Global Cards account from the Cards Info page, View by Account dropdown and click Edit. 3.! On the Ribbon Bar, click the Reassign Account button. 4.! In the message that appears, select the Cards Defined as Single and reassign them to a new account 20

Phoenix SQL Home Page & Modules!! Administration!! Sites!! Accounts!! Cards!! Scheduler!! FSC Transactions!! ATG Transactions!! Reports 21

Administration!! The Administration Menu provides options that can be used to create/maintain the Address Book, Groups, Users and Setup-related information used for reference and configuration throughout the application.!! The Administration Menu is comprised of the following links! Address Book System Error Log! Groups User Audit Trail! Users Fuel Zones! System Setup Card Defaults 22

Sites!! The Sites Menu module allows you to enter complete information for all Fuel Site Controller sites that Phoenix SQL will communicate with, in order to manage Cards/Accounts and Transaction data. It will also allow you to configure the Site s tanks and pumps, if the Site has an OPW-model Automatic Tank Gauge System or a 3rd-party Automatic Tank Gauge System that can support the Veeder Root TLS350 protocol. Sites that are configured in Phoenix SQL with Automatic Tank Gauges, will be polling the daily Inventories and Delivery history data, which can be used for reporting purposes.!! If you have a site that does not have Automatic Tank Gauge equipment installed, you can configure the sites tanks and pumps and still have the capability of reporting on tanks. You would be able to input the daily stick inventory readings and deliveries manually into Phoenix SQL.!! This setup will allow you to run reports on this manually entered data into the Phoenix SQL database, so you can manually reconcile your tanks through the Phoenix SQL software. 23

Sites (continued)!! The Sites Menu is comprised of the following:! Site Info! Tanks! Pumps! Terminal Window! Site Utilities! Fuel Provider 24

Accounts!! The Accounts menu provides options that can be used to delineate fuel usage by Division, Building, Organization, Customer or any other Phoenix SQL userdefined grouping that will have its own account cards that will require separate account reporting.!! The Accounts menu is comprised of the following links:! Accounts Info! Deleted Accounts 25

Cards!! The Cards menu provides access to options that can be used to create/maintain any Cards that are linked to the Phoenix SQL system.!! The Cards menu is comprised of the following links:! Cards Info! Card Utilities 26

Scheduler!! The Scheduler Menu allows you to schedule processes such as polling, printing report, card back-up, or any other operation that needs to be scheduled to execute automatically at a defined date and time.! FSC Scheduler! ATG Scheduler 27

FSC Transactions!! The FSC Transactions Menu allows you to view, add, edit, delete, export and reprice transactions.!! The FSC Transactions Menu is comprised of the following links:! Transaction Info! Export Data! Reprice! Deleted Transactions 28

ATG Transactions!! The ATG Transactions Menu allows you to view, add, edit and delete inventory and delivery information for any site configured within Phoenix SQL.!! Sites with a Tank Gauge installed can be polled by Phoenix SQL to collect the data.!! Data polled from a tank gauge cannot be edited or deleted, except a BOL delivery value, which can be entered against polled deliveries.!! Sites configured without a Tank Gauge installed can be edited to manually add and delete inventory and delivery information. Manually added deliveries do not allow BOL data to be entered. 29

Reports!! The Reports Menu allows you to calculate MPGs under Report Utilities, as well as reports for pre-defined topics, including:!!!!!!! Administrator Reports Site Reports Account Reports Card Reports Transaction Reports Product Reports Support Table Reports 30

Group Level Access!! Administrator! The Phoenix SQL Admin user has full access of the Phoenix SQL application and can perform any operation within it! Can create additional users as Administrators of Phoenix SQL! Can create groups with restrictions within the application!! Group Level Access (optional)! Site Level Access! Account Level Access! Site and Account Level Access 31

Site Level Access!"#$%&$'$(%)*$+!,-./($*! 011$**! 0.2"3"*#+45-3%!"#$*% 011-/3#*% 64+.*%!17$./($+% 8!6%9+43*45-3*% 09:%9+43*415-3*% ;$<-+#*% 32

Site Level Access ="$>%011$**?."#%011$** A-%B-(("3@%-+%C41D/<%E%;$*#-+$% 8/315-3* 0((->%0..F?."#FG$($#$%-H%!17$./($+% 643%0..%4%!"#$%>7"17%4/#-24514((I%J$1-2$*%?'$3#* <4+#%-H%#7$"+%2434@$.%@+-/< 6433-#%$K$1/#$%43I%!17$./($+%$'$3#* ;/3F?K$1/#$%!17$./($+%?'$3#* 6433-#%1743@$%43I%!"#$%!$#/<%.4#4,434@$%011$** 643%G$($#$%4%!"#$%"H%"3%#7$"+%@+-/< 643%$K$1/#$%B-((%!"#$L%!"#$%C41D/<%E% 643%1+$4#$%3$>%@+-/<*%1-3#4"3"3@%-3(I%#7$%!"#$%;$*#-+$!"#$*F011-/3#*%#7$I%2434@$ 643%'"$>%8!6%E%09:%#+43*415-3%.4#4%?."#%!"#$%M3H-L%6N,%<-+#%M3H-%43.% J/#%1433-#%0..%-+%?."# *$($1#%8!6%43.%09:%*I*#$2*%#I<$* 643%0**"@3%O/3P4**"@3$.Q%/*$+*%#-%#7$%@+-/<*% #7$I%1+$4#$ ="$>%E%B+"3#%;$<-+#* N<$3%9$+2"34(%R"3.->%#-%8!6%-+% 09: 643%G$($#$%@+-/<*%1-3#4"3"3@%!"#$*F011-/3#*% >"#7"3%#7$"+%2434@$.%@+-/< 643%="$>%943D*%43.%B/2<* 0..F?."#%8!6%E%09:%9+43*415-3* 643%G$($#$%8!6%9+43*415-3* 643%="$>%0..+$**%C--D%?3#+"$* 0((->%0..F?."#FG$($#$%-H%943D*%E% B/2<* 643%;$*#-+$%G$($#$.%8!6%9+43*415-3* 0((->%0..F?."#FG$($#$%-H%8/$(% B+-'".$+%O"31(/.$*%4**"@3"3@%#-%*"#$Q 643%G$415'4#$%4%/*$+ 33

Account Level Access 011-/3#%&$'$(%)*$+!,-./($*! 011$**! 0.2"3"*#+45-3%!"#$*% 011-/3#*% 64+.*%!17$./($+% 8!6%9+43*415-3*% 09:%9+43*415-3*% ;$<-+#*% 34

Account Level Access ="$>%011$**?."#%011$**,434@$%011$** ="$>%S!"#$%T-3$*S 643%0..%011-/3#*%#74#%4/#-24514((I%?."#%011-/3#%M3H-%43.%011-/3#%64+.% J$1-2$%<4+#%-H%#7$"+%2434@$.F1+$4#$% G4#4 @+-/< ="$>%011-/3#%"3H-+245-3 0..%E%?."#%64+.%G4#4 643%1+$4#$%3$>%@+-/<*%1-3#4"3"3@%-3(I% #7$%011-/3#*F!"#$*%#7$I%2434@$ ="$>%64+.%M3H-+245-3 B$+H-+2%64+.U%;$*$3.L%)<.4#$L% C41D/<%43.%;$*#-+$%H/315-3* 643%G$($#$%@+-/<*%4**"@3$.%011-/3#*F!"#$*%>"#7"3%#7$"+%2434@$.F1+$4#$%@+-/< 6433-#%<$+H-+2%43I%14+.% 2434@$2$3#%H/315-3*%O"V$VL% )<.4#$L%;$*$3.L%C41D/<%E% ;$*#-+$Q ;$4**"@3%64+.*%#-%011-/3#*%O$'$3% -/#*".$%#7$+$%@+-/<Q 643%G$($#$%14+.*%4**-1"4#$.%#-%011-/3#*% >"#7"3%#7$"+%2434@$.F1+$4#$%@+-/< 643%="$>%0..+$**%C--D%?3#+"$* 35

Site and Account Level Access!"#$%43.%011-/3#%&$'$(%)*$+!,-./($*! 011$**! 0.2"3"*#+45-3%!"#$*% 011-/3#*% 64+.*%!17$./($+% 8!6%9+43*415-3*% 09:%9+43*415-3*% ;$<-+#*% 36

Reconciliation Report 37

Questions? 3 8

Contact OPW Fuel Management Systems 708.485.4200 info@opwfms.com 3 9