Feasibility study

Network Design and Implementation: Steps

1. Feasibility study

2. Network Project Plan

3. Description of the Current Network

4. New Network Requirements

5. Identifying Geographic Scope

6. Circuit Requirement Calculations

7. Network Security and Control Requirements

8. Network Configurations

9. Network Cost Calculations

10. Implementation

1. Feasibility Study

The purpose of a feasibility study is to determine the possibility of improving the current network or developing a new network.

The primary purpose of the feasibility study is to identify the problem which could be solved or an opportunity which could be ceased by the network development project (clearly, in writing).

The feasibility study can be based on

a needs assessment in the organization

competition

a business opportunity

inter-organizational relationships

globalization

etc.

1. Feasibility Study continued...

The result of the phase is a Feasibility Study Report:

the problem or the opportunity described

objectives for the potential network development project (major, intermediate, wishes)

potential solutions (one is never enough)

technical, operational, and economic feasibility of potential solutions

recommendation

The Feasibility Study usually results in a decision

start the network development project

extend the feasibility study (clarifications, new alternative solutions, change of scope)

postpone the project

reject.

Some Examples of Objectives for NW dev.

implementing an electronic commerce business idea (e.g., electronic payment services for small businesses using EDI, the WWW and the Internet)

competitive advantage

improving quality of service

faster delivery of information/digital products

implementing virtual teams

need to improve

communications channels

need to bust organizational boundaries

need to reengineer

improving the corporate infrastructure

cost containment

increasing volumes

increasing productivity, flexibility of the work force

responding to uncertain futures

2. Network Project Plan

The purpose of the Network Project Plan is to

describe project phases

produce project resource plans (people, hours, equipment, funding etc.)

describe the project organization

produce timetables

determine checkpoints

define deliverables

evaluation criteria for the network development project

The result of the Network Project Plan phase is a detailed report which describes the concrete steps, timetables, resources and funding requirements for reaching the objectives defined in the feasibility study.

3. Description of the Current Network

The purpose of the Description of the Current Network is to gain complete understanding of the current situation in order to design the network.

This translates into:

1. describing the current network

applications and their data transmission needs

nodes and their operating systems

networks (network types, operating systems, devices and circuits)

descriptions are presented in the organizational context (geographical locations, organizational units, ranks and numbers of users, informal organizations)

2. describing the information needs for the new network (see 1.)

3. Description of the Current Network continued...

Techniques include

interviews

researching the applications and networks

estimating and sampling for volumes, timings and patterns

comparing the current network and existing alternatives.

The result of the phase is a Current Network

Description. It includes

organization charts

geographical network configurations

summaries of interviews

summaries of comparisons

data flow diagrams

sampling results

meeting minutes etc.

evaluation of the current network

design ideas gained

4. New Network Requirements

The purpose of New Network Requirements phase is to produce a list of requirements for the new network.

Requirements are derived from the objectives (see Feasibility Study) and refined by the results obtained in previous phases.

Requirements are influenced by the the organization’s long and short term plans (strategic plans, IT strategic plans, plans of refocusing the business changes in products or services, organizational change, growth, downsizing,

acquisitions, mergers, spin offs etc.)

The result of the Network Requirement Phase is a detailed list of business requirements translated into technical requirements (e.g., circuit capacities, processing times, reliability, security, speed requirements).

Requirements can be mandatory, desirable or wished.

5. Identify Geographic Scope

The purpose of Identifying Geographic Scope is to produce an accurate, detailed geographic map of the new network.

The scope of the network can be:

international

country

city or state

local facility

Start with the highest level

Draw connections (lines, concentrator sites, multipoint locations)

for international, country, city or state use maps

for local facilities use blue prints of the building

The result of the phase is detailed maps and drawings of the new network.

6. Circuit Requirement Calculations

The purpose of Circuit Requirement Calculations is to produce a detailed estimate of the transmission capacity required.

Circuit Requirement Calculations include

total characters transmitted per day (and/or hour) on each circuit (average or peak circuit traffic)

message volumes (current and estimated) (accuracy often not major concern)

response time criteria and evaluations

The result of the phase is traffic analysis reports. Circuit requirements are added to the maps drawn in the previous phase (5. Identify Geographic Scope).

7. Network Security and Control Requirements

The purpose of Network Security and Control Requirements phase is to include all security and control mechanisms into the new network plans.

