SOF Tech Data- PWS.docx

AIR FORCE LIFE CYCLE MANAGEMENT CENTER ROBINS AIR FORCE BASE, GEORGIA 31098-1670 PERFORMANCE-BASED WORK STATEMENT (PWS) FOR (PSP) Technical Documentation Project (TDP) FD2060-23-30010 30 May 2023

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their Contractors (Administrative or Operational Use) (14-06-11). Other requests for this document shall be referred to AFLCMC/WIUAA, Robins AFB, GA 31098-1670.

PR: FD2060-23-30010 PWS REVISION: 0

Distribution Statement: C

TABLE OF CONTENTS

2.0 SERVICES SUMMARY (SS) 4

3.0 GOVERNMENT PROPERTY AND SERVICES 5

4.0 TECHNICAL REQUIREMENTS 6

1.0 Description of Services

1.1 Objective(s): This Performance-based Work Statement (PWS) defines the professional engineering and technical services the Contractor shall provide in support of the AC-130 Precision Strike Package (PSP) Technical Documentation Project (TDP).

These services include:

· The Contractor shall provide necessary engineering services and technical writing support to be incorporated into subsequent Technical Orders (TO) development and drawings.

· In accordance with Appendix A, the Contractor shall provide Configuration Management (CM) by implementing the policies, procedures, techniques and tools that are required to manage, evaluate proposed changes, track changes and to update the PSP drawings, TOs and Time Compliance Technical Orders (TCTO) per the Technical Manual Contract Requirements (TMCR).

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by providing safe, accurate and effective PSP technical orders to support sustainment of the AC-130 and applicable PSP components, support equipment and modifications. This effort will provide timely, verified technical orders to the field, improved capability to the war-fighter and reduce demand on the existing Low Density/High Demand Gunship fleet as well as reducing Contractor Logistics Support (CLS) costs.

1.3 Background: This project was proceeded by a unique fast track Special Operations Forces (SOF) Capabilities Integration and Development Systems process. This process was utilized to provide a close air support PSP integrated on selected C-130 aircraft platforms. The PSP is a collection of sub-systems installed on select C-130 aircraft to support the primary mission to provide close air support, armed reconnaissance, force protection, integrated base defense, strike control and reconnaissance, air interdiction, and convoy escort to troops in contact. This project is part of an effort to continue the Air Force Special Operations Command (AFSOC) and United States Special Operations Command (USSOCOM) evolution and modernization of mission and to carry operations into the future. This effort will enable the USAF to provide increased support to modern Gunship capabilities, and support up to forty six AC-130 aircraft. The PSP is a self- contained ground attack platform with the ability to find, fix, track, target, engage and access in minimum time with deadly accuracy while minimizing collateral damage. The PSP incorporates a Ground Positioning Systems Mission Operator Pallet (GMOP), a Gun Weapon System (GWS) consisting of the medium caliber gun with trainable gun mount, multiple Stand-Off Precision Guided Munitions (SOPGM), internal crew member and external communications and Beyond Line of Sight (BLOS) data links, Line of Sight (LOS) data links and multiple Electrical Optical/Infrared sensors onto an existing MC-130J donor aircraft, creating an AC-130J. Additional provisions will consist of connections to operate carry-on equipment through established aircraft avionics and communication systems. The GMOP hosts the battle management system and fire control system software to operate all PSP mission equipment. All PSP equipment is managed through the Mission Operator Pallet (MOP)/GMOP to identify, track, and engage targets.

2.0 Services Summary

Reference Performance Threshold

Integrated Master Schedule (IMS): Adhere to all schedule performance parameters as set forth in the IMS

4.6 The draft IMS shall be submitted ten (10) business days prior to the Kick-Off Meeting. The Contractor shall have five (5) business days to resubmit the draft if changes were deemed necessary by the Government. After the Kick-Off Meeting, the IMS shall be updated to show progress and submitted along with the Status Reports. Deviations from the milestones require Government approval. Subtask revisions are due as changes occur. The Contractor shall remain within five (5) business days of schedule parameters set forth in the IMS unless revised. Any revision must be requested in writing and approved by the Government. The Contractor shall be held to the same five (5) day standard described. The Contractor shall not exceed three (3) schedule slippage incidents during the contract period of performance.

Quality of Contract Data Requirement List (CDRL) Deliverable

4.2.1 There shall be no more than one (1) rejection of any deliverable. There shall be no more than three (3) total rejection(s) of deliverables per 12 months. The Government will reject a deliverable if two (2) or more technical errors or three (3) or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within ten (10) business days of notification of Government rejection.

