Provisioning

The Powerhouse Dynamics (PhD) Operations team starts the onboarding process for the new equipment

Security

Virtual ConnectWare Module (VCWM) and ConnectWare Module (CWM) use an authentication key when sending equipment data. To get an authentication key, the VCWM/CWM uses a manufacturer x509 certificate. Some equipment IoT development partners have their own manufacturer x509 certificate that can only be used to generate authentication keys for their devices. The management of these keys is done by Open Kitchen.

PhD provides a self-signed certificate that will be loaded on all IoT machines. This certificate will be used to authenticate the IoT machine with Open Kitchen servers to validate that machine is authentic. PhD and IoT development partner will manage this certificate.

X.509 Certificates used for 802.1.X authentication would need to be installed through the IoT machine Controller firmware. PhD does not recommend using 802.1.X authentication for IoT devices as they are usually fixed assets, and are not roaming.

Yes.

If both pass client authentication and send equipment data to Open Kitchen Cloud under the same Device ID, they will be provisioned as one appliance, not two. Data from those two devices would be combined and displayed together.

It should fail client authentication

Network Connectivity

There are three ways to connect to Open Kitchen Cloud: 1) Using Secure Access Point (SAP), 2) Using Automatic Access Points (AAP), 3) Manually configuring WiFi credentials on Controller touch screen

At the moment, this is only possible if using AAP configuration. While it is possible to allow the equipment firmware to manage this, no manufacturer has created a proof of concept.