AU2021107221A4

AU2021107221A4 - System and method for generating building automations from a lighting plan

Info

Publication number: AU2021107221A4
Application number: AU2021107221A
Authority: AU
Inventors: James Cole; David O'driscoll
Original assignee: Kiko Automation Pty Ltd
Current assignee: Kiko Automation Pty Ltd
Priority date: 2021-08-25
Filing date: 2021-08-25
Publication date: 2021-12-09
Anticipated expiration: 2029-08-25

Abstract

SYSTEM AND METHOD FOR GENERATING BUILDING AUTOMATIONS FROM A LIGHTING PLAN ABSTRACT A system (100) and method for generating building automations from a lighting plan is disclosed. The system (100) comprises a user device (105) using which a lighting design for a lighting plan of a floor plan is created, wherein the lighting design defines relationship between the automation devices (115) and instructions on automations to be configured for the automation devices (115). The lighting design is exported to the automation hub (110), wherein the automation hub (110) creates user interfaces based on the lighting design, creates configuration policies for the automation devices (115) based on the relationship between the automation devices (115) and the instructions on the automations defined in the lighting design, and targeted technology and protocol, and creates virtual automation devices that matches the behaviour of real-world automation devices. 12 100 105 110 I 115 115a 115b 115c 115d 115e FIGURE1I

Description

100 105

110

I 115

115a 115b 115c 115d 115e

FIGURE1I

SYSTEM AND METHOD FOR GENERATING BUILDING AUTOMATIONS FROM A LIGHTING PLAN TECHNICAL FIELD:

[001] The present invention generally relates to building automations, and more particularly to a system and method for generating building automations from a lighting plan.

BACKGROUND:

[002] Generally, building automation refers to automation of a building's HVAC (heating, ventilation, and air conditioning) systems, lightings, shadings, access control and security systems, etc., through a building management system. The objective of such automation is to enhance the occupants' comfort, to improve the operation efficiency of the building system, to reduce the energy consumption, to enable remote operations and hence to reduce overall operation and maintenance cost.

[003] Conventionally, building automation devices are manually configured after commissioning of the devices. That is, for example, upon commissioning the devices such as lights, sensors, Human Interface Devices (HIDs), etc., the commissioned devices are configured either using a user interface (UI) for creating the automations or by writing the configuration files manually. Such as process require skilled persons for writing the configuration files and time consuming.

[004] Thus, there exists a need for a solution to overcome above-mentioned deficiencies.

SUMMARY:

[005] This summary is provided to introduce a method for configuring automation devices for generating building automations, in a building automation system. The method comprises, receiving the lighting plan of a floor plan, generating a lighting design for the lighting plan of the floor plan, the lighting design defining relationship between the automation devices in the floor plan and instructions on automations to be configured for the one or more automation devices, exporting the lighting design to an automation hub, grouping the automation devices based on layout and relationship between the automation devices within the lighting design, creating user interfaces based on the lighting design, creating configuration policies for the one or more automation devices based on the relationship between the automation devices and the instructions on the automations defined in the lighting design, and targeted technology and protocol, and creating virtual automation devices that matches the behaviour of real-world automation devices.

[006] These aspects and advantages will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.

BRIEF DESCRIPTION OF FIGURES:

[007] To further clarify advantages and aspects of the disclosure, a more particular description of the disclosure will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings, wherein:

[008] Figure 1 shows a system for generating building automations from a lighting design in accordance with an embodiment of the present disclosure;

[009] Figure 2 is a process flow diagram illustrating the method for configuring lighting automation devices for generating building automations, in the building automation system, in accordance with an embodiment of the present disclosure;

[010] Figure 3 shows exemplary user interfaces created using YAML template in accordance with an embodiment of the present disclosure; and

[011] Figure 4 shows an exemplary configuration that would be generated as part of the process.

[012] It may be noted that to the extent possible, like reference numerals have been used to represent like elements in the drawings. Further, those of ordinary skill in the art will appreciate that elements in the drawings are illustrated for simplicity and may not have been necessarily drawn to scale. For example, the dimensions of some of the elements in the drawings may be exaggerated relative to other elements to help to improve understanding of aspects of the disclosure. Furthermore, the one or more elements may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

DETAILED DESCRIPTION:

[013] It should be understood at the outset that although illustrative implementations of the embodiments of the present disclosure are illustrated below, the present disclosure may be implemented using any number of techniques, whether currently known or in existence. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.

