Search Icon

    FAQ About Occupancy Sensor Platform

    FAQ About Occupancy Sensor Platform

    The most expensive number in most buildings is the one nobody measures: how many square metres run heating, lighting and ventilation for rooms that sit empty half the week. Facility managers rarely lack data on energy consumption — they lack the occupancy context that explains it. That gap is exactly what an occupancy sensor platform closes, and it's also where most of the questions land when budget conversations start. Below are the ones that come up in real procurement meetings, answered without the marketing gloss.

    What does an occupancy sensor platform actually do beyond counting people?

    Counting is the input, not the product. A platform turns raw counts into decisions: which meeting rooms are booked but never used, when a lecture hall hits capacity, whether a floor justifies its cleaning schedule. Vemco, working in this field since 2005, splits this into two functions worth understanding separately. VemSpace handles space utilisation and facility optimisation — the reporting layer that tells you where you're paying for space you don't use. VemFusion connects that same occupancy data to HVAC, BMS and security systems, so a room that empties out can trigger setback on ventilation instead of running at full rate until midnight.

    How accurate is the counting, really?

    This is the question that separates serious vendors from optimistic ones. The honest answer: the contractual minimum is 96%, and in practice sensors typically reach 98–99% once conditions cooperate. Those conditions matter more than the headline figure. Lighting, room layout, mounting height and visitor behaviour all move the needle. A sensor over a clean, well-lit entrance with predictable flow performs differently than one above a cluttered atrium with glass reflections and people clustering to chat. Anyone who claims a flat 99% for every installation, sight unseen, is quoting a lab result, not a building.

    Does it count staff, or just visitors?

    Staff exclusion is built in, and it's more useful than it sounds. In a university library or a public service centre, employees walking the same routes all day inflate every metric if they're counted as footfall. Excluding them means your utilisation reports reflect the people you're actually planning space for. The AI sensors handle this distinction rather than relying on a manual toggle, which is what keeps the numbers usable for real capacity decisions instead of needing a caveat every time you present them.

    Can it warn us before a space gets overcrowded?

    Yes. Real-time occupancy comes with alerts at a predefined limit, so a reading room, a canteen or an event hall can flag when it's approaching capacity rather than after complaints arrive. For public institutions with safety obligations, this shifts crowd management from reactive to planned. The practitioner detail here: set your alert threshold below the legal maximum, not at it. By the time a live count catches up with reality — there's always a small lag as people flow through a doorway — you want staff already moving, not scrambling.

    How does it save money if we've already got a BMS?

    Most building management systems run on schedules and static assumptions — 8am to 6pm, five days a week, whether the space is full or empty. That's where waste from always-on systems accumulates. Occupancy data replaces the assumption with the actual pattern. A wing that clears out by 3pm on Fridays doesn't need conditioning until 6. A conference floor used twice a week doesn't need daily full-service HVAC. VemFusion feeds this into the BMS so decisions follow real presence. The savings aren't from installing sensors; they're from stopping the systems that were running for nobody.

    What about privacy — are these cameras?

    This is the first question in every university and public-sector meeting, and rightly so. The sensors count presence and movement; they aren't a surveillance feed identifying individuals. For a workplace leader, that distinction is what gets the works council on board. For a public building, it's what keeps the deployment defensible under data protection scrutiny. Be ready to explain in writing what the sensor stores and what it doesn't — the technical answer is easy, but the documentation is what procurement will ask for.

    Where does a platform like this pay off fastest?

    Some environments show returns quicker than others:

    • Offices weighing hybrid work against lease costs — utilisation data tells you if you're renting floors that sit at 30%.
    • Universities managing lecture halls, study spaces and libraries with wildly uneven demand across the term.
    • Public buildings where energy budgets are fixed and every kilowatt hour saved on empty rooms is money kept.

    What should we ask a vendor before signing?

    Ask three things. First, what accuracy they'll commit to in writing for your specific spaces, not a brochure figure. Second, whether the platform integrates with the BMS and security systems you already run, or whether it's a standalone dashboard someone will stop checking after month two. Third, how the reporting maps to a decision you'll actually make — reallocating space, adjusting HVAC schedules, planning a renovation. A platform that produces dashboards nobody acts on is just a nicer way to store the same uncertainty.

    If you're comparing occupancy sensor platforms and want an accuracy commitment tied to your actual floor plans — plus a clear view of how VemSpace and VemFusion would connect to your existing HVAC, BMS and security setup — talk to the Vemco team here. Bring your worst-performing space; that's usually where the numbers make the case fastest.

    Join Our Newsletter Community Today!

    Form-right