iot smart buildings challenge · -mongodb-cloudsql-google bigquery-workflow server-event processing...
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
Please submit on this slide:• Company name: Thing Technologies GmbH• Submitter name: Momo Allan and Florian Schiebl, [email protected] and [email protected]
• Identify who agreed to the Contestant Agreement, if different from this submitter• Link to company home page: www.thing-it.com• Who is representing which part of this submission (if it is a joint submission): no joint submission
Use Case Addressed – (3) Smart Automated Building
Make all technical equipment controllable within the center in order to create a system for reducing energy consumption. Some elements must be fitted with sensors and smart units. In addition, external data, such as weather data, are to be integrated
• Technical center management is driven by local teams, mostly no central data analysis• Significant difference existing between
- Best performing centers• Anticipate trends and outside factors• Early detection of and response to issues• Well maintaned equipment
- Worst performing centers• Overheat and subsequently overcool• Detect issues too late• Equipment operates outside of efficiency assumptions
è Different types of suitable sensors from different vendors gets integrated in central platformto increase transparency and comparison to detect and improve worst performing centers. Foster standardization.
Use Case Addressed – (3) Smart Automated Building
Make all technical equipment controllable within the center in order to create a system for reducing energy consumption. Some elements must be fitted with sensors and smart units. In addition, external data, such as weather data, are to be integrated
Reduce Energy Conumption
Save lighting energy Sensors measure lumen and activity in the space and adjust LED light lumen or automatically turn on/off lightsMobile app allows to individually adjust lights in certain rooms
Save heating energy Weather forecast data, sun light status, window status, shades status and control, historicutilization data and live activity data is combined by central platform to control heating systemautomatically -> low heating/cooling per night, pre-heating/cooling in the early morning, on-demandheating during the dayPush notifications get sent on mobile to close left open windows by staff in near distance
Save aircon energy Sensors based data about window status, utilization in space, room temperature, air quality isgetting combined by central platform to adjust aircon system to current need.Mobile app allows to individually adjust aircon in certain roomsPush notifications get sent on mobile to close left open windows by staff in near distance
Central platform initiates based on sensor data thesholds automatically events in stream processing, kick-offworkflow & task list on mobiles or push notifications on mobiles
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.
Communities EngagementsEvents, fairs, conferences Our founders are often invited as key note speakers to Smart Building
Events;
Pilots and installations +40 installations in Smart Office Buildings, university campus, ECE shopping malls, convention centers and FM labs to measure impact ofdigitalization
Building partner community Getting together divers HW vendors, system providers, asset ownersand FM providers in our Thing-it platfrm and in many projects to design seamless end-to-end processing
Solution Design: Business Perspective
TENANT
• Increased efficiency (e.g. office space usage, collaboration, communication)
• Access to new or better services
SERVICE PROVIDER• Expanded business by service offerings
into facility
• Seamless customer access for on-demand services
PROPERTY MANAGER• Empowering sustainability and building health
• Facilitation of energy management, incident management and transparent maintenance
FACILITY MANAGER• On-demand services through sensor measurements, e.g. smart cleaning and
predictive maintenance
• Efficient operations through process management
Integrated smart building platform adds value for all stakeholders along the property value chain
Lower operational
costs
Increased Property Value
Increased income> Traditional rent> New business
models
ASSET OWNER
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?In our platform we own finished products and integrated systems. If furthermore, we develop
a specific product or service with a client (ECE), we then contract an exclusivity agreement forthe application with this client. Of course we are also open to founding a cooperativepartnership for the purpose of marketing.
Solution Design: Differentiation
Project Efforts*
*Costs/Skill Set, Risk, Time-to-Market, Maintenance and Operations
Configuration instead of Coding
COMMUNICATION AND BOOKING
Wiki, PinboardDocuments and MediaChatEventsRoom/Equipment BookingPush Notifications
LOCATION/TRACKING/OCCUPANCY
User Location(if opted in)Equipment LocationRelative Position Userand Equipment (e.g. Cleaning)Heatmaps (Occupancy etc.)Moving Trails
ACCESS CONTROL
App-Access to Assa Abloy, BlueId, Kisi, Dorma KabaElevator ControlParking GatesLockerDynamic Entitlements viaProcesses
BUILDING CONTROL
HVACTransport (Elevators etc.)LightingShadesVisualizationIrrigation
FACILITIES MANAGEMENT
Incident ManagementInstallation and MaintenanceTeam Position and Work OrdersWork Control/MonitoringPreventive Maintenance
Co -Working
FacilitiesManage-
ment
Access Control
Parking
Energy Manage-
ment
BuildingControl
Assisted Living
Checkin/CheckoutDelivery Metering/
Billing
SecurityIncidentManage-
ment
BUSINESS PROCESSESEXTERNAL SYSTEMSCAFM, ERP, Payment
Systems, Parking Space Management, Accounting,
Asset Management
DEVICES / IOT-PLATFORMS
HVAC, Transport, Light, Access Control, Tracking,
Garbage Management/Hygiene
MOBILE USERTenant, Administration, Technical Team, Service Provider, Patient, Guest
THING-IT APPROACH EXEMPLARY USE CASES
The broadest central digitalization platform in the market, HW agnostic, with own central app, focus on end-to-end processing
Solution Design: Architecture
• The Thing-it PROD cloud platform is a conglomerate of cloud services (Thing-it Cloud Server) operated on AWS and Google
• The services follow a Micro-Services Architecture which allows for a multi-tenant scale-out.
• A tenant is a digital mesh in the Thing-it portal terminology and one or more sites. A mesh is structured in - Users, roles & entitlements
- BIM data (sites-buildings-floor etc.)
- Devices, Assets and Equipment
- IoT Data
- Content / Information
- Communication Channels
- Workflows & Business Processes
- Events & Rules
- External Runtime Environments
- Dashboards
• The mesh structure can be configured and managed in the Thing-it portal using dedicated management interfaces.
• The Thing-it Portal is connected to Thing-it cloud server and is a Angular CLI Web App – i.e. static web content also served from thing-it.com.
• Standards can get set across all sites and buildings in the mesh but each site can get individually configured in parallel
• BIMServer is a Java-based WAR-deployable file server which allows to access and to update BIM data
[thing-it] Cloud Instance
Device Integration(BACnet, KNX, Bluetooth, Wifi, Beacons, LoRa etc.)
Process Integration and Task Management(Documents, REST, UI)
Asset Management User(User, Entitlements)
BIM Devices
Predefined Packages(Information, Communication, Booking, Location, FM,
Parking)
Smart Energy
Processing
Smart Cleaning
Processing
Smart Mainten-
anceProcessing
[thing-it] Core(Configuration, Dashboard
etc.)
Devices/IOT PlatformsExternal Systems
Portal
3rd Party(z.B. Anomaly Detection,
Energy Rules)
App
Kiosk, Digital Signage
Customer
O365
ECE-GLT
Solution Design: Technology
• The Thing-it PROD cloud platform is a conglomerate of cloud services (Thing-it Cloud Server) operated on AWS and Google
Cloud Platform:
- NodeJS Services
- MongoDB
- CloudSQL
- Google BigQuery
- Workflow Server
- Event Processing Cloud Services
• The services follow a Micro-Services Architecture which allows for a multi-tenant scale-out.
• REST endpoints can be securely retrieved in the Thing-it cloud.
• Access to the REST Services (e.g. set of exposed services, throttling and DDOS rules) are managed via a API Gateway per
tenant as well as an nginx Proxy Load Balancer and Reverse Proxy with additional request rate limitations.
• Database services are laid out with a hot failover and hot/hot DR setup.
• The Thing-it platform provides one 2x-large EC2 instance handling authentication and bread-and-butter customers
• A fleet of satellite EC2 instances separate the handling of high-profile customers and provide dedictated runtimes
• A shared EFS fileshare is hosting the document repository
• BIMServer is a Java-based WAR-deployable file server which allows to access and to update BIM data
Copyright THING TECHNOLOGIES GmbH 2018 - Confidential www.thing-it.com
MAIN BUSINESS OBJECTS & MODULES
Via REST API’s we set-up bidirectional interfaces into 3rd party applications. All REST communication is guarded by server-side authorization.
Interfaces to existing building control applications and systems via BACnet or KNX protocols of customers are determined by customer requirements.
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.
[ From 200m² to 200.000m² - all sites can get served with retrofitting HW from various partners including EnOcean energy harvesting hardware
• Scaling up on the business and operational level: How would you ensure this?
[ Thing-it platform is utilizing AWS IaaS and can scale without limits; platform architecture is built as modular systems which can get expanded flexibly
[ A fleet of satellite EC2 instances separate the handling of high-profile customers and provide dedictated runtimes
[ Our open REST API layer allows to connect all kinds of various 3rd party systems
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.
The challenges we see are concerning the clarification of the following issues:• 90% of desired platform is already existing and running
• 10% of customized development to adjust platform to specific not yet given features need tobe developed- IP definition and allocation could become a challenge- Developer availability could become an issue depending on needed speed- Project team design and clear responsibilities might be a challenge
Tentative Timeline
• Provide a tentative pilot timeline:- Key milestone dates- Proposed date when you believe your PoC will be live
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
WAN
Ap
plic
ati
on
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
WAN
Appl
icatio
n 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 Phases1. Provisioning2. Tracing
- Chain of Custody- Usage Tracing- External Events- Structural Changes
3. Decommissioning
IoT Identity1. 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