System and method for providing load control and management based on load identification

Abstract

A method for providing load control and management based on load identification, the method comprising: Inserting a load power supply device (4) comprising: a power input (135), at least one power output (10, 12) for at least one consumer or load (LD), a plurality of sensors (170, 172, 174) configured to sense voltage and current at the at least one power output, and a processor (132); Providing (18) load identification based on the sensed voltage and current; Providing (20, 22, 24) load control and management by the processor based on the load identification, Providing a remote device (8) remote from the load power supply devices, which includes an online learning mechanism to detect context-dependent electrical activities that can be adaptively adjusted for individual usage scenarios; Communicating (14) between the load power supply devices and the remote device; and Recognizing a user's behavior pattern and providing an occupancy or usage type estimate based on different usage scenarios.

Description

[0001] This invention was made with government support under DE-EE0003911, awarded by the Department of Energy's National Energy Technology Laboratory. The government retains certain rights in this invention. BACKGROUND area

[0002] The disclosed concept relates generally to electrical loads and, more particularly, to load power devices and load power supply devices that supply power to such loads. The disclosed concept relates to energy systems that include load power supply devices that supply power to electrical loads and, more particularly, to load power devices that supply power to such loads. Background information

[0003] Power consumption monitoring and energy management of plug-in loads (PELs) within buildings is often overlooked. By knowing the operating mode (e.g., operating status) of an electrical load, energy savings can be achieved through effective management and control. Furthermore, the operating mode and energy consumption of electrical loads must be communicated to building management systems automatically, at low cost, and in a non-intrusive manner.

[0004] Electrical loads often exhibit unique characteristics in their electrical output signals (e.g., voltage, current, power). Such load characteristics provide a possible mechanism for identifying an operating state (e.g., active; standby, but not limited to this) by analyzing the electrical output signals.

[0005] Previous proposals include the use of wavelet coefficients obtained from wavelet transforms and event detection to detect load switching. Also, basic power quality-related signatures (e.g., one or more of the following: apparent power, cos(phi), active energy, reactive energy, frequency, period, RMS current, instantaneous current, RMS voltage, instantaneous voltage, current swing THD percentage (THD = total harmonic distortion), voltage swing THD percentage, current waveform spectral component, voltage waveform spectral component, active power waveform spectral component, reactive power waveform spectral component, network quality percentage, time, date, temperature, and humidity) are used as a signature to identify a load and its operating status.

[0006] For example, a load is in standby mode if the current value obtained for each load current is less than a percentage of the maximum for each load current in the normal operating mode. If an electrical device plugged into a main outlet consumes less power than a suitable threshold (e.g., that of standby power), then those peripheral outlets can be automatically turned off to cap further power consumption. While this may be true for some electrical devices, other electrical loads (e.g., microwaves; refrigerators, but not limited to) have an on-off behavior that is a unique inherent behavior of the electrical load itself (e.g., a desktop computer in a low-power mode).It is not user-friendly if the "OFF" cycle of such a device is mistakenly considered a "standby" mode and such a load is then switched OFF.

[0007] Furthermore, from US 2016 / 0 156 225 A1 a load power supply device with a power input, at least one power output for at least one load, a plurality of sensors, and a processor is known.

[0008] The plurality of sensors are configured to sense voltage and current at the at least one power output, and the processor is configured to provide real-time execution of: (a) a plurality of load identification algorithms, and (b) event and operating mode detection for the at least one load.

[0009] There is still scope for improvement in systems and processes that include load power supply devices. SUMMARY

[0010] These and other requirements are met by embodiments of the disclosed concept, which provides load identification based on sensed voltage and current, and load control and management based on load identification.

[0011] According to the invention, a method and a system for providing load control and management based on load identification are provided as claimed.

[0012] The method for providing load control and management based on load identification comprises: deploying a load power supply device having: a power input, at least one power output for at least one load; a plurality of sensors constructed to sense voltage and current at the at least one power output, and a processor; providing load identification based on the sensed voltage and current; providing load control and management based on the load identification; providing a remotely located deviceA remote device remote from the load power supply devices that includes an online learning mechanism to detect context-dependent electrical activities that can be adaptively adjusted for individual usage scenarios, communicating between the load power supply devices and the remote device, and detecting a user's behavior pattern and providing an occupancy or usage type estimate based on different usage scenarios.

[0013] As a further aspect of the disclosed concept, a system for providing load control and management based on load identification comprises, among other things: a plurality of load power supplies, each of the load power supplies having: a power input; at least one power output for at least one load; a plurality of sensors configured to sense voltage and current at the at least one power output; and a processor configured to provide: (a) load identification based on the sensed voltage and current, and (b) load control and management based on the load identification; and a remote energy management system remote from and in communication with the load power supplies. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] A full understanding of the disclosed concept can be obtained from the following description of the preferred embodiments when read in conjunction with the accompanying drawings in which: Fig. 1 is a block diagram of a load identification (ID) based control and management system including a smart receptacle (SR) according to embodiments of the disclosed concept. Fig. 2 is a block diagram of SR load control / management strategies / rules for the SR of the Fig. 1. Fig. Figure 3 is a flowchart of a plug-in load (PiL) management compliance verification function for the SR of the Fig. 1. Fig. Figure 4 is a flowchart of a CLO relay control signal generator function (CLO = Controllable Load Outlet) for the SR of the Fig. 1. Fig. Figure 5 is a flowchart of a momentary manual CLO control function of the SR of the Fig. 1. Fig. Figure 6 is a graphical representation of an automatic pre-OFF delay versus a confidence level regarding a user absence for the SR of the Fig. 1. Fig. Figure 7 is a flowchart of a local usage type or occupancy estimation function for the SR of the Fig. 1. Fig. Figure 8 is a flowchart of a local automatic CLO control function for the SR of the Fig. 1. Fig. Figure 9 is a flowchart of an SR push button handling function for the SR of the Fig. 1. Fig. 10 is a functional block diagram for the SR of the Fig. 1. Fig.11 is a block diagram of a remote energy management system (REMS) including a plurality of SRs according to one embodiment of the disclosed concept. DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] As used herein, the term “number” shall mean one or an integer greater than one (i.e., a plurality).

[0016] As used herein, the term "processor" shall mean: a programmable analog and / or digital device capable of storing, retrieving, and processing data; a computer; a workstation; a personal computer (PC); a controller; a microprocessor; a microcontroller; a microcomputer; a digital signal processor (DSP); a central processing unit (CPU); a mainframe computer; a minicomputer; a server; a network processor; or any suitable processing device or apparatus.

