Approval
Agreed
simon
-----Original Message-----
From: KAEMPF Stefan
Sent: 28 May 2014 15:44
To: MARSDEN Simon
Cc: BROGAN Kevin; SMYTH David
Subject: APP004 - new initiative
Dear Simon,
I am interested in decommissioning Change Control (MCC) and starting to use UniDesk's CMDB and Change & Release modules.
This is not a simple tasks and requires more than just migrating data from MCC to UniDesk, but requires stabling how we are going to represent our Configuration Items (CIs) in CMDB as well as updating process documentation.
Based on that I would like to use an APP004 process initiative to manage the work. I do not have detailed estimations yet, but we (Iain, Heather, Alex, Matt and myself) have discussed that we believe we will need about 40 days, 10 days this financial yer, 30 next year).
Are you ok to approve this project?
I have started writing a project Brief (see below) which may provide you with some more details, please let me know if you have any questions.
Thank you,
Stefan
///Background
IS Applications use an in-house developed change control application (MCC) to record LIVE changes to infrastructure and software. Change MCC covers both support and project related changes, for in-house and supplier based applications which are hosted by by IS Applications. The Change Control application has been developed more than 10 years ago.
MCC has has two components which work tightly together:
Change Management Database (CMDB)
Change records (Change and Release)
The long term plan was to replace MCC by using UniDesk modules. Change and Release module was launched in 2013 and CMDB was just launched in May 2014.
///Scope, Objectives and Deliverables
Scope:
The scope of this project is to move all Configuration items currently recorded in MCC to CMDB and update and/or create all relevant documentation used by IS Applications to use and maintain the CMDB. Out of scope is to migrate change records from MCC to CMDB. The Change records will be kept in MCC.
Objectives:
O1) migrate the configuration details from MCC to CMDB
O2) provide policies and process documentation how to use and maintain CMDB
Deliverables:
D1) agree structure and attributes for CI's to be used within CMDB
D2) Document agreed structure and attributes for CI's to be used within CMDB
D3)migrate all CDIs from MCC to CMDB.
- High and Medium priority services will use the new agreed structure and attributes
- other services will only migrate the server and service CIs in order to reduce the cost of migration. The other CIs will not be generated in CMDB by this project, but will be done whenever project or support work in future is performed against these services.
D4) Training for UniDesk operators covering these tasks:
- CMDB maintenance
- Change and release
D5) All IS Applications documentation regarding Change Control is updated to reflect the usage of CMDB instead of MCC
///Benefits
B1) CMDB is integrated with the wider ITIL processes which will ensure that processes such as Incident Management and Problem Management will benefit from moving from MCC to CMDB
B2) MCC is older than 10 years and it is no longer maintainable.
B3) CMDB allows more complex documentation of relationships as well as more details regarding CI attributes. Although not all of these new capabilities will be used as part of this project, it will be possible to do so in future.
B4) CI relationships are easier to be visualised and better reporting facilities will be available.
Success Criteria
S1) MCC can be decommissioned
S2) Incidents and Problems in UniDesk can be linked to specific CIs
S3) IS Applications use Change & Release for all support and project delivery
S4) IS application staff are able to easely visualise service setup and generate reports of service dependencies.
S5) Documentation how CMDB is setup/maintained as well as Documentation regarding the change process is in place