WO2008150815A2

WO2008150815A2 - Building automation system with text messaging

Info

Publication number: WO2008150815A2
Application number: PCT/US2008/065008
Authority: WO
Inventors: Amit Patni; Atul Ghaisas
Original assignee: Johnson Controls Technology Company
Priority date: 2007-05-30
Filing date: 2008-05-28
Publication date: 2008-12-11
Also published as: WO2008150815A3

Abstract

A method for sending a text message regarding one or more building automation system devices to a mobile wireless device includes, at a server, receiving data about the one or more building automation system devices. The method further includes determining whether to send a text message relating to the received data, the determination based on priority information associated with the received data. The method yet further includes formatting the text message according to a text messaging protocol compatible with the mobile wireless device and sending the text message to the mobile wireless device.

Description

BUILDINGAUTOMATION SYSTEM WITH TEXT MESSAGING

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims the benefit of U.S. Provisional Patent Application No. 60/940,884, filed May 30, 2007, the entire disclosure of which is incorporated by reference.

BACKGROUND

[0002] The present disclosure generally relates to building automation systems. The present disclosure relates more specifically to systems and methods for sending system text messages to personnel.

[0003] Building automation systems are often employed in buildings such as office buildings, schools, manufacturing facilities, and the like, for controlling the internal environment of the facility. Building automation systems may be employed to control temperature, air flow, humidity, lighting, energy, boilers, chillers, power, security, fluid flow, and similar building systems relating to the environment of the building. Some building automation systems include heating, ventilation, and/or air conditioning (HVAC) systems. HVAC systems commonly seek to provide thermal comfort, acceptable air quality, ventilation, and controlled pressure relationships to building zones. HVAC systems typically include an HVAC control system and one or more ventilation devices such as air handling units and variable air volume (VAV) boxes.

[0004] Building automation systems may be autonomous or networked together to form an integrated and/or distributed system. In either case, the systems may be controlled and/or accessed by computers, terminals, or workstations at one or more locations within the building or at a remote location. Such workstations may be located, for example, at the manager's office, the building operating engineer's office, and/or the security desk. When the building is part of a larger commercial or educational campus, the building automation systems and networks for each building may be connected to a wide area communication network, the Internet, or some other network that enables control from a variety of locations such as a central campus facility management office or an offsite location. Offsite communications may be accomplished by using standard or proprietary wired or wireless telecommunications links. [0005] Modern building automation systems typically include a variety of user interface features that allow a user (e.g., building engineer, building employee, contractor, manager, etc.) to view or control parameters or settings of various building automation components or systems (e.g., HVAC, security, emergency, etc.). For example, a building automation system may include a computer application or browser interface configured to display the various hardware components of the HVAC system and the components' operating parameters. As various components or subsystems of building management systems have become more connected and complicated, identifying and troubleshooting problems efficiently has become more challenging.

[0006] To facilitate the identification and notification of problems, building automation systems may forward component alarm messages from various lower level components to supervisory level controllers or to user interfaces. For example, certain conditions may be sensed or detected by building automation system components such as temperature sensors, flow sensors, security cameras, or other component of the system. Control devices of the building automation system (or the sensing devices themselves) may determine that certain sensed or detected conditions warrant an alarm being communicated to a supervisory controller, server, or user interface. For example, a networked control device may generate an alarm when a sensed air temperature in a particular zone exceeds a predetermined setpoint.

SUMMARY

[0007] The invention relates to a method for sending a text message regarding one or more building automation system devices to a mobile wireless device. The method includes at a server computer, receiving data about the one or more building automation system devices. The method further includes determining whether to send a text message relating to the received data, the determination based on priority information associated with the received data. The method yet further includes formatting the text message according to a text messaging protocol compatible with the mobile wireless device and sending the text message to the mobile wireless device.

[0008] The invention further relates to a server computer for communicating a text message relating to one or more building automation system devices to a mobile wireless device. The server includes a communications interface configured to communicate with the mobile wireless device over a wireless network. The server further includes a processing circuit configured to receive data about the one or more building automation system devices and to determine whether the text message should be sent based on priority information associated with the received data. The processing circuit is also configured to format the text message according to a text messaging protocol compatible with the mobile wireless device and to send the text message to the mobile wireless device. [0009] The invention further relates to a machine -readable medium for programming a computer to send a text message regarding one or more building automation system devices to a mobile wireless device. The medium includes processor executable instructions for receiving data about the one or more building automation system devices. The medium further includes processor executable instructions for determining whether to send a text message relating to the received data, the determination based on priority information associated with the received data. The medium further includes processor executable instructions for formatting the text message according to a text messaging protocol compatible with the mobile wireless device and sending the text message to the mobile wireless device.

[0010] The invention yet further relates to a first server computer having a software delivery module configured to transfer software code to a second server via a wired and/or wireless communications link. The software code is configured to program the second server to conduct the steps including: at the second server, receiving data about the one or more building automation system devices; determining whether to send a text message relating to the received data, the determination based on priority information associated with the received data; formatting the text message according to a text messaging protocol compatible with the mobile wireless device; and sending the text message to the mobile wireless device.

