Presentation of Connectorio's building's technical systems integrations expertise, services, and the ConnectorIO multi-protocol gateway with Industrial IoT and Building Management & Automation System Cloud platform. More information: 🔹 Our website: https://connectorio.com Social: ◼️ Linkedin: https://www.linkedin.com/company/12662346/ ◼️ Facebook: https://www.facebook.com/connectorio ◼️ Twitter: https://twitter.com/connectorio Contact us: 🔹 https://connectorio.com/contact/

1. Products, services . 2019
Cloud BMS, IIoT Platform | Integrate - Analyze - Automate
We connect the technical systems of industrial and commercial buildings, analyze their effectiveness,
automate in an intelligent way to make them work as valuable assets for your company.

2. ★ Integration of technical systems and devices
located in industrial and commercial real estate.
★ Development of a cloud-based software for
managing and optimizing building’s technical
systems.
We are ConnectorIO - Connector + IO (input/output)
We specialize in:
ConnectorIO
Cloud
Industry 4.0 | Commercial Real-Estate (CRE)
WITH OUR CLOUD, WE ALLOW YOU REMOTE:
⬡ Management
⬡ Control
⬡ Automation
⬡ Reporting and data analysis
01 Measure
02 Monitor
03 Analyze
04 Automate

3. ​Establishing company based on earlier work experience.
Main focus – software integration in enterprise
scenarios. Beginning of work with Nokia Siemens
Network.
Code-House launch
2008
Contracting work with American companies (Alcatel-
Lucent, Red-Hat later on) in development of products
fully based on open source software.
Open-Source involvement
2010
About Us
A Reliable Partner
Entrance of home automation software and related open
source community. First achievements in area of
BACnet and heating systems integrations.
Home Automation
2015
Formation of limited company aimed to build a complete
product for industrial and CRE markets around IoT and
Industry 4.0 principles.
ConnectorIO launch
2018
EXPERIENCE
Our implementations include
optimization of HVAC control panels,
lighting system control applications,
environmental monitoring of BLE
sensors (Bluetooth) and metering
of media consumption based on OMS
and WM-Bus.
ConnectorIO as a company and brand
was founded in 2018. We have
combined over 11 years of experience
in the development of open-source
software and middleware with a
passion for building automation and
experience in the field of system
integration since 2015.

4. Our services
● Open-source software consultancy.
● Integration of hardware with
IoT platforms.
● Software and IoT communication
protocols development.
● Cloud integrations
cloud → device
device → cloud
cloud → cloud
● Security and authentication,
authorization setups (OAuth 2 / OpenID)

5. Benefits – What makes
our software different?

6. Benefits
Benefits of installing ConnectorIO for the end-user:
Common communication bridge between devices from different manufacturers in one system.
Control of energy and media consumption in real-time (data sampling up to milliseconds).
Increasing the building's energy efficiency thanks to advanced automation based on intelligent
rules and scripts, not on inefficient schedules.
Full supervision over the infrastructure and construction/production data in one dashboard.
Secure data storage in the cloud - no restrictions on the amount of data, so you can sample data
at a high frequency and bypass the limitations of the hardware driver.
Quick and easy retro-fit of existing hardware infrastructure with IoT devices.
Remote access on mobile devices - different levels of access authorization.
Easy-to-use user interface and simple device configuration that doesn't require IT skills.
Auto-detect devices function (depending on the protocol).
Fast learning curve - ConnectorIO operation does not require advanced competencies.
Easy software update process (in the cloud - does not require intervention in the facility).
High scalability and modularity of the solution, which allows you to add new extensions
and remove devices from the system without having to reprogram the whole infrastructure.

7. One Platform – Many Integrations
Hardware, connectivity, supported devices

8. MODULAR ARCHITECTURE
Extensibility, easy system updating
and adding new functionalities
The modular architecture of the ConnectorIO system allows
you to flexibly add new extensions.
The extensions are located in the system's software layer,
which is independent of the end device's hardware driver.
That allows easy updating and adding new functionalities
without the need to program the firmware of the hardware
driver.
This modularity not only allows the integration of new
devices but also means the possibility of integrating
ConnectorIO with other cloud-based services and increasing
the functionality and value of the system even further.
CLOUD
KNX
BACnet
Modbus
OMS
EXTENSION

