WO2017205899A1

WO2017205899A1 - Methods and systems for configuring sensors

Info

Publication number: WO2017205899A1
Application number: PCT/AU2017/050304
Authority: WO
Inventors: Julian BOOT
Original assignee: Urbanise.com Limited
Priority date: 2016-04-07
Filing date: 2017-04-07
Publication date: 2017-12-07
Also published as: AU2017274568A1

Abstract

A handheld computing device for configuring sensors, the device being in communication with a server across a communications network and comprising a processor and a memory. The memory comprises a sensor configuration application, which when executed by the processor, is configured to cause the handheld computing device to: receive a scannable code, the scannable code associated with sensor installation data comprising at least sensor identifier and a sensor profile identifier; determine the sensor installation data from the scannable code; transmit the sensor installation data to the server across the communications network; determine a geographical location of the handheld computing device; and transmit the geographical location to the server across the communications network.

Description

"Methods and systems for configuring sensors"

TECHNICAL FIELD Described embodiments generally relate to methods and systems for configuring sensors. In particular, described embodiments are directed to methods and systems for configuring sensor networks and sensor systems.

BACKGROUND

The tasks of monitoring or maintaining a building and/or equipment within a building can be enhanced by the use of sensors to provide real-time telemetry data about the environment within the building. Data such as machine run-time, motor vibration, equipment temperature, and other information, can be used to maximise the efficiency of staff who would no longer need to perform manual checks of this information.

However, while many new buildings have modern control systems including sensors that provide real-time information, these systems are often prohibitively expensive and difficult to install and configure in existing buildings.

It is desired to address or ameliorate one or more shortcomings or disadvantages associated with prior systems for configuring sensor networks.

Any discussion of documents, acts, materials, devices, articles or the like which has been included in the present specification is not to be taken as an admission that any or all of these matters form part of the prior art base or were common general knowledge in the field relevant to the present disclosure as it existed before the priority date of each claim of this application. Throughout this specification the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated element, integer or step, or group of elements, integers or steps, but not the exclusion of any other element, integer or step, or group of elements, integers or steps. SUMMARY

Some embodiments relate to a handheld computing device for configuring sensors, the device being in communication with a server across a communications network and comprising a processor and a memory, wherein the memory comprises a sensor configuration application, which when executed by the processor, is configured to cause the handheld computing device to:

receive a scannable code, the scannable code associated with sensor installation data comprising at least sensor identifier and a sensor profile identifier;

determine the sensor installation data from the scannable code;

transmit the sensor installation data to the server across the communications network;

determine a geographical location of the handheld computing device; and transmit the geographical location to the server across the communications network.

According to some embodiments, the memory of the handheld computing device comprises a scanning application, which when executed by the processor, is configured to cause the handheld computing device to scan the scannable code provided on a sensor to be configured and to provide the scannable code to the sensor configuration application.

According to some embodiments, the scannable code comprises a unified resource locator (URL) and determining the sensor installation data from the scannable code comprises retrieving the sensor installation data from a webpage associated with the URL. According to some embodiments, the memory of the handheld computing device comprises a browser application, which when executed by the processor, is configured to display the webpage associated with the URL on a user interface of the device. In some embodiments, the handheld computing device is configured to decode the sensor installation data from the scannable code.

In some embodiments, the handheld computing device is configured to use the scannable code to retrieve the sensor installation data from a database in

communication with the device across the communications network. According to some embodiments, the device is configured to determine the

geographical location of the handheld computing device and to transmit the

geographical location to the server in response to receiving a request for the geographical location of the handheld computing device from the server. In some embodiments, the sensor profile identifier comprises at least one of a sensor profile indicator and a sensor type indicator. In some embodiments, the sensor profile indicator corresponds to a set of desired operational parameters of the sensor to be configured.

According to some embodiments, in response to receiving an indication that there is an existing entry in a sensor database for the transmitted sensor installation data, the device is configured to receive data relating to sensor readings from a sensor readings database and to execute a browser application to display information corresponding to the received sensor reading data on a display of a user interface of the device.

According to some embodiments, in response to receiving an indication that there is no existing entry in a sensor database for the transmitted sensor installation data, the device is configured to execute a browser application to provide at least one user selectable option on a display of a user interface of the device to allow a user to edit the sensor installation data and the geographical location for the sensor to be installed.

In some embodiments, the device is further configured to transmit the edited sensor installation data and the geographical location to the sensor database as a new database entry.

In some embodiments, the device is further configured to execute the browser application to provide at least one user selectable option on a display of a user interface of the device to allow the user to select from a number of sensor profile indicators based on the sensor installation data. In some embodiments, the device is further configured to execute the browser application to provide at least one user selectable option on a display of a user interface of the device to allow the user to select from a number of installation locations based on the geographical location. In some embodiments, the device is further configured to execute the browser application to provide at least one user selectable option on a display of a user interface of the device to allow a user to select a sensor profile from a sensor profile database based on the sensor type information.

According to some embodiments, the geographical location comprises one or more GPS coordinates.

Some embodiments relate to a server for configuring sensors, the server being in communication with a handheld computing device across a communications network and comprising one or more processors and a memory, wherein the memory comprises a sensor configuration application, which when executed by the one or more processors, is configured to cause the server to:

receive sensor installation data from the handheld computing device across the communications network, the sensor installation data comprising at least sensor identifier and a sensor profile;

receive a geographical location of the handheld computing device from handheld computing device across the communications network;

determine whether an entry for the received sensor identifier exists in asensor database; and

in response to determining that an entry for the received sensor identifier does not exist in the sensor database, create a new entry in the sensor database comprising the received sensor identifier, the received sensor profile and the received geographical location. In some embodiments, executing the sensor configuration application causes the server to retrieve data relating to sensor readings from a sensor readings database and to transmit information corresponding to the received sensor reading data to the handheld computing device in response to determining that an entry for the received sensor identifier does exist in an sensor database,.

