Pass-through integration for local government · records are never stored System status1-559-251-7767Sentra familySign in
SentraBridgeIntegration platform
ExampleTemplate

Meter reads from AMI to utility billing with zero-read check

Every morning, reads the Neptune 360 export from the SFTP folder. Reads that look wrong (35 days with no flow, a skipped read or a read error) go to the meter team and become re-read service orders; good reads load into utility billing.

Try it on your dataAll examples
This flow

9 steps

StartsOn a schedule
SystemsSFTP server, Utility billing (CIS)
Branches1
Stored recordsNone: pass-through
§ The flow

The whole flow, as it appears on the canvas.

Scroll sideways on small screens. Colors show the kind of step: start, read, change, decide, write.

Flow diagram: Meter reads from AMI to utility billing with zero-read checkEvery morning, reads the Neptune 360 export from the SFTP folder. Reads that look wrong (35 days with no flow, a skipped read or a read error) go to the meter team and become re-read service orders; good reads load into utility billing.Daily at 5 amOn a scheduleRead the AMI exportRead files · SFTPTo meter read fieldsMap fieldsZero or missing read?If / elseFields for: load the readMap fieldsFields for: open a re-readorderMap fieldsLoad the readSend records · Utility billingOpen a re-read orderSend records · Utility billingTell the meter teamSend emailNoYesYes
StartReadFilesDatabaseChangeDecideWriteAct
§ Step by step

What each step does.

  1. 01 · Start · On a schedule

    Daily at 5 am

    • Cron 0 5 * * * (workspace time zone)

    Then: Read the AMI export

  2. 02 · Files · Read files · SFTP server

    Read the AMI export

    • Reads files matching neptune360-reads-*.txt in inbox on SFTP server
    • Format: CSV, first row has the field names
    • Only files new since the last good run
    • After a good run, files move to archive

    Then: To meter read fields

  3. 03 · Change · Map fields

    To meter read fields

    • Shapes each record into 9 fields: account_number, meter_number, read_date, reading, unit, order_status, no_flow_days_code, leak_now, read_code

    Then: Zero or missing read?

  4. 04 · Decide · If / else

    Zero or missing read?

    • Yes when no_flow_days_code is 6 or order_status is one of SK,IN or reading contains : or reading is empty

    Then: No → Fields for: load the read; Yes → Fields for: open a re-read order; Yes → Tell the meter team

  5. 05 · Change · Map fields

    Fields for: load the read

    • Shapes each record into 6 fields: account_number, meter_number, read_date, reading, unit, read_code

    Then: Load the read

  6. 06 · Change · Map fields

    Fields for: open a re-read order

    • Shapes each record into 4 fields: account_number, type, status, notes

    Then: Open a re-read order

  7. 07 · Write · Send records · Utility billing (CIS)

    Load the read

    • Creates Meter reads in Utility billing (CIS)
  8. 08 · Write · Send records · Utility billing (CIS)

    Open a re-read order

    • Creates Service orders in Utility billing (CIS)
  9. 09 · Act · Send email

    Tell the meter team

    • Emails [email protected]: “{{count}} meters need a look”
    • One summary email
    • Records attached as CSV
§ Systems

Connectors used

Swap any of them for another system with the same kind of data.

§ Next

Keep exploring

Example311 triage: route every request to the right systemExampleLoad the bank's daily payment file into the city databaseExampleMunis paid checks to the bank positive pay fileExampleNightly 311 export as a CSV file on SFTP

Run this flow on your systems.

We'll set up a workspace with your systems in a sandbox and build your first flow with you.

Request a demoBrowse live examples