Scope of the platform work stream
Our goal is to describe architectural and design principles that are needed to reach a “Zero Outage” IT implementation which delivers value to customers through uninterrupted uptime.
In today’s economic environment, it is a must to develop solutions that meet growing customer expectations and business requirements for high availability, and avoiding the increasing costs of service interruptions, both direct and indirect, like damage to brand reputation.
The platforms on which the services are being delivered require to follow specific policies along all the phases of the Zero Outage Value Map, starting from a proper architecture (Plan), to a correct implementation (Build) and deployment (Deliver), to well managed operations (Run), to guarantee the level of resilience, security and availability that achieve the Zero Outage quality goal.
We help you build IT platforms that are there when you need them.
The Platform team joins perspectives and expertise of leading IT industry suppliers and major service providers, that collaborate to define requirements, recommendations and best practices that allow to run End-to-End an IT world of increasing complexity.
We do so through a holistic approach that provides practical guidance across the technology stacks and integrates that with Processes, People and Security elements.
The Platform Work Stream aims to remain vendor and technology agnostic, maintaining the focus on the Zero-Outage end goal, defining the requirements of the different IT-elements and how they should be co-operatively working together.
Structure of Platform Work Stream Content
The Platform Work Stream framework “slices” IT implementation in multiple technology layers, and within each layer in different constituting elements, which are called “building blocks”. Besides detailing for each of these “building blocks” what are the requirements that need to be met to contribute to a comprehensively compliant ZO implementation, we also aim to describe the interactions between building blocks and the requirements that these interactions need to respect to maintain an overall compliant infrastructure. Each layer has dependencies, on “lower” and/or “higher” layers, plus dependencies within the layer itself.
We recognize that a critical element in achieving the ambitious goal of a Zero Outage implementation is around having a very accurate monitoring of the landscape of the implementation because one can only can control what can be measured.
Additionally, applications need to be designed with business requirements in mind in order to achieve the desired level of ZO compliance.
Each of the above topics are expanded in the sections that are referred in the menu on the right side of this web page.