PWS.docx

Performance-Based Work Statement (PWS)

Purchase Request: FD2060-15-01128

Redesign of the, Radar Control Test Panel.

applicable to the APQ-166

Date: 23 Oct 15

1.0 Description of Services

1.1 Objective(s): This PWS is for redesign of National Stock Number 5998-01-228-9360, Numeric Display part of the Radar Control Test Panel which are all applicable to the APQ-166 on B-52H aircraft. The purpose of this effort is to provide for a Form Fit Function replacement of the Printed Wiring Assembly Numeric Display. This effort will also sustain maintainability by replacing obsolete components. The Contractor shall deliver a Form Fit Function replacement within 18 months ARO. Ultimately, repair cost reductions will be realized, mission capability will be increased in the battlefield, and war fighter support enhanced. All CAV-AF transactions shall be promptly and correctly maintained.

1.3 Background: The APQ-166 Radar Control Test Panel intermittently displays crucial radar control setting information. The displayed data are crucial to properly orienting the radar for maximum operational capability. Since the data are not displayed properly, the radar settings are incorrect which compromises radar performance.

2.0 Services Summary:

- GFM In-Transit

- Repairable GFM Accountability

- Assets Not on Contract

3.0 Government Property and Services:

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in their possession in accordance with the Federal Acquisition Regulation (FAR) and applicable supplements. The FAR and applicable supplements can be accessed at http://farsite.hill.af.mil.

3.2 Government Property to be provided: Government property (including material, equipment, etc.) to be provided. Reference the contract Appendix B, Government-Furnished Property.

3.3 Loss of Government Property

3.3.1 Definition of Loss of Government Property: In accordance with DFARS 252.245-7002, Reporting Loss of Government Property, “loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, theft, loss due to lack of security, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.3.2 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. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the http://www.dcma.mil/aboutetools.cfm

