Who can use the Open Smart Grid Platform?

tool (1)

Are you a producer of smart hardware and don’t want to create your own software and/or apps?

window

Did you create a great app without having any hardware or software?

technology (5)

Or perhaps you have a game changing idea…

road

And we invite all the utilities, smart cities, and (large) infrastructure operators to have a look at the Open Smart Grid Platform

The Open Smart Grid Platform allows you to monitor and control hardware in the public space. With several (generic) functions ready to use, the main benefits of the Open Smart Grid Platform are: scalability & high availability, high security, its  generic design, and no vendor lock-in.

 

Read more about our unique characteristics of the Open Smart Grid Platform

AVAILABILITY & SCALABILITY

Community

The Open Smart Grid Platform is a community. Which means that the community members together work on the requirements you like to develop. The other way around, we encourage you to collaborate with others on their requirements.

 

Endless devices

The Open Smart Grid Platform can connect to a (almost) endless amount of devices. There’s also no limit on the number of applications that control the devices.

The architecture and implementation of the open smart grid platform ensures scalability and availability. It can be deployed to multiple servers, even distributed over multiple datacenters in an active-active setup. Even if one datacenter fails, no data or functionality will be lost.

In a cloud hosted setup it is possible to use autoscaling to automatically add or remove servers on any of the platform layers to scale the platform to the current load and use. By using autoscaling the platform can run with a minimal set of servers, which can automatically be scaled up and down when necessary, thereby reducing the hardware costs.

This setup can also be used to minimize the costs during the phased rollout of smart devices.

SECURITY

Authentication of web-applications:

The platform uses two-sided TLS for the web (applications) to ensure that both parties are convinced of each other’s identity and all communication is encrypted. User organizations are responsible for the identity management and the access on their web applications. For example; applications are provided with a login page, passwords are being coded when saved. And every message towards the platform contains the organization id and is checked with the TLS certificate.

 

Authentication of the platform:

Using an unique platform key the devices authenticate the messages from the platform in order to ensure that devices only receive tasks from a ‘real’ platform. To prevent replay attacks every key message receives a serial number. Both the platform and the devices have a private and public key. This way the platform and devices are certain they communicate with the official platform/device

 

Authorization of organizations

The authorization of the platform functionality is role based. Roles are defined by both the platform functionality and the device functionality. Each role has one or more functions. The rights for each device can be set per device

 

Authentication of devices

All devices are delivered with unique keys. This enables the platform to differentiate between real and wrong devices. Furthermore, devices identify their own unique key. The traffic between platform and devices is signed by these unique keys to:

  1. Ensure the source is correct

  2. Ensure the integrity of the message

GENERIC

The core layer, which holds the generic functionality for device management, firmware management, time synchronization, device installation services, message routing to the correct device protocol, etc. Are applicable for all devices. The platform is designed for multiple applications to be added and for all devices ranging from waste bins, co2 sensors, traffic lights, etc. The protocols, generic functions within the core, and domains can be re-used for every new use-case, application and/or hardware. Therefore, investments in development can be divided over multiple business cases.

NO VENDOR LOCK-IN

The platform is open and independent because it makes use of open standards and it is open source itself. This allows third parties to develop new and innovative solutions. The trade-off is flexibility and freedom. Unlike closed proprietary software, open source software can be altered and extended by any developer familiar with the source code. This grants organizations freedom from “vendor lock-in” and assures long-term viability. A widely adopted oss project is often supported by hundreds of capable development shops that can always be called upon long into the future.

GENERIC FUNCTIONS

The Open Smart Grid Platform has generic functions incorporated that can be of use for several devices in the public space. I.e. firmware updates, hardware updates, time synchronization and workflow engines.

DOMAIN SPECIFIC FUNCTIONS

Furthermore, the Open Smart Grid Platform has several functional domains with specific functions like status updates, remote controls, automated events and filtering of devices.