6-Exhibit H - Interfaces.pdf

EXHIBIT H - INTERFACES

The Interfaces below highlight the current and desired future state of the new CIS, CRM, and MWFM solution.

1. MuleSoft Enterprise Service Bus

Status Interface Direction Frequency/ Volume

Transfer Method

COTS

Package

Current Bidirectional Frequencies vary by supported integration

API MuleSoft

Current functionality: Integrations which currently pass through MuleSoft include:

• Smart Energy Water (SEW) to MuleSoft to Fusion to CIS

• Smart Energy Water (SEW) to MuleSoft to CRM

• CRM to MuleSoft to Maximo Enterprise Asset Management

• Maximo to MuleSoft to CRM

• MyFW app to MuleSoft to CRM to MuleSoft to Maximo Enterprise

Asset Management

• CRM to MuleSoft to FWWD Data Warehouse to Tenon/Snowflake

• Looker (data warehouse) to MuleSoft, which concurrently sends it to both CRM (cases) and CIS (workorders through W3 API)

• OpenForms to MuleSoft to CRM

Future Bidirectional Real-time API MuleSoft

Future functionality to be delivered at implementation:

• The selected vendor will work with FWWD to evaluate the most cost-effective method of integration, considering both up-front configuration and long-term support. Based on this analysis and as approved by FWWD IT, the selected vendor will configure the above listed integrations either directly between systems or leveraging MuleSoft. FWWD may choose to develop in-house.

Data Sets C = Current F = Future

Type of Data From CIS C/F

To CIS C/F

See separate integration descriptions

2. Selectron IVR (Incoming)

Status Interface Direction Frequency/ Volume

Transfer Method

COTS

Package

Current Bidirectional Real-time/~5,000 calls per day

Selectron API to Naviline

Selectron

IVR

Current functionality: • Customer call comes into AVAYA telephony; customer selects the option to go to the Water IVR. Customers can retrieve basic information (amount owed, make payments, opt out to CSR).

Cloud based.

Future Bidirectional Real-time/~5,000 calls per day

API Selectron

IVR

Future functionality to be delivered at implementation:

• Reproduce existing functionality.

• Based on account number (customer id and location id)

Data Sets C = Current F = Future

Type of Data From CIS C/F

Account # C/F C/F Customer phone # C/F Account balance C/F Service address C/F Due date C/F Pending amount C/F Pending miscellaneous if any

C/F

Adjusted balance C/F Past due amount C/F Last five bills, including bill amount, bill issue date and bill due date

C/F

Last five payments, including payment amount and date

C/F

Cash only flag C/F Payment arrangement and status

C/F

Bill delivery type C/F Work order status C/F Water quality issue status

3. Selectron Outbound Dialer (Calls)

Volume

Transfer Method

COTS

Package

Current Outbound Daily at 10AM ~2000/day

Batch file

Current functionality: • Calls go out from 10AM to 6PM. Any calls not completed during the business day roll over to the next business day. Monday through Friday excluding holidays. Includes delinquent calls on day 37 of billing cycle for unpaid bills.

Future Outbound Daily at 10AM ~2000/day

Batch file Selectron

IVR

Future functionality to be delivered at implementation:

• Replicate current functionality based on current leading practices.

• Separately provide a cost to return call success rates from the outbound dialer to CIS.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Phone # C/F Customer info C/F Balance info C/F Due date info C/F Past payment info C/F Call results F

4. Avaya CTI Screen Pop

Volume

Transfer Method

COTS

Package

Current Naviline to SQL Server to CRM

Weekly DB transfer Avaya/SQL Server

Current functionality: • SQL Server table updated weekly with customer phone numbers from Naviline. Used to screen pop accounts in CRM.

Future Bidirectional Real-time/ ~2,000 calls per day

API (REST or WebSocket)

Avaya CTI

Future functionality to be delivered at implementation:

• Use incoming phone number to locate account; display account when call transfers to CSR.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Phone # F Account # F

5. Smart Energy Water (SEW) from CIS

Volume Transfer Method

COTS

Package

Current CIS to SEW Daily/ ~300,000 per day

Flat file

Current functionality: • Nightly customer details (change records)