In some embodiments, executing the sensor configuration application causes the server to transmit a request for the geographical location of the handheld computing device to the handheld computing device in response to receiving sensor installation data from the handheld computing device.

According to some embodiments, the server is configured to decode the received sensor installation data.

According to some embodiments, the server is configured to retrieve the sensor installation data from a database in communication with the server across the communications network in response to receiving a request for the sensor installation data from the handheld device and to transmit the sensor installation data to the handheld computing device.

In some embodiments, the sensor profile identifier comprises at least one of a sensor profile indicator and a sensor type indicator.

In some embodiments, the geographical location comprises one or more GPS coordinates. Some embodiments relate to a system for configuring sensors, the system comprising a handheld computing device according to some embodiments and a server according to some embodiments.

Some embodiments relate to a computer implemented method for configuring sensors operable on a handheld device, the method comprising:

receiving a scannable code, the scannable code associated with sensor installation data comprising at least sensor identifier and a sensor profile identifier; determining the sensor installation data from the scannable code;

transmitting the sensor installation data to the server across the communications network;

determining a geographical location of the handheld computing device; and transmitting the geographical location to the server across the communications network. Some embodiments relate to a handheld computing device for configuring sensors, the device being in communication with a server across a communications network and comprising a processor and a memory, wherein the memory comprises a sensor configuration application, which when executed by the processor, is configured to cause the handheld computing device to:

receive a scannable code, the scannable code associated with sensor installation data comprising at least sensor identifier;

determine the sensor installation data from the scannable code;

determine a geographical location of the handheld computing device; and transmit the geographical location to the server across the communications network. BRIEF DESCRIPTION OF DRAWINGS

Embodiments are described in further detail below, by way of example and with reference to the accompanying drawings, in which: Figure 1 is a block diagram of a typical sensor installation site, according to some embodiments;

Figure 2 is a block diagram of a sensor installation system, according to some embodiments;

Figure 3 is a flowchart of a sensor selection and installation process, according to some embodiments;

Figure 4 is a flowchart of an exemplary sensor installation process of the sensor installation process of Figure 3, according to some embodiments;

Figure 5 is a interaction diagram of the sensor installation process of Figure 4, according to some embodiments;

Figure 6 is an example user interface display showing information relating to a sensor being installed using the sensor installation system of Figure 2, according to some embodiments;

Figure 7 is an example user interface display showing sensor readings, according to some embodiments;

Figure 8 is an example user interface display showing a sensor profile set-up page, according to some embodiments; Figure 9 is an example vibration severity table;

Figure 10A is a sensor barcode encoding a sensor identifier and sensor type, according to some embodiments;

Figure 10B is a sensor barcode encoding a sensor identifier and sensor profile, according to some embodiments; and

Figure IOC is a sensor sticker having a QR code, according to some embodiments.

DETAILED DESCRIPTION Described embodiments generally relate to methods and systems for configuring sensors. In particular, described embodiments are directed to methods and systems for configuring sensor networks and sensor systems.

Some embodiments relate to methods of remote monitoring of building environments and/or machinery that provides heating, cooling, water and other technical services to these environments. Some embodiments relate to servers and server systems configured to perform methods of remote monitoring of building environments and/or machinery. Some embodiments relate to sensor packaging for installation purposes. Some embodiments relate to wireless sensor installation, although the same approach may be applied to wired sensors as well.

Sensors in the context of the described embodiments relate to electronic measuring devices that are capable of taking readings from the physical environment and converting them into signals that may be electronically transmitted to servers via the Internet. Examples of physical readings include vibration, temperature, humidity, motion, energy usage, water flow, voltage, current, pressure, etc.

Figure 1 shows an example of a sensor installation 100 provided in a plant or machinery room 110 with multiple items of machinery 120. As shown, one or more sensors 130 may be installed upon one or more of the items of machinery 120 for the purpose of recording different operational elements of the items of machinery 120, such as temperature and vibration. Sensors 130 may also be installed in room 110 itself to record ambient conditions such as humidity, temperature, flooding, vibration, or other conditions. In some embodiments, the sensor installation 100 may be provided in a location other than a machinery room, such as in a residential building, commercial premises, or other location. Figure 2 shows a sensor installation system 200, according to some embodiments. Sensor installation system 200 comprises a handheld computing device 210 and a server 280 accessible to the handheld computing device 210 via a communications network 285. Handheld computing device 210 may be a mobile phone, smart phone, tablet, laptop, or other computing device. Server 280 may comprise one or more servers, storage servers, server systems, and/or other computing devices. Communications network 285 may comprise the Internet according to some embodiments, or may be another type of communications network.

Sensor installation system 200 may further comprise one or more sensors 130 associated with a machine 120 or provided in a particular environment and server 280 may be configured to monitor the machine 120 or environment by communication with the one or more sensors 130 across the communications network 285.

Sensor 130 may be associated with a scannable code 260. For example, scannable code 260 may be a visual code, such as a barcode or QR code, or another scannable code, such as a radio-frequency identification (RFID) tag, that can be used to identify the sensor 130. In some embodiments, the scannable code 260 may comprise a profile- type code or a device-type code, as discussed in more detail below. In some embodiments, handheld computing device 210 may be configurable to communicate with an external scanner or camera to allow handheld computing device 210 to scan scannable code 260. In some embodiments, handheld computing device 210 may have an inbuilt scanner or camera for scanning scannable code 260.

As shown in Figure 2, handheld computing device 210 may be configurable to access a geo-location service 270 via a communications network 285, in some embodiments, which may be the Global Positioning Service. Sensor installation system 200 may further comprise one or more databases such as a location database 220, an installed sensor database 230, a profile database 240, a readings database 250, and/or an uninstalled sensor database 290. Databases 220, 230, 240, 250 and 290 may be accessible to the handheld computing device 210 and/or other computing devices via a communications network 285. According to some embodiments, handheld computing device 210 may access server 280 via communications network 285, and server 280 may communicate with databases 220, 230, 240,250 and 290 directly or via communications network 285.

