CN1305611B - System and method for object-oriented control of various electromechanical systems using computer network - Google Patents

Abstract

A control system methodology uses object-oriented software to integrate multiple control systems into a common object model. Object-oriented techniques are used to construct distributed Java-based applications in a multi-vendor open system environment for use in controlling and monitoring systems of varying size and configuration. The system provides both a browser client (101) (running on a Java-enabled browser) and a server client (121). The present invention has multiple stations: a Web BAS Server (110), a Network Processor (NP) (111), and a Field Controller (FC) (112). The NP and FC are preferably Java Virtual Machines implemented in a plug-in Java Modular Environment. Information is brought into a common object model and made available throughout the system. A custom programming language based on Java is provided for object creation, with access to objects controlled through a multi-level security protocol. Data flow is governed by a real-time information synchronization manager.

Description

System and method for object-oriented control of various electromechanical systems using computer network

This application claims the benefit of US Provisional Application Serial No. 60/085,539, filed May 15, 1998, the entire disclosure of which is incorporated herein by reference.

A part of this disclosure contains copyright claimed by the applicant. The applicant has no objection to the duplication of these contents in the reproduction of this application document or any patent that may issue this application, but reserves all other rights to these copyright contents.

The present invention generally relates to systems and methods for controlling and monitoring various systems using modular object-oriented control software running in local controllers associated with the systems being controlled and utilizing a communication network such as the Internet to centralize control, monitor and update it. These systems and methods are especially useful in building block automation system (BAS) applications.

In the past, control systems such as building block automation systems were typically either a single vendor's proprietary solution or a complex integration of separate systems. The industry has worked to develop standards so that such systems can be more efficiently integrated, but there is no true unified approach yet.

The release of the BACnet/LonMark ^TM fieldbus (fieldbus) communication standard for building block automation systems has caused a rethinking of the building block automation system architecture, which may revolutionize the control scheme landscape. Traditional purpose-built building block automation architectures work well, but they are expensive to design and install, cumbersome to reconfigure, and typically require extensive software for facility business integration of stand-alone applications. In contrast, under the distributed BACnet/LonMark fieldbus architecture, logic processing is encapsulated in autonomous multi-vendor modules that communicate with each other through standard software to coordinate building block control problems. However, in known building block automation architectures, the external interface characteristics of components added to the control system must be entered into a database representing the external interface characteristics of the components before the BAS can effectively control the new components.

Distributed control in this manner is expected to minimize installation wiring, optimize control software, reduce operation/maintenance costs, and simplify system expansion. In today's globally competitive marketplace, users need fieldbus flexibility, reusability, and effective building-block control solutions to respond quickly to changes in facility management operations.

Advances that have occurred in other computing fields but have not yet been applied in a satisfactory manner to building block automation systems. For example, various computer system standards have been developed that streamline the cost and development requirements of program systems. The main technologies include object-oriented software, namely Java ^(TM) Virtual Machine (JVM) and JavaBeans ^(TM) .

Object-oriented programming provides a new way of modeling real-world entities more directly with software building blocks that better match the real world than conventional programming mechanisms. This new software paradigm is increasingly affecting the software world in the same way that microprocessors have affected hardware design and functionality.

In object-oriented programming, applications are created from independent building block modules (objects). Rather than reinventing the wheel every time a new program is created, application engineers can take previously written application modules from a library and simply plug them in. By using object libraries, developers focus on wiring together the appropriate objects and writing any custom objects their application requires. Custom objects can in turn be added to the library for later reuse.

Networking standards have also evolved in an effort to streamline the cost and development requirements of system integration. Major technologies developed in the building block automation industry include the American Society of Heating, Refrigerating, and Air-Conditioning Engineers (ASHRAE) Assembly and Control Network (BACnet ^™ ) and the ECHELON LONTALK ^™ protocol (developed by Echelon Corporation, Palo Alto, CA).

At the same time in the computer industry efforts were being made to develop communication standards, although again these standards have not been applied in any really efficient way to the particular problems of building block automation. For example, the purpose of the Internet/www/Java/CORBA standard is to provide the information that users want, regardless of what kind of program is used, what kind of machine it runs on, or what format the information is in.

