ATCH_6_Peformance_Based_Work_Statement.pdf

PR: FD2060-17-30361 PWS Revision: 1 1

Performance-Based Work Statement for

ViaSat Engineering Services

FD2060-17-30361

06 Apr 2017

DISTRIBUTION D: Distribution authorized to Department of Defense and U.S. DoD contractors only. Other request for this document shall be referred to

AFLCMC/WNYBBA.

PR: FD2060-17-30361 PWS Revision: 1 2

1.0 Description of Services:

1.1 Objective (s): The purpose of this effort is to provide the Air Force Life Cycle Management

Center, Electronic Warfare & Avionics Division (AFLCMC/WNY), Robins Air Force Base with engineering, technical, and logistics support for the common avionics systems used across the

Department of Defense (DoD). This five year contract will consist of one base year and four 12-month ordering periods. The estimated value of this requirement is $1.5M.

The contractor will be required to provide logistics services, engineering services, operational support, training, and SME support at CONUS and OCONUS locations. Depending on the system operations tempo (OPSTEMPO), SME support may be necessary to operate and maintain systems during wartime and peacetime contingencies. All positions shall be filled with qualified personnel at contract/order award and any vacated positions shall be filled within one (1) calendar month of vacancy occurrence. The contractor will be required to conduct Software Engineering and Investigation (SE&I) for Tactical Data Links (TDL) for the sustainment of various common avionics systems including diagnostic troubleshooting for LRUs/parts, replacement of obsolete parts and maintenance of the various common avionics systems.

These services include technical and engineering/sustainment to the following systems, but are not limited to: Multifunctional Information Distribution System (MIDS) and MIDS Joint

Tactical Radio System (JTRS). This requirement is to support investigation of problem/deficiency reports, test and evaluation events, technical reviews and validation/ verification for provisioning, technical and engineering data associated with the TDL programs.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by providing the needed engineering, technical and logistics support for Common Avionics systems used across the DoD.

1.3 Background: AFLCMC/WNY has overall system support responsibility and authority for several USAF Common Avionics systems including MIDS and MIDS JTRS. The systems listed above will be further referenced in this document as TDL systems.

AFLCMC/WNY Common Avionics Division is responsible for operational and logistical reports concerning impacts to future aircraft missions. Non-recurring engineering services are therefore required to apply technical and logistical support 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 (1) calendar month of vacancy occurrence.

PR: FD2060-17-30361 PWS Revision: 1 3

Quality of CDRL deliverable

4.2.1 There shall be no more than one (1) 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.

Comply with all

Security

Requirements.

5.2 Zero (0) security violations during the contract period of performance due to the negligence of a Contractor employee.

Contractor

Manpower

Reporting

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

Contractor shall establish a record for the contract/order in eCMRA including Order Data, Contact Data and Location

Data.

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

3.1 Government Facilities: Use of Government Property will not be provided.

3.2 Government System(s): Access to Government system(s) will not be required to perform tasks under the contract/order.

4.0 Technical Requirements

PR: FD2060-17-30361 PWS Revision: 1 4

4.1 Period and Place of Performance: Work will be performed at CONUS/OCONUS locations up to six (6) times per year. They include but are not limited to: ViaSat facilities, all US Air

Force installations, contractor facilities, FMS nations and other travel locations.

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 four (4) additional one-year ordering periods. See Section

F.

4.2 Contract Data Requirements List (CDRL):

4.2.1 The Contractor shall deliver all data/reports associated with all CDRLs, with no more than one (1) rejection of each deliverable. 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.

A001, Contractor’s Progress, Status and Management Report, DI-MGMT-80227/T.

4.2.2.1 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 will 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.

4.2.2.2 Technical Support: The Contractor shall provide technical support for the resolution of systems hardware/software/firmware problems. Support includes equipment specialist related tasks such as technical support. 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

PR: FD2060-17-30361 PWS Revision: 1 5 software change testing and test plans. Work may include engineering support and testing and evaluation support.

4.2.2.3 Program 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 support, and technical reviews. The

Contractor shall use existing cost, schedule, and management control tools and processes in providing logistics support to the program.

4.2.2.4 Technical Training: 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 support relating to Data Fill in relation to other operational commands and sister services.

4.2.2.5 Data, Reporting and Deliverables: The contractor will generate a monthly status report. This report will include technical data, program/project status updates, major accomplishments during the reporting period and a financial recap. The contractor will provide a final report of tasks accomplished through task order completion as described in

A001, Contractor’s Progress, Status and Management Report, DI-MGMT-80227/T.

Performance based contracting methods will be used with this task order. Deliverables will be measured in accordance with the metrics provided below and documented by the

Contractor in a spreadsheet. This spreadsheet will be submitted as part of the Contractor's

Monthly Progress, Status and Management Report. The US Government Task Leader (GTL) will track these performance reports (see Attachment four, Inspection of Supplies and

Services Requirements).

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.

4.3 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

PR: FD2060-17-30361 PWS Revision: 1 6 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 COR or CR for approval 5 days prior to beginning any travel. In emergencies, direction to travel will be 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 names of all travelers, 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.4 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

(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 Knowledge and/or generation of classified information and/or Controlled Unclassified

Information (CUI) are required for performance of the contract/order. The Contractor shall ensure applicable Contractor personnel have security clearances at the appropriate level.

5.2.2 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and international 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)

PR: FD2060-17-30361 PWS Revision: 1 7

Program, DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual, and

Robins Air Force Base Integrated Defense Plan (RAFB IDP) 31-101.

5.2.3 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of

