Design Verification

System commissioning starts after the hotel developer has agreed to the features, design, and commercial details. This involves configuring the required mockup room jobs so that the devices can be programmed in the factory and installed with a standardized approach.

Commissioning then progresses to a temporary hotel job to allow end-to-end verification of all features. Commissioning is completed by creating a single hotel job file that is loaded into the onsite System Manager Server.

Recommended Process

This section outlines the tasks and tools for each phase of the commissioning process.

Phase Task Tools

Commercial

Identify customer requirements

  • Project intake form

  • Room alerts configuration intake form

System Design

Translate requirements into hardware design

  • Device Specification Sheets

  • Room Bill Of Quantities (BOQ)

  • Network Architecture and Site BOQ

Provide quote

  • Proposal Pricing Tool

  • Quotation

Mockup Room Commissioning

Prepare mockup room

  • Room layout

  • Hardware BOQ

  • Hardware single-line drawing

  • Circuit allocation table

  • Luminaire schedule

  • Room profile floor plan

  • Electrical drawings with indicative wiring arrangement

  • Device Installation Instructions

Define room logic

  • STR Template Library

  • Mockup room job files

  • Panel design and engraving

  • Preset scene definitions

  • Integration descriptions

  • Mockup room features table

  • Room controller IP address table*

  • Room mapping table

* The room controller IP address table is not required when using DHCP (Port Editor > Use static IP address is set to False).

Test interoperability

  • Third-party luminaire Interoperability test report and waiver

Complete Hotel Job file

  • Mockup room sign-off sheet
    (release for manufacturing)

  • Mockup room job files

  • Hotel job file

  • Notional energy load sign-off sheet

  • Room controller IP address table*

  • Floor gateway IP address table

  • DIP switch settings table

  • Site private key text file (must be kept secure)

* The room controller IP address table is not required when using DHCP (Port Editor > Use static IP address is set to False).

Deployment

Installation testing

  • System installation guide

  • Room layout

  • Electrical drawings

  • Gateway IP address table

  • Snagging list

System Manager setup

  • System Manager installation files

  • Room mapping table

  • Hotel job file

Commercial phase

In the Commercial phase of the project, the System Designer identifies the customer requirements by completing the Project intake form and the Room alerts configuration intake form.

The Intake Forms are simple Excel spreadsheets to help gather the customer requirements or summarize a tender request. The step-by-step format allows you to review all the available features together with the customer. Guided by system features and hotel room profiles, it helps you align features with customer needs and focus on value rather than specification.

Project reference tools

  • Project intake form

  • Room alerts configuration intake form

System design phase

In the design phase, the System Engineer translates the customer requirements into a specific feature set to be included in the quotation. They decide on the network architecture and produce a hardware BOQ for each room profile and for the site. To complete the design phase, the Proposal Manager prices the hardware design and feature offerings to produce a quotation.

Front-of-house, back-of-house, and architectural lighting can also be offered as part of the project.

Project reference tools

  • Device Specification Sheets

  • Room BOQ

  • Network architecture and site BOQ

  • Proposal pricing tool)

  • Quotation

Before proceeding, refer to the Architecture STR - System Architecture & Design learning pathway to ensure the design is STR compliant.

System building blocks

Ethernet gateway

An Ethernet gateway connects the SM server to a group of up to 25 rooms. Although they are referred to as floor gateways, they are centrally located in the server room.

Room controller

  • The design of every room must include one DDRC-GRMS-E controller.

  • Additional Dynalite load controllers may be added if more circuits are required.

  • If eight or fewer dimming circuits are required a DDRC-GRMS-E paired with a DDMC802 is often the best choice.

Expansions

  • Depending on the required control protocols you can add one or more expansion controllers:

    • DDRC810DT-GL relay controller.

    • DDMC802 multipurpose controller with the appropriate control modules.

    • DDBC120-DALI or DDBC320-DALI for DALI Addressable control.

    • DDBC1200 for 1-10V/DSI/DALI Broadcast control.

    • DDFCUC fan coil unit controller for controlling air conditioning.

