ARTS XML- NAFEM Work Team

Transcription

1 ARTS XML- NAFEM Work Team NAFEM-ARTS Protocol Converter Version 1.0 May 11, 2005 Copyright National Retail Federation All rights reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the NRF, ARTS, or its committees, except as needed for the purpose of developing ARTS standards using procedures approved by the NRF, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the National Retail Federation or its successors or assigns. Copyright 2005 ARTS XML. All rights reserved. Page 1

2 TABLE OF CONTENTS 1. References Abstract ARTS Association of Retail Technology Standards NAFEM National Association of Food Equipment Manufacturers Mission Statement Membership Roster Business Justification Mission Scope Use Case Survey Use Case: Store Automation Use Case: Holding Cabinet Scenario: Adding a Grilled Chicken Sandwich Scenario: Inventory Management Track Grilled Chicken Patties Scenario: Tracking Equipment Scenario: Provide Equipment Status Use Case: Beverage Dispenser Scenario: Adding a Promotion and New Drink Scenario: Reprogramming Promotion Scenario: CO 2 Re-supply Use Case: Clamshell Grill Scenario: Programming Clamshell Grill Scenario: Equipment Monitoring Tracking Energy Usage Planned Deliverables/Dates Revision History Issues Glossary endix...10 Copyright 2005 ARTS XML All rights reserved. Page 2

3 1. REFERENCES 2. ABSTRACT Broker Fryer Get/Set NAFEM Data Protocol Protocol Converter ARTS DM Figure 1: NAFEM-ARTS Protocol Converter System Block Diagram The goal is to turn data from foodservice equipment into actionable information for use by applications within the foodservice environment. The NAFEM Data Protocol (NDP) provides a standardized SNMP (Simple Network Management Protocol) based infrastructure for connecting and controlling foodservice equipment (fryers, grills, etc). ARTS provides a method of exposing this information between applications thru the use of a set of standardized XML messages. Furthermore, ARTS provides a datamodel for archiving this information. With the ARTS enterprise view, it is a natural fit for ARTS to extend their work into the foodservice vertical and interface with the NAFEM Data Protocol. ARTS XML s REMC schema is already built around wrapping the data from the NAFEM Data Protocol in the same manner as done have with LonWorks, IFSF and UPOS. With a minor extension, REMC can easily and quickly expose NDP data to the enterprise in standard XML. In fact this is a version 2 consideration. Copyright 2005 ARTS XML All rights reserved. Page 3

4 The ARTS-NAFEM protocol converter will be co-developed and act as the bi-directional translation engine between NAFEM s SNMP based protocol and ARTS XML Kitchen Schema. For example, it will allow the conversion of NAFEM s Notifications to ARTS Event Messages. Conversely it will allow an ARTS XML Kitchen Schema to query the NAFEM based device for things such as its inventory. 2.1 ARTS Association of Retail Technology Standards 2.2 NAFEM National Association of Food Equipment Manufacturers The NAFEM Data Protocol is a standard, non-proprietary technology protocol that enables bidirectional communication of relevant restaurant data between a Host and equipment located in a restaurant kitchen. Figure 2: NAFEM Overview The NAFEM Protocol is designed to make today s restaurants easier and simpler to operate by automating the management processes for inventory, labor, food safety, assets, energy consumption and administrative functions. Process automation, in these areas, will enable restaurant owners/operators, food equipment manufacturers and employees to serve a better quality product to the consumer, resulting in long-term success and overall profitability for the foodservice industry. The NAFEM Protocol was developed in response to a call for action by major U.S. restaurant chains to create the on-line kitchen. Anticipating that a lack of prompt action would allow Copyright 2005 ARTS XML All rights reserved. Page 4

