Questionnaire Evidence Index

Integration approach — APIs, import/export, MultiSpeak

Read-only REST + CSV/XML adapters are demonstrable. MultiSpeak requires a vendor endpoint, version, and credentials — no live adapter is connected.

What APIs exist

Read-only demo surface with API-key auth; write APIs would follow the same server-route pattern.

Android or iOS application

The responsive web application works in Android/iOS browsers, but there is currently no web app manifest or service worker and it is not an installable PWA. Native app-store applications would require custom development.

Time to run bills end-to-end

Demonstrated with measured per-step and total elapsed time on synthetic demo data; production timing is volume/infrastructure dependent.

Steps in the bill-run process

Six ordered steps shown: select cycle → validate → calculate → exceptions → finalize → output.

Touch-enabled tablet app for field workers

/work-orders is responsive and tablet-usable with mobile-friendly dialogs, but there is no dedicated field mode, offline sync, or photo capture. A purpose-built field application would require further implementation.

Role-based security

Role/permission model is configured and visible; enforcement requires the authentication integration (Microsoft Entra SSO) to be connected.

How account numbers are assigned

Prefix/sequence rules per account class and service type, including the stormwater-only 50 prefix.

How the cutoff list is generated

Configurable criteria (minimum balance, days past due) over synthetic accounts.

Manually remove accounts before cutoff finalization

Exclusions require a reason, create a cutoff hold, and are audited.

Arrangements visible when cutoff list generates

Active payment arrangements are flagged per candidate.

Block late fees temporarily/permanently per account

Permanent or until-date exemptions are honored by the late-fee calculation and are audited.

Query payments by date range and amount

Date range, amount range, method, and account/customer filters over real payment rows.

Transfer misapplied payments between accounts

Zero-net reversal/repost with the original payment preserved and full audit trail.

How ERP imports work

Illustrative GL CSV export demonstrates the handoff format; Tyler MUNIS is not connected.

Support roles for IT, Finance, end users

Separate limited-scope roles are modeled; live assignment requires the auth integration.

Add fees to a bill

Ad-hoc fee lines on synthetic bills with category, amount, and audit reference.

Simultaneous user capacity

No validated benchmark yet; no application-level hard cap; capacity is deployment dependent.

Cityworks APIs — ours or theirs

Design targets the vendor's Cityworks REST API with sample payloads; no connection exists.

Auto-update from Cityworks meter installs

Simulated locally: completing an exchange order retires/installs meters in the demo DB — the behavior a Cityworks callback would drive.

Generate Cityworks service orders during cutoffs

Creates local simulated turn-off orders marked Cityworks-ready / Not Synced; no live dispatch.

How software integrations occur

REST + file adapters demonstrated; out-of-the-box vendor connectors require vendor access.

Consume Esri REST services / other sources

The GIS page currently renders synthetic layers with measurement and asset-inspector behavior; Esri is not connected. A municipal Esri service URL plus vendor and client configuration are required.

Supported Cityworks and Esri versions

No vendor versions validated yet — targets are configuration dependent and listed as not yet validated.

Software compatibility matrix

In-app matrix covering browsers, runtime, database, and vendor integration validation status.

Service-line / customer-line material fields

Copper/PVC/PEX/Galvanized/Unknown values are stored and displayed on Account 360; the current UI is display-only for these fields.

Stormwater semiannual/annual or combined runs

Cycle frequency + service scope support combined, stormwater-only semiannual, and annual runs.

Stormwater-only account prefix '50'

Seeded synthetic stormwater-only accounts demonstrate the prefix without renumbering existing accounts.

Stormwater fee from IAS World impervious surface

Charges derive from stored impervious_sqft/ERU; CSV import adapter demonstrates the mapping. IAS World itself is not connected.

Stormwater credits on specified accounts

credit_pct reduces calculated charges and is surfaced on the stormwater parcel roll; it is not currently surfaced on Account 360.

Parcel-based stormwater billing

Parcel-keyed view with impervious area, ERU, credit, gross and net fee.

Appendix B — IT/SaaS/GIS compliance evidence

Evidence center covers architecture, hosting, security, and performance honestly; items needing client/vendor confirmation are explicitly listed.