Abeer11020541002 Summer Internship Report

A PROJECT REPORT ON
OSS Analyst : Process automation for OMC-R reports and analysis of existing OSS systems
FOR
BHARAT SANCHAR NIGAM LTD., CHHATTISGARH CIRCLE

UNDER THE GUIDANCE OF MR. KISHORI RAM CGM, BSNL CHHATTISGARH MR. D.K GUPTA DGM, MOBILE DIVISION MR. SURAJ BAGHEL JTO, MOBILE DIVISION
TOWARDS PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE AWARD OF MASTER IN BUSINESS ADMINISTARTION IN TELECOM MANAGEMENT
SUBMITTED BY
ABEER VERMA
Symbiosis Institute of Telecom Management

Pune 412115 MBA TM I Batch 2011-13 Systems & Finance
<SITM CERTIFICATE>
Summer Project Report OSS Analyst : Process automation for OMC-R reports and analysis of existing OSS systems Symbiosis Institute of Telecom Management Constituent of Symbiosis International University
Bharat Sanchar Nigam Ltd. Chhattisgarh circle
-2-
<BSNL CERTIFICATE>
-3-
ACKNOWLEDGEMENT
It is said Seeing is believing. The 8 week summer internship as a part of curriculum at SITM lays a foundation for aspiring managers like us not only by imparting quality, world class education but also giving us an opportunity to get appropriate industry exposure before we take the actual step in.
I would like to thank respected Director Sir Mr. Sunil Patil, Dy. Director Sir Mr. Prasanna Kulkarni and all the faculty members of SITM for sharing their extensive knowledge and expertise to equip us with the knowledge and skills to take on the dynamism of corporate India.
The concepts imparted by them proved to be very helpful in delivering the assignments on time, thereby making the summer internship successful.
I would also like to express my sincere gratitude to Mr. Kishori Ram, GM, BSNL Chhattisgarh and Mr. D.K Gupta, DGM, BSNL Chhattisgarh (Mobile) for guiding me throughout the internship period and believing in my ability to deliver all the assigned deliverables.
ABEER VERMA
-4-
ABSTRACT
For successful operator business it is important to rapidly bring new services into the market, monitor and control their quality, timely and accurate process customer requests. To do this, advanced
telecommunications infrastructure and intelligent staff have to be accompanied by flexible and automated business processes. The level and depth of business process automation today is the determining factor of competitive advantage.
The set of telecom companies business processes, as well as classes of OSS systems, are determined in the materials of the international organization TM Forum, the worlds leading telecommunications
companies, manufacturers and solutions integrators organization. The materials from TM Forum are now recognized as methodological basis for the telecommunications industry.
BSNL is constantly working on the implementation of effective solutions in the field of OSS, allowing them to meet pressing development challenges of their business. Next generation OSS solutions helps operators to develop new sales channels, reduce costs for customer interaction through self-service tools, provide pass-through process automation connectivity services and technical support of the application to automatically configure the subscriber equipment. OSS includes integration of business
components, each of which focused on certain tasks in the enterprise.
The role of the intern involved analysis of reports generated by the OMCR/OSS servers and automate the post report generation process to use the raw data of OMC-R report to generate a more useful USO-BTS Fault Reports (henceforth abbreviated as BFR), analysis of BFR for further action
-5-
(to be taken by accounts department) and analysis of existing OSS systems and suggest possible areas of improvements for a more automated, real time alarm status monitoring/logging.
These
process
automation
and
report
analysis
provided
BSNL
Chhattisgarh various benefits which are discussed in details in the following chapters. Some of the major benefits were savings in payment remittances, automation processes leading to reduction in time to generate the BFR, real time and correct logging of BTS fault event time etc.
-6-
CONTENTS
1. Objectives 2. Executive Summary 3. Chapter-1 : Company Profile 4. Chapter- 2 : Product/Technology description 2.1 Introduction to OSS systems 2.2 Introduction to 9153 OMC-R product 2.3 OMC-R embedded in Network Management Environment 2.4 Overview of 9153 configuration 5. Chapter- 3 : Data analysis, interpretations & findings Assignment-1 3.1 Details of assignment 3.2 Methodology 3.3 Sample input/output 3.4 Findings 3.5 Limitations 6. Chapter- 4 : Data analysis, interpretations & findings Assignment-2 4.1 Details of assignment 4.2 Methodology 4.3 Sample input/output 4.4 Findings 4.5 Limitations 7. Chapter- 5 : Data analysis, interpretations & findings Assignment-3 5.1 Details of assignment 5.2 Methodology 5.3 Findings 65 66 67 72 55 56 59 61 63 64 45 46 48 51 53 54 29 31 12 13 14 21 22 26
-7-
8. Chapter- 6 : Conclusion 9. Chapter- 7 : Recommendations 10. Chapter- 8 : References
73 75 77
-8-
LIST OF FIGURES
Note: Figures in bracket indicate page numbers 1. FIG-1 : OMC-R FUNCTIONAL MANAGEMENT DOMAIN (27)
2. FIG-2 : OMC-R POSITIONING IN TMN (30)
3. FIG-3
ALCATEL
LUCENT
BSS
NETWORK
MANAGEMENT
ENVIRONMENT (30)
4. FIG-4 : 9153 OMC-R SINGLE CONFIGURATION OVERVIEW (31)
5. FIG-5 : 9153 OMC-R DISTRIBUTED CONFIGURATION OVERVIEW (32)
6. FIG-6 : OMC-R TO BSC CONNECTION VIA PSDN (39)
7. FIG-7 : OMC-R TO BSC CONNECTION WITH THE HELP OF COLOCATED SITE (39)
8. FIG-8 : OMC-R TO BSC CONNECTION VIA A INTERFACE - MSC CONNECTION (ALCATEL- LUCENT UNIVERSAL ROUTING) (40)
9. FIG-9 : ALARM CALL OUT OPTIONS (43)
10. FIG-10 : GENERATION OF BFR (50)
11. FIG-11: BHOD SECTOR WISE REPORT (ONE DAY REPORT) (51)
12. FIG-12: DAILY REPORTS AGGREGATED FOR THE WHOLE MONTH AFTER RUNNING MACRO-1 (52)
-9-
13. FIG-13: SUMMARY OF REPORTS GENERATED FOR THE MONTH (MACRO-2) (52)
14. FIG-14 : GENERATION OF BTS<DATE> FOR ALL SUMMARY AND BTS<DATE>_MORNING REPORT (59)
15. FIG-15 : IP LOG (TXT) (61)
16. FIG-16: IP LOG FORMATTED IN EXCEL BY MACRO (61)
17. FIG-17: BTS<DATE> MORNING REPORT (62)
18. FIG-18: BTS<DATE> FOR ALL SUMMARY REPORT WITH EXACT EVENT DATE TIME EXTRACTED THROUGH MACRO (62)
19. FIG-19: LAYOUT OF SMS TRIGGER APPLICATION (68-70)
-10-
ABBREVIATIONS & NOMENCLATURES