Through the hypertext system, Web users can select and view information from all over the world. However, the Web lacks real interactivity—that is, real-time, dynamic, and visual interactions between users and applications. Java brings this missing interactivity to the Web. With a Java-enabled Web browser, users can encounter animated and interactive applications.

Efforts to implement real-time control systems over the Internet have generally been unsuccessful due to the variability in packet delivery times and the lack of guaranteed delivery over the Internet.

The conclusion is that historically control systems have been largely based on the proprietary technology of a single manufacturer. Although efforts have been made to standardize these structures, there has been only limited success. The present inventors believe that there is a need in the field of control systems for a highly comprehensive standard that integrates a Java-based common object model particularly suited for building block automation applications and provides centralized control and monitoring utilizing communication network standards such as the Internet.

Accordingly, it is a general object of the present invention to provide a control system and method using object-oriented software that integrates BACnet, LonMark, CORBA, Java and Internet systems into a common object model. The present invention in its preferred embodiment utilizes object technology as the key to building truly distributed applications in a multi-vendor open system environment supporting multiple industry standards. The architecture of BACnet/LonMark/Internet/CORBA is combined in the present invention and Java object-oriented software concepts are applied to realize distributed control and information management. Messages (events) are passed between autonomous modules that employ object technology to encapsulate both data and functionality. These functional objects are copied for reuse and clustered to form more complex functions that build on the work of other objects. The navigation tool of the Web BAS server provides an overall view of the process being controlled by the respective master fieldbus module and provides an unrestricted flow of information.

Another general object of the present invention is to provide a control system and method in which both pre-defined objects and user-defined and established objects exist in a single control system. Provides a custom programming language for object modification, creation and management. A set of predefined objects is also provided.

Yet another general object of the present invention is to provide a control system and method that maintains the integrity of system data in a distributed system and that distributes system data on the distributed system as needed by using archiving techniques and synchronization techniques. The master copy of each piece of data is preferably kept on a single virtual machine, and a synchronized and asynchronous caching system is used to ensure that objects in the control system have access to current system data. System data is archived to provide persistence.

Yet another object of the present invention is to provide a control system and method in which object properties associated with a component are dynamically updated to reflect the external interface characteristics of the component. To this end, the components of the control system are queried for their external interface properties and their associated object properties are updated accordingly. This provides management of components without necessarily requiring pre-programmed dedicated external interface representations.

These and other objects of the present invention will become apparent upon a study of this specification, including the appendices and drawings.

Figure 1 is a preferred overall architecture of an object-oriented control system consisting of clients, workstations, external components and remote hosts;

Figure 1A shows different types of workstations of the object-oriented control system.

Figure 2 shows an alternative embodiment of an object-oriented control system configuration in the form of a field controller system, wherein a client accesses a single field controller monitoring a LonMark ^™ fieldbus;

Figure 3 shows an alternative embodiment of an object-oriented control system configuration in the form of a small Web BAS server system, where clients access a single Web BAS server monitoring the LonMark ^™ fieldbus;

Figure 4 shows a preferred embodiment of an object-oriented control system configuration in the form of a two-stage system where the Web BAS server directly monitors the combination of network processors, field controllers and BACnet components;

Figure 5 shows an alternative embodiment that also provides an object-oriented control system configuration in the form of a three-level system, where the Web BAS server directly monitors the network processors, which in turn monitor the site controllers;

Figure 6 shows an alternative embodiment of an object-oriented control system configuration in the form of a distributed system, where a collection of large or small systems is connected and monitored by a remote host;

Figure 7 illustrates a preferred embodiment of a persistent and real-time information synchronization manager for an object-oriented control system;

Figure 8 outlines the object class hierarchy of an object-oriented control system;

Figure 9 illustrates communication between workstations and clients in a preferred embodiment of the object-oriented control system;

Figure 10 further illustrates communication between workstations and clients in a preferred embodiment of the object-oriented control system; and

Figure 11 illustrates the architecture of a preferred embodiment of an object-oriented control system.

A presently preferred embodiment of the object-oriented control system 100 provides a solution for distributed control of systems of various sizes and configurations. The overall architecture including client 101, workstation 102 (see FIG. 1A) and external components 105 is preferably set up as shown in FIG.

