Exhibit_A_-_Requirements_Workbook.xlsx
XLSX spreadsheet 72 KB Posted
- Solicitation number
- 2026-RFP-0143
- Issued by
- Los Angeles County, California
About this file
This is a Technical Requirements Workbook for an Advanced Metering Infrastructure (AMI) system and installation services procurement by the City of Pasadena, California, for its water and electric utilities. The document establishes comprehensive technical specifications organized into multiple categories including administration, systems integration, system performance and reliability, software/firmware releases, service levels, security, network performance, equipment requirements, diagnostics, configuration, IoT applications, event/alarm management, endpoints, metering functions, and installation services. Requirements are designated as either Critical or Optional priority levels, with vendors responding through pull-down menu options indicating whether functionality is provided in the current base product, available in a future release, partially compliant, not provided, or not applicable. The workbook contains 306 distinct requirements spanning AMI headend system capabilities, communications network infrastructure, meter hardware specifications, field installation procedures, and integration with the City's Oracle C2M and Oracle Meter Data Management systems.
The requirements encompass sophisticated technical capabilities including 99% or greater success rates for interval reads within 24 hours, 98% success for daily register reads, support for advanced encryption standards with AES 256-bit encryption, SOC 2 Type 2 and ISO 27001 compliance, disaster recovery with maximum 8-hour recovery time objectives, and bi-directional communication capabilities. Water-specific requirements include detection and reporting of backflow events, high-flow leaks, low-flow leaks, and continuous flow leaks with configurable thresholds. Electric-specific requirements address voltage and current monitoring per phase, power quality analysis, time-of-use scheduling with at least four daily time bands, demand reset functionality, and remote disconnect capabilities. Installation services requirements mandate data capture through digital imagery with GPS coordinates, 100% validation of meter reads against photographs, submission of completed work orders within two business days, 1-to-10 supervisor-to-installer ratios, multilingual customer support, and a work order management system accessible to at least twelve utility staff members concurrently with CSV and Excel export capabilities.
View the file
Other files
Show all 20
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Instructions
| Pasadena Water and Power |
| Technical Requirements Workbook |
| Instructions |
• Proposer shall respond to each requirement on each tab (Green) based on the response options provided in the "Proposer Response" column via pull down menu. If additional explanation is required, proposer shall fill out the "Proposer Comment" column.
• A detailed description of each priority set by the utility is provided in the 'Priority' tab. The right is reserved to modify prioritization of requirements at any point and without notice to Proposers.
• A detailed description of each response option is provided in the 'Response Options' tab.
Priority
| Pasadena Water and Power |
| Technical Requirements |
| Priority |
Priority Description
| Critical | This function is of the highest priority to addressing current operational needs at the utility; however, solutions that do not have high priority items in the current base solution will not be disqualified. |
| Optional | This function would be nice to have but does not present an immediate concern to the overall operational or implementation needs of the utility. |
Response Options
| Pasadena Water and Power |
| Technical Requirements |
| Response Options |
Vendor Response Description
| Current Base | The function is provided in the base product today. No modification is required. The pricing proposed encompasses this function. |
| Future Base Release | The function will be provided in a future base release that will be a general release within 18 months from submission of this response. No modification or customization is required, and no additional fees are needed for implementation. Vendor will indicate timing of when desired functionality will be available and make a statement of whether or not the vendor is agreeable to representing this function as a requirement in the final contract. |
| Partially Comply | This function can be supported in some manner by: providing alternative functionality; implementing an additional module; or by modifying an existing screen, existing view, or existing report. The function would not cause a change in the system source code and would not break the system upgrade path. The pricing proposed encompasses this function. A comment must be given explaining how the solution partially complies. |
| Not Provided | This function is not provided by the vendor in the proposed solution. The pricing proposed does not encompass this function. |
| Not Applicable | This function is not relevant due to the specifics of what is being proposed due to underlying technology differences (e.g., a requirement that would only apply to a cellular-based solution whereas the solution proposed is not cellular-based). Those requirements listing this response will be highly scrutinized for appropriateness, and the right is reserved to add or subtract points based on this response, at the discretion of the awarding body. |
AMI FAN
| ID | Category | Commodity | Priority | Requirements | Type | RTM | RF-Based | Proposer Response | Proposer Comment |
| 1 | Administration | All | Critical | Provide administrator tools and a console for the administration and monitoring of the application. | Standard | Yes | No | ||
| 2 | Systems Integration | All | Critical | Be capable of delivering the results of all received alarms, outages, and remote testing and diagnostic results to other systems in near-real time (within 30 seconds of receipt to the AMI headend). | Standard | Yes | No | ||
| 3 | Systems Integration | All | Critical | Be able to initiate an on-demand read request through a real-time interface from another authorized system (i.e., MDMS, CIS, OMS). | Standard | Yes | No | ||
| 4 | Systems Integration | All | Critical | Support scheduled batch loading of meter events to other enterprise IT systems at a configurable frequency, but at least 4 times per day. | Standard | Yes | No | ||
| 5 | Systems Integration | All | Critical | Be capable of securing and delivering register data, interval data, and logs from endpoints and communications network components at a configurable frequency, but at least 4 times per day. | Standard | Yes | No | ||
| 6 | Systems Integration | All | Critical | Support Common Information Model (CIM) structures, commercial enterprise application infrastructure interfaces, and service-oriented integration patterns for IT systems integration with the utility's CIS and other enterprise IT systems. | Standard | Yes | No | ||
| 7 | Systems Integration | All | Critical | Support Multi-Speak communication and protocols for integration with other enterprise IT systems. | Standard | Yes | No | ||
| 8 | System Performance and Reliability | All | Critical | Log all configuration commands and results for a minimum of 90 days. | Standard | Yes | No | ||
| 9 | System Performance and Reliability | All | Critical | Support remote configuration of multiple endpoints in a batched mode, via user-defined batching. | Standard | Yes | No | ||
| 10 | System Performance and Reliability | All | Critical | Support remote configuration of all user-controllable endpoint parameters. | Standard | Yes | No | ||
| 11 | System Performance and Reliability | All | Critical | Record metrology data while communicating and during communication failures. | Standard | Yes | No | ||
| 12 | System Performance and Reliability | All | Critical | Automatically retry commands when a message is not acknowledged. | Standard | Yes | No | ||
| 13 | System Performance and Reliability | All | Critical | Transmit and log the following information for each event: Event Timestamp, Event Type, AMI RF endpoint, and/or meter ID. | Standard | Yes | No | ||
| 14 | System Performance and Reliability | All | Critical | Be capable of receiving and processing incoming meter data on a continuous basis. | Standard | Yes | No | ||
| 15 | System Performance and Reliability | All | Critical | Secure register reads and interval data from unknown meters for which the system has not yet received notice of the AMI meter installation, and automatically store and process these reads once the meter data synchronization completes. | Standard | Yes | No | ||
| 16 | Software/Firmware Releases | All | Critical | Report firmware upgrade status (successful or unsuccessful) to the AMI headend. | Standard | Yes | No | ||
| 17 | Software/Firmware Releases | All | Critical | Log firmware download and upgrade attempts, failures, successes, reversions, etc., with timestamps. | Standard | Yes | No | ||
| 18 | Software/Firmware Releases | All | Critical | Continue normal operation while downloading software/firmware upgrades until instructed to switch to the new version. | Standard | No | No | ||
| 19 | Software/Firmware Releases | All | Critical | Provide a secure capability to perform meter program and firmware updates in the field without removing devices. | Standard | Yes | No | ||
| 20 | Software/Firmware Releases | All | Critical | Accept and install firmware upgrades remotely (over-the-air) via the AMI system in a secure manner. | Standard | Yes | No | ||
| 21 | Software/Firmware Releases | All | Critical | Retain all AMI Meter configuration and program settings, statuses, customer information, and event logs over a full software/firmware upgrade. | Standard | Yes | No | ||
| 22 | Software/Firmware Releases | All | Critical | Have a rollback plan in place and communicate it to the Utility prior to any software upgrades. | Standard | Yes | No | ||
| 23 | Software/Firmware Releases | All | Optional | Allow software releases to be scheduled at the Utility's discretion. | Standard | Yes | No | ||
| 24 | Software/Firmware Releases | All | Critical | Provide release notes prior to updates. | Standard | Yes | No | ||
| 25 | Service Level | All | Critical | Provide, at no cost to the utility, additional network infrastructure to meet network performance SLAs if required beyond originally designed and confirmed by the propagation study. | Standard | Yes | No | ||
| 26 | Service Level | All | Critical | Offer 99.9% uptime for a SaaS or NaaS solution. | Standard | No | No | ||
| 27 | Service Level | All | Critical | Maintain less than 1.50% failure rate per annum for all network communications equipment over the extended operating life of the system. | Standard | No | No | ||
| 28 | Service Level | All | Critical | Maintain less than 0.50% failure rate per annum for all network communications equipment over the required operating life of the system. | Standard | No | No | ||
| 29 | Service Level | All | Critical | Be capable of securing a 95% success rate or greater of all interval reads transmitted within 24 hours of read timestamp, processed at the AMI headend, and available for other systems. | Standard | Yes | No | ||
| 30 | Service Level | All | Critical | Be capable of securing a 98% success rate or greater of daily register reads transmitted within 24 hours of read timestamp, processed at the AMI headend, and available for other systems. | Standard | Yes | No | ||
| 31 | Service Level | All | Critical | Be capable of securing a 99% success rate or greater of daily register reads transmitted within 72 hours of read timestamp, processed at the AMI headend, and available for other systems. | Standard | Yes | No | ||
| 32 | Service Level | All | Critical | Be capable of 99.5% on-demand read success executed within 60 seconds when issued to a single meter. | Standard | Yes | No | ||
| 33 | Security | All | Critical | Be audited and certified under SOC 2 Type 2. | Standard | No | No | ||
| 34 | Security | All | Critical | Be audited and certified under SOC 2 Type 1. | Standard | No | No | ||
| 35 | Security | All | Critical | Be audited and certified under ISO 27001. | Standard | No | No | ||
| 36 | Security | All | Critical | Be compliant to NISTIR 7628 Rev. 1. | Standard | No | No | ||
| 37 | Security | All | Critical | Offer IP filtering for all applications and database access to the Vendor’s environment and to the cloud environment. | Standard | No | No | ||
| 38 | Security | All | Critical | Offer authentication and authorization from the “utility's environment to the Vendor’s environment” and "Vendor’s environment to the cloud-hosted environment” enhanced with SSO and MFA. | Standard | No | No | ||
| 39 | Security | All | Critical | For systems hosted using third-party cloud services, such as AWS, offer a secured, logically separated IT environment in the cloud consistent with the AWS Security Compute Services Whitepaper. | Standard | No | No | ||
| 40 | Security | All | Critical | Offer robust disaster recovery and business continuity solutions with a maximum 8 hours RTO (Recovery Time Objective) (i.e., in the event of a disaster, the services offered by the Vendor shall not exceed 8 hours of downtime). | Standard | No | No | ||
| 41 | Security | All | Critical | Securely encrypt utility's data during the operational process, hosted at rest, and the backup stage, at the Vendor's environment (including Vendor’s contracting organization’s environment). | Standard | No | No | ||
| 42 | Security | All | Critical | Securely transfer/process data between the utility and the Vendor's environment through SITE-TO-SITE VPN communication, enhanced with Multi-Factor Authentication (MFA). | Standard | No | No | ||
| 43 | Security | All | Critical | Provide Network Layer IP filtering solutions to allow access only from the utility's IP address to the remote server environment (especially hosted for the utility). | Standard | No | No | ||
| 44 | Security | All | Critical | Provide automated methods of preventing cross-site scripting (XSS) attacks or SQL injection attacks from compromising databases or software functions. | Standard | No | No | ||
| 45 | Security | All | Critical | Provide a configurable 'choke' to restrict the maximum number of disconnect operations allowed concurrently or on a daily basis, including those disconnect requests transmitted via other systems. | Standard | Yes | No | ||
| 46 | Security | All | Critical | Reject messages/requests that are received from unauthorized systems or devices. | Standard | Yes | No | ||
| 47 | Security | All | Critical | Restrict access to reconfiguration commands based upon user role. | Standard | Yes | No | ||
| 48 | Security | All | Critical | Support 2-factor authentication for system access. | Standard | Yes | No | ||
| 49 | Security | All | Critical | Log unauthorized access attempts. | Standard | Yes | No | ||
| 50 | Security | All | Critical | Provide access control mechanisms (i.e., Identification & Authentication) that prevent unauthorized access to information and resources. | Standard | No | No | ||
| 51 | Security | All | Critical | Provide a security audit store that includes the date and time of the event, event type, subject identity, and the outcome (success or failure) of the event. | Standard | Yes | No | ||
| 52 | Security | All | Critical | Implement mechanisms to audit and store all security-related events, including messages, access, and modification events, for 90 days. | Standard | Yes | No | ||
| 53 | Security | All | Critical | Support functions for secure device authentication, registration, and revocation of registration. | Standard | Yes | No | ||
| 54 | Security | Electric | Critical | Support ANSI C12.19/C12.18/C12.22 cryptographic solutions, including clear text, plain text, and cipher text communication. | Standard | No | No | ||
| 55 | Security | All | Critical | Support configurable rolling encryption keys. | Standard | No | No | ||
| 56 | Security | All | Critical | Support Advanced Encryption Standard (AES) with 256-bit (or higher) end-to-end encryption. | Standard | No | No | ||
| 57 | Security | All | Critical | Implement a configurable lockout mechanism for failed login/access attempts (minimum 3). This applies to the AMI headend application, meter and endpoint configuration products, field tool applications, meters, and endpoints. | Standard | Yes | No | ||
| 58 | Security | All | Critical | Log invalid login attempts and retain 12 months of authentication logs, including both successes and failures. | Standard | No | No | ||
| 59 | Security | All | Critical | Do not store personally identifiable customer information. | Standard | No | No | ||
| 60 | Security | All | Critical | Receive and process data requests from other systems (e.g., MDMS, CIS, OMS). | Standard | Yes | No | ||
| 61 | Distribution Automation | Electric | Critical | Support prioritization of distribution automation traffic over standard metering traffic. | Value-Added | Yes | No | ||
| 62 | Distribution Automation | Electric | Critical | Support communication, configuration, and control of fault indicators, line monitors, voltage/current sensors, capacitor bank controllers, line reclosers, switches, and voltage regulators. | Value-Added | Yes | No | ||
| 63 | Remote Disconnect | Water | Optional | Allow remote connect/disconnect operations to be initiated by authorized applications other than the AMI headend (e.g., MDMS, CIS, SCADA). | Value-Added | Yes | No | ||
| 64 | Remote Disconnect | Water | Optional | Support the identification of emergency and critical needs customers based on CIS information to prevent remote meter/valve disconnect. | Value-Added | Yes | No | ||
| 65 | Remote Disconnect | Water | Optional | Identify and report failed remote connect/disconnect operations. | Value-Added | Yes | No | ||
| 66 | Remote Disconnect | Water | Optional | Enable the retry of failed remote connect/disconnect operations on a configurable basis. | Value-Added | Yes | No | ||
| 67 | Remote Disconnect | Water | Optional | Provide the meter/valve disconnect switch state (i.e., open/closed) and last read after a remote connect/disconnect command is executed. | Value-Added | Yes | No | ||
| 68 | Remote Disconnect | Water | Optional | Provide the capability to perform an on-demand meter/valve remote connect/disconnect with a latency of no more than 10 minutes. | Value-Added | Yes | No | ||
| 69 | Remote Disconnect | Water | Optional | Provide the capability to perform meter/valve remote connect/disconnect operations. | Value-Added | Yes | No | ||
| 70 | IoT Applications | Electric | Critical | Provide a platform for distributed energy resources, demand response, load management, and distribution automation endpoint devices. | Value-Added | Yes | No | ||
| 71 | IoT Applications | Electric | Optional | Provide a platform for streetlight monitoring and control. | Value-Added | Yes | No | ||
| 72 | IoT Applications | Water | Optional | Provide a platform capable of bi-directional communication from remote disconnect devices, including valves and/or meters. | Value-Added | No | No | ||
| 73 | IoT Applications | Water | Optional | Be capable of transmitting and receiving data from water monitoring devices/sensors, such as those for pressure, temperature, lead detection, and water quality, at the headend. | Value-Added | Yes | No | ||
| 74 | Network Performance and Reliability | All | Critical | Provide coverage for 100% of the current meter population represented and cover infill areas within the bounds of the current meter footprint. | Standard | No | Yes | ||
| 75 | Network Performance and Reliability | All | Critical | Provide redundant communication pathways such that there is no single point of failure if a network asset is rendered inoperable. | Customized | No | Yes | ||
| 76 | Network Performance and Reliability | All | Critical | Perform data flow control after communication or power outages to prevent resource overload. | Standard | No | Yes | ||
| 77 | Network Performance and Reliability | All | Critical | Automatically select redundant communication paths if available. | Standard | No | Yes | ||
| 78 | Network Performance and Reliability | All | Critical | Uniquely identify all endpoints and communication devices on the system. | Standard | No | No | ||
| 79 | Network Performance and Reliability | All | Critical | Support full two-way communication from metering endpoint devices to the headend system. | Standard | No | No | ||
| 80 | Network Performance and Reliability | All | Critical | Support full two-way communication across the communications network (LAN, WAN, and Backhaul). | Standard | No | No | ||
| 81 | Network Performance and Reliability | All | Critical | Meet all applicable Federal, State, and local regulatory requirements (including, but not limited to, Federal Communications Commission (FCC Title 47 C.F.R, Part 15 - Radio Frequency Devices), and applicable standards by the American National Standards Institute (ANSI)). | Standard | No | No | ||
| 82 | Network Equipment | All | Critical | Provide network equipment capable of connecting to main voltages ranging from 120V to 480V with a tolerance of +/- 10%. | Standard | No | Yes | ||
| 83 | Network Equipment | All | Critical | Provide network equipment that utilizes non-volatile memory for storing, collecting, transmitting, and retaining data. | Standard | No | Yes | ||
| 84 | Network Equipment | All | Critical | Provide network equipment that complies with electrostatic discharge conditions specified in 61000-4-2. | Standard | No | Yes | ||
| 85 | Network Equipment | All | Critical | Provide network equipment that complies with surge conditions specified in ANSI C37.90.1 and ANSI C62.41. | Standard | No | Yes | ||
| 86 | Network Equipment | All | Critical | Provide network equipment that complies with humidity conditions specified in ANSI 12.20 and 5.4.3.18. | Standard | No | Yes | ||
| 87 | Network Equipment | All | Critical | Provide network equipment that complies with operating shock conditions specified in IEC 68-2-27. | Standard | No | Yes | ||
| 88 | Network Equipment | All | Critical | Provide network equipment that complies with operating vibration conditions specified in IEC 68-2-6. | Standard | No | Yes | ||
| 89 | Network Equipment | All | Critical | Provide network equipment that operates in temperatures between -40 and +85 degrees Celsius. | Standard | No | Yes | ||
| 90 | Network Equipment | All | Critical | Support backhaul communications on network infrastructure components, including Ethernet, fiber, and cellular. | Standard | No | Yes | ||
| 91 | Network Equipment | All | Critical | Utilize secure communications with all authorized systems and devices, including access ports, wireless communications (such as Bluetooth), field servicing tools, and communications to network infrastructure devices. | Standard | No | Yes | ||
| 92 | Network Equipment | All | Critical | Provide the ability to run on solar power for network components. | Standard | No | Yes | ||
| 93 | Network Equipment | All | Critical | Provide a battery backup for network components (collectors, repeaters, etc.) with a runtime of at least 24 hours. | Standard | No | Yes | ||
| 94 | Network Equipment | All | Critical | Provide notification of outage of network equipment. | Standard | No | Yes | ||
| 95 | Network Equipment | All | Critical | Provide reporting on backup battery level. | Standard | No | Yes | ||
| 96 | Network Diagnostics | All | Critical | Support configurable alert levels and notifications based on the severity of detected issues and the number of affected endpoints. | Standard | Yes | No | ||
| 97 | Network Diagnostics | All | Critical | Send non-usage messages and alarms to the AMI headend containing a date/time stamp from the internal meter clock, message code/type, and meter identifier. | Standard | Yes | No | ||
| 98 | Network Diagnostics | All | Critical | Export meter data upon request and provide capabilities to export log data. | Standard | Yes | No | ||
| 99 | Network Diagnostics | All | Critical | Provide on-demand reports containing key diagnostics and statistics from endpoints, devices, and field communication network elements, including event/transaction status reports, trouble reports, and additions/removals. | Standard | Yes | Yes | ||
| 100 | Network Diagnostics | All | Critical | Log the results of all remote testing and diagnostic activities and any automatic actions taken based on those results. | Standard | Yes | Yes | ||
| 101 | Network Diagnostics | All | Critical | Provide mechanisms for remotely correcting system/component issues, including the ability to remotely recycle (or restart) a component. | Standard | Yes | Yes | ||
| 102 | Network Diagnostics | All | Critical | Remotely detect network communication issues, including loss of redundant communication paths, diminishing signal strength, or poor performance. | Standard | Yes | Yes | ||
| 103 | Network Diagnostics | All | Optional | Provide managed services from a vendor-operated remote Network Operations Center for a hosted solution. Managed services will include, at a minimum, alerting of network health issues and remote troubleshooting services for network component maintenance/repair. | Standard | Yes | Yes | ||
| 104 | Network Diagnostics | All | Critical | Support a remotely or locally initiated test for communication connection status. Local diagnostics will include the capability to perform a “ping” and obtain network interface and link information, network association status, and signal level status. | Standard | Yes | Yes | ||
| 105 | Network Diagnostics | All | Critical | Make diagnostic log information available on-demand or through regular reporting. | Standard | Yes | Yes | ||
| 106 | Network Diagnostics | All | Critical | Log communication performance and report it regularly. | Standard | Yes | Yes | ||
| 107 | Network Diagnostics | All | Critical | Detect, log, and report microprocessor failure. | Standard | Yes | Yes | ||
| 108 | Network Diagnostics | All | Critical | Detect, log, and report excessive device temperature. | Standard | Yes | Yes | ||
| 109 | Network Diagnostics | All | Critical | Detect, log, and report communication link failure. | Standard | Yes | Yes | ||
| 110 | Network Diagnostics | All | Critical | Detect, log, and report power supply or battery failure/degradation. | Standard | Yes | Yes | ||
| 111 | Network Diagnostics | All | Critical | Detect, log, and report program or memory failure. | Standard | Yes | Yes | ||
| 112 | Network Configuration | All | Critical | Display and log communication network check results on all installed interfaces. | Standard | Yes | Yes | ||
| 113 | Network Configuration | All | Critical | Display and log configuration parameters. | Standard | Yes | Yes | ||
| 114 | IoT Interfaces and Gateways | All | Optional | Have the ability to use an alternate method for capturing sampling reads when unable to do so using the fixed network. | Value-Added | Yes | No | ||
| 115 | IoT Interfaces and Gateways | All | Optional | Have the ability to time-stamp and align sampling intervals as follows: a) for hourly intervals, on the hour; b) for 15-minute intervals, on the 15, 30, 45, and 60-minute clock positions. | Value-Added | Yes | No | ||
| 116 | IoT Interfaces and Gateways | All | Optional | Support configurable data sampling intervals, with a minimum of 15-minute intervals. | Value-Added | Yes | No | ||
| 117 | IoT Interfaces and Gateways | All | Optional | Be capable of sending all stored data over the AMI network when queried by an on-demand data request. | Value-Added | Yes | No | ||
| 118 | IoT Interfaces and Gateways | All | Optional | Be capable of receiving configuration changes and on-demand data requests over the AMI network for third-party devices. | Value-Added | Yes | No | ||
| 119 | IoT Interfaces and Gateways | All | Optional | Be designed to have a failure rate of less than 0.5% per year. | Value-Added | Yes | No | ||
| 120 | IoT Interfaces and Gateways | All | Optional | Be designed and constructed, excluding its replaceable battery, to have a life expectancy of at least 5 years. | Value-Added | Yes | No | ||
| 121 | IoT Interfaces and Gateways | All | Optional | Store hourly sampled data, including date and time stamps, for a minimum of 45 days in module memory. | Value-Added | Yes | No | ||
| 122 | IoT Interfaces and Gateways | All | Optional | Be capable of transmitting all collected sensor data over the AMI network at configurable intervals, with a minimum of hourly. | Value-Added | Yes | No | ||
| 123 | IoT Interfaces and Gateways | All | Optional | Be battery powered. | Value-Added | No | No | ||
| 124 | IoT Interfaces and Gateways | All | Optional | Read digital sensor inputs. | Value-Added | Yes | No | ||
| 125 | IoT Interfaces and Gateways | All | Optional | Read at least one 4-20 mA, 2-wire analog input from a sensor device. | Value-Added | Yes | No | ||
| 126 | Event/Alarm Management | All | Optional | Be able to display events and alarms on a map view. | Standard | Yes | No | ||
| 127 | Event/Alarm Management | Water | Critical | Detect, timestamp, and report backflow events. | Standard | Yes | No | ||
| 128 | Event/Alarm Management | Water | Critical | Detect, timestamp, and report high flow leaks or burst events based on a nominal value threshold. | Standard | Yes | No | ||
| 129 | Event/Alarm Management | Water | Critical | Detect, timestamp, and report low-flow leaks where some intervals may be zero. | Standard | Yes | No | ||
| 130 | Event/Alarm Management | Water | Critical | Detect, timestamp, and report continuous flow leaks based on a nominal value threshold. | Standard | Yes | No | ||
| 131 | Event/Alarm Management | Electric | Critical | Monitor the voltage of individual meters and allow comparisons of voltage between meters, including meters placed at the start of feeders or at transformers. | Standard | Yes | No | ||
| 132 | Event/Alarm Management | Electric | Critical | Monitor voltage, current per phase, and phase angles to detect incorrect polarity per phase or incorrect phase sequencing on poly-phase meters. | Standard | Yes | No | ||
| 133 | Event/Alarm Management | Electric | Critical | Be capable of configuring an alarm to be sent based on a defined number of sag/swell cycles. | Standard | Yes | No | ||
| 134 | Event/Alarm Management | Electric | Critical | Detect, date, and time-stamp voltage deviation events, such as high/low voltages, sags, and swells, with durations and magnitudes defined by programmable thresholds. | Standard | Yes | No | ||
| 135 | Event/Alarm Management | Electric | Critical | Detect, timestamp, and report the restoration of power, defined as the presence of line-side voltage within some percentage of nominal voltage for more than a programmable number of continuous seconds (nominally 60 seconds). | Standard | Yes | No | ||
| 136 | Event/Alarm Management | Electric | Critical | Detect, timestamp, and report the loss of power, defined as the reduction of line-side voltage by at least some percentage of nominal voltage for a programmable number of continuous seconds (nominally 60 seconds). | Standard | Yes | No | ||
| 137 | Event/Alarm Management | All | Critical | Detect and log access by any field device (e.g., optical port, Bluetooth connection, etc.). | Standard | No | No | ||
| 138 | Event/Alarm Management | All | Critical | Automatically resend event notifications until the message is acknowledged by the AMI headend. | Standard | Yes | No | ||
| 139 | Event/Alarm Management | All | Critical | Be capable of reporting low-priority messages within one-hundred twenty seconds 90% of the time. | Standard | Yes | No | ||
| 140 | Event/Alarm Management | All | Critical | Be capable of reporting medium-priority messages within sixty seconds 90% of the time. | Standard | Yes | No | ||
| 141 | Event/Alarm Management | All | Critical | Be capable of reporting high-priority messages within thirty seconds 90% of the time. | Standard | Yes | No | ||
| 142 | Event/Alarm Management | All | Critical | Support the ability to configure whether an event/alarm is transmitted instantaneously or with a regularly scheduled batch of readings and event data. | Standard | Yes | No | ||
| 143 | Event/Alarm Management | All | Critical | Support user-defined prioritization of events to allow critical traffic to take priority. | Standard | Yes | No | ||
| 144 | Event/Alarm Management | All | Critical | Support user-defined local thresholds (i.e., thresholds by individual meter or batch of meters) for alarms/events based on nominal values. | Standard | Yes | No | ||
| 145 | Event/Alarm Management | All | Critical | Support user-defined global thresholds (i.e., thresholds for all meters) for alarms/events based on nominal values. | Standard | Yes | No | ||
| 146 | Event/Alarm Management | All | Critical | Detect, timestamp, and report reverse flow on meters not operating as net or bi-directional meters. | Standard | Yes | No | ||
| 147 | Event/Alarm Management | All | Critical | Detect, timestamp, and report rollover events. | Standard | Yes | No | ||
| 148 | Event/Alarm Management | All | Critical | Detect, timestamp, and report stopped/dead/non-registering meters. | Standard | Yes | No | ||
| 149 | Event/Alarm Management | Electric | Critical | Detect, timestamp, and report meter tilt/tamper for meters with the capability to detect tilt. | Standard | Yes | No | ||
| 150 | Event/Alarm Management | All | Critical | Detect, timestamp, and report the removal of an endpoint (cut wire). | Standard | Yes | No | ||
| 151 | Event/Alarm Management | All | Critical | Allow for configuration or custom events or alarms based on analytics or calculations (e.g., continuous consumption) rather than a report. | Standard | Yes | No | ||
| 152 | Event/Alarm Management | All | Critical | Store all events and alarms for display to the user and for analysis using queries and reports. | Standard | Yes | No | ||
| 153 | Event/Alarm Management | All | Critical | Have the ability to forward selected events or alarms, once received, to another application as necessary to support distribution operations and monitoring. | Standard | Yes | No | ||
| 154 | Event/Alarm Management | All | Optional | Provide a mechanism to automatically communicate a certain event and/or alarm to designated recipients via SMS. | Standard | Yes | No | ||
| 155 | Event/Alarm Management | All | Critical | Provide a mechanism to automatically communicate a certain event and/or alarm to designated recipients via email. | Standard | Yes | No | ||
| 156 | Event/Alarm Management | All | Critical | Be configurable to analyze received events and alarms and initiate the creation of service orders or other exceptions. | Standard | Yes | No | ||
| 157 | Event/Alarm Management | All | Critical | Identify or flag events/alarms that require further investigation or field resolution. | Standard | Yes | No | ||
| 158 | Endpoints | Water | Critical | Keep time even if there is no communication with the AMI system. | Standard | Yes | No | ||
| 159 | Endpoints | Water | Critical | Provide security/authentication for local AMI meter data exchange to ensure that data exchanges can only be executed by authorized users or users authorized with designated field tools. | Standard | No | No | ||
| 160 | Endpoints | Water | Critical | Support local data exchange of all AMI communications data and logs. | Standard | No | No | ||
| 161 | Endpoints | Water | Critical | Be supplied with a scannable bar code label affixed to the endpoint. | Standard | No | No | ||
| 162 | Endpoints | Water | Critical | Be rated for performance of at least IP68 conditions or better. | Standard | No | No | ||
| 163 | Endpoints | Water | Critical | Be designed and constructed to have a life expectancy of at least 20 years. | Standard | Yes | No | ||
| 164 | Endpoints | Water | Critical | Store interval data and daily read data, including date and time stamps, for a minimum of 45 days in module memory for 15-minute interval data. | Standard | Yes | No | ||
| 165 | Endpoints | Water | Critical | Be designed to have a failure rate of less than 0.5% per year. | Standard | No | No | ||
| 166 | Endpoints | Water | Critical | Report an estimate battery life through voltage measurements. | Standard | No | No | ||
| 167 | Endpoints | All | Critical | Provide a means for extracting stored data directly from the device in the event of network communications or equipment failure. | Standard | Yes | No | ||
| 168 | Endpoints | Water | Optional | Have the ability to capture reads via an alternate method when unable to do so using the fixed network. | Standard | Yes | No | ||
| 169 | Endpoints | Water | Critical | Have the ability to time-stamp and align intervals in accordance with: a) for hourly intervals, on the hour; b) for 15-minute intervals, on the 15, 30, 45, and 60-minute clock positions. | Standard | Yes | No | ||
| 170 | Endpoints | Water | Critical | Be capable of configuring endpoints to deliver either hourly or 15-minute interval reads. | Standard | Yes | No | ||
| 171 | TOU | Electric | Optional | Be capable of exporting TOU register readings along with interval data and other register readings. | Value-Added | Yes | No | ||
| 172 | TOU | Electric | Optional | Be capable of retrieving and storing TOU registers. | Value-Added | Yes | No | ||
| 173 | TOU | Electric | Optional | Be capable of implementing over-the-air updates of TOU schedules to electric meters belonging to specific program groups. | Value-Added | Yes | No | ||
| 174 | TOU | Electric | Optional | Support at least 4 separate daily time bands for TOU schedules (e.g., on peak, off peak, mid peak, and shoulder peaks). | Value-Added | Yes | No | ||
| 175 | TOU | Electric | Optional | Provide the capability to create and maintain Time of Use schedules (at least 10) for enabling and updating TOU schedules in electric meters. | Value-Added | Yes | No | ||
| 176 | Remote Disconnect | Electric | Optional | Be available with a button or lever to enable the service disconnect switch to close when the "Arm to Connect" option is used for reconnecting service remotely for residential meters. | Value-Added | Yes | No | ||
| 177 | Remote Disconnect | Electric | Optional | Be available with an optional service disconnect switch capable of interrupting up to 320 amps. | Value-Added | Yes | No | ||
| 178 | Remote Disconnect | Electric | Optional | Be available with an optional service disconnect switch capable of interrupting up to 200 amps for residential meters (Form 2S class 320 meters excepted). | Value-Added | Yes | No | ||
| 179 | Load Limiting | Electric | Optional | Be able to send an acknowledgement of the current state of load limiting status for load-limiting supported meters. | Value-Added | Yes | No | ||
| 180 | Load Limiting | Electric | Optional | Be able to accept and process a remote load limiting command from the AMI Head-end system for load-limiting supported meters. | Value-Added | Yes | No | ||
| 181 | Load Limiting | Electric | Optional | Have the ability to support current/load limiting functionality for residential disconnect meters. | Value-Added | Yes | No | ||
| 182 | Electric Meters | Electric | Optional | Be available with an optional grid edge applications. | Value-Added | Yes | No | ||
| 183 | Electric Meters | Electric | Critical | Keep time even if there is no communication with the AMI system. | Standard | Yes | No | ||
| 184 | Electric Meters | Electric | Critical | Provide electric meters with FLEX-TITE ULTIMATE AMI Jointed Meter Locking Ring, color-coded green or blue based on self-contained or instrument-rated meters, respectively. | Customized | No | No | ||
| 185 | Electric Meters | Electric | Critical | Provide blue electric meter seals with a barcode and “PWP AMI” imprinted on it. | Customized | No | No | ||
| 186 | Electric Meters | Electric | Critical | Provide security/authentication for local AMI meter data exchange to ensure that data exchanges can only be executed by authorized users or users authorized with designated field tools. | Standard | Yes | No | ||
| 187 | Electric Meters | Electric | Critical | Provide a field tool and related software for diagnostic purposes, enabling the downloading of register and interval data from meters/endpoints as well as updating meter programs and firmware. | Standard | Yes | No | ||
| 188 | Electric Meters | Electric | Critical | Provide an electronic vendor meter inventory file with meter deliveries. | Standard | Yes | No | ||
| 189 | Electric Meters | Electric | Critical | Be supplied with a scannable manufacturer serial number bar code label, including the electric meter number, affixed to the meter faceplate. | Standard | Yes | No | ||
| 190 | Electric Meters | Electric | Critical | Provide an event denoting the date and time when field access was performed or attempted. | Standard | Yes | No | ||
| 191 | Electric Meters | Electric | Critical | Provide an instantaneous voltage reading on demand and maximum/minimum voltage readings for interval data. | Standard | Yes | No | ||
| 192 | Electric Meters | Electric | Critical | Provide an instantaneous amperage reading on demand and maximum amperage for interval data. | Standard | Yes | No | ||
| 193 | Electric Meters | Electric | Critical | Provide phase angle measurements, both positive (leading angle) and negative (lagging angle), for three-phase meters. | Standard | Yes | No | ||
| 194 | Electric Meters | Electric | Critical | Be capable of identifying service type/form factor. | Standard | Yes | No | ||
| 195 | Electric Meters | Electric | Critical | Store interval data and daily read data, including date and time stamps, for a minimum of 45 days in module memory for 15-minute interval data. | Standard | Yes | No | ||
| 196 | Electric Meters | Electric | Critical | Provide amperage per phase. | Standard | Yes | No | ||
| 197 | Electric Meters | Electric | Critical | Provide voltage per phase. | Standard | Yes | No | ||
| 198 | Electric Meters | Electric | Critical | For commercial meters, provide load profile register/interval data for the following units of measure in configurable 5, 15, 30, and 60-minute intervals with time stamps: max demand, kVAR, PF, kWh delivered, kWh received, kW delivered, kW received, kVARh delivered, kVARh received, kVA delivered, and voltage. | Customized | Yes | No | ||
| 199 | Electric Meters | Electric | Critical | For bellwether metering to support conservation voltage reduction, support 1-minute voltage profiling transmitted in 5-minute intervals. | Value-Added | Yes | No | ||
| 200 | Electric Meters | Electric | Critical | For residential meters, provide load profile register/interval data for the following units of measure in configurable 15, 30, and 60-minute intervals with time stamps: max demand, kVAR, PF, kWh delivered, kWh received, kW delivered, kW received, kVARh delivered, kVARh received, kVA delivered, and voltage. | Customized | Yes | No | ||
| 201 | Electric Meters | Electric | Critical | Be available to retrofit with a KYZ pulse output board without limiting AMI functionality for three-phase meters. | Standard | Yes | No | ||
| 202 | Electric Meters | Electric | Critical | Be able to support remote configuration of the kW read interval. | Standard | Yes | No | ||
| 203 | Electric Meters | Electric | Critical | Be able to support remote configuration of the kWh read interval. | Standard | Yes | No | ||
| 204 | Electric Meters | Electric | Critical | Be capable of operating at its maximum rated load without overflowing the interval data counter, regardless of the selected interval length. | Standard | Yes | No | ||
| 205 | Electric Meters | Electric | Critical | Log a date/time stamped event when an operation occurs, with a message to communicate success or failure, for meters with service disconnect switches. | Standard | Yes | No | ||
| 206 | Electric Meters | Electric | Critical | Perform a diagnostic self-test upon startup and, in the event of errors or warnings, report the error on the meter display and provide notification back to the AMI headend. | Standard | Yes | No | ||
| 207 | Electric Meters | Electric | Critical | Have sensors to detect hot socket/overvoltage and temperature. | Standard | Yes | No | ||
| 208 | Electric Meters | Electric | Critical | Support bi-directional (net) electric flow metering for the measurement and collection of delivered and received real and reactive energy consumption, demand, interval data, and time of use. | Standard | Yes | No | ||
| 209 | Electric Meters | Electric | Critical | Support configurable display registers with at least 6 digits plus 2 decimals. | Standard | Yes | No | ||
| 210 | Electric Meters | Electric | Critical | Report power factor at the time of each: peak kW, peak kVA, and peak kVAR. | Standard | Yes | No | ||
| 211 | Electric Meters | Electric | Critical | Provide a time stamp with the peak demand recorded for the period set in the metrology of the meter, for demand-enabled meters. | Standard | Yes | No | ||
| 212 | Electric Meters | Electric | Critical | Deliver the daily peak demand value and reset the demand register after midnight each day. | Value-Added | Yes | No | ||
| 213 | Electric Meters | Electric | Optional | Be able to accept and process a remote demand reset command from the AMI headend system >99% of the time. | Standard | Yes | No | ||
| 214 | Electric Meters | Electric | Optional | Remotely reset the meter peak demand register on the scheduled day for off-cycle events, such as move-in or move-out. | Standard | Yes | No | ||
| 215 | Electric Meters | Electric | Optional | Automatically reset the meter peak demand register on the billing cycle date, configurable to the utility's billing calendar. | Standard | Yes | No | ||
| 216 | Electric Meters | Electric | Critical | Be configurable to record 5-minute, 15-minute, 30-minute, and 60-minute demand values, either on a block or rolling basis. | Value-Added | Yes | No | ||
| 217 | Electric Meters | Electric | Critical | Send acknowledgement to the AMI headend when the demand reset function has been performed, along with the time stamp of the reset. | Standard | Yes | No | ||
| 218 | Electric Meters | Electric | Critical | Provide "lasp gasp" transmission for outages. | Standard | Yes | No | ||
| 219 | Functionality | Electric | Critical | Support a configurable parameter for differentiating between a sustained outage (e.g., one minute or greater) and a blink outage (e.g., < 1 minute). | Standard | Yes | No | ||
| 220 | Functionality | All | Critical | Support an 8-digit length serial number for meters or endpoints. | Standard | Yes | No | ||
| 221 | Functionality | All | Critical | Support a variety of registers with up to 9 digits on the register read. | Standard | Yes | No | ||
| 222 | Functionality | All | Critical | Support the ability to export report and query data in CSV, SQL, Excel, XML, TXT, or other flat-file formats. | Standard | Yes | No | ||
| 223 | Functionality | All | Optional | Provide the capability to assign internal user-specific screen presentation criteria (i.e., personalized home dashboard) based on user sign-in (role-based presentation). | Value-Added | Yes | No | ||
| 224 | Functionality | All | Critical | Process leap year changes across system devices. | Standard | Yes | No | ||
| 225 | Functionality | All | Critical | Process Standard Time and Daylight Savings Time changes across system devices. | Standard | Yes | No | ||
| 226 | Functionality | All | Critical | Log each instance when an event message has been sent to an AMI component, but no acknowledgement is received within the configured time frame. | Standard | Yes | No | ||
| 227 | Functionality | All | Critical | Log all messages sent to and received from all AMI components, including message date/time, event/message type identifier, and source/target(s) identifier. | Standard | Yes | No | ||
| 228 | Functionality | All | Critical | Track devices with missing data due to failed or incomplete communications and provide an automatic retry process to ensure multiple efforts are made to capture missing interval data for endpoints. | Standard | Yes | No | ||
| 229 | Functionality | All | Critical | Be able to distinguish between a missing interval and zero consumption and provide reporting capability for missing data or gaps. | Standard | Yes | No | ||
| 230 | Functionality | All | Critical | Be capable of performing on-demand read requests to retrieve events, usage, and register data. | Standard | Yes | No | ||
| 231 | General | All | Critical | Provide a minimum of 12 months of online storage for all AMI endpoint data collected. | Standard | No | No | ||
| 232 | General | All | Critical | Have a non-proprietary database file structure that is ODBC-compliant and SQL-compliant, provided by a standard commercial database supplier. | Standard | No | No | ||
| 233 | General | All | Critical | Provide context-sensitive system documentation for online user help. | Standard | Yes | No | ||
| 234 | General | All | Critical | Provision separate production and test environments, both fully integrated, for the AMI headend system for the duration of the contract. | Customized | Yes | No | ||
| 235 | General | All | Critical | Provide separate production and test environments, both fully integrated, for the AMI headend system prior to go-live. | Customized | Yes | No | ||
| 236 | Administration | All | Critical | Have the capability to automatically perform a last read of interval and register data before a configuration update is performed. | Standard | Yes | No | ||
| 237 | Administration | All | Critical | Support automatic and/or programmatic discovery of communications equipment (repeaters, collectors/concentrators, etc.). | Standard | Yes | Yes | ||
| 238 | Administration | All | Critical | Support automatic discovery of all new endpoint devices. | Standard | Yes | No | ||
| 239 | Administration | Electric | Critical | Support power status verification for electric meters by meter/customer or batch of meters/customers, via the user interface. | Standard | Yes | No | ||
| 240 | Administration | All | Critical | Be capable of remotely correcting system/component problems, including the ability to remotely recycle (or restart) a component. | Standard | Yes | Yes | ||
| 241 | Administration | All | Critical | Be capable of remotely detecting network communications problems, including loss of redundant communications pathways, diminishing signal strength, or poor interval performance. | Standard | Yes | Yes | ||
| 242 | Administration | All | Critical | Support centralized remote management, monitoring, graphical monitoring, and control of all endpoint hardware. | Standard | Yes | No | ||
| 243 | Administration | All | Critical | Support centralized remote management, monitoring, graphical monitoring, and control of all network hardware. | Standard | Yes | Yes | ||
| 244 | Administration | All | Critical | Collect all interval data and logs from meters and communications network components at a configurable frequency, but at least once per day. | Standard | Yes | No | ||
| 245 | Administration | All | Critical | Have the ability to archive and purge data according to a data strategy. | Standard | No | No | ||
| 246 | Administration | All | Critical | Provide tools or applications for users to create and export custom reports. | Standard | Yes | No | ||
| 247 | Administration | All | Critical | Provide export of all interval and register usage data, alarms, and events. | Standard | Yes | No | ||
| 248 | General | All | Critical | Accept and store customer account and meter data characteristics (e.g., Meter ID, Parcel ID, account number, account address, etc.) according to the CIS data structure. | Standard | Yes | No | ||
| 249 | General | Water | Critical | Support the units of measure: cubic feet. | Customized | Yes | No | ||
| 250 | General | Electric | Critical | Support the units of measure (delivered and received): kW, kWh, kVAR, kVARh, PF, max demand, voltage, kVA. | Customized | Yes | No | ||
| 251 | Event/Alarm Management | All | Critical | Process meter-related issues, including, at a minimum: meters with missing reads and unknown meters. | Standard | Yes | No | ||
| 252 | Event/Alarm Management | All | Critical | Process consumption-related issues, including, at a minimum: meter rollover, consumption on a vacant account, zero consumption on an active account, and high and low usage. | Standard | Yes | No | ||
| 253 | Event/Alarm Management | All | Critical | Allow for the configuration of high and low usage exception thresholds. | Standard | Yes | No | ||
| 254 | Event/Alarm Management | All | Critical | Allow high and low usage exception thresholds to be set based on customer parameters (e.g., customer class). | Standard | Yes | No | ||
| 255 | Event/Alarm Management | All | Optional | Allow for tolerances in the high and low usage exception thresholds based on weather. | Standard | Yes | No | ||
| 256 | Event/Alarm Management | All | Critical | Allow for configurable event notifications based on business rules (e.g., if a meter has not generated reads within X number of days). | Standard | Yes | No | ||
| 257 | Administration | All | Critical | Accept register reads via manual entry. | Standard | Yes | No | ||
| 258 | Administration | All | Critical | Allow for configuration by an authorized user, without the need for new code development, for the following validation parameters: type of service, meter type, customer, customer group, billing cycle, and rate category. | Standard | Yes | No | ||
| 259 | Administration | All | Critical | Process Daylight Savings Time changes. | Standard | Yes | No | ||
| 260 | Administration | All | Critical | Track meter events by billing account (e.g., flags, relocation, reconfiguration, tampering, etc.). | Standard | Yes | No | ||
| 261 | Billing | All | Critical | Align billing usage to start on the same date each month for coincident billing (i.e., align with the billing period and billing calendar set at the utility). | Standard | Yes | No | ||
| 262 | Billing | All | Critical | Upon request by the CIS for specified accounts and start/end dates, provide the configured billing determinants for each account. | Standard | Yes | No | ||
| 263 | Billing | All | Critical | Provide a tool to analyze and classify customers based on actual usage patterns, rather than nominal customer class. | Standard | Yes | No | ||
| 264 | Billing | All | Critical | Store raw reads, validated (via VEE) reads, and calculated billing determinants. | Standard | Yes | No | ||
| 265 | Billing | All | Critical | Allow export of raw reads, VEE reads, and calculated billing determinants in a standard file format (e.g., CSV, XLS, etc.). | Standard | Yes | No | ||
| 266 | Billing | Electric | Critical | If daily demand is reset at the electric meter, for each billing request for rates with a demand determinant, select the highest daily demand value for the billing period, for the specified meter, and deliver the demand value and corresponding date. | Standard | Yes | No | ||
| 267 | Administration | All | Critical | Validate newly provisioned AMI meters to ensure they are properly configured and communicating correctly. | Standard | Yes | No | ||
| 268 | Reporting | Electric | Optional | Support net metering by combining separate service and production meter readings for a solar account. | Standard | Yes | No | ||
| 269 | VEE | All | Optional | Have the ability to automatically validate register reads and interval data received from AMI meters to identify missing or invalid data using configurable validation rules. | Standard | Yes | No | ||
| 270 | VEE | All | Optional | Have the ability to automatically estimate missing or invalid register reads and interval data using configurable estimation rules. | Standard | Yes | No | ||
| 271 | VEE | All | Optional | Clearly identify any sets of reads or data requiring manual verification or editing to the user. | Standard | Yes | No | ||
| 272 | VEE | All | Optional | Provide a user interface and tools for viewing, verifying, and modifying register reads and interval data. | Standard | Yes | No | ||
| 273 | VEE | All | Optional | Receive, process, and store register reads and interval data from AMI meters where data was previously identified as missing and estimated, without deleting any previously received or estimated data. | Standard | Yes | No | ||
| 274 | VEE | All | Optional | Have the ability to identify scenarios where estimated data is used for billing and, subsequently, actual read data is received, ensuring both the estimate and actual are stored. | Standard | Yes | No | ||
| 275 | VEE | All | Optional | Do not overwrite, replace, or version valid data with estimated data unless the replacement occurs through a manual process. | Standard | Yes | No | ||
| 276 | VEE | All | Optional | Identify reads or data that require manual verification or editing and provide a user interface for verifying and modifying register reads and interval data, with an audit trail of all changes. | Standard | Yes | No | ||
| 277 | VEE | All | Optional | Have the ability to receive, process, and store reads from external sources (e.g., MV-90, manually captured reads, etc.). | Standard | Yes | No | ||
| 278 | VEE | All | Optional | Have the ability to assign VEE rule sets to each data channel to enable different VEE behavior for different data channels. | Standard | Yes | No | ||
| 279 | VEE | All | Optional | Support the modification of existing VEE rules or creation of new VEE rules. | Standard | Yes | No | ||
| 280 | VEE | All | Optional | Estimate interval data based on the characteristics of the meter. | Standard | Yes | No | ||
| 281 | Operations | All | Optional | Be capable of creating a service request to CIS or a work management system based on meter events and alarms received. | Standard | Yes | No |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .