OSS are there to do just that – support operations. So as OSS implementers we have to do just that too.
But as the old saying goes, you get back what you put in. In the case of OSS I’ve seen it time and again that operations need to contribute significantly to the implementation to ensure they get a solution that fits their needs.
Just one problem here though. Operations are hired to operate the network, not build OSS. Now let’s assume the operations team does decide to commit heavily to your OSS build, thus taking away from network ops at some level (unless they choose to supplement the ops team).
That still leaves operations team leaders with a dilemma. Do they take certain SMEs out of ops to focus entirely on the OSS build (and thus act as nominees for the rest of the team) or do they cycle many of their ops people through the dual roles (at risk of task-switching inefficiency)?
There are pros and cons with each aren’t there? Which would you choose and why? Do you have an alternate approach?Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email