Open APIs

 View Only
  • 1.  TMF for distinct type of service request.

    TM Forum Member
    Posted 17 days ago

    Hello everyone.

    We are designing an OpenAPI for creating service requests. However, in our CRM, we manage different types of service requests, such as product orders, claims, problems, etc.

    In this case, is TMF 641 used? Or should we design a TMF for each entity? For example, TMF622 for service requests associated with products, TMF656 for service issues, etc.

    We appreciate your help. Best regards.

    Soledad.



    ------------------------------
    María Soledad Alfonso
    Entel Chile
    ------------------------------


  • 2.  RE: TMF for distinct type of service request.

    TM Forum Member
    Posted 16 days ago

    Hi María,

    It depends on what you mean by "service request."

    If you aim to trigger a service order towards a software component capable of processing such requests, you should use TMF641. If instead you want to log an issue associated with a service, you would need to use TMF656, and so on.

    I believe the first step you should take is to identify which actions or processes you intend to implement in your system (using eTOM as a reference), which business entities are involved (based on SID), and which software components will be responsible for managing these entities and participating in the processes (keeping in mind the ODA components).

    With this overall map in mind, you'll be able to determine which APIs are needed to interconnect those components.

    If you can share a more concrete example, I might be able to provide more specific guidance.

    In any case, I hope this helps.

    Best regards,



    ------------------------------
    Abel Ruiz Huerta
    alvatross
    ------------------------------