Dismiss
InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

Office Productivity Suite Transformation Method

IP.com Disclosure Number: IPCOM000186027D
Original Publication Date: 2009-Aug-06
Included in the Prior Art Database: 2009-Aug-06
Document File: 4 page(s) / 169K

Publishing Venue

IBM

Abstract

Office productivity software suites provide word processing, spreadsheet and presentation applications. As the number of vendors offering office productivity software suites increases, many organisations today wish to evaluate which product is most appropriate and cost effective for use across their enterprise and then implement a project to transition from their current suite to the newly selected suite. This disclosure describes a method to shape and deliver such a transformation.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 30% of the total text.

Page 1 of 4

Office Productivity Suite Transformation Method

Disclosed is an "Office Productivity Suite Transformation Method" - it is a flexible framework of structured phases and activities that provides a systematic way for organisations to shape and deliver their technical office productivity software suite transitioning project. It is an effective approach to reducing the associated risk, cost and technical complexity typically incurred when introducing a new office productivity software suite into an organisation, and moving existing content and users to the new software suite, an example of this is moving from Microsoft* Office to IBM Lotus** Symphony.

    The method framework illustrated below in Figure 1 - comprises a set of five horizontal phases, each have a set of activities represented vertically - each activity is completed in turn as a prerequisite to moving to the next phase. Taking this approach ensures all activities are carried out by the project team in sequence, reducing both risk, complexity and cost of moving across to a new office productivity suite.

Figure 1 Office Productivity Suite Transformation Method

    Within each phase there is a set of predefined activities, these should be carried out in sequence top to bottom to complete all activities within the phase, allowing the next phase to be started.
The initiate phase is focused on the project startup, team formation and definition of the project (what is to be achieved, how, timescales, costs and deliverables).

The Plan phase centres on activities such as surveying existing users to understand which applications they use from their current vendor, how they use them, frequency of use along with details of key files created using their existing office productivity suite they use within their job, plus any dependancies with 3rd party or enterprise solutions. A key aspect of this phase is the ability to understand which users or departments would be suitable for the transition to a

[This page contains 1 picture or other non-text object]

Page 2 of 4

new office productivity suite, eg Microsoft Office to IBM Lotus Symphony.
The Pilot phase embodies those activities that would be undertaken to create and run a technical pilot based on the new office productivity suite they have targeted for deployment to ensure it can replace the existing office productivity suite for the previously identified users or departments. This also allows the creation and testing of education and support functions and the collection of information required for an enterprise deployment.

The Deploy phase encapsulates those activities that would be undertaken to physically deploy the new office productivity suite to targeted users personal computers and the removal the existing product. Migration of file content to the new / open standards would also be carried out here.

•...