CARA_PWS.docx

Performance Work Statement (PWS) for Combined Altitude Radar Altimeter (CARA)

04 June 2015 Prepared by:

AFLCMC/WWAP

Fighter/Bomber Directorate Hill AFB, Utah 84056

PR Number: F2DCAQ5125B001

REVISION RECORD

Table of Contents

5.5 Ozone Depleting Compounds…………………………………………………………

6.0 SERVICES SUMMARY………………………………………………………………..13

6.1 Government Quality Assurance Surveillance……………………………………………… 15

6.2 Assessment of Non-Services Summary Items……………………………………………. . 15

6.3 Remedies for Non-Conformance……………………………………………………………...15

6.4 Methods of Surveillance………………………………………………………………………..15

7.0 ATTACHMENTS……………………………………………………………………….15

ACRONYM LIST

1.0

INTRODUCTION

1.1 Purpose

1.1.1 The purpose of this effort is to include tasks required to keep the A-10 Weapon System sustained throughout the remainder of its service life, and to continue the sustainment and modernization of the A-10C aircraft avionics systems for the replacement of the APN-224 Radar Altimeter with the APN-232 Combined Altitude Radar Altimeter (CARA). The APN-232 has been identified as the replacement to the APN-224 radar altimeter.

1.2 Scope

1.2.1 This PWS defines the work necessary for the Contractor to develop and update source data, develop and produce a non-kitted field level TCTO solution, support of the CARA Flight Tests, and technical order changes affected by the APN-232 CARA Group A and Group B kit integration into the A-10C aircraft.

1.2.2 Aircraft Baseline:

All tasks described in this PWS apply to all active A-10C aircraft currently in service. The baseline shall be aircraft with the following modifications installed:

· SUITE 8 (TCTO 1A-10C-584)

2.0 APPLICABLE DOCUMENTS

2.1 Compliance Documents

These documents form a part of the proposed work only to the extent they are referenced in the main body of the PWS. In the event that a contradiction between the following documents and this PWS occurs, the order of precedence will be this PWS and then the referenced documents.

2.1.1 Military Documents

a. MIL-STD-38784, Standard Practice for Manuals, Technical: General Style and Format

b. MIL-DTL-38804, Time Compliance Technical Orders Preparation

c. MIL-STD-2073-1D, Standard Practice for Military Packaging

2.1.2 USAF Publications

a. TM 86-01P USAF Technical Manual Contract Requirements

b. USAF Technical Order Management Plan

c. USAF Technical Order Verification Plan

d. TO 00-5-1, Air Force Technical Order System

e. TO 00-5-3, Air Force Technical Manual Acquisition Procedure

2.1.3 Other

a. ASME Y14 series, Engineering Drawing and Related Documentation Practices

b. Technical Order Process Plan

c. 08-A10DOC-001, A-10 Drawing Practices

d. SAE-AS50881E, Wiring, Aerospace Vehicle

3.0 CONTRACTOR TASKING/REQUIREMENTS

3.1 Background

The current A-10 radar altimeter, the APN-224, is experiencing multiple obsolescence and reliability issues. An Operational Assessment (OA) was performed on the APN-232 CARA to validate its superiority over the current APN-224. WR-ALC and the user community have determined the APN-232 will replace the APN-224 on the A-10. 346 Group-B CARA Line Replaceable Units (LRU) units have already been purchased by the USAF and are currently being stored at the Defense Logistics Agency (DLA) warehouse in Robins AFB, GA. The following tasks shall be completed by the contractor for this modification:

· Develop drawing changes for aircraft installation and aircraft system and subsystem drawings and diagrams

· Develop source data for Technical Order (TO) changes, to include job guides, troubleshooting manuals, and all other affected TO commodity books

· Develop/Modify TO’s and Field-level Time Compliance Technical Orders (TCTOs) for Group-A and -B kit installation which must be accepted and approved by the November 2016 TO cutoff for the May 2017 publishing date

· Perform a validation of technical order source data changes to all technical manuals, drawing changes, engineering orders, and engineering change proposals

· Develop a non-kitted/field level installation (< 25 hour install) TCTO using stock listed parts only

· Design wire harness standoffs to prevent chaffing against the CARA LRU mount

