PWS.pdf

PR: FD2060-16-91013 PWS Revision: 0

DISTRIBUTION D. Distribution authorized to Department of Defense and U.S. DoD contractors only (Administrative or Operational Use.) (02 Nov 2016). Other request for this document shall be referred to AFLCMC/WNYBBA.

Performance-Based Work Statement (PWS) for

Contractor Logistics Support (CLS) and Services of the

AN/USQ-175 Communications Control Set (CCS)

PR: FD2060-16-91013

Date/Revision: 18 Apr 17 / 0

DISTRIBUTION D. Distribution authorized to Department of Defense and U.S.

DoD contractors only (Administrative or Operational Use.) (02 Nov 2016). Other request for this document shall be referred to AFLCMC/WNYBBA.

ROBE PWS 18 Apr 17

PR FD2060-16-91013 / PWS Revision 0

CHANGE LOG

Revision Date Reference Change Contact

TABLE OF CONTENTS

Section Title Page

1.0 DESCRIPTION OF SERVICES:

1.1 OBJECTIVE:

1.2 BENEFIT TO UNITED STATES AIR FORCE (USAF):

1.3 BACKGROUND:

2.0 SERVICES SUMMARY

3.0 GOVERNMENT FURNISHED PROPERTYAND SERVICES

3.1 GOVERNMENT PROPERTY

3.2 COMMERCIAL ASSET VISIBILITY (CAVAF)

3.3 GOVERNMENT SYSTEMS

3.4 GOVERNMENT FURNISHED FACILITIES

3.5 GOVERNMENT FURNISHED INFORMATION (GFI)

4.0 PROGRAM AND TECHNICAL REQUIREMENTS/CLIN STRUCTURE

4.1 CLIN X001 – SUSTAINING ENGINEERING

4.2 CLIN X002 - SPARES

4.3 CLIN X003 - DEPLOYED SUBJECT MATTER EXPERT (SME) SUPPORT

4.4 CLIN X004 - EXERCISE AND TEST EVENT SUPPORT (CONUS SME ONLY)

4.5 CLIN X005 - TECHNICAL PUBLICATIONS

4.6 CLIN X006 – CONTRACT DATA REQUIREMENTS LIST (CDRL)

4.7 CLIN X007 - TRAVEL

4.8 CLIN X008 – VARIABLE PMO

4.9 CLIN X009 - VARIABLE ENGINEERING

4.10 CLIN X010 - PRODUCTION AND FABRICATION

5.0 GENERAL INFORMATION

5.1 PERFORMANCE OF SERVICES DURING CRISIS

5.2 SECURITY REQUIREMENTS

5.3 COMMON ACCESS CARD (CAC)

5.4 INSPECTION OF SERVICES CLAUSE

5.5 ANTHRAX INFORMATION

5.6 AGENCY AFFIRMATIVE PROCUREMENT PROGRAMS

5.7 PROCEDURE FOR INVOICING/PAYMENT AND RECEIPT/ACCEPTANCE

5.8 SAFETY REQUIREMENTS

5.9 VOLUNTARY PROTECTION PROGRAM (VPP)

5.10 PACKAGING, HANDLING, STORAGE AND TRANSPORTATION

5.11 PLACE OF PERFORMANCE

5.12 CONTRACTOR MANPOWER REPORTING

5.13 TRAFFICKING IN PERSONS

5.14 QUALITY

5.15 COUNTERFEIT ELECTRONIC PARTS

5.16 ENVIRONMENTAL MANAGEMENT SYSTEM (EMS)

5.17 ACCESS TO CONTRACTOR FACILITIES

5.18 HOLIDAYS AND FACILITY CLOSINGS

6.0 APPENDICES

1.0 DESCRIPTION OF SERVICES:

Services and support requirements for the AN/USQ-175 Communications Control Set (CCS), also referred to as the Roll-On Beyond Line of Sight Enhancement (ROBE) Tactical Information Gateway Set (TIGS). Requirements include Contract Data Requirements Lists (CDRL) deliverables, maintenance and repair on items, software image integration, and SME support at CONUS an OCONUS locations.

1.1 OBJECTIVE:

This Performance-Based Work Statement (PWS) outlines requirements for Contractor Logistics Support (CLS) and Services for the ROBE TIGS. CLS support shall include, but is not limited to, maintenance and repair, logistics, and in-plant engineering support. In addition to CLS, the Contractor shall provide services such as cybersecurity management activities and Subject Matter Expert (SME) support at Continental U.S. (CONUS) and OCONUS locations. This PWS also includes tasks required for development, modification, and production efforts in fulfillment of Government approved Modification Proposals (AF Form 1067) and/or Engineering Change Proposals (DD Form 1693) as directed by the Government Procuring Contracting Officer (PCO).