[0011] Alternative exemplary embodiment relate to other features and combinations of features as may be generally recited in the claims.

BRIEF DESCRIPTION OF THE FIGURES

[0012] The disclosure will become more fully understood from the following detailed description, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements, in which:

[0013] FIG. 1 is a perspective view of a building having a plurality of devices, according to an exemplary embodiment; [0014] FIG. 2 is a close-up perspective view of a building zone of the building of FIG. 1 , according to an exemplary embodiment;

[0015] FIG. 3 is a diagram of a mobile device shown in communication with the building and/or building devices of FIG. 1, according to an exemplary embodiment;

[0016] FIG. 4 is a schematic diagram of a building automation system for the building of

FIG. 1, according to an exemplary embodiment;

[0017] FIG. 5A is a block diagram of a system including a server computer for communicating text messages with a mobile wireless device, according to an exemplary embodiment;

[0018] FIG. 5B is a detailed block diagram of the server of FIG. 5A, according to an exemplary embodiment;

[0019] FIG. 6A is a flow chart of a process for sending a text message regarding one or more building automation system devices to a mobile wireless device, according to an exemplary embodiment;

[0020] FIG. 6B is a detailed flow chart of a process for sending a text message regarding one or more building automation system devices to a mobile wireless device, according to an exemplary embodiment;

[0021] FIG. 7 is a graphical user interface that may be generated by the system for configuring a database and/or processing circuit for sending a text message regarding one or more building automation system devices to a mobile wireless device, according to an exemplary embodiment;

[0022] FIG. 8 is a graphical user interface that may be generated by the system for configuring a database and/or processing circuit of the system, according to an exemplary embodiment; and

[0023] FIG. 9 is a graphical user interface that may be generated by the system for configuring a database and/or processing circuit of the system, according to an exemplary embodiment.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

[0024] Before turning to the figures, which illustrate the exemplary embodiments in detail, it should be understood that the application is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology is for the purpose of description only and should not be regarded as limiting.

[0025] Referring generally to the figures, a building automation system (BAS) configured to send text messages to wireless devices is shown. In order to inform building personnel of BAS data (e.g., events, alarms, alerts, etc.) when building personnel are located at remote locations, a server converts BAS data into a text messaging format or protocol, such as the Short Message Service (SMS) format, and transmits the resulting text message to a mobile wireless device via a wireless communications system. The text messages may be generated and/or formatted by a server computer (or an application thereof) or controller when data warranting a text message or alarm is received. These text messages may then be sent to a communications interface compatible with the text messaging format. One type of communications interface compatible with text messages such as SMS text messages is a Global System for Mobile (GSM) communications modem (and/or any number of hardware/software applications for using the modem). A BAS with text messaging may route formatted text messages to the communications interface. The communications interface may then send the text messages over a wireless communications network (e.g., a GSM network) to a remote mobile wireless device such as a GSM cellular phone. Building personnel may receive BAS text messages in this manner and be apprised of the status of the BAS even when located remotely from a workstation.

[0026] FIG. 1 is a perspective view of a building 12 having a plurality of devices 13 capable of transmitting and/or receiving signals, according to an exemplary embodiment. As illustrated, building 12 may include any number of floors, rooms, spaces, zones, and/or other building structures and areas. According to various exemplary embodiments, building 12 may be any area of any size or type, including an outdoor area. Devices 13 may exist inside or outside the building, on walls or on desks, be user interactive or not, and may be any type of building device. For example, devices 13 may be security devices, light switches, fan actuators, temperature sensors, thermostats, smoke detectors, occupancy sensors, other various types of sensors (flow, pressure, etc.), etc. Devices 13 may be configured to conduct building automation functions (e.g., sense temperature, sense humidity, control a building automation device, etc.). Devices 13 may also serve any number of network functions (e.g., RF measuring functions, network routing functions, etc.). A controller system 14 is shown as a desktop wireless device. Controller system 14 may serve as a network coordinator, wireless access point, router, switch, or hub, and/or serve as another node on a network. A workstation 19 is shown as a personal workstation. Workstation 19 may allow building engineers to interact with controller system 14. Devices 13 may be connected to controller system 14 and/or workstations 19 via a wired and/or wireless connection.

