FIELD OF THE INVENTION

[0001] The present invention relates to systems, methods and apparatus for automated routine testing, data acquisition, transfer and management, remote monitoring, condition based assessment and alarm/isolation notification, of fire protection systems and equipment. However, the present invention may be applicable to other fire systems.

BACKGROUND TO THE INVENTION

[0002] In the field of Fire Protection Systems and Equipment (FPSE), the Australian Standards AS 1851 -2012 incorporates all fire detection and protection systems and equipment as listed under this standard and includes, but is not limited to, the fire detection and alarm systems (FDAS), sprinkler systems, fire pump systems, deluge systems and special hazards systems.

[0003] Fire detection and alarm systems are generally installed in commercial, retail, industrial, healthcare and government buildings to name a few types of applications. The fire detection and alarm system generally incorporate both a Fire Indicator Panel (FIP) and an Occupant Warning System (OWS). The Fire detection and Alarm system consists of a FIP, detection devices namely smoke obscuration (photo optical or ionisation) and thermal (heat) detectors, either conventional, analogue addressable or multi criteria (combination of smoke and thermal detection) and generally configured in a loop of devices which may include, manual call points, detectors, strobe lights, other Visual Warning Devices (VWD), and various other types of devices.

[0004] The FDAS has detection devices that monitor the ambient conditions within the building envelope for an indicative fire related condition either generated from a heat or smoke source. Other devices include manual call points, which are operated by breaking the glass in the event of a fire or similar event. [0005] The FDAS interface alarm signals from another system, e.g. a Heating Ventilation and Air Conditioning (HVAC) system or a smoke control system or a sprinkler system etc. All main FIP's are connected to Alarm Signalling Equipment (ASE) to alert a local fire and rescue authority of alarm activation and a potential fire condition.

[0006] Once the FIP is activated by a detection device it initiates the Occupant Warning System (OWS) or Emergency Warning and Intercommunications System (EWIS) to provide alert tones to the occupants that the building may need to be evacuated. Typically, all facilities have a fire warden or floor wardens with a chief warden to take charge in the event of alarm activation. They will investigate the cause of the alarm and liaise with the fire and rescue authority on their arrival. It will be appreciated that the fire and rescue authority may be known by another name, depending on the county, state, country or other locality in which the building is situated. For example, in Queensland, Australia, the fire and rescue authority is known as the Queensland Fire and Rescue Service (QFRS). The FIP provides crucial information through the location and description of the device that has activated and therefore it is paramount for the information to be accurate. Once an alarm is activated, if unchecked, it will quickly escalate to the evacuation signal to notify all occupants to evacuate the facility to the designated evacuation assembly areas.

[0007] The assigned detection devices are triggered once a pre-set threshold set by the Original Equipment Manufacturer (OEM) or a programmed value (heat or smoke level) is exceeded. Triggering of the assigned detection devices will in most cases initiate the ASE, which is monitored by the relevant fire and rescue authorities, who on receiving an alarm activation notification would dispatch a fire fighting appliance/unit to the facility.

[0008] A fire detection and alarm system needs to be seen, but not heard until needed. Every false alarm reduces the integrity of the system in the eyes of the occupants. Building owners are requesting more reliability from their building assets. Facility managers are faced with limited budgets and look for ways to increase the return on investment to building owners. More accurate information is required to extend the life of the assets as well as details of end of life and maintenance costs for budget preparation. [0009] The most significant assets within an analogue addressable fire system are the multiple detection devices which are generally a combination of smoke and thermal devices. Although the cost of the detection device is low when compared with the impact of the device activating, as a false alarm, the total financial impact of the false alarm will be many times the value of a detector. For example, in Australia, a $150 smoke detector, if it activates due to contamination rather than a genuine fire condition, will automatically call the fire and rescue authorities who typically will charge $1 ,300 to turn out to the facility. It will still require a technician to replace the faulty detector plus a further $200 - $500 (normal hours or after hours) to attend the site and swap out the contaminated detector, which equates to $350 - $650, plus the $1 ,300 fire and rescue authority charge, which will result in a substantial cost to the property owner. Multiple instances of activation due to contamination multiply the cost to the property owner.

[0010] Most Original Equipment Manufacturers of Fire Indicator Panels (FIPs) have developed obscuration reports within the FIP program that monitor the analogue addressable detectors to provide a means to identify a clean/dirty state of the detectors which is represented as an analogue value. Each OEM assigns their own notional analogue value to the device.

[0011] If the detectors are identified early as being contaminated by running obscuration reports where applicable the detectors could be changed as a preventative measure and not as corrective maintenance. The obscuration levels can be downloaded from the FIP locally using a notebook or laptop computer, or in some cases, if part of a major network, at a remote workstation.

[0012] Analogue addressable smoke detectors, either of the photo-optical or ionisation type, provide analogue values that indicate smoke obscuration levels, within the smoke detectors chamber. The level of obscuration is the density of smoke in the chamber represented as an analogue value and is stored in the FIP database. The obscuration reports are specific to the OEM brand. Most smoke detectors used today are of a photoelectric design. Photoelectric detectors determine the light obscuration level with the detector sensing chamber and trigger an alarm condition once the obscuration level exceeds the quiescent value. If the detector is operating within its design parameters, e.g. it has not reached a "contaminated" state, the cause of the alarm is most likely due to the concentration of smoke within the chamber. Local access to the FIP database to download obscuration reports is still provided via a serial port using a laptop, tablet or similar.

[0013] Thermal detection devices are used where smoke detectors are not suitable due to an operating environment, e.g. where they are exposed to either steam or dust. Reference can be made to the Australian Standard AS 1670-1 selection guide for the selection of appropriate detectors and equivalent standards in other countries.

[0014] The Fire Detection and Alarm Systems (FDASs) are maintained on a monthly and annual basis throughout Australia, to meet the building codes and relevant Australian Standards - AS 1851 to verify the general system operation and that in the event of an alarm condition the system would alert the occupants of an impending evacuation, and contact the fire and rescue authorities.

[0015] On a monthly basis the FIP, sprinkler system, pumps etc. are tested and the ASE is isolated as it is placed in a test mode of operation, and the OWS/EWIS is operated. This includes sound and/or visual warning devices which are initiated monthly, to verify their operation only.

[0016] The FDAS requires annual testing of the FIP and its dedicated devices and are generally tested with one zone isolated at a time once placed in test. There are some systems where the entire system is isolated for the annual test.

[0017] The detection devices are checked, at the nominated percentages under the prescribed Australian Standard, e.g. 50% of all smoke detectors and 20% of all thermal detectors and 100% of all manual call points per annum. Other percentages and checking frequencies may apply in other countries. This is typically performed using two technicians, one located at the FIP to communicate, via a two way radio or similar, the result to the other technician whilst testing each detector or device. The smoke or thermal detector testing is conducted using a fire detection test kit comprising an artificial smoke canister at the end of a long pole that can be triggered by the "tester". The heat detectors are tested using the same test kit containing a battery powered source of heat. This allows the technician to replicate the smoke/heat condition and once initiated its condition is verified at the panel by that technician. Other devices, e.g. manual call points, concealed space detectors, strobe lights, speakers, horns etc. are also tested as nominated under the Australian Standard, or equivalent standards in other countries. The results are recorded by the technician at the FIP and all anomalies are reported to the customer for rectification.

[0018] Whilst conducting the tests the technician at the FIP watches for a real fire condition within the building and would take the necessary steps to confirm that condition, and place the system back into normal mode to enable the ASE to be triggered.

