Blind Solutions AcademyC21 · The Specifier · CPD Category 1
Blind Solutions Academy · The Specifier · Practical Guide

Motorisation & IBMS Integration: The Practical How-To Guide

A step-by-step working companion to C21 — run the method on a live project, one layer and one zone at a time.

CourseC21
NQF Level7
FormatWorkflow + Checklists
How to use this guide

The four-layer pipeline


This guide turns the masterclass into a working method. Run the four layers in order for the system, then the per-lecture checklists below for every zone. Each checklist item is a deliverable; collected, they become your motorisation-and-integration specification and commissioning record.

LayerActivityOutput
1Actuator (motor)Torque-sizing worksheet & motor selection per blind (Nm, family, electronic limits)
2Control busControl-architecture decision record: bus per zone + feedback capability
3Integration interfaceGateway selection + per-blind/group object model on KNX/BACnet/Modbus; power & cabling topology
4IntelligenceSensor schedule, control logic, written priority hierarchy (wind/safety local)
Quick decision aid

Control bus → when to use it


BusFeedbackBest forAvoid when
Somfy RTSNone (one-way)Residential, simple retrofit, manual/timed controlBMS status / closed-loop sun-tracking required
io-homecontrolTwo-wayIntegrated retrofit, feedback without full cablingRF-hostile facade / very large deterministic estates
ZigbeeTwo-way (mesh)Third-party / IoT ecosystems2.4 GHz already congested with WiFi
Dry contactNone (open-loop)Safety/global overrides (fire, global wind, scenes)Individual addressing / position setting needed
RS485 / DC wiredFullLarge new-build, integration-critical, RF-hostileCabling genuinely impractical (existing building)
Specifier NoteFeedback capability is fixed by the motor's control variant at manufacture and is not field-changeable. Decide it on day one, or rule out BMS position reporting for the life of the building.
Per-lecture working checklists

Run the method, lecture by lecture


Step 1

From Manual to Motorised: Framing the Integration Problem

Motorising a blind is trivial; integrating shading into a building's intelligence is an engineering discipline, and this opening lecture establishes the distinction that the whole course depends on. A specifier who writes 'supply motorised blinds' onto a drawing has deferred every decision that actually determines whether the system works: motor torque adequacy, control protocol, power and cabling topology, the interface to the building management system, and the sensor and commissioning logic that makes the shading behave intelligently rather than merely move.

Commissioning & working checklist

Step 2

Tubular Motors: Anatomy, Families and the Somfy Reference

The tubular motor is the workhorse of shading motorisation, and a specifier must understand its anatomy before sizing or integrating one. This lecture dissects the tubular motor — the motor head, the gearbox reduction, the integral limit system, the thermal cut-out and the crown-and-drive adaptor set that couples it to a specific tube diameter — and maps the Somfy product families that have become the de facto reference across the industry.

Commissioning & working checklist

Step 3

Motor Sizing: Torque, Loads and the Newton-Metre Calculation

Motor sizing is where specification becomes engineering, and getting the torque calculation right is the single most important technical decision in motorisation. This lecture builds the torque calculation from first principles: the load the motor must overcome is the weight of the fabric or slat package plus the bottom bar acting at the radius of the loaded tube, and the required torque is that force multiplied by the effective radius, divided by mechanical efficiency, with a safety margin applied.

Commissioning & working checklist

Step 4

Control Buses: RTS, io-homecontrol, Zigbee and the RF vs Wired Decision

Once the motor is sized, the next decision is how it receives commands — and the choice of control bus governs reliability, feedback, integration capability and retrofit feasibility for the life of the building. This lecture compares the dominant control technologies: Somfy RTS (one-way 433 MHz radio, simple and ubiquitous but no feedback), io-homecontrol (two-way encrypted radio with position feedback and interoperability across io-partner brands), Zigbee (mesh radio used in third-party and IoT ecosystems), and wired control (dry-contact, RS485/digital-bus and DC data-over-cable).

Commissioning & working checklist

Step 5

Power, Cabling and Low-Voltage Topology

