Page 58 - RC21 EDGE Summer Issue

This consists of roughly 10 layers, each of which addresses a primary role in the system:
(10) Application: Presentation and organization of data to end-users tailored for a specific task.
(9) Business Intelligence: Low-code ability to create user-facing view into underlying data.
(8) Machine Learning: Automated analysis and insights into collected data.
(7) Data Access: Storing data into an organized and accessible repository.
(6) Data Ontology: Structure for how data is semantically connected and linked. Example is the Digital Buildings ontology.
(5) Device Management: Provisioning and ongoing operation of devices as a secured asset. An example of this is the open-source UDMI device- to-cloud specification.
(4) Networking: On-prem communication fabric connecting devices and services, using advanced platforms such as the open-source Faucet SDN controller.
(3) Device Assurance: Ensures that devices meet with stipulated standards and requirements. As an example, using the open-source Device Automated Qualification (DAQ) framework.
(2) Edge Compute: Managed compute situated on the edge for performant local capabilities.
(1) Device Ecosystem: Collection of digital equipment forming the digital building infrastructure.
The overall system, from top-to-bottom, encompasses application end-goals all the way through the base physical devices themselves. Functioning independently, each
layer provides core value without requiring vertical-stack lock-in, allowing implementers to pick-and-choose which components make most sense for their own needs.
Digital building certification
In the same way BREAAM and LEED revolutionized the sustainability industry, a common “digital building” certification is required to create a measured baseline
between spaces and buildings. It will be difficult to measure on an application level due to the variety; however, if the certification focused on the infrastructure flexibility and digital approach, it would be a foundation that all buildings could aim for and grow beyond as the industry develops.
Summary
To enable a truly smart ecosystem at a citywide (or global) level, the way buildings are designed, built and operated will need to change, with smart ready principles being built into the foundations, and a common technical infrastructure owned and managed by an enterprise.
No one company can solve this problem, the industry needs to work together to build an ecosystem of open standards, tools and products to enable a truly digital infrastructure.
Contributing Authors
Kathy Farrington is a chartered professional
engineer and Technical Program Manager at Google. She leads an internal program to make Google’s buildings smart. She previously worked at an engineering consultancy where
she led a team designing the smart infrastructure of data center, retail and commercial buildings
and residential complexes.
Trevor Pering is a software engineer focusing on physical IoT system design with an emphasis on security, networking, testability, and device management. His career has centered around the intersection of physical
and cyber systems, covering mobile computing, interactive experiences, and now building-oriented
projects. He is the column editor for the IEEE Computer IoT Connections article and active contributor to the FaucetSDN open-source community.
Sabine Lam is a Technology Program Manager on the Real Estate and Workplace Services team at Google. In this role, she focuses on bringing the connected building vision to the forefront of Google real estate
and facilities operations teams, and equips REWS to deliver next generation services and workspaces that
enhance employee productivity. Her responsibilities include collaborating with industry stakeholders to work towards a global strategy for building automation systems across the Google portfolio.
58