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

Collapse Expand Close

To join, please contact us.

In other languages
Collapse Expand Close
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.

MIKE2:Content Model

From MIKE2.0 Methodology

Jump to: navigation, search


MIKE2.0 Content Hierarchy

The MIKE2.0 Methodology is stored in various forms is distributed documents, tools and web content. In order to make this content flow together for the end-user, MIKE2.0 provides a content model that organizes the content and its relationships through the overall set of tasks and components in the architecture. As the development of the methodology is a continuous process, MIKE2.0 has been constructed in a fashion so that functionality can be added underneath the Overall Implementation Guide and SAFE Architecture framework.

Overall Content Model for MIKE2.0

Users of the MIKE2.0 Methodology should always start with the Overall Implementation Guide and the MIKE2.0 Usage Model before using any of the more detailed assets when undertaking a project as they explain the relationships between the phases, activities and tasks of the overall methodology.

MIKE2.0 Solution Offerings

MIKE2 Solutions

MIKE2.0 Solution Offerings address business and technology problems related to information management by supplementing the Overall Implementation Guide in both a detailed and holistic fashion. The detailed aspect to MIKE2.0 Solution Offerings means that they typically encompass very specific techniques, design patterns and process steps. The holistic aspect means that MIKE2.0 Solution Offerings tend to focus on a certain type of problem as opposed to being generalized for information management like the Overall Implementation Guide. MIKE2.0 Solution Offerings are mapped to Activities in the Overall Implementation Guide.

There are multiple types of Solutions that make up the MIKE2.0 Methodology:

  • Composite Solution Offerings are next-generation offerings that provide advanced information-centric capabilities across two or more core solution areas.
  • Vendor Solution Offerings provide integrated approaches to solving problems from a vendor perspective and are often product-specific.
  • The SAFE Architecture is a framework primarily used for architecting the Technology Backplane.

Thus far, the primary focus of MIKE2.0 has been on creating Solutions that apply to the Technology Backplane. The complementary MIKE2.0 Business and Vendor Solutions are newer areas and will have a greater ongoing focus as the methodology is further developed.

Core Solution Offerings

MIKE2.0 Core Solution Offering Groups

Core Solution Offerings are solutions for common problems in Information Management. These problems are fairly signficant and would come in the form of major projects that an organisation would conduct that would take place over months or years. Core Solutions are often industry-independent, complementing Business Solution Offerings which tend to apply to a specific type of organisation. They are also logical, complementing Product Solution Offerings which are technology-specific. They are delivered through Information Development and Infrastructure Development, using components from the SAFE Architecture.

Core Solution Offerings cover specific best practices around implementing foundation capabilities, advanced capabilities or an aggregate of these capabilities to deliver an overall architectural approach.

Core Solution Offerings are contained within 6 main Offering Groups:

Composite Solution Offerings go across offerings within different offerings groups.

The complete list of offerings are shown below within their respective Offering Groups. This list of Offerings will evolve over time and contributors are encouraged to propose new offerings.

MIKE2.0 for Enterprise Information Management - Core Solution Offerings

All Core Solution Offerings have common features, such as Design Patterns and Vendor Implementation Techniques. Core Solution Offerings are referenced against the SAFE Architecture and the MIKE2.0 Overall Implementation Guide.

Business Solution Offerings

Mike2 content model business solutions.jpg

MIKE2.0 Business Solutions provide recommendations for solving a number of business problems for which information management is critical to success.

Business Solutions help users by proving an introduction to the business problem, the industries it impacts and why the MIKE2.0 approach is beneficial to solving the problem. They also provide a set of high-level business requirements, required aspects of the SAFE Architecture and applicable activities from the Overall Implementation Guide. It also lists some recommended best practices for implementation, typical areas of complexity and applicable vendor technology solutions to solve the business problem.

Proposed initial MIKE2.0 Business Solutions include:

Business Solution Offerings relate to the Business Model View of the architecture and are complemented by Core Solution Offerings. To solve any complex business problem Application Development, Infrastructure Development and Information Development activities are needed.

It is envisaged that some users of MIKE2.0 will develop Business Solutions as Private Assets that are mapped into the open method or as assets developed in an open framework that is not part of MIKE2.0. The structure shown of the proposed solutions provides a framework as a starting point for solution development.

Product Solution Offerings

MIKE2.0 Product Solutions

Product Solution Offerings describe an offering that is specific to a commercial or open source product. They map directly to Core Solution Offerings and in some cases also map to Business Solution Offerings.

Vendor Solution Offerings are vendor-specific recommendations for solving problems in Information Management. Whereas core Solution Offerings tend to be logical in nature, Vendor solutions are physical as they focus on implementation approaches with specific vendor products.

