PWS.pdf

PR: FD2060-18-30243 PWS REVISION: 0 1

Distribution Statement: C

Performance-Based Work Statement for

Technical and Management Expertise

FD2060-18-30243

2 November 2017

Distribution Statement C: Distribution authorized to U.S. Government agencies and their contractors (Administrative or Operational Use; 04-01-23). Other requests for this document shall be referred to AFLCMC/WNY, Robins AFB, GA 31098.

PR: FD2060-18-30243 PWS REVISION: 0 2

1.0 Description of Services: This Performance-Based Work Statement (PWS) establishes requirements for contractor software, technical, logistics, engineering, operational tasks, training, cybersecurity and SME support at CONUS and OCONUS (Alaska) locations. The scope of work required is outlined by the definition of terms herein and the work requirements set forth in the sections below. Minor and indefinite details of work are not described; however, such minor work as is inherent in the support described is necessary to adequately accomplish work requirements shall be required.

1.1 Objective(s): This Performance-based Work Statement (PWS) is to obtain sustainment efforts within the Common Avionics Program Office at Robins AFB GA. These efforts include contractor software, subject matter experts, technical advisors/engineering, material oversight, and logistics provision with a Period of Performance (POP) of three (3) years (one 12-month basic with two ordering periods). To fully meet performance objectives, the Contractor shall fill all positions with qualified personnel at award and any vacated positions within one calendar month of vacancy occurrence. Throughout this PWS it should be understood that this entire

PWS is for the several USAF Common Avionics systems including, but not limited to CLIP, JADSI, JTIDS, MIDS, ROBE, SADL, DIRECT, JRE/JTEP, LAK and Pocket J, Airborne radios and Nuclear Command, Control and Communications system. The Common Avionics Program

Office effort is targeted to start 2 Feb 2018. The contract type shall be an Indefinite Delivery

Indefinite Quantity (IDIQ), estimated value for this contract effort is $4 million.

1.2 Benefit to United States Air Force (USAF): AFLCMC/WNY will have additional resources to acquire deliverables for the Common Avionics Systems via software, subject matter experts, technical advisors/engineering, material oversight, and program and logistics provisions to improve reliability, availability, maintainability, and sustainability.

1.3 Background: AFLCMC/WNY has overall system support responsibility and authority for the several USAF Common Avionics systems including, but not limited to CLIP, JADSI, JTIDS, MIDS, ROBE, SADL, DIRECT, JRE/JTEP, LAK and Pocket J, Airborne radios and Nuclear

Command, Control and Communications (NC3) system. The systems listed in the preceding paragraph will be referred to in the rest of this document as Tactical Data Link (TDL) and NC3 systems.

AFLCMC/WNY Common Avionics Program Office is responsible for operational and logistical reports concerning impacts to future aircraft missions. Non-recurring engineering and technical services are therefore required to apply technical and logistical elements to sustain Common

Avionics Systems. This effort includes requirements definition, systems engineering, installation support, and technical documentation and evaluation, on an as-required basis.

2.0 Services Summary:

Performance Objective PWS

Reference

Performance Threshold

Fill positions with required personnel to meet performance objectives.

1.1 All positions are filled with qualified personnel

at award and any vacated positions shall be filled within one calendar month of vacancy occurrence.

PR: FD2060-18-30243 PWS REVISION: 0 3

Quality of CDRL deliverable

4.2.1 There shall be no more than one total rejection

of deliverables per quarter. The Government will reject a deliverable if five (5) or more technical errors or ten (10) 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 defined as a typographical or grammatical error.

The rejected deliverable shall be corrected and resubmitted within three (3) business days of notification of Government rejection in accordance with the associated DD Form 1423 instructions/ requirements.

Receipt of CDRL deliverable

4.2.2 Contractor shall deliver all CDRLs with no more

than one (1) 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.

Quality and Receipt of

Monthly Status Reports

4.2.3