[0027] Building 12 may be a commercial building, an industrial building, an institutional building, a healthcare facility, a school, a manufacturing plant, an office building, a residential building, or any other building that makes use of a BAS. Building 12 may include any type or number of HVAC components or devices such as air handling units (AHUs) (e.g., a makeup air unit, a rooftop air unit, a fan coil unit, a constant air volume AHU, a variable air volume AHU, etc.). Building 12 may also include any type or number of HVAC subsystems and/or HVAC zones. For example, an HVAC zone may include a single room or multiple rooms. In other buildings or systems, each floor of a building may be a separate building zone or HVAC zone controlled by a separate HVAC system, HVAC subsystem, or HVAC component set. Any number of individual heating, cooling, or air control devices may be disposed around the building and/or each building zone. For example, variable air volume units may be installed throughout building 12. A variable air volume unit or set of variable air volume units may be used by an HVAC control system to regulate the air flow rate and other variables (e.g., heat, humidity, outside air, etc.) provided to the building zone by the HVAC system. Each variable air volume unit may be of any type or design and may include a damper, an actuator, and an actuator control circuit. [0028] Referring to FIG. 2, a close-up perspective view of a building zone 20 is shown, according to an exemplary embodiment. Building zone 20 may include an HVAC vent 26 coupled to ductwork. Supply air flow or ventilation may be provided to zone 20 via vent 26. Building zone 20 may include any number of additional or alternative objects, equipment, structures, surfaces, people, and/or lights. Building zone 20 may additionally include a workstation 19 and/or mobile workstations such as laptop 24. [0029] Sensors 22 may be disposed within and/or around building zone 20 and may be configured to sense building conditions or variables of building zone 20. For example, sensors 22 may be temperature sensors, humidity sensors, air quality sensors, equipment sensors, person sensors, lighting sensors, heat transferring object sensors, infrared sensors, RFID transceivers, and/or any other type of sensor that may be configured to sense a building related condition. Sensors 22 may be disposed on the walls of building zone 20, or may be located, positioned, or disposed in any manner or location within building zone 20. Sensors 22 may also have any number of user interface and/or communications features configured to facilitate operation with a BAS. Sensors 22 may be wireless or wired sensors configured to operate on a mesh network or any other network topology. Sensors 22 may also exist in ventilation devices, security devices, fire alarms, controllers, etc. [0030] Referring now to FIG. 3, an illustration of a mobile wireless device 300 receiving a text message from a system associated with a building device of building 12 is shown, according to an exemplary embodiment. Mobile wireless device 300 is shown as a personal digital assistant (PDA) having wireless communication capabilities but may be any device configured to communicate via communication network 302 (e.g., a mobile phone, a cellular phone, a dedicated text-messaging device, a personal navigation device (PND) configured for receiving text messages, an automotive control system configured for wireless communication, etc.). In FIG. 3, workstation 19 may be configured as a server computer for generating text messages based on event data generated by the BAS and/or building devices thereof. Workstation 19 is shown to be in communication with mobile wireless device 300 via communication network 302. Workstation 19 uses communication network 302 to send the generated text messages to mobile wireless device 300. FIG. 3 illustrates a text message received by mobile wireless device 300 displayed on the screen 304 of mobile wireless device 300. As shown, the text message may be an alarm and the text message may include information such as a building identifier, a zone identifier, a room identifier, a time and/or date for the text message, a narrative of the text message, a code for the text message, a title for the text message, or include any other relevant information about the BAS and/or the device that caused the generation of the text message. [0031] Referring to FIG. 4, a schematic diagram of a BAS 100 that may be used with the systems and methods of the present disclosure is shown, according to an exemplary embodiment. BAS 100 may include one or more supervisory controllers (e.g., a network automation engine (NAE)) 102 connected to a proprietary or standard communications network such as an IP network (e.g., Ethernet, WiFi, ZigBee, Bluetooth, etc.). Supervisory controllers 102 may support various field- level communications protocols and/or technology, including various Internet Protocols (IP), BACnet over IP, BACnet Master- Slave/Token-Passing (MS/TP), N2 Bus, N2 over Ethernet, Wireless N2, LonWorks, ZigBee, and any number of other standard or proprietary field-level building management protocols and/or technologies. Supervisory controllers 102 may include varying levels of supervisory features and building management features. The user interface of supervisory controllers 102 may be accessed via terminals 104 (e.g., web browser terminals) capable of communicably connecting to and accessing supervisory controllers 102. For example, FIG. 4 shows multiple terminals 104 that may variously connect to supervisory controllers 102 or other devices of BAS 100. For example, terminals 104 may access BAS 100 and connected supervisory controllers 102 via a WAN, an Internet location, a local IP network, or via a connected wireless access point. Terminals 104 may also access BAS 100 and connected supervisory controllers 102 to provide information to another source, such as printer 132. [0032] Supervisory controllers 102 may be connected to any number of BAS devices. The devices may include, among other devices, devices such as field equipment controllers (FEC) 106 and 110 such as field-level control modules, variable air volume modular assemblies (VMAs) 108, integrator units, room controllers 112 (e.g., a VAV device or unit), other controllers 114, unitary devices 116, zone controllers 118 (e.g., an AHU controller), boilers 120, fan coil units 122, heat pump units 124, unit ventilators 126, expansion modules, blowers, temperature sensors, flow transducers, other sensors, motion detectors, actuators, dampers, heaters, air conditioning units, etc. These devices may generally be controlled and/or monitored by supervisory controllers 102. Data generated by or available on the various devices that are directly or indirectly connected to supervisory controller 102 may be passed, sent, requested, or read by supervisory controller 102 and/or sent to various other systems or terminals 104 of BAS 100. The data may be stored by supervisory controller 102, processed by supervisory controller 102, transformed by supervisory controller 102, and/or sent to various other systems or terminals 104 of the BAS 100. As shown in FIG. 4, the various devices of BAS 100 may be connected to supervisory controller 102 with a wired connection or with a wireless connection. [0033] Still referring to FIG. 4, a server computer 130 (e.g., an application and data server (ADS), an enterprise server, etc.) is shown, according to an exemplary embodiment. Server computer 130 is a computer system (e.g., local and/or distributed) that includes a database management system (e.g., a relational database management system, Microsoft SQL Server, SQL Server Express, etc.) and server software (e.g., web server software, application server software, virtual machine runtime environments, application software, etc.) that provide access to data and route commands to BAS 100. For example, server computer 130 may serve user interface applications. Server 130 may also serve applications such as Java applications, messaging applications, trending applications, database applications, etc. Server 130 may store trend data, audit trail messages, alarm messages, event messages, contact information, and/or any number of BAS-related data (e.g., data relating to the building devices of the BAS). Terminals may connect to server 130 to access the entire BAS 100 and historical data, trend data, alarm data, operator transactions, and any other data associated with BAS 100, its components, or applications. Various local devices such as printer 132 may be attached to components of BAS 100 such as server 130. [0034] Referring to FIG. 5 A, a block diagram of server computer 130 interacting with a BAS (e.g., supervisory controller 102 and building device 402) to provide text messages to a mobile wireless device 300 is shown, according to an exemplary embodiment. Building device 402 may be a field controller or any other building device that may generate event data and be configured to provide the event data to the supervisory controller 102 or directly to server 130. Server 130 may be communicably coupled to supervisory controller 102, building device 402, and/or any other BAS devices via any wired or wireless technology of the past, present, or future. Supervisory controller 102 may be configured to route the event data (e.g., event messages, alarms, historical information, etc.) to server 130. FIG. 5A further illustrates a communications interface 408 configured to send text messages to mobile wireless device 300 via communication network 302.

