theodi
new_BDNS_desk_occupancy_sensor_DOS
Kelly, could you please provide a datasheet or product link to help progress this discussion?
Hi Rita, thank you for getting back to me, please see product datasheet link. https://resource.milesight.com/milesight/iot/document/vs34x-datasheet-v1.0.pdf
@TheFridgeShaman what is your view?
I know sometimes these are tagged as 'PCS' but it is indeed a different technology (occupied/unoccupied vs actual count of people)
Hi Rita and Kelly, ultimately we're talking about PIR sensors. If I understood correctly, and please correct me if I'm wrong, the spirit of BDNS so far was to name assets according to their technology rather than to their function or role in a specific scenario, and BDNS is not inclined to accept a new abbreviation for an asset that already exists in the abbreviation register. For this reason, it would make sense to call them MOS like any other motion sensors even though they work for occupancy counting. The counter-argument is that LMS exists for lighting motion sensors, but the exception there might be justified due to the separate control system and the large number of PIRs. I would suggest not calling them PCS because if you have actual people counters in the project you might have a hard time filtering them and telling them apart solely from the device name. Hope it helps. Please let me know your comments because it's a dilemma that appears often in projects.
Andrea and Rita, thank you both for the time given on this discussion and for the clarification provided.
To pick up this issue again. Is it useful to add a generic occupancy sensor? Does MOS satisfy the use case requirements here?
Hi @RitaLav , thank you for your message. New abbreviation for Desk Occupancy Sensor - DOS to BDNS it would be the best solution for Smart Building IoT devices, as we have seen a significant growth of the specific Desk Occupancy sensors (under desk) in projects. MOS is not 100% satisfying for the use case scenario, but it is the closest if DOS not added. Regards, Kelly