Good Morning

1
Good Morning
2
The NAFEM Data Protocol

• Presentation of
• Proposed RecommendationsData Protocol Steering
  Committee
• August 8, 2000
• Chicago Hilton OHare Airport

3
Introduction

• Michael Perez, Chair
• Dave Vuicich, Vice Chair
• NAFEM Technical Liaison Committee

4
Todays Agenda

• Introductions
• Review of Customer Needs
• Team Decisions -- A Brief History
• Systems Architecture Overview
• The Stack
• Device Profile Methodology
• Target (Customer View)
• Future NAFEM Role / Next Steps
• Afternoon Object Model work sessions

5
Introductions Steering Committee

• Rick Cartwright, Hobart Corp.
• Mario Ceste, F.A.S.T.
• Glenn DeYoung, Prince Castle
• Fernando Esparza, McDonalds Corp.
• Mike Harlamert, CFSP, KFC Corp.
• Jeff Kincer, Henny Penny Corp.

6
Introductions Steering Committee

• Steve Jones, Arbys Inc. / Triarc
• Chuck Maher, consultant
• Leon McNutt, Watlow, Inc.
• Malcolm Reay, Garland Industries
• Mike Thompson, Taylor Company
• Steve Weiss, Weiss Instruments
• Greg Richards, NAFEM Headquarters

7
The On-Line KitchenThe Chain Operators
Perspective

• Mike Harlamert, CFSP

8
Why Is This Important?

• Restaurant operators today face many
  challenges...
• Production and inventory management
• Labor Issues
• Food Safety Concerns
• Asset Management
• Energy Costs

9
What Can We Do?

• We must take advantage of available technology
• Use it to make our restaurants easier and simpler
  to operate
• While microcomputer based control systems have
  improved operations considerably, now is the time
  to take it to the next level
• We must bring our restaurants into the 21st
  century
• the On-Line Kitchen is the way to do it

10
What is the On-Line Kitchen?

• A closed loop, back-of-house network connecting
  all of the production and support equipment to a
  central computer in the restaurant managers
  office.
• Facilitates bi-directional communications between
  the kitchen equipment and the PC based managers
  workstation.

11
The On-Line Kitchen - Schematic
Ice Drink Systems
Drive-Thru POS
Fryers, Ovens, Grills. Etc.
Front Counter POS
Mgrs Work Station
Heated Holding Cabinets
Menu Board Systems
Other Prep Equip.
HVAC Controls
12
What Can the On-Line Kitchen Do for Us?

• Improve Inventory Management Product
  Projections
• Improve Labor Management
• Improve Food Safety
• Improve Asset Management
• Reduce Energy Costs
• Net Better Restaurant Level Profitability

13
Inventory Management Product Projections

• Allows front-of-house to drive back-of-house in
  Near Real Time
• POS feeds actual sales info into projection model
• Equipment feeds finished and in process info
• Model outputs production instructions to kitchen
• More accurate production management
• Improved Quality Product Availability (QPA)

14
Inventory Management Product Projections
POS
Mgrs Work Station
Production Equipment
Holding Equipment
15
Inventory Management Product Projections

• Real time QPA reports - Dashboard
• Green Enough product available within hold
  time
• Yellow Product hold time about to expire
• Red Not enough fresh product available for
  projected demand - cook more now!
• Above restaurant-level reports
• Use as a coaching tool

16
Food Safety

• The On-Line Kitchen can address many food safety
  issues facing our industry today
• Insures correct process set points are used
• Ability to monitor each cooking operation to
  insure proper thermal processing
• Notify manager of anomalies for corrective
  action
• Monitor hold times and conditions
• Maintain records of CCPs for HACCP compliance

17
Labor Management

• Anticipate tasks at optimal times to make current
  labor more efficient
• How much to cook and when
• How much to prep and when
• Monitor work loads within the kitchen
• Balance work loads of staff
• Report exact usage (per time periods) of products
  needing pre-preparation

18
Asset Management

