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.

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.

Information Lifecycle Management Solution Offering

From MIKE2.0 Methodology

Jump to: navigation, search
Hv2.jpg This Solution Offering currently receives Minor Coverage in the MIKE2.0 Methodology through the Overall Implementation Guide and SAFE Architecture, but Activities are missing and there are no detailed Supporting Assets. In summary, the Solution Offering has not yet been formulated to the point where it should be used.
A Creation Guide exists that can be used to help complete this article. Contributors should reference this guide to help complete the article.



The Information Lifecycle Management (ILM) Solution Offering provides an approach for data and content with respect to:

  • storage
  • archiving
  • recovery
  • destruction

ILM provides the processes and technologies to properly react to system failures and other undesirable effects. What's more, it improves overall system performance by allowing seldom-used information to be kept offline. At the same time, it makes this offline information available for currently undefined requirements. Examples of these include historical analysis or new regulations. ILM also provides techniques and technologies to increase the amount of data held online in a fashion that does not hinder performance or increase costs. It provides an approach for purging data from the organization to reduce storage costs and complexity.

Executive Summary

All information assets have a lifecycle–defining their point of origin, and point of disposition–in the organization. This lifecycle can either be explicitly managed/controlled or left to chance. Today, the volume of data that companies need to manage is increasing continuously and exponentially. The ever-changing landscape of compliance and regulatory requirements presents new challenges to organizations. A comprehensive ILM framework allows organizations to put the technologies, processes, policies, and culture in place to ensure that information is

  • treated as assets of the firm
  • cost-effectively managed throughout its lifecycle.

The ILM solution promotes IM and regulatory compliance best practices. It includes an approach to:

  • Facilitate cost-effective access to business data
  • Facilitate cost reduction of IT infrastructure
  • Optimize use of assets to improve systems' performance
  • Enable closer alignment of IM to business processes
  • Apply storage intelligence to backup operations
  • Classify information and identify its value to the business
  • Enable identification of IT compliance breaches and correct them without any impact on the business
  • Implementation and management of e-mail Management Solutions
  • Reduce cost of ownership through data compression, use of lower-cost mediums, and data destruction
  • Protect information assets from unplanned deletion or security violations
  • Explicitly manage the data destruction process. This minimizes the risk of information lingering around longer than required

By explicitly managing the information lifecycle, organizations can put in place an approach that proactively minimizes business risk. At the same time, it reduces technology infrastructure, and compliance & litigation costs.

Solution Offering Purpose

This is a Core Solution Offering (CSO). CSOs bring together all assets in MIKE2.0 relevant to solving a specific business and technology problem. Many of these assets may already exist. As the suite evolves, assets can be progressively added to an Offering.

A CSO contains all the elements required to define and deliver a go-to-market offering. It can use a combination of open, shared, and private assets.

Solution Offering Relationship Overview

Mike2 solution groups iam.jpg

MIKE2.0 Solution Offerings provide a detailed and holistic way of addressing specific problems. MIKE2.0 Solution Offerings can be mapped directly to the Phases and Activities of the MIKE2.0 Overall Implementation Guide. This provides additional content to help understand the overall approach. The MIKE2.0 Overall Implementation Guide explains the relationships between the Phases, Activities, and Tasks of the overall methodology. It also explains how the Supporting Assets tie to the overall methodology and MIKE2.0 Solutions. Users of the MIKE2.0 Methodology should always begin with the Overall Implementation Guide and the MIKE2.0 Usage Model. These serve as useful starting points for IM projects.

Solution Offering Definition

The Information Lifecycle Management (ILM) covers the scope of how information will be managed across the environment. The key elements on ILM covered in this offering include the following:

  • Business and Technology Strategy to define an improved approach to ILM
  • Selection of required technologies for ILM
  • Governance processes, standards, and policies for how business and IT users should help manage the information
  • Definition of a classification model for information assets
  • Design and prototyping of the ILM architecture
  • Design and development of ILM techniques and technologies related to storage, archiving, protection, and destruction of information assets
  • Testing procedures for implementing the solution
  • Continuous Improvement Activities focused on reducing costs, adjusting policies due to requirements, or improving performance and reliability