[0035] Communications interface 408 may be a module or device (hardware and/or software) configured to provide data communications functionality in accordance with different types of mobile telephone systems. Examples of mobile telephone systems may include Code Division Multiple Access (CDMA) cellular telephone communications systems, GSM cellular systems, GSM with General Packet Radio Service (GPRS) systems (GSM/GPRS), CDMA/lxRTT (1 times Radio Transmission Technology) systems, Enhanged Data Rates for Global Evolution (EDGE) systems, Evolution Data Only or Evolution Data Optimized (EV-DO) systems, etc. According to other exemplary embodiments, communications interface 408 may be configured to provide communications via wireless local area networks, wireless wide area networks, the Internet, through wireless access points, and the like. According to an exemplary embodiment, communications interface 408 is a GSM modem device connected to server 130 via a wired connection. [0036] When building device 402 connected to supervisory controller 102 experiences an event that may trigger an alarm (or some other condition), supervisory controller 102 may pass data relating to the event (e.g., an event message, an alarm signal, one or more electrical signals, etc.), or a device to which the event relates, to server 130. Server 130 may receive data from supervisory controller 102 via any type of wired and/or wireless network. Supervisory controller 102 may send event data directly or indirectly to BAS database 404. According to other various embodiments, server 130 is configured to poll BAS database 404 for updated data (e.g., at regular intervals). [0037] It should be noted that the event and/or the alarm may be any data about or regarding a building automation system device. For example, the event and/or the alarm used to generate a text message may be information about at least one of: a parameter sensed by the building automation system device, a status for the building automation system device, data stored in memory of the building automation system device, data stored in a supervisory controller of the building automation system device, an alarm condition determined by a supervisory controller to be associated with the building automation system device, and a second building automation system device attached to the building automation system device.

[0038] Server 130 is shown to include processing circuit 406. Processing circuit 406 may be configured to provide processing or computing resources to server 130. Processing circuit 406, according to an exemplary embodiment, is configured to conduct processing tasks for completing the activities described in the present disclosure. Processing circuit 406 may be use any suitable processor or logic device, such as a central processing unit or general purpose processor. Processing circuit 406 may include any number of components, processors, memory devices, and the like to support the activities for which it is responsible. Processing circuit 406 may be implemented to include one or more dedicated processors, embedded processors, I/O processors, field programmable gate arrays, programmable logic devices, application specific integrated circuits, or the like.

[0039] According to various exemplary embodiments, server 130 may be implemented using hardware generally capable of running modern operating systems, database management software, and/or application server software. For example, server 130 may include hardware capable and configured to run software such as a Windows Operating System, UNIX, Linux, OS/2, etc. Server 130 may include hardware such as random access memory, read-only memory, a serial port, a USB port, a printer port, a hard-disk drive, solid state memory, processing circuits for operating the other devices and/or software, etc. It is important to note that processing circuit 406 and modules 502-508 (shown in FIG. 5B) and databases 404 and 405 may be implemented in a building automation system enterprise controller, application server, and/or supervisory controller. For example, server 130 may be a Johnson Controls Metasys Network Automation Engine having a GSM modem connected on a communications port such as a serial port and having a valid GSM SIM card (or other valid GSM communication information).