[0019] Some FIP's are equipped with a single person test function that allows the fire technician to perform a single person test and an annual fire test of the system. Each OEM describes single person testing in their own way, for example, Single Man Test or Walktest.

[0020] Currently, FIPs are not configured for a single person test as they rely on either a sequential order of testing, i.e. a zone by zone approach to perform the annual device testing, or isolation of all the programmed FIPs for all devices connected to the FIPs before testing can commence. There is also a lack of confidence in using a single person test feature by the technician if they are working alone. The FIP is generally not programed or zones are not configured to allow ease of operation to test the devices, or technicians are unable to see the text or perform end to end checks, thus preventing the design features of the FIP to be fully utilised.

[0021] To obtain a list of detectors and their contamination levels (obscuration reports) from an existing FIP, the technician must use a laptop computer or similar. Most FIPs have a RS 232 printer port to allow for reports to be printed from the device. The technician typically boots the laptop up and signs in to Windows or other operating system. The technician opens a terminal software in the form of a terminal emulator, serial console and network file transfer application, an example of which is PuTTy, which supports various network protocols, such as SSH and Telnet and enables connection to a serial port. The technician configures the serial port on the computer to the required baud rate and connects the laptop to the FIP via a RS232 cable. Cable configurations vary depending on the brand of FIP. Software is then opened on the laptop to allow the data stream that is normally sent to a printer to be intercepted at the printer port. The data collected is then saved to the hard drive on the laptop, and can be assessed by the technician to determine which devices exceed the OEM predetermined contamination analogue value, and the customer is then advised of any devices that require replacement. This is time consuming and rarely performed. There is an expectation by the building owner that if offered, this should be performed free of charge and as part of the normal maintenance regime. In the event the obscuration report is downloaded the analogue values chosen could lead to detectors being replaced earlier than required as it may take a two month period, at best, to advise the customer, gain approval to proceed, and then attend to the replacement of the detectors.

[0022] Annual testing of smoke and thermal detectors relies on the technician recording which detectors and their locations are tested during that year's test. This would require a secure, easy to access database where this detail can be stored for future reference, e.g. the annual test the following year. This level of record keeping is not a mandatory Australian Standards requirement and is therefore seldom performed.

[0023] Currently there is no way to predict corrective maintenance requirements in advance, e.g. to determine in advance when detectors would need to be replaced in the foreseeable future. If accurate predictions could be provided it would greatly assist building owners/managers in preparing CAPEX budgets and in the long term asset management planning process.

[0024] Although a single person test function has been incorporated within many brands of FIP in the last 20 years, there has been reluctance by fire alarm technicians, facility managers and building owners to use the function as the system may not have been commissioned properly and the detector names and locations are often incorrect. There is no way currently to validate which detectors, interfaces and devices have been tested in a given year, and as a result many detectors may be missed during the annual test and the required completion rate of the devices, over the two - five year period, may never be achieved.

OBJECT OF THE INVENTION

[0025] It is a preferred object of the invention to provide systems and/or methods and/or apparatus that address one or more of the aforementioned problems of the prior art and/or provide a useful commercial alternative. [0026] A preferred object of the invention is to provide a cost-effective system and/or method and/or apparatus which automatically downloads data from the FIP/EWIS connected device identifiers, providing time and date verification details, verification of system testing results, from multiple types of FIP/EWIS manufacturers to various mobile, hand held and/or desktop devices.

[0027] Another preferred object of the invention is that the system and/or method and/or apparatus continuously interrogates processed data to determine pending corrective action, trends and patterns of the connected devices and provides long term storage of all captured data in a cloud based server. Stored data may include, but is not limited to, obscuration reports, which include analogue values of each analogue addressable smoke detector, alarm activations, fault activations, pressure sensing devices and fire system isolations.

[0028] Another preferred object of the invention is for the system and/or method and/or apparatus to relay relevant information to the technician via an internet connected wireless device (e.g. PDA) whilst conducting a single person test as the technician moves progressively through a building or facility, and should not rely on a specific testing sequence of the devices or detectors. It would then provide an accurate, validated, historical account of each device/detector, pass or fail and would verify the location of each device/detector.

[0029] Another preferred objective of the invention is to ensure that the fire technician is alerted to an actual fire condition whilst the FIP is isolated, whilst conducting any testing.

