It's quite clear that ideas from Continuous Service Improvement (CSI) activities will end up as Request for Change at some point. In fact the v3 CSI manual states:
What I want to know is when does the control pass from CSI to Change Management?Once CSI has come up with a recommendation for improvement, a change request is submitted.
The issue which has prompted this question is as follows:
Another part of the IT department have developed a CSI process for one of our major systems (and about time to) but it basically just pulls together the multiple ways improvement ideas are logged and processed. The suggested CSI process has six steps: log, assess, approve, plan, implement and review.
As the change manager it's blindingly obvious that this process an exact copy of an ITIL change process so I believe the new "CSI" process should be managed within the change management function and that the only true bit of CSI is initiating the ideas.
Although most people can see where I'm coming from, they want the business to own the assessment and approval of ideas, only handing over to change management when ideas have been approved. The main reasons they give are that only the business understand which ideas/changes are valid but my response is that, as the change manager, I can't assess or approve the ideas/changes but I at least can own and facilitate the process to ensure it runs smoothly and compliments other ITIL processes.
Before I turn into a broken record and start contradicting my own points, can anyone shed any light onto when control should pass from CSI to Change?