greenerApps Inventory Guide + User Manual

This guide is intended for anyone who is building a greenhouse gas (GHG) inventory in greenerApps for the first time. It integrates the greenerApps User Manual and a GHG inventory data collection guide into a single document. The goal of this guide is to teach you how to create an inventory as you learn how to use greenerApps itself.

DocumentsDate added

Order by : Name | Date | Hits [ Descendent ]
This section provides an overview of the GHG inventory process, greenerApps 2.0 and information on other key topics.
You will manage your organization's inventory information in greenerApps by creating records. Records are stored in the tabs that appear at the top of the user interface screen. greener Apps uses links between records and across the tabs to create "relationships". These relationships facilitate navigation within greenerApps, and they are crucial to accurate data reporting.
An overview of how to set up greenerApps to meet the needs of your organization and your inventory.
Source Data records contain detailed assumptions about energy and emissions. Information in Source Data records is integral to the calculation of your organization's greenhouse gas (GHG) emissions.
You can use Account or Organization records to link your energy providers to your Energy Use records for easy tracking.
Asset records include descriptive information about your organization's physical assets, such as buildings, vehicles, and HVAC units. The primary purpose of Asset records is to help you track the contribution of each of your assets to your total emissions so you can address the specific items that will have the greatest impact. greenerApps asset categories are: Properties, On-Site Energy, Vehicles, Refrigeration, Animals and Chemicals.
In this section you will learn about Usage records, which are used to calculate your GHG emissions. greenerApps Usage records categories are: Energy Use, Fleet Use, Commuting, Travel, Refrigerant Use, Farming, Fertilizer Use, Waste, Chemical Use, Offsets and Sinks.
Tracking records store general information as well as specific data related to assets. Some track local temperatures so that you can correlate them with your energy use, others track certain types of green projects that your organization may undertake.
Inventory records summarize all of your system data for a particular time frame. They are created by running reports, making a record, and then entering data from the reports into the Inventory record. This section will describe the process in detail.
greenerApps is designed to meet a broad range of reporting requirements for emissions and energy. greenerApps' reporting tools include pre-built reports, user-generated reports, reporting records and dashboards. This sectionprovides an overview of how to use these features.
ISO has developed Standard Number 14064 (ISO 14064) for the quantification, monitoring, reporting and verification of GHG emissions and/or removals. According to ISO, ISO 14064 "is expected to benefit organizations, governments, project proponents and stakeholders worldwide by providing clarity and consistency for quantifying, monitoring, reporting and validating or verifying GHG inventories or projects.
greenerApps users can increase their productivity and expand their communications options by taking advantage of the many built-in features of Force.com, the versatile platform on which greenerApps is built. The options listed un this section - and many more - are described at http://www.salesforce.com (http://www.salesforce.com/).
Once a Fleet Use record has been saved, greenerApps applies logic tests so that it can correctly calculate the resulting emissions. These logic tests are in place to ensure that the correct information from the Fleet Use record and the related Source Data record is applied. greenerApps has the flexibility to use both of the two commonly accepted emission calculation methods.
greenerApps 2.0 is an open source suite of applications. This section contains the entire source code for greenerApps 2.0, which is contained in a single Force.com Apex class and its related trigger. You are welcome to use this code however you wish for non-commercial projects.