The linkages between ILM and operational IT processes or infrastructure management is not the current focus of this solution. Instead, MIKE2.0 focuses on Information Development. These linkages may be added outside this offering to provide a more comprehensive approach. This is described in the section on Integration to Business Process and Infrastructure.

What is ILM?

What ILM Provides

The ILM Framework – Five Key Elements

Introduction to the Five Elements of ILM

The fundamental principle of ILM can be stated as follows: the value of information changes over time. Value is determined in two dimensions: 

  • by context-based variables or context-free attributes such as placement, distribution, index, search, retention, security, and availability
  • by the function of time.

The ILM Framework is carefully designed to account for different enterprise data management requirements. These requirements are categorized into five major disciplines, but can concurrently span multiple disciplines. These five disciplines (as illustrated in the diagram) are:

  • Regulatory & Compliance Requirements: These represent demands made on the organization by a variety of oversight bodies. These include: national and local governments, industry trade organizations, self-regulating organizations (SRO), and internal operational standards. Examples of these requirements span from Sarbanes-Oxley (SOX) to internal Six Sigma mandates.
  • Information Management Requirements: These represent policy and procedural requirements for the declaration, management, and disposition of data. They are derived partly from industry best practices and partly from internal procedures. The latter involve regulatory and compliance requirements as inputs.
  • Business Process Requirements: These requirements represent the essential bridge between business and IT. They are derived and integrate records' management and regulatory requirements with IT operational standards that cover infrastructure management and data protection.
  • Tiered Infrastructure Requirements: These requirements translate business value of data into a tier of the IT infrastructure. By defining these requirements, an organization can ensure that critical data resides on premium IT infrastructure. At the same time, non-critical data is moved to less expensive infrastructure. Collectively, this ensures that IT dollars are effectively applied to support the business.
  • Data Protection Requirements: These requirements define the operational strategy to safeguard enterprise data against mishaps. Generally speaking, data protection can be broken down into two categories: 1) business continuity--through the design of redundant systems; and 2) disaster recovery--through the design of off-site, parallel recovery centers.

Another foundational element contributing to a successful ILM strategy is the application of data classification. In essence, the enterprise defines types of applications (and the associated data created) through the use of classification “metadata” attributes. These attributes span:

  • Business facets of the application and data (such as business owner, department, or group)
  • Information management facets (such as record series produced and records retention period)
  • IT facets (such as IT support manager, NAS device).

The creation of an “attribute inventory” facilitates the design, management, and enforcement of ILM policies across the Five Key Elements.

Compliance and Regulatory Requirements

The first element of ILM addresses compliance and regulatory requirements. Compliance means conforming to a clearly defined specification, standard, or law. The definition of regulatory requirements refers to the restrictions, licenses, and laws applicable to a product or business and imposed by the government. An increasing number of regulations and regulatory requirements related to data and information management (IM) is a growing challenge for organizations. As a result, this is one of the key elements that an ILM framework needs to address.

Increasing Number and Complexity of Regulatory Requirements

Regulatory requirements have exacerbated a growing dichotomy in corporate America today. To be sure, federal, state, and System of Record (SRO) examining bodies continue to grow. These bodies are becoming more aggressive in seeking out violations. As such, the regulatory costs of staying compliant have become major economic and organizational burdens for many companies. Organizations need a solution that concurrently meets these requirements and cuts costs. Penalties imposed for noncompliance can cause considerable financial losses, declines in company stock price, and significant damage to a company’s reputation.

Regulatory requirements are making it necessary for organizations to provide access to data over varying time periods and with varying degrees of confidentiality. In other words, one size no longer fits all. The data needs to be easily accessed, retrieved on demand, and above all accurate. To accomplish this in an effective manner, organizations need to find ways to implement efficient, cost-effective solutions for records management, archiving, data protection, and business continuity.

