B08 ATTACH 8 QASP.pdf
PDF 344 KB Posted
- Attached to
- Request for Proposals- Aberdeen Test Center Data Collection Support Services Federal contract opportunity
- Solicitation number
- W91CRB-21-R-0005
About this file
This is a request for proposals issued by the Army Contracting Command-Aberdeen Proving Ground for data collection support services at the U.S. Army Aberdeen Test Center. The solicitation seeks proposals for a single-award indefinite delivery, indefinite quantity contract with a five year ordering period. Required services include data collection, computer operations, technical writing, and range scheduling support across various directorates and test mission areas at Aberdeen Test Center. The contract type will be cost plus fixed fee and firm fixed price task orders. The set-aside is for small businesses under NAICS code 518210 with a size standard of $35 million. Questions are due by June 22, 2021 and responses will be posted on SAM.gov where the solicitation is also located. Proposals must be submitted through the DoD Secure Access File Exchange by the closing date specified in the solicitation.
View the file
Other files for this federal contract opportunity
Show all 30
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DEPARTMENT OF THE ARMY
US ARMY ABERDEEN TEST CENTER
400 COLLERAN ROAD
ABERDEEN PROVING GROUND, MARYLAND 21005-5059
Quality Assurance Surveillance Plan
For Data Collection, Technical Writing and Support Services
1. INTRODUCTION
This Quality Assurance Surveillance Plan (QASP) is designed to provide an effective method of monitoring Contractor performance for each listed objective on the Performance Requirements Summary (PRS) in the contract. The Government is concerned primarily with the quality of the services provided, and not with the method that the Contractor uses to provide these services. If performance of any required service is unsatisfactory as a result of the Contractor's actions or omissions, then the Government may reduce the contract payments to reflect the decreased value of the services received in accordance with the PWS and/or applicable Federal Acquisition Regulation (FAR) clauses.
2. PURPOSE
This QASP was developed to comply with the FAR, Subpart 37.6- Performance Based Acquisition and 46-4, Government Contract Quality Assurance. In addition, FAR Subpart 46.103, Contracting Officer Responsibilities, states that agencies shall develop QASPs when acquiring services. The QASP describes methods that the Government will use to monitor whether the contractor’s performance of the contract is acceptable and is the Government’s written plan for administering the Contract and monitoring major aspects of the contractor's performance. The QASP is not part of the Contract. It is provided to the contractor solely for informational purposes and is subject to change by the Government at any time during the contract performance period. Therefore, the Government reserves the right to perform more or less surveillance than is provided in this QASP.
3. AUTHORITY
Authority for issuance of this QASP is provided under Contract Section E – Inspection and Acceptance, which provides for inspections and acceptance of the articles, services, and documentation called for in task orders to be accomplished by the Contracting Officer or his duly authorized representative.
4. RESPONSIBILITIES
The Government resources shall have responsibilities for the implementation of this QASP as follows:
a. Contracting Officer (KO) – The KO ensures performance of all necessary actions for effective contracting, ensures compliance with the terms of the contract and safeguards the interests of the United States in the contractual relationship. It is the Contracting Officer that assures the contractor receives impartial, fair, and equitable treatment under the contract. The Contracting Officer is ultimately responsible for the final determination of the adequacy of the contractor’s performance.
b. Contracting Officer Representative (COR) - The COR is responsible for overall administration of the project and assures proper Government surveillance of the contractor’s performance. The COR is not empowered to make any contractual commitments or to authorize any contractual changes on the Government’s behalf. Any changes that the contractor deems may affect contract, price, terms, or conditions shall be referred to the Contracting Officer for action.
c. Technical Monitor (TM) – The TM provides detailed technical oversight of the contractor’s performance and reports his or her findings to the COR in a timely, complete and impartial fashion to support the COR’s administration activities. While the TM may serve as a direct conduit to provide Government guidance and feedback to the contractor on technical matters, he or she is not empowered to make any contractual commitments or to authorize any contractual changes on the Government’s behalf. Any changes that the contractor deems may affect contract, price, terms, or conditions shall be referred to the KO for action.
d. ATC Contracts Team – The Contracts Team provides centralized contracts management support to all ATC activities to include, but not limited to, the following:
technical advice in the preparation of Acquisition Request Packages, QASP preparation and implementation, training, development of internal policies and procedures, and serves as the liaison office between contracting activities and ATC.
5. METHODS OF QA SURVEILLANCE
The below listed methods of surveillance shall be used in the administration of this QASP. In addition to specific instructions that may be mentioned, the appropriate and standardized form that is to be used for documentation of QA surveillance is the Surveillance Activity Checklist, included as Attachment A. The methods of evaluating contractor compliance may vary depending on the standards being evaluated. The TM is responsible for selection of the method(s) to be used and the specific detailing of the method(s). In determining the evaluation method, the TM should consider how performance can be observed and if the proposed method of surveillance is adequate to assure the required level of performance has been achieved. The following describes common methods of observation:
a. Validated Customer Complaint – Customer feedback may be obtained either from the results of formal customer satisfaction surveys or from random customer complaints. Customer complaints, to be considered valid, must set forth clearly and in writing the detailed nature of the complaint, must be signed by the customer and TM and forwarded to the COR. The COR shall maintain a summary log of all formally received customer complaints as well as a copy of each complaint in a documentation file. The COR shall also keep the tabulated results of all customer satisfaction surveys on file and shall enter the summary results into the Surveillance Activity Checklist.
Although usually not a primary method, this is a valuable supplement to more systematic methods. For example, in a case where random sampling indicates unsatisfactory service, customer complaints can be used as substantiating evidence. In certain situations, customers can be relied upon to complain consistently when the quality of performance is poor.
b. 100% Inspection - This level of inspection shall be accomplished by monitoring and documentation. Each month the TM and/or COR shall inspect designated performance tasks, review the generated documentation and enter summary results into the Surveillance Activity Checklist. This is the appropriate method of evaluating tasks that occur infrequently or tasks with stringent performance requirements, e.g., where safety or health is a concern. With this method, performance is inspected/evaluated at each occurrence. One hundred percent inspection is too expensive to be used in most cases.
c. Periodic Inspection – The TM and/or COR shall conduct periodic inspections on a daily, weekly, or monthly basis. This method, sometimes called “planned sampling,” consists of observing tasks on a scheduled basis. It is appropriate for tasks that occur infrequently or periodically, but where 100 % evaluation is neither required nor practicable. A predetermined plan for inspecting part of the work is established using subjective judgment and analysis of agency resources to decide what work to inspect and how frequently to inspect it.
d. Random Monitoring - Random monitoring shall be conducted as needed when periodic and 100% inspections are not practical or are not required or when the occurrence of a task is infrequent or unpredictable to monitor routinely. For the potential tasks that have been identified and included in this QASP, the random monitoring shall be performed by the TM and/or the COR.
6. PERFORMANCE STANDARDS.
The performance standards for each requirement area which the contractor will be evaluated are provided in the Performance Requirements Summary (PRS), which is presented in Table 1 below. Although the PRS includes surveillance methods planned for use for each performance threshold, the TPOC and/or COR may change the actual surveillance methods as needed in order to provide the level or surveillance required to assure the quality of support received.
TABLE 1. PERFORMANCE REQUIREMENTS SUMMARY
PERFORMANCE
REQUIREMENT
STANDARD
PERFORMANCE THRESHOLD
PLANNED
SURVEILLANCE
METHODS
5.2 DATA COLLECTION SUPPORT
6.2.2 Monitor, collect, and record data
The contractor shall collect and perform an initial review of all test data and verify the accuracy and completeness of the data prior to delivering to the Government.
The contractor shall meet 100% of the requested test execution and 100% completion of information as requested.
Documentation of 100% of all test incidents. Random monitoring, validated customer complaint Documentation of 100% accuracy and completeness of data related to safety.
100% inspection, validated customer compliant For non-safety related TIR data, no more than 1 technical error per 4 TIRs received per project per day.
Periodic inspection, validated customer complaint For non-safety related mission data, no more than 1 technical error for every 15 documents submitted per day.
Periodic inspection, validated customer complaint For non-safety related data collected on custom data forms created in ODIN, no more than the allotted errors per document specified by the government.
Periodic inspection, validated customer complaint For non-safety related spreadsheet data, no more than 1 technical error per 1,200 data fields per project per day.
Periodic inspection, validated customer complaint For non-safety related event summary sheets, no more than 1 technical error per 50 documents received per day.
Periodic inspection, validated customer complaint Except for spreadsheet data, all data and documents shall have no more than 1 non-technical error, inclusive of spelling, punctuation, grammar, word usage, format, and style, for every 3 pages of a document, 8.5 x 11” in size, single spaced with 12 point font.
Periodic inspection, validated customer complaint
Spreadsheet data shall have no more than 1 non-technical error, inclusive of spelling, punctuation, grammar, word usage, format, and style, per 1,200 data fields per project per day.
Periodic inspection, validated customer complaint
No errors are allowed that result in a security violation. 100% inspection, validated customer compliant Any instances where inaccuracies or incompleteness of any deliverables are identified shall be corrected, or at a minimum a plan of action coordinated with the government, within 6 hours of notification.
Random monitoring, validated customer complaint
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
Validated customer complaint
TABLE 1 (Cont)
SURVEILLANCE
METHODS
6.2.2 Submit all
data
The contractor shall meet 100% of the conditions in this requirement with 100% submission of information in the required timeframe
For TIR and mission data, no more than 2 instances of late submissions per week, with 0 incidents of late submissions for critical/safety related incidents.
Periodic inspection, validated customer complaint
For custom data forms created in ODIN, no more than 2 ins t an ce s of late submissions per week, with 0 incidents of late submissions for critical/safety related incidents.
Periodic inspection, validated customer complaint
For spreadsheet data, no more than 1 late submission per quarter.
Periodic inspection, validated customer complaint
For event summary sheets, no more than 1 late submission per 20 documents received per day.
Periodic inspection, validated customer complaint
For ADMAS harvests, no more than 1 failed or late data harvest for every 20 harvests per day, with any late or failed data harvests completed
Periodic inspection, validated customer complaint
All collected data shall be copied or uploaded to a network drive at the end of each shift with no more than 2 incidents of failed uploads identified per quarter.
Random monitoring, validated customer complaint
No errors are allowed in the data submission process that result in a security violation.
100% inspection, validated customer compliant
Any instances where inaccuracies, incompleteness, or lateness of any deliverables are identified shall be corrected within 6 hours of notification, unless
Random monitoring, validated customer complaint
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
Validated customer complaint
6.2.3 Instrumentation, image, video, and/or other related data efforts
The contractor shall perform an initial review of all test data and verify the accuracy and completeness of the data prior to delivering to the Government. This requirement entails 100% contractor support of the conditions set in this requirement with 100% completion of information requested within the schedule specified by the government.
No more than 1 technical error per fiscal quarter and no more than 1 late submission per fiscal quarter, as evidenced by a complaint substantiated by the COR which shows non-compliance with contract requirements.
Random monitoring, validated customer complaint
All documents generated to support this requirement shall have no more than 1 non-technical error, inclusive of spelling, punctuation, grammar, word usage, format, and style, for every 4 forms.
Random monitoring, validated customer complaint
No errors are allowed that result in a security violation. 100% inspection, validated customer compliant
SURVEILLANCE
METHODS
Any instances where inaccuracies, incompleteness, or lateness of any deliverables are identified shall be corrected, or at a minimum a plan of action coordinated with the government, within 6 hours of notification.
Random monitoring, validated customer complaint
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe
Validated customer complaint
6.2.5 Data quality
support
The contractor shall perform an initial review of all test data and verify the accuracy and completeness of the data prior to delivering to the Government. This requirement entails 100% contractor support of the conditions set in this requirement with 100% completion of information requested within the schedule specified by the government.
No more than 1 technical error per 9 man-hours of support per day, inclusive of all data sources that are being quality checked and no more than 1 non-technical error, inclusive of spelling, punctuation, grammar, word usage, format, and style, for every 4
Periodic inspection, validated customer complaint
No errors are allowed that result in a security violation. 100% inspection, validated customer compliant
Data quality reviews that provide 100% accuracy and completeness of data related to test safety issues.
100% inspection, validated customer compliant
All documents and data shall be reviewed within the specified schedule provided by the government, with no more than 1 complaint per fiscal quarter per full-time
Periodic inspection, validated customer complaint
Any instances where inaccuracies, incompleteness, or lateness of any deliverables are identified shall be corrected, or at a minimum a plan of action
Random monitoring, validated customer complaint
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
Validated customer complaint
6.2.1 Data
processing
The contractor shall meet 100% of the conditions set in this requirement with 100% completeness of information required within the schedule specified by the government.
No more than 1 complaint per fiscal year as to the accuracy or timeliness of any custom forms and databases generated or to the accuracy or timeliness of processing of data, with all complaints substantiated by the COR which shows non-compliance with contract requirements.
Random monitoring, validated customer complaint
No errors are allowed that result in a security violation. 100% inspection, validated customer compliant
Any instances where inaccuracies, incompleteness, or lateness of any deliverables are identified shall be corrected within 1 to 10 working days of notification depending upon the complexity of the document, unless otherwise specified by the government.
Random monitoring, validated customer
SURVEILLANCE
METHODS
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
Validated customer complaint
6.2.2, 6.2.3 & 6.2.4 Data uploading
The contractor shall meet 100% of the conditions set in this requirement with 100% completeness of information uploaded within the schedule specified by the government.
No more than 1 complaint per fiscal year as to the timeliness or accuracy of data or documents uploaded to electronic databases, as substantiated by the COR which shows non-compliance with contract requirements.
Random monitoring, Validated customer complaint
No errors are allowed that result in a security violation.
100% inspection, validated customer compliant
Any instances where inaccuracies, incompleteness, or lateness of any deliverables are identified shall be corrected within 5 working days of notification, unless otherwise specified by the government.
Random monitoring, validated customer complaint
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
Validated customer complaint
5.4 TECHNICAL WRITING, DATA AND WORD PROCESSING SUPPORT
6.4.1 Technical
writing
The contractor shall perform an initial review of all technical documents and verify the accuracy and completeness of the data prior to delivering to the Government.
The contractor shall meet 100% of the conditions set in this requirement with 100% completeness of information required within the schedule specified by the government.
No more than 1 error, inclusive of spelling, punctuation, grammar, word usage, format, style, and accuracy (e.g., incorrect arithmetic or orientation), per three pages of the body of a report or document, whereby a page is defined as 8.5 x 11” in size, single spaced with 12 point font.
Periodic inspection, validated customer complaint
No more than 1 error, inclusive of spelling, punctuation, grammar, word usage, format, style, and accuracy (e.g., incorrect arithmetic or orientation), per six pages of the appendix of a report or document, whereby a page is defined as 8.5 x 11” in size, single spaced with 12 point font.
Periodic inspection, validated customer complaint
No errors are allowed that result in a security violation. 100% inspection, validated customer compliant
No more than 1 complaint per fiscal year as to the timeliness of reports or documents generated, with all complaints substantiated by the COR which shows non-compliance with contract requirements.
SURVEILLANCE
METHODS
Any instances where inaccuracies, incompleteness, or lateness of any deliverables are identified shall be corrected within 1 to 10 working days of notification depending upon the complexity of the document, unless otherwise specified by the government.
Random monitoring, validated customer complaint
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
Validated customer complaint
6.4.3 Publishing
and distributing documents
The contractor shall meet 100% of the conditions identified in this requirement with 100% completeness of information required within the schedule specified by the government. All documents shall be delivered, uploaded, or published to the correct agencies and databases in the agreed upon timeframe and in accordance with security procedures as identified by the government POC.
No more than 1 complaint per fiscal year as to the accuracy, completeness, or timeliness of documents generated, published, or distributed, with all complaints substantiated by the COR which shows non-compliance with contract requirements.
Random monitoring, Validated customer complaint
No errors are allowed that result in a security violation. 100% inspection, validated customer compliant
Any instances where inaccuracies, incompleteness, or lateness of any deliverables are identified shall be corrected within 1 to 5 working days of notification, unless otherwise specified by the government.
Random monitoring, validated customer complaint
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
Validated customer complaint
6.4.4 Data
uploading
The contractor shall meet 100% of the conditions set in this requirement with 100% completeness of information uploaded within the schedule specified by the government.
No more than 1 complaint per fiscal year as to the timeliness or accuracy of data or documents uploaded to electronic databases, as substantiated by the COR which shows non-compliance with contract requirements.
Random monitoring, Validated customer complaint
No errors are allowed that result in a security violation. 100% inspection, validated customer compliant
Any instances where inaccuracies, incompleteness, or lateness of any deliverables are identified shall be corrected within 5 working days of notification, unless otherwise specified by the government.
Random monitoring, validated customer complaint
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
SURVEILLANCE
METHODS
6.4.2 & 6.4.5 Technical writing reviews and expertise
The contractor shall meet 100% of the conditions identified in this requirement with 100% completeness of information required within the schedule specified by the government.
No more than 1 complaint per fiscal year, as to the accuracy or timeliness of reviews or technical writing-related expertise provided, as substantiated by the COR which shows non-compliance with contract requirements.
Random monitoring, Validated customer complaint
Any instances where inaccuracies, incompleteness, or lateness of any deliverables are identified shall be corrected within 1 to 10 working days of notification depending upon the complexity of the document, unless otherwise specified by the government.
Random monitoring, validated customer complaint
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
Validated customer complaint
C.3.3 RANGE SCHEDULING SUPPORT
6.5.1 Range
scheduling requirements coordination
The contractor shall coordinate 100% of the assigned scheduling requirements with 100% completeness of schedule.
No more than 4 incidents per man-year of contract support where scheduling requirements are not accurately input into the Range Control Database Scheduling System within 4 business hours of receipt of the scheduling requirement, each corrected to 100% accuracy within 1 hour of identification of the error.
Random monitoring, validated customer complaint
No more than 3 incidents per man-year of contract support are allowed where the support provided resulted in a direct delay or issue with test execution due to inaccurate scheduling guidance provided.
Random monitoring, validated customer complaint
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
Validated customer complaint
6.5.2 Resolution of
range scheduling issues
The contractor shall meet 100% of the conditions identified in this requirement with 100% completeness of information required within the schedule specified by the government.
100% resolution of scheduling problems or conflicts with no more than 3 complaints from the government POC, COR, customers, coworkers, or test officers per man-year of contract support as to the level of support provided, inclusive of complaints as to the degree of tact and diplomacy used to complete this requirement.
Random monitoring, validated customer complaint
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
SURVEILLANCE
METHODS
6.5.3 Range The contractor shall Contractor attendance at 100% of all scheduled Random monitoring, scheduling meeting meet 100% of the meetings as required, with no incidents of unexcused validated customer attendance conditions identified in absences. complaint this requirement with No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
Validated customer complaint 100% completeness of information required within the schedule specified by the government.
7. FEEDBACK TO CONTRACTOR. The COR shall conduct Quarterly and as required meetings with the contractor to provide feedback on its performance and/or about any other contractual matter. The COR should summarize and document QASP results and provide to the contractor during the meeting. The COR shall document everything in writing and report unacceptable performance to the ATC Contracts Branch Chief. Prompt feedback is essential so the contractor can develop and implement a corrective action plan. Issues and concerns that cannot be resolved at the working level or which impact on contractual requirements shall be reported to the Contracting Officer for resolution and contractual action.
8. SURVEILLANCE FOLDER. The COR assigned to perform surveillance, with the assistance of the TPOCs, shall prepare a Surveillance Folder (this folder may consist of digital copies to reduce paper consumption) for their assigned contract requirements. The folder shall have, at a minimum, the following divisions:
a. COR appointment letters, contracting officer letter of designation, and Training
Record.
b. PWS, and other pertinent parts of the contract.
c. Surveillance Plan.
d. Surveillance Reports.
e. Other applicable documentation, such as:
i. Customer and user comments
ii. Data and technical reports
9. CONTRACT INFORMATION
a. Contract Number:
b. Contractor Name:
c. Contractor Address:
d. Contract Period:
e. Contracting Agency: RDECOM Contracting Center
f. Contracting Officer/Contract Specialist:
Phone: Email:
g. COR / Phone:
10. ATTACHMENTS
SURVEILLANCE ACTIVITY CHECKLIST
A-1
REQUIREMENT AND
SURVEILLANCE
ACTUAL
METHOD(S)
DATE
DESCRIPTION/COMMENTS
COMPLIANT?
(YES/NO)
C.3.1 DATA COLLECTION SUPPORT
6.2.2 Monitor, Documentation of 100% of all test incidents.
collect, and record data: The contractor shall collect and perform an initial review of all test data and verify the accuracy and completeness of the data prior to delivering to the Government.
The contractor shall meet 100% of the requested test execution and 100% completion of information as requested.
Documentation of 100% accuracy and completeness of data related to safety.
For non-safety related TIR data, no more than 1 technical error per 4 TIRs received per project per day.
For non-safety related mission data, no more than 1 technical error for every 15 documents submitted per day.
For non-safety related data collected on custom data forms created in ODIN, no more than the allotted errors per document specified by the government.
For non-safety related spreadsheet data, no more than 1 technical error per 1,200 data fields per project per day.
For non-safety related event summary sheets, no more than 1 technical error per 50 documents received per day.
Except for spreadsheet data, all data and documents shall have no more than 1 non-technical error, inclusive of spelling, punctuation, grammar, word usage, format, and style, for every 3 pages of a document,
8.5 x 11” in size, single spaced with 12 point font.
Spreadsheet data shall have no more than 1 non-technical error, inclusive of spelling, punctuation, grammar, word usage, format, and style, per 1,200 data fields per project per day.
A-2
(YES/NO)
No errors are allowed that result in a security violation.
Any instances where inaccuracies or incompleteness of any deliverables are identified shall be corrected within 6 hours of notification, unless otherwise specified by the
No substantiated complaints as to the overall performance of the contractor, whereby a substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement or that the contractor made severe errors in the quality of the work performed.
6.2.2 Submit all
data: The contractor shall meet 100% of the conditions in this requirement with 100% submission of information in the required timeframe.
For TIR and mission data, no more than 2 instances of late submissions per week, with 0 incidents of late submissions for critical/safety related incidents.
For custom data forms created in ODIN, no more than the allotted number of late submissions specified by the government with no more than 1 complaint per quarter.
For spreadsheet data, no more than 1 late submission per quarter.
For event summary sheets, no more than 1 late submission per 20 documents received per day.
For ADMAS harvests, no more than 1 failed or late data harvest for every 20 harvests per day, with any late or failed data harvests completed within the time specified by the government, but not to exceed one day from identification of failed or late data harvest.
A-3
(YES/NO)
All collected data shall be copied or uploaded to a network drive at the end of each shift with no more than 2 incidents of failed uploads identified per quarter.
No errors are allowed in the data submission process that result in a security violation.
Any instances where inaccuracies, incompleteness, or lateness of any deliverables are identified shall be corrected within 6 hours of notification, unless otherwise substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement
6.2.3 Instrumentation, image, video, and/or other related data efforts: The contractor shall perform an initial review of all test data and verify the accuracy and completeness of the data prior to delivering to the Government.
This requirement entails 100%
No more than 1 technical error per fiscal quarter and no more than 1 late submission per fiscal quarter, as evidenced by a complaint substantiated by the COR which shows non-compliance with contract requirements.
All documents generated to support this requirement shall have no more than 1 non-technical error, inclusive of spelling, punctuation, grammar, word usage, format, and style, for every 3 pages of a document, whereby a page is defined as 8.5 x 11” in size, single spaced with 12 point font.
A-4
(YES/NO)
contractor support of the conditions set in this requirement with 100% completion of information requested within the schedule specified by the deliverables are identified shall be corrected substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement
6.2.5 Data quality
support: The contractor shall perform an initial review of all test data and verify the accuracy and completeness of the data prior to delivering to the Government.
This requirement entails 100% contractor support of the conditions set in this requirement with 100% completion of information requested within the schedule specified by the government.
No more than 1 technical error per 9 man-hours of support per day, inclusive of all data sources that are being quality checked and no more than 1 non-technical error, inclusive of spelling, punctuation, grammar, word usage, format, and style, for every three pages of a document, whereby a page is defined as 8.5 x 11” in size, single-spaced in 12 point font.
Data quality reviews that provide 100% accuracy and completeness of data related to test safety issues.
All documents and data shall be reviewed within the specified schedule provided by the government, with no more than 1 complaint per fiscal quarter per full-time person assigned to the data quality role as to the timeliness of data quality reviews completed, with all complaints substantiated by the COR
A-5
(YES/NO)
which shows non-compliance with contract deliverables are identified shall be corrected substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement
6.2.1 Data
processing: The contractor shall meet 100% of the conditions set in this requirement with 100% completeness of information required within the schedule specified by the government.
No more than 1 complaint per fiscal year as to the accuracy or timeliness of any custom forms and databases generated or to the accuracy or timeliness of processing of data, with all complaints substantiated by the COR which shows non-compliance with contract deliverables are identified shall be corrected within 1 to 10 working days of notification depending upon the complexity of the document, unless otherwise specified by the substantiated complaint is defined as a
A-6
(YES/NO)
complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement
6.2.2, 6.2.3 & 6.2.4 Data uploading:
The contractor shall meet 100% of the conditions set in this requirement with 100% completeness of information uploaded within the schedule specified by the government.
No more than 1 complaint per fiscal year as to the timeliness or accuracy of data or documents uploaded to electronic databases, as substantiated by the COR which shows non-compliance with contract requirements.
deliverables are identified shall be corrected within 5 working days of notification, unless otherwise specified by the government.
substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement
C.3.1 TECHNICAL WRITING, DATA AND WORD PROCESSING SUPPORT
6.4.1 Technical
writing: The contractor shall perform an initial review of all technical documents and verify the accuracy and
No more than 1 error, inclusive of spelling, punctuation, grammar, word usage, format, style, and accuracy (e.g., incorrect arithmetic or orientation), per three pages of the body of a report or document, whereby a page is defined as 8.5 x 11” in size, single spaced with 12 point font.
A-7
(YES/NO)
completeness of the data prior to delivering to the Government.
The contractor shall meet 100% of the conditions set in this requirement with 100% completeness of information required within the schedule specified by the government.
No more than 1 error, inclusive of spelling, punctuation, grammar, word usage, format, style, and accuracy (e.g., incorrect arithmetic or orientation), per six pages of the appendix of a report or document, whereby a page is defined as 8.5 x 11” in size, single spaced with 12 point font.
No more than 1 complaint per fiscal year as to the timeliness of reports or documents generated, with all complaints substantiated by the COR which shows non-compliance with contract requirements.
deliverables are identified shall be corrected within 1 to 10 working days of notification depending upon the complexity of the substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement
6.4.3 Publishing and
distributing documents: The contractor shall meet
No more than 1 complaint per fiscal year as to the accuracy, completeness, or timeliness of documents generated, published, or distributed, with all complaints substantiated
A-8
(YES/NO)
100% of the conditions identified in this requirement with 100% completeness of information required within the schedule specified by the government. All documents shall be delivered, uploaded, or published to the correct agencies and databases in the agreed upon timeframe and in accordance with security procedures as identified by the government POC.
by the COR which shows non-compliance with contract requirements.
deliverables are identified shall be corrected within 1 to 5 working days of notification, unless otherwise specified by the government.
substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement
6.4.4 Data
uploading: The contractor shall meet 100% of the conditions set in this requirement with 100% completeness of information uploaded within the schedule specified by the government.
No more than 1 complaint per fiscal year as to the timeliness or accuracy of data or documents uploaded to electronic databases, deliverables are identified shall be corrected within 5 working days of notification, unless otherwise specified by the government.
substantiated complaint is defined as a
A-9
(YES/NO)
complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement
6.4.2 & 6.4.5 Technical writing reviews and expertise: The contractor shall meet 100% of the conditions identified in this requirement with 100% completeness of information required within the schedule specified by the government.
No more than 1 complaint per fiscal year, as to the accuracy or timeliness of reviews or technical writing-related expertise provided, deliverables are identified shall be corrected within 1 to 10 working days of notification depending upon the complexity of the substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement
C.3.1 RANGE SCHEDULING SUPPORT
6.5.1 Range
scheduling requirements coordination: The contractor shall coordinate 100% of the assigned scheduling
No more than 4 incidents per man-year of contract support where scheduling requirements are not accurately input into the Range Control Database Scheduling System within 4 business hours of receipt of the scheduling requirement, each corrected to 100% accuracy within 1 hour of identification of the error.
A-10
(YES/NO)
requirements with 100% completeness of schedule.
No more than 3 incidents per man-year of contract support are allowed where the support provided resulted in a direct delay or issue with test execution due to inaccurate scheduling guidance provided.
substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement
6.5.2 Resolution of
range scheduling issues: The contractor shall meet 100% of the conditions identified in this requirement with 100% completeness of information required within the schedule specified by the government.
100% resolution of scheduling problems or conflicts with no more than 3 complaints from the government POC, COR, customers, coworkers, or test officers per man-year of contract support as to the level of support provided, inclusive of complaints as to the degree of tact and diplomacy used to complete this requirement.
substantiated complaint is defined as a complaint validated by the COR which shows that the contractor failed to exercise good-faith judgment in completing this requirement
6.5.3 Range
scheduling meeting attendance: The contractor shall meet 100% of the
Contractor attendance at 100% of all scheduled meetings as required, with no incidents of unexcused absences.
A-11
(YES/NO)
conditions identified in substantiated complaint is defined as a this requirement with complaint validated by the COR which shows 100% completeness that the contractor failed to exercise good-of information faith judgment in completing this requirement required within the or that the contractor made severe errors in schedule specified by the quality of the work performed.
the government.
| DEPARTMENT OF THE ARMY |
| 1. INTRODUCTION |
| 2. PURPOSE |
| 3. AUTHORITY |
| 4. RESPONSIBILITIES |
| 5. METHODS OF QA SURVEILLANCE |
| 6. PERFORMANCE STANDARDS. |
| 9. CONTRACT INFORMATION |
| 10. ATTACHMENTS |
File details come from the government source that posted it. Updated .