[0017] As used herein, the term “load power supply device” shall mean a power strip, a smart power strip, a connector, a smart connector, a receptacle, a smart receptacle, a plug, and a single-phase UPS, a power / energy meter, and a power / energy monitoring device at a circuit branch level.

[0018] The disclosed concept is described in connection with exemplary load power devices, loads, and exemplary load characteristics, although the disclosed concept is applicable to a wide range of load power devices, loads, and a wide range of load characteristics.

[0019] The disclosed concept can be implemented, for example, through power strips, intelligent power strips, outlets, plugs, power / energy meters, branch-level power / energy monitoring for building energy management, single-phase UPSs, building energy management systems, intelligent connection zone networks, and building-level load control for load shedding and demand response.

[0020] The disclosed concept provides load identification (ID) based on load control and management in, for example, an improved or enhanced multiple socket / socket device, such as an intelligent connection or SR (SR = smart receptacle) 4 ( Fig. 1 and Fig.10) or an improved wiring device (e.g., a smart wall outlet), but is not limited to this. The SR 4 distributes power to downstream plugged-in devices similar to conventional power strips and outlets, but with a predetermined ALWAYS-ON load outlet (ALO) 10 and a controllable load outlet (CLO) 12, as shown in Fig. 10. Uncontrolled load devices are plugged into the ALO 10 and controlled devices are plugged into the CLO 12. The SR 4 preferably reports an energy or power consumption profile 16 ( Fig. 11) for each outlet in real time and identifies device types including non-permissible load devices that are prohibited based on a building management rule.

[0021] The multiple SRs within a zone (e.g., a zone area selected by a user that represents a specific usage scenario) work together as a zonal SR network. In the zonal SR network, each SR, such as 4, 5, 6 of the Fig. 11, is used to identify the type and operating status of a number of pluggable load devices using the electrical waveforms at the outlet level. An online learning mechanism is used to detect the context-dependent electrical activities, which can be adaptively adjusted for individual usage scenarios. Each SR 4, 5, 6 preferably also provides energy or power usage monitoring and responses to ON / OFF control commands. The SRs can be integrated with zonal SR analysis software (e.g., part of the remote energy management system or REMS) 8, which is implemented in Fig.11) located in a remote device (e.g., a PC or a smartphone, but not limited thereto), communicate via a communication network 14, such as the exemplary WiFi network. The information from individual SRs is consolidated to the zonal SR analysis software. An artificial intelligence (AI) learning algorithm is used to recognize user behavior patterns and to provide a usage type or occupancy estimate that is specifically tailored to the specific usage scenario. Users are also allowed to configure (e.g., customize) the load management and control rules (e.g., strategies) based on their own specific scenarios. In the zonal communication network 14 of the Fig.11, each SR 4, 5, 6 has a unique ID 4', 5', 6' (e.g., a unique IP address) that can associate the corresponding workspace with a specific occupant or user for selecting management and control rules, as well as for informing about compliance. This allows the corresponding SR sockets 10, 12 to be mapped to the user workspace.

[0022] It is believed that the combination of the disclosed load identification and sensorless occupancy estimation technologies and the SR and zonal SR network can lead to the next generation of smart sockets - the fundamental, modular building block of a flexible, highly efficient building-level management system.

[0023] With reference to Fig.1 shows the system 2 for load identification (ID) based on control and management. Consumer or load ID information 19 (e.g., Load.ID and Load.Opr_Sts; ID and operating status) from the load ID function 18 is the main input to the system 2 at the SR 4. The core functions of the system 2 include load management compliance verification 20, local occupancy estimation 22, and automatic control 24 for the controlled outlets, such as CLO 12 of the Fig. 10.

[0024] Fig.Figure 2 shows SR load control / management strategies / rules and provides a summary of how the rules and strategies relate to each other. Effective control and management of plug-in loads (PiL) in a building can be ensured by enforcing two sets of load management and control rules. First, building PiL management rules refer to the rules that building managers use to regulate the use of PiLs in buildings, as well as to verify end-user compliance with the rules. These are grouped into three exemplary levels: (1) Mgt_Policies_Level1 or Mgt_Rules_Level1 30; (2) Mgt_Policies_Level2 or Mgt_Rules_Level2 32; and (3) Mgt_Policies_Level3 or Mgt_Rules_Level3 34. Secondly, SR (relay) control strategies refer to the states or conditions when the SR socket relay(s) (e.g. Relay (RL) 13 of the Fig.10) should be automatically switched on / off. These can be based on both local and remote states: (1) locally provided automatic socket control strategies 36; and (2) remotely provided automatic socket control strategies 38.

[0025] Building PiL management policies (Mgt_Policies_Level1 30 and Mgt_Policies_Level2 32) support two main reasons why PiLs must be managed in buildings: energy conservation improvements and safety (e.g., the use of space heaters, but not limited to these). Building PiL management policies are the building policies that building managers select to regulate the use of PiLs in buildings to address these issues. Table 1 shows a few examples of building PiL management policies along with their inherent violation conditions. Table 1 Level Rule Injury conditions Actionable feedback Applicable load examples 1.1 Always leave critical loads ON It is detected that critical loads are plugged into controllable sockets or outputs Flag warning - potential damage to equipment; users are advised to switch the load to a non-controllable socket PCs; network equipment 1.2 Ensure that all controllable loads are properly controlled Controllable loads are detected when they are plugged into non-controllable sockets or outlets Flag warning - Devices are not controlled properly; users are suggested to switch the load to a controllable socket User assignment 1.3 Prohibit the use of certain load types The use of prohibited loads is detected Flag Alarm - Users are prompted to unplug the specific plugged-in load; after a time delay, power is removed from the specific load (this only applies to the controllable socket) User assignment 2.1 Reducing the use of low-efficiency loads The use of a load model with low efficiency is detected Flag warning - Users are advised to replace the device with a highly efficient load or consumer model Incandescent lamp loads; CRT 2.2 Reducing certain types of personal load usage The use of a non-recommended personal device is detected Flag warning - Users are advised not to use personal loads or consumers, but to use shared facilities in a public area User assignment 2.3 Ensure that loads go into power saving mode The plugged-in loads are detected if they never go into low-power mode Flag warning - Users are suggested to set up a power saving mode for the specific device Just as critical

[0026] How to enforce compliance with these rules is always challenging for PiLs such as plug-in devices, as these devices are typically distributed over a relatively large area. Auto-verification and feedback of compliance status can be provided centrally to building managers to help simplify the process. To verify whether the use of a PiL complies with building rules, the association between the loads (or load types) and the rules is established. Each load is assigned or associated with one or more management rules, either through general load types or customized load groups.

