|
Wiki Home
Members
To join, please contact us. Improve MIKE 2.0
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 BackplaneFrom MIKE2.0 Methodology -> You are here: Usage Model for Information Strategy, Architecture and Governance > Technology Backplane 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.
Translation to Business ValueTaking a Backplane-oriented approach can translate directly to Business Value. Some of the key benefits include: Competitive Advantage
The Technology Backplane enables comprehensive access to information in BusinessTime.
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
The cost reduction strategy is supported within the Technology Backplane Infrastructure by decommissioning and converging inefficient and redundant systems.
The Business Case for the Technology Backplane Infrastructure can be a cost neutral projection over a relatively short period.
The savings can used to better address Operational / Convergence / Analytical implementations in a more cost effective manner Future Integration
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
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 ApproachThe 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.
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 asset search
Toolbox
Views
Wiki Contributors
|

