The attached template provides sample approaches to defining the naming convention for your OctopOSS.
In situations where existing naming conventions are in place in an organisation, there are many considerations to take into account and no single “best” solution exists. The attached template provides a naming convention that has room for significant flexibility for any OctopOSS as well as guiding principles to defining your own naming convention.
I like to start with a variation of ITU’s M.1400 standard, shown below, with the bottom row showing the suggested starting point.
That is, a circuit name should be:
However, there are an infinite number of variations upon this theme, not to mention having the flexibility of fitting in with existing schemes already in place within a CSP.