Department aggregated list of performance measures and metric tracker. Data reporting may have a 14-day lag. Includes the following performance measures: Accuracy of Switching Orders; 12kV Substation Capacity Available for Use; Response Times to Call Outs; Reliability – Number of Outages; Reliability – Outage Duration (SAIDI); Reliability – Outage Frequency (SAIFI); and Accuracy of Meters.

Monthly summary of electric energy used by all City Buildings. Use is measured by (kWh) by City Buildings. The data is both internal (CIS) and external data sources (Salt River Project Utility Bills).

The list of sewer lines that are cleaned and/or inspected by month, including the number of miles cleaned or inspected. Inspections are accomplished with CCTV and acoustic technologies while cleaning uses a pressure washer to clean the inside of the pipe. The work is completed by City of Mesa crews and contractors. Contractor data is summarized. Location data has been redacted.

This version redacts sensitive information including personnel assigned and responding to the service request. This dataset allows for the calculation of the Arizona 811 Tickets submitted in the Mesa and/or Magma Service Areas. An 811 locate ticket is generated by a homeowner or excavator contacting Arizona’s 811 service and informing them that they have a project that involves underground excavation. The ticket is assigned a ticket identification number and forwarded to the appropriate utility that assigns department various staff (gas, water, electric, etc.) to identify and mark any existing underground utilities in the specified project area.

This dataset contains the necessary information to compute the average cost of a utility locate in the Mesa and/or Magma Service Areas (see Service Area maps). A utility locate involves identification of all underground utilities prior to excavation in a specified area. A utility locate is initiated, usually by a homeowner or excavator, by calling 811 or contacting Arizona’s 811 center’s website and providing the address, county and nearest cross street of where they’re planning to dig, as well as the type of project they’re completing and the exact area on the property they’re planning to dig. 811 then contacts the city’s utilities so they can mark the presence of any underground utilities in the proposed project area. Utility locates can contribute to increased safety to people and property and can eliminate unexpected costs due to accidental damage of buried utilities. A locate can be initiated by either a homeowner or an excavator. Data being reported may have a 14 day lag.

Total consumption in kWh and as percentage of overall city energy consumption by type of city facility.

This dataset allows for the monthly computation of the System Average Interruption Frequency Index (SAIFI) for the City of Mesa’s electric utility. The System Average Interruption Frequency Index is commonly used as a reliability indicator by electric power utilities. It measures the average outage frequency per customer and is calculated by taking the sum of the total customers interrupted divided by the total number of active customers. Data reporting may have a 14 day lag.

Budget Book page.

This version redacts all sensitive information including the person making the report, street number, longitude, latitude, geolocation, and name of excavator. This dataset contains information necessary to compute the number of reportable incidents occurring per month on Mesa’s natural gas system and determine the cause of any damages that may occur.

Aggregates current, previous and target energy usage for city owned facilities where site type = Drinking Water Treatment & Distribution.

SELECT
month_date,
sum(`kwh`),
sum(`previous_kwh_usage`),
sum(`target_kwh`),
case(`sum_kwh` > 0, (`sum_kwh` - `sum_previous_kwh_usage`) / `sum_previous_kwh_usage`) AS `total_percent_change`,
case(`sum_kwh` > 0, (`sum_kwh` - `sum_target_kwh`) / `sum_target_kwh`) AS `target_percent_change`

WHERE `site_type` IN ('Drinking Water Treatment & Distribution')

GROUP BY
`month_date`

ORDER BY `month_date` desc