Atch 1 - TDLOMO Draft PWS (18 Dec 23).pdf

PWS – TDLOMO Staff Support

FA489024R0004

Headquarters Air Combat Command (HQ ACC)

Directorate of Operations (A3)

Command, Control, Intelligence, Surveillance, and Reconnaissance Division (HQ A3C)

Performance Work Statement (PWS) for Tactical Data Link Operations and Management Organization (TDLOMO) Staff Support

Original Date: 1 June 2024

Record of Revisions

Change Note: yellow = changes, red = insertions, red strikethrough = deletions; text deleted by one revision will be removed from the subsequent revision and prior changes will be reset to black font.

Date Revision # Purpose 1 Jun 24 Original

Table of Contents

Section Title Page 1 Introduction 4

2 Scope 4

3 Objectives 5

4 Personnel 7

5 Deliverables 8

6 Government Furnished Property 10

7 Data 11

8 Other Direct Costs 11

9 Security 11

10 Transition 14

11 Administration Considerations 14

12 Quality 16

13 Environmental Safety and Health 16

1 INTRODUCTION

The Tactical Data Link Operations and Management Organization (TDLOMO), HQ ACC/A3CJ, provides Tactical Data Link (TDL) Operations and Management program support for ACC, as well as service support to the major commands (MAJCOMs) and Warfighting commands. A3CJ’s primary responsibility is to provide ACC/A3 with one organization to address cross platform TDL operations and any resulting issues from platform implementation, operational TDL employment, and data link management with the goal of fostering interoperability, cross-domain integration, and enhancing the digital kill chain. The TDLOMO operates the Air Force (AF) Link 16 Network Design Facility with primary responsibility for the design, delivery, and maintenance of Link 16 operational networks used by AF organizations worldwide for training, exercises, testing, and contingency operations. To support timely net-centric operations, A3CJ represents the AF as lead command for TDL operations throughout the four phases of the Link 16 network management process (planning, design, initiation, and operation).

2 SCOPE

2.1 Knowledge-Based Services

The purpose of this effort is to provide non-personal knowledge-based services in support of ACC Command, Control, Intelligence, Surveillance and Reconnaissance Division (A3C) supporting the TDLOMO within the A3CJ branch. The Contractor shall provide all personnel, equipment, supplies, transportation, supervision, and other items/services necessary to perform in accordance with (IAW) this Performance Work Statement (PWS), except as otherwise specified within the PWS (Section 6). The Contractor shall provide the number of qualified Full Time Equivalent (FTE) personnel (Appendix B) to perform the Level of Effort (LOE) required in this PWS (Sections 2 and 3) to accomplish this effort. The Contractor shall perform to the standards specified in the Services Summary (Appendix A). The Contractor’s output from these knowledge-based services shall take the form of information, advice, alternatives, analyses, evaluations, recommendations, scheduling, training, and other support as needed to complement the Government’s technical expertise.

2.2 General Personnel Support

In addition to the more detailed Objectives in Section 3, all Contractor personnel shall provide general office support as requested which may include, but is not limited to:

2.2.1 Participate in meetings, progress reviews, integrated teams, working groups, etc.

2.2.2 Draft, edit, and review a variety of material for correspondence and documentation, primarily using Microsoft Office applications.

2.2.3 Provide information management, records management, scheduling functions, meeting/conference support, etc.

2.2.4 Prepare briefing/training materials and present briefings/trainings.

2.2.5 Liaise and coordinate effectively with personnel at all levels inside and outside the organization.

2.2.6 Provide awareness of new and evolving requirements and recommendations to integrate them.

2.2.7 Provide support for planning, programming, tracking and financial execution.

2.3 Period of Performance

The period of performance (PoP) of this effort is anticipated to include one 12-month base year (BY), four 12-month option years (OYs), and a six-month extension.

3 OBJECTIVES

The Contractor shall perform the three primary tasks, and subtasks where applicable, identified in this section. A list of sample tasks is included with each of the primary tasks/subtasks to help identify the types of work to be accomplished, but the lists should not be interpreted as limiting the scope of performance to only the tasks identified in the lists.

3.1 Task 1 – Link 16 Network Designer

Tasks the Contractor shall perform include, but are not limited to:

3.1.1 Design Link 16 networks; determine connectivity requirements; and support integration of emerging and existing USAF Command and Control (C2), Intelligence, Surveillance, and Reconnaissance (ISR), non-C2 (fighter/bomber), and other platforms or systems into the multi-TDL architecture, with consideration for message delivery, network participation group, and necessary time slot considerations.

3.1.2 Provide Link 16 Network Design Development through the use of the Joint Network Design Aid (JNDA). Process shall include USAF-wide integration of platforms equipped with Joint Tactical Information Distribution System (JTIDS), Multi-Functional Information Distribution System (MIDS), MIDS Joint Tactical Radio System (MIDS-JTRS), and other emerging systems carrying the Link 16 wave form into exercises, daily training, testing, and real- world offensive and defensive contingency multi-link operations.

3.1.2.1 Provide Link 16 network development support, Link 16 network description documentation, platform load file generation, Link 16 network modification, Joint/Multi-National coordination, and Link 16 network design software technical support.