The Contractor shall provide monthly status reports to the Government. The Contractor shall document task status, data deliverables, contract issues and actions, expenditure data, as well as anticipated future task requirements during the next reporting period. In addition, all problem areas shall be covered, with recommended solutions and, if requested, the outcomes after solutions are implemented. The Contractor shall assign and track action items for each unresolved program task, problem and issue.

The Contactor shall assign action numbers based on the program and action item source. The monthly status report shall be delivered no later than the tenth calendar day of the following month. If no open projects exist or are projected, no monthly status report is due.

Monthly status reports shall conform to CDRL

A001 (DI-MGMT- 81991), Monthly Status

Reports.

PR: FD2060-18-30243 PWS REVISION: 0 4

Comply with all

Security Requirements

5.2

Zero security violations during the contract period of performance due to the negligence of a

Contractor employee.

Adherence to Contractor

Quality Management

System (QMS)

5.7 100% compliance with the QMS is required.

Contractor Manpower

Reporting

5.9 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.

The Contractor shall provide an annual count of contractor/subcontractor personnel performing services and report all contractor/subcontractor labor hours required for performance of services for each fiscal year. All data shall be reported no later than October 31 of the following fiscal year.

3.0 Government Property and Services: Should the contractor require information from the

Government, the Contracting Officer Representative (COR), (AFLCMC/WNY) is responsible for supplying that information within 15 business days after receipt of a written request (e-mail is acceptable). The Government will furnish the following information to be used for this task:

a. Reports providing related technical or historical data

b. Required drawings and technical orders

3.1 Government Property: The US Government will provide administrative equipment, computers and supplies for contractor’s performance of this effort. The US Government will provide the administrative office space used to perform the requirements of the PWS.

3.2 Government Property to be Provided: The Contractor will have access to on site computer equipment and data systems located at Robins AFB, Georgia. This includes access to computers, computer peripherals, local area networks/data systems, and email. Specific GFE to be provided (per person assigned to work the task on site) includes:

a. Office space with accompanying office furniture

b. Office furniture to include as a minimum; one desk, one chair, appropriate file/storage cabinets, and book shelves (as required)

c. US Government “Class A” telephone, facsimile, and email per office space provided

d. One US Government computer per office space provided

e. Any additional GFE required on an “as needed” basis

4.0 Technical Requirements

4.1 Period and Place of Performance:

PR: FD2060-18-30243 PWS REVISION: 0 5

4.1.1 Contract/Order Period of Performance: This will be an Indefinite

Delivery/Indefinite Quantity ID/IQ contract with a basic period of performance for one (1) year from the effective date of the contract, and will include two (2) additional one-year options.

4.1.2 Place of Performance: These services will primarily be performed at Robins AFB and the contractor facility. Occasional support services will be performed at CONUS and OCONUS (Alaska) locations.

4.1.3 Performance Requirements: The following task statements are meant to be descriptive, not specific. The specific work shall be in accordance with and within the scope of the subsequent paragraphs and identified in the task orders (TOs) placed on this contract.

The Contractor shall adhere to Organizational Conflict of Interest (OCI) clauses.

4.1.4 Data Analysis: The Contractor shall provide data systems analysis. The Contractor shall capture and integrate the available historical data from numerous US Government information systems for the purposes of identifying metrics and developing a matrix of the information. This matrix would be tailored to provide the Program Manager with the necessary information to enhance timely decisions for the most economic cost. The

Contractor shall assist in the identification of “bad actors”, critical paths, cost and schedule, and other necessary management information. The Contractor shall enhance the systems to the war fighter by providing the US Government with essential real-time information.

4.1.5 Technical: The Contractor shall work with the program manager to create an organic system of redundant support under the constructs of this document. At a minimum, training shall consist of process, procedures and methodologies to affect creation and testing of Data

Fills, tracking and implementing software/firmware changes affecting airborne systems, integration of any and all changes with the Lab; technical support for TO/TCTO changes and

CPIN updates, technical support to field activities for all software/firmware changes and applicable test plans; and all data analysis and logistics relating to Data Fill in relation to other operational commands and sister services.