Sensors

  • A core function of the system is determining real-time occupancy. This is used to move the room between states (Occupied/Unoccupied), which have parameters attached for temperature, lighting, power, curtains, etc. To achieve this, we need adequate sensor coverage combined with our tasking logic.

  • We recommend using a DUS360 sensor for cost and coverage balance, but any Dynalite sensor may be used.

  • In most standard rooms, two sensors are sufficient: Bedroom and Bathroom. In suites and large rooms, you can expand the design with additional sensors as required.

  • The AntiStumble feature uses the standard sensor with a lens cover, recessed into the wall or bedside table.

User Interfaces and Additions

  • One AntumbraDisplay is recommended for HVAC control. Other user interfaces can be added in accordance with the design requirements.

  • If you have wake-up lighting or are supporting multiple languages, AntumbraDisplay is a good choice for beside panels.

  • We recommend separating status/service and lighting control functions for guest clarity. In most cases it is good practice to use four button panels, especially where used as master panels at the entrance. Just because we can add a lot of functions to one panel doesn’t mean we always should.

  • A DLLI8I8O or DDRC-GRMS-E is required to drive the room status indicators on a corridor panel/doorbell and for any third-party panels.

  • We can source additional third-party environmental sensors such as a humidity sensor, if specified.

Control cable power

  • In a Dynalite network, all the controllers contribute power, and all other devices consume it.

  • We recommend that you calculate the network current in guestrooms to check that there is sufficient power available on the DyNet loop for all panels and sensors.

  • Our room BOQ template includes this calculation and allows you to build multiple room profiles easily.

  • Where required, you can add a DyNet power supply. It is better to not need one as it adds cost with no additional features for end users.

HVAC

There are two main types of HVAC control commonly found in hotels:

  1. FCU + Piped Water (Chilled/Heated)

    • Most commonly found in larger hotels (200+ rooms), this consists of central coolers/heaters and piped water around the building.

    • Valves in the room allow the water to pass through a Fan Coil Unit which cools/heats the air and blows it in to the room.

    • Our FCU controllers provide everything needed for these requirements:

      • Hot and Cold Valve control – power + (open/closed or variable 0-10 V or 0-24 V).

      • FCU fan motor control (Off/Low/Medium/High).

      • Configurable internal dead band logic to manage the achievement and maintenance of temperature setpoints.

      • Dry contact inputs for balcony doors, drip trays, filter sensors, etc.

  2. VRF/Split Units

    • Most commonly found in smaller hotels, these are often closed systems from consumer brands.

    • Fortunately, they almost always offer BACnet integration at the server level. With this link, we can either:

      1. Still provide the thermostat and pass setpoint and actual temperatures back for them to manage.
        OR

      2. Only send room state changes to trigger their system to shift between presets.

Example luxury room BOQ
Quantity Device Description

Relay Controllers

1 x

DDRC-GRMS-E
Room Controller

  • 7 switched lighting circuits.

  • 2 x 20 A switched circuits for GPO and Air Conditioning.

  • 2 dual curtain control relay channels.

  • 64 DMX Tx lighting channels.

  • 18 Dry contact inputs

  • 4 Digital outputs

  • UL924 input

  • Ethernet Port

Multipurpose Controllers

1 x

DDMC802

  • 8 channel multipurpose controller supports switched and dimmable loads up to 16 A total.

  • 8 Dry contact inputs

Integration Devices

1 x

DDFCUC

  • 0-10 V or 0-24 V control of the FCU hot and cold-water valve

Sensors

4 x

DUS360CR

  • Recessed 360° multifunction sensor for guest detection in bedroom and bathroom. Also used for AntiStumble in combination with DUS180WR cover plate.

2 x

DUS180WR

  • Wall-mounted cover plate enabling 180° multi sensor for AntiStumble night lighting.

User Interfaces

4 x

AntumbraButton &
DACM

  • 6-button backlit panel with temperature sensor, proximity sensor, and indicators to show which scene is active. For entrance, bathroom, bedside left and bedside right.

1 x

AntumbraDisplay &
DACM

  • 6-button backlit panel with LCD screen, temperature sensor, proximity sensor, and indicators used for HVAC control, displaying the current and set temperature, or the time and alarm status.

1 x

Corridor panel

  • Third-party panel with Doorbell and DND/MUR indicators.
Example Site BOQ
Quantity Device Description

Gateways

10 x

PDDEG-S Ethernet Gateway

  • Ethernet gateway to connect floors to building trunk network.

Computers

1 x

Windows Server with licensed Multiroom System Manager.

  • Central management and monitoring software to run on Windows Server or permanently running PC.

  • Browser-accessible dashboard providing real-time visibility of room status, system health, alerts, and event timeline.

Architecture

The system is comprised of room devices connected to a room controller in each guestroom. The rooms are then connected via floor Ethernet gateways to the System Manager server, which also integrates with other hotel systems.

Fast deployment is achieved with templated room configurations. By setting the DIP switches on the underside of the DDRC-GRMS-E, the installer can easily configure a unique box number. This also sets the box number range and area number range for devices in the room.

Floor gateways and DDRC-GRMS-E room controllers are given a unique IP address (IPv4 or IPv6) within a site-specific address range made available by the building’s IT administrator. This is recorded in the Room IP address table.

Ethernet to the room controller

One 40 Ethernet gateway per floor is connected via Ethernet/fibre to a 40 DDRC-GRMS-E room controller, then via an RS-485 sub-network to the room devices.

iah ethernet to room
Fibre connection requires an Optical Network Terminal (ONT).
DyNet addressing

The room controller DIP switch selects the following DyNet addressing:

  • Box number for the room controller.

  • Box number offset within the room.

  • Area offset within the room.

Area Distribution Example

Default Area Offset Multiplier = 20

20 areas per room x 50 rooms per floor = 1,000 areas per floor
1000 areas per floor x 64 floors = 64,000 areas total

50 rooms per floor x 64 floors (or other combinations): 3,200 rooms

The example would only have 48 rooms per floor due to not using DIP Switch setting 0 (zero) and the formula:
Offset = (DIP switch + 1) x Multiplier, meaning that Room 1 is allocated to areas 40 - 59.
Hence, Areas 0 - 19 and 20 – 39 are not used.
Within each room the first two areas are not used (Area 0 = all areas, Area 1 = unassigned area)
Twenty areas are recommended for typical guestrooms and forty or more areas for larger suites.
You can choose other floor ranges to suit different sized hotels.
Each floor Ethernet gateway supports connections for 25 DDRC-GRMS-E controllers.

The DDRC-GRMS-E has two sets of DIP switches labelled ID1 and ID2.

  • ID1 sets the DyNet addressing (room offset).

  • ID2 sets the Floor Gateway IP addressing in accordance with the Gateway Mapping.
Example DyNet addressing

The standard trunk-and-spur architecture employs address ranges with floor offsets and room offsets as in the below example (assuming floor offset = 1000 and room offset = 20):

  • Highest room number per floor = 48

  • Highest area number range per floor = 980-999

iah dynet address table
IP addressing

When an IPv4-based architecture is selected for the project:

  1. The floor IP address is programmed into the Ethernet gateway (PDDEG-S) on the floor.

  2. The room IP address is programmed into the DDRC-GRMS-E controller in the room.

IPv4 Example
Ethernet gateway Floor IPv4 address

Ground Floor

192.168.0.x

First Floor

192.168.1.x

Second Floor

192.168.2.x

Ground floor room

Room IPv4 address

Room 1

192.168.0.1

Room 2

192.168.0.2

Room 3

192.168.0.3

When an IPv6-based architecture is selected for the project:

  1. The floor IPv6 multicast address is programmed into the Ethernet gateway (PDDEG-S) on the floor.

  2. The DDRC-GRMS-E IPv6 address is automatically set based on its MAC address.

IPv6 Example
Ethernet Gateway Multicast IPv6 address

Ground Floor

FF12::4479:2:0:1

First Floor

FF12::4479:2:0:2

Second Floor

FF12::4479:2:0:3
The gateway mapping feature enables the IP address of every floor gateway to be programmed into every DDRC-GRMS-E so the connection can be selected by the ID2 DIP switches.