PWS.pdf

PDF 78 KB Posted

Attached to
Analog to Digital Converter Federal contract opportunity
Solicitation number
FA8539-16-R-0014
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Robins Air Force Base

About this file

Performance Based Work Statement

View the file

Other files for this federal contract opportunity

Other files attached to Analog to Digital Converter, newest first.
File Type Posted
FA853916R0014_______0002.pdf PDF
PWS_REV1.pdf PDF
FA853916R0014_______0001.pdf PDF
CDRLs.pdf PDF
FA853916R0014.pdf PDF
CDRL_A003.pdf PDF
CDRL_A002.pdf PDF
FA8539-16-R-0014.pdf PDF
CDRL_A005.pdf PDF
PWS.pdf PDF
CDRL_A004.pdf PDF
CDRL_A001.pdf PDF
CDRL_A007.pdf PDF
CDRL_A006.pdf PDF
PWS.pdf PDF
CDRLS.pdf PDF
Show all 16

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

PR: FD2060-16-00613 PWS REVISION: 0 1

Distribution Statement: C

Performance-based Work Statement

For

Engineering Services of the Analog to Digital Converter CCA

PR: FD2060-16-00613

12 August 2016

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government Agencies and their contractors only to protect information and technical data that relates to a specific military deficiency and to protect information on the system that is in the concept stage from premature dissemination (29 July 16). Other requests for this document shall be referred to 407 SCMS through government contracting office.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or the Export Administration Act 1979, as amended (Title 50, U.S.C., App. 2401 et seq.). Violators of these export laws are subject to severe criminal penalties. Disseminate IAW the provisions of DoD Directive 5230.25.

HANDLING AND DESTRUCTION NOTICE: Comply with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

PR: FD2060-16-00613 PWS REVISION: 0 2

1.0 Description of Services

1.1 Objective(s): This Performance-based Work Statement (PWS) describes the services required to redesign the Converter Circuit Card Assemblies (CCA) within the Analog to Digital Converter (ADC) used on the AN/APY-1/2 radar. The CCAs are components that perform the analog to digital converting within ADC which provides signal manipulation for the APY-1/2 radar system. These services require the contractor to accomplish a redesign of designated non-stock listed part numbers observing accepted quality standards and relevant technical standards.

The contractor shall ensure that all production assets pass all qualification and integration testing and that the technical data package contains no more than one revision of the data after initial submission and all drawing errors are corrected and returned within seven calendar days.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by maintaining the APY-1/2 radar system to provide a continued flow of serviceable assets to the warfighter thus increasing the mission capable rate and reliability of the weapon system. The continued operational availability and reliability of the APY-1/2 radar is critical to support the current mission requirement of the E-3 Airborne Warning and Control System (AWACS) aircraft. This effort will ensure availability levels are maintained. Continued availability of this system is critical.

1.3 Background: This PWS tasks the contractor to provide a Form Fit Function Interface (F3I) redesign of specified AN/APY-1/2 Radar system hardware, part number 3D62318G01 as described in Northrop Grumman source control drawing 782R746 and a Design Try-Out (DTO) for part number 3D62309G01 as described in Northrop Grumman source control drawing 782R746.

2.0 Services Summary:

Performance Objectives PWS

Reference Performance Threshold

Deliver two production first article items according to the new design.

4.3.1 Two production assets of the redesigned CCA and two

DTO units of each configuration shall successfully complete qualification and integration testing within a period of performance of 18 months and be delivered to 407 SCMS/GUEA.

Deliver the complete technical data package required for procurement of the new design.

4.3.7

No more than one revision after initial submission and all drawing errors are corrected and returned within seven calendar days.

Establish and maintain Contractor Manpower Reporting.

5.6 Within 30 calendar days of contract/order award, the

Contractor shall establish a record for the contract/order in eCMRA including Order Data, Contact Data and Location Data and make the annual report- no later than October 31 of the following fiscal year.

PR: FD2060-16-00613 PWS REVISION: 0 3

3.0 Government Property and Services

3.1 Government Property:

3.2 Government Property to be Provided: Government property in an unserviceable condition identified by part number and NSN in paragraph 1.3 may be provided if available as an engineering exhibit to accomplish this effort.

3.3 Reporting of Government Property: The Contractor shall create and maintain records of all Government property accountable to the contract, including Government-Furnished Property (GFP) in accordance with (IAW) the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

3.4 Loss of Government Property:

Reporting Loss of Government Property, the Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application to report loss of Government property at the site below IAW the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order. http://www.dcma.mil/aboutetools.cfm

