Readiness Assessment
Know what your apps actually do before anyone quotes the rebuild.
A fixed-fee engagement that turns an intimidating multi-year decision into one scoped purchase a GIS manager can approve.
What you get
Feature inventory
Every menu item, button and tool in each app, with the Studio mechanism that replaces it, a complexity rating, and the config file or recorded test it came from.
Behaviour tests
Real inputs run against the live app, with the observed result and the query behind it. These become the acceptance suite. The rebuild is done when each test returns the same records, or you have signed off on a stated difference.
Decisions, with recommendations
The questions only you can answer: which form fields people use, which internal hosts must be replaced, whether a report anyone has forgotten is still needed. Each one carries our recommendation, and most of them shrink the build.
Roadmap and fixed-price quote
A phased order of work and a per-app, per-workflow price you can put in a budget submission.
Why it earns its fee
What the map does not show you
Layer counts are not complexity. The expensive parts of a Geocortex app are the ones nobody sees from the map, and they only surface by using the app and reading its configuration.
One example: Studio search tokenizes input and ranks by relevance. An ID lookup that returned 12 records in Essentials can return 80 in Studio unless it is rebuilt as a workflow. That repeats on every app whose users search by number. Why, and what to do about it.
How it runs
Outside-in. Behaviour first, network trace second, configuration third, code last and least. Requirements live in what users see. Code is where we go to settle arguments.
Capture the deployed configuration
We read each site's REST configuration over HTTP with a viewer login. No server access, no filesystem access, and we never contact your ArcGIS Server or internal hosts.
Walk every menu
Toolbars, "I want to" menus, layer and result context menus. A button declared only in a disabled module is dead config. It gets a row and a zero estimate, with the evidence cited.
Record what it does
Real inputs from your team, not harvested ones. Each test row captures the observed result and the query it fired.
Assess the risky rows first
Priority is uncertainty times blast radius, not difficulty. Anything that repeats across your whole estate or depends on something you control gets looked at before anything easy.
Interview with the tests open
Who uses this, which inputs are real, which fields matter. This is where scope comes down, with evidence on the table.
Common questions
What do we get from a Readiness Assessment?
A feature inventory of every menu item and tool in each app with its Studio mechanism and a source you can check, a set of recorded behaviour tests that become the acceptance suite, a decisions list where every open question carries our recommendation, and a phased roadmap with a fixed-price migration quote.
What access do you need?
A viewer login matching a real user role and the Essentials REST endpoint. We read the deployed configuration over HTTP. No server or filesystem access, and we never call your ArcGIS Server or internal hosts directly.
How long does it take?
It depends on estate size and how many apps carry workflows and reports. We agree a fixed duration before starting.
Do we have to proceed with the migration afterwards?
No. The inventory, tests, decisions and quote are yours to use with any vendor or in-house. Half the assessment fee is credited if you sign a migration with us within 90 days.