Receipt of CDRL Deliverable Reporting Requirements – Reviews, Meetings and Working Group Participation

4.2.2, 4.5, 4.6 There shall be no more than two (2) late submission(s) of deliverables per quarter. 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.

Contractor Manpower Reporting

5.8 Within 30 calendar days of contract/order award, the Contractor shall establish a record for the contract/order in Enterprise-wide Contractor Manpower Reporting Application (eCMRA) including Order Data, Contact Data and Location Data and submit the annual report no later than October 31 of the following fiscal year.

3.0 Government Furnished Information and Property

3.1 Contractor Responsibility: The Contractor shall be responsible for Government Furnished Information and Property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2 Government Furnished Information (GFI) to be Provided: The GFI to be provided includes applicable Government AC-130W, AC-130J, C-130J, and MC-130J documentation and data, such as engineering data, vendor manuals and existing Technical Manuals, TCTOs, Operational Supplements and Support Equipment TOs, as required to support task execution. This includes data that may not have been delivered in final form from other AC-130 PSP Contractors. The Contractor shall establish (as required) a Proprietary Information Agreement with current PSP Contractor(s) supporting the AC-130W and/or the AC-130J to obtain the most current PSP data required for this activity and should define how required data will be obtained. The Government will provide, as necessary, access to appropriate Government data systems applicable to TO/TCTO development to support task execution. The Government will provide the Contractor with applicable Government documentation and data (source data) on an as available, required or authorized, basis to support contract execution. All GFI required to accomplish this requirement will be provided by the Program Office or geographically separated AC-130 Combat Acquisition Detachments (CAD). This will include approval and submittal of requests for User Identifications (ID) and passwords, approval and use of licensed software, both initial and upgrade training when applicable and any supporting documentation required to access databases necessary to meet contract requirements.

3.2.1 Government Furnished Equipment: The Government will provide access to AC-130 Gunship equipment, necessary government programs and systems as required for technical order development, certification and verification to be performed by the Contractor under this contract. This will be specified as appropriate under each individual order.

3.2.2 Reporting of Government Property: The Contractor shall create and maintain records of all Government property accountable to the contract/order. The Contractor shall record receipt and return of Government-Furnished Property (GFP) in the Item Unique Identification (IUID) Registry.

3.3 Loss of Government Property

3.3.1 Definition of 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, loss due to lack of security, theft, 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 report loss of Government property using Defense Contract Management Agency (DCMA) / Access To eTools.

3.3.3 Return or Retention of GFP: 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, CDRL, deliverables become the property of the Government upon receipt.

3.4 Government System(s): The Government will provide Contractor personnel access to system(s) necessary if required 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

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance: This contract will be a “D” Indefinite Delivery, Indefinite Quantity contract with a minimum order to be specified in the solicitation. The period of performance will be a (4) four year (Basic plus three (3) Option Year).

4.1.2 Place of Performance: These services shall be performed at the Contractor’s facility.

4.1.3 Government-Industry Data Exchange Program Not required

4.2 Contract Data Requirements List(s) (CDRL)

4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable. There shall be no more than three (3) total rejection(s) of deliverables per 12 month award period. The Government will reject a deliverable if two (2) or more technical errors or three (3) or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within ten (10) business days of notification of Government rejection.

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via Wide Area Workflow (WAWF) or Procurement Integrated Enterprise Environment (PIEE) and submitted directly to the Multi-Functional Team (MFT) member identified on the CDRL. There shall be no more than two (2) late submission(s) of deliverables per 12 Months. 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.

4.3 Engineering, Logistics and Technical Support

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

4.3.2 Source Data Configuration Management: The Contractor shall be responsible to implement the policies, procedures, techniques and tools that are required to manage, evaluate proposed changes, track changes and to maintain the technical orders and TCTO per the TMCR. The Contractor shall provide the PSP Program Manager (PM) and (Contracting Officer’s Representative) COR with any discrepancies and shortfalls that require compliance. The data status reports will be maintained in the Monthly Status Review (MSR) until all source data is accepted and TOs are delivered to the Government per the TMCR. All data submissions shall be delivered along with source data and affected TOs. (CDRL A001, DI-MGMT-80368A, Status Report).