3.1.2.2 Ensure accurate development of the Link 16 network to meet AF, Joint, or Combined operational taskings in coordination with AF data link managers and IAW Military Standards (MIL STDs) and Standardization Agreement (STANAGs).

3.1.2.3 Interpret platform Interface Control Documents (ICD) and their application to Link 16 interfaces.

3.1.2.4 Provide life cycle maintenance of the AF Link 16 Network Library to include initialization data load (IDL) file modifications/releases, network description document updates, as needed to support operational use.

3.1.2.5 Coordinate direct support to multi-National network design facilities (to include training in support of Foreign Military Sales (FMS) case requests) through branch leadership.

3.1.3 Validate and propose user modifications to software used for Link 16 Network Design.

Evaluate software performance and assist in developing software problem change requests (SPCRs) as needed to maintain the viable usability of the JNDA software tool as user requirements and system specifications change.

3.1.4 Analyze JNDA software for proper functionality by applying characteristics of Time Division Multiple Access (TDMA) structures, time slot structures, time slot allocation, time slot access modes, stacked net applications, multi-net architectures, message packing structures, network participation groups, non-timeslot parameters, platform baseline files, Link 16 initialization data load file hex parameters, data relay assignments, and all J-series messages in order to evaluate accurate performance of the software.

3.2 Task 2 – Tactical Data Link Management Support

Tasks the Contractor shall perform include, but are not limited to:

3.2.1 Perform Tactical Data Link cross-platform operations support providing expertise in Link 16 network design and data link management.

3.2.2 Provide technical support for keymat distribution to AF and Joint organizations.

3.2.3 Validate TDL operational employment requirements including spectrum deconfliction, messages standards, and platform capabilities and limitations.

3.3 Task 3 – Tactical Data Link Operations Support

Tasks the Contractor shall perform include, but are not limited to:

3.3.1 Provide technical support for network design deliveries IAW the TDLOMO Link 16 Network Design Business Rules to include development of Network Description Documentation.

3.3.2 Provide technical support for topics related to Link 16 network operations, such as frequency spectrum support/coordination, design document distribution, and production of other materials required to operate Link 16 worldwide by US and supported foreign forces.

3.3.3 Provide staffing support for branch tasks to include staff package development for studies, analysis, and reviews.

3.3.4 Design and develop load files for the emerging Tactical Targeting Networking Technology (TTNT) capability used by AF platforms.

3.3.5 Support TTNT network development, TTNT network description documentation, platform load file generation, TTNT network modification, Joint coordination, and TTNT network design software technical support.

3.3.6 Utilize the Host Initialization File (HIF) design tool and, if required, draft trouble reports or new requirements.

4 PERSONNEL

The selection, hiring, reassignment of duties, transfer, supervision, management, control, and termination of Contractor employees in performance of this PWS shall be the responsibility and prerogative of the Contractor; subject to verification by the Government that the minimum KSAs (knowledge, skills, and abilities) identified in Appendix B of this PWS are met. The Contractor shall designate one individual as their Site Lead for this effort. The Site Lead shall be the primary focal point for the Contracting Officer’s Representative (COR) and will be responsible for the general administration and scheduling of Contractor personnel to ensure there are no mission gaps due to illness, leave, or other personnel contingencies so that impact to the Government is minimal.

The Contractor shall ensure all Contractor personnel performing on this effort conform to the policy of their assigned office regarding dress code, professional appearance, and general office behavior.

4.1 Qualifications

The Contractor shall ensure all personnel performing on this effort meet the minimum qualification requirements as identified by position in Appendix B. The Contractor shall provide the COR, Contracting Officer (CO) and Contract Manager (CM) with a qualification package for each employee proposed to perform on this effort. This applies to new personnel and any incumbent personnel who were not previously performing the same tasks. Qualification packages shall include: the task number, projected start date; detailed qualification summary or resume (with personal contact information redacted); background check and security clearance status; and any other information necessary for the Government to verify all required KSAs are being met.

Note: For SCI/SAP/SAR positions, after the Contractor has submitted a qualification package for Government review and the Contractor has made the decision to hire an individual, the Contractor shall provide a notice of impending hire to the COR to forward to the cognizant requirement owner and security office. The Contractor shall begin the email subject line with “CUI\\” (Controlled Unclassified Information) and encrypt the email (if sent from a DoD email) or password protect the attached files and email the password separately. The notice shall include the following attachments:

a. Completed SAP Nomination Package Pre-Screening Questionnaire, and

b. Selectee’s full name, date of birth, and social security number.

4.2 Level of Effort (LOE)

For each FTE position, the Level of Effort is considered met if that position is filled for that month, or, if there is a vacancy of the position during the month and the vacancy does not exceed 30 calendar days. Per FAR 16.207-2, payment is based on the effort expended rather than on the results achieved. Therefore, if a position is vacant and remains vacant for more than 30 calendar days, the contractor shall not invoice for that vacant position. For vacancies that cross two or more months and exceed 30 days, the contractor may invoice for that position the month where the vacancy first occurred; however, the contractor shall not invoice for the second month (or longer) since the vacancy exceeded 30 days.

4.3 Turnover

The Contractor shall act to minimize personnel turnover throughout the life of the contract. The Contractor shall provide written notice to the COR/CO/CM within three workdays of knowing an employee will no longer be supporting this effort. This written notice shall include the tasks impacted, the date and time when current support for the position will end, the reason the employee will no longer work on the effort, the anticipated replacement date, and what management action will be taken, if any, to ensure all tasks are supported for the duration.