3.5 Return/Retention of Government Property:

All property provided by the Government remains the property of the Government and shall be returned to the Government upon completion of the contract/order unless the Procuring Contracting Officer (PCO) directs the contractor to retain the property for continued use under a successor contract. Retention of the property by the contractor will require modification of both losing and gaining contracts IAW the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO.

All material generated under the contract/order becomes the property of the Government and shall be returned to the Government upon completion of the contract/order. All Department of Defense (DD) Form 1423-1, Contract Data Requirements List (CDRL) deliverables become the property of the Government upon receipt.

3.6 Government System(s): The Government will provide contractor personnel access to system(s) necessary to perform tasks under the contract/order. Upon completion/termination of the contract/order or transfer/termination of contractor personnel, the system account(s) will be closed.

4.0 Technical Requirements

PR: FD2060-16-00613 PWS REVISION: 0 4

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order is 18 months.

4.1.2 Place of Performance: These services will be performed at facilities established by the contractor. Services are not expected to be performed on a USAF installation or Robins AFB.

4.2 Contract Data Requirements List (CDRL):

4.2.1 The Contractor shall deliver all data/reports associated with all CDRLs, with no more than one rejection of each deliverable. There shall be no more than one total rejection(s) of deliverables per reporting period. The Government will reject a deliverable if one or more technical errors or two or more minor errors are found within the deliverable. A technical error is defined as the format not being IAW the CDRL or the content not being accurate and complete IAW the CDRL, PWS or contract. A minor error is defined as a typographical or grammatical error. The rejected deliverable shall be corrected and resubmitted within fourteen business days of notification of Government rejection IAW the associated DD Form 1423 instructions/requirements.

4.2.2 The Contractor shall deliver all CDRLs with no more than one late submission(s) of deliverables per reporting period. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

A001, Service Engineering Report, DI-MISC-81384 A002, Test Plan, DI-NDTI-80566A A003, Report, Record of Meeting Minutes, DI-ADMN-81505 A004, Engineering Change Proposal, DI-CMAN-80639C A005, Product Drawings/Models and Associated Lists, DI-SESS-81000E/T A006, Contractor’s Progress, Status and Management Report, DI-MGMT-80227 A007, Counterfeit Prevention Plan, DI-MISC-81832

4.3 Engineering Services Details

4.3.1 Task Description: The new CCA designs shall be a Form, Fit, Function, and Interface (F3I) replacement for the legacy items and shall incorporate current, nonproprietary parts and technology with qualified sources defined by drawings and specifications. Two production assets of the redesigned CCA and two DTO units of each configuration shall successfully complete qualification and integration testing within a period of performance of 18 months and be delivered to 407 SCMS/GUEA. The new design CCAs shall incorporate considerations for:

a) Reliability: the new design shall provide at a minimum the reliability of the legacy design; b) Maintainability: the new design shall be repairable in a depot maintenance facility and require no special tooling or equipment; c) Supportability: the new design shall incorporate parts standardization when possible to avoid obsolescence.

PR: FD2060-16-00613 PWS REVISION: 0 5

4.3.2. Qualification Testing: The contractor shall perform qualification testing IAW legacy requirements to ensure that F3I requirements are met as well as the operational, physical, and environmental requirements of the legacy hardware. The requirements may be satisfied by functional and environmental testing with Government approval. The complete qualification results, testing, and/or analysis shall be documented and provided in the Service Engineering Report. [A001, DI-MISC-81384: Service Engineering Report]

4.3.3. Integration Testing: The contractor shall perform integration testing IAW a test plan submitted by the contractor. Test data shall support satisfactory compliance with requirements demonstrating F3I compliance with the APY-1/2 radar system. The results of the integration testing shall be documented in the Service Engineering Report. [A001, DI-MISC-81384: Service Engineering Report] [A002, DI-NDTI-80566A: Test Plan]

4.3.4. Preliminary Design Review (PDR): The PDR shall be held at the contractor’s facility, not to exceed 4.5 months after contract award. The PDR shall focus solely on the changes for the system and emphasize: a) the compatibility of the selected design approach with the requirements; b) a review of all analyses, circuit logic diagrams, and technical data available; c) the integrity of the selected design approach and the basis for the selection of the design approach presented; d) and a review of the major milestones schedule. The PDR establishes the formal identification of specific engineering documentation that defines the performance of the equipment. The contractor shall prepare an agenda and record the minutes for the PDR. [A003, DI-ADMN-81505: Report, Record of Meeting Minutes]

