1. KUBE 2 – Automated Brand Content Launch
Production Ready Features and Functionality

2. Automated Brand Content Launch - Concept
By simply waving a Brand specific“Badge”, Brand teams can now launch Brand specific content on the Kube stations within Seconds.
Eliminates the need to spend up to 10 minutes to pull up the right content on the screens
Same Badge can work across all the Kube stations
Content is not just limited to Social, it could be Sales, Finance, Innovation, etc..
Any web enabled content can now be configured in the “Badge”
The “Badge” can be configurable with the Custom Content - anytime, on-demand, as needed basis
“Badge” is printed with Brand Logo and Kube Logo
Version 1.0
12/20/2016

3. How it Works?
USB 2.0/3.0
USB 2.0/3.0 4 1 5
Local DB
NFC Application
USB 2.0/3.0 3 2
RFID Card Reader
RFID Card
Brand Person
Windows application capable of detecting RFID card activity is installed on the PC
User will be given an RFID access card with a unique code tied with their Brand
User swipes the card at the beginning of a Kube session – using the RFID card reader attached to the Kube
The branded content URLs, User Login information necessary to launch the Brand Content is pre-configured in the Local DB
The Application launches the Branded Content on the existing Chrome Browsers that are already open

4. Components of the System
Hardware
Windows PC
RFID Card Reader
Software
Chrome Browser
“Automated Content Launcher” Windows Application
Local database
Function
“Automated Content Launcher application is in the background, waiting to detect the “Badge” swipe by the Card Reader attached to the PC
Detects the ID from the badge, and pulls up the URLs associated with the ID
Detects open Chrome Browser window and launches the URLs

5. Brand, Content, Activity Management Dashboard
Brand/Content Management
Issue a New Badge / Remove a Badge
Brand Name assigned to a Badge or Removed from a Badge
Assign/Modify Content to a Badge
Assign new URLs to the Badge or modify existing URLs
User Activity Tracking and Reporting
Activity Tracking
Kube Name, Date, Time, Brand Name (and URLs) are tracked
Activity Reporting
Experience Planning Team can view the Activity Report using a web based URL (with secure access)

6. High-level System Architecture`
Admin Assignment of KubeId, UserId, brand Association and URLS
Badge Activity Tracking
Master Database
User Activity along with brand logo upload to database
Badge ID / Brand
Assigned
Re-assigned
HQ Snacks, Kube
Management
Brand Team
Badge ID / Brand
Assigned
Administrator
Merch Mart Kube
Badge
Content
Activity
Re-assigned
Re-assigned
High-level System Architecture
Badge ID / Brand
Assigned
KLA Kube

7. Next Steps and Timeline
Production-ready application development
3 to 4 weeks for application development, alpha test, printing on the Badge
Beta Test
We need all Kubes in HQ to participate in the Test
How many Brands we will be launching during Beta Test, who is the designated person for each brand that can provide us the final URLs to configure for the Badge? Brand Logos, etc..
Timing and schedules for the roll-out and testing
2 weeks testing, after successful testing, Showcase to the Leadership
Production Roll-out
Create a list of Kube stations to roll the production system for Production Launch Approval
Acquire the hardware, deploy and test
Hyper-care Support
Provide high-touch support service for the first 2 weeks of the production roll-out
Maintenance and Support
Hand-off to Maintenance and Support (Workplace Solutions Team)