Change management (engineering)

[2] Typical investment by organizations during initial implementation of large ERP systems is 15 to 20 percent of overall budget.

In the same vein, Hinley [3] describes two of Lehman's laws of software evolution: Change request management is also of great importance in the field of manufacturing, which is confronted with many changes due to increasing and worldwide competition, technological advances and demanding customers.

A few concepts are defined by the author (i.e. lack a reference), because either no (good) definitions could be found, or they are the obvious result of an activity.

Furthermore, some concepts (e.g. CHANGE REQUEST, SYSTEM RELEASE) lend themselves for the versioning approach as proposed by Weerd,[6] but this has also been left out due to diagram complexity constraints.

These two approaches can be viewed as minimalistic change request management (i.e. no real solution to the problem at hand).

Often users report bugs or desire new functionality from their software programs, which leads to a change request.

Following an analysis of the impact on the car design and production schedules, the planning for the implementation of the change can be created.

An eminent example of this is the Flixborough explosion, where improvised changes involving the bypassing of a stage in a reactor train was at the origin of the accident.

The main requirement is that a thorough review of a proposed change be performed by a multi-disciplinary team to ensure that as many possible viewpoints are used to minimize the chances of missing a hazard.