“If destruction be our lot, we must ourselves be its author and finisher.”
Flow-through provisioning is a wonderful thing. It usually takes a lot of effort to design the data model so that all the pieces of the jigsaw puzzle line up for each and every new service provisioned by your awesome product.
But the oft forgotten Cinderella at this dance is actually the flow-through deactivation process. It is this process that is often even harder, but usually more valuable to the CSP in terms of the time it saves. Tearing the service down may require you to deactivate just one link in the chain, so it doesn’t sound too hard at first glance. However, the key to the deactivation process is releasing all resources back into the pool for auto-provisioning of the next service.
In my early days as a SME (network Subject Matter Expert), I was focused only on the A in MACD (Moves, Adds, Changes, Deletes). I later found out that the D was often actually the bigger achievement.Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email