1.2 BENEFIT TO UNITED STATES AIR FORCE (USAF):

This acquisition will benefit the USAF by providing services and support for a non-integrated airborne tactical data link node flown onboard the KC-135 tanker aircraft. The ROBE system connects multiple dissimilar and incompatible tactical data networks and their participants with each other and battle directors in Joint Command & Control (C2) nodes. ROBE provides a Beyond Line of Sight (BLOS) capability, which is needed to permit transmission of C2 operational information across the theater of operations and to the Joint Air and Space Operations Center (JAOC). ROBE is essential for positive C2 to decrease the Find, Fix, Track, Target, Engage, and Assess (F2T2EA) decision cycle and thus, enhance Time Sensitive Targeting (TST) operations and the identification of non-targets in time to avoid fratricide.

1.3 BACKGROUND:

The ROBE system fulfills requirements described in the Unusual and Compelling Urgency for Roll On Beyond Line of Sight Memorandum signed March 2002 by AFC2ISRC/CC.

AFLCMC/WNY has overall system support responsibility and authority for the ROBE system.

2.0 SERVICES SUMMARY

This Services Summary (SS) identifies the critical performance objectives that will be monitored and the performance thresholds by which these objectives will be evaluated. Metrics regarding the evaluation of these performance objectives can be found in the Quality Assurance Surveillance Plan (QASP).

Performance Objective PWS Reference Performance Threshold

Quality/delivery of Contract Data Requirements List (CDRL) deliverables 4.6

CDRLs shall be delivered in accordance with guidelines established on DD Form 1423 Submittals. There shall be no more than one (1) rejection of each deliverable. There shall be no more than one (1) total rejection of deliverables per month. The Government will reject a deliverable if one (1) or more technical errors or five (5) 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 Government will reject the deliverable via a contracts letter. The rejected deliverable shall be corrected and resubmitted within five

(5) business days of notification of Government rejection.

Maintenance and repaired items 4.1.2 4.1.3 4.3.1

Contractor shall repair 100% of non- GFE reparable items to serviceable condition within 30 calendar days for ROBE LRUs and SRUs, from the date the system/item is received at the Contractor’s facility in San Diego, CA;

and 90 calendar days for subcontractor repaired items, from the date of shipment to subcontractor. The Contractor shall notify the Government within five (5) business days after receipt of delivery schedule if asset will not meet the scheduled delivery date and negotiate a revised delivery date. The late asset shall be delivered by the revised delivery date acceptable to the Government.

Performance Objective PWS Reference Performance Threshold

Software Image Integration

4.1.4 4.1.5

Delivered images shall be Security Technical Implementation Guide (STIG) compliant and free of Information Assurance Vulnerability Alert (IAVA) Category I findings. The Contractor shall notify the Government in writing within five (5) business days of discovery if IAVA CAT I findings cannot be remediated. The Contractor shall provide recommended course of action for compliance or remediation with initial notification. Delivered images shall have zero (0) operational deficiencies.

Subject Matter Expert Support

4.3 4.4

SMEs shall provide maintenance support to ensure, at a minimum, 95% operational availability of systems.

Contractor Manpower Reporting

5.12

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 FURNISHED PROPERTYAND SERVICES

3.1 Government Property

Government property will be provided in accordance with (IAW) the GFP attachment, attached to the contract/order. Reference Appendix B of the contract/order.

3.1.1 Contractor Responsibilities

The Contractor shall be responsible for Government property in its possession in accordance with the Federal Acquisition Regulation (FAR) and in the contract.

3.1.2 Reporting of Government Property

The Contractor shall create and maintain records of all Government property accountable to the contract, including Government-Furnished Property (GFP) and Contractor-Acquired Property (CAP) in accordance with FAR Part 35 and the contract.

3.1.2.1 Loss of Government Property

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

3.1.3 Return/Retention of Government Property

All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order unless the Government PCO directs the Contractor to retain the property for continued use under a successor contract. Retention of the property by the Contractor will require modification of both losing and gaining contracts in accordance with the FAR the contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the Government PCO.

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

The Government obtains title to CAP acquired or fabricated by the Contractor to perform tasks under the contract in accordance with the FAR and the contract. CAP shall be returned to the Government upon completion of the contract unless retained by the Contractor for continued use under a successor contract. If retained by the Contractor for a successor contract, CAP becomes GFP added to the successor contract by modification of both losing and gaining contracts in accordance with the FAR and the contract.