[0030] Another preferred object of the invention is to accurately record which smoke detection devices, thermal detection devices, manual call points (MCP's) and any other nominated fire system device/s were tested, recorded and the results stored, in a given time period, e.g. year.

[0031] A preferred object of the invention is to manage analogue addressable smoke detectors and alert the owner of contamination levels exceeding a pre-set obscuration reference value thus notifying of impending failure/s well in advance. This will therefore reduce unwanted fire alarms associated with contaminated detectors. [0032] Another preferred object of the invention is to facilitate single person testing of other fire systems including, but not limited to, the testing of sprinkler systems and suppression systems.

SUMMARY OF THE INVENTION

[0033] Generally, embodiments of the invention relate to an apparatus, a system and a method to gather specified data from a fire indicator panel (FIP) and related systems and devices of fire protection systems and equipment. Embodiments of the invention include accessing, processing and validating the specified data, providing secure two-way communication to a cloud based server, sending and receiving secure data from a database of the cloud based server to the FIP and mobile computing devices, such as smartphones, tablets and PDAs, and long term storage of the data to be accessed as required by field technicians, end users, and authorised parties.

[0034] The inventors have recognised the benefit of remotely accessing data via a secure communications system, from an FIP, and by continuously accessing, storing, validating and analysing the data to achieve a number of outcomes. These outcomes include the ability to perform single person fire systems testing confidently, verification in real time of all devices tested, and automatic notification of impending smoke detector alarms due to contamination levels approaching or exceeding preset values.

[0035] The inventors have developed a low-cost apparatus to interface to various brands of FIPs/EWISs to automatically access all relevant data nominated, in real time, and relay this data securely, to a cloud based server, via the cellular 3G/4G network. Data is stored in the cloud based server/s database/s for extended periods of time to allow, for example, instant retrieval of previous test results for testing purposes, alarm status/events and relevant trends.

[0036] Data is stored in the cloud based server database, and then analysed/processed and transmitted, in its processed form, as required to a mobile device, such as a smartphone, tablet, laptop or PDA or to a desktop computing device. This enables the fire technician to perform the tests having all relevant data displayed automatically on the screen of the device. [0037] All relevant testing information is validated and stored and specific testing information is sent to the fire technician to enable single person testing to be conducted knowing that the information displayed on the screen are current and accurate. In the event a real fire alarm condition was triggered, an audible alarm and visual indication would appear on the screen of the technician's PDA device.

[0038] Fire alarm reporting alerts the technician or nominated party of a current or an impending issue. Once the fire protection system and equipment is placed in test mode a snapshot of obscuration reports is provided. On completion the apparatus verifies the status of the fire protection system and that it has been successfully reinstated.

[0039] In some embodiments, the screen of the mobile device is divided into two parts - one showing detail from the apparatus and the other showing processed information from the Cloud based server database, acting in unison.

[0040] As a skilled addressee would appreciate the present invention can be applied to most FPSE sections, where applicable, for the purpose of performing random and periodic testing, such as monthly, six monthly, annual or five-year testing. It allows all results to be captured in real time and the test results to be verified and stored remotely.

[0041] According to one form, but not necessarily the broadest form, the present invention resides in an apparatus for accessing a fire indicator panel (FIP), the apparatus comprising: a processor in communication with a memory; at least one universal serial bus (USB) port in communication with the processor; at least one converter coupled to the USB port to enable communication between the apparatus and the FIP; and at least one communications interface in communication with the processor to enable communication of data obtained from the FIP from the apparatus to one or more remote devices.

[0042] Suitably, the at least one converter is a USB to serial port converter for coupling to a serial port of the FIP. [0043] Suitably, the at least one communications interface is 3G/4G Wi-Fi modem.

[0044] Suitably, the apparatus further comprises at least one optical isolator/coupler coupled between the USB to serial port converter and the serial port of the FIP.

[0045] Suitably, the apparatus comprises one or more of the following: a network subscriber identity module (SIM) in communication with the at least one communications interface; a bridge rectifier for coupling between a power supply of the FIP; one or more voltage regulators coupled between the bridge rectifier and the processor; a configurable input/output connection in communication with the processor; a micro controller in communication with the configurable input/output connection.

[0046] Suitably, the one or more remote devices include one or more of the following: a mobile computing device, such as a smartphone, tablet, laptop or PDA; a static computing device, such as a cloud server or desktop computer; another apparatus for accessing a FIP.

[0047] According to another form, but not necessarily the broadest form, the present invention resides in a system for accessing and processing data relating to a fire protection system, the system comprising: an apparatus as described above for accessing a fire indicator panel (FIP) of the fire protection system; and a remote computing device in communication with the apparatus via a communication network for receiving data about the fire protection system retrieved by the apparatus via the FIP.

[0048] The system may further comprise a mobile computing device, such as a smartphone, tablet, laptop or PDA, in communication with the apparatus and/or the remote computing device, to display, for example, to a technician in real time the data relating to the fire protection system.

[0049] According to a further form, but not necessarily the broadest form, the present invention resides in a method for performing testing of a fire protection system, including components thereof, optionally using the aforementioned apparatus and/or system. [0050] According to another form, but not necessarily the broadest form, the present invention resides in a method of determining a likely end of life of a detector of a fire protection system, optionally using the aforementioned apparatus, the method comprising: acquiring a plurality of measurements of an obscuration value of the detector, optionally via the apparatus; calculating a rate of contamination of the detector based on the plurality of measurements of obscuration value; and determining a likely end of life of the detector based on the calculated rate of contamination of the detector and a nominal end of life value for the detector set by a manufacturer of the detector.

[0051] Suitably, the plurality of measurements is acquired periodically, such as every 30 minutes.

[0052] The method may comprise automatically detecting when a detector of the fire protection system has been changed, for example, by comparing a historic average daily obscuration value of a detector in a location with a current average daily obscuration value of a detector in the same location and determining a reduction in the average daily obscuration value of the detector in the same location.

[0053] Suitably, determining the likely end of life of the changed detector comprises:

recording a start of life (SOL) of the changed detector; filtering the reduced average daily obscuration values recorded for the changed detector; and calculating the rate of contamination of the changed detector based on the historic average daily obscuration values recorded for the detector in the same location.

[0054] Suitably, the method may comprise identifying a detector in a location in which building works or the like are taking place; comparing a rate of contamination of the detector during the building works or the like based on measured daily obscuration values with historic average daily obscuration values recorded for the detector in the same location; and determining if the rate of contamination of the detector has been artificially reduced.

[0055] Suitably, the method comprises comparing the rate of contamination of multiple detectors to determine a relative efficiency value for each detector.

[0056] The method may comprise determining a quantity of a model of detector to be reordered based on a likely end of life calculated for each detector in a loop of detectors of the same model and a recorded last order date for ordering a replacement detector where the model of detector is being phased out.

[0057] The method may comprise determining one or more of the following based on the plurality of measurements of the obscuration value of the detectors in the fire protection system: the detectors for which the obscuration value has incremented over a predetermined number of times over a predetermined period; the detectors for which the obscuration value has incremented over a predetermined threshold more than once within a predetermined period; the periods during which the obscuration value for one or more detectors has incremented over a predetermined number of times; the detectors for which the obscuration value has incremented over a predetermined threshold in consecutive predetermined periods.

[0058] The method can comprise determining an estimate of time required to carry out an annual test of the fire protection system based on historical annual test times.

[0059] According to another form, but not necessarily the broadest form, the present invention resides in a system to determine a likely end of life of a detector of a fire protection system, the system comprising: an apparatus comprising: a processor in communication with a memory and at least one port; at least one converter coupled to the port to enable communication between the apparatus and a fire indicator panel (FIP) of the fire protection system; and at least one communications interface in communication with the processor to enable communication with a remote computing device and a mobile computing device; wherein the apparatus is configured to acquire a plurality of measurements of an obscuration value of the detector from the FIP; and wherein the remote computing device is configured to: calculate a rate of contamination of the detector based on the plurality of measurements of obscuration value; and determine a likely end of life of the detector based on the calculated rate of contamination of the detector and a nominal end of life value for the detector set by a manufacturer of the detector.

[0060] It will be appreciated that the apparatus and/or the remote computing device and/or the mobile computing device is configured accordingly to perform the aforementioned steps of the method.

[0061] Further forms and/or features of the present invention will become apparent from the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

[0062] In order that the invention may be readily understood and put into practical effect, reference will now be made to preferred embodiments of the present invention with reference to the accompanying drawings and wherein like reference numbers refer to identical elements:

[0063] FIG. 1 shows a typical four level building illustrating the fire protection systems and equipment (FPSE) and associated communication system(s), apparatus and interfaces required to facilitate the embodiments of the present invention;

[0064] FIG. 1A illustrates a technician moving through three of the four levels of the building shown in FIG. 1 conducting device testing using a smoke or thermal testing equipment;

[0065] FIG. 1 B shows three of the four levels of the building shown in FIG. 1 and a fire condition that has resulted in a sprinkler head fusible element breaking, releasing water thus tripping a sprinkler system flow switch and activating a fire sprinkler pump to quench the fire;

[0066] FIG. 2 is a schematic diagram showing the configuration of elements of an embodiment of the apparatus of the present invention; [0067] FIG. 2A is a schematic diagram showing connection of the apparatus in FIG. 2 to a fire indicator panel (FIP) and an emergency warning and intercommunications system (EWIS);

[0068] FIG. 2B is a schematic diagram showing connection of the apparatus in FIG. 2 to elements of a sprinkler system;

[0069] FIGS. 3-3F show a general flow diagram in multiple parts illustrating the operation of the apparatus shown in FIG. 2;

[0070] FIG. 4 is a sequence diagram showing the steps from initial isolation of a fire indicator panel (FIP), several test modes of operation and all alarm device activation;

[0071] FIG. 5 is a sequence diagram showing the process if a real alarm occurred during the test modes; and

[0072] FIG 6 illustrates a graphical user interface of a device divided into two parts, one part showing detail from the apparatus of FIG. 2 and the other part showing processed information from a server database in communication with the apparatus;

[0073] FIGS 7 and 8 illustrate reports generated from information obtained by the apparatus from the FIP/EWIS;

[0074] FIG 9 is a general flow diagram illustrating a method of determining a likely end of life of a detector of a fire protection system according to embodiments of the present invention;

[0075] FIGS 10-15 show examples of graphical representations of processed information obtained by the apparatus from the FIP/EWIS;

[0076] FIGS 16-17 show examples of a graphical user interface of a device divided into two parts, showing detail from the apparatus of FIG. 2 and processed information from a server database in communication with the apparatus;

[0077] FIG 18 shows examples of obscuration readings available, for example, from a cloud based server;

[0078] FIG 19 shows examples of an End Of Life (EOL) process to produce an EOL report;

[0079] FIG 20 shows examples of a detector life cycle report; and [0080] FIG 21 is a sequence diagram showing a method of collecting obscuration values from a fire indicator panel (FIP) and sending the data to the cloud based server.

[0081] Skilled addressees will appreciate that the drawings may be schematic and that elements in the drawings are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the relative dimensions of some of the elements in the drawings may be distorted to help improve understanding of embodiments of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0082] Embodiments of the invention will now be described in more detail with reference to the accompanying drawings, which illustrate the system, method and apparatus in detail and advantages of the invention. The detailed description provides the necessary detail for a person skilled in the art to understand the implementation and operation of the present invention and means through which it achieves the desired outcomes.

