Skip Headers
Oracle® Communications Network Intelligence Concepts
Release 7.2.2

E17891-03
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

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

7 Forecasting Service Demands

This chapter describes how to determine future service demand in the network using Oracle Communications Network Intelligence.

About Forecasting Service Demands

Network Intelligence enables planning engineers to forecast the demands for a service with a quantity of trails that require path routing. A forecast is defined as a collection of service demands with expected future trail growth counts for one, or more, future time periods.

The forecast is then converted to individual network point-to-point service demands, each of which consists of a route. A route is a collection of one of more trails that have the same start site, end site, capacity and service references, and a quantity of trails that require routing. The service demands are used to automatically configure routes for multiple trails over the existing, and new planned network.

About Forecast Plans

Forecast Creation Manager uses a wizard to create forecast plans. It provides the following options:

Forecast plans are displayed in the tree browser in predefined folders based on plan type for easy navigation. Double-click a tree browser folder to expand the selection; double-click any plan to open, and edit, the plan detail view. The plan detail view displays the primary attributes of the plan selected.

The ”create” icon is used to generate a new plan. Configuration of the plan requires a name; the planning type is forecast plan. Enter start and end dates for the plan, and the period type, which is measured in months, quarters, or years. When the number of periods is specified, the end date is automatically completed. Fill in the service demand values for the future plan dates; at least one service demand is required to route a forecast plan.

About Forecast Plan Views

When a plan has been completed, several tabbed views are available:

Any entities, such as cards or sites, that are created within a plan are only available to that plan.

A plan can be shared, which makes it visible to other users in the plans tree browser.

About the Plan Details View

The plan details view displays the plan entity and lists its primary attributes.

Each plan has the attributes outlined in Table 7-1.

Table 7-1 Plan Details View Attributes

Plan attribute Description

Name

The name used to identify the plan.

Planning type

The type of forecast:

  • Configuration

  • Forecast

  • Migration

  • Outage.

Start date

The first time period date of the plan.

End date

The last time period of the plan.

Archived date

The date before which the plan was archived, if archived.

Period type

The time period units used by the plan.

Shared

Whether this plan is shared with other users.


About the Service Demands View

The service demands view contains all of the service demands that comprise the plan, with all of the plan values for trail growth on the routes defined by the service demands.

About Carrying out Actions on the Service Demands View

Right-click the service demands view, or use the buttons displayed to perform actions on the view as defined in Table 7-2.

Table 7-2 Service Demands View Operations

Action Purpose

Analyze this plan

Attempt to analyze the selected service demands in the plan using the plan route manager.

Maintain

Display the plan maintenance manager window to alter the plan.

Edit history

Display the plan edit history which details all of the edits to the plan (user, date, and value change).

Edit selected routing demand route

Display the route view for the selected service demand route entity to allow you to change the policy of the route.

View selected service demand policy

View the service demand's policy.

You can change routing rules for a particular service demand, if necessary. The service demand may have failed but could be successful using a different set of routing rule criteria.

Edit Mode

Toggle between the plan field edit mode and the service demand selection mode.

Select All

Select all of the service demands in the plan.

Unselect

Unselect any selected service demands currently selected in the plan.

Delete Selected Service Demands

Select rows to delete. The view is automatically refreshed after deletion is confirmed, and the service demands are removed from the view.

Save Changes

Saves any changes that have been made to the plan during editing. This option is only available if the plan is in edit mode.

Save as HTML

Saves the plan to a user defined HTML file for viewing or distributing externally in Microsoft Word compatible format.

Save as CSV

Saves the plan to a user defined CSV file for viewing or distributing externally in spreadsheet format.

Copy to Clipboard

Saves the plan for pasting it elsewhere.

Open in Excel

Saves the plan to a user defined XLS file and displays it directly in Microsoft Excel.


About the Studies View

Each time a plan is routed it can be saved with the route solutions as a plan report. The studies view displays a list of plan reports for the selected plan. You can compare forecast reports and do the following:

  • View the relative numbers of route demands, paths, and circuits, and the relative success rates for services and customers;

  • View the tasks resulting from the routing forecast (for example, a suggested circuit route build).