The ILM Framework Can Help Cut Costs and Reduce Risks

The ILM framework provides a model, methodology, and supporting infrastructure to reduce costs associated with compliance and litigation support. It enables the identification of IT compliance breaches by providing metrics and processes to identify and prevent potential breaches. It also provides the possibility to correct these without any impact on the business.

The framework translates regulatory and compliance requirements into records management policies. What's more, it provides a policy-based management system for managing data assets. Collectively, these policies and the related management system help ensure a company’s compliance with regulatory requirements. Finally, they limit an organization’s exposure to noncompliant practices.

When organizations mature in their approach to compliance and corporate governance, they will move through a continuum of technologies. Beginning with fragmented point solutions for compliance and data recording, organizations move to more complex and standardized solutions to govern their company data. As organizations mature in their approach to data management they will take on a more holistic outlook.

As new regulations are created, ILM will play a significant role in helping IT professionals adhere to new standards while incurring minimum management headaches.

Industry Specific Requirements and Regulations

Since a significant number of existing regulatory requirements are industry-specific, an ILM implementation must be designed specifically for that industry or business. For example, an ILM solution developed for a life sciences' organization needs to address regulations such as HIPAA and 21 CFR Part 11. In contrast, a solution developed for the telecom industry needs to take PUC and the Calia Act into consideration. The ILM Solution Framework provides a supporting platform to ensure compliance with current and emerging laws end regulations in a variety of industries.


Business Processes

The ILM Framework is a methodology for translating non-IT requirements for the handling and management of data into IT requirements. In other words, they are facilitators and enforcers, built on-top of existing processes.

As a result, ILM business processes should be IT-facing, and vice-versa. It is important to ensure that ILM processes do not add burdensome overhead or management costs.

ILM Business Processes

ILM touches on corporate legal, compliance, and records management functions. Some of the key functions in these areas are:

  • Compliance Reporting: Records Management policies are partly driven by external legal, regulatory, or compliance obligations. The ILM Framework gives organizations a context to translate & map these obligations to policy development activities.
  • Records Retention: Records retention is the activity of storing and aging data through its lifecycle. By implementing enterprise-wide ILM, records management classifications can be directly translated into priority or reliability of the underlying IT infrastructure.
  • Legal Holds: A legal hold is the act of exempting records from deletion, in order to ensure preservation of data relevant to litigation against the firm. The ILM Framework gives a context by which data can identified and marked accordingly, as well as giving records management the tools to recognize valid holds.

The ILM framework allows cross-functional visibility between these areas, facilitating both Legal & Records Management activities, especially in the areas of eDiscovery & Policy Development.

ILM IT Processes

The ILM Framework is designed to bridge corporate & IT functions. In order to maximize transparency throughout the value-chain, it is essential to modify the key IT functions to map back to business functions as well as the overall ILM Framework. Some of these IT functions are:

  • IT Capacity Planning: The ILM Framework helps shapes capacity planning activities by shaping & classifying resource requirements (infrastructure, bandwidth, or even personnel) based on business priorities
  • Tiered Storage Infrastructure Design: Once capacity planning has prioritized resource requests, storage networks can be designed to ensure that data is mapped to the correct tier of storage.
  • Data Search & Retrieval: Just as the ILM Framework assists in the translation of legal, regulatory, and compliance obligations into records management policies, so does it help in translating data search parameters into a common taxonomy.
  • Application Lifecycle Management: It is important that the ILM Framework be extended into application management functions at the earliest stage. By doing so, proper gates and checkpoints are created in the application’s lifecycle to validate that application’s relevance to the ILM Framework, ensuring that proper tools and aids are made available to diverse groups – from application developers to application retirement teams.

Tiered Infrastructure

