East Bay Municipal Utility District Request for Information Advanced Metering Infrastructure Technology

Transcription

1 Request for Information Advanced Metering Infrastructure Technology REQUEST East Bay Municipal Utility District (EBMUD) requests technical information about available advanced metering Infrastructure (AMI) systems. EBMUD is planning to select a radio network to address distribution system and customer service needs. EBMUD is interested in a fully automated, 2-way, fixed based system. However, the capability to read systems in drive-by mode is of interest. The system must be able to read meters at least hourly with a battery life of 20 years based on this read frequency. EBMUD is interested in both current and in-development AMI technology that is scheduled to be released in the near future. The RFI should include the number of years equipment has been deployed in the market or, if in development, the scheduled release date. EBMUD works with a number of water utilities. Please let us know if you object to sharing any responses with other utilities that may request results. DEFINITION For the purposes of this Request for Information the following definitions will apply: MIU (Meter Interface Unit): The device which connects to water meters and transmits reads to a collector or repeater. Collector: The device that obtain reads from MIUs and/or repeaters at a permanently installed location. Mobile Data Collector: The device that obtains reads from MIUs in a mobile environment. Repeater: The device that relays radio transmissions from the MIU to the Collector. Server: The computer that accepts data from collectors. Backhaul: The system that transmits signals from collectors to servers. MDMS (Meter Data Management System): System that converts AMI data into a useable form for billing and other applications. SCADA (Supervisory Control and Data Acquisition): Computer system that controls the distribution network. ODBC: Open Database Connectivity: Standard middleware for accessing database systems. IoT (Internet-of-Things): A development of the Internet in which devices have network connectivity. DEADLINE Provide the requested information no later than Friday, October 16, BACKGROUND EBMUD is a large water utility covering approximately 325 square miles, servicing approximately 400,000 meters and a population of approximately 1.3 million people. EBMUD water service currently

2 grows at the rate of approximately 3,000 new meters annually. Refer to the link of EBMUD s service area: EBMUD plans to standardize on one type of AMI communication network. EBMUD plans to grow its AMI deployment over time focusing on areas of highest benefit. REQUESTED INFORMATION In support of this effort, EBMUD requests the following information. While this information is nonbinding, please be as thorough, accurate and clear as possible in the representation of the information. 1. General a. Provide a general description of the AMI technologies you have available and are planning including its current status. b. Indicate whether your AMI system would be considered mesh, star line-of-sight, cellular, power line carrier, or other. c. Indicate whether the system uses licensed or unlicensed frequencies and the frequency range of the network proposed for EBMUD. d. Indicate whether your system is 1-way, 2-way or other, and describe why you have given it that classification. e. Describe all reading modes your system can be configured to read such as walk-by, driveby, fixed network, and cellular. 2. MIU Description a. Provide a general description of the MIU you propose for EBMUD with physical dimensions including height, length, width, and weight. b. Indicate if the MIU antennae is internal or external and how far the antennae can be separated from the meter. c. Describe if multiport MIUs available are capable of reading more than one register. d. Describe the MIU numbering system. How are multiport MIU numbers handled? e. Battery Life. i. What type of battery does the MIU use? ii. What is the anticipated battery life of the MIU? iii. What is the theoretically maximum battery life in the best of conditions? iv. What factors affect the MIU battery life: 1. Temperature: Allowable range. 2. Humidity: Allowable range. 3. Frequency of inbound and outgoing transmissions. 4. Size of transmissions (i.e., bytes). 5. Number of ports. 6. Other factors. 2

