Module CC3002 Post Implementation Issues Lecture for Week 2 AY 2013 Spring

Installation System Installation Data Migration Deployment Business Change Training Documentation

Installation Issues Technical Issues: Installing IS Components – Hardware – Software – Network/Communication – Data Migration/Set-up

Installation Issues Social Issues: Human Factors – Training Users – Educating People (Selling System) – Business Change Overall Deployment Strategy

Client Server Architecture Client connects to Server for required remote processing e.g. data access Remote processing on the Server Local Processing on Client Processing is shared between Client and Server

Client Server Architecture

Software - Category System Software – Operating System – Utility Software Application Software – General Purpose – Specific Purpose Chaffey(2003)

Technical Installation/Configuration May need to install and configure hardware (server/client) May need to install (part of) network (for IS, some/all hardware, network may be in place) Will need to install (server application software, database, client application software)

Software Modules Application specific software is often developed in a modular fashion: – Lead Management Module – Requisition Management Module – Student Module – RTE Module – Financial Module Possible to Install some modules without having to install all modules

Software Migration How is software migrated to operational environment? Typical Software Migration Process Development TestProduction

Data Migration Existing Source of Data ? – Existing Paper Records – Existing Information Systems – New Data Data May be Converted using ETL Process

Extract-Transform-Load Existing System Transformation Process New System

Data Migration- Transfer Change Structure Change Format Add New Attribute(s) Remove Existing Attribute(s) Change Sequence (order of attribute)

Data Migration- Example Staff Details: Old Record Staff Details: New Record

Data Migration- Example

Deployment Options Existing SystemLiveLive New System Direct Change Over/ Immediate Cut Over

Deployment Options Existing SystemLiveLive New System Parallel Running

Deployment Options Existing SystemLiveLive New System Phased Modules

Deployment Options Existing SystemLiveLive New System Phased Geographic

Deployment Options Existing SystemLiveLive New System Pilot Running

Deployment Options Consider the Impact Of – Staffing – Workload – Cost – Time – Updates – Discontinuing of System

Business Issues during Installation Business Continuity – Cannot stop all work for installation Successful Installation – Key Process Testing Contingency Plan – What to do if things go wrong? Business and Organizational Change

Business & Organizational Change Change Causes Disruption to Staff – Changes to pattern of work – New roles/responsibilities – Risk of redundancy – Feel threatened by new technology – Users make mistakes – Need training – New system isn’t PERFECT either

Phases of Change

Change Program Should run alongside system development project Get users involved in the process Project Management – Identify a user project management to coordinate the business change management – Identify champions and change agents

Training Who to train? – Identify Users – What do the users need to know What to train? – Different users have different requirement – Tailor training to specific user groups

Training Planning the training – Who, How and Where? – Development Team, online, on the job Conducting the training – Train the trainers – Timing (when is system going LIVE?)

Documentation Maintenance of System – Why was this done? – How was this done? – Why was it done this way? For End Users – How do I get system to do ….? – What does this error message mean?

Summary – Need to Consider Technical Aspects – Hardware/Software – Data/Documentation Human Aspects – Impact on Staff/Workload – Training – Impact on Business

Thanks Y Thank You.