Patent Description:
Fire alarm systems are often installed within buildings such as commercial, residential, or governmental buildings. Examples of these buildings include offices, hospitals, warehouses, schools, shopping malls, government offices, and casinos.

The fire alarm systems typically include fire control panels (or control panels) that function as system controllers. Fire detection/initiation devices and alarm notification devices are then installed throughout the buildings and connected to the panels. Some examples of fire detection/initiation devices include smoke detectors, carbon monoxide detectors, flame detectors, temperature sensors, and/or pull stations (also known as manual call points). Some examples of fire notification devices include speakers, horns, bells, chimes, light emitting diode (LED) reader boards, and/or flashing lights (e.g., strobes).

The fire detection devices monitor the buildings for indicators of fire. Upon detection of an indicator of fire such as smoke or heat or flames, the device is activated and a signal is sent from the activated device to the control panel. The control panel then initiates an alarm condition by activating audio and visible alarms of the fire notification devices of the fire alarm system. Additionally, the control panel will also send an alarm signal to a monitoring station, which will notify the local fire department or fire brigade.

The monitoring stations will typically monitor multiple fire alarm systems for alarm signals and then notify the proper authorities. Monitoring stations are often required by regulations, making them a standard component of most fire alarm systems, regardless of age or manufacturer of the fire alarm systems' components. These monitoring stations can be administered by a third party company, the same company that provides or manufactures the fire alarm systems, or a public agency, among examples.

The monitoring stations will receive other signals, beyond the alarm signals, from the fire alarm systems. Handshaking signals between the control panels and the monitoring stations are used to confirm the connection status between the fire alarm systems and the monitoring station. Typically, monitoring stations include computer and software systems for receiving, storing, analyzing and displaying connectivity status and fire alarm information based on the signals received from the fire alarm systems. A technician monitors the information and, in the event of a potential fire, informs the local fire department or fire brigade and/or initiates a specified sequence of actions in response to receiving alarm signals for a potential fire.

Typically, building codes, local laws, standards, and/or insurance providers require that the fire alarm systems are periodically tested (e.g., monthly, quarterly, or annually) to verify that the fire detection/initiation and fire notification devices are physically sound, unaltered, working properly, and located in their assigned locations. This testing of the devices is often accomplished with a walkthrough test.

Historically, walkthrough tests were performed by a team of at least two technicians, also known as inspectors. The first technician walked through the building and manually activated each fire detection/initiation such as will artificial smoke while the second technician remained at the control panel to verify that the control panel received a signal from the activated device and/or that the fire notification device properly produced its form of alert. The technicians would typically communicate via two-way radios or mobile phones to coordinate the testing of each device. In some cases, the technicians might even have resorted to comparing hand written notes of the tested devices. After a group of fire detection and fire annunciation devices was tested, the technician at the panel reset the control panel while the other technician moved to the next group of fire detection or fire annunciation devices.

More recently, it has been proposed to use connected services systems to monitor control panels during walkthrough tests, for example. In some cases, the control panels have been given network connectivity to communicate with the connected services systems; in other cases, the technicians have temporarily connected testing computers to the control panels that functioned as gateways. This has allowed the control panels to report status information to the connected services systems, which are typically administered by fire alarm system companies and include, for example, databases for storing historical status information. These connected services systems will also often have remote diagnostic capabilities. As such, connected services systems facilitate the maintenance, compliance and tracking of repairs of fire alarm systems. control panels manufactured by third parties. Legacy control panels often lack the network connectivity necessary to connect to a connected services system. Similarly, third party control panels lack network connectivity and/or use different protocols than the connected services system to communicate status information. As a result, connected services systems are unable to incorporate non-compatible control panels.

Systems have been proposed to provide network connectivity to non-compatible control panels, including retrofitting non-compatible control panels with gateway devices. However, access to legacy control panels to complete the installation is often difficult to achieve, and third party control panels are often incompatible with even the gateway devices. Additionally, because connected services systems are not required by regulations, the expense of retrofitting control panels of a fire alarm system is difficult to justify.

The monitoring stations, on the other hand, are often required by regulations. As a result, they are considered a standard component of fire alarm systems.

<CIT> discloses a wireless communication system for use in a building.