See the Network Intelligence Help for instructions about comparing forecast reports.

About the Planned Entities View

The planned entities view displays a list of all entities that are planned for this plan.

Note:

These entities are only in scope within this plan and are not available to other plans.

To display an entity view for a planned entity, double-click an entity in the list.

About the Planned Trails View

The planned trails view displays a list of all trails that are planned for this plan.

Note:

These trails are only in scope within this plan and are not available to other plans.

To display a trail view for a planned trail, double-click a trail in the list.

About the Planned Equipment View

The planned equipment view displays a list of all planned equipment.

Note:

This equipment is only in scope within this plan and is not available to other plans.

To display an equipment view for a planned equipment, double-click an equipment in the list.

About the Planned Cards View

The planned cards view displays a list of all cards that are planned for this plan.

The format for this report is as shown in Table 7-3:

Table 7-3 Planned Cards View Attributes

Column name Data source

Site Name

The card's parent site name.

Equipment Name

The card's parent equipment name.

Slot Name

The card's parent slot name.

Card Name

The card instance name.

Card Definition

The card definition name.

Supplier

The card supplier.

Capacity

The capacity of the card.


Note:

These cards are only in scope within this plan and are not available to other plans.

To display a card view for a planned card, double-click a card in the list.

About the Planned Sites View

The planned sites view displays a list of all new sites that are planned for this plan.

Note:

These new sites are only in scope within this plan and are not available to other plans.

To display a trail view for a planned site, double-click a site in the list.

About the Planned Topologies View

The planned topologies view displays a list of all new topologies that are planned for this plan.

Note:

These new topologies are only in scope within this plan and are not available to other plans.

To display a trail view for a planned topology, double-click a topology in the list.

Creating a Plan By Selecting Routes

You can create a plan that selects routes, and applies service demand values to future time periods (for example, select a particular customer and capacity to display all routes of that type, and forecast service demands on those routes resulting from a projected 10% increase in capacity).

Creating a Plan by Selecting Network Entities and Applying Growth Criteria

You can create forecast plans by selecting any of the following network elements from the tree browser:

  • Topology

  • Equipment

  • Site

  • Trail

  • Service

  • Route

  • Customer

Use the context toolbar to select the type of data (for example, Trail or Equipment, and drag and drop the required NEs to the plan creation manager). Sort and select the trails that are in scope for the growth study, and enter the plan growth as a percentage in the format specified in Figure 7-1:

Figure 7-1 Creating a Plan by Selecting Trails in Scope for Growth Study

Description of Figure 7-1 follows
Description of "Figure 7-1 Creating a Plan by Selecting Trails in Scope for Growth Study"

Creating a Plan from an External File Source

You can create a plan by importing data from a file. This data takes the form of pre-prepared, comma separated variables (CSV), (for example, generated using Microsoft Excel). Network Intelligence supports two data types as inputs for plan generation:

Creating a Plan Using Service Demands

A plan containing a set of service demand entities can be created by importing a spreadsheet containing service demand line entries in CSV format. The contents of the service demand input file are loaded and validated, and routing process is carried out before displaying the plan service demands. This enables the plan service demands to be inspected before the plan is saved.

Figure 7-2 shows a sample file:

Figure 7-2 Creating a Plan from an External File Source

Description of Figure 7-2 follows
Description of "Figure 7-2 Creating a Plan from an External File Source"

In this format, each line of the file defines a service demand as described in Table 7-4:

Table 7-4 Service Demand Plan Outline

Column Name Description Column Order Number Compulsory Data Values

Demand Group

The name of a group to which the service demand belongs.

1

No

Customer

The name of the customer using the service demand.

2

Yes

Service

The name of the service required by the service demand.

3

Yes

Specified Capacity

The capacity bandwidth required (in Mb).

If this is specified here it overrides any capacity required set by the policy.

4

No

Priority

The priority allocated to this service demand on loading.

5

Yes

A Site

The start site name of the service demand connectivity requirement.

6

Yes

A Node

The start equipment node name of the service demand connectivity requirement.

7

No