3 v. Describe features of the transmitter that prevent corrosion or degradation of mechanical or electrical performance. vi. Is the battery field replaceable? vii. How is battery life calculated? Describe how the system indicates the end-of-battery-life at the battery and system software level. f. Firmware. i. Is the firmware upgradeable, and, if so, how is it upgraded? ii. Can firmware upgrades be performed over the network? iii. Describe the method and past frequently of firmware updates/upgrades. g. MIU transmissions. i. Are multiple communication pathways available such as cellular or IoT connection? ii. Indicate how MIUs can be switched from one mode to another, or if the MIU can communicate on both networks simultaneously. iii. Can MIUs communicate to mobile and fixed collectors? 1. Is a firmware change required to switch between mobile and fixed communication modes? 2. Can the MIU be switched to mobile mode via a collector or is physical contact required? iv. What data is contained in an MIU transmission? For example, alarm codes (list all codes), meter ID, and GIS coordinates. v. Is there a limit on the size of the transmission in bytes? vi. What is typical transmitter range of the MIU? Indicate factors that affect range. vii. What is the MIU standard transmission frequency? 1. How frequently can the MIU be configured to transmit? 2. What are the battery life impacts of transmitting more frequently? 3. Can transmission frequency by adjusted remotely? viii. What is the strength/power of the transmission? ix. Does the transmission power diminish over time? Does decreasing power affect range? Please describe. x. How is the MIU transmission encrypted? What type of encryption is used? What type of cyber security measures are employed at the MIU level? xi. What type of data can be received by the MIU? xii. Describe the communications protocol required by the device. 1. Will the device accept both pulse and encoded signals? 2. Can the device share communications protocols so other meter manufacturers and third party equipment provider devices can be read by your MIUs? xiii. List all encoder-type meters (brand and model) which your system is compatible with. List all encoder-type meters for which your system is NOT capable of reading all the digits on the dial (e.g., truncates or rounds reading). 3

4 1. Indicate any meters that you are not compatible with. xiv. Indicate the number of meter read digits that the MIU can store and transmit. h. What alarm codes can be read and transmitted from the meters (e.g., backflow, empty, high usage). i. Be specific about what meters you can read the codes from. ii. List specific meter models that the MIU are currently reading codes from. iii. Can the MIU be configured to work with different communication standards? i. How frequently can the MIU interrogate meters? i. At what interrogation frequency is battery life significantly affected? ii. Does sampling frequency affect the warranty? j. Describe how flow rate might be recorded and transmitted by the MIU. k. Connector to meters. i. Does the MIU connect to the meter with 2 or 3 wires? ii. Describe the recommended connection between the MIU and the meter register(s), and provisions to prevent misconnection, corrosion or failure. iii. Do you allow a third-party universal connector? If so, which ones have you approved for use with your system? iv. Describe other ways the MIUs can connect with third party meters. l. What factors can be adjusted remotely from the network such as frequency, transmission strength, alarm codes, firmware settings? m. Does the MIU have onboard data storage in the event a collector is unavailable? n. Can lost data be automatically uploaded to the network after re-establishing connection with the collector? o. What is smallest resolution that can be transmitted to the MIU (e.g., 1.0 CF, 0.01 CF)? Indicate any limitations with different manufacturers (e.g., if you can only read high resolution to certain manufacturers). p. Are the communication protocols for the MIUs open and useable by any AMR/AMI or meter manufacturer? Please be specific. 3. MIU Installation a. Describe how MIUs and antennae are installed in the meter box/pit. i. Is the MIU typically installed in pits through lid or under lid? ii. How far above the lid do the MIU antennae protrude? iii. Can the MIU be wall mounted? iv. What are the minimum requirements for the internal dimensions of the meter pit box? v. What are the minimum requirements of the meter pit lid (e.g., material construction, maximum thickness, diameter of hole if required)? b. Describe the device used to program/configure MIUs. i. Does the device have a bar code or RFID reader? 4