3.4 Return 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. All Government property shall be returned to the Government in the condition provided unless approved in advance by the Procuring Contracting Officer (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, Contract Data Requirements List (CDRL), deliverables become the property of the Government upon receipt.

3.5 Government System(s): The Government will provide Contractor personnel access to system(s) only as 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: Contractor shall redesign, fabricate prototype and update data for the Form/Fit/Function replacement of the 5998-01-228-9360, Numeric Display part of the Radar Control Test Panel (Part Number 377-11029-601) In Accordance With (IAW) this PWS and drawing 380-10376 Hexadecimal with Logic Display documents listed in Appendix A. In the event of conflict between data indentified in the PWS and Drawing 380-10376, Drawing 380-10376 shall govern.

4.1 Period and Place of Performance:

4.1.1 Contract/Order Period of Performance: The Contractor shall deliver an acceptable prototype within 18 months After Receipt of Order (ARO).

4.1.2 Place of Performance: These services shall be performed at the contractors facility.

4.2.1 Engineering Evaluation: The Contractor shall evaluate all analysis data including obsolete components to determine the improvements that may be needed. The evaluation may include but is not limited to: parts obsolescence replacement.

4.2.2 Obsolescence Correction, Reliability and Prototype: The contractor shall redesign, fabricate a prototype and update data for the Form/Fit/Function replacement of the 5998-01-228-9360, Numeric Display part of the Radar Control Test Panel (Part Number 377-11029-601) to eliminate obsolescence problems. This contract shall also improve reliability and maintainability by 20% for Numeric Display part of the Radar Control Test Panel (Part Number 377-11029-601) affecting the overall performance of the APQ-166. Any modified modules will be interoperable with all APQ-166 sets, in all modes of operation, in accordance with the requirements of the APQ-166 System Segment Specification. All modified SRUs shall be form, fit, and function equivalent to the existing assemblies. The Contractor shall submit a prototype with all changes documented. Successful FCA/PCA shall be held in accordance with MIL-HDBK-61A, after which the production baseline shall be considered established.After baseline approval, Engineering Change Proposals (ECP) will be required for any design changes. These prototypes shall be shipped to the government within 60 calendar days following completion of the effort. (CDRLA002, DI-CMAN-80639C, ECP if applicable)

4.2.3 Parts Control: The Contractor shall establish a parts control and standardization program using internal policies. Commercial Off-the-Shelf (COTS) materiel may be used to help reduce cost and risk; however, government approval is required before implementation. The contractor shall use MIL-HDBK-965 as a guide.

4.3 Human Factors/Performance:

The incorporation of any new Radar Control Test Panel components or CCAs/SRUs to correct obsolescence shall permit satisfactory operation and maintenance with minimal demands on personnel skill requirements. Any unique or extensive requirements shall be identified and reported as early as possible. Human engineering and obsolescence correction criteria and principles shall be applied.

4.4 Qualification:

Qualification by similarity shall be used unless an entirely new board design is required. If Qualification is required, the contractor shall conduct a test and evaluation program to verify the performance of all redesigned circuit cards/components. The design shall meet or exceed the current subcomponent’s Hexadecimal with Logic Display, requirements, performance, and test found in Drawing 380-10376. Drawing 380-10376 established the performance, design, development, test requirements and lists applicable documents. The test program philosophy shall be to plan, evaluate, test, document, and verify the functional performance and interface characteristics of the Radar Control Test Panel over the originally specified environmental variations to ensure the redesigned components, when integrated into the APQ-166, supports the mission requirements for which the B-52 aircraft system was intended.

4.4.1 The magnitude and duration of the Qualification tests shall be determined according to the extent of the redesign effort. Environmental tests shall be conducted in accordance with the test requirements of the APQ-166 specification; testing where required shall be limited to temperature, altitude, explosive atmosphere, random vibration, and acceleration (ultimate loads) testing. EMI testing shall be done by analysis were applicable, shall utilize all or portions of the original demonstration test procedure and be performed in accordance with 1994 SPS WG-1 TR-91-001 Rev A Guidelines.

4.4.1.1 If required, Environmental Qualification Testing shall be performed to validate the updated Radar Control Test Panel hardware. All other items internal to the APQ-166 are not changed by this effort and are already qualified. Any failures that may occur to these items during testing shall not constitute an Environmental Qualification Test failure of the APQ-166. Any failures that may occur to these items during testing shall be repaired and testing shall resume from where the failure was detected.

4.4.1.2 APQ-166 EMI Qualification Testing shall be performed to validate the updated Radar Control Test Panel hardware. All other items internal to the APQ-166 are not changed by this effort and are already qualified. Any outages that may be present in the "as received" configuration of the GFE unit shall not constitute an EMI Qualification Test failure of the APQ-166 when configured with the updated Radar Control Test Panel hardware. Any outages that may be present in the "as received" configuration shall be identified and the pass /fail criteria shall be taken into consideration.

4.5 Test Procedures

If necessary, test procedures may be modified before or during the performance of the test to improve the accuracy of the test results or to correct errors in setups and instructions. A master redline of the appropriate test procedure shall be maintained in accordance with standard configuration management procedures throughout the testing and shall be used to note any deviations from the original test methods. Reference Drawing 380-10376. A draft test plan shall be provided in accordance with contract requirements. A final test plan shall be available by the Test Readiness Review. (CDRL A003,DI-NDTI-80566A, Test Plan)

4.6 Data sheets/Test Report

Each deliverable test procedure shall contain data sheets for recording the system performance and examination data obtained while conducting the applicable tests and inspections. Reference Drawing 380-10376. Data sheets completed during testing of deliverable items shall be retained at the contractor's facility. Data recorded during any required testing shall be reviewed and analyzed. All test data and the analysis results shall be issued to 407 SMCS/GUEAC no later than 45 working days after completion of the testing. Any required qualification test reports will be issued to 407 SCMS/GUEAC no later than 60 calendar days after completion of testing. (CDRL A004, DI-NDTI-80809B, Test/Inspection Report)

4.7 Quality Control and Assurance

The contractor shall use existing internal Quality Control tools and processes in monitoring the Radar Control Test Panel redesign effort. All testing shall be in accordance with approved procedures and internal policies. Quality Plan shall be provided to the Quality Assurance Personnel. The contractor shall use existing quality program tools and metrics IAW IS0-9001 and IS0-10012-2 to ensure components are manufactured in accordance with commercial standard as applicable and meet all the requirements for operational performance. Quality assurance will ensure the standards of workmanship and acceptance testing are maintained. Reference Drawing 380-10376.

4.8 Testing

Testing shall be limited to functional performance testing and standard Environmental Stress Screening (ESS) as performed in the production environment. Tests shall be conducted in accordance with the test requirements of the APQ-166 specification. Reference Drawing 380-10376.

4.9 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), reference attached DD Form 1423 Block 16. [CDRL A005, Product Drawing/Models and Associated Lists] DI-SESS-81000E/T.

4.9.1 Engineering Data Guidance Conference: The contractor shall support and cochair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 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. The contractor shall address, discuss, and provide status on the following: (CDRL A008, DI-ADMN 81249A,ConferenceAgenda)(CDRL A009, Dl-ADMN-81505, Conference Minutes)

a. Understanding of all CDRL requirements, applicable DIDs, specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. Contractor's drafting practices/procedures/TDP drawing formats/CAD programs.

e. The contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f. The role of subcontractors and vendors who may deliver TDP documents under this contract.

g. The contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

h. Digital Technical Data Package (TDP) deliverables.

Note: Guidance Conference may be held in conjunction with other meetings or conferences.

