request for information
REQUEST FOR INFORMATION August 2012
Automated Meter Reading System
REQUEST FOR INFORMATION ISSUED BY: Gina Jenkins, Customer Services Manager East Bay Municipal Utility District 375 11th Street Oakland, CA 94607-4240 ISSUED ON: August 29, 2012 RFI RESPONSES DUE: 4:00 p.m., September 19, 2012 Submission via email or hardcopy is acceptable. Postmarks will not be accepted. DELIVER TO: East Bay Municipal Utility District AMR System – RFI Submittal Sanna Garcia – Associate Civil Engineer 375 Eleventh Street, MS 504 Oakland, CA 94607-4240 OR [email protected]
2
1.0 Introduction East Bay Municipal Utility District (EBMUD) issues this Request for Information (RFI) to obtain pre-proposal information on an automated meter reading (AMR) system to replace direct-read meter reading at some meter locations. EBMUD anticipates converting to AMR at an estimated 1,700 meters out of approximately 400,000 metered services, with locations throughout the 325-square-mile service area. The project will include replacement of approximately 1,200 meters (5/8 to 2 inch) and retrofit of 500 meters (5/8 to 10 inch) to absolute encoded output meters/registers. About 400 of the retrofit meters will require two registers. EBMUD staff will install the new meters, retrofit existing meters and install AMR system.
1.1
Project Intent
EBMUD requires an AMR system that will eliminate the need for direct-read where meters are
On steep embankments Located in deep vaults or meter pits In proximity to high-speed vehicular traffic or Not easily accessible (behind fence or other obstruction)
EBMUD will consider all read collection methods. EBMUD intends to select a system that minimizes the overall cost and effort of installation and integration with customer billing, as well as long-term maintenance and routine meter reading costs.
1.2
Scope of Work
A complete AMR system shall include the following:
Meter interface unit/transmitter Hardware/method for mounting transmitter Hardware/method for connecting transmitter to absolute encoded meter/register Read collection hardware Read collection software Training on installation, hardware use, software operation Support to integrate meter reading data with EBMUD’s billing system Software support Hardware warranty
3
2.0 Background EBMUD supplies water for parts of Alameda and Contra Costa Counties on the eastern side of San Francisco Bay in Northern California. Approximately 1.3 million people are served by EBMUD’s water system in a 325-square-mile area.
2.1
Meter Reading
EBMUD has approximately 400,000 metered water services. The meters have direct-read registers and are divided into about 890 meter reading routes. The vast majority of the accounts are read bi-monthly. Of the 865 bi-monthly accounts, 681 are walking routes and 184 are driving routes. EBMUD employs about 25 meter readers and together they read 7,000 to 10,000 meters per day. EBMUD has 42 billing cycles over a two month period. EBMUD currently uses Itron hand-helds for keyed entry of meter reads and meter reading error/work order codes. The Itron meter reading software uploads the reads to EBMUD’s Customer Information System (CIS) and loads routes onto the hand-helds via a tethered cradle system. EBMUD is in the process of selecting a replacement system for its hand-helds and meter reading software. EBMUD recently replaced its CIS system with an EBMUD developed system which was built with Java-based software. EBMUD has about 130 existing encoder register transmitters (ERT) and about 210 existing remote read-outs on difficult-to-access meters. These will be replaced as part of this project. An Ergonomic Job Task Analysis was performed for EBMUD meter readers in 2010. The analysis recommended identifying and mitigating meters which are difficult to access or read. In 2011, EBMUD identified the locations and ranked the severity of conditions. In 2012, EBMUD initiated a project to mitigate the most difficult meters to read. One of the tools being used is adoption of AMR at some meters.
2.2
Customer Information System
Customer Watch is the District’s Customer Information System (CIS). Customer Watch manages meters, work orders, meter reads, billing, payments, and customer communication. Customer Watch runs on a multi-tier architecture using Windows 2008 servers and Oracle 10.2 relational database management system (RDBMS) as its primary platform. Customer Watch interfaces with the District’s current Itron meter reading system. Customer Watch processes Itron meter reads by way of file based interface. Files are deposited every night for batch upload into Customer Watch. Customer Watch has alternate ways to interface with data, including extensible markup language (XML) based Web Services and structured query language (SQL) based RDBMS.
4
2.3
Meter Types
EBMUD uses positive displacement type meters for 5/8-inch through 2-inch meters. These meters are typically set in below-ground meter boxes. The EBMUD current standard installation for non-paved areas is shown in Drawing 3679-B (Attachment B). EBMUD predominantly uses compound type meters for 3-inch and up. Compound meters are typically installed in below-ground vaults. The approximate distribution by size of meters to be converted to AMR is shown below. Meter Size
Count
5/8 inch 3/4 inch 1 inch 1 1/2 inch 2 inch 3 inch 4 inch 6 inch 8 inch 10 inch
894 9 108 163 131 141 114 84 59 8
TOTAL
2.4
1711
Meter Boxes
EBMUD has a mix of different meter box material types, shapes and sizes. The most prevalent meter box style is concrete with rectangular shaped lids, Drawing 136-A (Attachment C). The second most prevalent are oval shaped concrete meter boxes, Drawing 149-A (Attachment D). EBMUD also has boxes with cast iron lids and newer concrete polymer boxes. Larger meters are typically in vaults with 3/8-inch steel plate covers.
2.5
Meter Locations
The locations (longitude, latitude) of meters to be converted to AMR are available in a shapefile format for use in a GIS application. To request a copy of this data, contact Sanna Garcia at [email protected].
5
3.0 Instructions to Vendors EBMUD requests a written technical submittal on a specific AMR system recommended for EBMUD. EBMUD will review the technical submittals provided in response to this RFI and this information will be used to compose a formal RFP (Request for Proposal). When responding to this RFI, all vendors shall adhere to the guidelines defined below.
3.1
Confidential Vendor Information
All technical submittals in response to this RFI shall become the property of EBMUD and a matter of public record. The vendor must identify all copyrighted material, trade secrets or other proprietary information that they claim are exempt from disclosure under the Public Records Act (California Code Sections 6250, et seq.). All information that is to be kept confidential and not subject to public scrutiny, must be stated as such, and be contained within an attachment named “Confidential Vendor Information”. In the event such an exemption is claimed, the vendor shall state in the submittal that they will defend any action taken against EBMUD to release such exempt material.
3.2
Questions
All questions should be directed to Sanna Garcia via email at [email protected] or by phone (510) 287-1679. To ensure response, questions must be received no later than 12:00 p.m. on September 14, 2012. EBMUD will respond to questions via email or phone by the end of the second business day.
3.3
RFI Submission Format
To expedite EBMUD’s review and evaluation process the vendor should follow the outline defined below when developing their submittal. Provide concise and informative answers to all questions contained in Attachment A – Required Technical Information.
3.3.1 Executive Summary Vendor shall provide a summary of the submission no more than 2 pages long, which outlines the highlights of their AMR system, unique skills and experience of the vendor and the advantages to EBMUD.
3.3.2 Required Information The required functional and technical information for a complete RFI submittal are listed in Attachment A. All responses shall reference the question number to which they pertain. References to external documents are not acceptable.
3.4
Schedule of RFI Process
The selection process for the automated meter reading system is outlined below, along with the approximate timeline.
6
Task
Timeline
Advertise RFI Vendor questions by RFI Submissions due Evaluate, Compose RFP RFP process Select vendor Conduct test Negotiations Board approval Contract/NTP Start deliveries/training
3.5
August, 2012 September, 2012 September, 2012 October, 2012 November/December, 2012 January, 2013 February, 2013 March, 2013 April, 2013 May, 2013 June, July, 2013
RFI Review/Development of RFP
The technical submittals will be reviewed by an EBMUD user group and used to compose specifications and a Request for Proposal for purchase of an AMR system to be used as outlined above. During the RFI review period, the District may contact vendors for further clarification on any information submitted as part of this RFI. The technical information submitted will be used to determine potential system/vendor performance in the following critical areas. At this time the District is NOT asking for pricing on any system or service. Pricing/bids will be part of the RFP process occurring at a later date. Category
Technical Information
Read Performance
Power, radio performance, data security, read success rate
Operational compatibility
Required hardware, meter reading data collection ease/flexibility, billing integration Field durability, failure rates, warranty, battery, product support
Maintenance Installation Experience Advanced features
Installation method, lid, connector, programming, training/support, meter compatibility References, vendor reputation, vendor’s recommended approach Higher resolution, greater data storage, more frequent readings, more options for data access, migration
7
ATTACHMENT A Required Technical Information
8
Attachment A Required Technical Information AUTOMATED METER READING (AMR) SYSTEM - REQUEST FOR INFORMATION No.
Please provide or describe the following in your technical submittal:
A. System A1 A2 A3 A4 A5
The type of AMR system being proposed: walk-by, mobile, network (respond to section D, E, or F, depending on system proposed) State the specific products (name, model #) and quanitity of units recommended for this project Describe general operation of system and how it will integrate with existing meter reading/billing History of this product, including release versions/dates and when next product version is expected. Vendor's practice of supporting prior generation products. Provide at least five references where this specific AMR product is installed and operational on at least 2,000 water meters. Provide name/contact information.
B. Meter Interface Unit (MIU)/Transmitter B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 B12 B13
Describe operation: continuous bubble-up (1-way), on-demand (2-way), wi-fi, cellular State power level of inbound and outbound transmissions and the typical range (based on vendors recommended installation) Specify frequency band, whether licensed, methods used to limit interference and whether frequency can be modified once installed Describe security features used to prevent unauthorized interception of data Provide dimensions of MIU and describe manufacturering/testing for environmental durability State warranty for MIU failures (years, full/partial replacement, and procedure) State maximum MIU failure rate which vendor is willing to guarantee (number of failures per year/number installed) List compatibility with multiple meter brands (absolute encoded output). Include maximum number of digits and the error codes that can be accepted from each meter brand. List the routine data transmitted with each meter reading (e.g. date, time, alerts, ids etc) Provide storage capacity of meter interface unit and how stored data is accessed Provide frequency of meter read interrogation (standard and best available) Indicate whether the MIU can be operated in more than one read collection mode and the process to switch between modes Describe advanced features which provide operational flexibility or enhanced data or allow proactive maintenance
C. Field Installation C1 C2 C3 C4 C5 C6
Recommended MIU installation for meter boxes; address lid material, and if MIU should be installed under, attached or through lid Recommended connector(s) between meter and MIU Recommended MIU installation for large meters in metal covered vaults Describe the field programming procedure List handhelds or other proprietary equipment needed for field installation and initiation of MIU If MIU is integrated with register, describe recommended process for installing/programming registers for multiple meter brands/sizes.
D. Read Collection - Walk-by D1 D2 D3
Hardware: describe equipment (size, weight) to transmit meter reads to existing manual input handhelds Operation: describe procedure for intiating a read and how it is transmitted to handheld Performance: required proximity to meter and elapsed time to obtain meter read
E. Read Collection - Mobile Drive-by E1 E2 E3 E4 E5 E6 E7
Hardware: describe mobile receiver/computer and number of units recommended for project Software: describe data collection functionality e.g. vehicle routing, route completion, alerts, account match up, high/low checks, required field checks, mapping etc. Performance: required proximity to meter and elapsed time to obtain meter read Describe ability to accept direct keyed entry such as manual read, alphanumeric notes Describe procedure to enter routing information. Describe ability to accept import route files and export data files to a third party meter reading software Describe read error reporting and procedures to recover from read errors.
F. Read Collection - Network (Radio, Cellular, Wi-Fi, Other) F1 F2 F3 F4 F5 F6 F7 F8 F9
Hardware: describe equipment, number of units and locations. If third party data collection, estimated annual service fees per meter Software: describe data collection functionality such as frequency of read, account match-up, read confirmation etc. Performance: State guaranteed read success rate (% of MIUs out of total installed reporting a valid read for billing) Describe back-up read collection if method does not work at a particular meter location Describe advanced features which provide operational flexibility or enhanced data or allow proactive maintenance Describe architecture and technology for moving read data between AMR system and District data store. Describe ability to move read data into current District file based standard Describe all additional hardware and software needed to store read data -- ie servers, RDBMS systems, disk space, etc. Describe suggested best practices to store and archive read data -- duration, disk space required, etc.
G. Training/Support G1 G2
Specify number/type/duration of resources recommended for training on system installation and operation Describe standard vendor-provided system maintenance and troubleshooting support (level and duration)
ATTACHMENT B Drawing 3679-B
9
ATTACHMENT C Drawing 136-A
10
NO. 11 GAS£ GALV. OUTSIDE WIRE 1
/
S
^ "*~1
r
\
I 1"
ME?AL R4M - SEE MOTE 2 \
1
4-
/
o
ft.
O
«
a
1
*« 0*
.0 • I*
^
1»
a
o
• < X
a •
•
c
MI*
* /
-
•
o". -ICM
/
\
j \
J 1"
2
PLAN NOTES: 1.
2.
REINFORCEMENT SHALL BE APPROVED WELDEOWIRE MAT WITH OUTSIDE WlflE AS SHOWN OR OTHER REINFORCEMENT SUBJECT TO APPROVAL BY THE DISTRICT. COVER TO HAVE NON-FERROUS METAL RIM COMPLETELY AROUND OUTSIDE EDGE.
V
J. • —mi o
^_
SECT. A-A RCViSED 19 NOV. 87 D.
EAST BAY MUNICIPAL UTILITY DISTRICT OAKLAND, CALIFORNIA
STANDARD DRAWING
NO. 1 M E T E R B O X COVER RECTA.NGULA.R 5/8" a 3/4" METERS
ATTACHMENT D Drawing 149-A
11
A«-l
METAL RIM SEEIWTE2
, — 5 MIN.
NO. 11 GAGEGALV. OUTSIT. Wf RE
PLAN REVISED I t NOV. 17 D. %t't
NOTES: 1.
2.
REINFORCEMENT SHALL BE AN APPROVED WELDED WIRE MATWITH OUTSIDE WIRE AS SHOWN OR OTHER REINFORCEMENT SUBJECT TO APPROVAL BY THE DISTRICT. COVER TO HAVE NON-FERROUS METAL RIM COMPLETELY AROUND OUTSIDE EDGE.
APPROVED.
^e/dl
CHIEP ENGINEER
SECT. A-A
EAST BAY MUNICIPAL UTILITY DISTRICT OAKLAND, CALIFORNIA
TYPE
STANDARD DRAWING 0 METER B O X COVER OVAL 5 / 8 " S 3/4" METERS TRACED BY J. W.TRAHSRN
DESIGNED BY
DRAWN BY J.W. TRAHERN
SCALE
CHECKED BY
DATE
IS
NO.
I 49-A
R. C. K.
RECOMMENDED BY APPROVED BY R.C. K.
3/8
SIZE
MAY
32
Automated Meter Reading System
REQUEST FOR INFORMATION ISSUED BY: Gina Jenkins, Customer Services Manager East Bay Municipal Utility District 375 11th Street Oakland, CA 94607-4240 ISSUED ON: August 29, 2012 RFI RESPONSES DUE: 4:00 p.m., September 19, 2012 Submission via email or hardcopy is acceptable. Postmarks will not be accepted. DELIVER TO: East Bay Municipal Utility District AMR System – RFI Submittal Sanna Garcia – Associate Civil Engineer 375 Eleventh Street, MS 504 Oakland, CA 94607-4240 OR [email protected]
2
1.0 Introduction East Bay Municipal Utility District (EBMUD) issues this Request for Information (RFI) to obtain pre-proposal information on an automated meter reading (AMR) system to replace direct-read meter reading at some meter locations. EBMUD anticipates converting to AMR at an estimated 1,700 meters out of approximately 400,000 metered services, with locations throughout the 325-square-mile service area. The project will include replacement of approximately 1,200 meters (5/8 to 2 inch) and retrofit of 500 meters (5/8 to 10 inch) to absolute encoded output meters/registers. About 400 of the retrofit meters will require two registers. EBMUD staff will install the new meters, retrofit existing meters and install AMR system.
1.1
Project Intent
EBMUD requires an AMR system that will eliminate the need for direct-read where meters are
On steep embankments Located in deep vaults or meter pits In proximity to high-speed vehicular traffic or Not easily accessible (behind fence or other obstruction)
EBMUD will consider all read collection methods. EBMUD intends to select a system that minimizes the overall cost and effort of installation and integration with customer billing, as well as long-term maintenance and routine meter reading costs.
1.2
Scope of Work
A complete AMR system shall include the following:
Meter interface unit/transmitter Hardware/method for mounting transmitter Hardware/method for connecting transmitter to absolute encoded meter/register Read collection hardware Read collection software Training on installation, hardware use, software operation Support to integrate meter reading data with EBMUD’s billing system Software support Hardware warranty
3
2.0 Background EBMUD supplies water for parts of Alameda and Contra Costa Counties on the eastern side of San Francisco Bay in Northern California. Approximately 1.3 million people are served by EBMUD’s water system in a 325-square-mile area.
2.1
Meter Reading
EBMUD has approximately 400,000 metered water services. The meters have direct-read registers and are divided into about 890 meter reading routes. The vast majority of the accounts are read bi-monthly. Of the 865 bi-monthly accounts, 681 are walking routes and 184 are driving routes. EBMUD employs about 25 meter readers and together they read 7,000 to 10,000 meters per day. EBMUD has 42 billing cycles over a two month period. EBMUD currently uses Itron hand-helds for keyed entry of meter reads and meter reading error/work order codes. The Itron meter reading software uploads the reads to EBMUD’s Customer Information System (CIS) and loads routes onto the hand-helds via a tethered cradle system. EBMUD is in the process of selecting a replacement system for its hand-helds and meter reading software. EBMUD recently replaced its CIS system with an EBMUD developed system which was built with Java-based software. EBMUD has about 130 existing encoder register transmitters (ERT) and about 210 existing remote read-outs on difficult-to-access meters. These will be replaced as part of this project. An Ergonomic Job Task Analysis was performed for EBMUD meter readers in 2010. The analysis recommended identifying and mitigating meters which are difficult to access or read. In 2011, EBMUD identified the locations and ranked the severity of conditions. In 2012, EBMUD initiated a project to mitigate the most difficult meters to read. One of the tools being used is adoption of AMR at some meters.
2.2
Customer Information System
Customer Watch is the District’s Customer Information System (CIS). Customer Watch manages meters, work orders, meter reads, billing, payments, and customer communication. Customer Watch runs on a multi-tier architecture using Windows 2008 servers and Oracle 10.2 relational database management system (RDBMS) as its primary platform. Customer Watch interfaces with the District’s current Itron meter reading system. Customer Watch processes Itron meter reads by way of file based interface. Files are deposited every night for batch upload into Customer Watch. Customer Watch has alternate ways to interface with data, including extensible markup language (XML) based Web Services and structured query language (SQL) based RDBMS.
4
2.3
Meter Types
EBMUD uses positive displacement type meters for 5/8-inch through 2-inch meters. These meters are typically set in below-ground meter boxes. The EBMUD current standard installation for non-paved areas is shown in Drawing 3679-B (Attachment B). EBMUD predominantly uses compound type meters for 3-inch and up. Compound meters are typically installed in below-ground vaults. The approximate distribution by size of meters to be converted to AMR is shown below. Meter Size
Count
5/8 inch 3/4 inch 1 inch 1 1/2 inch 2 inch 3 inch 4 inch 6 inch 8 inch 10 inch
894 9 108 163 131 141 114 84 59 8
TOTAL
2.4
1711
Meter Boxes
EBMUD has a mix of different meter box material types, shapes and sizes. The most prevalent meter box style is concrete with rectangular shaped lids, Drawing 136-A (Attachment C). The second most prevalent are oval shaped concrete meter boxes, Drawing 149-A (Attachment D). EBMUD also has boxes with cast iron lids and newer concrete polymer boxes. Larger meters are typically in vaults with 3/8-inch steel plate covers.
2.5
Meter Locations
The locations (longitude, latitude) of meters to be converted to AMR are available in a shapefile format for use in a GIS application. To request a copy of this data, contact Sanna Garcia at [email protected].
5
3.0 Instructions to Vendors EBMUD requests a written technical submittal on a specific AMR system recommended for EBMUD. EBMUD will review the technical submittals provided in response to this RFI and this information will be used to compose a formal RFP (Request for Proposal). When responding to this RFI, all vendors shall adhere to the guidelines defined below.
3.1
Confidential Vendor Information
All technical submittals in response to this RFI shall become the property of EBMUD and a matter of public record. The vendor must identify all copyrighted material, trade secrets or other proprietary information that they claim are exempt from disclosure under the Public Records Act (California Code Sections 6250, et seq.). All information that is to be kept confidential and not subject to public scrutiny, must be stated as such, and be contained within an attachment named “Confidential Vendor Information”. In the event such an exemption is claimed, the vendor shall state in the submittal that they will defend any action taken against EBMUD to release such exempt material.
3.2
Questions
All questions should be directed to Sanna Garcia via email at [email protected] or by phone (510) 287-1679. To ensure response, questions must be received no later than 12:00 p.m. on September 14, 2012. EBMUD will respond to questions via email or phone by the end of the second business day.
3.3
RFI Submission Format
To expedite EBMUD’s review and evaluation process the vendor should follow the outline defined below when developing their submittal. Provide concise and informative answers to all questions contained in Attachment A – Required Technical Information.
3.3.1 Executive Summary Vendor shall provide a summary of the submission no more than 2 pages long, which outlines the highlights of their AMR system, unique skills and experience of the vendor and the advantages to EBMUD.
3.3.2 Required Information The required functional and technical information for a complete RFI submittal are listed in Attachment A. All responses shall reference the question number to which they pertain. References to external documents are not acceptable.
3.4
Schedule of RFI Process
The selection process for the automated meter reading system is outlined below, along with the approximate timeline.
6
Task
Timeline
Advertise RFI Vendor questions by RFI Submissions due Evaluate, Compose RFP RFP process Select vendor Conduct test Negotiations Board approval Contract/NTP Start deliveries/training
3.5
August, 2012 September, 2012 September, 2012 October, 2012 November/December, 2012 January, 2013 February, 2013 March, 2013 April, 2013 May, 2013 June, July, 2013
RFI Review/Development of RFP
The technical submittals will be reviewed by an EBMUD user group and used to compose specifications and a Request for Proposal for purchase of an AMR system to be used as outlined above. During the RFI review period, the District may contact vendors for further clarification on any information submitted as part of this RFI. The technical information submitted will be used to determine potential system/vendor performance in the following critical areas. At this time the District is NOT asking for pricing on any system or service. Pricing/bids will be part of the RFP process occurring at a later date. Category
Technical Information
Read Performance
Power, radio performance, data security, read success rate
Operational compatibility
Required hardware, meter reading data collection ease/flexibility, billing integration Field durability, failure rates, warranty, battery, product support
Maintenance Installation Experience Advanced features
Installation method, lid, connector, programming, training/support, meter compatibility References, vendor reputation, vendor’s recommended approach Higher resolution, greater data storage, more frequent readings, more options for data access, migration
7
ATTACHMENT A Required Technical Information
8
Attachment A Required Technical Information AUTOMATED METER READING (AMR) SYSTEM - REQUEST FOR INFORMATION No.
Please provide or describe the following in your technical submittal:
A. System A1 A2 A3 A4 A5
The type of AMR system being proposed: walk-by, mobile, network (respond to section D, E, or F, depending on system proposed) State the specific products (name, model #) and quanitity of units recommended for this project Describe general operation of system and how it will integrate with existing meter reading/billing History of this product, including release versions/dates and when next product version is expected. Vendor's practice of supporting prior generation products. Provide at least five references where this specific AMR product is installed and operational on at least 2,000 water meters. Provide name/contact information.
B. Meter Interface Unit (MIU)/Transmitter B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 B12 B13
Describe operation: continuous bubble-up (1-way), on-demand (2-way), wi-fi, cellular State power level of inbound and outbound transmissions and the typical range (based on vendors recommended installation) Specify frequency band, whether licensed, methods used to limit interference and whether frequency can be modified once installed Describe security features used to prevent unauthorized interception of data Provide dimensions of MIU and describe manufacturering/testing for environmental durability State warranty for MIU failures (years, full/partial replacement, and procedure) State maximum MIU failure rate which vendor is willing to guarantee (number of failures per year/number installed) List compatibility with multiple meter brands (absolute encoded output). Include maximum number of digits and the error codes that can be accepted from each meter brand. List the routine data transmitted with each meter reading (e.g. date, time, alerts, ids etc) Provide storage capacity of meter interface unit and how stored data is accessed Provide frequency of meter read interrogation (standard and best available) Indicate whether the MIU can be operated in more than one read collection mode and the process to switch between modes Describe advanced features which provide operational flexibility or enhanced data or allow proactive maintenance
C. Field Installation C1 C2 C3 C4 C5 C6
Recommended MIU installation for meter boxes; address lid material, and if MIU should be installed under, attached or through lid Recommended connector(s) between meter and MIU Recommended MIU installation for large meters in metal covered vaults Describe the field programming procedure List handhelds or other proprietary equipment needed for field installation and initiation of MIU If MIU is integrated with register, describe recommended process for installing/programming registers for multiple meter brands/sizes.
D. Read Collection - Walk-by D1 D2 D3
Hardware: describe equipment (size, weight) to transmit meter reads to existing manual input handhelds Operation: describe procedure for intiating a read and how it is transmitted to handheld Performance: required proximity to meter and elapsed time to obtain meter read
E. Read Collection - Mobile Drive-by E1 E2 E3 E4 E5 E6 E7
Hardware: describe mobile receiver/computer and number of units recommended for project Software: describe data collection functionality e.g. vehicle routing, route completion, alerts, account match up, high/low checks, required field checks, mapping etc. Performance: required proximity to meter and elapsed time to obtain meter read Describe ability to accept direct keyed entry such as manual read, alphanumeric notes Describe procedure to enter routing information. Describe ability to accept import route files and export data files to a third party meter reading software Describe read error reporting and procedures to recover from read errors.
F. Read Collection - Network (Radio, Cellular, Wi-Fi, Other) F1 F2 F3 F4 F5 F6 F7 F8 F9
Hardware: describe equipment, number of units and locations. If third party data collection, estimated annual service fees per meter Software: describe data collection functionality such as frequency of read, account match-up, read confirmation etc. Performance: State guaranteed read success rate (% of MIUs out of total installed reporting a valid read for billing) Describe back-up read collection if method does not work at a particular meter location Describe advanced features which provide operational flexibility or enhanced data or allow proactive maintenance Describe architecture and technology for moving read data between AMR system and District data store. Describe ability to move read data into current District file based standard Describe all additional hardware and software needed to store read data -- ie servers, RDBMS systems, disk space, etc. Describe suggested best practices to store and archive read data -- duration, disk space required, etc.
G. Training/Support G1 G2
Specify number/type/duration of resources recommended for training on system installation and operation Describe standard vendor-provided system maintenance and troubleshooting support (level and duration)
ATTACHMENT B Drawing 3679-B
9
ATTACHMENT C Drawing 136-A
10
NO. 11 GAS£ GALV. OUTSIDE WIRE 1
/
S
^ "*~1
r
\
I 1"
ME?AL R4M - SEE MOTE 2 \
1
4-
/
o
ft.
O
«
a
1
*« 0*
.0 • I*
^
1»
a
o
• < X
a •
•
c
MI*
* /
-
•
o". -ICM
/
\
j \
J 1"
2
PLAN NOTES: 1.
2.
REINFORCEMENT SHALL BE APPROVED WELDEOWIRE MAT WITH OUTSIDE WlflE AS SHOWN OR OTHER REINFORCEMENT SUBJECT TO APPROVAL BY THE DISTRICT. COVER TO HAVE NON-FERROUS METAL RIM COMPLETELY AROUND OUTSIDE EDGE.
V
J. • —mi o
^_
SECT. A-A RCViSED 19 NOV. 87 D.
EAST BAY MUNICIPAL UTILITY DISTRICT OAKLAND, CALIFORNIA
STANDARD DRAWING
NO. 1 M E T E R B O X COVER RECTA.NGULA.R 5/8" a 3/4" METERS
ATTACHMENT D Drawing 149-A
11
A«-l
METAL RIM SEEIWTE2
, — 5 MIN.
NO. 11 GAGEGALV. OUTSIT. Wf RE
PLAN REVISED I t NOV. 17 D. %t't
NOTES: 1.
2.
REINFORCEMENT SHALL BE AN APPROVED WELDED WIRE MATWITH OUTSIDE WIRE AS SHOWN OR OTHER REINFORCEMENT SUBJECT TO APPROVAL BY THE DISTRICT. COVER TO HAVE NON-FERROUS METAL RIM COMPLETELY AROUND OUTSIDE EDGE.
APPROVED.
^e/dl
CHIEP ENGINEER
SECT. A-A
EAST BAY MUNICIPAL UTILITY DISTRICT OAKLAND, CALIFORNIA
TYPE
STANDARD DRAWING 0 METER B O X COVER OVAL 5 / 8 " S 3/4" METERS TRACED BY J. W.TRAHSRN
DESIGNED BY
DRAWN BY J.W. TRAHERN
SCALE
CHECKED BY
DATE
IS
NO.
I 49-A
R. C. K.
RECOMMENDED BY APPROVED BY R.C. K.
3/8
SIZE
MAY
32