One or more of databases 220, 230, 240,250 and 290 may be stored on a memory location in one or more servers or server systems, on computing devices, within cloud storage services, or in other memory locations. According to some embodiments, one or more of databases 220, 230, 240, 250 and 290 may be stored on server 280. In some embodiments, each database 220, 230, 240,250 and 290 may be stored on separate storage servers. In some embodiments, some or all of databases 220, 230, 240,250 and 290 may be stored on the same storage server. In some embodiments, parts of some or all of databases 220, 230, 240,250 and 290 may be split across multiple storage servers.

Location database 220 may be configured to store site names and associated GPS coordinates for locations for those sites and at which sensors 130 are or are to be installed. Installed sensor database 230 may be configured to store details relating to each sensor 130 that has been installed, such as a unique identifier, for example, a sensor identifier, the location of the site at which sensor 130 was installed, and a profile identifier of sensor 130 or in some embodiments, a pointer to the profile of sensor 130 in profile database 240. Profile database 240 may be configured to store sensor profiles or templates in the form of configurations or parameters for sensors 130 that define the dynamic behaviour of sensors 130 in the system 100 when sensors 130 are activated. In particular, profile database 240 may be configured to store operational parameters for types of sensors 130. For example, the operational parameters of a temperature sensor may define which temperature readings correspond to an allowable operational temperature, and which readings correspond to a high temperature for which an alarm or alert should be raised. An example of the information stored in profile database 240 is described in more detail below with reference to Figure 8. Readings database 250 may be configured to store sensor outputs, being output values received from sensors 130, as they are transmitted to readings database 250 across communications network 285.

Uninstalled sensor database 290 may be configured to store details relating to each sensor 130 that is planned to be installed, such as one or more of a unique identifier, for example, a sensor identifier, the location of the site at which sensor 130 is to be installed, and a profile identifier of sensor 130 or in some embodiments, a pointer to the profile of sensor 130 in profile database 240. According to some embodiments, instead of an uninstalled sensor database 290, system 200 may store uninstalled sensor data in installed sensor database 230. Installed sensor database 230 may include a confirmation field or flag that can be switched between "installed" and "uninstalled" to indicate whether each sensor in the database has been installed or not.

Referring to Figure 3, there is shown a process flow of a method for performing a sensor selection and installation process, according to some embodiments.

In general, to perform an installation, a site survey is conducted of the area or environment to be monitored, such as machinery room 110. Method 300 starts at step 301, where it is decided that a new system of sensors 130 is to be installed. At step 302, any current concerns with the site, such as machinery room 110, may be established. For example, a survey may be performed, asking workers whether they feel that the room or any equipment within the room is to hot or cold, too humid, too noisy or vibrating excessively. In some embodiments, this information may be used to determine suitable profiles for sensors to be installed. At step 303, a site inspection may be carried out. This may include an inspection of machinery 120 in machinery room 110, as well as a general inspection of machinery room 110, in order to identify where sensors 130 should be placed. Once the site survey has been performed, a list of sensors 130 required to monitor the machines 120 and the machinery room 110 may be created for the site. The list may be stored on an uninstalled sensor database 290.

At step 304, a quotation may be prepared based on the list of sensors 130 that are determined to be required, along with a contract for the customer in charge of machinery room 110 to sign. If the customer does not agree with the quotation or contract at step 305, method 300 may move to final step 317, and no installation is performed. If the customer agrees to sign the contract, method 300 may move to step 306. At step 306, a new entry is created in location database 220 for the location of the installation site, which may be machinery room 110. This entry may include a description site name, as well as GPS coordinates for the site. At step 307, the site survey may be reviewed. According to some embodiments, where a paper or electronic list or database of sensors to be installed has been created, the list or database may be reviewed instead of or in addition to the site survey. For each sensor 130 that is to be installed, the desired operational parameters are checked. For example, for a temperature sensor to be installed in an office building, a temperature of between 23 and 25°C may be designated to be the desired temperature, with a temperature above 29°C or below 20°C causing an alarm condition. Step 307 is performed for each sensor 130 to be installed.

At step 308, the profile database 240 is checked to determine whether a sensor profile entry exists for the operational parameters identified at step 307. If the sensor profile does not exist, a new entry is made in profile database 240 outlining the operational parameters of the new sensor profile, and in some embodiments, the expected profile ranges may be checked, for example, with the customer, at step 309. The identified or newly created sensor profiles are associated with the sensors to be installed in the uninstalled sensor database 290. The method may then move to step 310. If the sensor profile already exists, method 300 may move straight from step 308 to step 310. At step 310, the required sensors to be installed and any other necessary stock may be ordered.