As part of the ILM framework, the IT Tiered Infrastructure element becomes a by product of the three previous elements. Many IT vendors and practitioners have associated a Tiered Infrastructure with the storage environment. In this ILM model, the IT Tiered Infrastructure is looked at holistically, encompassing all IT aspects of the servers, storage devices and network connectivity used to support an application and its associated data types. A holistic approach must include the people and processes to support and maintain the operational state of the Tiered Infrastructure.

Data Classification Model

Architecting an IT Tiered Infrastructure is accomplished by utilizing the Data Classification model. This model is a compilation of governance, records management, business and application requirements information, which has been gathered and presented in a structured usable format. The format can be in the form of a spreadsheet or database. The data types collected in the Data Classification model include: data retention schedules, application criticality level (Mission Critical, Business Critical, Non-Mission Critical), data security & access controls, data encryption level, data steward, Service Level Agreement (SLA) class, data protection plan, Recovery Point Objective (RPO) and Recovery Time Objective (RTO). There may also be more information collected and provided as part of the overall model.

With the Data Classification model in hand, the IT Enterprise Systems Architect is able to design and build an IT Tiered Infrastructure capable of supporting an application and its associated data types. The information provided in the Data Classification model has not necessarily been centralized or provided in a simple and easy to use format. In the past, the information has often been provided as “Needed” and has lacked structure and details required to provide a complete picture or design. An architect would rely on what they knew from previous design projects or experience in order to fill in the gaps. Simply put, this model provides a simple classification of the data types which are living within the IT Tiered Infrastructure.

Four Layers

The IT Tiered Infrastructure is comprised of four layers: Production, Replication, Recovery, and Archive. These four layers are designed to meet specific support requirements for applications residing in a Tier. At the Production layer, the servers, storage devices, network connectivity, management staff, security, access controls and operational processes are defined, designed and deployed based on the policies and support requirements per application. Subsequent layers may use some or all of these components in its architecture.

The Replication layer provides supporting architecture related to data replication support functions for each tier. It is important to note that each tier in the IT Tiered Infrastructure may not have a need to provide data replication functions to support its applications. The importance of identifying the Replication Layer in the IT Tiered Infrastructure is to provide a holistic end-to-end view of the needed IT architecture.

At the Recovery layer, the focus is on the Data Protection plan with specific details related to the day-to-day backup and restore operations. Each Tier will have a different Data Protection schema with specific technical and operational processes designed to support the recovery of data types within the Tier. In the Tier1 Recovery layer, the architecture may only consist of disk-to-disk backup and restore capabilities, because of SLA, RPO, and RTO requirements, while the Tier3 Recovery layer architecture would consist of backup and restore from tape media. The Tier2 Recovery layer might consist of a combination of disk-to-disk or disk-to-tape capabilities.

The Archive layer is the final layer within this model. It encompasses the functions and architecture needed to support data archiving operations and long term support. Data types within this layer are considered to be critical and useful information, and may be kept past its data retention schedule based upon its usability. This layer may not be needed for a Tier3 application or data type. De-duplication of information is critical at this layer. In the past, data would be written to a tape media and stored for long periods of time as part of an archive strategy. Recent legal penalties and search/hold requirements make storage of data to tape no longer acceptable practice. Backup tapes are not considered searchable media and are very inefficient for this function.

A content management system should be deployed to manage the data types stored at this layer. Application databases have specific functions allowing for the management of data which has been extracted from the source system and stored on an archive target system. These systems require on-going support and management. The level of management and specific support requirements should be identified in the Data Classification model.

People and Processes

People and Processes are functional areas which are part of the IT Service Management (ITSM) framework. The operational activities of these two functions are incorporated and developed for each Tier and its associated Layers. Traditional operational activities include: Change Management, Configuration Management, Service Desk and Capacity Management. Other ITSM functions will apply based upon the model and configuration of the IT operations.