[0027] For implementation, this assignment / association is defined by a load management policy association table. A predefined association table can be provided by the system. The association table can also be customized by building managers or users based on their specific usage scenarios.

[0028] Table (2) (Association_Table_Load_Mgt_Policies_Level1) provides examples of the association table for a set of exemplary, general load types. Details on how the association table matches association words are discussed below.

[0029] Each management rule has a predefined bit position in the association word, as described in a mask code (e.g., 0x04 or bit 2 for critical loads, 0x02 or bit 1 for controllable loads, and 0x01 or bit 0 for prohibited loads). Each general load type has three association words for the three exemplary management rule levels 30, 32, and 34. The association words are compared with the corresponding mask codes to indicate the rules applicable to that facility class. The autoverification routine (PiL_Mgt_Compliance_Verification function 20 of the Fig. 1 and Fig. 3, discussed below) checks the compliance status of the PiL facility, i.e., whether the user complies with the applicable rules associated with its facility class.

[0030] Table 3 (Association_Table_Load_Mgt_Policies_Level2) and Table 4 (Association_Table_Load_Mgt_Policies_Level3) provide examples of the association tables for the exemplary set of general load types. Table 2 General load type Critical Controllable Forbidden Level1_AssociationWord or Level1_AssociationWord PC + 0x0004 monitor + 0x0002 Refrigerator + 0x0002 Room heating + 0x0001 light bulb + 0x0002 CRT + 0x0002 Printer + 0x0002 Table 3 General load type Energy savings Not wanted Low efficiency Level2 AssociationWord or Level2 AssociationWord PC + 0x0004 monitor 0x0000 Refrigerator + 0x0002 Room heating 0x0000 light bulb + 0x0001 CRT + 0x0001 Printer + + 0x0006 Table 4 General load type Free Error detection Energy Star or energy class evaluation Level3_AssociationWord or Level3_AssociationWord PC + 0x0001 monitor + 0x0001 Refrigerator + 0x0002 Room heating 0x0000 light bulb 0x0000 CRT 0x0000 Printer 0x0000

[0031] The applicable loads assigned to Mgt_Policies_Level1 30 are exclusive, meaning that a facility class can only be assigned one Mgt_Policy or Management_Rule in Level1, and each facility class is assigned by one of the Level1 management rules. Conversely, a load type can be assigned to multiple management rules in Level2 32. As a non-limiting example, as shown in Table 3, a desktop printer can be assigned two management rules in Level 2, e.g., Energy Savings and Not Desired. In this case, the building rule specifies that a printer is a discouraged personal facility that should enter a power-saving mode when not in use.

[0032] The PiL_Mgt_Compliance_Verification function 20 ( Fig. 1 and Fig.3) provides for automatic verification of user compliance with the PiL management rules. This includes messages that communicate the user's compliance status 47 of the PiL facilities, as well as a Disable_Cmd or deactivation_command 21 ( Fig. 1) at 50 ( Fig. 3) to control the CLO 12 ( Fig.10), if applicable. The inputs to function 20 include: Outlet_Header (e.g., an ID of the outlet, such as the SR number (or a unique IP address) and the outlet number (i.e., corresponding to CLO or ALO)); Load.ID + Load.Opr_Status (Last.ID + Last.Opr_Status 19 from the Last_ID function 18 at 40; PiL_Mgt_Policies (41) from the PiL_Mgt_Policy_Database (43) at 42; and PiL_Mgt_Policies_AssoTable or PiL_Mgt_Rule_Association_Table 45 from the PiL_Mgt_Policy_Database 43 at 44, which verifies the compliance status of the PiL facility based on the three association tables 45. The outputs of the function 20 include: Compliance_Status or Compliance_Status 47 to a REMS-PiL_Mgt_Compliance_Status or REMS-PiL_Mgt_Compliance_Status indicator 51 (Figure 1); and Disable_Cmd 21 to the CLO_Relay_Ctrl_Signal_Generator orCLO_Relay_Control_Signal_Generator 66 at 50. As in . Fig. As shown in Figure 3, function 20 receives the identified power load type at 40, obtains and verifies the applicable management rules 41 at 42 and 44, steps through the compliance states at 46, if applicable, and reports the exceptions accordingly at 48. Loads are disabled, if applicable, at 50. For some load types, the presence of this type of load is a violation of the building code. For other load types, how the load is used is significant.

[0033] SR socket (relay) control and strategies consider various socket control ON / OFF conditions or states. One of the building PiL management rules is to ensure that all controllable loads can be switched ON / OFF correctly based on the need for load usage, with minimal negative impact, while simultaneously achieving maximum savings. The control, i.e., the ON / OFF switching, of the socket relay (e.g., RL 13 of the Fig. 10) is fundamentally determined by the following ( Fig.1): (1) manual control of a user (local / remote) through the SR-CLO_Instan_Manual_Ctrl or SR-CLO_Instante_Manual_Control function 60; (2) automatic detection of the user's occupancy through local, automatic control through the local occupancy estimation function 22 and the CLO_Local_Auto_Ctrl or CLO_Local_Automatic_Control function 24; (3) a higher-level building decision related to a building load management rule to deactivate the CLO 12 through the management compliance verification function 20; and (4) a higher-level building decision related to building load shedding / building load demand response to provide remote, automatic control through the REMS-Building_Level_CLO_RemoteA_Ctrl function 63 and the SR-CLO_Remote_Ctrl_Cmd_Handling function 64.SR-CLO-Remote_Control_Command_Processing-Function 64 to be provided (provision of e.g. RemoteM_Instan and RemoteM_wDelay; immediate and delayed remote manual control).

[0034] For one implementation, the four socket control signals 61, 25, 21, 65 from the above four sources are combined by the CLO relay control signal generator function 66 ( Fig.1) are combined to determine an ON / OFF switching of the SR's CLO 12. The first signal is the Instant_Manual_Cmd signal 61 (either a locally provided instant manual ON / OFF switching (LocalM_Instan) from a Pushbutton_Code_Handling 27 or a remotely provided instant manual ON / OFF switching (RemoteM_Instan) from the REMS-CLO_RemoteM_Ctrl_Interface 62 via the SR_CLO_Remote_Ctrl_Cmd_Handling function 64). The second signal is the Local_Auto_Cmd or.Local_Auto_Command signal 25 (from function 24 and derived from the local occupancy estimation function 22), which accounts for real-time scheduling, remotely scheduled manual OFF with timer delay, locally scheduled manual OFF with timer delay (local manual control does not support the delayed ON action), an optional external occupancy sensor 23 (shown with a dash-dotted line), and load sensing (for master devices, power cycle-sensitive devices, and power cycle-insensitive devices, which are defined based on how sensitive these devices are to power cycling). The third signal is a Disable_Cmd 21 (the output of the PiL management compliance verification function 20; the disable command is applied only to the controllable outlet 12; for the always-on outlet 10, only the alarm or warning message is issued).The fourth signal is the remote, automatic control signal Remote_Auto_Cmd or Remote_Auto_Command 65 at the building level, which takes demand response and load shedding into account. Any further automatic control signals are based on control decisions at a higher level.