At step 311, it may be determined whether the scannable codes 260 are to be identifier codes, profile-type codes or device-type codes and the scannable codes 260 are generated. According to some embodiments, identifier codes may comprise only a unique sensor identifier. According to some embodiments, both profile-type codes and device-type codes comprise a unique sensor identifier and a profile identifier. However, for a profile-type code, the profile identifier may comprise a profile for sensor 130 associated with the sensor identifier. The profile identifier may also include a device type or data type of the sensor (e.g. temperature sensor, humidity sensor). In contrast, for a device-type code, the profile identifier may include a device type or data type of the sensor but not any information regarding the sensor profile. Using a profile- type code may require that the device type or data type of the sensor is matched up to or associated with the sensor identifier of the particular sensor 130 to be used at the time that the profile-type code is created, but may make the installation process easier as the installer may not need to select a particular profile of sensor 130 at the time of installation. In some embodiments, the sensor identifier is associated with each sensor 130 during sensor manufacture and may be stored on sensor 130 in non-volatile memory, for example. In some embodiments, the unique sensor identifier is transmitted along with sensor readings to readings database 250 once the sensor is installed to allow the readings of particular sensors to be readily identifiable. In some embodiments, sensor installation data including the sensor identifier, the sensor type and in some embodiments, the sensor profile identifier may be retrieved from uninstalled sensor database 290 and converted into a scannable code by a coding algorithm running on a computing device (not shown). In some embodiments, sensor installation data may be encoded in a URL and converted to a scannable code 260 or other code and associated with sensor 130. In some other embodiments, the sensor installation data may be encoded into a series of letters and/or numbers that are converted into a scannable code 260 or other code and associated with sensor 130. In some embodiments, a pointer to an address from where the sensor installation data may be retrieved, for example, an address in the uninstalled sensor database 290, is encoded in the generated scannable code 260.

Once the codes are generated, , the method moves to step 312, where the scannable code 260 is printed. The scannable code 260 may be printed on-site or off-site. For profile-type codes, the code may be printed and attached after the site survey is complete. The installer may need to carefully match sensor identifiers of each sensor to the correct printed codes when profile-type codes are used. The printed scannable code 260 may be attached to the sensor 130 or sensor packaging. In some embodiments, scannable code 260 may be printed onto a sticker 1030, as shown in Figure IOC, which is then physically attached to the case or packaging of sensor 130. In some embodiments, sticker 1030 may also contain other information, such as a sensor type label 1032, a sensor type symbol 1034, and sensor ID number 1036, for example.

For device-type codes, scannable code 260 may be printed at the time of manufacture, to ensure that the sensor identifier printed on scannable code 260 matches the sensor identifier assigned to sensor 130. In some embodiments, a sensor identifier may be written to memory in sensor 130 after a scannable code 260 has been attached to sensor 130. Thus, if the codes are to be device-type codes, method 300 moves straight from step 311 to 313.

At step 313, sensors 130 may be shipped or otherwise provided to the customer. Sensors 130 are installed in machinery room 110 and configured at step 314. When the installation occurs on site, an engineer or installer locates the machinery 120 or the locations in machinery room 110 where sensors are to be installed, physically attaches sensors 130 in those locations, and activates the sensors 130 so that they can begin taking readings. Once each sensor 130 is powered on, it begins sending readings to readings database 250 directly or indirectly, for example via server 280 via communications network 285. Depending on the design of sensor 130, this may be done directly via an inbuilt cellular data modem in sensor 130, via a local area gateway and cellular modem with radio transmission for sensor data, via Wi-Fi, ethernet or other wired communication protocol and appropriate software connectors to enable access to the readings database 250. In some embodiments, entries made in readings database 250 include the reading value and the unique sensor identifier for sensor 130, and may also include the type of data recorded (e.g. temperature, humidity), and/or a timestamp.

To complete the installation, the engineer or installer uses handheld computing device 210 to scan scannable code 260. An application running on handheld computing device 210 is configured to cause handheld computing device 210 to communicate with geo- location service 270 to determine current geo-location information for the handheld computing device 210. In some embodiments, this geo -information may be compared to the location information provided by scannable code 260 to verify that sensor 130 is being installed at the correct site. The application running on handheld computing device 210 is further configured to transmit the geo-location information and sensor installation data comprising the information derived from scannable code 260, including the sensor identifier, sensor profile information and, in come embodiments, location information, to server 280 to cause a new entry containing the sensor installation data to be created in installed sensor database 230. This process is described in further detail below, with reference to Figure 4.

At step 315, each sensor 130 is tested to ensure that the operational parameters of the sensor profile are correct. If the operational parameters are not correct, the sensor profile entry in profile database 240 is edited at step 316. This may be done using handheld computing device 210 via a web-based user interface page, as seen in Figure 8. Once all the sensor profiles are correct, the installation is considered complete at step 317.

The handheld computing device 210 comprises a processor (not shown) and a memory (not shown) comprising executable code, which when executed by the processor, is configured to carry out steps of method 300. In some embodiments, a sensor configuration application comprising executable code is stored on memory of the handheld computing device 210 and when executed by the processor, is configured to perform steps 306 and 308 of method 300. For example, the sensor configuration application may be configured to cooperate with a browser application to provide a display to allow a user to create a new entry in location database 220. The sensor configuration application may be configured to receive location information such as a description site name and GPS coordinates for a site and in response to receiving the location information from the user, may be configured to transmit the location information directly to location database or to server 280 to cause a new entry to be created in location database 230.

The sensor configuration application to may be configured to cooperate with a browser application to provide a display on the user interface of the handheld computing device 210 to allow a user to view profile data recorded in profile database 240 and/or to input profile data in profile database 240. An example of such a display is discussed in more detail below with reference to Figure 8. For example, the sensor configuration application to may be configured to determine whether a sensor profile entry exists for particular operational parameters, such as those identified at step 307. The sensor configuration application to may be configured to allow a new entry to be made in profile database 240 outlining the operational parameters of the new sensor profile. The sensor configuration application to may be configured to associate an identified or newly created sensor profile with sensor identifiers of sensors to be installed, as recorded in the uninstalled sensor database 290.

