FEASIBILITY STUDY SERVICES

If you are embarking on a large or potentially high-risk project, you will be needing to establish feasibility of one or more solutions with cost projections. Using our Feasibility Study services we can help you assess options and develop a sound business case on which to proceed. We synchronise the feasibility study conclusions with the prevailing enterprise architecture.

For a Feasibility Study our methodology delivers a standard report with the following sections:

Introduction

In which we present:

• background of the proposed study;
• the methodology used for performing the study;
• any reference materials used in conducting the study;
• the purpose of the study.

Management Summary

We present the summary findings of the study, describing the recommendations and conclusions. We summarise the approach to take the recommendation forward together with costs and return on investment projections. We also present the primary reasons for rejecting the alternate options.

Current Business Architecture

We illustrate in high level terms the constituent views of the "As Is" business architecture relating to:

• processes (manual and automated);
• organisational locations;
• organisational structure and governance;
• roles and responsibilities of key staff;
• business volumetrics;
• the supporting organisational culture as appropriate.

We show how these elements combine to deliver the current business capability.

Current Technical Architecture

We illustrate in high level terms the constituent views of the "As Is" technical architecture relating to:

• applications;
• data;
• physical hardware and network infrastructure;
• security.

We show how they combine to support the business capabilities. We also capture any operational constraints and issues relating to performance or capacity.

Requirements

In this section we describe the requirements and objectives sought of a new solution. Illustrating the key areas of change as they relate to the existing business and technical architectures.
We also state any known constraints and record any assumptions made in relation to the "As Is" architectures or requirements of the proposed future options.

Methodology

In this section we describe the method or strategy employed (e.g., survey, weighting, modeling, benchmarking, and simulation) to evaluate the proposed options and to arrive at the recommended option.

Recommended Option

Here we illustrate the option determined as the most appropriate solution for the stated requirements. We state the rationale that supports the recommendation of the option in itself and as it relates to the alternate options. More specifically, we describe the recommended solution in terms of:

• "To Be" Business architecture (and its constituent views);
• "To Be" Technical architecture (and its constitutent views);
• Strategy for transition from the "As Is" position to the "To Be" position;
• Cost, Benefit and Return-On-Investment estimates.
• We also state any outstanding issues and assumptions that may need to resolved in subsequent work.

Alternate Options

The rejected options are described and presented in summary form with rationale for rejection.