This dataset provides information regarding the location of existing site addresses within the City of Mesa. Site addresses are active and usable by property owners, the US Post Office, utility companies, etc. The dataset includes unit or suite addresses.

Filtered on current week, updates Mon @10am. Orange - # datasets exceeding expected last update age (timeliness); Green - # of datasets within expected currency range (timeliness) Use category filter to select individual department(s) for analysis.

Wifi Activity as connected to city-owned access points. Note: only devices that connected to an SSID is listed. Note that SSID @mesa generally reflects WiFi sessions by members of the public (non city employees or city devices). Other devices that may have been in the area but did not connect are not included. Sensitive fields such as device MAC address have been scrambled and are not actual addresses. However, although these have been changed, the uniqueness and mobility of the device has been maintained for listed sessions.

This is an annual customer survey sent out to City of Mesa employees. The survey asks employees to rate their overall satisfaction with Information Technology Services. This metric reports the score of those who report satisfied or very satisfied with overall performance of IT services

City boundary polygons excluding County islands. Data represents the current extent of the City’s jurisdiction and is updated whenever an annexation occurs. Delineates the boundary of the City which is useful for many projects and maps.

Zabbix, an open-source monitoring software tool, is reporting the availability of applications and infrastructure. Applications include Advantage, CIS, Kronos, Accela, Judicial Services, GIS, CMMS, and more. It is a roll up of 91 monitors. Infrastructure reports the enterprise platforms, which includes server, storage, network, IVR/ACD and UC platforms. It is a roll up of 57 monitors. The monitors include scheduled down time, which includes scheduled maintenance and upgrades. It also includes the routine downtime for Advantage The available time is converted to a percentage rounded to four 9s. The data set is coming from on ITD dashboard that is currently pulling the monitors’ data from Zabbix.

Information about the the timeliness of datasets published on the portal as measured by age of most recent data in each dataset compared with Max Expected Data Age. This dataset is populated via FME workflow that checks Socrata dataset currency by having the workflow keep a history of the dataset currency in Data Services data warehouse. A second FME workflow sends that currency data to this Socrata dataset. To remove a dataset from this check, enter 0 as the Max Expected Data Age metadata field for the relevant dataset.

Not included in the check are datasets that have:
a) RETIRED or DUPLICATE in the dataset name
b) 0 for Max Expected Data Age metadata field
c) no Max Expected Data Age value / does not have Date & Time formatted columns
d) no Date/Time formatted columns in the dataset.
e) draft dataset (not published)

This dataset contains all historical calendar dates through the current day and is used by datasets, performance measures and visualizations for the purposes of historical and calculations over time.

This data set lists projects currently in process and managed by the Department of Information Technology. Projects are noted if they are in an implementation phase, which would make their schedule and budget adherence applicable. Budget is listed and determined by project manager if they are within budget, at or under budget, to date. Schedule is determined by project start date, project manager original go live estimate and current go live estimate and /or actual go live date.

New dataset replacing https://citydata.mesaaz.gov/Information-Technology/Information-Technology-Project-Schedule-and-Budget/spka-r4fd.

This data set lists projects currently in process and managed by the Department of Information Technology. Projects are noted if they are in an implementation phase, which would make their schedule and budget adherence applicable. Budget is listed and determined by project manager if they are within budget, at or under budget, to date. Schedule is determined by project start date, project manager original go live estimate and current go live estimate and /or actual go live date.