[0083] The present invention relates to systems, methods and apparatus which reside in the fire detection and alarm systems (FDAS.) FIG. 1 is a schematic diagram which illustrates fire protection systems and equipment typically found in a building 10, which include the fire detection and alarm system components. The FDAS components comprise one or more alarm initiating devices, such as smoke detectors 71 , 75, 77, thermal detectors 76, manual call points 40 and a sprinkler alarm system 61. The sprinkler alarm system 61 comprises pipework 60, sprinkler heads/bulbs 97, an electric sprinkler pump 64 and/or a diesel sprinkler pump 65, a sprinkler system alarm control panel and pressure or flow switches etc.

[0084] As displayed in FIG. 1 , the sprinkler head/bulb 97 is one such example of a mechanical device. In the scenario in FIG.1 , the sprinkler head/bulb 97 has broken from the heat generated from the fire condition 99 on level 3 of the building and as the water pressure in the sprinkler system drops it activates the sprinkler pressure switch, activates one of the sprinkler pumps 64, 65 and registers an alarm at the FIP 30 calling the local fire and rescue authority via the ASE. [0085] Fire Protection Systems and Equipment (FPSE) which include fire detection and alarm systems (FDAS) 135 and sprinkler alarm systems 61 , are located either inside or outside a building or facility 10, which may include, but is not limited to commercial, retail, government, educational or industrial facilities. The FIP 30 is generally located either inside or outside the main foyer of a building for easy access by the fire and rescue authorities (emergency services). The designated entry point is typically defined by a strobe light and/or bell located adjacent the FIP 30 location.

[0086] The alarm initiating devices, such a manual call points (MCPs) 40, smoke detectors 71 , thermal detectors 76 (either conventional or analogue addressable devices), sprinkler alarm systems 61 (either flow or pressure activated) including sprinkler heads/bulbs 97, are connected to the FDAS 135 via a network 200 which is configured in either a single loop or multiple loops connected together. Network 200 is either hard wired or in some cases devices are connected using a Wi-Fi connection. Other interfaces may include fire sprinkler or hydrant pumps.

[0087] FIG. 1 illustrates apparatus 120 according to an embodiment of the present invention residing in or in communication with fire protection system and equipment 135. The apparatus 120 accesses obscuration data, times and events data when connected to the FIP 30. In some embodiments, the data is accessed via a serial port of the FIP 30 which is either directly connected to the RS 232/RS485 Ethernet or similar data source.

[0088] FIG. 2 is a schematic diagram showing the configuration of the apparatus 120. The apparatus 120 comprises a processor 221 , such as a single board computer 221 complete with communication interfaces in the form of Wi-Fi 222, Bluetooth 223, Ethernet port 224, Universal Serial Bus (USB) A 225, USB B 226, USB C 227 and USB D 228.

[0089] As shown in FIG. 2 apparatus 120 is powered by the FIP 30 or battery backed power source 231 . The electrical components of the apparatus 120 are protected by a fuse 232 and a bridge rectifier 233. The bridge rectifier 233 allows the apparatus 120 to operate with reverse polarity and protects the apparatus. The voltage regulator 234 provides 5 VDC to power the single board computer 221 and any additional boards required, such as the single board micro controller 229. An additional regulator 235 can be installed if other voltages are required, for example, running the 9 VDC RS232 8 wire optical isolator 217 if OEM FIP 30 or other device requires additional communication lines.

[0090] As shown in FIG. 2A the 5 VDC voltage regulator 234 and 9 VDC voltage regulator 235 are kept cool by the cooling fan 236, which also cools the single board computer 221 and any additional boards required, such as the single board micro controller 229. Power to the cooling fan 236 comes straight from the bridge rectifier 233.

[0091] As shown in FIG. 2 the single board computer 221 of the apparatus 120 is connected to USB A 225 and communicates through a 3G/4G Wi-Fi modem 210 or equivalent device. The 3G/4G Wi-Fi modem 210 contains its own backup battery charged by the connection to USB A 225. The 3G/4G Wi-Fi modem 210 can have a network static internet protocol (IP), but it can also operate with a dynamic IP address subscriber identity module (SIM) 21 1 installed allowing data transfer to a cloud based server 140. The 3G/4G Wi-Fi modem 210 creates its own Wi-Fi hotspot 207, a physical location where additional apparatus 120 may obtain internet access, to allow other apparatus 120 with the correct authority to communicate to the cloud based server 140.

[0092] As shown in FIGS.1 , 1 a and 1 b, the apparatus 120 is connected to a communications port 122 of the FIP 30. Apparatus 120 on level 2 of the building 10 creates its own Wi-Fi hotspot 207 which can allow an additional apparatus 218 installed to an electric pump 64 on level 1 of the building 10 below to obtain internet access from its on board Wi-Fi 208. An additional apparatus 219 installed to a diesel pump 65 on level 1 can obtain internet access from its on board Wi-Fi 209 by connecting to Wi-Fi hotspot 207 on level 2. This allows apparatus 120, 218, 219 according to the present invention installed in areas without reliable 3G/4G access to still obtain internet access. It also reduces initial implementation cost by reducing the number of modems required and internet access fees.

[0093] As shown in FIG. 1 , if Wi-Fi hotspot 207 and 3G/4G signal 130 is unavailable due to poor signal strength, the apparatus 218 and 219 can be connected via a local area network (LAN) 100.

[0094] As shown in FIG. 2B, where there are multiple apparatus, e.g. apparatus 218 and apparatus 219 require internet access to join the Wi-Fi hotspot 207 using the existing 3G/4G Wi-Fi modem 210. To connect to the Wi-Fi hotspot 207 of the 3G/4G network, the Wi-Fi modem 210 would need to be within range and have authorization. These communicate directly with the existing 3G/4G Wi-Fi modem 210 using the Single Board Computer 221 via the on-board Wi-Fi connection 209 on apparatus 219 and Single Board Computer Wi-Fi connection 208 on apparatus 218.

[0095] As shown in FIG. 2 the apparatus 120 has a USB to RS232 converter 212 connected to USB B 226. To communicate with the FIP 30 through converter 212, USB B 226 is referred to in the software as communication through apparatus 120 Port 1. Apparatus 120 also comprises a USB to RS232 converter 213 connected to USB C 227 and a USB to RS232 converter 214 connected to USB D 228. Communication to and from the FIP 30 through the USB to RS232 converter 213 is referred to in the software as communication through apparatus 120 Port 2. Communication to and from the FIP 30 through USB to RS232 converter 214 is referred to in the software as communication with the unique identifier apparatus 120 Port 3.

