Redundant Systems Consolidation

Overview

Symptoms

Many organizations have, for whatever reason, multiple systems that perform many of the same functions. This results in highly duplicative maintenance efforts, inconsistencies in user or customer presentation, duplicate or inaccurate information presentation and a host of integration problems.

Redundant systems occur when organizations acquire a competitor, when a merger occurs or when previously cloned systems in parallel lines of business are to be re-integrated. Symptoms indicating that this scenario is applicable include:

· Currently running several systems that essentially perform the same or similar functions

· Several similar systems contain overlapping and/or redundant physical data

· While not identical or as functionally rich, the duplicate system or systems serve the same basic function>

· The organization wishes to consolidate duplicate business areas into a single functional unit

· IS wishes to consolidate duplicate systems support areas into a single unit

· High IS and user support costs require the consolidation of duplicate functions

Requirements

The following requirements are based on the fact that one or more redundant systems exist and that the IS organization has a charter and funding to correct the situation.

· Deliver a single system that effectively replaces multiple, redundant systems

· Build target system utilizing Information Engineering methodology as target analysis, design and implementation paradigm

· Produce an integrated, comprehensive representation of strategic data

· Produce a system based on strategic analysis, tempered by operational data and business functions that have been derived from the current system

· Salvage and incorporate key business rules from existing systems under the new integrated architecture

· Establish a transition strategy to phase in the new application and phase out existing systems

· Identify and implement the best approach for achieving a new, integrated application

Redundant Systems Consolidation Planning Considerations

It is always wise to remember that the guidelines for this scenario should be tempered based on the number and availability of in-house systems, package applications, top-down models and subject matter expertise. Work plans should also be tempered appropriately to reflect specific project management guidelines, in-house review requirements, the political atmosphere, the use of outside consultants and the development methodology in use.

Finally, the task definitions outlined in the Comsys-TIM stages themselves provide the detail to actually plan and implement this scenario. The steps and options addressed within each task should be carefully considered during the planning and implementation of the duplicate systems scenario.

Build Redundant Systems Consolidation Plan

Develop Assessment Proposal

Objective setting & proposal development

Complete Executive Planning

Position System(s) Under Option Strategy Matrix

Note: The following step is where options/hypotheses are articulated for systems being assessed and typically includes options to capture and integrate bottom-up and/or top-down views as follows:
· Bottom-up (only) integration of existing, duplicate stand alone systems
· Bottom-up/top-down integration of existing, duplicate stand alone systems
If a vendor package is involved, treat it as another in-house, duplicate system.

Develop Inventory Analysis Objectives

Establish Assessment Task List

Note: The following steps are the actual Inventory Analysis steps to be used in this assessment - assume each system will undergo analysis.

Finalize Environmental Analysis Work Plan

Finalize Process Flow Analysis Work Estimates

Note: All steps of data definition analysis, including assess multi-system data definition usage, will be performed.

Finalize Data Definition Analysis Work Estimates

Note: Assume all steps of the architectural assessment are to be performed.

Finalize General System Architecture Work Plan

Finalize Presentation Layer Analysis Plan

Finalize Data Access Layer Assessment Plan

Create Architecture Summary Work Plan

Note: User backlog analysis should target redundant requests among systems. Some of these user requests may be fulfilled by existing functions in duplicate systems - this will become clear in remainder of functional assessment.

Finalize User Backlog Analysis Plan

Note: Next four steps focus on comparing bottom-up views of current systems to themselves or to top-down models based on options being evaluated. Integrated view is created as final step.

Finalize Subject Area Analysis Work Plan

Finalize Function Hierarchy Analysis Plan

Finalize Function Dependency Analysis Plan

Finalize Function Entity Type Analysis Plan

Note: Perform IS infrastructure analysis on all application areas supporting all systems being assessed.

Finalize IS Infrastructure Analysis Plan

Note: Narrow down hypotheses at this point to either focus on existing system integration with minor enhancements or bottom-up/top-down integration.

Finalize Feasibility Analysis Plan

Note: Interim plan will include improving & stabilizing components of assessed systems that are to be used as a baseline for the integrated target application.

Finalize Interim Planning Task Effort

Note: The redevelopment plan will include either a bottom-up integration or a top-down/bottom-up integration effort based on selected hypothesis.

Finalize Strategic Redevelopment Work Effort

Develop Inventory Analysis Work Plan

Complete Inventory Analysis Assessment Proposal