4.3.5. Critical Design Review (CDR). The CDR shall be held at the contractor’s facility when the detail design is complete, not to exceed 9 months after contract award. The CDR shall emphasize: a) the compatibility of the design with the specification; b) the system compatibility of the completed design; c) a comparison of the interface documentation with the engineering drawings for the equipment and/or review of specification; d) a risk assessment of the selected design shall be conducted including identification and analysis of any specific risks; e) and a review for any medium or high risks that result from the assessment. The contractor shall prepare an agenda and record the minutes for the CDR. [A003, DI-ADMN-81505: Report, Record of Meeting Minutes]

4.3.6. Functional Configuration Audit / Physical Configuration Audit (FCA/PCA). The FCA/PCA shall be held at the contractor’s facility a maximum of 13.5 months after contract award and a minimum of 60 calendar days prior to initiating integration testing. The FCA/PCA shall emphasize: a) the presentation of test reports and demonstration that the new configuration functions correctly according to design documentation including any specifications, drawings, part lists, technical orders, test reports, and safety assessment reports; b) physical adherence of the new configuration to design documentation including all signage and placarding according to Government requirements; c) and a safety assessment to evaluate risk and ensure all system and operation hazards are identified. The contractor shall provide any identified safety issues during the PDR and/or CDR. The only potential risks to be discussed are ones which require government review or decision. If no safety risks are identified, the contractor shall state that there were no safety risks identified during PDR and CDR.

FD2060- 14-00033; 26 Dec 13 PWS Page 3

PR: FD2060-16-00613 PWS REVISION: 0 6

Any changes to the established FCA/PCA baseline will require the submission of an Engineering Change Proposal (ECP). The contractor shall prepare an agenda and record the minutes. [A003, DI-ADMN-81505: Report, Record of Meeting Minutes] [A004, DI-CMAN-80639C:

Engineering Change Proposal]

4.3.7. Engineering Data: The contractor shall develop, produce, maintain, and deliver a Technical Data Package (TDP) that accurately depicts the final product. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). All engineering product definition data created using Government funding as a result of this contract shall be considered a part of the TDP and shall be delivered to the Government with unlimited rights. The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision L (CAGE 98752). No more than one revision after initial submission and all drawing errors are corrected and returned within seven calendar days. Reference attached DD Form 1423 Block 16 [A005, DI-SESS-81000E/T: Product Drawings/Models and Associated Lists]

4.3.7.1. Engineering Data Guidance Conference. The contractor shall support and co-chair a Guidance Conference with AFLCMC/EZGEM for engineering data within 60 calendar days after contract award. The Conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. Note: Conference may be held in conjunction with other meetings or conferences. The contractor shall address, discuss, and provide status on the: understanding of all CDRL requirements, DIDs, specifications, and standards; TDP review and delivery requirements and schedules; contractor's drafting practices, procedures, drawing formats, and CAD programs; contractor's quality assurance procedures relating to TDP documents including quality control of subcontractor and vendor data; role of subcontractors and vendors who may deliver TDP documents under this contract; contractor's configuration management system, methods for releasing documents, approving documents, and incorporating changes into documents; and digital TDP deliverables. [A003, DI-ADMN-81505: Report, Record of Meeting Minutes]

4.3.7.2. In-Process Review (IPR). The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP.

The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50% percent completion point and shall be held, when possible, in conjunction with other

PR: FD2060-16-00613 PWS REVISION: 0 7

reviews (i.e., PDR, CDR). The contractor shall notify AFLCMC/EZGEM a minimum of 30 calendar days prior to the anticipated date of completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review.

If the quantity of subcontractor/vendor data is of sufficient magnitude, the 407 SCMS/GUEA may schedule a separate IPR at the subcontractor's/vendor's facility. [A003, DI-ADMN-81505:

Report, Record of Meeting Minutes]

4.3.7.3. Relationship of Contractor with Subcontractors & Vendors. The contractor shall levy on sub-contractors and sub-vendors the same requirements for TDPs as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.

4.3.7.4. Engineering Data Updates and Revisions. The contractor shall, and shall cause subcontractors and vendors to, update and maintain engineering data for the item(s) designed/ developed/produced under this contract for the life of this contract and shall incorporate all changes IAW the following: all engineering changes shall be incorporated into the applicable engineering data within 90 calendar days after engineering release/Air Force concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately; all engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review; all engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media (this includes all Engineering Orders (EO)’s generated as a result of the preliminary data review); and revisions to existing engineering drawings/models and associated lists and other documentation to be included in the TDP for which the contractor is the current design activity shall result in the delivery of the entire revised document and associated data file with no regards to how minor or major the revision.

