Recap and Questions on the “Challenges in the Secure Deployment of Control & Analytics Apps in Distributed Systems” Webinar with IoTium and SkyFoundry

Last month , we hosted the ” Key Challenges in the Secure Deployment of Control & Analytics Apps in Distributed Systems” webinar with speakers from IoTium, Ron Victor and Dhawal Tyagi and SkyFoundry, John Petze. The webinar addresses deployment complexities and security issues starting from hardware root of trust to OS, network and cloud  and application vulnerabilities around IoT and distributed systems. Dhawal also walked us through how to create a  remote management solution which accomplishes one-click deployment for distributed building systems and analytics at the Edge.

Some great questions came across during the webinar. As promised, here is a brief capture of that Q&A.

Q: What is the process of replacing a failed IoTium edge hardware device?

In case of a hardware failure of an IoTium edge device, customer can do an in-field replacement with a brand new device. Orchestrator will automatically transfer the previously defined policies to the new device.

Q: How does the iNodeT connect to the JACEs? Does it come with a NiagaraAX/N4 license?

iNodeT acts as a networking device, like a switch, when connected into the same network as the JACEs. No, it doesn’t come with any Niagara license, customer is expected to procure those licenses independently.

Q: How is Niagara/SkySpark licensing handled and deployed? By the IoTium Orchestrator?

IoTium Orchestrator expects an appropriate license file (if required) while installing any edge service like SkySpark or Niagara.

Q: Is there on-going monitoring to let IoTium or the customer know that the IoTium edge hardware device has failed?

Yes, as part of the service, IoTium constantly monitors every aspect of the network, availability, performance, etc. IoTium’s ops/support team is automatically alerted of any issues related to customer’s network. Optionally, customers can also sign up to receive those alerts.

Q: What are using to poll or collect the IoT data?

SkySpark supports a variety of data acquisition connectors: Bacnet IP, Modbus TCP, Obix, Haystack, SNMP, Sedona, OPC UA, MQTT, SQL, CSV import (manual batch or automated), and a REST API.

Q: How is Niagara/SkySpark licensing handled and deployed? By the IoTium Orchestrator?

The standard SkySpark Everywhere pricing applies to distributed systems whether or not the software is hosted on the IoTium node. The license file for each node is included in the image that the IoTium orchestrator loads to the edge device.

Q: How scalable are the Skyspark collectors and orchestrator, i.e. rule of thumb how many IoT edge devices can be managed.

As far as SkySpark is concerned the amount of data that can be brought into an individual “node” scales with the capacity of that node. For example, on a node that is in the horsepower range of a Beagleboard Black you can easily support 100-200 points. We have people running 100 points on a Raspberry Pi as another example. With more horsepower (CPU and memory) the node can handle more. In server level applications we recommend 50,000 points as an upper limit is live data collection is being used. If data is being batch loaded we have systems running with 250K points on a single server uploading 27M data samples per day.

Orchestrator is designed to be a horizontally scalable cloud native service. It automatically scales on a need basis to millions of end points.

If you didn’t get a chance to watch the webinar, you can checkout the replay here:

Discover more

  • Schedule a demo and see how IoTium and SkyFoundry can simplify connectivity and migration of building automation solutions between on-premise and the cloud today!
  • Download our solution overview for building automation system here.