Assess IS Application Infrastructure

Environmental analysis

Note: The following steps are performed for each system input to this assessment.

Identify & Categorize Physical System Components

Identify & Categorize External System Components

Inventory & Cross Reference Mainframe Components

Review & Refine Environmental Analysis Results

Produce Environmental Counts and Scores

Produce Environmental Analysis Narrative Summary

Process flow analysis

Note: Process flow analysis is performed for each system input to this assessment.

Verify and Finalize System & Sub-System Groupings

Perform Process Flow Analysis

Note: Only one of the following two steps is executed based on tool availability. Mixed language types, however, may require both steps. Focus on code quality in various overlapping systems/programs.

Record Manually Derived Process Flow Metrics

Record Tool Derived Process Flow Metrics

Produce Process Flow Narrative Summary

Review Process Flow Analysis Results

Data definition analysis

Note: The following steps are performed for each system input to this assessment.

Perform System-Wide Data Definition Analysis

Note: Perform next step only as it relates to systems consolidation.

Perform Physical Data Analysis

Assign Data Definition Metric Counts

Note: The main target of data definition analysis in this scenario is the record grouping analysis. Other data definition metrics may be left blank.

Calculate Data Definition Metric Scores

Produce Data Definition Narrative Summary

Review Data Definition Analysis Results

Note: The following step is a required component of this analysis. This is a critical step since it will give the first clear indication of where and how the duplicate systems actually overlap.

Assess Multi-System Data Definition Usage

General system architecture assessment

Note: The following steps are performed for each system input to this assessment. These flows will be used later to identify overlapping or potentially redundant data stores, modules, etc.

Document Batch System Information Flow

Document On-Line System Information Flow

Develop System & Sub-System Interface Map

Assess Batch Versus On-Line Update Factor

Note: The following step is a required component of this analysis.

Document Related System Interfaces

Note: The following step may disqualify utilization of certain system components, or entire systems, as becoming the baseline system required in later integration stages. Non-standard databases or languages, for example, can eliminate a system from consideration.

Identify Use of Non-Standard Technologies

Document Subroutine Interface Levels

Summarize General Architecture Analysis

Presentation layer assessment

Note: The following steps are performed for each system input to this assessment. Identification of similar or overlapping screens and reports is facilitated by this step.

Identify Batch Output Presentation Media

Identify & Categorize Batch Input Sources

Identify & Categorize On-Line Presentation Media

Summarize User Supported Environments

Record Presentation Layer Analysis Metrics

Note: Focus on summarizing overlap among presentation views among duplicate systems.

Create Presentation Layer Narrative

Data access layer assessment

Note: The following steps are performed for each system input to this assessment.

Finalize Database & Data File Inventory

Note: Redundancy analysis in the following step should be extended to look at overlap among all systems being assessed.

Assess Physical Data Usage Redundancy

Note: The following step should also note potential data integration levels.

Determine Data Integration Levels

Rate Data Architecture Conformance

Summarize Data Architecture Analysis

Application Architecture Summarization

Build Architecture Summary Metrics

Verify/Finalize Architecture Analysis Results

User backlog requirements analysis

Categorize User Backlog Requests

Uncover Hidden User Request Backlog

Note: The following step is key to linking overlapping/redundant requests across related systems. Users also should note where a request may be satisfied by a pre-existing system.

Eliminate & Consolidate Redundant Requests

Perform User Request Critical Path Ordering

Calculate Functional Quality Metrics

Note: An integrated backlog should be created and summarized as it will probably indicate that the sum of work hours required from an integrated backlog (one team working on one integrated system) is significantly lower than the sum of all existing backlogs.

Complete User Backlog Analysis Summary

Subject Area & Entity Type Analysis

Derive Current System Subject Areas

Note: The following two steps are performed for each system being assessed.

Prepare & Load Current System Entity Types

Derive Existing Entity Relationship Diagram

Note: The following step is performed using current to current and/or current to target views based on hypotheses being explored.

Perform Current to Target Data Gap Analysis

Perform Current & Target ER Model Merge

Note: Be sure to note the level of overlapping entities between systems discovered during ER model merge.

Create Subject Area Analysis Summary

Function hierarchy analysis

Note: The following steps are performed for each system input to this assessment.

Create Current Function & Process Hierarchy

Map Functions to Program Source Modules