The client 101 in this system includes a browser client 120 and a full client 121 . Clients 101 provide access to the system through the Intranet and the Internet. Client 101 relies on server software on a workstation to provide such access. Browser client 120 provides full user access to the system from any approved Java enabled browser. Full Client 121 provides the full capabilities of Browser Client 120 plus application enabler tools.

Each workstation 102 is the heart of the object-oriented control system 100 . Workstation 102 includes Web BAS Server (WBS) (110), Network Processor (NP) (111) and Field Controller (FC) (112). Workstation 102 typically fulfills one or more of three functions.

1. Each workstation 102 integrates external components 108 into the system. WBS110, NP111 and FC112 can achieve this role.

2. Each workstation 102 monitors other workstations 102 . In this role workstations 102 integrate the workstations they monitor into the system. Monitoring also includes requirements such as monitoring and routing. WBS110 and NP111 can achieve this role.

3. Each workstation 102 can host the local system. In this role they provide continuous backup of all configuration information. WBS 110 and FC 112 do this.

In the integrator role, the workstation 102 builds information into objects so that the information is available to the rest of the system with predictable behavior. In its monitoring role, workstations 102 monitor other workstations 102, including checking system integrity and routing data and event information between workstations.

When acting as a master, workstation 102 is defined as the primary master of the system. The primary master provides a backup of all configuration information.

External components 105 include any system-compatible components that are not directly controlled using downloadable Java-based objects. Two specialized types of external components 105 are BACent ^™ components 123 and LonMark ^™ components 122, which comply with the various standards promulgated by the industry for these components. Remote host 108 provides some of the functionality of the system somewhere other than where the control system is located. Remote host 108 can connect to the job through any communication link that supports TCP/IP, including a serial modem.

The workstations 102 communicate with each other as illustrated in FIGS. 9 and 10 . Utilize Hypertext Transfer Protocol (HTTP) and Java Remote Method Invocation (RMI) to communicate through control network 106 each browser client 120 and each full client 121 and each workstation 102, including Web BAS server 110, network processor 111 and Field controller 112 . The Web BAS server 110 and the field controller 112 also include an object database 150 for accessing objects of the object-oriented control system 100.

A preferred architecture of an object-oriented control system 100 for various users is illustrated in FIG. 11 .

In order to allow a distributed control system to manage LonMark ^™ components 122, the component-specific type's external interface must be expressed in the object properties associated with each LonMark ^™ component 122. External interface information may include, for example, the set of network variables for that particular component type. In the past, in order to add each new LonMark ^™ component 122 to the system or to change the external interface of the LonMark ^™ component 122, the user of the distributed control system was required to first program the external interface information or input it into the LonMark ^™ component 122 The associated object properties cause the distributed control system to manage the LonMark ^™ components 122, which causes delays in bringing new or modified external components 105 online and controllable by the distributed control system. Object-oriented control system 100 overcomes this limitation by providing dynamic LonMarkr ^™ component updates to object properties associated with LonMark ^™ component 122 to reflect the external interface characteristics of the component. To accomplish this, the object-oriented control system 100 queries the LonMark ^™ components 122 for their external interface characteristics. The active corresponding object properties associated with the queried LonMark ^(TM) component 122 are then updated and configured based on the information received in response to the query. This dynamic component external interface update capability thus provides management of LonMark ^™ component 122 without requiring the user to first preprogram a specific external interface representation, which saves time and reduces the possibility of errors in configuring the properties of LonMark ^™ component 122 objects .

The workstation 102 of the network processor 111 and field controller 112 type is preferably implemented as a Java virtual machine (JVM), which can be programmed using Java objects dedicated to system control attached to the NP 111 and FC 112 . These JVM programming can be adjusted in real time by adding, removing, or reconfiguring connections between objects. Each object is preferably implemented using Java and corresponds to a specific control function, and is connectable to other objects using a predetermined set of links. For example, available objects may include function generators, analog and digital inputs and outputs, multi-state outputs, alarm objects, available workstation service objects, and user-programmed custom objects. Various of these objects can be combined in any desired manner to generate a virtual programmed controller for a component or group of components interfaced with the associated JVM.