[0040] According to an exemplary embodiment, when event data is received by server 130, server 130 may copy the event data from BAS database 404 to messaging database 405. BAS database 404 may be a history of events received by the enterprise server, and messaging database 405 may serve as a temporary record, a message queue, and/or a historical messaging record. Database information for either BAS database 404 or messaging database 405 may be added and/or changed by changing relationships, updating records, appending records, etc. It should be noted that database 404 and/or database 405 may be or include one or more tables of information. Further, according to various exemplary embodiments, database 404 and 405 are tables or sets of tables within the same database definition.

[0041] According to one exemplary embodiment, database 405 may include several data tables. One such table may include priority information. The database (or software for interacting with the database) may maintain a relationship between priority information (e.g., priority numbers, priority classes, etc.) and events of the BAS. For example, database 405 may include a table (and/or other data structures) of possible events (e.g., event identifiers) and associations between the possible events and priority information. By way of further example, an event identifier that is created when a temperature sensor detects a temperature five percent above setpoint might be associated with a priority level three while an event identifier that is created when the temperature sensor detects a temperature thirty percent above setpoint might be associated with a priority level one (e.g., indicating importance greater than that of priority level three). It may be noted that priority information other than numbers may be used (e.g., a different table may relate to high priority event data, letters or strings of characters may be used to distinguish priority levels). A table or other data structure for priority information may additionally include metadata (e.g., when the priority was added to the table, who added the priority, etc.). Data in the table may be added or updated by a user as new priorities are created or detected. [0042] Database 405 may also include information about a mobile wireless device identifier (e.g., phone number, e-mail address, SIM card identifier) to which event information should be passed (e.g., via a text message). According to an exemplary embodiment, contact or user records may be stored in database 405 and associated with varying priorities. If a high priority event is determined to be received by server 130, each contact person or user associated with the "high priority" level should receive a message relating to the event. Contact information for the contact (e.g., information about the user's mobile wireless device identifier) can then be used by server 130 for the transmission of a relevant text message.

[0043] According to another exemplary embodiment, another table may include information regarding sent messages. For example, the priority number or ID associated with the message, the date and time of the sent message, and contents of the actual message may be stored. Data in the table may be updated as new messages are sent. This table may be used, for example, after the user has received the text message to relate the text message to the specific BAS device that generated the event that triggered the message. [0044] Referring to FIG. 5B, a detailed block diagram of server 130 of FIG. 5 A is shown, according to an exemplary embodiment. Processing circuit 406 is shown to include a variety of modules configured to support the messaging applications described herein. According to an exemplary embodiment, processing circuit 406 includes and/or accesses a memory device or memory devices including computer code for processing, completing, and/or facilitating the activities of the present application. The computer code may be provided as a single application (e.g., a standalone Java application, a text messaging application, etc.), a series of software modules or applications, code for various web site functions and/or pages, or otherwise. Databases 404 and 405 of server 130 may include a number of data tables that may be updated, checked, queried, sorted, and/or compared to other data tables or data values.

[0045] According to the exemplary embodiment shown in FIG. 5B, processing circuit 406 is shown to include messaging application 502, communications module 504, GUI module 506, and BAS client module 508. Messaging application 502 may be the primary messaging application configured to receive user input regarding priority and mobile wireless device identifier information. Messaging application 502 may be configured to coordinate the tasks of modules 504-508 and/or of accessing, updating, and maintaining database 405. For example, when events are received from BAS devices in BAS database 404, messaging application 502 may be configured to cause BAS client module (e.g., software for communicating with a BAS database and/or other BAS devices such as a supervisory controller) 508 to retrieve relevant data from BAS database 404. By way of further example, when messaging application 502 determines that a text message should be sent, it may send commands and/or the text message to communications module 504. Communications module 504 may be a software and/or hardware module of processing circuit 406 configured to control and/or communicate with communications interface 408 (shown in FIG. 5A). GUI module 506 may be configured to generate graphical user interface (GUI) screens for displaying data to users and for receiving input from users. GUI module 506 may generally be configured to layout data sent to it and to provide the control interface for receiving user input. GUI module 506 may be, for example, a web server, application server, a runtime environment w/ GUI libraries, etc. [0046] FIG. 6A shows a flow diagram of a process 600 for sending a text message regarding one or more building automation system devices to a mobile wireless device. Process 600 includes the step of receiving data about one or more building automation systems (step 602). Process 600 further includes the step of determining whether to send a text message relating to the received data (step 604). The determination is based on priority information associated with the received data. If the determination is made to send a text message relating to the received data, the server formats the text message according to a text messaging protocol compatible with the mobile wireless device (step 606). Once the text message is formatted, the server may send the text message to the mobile wireless device (step 608). According to an exemplary embodiment, sending the text message to the mobile wireless device includes transmitting the text message to a communications network. The communications network may be a mobile telephone communications network, the mobile telephone communications network compatible with one or more of a GSM standard, a personal communications service (PCS) standard, and a CDMA standard. The text messaging protocol may be a SMS protocol or a multimedia messaging service (MMS) protocol. Various exemplary embodiments of process 600 may further include determining which of a plurality of possible mobile wireless devices should be sent the text message based on the priority information.

[0047] Referring to FIG. 6B, a detailed flow diagram of a process 650 for sending a text message regarding one or more building automation system devices to a mobile wireless device is shown, according to an exemplary embodiment. Process 650 is shown to include receiving event data from a supervisory controller (step 652). A BAS database within the server may be updated upon receiving the event from the supervisory controller (step 654). According to an exemplary embodiment, a message database may then be updated (e.g., events may be queued in a database for processing) (step 656). According to an exemplary embodiment, the message database is only updated if the event data matches a certain event type (e.g., an alert or alarm type). An entry regarding priority may be updated (e.g., a row of data describing the priority is updated with data). Priority information relating to the updated message record may then be compared to priority logic, the contents of a priority table, or via another mechanism / data relationship (step 658).

[0048] If the comparison step (step 658) indicates that the priority associated with the updated message record is relatively high (e.g., above a threshold, matching a priority associated with one or more intended recipients, etc.), the server may then retrieve and/or create data relating to the event (step 660). The data may already be stored in the BAS database on the server, stored in the message database, or similarly stored local to the server. According to other exemplary embodiments, a supervisory controller, BAS device, or other BAS component is queried or polled for more detailed information regarding the event. Raw event data may also be organized or serialized at step 660. For example, excess detail regarding an event may be stripped and/or a string describing the event may be generated. According to various embodiments, XML or another specification for creating custom markup languages may be used to describe the event data. Step 660 may further include formatting the event data into a format appropriate for transmission as a text message. The event data may be formatted into a text messaging format compatible with a standard or proprietary text messaging protocol. For example, the event data may be formatted to comply with a SMS protocol or a MMS protocol. It should be appreciated that any other text messaging protocol may be utilized (e.g., an America Online Instant Messenger (AIM) protocol, a Sametime messaging protocol, a Mobile Instant Messaging (MIM) protocol, a Jabber protocol, an eBuddy protocol, a Windows Live Messenger protocol, a QQ protocol, an ICQ protocol, a Yahoo! Messenger protocol, an e-mail protocol, etc.). The data of the text message may be compressed, encrypted, tagged, or the server may conduct any number of additional tasks to create a text message suitable for sending to a mobile wireless device.

[0049] Process 650 is further shown to include the step of associating serial data with a mobile wireless device or a group of devices (step 662). As previously described, the messaging database can maintain associations or relationships between events and contacts or mobile wireless device identifiers. The relationship between event data and mobile wireless devices can be made by priority, by a building device type, by event type, or via any other grouping or distinction. According to other exemplary embodiments, priorities or other event data properties are associated with specific contacts (e.g., a contact information for a person) and thereby to the contact's mobile wireless device. Using this information and capability, if an event occurs that relates to a chiller in the building, the server may send a text message relating to the chiller-related event to the chiller expert. Similarly, if a high priority event occurs within the building, a group of contacts relating to high priority events may each receive a copy of a high priority text message describing the event. [0050] Process 650 is further shown to include providing the created and formatted text message to the communication interface (step 664). Step 664 may also include converting the text message, compressing the text message, serializing the text message, encrypting the text message or otherwise changing the text message to a protocol or format expected by the communication interface. The text message may be provided to communication directly (e.g., via a direct wired connection) or indirectly (e.g., server sends a message to the communication interface via a wired or wireless network). Once received by the communication interface, the communications interface is configured to send the converted output (step 666).

[0051] Once the text message is sent, the server may conduct any number of activities to begin processing the next event in the message database. For example, according to some exemplary embodiments, as soon as the message is confirmed as having been sent by the communications interface, the event record is removed from the messaging database and another record is processed for sending. According to other exemplary embodiments, the server may maintain the event in the messaging database until a confirmed receipt of message indication is received by the system. For example, the system may wait for the wireless network to indicate delivery of the message or the system may wait to receive an actual response from the user of the mobile wireless device to which the message was sent. By way of further example, every message sent to a mobile wireless device may include instructions appended to the end of the message for confirming receipt and/or that the contact will handle the event. If the contact indicates that he or she will handle the event (e.g., by return message), the event will be removed from the messaging database/queue. If, on the other hand, the contact indicates that he or she cannot handle the event (or if the contact does not respond within a certain period of time) the system may be configured to resend the text message relating to the event to back-up contacts or secondary contacts until some contact indicates that the event will be handled (e.g., looked into, inspected, cleared, etc.). [0052] According to various exemplary embodiments, processing circuit 406 of server 130 may be configured to generate a user interface (e.g., that users may access via a remote browser, a local terminal, or otherwise). The user interface may be implemented with onscreen links/buttons/controls that allow a connected user to add and or edit a priority, multiple priorities, mobile cellular phone numbers, change priority levels of specific events, etc. The generated user interface may also allow for the creation of a report of the text messages (or potential text messages) that have been sent and/or not sent. The reporting feature may be configured to allow a user to sort by various parameters, including parameters such as priority number, event type, event, device type, supervisory controller, time, messages sent, person name, phone number, and/or message out date. Reports may also be saved in any number of computer formats (e.g., such as spreadsheet formats, text formats, PDF formats, etc.) so the reports can easily be sent, for example, via mail, fax, or email. According to various other exemplary embodiments, the BAS with text messaging may automatically forward reports electronically (e.g., via e-mail, text message, etc.). The graphical user interface may also be configured to allow a user to set and/or edit options for sending text messages from the previous three days or for sending new text messages (for example, when a backlog of messages has developed).

[0053] Referring to FIG. 7, a screenshot of GUI 700 for editing priority information is shown, according to an exemplary embodiment. GUI 700 is shown to include a table that includes a priority ID 702, a priority number 704, and a status 706 to indicate if the priority is active. Priority ID 702 may be used to uniquely identify the priority. Priority number 704 may be used to weigh or categorize the priority (e.g., a higher priority number indicates a more critical priority). A user may activate or deactivate a priority via control 706. For example, priority ID 3 is marked as inactive. Accordingly, the server may be configured to refrain from conducting any messaging activity when events relating to priority ID 3 are received. An option to add or save a new priority or priority changes may be provided by priority report 700. For example, a user may add a new priority using add button 708. As another example, a user may edit an existing priority and use save button 710 to save the changes. Any "save," "add," or "edit" activity may correspondingly update the records of the messaging database or relationships thereof.

[0054] Referring to FIG. 8, a screenshot of a GUI 800 for adding and/or editing a mobile wireless device identifier (e.g., phone number) is shown, according to an exemplary embodiment. Using GUI 800, a user may enter and associate a user's mobile wireless device identifier with a priority level (or levels). A priority number may be chosen from field 802 and a mobile wireless device identifier may be entered or edited by a user in field 804. Furthermore, a name of a user of the mobile number, other contact information and/or other metadata may be entered or edited by a user in field 806.

[0055] According to various exemplary embodiments, many different mobile devices may relate to one priority number and/or many different priority numbers may relate to one mobile device. It should be appreciated that GUI 800 could be modified to accommodate entries for setting up and/or editing many-to-one, one-to-many, and many-to-many relationships. A save button 808 is provided to save changes or updates to fields 804 and 806, and a cancel button 810 is provided to cancel changes or updates. [0056] Referring to FIG. 9, a screenshot of GUI 900 that may be generated by server 130 is shown, according to an exemplary embodiment. GUI 900 may be generated using data from messaging database 405. For example, GUI 900 is shown to include a priority ID 902, a priority number 904, a mobile number 906 associated with priority number 904, a name 908 associated with mobile number 906, and a field 910 to determine if the priority is active or not. GUI 900 includes an add button 912 to add new information and a save button 914 to save any changes made to any fields by the user. Any of the fields on GUI 900 may be directly edited.

[0057] According to other various exemplary embodiments, user interfaces may be generated by the system that allow users to view queues of unsent messages, to delete queued messages, to set numbers of attempts for sending messages, to set timeout values for receiving confirmations or responses to messages, to associate events with priorities, to associate events with contacts, to associate events with mobile wireless device identifiers, to group mobile wireless devices, to group contacts, to group events, to group priority numbers, etc. It should be noted that any GUI may be generated to facilitate configuring or setting up any of the relationships and/or settings described in the present application. [0058] According to various exemplary embodiments, a plurality of supervisory controllers may be used by a server configured to sending a text message regarding one or more building automation system devices. Such a server may be configured to route received messages to proper mobile wireless devices based on the supervisory controller from which the message originated. Further, priority information associated with events may be used to determine whether to send a text message to a person responsible for an individual supervisory controller or a person responsible for multiple supervisory controllers (e.g., an enterprise level manager or technician).

[0059] While the exemplary embodiments illustrated in the figures and described herein are presently preferred, it should be understood that the embodiments are offered by way of example only. Accordingly, the present application is not limited to a particular embodiment, but extends to various modifications that nevertheless fall within the scope of the appended claims.

[0060] The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system.

[0061] The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., the server and/or processing circuit may be local and housed in one casing, distributed, networked, multi-processor, etc.). For example, the position of elements may be reversed or otherwise varied and the nature or number of discrete elements or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.