Z Site

The end site of the service demand connectivity requirement.

8

Yes

Z Node

The end equipment node name of the service demand connectivity requirement.

9

No

30/06/2011

30/09/2011

The number of trail connections forecast for the service demand for a specified period.

There is no limit to the number of periods in a forecast.

The dates in the heading column correspond to each forecast period.

To be valid, dates must be entered in the format shown.

10

Yes


Validating Data

This section describes the validation carried out on imported data.

  • All dates must be in the required format (for example, DD/MM/YYYY for Europe, MM/DD/YYYY for the US). The date format depends on setting of the JAVA_LOCALE variable.

  • Demand Order is optional; if entered it can take any string value.

  • Customer names are mandatory, and must exist in Network Intelligence as customer entities with the same name specified in the file.

  • Service names are mandatory, and must exist in Network Intelligence as service entities with the same name specified in the file.

  • Capacity levels are mandatory, and must exist in Network Intelligence as capacity entities with the same name specified in the file.

  • A Site and Z Site are mandatory, and must exist in Network Intelligence as site entities with the same name specified in the file.

  • A Node and Z Node are optional, but if entered must exist in Network Intelligence as equipment entities with the same name specified in the file.

If the validation fails, a data error is displayed.

Understanding Data Errors

Table 7-5 lists the data errors reported if validation of the external file source fails:

Table 7-5 Forecast Manager Plan Data Errors

Data Error Description

Invalid A Site

The service demand row contains a site name that does not exist in Network Intelligence.

Invalid A Node

The service demand row contains an equipment node name that does not exist in Network Intelligence.

Same Location

Both sites in the service demand are at the same location, so the service demand does not require any routing.

Duplicated Route

The file contains two or more rows that reference the same service demand as described by A Site, Z Site, and Service.

You can merge these into one new service demand, or keep them separate. If merged, the forecast values are added.

Invalid Z Site

The service demand row contains a site name that does not exist in Network Intelligence.

Invalid Z Node

The service demand row contains an equipment node name that does not exist in Network Intelligence.

New Routes

Service demand rows in the file describe connectivity between the A and Z site which does not currently exist.

As a result, a new route is created on importing the plan.

These are not necessarily errors unless incorrect A and Z Site names have been input. You can create the new routes on importation.

No user privilege

The user attempting to upload the file has included routes that they do not have permission to use to create the plan.

To change user privileges, see Network Intelligence System Administrator's Guide.


Creating a Plan Using Bulk Service-Bandwidth Input Files

The bulk service demands are defined in CSV format, typically using Microsoft Excel. A sample file might look like the following:

Figure 7-3 Creating a Plan Using Bulk Service-Bandwidth Input Files

Description of Figure 7-3 follows
Description of "Figure 7-3 Creating a Plan Using Bulk Service-Bandwidth Input Files"

In this format, each line of the file describes a service followed by bulk capacity demands for future plan periods. The file contains no information about the A and Z connection details. Network Intelligence attempts to determine these details for the services in the file by using historical capacity growth on existing service routes.

The imported files are validated before import and must have the correct data headings. If the data titles are not exactly as described, the plan is not imported correctly and errors are returned.

After the bulk data is loaded, Network Intelligence derives the required service demands. It does this by finding the full set of routes that exist for the referenced services in the bulk import file.

Each route has a monthly growth value in bandwidth units, megabytes per second (Mbps). Network Intelligence takes the bulk bandwidth required (capacity) and apportions it by percentage to all routes belonging to the service that have monthly growth values greater than zero.

A route with higher monthly growth value is apportioned more of the bulk service capacity forecast that one with lower growth.

Validating Data

This section describes the validation carried out on imported data.

  • Demand Order is optional, and if entered can be any string value.

  • Customer, if entered, must be a valid customer name that exists in Network Intelligence.

  • Service name is mandatory, and must exist in Network Intelligence.

  • Capacity name is mandatory, and must exist in Network Intelligence.

If the validation fails, a data error is displayed. See "Understanding Data Errors".

About Maintaining a Forecast Plan

The plan maintenance manager allows you to make changes to a forecast plan. You can also edit parameters in an existing plan.