4.3.8. Contractor's Progress, Status, and Management Report. The contractor shall provide a monthly status report via email to the 407 SCMS/GUEA. These reports shall include: current master schedule; significant technical activities performed by the contractor and subcontractor if applicable during the previous month; projected tasks for the next month; expenditure data;

identification of any risks to cost, schedule, and performance; and mitigation recommendations for any identified risks. [A006, DI-MGMT-80227: Contractor’s Progress, Status and Management Report]

4.4 Item Unique Identification (IUID)

4.4.1 Item Identification and Valuation, unique item identification is a method of marking items with unique item identifiers which have machine-readable data elements. Unique item identification is required for all items to be delivered to the DoD that meet the criteria established

PR: FD2060-16-00613 PWS REVISION: 0 8

IAW the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

4.4.2 The contractor shall mark items IAW contract clauses, and Military Standard (MIL-STD)- 130N, Department of Defense Standard Practice / Identification Marking of U.S. Military Property.

4.4.3 IAW the Department of Defense Guide to Uniquely Identifying Items Assuring Valuation, Accountability and Control of Government Property, the Government agent or contractor representative responsible for causing “life cycle events” (i.e., abandoned, consumed, destroyed by accident, destroyed by combat, donated, exchanged – repair, exchanged – sold, exchanged – warranty, expended – experimental/target, expended – normal use, leased, loaned, lost, reintroduced, retired, scrapped, sold – foreign government, sold – historic, sold – nongovernment, sold – other federal, sold – state/local, and stolen) will update applicable item record(s) in the IUID Registry.

4.5 Packaging

4.5.1 The Contractor shall package and mark material and production first articles IAW the contract (basic or order, as applicable) IAW Air Force Materiel Command (AFMC) Form 158, Packaging Requirements. The Contractor shall package and mark material IAW other applicable Government regulations including, but not limited to, those regarding security, safety and environmental concerns.

4.5.2 The contractor shall package and mark material for movement, shipment, receipt and storage in a manner that ensures the protection and preservation of the material for shipment to and storage at the destination. The Contractor shall package electronic parts susceptible to electrostatic discharge damage IAW MIL-STD-1686C, Department of Defense Standard Practice / Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices), and MIL- HDBK-263B, Military Handbook / Electrostatic Discharge Control Handbook for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices).

4.5.3 IAW MIL-STD-2073-1E, Standard Practice for Military Packaging, shipping containers received, which meet the requirements of the AFMC Form 158 and are suitable for return shipment of serviceable assets, shall be reclaimed and stored for reutilization. Unsuitable shipping containers shall be disposed of and replaced with new containers that meet the requirements of the AFMC Form 158.

4.6 Counterfeit Electronics Parts: The contractor shall establish policy and procedures to mitigate the risk of counterfeit electronics parts being installed in end items or otherwise entering the USAF/DoD inventory IAW Aerospace Standard AS5553A, Counterfeit Electronics Parts;

Avoidance, Detection, Mitigation, and Disposition.

PR: FD2060-16-00613 PWS REVISION: 0 9

4.6.1 Counterfeit Prevention Plan (CPP): contractors that supply electronic parts or systems that contain electronic parts shall establish policies and procedures to avoid, detect, mitigate and disposition counterfeit electronic parts to prevent such parts from entering the USAF/DoD supply chain. These policies and procedures shall be documented in a CPP for submission and approval IAW Data Item Description (DID) DI-MISC-81832 and accomplished for all specified contract items. DI-MISC-81832 is applicable to Parts, Material and Processes Selection (PMPS) associated with delivery of systems and assemblies to the USAF and DoD. The requirements established by DI-MISC-81832 also apply to electronics components procured in sustainment of such systems and assemblies. The requirements of the recently DoD-adopted SAE AS5553 Counterfeit Electronics Parts; Avoidance, Detection, Mitigation, and Disposition shall also apply. At a minimum, the CPP shall address: [A007, DIMISC-81832: Counterfeit Prevention Plan]

4.6.2. At a minimum, the CPP shall address:

4.6.2.1 Applicability. The contractor shall identify all Business locations and programs to which the CPP applies. The CPP shall address materials, hardware, electronic parts, and procured assemblies.

4.6.2.2 Definitions. The contractor shall utilize definitions per AS5553 to ensure consistency.

Any contractor-derived definitions must be included in an appropriate CPP appendix or annex.

(Ref. AS5553, paragraph 3, 3.1, 3.2, 3.3, appendix H)

