HomeMy WebLinkAboutContract 53986-A1 CSC No. 53986-A1
FIRST AMENDMENT TO
FORT WORTH CITY SECRETARY CONTRACT NO. 53986
This First Amendment to Fort Worth City Secretary Contract No. 53986 ("First
Amendment") is made between the City of Fort Worth ("Fort Worth"), a municipal corporation
and Smart Energy Systems d/b/a Smart Energy Water(SEW),a California corporation("Vendor").
WHEREAS, Fort Worth and Vendor entered into an Agreement identified as Fort Worth
City Secretary Contract No. 53986 beginning June 5, 2020 (the "Agreement"); and
WHEREAS, it is the collective desire of both Fort Worth and Vendor to amend the
Agreement to provide additional professional services necessary for system design to improve the
customer experience through real time system integrations between SEW's SCM customer portal,
the existing Customer Relationship Management system, and Customer Billing systems used
within the Utility.
NOW THEREFORE,known by all these present,Fort Worth and Vendor, acting herein by
and through their duly authorized representatives, agree to the following terms, which amend the
Agreement as follows:
1. The Agreement is hereby amended by adding Attachment A, attached to this First
Amendment, to the Statement of Work listed as an Exhibit to the Addendum of the Agreement.
2. The Agreement is hereby amended by adding the following section to the
Addendum which is attached to the Agreement:
Compensation. City shall pay Vendor an amount not to exceed $225,000 for the
Services included in Attachment A to the First Amendment. Vendor shall not
perform any additional services for City not specified by this Agreement unless
City requests and approves in writing the additional costs for such services. City
shall not be liable for any additional expenses of Vendor not specified by this
Agreement unless City first approves such expenses in writing. City agrees to pay
all invoices of Vendor within thirty (30) days of receipt of such invoice.
3. All other terms,provisions,conditions,covenants and recitals of the Agreement not
expressly amended herein shall remain in full force and effect.
[Signature Page Follows]
OFFICIAL RECORD
CITY SECRETARY
FT. WORTH, TX
SEW CR
Executed effective as of the date signed by the Assistant City Manager below.
FORT WORTH:
City of Fort Worth Contract Compliance Manager:
By signing I acknowledge that I am the person
responsible for the monitoring and administration
of this contract,including ensuring all performance
By.Dana Burghdoff(Nov2,20 6:56 CSC and reporting requirements.
Name: Dana Burghdoff
Title: Assistant City Manager
Date: Nov 2, 2020 By Chan 4 (Nov2,202008:17CST)
Name: Madelene Rafalko,P.E.
Approval Recommended: Title: MyH2O Program Manager
Approved as to Form and Legality:
Cl ffrI&Ahl - fardnr
By.Christopher Harder(Nov 2,202011:15CST)
Name: Chris Harder TB Sfran
Title: Water Director ByJB Strong(Nov ,202O15:01C7
a F FORr Name: John B. Strong
Attest: ��,�° °° ° Title: Assistant City Attorney
�o
Ovo a=d
o° 9 Contract Authorization:
nEXASo4� M&C: 20-063609/01/2020
By.
Name: Mary J.Kayser
Title: City Secretary
VENDOR:
Smart Energy Systems d/b/a Smart Energy Water
By: �
Name: Harman Sandhu
Title: President
Date: October 30, 2020
OFFICIAL RECORD
CITY SECRETARY
FT. WORTH, TX
SEW CR
ATTACHMENT A
Client Name City of Fort Worth Water Department
Change Summary Discovery, Integration, and Enhancement
Software SCM
CR ID N/A
Change Request Description
Pursuant to the MSA/STATEMENT OF WORK entered between Smart Energy Systems, Inc. dba Smart Energy Water
("SEW") and City of Fort Worth ("Client"), Client would like to:
Background
Two prior change requests(CRs) were proposed and provided to FWWD. Further refinement of these CRs was
requested and both are now incorporated into this singular new CR.
This scope of this CR is a combination professional services and product enhancements and consisting of the
following:
1) Professional Services:
a. Discovery and validation of items#2 and#3 with FWWD staff and consultants
b. SCM Phase-2 Discovery and Scoping with FWWD staff and consultants
2) Central Square Fusion/MuleSoft API Interface Definition:
a. Existing Naviline Utilities API Methods
b. Additional Naviline Utilities API Methods
3) SCM Base Product Enhancement:
a. Connect Me/Service/Conservation Form Submission, Query, and Notification API
b. Notification Preference Addition—Generic Communication
c. Generic Communication Notification API
SEW CR
Additional/Supplemental Information (i.e.screenshots,mock-ups,detailed requirements):
Description:Central Square Fusion/MuleSoft API Interface Definition
SCM will integrate with FWWD's Central Square CIS using Fusion Web Services proxied through MuleSoft.The API
syntax and semantics are described at https://fusion.centralsquare.com/Fusion/Suite/NaviLine/GettingStarted
under the Utilities section; only the URI of the API will differ from this sample documentation.
The following existing Fusion methods are needed to support SCM:
1) PostValidatePin(registration)
2) Post UtiIitiesAccountSearchByAccount(registration)
3) PostUtilitiesSearch Address(new and transfer service)
4) GetUtilitiesAccount(home/billing/myaccount)
5) GetUtilitiesAddress(myaccount mailing address)
6) GetNotificaionlnfo (myaccount paperless billing)
7) PostNotificationlnfo(paperless billing enrollment)
8) PostUpdateAddress (phone number update)
9) GetUtilitiesBilling(billing)
10) GetCurrentCharges(billing)
11) GetSummaryCharges(billing)
SEW CR
12) GetBillingDetail(billing)
13) GetMeterDetail(usage/billing)
14) GetConsumptionHistory(usage/billing)
15) GetAutoPay(autopay)
16) GetAutoPaySetup(autopay)
17) PostAutoPayUpdate(autopay)
FWWD SOW and DOU requirements identified to date require additional web services not present in Fusion. The
API syntax and semantics for these new services will adhere to the conventions used for the available Fusion Web
Services as described above. The needed methods not present in Fusion are:
1) GetPaymentArrangementEligibility—used to determine an account's eligibility for a self-service payment
arrangement
2) GetPaymentArrangementDetail—used to extract the detailed status for an active payment arrangement
3) PostPaymentArrangementEnrollment—used to enroll in a self-service payment arrangement
4) GetUnbilledConsumptionCharges—used to support FWWD use case of providing customer an accurate cost
in$(per rate plan) of consumption since the last billing cycle
5) GetHomeSurveyDetail—used by FWWD to pull home survey responses for apremise
FWWD is responsible for making all web services as described, both existing and new, available to SEW to support
Central Square Integration with SCM. FWWD will provide SEW with the URI for each API.SEW is responsible for
configuring FWWD's SCM instance to use the provided URIs.Separately, under scope#1, Professional Services,SEW
and FWWD will jointly validate and document the interface specification for each API referenced here.
Description: SCM Base Product Enhancement
SEW commits to developing specific SCM functionality for FWWD,which will then be incorporated into all
subsequent releases of SCM as base product.This functionality extends the inbox/folder paradigm used in the
Connect Me, Service, and Conservation modules to include the ability to send request form contents to an external
system, incorporate and use a tracking identifier supplied by the external system, and to provide customer
notifications based on the tracking identifier.
The enhancement is envisioned to make use of four API calls,two of which expose SCM functions and two provided
by FWWD to access the external CRM system. The anticipated API methods are:
1) CreateCase—used by SCM to create a case in CRM, input parameters are account number, request type
(service/connect me/conservation), topic, and form contents as name/value pairs. Response consists of
status code, status description,and tracking identifier(success only)
2) QueryCase—used by SCM to query CRM for the detailed status of a specific case or all cases associated with
a customer's service address. Input parameters are tracking identifier(case number),or service address
(authenticated only). Response consists of status code, status description, and case detail.
3) CaseNotification—used by FWWD to initiate an SCM notification to a registered SCM customer based on a
status change in an open CRM case. This request to SCM contains the request type(service/connect
me/conservation),tracking identifier,and notification content. SCM uses these values to initiate a notification
to the customer associated with this tracking identifier,honoring their notification preferences for the specific
request type.All notifications initiated in this manner will be visible in SCM and in the CSP as part of the
interaction record for the specific tracking identifier.
4) GenericNotification—used by FWWD to initiate an SCM notification to a customer on demand from the
utility. To support these ad hoc utility communications,a new notification preference category"Generic
Communications"will be added to SCM.All notifications initiated in this manner will be visible in SCM
and in the CSP. This request to SCM contains account number,the request type (generic),and the
notification content. SCM initiates a notification to the customer associated with this account number,
honoring their notification preferences for the generic request type.Notifications initiated in this manner are
visible in SCM and in the CSP.
SCM uses a form-based model to structure Connect Me,Service, and some Conservation customer interactions.
This model manages these interactions using a mail-based inbox/folder paradigm where customers and CSRs
interact using SCM and CSP respectively.While the forms and interactions are distinct by topic and audience,the
underlying mechanism is the same.
The proposed change augments the form-based model by adding an option for the form contents to be shared
outside of SCM by invoking a configurable API method (CreateCase) associated at the topic level. Conceptually,
CreateCase takes as input parameters: a) account number; b) request type(service/connect me/conservation); c)
topic; and, d)form contents as name/value pairs(JSON format).The response will consist of a status code, status
description, and a tracking identifier.The operation is synchronous. If successful,SCM will use the tracking
identifier from the response instead of its own internally generated tracking identifier.
By way of an example, FWWD can use this new feature to create a case in their CRM system for new customers
wanting to establish utility service who make their request using SCM.Today, a new customer wanting to establish
service completes and submits a New Service form in SCM (unauthenticated). The form becomes visible to all CSRs
in the CSP.Some CSR will view the form, elect to perform their manual process,then, once completed, responds
back to the customer with the relevant disposition.The proposed enhancement alters this scenario whereby upon
the customer submitting the New Service form,SCM invokes the configured CreateCase API with a null account
number, request type of"Service",topic of"New Service" and the completed form contents(JSON format) as
parameters(account number is null since none is yet assigned).The request is processed and SCM receives a
response indicating success and containing a tracking identifier which is the distinct "case number" provided by
CRM for use in tracking the New Service Request from cradle to grave.This scenario is more complex that may be
first recognized due to the fact since no account number is yet associated with the customer and the customer is
not registered in SCM, SCM will not be able to provide status updates directly to the customer. Instead,the
customer would use the query capability(described below)to check the status using the tracking identifier returned
at the time of form submission.
Regardless of the request type (service/connect me/conservation),SCM would use the same approach of passing
request type,form topic and form contents to the configured URI for all such interactions.
SCM will also provide the customer with the ability to "query" CRM for request status through a new query screen
using either of a request tracking identifier(Case Number) or service address (authenticated only). CRM would
respond with a summary status for the tracking identifier or a summary of all outstanding cases raised against the
specific service address.
FWWD is responsible for developing and making the CreateCase and QueryCase web services as described, available
to SEW. FWWD will provide SEW with the URI for each API. Separately, under scope#1, Professional Services,SEW
and FWWD will jointly validate and document the interface specification for each API referenced here.SEW will
enhance SCM as described and is responsible for developing and providiing the URIs for the Case Notification and
GenericNotification API methods exposed to FWWD.
Type of Change ❑ Additional Modules ® Customization ❑ Additional Licenses
® Additional Services ❑ System Integration
Implementation ❑ Critical ® High ❑ Normal ❑ Low
Priority
SEW CR
Fees and Payment Terms
Cost I Invoice Milestone
$50,000 Upon execution of this CR
Total Cost(USD) $175,000 January 15, 2021
Total Cost: $225,000
• The total cost of this Change Request will be invoiced upon the milestones listed above.
• Payment will be due net-30 days from receipt of invoice by Client.
• Late Payment penalties are applicable in accordance with the terms and conditions of the applicable SOW.
• All applicable service level agreements between SEW and Client,if any,shall not be applicable so long as SEW
Payment Terms resources are being utilized to perform or complete the change(s) or solution(s) set forth in this Change
Request.
• This Change Request shall result in the allocation and dedication of resources for the commencement and
delivery of the change(s) or solution(s) described above. Therefore, any delay in schedules by Client may
adversely affect the timely delivery of this and other Change Requests and incur additional charges.
Accepted By: City of Fort Worth Water Department Accepted By: Smart Energy Water
Signature: Signature:
Name: Name: Harman Sandhu
Date: Date: October 16, 2020
First Amendment to Fort Worth City Secretary Contract No. 53986 Page 7 of 7
11/4/2020 M&C Review
Official site of the City of Fort Worth,Texas
CITY COUNCIL AGENDA FORTTII
DATE: 9/1/2020 REFERENCE NO.: **M&C 20-0636 LOG NAME: 60SEWAMEND1
CODE: C TYPE: CONSENT PUBLIC HEARING: NO
SUBJECT. (ALL)Authorize Execution of Amendment No.1 to City Secretary Contract No. 53986 with
Smart Energy Water for Additional Design and Configuration Services for the
MyH2O Advanced Metering Infrastructure Project in an Amount Not to Exceed
$567,734.00 for a for a Total Contract Amount of$2,085,798.80
RECOMMENDATION:
It is recommended that the City Council:
1. Authorize Amendment No. 1 to City Secretary Contract No. 53986 with Smart Energy Water
for the MyH2O Program in an amount not to exceed $567,734.00 for a total contract amount
of $2,085,798.80; and
2. Adopt the attached appropriation ordinance adjusting receipts and appropriations in
the Water Capital fund by increasing receipts and appropriations in the Advanced Metering
Infrastructure project (City Project No. CO2715) in the amount of $567,734.00, and by
decreasing receipts and appropriations in the Unspecified project (City Project No.
UNSPEC) by the same amount.
DISCUSSION:
On May 15, 2018 (M&C C-28695), the City Council authorized an amendment to City Secretary
Contact No. 48301 with Aqua Metric Sales Company (Aqua Metric)for the full City wide deployment of
advanced metering infrastructure, bringing the total contract amount to $69,841,431.00. Aqua Metric
serves as the program integrator for the MyH2O Program and maintained contractual responsibility for
the procurement and implementation of various technologies, including the planned customer portal.
Following an extensive review of portal options, City staff selected the Smart Customer Mobile (SCM)
portal offered by Smart Energy Water(SEW). The initial agreement with SEW (City Secretary
Contract No. 53986) included funding for the subscription, 3-year licensing, and professional services
necessary to begin the discovery phase of the portal design.
Staff has worked with SEW in the project's discovery phase to finalize design requirements to meet
the needs of Fort Worth's residential and commercial water and wastewater customers. This
amendment will enable the configuration of the design requirements addressed in the initial scope and
identified during the discovery phase. In addition, the scope will address opportunities to improve the
customer experience through real time system integrations between SEW's SCM customer portal, the
existing customer relationship management system, and customer billing systems used within the
utility. The additional services will streamline the customer experience, enable efficiencies for
customer relations staff and allow the utility to avoid unnecessary and costly customizations in future
upgrades and enhancements.
The SCM portal will include a full-service mobile solution with the following functionality to residential
and small commercial customers. Utility contact center representatives will have access to view the
same information to facilitate personalized account service, as well as additional data analytics tools.
Ability to request move in, move out services and transfer service;
Detailed interval water use data for accounts with Advanced Metering Infrastructure (AMI) meters,
offering multiple viewing options, including cost detail and options for comparison to prior use and
usage of other customers by neighborhood or zip code;
Smart IQ analytics and alerts allowing the customer to identify leakage, high use, and watering
violations, and providing home water reports;
Conservation tab providing educational information and enabling the user to view and enroll in
conservation-based programs;
Ability to set notification preferences using a variety of mediums;
apps.cfwnet.org/council_packet/mc_review.asp?I D=28205&councildate=9/l/2020 1/2
11/4/2020 M&C Review
Enrollment in paperless billing;
Ability to set budget alerts that notify the customer if certain percentage cost thresholds have been
met; and
Ability to electronically submit any billing related concerns.
In addition, large commercial and industrial customers will have access to the enterprise portal which
will also provide:
Ability to manage multiple accounts and aggregate payments;
Custom portfolios with multiple users based on business need; and
Ability to view individual and aggregate water use.
As we continue to rollout improvements over the next two years, additional discovery and professional
services will be required to enable additional functionality to better serve our customers including field
service appointment scheduling, additional payment scheduling and due date options, outage
notifications, custom forms, conservation monitoring and web chat capabilities.
MWBE OFFICE: A waiver of the goal for MBE/SBE subcontracting requirements was requested by the
Department and approved by the OBD, in accordance with the MWBE or BDE Ordinance, because the
purchase of goods or services is from sources where subcontracting or supplier opportunities are
negligible
FISCAL INFORMATION/CERTIFICATION:
The Director of Finance certifies that funds are currently available in the unspecified project within the
Water Capital fund and upon approval of the above recommendations and adoption of the attached
appropriation ordinance, funds will be available in the Water Capital fund for the AMI -Advanced
Metering Infras project to support the approval of the above recommendations and authorization of the
amendment to the contract. Prior to an expenditure being incurred, the Water Department has the
responsibility of verifying the availability of funds.
TO
Fund Department Account Project Program Activity Budget Reference# Amount
I ID ID I I Year (Chartfield 2)
FROM
Fund Department Account Project Program Activity Budget Reference# Amount
ID ID Year Chartfield 2
Submitted for City Manager's Office by_ Dana Burghdoff(8018)
Originating Department Head: Chris Harder (5020)
Additional Information Contact: Madelene Rafalko (5467)
ATTACHMENTS
60SEWAMEND1 funds avail (KH 08.05.20).docx
60SEWAMEND1 59601 A020(R2).docx
apps.cfwnet.org/council_packet/mc_review.asp?I D=28205&councildate=9/l/2020 2/2