See the following forecast plan maintenance tasks

About Editing Forecast Plans

After the plan has been created, you can edit certain aspects of the plan through the Service Demands view. By selecting Edit Mode on the context menu, you can modify:

  • Any service demand total for a future date period;

  • A demand group number;

  • A customer name.

Any fields that have been edited will appear with a yellow background color until saved.

Note:

Changes are not saved until you click Save Changes in the action panel, or on the context menu.

To revert without saving, simply close the Service Demands view.

See the Network Intelligence Help for instructions about editing plans.

About Extending Forecast Plans

Extending a plan entails adding extra time periods and extra service demand values to the plan.

See the Network Intelligence Help for instructions about editing plans.

About Truncating Forecast Plans

Truncating a plan entails removing future time periods and service demand values from the plan. Only future plan periods can be truncated from the plan.

See the Network Intelligence Help for instructions about truncating plans.

About Archiving Forecast Plans

Archiving a plan entails removing past time periods and associated service demand values from the plan.

See the Network Intelligence Help for instructions about archiving plans.

About Cloning Forecast Plans

Cloning a plan entails creating an exact copy of plan details and the service demand list. No reports or editing details are copied when a plan is cloned.

See the Network Intelligence Help for instructions about cloning plans.

About Deleting Forecast Plans

Deletion of a plan entails deleting the plan itself, and all entities associated with the plan, including:

  • Plan service demands;

  • Plan routing run studies;

  • Planned entities associated with the plan;

  • Editing history;

  • Red line conditions.

Note:

After a plan has been deleted, it is removed from Network Intelligence. No back-up of deletions is maintained.

See the Network Intelligence Help for instructions about deleting plans.

About Adding Routes to a Plan

Routes (and their associated service demands) can be added to a plan after it has been created (for example, service demands that were overlooked on creation may be added, or additional service demand requirements added to the plan after the plan changes).

See the Network Intelligence Help for instructions about adding routes to a plan.

About Tracking the Accuracy of Plans

Plan accuracy can be tracked. Tracking plan accuracy is the process of checking (previously) planned service demand quantities against known inventory route quantities. After the network has been developed to meet a service demand for a particular period, it is then possible to track the degree to which the plan was accurate.

You can set specific colors to check the following, for example:

  • Forecast totals against planned totals.

  • Planned totals against actual live totals.

Differences in values are displayed as colored cells in the service demand list view. You can quickly check a forecast for accuracy, and make adjustments for future forecast periods.

See the Network Intelligence Help for instructions about setting up tolerance values for a plan to track plan accuracy.

About Carrying out Plan Growth Scenario Tasks

The plan maintenance manager enables you to perform different growth scenarios on the plan. Applying growth scenarios entails the selection of one, or more, service demands within the plan, and setting traffic growths in the XX.X percent format for a particular future period (you expect traffic to grow on the selected service demands by XX.X percent by the selected future plan period).

To apply growth criteria to the plan, choose from the following options:

  • Select demand orders, and set the growth for a future period date. The plan is altered to include the new demand orders and the expected growth.

  • Select services, capacities, customers, or routes, and set the growth for a future period date. The plan is altered to include the new periods and the expected growth.

See the Network Intelligence Help for instructions about applying growth scenarios to a plan.

About Carrying out Plan Tasks

You can use the plan maintenance manager to plan network elements that are associated with a forecast. The following new network elements may be planned within a forecast:

  • Trail

  • Equipment

  • Site

  • Topology

If a network is planned within a plan, it is only applicable within that plan. If a new planned network is planned outside of the plan, it is available for all plans.

See the Network Intelligence Help for instructions about planning new network elements.

About the Plan Routing Manager

The plan routing manager is used to design routes based on the service demands contained in a plan. You can select one or all service demands in a plan, and invoke Trail Routing Manager. When processing is complete, the path analysis results are displayed. You can save results, edit policies, edit rules for service demands, and rerun the service demand set.

To perform analysis on the plan, see "About Analyzing Service Demands from a Plan".

See the Network Intelligence Help for instructions about displaying and using Trail Routing Manager.

