Solutions for Service Stations Automation

1. Solutions for Service Stations Automation SIS Technology: Professional Retail Solutions, 2012

2. Service Stations Automation Contents: NEXUS at the Head Office: Structure International Payment Systems NEXUS at the Service Station: Structure Integrated Loyalty Programs Integrated Utility Payments Integrated Payments by Credit Cards Communication with gauging systems NEXUS – Software characteristics SAP Integration - Principles Support & Maintenance Services Implementation Approach Certified Gas Pumps SIS Technology: Professional Retail Solutions, 2012

3. Service Stations Automation • Overview • Architecture • Front & Back Office Functionality • Forecourt and Cash Servers 1. NEXUS at the Service Station: Structure SIS Technology: Professional Retail Solutions, 2012

4. NEXUS at the Service Station - Structure Overview • Overview • NEXUS is a specialized software for petrol and gas service stations. The system covers the main business processes in a petrol and gas service station and follows the Bulgarian Legislation requirements. • Intuitive graphical easy-to- use user interface and automation prevents queues and helps staff. • Locally required developments and peripherals can be easily integrated. • Environment • Nexus software system works in Windows OS environment. The communication architecture is based on Client-Server mode. Security controlled access to a system levels according different user profiles prevent unacceptable data operation. • Software components of the system: • Cashreg – POS application • Cashserver - Server application • ForeCourt Server - Server application • Petrol Station Manager – Back office application • Desckview – Shell for restricted OS access • Communication SAP Interface • Borica Communication Interface • Utility company Interface

5. NEXUS at the Service Station - Structure Overview Pump 1 Pump 2 Pump X Automatic Tank Gauge . . . . . . FORECORT DEVICE COTROLLER RS 232 interface RS 232 interface POS 1 Master POS Utility Company DataBase Server POS 2 Replication of main data Real time transactions LAN interface Local DB Transactions Real Time Transactions POS…. Replication of main data Daily Transactions, customer data, card holders data, card points, etc. Host Data Borika Back Office

6. NEXUS at the Service Station - Structure Front Office Functionality • The NEXUS POS application, named Cashreg, fulfils the basic functionality of a POS petrol station and strictly follows the Legislation. Both the graphical user interface and a touch screen monitor allow easy accesses to the functions of the application, so that it is easy to learn and work with Cashreg, customers are best serviced. • Main POS functionality: • Customer service; up to 5 customer bills at the same time • Administration of the hot court articles at the POS • Fuel prices management • Forecourt activity control • Shift maintenance • POS fiscal, automatic ATG reports and fuel reports • Different security access levels • Different type of payments • Mixed type of payments in one customer bill • Invoice at the pos • Loyalty card payment • Advanced POS functionality: • Advertising movies at customer display • Payment of utility bills • Integrated credit card payment • Sales history at the POS • Real time price and stock information

7. NEXUS at the Service Station - Structure Back Office Functionality • Petrol Station Manager is the application intended for service station manager. The application provides the opportunity for detailed analysis of business processes for the past and present day. The PS Manager consists of several modules. Each of them could be accessed depending of specified user rights. • Manager module • Article data overview • Real time article stock and movement information • Sales, Z-repots, • Analytical fiscal receipt data; • Delivery processing • Request processing • Customer invoices • Incaso processing • Nomenclature module • Nomenclature overview • Inventory module • Inventory management • Reports • Article stock movement report • Fuel reports • Incaso report • Assurance and Vignette sales report • Comparison report: ATG - pump data • Card module • Loyalty card data overview • DKV, UTA sales data report

8. NEXUS at the Service Station - Structure Forecourt and Cash Servers CashServer is the main application that manages the local database and processes the POS, PS Manager and HH terminal requests. Each POS is connected having a separate tread and is recognized on the unique code. It provides a real time monitoring of connected POS terminals, serviced customers, sales and voids, connected PS Managers. It executes different system functions like archiving, reindexing, etc. This application is in charge of diagnostic procedures like consistency check, optimization of the database, etc. The SAP communication interface is integrated in CashServer. Nexus Forecourt Serveris in charge of connecting the Forecourt Device Interface with the POS system. It provides a reliable communication channel capable of handling the continuous information flow coming from the Forecourt. It also sends commands from the POS to the appropriate forecourt device. In order to assure a secure communication between the Forecourt Device Interface and the Nexus POS system a queuing system was implemented. The informationreceived from the Forecourt Device controller is redirected into a queue while the POS has a separate thread. Thisthread is able to read and process commands placed in the queue.