4.4 Removal of Personnel

The CO may request the Contractor provide a resolution within 1 workday if a Contractor employee, or subcontractor employee, is identified as posing a risk to the health, safety, security, general well-being, or operational mission of the installation and its population.

5 DELIVERABLES

The Contractor shall provide effort deliverables in a format mutually agreed upon by the CO, COR and the Contractor. All deliverables will be provided in the timeframes agreed upon between the Contractor and the Government. The Contractor shall ensure final drafts of all deliverables are professional and free of major errors. Major errors (mistakes, inconsistencies, absences, etc.) are those which, when relied upon, could cause harm (personal injury, equipment damage, financial loss, etc.) to the Government.

5.1 Hiring Status Report (HSR)

The Contractor shall provide an HSR (using Attachment 6) every Friday starting with the first Friday after contract award, until all positions are filled. The HSR shall contain, at a minimum, the name, security clearance and adjudication date for each new hire, and the position each is to fill.

The final HSR, provided on the last Friday of the Transition In period (Section 10.1), shall contain all information requested in the attachment for all positions, including incumbent personnel to be retained, shall be validated and signed by the Contractor’s Facility Security Officer (FSO), and will become the Personnel Roster.

5.2 Personnel Roster

The Contractor shall maintain a current listing of all personnel performing on this effort (using Attachment 6). The Personnel Roster shall identify the Contractor’s Site Lead and on-site Security PoC and shall include all information requested in the attachment for all positions. The Personnel Roster shall be validated and signed by the Contractor’s FSO and provided to the Sponsoring Agency’s Security Manager. The Contractor shall provide an updated Personnel Roster whenever an employee's status changes, or employee(s) are added to or removed from this effort.

Note: The Government may require Contractor personnel to provide their DoD Electronic Data Interchange number or social security number for some transactions (i.e. verifying clearances, processing visitor requests, etc.).

5.3 Monthly Status Report

The Contractor shall provide monthly status reports for the duration of this effort. The report shall include:

a. Planned versus actual accomplishments – a by-task summary for the period, including at least one bullet per task showing how the Contractor met each task.

b. Anticipated activity – planned activities (e.g. tasks, travel, etc.) for the next period.

c. Other information – lessons learned, risks identified and analysis thereof, significant accomplishments, training completed, outstanding issues and recommendations, certifications or security clearances pending/expiring and mitigation plan, etc.

5.4 Trip Report

Following official travel, the Contractor shall prepare a trip report detailing the purpose of the trip, the individuals contacted, any agreements that were reached during the trip, or any other significant issues that were identified during the travel. The Contractor shall provide this trip report to the COR within five workdays after the completion of travel.

5.5 Quality Control Plan (QCP)

The Contractor shall develop, submit, and implement a Quality Control Plan to identify and prevent, or ensure non-recurrence of, defective services. The QCP shall be submitted to the CO for acceptance no later than 30 calendar days after notice of award. The Contractor shall update the Quality Control Plan when deficiencies in quality control are identified, and the revised QCP shall be submitted to the CO for acceptance no later than (NLT) five workdays after implementation by the Contractor. The QCP should include as a minimum:

a. Introduction and Purpose

b. Management Structure and Contact Information

c. Roles and Responsibilities of Contractor Personnel

d. Processes and Procedures to meet the Objectives of the PWS, including Appendix A

e. Internal Staffing Procedures

f. Subcontractor Relationships (if applicable)

g. Contractor (and subcontractor) Invoicing Processes

h. Process to address Government-issued Minor and Major Non-Conformances

i. Deliverables

j. Network Design Quality Assurance process/report for delivery of a network to the government. This process and quality of artifacts will describe how contractor will provide a final network using the government provided Business Rules.

5.6 Continuity Folders

The Contractor shall update/maintain current Continuity Folders for all routine work processes they perform. The Contractor shall update the Continuity Folders quarterly or within 30 days of a specific request made by the Government. Electronic Continuity Folders located on the official A3 SharePoint or similar website are authorized. Continuity Folders will include, but are not limited to, product examples, templates and for common correspondence, process guides, how-to guides, and other information determined to be vital to daily operations.

5.7 Reports, Studies, etc.

The Contractor shall prepare and provide Reports, Studies, Briefings and similar when requested by the A3 office being supported.

5.8 Quarterly Lapse Rate Report

The Contractor shall provide a Quarterly Lapse Rate Report (using Attachment 6) for each 3 months of completed contract performance.

5.9 Final Network Artifacts

The Contractor shall provide Final Network Artifacts as defined in the TDLOMO Business Rules.

Table 1 – Deliverables

Deliverables PWS Ref. Deliver to Due Date

Hiring Status Report 5.1 COR/CO/CM 1st Friday after award, then each Friday until all positions filled

Personnel Roster 5.2 COR NLT 2 workdays after an employee is added to, removed from, or changes positions within the effort

Monthly Status Report 5.3 COR/CO/CM NLT the 15th of each month Trip Reports 5.4 COR NLT 5 workdays after return Quality Control Plan 5.5 COR/CO/CM NLT 30 calendar days after award

Continuity Folders 5.6 Cognizant A3 personnel

