Managed services · AMS
Give enterprise GIS operations a defined support model.
Organize the ongoing work that keeps enterprise GIS usable as people, data, and projects change. FieldCraft Workforce coordinates service resources and delivery, with Tech Maven Geospatial providing technical direction. Define administration, monitoring, maintenance, data operations, and escalation responsibilities around your environment and business requirements.
What we work toward
A usable result, with a clear handoff.
- Clear ownership of recurring GIS operations
- A defined route for incidents and service changes
- Operating knowledge organized for continuity and handover
The work
Connect routine operations with accountable follow-through.
Enterprise GIS support spans platform tasks, data workflows, user needs, and dependencies outside the GIS team. We help asset owners define that operating model and help capture or survey firms support the continuing use of delivered geospatial environments. The AMS scope establishes supported systems, recurring tasks, access, reporting, and escalation. Coverage, response expectations, service levels, and change responsibilities are agreed for the engagement rather than assumed.
ArcGIS Enterprise administration
Scope administration of ArcGIS Enterprise and the selected GIS environment, including service configuration, user and group coordination, access requests, and related operational tasks.
GIS and IT issue coordination
Define monitoring, issue ownership, and escalation across GIS and its supporting IT dependencies. Coordinate hosting, storage, identity, and network issues with the designated technical owners.
Maintenance coordination
Plan recurring maintenance and agreed changes around dependencies, customer approvals, operational constraints, and the technical procedures applicable to the selected systems.
Data and publication operations
Coordinate recurring data refresh, validation, publication, and exception handling so operational datasets and services follow a defined update process.
Backup and recovery responsibilities
Review the environment's backup and recovery arrangements and define the tasks, dependencies, validation, and customer responsibilities included in the service scope.
Operational documentation
Maintain the agreed procedures, system context, ownership information, and issue records needed for consistent service delivery and an organized transition or handover.
Deliverables
Agree what good looks like.
- An agreed service scope and responsibility matrix
- A recurring operations and maintenance plan
- A monitoring and escalation process
- Service reporting and an issue record
- Operating documentation and handover guidance
Scoping inputs
Start with what you know.
- System inventory and operational dependencies
- Current procedures, issues, and recurring tasks
- Access, change-control, and customer ownership requirements
- Required coverage and service-level expectations
Delivery approach
A clear path from scope to handoff.
Review the environment
01
Understand the systems, data workflows, users, dependencies, and current support arrangements. Identify the work to retain internally and the work to include.
Define the service
02
Agree supported platforms, recurring tasks, access, coverage, reporting, response expectations, escalation, and change approval. Document any exclusions and customer responsibilities.
Operate and coordinate
03
Perform the agreed work, track issues, coordinate technical review, and route decisions or changes to the appropriate owner within the service process.
Review and adapt
04
Use service reviews to assess recurring issues, changing workloads, documentation, and planned improvements. Update the scope when systems or operational requirements change.
Questions
Before we start.
Does AMS include GIS Help Desk support?
It can, when included in the agreed scope. Platform operations and user-facing help desk work have different responsibilities, so intake, coverage, escalation, and the relationship between the two are defined together.
What support hours and service levels are available?
Coverage, response expectations, priorities, and service levels are determined during scoping. They depend on the selected environment, workload, access, dependencies, and the operating model agreed for the engagement.
Can you take over an existing GIS environment?
An existing environment can be the starting point. We review its condition, documentation, dependencies, access, and current responsibilities before defining onboarding, ongoing tasks, and any separate remediation or improvement work.
Connected services
Build the right scope around the work.
Enterprise GIS Help Desk
Create an organized way to receive, assess, and resolve GIS questions and issues.
GIS Development Services (ADS)
Connect maps, data, and operational processes through scoped application development and integration.
Geospatial Data Engineering & Publishing
Connect existing imagery, vectors, point clouds, video-related information, and asset records to useful services and applications.
Start a conversation
Bring one project. Define the next step.
Tell us what you have, what needs to work, and where delivery is getting stuck. We will help define the people, work packages, and technical path around that outcome.
Existing data · New capture · Managed teams · Ongoing support