[0062] Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. When information is transferred or provided over a network or another Communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a machine, the machine properly views the connection as a machine-readable medium. Thus, any such connection is properly termed a machine-readable medium. Combinations of the above are also included within the scope of machine -readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

[0063] Further, embodiments within the scope of the present disclosure may also include a first server computer having a software delivery module (processing circuitry, memory, and/or computer code) configured to transfer software code to a second server (e.g., server 130) via a wired and/or wireless communications link, the software code configured to program the second server (e.g., a processing circuit, memory and/or computer code thereof) to conduct the activities described in the present disclosure. [0064] It should be noted that although the figures may show a specific order of method steps, the order of the steps may differ from what is depicted. Also two or more steps may be performed concurrently or with partial concurrence. Such variations will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.

Claims

What is claimed is:

1. A method for sending a text message regarding one or more building automation system devices to a mobile wireless device, the method comprising: at a server, receiving data about the one or more building automation system devices; determining whether to send a text message relating to the received data, the determination based on priority information associated with the received data; formatting the text message according to a text messaging protocol compatible with the mobile wireless device; and sending the text message to the mobile wireless device.

2. The method of Claim 1 , wherein sending the text message to the mobile wireless device comprises transmitting the text message to a communications network.

3. The method of Claim 2, wherein the communications network is a mobile telephone communications network, the mobile telephone communications network compatible with one or more of a global system for mobile communications (GSM) standard, a personal communications service (PCS) standard, and a code division multiple access (CDMA) standard.

