GPCCaR Purpose

1.1 Introduction & Purpose

 

 

 

 

 

 

 

 

 

 

guild_sphere_logo_with_motto_mch12_web_version.jpg

The GPCCaR to all intents and purposes defines the subject matter that the Global Project Community believe to be necessary in order to be a fully-rounded practitioner.  

It also forms the knowledge-domains in regard to Certification by The Guild. 

Project Controls practitioners operate in both OWNER and CONTRACTOR organisations so in addition to describing the processes needed for executing and delivering “projects” (i.e. carried out by CONTRACTOR practitioners) this guide extends further to address the operations which identify and define such “projects” (i.e. carried out by OWNER practitioners) before they are assigned to contractors to implement. This is explained as the “Full Life Span” of the project or initiative.

It should also be noted that Project Controls processes and procedures are also utilised to “implement” initiatives or projects other than physical structures such as a buildings or oil processing facilities and it should be remembered that such projects could be software systems and even projects defined in order to implement less tangible things such as organisational changes or “upgrades”.  So again, this guide is intended for use on all project types and in all industry sectors.

This document has been designed to be a compilation of “best tested" and "proven practices” along with references and sample templates purposed for Project Control Practitioners operating in a global and pan-industry environment.

This guide has been collated, organised and proposed by an unparalleled array of experienced practitioners and comprises many pages of references.  It serves as the Project Controls Compendium and Reference (CaR) with links to what Subject Matter Experts (SME) believe to be “best tested and proven” tools, techniques and methodologies. 

This Guild of Project Controls Compendium and Reference (GPCCaR) has been created to serve the following purposes:

  1. To be used as a handy “Project Controls Reference”- a compendium of tools, techniques, methodologies, references and templates developed by both owners and contractors, and;
  2. As the basis to prepare for one or more of the Guild of Project Controls certification exams, and;
  3. It provides standards to which practitioners are expected to adhere in order to be recognized by the Guild of Project Controls, and;
  4. It also defines appropriate performance benchmarks and standards against which they would be measured and provides a tool for continued education and learning, and;
  5. To be used in relation to Project Controls operations within any industry sector or global location

As time progresses will be updated to include additional external references and additional reading sources for the more advanced practitioner.

1.2 How To Use This Document

 

The processes of Project controls are not unique; they comprise fundamental tools, techniques and methodologies from different areas of general management - being applied to solve problems and / or to exploit opportunities.

It is expected that this would be the "first stop" a Project Control practitioner would make should he / she have a question about the practice of Project Controls and is equaly relevant for those operating in Owner and Contractor organisations.  

1.3 Living Document

 

The GPCCaR is a “living document”, which has been initially created by drawing from published papers and other references available under “open source”, "share alike" and / or “creative commons” principles.

If you have any suggested amendments to this document or wish to offer additional external references, papers, templates, case studies or exam questions please contact [email protected]

1.4 Who Is This Guide For?

 

Project Controls practitioners operate in both OWNER and CONTRACTOR organisations so in addition to describing the processes needed for executing and delivering “projects” (i.e. carried out by CONTRACTOR practitioners) this guide extends further to address the operations which identify and define such “projects” (i.e. carried out by OWNER practitioners) before they are assigned to contractors to implement. This is explained as the “Full Life Span” of the project or initiative.

It should also be noted that Project Controls processes and procedures are also utilised to “implement” initiatives or projects other than physical structures such as a buildings or oil processing facilities and it should be remembered that such projects could be software systems and even projects defined in order to implement less tangible things such as organisational changes or “upgrades”.  So again, this guide is intended for use on all project types and in all industry sectors.

 

GPCCAR Purpose, Revision 1.1