About Analyzing Service Demands from a Plan

You can analyze a selection of service demands from a plan:

  • Select the plan period and service demands that are in scope. Select the future period of the plan for routing.

    Only service demands that have a demand quantity greater than zero are displayed in the list. The demand quantity is calculated automatically by Network Intelligence as follows:

    • Select the Aggregate Approach check box to set the service demand total as the demand quantity less the total number of trails found in the database that belong to the route of the service demand (for example, if ten trails are forecast for a route defined by Site A, Site Z, Service B, and Capacity C, and eight trails in the database match this route, then the service demand is 10 - 8 = 2).

    • Deselect the Aggregate Approach check box to set the demand to equal the full demand value specified in each period column (no existing route trail total is deducted.)

  • Set prioritization for the service demands.

    You can set service demand priority individually by editing the service demand list. However, when analyzing a plan, you can also set priorities by group selection. Priorities can be set by:

    • Demand Group

    • Capacity

    • Customer

    • Service

    • No priority

    The lower the priority number, the higher is the routing priority. Service demands with a priority number of 1 are analyzed ahead of service demands with a priority number of 2, and so on. The order of prioritization can be altered before each analysis process.

    You do not have to set any priorities in this step (the default is no priority). If ignored, the original priorities are kept, and the service demands routed in that order.

  • Process the forecast service demand set.

    After setting priorities, the plan routing manager passes the list of in-scope service demands to Trail Routing Manager for routing. Each service demand is processed in turn, and the policy for each service demand is used to determine the path analysis rule criteria.

    Routing progress is displayed using a progress bar that updates after each service demand has been processed by Trail Routing Manager.

  • Process the forecast service demand set.

    After setting priorities, the plan routing manager passes the list of in-scope service demands to Trail Routing Manager for routing. Each service demand is processed in turn, and the policy for each service demand is used to determine the path analysis rule criteria.

    Routing progress is displayed using a progress bar that updates after each service demand has been processed by Trail Routing Manager.

  • Examine the routing results.

    When all of the selected service demands have been processed by Trail Routing Manager, the service demand routing results are displayed. The routing results consist of several sub-views.

    You can inspect the routing results by:

    • Viewing individual service demand results

    • Making policy edits including rule changes

    • Accepting routing solutions

    • Rejecting routing solutions

    • Rerunning the plan processing

    • Saving the plan process run as a report known as a study

    The routing result view displays the following views:

About the Analysis Summary View

The analysis summary view gives an overall view of the routing success of the plan run.

Within the analysis summary view, the summary panel itemizes the quantity of service demands, the individual trails successfully routed, and the percentage success factor.

It also displays the number of service demands carried out during the last routing run, and the number of individual trails successfully routed. This detail is important to note, and it enables you to monitor the number of successful routing solutions carried out during successive processing runs. The Number of Service Demands This Run figure should reduce with each successive processing run, as failed service demands are corrected, rerun, and successfully routed.

The failures displayed in the summary panel include:

  • Number of A ports

  • Number of paths found

  • Number of A terminating links

Individual service and customer successes are also classified.

About the Service Demand Summary View

The service demand summary view displays all of the individual service demands, and displays whether the routing was successful. Double-clicking any service demand displays the individual routing solution or failure view.

The service demands are color-coded as follows:

  • Red: The service demand is not routable; this is a failure.

  • White: The service demand is routable; this is a success.

  • Green: When you accept a routable service demand, the service demand changes to green after a short time.

  • Blue: When you select any service demand, it changes to blue.

About the Configuration Suggestions View

The configuration suggestions view details proposed changes to the build:

Suggesting New Links

Where no link exists previously, Trail Routing Manager suggests an entirely new link or path trail to be added to the network. This occurs only if the cumulative bandwidth demand between the two locations exceeds a pre-defined threshold.

Suggesting Existing Link Upgrades

This report applies where a route has direct link or path trails, and further bandwidth is required between the A and Z sites of the route.

If the nodes are known, a new trail build is suggested between two particular nodes in the network.

You can select the new trail suggested in the report and create it.

