ADaM Framework - Basic Concepts
 |
To simulate the business environment, the ADaM Framework creates a universe of components. Each component resides on a ‘layer’ at a different level within the infrastructure. Layers can be further categorized into sub layers.
The paradigm being that each level of the layer structure is dependant upon the layer beneath it.
In this example, a business service is dependant upon the business processes that drive the workflow. These processes depend upon the applications that collect and deliver the data, which in turn are dependant upon the hardware on which they run. The hardware is dependant upon the network for both data routing and communication. |
The ADaM Framework supports Projects which are a collection of changes to the ‘Universe’.
Project dependencies can be identified and linked into the operational framework so that impacts to components within a project scope can be assessed collectively.
Executives can view their various initiatives in a ‘dashboard’ that provides depth of knowledge on the relationships and dependencies of a project in terms of the business landscape.
Annual initiatives such as Year End or budgeting can be assigned to multiple entities and can be integrated into the workload by utilizing the central ADaM Framework calendar component and hence create ‘frozen zones’ for operational change during such periods.
The thin client portal which is an integral part of the ADaM Framework provides access to the universe for authorizations, enquiries and reporting.
The central calendar ensures that conflicts are highlighted, and full visibility of the status of the universe modifications is available.
The ADaM Framework supports a multi layered/sub layered infrastructure that allows components to be defined on the layers and their dependencies to other components on the same layers or adjacent layers. The ADaM Framework can be adopted to meet an ever increasing number of business use cases e.g. Business Continuity Planning, Systems Migration, Spreadsheet Risk Analysis, Infrastructure Governance, Human Resource Planning, Outsourced Services, Configuration Management and Financial Modeling.
Changing the layer names to reflect client-specific infrastructure enables the ADaM Framework o adopt a ‘colloquial’ façade so that the underlying dependency matrix fits into a client-specific business domain.