Advanced Metering Infrastructue ProjectTHE CITY OF
Dubuque
Du13
Masterpiece the Mississippi
Masterpiece on the Mississippi
TO: The Honorable Mayor and City Council Members
FROM: Michael C. Van Milligen, City Manager
SUBJECT: Advanced Metering Infrastructure Project
DATE: April 9, 2010
All AmedcaCBy
2007
As part of our Smarter Sustainable Dubuque Initiative, we are proposing to work with
IBM, and Interstate Power and Light on the Smart Metering and Measurement of
electrical energy utilization in Dubuque.
IBM would like to work on developing a prototype service using Web portals to access
the prototype service running on IBM servers, that would allow City management and
electric utility customers to monitor electric energy consumption on a near real -time
basis in order to better control and reduce the consumption of electric energy.
IBM is willing to work on developing the software tools for collecting, updating and
processing the Data provided by the volunteers participating in the project for use for
the Prototype Service; providing written reports to the City on the progress and results
of the project; and demonstrating the Prototype Service to the City and other Iowa
government agencies as agreed by the parties.
The City is willing to provide funding for the project subject to approval of the project by
the Iowa Power Fund. The City will identify volunteers among its residents to participate
in this project; work with City energy company, Interstate Power and Light Company on
the installation of smart meters with two -way communication capability necessary for
the project; provide the volunteers' energy consumption data to IBM in an anonymized
form, interface with the volunteers to answer questions about the Prototype Service,
work with IBM to analyze the results, and provide IBM with feedback on the results.
Interstate Power and Light Company will install up to 1000 Advanced Metering
Infrastructure meters for project participants in Dubuque, Iowa and provide the
individual customer electricity usage and related data as described to the City for
restricted display on a web portal and for independent analysis in accordance with the
City's research objectives for the project and for the City to provide any and all analysis
and reports resulting from such analysis to Interstate Power and Light Company as a
result of the project.
To achieve these goals, Smarter Sustainable Dubuque Project Manager David Lyons is
recommending that the City enter into the attached agreements with IBM and Interstate
Power and Light Company. The City will then ask for approval of the project by the Iowa
Power Fund. If approved, the City will be eligible for a grant from the Iowa Power Fund
in the amount of $1.4 million.
concur with the recommendation and respectfully request Mayor and City Council
approval.
MCVM:jh
Attachment
cc: Barry Lindahl, City Attorney
Cindy Steinhauser, Assistant City Manager
David Lyons, Project Manager
Michael C. Van Milligen
License No.
JOINT DEVELOPMENT AGREEMENT
Agreement No. W1055610
This Joint Development Agreement ( "Agreement ") is between City of Dubuque, Iowa,
with an address at 50 W. 13 Street, Dubuque, IA 52001 ( "City "), and International
Business Machines Corporation, a New York corporation, through its T. J. Watson
Research Center, with a location at 1101 Kitchawan Road, Route 134, Yorktown Heights,
NY 10598 ( "IBM ").
WHEREAS, IBM would like to work on developing a prototype service using Web
portals to access the prototype service running on IBM servers, that would allow City
management and electric utility customers to monitor electric energy consumption on a
near real -time basis in order to better control and reduce the consumption of electric
energy ( "Prototype Service "); and
WHEREAS, City is willing to provide funding for the project subject to approval of the
project by the Iowa Power Fund; identify volunteers among its residents to participate in
this project; work with City energy company, Interstate Power and Light Company (an
Alliant Energy company) ( "IPL "), on the installation of smart meters with two -way
communication capability necessary for the project; provide the volunteers' energy
consumption data to IBM in an anonymized form ( "Data "), interface with the volunteers
to answer questions about the Prototype Service, work with IBM to analyze the results,
and provide IBM with feedback on the results ( "Feedback "); and
WHEREAS, IBM is willing to work on developing the software tools for collecting,
updating and processing the Data provided by the volunteers participating in the project
for use for the Prototype Service ( "Tools "); provide written reports to City on the
progress and results of the project; and demonstrate the Prototype Service to City and
other Iowa government agencies as agreed by the parties;
NOW, THEREFORE, for good and valuable consideration as stated herein, City and
IBM agree as follows:
1.0 Scope of Work
1.1 The scope of work for the project is as described in Appendix A, Statement of
Work.
1
1.2 All components of the Prototype Service, the Tools, and the Feedback will be
owned by IBM and will be considered IBM Confidential Information in
accordance with the provisions of Article 7.0.
1.3 For a period of three (3) years after the expiration of this Agreement, IBM agrees
that IBM Research will make available to any Iowa governmental entity (State,
County or Local), the Prototype Service developed under this Agreement in
accordance with terms and conditions to be agreed upon by the governmental
entity and IBM, for the sole purpose of monitoring electric energy consumption
during the term of such entity's contract with IBM. In the event the Iowa
governmental entity is not referred to IBM by City, IBM will charge the
governmental entity IBM's then current rates for the Prototype Service. If the
Iowa governmental entity is referred to IBM by City, IBM will not charge the
governmental entity for the Prototype Service; however, each such governmental
entity will be required to pay IBM Research for: (i) any customizations that need
to be made to the Prototype Service, and (ii) use of the IBM Cloud Service, IBM
Smarter City Sustainability Model Software, and any other Software necessary to
run the Prototype Service (including, without limitation, IBM's Infosphere
Information Server, DB2, Cognos and Websphere Application Server), in each
case, at the then current rates for IBM Research.
IBM acknowledges that City has informed IBM that it is the. intent of City to enter
into an agreement with the Iowa Power Fund to allow the Iowa Power Fund to
make direct referrals to IBM of Iowa governmental entities on behalf of City for
purposes of this Article 1.3.
2.0 Technical Coordinators
David Lyons for City, and Milind Naphade, for IBM, are the Technical
Coordinators for this Agreement. Their responsibilities will include exchanging
information with the other party, coordinating any visits, and arranging all other
matters pertinent to this Agreement. Each party may change its Technical
Coordinator by giving written notice to the other party.
3.0 Costs and Expenses
3.1 City will pay IBM One Million Four Hundred Thousand Dollars ($1,400,000)
toward the costs of the project in accordance with the following payment schedule:
May 10, 2010 $140,000
July 1, 2010 $210,000
October 1, 2010 $210,000
2
January 1, 2011 $210,000
April 1, 2011 $210,000
July 1, 2011 $210,000
October 1, 2011 $210,000
These payments are nonrefundable.
TOTAL $1,400,000
3.2. Payment will be made by wire transfer to the following account:
Director of Licensing
International Business Machines Corporation
PNC Bank
500 First Avenue
Pittsburgh, PA 15219
Bank Account Number: 1017306369
ABA Routing Number: 043000096
3.3 The License Reference Number shown on the first page of this Agreement must
be included in all communications, including wire transfer payments, tax credit
certificates, letters, faxes and e-mail messages pertaining to the payments made
under Article 3.1.
3.4 IBM will be entitled to late payment fees on payments due but not received within
thirty (30) days after the due date. Late payment fees are defined as the lesser of
one percent (1 %) of the amount due, compounded each subsequent thirty (30) day
period that payments remain unpaid, or the highest rate permitted by law.
3.5 City will bear and pay all taxes (including, but not limited to, sales, property and
value added taxes) imposed by any governmental entity of any country in which
City is doing business as the result of the existence of this Agreement or the
exercise of rights hereunder, except that City will not be liable for any taxes based
on IBM's net income. Taxes paid by City will not be deducted from or credited
against payments due IBM.
4.0 Copyrights
4.1 "Software" means computer programs, computer program changes, computer
program enhancements, and /or any documentation related to computer programs.
3
The parties agree that no Software will be delivered by either party to the other
party under this Agreement.
4.2 IBM grants to City an irrevocable, nonexclusive, worldwide and fully paid -up
license to use, reproduce and distribute internally, any copyrightable materials
(other than Software) furnished or developed by IBM under this Agreement. In
addition, IBM grants to City the right to sublicense the Progress Reports and the
Summary Report identified in Appendix A to the Iowa Power Fund, for the Iowa
Power Fund to use, reproduce and distribute internally, subject to the
confidentiality provisions of Article 7.0 below, and to the provisions of Article
9.10.
4.3 City grants to IBM an irrevocable, nonexclusive, worldwide, and fully paid -up
license for any copyrightable materials (other than Software) furnished or
developed by City under this Agreement. This license includes the right to use,
execute, display, reproduce, perform, disclose, prepare derivative works from, and
distribute and transmit (internally and externally) such copyrightable materials and
their derivative works and to sublicense others to do any or all of the foregoing.
This license is subject to the confidentiality provisions of Article 7.0. IBM will
not take ownership interests in any copyrightable materials (including the Data)
furnished or developed by City under this Agreement.
5. Inventions
5.1 "Invention" means any idea, design, concept, technique, invention, discovery or
improvement, whether or not patentable, conceived or first reduced to practice
solely by one or more employees of a party hereto ( "Sole Invention "), or jointly by
one or more employees of one party with one or more employees of the other party
( "Joint Invention "), in the performance of work under this Agreement.
5.2 Each party will promptly provide to the other party a written description of each
Invention. The other party agrees to delay making public, by publication or
otherwise, until the earlier of (1) the first filing of a patent application claiming the
Invention by the owning party or (2) six months after the date the Invention is
disclosed to the other party, for any Invention for which the disclosing party has
decided, or is in the process of deciding, to seek patent protection.
5.3 Any Sole Invention will be the property of the inventing party, subject to a license
hereby granted to the other party of the scope set forth in Article 5.4 for such Sole
Invention and all patents issued on it. Any Joint Invention will be jointly owned,
and title to all patents issued on it will be joint, all expenses (including those
related to preparation, prosecution and maintenance) will be jointly shared (except
as provided below), and each party will have the right to license and assign its
ownership interest in the joint patent to third parties without need for consent
from or accounting to the other party. Where one party elects not to share equally
4
in the expenses for a Joint Invention, the other party will have the right to seek or
maintain such protection for such Joint Invention at its own expense and will have
full control over its preparation, prosecution and maintenance, even though title to
any issuing patent will be joint.
5.4 All licenses granted to City and IBM under this Article 5 will be worldwide,
irrevocable, nonexclusive, nontransferable, and fully paid -up, and will include the
right to make, have made, use, have used, lease, sell, offer to sell, import and /or
otherwise transfer any product, and to practice and have practiced any method.
All licenses granted to City and to IBM in this Article 5 will include the right of
the grantee to grant revocable or irrevocable sublicenses to its Subsidiaries, such
sublicenses to include the right of the sublicensed Subsidiaries correspondingly to
sublicense other Subsidiaries.
5.5 "Subsidiary" will mean a corporation, company, or other entity;
i. more than 50% of whose outstanding shares or securities (representing the
right to vote for the election of directors or other managing authority) are,
now or hereafter, owned or controlled, directly or indirectly, by a party
hereto, but such corporation, company, or other entity will be deemed to be a
Subsidiary only so long as such ownership or control exists; or
ii. which does not have outstanding shares or securities, as may be the case in a
partnership, joint venture or unincorporated association, but more than 50%
of whose ownership interest representing the right to make the decisions for
such corporation, company or other entity is now or hereafter, owned or
controlled, directly or indirectly, by a party hereto, but such corporation,
company or other entity will be deemed to be a Subsidiary only so long as
such ownership or control exists.
6.0 Term and Termination
6.1 This Agreement will begin on the date it is signed by the last signatory ( "Effective
Date "), and end twenty (20) months later, unless terminated earlier by either party
as provided in Article 6.2 or 6.3 below.
6.2 City may terminate this Agreement at the end of any calendar quarter with written
notice to IBM sent not less than thirty (30) days prior to the end of that quarter, on
condition that City pay IBM the payment due at the beginning of the next calendar
quarter commencing after the effective date of the termination.
6.3 IBM may terminate this Agreement at the end of any calendar quarter with written
notice to City sent not less than thirty (30) days prior to the end of that quarter.
5
6.4 This Agreement is subject to approval by the Iowa Power Fund by not later than
April 30, 2010, and in the event this Agreement is not so approved by such date,
this Agreement shall be null and void.
7.0 Confidentiality
7.1 "IBM Confidential Information" means the Feedback, and any technical
information about the Prototype Service and the Tools.
7.2 For five (5) years from the date of disclosure, City agrees to hold IBM
Confidential information in trust and confidence for IBM. City will limit
disclosure of the IBM Confidential Information to those of its employees who
have a need to know it. City will use IBM's Confidential Information only for
the purposes of this Agreement.
7.3 Disclosure of Confidential Information will not be precluded if the disclosure is
required by law, but City will give IBM reasonable notice to allow IBM an
opportunity to obtain a protective order. The obligations of Article 7.2 above will
not apply to information that is: (a) already in the possession of City without
obligation of confidence; (b) independently developed by City; (c) publicly
available, or becomes publicly available through no fault of City; (d) disclosed by
IBM without obligation of confidence; or e) disclosed with the permission of
IBM.
7.4 Each party agrees that the disclosure of its Confidential Information pursuant to
this Agreement does not limit the assignment or reassignment of the other party's
employees.
7.5 Notwithstanding any provision in this Agreement to the contrary, City may
provide any reports provided to City by IBM under this Agreement to the Iowa
Office of Energy Independence, and to other governmental entities in Iowa. In
addition, IBM agrees that the Iowa Office of Energy Independence and the Iowa
Utilities Board may have unrestricted access to all City records for purposes of
evaluating the work performed under this Agreement.
8.0 Representations, Warranties, Disclaimers, Indemnification and Limitation of
Liability
8.1 City will be solely responsible for the collection of the Data, and for determining
what Data may and will be provided to IBM under this Agreement.
8.2 City represents and warrants that it has all necessary third party consents to
provide the Data to IBM, and to permit IBM to use the Data as provided in this
Agreement. City further represents and warrants that it has anonymized the Data
6
delivered to IBM to an extent sufficient to ensure that a person without prior
knowledge of the original Data and its collection cannot, from the anonymized
Data and other publicly available information, deduce the personal identity of the
Data subjects.
8.3 Except as provided in Article 8.2, NEITHER PARTY MAKES ANY
WARRANTY, EXPRESS OR IMPLIED, CONCERNING COPYRIGHTABLE
MATERIALS, INVENTIONS, PROTOTYPES, DATA, INFORMATION, OR
OTHER DELIVERABLES SUPPLIED UNDER THIS AGREEMENT, WHICH
ARE ALL PROVIDED "AS IS." EACH PARTY EXPLICITLY DISCLAIMS
THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE, AND ANY WARRANTY OF NON -
INFRINGEMENT OF ANY THIRD PARTY'S PATENTS, COPYRIGHTS, OR
ANY OTHER INTELLECTUAL PROPERTY RIGHT.
8.4 EACH PARTY ALSO SPECIFICALLY DISCLAIMS ANY WARRANTY
REGARDING ANY PROTOTYPE(S) WHICH MAY BE DEVELOPED
PURSUANT TO THIS AGREEMENT INCLUDING THAT ANY
PROTOTYPE(S) WILL MEET ANY DEVELOPMENT OBJECTIVES, OR
ANY REQUIREMENTS OF EITHER PARTY. EACH PARTY WILL MAKE
GOOD FAITH EFFORTS TO COMPLETE THE ACTIVITIES UNDER THE
STATEMENT OF WORK. FAILURE TO COMPLETE SUCH ACTIVITIES
DOES NOT CONSTITUTE BREACH OF CONTRACT.
8.5 City will defend and indemnify IBM and IBM's Subsidiaries if a third party
makes a claim against IBM or its Subsidiaries based on an actual or alleged breach
of City's representations and warranties set forth in Article 8.2.
8.6 Except for claims arising out of Article 7.0, and indemnification obligations
arising under Article 8.5, neither party will be liable for any consequential
damages, lost profits, lost savings, loss of anticipated revenue, or any exemplary,
punitive, special or indirect damages, even if advised of their possibility. IBM's
total cumulative direct damages will not exceed a cumulative total of One
Hundred Thousand Dollars ($100,000).
9.0 General Provisions
9.1 Each party is an independent contractor. Neither party is, nor will claim to be, a
legal representative, partner, franchisee, agent or employee of the other. Neither
party will assume or create obligations for the other.
9.2 Except as otherwise provided herein, this Agreement does not confer any rights to
use in advertising, publicity or other marketing activities any name, trade name,
trademark, or other designation of either party hereto, including any contraction,
abbreviation, or simulation of any of the foregoing, without prior written
7
agreement, and each party agrees not to use or refer to this Agreement or its terms
in any such activities without the express written approval of the other party.
9.3 All notices will be in writing and will be valid if sent by: a) registered or
certified mail, return receipt requested, postage prepaid; b) by facsimile
(provided the receipt of the facsimile is evidenced by a printed record of
completion of transmission); or, c) by express mail or courier service providing a
receipt of delivery. Notice will be effective upon receipt and addressed as
follows:
IBM
Thomas J. Watson Research Center
IBM Corporation
1101 Kitchawan Road
Route 134
Yorktown Heights, NY 10598
Attn.: Manager, Business and
Government Relations
City
City of Dubuque, Iowa
50 W. 13th Street
Dubuque, IA 52001
Attn.: David Lyons
9.4 Neither party will be liable for any failure or delay in the performance of its
obligations under this Agreement if such failure or delay is due to acts of God,
acts of the other party, fire, flood, natural catastrophe, acts of any government or
of any civil or military authority, national emergencies, riots, war, insurrection,
strikes, or any occurrence beyond the reasonable control of such party.
9.5 Each party agrees to comply and to reasonably assist the other in complying with
applicable government export and import laws and regulations. Further, each
party agrees that unless authorized by applicable government license or regulation,
including but not limited to U.S. authorization, it will not directly or indirectly
export or reexport, at any time, any technology, software and /or commodities
furnished or developed under this Agreement, or any other agreement between the
parties, or its direct product, to any prohibited country (including release of
technology, software and /or commodities to nationals, wherever they may be
located, of any prohibited country) as specified in applicable export, embargo,
and sanctions regulations. This section will survive after termination or expiration
of this Agreement.
9.6 Except as expressly provided in this Agreement, neither party grants any licenses,
either directly or indirectly, by implication or estoppel or otherwise, to either party
under any patent, copyright or other intellectual property right of the other party.
9.7 Neither party may assign, or otherwise transfer, its rights or delegate its
obligations under this Agreement without prior written consent of the other party.
Any attempt to do so is void.
8
9.8 Except for claims arising out of Articles 5.0, 7.0, or 8.5, neither party may bring
an action arising out of this Agreement, regardless of form, more than one year
after the cause of action has accrued.
9.9 Neither party relies on any promises, inducements or representations made by the
other, or expectations of more business dealings, except as expressly provided in
this Agreement.
9.10 Each party represents that it has, or will have appropriate agreements with its
employees or others whose services the party may require to enable it to comply
with all the provisions of this Agreement.
9.11 Each party may have similar agreements with others, and may design, develop,
manufacture, acquire or market competitive products and services, and conduct its
business in whatever way it chooses. Each party will independently establish
prices and terms for its products and services.
9.12 If any provision of this Agreement is held to be invalid, illegal or unenforceable,
the validity, legality and enforceability of the remaining provisions will in no way
be affected or impaired thereby so long as the intent of the parties can be
preserved.
9.13 This Agreement is governed by the laws of the State of New York, without regard
to the conflict of laws provisions thereof. Any proceedings to resolve disputes
relating to this Agreement will be brought only in a U.S. federal court if there is
federal jurisdiction over such proceeding. The parties waive the right to trial by
jury in any matter which arises under this Agreement. The United Nations'
Convention on International Sales of Goods does not apply.
9.14 Any rights and obligations which by their nature survive and continue after any
expiration or termination of this Agreement will survive and continue and will
bind the parties and their successors and assigns, until such obligations are
fulfilled.
9.15 This Agreement may only be amended by a writing signed by authorized
representatives of the parties. No approval, consent or waiver which alters the
terms of this Agreement will be enforceable unless signed by both parties. Failure
to insist on strict performance or to exercise a right when entitled does not prevent
a party from doing so later for that breach, or a future breach.
9.16 There are no intended third party beneficiaries to this Agreement.
9.17 This Agreement and Appendix A are the complete and exclusive agreement
between the parties regarding the subject matter hereof and supersedes any prior
9
oral or written communications or understandings between the parties related to
the subject matter hereof.
By signing below, the parties agree to the terms of this Agreement.
INTERNATIONAL BUSINESS CITY OF DUBUQUE, IOWA
MACHINES CORPORATION
Name: Name:
Title: Title:
Date: Date:
10
Objective
The objective of the project is to develop a Prototype Service for near real -time
measurement of electric energy consumption that would enable electric utility customers
in City of Dubuque to better control their consumption of electricity, and generate data
that could be used for the analysis of consumption patterns for insights that could help
electric utility customers reduce their consumption.
Project Description
City will identify volunteers among the electric utility customers in City to participate in
this project. These volunteers will be required to allow the installation in their business or
residence of advanced energy meters, and agree to allow their electric energy usage
information to be provided to IBM in anonymized form for use in developing the
prototype service. The community -wide metric information generated by this project can
be used by City to begin estimating consumption baselines, and the aggregated data will
also be shared with the volunteers so that they can compare and benchmark their personal
usage with that of the entire aggregated volunteer community.
IBM will develop the applications for processing and handling the Data for use by the
Prototype Service. IBM will also develop the tools required to automatically feed the
Data into the Prototype Service, and to be refreshed at an agreed upon rate, limited by the
rate at which this Data is provided to IBM. IBM will also analyze the collected Data to
identify patterns and insights that will be shared with City and the volunteers.
Responsibilities of the Parties
IBM:
APPENDIX A
STATEMENT OF WORK
1. Work on developing the Prototype Service that provides a Web portal for near
real -time integrated sustainability monitoring that would:
a. allow City management to visualize, interact, and understand the electrical
energy consumption patterns and sustainability footprint of the volunteers
participating in the project;
b. allow City and participating volunteers to visualize, interact, and
understand their electrical energy consumption patterns and sustainability
footprint in comparison with that of the other volunteers participating in
the project; and
c. Provide access to participating volunteers to the consumption patterns of
other volunteers only in the aggregate, and not on an individual participant
basis.
2. Work on developing Tools to perform:
a. data processing and data management to prepare the Data and then enter it
into the Prototype Service;
b. exploratory analysis on the Data to extract consumption patterns and
insights to be shared with City management and participating volunteers;
and
c. if data is available for some volunteers from both water consumption and
electric energy consumption, work on developing tools that perform
exploratory analysis on electrical energy and water resource consumption.
3. Make available for use by IBM resources for the project the following IBM
technology:
IBM Cloud Service
IBM Smarter City Sustainability Model Software
Infosphere Information Server
DB2
Cognos
Websphere Application Server
4. Provide City with written progress reports within thirty (30) days after the end of
each calendar quarter, summarizing the work performed, the results achieved, and
the resources assigned to work on the project during the prior quarter ( "Progress
Reports ").
5. Provide a written report analyzing Citywide consumption patterns and sustainability
footprints for the participating volunteers, and summarizing the results of the project
( "Summary Report").
6. Demonstrate the Prototype Service to City and other Iowa government agencies as
agreed by the parties.
City:
1. Recruit up to one thousand (1,000) electric utility customer volunteers to participate
in the project.
2. Work with City's major electric energy supplier, IPL, to install smart meters with
two way communication capability for each of the volunteers by the end of June
2010.
3. Provide IBM with access to a data warehouse that will store electricity consumption
meter data as frequently as one reading every fifteen minutes, on an anonymized
basis.
4. Provide other available data, in an anonymized form, on the households of the
volunteers participating in the project, such as the size of the house, the number of
rooms, the number of windows and doors, the age of the house, appliances, and
family size and ages.
5. Provide personnel to interface with volunteers to answer questions about the
project, their service or their usage.
6. Work with IBM to analyze the results, and provide IBM with feedback on the
results.
Estimated Schedule
IBM will provide the following reports:
April 1, 2010 Readiness of the project, including project plan
June 1, 2010 Progress of requirements gathered
September 1, 2010 Progress made in identifying data sources, frequency of data
updates
December 1, 2010 Progress in developing tools for automated data gathering, and
warehousing from smart meters
March 1, 2011 Progress in development of the Prototype Service
June 1, 2011 Progress on end to end integration of data from the meters into the
Prototype Service
September 1, 2011 Progress of the demonstration of the Prototype Service
December 31, 2011 Project summary, included lessons learned regarding analysis of
consumption data, and insight on how the Prototype Service was
used
END
This Memorandum of Understanding (MOU) is made and entered into by and between
the City of Dubuque (City) and Interstate Power and Light Company (IPL) to set forth
the understandings and obligations of the parties pertaining to City's Sustainable
Dubuque AMI Pilot Project to assess energy efficiency technologies (the Project).
1. Scope /Objective
The overall objective of the Project is for IPL to install up to 1000 Advanced Metering
Infrastructure (AMI) meters for Project participants in Dubuque, Iowa and to provide the
individual customer electricity usage and related data as described in Exhibit D (the
Data) to City for restricted display on a web portal and for independent analysis in
accordance with the City's research objectives for the Project and for the City to provide
any and all analysis and reports resulting from such analysis to IPL as a result of the
Project. This MOU shall only relate to the activities described herein below and shall not
relate to any other project, contract or obligation undertaken by the parties, either jointly
or severally, including other IPL AMI or Smart Grid projects.
IPL was not awarded an American Recovery and Reinvestment Act Smart Grid
Investment Grant by the U.S. Department of Energy for a proposed demand response
pilot in Dubuque. In addition, in IPL's 2009 rate case order, IPL did not receive
accelerated meter depreciation for its existing electric meters, causing a delay in its AMI
deployment in Iowa. As a result, IPL is not implementing a demand response pilot in
Dubuque itself as originally envisioned, but is supporting the City's Sustainable
Dubuque AMI Pilot Project.
2. Term
Draft040910
MEMORANDUM OF UNDERSTANDING
BETWEEN
THE CITY OF DUBUQUE
AND
INTERSTATE POWER AND LIGHT COMPANY
FOR
THE SUSTAINABLE DUBUQUE AMI PILOT PROJECT
a. The term of this MOU shall commence on the date when the last of the two
parties has executed this MOU and shall expire upon completion of both
parties' Project obligations set forth herein, currently estimated to be no later
than March 31, 2013.
b. IPL may terminate this MOU upon prior written notice to City in the event City
or its contractors, including IBM, breaches any term of this MOU, including
but not limited to the Data restrictions set forth below.
c. IPL may terminate this MOU upon prior written notice to City in the event that
any submission by the City delays IPL's ability to commence interval Data
submission after December 31, 2010, in which event no further action will be
required by either party.
d. If the Iowa Power Fund notifies City that it desires to terminate the Project or
the portion of the Project for which IPL is responsible, within one day
thereafter, City will notify IPL in writing that it is terminating the Project or such
IPL portion at the request of the Iowa Power Fund and such notice will state
an effective date of termination.
e. City or IPL may terminate this MOU for its convenience upon one days' prior
written notice to the other party.
f. In the event of termination:
• IPL will immediately cease providing Data to City and City will
immediately cease providing anonymized Data to IBM.
• City will stop displaying individualized customer usage Data on the
portal.
• City and IBM will have 90 days to produce any reports from the Data
received prior to the effective date of termination.
• After such reports are produced, copies will be provided to IPL as
described in Section 4 below.
• Ninety days after the effective date of termination, City and IBM's
limited license to the use the Data shall terminate, except that both
may retain one archival copy in electronic form and one archival copy
in paper form and may only use such archival paper copies for on-
site reviews by the Iowa Power Fund or the Iowa Utilities Board as
described in Section 6 below.
3. Assumptions related to the Project
a. The Project participants shall be current customers of IPL located within the
areas specified on the map attached hereto as Exhibit A or such other areas
as the parties may agree in writing.
b. The Project participants shall be screened by IPL for elimination from
participation in the Project for reasons, including but not limited to, insufficient
network overage, irregular bill payment history, renter rather than
homeowner, or other applicable criteria.
c. Customer billing data will not be provided to City.
d. IPL's participant screening and consent process will last approximately one
(1) month after the final participant list is received from City. The target date
for completion of this task is set forth in Section 7 below.
e. The meter installation period will last approximately 26 weeks after the
commencement of the term of this MOU. The target date for completion of
this task is set forth in Section 7 below.
f. The Data will be collected starting approximately October 1, 2010, for a
minimum two -year period for each participant or through December 31, 2012,
whichever occurs earlier.
g. Customer meters will be manually read and billed through the current billing
process.
h. Any task not specified herein is excluded from the scope of this MOU.
i. IPL will not be offering new or incentive rates to electric customers as part of
this Project.
2
j. Meters installations may be subcontracted by IPL and all meters will be
installed during the installation period commencing on or about July 1, 2010.
k. IPL will not spend more than $400,000 to cover its activities and deliverables
outlined in this MOU.
4. Obligations of City
a. City shall provide IPL with a complete list of potential participants, including
names, addresses, participant's Anonymous ID number, and other applicable
information. City shall provide prompt periodic updates of this list to IPL for
additional customers and removal of customers, including dropouts. No
additions may be made after June 1, 2010 or when City has identified the list
as complete to IPL, whichever is earlier.
b. City shall provide secure test and production FTP sites with security as
described herein and otherwise consistent with IPL policies and requirements.
Data transmission must comply with best practices for file transfer using
Secure FTP (SFTP or FTPS) as set forth in FIPS 140 -2. The target date for
completion of this task is set forth in Section 7 below.
c. The Data transmitted is confidential information and must be protected by City
and its contractors from unauthorized use or users. User accounts must
comply with the Password Guidelines attached hereto as Exhibit B and
incorporated herein by this reference.
d. City shall promptly refer any meter and billing related questions, inquiries, or
complaints (e.g, can't hear meter, meter isn't transmitting, etc.) from
participants to IPL for resolution, at 1- 866 - ALLIANT (255 -4268) or
customercare @alliantenergy.com. Any change to this process will be
documented via a written modification of this MOU signed by both parties.
e. City is the primary point of contact for participants regarding the Project. IPL
is the primary point of contact for participants regarding meters.
f. City may use the Data provided by IPL, subject to Section 6 below.
g. City shall provide other deliverables to IPL for this Project as follows:
• Reports, analysis, and derivative works resulting from the Data
provided by the IPL with unlimited rights for IPL, promptly following
acceptance of the final version by City from its consultant or promptly
following submission if acceptance by City is not required — to include
at a minimum, the information showing how customers changed their
behavior and attained a heightened awareness of their energy usage.
• Reports, analysis, and derivative works resulting from the "Iowa
Power Fund Community Grant" with unlimited rights for IPL, promptly
following acceptance of the final version by City from its consultant or
promptly following submission if acceptance by City is not required —
to include at a minimum, the information showing how customers
changed their behavior and attained a heightened awareness of their
energy usage, energy savings and energy impacts to the community.
• Reports, analysis, and derivative works resulting from the
"Community Foundation of Greater Dubuque's EECBG ARRA Grant
for the Greater Dubuque /State of Iowa Smarter Cities & Smarter
3
State Retrofit Ramp -up" with unlimited rights for the IPL, promptly
following acceptance of the final version by City from its consultant or
promptly following submission if acceptance by City is not required —
to include at a minimum, the information showing how customers
changed their behavior and attained a heightened awareness of their
energy usage, energy savings and energy impacts to the community.
• IPL may use, reproduce, display, publish, or distributive, in whole or
in part, any of City's deliverables and may create derivative works
therefrom.
h. City agrees to adhere to EEI's Customer Data Access Principles for AMI, as
they may be amended from time, a current draft of which is attached hereto
as Exhibit C and incorporated herein by this reference. City agrees to treat
customer Data, including any inadvertent disclosures of personally identifiable
information by IPL, City or its contractors, in accordance with the restrictions
outlined therein for electric utilities and to be liable and responsible for lost or
misused customer - related Data as stated herein and therein.
i. In addition to approvals required by IPL's Corporate Communications director
or manager under Section 9.c below, City shall promptly provide drafts of all
communications that reference IPL, Alliant Energy, or electricity usage for
review and written approval by IPL's Project Manager or Program Manager
prior to publication or distribution. IPL shall have a reasonable period of time
to review such submissions. •
5. Obligations of IPL
a. IPL shall develop and provide to City screening criteria that IPL will use in
screening potential Project participants from the potential participants
identified by City.
b. IPL shall screen potential Project participants in accordance with such criteria
prior to meter installations.
c. Meter installations will begin after the participants have been identified, the
complete list of potential participants as outlined in section 4.a is received by
IPL from City in a mutually agreed upon electronic format, the participants are
screened by IPL and participants have agreed to participate in writing or
through other verifiable means sufficient to meet IPL's obligations for
customer consent for release of utility usage Data under applicable laws,
regulations and policies.
d. IPL shall promptly approve or reject changes in the participants identified by
City, including any replacements for drop -outs. The deadline for additions or
replacements is outlined in Sections 4.a and 7.
e. IPL shall address participants' questions, inquiries and complaints related to
meters in accordance with its standard procedures for all customer inquiries
at 1- 800 - ALLIANT (255 -4268) or customercare Ca�alliantenergy.com or through
another referral method to be mutually agreed upon in a written modification
to this MOU signed by both parties.
f. IPL may drop any participants at any time for any reason, upon written notice
to the City.
4
6. Data
g. IPL shall install meters at participants' locations after they have passed IPL's
screening.
h. IPL shall approve the security features of City's FTP site for Data before
posting any Data to it, but that IPL shall have no liability associated therewith.
IPL shall have the right to audit the security features of the FTP site at a
mutually agreeable time upon request to City during or after the term of this
MOU.
i. IPL shall provide deliverables to the City for this Project as follows:
• Data as further described in Section 6 below
• Up to 1000 electric AMI meters configured for 1 hour interval reads
including installation, trouble shooting, and repair /replacement. Of
these electric AMI meters, up to 250 may be configured for 15- minute
interval reads.
j. IPL shall transfer any customer calls regarding the Project to City's call center
at 1 -800- or email
k. Meter shipment delays to IPL that will impact the meter installation target
completion date will be promptly communicated to City. Meter delays will
result in a minimum day for day schedule delay.
a. City is granted a limited license to reproduce and use the Data solely for the
purposes of the Project during the term of this MOU. City may transfer the
Data to its contractor, IBM, only in anonymized form and IBM may reproduce
and develop software tools to collect, update and process the Data, provide
written reports to City on the progress and results of the Project, and
demonstrate its prototype service to City and other Iowa government
agencies as agreed by City and IBM during the term of this MOU. City may
not otherwise transfer, sell or license the individual customer Data supplied by
IPL or used by the City to any party in written or electronic form, including the
Office of Energy Independence, the Iowa Utilities Board, or other communities
in Iowa due to Iowa law restrictions on disclosure of such Data; however,
provided that if an individual customer has consented and has not withdrawn
any such consent, the Office of Energy Independence and the Iowa Utilities
Board may view individual customer Data at the city's offices where it is
stored. Otherwise, the Office of Energy Independence, the Iowa Utilities
Board, or other communities in Iowa may only view the aggregated Data as
contained in the reports to be produced as part of the City's Project. City may
display the Data in a restricted web portal so that each customer may only
view its own Data and no other customers may view a customer's Data.
Otherwise, all Data will be displayed or published in reports only on an
aggregated basis, to be approved in advance in writing by IPL. These limited
licenses are granted contingent on all applicable terms of this MOU being
incorporated into a written agreement between the City and IBM prior to the
supply of any real Data, including but not limited to Sections 6 and 9, a copy
of which signed City -IBM agreement will be provided to IPL prior to IPL
signing this MOU. Unless this MOU is terminated earlier, the City's and its
5
contractors' rights to use the Data supplied by IPL pursuant this MOU expire
upon completion of the deliverables or March 31, 2013, whichever occurs
earlier. At such time or date, the City will remove and destroy all such Data
from its electronic and written records and notify IPL that it has done so.
b. Data files to be supplied by IPL will consist of the participant's Anonymous ID
number and raw read Data files containing mutually agreed -to information
that is normally read from the meter and is available from the Remote
Network Interface (RNI)
c. IPL will use commercially reasonable efforts to read meters and to transmit
Data to City's secure FTP site at least one time per day.
d. For meters designated as one -hour interval read meters, the interval Data
reads will be a maximum of 24 one -hour increments per day.
e. For meters designated as high - resolution 15- minute interval read meters the
interval Data reads will be a maximum of 96 fifteen - minute increments per
day and configured for 10 Watt/Hr.
f. The parties will mutually agree on the file format for Data transmittals by April
2, 2010 in writing in which each party confirms that an attached or enclosed
list is acceptable.
g. Customer specific Data to be posted on City's website is for informational use
by individual customer only.
h. Data provided to City may not match a customer's bill so the Data provided
may not be consistent with the actual bill data.
i. Meter reader readings may not match the Data provided to City so the portal
may not be consistent with the actual bill data.
j. IPL will note readings in accordance with the list attached as Exhibit D in Data
submitted for analysis.
k. IPL may estimate a bill in lieu of performing actual meter reads, in its sole
discretion.
I. City is responsible for maintaining data relationships to any other data in its
Project that is provided or obtained from any other source.
m. Nothing contained in this MOU shall, by express grant, implication, estoppels
or otherwise, create in City or its contractors any ownership, right, title,
interest, or license in or to the Data supplied hereunder, except to the extent
expressly set forth in this MOU. The Data is and will remain owned by IPL
and its customers.
n. IPL disclaims any responsibility, liability, or warranty related to the Data,
including but not limited to, merchantability, fitness for a particular purpose,
suitability, accuracy, or completeness.
o. City represents and warrants that it has and will maintain adequate systems
and other controls in place to protect the Data supplied by IPL pursuant to this
MOU. City agrees that it shall only post Data on the portal for which IPL has
informed City that permission to do so has been received from the applicable
customer.
p. Data files for a participant will only be sent during the period that the
participant has agreed to participate.
7. Schedules and Timelines
6
Deliverables _ - -= _ -_ __ -- _ -
Target Date - ==
IPL submits Sample Raw Interval Data to City
February 26, 2010 (complete)
City submits initial proposed participant list to IPL
April 1, 2010 (complete)
City submits final proposed participant list to IPL. No
participant additions made after this date
June 1, 2010
IPL completes screening and consent process for all
participants
July 1, 2010
City has its test and production FTP sites ready to
accept Data
June 30, 2010
IPL installs up to 1000 Electric AMI Meters
October 1, 2010
Interval Data Provided by IPL to City — Start
October 1, 2010
Data collection complete
December 31, 2012
Estimated Schedule
Completion dates of IPL are contingent on City meeting the foregoing estimated target
dates. Delays in meeting target dates for submissions to IPL will result in a minimum
day for day delay in IPL meeting its target dates for providing deliverables.
8. Communication
a. The parties will hold a kick -off meeting at a mutually agreeable time and
location within two weeks after the effective date of this MOU.
b. The parties will agree on a schedule of and format for continuing meetings or
teleconferences throughout the Project at the kick -off meeting, which process
will be subject to change over the Project. The initial agreement will be
documented in meeting minutes after the kick -off meeting.
c. Notices, demands, or other communications related to this MOU will be sent
in writing by hand delivery or recognized overnight carrier service, although
electronic mail notices may be sent for specific issues if e-mail is specifically
allowed herein.
• Notices sent to IPL will be sent to:
Interstate Power and Light Company
c/o Alliant Energy Corporate Services, Inc.
Attention: Debbie Branson, Program Manager
4902 N. Biltmore Lane
Madison, WI 53718 -2148
E -mail: debbiebranson @alliantenergy.com
• Notices sent to the City will be sent to:
The City of Dubuque
Attention: City Manager
90 West 13 Street
Dubuque, Iowa 50301
E -mail:
7
9. Other Considerations
a. Each party will bear its own costs and liabilities of participating in this Project.
Nothing contained herein shall prevent IPL from including such costs in a rate
case.
b. Nothing in this MOU shall be deemed to constitute or create a joint venture,
partnership, or any type of permanent arrangement. The parties shall act in
all matters related to this MOU as independent contractors. The employees
of one party shall not be deemed employees of the other party. Nothing in
this MOU shall grant to any party the right to make commitments of any kind
or create any obligation, express or implied, for or on behalf of the other party
without the prior written consent of the other party.
c. No publicity or advertising will be released by City that directly or indirectly
references that IPL is providing support for this Project or refers to IPL or
uses IPL's name and /or logo (including the Alliant Energy name or logo),
without IPL's prior written consent of its Corporate Communications director
or manager. Similarly, IPL shall not release publicity or advertising
concerning this Project without the prior written consent of City. Neither party,
however, is precluded from revealing the contents of this MOU and the
relationship of the parties to appropriate governmental agencies, a court of
competent jurisdiction pursuant to a lawful order or a regulatory body having
jurisdiction over such party.
d. Each party will indemnify and hold harmless the other party against third party
claims for losses, expenses, damages, and liability of any nature, including
court costs and reasonable attorney's fees, arising out of or related to its
performance or non - performance under this MOU, including but not limited to,
infringement claims, breach of confidentiality or Data access provisions, or
adverse environmental effects. City and IPL will each maintain insurance
sufficient to cover its obligations hereunder and will provide a certificate of
such insurance to the other party upon request.
e. Neither City nor its contractor, IBM, may assign or transfer its duties,
interests, or obligations under this MOU without obtaining the prior written
consent of IPL.
f. Subject to Section 2.c above, a party shall not be in default because of any
failure to perform or delay in performing this MOU if the failure or delay arises
from causes beyond the control and without the fault or negligence of such
party.
8
10. This MOU, along with Exhibits A, B, C, and D hereto, constitutes the complete
agreement between the parties concerning its subject matter, and supersedes all
prior oral and written communications between the parties with respect to the
Project. No amendment to this MOU shall be binding unless agreed to in writing
and executed by both parties.
The City of Dubuque Interstate Power and Light Company
By: By:
Name: Name:
Title: Title:
9
EXHIBIT A
PROJECT AREA
10
11
User Passwords
EXHIBIT B
PASSWORD GUIDELINES
Applicability:
This standard applies to all passwords that are used on computer systems, terminals, data entry devices,
and personal digital assistants (PDAs) that are maintained by the corporation, carry corporate
information, or that connect to corporate networks or computer systems. This includes end user, shared,
system and administrative passwords.
Purpose:
To reduce risks posed by simple, obvious, or easy to guess passwords.
Standard:
Passwords are often the first line of defense in maintaining appropriate access controls for access to
corporate networks or computing resources. An easy to guess password can undermine the protection
provided by user credentials, allowing an unauthorized user to view or modify information to which he or
she would not normally have access.
Most IT computers and applications will enforce the following criteria when updating your
password:
Password History - end users must change their password 12 times before an old password can
be reused
Password Length — The password must be between 7 and 16 characters long
Password Complexity - The password contains characters from at least 3 of the following 5
categories:
• English uppercase characters (A - Z)
• English lowercase characters (a - z)
■ A number (0 - 9)
■ Non - alphanumeric (for example: !, $, #, or %)
■ Unicode Characters
Does not contain the user account name
Maximum password age Users must update their passwords every 60 days
1. Choose a good password. A good password shall be easy to remember so you don't have to write it
down, but difficult for someone else to guess or "crack ". Here are some guidelines to assist
• Password should not be a key sequence (i.e., 1234567, abcdefg, qwertyu)
• Don't use repeated keys (e.g, aaa, 111, $$$).
• Don't use dictionary words (ie.g, password, Iowa or Madison).
• Use a Pass - Phrase (e.g, PasswordsAreFun!)
• Substitute letters with special characters or numbers (e.g. a =@ e=3 i =1 o =0 u =4 s =5) 'boating'
made strong would be B0 @t1ng
System and Administrative Passwords:
Access to administrative passwords is restricted to network or system administrators who require access
to resources to perform job duties. Administrative passwords must meet at least the end user password
standard with the following additions:
1. Administrative passwords will not be hard -coded in files or tables to create a login shortcut
12
2. System ID passwords may be hard -coded in files or tables to create a login shortcut
3. Storage and transmission of passwords must be encrypted.
4. Delivered systems will be secured by placing controls (administrative accounts that cannot be
deleted or disabled will be secured with a strong password and, where possible, renamed)
upon all default accounts (i.e., admin, root, super user, anonymous, guest).
5. Access to administrative or system accounts will be limited to a specific use and accounts
with the lowest level of access will be utilized to apply changes
6. Systems must mask display of the password when entered by the user.
7. Invalid authentication attempts will not result in an account lockout for administrative or
system accounts.
13
EXHIBIT C
CURRENT EEI CUSTOMER DATA ACCESS PRINCIPLES
14
Ma EDISON ELECTRIC
INSTITUTE
EEI'S CUSTOMER DATA ACCESS PRINCIPLES
To meet the challenges of climate change, the need for increased reliability and quality of
electric service, as well as to provide many other benefits to the public, electric utilities are
increasingly using digital conuuunications tecluiologies, such as digital two -way communicating
meters (i.e., "Smart Meters" or "Advanced Metering Infrastruchue" ( "AMI ")) and digital two -
way communicating end -use devices to enable consumers to understand, monitor, and modify
their electricity consumption. With two -way conuuunication- enabled digital meters, customers'
consumption data can be collected even at the appliance level, and this information can be
conun unicatecl to the consumer, the electric utility and potentially other third parties. Similarly,
with two -way conunumcation capability, the customer may also receive data from the utility or
the retailer (e.g., pricing information, fuel portfolio. weather, restoration efforts, and requests to
curtail consumption, etc.). Hence, the Smart Grid will not only be an energy management
system, but a multi- directional "online" communication network that presents privacy
implications that should be addressed.
Although many utilities are in the process of implementing Smart Grid - related
deployments, many states only have general laws establishing privacy protections that are not
specific to the electric industry while some states have privacy requirements established in the
context of restructuring retail electric markets. In order for customer privacy to be protected. to
maintain the safe and reliable operation of the grid, and to optimize dispatch of generation, as
well as the potential for legal liability if data is lost, stolen or otherwise misused while in the
control of electric utilities, it is necessary for electric utilities to continue have access to and
15
protect this type of information. However, electric utilities need to carefully balance their
information collection and access policies in view of the appropriate pro - competitive role that
customer information can play in new and developing markets and the impacts on privacy,
reliability and efficiency. Accordingly, EEI, and its member companies, recommend the
following principles for the development of appropriate protections in the context of the Smart
Gricl for data collection, use, retention and disclosure of operational and customer data:
• As providers of essential services to the public and to ensure that the nation benefits from
the overall optimization of the grid, as well as to ensure the safe and reliable operation of
the grid, electric utilities must have unfettered access to operational and customer data for
planning, operations, and billing since this information is critical for load serving entities
( "LSEs ") and distribution utilities to conduct normal and customary business operations.
• Operational data must be controlled by the electric utility and /or the dispatching
entity. Electric utilities and /or the dispatching entity must continue to secure
operational or system configuration data and for which disclosure might threaten
system reliability. The electric utility and/or the dispatching entity should take
measures to prevent access to such data consistent with applicable state and federal
laws, policies and /or standards.
• Distributed resources that are authorized to be interconnected with utility systems
must share data with host utility and /or any dispatching entity. In order to preserve
system reliability and so that the operation of the entire system can be optimized and
protected, electric utilities must have access to operational data describing the status
of all distributed resources on their systems (e.g., distributed generators, distributed
storage devices, demand- responsive loads, and plug -in hybrid electric vehicles). This
means electric utilities should consider establishing contractual requirements for
owner /operators of distributed resources to share their data 01 their client's data with
the utility. Electric utilities should also consider including penalties in such
agreements in order to discourage non - compliance. These requirements should
extend to third party operators of micro- grids, as appropriate, and third parties who
have been authorized to operate customers' energy equipment.
• Given that customer assurance of privacy in taking electric utility services contributes to
customer confidence about utility choices, electric utilities rust continue to be
recognized at the prime stewards of customer - related information. In states with retail
access markets, both incumbent electric utilities and third parties that have been
authorized by customers to access this type of data should have comparable
responsibilities to protect customer - related information.
• Electric utilities should have a written policy regarding the collection, use, retention,
2
16
and disclosure of customer - relatecl information that is clear and understandable to
customers. Electric utility data policies must comport with applicable state laws and
policies. Customers should be infoiniecl of this policy at or before the time electric
service is initiated and with respect to changes to this policy on not less than an
annual basis. This policy should be accessible to customers (either upon request or
posted to the electric utility's website). Such a policy should describe the data or the
type of data collected, the purpose of the collection, use, retention and sharing of
customer-related data. To the extent applicable, the policy should describe any
choices available to customers relating to the collection, use, and retention and
disclosure of customer-related data.
• Electric utilities should only collect information required to fultill stated purposes,
and to the extent possible.
• Electric utilities should not release customer- related data to third parties absent a
customer's affirmative consent. Authorizations of third party access to customer-
related infonnnation should clearly establish that such consent is limited to defined
periods of time and for defined uses.
• Given the sensitivity of customer - relatecl data with respect to privacy as well as
security, third parties must agree to assume responsibility and liability for lost,
misused customer - related data.
• Electric utilities and authorized third parties should not sell customer- related
information to other parties without explicit consent of the customer.
• In order to protect customer privacy, whenever possible, electric utilities should
aggregate or reformat individual customer data in order to limit the potential for
computer matching of records. Aggregated data and or enhanced data, as opposed
data related to specific customers, is solely the property of the electric utility. If a
utility, for example, builds a decision support system (e.g., consisting of a data base, a
model base, and a user interface) to display customer data, the customer's property
rights properly extend only to their data, and not to any of these other possible
software enhancements.
• Electric utilities should consider maintaining a monitoring and compliance program
to ensure that utility operations comply with any applicable state privacy laws,
policies, or practices.
• Electric utilities should incorporate customer data use, retention and disclosure provisions
as part of the terms and conditions of customers taking electric service. Consistent with
applicable state and federal laws, such provisions should provide electric utility
customers with easy, efficient access to their electricity usage information.
• Customer and /or third party access to customer-related information should not
constrain or limit an electric utilities and or other applicable legal authorities to
transmit metered data to transmission and distribution operators, as needed, to
3
17
maintain system reliability.
• Electric utilities must have the flexibility to be responsive to customer needs for data.
Electric utilities should be able to provide customers with information via traditional
means (via telephone, mail, or inspection at utility offices, etc.) and/or electronic
media (i.e., the Internet) as consistent with any applicable federal and /or state
requirements.
• Electric utility agreements (e.g. service agreements) should provide customers with
reasonable control over disclosure of data to third parties. Customers should have the
right to determine what third parties or types of third parties will have access their data
and how it will be used.
• A customer's data should not be released to a third party unless the customer has
provided affirmative consent. Customer authorizations should be provided via
methods that ensure the identity of the authorizing individual is properly
authenticated.
• Access to a customer's data should be for defined periods of time, for defined uses.
These limitations should be stated in any authorization the customer is asked to agree
to, and any uses not specifically authorized by the customer should be prohibited.
• The reselling of or reassigiuuent of a license for customer data by third parties should
be prohibited.
• Incremental costs should be recovered. To the extent incumbent utilities Mau
incremental costs to provide expanded access by customers and /or their authorized agents
to customers' data, federal and state regulatory authorities should allow for such recovery
by the utilities.
4
18
EXHIBIT D
DATA FILE AND QUALITY FLAGS
19
Field Name
CMEP Data Type
Description
Anonymous ID
Arbitrary Text
City of Dubuque ID number assigned each
pilot participant.
Record Type
Protocol Text
Always "MEPMD01"
Record Version
Date
Release Date
Sender ID
Arbitrary Text
Always "Sensus"
Sender Customer ID
Arbitrary Text
Always "IPL:XXXXXX " , where X is Sensus
intemal customer id number.
Receiver ID
Arbitrary Text
Empty Field
Receiver Customer ID
Arbitrary Text
Flex ID
Time Stamp
Date/Time
( "YYYYMMDDHHMM ")
Date and Time that this record was created.
Meter ID
Arbitrary Text
The faceplate serial number to physically
identify a meter.
Purpose
Protocol Text
Indicates the reason for this data
transmission. "OK" = Normal transmission.
Commodity
Protocol Text
E — Electric
Units
Protocol Text
Describes the units of the data value.
- " SKWHREG" or KWHREG if a non -net
meter types
- "NKWHREG" if a net meter type
See Unit Table below for more information.
Calculation Constant
Numeric -Float
Used as a multiplier to convert data values
to engineering units. Typically, the value will
be "1".
Interval
Time Interval
Time between readings.
15 minute intervals = "00000015"
Count
Numeric Integer
Number of Triples to follow. For
SKWHREG record type, the value is always
"2" for the start and end reads.
Data Triples for SKWHREG Records
1 Interval Time Stamp
Date/Time
( "YYYYMMDDHHMM ")
UTC time
Data Quality Flag
Protocol Text
Data Quality Flag Table
Begin Reading
Numeric -Float
Last Interval Time Stamp
Date/Time
( "YYYYMMDDHHMM ")
UTC time
Data Quality Flag
Protocol Text
Data Quality Flag Table
End Reading
Numeric -Float
DATA FILE AND QUALITY FLAGS
A. Modified MEPMDD 1 MEP Interval Data File
The modified Inter al Data File is standard Clv1EF file format plus unique
identifier called Anonymous ID to identify each pilot participant at the
beginning of each meter record. This CMEP file is common separated (CSV
format) and do not exceed 2048 characters in record length. For each meter,
there will be two records: SKWHREG and SKWH.
1. CMEP SKWHREG Records - Data file format
The SKWHREG record contains start and end cumulative register reads
from the last 24 Hours, midnight to midnight reads.
20
Anonymous ID
Arbitrary Text
City of Dubuque ID number assigned each
pilot participant.
Record Type
Protocol Text
Always "MEPMD01"
Record Version
Date
Release Date
Sender ID
Arbitrary Text
Always " Sensus"
Sender Customer ID
Arbitrary Text
Always "IPL:XXXXXX " , where X is Sensus
internal customer id number.
Receiver ID
Arbitrary Text
Empty Field
Receiver Customer ID
Arbitrary Text
Flex ID
Time Stamp
Date/Time
( "YYYYMMDDHH M M ")
Date and Time that this record was created.
Meter ID
Arbitrary Text
The faceplate serial number to physically
identify a meter.
Purpose
Protocol Text
Indicates the reason for this data
transmission. Defined
values are:
"OK" — Normal transmission.
Commodity
Protocol Text
E — Electric
Units
Protocol Text
- "SKWH" or KWH if a non -net meter
types
- "NKWH" if a net meter type
This label indicates an interval line. See
Unit Table below for more information.
Calculation Constant
Numeric -Float
Used as a multiplier to convert data values
to engineering units. Typically, the value will
be "1 ".
Interval
Time Interval
Time between readings.
15 minute intervals = "00000015"
Count
Numeric Integer
Indicate the number of triples ....interval
data to follow. When there are more than
48 intervals for the reporting meter, the
SKWH record will have multiple lines in the
CMEP file.
Data Triples for SKWH Records
Note: The Hi Resolution 15 minute interval react meter will have 96 intervals entries in the SKWH
record ...... _.representing 24 hour period of 15- minute increments.
Interval Time Stamp
DatelTime
( "YYYYMMDDHHMM ")
UTC time
Data Quality Flag
Protocol Text
Data Quality Flag Table
Interval Usage
Numeric -Float
2. CMEP SKWH Record - Data file format
The SKWH record contains 24 hours of 15- minute interval readings (or 96
intervals) from the last 24 hours, midnight to midnight reads.
21
Prefix
Net Flow Property
N
F -R Simile Net
S
F +R Sum
Protocol Text
Description
NKWHREG NKWH
KWH net F -R
SKWHREG,SKWH
KWH sum (F +R)
Data Quality Value
Description
RO
Raw - Actual interval data or register read
N32
Missing — No interval data or register read
B. Protocol Text Defined Value Tables
Any field defined by CMEP as type "Protocol Text" should be defined with a
list of defined values.
1. Units
All units ending with "REG" indicate a register reading (cumulative).
Units not ending with "REG" indicate an interval reading.
2. Data Quality Flags
22