• Service Maintenance
• Detecting performance degradation
• Early warning of failures
• Preliminary diagnostics
• Preventative maintenance scheduling

19
Asset Management

• Tracking Equipment Assets
• Identify specific equipment by location
• Update equipment operating parameters (Auto
  download of process set points)
• Log abnormal operating events (i.e. aborted cook
  cycles)
• On-line warranty registration

20
Energy Management

• Tracking use of energy
• Optimizing energy use
• Reducing labor dependency

21
Challenges

• Lack of a standard communications protocol for
  commercial foodservice equipment
• Compatibility with POS systems
• Connectivity with as much installed equipment as
  possible
• Relatively low installation and per-node costs
• Reliability in hostile environments
• Ability to handle large amount of traffic

22
Why is a Standard Protocol Important?

• Lack of a standard, open protocol will mean
  higher costs, longer development time
• Multiple protocols for various operators
• Multiple software versions for the same
  applications
• We want to be able to specify NAFEM data
  communications compliant equipment

23
The On-Line Kitchen Can Help

• Having our kitchens on-line can address the major
  issues facing our operators today
• Production and inventory management
• Labor Issues
• Food Safety Concerns
• Asset Management
• Energy Costs

24
Team Decisions

• A Brief History
• Rick Cartwright
• Malcolm Reay

25
2/99

• NAFEM-Sponsored Workshop at COEX 99
• Too Many CooksReducing Labor Costs
• NAFEM accepts challenge to create protocol

26
5/99 NRA 99

• NAFEM Technical Liaison Committee acts
• Holds Open Forum
• Sends out Call for Volunteers
• Forms two task forces

27
NRA 99 (contd)

• Task force A Protocol Content
• What we want to say -- Identify the functional
  requirements of the protocol, including minimum
  or base-level information requirements
• Task force B Protocol Format
• How we can say it -- Assess existing protocol
  formats and determine suitability for NAFEM
• Develop glossary

28
7/99

• NAFEM Chain Advisory Task Force (CAT) formed
• Commits support to Task Forces
• Addresses key questions raised in Open Forum

29
9/99

• CAT presentation at NAFEM 99
• The On-Line Kitchen by members of CAT
• Large turnout by chains and OEMs

30
11/99

• Task Force members visit FS/TEC in Dallas to
• Collect viewpoints from seminars and exhibits
• Exchange and information and funnel knowledge to
  task forces
• First full Task Force meetings held in Chicago
• Task Force A Assigned members to gather data for
  information requirements
• Task Force B Assigned members to research and
  evaluating existing protocols

31
1/00

• Second full Task Force meeting held in Orlando
• Task Force A Continues to review the information
  requirements survey, and consolidate data-element
  worksheets
• Task Force B Continues to research and
  evaluating existing protocols
• Task Force C created to work on object models

32
2/00

• Task Force makes presentation at COEX 2000 in
  Las Vegas
• The On-Line Kitchen
• Provides audience update on status of Protocol
  project
• Task Force C holds conference calls
• Discusses application layers, object models,
  connection media

33
3/00

• Third task force meeting held in Chicago
• Task Force A Reviews and agrees upon sample
  object models, checks relevance to all appliances
• Task Force B Selects Ethernet and IP as
  underpinnings of draft Protocol
• Task Force C Further defines interoperability

34
5/00

• Task Force leadership appoints Task Force C to
  become Steering Committee
• Charges it with primary role in developing draft
  Protocol
• All others form Advisory Group
• Task Forces A and B continue on

35
5/00 -- NRA 00

• NAFEM Technical Liaison Committee meets in
  Chicago
• Reviews Protocol Task Force progress

36
5/00 -- NRA 00 (contd)

• First Steering Committee meeting
• Assigns responsibilities for object models (22)
• Further identifies protocol elements
• Full Task Force meets
• Task force members commit to teams, lead by
  members of the SC to complete object models

37
6/00

• Steering Committee meets in Chicago
• Reviews status of Object Models
• Accepts draft definition for Object Models
  presented by Doug Horton
