Enterprise ESRI Consulting & Integration Services
Esri Consulting & Integration Services for Enterprise Environments
Esri often holds the geospatial context behind assets, infrastructure, service areas, field activity, environmental conditions, facilities, routes, and operational risk. Microsoft platforms, enterprise applications, and operational systems often carry the workflows, reports, documents, collaboration, and data environments that teams use to act on that location intelligence. Risk appears when GIS remains isolated from the systems where operational decisions are made.
For enterprise IT, GIS, and operations leaders, Esri integration is not only about displaying maps in another tool. It determines how geospatial data moves, how field workflows connect to business processes, how location intelligence supports reporting, and how teams trust the spatial context behind operational decisions.
i3solutions delivers Esri consulting and integration services for organizations that need ArcGIS, geospatial data, field applications, dashboards, and spatial workflows to operate reliably across the enterprise environment. Our work focuses on geospatial data ownership, application integration, workflow continuity, reporting needs, Microsoft platform alignment, and the architecture required to support daily operations.
The result is a governed connection between geospatial systems and the enterprise operating environment, so location data, field activity, operational reporting, and business workflows remain reliable as requirements change.
Assess Esri Integration Risk Before Systems Connect
Esri integration should begin with a clear view of geospatial data ownership, field workflows, reporting needs, application dependencies, Microsoft platform impact, identity requirements, and support expectations. i3solutions evaluates the current environment before recommending an integration path, architecture model, or implementation approach.
Where Esri Integration Efforts Break Down
Esri integration efforts often break down when GIS is treated as a standalone mapping system instead of an operational data and workflow environment. Maps may be accurate, but the business process around them may still depend on disconnected spreadsheets, manual updates, separate reporting tools, or custom applications that do not share reliable location data.
These issues become more serious when ArcGIS supports asset management, field operations, planning, environmental monitoring, infrastructure, public-sector operations, utilities, logistics, facilities, or other mission-critical workflows.
GIS Data Remains Separate From Operational Systems
ArcGIS may hold the spatial record, while asset, customer, project, service, finance, or operational data lives elsewhere. When those systems are not connected, teams struggle to maintain consistent records and often rely on manual reconciliation to make location data useful.
Field Workflows Do Not Connect to Business Processes
Field teams may collect inspections, observations, asset conditions, location updates, or service information in Esri tools, but downstream work often continues in Microsoft applications, enterprise systems, reporting environments, or custom workflows. Without integration, field activity becomes disconnected from the processes it is supposed to inform.
Spatial Reporting Requires Manual Assembly
Leaders often need to see location-based activity alongside operational performance, asset status, service levels, risk indicators, or financial data. When Esri data does not connect with reporting environments, teams create manual map exports, spreadsheet summaries, screenshots, or disconnected dashboards.
GIS Access and Enterprise Identity Are Not Aligned
Geospatial systems often contain sensitive infrastructure, facilities, environmental, customer, or operational data. When ArcGIS access, enterprise identity, Microsoft permissions, application roles, and external sharing models are not aligned, the organization inherits security gaps and audit complexity.
Custom Applications Use Geospatial Data Inconsistently
Many organizations build custom portals, dashboards, workflow applications, or reporting tools that need location intelligence. If the application architecture does not define how Esri data is consumed, refreshed, secured, and governed, the result is brittle integration and inconsistent decision support.
What Esri Integration Requires
Esri integration is the controlled design of how geospatial data, maps, field workflows, spatial analytics, operational reporting, identity, and business applications operate across the enterprise environment. It is not a collection of disconnected map embeds or one-off data exports.
For Microsoft-centric organizations, Esri integration often affects Azure, SQL Server, Power BI, SharePoint, Teams, Microsoft 365, Power Platform, Dataverse, custom .NET applications, data platforms, identity systems, and operational workflows. For other organizations, the same issues apply across ERP, asset management, field operations, reporting, data, and custom business systems.
Integration as an Operational Decision Support Requirement
Geospatial data becomes more valuable when it informs the systems where operational work occurs. Location context may affect dispatch, planning, inspections, asset decisions, service coverage, environmental review, emergency response, or infrastructure investment.
i3solutions evaluates how Esri data should support operational decisions before defining the technical approach. The goal is not simply to surface maps. It is to make spatial information reliable, actionable, and supportable inside the workflows teams already use.
Integration as a Data and Reporting Decision
Esri data often needs to combine with operational, asset, finance, project, service, customer, or enterprise platform data. These reporting needs require clear decisions about source systems, spatial data ownership, refresh timing, transformation rules, validation, and dashboard trust.
i3solutions evaluates geospatial data flow and reporting dependencies before recommending an integration architecture.
Integration as a Governance and Access Decision
Esri integration affects access control, data classification, user roles, external sharing, application permissions, audit evidence, and long-term ownership.
i3solutions incorporates governance into the integration path from the beginning. This reduces the risk of creating GIS connections that work technically but are difficult to operate, secure, or maintain.
How Esri Connects Into the Enterprise Environment
Esri integration is not a single technical pattern. The right approach depends on the geospatial data involved, the enterprise systems affected, the workflow supported, the identity model, and the level of governance required.
i3solutions evaluates whether ArcGIS services, APIs, data synchronization, custom applications, Power BI reporting, SharePoint integration, workflow automation, identity integration, or hybrid architecture is the right path for each Esri integration.
Esri to Azure, SQL Server, and Enterprise Data Platforms
ArcGIS data often needs to interact with Azure-hosted applications, SQL Server databases, data platforms, integration services, and operational systems. These integrations require clear decisions about data ownership, synchronization, performance, security, and support. i3solutions designs Esri-to-data-platform integration patterns that allow geospatial data to support enterprise applications and reporting without creating fragile point-to-point dependencies.
Esri to Power BI and Reporting
Location intelligence often needs to appear in executive dashboards, operational reports, service metrics, risk views, and performance reporting. Power BI may need to combine geospatial data with operational, financial, project, asset, or customer data. i3solutions designs reporting integration patterns that clarify spatial data ownership, refresh timing, transformation rules, validation requirements, and dashboard trust.
Esri to SharePoint and Microsoft 365
Geospatial workflows often involve documents, records, inspections, field notes, permits, project files, or supporting evidence that need to live in governed Microsoft 365 environments. i3solutions supports Esri and SharePoint integration where maps, records, documents, metadata, permissions, and collaboration spaces need to remain connected to the operational process.
Esri to Teams and Collaboration Workflows
Location-based events often require cross-team coordination. A field issue, asset condition, environmental observation, or service area update may need to trigger communication inside Teams or another collaboration environment. i3solutions designs Esri-connected collaboration patterns that clarify what information should surface, who should act, and how context should remain connected to the system of record.
Esri to Power Platform
Power Apps and Power Automate can extend Esri-connected processes when teams need field intake, approvals, task routing, notifications, internal apps, or workflow automation across systems. i3solutions evaluates where Power Platform should support Esri-related workflows and where stronger integration architecture is required to avoid unmanaged automation.
Esri to Enterprise Line-of-Business Systems
GIS rarely operates alone. Asset systems, ERP platforms, work order systems, permitting systems, environmental databases, facilities applications, and custom line-of-business systems may all need geospatial context. i3solutions designs integration patterns that connect Esri with the systems that own operational work, assets, service activity, or business records.
Esri API and Custom Application Integration
Some Esri integrations require more than standard connectors or embedded maps. Custom applications, portals, operational dashboards, field tools, or business systems may require APIs, custom services, data transformation, or secure integration logic. i3solutions develops custom integration components where needed to support governed geospatial data movement, workflow continuity, and long-term supportability between Esri and enterprise systems.
Esri Identity and Access Integration
Geospatial systems often contain sensitive operational, infrastructure, environmental, facilities, or public-sector data. Identity integration needs to account for user roles, group membership, external access, single sign-on, permissions, and administrative control. i3solutions supports identity-aware integration patterns involving Microsoft Entra ID where relevant, ArcGIS access models, platform permissions, and governance controls.
How i3solutions Structures Esri Consulting & Integration Services
i3solutions structures Esri consulting and integration services as a defined delivery sequence. The work begins with GIS and process analysis, moves through enterprise alignment and integration architecture, and continues through implementation, validation, stabilization, and handoff.
This approach is designed for enterprise environments where Esri work needs to account for security, data integrity, field workflow continuity, reporting, and long-term support.
Esri & Geospatial Workflow Assessment
i3solutions reviews the Esri environment, ArcGIS data, maps, services, field workflows, applications, user roles, reports, integrations, APIs, connected systems, and known operational issues involved in the engagement. This assessment identifies where GIS creates operational dependency, where manual workarounds exist, and where geospatial data ownership needs to be clarified.
Enterprise Environment Alignment
Esri needs to fit within the broader enterprise environment. i3solutions evaluates how the work affects Azure, SQL Server, Microsoft 365, SharePoint, Teams, Power Platform, Power BI, Entra ID, custom applications, ERP systems, asset systems, reporting, and governance where relevant. This step clarifies where Esri should own spatial data, where enterprise systems should own operational records, and where integration or workflow responsibility needs to be defined.
Geospatial Data Flow & Ownership Mapping
Identity integration depends on clear decisions about user source, lifecycle triggers, provisioning rules, deprovisioning responsibility, group mapping, role assignment, access review, and exception handling. i3solutions maps how employees, contractors, partners, customers, and administrators move through the identity lifecycle so access remains controlled as roles and systems change.
Target Architecture & Integration Model
Once the current environment is understood, i3solutions defines the appropriate target architecture. This may involve ArcGIS services, APIs, Azure services, SQL Server, Power Platform, SharePoint, Power BI, custom applications, identity integration, data synchronization, or middleware services. The architecture is selected based on operational need, governance requirements, supportability, security, and long-term platform fit.
Implementation & Validation
Implementation may include Esri configuration, API development, data synchronization, reporting integration, workflow automation, identity integration, custom application development, middleware services, and validation of geospatial business rules. Integrations and related workflows are tested against real operational scenarios, not only technical connection success.
Stabilization, Documentation & Handoff
After implementation, i3solutions supports stabilization, issue resolution, monitoring validation, documentation, and knowledge transfer. Internal teams receive the context needed to operate integrations, manage data changes, resolve exceptions, and support the connected Esri environment over time.
Esri Integration Without Disrupting Operations
Esri consulting and integration work usually happens while teams continue to depend on maps, field data, asset information, location dashboards, service areas, inspections, and operational reporting. i3solutions plans Esri work around operational continuity, field workflow dependency, and support readiness.
Maintain Critical GIS Continuity
Business-critical GIS processes are sequenced so field, operations, planning, asset, and leadership teams can continue working while integrations, applications, or architecture changes are designed, implemented, and validated.
Reduce Risk Through Phased Implementation
Esri integration work is divided into manageable phases based on business priority, data dependency, application complexity, workflow impact, and production risk.
Support Coexistence During Transition
Some organizations need current and future GIS patterns to operate in parallel for a defined period. i3solutions plans for coexistence so teams understand which systems remain authoritative, which workflows have changed, and how exceptions should be handled.
Address Manual GIS Workarounds Before They Scale
Manual map exports, spreadsheet reconciliation, duplicate data entry, email-based field updates, and disconnected dashboards often grow around GIS integration gaps. i3solutions identifies those workarounds before they become permanent features of the connected environment.
Build Supportability Into the Architecture
Planning accounts for monitoring, logging, documentation, data ownership, update rules, and escalation paths. The result is an Esri environment that is not only configured or connected, but supportable.
Connect Esri with the Systems That Depend on Location Data
Esri decisions affect geospatial data, operational reporting, field workflows, identity, access governance, application architecture, and long-term support. i3solutions defines the integration path before connections are built so spatial information supports the operating model, not only the map layer.
Governance, Security & Trust in Esri Consulting and Integration
For enterprise and regulated organizations, Esri decisions affect sensitive geospatial data, field activity, user access, application permissions, maps, reports, audit evidence, and long-term data ownership. Governance and security should not be treated as final checklist items after systems connect.
i3solutions delivers Esri consulting and integration services through senior, US-based teams experienced in Microsoft-centric and enterprise integration environments, so governance, security, documentation, and compliance considerations are addressed by experienced specialists from the start.
Geospatial Data Ownership and Governance
Esri integrations often depend on authoritative layers, data stewardship, update rules, publishing controls, and ownership between GIS, operations, IT, and business teams. i3solutions reviews geospatial data ownership before defining the integration model.
Sensitive Location Data Handling
Geospatial data may expose infrastructure, facilities, customer locations, environmental assets, operational risk, public-sector resources, or security-sensitive information. i3solutions incorporates classification, access, retention, and sharing requirements into planning.
Audit Evidence and Traceability
Enterprise IT and GIS leaders need to explain how geospatial data connects with enterprise systems, where location data moves, which platform owns each process, how changes are validated, and who owns the integrated environment. i3solutions produces documentation that supports internal governance, support readiness, and audit-facing review.
Senior US-Based Delivery
Esri work often requires access to sensitive spatial data, operational workflows, credentials, applications, and production environments. i3solutions uses senior, US-based Microsoft and integration specialists so enterprise teams have direct access to experienced professionals throughout assessment, implementation, stabilization, and handoff.
Complex Esri Consulting and Integration Challenges We Handle
Not every Esri engagement is straightforward. Many enterprise environments contain disconnected GIS data, field workflows, custom maps, legacy applications, duplicated asset records, reporting gaps, and undocumented data ownership.
i3solutions is best aligned to Esri work where geospatial data, enterprise systems, governance, and long-term support matter.
Disconnected Customer & Account Data
Organizations often struggle when Salesforce, ERP, finance, service, reporting, and Microsoft systems each hold partial customer or account information. i3solutions clarifies ownership, data flow, update rules, and reporting impact before integrations are built.
Manual CRM Reconciliation & Duplicate Entry
Native connectors may not support the security, transformation, monitoring, or business logic required in enterprise environments. i3solutions evaluates when connectors are sufficient and when custom API or middleware development is needed.
Cross-Platform Sales & Service Workflows
Customer-facing processes often span Salesforce, Microsoft 365, Teams, SharePoint, Power Platform, ERP systems, finance systems, and custom applications. i3solutions maps process dependencies before defining the integration architecture.
Reporting & Dashboard Gaps
Salesforce reporting often needs to align with operational, finance, service, project, or executive reporting. i3solutions evaluates how Salesforce data should flow into Microsoft reporting environments without weakening data trust.
Disconnected Asset & Location Data
Organizations often struggle when ArcGIS, asset systems, ERP platforms, CRM systems, project databases, and reporting environments each hold partial location or asset information. i3solutions clarifies ownership, data flow, update rules, and reporting impact before integrations are built.
Field Workflow & Operational Handoffs
Field activity may begin in Esri tools, but follow-up work often depends on Microsoft workflows, enterprise applications, documents, dashboards, task routing, or internal applications. 3solutions maps how field data should move into the systems that drive operational action.
Map Exports & Manual Reporting
When spatial analysis does not connect to reporting environments, teams rely on static maps, screenshots, spreadsheets, and manual summaries. i3solutions evaluates how Esri data should flow into Power BI and other reporting tools without weakening data trust.
Custom Application & Portal Integration
Custom applications often need to consume maps, geospatial layers, location services, or spatial data from ArcGIS. i3solutions designs integration patterns for portals, dashboards, .NET applications, and business systems that need governed access to GIS data.
Identity, Sharing & External Access
GIS environments often involve internal users, field teams, contractors, partners, public-facing applications, or external stakeholders. i3solutions evaluates how identity, sharing, permissions, and access reviews should operate across Esri and enterprise environments.
What Esri Consulting and Integration Enables When Done Correctly
Esri consulting and integration reduces the operational friction created when geospatial systems, enterprise applications, and reporting environments do not work together cleanly. When the work is handled with architecture, governance, and ownership in place, teams spend less time reconciling spatial data, exporting maps, and working around disconnected field or reporting processes.
A well-structured Esri approach improves more than GIS connectivity. It creates clearer geospatial data ownership, stronger reporting trust, better access control, more reliable field workflows, and stronger visibility across location-dependent operations.
Stronger geospatial data control
Layer ownership, update rules, publishing responsibility, and support expectations are defined before integrations scale.
Cleaner geospatial data movement
Source systems, validation logic, transformation rules, and downstream reporting impact are clarified.
More reliable field and operational workflows
Inspections, asset updates, field notes, task routing, documents, and exceptions move across platforms with less manual follow-up.
Better security posture
Identity, service accounts, API access, sensitive location data, and administrative roles are reviewed before implementation.
Improved reporting confidence
Esri data flows are structured so leaders understand where spatial information comes from and how it changes.
Better enterprise environment alignment
Esri operates more effectively with Microsoft platforms, reporting tools, custom applications, operational systems, and connected business processes.
Related Platform Integration Services & Resources
Esri consulting and integration often raises broader decisions about geospatial data ownership, Microsoft reporting, field workflow automation, custom application architecture, and internal delivery capacity. These related services may be useful for organizations evaluating the right integration path before or after Esri work.
Enterprise Platform Integration Services
For organizations connecting external line-of-business systems with Microsoft environments through governed architecture, data flow, workflow continuity, identity alignment, and long-term support.
Power BI Services
For organizations that need location-aware reporting, operational dashboards, geospatial analytics, or executive visibility built on trusted data flows.
Custom Application Development Services
For organizations building portals, dashboards, field applications, operational tools, or .NET applications that need to consume Esri data or spatial services.
Hire Microsoft Integration Specialists
For organizations that need senior embedded Microsoft expertise to support internal teams during Esri integration, geospatial data integration, custom application development, reporting alignment, or post-integration stabilization.
Who Esri Consulting & Integration Services Are Designed For
i3solutions’ Esri consulting and integration services are designed for organizations where ArcGIS, geospatial data, field workflows, operational dashboards, or location intelligence need to connect reliably with enterprise platforms, reporting environments, or Microsoft systems.
These services are best suited for initiatives where governance, security, data trust, workflow continuity, and long-term support matter as much as the GIS work itself.
This service is a strong fit when Esri work has implications for operations, reporting accuracy, field workflows, security posture, compliance obligations, or the broader enterprise environment.
Best Fit Scenarios:
- Esri or ArcGIS needs to connect with Azure, SQL Server, Microsoft 365, SharePoint, Teams, Power Platform, Power BI, Entra ID, Dataverse, custom Microsoft applications, or other enterprise systems.
- Field workflows, inspections, asset updates, environmental observations, facilities data, or operational activity need to connect with business systems.
- Teams rely on manual map exports, spreadsheets, duplicate entry, email handoffs, or static dashboards to use GIS data outside Esri.
- Esri and other systems contain overlapping or conflicting versions of asset, location, project, customer, service, or operational data.
- Esri decisions affect sensitive location data, identity, access control, regulated information, or audit-facing processes.
- Legacy, ERP, asset management, infrastructure, environmental, field operations, or proprietary systems need to exchange data with Esri and Microsoft platforms.
- Internal IT, GIS, or operations teams need senior Microsoft integration expertise, architecture support, execution capacity, or embedded specialists for Esri integration workstreams.
While many i3solutions Esri engagements involve Microsoft platform integration, the service is also relevant when ArcGIS needs to connect with enterprise applications, operational data, field workflows, custom systems, or reporting environments outside the Microsoft stack.
Some Esri requests are better handled by GIS administrators, Esri-focused consultants, or internal GIS teams when they do not involve enterprise integration risk, architecture impact, or operational dependency.
Less Suited for Purely Tactical Needs
- Basic map creation with no enterprise integration dependency.
- Routine ArcGIS configuration, layer cleanup, or GIS administration.
- Standalone cartography, spatial analysis, or visualization work.
- Simple dashboard updates that do not affect cross-platform data or workflow processes.
- One-off GIS troubleshooting unrelated to enterprise systems, governance, or long-term supportability.
i3solutions is best aligned to Esri initiatives that require practical technical execution, Microsoft platform expertise where relevant, and a clear connection between geospatial systems, enterprise workflows, data governance, reporting, and long-term operational value.
Why Choose i3solutions for Esri Consulting & Integration Services
Organizations engage i3solutions for Esri consulting and integration services when geospatial data and field workflows support work that is too important, too complex, or too risk-sensitive for isolated GIS configuration or ad hoc connectors.
i3solutions brings 30 years of Microsoft platform, integration, workflow, application, data, and enterprise delivery experience to work that requires more than technical connectivity. Our senior, US-based specialists assess what Esri supports before recommending how it should connect with enterprise platforms, what should change, and what should be governed differently in the integrated environment.
We work across Azure, SQL Server, Microsoft 365, SharePoint, Teams, Power Platform, Power BI, Entra ID, Dataverse, custom Microsoft applications, Esri, asset systems, data environments, legacy systems, and custom application environments. That breadth matters because Esri work rarely affects GIS alone. Location data, field workflows, reporting, identity, documents, assets, and business processes often span multiple platforms.
For enterprise IT, GIS, and operations leaders, the value is not simply configuring Esri or connecting maps. The value is arriving at an environment where geospatial data, field activity, reporting, access controls, and support responsibilities are more secure, more governable, more observable, and better positioned for the decisions that come next.
Proven Enterprise Outcomes & Practical Insight
Real-world case studies and expert perspectives showing how organizations operationalize Microsoft platforms with governance, scale, and confidence.
Handheld Reporting Replaces Fax Machines for a Rail Operator Serving 90,000 Riders Daily
Health compliance data on food safety got faxed in, then entered a second time by hand, across a network serving 500 stations in 46 states. i3solutions replaced the fax machines with handheld reporting, so crews capture data once and it routes securely to serve nearly 90,000 daily riders.
A SharePoint Document Management Platform Improves Communication by 30% for a Research Provider
A single outdated file server had grown unchecked for years across 150+ employees in multiple divisions, straining collaboration on work behind more than 900 clients. i3solutions built a SharePoint document management platform with centralized storage and version control, improving communication...
Frequently Asked Questions
Esri consulting and integration services involve supporting ArcGIS, geospatial data, field workflows, reporting environments, APIs, identity models, and business applications so location intelligence operates reliably across the organization. For Microsoft-centric organizations, this often includes integrating Esri with Azure, SQL Server, Microsoft 365, SharePoint, Teams, Power Platform, Power BI, Entra ID, custom applications, legacy systems, and operational data environments.
General Esri consulting may focus on GIS administration, map production, ArcGIS configuration, spatial analysis, or platform support. Esri integration focuses on how geospatial systems connect with enterprise platforms, Microsoft environments, reporting tools, applications, and operational workflows. i3solutions is best aligned to Esri work where the issue involves integration, application architecture, geospatial data movement, workflow continuity, governance, reporting, identity, or enterprise supportability.
Yes. Many i3solutions Esri engagements involve Microsoft platform integration because that is where our enterprise systems integration background is strongest. However, Esri consulting and integration work may also involve enterprise applications, operational data, field workflows, custom systems, reporting environments, or application architecture outside the Microsoft stack.
Yes. i3solutions supports Esri integration with Power BI where geospatial data needs to support operational dashboards, executive reporting, location-aware analytics, or spatially informed decision-making. The specific architecture depends on the data sources, refresh requirements, ownership rules, reporting needs, and governance requirements.
Yes. Esri can be integrated with SharePoint when documents, records, inspection materials, project files, permits, or supporting evidence need to connect with geospatial workflows. i3solutions evaluates whether SharePoint should own documents, records, collaboration spaces, metadata, or workflow artifacts connected to Esri processes.
Yes. Esri can connect with Azure-hosted applications, SQL Server, data platforms, APIs, integration services, and custom Microsoft applications. i3solutions evaluates how ArcGIS data and services should interact with Azure architecture so geospatial information remains secure, performant, and supportable.
Sometimes. Native capabilities may be enough for simple use cases, but enterprise Esri integrations often require custom APIs, middleware, data transformation, orchestration, monitoring, or secure integration services. i3solutions evaluates whether standard integration options are sufficient or whether custom components are needed for long-term supportability.
i3solutions reduces integration risk by assessing the current environment before implementation begins. That includes geospatial data ownership, workflow dependencies, enterprise platform impact, identity requirements, governance needs, reporting impact, and support expectations. This approach reduces the likelihood of creating integrations that work technically but fail operationally.
i3solutions is not positioned as a routine GIS administration provider. Our Esri work is best aligned to integration, architecture, application connectivity, Microsoft platform alignment where relevant, geospatial data flow, workflow continuity, reporting, and enterprise supportability. Routine GIS administration is usually better handled by internal GIS teams or Esri-focused managed services providers.
Organizations should begin by identifying which Esri data, maps, services, workflows, field processes, reports, applications, and users are affected. They should also clarify which systems own spatial data and where enterprise platforms support related workflows. A readiness review determines what should be integrated, redesigned, governed, stabilized, or retired.
i3solutions is best aligned to Esri initiatives involving enterprise system dependencies, workflow complexity, sensitive geospatial data, reporting impact, identity governance, or operational continuity risk. Simple map updates, routine GIS support, or low-risk visualization requests are usually better handled by GIS administrators or internal GIS teams.
