Resources · Operating model

Infrastructure Operating Methodology

The infrastructure industry's shift from PPDIOO to DevOps has stalled at configuration management — the article argues for a new 'NetOps' or 'InfraOps' methodology that takes the best of both models and digitizes the full infrastructure lifecycle with visibility for providers and clients alike.

1 min read·From the blaZop journal

The shift in operating methodology

Infrastructure industry has been transforming to different operating methodology to speed up the infrastructure designs/implementation/operations processes.

Historically, there has been some transformation from PPDIOO methodology (prepare, plan, design, implementation, operate, optimize) to infrastructure DevOps. However, DevOps model is very software engineering centric and therefore infrastructure engineers don't find it as an alternate to PPDIOO model.

Therefore, we need a methodology & supported system called 'NetOps' or 'InfraOps', which uses best features of PPDIOO and DevOps model and enable a new optimized methodology wherein all the steps mentioned above can be digitized and visible not only to infrastructure IT providers but also to IT clients.

Where DevOps falls short for infrastructure

So far, in most cases, DevOps in Infrastructure space has been limited to configuration management wherein infrastructure engineers have built automated configuration management systems to deploy configurations to infrastructure devices. Given, PPDIOO methodology is not 1-to-1 mapped to DevOps, infrastructure engineers still have to do the following:

The case for NetOps / InfraOps

Therefore, we need a methodology & supported system called 'NetOps' or 'InfraOps', which uses best features of PPDIOO and DevOps model and enable a new optimized methodology wherein all the steps mentioned above can be digitized and visible not only to infrastructure IT providers but also to IT clients.

If you are interested to know how blaZop platform can help?

From PPDIOO to NetOps/InfraOps

PPDIOOTraditional modelPrepare, plan, design, implementation, operate, optimize — the classic infrastructure lifecycle methodology
Infrastructure DevOpsPartial adoptionSoftware-engineering centric; in practice limited to automated configuration management for infrastructure devices
The manual gapStill on engineersBusiness-intent validation, architecture & design, configuration policies, BOM, validation, standards tracking, cost & delivery timelines
NetOps / InfraOpsProposed methodologyCombines the best of PPDIOO and DevOps; digitizes every step with visibility for IT providers and IT clients

What to remember

  • PPDIOO (prepare, plan, design, implementation, operate, optimize) is the traditional operating methodology for infrastructure.
  • DevOps is too software-engineering centric for infrastructure engineers to accept it as a replacement for PPDIOO.
  • In practice, DevOps in the infrastructure space has been limited to automated configuration management.
  • Engineers still manually handle business-intent validation, architecture and design, configuration policies, BOM management, validation, standards tracking, and cost/delivery timelines.
  • A NetOps/InfraOps methodology should combine the strengths of PPDIOO and DevOps and digitize every step, visible to both infrastructure IT providers and IT clients.

See how the blaZop platform does this — book a demo →

Keep reading