According to aspects of the invention, this near-universal connection between non-compatible control panels and monitoring stations are used to transmit status information for non-compatible control panels to connected services systems. In this way, connected services systems can incorporate monitoring and tracking of non-compatible control panels as well as compatible control panels.

In general, according to one aspect, the invention features a method for monitoring fire alarm systems as set out in claim <NUM>.

The non-compatible control panels may include third party and legacy control panels. The non-compatible control panels send the fire alarm signals to the monitoring station possibly via several transmission media, including wide area networks, telephone systems, wireless radio networks, cellular networks, voice over internet protocol systems.

The monitoring station sends the status information for the non-compatible control panels to the connected services system via a wide area network, typically, and the status information is mapped to the connected services database via a mapping system, which can be a physically separate server or a process integrated with the standard system.

The status information can include identification, location, status history and alarm history.

Furthermore, in one embodiment not covered by the claims, status, diagnostic and testing information can be detected by the connected services system from scanning printed reports, translated into compatible information by the mapping service and stored in the connected services database.

Further, the connected services server can retrieve histories of status, diagnostic and testing information and then send them to mobile computing devices. In this way, a technician using a mobile computing device activates fire detection and annunciation devices of a fire alarm system during a walkthrough test and view the status of the activated devices on the mobile computing device. The technician can then add annotations to the histories, and the mobile computing device sends annotated histories to the connected services server to be stored in the connected services database.

In general, according to another aspect, the invention features a connected services system for monitoring fire alarm systems as set out in claim <NUM>.

The above and other features of the invention including various novel details of construction and combinations of parts, and other advantages, will now be more particularly described with reference to the accompanying drawings and pointed out in the claims. It will be understood that the particular method and device embodying the invention are shown by way of illustration and not as a limitation of the invention. The principles and features of this invention may be employed in various and numerous embodiments without departing from the scope of the invention.

<FIG> is a block diagram of a connected services system <NUM> according to the present invention.

In general, the connected services system <NUM> facilitates the monitoring, maintenance, testing, configuration and repair of fire alarm systems by gathering and storing information from connected fire alarm systems.

The connected services system <NUM> includes a connected services server <NUM> and a connected services database <NUM>. The connected services server <NUM> receives information from various connected fire alarm systems typically via a public network <NUM>, which is a wide area network such as the internet, and stores the information in the connected services database <NUM>.

The connected services system <NUM> gathers data from fire alarm systems by receiving information reported and transmitted from the fire alarm systems' control panels <NUM>, <NUM>. Control panels <NUM>, <NUM> are devices that direct the function of fire alarm systems by determining and displaying the operational status of connected fire detection and notification devices and by receiving alarm signals from fire detection devices, among other examples.

Each of the control panels <NUM>, <NUM> will each support one or multiple loops or networks of fire detection and alarm notification devices. For clarity only a network of fire detection and alarm notification devices is shown, connected to the legacy control panel <NUM>-L-<NUM>. Common examples of the fire detection devices <NUM>-<NUM>, <NUM>-<NUM> typically include smoke detectors <NUM>-<NUM>, carbon monoxide detectors, temperature sensors, and/or manual pull stations <NUM>-<NUM>, to list a few examples. Similarly, examples of the fire alarm notification devices <NUM>-<NUM> generally include speakers/horns <NUM>-<NUM>, bells/chimes, light emitting diode (LED) reader boards and/or flashing lights (e.g., strobes). In general, the fire detection and fire annunciation devices <NUM>-<NUM> to <NUM>-<NUM> connect to the control panels <NUM>, <NUM> via a safety and security wired and/or wireless network <NUM> (also known as a loop) , which supports data communication between the devices <NUM>-<NUM> to <NUM>-<NUM> and the control panels <NUM>, <NUM>.

The illustrated example includes compatible control panels <NUM>, which transmit data to the connected services server <NUM> via the public network <NUM>, usually through enterprise and/or cellular data networks. Data transmitted from compatible control panels <NUM> to the connected services server <NUM> include status information, diagnostic information and testing information pertaining to the control panel and other components of the fire alarm system such as fire detection and notification devices. Status information is information about whether the fire alarm system is operational and whether an alarm state is indicated. Generally, diagnostic information is data detected by various components of the fire alarm system that can be used to optimize or repair the system, and testing information is information about any tests of the fire alarm system. In some examples, diagnostic information includes identification information such as a unique identifier for the fire alarm control panel <NUM>, address of the device or devices, location information such as a physical location of the devices (<NUM>-<NUM>, <NUM>-<NUM>. <NUM>-n), a date and time of the activation, status information, including a fault state of the activated devices, analog and/or detected value generated by the devices such as a detected smoke level or detected ambient temperature.

