Professional Documents
Culture Documents
Commercial in Confidence
Issue Date: 16 November 2013
PO Box 109628
Auckland, New Zealand
info@powerbusiness.co.nz
Table of Contents
1.
2.
3.
4.
5.
Introduction
1.1
Background .............................................................................................................................. 6
1.2
1.3
Glossary of Terms .................................................................................................................... 7
Scope of Supply
10
2.1
2.2
Head-End ............................................................................................................................... 11
2.3
2.4
Telecommunications ............................................................................................................... 12
2.5
Additional Services ................................................................................................................. 12
RFP Proposals
13
3.1
3.2
3.3
Communications ..................................................................................................................... 15
3.4
3.5
3.6
3.7
3.8
3.9
Validity Period ........................................................................................................................ 17
RFP Terms and Conditions
18
AMI Components Overview
19
5.1
5.2
5.3
Standards ............................................................................................................................... 22
5.4
Service Functionality............................................................................................................... 22
5.5
Modularity............................................................................................................................... 23
5.6
5.6.1
Metrology
23
5.6.2
Configuration
24
5.6.3
Display
24
5.6.4
Installation
24
5.7
Head-End ............................................................................................................................... 24
5.7.1
24
5.7.2
25
5.8
5.8.1
5.9
Interfaces ............................................................................................................................... 25
25
Page: 2
5.9.1
Telecommunications Technologies
25
5.9.2
26
5.9.3
27
5.9.4
Network Coverage
30
5.10
5.10.1
33
5.10.2
Prepayment Management System
Responsibilities
6.
6.1
7.
31
36
6.1.1
Design
36
6.1.2
Installation
36
6.1.3
Commissioning
36
6.2
6.3
6.4
6.5
Training .................................................................................................................................. 37
6.6
Documentation ....................................................................................................................... 37
6.7
6.8
6.9
6.10
6.11
Systems Commissioning......................................................................................................... 40
6.12
Warranties .............................................................................................................................. 40
Equipment .............................................................................................................................. 41
7.2
Services ................................................................................................................................. 41
7.3
Currency Exchange ................................................................................................................ 41
8. Contract
42
Appendix A: Terms & Conditions of RFP
43
1.
2.
3.
4.
5.
6.
Subcontracting ....................................................................................................................... 45
7.
8.
Presentations ......................................................................................................................... 46
9.
10.
11.
Costs ...................................................................................................................................... 46
Page: 3
12.
13.
Confidentiality ......................................................................................................................... 47
14.
15.
16.
Conflict of Interest................................................................................................................... 47
17.
Liability ................................................................................................................................... 48
18.
19.
20.
21.
Currency/Foreign Exchange Rates ......................................................................................... 49
Appendix B: Requirements
51
1.
Metrology ............................................................................................................................... 51
1.1
Core Services
51
1.2
On Demand Services
54
1.3
58
1.4
Reporting
60
1.5
Fault Management
61
1.6
Metrology
62
1.7
65
1.8
Specific Functionality
66
1.9
External Interfaces
69
1.10
Delivery
70
1.11
Reference Sites
70
1.12
Technology Roadmap
71
2.
Telecommunications ............................................................................................................... 72
2.1
72
2.2
74
2.3
75
2.4
Security
76
2.5
77
2.6
Communications Technology
78
2.7
Reporting
80
2.8
Delivery
80
2.9
Reference Sites
81
2.10
3.
81
Technology Roadmap
82
Business Requirements
3.1.1
82
3.1.2
88
3.2
3.2.1
Technology Requirements
94
Technology Description
94
Page: 4
98
3.3
3.4
Expertise
100
3.5
100
3.6
Support Requirements
101
101
102
1.
2.
3.
4.
5.
6.
Other .................................................................................................................................... 111
Appendix D: Acknowledgement/Transmittal Forms
112
Appendix E: Key Contractual Terms
116
Page: 5
1.
Introduction
1.1
Background
Tonga Power Limited (TPL) has 17,000 residential and 4,000 commercial customers on its
four electricity networks throughout the Kingdom of Tonga. 85% of its customers are on
Tongatapu, the remainder on three small outer island grids.
TPL is interested in understanding the potential options for replacing its installed meter stock,
with a view to improving the credit management of its business, and potentially accessing the
functionality of smart metering technologies to improve the operation of its business.
Currently TPL disconnects close to 6% of its customers each month for non-payment of
electricity charges and is not able to recover the full cost of disconnecting and reconnecting these
customers.
Theft and meter bypass/tampering are also significant revenue protection challenges faced by
TPL that suggest some form of prepay metering solution would have a meaningful impact on the
payment behavior of its customers, and on TPLs quality of service to customers...
In addition to these specific revenue protection issues, TPL recognises that it has a range of
wider requirements including the move to more sophisticated tariffs, the ability to deal with
distributed generation and remote monitoring and/or enhanced control of certain elements of its
network which could be achieved through the use of Advanced Metering Infrastructure (AMI).
The purpose of this RFP is to find a suitable technology solution to meet TPLs requirements
that provide for some level of future proofing, while at the same time dealing with the
companys specific issues relating to revenue protection.
1.2
TPL is a state-owned enterprise, wholly owned by the Government of Tonga and operated as a
stand-alone company at arms-length under a concession overseen by an independent regulator.
TPL is a traditional, vertically integrated power supply company which serves four of the Tonga
archipelago of over 170 islands.
The main island of Tongatapu in the southern island cluster is the largest with some 80% of the
Tonga population living there.
Page: 6
Other systems are on Eua, also in the southern cluster, Haapai in the central cluster and Vavau
in the northern cluster. Each of these centres has a diesel power station and a medium to low
voltage distribution system.
Tongatapu has a small 11kV network, the three outer island networks currently operate at 6.6
kV. Some of these feeders are long relative to the voltage levels so that control of frequency and
voltage levels within acceptable ranges can be difficult. This is especially so for the low voltage
networks, given the low electricity demands of the connected customers.
With distributed generation located on these lines in the future, control problems and voltage
fluctuations will be exacerbated and must be explicitly evaluated in advance.
1.3
Glossary of Terms
Page: 7
Head-End means the meter head-end to be supplied by the Vendor to Tonga Power Limited
under the Contract having the functionality described in paragraph 5.7;
Issue Date means the issue date of this RFP;
MDM mean Meter Data Management;
Metering System means the Head-End, smart meters and the communications network that
together operates so as to deliver the functionality detailed within this RFP;
Normal Time means one-way communications between the Head-End and the smart meter that
takes longer that 5 seconds but which occurs within 30 seconds;
Notices to Proponents means clarification of particular items, additions to or subtractions from
this RFP issued by Tonga Power Limited from time-to-time in accordance with paragraph 3.5;
Preferred Proponent means the Proponent selected from the Short-Listed Proponents for
further negotiation in accordance with paragraph 3.1;
Proponent means the person or persons who lodge a Proposal in accordance with the RFP;
Proposal means a Proponent's proposal submitted in response to, and in accordance with, this
RFP;
RFP means this request for proposals, including all appendices, any addenda and any Notices to
Proponents;
Short-Listed Proponents means the Proponents whose Proposals have been selected for further
assessment in accordance with paragraph 3.1;
Smart Meters means the metering component of the AMI - generically meters with two way
communications
Support Services Agreement means the 15 year support services agreement to be entered into
by TPL and the Vendor contemporaneously with the Contract;
Technical Requirements means the technical requirements set out in the Technical
Requirements Overview in section Error! Reference source not found. and the Technical
Requirements in Appendix B;
TOU Means Time Of Use
Doc ID: 284/11/01, 16 November 2013
Page: 8
Page: 9
Scope of Supply
2.
This section sets out, at a high level, the scope of the system for which TPL is seeking Proposals
from Proponents. The specific requirements are set out in the Functional Requirements (being
section Error! Reference source not found. and Appendix B). Proponents may respond to
portions of the RFP rather than all of the AMI components described in the requirements section.
2.1
Smart Meters
Through this RFP, TPL is intending to enter into a long-term supply agreement with an AMI
vendor to purchase AMI meters, communications, meter Head-End software and Meter Data
Management solution. The number of smart meters purchased will depend on, amongst other
factors (refer paragraph 3.1), the price that the successful Proponent tenders.
The number of smart meters purchased could vary from 15,000 to 22,000 with possible ongoing
annual quantities of approx 250 meters.
TPL is seeking to purchase a modular smart meter in respect of the following physical or
functional features:
Mass Market Customers
Supply switching;
Load limiting;
Outage management
Page: 10
the above functions are essential and Proponents are asked to indicate the status of these
functions in their product roadmaps.
2.2
Head-End
TPL is seeking to purchase a Head-End which must interoperate with the smart meters.
The Head-End is software with functionality that:
(i)
(ii)
(iii) has a data warehouse to store meter asset data and the data collected from meters; and
(iv) a man-machine interface that can be used to compile and initiate tasks, register new
smart meters, view communications network data and that can be used to configure
individual meters.
Note that the Head-End may be embedded within the Meter Data Management System refer
below.
2.3
TPL is interested in accessing a MDM capability for the purposes of validating and processing
meter data to support billing and other utility functions. In addition to traditional MDM
capabilities TPL are seeking prepay management capabilities as either part of an MDM solution
or as a separate application that can be readily integrated with A MDM solution.
On this basis it will consider:
Purchasing a license to existing MDM software
Proponents should consider the scale of TPLs business and the appropriate fit for purpose MDM
solution for a Pacific Island nation in their responses.
Page: 11
2.4
Telecommunications
Additional Services
Proponents that wish to offer Additional Services can do so in the Response Schedules,
Appendix C.
Additional Services, that are not included in this RFP, could include:
It is important that Proponents offering Additional Services separate the costs of the Additional
Services from the pricing of the smart meters, Head-End, MDM and telecommunications (as
applicable). Furthermore Proponents should appreciate that any Additional Services offered will
not be evaluated as part of this RFP. If a Proponent that has offered Additional Services is
selected as the Preferred Proponent, then TPL may choose to discuss the offer of those
Additional Services. Proponents that do not offer Additional Services will not be penalised.
Page: 12
RFP Proposals
3.
This section sets out, at a high level, the requirements for Proponents' Proposals and the process
to be followed by Proponents and TPL. Proponents should ensure they comply with this section
3 and the specific Terms and Conditions of the RFP referred to in section 4.
3.1
TPL intends to evaluate and conform the Proposals to a common basis for evaluation. As part of
this process TPL may prepare a list of questions to obtain any additional or missing information
required from Proponents.
TPL intends to use a set of specific criteria and weightings for each component of this RFP,
including criteria such as:
Maturity of solution/services
Price of solution/services
The price evaluation will be based upon the component prices provided by Proponents together
with the expected operation and maintenance costs, including Proponent annual support costs.
Comparison of the different technologies will be made on an NPV basis over a 10 year period.
From the evaluation process TPL will select up to 4 Short-Listed Proponents. All Proponents
that submit Proposals will be advised in writing of their status following the evaluation process.
Short-Listed Proponents will be contacted to determine suitable dates for clarification visits,
reference site visits (refer section 6.2) and factory visits as required.
A TPL team will conduct the visits to obtain a clear understanding of the Short-Listed
Proponents':
technology offering(s);
Page: 13
engineering capabilities;
key personnel and resources responsible for delivering the Proponents solution;
support infrastructure;
technology roadmap;
commercial terms.
The TPL evaluation team may visit reference sites and discuss how the Proponents existing
solution has been implemented and what has been learnt from the ongoing performance of the
solution.
Following the visits programme, TPL will select a Preferred Proponent and notify all parties
accordingly. TPL will then commence contract negotiations with the Preferred Proponent.
3.2
Indicative Timetable
The indicative timetable for this RFP process is tabulated below. TPL reserves the right to vary
this timetable.
Activity
RFP Issued
Proponents confirmation of receipt
Proponents confirmation of intent to
respond
Last date for questions
RFP Closing Date (responses by email)
Last date for hard copy responses
Advise Short-Listed Proponents
Programme of visits commences
Preferred Proponent notified
Contract Awarded
Date
16 November 2013
18 November 2013
22 November 2013
06 December 2013
13 December 2013
20 December 2013
17 January 2014
20 January 2014
31 January 2014
28 February 2014
Page: 14
3.3
Communications
All communications with TPL relating to this RFP must be directed to:
John McCutcheon
TPL AMI Procurement Manager
Level 1, 79 Grafton Road, Grafton
PO Box 109628, Newmarket,
Auckland 1149, New Zealand
DDI +64 9 358 3503
Mobile +64 21 934 901
Email john@powerbusiness.co.nz
From the Issue Date of this RFP until a Contract is signed by both parties, all correspondence is
to be directed to the TPL AMI Procurement Manager. Proponents shall not be permitted to
communicate with other TPL personnel in relation to this RFP unless otherwise agreed with the
TPL AMI Procurement Manager.
3.4
Proponents are requested to notify receipt of this RFP within 24 hours from receipt by emailing
the form Acknowledgement of Receipt of RFP Form contained in Appendix D provided as a
separate electronic Microsoft Word format document.
Proponents are requested to notify their intent to respond or not as the case may be, by
completing the Intention to Respond Form, also contained in Appendix D provided as a
separate electronic Microsoft Word format document.
Proponents that do not notify their intention to respond (or not respond) within one week of the
Date of Issue of this RFP will be contacted to confirm receipt of the RFP and to ensure that any
Notices to Proponents are sent to the designated persons.
3.5
Notices to Proponents
TPL may issue Notices to Proponents to clarify this RFP or to effect modifications to this RFP
from time-to-time and at any time prior to the Closing Date. Each Notice to Proponents will be
issued to all Proponents who have notified TPL of their intention to respond. Upon such issue or
notification, each Notice to Proponents will form part of this RFP.
3.6
Format of Proposals
Page: 15
Proponents must submit all information required by this RFP in strict accordance with the forms
and formats contained in Appendices B and C. The reasons for this requirement are twofold:
(i)
to make it easy for TPL to evaluate and conform the responses; and
(ii)
Appendices B and C are issued in editable Microsoft Word format documents along with this
RFP. Proponents should expand the response portions of tables to accommodate the information
that they wish to provide to TPL. Information provided should allow a clear and detailed
evaluation of the Proponents solution.
Proposals submitted pursuant this RFP must be submitted electronically to the email address
listed in the Communications paragraph 3.3 above, in Microsoft Word format in English and by
one paper copy signed by a duly authorised person from the Proponent using the "RFP Proposal
Transmittal Form" in Appendix D, posted or delivered to the address in the Communications
paragraph 3.3.
Proponents may elect to respond against certain portions of the requirements outlined in this
RFP. Proponents are urged to complete the response forms fully of the components of the RFP
they are responding against as TPL may refuse to consider Proposals that do not provide all
information required by this RFP, or may score incomplete portions zero. Any non-compliance
with this RFP must be specifically highlighted by Proponents in their Proposals. Non-complying
Proposals may or may not be accepted by TPL at its sole discretion. Copies of brochures and
other Vendor material are not required.
3.7
Proponents may wish to offer multiple Proposals. In this case, Proponents should submit
complete separate Proposals including the Responses Schedules, Appendix B and C.
Proponents may wish to offer an Alternative Proposal. Alternative Proposals must accompany a
conforming Proposal. The Alternative Proposal must indicate that the Proponent can
demonstrate a technical or commercial advantage to be gained by TPL in implementing the
Alternative Proposal in preference to the conforming Proposal.
3.8
Delivery of Proposals
All Proposals must be delivered by email by 4pm, 13 December 2013 (Closing Date), to
john@powerbusiness.co.nz , with hard copies to follow by 20 December 2013, sent to the
offices of, or postal address as follows:
Page: 16
3.9
Validity Period
Proposals submitted pursuant to this RFP shall remain valid for a period of 3 months from the
Closing Date.
Page: 17
4.
The specific Terms and Conditions governing this RFP are contained in Appendix A. In the
event of any inconsistency between the specific Terms and Conditions and some other part of
this RFP, the specific Terms and Conditions take precedence.
Page: 18
5.
This section sets out, at a high level, the TPL requirements, including an indicative future state
AMI architecture and a description of the key underlying processes. Proponents should ensure
their Proposal addresses and complies with both this section Error! Reference source not found.
and the detailed Requirements for this RFP set out in Appendix B. Appendix B also serves as a
table of conformance. Proponents should use the provided Microsoft Word format document of
Appendix B to indicate their conformance with the Technical Requirements and all nonconformance and any departures/tags or commentary.
5.1
Conceptual Future State
The diagram below presents the high level conceptual future state of TPLs AMI architecture.
The highlighted portion shows the components that are either owned by TPL or managed via
outsourced service agreements with TPL.
CPE
Comms
Network
Payment
Channel &
Vending
System
AMI Headend
AMI MDMS
AMI
Prepaymt
Mgt System
CIS/Billing/
Asset/ Field
Mgt/
Integration
IHD
CIS/Billing/
Finance
Vending
System
Prepayment
Mgt System
TPLs Bank
Page: 19
Component
Owned by TPL
YES
NO
YES
NO
Supplier Partnership
YES
Arrangement
Vending Channels
NO
Supplier Partnership
NO
Vending System
NO
Supplier Partnership
NO
AMI Head-end
YES
YES
as a Services (SaaS) or
Outsourced back-office
service provider and
system arrangement
Meter Data Management
YES
System
YES
as a Services (SaaS) or
Outsourced back-office
service provider and
system arrangement
Prepayment Management
YES
System
YES
as a Services (SaaS) or
Outsourced back-office
service provider and
system arrangement
Customer
YES
NO
YES
Communications Channel
5.2
Core Components covered by this RFP
The diagram below shows the new components that are covered by this RFP.
The new components that are within the scope of this RFP are:
Smart Meters
Page: 20
The new components that are introduced in this future state but NOT in scope of this RFP are:
Vending System
The components that already exist in the current TPL business systems landscape that will have
to have integration points with the new components are:
Customer Comms
Vending Channels
Field Force
Portal
Vending
System
Prepay Mgt
System
Orion
AMI Head-end
System
(CIS/Billing)
Meter Data
Mgt
System
FileMaker
System
In Scope new
component
Out of Scope
existing
component
Finance
System
Page: 21
5.3
Standards
ANSI C12.19.
TPL appreciates that international standards have yet to mature in relation to smart metering but
where Proponents have developed their systems/products in accordance with Open Metering
System (OMS), or Device Language Message Specification (DLMS) Smart Metering Language
(SML) or other similar standards; such implementation should be noted in the Response
Schedules, Appendix B.
Telecommunications must comply with the following International Standard:
5.4
Page: 22
Capacity limiting;
Configurable levels of priority access to strategic devices (for network control and
monitoring); and
Ability to allocate meters/devices into multiple control groups (e.g. customer specific
and regional).
5.5
Modularity
TPL requires that smart meters are modular with respect to the following:
(i) Meter to Head-End communications;
(ii) Supply disconnect/reconnect; and
(iii) Load control relay(s).
5.6
Meters/Metering Equipment
5.6.1
Metrology
Page: 23
5.6.2
Configuration
Each order for meters will be accompanied with a configuration schedule indicating what
configuration is to be programmed into the meters and which of the modular options are to be
included into each type of meter.
5.6.3
Display
Although meters will be read remotely, meters are required to have a display that can display
various parameters that are listed in Appendix B.
5.6.4
Installation
Once installed by a qualified installer, the smart meter should self-configure onto the metering
network by communicating with the Head-End.
5.7
Head-End
meter data repository storage of all required meter data records and events scalable
up to a minimum of 50,000 meters;
(ii)
(iii)
a man-machine interface that can be used to compile and initiate tasks, view
communications network data and that can be used to configure individual meters;
(iv)
(v)
the ability to interface to TPL IT and SCADA systems two way communications.
5.7.1
Proponents are asked, in the Response Schedules, Appendix B to specify the minimum
requirements for hardware and operating systems to support the Proponents Head-End software
so that TPL can independently price these. Proponents may also offer to supply hardware and
operating software as an Additional Service.
Page: 24
Proponents not offering to supply Head-End software must provide details of a Head-End
software vendor who offers Head-End software which has been demonstrated to successfully
interoperate with the Proponents meters. Furthermore it is a requirement of this RFP that the
proposed Head-End has been in commercial operation for at least one year.
5.7.2
Proponents should clearly indicate their software licensing regime including how software
upgrades will be provided and whether upgrades that are not gratis will be optional and any
implications for ongoing support of software if TPL chooses not to upgrade. Licences should be
perpetual or at least available for a period of not less than 15 years. If there are any licensing
costs these should be included in the pricing schedule (Appendix C).
If third party intellectual property (including software) is utilised in a Proponents solution the
Proponent must warrant that it has the rights to use such intellectual property. Any costs
associated with the use of third party software should be clearly set out in the Proposal.
The costs of software licences will be factored into the evaluation by TPL who will adopt a
holistic evaluation methodology.
5.8
Interfaces
5.8.1
TPL may wish to have specific interfacing developed to connect to their IT systems (e.g. billing,
GIS, financial asset management) and SCADA systems (e.g. outage management, network
switching, load control). Proponents must indicate the feasibility of, and provide other
appropriate information (including pricing) relating to, developing appropriate bespoke
interfacing. As a minimum, Proponents must indicate that they will provide sufficient
interfacing details for TPL or a third party developer to develop an appropriate interface.
5.9
5.9.1
Telecommunications Technologies
TPL has restricted technologies that provide two-way communications between the meters and
their Head-End to:
(i) RF Mesh;
(ii) Power Line Carrier / Distribution Line Carrier
Page: 25
In considering the communications technology, TPL is looking for a network architecture that
delivers on a number of performance measures, including:
high coverage rates in a challenging Pacific Island environment [signal strength and
distance];
scalable architecture which supports densely clustered and also widely spread meter
locations and also needs to support regionally diverse meter locations that access a
common centrally held database;
potential for local control in the event a region becomes isolated from the central data
store;
a well dimensioned network that supports the types of traffic patterns generated by both
Fast-Time and Normal-Time meter communications particularly at peak periods;
Page: 26
In responding to the RFP each Proponent should illustrate how its communications solution
meets these requirements.
5.9.3
Future
Current OR
Requirement
Normal Time
Requirement
Task
Fast Time
The following table provides requirements for Head-End to meter communications. Fast-Time
response is less than 5 seconds. Normal Time response is less than 30 seconds. Proponents
should clearly indicate any non-compliance with these times to communicate in their Proposal.
Automated Meter
Reporting
Meter reporting of kWh
power consumption
Customer Services
Prepayment functionality
volume registers
Page: 27
Future
Current OR
Requirement
Normal Time
Requirement
Task
Fast Time
Notification (include in
response if available)
Outage Cause Analysis
teams
Outage Information
Monitoring Feeders
Volt / VAR measurement of
via meters
Operation of capacitors
system capacity /
constraints
management.
load
Page: 28
flow calculations
system capability
Perform maintenance, move
Future
Current OR
Requirement
Normal Time
Requirement
Task
Fast Time
load or equipment as
necessary
Load Balancing
Across phases.
Distribution Automation
Automated Load Switching
fault switching.
Monitoring operating state
of distribution assets
Controlling distribution
Load Control
Under frequency load
shedding
(initiation
(reset)
remote)
customer premises
Time based load control
Revenue Protection
Locating and reconciling
unidentified losses
Page: 29
Future
Current OR
Requirement
Task
Normal Time
Fast Time
Requirement
Other
Network visibility
Reporting interface into
SCADA
and outage.
Distributed generation
Messaging
5.9.4
In-home messaging
Network Coverage
Head-End to meter connectivity is required to cover a minimum of 95% of meters on the TPL
network. Proponents that have compatible solution(s) to extend the coverage to the remaining
meters can include descriptions of those solutions but are not required to provide pricing at this
juncture.
Proponents are required to provide complete pricing for their solutions in the Response
Schedules, Appendix C but that pricing will exclude all facets of the solution that are not
completely under the Proponents control such as:
(i) Local Authority consents;
(ii) Costs of co-locating with established communications operators at particular sites;
(iii) Land owner agreements and easements;
(iv) Third party agreements for back haul services; and
Page: 30
5.10.1
Page: 31
Exceptions Management
o Efficient exceptions management at file import, record management, admin data
management and process execution levels
Integration Layer
o Flexible configuration of integration with external system either via messaging or
batch file transfer
o Secure integration layer with identity management of source
Page: 32
Page: 33
Efficient and reliable importing of connection status information from the backoffice system
Exceptions Management
o Efficient exceptions management at file import, record management, admin data
management and process execution levels
Integration Layer
Page: 34
o
o
Page: 35
6.
Responsibilities
Once the Preferred Proponent(s) sign a Contract with TPL for the respective components of this
RFP, it (they) will become the Vendor(s). This section sets out, at a high level, the
responsibilities that the Vendor(s) will be required to undertake and, where applicable, the
relevant information Proponents are required to provide. More details of the Vendor(s)'
responsibilities can be found in the Conditions of Contract in Appendix E.
6.1
6.1.1
Design
As between TPL and the Vendor(s), the Vendor(s) will be responsible for the design of the
Head-End, smart meters, the telecommunications equipment supplied by the Vendor(s) and the
telecommunications network (which, if applicable, will include the radio network architecture
and the configuration of the radio equipment) and the MDM.
6.1.2
Installation
The Head End Vendor will be responsible for the installation of the Head-End and the training of
TPLs field service providers who will install the smart meters.
The Telecommunication Vendor, as applicable, will be responsible for training TPLs
telecommunications network field service providers who will install the telecommunications
equipment.
6.1.3
Commissioning
The Vendor(s) will be responsible for commissioning and testing the Head-End and smart meters
and, if applicable, the telecommunications equipment and MDM. TPL reserves the right to
witness that commissioning. The Vendor will issue a Final Acceptance Certificate after the
Metering System has satisfactorily passed all the commissioning tests.
6.2
Reference Sites
Proponents are required to provide a schedule of reference sites (Response Schedules, Appendix
B) where TPL can view their proposed solution working and discuss related matters with client
organisations. Preferred Proponents are required to give access to the reference sites listed in
their Proposal to TPL personnel as part of the evaluation process.
Page: 36
6.3
Factory Acceptance Testing
TPL may wish to undertake or witness factory testing of the Vendors solution or part of that
solution. Proponents are to indicate the location for such testing in the Response Schedules
(Appendix B).
6.4
Installation Support
The Vendor is required to be available at 48 hours' notice to provide on-site technical support
during the initial installation phase of the meter roll-out programme which will be for a period of
3 months from delivery of the initial order and thereafter to provide non-urgent on-site support at
72 hours' notice.
Vendors that have special tools and software program(s) that will aid the installation process
must provide details and pricing in the response Schedules, Appendix C.
All installation support costs are to be provided in the Response Schedules, Appendix C.
6.5
Training
The Meter Vendor is required to provide training to TPL's (or the TPL Distributors') installation
contractors on the correct methods of installation of all types of their meters one month ahead of
TPLs start date for meter installation. TPL will give the Vendor one months' prior notice of the
start date for meter installation.
The Head End Vendor will be required to provide training in the operation and maintenance of
the Head-End and Head-End software.
If the telecommunications solution includes RF Mesh communications solutions, the
Telecommunications Vendor will be required to provide training in the operation and
maintenance of those solutions.
TPL requires that the Vendor(s) provides sufficient training to minimise any requirement on TPL
to use the Vendors staff on an ongoing basis. Whilst some training may be required at the
Vendor's factory it is expected that the majority of training will occur in Tonga.
All training costs and venues are to be set out in the Response Schedules, Appendix C. Ongoing
support costs are to be priced separately from deployment and commissioning training.
6.6
Documentation
Page: 37
The Vendor(s) must provide all documentation required by TPL to operate and maintain the
systems provided by the Vendor (s). This documentation shall be provided in electronic format
and shall include, but shall not be limited to:
Operating manuals;
Maintenance manuals (both hardware and software and including any procedure for
undertaking system upgrades);
The Vendor(s) shall provide samples of the documentation which shall be approved by TPL
before acceptance.
6.7
Support Services
The Vendor(s) are required to provide support for their proposed solution for a period of not less
than 15 years under a Support Services Agreement to be entered into between TPL and the
Vendor.
Proponents are required to detail the levels of support proposed and the associated annual costs
in the Response Schedules, Appendix C
First Level support will be provided by TPL field service staff and Second Level will be
provided by TPLs meter/communication specialists.
TPL requires Third Level support to be provided by the Vendor. This support may, on
occasions, require site visits otherwise it is expected that most problems will be resolved using
phone and email communications.
6.8
Spare Parts
Proponents are required to list any recommended spare parts required, other than meters, to be
held by TPL. Spares should include Head-End componentry as well as numbers of each spare
Page: 38
part. The numbers should be based on a 20,000 meter network. The Vendor is required to make
spare parts available to purchase for a minimum period of 10 years.
Proponents are required to nominate quantities and prices for spare parts in the Response
Schedules, Appendix C.
6.9
Test Equipment
Proponents should specify any test equipment essential for the installation and commissioning of
the Head-End, meters and communications network that their commissioning personnel will not
provide during the period of system commissioning.
Proponents should also specify any test equipment that is considered necessary for TPL to own
or to have access to in order to operate and/or maintain the meters, Head-End or communications
network.
6.10
Supply Orders
TPL intends to enter into a non-exclusive, long term (not less than 15 years) supply agreement
with the Vendor to supply smart meters. The Vendor will be required to supply interoperable
meters for the duration of the Contract.
Most of the smart meters will be installed in residential premises but some agricultural,
commercial and light industrial customers will also be supplied with 3 phase smart meters.
The approximate ratios of meter types are:
3 phase CT 1%
The Vendor is only required to supply smart meters upon receipt of an order to supply from TPL.
Following the first supply order, the time from receipt of order to delivery in Tonga shall be 3
months (subject to the volume of meters to be supplied in subsequent orders, which will be
discussed with Short-Listed Proponents).
TPL would like to have the first order supplied, in Tonga during the 3rd quarter of 2014.
Proponents should indicate if this date is achievable and if not what the firm supply date would
be. Proponents should also indicate whether they can supply ahead of the required delivery date
Page: 39
and provide the early delivery date. Proponents should assume a quantity of 5,000 meters for the
initial shipment.
Proponents should indicate their flexibility to respond to just in time requests for orders by
reconfiguring meters in stock for shipment.
6.11
Systems Commissioning
The Vendor is required to take responsibility for commissioning the communications network
and provide at least one commissioning engineer for a period of not less than 4 weeks to
undertake that task. During this period the Vendors commissioning personnel shall provide onthe-job training to TPL personnel.
At the end of the commissioning process, the Vendor's lead commissioning engineer is required
to certify that the system complies with the Technical Requirements and is fit for its purpose and
ready for final acceptance testing. Commissioning will be declared complete by the TPL project
manager after reviewing the Vendors completion certificate and undertaking final acceptance
testing.
6.12
Warranties
The Vendor(s) are required to warrant the reliable, safe and fit for purpose operation of all
products supplied to TPL.
The Vendor(s) are required to warrant that a Head-End has capacity to interface with 50,000
smart.
The Vendor(s) are required to warrant that services provided by the Vendor(s) will be rendered
by qualified and competent personnel and that those services will be delivered in keeping with
good industry practice for those services.
The Vendor(s) are required to warrant that the Head-End will output data appropriate for the
purpose for which TPL is acquiring the system.
6.13
Escrow
Source code for any software that is specifically developed for TPL by the Vendor(s) shall be
delivered to TPL (including source materials). The source materials for any other software used
in the Vendor's solution shall be placed in escrow.
Page: 40
7.
Pricing
7.1
Equipment
The Response Schedules, Appendix C, requires Proponents to list their respective component
prices. TPL will commit to a minimum order quantity (MOQ) of smart meters over minimum
order period (MOP) of two years. This commitment will be made in the Contract. TPL expects
Proponents to factor this commitment into their pricing.
The unit meter prices to be paid for each new order for meters during the MOP will be fixed for
the duration of the MOP.
There will be a price reset at the second and every subsequent anniversary of the Acceptance
Date to take into account any change in Vendors standard pricing but if the Vendor's standard list
price is less than the adjusted price then the former will apply for the next 12 months.
7.2
Services
Services that relate directly to the procurement, installation and commissioning of meters are to
be priced on a daily rate basis plus disbursements. Post commissioning and system handover
ongoing support services are to be priced as an annual fee or on a daily rate basis plus
disbursements as is the Proponent's policy.
Prices for Additional Services (refer Section 2.5) are to be priced on a fixed fee and/or daily rate
basis plus disbursements.
7.3
Currency Exchange
Proponents should refer to clause 21 of the Terms and Conditions of RFP in Appendix A for
details on nominated currencies and how currency exchange rates will be addressed.
Page: 41
8.
Contract
The proposed key terms for the Contract resulting from this RFP are set out in Appendix E. The
Preferred Proponent will be expected to enter into a Contract that substantially reflects these
terms; therefore Proponents should clearly identify any proposed departures from/tags to the key
terms in their Proposal.
Page: 42
2.
Responsibilities of Proponents
The information contained in this RFP or otherwise provided to Proponents by TPL in
connection with this RFP is for the purpose of the Proponents considering, and
responding to, this RFP. TPL has taken reasonable steps to ensure that the information
provided is accurate, complete and not misleading, but does not warrant or represent
that this is the case.
No assurances or representations are made by TPL, whether before or after the issue of
this RFP or during the RFP process and each Proponent accepts and acknowledges, and
is deemed to have accepted and acknowledged that its decision as to whether to submit
a Proposal or not, and the Proposal itself, is made solely on its own judgement and not
upon any express or implied representation, statement or warranty made by TPL, or on
behalf of TPL.
Each Proponent acknowledges that it is its own responsibility, before submitting a
Proposal, to:
examine this RFP, any documents referenced by this RFP and any other information
made available to it by TPL or via TPLs website (www.tongapower.to)
identify and obtain all information it may require to prepare and submit its Proposal;
obtain independent advice (including legal and accounting advice);
consider all the risks, contingencies, impacts and other circumstances which may
affect its Proposal and its ability to perform in accordance with it; and
satisfy itself as to the correctness and sufficiency of its Proposal, including the
costings and prices stated in the Proposal, and all information provided with its
Proposal.
Without limiting this section 2, in submitting a Proposal, each Proponent acknowledges
and agrees that it has not relied on any express or implied statement, representation or
warranty as to the truth, accuracy or completeness of the information contained in this
RFP or otherwise provided to the Proponent by TPL.
3. TPL has no Obligations
No legal or other obligations will arise between a Proponent and TPL in relation to this
RFP, or in relation to the process, conduct, or outcome of this RFP, unless and until that
Proponent and TPL have entered into a binding written Contract and the Contract is, or
becomes, unconditional in which case the Contract will be binding on the parties only in
accordance with its terms.
Page: 43
This RFP does not constitute an offer by TPL to acquire services, buy or sell assets or
enter into any arrangement with any person.
This RFP does not commit TPL to proceed with, continue, or follow, the process
outlined in this RFP or to evaluate any particular Proponent's Proposal or enter into any
discussions, negotiations or contractual arrangements with any Proponent.
Nothing in this RFP, or in the relationship of TPL and each Proponent, imposes any
duty of care on TPL and any such duty of care is expressly excluded.
The provisions of this Section 3 apply notwithstanding any other provision of this RFP
and in the event of any inconsistency, this Section 3 will take precedence.
4.
Submission of Proposals
Proposals must be submitted in accordance with, and must comply with, the terms of
this RFP.
Each Proponent warrants and represents to TPL that:
the information contained in, and submitted with, its Proposal is complete and
accurate in all material respects and may be relied upon by TPL; and
the provision of the information contained in, and submitted with, its Proposal, and
the use of it by TPL or any third party to whom TPL may make such information
available to:
o for the evaluation of, and discussions in respect of, the Proposal or any offer by
the Proponent to provide the Services; and/or
o in the negotiation of the terms of any contract in relation to the Proposal
(whether or not resulting in a Contract),
o will not breach any third party intellectual property rights,
and each Proponent indemnifies TPL against all direct losses incurred by TPL as a
result of a breach of such warranties or the representations being incorrect.
A Proposal, once submitted to TPL, may be varied by the Proponent only on the request
of TPL, and will remain open for consideration by TPL for 6 months after the Closing
Date.
Proponents may be asked to clarify their respective Proposals or provide additional
information in connection with the evaluation of their Proposals. These requests will
require prompt action and must be responded to in writing in the time specified in the
request.
Failure in doing so may result in the Proponent's Proposal not being considered any
further.
5.
Proposal Qualifications
Any qualifications to a Proposal must be clearly recorded in the Proposal and in the
relevant sections of the Appendices. Any qualifications not clearly recorded in this
manner may be excluded from further consideration in relation to this RFP.
Proposals submitted subject to significant qualifications may be considered as
alternative Proposals and will, if evaluated, be evaluated by TPL accordingly.
Page: 44
Subcontracting
TPL may consider Proposals where the Proponent subcontracts one or more portions of
the services to others. If a Proponent's Proposal includes services to be performed by
subcontractors or third parties, the names of the subcontractors or third parties, and the
particular services that they will each perform, must be clearly identified.
The Proponent must ensure that there is a single point of contact for account
management and assume total responsibility for the actions of the subcontractors or
third parties and will not be relieved of any of its obligations under the Proposal for the
supply of any goods or services from subcontractors or third parties.
7.
Joint/Consortia Proposals
TPL may accept Proposals from multiple joint Proponents (including consortia). If a
joint or consortium Proposal is submitted, a clearly identifiable, single organisation is
required to be responsible for the joint Proponents. The following information is
required:
a detailed description of the proposed:
o legal relationship between each joint-Proponent/member of the consortium;
o management structure for the joint Proponents/consortium;
o roles and responsibilities of each joint-Proponent/member of the consortium;
o primary responsible organisation for TPL to direct contract, management and
performance engagement issues; and
o the manner in which the joint Proponents/consortium will enter into contracts,
including the proposed party or parties to enter into agreements with TPL; and
confirmation that either:
o each joint-Proponent/member of the consortium:
(a) appoints a nominated member of the consortium to represent it in all
discussions and negotiations with TPL in relation to this RFP (with such
nominated member being authorised to also represent all other joint
Proponents/members of the consortium); and
(b)authorises that nominated member party to bind it in relation to those
matters; and
(c) is jointly and severally liable for the performance of all jointProponents/members of the consortium under any agreement that may be
entered into with TPL; or
o one joint-Proponent/member of the consortium is fully liable for the
performance of all others; and
Page: 45
Presentations
Proponents may be invited to meet with representatives of TPL and its advisers after the
Closing Date to make presentations relating to their Proposals and to take part in a
question and answer session. The dates for these presentations (if applicable) will be
notified by TPL to the Proponents in advance. The purpose of the presentations is to
assist TPL with its evaluation of the Proposals. The Proponents may be requested to
confirm in writing any statements made by the Proponents during the presentations.
Any questions raised or statements made by TPL at the presentations are subject to
these terms and conditions.
9.
10.
No Canvassing or Influencing
Proponents must not, directly or indirectly, canvass or seek to influence the decision of
any TPL employee, consultant or contractor acting on behalf of TPL at any stage in
connection with this RFP. Any Proponent who indirectly or directly canvasses or seeks
to influence any employee, consultant or contractor acting on behalf of TPL concerning
any aspect of this RFP may in TPLs discretion be disqualified from further
consideration for this RFP.
11.
Costs
Each Proponent must pay its own costs in connection with this RFP, including but not
limited to:
any communications or negotiations with TPL;
any meetings, presentations or interviews with TPL;
any Proponent briefings, meetings and/or site visits;
any legal costs and expenses and any professional consultants fees; and
Page: 46
13.
Confidentiality
The information supplied by TPL (either itself or through its consultants or advisors) in
connection with this RFP that is not publicly available is confidential. The Proponent
must not release or disclose any such information to any other person, or use any such
information to the detriment of TPL or for any purpose other than for the purposes of
this RFP. TPL may require a Proponent(s) to enter into a deed of confidentiality in
relation to this RFP at any stage.
TPL will keep Proposals received confidential provided that Proposals may be
disclosed:
to any persons advising or assisting TPL in relation to this RFP; and
as may be required by law.
TPL is not required to keep the name of any Proponent confidential.
No advertisement, press release, public statement or other information relating to the
acceptance or otherwise of any Proposal may be published in any newspaper, magazine,
journal, or other advertising media without the prior written permission of TPL.
14.
15.
No Anti-Competitive Behaviour
Proponents must not, in the preparation of any Proposals, or in any discussions or
negotiations with TPL, engage in collusive, deceptive or improper conduct.
16.
Conflict of Interest
Each Proponent must disclose to TPL, both at the time of submitting the Proponent's
Proposal and on a continuing basis, any conflict of interest or potential conflict of
interest in relation to the matters covered by this RFP or any subsequent arrangement
that may be entered into by the Proponent in connection with the matters covered by
this RFP.
Page: 47
17.
Liability
Neither TPL, nor TPL's employees, advisers, contractors or agents, will be liable (in
contract, tort (including negligence), equity or otherwise) for any direct or indirect
damages, losses, costs or expenses (including wasted costs, loss of profits or loss of
business opportunity) incurred by a Proponent or any other person and arising in any
way in connection with this RFP, including in connection with:
the evaluation of Proposals;
the preparation of any Proposal;
any investigations of, or by, any Proponent;
the acceptance or rejection of any Proposal;
the variation, suspension or cancellation of the process outlined in this RFP; or
any information given, or not given, to a Proponent.
Each Proponent waives any rights it may have to make a claim against TPL, or TPL's
respective officers, employees, contractors, agents or advisers arising out of or in
connection with this RFP.
Nothing contained or implied in, or arising out of, this RFP shall be construed as legal,
financial or other advice of any kind.
18.
Governing Law
This RFP and any contract entered into under this RFP shall be construed according to
and governed by Tongan law. Each Proponent agrees to submit to the non-exclusive
jurisdiction of Tongan courts in any dispute concerning this RFP or any Proposal.
19.
Verbal Advice/Information
TPL will not be bound by any verbal advice given or information furnished by any of its
officers, employees or agents in respect of this RFP. An answer or clarification relating
to any matter set out in this RFP will only be made by TPL in accordance with this RFP.
20.
General Conditions
TPL reserves the right, at its absolute discretion, to:
Not consider, or reject, any Proposal even if it complies with all requirements of this
RFP.
Not accept or award a contract to the lowest priced Proposal, the highest scoring
Proposal or any other Proposal that may be received.
Consider and accept a Proposal even if it is received after the Closing Date, does not
comply with the requirements of this RFP or is non-conforming in any respect with
this RFP.
Not give any reason to any person for the rejection, failure or otherwise of any
Proposal, or any suspension or cancellation of this RFP.
Page: 48
Negotiate with any Proponent (to the exclusion of any other Proponent), at any time
before, or after selection of Short-listed Proponents or Preferred Proponents, and
upon any terms and conditions.
Deal separately with any divisible element of any Proposal, unless the relevant
Proposal specifically states that those elements must be taken collectively.
Seek clarification and/or adjustment of any Proposal.
Award a contract for all or part of any combination of parts of the supply of
equipment and services under this RFP to one of more Proponents.
Waive any irregularities or failures by a Proponent to comply with any of the
requirements in this RFP.
Amend any part of this RFP, or any associated documents (including any date and
the scope of any requirements to be met by any Proponent), by issuing a written
amendment notice.
Suspend or cancel (in whole or in part) this RFP and/or issue a new RFP.
Conduct or not conduct reference checks or credit checks on Proponents.
Re-advertise for Proposals.
Not enter into any contract in relation to the supply of equipment and services under
this RFP or enter into one or more contracts in relation to this.
Obtain similar services from any third party and not deal exclusively with any
Proponent.
Evaluate each Proposal against criteria, and in accordance with an evaluation
process, determined by TPL.
Give whatever weight it considers appropriate to any policy or criteria relating to this
RFP or evaluation of any Proposal.
Take account of any other relevant information that TPL may have in its possession
and to make enquiries of any person to assist it in the evaluation of Proposals.
Otherwise conduct the evaluation and contract award processes for the services in
any manner it sees fit.
21.
Page: 49
excess of 2%) between the TOP and the other currency, from the end of the Validity
Period to the date of the Contract.
Page: 50
Appendix B: Requirements
1.
Metrology
1.1
Core Services
Requirement
Background
COR.BRQ.01
COR.BRQ.02
Compliance / Alternatives
Page: 51
Requirement
Background
COR.BRQ.03
COR.BRQ.04
COR.BRQ.05
COR.BRQ.06
Compliance / Alternatives
Page: 52
Requirement
Background
Compliance / Alternatives
system.
Data formats should be
commonly used industry
protocols (such as XML, or
already existing data swapping
file formats) through which all
authorised service users can
access the services provided via
the AMI system.
COR.BRQ.07
COR.BRQ.08
Page: 53
1.2
On Demand Services
Requirement
Background
ODS.BRQ.01
ODS.BRQ.02
ODS.BRQ.03
ODS.BRQ.04
Compliance / Alternatives
Page: 54
Requirement
Background
Compliance / Alternatives
or received as a batch
ODS.BRQ.05
ODS.BRQ.06
ODS.BRQ.07
Page: 55
Requirement
Background
Compliance / Alternatives
future
ODS.BRQ.08
ODS.BRQ.09
ODS.BRQ.10
Page: 56
Requirement
Background
Compliance / Alternatives
reporting.
Page: 57
1.3
SRS.BRQ.01
Background
Compliance / Alternatives
Page: 58
Requirement
Background
Compliance / Alternatives
this functionality.
SRS.BRQ.02
SRS.BRQ.03
Page: 59
1.4
Reporting
Requirement
Background
REP.BRQ.01
REP.BRQ.02
REP.BRQ.03
Compliance / Alternatives
Page: 60
Requirement
Background
Compliance / Alternatives
1.5
Fault Management
Requirement
FMT.BRQ.01
Background
Compliance / Alternatives
Page: 61
1.6
Metrology
Requirement
MET.BRQ.01
MET.BRQ.02
Min Current
80 Amps (1 phase)
100 Amps (3 phase Whole Current)
6 Amps (3 phase CT)
MET.BRQ.03
MET.BRQ.04
Terminal configuration
2 screws, slotted head combi
BS5685 (1 phase)
DIN43857 (3 phase)
MET.BRQ.05
Operating Voltage
230VAC +/- 15% (1 phase)
400VAC +/- 15% (3 phase)
Compliance / Alternatives
Page: 62
Requirement
MET.BRQ.06
Environmental Protection
IP53
MET.BRQ.07
MET.BRQ.08
International Standards
IEC62052 Pt 11 and 21
IEC62053 Pt 23, or
ANSI C12.19
MET.BRQ.09
Protocols
AMS
DLMS
SML
MET.BRQ.10
MET.BRQ.11
MET.BRQ.12
Pulse output
DIN 43864 or IEC6253-31
MET.BRQ.13
Indicators
Pulsing LED for consumption
MET.BRQ.14
Compliance / Alternatives
Page: 63
Requirement
Compliance / Alternatives
kW
kWh (last account)
Tariff
Meter status (disconnected, tamper)
Retailer and telephone number
Communications signal strength for
wireless communications (optional)
Pre-pay (credit? other)
Alphanumeric messaging
MET.BRQ.15
Operating Temperature
Minus 20 to plus 50 degrees C
MET.BRQ.16
Labelling
Asset number, bar code (to EAN Standard
EAN 128), logo
MET.BRQ.17
Power Consumption
Normal continuous power consumption for
steady-state metering with communications
in stand-by mode
MET.BRQ.18
MET.BRQ.19
MET.BRQ.20
Page: 64
1.7
The following options have been identified as essential (E), desirable (D) of interest (I). The Proponent should clearly indicate whether the
functionality is currently in commercial production, is being developed, could be developed or not available. If the particular function is being
developed, please indicate when the function will be available.
Requirement
MCO.BRQ.01
MCO.BRQ.02
Importance
Compliance / Alternatives
E
E
Load Control
MCO.BRQ.03
MCO.BRQ.04
MCO.BRQ.05
MCO.BRQ.06
MCO.BRQ.07
MCO.BRQ.08
Other
Page: 65
SPF.BRQ.02
SPF.BRQ.03
SPF.BRQ.04
Storage Registers
Require ability to program a minimum of 5 registers per element
Backup power supply - battery / Super cap capacity to power meter data
for period of up to 7 days without mains power
SPF.BRQ.05
SPF.BRQ.06
Meter Security
- Security levels for whole of meter compliant with recognised internal
standards
SPF.BRQ.07
Meter Registration
-Auto meter registration on power up
-Unique identification and addressing
-Programmed firmware upgrades and rollback
SPF.BRQ.08
Compliance / Alternatives
Page: 66
Requirement
Compliance / Alternatives
Power Quality
-Voltage sag/swell recording
-Voltage imbalance
-Current imbalance
-Power factor
-Harmonic measurement
- Alert notification with (remotely configurable)preset trigger level
SPF.BRQ.10
Tamper Alert
- Removal of meter cover
- Provision for conventional seal (non-lead based)
- Bypassing and reverse current detection
SPF.BRQ.11
SPF.BRQ.12
Load Control
- Store two different Time of Day (ToD) load control tables.
- Switch between active and alternate ToD tables at a preset date and time
- Accept remote overriding load control commands
SPF.BRQ.13
Tariff Tables
Page: 67
Requirement
Compliance / Alternatives
Disconnection/Reconnection
- Local / remote report on connection status
- Soft reconnection support a rearmed status allowing on-site reconnection via
enable button on the meter
Hard Reconnection support on-site reconnection without the need for button
push at meter
- Describe any additional security / handshake features that enable remote
reconnection
- Display retailers name and phone number when disconnected
SPF.BRQ.15
Page: 68
Head-End
SPF.BRQ.16
Describe the history of the development of the Head-End proposed and detail
how frequent new releases are provided and the release strategy for upgrades.
SPF.BRQ.17
SPF.BRQ.18
Describe the resources used for installing and configuring the Head-End
Describe the hardware requirements for the Head-End software
SPF.BRQ.19
SPF.BRQ.20
SPF.BRQ.21
SPF.BRQ.22
Compliance / Alternatives
EXI.BRQ.03
External field contractors: Is there provision for field contractors to verify meter
installations?
EXI.BRQ.04
Page: 69
1.10 Delivery
DEL.BRQ.01
DEL.BRQ.02
Product Delivery
Advise delivery date from receipt of order for Meter components sufficient to
build, commission and to operate the Meter Network commercially
Flexibility to respond to just in time request for orders, to reconfigure meters in
stock before shipment.
List 3 reference sites where TPL can visit to view the Meter technology being
offered in commercial operation.
Page: 70
Set out the temporal roadmap for the ongoing development of the Head-End and
Meter technology
Page: 71
2.
2.1
Telecommunications
Communications Response Times
The following table indicates TPLs desired times to communicate between the Head-End and Meter.
Requirement
Explanation
Individual
Meters
Group of Meters
(1,000 Meters)
90%
99.9%
5 10
secs
1 minute
5 minutes
30 minutes
Minimum scheduled
requirement
24 hours
72 hours
TEL.BRQ.04
TEL.BRQ.05
TEL.BRQ.01
TEL.BRQ.02
TEL.BRQ.03
5 secs
30 seconds
Proponent Response
30 seconds
Page: 72
Requirement
Explanation
Individual
Meters
Group of Meters
(1,000 Meters)
90%
TEL.BRQ.06
Proponent Response
99.9%
5 minutes
Page: 73
2.2
MMC.BRQ.02
MMC.BRQ.03
MMC.BRQ.04
MMC.BRQ.05
Is the aerial for the modem integrated into the modem or connected
separately?
MMC.BRQ.06
MMC.BRQ.07
MMC.BRQ.08
What is the mean time between failure (MTBF) for the modem
Vendor Proponent
Page: 74
2.3
MHC.BRQ.02
MHC.BRQ.03
MHC.BRQ.04
MHC.BRQ.05
MHC.BRQ.06
MHC.BRQ.07
MHC.BRQ.08
Proponent Response
Page: 75
2.4
Security
Requirement
SEC.BRQ.01
SEC.BRQ.02
SEC.BRQ.03
SEC.BRQ.04
SEC.BRQ.05
SEC.BRQ.06
SEC.BRQ.07
Proponent Response
Page: 76
2.5
Proponent Response
Page: 77
2.6
Communications Technology
Complete the table below which is relevant to the proposed telecommunication Network solution:
2.6.1
Mesh Solution
Requirement
MSH.BRQ.01
Radio spectrum bands in which the equipment will operate, note if licensed or
unlicensed spectrum?
MSH.BRQ.02
MSH.BRQ.03
MSH.BRQ.04
MSH.BRQ.05
MSH.BRQ.06
MSH.BRQ.07
MSH.BRQ.08
MSH.BRQ.09
Does the mesh network utilise dedicated relays / repeaters to extend the mesh
Typical communications latency across the mesh component of the network?
MSH.BRQ.10
What communications protocol is used for the WAN connection (GPRS, 3G, other)
Proponent Response
Page: 78
2.6.2
PLC/DLC
Requirement
PLC.BRQ.01
PLC.BRQ.02
PLC.BRQ.03
PLC.BRQ.04
PLC.BRQ.05
PLC.BRQ.06
PLC.BRQ.07
What communications protocol is used for the WAN connection (GPRS, 3G, other)
2.6.3
Proponent Response
LRR.BRQ.01
Radio spectrum bands in which the equipment will operate, note if licensed or
unlicensed spectrum?
LRR.BRQ.02
LRR.BRQ.03
LRR.BRQ.04
Proponent Response
Page: 79
Requirement
Proponent Response
Radio Standards/Compliance?
LRR.BRQ.06
LRR.BRQ.07
LRR.BRQ.08
2.7
Reporting
Fault Events
TRT.BRQ.01
2.8
Reporting on network fault events when they occur and summary reporting at
selectable periods.
Delivery
Product Delivery
TDE.BRQ.01
Page: 80
2.9
Reference Sites
References
TRF.BRQ.02
2.10
List 3 reference sites where TPL can visit to view the telecommunications technology
being offered in commercial operation state location and names and contact details
of Proponent clients that will agree to act as referees.
Technology Roadmap
Roadmap
TTR.BRQ.01
Set out the temporal roadmap for the ongoing development of the
telecommunications technology proposed.
TTR.BRQ.02
Page: 81
3.
For each question, proponents are requested to specify whether their solution meets the functionality that is required. In response to each
question, please indicate in the space provided:
F (Full)
P (Partial)
N (No)
Response
Response Detail
(F/P/NR/N)
Page: 82
Response
Response Detail
(F/P/NR/N)
Page: 83
Response
Response Detail
(F/P/NR/N)
Page: 84
Response
Response Detail
(F/P/NR/N)
Page: 85
Response
Response Detail
(F/P/NR/N)
available.
Exceptions Management
MDM.BRQ.22 Ability to raise exceptions during file or
data import at the file level, record level,
technical validation level and business
validation level.
MDM.BRQ.23 Ability to raise exceptions during data
processing e.g. VEE batch process failures.
MDM.BRQ.24 Ability to resolve exceptions in batch or for
individual records.
MDM.BRQ.25 Ability to re-run failed processes after
correction from source or master or admin
data has been completed.
MDM.BRQ.26 Ability to have audit trail on exceptions and
exceptions resolution.
System and Data Administration
MDM.BRQ.27 User friendly system configuration and
setting
MDM.BRQ.28 Ability to configure master data synch
process and rules
MDM.BRQ.29 Ability to configure administrative data
such as look-up tables, rules tables and
Page: 86
Response
Response Detail
(F/P/NR/N)
control tables
MDM.BRQ.30 Ability to configure security access profile
at group and at individual level at the
system function and screen level.
Integration Layer
MDM.BRQ.31 Ability to configure integration points with
different external systems via preferred
integration mechanism eg messaging or
batch file transfer:
Page: 87
Response
Response Detail
(F/P/NR/N)
Page: 88
Response
Response Detail
(F/P/NR/N)
Page: 89
Response
Response Detail
(F/P/NR/N)
Page: 90
Response
Response Detail
(F/P/NR/N)
Page: 91
Response
Response Detail
(F/P/NR/N)
individual records.
PMS.BRQ.22 Ability to re-run failed processes after
correction from source or master or admin
data has been completed.
PMS.BRQ.23 Ability to have audit trail on exceptions and
exceptions resolution.
System and Data Administration
PMS.BRQ.24 User friendly system configuration and
setting
PMS.BRQ.25 Ability to configure master data synch
process and rules
PMS.BRQ.26 Ability to configure administrative data such
as look-up tables, rules tables and control
tables
PMS.BRQ.27 Ability to configure security access profile at
group and at individual level at the system
function and screen level.
Integration Layer
PMS.BRQ.28 Ability to configure integration points with
different external systems via preferred
integration mechanism eg messaging or
batch file transfer:
Page: 92
Response
Response Detail
(F/P/NR/N)
Page: 93
Requirement
TRQ.01
TRQ .02
Page: 94
Response
Response Detail
(CC/FC/CO)
Requirement
TRQ.03
TRQ.04
requirement.
Is the solution based on a flexible
architecture?
Please provide range of technology that
can be used to support the solution (eg
DB server can be MS SQL or Oracle
10, 11g, etc)
Is the solution designed for high
availability?
TRQ.05
TRQ.06
TRQ.07
TRQ.08
TRQ.09
TRQ.10
TRQ.11
Page: 95
Response
Response Detail
(CC/FC/CO)
Requirement
TRQ.12
(scheduled, ad hoc)?
Describe systems data exporting
capabilities (scheduled, ad hoc)?
TRQ.12
TRQ.13
TRQ.14
TRQ.15
TRQ.16
TRQ.17
TRQ.18
TRQ.19
Page: 96
Response
Response Detail
(CC/FC/CO)
Requirement
TRQ.20
TRQ.21
TRQ.22
TRQ.23
TRQ.24
TRQ.25
TRQ.26
TRQ.27
TRQ.28
Page: 97
Response
Response Detail
(CC/FC/CO)
Requirement
TRQ.29
Page: 98
Page: 99
3.4 Expertise
TPL requires information about implementing the products and services described in your solution.
Licensing Options
Licensed deployed instance to be owned by
TPL with maintenance support agreement.
Response
Page: 100
Response
Page: 101
Basis of Pricing
Proponents are required to specify the prices for all components in Tongan paanga
(TOP). If the Proponent wishes to be paid in another currency should refer to the process
set out in Clause 21 of the Terms and Conditions of RFP in Appendix A.
2.
Metrology
Single-Phase Meter
and options
Single element basic meter
Two element basic meter
100A supply disconnect
incremental cost
40A load control relay
incremental cost
Under frequency load shedding
(if not included in ripple relay
price above) incremental
cost
2A Slave relays, 2 of
incremental cost (if not
included in basic meter price)
Load limiting control
functionality incremental
cost
40A control relay (additional
load control switch)
incremental cost
Outage notification (last gasp)
incremental cost of including
at time of meter manufacture
Outage notification (last gasp)
incremental cost post
manufacture
Doc ID: 284/11/01, 15 November 2013
Volume
Notes
Page: 102
Three-Phase Meter
and options
Whole Current, one element
per phase basic meter
Whole Current, two elements
per phase basic meter
External CTs, one element
per phase basic meter
External CTs, two elements
per phase basic meter
100A supply disconnect
incremental cost
40A load control relay
incremental cost
Two channel ripple relay
incremental cost
Two channel ripple detect (if
not included in ripple relay
price above) incremental
cost
Under frequency load
shedding (if not included in
ripple relay price above)
incremental cost
2A Slave relays, 2 of
incremental cost (if not
included in basic meter
price)
Load limiting control
functionality incremental
cost
40A control relay
(additional load control
switch) incremental cost
Volume
Notes
Page: 103
Three-Phase Meter
and options
Outage notification (last
gasp) incremental cost of
including at time of meter
manufacture
Outage notification (last
gasp) incremental cost post
manufacture
Volume
Notes
Other Prices
Software Licensing Fees (detail the pricing regime which could include
initial price and ongoing pa price per meter and upgrade pricing)
Third party software pricing (as applicable)
Extended warranty (advise the term and price of any extended warranty
offered in respect of the Head-End and/or smart meters
Head-End Servers to support the Head-End software
Business Support Systems (BSS) Provisioning Manager
Network Detailed Design Services (any prices required to design the system
to deliver the services required by TPL)
Engineering Installation and Commissioning Services provide estimated
days and daily rates for grades of personnel required to install and
commission the Head-End software
Documentation (any prices to provide the documentation to operate the
Metering System)
Price
Price Escalation
Document any price
escalation that would
apply during the primary
supply period to the end
of 2016 or regime that
could result in reduced
prices.
Page: 104
Spare Parts
List recommended spare
parts, quantities and price
each assuming a meter
installed base of 20,000.
Installation/Test
Equipment
List recommended
installation and/or test
equipment and price each
Page: 105
3.
Telecommunications
Item
Volume
Unit
Price
Total
Price
Price
AMI Headend
Licensed Model
Unit
Price/ Unit
and
Technical
Page: 106
applicable
Estimated hardware cost for
20,000 installations
Software as a Service
< Please indicate if per
number of meters>
Other items paid as part of <Please indicate if per
SaaS such as back-office users
number of named users>
Monthly SaaS Fee
access to UI
Price Escalation
Document any price
escalation that would
apply during the primary
supply period to the end
of 2015
4.
Page: 107
MDM
Bespoke Solution
Unit
Price/ Unit
and
Licensed Model
<Please indicate if per
instance, per CPU, per
number of meters>
and
Technical
Software as a Service
< Please indicate if per
number of meters>
Other items paid as part of <Please indicate if per
Monthly SaaS Fee
Page: 108
access to UI
End User Training
Unit
Price/ Unit
and
Licensed Model
Software License Fee
Page: 109
and
Technical
Software as a Service
Monthly SaaS Fee
5.
Additional Services
Page: 110
Describe and price any Additional Services that are offered in addition to the primary
requirements of this RFP (those being smart meters, Head-End and telecommunications
connectivity between the smart meters and Head-End).
Additional Services
6. Other
Third Party Impacts
(detail any factors not
under the control of the
Proponent that may
affect the offer)
Conflicts of Interest
(detail any conflicts that
may relate to the
Proponents offer)
Page: 111
Contact Person
This notice is to formally advise that the above Proponent has received the TPL RFP in
respect of Advanced Metering Infrastructure.
Response on behalf of Proponent
By:
Position:
Date:
Page: 112
Intention to Respond Form (To be returned within one week of data of issue of RFP)
1.
Description
TPL AMI Systems Procurement Request for
Proposals (RFP)
2.
Closing Date
13 December 2013
3.
TPL Procurement
John McCutcheon
Manager
TPL Procurement Manager
79 Grafton Road
PO Box 109 628
Newmarket
Auckland 1149
DDI +64 9 358 3503
Mob +64 21 934 901
Email john@powerbusiness.co.nz
Proponent
4.
Proponent Name
5.
Contact Person
Consortium Partners (as applicable)
6.
7.
This notice is to formally advise that the above Proponent does/does not (delete as
applicable) intend to submit a Proposal to the RFP.
We agree to comply with the provisions of the RFP, in particular, the conditions related
to confidentiality during the evaluation and negotiation period.
Response on behalf of Proponent
By:
Position:
Date:
Page: 113
Page: 114
I/We have fully disclosed in the Proposal all circumstances when my/our duties and
responsibilities to TPL related to the RFP could be adversely affected by some other
separate duty to a third party.
I/We have fully disclosed in the Proposal all known circumstances where any actual or
perceived conflict of interest could occur in relation to this Proposal.
I /We warrant that I/we am/are duly authorised to sign the Proposal for and on behalf of
the Proponent.
Page: 115
Financial
Liquidated Damages
Warranties
Confidential
information
Page: 116
Force Majeure
Termination
Intellectual Property
Insurance
special loss
No liability for either party in the case of a Force Majeure
event
TPL able to terminate in the event of a breach of
contract
TPL able to terminate for convenience with an agreed
notice period
Vendor unable to terminate the contract for
convenience
Both parties are to retain the intellectual property rights to the
intellectual property they introduce or create in the provision
of services under the contract
Vendor to hold appropriate insurances up to agreed limits to
ensure it is able to meet the obligations of the contract
between the parties including at least:
Public liability
Professional indemnity
Page: 117