[014] The term "some" as used herein is defined as "none, or one, or more than one, or all." Accordingly, the terms "none," "one," "more than one," "more than one, but not all" or "all" would all fall under the definition of "some." The term "some embodiments" may refer to no embodiments or to one embodiment or to several embodiments or to all embodiments. Accordingly, the term "some embodiments" is defined as meaning "no embodiment, or one embodiment, or more than one embodiment, or all embodiments."

[015] The terminology and structure employed herein is for describing, teaching and illuminating some embodiments and their specific features and elements and does not limit, restrict or reduce the spirit and scope of the claims or their equivalents.

[016] More specifically, any terms used herein such as but not limited to "includes," "comprises," "has,'''consists," and grammatical variants thereof do NOT specify an exact limitation or restriction and certainly do NOT exclude the possible addition of one or more features or elements, unless otherwise stated, and furthermore must NOT be taken to exclude the possible removal of one or more of the listed features and elements, unless otherwise stated with the limiting language "MUST comprise" or "NEEDS TO include."

[017] Whether or not a certain feature or element was limited to being used only once, either way it may still be referred to as "one or more features" or "one or more elements" or "at least one feature" or "at least one element." Furthermore, the use of the terms "one or more" or "at least one" feature or element do NOT preclude there being none of that feature or element, unless otherwise specified by limiting language such as "there NEEDS to be one or more. . . " or "one or more element is REQUIRED."

[018] Unless otherwise defined, all terms, and especially any technical and/or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having an ordinary skill in the art.

[019] Reference is made herein to some "embodiments." It should be understood that an embodiment is an example of a possible implementation of any features and/or elements presented in the attached claims. Some embodiments have been described for the purpose of illuminating one or more of the potential ways in which the specific features and/or elements of the attached claims fulfil the requirements of uniqueness, utility and non-obviousness.

[020] Use of the phrases and/or terms such as but not limited to "afirst embodiment," "a further embodiment," ''an alternate embodiment," ''one embodiment," "an embodiment," "multiple embodiments," "some embodiments," "other embodiments," "further embodiment", "furthermore embodiment", "additional embodiment" or variants thereof do NOT necessarily refer to the same embodiments. Unless otherwise specified, one or more particular features and/or elements described in connection with one or more embodiments may be found in one embodiment, or may be found in more than one embodiment, or may be found in all embodiments, or may be found in no embodiments. Although one or more features and/or elements may be described herein in the context of only a single embodiment, or alternatively in the context of more than one embodiment, or further alternatively in the context of all embodiments, the features and/or elements may instead be provided separately or in any appropriate combination or not at all. Conversely, any features and/or elements described in the context of separate embodiments may alternatively be realized as existing together in the context of a single embodiment.

[021] Any particular and all details set forth herein are used in the context of some embodiments and therefore should NOT be necessarily taken as limiting factors to the attached claims. The attached claims and their legal equivalents can be realized in the context of embodiments other than the ones used as illustrative examples in the description below.

[022] In accordance with an embodiment of the present disclosure, a system and method for generating building automations from a lighting plan is disclosed. The proposed system and method allow a building's lighting design to be imported into a building automation hub to automatically create/configure the devices (automation devices) which will be installed in the building. The automation devices as described herein may include but not limited to lighting devices, cameras, sensors, heating, ventilation, and air-conditioning (HVAC) devices, human interface devices (HIDs), etc.

[023] Figure 1 shows a system for generating building automations from a lighting design in accordance with an embodiment of the present disclosure. As shown, the system 100 comprises a user device 105, an automation hub 110 and a plurality of automation devices 115 (for example, 115a, 115b to 115e), wherein the user device 105, the automation hub 110 and the automation devices 115 are communicatively connected via known wired or wireless communication networks. The automation devices 115a to 115e may include but not limited to lighting devices, cameras, heating, ventilation, and air-conditioning (HVAC) devices, switches, sensors (motion sensors, light sensors, counters, etc.), human interface devices (HIDs), etc., that are often implemented in homes, offices, industries or in any given space. Such devices have wired or wireless communication capabilities to communicate with each other or with the automation hub

110. It is to be noted that, the term "automation devices" refers to any electrical, electronic, electro-mechanical devices are that used in building or home automations.