• Reviews research
• Outlines open protocol issues
• Steering Committee meets in Cincinnati
• Proposes Protocol Stack
• Assigns research to resolve roadblocks

38
7/00

• Steering Committee meets in Chicago
• Explores legal and administrative issues
• Reviews research to confirm draft model
• Adopts draft protocol

39
Systems Architecture

• Mario Ceste

40
The On-Line Kitchen - Schematic
Ice Drink Systems
Drive-Thru POS
Fryers, Ovens, Grills. Etc.
Front Counter POS
Mgrs Work Station
Heated Holding Cabinets
Menu Board Systems
Other Prep Equip.
HVAC Controls
41
Supply Chain
Service Provider
Chain Headquarters
THE OUTSIDE WORLD
BACK OFFICE COMPUTER
THE RESTAURANT TODAY
Managers Workstation
POS

HVAC
Grill
Refrigeration /Freezer
Fryer Bank
Oven
Toaster
Coffee Maker
42
Supply Chain
Service Provider
Chain Headquarters
Dial Up
THE OUTSIDE WORLD
BACK OFFICE COMPUTER
THE RESTAURANT TODAY
Managers Workstation
POS

HVAC
Grill
Refrigeration /Freezer
Fryer Bank
Oven
Toaster
Coffee Maker
43
Supply Chain
Service Provider
Chain Headquarters
The Internet
Dial Up
THE OUTSIDE WORLD
Mission Critical Store Server
THE RESTAURANT BACKBONE
Managers Workstation
POS
HVAC
Grill
Refrigeration / Freezer
Fryer Bank
Oven
Toaster
Coffee Maker
44
Supply Chain
Service Provider
Chain Headquarters
The Internet
Dial Up
THE OUTSIDE WORLD
Mission Critical Store Server
THE RESTAURANT BACKBONE
Managers Workstation
POS
HVAC
Gateway
Grill
Refrigeration / Freezer
Fryer Bank
Oven
Toaster
Coffee Maker
45
Supply Chain
Service Provider
Chain Headquarters
Dial Up
The Internet
The Internet
Other
THE OUTSIDE WORLD
Firewall
Mission Critical Store Server
THE RESTAURANT BACKBONE
Managers Workstation
POS
HVAC
Gateway
Grill
Refrigeration / Freezer
Fryer Bank
Oven
Toaster
Coffee Maker
46
ASP Server
Supply Chain
Service Provider
The Internet
THE OUTSIDE WORLD
Router/ Firewall
THE RESTAURANT BACKBONE
POS
Gateway
HVAC
Grill
Refrigeration /Freezer
Fryer Bank
Oven
Toaster
Coffee Maker
47
Supply Chain
Service Provider
Chain Headquarters
Dial Up
The Internet
The Internet
Other
THE OUTSIDE WORLD
Firewall
Mission Critical Store Server
THE RESTAURANT BACKBONE
Managers Workstation
POS
HVAC
Gateway
Grill
Refrigeration / Freezer
Fryer Bank
Oven
Toaster
Coffee Maker
48
Guidelines for Committee Work

• Adopt Protocol which is
• Open
• Uses widely available infrastructure
• Simple
• Cost Effective
• Ready to implement
• Lets not reinvent the wheel!

49
The Protocol Stack

• Leon McNutt

50
The Stack - Physical Layer
10 Base T unshielded Twisted Pair - ONE WIRE
- CO-Existence ARP- Address Resolution
Protocol Extendable Interfaces- RF, IRda, FDDI
ARP
EtherNet
51
The Stack - Network Layer
Internet Protocol v4.0 - Internet Compatible -
Unique Addressing ICMP - Internet Control
Message Protocol - Standard Error Messaging
IP
ICMP
ARP
EtherNet
52
The Stack - Transport Layer

• Targets messages to proper Application Service
• Pairs applications within Hosts by Ports
• Low Overhead

TCP
UDP
IP
ICMP
ARP
EtherNet
53
The Stack - Application
SNMP
BOOTP
TFTP

• Large Volume Transfer
• Downloading
• Programs
• Recipes
• Uploading
• Programs
• Multiple Parameters