Figure 4 shows a flowchart illustrating a method 400 of configuring a sensor as per step 314 as described above. Although some steps of method 400 are described as being performed by handheld computing device 210 and some steps are described as being performed by server 280, some or all of the processing steps may be performed on any one of handheld computing device 210, server 280 or an external device communicating with handheld computing device 210. Server 280 may comprise a server-side sensor configuration application stored in memory, which when executed by one or more of processors of server 280 is configured to perform the server side steps of the methods described herein, including method 300 and method 400. Method 400 is further illustrated in interaction diagram 500. Referring to Figures 4 and 5, at step 401 the method may starts when a sensor 130 is installed at an installation site. This may be on a piece of machinery 120 or in a machinery room 110, for example. At step 402, one or more scannable codes 260 associated with sensor 130 are scanned by an engineer or installer 501. Scannable codes 260 may be scanned using handheld computing device 210, or using a camera or scanner in communication with handheld computing device 210. Scannable codes 260 comprise sensor installation data, which may comprise a sensor identifier (sensor ID) and a sensor profile identifier, which may include one or more of a sensor type, and a sensor profile. According to some embodiments, scannable codes 260 may further comprise a desired installation location of sensor 130. In some embodiments, scannable code 260 encodes the sensor installation data as a URL, as described in further detail below with reference to Figure IOC. In some embodiments, scannable code 260 encodes the sensor installation data as a sequence of letters, number and/or symbols , as described in further detail below with reference to Figures 10A and 10B. In some embodiments, scannable code 260 encodes information required to retrieve the sensor installation data from remote storage, such as uninstalled sensor database 290. When scanned, for example, using a scanning application stored in memory of handheld computing device 210 and executed by processor of handheld computing device 210, scannable code 260 may cause a browser application running on handheld computing device 210 to open the coded URL, to decode the scannable code 260 to retrieve the information stored by the coded sequence, which may include the sensor installation data or may be information required to retrieve the sensor installation data from remote storage. In some embodiments, scanning the scannable code using a scanning application running on handheld computing device 210 may cause a decoding application running on handheld computing device 210 to decode the information stored by the coded sequence of scannable code 260.

Handheld computing device 210 may be configured to retrieve the sensor installation data associated with scannable code 260 from the URL, or based on the decoded information. In some embodiments, the sensor configuration application running on the handheld computing device 210 may be configured to provide the scanned scannable code 260 to server 280 and server may be configured to decode and/or retrieve the sensor installation data. Once the sensor installation data associated with scannable code 260 is retrieved, this information is communicated by handheld computing device 210 or server 280 to installed sensor database 230 via communications network 285. In some embodiments, at step 403, server 280, and in particular, server-side sensor configuration application, may determine whether the sensor identifier (sensor ID) associated with scannable code 260 already exists on installed sensor database 230. In some embodiments, if the sensor identifier is found in installed sensor database 230, this is an indication that the sensor has been previously installed, and the method moves to step 404. At step 404, site permissions may be checked against the user credentials of installer 501. If installer 501 has authorisation, sensor configuration application may cause handheld computing device 210 to display a sensor view page for sensor 130 at step 416, an example of which is shown in Figure 7. In some embodiments, if the sensor identifier is found in installed sensor database 230, sensor configuration application may cause handheld computing device 210 to communicate with geo- location service 270 to determine the location information of computing device 210, which may be provided by geo-location service 270 as latitude and longitude GPS coordinates. If the location associated with the sensor identifier does not match the location information determined by handheld computing device 210, an error may be displayed, alerting the installer that the sensor has already been installed at a different location. If installer 501 does not have authorisation to view the sensor page, the method moves to step 405 and an access error message is displayed on handheld computing device 210. Installer 501 may be able to exit from the error message and scan another code 260 to start the method again from step 401.

If at step 403 it is determined that the sensor identifier does not exist on sensor database 440, this may indicate that sensor 130 has not yet been installed. In some embodiments, handheld computing device 210 communicates with geo-location service 270 to determine the location information of computing device 210, which may be provided by geo-location service 270 as latitude and longitude GPS coordinates at step 406. In some embodiments, handheld computing device 210 may communicate with geo- location service 270 to determine the location information of computing device 210 in the event that a sensor has not yet been installed. For example, server-side sensor configuration application may be configured to cause server 230 to transmit a notification comprising an indication that the sensor has not yet been installed to handheld computing device 210. At step 407, the coordinates provided by geo-location service 270 may be used to find nearby locations in location database 220 and to display on user interface display of the handheld computing device 210 a selection of the nearest locations to handheld computing device 210, as shown in Figure 6 and described in further detail below. In some embodiments, the closest location may be automatically pre-selected by handheld computing device 210. Installers 501 may have limited access to locations in some embodiments, and handheld computing device 210 may be configured to only present a subset of locations listed in location database 220 as options for installation. By pre-selecting the closest location, installer 501 may not need to enter any additional information to perform the sensor installation. In some embodiments, the scannable code 260 may comprise a desired installation location for the sensor and the sensor configuration application may be configured to compare the location information, for example, the GPS coordinates, to the desired installation location associated with scannable code 260 to ensure that sensor 130 is being installed at the correct installation site.

In some embodiments, at step 408, installer 501 may be asked to confirm the location. They may be able to change the selected location, as well as the name of the sensor to be installed, before confirming. If installer 501 does not see a location that matches, they may be able to create a new location in location database 220 at step 409, using the geo-location information provided by geo-location service 270 to handheld computing device 210. This new location may then be used for the remainder of the installation flow for sensor 130 and may remain available in location database 220 for installation of further sensors 130. If installer 501 confirms a pre-existing location at step 408, the method moves to step 410. If installer 501 cancels the installation at this point, sensor 130 is not configured, and any saved data about sensor 130 is deleted from installed sensor database 230.