5 ii. Does the device have built in GPS? iii. Describe the default operation and troubleshooting features of the handheld device for installation. iv. Describe if the handheld device can be programmed to input additional information such as GPS coordinates or service repair codes (e.g., needs new box) or can take a photo. v. Describe the ability to import/export installation reports. vi. Does the device communicate wirelessly with the server or collector? vii. How far away can an MIU be read by the device? viii. How far away can an MIU be programmed by the device? c. Describe the process to program/configure and install the MIU. i. Describe equipment needed to install MIUs? ii. Can the MIU be programmed from the network? iii. Can the MIU be pre-configured in the factory? iv. Describe how the MIU handles meter exchanges. v. Indicate provisions to avoid installation, connection to meters, and programming mistakes. vi. Can successful installation be verified in the field? vii. Briefly describe procedures that need to be followed to replace failed transmitters. d. Can a meter to be read by more than one MIU or other communication device without affecting the MIU? 4. Collector Description a. Provide a general description of the collector(s) you propose for EBMUD with physical dimensions including height, length, width, and weight. b. Power supply. i. What is the preferred power source and what are the requirements for power supply? ii. Is there a backup power supply? iii. How long is the backup power supply? iv. Is a solar powered option available? c. Collector communications. i. Provide the methods of data backhaul that are available. 1. Are multiple communication pathways available such as cellular or IoT connection? ii. What data is contained in a transmission? For example, meter reads and alarm codes, collector operation data, signal strength, etc. iii. Is there a limit on the size of the transmission in bytes? iv. What is the strength/power of the transmission? v. Does the transmission power diminish over time? Does decreasing power affect range? Please describe. 5

6 vi. How is the transmission encrypted? What type of encryption is used? What type of cyber security measures are employed at the collector level? vii. What type of data can be received by the collector? viii. Describe the communications protocol required by the device. 1. Are the communication protocols for the collectors open and useable by any AMR/AMI or meter? 2. Will the collector accept signals from third party devices? 3. Can the collector share communications protocols so other AMI manufacturers and third party equipment provider devices can be read by your collector? ix. How frequently can the collectors interrogate MIUs? x. What factors can be adjusted remotely from the server such as frequency, transmission strength, alarm codes, firmware settings? xi. Does the collector have onboard data storage in the event communication with a server is unavailable? 1. If so, how many meter reads and alarm codes can be stored. 2. Can lost data be automatically uploaded to the network after re-establishing connection with the server? d. Describe environmental tolerances for the collector equipment (e.g., temperature, humidity, vibration, wind). e. Provide recommended maintenance requirements. f. What is the power output and typical transmission range of the device (identify any circumstances that would limit this range)? g. Firmware. i. Is the firmware upgradeable, and, if so, how is it upgraded? ii. Can firmware upgrades be performed over the network? iii. Describe the method and past frequently of firmware updates/upgrades. 5. Repeater Description a. Provide a general description of the repeater(s) you propose for EBMUD with physical dimensions including height, length, width, and weight. b. Power supply. i. What is the preferred power source and what are the requirements for power supply? ii. Is there a backup power supply? iii. How long is the backup power supply? iv. Is a solar powered option available? c. Repeater communications. i. What data is contained in a transmission? For example, meter reads and alarm codes, collector operation data, signal strength, etc. ii. Is there a limit on the size of the transmission in bytes? 6