• Six files daily o Billing notification (all bills that ran in nightly bill update process) o Bill data is the details of what is in the bill. This supports a section in the portal that shows the bill details.

o Customer data file, address, location o Daily balance file o Payment file (all payments processed that night) o Payment reminder (3 days prior to bill due date, text and/or email will be sent to the customer) if signed up.

Future Outgoing Daily/ ~300,000 per day

Flat file

Future functionality to be delivered at implementation:

• Reproduce existing functionality based on current leading practices.

• Enhance included data based on new CIS functionality and configuration

Data Sets C = Current F = Future

Type of Data From CIS C/F

Bill events C/F Bill details, including charges, payments, and installment agreement details

C/F

Customer info C/F Balance C/F Payment details C/F Payment reminder trigger

6. Smart Energy Water (SEW) to CIS

Volume

Transfer Method

COTS

Package

Current Incoming through MuleSoft

Daily/ ~2,500- 5,000 per day

API SEW/

MuleSoft

Current functionality: • Customer information updates o Address updates o Phone number updates o Email updates

• Autopay elections (at time of election), including payment method type, due date only.

• Balance due is requested, real-time, by SEW of Naviline, prior to each autopayment.

• Assistance requests start in SEW and are passed through MuleSoft to CIS

• Data passes through MuleSoft

NOTES:

• Ebills and paperless bill notifications are sent directly to the customer based on the information in the file the night before using the email address and/or text messages and elections entered by the customer into SEW.

o Your bill is ready o Real-time lookup at DataProse for bill presentment

(outside of this contract)

• Paperless settings are sent to CIS with the email address.

• Notification elections are not sent to CIS

• Exception files – 3 for AMI and 4 for CIS – are not uploaded to

CIS

Future Bidirectional Real-time/ ~2,500- 5,000 updates and payments per day;

~ 25 cases per day

API SEW/

MuleSoft*

Future functionality to be delivered at implementation:

• Reproduce existing functionality based on current leading practices.

• Ability to submit meter readings and associated pictures through the ConnectMe portal which are subsequently passed to the CIS as a billing read with associated picture.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Address C/F Phone # C/F Email address C/F Autopay election & details C/F

Ebilling election & details

C/F

Assistance request (SR) details

*See MuleSoft, above.

7. Paymentus Payment Processing

Volume Transfer Method

COTS

Package

Current Incoming Real-time/~20,000 payments per day

Fusion Paymentu s

Current functionality: • Customers can make payments through Selectron and SEW and the Cash Office for card transactions. Swipe enabled, no chip yet.

Proposed upgrade to touch.

Future Incoming Real-time/~20,000 payments per day

API Paymentu s

Future functionality to be delivered at implementation:

• Replicate current functionality based on current leading practices.

• Automatically reverse payments based on reversal flag and payment tracking number.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Account # C/F Payment date/time C/F Payment tracking # C/F Payment amount C/F Payment origin C/F Payment channel C/F Payment method C/F Payment batch C/F Reversal Flag C/F

8. Fidelity Express Payments

Volume

Transfer Method

COTS

Package

Current Incoming Daily M-F /~250/day

Flat file

Current functionality: • Local payment service

• Nightly file

• Includes customer location id and amount of payment

• No information provided from CIS to Fidelity Express

• Go to their website and download or receive by email

Future Incoming Daily M_F /~ 250/day

API Fidelity Express

Future functionality to be delivered at implementation:

• Ability to accept payment information in real-time via API initiated by Fidelity Express.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Payment date C/F Payment amount C/F Payment type C/F Check # C/F

9. Chase Bank

Volume

Transfer Method

COTS

Package

Current Incoming See below Flat file

Bank - Current functionality:

Volume:

Daily/~ 500/day

• Another IT department receives the file specific to Water payments. FWWD credit and collections group picks up the file off the City network and brings it to Water network for processing.

• City Finance manages the relationship with Chase Bank.

• This file includes checks mailed directly to FWWD that were scanned as well as checks mailed to FWWD by Chase due to inability to process.

Lockbox - Current functionality:

Volume:

Daily/~ 1000/day

• Files uploaded to a specific folder; Brad Weaver in IT solutions pulls from the Water Zena folder.