Quarterly, or within 30 calendar days of request

Reports, Studies, etc. 5.7 Cognizant A3 personnel

As agreed upon by Government and Contractor

Quarterly Lapse Rate Report 5.8 COR/CO/CM Within 5 workdays after the end of each quarter of performance.

Final Network Artifacts 5.9 COR At Network Delivery, as defined in the

TDLOMO Business Rules.

6 GOVERNMENT FURNISHED PROPERTY (GFP)

6.1 Government Provided Documentation

The Government will provide access to relevant Government organizations, information, documentation, manuals, texts, briefs, and other materials as required and available.

6.2 Government Provided Equipment / Office Space / Office Supplies The Government shall provide office space, Local Area Network (LAN) connections, computer (hardware and software), unclassified and classified e-mail and internet access, and other standard office equipment and supplies necessary to support the Contractor in performance of this effort.

Laptops may be issued via hand receipt and shall be returned to the Government following completion of requirements for their use.

6.3 Loss, Damage, or Unauthorized Use

The Contractor shall establish and implement procedures to ensure all Government provided equipment is not lost, damaged, used by unauthorized persons, or connected to unauthorized external devices, physically or otherwise. The Contractor shall notify the CO/COR of any occurrences of loss, damage, or unauthorized use within two hours of discovery of occurrence.

7 DATA

The Government has unlimited rights, including intellectual property rights, to all deliverables of this effort to include technical data derived from the completion of briefings, papers, studies, or other Government-directed work.

8 OTHER DIRECT COSTS

8.1 Travel

The Contractor may be required to travel to attend meetings/events/exercises in support of the PWS Objectives/Tasks. All trips will be in accordance with regulatory requirements and actual travel shall be coordinated and pre-approved by the COR in writing. The Government will only reimburse allowable costs in accordance with FAR 31.205-46. The Contractor shall provide travel receipts to the COR as attachments in Wide Area Workflow (WAWF) when invoicing for travel related costs. Travel projections are subject to change based on Government requirements and travel cost reimbursements are limited to the not to exceed (NTE) cost estimate of the applicable contract line item.

Table 2 – Travel Estimate (per year of performance)

Origin Destination Number of Travelers Per Year

Number of Trips Per Traveler

Typical Number of Days Per Trip

JB Langley-Eustis, VA CONUS Locations 7 3 6 JB Langley-Eustis, VA OCONUS Locations 7 2 8 Note 1: This contract may require performance at locations listed as a Designated Operational Area in accordance with U.S Department of State (DoS) guidance. Contractor personnel performing overseas may be covered under the Status of Forces Agreement (SOFA) with the host nation where they are located; SOFA agreements can be found at www.state.gov.

Note 2: Local travel to attend meetings within the local city or base of assignment commuting vicinity (~40 miles) shall be considered a cost of doing business and shall not be separately reimbursed.

8.2 Defense Base Act Insurance

The Contractor shall ensure Defense Base Act (DBA) insurance coverage is provided for all Contractor employees working outside the United States in performance of this effort (see FAR 28.305). The Contractor shall itemize and invoice the cost of DBA insurance with other travel costs as applicable. DBA costs shall NOT be included in labor rates.

9 SECURITY

All Contractor personnel shall abide by all DoD, AF, and local rules, procedures, and standards of conduct while on any Government installation. This includes complying with installation traffic regulations, prohibitions on possession of weapons, AFMANs 16-1404 and 16-1406, etc.

9.1 DD254

A Department of Defense Contract Security Classification Specification (DD Form 254, Attachment 2) is required for access to classified material. The Contractor shall also perform in accordance with the Compliance with National Industrial Security Program Operating Manual (NISPOM—Part 117 of Title 32, Code of Federal Regulations).

http://www.state.gov/

9.2 Visitor Group Security Agreement (VGSA)

The Contractor may be required to enter into a long term VGSA with the host base Information Protection Office if contract performance is on base for 90 days or more. The VGSA shall outline how the Contractor integrates security requirements for contract operations with the AF to ensure effective and economical operation on the installation. The agreement should address:

9.2.1 Security support provided by the AF to the Contractor to include storage containers for classified information/material, use of base destruction facilities, classified reproduction facilities, use of base classified mail services, security badging, base visitor control, investigation of security incidents, base traffic regulations, the use of security forms, and inspections.

9.2.2 Security support requiring joint Air Force and Contractor coordination includes packaging classified information, mailing and receiving classified materials, implementing emergency procedures for protection of classified information, security checks, and internal security controls for protection of classified material and high value pilferable property.

9.3 Facility Clearance (FCL)

The Contractor shall possess a Top Secret FCL.

9.4 Security Clearances

Requirements for security clearance qualifications of the personnel performing on this PWS are detailed in Table 3. Contractor personnel shall have appropriate clearances prior to commencing work unless otherwise approved in writing by the CO. Personnel performing on this PWS require a favorably completed Tier 5 (T5) resulting in Top Secret (TS) access with Sensitive Compartmented Information (TS/SCI). Contractors will complete the customer-provided Intelligence Oversight training by customer requirements and will report any Questionable Intelligence Activity (QIA), Significant/Highly Sensitive Matter (S/HSM), and/or Federal Crimes IAW procedures established in DoD Directive 5148.13, Intelligence Oversight, and AFI 14-104, Intelligence Oversight. For contracts involving cryptographic matters in addition to DoDD and AFI reference, USSID 18, Legal Compliance and U.S. Persons Minimization Procedures applies.