Open Source Solution Offerings are used to implement solutions to Information Management problems, solely through the use of open source technologies. Open Source products tend to be immature when compared with commercial offerings in the Information Management space – one of the goals of MIKE2.0 is to address this issue by becoming an organizing framework for the use of Open Source technologies

Within MIKE2.0 there is a particular focus on the use of open source technologies. These open source products are similar to commercial product offerings in that they map into the logical solutions.

MIKE2.0 Solution Capabilities

Solution Capabilities that Support Solution Offerings within the overall content model

Solution Capabilities are the assets that bring together the MIKE2.0 Methodology. They provide the lowest level assets within MIKE2.0 as well an overall set of activities and tasks for Enterprise Information Management that are provided through an proposal software implementable method.

While they are typically not market-facing sales assets, Solution Capabilities are a critical aspect of the delivery process and therefore a key aspect of the solution. They support go-to-market Solution Offerings through a number of Foundational Solutions, an Overall Implementation Guide, Usage Model, and Supporting Assets that are critical to delivery of each solution.

While Solution Offerings are often seen as the "face" of the MIKE2.0 Methodology, Solution Capabilities are the "glue". Solution Capabilities make up the great majority of content. MIKE2.0 makes use of open, shared and private versions of these assets that factor into the sales and delivery process. A number of Solution Capabilities are protected as Core Methodology.

Overall Implementation Guide

MIKE2.0 Content Model

The Overall Implementation Guide collates all of the content contained within MIKE2.0 framework. In a nutshell, the guide is the organizing framework for bringing everything together. The Overall Implementation Guide is comprised of the following:

  • Overview and Key Concepts introduces users to a new set of enterprise models and the concept of Information Development. The latter is especially important, as it is used extensively throughout the MIKE2.0 Methodology. It helps users understand the benefits of superior information management.
  • The section on Rationale details the development of the MIKE2.0 approach. It further details why the solution was created and a bit of the history on how it took its current form.
  • The 5 Phases of MIKE2 outline how MIKE2.0 has adopted an iterative, agile approach for continuous implementation. This approach divides the development and rollout of an entire system into a series of implementation cycles.
  • The Overall Task List provides the overall set of Phases, Activities, and Tasks for MIKE2.0.
  • The Usage Model provides some guidance on how these tasks are applied to different types of projects.

To better appreciate the activities and tasks of the Overall Implementation Guide, it is useful to describe the architecture framework and delivery model at a high level. This includes:

  • Information Governance Solution Offering. This helps users understand the skills that will be required on the team, how tasks are to be structured, and some of the guiding principles around the MIKE2.0 delivery approach.

Note that the development of the methodology is a continuous process. To this end, MIKE2.0 has been constructed in a fashion that allows functionality to be added underneath the Overall Implementation Guide and governing architecture.

MIKE2.0 Task Model

The Overall Implementation Guide provides the governing set of Phases, Activities, and Tasks for the MIKE2.0 Methodology:

  • Phases are the major lifecycles of a programme. The MIKE2.0 Methodology has five phases as part of its continuous implementation approach.
  • Activities describe major units of work through a focus on key concepts and deliverables.
  • Tasks describe the detailed set of steps within an Activity that are required to produce the overall set of deliverables.

Each Phase, Activity, and Task consist of the following:

  • Objective - an overview of the particular step
  • Input - dependencies to initiating the particular step in the process
  • Deliverables/Output - describe the ultimate work or item created via this step in the process

At the Activity level, the following are also defined:

  • Core Supporting Assets - references to Key Supporting Assets (KSAs). Only Public Supporting Assets are listed within the Overall Implementation Guide. A number of other KSAs are linked into the methodology through either internal knowledge management systems (internal version) or through categories in the open methodology.
  • Yellow Flags - issues that typically cause problems--or at least pose the risk of doing so.
  • Key Resources - typical types of resources needed to perform an activity. Note that this key resources reflect high-level models. For more detailed analysis and work, users should employ MIKE2.0 estimating tools for more accurately results.

Each of these areas will be enhanced over time. Doing so supplement the core methodology. Contributors to MIKE2.0 can recommend extensions and new Core Supporting Assets to the Overall Implementation Guide.

When undertaking a project, users of the MIKE2.0 Methodology are best served as follows: 

  • start with this Overall Implementation Guide
  • look at the MIKE2.0 Usage Model
  • then use the more detailed assets

Usage Model

The MIKE2.0 Usage_Model provides a guide in determining which phases, activities, and tasks from the overall methodology process are typically used for Enterprise Information Management (EIM) engagements. While there are certainly differences among each of the projects, there are also many similarities with respect to the overall approach, tasks, and more detailed required supporting assets. As a result, all projects are described in the context of the Overall Implementation Guide and the Usage Model are used to map the relevant tasks required for implementation.

A number of Usage Models exist to map Activities to Solution Offerings. These include models for:

The corresponding Offerings explain the context in which these activities are used. What's more, they are performed for each activity in the Overall Implementation Guide.

Even if the project represents only a small subset of work, organisations should attempt to cross-check the approach against the overall steps in the methodology. Doing so ensures that all requird activities have been completed. Ultimately, this means that even tactical projects may start with a review of the Blueprint stage.

Integrating MIKE2.0 to External Assets provides the approach for using MIKE2.0 in the context of an overall implementation programme.

Foundational Solutions

Mike2 content model foundational solutions.jpg

Foundational Solutions are "background" solutions that support the Core Solution Offerings of the MIKE2.0 Methodology. Foundational Solutions include:

Some Foundational Solutions are also go-to-market offerings. These include:

Foundational Solutions represent the lowest-level assets within MIKE2.0 that are comprehensive in nature. They often tie together multiple Supporting Assets; they  are referenced from the Overall Implementation Guide and other Solution Offerings.

SAFE Architecture

SAFE Architecture

SAFE (Strategic Architecture for the Federated Enterprise) provides the technology solution framework for MIKE2.0. The SAFE Architecture goes across applications, data, and infrastructure and was designed to accommodate the inherent complexities of a highly federated organisation. SAFE covers a number of capabilities, varying from those that are fundamental for the majority of project implementations to advanced capabilities that are only emerging in the area of Enterprise Information Management.

MIKE2.0 uses an architecture-driven approach that moves from a conceptual vision of the architecture to a set of strategic vendor products before moving into a solution architecture and design for each increment. Many of the tasks of the Overall Implementation Guide are architecture-specific, and all MIKE2.0 Solutions reference aspects of the SAFE Architecture as part of their approach to implementation.

Information Governance

Mike2 content model governance.jpg

An Information Governance framework is a key aspect of the MIKE2.0 Methodology. The Information Governance Solution Offering is a go-to-market offering that also acts as a foundational aspect of the suite. The offering provides a comprehensive approach to improving Information Governance through a method for moving to an improved competency in how information is managed across the organization. This includes staff skill sets, policies, procedures and processes, organizational structures and technology.

The broad definition of Information Governance employed in MIKE2.0 is therefore an important driver for organizational change that include analysis of information maturity levels, communications models and interactions with senior technology and business stakeholders. .

The offering for Information Governance is the key enabler for delivering an Information Development approach.

Supporting Assets

Mike2 content model supporting assets.jpg

Supporting Assets are reusable building blocks that provide the requisite detail to complement the MIKE2.0 Methodology. Many of the activities within the methodology involve sample assets to which end-users can refer during the implementation process. There are a number of different types of Supporting Assets:

  • Deliverable Templates are framework documents that can be used on any project implementation. Unlike Tools and Technique Papers that focus on process, Deliverable Templates provide a document structure that defines the output of an activity and its tasks.
  • Capability Statements are overview presentations, selling messages, and client and vendor cases studiesrelated to the MIKE2.0 Methodology. They encourage users to take a MIKE2.0 approach.
  • Software Assets on the Open MIKE2.0 site are open source software artifacts that can be used as part of the overall methodology. Users of the MIKE2.0 Methodology may also wish to house private software assets mapped into the overall organising framework provided by MIKE2.0. Vendors can also map in their product sets into MIKE2.0 through MIKE2.0 Vendor Solutions.
  • Engagement Management Assets provide recommended team structures, estimating models, and starter project plans for conducting Information Development projects. Engagement Management Assets are often MIKE2.0 Private Supporting Assets. However, some of the former are available on the open methodology site.
  • Project Examples are example deliverables (both document- and software-based) that have been used in Information Development implementations. They can provide guidance for project implementations.

Substantial additions/changes to the Overall Implementation Guide and Solution Offerings are typically driven through the creation of Supporting Assets. Guidelines for contributing to the methodology define this process.

MIKE2.0 Collaboration Environment

MIKE2.0 is hosted within a comprehensive collaboration environment that allow users to engage in knowledge sharing, content development and skills improvement. The capabilities provided by omCollab include:

  • A Wiki to collaboratively create and share content (based on MediaWiki which powers Wikipedia, the world's largest Wiki).
  • Blogs to publish individual or group-based information (based on Wordpress, the world's most popular blogging platform).
  • Social Bookmarking for storing, sharing and discovering web bookmarks. We have released this as omBookmarks, a fork of the codebase from Scuttle.
  • Forums to support discussion groups and frequently asked questions (based on phpBB, the most widely used open source forums solution)
  • Search for users to discover content across federated repositories.
  • Rich User Interface with advanced navigational components, an integrated skin and single sign on to provide common look and feel across the platform.

There are also a number of extensions to these components, that can be found of the Special:Version page of MIKE2.0.

Wiki Contributors
Collapse Expand Close