Suggesting Existing Equipment Upgrades

If a service demand requires port terminations, and there are none at a particular equipment node, but the node could be upgraded with a card insertion, then the type of card and node slot is itemized here for each site.

Suggesting New Equipment

If a service demand requires port terminations, and there are no nodes at the site where the ports are required, then a new equipment build is suggested. Select the required equipment and use the Equipment Configuration wizard to create the new equipment.

About the Planned Build View

When planned entities have been built as suggested, the entities subsequently appear in the Planned Build view.

The Planned Build view lists the following:

If the service demand fails due to lack of capacity (port or trail bandwidth), you can build planned entities using the plan maintenance manager, or the plan routing manager suggested build. After building the planned entities, rerun the service demand plan for the failed solutions.

Some previous routing failures should now be routed successfully.

About the Network Plan Impact Report

The network plan impact report details the bandwidth utilization for all link and path trail levels of the network before the plan has been run, after the plan has been run, and after the trail resources have been consumed.

The network plan impact report sub-views define the plan in terms of the following reports:

  • Network impact trail summary

  • Network impact equipment summary

  • Network trail impact

  • Network equipment impact

  • Network site impact.

Note:

The impact reports are generated only if you have accepted solutions in the Service Demand Summary view.

About the Network Impact Trail Summary Report

The network impact trail summary report provides a summary of all trails consumed grouped by service and capacity, and lists the available capacity before and after the forecast (all values are in Mbps). Table 7-6 lists the report details:

Table 7-6 Network Impact Trail Summary

Column Name Description

Service

The name of the service.

Trail Capacity

The capacity of the trail.

Trail Definition

The name of the trail definition associated with the trail.

Total Capacity (Mbps)

The capacity of all trails of this service, and of this capacity.

Used Capacity Pre (Mbps)

The amount of capacity that was used for all the trails before the forecast run.

% Utilization Pre

The percentage utilization of all trails before the forecast was run.

Take Up (Mbps)

The amount of bandwidth consumed by the forecast run.

% Change

The percentage change in bandwidth usage between post and pre forecast run.

% Utilization Post

The percentage utilization after the forecast was run.


About the Network Impact Equipment Summary Report

The network impact equipment summary report provides a summary of all equipment nodes consumed by the forecast run, grouped by platform, type, and entity. Table 7-7 lists the report details:

Table 7-7 Network Equipment Impact Summary

Column Name Description

Platform

The name of the equipment platform family.

Type

The platform type.

Equipment Definition

The name of the equipment definition associated with the equipment.

Port Definition

The name of the port definition associated with the port.

Total

The percentage utilization of all the trails before the forecast was run.

Free Total Pre

The total number of ports of the stated capacity that were free before the forecast run.

Free Total Post

The total number of ports of the stated capacity that are free after the forecast run.

Take Up

The number of ports of the stated capacity consumed by the forecast.

% Used Pre

The percentage of ports of the stated capacity that were used before the forecast run.

% Used Post

The percentage of ports of the stated capacity that are used after the forecast run.


About the Network Trail Impact Report

The network trail impact report gives you a summary of all trail capacity nodes consumed by the forecast run, but listed for each individual trail. Table 7-8 lists the report details:

Table 7-8 Network Trail Impact

Column Name Description

Trail

The name of the trail.

Trail Definition

The name of the trail definition associated with the trail.

Trail Capacity

The capacity of the trail.

A Node

The start termination equipment node name.

Z Node

The end termination equipment node name.

Take Up

The amount of bandwidth consumed on the trail by the forecast run.

% Before

The percentage utilization of the trail's capacity before the forecast run.

% After

The percentage utilization of the trail's capacity after the forecast run.

Full

Yes: if the trail's capacity is now fully consumed.

No: if the trail's capacity is not fully consumed.

Exhaustion Date

The predicted exhaustion date, as calculated by Network Intelligence.


About the Network Equipment Impact Report

The network equipment impact report gives you a detailed list of all equipment nodes consumed by the forecast run. Table 7-9 lists the report details:

Table 7-9 Network Equipment Impact

Column Name Description

Site