Note: The following step utilizes top-down target model where available. If a single existing system (functionally richest of duplicates being assessed) is available and fairly cohesive in terms of functional decomposition, consider using that system as basis for comparison.

Build Current to Target Function Map

Note: This step should also summarize the amount of overlapping functionality among systems.

Summarize Functional Reusability Analysis

Function dependency analysis

Note: The following step is performed for each system input to this assessment.

Derive Current System Dependency Diagram

Note: The following step requires top-down target model.

Map Current to Target Dependency Diagrams

Summarize Function Dependency Analysis

Business Function & Entity Type Analysis

Note: The following step is performed for each system input to this assessment.

Establish Current System Matrix

Note: The following step compares duplicate bottom-up views to assess level of overlapping and unique functionality. This analysis will be key to finalizing which system is to serve as the baseline system if no top-down models are available at this stage or during integration effort performed later in this scenario.

Assess Current System Matrix Overlap

Note: The following step requires top-down target model. Could also use the cohesive baseline (one of the duplicate systems selected above) as a point of comparison.

Compare Current to Target Matrices

IS infrastructure analysis

Note: The following steps are performed for each application support area for each system input to this assessment.

Determine Staff Experience & Skill Ratings

Determine Testing Skill & Maturity Ratings

Determine IS Development Tool Ratings

Determine IS Quality & Maturity Ratings

Determine IS Summary Rating Factors

Perform Feasibility Analysis

Assessment Integration & Feasibility Analysis

Note: The following steps focus on selecting an approach (hypothesis). This scenario demands selection of a single hypothesis at this point since the complexity of integrating duplicate systems does not lend itself to dual plan development.

Develop Application Summary Metrics

Develop Assessment Findings Report

Create Redundant Systems Consolidation Plan

Create interim support plan

Create Interim Plan Outline

Correlate Analysis Requirements & Findings

Identify Positioning Tasks & Cost Analysis

Develop Pilot/Proof of Concept Plan

Note: The "finalize interim support work plan step" refers to each of the subsequent work plan steps (each belonging to a respective Positioning task) that follow.

Finalize Interim Support Work Plan

Note: Application staging estimates are developed for each of the subsequent Positioning steps listed below. These planning steps may reflect separate work plans for all or part of each system input to this scenario.

Finalize Application Staging Plan

Finalize Conversion Tasks and Work Effort

Note: This language change task planning step is optional based on required reuse of components in one or more systems that are not in a "reusable" language type (such as COBOL).

Finalize Flaw Analysis & Removal Work Plan

Determine Restructuring Work Effort

Finalize Design Improvement Work Effort

Assess Data Definition Rationalization Scope

Finalize Data Definition Rationalization Plan

Develop Literal Externalization Work Plan

Note: Perform next step only as it relates to systems consolidation. The step referenced in next phase is

Finalize Physical Data Upgrade Plan

Note: Code slicing is done on a selective basis more for its value in near term maintenance improvement than in reusability preparation. Extensive remodularization is handled in the subsequent step.

Finalize Code Slicing Work Plan

Note: The following step is driven by results of functional assessment that indicate the functional (and therefore physical) components of a given system to be reused under the integrated target architecture.

Develop Reconciliation & Re-Aggregation Plan

Note: Validation step below is used to develop an estimate to validate each Positioning step above. Multiple estimates are required for each delineated group of Positioning steps as depicted in the Prepare Redundant Systems for Integration phase of this scenario. Multiple systems typically require separate code improvement work plans.

Establish Validation Criteria & Plan

Identify Support Structure Adjustments

Integrate Interim Plan & Strategic Objectives

Create strategic redevelopment plan

Note: The functions to be derived and/or consolidated from the various duplicate system candidates must be finalized during this planning phase. This may impact work estimates established for the reconciliation/re-aggregation plan built above.

Build Strategic Redevelopment Plan

Develop Redevelopment Cost Benefit

Note: The following steps identify the work tasks and associated estimates required to complete the above two planning steps. Each step must focus on capturing and/or reconciling selected functional components from multiple duplicate systems. If a top-down target is available, it will be used for mapping purposes. Otherwise the steps below select a current system and use it as the target.

Finalize Logical Data Analysis Work Plan

Finalize Process Hierarchy Analysis Plan

Finalize Process Dependency Work Plan

Finalize Business Rule Derivation Plan

Finalize System Structure Analysis Plan

Finalize Interaction Analysis Work Plan

Finalize Dialog Flow Analysis Plan

