DaaS Implementation

How do I implement Data as a Service (DaaS)?

Data as a Service (DaaS) is a fundamentally different approach to building out business solutions. The implications in how we implement solutions are both subtle and profound.

By eliminating much of the cost, effort and risk of developing application components we have fundamentally shifted the Functionality/Software return on investment calculation. What we need to do now is look holistically at the business to change the way we utilise IT to create sustainable competitive differentiation.

But we are different!

How a business goes to market, how a product works, how a business differentiates itself is unique in many ways. That differentiation for most organisations should stop at the IT level.

Most business solutions run on servers that are connected to a network. They store their information in databases or file shares. They share information with other applications or third parties. They run office applications including email. At best, they have implemented High Availability solutions and have created Disaster Recovery Plans and Sites.

For most businesses, it is no longer necessary to create a unique solution architecture to support their operations. Indeed, creating a unique architecture can increase the cost and risks associated with solution development and operation making it harder to recruit and train staff.

Over the years the IT industry has coalesced around a few core architectural designs and best practises for the creation of business solutions. Be warned - best practices aren’t simply a pick and mix buffet – you need to ensure that you adopt a coherent approach that spans the whole organisation from strategy to operation.

Don’t reinvent the wheel

Pick a mature DaaS implementation framework as a starting place and work from there. The framework should cover the following areas:

  • Strategy – Covers the alignment of business and IT and ensures that the IT team is properly supporting the creation of business value.
  • Architecture– Covers the architectural design, guidelines, standards and processes for the creation of IT solutions to support business operations.
  • Transformation– Ensures that IT effort of focused on the delivery and operation of solutions to maximise business value.
  • Components – Ensures that IT components are developed and reused consistently within business solutions to minimise the effort, cost and risk of software development.
  • Implementation– Ensures that all new software is developed efficiently and effectively within the agreed architectural framework.
  • Operation – Ensures that the IT solutions are available to support the business operations.

Adopting a mature set of industry best practises makes it easier to onboard new staff and reduces operation risks associated with attrition of “key employees”.