Orcserve is the two-way sync layer between the enterprise systems you already run (311, CRM, ERP, work-management) and ArcGIS Field Maps. Configured, not custom-coded.
To put work on the map today, most agencies bridge this gap one of three ways, and each one costs them.
Meanwhile the office and the field stay out of sync, paid for in time, budget, or flexibility.
The system of record (your 311, CRM, ERP, work-management or permitting platform) knows every job. ArcGIS knows every place. Between them sits a gap, and closing it is where agencies quietly lose time and money.
Crews enter the same job into 311, a spreadsheet and a map by hand. It's slow and error-prone, and updates get lost, duplicated, or logged days late.
Expensive, and it brings its own fixed process, so you reshape your operation to fit the software instead of the other way around, and it still can't bend to the unique way each workflow runs.
Costly and slow to build, brittle when a connected system changes, and expensive to maintain, often living in one developer's head.
Each path trades away your time, your budget, or your flexibility. Orcserve takes a different one. It connects the systems you already run to ArcGIS, configured to your workflows instead of forcing you onto someone else's.
Orcserve reads the work you already have, publishes it to ArcGIS for the field, and writes validated field updates straight back, with loop prevention and a full audit trail.
Read new and changed work from CRM, ERP, 311, asset or permitting systems through approved APIs. You choose the records and fields.
Work becomes live features for Field Maps, Dashboards, Experience Builder, Survey123, routing and analysis, on the platform you already own.
Validated field updates (status, notes, photos, inspections) flow back to the system of record. It stays the single source of truth.
A real lifecycle, from a citizen report to a closed record, without anyone re-typing a thing. Here is an actual sync run.
A pothole arrives in the CRM as SR-1001 with an address.
system of recordGeocoded and published as a point on an ArcGIS feature layer.
ArcGIS featureA crew opens it on a phone, marks it resolved, attaches a photo.
Field MapsThe status flows back to 311. The CRM stays the source of truth.
system of recordBecause Orcserve runs on the ArcGIS platform you already own, it unlocks capabilities agencies usually buy a separate product for.
Not just status. Orcserve pulls the custom fields and the source images from your system and attaches them to the map feature, so a crew taps a point in Field Maps and sees the full picture: the request, the photo, the details, right where the work is.
Build named, numbered, optimized routes and assign them to different crews, using the ArcGIS routing your agency already owns. It's the capability others sell as a standalone product, delivered on the platform you already pay for.
With Esri location sharing, crews' routes and visits show up on the map: where they have been, when, and proof a site was serviced. A vendor or field process that used to be a black box becomes transparent, on the ArcGIS you already own.
Every closure is tracked as the work is performed and synced back, so your operation shows up in the BI tools you already own. Orcserve ships starter dashboards for ArcGIS, Power BI and Tableau, ready to point at your data.
Sample dashboard. Orcserve ships starter dashboards for ArcGIS, Power BI and Tableau; point them at your synced data.
No two agencies run service requests the same way. A pothole, an illegal-dumping report, a downed sign and a missed pickup each follow a different path. Orcserve adapts to the workflows you already run, per request type, and keeps your system of record in charge.
Adopt an all-in-one platform's built-in process and reshape your operation around it.
Keep your systems and your workflows, and connect them to ArcGIS. Orcserve is the integration.
One reusable platform, configured per request type, across the everyday work of public works and municipal operations.
Reported, geocoded, routed to a crew, and closed with a photo, back in 311.
Field-verified, documented, and cleared, with the whole trail synced.
Waste and recycling misses on the map, resolved on the route.
Downed signs and faults tracked from report to repair.
Locations, before/after photos, and status, all in sync.
Field inspections and findings flow straight to the record.
Outages and assets, worked in the field and closed in the office.
Catch basins, grounds, fleet: anything with a place and a state.
Drawn from work at a large East Coast metropolitan public works department. Different request types, the same pattern: a manual, paper-and-spreadsheet process turned into a live, transparent field operation.
A supervisor printed hundreds of worksheet pages and handed them out by ward. Crews couldn't tell which site to do first, and a text description often didn't match what was on the ground. Completed work was hand-written on the worksheet and re-keyed by the supervisor into the legacy system.
Each request flows from 311 onto Field Maps with the resident's and the inspector's photos attached, so crews see exactly what to do and where. They work it on a phone, attach their own completion photos, and the status and photos sync straight back to 311, to the resident. Supervisors can see where crews have been on the map.
Every week about 500 requests were exported to Excel and emailed to a field vendor working on a separate system. Every day an Excel came back listing what they had done. The round-trip meant errors, missed work, no visibility into the vendor's progress, heavy manual effort, and high cost.
Requests sync directly to the field app and completed work syncs back automatically, with no spreadsheets. With Esri location sharing, the previously-invisible vendor work becomes visible on the map: where crews went, and which sites were serviced.
Missed-collection requests moved through a convoluted, manual, multi-step process spread across systems and paper, with little visibility into status or coverage.
Requests flow to the field prioritized and mapped, crews work and close them on a phone with photos, and status syncs back to 311 automatically, with crew activity visible on the map.
Case studies are de-identified. Capabilities shown use Esri ArcGIS and Field Maps; crew location sharing requires the applicable Esri licensing and is used with appropriate consent.
Rip-and-replace platforms and one-off custom integrations are measured in quarters and budget cycles. Because Orcserve is configured on a reusable platform (not rebuilt from scratch each time), a first workflow can go live in weeks.
Typical ranges for enterprise field-operations projects; actual timelines depend on scope, data access and approvals.
The platform you already pay for does more than you think. Orcserve connects it to the field instead of replacing it.
No rip-and-replace. Your enterprise platform stays the system of record; Orcserve connects it to the field.
New fields, statuses, rules and ArcGIS layers are configured, not another custom integration project every time.
Runs on-premises or in your own Azure or AWS. Credentials, logs and operational data stay in an approved environment.
Please complete the form with the systems you currently use and your workflows, and we'll reach out to set up a demo.
Based on what you share, we prepare a demo that walks through your workflow and shows how Orcserve fits and serves your needs.
McLean, Virginia · working with agencies nationwide