Performance based contracting methods will be used with this task order. The Government will measure deliverable in accordance with the metrics provided below and documented by the contractor in a spreadsheet. The Contractor shall submit this spreadsheet as part of the

Monthly Progress, Status and Management Report. The COR will track these performance reports.

For performance based metrics, timeliness of reports shall be considered as follows:

Contractor's Monthly Progress, Status and Management Reports (CDRL A001)

Good: Delivery on or before date indicated.

Fair: Delivery within one week of good performance metric.

Poor: Delivery beyond one week of good performance metric.

PR: FD2060-18-30243 PWS REVISION: 0 6

Unsatisfactory Contractor performance will result in the COR issuing a negative PAR.

The COR will set a suspense date and forward the PAR to the PCO for submission to the

Contractor. The PCO will submit the PAR to the Contractor for corrective action. The

Contractor shall explain the deficiency and identify the corrective action they shall take to resolve the deficiency and prevent recurrence. The Contractor shall sign and return a negative PAR to the PCO by the suspense date. The COR will upload the PAR in the

CORT Tool under COR Status Reports.

4.2 Contract Data Requirements List (CDRL):

4.2.1 There shall be no more than one (1) total rejection(s) of deliverables per quarter. The

Government will reject a deliverable if five (5) or more technical errors or ten (10) 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 defined as a typographical or grammatical error. The rejected deliverable shall be corrected and resubmitted within three

(3) business days of notification of Government rejection in accordance with the associated

DD Form 1423 instructions/requirements.

4.2.2 The Contractor shall deliver all CDRLs with no more than one (1) 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.

4.2.2.1 Monthly Status Report: The Contractor shall provide monthly status reports to the Government. The Contractor shall document task status, data deliverables, contract issues and actions, expenditure data, as well as anticipated future task requirements during the next reporting period. In addition, all problem areas shall be covered, with recommended solutions and, if requested, the outcomes after solutions are implemented.

The Contractor shall assign and track action items for each unresolved program task, problem, and issue. The Contactor shall assign action numbers based on the program and action item source. The monthly status report shall be delivered no later than the tenth calendar day of the following month. If no open projects exist or are projected, no monthly status report is due. Monthly status reports shall conform to CDRL A001 (DI-

MGMT- 81991), Monthly Status Reports.

4.2.2.2 Software Support: The Contractor shall perform all the necessary actions to review and analyze software change requests (CR) or Materiel Improvement Projects

(MIP)/Deficiency Reports (DRs) submitted against systems software. The Contractor shall review software/firmware documentation such as software design documents, test plans, test cases, and block cycle change documents. The Contractor shall create Data Fill software for the systems and perform the planning and implementation of software changes between the Lab and the military services, including integration support, regression, and platform interoperability testing. Work status reports shall be submitted

PR: FD2060-18-30243 PWS REVISION: 0 7

as described in the Contract Data Requirements List (CDRL) A001, DI-MGMT- 81991, Monthly Status Report.

4.2.2.3 Technical Support: The Contractor shall provide technical support for the resolution of systems hardware/software/firmware problems. Support includes equipment specialist related tasks and Technical support to be provided may include

Technical Order (TO) and Time Compliance Technical Order (TCTO) changes, Computer Software Configuration Item (CSCI) and Computer Program Identification

Number (CPIN) updates, technical drawings review, assistance to platform managers

(such as F-15, E-3, C-130, C-5, KC-135, TSC-159 and other C2 platforms) on integration issues, technical support to field activities, investigation of deficiencies reports received and for software support of software change testing and test plans. Work may include engineering support and testing and evaluation support. Work status report shall be submitted as described in CDRL A001, DI-MGMT- 81991 Monthly Status Report.

4.2.2.4 Program Management and Logistics Support: The Contractor shall participate in systems Program Reviews, Communications Product Improvement

