[go: up one dir, main page]

WO2013037051A9 - Système et procédé de génération, de traitement et d'affichage de données relatives à des données de consommation, avec une application - Google Patents

Système et procédé de génération, de traitement et d'affichage de données relatives à des données de consommation, avec une application Download PDF

Info

Publication number
WO2013037051A9
WO2013037051A9 PCT/CA2012/000853 CA2012000853W WO2013037051A9 WO 2013037051 A9 WO2013037051 A9 WO 2013037051A9 CA 2012000853 W CA2012000853 W CA 2012000853W WO 2013037051 A9 WO2013037051 A9 WO 2013037051A9
Authority
WO
WIPO (PCT)
Prior art keywords
data
consumption data
consumption
graphical representation
datapoints
Prior art date
Application number
PCT/CA2012/000853
Other languages
English (en)
Other versions
WO2013037051A1 (fr
Inventor
Ron Samuel Dembo
Linda Bartram
Original Assignee
Zerofootprint Software Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zerofootprint Software Inc. filed Critical Zerofootprint Software Inc.
Publication of WO2013037051A1 publication Critical patent/WO2013037051A1/fr
Publication of WO2013037051A9 publication Critical patent/WO2013037051A9/fr
Priority to US13/907,021 priority Critical patent/US9390391B2/en
Priority to CA2825809A priority patent/CA2825809A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units
    • G06F3/1407—General aspects irrespective of display type, e.g. determination of decimal point position, display with fixed or driving decimal point, suppression of non-significant zeros
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
    • G01D4/00—Tariff metering apparatus
    • G—PHYSICS
    • G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
    • G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
    • G09G2340/00—Aspects of display data processing
    • G09G2340/14—Solving problems related to the presentation of information to be displayed
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/80—Management or planning
    • Y02P90/84—Greenhouse gas [GHG] management systems

Definitions

  • the disclosure relates generally to a system and method for generating, retrieving, processing and displaying data, with a particular implementation that processes resource consumption data and integrating the consumption data in an application.
  • consumption data can be analyzed and shown in a graphical form with a particular datapoint being shown within a range of values, for example, in an x-y graph.
  • Existing data processing and analysis tools are not provided to a user in easy-to-access applications.
  • a method of integrating consumption data with an application at a device comprises:
  • GUI graphical user interface
  • the GUI comprises: a table containing at least one day entry and at least one time entry for the at least one day entry; a first graphical representation in the table representing a calendar entry in the calendar data for the at least one day entry, when applicable; and a second graphical representation in the table representing a consumption data level in the consumption data for the at least one day entry.
  • the table may contain at least a week of day entries; a column may be provided for each of day of the week; rows in the table may mark times of the day; the first graphical representation may be marked in a cell in the table for the calendar entry in the calendar data for the at least one day entry, when applicable; and the second graphical representation may be a plurality of bar graphs in cells of the table representing consumption data levels in the consumption data for corresponding times and dates.
  • each bar graph of the plurality of bar graphs may have a length that is proportional to a related consumption data level in the consumption data; and each bar graph of the plurality of bar graphs may have a visual indicator representing a range in which the related consumption data level in the consumption data is located.
  • the method may generate a graphical representation of an interpolated consumption value between the first and second times.
  • the method may further comprise generating a message for the display when a value in the consumption data meets a target or exceeds a limit associated with the
  • the method may further comprise generating in the GUI on the display a third graphical representation of a consumption level at a current time in the consumption data for the device.
  • the third graphical representation may further comprise: an axis for a scale for a range of values for a set of datapoints in the consumption data at the current time; a first marker a first boundary for a first segment in a scale for a range of values for the set of datapoints at the current time; a first graphical feature representing the first segment, the first graphical feature spanning a first length along the axis; a second graphical feature representing a second segment in the set of datapoints, the second graphical feature spanning a second length along the axis; and a first indicator for a first datapoint at the current time.
  • a system for integrating consumption data into an application operating on a device comprises: a processor; a display device; a memory device; and a first module to provide instructions for the processor to process calendar data to generate a GUI of the calendar data on the display device.
  • the GUI comprises: a table containing at least one day entry and at least one time entry for the at least one day entry; a first graphical representation in the table representing a calendar entry in the calendar data for the at least one day entry, when applicable; and a second graphical representation in the table representing a consumption data level in the consumption data for the at least one day entry.
  • the table may contain at least a week of day entries; a column may be provided for each of day of the week; rows in the table may mark times of the day; the first graphical representation may be marked in a cell in the table for the calendar entry in the calendar data for the at least one day entry, when applicable; and the second graphical representation may be a plurality of bar graphs in cells of the table representing consumption data levels in the consumption data for corresponding times and dates.
  • each bar graph of the plurality of bar graphs may have a length that is proportional to a related consumption data level in the consumption data; and each bar graph of the plurality of bar graphs may have a visual indicator representing a range in which the related consumption data level in the consumption data is located.
  • the first module may provide further instructions for the processor to generate a graphical representation of an interpolated consumption value between a first and a second time for the second graphical representation where consumption data values in the consumption data is not available between the first and the second time.
  • the first module may provide further instructions for the processor to generate a message for the display when a value in the consumption data meets a target or exceeds a limit associated with the consumption data.
  • the first module may provide further instructions for the processor to generate a third graphical representation of a consumption level at a current time in the consumption data for the device.
  • the third graphical representation may further comprise: an axis for a scale for a range of values for a set of datapoints in the consumption data at the current time; a first marker a first boundary for a first segment in a scale for a range of values for the set of datapoints at the current time; a first graphical feature representing the first segment, the first graphical feature spanning a first length along the axis; a second graphical feature representing a second segment in the set of datapoints, the second graphical feature spanning a second length along the axis; and a first indicator for a first datapoint at the current time.
  • a method of processing data comprises: determining a start time and an end time in a set of datapoints comprising a plurality of data relating to a plurality of times; generating a first graphical representation of the set of datapoints on an output device and generating a second graphical representation of the datapoints at a target time on the output device with the first graphical representation.
  • the first graphical representation includes: a time axis; a value axis; a plot of the set of datapoints between the start time and the end time; a plot of a first band relating to the set of datapoints between the start time and the end time; a plot of a second band relating to the set of datapoints between the start time and the end time; a plot of a first boundary of a first band of values relating to the set of datapoints between the start time and the end time; a plot of a second boundary of a second band of values relating to the set of datapoints between the start time and the end time; and a cursor for marking the target time between the start time and the end time.
  • the second graphical representation includes: an axis for a scale for a range of values for the set of datapoints at the target time; a first marker a first boundary for a first segment in a scale for a range of values for the set of datapoints at the target time; a first graphical feature representing the first segment, the first graphical feature spanning a first length along the axis; a second graphical feature representing a second segment in the set of datapoints, the second graphical feature spanning a second length along the axis; and a first indicator for a first datapoint at the target time.
  • the method may further comprise: for the plot of the set of datapoints in the first graphical representation, interpolating datapoints for values between a third time and a fourth time where data is not available for a period of time.
  • the method may further comprise: for the plot of the set of datapoints in the first graphical representation, extrapolating datapoints for values after a third time when data from the datapoints after that third time is not available.
  • the plot of the first boundary of the first band of values relating may be determined from a factor of a standard deviation from a mean value for the set of datapoints between the start time and the end time.
  • the standard deviation may be based on a normal distribution for the set of datapoints.
  • the scale may have a plurality of markers that are consistent in scale between the start point and the end point.
  • the second length may be approximately equal to the first length; and the range of datapoints of the first segment may have a different scale to a range of datapoints in the second segment.
  • the method may further comprise generating in the graphical representation a second indicator for a second datapoint in the set of datapoints.
  • the second datapoint may represent a target value or a historic value for the first datapoint.
  • the method may further comprise generating a second graphical representation with the graphical representation for a second set of datapoints.
  • the second set of datapoints may relate to the consumption data or other data, but the second set of datapoints may relate to a timeframe that differs from the timeframe associated with the first set of datapoints.
  • the first graphical feature may be provided in a first colour; and the second graphical feature may be provided in a second colour.
  • the first colour may be green; and the first segment may represent a range of target values in the set of datapoints. Alternatively, the first segment may represent actual values.
  • the set of datapoints may represent consumption data for a resource; and the first datapoint may represent consumption of the resource at a location.
  • the set of datapoints may represent cost or emission data for a resource.
  • the method may further comprise: analyzing model data to identify a goal for consumption of the resource at the location; and generating in the graphical representation a second indicator for the goal or historical data.
  • the method may further comprise determining a progression rate to change usage of the resource at the location from the first datapoint to the goal.
  • the method may further comprise generating control signals to control a device to implement the progression rate.
  • the goal may be based on at least one of time of using savings and a rebate program.
  • the model data may include goal data based on at least one of time of using savings and a rebate program.
  • a system for processing data comprises: a processor; a display device; a first module to provide instructions for the processor to process a set of datapoints to generate a first graphical representation of the datapoints on the display device; a second module to provide instructions for the processor to process the set of datapoints; and a third module to provide instructions for the processor to generate a second graphical representation of the datapoints for the display device, by generating data for the second graphical representation with the first graphical representation.
  • the first graphical representation includes: a time axis; a value axis; a plot of the set of datapoints between the start time and the end time; a plot of a first band relating to the set datapoints between the start time and the end time; a plot of a second band relating to the set of datapoints between the start time and the end time; a plot of a first boundary of a first band of values relating to the set of datapoints between the start time and the end time; a plot of a second boundary of a second band of values relating to the set of datapoints between the start time and the end time; and a cursor for marking a target time between the start time and the end time.
  • the second module includes instructions to: determine a scale for a range of values of the set of datapoints at the target time; determine a first segment in the range of values of the set of datapoints at the target time; and determine a second segment in the range of values of the set of datapoints at the target time.
  • the third module generates data for the second graphical representation relating to: an axis for the scale; a first marker for the first boundary; a first graphical feature
  • the system may comprise a fourth module to. analyze model data to identify a goal for consumption of the resource at the location; and generate additional data for the graphical representation for a second indicator for the goal.
  • the second length may be approximately equal to the first length; and the range of datapoints of the first segment may have a different scale to a range of datapoints in the second segment.
  • the third module may: generate data to produce the first graphical feature in a first colour; and generate data to produce the second graphical feature in a second colour.
  • the first segment may represent a range of target or actual values in the set of datapoints.
  • the data and the additional data for the graphical representation may be provided to the output device.
  • the output device may be a display associated with a device in communication with the system.
  • the system may further comprise a fourth module to utilize the goal and the first datapoint to control operation parameters of one device at the location.
  • FIG. 1 is a schematic diagram of a network with a server and a device providing data analysis according to an embodiment
  • FIG. 2 is a block diagram of the server and device of Fig. 1 according to an embodiment
  • FIG. 3 is a flowchart of a data process executed by the server of Fig. 1 according to an embodiment
  • FIG. 4 is a flowchart of a data visualization process executed by the server of
  • FIG. 1 according to an embodiment
  • Fig. 5 is a first representative data visualization output in a graphical user interface
  • Fig. 6 is a second representative data visualization output in a graphical user interface
  • Fig. 7 is a third representative data visualization output in a graphical user interface
  • Fig. 8a is a fourth representative data visualization output in a graphical user interface
  • Fig. 8a (ii) is an expanded view of part of the fourth representative data visualization output graphical representation generated by the server of Fig. 1 according to an embodiment
  • Fig. 8b is another version of part of the fourth representative graphical
  • Fig. 8c is yet another version of part of the fourth representative graphical
  • Fig. 9 is a flowchart of another data graphing process executed by the server of
  • FIG. 1 according to an embodiment
  • Fig. 10 is a flowchart of a data interpolation process executed by the server of
  • FIG. 1 according to an embodiment
  • FIG. 11 is a flowchart of a data extrapolation process executed by the server of
  • FIG. 1 according to an embodiment
  • Fig. 12 is a flowchart of a data scenario process executed by an application
  • Fig. 13 is a representative data visualization output in a graphical representation generated by the application of Figs. 1 and 12 according to an embodiment
  • Fig. 13 (ii) is an expanded view of part of the representative data visualization output graphical representation generated by the device of Figs. 1 and 12;
  • Fig. 14 is a flowchart of a data scenario process executed by the server of Fig. 1 according to an embodiment.
  • An embodiment generally provides a system, method and device for generating, retrieving, processing and displaying data, with an implementation that processes resource consumption data in a set of datapoints.
  • One feature of an embodiment generates visual representations of consumption data for a datapoint in a time frame and provides visual cues for gauging the relative consumption at a given time within statistical models and data interpolation and extrapolation features.
  • Another feature of an embodiment generates visual representations of consumption data for a datapoint in the set with visual cues providing comparisons to consumption data of one or more peers in the set.
  • the visual representation can provide a scale indicating a total range of values for the datapoints in the set (e.g. from a minimum to maximum value(s)) and an indicator of relative usage values (e.g. visual cues indicating distributions of values within the set).
  • Another feature integrates the consumption data into an application operating on a device.
  • Fig. 1 shows system 100 where network 102 provides data and control
  • server 104 provides data collection, storage, processing and analysis features of an embodiment.
  • Database 110 is connected to server 104 and provides a repository for data for server 04.
  • Device 106 is configured to access server 104, initiate commands for server 104 to conduct analysis on data from database 110 and process the data and generate graphical representations of aspects of the data analysis on its display for viewing by user 108.
  • Network 102 can be implemented in any known architecture, providing wired and/or wireless connections to its elements, and including one or more interface servers (not shown) that may allow network 102, and its elements, to be in communication with other networks and their elements.
  • Network 102 may be implemented as a local area network (LAN) that provides local wired connections to its elements.
  • Network 102 may be connected to the Internet (not shown) via an interface server (not shown).
  • Network 102 may also be a Wi-Fi network generally following standards set by the IEEE LAN/MAN Standards Committee, known as IEEE 802, through its working group "11".
  • Security features may be provided by network 102. For example, access to its systems may be provided through secure protocols/links, e.g. through a Hypertext Transfer Protocol Secure (HTTPS) scheme.
  • HTTPS Hypertext Transfer Protocol Secure
  • server 104 With features of exemplary network 102 and selected elements provided, further detail is provided on server 104 and device 106. Each is described in turn.
  • FIG. 2 illustrates details of its internal components.
  • server 04 is a processor-based computing platform. It may have the form factor f a rack-mounted, desktop or laptop computer. It may be a minicomputer. It may be a virtual omputing device comprising processing modules that are installed on one or more devices.
  • processor 202 Within server 104, there is processor 202, memory 204, input system 206, output ystem 208, and storage system 210.
  • Processor 202 controls the overall operation of server 04 through instructions provided to it that are typically stored in its memory 204 and / or torage system 208.
  • Exemplary processors for processor 202 may include "x86" - compatible rocessors (trade-mark) available from Intel Corporation.
  • Memory 204 may be dynamic andom-access memory, flash memory or other volatile and non-volatile storage devices.
  • an operating system DS Controlling overall operating of processor 202 (and as such, server 104), an operating system DS) is provided that may be stored in memory 204.
  • An exemplary OS is Windows Server xade-mark) by Microsoft Corporation.
  • Software modules 212 provide a series of program instructions to execute various ommands on processor 202. Such modules are typically stored in either memory 204 and / or torage system 210.
  • software modules include data capture module 212A, ata analysis module 212B, data visualization module 212C, data scenario module 212D;
  • ontrol module 212E calendar module 212F and other modules 212G. Further details on these oftware modules are provided below.
  • Input system 206 is part of a class of components for receiving data input by server 04.
  • Input system 206 may a keyboard, mouse device, trackball, touchpad, touch screen, licrophone, accelerometer, lightpen or other device.
  • Input system 206 may also include a omponent that receives data over network 102 or via application programming interfaces ⁇ P ⁇ s).
  • Input system 206 may also include a component configured to receive electronic data " om a monitoring device, such as a utility meter, smart meter, water meter, volt meter, imperage meter, light meter, wind meter, hydrometer, etc.
  • Input system 206 may be an indirect iata capturing system.
  • system 206 may be camera that records images of a leter, capturing changes in its readings. Processes may then be provided to analyse the nages and extract the data readings from them.
  • Output system 208 may be a component for transmitting data to an internal or xternal component or device to server 104.
  • Output system 208 may include a display, speaker r printer.
  • Output system 208 may also include a network component configured to transmit 3 ⁇ 4ta to an external device, through a connection and / or through network 102.
  • Storage system 210 stores data and may be internal to server 104; it may be comparable to storage 110 (Fig. 1 ). Alternatively, storage system 210 may be external to server 104. Where storage system 210 is external to server 104, storage system 210 may be in direct communication with server 104 or in communication with server 104 via a network (not shown), such as a LAN. Storage system 210 may comprise any type of appropriate physical storage medium, such as hard drives and/or flash memory. Access to data in storage system 210 may be controlled through software operating system on and / or through system 210, such as through a database application, such as Access (trade-mark) or SQL.
  • a database application such as Access (trade-mark) or SQL.
  • device 106 it has similar components to server 104. As such, Fig. 2 may be used to represent corresponding components of device 06.
  • device 106 is a processor-based electronic computing device. It may by a computer, laptop computer, minicomputer, tablet computing device, smart phone, personal digital assistant (PDA) or other computing device.
  • Device 106 may have internal components that are analogous to internal components of server 104, including processor 202, memory 204, input system 206, output system 208 and storage system 210.
  • device 106 may comprise a network component (as part of its input system 208) for receiving a data from server 104 and display and / or print as part of its output system 208.
  • server 104 and device 106 may comprise a single device, and in such embodiments.
  • flow chart 300 shows an exemplary data capture process in receiving data by an embodiment. It may be executed or controlled in whole or in part by server 104. Therein, data capture module 212A (Fig. 2) may provide programming code for execution on processor 202 (Fig. 2) to effect execution of the process. The process may also operate in whole or in part on device 106.
  • an embodiment generates visual graphical representations of data, in particular consumption, cost or emission data.
  • data can be provided from any data capturing device (e.g. a smart gas meter, smart electric meter, utility meter, water meter, volt meter, amperage meter, light meter, wind meter, volatile organic compound (VOC) sensor, oxygen sensor, carbon dioxide sensor, air quality sensor etc.) or any data source (e.g. tabular data such as historic daily temperature readings, daily resource consumption data, etc.).
  • Data can be collected and stored at a central or distributed system through network 102.
  • Transmitted data can contain a data value and additional information (e.g.
  • the data may relate to usage data from utility bills, data received from utility meters, bulk information received from third-party databases or data submitted by third-parties via an API made available by input system 206. After start process 302, such data is received from an input system in process 304.
  • the data may reflect instantaneous usage data, data gathered over a time period, change data, rate of change data, projection data of usage or other values.
  • the data may indicate a rate of water usage every hour, on the hour, for a particular household, the data being a negative or positive value representing the difference in rate for the present point in time, as compared to an earlier point in time.
  • Additional data that may be provided includes identifying information about the data source, e.g. serial number of device, street address for house for meter, size information for house, weather data for the day, utility prices for the day, etc.
  • the data is processed and stored. This may involve tagging the data with a timestamp and source details and may involve storing the data in a certain section of database 1 10. Some data may be discarded without being stored, for example, if the data is out of range, corrupted, inconsistent, erroneous or invalid.
  • the received data is converted into standardized units before storage.
  • data capture module 212A may receive data comprising a first household's usage of natural gas in cubic feet over the course of every hour, and a second household's usage of natural gas as an instantaneous rate in litres / minute, at the start of every minute. Data capture module 212A may convert this data into predetermined standardized units, such as cubic meters per day, including by applying standard estimation techniques such as interpolation or extrapolation, as necessary.
  • a stored data element in database 1 10 per flow chart 300 may be referred to as a datapoint.
  • Database 110 contains multiple different datapoints.
  • a collection of datapoints (grouped by applicable parameters), is referred to herein as a dataset for the purpose of convenience and not limitation.
  • Flow chart 300 ends at process 308.
  • flow chart 400 shows an exemplary data analysis process for analyzing captured data by an embodiment. Again, the process is described as operating on server 104, but it may also operate in whole or in part on device 106.
  • data analysis module 212B (Fig.
  • One or more servers 104 and / or devices 106 may maintain a web site that produces visual representations of datasets based on inputs provided to the web site. Such a web site may be accessed by any device connected to the Internet.
  • One or more processes of flow chart 400 may be executed on a "thin” or a "thick" client in network 102, depending on computing power, storage capacity and / or network connections of the client.
  • the process starts at process 402, which may be initiated on a periodic basis (e.g. once an hour, once a day, every night, etc.) and / or on an event basis, such from a request from an external device, such as device 106 or from a software module operating on server 104 and / or device 106.
  • a set of parameters for a visualization request are provided.
  • the parameters may have been preset, as a default, or may be provided with the request itself.
  • a graphical user interface may be provided on device 106 showing an interface on its display providing options and fields for user 108 to define the parameters for the request.
  • parameters from the request are used to determine what data is extracted.
  • the parameters may include one or more of: a time boundary (e.g. data from today, last hour, this spring, this year, last year, etc.); a device reading identifier (e.g. readings from one or more power meters from a first residence, power meters, carbon meters, water meters, wind meters, temperature meters, humidity meters, barometers, etc.); a geographic/location boundary (e.g. reading from one residence, residences in a city block, residences in a postal code, a cottage, an industrial complex, one or more rooms within a building, one or more specified industrial plants, etc.) and other ad hoc parameters (e.g. only meters of a particular brand).
  • a time boundary e.g. data from today, last hour, this spring, this year, last year, etc.
  • a device reading identifier e.g. readings from one or more power meters from a first residence, power meters, carbon meters, water meters, wind meters, temperature meters
  • a database command is built from the request and its parameters and a database query is sent to a target database, such as database 110, to retrieve a dataset populated with records in the database that match the request.
  • the retrieved dataset is processed.
  • Part of the processing may include filtering the data. This may be an optional process. Filtering may eliminate extraneous datapoints in the dataset. For example, filtering may eliminate datapoints that are above and / or below a threshold, or that are outside a given time or geographic parameter.
  • the filter parameters may be set in the search parameters and / or there may be a default set of filtering parameters accessed by the system.
  • the retrieved dataset may contain data from multiple sources relating to different consumption or usage data over a particular time period. Part of the filtering may include making adjustments to the dataset to level, normalize and / or localize the data.
  • Levelling adjusts the dataset to correct for different coverage of different data sources, to facilitate comparison of datapoints. For example, if the dataset includes
  • consumption data for a source over a particular time period may not be available from other sources.
  • the dataset may be filtered to utilize datapoints that are complete over a time period for all sources.
  • values for missing or incorrect values may be interpolated or extrapolated from similar data.
  • Normalizing data adjusts the dataset so that comparisons can be made for different data sources.
  • readings for a site spanning a number of days/weeks/seasons can be normalized to unitized values to allow them to be more easily compared.
  • readings from different locations can be normalized to unitized values to allow them to be more easily compared.
  • a dataset may include consumption data for a time period from multiple sources.
  • the sources may have different attributes that may affect consumption values.
  • a data source may correspond to a household with multiple occupants, whereas another data source may correspond to a household with a single occupant.
  • the dataset may be adjusted so that consumption usage is calculated on a per household occupant basis.
  • Data for differently sized locations can be normalized to a per square foot/meter basis to allow comparison. Normalizations may be performed to include more than one factor (e.g. data can be recalculated to be presented on a per square foot and a per occupant basis).
  • a balance point may be used, representing a 'normal' value for a factor relating to the data.
  • the balance point for heating a building may be a baseline building temperature at which the building does not need to be heated internally. If the building temperature is above that baseline, then the building does not require internal heating.
  • the building temperature can include readings from external temperatures, internal ambient temperature and / or the temperature of the frame of the building. In a given winter, a building's heating balance point may be constant, but the heating may be activated for longer or shorter periods over the winter depending on the outdoor temperature.
  • the difference between the current building temperature and the balance point can be used as a factor in normalizing the data. Additional factors can be provided once the difference is calculated.
  • the heating consumption data is normalized, extra energy usage for heat on colder days can be normalized against less energy usage for heat on warmer days. Comparable normalization calculations can be provided for energy usage for cooling a building.
  • Localization adjusts values of the datapoints to correspond to a particular user's actual or predicted preferences. For example, values may be stored in storage system 210 in standardized units such as cubic meters, whereas if system 100 is aware that user 108 is located in the United States, data analysis module 21 may adjust all values to be in cubic feet, instead of cubic meters. Other types of localization adjustments that adjust and / or normalize the dataset may be provided. Localization may adjust values in the dataset to local parameters (e.g. the local time zone, the local currency, etc.).
  • local parameters e.g. the local time zone, the local currency, etc.
  • datasets may be filtered to take into account weather or seasonal effects. Adjustments may also be made for a given data source in view of a change to the data source over a period of time. For example if a household replaces its furnace then an adjustment may be made for consumption data before the replacement. It will be appreciated that other filtering and adjustments can be made.
  • the retrieved dataset may be filtered to account for any permission levels of the entity making the request.
  • the request from process 404 may originate from a school and the target analysis may be for energy usage of the school against its peers.
  • the extracted dataset may collect energy usage records for all schools in a relevant district.
  • the filtering may then identify the relevant peers (based on school board information, postal codes, etc.). Filtering may also remove outliers from the retrieved dataset. For example, data records that do not show any usage of electricity could be removed from a data set on the basis that such data records are clearly outliers, and unlikely to be accurate data.
  • the data may contain multiple values directly related to consumption or usage.
  • a data record may indicate for a particular household and a particular time period both usage of electricity and natural gas during that time period. With such data, a sort/filter may be applied to extract the relevant datapoint(s).
  • any of the filtering processes described herein may be conducted by either server 104 and / or device 106. In some instances, such processes may be conducted at any time prior to generation of the visual representation of the dataset.
  • the filtered dataset is analyzed.
  • the data is analyzed to identify segments in the dataset which can be used to indicate notable parts of the dataset when a visual representation of the dataset is generated.
  • the analysis one or more of the following determinations may be made, in any order.
  • a first determination may be to identify boundaries of the dataset, per process 408A. This may include identifying the start and end datapoints.
  • the parameters for the end points may be based on time parameters (e.g. start and end times) or value parameters (e.g. minimum and maximum values).
  • a scale may be determined for the range of values for datapoints between the start and end datapoints. This may have been done at the filtering process. With a scale and one or more end points determined for the dataset, a range of values can be established for the dataset when a visual representation is made of it.
  • a second determination may be to identify one or more segments and their boundaries with the dataset, per process 408B.
  • a segment is a section of the dataset and the two terms can be used interchangeably.
  • One segment or multiple segments may be provided in a dataset. Generally, the segments are sequential, but they do not have to be.
  • a gap may or may not separate segments.
  • the number of segments can be used to group datapoints together (e.g. datapoints above, below or within certain ranges).
  • each segment can be displayed in a contrasting manner to the other segment to visually distinguish the segments from each other. This provides a visual cue to the viewer as to a distribution of datapoints in the dataset.
  • the boundaries for each segment divide the segments into equal parts or non-equal parts. Further detail is provided on the segment determination below.
  • a third determination may be to identify a location of a specific datapoint in the dataset, per process 408C.
  • the dataset may have one or more segments.
  • a value of a target datapoint will determine in which segment it is shown. For example, for an exemplary dataset of meter readings for houses within a city block, meter data for a particular house can be selected. That meter reading's value is shown by an indicator in a visual representation for the meter readings of the city block. This provides a visual cue in the representation of the relative location of that house's meter readings compared to aggregate readings for that block.
  • a visual representation of the dataset is produced using the dataset, the boundaries of the dataset, the segments and the location of a given datapoint and any other parameters that have been provided.
  • Any device having access to a dataset e.g. server 104 and / or device 106) can generate the visualization.
  • the visualization can be generated on a display of a device (e.g. at device 106, server 104 or a remote device to network 102).
  • data visualization module 212C (Fig. 2) may provide programming code for execution on processor 202 (Fig. 2) to effect execution of the process.
  • an embodiment utilizes the dataset to provide a graphical representation of same.
  • An embodiment can provide a plurality of different visual
  • Fig. 5 shows a first exemplary graphical representation of the output in the graphic form of gauge 500, which may be generated on an output device such as a display and / or a printer.
  • An exemplary dataset used to produce gauge 500 is provided in Table A:
  • gauge 500 shows datapoints relating to energy consumption of homes in a city block.
  • the total number of datapoints would be N+M+O+P.
  • gauge 500 has a form of a semi-circle, mimicking a layout of a speedometer.
  • Start point 502A is located at the bottom left edge of the bottom of gauge 500, representing the lowest range of data in the dataset.
  • End point 502B is located at the bottom right edge of the bottom of gauge 500, representing the highest range of data in the dataset (namely data having values below 155,672).
  • Scale 504 is located along the perimeter of the semicircle and represents an axis against which datapoints in the set are plotted. Scale 504 also indicates datapoints between the lowest and highest ranges. Markers for specific values in the dataset may be provided on scale 504. It will be appreciated, while gauge 500 appears to be a two dimensional form, the datapoints are effectively in a tabular, one dimensional form, where all datapoints reflect a certain meter reading.
  • segments have been defined for the dataset.
  • the segments can represent one or more segments, dividing the dataset into halves, thirds, quarters, fifths, etc., with each segment being approximately the same size in the visual representation.
  • an exemplary parameter for process 408C has determined that there will be three segments of approximately equal size (in terms of visual area in gauge 500).
  • boundary 51 OA at datapoint "3,768” shows a boundary between the first (lowest) third and the middle third for values in the dataset.
  • Boundary 510B at datapoint "8,607” shows a boundary between the middle third and the highest third for values in the dataset.
  • data analysis module 212A may determine boundary values using statistical analysis tools and calculations, including distribution analysis tools. Such analysis may identify boundaries based on average values, population distribution values (e.g. to identify boundaries where one third of the values are in the lowest third, one third are in the middle third and one third are in the upper third). The boundaries are shown along the axis of scale 504.
  • Gauge 500 shows the defined segments and their boundaries. For an example where a dataset has three segments, gauge 500 shows three segments 508A, 508B and 508C. Segments 508A and 508B are separated by boundary 51 OA and segments 508B and 508C are separated by boundary 510B. For ease of identifying segments, different graphical features are used to visually differentiate the segments from each other. In one embodiment, the number of datapoints in each segment is the same or almost the same. Colours can be used to show different segments to provide a visual cue for the relative locations of data within the dataset. Here, segment 508A is shown in green; segment 508B is shown in yellow and segment 508C is shown in red.
  • a "green-yellow-red” colour scheme provides a "go-caution-stop” visual analogy that a viewer can understand and interpret information provided in gauge 500.
  • Each segment can represent a different relative state its datapoints. Datapoints in a "green” segment can represent values having an ideal, target, best and / or preferred value (e.g. least consumption, most efficient, etc.); datapoints in a "yellow” segment can represent values having an acceptable value (e.g. within an average, etc.); and datapoints in a "red” segment can represent values having a non-ideal, worst or least preferred value (e.g. most consumption, least efficient, etc.).
  • Representations and ranges of values may be defined based on the types of data in the datapoints, the number of datapoints, target usage conditions (e.g. based on laws and regulations, such as vehicle emissions regulations) and other factors.
  • Other graphical features can be provided to differentiate segments, e.g. black-white, white-grey, green-red (indicating "go/stop"), rainbow colour schemes, different background patterns in segments (e.g. dots, stripes, stippled lines, etc.), different labels provided for different segments, etc.
  • Values for the scales and additional marking for graph 500 may have been determined during localization, described above for process 406 (Fig. 4).
  • localization is conducted at server 104 (Fig. 1 ).
  • localization is done at device 106 (Fig. 1).
  • Localization can include providing markings for values that adhere to local idioms. For example, either a period ".” or a comma ",” can be used to separate the integer portion of a number from its fractional portion, depending on whether North American or European number marking conventions are used. Similar localization changes may be made to the data to for time, date (e.g. MM/DD/AA or DD/MM/AA formats) and currency idioms.
  • the visual presentations can be augmented to show additional data in two and three dimensions.
  • a two dimensional representation may introduce another parameter on another axis (e.g. time or location).
  • additional "slices" of gauge 500 may be shown stacked against gauge 500 showing different usage snapshots at different times for the city block or showing different usage snapshots for different city blocks at a given time.
  • a three-dimensional representation may introduce two parameters on two additional axes (e.g. axes showing time and location).
  • scale 504 can be linear, non-linear or linear in sections and non-linear in other sections, so that the scale values along scale 504 differ in different sections. Values for such sections can be based in part on the number of segments defined. Markers 506 show values along scale 504 in major and minor increments. In this representation, scale 504 is linearly scaled within each segment 508. For example, in segment 508A markers are calibrated to be approximately 1 ,256 units apart; in segment 508B markers are calibrated to be approximately 1 ,613 units apart; and in segment 508C markers are calibrated to be approximately 49,022 units apart. Notably, among the three segments for this exemplary dataset, there is no linearity of calibrations.
  • Gauge 500 shows an exemplary graphical representation where each segment 508A, 508B and 508C in gauge 500 is approximately of equal size, where each segment spans approximately the same length along the axis of scale 504. However, as noted above each segment may not show an equal range of datapoints along scale 504: each segment covers a range of datapoints in the dataset that may not be linear to a range of datapoints in another segment.
  • segment 508A shows to a portion of scale 504 for datapoints having values between 0 and 3,768
  • segment 508B corresponds to a portion of scale 504 for datapoints between 3,768 and 8,607
  • segment 508C corresponds to a portion of scale 504 for datapoints between 8,607 and 155,672.
  • markers 506 along scale 504 may be presented in different colours, fonts and / or emphasis (e.g. bold, italics) to indicate the different segments.
  • segments 508 and scale 504 of gauge 500 provide an indication of an overall distribution of datapoints within a dataset.
  • Gauge 500 also provides an indication of the location of a particular datapoint within the distribution, through indicator 512.
  • indicator 512A provides a visual marker noting a value in scale 504 for a particular datapoint.
  • indicator 512A is presented as a needle within the speedometer paradigm of gauge 500.
  • Other forms for indicators can be provided (such as a box marker along scale 504).
  • Indicator 512A "points" to a value of around 2,512, representing the energy usage for the "current household” within the block of houses, per Table A.
  • An embodiment also provides a second indicator 512B on gauge 500 that can be used to mark a second value in scale 504.
  • the second value may represent a goal, target and / or historic datapoint (e.g. energy usage for the house last week).
  • the second value represents a Target Household's consumption level, per Table A.
  • gauge 500 is shown as a speedometer.
  • other speedometers can be circular, rectangular, square, oval or linear.
  • General characteristics of a speedometer are that there is a scale having values identified thereon than progress from a first value to a higher value or from a first value to a lower value. The progression may or may not be linear.
  • segments for datapoints can be identified an indicator can be provided showing a current value of a target datapoint. The location of the indicator may be updated periodically depending on updates to the dataset.
  • Fig. 6 shows a second exemplary graphical representation of gauge 600.
  • Gauge 600 has comparable elements to gauge 500 (Fig. 5), including start point 602A, end point 602B, scale 604, three segments 608A, 608B and 608C, boundaries 61 OA and 610B and indicators 612A and 612B.
  • each segment has an equal number (or close to equal number) of datapoints to one or more or all of the other segments. If one datapoint moves from one segment to another, one datapoint may be moved out so that the number of datapoints remains equal. This also allows the bar to be moved up as the consumption decreases.
  • gauge 600 is shown as a linear scale from start point 602A to end point 602B.
  • scale 604 may show units in a logarithmic or exponential scale.
  • segments 608A, 608B and 608C may have different sizes and boundaries 61 OA and 610B may be located along scale 604 to reflect those different sizes.
  • segment 608B is larger than segment 608A, which is larger than segment 608C.
  • segment 608B shows that it has the widest dispersion of datapoints for the segments.
  • segments may have different numbers of datapoints among themselves.
  • the size of a segment may reflect the relative number of datapoints within that segment.
  • Fig. 7 shows a third exemplary graphical representation of gauge 700, shown as a thermometer.
  • gauge 700 has comparable elements to gauges 500 and 600 (Figs. 5 and 6), including start point 702A, end point 702B, scale 704, three segments 708A, 708B and 708C, boundaries 71 OA and 710B and indicators 712A and 712B.
  • the values on scale 704 may be non-linear (per Fig. 5) or linear (per Fig. 6).
  • output of an analysis of the datapoints may be represented in other graphical representations, such on a line graph, in a pie chart, in a bulls-eye chart, in two- and three-dimensional charts (e.g. a chart having time as one dimension in addition to the usage charts) or other forms.
  • Data may also be presented in a tabular form, where sections of a table may be highlighted to show segments and indicators.
  • an embodiment provides tracking of consumption data and generation of graphs and charts where a large data set is provided. For example, in real-time
  • consumption data can be gathered and stored for a given site (or collection of sites).
  • An embodiment provides graphical tools to show historic, current and projected levels of consumption. Figs. 5-7 and their related descriptions provide a snapshot of a current level of consumption/use of the tracked item. The snapshot can be at a certain point in time, such as a current time, a specific previous time, a projected time or an average over a determined period of time.
  • An embodiment provides additional data, in graphical form, where a range data of consumption levels over a period of time tracked in a dataset.
  • FIG. 8a shows line graph 800a representing power consumption over a period of time at a specific site.
  • Y-axis 802 shows an exemplary range of power consumption amounts.
  • X-axis 804 shows an exemplary range times of power consumption amounts.
  • the x and y-axes in graph 800a-c have linear scales, but in other embodiments, either axis may have non-linear scales (e.g. disjoint, logarithmic, algorithmic etc.).
  • Line 806 shows a series of datapoints at a series of different times, where each datapoint represents the level of consumption (in the y-axis) at that related time (in the x-axis).
  • Line 806 may be replaced with a series of discrete markers (e.g. dots) representing datapoints at discrete instances of time.
  • values between actual data values i.e. between time intervals
  • line 808 a specific level of consumption can be shown. This specific level of consumption can map to a consumption gauge, such as gauge 810 which can be generated in concert with graph 800a.
  • Gauge 810 may represent a snapshot of a consumption data in the datapoints at a target time that can be changed via movement of a cursor in a GUI.
  • Line 808 may represent the cursor and the consumption values at that instance of time may be provided in gauge 810.
  • graphs 800a-c and gauge 810 may be simultaneously generated in a screen on a display of device 106 (Fig. 1).
  • Gauge 810 is comparable to gauge 500 (Fig. 5), including having segments 508A-508C, with green, yellow and red backgrounds.
  • the mapping of the value of line 806 at line 808 does not graphically correspond to the position of the indicator in gauge 810 along its scale; however, it is preferred that there is a correspondence.
  • Graph 800a has a series of background ranges shown in the plot area of graph 800a, representing bands of ranges of consumption. To facilitate distinguishing among the bands, each band may be shown in a different colour. A value for a band (namely, its range) at a point in time may correspond to a segment as provided in gauges 500 or 600 (Figs. 5 and 6). In one embodiment, three bands are provided, namely use bands 812, 814 and 816. Band 812 is shown in the lower portion of graph 800a in green and represents a low consumption level for various times along the x-axis. Band 814 is shown in the middle portion of graph 800a in yellow and represents an average of consumption level for various times along the x-axis.
  • Band 816 is shown in the upper portion of graph 800a in yellow and represent a high consumption level for various times along the x-axis. It will be seen that features of the segments described for gauges 500 and 600 can be mapped to the bands for graphs 800a-800c and vice versa.
  • the sizes and locations of the bands and their boundaries at a given time need to be defined. It will be seen that there is a boundary between the lower portion and the middle portion and a boundary between the middle portion and the upper portion.
  • determination of the values of the ranges for the bands and boundaries may be established via distribution analysis, based on historic consumption data for the site and / or data from one or more acceptable peer(s) comparable to the site.
  • the bands may represent approximate "thirds" for a range of consumption levels, where the middle portion represents the "middle” third of the distribution, the lower portion represents the low third of the distribution and the upper portion represents the upper third of the distribution.
  • the ranges for the bands may be based on the mean or median of the distribution.
  • the consumption data can be assumed to follow a normal (Gaussian) distribution.
  • the center of the distribution can be considered to be the middle of the middle band.
  • the center of the distribution can be the mean or median of the consumption values.
  • the lower boundary may be set at values that are a factor of a standard deviation.
  • the lower boundary in one embodiment is set to be 1/6 of a standard deviation lower the center, where 1/6 is half of 1/3 of the band.
  • the upper boundary can be set at values that are 1/6 of a standard deviation above the center.
  • Other factors, equations and offsets may be used and other distributions may be used (e.g. log-normal, Pareto, Poisson, exponential and others).
  • the consumption data can be shown as per gauge 500 (Fig. 5) where each segment 508 is approximately the same size. It will be appreciated that other factors for boundary values can be applied (e.g. 1/2, 1/3, 1/4 of a standard deviation, etc.).
  • a distribution can be generated from consumption data for a site for a previous period of time.
  • the period of time may be measured in business days, e.g. consumption data for the previous twenty (20) business days. Any range of data may be used (e.g. from 0 day to 3 years or more).
  • One embodiment examines energy consumption at a site at continuous points in time and compares the value to historical consumption values.
  • An embodiment estimates the mean and standard deviation at a particular time point for the data based a modelling assumption that the distribution of data values follows a normal distribution.
  • a boundary for the medium and higher band may be set by one or more parameters.
  • one parameter is used and is set to approximately 0.5 (in one embodiment it is set at 0.49) of a standard deviation above the mean.
  • a boundary for the medium and lower band is set at approximately 0.5 of a standard deviation below the mean.
  • approximately one third of the consumption values at a point in time over the historical period are located in the higher band (i.e. at or above the boundary between the middle and higher band; approximately one third of the consumption values at that time are located in the middle band; and approximately one third of the consumption values are located in the lower band.
  • Other values for portions of a standard deviation can be used. Different values can be used for the upper and lower boundaries.
  • gauge 810 may reflect those bands by showing its segments as evenly spaced segments and having the current datapoint centered in the middle of the middle segment.
  • the boundaries between the segments are based on the portions of the standard deviation (0.49 as noted in this example).
  • the boundaries of the segments in gauge 810 may map to the boundaries of the bands in graph 800a at the relevant point in time.
  • the boundaries of the segments in gauge 810 have different boundaries - for example boundaries of the segments may follow layouts described for gauges 500 and 600.
  • visual presentation of the scale of each of the bands can be varied.
  • the lower and / or middle sections may have a concentrated number of values therein, thereby leading to a skewing of the weighting of the distributions.
  • the bands were displayed in a linear manner, the lower and / or middle bands would occupy a very small portion of graph 800a.
  • the y-axis may be adjusted to widen the scale where there is a higher concentration of values and / or shrink the scale where there is a lower concentration. This adjustment of boundaries can be applied to any graphical representation of data described herein (for example to graphs 800b and 800c).
  • FIG. 9 shows flow chart 900 outlining an exemplary data mapping process in processing historic data by an embodiment. It may be executed or controlled in whole or in part by server 104. Therein, data analysis module 212B (Fig. 2) may provide programming code for execution on processor 202 (Fig. 2) to effect execution of the process. The process may also operate in whole or in part on device 106.
  • an embodiment processes historic consumption data to generate a usage graph, such as graph 800a.
  • the data can be any type of data described herein. After start process 902, such data is received in process 904.
  • Process 908 calculates are made using the identified boundaries and graphical representations of graph 800a are generated and displayed in the GUI. Once the graph is generated, it can be updated. Process 908 may also generate gauge 810 in association with the time marked by a cursor on graph 800a, per Fig 8a. Flow chart 900 ends at process 910.
  • graph 800a provides a historical view of consumption data.
  • cursors can be generated and moved on graph 800a in the GUI to provide specific snapshots of the consumption data.
  • line 808 is provided as a marker for an instant of time in graph 800a. The placement of line 808 can be moved by a viewer along x-axis 804. For the present example, line 808 shows the consumption data for 6 p.m. on the given day.
  • Gauge 810 shows consumption data at 6 p.m. in the previously described format. As line 808 is moved to different times, the values shown in gauge 810 are reflected to represent the consumption value for the noted times.
  • graph 800a and gauge 810 are generated on one screen (window, pane, etc.) in a GUI on a display of a computer.
  • graph 800a and gauge 810 are shown to be linked (e.g. through a "pop-up" window for gauge 8 0.
  • FIGs. 8b and 8c further details are provided on another aspects of an embodiment. As shown in Figs. 8b and 8c, graphs 800b and 800c produce a historic chart of consumption at a site over a period of time. An embodiment also provides data interpolation and data extrapolation features. Each is discussed in turn.
  • an embodiment provides data interpolation features for the dataset.
  • the consumption line is shown in three parts, 806a, 806b and 806c, where line 806a and 806c represent data from a dataset and line 800b represents interpolated data from the dataset.
  • Data may need to be interpolated if data is not available for gaps in time.
  • graph 800b may show real time consumption data for a site for a given day. As long as the meters and communication links are functioning, an embodiment can provide real time mapping of consumption to graph 800b.
  • an embodiment does not have accurate data to map to graph 800b in that time.
  • an embodiment interpolates data within the gap period.
  • the interpolated data may use historical data averages at the same or comparable time(s) from the and / or from peers.
  • the interpolated data may be shown in a different visual scheme from actual data. In graph 800b, line 806b is shown as a dotted line.
  • Fig. 10 shows flow chart 1000 outlining an exemplary data interpolation applied to historic data by an embodiment. It may be executed or controlled in whole or in part by server 04. Therein, data analysis module 212B (Fig. 2) may provide programming code for execution on processor 202 (Fig. 2) to effect execution of the process. The process may also operate in whole or in part on device 106. [00136] As noted above, an embodiment processes historic consumption data to generate a usage graph, such as graph 800b. The data can be any type of data described herein. After start process 1002, a gap in the data is identified in process 1004.
  • the interpolated datapoints may be generated by accessing historical data for the site or its peer(s) around the time(s) of the gap and averaging functions can be used to generate interpolated values. Functions can take into account the time of day, the season, weather conditions and other factors. Straight line interpolations may also be used.
  • Process 1008 calculates are made using the actual and interpolated data and graphical representations of graph 800b are generated and displayed.
  • Process 1008 may also generate gauge 810 in association with graph 800b. Once the graph is generated, it can be updated.
  • Flow chart 1000 ends at process 1010.
  • an embodiment provides data extrapolation features for the dataset.
  • the time indicated by line 808 may be at the end of the dataset for the site.
  • an embodiment extrapolates a range possible use values.
  • the extrapolated data can use historical data averages at the same or comparable time(s) from the and / or from peers.
  • the amount of time forward from time at line 808 likely increases the variations of possible extrapolated datapoints.
  • graph 800c shows region 806d that reflects the extrapolated datapoints following line 808.
  • Region 806d is bounded by an upper limit line and a lower limit line, which delimit a range of extrapolated consumption values from line 808 onward.
  • region 806d An estimated value is also plotted in region 806d.
  • the upper and lower limits can be defined in terms of statistical deviations from the normal of the estimated value, where the deviations may get larger as the estimates move further in time from line 808. Other factors may affect the deviations, including historical data and external events (expected or received). It can be seen that region 806d starts at line 808 with values very near the consumption value at line 808, but then a larger number of possible consumption values generally are provided the further the extrapolated data is extended from that time. The extrapolated data can be shown in a different visual scheme from actual data. In graph 800c, region 806d is shown as a dotted region with dotted boundary lines.
  • FIG. 11 shows flow chart 1 100 outlining an exemplary data extrapolation for historic data by an embodiment. It may be executed or controlled in whole or in part by server 104. Therein, data analysis module 212B (Fig. 2) may provide programming code for execution on processor 202 (Fig. 2) to effect execution of the process. The process may also operate in whole or in part on device 106.
  • an embodiment processes historic consumption data to generate a usage graph, such as graph 800c.
  • the data can be any type of data described herein.
  • extrapolated datapoints following the end of the dataset are determined.
  • the extrapolated datapoints may be generated by accessing historical data for the site or its peer(s) around the end time and averaging and predictive functions may be used to generate extrapolated values. Functions can take into account the time of day, the season, weather conditions and other factors. Straight line extrapolations can also be used.
  • Process 1108 may also generate gauge 810 in association with graph 800c. Once the graph is generated, it can be updated.
  • Flow chart 1100 ends at process 1 110.
  • an embodiment integrates (consumption) data with an application operating on a device, such as device 106 and / or server 104.
  • an embodiment also integrates consumption data with other output(s) of other applications.
  • consumption data is presented on a display of a device (such as device 106 or server 104) that is integrated with screens, GUIs, icon and other interfaces generated by such applications.
  • a device such as device 106 or server 104
  • one embodiment integrates visual representations of consumption data (as noted above) with a calendar application, such as calendar module 212F (Fig. 2) operating on device 106.
  • Calendar module 212F provides exemplary meeting and calendar tracking functions provided by typical calendar applications, such as tracking meetings and appointments and generating various GUIs that show a calendar of appointments (e.g., based on daily, weekly, monthly schedules). As such, calendar module 212F provides tracking and displaying of "events" in a daily schedule for a user, akin to a scheduling log. Module 212F may include functions similar to those provided by existing calendar applications, such as Outlook, Google Calendar and Apple Calendar (all trade- marks). Calendar entries can be provided by a user at the device or be added remotely (e.g. via external messages for meeting requests received by module 212F.
  • flow chart 1200 shows an exemplary data integration process which may be provided as part of an exemplary application operating on device 106 (Fig. 1).
  • calendar module 212F (Fig. 2) may provide programming code for execution on processor 202 (Fig. 2) to effect execution of the process.
  • the process may also operate in whole or in part on server 104 in a corresponding application / module.
  • an exemplary dataset relating to consumption data for a household and scheduling data for calendar module 212F are used.
  • the consumption data may be stored on device 106 or may be accessed by device 106 through server 04.
  • Flow chart 1200 is initiated at start process 1202, which may be initiated by device 106; once initiated, module 212F in whole or in part may operate in its background.
  • module 212F may receive and process calendar entry commands as provided by a user at device 106 operating module 212F or by remote signals provided to module 212F. Such commands may include commands to create, delete and / or modify calendar entries processed by module 212F (e.g. create a new meeting request for Monday June 25 between 12 PM and 2 PM with John Doe, delete meeting request on Wednesday June 27 at 5 PM, modify entry for sample meeting on Thurs. June 28 at 9-12 to invite John to meeting, etc.).
  • consumption data for a site that has been associated with module 212F is updated.
  • Process 1206 can include one or more data retrieval and processing features and functions of process 300 (Fig. 3).
  • a trigger e.g. a request initiated by a user to view a part of a calendar or an internal request by a process in module 212F to view or update a view of a calendar
  • the consumption data and the calendar data are retrieved for integration and generation into a display on a GUI.
  • the consumption data and the calendar data may be stored, tracked and updated on device 106 and / or some or all of the consumption data may be provided to device 106 by server 104 (or another external device). It will be appreciated that any of processes 1204, 1206 and 1208 may be continually operating (e.g.
  • a GUI of a view of a calendar data is generated on a display associated with device 106.
  • the GUI provides a snapshot of typical a "calendar", e.g. in a table where sequential columns representing a set of consecutive days with rows in the table representing sequential times during the day. Meeting and other events tracked by module 212F are provided as visually distinct graphical representations in the table. In addition, graphical representations of consumption data for the displayed period of time are shown in the table.
  • a snapshot gauge (such as gauge 500, Fig. 5) may be generated as a separate, real time graph that is shown with the table.
  • features relating to analyzing consumption data and providing additional graphical representations of the consumption data in GUIs for applications may be provided as a separate module that is designed to work with an existing calendar module that does not provide such features.
  • GUI 1300 is an exemplary graphical output of calendar and consumption data tracked by module 212F.
  • GU1 1300 provides table 1302 representing a series of sequential days (here Sunday June 24 to Sat. June 30). (Sequential) days are listed at the top of table 1302 in day row 1304. (Sequential) times in the days are listed at the left side of table 1302 in time column 1306. Each day in table 1302 is represented by a column of times. When applicable (i.e. where there is a calendar entry for a given date and time), for such calendar entries (as tracked by module 212F), the corresponding intersecting cell in table 1300 of the days and times for the entries are highlighted.
  • GUI 1300 shows graphical representations of calendar entries 1308 as darkened cells in table 1302. Each entry 1308 has text describing its related meeting or event. Other views (such as month and day views) may be generated containing similar information on calendar events and consumption data. Other orientations for the calendar data may be provided (e.g. where the days are represented by rows and the time are represented by columns).
  • GU1 1300 generates as part of table 1302 graphical representations of consumption data tracked and / or provided to device 106.
  • table 1302 in the day columns, for one or more of the time cells, a graphical representation of an amount of a tracked consumed resource (e.g. energy) is provided integrally with table 1302 as a series of bar graphs 1310.
  • a graphical representation of an amount of a tracked consumed resource e.g. energy
  • table 1302 is segmented into a series of sections.
  • a (horizontal) bar graph is provided for a time entry with a graphical bar generated spanning a proportional amount of the series of sections indicating, graphically, an amount of the consumed resource that was consumed at that time period.
  • Each bar graph has a length that is proportional to a related consumption data level in the consumption data.
  • GUI 1300 provides integrated graphical representations of calendar entries with consumption data.
  • GUI 1300 also includes gauge 312 that shows the current consumption data (or a specific time for the consumption data) tracked by device 106 (akin to gauges 500 and 600 in Figs. 5 and 6 and other graphs described herein).
  • Fig. 13 (ii) provides a magnified view of exemplary calendar entries in table 1302, shown as table extract 1302(ii).
  • table extract 1302(ii) Therein for the period between 10 AM and 5 PM on Monday 6/25, calendar entries and consumption data as tracked are generated.
  • a lunch meeting with John scheduled between 12 PM and 2 PM is shown as an entry 1308.
  • the related consumption data as tracked is shown as a series of bars 1310, with each bar for each hour showing the consumed amount for that hour. Bars that are generated in between 12 PM and 2 PM are visible through entry 1308.
  • Extract 1302(ii) shows that its cells are divided into quarters by markers 1318, providing visual indicators to identify ranges of consumption for the consumed resource.
  • markers 1318 may be used to split the range into halves, thirds, quarters (as shown), fifths, etc.
  • the marker may show uneven ranges (per uneven ranges shown in gauge 600 in Fig. 6).
  • bars 1310 are generated with differentiating visual features (e.g. different shading, colours, speckling etc.) to show differentiate when a consumed value is “low”, “average” or “high”. Bars 1310 are shown in light, medium and dark shadings to indicate “low”, “average” and “high” consumption values. It will be appreciated that rankings for these ranges can be set following preset values or ranges as described herein for earlier graphical representations (e.g. gauges 500 and 600 and graphs 800a, 800b and 800c).
  • GUI 1300 has been generated to show graphical representations of cumulative consumption amounts to date.
  • section 1314 shows cumulative amount of consumption at the various cost rates (low, middle and high) consumption rates.
  • Icons 1316 provide additional "radio buttons" for activating different views for table 1300 (e.g. day, month, week, etc.). It will be appreciated that depending on the level of detail of the view (e.g. by day, by week, by month, etc.) the level of detail for the consumption data and the related calendar entries will vary accordingly. For example, for a month view, each day entry may show average consumption levels for either the day for the calendar or morning and afternoon consumption levels with any calendar entries.
  • the day's entry may show additional consumption information (per graphs 800a, 800b or 800c) as space permits with the calendar entries for that day.
  • An additional radio button can be linked to execute a function associated with the consumption data, for example, generating additional graphs (e.g. gauges 500 or 600 or graphs 800a, 800b or 800c described earlier).
  • an embodiment provides additional integration features among consumption data, tracked events and contacts.
  • One additional feature of an embodiment provides target and limit tracking and reporting for consumption data.
  • a target or limit can be placed on a specific period of time. For example, when module 212F processes the consumption data (per processes 1206 and 1208, Fig. 12), if the detected consumed resource exceeds a limit (as an undesired result) or falls below a limit (as a desired result), module 212F may automatically provide an announcement or message that is generated on the display of device 106. Additionally or alternatively, a message may be sent to other devices by module 212F.
  • an embodiment can generate a message as a calendar alert on the display of device 106 when a limit is exceeded or not or when a tracked energy event occurs (e.g. change in electricity rates for an event).
  • GUI 1300 when consumption data is not available, no consumption data may be provided for bars 1310.
  • an embodiment may generate bar graphs that represent a graphical representation of an interpolated consumption value between the first and second times.
  • the interpolation process may use processes defined herein.
  • data may be extrapolated as described herein.
  • Consumption data generated in GUI 1300 may be based on data gathering, analysis and comparison features described herein earlier. It will be seen that GUI 1300 provides an unobtrusive visual interface for providing graphical representations of consumption data in applications that are frequently executing on device 106. As such, there is a convenient and natural interfacing of time based events (as calendar events) with time-based consumption data. The consumption data may be integrated into other applications operating on device 106 that track time or events (e.g. a clock application that displays gauge 500 or 600 in its clock window).
  • flow chart 400 provides analysis of a dataset comprising consumption data from a plurality of data sources. As such, the analysis in flow chart 400 provides information on a how a particular datapoint compares a dataset in a certain population.
  • An embodiment also provides a data scenario tool, which can access model data and generate different scenarios for a given dataset.
  • the scenarios may relate to models for consumption, usage, emission targets and / or other requirements.
  • Rebate information may be incorporated into the scenario data.
  • one consumption program may provide additional rebates on consumption rates when target consumption savings are achieved.
  • “Time of use” information may be incorporated into the scenario data. For example, different cost rates may apply to a consumable (e.g. water, electricity) depending on when it is consumed (e.g. during the working day, during weekends, at night, etc.).
  • Scenarios may be developed and presented that estimate consumption or usage for a consumable based on a dataset. As such the scenarios may represent other datapoints that are not necessarily based on data from peers. This scenario data may be used to augment a visual representation of a dataset generated by data visualization module 212C.
  • flow chart 1400 shows an exemplary data scenario generation process which may be provided by server 104 (Fig. 1).
  • data scenario module 212D (Fig. 2) may provide programming code for execution on processor 202 (Fig. 2) to effect execution of the process.
  • the process may also operate in whole or in part on device 106.
  • an exemplary dataset relating to energy usage of a house within a city block is used.
  • the process is initiated at start process 1402, which may be initiated by device 106 after receiving a request from device 106 through user 108.
  • a dataset is obtained and analyzed.
  • Process 1404 may incorporate one or more functions of processes in flow chart 400 (Fig. 4), including processes 440, 406 and 408.
  • the dataset may be adjusted to filter, sort, localize, level and/ or normalize the dataset to provide a calibrated dataset.
  • Adjustments may be made to reflect its minimum and maximum values and comparable adjustments may be made to its scale (504, Fig. 5) when a visual representation is generated.
  • scenario data is obtained.
  • Scenario data may be stored in database 110.
  • Scenario data may model different hypothetical or actual performance targets or traits for a dataset.
  • a scenario may include target usage data relating to consumption targets, emission targets, cost targets, rebate offers, time of use charges for utilities, tariff charges on excess usage and other goals and / or targets.
  • Scenario data may relate to a particular data source (e.g. a given building) and may reflect changes implemented at the source (e.g. installing high-efficiency lighting, replacement of water heater, additional of new wing, etc.).
  • Scenario data may provide data reflecting effects of such change(s).
  • the data may show differences (e.g. in saved consumption/emissions/costs and / or additional
  • Changes may be show over different time periods (e.g. short term and long term), with a projected "payback" time incorporated.
  • the results may be displayed in a "raw" form, where basic difference information is displayed. For example, if the difference is determined to be a savings of 100 litres of gasoline, the result may simply state "100 litres of gasoline are saved" or a comparable message.
  • an embodiment also provides a facility to provide an analogous report to the raw data where the raw data is converted to a second set of units and that may be further converted to a suitable paradigm using the second units. For example, if the raw data indicates a certain amount of gasoline that is used, an analogous report may convert the gasoline units to units related to carbon emissions. The conversion is based on how many units of gasoline produce a unit of carbon emission. Then the savings may be expressed in terms of carbon savings.
  • the amount of carbon savings can be further converted to other paradigms associated with carbon usage.
  • the total amount of carbon emissions saved can then be converted to units such as an equivalent number of cars that would be removed from the streets that would have produced the calculated carbon emissions saved.
  • other conversions can be provided.
  • the following units can be converted among each other, provided that a suitable conversion rate is provided: energy consumed/saved, electricity consumed/saved, carbon generated/saved, costs, payback time, heat generated/saved, water consumed/saved and others. Conversions can be provided through one or more conversion steps among units.
  • the scenario data is integrated with the dataset.
  • the scenario data may define one or more boundaries (510, Fig. 5) for the dataset, based any goals or limits defined for the selected scenario.
  • a scenario dataset can be analyzed and segmented in a similar fashion to a population consumption dataset, described earlier. As such, a visual representation of a scenario dataset may also be generated.
  • a visual representation of the scenario data is produced.
  • Process 810 may incorporate one or more functions of processes in flow chart 400 (Fig. 4), including process 410 to generate a graphical representation, such as any representation shown in Figs. 5-7, 8a-8c and 13.
  • an embodiment may display results in other graphical representations.
  • a series of line graphs can be provided with multiple graphs generated thereon.
  • the x-axis can represent time units (e.g. days) and the y-axis can represent a consumable (e.g. energy used/saved).
  • one graph can be provided to plot current energy usage for a subject entity (e.g. a building) as calculated.
  • a second graph can be provided to plot current energy usage for a group of entities relating to the subject entity (e.g. buildings in a block).
  • a third graph can be provided to plot the current energy usage for another group of entities (e.g. best buildings in the dataset). Other plots can be provided.
  • the embodiment also provides direct control of function(s) of an entity being evaluated.
  • function(s) of an entity being evaluated For example for energy usage for a building, the embodiment can provide for direct and / or scheduled control of one or more operational components in the building (e.g. lights, heat, HVAC, etc.).
  • an embodiments when a target indicator is provided, an embodiments also provides an ability to change the setting of the target indicator (e.g. indicator 512B, Fig. 5), by dragging and changing the indicator directly through the GUI. As the indicator changes, this may have an effect on the current operating characteristics of the target indicator (e.g. indicator 512B, Fig. 5), by dragging and changing the indicator directly through the GUI. As the indicator changes, this may have an effect on the current operating characteristics of the target indicator.
  • An embodiment may provide a direct feedback control to change operating characteristics of one or more components relating to the data being plotted.
  • changing the target indicator may cause a change in one or more operational components in the building (e.g. lights, heat, HVAC, etc.).
  • a particular datapoint for a consumed resource at a particular location may be mapped onto the representation.
  • the particular datapoint may be shown as an indicator such as indicator 512A (Fig. 5).
  • an indicator may be provided representing the current energy usage of the house.
  • one or more (consumption) goals may be provided. Each goal may be based on a different combination of savings parameters (e.g. time of use saving, amount of use reductions, rebate targets, etc.) and / or on different savings progressions (e.g. mild savings, moderate savings, aggressive savings).
  • data scenario module 212D may determine a progression to move the tracked usage from its current level to the target level. For example a reduction of usage may be calculated to have a daily incremental reduction of usage over a period of time to reduce the current usage level to the target level. Such a progression rate may be identified to change a usage pattern of a device (e.g. a water heater) associated with the first datapoint to the goal.
  • a device e.g. a water heater
  • a visual representation of a population's consumption data may be generated (as noted above) and scenario data may then be accessed.
  • a particular datapoint relating to a specific location's consumption data may be provided in the visual representation (e.g. as indicator 512A).
  • Scenario data (as described above) may be analyzed to identify a goal for that a particular datapoint and the goal may be provided in the visual representation (e.g. as indicator 512B). For example, using consumption data from Table A, exemplary goal data in Table B may be provided for analysis.
  • Goal data may be absolute (providing set values as noted in Table B) and / or may be expressed as a percentage (e.g. a percentage reduction from the current usage rate).
  • An embodiment also provides control features to implement a plan to move the current consumption level towards the identified goal. Part of the control features utilize identified consumption value of a consumable for a given location.
  • an embodiment can have direct control over one or more systems (e.g. lighting, heating, water circulation, HVAC, etc.) and can implement signals that are generated and transmitted from server 104 to start, stop and / or reduce the usage.
  • Control module 212E (Fig. 2) may provide programming code for execution on processor 202 (Fig. 2) to effect execution of the process.
  • the control module may generate control signals to control operation parameters of a device (e.g. to the above noted water heater to control when it is operated and at what temperatures the heater is set to) to implement the progression rate.
  • the controls can be provided to control like groups of items.
  • controls can be provided to manage different types of utilities in a location (e.g. heat, water, HVAC, etc.) or all the same utilities in a location (e.g. all water usage in a city block).
  • Part of the control features may provide a trigger to recalculate a visual representation of consumption data as the controls are implemented (per process 402, Fig. 4).
  • a matrix of control signals can be provided to control multiple devices.
  • An embodiment can provide a separate plan for each device, but an overall plan can be provided that has coordinated controls over parameters for multiple devices.
  • server 104 and device 106 can be implemented using known programming techniques, languages and algorithms.
  • modules described are implemented in server 104, it will be appreciated that some functions of the modules may be provided in a separate server that is in communication with server 104 and/or device 106, or even provided in device 106 itself.
  • the titles of the modules are provided as a convenience to provide labels and assign functions to certain modules. It is not required that each module perform only its functions as described above. As such, specific functionalities for each application may be moved between modules or separated into different modules. Modules may be contained within other modules. Different signalling techniques may be used to communicate information between applications using known programming techniques. Known data storage, access and update algorithms allow data to be shared between applications. It will further be appreciated that other applications and systems on server 104 or device 106 may be executing concurrently using programming techniques known in the art.
  • embodiments relating to client devices, server devices and systems may be implemented tangible and intangible forms.
  • embodiments may be provided in a tangible form in a combination of electronic hardware, firmware and software and other tangible forms.
  • the firmware and software may be implemented as a series of processes, applications and/or modules that provide the functionalities described herein.
  • the algorithms and processes described herein may be executed in different order(s). Interrupt routines may be used.
  • Data may be stored in volatile and non-volatile devices described herein and may be updated by the hardware, firmware and/or software.
  • a threshold or measured value is provided as an approximate value (for example, when the threshold is qualified with the word "about")
  • a range of values will be understood to be valid for that value.
  • a threshold stated as an approximate value a range of about 25% larger and 25% smaller than the stated value may be used.
  • Thresholds, values, measurements and dimensions of features are illustrative of embodiments and are not limiting unless noted.
  • a "sufficient" match with a given threshold may be a value that is within the provided threshold, having regard to the approximate value applicable to the threshold and the understood range of values (over and under) that may be applied for that threshold.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un système, un procédé et un dispositif servant à intégrer, à des données de consommation, une application fonctionnant sur un dispositif. Le procédé consiste à : accéder à des données calendaires stockées en mémoire et relatives à des entrées de calendrier ; accéder à des données de consommation stockées en mémoire ; et générer une interface IUG (interface utilisateur graphique) sur un dispositif d'affichage pour le dispositif. L'interface IUG comprend : une table contenant au moins une entrée pour le jour et au moins une entrée pour l'heure pour la ou les entrées pour le jour ; une première représentation graphique dans la table représentant une entrée de calendrier dans les données calendaires pour la ou les entrées pour le jour, si applicable ; et une seconde représentation graphique dans la table représentant un niveau de données de consommation dans les données de consommation pour la ou les entrées pour le jour.
PCT/CA2012/000853 2011-09-15 2012-09-14 Système et procédé de génération, de traitement et d'affichage de données relatives à des données de consommation, avec une application WO2013037051A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/907,021 US9390391B2 (en) 2011-09-15 2013-05-31 System and method for benchmarking environmental data
CA2825809A CA2825809A1 (fr) 2012-08-31 2013-08-29 Systeme et methode d'analyse comparative de donnees environnementales

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CA2,752,364 2011-09-15
CA2752364A CA2752364A1 (fr) 2011-09-15 2011-09-15 Systeme et methode de traitement et d'affichage de donnees liees aux donnees de consommation
PCT/CA2012/000800 WO2013037038A1 (fr) 2011-09-15 2012-08-31 Système et procédé permettant de générer, de traiter et d'afficher des données relatives à des données de consommation
CAPCT/CA2012/000800 2012-08-31

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA2012/000800 Continuation-In-Part WO2013037038A1 (fr) 2011-09-15 2012-08-31 Système et procédé permettant de générer, de traiter et d'afficher des données relatives à des données de consommation

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/907,021 Continuation-In-Part US9390391B2 (en) 2011-09-15 2013-05-31 System and method for benchmarking environmental data

Publications (2)

Publication Number Publication Date
WO2013037051A1 WO2013037051A1 (fr) 2013-03-21
WO2013037051A9 true WO2013037051A9 (fr) 2013-05-10

Family

ID=47882061

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CA2012/000800 WO2013037038A1 (fr) 2011-09-15 2012-08-31 Système et procédé permettant de générer, de traiter et d'afficher des données relatives à des données de consommation
PCT/CA2012/000853 WO2013037051A1 (fr) 2011-09-15 2012-09-14 Système et procédé de génération, de traitement et d'affichage de données relatives à des données de consommation, avec une application

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CA2012/000800 WO2013037038A1 (fr) 2011-09-15 2012-08-31 Système et procédé permettant de générer, de traiter et d'afficher des données relatives à des données de consommation

Country Status (2)

Country Link
CA (3) CA2752364A1 (fr)
WO (2) WO2013037038A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9866578B2 (en) * 2014-12-03 2018-01-09 AlphaSix Corp. System and method for network intrusion detection anomaly risk scoring

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003084022A1 (fr) * 2002-03-28 2003-10-09 Robertshaw Controls Company Systeme et procede de gestion d'energie
JP4185876B2 (ja) * 2004-03-25 2008-11-26 キヤノン株式会社 情報処理装置
US7274975B2 (en) * 2005-06-06 2007-09-25 Gridpoint, Inc. Optimized energy management system
BRPI0705569A2 (pt) * 2007-09-11 2009-05-05 Univ Minas Gerais método para medição e monitoramento
US20100064001A1 (en) * 2007-10-10 2010-03-11 Power Takeoff, L.P. Distributed Processing
WO2009104166A1 (fr) * 2008-02-20 2009-08-27 Frans Gustav Theodor Radloff Gestion de consommation d'énergie
US20100235144A1 (en) * 2008-04-24 2010-09-16 David Mosberger-Tang Method and system for automated monitoring of the production and/or consumption of meterable substances or thermodynamically quantifiable entities, including power and energy
BRPI0912476A2 (pt) * 2008-05-12 2019-09-24 Energy And Power Solutions Inc sistema e métodos de determinação, monitoração e otimização do consumo de energia, de emissões de consumo ou descarte de energia e das emissões de carbono e de preparação de dados para análise e de alerta de usuário de sistema de coleta de dados de instalações industriais
US20100328314A1 (en) * 2009-06-26 2010-12-30 Donald B. Ellingham Methods, apparatus and system for energy conservation
US8509954B2 (en) * 2009-08-21 2013-08-13 Allure Energy, Inc. Energy management system and method
WO2011014828A2 (fr) * 2009-07-30 2011-02-03 Google Inc. Surveillance de ressource sur un dispositif mobile
JP5552817B2 (ja) * 2010-01-25 2014-07-16 ソニー株式会社 電力管理システム、電力管理装置、電力管理方法、蓄電装置、及び電動移動体
US9460444B2 (en) * 2010-09-03 2016-10-04 Hewlett Packard Enterprise Development Lp Visual representation of a cell-based calendar transparently overlaid with event visual indicators for mining data records

Also Published As

Publication number Publication date
CA2752364A1 (fr) 2013-03-15
CA2788302A1 (fr) 2013-03-15
CA2789863A1 (fr) 2013-03-15
WO2013037038A1 (fr) 2013-03-21
WO2013037051A1 (fr) 2013-03-21

Similar Documents

Publication Publication Date Title
US20130069951A1 (en) System and method for generating, processing and displaying data relating to consumption data with an application
US20130069949A1 (en) System and method for generating, processing and displaying data relating to consumption data
US7392115B2 (en) Characterization of utility demand using utility demand footprint
US7647137B2 (en) Utility demand forecasting using utility demand matrix
US20190087389A1 (en) Systems and methods for configuring display layout
CN110704565B (zh) 一种基于遥感与gis的人口统计数据网格化建模方法
US20130055132A1 (en) Energy dashboard
US20190086452A1 (en) Systems and methods for managing resource consumption
US10339682B2 (en) Method and apparatus for energy data visualization
US8947433B2 (en) Spatiotemporal visualization of sensor data
EP3210032A1 (fr) Mappage de topologie de réseau électrique à l'aide de données de tension
US20190086878A1 (en) Systems and methods for determining baseline consumption
Haberl et al. Exploring new techniques for displaying complex building energy consumption data
CN108885730A (zh) 基于gis的集中式碳足迹监测系统及其方法
Clites et al. Visualizing relationships between hydrology, climate, and water level fluctuations on Earth's largest system of lakes
Hossain et al. Forecasting Energy Consumption Trends with Machine Learning Models for Improved Accuracy and Resource Management in the USA
WO2013037051A9 (fr) Système et procédé de génération, de traitement et d'affichage de données relatives à des données de consommation, avec une application
JP7612482B2 (ja) エネルギー管理システム
Fireteanu Integrating Tableau with internet of things acquiring projects
Zipper et al. Estimating irrigation water use from remotely sensed evapotranspiration data: Accuracy and uncertainties across spatial scales
JP2015225637A (ja) 相関分析装置、相関分析方法、および相関分析用プログラム
Veronesi et al. Generation and validation of spatial distribution of hourly wind speed time-series using machine learning
Li et al. A Large-Scale Residential Load Dataset in a Southern Province of China
WO2019055050A1 (fr) Systèmes et procédés d'affichage d'économies de ressources
WO2019055054A1 (fr) Systèmes et procédés de gestion de consommation de ressources

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12831409

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12831409

Country of ref document: EP

Kind code of ref document: A1