Records, Contracts and IP Management Solution Offering

From MIKE2 Methodology

This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.

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.

Contents 1 Introduction 1.1 Executive Summary 1.2 Solution Offering Purpose 1.3 Solution Offering Relationship Overview 2 Solution Offering Definition 3 Relationship to Solution Capabilities 3.1 Relationship to Enterprise Views 3.2 Mapping to the Information Governance Framework 3.3 Mapping to the SAFE Architecture Framework 3.4 Mapping to the Overall Implementation Guide 3.5 Mapping to Supporting Assets 3.5.1 Logical Architecture, Design and Development Best Practices 3.5.2 Product-Specific Implementation Techniques 3.5.3 Product Selection Criteria 4 Relationships to other Solution Offerings 5 Extending the Open Methodology through Solution Offerings 5.1 Potential Activity Changes 5.1.1 Overall Business Strategy for Information Development 5.1.1.1 Organisational QuickScan for Information Development 5.1.1.2 Data Standards 5.1.1.3 Data Classification 5.1.1.4 Information Workflow 5.1.1.5 Solution Architecture 5.1.1.6 Information Security Design

Introduction

The Records, Contracts and IP Management Solution Offering provides an approach to managing content whereby changes can only take place within a strict governance framework as minor changes to content may significantly impact product development or ongoing engagements. Due to the nature of this content, key enablers of this offering include information security, information workflow and governance standards, policies and procedures.

Executive Summary

Solution Offering Purpose

This is a Core Solution Offering. Core Solution Offerings bring together all assets in MIKE2.0 relevant to solving a specific business and technology problem. Many of these assets may already exist and as the suite is built out over time, assets can be progressively added to an Offering.

A Core Solution Offering 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.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, providing 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 as well as how the Supporting Assets tie to the overall methodology and MIKE2.0 Solutions. Users of the MIKE2.0 Methodology should always start with the Overall Implementation Guide and the MIKE2.0 Usage Model as a starting point for projects.

Solution Offering Definition

Relationship to Solution Capabilities

Relationship to Enterprise Views

Mapping to the Information Governance Framework

Mapping to the SAFE Architecture Framework

Mapping to the Overall Implementation Guide

Mapping to Supporting Assets

Logical Architecture, Design and Development Best Practices

Product-Specific Implementation Techniques

Product Selection Criteria

Relationships to other Solution Offerings

Extending the Open Methodology through Solution Offerings

Listed below are proposed extensions to the Overall Implementation Guide to meet the requirements for this Solution Offering:

Potential Activity Changes

Overall Business Strategy for Information Development

The Business Strategy for records management would require expanding beyond the metrics and KPIs and should involve knowledge requirements

Organisational QuickScan for Information Development

Should explicitly extend the QuickScan tools to cover search and more broadly the management of unstructured and semi-structured content.

Data Standards

Should be extended to include Content Modelling Standards

Data Classification

If this activity is completed and includes the development of taxonomies than it would be more relevant for this offering. It should probably be generalised to cover structured data and unstructured content.

Information Workflow

An activity may be explicitly added that relates to the flow of information across systems where process is long-lived and complex. Workflow is important for IP management.

Solution Architecture

This activity will likely be generalised to better cover solution offerings

Information Security Design

This activity is still under development. It may have some more detail added to it in relation to content security. Security is particularly important for this offering.