Skip Headers
Oracle® Communications Network Intelligence User's Guide
Release 7.2.2

E36059-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

14 Forecasting Service Demands

This section describes Forecast Manager in Oracle Communications Network Intelligence. Forecast Manager allows planning engineers to perform accurate service demand forecasting. A forecast is defined as a collection of service demands with expected future trail growth counts for one, or more, future time periods.

The result is then converted to individual network point-to-point service demands, each of which consists of a route object with 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.

Using the Plans Tree Browser

The Plans tree browser is made up of a series of folders, each of which contains all service projects, that is, plans, currently in Network Intelligence: forecast plans, migration plans, outage plans, or configuration plans. Figure 14-1 shows the Plans tree browser.

Figure 14-1 Plans Tree Browser

Plans Tree Browser

Double-click any tree browser folder to expand the selection. Double-click any plan object to open the plan view; for example: to display a forecast plan and its sub-views, double-click the forecast object in the tree browser within the forecast sub-folder.

The Plans tree browser is split into two separate folders:

  • My Plans

  • Other Plans

Using the My Plans Folder

The My Plans folder consists of all service projects within Network Intelligence created by the current user. These plans are always visible on a Network Intelligence GUI opened by this user.

These plans may, or may not be, shared with other users. When you create a plan, there is an option to set the Shared option to make this plan sharable (and visible) to other users. If a plan is not shared, it is not visible to other users in the Plans tree browser.

Using the Other Plans Folder

The Other Plans folder consists of all service projects within Network Intelligence created by other users. These plans are visible on a Network Intelligence GUI opened by this user (that is, the owner of the My Plans folder) if they have been shared by the other users.

Related Topics

Using the My Plans Folder

Creating a Plan

The plan creation manager uses a wizard to enable you to create new plans in different ways. The steps taken depend on the creation method chosen.

Note:

Migration and outage plans are created using the migration and outage managers respectively. See "Migrating Network Entities" and "Managing Outages"

To create a plan

  1. Click Plans on the context toolbar.

  2. Click the Create icon to display the plan creation manager wizard.

  3. Choose which type of plan to create:

Creating a Plan By Selecting Routes

To create a plan by selecting a route object using the route filter, and applying plan values to future periods, perform the following steps:

  1. Select Create Plan by Selecting Routes in the plan creation manager window.

  2. Complete the details of the plan, such as the name and planning type. See "Using the Plan Details View" for definitions of the fields.

  3. Use the Route Filter to select routes for the new plan.

    1. Click Select From Routes to display the Route Search window.

    2. Select any required filter criteria, and click Search. For example, select the required customer and capacity to display all routes of that type.

    3. Select the required routes by clicking the rows associated with them, and click Select to display the routes.

    4. Click Next to select the start dates and end dates for the plan and the period type.

  4. Enter the start dates and end dates for the plan, and the period type. The period type is measured in months, quarters, or years.

    When the number of periods field is filled, the end date is automatically completed.

  5. Fill in the service demand values for the future plan dates. Click Next to save the plan.

  6. Select one of the following options:

    • Save and Display Plan.

    • Save and Close Plan

  7. Click Finish to complete the plan.

Creating a Plan by Selecting Network Objects and Applying Growth Criteria

To create plan scenarios by selecting any network object in the tree browser, perform the following steps:

  1. Select Create Forecast by Selecting Network Objects and Applying Growth Criteria in the plan creation manager window.

    The following network entities may be selected for this type of plan creation:

    • Topology

    • Equipment

    • Site

    • Trail

    • Service

    • Route

    • Customer

  2. Select the required entities:

    1. To display the required network inventory data, use the context toolbar to select which type of data you want to see; for example, trails or equipment.

    2. Drag and drop the entities to the plan creation manager. To remove an object, right-click it and select Remove.

  3. Click Next to select the trails that are in scope for the growth study. To select all trails in the table, select the Select All check box.

    Because you may not want to select all trails from the network entities selected, sort the table as required, and select the required trails. Enter the plan growth as a percentage in the format specified. See Figure 14-2.

    Figure 14-2 Creating a Plan by Selecting Trails in Scope for Growth Study

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

  4. Complete the details of the plan, such as the name and planning type. See "Using the Plan Details View" for definitions of the fields. Click Next to select the start dates and end dates for the plan and the period type.

  5. Enter the start dates and end dates for the plan and the period type. The period type is measured in months, quarters, or years.

    When the number of periods field is filled, the end date is automatically completed. Click Next to display the service demand values.

  6. Complete the service demand values for the future plan dates. Click Next to save the plan.

  7. Select one of the following options:

    • Save and Display Plan

    • Save and Close Plan

  8. Click Finish to complete the plan.

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-delimited file format, generated using Microsoft Excel, for example. Network Intelligence currently supports two data types as inputs for plan generation:

Using Service Demands

A plan containing a set of service demand objects can be created by importing a spreadsheet containing service demand line entries. The file must be a CSV file format, generated using Microsoft Excel, for example.

Figure 14-3 shows a sample file:

Figure 14-3 Creating a Plan from an External File Source

Description of Figure 14-3 follows
Description of "Figure 14-3 Creating a Plan from an External File Source"

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

Table 14-1 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 service 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 and if entered can be any string value.

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

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

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

  • A Site and Z Site are mandatory, and must exist in Network Intelligence as site objects 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 objects with the same name specified in the file.

If the validation fails, a data error is displayed.

Understanding Data Errors

Table 14-2 lists the possible data errors if validation of the external file source fails.

Table 14-2 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

One or more 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 object 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 by Importing Service Demands

To create a plan by importing service demands, perform the following steps:

  1. Select Create Plan From An External File Source in the plan creation manager window.

  2. Click Next to select the file type to be used as the data input for the plan.

  3. Select the file type for the plan. Click Create a plan from a Route A-Z spreadsheet file, and browse to the location of the file.

  4. Click Next to load and validate the service demand input file.

  5. Complete the plan attributes. Setting the Shared option makes this plan sharable to others. If a plan is not shared, it is not visible to other users in the Plans tree browser.

  6. View the plan service demands. This step enables you to inspect the plan service demands before the plan is saved.

  7. Select one of the following options:

    • Save and Display Plan.

    • Save and Close Plan.

  8. The plan is displayed in the Network Intelligence GUI as shown in Figure 14-4.

    Figure 14-4 Creating a Plan by Importing Service Demands

    Description of Figure 14-4 follows
    Description of "Figure 14-4 Creating a Plan by Importing Service Demands"

Using Bulk Service-Bandwidth Input Files

The bulk service demands are defined in CSV format, typically using Microsoft Excel. Figure 14-5 shows a sample CSV file.

Figure 14-5 Creating a Plan Using Bulk Service-Bandwidth Input Files

Description of Figure 14-5 follows
Description of "Figure 14-5 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.

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 "Using Service Demands".

Creating a Plan by Importing Bulk Service Bandwidths