7 iii. What is the strength/power of the transmission? iv. Does the transmission power diminish over time? Does decreasing power affect range? Please describe. v. How is the transmission encrypted? What type of encryption is used? What type of cyber security measures are employed at the repeater level? Is that different than a collector? vi. What type of data can be received by the repeater? Is that different than a collector? vii. Describe the communications protocol required by the device. 1. Are the communication protocols for the repeaters open and useable by any AMR/AMI or meter? 2. Will the repeater accept signals from third party devices? 3. Can the repeater share communications protocols so other AMI manufacturers and third party equipment provider devices can be read by your collector? viii. How frequently can the repeaters interrogate MIUs? ix. What factors can be adjusted remotely from the server such as frequency, transmission strength, alarm codes, firmware settings? x. Does the repeater have onboard data storage in the event communication with a collector is unavailable? 1. If so, how many meter reads and alarm codes can be stored. 2. Can lost data be automatically uploaded to the network after re-establishing connection with a collector? d. Describe environmental tolerances for the collector equipment (e.g., temperature, humidity, vibration, wind). e. Provide recommended maintenance requirements. f. What is the power output and typical transmission range of the device (identify any circumstances that would limit this range)? g. Firmware. i. Is the firmware upgradeable, and, if so, how is it upgraded? ii. Can firmware upgrades be performed over the network? iii. Describe the method and past frequently of firmware updates/upgrades. 6. Collector and Repeater Installation a. Provide collector and repeater installation guidelines and restrictions. b. Is collector and repeater installation typically done by your company, third party, or your customers? c. Can installation be done by qualified EBMUD staff? d. Provide utility requirements for each collector/repeater type proposed. e. Describe any special mounting requirements including pole, tower and bracing restrictions, the recommended sighting and the minimum separation from other radio, cellular, microwave or other sources of interference. 7

8 f. If pole or tower mounted, can the unit be installed at the base with the antennae mounted on the tower? g. Describe the process to program/configure and install the collectors and repeaters. i. Describe equipment needed? ii. Can the collectors and repeaters be pre-configured in the factory? iii. Can successful configuration be verified in the field? iv. Briefly describe procedures that need to be followed to replace failed collectors and repeaters. 7. Mobile Data Collector a. Indicate if the system has the capability of collecting data via a mobile collector should an MIU not be in range of a fixed collector or the collector has failed. b. Describe the mobile collection system(s)? Indicate if it is computer, handheld based or both? i. Does the mobile system have a GPS map with navigation tools and driver alerts? ii. Can file routes be updated to the system wirelessly? iii. Describe any programmable features of the mobile data collection software. c. Can interval data be recovered from MIUs via mobile wireless connection? i. Indicate the maximum number of reads that can be collected? ii. Indicate the approximate time to download the maximum number of reads. d. Briefly describe the process of downloading billing reads to the server. e. Indicate if interval reads can be downloaded to the server or MDMS? f. How many concurrent users can the system accommodate? What is the licensing arrangement for concurrent users? g. How is the mobile collected data encrypted, and what type of cyber security measures do you employ at the mobile collector level? 8. Server Description a. Describe the type of server needed to handle EBMUD s meter collection system. Assume 100,000 MIUs will be needed initially with growth to 500,000 endpoints over time with hourly reads. Describe the MDMS with available storage capacities. b. Describe any capacity limitations (e.g., the number of accounts, number of readings per account) for the proposed configuration. Describe any provisions for archiving data. c. Describe data back-up capabilities and procedures to ensure that system and consumption data is not corrupted or lost. d. Describe how data can be queried via ODBC to generate data extractions and reports. e. Describe any built in tools for data views. f. Is the user interface browser-based or is client software required? i. Will the software run on Windows 7 and Windows 10? Other? 8