[0035] The CLO relay control signal generator function 66 ( Fig. 1 and Fig. 4) generate the CLO_Relay_Ctrl_Signal or CLO_Relais_Steuer_Signal 68, which is used to physically control the CLO relay 13 ( Fig. 10). This function 66 is the last step of the CLO control logic, and the CLO_Relay_Ctrl_Signal 68 is provided by the DSP circuit 132 ( Fig. 10) is sent to a microcontroller (not shown) that interfaces with the REMS 8 and various local inputs (e.g. the optional external occupancy sensor 23; the push button 138 ( Fig. 10); the real-time clock or RTC (RTC = real-time clock) 137 ( Fig. 1 and Fig. 10), without being limited thereto) and outputs (e.g., RL 13, without being limited thereto). The inputs of function 66 of the figure include: (1) Instan_Manual_Cmd or Sofort_Manuell_Kommand 61 from the CLO_Instan_Manual_Ctrl function 60 ( Fig. 1) at 70; (2) Local_Auto_Cmd 25 from the CLO_Local_Auto_Ctrl function 24 ( Fig. 1) at 72; (3) Disable_Cmd 21 from the PiL_Mgt_ComplianceVerification function 20 ( Fig. 1) at 74; and (4) Remote_Auto_Cmd 65 from the CLO_Remote_Ctrl_Cmd_Handling function 64 ( Fig. 1) at 76. The output at 78 is the CLO_Relay_Ctrl signal 68. Table 5 shows four groups of control priority of locally provided automatic control, remotely provided automatic control, manual control, and disable command control, and how they interact to generate the final relay control signal 68. Table 5 Relay control signal (output) Local_Auto_Cmd or Local_Auto_Command Remote_Auto_Cmd or Remote_Auto_Command Instan_Manual _Cmd or Instant_Manual_Command _ Disable_Cmd or deactivation_ command 0 X X X 0 1 X X ↑ 1 0 X X ↓ 1 0 X ↓ X 1 0 0 ↑ X 1 1 1 ↑ X 1 1 ↑ 1 X 1 0 ↑ 0 X 1 0 ↓ X X 1

[0036] In Table 5, column 1, open (relay) = OFF (load) = 0 (control signal) and closed (relay) = ON (load) = 1 (control signal). Therefore, "↑" is a 0-to-1 transition and "↓" is a 1-to-0 transition.

[0037] The CLO_Instan_Manual_Ctrl function 60 ( Fig. 1 and Fig. 5) handles the logic between the two remote and local instantaneous manual control commands (RemoteM_Instan and LocalM_Instan) and generates the instantaneous manual control command 61 for the CLO. The inputs of function 60 include: (1) an enable word for a LocaIM_Instan_Bit or LocalM_Instan_Bit from the pushbutton handling function 80 ( Fig. 9) at 90 ( Fig. 5); (2) the LocalM_Instan_Bit at 90 ( Fig. 5) from the push button handling or processing function 80 ( Fig.9) at 90; (3) an activation word for a RemoteM_Instan_Bit or FernM_Sofort_Bit from the CLO_Remote_CtrI_Cmd_Handling function 64 ( Fig. 1) at 94; (4) the RemoteM_Instan_Bit from function 64 ( Fig. 1) at 94; and (5) the CLO relay status of RL 13 ( Fig. 10). The output of function 60 is the Instan_Manual_Cmd 61 to the CLO relay control signal generator 66 ( Fig. 1). The two instant manual control commands are complementary and set corresponding bits at 92 and 96, and a toggle mechanism is used to manually switch the socket relay 13 ON / OFF at 100. Table 6 shows how the Instan_Manual_Cmd command 61 is generated. Table 6 Instan_Manual_Cmd or Instant_Manual_Command Relay current status RemoteM_Instan_Bit or RemoteM_Sofort_Bit LocalM_Instan_Bit or LocalM_Sofort_Bit 1 0 pulse X 1 0 X pulse 0 1 pulse X 0 1 X pulse

[0038] The generation of the Remote_Auto_Cmd signal 65, the Instant_Manual_Cmd signal 61, and the Disable_Cmd signal 21 is easily derived by one skilled in the art. The following discusses the logic for the locally provided automatic control function 24 of the CLO.

[0039] The local use type or occupancy estimation function 22 ( Fig. 1 and Fig. 7) estimates the occupancy or usage status of the user based on the information available to SR 4 (with or without the optional external occupancy sensor 23). This approach can also be referred to as sensorless occupancy estimation. Occupancy estimation addresses the locally provided automatic control of the CLO 12 ( Fig. 10) with minimal negative impact on users. The inputs of function 22 include: (1) real time, as synchronized by the microcontroller real-time clock 137 ( Fig. 1 and Fig.10); (2) Status of the external occupancy sensor from the optional occupancy sensor 23; (3) Last_Manual_ON_RealTime from the CLO_Instan_Manual_Ctrl function 60 ( Fig. 1); (4) Load.ID + Load.Opr_Sts 19 from the load identification function 18 ( Fig. 1); and (5) Outlet_Ctrl_Strategies or Outlet_Control_Strategies 125 from the REMS Outlet_Ctrl_Strategies or REMS Outlet_Control_Strategies function 123. The outputs of function 22 include: (1) Occup_Est_Sts or Occupancy_Estimation_Status 139 to the CLO_Local_Auto_Ctrl function 24 ( Fig. 1); and (2) Auto_PRE_OFF_Timer or Auto_VOR_AUS_Timer (not shown) to the CLO_Local_Auto_Ctrl function 24 ( Fig. 1).