The Contractor shall also complete visit requests for each individual who will be performing work on this effort in the Defense Information System for Security (DISS) prior to performance start unless otherwise approved in writing by the CO. The Contractor shall ensure that any teaming partners or subcontractors have the appropriate clearances prior to beginning performance.

9.5 Notification

The Contractor shall notify the Servicing Security Activity at each location, and the local unit through DISS, 30 calendar days prior to contract performance on base. In the remarks section in the DISS visit request add the contract number and the company FSO name and contact number.

9.6 On-site Security PoC

The Contractor shall appoint an on-site Security PoC. The Security PoC, in coordination with the sponsoring agency's Security Manager, shall ensure all contractor personnel are integrated into the sponsoring agencies Information Protection Program and receive initial and recurring security education training IAW DoD 5200.01, DoD Information Security Program Manual, and AFMAN 16-1404, Air Force Information Security Program.

9.7 Access and Identification Media

The Contractor shall ensure the Government-issued access and identification media (e.g. common access cards, etc.) required for contract performance are obtained for each employee performing on this effort, and for non-government owned vehicles if applicable. The Contractor shall implement controls to ensure all access and identification media issued to the Contractor by the Government are not lost, damaged, or used by unauthorized persons.

9.7.1 Retrieving Identification Media. The Contractor shall retrieve all identification media from any employee who ceases to perform work on this effort, for any reason, and provide the identification media to the COR within three workdays of them ceasing to perform.

9.7.2 Lost Identification Media. The Contractor shall immediately report to the COR/CO/CM any occurrences of lost identification media. The Government may, at its discretion, deduct the cost of replacing lost identification media from any payment due the Contractor.

9.7.3 Prohibited Use. The Contractor shall prohibit the use of Government-issued identification by any persons other than the individual for whom it was issued, and for any purpose other than performance of this contract unless otherwise authorized in writing by the CO.

9.8 Controlled Unclassified Information (CUI)

The Contractor shall comply with DoDI 5200.48, Controlled Unclassified Information. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding CUI.

9.9 Reporting Requirements

Contractor personnel shall report to an appropriate authority any information or circumstances of which they are aware that may pose a threat to the security of DoD or Contractor personnel or resources, or to classified or unclassified defense information. The Site Lead shall brief reporting requirements to all Contractor employees upon their initial on-base assignment.

9.10 Physical Security

The Contractor shall be responsible for safeguarding all Government property, information, and controlled forms provided for Contractor use. At the end of each work period, all Government facilities, equipment, and materials shall be secured.

9.11 Controlled/Restricted Areas

The Contractor shall implement local base procedures for entry to Air Force controlled/restricted areas where Contractor personnel will work. An AF Form 2586, Unescorted Entry Authorization Certificate, must be completed and signed by the sponsoring agencies Security Manager before a Restricted Area Badge will be issued.

9.12 Communications Security (COMSEC)

The Contractor may require access to COMSEC information. The DD 254 provides further instructions on safeguarding and managing COMSEC material.

9.13 Government Network Access

Contractor employees who require access to government IT systems to perform on this contract must receive system authorization through a government-approved DD Form 2875, which includes a favorable security investigation commensurate with their tasks. If a contractor employee cannot obtain an approved DD Form 2875 within 5 workdays of beginning performance the CO may direct their removal from performance on any tasks that require a DD Form 2875.

9.14 Non-government networks

Visitor groups are prohibited from establishing their own Information Technology (IT) systems/networks (Local Area Networks (LAN), Wide Area Networks (WAN), Cellular phone/USB Modem as WAN, Wi-Fi as WAN etc.).

9.15 Computer Security

The Contractor shall ensure all contractor personnel performing on this contract complete the IA training (e.g. Cyber Awareness) at https://public.cyber.mil/training/cyber-awareness-challenge/ prior to gaining access to ".mil" or ".smil"(Secure .mil) domains. The contractor shall maintain a record of course certificates to provide to the Government upon request.

10 TRANSITION

10.1 Transition In

The Government intends to award the contract approximately one month prior to when the awardee will assume responsibility for the PWS Objectives/Tasks. The Contractor may use this Transition In period for transition-related activities like coordinating interviews with current and prospective employees, identifying training requirements, familiarization with Government programs and personnel, and similar. The Transition In period will be considered part of the contract period of performance.

10.2 Transition Out

Prior to the end of the TO period of performance, the Contractor shall support a Transition Out period of up to one month. The Contractor shall remain responsible for providing the services required by this PWS for the Transition Out period. During the Transition Out period, the Contractor shall coordinate with the incoming contractor, the COR, and other cognizant Government personnel to ensure all programs, information, data, etc. is passed from the Contractor to the incoming contractor, so there is no break in customer or mission support. The Contractor shall disclose necessary personnel records for employees performing on this contract and allow the incoming contractor to conduct on-site or remote interviews with them. If these employees accept employment with the incoming contractor, the Contractor shall release them at a mutually agreeable date.

11 ADMINISTRATION CONSIDERATIONS

11.1 Place of Performance

Performance shall take place on Langley AFB, VA.