Security and control requirements are derived from the organization’s security policies.

The result of the Network Security and Control phase is a detailed document of the security and control requirements concerning the new network. This document refers to the geographic maps and blue prints.

8. Network Configurations

The purpose of Network Configurations phase is to configure the circuits, hardware, and software between the computers in the network.

The steps (iterative):

evaluating software (may limit hardware and network protocol choices)

evaluating hardware

designing the type and

placement of network circuits choosing network protocols (e.g., TCP/IP, SNA)

considerations: internetworking, expansion, inter-organizational needs

(don’t forget diagnostics and maintenance tools)

use models and simulations where needed.

The result of Network Configurations phase is several alternative network configurations.

9. Network Costs

The purpose of the Network Cost phase is to produce cost/benefit analysis for the alternative configurations.

Sources of costs:

circuit costs

internetworking device costs (repeaters, bridges, gateways etc.)

other hardware costs (servers, cards, memory, printers, desktop computers etc.)

software costs (network

operating system application software, middleware, protocol conversion software, etc.)

network management costs (special hardware, software, and training needed to develop a network management system)

personnel costs (network administrator, consultants, technicians etc.)

testing and maintenance costs (monitoring equipment and software etc.)

security costs (security software, hardware, personnel)

9. Network Costs continued...

Types of costs:

initial versus recurring costs

direct versus indirect costs

the problem of identifying intangible benefits

The result of the Network Cost phase is a Request for Proposal (RFP).

RFP is a detailed requirements document for vendors.

Its list of contents includes:

Organizational background information

Network Requirements

Service Requirements

Description of the Bidding Process

Information Required from Vendor

10. Implementation

Implementation phase includes “making it work” and evaluating the new network against the evaluation criteria.

Strategies:

a pilot project

chronological cutover

phased implementation

direct cutover (not recommended)

Follow-ups for several months.

The result of this phase is the new network in production

A feasibility study is usually conducted for a single application or small group of related applications. The level of detail included in a feasibility study sits between that of an information systems plan and the more detailed requirements specifications. If an information systems plan exists, a feasibility study should refine and build on the core work products developed during the planning project. If a significant amount of time has elapsed since the information systems plan was developed, care should be taken to include any significant business changes that may have occurred.

FS1 Define Project Scope

FS2 Activity Analysis

FS3 Needs Analysis

FS4 Conceptual Modelling

FS5 Use Case Modelling

FS6 Identify Non-Functional Requirements

FS7 Identify Options

FS8 Select Option

The feasibility study generates a number of options for acquiring a new application. These options are evaluated for technical and financial feasibility

FS9 Plan Acquisition Strategy

FS10 Develop Business Case

a Business Case for the proposed acquisition is developed.

FS11 Package Feasibility Study

THE FEASIBILITY STUDY

Is it possible?, is it practicable?, can it be done ?

Not only economic feasibility, but also technical feasibility, schedule feasibility, operational

feasibility .

Economic feasibility - are the benefits greater than the costs? (see CBA)

Technical feasibility - do we ‘have the technology’?; if not, can we get it ?

Schedule feasibility - will the system be ready on time ?

Operational feasibility - do we have the resources to build the system?, will the system be

acceptable?, will people use it?

FEASIBILITY ISSUES

We cannot properly answer many of these questions at this stage.

For example, data on actual costs and benefits is not available, we don’t know what resources will be at our disposal.

The feasibility study is an educated guess. Often a ‘rough and ready’ approach’

Some elements of feasibility will be more important than others and some may directly conflict.

Sometimes ‘external considerations’ are more important than the narrow feasibility issues discussed here.

OTHER QUESTIONS ADDRESSED IN THE FEASIBILITY STUDY

What are the requirements of the users?

What data is needed? Where does it originate? How much data is needed?

What are the main functions and characteristics of the proposed system?

What are the design alternatives? ( e.g. simple v sophisticated, manual v computer)

What are the development alternatives? ( which methodology?, do we need prototyping or pilot studies?)

Is all of this consistent with the business and IT strategy?

THE FEASIBILITY REPORT

The feasibility study will normally be carried out by analysts or consultants who interview potential users and review documentation.

The feasibility report should include a description of functional requirements and possible alternative solutions.

It should cover the four aspects of economic, technical, schedule and operational feasibility together with recommendations on the best way to proceed.