This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.scrm-wg/wiki/M.3050SeriesEnhancedTelecomOperationsMap at Thu, 03 Nov 2022 00:17:19 GMT SourceForge : View Wiki Page: M.3050SeriesEnhancedTelecomOperationsMap

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Wiki Pages Project: scrm-wg     Wiki > M.3050SeriesEnhancedTelecomOperationsMap > View Wiki Page
wiki1515: M.3050SeriesEnhancedTelecomOperationsMap

STANDARD

1. The name of the specification.

M.3050 series: Enhanced Telecom Operations Map

2. A short statement (<100 words) of the purpose and function of the specification.

This Recommendation is equivalent to the Enhanced Telecom Operations Map® (eTOM) version 7.0 developed by the TeleManagement Forum (TMF) as a reference framework for categorizing all the business processes that a service provider will use. It is a multipart document with the following structure:

  • M.3050.0 - eTOM - Introduction
  • M.3050.1 - eTOM - The Business Process Framework (TMF GB921 Release 7.0)
  • M.3050.2 - eTOM - Process Decompositions and Descriptions (TMF GB921 Addendum D Release 7.0)
  • M.3050.3 - eTOM - Representative Process Flows (TMF GB921 Addendum F Release 4.5)
  • M.3050.4 - eTOM - B2B Integration: Using B2B Inter-enterprise integration with the eTOM (TMF GB921 Addendum B Release 6.1)
  • M.3050 Supplement 1 - eTOM - An Interim View of and Interpreter’s Guide for eTOM and ITIL Practicioners (TMF GB921 Application Note V Release 6.0)
  • M.3050 Supplement 2 - eTOM - Public Business Operations Map (BOM) Application Note (TMF GB921 Addendum C Release 4)
  • M.3050 Supplement 3 - eTOM to M.3400 Mapping
  • M.3050 Supplement 4 - An eTOM Primer (TMF GB921 Addendum P Release 4.5)

3. The version number (or other distinct identifier) of the most recently approved version of the specification.

M.3050.x-2007

4. If the specification is part of a group of explicitly related specifications from the same source, the name of the group of specifications.

NGN Management

5. URI for the normative text of the specification.

www.itu.int/rec/recommendation.asp?type=products&lang=e&parent=T-REC-M


SOURCE

6. The name of the SDO that generated/authored/hosted the specification.

ITU-T (Study Group 4)

7. URI for the SDO.

www.itu.int/ITU-T/studygroups/com04/index.asp

8. The level of approval that the SDO has conferred on the specification as described by the SDO's process.

Approved

9. The language or languages in which the specification is available.

English initially, Spanish, French, Arabic, Chinese, Russian


SUBJECT

10. Which of the ITU-T TMN FCAPS model layers does the specification's functionality address?

(http://en.wikipedia.org/wiki/FCAPS, http://www.futsoft.com/pdf/fcapswp.pdf)
  • Fault Management: Fixing broken resources.
  • Configuration Management: Controlling a resource's operational parameters.
  • Accounting Management: Recording and analyzing resource use.
  • Performance Management: Controlling speed and efficiency of resource use.
  • Security Management: Controlling access to resources.

12. Where does the specification directly operate, as among the layers defined in the ISO Open System Interconnect (OSI) model?

(http://www.looselycoupled.com/opinion/2003/saruk-osi-infr0905.html )
  • Physical layer
  • Data link layer
  • Network layer
  • Transport layer
  • Session layer
  • Presentation layer
  • Application layer.

13. Which of the following (CIM based) functional areas does the model of the specification address?

(http://www.dmtf.org/standards/cim/)
  • Policy
  • Management Infrastructure
  • Physical Networks
  • Logical Networks
  • Physical Systems
  • Logical Systems
  • Physical Devices
  • Logical Devices
  • Users
  • Security
  • Support

OPTIONAL

14. The level of approval of the specification in this generic lifecycle taxonomy:

  • Approved

15. URI for the applicable SDO's patent and copyright rules, if any, applicable to development and use of the specification.

N/A

16. URI for the SDO's posting location, if any, for notices from participants or individuals regarding claims under number 15.

N/A

17. Interoperability, conformance, or certification test activity for the specification (by owner name or URI).

N/A

18. Known implementations of the specification (by owner name or URI).

N/A

19. A list (or URI pointer to same) of the other specifications that are normatively referenced in the specification.

N/A

20. A list (or URI pointer to same) of the other specifications that are explicitly referenced in the specification (except the ones listed in number 19).

N/A

21. A list (or URI pointer to same) of otherspecifications with which the specification may (speculatively) interoperate or act in complementary, compatible fashion.

N/A

22. A list (or URI pointer to same) of other specifications. (Whether or not substitutable.)

Equivalent to TMF's Enhanced Telecom Operations Map 4.0

 




The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.scrm-wg/wiki/M.3050SeriesEnhancedTelecomOperationsMap at Thu, 03 Nov 2022 00:17:19 GMT