[0096] As shown in FIG. 2, the apparatus 120 communicates via USB B 226 to USB to RS232 converter 212 to FIPs 30 through an optical RS232 isolator/coupler 215. The optical RS232 isolator 215 protects the FIP 30 by electrically isolating the data communications. The optical RS232 isolator 215 is typically a 3-wire protection device covering the elements TX, RX and GND. Optical RS232 isolator 215 effectively protects against high-voltage spikes, surges, ground loops and other damaging voltages.

[0097] The data source the apparatus 120 collects is gathered from OEM available printer port/s. In some cases additional standard OEM hardware is required to provide printer port/s. It is important to note that a design feature of the apparatus 120 is that it does not impede the normal operation of the FDAS.

[0098] As shown in FIG. 2 the apparatus 120 communicates via USB D 228 to USB to serial converter 214 to FIPs 30 through an optical RS232 isolator/coupler 8 wire device 217. The optical RS232 isolator 217 protects the FIP 30 by electrically isolating the data communications. The optical RS232 isolators 215 and 216 are typically a 3-wire protection devices covering the elements TX, RX and GND. The Optical RS232 isolator 217 is an 8-wire protection device covering the elements DCD, TXD, RXD, DTR, RTS, CTS. GND may also be required, but this is dependent on specific OEM communications requirements. The 3-wire and 8-wire optical RS232 isolators 215, 216, and 217 can operate on either of these ports USB B 226, USB C 227 and USB D 228.

[0099] The powering up of the apparatus 120 and its operating program are shown in the general flow diagrams in FIGS. 3-3F. FIG 3 is an overview of the interrelationship of FIGS 3A-3F. References to DCT in FIGS 3A-3F are references to the apparatus 120.

[0100] Turning to FIG. 3A, the technician arrives on site, connects the apparatus 120 to the power and communication connections of the FIP 30. A modem of the apparatus 120 is activated if not automatically activated and allowed to boot up. The apparatus 120 connects to an online portal via communications network 200. The relevant FIP 30 is then selected from a management menu by the technician. Under a tools menu, the particular type of apparatus 120 connected to the FIP 30 is selected. An SMT option is selected from the tools menu to check the external IP address, which is then stored as a session variable. Streaming is then activated.

[0101] Turning to FIG 3B, activating streaming writes an integer to a text file stored in the apparatus 120. The cloud based server 140 periodically, e.g. every minute, checks if the apparatus 120 is assigned to a FIP 30 and whether the apparatus has been active in a preceding period, e.g. in the last 15 minutes, if the apparatus 120 has been deployed and marked as automation ready. If these criteria are satisfied, the server 140 logs into the apparatus 120 via a secure, encrypted connection protocol, such as secure shell (SSH) and runs a streaming script stored on the server 140 directly to the apparatus 120. Preferably, this is achieved via a shell_exec command that has a tail of 10 seconds sleep after which it has a kill command targeted at the most recently started process on the server 140. The apparatus 120 imports modules required for, for example, communication with the FIP 30 and time based commands. A numeric value of the text file stored on the apparatus is then checked. For example, a value of 0 terminates the script. A value of 4 indicates the script was terminated improperly. The value is then set to 0 for a period of time and reset to 3, which is recognised as indicating that the apparatus 120 is ready to run.

The numeric value is then updated to 4 (running). A time on the apparatus 120 is updated using a network time protocol (NTP) server and initialises the websockets. [0102] Turning to FIG 3C, the script collects the arguments passed by the server 140, such as database connection information, an identifier for the apparatus 120 connected to the FIP 30, the commands to run and the frequency. Recurring commands for 3 hash characters are checked as these are used to separate multiple commands in a single string. For example, some FIPs, the apparatus needs to log in before issuing a command. Multiple commands are stored as separate commands and a variable is set to indicate that multiple commands per cycle must be executed. The apparatus 120 then connects to the database of the server 140 and the database records information via the apparatus 120 such as the type of FIP 30, serial port settings of the FIP 30, the number of communication ports on the FIP and the like. If a second communication port is present, it is initialised and the buffers are flushed. The database of the server 140 connects to the primary communication port of the FIP 30 and flushes the buffers. UTC and AEST are stored for use in tracking updates and displaying current time. The current local time is written to the text file smt.txt for the streaming view and to smt_long.txt for the full script history file. If the primary communication port of the FIP 30 is open, the apparatus 120 updates the database of the server 140 with the current time in the last_connected field for tracking which apparatus 120 are active. The apparatus 120 then starts a loop dependent on the primary communication port of the FIP 30 being active.

[0103] Turning to FIG 3D, the current time is collected and if a predetermined time has elapsed, such as 10 minutes, since he apparatus 120 notified an active status to the server 140, the server is updated again. The one or more serial ports of the FIP 30 are read by the apparatus 120 for new data. If there is no new data, see 308 of FIG 3E described below. If there is new data, a data segment count is incremented. The type of FIP is checked and patterns are used for matches depending on the type of FIP and/or other fire protection equipment, such as pumps, EWIS, sprinklers etc. if the data is non-ASCII, the apparatus 120 advises the websockets of this and pattern matching is skipped. Each line of data is pattern matched for walk test, test completions and obscuration data etc. If the data matches a pattern, the data is written to the database of the cloud server 140 as per criteria set for the particular FIP type. The data is sent to the websockets with a new line character replaced with html </br>. If the data does not match a pattern, the data is sent to the websockets with a new line character replaced with html </br>. [0104] Turning to FIG 3E, at 308 if the data segment count is over 50 and there have been at least predetermined number of cycles, e.g. 10 cycles of no data from the communication ports of the FIP 30, the contents of the smt_long.txt file are uploaded by the apparatus 120 to the database of the server 140. The file is emptied and the current date and time are written to the top of the file. The text file is then checked for any new commands. This is also the next step at 309. If a predetermined time has been exceeded since the apparatus 120 last rain its recurring commends, these are loaded into memory for writing to the communications port of the FIP 30. If there are one or more commands in the queue, a portion of the commands are checked, such as the first six characters of the commands. The outcome of this check is discussed with reference to FIG 3F.

[0105] Turning to FIG 3F, at 31 1 , if the first characters equal port2 or port3, the apparatus 120 sends the command to communications port 2 or port 3 respectively. There is a delay, e.g. of 1 second between multiple commands. At 312, if the first characters do not equal port2 or port3, the apparatus 120 sends the command to communications port 1. There is a delay, e.g. of 1 second between multiple commands. At 313, if there is no command, the custom command file is truncated, which is also the subsequent step after the command is sent to one of the communication ports. The value of the text file is then checked. A value of 4 causes the apparatus to continue the process at 315 in FIG 3C. If the value does not equal 4, the full script history in the smt_long.txt file is uploaded to the database of the cloud server 140, the serial ports are closed and the process is terminated.

[0106] To facilitate routine testing of the fire detection and alarm system 135, as shown in Fig. 1A the system 135 must first be placed in test mode by the technician 150. Once the fire detection and alarm system 135 is isolated, the ASE 121 is also placed in test mode to prevent an unwanted attendance by the fire and rescue authority (monitoring centre) 105.

[0107] The apparatus is designed to work on multiple OEM FIP's 30 and each FIP 30 has its own single person test function built in.

[0108] As shown in FIG. 1A, after the system is isolated and placed in test mode routine testing can commence. The technician 150 logs on to the cloud based server 140 using his user name and password via their Personal Digital Assistant (PDA) 1 10, mobile telephone (smartphone), tablet or similar mobile device.

