Resources > Dataprotocol > History > NAFEM Data Protocol Standard

Background

History

Major U.S. restaurant chains, recognized the potential efficiencies associated by linking individual pieces of commercial kitchen equipment and began working with NAFEM to develop an industry-wide set of rules, or protocol, to allow the exchange of data between independent pieces of commercial equipment and a personal computer.

Working together for an all-industry solution, NAFEM and chain representatives created the NAFEM Data Protocol (NDP), a standard based on existing, open Internet Protocols (IP). The NDP is a non-proprietary technology protocol that enables bi-directional communication of relevant food equipment data between a PC-based workstation foodservice equipment.

Using the NDP to automate management processes, owner/operators, food equipment manufacturers and employees benefit. Kitchens may be designed around the menu to minimize unnecessary steps and simplify processes. Foodservice facility owners and operators can maximize productivity by improving job quality and making the workday more rewarding for employees. Maintenance and service schedules may be automated to create troubleshooting and diagnostic capabilities which, in turn, reduce expensive downtime.

By using NDP, manufacturers gain the ability to allocate research and development resources to other products and services. As a whole, the industry gains the ability to monitor trends, collect information and provide equipment solutions to increase operational efficiency.

The essential framework of the NDP consists of several building blocks called Enterprise Groups that identify specific functions and information related to the exchange of data such as:

• format
• method of communication
• recipient(s)
• timing

These Enterprise Groups are separated into two categories - Administration Enterprise Groups and Application Enterprise Groups. The former are mandatory, while the latter are optional.

Administration Enterprise Groups include:

• Administration: Identifies the piece of equipment to the network.
  
  
• Clock Calendar: Enables scheduling functions by tracking current date and time.
  
  
• Asset Management: Maintains the specific records of each piece of equipment, such as model number, serial number, manufacturing date, and controller software version.

Application Enterprise Groups include:

• Monitor: Defines measurement criteria, such as cook and hold times and temperatures, beverage dispensing system flow and volume rates, as well as safety-related information to meet HACCP requirements. Other information may be related to equipment performance such as compressor run-time, cook cycle and abnormal operating conditions.
  
  
• Maintenance: Schedules equipment preventative maintenance and cleaning based on usage and performance data. Uses preliminary diagnostics to detect performance degradation and trigger early warning of failures.
  
  
• Utility Management: Assists management of energy costs by defining and monitoring all utility related information. This information supplements the Asset Management functions and defines the equipment startup/setback/shutdown functions based on predetermined criteria.
  
  
• Inventory Management: Captures near real-time assets such as minimum levels of supply based on product usage.
  
  
• Notification: Sends data and reports alarms according to predetermined criteria and priorities.
  
  
• Bulk Transfer: Enables managers to send large packets of information between the manager's computer and any pieces of equipment on the network.
  
  
• Security: Establishes the system parameters which allow registered users varying levels of access to operate the system.