SLAMs Change Management Control software is a comprehensive change management solution that enables users to track, manage, and control change in a fully web based environment. Developed specifically in response to the needs of clients from companies both large and small
Member for
23 years 3 months
Member for23 years3 months
Submitted by Rahmat Hidayat on Mon, 2006-04-17 22:26
Your explaination is about changes in relation with Client. Its change authorization. But what I mean is change control system for internal purpose, to control our working budget due to growth in design, miss estimate, change in method, etc.
A change control system is very simple. Most projects have one of these. The concept is very simple – prior to any change being implemented the client must be given the opportunity to approve this change and just as importantly, approved the implications of the change.
Change can come from almost anywhere – from the client, a designer, an engineer, a contractor, a statutory authority. If change was uncontrolled, costs could rise dramatically and the programme could be extended and so through the change control process the client is made aware of the cost of the change and the programme implications of the change, before the change is instructed. In this way the client is approving the change in the full knowledge of the implications.
It normally works like this…..
1. Somebody completes a change request form, setting out what the proposed change is and why it is needed.
2. To the form is added the cost implications of the change
3. To the form is then added the programme implications of the change
4. The form is then passed to the client for approval of the change
It is very simple indeed.
Who does what on the form and who controls the whole process is dependent on the contractual arrangements of the project.
Very often the system is all electronic, either using databases or even as simple as spreadsheets. Most larger organisations have an in-house system for dealing with this. Often, it is built into bespoke management systems, but don’t let that worry you – the principle is the same whatever system is used – it is an approval process that allows the client to sign off the full implications of change.
In respect of the programme, the client is aware if the programme will be affected / delayed before he / she approves the change.
Member for
22 years 3 monthsRE: Change Control System
SLAMs Change Management Control software is a comprehensive change management solution that enables users to track, manage, and control change in a fully web based environment. Developed specifically in response to the needs of clients from companies both large and small
Member for
23 years 3 monthsRE: Change Control System
Hi Gary,
Your explaination is about changes in relation with Client. Its change authorization. But what I mean is change control system for internal purpose, to control our working budget due to growth in design, miss estimate, change in method, etc.
Regards.
Member for
21 years 11 monthsRE: Change Control System
Rahmat,
A change control system is very simple. Most projects have one of these. The concept is very simple – prior to any change being implemented the client must be given the opportunity to approve this change and just as importantly, approved the implications of the change.
Change can come from almost anywhere – from the client, a designer, an engineer, a contractor, a statutory authority. If change was uncontrolled, costs could rise dramatically and the programme could be extended and so through the change control process the client is made aware of the cost of the change and the programme implications of the change, before the change is instructed. In this way the client is approving the change in the full knowledge of the implications.
It normally works like this…..
1. Somebody completes a change request form, setting out what the proposed change is and why it is needed.
2. To the form is added the cost implications of the change
3. To the form is then added the programme implications of the change
4. The form is then passed to the client for approval of the change
It is very simple indeed.
Who does what on the form and who controls the whole process is dependent on the contractual arrangements of the project.
Very often the system is all electronic, either using databases or even as simple as spreadsheets. Most larger organisations have an in-house system for dealing with this. Often, it is built into bespoke management systems, but don’t let that worry you – the principle is the same whatever system is used – it is an approval process that allows the client to sign off the full implications of change.
In respect of the programme, the client is aware if the programme will be affected / delayed before he / she approves the change.
Gary France
The Planning Engineers Organisation