4.3.3 Program Management: The Contractor shall employ a program management structure to ensure the efficient execution of all tasks and the capability to report on the status of work performed. The Contractor shall use a single PM to administer all project activities and serve as the principle Point of Contact (POC) for all matters regarding project administration and reporting. To ensure efficient on-site management and administration of this contract, the Contractor shall identify a primary POC and an alternate who shall provide the direct, recurring interface between the Contractor, Quality Assurance (QA) personnel and the applicable directorate staff. The Contractor shall promptly notify the PCO of any issues or problems requiring a Government response. The Contractor shall perform program management necessary to effective and efficiently manage, administer, and control the overall program.

4.3.4 Travel: Contractor personnel may be permitted to travel to other Government installations or to subcontractor facilities to observe and conduct operational checkouts, ensure compatibility or configuration changes, to attend meetings, or in other related capacities. Trips, numbers and types of personnel shall be limited to the minimum required to accomplish work requirements. The Contractor shall be responsible for arranging all Contractor personnel travel during the program effort in accordance with the Department of Defense (DOD) Joint Travel Regulations (JTR). The Contractor shall use the lowest cost mode of transportation commensurate with mission requirements and good traffic management principles. All travel must be approved by the PCO in advance. All travel requests shall include the number of personnel, destination, purpose, number of days, and the cost estimate of required travel. The use of Video Teleconference (VTC)/Telecom is the recommended means for meetings and information exchange. Travel requests for contractor/subcontractor personnel shall be submitted for approval to the PCO prior to costs being incurred and a minimum of 10 business days in advance of departure. Receipts must be presented with the invoice for reimbursement of actual travel costs.

4.3.4.1 Labor: Contractor personnel will be authorized labor while working with government personnel in duties essential to the contract. Labor will be authorized during travel and while on location for verification efforts. All labor estimated must be approved 10 days before travel is scheduled to begin. Contractor No overtime will be authorized on this contract. Technical Order Requirements

4.3.4 Certification/Validation and Verification: The Contractor shall perform Certification/Validation and In Accordance With (IAW) TO 00-5-1, TO 00-5-3 and the TMCR. The Government will perform Verification and will have approval rights for final deliverable technical orders. The Contractor shall attend all verification meetings until the final deliverable TOs are verified. (CDRL A003, DI-TMSS-80607, Technical Order Verification Recommendation (TOVR)).

4.3.5 Time Compliance Technical Order (TCTO): The Contractor shall develop a new TCTO to document the final AC-130 PSP configuration and instructions for removal of the existing systems (if required). The TCTO shall be prepared IAW TO 00-5-15, MIL-PRF-38804C and the applicable Air Force Materiel Command (AFMC) Form 873, Time Compliance Technical Order Requirements. (CDRL A004, TM-86-01, Technical Manual Contract Requirements).

4.3.6 Technical Orders: The Contractor shall develop technical orders as indicated below in accordance with the applicable TMCR. The Contractor shall use documentation identified in Appendix C as well as any additional sources required to complete the task. The Contractor shall provide digital technical data capable of being displayed on and off the aircraft and compatible with standard desktop personal computers. The Government will have unlimited data rights to all technical orders developed and delivered under this contract. (CDRL A004, TM-86-01, Technical Manual Contract Requirements).

4.5 Reviews, Meetings and Working Group Participation: The Contractor shall prepare for and participate in reviews, meetings and working group meetings which may be required to support activities for the PSP TDP, as detailed below. The Contractor shall not have more than two (2) late CDRL delivery dates for the twelve (12) month period of performance. The CDRLs and related documents will have no more than three (3) errors. (CDRL A002, DI-MGMT- 81250B, Conference Minutes), (CDRL A007, DI-MGMT-81250A, Conference Agenda).

4.5.1 Logistics Meetings: The Contractor shall provide local support to logistics meetings at a mutually agreed upon location. Such meetings include technical order reviews, Integrated Product Team (IPT) meetings Integrated Product Review (IPR), technical interchange meetings. . (CDRL A002, DI-MGMT- 81250B, Conference Minutes), (CDRL A007, DI-MGMT-81250A, Conference Agenda).

4.5.2 Kick-Off Meeting: The Contractor shall plan and conduct a Kick-Off Meeting at the Contractor’s facility within 45 business days of contract award to include participation from PCO, Government PM, USSOCOM/AFSOC to discuss program status. (CDRL A002, DI-MGMT- 81250B, Conference Minutes), (CDRL A007, DI-MGMT-81250A, Conference Agenda).

4.6 Reporting Requirements: The Contractor management organization shall report to the Government the technical, support and cost aspects of the AC-130 PSP TDP activities throughout the performance of the contract. Without exception, when a report format is specified, all data elements called out in the format shall be captured in the Government or Contractor allowed report format. All data to be delivered from this PWS shall be in accordance with the corresponding CDRL. The Contractor shall not have more than two (2) late CDRL delivery dates for the twelve (12) month contract period of performance. The CDRLs and related documents will have no more than three (3) errors.

