Attachment 1 PWS Updated.pdf

Contract No.

1 | P a g e

EIELSON AIR FORCE BASE COUNTER-

SMALL UNCREWED AERIAL SYSTEM

RED TEAM ASSESSMENT

PERFORMANCE WORK STATEMENT (PWS)

PACAF/A4S & PACAF A5/8

17 September 2024

2 | P a g e

Summary of Changes

Date of Revision Description of Change

09/17/24 1.1.3, 1.2.3.3, 1.2.5.1 09/18/24 1.2.5.1, 1.3

3 | P a g e

Table of Contents

1.1 Background

1.1.1 Definitions

1.1.2 General

1.1.3 Mission

1.1.4 Purpose

1.1.5 Scope

1.2 Performance Requirements

1.3 Service Summary

1.4 Data Deliverables

1.5 Program Management

1.6 Quality

1.7 Environmental Safety and Health

1.8 Government Support and Services

1.9 Security

1.10 Other Pertinent Information

4 | P a g e

1.1 BACKGROUND.

1.1.1 Definitions of Relevant Terms, Organizations, and Equipment

a) Counter-Small Uncrewed Aerial System (C-sUAS). Air defense systems designed to detect, track, identify and/or defeat airborne threats from uncrewed aircraft.

b) Pacific Air Forces (PACAF). The Major Command (MAJCOM) located at Joint Base Pearl Harbor-Hickam (JBPH-H) that funds and provides mission requirements for the operational assessment of Anduril at Eielson Air Force Base.

c) PACAF/A4S. The Security Forces/Force Protection Division that falls within the Directorate of Logistics, Civil Engineering and Force Protection (A4) at Headquarters, Pacific Air Forces. PACAF/A4S is the office of primary responsibility (OPR) for C-sUAS within the PACAF area of responsibility (AOR).

d) Anduril Anvil. Privately held technology and innovation company that specializes in uncrewed systems, ground and aerial surveillance and air defense systems. Anduril’s Long-Range Sentry Tower-82 (LRST-82) with Anvil kinetic UAS interceptor is an air defense/C-sUAS platform present at Eielson Air Force Base under an operational assessment.

e) Negation of Improvised Non-State Joint Aerial System (Ninja). An Air Force Research Lab and Black River Systems produced C-sUAS package that provides passive radio frequency detection and non-kinetic electronic warfare engagement options in pursuit of air defense against small drones.

f) Dronebuster. Compact, lightweight, highly mobile handheld system that is manually aimed at airborne UAS threats and offers radio frequency and position, navigation and timing (PNT) jamming options.

1.1.2 General. In order to effectively and efficiently employ air defenses and C-sUAS, make knowledgeable acquisition, procurement and sustainment decisions, and inform research, development, test and evaluation (RDT&E) efforts, Department of Defense (DoD) leaders must have a comprehensive understanding of their capability gaps. Independent, deliberately planned, threat-informed and enemy-centric “red team” events are a highly effective method of assessing operational strengths and weaknesses.

1.1.3 Mission. This Performance Work Statement (PWS) facilitates an individual red team test and evaluation event at Eielson Air Force Base, on or before 1 Jan 2026, in order to assess the efficacy of air defense systems and identify capability gaps.

5 | P a g e

1.1.4 Purpose. The purpose of this contract is provide 354th Fighter Wing, Pacific Air Forces, Air Force and Department of Defense leaders with sufficient information and understanding of the operational environment, air defense strengths and weaknesses, and the end-user feedback necessary to make decisions regarding training, standard operating procedures (SOP), resourcing, capability development, acquisition and sustainment for C-sUAS.

1.1.5 Scope. The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision and other items necessary to perform C-sUAS red team services and capability assessments as described in the PWS and associated contract documents, except for those items specified in section 1.8 Government Support and Services.

The Contractor shall perform to the standards and acceptable quality levels identified in this PWS and associate contract documents.

1.1.5.1 Collaboration between the Government and Contractor for sUAS threat information, airspace deconfliction and approvals, local air traffic control (ATC) coordination, DoD and FAA sUAS exception to policies and flight waivers, C-sUAS system operation, scheduling, installation access, as well as other unforeseen events are unavoidable and expected. However, the Contractor shall ultimately be responsible for ensuring that all planning, approvals and legal authorities are completed within the prescribed timelines and quality specifications/requirements of this PWS. Both the Government and Contractor must act in good faith toward efforts to collaborate and share information in a manner appropriate to meet the requirements outlined in this PWS.