[0040] Function 22 estimates the occupancy (or absence) status of the user, i.e., Occup_Est_Sts 139 with Absent_Conf_Level or absence confidence level, determines the correct time to switch ON / OFF the CLO 12, i.e., Auto_PRE_OFF_Timer based on the Occup_Est_Sts 139, and allows the user to customize the applicable conditions, i.e., the Outlet_Ctrl_Strategies 125, to evaluate the Occup_Est_Sts 139. The following conditions are the Occup_Est_Conditions or occupancy estimation conditions for evaluating the confidence level of the user's occupancy / absence: (1) Real-time scheduling or RTS (RTS = real-time scheduling) at 112 ( Fig.7); (2) manual turn-on or MTO (e.g., the first seven hours after the CLO 12 has been turned ON provide a strong indication of user occupancy) at 114; (3) optional occupancy sensor 23 at 116; (4) PiL load sensing or PiLS (PiLS = Plugged-in Load Sensing) for master device operating mode or MSO mode (MSO = Master-Device Operating); power-cycling-sensitive operating mode or PSO (PSO = Power-Cycling-Sensitive Operating Mode); and power-cycling-insensitive operating mode or PISO (PISO = Power-Cycling-Insensitive Operating Mode); these include the load ID and operating status 19 from the load identification function 18 ( Fig. 1) at 118.

[0041] At 120, a load control attribute is determined based on a load control sensitivity association table (Table 11). Then, at 122, the outlet control strategies 125 ( Fig. 1) retrieved from the REMS 8.

[0042] If any of the four exemplary Occup_Est_Conditions or Occupancy_Estimation_Conditions at 124 change, then function 22 sets New_Occup_Sts_Detected = ONE or New_Occupancy_Status_Detected = ONE; begins evaluating the confidence level of occupancy (or absence of the user) at 126; assigns the corresponding Auto_PRE_OFF_Delay or Auto_PRE_OFF_Delay based on the trigger curve 110 of the Fig. 6 at 128; and updates Auto_PRE_OFF_Timer = Auto_PRE_OFF_Delay at 130. Otherwise, if there is no change in Occup_Est_Conditions at 124, and if Auto_PRE_OFF_Timer > 0, then Auto_PRE_OFF_Timer = Auto_PRE_OFF_Timer - 1 counts down at 131. Finally, after 130 or 131, Auto_PRE_OFF_Timer is updated at 133.

[0043] Fig.Figure 6 graphically plots the Auto_PRE_OFF_Delay (minutes) versus the user's absence confidence level. Table 7 shows an example of an assignment of Occup_Est_Sts and Absent_Conf_Level based on different Occup_Est_Conditions scenarios. The assignment for Absent_Conf_Level and Auto_PRE_OFF_Delay can be customized / configured by users based on their own usage scenarios.

[0044] Table 8 shows the occupancy detection logic and describes the interaction between the two MOFF_wDelay or MOUSE_withDelay conditions and the effect of the M_PRE_OFF_Delay or M_PRE_OFF_Delay. Table 7 I / O signal O Auto_PRE_OFF_Delay or Auto_VOR_AUS_Delay -1 5 hours 4 hours 3 hours 2 hours 1 hour 0 O Absent_Conf_Level or Absence_Confidence Level 1 2 3 4 5 6 7 O Occupancy Estimate Status Occupied or used Absent? Absent? Absent? Absent? Absent? Absent? O Local Auto_Ctrl Action or Local_Auto_Control_Action Switch ON Switch ON Switch ON Switch ON Switch ON Switch ON Turn off I Real-time scheduling X 1 1 0 0 1 0 I Manual Turn-ON I Occupancy sensor X X 1 1 X 0 0 I Pwr-Insensitive Device O-Status or operating status of the power-insensitive device X 1 0 0 1 0 0 I Master / Pwr-Sensitive Device O-Status or operating status of the master device / power-sensitive device 1 0 0 0 0 0 0 Table 8 Inputs expenditure I / O LocalMOFF_wDelay_Enabled or Local-MOUSE_with_delay_Enabled RemoteMOFF_wDelay_Enabled or Remote MOUSE with Delay Enabled MOFFwDelay_Enabled or MOFF withDelay_Enabled M_PRE_OFF_Delay or M_VOR_AUS_Delay M_PRE_OFF_Timer or M_VOR_AUS_Timer O 0 ↑ ↑ M_PRE_OFF_Delay =RemoteM_PRE_OFF_Delay M_PRE_OFF_Timer =M_PRE_OFF_Delay;RemoteM_PRE_OFF_Delay =0 O 1 ↑ ↑ O ↑ 0 ↑ M_PRE_OFF_Delay =LocalM_PRE_OFF_Delay M_PRE_OFF_Timer =M_PRE_OFF_Delay;Local_PRE_OFF_Delay = 0 I ↑ 1 ↑ M_PRE_OFF_Delay =LocalM_PRE_OFF_Delay+ M_PRE_OFF_Timer I 0 0 0 0 0 I 1 1 1 M - PRE - OFF - Timer counts down I 1 0 1 I 0 1 1

[0045] The CLO_Lokal_Auto_Ctrl function 24 ( Fig. 1 and Fig. 8) handles or processes the logic between the conditions that allow the automatic ON / OFF switching of the CLO 12 ( Fig.10). The inputs of function 24 include: (1) LocalMOFF_wDelay + LocalM_PRE_OFF_Delay (LocalM_wDelay) from the PushButton_Code_Handling function 27 ( Fig. 1) at 140; (2) RemoteMOFF_wDelay + RemoteM_PRE_OFF_Delay (RemoteM_wDelay) from the CLO_Remote_Ctrl_Cmd_Handling function 64 ( Fig. 1) at 142 (e.g. from the REMS 8 via a network or web GUI); and (3) Occup_Est_Sts 139 + Auto_PRE_OFF_Timer from the local occupancy estimation function 22 ( Fig. 1) at 146. The outputs of function 24 include: (1) Local_Auto_Cmd 25 to the generator function 66 of the CLO relay control signal 10 ( Fig.1) at 152; and (2) a LocalM_PRE_OFF_Delay (global). Function 24 uses three automatic control conditions, two of which are issued with user intervention (MOFF_wDelay_Conditions) at 144: (1) locally provided manual OFF control with time delay (LocalMOFF_wDelay: issued in response to the SR pushbutton 138 ( Fig. 10)); and (2) remote OFF control with time delay (RemoteMOFF_wDelay: triggered by a network GUI of the REMS 8 ( Fig. 1 and Fig. 10)). The third automatic control condition is determined by the local occupancy estimation function 22 ( Fig. 1) (Occup_Est_Conditions) generated using locally provided automatic ON / OFF switching control with time delay.