4.6.1 Monthly Status Report (MSR): The Contractor shall provide a MSR, which may include items such as, accomplishments, innovations, challenges, problems, special interest items, or issues with limitation of subcontracting requirements, Organizational Conflict of Interest, manpower, recruiting, security, or quality assurance at the contract or TO level or any discrepancies or shortfalls in source data. Provide monthly reports for the purpose of maintaining a clear understanding of current program status. (CDRL A001, DI-MGMT-80368A, Status Report).

4.6.2 Program Management Review Agenda: The Contractor shall prepare an agenda and present a Quarterly Program Management Review (PMR) that provides a brief description of the tasks, current status, expenditures to date, manpower information, total TO value, accomplishments, innovations, performance initiatives, problems/issues, if any, affecting performance and final minutes of the meeting. (CDRL A002, DI-MGMT- 81250B, Conference Minutes), (CDRL A007, DI-MGMT-81250A, Conference Agenda).

4.6.3 Integrated Master Schedule (IMS): The Contractor shall develop an IMS containing the networked, detailed tasks necessary to ensure successful program execution. The IMS shall be used to verify attainability of contract objectives, to evaluate progress toward meeting program objectives and to integrate the program schedule activities with all related components. The draft IMS shall be submitted ten (10) business days prior to the Kick-Off Meeting. The Government will have five (5) business days to approve or disapprove the draft IMS. The Contractor shall have five (5) business days to resubmit the draft if changes were deemed necessary by the Government. After the Kick-Off Meeting, the IMS shall be updated to show progress and submitted along with the Status Reports. Deviations from the milestones require Government approval. Subtask revisions are due as changes occur. The Contractor shall remain within five (5) business days of schedule parameters set forth in the IMS unless revised. Any revision must be requested in writing and approved by the Government. The Contractor shall be held to the same five (5) day standard described. The Contractor shall not exceed three (3) schedule slippage incidents during the contract period of performance. (CDRL A005, DI-MGMT-81861A, Integrated Manual Contract Requirements).

5.0 General Information

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

5.2 Security Requirements

5.2.1 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure Contractor/subcontractor personnel who perform work on a Government facility comply with the security requirements of the facility. The Contractor shall comply with the following security regulations: 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 FAR 52.204-2, Security Requirements. The Contractor shall comply with Government security regulations including, but not limited to, DoD 5200.2-R, Personnel Security Program; DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; DoD Manual 5205.02-M, and DoD OPSEC Program Manual.

5.2.2 (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 United States Government interests. The Contractor shall ensure Contractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

5.2.3 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or Controlled Unclassified Information (CUI) in accordance with DoD 5220.22- M. Applicable equipment shall be safeguarded, maintained and operated in accordance with DoD 5220.22-M.

5.2.4 Security Clearance: Not required.

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

5.2.6 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.7 Access to Government System(s): If required, 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.2.8 Access to Government Facility or Military Installation: The Contractor shall ensure Contractor personnel who require access to a Government facility comply with the security requirements of the facility

5.2.8.1 Requirements for Common Access Card (CAC): Identification (ID) Card/Badge: The Contractor shall ensure a CAC is obtained by all Contractor/Subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The Contractor shall provide a list of personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to complete a Contractor Verification System (CVS) application and notify the Contractor of approval/disapproval of Contractor/Subcontractor personnel application. Contractor/Subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)].

5.2.8.2 Lost or Stolen CAC : The Contractor shall immediately report a lost or stolen CAC as directed by local Government policy. The Contractor shall notify the PCO of any change to the list of Contractor/Subcontractor personnel who require a CAC and provide an updated list within five (5) business days. The Contractor shall return a CAC within five (5) business days once Contractor/Subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five (5) business days after the expiration date. The Contractor shall return any and all CACs within five (5) business days after completion/termination of the contract as directed by local Government policy.

5.3 Environmental Management System (EMS): All work to be performed at the Contractor’s facility, therefore, Environmental Management System training is not required.

5.4 Agency Affirmative Procurement Programs: This acquisition does not require the purchase of Environmental Protection Agency (EPA)-designated products or United States Department of Agriculture (USDA)-designated products; therefore, the requirement does not apply.

5.5 Safety Requirements