The name of the site that the equipment node resides in.

Site Address

The address of the site.

Node

The equipment full name.

Node Definition

The port capacity that you are reporting on.

Slots Full

Yes: if all of the node backplane capacity is consumed after the forecast run.

No: if some node backplane capacity remains after the forecast run.

Cards Full

Yes: if all of the nodes access or drop capacity is consumed after the forecast run.

No: if all of the nodes access or drop capacity is not consumed after the forecast run.

Exhaustion Date

The predicted exhaustion date of this equipment node for the stated port capacity, as calculated by Network Intelligence.

Port Definition

The port definition associated with the port.

Free Total Pre

The total number of ports of the stated capacity that were used before the forecast run.

Free Total Post

The total number of ports of the stated capacity that are used after the forecast run.

Take Up

The number of ports consumed for the stated capacity for this forecast run.


About the Network Site Impact Report

The network site impact report gives you a list of all ports consumed by the forecast run, broken down per site per capacity. Table 7-10 lists the report details:

Table 7-10 Network Site Impact

Column Name Description

Site

The name of the site that the ports reside in.

Site Address

The address of the site.

Port Definition

The port definition associated with the port.

Free Total Pre

The total number of ports of the stated capacity that were used before the forecast run.

Free Total Post

The total number of ports of the stated capacity that are used after the forecast run.

Take Up

The number of ports consumed for the stated capacity for this forecast run.

Exhaustion Date

The predicted exhaustion date of this equipment node for the stated port capacity, as calculated by Network Intelligence.


About the Cost Estimation Reports

If you create a planned entity within a plan (using the plan maintenance manager), all the tasks (and related costs) associated with this new planned entity are included in the cost report each time the plan routing manager is run.

You can create the following entities within a plan:

  • Site

  • Equipment

  • Trail

  • Topology.

The Cost Estimation report details the estimated cost of carrying out the network build to satisfy the plan network demand.

The Cost Estimation report sub-views define the plan in terms of:

The summary provides a list of associated costs, defined in terms of:

  • Capital expenditure

  • Operating expenditure

  • Network expenditure

  • Total expenditure.

Routing Solution Acceptance Costs

These costs are the cost of using successful routing solutions. When a route solution is accepted the system finds any tasks that are associated with the route solution elements comprising the accepted solutions. The tasks and their associated costs are displayed in the cost estimation report.

Viewing Task Details

The task details view gives you a summary list of all of the tasks, with their costs, that are required to realize the build plan. If you do not define any tasks or costs, this view is empty.

Viewing Equipment Cost Details

The equipment cost details view summarizes the cost of any new equipment node builds that are required for the plan.

Viewing Labor Cost Details

The labor cost details view summarizes the build cost in terms of labor tasks, and is ordered by labor type and labor grade. Labor tasks and related costs are usually recorded as an Opex expenditure.

Viewing Trail Cost Details

The trail cost details view summarizes the costs by listing all the tasks, by quantity, for all tasks that are trail build related. This includes unit timeslot build costs, if defined.

Viewing Cost by Service Details

The cost by service details view is another trail cost summary view that summarizes all the trail build costs, broken down by service type. This is useful to see how much each service type costs, as part of the overall plan cost.

Viewing Planned Entity Cost Details

The Planned Entity Cost Details view displays the costs of entities (topology, site, equipment, trail, card) that are planned to be built.

Table 7-11 lists the Planned Entity Cost Details view attributes:

Table 7-11 Planned Entity Cost Details View Attributes

Attribute Description

Entity Name

The name of the planned entity.

Entity Type

The type of the entity (topology, site, equipment, trail, card).

In Service Date

The In Service Date of the entity.

Status

The status of the entity.

Expenditure Type

The expenditure type of the costs associated with the entity:

  • OpEx (operating expenditure)

  • CapEx (capital expenditure)

  • NetEx (network expenditure).

Total

The total cost for each line item.


Viewing OLO Cost Details

Network Intelligence enables trails provided by other licensed operators (OLO) to be modeled. These trails are normally used by a company to provide transmission coverage in areas where a company does not have any network. These trails have a leased cost associated with them, which is recorded as a monthly recurring cost.