[0046] Table 9 shows the logic that describes the interaction between the aggregated MOFF_wDelay_Conditions and the Occup_Est_Conditions, the effect on the PRE_OFF_Timer and other actions. Table 9 expenditure Scenarios PRE_OFF_Timer Other actions Occupied or used ↑ PRE_OFF_Timer-1 (infinite) Local_Auto_Cmd =AN,New_Occup_Sts_Detected = NULL Absent<7 ↑ PRE_OFF_TimerA_PRE_OFF_Timer Local_Auto_Cmd =AN,New_Occup_Sts_Detected = NULL Absent>7 ↑ PRE_OFF_Timer=0 Local_Auto_Cmd =OFF,New_Occup_Sts_Detected = NULL Used ↑ +MOFF_wDelay_Enabled PRE_OFF_Timer-1 (infinite) Local_Auto_Cmd =AN,New_Occup_Sts_Detected = NULL Away<7 ↑ +MOFF _wDelay_Enabled PRE_OFF_Timer= max(A_PRE_OFF_Timer,M_PRE_OFFL_Timer) Local_Auto_Cmd =AN,New_Occup_Sts_Detected = NULL Away>7 ↑ +MOFF _wDelay_Enabled PRE_OFF_Timer= 0 Local_Auto_Cmd =OFF,New_Occup_Sts_Detected = NULL Used +MOFF _wDelay_Enabled ↑ PRE_OFF_TimerM_PRE_OFF_Delay Away<7 +MOFF _wDelay_Enabled ↑ PRE_OFF_Timer= max(A_PRE_OFF_Timer,M_PRE_OFF_Delay) Away>7 +MOFF _wDelay_Enabled ↑ not applicable or no information orPRE_OFF_DelayM_PRE_OFF_Delay not applicable or no information

[0047] When the PRE_OFF_Timer counts down to zero at 150, function 24 sets Local_Auto_Cmd = OFF at 152, resets MOFF_wDelay_Enabled to zero, and resets LocalMOFF_wDelay_Enabled or RemoteMOFF_wDelay_Enabled to zero, whichever is applicable.

[0048] The (DSP-side) PushButton_Code_Handling function 80 ( Fig. 9) interacts with the PushButton_Code or the push button code sent by the microcontroller function 27 ( Fig.1) at 160 for various CLO control commands (e.g., LocalM_wDelay; LocalM_Instan), and updates the CLO_Ctrl_Word or CLO_Control_Word accordingly. The inputs of function 80 include: (1) PushButton_Code from microcontroller function 27 at 160; (2) CLO_Relay_Status from the microcontroller routine (not shown); and (3) LocalM_PRE_OFF_Delay (global) from CLO_Local_Auto_Ctrl function 24 ( Fig. 1). The outputs of function 80 include: (1) an activation word for the CLO LocalM_Ctrl_Instan_Bit or CLO-LocalM_Control_Immediate_Bit; (2) the CLO LocalM_Ctrl_Instan_Bit; (3) an activation word for the CLO LocalMOFF_wDelay_Bit or CLO-Local_MOUSE_with_Delay_Bit; (4) the CLO LocalMOFF_wDelay_Bit; and (5) the CLO TimeDelay.LocalMOFF_wDelay or CLO TimeDelay.LocalMOUSE_with_Delay. Table 10 shows the logic of function 80 and Fig. 9 shows the flowchart.

[0049] The Load ID algorithm real-time implementation hardware platform for the SR 4 integrates the embedded Load ID, PiL control and management strategies, Wi-Fi communications, and a web service-based user interface. As described in Fig. 10, includes the SR 4 V / I-10. This allows System 2 to identify and warn if a load is not permitted on the CLO 12 or the ALO 10, or both.

[0050] The distribution of power to downstream plug-in load devices or PiL devices is similar to conventional multiple outlets or connections, but with the predetermined ALWAYS-ON load outlet (ALO) 10 and the controllable load outlet (CLO) 12 with relay / switch circuits (e.g., 120 V @ 60 Hz; 230 V @ 50 Hz) for the output control relay 13. A color-coded LED (LED = light emitting diode) 136 indicates a CLO status and a load compliance status. A mini SD card 69 ( Fig. 1) supports data logging, web page scripts, and load control / management rules. Web services support remote access to the SR 4. A push button 138 provides support for manual override of the CLO control and an OFF delay extension. The REMS 8 user interface ( Fig. 1) includes a real-time load usage status display, remote control of CLOs 12 ( Fig. 1) and a management and control configuration for plug-in loads or PiLMC configuration (PiLMC = Plug-in Loads Management and Control). Table 10 Push-button operation Push button code CLO_Ctrl_Cmd or CLO_Control_Command updates Press and hold the push button for >2 seconds LocalM_Ctrl_Instan CLO_ Ctrl_Cmd.Enable_Word.LocalM_Instan_Bit = 1;CLO Ctrl_Cmd.Cmd Word.LocalM_Instan_Bit =1 Press and hold the push button for <1 second LocalMOFF_wDelay If CLO_Relay_Status = 1, then ifCLO_Ctrl_Cmd.Enable_Word.LocalMOFF_wDelay_Bit = 0 andCLO_Ctrl_Cmd.Cmd_Word.LocaIMOFF _wDelay_Bit = 0, then CLO_Ctrl_Cmd.Enable_Word.LocalMOFF_wDelay_Bit = 1; CLO_Ctrl_Cmd.Cmd_Word.LocalMOFF_wDelay_Bit = 1; CLO_Ctrl_Cmd.Ctrl_TimeDelay.LocalMOFF_Delay =CLO_Ctrl_Cmd.Ctrl_TimeDelay.LocalMOFF_Delay + 30 minutes

[0051] In general, if the press-hold duration of the SR push button 138 ( Fig. 10) is longer than 2 seconds at 162 of the Fig. 9, then it is interpreted as an immediate manual ON / OFF control, and the command is for an ON or OFF action depending on the current status of the CLO 12 at 164. Otherwise, if the press-hold duration of the push button 138 is less than 1 second, then it is interpreted as a manual OFF control with time delay at 166, and a press-hold (< 1 second) extends the SR_PRE_OFF_Timer for a predetermined delay (e.g., half an hour, but not limited to this) at 168.

[0052] The Outlet_Ctrl_Strategies 125 are the conditions determined by the local occupancy estimation function 22 ( Fig. 1 and Fig. 7). This function 22 updates the local SR outlet control strategies based on the strategies sent from the microcontroller (not shown). The inputs are the Outlet_Ctrl_Strategies 125 from the REMS 8 or the SD card 69 by the microcontroller routine (not shown), and the outputs are the Outlet_Ctrl_Strategies. Two specific fields are required by function 22: (1) Outlet local control ON / OFF condition assignment - these are passed in the Outlet_Ctrl_Strategies (user can store up to eight customized control strategies that can be provided by the SD card 69 ( Fig.1), and it can also be customized by a user through the network or web GUI); and (2) Load Control Sensitivity Association Table (Table 11), which is used to define how sensitive the general facility classes are to the cyclic behavior of power and the usage type or occupancy of a user. Table 11 shows the Control_Strategies or ON / OFF-Conditions_AssoTable and the Control_ONConditions_AssoTable. Table 11 General load class master Power cycle sensitive Power cycle insensitive Load_CtrlSensitivity_Association Word or Load_ControlSensitivity_AssociationWord PC + + 0x0006 monitor + 0x0002 Refrigerator 0x0000 Room heating + 0x0001 light bulb + 0x0001 CRT + 0x0002 Printer