9. Unification of Communication & Control
Support for multiple protocols, integration of devices from different manufacturers in one panel.
® Registered signs - means that all the mentioned brands and logos are registered trademarks belonging to their respective owners.
ConnectorIO is a universal, software communication bus (a common channel through which devices exchange data). The system unifies data
(and measurement units) from different manufacturers' devices and ensures compatibility, so you can manage all of them in one place.
COMMUNICATION BUS
Compatibility, Data Harmonization
Many Devices – One Platform

10. ConnectorIO : Hardware + Software
ConnectorIO needs a minimum of one central computer unit with control software
based on a secured Linux system.
The role of the Central Unit:
• acts as a server of data transferred to the cloud,
• creates and supports digital equivalents of devices (digital-twin),
• supports local communication and stores device automation rules,
• collects data in the absence of communication with the cloud and transfers the data
when the connection is restored.
The Central Unit (CN) is an industrial computer that enables operation in extreme
conditions (dust, high/low temperatures). The central processing unit (CN) comes in
many different configurations and provides support for as many end-point devices as
there are I/O ports available.
In the case of real estate with a very dispersed structure, communication with end
devices can be provided wirelessly, or the number of ConnectorIO communication
gateways can be increased accordingly.
ConnectorIO can work:
• As a cloud-based service or a local system.
• Parallel to the existing BMS/SCADA system, or independently operate the building's
technical systems.
Central Unit (CN) / ConnectorIO Gateway - the software
is installed here (on Linux OS).
CN
We Aggregated Data in The Cloud
we integrate all systems in one
central user panel from which they can be
monitored and controlled.
Building’s Technical Systems
ConnectorIO
CLOUD

11. The concept of connecting devices in ConnectorIO
NOTE: one gateway can support several different
protocols. Additional gateways are drawn in the
diagram only to show the type of connection.
In a minimal configuration, only one C.U. is needed
in place of a ConnectorIO Gateway from the drawing.

12. INBOX
– adding devices
• Standard devices that allow communication are automatically recognized
and appear in the "Inbox".
• The process is fully automatic, the user only needs to authorize the device
integrated within the system.
• The scanning process can be started and repeated many times without affecting
already integrated devices.
Device search and quick integration:
Devices that support auto-discovery
can be added in a few clicks.
• The system creates a digital equivalent of the device - the so-called Digital-Twin.
• The Digital-Twin is a type of logical layer that protects a physical device against hacker
attacks and protects against access to the entire building automation network.

13. * Automated - with an additional description or data source, the whole process can be done with minimal effort.
* Possible - feasible, not yet implemented.
* Template - you can create a device template and define it with one click.
* "Homie IoT" - An MQTT Convention for IoT/M2M - more info: https://homieiot.github.io/
AUTO-DISCOVERY COMPATIBILITY
(automatic discovery of devices and their parameters – inputs/outputs, so called Plug & Play)
Auto-Discovery (Plug & Play)
Automatic device detection and definition
feature.
Thanks to the auto-discovery (A.-D.) functionality, the
System Integrator or Installer can incorporate devices into
the system in a few simple steps.
BENEFITS OF AUTO-DISCOVERY:
• Time saving - rapid integration of devices.
• Simplicity - no need to program drivers.
• Basic competences related to the operation of computer
systems are sufficient to integrate devices with A.-D.

14. Device configuration • It does not require knowledge of programming languages and usually boils down
to providing the device's IP address and/or port number.
• When there are changes in the hardware configuration, it is enough to edit the
device parameters in the Things tab to update the system without restarting.
Device integration and automation settings in ConnectorIO do not
require knowledge of programming languages.
To operate the system, basic skills in operating typical computer
systems or mobile applications are sufficient.
The automation mechanism is shown later in this presentation.

15. Digital-Twin
Digital representation of the device in the system.
Security & interchangeability of components
The role of a DIGITAL-TWIN:
• It reflects only those device functionalities
that have been authorized by the admin.
• Access to the physical device is via the twin.
The digital-twin is not limited by hardware
driver software, so it can provide extended
functionality.
(for example, writing and reading from the
device may occur at a higher frequency than
directly from the controller).
• Digital Twins can communicate with each
other in the system regardless of whether
they are actually physically connected or not.
The digital-twin allows you to control the status
of the device while acting as a firewall.
ConnectorIO does not communicate directly with the end device
hardware drivers, but with the digital twins. The system is built in such
a way that the physical layer is separated from the software and there
is no possibility of attacking devices from the network.