The data loader process loads these costs into Network Intelligence from an outside source, and associates the cost with each leased trail. If you subsequently use these trails to path services in a forecast plan, the cost of each service consumption on the leased trails is listed in the cost summary report.

About Saving Plan Run Results

To save a plan, click Save Report, and enter a name for the report. Each report must use a unique name. If you create a report using a name that is already in use, a warning dialog box is displayed.

When a plan routing run is saved, all of the routing results are saved. This includes the status of a routing result (whether the result has been accepted.) All of the resources that each routing result consumes are also saved. You can easily reload a report at any time, and perform further plan routing with subsequent routing runs.

Note:

It may take a few moments for a plan routing run to save as a report, or reload as a report. The time taken depends on the number of service demands contained in the plan routing run.

About Rerunning a Plan Run

You can rerun a plan run at any time. For example, you might create a plan and route it for a particular period. You inspect the initial routing results, and accept service demand route solutions. For other service demands, you may make changes to the service policies to change the routing offered, or for failures, may alter the policy to look for a routing solution on a rerun.

Suggested trails, cards, or equipment may be built, or new topologies or sites planned, and the plan rerun.

After each rerun, you can save the plan run as a report. After some iterations, during which changes were made, the plan is satisfactory. This normally occurs when the overall plan routing success percentage is sufficiently high. In certain cases, it may be 100 percent, which means that all of the service demands must be successfully routed.

About Analyzing the Routing Solution and Result

A loaded report or a finished routing run can be rerun as many times as required. The most important view for routing solution analysis is the routing results view, which contains a list of all of the service demands that required routing.

The routing results view displays the success or failure status of each service demand, and whether the service demand result has been accepted. The popup menu associated with this view displays the options shown in Table 7-12.

Table 7-12 Options Associated with the Routing Solution

Plan attribute Description

Accept All Solutions

The accept all solutions option changes the status of all successful solutions to accepted; they are not routed on subsequent reruns. After a solution has been accepted, its entry is displayed with a green colored background rather than a white colored background. The network resources used by this service demand result's routing solutions are not available for other service demands in subsequent reruns.

Accept Selected Solutions

Select a service demand result to accept by clicking it. Use the Ctrl key to make multiple selections. The accept selected solutions option accepts each selected solution in the same way as in the Accept all Solutions option.

Reject All Solutions

All accepted solutions are rejected. On a subsequent rerun, all of these service demands are sent to Trail Routing Manager for routing. All resources consumed by the service demand result are released, and are available to Trail Routing Manager when looking for routing solutions.

Reject Selected Solutions

All selected solutions are rejected. On a subsequent rerun, all of these service demands are sent to Trail Routing Manager for routing. All resources consumed by the service demand result are released, and are available to Trail Routing Manager when looking for routing solutions.

Accept All Partial Solutions

All partial solutions are accepted; on subsequent reruns, only the outstan.ding total of the partial route is attempted.

Accept Selected Partial Solutions

Click a route to select it, or use the Ctrl key to select multiple routes. Select accept selected partial solutions to accept any selected routes.

Reject All Partial Solutions

All accepted partial solutions are rejected. On a subsequent rerun, all routes must be routed.

Reject Selected Partial Solutions

All selected partial solutions are rejected. On a subsequent rerun, these routes must be routed for the full total.

Edit Selected Route

Enables you to edit the route.

View Selected Service Demand Service Policy

The Edit option enables you to edit the policy for the service demand associated with this routing result.

If service demand results are selected, then only these routes are routed on a rerun. If no service demands are selected, all non-accepted and outstanding partials and failures are routed.

To rerun the report, click Route on the report window.

Save as HTML

Save the view in an HTML file.

Save as CSV

Save the view in a comma separated file.

Copy to Clipboard

Save the plan for pasting it elsewhere.

Open in Excel

Save the plan as a user defined Microsoft Excel file, and display it directly in Microsoft Excel.


About Publishing a Plan

When you are finished working on the plan, you may publish it. To publish a plan, export the various views into Microsoft Excel for circulation in a single workbook.