Open APIs

Hi all,
Quick clarification: Do vendor NMS/EMS expose TM Forum Open APIs (e.g., TMF639, TMF642, TMF628), or is it industry best practice to always implement them via a mediation/integration façade (like ODA suggests)?

Thank you in advance !

Concept of EMS i.e. device level management is not used in more modern ITU-T TMN Architecture e.g. M.3041 and M.3080.
There is a move in modern networking equipment suppliers towards network Service level integration . For integrating with legacy EMS solution one can use a legacy pattern of adaptors /Facade.  However the target is NMS Intent based interface which are in some cases developed using IETF/ BBF/3GPP stnadards and can use TM Forum Intent APIs 

we have studied this Area in ODA production and intiel thoughts are captured in :

• TR313A Business Assessment of Industry Adoption Barriers to ODA Production v1.0.0
• TR313B Technical Assessment of ODA Production Challenges v1.0.0
• TR313 Architecture options for Integration with Resource Technology-Specific Domains v1.0.0
• TR313C ODA (Production) Components for NaaS Evolution (Submit for Publication)

which focus on intent and controller based solutions

For TM Forum members there is an early  draft under the ODA Production team looking at Legacy aspects

TR ..... Working Paper: Legacy and non TM Forum API Network Integration Options - Components and Canvas - TM Forum Confluence

in summary the challenge is that some of the simpler technical solution are brittle and the business case for their implementation is often not there. It is usually deployment context specific