Enhanced Field Execution module

The Field Execution module provides a controlled, map-based workflow for configuring, importing, visualizing, filtering, and inspecting work orders within the NextGen Geo ecosystem. By introducing granular administrative filtering parameters—such as operation center, work order status, asset type, and creation time ranges—the system restricts data imports to specific operational boundaries. This configuration layer optimizes technician dispatching and service workflows by allowing administrators to eliminate irrelevant data noise, ensuring field operators interact only with actionable, geographically accurate work order details and related sub-operations.

Purpose of the feature

The purpose of this improvement is to make Field Execution more configurable and more aligned with operational workflows. Administrators can now define a narrower and more meaningful work order scope, while end users can work with a focused list of work orders related to a specific operational context. This is especially useful when different teams, areas, or operation centers need dedicated work order views.

Configuration enhancements

The module configuration includes a dedicated Field Execution Configuration area. This interface allows administrators to define the import and visibility criteria used by the module to determine which work orders are retrieved and made available.

User workflow

1. Navigate to the system administration dashboard by selecting the admin console icon from the primary application panel.

2. Open the module management framework by clicking Field Execution Configuration.

3. Select the data management tab to open the data ingestion control fields.

4. Define your target configuration parameters by clicking the corresponding dropdown fields, checkboxes, or text boxes outlined in the table below:

5. Click Save Configuration on the bottom toolbar to publish the scope rules to the target user workspace.

Zone and operation center configuration

Operation centers are organized within a hierarchical structure inside the system zone configuration. This dependency links specific operational centers with designated geographic map structures, ensuring that user modules automatically load with the correct spatial context.

User workflow

1. Navigate to the infrastructure topology area by clicking Zones within the administration console.

2. Select the target zone record from the hierarchical tree list to display its configuration property sheet.

3. Review or modify the structural metadata by filling out the designated fields outlined in the table below:

4. Click Apply Structural Changes to bind the operational maps to the selected zone or operation center tier.

Module access

Once configured by an administrator, customized Field Execution modules become available as individual entries within the primary module workspace. This allows the system to support multiple, isolated operational contexts derived from a single product capability.

User workflow

1. Navigate to the operator interface by launching the NextGen Geo user workspace.

2. Open the module management panel by clicking the primary navigation drawer on the left side of the screen.

3. Select the customized module entry dedicated to your assignment (for example, clicking Work orders - OC 1 or work orders for NE Operation Center).

4. Verify the visualization by observing the map workspace, which automatically renders the geographic distribution of work orders and related network asset layers side by side with a tabular work order list.

Work order list

The module displays a paginated, tabular list of work orders matching the active administrative configuration. Operators can view primary asset statuses, dates, and execution centers at a glance.

User workflow

1. Navigate to the active module view by launching your assigned Field Execution workspace.

2. Review the tabular rows within the primary list view panel to evaluate the high-level metrics detailed in the table below:

3. Control list density by clicking the pagination dropdown at the bottom of the table and selecting a record count limit per page.

4. Navigate through long datasets by clicking the Next Page or Previous Page arrow icons on the pagination ribbon.

Work order filtering

An inline filter panel allows end users to instantly restrict the active work order list and matching map markers to smaller, highly specific operational subsets.

User workflow

1. Navigate to the list view within the active Field Execution module window.

2. Open the criteria menu by clicking the expand arrow on the Filter Panel header.

3. Refine your list results by clicking into or selecting values from the searchable fields outlined in the table below:

4. Execute the query modification by clicking Search.

5. Revert to the default administrative dataset by clicking Reset.

Work order details

Opening a work order launches a deep-dive interface organized into discrete tabs. This allows operators to review structural, scheduling, and asset-specific metadata associated with a particular task.

User workflow

1. Navigate to the work order list view or click a work order marker directly on the active map canvas.

2. Open the detail dashboard by clicking the name string of the target record (e.g., clicking OCENE02362).

3. Access specific information blocks by clicking the individual navigation tabs outlined in the table below:

Work order operations

A dedicated sub-section allows users to drill down below the master work order level to inspect the individual execution components, called operations, that make up the total task.

User workflow

1. Navigate to the work order detail layout for a selected record.

2. Open the operational sub-tier by clicking WO Operations.

3. Review the summary table containing operation codes, activity types, status markers, duration variables, and progress timelines.

4. Open an individual operation row by clicking the expand arrow next to the operation code.

5. Inspect discrete operation metadata by clicking through its internal tabs outlined in the table below:

Functional behavior

Configurable import scope

The module no longer exposes a generic or uncontrolled set of work orders. Instead, the imported work orders are determined by explicit configuration criteria: operation center, status, type, creation period, and import language. This improves governance and prevents users from seeing irrelevant work orders.

Operation center-based workflows

Different module configurations can be created for different operation centers. This supports organizational separation and allows teams to work only with the work orders that belong to their operational area.

Map and list synchronization

The module combines a map-based view with a tabular work order list. Users can evaluate work orders geographically while also using structured list information for filtering and navigation.

Drill-down from work order to operation

The workflow supports progressive navigation:

1. Open the Field Execution module.

2. View the work order list.

3. Open a work order.

4. Review work order details.

5. Open related operations.

6. Inspect operation-level information.

Example scenario

An administrator configures a Field Execution module for the North East Energy OC operation center to isolate open maintenance work from the past 90 days. Users then load this profile to process localized tasks.

User workflow

1. Navigate to the admin panel and select Field Execution Configuration.

2. Configure the following explicit values:

   • Operation Center: North East Energy OC

   • Work Order Status: Open, Planned, Schedulable, In Charge, To reschedule

   • Work Orders created in the last: 90 days

   • Import language: English

3. Click Save Configuration.

4. Navigate to the user module entry panel and click work orders for NE Operation Center to load the focused, map-synchronized baseline.

5. Locate the target task by typing OCENE02362 into the search field and clicking Search.

6. Open the asset file by clicking the record name, then click WO Operations to analyze the sub-tasks assigned to the field technicians.

Benefits

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

Expected impact

This improvement makes the Field Execution module more configurable and more useful for real operational scenarios. The main value is the ability to configure the module around specific operation centers and work order criteria, then provide users with a focused map-based workflow for inspecting work orders and related operations.