[0109] The PDA 1 10 has many functions which include identifying all detectors and devices within the FDAS 135, classifying all detectors and devices as red until the detectors and devices are tested, recording the number of devices in the FDAS 135 and the relevant percentages (scores) of the detectors and devices based on the type and denomination of the detector and device.

[0110] As shown in FIG. 1A the technician 150 selects the type of test to be performed via a drop down menu displayed on the PDA 1 10. For example, an annual test will be performed on the smoke detectors 71 , connected to the FIP 30, referencing the relevant Australia Standard

[0111] The technician 150 must test each detector and device in the nominated percentages (refer Australian Standards as above) employing the traditional testing method and using the appropriate test medium for smoke, heat or carbon monoxide. All other fire detection and alarm system activation devices are tested using the nominated reference medium to determine, for example, whether the detector or device is operational within tolerances or whether the detector or device requires replacement.

[0112] To illustrate the testing process, a detector or device is selected in any sequence. In this example, smoke detector 71 is selected and is activated by the technician 150 applying the test medium controlled to produce the predicted smoke concentration level to activate the smoke detector 71 . This is achieved by placing the test equipment 160 over the smoke detector 71 with a barrier (hood) to provide a controlled environment and which prevents smoke escaping from the chamber prematurely. The test medium in this instance is artificial smoke. A detailed account of the annual testing process can be found in the sequence diagram shown in FIG. 4.

[0113] Once the smoke detector 71 is activated an alarm signal is sent to the FIP 30 via the network 200. The streamed data "detector 71 " is sent to the apparatus 120. The apparatus 120 then sends streamed data to PDA 1 10. Apparatus 120 sends processed data to cloud based server 140, as described herein with reference to FIGS 3 to 3F. The FIP 30 turns on the smoke detector 71 communicating via network 200. Technician 150 visually observes illumination from LED 81 on smoke detector 71 . The technician 150 completes the test, removing the testing apparatus/hood and moves to the next device, e.g. smoke detector 72.

[0114] Cloud based server 140 marks smoke detector 71 as tested, e.g. by an indicium, such as colour coding, such as green, once the valid test is received, and adds to the detector count completed by one. Once the alarm signal is received it creates an event in the database which contains the date and time of the alarm. The system calculates the percentage complete by detector type, e.g. the Australian Standards require 50% of all smoke detectors to be tested once per annum. If one is tested from a total of 10 it would now show a 10% completion rate. Technician 150 validates all relevant location information and device description e.g. Level 4, Room 401 .

[0115] As the FIP 30 is in its specific OEM single man test, the FIP 30 sends a reset signal to smoke detector 71 via the network 200. The FIP 30 receives a smoke detector 71 "normal" status signal or similar. FIP 30 turns off the LED 81 of the smoke detector 71 .

[0116] Technician 150 moves to the next smoke detector 72 and performs the required test, as above.

[0117] The technician 150 places test smoke in the smoke detector 72 as described above. Once the smoke detector 72 is activated an alarm signal is sent to the FIP 30 via the network 200. The streamed data "detector 72" sent to apparatus 120. The apparatus 120 sends streamed data to PDA 1 10. The apparatus 120 also sends processed data to cloud based server 140. The FIP 30 then turns on LED 82 of smoke detector 72 communicating via network 200. Technician 150 visually observes LED illumination 82 on smoke detector 72. Technician 150 completes the test by removing the testing apparatus/hood.

[0118] Cloud based server 140 marks device 72 as green once the valid test is received, and adds to the detector count completed by one. Once the alarm signal is received it creates an event in the database which contains the date and time of the alarm. The system calculates the percentage complete by detector type. Technician 150 validates all relevant location information and device description e.g. Level 4, Room 402. [0119] As the FIP 30 is in its specific OEM single person test it sends a reset signal to smoke detector 72 via the network 200. The FIP 30 receives smoke detector 72 "normal" status signal. FIP 30 turns off the device LED 82.

[0120] Technician 150 moves to the next detector.

[0121] The technician 150 places test smoke in the smoke detector 73. This is achieved by placing the test equipment 160, with a barrier (hood), over the smoke detector 73 to provide a controlled environment. Once the smoke detector 73 is activated an alarm signal is sent to the FIP 30 via the network 200.

[0122] As an example, smoke detector 71 can reactivate due to smoke not properly clearing from the chamber. Once the smoke detector 71 is activated an alarm signal is sent to the FIP 30 via the network 200. The streamed data "smoke detectors 73 and 71" is sent to the apparatus 120. The apparatus 120 sends streamed data to PDA 1 10. The technician 150 can see streamed data on the PDA 1 10 identifying smoke detectors 73 and 71 . Apparatus 120 sends processed data to cloud based server 140. FIP 30 turns on smoke detector 73 LED 83 communicating via network 200. FIP 30 turns on smoke detector 71 LED 81 communicating via network 200. Technician 150 visually observes LED illumination 83 on device 73. Technician 150 completes the test by removing the testing apparatus/hood. The sequence diagram of FIG 5 shows the sequence of events for any alarm activation from a device, such as a smoke detector during testing of another device.

[0123] Cloud based server 140 registers the device 73 as green once valid test is received, and adds to the detector count completed by one. Cloud based server 140 has already marked device 71 as green. It will not adjust the count nor will it move 71 to the top of the PDA screen. The top of the screen is reserved for a detector that has not been tested, and once tested and validated cannot return to the top of the screen. If this detector re-alarms within a predetermined number of minutes it will not flag an anomaly to the PDA 1 10.

[0124] As the FIP 30 is in its specific OEM single person test it sends a reset signal to device 73 via the network 200. The FIP 30 receives device 73 "normal" status signal. FIP 30 turns off the device LED 71 . Technician 150 then moves to the next detector and so on.

[0125] Testing of the FIP 30 is completed when all devices have been tested. [0126] The apparatus 120 sends the OEM-specific command to the FIP 30 to trigger an obscuration report for all connected smoke detectors currently programmed to download the detail every 30 minutes. This report is processed by the apparatus 120 and sent to the cloud based server 140 and stored within a database location specific to the customer.

[0127] With reference to FIG 6, in some embodiments, a display of the PDA 1 10, mobile telephone (smartphone), tablet or similar mobile device, laptop or desktop computer is divided into at least two parts. One part of the display shows information from the apparatus 120 and another part of the display simultaneously shows processed information from the cloud based server database in communication with the apparatus. In the embodiment shown in FIG 6, the display is divided vertically into two halves. Alternatively, the display can be divided horizontally into two halves. In other embodiments, the display can be divided into more than two parts. In the embodiment shown in FIG 6, the left-hand side of the display shows processed information from the cloud based server database including details of detectors, their location and whether or not they have been tested in the current test. For example, M1 -43 LVL 5 BED 502 THERMAL identifies a thermal detector on level 5 of a building, such as a hotel, in bedroom 502. The text can be colour coded to clearly indicate whether a detector has been tested or is yet to be tested. For example, green can be used to show that a detector has been tested and red can be used to show that a detector is yet to be tested. Other colours and/or text effects can be used. In the embodiment shown in FIG 6, the left-hand side of the display can show other information, such as a total number of detectors to be tested, a number of detectors tested, a percentage of the detectors represented by specific types of detectors, a current duration of the test and an estimated time of completion of the test. In the embodiment shown in FIG 6, the right-hand side of the display shows a stream of information from the apparatus 120 in real time with a time stamp for each piece of information. The display can also display an icon, such as a bar graph indicating that the apparatus 120 is operational and a menu comprising selectable command options. The display also comprises a field to allow the technician to enter notes, such as notes relating to the tests. Further examples of a graphical user interface presented on a display of the PDA 1 10, mobile telephone (smartphone), tablet or similar mobile device, laptop or desktop computer divided into at least two parts is shown in FIGS 16 and 17.