4.6.2.3 Parts Availability and Use of Parts Brokers. The contractor shall not procure materials, systems, assemblies, subassemblies or parts from parts Brokers when available from Original Manufacturers (OM) or their Authorized Distributors. In cases where materials, systems, assemblies, subassemblies or parts are no longer available from the OM or their Authorized Distributors, procurement from Brokers may be authorized as defined by the contractor’s policy and their CPP. (Ref. AS5553, paragraph 4.1.1, 4.1.2.e., appendix A)

4.6.2.4 Procurement Policies. The contractor shall provide and implement policy directing development and implementation of business practices and procedures, and processes to prevent procurement of Counterfeit materials and parts. The contractor shall identify the appropriate office(s), business units, functional organizations, and programs, which shall have responsibility for development, maintenance and implementation of the CPP. The CPP shall identify the specific roles and responsibility for each. (Ref. AS5553, paragraph 4.1.2, 4.1.3, appendix B, C, D)

4.6.2.4.1 Risk Assessment. The contract shall address the risk of using unknown sources and/or unauthorized suppliers in the CPP. Application or technical risk assessments shall establish the effect that counterfeit parts may have on performance. Vendor or source of supply risk assessments shall establish the potential for obtaining counterfeit parts. Using any risk analysis tool acceptable to the Government, the contractor shall conduct a risk assessment based upon item characteristics and how likely it is that a counterfeit part will be received. The contractor shall identify and describe in the CPP how parts are selected for assessment and what risk is acceptable based upon the parts design, construction, material and functional requirements. As a

PR: FD2060-16-00613 PWS REVISION: 0 10

minimum, analysis shall be completed for flagging high risk items, such as items that are obsolete, discontinued, rare, etc. The contractor shall require completion of a trade study, documented within the CPP that shall facilitate determining whether 100% testing of parts procured from after-market sources is more cost effective than qualification or requalification of a manufacturer. (Ref. AS5553, paragraph 4.1.2, 4.1.3, appendix B, C, D)

4.6.2.5 Detection and Avoidance Responsibilities. The contractor shall establish processes for the review and approval of contractor and applicable subcontractor systems for the detection and avoidance of counterfeit electronic parts and suspect counterfeit electronic parts, which processes shall be comparable to the processes established for contractor business systems under section 893 of the Ike Skelton National Defense Authorization Act for Fiscal Year 2011 (Public Law 111–383; 124 Stat. 4311; 10 U.S.C. 2302 note). The contractor shall flow down such requirements and processes to their subcontractors per ODASD Memo titled “Overarching DoD Counterfeit Prevention Guidance”, dated 16 March 2012. (Ref. AS5553, paragraph 4.1.4, 4.1.5, appendix E)

4.6.2.6 Testing and Verification. The contractor shall establish and accomplish testing and verification processes for items not received from an original equipment manufacturer, original component manufacturer, or authorized distributor that are identified as having high risk for counterfeit potential. These processes apply to prime contracts, and to subcontracts or suppliers below the prime contracts. The contractor shall provide a list of acceptable test facilities if the subcontractor or supplier does not have the capability to perform required testing. Submittal of Certificates of Compliance indicating the parts are not counterfeit shall be acceptable for verification of testing. (Ref. AS5553, paragraph 4.1.4, appendix E)

4.6.2.7 Configuration Identification and Traceability. The contractor shall identify and control the configurations of all systems, assemblies, subassemblies and parts, and enable mechanisms to provide traceability of parts. The contractor shall report to the Government when control of the configurations of all systems, assemblies, subassemblies and parts, and mechanisms to provide traceability of parts are not possible. The contractor shall identify the specific systems, assemblies, subassemblies and parts beyond the contractors’ control. The contractor shall be responsible for detecting and avoiding the use or inclusion of counterfeit materials and parts, to include procured assemblies and subassemblies, in such products and shall be responsible for the rework or corrective action that may be required to resolve the use or inclusion of counterfeit materials and parts. The cost of counterfeit electronic parts and suspect counterfeit electronic parts and the cost of rework or corrective action that may be required to remedy the use or inclusion of such parts are not allowable costs under Department contracts , unless: a) the contractor has established a counterfeit avoidance/detection system approved by the DoD, b) the counterfeit parts were procured from a DoD-accredited trusted supplier or provided as government property, and c) the contractor has provide timely notification to the government.

(Ref. AS5553, paragraph 4.1.6, appendix F)

