Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Members
Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

Technology Backplane

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search

In the context of the SAFE Architecture, Information Development and Infrastructure Development are thought of as a Technology Backplane. The Technology Backplane consists of Information and the Infrastructure which supports the management, storage and movement of data.

The framework of data in databases (at rest) and data in messages, file transfers etc. (in motion) as well as data participating in interfaces is ‘in total’ the data architecture.

When the data architecture is integrated with people, process, organisation, technology and strategy the result is ‘Information Development’. Information Development is the overall goal in-so-far as that is what actually implements data architecture in support of Application Development.

The result is that there are three streams of work to be explicitly managed – Application Development, Infrastructure Development and Information Development.

Contents

Translation to Business Value

Taking a Backplane-oriented approach can translate directly to Business Value. Some of the key benefits include:

Competitive Advantage

  • Near real-time requirements of the Business addressed

The Technology Backplane enables comprehensive access to information in BusinessTime.

  • An extensible information infrastructure

The Technology Backplane infrastructure minimizes time and cost to design and implement new products and services.

The Technology Backplane makes it easier for customers to do Business by enabling more customer self service as well as the management of complex customer processes

Cost Rationalization

  • Rationalization of Business Operations

The cost reduction strategy is supported within the Technology Backplane Infrastructure by decommissioning and converging inefficient and redundant systems.

  • Implementation of Common Services and Functions

The Business Case for the Technology Backplane Infrastructure can be a cost neutral projection over a relatively short period.

  • Rationalization of Processes

The savings can used to better address Operational / Convergence / Analytical implementations in a more cost effective manner

Future Integration

  • Iterative and cost effective approach to future Technologies
  • Standards based approach (e.g. XML)

The Technology Backplane Architecture reduces the risk of technology obsolescence. Application suites become ‘plug and play’ with respect to the infrastructure.

Using the Technology Backplane Architecture, new and old environments can co-exist, helping to more effectively support mergers, acquisitions, B2B and as well at IT transformations.

Regulatory

  • Platform for rapid adaptation to regulatory requirements
  • Regulatory Reporting, Compliance and Analytics

As part with the implementation of the Technology Backplane Infrastructure there are initiatives to improve the data quality, timeliness and accessibility. This directly enhances the ability to demonstrate conformance to regulatory requirements.

Delivery Approach

Get the Technology Backplane 'Out In Front'

The Goal is to get Technology Backplane capabilities out in front. This is done through an initial baseline implementation and then ongoing development in each increment.

  • The Tactic is to use the business drivers from the initial Blueprint and the defined Application Development Sequence to drive the initial set of Foundation Activities of the Technology Backplane.
  • The Goal is to get the Backplane capabilities ahead of the application development so there are no inherent delays which preclude proper architectural implementations.

This means that the Technology Backplane is initially implemented for the first piece of work and there is a major focus on the initial infrastructure capabilities. The Backplane is continually improved to the point where it becomes a capability that is ahead of the Application Development curve.

The Technology Backplane is not infrastructure for infrastructure's sake. Done correctly, it supports iterative implementations reducing risk and brings Business Value sooner.

Wiki Contributors
Collapse Expand Close