http://www.dcma.mil/aboutetools.cfm

3.2 Commercial Asset Visibility (CAVAF)

The Contractor shall report production using CAV-AF. The Contractor shall provide data on the actions conducted for each unit. The Contractor shall report as actions occur. The following metrics will be monitored: GFM In-Transit, Repairable GFM Accountability and Assets Not on Contract. If CAV-AF training is required, Contractor personnel may send an email to:

406scms.cav.af.ar@us.af.mil. (A001DI-MGMT-81634C, Commercial Asset Visibility Air Force (CAVAF) / Government Furnished Material Report).

3.3 Government Systems

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 Automated Information System (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) is/are closed.

3.4 Government Furnished Facilities

The Government will provide Contractor personnel access to Government facilities necessary to perform tasks under the contract/order. 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 in the contract.

3.5 Government Furnished Information (GFI)

The Government will provide Contractor personnel access to Government furnished information (GFI) necessary to perform tasks under the contract/order.

4.0 PROGRAM AND TECHNICAL REQUIREMENTS/CLIN STRUCTURE

This contract will have a Period of Performance (PoP) of five (5) years; one (1) twelve month base with four (4) twelve month option periods. These services will be performed at the contractor’s facility, subcontractor’s facilities, and Government sites as needed. The following fundamental technical and managenet requirements shall be provided in support of the ROBE system.

4.1 CLIN X001 – Sustaining Engineering

The Contractor shall provide program management services, logistics support, depot maintenance and repair, and system/functional engineering services for the ROBE system and associated ground support equipment. The Contractor shall conduct quick reaction sustainment activities, performance improvements, and analysis activities to include failure analysis for depot repair.

4.1.1 Program Management

The Contractor shall establish and implement a Program Management Office (PMO) function to manage performance, cost, schedule, and data delivery requirements of the contract. The Contractor shall ensure management operations include the following areas:

a) Program Planning and Control

b) Subcontractor Control

c) Financial Management

d) Data Management

e) Management and Accountability for Government Furnished Equipment, Material or Information

f) Risk Management

g) Material Management

h) Quality Assurance

The Contractor shall maintain a single point of contact within the PMO for all CLS requirements under this contract. The Contractor shall submit monthly status reports for all technical performance, cost, schedule, and material procurements required for this contract. A technical error includes logic errors, incorrect, or missing data. The monthly status report shall also address the following program elements:

• Management Review

• Technical Status

• Schedule on repairs (estimated down time and delivery)

• Material procurement (including any subcontractor supplied parts and materials)

• Status of drawing updates (as a result of internal and external CCBs)

• Action Item Review

The Contractor shall support program status reviews and technical interchange meetings (TIM) as required by the Government PMO. TIMs may be used to define or clarify new/modified system requirements and review progress on technical performance. The Contractor will incorporate TIMs with other program reviews where possible. The appropriate Contractor personnel will participate in the reviews and participate in discussions on their respective areas of responsibility as required. The Integrated Test Team (ITT) meetings will be considered a TIM.

(A002, DI-MGMT-81453A Data Accession List (DAL); A003, DI-MGMT-81991, Contract Status Report– Monthly Status Report)

4.1.2 Depot Maintenance and Repair

The Contractor shall provide maintenance and repair capabilities for the ROBE system. The Contractor shall maintain the necessary infrastructure to provide depot level maintenance and repair activities for the ROBE system. The Contractor shall provide services to analyze, troubleshoot, repair, overhaul and test ROBE items, assemblies and parts that are maintained or repaired under this contract. The contractor shall repair items to serviceable condition to the latest Government approved configuration. The Contractor shall not alter functional capabilities, hardware configuration, or aircraft interface (KC-135) without a Government approved Engineering Change Proposal (ECP). The Contractor shall report all maintenance actions performed, coordination or support required, and system reliability and maintainability figures to a part and serial number level (A004 DI-MGMT-80995A, Maintenance Service Report)

4.1.3 Turn Around Time (TAT)

Contractor repaired items shall be returned with a turnaround time (TAT) not more than 30 calendar days from the date the system/item is received at the Contractor’s facility. For subcontractor repaired LRUs and SRUs items shall be returned with a turnaround time (TAT) not more than 90 calendar days from shipment to subcontractor. Actual TAT is measured from Contractor’s induction of the repairable item to Ready for Issue (RFI) or serviceable condition.