• Lockbox o If the bank cannot match an account, payment is mailed to

FWWD.

o Mail to Water PO Box eLockbox – Current functionality

• N/A

Future Incoming Daily/~ 500/day Flat file

Bank – Future functionality:

• Future functionality to be delivered at implementation: Reproduce existing functionality based on current leading practices.

Lockbox - Future functionality:

• Reproduce existing functionality based on current leading practices.

eLockbox – Future functionality:

• If supported by Chase Bank, separate out eLockbox payments.

• Capture unique Chase Bank payment id for each eLockbox payment.

• Auto apply reversals based on Chase Bank payment id.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Payment date C/F Payment amount C/F Payment type C/F Check # C/F

10. PeopleSoft Financials GL

Volume

Transfer Method

COTS

Package

Current NA Daily/~1200/day Flat file

Current functionality: • Manual Scripts run daily; for previous day(s); files are posted to a file folder

• Validated by Accounting

• When approved, Water IT drops onto file location where it is picked up by PeopleSoft

• Some adjustments are entered manually

• Journal entries are also entered directly into PeopleSoft

Future Outgoing Daily/~ 1200/day API Peoplesof t

Future functionality to be delivered at implementation:

• Summarized totals by GL are transferred daily to PeopleSoft.

• Validation by Accounting will not be required with the new system.

• Manual adjustments will hopefully not be required with the new system.

• Journal entries directly into PeopleSoft should not be required with the new system.

Data Sets C = Current F = Future

Type of Data From CIS C/F

General ledger (GL) #s

F

Summary credits and debits per GL

F

11. PeopleSoft Financials Refund Checks

Volume

Transfer Method

COTS

Package

Current NA Daily/~ 150/weekly Flat file

Current functionality: • Process is manually ran thru CIS and reports are sent to Accounting for review by Water IT

• Accounting manually exported from CIS to Excel.

• Manually reviewed.

• Water IT drops file into file location where it is picked up by

PeopleSoft.

• Automatically imported into PeopleSoft Financials.

• Water IT manually imports previous weeks PeopleSoft information into CIS.

Future Bidirectional Real-time API PeopleSof t

Future functionality to be delivered at implementation:

• Provide a list of contacts, address, and amount of refund.

• Return check number

• Query Peoplesoft and update CIS with date cleared for each refund check.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Payee name C/F Payee address C/F Amount C/F Check # F Date cleared F

12. PeopleSoft Financials Inter-Departmental Bills

Volume

Transfer Method

COTS

Package

Current NA

Current functionality: •

Future Outgoing Nightly/~170 total IDB accounts; <50 /day

API PeopleSoft

Future functionality to be delivered at implementation:

• This interface is intended to pass electronic billing data related multiple departments within FWWD to PeopleSoft Financials at a summarized level.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Account # F

General ledger (GL) #s specific to IDB account

F

Summary credits and debits per GL

13. Fire / Police / EMS Address Information

Volume

Transfer Method

COTS

Package

Current NA

Current functionality: • Currently new addresses are manually entered into Naviline based on a report of addresses available in the City GIS.

• Also receive address letters by email. These could have a slightly longer time before available in GIS.

• New addresses come from the separate Fire / Police / EMS organizations within each County.

Future Incoming to CIS Nightly / up to 350/night

Flat file

Future functionality to be delivered at implementation:

• FWWD desires to pursue integration with Tarrant County Fire / Police / EMS only at the time of system implementation.

• FWWD will continue to look up information as needed in the Fire / Police / EMS systems of other counties included in the FWWD service area.

• Simultaneously provide assigned addresses to City of Fort Worth GIS team and import into CIS.

• Automatically add to CIS as new locations.

• Visible to Water GIS as a point feature class.

• Flag combinations, splits, and retirements for manual review.

• Include the ability to manually add addresses in advance of GIS when required. Flag for reconciliation when the actual address appears.

• NOTE: At time of implementation, FWWD may elect to pass address through GIS rather than supporting a parallel upload. In that event, addresses would be added to the GIS interface and this interface would become out of scope for the Responder.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Premise ID F Address info F Date added/changed

14. Lien and Change of Ownership Information & Stormwater Sq.