Working Groups (PIWGs) and technical interchange meetings; evaluation and assistance in the development and review of system design for supportability, integrated logistics, and technical reviews. The contractor shall participate in developing, submitting, editing and updating documentation required for system design, development, testing and certification to include: Engineering Support Plans, Information Support Plans, Program

Protection Plans, Security Classification Guides, Life Cycle Management Plans, Enterprise Architecture Documents and Test Requirements Documents, and other documents required for system sustainment, etc. The Contractor shall use existing cost, schedule, and management control tools and processes in providing logistics. Work status report shall be submitted as described in CDRL A001, DI-MGMT- 81991 Monthly Status

Report.

4.2.2.5 Data, Reporting and Deliverables: The Contractor shall generate a monthly status report. This report shall include technical data, program/project status updates, and major accomplishments during the reporting period as described in CDRL A001, DI-

MGMT- 81991 Monthly Status Report.

4.2.2.6 Travel: Travel will be reimbursed at actual cost in accordance with the limitations set forth in FAR 31.205-46. Profit shall not be applied to travel costs.

Contractors may apply indirect costs to travel in accordance with the contractor’s usual accounting practices consistent with FAR 31.2. The contractor shall ensure that the requested travel costs will not exceed the amount authorized in this contract. There may be cases due to short-notice requirements where an over per diem situation arises. When this is the case, the COR or CR is required to authorize the over per diem rate in advance.

A contractor-generated travel authorization request form shall be submitted to the CO for approval 5 days prior to beginning any travel. In emergencies, direction to travel will be

PR: FD2060-18-30243 PWS REVISION: 0 8

given via other means in which case a travel authorization request form shall be submitted within five (5) duty days upon return. The form must identify the traveler’s name, travel dates, location(s), per diem rates, purpose of trip, all estimated expenses

(i.e., lodging, lodging tax, M&IE, transportation [air fare, train, bus, rental car, fuel for rental car, private car mileage], registration, tolls, parking, other related expenses), and an estimate of the remaining travel funds after the travel being authorized is complete. An electronic copy of the approved request form and a Travel Expense Summary shall be submitted with the monthly invoice.

The contractor may be required to travel to other US Government installations and contractor facilities. Trips and numbers and types of personnel shall be limited to the minimum required to accomplish requisite work. The contractor shall be responsible for arranging all contract personnel travel during the program effort. The contractor shall use the lowest cost mode of transportation commensurate with mission requirements and good traffic management principles. Travel will be reimbursed in accordance with the current Joint Travel Regulation (JTR) rates in effect at the time of travel. All travel must be approved by the government PM and shall be documented in trip reports.

4.3 Holidays and facility closings: Contractor personnel shall observe the 10 federal holidays and facility closings, e.g., energy down days, authorized by the Government in accordance with

AFMC MP 5337.1, Service Contracts - General. Contractor personnel will only be permitted access to Government facilities when Government personnel are present.

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis: The Functional

Commander/Functional Director (FC/FD) has determined, by placing in writing their decision, that this requirement is not Mission Essential (M-E) in accordance with DoDI 1100.22.

5.2 Security Requirements:

5.2.1 General: The effort required for this task is expected to be primarily UNCLASSIFIED but may be classified at the SECRET level. All handling or classified information and material shall be located on Government sites. There will be no requirement for classified handling on Contractor sites. Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of US Government systems without prior approval. All requests for information shall be forwarded to the

AFLCMC/WNY Security Manager.

5.2.2 Security Regulations: The Contractor shall ensure personnel, information, systems, property, and 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.

PR: FD2060-18-30243 PWS REVISION: 0 9

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. The Contractor shall ensure Contractor personnel who perform work on a Government facility comply with the

OPSEC procedures of the facility.

5.2.4 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or CUI in accordance with DoD 5220.22-M, National Industry Security

Program. Applicable equipment shall be safeguarded, maintained and operated in accordance with DoD 5220.22-M.

5.2.5 Security Clearance: The Contractor shall ensure applicable Contractor personnel have security clearances at the Secret level for proper accomplishment of contract/order requirements. The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. Contractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified information and/or CUI and classified items.