TAT shall be suspended on a line replaceable unit (LRU) awaiting Government response to the Contractor, if the LRU is an Extraordinary Repair Action (ERA). 100% of items not approved as condemnation/Beyond Economical Repair (BER) shall be repaired and returned to serviceable condition within 30 calendar days for ROBE LRUs and SRUs and 90 calendar days for subcontractor repaired items. The Contractor shall notify the Government within five (5) business days after receipt of delivery schedule if the delivery of any asset will not meet the scheduled delivery date and negotiate a revised delivery date. The late asset shall be delivered by the revised delivery date acceptable to the Government.

4.1.4 Software Integration

Software Image Integration consists of tasks required in order to combine a computer operating system (OS), new or updated Government furnished tactical data link gateway software, ancillary utility application programs, and information assurance/cybersecurity patches in order to ensure that a system meets Defense of Department cybersecurity requirements. The contractor shall update the ROBE configuration items with the latest fielded GFI (software/firmware). New software and firmware shall successfully complete Acceptance Test procedures (ATP) testing prior to incorporation into the ROBE baseline configuration. The Contractor shall construct software image in accordance with National Institute of Standards & Technology Special Publications. The Contractor shall "lock down" and test the ROBE system with Defense Information Systems Agency (DISA) approved validation tools for compliance of the latest applicable DISA Security Technical Implementation Guides (STIGs), Security Requirements Guides (SRGs), Secuirty Content Automation Protocol (SCAP) Benchmarks, Security Readiness Review (SRR) (to include SCC), and applicable Security Checklists. The Contractor shall implement all applicable DISA STIGS available on or before the agreed upon baseline cutoff date.

The Contractor shall conduct automated network vulnerability scans, configuration assessments, application vulnerability scans, device configuration assessment, and network discovery. The Contractor shall document and provide the Government with all test and scan results. The contractor shall analyze all latent defects and attribute vulnerability categorization codes (e.g.

CAT I, CAT II, CAT III). The Contractor shall provide software images free from all CAT I findings and satisfactorily mitigate all CAT II findings to achieve and maintain the Authority to Operate (ATO). The ROBE system shall be patched on an annual basis. The Contractor shall plan for one (1) out-of-cycle software image for Information Assurance Vulnerability Alert (IAVA) update per year on an as required basis. Out-of-cycle software image update will be directed by the Government PCO as required. The contractor shall obtain Government approval for the inclusion of all mitigation that may result in an ECP. All deviations to settings will become findings and shall be documented and submitted to the Government. The Contractor shall document areas of compliance and/or non-compliance and provide documentation/artifacts to support remediation actions, risk mitigation plans and justification of non-compliance. The contractor shall update the Plan of Actions and Milestone (POA&M) for findings, remediations, deviations, and mitigation plans based on Cybersecurity Test and Evaluation (CT&E). The Contractor shall obtain Government approval for the inclusion of all third party software (e.g., open-source, freeware, mobile code, source code or binaries) proposed for use on ROBE prior to its use or integration. All software must meet the requirements defined in the DISA Application Security STIG. The Contractor shall conduct Formal Qualification Test (FQT) / Regression Test of created image against the approved ROBE baseline configuration. (A005, DI-ADMN-80925 Revisions to Existing Government Documents - POA&M

The Contractor shall deliver two (2) copies of the developed image on removable hard drives and one (1) copy on CD/DVD to the Government for validation testing. The Contractor shall provide software image in an auto start (or plug and play) format. Delivered images shall not degrade functionality of GFI or ROBE hardware. Delivered images shall be Security Technical

Implementation Guide (STIG) compliant and free of Information IAVA Category I findings. The Contractor shall notify the Government in writing within five (5) business days of discovery of IAVA CAT I findings that cannot be remediated. The Contractor shall provide recommended course of action for compliance or remediation with initial notification. Delivered images shall have zero (0) operational deficiencies. Out of cycle software images will be handle as an Over and Above requirement.

A006, DI-NDTI-80809B, Test/Inspection Report - ATP; A007, DI-MISC-80508B Technical Report – Study/Services - CT&E Artifacts, Scan results/remediation and/or mitigation plan)

4.1.5 Cybersecurity

The Contractor shall support the ROBE Information Systems Security Manager (ISSM) in completion of the cybersecurity accreditation process to assist in obtaining and maintaining an Authority to Operate (ATO) and Authority to Connect (ATC) from the Authorizing Official (AO). In the event the AO grants an ATO/ATC with conditions the Contractor shall support the Government ISSM on POA&M items until the ATO/ATC is granted. This involves providing system documentation and artifacts for input into the Authorization package.

