Municipal software built to how your city works, not a box it has to fit.
Zanevan One is built on ArcGIS. Your records stay in your own ArcGIS Online, and every department works from the same ones.
- Built on ArcGIS
- Your records in your own ArcGIS Online
- One deployment per city
Why it's different
Built around the city, not the other way round.
Four decisions sit underneath every module.
Your records stay in your ArcGIS Online.
Zanevan One is built on ArcGIS. The records it keeps are feature layers in your own ArcGIS Online organization, and those layers are the record. Staff save under their own sign-in, so every change carries their name. Anything kept outside ArcGIS Online is operational only: lose it, and you lose no record.
Your way of working is settings, not code.
Workflows, forms, fees, pick lists and printed permits are your city's settings. Fees and your own lists you change yourself, in the app; the rest we change when you ask. None of it means rebuilding the software. Adding a new field to a layer is the one controlled step, and only with your yes.
Departments work in lockstep.
Every module keeps its records in the same ArcGIS Online organization, so a permit, a work order and a code case at the same address sit side by side, not in three separate systems. It is built so one department's step can start another's, such as a permit opening the work order that follows it.
Data protection by design.
Nothing is deleted: a record that should not exist is voided, with a reason. Only the staff who work in a layer can edit it; everyone else reads through a read-only view. Editor tracking records who made every change, and when.
The One family
A module for each department, one record underneath.
Each department gets its own module, and every module keeps its records in your ArcGIS Online. Open any of them to click around a demo with invented records.
Demos are high-level examples. In your city, each module is configured to your departments' own workflows during implementation. How implementation works
Permits from application to issue, with your own permit types, fees, stages and printed permits.
Click around the demo: OnePermit
Public Works work orders, including ones a permit starts automatically at the stage you choose.
Click around the demo: OneWork
Inspections, with the forms and outcomes each one calls for set by your city.
Click around the demo: OneInspect
Code enforcement cases, from the first report through every notice and visit, kept as one running log.
Click around the demo: OneCode
Parks records such as pavilion rentals, visible to the departments that need to know.
Click around the demo: OneParks
What the fire department needs from the rest of the city, such as hydrant flow tests and road closures.
Click around the demo: OneFire
The city records officers need on a call, and a way to report a problem, like a street light out, to the department that fixes it.
Click around the demo: OnePolice
The city's infrastructure and the records that go with each piece of it.
Click around the demo: OneAsset
Implementation
How implementation works
Zanevan One is built to work the way your city works, not to make your city fit a box. So implementation starts with listening, and nothing goes live until you have seen it working with your own settings and signed for it.
Step 1: Get ready together.
We check your ArcGIS Online organization with your IT staff: your users, licenses, administrators and security settings. We agree your goals, name a champion in each department, and plan who hears what and when. Nothing in your organization changes.
Step 2: Learn how each department works.
We sit at your counter and ride along in the field while real work happens. We go through your forms, your ordinances and fees, your printed documents, who does what, and what happens when things go wrong. We write it all down as your department's Configuration Brief: your workflow, in plain words, as Zanevan One will run it. Your department head signs it.
- You signConfiguration Brief
Step 3: See it working, with your settings.
Within days you see your own forms, stages, fees and wording on screen. Then your staff work through it on your city's own test site, signed in with their own logins, on practice data. Tell us what to change; most changes are back on the test site in a day or two.
Step 4: Bring your records across.
Your old records are moved over, complete. Nothing is silently “fixed”: anything odd is flagged so you can see it. We rehearse the move, and you check the counts, the totals and the records you choose before signing a Reconciliation Report.
- You signReconciliation Report
Step 5: Train your people on their own screens.
Short, practical sessions by role (clerks, inspectors, crews, supervisors), on your test site, so each person sees exactly what they will see on the day. Your champion is trained first and becomes your in-house expert.
Step 6: Test it yourselves, and sign off.
Your staff run an Acceptance Checklist built from your Configuration Brief, doing their own work. You decide when it is ready.
- You signAcceptance Checklist
- You signYour decision to go live
Step 7: Go live, with us beside you.
We are on site on go-live day and check in with you every day of the first week. For the weeks after, small changes are made quickly and you get a one-page summary each week. Then changing how you work becomes routine.
You sign at every step that matters: the Configuration Brief, the Reconciliation Report, the Acceptance Checklist, and the decision to go live.
You see it working with your settings before anything goes live.
Every department works through its own configuration on its own test site first.
Your records stay in your ArcGIS Online.
Zanevan One is built on ArcGIS. Your records are feature layers in your own organization, protected from the first one saved: the app never deletes a record, only the right staff can edit, and every change carries the name of the person who made it.
One department at a time, at your pace.
Start with one department. Each one after it builds on what is already in place, and the departments start working together as they join.
FAQ
Questions cities ask
Plain answers to what comes up most. If yours is not here, ask us directly.
Email Chase DirectlyWho owns our data?
You do. Your records are feature layers in your own ArcGIS Online organization, not in a Zanevan database. Anything Zanevan One keeps outside ArcGIS Online is only there to help the app run, and losing it would lose no record.
Do we need Esri licenses?
Yes. Zanevan One is built on ArcGIS and runs in your ArcGIS Online organization, so each person signs in with their own ArcGIS Online login. Staff who create or change records need a user type that can edit; people who only look things up can use a view-only user type. During implementation we work out with your IT staff exactly how many of each you need.
Is it secure?
Staff sign in on ArcGIS Online's own sign-in page; Zanevan One never sees a password. What each person can do comes from the groups your city manages in ArcGIS Online. The app never deletes anything: a record entered by mistake is voided, with a reason. Only the staff who work in a layer can edit it; everyone else reads it through a read-only view, and private details such as a caller's telephone number are left out of that view. Every change records who made it and when. Each city has its own deployment, connected only to its own organization.
How long does implementation take?
It depends on the department and on how much history comes across. As a guide, a single department takes a few months from the first conversation to the end of the support period after go-live, and departments after the first go faster because they build on what is already there. We give you a plan with dates for your city after the readiness step, and we never skip a sign-off to meet a date.
How are our staff trained?
By role, on your own test site, with each person signed in as themselves, so they practice on exactly the screens they will use. Sessions are short and practical. Each department has a champion who is trained first, helps train others, and keeps the training material for new staff. Every role gets a one-page reference card.
What if our process changes after we go live?
That is what Zanevan One is built for. Your workflows are settings, not code. Fee changes and your own pick lists you make yourselves, in the app. Who may do what is your group membership in ArcGIS Online. Changes to forms, stages, printed wording or rules are made by us on request, shown to you on your test site first, then released. Adding a new column to your records is the one controlled step, and only with your yes, because it changes your system of record.
Do the demos show exactly what we will get?
No. They are high-level examples on an invented city. Your modules are configured to how your departments work, and you see and sign for that configuration before anything goes live.
Do we have to move every department at once?
No. Most cities start with one department and add the rest one at a time. Each new department finds the others' records straight away, and the rules that connect departments are switched on when both sides are ready.
What happens to our old records?
We map every old record to its new home, move it complete, and flag anything odd rather than quietly changing it. You check counts, totals and records you choose, and sign before the move is done for real. Your old system stays available, read-only, as an archive.
From Zanevan Engineering
Built by an engineering firm.
Zanevan One is built by Zanevan Engineering: civil and structural engineering, land surveying and geospatial services, under one firm. It is held to the same standard as the rest of our work.
Visit zanevan.comTalk to us
Tell us how your departments work today.
We will walk through it with you and show how Zanevan One would be shaped to the way your city works.