[0053] In the example association word in Table 1, power cycle insensitive is 0x0001 (bit 0), power cycle sensitive is 0x0002 (bit 1), and master is 0x0004 (bit 2). These bits can be ORed (as shown, for example, with PC = 0x0006).

[0054] For user interaction with PiL control and management, websites are preferably used, which allow the individual customization of load management / control rules and strategies by users. For PiL management rule configuration at the building level, the user can fill out a table similar to Tables 2-4. The resulting information is the Struct Mgt_Policies_AssoTable_Strct and the Generic_Mgt_Policy_AssoTable or Generic_Mgt_Rule_Association_Table

[25] , which contains, for example, 25 general facility classes. For the socket control strategy configuration, the user provides two units of information. First, a simple questionnaire helps to determine the user's behavior and the planned use of SRs (e.g., example questions could be: Do you have a regular work schedule?; What does your normal work schedule look like?; Do you use a usage type orOccupancy sensor for the SRs?; Do you want to use the ALO device as the master device to control CLO devices?). Second, the answers to the above questions help set the outlet local control ON / OFF conditions and assign the significant level for each condition. The resulting information is the Outlet_Ctrl_Strategy struct Outlet_Local_Ctrl_Strategies. This information forms the basis for occupancy status estimation and, consequently, reliable automatic control decisions for controlled outlets. The resulting information is the Load_CtrlSensitivity_AssoTable_Strct struct.

[0055] The disclosed concept allows occupants and building energy managers to have contextual visibility into actual occupant activity and behavior patterns, thereby gaining a better understanding of minimum energy supply demand and where energy is wasted. This contextual information enables further energy-efficient actions for further energy savings potential.

[0056] The disclosed concept can not only directly provide energy savings, but also improvements in usage and user acceptance. The latter factors are essential to enabling true adoption and compliance with PiL control and management solutions and consequently enable / improve actual energy savings from PiL power consumption.

[0057] It is believed that the disclosed concept can provide a greater than 10% reduction in energy consumption at the plug level. The disclosed SR 4 with integrated load ID is capable of achieving improved energy savings through automatic control of the CLO 12. This improves visibility, identifying actionable information and further savings opportunities, and reduces the negative impact due to a potential (perceived) disruption to workflow through an estimated 10% reduction in nuisance triggering of the CLO control of the SRs compared to known control solutions for an improved multiple socket orAPS (APS = advanced power strip) reduces installation costs by reducing the time spent on initial setup and configuration by at least half, with the rate of reduction increasing with larger system deployments, and reduces ongoing maintenance costs (recommissioning costs) due to improved compliance.

[0058] While specific embodiments of the disclosed concept have been described in detail, it will be apparent to those skilled in the art that various modifications and alternatives to those details could be developed in light of the overall teachings of the disclosure. Accordingly, the specific arrangements disclosed are intended to be illustrative only and are not intended to limit the scope of the disclosed concept, which is to be accorded the full breadth of the appended claims and any and all equivalent embodiments thereof. 36340 LIST OF REFERENCE SYMBOLS 2 systems 4 improved multiple sockets / socket devices, such as an intelligent connection or SR (smart receptacle) 4' unique ID 5 SR 5' unique ID 6 SR 6' unique ID 8 REMS 10 ALWAYS-ON load outlets (ALO = ALWAYS-ON load outlet) 12 Controllable Load Outlet (CLO) 13 Relays (RL) 14 Communication network 16 Energy or power consumption profile 18 Last ID function 19 Load ID information (Load.ID + Load.Opr_Status or Last.ID + Last. Operation_Status) 20 Load management compliance verification function (PiL_Mgt_Compliance_Verification function or PiL_Mgt_Einhaltes_Verifikations-Funktion) 21 Disable command (Disable_Cmd or Deactivation_Command) 22 Local occupancy estimation function 23 optional external usage type or occupancy sensor 24 locally provided, automatic control function of the CLO (CLO_Local_Auto_Ctrl or CLO_Lokal_Auto_Steuerung) 25 Local_Auto_Cmd or Local_Auto_Command signal 27 Microcontroller function (Pushbutton_Code_Handling or Pushbutton_Code_Processing) 30 building management rules for pluggable loads (Mgt_Policies_Level1 or Mgt_Rules_Level1) 32 building management rules for pluggable loads (Mgt_Policies_Level2 or Mgt_Rules_Level2) 34 Building Management Rules for Pluggable Loads (Mgt_Policies_Level3 or Mgt_Rules_Level3) 36 locally provided automatic control strategies of the socket 38 remote automatic control strategies of the socket 40 steps 41 PiL_Mgt_Policies or PiL_Mgt_Rules 42 steps 43 PiL_Mgt_Policy_Database or PiL_Mgt_Rule_Database 44 steps 45 association tables (PiL_Mgt_Policies_AssoTable or PiL_Mgt_Rules_AssoziierungsTabelle) 46 steps 47 Compliance status 48 steps 50 steps 51 REMS PiL_Mgt_Compliance_Status- or REMS_PiL_Mgt_Conformity_Status-Display 60 SR CLO_Instan_Manual_Ctrl - or SR-CLO_Instant_Manual_Control_Function 61 Instantaneous Manual Command Signal (Instan_Manual_Cmd) 62 REMS CLO_RemoteM_Ctrl_Interface or REMS-CLO_RemoteM-Control_Interface 63 REMS Building-Level_CLO_RemoteA_Ctrl- or REMS Building-Level_CLO_RemoteA_Control-Function 64 SR CLO_Remote_Ctrl_Cmd_Handling- or SR-CLO_Remote_Control_Command_Processing-Function 65 remote automatic control signal at building level (Remote_Auto_Cmd or Fern_Auto_Kommand) 66 CLO relay control signal generator 68 CLO_Relay_Ctrl_Signal or CLO_Relais_Steuer_Signal 69 Mini SD card 70 steps 72 steps 74 steps 76 steps 78 steps 80 Push button handling or processing function (PushButton_Code_Handling or PushButton_Code_Processing (DSP side)) 90 steps 92 steps 94 steps 96 steps 98 steps 100 steps 110 Trigger curve 112 steps 114 steps 116 steps 118 steps 120 steps 122 steps 123 REMS Outlet_Ctrl_Strategies or REMS socket control strategies function 124 steps 125 Outlet_Ctrl_Strategies or Outlet_Control_Strategies 126 steps 128 steps 130 steps 131 steps 132 DSP circuit 133 steps 134 Wi-Fi RF module 135 Power input 136 color-coded LEDs (LED = light emitting diode) 137 Real-time clock (RTC) 138 push button 139 Occup_Est_Status or Occupancy_Estimation_Status 140 steps 141 Operating mode identification 142 steps 144 steps 146 steps 148 steps 150 steps 152 steps 160 steps 162 steps 164 steps 166 steps 168 steps 170 voltage sensor 172 Current sensor 174 Current sensor

