WO2017121997A1

WO2017121997A1 - Server implemented building control system

Info

Publication number: WO2017121997A1
Application number: PCT/GB2017/050048
Authority: WO
Inventors: Bernard Cook
Original assignee: Bernard Cook
Priority date: 2016-01-11
Filing date: 2017-01-10
Publication date: 2017-07-20
Also published as: GB2546258A; GB201600431D0

Abstract

A building 10 comprises a server-implemented control system 12, and at least one energisable building system 24controllable by the server-implemented control system 12. The system12 includes a server 40, a master controller 42, high-priority slave controller 44, and low-priority slave controller 46 having matching or substantially matching hardware. The server 40is in data communication at one side to a distributed computer network 48 and at another side to the master controller 42. The master controller 42 is in data communication with the high-priority slave controller 44 and the low-priority slave controller 46, and the high-priority slave controller 44 is in communication with a switch device 28, the low-priority slave controller 46 is in communication with an energisable device 25 activatable by the switch device 28 and forming part of the energisable building system 24. A unique identifier 38, 50is associated with the master controller 42, high-priority slave controller44, low-priority slave controller46, switch device 28 and energisable device 25, and the server 40 having a relationship matrix 54 in whichthe unique identifiers38, 50 are inserted whereby the master controller 42 is associated with the high-priority slave controller 44 and the low-priority slave controller 46 and vice versa, and the high-priority slave controller 44 is associated with the low-priority slave controller46and vice versa. The server 40 automatically determines and installs based on the relationship matrix 54 the firmware required by each of the master controller 42, high-priority slave controller 44 and the low-priority slave controller 46, so that the high-priority slave controller 44 and the low-priority slave controller 46 can communicate with and/or control the respective switch device 28 and energisable device 25, and so that the master controller 42 can communicate with the high-priority slave controller 44 and the low-priority slave controller 46 and vice versa. The master controller 42 has the relationship matrix 54 automatically locally installed by the server 40, whereby the high-priority slave controller 44 and the low-priority slave controller 46 are controllable by the master controller 42 independently of the server 40.

Description

Server Implemented Building Control System

The present invention relates to a server-implemented building control system, to a building having such a control system, to a method of controlling with reduced or limited latency at least one energisable building system preferably within such a building, and to a method of simplifying an installation of a server-implemented control system for controlling at least one energisable building system preferably of such a building.

A traditional building control system simply involves one or more manual switches which are electrically connected to one or more associated energisable devices, such as lights. When an occupant leaves the room of the building, they operate the manual switch, and the associated lights are deenergised. However, it is often the case that the occupant, when leaving does not operate the switch to extinguish the lights. This results in a significant increase in energy consumption, leading to higher costs and damage to the environment.

Time-operated systems to overcome the above issue have therefore been implemented over the last number of years, which involves disabling the main lighting circuit to the floors within a building using a timing switch. Consequently, at a certain time in the evening, the lights are extinguished, and then at a certain time in the morning, the circuit is reactivated. However, if occupants need to work late or arrive particularly early, then they either work in the dark or need to have access to a manual override, typically controlled by a security guard or night watchman. If the security guard or watchman is not at his or her station, then the lights cannot be activated. Similar issues occur with other energisable circuits which control building systems, such as heating and cooling, computers and displays.

The above-described system is not only inflexible to meet different occupants' needs, but also cannot be easily rolled out to other parts of the building or indeed easily installed in a new building project. To reduce cost, warehousing and to reduce a number of dissimilar components that have to be procured and installed, it would also be highly beneficial to utilise as many common components in any system as possible. The present invention therefore seeks to provide a solution to these problems, whereby bespoke control of an energisable building system can be achieved simply and with a substantial degree of automation, along with a system which can be implemented quickly and cost-effectively.

According to a first aspect of the invention, there is provided a building comprising a server- implemented control system, and at least one energisable building system controllable by the server-implemented control system, the server-implemented control system including: a server, at least one master controller, and at least one slave controller, the master controller and slave controller having matching or substantially matching hardware, the server being in data communication at one side to a distributed computer network and at another side to the at least one master controller, the at least one master controller being in data communication with the at least one slave controller, the slave controller being in communication with at least one switch device, and/or in communication with at least one energisable device activatable by the switch device and forming part of the said at least one energisable building system, the master controller, slave controller, switch device and energisable device each having a unique identifier, and the server having a relationship matrix in which the unique identifiers are inserted whereby the master controller is associated with the slave controller and vice versa, the server automatically determining and installing based on the relationship matrix the firmware required by each of the master controller and the slave controller, so that the slave controller can communicate with and/or control the respective switch device and/or energisable device, and so that the master controller can communicate with the slave controller and vice versa, the master controller having the relationship matrix or at least a portion thereof or an element relating thereto automatically locally installed by the server, whereby the slave controller is controllable by the master controller independently of the server.