5.2.6 Security Incident or Violation: The contractor will immediately notify the organization security team of any actual security violation, security incident, or of any indication of a potential unauthorized disclosure or compromise of classified or sensitive but unclassified information.

5.2.7 Access to Government Facility or Military Installation: The Contractor shall ensure personnel, information, systems, property, facility and international security requirements are met. The Contractor shall comply with all applicable security regulations and clauses listed in the contract.

5.2.8 Common Access Card (CAC): The Contractor shall ensure a CAC is obtained/maintained and managed by all contractor/subcontractor personnel who require a

CAC for access to DoD computer networks and systems, for DoD installation entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

5.2.9 Access to Robins Air Force Base (AFB)

5.2.9.1 Background Check: In accordance with AFI 31-113, Installation Perimeter

Access Control, all non-DoD personnel requiring frequent or recurring access to Robins

AFB must have a background check completed by the 78th Security Forces Squadron (78

SFS)/S5P Visitor Control Center (VCC) or Base Defense Operations Center (BDOC) before they will be granted qualified base access.

PR: FD2060-18-30243 PWS REVISION: 0 10

5.2.9.2 Entry to Robins AFB: In accordance with RAFB IDP 31-101, Contractor personnel granted qualified base access may receive installation entry and circulation privileges under limited circumstances or conditions. They do not have the authority to sponsor anyone for access to Robins AFB or vouch for anyone to enter Robins AFB.

5.2.9.3 Identification of Contractor Personnel Requiring Access: In accordance with

RAFB IDP 31-101, a Contractor awarded a contract/order that requires services to be performed on Robins AFB shall provide the badging agent and PCO a list of all contractor/subcontractor personnel requiring access to Robins AFB, the contract/order number and the period of performance. The Contractor shall also provide, if possible, the location of the work site and the days/hours during which the contractor/subcontractor personnel will require access to Robins AFB.

5.2.9.4 Defense Biometric Identification System (DBIDS) Identification (ID) Card:

In accordance with RAFB IDP 31-101, Contractor personnel requiring access to Robins

AFB, but not LAN (Local Area Network) access, shall complete the Robins AFB Access

Affidavit to obtain a DBIDS ID card and return it to the badging agent. After verification by the badging agent, Contractor personnel shall come to the VCC to claim their DBIDS

ID card.

5.2.9.5 Common Access Card (CAC): In accordance with RAFB IDP 31-101, Contractor personnel requiring access to Robins AFB and LAN access will be entered in the Contractor Verification System (CVS) by the Trusted Agent (TA). The TA will email their user ID/password and instructions on accessing the Robins AFB public website to the Contractor personnel. Contractor personnel shall access the website and complete all applicable forms as directed. After this process is completed, Contractor personnel shall make an appointment with the 78th Mission Support Group (MSG) via the CAC Web

Scheduler to claim their CAC.

5.2.9.6 Loss of Card: In accordance with RAFB IDP 31-101, if Contractor personnel lose their DBIDS ID card or CAC, they shall notify the badging agent immediately.

5.2.9.7 Retrieval of Card(s): In accordance with RAFB IDP 31-101, the Contractor shall notify the badging agent immediately upon Contractor personnel being transferred/ terminated. The Contractor is responsible for retrieving contractor/subcontractor CAC(s) and/or DBIDS ID card(s) (including restricted/controlled area badges) upon transfer/ termination of Contractor personnel or completion/termination of the contract/order. The

Contractor shall return all retrieved CAC(s) and/or DBIDS ID card(s) to 78 SFS/S5P.

5.3 Environmental Management System (EMS): IAW 1 Aug 07, AFMC/CV Policy Letter, Conformance with AF Environmental Management System (EMS) Requirements for Contracts

Performed on AF Installations and the 11 Dec 06, SAF Policy Letter, Conformance with AF

Environmental Management System (EMS) Requirements for Contracts Performed on AF