5.5.1 Contractor Compliance: The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596, Occupational Safety and Health Act (OSHA), and DoDD 4715.1E, Environmental, Safety, and Occupational Health (ESOH). OSHA and ESOH requirements shall be incorporated into the Contractor’s safety program.

5.5.2 Voluntary Protection Program (VPP): The USAF is a participant in the OSHA VPP. Additional information regarding VPP is available at the site below: http://www.osha.gov/dcsp/vpp/index.html

5.5.3 Mishap Notification/Investigation

5.5.3.1 In accordance with Air Force Instruction (AFI) 91-204, Safety Investigations and Reports the Contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off- duty DoD military personnel; injury to on-duty DoD civilian personnel; and damage to public or private property or injury or illness to non-DoD personnel caused by Government operations. The Contractor shall ensure the Safety Office and the PCO are notified of mishaps. The Contractor shall contact the MFT (Contracting Officer’s Representative (COR), if available, or another MFT member) by telephone within four business hours. The Contractor shall cooperate with Government safety investigations.

5.5.4 Safety and Health Plan: Not required.

5.6 Reserved

5.7 Contractor Manpower Reporting: In accordance with 10 United States Code 2330a, the Contractor shall provide an annual count of Contractor/subcontractor personnel performing work for each fiscal year if the DoD is the requiring activity and if the acquisition is in excess of $3,000,000.00. The Contractor shall report all Contractor labor hours, including subcontractor labor hours, required for performance of the services provided under the contract in the eCMRA. 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 shall establish a record for the contract/order in eCMRA no later than 30 calendar days after contract/order award. The Contractor shall enter Order Data, Contract Data and Location Data. Data for Air Force service requirements must be input at the Air Force CMRA link. Additional information and user manuals for Government personnel and Contractors are available at the Army CMRA link at http://www.emcra.mil.

5.8 Invoicing/Payment and Receipt/Acceptance

5.8.1 In accordance with DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports, the Contractor shall submit/process payment requests (invoices, Receiving Reports or combos) and receipt/acceptance documents via PIEE. Additional information regarding PIEE is available at the site below:

https://wawf.eb.mil

5.8.2 CDRL deliverables may be submitted using PIEE or be submitted directly to the applicable MFT member in accordance with the CDRL. The CDRL will determine submittal requirements; however, separately priced data must be accepted in PIEE in order for the Contractor to receive payment, and both separately priced and non-separately priced data must be accepted in PIEE in order for the contract line item to be closed out.

5.8.3 Services will be accepted by the COR/Program Manager, AFLCMC/WIUAA

5.9 Quality Management System (QMS): The Contractor shall ensure the quality of services through a quality and/or inspection system. The Contractor shall submit a Quality Control Plan (QCP) addressing detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur. The plan shall include the schedule of quality assurance/control inspections planned by the Contractor. 100% compliance with the QMS is required. (A006, DI-QCIC-81722, Quality Program Plan).

5.10 Trafficking in Persons

5.10.1 The Contractor shall comply with FAR 52.222-50, Combating 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 at the site below: http://www.state.gov/j/tip

5.10.2 In accordance with the Defense Contingency COR Handbook section on Combating Trafficking in Persons, the COR must inform the PCO if the Contractor fails to comply with the requirements of FAR 52.222.50. The PCO must convey the information to DoD Combat Trafficking in Persons Law Enforcement and Support /Office of Under Secretary of Defense (OUSD) Personnel and Readiness (P&R) Defense Human Resources Activity (DHRA).

6.0 Appendices

reissued 10 April 2014 http://www.e- publishing.af.mil/ Paragraphs 1.3.1.1, 2.4.6.1.1- 2.4.6.1.2

September 2012 http://www.acq.osd.mil/dp ap/ccap/cc/corhb/Files/DC COR_Handbook_2012.pdf Section on Combating Trafficking in Persons – Chapter 8, Monitoring the Contractor

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

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

www.acquisition.gov Sections applicable to contract and PWS

http://www.acq.osd.mil/dpap/policy/ policyvault/Enterprise- wide_Contractor_Manpower_Report ing_Application_memorandum.pdf Entire

http://www.osha.gov/pls/osha web/owadisp.show_documen t?p_id=2743&p_table=OSH ACT Entire

6.1 Appendix C – Required Documentation

The following documentation is required to properly develop and draft the required technical orders for the AC-130 effort.

Military Standards and Handbooks

Nongovernmental Documents

SNC AC-130 Documentation

PR: FD2060-23-30010 PWS REVISION: 0

Distribution Statement: C

6.2 Appendix D – List of Acronyms