· Support Government verification of all technical order source data changes to all technical manuals, drawing changes, engineering orders, flight testing and engineering change proposals

· Plan, schedule and execute contractor-hosted meetings or telecoms as required for the above tasks

· Build prototype kits of the government approved solution

3.2 Deliverables/Tasking’s (Services Summary)

3.2.1 Group-A Wiring Kit Design (Contract Data Requirements Lists (CDRL’s) A002, A003, A007) The contractor shall be responsible for designing aircraft and wiring modifications necessary to integrate the APN-232 CARA into the A-10C aircraft. The design shall use stock listed, air/flight worthy components only. The design shall be incorporated into a non-kitted field-level TCTO which will be used for final installation of the APN-232 into A-10C aircraft. All designs shall adhere to the wiring standards set forth in the SAE-AS50881E and be approved by AFLCMC/WWA.

3.2.1.1 The contractor shall design a wiring harness which will allow the APN-232 CARA to electrically interface with the A-10C aircraft.

3.2.1.2 The contractor shall finalize design of a wiring modification to the Right Hand Circuit Breaker Panel and the Auxiliary Circuit Breaker Panel that will provide power to the APN-232 CARA.

3.2.1.3 The contractor shall design a solution that mitigates wire chafing caused by the installation of the APN-232 CARA into A-10C aircraft.

3.2.1.4 During the design of the initial harnesses, any applicable design questions, comments, or concerns shall be directed toward A-10 System Program Office (SPO) Engineering (AFLCMC/WWAE) for resolution.

3.2.1.5 After the initial wire harness design has been approved by AFLCMC/WWAE the contractor shall acquire the parts necessary to build three prototype kits as directed by the SPO.

3.2.1.6 After all applicable design concerns have been resolved and the prototype harness construction and kits has successfully been demonstrated and approved by the A-10 SPO (AFLCMC/WWA), the contractor shall construct six additional Group A wiring kits utilizing any design updates that may have been made during the initial prototype Group A wiring kit construction to be used for the fit check for the prototypes. The location of the fit check shall be determined no later than (NLT) 30 days prior to completion of the wiring kit construction.

3.2.2 Non-Kitted and Field-Level TCTO Solution (CDRLS A002, A006, A007)

3.2.2.1 The contractor shall provide a solution in which the Group-A wiring kit will be a non-kitted field-level TCTO using stock listed parts only. The TCTO shall be approved by AFLCMC/WWA.

3.2.2.2 The TCTO shall be achieved by a field-level TCTO to meet Government requirements for Group-A and –B kit installation. This limits the installation time to less than 25 man-hours for the completion of the modification.

3.2.3 Drawings/Engineering Documentation

The contractor shall create accurate and error-free engineering documentation of all changes that result from the addition of the APN-232 CARA into the A-10C aircraft. This shall include the correction of prior technical data that is found to be in error/inaccurate and affected by this modification. The Contractor shall be provided the drawing package that details the Government reviewed and approved design of radar altimeter wiring kits, and AN/APN-232 CARA. Changes to this drawing package may be required as a result of various contract tasks, such as validation/verification and TCTO-proof. All drawings shall be in accordance with 08-A10DOC-001, A-10 Drawing Practices, and ASME Y14 series, Engineering Drawing and Related Documentation Practices (CDRL A002, A003, A007). This task shall include modification, harness, and installation drawings as well as engineering orders written against current baseline drawings.

3.2.3.1 The government shall have 30 working days to review, approve, disapprove, or submit comments for all submitted drawings.

3.2.4 Technical Orders

All TOs updated as a result of this modification shall show before and after data as well as effectivity in the technical documentation. TOs shall be IAW TO 0051, TO 0053, and TM 86-01P. All TO modification’s to include all technical data delivery must be accepted and approved by the November 2016 TO cutoff for the May 2017 publishing date. (CDRL A003, A007)

3.2.4.1 TO Validation

The Contractor shall provide validated TO source data and TCTOs that incorporate the results of In-Process Review efforts as validated on field representative assets. All required Government Furnished Equipment (GFE) to perform validation efforts shall be coordinated through the Government program manager. This activity is to be performed in conjunction with Government TO verification to insure the efficient use of Government assets (CDRL A003, A007).