In a presently preferred embodiment, predefined objects and user-defined objects coexist in a single object-oriented control system 100 . To facilitate object creation, a custom programming language is preferably provided based on the Java language, but it is both customized and simple for control applications. The custom programming language is used to specify programming instructions for each program node of the object-oriented control system 100 . In addition, a programming editing program as a development tool is also provided for users to program each program node with the customized programming language.

In this specification and the appended appendices, the term "node" is used to refer to some objects provided by the object-oriented control system 100 and their properties. It should be understood that in the context of the presently preferred embodiment of the object-oriented control system 100, a "node" is an object. The processing and functional behavior of a node is determined by its associated set of programmable properties. Most of the software applications that make up the object-oriented control system 100 are provided in the form of nodes.

A set of object properties is provided by the object-oriented control system 100 . A set of predefined objects is provided by the object-oriented control system 100 .

In addition, the object-oriented control system 100 provides calendars, schedules, and logs by means of which the user can control the timing and execution of commands and software applications of the system. The calendar allows specifying those days that should be treated specially for system operation. Schedules allow some program commands to be executed at specific times. Logs are a set of nodes and services that collect system information into buffers to share information throughout the object-oriented control system 100 .

Logs are stored persistently in a database that supports intelligent archiving of information. Specific types of logs include, but are not limited to:

1. Control logs, used to collect and store numerical state values and output string values. Control logs are implemented in the control engine to collect information output from other nodes.

2. Service logs for login errors and changes made by the operator. The service log occurs once per workstation 102 .

3. External logs, which contain log information obtained from systems other than the object-oriented control system 100 .

Additionally, the "Log Service" software application provides web-based access to all logs via Hypertext Transfer Protocol.

Access to objects or nodes is preferably controlled by a multi-level security protocol (preferably, 8-level protocol), and objects can be grouped into "repositories" which facilitate the display of different levels of detail. That is, a person who monitors, controls, or programs the operation of an object can display linked objects at various levels of detail according to immediate needs. Several features are provided to control who has access to the object-oriented control system 100 and who can access and modify individual objects, including but not limited to requiring an original password to log in and programmable security groupings for each object.

More specifically, the security model requires each user entering the system to have a valid password. Permission can be assigned or denied to each user object at any of 8 access levels (security permissions) for 8 security groups. These security groups are independent of each other and their significance is only partial. Any combination of these 8 security groups can also be assigned to each object. In this way many different access definitions can be defined simultaneously.

Each user object defined in the database has a username and password required to enter the system. Permission to any of the security permissions can be granted or denied to individual user objects within each of the 8 security groups. There are 8 security groups defined for the system. They are independent of each other and their meaning is local. Any combination of these 8 security groups can be assigned to each object through the property security group. By default, each object is assigned security group 0 (normal). In this way many different security permissions can be defined simultaneously. The default security groups are as follows:

0 = normal

1 = hvac (heating, ventilation and cooling)

2 = Confidential

3 = lifetime safety

4 = group 4

5 = group 5

6 = group 6

7 = Group 7

Security permissions are fundamental rights granted to individual users. These include, but are not limited to: Operator Read, Operator Write, Admin Read, Admin Write, Standard Commands, Acknowledgment Warnings, Emergency Commands, and Admin Commands.

A user's access rights to an object are determined by the combination of his rights to each group, which are checked or indicated in the object's security group properties. Additionally, if a user has rights to a container, certain rights apply to its children. If a user has "operator read" permission on a storage, the user can see the children from the workspace perspective. If a user has "administrator write" permission on a storage, the user can perform many operations on the storage, including connecting, disconnecting, copying, duplicating, deleting and renaming.

An object's security is determined by a combination of the security groupings that the user has assigned to the object, and each of the object's properties that are specified by operator or administrator properties. Users can assign any combination of the 8 security groups defined by the system to any object. This is achieved through feature security groups, by default security group 0 (normal) is assigned to each object.

Each property in the system is identified as either an operator property or an administrator property. This determines what security permissions a user must have in order to view or edit an object's properties.

Operator security permissions are defined as the functionality required by a system operator who may only need to view or edit the lowest level characteristics of an object.

Administrator security permissions are defined as the capabilities required to configure the system. This person may need to view or edit all features of the system. "Administrative Editing" includes creating objects, connecting objects, and editing properties.

