STAGING WIKI ---- STAGING WIKI
Collaboration Process, Guidance and Governance

Space shortcuts

Page tree

Guide Book (GB9xx):  used in cases where:

  • The document lays out a ‘core’ part of TM Forum’s approach to automating business processes. Such guide books would include the Telecom Operations Map and the Technology Integration Map, but not the detailed specifications that are developed in support of the approach.
  • Information about TM Forum policy, or goals or programs is provided, such as the Strategic Plan or Operating Plan. 
  • Information about the marketplace is provided, as in the report on the size of the OSS market

Technical Report (TR2xx): used in cases where:

  • TM Forum staff and its working teams develop and release a variety of reports and papers within the Membership. 
  • These technical reports have a broad range, e.g., review of industry standard groups and value chain market issues. 
  • Technical Reports are not generally shared outside the TM Forum membership. 

Technical Specification (TMF0xx):

This document type explores the business problem and investigates customer requirements that must be met to solve this problem. It is expected that this document will be used: 

  • To facilitate requirement agreement between Service Providers and vendor 
  • As input to a service Provider’s Request for Information / Request for Proposal (RFI/RFP—RFx) 
  • As input for vendors developing Commercial Off The Shelf (COTS) products 
  • As a source of requirements for other bodies working in this area. 

Introductory Guide/Exploratory Report (IG11xx):  

This document type is used to explore a new topic, document a point of view, or establish positioning for a market, technology or concept.

TM Forum Open API (TMF6xx & TMF7xx):  

  • This format is used for specifications that provide protocol neutral and technology independent object models (documented in UML) in support of requirements defined in TM Forum’s Business Agreements. 
  • TM Forum methodology requires use of UML to ensure as much future re-usability as possible. 
  • Information Agreements provide the UML Information Model that address a specific business problem or overall requirement.

Interface Implementation Specifications (TMF8xx):

  • This format provides the definition of interfaces among the member company elements of a Catalyst Solution. 
  • Interface Implementation Specifications are developed and issued by Catalyst project teams to document what the project did and how it was done.
  • Interface Implementation Specifications include: 
    • definition of the business problem addressed,
    • the business process(es) involved,
    • an abbreviated business requirements model,
    • an information model, 
    • the technical solution,
    • and protocol specific implementation.


TM Forum Components (TMFCxx):

  • This document aims to provide an inventory of reference ODA Component as input for ODA reference implementation blueprint. This inventory of ODA Components is specifically aimed at the software application landscape of service providers.
  • The approach taken to develop and categorize the candidate ODA components in this inventory is meant to help the design and implementation of solutions that meet the architectural design requirements of ODA.
  • The target audience is Service Provider technology managers, product & R&D managers of Software Vendors, Solution architects of Systems Integrators, Application managers of Service Providers, Independent Software developers, Equipment suppliers, and Solution Managers.
  • No labels