9 ii. Describe the software update process. Indicate the minimum hardware and software requirements for the client/user interface. g. What provisions exist for data entry and editing by users? h. Provide a list, with brief descriptions and screenshots or sample pages, of the standard reports provided for system and component performance; missing or late data; errors, anomalies and alarm conditions; data transfer, management and administration; analysis of consumption for individual customers or groups of customers; and other major report categories. i. Custom Reports/Queries. i. Explain how EBMUD can write custom reports against the data in the server. ii. Provide a database schema for the data source EBMUD can use for querying data. j. Traps for questionable readings. Describe any system capabilities to validate meter readings for reasonableness, such as unusually high or low readings, or meter rollover reads. k. Describe any tools available to assess the performance of the system and to diagnose problems (e.g., radio transmission strength/problems, server malfunction, and battery life status). l. Provide software system overview; flow charts; file descriptions and record layouts; database structure diagrams; description of program function and logic; back-up and recovery procedures; operating procedures; screen layouts; data entry procedures; report descriptions; descriptions of all user options; and descriptions of all error messages. m. Third-party software. i. Indicate third party software (operating system, database, report writer, etc.) specifically required to support vendor s application. ii. Indicate the warranty, licensing and support provisions for any such packages. n. Software test environment. i. Describe how software is tested prior to placing changes into production. Does the software enable simulation of operating with sample data before permanent changes are incorporated into the code or processes? ii. Describe what hardware, software and licenses must be purchased (if any) to provide a test environment. o. Security. i. What restrictions are placed on such functions to ensure security and data integrity? ii. Does the software include a security system, incorporating multiple levels of authorization and access to limit specific data, users, modules and/or specific tasks? iii. Can the System Administrator modify the levels of security? Describe security features, logging and levels. iv. Describe how data is encrypted, user authentication protocols, and other cybersecurity protocols that are available. v. Describe whether the system has undergone an independent third-party data security assessment. p. Support. i. Indicate support services your server/system will come with including but not limited to: 9

10 1. Telephone support. 2. All software licenses and updates. 3. Equipment loaner program. 4. Remote diagnostics. 5. On-site troubleshooting, if needed. ii. Do you provide onsite support? 1. Describe the types of problems that would need to be addressed by on-site support and the response time EBMUD will receive. 2. Indicate what companies will provide the support and where their offices are located. q. Indicate if Software-as-a-Service is available for the server and for an MDMS. r. Is a backup server available? 9. Network Description a. Provide an estimate of the number of collectors and repeaters that might be needed to cover EBMUD s service area with 98% of the meter reads collected at least 23 hours per day. b. Aside from MIUs, collectors, communication systems, repeaters, and possibly servers what other hardware may be needed? 10. Other Network Functions a. Describe other functions your network can provide such as SCADA control, communications, remote instrumentation, etc. b. Describe any optional equipment or software that can be purchased from your company that adds additional functionality. c. Describe other communications protocols your equipment uses including, but not limited to, Modbus, Modbus TCP, DNP3, etc. d. Describe how the system can be connected to SCADA networks, which SCADA systems your system have been integrated with, and what security standards and communication protocols are used for data exchange and control. 11. Licenses a. What FCC or other regulatory agency licenses does the system require? i. Indicate the expected length of time to acquire such licenses. ii. Indicate what problems can occur in the process of obtaining such licenses. iii. Note if licenses must be acquired prior to the installation of the AMR system equipment. iv. Note the duration of the license as well as renewal procedure and cost. b. Can you obtain the license on EBMUD s behalf? c. Will you maintain the FCC license for the life of the system and replace/repair hardware consistent with the warranty provisions independent of service contract? 12. Meter Data Management Systems (MDMS) Compatibility 10

11 a. Describe the MDMS your AMI network has demonstrated compatibility with. Indicate which systems your MDMS is not compatible with. b. Describe if an MDMS system is included as a Software-as-a-Service (SaaS) for your network. Include the pricing structure for any SaaS service. 13. Third-Party Devices a. Describe all third party devices that your AMI endpoint has successfully connected to including but not limited to: i. Acoustic leak detection devices. ii. Pressure gauges. iii. Water quality instrumentation. iv. Remote shutoff valves either through the meter or stand-alone devices. v. SCADA system endpoints. b. Describe the communications protocol used to connect to these third-party devices. 14. Performance a. What is the estimated annual failure rate of new MIUs? b. What was the 2014 ratio of MIUs sold new vs. warranty replacements by model line? 15. Number of Current Installations a. For each AMI system suggested, provide the i. Make and model number, year shipments began and total number of units (same model number) purchased & shipped in the United States. ii. Total number of MIUs sold in the last 12 months by your company. iii. Total number of MIUs you anticipate selling in the next 12 months. iv. Total number of installations and MIUs sold to date. v. Total as part of complete deployments. vi. Total in operation more than 3 years. b. Is there a user s group for your product? Is it organized by your company or a third party? c. Are the MIU you are proposing in production and how long have they been in production? If they are not in production, when do you anticipate it will be available for purchase? d. Describe whether the MIUs and collectors are manufactured by your company, purchased from another company, or manufactured by another company for your use. e. What would be the estimated delivery time of a 10,000 MIU order? 16. R&D Activities / Strategic Product Direction a. Provide your current research and development activities. Include the percentage of total revenue reinvested in R&D annually and provide the dollar figure for the past five (5) years. b. Provide a statement of your strategic direction for each of the product lines being proposed. 11