Motorised shading is an electrical installation, and the power and cabling topology decided at design stage determines whether the system is safe, serviceable and integration-ready or a maintenance liability. This lecture covers the practical electrical engineering: AC mains versus low-voltage DC distribution, circuit grouping and the number of motors per circuit, cable types and sizing for power and for data buses, the segregation of power from data and from other building services, and the provision of isolation, local switching and accessible junctions.

Commissioning & working checklist

Step 6

Integration Interfaces I: Dry Contacts and the Gateway Concept

Integration begins with the simplest interface and the most important concept: the dry contact and the gateway. This lecture explains how a shading system exposes control to the wider building — at the crudest level through volt-free dry contacts that any controller can drive, and at the proper level through a gateway that translates between the shading manufacturer's native protocol and a building automation protocol.

Commissioning & working checklist

Step 7

Integration Interfaces II: KNX, BACnet and Modbus

This lecture gives the specifier working fluency in the three building-automation protocols that a shading gateway speaks: KNX, BACnet and Modbus. We characterise each — KNX as the decentralised, peer-to-peer European building-control standard with its group-address model; BACnet as the HVAC-centric building-automation protocol with its rich object/property model and BACnet/IP and MS/TP variants; and Modbus as the simple, robust, register-based industrial protocol common on device-level and legacy links.

Commissioning & working checklist

Step 8

Sensors and Intelligence: Sun, Wind and Daylight Logic

Motors and protocols give a blind the ability to move; sensors and logic give it the intelligence to move correctly, and this lecture builds the sensing and control strategy that turns motorised shading into a daylight- and safety-management system. We cover the sensor suite: rooftop global and facade-specific sun (irradiance/lux) sensors, the wind sensor (anemometer) that drives the non-negotiable high-wind retraction of exterior shading, rain and temperature sensors, and interior glare/lux sensors for closed-loop daylight control.

Commissioning & working checklist

Step 9

Designing the Integrated System: Architecture and Zoning

With motors, buses, interfaces, power and sensors understood individually, this lecture assembles them into a coherent system architecture — the drawing-and-schedule deliverable that a controls contractor builds from. We work through facade and zone definition (grouping blinds by orientation, room and control intent), the controller hierarchy (local shading controllers, gateways, BMS), the network and addressing plan, and the head-end and user-interface layer (wall keypads, touch panels, BMS graphics, mobile apps).

Commissioning & working checklist

Step 10

Commissioning: From Installed Hardware to Verified Behaviour

Installed and wired is not the same as commissioned, and this lecture sets out the structured commissioning process that turns a physically complete shading installation into a verified, documented, intelligent system — the stage projects most often skimp and most often regret. We sequence the work: motor limit-setting and direction checking, address assignment and group/zone configuration, gateway and protocol binding (KNX group addresses, BACnet object mapping, Modbus register verification), sensor calibration and the critical wind-retraction proving, then sun-tracking and daylight-logic tuning, scene programming, and integrated testing with the BMS and lighting.

Commissioning & working checklist

Step 11

Standards, Safety and Compliance: IEC 60335-2-97 and the SA Frame

Motorised shading sits inside a safety and compliance framework that a specifier must map, because non-compliance stalls approvals, voids warranties and creates liability. This lecture decodes the key standards: IEC 60335-2-97 as the particular safety standard for the drives of rolling shutters, awnings, blinds and similar equipment; the general appliance-safety standard IEC 60335-1 beneath it; the South African electrical installation frame of SANS 10142-1 and the Certificate of Compliance; the wind-action standard SANS 10160-3 that underpins exterior-blind retraction setpoints; and the EMC and low-voltage directive context for the equipment itself.

Commissioning & working checklist

Step 12

The Motorisation & Integration Specification: Documentation and Hand-off

The course closes where real projects live — in the specification and documentation that carry the design into procurement, installation and operation. This capstone lecture assembles every preceding deliverable into the two artefacts that govern a motorised, integrated shading project: the motorisation-and-integration specification and the project documentation set.

Commissioning & working checklist

Self-assessment

Assessment Question Bank (10 MCQs)


Application-based questions. Minimum pass mark 70% (7 of 10). Reveal each answer to check your reasoning and the section it draws on.

