Scenario and hypothesis cloning

The new cloning capability allows users to duplicate existing simulations and hypotheses to create new planning alternatives starting from an already configured scenario. By enabling the direct replication of simulations, hypotheses, configurations, associated services, branch versions, and map contexts, this feature eliminates the need to manually recreate these complex structures from scratch. This enhancement optimizes field service workflows by allowing dispatchers and planners to rapidly evaluate multiple similar planning variations and accelerate iterative decision-making.

Purpose of the feature

The feature introduces the ability to clone existing scenario planning elements, allowing users to reuse an existing configuration as the starting point for a new alternative. The main goal is to support faster creation of planning variants. Instead of manually creating a new hypothesis and reconfiguring all related information, the user can clone an existing one and then modify only the elements that are different.

The table below outlines common use cases for this feature:

Main concept

Cloning creates a new item based on an existing simulation or hypothesis. The cloned item inherits the relevant configuration and context from the original item, allowing the user to continue working from a known baseline.

The table below details the specific configuration and context data inherited by the cloned object depending on the implementation rules:

The cloned item is then managed independently from the original one.

Hypothesis cloning

Description

Hypothesis cloning allows users to duplicate an existing hypothesis inside a simulation. A cloned hypothesis represents a new planning alternative based on the same initial configuration of the source hypothesis.

User workflow

1. Navigate to the simulation workbench by selecting the simulation module from the primary application menu.

2. Open a simulation that contains one or more existing hypotheses (for example, Crossing Ohio River) by clicking on the simulation row. The simulation detail page displays the list of available hypotheses.

3. From the hypotheses list, identify the hypothesis that should be used as the starting point (such as Minimize cost, Minimize impact, or Balanced route). The selected hypothesis already contains the configuration, branch version, service association, and planning context needed for the analysis.

4. Execute the clone action by clicking the clone icon located in the target hypothesis row. The system creates a new hypothesis based on the selected one, adds it to the same simulation, and displays it in the hypotheses list as a separate item.

5. Review the cloned hypothesis by clicking its name in the list to open it. The cloned hypothesis behaves as an independent working alternative where you can inspect details, description, related service, branch version, layers, attribute table, attachments, and last update information.

6. Modify the cloned hypothesis by clicking edit, making your required geometry or attribute adjustments, and clicking save. This allows you to test variations (such as changing route geometry from Balanced route copy) while preserving the source hypothesis.

Simulation cloning

Description

Simulation cloning allows users to duplicate a complete simulation, including its scenario context and related hypotheses. This is useful when a user wants to create a new planning scenario that is very similar to an existing one, but should evolve separately. For example, a project team may want to reuse the structure of an existing river-crossing simulation for a new planning cycle, a new geographic area, or a new set of assumptions.

User workflow

1. Navigate to the simulation tracking dashboard by selecting the simulation management option from the main navigation panel.

2. Open the simulation list where each simulation is displayed with information such as name, owner, status, and available actions.

3. Select the simulation to clone by clicking the checkbox next to the target simulation record that will act as the source template.

4. Execute the clone action by clicking the global clone button on the top toolbar. The system creates a new simulation based on the selected one, adds it to the simulation list, and renders it as a separate scenario container.

5. Work on the cloned simulation by clicking its row to open the workspace. From here, you can click edit to modify the simulation name, description, status, hypotheses, attachments, scenario data, and related planning information independently.

Functional behavior

Independent copy

The cloned item must be treated as an independent object. Changes made to the cloned simulation or hypothesis must not modify the original item. This is the core functional value of the feature: users can safely experiment with alternatives without losing or changing the source configuration.

Reuse of existing configuration

Cloning reduces manual configuration effort by reusing the source object as a baseline. This avoids repetitive setup of the elements listed below:

• Services

• Layers

• Branch versions

• Metadata

• Scenario context

• Attachments, where applicable

• Map configuration

Support for iterative planning

The feature supports an iterative workflow where users can progressively refine alternatives. The standard functional progression follows these phases:

1. Create an initial hypothesis.

2. Review it on the map.

3. Clone it.

4. Modify the clone.

5. Compare the original and the clone.

6. Keep the best alternative or create further copies.

Naming convention

Description

When an item is cloned, the system creates a recognizable copy. Cloned hypotheses use the suffix copy (for example, Minimize cost copy or Balanced route copy). This makes it clear that the new item was generated from an existing one and helps users distinguish original hypotheses from duplicated alternatives.

User workflow

1. Navigate to the asset list view by selecting the appropriate data tier from the sidebar.

2. Select the hypothesis to clone from the active data table.

3. Click the Clone icon on the action panel to automatically generate the duplicated asset.

4. Verify the suffix by observing the asset list, where the system automatically appends copy to the original name string.

5. Edit the system-generated name by clicking the Edit icon next to the heading field, entering your custom nomenclature, and saving your changes.

Example scenario

Description

A utility company is evaluating different options to cross the Ohio River with a gas transportation pipeline. The planning team already has a hypothesis called Balanced route which represents a compromise between cost, technical feasibility, and environmental impact. The team wants to evaluate a slightly different version of the same route without losing the original balanced alternative.

User workflow

1. Navigate to the Crossing Ohio River simulation workspace by selecting it from the dashboard.

2. Locate the Balanced route entry within the hypotheses management table.

3. Click the clone action item in that specific row to generate Balanced route copy.

4. Open the cloned hypothesis by clicking on Balanced route copy.

5. Modify the route attributes and layout by using the map drawing tools and property panels, then click Save.

6. Verify your changes by opening the original Balanced route to confirm its configuration remains unchanged while the cloned version functions as a standalone alternative.

Benefits

The cloning feature improves efficiency across several key metrics. The table below outlines the core benefits provided by this tool:

Expected impact

Description

The cloning feature improves the efficiency of scenario planning workflows in NextGen Geo. Its main value is the ability to duplicate existing simulations or hypotheses and use them as controlled starting points for new alternatives. This allows users to evaluate planning variations faster, preserve original scenarios, and manage iterative decision-making in a structured way.

User workflow

1. Navigate to the performance analytics dashboard to review scenario turnaround times.

2. Select the cloned scenario from the active workspace to verify the operational impact.

3. Click the comparison view tab to load both baseline and cloned metrics side by side.

4. Review the generated planning variations to confirm the structured decision path without having to compile separate external reports.