Implementation & onboarding : how smart360 helps

Go Live in 20-24 weeks, without a paused billing cycle.

For US water, electric, and gas utilities serving 3,000 to 100,000 connections. Seven structured phases, one named team through go-live, and a rollback safety net that keeps your legacy system running until the new one is proven. That is why 100% of utilities who went live with SMART360 are still on it.

• For water, electric, and gas US utilities serving 3,000 to 100,000 meters •

Ac
Aclarian
Smart metering platform
Connected · Health 98%
Records synced · 24h
12,522
↑ 12.4% vs yesterday
Sync flows
BillsSMART360 → Aclarian · Outbound
99.1%
PaymentsAclarian → SMART360 · Real-time
99.8%
Success rate · 24h
99.2%
↑ 0.4%

Backed by Stanford University. Recognized By Google. Partnered with Isle Utilities.

SOC 2 Certified
NIST 800-53
99.9% uptime SLA

Your Systems Don't Talk. Your Staff Pays the Price.

Phone App - Elements Webflow Library - BRIX Templates

Your AMI Data Stops at the Edge

Your AMI vendor and your billing vendor never agreed to work together. You're the integration in the middle.

Desktop App - Elements Webflow Library - BRIX Templates

Payments Confirm. Balances Don't Update.

Payment reconciliation is not a job. It's a symptom of disconnected systems.

Multiple Users - Elements Webflow Library - BRIX Templates

GIS Is a Different Universe

When field and office see different maps, mistakes are expensive.

Gear Icon - Elements Webflow Library - BRIX Templates

Custom Integrations Never Really End

Custom middleware is technical debt that grows with every vendor update.

Every Integration in One View

Connect, monitor, and manage every external system from a single dashboard.

Track active integrations, records synced, and failed records in real time

Filter by connected, errored, paused, or not connected

See a health score for every connection at a glance

Feature Image
Feature Image

Connect in Minutes, No Code

A guided wizard walks you through each connection, step by step.

Enter credentials and test the connection before going live

API key or OAuth authentication, your choice

Credentials encrypted with AES-256, saved automatically as a draft

See Every Sync, Catch Every Error

Define each data flow between SMART360 and your systems.

Set direction per flow: inbound or outbound

Choose real-time or scheduled sync

Run multiple endpoints, like bills and payments, independently

Feature Image
BENEFITS

Connect your stack, keep your systems

Keep the systems you already run

Your AMI, payment gateway, and GIS stay in place. SMART360 connects to them, so there's no rip-and-replace and no disruption for your consumers.

An open API for everything else

If your system isn't pre-built, SMART360's RESTful API, OAuth 2.0 authentication, and webhooks connect it. Custom connections typically take 2 to 4 weeks.

Add integrations anytime

The API framework supports new connections after go-live, and the pre-built catalog expands with quarterly connector releases.

Pre-built, not a custom project

25+ pre-built connectors for the AMI, payment, and GIS systems US utilities already run, activated during implementation rather than billed as a separate integration project.
HOW IT WORKS

Watch SMART360 Connect Your Stack

See how reads become bills and payments update balances automatically, no manual re-entry.

50
1
2
3
4
1
2
3
,
0
1
2
3
4
5
6
7
8
9
0
0
0
0
0
0
0
0
00+
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7

Meters Live

9
1
2
3
4
5
6
7
8
9
0
0
0
0
0
0
0
0
2
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
%

Less Billing Errors

4
1
2
3
1
2
7
1
2
3
4
5
1
2
3
4
%

Less Ops Investment

2
1
2
3
4
1
2
3
5
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9

Built-in Integrations

Plus Icon
SMART360 vs. Legacy CIS Integrations

Pre-Built vs. Custom-Built

Legacy CIS SMART360
Custom middleware, months of work Pre-built connector, activated during onboarding
Custom API work, billed hourly Stripe, Worldpay, ACH, Square are pre-built
Separate contract, separate project ESRI ArcGIS included in platform
New project, new cost RESTful API framework. No rebuild required
Scheduled batch transfers between platforms Not needed: same-database architecture
Get started  now
Simplify Your Operations.
Reduce Costs.
Improve Customer Satisfaction.
contact us today
contact us today
White Arrow

Implementation & Onboarding