Footage Tarrant County Appraisal District and Denton County

Status Interface Direction Frequency/ Volume

Transfer Method

COTS

Package

Current NA

Current functionality: • CSR reviews County Appraisal website when setting up new services. Verifies new owner.

• When $500 balance due, it is reviewed for potential lien. Validate account with owner. If owner and no exemption, proceed with lien.

• Cannot lien for previous customer’s water.

• If a lien exists prior to a sale but is not discovered during the sale, the new owner is then responsible for the lien.

• Can only file lien if the account is active or terminated with a remaining balance.

• Can only lien if the debt was incurred by an owner and not by a tenant.

Future Bidirectional Real-time/ ~5,000 each time liens are evaluated;

~50,000 each time stormwater ERUs are updated; 2-3 per day based on customer interactions

API TBD

Future functionality to be delivered at implementation:

• Integration with Tarrant County and Denton County only. All other counties will continue to require CSR website review.

• Pass a premise id to Tarrant County or Denton County, as appropriate.

• Retrieve the information listed below.

• Retain the information in CIS with a retrieval date.

• Retrieval is on-demand only, as follows:

o All customers potentially eligible to lien o All customers potentially eligible to have an updated ERU.

o One customer as requested by CSR.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Premise ID F Property type

(duplex vs single family, etc.)

F

Current ownership info

F

Homestead exemption

Stormwater square footage

F

Existing water lien (Y/N)

15. City/State/Zip Code Data

Status Interface Direction

Frequency/ Volume

Transfer Method

COTS Package

Current Incoming Monthly/42,000 Flat file WorksRight

Current functionality: • Import a list of validated city/state/zip code combinations

Future Incoming Monthly/42,000 TBD Responder to recommend a product/process

Future functionality to be delivered at implementation:

• Import a list of validated city/state/zip code combinations

Data Sets C = Current F = Future

Type of Data From CIS C/F

City name and abbreviation

C/F

State name and abbreviation

5-digit zip code(s) C/F

16. ESRI GIS

Volume

Transfer Method

COTS

Package

Current NA Daily GIS to Warehouse Weekly Warehouse to GIS Real-time surveys to GIS 301,653 locations in GIS as of 12/3/2024

SQL queries

Current functionality: • Meter information (Naviline to data warehouse to GIS)

• Includes location information.

• Multistep process prior to passing to GIS.

• Water Applications makes addresses and Location ID’s for new services once in CIS as an available service. When a customer moves a meter into a service, then it passes to GIS, but GIS does not know exactly where it is. When the meter is installed, then meter services adds GPS coordinates.

• Service lines are surveyed and placed in GIS with a Service ID.

• Capture coordinates as part of Community Facility Agreement

(CFA) development projects for:

1) New subdivisions;

2) Existing location asset replacements; and

3) Work orders for Field Ops taps.

• General address for parcel, which has a point at the parcel center.

• Currently addresses are added to CIS. Should be in GIS as well.

Future Bidirectional Nightly batch deltas / ~ 10,000/night Weekly full refresh / ~300,000 meters plus other layers Surveys real-time / ~50/day Real-time ad hoc return of selected data within a polygon / ~500/day

SQL queries

Future functionality to be delivered at implementation:

• Address information will come into GIS and CIS from Fire / Police / EMS (addressed separately in this document).

• Meter and account information from CIS to GIS.

• Service information from CIS to GIS

• Any identified data within GIS:

o Service point information from GIS to CIS.

o Zip code changes from GIS to CIS o Location of Capital Improvement Program (CIP) pipes from GIS to CIS o Location of lead pipes from GIS to CIS o Proposed Lat/Long/Elevation from CIS to GIS for review.

o Lat/Long/Elevation from GIS to CIS

• Ability to draw polygons over a service area and return a list of accounts to receive communication from within CIS.

• The ability to spatially display a list of information based on accounts, customers, or meters, etc., selected from within CIS.

• Ability to view the following layers from within CIS:

o Stormwater layer o ERU (stormwater layer) o City limit layer o Sanitation layer o Meter layer, including meter size o Taps layer

C = Current F = Future

Type of Data From CIS C/F

GIS Address_ID F Proposed