Installations

PR: FD2060-18-30243 PWS REVISION: 0 11

All contractors who physically perform work on Robins AFB must receive EMS awareness training. All prime contractors must complete the training prior to beginning work on RAFB and must ensure that all subcontractors comply with this requirement.

78 CEG/CEV has already developed EMS training and it’s a requirement for military and civilians working on Robins. The policy letter made it mandatory for contractors working on

Robins to complete EMS Training.

There are 3 ways contractors can complete EMS training:

1) With CAC, go to 78 CEG/CEV website and click on EMS Awareness Training, choose

Option 1 https://geobase.robins.af.mil/emstraining/EMSTrainingOptions.aspx

2) Without a CAC, request a copy of EMS training from 78 CEG/CEV Workflow Mailbox.

3) If a company is ISO 14000 certified, the contractor does not have to complete Robins

AFB EMS Awareness Training; however, the contractor must submit documentation to the Contracting Officer (CO) stating ISO 14000 Certification.

5.4 Agency Affirmative Procurement Programs: In accordance with FAR 23.404, Agency

Affirmative Procurement Programs, 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 biobased product listings

[http://www.biopreferred.gov] shall, at a minimum, meet the EPA or USDA standards for recovered materials or biobased 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.

5.5 Safety Requirements:

5.5.1 Contractor Compliance: Contractors shall comply with Occupational Safety and

Health Act (OSHA) (Public Law 91-596) and OSHA Standard 29 CFR 1910, 1926, for the protection of their employees. To ensure the protection of Air Force personnel, assets, and interests, the contractor is solely responsible for compliance with all federal, state and local laws, codes, ordinances, regulations, the Occupational, Safety and Health Act (Public Law

91-596), and the resulting Occupational Safety and Health Administration (OSHA) Standard

29 CFR 1910 and 1926, all Air Force Occupational Safety and Health (AFOSH) Standards, and any applicable local guidance. The contractor shall establish and maintain a safety and health program detailed in a written Contractor’s Safety and Health Plan. The Air Force is part of the OSHA Voluntary Protection Program (VPP). All contractors are required to familiarize themselves with the requirements of VPP. Information on the VPP can be accessed at http://www.osha.gov/dcsp/vpp/index.html.

5.5.2 Mishap Notification/Investigation: 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 (COR, if available, or another https://geobase.robins.af.mil/emstraining/EMSTrainingOptions.aspx

PR: FD2060-18-30243 PWS REVISION: 0 12

MFT member) by telephone within 48 hours. The Contractor shall cooperate with

Government 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 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. 100% compliance with the QMS is required.

5.8 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.9 Contractor Manpower Reporting:

5.9.1 In accordance with 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 award. In accordance with the Contractor Manpower Reporting / Contractor

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

5.9.2 United States Code title 10, Section 2330a (10 USC 2330a) requires an annual inventory of contracts for services performed during the fiscal year including the number of

Contractor employees. In accordance with the Secretary of the Air Force for Acquisition

(SAF/AQ) Memorandum, Implementation of FY11 NDAA [National Defense Authorization

Act] 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 for each fiscal year 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.9.3 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 eCMRA site http://www.state.gov/j/tip

PR: FD2060-18-30243 PWS REVISION: 0 13

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.10 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.

5.11 Limitations on Contractor Performance

The Contractor shall not perform the following functions in connection with the services provided under this delivery order:

o Approve, decide, or sign as a Contracting Officer;

o Negotiate with Air Force suppliers;

o Accept or reject supplies or services;

o Determine acquisition, disposition, or disposal of Government property;

o Direct other Contractor or Government personnel;

o Determine cost reasonableness, allowability, or allocability;

o Vote on a source selection board;

o Supervise Government personnel;

o Approve Government requirements or plans;

o Determine Government policy.

6.0 Appendices: CDRLs

Data Item Number Title of Data Item Authority

A001 Monthly Status Report DI-MGMT- 81991 http://www.ecmra.mil/