Automation is about using machines / algorithms to respond faster than humans can, or more efficiently than humans can, or more accurately than humans can… but only if the outcomes justify the costs. When it comes to automations, it’s a case of, “just because we can, doesn’t mean we should.”
The more complex the decision tree you’re trying to automate, the higher the costs and therefore the harder it becomes to cost-justify. So the first step in any automation is taking a lateral thinking approach to simplifying the decision tree.
This recent post highlighted a graph from Nokia’s Bell Labs and the financial dependency that network slicing has on operational automation:
Let’s use the Toyota Five Whys technique to work our way through the implications of this:
Statement 0: As CSPs, we need to drastically reduce complexity in the processes / decision-trees across our whole organisation.
Why 1? So that we can apply significant levels of automation
Why 2? So that we can apply technologies / techniques such as network slicing or virtualisation that are cost-justifiable
Why 3? So that we can offer differentiated, premium services
Why 4? So that our offerings don’t become commodities
Why 5? So that we retain corporate profitability to return to shareholders and/or invest in further interesting projects
I love that we’re looking to all number of automation technologies / techniques to apply to our OSS. However, we’re bypassing the all-important statement 0. We’re starting at Why 1 and partially missing the cost-justifiable part of Why 2. If our automation projects don’t prove cost-justifiable, then we never get the chance to reach whys 3, 4 and 5.Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email