1.2 PERFORMANCE REQUIREMENTS.

This section specifies the Performance Objectives and Performance Elements for the contract.

The Contractor shall perform the following lines of effort in a cyclical manner to complete this project:

• Initial Planning

• Receive Necessary Authorities and Approvals for Test Event(s)

• Develop Campaign Plan and Prepare Required Materials

• Final Planning and Dry Run

• Red Team Event Execution and Data Collection

• Data Analysis and Publication of Conclusions, Lessons Learned, and After-Action Report

While the lines of effort above are generally listed in chronological order, they may be executed consecutively, where appropriate, to increase efficiency of time and resources.

6 | P a g e

1.2.1 INITIAL PLANNING.

1.2.1.1 Timeline, Expectations and Next Steps. The Contractor shall schedule and coordinate a post-award meeting (virtual telecon) NLT 5 business days after receipt of contract award with the meeting to be conducted NLT the third business day of the period of performance. The meeting will include an introduction between the Contractor personnel and Government personnel and provide the opportunity to discuss technical details, management, security and clearance issues, installation access, planning and execution timelines, assessment criteria, threat/intel information, approval actions, and other administrative or housekeeping items. At a minimum, the attendees shall include key Contractor personnel, key Government personnel, CO, and COR. The Contractor shall provide the following for the kickoff meeting:

a) Post-Award Meeting Presentation

b) Initial planning actions necessary to include material requirements, airspace deconfliction and approvals, sUAS flight waivers, scheduling considerations, environmental limitations (as applicable), and any other planning considerations deemed appropriate.

c) Communication plan and recommended tempo/rhythm for check-in meetings or syncs between Contractor and Government personnel to ensure consistent and efficient progress toward meeting timeline and quality goals.

d) Recommended measures of effectiveness (MoEs) and measures of performance (MoPs) for consideration and ultimate approval of key Government personnel. MoEs and MoPs will be tracked and will drive the data collection process at all red team events.

e) Meeting Minutes to include any action items resulting from the kickoff meeting.

1.2.2 RECEIVE NECESSARY AUTHORITIES AND APPROVALS FOR TEST EVENTS.

1.2.2.1 The Contractor, in coordination with and supported by key Government personnel where required, will pursue and receive the necessary local and/or federal airspace approvals and sUAS flight waivers in order to conduct red team events in accordance with local, state and federal regulations. The Contractor is responsible for ensuring that all required authorities and approvals have been received prior to the start of each scheduled test event and must do everything reasonably within it’s power to attain aforementioned approvals in a timeline that meets the intent and requirements of this PWS.

1.2.2.2 The Contractor will notify (in writing) key Government personnel of progress toward approvals and authorizations necessary for red team events. Each approval and/or authorization, once received, will be provided (in writing) to the Government for record.

7 | P a g e

1.2.2.3 To aid in continuity efforts and support future airspace deconfliction and sUAS waivers, the Contractor will maintain a list of notable points of contact (POCs), procedural notes, recommendations and lessons learned that will be documented in a single continuity product to be provided to the Government at the conclusion of the agreed upon period of performance.

1.2.3 DEVELOP CAMPAIGN PLAN AND PREPARE REQUIRED MATERIALS.

1.2.3.1 The Contractor will use intelligence and USINDOPACOM area of responsibility (AOR) threat data from open sources and as provided by key Government personnel to design a red air campaign plan that is modeled after likely enemy systems and tactics, techniques and procedures (TTPs). Unless waived, key Government personnel will approve the red air campaign plan, in writing, prior to the Contractor initiating steps to gather materials to build the red sUAS fleet.

The red air campaign plan must be submitted by Contractor to Government NLT 30 calendar days from start of the period of performance (PoP).

1.2.3.2 Working off the approved red air campaign plan, the Contractor will purchase, build and/or modify a minimum of 36 sUAS for red teaming. All sUAS, unless specified and approved by the Government, will be considered Government property and eligible for destructive testing (i.e. can be engaged via kinetic or non-kinetic means) at the discretion of key Government personnel in collaboration with the contractor.

1.2.3.3 At a minimum, the red air sUAS will include a variety of different unmanned aircraft “types”: 1) small quadcopter (0-20 lbs.), 2) medium quadcopter (21-55 lbs.), 3) large quadcopter (>55 lbs.), 4) small fixed-wing (size is discretionary), 5) medium fixed-wing (size is discretionary), 6) large fixed-wing (size is discretionary). Each individual aircraft “type” must have a representative mix of variations or modifications, to the extent the budget permits.