1. BSNL: Bharat Sanchar Nigam Limited 2. OSS: Operations Support Systems 3. BSS: Business Support Systems/Base Station Sub system 4. OMC-R: Operation & Maintenance Center for Radio 5. BFR: BTS Fault Report 6. BTS: Base Transceiver Station 7. BSC: Base Station Controller 8. MSC: Mobile Station Controller 9. SSA: Secondary Service Area 10. USO: Universal Service Obligation 11. DOT: Department of Telecommunication 12. ISP: Internet Service Provider 13. TRAI: telecom Regulatory Authority of India 14. PSDN: Public Switched Data Network 15. ISDN: Integrated Services Digital Network 16. GPRS: General Packet Radio Service 17. SMS: Short Messaging Service 18. MNP: Mobile Number Portability
-11-
OBJECTIVES
The 8 week summer internship involved the following objectives to be met for BSNL, Chhattisgarh (Mobile/OSS division):
1. Analysis of BTS Fault reports for further action (to be taken by accounts department towards payment remittances to electrical vendors).
2. Design & implement process automation for OMC-R reports. 3. Analysis of existing OSS system and suggest possible areas of improvements for a more automated, real time alarm status monitoring/logging.
-12-
EXECUTIVE SUMMARY
BSNL is one of the major telecom players in Chhattisgarh with 48,19,853 wireless subscribers (MP-CG Circle). BSNL has in Chhattisgarh, more than 1800 BTS, 44 BSCs and 2 MSCs (NGN) at Durg & Raipur respectively.
With emerging technology, need for a more robust and scalable network and ever increasing subscriber base, BSNL replaced the legacy systems with Next Generation OSS systems. The OSS comprised of OSS Server, provided by HCL technologies and an OMC-R (Operation & Maintenance Center for Radio) server from Alcatel Lucent running on Sun Solaris operating system.
Over the years, BSNL has gained a lot in terms of technology and usage by the new OSS systems, which included better and real time network and QoS monitoring, ease of maintenance and more efficient operations, but there were some issues which had crept in and needed attention. Some of the issues were related to OMC-R report generation, which was done manually, everyday to generate useful reports related to network status, BTS faults in 6 SSAs of Chhattisgarh and also monitor the QoS standards. These processes were tedious, redundant and were often irregular (absence of staff, technical issues etc) thus leading to accumulation of insufficient/incomplete data for further analysis.
The reports generated by OMC-R server is of utmost importance to BSNL as this is the only (and most advanced) source of data pool BSNL uses to monitor the network of Chhattisgarh. Since most of the rural parts are affected by bad weather, difficult terrain and naxalites, it is important to not only have a real time logging of network status, but also have useful reports generated by the raw data provided by OMC-R servers in order to analyse
-13-
the status of BTS/Sectors which are down, send the response teams for repair work as soon as possible and also to check the payments against the invoices generated by third party electrical vendors providing power backup to USO-BTS (Details discussed in later part of this report).
The role of OSS analyst involved thorough analysis of OMC-R reports to come up with suggestions and solution(s) to generate more useful reports from the raw data of OSS servers
-14-
CHAPTER - 1 COMPANY PROFILE
-15-
harat Sanchar Nigam Limited (BSNL) is an Indian state-owned telecommunications company headquartered in New Delhi, India with Mr. R.K. Upadhyay as Chairman & MD. It is the largest provider of fixed telephony and fourth largest mobile telephony provider in India, and is also a provider of broadband services.
BSNL is India's oldest and largest communication service provider (CSP). It had a customer base of 98.5 million as of March 2012. It has footprints throughout India except for the metropolitan cities of Mumbai and New Delhi, which are managed by Mahanagar Telephone Nigam (MTNL).
Financial facts about BSNL:
Revenue : 32,045 crore (US$6.39 billion) (2009-10)[1] Net income : 1,822 crore (US$-0.36 billion) (200910) Total assets : 132,243 crore (US$26.38 billion) (200910)[2] Owner : Government of India
BSNL, then known as the Department of Telecommunications had been a near monopoly during the socialist period of the Indian economy. During this period, BSNL was the only telecom service provider in the country. MTNL was present only in Mumbai and New Delhi. During this period BSNL operated as a typical state-run organization, inefficient, slow, bureaucratic, and heavily unionized. As a result subscribers had to wait for as long as five years to get a telephone connection. The corporation tasted competition for the first time after the liberalization of Indian economy in 1991. Faced with stiff competition from the private telecom service providers, BSNL has subsequently tried to increase efficiencies itself. DoT veterans, however, put the onus for the sorry state of affairs on the
-16-
Government policies, where in all state-owned service providers were required to function as mediums for achieving egalitarian growth across all segments of the society. The corporation (then DoT), however, failed to achieve this and India languished among the most poorly connected countries in the world.
BSNL was born in 2000 after the corporatization of DoT. The corporatisation of BSNL was undertaken by an external international consulting team consisting of a consortium of A.F.Ferguson & Co, JB Dadachanji and NM Rothschild - and was probably the most complex corporatisation exercise of its kind ever attempted anywhere because of the quantum of assets (said to be worth USD 50 Billion in terms of breakup value) and over half a million directly and indirectly employed staff. Satish Mehta, who led the team later confessed that one big mistake made by the consortium was to recommend the continuation of the state and circle based geographical units which may have killed the synergies across regions and may have actually made the organization less efficient than had it been a seamless national organization. Vinod Vaish, then Chairman of the Telecom Commission made a very bold decision to promote younger talent from within the organization to take up a leadership role and promoted the older leaders to a role in licensing rather than in managing the operations of BSNL. The efficiency of the company has since improved, but needs more attention, resources and bold decisions.
The corporation remains heavily unionised and is comparatively slow in decision making and its implementation, which largely acts at the instances of unions without bothering about outcome. Management has been reactive to the schemes of private telecom players. However, BSNL is now pacing up being the first operator to launch 3G services in India, and the only operator to have pan india 3G license. It is also rolling out 4G Wimax
-17-
services, another first in the category. BSNL has been providing connections in both urban and rural areas. Pre-activated Mobile connections are available at many places across India. BSNL has also unveiled cost-effective broadband internet access plans (DataOne) targeted at homes and small businesses. At present BSNL enjoy's around 65% of market share of ISP services. (All subscriber stats courtesy TRAI, March 2012)
BSNL is rolling out new broadband services such as triple play. BSNL planned to increase its customer base to 108 million customers by 2010. With the frantic activity in the communication sector in India, the target was almost achieved.
BSNL is a pioneer of rural telephony in India. BSNL has recently bagged 80% of US$ 580 m (INR 2,500 crores) Rural Telephony project of Government of India.
In March 2009 BSNL advertised the launch of BlackBerry services across its Telecom circles in India. The corporation has also launched 3G services in select cities across the country.
Since December 2011, many other private operators have started rolling out their 3G services alongside BSNL and are enjoying some success in their campaigns to get a pie of market share. While BSNL still maintains it's connectivity standard and expands to many more areas including rural areas with their 3G services. Also the network infrastructure has been upgraded to provide speeds upto 7.2 MBits/sec and 21.1 MBits/sec. It is enjoying a slow but somewhat steady success in gaining market share in this regard.
-18-
The introduction of MNP (Mobile Number Portability) which is a service that lets the consumer change wireless service providers while retaining their mobile number, BSNL has seen many customers opting for this service to join their network, hence increasing the market share. As the Indian Wireless market grows, BSNL still has a loyal base of subscribers and many more subscribers being added to it every day.
BSNL has the largest 3G network in India. Additionally, BSNL 3G services usually cover not only the main town/city but also the adjoining suburbs and rural areas as well. As of now BSNL has 3G services in more than 900 cities across India.
BSNL Chhattisgarh:
Chhattisgarh, which is the 10th-largest state in India shares a common telecom circle with Madhya Pradesh (as MP-CG circle) with an overall teledensity of 53.88 as on 31 March 2012.
BSNL is among the 9 major telecom service providers (wireless/wireline, barring Loop & Etisalat) in Chhattisgarh with wireless subscriber base of 48,19,853 connections and wireline subscriber base of 8,51,068 as of March 2012.
In Chhattisgarh, BSNL operates with 6 SSAs, 1800+ BTS, 44+ BSCs and 2 MSCs, both equipped with Next Generation Switching systems. BSNL was the first operator to introduce 3G and Wimax services in Chhattisgarh.
-19-
BSNL subscriber base vis--vis other major wireless service providers:
MP-CG Subscriber base (Wireless)