In support of the cybersecurity accreditation process, the Contractor shall provide input and updates to the ROBE documentation. Documentation which includes, but is not limited to, the following:

a) System Security Plan

b) Security Concept of Operations

c) ROBE Contingency and Business Continuity Plan

d) ROBE unique incident response requirements to supplement the 340 EARS Incident

Response Plan

e) Hardware listing (baseline)

f) Software listing (baseline)

g) Ports and Protocol Services Matrix

h) Vulnerability Management Plan

(A005, DI-ADMN-80925 Revisions to Existing Government Documents – Cybersecurity Documentation)

The Contractor shall implement Cybersecurity controls as identified by the PMO's initial control baseline derived from the Categorization performed in accordance with DoDI 8510.01, Risk Management Framework for DoD Information Technology and Committee for National Security Systems (CNSS) 1253 and the RMF Knowledge Service, as well as specific controls identified by Attachment 5 of Appendix F of CNSS 1253, Classified Information Overlay.

(Ref. DoD 8510.01, RMF)

4.1.6 Configuration Management

The Contractor shall provide configuration management (CM) in support of hardware, software, lab, and documentation for the ROBE system. The Contractor shall ensure ROBE hardware, software, lab assets, and documentation are updated with Government approved configuration.

Configuration Management tasks include, but are not limited to, collection, review, tracking and archiving of Configuration Control Documents; Configuration Identification, Configuration Status Accounting, Contract Data Management, Deficiency Reporting and Investigating, maintenance of Product Data; support to Configuration Control Boards; and performance of Functional Configuration Audits and Physical Configuration Audits as required. The contractor shall track GFI software/firmware version changes via the Enhanced Technical Information Management System (ETIMS) to ensure ROBE configuration is maintained to updated configuration. The Contractor shall submit an ECP for all Class I changes to the baseline configuration. The Contractor shall notify the Government of all Class 2 changes, including all substitute parts changes, through Document Change Notices (DCN) within 30 calendar days.

Neither design nor functional capabilities shall be changed, modified or altered except when an Engineering Change Proposal (ECP) is submitted and approved by the Government PCO. Any changes made without written approval from the contracting agency shall require removal and replacement at the Contractor’s expense. ECPs generated and approved under a formal retrofit program may be implemented under this contract. (A008 DI-CMAN-80639D, Engineering Change Proposal)

4.1.7 Deficiency Reports (DR)

The Contractor shall investigate root causes of performance exception reports identified by the Government and provide recommendations for implementing solutions and/or system improvements. The Contractor shall initiate and track DRs and recommend appropriate corrective actions to the Government. The Contractor shall comply with TO 00-35D-54 (Deficiency Reporting, Investigation, and Reporting) for processing DRs for hardware and software deficiencies. The Contractor’s inspection system shall include the complete processing of Material Deficiency Reports (MDR) and Quality Deficiency Reports (QDR) in accordance with the AFMC Form 807 including evaluation of DR contract repair exhibits at no additional cost to the Government. Timely correction and reporting of defects found to prevent repeated discrepancies shall be an integral part of the Contractor’s quality procedures. Corrective action shall extend to the performance of all contractors and subcontractors. (A009, DI-ALSS-81534, Teardown Deficiency Report)

4.1.8 Diminishing Manufacturing Sources and Material Shortages (DMSMS)

The Contractor shall provide DMSMS on Maintenance Significant Items (MSIs) as required.

Contractor shall notify the Government of evolving obsolete part conditions and make recommendations including life of type (LOT) buy opportunities and any redesign that may ensue. Request for funding on all related issues will be directed through the Government PCO.

This support shall include proactive management of the component obsolescence, continuous assessment of component availability for customer systems and support for DMS component issues, alerting the Government of DMS issues specifically affecting the system and providing recommendations to the Government for resolving DMS issues based on cost, risk or other critical factors. The Contractor shall investigate Diminished Manufacturer Supplier and Vanished Vendor issues for system components. A technical status report shall be provided for DMSMS issues that may require replacement parts or re-design. Any DMSMS recommendations shall consider solution sets that minimize impact to form, fit, function, and interfaces of the system. (A007 DI-MISC-80508B, Technical Report–Study/Services – DMSMS Report)

4.1.9 Item Unique Identification (IUID)