The object-oriented control system 100 provides users with a service of defining new users through user objects. The user service ensures that user security groups and permissions are mandatory for each user. Creates a new user object for a new user with a default username and password. The user can change his password. A user or object can be assigned one or more security groups. Security permissions may be changed for individual users.

Objects can be dynamically linked together using one of the following links, but not limited to: "General", "Triggered", "LanTalklocal", "LonTalkNetwork", "UI", "Mixed", or "External".

In addition, the object-oriented control system 100 utilizes BACnet ^(TM) commands to prioritize actions performed by mediation software applications on objects or nodes. ^BACnet (TM) command prioritization is achieved by assigning different priorities to applications that can command a particular object or node and storing that specific priority at that node as an object property of that node. Each node or object acts on commands received from the software application according to its command priority.

Client 101, server 110 and network processor 111 are preferably implemented using a personal computer, such as an Intel Pentium( ^TM) based personal computer, running Microsoft's Windows 95 or Windows NT operating system. The site controller 112 can be implemented with a limited-function, inexpensive single-board computer that can run as a Java virtual machine. For example, so-called network computers can be used for this purpose.

The architecture of the present invention supports many different system configurations. Some of the more common configurations include field controller systems (Figure 2), small Web BAS server systems (Figure 3), two-stage systems (Figure 4), three-stage systems (Figure 5), and distributed systems (Figure 6).

Referring to FIG. 2, the field controller system is a configuration of the present invention in which each client accesses a single field controller 112 monitoring a LonMark field bus 107 to which multiple LonMark components 122 are connected.

Fig. 3 shows a small-scale Web BAS server system, wherein each client computer 101 (or browser client computer 120 or full client computer 121 or both) visits the Web of a LonMark Fieldbus 107 that a plurality of LonMark parts 122 connections of single monitor BAS server 110. A two-stage system as shown in FIG. 4 is a system configured to directly monitor any combination of network processors 111, site controllers 112, and BACnet components 123 with Web BAS server 110. As shown in FIG. 5 , it is also possible to set up a three-level system in which the WebBAS server 110 directly monitors the network processor 111 which in turn monitors the site controller 112 . Finally, FIG. 6 shows an alternative embodiment of configuring the object-oriented control system 100 as a distributed system comprising one remote host 108 and wherein a collection of large and small systems are connected and monitored through the remote host 108 using a modem 109 .

The system includes an architecture for building, deploying and running systems that automate the many services necessary to successfully run and manage office, commercial, healthcare, educational and industrial facilities.

A persistent and real-time information synchronization manager (PRISM) 200, preferably at each workstation 102, manages the flow of data in the system, which is critical to the various purposes of the distributed object-oriented control system 100. By employing archiving and synchronization techniques as illustrated in FIG. 7 , PRISM 200 maintains system data integrity throughout object-oriented control system 100 . Data related to the object-oriented control system 100 is categorized into system data, Java Application and Control Engine (JACE), nodes, and properties. In addition, each piece of data in the object-oriented control system 100 is also classified according to its life cycle. Ephemeral data exists only during the lifetime of its host virtual machine (VM). Persistent data exists beyond the life of its host VM and survives a power loss or shutdown. The virtual machines that appear in the object-oriented control system 100 include, but are not limited to: a full user interface 206 related to the full guest machine 121, a browser user interface 208 related to the browser client 120, Taz 210, and one or more JACE212. Archive permanent data by storing it in non-volatile memory. In a preferred embodiment, flash memory 204 and disk 202 are utilized as non-volatile storage media (ie, "persistent storage") to store archived persistent data. JACE212 maintains a master copy of related temporary and permanent data. Synchronized and asynchronous caches are used under the control of PRISM 200 to ensure that objects access current system data. Each virtual machine has at least one cache that contains all the data that the virtual machine needs. The cache is maintained by a coherency method in which the caches of the virtual machines are consistent with or updated to the caches of their monitoring workstations 102 . The workstations 102 then reconcile their caches with each other. In a presently preferred embodiment, checksums are used to determine inconsistencies in current data. Each monitor workstation 102 obtains the current virtual machine cache data for each node stored at a monitor workstation, and then computes a checksum over its cache contents and the cache data received from the queried virtual machine. If the checksums do not match, an inconsistency is detected, in which case the monitoring workstation 102 takes steps to correct the problem, steps including but not limited to: updating its cache to reflect the updated data, performing a timestamp comparison to select the updated data Or give an alarm or error indication.

