Smart Scan for Network Analysis Workflow

Overview

Smart Scan is an optimization capability available in the Network Analysis Workflow.

It determines which Fiber Nodes require analysis during a workflow execution and helps avoid unnecessary processing of nodes that do not require analysis.

Smart Scan also controls how the configured Hydration Queries are refreshed based on the type of refresh required.

This is particularly useful for Network Analysis Workflows that run on a recurring schedule and process a large number of Fiber Nodes.

Instead of repeatedly performing the same processing for every Fiber Node, Smart Scan uses the configured priority, cadence, and refresh mapping to determine how the data should be processed.

Note: Smart Scan is configured within the Network Analysis Workflow. For information about creating and executing the complete Network Analysis Workflow, refer Network Analysis Workflow.

Prerequisites

Before configuring Smart Scan, ensure that:

Network Intelligence AI is enabled.
A Network Analysis Workflow is available.
The workflow has the required scan and hydration queries configured.
The user has permission to edit the workflow configuration.

Access Smart Scan Configuration

To access the Smart Scan configuration:

Navigate to AI Orchestration → Workflows.
Open the required Network Analysis Workflow.
Open the Smart Scan tab.

The Smart Scan page displays the current Smart Scan configuration.

To modify the configuration:

Open the Smart Scan tab.
Click Edit.
Configure the required Priority & Cadence settings.
Configure the Refresh Mapping settings.
Save the configuration.

Note: The available configuration options may depend on the workflow and its configured queries.

Enable or Disable Smart Scan

Smart Scan can be enabled or disabled using the toggle available in the Smart Scan configuration.

When Smart Scan is enabled

The workflow evaluates the Fiber Nodes identified by the Scan Query and determines which nodes require processing.

The processing decision considers the configured:

Priority
Cadence
Refresh rules
Node changes
Device membership changes

Only the Fiber Nodes that require processing are analyzed.

When Smart Scan is disabled

The workflow follows the legacy processing behavior.

The Scan Query identifies the Fiber Nodes, and the configured Hydration Queries are executed for the Fiber Nodes without Smart Scan determining whether each node can be skipped.

Note: Smart Scan is intended to reduce unnecessary processing for recurring Network Analysis Workflow executions.

Priority & Cadence

The Priority & Cadence section determines how frequently Fiber Nodes are processed based on their priority.

The configuration contains three columns:

Field	Description
Priorities	The Fiber Node priority associated with the configuration.
Cadence	The interval at which nodes with the selected priority are processed.
Scheduled Job	The scheduled job associated with that cadence.

Cadence

Cadence defines the processing interval for the associated priority.

For example:

00:15 represents a 15-minute cadence.
00:25 represents a 25-minute cadence.
24:00 represents a 24-hour cadence.

The cadence allows different priority levels to be processed at different frequencies.

For example, a higher-priority Fiber Node can be configured with a shorter cadence, while nodes with lower or unassigned priority can be processed less frequently.

Note: The cadence value must be within the minimum(5-minute) and maximum(24-hour) values supported by the Smart Scan configuration.

Default – Unassigned Priority Values

The Default – Unassigned priority values are handled row applies to Fiber Nodes that do not have one of the explicitly configured priority values.

This provides a default cadence for nodes without an assigned priority.

Refresh Mapping

The Refresh Mapping section defines which refresh modes are supported by each Hydration Query.

The table contains the following columns:

Hydration Query
Full Refresh
Rescope
Delta

Each row represents a Hydration Query configured for the Network Analysis Workflow.

Understanding Full Refresh, Rescope, and Delta

The Refresh Mapping section determines which Hydration Queries are executed for different types of changes detected for a Fiber Node.

Full Refresh

Full Refresh applies when:

A Fiber Node is new.
A Fiber Node escalates in priority.
A Fiber Node picks up devices that do not have data yet.

During a Full Refresh, all configured templates are executed for the applicable Fiber Node.

Full Refresh is mandatory and cannot be disabled.

Note: Because Full Refresh runs all templates, the Full Refresh option cannot be turned off from the Refresh Mapping configuration.

Rescope

Rescope applies when a Fiber Node covers fewer devices than it covered previously.

When the node's device membership decreases, data based on the previous membership may become stale. Rescope refreshes the affected data by re-running the Hydration Query templates selected under Rescope.

For example, if a Fiber Node previously covered 100 devices and now covers fewer devices, the data associated with the previous membership may need to be refreshed.

Only the templates selected for Rescope are re-run.

Delta

Delta applies when the condition or state of a Fiber Node changes, but the devices associated with the node remain the same.

In this case, Smart Scan does not need to perform a full refresh. It re-runs only the Hydration Query templates selected under Delta.

This allows the workflow to process the relevant changes without re-running templates that are not required for the change.

Fiber Node Incident

A Fiber Node Incident is the incident record generated as part of the Network Analysis Workflow execution for a Fiber Node that is processed.

The Fiber Node Incident contains the analysis and network information associated with the Fiber Node.

If Smart Scan determines that an existing Fiber Node does not require processing, the node is skipped and a new incident is not created for that execution.

First Workflow Execution

When the workflow runs for the first time and identifies Fiber Nodes that do not already exist:

The workflow identifies the Fiber Nodes from the source data.
New Fiber Node records are created.
Smart Scan determines the required processing.
The applicable Hydration Queries are executed.
The Fiber Nodes are analyzed.
Fiber Node Incidents are created as a result of the analysis, where applicable.

Example

Suppose the first execution identifies three Fiber Nodes:

If these nodes do not already exist, the workflow creates the three Fiber Node records.

After the nodes are processed, the corresponding Fiber Node Incidents can be viewed in:

Asset Dictionary → Fiber Node Incident

Subsequent Workflow Execution

When the same job runs again, Smart Scan checks the Fiber Nodes identified by the scan.

If the Fiber Nodes already exist and there is no relevant change that requires processing, Smart Scan skips those nodes.

Review Fiber Node Incidents

When a Fiber Node is processed by the Network Analysis Workflow, the resulting analysis is available through the associated Fiber Node Incident in the Assets Dictionary.

The Fiber Node Incident provides the analysis results and information about the current condition of the Fiber Node.

Steps

Navigate to Assets Dictionary.
Search for the required Fiber Node.
Open the Fiber Node record.
Select the Analysis tab.

Note: Last Telemetry On indicates when the latest telemetry data was received for the Fiber Node, while Last Analyzed On indicates when the Fiber Node was most recently analyzed as part of a Network Analysis Workflow execution. These timestamps may be different because new telemetry data may be available even when the Fiber Node has not yet been selected for analysis.

In This Article: