Presentation is loading. Please wait.

Presentation is loading. Please wait.

Meeting Room Automation

Similar presentations


Presentation on theme: "Meeting Room Automation"— Presentation transcript:

1 Meeting Room Automation
1. Xhesika RUCI 2. Mina Rady 3. Ida McSey 4. Mukhammadjon Jalolov

2 Problem Devices consuming power after work Meeting time Conflict
Degraded Comfort Level Meeting time Conflict Waste of electricity Inefficient Meetings Security of Facility

3 We are motivated to improve
Motivations We are motivated to improve Energy Efficiency Monitoring Smart Comfort Facility Security Smart Comfort

4 Sustainability Social Sustainability Efficiency Economic Save money
Environmental Save natural Resources

5 Idea Our system synchronizes with personal or organizational calendars and adapts room comfort and security measures accordingly.

6 TAVATA offers - Integration with existing personal and organizational calendars. - Monitor Air Quality - Wait until people leave and turn Off heater/cooler, lights. - Monitor unauthorized access in the room through motion detection and door status. - Notify admins via of security breaches.

7 System Architecture Meeting room LED Displays Motion Sensor Dimmer
Meeting room LED Displays Motion Sensor Dimmer Thermostat Humidity/Temperature

8 Main Logic Display Control Watchdog: Notifications:
Display current Temp/Hum Check current schedule: Room is empty Display upcoming meeting schedule Display current meeting title Watchdog: Check door status and check calendar No scheduled meeting and no motion Turn off lights No scheduled meeting and door is open Warning to administrator Notifications: Door opens Turn on light Motion detected out of schedule hours Warning and make sure devices are turned off

9 Short Explanation of FHEM and impression
FHEM provides common interface to interact with different home automation technologies. It offers different open interfaces as well to allow other systems to be interoperable with it. Mainly JSON and XML It allows integrating PERL codes and scripts. However, it provides many limitations as all configuration has to be done within the FHEM framework. All FHEM forums are in German which made it difficult to get feedback from other developers facing similar problems.

10 FHEM Limitations FHEM runs on single-threaded Raspberry PI. This makes it quite challenging to trigger multiple notifications for the same event. FHEM does not allow typical HTTP hosting for any files outside of its framework, we had to install APACHE server to implement our monitoring interface. FHEM does not allow safe modularity or scalability. Since PERL scripts can only be used within its framework, the only way to create truly modular perl components is to use an embedded tool: 99_myUtils.pm which has to be completely compliant to the particular limitations and dependencies of FHEM.

11 Savings Considering the average CO2 emission factor = 0.527 kg / kWh
The electricity price EUR per kWh Around 12 meetings per month. Assuming appliances are left on for 10 hours after meeting Appliance Money saving per month CO2 emissions Per year CO2 Per year Heaters (2) 2400 W 63.36 EUR 151.7 kg EUR kg LED lights (20) 300 W 7.92 EUR 18.9 kg 95.04 EUR 226.8 kg Air conditioners (2) 2400 W (in summer time) Total: 71.28 EUR 170.6 kg EUR kg

12 Wireless Communications Protocol
Residential Control Automation Market Z-Wave Technology Smart Living Solutions Wireless Security Sensors & Emergency Alarms IoT based devices Energy & Light Commercial Apps

13 Z-Wave Technology Originally developed by Danish Startup Zen-Sys Acquired by Sigma Designs (American public Corporation) in 2008 Over 1700 interoperable Z-Wave products marketed Over 35 million been sold since 2005

14 How Z-Wave works ? Z-Wave Network – Unique Home ID
Slave Devices: Up to 232 Nodes Home ID + unique Node ID Bridging Option - if more devices needed. Controller Devices: Predefined Network ID Primary/Secondary

15 Z-Wave Protocol Stack Application Security Network Transport
Device Specific Commands App specific commands Takes control of payloads in the frames Application Encryption (AES-128 type) (Implementation Specific) Security Topology Discovery Frame Routing/ Routing Table Update Network Error Detection & Retransmission Acknowledgements Transport 32-bit Home ID, up to 4 billion Z-Wave Networks 8- bit Node ID- max 232 Nodes (EU) / (US) MHz- unlicensed ISM bands Modulation, RF channel assignment, Preamble addition MAC & Physical ITU-T G9959 Physical Layer- Modulation, RF channel assignment, preamble addition in transmitter and synch of preamb in receiver MAC- control the medium between nodes based on collision avoidance alg and backoff alg

16 Why use Z-Wave ? Network installation is easy and simple
Lightweight hop protocol Low Power Consuption Devices- Power Save mode Low-latency transmission of small data packets. Z-Wave devices are interoperable with other IoT wireless devices AES-128 type of encryption - Secured wireless network No Wi-Fi Interference, quiet frequency

17 Technical Specifications
Z-Wave - source-routed mesh network architecture Downfall: increased frame length, the route should be included inside of the payload Low-latency transmission of small data packets. Supports 9.6 Kb/s, 40 Kb/s up to 100 Kb/s data rates - control and sensor applications Communication distance between two nodes – about meters. Up to 4 hops Message FSK Modulation with Manchester channel encoding Max payload data – 64 bits, 8 bit address blocks Z-wave devices are interoperable with other wireless devices in IoT It uses AES-128 type of encryption to provide secured wireless network- spec. for the encryption of electronic data. The algorithm described by AES is a symmetric-key algorithm, meaning the same key is used for both encrypting and decrypting the data. AES is included in the ISO/IEC standard. AES is available in many different encryption packages, and is the first (and only) publicly accessible cipher approved by the National Security Agency (NSA) for top secret information when used in an NSA approved cryptographic module (see Security of AES, below).

18 Comparisons Wi-Fi : noisy static larger bandwidth (2.4/ 3.6/ 4.9/ 5 / 5.9 GHz, 22MHz Channels ) Bluetooth: No remote access: point to point bandwidth (2.4GHz, 2MHz channels) Z-wave : Interoperability, quiet frequency Zigbee: Similar in power, range and low cost but incompatible with Z-wave.

19

20 Thank you!


Download ppt "Meeting Room Automation"

Similar presentations


Ads by Google