Finalize Presentation Analysis Work Plan

Finalize Physical Data Design & Migration Plan

Finalize Program Specification Work Plan

Finalize Redevelopment Work Plan

Prepare Redundant Systems for Integration

Establish System Baseline

Application staging

Identify & Categorize Components of Interest

Create Working Version Libraries

Document Versions and Library Protocol

Synchronize Staged Source with Production

Language change/language upgrade

Note: Placement of this task within this scenario supports partial or small scale language change objectives for selected modules. System-wide efforts should refer to the Comsys-TIM language conversion scenario.

Prepare Source Code for Conversion

Convert/Upgrade Each Source Module

Perform Environmental Migration

Validation

Perform Code Quality Assurance

Compile & Link Baseline Components

Compile & Link Positioned Components

Identify Validation Data Sets

Refine Validation Data Sets

Validate Modified Programs

Obtain Validation Sign-Off

Stabilize Application Code

Note: Apply selected stabilization steps based on findings of the assessment. Systems, or portions thereof, will be improved based on freeing design analysts for subsequent redesign efforts or based on the fact that those components are the basis for subsequent rule analysis and extraction.

Application staging

Identify & Categorize Components of Interest

Create Working Version Libraries

Document Versions and Library Protocol

Synchronize Staged Source with Production

Flaw analysis & removal

Produce Detailed Flaw Analysis Reports

Note: Enter/execute following steps only as required.

Eliminate Runaway Logic Paths

Assess and Eliminate Dead Code

Review & Eliminate Active Exits

Review & Eliminate Looping Range Violations

Review and Eliminate Recursive Performs

Review and Eliminate ALTER Logic

Perform Quality Review and Finalize Changes

Code restructuring

Create Detail Restructuring Analysis

Perform Program Structuring Adjustments

Establish Restructuring Parameters

Perform Source Code Restructuring

Design review & improvement

Optimize Program Size

Optimize Procedure & Paragraph Size

Eliminate Logic Spikes & Reduce Complexity

Review and Correct Switch Variables

Review and Improve Procedure Names

Review & Refine Table Handling Techniques

Finalize Design Review & Improvement Task

Validation

Perform Code Quality Assurance

Compile & Link Baseline Components

Compile & Link Positioned Components

Identify Validation Data Sets

Refine Validation Data Sets

Validate Modified Programs

Obtain Validation Sign-Off

Standardize System-Wide Data Definitions

Note: Apply selected data definition standardization steps based on findings of the assessment effort.

Application staging

Identify & Categorize Components of Interest

Create Working Version Libraries

Document Versions and Library Protocol

Synchronize Staged Source with Production

Data name rationalization

Setup Data Name Rationalization Libraries

Review Record Grouping Analysis

Build Composite Record Definitions

Identify & Reduce Homonyms

Apply Descriptive Composite Names

Propagate Composite Record Definitions

Review and Propagate Secondary Names

Reconcile DNR Source with Production

Validate & Implement Rationalized Code

Validation

Perform Code Quality Assurance

Compile & Link Baseline Components

Compile & Link Positioned Components

Identify Validation Data Sets

Refine Validation Data Sets

Validate Modified Programs

Obtain Validation Sign-Off

Application staging

Identify & Categorize Components of Interest

Create Working Version Libraries

Document Versions and Library Protocol

Synchronize Staged Source with Production

Literal externalization

Note: This task is performed optionally based on a requirement to capture and externalize embedded data within current system. Perform no more than one of the following three steps.

Perform Literal Group Analysis

Create Tables from Literals

Externalize Embedded Literals

Validation

Perform Code Quality Assurance

Perform Data Quality Assurance

Compile & Link Baseline Components

Compile & Link Positioned Components

Identify Validation Data Sets

Refine Validation Data Sets

Validate Modified Programs

Obtain Validation Sign-Off

Physical data upgrade

Note: Perform following only as it pertains to physical file merge. Merger of physical files typically involves some expansion or consolidation and potentially some conversion.

Verify Physical Data Integrity

Purify Physical Data

Expand & Convert Physical Data

Validation

Perform Data Quality Assurance

Remodularize Selected Source Code

Note: Code slicing is a short-term, high pay back task that reduces work associated with code reconciliation & re-aggregation. If large modules do not exist (no immediate slicing need), slicing may be integrated in code reconciliation & re-aggregation.

Application staging

Identify & Categorize Components of Interest

Create Working Version Libraries

