本文主要摘自CISCO的一篇白皮书.

名词:

NGOSS: Next Generation Operations Systems and Software.

eTom: enhanced Telecommunication Operations Map

ITIL: Information Technology Infrastructure Library

1.什么是NGOSS?

NGOSS (Figure 1) is a comprehensive, integrated framework for developing, procuring, and deploying operations and business support systems (OSSs/BSSs) and software. It is available as a toolkit of industry-agreed specifications and guidelines that cover key business and technical areas including:

●  eTOM Business Process Map: An industry-agreed set of integrated business process descriptions, created with today’s customer-centric market in mind, used for mapping and analyzing operational processes. (笔者理解:流程)
●  Shared Information/Data (SID) Model: Comprehensive,standardized information definitions acting as the common language for all data to be used in NGOSS-based applications. A common information language is  the linchpin in creating easy-to-integrate software solutions.(笔者理解:数据模型与接口)
●  Technology Neutral Architecture: Key architectural guidelines and specifications to ensure high levels of flow through amongst diverse systems and components. 
●  Compliance and Conformance Criteria: Guidelines and tests to ensure that systems defined and developed utilizing NGOSS specifications will interoperate. 
●  Lifecycle and Methodology: Processes and artifacts that allow developers and integrators to use the toolset to  develop NGOSS-based solutions employing a standard approach.

(Figure 1)

这种统一的流程、统一的数据模型、统一的接口、中立的技术架构、兼容性测试、生命周期与方法论,对于运营商与厂商的好处就不言自明了。

2.什么是eTom

At the overall conceptual level (Figure 3), the Business Process Framework can be viewed as having the following three major process areas:

●  Strategy, Infrastructure, and Product (SIP) covering planning and lifecycle management 
●  Operations covering the core of day-to-day operational management 
●  Enterprise Management covering corporate or business support management

The Level 0 Framework also includes views of functionality as they span horizontally across an enterprise’s internal  organizations: 
●  Market, Product, and Customer: High-level view of the market and the enterprise’s offerings 
●  Service: Product components developed by the enterprise 
●  Resource (Application, Computing, and Network): Consumed in the production of the Service 
●  Supplier/Partner: Providing products and services to the enterprise for the production of the Service

A more detailed view of the Enterprise processes is presented in the Level 1 eTOM model (Figure 4). The model  shows seven end-to-end vertical process groupings required to support customers and manage the business. 
Among these vertical groupings, the focus of eTOM is on the core customer operational processes of Fulfillment, Assurance, and Billing (FAB).

Operations Support and Readiness (OSR) is the “back-office” environment that  enables support and automation for FAB. The SIP processes do not directly support the customer and they include  the Strategy and Commit and the two lifecycle process groupings.

The next three figures show the Level 2 core processes for the Operations, SIP, and Enterprise Management areas. 
Each core process is generally part of one verticalLevel 1 grouping and also one horizontal process grouping. In 
some cases a Level 2 process is “stretched” across several Level 1 vertical groupings because the process 
concerned is needed in several Level 1 verticals.

This procedure can be continued  at lower levels as required. The eTOM layers can generally be described as following:

●  Level 0: Business Activities that distinguish operational customer-oriented processes from management and 
strategic processes 
●  Level 1: Process Groupings including business functions and standard end-to-end processes 
●  Level 2: Core Processes that combine together to deliver service streams and other end-to-end processes 
●  Level 3: Tasks and associated detailed “success model” business process flows 
●  Level 4: Steps and associated detailed operational process flows with error conditions and product and
geographical variants (where required) 
●  Level 5: Further decomposition into operations and associated operational process flows where required

3.Using eTom

The focus of eTOM is on the business processes used by service providers, the linkages between these processes, 
the identification of interfaces, and the use of customer, service, resource, supplier/partner, and other information by 
multiple processes. eTOM represents an industry consensus on the service provider processes, which hasbeen 
harmonized across the global scene and is based on TM Forum Member contributions. It is allowable, andindeed 
expected, that this will mean that eTOM must be tailored and/or extended for use within an individual company.

eTOM can be used to analyze existing organizational processes in order to discover gaps, to eliminate duplication 
and to optimize processes.The two main techniques used to analyze existing organizational processes are through process interaction and process flows, illustrated in Figures 8 and 9.

Figure 8不贴图了,其实process interaction就跟UML的collobration一样,没有次序,只能看出来谁的交互比较多;Process flow就是流程图了,类似于UML的sequence,不过一般用泳道图,这样能够清晰的看出来每个功能点属于哪个模块:

4.eTOM and ITIL

