Enterprise Energy Management System

The vendor is required to provide enterprise energy management system (EEMS) is to assist the city in meeting that goal by delivering high-quality data tracking to provide visibility into energy performance, accurate reporting of the city’s progress towards GHG reduction goals, and verification of utility bill charges.
- The additional module includes:
• Specialty support for building emissions reduction and disclosure ordinance (including but not limited to):
o Capturing and exporting solar generation data (either in the form of on-bill credits or power purchase agreement)
o Capturing the enrollment status of each municipal account (particularly those that are associated with buildings) in city choice electricity and the associated adjusted grid emissions factor
• Emissions details
o Complete emissions history for all individual assets and asset types
o Emissions factors for all energy types, and with respect to electricity, emissions factors that pertain to specific periods of consumption and are in line with the city and other accepted analysis of the regional grid emissions factors
• Cleaning, hosting, and visualizing interval data from time of use electric accounts
• Cleaning, hosting, and visualizing fleet fuel consumption and cost data from four city of fleets
- Core services
1. Data capture and organization
a. Data capture
• The city consumes resources (energy and water) across a wide portfolio of assets, and receives invoices and consumption data via various delivery methods. the capture, organization, and hosting of this data is a primary function of the EEMS and must be performed in a manner that meets the city’s requirements.
• The city will also require the integration of thirteen (13) years of historical data (commencing July 1, 2009), which is being hosted on the city’s current EEMS
• This is necessary to enable the city to measure progress against established de-carbonization benchmarks
• There are a small number of bills for a subset of electric accounts, gas accounts, steam accounts and fuel oil deliveries that are delivered physically as hard-copies or electronically as pdf files
b. Commodities/service types
• Electricity
o Local distribution company (“LDC”) utility billing
o Third party electricity supply billing
o Physical solar power purchase agreement billing
o Virtual power purchase agreement billing
• Natural gas
o LDC utility billing
o Third party natural gas supply billing
• Water, sewer, and stormwater
• District steam
• Delivered fuels
c. Frequency
• Monthly utility bills (current and historic)
• Quarterly fuel deliveries (current and historic)
• Manually uploaded data (as needed)
d. Asset types
• Buildings - single occupant and some multi-tenancy
• Parks - green spaces, athletic fields, fountains, sprinklers, squares, etc.
• Streetlights and traffic signals
• Unmetered and tariff-calculated utility bills
2. Data validation and normalization
a. General invoice validation
• The selected vendor must be able to collect energy and water billing data directly from the respective local distribution companies (LDCS) or utility (major vendors), as applicable, and fuel vendors, mostly as bulk ascii text files with the exception of some individual .pdf and .xls files, and hard copies.
b. unit of measure normalization
• The city is billed for energy and water consumption in a variety of units of measure (UOM).
• The selected vendor must be able to convert between all billed UOMs and be able to convert energy data to million British thermal units (MMBTUS).
3. Data reporting, extraction, and integration
a. Monthly payment reporting
• For all utility services where the selected vendor is performing general invoice validations against monthly bill files, a payment advice report must be generated and sent to the city’s auditing department
this report will identify total current charges due for each city department, matching all utility accounts to their respective budget codes.
• All current charges must be verified as accurate and be approved for payment
• The vendor will be responsible for working with the city’s EEMS administrator and auditing department as well as the relevant utility vendors to resolve any errors, credits, or amended billing amounts such that any adjustments are accurately reflected in the subject city department’s budget for the correct fiscal period.
b. Annual reporting
• The city is required to report energy consumption and greenhouse gas emissions for all municipal operations on an annual basis.
• The ideal solution will allow reporting on a calendar year (January-December), as well as on a fiscal year (July-June) basis, and be easily exported to microsoft excel.
c. Energy star portfolio manager; BERDO
• Energy star portfolio manager (ESPM) is a critical tool for complying with the city’s reporting obligations.
• ESPM is used to report energy metrics for all 350+ municipal buildings and is the means by which the city meets its reporting obligation under its own building emissions reduction and disclosure ordinance (BERDO), as well as voluntary programs such as the department of energy better buildings challenge
the proposed EEMS solution must automatically synchronize energy and water data with energy star portfolio manager
• Energy star portfolio manager requires twelve (12) uninterrupted, consecutive months of energy data to calculate an energy use intensity (EUI): the EEMS must deliver this data consistently and accurately, ensuring that there are no gaps for any such monthly periods
d. Data ownership and extraction
• Site details
• Department
• Asset name
• Street address
• Energy details
• Complete cost and consumption history for all service types including on-site generation
• Account and meter numbers
• Service type
• Rate class and rate code
• Vendor
• Formatting
• Ability to export selected or all data to pdf
• Ability to export selected or all data to excel
• Ability to export selected or all data to csv
• Ability to set up an automated export of raw data in json or csv format to an ftp, rest endpoint, or a SQL server owned by city.
- Contract Period/Term: 3 years
- Pre-Proposal Questions Conference Call Date: April 7, 2025