Another integral part of the IT Tiered Infrastructure model is the Chargeback methodology. With the structure and design of this model a chargeback methodology can be deployed, which provides performance metrics and criteria for successfully delivering services to various business units. The IT Tiered Infrastructure streamlines operational processes and aligns IT with the business needs and required application support. Cost savings and cost avoidance are financial attributes to this model.

Information Management

As part of the ILM framework, the Information Management element helps meet Compliance and Regulatory requirements and is supported by Business Process, Data Protection, and the Tiered Infrastructure elements. Information Management is a process of identifying and handling information and data during its entire lifecycle: from its initial creation to disposal. Information and records are the evidence of what the organization does. They capture its business activities and transactions which can include but is not limited to contracts, business correspondences, data bases, user files, personnel files, and financial statements. They are subject to litigation search and hold requirements, and can be crucial to the business’s daily activities and compliance requirements.

Records Management Requirements

The requirements represent policy and procedures for the declaration, management, and final disposition of data. They are derived from compliance and regulatory requirements, internal procedures, and industry best practices. Organizations have a duty to all stakeholders to manage records effectively in order to control cost and ensure compliance with regulatory requirements. Effective records management ensures that the information needed is authentic, retrievable at all times, and protected from improper use and exposure.

Records Retention Schedule

A Records Retention Schedule is a document detailing plans, and designs for a Records Management policy for the storage and the appropriate disposition of all records within the company. Records Management policies are derived from a comprehensive analysis of all identified regulations, business operational processes, industry standards, and business obligations, both internal and external. A robust Records Retention Schedule is a fundamental tool for the implementation of an ILM strategy which will affect the Tiered Infrastructure and Data Protection models and policies. Enterprise-wide records management policies and processes determine what defines a record, its lifecycle, and how it fits within the data classification model. The data classification model is used to define the controls and processes to follow for securing, managing, and safely disposing records. Policies spawn operating processes and procedures – both IT and non-IT. These policies must be measured, monitored, and managed to ensure compliance and effectiveness. Keys to this activity are proper performance management and development of measurable metrics.

Email Management

An Email Management Solution and Methodology facilitates the archiving of email based upon its relevance at any given point in time. A key aspect of this solution is the ability to distinguish between the content of an email and email attachments. Different storage and archiving requirements could apply to both – identifying and separating them can free storage space by eliminating redundancies in the stored data.

Data Classification

Data Classification provides a common terminology and rule set for managing information in a cost-effective way. A company must be aware of the legal requirements for retention of all data, information and records. Rules can then be applied to leverage a multi-tiered storage infrastructure.

Records Types

Records Management includes physical and electronic forms. Both types of records become sensitive data elements when they are used for transporting and communicating trade secrets, intellectual property, and highly sensitive and confidential customer information. Safeguarding this information when in transit is one of the primary areas of concern, especially for electronic records.

  • Physical Records

Physical records management handles the lifecycle of physical records such as tape backups, paper files, medical records, microfilm/microfiche, and any other physical entity. Container management and storage limitations are also included in Physical Records Management.

  • Electronic Records

Electronic Records Management is not as concerned with electronic storage limitations and management, as it is with metadata management and storage based upon business content. Compliance, Risk Management, operational efficiency and enhanced productivity are the primary motivations.

Records Security Management

Records must be stored and there must be confidence that they are protected from unwanted or undesirable access. A Records Security Management solution defines what material needs to be stored securely, at what level, who is allowed get to it, and provide a set of controls around storage of items such as passwords, codes, safe combinations, etc.

Data Protection

Relationship to Solution Capabilities

This Solution Offering maps into the Solution Capabilities of MIKE2.0 as described below.

Relationship to Enterprise Views

The MIKE2.0 Solution Offering for Information Lifecycle Management goes across the Infrastructure Development and Infrastructure Development views of the overall Enterprise Views model. The focus on the MIKE2.0 Solution Offering is to explain the information-oriented aspects of the solution.

Mapping to the Information Governance Framework

