Approach OCS study as a chain of decisions: what the sensor detects, what the controller infers, and what action follows. Work through each link with labeled paper scenarios, compare competing control choices explicitly, and check your reasoning against observations you can make in ordinary occupied spaces.
Occupancy versus vacancy logic: two different control contracts
Occupancy sensing turns equipment on automatically when presence is detected; vacancy logic requires a manual on but still turns equipment off automatically. Treat them as different control contracts, not minor variants of one sensor.
An occupancy sensor answers the question 'is anyone here?' and the controller may act on both edges of that answer: on when presence appears, off after a timeout when it does not. A vacancy sensor only automates the off edge; the on edge is a deliberate human action. This distinction matters because the failure modes differ: occupancy control can switch lights or equipment on for passing traffic in corridors or near doorways, while vacancy control eliminates that false-on problem but adds a manual step the occupant must actually perform.
When a scenario gives you a space type, decide which contract fits before touching any setting. A storage room visited briefly and rarely suits automatic-on occupancy control. A private office where an occupant wants light only while seated often suits vacancy control, because the manual switch confirms intent and the sensor still guarantees shutoff. Practice stating, in one sentence, which edge of control is automated and which is not; that sentence is the foundation every later tuning decision rests on.
PIR, ultrasonic, and dual-technology detection: matching physics to space
Passive infrared detects moving thermal contrasts within line of sight; ultrasonic detects motion via reflected high-frequency sound; dual-technology requires agreement. Match detection physics to obstacles, motion type, and coverage before judging any setting.
PIR sensors see only what is within their field of view, so partitions, shelving, and glass can create coverage gaps or block detection of a seated person making small movements. Ultrasonic sensors do not need line of sight and sense fine motion, which makes them useful around obstructions but also prone to registering air movement from HVAC diffusers, open windows, or corridor traffic as occupancy. Dual-technology units reduce false triggers by requiring both technologies to agree, trading some sensitivity for reliability.
A defensible selection argument names three things: the motion the space actually produces, the obstructions that shape coverage, and the interference sources nearby. Minor-motion spaces such as private offices call for more sensitive coverage of small movements; major-motion spaces such as corridors tolerate simpler detection. Compare a glass-walled conference room against a walled storage room in your notes: the same PIR unit behaves very differently in the two, and being able to explain why is exactly the kind of reasoning to rehearse.
| Technology | Detects | Strength | Typical weakness | Better fit |
|---|---|---|---|---|
| PIR (passive infrared) | Moving thermal contrast in line of sight | Low false-trigger rate from non-occupant sources | Coverage gaps behind obstructions; weak on small motion | Corridors, open major-motion areas |
| Ultrasonic | Motion via reflected sound; no line of sight needed | Sensitive to small movements around obstacles | May respond to air movement or adjacent-space activity | Offices with partitions, restrooms |
| Dual-technology | Agreement of two technologies | Filters most single-technology false triggers | Slightly slower or less sensitive response | Spaces with both obstructions and interference |
| Vacancy (manual-on, auto-off) | Same detection, manual-on contract | No automatic-on false triggers | Depends on occupant compliance to turn on | Private offices, spaces with daylight |
Time delays, setbacks, and deadbands: the tuning triangle
Timeout duration, HVAC setback depth, and the deadband between heating and cooling setpoints interact. Changing one shifts the behavior of the others, so evaluate them together rather than as independent knobs.
A timeout that is too short causes frequent cycling: lights and terminal equipment drop out during a meeting where people sit still, then restart, disturbing occupants and adding wear. A timeout that is very long wastes energy by holding a space in occupied mode long after departure. The same trade shapes setback depth: a deep setback saves more energy but extends recovery time, and the deadband must stay wide enough that recovery from setback does not immediately call for the opposite mode.
Worked scenario: a small meeting room uses an occupancy sensor with a short timeout, and during long video calls the lights drop out whenever participants sit motionless. The plausible-but-weak fix is to raise sensor sensitivity, which invites false triggers from the corridor door. The better decision is to lengthen the timeout to cover typical minor-motion gaps and confirm the sensor technology actually suits seated minor motion. Why it matters: the first fix treats the symptom by making detection more aggressive; the second addresses the mismatch between the space's motion profile and the control contract, and it keeps the off-edge protection intact.
From sensor signal to sequence: tracing what the controller actually does
Every occupancy control system follows a sequence: detect, decide against schedule and setpoints, then act on lighting, terminal units, or ventilation. Practice tracing the full chain for one zone until each step is explicit.
In a building automation context, a raw sensor input never acts alone. The controller evaluates it against the time schedule, the current mode, the setpoints and deadbands, and any hold or override requests from occupants. Only after that evaluation does it issue outputs: a lighting relay, a damper position, a fan state, or a setpoint change. When you read or write a sequence of operations, name each input, each condition, and each output in order; ambiguity in that chain is where control descriptions become untestable.
Compare two ways a zone can respond to vacancy. In one, the sensor directly breaks the lighting circuit after a timeout. In the other, the sensor reports to the BAS, which waits for the timeout, applies a setback to the zone setpoints, and keeps a local manual override available. Same sensor, different sequences, different occupant experience. Tracing both versions on paper, step by step, trains you to notice what a sequence description leaves out, such as what happens to ventilation during setback or how long an override is honored.
Demand-controlled ventilation: occupancy as an airflow input
Demand-controlled ventilation uses an occupancy-related signal to modulate outdoor air. The signal can be direct (people-counting) or indirect (carbon dioxide concentration), and each has distinct assumptions you must state.
Carbon-dioxide-based DCV does not measure people; it measures a concentration that rises toward a steady-state balance between generation and dilution. That means it responds with a lag, it reflects recent rather than instant occupancy, and it is only meaningful relative to a well-chosen baseline outdoor concentration. A people-counting or presence-based approach reacts faster but depends on the counting technology's accuracy and placement. A sound exam answer names which signal a sequence uses and what that signal can and cannot tell the controller.
Worked scenario: a conference room's CO2-based DCV holds airflow low for the first ten minutes of a full meeting because the concentration has not yet risen, and the room feels stuffy at the start. The tempting fix is to raise the CO2 setpoint trigger sensitivity globally, which then over-ventilates sparsely occupied periods all day. The better decision is a sequence-level one: add a scheduled or presence-based pre-ventilation stage before predictable meetings, or combine the CO2 signal with an occupancy input. Why it matters: the signal's inherent lag is a property of the physics, so the correction must come from the sequence, not from chasing the sensor reading.
Commissioning observations and documentation: making tuning defensible
Commissioning occupancy controls means observing real behavior against the written sequence and recording what was set and why. Build a simple observation log and rubric now; it converts vague study into checkable evidence.
Practical exercise you can run safely in ordinary spaces: pick two rooms you can observe, such as a corridor with automatic lighting and a meeting room. For each, record the space type, visible sensor type if identifiable, when the controlled equipment turns on, whether it ever turns on with no one present, whether it ever drops out while occupied, and roughly how long shutoff takes after departure. Repeat observations at two different times of day. This is observation of everyday building behavior, not any invasive or hazardous procedure, and it grounds every concept above in something you saw.
Self-check rubric for your log: (1) you can state the control contract, occupancy or vacancy, for each space; (2) you can propose a detection technology consistent with the space's obstructions and motion profile; (3) you identified at least one mismatch between observed behavior and a sensible sequence, with a proposed adjustment; (4) your notes separate what you observed from what you inferred; (5) you wrote the adjustment as a sequence-level change with an expected effect. These are learning milestones for judging your own notes, not predictions of any exam result, but reaching all five means your documentation habits are exam-usable.
An adaptable preparation sequence for OCS topics
Study in four passes: concepts, contrasts, scenarios, and self-testing. Each pass has a concrete output, so progress is visible and gaps are specific rather than generic feelings of unreadiness.
Pass one, concepts: write one-line definitions in your own words for occupancy sensing, vacancy control, setback, deadband, timeout, dual-technology detection, and DCV, using no resources, then correct them. Pass two, contrasts: for each pair (occupancy vs vacancy, PIR vs ultrasonic, direct vs indirect occupancy signal), write when you would choose each side and why. Pass three, scenarios: take the two worked scenarios in this guide, change one condition each, such as a partitioned room or a shared space, and resolve them again. Pass four, self-testing: redo your concept list cold and score your scenario answers against the rubric in the previous section.
Readiness checks before you consider the subject covered: you can trace a full sequence from sensor input to equipment output without a reference; you can explain the lag property of CO2-based DCV and one sequence-level remedy; you can defend a timeout and setback choice for a described space in three sentences; your observation log meets all five rubric points. If any check fails, return to the matching pass rather than rereading everything. For administrative details about this credential, rely on the issuer's official information rather than study summaries; a scope note for the catalog entry is on the practice page linked below.