Also illustrated are non-compatible control panels <NUM> such as legacy control panels <NUM>-L and third party control panels <NUM>-C. Legacy control panels <NUM>-L are control panels that lack network connectivity and thus are unable to connect via the public network <NUM>. Such control panels <NUM>-L can be manufactured by the same company providing the connected services system <NUM> but at a time before network connectivity was desirable in control panels. Third party control panels <NUM>-C are control panels manufactured by different companies or business entities than that providing the connected services system <NUM> and may or may not have network connectivity. Even if they have network connectivity, third party control panels <NUM>-C will often use different protocols than the connected services system to communicate status, diagnostic and testing information.

Non-compatible control panels <NUM> can be retrofitted with devices that enable network connectivity. In the illustrated example, one non-compatible control panel <NUM> connects to a gateway device <NUM>. The gateway device <NUM> provides access for the non-compatible control panel <NUM> to the public network <NUM> and thus to the connected services server <NUM>.

However, regardless of age or manufacturer, control panels will almost universally communicate with a monitoring station <NUM>, which is a service for monitoring multiple fire alarm systems for indications of a potential fire and notifying the proper authorities, such as the fire department. Monitoring stations <NUM> can be administered by a third party company, the same company that manufactured the fire alarm system, the same company providing the connected services system <NUM>, or a public agency, among other examples. They are often required by regulations, making them a standard component of most fire alarm systems.

According to the present invention, instead of sending information directly to the connected services server <NUM>, the non-compatible control panels <NUM> send connection status signals and alarm signals to the monitoring station <NUM>. Connection status signals are signals that will typically employ a handshaking arrangement to confirm the connection between the control panels <NUM>, <NUM> and the monitoring station <NUM> is active and functionality properly. Alarm signals are signals indicating that a fire alarm system has entered an alarm state, indicating a potential fire.

In different examples, the non-compatible control panels <NUM> will send signals to the monitoring station <NUM> via several different transmission media, including wide area networks such as the internet, telephone systems, wireless radio networks, cellular networks and voice over internet protocol (VOIP) systems.

The monitoring station <NUM> receives the connection status and alarm signals from the non-compatible control panels <NUM> and forwards status information for the non-compatible control panels <NUM> to the connected services system <NUM> via the public network <NUM>.

In an arrangement not covered by the claims, the status information is translated by a translation system <NUM>. This translation system can be a process that executes on the computer system of the monitoring station <NUM> or executes on a separate monitoring station gateway computer system. In either case, the translation system <NUM> translates status information into a compatible format before it is sent to the connected services system <NUM>.

According to the invention, status information from the monitoring station <NUM> is received by a mapping service <NUM>. This mapping service can be a mapping server or mapping process executing on a connected services server <NUM> of the connected services system <NUM>. The mapping service <NUM> is a process that translates status information received from the monitoring station <NUM> into compatible status information that is stored to the connected services database <NUM>.

Also shown is an on-site technician <NUM> using a mobile computing device <NUM>. In general, the technicians will perform maintenance, testing and repair on the different fire alarm systems. The mobile computing device <NUM> connects to the public network <NUM> over a wireless communication link and operated by the technician <NUM>. In examples, the mobile computing device <NUM> is a laptop computer, smart phone, tablet computer, or phablet computer (i.e., a mobile device that is typically larger than a smart phone, but smaller than a tablet), to list a few. The mobile computing device <NUM> receives and displays status, diagnostic and testing information from the connected services server <NUM> via the public network <NUM>.

<FIG> illustrates an example of information being stored in the connected services database <NUM> of the connected services system <NUM>.

In one example, a compatible control panel <NUM> sends status, diagnostic and testing information directly to the connected services server <NUM> via the public network <NUM>. The connected services server <NUM> stores the information in the connected services database <NUM>. The information is stored in "Control panel record <NUM>", which includes identification information, location information, status history/state data, diagnostic data, alarm history and test data pertaining to the fire alarm system that includes the compatible control panel <NUM>.

