Re-entry
Dispatchers copy requests into the crew schedule.
Field workSolution
Potholes to crews.
Work orders to 311.
New pothole, streetlight and tree requests become crew visits in Sentra Scheduler, and work orders entered in the city database show up as 311 requests.
This solution
Public works & field crews
StartsOn a schedule · Every 15 minutes
SystemsSentra 311, Sentra Scheduler, Cityworks (Trimble Unity), Microsoft SQL Server…
Templates3 ready-made flows to start from3
Stored recordsNone: pass-through, in memory only0
Preview any template on your own data before it writes anything.
§ The problem
What it looks like today.
Invisible work
Work orders phoned in or entered in another system never appear in 311.
Duplicates
The same pothole reported three times becomes three visits.
§ How it works
How it works: Public works & field crews
- 01Changed requestsFrom Sentra 311
- 02Open potholesFilter by type and status
- 03Shape a visitCrew, address, notes
- 04Create visitIn Sentra Scheduler
§ 01 / Requests to crews
A visit for every new pothole.
Every 15 minutes, new or changed pothole requests become visits for the street repair crew in Sentra Scheduler.
- Remove duplicates by address or ID
- Cityworks (Trimble Unity) as a destination too
- Replay by ID if Scheduler was down
§ 02 / Work orders to 311
Reverse sync from the database.
Work orders created or changed in the city database become Sentra 311 requests, so phone and inspection work shows up in 311.
- Database change triggers
- Read with a table or query
- Matched by ID for updates
§ Templates
Ready-made flows for this.
Sentra 311 → Sentra Scheduler
New pothole requests become Scheduler visits
Every 15 minutes, takes new or changed pothole requests from Sentra 311 and creates a visit for the street repair crew in Sentra Scheduler.
PostgreSQL / PostGIS → Sentra 311Reverse sync: database work orders become Sentra 311 requests
Every 15 minutes, reads work orders created or changed in the city database and creates matching Sentra 311 requests, so phone and inspection work…
Sentra 311 → Sentra Scheduler → PostgreSQL / PostGIS → Esri ArcGIS feature layer → SFTP server311 triage: route every request to the right system
Cleans and checks changed 311 requests, sends bad ones to a data-quality sub-flow, checks the city database to see if each is new, then routes new…
§ Systems
Works with
Pre-built connectors used in this solution. Anything else with an API, a database or SFTP works too.
Sentra 311
Sentra SchedulerSee your own systems connected.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.