Modifications and variants can include, but are not limited to, primary material used for aircraft body & components (i.e. plastic vs. high density foam vs. carbon fiber vs. aluminum, etc.), frequency used for operation, radio frequency (RF) command and control (C2) link versus global positioning system (GPS) link, and more. The red air campaign plan will also account for various enemy-centric flight profiles that will challenge C-sUAS sensor capabilities. The destruction and mitigation of these systems is dependent on key Government personnel in combination with the contractor.

1.2.4 FINAL PLANNING AND DRY RUN.

1.2.4.1 The Contractor will host (via telecon) a final planning meeting with key Government personnel NLT 14 calendar days prior to each scheduled red team test event. The Contractor will be prepared to present the following items at the final planning meetings:

a) Approved red air campaign plan and how the red team event is designed to reflect intelligence and threat data provided via open source or the Government earlier in the planning process.

b) Review all airspace approvals and sUAS flight waivers necessary for red team event(s).

8 | P a g e

c) Outline the planned schedule of events at no less than 2-hour increments, to include roles and responsibilities, contingency and emergency plans, safety and risk assessments, and anticipated or expected issues or concerns.

d) Provide overview of approved measures of effectiveness (MoEs) and measures of performance (MoPs).

e) “Dry-run” or rehearsal of concept (ROC) drills will be accomplished at the discretion of key Government personnel with inputs from the Contractor, local airspace controllers and wing, group and squadron leadership at Eielson Air Force Base.

1.2.5 RED TEAM EVENT EXECUTION AND DATA COLLECTION.

1.2.5.1 Unless a deviation is approved by the Government for operational or airspace deconfliction reasons, the baseline standard for a red team event will be 3x pilots flying up to three (3) sUAS at a time for a total of 40 hours flight campaign with up to an additional 40 hours of preparation time (aircraft modification, etc). In order to account for shift work as well as hours of darkness and daylight, the default work hours during red team events will be 1100-2300 (may be flexible as conditions permit). If mission does not allow or airspace approvals or are not feasible, the total of 80 hours for each red team event will be distributed as reasonably agreed to by all parties.

1.2.5.2 The Contractor will be responsible for data collection efforts appropriate to provide data of sufficient value toward the assessment of approved MoEs and MoPs.

1.2.6 DATA ANALYSIS AND PUBLICATION OF CONCLUSIONS, LESSONS LEARNED

AND AFTER-ACTION REPORT.

1.2.6.1 Within 7 calendar days of a red team event, the Contractor will provide the Government with a preliminary after-action report (AAR) that will include, at a minimum:

a) Dates, times, locations, name/contact info of key personnel involved in the event. In addition, an overview of MoEs and MoPs assessed to establish a clear methodology of evaluation.

b) Clear performance trends (strengths, weaknesses, neutral), summarized or significant pilot feedback, summarized or significant C-sUAS operator feedback.

c) General event successes and areas of improvement.

d) Thoughts, recommendations or ideas for consideration in future red team events.

1.2.6.2 Within 30 calendar days of each red team event, the Contractor will provide the Government with a final AAR that will include, at a minimum (and in addition to the items listed in paragraph 1.2.6.1 above):

9 | P a g e

a) Detailed flight profile information, broken down by sUAS “type” and “variant”.

Graphics, tables and charts should be used where they are value-added.

b) Success and failure statistics broken down by C-sUAS platform (i.e. Ninja, Dronebuster, Anduril) regarding detect, track, identify, and defeat actions (as applicable or relevant).

These statistics will correspond to and be broken down by sUAS “type” and “variant”.

Graphics, tables and charts should be used where they are value-added.

c) Information gaps or assessed blind spots in the data that may mislead or misinform analysis efforts or attempts to reach conclusions.

d) Areas that must be assessed or evaluated in the future in order to reach more informed conclusions and gain a better understanding of capability gaps.

e) Expanded and detailed list of significant trends or conclusions that can reasonably be reached from the red team event individually, or through the consolidation and collective assessment of findings from multiple red team events.

1.3 SERVICE SUMMARY.

Performance Objective PWS Reference Performance Threshold

Initial Planning 1.2.1

The Contractor shall schedule a virtual post-award initial planning meeting, IAW timelines listed in section 1.2.1, to cover initial planning actions and will provide written meeting minutes to Government.

Receive Necessary Authorities and

Approvals for Test Event(s)

1.2.2

