Lotus7312
HEC is quite right, a Master Validation Plan is no small task. The Validation Plan is a roadmap that defines what you are going to to do (and by implication, not do) to validate the Plant. The scope and approach of the MVP depends on whether you are validating a Plant (in which case you will largely be writing a Qualification Plan) or whether you are Validating an entire process (in which case modules such as analytical validation, Information Systems Validation and other hangers on are included).
Whether you include HVAC's, Utilities, Buildings etc. depends entirely on the impact that theses items have on the Product or API quality. If the HVAC's are for Human Comfort, then it can be excluded. How you define whether there is an impact, which systems are to be validated and how they will be validated is basically what goes into the Validation Plan.
In my experience, if you remember what Validation is (documentary evidence that a System or Process consistently meets or performs at a predetermined specification), you are halfway home.
If you are looking for a template you will find many on the Internet. Ultimately, though, your best bet will be to draft one for yourself.
Regards,
Kevin Seymour