Preferably, at least one slave controller comprises a high-priority slave controller and a low- priority slave controller, the high-priority slave controller being communicable with the said at least one switch device, and the low-priority slave controller being communicable with the said at least one energisable device. The high-priority slave controller and low-priority slave controller may beneficially each have a said unique identifier, to allow facile management and use of a multiplicity of controllers in the system. The relationship matrix in which the unique identifiers are inserted preferably associates the master controller with the high-priority slave controller and the low-priority slave controller and vice versa, and the high-priority slave controller is associated with the low-priority slave controller and vice versa.

Beneficially, the server may automatically determine and install based on the relationship matrix the said firmware required by each of the master controller, high-priority slave controller and the low-priority slave controller, so that the high-priority slave controller and the low-priority slave controller can communicate with and/or control the respective switch device and energisable device, and so that the master controller can communicate with the high-priority slave controller and the low-priority slave controller and vice versa.

Preferably, the building has a plurality of levels, each level having a said at least one master controller, a said at least one high-priority slave controller, a said at least one low-priority slave controller, a said at least one switch device, and a said at least one energisable device.

The said at least one master controller preferably is associated with a plurality of said high-priority slave controllers and a plurality of said low-priority slave controllers. Each said high-priority slave controller may beneficially be associated with a plurality of said switch devices. Likewise, each said low-priority slave controller preferably is associated with a plurality of said energisable devices.

Preferably, the or each said slave controller is in communication with at least one switch device to receive a control signal therefrom and at least one energisable device controllable by the switch device to which the slave controller outputs a further control signal. In any of the above cases, the master controller and the slave controller preferably are provided in a common housing. The master controller and the slave controller may utilise common hardware while being differentiated by software. This is advantageous in that it reduces the production costs of the controller hardware as all controller units can be thus produced by the same process.

The said at least one energisable device preferably is or includes, more than one of, or a combination of: a light emitting element, an air-conditioning unit, a vent, a radiator, a blind, a window, an electronic display, a computer system, a mains power socket.

The unique identifier may be advantageously provided as an optically-recognisable code. Most preferably, the optically-recognisable code is provided as at least one of a barcode or a QR code.

According to a second aspect of the invention, there is provided a server-implemented building control system for a building, preferably in accordance with the first aspect of the invention, the control system comprising: a server, at least one master controller, and at least one slave controller, the master controller and slave controller having matching or substantially matching hardware, the server being in data communication at one side to a distributed computer network and at another side to the at least one master controller, the at least one master controller being in data communication with the at least one slave controller, the slave controller being in communication with at least one switch device, and/or in communication with at least one energisable device activatable by the switch device and forming part of the said at least one energisable building system, the master controller, slave controller, switch device and energisable device each having a unique identifier, and the server having a relationship matrix in which the unique identifiers are inserted whereby the master controller is associated with the slave controller and vice versa, the server automatically determining and installing based on the relationship matrix the firmware required by each of the master controller and the slave controller, so that the slave controller can communicate with and/or control the respective switch device and/or energisable device, and so that the master controller can communicate with the slave controller and vice versa, the master controller having the relationship matrix or at least a portion thereof or an element relating thereto automatically locally installed by the server, whereby the slave controller is controllable by the master controller independently of the server.

A method of controlling with reduced or limited latency at least one energisable building system within a building, preferably in accordance with the first aspect of the invention, the method comprising the steps of: a] using matching or substantially matching hardware to provide a master controller and at least one slave controller for communication with at least one switch device of the at least one energisable building system and/or for controlling at least one energisable device of the at least one energisable building system, the master controller being local to the slave controller; b] identifying a relationship between the master controller and the slave controller in a relationship matrix; c] using a server to automatically determine and install based on the relationship matrix the firmware required by each of the master controller and slave controller; and d] the server automatically installing the relationship matrix or at least a portion thereof or an element relating thereto on the master controller, so that the slave controller is locally controllable via the master controller based on the relationship matrix.

A method of simplifying an installation of a server-implemented control system for controlling at least one energisable building system of a building, preferably in accordance with the first aspect of the invention, the method comprising the steps of: a] using matching or common hardware to provide a master controller and at least one slave controller for communicating with at least one switch device of the at least one energisable building system and/or a for controlling at least one energisable device of the at least one energisable building system; b] identifying a relationship between the master controller and the slave controller in a relationship matrix; c] using a server to automatically determine and install based on the relationship matrix the firmware required by each of the master controller and the slave controller; and d] the server automatically installing the relationship matrix or at least a portion thereof or an element relating thereto on the master controller, so that the slave controller is locally controllable via the master controller based on the relationship matrix. The invention will be more particularly described, by way of example only, with reference to the accompanying drawings, in which:

Figure 1 shows a diagrammatic layout of a first embodiment of a building, according to the first aspect of the invention, and having a basement below ground and a server-implemented control system in accordance with the second aspect of the invention for controlling at least one energisable building system within the building; and

Figure 2 shows a diagrammatic layout of a second embodiment of a building, similarly to Figure 1 and according to the first aspect of the invention.