The Contractor, supported as needed by Government, will seek out and receive all necessary airspace and sUAS flight authorizations as required by local, state and federal regulations. Written notification and proof of approvals must be submitted to Government.

Develop Campaign Plan and Prepare Required

Materials 1.2.3

Utilizing open-source and Government-provided intelligence, Contractor will develop a threat-informed red air campaign plan. Upon approval, Contractor will purchase, build and/or modify a minimum of 36 target sUAS for red team event(s).

Final Planning and Dry Run 1.2.4

The Contractor will host a virtual final planning meeting NLT 14 days prior to each red team event to review and provide details for items listed in section

1.2.4. A dry-run or ROC may be accomplished at the

discretion of key Government personnel. Final approval for each red team event will be provided in writing by the Government.

10 | P a g e

Red Team Event Execution and Data

Collection 1.2.5

Unless a deviation or exception is approved by the Government, each red team event will consist of 3x pilots flying up to three (3) sUAS at a time for a total of 40 flight campaign hours with up to an additional 40 hours of preparation time (80 total hours).

Data Analysis and Publication of

Conclusions, Lessons Learned and After-

Action Report

1.2.6

The Contractor will provide, in writing, a preliminary report to Government within 7 days of each red team event and, within 30 days of each test event, a final AAR evaluating all approved MoEs and MoPs as well as requirements listed in section 1.2.6.

1.4 DATA DELIVERABLES.

1.4.1 Format. The Contractor shall deliver all electronic deliverables by email as well as placing in the Contracting Officer Representative’s (COR) designated repository. Identified below are the required electronic formats, which must be compatible with AF’s software licenses.

Text Microsoft Word Spreadsheets Microsoft Excel Briefings Microsoft PowerPoint Drawings Computer Aided Design Software Schedules Microsoft Excel

1.4.2 Products. The following schedule of milestones will be used by the COR to monitor timely progress under this contract. The Contractor shall provide the following listed deliverables:

Deliverable Section Required Completion Date Initial Planning Meeting Scheduled 1.2.1.1 NLT 5 business days after contract award Initial Planning Meeting Minutes 1.2.1.1 NLT third day of the period of performance All required airspace & sUAS approvals 1.2.2.1 Prior to each scheduled red team event Continuity documentation 1.2.2.3 At conclusion of period of performance Red air campaign plan 1.2.3.1 NLT 30 calendar days from start of PoP

11 | P a g e

Final Planning Meeting 1.2.4.1 NLT 14 calendar days prior to each test event Dry run or rehearsal of concept 1.2.4.1.e As applicable, prior to each test event Preliminary after-action report (AAR) 1.2.6.1 NLT 7 calendar days after each test event Final after-action report (AAR) 1.2.6.2 NLT 30 calendar days after each test event Quality Control Plan (QCP) 1.6.2 NLT 30 calendar days after contract award

1.5 PROGRAM MANAGEMENT

1.5.1 General Requirements. At a minimum, the Contractor shall:

1.5.1.1 Provide a primary point of contact who is responsible for program management of the red team contract and who will work with the Government Program Manager (PACAF/A4S) on all issues.

1.5.1.2 Immediately notify the contracting officer (CO) of direction that is considered outside the scope of PWS prior to performing the work.

1.5.1.3 Identify, document, and notify the COR of actual or potential Contractor program management problems and deficiencies and report unresolved problems to the CO and COR.

Contractor shall also perform corrective actions for all identified Contractor program management problems and deficiencies.

1.5.2 Schedule. Contractor shall adhere to all scheduled timelines, milestones, delivery schedules, and administrative requirements to include scheduled on-time delivery of reports, data products, billing invoices, staffing of personnel, and action item completion.

1.5.3 Contractor Furnished Supplies and Services. Except for those items or services specifically stated in this PWS as Government furnished, Contractor shall furnish the required supplies and services needed to perform the contract.

1.5.4 Duty hours. Normal workdays for administrative and event planning actions are Monday through Friday from 0730 to 1630 local time. Normal workdays for test events, unless otherwise coordinated, are Monday through Friday from 1100-2300.

1.5.5 Recognized Holidays. The following Federal holidays are observed under this contract:

• New Year’s Day • Labor Day

• Martin Luther King Jr.’s Birthday • Columbus Day

• Presidents’ Day • Veterans Day

• Memorial Day • Thanksgiving Day

• Independence Day • Christmas Day

*Any of the above holidays falling on a Saturday shall be observed on the preceding Friday.

Holidays falling on a Sunday shall be observed on the following Monday.

12 | P a g e