Note: This contract may require temporary performance at locations listed as a Designated Operational Area in accordance with U.S Department of State (DoS) guidance. If applicable, the Contractor shall include relevant allowable costs in their price proposal. Reference DoS Standardized Regulations (DSSR)-650; FAR subpart 25.3 and clause 52.225-19.

https://public.cyber.mil/training/cyber-awareness-challenge/

11.2 Duty Hours

Normal duty hours are 0800-1700, Monday through Friday, for the duration of the period of performance, except for Federal Holidays (https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/). Contractor personnel who travel on temporary assignment, if applicable, may be required to follow the schedule at the local place of performance and will be notified of temporary duty hours prior to departure. During Exercise support, the duty hours may shift, but total hours will not exceed nine hours per day. Changes to duty hours will be coordinated 48 hours in advance and shall conform to a schedule agreed upon by the Contractor and the COR.

11.3 Alternate Work Location

Telework is not authorized. However, alternate work locations may be permitted for this effort on a case-by-case basis with CO and COR approval. If the primary duty location is not available to Contractor personnel (i.e. office closed) then Contractor personnel may be directed to work from an alternate location. Working from an alternate location shall not involve working with or transporting classified information.

11.4 Contractor Identification

Each Contractor employee shall, while on duty, wear in plain view on the upper portion of their outer garment a durable (e.g. metal, plastic, etc.) identification badge to be furnished by the Contractor, containing the company name, employee name, and the section where the employee works. Contractor employees shall clearly identify themselves as "contractors" at all times, in all communications and representations (e.g. in meetings, conversations, phone calls, emails, etc.), whether with Government personnel, other contractor personnel, or with the public. Contractors with access to the base LAN or with a Government email address shall include the designation "ctr" in their email address and the signature block of their emails shall include their company’s name. The Contractor shall notify the COR if the "ctr" designation is not included in the email address for their personnel performing on this effort.

11.5 Base Shutdown / Inclement Weather

The Contractor shall follow guidance of the installation containing their place of performance to determine reporting schedules and locations during a base closure or inclement weather. The website for guidance regarding status of Langley AFB is http://www.jble.af.mil.

11.6 Family Days / Down Days

ACC Family and Down Days do not apply to Contractor personnel.

11.7 Kickoff Meeting

The Contractor shall attend a kickoff meeting specific to this effort within 14 calendar days of contract award. The Contractor shall coordinate the date, time, and location for the meeting with the COR/CO/CM at least three workdays prior to the kickoff.

11.8 CPARS

Performance history will be reported in the Contractor Performance Assessment Reporting System (CPARS) IAW FAR subpart 42.15.

http://www.jble.af.mil/

12 QUALITY

12.1 Quality Control

Quality control is the Contractor’s responsibility. The Contractor shall identify and control non-conformances through root cause analysis, corrective actions, preventive actions, etc. The Contractor shall maintain an organized record of non-conformances and corrective actions taken.

The Contractor shall respond to and correct all Government-identified non-conformances IAW time frames specified by the CO.

12.2 Quality Assurance

The Government will perform quality assurance surveillance and will evaluate the Contractor’s performance in accordance with this PWS and the Services Summary in Appendix A. This does not relieve the Contractor of the responsibility for quality control, nor does it limit the Government’s rights under any of the terms of the contract. The absence of any PWS or contract requirement from the Services Summary does not detract from its enforceability nor limit the rights or remedies of the Government under any other terms of this effort.

12.2.1 Access. The Contractor shall, on a non-interference basis, provide the CO or their authorized representative with access to all work areas, records, and data used in the performance of the contracted services within one workday of access being requested.

12.2.2 Minor Non-conformance. A minor non-conformance is a non-conformance which, by itself, does not adversely impact: the mission; the safety of personnel or equipment; or, program performance, schedule, or cost. A minor non-conformance does not increase risk to the Government. Minor non-conformances are typically low risk. Upon receipt of a non-conformance notification, the Contractor shall complete applicable sections and return it to the CO within time constraints directed by the CO in the notice.

12.2.3 Major Non-conformance. A major non-conformance is a non-conformance that does adversely impact (or has the potential to adversely impact): the mission; the safety of personnel and/or equipment; or, program performance, schedule, or cost. A major non-conformance increases risk to the Government. An example of increasing risk would be a significant number of recurring non-conformances, minor or major, which is an indication of inadequate quality control and lowers the Government’s confidence that the Contractor can provide quality services on time and within costs. The CO will communicate major non-conformances on a Corrective Action Request (CAR) form. Upon receipt of a CAR, the Contractor shall develop and provide a corrective action plan by the suspense date identified by the CAR. At a minimum, the Contractor’s corrective action plan will address:

a. Action taken (or to be taken and when) to fix the immediate non-conformance.

b. Findings from a root cause analysis of the problem.

c. Corrective action taken (or to be taken and when) to resolve the cause of the problem.

d. Actions to be taken to prevent recurrence of the non-conformance.

13 ENVIRONMENTAL SAFETY AND HEALTH

13.1 Environmental

The Contractor shall comply with all applicable Federal, State, and local environmental laws, regulations, and policies, including changes and amendments to the same made during the period of performance. The Contractor shall comply with the highest degree of environmental protection where any disagreements exist. For OCONUS work, if applicable, the Contractor shall also comply with all applicable host nation statutes and agreements. In addition, the Contractor shall comply with the DoD Overseas Environmental Baseline Guidance Document (OEBGD) or the Final Governing Standards (FGS) if applicable.

