Basemap Composition
The Basemap Composition capability introduces a more flexible way to create and manage basemaps in NextGen Geo.
Administrators can now compose a basemap by combining multiple map services instead of relying on a single predefined basemap source. This allows different services, such as tile layers, vector tile layers, map image layers, Bing layers, HERE layers, or OpenStreetMap layers, to be selected, ordered, and reused as part of a single basemap configuration.
The new configuration workflow allows administrators to define the basemap title, assign tags, select the services included in the composition, control their rendering order, and generate a representative thumbnail for the basemap selector. Once saved, the composed basemap becomes available to end users as a standard selectable basemap.
This improves cartographic flexibility, supports richer basemap configurations, and makes it easier to create reusable basemaps tailored to specific operational or business needs.
Dashboard Data Sources
Dashboard configuration has been extended to support additional data source models for chart generation.
Dashboards can now be based not only on GIS layers or feature services, but also on REST services exposed through an OverIT-defined API and on SQL tables or SQL views selected from configured database connections.
This capability enables NextGen Geo dashboards to consume analytical data from external systems, backend services, aggregated datasets, or prepared database objects. The configuration model has also been aligned with the Report configuration approach: administrators no longer define custom SQL queries directly in the configuration form, but select predefined tables or views instead.
This improves security, maintainability, governance, and consistency between dashboard and report configuration, while allowing the same dashboard to combine charts based on feature services, REST APIs, SQL tables, and SQL views.
GeoSmartOperation
GeoSmartOperation introduces a modular and extensible component for exposing spatial data and supporting advanced geospatial operations within the NextGen Geo ecosystem.
The component has been designed to productize activities that previously required custom implementations, specialized ArcGIS Server Object Extensions, and high-level ESRI technical expertise. By providing a reusable and extensible framework, GeoSmartOperation reduces the need for project-specific development and lowers the dependency on rare profiles capable of writing, installing, and maintaining ArcGIS SOEs.
GeoSmartOperation also enables spatial data exposure without necessarily passing through ESRI infrastructure. This is especially useful for operational data coming from FSM, such as Work Orders, Operations, and Technical Objects, which can be exposed and consumed spatially in NextGen Geo even when they are not published as ESRI feature services.
The component strengthens NextGen Geo’s product architecture by improving reusability, delivery scalability, maintainability, and support for non-ESRI operational data sources.
Scenario and Hypothesis Cloning
Scenario Planning for Infrastructure has been enhanced with cloning capabilities for simulations and hypotheses.
Users can now duplicate existing simulations or hypotheses to create new planning alternatives starting from an already configured scenario. The cloned item inherits the relevant context and configuration from the original one, allowing users to modify only the elements that need to change.
This capability is particularly useful when teams need to create route alternatives, test variations of an existing hypothesis, preserve an original scenario while editing a copy, or accelerate iterative planning workflows.
Cloned simulations and hypotheses are managed as independent objects. Changes made to the cloned item do not affect the original one, allowing safer experimentation and better governance of planning alternatives.
Field Execution Improvements
The Field Execution area has been improved to provide a more controlled and operationally focused workflow for configuring, importing, visualizing, filtering, and inspecting work orders in NextGen Geo.
Administrators can now define the scope of work orders exposed by a Field Execution module using parameters such as operation center, work order status, work order type, creation time range, and import language. This allows different module configurations to be created for different operational contexts, teams, or geographical areas.
End users can open the configured Field Execution module to view work orders on the map, filter them through a dedicated panel, inspect work order details, and access related operations. The workflow supports a progressive drill-down from work order overview to work order details and operation-level information.
This improvement reduces data noise, improves operational focus, and supports map-based awareness of work order distribution and execution context.
Common Module Configuration – Multilanguage Management
The common module configuration experience has been improved to simplify multilingual label management and prevent missing labels when a user accesses a module in a language that has not been explicitly configured.
The new approach introduces a fallback mechanism for multilingual fields. If a translation is not available for the user’s current language, the system displays the default configured value instead of leaving the label empty.
This makes module configuration safer and easier to manage, because administrators are no longer required to populate every language field manually. Optional translations can be added progressively, while the default language ensures that titles, descriptions, and labels remain visible and understandable.
The multilingual configuration interface has also been simplified to reduce repetitive actions and improve readability for administrators.