4. The method of Claim 1 , wherein the text messaging protocol is a short message service (SMS) protocol or a multimedia messaging service (MMS) protocol.

5. The method of Claim 1 , further comprising: determining which of a plurality of possible mobile wireless devices should be sent the text message based on the priority information.

6. The method of Claim 1, further comprising: displaying a graphical user interface (GUI) to a user, the GUI configured to allow the user to change contact information for the mobile wireless device.

7. The method of Claim 6, wherein the contact information is at least one of a phone number, a mobile subscriber identifier, an e-mail address, and a user name.

8. The method of Claim 1 , wherein the received data comprises an event identifier about the one or more building automation system devices.

9. The method of Claim 7, further comprising: accessing a database and looking up the priority information based on the event identifier received with the data, wherein the database is configured to relate possible event identifiers to the priority information.

10. The method of Claim 1 , further comprising: selecting the mobile wireless device from a plurality of mobile wireless devices, the selection based upon a relationship stored in the database between contact information and the priority information associated with the received data about the one or more building automation system devices.

11. A server for communicating a text message relating to one or more building automation system devices to a mobile wireless device, comprising: a communications interface configured to communicate with the mobile wireless device over a wireless network; and a processing circuit configured to receive data about the one or more building automation system devices and to determine whether the text message should be sent based on priority information associated with the received data; and wherein the processing circuit is configured to format the text message according to a text messaging protocol compatible with the mobile wireless device and to send the text message to the mobile wireless device.

