iot smart buildings challenge - iiconsortium.orgsolution - when fully deployed - create value for...
TRANSCRIPT
Evaluation Criteria
Community Contribution
How well have the contributors supported the challenge events reflected
in the timeline?
TechnologyHow well does the proposal describe how it will ensure
scalability and realistic rollout in an enterprise environment? Proof of concepts will be given bonus consideration.
BusinessHow well does the proposal
support the outlined use cases, provide value-add for
the partners and deliver innovation?
Submission deadline: August 30, 2019
The submitted proposals will be evaluated according to the following criteria:
Challenge SubmissionPlease use the following slides to make your submission to the challenge
Use this PowerPoint template to submit your proposed concept for the challenge.
Fill out each slide from the following, using the appendix for additional material.
Optional:
▪ Video
• Highly recommended
• Should provide insights into the work you did for the challenge (not simply product advertisement)
• Please attach or embed this into this PPT
▪ Code / PoC (proof of concept) Results
• Optional, but highly desirable
• Include high-level overview in PPT, with link to your repo
About Your Company OR Challenge Team
Umajin Inc.
David [email protected]
Contestant Agreement – David Brebner
www.umajin.com
Use Case Addressed: Smart Metering
Core solution elements
• Battery powered pulse port reader (spoke). This sensor can connect to a pulse port on any smart meter to count and relay in real time the current resource usage.
• Battery powered edge OCR (spoke) for analog and digital meters (gas/power/water). This extremely low cost camera system can be mounted without needing to touch the meter, pointing at the visible display. It is self illuminating and able to read with extremely high accuracy even old fashioned rotating odometer style meters.
• Flexible backhaul (hub) with WLan, LoRa and Sigfox backhaul are supported with flexible data relay and integrated dashboarding capabilities.
• The OCR solution has achieved 99.9% accuracy since trials beginning January 2019
Contributions to the Smart Buildings Challenge
Please describe the contributions your team has made to building the smart buildings community, e.g. by participating in challenge-related hackathons, attending or organizing challenge-related workshops, promoting the challenge actively via social media or presentations, helping to advance the TIOTA framework, helping to advance the IIC reference architecture, etc.
The goal is to initially attend the kickoff in September, and the end user speed dating in November. We will be able to provide working examples of the technology to collect feedback and refine the scope for our potential trial process.
Umajin presented at the IIC event in 2015 at the GE facility in Niskayuna, New York where we first became aware and started working towards incorporating the reference architecture.http://www.davidbrebner.com/?p=1158
Umajin is a leading provider of IOT solutions in the hospitality industry and sees retail and industrial verticals as logically aligned.
Solution Design: Business Perspective
Describe your proposed solution from a business/end-user perspective (e.g., how would the solution - when fully deployed - create value for participants in the ecosystem including owners, operators and tenants of industrial buildings.
The self installable smart readers can be attached to the pulse port on smart meters, or with the camera option be added to traditional meters. These can read power, gas, water or other types of meters as required. A third option is induction sensors on power lines for individual tenants if no meter was installed. These sensors can be self installed by the property facilities management. These solutions are battery powered making installation easy.
The overall result is extremely cost effective and scalable telemetry which can be flexibly analysed at the corporate, building and tenant level.
The backhaul can be relayed to other REST services or analysed and presented in dashboard form using the systems provided.
Solution Design: GTM Perspective
If the go-to-market (GTM) for your solutions involves multiple stakeholder from the challenge ecosystem (e.g. your team, and/or some of the sponsors), please describe:
• The business model which would allow the ecosystem participants to jointly benefit from the solution
- For example: How will we deal with IP which is created in the ecosystems?- Potential legal form and organization: How will the solution be developed, sold and
supported?
Umajin is a platform and technology licencing company and works with many technology and implementation partners. Intel supplies core camera technology for the solution, cloud partners like Microsoft and AWS provide the storage and compute. Systems Integrators and enterprise customers can utilise the Umajin platform to customise and integrate the solutions into their ecosystem and add real time dashboarding.
Umajin also provides hardware reference designs where appropriate, and supports manufacturing partners in building unique IOT elements which can be integrated into solutions.
Solution Design: Differentiation
Differentiation -- how would your proposed solution differentiate itself from others in the market?
Umajin is an expert in high performance machine vision. We helped power the pattern matching systems for the Intel RealSense camera – this capability has been extended to create a unique and extremely accurate (but low power) OCR system to read older meters.
We also have a flexible ‘hub’ which can use multiple protocols to get data back to a central point
Core to the differentiation is that Umajin provides a best of breed multi user editor allowing enterprise customers or systems integrators to collaboratively perform their own customisation and integration very quickly and efficiently.
Solution Design: Architecture
• Please provide an overview of the proposed solution architecture
• Optional- For IIoT: Please use an IIC architecture pattern (e.g. 3-Tier IIoT
architecture) in the Appendix as the “canvas” and map the main elements of your solution onto it
- For DLT-centric solutions with IoT, please use the TIOTA Reference Architecture in the Appendix as a “canvas” and map the main elements of your solution onto it
This is a hub and spoke solution which is able to perform the reading of the meter or sensor, relay this information securely to the local hub, which is then in turn relayed securely to the hosting environment on AWS or Azure. From here a REST relay can be performed, or the time series data can be analyzed and dashboardedin place.
Solution Design: Technology
Describe your proposed solution from a technology perspective. In your description, please describe how IoT and/or blockchain/distributed ledger-based technology will be used in your solution.
Optional: Please describe how your description will leverage technologies provided by the Challenge’s Enabling Technology Partners.
The patented pattern matching allows extremely low cost battery powered units to be self installed and relay accurate readings via a flexible backhaul architecture.
The ability to provide retrofit telemetry of building and tenant level meters adds value directly to the Bosch Energy and Building Technology group goals and services.
Solution Design: Scale
• Scaling up on the technical level: At what scale do you expect the solution to work, e.g. size of property, throughput, transaction times, etc.
• Scaling up on the business and operational level: How would you ensure this?
Umajin has been in operation for over 20 years and supports product and services with partners and customers like Intel, Dell, HP, Sony, PwC, Hilton, Mariott, Hyatt.
Our goal has always been to license technology which partners can implement. This is our core strategy which has enabled us to scale to massive customer volumes.
Potential Issues/Challenges
What issues/challenges might you encounter when creating your solution? Challenges might be related to the underlying technology, integrations, platform development, etc.
We have retrofit meter solutions with the hosting and dash boarding in market.
The challenges would be to work with the site to ascertain the appropriate backhaul and a partner to deliver a suitable number of camera units for the challenge.
Tentative Timeline
• Provide a tentative pilot timeline:
- Key milestone dates
- Proposed date when you believe your PoC will be live
We have deployments in market, so the proposed date will be based around the backhaul choices and finding suitable suppliers for the camera modules and any integration support required.
Appendix
• Attach any supporting materials to this appendix
Field
Backend
Asset
IoT Cloud
BC Middleware
BC Network ❻❺
❹
❸
❷
Asset Layer▪ Examples: Truck, Train, Machine▪ Includes local and remote communication and
processing (on asset, fog)▪ Can include local blockchain clients
IoT Cloud Layer▪ Asset connectivity & FOTA▪ Digital Twin, Asset-related data, event management▪ Enterprise Application Integration
▪ Asset-related ledger entries▪ Peer-to-Peer Middleware for management of BCs▪ Network of compute nodes for BC
Blockchain Cloud Layer
WANA
pp
licat
ion
Lo
gic
Optional (for DLT-centric solution proposals): Mapping against TIOTA Reference Architecture
Blockchain Cloud
❶
Application Logic▪ Distributed across the different layers, e.g. apps + HMI on the asset; digital twin-
based apps in the IoT Cloud; or smart contracts in the blockchain cloud
Gateway
EnterpriseApplications
(ERP, Legacy, etc)
Field
Backend
Asset
IoT Cloud
BC Middleware
BC Network
WANA
pp
licat
ion
Lo
gic
Optional: Architecture Canvas for your Solution Proposal
Blockchain Cloud
Gateway
Please use this slide as a canvas for your solution proposal. This
will help us to compare the different proposals, and to build up a library of re-usable design
patterns.
If you feel there are elements missing of the structure is not
right, please feel free to change it as you see fit.
Optional: Identity and Trusted Lifecycle
Trusted IoT Lifecycle Phases
1. Provisioning2. Tracing
- Chain of Custody- Usage Tracing- External Events- Structural Changes
3. Decommissioning
IoT Identity
1. Assets2. Users
If applicable: Please explain how your solution is using DLTs etc. to enable identity management for the IoT.How is your solution supporting the trusted IoT lifecycle, in the context of the reference architecture?
Lifecycle
Optional: Key/Certificate Lifecycle Management
If applicable: Please explain how your solution is supporting the lifecycle management of keys in a distributed environment (again, using the TIOTA reference architecture)
Key/Certificate Lifecycle Management
▪ Secure generation of keys and certificates ▪ Root of Trust: Keys and certificates
injection at chip wafer level▪ Tamper resistance to ensure protection of
keys in the supply chain and in the field (e.g. via TPM)
▪ Secure key management and forward security: key negotiation, key wrapping, key regeneration, …
IIC 3-Tier IIoT System Architecture
The edge tier collects data from the edge nodes, using the proximity network. The architectural characteristics of this tier, including the breadth of distribution, location, governance scope and the nature of the proximity network, vary depending on the specific use cases.
The platform tier receives, processes and forwards control commands from the enterprise tier to the edge tier. It consolidates processes and analyzes data flows from the edge tier and other tiers. It provides management functions for devices and assets. It also offers non-domain specific services such as data query and analytics.
The enterprise tier implements domain-specific applications, decision support systems and provides interfaces to end-users including operation specialists. The enterprise tier receives data flows from the edge and platform tier. It also issues control commands to the platform tier and edge tier.
The proximity network connects the sensors, actuators, devices, control systems and assets, collectively called edge nodes. It typically connects these edge nodes, as one or more clusters related to a gateway that bridges to other networks.
The access network enables connectivity for data and control flows between the edge and the platform tiers. For example, it could be a corporate network, an overlay private network over the public Internet or a 4G/5G network.
Service network enables connectivity between the services in the platform tier and the enterprise tier, and the services within each tier. It may be an overlay private network over the public Internet or the Internet itself, allowing the enterprise grade of security between end-users and various services.
Mapping Between a Three-tier Architecture to the Functional Domains
IIC Gateway-Mediated Edge Connectivity and Management Pattern
The local network may use different topologies as described below:
In a hub-and-spoke topology, an edge gateway acts as a hub for connecting a cluster of edge nodes to each other and to a wide area network. It has a direct connection to each edge entity in the cluster allowing in-flow data from the edge nodes, and out-flow control commands to the edge nodes.
In a mesh network (or peer-to-peer) topology, an edge gateway also acts as a hub for connecting a cluster of edge nodes to a wide area network. In this topology, however, some of the edge nodes have routing capability. As result, the routing paths from an edge node to another and to the edge gateway vary and may change dynamically. This topology is best suited to provide broad area coverage for low-power and low-data rate applications on resource-constrained devices that are geographically distributed.
In both topologies, the edge nodes are not directly accessible from the wide area network. The edge gateway acts as the single entry point to the edge nodes and as management point providing routing and address translation.
The edge gateway supports the following capabilities:
• Local connectivity through wired serial buses and short-range wireless networks. New communication technologies and protocols are emerging in new deployments.
• Network and protocol bridging supporting various data transfer modes between the edge nodes and the wide area network: asynchronous, streaming, event-based and store-and-forward.
• Local data processing including aggregation, transformation, filtering, consolidation and analytics.
• Device and asset control and management point that manages the edge nodes locally and acts an agent enabling remote management of the edge nodes via the wide area network.
• Site-specific decision and application logic that are performed within the local scope.
IIC Layered Databus Architecture
This architecture provides low-latency, secure, peer-to-peer data communications across logical layers of the system. It is most useful for systems that must manage direct interactions between applications in the field, such as control, local monitoring and edge analytics.
Smart machines use databuses for local control, automation and real-time analytics. Higher-level systems use another databus for supervisory control and monitoring. Federating these systems into a “system of systems” enables complex, Internet-scale, potentially-cloud-based, control, monitoring and analytic applications.
A databus is a logical connected space that implements a set of common schema and communicates using those set of schema between endpoints. Each layer of the databus therefore implements a common data model, allowing interoperable communications between endpoints at that layer.
A Three-layer Databus Architecture
Join Us Now!
• Submit your application before August 30, 2019
• Fill in the Submission PPT Template and email it to:
Kathy [email protected]
orEvan Birkhead