The IUID Program requires each qualifying Air Force (AF) asset to be uniquely identified with a permanent marking that can sustain its information throughout the life of the asset. The program addresses two categories of assets—those already in the AF inventory and those currently under contract but not currently in the AF inventory. For assets under this contract, IUID requirements are specified in Defense Federal Acquisition Regulation Supplement (DFARS) 252-211.7003, Item Identification and Valuation, DFARS 211.274-2, Policy for item unique identification, and Department of Defense (DoD) 4100.39-M, Federal Logistics Information System (FLIS). All assets subject to marking shall be recorded in the DoD IUID Registry.

4.1.9.1 IUID Marking Plan

The Contractor’s IUID Marking Plan shall fully detail and document the strategy and scope to be used to meet MIL-STD-130N, DoD Standard Practice Identification Marking of US Military Property. The plan must be approved by the Government PCO prior to implementation.

(A010 DI-MGMT-81803, Item Unique Identification (IUID) Marking Plan)

4.1.9.2 IUID Marking Activity and Verification Report

The Contractor shall provide an IUID Marking Activity and Verification Report. A key attribute for the report is the Verification column which indicates pass/fail for each item’s Data Matrix Symbol Quality. (A011 DI-MGMT-81804A, Item Unique Identification (IUID) Marking Activity, Validation and Verification Report)

4.2 CLIN X002 - Spares

The Contractor shall provide the Government with a list of Maintenance Significant Items for the ROBE system. The identification of spares/parts shall be compatible with the configuration of the currently fielded system reflected in engineering drawings and technical manuals. The Contractor shall perform analysis and make recommendations to the Government for spares replenishment and for the repair of failed equipment. The Contractor shall purchase spares and repair materials required to sustain the ROBE system. (A012 DI-MGMT-81947A, Government Furnished Property Inventory and Forecasting Report)

4.3 CLIN X003 - Deployed Subject Matter Expert (SME) Support

SME support includes services external to the Contractor’s depot operations. SMEs shall be thoroughly trained in all aspects of Chairman of the Joint Chiefs of Staff Manual (CJCSM) 6120.01F (Joint Multi-Tactical Data Link Operating Procedures) to include both radio frequency and internet protocol applications. Subject Matter Expert services may be required to be performed in OCONUS locations that may or may not be within a Hazardous Duty area as defined through an Executive Order issued by the President of the United States. SMEs shall provide maintenance support to ensure, at a minimum, 95% operational availability of systems.

SMEs shall provide operational support required to accomplish pre- and post- mission analysis.

4.3.1 Deployed Maintenance and Operations Support

SMEs shall provide maintenance, repair, and operational support of the ROBE system and associated ground support equipment. Reliability, Maintainability, and Availability (RM&A) support shall be provided, to include, data collection, review, assessment, analysis, evaluation and improvement recommendations as required. SMEs will be responsible for cybersecurity activities required for control of the ROBE system at the deployed location. SMEs shall provide weekly status reports detailing maintenance activities performed, metrics for all ROBE missions flown, and ancillary issues which may cause program impacts. Impacts to operational availibilty caused by GFE items will be reported in the weekly status reports. The ROBE PMO will waive availability impacts caused by GFE availability on a case by case basis. These metrics shall include both planned and actual data link connectivity, any troubleshooting steps accomplished by aircrew members or SMEs, and a root cause analysis for all mission deviations. (A004 DI- MGMT-80995A, Maintenance Service Report (SME))

4.3.2 Training and Training Support

The Contractor shall provide just-in-time training to ROBE operators. The Aircrew/Mission Crew training shall be designed to facilitate training of boom operators. Contractor shall provide the minimum required training materials (student guides, charts and diagrams, etc.) to facilitate training conduct. (A013, DI-PSSS-81523C, Training Materials)

4.4 CLIN X004 - Exercise and Test Event Support (CONUS SME ONLY)

The Contractor shall support Government field training exercises and Government test events that require ROBE system participation. At a minimum, the Contractor shall participate in the following field exercises: Northern Edge (Alaska) every two (2) years (odd years), Sentry Aloha (Hawaii) annually, Valiant Shield (Guam) every two (2) years (even years), and Vigilant Shield (Canada) annually. The exercises listed are not all inclusive of potential exercise events that may occur within a year. Contingent upon funds available, the Government may sustititute events as prioritized by the ROBE user community.Each exercise is anticipated to have one (1), four (4) day planning conference and a two (2) week duration for the exercise event. Maintenance and repair, operations support (to include training of Government personnel), and reach back support for troubleshooting shall be provided during these exercises. The Contractor shall, as required, support test events. The Contractor shall anticipate a minimum of one recurring test event per year. Other test events will be negotiatied with tradeoffs within existing travel funds. Travel for all exercises and test events will be at the approval of the Government PCO.