At step 410, the sensor profile identifier from the scanned scannable code 260 is determined. If the sensor profile identifier includes a sensor profile, then at step 411, server 280 determines whether a matching sensor profile already exists in profile database 240. If no profile is found, or if the sensor profile identifier only includes the sensor type, then the data type of the sensor (e.g. temperature, humidity, vibration, etc.) which may form part of the profile identifier and/or the sensor profile identifier, is used to select a generic profile at step 412. In some embodiments, the installer may be presented with the option to select or edit the selected sensor profile at this stage. In some embodiments, the sensor profile can be changed or edited at a later stage via handheld computing device 210 or an external device, as described below in further detail with reference to Figure 8. At step 413, once the sensor profile and location have been identified, a new sensor entry with the unique sensors identifier as read from scannable code 260 is created in sensor database 240. According to some embodiments, scannable code 260 is created in sensor database by handheld computing device 210. According to some embodiments, scannable code 260 is created in sensor database by server 280. For example, the new sensor entry may include at least one of the sensor identifier, sensor profile and/or desired installation location associated with sensor 130 being installed. In some embodiments, the new sensor entry may include the sensor identifier, and at least one of a pointer to a profile database entry in profile database 240 and a pointer to a location database entry in location database 220. Access to the new sensor information within sensor database 230, and any associated readings in readings database 250, is controlled by the same rules that limit access to all sensors 130 at the site, so that only authorised installers 501 are able to access data related to sensor 130. At step 414, server 280 looks in readings database 250 to find readings that match the sensor identifier for the new sensor entry in sensor database 240. In some embodiments, if readings are found, which may be readings from a sensor that was recently turned on, for example, the latest reading value is compared to the sensor profile for sensor 130. This allows the current status of sensor 130 to be determined at step 415, based on the thresholds set by the sensor profile for various status types, as described in further detail below. Each sensor profile may be configured to define the status that should be displayed for sensor 130 for a range of readings. For example, a particular sensor profile may be configured to set a vibration sensor status to "HIGH" if sensor 130 senses a vibration of between 1000 and 2000mm/s. If no readings exist, the sensor status may be set to "UNKNOWN". Once the status has been determined, the sensor user interface page may be displayed at step 416, an example of which is shown in Figure 7. Method 400 may finish at step 417 when installer 501 closes out of the user interface page. Figure 6 shows handheld computing device 210 displaying an example of a user interface page 600 on user interface of handheld computing device 210. User interface page 600 may be displayed during the installation of a sensor 130, as described above with reference to Figure 4. User interface page 600 includes a sensor ID label 601, a "Check Location" virtual button 602, a "Change Location" virtual button 603, an installation site name 604, a map 605, a sensor name 606, a virtual "Confirm" button 607 and a virtual "Cancel" button 608. Sensor ID label 601 may show the sensor identifier of a sensor 130. Pressing the "Check Location" virtual button 602 may cause handheld computing device 210 to communicate with geo-location service 270 to determine the location of handheld computing device 210. Pressing the "Change Location" virtual button 603 may cause handheld computing device 210 to display a list of selectable location options for installer 501 to choose from. Installation site name 604 may give a description of the selected location or site name. Map 605 may display the nearest selectable location to the determined location of handheld computing device 210 on a map. Sensor name 606 may display a descriptive name associated with sensor 130, which may be editable by installer 501. Pressing the virtual "Confirm" button 607 may cause handheld computing device 210 to save all changes to the sensor data and exit the page, while pressing virtual "Cancel" button 608 may exit the page without saving any changes made. Figure 7 shows handheld computing device 210 displaying an example of a user interface page 700 on user interface of handheld computing device 210. User interface page 700 may display sensor readings once sensor 130 has been installed, as described above with reference to Figure 4. As shown, user interface page 700 includes a location label 701, a sensor name label 702, a sensor reading value 703, a sensor status 704, a threshold spectrum 705, a graph of sensor readings 706, a virtual "Edit" button 707 and a virtual "Delete" button 708.

Location label 701 may display the location of the sensor 130. Sensor name label 702 may display a descriptive name associated with sensor 130. Sensor reading value 703 may display the current sensor output as a numerical value. This may include the units of the output measurement, and the value may be calculated from raw readings from sensor 130 with any scaling and calibration options from the sensor profile. Sensor status 704 may show a status that corresponds to the sensor output value, based on the selected sensor profile. The sensor status may be calculated by comparing the adjusted value of the latest reading from sensor 130 to the thresholds in the active profile of sensor 130. For example, the sensor status may be calculated by server 280 in some embodiments. Threshold spectrum 705 may graphically show the spectrum of thresholds as defined by the active sensor profile. Graph 706 may show the history of sensor readings in a trend graph, if a number of readings have already been collected. Pressing virtual "Edit" button 707 may allow installer 501 to be able to make adjustments to the calibration, name, or profile of sensor 130. Pressing the "Edit" button may cause handheld computing device 210 to communicate with server 280, to cause server 280 to update the data stored in installed sensor database 230 to reflect any changes made to the calibration, name, or profile of sensor 130 by installer 501 through the user interface of handheld computing device 210. Pressing virtual "Delete" button 708 may cause handheld computing device 210 to delete the sensor readings for sensor 210 from readings database 250.

Handheld computing device 210 or another external computing device, which may be a desktop computer, laptop computer, or handheld computing device in some embodiments, may be able to access a user interface 800 to create and edit profiles, as shown in Figure 8. User interface 800 may display a sensor profile name 801, a sensor data type 802, a sensor type 803, a number of statuses 804 and an "Add Range" virtual button 809. Each status may have a threshold lower bound 805, a threshold upper bound 806, a use case 807, and an alert flag 808.

Sensor data type 802 may be selectable between being continuous, cumulative, or discrete. A continuous data type may correspond to a continuous series of readings with no restriction on values, such as temperature reading values. A cumulative data type may correspond to a cumulative series of ever increasing numbers, which may be used for usage meters for water or electricity, for example. A discrete data type may be correspond to discrete reading for specific conditions, such as 1 for "on" and 0 for "off, for example.

Sensor type 803 may be based on a specific type of reading value, such "temperature", "humidity", "vibration", or another reading value type. These data types may represent the environmental condition to be monitored by sensor 130.

Profiles allow the mapping from various ranges to specific user-meaningful conditions based on the values chosen for each status 804. Thresholds are defined from a lower bound 805 to an upper bound 806. This range is then named based on the use case 807. Furthermore, each status 804 can be flagged for processing by the system based on its alert flag 808.

