Smart meter field app integration without middleware

Why integration decides whether a rollout works

A field app that doesn't talk to anything becomes another place to copy data from. The installation is done, the photos are perfect, and then someone in the office types the new meter serial into the head-end system by hand. That is where most commissioning failures start: one transposed digit between the field record and the system of record.

So the question to ask any field platform is not "do you have an API?" but "who builds the connection, how long does it take, and what happens when it fails at 2 a.m.?"

What Connectorly connects to

REST APIs. Any system that exposes data over HTTP, with Basic authentication, a Bearer token or OAuth 2.0. Most modern HES, MDM and billing platforms offer this, and SAP systems usually expose their data as OData services over HTTP, which Connectorly calls like any other API.

SQL databases. PostgreSQL, MySQL, Microsoft SQL Server and SQLite. If your billing team can give you a read-only view or a staging table, Connectorly can read it directly, with no API project needed.

Webhooks. Systems that push data can send it to a Connectorly endpoint as it happens, instead of waiting for a scheduled pull.

Connectorly is built to integrate with SAP IS-U and Oracle CC&B-style billing systems, and with the HES and MDM platforms used in smart metering. See the pages on HES and MDM, SAP IS-U and Oracle CC&B.

Setting up a Connectorly integration starts with one choice: pull data in, or push it out.

Data in, data out

In. Connectorly can bring records into five places in PIEBENCH: service points, meters, work orders, installations and completed field jobs. A typical setup pulls consumers from billing as service points, the meter stock from the AMISP's inventory, and a list of jobs (for example, non-communicating meters from the HES) as work orders. Filters let you take only the records you want, such as one division or one status.

Out. When a field job is approved, PIEBENCH fires an event for it, for example every approved meter installation. Connectorly sends that record to the system you choose, and tracks whether each delivery succeeded.

How a connection is set up

1. Choose the source. Pick REST, SQL or webhook, then enter the address and credentials.
2. Test the connection. Connectorly checks that it can reach the system and read a sample before you go further.
3. Map the fields. Connectorly reads the structure of the sample and suggests which incoming field matches which PIEBENCH field. You confirm or change each match, and add transformations where formats differ.
4. Set a filter and a schedule. Decide which records to take and how often to run: on a schedule, on demand, or as webhooks arrive.
5. Watch the runs. Every run is logged with the number of records processed and failed, and you can open any run to see what happened.

For most standard sources this takes about 10 minutes. No middleware layer, no consultant, no code.

When something fails

Integrations fail. Passwords expire, servers restart, a field changes type. Connectorly treats this as normal. Sync jobs retry automatically, up to five attempts with increasing gaps between them, so a short outage on the other side fixes itself. Scheduled runs that are skipped or fail are logged with a reason. And because every run is recorded, the question "did yesterday's installs reach the HES?" has a precise answer.

Who builds it

Usually the same project admin who set up the forms. Connectorly is designed for people who know their data, not people who write code. If your IT team prefers to own the connection, the same screens show them exactly what is being sent and received.

Connectorly is included in the Pro and Enterprise plans. Pro starts at $499 a month; see pricing. Enterprise adds custom integrations built with you.