In the presently most preferred embodiment, the object-oriented control system 100 includes multiple Web BAS servers 110 rather than a single Web BAS server 110, each Web BAS server 110 having its own persistent data database. In this presently most preferred embodiment, object accesses persistent data regardless of the physical location of the specific Web BAS server 110 where the data is archived. A workstation 102 can communicate with another workstation 102 regardless of whether the other workstation 102 is also connected to its local Web BAS server 110.

As previously stated, to support the wide variety of requirements for objects in all types of installations, the preferred embodiment of the present invention provides a Java modular environment that allows software modules to be inserted anywhere in the control system. Objects can be placed where they are needed in this way and provide the best real-time performance.

The system preferably consists of Java class files to implement the system in a platform-independent manner so that the system can be delivered on any supported platform. The core class hierarchy according to the present invention provides a system with nodes and platforms that allow this flexibility. This layer is supported by a method of flexible configuration of drivers for different interfaces and protocols for different platforms. In addition to this core class hierarchy, user objects are organized hierarchically so that they inherit behavior hierarchically and behave predictably.

The hierarchy established in a preferred embodiment is shown in FIG. 8 .

In a presently preferred embodiment, a user of the object-oriented control system 100 can create and manipulate objects associated with a variety of object types, including but not limited to the following object types: controls, applications, user interfaces, storage, LonWorks ^TM , BACnet, management and services.

In addition, the Control Object type includes the following subtypes: Analog Input, Analog Output, Binary Input, Binary Output, Compare, Logic, Loop, Math, Function Generator, and Adder.

In addition, the application object type includes the following subtypes: schedule, calendar, program, analog log, binary log, and integer log.

In addition, the user interface object type includes the following subtypes: Bar Graph, Boolean Image, Boundary Image, Damper, Fan, Hot Spot, Image Spectrum, Text, and Time Graph.

In addition, storage object types also include hybrid subtypes and generic subtypes.

In addition, the LonWorks ^TM object type includes the following subtypes: Snvt Switch Multiplexer, Snvt Switch Demultiplexer, DemoFcu, Leviton Switch, Leviton Switch 481, Action Tool AO, Action Tool Al, Action Tool DO, and Local Lon Node .

In addition, the BACnet object type also includes the following subtypes: component, analog input, analog output, binary input, and binary output.

In addition, the service object type also includes the following subtypes: control engine, UI engine, user access, inter-workstation connection, HTTPD service, web text, web view, media, program debugging, dial-up, Lonworks, Lon communication, network variable polling Schedule, Network Variable Manager, BACnet Server, BACnet Client, BACnet Polling, BACnet Transmit, BACnet Network, BACnet Ethernet, Error Archiving, Error Forwarding, and Mail.

Additionally, managed object types include user subtypes.

The purposes and uses of these objects provided by the object-oriented control system 100 include, but are not limited to, the general purposes and uses associated with the various object types and subtypes.

To operate acceptably in a real-time environment, the control engine for the objects must operate predictively and also provide the user with control over the execution order of the objects. The present invention provides this capability. In a presently preferred embodiment, object properties are set to specify the frequency and order of execution. In a presently most preferred embodiment, five different execution frequencies can be specified. Individual execution frequencies can be tuned by editing the associated object properties over a number of 100 milliseconds. In a presently most preferred embodiment, three different execution sequences can be specified.

To provide remote locations with information about field operations, the system provides a programmable mail service to send real-time information to remote locations whenever programmed to do so.

The system sets all of its object properties as elements accessible as standard data types. This allows user and program objects to efficiently use any feature. These properties are then exposed as Extensible Markup Language (XML) for manipulation by other tools.

The system needs a means to allow users to create custom objects for certain applications. To meet this requirement a scripting language is defined which exposes the system under a program object for user access and control. The language is simple, uses standard object linkage, provides access to libraries and provides a complete debugger.

The invention also applies the hybrid document paradigm of the Internet to control the system in novel ways. It provides uniform visibility of resources through commonly used Uniform Resource Locators (URLs). These resources are linked together to allow navigation to establish a hyperlinked web of resources.