20-24 Weeks to Go-Live.

Seven structured phases. A named team — not a support queue. And a track record: 100% customer retention from utilities who went through it.
SMART360 unified utility management platform dashboard

Utility-focused. Industry-recognized. Investor-backed.

TRUST
See how small and mid-sized utilities achieved measurable ROI with SMART360.
50
1
2
3
4
1
2
3
,
0
1
2
3
4
5
6
7
8
9
0
0
0
0
0
0
0
0
00+
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7

Meters Live

8
1
2
3
4
5
6
7
8
9
0
0
0
0
0
0
0
0
0
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
%

ROI Increased

4
1
2
3
1
2
7
1
2
3
4
5
1
2
3
4
%

Less Ops Investment

2
1
2
3
4
1
2
3
5
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9

Built-in Integrations

Plus Icon

Why Most Utility Implementations Fail

Phone App - Elements Webflow Library - BRIX Templates

The Project Starts Strong. Then Goes Quiet.

A dedicated team shows up for kickoff. By month four, you're emailing a support alias. The project manager changed twice. Nobody has the full picture anymore.

Desktop App - Elements Webflow Library - BRIX Templates

"Go-Live" Didn't Mean Ready

The system went live. The reports weren't configured. The consumer portal wasn't finished. Billing ran manually for another three months while the vendor "completed deployment."

Multiple Users - Elements Webflow Library - BRIX Templates

Data Migration Added Six Months

Legacy data came in a proprietary format. The new vendor needed custom scripts. The migration ran late. Billing go-live was pushed. You lost a year of operational progress.

Gear Icon - Elements Webflow Library - BRIX Templates

Staff Learned on Live Consumers

Training happened the week before go-live. Three days of slides. On the first billing cycle, your team was problem-solving in real time — with real consumer accounts at risk.

SMART360's implementation methodology

Seven Phases. Every Step Visible. One Dedicated Team.

SMART360 vs. Legacy CIS Implementation

SMART360 vs. Legacy CIS Implementation

Legacy CIS
SMART360
12-18 months average
20-24 weeks, full production go-live
Team changes mid-project; knowledge gaps accumulate
Named team — CSM, Config Specialist, Training Specialist, Support Engineer — maintained through go-live
Custom scripts, proprietary formats, often delayed six or more months
ML-based cleansing in parallel with configuration; 100% accuracy confirmed before cutover (SWA)
Calendar date — issues discovered post-cutover
Accuracy gate — cutover happens only when your team confirms readiness
Project team reassigned; support queue takes over
Phase 7 stabilization (weeks 25-36) with named Customer Success contact

Success Story

Water Utility

Island Water Authority Reduces Costs by 47%

92%
decrease in billing errors
35%
more service calls
$1.2M
savings annually

Size: 28,000 connections

28,000 connections. How a municipal utility replaced legacy systems and achieved 99% billing accuracy with 47% lower costs in year one.

Read Full Case Study

Questions About Implementation

What does "20-24 weeks" actually include?

The full timeline covers all seven phases: discovery, configuration, data migration, training, UAT, sandbox adoption, and go-live cutover. It is a full production go-live — not a pilot or partial deployment.

What is my team's time commitment?

Project Sponsor: 2-4 hours per week. IT contact: 8-10 hours per week. Subject matter experts: 4-6 hours per week. End users participate in training hours only. Implementation is not a full-time job for your staff.

What happens if go-live slips?

Go-live is gated on accuracy — not a fixed date. If the parallel run or UAT reveals issues, the timeline adjusts before cutover happens. A two-week delay is far less costly than one billing cycle with data errors.

What happens after go-live?

Phase 7 — post-launch stabilization — runs from weeks 25 through 36. Your named Customer Success contact supports your team through the first billing cycles and configuration refinements. You are not handed a support queue at week 25.

Do we need dedicated IT staff for the project?

Your IT contact commits 8-10 hours per week. SMART360 is no-code configuration, so your IT team is not writing scripts or managing infrastructure. Their role is reviewing integrations and validating data — not building the system.

Can implementation run during our billing cycle?

Yes. Implementation runs in parallel with your existing operations. Your legacy system stays live through the entire process. Billing is never interrupted. Cutover happens only after parallel run validation confirms accuracy.