The Information Governance Solution Offering is required across all Solution Offerings. For ILM, it is of particular import. The Information Governance Solution plays a part in determining an enterprise’s information architecture, which in turn affects the domain across which ILM is applicable. Information Governance also determines standards and rules that affects what information should be retained and for how long and thus in part determines the lifecycle of all information across the enterprise. In addition, part the Information Governance solution ensures that there is an appropriate level of data quality across the enterprise. This integrity of data is important so that the data can be properly classified and managed as regards Information Lifecycle Management.

Mapping to the SAFE Architecture Framework

The SAFE Architectural components for ILM are defined across the Technology Backplane and are primarily related to the Foundation Capabilities for Infrastructure Development. This component of the SAFE Architecture addresses the fundamental of technologies required for any implementation and includes the Information Security Component, Platform Component, Network Component, and Operations and Monitoring Component. Hence, Tiered Infrastructure and Data Protection, two of the Key Elements of ILM, are supported through these components.

Additional components of the SAFE Architecture that are key to the ILM solution include the Enterprise Business Management Component, specifically Business Process Management which is focused on the definition, measurement, management, and improvement of Business Processes in relation to ILM. The ILM solution offering also maps to the Enterprise Content Management Component, the Information Formats Component, and the Information Repositories Component, all dealing with the management and support related to the Information Management Element of ILM.

Mapping to the Overall Implementation Guide

Phase 1 - Business Assessment and Strategy Definition Blueprint

Overall Business Strategy for Information Development

In the Overall Business Strategy for Information Development activity some of the initial non-functional requirements may begin to emerge that relate more specifically to Information Lifecyle Management at a high level. For example, the need to retain information for 7 years may be a major business requirement and would be identified at a strategic level.

Some tasks may need to be added to this activity to relate better to Information Lifecycle Management.

Organisational QuickScan for Information Development

The Organisational QuickScan for Information Development is used to gain an overview of the current-state environment. This is the first pass in assessing the overall information and infrastructure technology environment, as well as the staff and organisational models that support its management. Assessment tools like Infrastructure Maturity QuickScan are particularly important for Information Lifecycle Management.

Future State Vision for Information Management

The Future State Vision for Information Management defines the strategic conceptual architecture for Information Lifecycle Management. This includes Guiding Principles for Information Management, the necessary components for managing information across the lifecycle and a variety of high-level solution architecture options. It is important to introduce options at this stage as there are a number of different techniques and technologies for managing information across its lifecycle.

Return on Investment of Information Assets

Calculating the Return on Investment of Information Assets is typically done within the context of another Solution Offering and should be brought into this effort. Calculating the Return on Investment of Information Assets is particularly important for ILM as even though the cost of storage continues to decrease, data volume growth rates are increasing at an even faster pace. In addition, new regulations are pushing organisations to store data for longer periods of time as well as more actively in an online form.

Phase 2 - Technology Assessment and Selection Blueprint

Strategic Requirements for Technology Backplane Development

As ILM is focused on capabilities that relate to the Technology Backplane, defining the Strategic Requirements for Technology Backplane Development is a key activity. Sometimes these requirements will be conducted as part of an overall Enterprise Information Management Strategy Solution Offering while other times they will be defined specific to this offering. In large organisations they will typically be done at an overall strategic level and then re-visited for the strategic aspects of each individual solution offering. For Information Lifecycle Management its important that these backplane capabilities cover structured data and unstructured content.

Strategic Non-Functional Requirements

Defining Strategic Non-Functional Requirements is also one of the most critical activities for Information Lifecycle Management. These requirements will define the set of ILM techniques and technologies that will be needed for performance, reliability and monitoring of the system. Non-functional requirements will be driven from many different perspectives for ILM, although regulatory-related requirements will be particularly important.

Current-State Logical Architecture

Unlike other solution offerings, all organisations will already have a significant investment in technologies and techniques related to Information Lifecycle Management. Establishing the Current-State Logical Architecture, therefore, is particularly important. Through a strong understanding of the current-state, decisions can be made related to whether the existing technology meets the required capabilities for ILM and in which cases they need to be replaced.

