CASE STUDY

Case Study: Drain-O-Mite UK Ltd

Table of Contents

1.Introduction1

1.1 Purpose of document1

1.2 Scope1

2.Installation2

2.1. Deployment plan2

2.2. Data migration2

2.3. Training5

2.4. Documentation7

2.5. Business change issues8

2.6. Installation schedule9

3.Support9

3.1. Support needs9

3.2. The ISST Help Desk10

3.3. Issue tracking and escalation11

3.4. Support service levels12

3.5. Benefits of the support service13

4.Project failure13

5.Use of feedback15

Bibliography16

Appendcies18

Case Study: Drain-O-Mite UK Ltd

Introduction

1.1 Purpose of document

The purpose of the report is to plan a project based on the installation of DOMINO development project at Drain-O-Mite UK Ltd. Specifically this report presents the overall plan of installing the IS system i.e. EPOS system to upgraded DIPS system.

1.2 Scope

The project plan includes the overall project characteristics in order to successfully installed the DOMIN O linking EPOS system to upgraded DIPS system. The project includes the Project brief, including feasibility assessment, Project Initiation Document (PID) including baseline plan. Analysis & desgin phase in which istallation plan and support plan are discussed in detail. The project also includes any failure and risk assessment strategies.

This project not includes the critical path method for estimation of the project along with the risk assessment work.

It is assume that all the resources are ideally avaiable in order to execute the project including the finance required, time availability, materials and expertise labour are available.

Installation

2.1. Deployment plan

The team's approach for developing the Deployment Plan was to prepare a comprehensive equipment list and timeline highlighting key milestones for deploying DOMINO project. To track software development activities, the team has created a prioritization matrix that includes two major software builds for the DOMINO. In addition, several plans describing risk management, CM, maintenance, and training have been defined to manage the deployment activities effectively and efficiently.

2.2. Data migration

What data is required in the new system?

For the DOMINO, the new system requirements must be identified. The Host system which is connected to PATA EDOM should meet system requirements at minimum.

Power Requirement

Voltage: DC +5V ± 5%

Operating System

Windows 2000/XP

Linux

DOS

WinXP Embedded

WinCE

Interface

IDE (ATA) Standard Interface

Specifications

Compliant with ATA-7 V3 specification.

Supports PIO modes 0 ~ 6

Supports Multi-Word DMA Modes 0 ~ 4

Supports Ultra DMA Modes 0 ~ 4

Supports ECC (Error Correction Code)

Supports Wear-leveling

Is there any existing data that is not required in the new system?

The existing data to be migrated includes a single proprietary inventory system known as DIPS (Drain-O-Mite Inventory Procurement System), operating as a client-server system across a newly-installed WAN, with a single database server in the Nottingham ISST department. DIPS was used for transaction processing (stock movements, purchase ordering, etc.) in the LDCs and supported basic management information reporting at the Nottingham HQ.

How existing data will be transferred?

This section is the most important aspect of the project in which the migration of old/existing IT system data to be transferred in to new syste. It will done by applying certain tools and techniques so that the quality of the data may not disturbs and data may be merged properly with the new systems.

Once the decision is made to perform data migration and before migration can begin the following analyses must be performed: ...