[Archived] BK DE - Oracle POS Integration (Pre-September)

This page and all pages under it were used to manage the BK DE Oracle Integration project before September 2024. During September we re-organised the project and started managing progress here:

Contents

Context & Assumptions

From an RBI standpoint, SIDES is treated as a POS integration. This is important because we only support one POS integration per restaurant.

Note that SIDES has attempted to integrate with Toshiba, but BK DE shared the integration is not reliable.

  • Delivery fulfillment is done by own drivers. SIDES also takes care of driver management.

    • Team member will assign the order to an own driver. Drivers have a SIDES app which provides delivery instructions.

    • Note that SIDES has built an integration into UberDirect, which will allow 1P delivery orders to be delivered with UberEats drivers. BK DE is currently testing this integration.

Goal

  • All BK DE restaurants currently use Toshiba as the POS and BK DE will replace Toshiba POS with Oracle POS.

    • As part of that replacement, we need to ensure that stores with Oracle POS support Mobile Ordering and Loyalty.

      • The following service modes, POS Integration will be implemented:

        • Delivery

        • Click & Collect

        • Dine In

        • Drive Thru

        • Table Service

Tech Requirements

Architecture

Screenshot 2024-03-05 at 19.33.05.png
SIDES Integration needs to be defined.

 

  1. Oracle POS already has an integration with RBI via the Khumbu middleware using our PartnerAPI.

  2. In Sanity → Vendor Config need to be updated to support the integration:

    1. Create new field Toshiba-Loyalty to support current setup (input offers and rewards) which it’s using as part of the Loyalty Integration with Toshiba, Acrelec and Tillster.

      1. Script to migrate PLUs from the current Partner field to Toshiba-Loyalty including the whole Menu structure (items, combos, modifiers)

    2. Use Partner field to store the Pick Up and Delivery PLUs for Oracle POS.

Integration Oracle Simphony POS

  1. Defined to use the Transaction Services API Generation 2 for:

    1. Order Injection

    2. Price and Product Availability

    3. Heartbeat

Details on Oracle and Khumbu integration

  1. Contact Oracle to activate the Transaction Services API Generation 2;

  2. Create Store ID for both Staging and Production environment;

    1. Create new store on Sanity and set POS as Vendor Partner

  3. Mapping of RBI service modes to Oracle Simphony’s (orderTypeRef)

  4. Loyalty package need to be installed by Oracle following the guideline

Configuration on Partner API

  1. Process to create store (Staging, QA and Prod) on Partner API:

Content Management

In Sanity, on Vendor Configs, all PLUs need to be set on Partner field.

Project Plan

  1. Enable Oracle POS on BK DE - Loyalty Program

    1. For the pilot, focus on enabling loyalty at the front-counter (we will not have kiosk at this stage).

  2. Enable Click & Collect for Oracle POS.

    1. We need to review the approach for Click & Collect service mode.

  3. Enable Delivery for Oracle POS.

    1. We need to decide the approach for Fulfillment provider.

  4. Enable the remaining service modes for Oracle POS.

    1. Dine In

    2. Drive Thru

    3. Table Service

Project Deliverables

 

Status Keys

We use the following status keys across to report progress:

  • NOT STARTED work on this item has not started yet

  • IN PROGRESS work on this item has started and is progressing to plan

  • WAITING development done, awaiting deployment or completion of a dependency

  • AT RISK work on this item has started and is at risk of delaying

  • DELAYED work on this item is delayed, however it is not causing a major impact

  • DELAYED work on this item is delayed and it is causing an impact on project due dates or other dependencies

  • BLOCKED cannot move on this item until a dependency is resolved

  • COMPLETED item has been completed

Stakeholders

Name

Role

Company

Email

Name

Role

Company

Email

1

Stefan Rittelmeyer

Project Manager

Oracle Local Vendor

stefan.rittelmeyer@onlinecorner.eu

2

Ela Bhatnagar

Middleware Integrator

Khumbu

ela.bhatnagar@khumbusystems.com

3

Philipp Hühler

AFL

RBI

phuhler@rbi.com

4

Daniela Corrales

Guest Experience

RBI

dteixeiracorrales@rbi.com

5

Julia

Head of Digital

BK DE

julia.barsch@burgerking.de

6

Melina Rönpagel

Digital Manager

BK DE

melina.roenpagel@burgerking.de

7

Mariann Reitz

CRM/Loyalty Manager

BK DE

mariann.reitz@burgerking.de

8

Lionel

Content Management

David & Martin Agency (BK DE)

lionel.knobloch@davidundmartin.com

9

Anton Benet

Digital Operations

RBI

abenet@rbi.com

10

Silvia Fagundes

CSM Team

RBI

sfagundes@rbi.com

11

Magdalena

Fulfilment Team - Product Manager

RBI

mdlugolecka2@rbi.com

12

Marco

Engineer Manager (Partner API)

RBI

mfernandezpranno@rbi.com

13

Semih

Menu & Restaurant Team - Product Manager

RBI

syildirim@rbi.com

14

Valentina

Loyalty & Offers - Product Manager

RBI

vlopesdacosta@rbi.com

Risks Management

 

LOW

MEDIUM

HIGH

EXTREME

  • Acceptable

  • Ok to proceed

  • As low as reasonably practicable

  • Take mitigation efforts

  • Generally unacceptable

  • Take mitigation efforts

  • Intolerable

  • Seek support

 

 

 

 

LIKELIHOOD

SEVERITY

ACCEPTABLE
Little to no effect on event

TOLERABLE
Effects are felt, but not critical to outcome

UNDESIRABLE
Serious impact to the course of action and outcome

INTOLERABLE
Could result in disaster

IMPROBABLE
Risk is unlikely to occur

 

 

 

 

POSSIBLE
Risk will likely occur

 

 

 

 

PROBABLE
Risk will occur

 

 

 

 

 

 

Risk Management

 

Risk Management

 

Risk

Rating

Description

Mitigation Action

Owner

Enable Delivery with SIDES

HIGH

Today SIDES is treated as a POS integration

  • Change way that we treat SIDES to act as fulfilment partner;

    • Khumbu might be develop an integration with SIDES

  • Likely to move to Deliverect in the future - to discuss with BK DE

@Fagundes, Silvia