16. Laying of technical infrastructure
& Connectivity
Physical connection of devices with the
ConnectorIO Gateway. Devices authorization
process using tokens. Creation of digital-twins.
Launching the cloud
& User authentification
Launching the ConnectorIO software,
creating accounts and granting access
to users, generating tokens
and login passwords.
Customizing the dashboard
& Automation rules
Each customer has different needs, therefore:
- the user interface allows you to create
widgets that visualize data,
or
- the Connectorio Team can customize the user
panel and adapt it to the specific customer
needs.
1
2
3
The Implementation Process
Installation of the system requires three steps
12

17. ConnectorIO as a Building
Management System
Local BMS vs. ConnectorIO

18. HVACThere are many control systems in the
buildings that are NOT CONNECTED!
Installation design is often carried out by separate entities, which
leads to incompatibilities and lack of data exchange between the
systems put into use.
Some systems are available on each floor and the Tenant has
access to these, but others are operated by the Property Manager.
Despite the implementation of automation, many devices are still
controlled based on simplified schedules.
Schedule-based management is inefficient!
It does not work particularly well in the case of office buildings,
where the floor occupancy schemes change constantly.
INEFFECTIVE power management
based on schedules!
Sensors
Electricity
Access Control

19. Sensors that monitor temperature, humidity, environmental parameters.
Manual and wall switches
Environmental sensors
Alarm and access control systems
Media and electricity meters
HVAC systems
SYSTEMS THAT WE INTEGRATE
Manual switches can be monitored in the system.
They can be used as additional indicators of presence in the facility.
Monitoring of gas, heating, water and electricity demand.
Performance monitoring in combination with actual demand.

20. Limited electricity spendings
Reduced heating demand
Valid cooling
Reduced CO2 emmission
01
02
03
04
Devices and lights are turned on only when necessary and not
when left turned on.
Less lights, less overhead
Places which are not occupied require a smaller amount of
heat. Upon reasonable calculation adjustment of heating can
be made.
No heating for empty rooms
Rooms left empty for a long time should automatically limit
the demand for cooling as this cold air serves no one but
furniture.
Cooling for people, not furniture
The ongoing trend of emission reduction forces real estate and
facility management to seek for savings. With all above it's not
only possible but profitable.
Green building
Mastered Device Interoperability
= Savings!

21. ConnectorIO vs. Traditional Building Management System comparison.
Feature Traditional BMS ConnectorIO
Controller Closed - dedicated to 1 or 2 defined standards
Open - not tied to a specific communication protocol.
Limited only by the physical interfaces.
Device auto-discovery possible in the case of some communication standards.
Data streams (input/output) Limited Configurable, all available channels can be used if necessary
Gateways - basic
(system couplers)
- $$$ expensive (hundreds EU),
- combine only 2 standards,
- standards coupling needs to be programmed before operation using industry-specific
design tools
+ firmware update
- gateways operate in a distributed way - passive element, limited communication between
gateways.
- changes in the configuration of the edge device are moderately simple,
- no direct physical interaction with the edge device is required
- changes can be applied through the network
Gateways - with a webserver
- $$$$ more expensive than the basic solution,
- still lots of programming done outside the gateway
Operation
Only local - on-premises.
Cloud connection possible but limited to functions programmed in device-specific
controllers.
Local or Cloud - on or off-premises
Cloud solution
Limited, not flexible:
- limited to device model and firmware update compatibility.
- usually only mainstream providers available or vendor-specific cloud systems.
Not limited, flexible:
- works with different mainstream and non-mainstream cloud providers.
System device updates
Costly and Complicated - demands controller’s firmware reprogramming or hardware
update and intervention of multiple vendors (integrators, BMS operators) on-premises.
Relatively easily, no need for physical intervention.
System operator competences Highly skilled professionals needed. Basic computer operation skills or regular IT intervention.
Data storage capabilities Data is usually stored in an SQL database on a physical storage device located on-premises. Data can be stored locally or in the cloud.
Stored data range
Limited
- usually limited to “trend logs” available from the controller’s registers and then copied to
the SQL database
Not limited, can be re-programmed, re-defined.
Data retention time
5-60 mins, 1 day, 1 week, 1 month
- limited by the capacity of local BMS data carrier,
- data is being averaged,
- data subject to “blurring” of the extreme values,
- in case of hardware changes, the storage should be replaced as well.
Depends only on the resolution of data probing by device and the storage
capacity.
- could be milliseconds and up to months/years of stored data in case of cloud
storage.