Dynamic Addressing
UDP
IP
ICMP
ARP
EtherNet
54
The Stack - Application SNMP

• Polling
• Alarming
• Request response Messaging.
• One Frame One Message
• Interpretability with defined objects

SNMP
UDP
IP
ICMP
ARP
EtherNet
55
The Stack - Proposed Protocol
SNMP
BOOTP
TFTP
UDP
IP
ICMP
ARP
EtherNet
56
Object Model
The way to interoperability..
57
Object Model - Device Profiles

• Dispensing
• Food Prep
• Frozen Desserts Beverages
• Griddles/Grills
• Holding Cabinets
• Hot Beverages
• HVAC
• Ice Equipment
• Ovens
• POS

• Refrigeration
• Security Systems
• Steamers
• Temperature Measurement
• Timers
• Toasters
• Ventilation
• Warewashing
• Waste Systems
• Weighing

58
Object Model - Fryer Profile
59
Object Model - Structure
Profile
Grouping
Attributes
Values
60
Next Steps

• Finalize and refine Object structures
• Build Object definitions from device profiles
• Compile / publish draft standard
• RFC period
• Publish standard 1.0

61
Target Customer View

• Fernando Esparza

62
YES
63
Development Screens

• From a Customer Perspective...
• Open
• Available
• Flexible
• Upgradeable
• Cost Effective
• Internet Ready

64
(No Transcript)
65
Why Now?

• Internet enables and encourages cost-effective
  communication to / from a restaurant
• Offers flexibility to implement different
  solutions based on individual needs
• Challenge now moves to the development of the
  applications
• Finalize the definition of the Object Models
• See what happens with the information

66
Networked RestaurantAdditional Applications

• Inventory Control Management
• POS
• Customer Monitors
• Ordering Kiosks
• Wireless Ordering (Ipass?)

67
Future NAFEM Role

• Greg Richards
• NAFEM Headquarters

68
Potential Key Functions

• Publisher
• Administrator
• Promoter
• Educator

69
NAFEM as Publisher

• Publish Protocol 1.0
• Use website as primary vehicle
• Register users, require Terms of Use agreement
• Provide references/links to related RFCs
• Give Basic implementation guidelines

70
NAFEM as Administrator

• Oversee a volunteer review body or Advisory
  Board for periodic review
• Invite / publish new Object Models
• Publish RFCs on revised Protocol
• Maintain user/subscriber database and
  communication

71
NAFEM as Administrator (contd)

• Establish approved/recommended means of
  conformance self-testing
• Authorize third-party sources for testing
• Establish and administer a compliance mark
  (decal or document) for equipment

72
NAFEM as Promoter

• Wage public relations campaign to encourage
• Compliance among OEMs
• Use by operators in diverse segments
• Recognition of key contributors
• New volunteers to assist with administration
• Utilize NAFEM, industry pubs/sites/events
• Engage allied associations and groups

73
NAFEM as Educator

• Publish implementation guide case studies
• Stage implementation workshops
• Case Studies
• Relevant new technologies
• Third-party exhibits (to defray expenses)

74
Next Steps

• Capture other tasks, ideas
• Establish priorities
• Determine economic model
• Who pays
• From what industry segments
• Advise in budget development
• Help present to secure funding

75
Discussion Period

• Your Comments and
• Questions Welcomed

76
Thank You

• WWW.NAFEM.ORG

77
Object Model Workshop

• Prof. Leon McNutt

78
Object Model Workshop

• AGENDA
• Object Model Limits
• SNMP
• SMI
• MIB
• Going Forward

79
Object Model Limits

• SNMP
• Minimum 483 bytes frame
• Get Request
• Get Response
• Get Next
• Set
• Trap

80
Object Model Limits

• SMI
• Data Types
• Integer
• Octet String

81
Object Model Limits

• MIB
• Object ID
• Syntax
• Access
• Description

82
Going Forward

• Tree Structure
• Object Names
• Data Syntax
• Transpose profiles to Object Structures