The system manages resources to ensure accessibility and availability. Resources in the system include class files, executables and DLLs, media, documents, applications, property files, databases and logs, and third-party software.

The control system must be usable by a wide range of personnel, including facility managers, application engineers and information specialists. Typically, the system provides a novel and unique control interface including a custom browser interface for accessing objects and information. The interface includes workspace display, workspace editor, property display, link display, and help feature. Through this control interface the user can issue commands to any object or to the system and change operating characteristics.

In order to fold the information management and real-time expert control system into a common workstation, the BAS architecture according to the present invention is simplified and provides the user with a single point of access to both information and control. The Web BAS server platform provides a common graphical user interface based on Java Web browser technology for all facility management information and building block control applications. In addition, the open unified software environment provides Internet-compatible configuration tools via any industry-standard browser for information/fieldbus network and control system applications.

The Web BAS server platform disclosed herein is the BAS industry's first software technology to integrate disparate BACnet, LonMark, and Internet/CORBA standards into a common object model application environment through a Java-enabled Web browser interface. This embodiment also integrates network management tools to support BAS field controller channels on the planning, design, configuration, installation and maintenance of BACnet/LonMark/Internet/CORBA system networks.

The very scalable Web BAS server software can be used in small buildings such as a single customer front end platform directly attached to the BACnet/LonMark fieldbus. On large BAS installations, the Web BAS server can be configured to monitor many Ethernet-connected network processors and support an unlimited number of remote Web browser operator interface users. For corporate users, the Web BAS server can be configured to integrate the BAS architecture into the IBM corporate information infrastructure and/or the Groupe Schneider industrial/energy systems architecture.

A salient feature of the present invention is the improvement of the BAS controller module (network processor). The memory, speed, and throughput of traditional dedicated BAS controller platforms are too small to support multiple building block service applications. Thus, various applications such as HVAC (heating, ventilation, and air conditioning) and access control are provided using separate controllers, which breaks down the user's actual problem into solvable independent components but it is not a comprehensive solution . This results in ever-increasing installation costs and minimal integration between incompatible stand-alone building-block service solutions.

These limitations are overcome in the present invention by connecting BAS controller processor technology to a cooperating BACnet/LonMark fieldbus. To take advantage of this new high performance technology, the present invention uses application development capabilities that exploit available processing power. Thus, integration and multiple building block service applications can be realized by the same computing platform.

In order to overcome the limited application development capability of current BAS controllers, the network processor in the present invention adopts Java application environment based on object-oriented analysis, design and programming. NP uses a powerful Java object/rule engine based on Sun's Java software technology to integrate multiple high-level building block service applications and support multi-vendor fieldbus solutions. Examples of network processor applications include global alerting, global scheduling, trending/data collection, diagnostic services, and demand limiting/energy management for integration into common building-block service offerings.

Preferably, the network processor (NP) object software environment is set up on the embedded controller hardware platform. The NP platform package supports LonMark fieldbus from multiple manufacturers and also provides Ethernet peer-to-peer networking (see Figure 1-BACnet/L0nMark/Internet Architecture) structure for other NP and Web BAS servers.

As shown in the figures and appendices, the present invention provides three embodiments of a field controller (FC) platform. The FC platform preferably uses a 32-bit processor and can optionally be connected to the BACnet/LonMark fieldbus cooperating with each other through an Echelon coprocessor. These platforms employ real-time operating systems that support Java's object/rule engine for applications. The Web BAS server configures the FCs on this fieldbus or via the FC's local RS232/modem port or video modem interface.

The first FC components support locally connected junction box I/O modules manufactured by Groupe Schneider. Applying this integrated design approach to advanced industrial and commercial controllers is very flexible and cost-effective. BACnet/LonMark object/rule engine can use any local input/output data or any fieldbus component data under its powerful application environment.

The second class of fieldbus-attached 32-bit field controllers does not support locally connected I/O, but includes an integrated inexpensive programmable operator interface and BACnet/LonMark object engine. A Web BAS server configuration tool programs this flexible operator interface with control and data access to any node component on the fieldbus network.

A third embodiment of the site controller assembly integrates a video cable modem to provide low cost Internet connectivity to small building blocks for remote control and monitoring of the Web BAS server.

