Integration Requirements Survey

Instructions

Please fill in the answers below in this description. The intention of this survey is to get us the top-level information about what is possible with this equipment.  Further details will be captured in follow-up conversations. This should help us gather enough information to scope the magnitude of the project up front and help us recommend to the firmware developers what types of data should be in the data dictionary.  These questions are to be asked in an interactive meeting on video if possible.  

OEM partner brands should fill out the following and send it to the Powerhouse Dynamics product team at integrations@powerhousedynamics.com

Project Questions:

1. Partner brand name:

2. Equipment model family:

3. Equipment model name:

4. Project champion at partner brand:

5. Firmware development technical contact:

6. Partner business contact:

7. Please attach a company logo.

8. Please attach a sales/marketing-quality equipment photo and/or logo.

9. Please attach a vector file of a front view of the equipment.

Questions about prior integrations: 

1. Have you integrated products onto Open Kitchen before? 

2. If so, do you want this model to be added to an existing product family on Open Kitchen? If yes, please specify the family.

Questions about the business case:  

1. What is the business opportunity driving your need to connect this model?

2. How many units in 2026 do you estimate having a paid subscription to Open Kitchen?

3. How many units in 2027 do you estimate having a paid subscription to Open Kitchen?

Questions about the product:

1. In a few sentences, please describe what the product does and how it works.

2. What is the competitive advantage of this product to your brand? 

3. Is this a new product or an upgrade to an existing product?

4. If there is an older version of this product, will it be retrofittable for connectivity?

5. What are the biggest challenges your users face when using this product? (energy usage, maintenance, operator training, equipment uptime, etc.)

Questions about the equipment configuration:

1. Does this product have multiple cavities, zones, lanes, or vats, etc, that are tracked through a single controller?

2. Does this product have multiple controllers that will pass data through a single piece of connectivity hardware?

3. Do you intend to support a parallel or alternative connectivity path besides Open Kitchen, whether hardware, software, or other? If so, please provide details.

Questions about connectivity data:

1. In addition to telemetry data, does the equipment generate files that need to be stored on Open Kitchen, such as HACCP or system logs?

2. Does the equipment report when maintenance is due or has been performed?

3. Does this equipment have different operational states that customers may wish to track; e.g. energy savings mode, etc?

4. What event would indicate that the equipment is not being used, assuming there is no fault code present? For example, less than 1 cook cycle per day, etc.

5. Does your equipment track energy, water, or consumable usage totals? If so, please specify.

6. Does your equipment log usage data? If so, is it available at a system level and component level? For example: total time the unit is on (system level), number of relay cycles or hours on a blower motor (component level).

7. Do you want the equipment to allow some parameters to be written remotely?

Questions about connectivity features and benefits:

1. Does this equipment require remote menu or recipe distribution?  

2. Do you want Over the Air (OTA) Firmware Updates supported on this model?

3. Do you want to utilize Menu Builder; i.e., the ability to create, edit, and publish menus and recipes in Open Kitchen? If so, please provide a sample menu file and a detailed menu file mapping spec.

4. What are the most important faults to report on?

5. What insights on this product are important to show at the enterprise level (multiple stores)? 

6. What insights would help the product manufacturer?

7. What cloud connected capabilities do you feel are the most important to have for your first customer?

8. Are there features you are interested in pursuing after the initial product launch, but are not going to be included as part of the initial integration work?