13.2 Safety and Health

The Contractor shall comply with all applicable Occupational Safety and Health Administration (OSHA) and Air Force Occupational Safety and Health (AFOSH) standards, technical orders, regulations and referenced publications, both inside and outside of the US. The Contractor shall comply with the highest degree of safety protection where any disagreements exist.

APPENDIX A: SERVICES SUMMARY

Table 4 – Services Summary

# Performance Objective

PWS

Reference Performance Ratings

Quality

Q1 Provide quality service IAW the PWS

Sections 2, 3, 5, and 12

1. Exceptional –

a. COR/CO receive multiple positive feedbacks from Mission Partners (cognizant A3 orgs) indicating how Contractor exceeded expectations; and

b. No Major Non-conformances and no unresolved Minor Non-conformances.

2. Very Good –

a. COR/CO receive positive feedback from

Mission Partners indicating how Contractor exceeded expectations; and

b. No Major Non-conformances and no unresolved Minor Non-conformances.

3. Satisfactory – No unresolved Major Non-conformances, no recurring Major Non-conformances, no more than one resolved Major Non-conformances, and no negative mission impact realized due to Non-conformances.

4. Marginal – No unresolved Major Non-conformances.

5. Unsatisfactory – Any unresolved Major Non-Conformance.

Schedule

S1

Provide timely, accurate deliverables and timely communication IAW the PWS

Sections 2, 3, 5, and 12

1. Exceptional –

a. All deliverables are timely and accurate on the first submission; and

b. Consistently responds to COR/CO and

Mission Partner communications within one workday.

2. Very Good –

a. All deliverables are timely and accurate, with no more than two exceptions to being accurate on first submission; and

b. Consistently responds to COR/CO and Mission Partner communications within one workday.

3. Satisfactory –

a. No more than 5 deliverables are untimely and all deliverables are accurate; and

b. Consistently responds to COR/CO and Mission Partner communications within two workdays.

4. Marginal –

a. More than five deliverables are untimely or inaccurate: or

b. Consistently takes more than two workdays to respond to COR/CO or Mission Partner communications.

5. Unsatisfactory –

a. More than ten deliverables are untimely or inaccurate: or

b. A pattern of being nonresponsive, or of delaying to similar effect, to COR/CO or Mission Partner communications.

Management

M1

Provide qualified personnel at performance start IAW the PWS

Sections 4 and 5.2, and Appendix B

Performance is acceptable when:

a. All positions have qualified personnel identified NLT the last workday of the Transition In period; and

b. All positions begin work on the first day of performance unless previously negotiated with the CO.

M2

Provide qualified personnel to resolve vacancies in a timely manner and maintain required security clearances IAW the

PWS

Sections 4, 5.2, 9, 11.3, Appendix B, and DD254

1. Exceptional –

a. All vacancies filled with qualified personnel within 30 calendar days;

b. No negative mission impact during vacancies; and

c. All required security clearances are kept current.

2. Very Good –

a. No more than one vacancy exceeding 30 calendar days;

b. No negative mission impact during vacancies; and

c. All required security clearances are kept current.

3. Satisfactory –

a. No more than two vacancies exceeding 30 calendar days;

b. No negative mission impact during vacancies; and

c. No negative mission impact due to lack/lapse of required security clearance(s).

4. Marginal –

a. Any number of vacancies longer than 30 calendar days having minor negative mission impact; or

b. Lack/lapse of required security clearance(s) having minor negative mission impact.

5. Unsatisfactory –

a. Any number of vacancies longer than 30 calendar days having major negative mission impact; or

b. Lack/lapse of required security clearance(s) having major negative mission impact or potential negative mission impact.

APPENDIX B: KNOWLEDGE, SKILLS, AND ABILITIES (KSAs)

Note: All positions require technical and conversational fluency in English speaking, reading, and writing. Unless otherwise indicated, “recent” means within the last 5 years.

Table 5 – KSAs

Task 4.1: Link 16 Network Designer # of FTEs KSA # Minimum Experience / Education / Security Requirements 5

4.1(a)

2 years of experience with JNDA and the AF employment of the JTIDS and MIDS and other Link 16 terminals, the sequence and timing of contingency and operational events and key strategic requirements in the context of tactical information exchanges applicable to current AF programs and weapons systems

OR

3 years of experience operating and maintaining a Link 16 terminal in crew positions such as:

CRC/ASOC Gateway - 1C5; AWACS – Communications Technician; Rivet Joint – Data Link Operator; or similar type position

4.1(b)

2 years of knowledge of the Link 16 network design process

OR

2 years of experience in the use of the JNDA software for development of Link 16 networks and the interoperability requirements for Link 16 operations in Joint and coalition TDL operations.

4.1(c) 2 years of operational experience in data link management and employment of US military C2, ISR, and fighter/bomber systems; technical understanding and one years’ experience with Link 16 message structures and terminal setup, crypto key usage, and operations.

4.1(d)

2 years of experience with the operations and sustainment of currently used Air Force tactical data link systems, their respective mission areas, their applicability in the conduct of combat air operations, including the ability to develop working hypothesis and theory to address current and future system requirements.