Referring firstly to Figure 1 of the drawings, there is shown a diagrammatic representation of an internal floor layout of a building 10 which comprises a first embodiment of a server-implemented building control system 12. The building 10 may have a basement 14 which may be below ground level 16, along with a ground floor 18, first floor 20 and second floor 22. However, this is for illustrative purposes only, and the building control system 12 of the present invention can be applied to any building structure having a single floor or any number of floors.

The building 10 includes one of typically several energisable building systems 24. In this case, by way of example, the energisable building system 24 is a series of energisable devices 25, such as light emitting elements 26, a plurality of which is provided on at least the ground floor 18, first floor 20 and second floor 22. The light emitting elements 26 on each floor may be arranged in groups with each group being independently switchable via a switch device 28, such as a light switch 30, again typically being locally provided on a wall 32 of the respective floor, and generally close to an entrance/exit door 34. Switching may also be achieved via any other suitable switch device 28 or a combination thereof, such as a motion detector 36 or other remote-monitoring detector, an image capture device, camera or video, for example.

Although the switch devices 28 and the respective energisable devices 25, in this case being light emitting elements 26, may all be on a common floor, it is feasible that certain switch devices, including monitoring devices, may energise and deenergise associated light emitting elements and/or other energisable devices forming part of the or multiple building systems on different floors, as necessity dictates.

Although the energisable building system 24 is predominantly suggested as being a lighting circuit, other energisable building systems or a combination thereof may be controllable in a similar manner. Such energisable building systems may include, for example, but not necessarily limited to a boiler and/or associated heating and/or cooling system or circuits, computers, displays and/or peripheral computer devices such as printers and scanners.

In all of these instances, each component of the energisable building system 24, in this case being the light switches 30 and the associated light emitting elements 26, preferably include a unique identifier 38. Advantageously, the unique identifier 38 may be an optically-readable code, such as a barcode or QR code. In this case, the unique identifier 38 is preferably provided on an exterior surface of the said component, such as via a printed sticker.

The control system 12 in its broadest aspect includes a server 40, master controller 42, high-priority slave controller 44, and low-priority slave controller 46. The server 40 comprises known suitably robust computer hardware capable of facilitating both a running instance of software that is capable of accepting requests from at least the master controller 42, high-priority slave controller 44 and the low-priority slave controller 46, and which is capable of facilitating execution of such software by way of suitable processor or processors and memory storage.

The server 40, in this embodiment, is situated in the basement 14 of the building 10, and is in data communication at one side to a distributed computer network 48, for example, the Internet, and at another side to at least the master controller 42. The location of the server may be inside or outside of the building 10 at any preferred position, and may be 'cloud' based and thus located in a centralised data centre remote from the building 10, whereby the master, high-priority slave and low-priority slave controllers 42, 44, 46 undertake data transfer with the server external of the building 10.

In the present embodiment, one server 40, and one master controller 42, high-priority slave controller 44 and low-priority slave controller 46 per floor are suggested. However, multiple servers, master controllers, high-priority slave controllers and/or low-priority slave controllers can be utilised within the control system 12. It is preferable that the or each master controller 42, the or each high-priority slave controller 44 and the or each low-priority slave controller 46 have matching or substantially matching hardware. This is particularly beneficial in reducing stock levels, delivery times, and the real time commissioning by the installer or installers. It also deskills the installer, leading to reduced errors and mistakes during the installation process. As with the components of the energisable building system 24, in this case being the or each switch 30, monitoring device 36 and light emitting element 26, the or each master controller 42, the or each high-priority slave controller 44 and the or each low-priority slave controller 46 has a further unique identifier 50. This may take the form of an externally-mounted optically-readable code, such as a barcode or QR code. Additionally or alternatively, the or each master controller 42, the or each high-priority slave controller 44 and the or each low-priority slave controller 46, along with each switch device 28 and/or energisable device 25 as required, may also include a unique digital identifier not shown. The digital identifier preferably corresponds to the external identifier 50, and this would typically be a fixed or static IP address, for example, to ultimately allow the server 40 to communicate therewith, as will be understood hereinafter. To install the control system 12, an installer preferably utilises a handholdable mobile computing device 52, such as a tablet computer or laptop. The computing device 52 includes a relationship matrix 54 implemented to run by software thereon, having a user interface 56 on a display screen of the computing device 52 preferably depicting a generalised floor plan of the building 10. To enable input or capture of the associated further unique identifiers 50, the mobile computing device 52 preferably includes an optical reader, scanner or other suitable image capture and recognition device or system 58. As an alternative, the installer may be provided with a separate image capture and recognition device or system, such as a handholdable portable scanner.