3.2.4.2 TCTO Kit-Proof The Contractor shall assemble all required components for installation of the Group A wiring kit and deliver to the Government within 270 calendar days after receipt of (ARO) contract for kit proofing to ensure that the kit, as developed, meets the Government’s requirements. The Contractor shall provide personnel to observe the kit proof to address/resolve any issues that arise, if needed. The location of the kit proof shall be determined no later than (NLT) 30 days prior to kit delivery. The estimated duration of the kit proof is 3 workdays (CDRL A007).

3.2.5 Flight Test

The contractor shall assist the flight testing portion of this requirement of open-air test missions. It is anticipated that flight testing will be conducted at Eglin AFB, Florida, Davis-Monthan AFB, Arizona or Nellis AFB, Nevada. Reference PWS paragraphs 5.1, 5.1.1, 5.2, and 5.2.1 for clearance and requirements for access.

3.2.6 Program Manager (PM) Deliverables

The Contractor shall establish and use disciplined, comprehensive, systematic program management practices. The Government will review the Contractor's plans for measurements to be used in tracking program status at the kick-off meeting. The deliverables for this tasking will include documentation of the specific task requirements and the engineering fulfillments of those requirements. (CDRL A001)

3.2.7 Meetings

The Contractor shall be responsible for the planning and scheduling of the Contractor-chaired meetings for the execution of tasks in this PWS. Where appropriate, and with Government Program Manager approval, the Contractor shall be permitted to combine meetings to achieve efficiencies. In-person meetings or meetings/conferences via teleconference or defense connect online (DCO) meetings will be determined for all meetings. It is anticipated that meetings will be held at Hill AFB, UT or in the local area. Besides the meetings stated in next paragraphs, the contractor shall also provide telecoms for program status if requested by the Government (CDRL A004, A005)

3.2.7.1 Technical Order Guidance Conference

The Contractor shall plan a Technical Order Guidance Conference (TOGC) at Hill AFB within 60 days of contract award to support the tailoring of the TM 86-01P for this effort. The meeting shall review the impacts to the TOs. The meeting shall also review the program Integrated Master Schedule (IMS) and overall TO IMS to identify possible conflicts with other modifications. The goal of the TOGC is to establish the program schedule, identify the Technical Order Review Team (TORT) and TORT chairperson, review the draft Technical Order Verification Plan (TOVP), review the Technical Order Process Plan (TOPP) and have an updated TM 86-01P at the conclusion of the meeting. (CDRL A003, A007)

3.2.7.2 In-process Reviews (IPR) (Refer to TM 86-01P)

The Contractor shall plan for two IPR’s IAW TM 86-01P. These IPRs may be conducted by telecon or video teleconference with the first IPR preferred face to face between the contractor and the Government. The Contractor shall provide resources for all formal reviews as defined by the TOPP.

3.2.7.3 Technical Order Verification

The Contractor shall provide TO source data that incorporate the results of Validation efforts. The Contractor shall also provide on-site support during Government TO Verification activities that may be conducted during the TCTO Proofing period. The Government shall identify the location/unit after the Second Look IPR. (CDRL A003)

3.2.7.4 Program Management Reviews (PMR’s)

The contractor shall schedule and support at least one PMR. At a minimum, the contractor shall present program status, schedule, milestone status, financial performance, risk/problem areas and reckoned corrective actions for Government review. These PMR’s will be either in person at the contractor’s facility, Hill AFB, Robins AFB, or via teleconference/DCO (CDRL A004, A005).

3.2.7.5 Design Reviews

The contractor shall execute a Preliminary Design Review (PDR) and a Critical Design Review (CDR) as part of system engineering major milestone reviews (CDRL A004, A005).

3.2.7.6 Kickoff Meeting

The contractor shall conduct and execute a kickoff between the Government and contractor NLT 30 days after contract award at Hill AFB, UT. The kickoff meeting may be conducted via teleconference if practical (CDRL A004, A005).

3.2.8 Program Schedule

3.2.8.1 The Contractor shall develop, update, and manage an Integrated Master Schedule (IMS) for the technical manuals to be updated under this contract as well as all other program milestones. The IMS shall integrate the tasks of all members of the Contractor's team and allow critical path methodology to determine/track the program's critical elements. The IMS shall contain all control points (milestones) plus all requirements for reviews, audits and meetings required by this PWS. The schedule shall be maintained in Microsoft Project (*.mpp) format included as a regular part of all meetings and telecoms and delivered as part of the monthly status report (MSR). (CDRL A001, A006)

