Skip Headers
Oracle® Communications Network Intelligence Concepts
Release 7.2.2

Go to Documentation Home
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

8 Configuring Plans

This chapter describes configuration planning using Oracle Communications Network Intelligence.

About Configuration Planning

Configuration planning supports complex network planning scenarios that require several configuration changes. It is principally used to support work order input for network engineers, such as:

  • Bulk trail update

  • Trail re-arrangement

  • Bearer or facility upgrades

  • Card slot movement

  • New service builds

  • New planned node builds

  • New transport facility or bearer creation

You capture live configuration changes to network resources in Network Intelligence (for example, site creation, equipment modification, or trail deletion) and view these actions - and interactions with other supported entities - in a configuration plan.

Configuration plans apply to the following entities:

  • Sites

  • Equipment, and the associated equipment hierarchy (cards, ports, logical ports, and so on)

  • Trails, and the associated trail hierarchy

You click a button on the GUI to record attribute and relationship changes to supported entities.

See "Recording Data for the Configuration Plan".

All configuration changes recorded are available in chronological order in a plan, and can be exported in various formats, or viewed in a report.

See "About the Configuration Change Report".

Creating a Configuration Plan

To create a configuration plan, complete the details of the plan, such as the name and planning type.

See "About the Configuration Plan Details View" for definitions of the fields.

About the Configuration Plan Details View

The configuration plan details view, selected by double-clicking a configuration plan in the tree browser, displays the plan and lists its primary attributes.

A configuration plan has the attributes described in Table 8-1.

Table 8-1 Configuration Plan Attributes

Plan attribute Description


The name used to identify the plan.

Planning type

The type of plan:

  • Configuration

  • Forecast

  • Migration

  • Outage

Configuration is the default.

Plan action

The task to be carried out.

You can add plan actions using

  • The Metadata administration web portal, which creates, administers, and maintains metadata data values in Network Intelligence.

    See the Domains chapter of Network Intelligence Developer's Guide.

  • Using the domain_value_stg table in the Staging schema. See the chapter on populating the staging database in Network Intelligence Developer's Guide.

Start date

The first time period date of the plan.

End date

The last time period of the plan.


Whether this plan is shared with other users.


Other information about the plan (for example, information relating to part of a works order to be completed using the plan).

Configuring a Sample Configuration Plan

In this plan, Network Intelligence is used to make changes to the path taken by an existing trail, by reconfiguring its parent trail assignments. All resource configuration changes are captured against a configuration plan called Reconfigure Trail. All changes can be viewed in the Configuration Change report.

The sample configuration plan the attributes described in Table 8-2.

Table 8-2 Sample Configuration Plan Attributes

Plan attribute Description


Reconfigure Trail.

Planning type

The type of plan:

  • Configuration

This field cannot be edited.

Plan action

Trail upgrade.

Start date

January 4, 2013.

End date

January 7, 2013.




This plan forms the basis for a Trail Rearrange works order for a trail called Intersite 1GB Ethernet Trail. The works order must be completed before 31st March, 2013.

Recording Data for the Configuration Plan

You create a configuration plan to record configuration actions. Icons on the Network Intelligence toolbar are used to start and stop recording.

You can examine the data in the configuration report. See "About the Configuration Change Report".