Hi
Dave
I'm
sure that others who have gone through similar processes will be able to offer
more advice, but my thoughts on your dilemma are as follows:
With a
go live date of 15th May, your only option is to go with vanilla out-of-the-box
functionality. It's probably going to take you that long to set up the new
server, plan what data needs to be migrated (config, asset/cmdb, live tickets
and history) and get that done, and do some simple testing. Also, if you have
any external integrations for data sources, such as people data, those obviously
need to be in place. By itself, just doing that lot is probably optimistic
for less than 2 weeks. Also, don't forget the licensing implications of going
from change lite to full CM.
Doing
a gap analysis between your current processes/functionality and what is in the
OOTB applications is a task that is going to need a thorough understanding of
both applications, and many sessions with process owners to identify the
changes, see where new functionality replaces that in the existing apps, and
plan what changes are really needed in the new app. My guess is that
this sort of process is going to take at least a couple of weeks (with
proper buy-in and time from the process owners), and having identified the
changes needed, another period of time after that to develop, test and migrate
the new changes..... and then there's user training. And don't forget
proper documentation of your changes this time too ! Ball park, I'd guess you'd
need a couple of months, depending on the level of changes
needed.
I
think you need to make sure that people know that what is being asked really
isn't possible; either they need to change the go-live date and then plan a
proper migration strategy with enough resources, or accept the vanilla app,
prioritize the changes needed, and plan incremental functionality changes after
the go live date. The most important issue is to get them to accept the
problem now rather than waiting until a couple of days before they expect to go
live.
Looks
like you're going to have an 'intersting' couple of months ahead. Hope this
helps some
David Sanders
Remedy Solution Architect
Enterprise Service Suite @
Work
==========================
ARS List Award
Winner 2005
Best 3rd party
Remedy Application
tel +44 1494 468980
mobile +44 7710 377761
email [EMAIL PROTECTED]
__20060125_______________________This posting was submitted with HTML in it___-----Original Message-----**
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED]On Behalf Of Dave Barber
Sent: 03 May 2006 11:12
To: arslist@ARSLIST.ORG
Subject: Migration from Helpdesk 4 to 6 ... timescalesAll,Just a little history first.We've been running helpdesk 4/ARS 5.1.1 for quite a few years. We had our test server upgraded to ARS 6.3, ITSM 6 towards the back end of last year, but work pretty much stopped as performance was seriously bad.After a lot of badgering of management, we finally got two new servers in place - one is in place and running with our test apps (ARS 6.3, ITSM6), the other is just sitting idle .... (which is a continual wind up, as our live server is having serious problems with its workload, I'm sure that the app and data migration onto that would be a pretty minor process).Anyways, to cut a long story short, the planning/testing/etc for the migration just hasn't been happening due to timescales and staffing issues (sickness, holidays, and people just not seeming to be interested). My manager has finally decided to allow me to allocate a lot more of my working day to getting the migration planned, tested and doneWhat has really gotten me interested/concerned is the timescales. In effect I'm having to start from scratch, as none of my colleagues have really documented what they've gone through, and I've been told that I have to get it all ready for 15th May. Scoping the whole application, getting necesary changes made, test data migrations, and the one I dont like - our change management is totally different to the standard packaged application (its based on the v4 lite change application, but with a lot of changes)I really, really don't think that a week and a half is sufficient to get this migration completed, especially with the decision making processes - any changes that I want to make to the standard application will obviously have to be agreed upon, not just by my manager and my immediate team, but by key users of the applications (who I'm sure will want other changes as well).Anyone else think that I'm going to have a difficult time with this?RegardsDave__20060125_______________________This posting was submitted with HTML in it___
