Managing New HW and SW Installs

[dsemeniuk]

We are currently in the process of creating our production environment and want it to be under change control as we get ready for going live with our new system.

Does this process seem reasonable:

Harwdware Process

1. Submit RFC as to what Hardware is wanted to be built with specs

2. Change Management reviews, approves and schedules

3. Configuration Management enters new HW CIs with appropriate status

Software Process

1. Submit RFC for what software is needed to be installed on the new HW

2. Change Management reviews, approves, schedules

3. Configuration Management enters relationships of CIs as the SW Ci probably already resides in the CMDB from the other environments


We are having a problem with the production environment build out as people don't want to submit RFCs and just go build things and install. We encountered a problem already with licensing issues as the software install wasn't reviewed properly and change and release management were not aware of the installation and why, where etc...

Just want to confirm that this makes sense to do this as I do not know of any other way that we can properly track the new CIs and get then entered into the CMDB without submitting an RFC upfront.

[Cotswolddave]

It might be a good idea to define an internal asset lifecycle at at what stage a change request applies, plus when is something entered onto the CMDB/change system.

Example asset lifecycle

Need identified - new server required for project
Technical review - h/w, s/w required
Sourcing - buy, use of stock, etc.
Detailed design - how/where to deploy
Build - could separate h/w and s/w
Deploy - Physical install
Handover - go live
In service
Not in service
Decommission
Disposal

Often for ITIL change processes an RFC may only need to submitted for deploy and changes to in-service boxes. The rest is project activities or tasks where the box may have no name or reference other than an asset number. So you couldn't submit an RFC that woudl be meaningful.

Asset management however should track all the stages of your lifecycle so you know whats wanted, whats on order, whats in stock, where something is, whats its refresh date etc.

If you classified service request and change requests separately, then it may help.

Dave