[024] The user device 105 may be a computer or computer server or a network of computers associated with a designer, and may include one or more processors, associated processing modules, interfaces and storage devices communicatively interconnected to one another through one or more communication means for communicating information. The storage associated with the user device 105 may include volatile and non-volatile memory devices for storing information and instructions to be executed by the one or more processors and for storing temporary variables or other intermediate information during processing. In one embodiment of the present disclosure, the user device 105 comprises a lighting design software that enables the lighting designer to specify the automation devices and physical layout of the automation devices that make up a lighting design for a floor building/area.

[025] The automation hub 110 may be a desktop computer, a tablet, a smartphone, or any dedicated electronic device (often referred as gateway device) which connects the automation devices 115 and operates the one or more connected automation devices 115. As well known in the art, the automation hub 110 comprises one or more processors, memory unit, network interface modules, user interface modules, hardware interface modules, etc., for managing the one or more connected automation devices 115. In one embodiment of the present disclosure, the automation hub 110 comprises a configuration import module configured for receiving a lighting design as an input and produces a configuration for the automation devices and hence for the generating building automation. Further, in one embodiment, the automation hub 110 comprises a automation building module that enables control, automation and monitoring of the connected automation devices. The manner in which the automation devices 115 are configured for generating building automations is described below in further details. It is to be noted the lighting is considered as an example in this disclosure, however, the system may include other devices such as HVACs as described, and the same may be automatically configured with or without minor modifications.

[026] Figure 2 is a process flow diagram illustrating the method for configuring lighting automation devices for generating building automations, in the building automation system, in accordance with an embodiment of the present disclosure. At step 205, a lighting design plan is created for a given floorplan or building. That is, using the user device 105, a lighting designer makes a lighting plan by laying out lights, sensors, and HIDs on the floorplan. Further as shown at step 210, in one embodiment of the present disclosure, a lighting design is generated, by the lighting designer, for the lighting plan of the floor plan, the lighting design defining relationship between the automation devices 115 in the floor plan and instructions on automations to be configured for the one or more automation devices 115. In other words, the lighting design defines one or more configuration policies for the automation devices 115 or for the floorplan. In one example, if a light specified in the design supports CCT tuning then the designer may select the same and specify that it should use a "Dayshift" automation. In another example, if a room contains a motion sensor (PIR) in the design then the designer may select the same and specify that the lights in the room (or a subset of the lights) should be motion activated. Similarly, the designer may define one or more configuration policies for the one or more automation device 115 or for the floorplan. Then the generated lighting plan is exported to the automation hub 110.

[027] At step 215, upon importing the lighting design, the automation hub 110 groups the automation devices and creates user interfaces based on the lighting plan and design, that is, based on the relationship between the one or more automation devices and the one or more policies defined by the designer. It is to be noted that the grouping is performed for various reasons. In one example, lights in lighting designs are usually grouped by circuit as well as room, and groups needed to be created in the automation software for things like all groups in a room, all groups in a circuit, all lights in a building and all circuits in a room. In another example, lights may need to be grouped by functionality, for example, all lights that support RGB colour, all lights that support brightness adjustment or all lights that support colour temperature tuning.

[028] In one embodiment of the present disclosure, the user interfaces for the one or more automation devices 115 are generated using YAML template. Figure 3 shows exemplary user interfaces created using YAML template in accordance with an embodiment of the present disclosure.

[029] Then, at step 220, the automation hub 110 creates one or more configuration for the one or more automation devices 115 present in the lighting plan. In one embodiment of the present disclosure, the one or more configuration policies for the one or more automation devices 115 are created based on the relationship between the automation devices 115, and the instructions on the automations defined in the lighting design, and targeted technology and protocol. That is, the automation hub 110 reads the specified automation types from the lighting design (instructions on the configuration policies), interpolates the device names and/or device IDs for a specific automation into an automaton template or pre-set automation structure, and generates configurations in a format that can be imported into the building automation module of the automation hub or equivalent environment. Below are the examples of some of the automations that are automatically configured by the automation hub 110.

• Turning lights ON when motion is detected and turning OFF again after a period of inactivity. • Turning of high load devices such as hot water heaters, heating and cooling systems, pool pumps etc., based on current solar generation. • Switching ON/OFF or adjusting devices based on power spot market prices or solar generation. • Opening windows and/or blinds in conjunction with heating and cooling systems to optimise comfort and power consumption. • Matching brightness and colour temperature for CCT tuneable lights based on inputs such as time of day, sunrise/sunset and/or external conditions (referred to as Dayshift).