5 independent protocols to emerge from the chains, a qualified steering committee was appointed to design and build a protocol that would enable connectivity, thereby improving the uniformity of kitchen processes, data speed, and costs. Using the NAFEM Protocol to automate restaurant management processes can benefit employees, restaurant owner/operators, and food equipment manufacturers. Restaurant owners/operators can maximize productivity by improving job quality and making the workday more rewarding for employees. Plan the kitchen design around the menu to minimize unnecessary steps/tasks, and simplify processes. Ensure proper exhaust systems and monitor air quality to provide a safe and comfortable working environment. Enable intuitive functional and physical equipment design to help employees make the right decisions about what to do and when, to get the job done right. Equipment manufacturers can monitor industry trends and changes to provide timely equipment solutions. Understand the issues facing restaurant owners/operators and employees, and how equipment is utilized, in order to recommend robust, reliable equipment designs that reduce labor intensity. For example, automate the scheduling of equipment service programs to aid maintenance crews in completing timely repairs. 3. Mission Statement The goal is to turn data from foodservice equipment into actionable information for use by applications within the foodservice environment by leveraging the synergies of NAFEM and ARTS. NAFEM Data Protocol brings the equipment communications standard/applications programmers interface (API). ARTS brings the business information through the ARTS XML Kitchen Schema. Integrating these two elements enables the necessary environment to develop the killer app and eventually prevalent foodservice enterprise resource planning (ERP) systems. 4. Membership Roster Create an outline of the ideal representation for writing the specifications. The composition should include at least: Two technical representatives from NAFEM member companies, i.e., Eran Bernstein, E- Control Systems; William Flynn, FAST/SCK; and/or Leon McNutt, Watlow Controls (requirement: must know SNMP and XML) Two ARTS XML representatives, i.e., John Fluke, IBM; other volunteers (preferably from the chain store group within the NRF) Two foodservice operators, i.e., IT-side, i.e., Keith Dennison or Eric Elwell, YUM! (The group should try to broaden this group beyond YUM!) Solicit middleware vendor input and involvement, i.e., IBM, Microsoft, Sonic Software, etc. Staff Representatives: Richard Halter, ARTS; Charlie Souhrada, NAFEM This might incorporate Members who participate and vote in-person; and Associates who send in recommendations/observations via proxy. Copyright 2005 ARTS XML All rights reserved. Page 5

6 5. Business Justification Provide communication standards that enable complete store operation integration through automation for greater efficiency and effectiveness. Benefits resulting from this integration may include, but are not limited to, the following: Asset Management Consistency Equipment APIs Enterprise Requirements Planning System (ERP) o Energy Management o Forecasting lications o Inventory o Preventative Maintenance/Failure Notification o Remote Monitoring and Control o Safety and Security o Wireless lications Improved Cost Control Increased Customer Satisfaction 6. Mission Scope Identify and develop a NDP to/from ARTS XML Kitchen Schema protocol converter for in-store use. In Scope (assumes the converter is running on an in-store system) Design logical and physical system architecture (extension to Attachment A). Establish a protocol for data conversion between NDP and ARTS XML communication standards Mapping the process for this conversion. Map NDP to the ARTS XML schemas, Request/Response, for example, may map to the NDP Inventory Management Group. Identification/enumeration of missing elements in both protocols. Investigate security concerns (this may require separate levels of security for separate applications) o Should a firewall reside between the equipment and the converter, or the converter and XML? Where does the converter reside on the system architecture? Develop the appropriate certification process. Out of Scope Data ownership identification (deals with whether the data belongs with the equipment manufacturer or the restaurant owners/operators) Enterprise integration Copyright 2005 ARTS XML All rights reserved. Page 6

