Chapter 5
Doing Surveillance
5-1. -- Surveillance Methods.
This chapter
tells how to do surveillance once the plan is written.
It tells how to build a monthly schedule, how to use the
surveillance plan, and what to do when there is poor contractor
performance. This chapter
applies to Quality Assurance Evaluators (QAEs) and contract
administrators.
5-2. -- Building a Schedule.
A surveillance
plan is organized to facilitate use by the QAE.
The QAE is responsible for developing a monthly schedule for
activities, based on the surveillance plan’s requirements.
Complete the Quality Assurance Evaluator Schedule by the last
workday of the preceding month and send a copy to the contract
administrator and the functional area chief for their information and
review. Each QAE builds a
schedule by filling in the blocks on the schedule.
Specific instructions for filling out the schedule are provided
below.
a.
Quality
Assurance Evaluator Schedule.
An example of a surveillance schedule is shown in
figure 5-1. The left-hand
side of the schedule divides the sheet into days of the week.
This example shows only a 7-day schedule.
The QAE must make up enough sheets to include each day of the moth.
Along the top of the schedule, insert the items to be checked
during the month. Along the
bottom of the schedule, indicate the number of observations to be made
during the month (that is, how often a MIS is checked, how many samples
will be taken, how often a surveillance checklist will be used).
b.
Filling
In And Updating the
Schedule.
To fill in the inspection schedule, the QAE refers
to the sampling guide for each service being monitored.
The sampling guide is used with the random number table to
determine the inspections (observations) to be made during the month (see
chapter 4, paragraph 4-4).
(1)
Contract surveillance must cover all hours of
operation. Random observations are scheduled at night, on weekends and
holidays when services are performed during these periods.
Areas that are monitored on a set schedule (for example, VIMS
standards and analysis reports) are included in the monthly schedule.
This monthly schedule shows where and what the QAE is monitoring
at all times.
(2)
Post any changes to the schedule weekly and send
copies to the contract administrator and to the functional area chief.
Document and explain the reasons for each change.
Actual surveillance activity recorded on the surveillance
checklist must be comparable to the monthly schedule.
(3)
As updated, one must be able to conduct a complete
audit trail from the monthly schedule, to observing the QAE perform
sampling, to completion of the surveillance checklist.
(a)
There must also be a correlation between
contractor performance versus standards, AQLs, checklists and action
taken by the contract administrator.
The sample in figure 5-1 shows the schedule for one week.
The QAE completes the blank forms, indicating week of (Monday
through Sunday), and enters the time, observation, and check (if
pertaining to a checklist), in the blocks corresponding to the item
and day.
(b)
After it is completed and filled in, this form
is “For Official Use Only” and must not be shown to
the contractor.
Figure 5-1.
-- QAE Surveillance Schedule
QAE Surveillance
Schedule Week of : 1 thru 7
Jan 78 |
Day |
VO
Sanpling Guide #1 |
VO
Sanpling Guide #2 |
VO
Sanpling Guide #3 |
VM
Sanpling Guide #1 |
VM
Sanpling Guide #2 |
RA
Sanpling Guide #2 |
Check
AF Forms 15 |
1
Jun |
|
:2215/9
:2345/54 |
B7125
B6704 |
7320
7340
7345 |
|
|
|
2
Jun |
|
:0715/63
:0815/2 |
B4392
B8763 |
7350
7370
7400 |
:0900 |
|
|
3
Jun |
Leave |
4
Jun |
:0915
:0956 |
:0900/4
:0915/59
:1002/64
:1023/83 |
B9763
B8794
B1001 |
|
|
|
|
5
Jun |
:1101 |
|
|
|
:1305 |
|
X |
6
Jun |
:0710
:1022
:1303 |
|
|
|
|
|
|
7
Jun |
|
|
|
|
|
|
|
Week
Total |
6 |
8 |
7 |
6 |
2 |
|
|
Month
Total |
20 |
32 |
32 |
32 |
5 |
50 |
|
5-3. -- Doing Surveillance.
Doing
surveillance involves using the surveillance plan called for in the
monthly schedule. Use the
following procedure to record observations and take action when the
contractor’s defects exceed the allowable number.
a.
Recording
Observations.
Monthly tally and surveillance checklists are used
for each sampling guide and less frequently checked services.
They are used to tally information on scheduled observations and
defects noted. Each
observation in the sample is recorded on the checklists, and the documents
then become a formal government record for later reference.
(1)
When random sampling guides are used, the tally of
observations and defects at the end of each month are compared to the
acceptable number of defects appearing in the sampling guide.
(2)
The contractor is told each time an error is found
during scheduled observations and asked to initial the observation
recorded on the checklist.
(3)
Errors found in services not scheduled for
observation should be brought to the contractor’s attention but not
used to count as a defect for determining if the AQL has been met.
(4)
Checks done with a surveillance activity checklist
are likewise recorded.
b.
Potential
Unsatisfactory Performance. If
the sampling guide or surveillance activity checklist indicates that the
number of defects is too high, the QAE goes to the decision table for that
service indicator.
(1)
The QAE must locate the specific service that is
unsatisfactory. The table will identify the possible causes of the
unsatisfactory performance and list a number of questions which, if
answered, will probably pinpoint the source of the problem.
(2)
The decision table helps the QAE identify the
problem so that, among other things, a meaningful evaluation can be made
of the contractor’s explanation and corrective action.
For example, if the contract specifies a maximum
out-of-commission rate for vehicles of 8 percent, and the rate was 10
percent, examination may reveal the excess was caused by excessive
vehicle down for parts (VDP). This
could have been caused by the government’s inability to provide timely
parts support.
(3)
In such a situation, the contractor may not
be at fault. If, on the
other hand, the excessive VDP was created because the contractor ordered
the parts on a routine priority rather than priority, it might be the
contractor’s fault. The
decision tables will assist the QAE in making such a determination.
c.
Documenting
Unsatisfactory Performance. If
performance in any area is judged unsatisfactory, the contractor is
required to respond to a Contract Discrepancy Report (CDR). See sample in Figure 5-2.
(1)
The QAE prepares the form and sends it to the
contracting officer, who signs and sends it to the contractor.
(2)
When completed and signed, the report, along with
the tally checklist or surveillance activity checklist become the
documentation supporting payment, nonpayment, or other necessary action.
5-4. -- Taking Action.
The QAE may check
the contractor’s performance and document any non-compliance, but only
the contracting officer may take formal action against the contractor for
unsatisfactory performance.
Figure 5-2.
-- Contract Discrepancy Report
a.
Ground
Rules. This section lists the normal steps to be
taken by contract administration when the QAE reports these deficiencies.
The actions listed are not hard-and-fast rules, and are a minimum.
More serious action can be taken sooner.
(1)
When the contractor’s performance is
unsatisfactory as defined in the surveillance plan and a formal action
is indicated, the QAE, the functional area chief, and the contract
administrator meet to determine what action is appropriate for the
specific circumstances.
(2)
If a decision is reached not to take a monetary
deduction, the reasons are documented.
The contracting officer must indicate agreement with the decision
by signing the contract discrepancy report or other decision
documentation.
b.
Actions.
Following are the actions normally taken when poor
performance is found.
(1)
As a rule, the QAE tells the contractor’s site
manager, in person, when discrepancies occur and asks the contractor to
correct the problem. The QAE makes a notation on the tally or surveillance
checklist, of the date and time the deficiency was discovered, and has a
contractor representative initial the entry on the checklist.
(2)
If the number of discrepancies found exceeds the
level for satisfactory performance, the QAE uses the decision tables in
the surveillance plan to determine the cause(s).
(a)
If the government created any of the
discrepancies, these are not to be counted against the contractor’s
performance.
(b)
When the government has caused the contractor to
perform in an unsatisfactory manner. the QAE prepares a letter to be
sent to the responsible organization requesting corrective action be
taken. The QAE sends it
to the organization through the contracting officer.
(3)
When the contractor is responsible for exceeding
the limits of satisfactory performance, the contracting officer issues a
contract discrepancy report (CDR) to the contractor (see paragraph
5-3c). If the failure is
serious enough, issue the CDR at the time of the unsatisfactory
performance, rather than at the end of the month.
(4)
When a CDR is issued for a specific service the
contracting office deducts from the month’s payment, an amount up to
the percentage indicated in the Performance Requirement Summary exhibit
of the contract. Do not
delay the deduction until the contractor responds to the CDR.
If surveillance was done right and the decision tables used, the
unsatisfactory performance is clearly the fault of the contractor.
For a specific example of a deduction, see paragraph 5-5.
(5)
If the contractor does not achieve satisfactory
performance in that specific service by the end of the next month, the
contracting officer issues another CDR and deducts the appropriate
amount from the contractor’s payment.
(6)
If a third CDR must be issued, consider issuing a
cure notice. (However, a cure notice can be issued sooner, if necessary).
(7)
Depending on the contractor’s overall
performance, the government may issue a Show Cause letter if the reply
to a cure notice is unsatisfactory; next consider terminating the
contract.
Figure 5-3.
-- Deducting for Non-Performance
Deduct
Formula (Example) |
If:
and:
and:
and:
and: |
Quality
of completed work is unsatisfactory (AQL of 6.5% exceeded)
Contract Price is $100,000 per month
Quality of completed work deduct percentage is 10%
Sample size is 50
Number of defects in the sample is 10 (Reject number is 8) |
Then: |
Deduction
from the current month’s invoice is: |
|
Contract
price
X Deduct Percentage
X Percent of sample defective
Deduction |
=
=
= |
$100,000
.10
$10,000
.20
$2,000 |
5-5. -- Deductions For Non-Performance.
Through the
Inspection of Services clause, the government can deduct from a
contractor’s payment an amount equal to the services not provided.
a.
To do this, the contract administrator must know the
major cost categories in the contract and the percentage of cost each
service output represents. The
percentage cost of each service is found in deduct analysis; see chapter
2, paragraph 2-9. An example of how the deduct formula works is shown in figure
5-3.
b.
Suppose the bid schedule showed the monthly contract
price for vehicle operations, maintenance, and analysis as shown.
The percentage cost of the service output is then found by looking
at the Performance Requirements Summary Technical Exhibit in the contract
statement of work. In the
example, the percentage cost of quality of completed work is 10 percent.
This is then multiplied by $100,000 to obtain the maximum amount of
deduct.
c.
If completed work was unsatisfactory during the
month (that is, did not meet performance values) and the percent of the
sample found bad was 20 percent, $2000 would be deducted from the payment
normally due the contractor.
d.
This amount for quality of completed work is
deducted because the contractor failed to provide reliable, uniform
services within the assigned performance values.
Although some completed work may have met the standard during the
month, the acceptable quality level was not met and at least 20 percent of
the observations were defective. Hence, the total quality performance requirement has not been
achieved. As a consequence,
the service output is unsatisfactory.
5-6. -- Good Performance.
When a
contractor’s quality control program works, good performance results.
If the result of a QAE’s surveillance shows consistently good
performance, the amount of surveillance can be decreased.
a.
Reduced
Inspection.
Inspection can be reduced when the following
conditions have been met for a sampling guide.
(1)
The preceding 4 lots (that is, the last 4 months)
have all been acceptable.
(2)
The number of defects in each of the preceding 4
lots is less than one half of the acceptance number.
For example, with an AQL of 6.5 percent and a sample size of 32,
the acceptance number is 5. If
two or less defects ere found in each of the last 4 lots, reduced
inspection could be used.
(3)
The normal sample size is being used.
(4)
The functional area chief and the contract
administrator agree to use reduced inspection.
b.
Reduced
Sample Size and Acceptance
or Rejection Numbers. Reduced inspection decreases the sample size
as shown in figure 5-4. In
addition, the acceptance and rejection numbers change as shown in figure
5-5. To make the changes to the existing sampling guide, take the
following steps.
(1)
Make sure that the original sampling guide was
using the normal sample size. To
determine this, see Chapter 4, figure 4-3 and compare the lot size with
the sample size in the sampling guide.
(2)
Find the new sample size by using figure 5-4.
Take the lot size and find the new reduced sample size.
(3)
Using the AQL in the sampling guide and the new
reduced sample size, see figure 5-5 for the new acceptance and rejection
numbers. Note that there is
a gap between the acceptance and rejection numbers (for example, sample
size 32 and AQL 6.5 percent, accept is 5 and reject is 8).
This means that the lot would not be rejected unless 8 defects
were found and would be accepted if 5 or less defects were found.
However, a number of defects greater than five will be cause for
returning to normal inspection (that is, return to the sample size and
acceptance and rejection numbers used in the original sampling guide).
c.
Returning
to Normal Inspection.
When reduced inspection is in effect return to
normal inspection the next month under the following conditions.
(1)
When the number of defects exceeds the acceptance
number under reduced sampling or,
(2)
The functional area chief and the contract
administrator deem it necessary to return to normal inspection.
d.
Returning
to Reduced Inspection. If
during the first month of the return to normal inspection, the number of
defects found is again less than 50 percent of the reject level, a return
to reduced inspection may be done the next month.
If the number of defects found is over 50 percent, then normal
sampling must be accomplished until 4 months of less than 50 percent of
reject level defects are found.
Figure 5-4.
-- Reduced Sample Size
Lot
Size |
Normal
Sample Size |
Reduced
Sample Size |
2-8 |
2 |
2 |
9-15 |
3 |
2 |
16-25 |
5 |
2 |
26-50 |
8 |
3 |
51-90 |
13 |
5 |
91-150 |
20 |
8 |
151-280 |
32 |
13 |
281-500 |
50 |
20 |
501-1,200 |
80 |
32 |
1,201-3,200 |
125 |
50 |
3,201-10,000 |
200 |
80 |
10,001-35,000 |
315 |
125 |
35,001-150,000 |
500 |
200 |
150,001-500,000 |
800 |
315 |
500,001
and over |
1250 |
500 |
Figure
5-5. -- MIL-STD-105D Acceptance Rejection Levels for Reduced Inspection
Note:
See Hardcopy for MIL-STD-105D Acceptance Rejection Levels for
Reduced Inspection
5-7. -- Documentation.
During the course
of the contract the QAE retains a copy of all inspection schedules, tally
checklists, and surveillance activity checklists.
At the end of the contract period, the QAE forwards these records
for inclusion in the contract file. However,
when a specific service becomes unsatisfactory during a surveillance
period, the inspection documentation supporting the contract discrepancy
report is forwarded to the contracting officer no later than 5 days after
the end of the previous performance period.
|
Contents
Acknowledgement
Chapter
1
Chapter
2
Chapter
3
Chapter
4
Chapter
5
Chapter
6
|