Once a sensor profile is updated, all sensors 130 that use that profile will be updated to function with the new threshold. Readings output by sensors 130 are transmitted via communications network 285 and stored in readings database 250. Each sensor 130 is identified by a globally unique identifier, as stored in installed sensor database 230, which in some embodiments, may function like a MAC address. Each sensor reading stored in readings database 250 may contain the current sensor reading value, the sensor identifier, and the sensor data type. Readings may be recorded regardless of whether the sensor has been pre-configuration, or whether the sensor data has been stored on installed sensor database 230.

The data type sent by sensor 130 to readings database 250 can be matched to a data type which the sensor profile is based on. The combination of data type and sensor identifier allow sensor profiles to be matched with sensors 130 post installation. According to some embodiments, sensor 130 may send only the current sensor reading value and the sensor identifier to readings database 250, and the sensor identifier alone may be used to match with sensors 130 post installation.

In some embodiments, a sensor 130 may be configured to sense vibration. ISO 10816 defines acceptable vibration for various classes of electrical motors, as shown in table 900 of Figure 9. By attaching a wireless vibration sensor 130 which measures vibration using an accelerometer configured with a corresponding sensor profile to a machine 120, alerts can be generated based on the vibration of machine 120. For example, based on table 900, for a Class I small machine, the sensor profile can be set to thresholds in mm/s such as:

0.0 < OFF <= 0.1

0.1 < ON <= 0.71

0.71 < OK <= 1.8

1.8 < CHECK <= 4.5

4.5 < ISSUE <= 25.0

25.0 < REPAIR <= 50.0

In some embodiments, a sensor 130 may be configured to sense temperature. A manufacture of wooden trusses, used for roof construction, requires timber to be cured at a moderate temperature. When older heating units are not fully automated with a thermostat, it is possible to install wireless temperature sensors 130 to generate alerts if the temperature gets too hot, to allow operators to take action. The sensor profile can be set to thresholds in degrees C such as: 0.0 < NORMAL <= 40.0

41.0 < HOT <= 44.0

45.0 < TOO HOT <= 50.0

For example, in Australia, when public cinemas become too hot or too cold, the cinema is forbidden from selling tickets until the environment is back to a nominal comfort level. By installing wireless temperature sensors 130 in each theatre, a cinema is able to take action before the cut-off temperatures are exceeded. Remedial action can be taken without the need to wait for customer complaints. The sensor profile can be set to thresholds in degrees C such as:

0.0 < COLD <= 18.0

18.0 < COMFORT <= 23.0

23.0 < HOT <= 35.0

In some embodiments, a sensor 130 may be configured to sense humidity. For example, high-end hotels in the tropics ensure customer comfort by using air conditioners to keep the temperature acceptable. However, relative humidity is also a key factor in how comfortable a space is for people. By installing wireless humidity sensors 130 in a sample of rooms, hotel managers are able to track and judge the effectiveness of heating, ventilating, and air conditioning (HVAC) equipment and make decisions on upgrades and replacements. The sensor profile can be set to thresholds in percentage humidity such as::

0.0 < DRY <= 50.0

50.0 < GOOD <= 60.0

60.0 < HUMID <= 75.0

75.0 < VERY HUMID <= 100.0

In some embodiments, scannable code 260 may be used to encode sensor installation data, which comprises a sensor identifier, a sensor profile identifier, which may include an indication of a sensor profile and/or an indication of a sensor type, and in some embodiments, a desired installation location. In some other embodiments, different types of scannable codes may be used to encode this data in different ways. In some embodiments, where device-type sensor codes are used (as described above with reference to Figure 3), an installer 501 may carry a sheet or booklet of scannable codes, which may be bar codes, QR codes, or RFID tags, or other codes. Each code may represent a specific sensor profile. For example, a code could be for "Hotel Room Humidity". Furthermore, each sensor 210 may have a scannable code that represents the sensor identifier. Using an application executed on handheld computing device 210, the installer 501 may be able to scan the sensor identifier code on sensor 130, and also scan the corresponding sensor profile code from the reference sheet. The reference sheet may be printed with a list of sensor profiles specific to the site being configured, or be a generic list suitable for all sites. Each code in the reference sheet may corresponds to a matching sensor profile stored in profile database 240.

In some embodiments, the sensor identifier and sensor type may be encoded in a single bar code. For example, for a barcode representing the number 004/998877, the digits "004" may correspond to a particular sensor type, such as temperature or humidity, and the digits "998877" may correspond to the sensor identifier. An example of such a barcode 1010 is shown in Figure 10A. An application running on handheld computing device 210 may be able to decode this sequence of numbers, break it down into its various components and lookup and/or create a new configured sensor entry in installed sensor database 230 based on the sequence. According to some embodiments, the sensor identifier and sensor profile may be encoded in a single bar code. For example, for a barcode representing the sequence 998877/P00003, the sequence "998877" may correspond to the sensor identifier, and the sequence "P00003" may correspond to the sensor profile, such as "Indoor Temperature, alerts over 28 deg C", for example. An example of such a barcode 1020 is shown in Figure 10B.

An application running on handheld computing device 210 may be able to decode this sequence of numbers, break it down into its various components and lookup and/or create a new configured sensor entry in installed sensor database 230 based on the sequence. According to some embodiments, the barcode may be a URL that can be opened by handheld computing device 210, which stores the sensor identifier and sensor profile. For example, the URL may be https://qr.example.eom/s/004/998877 , in which https://qr.example.eom/s/ may correspond to the protocol, host and routing prefix, "004" may correspond to the sensor type, and "998877" may correspond to the sensor identifier. According to some embodiments, the URL may be encoded into a QR code, such as code 260 on sticker 1030 as shown in Figure IOC.

