Central plant
Boiler purge and flame proving, pump duty, valves, heat exchange and plant alarms.
Building automation training · BAS + BMS
Run the whole building, not another slide deck.
Program HVAC zones, central plant, access control and alarms in one browser lab. Then open the full 3D building-automation floor and trace every sensor, actuator, permissive and failure back to PLC logic.
One curriculum, connected systems
Practice the sequences a BMS has to coordinate.
The page deliberately combines building automation systems training and building management system training into one canonical learning path. Search wording changes; the underlying control work does not.
HVAC zones
Four editable VAV zones with analog position, airflow and temperature feedback.
Access and vertical transport
Garage doors, barriers, traffic lamps and elevator landing calls in one environment.
Controls network
PLC cabinet, HMI, remote I/O and industrial Ethernet props with generated tags.
Five working labs before you compose your own floor.
Each scenario has requirements, visible I/O and objective checks. Use those constrained exercises to learn the pattern; use the Sandbox to combine the systems.
01VAV damper modulationAnalog demand, deadband, occupied mode and safe-state behaviour.02Boiler startup sequencePurge, ignition, flame proving, run permissives and trip handling.03Chiller lead-lag sequencingStage multiple machines and remove unavailable equipment from service.04Garage door controllerLimits, obstruction handling and mutually exclusive motor outputs.05Elevator controllerCalls, travel direction, landing state and door interlocks.
Building automation in the 3D Sandbox
Start from a full plant-and-access floor. Change every component.
The new building-automation starter is assembled from reusable, PBR-textured components with typed I/O and code-native motion. It is a real editable scene, not a fixed background render.
151
reusable components
3
lazy-loadable packs
PLC
driven motion + faults
Public viewer is free. Guided 3D starts on Basic; composing and saving custom 3D scenes is Pro.
Live WebGL component viewer
151 real-time factory components
Load the interactive viewer when you are ready to orbit the models.
Loads 3D only after your click
Drag to orbit · scroll to zoom · choose any componentOpen full viewer ↗
The honest training boundary.
This is a control-logic and troubleshooting environment. It can make BAS sequences visible and repeatable, but it cannot certify a technician, commission a production BACnet network or replace supervised work on live equipment.
Best conversion path
Learn a sequence → prove it → combine systems.
Free visitors can inspect the public component library. Guided BAS exercises start in the training plans. Pro unlocks composing and saving the complete custom 3D floor.
Compare training plansQuestions
Building automation and BMS training questions
Building automation training teaches how controllers, sensors and actuators coordinate HVAC plant, occupied zones, alarms, access systems and other building services. This course-style simulator focuses on PLC control logic, sequences, interlocks, analog values and faults.
Competency and practice field guide
Building automation training: implementation, evidence and troubleshooting
Direct answer
Building automation training becomes useful when it connects building use, equipment, occupancy modes, setpoints, sensors, actuators, interlocks, safeties, alarms, trends and operator tasks with zone or plant demand through bas logic, equipment command, physical proof, environmental response and supervisory display, then proves occupied startup, stable operation, mode change and controlled shutdown of one representative system under normal, boundary, fault and recovery conditions. The objective is a repeatable engineering or learning result, not merely activity inside a page or tool.
This guide is written for hVAC technicians, electricians and controls learners studying air handlers, pumps, boilers, chillers, zones, sensors, actuators, alarms and BAS supervision. The intended result is specific: the learner can trace an occupancy or environmental demand through mode logic, equipment sequence, proof, loop response, alarm and operator display.
System map / 02
Six concepts that control the result
Treat these as connected checkpoints. Each checkpoint has an expected state, an observable state and a boundary to the next part of the system. That structure prevents a software indication from being mistaken for physical proof.
NODE 01observable
Define the operating contract
building use, equipment, occupancy modes, setpoints, sensors, actuators, interlocks, safeties, alarms, trends and operator tasks. For building automation controls, sequences and diagnostics, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation.
NODE 02observable
Map the evidence path
zone or plant demand through BAS logic, equipment command, physical proof, environmental response and supervisory display. Separate request, internal state, output or service, physical or user-visible result and independent feedback so each boundary can be inspected.
NODE 03observable
Prove normal operation
occupied startup, stable operation, mode change and controlled shutdown of one representative system. Run more than one cycle from a known state and retain the values, timings or artifacts that demonstrate repeatability.
NODE 04observable
Exercise a boundary case
freeze protection, smoke interface, lost airflow, failed valve or damper, sensor bias, utility loss and restart. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path.
NODE 05observable
Diagnose a controlled fault
a mode, schedule, permissive, command, proof, loop, instrument, network or process-response fault. Preserve the first symptom, divide the system at a measurable boundary and change one condition only after predicting the result.
NODE 06observable
Transfer and hand over
the sequence compared with approved design documents and commissioned on the actual BAS and equipment. Restore normal state, remove temporary changes, repeat affected checks and document which claims remain limited to the learning environment.
Procedure / 03
A six-step practice and commissioning workflow
Run the steps in order the first time. Later, the same structure becomes a diagnostic loop: define the expected condition, observe the boundary, interpret the difference and choose one proving action.
- 01
Write the acceptance case
Convert building use, equipment, occupancy modes, setpoints, sensors, actuators, interlocks, safeties, alarms, trends and operator tasks into initial conditions, one stimulus and observable pass criteria.
Evidence: Another person can repeat the case without guessing the intended result.
Avoid: Using page completion or an animation as the acceptance criterion.
- 02
Build the map
Document zone or plant demand through bas logic, equipment command, physical proof, environmental response and supervisory display and name who owns each state or decision.
Evidence: Every request and result has a source, destination and useful inspection point.
Avoid: Using the same value as command, status and independent feedback.
- 03
Run the baseline
Apply occupied startup, stable operation, mode change and controlled shutdown of one representative system from a clean start and record the expected evidence.
Evidence: Repeated runs produce the same bounded result.
Avoid: Changing several parameters before a baseline exists.
- 04
Challenge assumptions
Test freeze protection, smoke interface, lost airflow, failed valve or damper, sensor bias, utility loss and restart without changing the acceptance contract.
Evidence: Limits, timing and restart behavior reach defined states.
Avoid: Testing only one ideal sequence.
- 05
Isolate one failure
Introduce or analyse a mode, schedule, permissive, command, proof, loop, instrument, network or process-response fault and locate the first disagreement.
Evidence: The proving action distinguishes the leading hypotheses.
Avoid: Resetting, forcing or replacing before evidence is retained.
- 06
Close the evidence loop
Complete the sequence compared with approved design documents and commissioned on the actual bas and equipment and repeat the affected regression cases.
Evidence: A learner completes the surface by explaining the result, passing a changed case and identifying what still requires supervised target-equipment practice.
Avoid: Treating an acknowledged message or one successful rerun as handover.
Diagnostic matrix / 04
Symptoms, proving points and next actions
The table is a reasoning aid, not a parts-replacement chart. Preserve the initial symptom, inspect the named boundary and use the interpretation to choose the next controlled test. Site safety procedures and equipment manuals remain authoritative.
| Observed symptom | Inspect | Interpretation | Next proving action |
|---|---|---|---|
| The expected result is unclear | Requirement, initial state, actor, stimulus, units and pass condition | The learner, instructor and assessor may be solving different versions of the task. | Rewrite one observable acceptance case before continuing. |
| Internal state changes but the outcome does not | Request, final owner, output or service boundary and independent feedback | A software or interface indication proves intent at one layer, not the complete outcome. | Trace the first boundary after the changing state. |
| Normal case passes but an edge case fails | Limits, timing, simultaneous events, reset and restart assumptions | The implementation contains a hidden assumption exposed by the changed condition. | Add the failed boundary as a permanent regression case. |
| The failure disappears after reset | Original symptom, histories, diagnostics, timestamps and active cause | Reset changed evidence or state without proving the initiating cause. | Reproduce under a controlled condition and preserve pre/post-event data. |
| Simulator and target disagree | Model boundary, software version, task timing, I/O behavior, data types and configuration | A learning model and the intended target do not share one of the recorded assumptions. | Reduce the case and verify against current target documentation. |
| The result cannot be explained | Prediction, observation, proving action, alternative hypotheses and limitations | Activity occurred but the evidence is not yet transferable or reviewable. | Have the learner defend the signal path and repeat a changed case. |
Product evidence / 05
What the browser practice can actually demonstrate
The browser platform can retain programs, scenario results, attempts and observable machine state so practice is attached to evidence rather than seat time alone.
Where simulation stops
Browser training does not certify life-safety sequences, size plant, commission a building, reproduce a vendor BAS or authorize electrical and mechanical work.
Commissioning notebook / 06
Six cases that turn the concepts into evidence
Use these as written briefs rather than click-through instructions. For every case, state the expected condition before acting, retain the first useful observation and explain why the final result proves the requirement. A different program or component choice can still be correct when it produces the same bounded behavior and evidence.
Case 01
predict → observe → prove
Prove define the operating contract
Engineering context. building use, equipment, occupancy modes, setpoints, sensors, actuators, interlocks, safeties, alarms, trends and operator tasks. For building automation controls, sequences and diagnostics, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Write the acceptance case” stage of the workflow: convert building use, equipment, occupancy modes, setpoints, sensors, actuators, interlocks, safeties, alarms, trends and operator tasks into initial conditions, one stimulus and observable pass criteria. The acceptance record should show this result: another person can repeat the case without guessing the intended result. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The expected result is unclear” as one bounded deviation. Inspect requirement, initial state, actor, stimulus, units and pass condition The working interpretation is that the learner, instructor and assessor may be solving different versions of the task. The next proving action is to rewrite one observable acceptance case before continuing. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is using page completion or an animation as the acceptance criterion. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: What should a building automation course teach first? A defensible short answer is: Begin with equipment purpose, mode and signal paths before programming: demand, permissives, command, proof, environmental response, alarm and safe shutdown.
Case 02
predict → observe → prove
Prove map the evidence path
Engineering context. zone or plant demand through BAS logic, equipment command, physical proof, environmental response and supervisory display. Separate request, internal state, output or service, physical or user-visible result and independent feedback so each boundary can be inspected. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Build the map” stage of the workflow: document zone or plant demand through bas logic, equipment command, physical proof, environmental response and supervisory display and name who owns each state or decision. The acceptance record should show this result: every request and result has a source, destination and useful inspection point. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Internal state changes but the outcome does not” as one bounded deviation. Inspect request, final owner, output or service boundary and independent feedback The working interpretation is that a software or interface indication proves intent at one layer, not the complete outcome. The next proving action is to trace the first boundary after the changing state. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is using the same value as command, status and independent feedback. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: Can I learn BAS without a physical building lab? A defensible short answer is: You can learn sequence reasoning, I/O, alarms, trends and diagnosis in simulation, but target controllers, networks, field devices and life-safety interfaces still need supervised practice.
Case 03
predict → observe → prove
Prove prove normal operation
Engineering context. occupied startup, stable operation, mode change and controlled shutdown of one representative system. Run more than one cycle from a known state and retain the values, timings or artifacts that demonstrate repeatability. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Run the baseline” stage of the workflow: apply occupied startup, stable operation, mode change and controlled shutdown of one representative system from a clean start and record the expected evidence. The acceptance record should show this result: repeated runs produce the same bounded result. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Normal case passes but an edge case fails” as one bounded deviation. Inspect limits, timing, simultaneous events, reset and restart assumptions The working interpretation is that the implementation contains a hidden assumption exposed by the changed condition. The next proving action is to add the failed boundary as a permanent regression case. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is changing several parameters before a baseline exists. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: What should I learn first about building automation controls, sequences and diagnostics? A defensible short answer is: Start with the operating contract and evidence path: building use, equipment, occupancy modes, setpoints, sensors, actuators, interlocks, safeties, alarms, trends and operator tasks, followed by zone or plant demand through bas logic, equipment command, physical proof, environmental response and supervisory display. Add advanced features only after the baseline is predictable.
Case 04
predict → observe → prove
Prove exercise a boundary case
Engineering context. freeze protection, smoke interface, lost airflow, failed valve or damper, sensor bias, utility loss and restart. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Challenge assumptions” stage of the workflow: test freeze protection, smoke interface, lost airflow, failed valve or damper, sensor bias, utility loss and restart without changing the acceptance contract. The acceptance record should show this result: limits, timing and restart behavior reach defined states. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The failure disappears after reset” as one bounded deviation. Inspect original symptom, histories, diagnostics, timestamps and active cause The working interpretation is that reset changed evidence or state without proving the initiating cause. The next proving action is to reproduce under a controlled condition and preserve pre/post-event data. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is testing only one ideal sequence. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: How do I practise building automation controls, sequences and diagnostics effectively? A defensible short answer is: Use short cases with known initial conditions, a written prediction, one action and an observable result. Then alter a boundary or fault and explain why the evidence changed.
Case 05
predict → observe → prove
Prove diagnose a controlled fault
Engineering context. a mode, schedule, permissive, command, proof, loop, instrument, network or process-response fault. Preserve the first symptom, divide the system at a measurable boundary and change one condition only after predicting the result. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Isolate one failure” stage of the workflow: introduce or analyse a mode, schedule, permissive, command, proof, loop, instrument, network or process-response fault and locate the first disagreement. The acceptance record should show this result: the proving action distinguishes the leading hypotheses. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Simulator and target disagree” as one bounded deviation. Inspect model boundary, software version, task timing, I/O behavior, data types and configuration The working interpretation is that a learning model and the intended target do not share one of the recorded assumptions. The next proving action is to reduce the case and verify against current target documentation. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is resetting, forcing or replacing before evidence is retained. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: What counts as proof of competence? A defensible short answer is: A repeatable artifact or system result plus an explanation of the signal path is stronger than time spent, screenshots or a copied answer. Physical competence requires separate supervised evidence.
Case 06
predict → observe → prove
Prove transfer and hand over
Engineering context. the sequence compared with approved design documents and commissioned on the actual BAS and equipment. Restore normal state, remove temporary changes, repeat affected checks and document which claims remain limited to the learning environment. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Close the evidence loop” stage of the workflow: complete the sequence compared with approved design documents and commissioned on the actual bas and equipment and repeat the affected regression cases. The acceptance record should show this result: a learner completes the surface by explaining the result, passing a changed case and identifying what still requires supervised target-equipment practice. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The result cannot be explained” as one bounded deviation. Inspect prediction, observation, proving action, alternative hypotheses and limitations The working interpretation is that activity occurred but the evidence is not yet transferable or reviewable. The next proving action is to have the learner defend the signal path and repeat a changed case. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is treating an acknowledged message or one successful rerun as handover. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: Why test faults and restart behavior? A defensible short answer is: Because a mode, schedule, permissive, command, proof, loop, instrument, network or process-response fault or freeze protection, smoke interface, lost airflow, failed valve or damper, sensor bias, utility loss and restart can expose assumptions that never appear during ideal startup and steady operation.
Answer surface / 07
Questions people ask about Building automation training
These concise answers define the operating, training and product boundaries most often missed in broad summaries. The full workflow and diagnostic table above provide the evidence behind them.
What should a building automation course teach first?
Begin with equipment purpose, mode and signal paths before programming: demand, permissives, command, proof, environmental response, alarm and safe shutdown.
Can I learn BAS without a physical building lab?
You can learn sequence reasoning, I/O, alarms, trends and diagnosis in simulation, but target controllers, networks, field devices and life-safety interfaces still need supervised practice.
What should I learn first about building automation controls, sequences and diagnostics?
Start with the operating contract and evidence path: building use, equipment, occupancy modes, setpoints, sensors, actuators, interlocks, safeties, alarms, trends and operator tasks, followed by zone or plant demand through bas logic, equipment command, physical proof, environmental response and supervisory display. Add advanced features only after the baseline is predictable.
How do I practise building automation controls, sequences and diagnostics effectively?
Use short cases with known initial conditions, a written prediction, one action and an observable result. Then alter a boundary or fault and explain why the evidence changed.
What counts as proof of competence?
A repeatable artifact or system result plus an explanation of the signal path is stronger than time spent, screenshots or a copied answer. Physical competence requires separate supervised evidence.
Why test faults and restart behavior?
Because a mode, schedule, permissive, command, proof, loop, instrument, network or process-response fault or freeze protection, smoke interface, lost airflow, failed valve or damper, sensor bias, utility loss and restart can expose assumptions that never appear during ideal startup and steady operation.
Can browser practice replace official software or hardware?
No. It can build concepts and diagnostic reasoning. Exact firmware, I/O electrical behavior, networking, safety and commissioning require current official tools, documentation and target equipment.
How should progress be documented?
Keep the requirement, initial state, program or configuration, observed values, fault hypothesis, proving action, recovery result and a concise limitations statement.
Continue the signal path / 08
Related practice and reference pages
PLC simulator for HVACContinue from building use, equipment, occupancy modes, setpoints, sensors, actuators, interlocks, safeties, alarms, trends and operator tasks.HMI simulatorContinue from zone or plant demand through bas logic, equipment command, physical proof, environmental response and supervisory display.PID simulatorContinue from occupied startup, stable operation, mode change and controlled shutdown of one representative system.SCADA trainingContinue from freeze protection, smoke interface, lost airflow, failed valve or damper, sensor bias, utility loss and restart.SCADA versus HMI responsibilitiesContinue from a mode, schedule, permissive, command, proof, loop, instrument, network or process-response fault.PID temperature scenarioContinue from the sequence compared with approved design documents and commissioned on the actual bas and equipment.Explore plc training in south africaContinue from building use, equipment, occupancy modes, setpoints, sensors, actuators, interlocks, safeties, alarms, trends and operator tasks.How a VFD works field guideContinue from zone or plant demand through bas logic, equipment command, physical proof, environmental response and supervisory display.