The installer thereby installs the master controller 42 generally locally or in relatively near proximity to the components 25, 28 of the energisable building system 24 to be controlled. It is preferable to enable reduced latency during an energisation and a deenergisation procedure to have the master controller 42 closer to the components 25, 28 than the server 40. In the example being described, a said master controller 42 is installed on each floor of the building 10, and in this case it may be convenient to locate the master controller 42 on the interior wall 32 of the building 10, or within the wall 32, floor 60 or ceiling cavity 62 of the associated floor. Prior to, during or following installation of the master controller 42, the further unique identifier 50 is logged, for example, by scanning using the image capture and recognition device or system 58, which identifies the position of the master controller 42 on the floor plan. The further unique identifier 50 corresponding to the master controller 42 is thus recorded by the relationship matrix 54.

The installer preferably then installs the low-priority slave controller 46, in this case on or within a ceiling cavity 62. The low-priority slave controller 46 is connected to one or more of the energisable components 25 of the building system 24, for example, one or a group of the light emitting elements 26. Again, prior to, during or following installation of the low-priority slave controller 46, the associated further unique identifier 50 is logged which identifies the position of the low-priority slave controller 46 on the floor plan. The further unique identifier 50 corresponding to this particular low-priority slave master controller 42 is thus recorded by the relationship matrix 54. Similarly, with the controllable light emitting elements 26 or other energisable components 25 installed, the associated unique identifiers 38 are also logged, for example, by scanning using the image capture and recognition device or system 58, and thus recorded appropriately in the relationship matrix 54. Within the matrix 54, therefore, a specific said low-priority slave controller 46 is identified as communicating with one or more specifically identified light emitting elements 26 or other components of the building system 24.

With the or each low-priority slave controller 46 associated and communicating with the light emitting elements 26 or other energisable components, as required, the installer may then install the or each high-priority slave controller 44. The high-priority slave controller 44 is connected to one or more of the switch devices 28, whether that is a manual switch 30 and/or a remote-detector switch 36. Similarly, the high-priority slave controller 44 may be mounted on the wall 32, ceiling or floor of the building 10 or in a cavity void, preferably in relatively close proximity to the switch device or devices 28. The installer logs the further unique identifier 50 on the floor plan and thus in the relationship matrix 54, and connects the high-priority slave device to the associated switch devices 28 for communication therebetween, which are similarly logged in the relationship matrix 54 by their unique identifiers 38. The installer also associates one or more of the installed high- priority slave controller 44 with one or more of the installed low-priority slave controllers 46 to indicate a control relationship, and this is identified on the floor plan and thus also on the relationship matrix 54. Following this, the installer further associates one or more specific installed master controllers 42 with one or more high-priority and low-priority slave controllers 44, 46, in accordance with the control required of the building system 24.

With all the components 25, 28 of the building system 24 installed and logged, along with the master controllers 42 associated with their respective high-priority slave controllers 44 and their low-priority slave controllers 46 to allow two-way communication therebetween, and the high- priority and low-priority slave controllers 44, 46 also in two-way communication, the relationship matrix 54 is uploaded by the installer via the computing device 52 to the server 40 and to the or each master controller 42.

Following upload, the server 40 automatically determines based on the relationship matrix 54 the firmware required by each of the master controller 42, high-priority slave controller 44 and the low-priority slave controller 46. Through the connection to the distributed computer network 48, in this case being the Internet, the server 40 automatically requests and downloads the appropriate software, and distributes this within the building 10 to the or each master controller 42, high- priority slave controller 44 and low-priority slave controller 46. Installation occurs automatically on arrival via a self-executable file structure package. The firmware installation automatically by the server 40 enables the or each high-priority slave controller 44 and low-priority slave controller 46 to communicate with and/or control the respective associated switch devices 28 and energisable devices 25, along with the or each master controller 42 controlling the respective associated high- priority and low-priority slave controllers 44, 46, in accordance with the locally automatically installed relationship matrix 54.

In use, it is therefore the master controller 42, which is typically in closer proximity to the high- priority and low-priority slave controllers 44, 46 and their associated components 25, 28 of the building system 24 than the server 40, which is dedicated to the control function of the energisable devices 25, such as the light emitting elements 26, independently of the server 40.

When, for example, a said light switch 30 is manually activated by an occupant of the building 10, this is communicated to the high-priority slave controller 44, which outputs a first activation signal to the master controller 42. The master controller 42, via the relationship matrix 54, thereby outputs a second activation signal to the low-priority slave controller 46, which thereby enables energisation of the associated one or group of lights. A similar process occurs when the or each light is required to be deenergised.

If the relationship between the master controller 42, high-priority and low-priority slave controllers 44, 46, and their respective switch devices 28 and energisable devices 25 is to be changed or modified, this is a simple case of the installer reconfiguring the relationship matrix 54 via the floor plan on his or her mobile computing device 52 or other suitable computing device, as required. Once the reconfiguration has taken place, the revised relationship matrix 54 is uploaded to the server 40, which in turn then automatically downloads and distributes the required firmware for unattended installation, again as required. With the revised relationship matrix 54 also uploaded to the designated master controllers 42, two-way communication between the master controller 42 and associated high-priority and low-priority slave controllers 44, 46, and between the high- priority and low-priority slave controllers 44, 46 themselves is achievable, again, as required.

