Minimum Viable Path (MVP)

“…the more data you cross-link into a chain, the more likely you are to have broken chains.”

The diagram above provides a visual perspective on yesterday’s blog.

Circuit Level 1 shows the minimum data that allows the service activation to occur (although it relies on all of the infrastructure to be set up prior). The downside is that there isn’t much information available for assurance purposes. The field techs and network operations teams have to do all the fault diagnosis work.

Circuit Level 3 is the “perfect” data set that shows all of the hops / data-points (ie the black dots) that make up the service. Perfect for assurance, but a massive challenge for the OSS teams who have to ensure that every link in every chain lines up perfectly.

With the right OSS tools, you can start at Level 1 and then add extra data points as needed (as per Level 2). But not all tools provide this type of in-fill functionality.

Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email

2 thoughts on “Minimum Viable Path (MVP)

  1. This is where GIS modelling of both Physical Bearers with External and Internal views and Logical Network Information, with Service Mgmt links to contracted SLA/OLA’s. This should include contracted Diversity Links with Standby Status and points of contact.

  2. Hi Chris

    Absolutely right!! The outside plant components managed within GIS frameworks is the hardest to “perfect” because it doesn’t have a native programmatic interface to run audits across. Then aligning with inside plant and services becomes a huge challenge. Sounds like you’ve already had lengthy experience wrestling with this beast!

Leave a Reply

Your email address will not be published. Required fields are marked *