Identification information can include a user specified name or serial number, among other examples. Location information can include an address of the premises in which the fire alarm system is installed as well as specific locations within the premises where the compatible control panel <NUM>, or other fire detection and notification devices are installed. Status history/state data can include the operational status of the fire alarm system and its components over time. Diagnostic information can include the power status (such as line voltage, battery voltage, and whether the device is powered by the battery or the line), sensor data (such readings from the sensors of various individual fire detection devices), and loop status, among other examples. Testing information can include the time and date of tests performed on the fire alarm system, the pass/fail result of the tests, and the readings detected by components of the fire alarm system during testing, among other examples.

In another example not covered by the claims, one or more non-compatible control panel <NUM> sends status, diagnostic and testing information to the connected services server <NUM> via the gateway device <NUM>, which allows connectivity to the public network <NUM>. The connected services server <NUM> stores the information in the connected services database <NUM>. The information is stored in "Control panel record <NUM>", which includes the same types of information described for "Control panel record <NUM>" pertaining to the fire alarm system that includes the non-compatible control panel <NUM>.

According to the invention, a legacy control panel <NUM>-L sends connection status and alarm signals to the monitoring station <NUM>. The monitoring station <NUM> then forwards status information for the legacy control panel <NUM>-L to the mapping service or server <NUM> via the public network <NUM>. The mapping service <NUM> translates the status information into a compatible format and forwards it to the connected services server <NUM>. The connected services server <NUM> then stores the information in the connected services database <NUM>. The information is stored in "Control panel record <NUM>", which includes identification information, location information, status history/state data, alarm history and test data pertaining to the fire alarm system that includes the legacy control panel <NUM>-L.

In another example, a third party control panel <NUM>-C sends connection status and alarm signals to the monitoring station <NUM>. The monitoring station <NUM> then forwards status information for the third party control panel <NUM>-C to the mapping service <NUM> via the public network <NUM>. The mapping service <NUM> translates the status information into a compatible format and forwards it to the connected services server <NUM>. The connected services server <NUM> stores the information in the connected services database <NUM>. The information is stored in "Control panel record <NUM>", which includes identification information, location information, status history/state data, alarm history and test data pertaining to the fire alarm system that includes the legacy control panel <NUM>-C.

Also illustrated in this example are print reports <NUM>, which are reports printed on paper that can include status, diagnostic and testing information pertaining to fire alarm systems. This information is detected and extracted from the print reports <NUM>, for example, by a scanner <NUM> in conjunction with software with optical character recognition capabilities. The mapping service <NUM> receives the information from the printed reports <NUM> via the OCR scanner <NUM> and translates it into a compatible format. The information is then stored in the connected services database <NUM> in the appropriate control panel records.

In one example, a university includes several buildings with several fire alarm systems, which include components that vary by age and manufacturer, including compatible control panels <NUM> and/or non-compatible control panels <NUM>. A technician <NUM> testing or repairing the fire alarm systems for the university can use the connected services system <NUM> to generate a comprehensive inventory of control panels for the entire university, regardless of compatibility between the control panels and the connected services system <NUM>. The inventory is requested with, received by, and displayed on the mobile computing device <NUM>.

In another example, a fire alarm system including a non-compatible control panel <NUM> is operating normally. Connection status signals are sent from the control panel <NUM> to the monitoring station <NUM>. The monitoring station <NUM> forwards status information to the connected services system <NUM>. The information is mapped by the mapping service <NUM> and stored in the connected services database <NUM>. A technician <NUM> views the control panel record for the fire alarm system on the mobile computing device <NUM> and confirms that the connection between the fire alarm system and the monitoring station <NUM> is consistently strong.

In another example, a fire alarm system including a non-compatible control panel <NUM> intermittently loses connectivity with the monitoring station <NUM>. A technician <NUM> reviews and analyzes the status history of the non-compatible control panel <NUM> on the mobile computing device <NUM> to determine possible causes of the loss of connectivity such as recurring network congestion or a periodic walkthrough tests of the fire alarm system, causing the fire alarm system to be disconnected from the monitoring station <NUM>.

The above described systems can also be used to facilitate, monitor and validate walkthrough tests. The following describes a conventional walkthrough test using a connected services system and then a test in which the panel is connected to the connected services system via a monitoring station.