Referring now to Figure 2, there is shown a diagrammatic representation of an internal floor layout of a building 110 which comprises a second embodiment of a server-implemented building control system 112. The building and system are similar to the first embodiment, and therefore features or elements which are similar or identical utilise the same or similar references, typically with an increment of 100. In this case, further detailed description is omitted for the sake of brevity.

The building 110 may have a basement 114 which may be below ground level 1 16, along with a ground floor 118, first floor 120 and second floor 122. However, again, this is for illustrative purposes only, and the building control system 112 can be applied to any building structure having a single floor or any number of floors.

The building 110 includes one of typically several energisable building systems 124. By way of example, the energisable building system 124 is a series of energisable devices 125, such as light emitting elements 126, a plurality of which is provided on at least the ground floor 118, first floor 120 and second floor 122. The light emitting elements 126 on each floor may be arranged in groups with each group being independently switchable via a switch device 128, such as a light switch 130. Switching may also be achieved via any other suitable switch device 128 or a combination thereof, such as a motion detector 136 or other remote-monitoring detector. As in the first embodiment, each component of the energisable building system 124, preferably includes a unique identifier 138. The unique identifier 138 may be an optically-readable code, such as a barcode or QR code, and is preferably provided on an exterior surface of the said component, such as via a printed sticker.

The control system 112 in its broadest aspect includes a server 140, master controller 142, and a slave controller 200. The server 140 comprises known suitably robust computer hardware capable of facilitating both a running instance of software that is capable of accepting requests from at least the master controller 142, and the slave controller 200, and which is capable of facilitating execution of such software by way of suitable processor or processors and memory storage.

The server 140, in this embodiment, is situated in the basement 114 of the building 110, and is in data communication at one side to a distributed computer network 148, for example, the Internet, and at another side to at least the master controller 142.

In the present embodiment, one server 140, one master controller 142, and one slave controller 200 per floor are suggested. However, multiple servers, master controllers, and slave controllers can be utilised within the control system 112. It is preferable that the or each master controller 142, and the or each slave controller 200 have matching or substantially matching hardware along with the aforementioned further unique identifiers 150 and/or corresponding unique digital identifiers. As above, this is particularly beneficial in reducing stock levels, delivery times, and the real time commissioning by the installer or installers. It also deskills the installer, leading to reduced errors and mistakes during the installation process.

To install the control system 112, an installer preferably utilises the handholdable mobile computing device 152, such as a tablet computer or laptop. The computing device 152 includes a relationship matrix 154 implemented to run by software thereon, having a user interface 156 preferably depicting a generalised floor plan of the building 110. As before, the installer installs the master controller 142 generally locally or in relatively near proximity to the components 125, 128 of the energisable building system 124 to be controlled, in an effort to reduce latency during an energisation and a deenergisation procedure

Prior to, during or following installation of the master controller 142, the further unique identifier 150 is logged which identifies the position of the master controller 142 on the floor plan. The further unique identifier 150 corresponding to the master controller 142 is thus recorded by the relationship matrix 154.

The installer preferably then installs the slave controller 200, in this case on or within a wall cavity or void, but equally in any appropriate position. The slave controller 200 is connected to one or more of the energisable components 125 of the building system 124, for example, one or a group of the light emitting elements 126, and the further unique identifier 150 is recorded by the relationship matrix 154.

With the controllable light emitting elements 126 or other energisable components 125 also installed, the associated unique identifiers 138 are also logged, and thus recorded appropriately in the relationship matrix 154. Within the matrix 154, therefore, a specific slave controller 200 is identified as communicating with one or more specifically identified light emitting elements 126 or other components of the building system 124.

The installer then associates the or each slave controller 200 with one or more of the switch devices 128, whether that is a manual switch 130 and/or a remote-detector switch 136, for example. Although preferable, such association does not have to correspond to the same floor as the energisable components 125, and may correspond to multiple floors, combinations, or remote or distant floors.

The associated switch devices 128 are similarly logged in the relationship matrix 154 by the installer against one or more specific slave controllers 200 by their unique identifiers 138. A control relationship is indicated on the relationship matrix 154 by the installer between the energisable components 125 and the switch devices 128, via the respective slave controller 200 and in accordance with the control required of the building system 124.

With all the components 125, 128 of the building system 124 installed and logged, along with the master controllers 142 associated with their respective slave controllers 200 to allow two-way communication therebetween, the relationship matrix 154 is uploaded by the installer via the computing device 152 to the server 140 and to the or each master controller 142.

Following upload, the server 140 automatically determines based on the relationship matrix 154 the firmware required by each of the master controller 142 and slave controller 200. Through the connection to the distributed computer network 148, in this case being the Internet, the server 140 automatically requests and downloads the appropriate software, and distributes this within the building 110 to the or each master controller 142 and the or each slave controller 200. Installation occurs automatically on arrival via a self-executable file structure package. The firmware installation automatically by the server 140 enables the or each slave controller 200 to communicate with and/or control the respective associated switch devices 28 and energisable devices 25, along with the or each master controller 42 controlling the respective associated slave controller 200, in accordance with the locally automatically installed relationship matrix 154.