22. How do we implement
cloud-computing?

23. A) BMS1: Traditional integration (local)
Device Controller BMS
1) Same applies to SCADA systems, which BMS originates from.
B) IoT: Standard implementation
Device Gateway Vendor Cloud2
Traditional BMS integration + IoT Cloud
2) For example, one of the leading cloud-computing providers in the market.

24. ConnectorIO Cloud implementation options
Driver Device
ConnectorIO
Cloud 1
REST
API
ConnectorIO
Gateway
1. Directly to the Device
Controller Device
ConnectorIO
Cloud
REST
API
ConnectorIO
Gateway
2. Via a controller
1) ConnectorIO Cloud can use the infrastructure of any cloud-computing solution provider. The customer has full freedom of choice.

25. 3. Via an existing gateway (or BMS) 4. Cloud to Cloud
ConnectorIO
Cloud
Gateway
Device
Vendor Cloud
HTTP/COAP/
MQTT/TCP
etc.
polling or eventing
REST
API
ConnectorIO
Gateway
Gateway
Device
Legacy
HVAC
HTTP +
webhook
MQTT (?)
Vendor CloudConnectorIO
Cloud
REST
API
ConnectorIO
Gateway
ConnectorIO Cloud implementation options
In scenario 4, ConnectorIO can be used to provide connectivity to
older devices that are not supported by the IoT Cloud, which will allow
the integration of modern IoT devices with existing building installations.

26. System Interface
Data Visualization

27. Administration
In the main administration panel the
user can perform the following actions:
• View the status of inputs and outputs
that are grouped by the device.
• Manually limit/allow the recording of
input data from devices.
The system provides a uniform interface
for all integrated devices. This is an
important aspect of the Digital-Twin
concept.

28. Device channels • Each device has many channels (inputs/outputs), but the user decides which
of them will be available in the system and which will be disconnected.
• Disconnecting unused channels simplifies the interface.

29. Automation
• The automation mechanism is
based on logical rules.
• All systems integrated into
ConnectorIO can interact with each
other - for example, you can
choose the appropriate device
state 1 that will trigger a specific
operation on devices 2 and 3,
which are not physically connected
together.
• In justified cases, it is possible to
add very complex automation
thanks to scripting.

30. Output
Input
A certain threshold, an event or state
change are the most common reasons for
writing a rule. For example – temperature
above 22C or below 19C, sunrise, a
detected motion.
What can be triggered
A result of rule execution might be a
state change of another channel in
another device, another event. An action
might include switching on the light,
changing setpoint or sending an
email/text message.
What can happen
Conditions which need to happen
in order to execute the rule
Criteria
List of commands and states to set
when criteria match the state of the
system.
Action
Rule engine
Automation made easy

31. Customizable visualizations & widgets

32. Gas
Gas consumption

33. Ventilation
Temperatures

35. Do you implement an automation project?
We invite you to contact us!

36. SUMMARY OF BENEFITS
Savings
Optimizing only HVAC operation and
lighting translates into 70%
optimization of the building's total
electricity consumption.
Effectiveness
Increasing the efficiency of HVAC
AHUs by 34-48% thanks to the
automation of its operation adjusted
to real-time occupancy schemes.
Compatibility & Simplicity
A solution is independent of hardware
suppliers that ensure compatibility and
unification of data between multiple
systems. Very easy to install.
Data Analytics & Reports
Large sets of building system data
collected in one place allow us to
predict media consumption trends
and introduce savings.
Real-Time Monitoring
Maintenance and reduction of device
failure risk due to central supervision
over their work from a panel on a
laptop or mobile phone in real-time.
Building Retrofit
Class B commercial real estate can
offer more comfort if able to connect
existing infrastructure with the
modern Internet of Things equipment.

37. Contact Us
CEO: Łukasz Dywicki +48 721 151 666 - lukasz@connectorio.com
CMO: Ireneusz Krajewski +48 512 733 982 - irek@connectorio.com
Connectorio Sp. z o.o. – Krasiczynska 3/80, 03-379 Warsaw, POLAND