9. Service Stations Automation • General Graph of Head Office 2. NEXUS at the Head Office: Structure SIS Technology: Professional Retail Solutions, 2012

10. NEXUS at the Head Office - Structure CashServer DataBase Server POS Link Communication Module COMM Server Communication Server DataBase Engine Business Gate Head Office application SM Manager CashReg Local DataBase

11. Service Stations Automation • Centralized Customers Database • Clients’ Cards (for additional presentation) • Fleet cards (for additional presentation) 3. Integrated Loyalty Programs SIS Technology: Professional Retail Solutions, 2012

12. Centralized Customers Database Centralized Database Server Answer: Customer’s name, VAT number, address Request: Data for a new client or update of an existing one • Real time processing • Always up-to-date • Easy to find new customer

13. Service Stations Automation • System Architecture • Model of an Utility Payment 4. Integrated Utility Payments SIS Technology: Professional Retail Solutions, 2012

14. Integrated Utility Payments System Architecture KIOSK Network POS Network Internet Back Office Main Database Stand-In Online utility supplier Type of connections: On-line Card Owner Off-line

15. Integrated Utility Payments Model of an Utility Payment Try again or Exit Enter client number Bill request Bill Answer Answer Result Not found or already paid UTILITY PAYMENT SERVER Pay bill Client is found – Bill amount Pay bill Result Not successful Pay bill Result Successful Print Receipt Utility Payment Center

16. Integrated Utility Payments Payment at the Front Office Client’s number provided by the Utility company Bill amount

17. Service Stations Automation • Main principles of EFT integration • Automated Sequence of operations while EFT payment is proceeded 5. Integrated Payments By Debit/Credit Cards SIS Technology: Professional Retail Solutions, 2012

18. Integrated Payments by Credit Cards Main Principles In NEXUS system are implemented two of the four possible interface protocols for integration of EFT terminals with POS systems: Borika and UBB. These protocols cover more than 90% of the installed base of EFT (Electronic Funds Transfer) terminals in Bulgaria. The EFT terminal must be connected to a separate COM port on the POS computer and must be preinstalled with POS-communication capable version of its application software. The integration of EFT terminals into the POS environment allows the cashiers not to type the amount of the transaction in the EFT terminal. They just have to press ‘Card’ button on the Nexus POS interface screen and the amount is automatically transferred to the EFT terminal. Then the cashier swipes the card on the EFT terminal, the customer is prompted to enter PIN and EFT waits for the answer of the authorization center. If the transaction is authorized, the EFT passes a positive answer to the POS and the fiscal receipt is automatically printed. If the transaction is not authorized, POS receives the reason, i.e. ‘Card is blocked’, ‘Not enough money in the card’, etc. and the system waits another try or different Payment method to be applied.

19. Integrated Payments by Credit Cards EFT Payment – Automated operations 1. Request for Approval 2. Request for Amount 3. Send the Amount 4. Read the Card 5. Enter PIN code 6. Authorization 7. Send the result from the transaction 8. Print fiscal receipt or 5. Abort if the transaction is unsuccesful If the answer at step 7 is positive, the EFT terminal sends the type of card used (first four digits of the card number), along with the authorization and transaction codes (for further reference). This information can be printed on the fiscal receipt and/or can be stored in a table in the POS and Server databases. Sending the type of card means simplifying the process of grouping the amounts, due by the different card operators (i.e. Borica, Mastercard, Visa) and determining the exact date of the money transfers. Moreover via the integrated EFT terminals, a new function for the Bulgarian market, the Cashback, can be activated from NEXUS. Example: the customer has to pay 110.94 BGN, but asks to pay 150 BGN. The remaining amount of 39.06 BGN is given by the cashier from the cashdrawer. This reduces the costs for cash handling at the service station and provides one more service for customers, instead of going to an ATM or cash dispenser.

20. Service Stations Automation • Supported international payment systems • Automated Payment Procedure 6. International Payment Systems SIS Technology: Professional Retail Solutions, 2012

21. International Payment Systems Automated Payment Procedure POS Network (Payments) Internet List of issued cards; Black lists; Limits by cards; Vehicles’ details, etc. Authorization requests Authorization Server Main Database Stand-In Details about payments Proceeded (TXT file) Card Issuer Server Type of connections: On-line Off-line

22. Service Stations Automation • NEXUS Certificates issued by BIM • List of pumps licensed to work with NEXUS 7. Certified Gas Pumps SIS Technology: Professional Retail Solutions, 2012

23. Certified Gas Pumps NEXUS sertificates

24. Certified Gas Pumps NEXUS certificates

25. Certified Gas Pumps NEXUS certificates

