Use cases

Case 1: Invoicing data for a utility company

Automate registration of data for invoicing the delivery of garbage, at a utility company. When a truck arrives, they stop at a gate with a weight built into the road and a camera that points towards the truck. The camera finds the license plate and looks up the customer. Then we save the current weight of the truck, and we open the gate (or notify an operator if the customer was not found or the reading of the license plate failed). When the truck leaves the area, it stops at another gate with a weight and camera. We note the weight difference and update the customers current invoice balance, with the amount of material delivered.

Case 2: Monitoring buildings and health care equipment.

To lower cost we can design a solution using consumer electronics with sensors checking water pressure, electricity usage, humidity, temperature, air flow and many other parameters in buildings and place several small raspberry pi with an zwave/zigbee connector or any other radio link needed, and use simple NodeRED flows for light automation and data collection inside NodeRED. Then a central point we can do reporting and process automation based on data from the devices. By also controlling (and updating) the NodeRED workflow centrally it now becomes easy to finetune the installation across all buildings.

Case 3: Show production KPI´s at a production plant

A production plant producing soap wants to get better and faster data about current productions KPI’s. They install OpenFlow NodeRED on a Siemens SIMATIC IOTxxxx or a Kunbus RevPI that then can read out all information from the machines and then from a NodeRED started inside OpenFlow, expose a dashboard showing current numbers and general status of the production facility, and using custom dashboard management can get easy access to current and historical data about utilization of the equipment.

Case 4: Automate common tasks as a consultant

A consulting firm that helps small and medium sized customers automate mundane tasks creates a library of common processes that is common in that country for the type of customers they serve, and depending on the size and type of task, they deploy a OpenRPA robot and/or a OpenFlow NodeRED instance at the customer site, to assist the users in getting the tasks automated, the consulting firm can continuously improve, monitor and maintain the process from their central OpenFlow and the customers don’t need to run and maintain an OpenFlow installation them self.

Case 5: Maintaining the electricity grid as a utility company

An utility company responsible for maintaining the electricity grid is considered highly sensitive and have strict security policies, and require all software to support working in an environment where you can control weather data is pushed or pulled between specific networks, by chaining multiple separate OpenFlow instances together they can now control the direction and flow of data, while also ensuring each OpenFlow instance able to operate without having contact to any other instances when needed.

As an added benefit they can now easily collect electricity metering data from all households and while saving the telemetry data add ACL that controls who has access to the data. That way, each household can get real time access to their own data, each municipality and power companies can draw both real time and aggregate data for each own region/service area and they can give scientists access to anonymized and aggregated data. Without having to run git ETL jobs that convert all data into a cube/data warehouse, and still maintaining high security and if needed use the on the fly encryption of sensitive data.

Case 6: Collecting data and automizing in a municipality

A municipality who pride themselves as being highly digitalized and ready to try out new things is struggling with trying to maintain data in many different systems from different vendors, they want to take control of their own data and not be dependent on different third party vendors software solutions. Collecting data from buildings ventilation and airflow systems, collecting data from IoT solutions for parking sensors, garbage bin sensors, weather stations etc. needs to be owned and control by the municipality so different departments/magistrates easily can use/report on the data and create workflows that reacts on changes in the data, to automate processes across different domains. By using OpenFlow they can collect data from and interact with any platform and take back control over their data and they can start automating across different platforms and departments/magistrates.

Case 7: Monitor multiple cement factories around the world

A consortium running multiple cement factories in different regions around the world needs a solution that is easy to modify to fit local needs but also makes it easy to monitor and do high level controls from the central headquarters where a 24/7 NOC team is making sure everything is running smoothly. By running one or more OpenFlow installations at each site they can allow each factory to automate and fine tune processes that they find the most useful, while allowing a central OpenFlow connect into each sites OpenFlow and do high level collection of PKI’s and to activate specific generic workflows and processes that is implemented across all plants. This way the management team at each site can choose the level of autonomous automation they want while still complying with HQ’s demands.