Skip Headers
Oracle® Communications Network Intelligence Concepts
Release 7.2.2

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

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

9 Managing Network Outages

This chapter describes how to use Oracle Communications Network Intelligence to manage network outages.

About Managing Network Outages

You can use Network Intelligence to report affected inventory systems during a planned, or unplanned, network outage. You can also determine the outage impact on customers, sites, trails, equipment, services, cards, and other entities.

For example, if there is a planned outage for some part of your network, such as the replacement of an underground cable supplying customer broadband services, you can generate an outage report to find out which sites, equipment, customers, and services are disrupted, and the ways in which they are impacted. The information in the outage reports can also help you restore the network by generating a set of service demands to suggest restoration paths for impacted services. You can also notify a list of contacts in affected customer accounts.

Outages can be tracked by date and duration for summary reporting, and this information can be saved (for example, in tracking a service level agreement). You can control customer email notification by filtering the list of contacts at a client company.

Generating an Outage Report

To generate an outage report, complete the report details, such as the name and outage type. Select the outage resources associated with a planned outage and view the impacted entities:

  • Customers

  • Services

  • Equipment

  • Sites

  • Trails for notification

Select customer contacts to be notified of the outage by email, and save the outage plan.

About Outage Plans

The outage plan details view shown in Table 9-1 displays the primary attributes of the outage plan.

Table 9-1 Outage Plan Attributes

Plan attribute Description


The name of the planned outage. All plans must be unique.

Outage Owner

The person who generates the outage report.

Start Date

The time and date on which the outage starts.

End Date Time

The time and date on which the outage ends.


Further description of the outage (for example, a reference number known by the customer, or order management system).

Selecting Outage Resources

You use Outage Report Manager to select the entities to be associated with an outage plan. Define the outage resources by:

  • Selecting the entity type

  • Adding entities of that type

You can create a plan with multiple entities, and with entities of different types (for example, site and equipment). The supported entity types are:

  • Card

  • Customer

  • Equipment

  • Resource Group

  • Route

  • Service

  • Site

  • Topology

  • Trail


    If you use Outage Report Manager to search for trails, the search returns not only children of the trail, but where the selected trail is a protecting trail, the search also returns children of the protected trail.

Adding Entities to the Outage Plan

Search for all entities of a particular type to add to the outage plan resources. For example, you can add a resource group containing a collection of associated network elements, specify a particular customer, or select an affected site (and all of its associated trails, which are retrieved automatically).

In general, there are three options for selecting entities for an outage plan:

  • Manually select individual entities: This ad-hoc approach is generally favored when the outage affects a small number of entities.

  • Use a resource group, which is a defined list of entities generally used repeatedly for outage analysis.

  • Load entities from a spreadsheet (in a similar manner to the resource group), but where this list of entities is generally not used elsewhere, so there is no requirement for the overhead of creating a resource group.

Importing Entities into the Outage Plan

You can select a file of comma separated variable (CSV) format containing the entities in a resource group to be associated with the outage. The file must be defined by columns called Entity Type and Entity Name.

So, for example, consider a situation where a very large number of entities is associated with an outage (for example, cards on an equipment). Importing the cards in bulk using a resource group is easier than adding each card singly by typing in the entity names.

Entity names are persisted in the outage report, but otherwise the grouping is not retained.

This mechanism is similar to that used to load service demands in Forecast Manager. See "Creating a Plan Using Service Demands".

About Impacted Entities

You generate an outage report to identify the network elements affected by a planned, or unplanned, outage.

Affected network elements include:

  • Trails

  • Equipment

  • Customers

  • Services

  • Sites

Viewing Impacted Entities

You can view affected entities by clicking a tabbed pane on the impacted entities report.

  • Affected nodes are defined by name, number of impacted trails, site, customer, and so on.

  • Affected customers are listed by name, type, and number of impacted entities per customer.

  • Affected services are listed by name, trail capacity, and number of impacted trails per service.

  • Affected locations are listed by name, number of impacted trails per location, address, and parent location.

  • Affected sites are listed by name, number of impacted trails per site, address, geographical coordinates, site type, and so on.

About Customer Contacts

You can select customer contacts to be notified of the outage by email. If no contacts are selected, no emails are sent. You can modify the subject title, or add more detail about the outage mail to the contacts.

See "Defining Customer Contacts" for further information on contact configuration.

Defining Customer Contacts

You can add, edit, or delete contact details in Network Intelligence using the Administration menu.

See the Network Intelligence Help for further information about configuring customer contacts.

Viewing Outage Reports

An outage plan contains individual reports for all outage and impacted entities, planned entities, and a set of service demands to find restoration paths for impacted services. Outage plans are listed in the Outage subfolder of the Plans folder in the tree browser.

See "About Outage Reports" for more information about outage reports.