4.6.2.8 Counterfeit Notification and Reporting. The contractor shall report in writing to the Procuring Activity within 30 days of determining any end item, component, part, or material contained in supplies purchased by the Department of Defense, or purchased by a contractor or subcontractor for delivery to, or on behalf of, the Department, contains counterfeit electronic

PR: FD2060-16-00613 PWS REVISION: 0 11

parts or suspect counterfeit electronic parts for the purpose of investigation and notification of the Air Force Office of Special Investigations (AFOSI). The PCO shall coordinate reporting to the appropriate Program Management/Item Management, System Engineering Management, the AFMC Discrepant Materiel Reporting Program (DMRP) Office in 406 SCMS/GULAB, and the AFOSI. Additionally, the contractor shall within the same 30 day period ensure all suspected or confirmed counterfeit items are entered into the Government-Industry Data Exchange Program (GIDEP) system, which will serve as the DoD central reporting repository. (Ref. AS5553, paragraph 4.1.7, appendix G)

4.6.2.9 Counterfeit Prevention Training. The contractor shall provide appropriate training and shall require all personnel working procurement within their company, to include at a minimum their supply chain management specialists, receiving inspectors, and engineers, to complete said training. The contractor shall determine the appropriate training required. Training may be developed in-house or may be other Industry accepted training. The CPP shall describe and list the training provided by the contractor to their personnel.

4.7 Government-Industry Data Exchange Program (GIDEP): The contractor shall participate in GIDEP IAW Air Force Joint Instruction (AFJI) 63-108, Government-Industry Data Exchange Program (GIDEP), and GIDEP Operations Manual S0300-BT-PRO-010, Government-Industry Data Exchange Program.

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis: The Functional Commander (FC) or civilian equivalent has determined these services are not mission-essential and services will not continue in the event of a crisis.

5.2 Security Requirements

5.2.1 Actual knowledge and/or generation of classified information and/or Controlled Unclassified Information (CUI) are not expected to be necessary for performance of the contract/order. However, Contractor personnel are required to comply with security requirements to preclude potential security incidents or violations.

5.2.2 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility security requirements are met. The Contractor shall comply with security regulations including, but not limited to, Department of Defense (DoD) 5200.2-R, Personnel Security Program; DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM); DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program;

DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual; and Robins Air Force Base Integrated Defense Plan (RAFB IDP) 31-101.

5.2.3 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The contractor shall ensure compliance with DoDD 5205.02E and DoD Manual 5205.02-M to protect U.S.

Government interests.

PR: FD2060-16-00613 PWS REVISION: 0 12

5.2.4 Security Clearance

5.2.5 Security Clearance: It is not expected contractor personnel will require security clearances for proper accomplishment of contract/order requirements. Contractor personnel shall not be authorized access to classified information and/or CUI and classified items or be permitted to work on classified projects and/or programs without a valid security clearance and a need-to-know. If security clearances become necessary after contract/order award, the contractor shall ensure applicable contractor personnel obtain valid security clearances appropriate to the access required for proper accomplishment of contract/order requirements.

5.2.6 Security Incident or Violation: The contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.

5.2.7 Security of Contractor System(s): The contractor shall ensure the security of Automated Information System(s) (AIS) at the contractor’s facility to preclude potential security incidents or violations.

5.2.8 Access to Government Facility or Military Installation: Access to a Government Facility or Military Installation is not expected for the performance of this contract. The contractor shall ensure contractor personnel who require access to a Government facility comply with the security requirements of the facility.

5.2.9 Government System

5.2.10 Access to Government System(s): The need for a CAC is not expected for the performance of this contract. The Government will provide contractor personnel access to system(s) necessary to perform tasks under the contract/order. The contractor shall ensure contractor personnel who require access to an unclassified or classified Government AIS have the appropriate background check or security investigation conducted. The Government will provide system access subject to approval of the DD Form 2875, System Authorization Access Request (SAAR). Upon completion/termination of the contract/order or transfer/termination of contractor personnel, the system account(s) will be closed.

5.3 Environmental Management System (EMS): These services are expected to be performed only at the contractor’s facility; therefore, the EMS requirement does not apply to this effort, but this statement does not exempt the contractor from any other Federal, State or local statute or requirement.

5.4. Affirmative Procurement Programs (APP):

