Networked facilities management system

• US 5,522,044 A
• Filed: 01/21/1994
• Issued: 05/28/1996
• Est. Priority Date: 01/30/1990
• Status: Expired due to Term

• Current Assignee: Johnson Controls Technology Company (Johnson Controls International plc)
• Original Assignee: Johnson Service Company
• Inventors: Nesler, Clay G., Rasmussen, David E., Singers, Robert R., Decious, Gaylon M., Burkhardt, Dennis E., Mageland, Otto M., Woest, Karen L., Wagner, Michael E., Pascucci, Gregory A., Vairavan, Vairavan, Koch, David L., Spacek, Dan J., Hyzer, Susan M., Garbe, James R., Standish, Darrell E., Madaus, Paul W., Gottschalk, Donald A. Jr., Stark, James K.
• Primary Examiner(s): Harrell, Robert B.
• Application Number:
  US08/185,181
• Time in Patent Office: 858 Days
• Field of Search: 364/DIG. 1 MS File, 364/DIG. 2 MS File, 370/60, 370/94, 370/99, 370/110.1, 370/94.1, 370/85.1, 370/85.7, 370/95.1, 370/60.1, 395/200, 395/250, 395/275, 395/650, 395/800
• US Class Current: 709/222
• CPC Class Codes: G06F 11/22 Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A networked system having a wide variety of applications and particularly applicable to facilities management systems has multiple levels of software in processing nodes. The levels include a "features" processing level which communicates requests for data to a software object level containing databases of processes and attributes and database managers. The database managers in the software object level operate to provide data to the high level features in the same format. The software object level communicates with a hardware object level which also contains databases and database managers to mask differences between operational hardware units. By categorizing operational units by type, additional units of a known type can be added with only low level hardware object database changes. Adding units of a new type is facilitated by software changes confined to the lower level hardware and software objects, avoiding software changes at high level features. Individual software objects are tailored for typical types of inputs and output devices encountered by facilities management systems. Universal drive circuitry also provides applicability to a broad range of devices. Nodes are provided with ports which may accommodate a non-configured device. When a non-configured device is identified on a port, a drop identifier specifying the port is transmitted to the non-configured device for use in establishing a network address by which the non-configured device can be accessed.

Claims

1. A facilities management system configured to allow access to the system by a non-configured portable computing unit, the facilities management system including a plurality of network controllers arranged to control a process, the network controllers being configured as at least one network and being interconnected by at least one communication link, each of the network controllers including an equipment interface for receiving data related to the process, and a processor including a drop port, the processor being coupled to the equipment interface, the facilities management system being initialized so that the network controllers are configured to each have a network address indicative of a particular location in the facilities management system, the network address including a subset indicative of an associated communication link to which the network controller is connected, a local address indicative of the network controller, and a node drop ID indicating that the network controller is a configured network controller, the facilities management system comprising:

a first configured network controller including a first processor having a first port for receiving the portable computing unit, the first configured network controller configured on the system at a first location defined by a first subset indicative of the communication link, a first local address indicative of the first configured network controller and the node drop ID;

a second network controller having a first equipment interface, the second network controller being coupled to the communication link and being configured on the system at a second location defined by a second subset indicative of the communication link and a second local address indicative of the second configured networked controller, the second network controller having a second network address including the second subset, the second local address and the node drop ID;

means for assigning a first network address to the portable computing unit, the first network address including the first subset, the first local address and a first drop identifier indicative of the first port;

means for transmitting a request for data received at the first equipment interface of the second configured network controller located at the second location from the portable computing unit to the second network controller, the request including the second network address as a destination indicator and the first network address as a source indicator;

means for transmitting the data from the second configured network controller to the portable computing unit in response to the request for data, the data including the second network address as the source indicator and the first network address as the destination indicator;

means for receiving the data from the second configured network controller at the first processor of the first network controller according to the subset and local address of the first configured network address; and

means for transmitting the data to the portable computing unit through the first drop port specified by the first drop identifier.

2. The system of claim 1 wherein each network controller further includes a network layer, and a data link layer, the facilities management system including intermediate network controllers located between the first configured network controller and the second configured network controller, the system further comprising:

means for transmitting the request for data to the intermediate controllers along a path between the first configured network controller and the second configured network controller, the intermediate network controllers receiving the request at the data link layer and decoding the destination address in the network layer, the intermediate network controllers retransmitting the request at the data link layer along the path to a next intermediate controller until the second configured network controller is reached.

3. The system of claim 2 further comprising:

means for retrieving the data from the equipment interface of the second network controller in response to the request for data.

4. The system of claim 3 further comprising:

means for transmitting the data to the intermediate controllers along the path between the first network controller and the second network controller, the intermediate network controllers receiving the request at the data link layer, decoding the destination address in the network layer, the intermediate network controllers retransmitting the request from the data link layer along the path to the next intermediate controller until the first network controller is reached.

5. The system of claim 4 further comprising:

means for routing the data between the portable computing unit and the second configured network controller along routes for message traffic between the first configured network controller and the second configured network controller in accordance with a routing table stored in the network controllers.

6. The system of claim 5 further comprising:

means for storing at each network controller a routing table when the facilities management system is initialized, the table having an entry for the destination address, the entry of the table defining the next address along the routes for message traffic.

7. The system of claim 6 further comprising:

means for storing portions of predetermined routes in sequences of the intermediate network controllers as a series of network addresses, each network address defining a next location along the path from the first configured network controller to the second configured network controller.

8. The system of claim 4 further comprising:

means for receiving the data at the data link layer of the first network controller, providing the data to the network layer, and transmitting the data from the network layer to the first drop port of the processor of the first configured network controller.

9. The system of claim 8 further comprising:

means for receiving the data with the portable computing unit at the first drop port.

10. The system of claim 4 further comprising:

means for storing a static routing table at each network controller, the static routing table having an entry for each destination address, the entries of the table defining the next address along the path from the first configured network controller to the second configured network controller.

11. The system of claim 4 further comprising:

means for storing the predetermined route portion in a table in a central processor in the facilities management system and accessing the table to define the route.

12. The system of claim 4 further comprising:

means for adaptively routing the request and data between the portable computing unit and the second configured network controller along the routes for message traffic between the first network controller and the second network controller determined by a dynamic routing strategy sensitive to message traffic throughout the facilities management system.

13. The system of claim 1 further comprising:

means for routing the data between the portable computing unit and the second configured network controller along routes for message traffic between the first configured network controller and the second configured network controller.

14. The system of claim 13 further comprising:

means for adaptively routing messages between the portable computing unit and the second configured network controller along the routes for message traffic between the first configured network controller and the second configured network controller determined by a dynamic routing strategy sensitive to message traffic throughout the facilities management system.

15. The system claim 13 further comprising:

means for storing at each network controller a routing table, the table having an entry for the destination address, the entry of the table defining a next address along the routes for message traffic.

16. The system of claim 1 further comprising:

means for predetermining the routes when the facilities management system is initialized; and

means for storing portions of the predetermined routes in sequences of the network controllers as a series of network addresses, each network address defining a next location along a path from the first configured network controller to the second configured network controller.

17. The system of claim 16 further comprising:

means for storing a static routing table at each network controller, the static routing table having an entry for each destination address, the entries of the table defining a next address along paths from the first configured network controller to the second configured network controller.

18. The system of claim 16 further comprising:

means for storing the predetermined route portion in a table in a central processor and accessing the table to define the route.

19. The system of claim 1 wherein the portable computing unit is a lap top computer.

20. The system of claim 1 wherein the process is internal environmental control.