In more detail, <FIG> is a sequence diagram illustrating how the mobile computing device <NUM>, fire detection and fire annunciation devices <NUM>-<NUM> to <NUM>-<NUM>, control panel <NUM>, a testing computer <NUM>, connected services server <NUM>, and connected services database <NUM> interact during a walkthrough test in a conventional setup.

This method is disclosed in an earlier application entitled "Testing System and Method for Fire Alarm System" by <CIT>), which is incorporated herein by this reference.

In this setup, the testing computer <NUM> is connected to the control panel <NUM> (with an RS-<NUM> cable, a universal serial bus (USB) cable or Ethernet (IEEE <NUM>) cable (e.g., Cat <NUM> or Cat <NUM>), to list a few examples). The testing computer <NUM> also connects to the public network <NUM>.

In a first example (labeled Device <NUM> Test), the on-site technician <NUM> activates one of the fire detection and fire annunciation devices <NUM>-<NUM> to <NUM>-<NUM> of the fire alarm system. The activated device sends an electronic signal to the control panel <NUM>. This electronic signal could be a binary signal indicating an alarm state and/or what is termed an analog value, which is representation of the level of smoke detected (obscuration level) by the device.

The control panel generates event data, which are sent to the testing computer <NUM>. The event data are then sent from the testing computer <NUM> to the connected services server <NUM>, which stores the event data in the connected service database <NUM>. The connected services server <NUM> then sends the event data and device history data to the mobile computing device <NUM>.

Typically, the event data includes identification information such as a unique identifier for the fire alarm control panel <NUM>, <NUM>, address of the activated device or devices generating the event data, location information such as a physical location of the activated devices (<NUM>-<NUM>, <NUM>-<NUM>. <NUM>-n), a date and time of the activation, status information, including a fault state of the activated devices, at least one analog and/or detected value generated by the activated devices such as a detected smoke level or detected ambient temperature, and/or custom labels of the activated devices. Additionally, acknowledgement and restoral times of the control panel are included in the event data.

In the illustrated example, the on-site technician <NUM> reviews the event data and optionally applies annotations to the event data. These annotations typically include testing information such as a pass or fail status, images, and/or voice and text messages, to list a few examples. For example, if the fire detection or fire annunciation device appears worn or damaged, the technician would annotate the event data with an image of the device. The annotated event data are then sent back to the connected services server <NUM> and stored in the connected services database <NUM>. This annotated device history may be accessed later by the on-site technician <NUM>, a remote technician, or other users that are authorized to access the event data.

A second example (labeled Device <NUM> Test) illustrates a scenario in which the mobile computing device <NUM> temporarily loses communication with the connected services server <NUM>. In general, the testing process is similar to the previous example (i.e., Device Test <NUM>). In this example, however, the mobile computing device <NUM> temporarily loses communication with the connected services server <NUM>. Because communication has been lost, the transmission of event data from connected services server <NUM> fails to reach the mobile computing device <NUM>. In the illustrated example, this is shown by the "X. " In a current implementation, if there is a failed transmission, the connected services server <NUM> buffers and attempts to resend the event data. This event data could be resent based on a request from the mobile computing device <NUM> or the connected services server <NUM> could attempt resend the event periodically until event data are received and acknowledged by the mobile computing device <NUM>.

The sequence diagram further illustrates a report request from the on-site technician <NUM> (labeled Report Request). Typically, reports are generated after the on-site technician <NUM> has completed the test of the entire fire alarm system, but the on-site technician <NUM> (or a remote technician) could request a report at any time before or during the test.

In the illustrated embodiment, the on-site technician <NUM> sends a report request to the connected services server <NUM>. The connected services server <NUM> queries the connected services database <NUM> to obtain an aggregate history for all of the fire detection and fire annunciation devices of the fire alarm system. The aggregate history data are transferred to the mobile computing device <NUM> and reviewed by the on-site technician <NUM>. The on-site technician <NUM> may then add annotations to the aggregate history data and send the annotated aggregate history data to connected services server <NUM>.

<FIG> is a sequence diagram illustrating how the monitoring station <NUM> can be used to communicate status information and/or event data from legacy or third party control panels <NUM> to the connected services server <NUM> during a walkthrough test of a fire alarm system.

