3 Management Functional Areas
Last update PvD

3.8 MFA versus LLA

Relation between Management Functional Areas and Logical Layered Architecture

Overview

1. Introduction
2. FM
3. CM
4. AM
5. PM
6. SM
7. Process Cycles

Introduction

The Logical Layered Architecture defines the information hierarchy, i.e. stacked horizontal layers.  The Management Functional Areas defines functions independent of these layers, i.e. orthogonal to it, or vertical.

It seems natural to identify subfunctions at the intersections in the matrix of horizontal layers and vertical management areas.  However, subfunctions of the Functional Management Areas in general do not map exactly to one particular layer; they are often between layers or comprise multiple layers.

Example:  Fault Management includes a function 'fault correlation' (i.e. conclude that multiple fault reports are caused by the same fault).  This function however will exist at EML (correlate faults within a NE), at NML (correlate faults between NEs), and at SML (Trouble Management).

Also, the Management Functional Areas are not autonomous and have considerable overlap.  For example SLA management (PM) requires performance data for individual users, which overlaps the billing data (AM) for that user.  AM should keep track of resource costs, which overlaps PM data for usage.

Some map can be created, but as most functions cross layers it is not a true matrix.
The tables below have a column for each layer of the Logical Layered Architecture, plus an area between the layers to reflect overlap.  You will find subfunctions of each Management Functional Area positioned in or between the layers.

FM

CM

AM

PM

SM

Process Cycles

Most processes in network management are part of a cycle, i.e. an activity is not stand-alone but part of an set of interconnected processes and executed cyclically.

OSSes are to support business processes.  There is not necessarily a one-to-one mapping of a business process to an OSS:

• multiple business processes may use the same OSS;
  the OSS may be less suited for a particular process.
• a business process may use multiple OSSes;
  in this case there is an integration issue.

The following processes are described as a cyclic sequence of steps:

• Equipment life-cycle (CM)
• Service life-cycle (CM)
• Fault life-cycle (FM)
• Capacity Management cycle (PM)

Next section: Summary
Up to Contents
Up to Index

=O=