Generic selectors
Exact matches only
Search in title
Search in content
Search in posts
Search in pages

Products, CFS and RFS

This topic contains 1 reply, has 0 voices, and was last updated by  Wallis Dudhnath 7 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #70238 Reply

    Wallis Dudhnath

    Products, CFS and RFS

    At the time of writing a number of traditional Communication Service Providers (CSPs) are “morphing” into total digital players. This is seen as a means to address the dynamic, competitive ICT Market and to allow Value Added OTTs (VAOTTs) to be a part of the CSP’s value chain. As King Canute (Cnut) “discovered” it is somewhat a challenge to hold back the tide. The same is being seen with the competitors that are snapping at the heels of the CSPs.

    To help CSPs, the adoption of a Catalog will help by providing a much needed “truth table” of what Products and Resources will be required to entertain and deliver Products to the end customer (e.g. Retail, Wholesale, etc..). A Catalog helps with Product creation and the end to end lifecycle of Products supported by the CSP.

    A central and unified Catalog is an enabler facilitate the consolidation of the “home grown” IT estate (e.g. numerous Databases, manual processes, non-standard technologies, etc..) and to serve as a catalyst for further business growth by offering flexibility with Product creation and deployment.

    From a high level perspective, a Catalog can be split into the following parts:-

    -Product (e.g. Sales Catalog, Product Catalog, Services Catalog, etc..) that highlights what can be ordered and consumed)

    -Services, (e.g. configuration and technical details) and
    Resources (e.g. what needs to be setup with the Network)

    The Services are basically Customer Facing Services (CFS) and Resource Facing Services (RFS). Generally, CFS is tied, or linked, to a Product and RFS is connected with the required resource.

    VBR/ Wallis Dudhnath

    Reference:

    TMF Forum and the SID (Shared Information Data) model

    #70239 Reply

    Wallis Dudhnath

    eTOM/SID/TAM:

    Below is a high level description of eTOM, SID and TAM.

    -Business Process Framework (earlier known as eTOM – enhanced Telecommunication Operation Map) captures the key and typical business processes that a Communication Service Provider (CSP) will support so that they can become “digital” CSP with agile qualities.

    At a high level there is “operations” and this covers: Fulfillment, Assurance and Billing (FAB). FAB processes ensure that Services can be delivered and that they can be charged / billed (usage).

    -Shared Information Data (SID): A model that abstracts information in the Network. Promotes integration.

    -Telecommunication Application Map (TAM): Description of the software stack for the OSS/BSS environment. Helps to list the software artifacts that are used with the AS-IS software stack.

    -Integration Framework: API Gateways and Enterprise Service Bus (ESB) / Enterprise Application Integration.

    VBR/ Wallis Dudhnath

Viewing 2 posts - 1 through 2 (of 2 total)
Reply To: Products, CFS and RFS
Your information:




<a href="" title="" rel="" target=""> <blockquote cite=""> <code> <pre> <em> <strong> <del datetime=""> <ul> <ol start=""> <li> <img src="" border="" alt="" height="" width="">