Lat/Long/Elevation F

Lat/Long/Elevation F Service Types F Meter info F Account info, including customer type

F

Address info F Lead pipe flag F F Political jurisdiction

(city, county) F

Council district F Meter Services

District F

Cycle and route F F Previous program participation

17. AVL

Volume

Transfer Method

COTS

Package

Current NA myGeoTa b

Current functionality: • Available from a website. Fairly new. Used by Water Department, Field Ops and ES.

Future Link to display Real-time SDK myGeoTa b

Future functionality to be delivered at implementation:

• Shows current location

• Shows travel history

• Data remains in external system

• Ability to search by type of data listed below

Data Sets C = Current F = Future

Type of Data From CIS C/F

Truck # C/F C/F

Truck type C/F C/F Customer address C/F C/F Lat & Long C/F Date/time range C/F C/F

18. Mobile Workforce Management (MWFM)

Volume

Transfer Method

COTS

Package

Current NA

Current functionality: • Currently printed from CIS, worked on paper, and closed out in the CIS after work is complete.

• Manually entering work orders into SPMR.

• Using SPMR for all field work orders. CSR can see the real-time status. Can run a report to see what happened in the field. CSR closes those. Also, for inactive work orders and AMI work orders.

Metering Services closes them.

• Allows capture of meter readings.

• Manually run reports.

• Manually route and prioritize work.

• Runs on IOS

• All field staff using SPMR. No API integration capability. Limited availability after hours. The system is not available after 8:00pm.

• No capability for storing pictures/videos for validation.

Future Bidirectional Real-time/ ~ 100 per day

API New

Future functionality to be delivered at implementation:

• Ability to integrate with:

o CIS o Maximo o AVL o GIS o Outage map o Other

• Work is identified in CIS and passed to MWFM.

• Work is performed in the field and documented in the MWM.

• Work completion details are returned in real-time to CIS.

o Lat/Long/Elevation can be captured in the field and passed with the work completion details.

o Meter reading(s) can be captured in the field, passed to

CIS.

o Meter reading(s) can be applied as a billing read directly or after back-office review and approval.

• Work may be identified in the field and created in MWM.

o Work identified in the field must be associated with an existing CIS account, location, or meter.

o Ability for user-friendly reporting and analytics.

o Ability of storing pictures/videos for validation o Ability for asset management tracking and reporting.

C = Current F = Future

Type of Data From CIS C/F

T o CIS

Work type F F Account info F F Location info F Service Area info F Cycle info F Meter info F F Meter reading F F Lat/long/elevation F F Work instructions F Customer info F Register identifier F F Radio transmitter identifier F F

Crew info F Completion details F

19. Maximo Enterprise Asset Management

Volume

Transfer Method

COTS

Package

Current Bidirectional ~100/day API through MuleSoft

MuleSoft/ Maximo

Current functionality: • Currently create a CRM case which generates the Maximo work orders as emergency work to be dispatched immediately or scheduled through supervisors.

• Status updates are returned from Maximo to CRM.

• New Services created case in CRM to install new taps passes through MuleSoft to create a WO in Maximo.

• MyFW App customers can submit tickets. Comes through

MuleSoft to CRM to Maximo. Vetted within Maximo.

• CRM techmail ingests MyWaterAccount email and creates a CRM case. Reviewed in CRM.

• Currently passes through MuleSoft.

Future Bidirectional Real-time; ~ 100/day

API (evaluate MuleSoft)

Maximo*

Future functionality to be delivered at implementation:

• Ability to trigger emergency work orders (including, for example, sewer and water main breaks) from CIS to be sent to Maximo and dispatched. Status updates returned until completion.

• Ability to trigger routine work orders (including, for example, new tap installations) from CIS to be sent to Maximo and scheduled.

Status updates returned until completion.

• Where appropriate, follow-up work should be automatically triggered on completion of prerequisite work (meter install when tap install is complete).

• Ability to send pictures to Maximo.

• Ability to receive pictures from Maximo.

