Open APIs

Expand all | Collapse all

Migrating to TMF620 - Catalog Management

  • 1.  Migrating to TMF620 - Catalog Management

    Posted Nov 23, 2020 12:52

    Good day Members!

    We are trying to adapt with TMF620's spec for our APIs in Catalog Management. Right now, at the analysis stage, we explored the TMF's specs, finding it having a different architecture (Obviously) than our current system. I have few questions regarding to it

    1. Since we already have an well established Catalog model & APIs (In-house), what would be the best way to adopt TMF's specs? Meaning do we need to completely change our system's architecture or just the API  part (I know it sounds ridiculous but we want to reduce the impact of existing architecture) ?
    2. will changing Catalog would require complete revamp of the underlying ecosystem (business process & Other Management systems like quoting, ordering, billing, etc.) or just APIs?
    3. We have some business process which can't be eliminated even if we follow TMF's specs and it would lead to either extend on top of TMF spec or to not use some model from it.
    4. Being said, how the TMF's certification process does the evaluation? I have read through the process and conformance docs to understand it. But is it limited only to API or does it evaluates the complete architecture of the implementation system ?

    Eswar Babu Kutuva Naraynamoorthy
    Verizon Communications

  • 2.  RE: Migrating to TMF620 - Catalog Management

    TM Forum Member
    Posted Nov 24, 2020 08:51
    This appears to be a duplicate post, please keep the discussion on the other post here.

    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.