In a first example (labeled Device <NUM> Test), the on-site technician <NUM> activates one of the fire detection and fire annunciation devices <NUM>-<NUM> to <NUM>-n of the fire alarm system. This can be accomplished by depressing a self-test button on the housing of the device or by placing a hood over a smoke detector, for example, and filling the hood with real or artificial smoke.

As before, the activated device sends an electronic signal to the control panel <NUM>. This electronic signal could be a binary signal indicating an alarm state and/or what is termed an analog value, which is representation of the level of smoke detected (obscuration level) by the device.

The control panel <NUM> generates event data, which are sent to the monitoring station <NUM> via the POTS, VOIP, Cellular or other data connection. The event data are then sent from the monitoring station <NUM> to the connected services system <NUM>, which stores the event data in the connected service database <NUM>. Here, the event data includes identification information such as a unique identifier for the fire alarm control panel <NUM>, address of the activated device or devices generating the event data, location information such as a physical location of the activated devices (<NUM>-<NUM>, <NUM>-<NUM>. <NUM>-n), a date and time of the activation, status information, including a fault state of the activated devices, at least one analog and/or detected value generated and transmitted by the activated devices such as a detected smoke level or detected ambient temperature, and/or custom labels of the activated devices. Additionally, acknowledgement and restoral times of the control panel and/or tested devices are included in the event data.

In some examples, the translation system <NUM> in the monitoring station <NUM> is used to translate the event data into a format expected by the connected services server <NUM>. In other examples, this translation is performed by the mapping service <NUM>.

In any event, the connected services server <NUM> then sends the event data and device history data (including identification information, location information, status history/state data, diagnostic data, alarm history and test data) to the mobile computing device <NUM>.

As before, the on-site technician <NUM> reviews the event data and optionally applies annotations to the event data. These annotations typically include a pass or fail status, images, and/or voice and text messages, to list a few examples. For example, if the fire detection or fire annunciation device appears worn or damaged, the technician would annotate the event data with an image of the device. The annotated event data are then sent back to the connected services server <NUM> and stored in the connected services database <NUM>. This annotated device history may be accessed later by the on-site technician <NUM>, a remote technician, or other users that are authorized to access the event data.

The sequence diagram further illustrates the report request from the on-site technician <NUM> (labeled Report Request). Typically, reports are generated after the on-site technician <NUM> has completed the test of the entire fire alarm system, but the on-site technician <NUM> (or a remote technician) could request a report at any time before or during the test.

In the illustrated embodiment, the on-site technician <NUM> sends a report request to the connected services server <NUM>. The connected services server <NUM> queries the connected services database <NUM> to obtain an aggregate history for all of the fire detection and fire annunciation devices of the fire alarm system. The aggregate history data are transferred to the mobile computing device <NUM> and reviewed by the on-site technician <NUM>. The on-site technician <NUM> may then add annotations to the aggregate history data and send the annotated aggregate history data to connected services server <NUM> as before.

One advantage of the present system is that this automated inspection feature is the proof of inspection created by connected service system <NUM>, including time stamping and coverage of testing despite the fact that the inspection is being performed on a legacy control panel <NUM>-L, for example. As a result, testing validation is now possible on existing panels <NUM>, which only have a connection to a monitoring station <NUM>.

Claim 1:
A method for monitoring fire alarm systems, the method comprising:
sending, from non-compatible control panels (<NUM>) of fire alarm systems to monitoring stations over a connection with the monitoring stations (<NUM>), alarm signals indicating that the fire alarm systems have entered an alarm state, wherein the non-compatible control panels are non-compatible for directly communicating with a connected services system;
responding, by the monitoring stations (<NUM>), to the alarm signals by notifying authorities of potential fires;
forwarding, by the monitoring stations (<NUM>), status information directly to a connected services system, wherein the status information includes information about the alarm state of the fire alarm systems;
sending, via compatible control panels (<NUM>) of the fire alarm systems that are compatible for directly communicating with the connected services system, status, diagnostic and/or testing information directly to the connected services system and alarm signals to the monitoring stations (<NUM>);
translating, by the mapping service (<NUM>), the status information from the monitoring stations (<NUM>) into a compatible format for a connected services database (<NUM>) of the connected services system;
storing, by the connected services server (<NUM>), the translated status information in the connected services database (<NUM>); and
storing, by the connected services server (<NUM>), the status, diagnostic and testing information for the compatible control panels (<NUM>) in the connected services database.