26. Certified Gas Pumps NEXUS certificates

27. Service Stations Automation • Automated Gauging System • Auto Fuel Delivery 8. Communication with Gauging systems SIS Technology: Professional Retail Solutions, 2012

28. Gauging Systems Automated Gauging System Communication with Automatic Tank Gauge System VEEDER ROOT • - Reads and records values from Automatic Tank Gauge System system for fuel stocks at the end of each shift and at the end of the day • Keeps history of measuredlevels of fuels for future reference

29. Gauging Systems Auto Fuel Delivery Values from ATG System at the beginning and at the end of the delivery

30. Service Stations Automation • System architecture • General Graph of Applications • Security overview 9. System Architecture SIS Technology: Professional Retail Solutions, 2012

31. NEXUS – System Architecture System Architecture NEXUS is a system based on the Client/Server architecture and consists of several different modules which are installed depending on the user requirements and the specificity of business processes managed by the software system. The minimal configuration consists of Cashserver and CashReg modules. Cashserver is our own developed server application, which takes care about data transaction of different client modules. It manages database, transactions, database maintenance, and some system settings. For every client is opened separate port for communications. The opened ports are system settings and are subject of adjustment. These ports are used by default: Cashreg– 700 SM Manager– 6610 System port– 6660 HHT Base port 660 CashReg is our front POS module, which produces the sales transactions at the Front Office of the outlet. It communicates via own TCP/IP based protocol with CashServer. The communication with the server is online and simultaneously the application writes in local data base every single transaction. PS Manager is back or middle office client, which provides the management of deliveries, inventory, stocks, orders, nomenclature etc. It communicate with CashServer via own TCP/IP based protocol. NightRun is a system report module, which works during the down time or in time with low activities in the night and makes some calculation and prepares managerial and operational store reports. It is not connected to CashServer but to Application Manager. It operates independent from Cashserver and only when Cashsever is stopped / no transactions are allowed /. POSLink is communication client, which receives data from Head Office, import the data in the store database and export actual sales data to the main databases in Head office. It communicates and shares resources with CashSever.

32. NEXUS – System Architecture General Graph HHT Server Local DB Cashreg Forecourt Server Central DB CashServer Business gate DB Engine ComServ POSLink SMManager External Back Office Software Night Run Mode

33. NEXUS – System Architecture Security Overview • User accounts • Every system module of NEXUS is accessible via different type of user accounts: • CashServer– there is only one user account for this module –administrator. It is password protected. If the system settings have to be changed, the only way is to be done by administrator. The Cashserver application only accesses the central database. If even unauthorized person try to physically access the server, the changes in the system setting are not allowed if not administrator password is applied. • CashReg: • Administrator accounts. It operates with system settings. Proper password must be entered. • User accounts. Limited user rights – no system settings change. There are different settings for user functionality. • There is no file sharing visibility to the server data, central data base. The communication is made via securitized own TCP/IP based communication protocol. • The system provides protected main cashier account, which can access some critical parameters and is able to permit voids and other special operations. • PS Manager: • Administrator accounts. It is password protected. It takes care about the system and user settings and also about user rights and permissions. • User accounts. The user accounts are password protected. Every user account may possess specific rights given by the administrator account. The rights and permissions include different operations, read/write access, access to different software functionality. • Other system modules: There are always password protected administrator accounts, which possess system settings and functionalities.

34. NEXUS – System Architecture Security Overview • 2. Storage and management of sensitive data • According to the Bulgarian laws there is a special regulation for private data protection. If a trade company wants to operate with private data / person name, address, EGN number - equivalent to social insurance number / it has to be registered by special government commission. • The private data in the system is stored in the database and could be retrieved only by certified user of the system, to whom access have been granted in advance. • Numbers of credit cards are not stored in the system. The header information is stored because of accountancy and reporting purposes. • 3. races/logs and retention period. • NEXUS supports logging of information in two main log files – for the front and for the back office transactions. These files are managed by the CashServer. The names and locations of the log files are user defined. CashServer has an integrated automatic log files back-up procedure, which makes the retention period of the log files unlimited. • 4. Logging of transaction. • There is logging of the transactions for storing data, related to the physical processes in the store – sales, goods deliveries, orders to suppliers etc. The logged information is: • - Type of the transaction, date and time of its start; • - Date, time, duration and result of every single step of the transaction; • - Date and time of the operation’s end and the final result of the transaction execution; • IP address of the workstation which initiates the transaction; • Sales transactions processed at the front office are logged with full details.

35. Service Stations Automation • SAP Integration Model • “Cross” Model • “Direct” Model 10. SAP Integration Principles SIS Technology: Professional Retail Solutions, 2012

