Laserfiche WebLink
38 <br />AMI Feasibilitv Report I Client Name: City of Santa Ana <br />the availability of the historical data and analytic tools turn the data into useful information and a <br />powerful customer engagement tool. Providing comparison information to educate customers on <br />how their usage compares with their peers helps them identify potential equipment problems or <br />leaks. Delivering the notifications and information in easy-to-use formats has proven valuable and <br />impactful in the industry. <br />8.3 RAW AND PROCESSED DATA <br />The AMI system will collect the raw data from the water meter MTUs. There is some data validation <br />and error handling done in the AMI systems, but most data management is performed by the <br />MDMS. The raw data from the AMI system is sent to the MDMS, where it is processed. The raw data <br />is always maintained in their original form and never manipulated. If the MDMS must make <br />modifications to the data as part of its validation, estimation, and editing routines, it creates a new <br />copy of the data and stores both the processed data and raw data. This allows the City to go back to <br />the original data if necessary. <br />8.4 DATA ANALYTICS <br />In addition to the data analytics capabilities of the MDMS, there are other third -party applications <br />that are designed to take AMI data and perform higher order analytics to assist the City in <br />forecasting water use, optimizing operations of water production facilities, improving electricity <br />management for pumping stations, and similar capabilities. Some of the MDMS vendors offer <br />advanced water analytics capabilities that are separate from their core MDMS solutions but are <br />designed to allow for easier integration and use. <br />8.5 DATA STORAGE AND SECURITY <br />This is a critical aspect of any information technology project. For AMI systems, security is <br />addressed in several ways. <br />Meter consumption information is securely stored in the meter MTU, requiring a person to have the <br />appropriate tools and authorization to access the meter MTU. The information is then sent across <br />the AMI network in an encrypted fashion; it is not persisted on the network under normal operating <br />conditions for an extended length of time, but is transferred to the AMI HES. The HES, whether on <br />the utility site or hosted, is managed in a secure fashion - both physical and cyber security. <br />Access to the AMI HES, as well as the MDMS will be password -protected and role -based. People can <br />access only the portions of the systems to which they are authorized. The AMI industry has gone to <br />great lengths over the past decade to make the AMI end-to-end systems secure. Additionally, the <br />City's IT Department security practices, architectures, and protocols should be followed. <br />Meter reads and system information is normally maintained in the AMI HES for only 2 to 3 months. <br />The MDMS will normally contain one or more years' worth of interval data, with the exact amount <br />determined by the City data management team. Once the data have aged beyond the time of <br />retention for the MDMS, they are archived to a long-term data repository. This need not be a <br />dedicated data warehouse but can be combined with other City data for long-term storage. <br />25G-156 <br />