Those of you familiar with TM Forum are already quite familiar with the Frameworx enterprise architecture model. It’s as close as we get to a standard used across the OSS industry.
Frameworx consists of four main modules, with eTOM, TAM and SID being the most widely referred to:
But there’s a newer weapon in the TM Forum arsenal that appears to be gaining widespread use. It’s the TM Forum Open API suite, which has over 50 REST-based APIs as well as having many more under development. This link provides the full list of APIs, including specifications, swagger files and postman collections.
The following diagram comes from the Open API Map (GB992) (accurate as of 9 Jan 2018).
It’s well worth reviewing as I think you’ll be hearing about TMF642 (Alarm Management API) and all its sister products as commonly as you hear eTOM or SID mentioned today.
Have you ever had an OSS or BSS project that’s impacted by poor data quality? The problem of data integrity gets raised on almost every
“One of my favorite things about designing software is designing the defaults. The defaults define the experience for everyone out of the box. And, therefore,
Have you ever been tasked with mapping out the processes for the telco you work for? Either as a way of documenting current state, or
In the last week alone, I’ve had two potent reminders that the world of OSS is simply (pun intended) too complex. This manifests in many
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
