Project vs. Customer Deliverables

The new API Spec Q2 standard requires Service Supply Organizations to develop a Service Quality Plan to control the execution of the service or the use of a service related product (SRP).  As part of the plan documentation, we are required to identify project deliverables, as well as customer deliverables.  Distinguishing the two terms can create some confusion, so we would like to define and differentiate between the two in today’s post.

Let’s start with project deliverables. This is the list of all activities that are required to develop the project but aren’t necessarily the deliverables required by the contract. This includes activities like sketches, models, training, calculations, and so on that allow you to produce the customer deliverable. It is important to have a detailed list of project deliverables to calculate the time, cost, and/or resources required to provide the service.

On the other hand, customer deliverables are activities that must be satisfied and are used to make payment, or monitor project progress.   A simple example, not related to the oil and gas industry, would be the production of an automobile.  The customer wants your organization to build a car and gives you all of the required specifications including color,  accessories and horsepower specifications.  In order to fulfill the customer requirements, you must complete the production of the car to the specifications.

However, there are a variety of project deliverables you must complete in order to make the car. This includes planning, materials, labor, machinery and sub-components required to develop and manufacture the car. To summarize, customer deliverables are what you get paid for, and project deliverables define how you produce what you get paid for.

For more information on how Accupoint’s cloud-based quality management systems can help your organizations handle the documentation of deliverables, visit www.accupointsoftware.com or call us toll free at 800.563.6250!