• Sleep, arrival, and departure routines which switch on/off or adjust devices based on whether the building is occupied, empty or occupants are sleeping.

[030] Figure 4 shows an exemplary configuration that would be generated as part of the process. This example automatically turns ON a light when motion is detected, and the sun is below the horizon and then switches it OFF after 120 seconds.

[031] Then, at step 225, the automation hub 110 creates virtual automation devices that matches the behaviour of real-world automation devices 115. The generated virtual automation devices enable the designer to perform a simulation of how the system behaves with real automation devices in the given floorplan or building. The virtual automation devices are then swapped for real automation devices 115 during the commissioning or installation process.

[032] The system and method for generating building automations from a lighting plan disclosed in the present disclosure automates the process of configuration of the automation devices and further enable real-time simulation of the devices by creating virtual automation devices present in the lighting design or the lighting plan.

[033] Further, the system and method disclosed in the present disclosure, allows a building's lighting design to be imported into a building automation hub to automatically create/configure the devices which will be installed in the building, thereby solving the problem of configuring the hub device to match the design.

[034] While certain present preferred embodiments of the disclosure have been illustrated and described herein, it is to be understood that the disclosure is not limited thereto. Clearly, the disclosure may be otherwise variously embodied, and practiced within the scope of the following claims.

Claims

We Claim:

1. A method for configuring automation devices (115) for generating building automations, in a building automation system (100), the method comprising: receiving the lighting plan of a floor plan; generating a lighting design for the lighting plan of the floor plan, the lighting design defining relationship between the automation devices (115) in the floor plan and instructions on automations to be configured for the one or more automation devices (115); exporting the lighting design to an automation hub (110); grouping the automation devices (115) based on layout and relationship between the automation devices (115) within the lighting design; creating user interfaces based on the lighting design; creating configuration policies for the one or more automation devices (115) based on the relationship between the automation devices (115) and the instructions on the automations defined in the lighting design, and targeted technology and protocol; and creating virtual automation devices that matches the behaviour of real-world automation devices (115).

2. The method as claimed in claim 1, wherein creating the configuration policies comprises the steps of: reading the instructions on the automations to be configured for the one or more automation devices from the lighting design; interpolates the automation device IDs for a specific automation into an automaton template; and generating configuration policies in a format that can be imported into the building automation module of the automation hub or equivalent environment.

3. The method as claimed in claim 1, wherein the user interfaces are created using YAML template.

4. The method as claimed in claim 1, wherein the virtual automation devices are swapped with automation devices (115) during the commissioning.

5. A system for configuring automation devices (115) for generating building automations, the system comprising: a user device (105) enabling generation of a lighting design for a lighting plan of a floor plan, the lighting design defining relationship between the automation devices (115) in the floor plan and instructions on automations to be configured for the one or more automation devices (115); and a automation hub (110) configured for: grouping the automation devices based on layout and relationship between the automation devices within the lighting design; creating user interfaces based on the lighting design; creating configuration policies for the one or more automation devices based on the relationship between the automation devices and the instructions on the automations defined in the lighting design, and targeted technology and protocol; and creating virtual automation devices that matches the behaviour of real world automation devices.

100 105 2021107221

110

115

115a 115b 115c 115d 115e

FIGURE 1

Generate Lighting Plan for a Floorplan

210 2021107221

Generate Lighting Design for the Lighting Plan and Export The Lighting Design to Automation Hub

215

Group Automation Devices and Creating User Interfaces

220

Create Configuration Policies for the One or More Automation Devices

225

Create Virtual Automation Devices

FIGURE 2

FIGURE 3

- id: '1596627762492' alias: Turn entrance light on when arriving home after dark description: '' trigger: 2021107221

- entity_id: binary_sensor.people_home from: 'off' platform: state to: 'on' condition: - condition: state entity_id: binary_sensor.hw1_pr_2_pr state: 'on' - condition: state entity_id: sun.sun state: below_horizon action: - data: {} entity_id: switch.lr1_sw1_3 service: switch.turn_on - delay: '120' - condition: not conditions: - condition: state entity_id: input_select.energy_mode state: home - data: {} entity_id: switch.lr1_sw1_3 service: switch.turn_off mode: single

FIGURE 4