[0128] FIGS 7 and 8 illustrate reports generated from information obtained by the apparatus 120 from the FIP/EWIS. FIG 7 shows an example of the estimated end of life of detectors as calculated from the information recorded by the apparatus 120. The report identifies each detector with an identifier, location and position information within the building in which each detector is located. A value for the detector is determined, for example, 92.000, 83.000 etc., based on the information recorded by the apparatus 120. If the value exceeds a pre-set threshold or a programmed value set by the OEM, the detector should be replaced. In this regard, FIG 8 shows a report for a different building listing the detectors in that building that need to be replaced based on the information recorded by the apparatus 120. In this example, all of the detectors are connected to the same FIP, 10001 , and each detector is individually identified, e.g. M3-1 1 , with an associated location of the detector, e.g. level 2, hallway, adjacent bedroom 212. A value for each detector is provided and in this example, each value exceeds the pre-set threshold or programmed value for that particular detector such that the 27 listed detectors need replacing.

[0129] According to another form, and with reference to the general flow diagram in FIG 9, the present invention resides in a method of determining a likely end of life of a detector, such as, but not limited to smoke detectors 71 , 75, 77 and thermal detectors 76, of a fire protection system 135 as described herein using the aforementioned apparatus 120. The method 600 comprises at step 602 acquiring a plurality of measurements of an obscuration value of the detector via the apparatus 120. The method 600 includes at step 604 calculating a rate of contamination of the detector based on the plurality of measurements of obscuration value. The method 600 includes at step 606 determining a likely end of life of the detector based on the calculated rate of contamination of the detector and a nominal end of life value for the detector set by a manufacturer of the detector. The method can be performed for every detector in the building 10. The plurality of measurements is acquired periodically, such as, but not limited to every 30 minutes. Other time intervals can be used depending on factors such as, but not limited to the type of detector, the location of the detector, a level of pollution or contamination in the location. [0130] FIGS 10-15 show examples of graphical representations of processed information obtained by the apparatus from a FIP/EWIS. FIG 10 shows values for specific detectors over a selected value, in this case 95, for two specific dates. FIG 1 1 shows peak values for a specific detector over a range of dates. FIG 12 shows total detector values for particular locations for three consecutive dates. FIG 13 shows peak data and average data for detectors for a specific date. FIG 14 shows another example of total detector values for particular locations for three consecutive dates. FIG 15 shows another example of values for specific detectors over a selected value, in this case 95, for two specific dates.

[0131] Figure 18 shows sample obscuration readings from a fire panel. The data is collected and examined from the date of installation of a new detector Start Of Life (SOL) to the current date for each detector. The target data is an expected End Of Life (EOL). The average change per day in the obscuration value is calculated and any changes of the detector are taken into account. Then the detector data timeframe is split based on points where it has significantly changed, and these timeframe/change values are used to construct a model for the predicted EOL.

[0132] The main change formula is taken from all detectors of the same model in communication with this brand of fire panel and modifiers are used from the individual detector data to tailor the prediction of the EOL for the individual detector.

[0133] Figure 19 illustrates an example. If an obscuration value of all detectors in communication with this panel incremented by 1 every year on average, this would be the base annual obscuration increment value for this formula. Based on an approximate obscuration start value of 65 and an EOL obscuration value of 95, Figure 19 shows the average for smoke detectors is an increment of 1 per year. The average for the individual M1 -1 detector is 2 per year. Using a basic version of the EOL algorithm, these ratios are averaged out and it is determined that M1 -1 is likely to increment by 1 .5 per year. Based on this, an EOL estimate of 2 years would be determined for detector M1 -1.

[0134] When more data for the detectors is available, it is sometimes found that as the detectors get dirtier they have a compounding effect on the obscuration values. For instance, in one example, it is assumed that the obscuration value for the detectors on average increment by 0.5 per year from an installation (Start of Life (SOL)) value of 65 to 75 and then by 1 each year from 76 to 85 and then by 1 .5 per year from 86 to 95. This would give the following estimate for detector M1 -2: The average per year for all detectors is 1 per year. The average increment for a detector in this range and for this type of detector is 1.5 per year. Compounding these observations, an averaged expected increment per year of 1 .17 is determined. This provides an estimated EOL of 3 years and 5 months.

[0135] Embodiments of the invention can include detecting when a smoke detector has been changed and generating a Life Cycle Report. With reference to Figure 20, embodiments of the invention automatically detect any detectors that have been changed to validate/record they have been changed and start a new EOL report function. In Figure 1 , the apparatus 120 requests instantaneous obscuration readings from the FIP 30 which in turn gathers readings from the detectors/devices 75, 76, 77. To illustrate the collection of the obscuration readings, the apparatus 120 requests from the cloud based server 140 the scheduled command, which may be OEM dependent, to request the obscuration data from the FIP 30. The FIP 30 reads the data from the devices 75, 76, 77 and then reports the data to the apparatus 120. The apparatus 120 sends the data and inserts the data individually in the cloud based server 140. The cloud based server 140 schedules many requests throughout the day to obtain a plurality of readings to make the data more accurate. The cloud base server 140 provides off site data collection and backup of all the data sent to it. A detailed account of the obscuration collection can be found in the sequence diagram shown in FIG. 21 .

[0136] The cloud based server 140 creates its own average readings for the detectors. Many different average readings are calculated in the cloud based server 140 to allow quicker analysis and programming of the readings. This also reduces the load on the cloud-based servers/computers and enables a quicker response to be provided during data queries, graphing and reporting.

[0137] An average value is used to determine if a detector has been changed automatically. The system then archives the old readings within the cloud-based server 140 for the detector that has been changed.

[0138] The cloud based server 140 automatically determines the position of the data by the unique identifier that is tied to the location of the detector. All detectors are required to have an accurate description to allow the location of the smoke/heat/fire detected by the detector to be found quickly and accurately from the display from the FIP 30 shown in Figure 1. The detectors 77 in Figure 1 are addressable and have a unique identifier, for example M2-37.

[0139] Using the daily average readings, the present invention determines when a detector is replaced/changed. The fact the detector is not present for a small period of time during the detector change process does not change the detector average reading. Too low an obscuration data reading, such as a zero, is ignored by the cloud based server 140 for the daily average reading to count towards the detector change report.

[0140] Once an existing detector is replaced with a new detector, the average obscuration value will drop over a subsequent period, such as the next two days. This drop is recorded in the cloud based server 140 and it creates a table/report shown on Figure 20. The system thus records that a new detector has been installed and uses the previously collected data from the detector position to estimate the new EOL value. Hence, embodiments of the methods of the present invention can comprise automatically detecting when a detector of the fire protection system has been changed by comparing a historic average daily obscuration value of a detector in a location with a current average daily obscuration value of a detector in the same location and determining a reduction in the average daily obscuration value of the detector in the same location.

