1 / 62

UK Discovery Workshop (GT2) 21 st February – 3 rd March 2006

UK Discovery Workshop (GT2) 21 st February – 3 rd March 2006. GSS/DART Solution. GSS:. Proposed UK Discovery Sessions. Seven sessions have been identified for UK Discovery: Technical Architecture, Networks, Interfaces and Security EFT, Fuel Cards, Payment Terminals, Loyalty

tan
Download Presentation

UK Discovery Workshop (GT2) 21 st February – 3 rd March 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UK Discovery Workshop (GT2)21st February – 3rd March 2006

  2. GSS/DART Solution GSS:

  3. Proposed UK Discovery Sessions Seven sessions have been identified for UK Discovery: Technical Architecture, Networks, Interfaces and Security EFT, Fuel Cards, Payment Terminals, Loyalty Fuel Ordering & Receiving, Wet Stock Supply Chain and Dry stock Supply Chain Data Requirements Foodservice Joint Ventures Fiscal and Trading Legal (including Trading Standards requirements and certification requirements)

  4. Session 1- Technical Architecture, Networks, Interfaces & Security

  5. Additional head office systems SAP (DART) head office systems Retalix Host Wetstock Pricing Wetstock Inventory HR Supply Chain/EDI Portal eMaintenance Email Etc. Merchandising Financials MI (POS Keybd maint) Interfaces EPS Interfaces Interfaces Interface Interfaces WAN infra structure Forecourt Devices Interfaces Car wash Dispensers OPPs Tank Monitor Price pole Site infra structure Add’l BOS software Interfaces Wetstock Pricing HR/Timekeeping MSOffice Remote Support Other Site Devices Interfaces • QSR systems • Local cards (e.g. HTEC) • Cameras • Etc. GSS Implementation High Level Conceptual Model Cards FEP(s) Retalix BOS Retalix POS BP Global Template (config and S/W) BP Global Template (config and S/W) Retalix Fuel GSS Site Components Global Template BP Global Template (config and S/W) GSS Integration Work NCT/EPS Components Head office systems Existing site systems

  6. GSS Generic Technical Architecture Diagram

  7. Known Information on UK Technical Architecture Forecourt controllers • Forecourt controllers need to be replaced at Wayne sites (DOMS 5000) need to be installed. This is approximately 45 sites

  8. DART/GSS Interfaces and Data Flows

  9. Known Information on Current UK Interfaces (1) Forecourt Controller: • The combined wetstock inventory information will be output in the standard GSS format in development for the Orion CRD. • Recognizing that the file exists and transporting it to the Orion system will be handled by the infrastructure (IntraNect). No use of the separate DOMS recovery console Price Boards/Poles: • No interface needed to electronic Price Boards / Price Poles

  10. Known Information on Current UK Interfaces (2) Tank Gauges: • Any interface to the Veeder Root TLS tank gauge will be handled by DOMS • Two-way interface between DOMS and TLS-350R. DOMS sends every other sale to TLS so it can do reconciliation/recalibration LPG: • LPG tanks are interfaced to DOMS Component interactions: • GSS platform (probably POS1) will run: • Retalix PumpSrv • Retalix convert layer for DOMS EPS: • Interface from POS to Dionne – need to confirm what Dionne protocol is used

  11. StorePoint Office HEADOFFICE RPO Serial/RF WAN OFFICE DB EFT Services (option) WAN Standard LANTCP/IP Win NT/2000/XP Report Printer (Option) 1 Fries 1 rice 1 Fries 1 rice WAN Local Receipt Printer (Option) EFT Terminal (option) Touch based POS Terminals DART/GSS LAN/WAN: Store Configuration

  12. GSS Template 2 WAN Requirements • The following are ideal state WAN requirements for GSS Template 2: • WAN Bandwidth must support, at least: • Software Distribution of 2-Gig Image to every site within 1 week • Software Distribution of 2-Gig Image to one site within 1 day • Bandwidth to support the above will depend on: • Network Configuration within country • Number of Sites within Country • It is up to each country to establish the Bandwidth required based on the above and additional country specific requirements of the WAN

  13. GSS Template 2 LAN Requirements • The GSS Template 2 ideal state LAN requirements are the following: • Cat 5 network cabling • 100 MG local LAN • GSS will provide the switch required at each site

  14. Point of Sale Back Office System Overview of GSS Template 2 POS/BOS Security Restrictions: There will be no MS Office, email, internet access from the BOS or the POS – The site PC will have to be used for this. The Operating System will be secured so that the users cannot get access to the Start Menu/Desktop or use any function other than the Retalix software Logon: Operating system will auto-logon a secure Operating System user Store user will need to logon to the application using a dedicated user ID & Password

  15. Session 2 - Fuel Cards, Payment Terminals, Loyalty

  16. Known Information on Current UK EPS, Payment Terminals and Loyalty Solution Assumptions: • Nectar Loyalty in place today through Dionne • Retalix does interface to Dionne. Need to confirm that this is the same Dionne protocol as the devices in the UK. • UK will require EMV certification – need to confirm what elements of the solution need to be certified eg. Dionne? Entire EPS solution certification? • UK will require cards certification • Ingenico will be working on Spain, Portugal, and Germany simultaneously • If the UK uses OPPs, they will use the Retalix OSP software being designed for Germany and Portugal • No OPPs today; assumption is that UK would take the same Ingenico solution as Germany and Portugal Questions: • Verify ability of Retalix to reuse the WelcomeBreak StorePoint – Dionne interface.

  17. Proposed EPS Data Flow Fuel PC ISDN communications to the FEPs: • PHH • Atos • Nectar loyalty through Atos • Epay for top ups BOS Retalix PumpSRV Retalix – DOMS Convert Layer POS Dione Sarian Hub DOMS FC module POS Dione

  18. GSS Template 2 Fuel Payment Methods In Scope: • Pay at Kiosk • Fuel transaction started by fuelling in the forecourt and paid in the store • Preset • Transaction where cashier specifies preset GBP amount or volume of fuel to be dispensed • Prepay • Fuel transaction where customer enters store and prepays a specified amount Out of Scope: • Pay at Pump • Fuel transaction where customer pays at an outside payment terminal.

  19. Known Information on UK Forecourt Interfaces (1) Forecourt Controller: • DOMS 5000 will be used to interface to the forecourt devices; all COCO sites will be upgraded from DOMS 2000 • Retalix will send configuration information to the DOMS via a configuration file interface. There will be no site user interaction directly with the DOMS for configuration. • BP UK does not have any sites with more than the DOMS limit of 40 fueling positions • Some double doms sites – how will these be upgraded? LPG: • DOMS has interfaces to the petrol and LPG dispensers used by BP in the UK (LPG tbc) • LPG tank monitors do not have an electronic interface • Separate LPG control box handles LPG leak detection solution as Germany and Portugal

  20. Known Information on UK Forecourt Interfaces (2) Tank Gauges: • All COCO sites have Veeder Root TLS 350 or 350R devices interfaced through the DOMS • All UK COCO sites have automated tank gauges Car Wash: • Car wash is a mix of token based systems and non-interfaced car wash code generators • Therefore a car wash interface is required Electronic Pole Signs: • Separate project looking at electronic pole signs. One site running in Scotland with a manual key pad for changing prices. Additional Peripherals: • No OPPs today; assumption is that UK would take the same Ingenico solution as Germany and Portugal

  21. Proposed Forecourt Interfaces Data Flow POS 1 BOS Retalix PumpSRV Retalix POSPump POS2 Retalix – DOMS Convert Layer Retalix POSPump POSn DOMS 5000 Forecourt Controller Retalix POSPump Petrol & LPG Dispensers (up to 16) OPPs & OPTs (out of scope for GSS) Car Wash Controller (not interfaced) TLS Petrol tanks LPG tanks (not interfaced?)

  22. Session 3 - Fuel Ordering & Receiving, Wet Stock Supply Chain & Dry stock Supply Chain

  23. Overview of GSS Template 2 Fuel Ordering & Receiving • Wet Stock levels are monitored and managed centrally by the 3rd party’s system • Fuel deliveries are “pushed” to the different sites (COCO only) • There is no reconciliation with an order document as fuel replenishment is an off-site activity • Automatic readings will be taken before and after each delivery by the tank monitor • Mandatory Information recorded: • Bill of Lading: Date & Time • Invoice Ref number \ Bill of Lading Number • Delivery Date & Time • Delivery information is sent to DART

  24. Point of Sale Back Office System Overview of GSS Template 2 Fuel Reconciliation • POS EOD sends the BOS: • Pump readings • Tank readings • POS transactions • BOS compares Tank/Pump Readings vs. Fuel Sales and displays warning in EOD dialog whenever a variance is detected • If variance is greater than defined threshold, BOS prevents the EOD process from running until the Fuel Tolerance has been accepted by the Manager • If EOD is completed while overriding the criteria, a file will be created holding information on the tank where variance existed

  25. Overview of GSS Template 2 Fuel Pricing • Wet stock price changes are: • Interfaced from regional fuel system • Automatically posted to the BOS and POS • When a price update is triggered: • All currently idle pumps update immediately, and dispensing (non-idle) pumps wait until they become idle and then change price • Ability to handle different prices on different pumps (i.e. where one POS is idle and one is busy when price update takes place)

  26. Known Information on Wetstock Supply Chain and pricing (1) Assumptions: • The basis of the wetstock price notice lifecycle will be the GSS European template (needs to be confirmed) • Retalix will receive and generate price change notices and confirmations in existing “vanilla” GSS formats. This will require data conversion off site in IntraNect or in the head office systems that send and receive pricing information. • No function currently in place for head office personnel to query retail prices at site • LPG tanks report their inventory to DOMS (contradicts other statements?) • The generic wetstock inventory report file (Orion interface CRD) will be applicable to UK • UK requires current inventory levels by 6 am; tank stock movements by 7am • Invoices for stores are based on deliveries • The head office systems will not send wetstock invoices to the site, and there is no need to import these into the Retalix system

  27. Known Information on Wetstock Supply Chain and pricing (2) Component interactions: • The PriceNet system currently generates recommended prices and sends them to ISP-S • ISP-S generates the site wetstock price notices and sends them through IntraNect to site. • These price changes are assumed to be effective at midnight. • When the price change becomes active, Retalix will generate a price change notification file in its standard format and place it in a directory for pick up by IntraNect. • Retalix currently creates these messages when the change is posted, UK needs the message when the price actually becomes active. • The standard GSS-Retalix features for notifying each POS device of a pending wetstock price change will also be used in UK • Wetstock sales and stock movements will be part of the DGI Retalix Daily Export (DailyTrans) file. This file will be generated at site and sent to DART.

  28. Known Information on Wetstock Supply Chain and pricing (3) Known CRDs: • The Retalix site system expects wetstock price changes to include an effective date and time. IntraNect or ISP-S will have to be modified to add an effective date and time to the price changes. • Possible modifications to IntraNect to handle the wetstock prices and confirmations • Retalix – Generate a price notice when the price is actually changed (currently they generate the notice when the prices are committed in the BOS)

  29. Known Information on Wetstock Supply Chain and pricing (4) Outstanding Questions: • Need to determine what work IntraNect will need to do for • Price notices moving out • Price confirmations coming back • Price inquiry • Business process question: • Should price changes be effective immediately or at a specific time? • Are multiple price changes per day required? • How will the VMI project affect uses of wetstock data? (Owner: Victor de Jong) • New fuels solution going in – FuelSmart: • 1st COCO site will move to this in March with rollout by end of the year • need to understand interface

  30. Retail IP WAN Proposed Wetstock Pricing Data Flow DGI Integration Layer DART SAP Retail BOS Existing GSS Price Import and Export DART SAP BW PHH IntraNect POS Competitor Prices PriceNet POS Price change confirmations Proposed prices ISP-S Price change confirmation notices in the current GSS Europe format

  31. Known Information on UK Wetstock Inventory interfaces Assumptions: • Wetstock delivery records are not sent from the TLS to the DOMS; the deliveries will be recorded by the site manager on the BOS • Fairbanks system is used for environmental reconciliation

  32. POS Retail IP WAN PumpSRV DOMS Convert Layer Underground Tanks TLS Proposed Wetstock Inventory Data Flow Wetstock inventory will be reported as part of the daily reconciled data feed. BOS DART SAP Retail DGI Integration Layer GSS Standard Wetstock Inventory Report (in development) DART SAP BW IntraNect Orion Fairbanks DOMS Wetstock data as part of the unreconciled (midnight) feed

  33. POS Retail IP WAN PumpSRV DOMS Convert Layer Proposed Wetstock Invoicing Data Flow BOS DART SAP Retail All sales and stock movements, including wetstock DGI Integration Layer GSS Standard Export (DailyTrans) IntraNect DART SAP BW Bank Reconciliation data ISP-A Generated invoice Sales data needed to create invoice DOMS ISP-S

  34. GSS Template 2 Ordering There are 2 methods of creating an order: • CAO (Computer Assisted Ordering) • Algorithm based ordering mechanism which recommends quantities of items and generates orders • Create order using CAO – CAO suggests items -> quantities for multiple suppliers • Manual • Create Manual Order – User selects supplier -> items -> quantities. • Create Manual/CAO Order - User selects supplier ->items -> CAO process recommends quantities. Note: • Orders are created in BOS • Orders can be placed via EDI, Phone or Fax dependant on supplier • Stock can also be ordered from other sites – using Transfer In/Out functionality

  35. Overview of GSS Template 2 CAO Ordering • The recommended quantities are based on an algorithm of: • Sales statistics over the past 6 weeks • Minimum stock quantities per item (as defined by Site Manager) • Expected Sales before next delivery (lead time between order and delivery) • Quantity in open orders • Accuracy is dependent on the correct: • Setup of supplier ordering and receiving dates and times • Setup of minimum quantities per item • Stock levels Note: Users will be allowed to revise recommended quantities if required

  36. Overview of GSS Template 2 Receiving • Stock can be received: • Against an Order • Without an Order/ DSD (Van sales) • Receiving against Advanced Shipment Note • Note - This will not be part of GT2, but will be defined regionally • Additional Information: • All suppliers will be defined by DART • Sites can receive additional items against an order • Receiving/Ordering is not allowed for a business day that is already closed.

  37. Overview of GSS Template 2 Stock Adjustments Stock adjustments can be carried out for: • Return to Vendor • Supplied quantities were more than ordered • Substitute items that were keyed into a delivery note but need to be returned • Contract with vendor that enable the return of expired goods • Damaged good were received • Waste • All items that were broken, spilled or expired need to be accounted for and deducted from stock Note - Every wasted item must have a reason code against it

  38. Sales Deliveries Waste Transfer Out Customer Refunds Prepare using ingredients StockCount Store Returns Transfer In Prepare of a new item Overview of Stock Levels • Store activities that Increase and Decrease stock levels:

  39. Overview of GSS Template 2 Stock Counts • 2 types of Stock Count: • Partial Stock Count - Counting by Department, Category, shelf or any sporadic group of items • Full Stock Count - Counting entire store. This will zero any items against which no stock count quantity has been entered. Stock count can be done using RPO, BOS or both. Notes: • Stock count can be done using RPO, BOS or both • No limit to the number of stock counts conducted for an item/for a day • Each stock count overrides the current stock balance for the item • Unable to close Business Day if a Stock Count is still open • Since Post Sales is suspended while a Stock Count Document is open, it is not recommended in the interim to do Ordering, Receiving or Wasting of items in count or Transfers in\out

  40. Session 4 - Data Requirements

  41. Overview of GSS Template 2 Master Data & Site Data • All Master Data (Dynamic and Static) elements are maintained by the central Head Office system in the DART- GSS Template 2 • All Master Data is interfaced in daily update files for new data or changes to existing data Dynamic Data: • Item details • Vendor details • Site details • Promotions Static Data: • Department • Sub Department • Categories • Tax e.g. VAT • Units Of Measure

  42. Overview of GSS Template 2 Item Setup Overview: All items are maintained in the central SAP system (DART) and sent to GSS through an automatic interface process Stores will not have the ability to setup or maintain items locally. However stores will be able to locally maintain certain attributes (e.g. Min/Max Quantity) Stores are able to view item details using the Item Setup dialogue. It is not possible to delete items either manually or through the interface, only set them as inactive Stores will not manage Cost Price in Global Template 2 Prices: Retail prices will be sent to sites up to 5 days in advance Vendor Links: Items will only be linked to 1 vendor (this is the primary vendor in DART) UOM: If an item is sold in multiple UOMs, every sellable UOM will be set up as a different item in DART (without any connection)

  43. Overview of GSS Template 2 Vendor Setup Overview: • Vendor Setup is maintained in the DART central SAP system and sent to GSS by way of an automatic interface process. • Vendor Setup is a dynamic file for the purposes of the DART to GSS interface as changes can occur on a daily basis. Local Attributes: • Stores are able to locally maintain the following vendor attributes: • Order Until Time – the latest time in the day when vendor can receive orders • Order Notify Days – the number of days in advance that an item must be ordered from the vendor before it is delivered • Order Days – the days on which the vendor receives orders • Delivery Days – the days on which the vendor delivers, morning or afternoon can also be specified

  44. Overview of GSS Template 2 Promotions Setup Two types of promotions: TPR (Temporary Price Reduction) Promotions: Items sold at discounted prices in order to promote a new product. These are linked to one item. Combination promotions/Bonus Buys Enables customer to purchase several individual items together at a reduced price. The promotion is triggered by selling one or more item. BOGOF – Buy One item and Get One Free or Multibuy Combo Deal - Purchase items from each of a given number of groups and receive the items for a fixed amount. Mix ‘n’ Match - Purchase a given no. of items for a fixed amount. TPR and combination promotions are automatically activated at the date and time specified in the interface from DART. Stores are not able to set up their own promotions.

  45. Default Receipt Printing: EFT Transaction Return Manual Fuel Correction Pre Pay (Regional) Regions may have different regulations as to when a Pre-Pay receipt can be issued. Some regions require this to be issued after dispensing No Receipt Printing by Default: Sale Pay at Kiosk Pay In Pay Out No Sale (Regional) Void Transaction (Regional) Overview of GSS Template 2 Receipt Printing Note: GSS Template 2 design for receipts is still to be confirmed

  46. Overview of GSS Template 2 Shelf Edge Labels • Shelf Edge Labels are printed through the Label Queue dialog accessible from the BOS, using either: • Price Server Editor (following item changes) • Item Category Management, Shelf Label (on an ad-hoc basis) • Shelf Edge Labels will display Actual Price (not Promotional Price) • One globally defined printer for Shelf Edge Labels & Reports • RPO can be used to ensure the price on the Shelf Edge Labels is correct, items with incorrect shelf edge labels can be imported to the BOS & reprinted • There will only be one shelf edge label template defined for GT2: Template Example

  47. Session 5 - Foodservice

  48. Overview of GSS Template 2 Food Service Item Types: Buy – An item bought from the vendor, and sold at the POS terminal as is. Eg. yogurts, muffins etc Ingredient – An item bought from the vendor and is consumed when creating Make or Prepare items. Eg. slices of tomato, salt, eggs etc Make – An Item that is prepared upon customer order. It has its own unique recipe, comprised of ingredients. Eg. Latte etc Note: DART does not support Prepare Items – An Item that is prepared in advance, eg Pies. Full Cycle: All types of items are setup in DART and downloaded to BOS Buy and Make items are sold at the POS during the day Waste Document is created for all items that were wasted Daily Stock Count document is created at the end of a day including Stock on hand of all ingredient items, Stock on hand of all make items = 0

  49. Session 6 - Joint Ventures

  50. Known Information on Current UK Joint Ventures (1) Safeway: • There are no more Safeway JVs • Ex-Safeway stores are handled differently: • Different categories and pricebook and supply chain – how does this work • Are Safeway stores supported by SAP R1 today? Marks & Spencer: • The UK solution will have to accommodate Marks & Spencer sites • Areas that require further investigation: • Pricebook changes • Accounting changes • MI changes • Merchandise ordering

More Related