7 7. Use Case Survey NOTE: These scenarios were derived from a NAFEM Data Protocol Education Workshop. 7.1 Use Case: Store Automation A predictive store operations software package determines they need to have 10 chickens ready for their 11:00 am rush. This information can be combined with the recipe software which says it takes 15 minutes to cook a chicken and with the POS which says they ve sold 5 chickens and the inventory system which reports they only have 7 chickens to tell the fryer to start cooking 3 chickens at 10:45 am. 7.2 Use Case: Holding Cabinet Scenario: Adding a Grilled Chicken Sandwich A foodservice operator is introducing a new grilled chicken sandwich. After the product is grilled it will be held in the mobile, heated holding cabinet before being placed on the sandwich and served to the consumer Scenario: Inventory Management Track Grilled Chicken Patties It is necessary that at any time to know the quantity of chicken patties in the cabinet, when it went into the cabinet and when they must be sold by before being discarded. The proper recording of cabinet temperature must be recorded and reported for the customer s food safety log, which are kept in the unit and also at the regional office. For versatility and cleaning the holding cabinet is moved around the kitchen while in use Scenario: Tracking Equipment Since this is a new piece of equipment the customer must be able to track the equipment installed in all locations by serial number, installation date and revision level. Changes and updates to the software in the holding cabinet is expected since all the holding time and temperature parameters for the chicken patty will not be determined prior to the equipment being installed in the unit. The customer is concerned about service costs updating the equipment and expects you to provide the updating of software either by your local service company or your corporate help desk without a visit to the store Scenario: Provide Equipment Status Most importantly you are being asked to provide status for each holding cabinet at any time during the store s operating hours. Copyright 2005 ARTS XML All rights reserved. Page 7

8 7.3 Use Case: Beverage Dispenser Scenario: Adding a Promotion and New Drink A foodservice operator is introducing a new carbonated beverage in conjunction with a chicken sandwich promotion. Not only is the customer adding the new beverage, but also a family size 2- person drink Scenario: Reprogramming Promotion Unfortunately the marketing dept is still experimenting with the size of the 2-person drink. Some believe 40 oz. Is the desired size while others are lobbying for a 48 oz. size. This means you will be faced with reprogramming the portion sizes during the promotion because they intend to run the 40 oz. Size on weekdays and offer the 48 oz. Version only on weekends. Also it is required that daily tallies be collected by the unit from the equipment on the total quantity of drinks dispensed, by size each day along with an hourly subtotal Scenario: CO 2 Re-supply One issue with the beverage system is that an outside supplier must refill the bulk CO 2 tank during a service visit. The customer is requiring that the supplier automatically come to the unit whenever the CO 2 tank reaches a low level. 7.4 Use Case: Clamshell Grill Scenario: Programming Clamshell Grill Programming the grill is a complicated process and may only be performed by authorized personnel. The clamshell grill features an electric top cooking surface and a gas fired bottom cooking surface. The cooking process is controlled by several settings: top and bottom surface temperatures and cooking time. The temperature settings and cooking time are still undergoing testing, so the customer must have the ability to make both temperature and time adjustments from the manager s office Scenario: Equipment Monitoring Tracking Energy Usage One major concern on this equipment is the high-energy usage compared to the current grill in use. Therefore, the new grill must have a standby setting to setback the temperature setting during non-peak periods. Due to the high energy usage, the customer will be collecting energy use data for comparison studies at the store level and at corporate headquarters. The data must delineate gas and electrical consumption so it can be determined which part of the grill costs more to operate. Copyright 2005 ARTS XML All rights reserved. Page 8

9 8. Planned Deliverables/Dates Primary Goal: May 2006 Introduce NDP/ARTS XML Protocol Converter Interim Steps: Step 1: Finalize MOU between ARTS and NAFEM June 2005 Step 2: Establish Team Membership June 2005 Step 3: Establish First Draft Technical Specifications for the Converter August 2005 Step 4: Stakeholder Review and Signoff Meeting November 2005 Step 5: Establish Final Technical Specifications for the Converter December 2005 Step 6: Introduce Converter Specifications January 2006 Step 7: Communicate Converter Specifications to ropriate Audiences January 2006 Step 8: Implement Conformance Plan April 2006 Step 9: Demonstrate the Protocol Converter and National Restaurant Association Show, Chicago, May 2006 Step 10: Product The NAFEM Show, September REVISION HISTORY Date Name Comments 10. ISSUES 11. GLOSSARY Term ARTS NAFEM NDP Definition Association of Retail Technology Standards North American Food Equipment Manufacturers NAFEM Data Protocol Copyright 2005 ARTS XML All rights reserved. Page 9

10 12. APPENDIX Copyright 2005 ARTS XML All rights reserved. Page 10