3 Management Functional Areas
Last update
PvD
3.3 CM
Configuration Management
Overview
- Standard
- Provisioning
- Equipment management
- Service management
Standard
[M.3400]: Configuration Management (CM) provides functions to exercise control over, identify, collect data from and provide data to NEs.
- NE Installation {support}
The TMN can support the installation of equipment which makes up the telecommunication network. It covers also the extension or reduction of a system. Some NEs call for the initial exchange of data between themselves and the TMN. An example of another function is the installation of programs into NEs from database systems within the TMN. In addition, administrative data can be exchanged between NEs and the TMN.
- Provisioning
Provisioning consists of procedures which are necessary to bring an equipment into service, not including installation. Once the unit is ready for service, the supporting programs are initialized via the TMN. The state of the unit, e.g. in-service, out-of-service, stand-by, reserved, and selected parameters may also be controlled by provisioning functions. It includes:
- NE Configuration
- NE Administrative functions
- NE Database management
- NE Status and Control
The TMN provides the capability to monitor and control certain aspects of the NE on demand. Examples include checking or changing the service state of a NE or one of its sub-parts (in-service, out-of-service, stand-by) and initiating diagnostic tests within the NE. Normally, a status check is provided in conjunction with each control function in order to verify that the resulting action has taken place. When associated with failure conditions, these functions are corrective in nature (e.g. service restoral).
Status and control functions can also be part of routine maintenance when executed automatically or on a scheduled periodic basis. An example is switching a channel out-of-service in order to perform routine diagnostic tests.
A TMN will enable the exclusion of faulty equipment from operation and as a result it may rearrange or re-route traffic. A TMN can enable the entry of a proposed configuration in order to automatically analyze the feasibility of that design before implementing it. It includes:
- Generic NE status and control functions
- Message handling systems network status
- Leased circuit network status
- Transmission network status
So Configuration Management includes all day-to-day functions to operate the network, and that requires to keep inventory:
- Equipment management
- Service management
We return to above points later.
Provisioning
The term 'Provisioning' has a particular and rather restrictive meaning in the standard:
[M.3400] Provisioning consists of procedures which are necessary to bring an equipment into service not including installation.
So, provisioning is only configuring the hardware and software.
Note:
- 'support for installation' is a separate subject in CM;
- 'service provisioning' is not mentioned at all.
In this document the term 'provisioning' is applied in the more commonly used sense:
- it may imply physical work on equipment when suitable equipment is not available (e.g. cable installation, board installation and strapping so it is ready for service: Operational state = Enabled); and
- it is also used for service provisioning: allocate unused equipment and configure it (and potentially configure the TMN) such that it can be used by a customer (fill-in user profile and unlock: Administrative state = Unlocked).
Note that 'service creation' is not 'provisioning'; service creation is introducing a new service, and service provisioning is enabling an existing service for a new user.
Equipment management
This is directed to the equipment in the network, and includes inventory control (not spares and stock but more what is in the field), equipment ordering & provisioning, installation support, (software & data) loading, activation, modification of operation, shut-down for maintenance, replacing, de-installation, and finally scrapping.
Note that inventory control includes several layers of abstraction, i.e. not only boards, but also the racks, nodes, trunk groups, etc.
This is the area for Work Orders: Orders for field engineers to install/modify/de-install equipment or to perform (preventive/corrective) maintenance on equipment.
Service management
This is directed towards users, and includes service inventory control, service provisioning, service activation, attribute modification, cessation of service.
Here also there are several levels (e.g. a special switched service may require a leased line for access).
This is the area for Service Orders: Orders to activate/modify/de-activate a service for a user (hopefully only data manipulation, so it can be automated).
If suitable equipment is not available for service provisioning, it will lead to Work Orders.
Obviously there is a relationship between service and equipment; the service is provided through the equipment. However, this relationship is not straightforward at all; it depends on the type of service and the vendor's implementation in equipment.
This relationship is required for various reasons; some examples:
- It must be possible to identify (semi-permanent) services/users using a particular function/equipment (i.e. map the equipment to supported users). This can be used to identify consequences (impacted users) after a fault or for a planned action e.g. to investigate what happens when equipment is shut-down (i.e. for maintenance or upgrade).
- The reverse –what functions/equipment are used for a particular service/user– is also required, for example for diagnostic purposes (e.g. to solve customer complaints).
- Similarly, in order to apply service provisioning, there must be a mapping of the customer's topological address to geographically nearby equipment (then look for unused equipment, if not available issue an installation Work Order).
Further references:
=O=