Difficulty: expert
Content
| Table of Contents | ||||
|---|---|---|---|---|
|
Learning Objectives
After reading this article, you’ll be able to:
include Zens data in Workplace
How does Zens PuK IoT Visual work?
Both the use of the wireless charger and the motion sensor being triggered is regarded as a sign of occupancy.
If both are triggered, Workplace considers the location as being occupied.
Wireless Charging
NB-IoT communication
Occupancy sensor
iBeacon
Charging module
PuK iOT visual parts
Place a phone that supports wireless charging on the LED cover.
You’ll hear a “beep” within a few seconds. This beep indicates that charging has started. In addition, the phone will also show a charging indication on the screen.
The LED ring on the PuK will turn red.
A message is send to the Workplace platform, indicating that occupancy/presence has been detected.
Motion Sensor
If the motion sensor has detected movement, the LED ring on the PuK will turn red.
A message is send to the Workplace platform, indicating that occupancy/presence has been detected.
LED indications on the motion sensor:
Green: connected to Power
Red: Motion detected
How is Motion sensor data reflected in Workplace Live Views?
Upon the charger being used, the signal goes up immediately, and will remain actively sending updates to Workplace.
Upon a Motion sensor being triggered, the signal goes up immediately, but only goes down after a few minutes:
So as soon as occupancy is detected, a signal is send to the Workplace Platform, which will reflect in Workplace touchpoints' floorplans in near-real time: the location occupancy color goes from GREEN to RED almost instantly, but goes from RED to GREEN based on a fixed timer which cannot be shorter than 10 minutes.
This means that human motion can only trigger the sensor to go from '0' to '1' , and not the other way around.
Once the sensor goes up (meaning “presence detected”), it can't change its state faster than 10 minutes, which is why the default decay on the red icon lasts 15 minutes. The decay is actually nothing more than a clock counting down until the next refresh, regardless of the presence during that window.
In other words: The reason for using this decay is to indicate that the probability that the location is still occupied is lowering.
Decay Configuration options
Perhaps you would want to indicate in Workplace Live Occupancy View that if a Desk sensor has been triggered, the location is occupied for at least 2 more hours, so that colleagues and guests can go to lunch or drop by a meeting without having to fear that someone is clearing out their workplace? But at the same time you want to indicate that a meeting room has freed up as quickly as possible, so that it turns green (“available”/”not occupied”) and people can recognize this at a glance?
The Workplace back-end Studio configuration options have you covered: per room category, both the icon and the decay timer can be modified (for the reasons explained above: the timer can be set to anything higher than 15 minutes).
How does this reflect in Workplace Dashboards?
Even if you want to show your colleagues in Workplace Live Occupancy View that a desk is “occupied” while you’re actually jumping from meeting to meeting in other rooms, the data will show that the desk was only really occupied for some brief moments. Per default, data aggregation happens per 15 minutes.
Following page provides more insight into how data is saved into the Workplace IoT Platform: /wiki/spaces/WM/pages/492237
Installation
Installation is done by Zens.
Requirements:
For the PuK IoT Visual / wireless charger: A hole with a diameter of 81 mm needs to be drilled in the table at the position where the PuK IoT Visual should be placed.
The motion sensor needs to be installed in the center at the bottom of the desk.
The ideal distance from the front of the desk to the front of the sensor is 300 to 350 mm
Provide an unobstructed view of the sensor for an optimal detection area
The motion sensor will be screwed with two screws on the underside of the desk
Data-Stream Configuration
Zens will connect to the Workplace platform through Generic Endpoint.
Deploy sensors in Workplace Platform
Add New Device in Workplace back-end Studio
Go to your environment ( ) and log in
Select the location, where you can manually add a sensor via "Add New Device"
Manually add device through location > devices > new: location is filled in.
Select Device Type "Generic PIR". This will automatically link the device channel.
Enter Device ID as
prefix “zens|”
Device ID will be provided by the ZENS project team
example: “zens|867723035258986”
Enter a meaningful Device Name (eg customer_floor number_area).
Select a Location from the location tree if this is already known (automatically filled in if location was selected before adding new device).
Linked Locations is not relevant for this kind of sensor.
Selecting the correct Device Type "TrackNet Motion v1.3" should automatically set the Type to "Presence" and the Channel to “PIR” (see Advanced).
For more information on how to add multiple new devices to Studio, check out Configure devices (add, remove, import/export).
Electrical Specifications
Power Adapter | |
|---|---|
Input voltage | 100-240 VAC |
Output voltage | 15V +/-5% |
Input frequency | 50 / 60 Hz |
Efficiency level | Energy Star Level V |
Standby power | < 0.3W |
Cable length | 1500±50 mm |
Charging Module | |
|---|---|
Input voltage | 15VDC +/-5% |
Maximum input current | 1,6A (adapter) |
Charging unit | WPC-compatible devices |
Charging frequency | 127kHz |
Operating temperature | 0 tot 35 °C |
Storage temperature | -20 tot 70°C |
Motion sensor | |
|---|---|
Input voltage | 3.5- 5.0 VDC |
Nominal input current | 10mA |
Operating temperature | 0 tot 50°C |
Sensor range | 0-800 mm |
Search
| Live Search |
|---|