3.2.8.2 The Contractor shall also maintain a record of program problem areas and problem resolutions (i.e. risks/issues). The Contractor shall report problem areas and problem resolutions at each design review, program review, and monthly status reports (MSR). (CDRLs A002, A003, A001)

3.2.9 Subcontract Management

The Contractor shall provide a subcontracting plan and ensure flow-down of process, quality and other standards, specifications, and terms and conditions to subcontractors if the contractor subcontracts any workload on this contract to other entities. The Contractor shall be solely responsible for the performance and quality of all subcontractor work performed in response to the requirements of this contract. The Contractor shall identify, track, and monitor subcontractor data submittals and significant technical, quality, schedule, and milestone achievements and incorporate into the execution schedule. The Contractor shall ensure all contractual requirements are allocated down to the subcontractor level. The Contractor shall report subcontract status at each PMR.

3.2.10 MSR

The Contractor shall provide a MSR that, at a minimum, shall include a monthly status summary, projected activity within the next month, any GFE/ Government Furnished Material (GFM)/ Government Furnished Property (GFP) requirements or issues, open correspondence issues, schedule, risk management update, and the status of technical data and other CDRLs. (CDRL A001)

3.2.11 Contractor Manpower Requirement

IAW FY11 NDAA Section 8108, the Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the A-10 System Program Office via a secure data collection site. The Contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the Contractor Manpower Reporting Application (CMRA) help desk.

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and Contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the Contractor name and contract number associated with the data.

User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for government personnel and Contractors are available at the Army CMRA link at http://www.ecmra.mil.

3.2.12 Deliverable - Final Report

The Contractor shall deliver a final report that shall include final revisions of all drawings, source data, TCTOs, TO changes, engineering orders, non-kitted TCTO solution with applicable parts and any other technical submissions. These revisions shall include all Government prescribed red-line changes. This report shall be submitted to the Government for review and approval. (CDRLs A002, A003, A007)

3.2.13 Engineering Data

The Contractor shall use systems engineering and quality assurance processes to ensure thoroughness, accuracy, completeness during the development and analyses in this PWS that will ensure the delivery of error-free technical order source data, drawings, engineering orders, engineering change proposals, interface control documents, and all other technical submissions. The Contractor shall support Government reviews of data, drawings, and documentation to be included in any data package changes. The Contractor and subcontractors/vendors shall correct discrepancies identified during in house reviews to minimize errors in data delivered to the A-10 SPO. The Contractor and subcontractors/vendors shall also track and correct discrepancies identified during all reviews with the A-10 SPO, resubmit data, and take action to improve their processes and in house reviews to eliminate the reoccurrence of the same type of errors. After each review the Contractor shall ensure that all ensuing technical data with the same or similar discrepancies shall be corrected prior to delivery to the A-10 SPO. All technical data to be disseminated is to be marked with the appropriate distribution statement, export control warning (where applicable), and destruction notice (where applicable) IAW DoD 5230.24 and 25. (CDRLs A002, A003, A007)

3.2.13.1 Data Rights

All data generated under the tasks defined in paragraph 3.0 of this PWS shall be developed for the A-10 and shall be non-proprietary (unlimited rights). All existing vendor proprietary data used in the execution of these tasks, such as trade studies, shall be marked as Third Party Proprietary Data and provided to the Government for Government Internal Use Only (not to be disseminated outside the Government). The Government shall have unlimited rights to all intellectual property, material solutions or concepts, including all items, and data developed by the Contractor and/or its subcontractors under this contract. The Government may use any such items, data, or other property for re-procurement or any other purpose as stated in the DFARS definition of “unlimited rights.” The Contractor shall identify and receive written approval from the Procuring Contracting Officer (PCO) prior to committing to the use of any privately-developed items, components, processes, computer software and/or technical data which the Contractor intends to deliver with limited rights, Government purpose rights, or restricted rights.

3.2.13.2 Discrepancies

The Contractor and subcontractors/vendors shall correct discrepancies identified during reviews, resubmit data, and take action to eliminate their reoccurrence.

