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.

Future State Vision for Information Management

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Content Model Relationship

Contents

Activity: Future-State Vision for Information Management

Objective. This Future State Vision for Information Management activity presents the strategic architecture at a conceptual level, based on the initial set of strategic business requirements, the current-state environment and industry best practices. Much of the vision is still at the “options” level, but these options are no longer theoretical - they are tied to actual business requirements and the specifics of the current environment.

This activity may also be referred to as the Future-State Conceptual Architecture.

Major Deliverables
  • Best Practices & Industry Summary
  • Future State Alternatives
  • Guiding Principles for the Strategic Architecture and Solutions Delivery
  • Future State Business Process Model
  • Future State Conceptual Data Model
  • Future State Strategic Component Architecture
  • Future State High Level Solution Architecture Options
  • Future State use of Information Economic Principles within the Enterprise


Common assets:

Tasks

Task: Introduce Industry Business Practices for Information Management

Objective: Market leaders, best practices and market trends provide insight into the components of successful business models and gaining an understanding of “what are our competitors doing?” This may include processes outside the particular organisation's industry or discipline.


Input:


Output:

Task: Define Future-State Business Models

Objective: The Future-State Business Architecture provide new alternative strategies for accomplishing the organisation's business vision. Future-state business models consider current business processes, resources, cultural impact, and constraints. These new business models may require in new processes and supporting information or they may result in changes to existing processes or improvements to information. This list of processes and information will be analysed in subsequent tasks. Whilst there is some coverage of technology, it is primarily left until later in the activity.


Input:


Output:

Task: Define Information Management Guiding Principles

Objective: Information Management Guiding Principles provide a framework for how information is to be shared, captured, stored, modelled and kept reliable across the environment. They are the first step in the definition of the Information Development environment. As organisations need to be able to clearly enunciate the principles by which it leverages information, a clear set of Information Management Principles are particularly important. Implementing these principles will result in an enterprise that excels at leveraging data for the benefit of all of its stakeholders by providing better service and a better financial return.

These principles should be referred to throughout the implementation programme as they provide an overall guide for the implementation teams.


Input:


Output:

Task: Define Technology Architecture Guiding Principles

Objective: Technology Guiding Principles are to provide a framework for making technology decisions related architecture, implementation and product selection. Technology Guiding Principles are typically broken down into IT Guiding Principles and Technology Guiding Architecture Principles. Technology Architecture Guiding Principles:

  • Define a solution framework and a vision that can be applied to evolving technologies
  • Define how technology will be implemented as a solution to meet the needs of the business

These principles should be referred to throughout the implementation programme as they provide an overall guide for the implementation teams.


Input:


Output:

Task: Define IT Guiding Principles (Technology Backplane Delivery Principles)

Objective: Technology Guiding Principles are to provide a framework for making technology decisions related architecture, implementation and product selection. Technology Guiding Principles are typically broken down into IT Guiding Principles and Technology Architecture Guiding Principles. IT Guiding Principles:

  • Guide the manner in which IT will relate to the Business
  • Guide technology choices and how it is delivered and managed

Together with Technology and Information Management Principles, Guiding Principles for Technology Backplane Delivery provide the following benefits:

  • Provide a clear linkage to business priorities
  • Guide the technology organisation
  • Facilitate communication of initiatives to business users
  • Help to simplify decision-marking processes
  • Define best practices for implementation

These principles should be referred to throughout the implementation programme as they provide an overall guide for the implementation teams.


Input:


Output:

Task: Define Strategic Future-State Information Process Model

Objective: This is the definition of the overall information process model (business processes for information management) for the target environment. It is not at a low level of detail – it the definition of business processes at the strategic level. This task shows what will be the major processes (Level 1 and possibly Level 2 depending on the scope of work) processes across the pillars of the business. This will typically be a long-running task – it is important that this be kept at a high level. Later activities focus on re-factoring business processes after they are understood at a more detailed level.


Input:


Output:

Task: Define Future-State Conceptual Data Model

Objective: This is the definition of the overall conceptual data model for the target environment. The conceptual data model may then be refined during the creation of the Solution Architecture, before creating the Logical and Physical models. It is strongly preferred that at this stage we begin capturing some of the major information requirements into a case tool, although in some cases a tool will not have been selected yet. Not all projects employ conceptual modelling (high level logical modelling) but it is generally recommended as part of the MIKE2 methodology.


Input:


Output:

Task: Define Source-to-Target Matrix

Objective: The two vertices of this matrix shows the source and target systems respectively. A system can be both a source and a target. This tool is an excellent communication tool to help set scope, identify gaps and overlaps and demonstrate the complexity of the project. It allows costs to be allocated to business drivers. At this stage it is a high level view but is developed in further detail in subsequent tasks.


Input:


Output:

  • Source to Target matrix

Task: Define Future-State Strategic Component Architecture

Objective: The future-state strategic component architecture maps in the capabilities that are envisaged to be required in the future-state environment. The strategic component architecture is at a very high-level and is presented in a form that can be easily understood by management staff with some technology background. It is only to present what “could be” based on the information gathered during the and will go through multiple revisions.

For the Technology Backplane, the SAFE Architecture for Enterprise Information Management can be used as a starting point.


Input:


Output:

Task: Define High-Level Recommendations for Solution Architecture

Objective: These are high level recommendations only (further detail will come during Phase 3) and are at the conceptual level. The recommendations derive from previous sessions on leading industry practices and the needs of the client. At this stage, the recommendations should be very much at the “options” level.

These Solution Architecture models also provide recommendations on the “transition-state” – going from the current-state architecture to the future-state.

The SAFE Architecture Solutions and Supporting Assets contain leading practices that should be referenced for this task.


Input:


Output:

Role:Senior Business Analyst

Role:Solution Architect

Role:Infrastructure Architect

Role:Information Architect

Yellow Flags

  • Disconnect between future-state conceptual architecture capabilities and strategic business and technology vision from QuickScan assessments
  • Team has obvious skill issues with new technologies that were not addressed during Awareness
  • High Level Solution Architecture is not presented as options – only a single approach as presented as the strategic approach

Potential Changes to this Activity

This activity should have a task added to also cover development of a future-state content model.

Define Future-State Conceptual Content Model

This is the definition of the overall conceptual content model for the target environment. This model will be refined in Phase 3 in more detail.

Wiki Contributors
Collapse Expand Close

View more contributors