Future-State Logical Architecture and Gap Analysis

The Future-State Logical Architecture and Gap Analysis builds off the strategic requirements and current-state that were established in the preceding acitvities. As ILM technologies have undergone significant changes in recent years and data volume growth continues to rise rapidly, a gap analysis is important, even when organisations feel existing technologies may do the job effectively. For ILM, it is typically important that requirements take into account projections for business growth over the next 3 - 5 years.

Data Governance Policies

Data Governance Policies are particularly important for ILM as they set guidelines for how to manage information over long periods of time. Organisations often lose focus in information assets as they age yet this information is often still critical. Although policies may be set as part of an overall [Information Governance programme or Information Management Strategy they should be re-visited as part of an ILM initiative.

Data Standards

Data Standards are important for defining how information will be managed. For ILM, some of the most important standards are those that feed into the Information Security Design.

It may be better to expand the current activity to more generally cover Data Protection and thereby cover how data will be stored online and offline as well as kept secure from an access perspective.

Technology Blueprint Completion

The Technology Blueprint Completion activity brings together the output of the activities from the technology blueprint and also refines some of the earlier content from the Business Blueprint such as the business case . The business case for ILM will be particularly important as technology costs will typically be signficant and ROI a major focus.

Phase 3 - Information Management Roadmap and Foundation Activities

Information Management Roadmap Overview

The Information Management Roadmap Overview scopes the release and how it will be implemented for the specific increment. The relative work efforts for ILM initiatives tend to be more significant in the first increment than other increments.

Detailed Business Requirements

The Detailed Business Requirements are defined for each release increment and subsequently translated into corresponding non-functional requirements. These requirements will drive the scope of information to be managed as part of the release.

Solution Architecture Definition/Revision

The ILM Solution Architecture Definition/Revision defines the approach for how information will be managed: from creation to its destruction. If the full lifecycle of information is covered, it may also link into the architectural contents in other offerings and this offering may be included within other offerings. Therefore, it is important that the architectural model be defined in a fashion so that it can be used effectively across solution offerings.

Although there are some activities in the Solution Architecture that apply to the infrastructural aspects of managing information, the coverage is incomplete. This activity will likely be revised so it is more general in nature and has better coverage for the ILM offering.

Prototype the Solution Architecture

The activity to Prototype the Solution Architecture can be a valuable way to test a number of ILM concepts. In particular, it can be valuable for testing automation processes, high load scenarios and the use of new technologies and techniques.

This activity will likely be revised so it is more general in nature and has better coverage for the ILM offering.

Data Classification

Data Classification is a key aspect of Information Lifecycle Management as it is the implementation of rules for how information assets should be stored, managed, valued and eventually destroyed. Data classification typically involves the implementation of rules into a metadata repository but also involves making use of the classification information that is already associated with each asset.

Phase 4 - Design Increment

Information Security Design

The Information Security Design activity provides the logical and physical design of how information will be kept secure. It builds off the initially defined security model for the solution and goes across the in-scope set of information systems. This activity has some overlap into the Infrastructure Management Process Design for how information assets are to be protected. For Information Lifecycle Management, the end-to-end process covered within both of these activities is particularly important.

Infrastructure Management Process Design

The Infrastructure Management Process Design activity is focused on physical tuning of data stores (primarily for performance optimisation), backup processes, archival and restoration procedures. All of these are critical elements of Information Lifecycle Management. For a comprehensive ILM solution the focus is on bringing this design together across the environment as opposed to just applying it to a single system.

Phase 5 - Develop, Test & Deploy Increment

Technology Backplane Development

Technology Backplane Development involves the implementation of physical infrastructure components for managing information infrastructure, building on earlier design activities. Infrastructure Management processes for ILM may involve developing multiple components as well as automating the interactions between these components.

End-to-End Testing

Although these new capabilities should be tested independently earlier in the lifecycle, key aspects of ILM undergo the most signficant testing from an overall solution perspective during End-to-End Testing. It is at this stage that the context is brought together in the overall solution context. Testing should certainly be done from a functional and integration perspective.

Stress and Volume Testing

ILM initiatives will typically deal with very large data volumes and therefore Stress and Volume Testing is a key activity. Testing should be focused on the need to meet performance requirements. Timeframes for re-initiating a backup and recovery process should also be tested for timeframes and impacts on other systems.

Continuous Improvement - Standards, Policies and Processes

As Standards, Policies and Procedures are refined it must be ensured that these policy changes are then implemented. These policies can have a major impact on the business in terms of cost or its ability to meet regulatory requirements. As part of a continuous improvement programme they should be explicitly re-visited as part of the ILM Solution Offering. In particular, policies related to data retention, information sharing processes and new standards based on new regulatory requirements should be reviewed.

Continuous Improvement - Infrastructure

Infrastructure technologies continue to change dramatically. Organisations should look to periodically re-factor their infrastructure, including technologies that relate to ILM. Benefits include the ability to more easily meet new functionality requirements, lower cost of ownership, improve performance and reduce risks of data loss.

Mapping to Supporting Assets

Logical Architecture, Design and Development Best Practices

Although some ILM best practices are product-specific, a number of logical techniques can also be defined. These techniques can then be mapped below to implementation with a specific product.

Key logical assets include:

Product-Specific Implementation Techniques

Specific techniques referenced in this section would include content from organisations such as:

  • EMC
  • HP
  • IBM
  • Microsoft
  • NetApp
  • Sybase

Product Selection Criteria

Key criteria for selection include:

  • Breadth of offering into areas such as data compression, performance, data protection and reliability
  • Administrator usability
  • Market positioning

The Technology Assessment QuickScan model should be extended to cover ILM component capabilities in more detail. Some capabilities are already listed in Infrastructure Maturity QuickScan

Relationships to other Solution Offerings

Information Lifecycle Management ties in closely with many other offerings as they means to support the long-term use of information. As the initiatives deal with very large volumes of information or complex requirements related to information access, the offerings below are dependent on a strong ILM foundation:

Extending the Open Methodology through Solution Offerings

Listed below are proposed extensions to the Core MIKE2.0 Methodology to meet the requirements for Information Lifecycle Management:

Integration to Business Process and Infrastructure

The ILM Solution Offering is focused strictly on the management of information. A more complete solution offering for ILM should:

  • Explicitly tie the offering to the key business process that are enabled (such as regulatory requirements). This is done through Business Solution Offerings.
  • Explicitly tie the offering to other best practices frameworks that relate to ILM such as Six Sigma or ITIL
  • Although the offering covers the infrastructural aspects of information management, it doesn't cover infrastructure areas such as Virtualisation or Server Management as they are not within the scope of the MIKE2.0 Methodology. for a complete ILM solution, however, they are relevant concepts.

Potential Activity Changes

Overall Strategic Requirements for Information Development

Some tasks may need to be added to this activity to relate better to Information Lifecycle Management.

Organisational QuickScan for Information Development

Assessment tools such as Information Maturity QuickScan should be extended to provide full coverage of the Information Management Lifecycle. Infrastructure Maturity QuickScan needs to be made more objective and more of the content put online, so it is defined in the same fashion as IM QuickScan. There is some overlap between these tools and a clear distinction should be made on where each is to be used.

Solution Architecture Definition/Revision

This activity will likely be revised so it is more general in nature and has better coverage for the ILM offering.

Solution Architecture Definition/Revision

This activity will likely be revised so it is more general in nature and has better coverage for the ILM offering.

Prototyping the Solution Architecture

This activity will likely be revised so it is more general in nature and has better coverage for the ILM offering.

Data Classification

This activity is still being defined; changes will impact it use in the overall solution offering.

Wiki Contributors
Collapse Expand Close

View more contributors