12. The server of Claim 11 , wherein the wireless network is a mobile telephone communications network, the mobile telephone communications network compatible with one or more of a global system for mobile communications (GSM) standard, a personal communications service (PCS) standard, and a code division multiple access (CDMA) standard.

13. The server of Claim 11 , wherein the wireless network is at least one of a ZigBee network, a WiMax network, and a WiFi network.

14. The server of Claim 11 , wherein the text messaging protocol is a short message service (SMS) protocol or a multimedia messaging service (MMS) protocol.

15. The server of Claim 11 , further comprising: a graphical user interface (GUI) module configured to present a GUI to a user, the GUI configured to allow the user to change contact information for the mobile wireless device.

16. The server of Claim 15, wherein the contact information is at least one of a phone number, a mobile subscriber identifier, an e-mail address, and a user name.

17. The server of Claim 11, wherein the received data comprises an event identifier about the one or more building automation system devices.

18. The server of Claim 11 , further comprising: a database configured to store the priority information and to relate possible event identifiers to the priority information; wherein the processing circuit is further configured to lookup the priority information based on the event identifier received with the data.

19. The server of Claim 18, wherein the database is further configured to relate different contact information with different priority information and wherein the mobile wireless device is one of a plurality of possible mobile wireless devices; wherein the processing circuit is configured to send the text message to the mobile wireless device based upon the contact information related to the priority information associated with the received data about the one or more building automation system devices.

20. The server of Claim 11 , wherein the data about the one or more building automation system devices is information about at least one of: a parameter sensed by the building automation system device, a status for the building automation system device, data stored in memory of the building automation system device, data stored in a supervisory controller of the building automation system device, and a second building automation system device attached to the building automation system device.

21. A machine-readable medium for programming a computer to send a text message regarding one or more building automation system devices to a mobile wireless device, the medium comprising processor executable instructions for: receiving data about the one or more building automation system devices; determining whether to send the text message relating to the received data, the determination based on priority information associated with the received data; formatting the text message according to a text messaging protocol compatible with the mobile wireless device; and sending the text message to the mobile wireless device.

22. A first server comprising a software delivery module configured to transfer software code to a second server via a wired and/or wireless communications link, the software code configured to program the second server to conduct the steps comprising: at the second server, receiving data about the one or more building automation system devices; determining whether to send a text message relating to the received data, the determination based on priority information associated with the received data; formatting the text message according to a text messaging protocol compatible with the mobile wireless device; and sending the text message to the mobile wireless device.