Back to Top Mobile Nav


To accommodate so many discrete systems and devices, our platform has to be flexible. To grow and evolve over time it has to be extensible. And to successfully analyze, report and guide, it has to be intelligent. Here’s how we’ve built it to achieve these goals.

Privacy is Paramount

Our 12-point privacy policy puts a premium on personal information security. Customers can control what information is stored about them, who can see it, and determine whether that data is anonymized or deleted entirely.

Conforming to the latest standards of privacy set forth by the European Union, our platform honors every person's right to be forgotten. This right is not only enforced in our policy, it's built into the PlanIT UOS™ – supported through APIs specifically designed to irrevocably anonymize user-related data, while maintaining that data’s aggregate usefulness for solution providers.

Scalable Security

For highly scalable situations like those addressed by the PlanIT UOS, security becomes a problem to accurately configure and maintain. Managing sensitive data and complex relationships across myriad devices and users, safely and reliably, poses unique challenges.

We’ve cracked this issue with a policy-driven security mechanism. Security is defined as context-based policy statements in a structured language such as ODRL, and this is compiled to provide platform security settings. This allows a wide range of scenarios to be covered in a small number of statements, as opposed to extensive and risky explicit coding of settings using copy-and-paste.

PlanIT UOS™ Architecture

The Core and Control layers are the heart of the PlanIT UOS, uniting sensors, devices, systems and the users who need to access them.

Detailed Tech PDF


UOS can be deployed to suit the specifics of your environment and operational context, and is equally happy running on the cloud, locally, or as a hybrid.


The UOS Core can run on premise in your own servers or Living PlanIT preconfigured appliances, optimized for remote operation.


The UOS Core is optimized for popular cloud environments such as Microsoft Azure and Amazon Web Services, and can be optimized for most cloud environments.


Sophisticated multinode deployments provide support and flexibility at scale. Extensible, hybrid architectures leverage the benefits in reliability and efficiency of both local and cloud operation.

Planit UOS Deployment

Let’s walk through an example of how the PlanIT UOS Core & Control architecture enables it to scale effectively across many sensors, devices and environments – whether deployed locally, on the cloud, or as a hybrid.

Let's Start


With in-the-box support for hardware developers, our API for software developers, and the ability to integrate closely with partners, we've made implementation as seamless and streamlined as possible. We are happy to answer any questions and here to help get you up and running.


PlanIT UOS offers in-the-box support for tens of thousands of legacy devices. But it doesn't matter how many – it only matters that we support yours. That's why we've made it easy to support devices old and new, with model-driven development and a device-driven toolkit. These make it easy to connect your devices without having to write a single line of code.


PlanIT UOS™ API is enabled entirely by open, cross-platform standards including oData (Open Data Access), OpenID, oauth and ODRL. UOS REST-based APIs are tested against multiple platforms to ensure interoperability. The PlanIT UOS API has three subclasses:


These expose the functionality of the PlanIT UOS Core. This delivers mainstream UOS functions, the ability to interface with sensors, actuators, the control tier and more. The Core API is designed to enable the UOS to serve applications in a reliable, scalable and high-performance way.


These provide application service facilities and shared services, such as application persistence, notification, privacy, security and reporting. Developers have the option of co-hosting their applications with the UOS where appropriate.


These expose functionality enabled by integrated capital equipment at a logical level, abstracting details away from the application, providing a common way for different makes and models of equipment to work in harmony.