36. SAP Integration Principles SAP Integration Model • Based on a standard iDoc technology • Import in SAP • iDoc preparing in outlet – • BackOffice - after each document save in the system • Front Office – periodically on after defined period of time - Automatic activation – periodically after defined period of time system checks for iDoc data via EDI interface • Manually – via standard SAP RFC client • Data processing – in PIPE or SAP R/3 • Export from SAP - Preparing iDoc via EDI port • Notifying POSMaster for dat aavailability: • - via status file • - via command file started on SAP server by EDI interface • Data processing – in POSMaster CashServer module

37. SAP Integration Principles SAP Integration Model Централен офис SAP R/3 4.7 EES 2.00 SAP BW 3.5 BI Content 3.53 Applications Business Content Retail Master Data POS Interface EDI Interface PIPE R/3 Outbound R/3 Inbound BW Inbound Магазин Communication IDoc Converter POS Server Back Office Back Office Label Print Scale POS POS POS POS Back Office Back Office Head office Service Station / Outlet

38. SAP Integration Principles “Cross” Model Files from SAP(DBF , TXT) SAP NEXUS (Head Office) Files from NEXUS ( IDoc type ) NEXUS standard transfer type NEXUS (Object 1)

39. SAP Integration Principles “Direct” Model Import in database Object ( iDoc type )Transfer of exported data Transfer of exported data from Head Office to the objectsfrom Objects to the HO Data Import Object / iDoc / Data export object / iDoc / Data export from SAP(iDoc) Communication Server SIS SAP Import in database Object ( iDoc type ) Transfer of exported data (from Head Office to the objects Transfer of exported data from Objects to the Head Office Data Import Object / iDoc NEXUS Object Communication Client SIS • Main parameters: • Data export from SAP includes following : • Article list; • Nomenclatures; • Suppliers; • Prices and promotions; • Data transfer is done periodically in different time periods according to SAP conception and concerning data archiving and control files model. Time periods may vary according to user requests. Communication software is SIS Technology’s software product. • Data export from objects. Made by NEXUS software, according settings which described software model implemented by SAP, including communication model, ports, production systems etc. Main exported data: • Purchases and goods receiving – immediately after completion of single transaction; • Sales – after specified time period; • Fuel stocks by VEDEER ROOT – after end of the day. Data export object / iDoc /

40. Service Stations Automation • Implementation Approach – Stage 1 • Stage 2 • Stage 3 11. Implementation Approach SIS Technology: Professional Retail Solutions, 2012

41. Implementation Approach STAGE 1 – DEFINITION OF THE PROJECT SCOPE AND SYSTEM REQUIERMENTS • Set up of implementation joined workgroup and nominating project managers; • Performing an initial workgroup training; • Complete installation and implementation of the hardware configuration; • Preparing and accepting the project for • additional functionality; • Start of the Process of licensing the system • by BIM.

42. Implementation Approach STAGE 2 – DEVELOPMENT AND TEST PERIOD • Installation of Head Office and emulation of outlet (customers center); • Development and tests of additional functionality; • Nomenclature initial conversion, SAP communication; • Monitoring of the system performance at a Pilot • service station;

43. Implementation Approach STAGE 3 – PRODUCTIVE START OF THE SYSTEM • Mass Rollover installations over all service stations; • On-site trainings; • Baby sitting; • Workgroup meetings for analyze of implementation process;

44. Service Stations Automation • Support and Service Centers 12. Services SIS Technology: Professional Retail Solutions, 2012

45. Support and Maintenance After the sale, after the promises and the commitments, after you have put your money down, we have the resources to provide the highest quality services and supplies, today and into the future. SIS Technology provides integrated solutions for the customers rather then supplying pieces and parts. With our own staff we provide 7 days a week hardware and software service and support for the clients countrywide. With the expansion of our offices and service facilities, we are now able to offer same day installation on all of our products

46. STRIVE FOR PERFECTION IS THE REASON WE COME TO WORK EVERY DAY! Thank you! George Yankov National Sales ManagerBusiness Park Varna, building B19009 Varnatel + 359 52 702123fax + 359 52 750 507mobile +359 88 7 761040e-mail  g.yankov@sistechnology.comweb WWW.SISTECHNOLOGY.COM Svilen SavchevChairman of the Board of DirectorsBusiness Park Varna, building B19009 Varnatel + 359 52 702110fax + 359 52 750 507mobile +359 888 561351e-mail  savchev@sistechnology.comweb WWW.SISTECHNOLOGY.COM