Claims

[1] A method for providing load control and management based on load identification, wherein the method comprises: Insertion of a load power supply device (4) comprising: a power input (135), at least one power output (10, 12) for at least one consumer or load (LD), a plurality of sensors (170, 172, 174) configured to sense voltage and current at the at least one power output, and a processor (132); Provision (18) of load identification based on the sensed voltage and current; Provision (20, 22, 24) of load control and management by the processor based on load identification, Providing a remotely located facility or remote facility (8) away from the load power supply facilities, which includes an online learning mechanism to detect context-dependent electrical activities that can be adaptively set for individual usage scenarios; Communicate (14) between the load power supply facilities and the remote facility; and Identifying a user's behavior pattern and providing an occupancy or usage type estimate based on different usage scenarios. [2] Method according to claim 1, further comprising enabling a configuration (8) of load management and control rules. [3] Method according to claim 1, further comprising providing a sensorless occupancy or usage type estimation (22). [4] The method of claim 1, further comprising: Detecting an activation (27; 162; 164) of an input element (138) of one of the load power supply devices for longer than a first predetermined time and responding to it by changing an on or off state of one (12) of the at least one power output(s); and Detecting an activation (27; 166) of the input element for a shorter period than a shorter second predetermined time and, in response, switching off one of the at least one power output(s) after a third predetermined time. [5] The method of claim 1, further comprising: providing a device (8) that includes an online learning mechanism to detect context-dependent electrical activities that can be adaptively set for individual usage scenarios; communicating (14) between the load power supply devices and the device that includes the online learning mechanism; and detecting a user's behavior pattern and providing a usage type estimate based on different usage scenarios. [6] A system (2) for providing load control and management based on load identification, wherein the system comprises: a plurality of load power supply units (4, 5, 6), each of the load power supply units comprising the following: a power input (135); at least one power output (10, 12) for at least one consumer or load (LD); a plurality of sensors (170, 172, 174) designed to sense voltage and current at the at least one power output; and a processor (132) designed to provide: (a) load identification (18) based on the sensed voltage and current, and (b) load control and management (20, 22, 24) based on the load identification; and a remote energy management system (8) that is located remotely from and in communication with the load power supply facilities, wherein the load power supply facilities and the remote energy management system form a zonal communication network (14); and wherein each of the load power supply facilities has a unique identifier (4', 5', 6') to associate a corresponding workspace with a specific occupier for selecting load management and control rules. [7] System (2) according to claim 6, wherein the load control and load management are based on a first set of load control rules (30) and a second set of load management rules (32); wherein the first set includes locally provided automatic socket control strategies (36) and remotely provided automatic socket control strategies (38); and wherein the second set includes a plurality of load management rules to control the use of loads in buildings and to verify user compliance with the load management rules, [8] A system (2) for providing load control and management based on load identification, wherein the system comprises: a plurality of load power supply units (4, 5, 6), each of the load power supply units comprising the following: a power input (135); at least one power output (10, 12) for at least one consumer or load (LD); a plurality of sensors (170, 172, 174) designed to sense voltage and current at the at least one power output; and a processor (132) designed to provide: (a) load identification (18) based on the sensed voltage and current, and (b) load control and management (20, 22, 24) based on the load identification; and a remote energy management system (8) that is located remotely from and in communication with the load power supply facilities, wherein the load control and load management are based on a first set of load control rules (30) and a second set of load management rules (32); wherein the first set includes locally provided automatic socket control strategies (36) and remotely provided automatic socket control strategies (38); and wherein the second set includes a variety of load management rules to regulate the use of loads in buildings and to verify user compliance with the load management rules, wherein the load control rules include (1) local or remote manual control (60); (2) local automatic control based on a user’s usage pattern (24, 22, 20); and (3) remote automatic control (63, 64), wherein the locally provided automatic control provides for an automatic switching OFF of one of the at least one power output as a function of a confidence level (139) of the absence of a user. [9] System (2) according to claim 7 or 8, wherein the load management rules include a plurality of stages (30, 32, 34), each of which associates a plurality of loads or load types with the load management rules. [10] System (2) according to claim 9, wherein a load management rule association table (45) defines the association of the loads or load types with the load management rules. [11] System (2) according to claim 9, wherein the stages comprise at least a first stage (30) and a second stage (32); wherein one of the plurality of load device classes is associated with only one of the load management rules in the first stage; and wherein each of the load device classes is assigned to one of the load management rules in the first stage. [12] System (2) according to claim 11, wherein one of the load types is assigned to a plurality of load management rules in the second stage. [13] System (2) according to claim 7 or 8, wherein the processor includes a management compliance verification function (20) designed to provide automatic verification of user compliance with the load management rules. [14] System (2) according to claim 13, wherein one (12) of the at least one socket is controllable (24) by the processor for a controlled load device; wherein the processor is further configured to output (20, 51) a user compliance status (47) of the user compliance or rule compliance and the controlled load device and a deactivation command (21) for controlling one of the at least one socket. [15] System (2) according to claim 7, wherein the load control rules include (1) local or remote manual control (60); (2) local automatic control based on a user’s usage pattern (24, 22, 20); and (3) remote automatic control (63, 64). [16] System (2) according to claim 8 or 15, wherein the remotely provided automatic control responds to a building load management rule (41) and / or to building load shedding / demand response considerations (63). [17] System (2) according to claim 6 or 8, wherein the user's occupancy or usage type is determined based on at least one of the following: (1) Real-time planning or allocation (137); (2) Manual switching on (138) of one of the at least one socket; (3) a usage type sensor (23); and (4) Load sensing for a master device operating mode, a power cycle sensitive operating mode and a power cycle insensitive operating mode. [18] System (2) according to claim 15, wherein the locally provided automatic control provides for an automatic switching OFF of one of the at least one power output as a function of a confidence level (139) of the absence of a user. [19] System (2) according to claim 6 or 8, wherein the remote energy management system (8) enables or activates a configuration of the load control and management from a web page that configures a variety of load management and control rules.

Images