An application running on handheld computing device 210 may be able to open this URL, and lookup and/or create a new configured sensor entry in installed sensor database 230 based on the sensor identifier and sensor type.

It will be appreciated by persons skilled in the art that numerous variations and/or modifications may be made to the above-described embodiments, without departing from the broad general scope of the present disclosure. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive.

Claims

CLAIMS:

1. A handheld computing device for configuring sensors, the device being in communication with a server across a communications network and comprising a processor and a memory, wherein the memory comprises a sensor configuration application, which when executed by the processor, is configured to cause the handheld computing device to:

receive a scannable code, the scannable code associated with sensor installation data comprising at least a sensor identifier and a sensor profile identifier;

determine the sensor installation data from the scannable code;

2. A handheld computing device for configuring sensors, the device being in communication with a server across a communications network and comprising a processor and a memory, wherein the memory comprises a sensor configuration application, which when executed by the processor, is configured to cause the handheld computing device to:

receive a scannable code, the scannable code associated with sensor installation data comprising at least a sensor identifier;

determine the sensor installation data from the scannable code;

3. The handheld computing device of claim 1 or claim 2, wherein the memory of the handheld computing device comprises a scanning application, which when executed by the processor, is configured to cause the handheld computing device to scan the scannable code provided on a sensor to be configured and to provide the scannable code to the sensor configuration application.

4. The handheld computing device of any one of claims 1 to 3, wherein the scannable code comprises a unified resource locator (URL) and determining the sensor installation data from the scannable code comprises retrieving the sensor installation data from a webpage associated with the URL.

5. The handheld computing device of claim 4, wherein the memory of the handheld computing device comprises a browser application, which when executed by the processor, is configured to display the webpage associated with the URL on a user interface of the device.

6. The handheld computing device of any one of claims 1 to 3, wherein the handheld computing device is configured to decode the sensor installation data from the scannable code.

7. The handheld computing device of any one of claims 1 to 3, wherein the handheld computing device is configured to use the scannable code to retrieve the sensor installation data from a database in communication with the device across the communications network.

8. The handheld computing device of any one of the preceding claims, wherein the device is configured to determine the geographical location of the handheld computing device and to transmit the geographical location to the server in response to receiving a request for the geographical location of the handheld computing device from the server.

9. The handheld computing device of any one of the preceding claims, wherein the sensor profile identifier comprises at least one of a sensor profile indicator and a sensor type indicator.

10. The handheld computing device of claim 8, wherein the sensor profile indicator corresponds to a set of desired operational parameters of the sensor to be configured.

11. The handheld computing device of any one of the preceding claims, wherein in response to receiving an indication that there is an existing entry in a sensor database for the transmitted sensor installation data, the device is configured to receive data relating to sensor readings from a sensor readings database and to execute a browser application to display information corresponding to the received sensor reading data on a display of a user interface of the device.

12. The handheld computing device of any one of the preceding claims, wherein in response to receiving an indication that there is no existing entry in a sensor database for the transmitted sensor installation data, the device is configured to execute a browser application to provide at least one user selectable option on a display of a user interface of the device to allow a user to edit the sensor installation data and the geographical location for the sensor to be installed.

13. The handheld computing device of claim 11, wherein the device is further configured to transmit the edited sensor installation data and the geographical location to the sensor database as a new database entry.

14. The handheld computing device of claim 11 or claim 12, wherein the device is further configured to execute the browser application to provide at least one user selectable option on a display of a user interface of the device to allow the user to select from a number of sensor profile indicators based on the sensor installation data.

15. The handheld computing device of any one of claims 11 to claim 13, wherein the device is further configured to execute the browser application to provide at least one user selectable option on a display of a user interface of the device to allow the user to select from a number of installation locations based on the geographical location.

16. The handheld computing device of any one of claims 11 to claim 14, wherein the device is further configured to execute the browser application to provide at least one user selectable option on a display of a user interface of the device to allow a user to select a sensor profile from a sensor profile database based on the sensor type information.

17. The handheld computing device of any one of the preceding claims, wherein the geographical location comprises one or more GPS coordinates.

18. A server for configuring sensors, the server being in communication with a handheld computing device across a communications network and comprising one or more processors and a memory, wherein the memory comprises a sensor configuration application, which when executed by the one or more processors, is configured to cause the server to:

in response to determining that an entry for the received sensor identifier does not exist in the sensor database, create a new entry in the sensor database comprising the received sensor identifier, the received sensor profile and the received geographical location.

19. The server of claim 18, wherein executing the sensor configuration application causes the server to retrieve data relating to sensor readings from a sensor readings database and to transmit information corresponding to the received sensor reading data to the handheld computing device in response to determining that an entry for the received sensor identifier does exist in an sensor database,.

20. The server of claim 18 or claim 19, wherein executing the sensor configuration application causes the server to transmit a request for the geographical location of the handheld computing device to the handheld computing device in response to receiving sensor installation data from the handheld computing device.

21. The server of any one of claims 18 or claim 20, wherein the server is configured to decode the received sensor installation data.

22. The server of any one of claims 18 to 21, wherein the server is configured to retrieve the sensor installation data from a database in communication with the server across the communications network in response to receiving a request for the sensor installation data from the handheld device and to transmit the sensor installation data to the handheld computing device.

23. The server of any one of claims 18 to 22, wherein the sensor profile identifier comprises at least one of a sensor profile indicator and a sensor type indicator.

24. The server of any one of claims 17 to 23, wherein the geographical location comprises one or more GPS coordinates.

25. A system for configuring sensors, the system comprising the handheld computing device of any one of claims 1 to 17 and the server of any one of claims 18 to 24.

26. A computer implemented method for configuring sensors operable on a handheld device, the method comprising:

determining a geographical location of the handheld computing device; and transmitting the geographical location to the server across the communications network.