4.5 CLIN X005 - Technical Publications

The Contractor shall provide services necessary for maintenance of, revisions to and updating of technical manuals, data, and other documentation pertaining to the ROBE system. The Contractor shall provide Technical orders and drawings in accordance with TMCR 86-01P.

4.5.1 Engineering Data

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

(A014 DI-SESS-81000E/T Product Drawings/Models and Associated Lists)

4.5.2 Engineering Data Guidance Conference

In association with Class I ECPs, the Contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 days after contract award.

The Conference shall be convened at a site and on a date agreed upon by the Government Contracting Officer and the Contractor. The Contractor shall prepare an agenda and record the minutes of the Guidance Conference. The Contractor shall address, discuss, and provide status on the following: [A015, DI-ADMN-81249B, Conference Agenda ; A016, DI-ADMN-81250A] Conference Minutes

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

b) TDP review requirements and schedules.

c) TDP delivery requirements and schedules.

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

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

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

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

h) Digital Technical Data Package (TDP) deliverables.

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

4.5.3 In-Process Review (IPR) of the TDP

The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50% percent completion point and shall be held, when possible, in conjunction with other reviews (i.e., PDR, CDR). The contractor shall notify AFLCMC/LZPEM a minimum of 30 days prior to the anticipated date of completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP.

The contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility.

(A015 DI-ADMN-81249A, Conference Agenda ; A016 DI-ADMN-81250A Conference Minutes)

4.5.4 Relationship of Contractor with Subcontractors/Vendors

The contractor shall levy on sub-contractors and sub-vendors the same requirements for Technical Data Packages (TDPs) as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.

4.5.5 Engineering Data Updates and Revisions

The contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/ developed/modified/produced and funded by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a) All engineering changes shall be incorporated into the applicable engineering data within 90 days after engineering release/Air Force concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

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

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

d) Revisions to existing engineering drawings/models and associated lists and other documentation to be included in the TDP for which the contractor is the current design activity shall result in the delivery of the entire revised document and associated data file.

For example, when a portion of a document is revised the entire document shall be delivered.

4.6 CLIN X006 – Contract Data Requirements List (CDRL)

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 month. The Government will reject a deliverable if one (1) or more technical errors or five (5) 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 five (5) business days of notification of Government rejection, in accordance with the associated DD Form 1423 instructions/requirements.

The Contractor shall deliver all CDRLs with no more than one (1) late submission(s) of deliverables per contract year. 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, DI-MGMT-81634C, Commercial Asset Visibility Air Force (CAVAF) / Government Furnished Material Report

• A002, DI-MGMT-81453A Data Accession List (DAL)

• A003, DI-MGMT-81991, Contract Status Report

• A004 DI-MGMT-80995A, Maintenance Service Report

• A005, DI-ADMN-80925 Revisions to Existing Government Documents

• A006, DI-NDTI-80809B, Test/Inspection Report

• A007, DI-MISC-80508B Technical Report – Study/Services

• A008, DI-CMAN-80639D, Engineering Change Proposal

• A009, DI-ALSS-81534, Teardown Deficiency Report

• A010, DI-MGMT-81803, Item Unique Identification (IUID) Marking Plan

• A011, DI-MGMT-81804A, Item Unique Identification (IUID) Marking Activity, Validation and Verification Report

• A012, DI-MGMT-81947A, Government Furnished Property Inventory and Forecasting

Report

• A013, DI-PSSS-81523C, Training Materials

• A014, DI-SESS-81000E/T, Product Drawings/Models and Associated Lists

• A015, DI-ADMN-81249A, Conference Agenda

• A016, DI-ADMN-81250A, Conference Minutes

• A017, DI-MGMT-81861A, Integrated Program Management Report

• A018, DI-SAFT-81563, Accident/Incident Report (Mishap Notification & Reporting)

• A019, DI-SAFT-80102C, Safety Assessment Report

• TMCR 86-01P

4.7 CLIN X007 - Travel

Contractor personnel may be required to travel to accomplish tasks or training as directed by the Government. The number of trips and personnel traveling shall be limited to the minimum number required to accomplish assigned tasks. Travel by Contractor personnel shall be conducted in accordance with FAR 31.205-46, Travel Costs. Travel will be reimbursed in accordance with the current Joint Travel Regulation (JTR) rates in effect at the time of travel.

Contractor should submit a request for travel to the COR and Contracting Officer 10 business days prior to travel to obtain approval for all Contractor personnel scheduled to travel.