• Ability to communicate with the Mobile Workforce Management module of CIS.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Work type C/F C/F Account info C/F C/F Location info C/F Service Area info C/F Cycle info C/F Meter info C/F C/F Meter reading C/F C/F Lat/long/elevation C/F C/F Work instructions C/F Customer info C/F Register identifier C/F C/F Radio transmitter identifier C/F C/F

Crew info C/F Completion details C/F

*See MuleSoft, above.

20. City 311 Motorola CRM (MyFortWorth)

Status Interface Direction Frequency/ Volume

Transfer Method

COTS

Package

Current City 311 to Oracle

CRM

Daily/Ad Hoc;

~20/day

API through MuleSoft

Current functionality: • Calls captured in City311 are passed through MuleSoft to the FWWD Oracle CRM.

Future City 311 to CIS Real-time; ~ 20/day

API Motorola

CRM/

Mulesoft* implementation:

• Replicate existing integration through MuleSoft or connect directly from Motorola 311 to new CIS, as agreed upon by the vendor and

FWWD.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Customer Name C/F Customer Address C/F Call details C/F

*See MuleSoft, above.

21. Ivanti CRM/ISM (Environmental)

Volume

Transfer Method

COTS

Package

Current NA

Current functionality: •

Future Bidirectional Real-time/ ~500 per day

API Ivanti

CRM/ISM

Future functionality to be delivered at implementation:

• Customer information is passed from CIS to Ivanti.

• New locations are passed to Ivanti with a route and type.

• Both systems track the location identifier of the other system.

• Work orders start in CIS and are passed to Ivanti.

• Customer issue tickets may also be created in Ivanti based on requests received from MyH2O and/or City311.

• Work and ticket completion details are captured in Ivanti and passed to CIS when approved within Ivanti.

• Serial numbers are maintained in Ivanti and NOT in CIS.

• Events which may lead to fees or fines are identified in Ivanti as part of occurring route work, ad hoc customer requests and during completion of work orders which start in CIS. When approved in Ivanti, the fees or fines pass to CIS and are charged to the customer.

• NOTE: SmartTruck events will be manually entered into Ivanti and then passed to CIS.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Route type (Trash, Recycle, Yard, Bulk)

F

Service location F F Type and size of bin to add, remove, repair or exchange

Fee and or fine to apply

F

Work completion details

22. Vepo Envirotrax (Backflow)

Volume

Transfer Method

COTS

Package

Current NA Vepo Envirotrax

Current functionality: • Commercial and residential new services require a customer service inspection (CSI) before services start.

• Commercial and residential customers require annual testing for backflow.

• Track tester licenses, equipment certification, list of authorized testers, track employee tester licenses.

• Testers enter results in their application.

• Test commercial annually.

• Test some residential annually.

• Test City-owned devices.

• Charge fees to upload forms.

• Enforcement process, including lockout, is in a work order in

Naviline. The backflow group does the lockout. A fee is applied within CIS with lockout.

• Vepo sends mail a month prior to the due date. There are three rounds of letters, all automatic.

• There is no registration fee for testers.

The backflow group currently uses Accela to find out about new services.

Changes not through Accela might not be caught.

Future Pull from and push to Vepo

Real-time/60,000 backflow devices;

~250 transactions / day

API Vepo Envirotrax

Future functionality to be delivered at implementation:

• CIS sends new meter locations which will require backflow testing to Vepo Envirotrax. (Assume 5% per year, three thousand)

• CIS pull customer service inspection (CSI) completion details from Vepo for new services as part of the workflow to turn on service for the first time. (Assume 5% per year, three thousand)

• CIS sends customer information to Vepo Envirotrax when applicable information changes in CIS. (Assume 20% per year, 18,000)

• CIS pull locations eligible for enforcement fees from Vepo Envirotrax and automatically apply fees in CIS. (assume 20% per year, 18,000)

• CIS pull locations eligible for enforcement lockout from Vepo Envirotrax and automatically creates enforcement shut-off work order in CIS. (assume 5% per year, 3,000)

Data Sets C = Current F = Future

Type of Data From CIS C/F

Meter locations requiring backflow

F

Customer info (Name, address, contact info)

F

Locations eligible for enforcement fees

F

Locations eligible for enforcement lockout

23. Harris SmartWorks Compass MDMS

Volume Transfer Method

COTS

Package

