SDDC Service Discovery Workshop

Summary of VMWare's Digital Boardroom - Thursday 30th April 2020

Like Comment

The SDDC Service Discovery Workshop is a service provided by VMWare to multiple customers globally with the goal of mapping business priorities with SDDC and cloud services.


Why SDDC Service Discovery

The Organisation of the Future

VMWare works with a lot of customers worldwide and they all have something in common; we are living in a very rapidly changing world and it is becoming harder to identify competitors. If any companies want to survive today, they need to become fast and agile and embrace new technologies with maintaining sustainability.


VMWare Software Driven Approach

Everything VMWare does is software defined, from desktops to data centres to management and the approach has proven itself to be the most important approach for next generation businesses as it becomes more manageable and agile as we move towards new applications and infrastructure. It is the key for everything we do today in the data centre, which is no longer a product but an architecture or concept.


‘The future of IT is both revolutionary and expected. It is the best business response to unrelenting forces and goes toward the long-term survival of the firm in a market where digital excellence will be both table stakes and critical to success.’ Forrester Research 2019


Goals & Outcomes

The goal of the workshop is to help organisations create a service factory that will enable fast service creation and delivery, aligned to business outcomes. The aim is to provide the customer with a more agile architecture, more stable operations, steps to create a service life cycle methodology and/or more sustainability and resiliency within their business.


Cloud Architecture Impact on IT

Consumption Evolution- The Operational Model needs to evolve

Not so long ago everything used to be done manually in the organisation. During the last decade we have been trying to automate everything which was a nice idea, but what has been observed is that as far as you can go with automation, the complexity of it is becoming more of a burden than a benefit to the organisation as the management of it grows.


Then in the last couple of years, we are starting to see that infrastructure is being reinvented in order to deal with the huge demands. So we are starting to see declared systems, where we can declare states we want systems to be in and let the different components configure themselves to the desired outcome.


Cloud Operation Model- Run it like a Power Plant

Many years ago we would operate infrastructure by fixing whatever is broken and simply Keep the lights on. Today, the assumptions that we have is that consumption rates are unknown and our performance relies on capacity changes and they must be balanced. Consumers expect a product to always be readily available with unlimited capacity and performance with all the services they need at all times.


And from an IT perspective, they still need to manage everything as they always have, so organisations need to work out how that can achieve all this to have an effective operating model. 


This model we strive for closely resembles that of a power plant; you have a lot of consumers who can access whenever they want and the plant’s main aim is to provide the resource to everyone as everyone expects it to be available at all times. We know it doesn’t work that easily, but this model seems to work in principle.


The Service Factory

The Service Factory outlines how to mass produce products versus how to customise allowing organisations to focus on how to service the customer rather than simply looking at what products they already have. It can allow for prototypes to be constructed quicker allowing staff to fail fast and learn and succeed quickly.


By doing this factories can serve as real-time demonstrators of the technology and systems the company sells and can help customers with installation, maintenance and troubleshooting, enhancing customer confidence.


How to Build a Service Factory

The key thing is to focus on what the customer really needs, focus on the key points that have value for those customers and then take things that were done well manually which we know how to do well and automate it if possible. Examples of this include:

  • Development environment aaS
  • Production server aaS
  • Data centre capacity on demand
  • Archives for future support


SDDC as a Foundation for a Service Factory

In the past computing, automation, storage, networking and security would be siloed and if a customer had a request for a certain silo, these can be completed very quickly. However, if a customer asked for something larger covering several silos, they also need to talk to each other as they work on their tasks to be in agreement and know who is responsible, which can take much longer and lead customers to look outside the organisation, which is where having these things in a cloud can speed up the process.


The SDDC model puts those small API hooks between the silos and teams so they can speak to each other and sync much quicker, making each silo a service provider that owns what they provide creating APIs to the consumers and the other silos. So if a user wants something, the service designer will design a plan, it will go to the providers to work on their tasks and the process is sped up dramatically.


SDDC as a Service Factory Platform

  • Everything within the platform must be abstracted to software. If it cannot be software defined, it cannot be part of the assembly line as it cannot be controlled. This means that proxies or connectors may need to be created that can define things remotely.
  • Everything needs to be service and outcome-oriented. If it doesn’t deliver something as a service, there is no telling if it works or has value for someone
  • Out of the box services for legacy, current and future applications may be required to be able to expose problems before going to the customers


Business Use Cases & Cloud Services

The business and IT will have different priorities and roles within the organisation and so when it comes time to make the big decisions, it can feel like the two sides are speaking different languages making it difficult to get things done.


The business value pyramid can help organisations discover what the goal of a business is, how we can help them understand the initiatives and then create a process to allow this to happen over and over and much quicker.


Use Case Definition

The three elements a use case must contain:

  • Actor- The user
  • System- The process that is required to reach the outcome
  • Goal- The successful user outcome


Additional elements may include:

  • Stakeholders- Those who have an interest in how the system turns out, even if they are not direct users
  • Preconditions- Things that must be true before a use case can run
  • Triggers- Events that occur for a use case to begin


Having a good use case can provide a list of goals so it is clear early on what the system may look like, what needs to be achieved, how much it will cost and what can go wrong along the way, making it bulletproof before moving forward as it becomes more complex.


Service Design Process

  • Analyse the customer needs and stick to them to avoid being sidetracked
  • Plan the implementation thoroughly to keep track of costs, define boundaries and stay on course
  • Make sure it is a continual process which can be reviewed and improved over time



  • The Cloud Operation Model (The Power Plant)
  • Use Case & Service Definition
  • Building a Service Factory
  • Common & Out of the Box Services
  • SDDC Architecture
  • Build to Last


To learn more about all our upcoming events, click here.

Global CIO Institute

Administrator, GB Intelligence Ltd

713 Contributions
1 Following