Question 1
A roller blind has 7.2 m2 of fabric at 0.35 kg/m2 plus a 1.8 kg bottom bar, on a tube where fabric build-up makes the effective lifting radius about 0.030 m. Taking gearbox/assembly efficiency at 0.7 and applying a 1.3x margin, which standard Somfy motor rating is the soundest selection?
AA 6 Nm motor — the required torque is roughly 2.4 Nm after efficiency and margin, so 6 Nm is a conservative, quiet selection
BA 0.5 Nm motor, because the fabric is light
CA 40 Nm motor, because roller blinds always need high torque
DTorque cannot be determined without the motor's rpm
Show answer & explanation
Correct: A. Suspended mass = 7.2 x 0.35 + 1.8 = 4.32 kg; F = 4.32 x 9.81 = 42.4 N; tube torque T = F x r = 42.4 x 0.030 = 1.27 Nm; motor-side = 1.27 / 0.7 = 1.82 Nm; x 1.3 margin = 2.4 Nm. The next standard rating up that gives quiet, conservative running is 6 Nm (Lecture 3). The other values ignore the calculation entirely.
Question 2
A client wants the BMS dashboard to display the actual position of every blind. A specifier is choosing the control bus. Which choice makes this impossible and why?
Aio-homecontrol, because it is encrypted
BRS485 wired, because it cannot be addressed individually
CSomfy RTS, because it is a one-way protocol that sends no position feedback back from the motor
DZigbee, because it uses a mesh topology
Show answer & explanation
Correct: C. RTS is one-way 433 MHz radio: the controller can command the motor but the motor reports nothing back, so individual position status cannot reach the BMS (Lecture 4). io-homecontrol, Zigbee and RS485 are all two-way/feedback-capable. Feedback capability is fixed by the motor's control variant at manufacture, so this is an architecture decision, not a later add-on.
Question 3
On a large new-build commercial tower with a BACnet/IP BMS, the specifier needs individually-addressable blinds with position feedback that the BMS can read and write. What is the most appropriate integration approach?
AConnect each motor to the BMS with a single up/down dry contact per blind
BUse RTS motors and a handful of dry-contact group triggers to the BMS
CUse feedback-capable wired/io motors behind a shading gateway that exposes each blind as BACnet objects (e.g. Analog Value for position, status objects) to the BACnet/IP BMS
DSpecify Modbus because it is the only protocol blinds support
Show answer & explanation
Correct: C. Real integration of an addressable, feedback-rich system needs a gateway translating the shading bus to the building's protocol — here BACnet/IP — exposing each blind as BACnet objects the BMS reads and writes (Lectures 6-7). Dry contacts are open-loop and coarse; RTS gives no feedback; Modbus is not the only option and is register-based without an object model.
Question 4
An external screen on a coastal facade must retract in high wind. Where must the wind-retraction logic execute, and why?
AIn the BMS, so it can be coordinated with HVAC scheduling
BLocally in the dedicated shading controller, hard-wired to the anemometer threshold, so it pre-empts all other commands and does not depend on a BMS round-trip or BMS availability
CIn the cloud, for remote monitoring
DIn the wall keypad the occupant uses
Show answer & explanation
Correct: B. Wind retraction is a life-and-property safety function and the top of the priority hierarchy; it must run in fast local logic independent of the BMS, because a BMS delay, fault or reboot must never leave an exterior blind deployed in a gale (Lecture 8 — the George coastal storm case). Comfort and energy logic may live in the BMS, but wind/safety logic is local.
Question 5
A specifier writes 'motors compliant with IEC 60335-2-97'. What does this requirement actually govern?
AThe colour and aesthetic finish of the headrail
BThe building's overall energy consumption target
CThe particular electrical and mechanical safety of the drive — insulation, temperature-rise limits, the thermal cut-out behaviour and protection against hazards — working with the general standard IEC 60335-1
DThe width of the data cable used for the bus
Show answer & explanation
Correct: C. IEC 60335-2-97 is the particular safety standard for drives of rolling shutters, awnings and blinds, used with the general standard IEC 60335-1; it governs insulation, temperature rise, the intermittent-duty thermal cut-out and protection against hazards (Lecture 11). It is why a reputable motor trips and cools rather than burning out. It does not address aesthetics, building energy targets or cable width.
Question 6
On a new-build the architect wants 1,200 blinds to behave intelligently per facade. The proposed architecture is a single flat control group. What is the primary problem?
AIt is ideal — one group is the simplest and best design
BEvery sun event commands all 1,200 motors at once: it cannot let the shaded facade behave differently from the sunlit one and creates a severe coincident-load problem on the power circuits
CFlat grouping improves feedback resolution
DIt reduces the number of addresses needed, which is the main design goal
Show answer & explanation
Correct: B. Sun and shadow logic acts per orientation, so zoning by facade (then by room/use) is the architecture's foundation (Lecture 9 — the Rosebank case). A flat group moves everything together, prevents per-facade behaviour, and slams all motors on at once — a coincident-load issue for circuits (Lecture 5). Proper zoning, not address-count minimisation, is the goal.
Question 7
During commissioning, which step is the non-negotiable, witnessed verification for an installation with exterior shading?
AConfirming the fabric colour matches the sample
BPhysically proving that an over-threshold wind signal drives the exterior blinds to retract through the local controller logic, independent of the BMS, within the required time
CChecking the warranty card is filled in
DVerifying the mobile app icon appears on the client's phone
Show answer & explanation
Correct: B. The witnessed wind-safety test proves the most critical safety function actually works through local logic, not just that it was configured on paper (Lecture 10 — the Centurion skimp, and the George storm). A configured-but-unproven wind function is exactly how exterior screens get destroyed. Colour, warranty and app cosmetics are not safety verifications.
Question 8
A building runs KNX for lighting/room control and BACnet/IP for HVAC and the central BMS. How should shading integration be specified?
APick one protocol arbitrarily and ignore the other system
BSpecify a controller/gateway that presents the required objects on both interfaces — scene/switch objects on the KNX side and position/status/override objects on the BACnet/IP side
CUse only dry contacts so no protocol is needed
DRequire the BMS vendor to rewrite the lighting system onto BACnet
Show answer & explanation
Correct: B. Multi-protocol buildings are normal; the shading must match what each adjacent system speaks, so a controller/gateway carrying both interfaces presents KNX objects for lighting-coordinated scene control and BACnet objects for BMS sun-tracking and energy coordination (Lecture 7 — the Midrand campus). Choosing one arbitrarily, reverting to dry contacts, or re-platforming the lighting are all wrong.
Question 9
An exterior zip-screen blind is being sized. Why is the gravity (fabric weight) torque term often not the governing load?
ABecause exterior fabrics are always lighter than interior ones
BBecause windload acting on the fabric area, derived from the SANS 10160-3 regional wind pressure, can dwarf the gravity term and becomes the dominant design force the motor, brackets and fixings must resist
CBecause exterior motors have no torque rating
DBecause gravity does not act on vertical surfaces
Show answer & explanation
Correct: B. For exterior shading the wind force on the exposed fabric area, computed from SANS 10160-3 site wind data, typically exceeds the gravity lift term and is the dominant design load for the motor, brackets and fixings (Lectures 3 and 11). It is also why the wind class and retraction setpoint matter. Exterior fabrics are usually heavier, motors are torque-rated, and gravity certainly loads a vertical blind's bottom bar.
Question 10
A quantity surveyor proposes deleting the BACnet gateway and downgrading io motors to one-way RTS to cut cost. Which specification approach best protects the integrated system?
AList the gateway and motors by part number only, leaving cost to decide
BMark integration as 'optional smart features' so it can be removed cleanly
CRemove the performance and safety rationale so the document reads more simply
DBind each requirement to its consequence — that RTS forfeits position feedback and sun-tracking verification, that removing the gateway collapses addressable blinds into a few dry-contact groups and forfeits the daylight-harvesting energy benefit, and that any wind logic must remain local for safety
Show answer & explanation
Correct: D. A specification survives value engineering when deletion visibly threatens function, the energy business case and safety (Lecture 12 — the Sandton retrofit). Tying the gateway to integration, feedback to sun-tracking and BMS status, and wind logic to safety/liability makes the consequences of removal explicit, so cost pressure redirects rather than guts the system. Part-numbers-only, 'optional', or stripped rationale all invite deletion.
Capstone

Specification deliverable template


Assemble the outputs from every checklist above into a single motorisation-and-integration specification with this spine: