Networked Lighting Controls Ownership Commissioning & Handover

The owner should be able to change a schedule after handover

A networked lighting project is not complete merely because the installer can dim a room from a phone. The facility needs to locate devices, understand zones, change permitted settings and obtain support when staff or room uses change. Those operating tasks should be part of the purchase and commissioning scope.

For commercial lighting controls, specify an owner handover that connects the physical installation to its configuration, access arrangements and service responsibilities. A feature list describes capabilities; the handover must show how this building will use and maintain them.

Decide which functions the facility will own

Identify routine tasks such as changing holiday schedules, adjusting a permitted scene, investigating a sensor complaint and replacing a failed device. Decide which tasks facilities staff will perform, which require an installer and which depend on manufacturer support.

Ask vendors to identify required controllers, gateways, applications and optional services. For each promised function, establish where the configuration resides and what access is needed to change it. Do not assume that every platform supports the same user roles, exports or recovery process.

The DLC NLC V5.2 requirements apply to networked control systems, while luminaires, retrofit kits and lamps are qualified separately under the SSL program. A system qualification is useful evidence of the identified system's capabilities; it does not approve every fixture, integration or proposed project arrangement.

If an incentive matters, verify the exact system and project requirements with the administering program. Keep that financial decision separate from the demonstration that the installed controls perform the owner's sequence.

Make the device map the common reference

Assign each physical device a location and connect its identifier to the room, fixture schedule and control group. Use the platform's terminology accurately, but include room names that facilities staff recognize. A software group called “Area 12” needs a clear relationship to the actual building.

The Lightcloud Blue installation overview recommends placing device IDs on a device table or lighting layout and includes commissioning and site-function verification. This is a useful manufacturer example of the link between physical devices and software assignments.

When reviewing RAB lighting controls, identify the actual platform and generation. Documentation for one offering should not be assumed to describe every RAB control system.

Establish access and recovery while the installer is present

Agree on the owner-controlled account arrangement, authorized users and recovery contact using the platform's supported process. Keep passwords and recovery credentials out of public as-built documents. Record who is responsible and where approved access information is maintained.

Demonstrate a routine owner task, such as finding a room and viewing its schedule, with the intended staff access. Identify the process for transferring responsibility when a staff member leaves. A project remaining solely on a contractor's account or phone can leave ownership unclear even when daily lighting continues to work.

Ask how configuration can be preserved and restored. Where exports are supported, retain a final accepted version; where they are not, agree on a readable alternative and its limitations. Use documented recovery verification rather than deleting a site or resetting equipment as an informal test.

Commission the agreed behavior

Use the sequence of operations to choose test cases. Include occupancy, vacancy, daylight response, schedules, scenes and manual overrides as applicable. For each case, establish the starting state, input and expected output before observing the result.

Also identify the documented behavior when a network connection, gateway or mobile device is unavailable. These are different conditions, and the answer depends on system architecture. Arrange permitted demonstrations with the manufacturer and facility without disrupting required lighting or safety functions.

Capture the final configuration after corrections. An export made before acceptance may preserve the settings that caused the failures rather than the settings the owner approved.

Clarify service scope and ongoing costs

RAB's Lightcloud system support page describes commissioning, technical support and training subject to its applicable terms. Review the agreement for the actual system being purchased; do not transfer that offering automatically to another platform or generation.

Identify who handles replacement devices, software updates, retraining and configuration changes. Ask which services are included, which incur charges and what information support needs to identify the installation. Keep that contact and service path with the device map.

Involve the owner's technology representative where connectivity, accounts or organizational security policies affect the deployment. A wireless control description does not by itself settle those operational requirements.

Keep energy reporting separate from functional acceptance

If the system provides energy data, establish whether it measures power or estimates it from configured values and operating states. Identify the time basis, reporting interval, missing-data behavior and available exports before using the dashboard for savings claims.

Finish handover with a practical owner exercise and an assigned list of remaining items. Preserve the accepted configuration alongside later changes, and provide retraining when responsibility shifts. The owner should leave commissioning able to operate the agreed functions and obtain a supported correction when the building changes.