4.9.2 In-Process Review (IPR) of the TDP: 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 reviews (i.e., PDR, CDR). The contractor shall notify AFLCMC/LZPEM a minimum of 30 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 Government may schedule a separate IPR at the subcontractor's/vendor's facility.

(CDRL A008, DI-ADMN 81249A,ConferenceAgenda)(CDRL A009, Dl-ADMN-81505, Conference Minutes)

4.9.3 Relationship of Contractor with Subcontractors/Vendors: The contractor shall levy on sub-contractors and sub-vendors the same requirements for Technical Data Packages (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.9.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/modified/produced and funded by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a. All engineering changes shall be incorporated into the applicable engineering data within 90 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.

b. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media.

d. 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. For example, when a portion of a document is revised the entire document shall be delivered.

4.10 Technical Order (TO) Updates

If applicable, the Contractor shall notify the government of any required TO updates in accordance with TM-86-01N.

4.11 Program Management

The Contractor shall provide internal management and control on all matters related to this PWS, from conception to final completion. A Program Manager (PM) shall be designated to serve as Contractor's focal point for the Government and will ensure successful fulfillment of all PWS requirements within the agreed upon schedule. The Contractor PM shall report program status quarterly in accordance with contract requirements. The report shall include milestone/task status, future plans, contract delivery status, and report preparer as defined in Dl-MGMT-80368A. (CDRL A006, DI-MGMT-80368A, Project Status Reports)

4.12 Plans and Schedules

The contractor shall prepare and maintain a Management Plan that describes how the contractor shall accomplish the tasks within this PWS and reflects key milestones. Only one schedule slippage per quarter allowed and all slippages shall be completed within five business days. This mutually agreed upon Management Plan will become the program schedule baseline. Program Management Plan shall be coordinated with the Government PM for approval.

(CDRL A007, DI-MGMT-80004A, Management Plan)

4.13 Meetings, Reviews,and Audits

The Contractor shall attend all meetings, reviews, and audits unless otherwise mutually agreed to by the Contractor and Government. The Contractor shall prepare, coordinate, distribute agenda, and minutes with the Government at the applicable times. (CDRL A008, DI-ADMN-81249A, Conference Agenda) (CDRL A009, DI-ADMIN 81505, Conference Minutes.

4.14 Design Reviews

The Contractor shall host and conduct the following design reviews to assess the degree of completion of technical efforts:

· The Preliminary Design Review (PDR) shall be scheduled as mutually agreed to by the Contractor and Government PMs. The PDR will be held at approximately the 30% design point as measured by the Program Management Plan (PMP).

· The Critical Design Review (CDR) shall be scheduled as mutually agreed to by the Contractor and the Government PMs. The CDR will be held at approximately the 75% design point as measured by the PMP.

· The PDR/CDR will be held at the 30%/75% design point as measured by the PMP. The performance is acceptable when contractor has adequately demonstrated the following:

· The detaildesign satisfies the performance and requirements of the specs.

· Established detail design compatibility among the APQ-166 interface and any other interfacing items of equipment and software.

· Assessed risk analysis of design configuration control.

· Assessed results of the production analyses conducted on hardware.

(CDRL A008, DI-ADMN 81249A,ConferenceAgenda)(CDRL A009, Dl-ADMN-81505, Conference Minutes)

4.15 Test Readiness Review (TRR)

The Contractor shall conduct a TRR IAW the PMP to assess the program maturity and preparation for testing. The Contractor shall be prepared to discuss the following at a minimum: requirements specification changes, design changes, test procedures and limitations, and documentation updates. (CDRL A003, DI-NDTl-80566A, Test Plan) (CDRL A008, DI-ADMN-81249A,Conference Agenda) (CDRL A009, Dl-ADMN-81505, Conference Minutes)

4.16 Audits

The contractor shall conduct a Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA) IAW the PMP for each prototype. The PCA shall provide opportunity to visually inspect and compare the prototypes to analysis documentation. The FCA shall provide opportunity to functionally check the prototypes for operational integrity. The contractor shall demonstrate that the actual performance of the redesigned CCAs meets specification requirements. Configuration documentation adequately reflects the exact design of the redesigned CCAs hardware. Any elements that were redesigned after completion of FCA must also meet specification requirements. Action items have been completed within the designated suspense date and contractor has submitted adequate evidence of completion. The contractor shall provide data to support each PCNFCA, using MIL-HDBK-61A as guidance for PCNFCA. FCA and PCA approval shall not constitute approval of the TDP.

4.17 PACKAGING

4.17.1 The Contractor shall package and mark material in accordance with the contract (basic and/or order, as applicable) in accordance with the attached Air Force Materiel Command (AFMC) Form 158, Packaging Requirements. The Contractor shall package and mark material in accordance with other applicable Government regulations including, but not limited to, those regarding security, safety and environmental concerns including MIL-STD-129P Department of Defense / Standard Practice / Military Marking for Shipment and Storage; MIL-STD-130N Department of Defense / Standard Practice / Identification Marking of U.S. Military Property.

4.17.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 in accordance with 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.17.3 In accordance with 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.18 Commercial Asset Visibility-Air Force (CAV-AF): The Contractor shall report production using CAV-AF. The Contractor shall provide data on the actions conducted for each unit. The Contractor shall report daily or as actions occur. If CAV-AF training is required, Contractor personnel may send an email to: 406scms.cav.af.ar@robins.af.mil. (CDRL A001, DI-MGMT-81634C, Commercial Asset Visibility Air Force (CAVAF)/Government Furnished Material Report)

4.19 The Contractor shall provide a Safety Assessment Report (SAR) 14 days prior to PDR. The report shall be acceptable in contractor format and is acceptable on electronic media (CD/DVD). The data shall be delivered electronically in Rich Text Format, and/or other Government approved word processing format. The SAR is a comprehensive evaluation of the safety risks being assumed prior to test or operation of the system or at contract completion. It identifies all safety features of the system, design and procedural hazards that may be present in the system being acquired, and specific procedural controls and precautions that should be followed. Reference DI-SAFT-80102B for subject matter to be included in the SAR. (CDRL A010, DI-SAFT-80102B, Safety Assessment Report)

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. Contractor personnel are required to comply with security requirements to preclude potential security incidents or violations. If a change in the security classification of the contract/order becomes necessary after contract/order award, the Contractor shall make a reasonable effort to continue performance of tasks under the contract/order in compliance with the change in security classification in accordance with Security Requirements.

5.2.2 Security Regulations: The Contractor shall ensure personnel, information, systems, property, facility and security requirements are met. The Contractor shall comply with all applicable security regulations and clauses listed in the contract and in accordance with DoD 5200.2-R Personnel Security Program.

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, DoD Directive for Operations Security (OPSEC) and DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual to protect United States (U.S.) Government interests.

5.2.3 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.4 Security Incident or Violation: The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation including potential or actual unauthorized disclosure or compromise of classified information and/or CUI.

5.2.5 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 including potential unauthorized disclosure or compromise of classified information and/or CUI.

5.2.6 Access to Government System(s): 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): Services will be performed at the contractor’s facility; therefore, the local EMS requirements do not apply to this effort. This statement does not exempt the Contractor from any other Federal, State or local statute or requirement.