4.1(e)

2 years of experience working in a Headquarters Staff (NAF, MAJCOM, or above) environment producing decision documents, presenting briefings, building staff packages, coordinating with other staff personnel, working with other major command elements, interfacing with USAF staffs, and coordinating taskers using existing Task Management Tool (TMT) or other staff coordination standards

4.1(f) Proficient with Microsoft Office Suite (Word, Excel, Access, PowerPoint, and Outlook) Microsoft Teams, Microsoft SharePoint, and Adobe Acrobat software

4.1(g) Top Secret, SCI Eligible & NATO Secret Security Clearance Task 4.2: Tactical Data Link Management Support # of FTEs

KSA # Minimum Experience / Education / Security Requirements 1 4.2(a) 2 years of experience with AF employment of Link 16, contingency and operational events in the context of tactical information exchanges applicable to current AF programs and weapons systems.

4.2(b) 2 years of experience with the Link 16 network design process for development of Link 16 networks and the interoperability requirements for Link 16 in Joint and coalition TDL operations to be used in creation of Link 16 network description documentation

4.2(c) 2 years of operational experience in data link management and employment of USAF C2 and ISR, and fighter/bomber systems. Operational employment includes frequency assignments requirements, spectrum deconfliction and platform capabilities and limitations

4.2(d)

2 years of experience working in a Headquarters Staff (NAF, MAJCOM, or above) environment producing decision documents, presenting briefings, building staff packages, coordinating with other staff personnel, working with other major command elements, interfacing with USAF staffs, and coordinating taskers using existing Task Management Tool (TMT) or other staff coordination standards

4.2(e) Proficient with Microsoft Office Suite (Word, Excel, Access, PowerPoint, and Outlook) Microsoft Teams, Microsoft SharePoint, and Adobe Acrobat software

4.2(f) Top Secret, SCI Eligible & NATO Secret Security Clearance Task 4.3: Tactical Data Link Operations Support # of FTEs

KSA # Minimum Experience / Education / Security Requirements 1 4.3(a) 2 years of experience with AF employment of Link 16, contingency and operational events in the context of tactical information exchanges applicable to current AF programs and weapons systems.

4.3(b) 2 years of experience with the Link 16 network design process for development of Link 16 networks and the interoperability requirements for Link 16 in Joint and coalition TDL operations to be used in creation of Link 16 network description documentation

4.3(c) 2 years of operational experience in data link management and employment of USAF C2 and ISR, and fighter/bomber systems. Operational employment includes frequency assignments requirements, spectrum deconfliction and platform capabilities and limitations

4.3(d)

2 years of experience working in a Headquarters Staff (NAF, MAJCOM, or above) environment producing decision documents, presenting briefings, building staff packages, coordinating with other staff personnel, working with other major command elements, interfacing with USAF staffs, and coordinating taskers using existing Task Management Tool (TMT) or other staff coordination standards

4.3(e) Proficient with Microsoft Office Suite (Word, Excel, Access, PowerPoint, and Outlook) Microsoft Teams, Microsoft SharePoint, and Adobe Acrobat software

4.3(f) Top Secret, SCI Eligible & NATO Secret Security Clearance

APPENDIX C: FTE SUMMARY

Table 6 – FTE Summary

Task Core FTEs

Opt.

FTEs

Task 4.1: Link 16 Network Designer 5 0 Task 4.2: Tactical Data Link Management Support 1 0 Task 4.3: Tactical Data Link Operations Support 1 0

Total FTEs 7 0

APPENDIX E: ACRONYMS

Table 8 - Acronyms

Acronym Definition ACC Air Combat Command AF Air Force AFB Air Force Base AFI Air Force Instruction AFOSH Air Force Occupational Safety and Health AMIC Acquisition Management and Integration Center AMIC/DRQQ AMIC/Quality Assurance Division AMIC/PKA AMIC/Advisory and Assistance Services Division C2 Command and Control CAR Corrective Action Request CDRL Contract Data Requirements List CM Contract Manager CMRA Contract Manpower Reporting Application COMSEC Communications Security CONUS Continental United States COR Contracting Officer’s Representative CPARS Contractor Performance Assessment Reporting System CTR Contractor DMDC Defense Manpower Data Center DoD Department of Defense DSS Defense Security Service DSSR DoS Standardized Regulations FAR Federal Acquisition Regulation FGS Final Governing Standards FMS Foreign Military Sales FOIA Freedom of Information Act FOUO For Official Use Only FSO Facility Security Officer FTE Full Time Equivalent FY Fiscal Year GSA General Services Administration HQ Headquarters HQ ACC Headquarters Air Combat Command HSR Hiring Status Report IAW In Accordance With ICD Interface Control Documents IDIQ Indefinite Delivery/Indefinite Quantity IDL Initialization Data Load ISR Intelligence, Surveillance and Reconnaissance JBLE Joint Base Langley-Eustis JNDA Joint Network Design Aid

JPAS Joint Personnel Adjudication System JTIDS Joint Tactical Information Distribution System KSA Knowledge Skills and Abilities LAN Local Area Network MIDS Multi-Functional Information Distribution System MIDS-JTRS MIDS Joint Tactical Radio System MIL STDs Military Standards NAC National Agency Check NACI National Agency Check with Inquiries