3.2.14 Associate Contractor Agreement (ACA)

The Contractor shall establish ACAs as necessary to affect the design and to accomplish the requirements of this program. Non-Disclosure Agreements (NDAs) shall be established with the vendors, as required to support the tasks identified in this PWS.

3.2.15 Quality Assurance Program

The Contractor shall assure quality through implementation of a quality program in accordance with current ISO 9001 processes. The quality program shall ensure that solutions, products, and services fully satisfy Government specified requirements, and are of the highest level of quality.

4.0 PERIOD OF PERFORMANCE (PoP) AND DELIVERABLES

4.1 The PoP for this contract is 18 months after contract award with an option for 3 additional months for technical assistance for the effort. If deemed necessary by the Government, the government will exercise the technical assistance option for potential technical data modification, and testing and fielding support.

4.2 Deliverables (Contractor Data Requirements List)

The Contractor shall prepare and deliver data IAW references in earlier sections. All Data Item Descriptions (DIDs) in the Contractor Data Requirements List, as contained in the following table, shall be used as guides in developing the data. Distribution and Number of Copies: All CDRL items will be logged into and maintained in the Contractor's electronic library, and a cover letter paper/electronic submittal will be provided to the Government's Contracting Officer identifying the data item and its configuration identification (date and revision level). Late submittals shall be coordinated through the Government PM.

DI-TMSS-81812

3.2.6, 3.2.8.1, 3.2.8.2, 3.2.10

DI-SESS-80776A

3.2.1, 3.2.12, 3.2.13, 3.2.3

DI-TMSS-80229D

Notice 1-Validation 3.2.1, 3.2.3, 3.2.4, 3.2.4.1, 3.2.7.1, 3.2.7.3, 3.2.8.2, 3.2.12, 3.2.13

Amendment 1

DI-ALSS-81531

3.2.1, 3.2.3, 3.2.4, 3.2.4.1, 3.2.4.2, 3.2.7.1, 3.2.12, 3.2.13

4.3 Government Inspection and Acceptance of Deliverables

The Government will have the right to reject or require correction of any deficiencies found in deliverables. In the event of rejection of any deliverable, the Contractor will be notified in writing by the Government of the specific reasons why the deliverable was rejected. The Government shall have the right to require that the Contractor make changes to any submissions until the final CDRL submissions have been accepted.

5.0 ADMINISTRATIVE

5.1 Security

Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for information shall be forwarded to the A-10 SPO PCO.

5.1.1 Security Classified Information

It is anticipated that the efforts for this task will not require access to classified information. No DD Form 254 is necessary at this time.

5.2 Access to Government / Contractor Facilities and Property The Government Program Manager will assist Contractor personnel in processing the necessary DoD forms to obtain base or area badges for access to Government facilities. The Contractor shall obtain base identification for all Contractor personnel who make frequent visits to or perform work on the Air Force installation(s) cited in the Contract. Contractor personnel are required to wear or prominently display installation identification badges or Contractor-furnished, Contractor identification badges while visiting or performing work in the installation. During performance of the contract, the Contractor shall be responsible for obtaining required identification for newly-assigned personnel and for prompt return of credentials for any employee who no longer requires access to the work site. Access to Government facilities is limited; control of facilities shall remain with the Government.

5.2.1 Controlled/Restricted Area Access

When work under this contract requires unescorted entry to controlled or restricted area, the Contractor shall comply with AFI 31-101, Volume 1, The Air Force Installation Security Program, and the AFI 31-501, Personnel Security Program Management, as applicable.

5.3 Government Furnished Equipment, Materials, and Software

All products developed under this contract shall be considered Government work and shall have no license encumbrances. All Government Furnished Property (GFP) to include Government Furnished Equipment (GFE), and Government Furnished Material (GFM) shall be returned to the Government upon completion of this contract. The Contractor shall provide a comprehensive list of all anticipated GFP requirements at the time of proposal and in the MSR. Additionally, the Contractor shall provide a criticality level for each item and a description of possible workarounds if an item is unavailable for use under this task. Upon contract award official requests shall be made through appropriate Government Contracting Officer channels NLT 60 days prior to actual need date for GFE, NLT 30 days for GFP, and GFM. The Government will provide these as deemed necessary and available, excluding proprietary data, upon request of the Contractor. Requests shall be made through appropriate Government Contracting Officer channels. (CDRL A001)