IAW FAR 23.404(b)(1), 100% of purchases of Environmental Protection Agency (EPA)-designated products included in the Comprehensive Procurement Guidelines (CPG) list [http://www.epa.gov/cpg/products.htm] and/or United States Department of Agriculture (USDA)-designated products included in the bio based product listings [http://www.biopreferred.gov] shall, at a minimum, meet the EPA or USDA standards for

PR: FD2060-16-00613 PWS REVISION: 0 13

recovered materials or bio based content, respectively, unless an item cannot be acquired competitively within a realistic timeframe, meet appropriate performance standards, and/or be acquired at a reasonable price.

IAW FAR 23.404(a)(iii), the Contractor shall provide estimates and verification of recovered material for EPA-designated CPG products and certification for both EPA-designated CPG products and USDA-designated bio based products. IAW the Robins Air Force Base, Georgia / Green Procurement Program (GPP) Plan, the Contractor shall provide estimates and certifications to the Government for completion of the applicable attachment(s) to be included in the Purchase Request (PR) package.

5.5 Safety Requirements:

5.5.1 Contractor Compliance: While performing work under this contract the contractor shall comply with all applicable federal, state and local regulations regarding occupational safety and health. IAW AFI 91-204, Safety Investigations and Reports, the contractor shall report mishaps involving damage or injury to the USAF. The contractor shall make required notification of all mishaps, and if requested by the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by the Procuring Safety Office.

5.5.2 Mishap Notification/Investigation: IAW AFI 91-204, Safety Investigations and Reports, the contractor shall report mishaps involving damage or injury to USAF interests. The contractor shall ensure the USAF is notified of mishaps. The contractor shall contact the Contracting Officer’s Representative (COR), if available, or another MFT member by telephone within 8 business hours and the contractor shall cooperate with USAF safety investigations.

5.5.3 Safety and Health Plan: The contractor shall submit a Safety and Health Plan to the PCO prior to contract (basic or order, as applicable) award. IAW Air Force Pamphlet (AFPAM) 91- 210, Contract Safety, paragraph 6.4, the Safety Office will review the plan to determine if safety requirements are correctly addressed. The contractor shall establish and maintain a safety program IAW OSHA, ESOH, the contract/order Appendix C (Industrial Safety Requirements), and the Safety and Health Plan.

5.5.3.1 If, during the performance of the contract/order, revision to the contractor’s Safety and Health Plan become necessary, the contractor shall inform the PCO. The same process of review and negotiation, if applicable, involved in the original submission will apply to any revision submitted after contract/order award.

5.5.3.2 The prime contractor shall ensure subcontractors comply with the safety requirements.

5.6 Contract Manpower Reporting

5.6.1 IAW the Contractor Manpower Reporting / Contractor Quick Reference Guide, the Contractor shall establish a record for the contract/order in the Enterprise-wide Contractor Manpower Reporting Application (eCMRA) no later than 30 calendar days after contract/order

PR: FD2060-16-00613 PWS REVISION: 0 14

award. IAW the Contractor Manpower Reporting / Contractor User Guide, the Contractor shall enter Order Data, Contact Data and Location Data.

5.6.2 IAW the Secretary of the Air Force for Acquisition (SAF/AQ) Memorandum, Implementation of FY11 National Defense Authorization Act (NDAA) Section 8108 of Public Law 112-10 of the Department of Defense and Full-Year Continuing Appropriations Act, 2011, Contractor Inventory, dated Nov 13 2012, the Contractor shall provide an annual count of Contractor/subcontractor personnel performing work if the DoD is the requiring activity, if the acquisition is using U.S. Government appropriated funds, and if the acquisition is equal to or greater than the Simplified Acquisition Threshold (SAT).

5.6.3 IAW the Office of the Secretary of Defense (OSD) Memorandum, Enterprise-wide Contractor Manpower Reporting Application, dated Nov 28, 2012, the Contractor shall report all Contractor labor hours, including subcontractor labor hours, required for performance of the services provided under the contract at the eCMRA site below. Reporting shall be conducted for each fiscal year, which extends October 1 through September 30. While inputs may be made any time during the fiscal year, all data shall be reported no later than October 31 of the following fiscal year. The Contractor may direct questions to the help desk at the eCMRA site.

http://www.ecmra.mil

5.8 Inspection of Services: Inspection of Services will be accomplished in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The Government reserves the right to inspect Contractor performance.

5.9 Invoicing/Payment and Receipt/Acceptance:

5.9.1 The Contractor shall submit/process payment requests and receipt/acceptance documents via Wide Area Workflow e-Business Suite / Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) IAW all applicable clauses located in the basic contract.

5.9.2 CDRL deliverables may be submitted using WAWF or be submitted directly to the applicable MFT member IAW the CDRL. The CDRL will determine submittal requirements;

however, separately priced data must be accepted in WAWF in order for the contractor to receive payment, and both separately priced and non-separately priced data must be accepted in WAWF in order for the contract line item to be closed out.