Submissions received with less than 10 business days’ notice may not be approved by the Government and must include a requirement for why the 10 business day requirement could not be met.

4.8 CLIN X008 – Variable PMO

The Contractor shall estimate additional PMO required to manage taskings under CLIN X009 Variable Engineering as needed. This level of support shall be in accordance with Paragraph

4.1.1 of this PWS.

4.9 CLIN X009 - Variable Engineering

This paragraph provides a contingency for workload that is not specifically defined within the current line item structure. This CLIN will be used in conjunction with associated CLINS defined under the current CLS contract with scope to be defined with a separate Task Description/RFP.

4.9.1 Modifications

Such requirements include development of necessary ROBE configuration baseline changes associated with Modification Proposals (AF Form 1067). Upon receipt of an approved Block Cycle Change request from user with an approved (AF Form 1067, Modification Proposal) or Engineer Change Proposal (ECP) from contractor. Major changes to the ROBE configuration that are the results or Government approved Engineering Change Proposals, Urgent Operational Needs and Safety of Flight Issues that are outside the scope of this statement of work shall be accomplished as required. Engineering support will include out of cycle software images, hardware changes, integration, test and verification at the Contractor facility and external facilities as directed by the Government PCO.

4.9.2 Engineering Studies

Tasks shall include engineering support to conduct performance improvement investigations.

Study efforts to focus on requirements for system improvements utilizing current and or proposed future system configurations. Reports containing investigation results and performance improvement recommendations will be submitted to the Government at the conclusion of each investigation.

(A007, DI-MISC-80508B Technical Report – Study/Services – Engineering Studies)

4.10 CLIN X010 - Production and Fabrication

The Contractor shall acquire and/or fabricate materials and/or equipment to support ROBE hardware kit completion, delivery and installation associated with modification proposals and or ECPs. The contract shall establish and maintain an Integrated Master Schedule (IMS). The IMS shall be provided to the Government. Procurement lead time will be considered to ensure equipment and parts are purchased in a timely manner to meet the kit delivery and installation schedules. Completed kits will be delivered prior to installation. The Contractor shall support a partial Physical Configuration Audit conducted by the Government on a selected aircraft. The Contractor shall deliver for information a report documenting completion of the PCA. DCMA will conduct Government inspection of kits. (A007, DI-MISC-80508B Technical Report – Study/Services – PCA/FCA Reports; A017 DI-MGMT-81861A, Integrated Program Management Report)

5.0 GENERAL INFORMATION

5.1 Performance of Services During Crisis

In accordance with DFARS 252.237-7023, Continuation of Essential Contractor Services, essential contractor service is defined as a service provided by a firm or individual under contract to DoD to support mission-essential functions, such as support of vital systems, including ships owned, leased, or operated in support of military missions or roles at sea; associated support activities, including installation, garrison, and base support services; and similar services provided to foreign military sales customers under the Security Assistance Program. Services are essential if the effectiveness of defense systems or operations has the potential to be seriously impaired by the interruption of these services, as determined by the appropriate functional commander or civilian equivalent.

Mission-essential functions are defined as those organizational activities that must be performed under all circumstances to achieve DoD component missions or responsibilities, as determined by the appropriate functional commander or civilian equivalent. Failure to perform or sustain these functions would significantly affect DoD’s ability to provide vital services or exercise authority, direction, and control.

In accordance with DFARS 237.7602(a), Continuation of Essential Contractor Services / Policy, DFARS 252.237-7023(a)(2), and Air Force Instruction (AFI) 10-403, Deployment Planning and Execution, paragraph 1.9.1.33.2, 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

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 a minimum of a (Confidential, Secret) security clearance.

5.2.1 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) Program; and DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual.

5.2.2 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.3 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, controlled, maintained and operated in accordance with DoD 5220.22-M.

5.2.4 Security Clearance

The Contractor shall ensure applicable Contractor personnel have security clearances at the appropriate level (a minimum of Confidential, Secret) 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.5 Security Incidents and Violations

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.6 Security of Contractor System

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.3 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 AFFARS 5352.242-9001, Common Access Cards (CAC) for Contractor Personnel.

5.4 Inspection of Services Clause

In accordance with the following Inspection of Supplies/Services clauses, the Government reserves the right to inspect Contractor performance.

- FAR 52.246-3, Inspection of Supplies - Cost-Reimbursement

- FAR 52.246-4, Inspection of Services - Fixed-Price

- FAR 52.246-5, Inspection of Services - Cost-Reimbursement

- FAR 52.246-11, Higher-Level Contract…