The Government will provide, upon request of the Contractor, pertinent background data such as existing T-2 modification package, engineering drawings, access to the A-10 TO library, and A-10 systems architecture. Requests shall be made through appropriate PCO channels. The Government shall perform the installation and kit proofing of the first production wiring kit. The Government will provide, upon request of the Contractor, any GFM necessary for the completion of the contract. Requests shall be made through appropriate PCO channels.

5.4 Government Program Management and Contract Management

5.4.1 Government Program Management

The A-10 Division (AFLCMC/WWA) will provide the Government Program Manager for this effort. The Government Program Manager will provide the Contractor access to all available technical data required to perform approved tasking.

5.4.2 Government Contract Management

The Air Force Procurement Contracting Officer (PCO) shall be responsible for contract management. Only the PCO can make changes affecting this contract. Any instances where implied or explicit direction, received from any Government representative and perceived by the Contractor to affect performance of tasks under this contract, or to have a material impact on costs incurred in association with this contract, shall be brought to the immediate attention of the PCO for disposition and instructions before proceeding with any work thus affected.

5.4.3 Travel

Airfare for travel and per diem shall be billed IAW Joint Travel Regulations (JTR). The Contractor is responsible for making all necessary travel arrangements. Actual travel expenses are limited by Government travel regulations. All travel will be accomplished IAW FAR 31.205-46.

Projected travel events are below but are not all inclusive.

a. Kickoff Meeting

b. Program Management Reviews (PMR’s)

c. TOGC

d. Technical Order IPR’s

e. Fit Check Prototypes

f. Flight Test(s)

g. Technical Order Validation/Verification support

h. Kit Proof

5.5 Ozone Depleting Compounds

The contractor shall eliminate all Class I Ozone Depleting Compounds (ODCs) in the fulfilment of the requirements of this contract, IAW AFMCI 20-102, 11 Jul 13

6.0 SERVICES SUMMARY

The following table summarizes the performance objectives and thresholds that will be used to assess contractor performance and compliance of the associated PWS.

SERVICES SUMMARY

Integrated Master Plan-Integrated Master Schedule

(Monthly)

Conference Agenda and Minutes

6.1 Government Quality Assurance Surveillance

The role of the Government quality assurance is to ensure that the contract standards are achieved. In this contract, the quality control program is the driver for service quality. The Contracting Officer Representative (COR) will review comments from functional and technical experts and contracting personnel. The contractor will be notified of comments/corrections as required. For all tasks, the Contractor shall perform engineering and quality assurance processes to ensure thoroughness, accuracy, and completeness during the development of all deliverables under this PWS and to ensure the delivery of near error free, high quality technical data.

6.2 Assessment of Non-Services Summary Items

All other tasks required under the PWS may be inspected on a random basis and at a frequency determined by the CO, COR supervisor, and/or COR per the Inspection of Services Clause within the contract.

6.3 Remedies for Non-Conformance

If inspections indicate unacceptable performance, the COR will notify the contractor’s POC of the deficiencies for correction. After notification of the unacceptable performance and depending on the discrepancy identified, the contractor shall be given an appropriate period of time to correct the deficiency. If deficiencies are not corrected within the required timeframe, the COR shall notify the CO for action. If the contractor disagrees with the noted discrepancy and an agreement cannot be reached, the CO shall be notified for a final decision.

6.4 Methods of Surveillance

6.4.1 One-Hundred Percent Inspection

This method implies inspecting every time the requirement occurs. Use of this technique may be appropriate when performance has an especially critical impact on mission accomplishment or safety, occurs infrequently, or contains stringent requirements.

6.4.2 Periodic Surveillance/Inspection

Periodic surveillance/inspection is the type of surveillance that is based upon selecting samples for evaluation on other than 100% inspection or on a statistically random basis. Periodic surveillance can be accomplished periodically using a checklist method.

7.0 ATTACHMENTS:

A. TM 86-01P (Aircraft & Commodity) B. Technical Order Process Plan C. Technical Order Life Cycle Management Plan D. Bidders’ Library image1.jpeg