1.5.6 Place of Performance. All planning and administrative actions can be performed in a location of the Contractors choosing. All test event actions will take place on or within the immediate vicinity of:

a) 354th Fighter Wing, Eielson Air Force Base, Alaska

1.5.7 Conflicts of Interest. Contractor shall include in its proposal any actual or potential conflicts of interest that may arise under the performance of its contract. In addition, Contractor shall immediately notify the CO, if during the performance of the contract, Contractor becomes aware of any circumstance where its personnel or sub-contractors may have a conflict of interest. In such circumstances, Contractor shall propose a Conflict of Interest mitigation plan offering suitable processes for alleviating situations that lead to actual and/or potential conflict of interest situations, as well as situations that give the appearance of a conflict of interest.

Contractor is also cautioned that there may be instances where actions it takes under this contract may preclude it from proposing on request for proposals in support of the AF mission or other related activities of the AF.

1.5.8 Financial Management.

1.5.8.1 Cost Control. Contractor shall demonstrate effectiveness in forecasting, managing, and controlling contract costs. Contractor shall provide total accountability, accuracy, disclosure, control, forecasting, estimating, and overall management of material costs.

1.5.8.2 Invoicing. Invoices shall be provided within 30 days after the end of billing period or contract line item number (CLIN). Invoices shall be processed via Wide Area Work Flow (WAWF). Submit WAWF notification e-mails to the COR and CO.

1.5.8.3 Purchasing. Contractor shall not purchase any material billable to the Government without prior written consent of the CO.

1.6 QUALITY.

1.6.1 Quality Control. Contractor shall develop, implement, and maintain a comprehensive inspection system that assures compliance with all requirements of this contract and IAW FAR Part 46.

1.6.2 Quality Control Plan (QCP). The Contractor shall develop a contract QCP and maintain an effective QCP to ensure services are performed IAW this contract. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Contractor shall provide the QCP to the CO and COR NLT 30 calendar days after award of the contract. Contractor shall also provide updated versions within 14 days of when any updated QCP is implemented. At a minimum, the QCP shall demonstrate Contractor’s ability to

13 | P a g e control task processes, invoicing and deliverables, as well as accomplish performance objectives and requirements listed within this PWS.

1.6.3 Performance Evaluation. Contractor performance outputs are subject to surveillance by a Government COR to ensure compliance with this PWS. At a minimum, the Contractor shall:

a) Access. Allow CORs access to work areas and data, provide support, and not interfere with the CORs, state, federal, and other designated personnel in the performance of their official duties. Contractor shall permit the CO or his/her authorized representative access to all records, and data used in the performance of the contracted services. Access shall be provided as soon as possible, but not to exceed one business day after receipt of a written request for access from the CO

b) Non-conformances. Take immediate remedial and corrective actions for all identified non-conformances. Correct all Government-identified problems and deficiencies IAW time frames specified by CO and PWS.

c) Corrective Action Request (CAR). Upon receipt of a CAR, complete applicable sections of the CAR (or automated equivalent) and return it to the CO and COR within time constraints issued by the CO in the CAR. At a minimum, provide corrective and preventive action plans that address why the performance threshold was not met (root cause), how performance shall be returned to acceptable levels (corrective action), and how recurrence of the cause shall be prevented in the future (preventive action)

1.7 ENVIRONMENTAL SAFETY AND HEALTH.

1.7.1 Environmental Requirements. Contractor shall comply with all applicable federal, state and local environmental statutes, instructions, manuals, handbooks, regulations, guidance, policy letters and rules (including all changes and amendments) and all Presidential Executive Orders, in effect on the date of issuance of each task. Contractor shall comply with the highest degree of environmental protection where any disagreements exist.

1.7.2 Safety and Health Requirements. 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 within and outside of the US. Contractor shall comply with the highest degree of safety protection where any disagreements exist.

1.8 GOVERNMENT SUPPORT AND SERVICES.

1.8.1 Contracting Officer Representatives (COR). The CO will appoint a COR in writing. The COR will receive, for the Government, all work called for by the contract and will represent the CO in the technical phases of the work. The COR will provide no supervisory or instructional assistance to Contractor personnel. The COR is not authorized to change any of the terms and conditions, scope, schedule, and price of the contract. Only the CO will make changes in the scope of work by properly executed modifications to the contract.

14 | P a g e

1.8.3 Place of Inspection and Acceptance. Inspection and acceptance of all work performance, reports and other deliverables under this contract shall be performed at duty locations listed in Sections 1.5.6.