13,737,890
12,227,971 9,671,545
4,840,432
4,819,853
4,106,915
1,243,694 934,803 Aircel
Idea
Reliance
Airtel
Tata
BSNL
Vodafone
Videocon
(All subscriber statistics courtesy TRAI, March 2012)
-20-
CHAPTER - 2 PRODUCT/TECHNOLOGY DESCRIPTION
-21-
he product discussed in this report is the OSS Server, provided by HCL Technologies Ltd. and OMC-R server, provided by Alcatel Lucent, running on Sun Solaris systems. BSNL awarded HCL, one of Indias leading IT and technology services a major contract to provide a highly scaleable OSS solution in the form of Inventory Management, Provisioning and Fault Management for support of all voice services. HCLs contract applies to the Southern and Eastern zones of India , representing support for a subscriber base of 20 million.
This Next generation OSS delivers a tightly integrated provisioning, inventory and fault management solution, allowing BSNL to build unparalleled services levels to its customer base. The majority of subscribers will benefit immediately from the new platform, and this innovative approach to OSS supports BSNLs movement towards aligning their business model on customer line, rather than individual product and service offerings. HCL has also delivered a highly scalable solution, designed to rationalize the number of IT platforms, consequently lowering infrastructure and capital expenses, as well as reducing time to market.
Together, these systems provide various reports pertaining to network, inventory and services as well as their configuration. While the OMC-R server produces raw data in the form of text files, the OSS server uses the built in intelligence to generate meaningful reports to carry out various analysis and take suitable actions whenever required.
-22-
2.1 Introduction to OSS systems
OSS stands for Operations Support Systems, i.e. an IT system for a telecommunications network. OSS software are dedicated specifically to providers of telecommunications services. The processes supported by OSS systems include service management and maintenance of the network inventory (modules: Service Inventory Management and Network Inventory Management), configuration of particular network components as well as fault management.
An issue related to OSS systems, apart from integration, was the construction of system architecture. Ultimately, OSS systems were structured around four basic elements:
Processes Data Applications Technology
-23-
The processes pertain to the order of particular activities. Data concerns the information stored in OSS systems. Applications join the above elements: they realize the processes of data management. Finally, technology defines the method for creating applications. The exact definition of OSS architecture was formulated in 1990 in the model named Telecommunications Management Network (TMN) by the Telecommunication Standardization Sector within ITU (International Telecommunication Union). OSS systems consist of four levels:

Business Management Level (BML) Service Management Level (SML) Network Management Level (NML) Element Management Level (EML)
The management level was further defined by the ISO norm for the FCAPS (Fault, Configuration, Accounting, Performance, Security) model. The norm was also adopted by ITU-T standards as a basis for TMN 3000 M. - M.3599 standards. Although the FCAPS model was originally dedicated to IT enterprises, it also found use in public telecommunications networks of service providers conforming with the ITU-T TMN norm.
The development of broadband services and VoIP technology in the 21st century has included home network management within the scope of Operations Support Systems.
Present-day OSS platforms offered by IT companies are structured in accordance with the NGOSS standards. They consist of fully configurable modules which allow for adapting OSS software to individual needs. The
-24-
result is an increased return on investment (ROI) and a reduction in operating costs involved in the implementation and use of OSS systems. Advanced OSS systems constitute a comprehensive support for all processes within Operations Support Systems. They are noteworthy for high efficiency which is due to such state-of-the-art information
technologies as J2EE, Cobra, RMI, XML and SOAP. As a result, OSS systems can integrate with other IT systems implemented in the company, e.g. BSS systems and CRM (Customer Relationship Management) .
There are, in consequence, many benefits to be drawn from OSS systems. First of all, the modules that can be configured and adapted to a user's individual needs constitute an important source of the competitive advantage right from the beginning. The possibility of their integration raises the flexibility of the system and allow for quick response to dynamic changes in the business environment. Furthermore, operating costs are reduced and the return on investment rises. OSS systems allow for efficient management of services and the entire telecommunications network, which is a corollary of their comprehensive approach to management. Another advantage is the reduced number of problems, breakdowns and defects. Advanced well-designed OSS systems consist of efficient modules for fault management which ensures quick detection and solving of problems. Additionally, the structure of OSS systems enables their users to extend the telecommunications network based on the very same platform without further investments. High scalability and welldesigned support for developing telecommunications networks are also important features of advanced OSS systems. Moreover, they also contain modules for customer service which provide such optimized and userfriendly functions as contract management.
-25-
2.2 Introduction to 9153 OMC-R Product (Alcatel-Lucent)
In the GSM world, the OMC or Operation and Maintenance Center is defined as a system responsible for operation and maintenance of a given set of network equipments. The Alcatel-Lucent 9153 Operation & Maintenance Center for Radio is a flexible, easy-to-use solution which provides Network Element (NE) management for Alcatel-Lucent BSS voice and data services, including GPRS, EDGE.
In compliance with the GSM specifications, the 9153 Operation & Maintenance Center for Radio Part (OMC-R) is concerned with Element Management and Sub-Network Management of BSS network subsystem:
The whole set of BSSs, i.e. BSCs, BTSs, TCs and transmission systems GPRS Multi-BSS Fast packet Server (MFS), i.e. the BSS part of GPRS equipment.
9153 OMC-R is a management system based on one or several UNIX servers connected with a number of user terminals via Ethernet-LAN or WAN (depending on the network configuration) and with a number of BSCs and MFSs that have to be managed. Figure 1 shows an overview of OMCR with respect to managed elements physical and functional
interconnection.
-26-
Operation and maintenance functions used for BSS and GPRS/EDGE management can be organized into some of the functional management domains specified by ITU-T M.3010. These domains are:
1. Performance Management (PM)
BSS Performance Management handles administration, scheduling and triggering of measurement campaigns to be performed per BSC and MFS in order to supervise the Quality of Service (QoS) offered to telecom subscribers. It provides retrieval, forwarding, processing, presentation and archiving of measurement results. At OMC-R level two types of measurement results are handled:
a. BSS observation counters, i.e. retrieval of proprietary measurement results for display, analysis and export (in binary or ASCII format).
-27-
b. BSS performance indicators for dedicated supervision of QoS information and fast detection of telecom service degradation. Performance indicators can be compared with user defined thresholds allowing the generation of QoS alarms (handled by the standard OMC-R alarm handling function). These indicators are also displayed and analyzed thanks to graphic or tabular reports.
2. Configuration Management (CM)
BSS Configuration Management provides hardware management (BSS network extension, reduction or reconfiguration), software management (BSS software release migration), logical configuration management (BSS radio parameter adjustment for optimized configuration of radio related resources), as well as BSS date and time management.
9153 OMC-R also provides functions for extensive and time efficient logical configuration management with minimum telecom impact, e.g. massive adjustment of parameters for an optimized radio configuration or network wide activation of a new frequency plan.
3. Fault Management (FM)
BSS Fault Management offers network supervision through alarm handling, status monitoring of equipment and resources, equipment handling and test management. In addition, the Alcatel-Lucent BSS supports autonomous recovery of GSM resources through reconfiguration of BTS in case of TRX failures.
-28-
A single OMC-R configuration can supervise multiple BSSs (the BSCs with all related BTSs), BSSs connected to different MSCs depending on the chosen configuration and multiple GPRS MFSs. Moreover, the OMC-R provides the capability to be connected to a Regional or Network Management Center (NMC) via vendor independent Q3 BSS mediation interface or via any available external interfaces.
2.3 9153 OMC-R embedded in the Network Management environment
9153 OMC-R follows the Hierarchical Network Management approach defined in TMN standards; it takes the functional role of an element manager of Alcatel-Lucent BSS network elements:
-29-
-30-
2.4 OVERVIEW OF 9153 OMC-R CONFIGURATIONS
2.4.1 Components of an 9153 OMC-R
9153 OMC-R architecture allows a flexible distribution of management components across the different nodes of the network according to specific needs related to for instance network dimensions and performance requirements. By means of this configuration flexibility, the management system can evolve and be adapted to new dimensioning requirements, adding new machines where necessary.
The main hardware configurations supported by 9153 are:
- Single server configuration with front-end workstations and X-terminals:
-31-
-Distributed configuration with three dedicated servers and front-end workstations, and X- terminals:
The physical hardware configuration of an OMC-R is composed of:
- Master Server:
Unix Server, whose main purpose is to run the OMC-R management application. In particular, this server hosts system administration functions, Alarm Database and Surveillance module, Q3 mediation and the Radio Network Configuration database.
In the Single server configuration only, this host server mediates also data from the Network Elements, and stores these data in the BSS database.
-32-
- Agent Server:
Unix Server, only present in the distributed configuration, whose main purpose is to host the mediation of group of Network Elements in order to increase the capacity of the OMC-R.
- HMI Server:
Unix Server whose main purpose is to enhance the performance of the system by moving the user interface part of the processing from the master Server to the HMI Server. In case of remote user terminals, a HMI server is required to ensure the terminal performances, which might be limited by weak transmission capability.
- User Terminal:
Graphical Workstations connected to the master Server or to the HMI Server.
Besides the OMC-R application software, the software part includes thirdparty software (e.g. Sun Solaris OS, Object Store database, X.25 protocol, OSI stack, etc.).
-33-
2.4.2 OMC-R Configurations
Depending on the size of the BSS network that has to be supervised, five types of OMC-Rconfigurations have been described as generic. The relevant BSS capacity for each OMC-R configuration is listed below:
1. Small OMC-R configuration (SML)
2. Standard OMC-R configuration (STD)
3. Large OMC-R configuration with two variants (LRG)
4. Extra Large OMC-R configuration (X-Large) (XLRG)
5. Extra Extra Large OMC-R configuration (XX-Large) (XXLRG)
The first three configurations have only one Master Server and no Agent Server. The X-large configuration (distributed configuration) is composed of one Master Server and one or two Agent Servers (depending on server generations). The XX-Large configuration is composed of one Master and two Agent servers (UltraSparc IV generation only).
OMC-R host and HMI Servers are built on Sun Microsystems1M servers. Two generations of these servers are used:
UltraSparc III generation since B7 release
UltraSparc IV generation since BB release
-34-
OMC-R host servers (Master or Agent) are built on Sun Fire "(UltraSparc III and UltraSparc IV generations) servers which are the highest fault-resistant systems in their class. They offer excellent Reliability, Availability, and Serviceability (RAS) features. As an example, autonomous restoration mechanisms are supported in case of following failures: - Power supply and cooling module failure - CPU failure - Memory failure - Disk failure (RAID technology, 100 % data redundancy, hot plug disks).
2.4.3 User Terminals
Workstations (WS) are used as user terminals. Workstations are client graphical terminals running on their own operating system. They can be used as terminals to operate the network with the OMC-R application but it is also possible to run some applications (e.g. measurement post processing) without impacting server resources.
OMC-R terminals are not dedicated to an OMC-R and an operator can use the same terminal to access different OMC-Rs (and possibly other applications).
The Citrix MetaframelM client software is installed on the terminals and is communicating with the Citrix MetaframelM server software, hosted on the OMC-R HMI server. The maximum number of user sessions supported by this Citrix HMI server is in this case reduced by one user (except for the Tiny HMI server)
-35-
2.4.4 HMI Servers
There are several kinds of HMI servers, each of them providing a different capacity in terms of number of operator sessions depending on the OMC-R type they are connected to. All HMI servers can be located either at the OMC-R site or remotely depending on the chosen operating topology. The large capacity HMI servers are usually located at the OMC-R site when the small capacity servers are often remotely located. 2.4.5 OMC-R Components Hardware Generations
The following table defines the hardware reference of the OMC-R host and HMI server per type of configuration.
OMC-R server Tiny Small Sun Fire V880 Sun Fire V490 Standard Sun Fire V880 Sun Fire V490 Large Sun Fire V880 Sun Fire V490 with external disk bay SE3510 X-Large Sun Fire V880 (x2) Sun Fire V490 with external disk bay SE3510 (x2) XX-Large Sun Fire V490 with external disk bay SE3510 (x3)
HMI server Sun Blade 150, Ultra25 Sun Fire 280R Sun Fire V440 or Netra 440 Sun Fire 280R Sun Fire V440 or Netra 440 Sun Fire V440 or Netra 440
-36-
The workstations can be either Sun U51 U1 a, or Sun Blade series 100/150, or Ultra25 or any terminal when a Citrix solution is used (Universal terminal concept).
2.4.6 Software
The software part of the 9153 OMC-R is based on the Alcatel Management Platform (ALMAP 3). ALMAP offers a powerful development environment (COMET) and a set of reusable components that fulfill telecommunication operator requirements.
The architecture of ALMAP is object-oriented and complies with the major TMN and system management standards issued by ITU-T, ETSI and ISO and with recommendations from industry forums such as NMF. The ALMAP architecture is designed to support integration, scalability and flexibility.
ALMAP provides a comprehensive family of generic component reusable for the development of Network Management products. These generic components cover the functions common to all Network Management products, such as alarm surveillance (compliant with X733 standards), security (management of user accounts with profiles definition allowing to associate functions and network elements to a user) or system management functions. The open architecture permits to reuse or share these components across the Alcatel Management products for different telecommunication areas, including access, transmission, switching or mobile networks, thus providing the operator with a homogeneous management system, and also minimizing Alcatel Element and SubNetwork Managers cost of ownership.
-37-
ALMAP is multi-OS platform. In the BSS case, only the SUN Solaris compatible version of ALMAP is used. ALMAP has been regularly updated according to the different version of Solaris, from 2.6 up to Solaris 10.
In addition to ALMAP, other third-party softwares are used on OMC-R: Communication stacks : Solstice X.25, OSI and CMIP Graphical window management : X11 and Motif, Windows CDE, OMC-R database : Object Store distributed database (Progress Software), Help and documentation on-line : HTML Server and/or Navigator, Database for BSS Performance Management : Oracle
2.4.7 OMC-R - BSC interconnection
The OMC-R host can be connected to the BSC in several ways that give a high degree of flexibility in choosing the OMC-R site (see following Figures).
(1) Via PSDN
The OMC-R - BSC can be connected remotely through Packet Switched Data Network. In this case, up to two 64 kbitls links at OMC-R site and one 64 kbitls link at each BSC site may support the X.25 connection to the X.25 PSDN. For security reasons all physical X.25 connections can be configured redundantly. (Refer fig- 6)
-38-
Fig-6 : OMC-R to BSC connection via PSDN
(2) Co-located site
Without use of additional router, the OMC-R can be co-located with maximum one or two 9120 BSCs depending on the use of redundancy. In this case the interconnection is realized through dedicated serial lines.
Fig-7 : OMC-R to BSC connection with the help of co-located site
In case of 9130 BSC Evolution, the BSC can be connected to the LAN where the OMC-R is also connected. In such case, there are no limitations in terms of number of BSC Evolution managed locally, except the maximum number of cells managed by OMC-R.
-39-
(3) Via A Interface - MSC Connection (Alcatel- Lucent Universal Routing)
The OMC-R can be connected remotely to the 9120 BSC or 9130 BSC at the MSC site by routing the O&M links over AI Ater interface (either X25 over AI Ater for 9120 BSC or IP over AI Ater for 9130 BSC Evolution).
Fig-8 : OMC-R to BSC connection via A Interface - MSC Connection (Alcatel- Lucent Universal Routing)
Thanks to the availability on the market of 'intelligent' multi-protocol routers, the Alcatel-Lucent 'Universal Routing' solution is recommended as the standard solution. Deployment of NGN in the field, replacing the MSCs, requires a new way for routing the O&M links between OMC-R and NEs (BSC and MFS).
2.4.8 OMC-R -MFS (GPRS) interconnection
This interface requires an IP connection in order to support Q3 and FTP protocols. Whatever the generation, 9135 MFS or 9130 MFS Evolution, the MFS supports two Ethernet ports to connect directly the Local Maintenance Terminal and the OMC-R.
For the 9130 MFS Evolution, in case the MFS is eo-located with BSC Evolution it is also possible to encapsulate the MFS O&M flow into the Ater
-40-
interface and to use the Alcatel-Lucent Universal Routing solution to establish the O&M link between MFS and OMC-R.
The minimum bandwidth required for MFS - whatever the generation - is of 256 Kbits/s.
2.4.9 Centralized Management
Several possibilities exist to supervise several OMC-Rs from one central location. They are detailed here below:
a. Alarm Call Out
The Alarm Call Out (ACO) feature enhances the alarm handling service. It allows supervision of the network with a reduced number of operators, for example at nighttime or during the weekend.
ACO can be activated from any OMC-R terminal, either local or remote. ACO applies a defined filter on the alarms received at OMC-R. Only one ACO filter can be activated per OMC-R.
The filter is based on criteria as alarm severity, alarm type, probable cause, event date and time. This filter can be activated:
According to a defined schedule (range of days in the week and range of hours for each day of the week) On all the BSC or on a subset
The alarms complying with the filter are:
-41-
Either sent to a printer Or posted to predefined e-mail addresses (up to 2 different addresses) Or both sent to printer and posted to predefined e-rnail addresses.
When mail is chosen as output, for each alarm matching the filter, a mail is sent. The definition of alarm in the mail is restricted to 160 characters.
The same 160 characters per alarm are printed out when printer is chosen as output. Printer can be either located on the OMC-R LAN or connected to a remote HMI server on a distant site.
The filtering criteria of ACO and of Alarm Surveillance (AS) module are the same. Consequently an alarm sub-list can be created in AS module in order to display the alarms verifying the ACO filter.
AS views are available on any terminals connected to local or remote HMI servers. AcO filter and service definitions are available through a WEB browser interface.
Consequently, on condition that IP addresses of other OMC-R have been set, and routes have been opened, an operator can define the ACO filter and services for several OMC-Rs from his terminal, without having to do any remote connection on the other OMC-Rs.
-42-
Fig-9 : Alarm call out options
These automatic actions are performed through command mode scripts defined by the operator specifically for each action. Typical examples are:
Sending a SMS/email to on-duty people upon reception of a predefined set of alarms. This is equivalent to the previously described Alarm Call Out feature but with the benefit of a real- time reaction.
Performing a well-defined action upon reception of a certain alarm (such as restarting the board concerned by the received alarm). This allows OMC-R operator concentrating on the most important alarms.
In both cases, main benefit from the feature is that it allows saving aPEX cost.
-43-
b. Centralized management via Network Management System (NMS)
Thanks to the real-time Q3 interface for Fault Management, it is possible to connect one or several OMC-R to a NMS, centralizing the network supervision.
Filtering capabilities are proposed on this interface in order to reduce the flow of alarms when several OMC-R are used, allowing central operators to concentrate only on important alarms.
-44-
CHAPTER - 3 DATA ANALYSIS, INTERPRETATION AND FINDINGS (ASSIGNMENT-1)
-45-
nalysis (and automation) of BTS Fault reports for further action to be taken by the management.
3.1 Details of the assignment: As mentioned earlier, BSNL has more than 1800 BTS in Chhattisgarh, of which, nearly 50% BTS are owned and maintained by BSNL, and the rest is outsourced to third parties, including the power supply. The BTS having power supply from third party vendors are named as USO-BTS. All the BTS are monitored by the central switching office at Raipur. The OMC-R servers monitor and log critical information of all the BTS in the 6 SSAs of Chhattisgarh state. Any fault like loss of traffic, disruption in operations due to power supply or environmental factors are logged by the OMC-R server. This data is used by the OSS server to generate daily reports, in various formats and different contexts including (but not limited to):
BHOD BSC report BHOD BTS report BHOD Sector wise reports BTS wise busyhour report Call drop report Handover report Hourly report Interference report TRAI network congestion report
-46-
The assignment involved thorough analysis of BTS fault reports to extract the details of faulty USO-BTS in all the 6 SSAs in Chhattisgarh region. The reports were to be generated area wise, broken down into monthly basis for the year 2011-12.
The reports generated would then be analyzed by the management for various payments to be remitted to various electrical vendors. (Analysis of payments was not a part of the assignment)
An estimated more than Rs. 3.5 Lakh (rough estimate, actual may be higher) savings is expected by the management when these reports are used to verify the payments to be made.
The data of faulty BTS is extracted from multiple OSS reports, namely the Sector wise BTS report (generated on daily basis by the OSS server, from data received from OMC-R server) and the Monthly aggregated report.
These two reports are generated separately and the process of generating BFR using these two reports was done manually on daily basis.
The BFR report was then summarized for separate SSAs for a particular month. The summarized reports were used to analyze the invoices sent by the power supply vendors. The report was then forwarded by the management to the accounts department for further action.
The assignment also required the entire process of generating the BFR to be automated. This was necessary as well as beneficial for the management in the following ways-
-47-
1. The process of generation of BFR would be more streamlined, regular and organized.
2. Format of BFR will be standardized. Anyone can generate the reports in a standard format. 3. Well organized and documented reports. 4. Automated process would drastically reduce the time taken in generation of BFR, enabling management to respond quickly on critical alarms.
3.2 Methodology
In order to automate the process of generation of USO BTS fault reports, it was decided that the automation will be done using Macros in Microsoft Excel. This was the most cost effective and efficient method of process automation and was deliverable in 15 working days.
The automated solution could run the following steps automatically1. Using the sector wise daily report, extract the USO BTS by filtering by name. It is to be noted that each BTS has a unique ID and every USO BTS ID has the term USO appended into it.
-48-
2. Filter out the USO BTS having zero traffic in all the 3 sectors. It is to be noted that every BTS has 3 sectors, identified as <BTS NAME>_1 (alpha sector), <BTS NAME>_2 (beta sector) and <BTS NAME>_3 (gamma sector). For example : AKTR_USO_BTS_Ramnagar_1 is an alpha sector of USO BTS in Ramnagar area of Akaltara BSC. 3. The BTS having zero traffic in less than 3 sectors will not be considered as all 3 sectors must have zero traffic in order for a BTS to be termed as faulty or dead. 4. Sort the BTS SSA wise and remove duplicate entries. 5. Copy and paste the filtered data into a new excel workbook. This workbook would store the filtered data extracted from daily reports for the whole month. 6. Repeat the procedure on all sector wise reports for the month (28/29/30/31 days as the case may be) 7. After the monthly report has been generated, create a summary sheet and calculate the total number of faulty USO-BTS (having zero traffic in all 3 sectors), grouped by SSAs.
-49-
Sector wisedaily network monitoring report
Macro-1 Copy filtered data (Manual)
Detailed USO-BTS fault report generated
Macro-2
Detailed + Summarized USO-BTS fault report generated
Monthly aggregated network monitoring report
Macro-1
Fig-10 : Generation of BFR
After the automation was done, the SSA wise faulty reports were analyzed against the invoices sent by the power supply vendors. This was done by:
1. Comparing the downtime obtained by the reports generated and the downtime and BTS location/name mentioned in the invoice.
2. Preparing a detailed report to estimate the over-invoicing, if any. 3. Forward the report to the accounts department for further action.
-50-
3.3 Sample input and resultant (automated) output reports
Note : Due to confidentiality of the data contained in these reports, the values have been changed to arbitrary numbers.
Fig-11: BHOD Sector wise report (one day report)
Fig-12: Daily reports aggregated for the whole month after running macro-1
-51-
Fig-13: Summary of reports generated for the month (Macro-2)
-52-
3.4 Findings
It was found that using the macro enabled excel workbook for automation of report generation of USO-BTS faults, the objectives of management were met successfully without having to invest in developing a separate software to generate the desired reports.
The automated process brought the following benefits to the management-
1. Almost 80% reduction of time in generation of processed OMC-R reports and BFRs. Manual process replaced by automated report generation.
2. Well organized and error free BFR generated for the whole year (Month wise)
3. Verification of accounts payable, electrical department lead to consolidated savings of more than Rs. 3,45,000 towards payment to third party power backup vendor.
-53-
3.5 Limitations
The macro based automated process has the following limitations:
1. The format of the sector wise daily report and monthly aggregated reports should not change as the macro programming is done over selective columns. Since these reports are generated by OSS server using raw data of OMC-R server, any change in format is unlikely. Remedy: If for any reason, the format of the above mentioned reports change, some minor modifications will be needed in the macro code in order to make the macro execute successfully.
2. As of now, the macro code does not automatically copy-pastes the filtered data from Sector wise-daily network monitoring report and monthly aggregated network monitoring report to the BFR. This is done manually (28/29/30/31 times as the case may be). For generating summarized data from detailed report, a separate macro has been written.
Remedy: Due to time constraint on deliverable, this method (of creating two macros) was adopted. It is possible to integrate the two macros and implement the code to automatically read the daily reports from the repository and perform the automation, which would require time and expertise.
-54-
-55-
esign & implement process automation for OMC-R reports.
4.1 Details of the assignment:
One of the most important reports/logs generated using the data of OMC-R server are: 1. IP1-<date> log: (Generated by OMC-R) This report is aggregation of various data incorporated over time (every 15 days) which includes BTS faults generated, time of occurrence of fault, reason (Loss of all channels, performance degradation etc.), sectors affected, fault clear time (if cleared).
2. BTS_<date>.morning report: (Generated by OSS) This report contains the daily list of faulty BTS in the respective BSCs. The report contains data of past 6 months till the current date (on which the report is made). The report contains MSC name, BSC name, BTS Name (which is down), responsible person (for carrying out repair process), SSA name, Event date & time, reason, city, radiation date, phase etc.
With the help of the above two reports, a report named BTS<date>for all summary report is generated manually, on daily basis. This report contains the aggregation of above two reports (both for 2G & 3G BTS) and the database of the concerned employees of BSNL responsible for the restoration process of faults in BTS in their respective serviceable areas. The database includes the Name, designation, area and phone number of the concerned person.
-56-
The report contains faulty BTS summarized in various formats viz. SSA wise, city wise, USO electrical (power supplied by third party vendor), USO KEC (power supply by BSNL) etc.
These reports are currently generated manually, on daily basis. For this, a dedicated resource is engaged every morning to perform the task.
This process had several limitations including resource wastage, inconsistent data/old data and often missing data (non generation of reports due to employee absence etc).
One more limitation of the generation of BTS<Date>for all summary was the logging of time in the event date * time field of the report. This column is used to log the actual time of occurrence of fault in any particular BTS. A known issue of time mismatch between the data sent by the OMC-R server and that interpreted by the OSS server was preventing the exact fault occurrence time to be logged in the mentioned column in the BTS<Date>for all summary report & BTS<date>_morning report.
For example, if a fault occurred at 20:38 hours on 02/06/2012, the OSS server would punch in only the date of occurrence of the event, whereas the time would be an arbitrary value or NULL.
Hence, the person generating the report next morning would enter event time as 00:00:00 hours, hence quoting incorrect time. This was causing problems in estimating the exact downtime of BTS and hence any payment related decisions were becoming difficult by the accounts department since they were unable to estimate the exact downtime in hours, especially if the penalty to be imposed (on power
-57-
suppliers in case of power fault) was on hourly basis, thus resulting in losses.
Although the exact time could be obtained from the IP1_<date> log generated by the OMC-R server, but it would have been a tedious task to do so as the log contains millions of data.
The management at BSNL required this problem of incorrect/inability to log the correct time of event to be solved, and also the manual process of generating the BTS<date>for all summary and a modified version of IP1_<date> log (in readable and filtered excel format) to be automated.
The assignment consisted of the following deliverables:
1. Study of process of generation of BTS<date>for all summary report 2. Identify a solution for the problem of incorrect event date logging. 3. Implement the above suggested solution. 4. Identify the requirements of modification of IP1_<date> log into readable and filtered excel format. 5. Analyze the automation techniques and suggest a cost effective solution. 6. Design the suggested automation solution for fetching correct event time values to both BTS<date>_morning report and BTS<date> for all summary report. 7. Implement the automated solution after proper testing and approval from management.
-58-
4.2 Methodology
At first it was decided to approach HCL for correction of mismatch between event time generated in IP1_<date> log by the OMC-R server and that fetched by the OSS server. But after even after several reminders and follow ups, there was no satisfactory response from the service center.
The BSNL management then decided to implement the automation by the use of Macro tool in Microsoft Excel. The reason being the same Protecting confidential data from any other third party software vendor and most importantly, saving the cost of development of separate software.
This was an indirect way of fetching the date from the log by comparing the values in BTS<date>for all summary and IP1_<date> log and substituting the date based on matched BTS, BSC and MSC names. Since the process would be automated, it will take less time for the reports to be generated with the correct event date and time.
Macro-1 IP1_<date> log (text file) Load into excel in delimited format Run macro to format, move & rename the columns in proper format, remove colons, commas and other delimiters. Filter the data as BTS faulty in all 3 sectors and reason as Loss of all channels
Filter BTS<date> for all summary report & BTS<date>_morning report on the basis of event time & date column having no time value.
Macro-2
Event time values pasted in BTS<date> for all summary and BTS<date>_mor ning report
Compare using VLOOKUP function and paste values
Fig-14:
Generation
of
BTS<date>
for
all
summary
and
BTS<date>_morning report
-59-
Steps for automation: 1. Open the IP1_<date> log in to excel, select delimiter as ; and load the file.
2. Run the macro-1. The macro will format the columns and rows in a proper manner (See screenshots below) and will rename the columns into proper English words (for eg. EVTTIM will be renamed as EVENT TIME etc)
3. Macro will also filter the BTS whose all 3 sectors are down with the reason Loss of all channels
4. The next filter will be to enlist only those BTS for which the clear time is NULL (i.e, the alarm has not been cleared yet, indicating that the BTS is still down)
5. Open the BTS<date> morning report and run Macro-2. This macro will filter the BTS having no time values in event date & time column and would use the VLOOKUP function to compare the BTS name, BSC name & MSC name from the (modified) IP1_<date> opened in excel and will fetch the exact event time into the respective column.
6. Similar macro to be run on BTS<date> for all summary report to fetch the event time correctly in the respective column.
-60-
4.3 Sample input and resultant (automated) output reports
Note : Due to confidentiality of the data contained in these reports, the values have been changed to arbitrary numbers.
Fig-15: IP log (txt)
Fig-16: IP Log formatted in excel by macro
-61-
Fig-17: BTS<date> morning report
Fig-18: BTS<Date> for all summary report with exact event date time extracted through macro (Image shown for only 2G worksheet)
-62-
4.4 Findings After the automation was implemented, the correct and exact fault time was being fetched into both the reports. This helped the management in estimate the exact downtime in hours and calculate the the penalty to be imposed (on power suppliers in case of power fault) on hourly basis, thus preventing any losses.
This assignment brought about the following benefits for BSNL:
1. Logging of correct event time in BTS fault report for proper monitoring of downtime, which was earlier being logged erroneously.
2. Reduction of time in generation of BTS<date>for all summary reports. Manual process replaced by automated report generation.
3. Well organized and error free BTS<date>for all summary report generated for the whole year (Month wise)
4. Recovering of correct penalties from electrical vendors (in case the down time was due to power failure).
-63-
4.5 Limitations: The above method of automation had the following limitations: 1. The format of the IP1_<date> log and BTS<date> morning report should not change as the macro programming is done over selective columns. Since these reports are generated by OSS server using raw data of OMC-R server, any change in format is unlikely.
Remedy: If for any reason, the format of the above mentioned reports change, some minor modifications will be needed in the macro code in order to make the macro execute successfully.
-64-
-65-
nalysis of existing OSS system and suggest possible areas of improvements for a more automated, real time alarm status monitoring/logging.
5.1 Details of the assignment The assignment required designing a solution for : sms alert system for USO cell site alarms (MAJOR & CRITICAL)
(Such a feature is provided by OSS server currently used by BSNL, but due to some technical difficulties, the SMS are not getting delivered. Also the provision for SMS triggering is only for critical alarms but the management required triggering of alarms for alarms of type major as well) Requirements-
1. Application should be able to extract alarm log from the OMCR Alarm software 2. Application should filter the alarm types as major and critical
3. Application should enlist the BTS Names of the concerned alarm
4. Application should enlist the name, area and mobile number of the concerned person from the database/excel <BTS Fault
report/Updated matrix>
5. Application should send an sms (Manual trigger or automated trigger) to the concerned person regarding the alarm.
-66-
5.2 Methodology
1. The application can be built either as an executable file to be run in Sun Solaris OS
OR
2. The application can be built as an excel plugin to perform the necessary actions
Functionality of executable jar file:
1. Integrate with OMCR alarm application
2. Extract real time alarm status
3. Store on a day wise record (txt or csv)
4. User can view the alarms through one or combination of the following filtersa. Alarm type b. Area wise c. Date wise
5. Application will enlist the name and phone number of the concerned person responsible for initiating the repair process
6. In case no phone number is available, provision for manually entering the mobile number
-67-
7. Provision to save the manually entered number in to records
8. Application will use an sms gateway (purchased separately/in house) to send sms to the designated mobile numbers
9. Application will log the time of sms sent
Fig-19: Layout of SMS trigger application:
Start screen
-68-
Send SMS screen
-69-
SMS Sent confirmation screen
-70-
Functionality of excel plugin-
1. Macro based plugin 2. Macro to filter the alarms as per criteria Major or Critical
3. Macro to look up the mobile numbers of the concerned persons responsible for maintenance of the BTS (Stored in other excel)
4. Highlight the BTS having no numbers assigned (For manual entry)
5. User will enter the mobile numbers in the highlighted fields
6. Additional plugin (Purchased separately/in house) to send sms through sms gateway
SMS contents1. Alarm Severity 2. ACK Status 3. FRDNAME 4. Event type 5. SPECPB 6. PBCAUSE 7. EVT TIME
-71-
Mode of application development:
Since the application involves handling of sensitive & confidential data, it is suggested to be contracted to the OSS vendor (HCL Ltd. in this case) through the standard process of inviting quotations and agreement on the final cost of development, along with the required SLA as required by BSNL.
5.3 Findings The above proposal was taken up by the BSNL management for consideration. After the approval of the technical team, the solution (as it is or modified) would be discussed with HCL to be implemented accordingly.
This process (of approval and forwarding to HCL) would take up to 3 months. The solution would benefit to BSNL by having a more advanced SMS based BTS fault warning system which could minimize the time of restoration of network in the affected cell site, thus minimizing downtime and losses due to it.
-72-
CHAPTER - 6 CONCLUSION
-73-
The three assignments delivered for BSNL, Chhattisgarh not only proved (again) the importance of automation, but also helped in maintaining detailed, correct, well-sorted and regularized reports with minimum effort, as compared to previously followed manual process.
The deliverables were assigned to the intern in such a manner that it would balance both the technical as well as management aspects of the particular process being worked upon. In any management internship, it is important that the intern gets an insight of both the aspects, so that it related to the concepts imparted by the respective faculties.
The deliverables were completed in stipulated time, were thoroughly tested before delivering to the management/process owners and are well suited for minimum 3 years of maintenance free operation (as discussed with the management)
The assignments also threw a light on working methodology of a large scale government organization where in process automation can bring immense benefits, given the large volume of paperwork involved and the need of a cost effective solution like macro based automation.
Thus, the 8 week internship at BSNL was beneficial for both the intern & the organization.
-74-
CHAPTER - 7 RECOMMENDATIONS
-75-
The following points may be recommended to BSNL, Chhattisgarh:
1. Given the time constraint and urgency of
the automation
requirements, using macro based solution was the most cost effective & fast implementable solution. But it is recommended to contact HCL Ltd. To rectify the mismatch occurring between OMC-R server & OSS server w.r.t fault event time logging. This would make the generation of BTS<date>for all summary report quicker and without the need of using an indirect method.
2. The SMS trigger system proposed in the assignment# 3 can be implemented within a short period of time. It is recommended to the management to implement the solution (with approval from technical team and higher management and suitable changes, if any) as this will help BSNL rectify the BTS faults quickly, minimizing the delay and ultimately reducing losses and most importantly, increasing customer satisfaction.
-76-
CHAPTER - 8 REFERENCES AND ANNEXURE
-77-
1. 9153 OMC-R Product description manual Provided by Alcatel Lucent
2. en.wikipedia.org 3. www.bsnl.co.in
4. http://gsmfordummies.com/tdma/logical.shtml#sdcch
5. http://www.ossnewsreview.com/telecom-oss/clarity-and-hcl-set-totransform-bsnl-network-with-next-generation-oss/
6. http://www.oss-system.net/oss-system-architecture.html
7. http://workcast-email.net/IN/F/A2zxIlBw0TGJ9EhDMiyb3Q/
8. http://www.teradata.com/resources/brochures/oss-bss-integratedbusiness-intelligence-for-the-communications-industry-eb5362/ 9. http://www.lightreading.in/document.asp?doc_id=215893
-78-