Document Versions and Library Protocol

Synchronize Staged Source with Production

Code slicing

Develop Program Slicing Analysis

Perform Program Slicing Process

Perform Alternative Slicing Technique

Re-Configure Slice Related Components

Validation

Perform Code Quality Assurance

Compile & Link Baseline Components

Compile & Link Positioned Components

Identify Validation Data Sets

Refine Validation Data Sets

Validate Modified Programs

Obtain Validation Sign-Off

Application staging

Identify & Categorize Components of Interest

Create Working Version Libraries

Document Versions and Library Protocol

Synchronize Staged Source with Production

Code reconciliation & re-aggregation

Note: The scope of this task is governed by the reusable components discovered during function hierarchy analysis. Reusable processes may be isolated during this task at the physical code level prior to entering Transformation. See task objectives for more insight.

Build Reconciliation & Re-Aggregation Analysis

Note: The scope of the following step is limited to redundancy identified within a system. Cross system redundancy will be handled during Transformation.

Eliminate & Reconcile Redundant Processes

Re-Aggregate Segregated Functions

Validation

Perform Code Quality Assurance

Compile & Link Baseline Components

Compile & Link Positioned Components

Identify Validation Data Sets

Refine Validation Data Sets

Validate Modified Programs

Obtain Validation Sign-Off

Develop Integrated Application Architecture

Finalize Integrated Data Architecture

Logical data analysis

Load & Merge Bottom-Up ER Model(s)

Note: The following step is used to integrate existing system data usage. If this is the basis for the target system (i.e. no top-down model), extensive effort must go into reconciling redundant entities and attributes.

Refine Bottom-Up Derived ER Model

Note: The following step is optional based availability of top-down model based on the redevelopment option selected.

Merge Top-Down/Bottom-Up ER Models

Note: The following step creates normalized data model representing an integrated/consolidate view of existing stand alone systems and new data as defined by top-down view or added to the integrated bottom-up view.

Normalize Merged ER Model

Review and Sign-Off Normalized Data Model

Develop Integrated Process Models

Process hierarchy & dependency analysis

Note: The following step is performed on a system by system basis.

Derive Bottom-Up Process Hierarchy Model

Note: The following step is used only where no top-down model is available based on a bottom-up selected approach (hypothesis).

Redesign Bottom-Up Process Hierarchy(ies)

Note: The following step is used to integrate existing system processes where no top-down model exists - it is mutually exclusive with the subsequent top-down step. Uses existing baseline system, selected in assessment planning phase, as target set of models.

Merge Bottom-Up Process Hierarchies

Note: The following step relies on availability of top-down model.

Integrate Bottom-Up & Top-Down Hierarchies

Finalize Target Process Hierarchy

Develop Bottom-Up Process Dependencies

Note: The following step integrates existing process dependencies where no top-down model exists and is mutually exclusive with subsequent top-down step.

Merge Bottom-Up Process Dependencies

Note: The following step relies on availability of top-down model.

Merge Current & Target Process Dependency Models

Finalize Target Process Dependency Model

Business rule analysis

Derive Bottom-Up Process Action Diagrams

Merge Processes into Target Action Diagram

Refine Completed Process Action Diagram

System structure analysis

Note: Perform the following step for each existing system being integrated.

Derive Current System(s) Structure Chart

Build Target System(s) Structure Chart

Interaction analysis

Note: Perform the following step for each existing system being integrated.

Build and Refine Current System Matrix

Build and Refine Target Application Matrix

Complete Integrated & Consolidated Design

Dialog flow analysis

Note: Perform the following step for each existing system being integrated.

Assess Current System Dialog Flows

Perform Dialog Flow Gap Analysis

Create Target Dialog Flow Diagrams

Presentation analysis

Note: Perform the following step for each existing system being integrated.

Categorize Existing Screen/Report Layouts

Perform Presentation Functional Analysis

Determine Reusability Under Target System

Refine Target System Report & Screen Design

Program specification

Note: Emphasis of these steps is to reconcile redundant procedures to create new consolidated system.

Capture & Import Reusable Procedures

Finalize Target Procedure Action Diagrams

Finalize Data Integration Phase

Physical data analysis & migration

Finalize Physical Data Model

Note: Data migration under the integration scenario places a significant emphasis on the reconciliation and consolidation of redundant or overlapping physical data.

Perform Physical Data Migration Process

Gain Physical Design & Migration Plan Sign-Off