1.8.4 Scope of Inspection. All deliverables will be inspected for content, completeness, accuracy and conformance to contract requirements by the COR. Inspection may include validation of information or software by automated tools, testing or inspections of the deliverables, as specified in the contract. The scope and nature of this inspection will be sufficiently comprehensive to ensure the completeness, quality and adequacy of all deliverables.

1.8.5 Government Property and Services. The Government will provide to or assist the Contractor with the following actions:

1.8.5.1 Installation Access. Contractor personnel requiring installation access to Eielson Air Force Base for the performance of official duties will be processed and granted visitor access IAW 354th Fighter Wing and 354th Security Forces Squadron policy.

1.8.5.2 Red Threat Intelligence. Within 7 calendar days of start of the period of performance, Government will provide Contractor with access to any classified intelligence necessary for Red Air Campaign Plan preparation. If the Government chooses not to provide classified sUAS threat information, the Contractor will build the Red Air Campaign Plan to align with provided Government direction and intent, as well as available open source information.

1.8.5.2 Red Team Event Authorities and Approvals. The Government will coordinate with and assist the Contractor, as necessary and applicable, to submit and receive required airspace and sUAS waiver authorities to operate and conduct each red team event. This coordination includes, but is not strictly limited to, local airspace deconfliction and sUAS flight window designation with FAA, 354th Operations Support Squadron and local air traffic control, waiver, risk assessment or concept of operations (CONOPS) processing at the Wing, Major Command (MAJCOM), or Air Force (HAF) level.

1.8.5.3 Guidance and Approvals. The Government will provide the Contractor with general intent and guidance at the initial planning meeting to assist with red air campaign planning, measure of effectiveness (MoE) and measure of performance (MoP) development and scheduling coordination. The Government COR will also act as a liaison between the Contractor and other Department of Defense, Pacific Air Forces (PACAF) and 354th Fighter Wing organizations and POCs in the pursuit of successful and effective red team events.

1.9 SECURITY.

1.9.1 Physical Security. Contractor shall provide information and documentation to comply with the requirements of Defense Department (DD) Form 254, DoD Contract Security Classification Specification.

1.9.2 Clearance. All Contractor personnel with any involvement in or access to classified

15 | P a g e material provided for Red Air Campaign Plan development must possess a Security Clearance granted by the DoD and their parent Contractor facility must also have the appropriate Facility Clearance IAW DoD National Industrial Security Program (NISPOM) 5220.22R prior to performing work on any classified Government systems or products. Contractor shall comply with all appropriate provisions of applicable security regulations. Specific security requirements are identified in the DD Form 254, DoD Contract Security Classification Specification. For access to unclassified AF networks only, Contractor must, at minimum, have a completed verifiable National Agency Check with Written Inquiries (NACI) and current completed background check. Contractor shall establish and maintain procedures to ensure this security level is maintained at all times.

1.9.3 Access to Government Facilities with Controlled or Restricted Areas. Contractor must comply with security regulations imposed by the installation commander and/or the agency responsible for the project location. Due to specific mission requirements inherent in the nature of controlled or restricted areas, the Government may direct Contractor to leave the controlled or restricted areas at any given time.

1.9.4 Safeguarding Classified or Unclassified Information. Contractor shall meet Air Force standards for storing, processing, and handling classified information and systems, IAW AFI 16- 1404, Information Security Program. Additionally, all resources (e.g. maps, publications/ instructions, photos) provided by the Government to assist Contractor in the performance of the contract will be surrendered upon termination of employment or the end of the contract performance period.

1.10 OTHER PERTINENT INFORMATION.

1.10.1 Non-Disclosure Agreements. To safeguard information, Contractor shall enter into non-disclosure agreements with the responsible local security manager. A copy of all NDAs shall be provided to the COR and CO at request.

1.10.2 Non-personal Services. This contract is a “non-personal services contract” as defined in FAR 37.101. It is, therefore, understood and agreed that Contractor and/or Contractor’s employees: (1) shall perform the services specified herein as independent Contractors, not as employees of the Government; (2) shall be responsible for their own management and administration of the work required and bear sole responsibility for complying with any and all technical, schedule, or financial requirements or constraints associated with performance of this contract; (3) shall be free from supervision or control by any Government employee with respect to the manner or method or performance of the services specified; but (4) shall, pursuant to the Government’s right and obligation to inspect, accept or reject the work, comply with such general direction of the CO, or the duly authorized representative of the CO as is necessary to ensure accomplishment of the contract objectives.