1.
Presented By LOKESH GUPTA RAKESH SONAR MANISH PANDEY VIKASH SHARMA BAIJNATH MANDAL ADITYA MAHAKULKAR ETOM PROCESS MODEL Balaji Institute Of Telecom Management ( BITM) Pune

2.
Purpose of the framework <ul><li>Service providers require well-automated operations processes </li></ul><ul><li>They are faced with </li></ul><ul><ul><li>ever-increasing competition </li></ul></ul><ul><ul><li>unpredictable market </li></ul></ul><ul><ul><li>an industry undergoing shakeup. </li></ul></ul><ul><li>The challenges before the service providers are </li></ul><ul><ul><li>Quickly provisioning new customers </li></ul></ul><ul><ul><li>Service quality issues </li></ul></ul><ul><ul><li>Introduction of new value-added services </li></ul></ul><ul><ul><li>Improvements in customer support. </li></ul></ul><ul><ul><li>Manage the integration required in mergers and acquisitions activity due to the consolidation trend the industry is now experiencing. </li></ul></ul>

3.
Objective behind TOM & eTOM <ul><li>An ‘Industry owned’ common business process model </li></ul><ul><li>Common definitions to describe processes of a Service Provider </li></ul><ul><li>Agreement on the basic information required to perform each process , sub-process and process activity </li></ul><ul><li>A process framework for identifying which processes and interfaces are in most need of integration and automation </li></ul>

4.
<ul><li>Purpose of the framework is to implement a process driven approach for managing the enterprise. </li></ul><ul><li>Ensure integration among all vital ESS. </li></ul><ul><li>The focus of eTOM is on the business processes </li></ul><ul><ul><ul><li>The linkages between the processes </li></ul></ul></ul><ul><ul><ul><li>Identification of interfaces </li></ul></ul></ul><ul><ul><ul><li>Common definition of terms </li></ul></ul></ul><ul><ul><ul><li>Agreement on basic information required for each process and identification of interfaces </li></ul></ul></ul>

5.
Concept of ETOM <ul><li>The eTOM (enhanced Telecom Operations Map) is a guidebook, the most widely used and accepted standard for business processes in the telecommunications industry. </li></ul><ul><li>common companion of ITIL. </li></ul><ul><li>these frameworks are part of the larger context of Total Quality Management. </li></ul><ul><li>ITU-T International Recommendation, known in 2004. </li></ul><ul><li>follow a customer focused pattern. </li></ul>

6.
<ul><li>Strategies within ETOM suggest </li></ul><ul><ul><ul><li>business-to-customer relationship </li></ul></ul></ul><ul><ul><ul><li>Also business-to-business relationships </li></ul></ul></ul><ul><li>ETOM is the product of the TeleManagement Forum. </li></ul><ul><li>part of the International Telecommunications Union. </li></ul><ul><li>developed in 1995. </li></ul><ul><li>through contributions of more than 35 TMF member companies and was formally approved by the ITU in 2004. </li></ul><ul><li>ETOM describes all the enterprise processes required by a service provider and analyzes them. </li></ul><ul><li>strength of eTOM as a business process framework is that it is part of the TM Forum NGOSS program and links with other work underway in NGOSS </li></ul>

9.
Some Standard <ul><li>ITIL </li></ul><ul><li>ISO9000 </li></ul><ul><li>ETOM </li></ul><ul><li>The eTOM team is responsible for capturing and representing business requirements in the form of business process models, and for developing and publishing these in the eTOM documentation. </li></ul>

10.
Description <ul><li>The eTOM model consists of Level-0, Level-1, Level-2 and Level-3 processes </li></ul><ul><li>The graphic representation of an eTOM model consists of rows and columns </li></ul><ul><li>The intersections of these rows and columns point out to specific processes as specified by eTOM </li></ul><ul><li>The topmost row denotes the customer facing activity i.e. marketing </li></ul><ul><li>the bottom most row indicates the supplier facing activity and the support activities </li></ul>

23.
Advantages <ul><li>It develops a scope addressing all enterprise processes. </li></ul><ul><li>It distinctly identifies marketing processes to reflect their heightened importance in an e business world. </li></ul><ul><li>It distinctly identifies Enterprise Management processes, so that everyone in the enterprise is able to identify their critical processes, thereby enabling process framework acceptance across the enterprise. </li></ul><ul><li>It brings Fulfillment, Assurance and Billing (FAB) onto the high-level framework view to </li></ul><ul><li>emphasize the customer priority processes as the focus of the enterprise </li></ul>

24.
<ul><li>eTOM Models </li></ul>

25.
The eTOM Business Relationship Context Model

26.
Service Provider Relationships

27.
Operator Work Processes... reality Customer Care Performance Management Fault Management Configuration Management Billing Traffic Management Awareness Creation Decision Support Implement. of Decision Supervision Restoration Fault Analysis Traffic Monitoring Traffic Analysis Rerouting Performance Measurements Results Setting Measurements Thresholds Performance Analysis Maintenance Actions Work Force Administration Billing Data Collection Invoicing Rating Discounting Order Handling Customer Query Cust.Info Analysis Service Activation Design Installation Problem Handling Planning Customer Installation AXE Network Provisioning AXE Configuration Analysis AXE Software Loading

28.
Other Operators <ul><li>eTOM is a framework for defining your own processes, not the final </li></ul><ul><li>answer itself. </li></ul>Fault Analysis Performance Data Collection Service Inventory Resource Inventory Customer Care Order Manager Network Activator Other OSS Supervision Usage Data Collection Fault Data Collection Fault Management Service Activation Billing & Rating Quality of Service Billing Product Inventory Inventory

29.
Any J2EE-Compliant Application Server EMS EMS NMS NMS EMS Connector API Java API XML API Java upon JMS/IIOP/RMI XML upon JMS Java upon JMS/IIOP/RMI XML upon JMS Third-Party Solutions JAXR ebXML JAXM SOAP JAX-RPC UDDI WSDL B2B Web Services enabled Solutions Legacy Solutions API XML enabled Application XML API Wrapping and Adapters Strategies Connector Legacy Application Native Implementations API J2EE Application API XML Application