In use, it is therefore the master controller 142, which is typically in closer proximity to the respective slave controller 200 and the associated components 125, 128 of the building system 124 than the server 140, which is dedicated to the control function of the energisable devices 125, such as the light emitting elements 126, independently of the server 140.

When, for example, a said light switch 130 is manually activated by an occupant of the building 110, this is communicated to the slave controller 200, which outputs a first activation signal to the master controller 142. The master controller 142, via the relationship matrix 154, thereby outputs a second activation signal to the or a different associated slave controller 200, which thereby enables energisation of the associated one or group of lights. A similar process occurs when the or each light is required to be deenergised.

If the relationship between the master controller 142 and slave controller 200, and their respective switch devices 128 and energisable devices 125 is to be changed or modified, this is a simple case of the installer reconfiguring the relationship matrix 154 via the floor plan on his or her mobile computing device 152 or other suitable computing device, as required. Once the reconfiguration has taken place, the revised relationship matrix 154 is uploaded to the server 140, which in turn then automatically downloads and distributes the required firmware for unattended installation, again as required. With the revised relationship matrix 154 also uploaded to the designated master controllers 142, two-way communication between the master controller 142 and the associated slave controller 200, is achievable, again, as required. In both embodiments described above, it is also feasible for an installer or operator to remotely log in to the server 14, 140 to remotely reconfigure the relationship matrix 54, 154 and thus the association between the or each master controller 42, 142 and the or each slave controller 44, 46, 200. As already described, once the reconfiguration has taken place, the server 40, 140 uploads the revised relationship matrix to the master controllers 42, 142, and automatically downloads and distributes the required firmware for unattended installation, again as required.

It is also beneficial that the status of the relationship matrix 54, 154 at the or each master controller 42, 142 is periodically downloaded to the server 40, 140 for, preferably, real time or near real time monitoring by an operator or installer. This monitoring may be onsite at the server 40, 140, or remotely by logging in to the server 40, 140 through the Internet or other distributed computer network. Once the master controller 42, 142 receives the activation signal from the or each slave controller 46, 200, and outputs an appropriate control signal based on the relationship matrix 54, 154 to the associated slave controller 44, 200, this is preferably logged, for example, in the relationship matrix 54, 154 or other suitable logging means, and as such preferably outputted to the server 40, 140 for historical archiving and also to enable real time or near real time monitoring. This also enables failed components with the system to be easily and remotely monitored to allow for repair and/or replacement, as required.

Although the above embodiments suggest that the master controller and the or each slave controller may be separate or distinct hardware components, which may be spaced from each other, it is feasible that the master controller and one or all slave controllers may be a single hardware device. In this case, the master and slave controllers may be defined by separate or distinct hardware or circuitry within a single housing and/or may utilise common hardware and/or circuitry but be differentiated virtually by appropriate software.

Additionally or alternatively, although it may be preferred that the server uploads the entire relationship matrix to the or each master controller, only one or more required portions of the relationship matrix may be uploaded, as determined by logic code or circuitry provided on the server and/or in accordance with the unique identifiers.

Similarly, it may be preferred that only relevant portions of the relationship matrix or parts thereof are downloaded periodically to the server from the or each master controller to enable remote monitoring. Both of the above options are advantageous in reducing or optimising bandwidth usage over the system network.

Although the slave controller of the second embodiment is suggested as a single unit or element, it can be considered to be equivalent to the high-priority slave controller and the low-priority slave controller of the first embodiment. As above, the slave controller of the second embodiment may encompass distinct hardware separately defining the high-priority slave controller and the low- priority slave controller within a single housing, may utilise a single integrated hardware set which defines the high-priority and low-priority slave controllers, and/or may define the high-priority slave controller and the low-priority slave controller virtually through appropriate software code received from the server.

Due to the commonality of the hardware of the master controller and the slave controllers, it is a vastly simplified process to reconfigure the controllers as required to adopt new functions. It also becomes a much more streamlined process for an installer to roll out a control system for an energisable building system, with far less opportunity for error during the installation process. The present invention also enables the option of a modular system, whereby additional switch devices and/or energisable devices can be retrospectively included for control by a pre-installed slave controller. Furthermore, an additional master controller, and/or slave controller can be retrospectively included as part of the server-implemented control system, again simply by reconfiguring the digital relationship matrix following installation. An additional benefit allows the server to periodically check for firmware updates, and to automatically rollout updated software for self-executing installation to the designated master controller, and lo slave controller at appropriate periods. Furthermore, by enabling external remote access to the server, the relationship matrix can be monitored and reconfigured remotely and offsite, without thereby requiring an installer to visit the installation site in person, again saving time and reducing cost.

