Gordon Lawrence discusses the importance of prescriptive scope criteria in a turnaround premise document
IT IS generally accepted in the maintenance turnaround community that the larger and more complex a turnaround becomes, the more difficult it is to control costs and schedule. An obvious, but generally overlooked route to ensure a turnaround is no larger than it needs to be, is to ensure that only the necessary scope is included in the turnaround event.
The best way to ensure that this happens, is to include very clear, prescriptive scope criteria in the turnaround premise document that is issued at the start of preparation and planning. Unfortunately, too many teams write premise documents that focus only on the tactical targets of turnaround event cost and schedule and ignore the strategic issue of defining what the purpose and objective of the turnaround event is. This article explains what information is important to include in a premise document and lays out an example temp