1. Field of the Invention
The present invention relates to a centralized circuit breaker protection system for a power distribution system, and more particularly, to a technique for automatically configuring a processor in a centrally controlled circuit breaker protection system.
2. Description of the Related Art
Industrial power distribution systems commonly divide incoming power into a number of branch circuits, where the branch circuits supply power to various equipment (i.e., loads) in an industrial facility. Circuit breakers are provided in each branch circuit to facilitate protection of equipment within the branch circuit. The circuit breakers can be opened or closed by non-automatic means, and can also be opened automatically when subjected to a predetermined over-current. Since this automatic protection is based on conditions of the power (e.g., current), suppliers of circuit breakers have commonly made a large range circuit breakers to meet the various current demands.
The present inventor has developed a unique technique to ensure a proper configuration of components in a centralized circuit breaker protection system for a power distribution system.
A centralized circuit breaker protection system controls and monitors the power distribution system from a central control processing unit. Configuration of control and protection settings for safe and reliable operation of a power distribution system typically requires substantial training and knowledge of power systems engineering, protective relaying, control systems engineering, and computer systems. Each particular application of such a system may require a different configuration to fulfill its commercial requirements. Manually configuring a circuit breaker protection system is a very labor intensive and time consuming process, and requires skilled technical service personnel to set various components of the system in order to satisfy unique customer specifications.
When a centralized circuit breaker protection system for a power distribution system, is initialized, values are assigned to variable elements in data structures to determine performance characteristics of the centralized circuit breaker protection system. The present invention provides for configuration of a centralized circuit breaker protection system by executing a process that automatically sets variable parameters of the elements of such a system.
One embodiment of the present invention is a computer-implemented method for configuring a centralized circuit breaker protection system. The method includes determining configuration data for a processor in the centralized circuit breaker protection system in accordance with a parameter relating to an operation of the centralized circuit breaker protection system, and configuring the processor with the configuration data. Other embodiments of the present invention are an apparatus for configuring a centralized circuit breaker protection system, and a storage media containing instructions for controlling a computer for configuring a centralized circuit breaker protection system.
Referring now to the drawings and in particular to
Power bus 12 is illustrated by way of example as a three-phase power system having a first phase 18, a second phase 20, and a third phase 22. Power bus 12 can also include a neutral phase (not shown). System 10 is illustrated for purposes of clarity distributing power from power bus 12 to four circuits 16 by four breakers 14. Of course, it is contemplated by the present disclosure for power bus 12 to have any desired number of phases and/or for system 10 to have any desired number of circuit breakers 14.
Each circuit breaker 14 has a set of separable contacts 24 (illustrated schematically). Contacts 24 selectively place power bus 12 in communication with at least one load (also illustrated schematically) on circuit 16. The load can include devices, such as, but not limited to, motors, welding machinery, computers, heaters, lighting, and/or other electrical equipment.
Power distribution system 10 is illustrated in
Thus, protection system 26 can include protection and control schemes that consider the value of electrical signals, such as current magnitude and phase, at one or all circuit breakers 14. Further, protection system 26 integrates the protection, control, and monitoring functions of the individual breakers 14 of power distribution system 10 in a single, centralized control processor (e.g., CCPU 28). Protection system 26 provides CCPU 28 with all of a synchronized set of information available through digital communication with modules 30 and circuit breakers 14 on network 32 and provides the CCPU with the ability to operate these devices based on this complete set of data.
Specifically, CCPU 28 performs all primary power distribution functions for power distribution system 10. Namely, CCPU 28 performs all instantaneous overcurrent protection (IOC), short time overcurrent, longtime overcurrent, relay protection, and logic control as well as digital signal processing functions of protection system 26. Thus, protection system 26 enables settings to be changed and data to be logged in a single, central location, i.e., CCPU 28. CCPU 28 is described herein by way of example as a central processing unit. Of course, it is contemplated by the present disclosure for CCPU 28 to include any programmable circuit, such as, but not limited to, computers, processors, microcontrollers, microcomputers, programmable logic controllers, application specific integrated circuits, and other programmable circuits.
As shown in
Module 30 sends and receives one or more second signals 38 to and/or from circuit breaker 14. Second signals 38 can be representative of one or more conditions of breaker 14, such as, but not limited to, a position of separable contacts 24, a spring charge switch status, and others. In addition, module 30 is configured to operate circuit breaker 14 by sending one or more third signals 40 to the breaker to open/close separable contacts 24 as desired. In a first embodiment, circuit breakers 14 cannot open separable contacts 24 unless instructed to do so by protection system 26.
Protection system 26 utilizes data network 32 for data acquisition from modules 30 and data communication to the modules. Accordingly, network 32 is configured to provide a desired level of communication capacity and traffic management between CCPU 28 and modules 30. In an exemplary embodiment, network 32 can be configured to not enable communication between modules 30 (i.e., no module-to-module communication).
In addition, protection system 26 can be configured to provide a consistent fault response time. As used herein, the fault response time of protection system 26 is defined as the time between when a fault condition occurs and the time module 30 issues a trip command to its associated breaker 14. In an exemplary embodiment, protection system 26 has a fault response time that is less than a single cycle of the 60 Hz (hertz) waveform. For example, protection system 26 can have a maximum fault response time of about three milliseconds.
The configuration and operational protocols of network 32 are configured to provide the aforementioned communication capacity and response time. For example, network 32 can be an Ethernet network having a star topology as illustrated in FIG. 1. In this embodiment, network 32 is a full duplex network having the collision-detection multiple-access (CSMA/CD) protocols typically employed by Ethernet networks removed and/or disabled. Rather, network 32 is a switched Ethernet for managing collision domains.
In this configuration, network 32 provides a data transfer rate of at least about 100 Mbps (megabits per second). For example, the data transfer rate can be about 1 Gbps (gigabits per second). Additionally, communication between CCPU 28 and modules 30 across network 32 can be managed to optimize the use of network 32. For example, network 32 can be optimized by adjusting one or more of a message size, a message frequency, a message content, and/or a network speed.
Accordingly, network 32 provides for a response time that includes scheduled communications, a fixed message length, full-duplex operating mode, and a switch to prevent collisions so that all messages are moved to memory in CCPU 28 before the next set of messages is scheduled to arrive. Thus, protection system 26 can perform the desired control, monitoring, and protection functions in a central location and manner.
It should be recognized that data network 32 is described above by way of example only as an Ethernet network having a particular configuration, topography, and data transmission protocols. Of course, the present disclosure contemplates the use of any data transmission network that ensures the desired data capacity and consistent fault response time necessary to perform the desired range of functionality. The exemplary embodiment achieves sub-cycle transmission times between CCPU 28 and modules 30 and full sample data to perform all power distribution functions for multiple modules with the accuracy and speed associated with traditional devices.
CCPU 28 can perform branch circuit protection, zone protection, and relay protection interdependently because all of the system information is in one central location, namely at CCPU 28. In addition, CCPU 28 can perform one or more monitoring functions on the centrally located system information. Accordingly, protection system 26 provides a coherent and integrated protection, control, and monitoring methodology not considered by prior systems. For example, protection system 26 integrates and coordinates load management, feed management, system monitoring, and other system protection functions in a low cost and easy to install system.
An exemplary embodiment of module 30 is illustrated in FIG. 2. Module 30 has a microprocessor 42, a data bus 44, a network interface 46, a power supply 48, and one or more memory devices 50.
Power supply 48 is configured to receive power from a first source 52 and/or a second source 54. First source 52 can be one or more of an uninterruptible power supply (not shown), a plurality of batteries (not shown), a power bus (not shown), and other sources. In the illustrated embodiment, second source 54 is the secondary current available from sensors 34.
Power supply 48 is configured to provide power 56 to module 30 from first and second sources 52, 54. For example, power supply 48 can provide power 56 to microprocessor 42, data bus 42, network interface 44, and memory devices 50. Power supply 48 is also configured to provide a fourth signal 58 to microprocessor 42. Fourth signal 58 is indicative of what sources are supplying power to power supply 48. For example, fourth signal 58 can indicate whether power supply 48 is receiving power from first source 52, second source 54, or both of the first and second sources.
Network interface 46 and memory devices 50 communicate with microprocessor 42 over data bus 44. Network interface 46 can be connected to network 32 so that microprocessor 42 is in communication with CCPU 28.
Microprocessor 42 receives digital representations of first signals 36 and second signals 38. First signals 36 are continuous analog data collected by sensors 34, while second signals 38 are discrete analog data from breaker 14. Thus, the data sent from modules 30 to CCPU 28 is a digital representation of the actual voltages, currents, and device status. For example, first signals 36 can be analog signals indicative of the current and/or voltage in circuit 16.
Accordingly, protection system 26 provides the actual raw parametric or discrete electrical data (i.e., first signals 36) and device physical status (i.e., second signal 38) to CCPU 28 via network 32, rather than processed summary information sampled, created, and stored by devices such as trip units, meters, or relays. As a result, CCPU 28 has complete, raw system-wide data with which to make decisions and can therefore operate any or all breakers 14 on network 32 based on information derived from as many modules 30 as the control and protection algorithms resident in CCPU 28 require.
Module 30 has a signal conditioner 60 and an analog-digital converter 62. First signals 36 are conditioned by signal conditioner 60 and converted to digital signals 64 by A/D converter 62. Thus, module 30 collects first signals 36 and presents digital signals 64, representative of the raw data in the first signals, to microprocessor 42. For example, signal conditioner 60 can includes a filtering circuit (not shown) to improve a signal-to-noise ratio first signal 36, a gain circuit (not shown) to amplify the first signal, a level adjustment circuit (not shown) to shift the first signal to a predetermined range, an impedance match circuit (not shown) to facilitate transfer of the first signal to A/D converter 62, and any combination thereof. Further, A/D converter 62 can be a sample-and-hold converter with external conversion start signal 66 from microprocessor 42 or a clock circuit 68 controlled by microprocessor 42 to facilitate synchronization of digital signals 64.
It is desired for digital signals 64 from all of the modules 30 in protection system 26 to be collected at substantially the same time. Specifically, it is desired for digital signals 64 from all of the modules 30 in protection system 26 to be representative of substantially the same time instance of the power in power distribution system 10.
Modules 30 sample digital signals 64 based, at least in part, upon a synchronization signal or instruction 70 as illustrated in FIG. 1. Synchronization instruction 70 can be generated from a synchronizing clock 72 that is internal or external to CCPU 28. Synchronization instruction 70 is simultaneously communicated from CCPU 28 to modules 30 over network 32. Synchronizing clock 72 sends synchronization instructions 70 at regular intervals to CCPU 28, which forwards the instructions to all modules 30 on network 32.
Modules 30 use synchronization instruction 70 to modify a resident sampling protocol. For example, each module 30 can have a synchronization algorithm resident on microprocessor 42. The synchronization algorithm resident on microprocessor 42 can be a software phase-lock-loop algorithm. The software phase-lock-loop algorithm adjusts the sample period of module 30 based, in part, on synchronization instructions 70 from CCPU 28. Thus, CCPU 28 and modules 30 work together in protection system 26 to ensure that the sampling (i.e., digital signals 64) from all of the modules in the system are synchronized.
Accordingly, protection system 26 is configured to collect digital signals 64 from modules 30 based in part on synchronization instruction 70 so that the digital signals are representative of the same time instance, such as being within a predetermined time-window from one another. Thus, CCPU 28 can have a set of accurate data representative of the state of each monitored location (e.g., modules 30) within the power distribution system 10. The predetermined time-window can be less than about ten microseconds. For example, the predetermined time-window can be about five microseconds.
The predetermined time-window of protection system 26 can be affected by the port-to-port variability of network 32. In an exemplary embodiment, network 32 has a port-to-port variability of in a range of about 24 nanoseconds to about 720 nanoseconds. In an alternate exemplary embodiment, network 32 has a maximum port-to-port variability of about 2 microseconds.
It has been determined that control of all of modules 30 to this predetermined time-window by protection system 26 enables a desired level of accuracy in the metering and vector functions across the modules, system waveform capture with coordinated data, accurate event logs, and other features. In an exemplary embodiment, the desired level of accuracy is equal to the accuracy and speed of traditional devices. For example, the predetermined time-window of about ten microseconds provides an accuracy of about 99% in metering and vector functions.
Second signals 38 from each circuit breaker 14 to each module 30 are indicative of one or more conditions of the circuit breaker. Second signals 38 are provided to a discrete I/O circuit 74 of module 30. Circuit 74 is in communication with circuit breaker 14 and microprocessor 42. Circuit 74 is configured to ensure that second signals 38 from circuit breaker 14 are provided to microprocessor 42 at a desired voltage and without jitter. For example, circuit 74 can include de-bounce circuitry and a plurality of comparators.
Microprocessor 42 samples first and second signals 36, 38 as synchronized by CCPU 28. Then, converter 62 converts the first and second signals 36, 38 to digital signals 64, which is packaged into a first message 76 having a desired configuration by microprocessor 42. First message 76 can include an indicator that indicates which synchronization signal 70 the first message was in response to. Thus, the indicator of which synchronization signal 70 first message 76 is responding to is returned to CCPU 28 for sample time identification.
CCPU 28 receives first message 76 from each of the modules 30 over network 32 and executes one or more protection and/or monitoring algorithms on the data sent in all of the first messages. Based on first message 76 from one or more modules 30, CCPU 28 can control the operation of one or more circuit breakers 14. For example, when CCPU 28 detects a fault from one or more of first messages 76, the CCPU sends a second message 78 to one or more modules 30 via network 32.
In response to second message 78, microprocessor 42 causes third signal 40 to operate (e.g., open contacts 24) circuit breaker 14. Circuit breaker 14 can include more than one operation mechanism. For example, circuit breaker 14 can have a shunt trip 80 and a magnetically held solenoid 82. Microprocessor 42 is configured to send a first output 84 to operate shunt trip 80 and/or a second output 86 to operate solenoid 82. First output 84 instructs a power control module 88 to provide third signal 40 (i.e., power) to shunt trip 80, which can separate contacts 24. Second output 86 instructs a gating circuit 90 to provide third signal 40 to solenoid 82 (i.e., flux shifter) to separate contacts 24. It should be noted that shunt trip 80 requires first source 52 to be present, while solenoid 82 can be operated only when second source 54 is present. In this manner, microprocessor 42 can operate circuit breaker 14 in response to second message 78 regardless of the state of first and second sources 52, 54.
In addition to operating circuit breaker 14, module 30 can communicate to one or more local input and/or output devices 94. For example, local output device 94 can be a module status indicator, such as a visual or audible indicator. In one embodiment, device 94 is a light emitting diode (LED) configured to communicate a status of module 30. In another embodiment, local input device 94 can be a status-modifying button for manually operating one or more portions of module 30. In yet another embodiment, local input device 94 is a module interface for locally communicating with module 30.
Accordingly, modules 30 are adapted to sample first signals 36 from sensors 34 as synchronized by the CCPU. Modules 30 then package the digital representations (i.e., digital signals 64) of first and second signals 36, 38, as well as other information, as required into first message 76. First message 76 from all modules 30 are sent to CCPU 28 via network 32. CCPU 28 processes first message 76 and generates and stores instructions to control the operation of each circuit breaker 14 in second message 78. CCPU 28 sends second message 78 to all of the modules 30. In an exemplary embodiment, CCPU 28 sends second message 78 to all of the modules 30 in response to synchronization instruction 70.
Accordingly, protection system 26 can control each circuit breaker 14 based on the information from that breaker alone, or in combination with the information from one or more of the other breakers in the protection system 26. Under normal operating conditions, protection system 26 performs all monitoring, protection, and control decisions at CCPU 28.
Since the protection and monitoring algorithms of protection system 26 are resident in CCPU 28, these algorithms can be enabled without requiring hardware or software changes in circuit breaker 14 or module 30. For example, protection system 26 can include a data input/output device 92, such as a human-machine-interface (HMI), in communication with CCPU 28. Data input/output device 92 allows a user to provide data and commands for use by protection system 26, and to receive messages and other information from protection system 26. An exemplary embodiment of data input/output device 92 is processor with a keyboard and a display. In the embodiment of protection system 26 shown in
Thus, circuit breaker 14 and module 30 can be more standardized than was possible with the circuit breakers/trip units of prior systems. For example, over one hundred separate circuit breakers/trip units have been needed to provide a full range of sizes normally required for protection of a power distribution system. However, the generic nature of circuit breaker 14 and module 30 enabled by protection system 26 can reduce this number by over sixty percent. Thus, protection system 26 can resolve the inventory issues, retrofittability issues, design delay issues, installation delay issues, and cost issues of prior power distribution systems.
It should be recognized that protection system 26 is described above as having one CCPU 28 communication with modules 30 by way of a single network 32. However, it is contemplated by the present disclosure for protection system 26 to have redundant CCPUs 26 and networks 32 as illustrated in phantom in FIG. 1. For example, module 30 is illustrated in
Modules 30 can further include one or more backup systems for controlling breakers 14 independent of CCPU 28. For example, protection system 26 may be unable to protect circuit 16 in case of a power outage in first source 52, during the initial startup of CCPU 28, in case of a failure of network 32, and other reasons. Under these failure conditions, each module 30 includes one or more backup systems to ensure that at least some protection is provided to circuit breaker 14. The backup system can include one or more of an analog circuit driven by second source 54, a separate microprocessor driven by second source 54, and others.
A wizard is a utility that helps a user of a processor to complete a particular task. Referring again to
Wizard 425 is contemplated as being computer implemented. As such, wizard 425 can be implemented in software, firmware or as a discrete circuit. When implemented in software, wizard 425 is installed into a memory, such as a memory associated with data input/output device 92 or another configuration computer. However, wizard 425 can reside on an external storage media 29 for subsequent loading into data input/output device 92. Storage media 29 can be any conventional storage media, including, but not limited to, a floppy disk, a compact disk, a magnetic tape, a read only memory, or an optical storage media. Storage media 29 could also be a random access memory, or other type of electronic storage, located on a remote storage system and coupled to CCPU 28. Although wizard 425 is shown in
Variable settings 305 represent data elements that are customized for each individual protection system 26. These data elements may be further customized for a particular CCPU 28 or module 30.
Firmware code 310 represents data for programmable components such as that used for a state machine or a memory controller. Firmware code 310 is typically standardized to a revision level, and therefore may be regarded as being independent of the unique requirements of a particular protection system 26. Nevertheless, firmware code 310 may be subject to an occasional update.
Operating system 315 is a real-time operating system, for example VX Works, which is available from Wind River Systems, Inc., 500 Wind River Way, Alameda, Calif. 94501. Such an operating system is also conventionally known as an embedded operating system. Operating system 315 may be subject to an occasional update.
Configuring data 300, that is, installing or updating any of variable settings 305, firmware code 310 or operating system 315, when performed manually, can be a time consuming task. Furthermore, as the size or complexity of system 10 increases, typically, so does the size and complexity of protection system 26, and likewise of data 300. Thus, manual configuration can present many opportunities for erroneous data entry, and consequently, faulty operation of protection system 26. The configuration of processors in protection system 26 also requires a specialized, yet diverse, set of skills. For example, a person performing such a configuration must typically have some familiarity with customer requirements, electrical power systems, overcurrent protection, protective relaying, software configuration, control logic programming and communications networks.
OTR system 420 receives parameters from customer sales and marketing personnel 405 and consultant 410, and passes the parameters to wizard 425. OTR system 420 may include an order entry tool for sales people, a list of choices that may be made with respect to a configuration of ordered products, inventory management and parts ordering systems for factories, work order processing, dispensing of options to products that are ordered, manufacturing flow tracking for individual orders, and shipping information and tracking.
Wizard 425 is implemented as part of an interactive interface that assists a user, such as product engineer 415, to perform the configuration of protection system 26. Wizard 425 provides step-by-step instructions for entering parameters for configuring protection system 26 and automatically configures data elements for the processors of protection system 26. Thus, wizard 425 enables a wide range of personnel to configure protection system 26 with minimal time and minimal prerequisite knowledge.
Wizard 425 receives the parameters from OTR system 420 and product engineer 415, determines configuration data for CCPU 28 and modules 30A and 30B in accordance with the parameters, and configures CCPU 28 and modules 30A and 30B with the configuration data. Configuring CCPU 28 and modules 30A and 30B can involve (a) configuring software in CCPU 28 and modules 30A and 30B, (b) configuring firmware in CCPU 28 and modules 30A and 30B, (c) installing software in CCPU 28 and modules 30A and 30B, and (d) updating an operating system in CCPU 28 and modules 30A and 30B.
Organization of information to be entered is also a feature of wizard 425 that can save time and reduce the amount of requisite domain knowledge required by an operator. By grouping information to be entered into discrete, limited sets within a construct of a series of sequential screens, the operator need only consider information relevant to singular or basic decisions, in the precise logical order in which it is necessary for them to be considered, thereby further simplifying the configuration process.
Assume that product engineer 415 wishes to configure CCPU 28 for a rating switch value. Product engineer 415 accesses wizard 425 via data input/output device 92.
Wizard 425 prompts product engineer 415 for a breaker frame size, and more particularly offers product engineer 415 an opportunity to select from four possible breaker frame sizes, i.e., 800, 1600, 2000 and 3200 Amps. Assume product engineer 415 selects a breaker frame size of 800 Amps.
Wizard 425 then prompts product engineer 415 to select a CT rating from a limited set of 150, 400 and 800 Amps. That is, wizard 425 only offers product engineer 415 a valid set of CT ratings. Note, for example, that if product engineer 415 had previously selected a breaker frame size of 1600 Amps, then wizard 425 would have offered CT ratings of 800 and 1600 Amps. However, since product engineer 415 selected a breaker frame size of 800 Amps, the option of selecting a CT rating of 1600 Amps is not available. Product engineer 415 does not need detailed knowledge of what values of a parameter are allowable in view of previously selected parameters. By limiting the selection of CT ratings only to a valid set, wizard 425 prevents product engineer 415 from inadvertently entering a value for a parameter that is invalid in light of a previously selected parameter, and helps to minimize the opportunity for product engineer 415 to specify an invalid or unsafe combination of breaker frame size and CT rating. Furthermore, wizard 425 either requires product engineer 415 to enter a value for a parameter, or assigns a default value to the parameter. For the present example, assume that product engineer 415 selects a CT rating of 150 Amps.
Wizard 425 then prompts product engineer 415 to select an LT rating multiplier from a limited set of values. Assume that product engineer 415 selects an LT rating multiplier of 0.
Wizard 425 automatically determines the rating switch value to be 60 Amps, and furthermore, determines the appropriate configuration data to configure CCPU 28 with a rating switch value of 60 Amps. Thereafter, wizard 425 configures CCPU 28 with the configuration data.
Although the present example was introduced above as indicating that product engineer 415 wished to configure the rating switch value for CCPU 28, product engineer 415 need not even be aware that wizard 425 determined the rating switch value. In other words, wizard 425 relieves product engineer 425 of the responsibility of knowing which particular configuration data is being determined and knowing which particular processor is being configured. Note also that wizard 425 may have received, in addition to the parameters from product engineer 415, other parameters from personnel 405 or consultant 410. Wizard 425 determines the configuration data to be consistent with all of the parameters.
With reference to Table 2, recall that wizard 425 used breaker frame size, CT rating, LT rating multiplier to determine the rating switch value for configuring CCPU 28. However, a parameter can serve as a basis for determining configuration data for more than one processor in protection system 26. When wizard 425 uses an input parameter for determining more than one configuration setting, product engineer 415 does not need to enter a value for that parameter for each individual configuration.
Assume that module 30A controls a first circuit breaker and that module 30B controls a second circuit breaker. Based on the parameters, wizard 425 can determine a first version of configuration data for module 30A and a second version of configuration data for module 30B, and, the first version can be different from the second version. Furthermore, wizard 425 can determine a configuration setting that can be applied to all of module 30A, module 30B and CCPU 28.
Recall that in the discussion of Table 2, product engineer 415 selected a value of 150 Amps for CT rating. CT rating is also known as sensor rating. Thus, with reference to Table 4, the selection of 150 Amps for CT rating corresponds with a sensor rating in the range of 150-2000 Amps. Wizard 425 automatically determines the maximum ground fault pickup threshold value to be 0.6, determines corresponding configuration data for CCPU 28 and configuration data for modules 30A and 30B, and configures CCPU 28 and modules 30A and 30B with their respective configuration data.
The manner in which data is organized and represented in CCPU 28 is likely to be different from the manner in which data is organized and represented in modules 30A and 30B. Accordingly, the configuration data for modules 30A and 30B may be different from the configuration data for CCPU 28. Nevertheless, wizard 26 configures and formats the configuration data as required by each of CCPU 28 and modules 30A and 30B.
Some settings such as delay band constants, cooling time constants, alarm parameters are generally not of immediate interest with respect to getting a system up and running. For such settings, calculated or default values can be automatically determined based on other more critical values that have been entered or specified, and the calculated or default values can be used without further user interaction of confirmation. Additionally, wizard 425 can limit a number or range of choices on subordinate related parameters based on decisions and/or values chosen up to a present point. This is achieved by providing wizard 425 with requisite domain knowledge associated with a relationship of the lesser parameters into logical structures and algorithms of wizard 425.
Wizard 425 is also contemplated as having a capability of testing the components of protection system 26. As such, when wizard 425 configures a processor, the processor, in turn, performs a test. For example, the configuration data may cause CCPU 28 to invoke a test to validate the functionality of modules 30A and 30B. Such a test may involve an exchange of data between wizard 425 and CCPU 28, where for example, wizard 425 prompts CCPU 28 to perform the test, and CCPU 28 reports test results, validation results, or other diagnostic feedback to wizard 425.
A user can access wizard 425 through data input/output device 92, which is contemplated as providing a graphic representation of the components of protection system 26, e.g., virtual components. Ordinarily, the user will control the actual components of protection system 26 by manipulating the virtual components on data input/output device 92. As system 10 may include a plurality of circuit breakers 14 and thus protection system 26 includes a plurality of modules 30, data input/output device 92 may be remotely located from some or all of the components of protection system 26. However, an important aspect of testing or controlling the components of system 10 and protection system 26 is that the user know, with certainty, which of the actual components is being tested or controlled. Accordingly, the components of protection system 26 can include an annunciator, i.e., an indicator, where the configuration data causes the indicator to affirmatively indicate an actual component that corresponds to a representation of the component on data input/output device 92. For example, with reference to
Database 435 is a product configuration database. Wizard 425 sends data relating to the configuration of protection system 26 to database 435.
Marketing analysts 430 utilize database 435 for marketing purposes, such as determining an additional product that can be used in protection system 26, and thus, to target the product to the users of protection system 26. For example, by knowing the configuration of protection system 26, marketing analysts 430 may recognize that an additional product can be used as an alternative to an existing component in protection system 26, or that the additional product could enhance the operation of protection system 26.
Field service engineers 440 utilize database 425 for maintenance purposes, such as determining a time for a maintenance operation for protection system 26. That is, by knowing how the components of protection system 26 are being used, field service engineers 440 can offer a preventive or predictive maintenance service for protection system 26.
Note that the operations of marketing analysts 430 and field service engineers 440 need not be performed by humans, but instead, could be automated processes.
It is also contemplated for wizard 425 to receive parameters from database 435 relating to the operation of protection system 26, and to consider such parameters when determining the configuration of the components of protection system 26. For example, database 435 can provide parameters for automatically updating the configuration of the components. Such updates could be initiated by marketing analysts 430 or field service engineers 440. The testing of components via wizard 425, as mentioned above, could also be initiated by marketing analysts 430 or field service engineers 440.
Wizard 425 provides several advantages that are worth noting. It minimizes time required for configuring protection system 26, and minimizes prerequisite knowledge that would otherwise required by an individual tasked to perform the configuration. It assists in quality control in that it minimizes erroneous entries of variable settings. It improves uniformity by reducing variability that may result when a setting is otherwise left to the discretion of an individual. It can be implemented to utilize programmable logic control, and thus relieves individuals from having to write code.
It should be understood that various alternatives and modifications of the present invention could be devised by those skilled in the art. Nevertheless, the present invention is intended to embrace all such alternatives, modifications and variances that fall within the scope of the appended claims.
The present application is claiming priority of U.S. patent application No. 60/359,544 filed on Feb. 25, 2002 for “Integrated Protection, Monitoring, and Control” the contents of which are incorporated by reference herein. The present application is also claiming priority of U.S. patent application No. 60/438,159 filed on Jan. 6, 2003 for “Single Processor Concept for Protection and Control of Circuit Breakers in Low-Voltage Switchgear” the contents of which are incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
3772505 | Massell | Nov 1973 | A |
3938007 | Boniger et al. | Feb 1976 | A |
3956671 | Nimmersjo | May 1976 | A |
3963964 | Mustaphi | Jun 1976 | A |
4001742 | Jencks et al. | Jan 1977 | A |
4245318 | Eckart et al. | Jan 1981 | A |
4291299 | Hinz et al. | Sep 1981 | A |
4301433 | Castonguay et al. | Nov 1981 | A |
4311919 | Nail | Jan 1982 | A |
4415968 | Maeda et al. | Nov 1983 | A |
4423459 | Stich et al. | Dec 1983 | A |
4432031 | Premerlani | Feb 1984 | A |
4455612 | Girgis et al. | Jun 1984 | A |
4468714 | Russell | Aug 1984 | A |
4589074 | Thomas et al. | May 1986 | A |
4623949 | Salowe et al. | Nov 1986 | A |
4631625 | Alexander et al. | Dec 1986 | A |
4642724 | Ruta | Feb 1987 | A |
4652966 | Farag et al. | Mar 1987 | A |
4672501 | Bilac et al. | Jun 1987 | A |
4672555 | Hart et al. | Jun 1987 | A |
4674062 | Premerlani | Jun 1987 | A |
4689712 | Demeyer | Aug 1987 | A |
4709339 | Fernandes | Nov 1987 | A |
4751653 | Junk et al. | Jun 1988 | A |
4752853 | Matsko et al. | Jun 1988 | A |
4754407 | Nolan | Jun 1988 | A |
4777607 | Maury et al. | Oct 1988 | A |
4783748 | Swarztrauber et al. | Nov 1988 | A |
4796027 | Smith-Vaniz | Jan 1989 | A |
4833592 | Yamanaka | May 1989 | A |
4849848 | Ishii | Jul 1989 | A |
4855671 | Fernandes | Aug 1989 | A |
4862308 | Udren | Aug 1989 | A |
4964058 | Brown, Jr. | Oct 1990 | A |
4979122 | Davis et al. | Dec 1990 | A |
4983955 | Ham, Jr. et al. | Jan 1991 | A |
4996646 | Farrington | Feb 1991 | A |
5053735 | Ohishi et al. | Oct 1991 | A |
5060166 | Engel et al. | Oct 1991 | A |
5101191 | MacFadyen et al. | Mar 1992 | A |
5134691 | Elms | Jul 1992 | A |
5136458 | Durivage, III | Aug 1992 | A |
5162664 | Haun et al. | Nov 1992 | A |
5166887 | Farrington et al. | Nov 1992 | A |
5170310 | Studtmann et al. | Dec 1992 | A |
5170360 | Porter et al. | Dec 1992 | A |
5179376 | Pomatto | Jan 1993 | A |
5182547 | Griffith | Jan 1993 | A |
5185705 | Farrington | Feb 1993 | A |
5196831 | Bscheider | Mar 1993 | A |
5214560 | Jensen | May 1993 | A |
5216621 | Dickens | Jun 1993 | A |
5225994 | Arinobu et al. | Jul 1993 | A |
5231565 | Bilas et al. | Jul 1993 | A |
5237511 | Caird et al. | Aug 1993 | A |
5247454 | Farrington et al. | Sep 1993 | A |
5253159 | Bilas et al. | Oct 1993 | A |
5272438 | Stumme | Dec 1993 | A |
5301121 | Garverick et al. | Apr 1994 | A |
5305174 | Morita et al. | Apr 1994 | A |
5311392 | Kinney et al. | May 1994 | A |
5323307 | Wolf et al. | Jun 1994 | A |
5353188 | Hatakeyama | Oct 1994 | A |
5361184 | El-Sharkawi et al. | Nov 1994 | A |
5367427 | Matsko et al. | Nov 1994 | A |
5369356 | Kinney et al. | Nov 1994 | A |
5381554 | Langer et al. | Jan 1995 | A |
5384712 | Oravetz et al. | Jan 1995 | A |
5402299 | Bellei | Mar 1995 | A |
5406495 | Hill | Apr 1995 | A |
5414635 | Ohta | May 1995 | A |
5420799 | Peterson et al. | May 1995 | A |
5422778 | Good et al. | Jun 1995 | A |
5440441 | Ahuja | Aug 1995 | A |
5451879 | Moore | Sep 1995 | A |
5487016 | Elms | Jan 1996 | A |
5490086 | Leone et al. | Feb 1996 | A |
5493468 | Hunter et al. | Feb 1996 | A |
5530738 | McEachern | Jun 1996 | A |
5534782 | Nourse | Jul 1996 | A |
5534833 | Castonguay et al. | Jul 1996 | A |
5537327 | Snow et al. | Jul 1996 | A |
5544065 | Engel et al. | Aug 1996 | A |
5559719 | Johnson et al. | Sep 1996 | A |
5560022 | Dunstan et al. | Sep 1996 | A |
5576625 | Sukegawa et al. | Nov 1996 | A |
5581471 | McEachern et al. | Dec 1996 | A |
5587917 | Elms | Dec 1996 | A |
5596473 | Johnson et al. | Jan 1997 | A |
5600527 | Engel et al. | Feb 1997 | A |
5608646 | Pomatto | Mar 1997 | A |
5613798 | Braverman | Mar 1997 | A |
5619392 | Bertsch et al. | Apr 1997 | A |
5627716 | Lagree et al. | May 1997 | A |
5627717 | Pein et al. | May 1997 | A |
5627718 | Engel et al. | May 1997 | A |
5629825 | Wallis et al. | May 1997 | A |
5631798 | Seymour et al. | May 1997 | A |
5638296 | Johnson et al. | Jun 1997 | A |
5650936 | Loucks et al. | Jul 1997 | A |
5661658 | Putt et al. | Aug 1997 | A |
5666256 | Zavis et al. | Sep 1997 | A |
5670923 | Gonzalez et al. | Sep 1997 | A |
5694329 | Pomatto | Dec 1997 | A |
5696695 | Ehlers et al. | Dec 1997 | A |
5719738 | Singer et al. | Feb 1998 | A |
5734576 | Klancher | Mar 1998 | A |
5736847 | Van Doorn et al. | Apr 1998 | A |
5737231 | Pyle et al. | Apr 1998 | A |
5742513 | Bouhenguel et al. | Apr 1998 | A |
5751524 | Swindler | May 1998 | A |
5754033 | Thomson | May 1998 | A |
5754440 | Cox et al. | May 1998 | A |
5768148 | Murphy et al. | Jun 1998 | A |
5784237 | Velez | Jul 1998 | A |
5784243 | Pollman et al. | Jul 1998 | A |
5786699 | Sukegawa et al. | Jul 1998 | A |
5812389 | Katayama et al. | Sep 1998 | A |
5821704 | Carson et al. | Oct 1998 | A |
5825643 | Dvorak et al. | Oct 1998 | A |
5828576 | Loucks et al. | Oct 1998 | A |
5828983 | Lombardi | Oct 1998 | A |
5831428 | Pyle et al. | Nov 1998 | A |
5867385 | Brown et al. | Feb 1999 | A |
5872722 | Oravetz et al. | Feb 1999 | A |
5872785 | Kienberger | Feb 1999 | A |
5890097 | Cox | Mar 1999 | A |
5892449 | Reid et al. | Apr 1999 | A |
5903426 | Ehling | May 1999 | A |
5905616 | Lyke | May 1999 | A |
5906271 | Castonguay et al. | May 1999 | A |
5926089 | Sekiguchi et al. | Jul 1999 | A |
5936817 | Matsko et al. | Aug 1999 | A |
5946210 | Montminy et al. | Aug 1999 | A |
5958060 | Premerlani | Sep 1999 | A |
5963457 | Kanoi et al. | Oct 1999 | A |
5973481 | Thompson et al. | Oct 1999 | A |
5973899 | Williams et al. | Oct 1999 | A |
5982595 | Pozzuoli | Nov 1999 | A |
5982596 | Spencer et al. | Nov 1999 | A |
5995911 | Hart | Nov 1999 | A |
6005757 | Shvach et al. | Dec 1999 | A |
6005758 | Spencer et al. | Dec 1999 | A |
6018451 | Lyke et al. | Jan 2000 | A |
6038516 | Alexander et al. | Mar 2000 | A |
6047321 | Raab et al. | Apr 2000 | A |
6054661 | Castonguay et al. | Apr 2000 | A |
6055145 | Lagree et al. | Apr 2000 | A |
6061609 | Kanoi et al. | May 2000 | A |
6084758 | Clarey et al. | Jul 2000 | A |
6138241 | Eckel et al. | Oct 2000 | A |
6139327 | Callahan et al. | Oct 2000 | A |
6141196 | Premerlani et al. | Oct 2000 | A |
6157527 | Spencer et al. | Dec 2000 | A |
6167329 | Engel et al. | Dec 2000 | A |
6175780 | Engel | Jan 2001 | B1 |
6185482 | Egolf et al. | Feb 2001 | B1 |
6185508 | Van Doorn et al. | Feb 2001 | B1 |
6186842 | Hirschbold et al. | Feb 2001 | B1 |
6195243 | Spencer et al. | Feb 2001 | B1 |
6198402 | Hasegawa et al. | Mar 2001 | B1 |
6212049 | Spencer et al. | Apr 2001 | B1 |
6233128 | Spencer et al. | May 2001 | B1 |
6236949 | Hart | May 2001 | B1 |
6242703 | Castonguay et al. | Jun 2001 | B1 |
6268991 | Criniti et al. | Jul 2001 | B1 |
6285917 | Sekiguchi et al. | Sep 2001 | B1 |
6288882 | DiSalvo et al. | Sep 2001 | B1 |
6289267 | Alexander et al. | Sep 2001 | B1 |
6291911 | Dunk et al. | Sep 2001 | B1 |
6292340 | O'Regan et al. | Sep 2001 | B1 |
6292717 | Alexander et al. | Sep 2001 | B1 |
6292901 | Lys et al. | Sep 2001 | B1 |
6297939 | Bilac et al. | Oct 2001 | B1 |
6313975 | Dunne et al. | Nov 2001 | B1 |
6341054 | Walder et al. | Jan 2002 | B1 |
6347027 | Nelson et al. | Feb 2002 | B1 |
6351823 | Mayer et al. | Feb 2002 | B1 |
6356422 | Bilac et al. | Mar 2002 | B1 |
6356849 | Jaffe | Mar 2002 | B1 |
6369996 | Bo | Apr 2002 | B1 |
6377051 | Tyner et al. | Apr 2002 | B1 |
6385022 | Kulidjian et al. | May 2002 | B1 |
6396279 | Gruenert | May 2002 | B1 |
6397155 | Przydatek et al. | May 2002 | B1 |
6405104 | Dougherty | Jun 2002 | B1 |
6406328 | Attarian et al. | Jun 2002 | B1 |
6411865 | Qin et al. | Jun 2002 | B1 |
6441931 | Moskovich et al. | Aug 2002 | B1 |
6459997 | Anderson | Oct 2002 | B1 |
6496342 | Horvath et al. | Dec 2002 | B1 |
6535797 | Bowles et al. | Mar 2003 | B1 |
6549880 | Willoughby et al. | Apr 2003 | B1 |
6553418 | Collins et al. | Apr 2003 | B1 |
20010010032 | Ehlers et al. | Jul 2001 | A1 |
20010032025 | Lenz et al. | Oct 2001 | A1 |
20010044588 | Mault | Nov 2001 | A1 |
20010048354 | Douville et al. | Dec 2001 | A1 |
20010055965 | Delp et al. | Dec 2001 | A1 |
20020010518 | Reid et al. | Jan 2002 | A1 |
20020032535 | Alexander et al. | Mar 2002 | A1 |
20020034086 | Scoggins et al. | Mar 2002 | A1 |
20020045992 | Shincovich et al. | Apr 2002 | A1 |
20020059401 | Austin | May 2002 | A1 |
20020063635 | Shincovich | May 2002 | A1 |
20020064010 | Nelson et al. | May 2002 | A1 |
20020091949 | Ykema | Jul 2002 | A1 |
20020094799 | Elliott et al. | Jul 2002 | A1 |
20020107615 | Bjorklund | Aug 2002 | A1 |
20020108065 | Mares | Aug 2002 | A1 |
20020109722 | Rogers et al. | Aug 2002 | A1 |
20020111980 | Miller et al. | Aug 2002 | A1 |
20020116092 | Hamamatsu et al. | Aug 2002 | A1 |
20020124011 | Baxter et al. | Sep 2002 | A1 |
20020146076 | Lee | Oct 2002 | A1 |
20020146083 | Lee et al. | Oct 2002 | A1 |
20020147503 | Osburn, III | Oct 2002 | A1 |
20020159402 | Binder | Oct 2002 | A1 |
20020162014 | Przydatek et al. | Oct 2002 | A1 |
20020163918 | Cline | Nov 2002 | A1 |
20020165677 | Lightbody et al. | Nov 2002 | A1 |
20020181174 | Bilac et al. | Dec 2002 | A1 |
20020193888 | Wewalaarachchi et al. | Dec 2002 | A1 |
20030043785 | Liu et al. | Mar 2003 | A1 |
Number | Date | Country |
---|---|---|
0718948 | Jun 1996 | EP |
0723325 | Jul 1996 | EP |
0949734 | Oct 1999 | EP |
Number | Date | Country | |
---|---|---|---|
20030212513 A1 | Nov 2003 | US |
Number | Date | Country | |
---|---|---|---|
60438159 | Jan 2003 | US | |
60359544 | Feb 2002 | US |