Although the automatic determination of the required firmware by the server is beneficial, the installation may follow authorisation by a user. Thus, whilst preparation may be automated, the installation may be semi-autonomous due to requiring a manual-input authorisation by a controller or other authorised person. Additionally or alternatively, during installation of the hardware, the installer may be prompted to define operating characteristics of the hardware. This may be by drop down menus or other option prompts on a handheld mobile communications device, such as a tablet computer or smartphone, and/or on a scanning device carried by the installer and which is able to communicate with the relationship matrix and consequently server. The defined operating characteristics are then fed into the relationship matrix, whereby the server can automatically determine the appropriate firmware to achieve the required operating parameters. For example, if the switch device is required to have a variable ON state, such as when controlling a dimmable light emitting element, then the firmware needs to account for this. Furthermore, if the energisable device is for example a light emitting element and should only be energised in its particular location to fifty percent of its maximum power, again, the firmware associated with the corresponding slave controller, whether that is onboard the energisable device, in close spaced proximity, or remote should account for this.

Additionally or alternatively, a straightforward change in brightness or luminosity of the associated light emitting element may not require a firmware change. However, if the slave controller, based on the relationship matrix, has a switch device and a dimming light-emitting element associated therewith, then the firmware may or would account for this and as such be automatically determined or accounted for by the server during any change. Furthermore, if the slave controller was, for example, moved and required to operate a thermocouple and boiler or at least an energisable building system that was determined by the server to be functionally sufficiently different, then the firmware would be replaced or superseded by the updated relationship matrix interacting automatically with the server and in accordance with the process and systems described above.

It is also feasible for the server-implemented building control system to be provided as a standalone package which can be installed as required in an existing building. As an alternative, the building control system can be incorporated to be integral with the building as the building is being built or during construction. The standalone building control system may also beneficially be modular, as described above, thereby allowing components to be procured or removed as required, and also simplifying maintenance once installation has been complete.

The words 'comprises/comprising' and the words 'having/including' when used herein with reference to the present invention are used to specify the presence of stated features, integers, steps or components, but do not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof.

It is appreciated that certain features of the invention, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable sub-combination.

The embodiments described above are provided by way of examples only, and various other modifications will be apparent to persons skilled in the field without departing from the scope of the invention as defined by the appended claims.

Claims

1. A building (10) comprising a server-implemented control system (12), and at least one energisable building system (24) controllable by the server-implemented control system (12), the server-implemented control system (12) including: a server (40), at least one master controller (42), and at least one slave controller (44; 46), the master controller (42) and slave controller (44; 46) having matching or substantially matching hardware, the server (40) being in data communication at one side to a distributed computer network (48) and at another side to the at least one master controller, the at least one master controller (42) being in data communication with the at least one slave controller (44; 46), the slave controller (44; 46) being in communication with at least one switch device (28), and/or in communication with at least one energisable device (25) activatable by the switch device (28) and forming part of the said at least one energisable building system (24), the master controller (42), slave controller (44; 46), switch device (28) and energisable device (25) each having a unique identifier, and the server (40) having a relationship matrix (54) in which the unique identifiers (38; 50) are inserted whereby the master controller (42) is associated with the slave controller (44; 46) and vice versa, the server (40) automatically determining and installing based on the relationship matrix (54) the firmware required by each of the master controller (42) and the slave controller (44; 46), so that the slave controller (44; 46) can communicate with and/or control the respective switch device (28) and/or energisable device (25), and so that the master controller (42) can communicate with the slave controller (44; 46) and vice versa, the master controller (42) having the relationship matrix (54) or at least a portion thereof or an element relating thereto automatically locally installed by the server (40), whereby the slave controller (44; 46) is controllable by the master controller independently of the server (40).

2. A building (10) as claimed in claim 1, wherein the said at least one slave controller (44; 46) comprises a high-priority slave controller (44) and a low-priority slave controller (46), the high-priority slave controller (44) being communicable with the said at least one switch device (28), and the low-priority slave controller (46) being communicable with the said at least one energisable device (25).

3. A building (10) as claimed in claim 2, wherein the high-priority slave controller (44) and low-priority slave controller (46) each have a said unique identifier (38; 50).

4. A building (10) as claimed in claim 2 or claim 3, wherein the relationship matrix (54) in which the unique identifiers (38; 50) are inserted associates the master controller (42) with the high-priority slave controller (44) and the low-priority slave controller (46) and vice versa, and the high-priority slave controller (44) is associated with the low-priority slave controller (46) and vice versa.

5. A building (10) as claimed in any one of claims 2 to 4, wherein the server (40) automatically determines and installs based on the relationship matrix (54) the said firmware required by each of the master controller (42), high-priority slave controller (44) and the low- priority slave controller (46), so that the high-priority slave controller (44) and the low-priority slave controller (46) can communicate with and/or control the respective switch device (28) and energisable device (25), and so that the master controller (42) can communicate with the high- priority slave controller (44) and the low-priority slave controller (46) and vice versa.

6. A building (10) as claimed in any one of claims 2 to 5, which has a plurality of levels, each level having a said at least one master controller (42), a said at least one high-priority slave controller (44), a said at least one low-priority slave controller (46), a said at least one switch device (28), and a said at least one energisable device (25).

7. A building (10) as claimed in claim 6, wherein the said at least one master controller (42) is associated with a plurality of said high-priority slave controllers (44) and a plurality of said low- priority slave controllers (46).

8. A building (10) as claimed in any one of claims 2 to 7, wherein each said high-priority slave controller (44) is associated with a plurality of said switch devices (28).

9. A building (10) as claimed in any one of claims 2 to 8, wherein each said low-priority slave controller (46) is associated with a plurality of said energisable devices (25).

10. A building (10) as claimed in claim 1, wherein the or each said slave controller (44; 46) is in communication with at least one switch device (28) to receive a control signal therefrom and at least one energisable device (25) controllable by the switch device to which the slave controller outputs a further control signal.

11. A building (10) as claimed in any one of the preceding claims, wherein the master controller (42) and the slave controller (44; 46) are provided in a common housing.

12. A building (10) as claimed in any one of claims 1 to 11, wherein the master controller (42) and the slave controller (44; 46) utilise common hardware and are differentiated by software.

13. A building (10) as claimed in any one of the preceding claims, wherein the said at least one energisable device (25) is or includes one, more or a combination of a light emitting element, an air-conditioning unit, a vent, a radiator, a blind, a window, an electronic display, a computer system, a mains power socket.

14. A building (10) as claimed in any one of the preceding claims, wherein the unique identifier (38; 50) is an optically-recognisable code.

15. A building (10) as claimed in claim 14, wherein the optically-recognisable code is at least one of a barcode or a QR code.

16. A server-implemented building control system (12) for a building (10) as claimed in any one of the preceding claims, the control system (12) comprising: a server (40), at least one master controller (42), and at least one slave controller (44; 46), the master controller (42) and slave controller (44; 46) having matching or substantially matching hardware, the server (40) being in data communication at one side to a distributed computer network (48) and at another side to the at least one master controller (42), the at least one master controller (42) being in data communication with the at least one slave controller (44; 46), the slave controller (44; 46) being in communication with at least one switch device (28), and/or in communication with at least one energisable device (25) activatable by the switch device (28) and forming part of the said at least one energisable building system (24), the master controller (42), slave controller (44; 46), switch device (28) and energisable device (25) each having a unique identifier, and the server (40) having a relationship matrix (54) in which the unique identifiers (38; 50) are inserted whereby the master controller (42) is associated with the slave controller (44; 46) and vice versa, the server (40) automatically determining and installing based on the relationship matrix (54) the firmware required by each of the master controller (42) and the slave controller (44; 46), so that the slave controller (44; 46) can communicate with and/or control the respective switch device (28) and/or energisable device (25), and so that the master controller (42) can communicate with the slave controller (44; 46) and vice versa, the master controller (42) having the relationship matrix (54) or at least a portion thereof or an element relating thereto automatically locally installed by the server (40), whereby the slave controller (44; 46) is controllable by the master controller (42) independently of the server (40).

17. A method of controlling with reduced or limited latency at least one energisable building system (24) within a building (10) as claimed in any one of claims 1 to 9, the method comprising the steps of: a] using matching or substantially matching hardware to provide a master controller (42) and at least one slave controller (44; 46) for communication with at least one switch device (28) of the at least one energisable building system (24) and/or for controlling at least one energisable device (25) of the at least one energisable building system (24), the master controller (42) being local to the slave controller (44; 46); b] identifying a relationship between the master controller (42) and the slave controller (44; 46) in a relationship matrix (54); c] using a server (40) to automatically determine and install based on the relationship matrix (54) the firmware required by each of the master controller (42) and slave controller (44; 46); and d] the server (40) automatically installing the relationship matrix (54) or at least a portion thereof or an element relating thereto on the master controller (42), so that the slave controller (44; 46) is locally controllable via the master controller (42) based on the relationship matrix (54).

18. A method of simplifying an installation of a server-implemented control system (12) for controlling at least one energisable building system (24) of a building (10), the method comprising the steps of: a] using matching or common hardware to provide a master controller (42) and at least one slave controller (44; 46) for communicating with at least one switch device (28) of the at least one energisable building system (24) and/or a for controlling at least one energisable device (25) of the at least one energisable building system (24); b] identifying a relationship between the master controller (42) and the slave controller (44; 46) in a relationship matrix (54); c] using a server (40) to automatically determine and install based on the relationship matrix (54) the firmware required by each of the master controller (42) and the slave controller (44; 46); and d] the server (40) automatically installing the relationship matrix (54) or at least a portion thereof or an element relating thereto on the master controller (42), so that the slave controller (44; 46) is locally controllable via the master controller (42) based on the relationship matrix (54).