KARPEDIUM
reTHINKING CONSTRUCTION
Targeted Clientele >> Owner >> Procurement Policies & Procedures

Procurement Policies & Procedures

Policies and standards ensure that processes, procedures and deliverables are consistent and meet the needs of the business, while complying with current POLICIES. Policies should be clearly communicated through all levels of an organization detailing who responsible for each policy and what onus that places on individuals employed by the organization.

KarpeDium assists a client in creating a comprehensive Program and Procedures manual that serves as the bible for all stakeholders delineating and defining each and every phase, process, procedure and the roles and responsibilities associated with all constituents of the plan. It is also used as a baseline for reference to monitor progress in terms of Contract Deliverables and any ambiguity that arises thereof. This along with the Project/Program Plan provides the business case with planned project costs and it identifies the management stages and other major control points.

Project Execution Plan is equivalent to the project initiation document plus the updated Project Plan.

Our focus is to answer the following:
Is the plan achievable?
Does it support the rest of the Project Initiation Document?

Our Project Execution Plan consists of:

Plan description, giving a brief description of what the plan covers
Project prerequisites, containing any fundamental aspects that must be in place at the start of
   the project and any that must remain in place for the project to succeed
External dependencies, identifying the products that must be provided to the project so that it can    continue but which the Project Management Team has no authority over and so cannot ensure    delivery fits the project requirements.
Planning assumptions concerning availability of resources, skills/competency requirements etc.
Project plan, covering.

Project level Gantt chart or bar chart with identified management stages, e.g. milestones and
   control points
Project level product breakdown structure
Product descriptions, defining what the project will deliver including the required quality level
Project level activity network and product dependencies
Project level table of resource requirement
Requested/assigned specific resources
Project change budget (if appropriate)
Project level tolerance, for both time and budget as triggers for contingency plans and escalation   processes
Contingency plans, explaining how it is intended to deal with the consequences of any risks that    materialize



Targeted Clientele
Contact Us
Tel : +1-312-850-3077
contact@karpedium.com

Site Development
| HOME | ABOUT US | MEMBER LOGIN | CAREERS |  SITE MAP |