[0141] Embodiments of the system can predict the Start of Life (SOL) of the detector within the existing building. Drawing from the method designed and learning to predict the End of Life (EOL) of a smoke detector due to contamination due to the environment of the detector, the method can be tested using similar processes to predict the Start Of Life (SOL) date. By using the method, both EOL and SOL, it allows more data to be tested based on the prediction. SOL can be known from a new building opening date and commissioning data. Log book entries can show detector replacements and dates. All this extra data can be used to increase the accuracy of the EOL and in turn the SOL based on manual data input into the cloud based server 140. Hence, embodiments of the methods of the present invention can comprise determining the likely end of life of the changed detector by recording the start of life (SOL) of the changed detector, filtering the reduced average daily obscuration values recorded for the changed detector and calculating the rate of contamination of the changed detector based on the historic average daily obscuration values recorded for the detector in the same location.

[0142] If an area of a building is undergoing building works, the detectors in the area can be marked in the system as detectors that may be contaminated due to the building works. The detectors in the area of works should be protected from contamination by installing covers over the detectors during the works. The detectors will need to have the covers removed when works are not being carried out as the risk of an undetected fire is higher because once building works commence the public will not normally be allowed in the works area. The builder could then be liable for reducing the detector contamination average in line with the previous EOL expectation. Hence, embodiments of the methods of the present invention can comprise identifying a detector in a location in which building works or the like are taking place, comparing a rate of contamination of the detector during the building works or the like based on measured daily obscuration values with historic average daily obscuration values recorded for the detector in the same location and determining if the rate of contamination of the detector has been artificially reduced.

[0143] Since the apparatus 120 can communicate with many, if not all brands of addressable fire detection systems, many different detectors in the real world environment can be compared and the performance of detectors across brands and models can be compared. Chamber designs that are more efficient so as not to collect dust quicker than their competitor will be identified. Hence, embodiments of the methods of the present invention can comprise comparing the rate of contamination of multiple detectors based on recorded obscuration values to determine a relative efficiency value of each detector.

[0144] Embodiments of the present invention assist in reducing environmental and financial waste and planning for last order date when models are phased out.

Manufacturers often bring out new models of detectors that are not compatible with the old model of detectors running on the same data pair. This can be due to better protocols of communication being used at faster speeds or more data points being available on one detector loop. The apparatus 120 can identify the detectors that still have life remaining, so the detectors can be gradually changed a loop at a time rather than disposal of many detectors that are incompatible. For example, the detectors on loop 2 / level 2 of a building could be changed and the detectors with life remaining held as spares. By using the data clearer decisions can be made on the best time to upgrade and the likely requirements into the future for detector numbers. The client could buy sufficient detectors during the manufacturers model end of life announcements and before the last order date of the model being phased out. Hence, embodiments of the methods of the present invention can comprise determining a quantity of a model of detector to be reordered based on the likely end of life calculated for each detector in a loop of detectors of the same model and the recorded last order date for ordering a replacement detector where the model of detector is being phased out.

[0145] Furthermore, detectors can be refurbished, cleaned and tested with confidence before the detectors are placed back in service.

[0146] Embodiments of the present invention can identify all "bad weeks", "repeat offenders", "spikes" and "mini spikes". "Repeat Offenders" is a query based on daily summary data to identify detectors for which the obscuration value has incremented, for example, over 4 times, for example, two or more weeks of the year. "Spikes" is a query based on daily summary data to identify detectors where, for example, within a week of the year, the detector's obscuration value has incremented, for example, at least 10% more than once. "Problem Weeks" is a query based on daily summary data to show detectors where, for example, within a week of the year, the detector's obscuration value has incremented, for example, over 4 times. "Mini Spikes" is a query based on granular 'fip_data' to identify detectors by week, or other period, where the detectors experienced a jump of, for example, 50% in their obscuration value day to day. It will be appreciated that time periods and/or thresholds different from the above examples can be used. Hence, embodiments of the method can comprise determining one or more of the following based on the plurality of measurements of the obscuration value of the detectors in the fire protection system: the detectors for which the obscuration value has incremented over a predetermined number of times over a predetermined period; the detectors for which the obscuration value has incremented over a predetermined threshold more than once within a predetermined period; the periods during which the obscuration value for one or more detectors has incremented over a predetermined number of times; the detectors for which the obscuration value has incremented over a predetermined threshold in consecutive predetermined periods.

[0147] The apparatus 120 allows a standard addressable fire panel from many manufactures to be able to predict the time required to carry out an annual test of the fire panel based upon the speed of the individual carrying out the tests.

[0148] The apparatus 120 allows a standard addressable fire panel from many manufactures to be able to have the data of the detectors tested to be validated that the works have been carried out with the required 20% of thermal detectors per year, such that over 5 years all detectors have been tested. As other examples, the apparatus 120 can also validate 50% of thermal detectors each year and 100% of manual call points each year.

[0149] Embodiments of the present invention can identify areas within a building that have a dirtier atmosphere than other areas that contaminate the detectors quicker. Hence, embodiments of the present invention reside in a system to determine a likely end of life of the detectors of the fire protection system. The system comprises the apparatus 120, which comprises the processor 221 in communication with a memory 205, 206 and at least one port; at least one converter coupled to the port to enable communication between the apparatus 120 and a fire indicator panel (FIP) 30 of the fire protection system 135; and at least one communications interface 222 - 228 in communication with the processor to enable communication with the remote computing device 140 and the mobile computing device 1 10. The apparatus is configured to acquire the plurality of measurements of the obscuration value of the detectors from the FIP 30. The remote computing device 140 is configured to calculate a rate of contamination of the detectors based on the plurality of measurements of obscuration values and determine a likely end of life of the detectors based on the calculated rate of contamination of the detectors and a nominal end of life value for the detectors set by a manufacturer of the detectors.

[0150] Hence, embodiments of the present invention address or at least ameliorate the aforementioned problems of the prior art by providing an apparatus, and a system comprising the apparatus, and a method that enables remote access to data relating to fire protection systems and equipment via a secure communications link via a FIP. The apparatus, system and related method enable the data to be continuously accessed, stored, validated and analysed, which allows a range of new outcomes to be achieved. These outcomes include the ability to perform single person fire systems testing confidently, verification in real time of the status of all devices and detectors tested, notification of impending smoke detector alarms due to contamination levels approaching or exceeding pre-set values. Tests show whether devices pass/fail and test data can be retrieved from previous periods, such as the previous year, to ensure 100% of devices are tested within the specified timeline. Tests provide all relevant data displayed on the screen of a mobile device, such as a mobile telephone, tablet, PDA or the like. Direct real-time access to obscuration reports is provided to authorised parties. Complete and comprehensive audit trails of all maintenance, testing or work performed on the systems many devices are provided. Hence, objective evidence of all work performed on the system is provided. Data is held securely in a database server. A customer portal allows building owners and managers and the like to access fire system PM status, failures, obscurations, fault reporting, and excessive run times on equipment, such as pumps etc.

[0151] In this specification, the terms "comprises", "comprising" or similar terms are intended to mean a non-exclusive inclusion, such that a system, a method or an apparatus that comprises a list of elements does not include those elements solely, but may well include other elements not listed.

[0152] The reference to any prior art in this specification is not, and should not be taken as, an acknowledgement or any form of suggestion that the prior art forms part of the common general knowledge.

[0153] Throughout the specification the aim has been to describe the invention without limiting the invention to any one embodiment or specific collection of features. Persons skilled in the relevant art may realize variations from the specific embodiments that will nonetheless fall within the scope of the invention which is defined by the subsequent claims.