粗浅的理解,ITIL因为整个IT及ICT行业,所以比较宽泛,而eTom更加针对ICT细化,所以eTom可以借鉴部分ICT的流程:

The conclusions of the joint eTOM-ITIL® team are that the two frameworks are compatible, complementary and  mutually supportive. eTOM and ITIL® can be integrated by using ITIL® best practices to specialize eTOM processes.

NGOSS与eTom简介相关推荐

  1. NGOSS的一点简单概念

    NGOSS(Next Generation Operational Support Systems)是由TMF(Tele Management Forum)提出的,他用于电信领域,是构建下一代OSS/ ...

  2. TMF、NGOSS介绍

    TMF全称:TelecomManagement Forum(电信管理论坛) TMF提出了NGOSS模型,包括了eTOM.TAM.SID和TNA四个框架模型, 被国际电信运营商和设备提供商以及电信运营支 ...

  3. 【TMF eTOM】业务流程框架介绍

    TMF文档版权信息 Copyright © TeleManagement Forum 2013. All Rights Reserved. This document and translations ...

  4. etcd 笔记(01)— etcd 简介、特点、应用场景、常用术语、分布式 CAP 理论、分布式原理

    1. etcd 简介 etcd 官网定义: A highly-available key value store for shared configuration and service discov ...

  5. Docker学习(一)-----Docker简介与安装

    一.Docker介绍 1.1什么是docker Docker是一个开源的应用容器引擎,基于Go语言并遵从Apache2.0协议开源 Docker可以让开发者打包他们的应用以及依赖包到一个轻量级,可移植 ...

  6. 【Spring】框架简介

    [Spring]框架简介 Spring是什么 Spring是分层的Java SE/EE应用full-stack轻量级开源框架,以IOC(Inverse Of Control:反转控制)和AOP(Asp ...

  7. TensorRT简介

    TensorRT 介绍 引用:https://arleyzhang.github.io/articles/7f4b25ce/ 1 简介 TensorRT是一个高性能的深度学习推理(Inference) ...

  8. 谷粒商城学习笔记——第一期:项目简介

    一.项目简介 1. 项目背景 市面上有5种常见的电商模式 B2B.B2C.C2B.C2C.O2O B2B 模式(Business to Business),是指商家和商家建立的商业关系.如阿里巴巴 B ...

  9. 通俗易懂的Go协程的引入及GMP模型简介

    本文根据Golang深入理解GPM模型加之自己的理解整理而来 Go协程的引入及GMP模型 一.协程的由来 1. 单进程操作系统 2. 多线程/多进程操作系统 3. 引入协程 二.golang对协程的处 ...

最新文章

  1. linux shell seq 序列生成命令 可用于for循环 简介
  2. sublime text使用小技巧
  3. 一条进程的栈区、堆区、数据区和代码区在内存中的映射
  4. Python入门100题 | 第074题
  5. hust1347(归并排序求逆序对)
  6. linux su切换用户提示Authentication failture的解决办法
  7. winform + INotifyPropertyChanged + IDataErrorInfo + ErrorProvider实现自动验证功能
  8. ZOJ 3981 2017CCPC秦皇岛 A:Balloon Robot
  9. 三菱q系列特殊继电器一览表_2020山西三菱Q系列PLC模块回收购销
  10. MS08067 第一期 “恶意代码分析”实战班 12.17号开班~
  11. sql查询每个班级的前三名
  12. 软件工程入门基本知识
  13. 激光雷达是什么?为什么移动机器人必不可少?
  14. 通过PS抠出透明的玻璃瓶
  15. Android 软件行为监控系统 的原理 主要是利用binder机制原理添加一个filter
  16. edi许可证和ICP区别
  17. [codechef] TOURISTS
  18. Ubuntu终端Terminator的安装与配置使用
  19. 【Java EE】从零开始写项目【总结】
  20. moses 编译_moses工具的配置详解

热门文章

  1. JS10day(api 阶段性完结,正则表达式简介,自定义属性,过滤敏感词案例,注册模块验证案例)
  2. 24届近5年华南理工大学自动化考研院校分析
  3. [转] 《我的助理辞职了》
  4. 程序员如何开启职业第二春?年薪50w+的金融IT岗了解一下
  5. oracle dual nextval值,oracle序列参数:nextval和currval
  6. 网页JAVASCRIPT常用命令
  7. mysql tee_shell中执行 mysql 使用tee 返回执行结果
  8. 《Beauty of Mathmatics - 数学之美》的简单总结与推荐
  9. 网络双星-XML与Java技术
  10. 企业如何建立商业信用邓白氏信用等级?