In order to achieve consistency, not only between the different workstreams, but also between the different complexities of prescriptive design principles vs. descriptive best practices, an architectural framework is necessary in which the individual workstreams can operate fairly independent, yet still deliver consistent outcome. This framework entails three major components:
- Zero Outage Map: structuring and describing the taxonomy of the modern IT Landscape as a holistic, end-to-end IT Value Chain, which helps guiding the development of the standard work as well as navigating through the consumption of the outcome. The remainder of this document focuses on this element.
- Functional and Information Architecture (part of Reference Architecture): translates the integrated IT capabilities described in the ZO Map towards the architectural specificity of a functional model and information model. In other words, it specifies the functions required to achieve the capabilities, the information they hold, and how the functions need to interact in order to preserve the quality and integrity of the data. The reference architecture is a frame in which many specific implementation architectures can be defined in the context of a specific provider-consumer relationship.
- Layered Model: The functions of the reference architecture implement the end-to-end delivery of services on top of IT technologies. These technologies are not independent, but organized as an interconnected stack, e.g. infrastructure typically consists of network, storage and computing layers that depend on each other. However, these connections can be very diverse and dynamically changing. Therefore it is essential to provide design principles across the stack, for which the layered model provides a fundamental and generic structure.
Graphic 1 illustrates the different elements of the Zero Outage architectural framework, how they build on each other, and the related components.