Patent Grant
11954713
The present disclosure relates generally to the field of variable refrigerant flow systems, and more particularly to a method and system for apportioning electricity costs among multiple tenants of a facility served by a variable refrigerant flow system. In a variable refrigerant flow system, a refrigerant is conditioned by an outdoor condensing unit and circulated within a building to multiple indoor units, with a large portion of the electrical power consumption of the system attributable to the outdoor condensing unit.
Variable refrigerant flow systems are popular in multi-tenant buildings, such as apartment buildings, office buildings, or mixed-use facilities. For many multi-tenant buildings, electrical utility costs are billed to each tenant based on that tenant's electricity consumption, for example as determined by a meter that measures electricity consumption attributable to a tenant's unit in the building. However, because electricity consumption in a variable refrigerant flow system is largely due to the outdoor condensing unit that serves multiple tenants, a challenge exists to accurately apportion the costs of electricity consumption of the outdoor condensing unit among the tenants that it serves.
One implementation of the present disclosure is a variable refrigerant flow system for a building. The variable refrigerant flow system includes a plurality of indoor units, a first outdoor unit, an outdoor meter, and a variable refrigerant flow management system. The plurality of indoor units are configured to generate activation requests. The first outdoor unit is configured to receive the activation requests and, in response to the activation requests, provide a refrigerant to the plurality of indoor units. The outdoor meter is configured to provide an outdoor unit electricity consumption measurement. The variable refrigerant flow management system is configured to receive the outdoor unit electricity consumption measurement and activation data indicating the activation requests and apportion an outdoor share of the outdoor electricity consumption measurement to each of the plurality of indoor units based on the activation data.
In some embodiments, the first outdoor unit includes a compressor and the activation data includes a compressor request frequency for each of the plurality of indoor units. In some embodiments, the variable refrigerant management system apportion each outdoor share of the outdoor electricity consumption by calculating an outdoor consumption factor for each indoor unit based on the compressor request frequency corresponding to the indoor unit, calculating a power proportional index for each indoor unit by dividing the outdoor consumption factor corresponding to the indoor unit by a sum of the outdoor consumption factors for each of the plurality of indoor units, and multiplying the power proportional index for each indoor unit by the outdoor electricity consumption measurement.
In some embodiments, the variable refrigerant flow system also includes one or more additional outdoor units configured to receive activation request. The outdoor meter measures electricity consumption for the first outdoor unit and the one or more additional outdoor units to generate the outdoor unit consumption measurement. The variable refrigerant flow management system is further configured to apportion a share of the outdoor unit consumption measurement to the first outdoor unit based on the activation requests.
In some embodiments, the first outdoor unit includes a compressor and the activation data includes compressor requests frequencies. The variable refrigerant flow management system is further configured to apportion a share of the outdoor unit consumption measurement to the first outdoor unit based on the activation requests by determining a compressor run time of the first outdoor unit, determining a compressor total frequency based on the compressor request frequencies of the activation requests received by the first outdoor unit, calculating a consumption factor of the first outdoor unit based on the average compressor total frequency and the compressor run time, calculating a power proportional index for the first outdoor unit by dividing the consumption factor of the first outdoor unit by a sum of consumption factors of the one or more additional outdoor units and the consumption factor of the first outdoor unit, and multiplying the outdoor unit consumption measurement by the power proportional index.
In some embodiments, the variable refrigerant flow system also includes an indoor meter that measures electricity consumption of the plurality of indoor units to generate an indoor electricity consumption measurement. The variable refrigerant flow management system is further configured to apportion the indoor electricity consumption measurement among the plurality of indoor units.
Another implementation of the present disclosure is a method for operating a variable refrigerant flow system for a building. The method includes generating, generating, by a plurality of indoor units, activation requests and receiving, by a first outdoor unit, the activation requests. In response to the activation requests, the first outdoor unit provides refrigerant to the plurality of indoor units. The method also includes obtaining an outdoor unit electricity consumption measurement and activation data indicating the activation requests and apportioning an outdoor share of the outdoor electricity consumption measurement to each of the plurality of indoor units based on the activation data.
In some embodiments, the first outdoor unit includes a compressor and the activation data includes a compressor request frequency for each of the plurality of indoor units. In some embodiments, apportioning an outdoor share of the outdoor electricity consumption measurement to each of the plurality of indoor units based on the activation data includes calculating an outdoor consumption factor for each indoor unit based on the compressor request frequency, calculating a power proportional index for each indoor unit by dividing the outdoor consumption factor corresponding to the indoor unit by a sum of the outdoor consumption factors for each of the plurality of indoor units, and multiplying the power proportional index for each indoor unit by the outdoor electricity consumption measurement.
In some embodiments, obtaining the outdoor electricity consumption measurement includes measuring electricity consumption for the first outdoor unit and one or more additional outdoor units to generate a total outdoor unit consumption measurement and apportioning the outdoor unit consumption measurement to the first outdoor unit as a portion of the total outdoor unit consumption measurement based on the activation data. In some embodiments, the first outdoor unit includes a compressor and the activation data includes compressor request frequencies. Apportioning the outdoor unit consumption measurement to the first outdoor unit includes determining a compressor run time of the first outdoor unit, determining a compressor total frequency based on the compressor request frequencies of the activation requests received by the first outdoor unit, calculating a consumption factor of the first outdoor unit based on the compressor total frequency and the compressor run time, calculating a power proportional index for the first outdoor unit by dividing the consumption factor of the first outdoor unit by a sum of consumption factors of the one or more additional outdoor units and the consumption factor of the first outdoor unit, and multiplying the total outdoor unit consumption measurement by the power proportional index.
In some embodiments, the method also includes obtaining an indoor electricity consumption measurement of the plurality of indoor units and apportion an indoor share of the indoor electricity consumption measurement among the plurality of indoor units. In some embodiments, attributing each indoor share of the indoor electricity consumption measurement among the plurality of indoor units includes calculating an indoor consumption factor for each indoor unit based on a runtime and a capacity corresponding to the indoor unit, calculating an indoor power proportional index for each indoor unit by dividing the indoor consumption factor corresponding to the indoor unit by the sum of the indoor consumption factors for each of the plurality of indoor units, and multiplying the power proportional index for each indoor unit by the indoor electricity consumption measurement.
In some embodiments, the method also includes determining an indoor unit total consumption by adding the indoor share corresponding to the indoor unit and the outdoor share corresponding to the indoor unit. The method also includes generating a total indoor unit charge for each indoor unit by multiplying the indoor unit total consumption corresponding to the indoor unit by an electricity tariff rate. In some embodiments, the method also includes generating an electricity bill for each of a plurality of tenants. Each tenant corresponds to one or more of the plurality of indoor units.
Another implementation of the present disclosure is a system. The system includes an outdoor meter and a management system. The outdoor meter is configured to provide an outdoor electricity consumption measurement of an outdoor unit of a variable refrigerant flow system. The outdoor unit is configured to provide refrigerant to a plurality of indoor units in response to activation requests from the plurality of indoor units. The management system includes a processing system that has a memory and processor. The memory is structured to store instructions that are executable by the processor and cause the processing circuit to receive the outdoor electricity consumption measurement from the outdoor meter, receive activation data relating to the activation requests, and apportion the outdoor electricity consumption measurement among the plurality of indoor units based on the activation data.
In some embodiments, the activation data includes at least one of a compressor request frequency, an average compressor request frequency, a thermo-on time, an indoor unit model number, or an indoor unit capacity. In some embodiments, the processing circuit is caused to apportion the outdoor electricity consumption measurement among the plurality of indoor units based on the activation data by determining an outdoor consumption factor for each the plurality of indoor units based on the activation data, determining a power proportional index for each of the plurality of indoor units based on the outdoor consumption factors, and multiplying each power proportional index by the outdoor electricity consumption measurement.
In some embodiments, the system also includes an indoor meter that provides an indoor electricity consumption measurement of the plurality of indoor units. The indoor units are configured to provide runtime data. The processing circuit is further caused to receive the indoor electricity consumption measurement, receive runtime data relating to the runtimes of the plurality of indoor units, look up a capacity for each of the plurality of indoor units in a database, and apportion the indoor electricity consumption measurement among the plurality of indoor units based on the runtime data and the capacities.
In some embodiments, the plurality of indoor units are operable to regulate the temperature in various building zones corresponding to various tenants. The processing circuit is further caused to generate electricity bills for various tenants based on the apportioned outdoor electricity consumption measurements.
Variable Refrigerant Flow Systems
Referring now to
One advantage of VRF system 100 is that some indoor VRF units 104 can operate in a cooling mode while other indoor VRF units 104 operate in a heating mode. For example, each of outdoor VRF units 102 and indoor VRF units 104 can operate in a heating mode, a cooling mode, or an off mode. Each building zone can be controlled independently and can have different temperature setpoints. In some embodiments, each building has up to three outdoor VRF units 102 located outside the building (e.g., on a rooftop) and up to 128 indoor VRF units 104 distributed throughout the building (e.g., in various building zones). Building zones may include, among other possibilities, apartment units, offices, retail spaces, and common areas. In some cases, various building zones are owned, leased, or otherwise occupied by a variety of tenants, all served by the VRF system 100.
Many different configurations exist for VRF system 100. In some embodiments, VRF system 100 is a two-pipe system in which each outdoor VRF unit 102 connects to a single refrigerant return line and a single refrigerant outlet line. In a two-pipe system, all of outdoor VRF units 102 may operate in the same mode since only one of a heated or chilled refrigerant can be provided via the single refrigerant outlet line. In other embodiments, VRF system 100 is a three-pipe system in which each outdoor VRF unit 102 connects to a refrigerant return line, a hot refrigerant outlet line, and a cold refrigerant outlet line. In a three-pipe system, both heating and cooling can be provided simultaneously via the dual refrigerant outlet lines. An example of a three-pipe VRF system is described in detail with reference to
Referring now to
Outdoor VRF unit 202 is shown to include a compressor 208 and a heat exchanger 212. Compressor 208 circulates a refrigerant between heat exchanger 212 and indoor VRF units 204. The compressor 208 operates at a variable frequency as controlled by outdoor unit controls circuit 214. At higher frequencies, the compressor 208 provides the indoor VRF units 204 with greater heat transfer capacity. Electrical power consumption of compressor 208 increases proportionally with compressor frequency.
Heat exchanger 212 can function as a condenser (allowing the refrigerant to reject heat to the outside air) when VRF system 200 operates in a cooling mode or as an evaporator (allowing the refrigerant to absorb heat from the outside air) when VRF system 200 operates in a heating mode. Fan 210 provides airflow through heat exchanger 212. The speed of fan 210 can be adjusted (e.g., by outdoor unit controls circuit 214) to modulate the rate of heat transfer into or out of the refrigerant in heat exchanger 212.
Each indoor VRF unit 204 is shown to include a heat exchanger 216 and an expansion valve 218. Each of heat exchangers 216 can function as a condenser (allowing the refrigerant to reject heat to the air within the room or zone) when the indoor VRF unit 204 operates in a heating mode or as an evaporator (allowing the refrigerant to absorb heat from the air within the room or zone) when the indoor VRF unit 204 operates in a cooling mode. Fans 220 provide airflow through heat exchangers 216. The speeds of fans 220 can be adjusted (e.g., by indoor unit controls circuits 222) to modulate the rate of heat transfer into or out of the refrigerant in heat exchangers 216.
In
In the heating mode, the refrigerant is provided to indoor VRF units 204 in a hot state via heating line 232. The hot refrigerant flows through heat exchangers 216 (functioning as condensers) and rejects heat to the air within the room or zone of the building. The refrigerant then flows back to outdoor VRF unit via cooling line 224 (opposite the flow direction shown in
As shown in
Outdoor unit controls circuit 214 receives compressor frequency requests from one or more indoor unit controls circuits 222 and aggregates the requests, for example by summing the compressor frequency requests into a compressor total frequency. In some embodiments, the compressor frequency has an upper limit, such that the compressor total frequency cannot exceed the upper limit. The outdoor unit controls circuit 214 supplies the compressor total frequency to the compressor, for example as an input frequency given to a DC inverter compressor motor of the compressor. The indoor unit controls circuits 222 and the outdoor unit controls circuit 214 thereby combine to modulate the compressor frequency to match heating/cooling demand. The outdoor unit controls circuit 214 may also generate signals to control valve positions of the flow control valves 228 and expansion valve 230, a compressor power setpoint, a refrigerant flow setpoint, a refrigerant pressure setpoint (e.g., a differential pressure setpoint for the pressure measured by pressure sensors 236), on/off commands, staging commands, or other signals that affect the operation of compressor 208, as well as control signals provided to fan 210 including a fan speed setpoint, a fan power setpoint, an airflow setpoint, on/off commands, or other signals that affect the operation of fan 210.
Indoor unit controls circuits 222 and outdoor unit controls circuit 214 further store and/or provide a data history of one or more control signals generated by or provided to the controls circuits 214, 222. For example, indoor unit controls circuits 222 may store and/or provide a log of generated compressor request frequencies, fan on/off times, and indoor VRF unit 204 on/off times. Outdoor unit controls circuit 214 may store and/or provide a log of compressor request frequencies and/or compressor total frequencies and compressor runtimes. Data points are provided to a VRF management system 502 as shown in
The VRF system 200 is shown as running on electrical power provided by an energy grid 250 via an outdoor meter 252 and an indoor meter 254. According to various embodiments, the energy grid 250 is any supply of electricity, for example an electrical grid maintained by a utility company and supplied with power by one or more power plants. The outdoor meter 252 measures the electrical power consumption over time of the outdoor VRF unit 202, for example in kilowatt-hours (kWh). The indoor meter 254 measures the electrical power consumption over time of the indoor VRF units 204, for example in kWh. As shown in
Electricity Metering Configurations for VRF Systems
Referring now to
Referring particularly to
In many cases, each building zone is leased or otherwise corresponds to a particular tenant 310 (e.g., Tenant_2) responsible for the electrical utility costs for that building zone. In the first metering configuration 300, each of the multiple tenants 310 is responsible for the portion of the power consumption of the ODU 302 as measured by the outdoor meter 308 that corresponds to that tenant's IDU 304. Because the electrical power consumption of ODU 302 measured by the outdoor meter 308 corresponds to cooling/heating provided to all IDUs 304, a challenge exists to accurately apportion the measured electrical power consumption among the multiple IDUs 304.
Referring now to
As in the first metering configuration 300, each ODU 352 serves multiple IDUs 354 located in a variety of building zones that correspond to a variety of tenants 355. For example, ODUA serves IDUA1 through IDUAN, which are located in building zones corresponding to Tenant_A1 through Tenant_AN respectively. In the second metering configuration 350, building zones and tenants also correspond to a variety of system managers 360. According to various embodiments, the system managers 360 are landlord, building owners, or property management companies. For example, in a mixed-use facility, System Manager A may be an apartment management company that manages apartments leased by Tenant_A1 through Tenant_AN, System Manager B may be a condominium association that manages condo owners Tenant_B1 through Tenant_BN, and System Manager Ω may be a commercial leasing firm that manages commercial tenants, including Tenant_Ω1 through Tenant_ΩN.
Each ODU 352 typically consumes a different amount of electrical power, based on the demand on each ODU 352 from the IDUs 354 that the ODU 352 serves. Thus, in order to apportion electrical utility costs for the facility among the system managers 360, a challenge exists to accurately apportion the total electricity consumption measurement of the outdoor meter 358 among the multiple ODUs 352. A process 700 for apportioning electricity consumption among multiple ODUs is shown in
Referring now to
Referring now to
According to various embodiments, the third metering configuration 400 and/or the fourth metering configuration 450 is used with the first metering configuration 300 and/or the second metering configuration 350 to yield a wide variety of possible metering configurations. For example, the VRF system 200 shown in
VRF Systems and Methods with Cost Apportionment
Referring now to
Energy grid 512 supplies electrical power to the VRF system 500. Energy grid 512 is any supply of electrical power, for example a regional electrical grid maintained by a utility company and supplied by one or more power plants that generate electrical power from nuclear, hydro-electric, geothermal, solar, wind, fossil fuel, or other energy sources. In some embodiments, energy grid 512 is a local energy supply, for example a system of building solar panels or another local power system.
ODUs 504 can be located outside a building and can operate to heat or cool a refrigerant, for example by consuming electricity to convert refrigerant between liquid, gas, and/or super-heated gas phases. Each ODU serves a plurality of IDUs 506 by providing the refrigerant to the IDUs 506. Each ODU 504 includes one or more compressors (e.g., compressor 208 shown in
IDUs 506 can be distributed throughout various building zones within a building and can receive the heated or cooled refrigerant from the ODUs 504. Each IDU 506 can provide temperature control for the particular building zone in which the IDU 506 is located. For example, as shown in
Each IDU 506, for example using an IDU controls circuit (e.g., indoor unit controls circuit 222), determines a heat transfer capacity required by the IDU 506 and a frequency of compressor 208 that corresponds to that capacity. The heat transfer capacity required by the IDU 506 may be based on a building zone temperature setpoint, a current building zone temperature reading, and/or some other settings or measurements. When the IDU 506 determines that the IDU 506 must provide heating or cooling of a certain capacity, the IDU 506 then generates and transmits a compressor frequency request to the ODU 504 including the compressor frequency corresponding to the required capacity. In some embodiments, the determination of a required capacity and generation of a compressor frequency request are done by a building management server external to the IDU 506.
IDUs 506 are also configured to collect, store, and provide data relating to the operation of the IDUs. IDU data includes, for example, IDU runtimes (e.g., fan runtimes), thermo-on times (i.e., times when heated/cooled refrigerant is requested/received), compressor request frequencies, and/or other data. The IDUs 506 provide this IDU data to the VRF management system 502. According to various embodiments, VRF system 500 includes any number of IDUs 506 of various brands, manufacturers, models, etc.
Outdoor meters 508 measure electrical power consumption of the ODUs 504, for example in units of kWh (kilowatt hours). According to various embodiments, the outdoor meters 508 may be of various brands, types, manufacturers, models of any electricity meter suitable for measuring electrical power consumption. The outdoor meters 508 may be linked to ODUs 504 in various metering configurations as shown in
Indoor meters 510 measure electrical power consumption of the IDUs 506, for example in units of kWh. According to various embodiments, the indoor meters 510 may be of various brands, types, manufacturers, models of any electricity meter suitable for measuring electrical power consumption. The indoor meters 510 may be linked to IDUs 506 in various metering configurations as shown in
VRF management system 502 collects consumption measurements from outdoor meters 508 and indoor meters 510, ODU data from ODUs 504, and IDU data from IDUs 506, and uses that information with stored VRF-system information to apportion electricity costs among tenants. VRF Management System 502 includes a processing circuit 520, a data collection circuit 526, a VRF database 528, a cost-apportionment circuit 530, and an input/output circuit 532.
Processing circuit 520 is configured to carry out one or more functions of the VRF management system 502 described here. Processing circuit 520 includes a memory 522 and a processor 524. The processor 524 may be implemented as a general-purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a digital signal processor (DSP), a group of processing components that may be distributed over various geographic locations or housed in a single location, or other suitable electronic processing components. The one or more memory devices that comprise memory 522 (e.g., RAM, NVRAM, ROM, Flash Memory, hard disk storage, etc.) may store data and/or computer code for facilitating the various processes described herein. Moreover, the one or more memory devices that comprise memory 522 may be or include tangible, non-transient volatile memory or non-volatile memory. Accordingly, memory 522 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described herein.
Data collection circuit 526 is configured to receive and categorize data from ODUs 504, IDUs 506, outdoor meters 508, and indoor meters 510. Data received by the data collection circuit 526 includes, but is not necessarily limited to, compressor runtimes, compressor requested frequencies, compressor total frequencies (and/or an average compressor total frequency over a period of time), thermo-on times, IDU runtimes, outdoor meter electricity consumption measurements, and indoor meter electricity consumption measurements. The data collection circuit 526 sorts the received data and stores it in the VRF database 528.
VRF database 528 receives and stores data from the data collection circuit 526 and stores other VRF-related information. The other VRF-related information in the VRF database 528 includes a directory of meters 508-510, IDUs 506, and ODUs 504 that includes relationship information defining the associations between meters 508-510, IDUs 506, and ODUs 504 (i.e., that show which IDUs 506 are served by which ODUs 504, and which meters 508-510 measure consumption of which IDUs and ODUs), as well as links between system managers, tenants, and ODUs 504 and IDUs 506 (e.g., that shows which IDUs 506 operate to heat/cool a building zone leased be a particular tenant). The VRF database 528 thereby stores the information necessary for determining the metering/VRF configuration of the VRF system 500 from among the various possible configurations explained with reference to
For each ODU 504, the VRF database 528 stores a set of ODU characteristics, including, but not limited to, a model number, a number of compressors included in the ODU 504, a standby power consumption quantity, and an ODU capacity (e.g., as provided by the manufacturer and provided in a product bulletin or manual). For each IDU 506, the VRF database 528 stores a set of IDU characteristics, including, but not limited to, a model number and an IDU capacity (e.g., as provided by the manufacturer and provided in a product bulletin or manual). The VRF database 528 may also store electricity rate information, for example a set amount of money per kWh, or some other schedule of electricity rates (e.g., a variable electricity cost rate such that a kWh unit costs more at certain times of day than at other times), and contact information or payment information for tenants to facilitate the provision and/or payment of electricity bills corresponding to electricity consumption of the VRF system 500.
The cost-apportionment circuit 530 is configured to access information stored in the VRF database 528 and use that information to accurately apportion the electricity consumption of the VRF system 500 among multiple tenants and determine an amount of money to charge to each tenant to cover the cost of the power consumption. Accordingly, the cost-apportionment circuit 530 carries out one or more of a series of processes for the accurate apportionment of electricity consumption and assignment of monetary charges shown in
The cost-apportionment circuit 530 apportions consumption measurements from an outdoor meter 508 shared by multiple ODUs 504 (i.e., for the second metering configuration 350 of
The cost-apportionment circuit 530 apportions consumption measurements attributed to an ODU 504 among the multiple IDUs 506 that it serves (i.e., the first metering configuration 300 of
The cost-apportionment circuit 530 apportions a consumption measurement of an indoor meter 510 shared by multiple IDUs 506 (i.e., the fourth metering configuration 450 of
The cost-apportionment circuit 530 assigns monetary charges to tenants by determining which IDUs correspond to which tenants based on information stored in the VRF database 528, accessing a tariff rate in the VRF database 528, and calculating a charge by multiplying the tariff rate by the total electricity consumption apportioned to IDUs corresponding to each tenant.
The input/output circuit 532 is configured to generate notifications, bills, user interfaces, and/or other communications to a user of the VRF system 500 and to accept user input to the VRF management system 502 regarding set-up, settings, options, or other information a user desires to provide to the VRF management system 502. For example, in some embodiments the input/output circuit 532 generates an email containing an indication of the monetary charges owed by a tenant to cover the tenant's share of the electricity consumption of VRF system 500 and transmits the email to the tenant's email inbox, mobile device, or other electronic device. In some embodiments, the input/output circuit 532 generates a user interface that a system manager can access using a computing device (e.g., a laptop, tablet, mobile device, desktop computer) to view VRF electricity apportionments and edit tenant information or other settings. The input/output circuit 532 thereby facilitates the communication of the electricity consumption apportionment of the cost-apportionment circuit 530 to one or more users.
Referring now to
Referring now to
At step 702, the number of tenants for each outdoor power group is determined. As described with reference to
At step 704, the cost-apportionment circuit 530 asks if the number of tenants in the outdoor power group is greater than one. If not, the process 700 proceeds to step 706, where the electricity consumption reading is taken from the outdoor meter and assigned the label “kWh_Outdoor.” Because only one tenant is served by the outdoor power group, the total kWh_Outdoor can be attributed to that tenant for purposes of electricity cost apportionment, and the process 700 can end at step 706.
If the number of tenants served by the outdoor power group is greater than one, at step 708 the cost-apportionment circuit 530 access the electricity consumption measurement from the outdoor meter and labels it “kWh_Outdoor_Overall.” The measurement kWh_Outdoor_Overall includes electricity consumption corresponding to multiple tenants that can be apportioned among the multiple ODUs according to the remaining steps of process 700.
At step 710, the cost-apportionment circuit 530 identifies all ODUs in the outdoor power group, among which kWh_Outdoor_Overall is to be apportioned. The process 700 continues from step 710 in
At step 712, the VRF management system 502 determines whether all IDUs served by ODUn are in standby. Standby may refer to a status in which none of the IDUs served by ODUn operate to heat/cool corresponding building zones during the sample time period. If all IDUs serve by ODUn are in standby, at step 714 the VRF management system 502 determines whether the IDUs are in standby or in absolute standby. If the IDUs are in standby, at step 716 the cost-apportionment circuit 530 accesses the VRF database 528 to look up a standby consumption for ODUn (“Standby_kWhODUn”), which may be stored in the VRF database 528 based on a standby consumption rate quoted in a product manual or information sheet. At step 718, the cost-apportionment circuit 530 defines the outdoor power consumption attributable to ODUn (“kWh_outdoorODUn”) to be equal to Standby_kWhODUn.
If the IDUs are in absolute standby, at step 720 the total consumption measurement measured by the outdoor meter (“kWh_outdoor_overall”) and ODU capacity for each ODU in the outdoor power group are accessed by the cost-apportionment circuit 530. ODU capacity may be stored and accessed in the VRF database 528 based on capacity information found in a product manual or information sheet. The kWh_outdoor_overall measurement may be provided to the cost-apportionment circuit by the data collection circuit 526 or may be stored and accessed in the VRF database 528.
At step 722, the cost-apportionment circuit 530 calculates kWh_outdoorODUn as equal to kWh_outdoor_overall multiplied by the capacity of ODUn and divided by the sum of the capacities of all ODUs in the outdoor power group. That is, kWh_outdoorODUn=kWh_outdoor_overall*(capacity of ODUn)/(Σ capacity of ODUk, for all k in power group). In other words, kWh_outdoor_overall is apportioned proportionally based on manufacturer-defined capacities of the ODUs.
If not all of the IDUs are on standby (i.e., one or more IDUs serving ODUn are not on standby), the process 700 proceeds from step 712 to step 724 where, for each ODUn, the cost-apportionment circuit 530 acquires an average ODUn compressor total frequency (“AVG_ODUn_TOT_FREQ”) over a sample time period, the compressor runtime for each compressor in ODUn, and the number of compressors in ODUn. For example, the cost-apportionment circuit 530 may access this data in the VRF database 528. In some embodiments, the cost-apportionment circuit 530 acquires the average ODUn compressor total frequency by getting a series of ODUn compressor total frequencies for the sample time period and running an averaging calculation to determine the average ODUn compressor total frequency over the time period.
At step 726, an ODUn compressor runtime factor is defined as the sum of compressor runtimes divided by the multiple of the calculation cycle time and the number of compressors in ODUn. That is, the ODUn compressor runtime factor=(Sum of Compressor Runtimes)/(number of compressors in ODUn*calculation cycle time). In some embodiments, for example, the calculation cycle time is thirty minutes. At step 728, an ODUn actual capacity factor is defined as the average ODUn compressor total frequency divided by the multiple of the calculation cycle time and the number of compressors in ODUn. That is, ODUn actual capacity factor=AVG_ODUn_TOT_FREQ/(number of compressors in ODUn×calculation cycle time). At step 730, an ODUn consumption factor (“OdCFODUn”) is defined as the ODUn compressor runtime factor multiplied by the ODUn actual capacity factor. That is, OdCFODUn=(ODUn Compressor Runtime Factor)*(ODUn Actual Capacity Factor).
At step 732, an outdoor ODUn power proportional index (“PPIoutdoor_ODUn”) is defined as the ODUn consumption factor divided by the sum of ODU consumption factors for all ODUs in the outdoor power group. That is, PPIoutdoor_ODUn=OdCFODUn/ΣOdCFODUk for all ODUk in the power group.
At step 734, PPIoutdoor_ODUn is used to apportion kWh_outdoor_overall among the ODUs in the outdoor power group to get a consumption measurement for each ODUn (“kWh_outdoorODUn”). The cost-apportionment circuit 530 calculates kWh_outdoorODUn=PPIoutdoor_ODUn*kWh_outdoor_overall. Process 700 thereby results in an accurately apportioned electricity consumption quantity for each ODU 504 in VRF system 500.
Referring now to
At step 802, the cost-apportionment circuit 530 starts process 800 by getting the electricity consumption for the ODU of interest, for example by taking kWh_Outdoor from step 706 of process 700, or kWh_Outdoor_ODUn from step 718, step 722, or step 734 of process 700.
At step 804, the cost-apportionment circuit 530 identifies all IDUs served by the ODU, and asks whether all IDUs are on standby. If all IDUs are on standby, at step 806 the cost-apportionment circuit 530 counts the IDUs to determine the number of IDUs served by the ODU. In some embodiments, the cost-apportionment circuit 530 looks up the number of IDUs served by the ODU in the VRF database 528. At step 808, the ODU's electricity consumption attributable to each IDU (“kWh_outdoor_IDUn”) is calculated as kWh_outdoor_ODUn divided by the number of IDUs served by ODUn. That is, kWh_outdoor_IDUn=kWh_outdoor_ODUn/(number of IDUs).
If the IDUs are not all on standby as determined in step 804, the process 800 proceeds to step 810. At step 810, for each IDUn served by ODUn, the cost-apportionment circuit 530 acquires a thermo-on time (“THER_ON_IDUn”) for a sample time period, compressor request frequencies (“COMP_REQ_FREQ_IDUn”) over the sample time period, and the model number of IDUn. For example, the cost-apportionment circuit 530 may look up this data in the VRF database 528. At step 812, an IDUn thermo-on time factor is calculated as equal to THER_ON_IDUn divided by the duration of the sample time period.
At step 814, the cost-apportionment circuit 530 looks up the IDUn capacity (“IDUn_cap”) based on the model number in the VRF database 528. IDUn_cap is a value stored in the VRF database 528 and included by the manufacturer of IDUn in a product information sheet for the model of IDUn. At step 816, an average zone load (“AVG_ZN_LOAD_IDUn”) is defined as the average of COMP_REQ_FREQ_IDUn over the sample time period. At step 820, an IDUn actual capacity factor is defined as AVG_ZN_LOAD_IDUn multiplied by IDUn_cap.
At step 822, an IDUn outdoor consumption factor (“OCFIDUn”) is defined as the IDUn thermo-on time factor multiplied by the IDUn actual capacity factor. At step 824, an IDUn outdoor power proportional index (“PPIoutdoor_IDUn”) is defined as OCFIDUn divided by the sum of outdoor consumption factors for all IDUs in the indoor power group (i.e., all IDUs served by the ODU). That is, PPIoutdoor_IDUn=OCFIDUn/ΣOCFIDU, k for all IDUs served by one ODU.
At step 826, the electricity consumption attributable to IDUn (“kWh_outdoor_IDUn”) is calculated as PPIoutdoor_IDUn multiplied by the total electricity consumption attributed to the ODU, i.e., kWh_outdoor_ODUn. That is, kWH_outdoor_IDUn=PPIoutdoor_IDUn*kWh_outdoor_ODUn. Process 800 thereby apportions electricity consumption of one ODU (e.g., ODUn) among the IDUs that the ODU serves.
Referring now to
At step 902, the cost-apportionment circuit 530 acquires an electricity consumption measurement (“kWh_indoor”) from an indoor meter 510 that measures the indoor consumption of multiple IDUs 506 (e.g., indoor meter 456 of
At step 904, for each IDU (e.g., IDUn) in the indoor power group, the cost-apportionment circuit 530 looks up the IDUn capacity (“IDUn cap”) based on IDUn's model number in the VRF database 528 and acquires an IDUn_runtime (“RT_IDUn”). In some cases, RT_IDUn corresponds to a duration of time that a fan in IDUn was powered-on and rotating during a calculation cycle time. RT_IDUn may be collected by the data collection circuit 526 and stored in the VRF database 528.
At step 906, an IDUn runtime factor is defined as RT_IDUn divided by the duration of the calculation cycle time. That is, the IDUn runtime factor is the proportion of the total calculation cycle time for which the IDU was running. At step 908, an IDUn capacity factor is defined as equal to IDUn cap. At step 910, an IDUn indoor consumption factor (“ICFIDUn”) is defined as the IDUn runtime factor multiplied by the IDUn capacity factor.
At step 912, an IDUn indoor power proportional index (“PPIindoor_IDUn”) is defined as equal to ICFIDUn divided by the sum of indoor consumption factors for all IDUs in the indoor power group. That is, PPIindoor_IDUn=ICFIDUn/ΣICFIDUk, k for all IDUs measured by the same indoor meter.
At step 914, the cost-apportionment circuit 530 determines an indoor power consumption attributable to each IDU (“kWh_indoor_IDUn) based on the indoor power proportional indexes and kWh_indoor. More particularly, the cost-apportionment circuit 530 calculates kWh_indoor_IDUn=PPIindoor_IDUn*kWh_indoor. Process 900 thereby results in an indoor power consumption attributable to each IDU in an indoor power group.
Referring now to
At step 1002, the cost-apportionment circuit 530 takes kWh_outdoor_IDUn for all n from the end of process 800 (i.e., from step 808 and/or step 826). At step 1004, the cost-apportionment circuit 530 takes kWh_indoor_IDUn for all n from the end of process 900 (i.e., from step 914).
At step 1006, a total IDUn electricity consumption (“kWh_IDUn”) is defined as kWh_IDUn=kWh_outdoor_IDUn+kWh_indoor_IDUn. That is, the outdoor consumption attributable to each IDU is summed with the indoor consumption attributable to that IDU to get a total electricity consumption for that IDU.
At step 1008, the cost-apportionment circuit 530 gets a tariff rate for each unit of electricity (e.g., dollars per kWh). The tariff rate can be in any currency (e.g., dollars, Euros, rupees) rated per unit of electricity consumption. The tariff rate may be stored in the VRF database 528, for example as supplied by an electrical utility company. At step 1010 a charge per IDUn for a sample time period (“Charge_IDUn”) is defined as the tariff rate multiplied by kWh_IDUn.
At step 1012, the cost-apportionment circuit 530 calculates a charge for each tenant as the sum of Charge_IDUk for all IDUs assigned to a tenant. The cost-apportionment may access a list of tenants and IDUs in the VRF database 528 to determine which IDUs correspond to which tenants. Process 1000 thereby results in an amount of currency that can be billed to tenants that accurately reflects the tenants' contribution to the power consumption of the VRF system 500. In some embodiments, the input/output circuit 532 generates bills, transmits bills to tenants, receives payment information from tenants, and otherwise facilitates tenant's fulfillment of the calculated charges.
Configuration of Exemplary Embodiments
The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements can be reversed or otherwise varied and the nature or number of discrete elements or positions can be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps can be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions can be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.
As used herein, the term “circuit” may include hardware structured to execute the functions described herein. In some embodiments, each respective “circuit” may include machine-readable media for configuring the hardware to execute the functions described herein. The circuit may be embodied as one or more circuitry components including, but not limited to, processing circuitry, network interfaces, peripheral devices, input devices, output devices, sensors, etc. In some embodiments, a circuit may take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (IC), discrete circuits, system on a chip (SOCs) circuits, etc.), telecommunication circuits, hybrid circuits, and any other type of “circuit.” In this regard, the “circuit” may include any type of component for accomplishing or facilitating achievement of the operations described herein. For example, a circuit as described herein may include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring, and so on).
The “circuit” may also include one or more processors communicably coupled to one or more memory or memory devices. In this regard, the one or more processors may execute instructions stored in the memory or may execute instructions otherwise accessible to the one or more processors. In some embodiments, the one or more processors may be embodied in various ways. The one or more processors may be constructed in a manner sufficient to perform at least the operations described herein. In some embodiments, the one or more processors may be shared by multiple circuits (e.g., circuit A and circuit B may comprise or otherwise share the same processor which, in some example embodiments, may execute instructions stored, or otherwise accessed, via different areas of memory). Alternatively or additionally, the one or more processors may be structured to perform or otherwise execute certain operations independent of one or more co-processors. In other example embodiments, two or more processors may be coupled via a bus to enable independent, parallel, pipelined, or multi-threaded instruction execution. Each processor may be implemented as one or more general-purpose processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), or other suitable electronic data processing components structured to execute instructions provided by memory. The one or more processors may take the form of a single core processor, multi-core processor (e.g., a dual core processor, triple core processor, quad core processor, etc.), microprocessor, etc. In some embodiments, the one or more processors may be external to the apparatus, for example the one or more processors may be a remote processor (e.g., a cloud based processor). Alternatively or additionally, the one or more processors may be internal and/or local to the apparatus. In this regard, a given circuit or components thereof may be disposed locally (e.g., as part of a local server, a local computing system, etc.) or remotely (e.g., as part of a remote server such as a cloud based server). To that end, a “circuit” as described herein may include components that are distributed across one or more locations. The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure can be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
Although the figures show a specific order of method steps, the order of the steps may differ from what is depicted. Also two or more steps can be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, calculation steps, processing steps, comparison steps, and decision steps.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5301109 | Landauer et al. | Apr 1994 | A |
| 5446677 | Jensen et al. | Aug 1995 | A |
| 5581478 | Cruse et al. | Dec 1996 | A |
| 5812962 | Kovac | Sep 1998 | A |
| 5960381 | Singers et al. | Sep 1999 | A |
| 5973662 | Singers et al. | Oct 1999 | A |
| 6014612 | Larson et al. | Jan 2000 | A |
| 6031547 | Kennedy | Feb 2000 | A |
| 6134511 | Subbarao | Oct 2000 | A |
| 6157943 | Meyer | Dec 2000 | A |
| 6285966 | Brown et al. | Sep 2001 | B1 |
| 6363422 | Hunter et al. | Mar 2002 | B1 |
| 6385510 | Hoog et al. | May 2002 | B1 |
| 6389331 | Jensen et al. | May 2002 | B1 |
| 6401027 | Xu et al. | Jun 2002 | B1 |
| 6437691 | Sandelman et al. | Aug 2002 | B1 |
| 6477518 | Li et al. | Nov 2002 | B1 |
| 6487457 | Hull et al. | Nov 2002 | B1 |
| 6493755 | Hansen et al. | Dec 2002 | B1 |
| 6577323 | Jamieson et al. | Jun 2003 | B1 |
| 6626366 | Kayahara et al. | Sep 2003 | B2 |
| 6646660 | Patty | Nov 2003 | B1 |
| 6704016 | Oliver et al. | Mar 2004 | B1 |
| 6732540 | Sugihara et al. | May 2004 | B2 |
| 6764019 | Kayahara et al. | Jul 2004 | B1 |
| 6782385 | Natsumeda et al. | Aug 2004 | B2 |
| 6813532 | Eryurek et al. | Nov 2004 | B2 |
| 6816811 | Seem | Nov 2004 | B2 |
| 6823680 | Jayanth | Nov 2004 | B2 |
| 6826454 | Sulfstede | Nov 2004 | B2 |
| 6865511 | Frerichs et al. | Mar 2005 | B2 |
| 6925338 | Eryurek et al. | Aug 2005 | B2 |
| 6986138 | Sakaguchi et al. | Jan 2006 | B1 |
| 7031880 | Seem et al. | Apr 2006 | B1 |
| 7401057 | Eder | Jul 2008 | B2 |
| 7552467 | Lindsay | Jun 2009 | B2 |
| 7627544 | Chkodrov et al. | Dec 2009 | B2 |
| 7818249 | Lovejoy et al. | Oct 2010 | B2 |
| 7889051 | Billig et al. | Feb 2011 | B1 |
| 7996488 | Casabella et al. | Aug 2011 | B1 |
| 8078330 | Brickfield et al. | Dec 2011 | B2 |
| 8104044 | Scofield et al. | Jan 2012 | B1 |
| 8229470 | Ranjan et al. | Jul 2012 | B1 |
| 8401991 | Wu et al. | Mar 2013 | B2 |
| 8495745 | Schrecker et al. | Jul 2013 | B1 |
| 8516016 | Park et al. | Aug 2013 | B2 |
| 8532808 | Drees et al. | Sep 2013 | B2 |
| 8532839 | Drees et al. | Sep 2013 | B2 |
| 8600556 | Nesler et al. | Dec 2013 | B2 |
| 8635182 | MacKay | Jan 2014 | B2 |
| 8682921 | Park et al. | Mar 2014 | B2 |
| 8731724 | Drees et al. | May 2014 | B2 |
| 8737334 | Ahn et al. | May 2014 | B2 |
| 8738334 | Jiang et al. | May 2014 | B2 |
| 8751487 | Byrne et al. | Jun 2014 | B2 |
| 8788097 | Drees et al. | Jul 2014 | B2 |
| 8805995 | Oliver | Aug 2014 | B1 |
| 8843238 | Wenzel et al. | Sep 2014 | B2 |
| 8874071 | Sherman et al. | Oct 2014 | B2 |
| 8941465 | Pineau et al. | Jan 2015 | B2 |
| 8990127 | Taylor | Mar 2015 | B2 |
| 9070113 | Shafiee et al. | Jun 2015 | B2 |
| 9116978 | Park et al. | Aug 2015 | B2 |
| 9185095 | Moritz et al. | Nov 2015 | B1 |
| 9189527 | Park et al. | Nov 2015 | B2 |
| 9196009 | Drees et al. | Nov 2015 | B2 |
| 9229966 | Aymeloglu et al. | Jan 2016 | B2 |
| 9286582 | Drees et al. | Mar 2016 | B2 |
| 9311807 | Schultz et al. | Apr 2016 | B2 |
| 9344751 | Ream et al. | May 2016 | B1 |
| 9354968 | Wenzel et al. | May 2016 | B2 |
| 9507686 | Horn et al. | Nov 2016 | B2 |
| 9524594 | Ouyang et al. | Dec 2016 | B2 |
| 9558196 | Johnston et al. | Jan 2017 | B2 |
| 9652813 | Gifford et al. | May 2017 | B2 |
| 9753455 | Drees | Sep 2017 | B2 |
| 9811249 | Chen et al. | Nov 2017 | B2 |
| 9838844 | Emeis et al. | Dec 2017 | B2 |
| 9886478 | Mukherjee | Feb 2018 | B2 |
| 9948359 | Horton | Apr 2018 | B2 |
| 10055114 | Shah et al. | Aug 2018 | B2 |
| 10055206 | Park et al. | Aug 2018 | B2 |
| 10116461 | Fairweather et al. | Oct 2018 | B2 |
| 10169454 | Ait-Mokhtar et al. | Jan 2019 | B2 |
| 10171586 | Shaashua et al. | Jan 2019 | B2 |
| 10187258 | Nagesh et al. | Jan 2019 | B2 |
| 10514963 | Shrivastava et al. | Dec 2019 | B2 |
| 10515098 | Park et al. | Dec 2019 | B2 |
| 10534326 | Sridharan et al. | Jan 2020 | B2 |
| 10536295 | Fairweather et al. | Jan 2020 | B2 |
| 10705492 | Harvey | Jul 2020 | B2 |
| 10708078 | Harvey | Jul 2020 | B2 |
| 10845771 | Harvey | Nov 2020 | B2 |
| 10854194 | Park et al. | Dec 2020 | B2 |
| 10862928 | Badawy et al. | Dec 2020 | B1 |
| 10921760 | Harvey | Feb 2021 | B2 |
| 10921972 | Park et al. | Feb 2021 | B2 |
| 10969133 | Harvey | Apr 2021 | B2 |
| 10986121 | Stockdale et al. | Apr 2021 | B2 |
| 11016998 | Park et al. | May 2021 | B2 |
| 11024292 | Park et al. | Jun 2021 | B2 |
| 11038709 | Park et al. | Jun 2021 | B2 |
| 11070390 | Park et al. | Jul 2021 | B2 |
| 11073976 | Park et al. | Jul 2021 | B2 |
| 11108587 | Park et al. | Aug 2021 | B2 |
| 11113295 | Park et al. | Sep 2021 | B2 |
| 11229138 | Harvey et al. | Jan 2022 | B1 |
| 11314726 | Park et al. | Apr 2022 | B2 |
| 11314788 | Park et al. | Apr 2022 | B2 |
| 20020010562 | Schleiss et al. | Jan 2002 | A1 |
| 20020016639 | Smith et al. | Feb 2002 | A1 |
| 20020059229 | Natsumeda et al. | May 2002 | A1 |
| 20020123864 | Eryurek et al. | Sep 2002 | A1 |
| 20020147506 | Eryurek et al. | Oct 2002 | A1 |
| 20020177909 | Fu et al. | Nov 2002 | A1 |
| 20030005486 | Ridolfo et al. | Jan 2003 | A1 |
| 20030014130 | Grumelart | Jan 2003 | A1 |
| 20030073432 | Meade, II | Apr 2003 | A1 |
| 20030158704 | Triginai et al. | Aug 2003 | A1 |
| 20030171851 | Brickfield et al. | Sep 2003 | A1 |
| 20030200059 | Ignatowski et al. | Oct 2003 | A1 |
| 20040068390 | Saunders | Apr 2004 | A1 |
| 20040128314 | Katibah et al. | Jul 2004 | A1 |
| 20040133314 | Ehlers et al. | Jul 2004 | A1 |
| 20040199360 | Friman et al. | Oct 2004 | A1 |
| 20050055308 | Meyer et al. | Mar 2005 | A1 |
| 20050097902 | Kwon | May 2005 | A1 |
| 20050108262 | Fawcett et al. | May 2005 | A1 |
| 20050154494 | Ahmed | Jul 2005 | A1 |
| 20050278703 | Lo et al. | Dec 2005 | A1 |
| 20050283337 | Sayal | Dec 2005 | A1 |
| 20060095521 | Patinkin | May 2006 | A1 |
| 20060140207 | Eschbach et al. | Jun 2006 | A1 |
| 20060184479 | Levine | Aug 2006 | A1 |
| 20060200476 | Gottumukkala et al. | Sep 2006 | A1 |
| 20060265751 | Cosquer et al. | Nov 2006 | A1 |
| 20060271589 | Horowitz et al. | Nov 2006 | A1 |
| 20070028179 | Levin et al. | Feb 2007 | A1 |
| 20070203693 | Estes | Aug 2007 | A1 |
| 20070261062 | Bansal et al. | Nov 2007 | A1 |
| 20070273497 | Kuroda et al. | Nov 2007 | A1 |
| 20070273610 | Baillot | Nov 2007 | A1 |
| 20080034425 | Overcash et al. | Feb 2008 | A1 |
| 20080094230 | Mock et al. | Apr 2008 | A1 |
| 20080097816 | Freire et al. | Apr 2008 | A1 |
| 20080142607 | Yoshii | Jun 2008 | A1 |
| 20080186160 | Kim et al. | Aug 2008 | A1 |
| 20080249756 | Chaisuparasmikul | Oct 2008 | A1 |
| 20080252723 | Park | Oct 2008 | A1 |
| 20080281472 | Podgorny et al. | Nov 2008 | A1 |
| 20090195349 | Frader-Thompson et al. | Aug 2009 | A1 |
| 20100045439 | Tak et al. | Feb 2010 | A1 |
| 20100058248 | Park | Mar 2010 | A1 |
| 20100131533 | Ortiz | May 2010 | A1 |
| 20100274366 | Fata et al. | Oct 2010 | A1 |
| 20100281387 | Holland et al. | Nov 2010 | A1 |
| 20100286937 | Hedley et al. | Nov 2010 | A1 |
| 20100324962 | Nesler et al. | Dec 2010 | A1 |
| 20110015802 | Imes | Jan 2011 | A1 |
| 20110047418 | Drees et al. | Feb 2011 | A1 |
| 20110061015 | Drees et al. | Mar 2011 | A1 |
| 20110071685 | Huneycutt et al. | Mar 2011 | A1 |
| 20110077950 | Hughston | Mar 2011 | A1 |
| 20110087650 | MacKay et al. | Apr 2011 | A1 |
| 20110087988 | Ray et al. | Apr 2011 | A1 |
| 20110088000 | MacKay | Apr 2011 | A1 |
| 20110125737 | Pothering et al. | May 2011 | A1 |
| 20110137853 | MacKay | Jun 2011 | A1 |
| 20110153603 | Adiba et al. | Jun 2011 | A1 |
| 20110154363 | Karmarkar | Jun 2011 | A1 |
| 20110157357 | Weisensale et al. | Jun 2011 | A1 |
| 20110178977 | Drees | Jul 2011 | A1 |
| 20110191343 | Heaton et al. | Aug 2011 | A1 |
| 20110205022 | Cavallaro et al. | Aug 2011 | A1 |
| 20110218777 | Chen et al. | Sep 2011 | A1 |
| 20120011126 | Park et al. | Jan 2012 | A1 |
| 20120011141 | Park et al. | Jan 2012 | A1 |
| 20120022698 | MacKay | Jan 2012 | A1 |
| 20120062577 | Nixon | Mar 2012 | A1 |
| 20120064923 | Imes et al. | Mar 2012 | A1 |
| 20120083930 | Ilic et al. | Apr 2012 | A1 |
| 20120100825 | Sherman et al. | Apr 2012 | A1 |
| 20120101637 | Imes et al. | Apr 2012 | A1 |
| 20120135759 | Imes et al. | May 2012 | A1 |
| 20120136485 | Weber et al. | May 2012 | A1 |
| 20120158633 | Eder | Jun 2012 | A1 |
| 20120259583 | Noboa et al. | Oct 2012 | A1 |
| 20120272228 | Marndi et al. | Oct 2012 | A1 |
| 20120278051 | Jiang et al. | Nov 2012 | A1 |
| 20130007063 | Kalra et al. | Jan 2013 | A1 |
| 20130038430 | Blower et al. | Feb 2013 | A1 |
| 20130038707 | Cunningham et al. | Feb 2013 | A1 |
| 20130060820 | Bulusu et al. | Mar 2013 | A1 |
| 20130086497 | Ambuhl et al. | Apr 2013 | A1 |
| 20130097706 | Titonis et al. | Apr 2013 | A1 |
| 20130103221 | Raman et al. | Apr 2013 | A1 |
| 20130167035 | Imes et al. | Jun 2013 | A1 |
| 20130170710 | Kuoch et al. | Jul 2013 | A1 |
| 20130204836 | Choi et al. | Aug 2013 | A1 |
| 20130246916 | Reimann et al. | Sep 2013 | A1 |
| 20130247205 | Schrecker et al. | Sep 2013 | A1 |
| 20130262035 | Mills | Oct 2013 | A1 |
| 20130275174 | Bennett et al. | Oct 2013 | A1 |
| 20130275908 | Reichard | Oct 2013 | A1 |
| 20130297050 | Reichard et al. | Nov 2013 | A1 |
| 20130298244 | Kumar et al. | Nov 2013 | A1 |
| 20130331995 | Rosen | Dec 2013 | A1 |
| 20140032506 | Hoey et al. | Jan 2014 | A1 |
| 20140059483 | Mairs et al. | Feb 2014 | A1 |
| 20140081652 | Klindworth | Mar 2014 | A1 |
| 20140135952 | Maehara | May 2014 | A1 |
| 20140152651 | Chen et al. | Jun 2014 | A1 |
| 20140172184 | Schmidt et al. | Jun 2014 | A1 |
| 20140189861 | Gupta et al. | Jul 2014 | A1 |
| 20140207282 | Angle et al. | Jul 2014 | A1 |
| 20140238061 | Shimamoto et al. | Aug 2014 | A1 |
| 20140258052 | Khuti et al. | Sep 2014 | A1 |
| 20140269614 | Maguire et al. | Sep 2014 | A1 |
| 20140277765 | Karimi et al. | Sep 2014 | A1 |
| 20140278461 | Artz | Sep 2014 | A1 |
| 20140327555 | Sager et al. | Nov 2014 | A1 |
| 20140345826 | Kim et al. | Nov 2014 | A1 |
| 20150019174 | Kiff et al. | Jan 2015 | A1 |
| 20150042240 | Aggarwal et al. | Feb 2015 | A1 |
| 20150105917 | Sasaki et al. | Apr 2015 | A1 |
| 20150145468 | Ma et al. | May 2015 | A1 |
| 20150156031 | Fadell et al. | Jun 2015 | A1 |
| 20150168931 | Jin | Jun 2015 | A1 |
| 20150172300 | Cochenour | Jun 2015 | A1 |
| 20150178421 | Borrelli et al. | Jun 2015 | A1 |
| 20150185261 | Frader-Thompson et al. | Jul 2015 | A1 |
| 20150186777 | Lecue et al. | Jul 2015 | A1 |
| 20150202962 | Habashima et al. | Jul 2015 | A1 |
| 20150204563 | Imes et al. | Jul 2015 | A1 |
| 20150211758 | Macek | Jul 2015 | A1 |
| 20150235267 | Steube et al. | Aug 2015 | A1 |
| 20150241895 | Lu et al. | Aug 2015 | A1 |
| 20150244730 | Vu et al. | Aug 2015 | A1 |
| 20150244732 | Golshan et al. | Aug 2015 | A1 |
| 20150261863 | Dey et al. | Sep 2015 | A1 |
| 20150263900 | Polyakov et al. | Sep 2015 | A1 |
| 20150286969 | Warner et al. | Oct 2015 | A1 |
| 20150295796 | Hsiao et al. | Oct 2015 | A1 |
| 20150304193 | Ishii et al. | Oct 2015 | A1 |
| 20150316918 | Schleiss et al. | Nov 2015 | A1 |
| 20150324422 | Elder | Nov 2015 | A1 |
| 20150341212 | Hsiao et al. | Nov 2015 | A1 |
| 20150348417 | Ignaczak et al. | Dec 2015 | A1 |
| 20150379080 | Jochimski | Dec 2015 | A1 |
| 20160011753 | McFarland et al. | Jan 2016 | A1 |
| 20160033946 | Zhu et al. | Feb 2016 | A1 |
| 20160035246 | Curtis | Feb 2016 | A1 |
| 20160065601 | Gong et al. | Mar 2016 | A1 |
| 20160070736 | Swan et al. | Mar 2016 | A1 |
| 20160078229 | Gong et al. | Mar 2016 | A1 |
| 20160090839 | Stolarczyk | Mar 2016 | A1 |
| 20160119434 | Dong et al. | Apr 2016 | A1 |
| 20160127712 | Alfredsson et al. | May 2016 | A1 |
| 20160139752 | Shim et al. | May 2016 | A1 |
| 20160163186 | Davidson et al. | Jun 2016 | A1 |
| 20160170390 | Xie et al. | Jun 2016 | A1 |
| 20160171862 | Das et al. | Jun 2016 | A1 |
| 20160173816 | Huenerfauth et al. | Jun 2016 | A1 |
| 20160179315 | Sarao et al. | Jun 2016 | A1 |
| 20160179342 | Sarao et al. | Jun 2016 | A1 |
| 20160179990 | Sarao et al. | Jun 2016 | A1 |
| 20160195856 | Spero | Jul 2016 | A1 |
| 20160212165 | Singla et al. | Jul 2016 | A1 |
| 20160239660 | Azvine et al. | Aug 2016 | A1 |
| 20160239756 | Aggour et al. | Aug 2016 | A1 |
| 20160313751 | Risbeck et al. | Oct 2016 | A1 |
| 20160313752 | Przybylski | Oct 2016 | A1 |
| 20160313902 | Hill et al. | Oct 2016 | A1 |
| 20160350364 | Anicic et al. | Dec 2016 | A1 |
| 20160357828 | Tobin et al. | Dec 2016 | A1 |
| 20160358432 | Branscomb et al. | Dec 2016 | A1 |
| 20160363336 | Roth et al. | Dec 2016 | A1 |
| 20160370258 | Perez | Dec 2016 | A1 |
| 20160377309 | Abiprojo | Dec 2016 | A1 |
| 20160378306 | Kresl et al. | Dec 2016 | A1 |
| 20160379326 | Chan-Gove et al. | Dec 2016 | A1 |
| 20170006135 | Siebel | Jan 2017 | A1 |
| 20170011318 | Vigano et al. | Jan 2017 | A1 |
| 20170017221 | Lamparter et al. | Jan 2017 | A1 |
| 20170039255 | Raj et al. | Feb 2017 | A1 |
| 20170052536 | Warner et al. | Feb 2017 | A1 |
| 20170053441 | Nadumane et al. | Feb 2017 | A1 |
| 20170063894 | Muddu et al. | Mar 2017 | A1 |
| 20170068409 | Nair | Mar 2017 | A1 |
| 20170070775 | Taxier et al. | Mar 2017 | A1 |
| 20170075984 | Deshpande et al. | Mar 2017 | A1 |
| 20170084168 | Janchookiat | Mar 2017 | A1 |
| 20170090437 | Veeramani et al. | Mar 2017 | A1 |
| 20170093700 | Gilley et al. | Mar 2017 | A1 |
| 20170098086 | Hoernecke et al. | Apr 2017 | A1 |
| 20170103327 | Penilla et al. | Apr 2017 | A1 |
| 20170103403 | Chu et al. | Apr 2017 | A1 |
| 20170123389 | Baez et al. | May 2017 | A1 |
| 20170134415 | Muddu et al. | May 2017 | A1 |
| 20170177715 | Chang et al. | Jun 2017 | A1 |
| 20170180147 | Brandman et al. | Jun 2017 | A1 |
| 20170188216 | Koskas et al. | Jun 2017 | A1 |
| 20170212482 | Boettcher et al. | Jul 2017 | A1 |
| 20170212668 | Shah et al. | Jul 2017 | A1 |
| 20170220641 | Chi et al. | Aug 2017 | A1 |
| 20170230930 | Frey | Aug 2017 | A1 |
| 20170235817 | Deodhar et al. | Aug 2017 | A1 |
| 20170251182 | Siminoff et al. | Aug 2017 | A1 |
| 20170270124 | Nagano et al. | Sep 2017 | A1 |
| 20170277769 | Pasupathy et al. | Sep 2017 | A1 |
| 20170278003 | Liu | Sep 2017 | A1 |
| 20170294132 | Colmenares | Oct 2017 | A1 |
| 20170315522 | Kwon et al. | Nov 2017 | A1 |
| 20170315697 | Jacobson et al. | Nov 2017 | A1 |
| 20170322534 | Sinha et al. | Nov 2017 | A1 |
| 20170323389 | Vavrasek | Nov 2017 | A1 |
| 20170329289 | Kohn et al. | Nov 2017 | A1 |
| 20170336770 | MacMillan | Nov 2017 | A1 |
| 20170345287 | Fuller et al. | Nov 2017 | A1 |
| 20170351957 | Lecue et al. | Dec 2017 | A1 |
| 20170357225 | Asp et al. | Dec 2017 | A1 |
| 20170357490 | Park et al. | Dec 2017 | A1 |
| 20170357908 | Cabadi et al. | Dec 2017 | A1 |
| 20180004173 | Patel et al. | Jan 2018 | A1 |
| 20180012159 | Kozloski et al. | Jan 2018 | A1 |
| 20180013579 | Fairweather et al. | Jan 2018 | A1 |
| 20180024520 | Sinha et al. | Jan 2018 | A1 |
| 20180039238 | Gartner et al. | Feb 2018 | A1 |
| 20180048485 | Pelton et al. | Feb 2018 | A1 |
| 20180069932 | Tiwari et al. | Mar 2018 | A1 |
| 20180114140 | Chen et al. | Apr 2018 | A1 |
| 20180137288 | Polyakov | May 2018 | A1 |
| 20180157930 | Rutschman et al. | Jun 2018 | A1 |
| 20180162400 | Abdar | Jun 2018 | A1 |
| 20180176241 | Manadhata et al. | Jun 2018 | A1 |
| 20180198627 | Mullins | Jul 2018 | A1 |
| 20180203961 | Aisu et al. | Jul 2018 | A1 |
| 20180239982 | Rutschman et al. | Aug 2018 | A1 |
| 20180275625 | Park et al. | Sep 2018 | A1 |
| 20180276962 | Butler et al. | Sep 2018 | A1 |
| 20180292797 | Lamparter et al. | Oct 2018 | A1 |
| 20180336785 | Ghannam et al. | Nov 2018 | A1 |
| 20180359111 | Harvey | Dec 2018 | A1 |
| 20180364654 | Locke et al. | Dec 2018 | A1 |
| 20190005025 | Malabarba | Jan 2019 | A1 |
| 20190013023 | Pourmohammad et al. | Jan 2019 | A1 |
| 20190025771 | Park et al. | Jan 2019 | A1 |
| 20190037135 | Hedge | Jan 2019 | A1 |
| 20190042988 | Brown et al. | Feb 2019 | A1 |
| 20190088106 | Grundstrom | Mar 2019 | A1 |
| 20190094824 | Xie et al. | Mar 2019 | A1 |
| 20190096217 | Pourmohammad et al. | Mar 2019 | A1 |
| 20190102840 | Perl et al. | Apr 2019 | A1 |
| 20190138512 | Pourmohammad et al. | May 2019 | A1 |
| 20190147883 | Mellenthin et al. | May 2019 | A1 |
| 20190158309 | Park et al. | May 2019 | A1 |
| 20190163152 | Worrall et al. | May 2019 | A1 |
| 20190268178 | Fairweather et al. | Aug 2019 | A1 |
| 20190310979 | Masuzaki et al. | Oct 2019 | A1 |
| 20200226156 | Borra et al. | Jul 2020 | A1 |
| 20200285203 | Thakur et al. | Sep 2020 | A1 |
| 20210042299 | Migliori | Feb 2021 | A1 |
| 20210381711 | Harvey et al. | Dec 2021 | A1 |
| 20210381712 | Harvey et al. | Dec 2021 | A1 |
| 20210382445 | Harvey et al. | Dec 2021 | A1 |
| 20210383041 | Harvey et al. | Dec 2021 | A1 |
| 20210383042 | Harvey et al. | Dec 2021 | A1 |
| 20210383200 | Harvey et al. | Dec 2021 | A1 |
| 20210383219 | Harvey et al. | Dec 2021 | A1 |
| 20210383235 | Harvey et al. | Dec 2021 | A1 |
| 20210383236 | Harvey et al. | Dec 2021 | A1 |
| 20220066402 | Harvey et al. | Mar 2022 | A1 |
| 20220066405 | Harvey | Mar 2022 | A1 |
| 20220066432 | Harvey et al. | Mar 2022 | A1 |
| 20220066434 | Harvey et al. | Mar 2022 | A1 |
| 20220066528 | Harvey et al. | Mar 2022 | A1 |
| 20220066722 | Harvey et al. | Mar 2022 | A1 |
| 20220066754 | Harvey et al. | Mar 2022 | A1 |
| 20220066761 | Harvey et al. | Mar 2022 | A1 |
| 20220067226 | Harvey et al. | Mar 2022 | A1 |
| 20220067227 | Harvey et al. | Mar 2022 | A1 |
| 20220067230 | Harvey et al. | Mar 2022 | A1 |
| 20220069863 | Harvey et al. | Mar 2022 | A1 |
| 20220070293 | Harvey et al. | Mar 2022 | A1 |
| 20220138684 | Harvey | May 2022 | A1 |
| 20220215264 | Harvey et al. | Jul 2022 | A1 |
| 20230010757 | Preciado | Jan 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 101415011 | Apr 2009 | CN |
| 101464025 | Jun 2009 | CN |
| 102136099 | Jul 2011 | CN |
| 102136100 | Jul 2011 | CN |
| 102650876 | Aug 2012 | CN |
| 103124879 | May 2013 | CN |
| 103202034 | Jul 2013 | CN |
| 104040583 | Sep 2014 | CN |
| 104603832 | May 2015 | CN |
| 104919484 | Sep 2015 | CN |
| 105473354 | Apr 2016 | CN |
| 106204392 | Dec 2016 | CN |
| 106406806 | Feb 2017 | CN |
| 106871475 | Jun 2017 | CN |
| 106960269 | Jul 2017 | CN |
| 107147639 | Sep 2017 | CN |
| 107598928 | Jan 2018 | CN |
| 1 536 186 | Jun 2005 | EP |
| 2 528 033 | Nov 2012 | EP |
| 3 324 306 | May 2018 | EP |
| H10-049552 | Feb 1998 | JP |
| 2000-234792 | Aug 2000 | JP |
| 2001-108277 | Apr 2001 | JP |
| 2003-162573 | Jun 2003 | JP |
| 2005-147651 | Jun 2005 | JP |
| 2007-018322 | Jan 2007 | JP |
| 4073946 | Apr 2008 | JP |
| 2008-107930 | May 2008 | JP |
| 2008-151443 | Jul 2008 | JP |
| 2013-152618 | Aug 2013 | JP |
| 2014-044457 | Mar 2014 | JP |
| 20160102923 | Aug 2016 | KR |
| WO-2009020158 | Feb 2009 | WO |
| WO-2011100255 | Aug 2011 | WO |
| WO-2013050333 | Apr 2013 | WO |
| WO-2015106702 | Jul 2015 | WO |
| WO-2015145648 | Oct 2015 | WO |
| WO-2017035536 | Mar 2017 | WO |
| WO-2017192422 | Nov 2017 | WO |
| WO-2017194244 | Nov 2017 | WO |
| WO-2017205330 | Nov 2017 | WO |
| WO-2017213918 | Dec 2017 | WO |
| Entry |
|---|
| Fujitsu General Limited, Electricity Charge Apportionment Tool for Touch Panel Controller Instruction Manual, 2015, 117 pages. |
| International Search Report and Written Opinion for International Application No. PCT/US2019/021878, dated Jun. 21, 2019, 14 pages. |
| Balaji et al., “Brick: Metadata schema for portable smart building applications,” Applied Energy, 2018 (20 pages). |
| Balaji et al., “Brick: Metadata schema for portable smart building applications,” Applied Energy, Sep. 15, 2018, 3 pages, (Abstract). |
| Balaji et al., “Demo Abstract: Portable Queries Using the Brick Schema for Building Applications,” BuildSys '16, Palo Alto, CA, USA, Nov. 16-17, 2016 (2 pages). |
| Balaji, B. et al., “Brick: Towards a Unified Metadata Schema for Buildings.” BuildSys '16, Palo Alto, CA, USA, Nov. 16-17, 2016 (10 pages). |
| Bhattacharya et al., “Short Paper: Analyzing Metadata Schemas for Buildings—The Good, The Bad and The Ugly,” BuildSys '15, Seoul, South Korea, Nov. 4-5, 2015 (4 pages). |
| Bhattacharya, A., “Enabling Scalable Smart-Building Analytics,” Electrical Engineering and Computer Sciences, University of California at Berkeley, Technical Report No. UCB/EECS-2016-201, Dec. 15, 2016 (121 pages). |
| Brick, “Brick Schema: Building Blocks for Smart Buildings,” URL: chrome-extension://efaidnbmnnnibpcajpcglclefindmkaj/https://www.memoori.com/wp-content/uploads/2016/06/Brick_Schema_Whitepaper.pdf, Mar. 2019 (17 pages). |
| Brick, “Brick: Towards a Unified Metadata Schema for Buildings,” URL: chrome-extension://efaidnbmnnnibpcajpcglclefindmkaj/https://brickschema.org/papers/Brick_BuildSys_Presentation.pdf, Presented at BuildSys '16, Nov. 2016 (46 pages). |
| Brick, “Metadata Schema for Buildings,” URL: https://brickschema.org/docs/Brick-Leaflet.pdf, retrieved from internet Dec. 24, 2019 (3 pages). |
| Chinese Office Action on CN Appl. Ser. No. 201780003995.9 dated Apr. 8, 2021 (21 pages). |
| Chinese Office action on CN Appl. Ser. No. 201780043400.2 dated Apr. 25, 2021 (15 pages). |
| Curry, E. et al., “Linking building data in the cloud: Integrating cross-domain building data using linked data.” Advanced Engineering Informatics, 2013, 27 (pp. 206-219). |
| Daikin AC, “Power Proportional Distribution (PPD),” URL: http://www.daikinac.com/content/assets/Controls/Intelligent-Controller-PPD-Option-General-Product-Description.pdf, retrieved from internet Dec. 20, 2017 (10 pages). |
| Digital Platform Litigation Documents Part 1, includes cover letter, dismissal of case DDE-1-21-cv-01796, IPR2023-00022 (documents filed Jan. 26, 2023-Oct. 7, 2022), and IPR2023-00085 (documents filed Jan. 26-Oct. 23, 2022) (748 pages total). |
| Digital Platform Litigation Documents Part 10, includes DDE-1-21-cv-01796 (documents filed Nov. 1, 2022-Dec. 22, 2021 (1795 pages total). |
| Digital Platform Litigation Documents Part 2, includes IPR2023-00085 (documents filed Oct. 20, 2022) (172 pages total). |
| Digital Platform Litigation Documents Part 3, includes IPR2023-00085 (documents filed Oct. 20, 2022) and IPR2023-00170 (documents filed Nov. 28, 2022-Nov. 7, 2022) (397 pages total). |
| Digital Platform Litigation Documents Part 4, includes IPR2023-00170 (documents filed Nov. 7, 2022) and IPR2023-00217 (documents filed Jan. 18, 2023-Nov. 15, 2022) (434 pages total). |
| Digital Platform Litigation Documents Part 5, includes IPR2023-00217 (documents filed Nov. 15, 2022) and IPR2023-00257 (documents filed Jan. 25, 2023-Nov. 23, 2022) (316 pages total). |
| Digital Platform Litigation Documents Part 6, includes IPR2023-00257 (documents filed Nov. 23, 2022) and IPR 2023-00346 (documents filed Jan. 3, 2023-Dec. 13, 2022) (295 pages total). |
| Digital Platform Litigation Documents Part 7, includes IPR 2023-00346 (documents filed Dec. 13, 2022) and IPR2023-00347 (documents filed Jan. 3, 2023-Dec. 13, 2022) (217 pages total). |
| Digital Platform Litigation Documents Part 8, includes IPR2023-00347 (documents filed Dec. 13, 2022), EDTX-2-22-cv-00243 (documents filed Sep. 20, 2022-Jun. 29, 2022), and DDE-1-21-cv-01796 (documents filed Feb. 3, 2023-Jan. 10, 2023 (480 pages total). |
| Digital Platform Litigation Documents Part 9, includes DDE-1-21-cv-01796 (documents filed Jan. 10, 2023-Nov. 1, 2022 (203 pages total). |
| El Kaed, C. et al., “Building management insights driven by a multi-system semantic representation approach,” 2016 IEEE 3rd World Forum on Internet of Things (WF-IoT), Dec. 12-14, 2016, (pp. 520-525). |
| Ellis, C. et al., “Creating a room connectivity graph of a building from per-room sensor units.” BuildSys '12, Toronto, ON, Canada, Nov. 6, 2012 (7 pages). |
| Extended European Search Report on EP Application No. 18196948.6 dated Apr. 10, 2019 (9 pages). |
| Fierro et al., “Beyond a House of Sticks: Formalizing Metadata Tags with Brick,” BuildSys '19, New York, NY, USA, Nov. 13-14, 2019 (10 pages). |
| Fierro et al., “Dataset: An Open Dataset and Collection Tool for BMS Point Labels,” DATA'19, New York, NY, USA, Nov. 10, 2019 (3 pages). |
| Fierro et al., “Design and Analysis of a Query Processor for Brick,” ACM Transactions on Sensor Networks, Jan. 2018, vol. 1, No. 1, art. 1 (25 pages). |
| Fierro et al., “Design and Analysis of a Query Processor for Brick,” BuildSys '17, Delft, Netherlands, Nov. 8-9, 2017 (10 pages). |
| Fierro et al., “Mortar: An Open Testbed for Portable Building Analytics, ” BuildSys '18, Shenzhen, China, Nov. 7-8, 2018 (10 pages). |
| Fierro et al., “Why Brick is a Game Changer for Smart Buildings,” URL: https://brickschema.org/papers/Brick_Memoori_Webinar_Presentation.pdf, Memoori Webinar, 2019 (67 pages). |
| Fierro, “Writing Portable Building Analytics with the Brick Metadata Schema,” UC Berkeley, ACM E-Energy, 2019 (39 pages). |
| Fierro, G., “Design of an Effective Ontology and Query Processor Enabling Portable Building Applications,” Electrical Engineering and Computer Sciences, University of California at Berkeley, Technical Report No. UCB/EECS-2019-106, Jun. 27, 2019 (118 pages). |
| File History for U.S. Appl. No. 12/776,159, filed May 7, 2010 (722 pages). |
| Final Conference Program, ACM BuildSys 2016, Stanford, CA, USA, Nov. 15-17, 2016 (7 pages). |
| Gao et al., “A large-scale evaluation of automated metadata inference approaches on sensors from air handling units,” Advanced Engineering Informatics, 2018, 37 (pp. 14-30). |
| Harvey, T., “Quantum Part 3: The Tools of Autonomy, How PassiveLogic's Quantum Creator and Autonomy Studio software works,” URL: https://www.automatedbuildings.com/news/jan22/articles/passive/211224010000passive.html, Jan. 2022 (7 pages). |
| Harvey, T., “Quantum: The Digital Twin Standard for Buildings,” URL: https://www.automatedbuildings.com/news/feb21/articles/passivelogic/210127124501passivelogic.html, Feb. 2021 (6 pages). |
| Hu, S. et al., “Building performance optimisation: A hybrid architecture for the integration of contextual information and time-series data,” Automation in Construction, 2016, 70 (pp. 51-61). |
| International Search Report and Written Opinion for PCT Appl. Ser. No. PCT/US2017/013831 dated Mar. 31, 2017 (14 pages). |
| International Search Report and Written Opinion for PCT Appl. Ser. No. PCT/US2017/035524 dated Jul. 24, 2017 (14 pages). |
| International Search Report and Written Opinion on PCT/US2017/052060, dated Oct. 5, 2017, 11 pages. |
| International Search Report and Written Opinion on PCT/US2017/052633, dated Oct. 23, 2017, 9 pages. |
| International Search Report and Written Opinion on PCT/US2017/052829, dated Nov. 27, 2017, 24 pages. |
| International Search Report and Written Opinion on PCT/US2018/024068, dated Jun. 15, 2018, 22 pages. |
| International Search Report and Written Opinion on PCT/US2018/052971, dated Mar. 1, 2019, 19 pages. |
| International Search Report and Written Opinion on PCT/US2018/052974, dated Dec. 19, 2018, 13 pages. |
| International Search Report and Written Opinion on PCT/US2018/052975, dated Jan. 2, 2019, 13 pages. |
| International Search Report and Written Opinion on PCT/US2018/052994, dated Jan. 7, 2019, 15 pages. |
| International Search Report and Written Opinion on PCT/US2019/015481, dated May 17, 2019, 15 pages. |
| International Search Report and Written Opinion on PCT/US2020/058381, dated Jan. 27, 2021, 30 pages. |
| Japanese Office Action on JP Appl. No. 2020-547334 dated Feb. 7, 2023 (10 pages). |
| Japanese Office Action on JP Appl. Ser. No. 2018-534963 dated May 11, 2021 (16 pages). |
| Koh et al., “Plaster: An Integration, Benchmark, and Development Framework for Metadata Normalization Methods,” BuildSys '18, Shenzhen, China, Nov. 7-8, 2018 (10 pages). |
| Koh et al., “Scrabble: Transferrable Semi-Automated Semantic Metadata Normalization using Intermediate Representation,” BuildSys '18, Shenzhen, China, Nov. 7-8, 2018 (10 pages). |
| Koh et al., “Who can Access What, and When?” BuildSys '19, New York, NY, USA, Nov. 13-14, 2019 (4 pages). |
| Li et al., “Event Stream Processing with Out-of-Order Data Arrival,” International Conferences on Distributed Computing Systems, 2007, (8 pages). |
| Midea, “IMM (Intelligent Manager of Midea): 4th Generation of Network Control System, Technical Manual,” URL: https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwjXvpGQ4ZjYAhXJPY8KHfWRBKgQFggmMAA&url=http%3A%2F%2Fwww.mdv-russia.ruk%2Fservice%2Ftekhnicheskaya-biblioteka%2Fcategory%2F178-gateways.html%3fdownload%3D1844%3Aimm-technical-manual&usg=AOvVaw0KhIMPfjb_czGZLsOgq-VE, retrieved from Internet Dec. 20, 2017 (188 pages). |
| Nissin Electric Co., Ltd., “Smart power supply system (SPSS),” Outline of the scale verification plan, Nissin Electric Technical Report, Japan, Apr. 23, 2014, vol. 59, No. 1 (23 pages with English language abstract). |
| Passivelogic, “Explorer: Digital Twin Standard for Autonomous Systems. Made interactive.” URL: https://passivelogic.com/software/quantum-explorer/, retrieved from internet Jan. 4, 2023 (13 pages). |
| Passivelogic, “Quantum: The Digital Twin Standard for Autonomous Systems, A physics-based ontology for next-generation control and AI.” URL: https://passivelogic.com/software/quantum-standard/, retrieved from internet Jan. 4, 2023 (20 pages). |
| Quantum Alliance, “Quantum Explorer Walkthrough,” 2022, (7 pages) (screenshots from video). |
| Results of the Partial International Search for PCT/US2018/052971, dated Jan. 3, 2019, 3 pages. |
| Sinha, Sudhi and Al Huraimel, Khaled, “Reimagining Businesses with AI” John Wiley & Sons, Inc., Hoboken, NJ, USA, first ed. published 2020 (156 pages). |
| Sinha, Sudhi R. and Park, Youngchoon, “Building an Effective IoT Ecosystem for Your Business,” Johnson Controls International, Springer International Publishing, 2017 (286 pages). |
| Sinha, Sudhi, “Making Big Data Work for Your Business: A guide to effective Big Data analytics,” Impackt Publishing LTD., Birmingham, UK, Oct. 2014 (170 pages). |
| The Virtual Nuclear Tourist, “Calvert Cliffs Nuclear Power Plant,” URL: http://www.nucleartourist.com/us/calvert.htm, Jan. 11, 2006 (2 pages). |
| University of California at Berkeley, EECS Department, “Enabling Scalable Smart-Building Analytics,” URL: https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-201.html, retrieved from internet Feb. 15, 2023 (7 pages). |
| Van Hoof, Bert, “Announcing Azure Digital Twins: Create digital replicas of spaces and infrastructure using cloud, AI and IoT,” URL: https://azure.microsoft.com/en-us/blog/announcing-azure-digital-twins-create-digital-replicas-of-spaces-and-infrastructure-using-cloud-ai-and-iot/, Sep. 24, 2018 (11 pages). |
| W3C, “SPARQL: Query Language for RDF,” located on The Wayback Machine, URL: https://web.archive.org/web/20161230061728/http://www.w3.org/TR/rdf-sparql-query/), retrieved from internet Nov. 15, 2022 (89 pages). |
| Wei et al., “Development and Implementation of Software Gateways of Fire Fighting Subsystem Running on EBI,” Control, Automation and Systems Engineering, IITA International Conference on, IEEE, Jul. 2009 (pp. 9-12). |
| Zhou, Q. et al., “Knowledge-infused and Consistent Complex Event Processing over Real-time and Persistent Streams,” Further Generation Computer Systems, 2017, 76 (pp. 391-406). |
| Japanese Office Action on JP Appl. No. 2020-547334 dated Sep. 12, 2023 (8 pages with English language translation). |
| Chinese Office Action on CN Appl. No. 201980031607.7 dated Jan. 25, 2024 (21 pages with English language translation). |
| Number | Date | Country | |
|---|---|---|---|
| 20190287147 A1 | Sep 2019 | US |