Current Bidirectional Daily at 12:40 AM

Import sync in MDM starts at

3AM.

CMEP processed twice daily at 5:00AM and 12:00 PM; requires 4 hours to complete

Up to 25,000 meters/cycle

Flat file

Sensus hosted sftp site

Harris SmartWork s Compass

MDMS

Current functionality: Receives thirteen files of accounts that update customer information in MDMS.

1. Account customer cross-reference

2. Account services

3. Accounts

4. Billing schedule

5. Customers

6. Holidays

7. Locations

8. Meters connection statuses

9. Meter lat/long

10. Meter location cross references

11. Meter rate codes

12. Meters

13. Rate plans

CMEP file from Sensus AMI to MDMS includes three files.

o Interval report o Meter sync report o Alarm report

In addition, a Reading Request file is manually submitted from CIS to Harris SmartWorks by Metering Services. The file is loaded to Billing Automation Input folder. Can manually execute the job or set up to search for a file, ingest and provide results to an output folder.

The Reading file is imported from the output folder into CIS.

Harris SmartWorks provides, and CIS also receives a “failed to read” report that Metering Services uses to manually create field orders.

Do not currently request off-cycle readings.

Harris SmartWorks Compass MDMS separately submits data usage to SEW portal via flat file.

Future Bidirectional Scheduled (as above) and Real-time (ad hoc)

Flat files (csv) and API

Harris SmartWork s Compass

MDMS

Future functionality to be delivered at implementation:

• Recreate existing functionality related to information provided to Harris SmartMeter as well as meter read requests, responses and errors based on current leading practices.

• Real-time updates to accounts which are in and out of service.

Will require coordination with updates which occur in Mobile.

Updates from Mobile should be passed to MDM.

• Ability for CSR and/or billing to grab a single real-time meter reading on demand.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Standard CMEP and MVRS formats

Ad hoc meter reading request

F F

26. Waste Hauler Truck Consumption

Volume

Transfer Method

COTS

Package

Current NA Swift Comply

Current functionality: • SQL backend.

Future Incoming ~100 per month Daily uploads preferred

Flat File Internally developed

SQL DB/

application

Future functionality to be delivered at implementation:

• Import consumption nightly, converting gallons to CCF.

• Assume one too many trucks per account.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Truck # F Account Name F Consumption F Transaction date/time

27. DataProse Bill Presentation and Delinquency Letters

Volume

Transfer Method

COTS

Package

Current Outgoing Daily/~15,000 per day

Flat files

Current functionality: CIS staff manually upload Bill and Delinquency letter information into DataProse for processing and sending to customers.

DataProse prints and mails the bills and letters. They can suppress bills from being mailed and/or printed.

(SEW connects to Data Prose to display customer bills in the portal)

DataProse provides CFW reports of change addresses that are copied to the network, reviewed by Customer Care and updated in

CIS.

Future Bidirectional Daily/~15,000 per day

XML

implementation:

• Reproduce existing functionality based on current leading practices.

• Enhance included data based on new CIS functionality and configuration.

• Retrieve bill and notice PDFs and store in CIS-associated document management system.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Account info C/F Customer info C/F Delinquency info C/F Meter info C/F Consumption info C/F Charge details C/F Payment details C/F Installment agreement details

PDF files C/F

28. DataProse USPS Return Mail Address Change Service and NCOA

Volume

Transfer Method

COTS

Package

Current NA

Current functionality: DataProse provides flat files from the USPS which FWWD may use to update addresses manually

Future Incoming Daily/~1,000/day Flat file

Future functionality to be delivered at implementation:

• FWWD will work with their print/mail vendor, DataProse, to enhance the data returned from the USPS with account numbers and, if possible, communication type.

• FWWD will retrieve the flat files from DataProse and post in a location accessible to the Responder.

• Responder will import the information provided by DataProse into an accessible database format.

• The Responder will add a flag to contacts which have an outstanding return mail item or NCOA item associated with the contact and address combination.

• The flag will automatically be cleared once the address is expired or updated so that it no longer matches the USPS return mail record or NCOA record.

Data Sets C = Current F = Future

Type of Data From CIS C/F

Account info F Contact info F Change record type

Report date F