ENTERPRISE ARCHITECTURE (EA)

Introduction

Enterprise Architecture enables the accurate detailing of an organization's structure and operations; effectively creating an 'overlay' of its technology, business processes, business rules and its people, and defining how the interconnections between these relate.

Through the development of such a 'business blueprint', the enterprise architect can assist and guide an organization's strategy development and play a crucial role in mapping business future vision to effective enterprise change.

The Enterprise Architecture Project utilizes a central repository for the collection of all architecture related artefacts, facilitating the reuse and reference of components. Enabling the business to effectively document and maintain the process, business rules and other relevant components to support the execution cycle of new products and services and also the enhancement of existing products and services.

The repository also contains artefacts collected by other business units, including the standard processes (defined by architecture working groups) and business rules, enabling a reuse of critical information to support business and IT decisions.

The repository is an ecosystem, enabling the automated generation of documentation, supporting compliance and audit objectives to enhance the capability to comply with international standards, such as ISO 9001:2, ISO 20000 and other industry-relevant organizational certifications.

Development on the repository ecosystem enable the business to create viewpoints against the component-based capability models.

Strategic Alignment and Support

The Enterprise Architecture Strategy

  1. Speed of Execution – The project collects all Business and Technical Processes and standardizes them, reducing the time for the ITS Architecture team to produce impact assessments, which in turn reduces the time to develop or enhance products and services.
  1. One Way of Working – The EA knowledge base is a collective knowledge base, thus executions in other business units may be leveraged to reduce execution time and enterprise knowledge may be leveraged to create advantage.
  1. Transforming the Operating Model – As the Lines of business diversify into Digital, Enterprise Business and Financial Services, EA Services provides standardized processes for managed assimilation into the existing operating models.
  1. Improved Governance – Visibility of risk areas, business rules and possible legislative exposures within existing business process and offerings to align with regulatory compliance and the reduction or mitigation of potential risk areas.

Background and Approach

The A1L Enterprise Architecture approach is based off four (4) years of partnering with MTN, within MTN Group, MTN South Africa, MTN Nigeria, and MTN Irancell, Sasria, Telkom, Nashua, King Abdullah bin Abdulaziz university hospital, Sidra Medical & Research Centre and has produced a way-of-working that eliminates the heavyweight approach of TOGAF and an EA practice and implements Enterprise Architecture in a pragmatic, results-driven manner that is contextualised within the Enterprise Capability Orchestration (ECO) model.

The approach allows flexibility to choose what modules are needed for the level of maturity of the solution and enterprise architecture practices.

The modular approach of ECO builds upon previously developed intellectual property and operationalises solutions and measures to ensure that the enterprise architecture practice is not simply an academic exercise.

Approach

The Enterprise Architecture project is divided into five (5) maturity phases, whereby each phase builds upon the improvements and the components or artefacts developed within the previous phase.

The maturity model represents a macro process that develops both the organisation and the organisational knowledge to produce quantifiable and measurable value within the organisation, its people, technology and processes. The organisation maturity develops through the phases to ensure long-term value assurance.

The maturity model applies to an Enterprise Architecture subject area, as such multiple subject areas may be within different stages of the maturity cycle.