Abeer11020541002 Summer Internship Report

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Abeer11020541002 Summer Internship Report

Enviado por

Direitos autorais:

Formatos disponíveis

A PROJECT REPORT ON

BHARAT SANCHAR NIGAM LTD., CHHATTISGARH CIRCLE

Symbiosis Institute of Telecom Management

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

components, each of which focused on certain tasks in the enterprise.

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

8. Chapter- 6 : Conclusion 9. Chapter- 7 : Recommendations 10. Chapter- 8 : References

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

2. FIG-2 : OMC-R POSITIONING IN TMN (30)

4. FIG-4 : 9153 OMC-R SINGLE CONFIGURATION OVERVIEW (31)

5. FIG-5 : 9153 OMC-R DISTRIBUTED CONFIGURATION OVERVIEW (32)

6. FIG-6 : OMC-R TO BSC CONNECTION VIA PSDN (39)

9. FIG-9 : ALARM CALL OUT OPTIONS (43)

10. FIG-10 : GENERATION OF BFR (50)

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

15. FIG-15 : IP LOG (TXT) (61)

16. FIG-16: IP LOG FORMATTED IN EXCEL BY MACRO (61)

17. FIG-17: BTS<DATE> MORNING REPORT (62)

19. FIG-19: LAYOUT OF SMS TRIGGER APPLICATION (68-70)

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

ABBREVIATIONS & NOMENCLATURES

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

CHAPTER - 1 COMPANY PROFILE

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Financial facts about BSNL:

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

BSNL subscriber base vis--vis other major wireless service providers:

MP-CG Subscriber base (Wireless)

(All subscriber statistics courtesy TRAI, March 2012)

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

CHAPTER - 2 PRODUCT/TECHNOLOGY DESCRIPTION

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

2.1 Introduction to OSS systems

Processes Data Applications Technology

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

2.2 Introduction to 9153 OMC-R Product (Alcatel-Lucent)

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

1. Performance Management (PM)

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

2. Configuration Management (CM)

3. Fault Management (FM)

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

2.3 9153 OMC-R embedded in the Network Management environment

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

2.4 OVERVIEW OF 9153 OMC-R CONFIGURATIONS

2.4.1 Components of an 9153 OMC-R

The main hardware configurations supported by 9153 are:

- Single server configuration with front-end workstations and X-terminals:

Bharat Sanchar Nigam Ltd. Chhattisgarh circle

The physical hardware configuration of an OMC-R is composed of: