Change request

Not all instructions need to be documented - it depends upon the nature of the message being conveyed. Many types of forms have been conceived to convey instructions. Purchase Orders, Change Requests, Amendment Instructions, Engineering Orders, and Print Requisitions are all instructions that cause people to do work and hence are work instructions rather than procedures. 

A Change Request Form, which contains the reason for change and the results of the evaluation. This was described previously as it is used to initiate the change and obtain approval before being implemented. 

To provide these authorities with pertinent background information you will need to submit the change request to them. In fact this is another good reason to formalize the change request process. Your change requests need to specify ... 

The originator of the change request (who is proposing the change, his/her location or department)... 

Create a formal change request mechanism for initiating changes to controlled documents. 

Provide a means for collecting design change and document change requests. 

Customer complaints Warranty claims Failure analysis reports Process capability studies Service reports Concessions Change requests Subcontractor assessments Performance analysis Deviations and waivers Contract change records Quality cost data External Quality Audit records... 

Packages contain everything including business models, change requests, component specifications, source code, bug reports and their test data, changes and bug fixes to code,... 

All interfaces that are believed to be affected by change request RedoItAll81 ... 

Records the work request code number, the change request date, the system experiencing the change, and a description of the change. It also records testing status, start and close dates, and the programmer s initials. 

A record of change requests and actions is available and archived... 

The departmental manager will initiate a process change request form prior to any change in the approved and authorized procedure. The form will be forwarded to the quality assurance manager to review and approve. 

Change requests can result from both planned and unplanned events. Planned events can be scheduled, and can be the result of a planned expansion in business requirements. Emergency or unplanned events can result from software or hardware problems that prevent the application from performing its defined tasks. 

During the operational life of the computer system, a change request to enhance or amend the computer system will result in this period being initiated again and the original concept being reviewed and updated if necessary. 

Example of Critical Change Control Guideposts CHANGE REQUEST NO (a) DATE (b) ... 

Documentation. The completed change request forms and all activities surrounding the implementation of each change should be properly documented. These files should be maintained in a state ready to be reviewed by an investigator at any time. These files can also provide good historical data for your ongoing plant operations. 

---