To create a plan by importing bulk service bandwidths, perform the following steps:

  1. Select Create Plan From An External File Source in the plan creation manager window.

  2. Click Next to select the file type to be used as the data input for the plan.

  3. Select the file type for the plan. Click Create a plan from a Bulk Service-Bandwidth spreadsheet file, and browse to the location of the file.

  4. Click Next to load the bulk data. Network Intelligence derives the required service demands. It does this by finding the full set of route objects that exist for the referenced service objects in the bulk import file.

    Each route object has a monthly growth value in bandwidth units (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.

  5. Complete the plan attributes. Setting the Shared option makes this plan sharable to others. If a plan is not shared, it is not visible to other users in the Plans tree browser.

  6. View the plan service demands. This step enables you to inspect the plan routing service before the plan is saved.

  7. Select one of the following options:

    • Save and Display Plan.

    • Save and Close Plan.

For further information about plan object views, see Network Intelligence Concepts.

Working with Plan Object Views

The plan object offers the following views:

  • Service Demands

  • Studies

  • Planned Entities

  • Planned Trails

  • Planned Equipment

  • Planned Cards

  • Planned Sites

  • Planned Topologies

Using the Plan Details View

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

Each plan has the attributes outlined in Table 14-3.

Table 14-3 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.


Using 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.

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 14-4.

Table 14-4 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 object to allow you to change the service policy of the route object.

View selected service demand policy

View the service demand's service 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 one or more 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.


Using the Studies View

Each time a plan is routed it may be saved with the route solutions as a plan report. The studies view displays a list of plan reports for the selected plan.

Double-click the report in the list to select it.

Comparing Forecast Reports

To compare forecast reports:

  1. From the Studies view, select two, or more, reports.

  2. Right-click the reports, and select Forecast Comparison Report.

  3. Select one of the tabs to compare the route solutions:

    • Click the Summary tab to view the relative numbers of route demands, paths, and circuits, and the relative success rates for services and customers.

    • Click the Impact Summary tab to view the tasks resulting from the routing forecast; for example: a suggested circuit route build.

Using 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.

Using 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.

Using the Planned Equipment View

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

Note:

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

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

Using the Planned Cards View

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

Table 14-5 outlines the attributes for cards.

Table 14-5 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.

Using 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.

Using 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.

Editing Plans

After a plan has been created, it can be edited or maintained. The plan maintenance manager enables changes to the plan set of service demands, such as extending the plan future periods, or archiving historic periods.

You can also edit values in an existing plan.

To edit a plan:

  1. Select the plan to be edited from the Plans tree browser.

  2. Select the service demands view.

  3. When the view is displayed, right-click it to invoke a popup menu. The Edit Mode option switches on the edit mode.

    In edit mode, the following fields can be edited:

    • Any plan demand total for a future date period.

    • The demand order number.

    • Priority.

Any fields that cannot be edited are displayed with a light gray foreground color.

Any fields that have been edited are displayed with a yellow background color until saved. Edits are not saved until Save Changes is selected. To revert without saving, close the plan view.

Maintaining Plans

Plan maintenance involves performing several tasks on a plan using the plan maintenance manager.

Carrying Out Plan Date Tasks

There are three tasks associated with plan dates:

  • Extending a plan

  • Truncating a plan

  • Archiving a plan

Extending a Plan

Extending a plan means adding extra time periods to the plan, with extra service demand values.

To extend a plan:

  1. Select the plan from the Plans tree browser.

  2. Select the service demands list view.

  3. Right-click the list to invoke the popup menu.

  4. Select Maintain to display the plan maintenance manager.

  5. Click the Date Tasks tab.

  6. Select Extend Plan, and click Next to display the extend plan window.

  7. Extend the plan. The new end date is calculated automatically.

    Select whether to populate new entries with current end date values by selecting, or deselecting, the check box.

  8. Click Finish to complete the plan.

Truncating a Plan

Truncating a plan means removing future time periods from the plan, with their service demand values. Only future plan periods can be truncated from the plan.

To truncate a plan:

  1. Select the plan from the Plans tree browser.

  2. Select the service demands list view.

  3. Right-click the list to invoke the popup menu.

  4. Select Maintain to display the plan maintenance manager.

  5. Click the Date Tasks tab.

  6. Select Truncate Plan to display the truncate plan window.

  7. Shorten the plan by a selecting a new end date.

  8. Click Finish to complete the plan.

Archiving a Plan

Archiving a plan means removing past time periods from the plan, with their service demand values.

To archive a plan:

  1. Select the plan from the Plans tree browser.

  2. Select the plan's service demands list view.

  3. Right-click the list to invoke the popup menu.

  4. Select Maintain to display the plan maintenance manager.

  5. Click the Date Tasks tab.

  6. Select Archive Plan to display the archive plan window.

  7. Archive the plan up to a past date.

  8. Click Finish to complete the plan.

Cloning a Plan

Cloning a plan means creating an exact copy of an existing plan. Only the plan details and the service demand list entities are copied. Any reports or editing details are not copied in a clone task.

To clone a plan:

  1. Select the plan from the Plans tree browser.

  2. Select the service demands list view.

  3. Right-click the list to invoke the popup menu.

  4. Select Maintain to display the plan maintenance manager.

  5. Click the Copy/Delete Tasks tab.

  6. Select Clone Plan to display the clone plan window.

  7. Enter the name of the new cloned plan.

  8. Click Finish to complete the plan.

Deleting a Plan

Deleting a plan means deleting the plan object and all related entities associated with the plan. This includes:

  • Plan service demands

  • Plan routing run reports

  • Planned entities associated with the plan

  • Editing history

  • Red line conditions

To delete a plan:

  1. Select the plan from the Plans tree browser.

  2. Select the service demands list view.

  3. Right-click the list to invoke the popup menu.

  4. Select Maintain to display the plan maintenance manager.

  5. Click the Copy/Delete Tasks tab.

  6. Select Delete Plan.

  7. Click Finish to complete the deletion.

  8. Confirm the deletion.

    Note:

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

Adding Routes to a Plan

A plan may have routes (service demands) added to it after the plan has been created. You may have forgotten to include service demands on creation, or the plan may have changed, necessitating additional service demand requirements.

To add routes to a plan:

  1. Select the plan from the Plans tree browser.

  2. Select the service demands list view.

  3. Right-click the list to invoke the popup menu.

  4. Select Maintain to display the plan maintenance manager.

  5. Click the Route Tasks tab.

  6. Click Add Routes.

  7. Click Select Routes and select the routes required.

  8. Click Finish to complete the route addition which creates new service demands.

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 ”redline” colors to check the following:

  • 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.

To set up redline tolerance values for a plan:

  1. Select the plan from the Plans tree browser.

  2. Select the service demands list view.

  3. Right-click the list to invoke the popup menu.

  4. Select Maintain to display the plan maintenance manager.

  5. Click the Tracking Tasks tab.

  6. Click Configure Redline Colors to display the Configure Redline Colors window.

  7. Configure the colors for both the Forecast-Planned and Planned-Live tabs.

    Set the colors for both the upper threshold and lower threshold in each case.

  8. Click Finish to complete the configuration.

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 (that is, 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 one or more 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 one or more 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.

Applying a Growth Scenario

To apply a growth scenario to a plan:

  1. Select the plan from the Plans tree browser.

  2. Select the service demands list view.

  3. Right-click the list to invoke the popup menu.

  4. Select Maintain to display the plan maintenance manager.

  5. Click the Growth Scenario tab.

  6. Select the plan type group object to apply the growth criteria to.

  7. Enter the growth criteria values against the select forecast group entities.

    Click Next.

  8. Select the period range that the growth criteria is applied against. If the growth criteria is for one period only, then the start and end dates should be equal.

    Click Next.

  9. Click Finish to complete the configuration.

Carrying out Plan Tasks

Use the plan maintenance manager to plan network entities that are associated with a plan. The following new network entities may be planned within a forecast:

  • Trail

  • Equipment

  • Site

  • Topology

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

To plan a new network object within a plan:

  1. Select the plan from the Plans tree browser.

  2. Select the service demands list view.

  3. Right-click the list to invoke the popup menu.

  4. Select Maintain to display the plan maintenance manager.

  5. Click the Plan Tasks tab.

  6. Select the object type:

  7. Follow the object creation steps.

  8. Click Finish to complete the configuration.

Planning a New Site

To plan a new site, follow the steps in "Carrying out Plan Tasks".

  1. Select the object type:

    • Plan new site

  2. Complete the details of the site object:

  3. Click Finish to complete the configuration.

Planning a New Topology

To plan a new topology, follow the steps in "Carrying out Plan Tasks".

  1. Select the object type:

    • Plan new topology

  2. Complete the details of the topology object.

  3. Click Finish to complete the configuration.

Using 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 display the plan routing manager window:

  1. Select and display the plan that is of interest.

  2. Select the service demands view.

  3. Select one or more service demands for routing.

    To select all service demands, click Select All.

  4. Click Analyze this Plan.

  5. The plan routing manager window is displayed. See "Analyzing Service Demands from a Plan".

Analyzing Service Demands from a Plan

To analyze a selection of service demands from a plan:

  1. Select the plan period and service demands that are in scope. Select the future period of the plan that is of interest 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, that is, no existing route trail total is deducted.

  2. 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.

  3. 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.

  4. 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:

Using 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.

Using 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.

Using 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 one or more 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.

Using 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 object types:

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.

Using 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 network 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.

Using 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 14-6 lists the report details:

Table 14-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.


Using 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 14-7 lists the report details:

Table 14-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.


Using 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 14-8 lists the report details:

Table 14-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.


Using 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 14-9 lists the report details:

Table 14-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.


Using 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 14-10 lists the report details:

Table 14-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.


Using the Cost Estimation Reports

If you create a planned object within a plan (using the plan maintenance manager), all the tasks (and related costs) associated with this new planned object 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 14-11 lists the he Planned Entity Cost Details View attributes.

Table 14-11 Planned Entity Cost Details View Attributes

Attribute Description

Entity Name

The name of the planned object.

Entity Type

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

In Service Date

The In Service Date of the object.

Status

The status of the object.

Expenditure Type

The expenditure type of the costs associated with the object:

  • 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.

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 name that is 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, that is, 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.

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 service 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.

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 14-12.

Table 14-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 service policy for the service demand that is associated with this routing result.

f one or more 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-delimited 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.


Publishing a Plan

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