USAF missions to adversary collection and exploitation of critical information. The Contractor shall ensure compliance with DoDD 5205.02E and DoD Manual 5205.02-M to protect 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 Removal of Documentation: Contract 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.5 Processing DoD Forms: The US Government Program Manager will assist contract personnel in processing the necessary DoD forms to obtain base or area badges for access to US

Government facilities, as required.

5.2.6 Divulging Information: The contractor shall not divulge any information regarding files, data, processing activities/functions, user ID's, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contract personnel shall abide by all US Government rules, procedures, and standards of conduct. Contractors requiring access to US Government Automated Information Systems (AIS) shall have background investigations and complete security awareness training prior to the start of contract performance. When the period of performance is complete or and contractor personnel leave work on this project they will have five days to terminate all their network user account and to return all access cards and base identification badges specifically acquired for this contract or task orders.

5.2.7 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.8 FOR OFFICIAL USE ONLY INFORMATION: FOUO information provided under this contract shall be safeguarded as specified in DoDM 5200.01-V4, DoD Information Security

Program: Controlled Unclassified Information.”

5.2.9 VISIT AUTHORIZATION REQUEST: Access to US Government facilities may be limited. Should access to secured government facility be required in the performance of duties, the contractor shall have the corporate security manager submit a Visit Authorization Request

(VAR) via the Joint Personnel Adjudication System (JPAS). This shall be done at least five workdays prior to the required access date. This request should be for a one-year access to the facility and be renewed on an annual basis through the submission of a subsequent VAR.

PR: FD2060-17-30361 PWS Revision: 1 8

5.2.10 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.11 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.12 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.13 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 Contractor shall ensure the system account(s) are closed.

5.2.14 Access to Government Facility or Military Installation: The Contractor shall ensure

Contractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation. The Contractor shall ensure

Contractor personnel who require access to a USAF installation comply with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

5.2.15 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.16 Access to Robins Air Force Base (AFB)

5.2.16.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-17-30361 PWS Revision: 1 9

5.2.16.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.16.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.16.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.16.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.16.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.16.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)

5.3.1 Executive Order (E.O.) 13423, Strengthening Federal Environmental, Energy, and

Transportation Management, and E.O. 13514, Federal Leadership in Environment, Energy, and

Economic Performance, establish the requirement for an EMS.

PR: FD2060-17-30361 PWS Revision: 1 10

5.3.2 In accordance with the Assistant Secretary of the Air Force Memorandum, Conformance with Air Force Environmental Management System (EMS) Requirements for Contracts

Performed on Air Force Installations, dated 11 Dec 06, and the Air Force Materiel

Command/Vice Commander (AFMC/CV) Memorandum, Conformance with Air Force

Environmental Management System (EMS) Requirements for Contracts Performed on Air Force

Installations, dated 1 Aug 07, Contractor personnel who perform work on any USAF installation shall comply with the EMS requirements established by the installation.

5.3.3 Contractor personnel shall complete EMS training prior to beginning work on any USAF installation.

The EMS training requirement may be satisfied by any of the following means:

1) If the Contractor is International Organization for Standardization (ISO) 14000-certified, Contractor personnel do not have to complete EMS training; however, the Contractor must provide documentation of ISO 14000 certification to the PCO.

2) If Contractor personnel possess CAC(s), they may complete Advanced Distributed

Learning Service (ADLS) ZZ133070, Environmental Management System - General

Awareness Training. The Contractor shall provide their certificate(s) to the PCO.

If services will be performed on Robins AFB, include the following paragraph.

3) If Contractor personnel do not possess CAC(s), the Contractor may request a copy of

Environmental Management System Awareness training via the Environment

Management Workflow below. The Contractor shall notify the PCO that EMS training has been completed.

78ceg.cev.FrontOfc@us.af.mil

5.3.4 The prime Contractor shall ensure subcontractors comply with the EMS requirement.

5.4 Affirmative Procurement Programs (APP)

5.4.1 Agency Affirmative Procurement Programs

In accordance with FAR 23.404(b)(1), 100% of purchases of Environmental Protection Agency

(EPA)-designated products included in the Comprehensive Procurement Guidelines (CPG) list

[http://www.epa.gov/cpg/products.htm] and/or United States Department of Agriculture

(USDA)-designated products included in the 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.

In accordance with FAR 23.404(a)(iii), the Contractor shall provide estimates and verification of recovered material for EPA-designated CPG products and certification for both EPA-designated mailto:78ceg.cev.FrontOfc@us.af.mil http://www.epa.gov/cpg/products.htm http://www.biopreferred.gov/

PR: FD2060-17-30361 PWS Revision: 1 11

CPG products and USDA-designated biobased products. In accordance with the Robins Air

Force Base, Georgia / Green Procurement Program (GPP) Plan, the Contractor shall provide estimates and certifications to the Government for completion of the applicable attachment(s) to be included in the Purchase Request (PR) package.

5.5 Safety Requirements

5.5.1 Contractor Compliance:

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, Environment, 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):

Contractor personnel performing work on a USAF installation shall participate in the local VPP.

5.5.3 Mishap Notification/Investigation:

In accordance with AFI 91-204, Safety Investigations and Reports, the Contractor shall report mishaps involving damage or injury to USAF interests. The Contractor shall ensure the USAF is notified of mishaps. The Contractor shall contact the Contracting Officer’s Representative

(COR), if available, or another MFT member by telephone within 48 business hours and the

Contractor shall cooperate with USAF safety investigations.

5.6 Contractor Manpower Reporting

5.6.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.6.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).

PR: FD2060-17-30361 PWS Revision: 1 12

5.6.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 https://afcmra.dmdc.osd.mil. 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.