U.S. patent application number 12/766027 was filed with the patent office on 2011-03-10 for system and method for managing sustainability for an organization.
This patent application is currently assigned to Computer Associates Think, Inc.. Invention is credited to Terrence G. Clark, Peter J. Gilbert, Janne M.P. Koponen, James B. Mercer.
Application Number | 20110060617 12/766027 |
Document ID | / |
Family ID | 43648412 |
Filed Date | 2011-03-10 |
United States Patent
Application |
20110060617 |
Kind Code |
A1 |
Clark; Terrence G. ; et
al. |
March 10, 2011 |
System and Method for Managing Sustainability for an
Organization
Abstract
A computer-implemented method for managing sustainability for an
organization is disclosed. The method may include storing on one or
more memory modules of a computer system a plurality of instances
of an ecoActivity object. Each instance of the ecoActivity object
may represent an activity of the organization affecting
environmental sustainability. The method may further include
storing a plurality of instances of an emission factor object. Each
instance of the emission factor object may at least partially
quantify one or more green house gas emissions as a function of one
or more respective metrics. The method may include establishing a
computer-based logical link between each one of the plurality of
instances of the ecoActivity object and at least one of the
instances of the emission factor object. In certain embodiments,
the method may include receiving data representing the metric(s)
for the logically linked instance(s) of the emission factor object.
For each one of the plurality of instances of the ecoActivity
object, the method may include calculating one or more green house
gas emission quantities based at least in part by applying, for the
logically linked at least one of the plurality of instances of the
emission factor object, the function of the metric(s) to the
received metric(s). Additionally, the method may include
aggregating together at least some of the green house gas emission
quantities. In various embodiments, the method may include
transferring data representing the aggregation of the calculated
green house gas emission quantities.
Inventors: |
Clark; Terrence G.;
(Smithtown, NY) ; Gilbert; Peter J.; (New York,
NY) ; Mercer; James B.; (Millville, MA) ;
Koponen; Janne M.P.; (Buckinghamshire, GB) |
Assignee: |
Computer Associates Think,
Inc.
Islandia
NY
|
Family ID: |
43648412 |
Appl. No.: |
12/766027 |
Filed: |
April 23, 2010 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61240968 |
Sep 9, 2009 |
|
|
|
Current U.S.
Class: |
705/7.37 ;
705/348 |
Current CPC
Class: |
G06Q 10/06 20130101;
G06Q 10/063 20130101; G06Q 10/103 20130101; G06Q 10/067 20130101;
Y02P 90/84 20151101; G06Q 10/0639 20130101 |
Class at
Publication: |
705/7 ;
705/348 |
International
Class: |
G06Q 10/00 20060101
G06Q010/00; G06Q 50/00 20060101 G06Q050/00 |
Claims
1. A computer-implemented method for managing sustainability for an
organization, the method comprising: storing on one or more memory
modules of a computer system a plurality of instances of an
ecoActivity object, each of the plurality of instances of the
ecoActivity object representing an activity of the organization
affecting environmental sustainability; storing on the one or more
memory modules of the computer system a plurality of instances of
an emission factor object, each of the plurality of instances of
the emission factor object at least partially quantifying one or
more green house gas emissions as a function of one or more
respective metrics; establishing a computer-based logical link
between each one of the plurality of instances of the ecoActivity
object and at least one of the plurality of instances of the
emission factor object; receiving data representing the one or more
respective metrics for the logically linked at least one of the
plurality of instances of the emission factor object; for each one
of the plurality of instances of the ecoActivity object,
calculating using a computer unit one or more green house gas
emission quantities based at least in part by applying, for the
logically linked at least one of the plurality of instances of the
emission factor object, the function of the one or more respective
metrics to the received one or more respective metrics; aggregating
together the one or more green house gas emission quantities
calculated for at least two of the plurality of instances of the
ecoActivity object; and transferring data representing the
aggregation of the one or more green house gas emission quantities
calculated for the at least two of the plurality of instances of
the ecoActivity object.
2. The method of claim 1, wherein transferring the data comprises
transferring the data in a computer-displayable format.
3. The method of claim 1, wherein transferring the data comprises
transferring the data in a tangible format.
4. The method of claim 1, wherein the respective activity of at
least one of the plurality of instances of the ecoActivity object
is selected from the group consisting of: waste production;
shipping; one or more manufacturing processes; business air travel;
water usage; burning of natural resources; electricity usage;
electricity production; and fugitive emissions.
5. The method of claim 1, wherein the data is aggregated using
geographic data logically linked to each of the at least two of the
plurality of instances of the ecoActivity object.
6. The method of claim 1, wherein the data is aggregated using
categorical data logically linked to each of the at least two of
the plurality of instances of the ecoActivity object.
7. The method of claim 1, further comprising disaggregating the one
or more green house gas emission quantities calculated for at least
one the plurality of instances of the ecoActivity object.
8. The method of claim 7, wherein the disaggregation is based at
least in part on geographic data logically linked to the one or
more respective metrics of the respective one or more of the
plurality of instances of the emission factor object logically
linked to the at least one of the plurality of instances of the
ecoActivity object.
9. A non-transitory computer-readable medium comprising software
operable, when executed by at least one processor, to: store on one
or more memory modules of a computer system a plurality of
instances of an ecoActivity object, each of the plurality of
instances of the ecoActivity object representing an activity of the
organization affecting environmental sustainability; store on the
one or more memory modules of the computer system a plurality of
instances of an emission factor object, each of the plurality of
instances of the emission factor object at least partially
quantifying one or more green house gas emissions as a function of
one or more respective metrics; establish a computer-based logical
link between each one of the plurality of instances of the
ecoActivity object and at least one of the plurality of instances
of the emission factor object; receive data representing the one or
more respective metrics for the logically linked at least one of
the plurality of instances of the emission factor object; for each
one of the plurality of instances of the ecoActivity object,
calculate using a computer unit one or more green house gas
emission quantities based at least in part by applying, for the
logically linked at least one of the plurality of instances of the
emission factor object, the function of the one or more respective
metrics to the received one or more respective metrics; aggregate
together the one or more green house gas emission quantities
calculated for at least two of the plurality of instances of the
ecoActivity object; and transfer data representing the aggregation
of the one or more green house gas emission quantities calculated
for the at least two of the plurality of instances of the
ecoActivity object.
10. The computer-readable medium of claim 9, wherein the data is
transferred in a computer-displayable format.
11. The computer-readable medium of claim 9, wherein the data is
transferred in a tangible format.
12. The computer-readable medium of claim 9, wherein the respective
activity of at least one of the plurality of instances of the
ecoActivity object is selected from the group consisting of: waste
production; shipping; one or more manufacturing processes; business
air travel; water usage; burning of natural resources; electricity
usage; electricity production; and fugitive emissions.
13. The computer-readable medium of claim 9, wherein the data is
aggregated using geographic data logically linked to each of the at
least two of the plurality of instances of the ecoActivity
object.
14. The computer-readable medium of claim 9, wherein the data is
aggregated using categorical data logically linked to each of the
at least two of the plurality of instances of the ecoActivity
object.
15. The computer-readable medium of claim 9, wherein the software
is further operable, when executed by the at least one processor,
to disaggregate the one or more green house gas emission quantities
calculated for at least one the plurality of instances of the
ecoActivity object.
16. The computer-readable medium of claim 15, wherein the
disaggregation is based at least in part on geographic data
logically linked to the one or more respective metrics of the
respective one or more of the plurality of instances of the
emission factor object logically linked to the at least one of the
plurality of instances of the ecoActivity object.
17. A data processing system for managing sustainability for an
organization, the data processing system comprising: at least one
processor; and one or more memory modules collectively storing: a
plurality of instances of an ecoActivity object, each instance of
the ecoActivity object representing a respective activity of the
organization affecting environmental sustainability; a plurality of
instances of an emission factor object, each instance of the
emission factor object at least partially quantifying one or more
green house gas emissions as a function of one or more respective
metrics; one or more logical links associating each one of the
plurality of instances of the ecoActivity object with a respective
one or more of the plurality of instances of the emission factor
object; and logic operable, when executed by the at least one
processor, to: receive data representing the one or more respective
metrics for the logically linked at least one of the plurality of
instances of the emission factor object; for each one of the
plurality of instances of the ecoActivity object, calculate using a
computer unit one or more green house gas emission quantities based
at least in part by applying, for the logically linked at least one
of the plurality of instances of the emission factor object, the
function of the one or more respective metrics to the received one
or more respective metrics; aggregate together the one or more
green house gas emission quantities calculated for at least two of
the plurality of instances of the ecoActivity object; and transfer
data representing the aggregation of the one or more green house
gas emission quantities calculated for the at least two of the
plurality of instances of the ecoActivity object.
18. The data processing system of claim 17, wherein the data is
transferred in a format selected from a computer-displayable format
and a tangible format.
19. The data processing system of claim 17, wherein the respective
activity of at least one of the plurality of instances of the
ecoActivity object is selected from the group consisting of: waste
production; shipping; one or more manufacturing processes; business
air travel; water usage; burning of natural resources; electricity
usage; electricity production; and fugitive emissions.
20. The data processing system of claim 17, wherein the data is
aggregated using data logically linked to each of the at least two
of the plurality of instances of the ecoActivity object, the
logically linked data selected from the group consisting of
geographic data and categorical data.
Description
RELATED APPLICATION
[0001] This application claims the benefit under 35 U.S.C.
.sctn.119(e) of U.S. Provisional Application Ser. No. 61/240,968
filed Sep. 9, 2009.
TECHNICAL FIELD
[0002] This invention relates generally to computer management, and
more particularly to a system and method for managing
sustainability for an organization.
BACKGROUND
[0003] Many business organizations are being pressured to report on
their carbon footprint and to achieve environmental sustainability
goals. The task of accurately reporting the collective resources
consumed and expended by an organization, however, has considerable
complexity for some organizations. For example, some organizations
may engage in various different types of activities affecting the
environment. Additionally, some organizations may have multiple
facilities remotely located from each other. Various attempts at
tracking sustainability information from diverse sources is often
time-consuming and error-prone to the point that efficiently
measuring and managing progress toward sustainability goals has
traditionally been difficult if not untenable. Another challenge to
managing sustainability for an organization is that some
organizations may have multiple stakeholders with divergent
objectives.
OVERVIEW
[0004] According to one embodiment, a computer-implemented method
for managing sustainability for an organization is disclosed. The
method may include storing on one or more memory modules of a
computer system a plurality of instances of an ecoActivity object.
Each of the plurality of instances of the ecoActivity object may
represent an activity of the organization affecting environmental
sustainability. The method may further include storing on the one
or more memory modules of the computer system a plurality of
instances of an emission factor object. Each of the plurality of
instances of the emission factor object may at least partially
quantify one or more green house gas emissions as a function of one
or more respective metrics. The method may include establishing a
computer-based logical link between each one of the plurality of
instances of the ecoActivity object and at least one of the
plurality of instances of the emission factor object. In certain
embodiments, the method may include receiving data representing the
one or more respective metrics for the logically linked at least
one of the plurality of instances of the emission factor object.
For each one of the plurality of instances of the ecoActivity
object, the method may include calculating using a computer unit
one or more green house gas emission quantities based at least in
part by applying, for the logically linked at least one of the
plurality of instances of the emission factor object, the function
of the one or more respective metrics to the received one or more
respective metrics. Additionally, the method may include
aggregating together the one or more green house gas emission
quantities calculated for at least two of the plurality of
instances of the ecoActivity object. In various embodiments, the
method may include transferring data representing the aggregation
of the one or more green house gas emission quantities calculated
for the at least two of the plurality of instances of the
ecoActivity object.
[0005] Certain embodiments may provide one or more technical
advantages. For example, certain embodiments may enable
organizations to track substantially all of their activity that may
affect the environment using a normalized format, referred to
herein as instances of an "ecoActivity" object. In particular
embodiments, most or all enterprise-wide activities can be recorded
in such a normalized format. This normalized structure may allow
recording of various related data that can later be used as
intensity metrics. In particular embodiments, an instance of an
ecoActivity object may inherit user-defined characteristics
depending upon its association with various other parameters. For
example, a user may be able to exploit configured characteristics
based upon a facility, underlying source, emissions factors,
geographic location, activity type, etc. In certain embodiments,
the adaptable nature of the design may enable the user to either
exploit the inherited characteristics or override them at the
instance level. Additionally, particular embodiments may provide
data extrapolation capabilities. Certain embodiments may provide
all, some, or none of these advantages. Certain embodiments may
provide one or more other technical advantages, one or more of
which may be apparent to those skilled in the art from the figures,
descriptions, and claims included herein.
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] For a more complete understanding of the present invention
and advantages thereof, reference is now made to the following
description taken in conjunction with the accompanying drawings, in
which:
[0007] FIGS. 1A through 1B are example block diagrams illustrating
a portion of a system for managing sustainability according to one
embodiment;
[0008] FIG. 2 is an example flowchart illustrating steps that may
be implemented at least in part by the system of FIGS. 1A and 1B;
and
[0009] FIGS. 3 through 10 are example GUI dashboards that may be
generated by the system of FIGS. 1A and 1B according to various
embodiments.
DESCRIPTION OF EXAMPLE EMBODIMENTS
[0010] The present disclosure generally relates to systems and
methods for managing objectives for an organization. In general,
particular embodiments may facilitate defining objectives for an
organization and may further provide automated and customizable
data collection and feedback based on a variety of progress
indicators. In some embodiments, the feedback may be used to inform
a decision-making process and to maintain or advance the defined
objectives. Some embodiments may be implemented as Software as a
Service (SaaS), whereby a provider may license and/or host all or a
part of an application for use as a service on demand. Alternative
embodiments may be hosted and implemented locally (e.g., using a
standalone program installed at a local machine or network).
Particular example embodiments are explained in the context of
objectives related to environmental sustainability, such as, for
example, managing energy usage, energy spend, and/or greenhouse gas
(GHG) emissions for all or a portion of an organization. It should
be understood at the outset, however, that although example
embodiments are explained in the context of objectives in terms of
sustainability, various embodiments may be capable of managing a
variety of alternative objectives. Additionally, the present
disclosure should in no way be limited to the example embodiments,
drawings, and techniques disclosed.
[0011] FIG. 1A is one example of a block diagram illustrating a
portion of a data processing system 100. In particular embodiments,
data processing system 100 is capable of facilitating the
management of sustainability for an organization. In the
illustrated example, system 100 generally includes a plurality of
computing systems 102 coupled together through a network 104. As
used throughout this document, the term "couple" and/or "coupled"
refers to any direct and/or indirect communication between two or
more elements, whether or not those elements are in physical
contact with one another.
[0012] Each computing system 102 may comprise any computing and/or
communication device capable of enabling the communication of
information to and/or from network 104 or another component in
system 100. In some embodiments, a particular computing system 102
may enable the communication of information to and/or receive
information from one or more other computing systems 102 or some
other component of system 100.
[0013] In some cases, each computing system 102 may include any
combination of software, hardware, and/or firmware capable of
receiving input, generating data, processing data, recording data,
executing logic, and/or enabling the communication of information
to and/or from network 104 or another component in system 100. For
example, particular computing systems 102 may include one or more
wireless devices, voice over Internet protocol (IP) devices,
desktop computers, laptop computers, personal digital assistants,
cell-phones, telephones, Wi-Fi devices, workstations, mainframe
computers, mini-frame computers, servers (including web servers),
routers, data bases, directories, any combination of the preceding,
or any other computing and/or communicating devices.
[0014] In particular embodiments, computing systems 102 may include
one or more data repositories capable of recording data. The data
may be received from any suitable data source. For example, in
certain embodiments the data may be collected using manual input
and/or the data may be provided by one or more meters or sensors.
Each meter and/or sensor may be capable of measuring one or more of
the following: energy; resource use and/or consumption; physical or
environmental characteristics of components, processes and/or
facilities associated with system 100; and/or some other
measureable factor related to organizational objectives. For
example, meters or sensors may be capable of measuring
kilowatt-hours of electricity consumed or produced by a facility,
carbon dioxide emissions produced by a facility, etc.
[0015] In various embodiments, system 100 may include one or more
meters or sensors. For example, particular meters or sensors may be
capable of generating an output based on physical measurements and
communicating the output to network 104 or another component in
system 100. In an alternative embodiment, system 100 may use data
provided by meters and/or sensors that are external to system 100.
For example, the output of one or more meters and/or sensors
external to system 100 may be derived from a statement that
accounts for activity of electricity, gas, water, waste, emitted
gases, etc.
[0016] In these examples, one or more computing systems 102
communicate with one or more other computing systems 102 through
network 104. Network 104 may comprise any wireless network,
wireline network, or combination of wireless and wireline networks
capable of supporting communication between network elements using
ground-based and/or space-based components. In various embodiments,
network 104 may be capable of transmitting audio, video, signals,
data, messages, or any combination of these or other communication
signals. For example, network 104 may comprise a data network, a
public switched telephone network (PSTN), an integrated services
digital network (ISDN), a local area network (LAN), a wide area
network (WAN), a metropolitan area network (MAN), all or a portion
of the global computer network known as the Internet, and/or other
communication systems or combination of communication systems at
one or more locations. Although FIG. 1 illustrates computing
systems 102 coupled to each other through network 104, the
communication between some computing systems 102 may be performed
internally, such as, for example, via a system bus.
[0017] FIG. 1B is one example embodiment of a block diagram
illustrating a portion of at least one of the computing systems 102
of FIG. 1A. In this example, computing system 102 includes at least
one memory module 106, processor 108, data storage device 110,
input/output functionality 112, and interface 114. Although this
embodiment includes memory module 106, processor 108, data storage
device 110, input/output functionality 112, and interface 114,
other embodiments may exclude one or more of memory module 106,
processor 108, data storage device 110, input/output functionality
112, and interface 114 without departing from the scope of the
present disclosure.
[0018] In this embodiment, computing system 102 may include a
manager application 150 residing in memory module 106. Manager
application 150 may comprise, for example, software, firmware,
code, portions of code, data compilations, content, and/or a
combination of these or any other type of data. As explained
further below, manager application 150 may include a variety of
software objects and a module for generating graphical user
interface (GUI) dashboards 152. Although manager application 150
resides within memory module 106 in this example, all or a portion
of manager application 150 may alternatively reside at any other
suitable location, such as, for example, external to memory module
106 and/or external to computing system 102. In some embodiments,
manager application 150 may be embodied or recorded on any of a
variety of other suitable tangible, non-transitory
computer-readable medium, such as, for example, removable
computer-readable media. In particular embodiments, manager
application 150 may be hosted at one or more computing systems 102
under a SaaS model of software deployment. The computing systems
102 hosting manager application 150 may, for example, be configured
to receive data communicated via network 104 from other computing
systems 102. Alternative embodiments may be hosted and implemented
locally (e.g., using a standalone program installed at a local
machine or network).
[0019] In various embodiments, manager application 150 may be
structurally and/or functionally interrelated to particular
tangible, non-transitory computer-readable media in the form of
memory module 106 or other tangible, non-transitory
computer-readable media, which computer-readable media may at least
partially enable the functions of manager application 150 to be
realized. Additionally, manager application 150 may be structurally
and/or functionally interrelated to one or more processors 108.
Processor 108 may refer, for example, to the portion of computing
system 102 capable of carrying out instructions of a computer
program. In certain embodiments, processor 108 may comprise the
primary element or elements executing or realizing various
logic-based functions, including, for example, the functions of
manager application 150.
[0020] In operation of particular embodiments, the execution of
manager application 150 by one or more processors 108 may
facilitate defining objectives of for organization in terms of
environmental sustainability. Additionally, manager application 150
may be capable of providing customizable data collection and
feedback based on a variety of progress indicators. The feedback
may be presented to the user in a customizable GUI format that
enables a number of different hierarchical views of an
organization's progress with regards to sustainability objectives.
The feedback may also be used to inform a decision-making process
and to maintain or advance the defined objectives.
[0021] Computing system 102 may also comprise one or more memory
modules 106 and/or data storage devices 110. These memory modules
106 and/or data storage devices 110 may comprise any hardware,
software, firmware, or combination thereof operable to store and
facilitate retrieval of information. The one or more modules 106
and/or data storage devices 110 may store information using any of
a variety of information structures, arrangements, and/or
compilations. Memory module 106 may, for example, comprise a
dynamic random access memory (DRAM), a static random access memory
(SRAM), a NAND flash memory, or any other suitable volatile or
nonvolatile storage and retrieval device or combination of devices.
Data storage device 110 may comprise, for example, one or more
databases, computer components, devices, and/or recording media
capable of retaining digital data. Data storage device 110 may, for
example, comprise a magnetic data storage device (e.g., a diskette
or a hard disk drive), an optical disc storage medium (e.g., a
Laserdisc), a magneto-optical disc-based data storage device (e.g.,
a MiniDisc), a dynamic random access memory (DRAM), a static random
access memory (SRAM), a NAND flash memory, or any other suitable
volatile or nonvolatile storage and retrieval device or combination
of devices.
[0022] The one or more memory modules 106 and/or data storage
devices 110 may comprise any number of storage media without
departing from the scope of the present disclosure. Additionally,
all or part of the one or more memory modules 106 and/or data
storage devices 110 could reside locally within computer system 102
or could reside in a location remote from and accessible to
computer system 102 (e.g., at some other computing system 102,
within removable media, and/or at an external database). Computing
systems 102 could communicate with the one or more memory modules
106 and/or data storage devices 110 through network 104 or, in
other embodiments, computing system 102 could communicate with the
one or more memory modules 106 and/or data storage devices 110
using direct links.
[0023] Input/output ("I/O") functionality 112 may comprise, for
example, any communication method between computing systems 102
and/or within a particular computing system 102 (e.g., from an
image buffer to a display). In some embodiments, input
functionality may comprise, for example, the receiving signals or
data by a computing system 102 using a standard or non-standard
communication method. In other embodiments, output functionality
may comprise, for example, the communication of signals or data by
a computing system 102 using a standard or non-standard
communication method. These terms may also refer to part of an
action, such as, for example, to "perform I/O" may involve
performing an input and/or output operation. In some cases, devices
for communication between computing systems 102 may be used to
implement both input and output functionality.
[0024] Interface 114 may comprise, for example, any device(s) that
may be used (e.g., by a person, or by another device or system) to
communicate with a particular computing system 102. For example,
keyboards and mice may be considered input interfaces 114 of some
computing systems 102, while monitors and printers may be
considered output interfaces of some computing systems 102.
[0025] FIG. 2 is one embodiment of a flowchart 200 illustrating
example steps that may be implemented by the data processing system
100 of FIG. 1. In general, flowchart 200 includes steps related to
developing a strategy of objectives, risk management, compliance
management, project management, portfolio management, performance
management, and idea management. Although this example is explained
in the context of sustainability, manager application 150 may be
capable of facilitating the management of a variety of alternative
objectives.
[0026] In step 202, sustainability objectives may be defined. For
example, manager application 150 may prompt a user to input
environmental sustainability objectives. In certain embodiments,
manager application 150 may prompt a user to input environmental
sustainability objectives by performing one or more of the
following steps: asking the user a series of questions, receiving
user responses to the series of questions, determining various
environmental sustainability objectives that may be related to the
received user responses, and providing a selection of potential
environmental sustainability objectives to the user based on the
determination. In a particular embodiment, objectives for an
organization and/or a particular division of an organization may
include reducing the carbon footprint by a particular amount,
reducing energy consumption by a certain percentage within a
particular time frame, increasing renewable energy production,
etc.
[0027] In step 204, risk attributes may be identified. For example,
manager application 150 may prompt a user to input risk attributes.
Risk attributes may include, for example, funding capabilities of
an organization, technical complexities of sustainability projects,
environmental impact of various activities, and/or a variety of
other risk attributes that may be related to the sustainability
objectives defined in step 202. In particular embodiments, manager
application 150 may provide a user with an option to select from a
set of risk attributes. The set provided to the user may be based
upon the sustainability objectives defined in step 202. For
example, manager application 150 may automatically perform a query
or a lookup (e.g., using data storage device 110) based upon the
sustainability objectives defined in step 202 and manager
application 150 may return a corresponding subset of risk
attributes related to those objectives. Manager application 150 may
be capable of providing a user the option to select among the
returned subset of risk attributes, to modify the returned subset
of risk attributes, and/or to input alternative risk
attributes.
[0028] In step 206, compliance requirements may be identified. For
example, manager application 150 may prompt a user to input
measurable performance expectations for the organization related to
environmental sustainability, such as, for example, internal
policies related to energy consumption and/or GHG emission
reduction targets. Additionally, manager application 150 may prompt
a user to input various parameters describing an organization and,
in response to the user's input, manager application 150 may
automatically output suggested compliance requirements based upon a
predefined relationship between those parameters and potentially
applicable environmental regulations. Manager application 150 may
further be capable of providing a user the option to select among
the suggested compliance requirements, to modify the suggested
compliance requirements, and/or to input alternative
requirements.
[0029] In step 208, potential projects are identified. In
particular embodiments, each project generally includes
initiatives, ideas, and/or planned activities generally related to
advancing one or more objectives. According to one embodiment,
manager application 150 may retrieve project submissions provided
by various sources (e.g., via a webpage) that may be internal
and/or external to an organization. Additionally, manager
application 150 may enable a user to categorize project submissions
and provide a GUI that is logically structured to facilitate
browsing for project submissions on particular topics, scope,
costs, carbon mitigation, etc. Manager application 150 may further
be capable of providing a user the option to add comments or
otherwise modify particular projects, to group projects (e.g., into
folders and/or hierarchical directories), and/or to input
alternative projects. In various embodiments, projects and/or their
foundational ideas may be categorized using a hierarchical
categorization.
[0030] In step 210, a potential project portfolio is identified.
For example, manager application 150 may enable user to evaluate
project submissions and promote those projects deemed worthy of
further examination by submitting scores, which may be received and
recorded by manager application 150. In various embodiments,
manager application 150 may summarize project scores submitted by
users and indicate those projects considered to be the best
possible initiatives. In addition, manager application 150 may be
capable of automatically indicating, and/or enable a user to
indicate, those projects that are most likely to further objectives
identified in step 202. In some embodiments, manager application
150 may further be capable of providing a user the option to set
and/or weight the scores of those projects indicated as being the
most likely to further the identified objectives.
[0031] Step 210 may further include comparing environmental
improvement projects using a number of alternative considerations.
For example, manager application 150 may prompt a user to input
various environmental, financial, and social considerations for
particular projects identified in step 208. According to one
embodiment, environmental considerations may include the potential
impact of a particular project on the carbon footprint of an
organization and/or resource optimization. Particular financial
considerations may, for example, be measured in terms of pure cost,
return on investment (ROI), net present value (NPV), and projected
breakeven point. Social considerations may, for example, include an
estimated score of how favorably or unfavorably the project may be
perceived by those holding a stake in the organization (e.g.,
collected via supplier assessments, customer assessments, etc.). In
particular embodiments, manager application 150 may be capable of
providing a user the option to modify or otherwise set and/or
weight recorded scores in a manner that reflects these alternative
considerations. In various embodiments, the comparison may be
illustrated in a GUI dashboard.
[0032] FIG. 3 is one example embodiment of a GUI dashboard 152 that
may be used in step 210 to assist a user in identifying a project
portfolio. In this example, potential projects are organized into
rows according to a three-level hierarchy. Although this example
includes a three-level hierarchy, any other hierarchy may be used
without departing from the scope of the present disclosure. In this
example, the first four columns (e.g., cut costs, reduce carbon,
enhance reputation, and increase revenue) correspond to four
identified high-level organizational objectives. As part of the
project approval process, each potential project may be evaluated
against the higher-level objectives and scored as to how they are
expected to align. If other project attributes (e.g., ROI,
projected breakeven point, etc.) are comparable, the projects
selected for execution may include those with the highest expected
alignment scores.
[0033] Based on one or more results of steps 202, 204, 206, 208
and/or 210, manager application 150 may be capable of providing
holistic views that may be used to compare potential projects in
terms of a cost/benefit analysis. Using these view-based
comparisons, a user may be able to strategically select a potential
project portfolio that includes those projects anticipated to
collectively optimize a cost-to-benefit ratio. Manager application
150 may further be capable of providing a user the option to modify
the composition of a project portfolio and/or group projects into
alternative project portfolios.
[0034] Steps 212 through 220 generally relate to the feedback loop
that may be used to capture, calculate, and/or measure information
about environmental activity, impacts, and performance. In
particular embodiments, this information may be used to inform the
decision-making process and to maintain or advance organizational
objectives.
[0035] In step 212, a software object referred to herein as one (or
more) instances of "source" is initialized. For example, manager
application 150 may prompt a user to input various characteristics
defining diverse activities of an organization, which in some cases
may facilitate measuring the environmental impact of such
activities. In various embodiments, the characteristics defined in
step 212 may be used to perform detailed sustainability analyses,
as explained further below.
[0036] FIG. 4 is one example embodiment of GUI dashboard 152 that
illustrates various types of activities of an organization that are
each linked to a respective source object. In this example, air
travel is partially defined in terms of miles traveled, electricity
consumption from a power grid is partially defined in terms of
kilowatt-hours, and particular manufacturing processes may be
partially defined in terms of tons of coal consumed. Although
particular examples of activities are disclosed, any other activity
of an organization or division of an organization may be evaluated
without departing from the scope of the present disclosure. Each of
these activities may directly and/or indirectly contribute to
carbon emissions. As shown in FIG. 4, each activity is further
defined in terms of category. In some cases, activities may be
defined in terms of location, which may be relevant, for example,
if an organization spans one or more power grids supported by
different energy sources (e.g., coal-fired power versus renewable
energy sources). Additionally, instances of the source object may
extend into business characterizations of an organization
including, for example, revenue, inventory, and/or any other
business-related basis that an organization might use to help
measure the environmental impact of a business-related
activity.
[0037] As data processing system 100 records various activities,
the pertinent characteristics of the source object are inherited or
logically linked into the resulting activity. As such, the
environmental impact of disparate activities may be readily
quantifiable, aggregated, and compared on an apples-to-apples
basis. As illustrated in FIG. 5, for example, manager application
150 may be capable of providing a GUI dashboard 152 that shows
total energy consumption aggregated by source and year. Although
this example compares energy consumption, any other environmental
impact comparison may be used without departing from the scope of
the present disclosure.
[0038] In various embodiments, manager application 150 may enable a
user to modify characteristics of a source and may further respond
to such modification by dynamically updating previously recorded
data. As time progresses, source instances can be modified, added,
and/or removed as desired to meet the changing needs of an
organization.
[0039] In step 214, a software object referred to herein as one (or
more) instances of "emission factor" is initialized. For example,
manager application 150 may prompt a user to identify, for each
organizational activity tracked by data processing system 100, a
representative value that relates the quantity of one or more GHG
emissions released to the atmosphere (or some other sustainability
factor) with an activity associated with the release of that
emission. In particular embodiments, emission factors may be
expressed as the weight of pollutant divided by a unit mass,
volume, distance, or duration of the activity emitting the
pollutant (e.g., kilograms of carbon dioxide per kilowatt-hour of
electricity consumed). Various emission factors may be dependent
upon date, location, and/or source. For example, electricity
consumption at a particular location powered by a hydro plant may
have a smaller emission factor for one or more types of GHG
emissions than electricity consumption at another location powered
by a coal plant.
[0040] In various embodiments, the emission factor object structure
may be designed to ensure an organization maintains critical data
regarding an emission factor. For example, data processing system
100 may retain data about the emission factor itself, the source
from which it is derived, and/or may allow the user to attach
related documentation. In some cases, data is maintained to record
the time-period relevant to the emission factor and/or a time-stamp
of when the emission factor was last examined for accuracy. In
particular embodiments, the granularity of the emission factor can
be recorded as CO2e and/or as an individual emission gas.
[0041] In various embodiments, manager application 150 may enable a
user to define multiple facilities of an organization using a
straightforward hierarchy. For example, a geographical
organizational breakdown structure (OBS) may be defined in terms of
Company
Name.fwdarw.Region.fwdarw.Country.fwdarw.State/Province.fwdarw.City.
The organization may be given the flexibility to define emission
factors at any level of the hierarchy as appropriate. For example,
an organization may have 175 facilities using natural gas in North
America (region) that can share the same emission factor based upon
reliable information about commercial gas furnaces. Rather than
tracking 175 separate records, the organization can set this once
at the region level. In various embodiments, manager application
150 may be capable of automatically applying the recommended
emissions factor to all facilities within the region. Additionally,
manager application 150 may enable a user to override this
region-level emission factor setting. For example, if a particular
facility uses a special type of furnace, a user may be given the
option to override a region-based emission factor value by
explicitly creating an emission factor for that facility. Manager
application 150 may be configured to apply the most granular factor
available, by default, thereby potentially enhancing accuracy.
[0042] In particular embodiments, manager application 150 may
enable a user to modify characteristics of an emission factor.
Manager application 150 may further respond to such modification by
dynamically updating recorded data. As time progresses, emission
factor instances can be modified, added, and/or removed as desired
to meet the changing needs of an organization.
[0043] Because the emission factor object itself has information
regarding the age of the underlying data, manager application 150
may be capable of storing stale data thresholds that ensure
out-of-date emission factors are not used. For example, if the
explicit emission factor for a Boston office has not been kept
current and its review date is older than the user-specified stale
data threshold, then manager application 150 may automatically look
further up the hierarchy to locate an emission factor that is
applicable to the Boston office.
[0044] Such a design may provide a variety of useful features. For
example, the geographic hierarchy of some emission factors may
enable users or manager application 150 to readily identify
particular locations or regions that provide the cleanest energy.
In some embodiments, manager application 150 may be capable of
suggesting the hierarchy level for each emission factor. In certain
embodiments, users may be capable of determining the hierarchy
level applied for each emission factor. Additionally, emission
factors that fall out-of-date may be flagged for review by manager
application 150, which may also store an audit trail documenting
who reviewed what emission factor and when. An organization may be
allowed to set standards for how often emission factors should be
reviewed. In some embodiments, users may be able to identify the
emission factors used to determine emissions data for any given
time period using available emission factors history maintained by
manager application 150. Yet another advantage is that setting
stale data thresholds may mitigate the risk that the same old data
is used year-after-year.
[0045] According to a particular embodiment, the processing of
emission factors in step 214 may be substantially similar to the
following:
TABLE-US-00001 { OBS /* Hierarchical OBS structure */
emission_factor /* documented applicable emission */ /* factor */
/* within OBS */ current_date emission_factor_review_date /* Date
Emission Factor was */ /* last reviewed */ stale_data_threshold /*
user-defined threshold for */ /* acceptable aging of emission
factor */ emission_factor_for_activity /* emission factor
multiplier that will */ /* be used to calc the actual emissions */
/* of the activity */ Read lowest level of OBS do { If
(emission_factor exists) { If ((current_date -
emission_factor_review_date) < stale_data_threshold) { Copy
emission_factor to emission_factor_for_activity } Read next level
of OBS } While (emission_factor_for_activity= null) }
[0046] In step 216, performance is measured. In various
embodiments, manager application 150 may track relevant ecological
activity of an organization in a normalized format, referred to
herein as the software object "ecoActivity." In particular
embodiments, ecological activities of an organization that may be
tracked by instances of the ecoActivity object may, for example,
include one or more of the following: waste production; shipping;
one or more manufacturing processes; business air travel; water
usage; the burning of natural resources (e.g., natural/LP gas, coal
and/or diesel fuels); electricity usage; electricity production;
and/or fugitive emissions.
[0047] Particular instances of the ecoActivity object may track
these or other activities in terms of gas consumption, electricity
consumption, carbon emissions, cost, employee headcount, affected
square footage, ambient temperature, a timeframe of the activity,
and/or any of a variety of other quantifiable elements that may or
may not be directly related to sustainability. For example, manager
application 150 may calculate carbon emissions data in step 216 by
linking an ecoActivity instance to a corresponding emission factor.
In particular embodiments, the calculated carbon emissions may be
measured in terms of CO2e and/or as an individual GHG. In the case
of business air travel or shipping, for example, carbon emissions
may be calculated as a multiple of distance units (e.g., miles or
kilometers traveled), which may be at least partially defined by
logically-linked source and emission factor objects.
[0048] The normalized data structure provided via the ecoActivity
object may enable recording of various related data that can later
be used as intensity metrics. In addition, ecoActivity may enable a
user to exploit configured characteristics based upon the location
and/or type of an activity. As such, an instance of the ecoActivity
object may inherit user-defined characteristics. Furthermore, the
ecoActivity object may enable a user to aggregate data at a variety
of different hierarchical and/or logical levels that may be
reported in a variety of useful and flexible ways, as described
further below.
[0049] Each instance of the ecoActivity object may be recorded in
step 216 at any suitable level of granularity. In some embodiments,
for example, instances may be recorded at a high-level for a
particular country or region. Alternatively, instances may be
recorded at a more granular level, such as, for example, by
facility, utility account, and/or individual meter. In addition,
instances may be recorded at any suitable periodic intervals (e.g.,
daily, weekly, monthly, quarterly, yearly, etc.) and/or after
particular events trigger (e.g., after completion of particular
project milestones).
[0050] Step 216 may further include populating a portion of a
project performance dataset by extrapolating estimated data based
on actual measurements. In this manner, gaps within a dataset may
be automatically or manually filled, thereby potentially enhancing
analytical options available to a user. In particular embodiments,
a user may be given the option to either include or exclude
extrapolated data from the results during subsequent reporting.
Further, a user may optionally identify ecoActivity data as
non-aggregated, which in some cases may prevent the data from being
included in data aggregation.
[0051] In step 218, reports are generated. Throughout this document
the term "report" generally refers to any collection of information
provided to a user. In various embodiments, the report can
comprise, for example, an aggregation and/or a dis-aggregation of
information. The information may be provided to the user in a
computer-displayable format (e.g., in a PDF format, as a dashboard
152, as a text message, etc.), in a tangible format (e.g. a
computer printout, a fax, etc.), and/or any other suitable format
for display to a user. For example, manager application 150 may be
capable of enabling a user to interface with a variety of GUI
dashboards 152 summarizing one or more of the project performance
measurements recorded in step 216. In an alternative embodiment,
reports may be generated in 218 that indicate performance of all or
a portion of the organization in a manner that may not necessarily
be defined or bounded in terms of projects. For example, a report
may indicate one or more of the following: the carbon footprint of
the organization as a whole; energy consumption of particular
facilities; shipping in terms of nautical miles attributed to
particular organizational divisions or products; and/or any other
performance indicator(s) for all or a portion of an
organization.
[0052] In particular embodiments, GUI dashboards 152 may enable a
user to aggregate data at variety of different hierarchical levels.
According to one embodiment, data may be aggregated according to
the geographical OBS. Additionally, data may be further aggregated
according to a variety of logical hierarchies. For example, FIG. 6
is an example GUI dashboard 152 illustrating total energy
consumption aggregated by year. FIG. 7 is an example embodiment of
GUI dashboard 152 illustrating energy consumption per headcount and
aggregated by year.
[0053] In various embodiments, manager application 150 may provide
a user with the option to input metric data, which may contribute
to the generation of key performance indicators (KPIs). In
particular embodiments, KPIs may be used to measure the progress of
one or more projects in terms of achieving identified objectives.
In some embodiments, for example, KPIs for environmental
sustainability may include energy consumption, actual return, cost
savings, reduction of particular GHG emissions, and/or any other
indicator that may be used to measure the progress of one or more
projects in terms of achieving identified objectives. In addition,
project performance may be measured in terms of project management
features, such as, for example, schedules, milestones, tasks, and
resource consumption. In various embodiments, KPIs may be used to
measure the progress of all or a portion of an organization in a
manner that may not necessarily be defined or bounded in terms of
projects. For example, some KPIs may indicate one or more of the
following: the carbon footprint of the organization as a whole;
energy consumption of particular facilities; shipping in terms of
nautical miles attributed to particular organizational divisions or
products; and/or any other performance indicator(s) for all or a
portion of an organization.
[0054] FIG. 8 is one example embodiment of GUI dashboard 152
showing various KPIs for multiple objectives organized into rows
according to a two-level hierarchy. Although this example includes
a two-level hierarchy, any other hierarchy may be used without
departing from the scope of the present disclosure. In this
example, the KPI columns include a trend column populated with
arrow icons for each objective. The direction of the arrow
indicates a positive, neutral, or negative trend relative to
sustainability objectives. Each KPI cell may be drilled into (e.g.,
via a mouse-click selection) to see how the data associated with
the underlying metric is progressing. For example, selecting one of
the arrow icons of the trend column may reveal a trend line
charting the available data values over time.
[0055] In particular embodiments, step 218 may include generating
reports related to stakeholder impact on sustainability. The term
"stakeholder" as used herein generally refers to any customer,
supplier, internal or external partner, employee, manager,
nongovernmental organization (NGO), etc. that may impact, and/or be
impacted by, environmental sustainability decisions and/or
activities of an organization. In various embodiments, a
stakeholder software object may enable organizations to maintain
stakeholder related data and integrate such data into key business
sustainability practices.
[0056] In various embodiments, stakeholder objects maintained by
system 100 may have instances defining one or more of the following
characteristics of the stakeholder: description; category (e.g.,
customer, competitor, NGO, etc.); owner of the relationship; nature
of the relationship; funds provided by the stakeholder; approval
power granted to the stakeholder; importance rating from an
organizational perspective; objectives that may affect the
stakeholder relationship; projects that the stakeholder may have
suggested to the company (whether formally or informally); past,
present, or future projects that may impact the stakeholder
interest; how stakeholder interest may be affected by past,
present, or future projects (i.e. positively or negatively);
assessment activities involving the stakeholder; etc. FIG. 9
illustrates an example embodiment of dashboard 152 that may be used
to display stakeholder data.
[0057] The stakeholder object may further enable a user or manager
application 150 to score the extent to which stakeholder interests
align with organizational interests and/or the extent to which such
interests may be optimally aligned. In some cases, this information
may indicate the volatility of particular stakeholder
relationships. For example, if a stakeholder is rated as important
and the delta between actual and optimal interest alignment is
high, then manager application 150 may suggest taking action to
improve the relationship. Manager application 150 may be capable of
generating reports that indicate organization activities that have
a significant impact on stakeholder interests. Thus, step 218 may
include generating a variety of reports logically linked to
particular stakeholders, which may be used, for example, to help
shape the perception of sustainability efforts and objectives.
[0058] In various embodiments, stakeholder objects may be linked to
one or more projects. In this manner, stakeholder interests may be
a factor considered during the portfolio identification of step
210. Additionally, during the course of a project, various progress
reports and/or dashboards may be generated in step 218 and
automatically communicated to stakeholders. The relevant
stakeholder identities for each project may be readily determined
using the linked stakeholder objects. In addition, as shown in FIG.
9, the nature of various relationships between stakeholders and
projects may be defined. For example, the stakeholder "Building
Technologies, Inc." is shown as having or expected to have a very
strong influence over the "building insulation" project. As another
example, the stakeholder "Employees" are impacted only minimally by
the "several consolidation" project.
[0059] Thus, customizable reports may be generated in step 218
using a variety of different software objects that may be logically
linked together. In various embodiments, the reports may provide
feedback that informs subsequent decision-making process as
flowchart 200 loops back to step 202 or some other step in the
process.
[0060] In step 220, assessments may be defined and executed. Each
assessment may have any number of attributes. For example,
particular assessments may have one or more attributes selected
from the following: date range; human rights; health and safety;
labor management relations; diversity of workforce; water usage;
applicable facilities; operational boundaries; organizational
boundaries; geographical boundaries; product safety; supply chain;
number of employees; carbon emissions; energy efficiency; waste;
recycling; environmental safety; transportation; travel; and
reporting.
[0061] Particular assessments may enable users to step back and
objectively determine how an organization is performing in a
variety of different areas. Some assessments may be initiated in
response to the detection of a problem related to one or more
defined objectives. The format, design and purpose of an assessment
can vary widely and may be highly customizable. FIG. 10 illustrates
one example embodiment of GUI dashboard 152 illustrating various
assessments performed by manager application 150.
[0062] In particular embodiments, manager application 150 may
provide templates that can be used as a guide for creating and
executing successful assessments. For example, a collection of
common assessment attributes may be made available to users to
jumpstart the assessment creation and provide some fundamental
traits from which to choose. These object attributes can be
concealed or added to the assessment view to meet the specific
requirements. Alternatively, manager application 150 may enable
users to generate customized assessments from scratch.
[0063] Although the type and context of the assessment can vary,
the framework of linked objects provided by various embodiments
generally enables a variety of features. For example, particular
assessments may include the ability to: generate assessment related
activity records for monitoring progress of data collection; align
the assessment with a project to manage associated costs, resources
and progress; provide a record (e.g., an audit trail) of
organizational efforts surrounding the assessment type (e.g., past
and present); spawn and track ideas created as part of the
assessment findings; use ideas spawned by assessments to generate
projects; provide dashboard-type reporting of assessment progress
(e.g., GUI dashboard 152 of FIG. 10); preserve assessment results
for auditing, which may be used to serve as a foundation for future
assessment iterations; attach key assessment documents, such as
surveys and attestations; integrate with web-based data collection
forms; collect data using online questionnaires, surveys, etc.,
whether provided internally within system 100 or externally by
third party online survey providers, and/or some other ability
related to assessing performance of an organization.
[0064] Once an assessment is defined, the assessment may later be
recalled to help instantiate a new assessment. Particular
user-defined assessment types can be instantiated as many times as
needed as part of a process of ongoing monitoring and improvement.
Each assessment may inherit the innate capabilities of the parent
assessment.
[0065] The components of the systems and apparatuses disclosed
herein may be integrated or separated. Moreover, the operations of
the systems and apparatuses may be performed by more, fewer, or
other components. The methods may include more, fewer, or other
steps. Additionally, steps may be performed in any suitable order.
For example, although FIG. 2 illustrates step 220 as an individual
step within flowchart 200, in particular embodiments the
assessments described in step 220 may be used to help identify
risks in step 204, to identify sources in step 212, to measure
performance in step 216, to notify individuals or sub-systems to
track sources for particular locations, and/or to enable a variety
of other features. In particular embodiments, all or a portion of
the steps disclosed herein may be wholly automated, partially
automated, and/or partially performed manually. Particular
operations of the systems and apparatuses disclosed herein may be
performed using any suitable logic embodied in non-transitory
computer-readable media. As used in this document, "each" refers to
each member of a set or each member of a subset of a set.
[0066] Although the present disclosure has been described above in
connection with several embodiments, a myriad of changes,
substitutions, variations, alterations, transformations, and
modifications may be suggested to one skilled in the art, and it is
intended that the present invention encompass such changes,
substitutions, variations, alterations, transformations, and
modifications as fall within the spirit and scope of the appended
claims.
[0067] To aid the Patent Office, and any readers of any patent
issued on this application in interpreting the claims appended
hereto, applicants wish to note that they do not intend any of the
appended claims to invoke paragraph 6 of 35 U.S.C. .sctn.112 as it
exists on the date of filing hereof unless the words "means for" or
"step for" are explicitly used in the particular claim.
* * * * *