|
|
|
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.
|
Future State Vision for Information ManagementFrom MIKE2.0 Methodology -> You are here: Future State Vision for Information Management
Activity: Future-State Vision for Information ManagementObjectiveThis 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
TasksIntroduce Industry Business Practices for Information ManagementObjective: 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:
Reference Materials, such as:
Define Future-State Business ModelsObjective: 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:
Define Information Management Guiding PrinciplesObjective: 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: Define Technology Architecture Guiding PrinciplesObjective: 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:
These principles should be referred to throughout the implementation programme as they provide an overall guide for the implementation teams. Input:
Output: 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:
These principles should be referred to throughout the implementation programme as they provide an overall guide for the implementation teams. Input:
Output: Define Strategic Future-State Information Process ModelObjective: 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: Define Future-State Conceptual Data ModelObjective: 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:
Define Source-to-Target MatrixObjective: 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:
Define Future-State Strategic Component ArchitectureObjective: 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: Define High-Level Recommendations for Solution ArchitectureObjective: 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:
Core Supporting AssetsYellow Flags
Key Resource RequirementsPotential Changes to this ActivityThis activity should have a task added to also cover development of a future-state content model. Define Future-State Conceptual Content ModelThis 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 asset search
Toolbox
Views
Wiki Contributors
Suggestions
|