5.4 Green Procurement Program (GPP): Under Secretary of Defense (USD) Memorandum, Establishment of the DoD Green Procurement Program, dated August 27 2004, establishes the requirement for a GPP. Green procurement is the purchase of environmentally preferable products and services and shall be managed in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

5.5 Safety Requirements: While performing work under this contract the Contractor shall comply with all applicable federal, state and local regulations regarding occupational safety and health. In accordance with 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.1 In accordance with AFI 91-204, paragraph 2.4.6.1.1, the Contractor shall ensure the USAF Safety Office and the applicable contract management authority are notified of mishaps. The Contractor shall contact the Multi-Function Team (MFT) [Contracting Officer’s Representative (COR), if available, or another MFT member] by telephone within eight business hours. The MFT will notify the Safety Office and the PCO.

5.5.2 In accordance with AFI 91-204, paragraph 2.4.6.1.2, the Contractor shall cooperate with USAF safety investigations.

5.6 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.7 Trafficking in Persons: The Contractor shall comply in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons. Additional information about Trafficking in Persons is available at the site for the Department of State’s Office to Monitor and Combat Trafficking in Persons. http://www.state.gov/j/tip

5.8 Contractor Manpower Reporting:

5.8.1 In accordance with 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.8.2 In accordance with 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 Enterprise-wide Contractor Manpower Reporting Application (eCMRA) site below. Reporting shall be conducted for each fiscal year (FY), which extends October 1 through September 30. While inputs may be made any time during the FY, all data shall be reported no later than October 31 of the following FY. The Contractor may direct questions to the help desk at the eCMRA site. http://www.ecmra.mil

5.9 Invoicing/Payment and Receipt/Acceptance: 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) in accordance with all applicable clauses located in the basic contract.

6.0 Appendix: References

Entire

Entire

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

Entire

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

http://www.dtic.mil/whs/directives/corres/pub1.html Entire

http://www.dtic.mil/whs/directives/corres/pub1.html Entire

Sections applicable to contract and PWS

28 November 2012 http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf Entire

https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5337/2012-11-13_saf-aq-memo.pdf Entire

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 Entire

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

MIL-STD-2073-1E

Notice 1, 10 May 2002

Entire

Entire

PR: FD2060-15-01128 PWS 1