5.9.3 Services will be accepted by the DCMA QAR.

PR: FD2060-16-00613 PWS REVISION: 0 15

6.0 Appendices

6.1 Appendix A: References

Publication Title of Publication

Date of Publication Section(s) that Apply

AFI 91-204 Safety Investigations and Reports

9 August 2012 reissued 8 April 2013 http://www.e-publishing.af.mil/

Paragraphs 1.3.1.1, 2.4.6.1.1- 2.4.6.1.2

None Defense Contingency COR Handbook

Version 2 September 2012 http://www.acq.osd.mil/dpap/ccap/cc/corh b/Files/DCCOR_Handbook_2012.pdf

Section on Combating Trafficking in Persons in Chapter 8, Monitoring the Contractor

DoD 5200.2-R Personnel Security Program

1/1/87 Change 1 - 2/12/1990 Change 2 - 7/14/1993 Change 3 - 2/23/1996 http://www.dtic.mil/whs/directives/corres/ pub1.html

Entire

DoDD 5205.02E DoD Operations Security

(OPSEC)

Program

June 20, 2012

DoD Manual 5205.02-M

DoD Operations Security

(OPSEC)

Program Manual

November 3, 2008

FAR and supplements

Federal Acquisition Regulation http://farsite.hill.af.mil

Sections applicable to contract and

PR: FD2060-16-00613 PWS REVISION: 0 16

PWS

OSD

Memorandum

Enterprise-wide Contractor Manpower Reporting Application

Nov 28 2012 http://www.acq.osd.mil/dpap/policy/polic yvault/Enterprise-wide_Contractor_Manpower_Reporting_ Application_memorandum.pdf

SAF/AQ

Memorandum

Implementation of FY11 NDAA Section 8108, Contractor Inventory

Nov 13 2012 https://cs.eis.af.mil/airforcecontracting/kn owledge_center/Documents/AFFARS_Li brary/5337/2012-11-13_saf-aq-memo.pdf

USD

Memorandum

Establishment of the DoD Green Procurement Program

August 27 2004 http://www.wbdg.org/pdfs/dod_gpp_0827 04.pdf

AFJI 63-108 Government- Industry Data Exchange

(GIDEP)

15 May 1980 http://www.e-publishing.af.mil/

AS5553A

Fraudulent /Counterfeit Electronics Parts;

Avoidance, Detection, Mitigation, and Disposition

Revision A 2013-01-21 none Department of Defense Guide to Uniquely Identifying Items Assuring Valuation, Accountability and Control of Government Property, Version 2.5

September 15, 2012 www.acq.osd.mil/dpap/UID/attachments/ DoDUIDGuideVer2_5.pdf

PR: FD2060-16-00613 PWS REVISION: 0 17

DoD 5220.22-M

National Industrial Security Program Operating Manual

(NISPOM)

February 28, 2006 Change 1 - March 28, 2013

GIDEP

Operations Manual S0300-

BT-PRO-010

Government- Industry Data Exchange

September 2009 http://www.gidep.org/

Chapter 2, Participatio n Requiremen ts

MIL-STD-129P Department of Defense / Standard Practice / Military Marking for Shipment and Storage

15 December 2002 Change 1 - 15 January 2004, Change 2 - 10 February 2004, Change 3 - 29 October 2004, Change 4 - 19 September 2007 http://www.acq.osd.mil/log/sci/ait/MIL- STD-129PCH4.pdf

MIL-STD-130N Department of Defense / Standard Practice / Identification Marking of U.S.

Military Property

17 December 2007 Change 1 – 16 November 2012 http://www.acq.osd.mil/dpap/pdi/uid/docs /MIL-Std130N_Ch1.pdf

MIL-STD-2073-

1E

Department of Defense / Standard Practice for Military Packaging

23 May 2008, Chg 1, Jan 2011

MIL-STD-

1686C

Department of Defense Standard Practice / Electrostatic Discharge Control Program for Protection of

25 Oct 1995

PR: FD2060-16-00613 PWS REVISION: 0 18

Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices)

RAFB IDP

31-101

Robins Integrated Defense Plan

January 2012 Entire

AFPAM 91-210 Contract Safety 14 Feb 14 Paragraph 6.4

MIL-HDBK-

263B

Electrostatic Discharge (ESD) Control Handbook for Protection of Electrical and Electronic Parts, Assemblies, and Equipment (Excluding Electrically Initiated Explosive Devices) (31 Jul 1994)

31 July 94 Entire

File details come from the government source that posted it. Updated .