In order to simplify integration and use, the various operating elements of the system are modeled as objects. This includes user specification, network management, network control, real-time control, and component objects.

As another feature of the present invention, in order to avoid the relatively high cost of the client's non-stop connection to the Internet or long-distance telephone calls from the server to the client, the server employs a simple dial-in notification mechanism to enable the client to reopen connection to the server. In operation, the server dials the modem connected to the client and terminates the call before the client answers. The client recognizes this as the server requesting contact. In response to the call the client dials its local ISP which has a low price monthly service account. The client then establishes a connection with the server on the Internet. This mechanism avoids per-communication or per-minute billing by limiting access charges to the monthly fee charged by the ISP.

Thus, a control system and method is shown that utilizes object-oriented software to integrate BACnet, LonMark, CORBA, Java, and Internet systems into a common in the object model. The control system and method of the present invention provides predefined objects and user-defined objects in a single control system. Maintain and distribute system data integrity and continuity by adopting archiving and synchronization technologies. Dynamically update properties associated with a component to reflect the component's external interface characteristics.

This application incorporates by reference the US utility application entitled "System and Method for Object-Oriented Control of Various Electromechanical Systems Using a Computer Network" by Gerald Frank et al., filed May 14, 1999.

Claims (7)

1. OO control system comprises:

A plurality of client computer are used to provide the visit to this OO control system, control and supervision by electric network;

A plurality of external components, they can not be directly by utilizing Downloadable object control based on Java;

A plurality of workstations are used to utilize Common Object Model that described external component is integrated into this OO control system, the main control computer that is used to monitor other workstation He is used to serve as local system, and wherein main control computer provides the lasting backup of all configuration informations; And

A flexible and open architecture, it supports the multiple different configuration of described client computer, external component, communication protocol and workstation, wherein, described communication protocol comprises first agreement that is used for described electric network and second agreement that is used for communicating with described external component;

A real-time Sync Manager is used to regulate carrying out in order and timely of a plurality of tasks;

A plurality of user-defined objects;

Described object and described characteristic are set up and revised to an object apparatus for establishing to allow the user according to a plurality of described object types;

A multilevel security equipment;

The predefine object of a plurality of and described user-defined object coexistence;

A lasting and real-time information synchronization manager, it is by adopting the integrality of filing and keeping system data synchronously on whole OO control system;

A Control Engine device is used to provide the order of the described object of predictable execution; And

A mail service device able to programme is used for sending the email notification that contains real time data to remote site,

Wherein, described object has a plurality of plant characteristics, a plurality of object type and a core classes level.

2. the external interface plant characteristic that the described OO control system of claim 1, wherein said object apparatus for establishing also are used for dynamically upgrading or interpolation is relevant with described external component.

3. the described OO control system of claim 1 also comprises a distance host, is used to allow from physically different with other member of this OO control system position visits, control and this OO control system of supervision.

4. OO control system comprises:

Access means is used to each object that allows the user to use electric network control and monitor this OO control system;

Integrating device, this OO control system is utilized Common Object Model control and is monitored a plurality of external components by it, wherein, described integrating device is supported a plurality of communication protocols, second agreement that comprises first agreement that is used for described electric network and be used for communicating with described external component;

Supervising device is used to allow a workstation control and monitors other workstation, and it comprises the ability of the main control computer that serves as local system;

Synchronous device is used to regulate carrying out in order and timely of a plurality of tasks in real time;

New user object apparatus for establishing is used to allow the user to set up and revise object according to a plurality of object types;

The multilevel security device is used for disable access or revises some information relevant with certain object;

The Control Engine device is used to provide predictable object execution order; And

Mail device able to programme is used for sending the email notification that contains real time data to remote site.

5. method of using OO control system comprises:

Provide visit, control and supervision to this OO control system by electric network, wherein, described electric network is supported first agreement; And

Utilize a representative system information and make on this OO control system can both using system information Common Object Model, external component is integrated in this OO control system, wherein, described external component uses second agreement to communicate.

6. the method for claim 5 also comprises programming language foundation that utilizes customization and the object of revising OO control system.

7. the method for claim 5 also comprises:

Each object is grouped in the reservoir so that show the details of different levels;

According to core classes hierarchical organization object; And

By adopting the visit of multilevel security agreement control to object.

Images