12 c. Provide a product overview and discuss the evolution of the proposed AMI product from the first major release of the product through to the present. Include the historical timeline. d. Provide a copy of the AMI product development roadmap outlining the vision and strategy for the future of the proposed AMI System. Include a description of the upgrades/enhancements that are in the planning or design stage and an estimated release schedule for planned upgrades/enhancements. e. Describe the quality assurance/quality control policies and procedures you have adopted for system design, manufacturing, component sourcing and any other aspects that affect the serviceability and useful life of the equipment and software. Briefly describe the failure analysis process used when a product is returned. 17. Technical Support a. Provide a list of all known outstanding errors/system deficiencies and the anticipated schedule for their resolution. b. Describe your guaranteed and average response time for support calls during work hours (6 a.m. to 7 p.m. PST) and during off-hours (7 p.m. to 6 a.m. PST). c. Do you provide telephone support on an on-going basis? What are the times during the day that it is available? Is the cost of this support included in the Annual Hosting Fee? d. Do you provide product corrections, without charge, for any equipment failures or in the event that equipment fails to perform according to minimum agreed specifications discovered after installation of the endpoint? Does this support continue for the life of the contract? e. Do you provide on-site support if there is a critical failure of the system and the remote diagnostics prove inconclusive? f. Please describe how problems are classified according to degree of urgency. For example: (very urgent) is responded to within 2 hours; (urgent) within 8 hours; (somewhat urgent) within 48 hours; and, (not critical) within 5 working days. Who determines the priority of the problem? g. Provide escalation procedures that address circumstances where you are unable to resolve a problem within the established response times. 18. Warranty a. Describe your standard warranty in detail. i. What is the standard warranty period? ii. Is a full 20-year warranty available? iii. List the warranty for each component including but not limited to: 1. MIU. 2. MIU installation device or programmer. 3. Collector. 4. Mobile Collector. 5. Repeaters. 6. Server. 12

13 b. What factors, if any, will affect warranty such as sampling frequency, connection to third party devices, or required maintenance. c. Is battery life warranted? If so, how long is the warranty? d. Is MIU transmission strength part of the warranty? 19. Pricing a. Provide approximate pricing for the following: i. Approximate MIU pricing based on purchase of 20,000-50,000 MIUs per year. ii. Collectors (fixed and mobile). iii. Repeaters. iv. Installation services for collectors and repeaters. v. Server capable of handling 100,000 endpoints at 1-hour interval with 10-year storage. vi. Annual license fee based on 25,000 MIUs, 50,000 MIUs, 100,000 MIUs, etc. vii. One time set up costs. viii. Annual support contract. ix. Other items not listed here. 20. AMI-Able Compliance a. Indicate what provisions of the AMI-Able standards you comply with. b. Indicate if you have a road map that complies with these provisions. c. Provide a brief explanation for any compliance provision that you do not agree with. Refer to: Other Provide any additional information about your product that may be of interest. 22. Submittal: Submit your responses to the addresses below. and/or hard copies are acceptable. If you have any technical questions, please contact Mr. David Wallenstein at or at dwallens@ebmud.com. Thank you in advance for your interest in this request. David Wallenstein, P.E. EBMUD Water Conservation th Street, MS 109 Oakland, CA dwallens@ebmud.com 13