Attachment 2 - PWS DSS III Draft 5 Feb 2025.pdf

PERFORMANCE WORK STATEMENT FOR

PILOT TRAINING TRANSFORMATION

DEVICE SUPPORT SERVICES III

Version: 5 Feb 25

1.0. EXECUTIVE SUMMARY.

The Defense Innovation Unit (DIU), entered into a 10 U.S.C. 2371b Prototype Other Transaction (OT) agreement for Commercial Solutions Opening (CSO) Area of Interest (AOI): Pilot Training Transformation (PTT). DIU, located in Mountain View, California, was established to serve as a bridge between those in the U.S. military executing on some of our nation’s toughest national security challenges and companies operating at the cutting edge of technology. DIU continuously iterates on how to best identify and prototype novel innovations through sources traditionally not available to the Department of Defense (DoD), with the goal of accelerating the transfer of this technology into the hands of the Warfighter. PTT sought a prototype solution to streamline pilot training utilizing state-of-the-art commercial solutions. Focus areas include software solutions for the user portal, simulation environment, artificially intelligent (AI) flight instructor, Learning Management System (LMS), and on- premises network and data architecture.

2.0. PURPOSE.

The purpose of this requirement is to maintain and support PTT’s device solutions based on state-of-the-art commercial simulation environments, hardware solutions for the cockpit simulation environment, and ancillary software elements.

3.0. SCOPE.

The Contractor shall provide all services and equipment necessary to install, maintain, and support new and existing PTT devices. Devices currently fit into the following classifications: common Immersive Training Device (cITD), enhanced Immersive Training Devices (eITD), Helicopter Immersive Training Device (HITD), and TH-1H Multi-Place Mixed Reality (MPMR) device.

Any new classifications will need to be defined and evaluated prior to inclusion in this scope.

The Contractor shall support 142 ITDs and up to 30 Instructor Operating Stations (IOS) at the following locations: Joint Base San Antonio (JBSA) – Randolph, TX; Columbus Air Force Base (AFB), MS; Laughlin AFB, TX; Vance AFB, OK, Sheppard AFB, TX; and Fort Novosel, AL.

The four MPMR immersive aircrew training devices will require support starting 60 days prior to the forecasted initial class start date. The Contractor shall maintain a common software interface to integrate current and future PTT software and hardware components as required by program goals, hardware solutions for the cockpit simulation environment, and on-premises network and data architecture hardware and support, as appropriate for deployed training systems.

4.0. DESCRIPTION OF SERVICES.

4.1 The Contractor shall maintain and support third-party simulation environment components that shall abstract all bi-directional communication with PTT ecosystem component micro-services, such as those implemented by AI flight instructors, LMS, and Electronic Flight Bag (EFB) solutions. The components shall additionally implement micro-services intended to expose custom functionality implemented within the flight simulation environment as part of the PTT program, e.g., in a virtual reality dynamic menu system. The projected number of ITDs/IOSs/MPMR devices are as follows:

● Joint Base San Antonio, Randolph AFB, TX

• 22 ITDs

● Columbus AFB, MS

• 30 ITDs

• 5 cITDs to be utilized for spare parts

• Up to 10 IOSs

● Laughlin AFB, TX

• 30 ITDs

• 5 cITDs to be utilized for spare parts

• Up to 10 IOSs

● Vance AFB, OK

• 30 ITDs

• 5 cITDs to be utilized for spare parts

• Up to 10 IOSs

● Sheppard AFB, TX

• 20 ITDs

● Fort Novosel, AL

• 10 HITDs

• (Option) 4 MPMR devices

The Government POC at each location will support development patching with one or two (for any multiplayer updates) of the existing supported devices at each location with the exception of Randolph AFB. Randolph AFB will have 1 cITD and 1 eITD for testing and development patching support. The Government at each base will designate a device(s) to remove from training when patches and updates are released. The device(s) will only be removed from training during the testing of patches/updates. Once the patch or update is approved/rejected by the Government, the device will be placed back into the training rotation (removing any unaccepted patches or updates).

The Government will not be developing/testing new concepts/software/hardware at any base or device other than test devices located at Randolph AFB. If personnel at the other locations have ideas about hardware or software improvements/modifications, the request will be submitted for consideration to the 19 AF Flying Training Center of Excellence.

Aggregate PTT device functionality shall be exposed to the higher-level PTT components via two proposed components that shall be implemented using service-oriented architectures (SOAs):

a. The “ITD Management Service Application” that will be implemented as a persistent Windows service application responsible for receiving login event notifications from the Google Single Sign-On (SSO) (or equivalent) and (a) initializing all local ITD software with required runtime data, and (b) launching the Student Portal (login landing page).

b. The flight simulator-agnostic “ITD Common Interface” will directly integrate with flight simulator-specific and third-party plugins and effects to expose various PTT device data, scenario configuration and initialization functionality, aircraft/avionics data, and dynamic menu/injectable visual content functionality to higher-level PTT applications via open and custom micro-services. Specific integration pathways-i.e., the ITD Common Interface and individual PTT components shall leverage either existing PTT component micro-services or new ITD Common Interface micro-services as required.

The Contractor shall participate in the design, implementation and device-level identity management and authentication solutions across PTT devices as requested by designated program authorities and cybersecurity Authority to Operate (ATO) requirements.

4.2 The Contractor shall coordinate with third-party personnel through the Government COR in support of but not limited to: maintaining the scaled software and hardware component integration interfaces and communication standards, maintain a common style guide and user interface (UI) design across all components. The Contractor shall perform all additional work necessary to support and maintain all required PTT devices, including all integrated components. (See also Paragraphs 5.1.)

5.0. PROGRAM DEVICES & SUPPORT.

5.1. The Contractor shall maintain and support existing PTT devices at locations identified by the Government (Material acquisition to be accomplished as noted in Paragraphs 5. The Contractor shall connect all devices to network infrastructure provided by the cloud data storage and user authentication solution provider. The Government will provide on-site contractors with desk space at all designated locations, a space the Contractor can use to assemble the devices, a Government computer, and network access. PTT devices comprise, but are not limited to, the following hardware components and materials:

● Desktop and laptop computers;

● Head-Mounted Displays (HMDs) and all associated peripherals;

● Tablets;

● Monitors;

● Robust flight chairs;

● Hands-on throttle and stick (HOTAS); and

● Chair mounted rudder pedals.

The Contractor shall:

● Maintain operability of devices to support training in accordance with performance objectives listed in paragraph 17 of this PWS.

● Maintain the PTT devices, including replacing broken parts and troubleshoot software issues.

● Provide resolution for technical and troubleshooting issues No Later Than (NLT) three business days from reporting.

● Apply software patches NLT three business days upon release.

● Assist students and instructors with use of the systems.

● Collect user feedback as students use the systems and provide bi-weekly written report to the COR as part of the Monthly Status Report (MSR) (see Paragraph 6.5).

● Collect usage data at each operating location to include hours available, events scheduled per Government scheduler, ITD utilization based on student selection of free flight or syllabus modes, and report as part of the MSR (see para. 6.5).

The Contractor shall advise the Government, and document accordingly, when Government-imposed requirements prevent the Contractor from obtaining a performance objective, NLT 3 business days.

5.2. Hardware and Shipping Purchases

In the event a hardware component, consumable, or software must be purchased to maintain operability of the devices, or existing items need to be sent for repairs, the Contractor shall request approval from the COR, prior to any purchase. The COR will validate the need, verify available funding, and approve via email. The Contractor shall be responsible for only approved and funded purchases of materials and shipping and will invoice the Government for only approved requests.

The Government shall not be responsible for purchases made without prior approval. If a replacement item is not available for purchase (due to obsolescence, Diminishing Manufacturing Sources and Material Shortages (DMSMS), etc.) the Contractor shall research alternatives to provide for Government consideration and approval. The Contractor shall provide inputs and documentation to the Government for the Request for Change (RFC) process and other approvals necessary for the Government to obtain and maintain the ATO.

5.3. (OPTION) TH-1H Multi-Place Mixed Reality (MPMR) immersive aircrew training device The Contractor shall provide all services and equipment, at Fort Novosel, AL, necessary to maintain and support MPMR devices starting 60 days prior to the forecasted initial class start date. The Contractor shall maintain a common software interface to integrate current and future software and hardware components as required by program goals, hardware solutions for the cockpit simulation environment, and on-premises network and data architecture hardware and support, as appropriate.

The Contractor shall:

a. Ensure MPMR device 85% Operational Availability (OA to meet the required scheduled training hours, 12 hours per day per MPMR. Calculated per month; (Availability Rate (AR), formula ((Y/X) *100 = AR), X = scheduled hours; Y = MPMR hours available, ex.

850/1000 = .85 * 100 = 85).

b. Maintain the MPMR devices, including replacing broken parts and troubleshooting software issues.

c. Provide resolution for technical and/or troubleshooting issues No Later Than (NLT) three business days from reporting.

d. Apply software patches NLT three business days upon release.

e. Manage check-in and check-out of the MPMR devices 100% of the time.

f. Assist students and instructors with use of the system.

g. Assist instructors with Spin up training to learn how to use the MPMR devices.

h. Collect user feedback as students use the devices and provide bi-weekly written reports to the COR as part of the MSR.

6.0. CONTRACT MANAGEMENT.

6.1. Kick-Off Meeting. The Contractor shall schedule, coordinate, and host a program kickoff meeting NLT Ten (10) business days after contract award. The meeting shall provide an introduction between Contractor and Government stakeholders, and allow for discussion of technical, management, security requirements, travel authorizations, and reporting procedures. At a minimum, the attendees shall include the key Contractor personnel, CO, PM, and COR.

The Contractor shall provide a meeting agenda for review and approval by the CO and COR/Project Manager (PM) NLT two (2) business days before scheduled meeting. The agenda shall include the following topics/deliverables:

Government

a. Introduction of CO, PM, COR, and other key personnel.

b. Roles, Responsibilities, and Authorities.

c. Monthly Status Reports (MSR).

d. Invoicing Requirements

Contractor

a. Introduction of PM and other key personnel

b. Security discussion and requirements

c. Draft Project Management Plan

The Contractor shall provide meeting minutes to the COR NLT five (5) business days after the kickoff meeting. Minutes will include contractor/government comments, actions, and guidance/direction and schedule changes.

6.2. Contractor Program Manager (PM). The Contractor shall identify a PM who shall be the primary Contractor representative responsible for all work awarded under this requirement, participate in Program/Project Management Reviews quarterly, and ensure all standards referenced herein are adhered to. The Contractor PM’s contact information (i.e., name, phone number, email, etc.) shall be sent to the COR NLT five business days after contract start date. This includes:

a. Serving as the Government’s primary point of contact for all contractual matters.

b. Requesting any Government-Furnished Information (GFI) or Equipment (GFE).

c. Manage program risks, issues, and opportunities with the Government PM by identifying program risks in a risk register, issues, and opportunities, developing risk mitigation strategies, risk response plans, issues handling; and opportunities recommendations.

d. Executing and managing Associate Contractor Agreements (ACAs) and/or memoranda of understanding (MOUs) among other prime contractors supporting the program.

6.3. Transition Phase-In/Phase-Out. To minimize any decrease in productivity and to prevent possible negative impacts on services, the Contractor shall have personnel on board and prepared to commence full performance of services within 15 business days after the contract start date. If the personnel are not made available at that time, the Contractor shall notify the CO and show cause. If the Contractor does not show cause, the Contractor may be subject to default action.

a. The contractor shall provide a transition plan within the program management plan (PMP) that outlines the designated time period and strategy to transition into the duties as the contractor and to transition out of the contract at the end of the period of performance.

b. The Phase In transition period shall not exceed 10 business days and the Phase Out transition period shall not exceed thirty (30) calendar days.

c. If there is a change in contractor, the incumbent contractor shall provide familiarization and allow the follow-on contractor and/or government personnel to observe operations, facilities, work, equipment locations, and reporting procedures on a non-interference basis.

During the phase-out familiarization period, the incumbent shall be fully responsible for operation of the Device Support Services III support workload.

6.4. Associate Contractor Agreements ( A C A ) . The Contractor shall maintain ACAs for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the PTT program, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract. ACAs shall:

a. Identify the associate contractors and their relationships.

b. Identify the program involved and the relevant Government contracts of the associate contractors.

c. Describe the associate contractor interfaces by general subject matter.

d. Specify the categories of information to be exchanged or support to be provided.

e. Include the expiration date (or event) of the ACA.

f. Identify potential conflicts between relevant Government contracts and the ACA.

g. Include agreements on protection of proprietary data and restrictions on employees.

6.5 Monthly Summary Reports (MSR).

6.5.1 The Contractor shall document all program management activities in the MSR, due NLT five

(5) business days following the month that the report covers. At a minimum, the report shall:

a. Document all sustainment support activities.

b. Provide rough order of magnitude (ROM) unit cost estimates.

c. Document replacement of hardware or software.

d. Document PTT devices in subsequent efforts.

e. Document user feedback report.

f. Document updates with any changes to the final version of the design document.

g. Document Government actions required.

h. Highlight changes to the register, issues, and opportunities.

6.5.2 The Contractor shall provide labor and personnel with experience, education, certifications, and the skills necessary to complete the requirements for the maintenance and support of the PTT devices. The Contractor shall provide labor for both professional and technical expertise that meet the necessities of all tasks in support of the requirements specified in this PWS, including program management.

6.5.3 The Contractor shall conform to standards of conduct and code of ethics, which are consistent with those applicable to Government employees. Contractor personnel shall obtain authorization to have access to support sites and Government facilities if needed.

6.5.4 The Contracting Officer (CO) may require the Contractor to remove any Contractor employee who is identified as a potential threat to the health, safety, security, general well-being or operational mission of the installation and its population.

7.0. REQUIRED TRAINING COURSES & COMPLETION CERTIFICATES.

The Contractor shall ensure that its employees have all the required professional certifications and licenses (current and valid) for each applicable task before commencement of work. Contractor personnel are required to possess the skills necessary to support their company’s minimum requirements of the labor category under which they are performing. Training necessary to meet minimum requirements will not be paid for by the Government. The Contractor shall ensure all employees complete mandatory annual training courses required by the Government

8.0. NON-PERSONAL SERVICES.

The Government will neither supervise contractor employees nor control the method by which the Contractor performs required services. Under no circumstances shall the Government assign work to or prepare work schedules for individual Contractor employees. It shall be the responsibility of the Contractor to manage its employees, and to guard against any actions that are of the nature of personal services or give the perception of personal services. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor’s responsibility to notify the CO immediately. These services shall not be used to perform work of a policy/decision making or management nature (i.e., inherently Governmental functions). All decisions relative to programs supported by the Contractor shall be the sole responsibility of the Government.

9.0. PERFORMANCE REPORTING.

The Contractor’s performance will be monitored by the Government and reported in the Contractor Performance Assessment Reporting System (CPARS), except where a degradation of service, negative performance, or other disruption stems from Government-imposed requirements or restrictions. Performance standards shall include the Contractor’s ability to provide or satisfy the following:

a. Provide satisfactory solutions to requirements with the necessary customer support.

b. Provide solutions and services that meet or exceed specified performance parameters.

c. Deliver timely and quality deliverables to include accurate reports.

d. Ensure solutions to requirements are in compliance with applicable policy and regulation.

9.1 The Contractor is responsible for the security, integrity, and authorized use of their systems interfacing with the Government and or used for the transaction of any and all Government business.

9.2 The Government, at its discretion, may suspend or terminate the access and/or use of any or all Government access and systems for conducting business with any/or all Contractors when a security or other electronic access, use or misuse issue gives cause for such action. The suspension or termination may last until such time as the Government determines that the situation has been corrected or no longer exists.

10.0 CONTRACT MANPOWER REPORTING

The Contractor shall report all contractor labor hours (including sub-contractor labor hours) required for performance of services provided under this contract via a secure data collection site.

Enterprise Contractor Manpower Reporting Application (eCMRA) was replaced with Service Contract Report (SCR). The System for Award Management (SAM) (https://www.sam.gov) is the secure data website and collection point for SCR information. Data for service requirements must be uploaded to the SAM website at https://www.sam.gov. The Contractor shall create an initial contract record in the applicable electronic SAM tool within the 15 business days after contract award. The Contractor is required to completely fill in all required data fields using the sam.gov address provided above. Once logged into the SAM site, click on the icon for the Department of Defense (DoD) organization that is receiving or benefitting from the contracted services.

Reporting inputs will be for the labor executed during the PoP during each Government fiscal year (FY), which runs from 01 October through 30 September. While inputs may be reported at any time during the FY, all data shall be reported NLT 31 October of each calendar year. The SCR Guidebook, SCR Frequently Asked Questions (FAQ), and the Customer Service Helpdesk for Government personnel and Contractors are available at https://www.sam.gov.

11.0. TRAVEL AND SHIPPING.

Contractor personnel may be required to travel in performance of assigned functions consistent with the scope of this PWS. When travel is required outside of contractor’s local area, the Contractor shall submit a request to the Contracting Officer’s Representative (COR) identifying the purpose, location, dates, and personnel (name and title) needed for the travel. Costs that exceed maximum per diem rates or the lowest customary standard, coach, or equivalent airfare must include written justification for use of the higher amounts approved by an officer of the Contractor’s organization and are subject to advance approval by the CO. After review of the estimated costs and verification of funds availability, the COR will notify the Contractor that the travel has been approved by the CO. After completion of travel, the Contractor shall provide a

Trip Report (A00X), identifying actual costs paid, and shall submit an invoice via Wide Area Workflow (WAWF) with a detailed breakdown of reimbursable travel costs incurred and receipts for all expenses of $75.00 or more. The Trip Report shall also include the following information.

Personnel traveled Dates of travel Destination(s) Purpose of Trip; contract effort supported and Contract ID number;

Organizations supported; Action Items Results of trip Approval Authority

Travel shall be conducted IAW Federal Acquisition Regulation (FAR) 31.205-46 and Federal Travel Regulations. Travel conducted that does not follow the above procedures and regulations will not be reimbursable to the Contractor. The Government will be responsible for all shipping expenses for PTT Devices to and from events and off-site in their entirety. Travel and shipping costs will be reimbursed for actual costs only – no G&A, overhead, or profit may be added. The Contractor will only be reimbursed for travel outside the Contractor’s local area.

12.0. MATERIALS, EQUIPMENT, AND FACILITIES.

The Contractor shall furnish all material and equipment needed in performance of this requirement.

The Contractor shall ship, move, store, inventory, and handle installation material that is identified as contractor furnished equipment (CFE). The Contractor shall establish and maintain an inventory of on-site contractor assets (i.e. CFE) and maintenance services purchased.

Agency specific requirements for equipment and facilities will be defined by the Government. If deemed necessary by the Government, Government Furnished Equipment (GFE), AF email accounts, and CACs shall be issued as part of onboarding.

GFE is defined as any and all equipment/property owned or leased by the Government. GFE is incidental to the place of performance, when the contract requires contractor personnel to be located on a government site or installation, and when the property used by the contractor within the location remains accountable to the Government. Items considered to be incidental to the place of performance include but are not limited to office space, desks, chairs, telephones, computers, copiers, and fax machines. GFE does not include intellectual property and software.

13.0. CONTRACTOR IDENTIFICATION.

All Contractor/subcontractor personnel shall wear AF-approved picture identification badges so as to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone, or via electronic mail, Contractor/subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees.

Contractors/subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic email signatures shall reflect Contractor status. Where practicable, Contractor/subcontractors occupying collocated space with their Government program customer should identify their work-space area with their name and Contractor status.

14.0. PLACE OF PERFORMANCE.

The primary place(s) of performance shall be at the following locations: JBSA – Randolph, TX;

Columbus AFB, MS; Laughlin AFB, TX; and Vance AFB, OK; Sheppard AFB, TX; and Fort Novosel, AL. Each UPT base may have ITDs at various locations, all within 400 meters of each other. The Contractor may be required to travel periodically to locations for technical demonstrations and/or testing to include Government workshops. The Government will reimburse Contractor travel and related shipping costs where applicable, IAW Paragraph 11.0.

15.0. NORMAL HOURS OF OPERATION.

15.1. Contractor personnel supporting ITDs shall be available between the hours of operation of 0800-1700 hours, Monday through Friday.

15.2. Contractor personnel supporting the MPMR devices shall be available for three training iterations totaling 13.5 hours (e.g. 0630L-2000L), Monday through Friday.

The Contractor shall have the flexibility to schedule work outside the normal hours when needed, with prior approval of the COR and CO. However, in no case shall on-site support be provided outside normal hours when there are no Government employees in the work area. The following federal holidays are observed:

New Year’s Day Martin Luther King Jr’s Birthday Presidents’ Day Memorial Day Juneteenth Independence Day Labor Day Columbus Day Veteran’s Day Thanksgiving Day Christmas Day

Down days or other days declared by the Commander in Chief or the Commander are considered duty days and are not included in the definition of a holiday.

16.0. CONTRACT DELIVERABLES

The following list provides deliverables applicable to the PTT Device Support Services PWS. This list is not meant to be exhaustive or inclusive of all that may be required, referenced, or otherwise identified within this PWS. The government CO and/or COR, if desired, may require that a deliverable comply with a specific DID or Military Standard, even if it has been rescinded, cancelled, or exists only in a draft form. The government PWS CO and/or COR may likewise require the contractor to comply with an identified industry or commercial standard or request the contractor format or utilize existing contractor data. Acceptance of final documents is subject to Government approval.

Deliverable

Number Title PWS Task

Reference Frequency

A001 Monthly Status Report (MSR) 6.5 Monthly

A002 Travel Authorization Form 11.0 As required

A003 Travel Trip Report 11.0 As required

A004 Quality Control Plan 26.0 One time with revisions as required

A005 Kick-off Meeting Agenda 6.1 One time with revisions as required

A006 Meeting Minutes 6.1, 6.6 As required

A007 Program Management Plan

(PMP)

6.3 One time with revisions as

required

17.0. SERVICES SUMMARY.

The Contractor’s performance at the contract level will be assessed by a process that measures success towards achieving defined performance objectives. The Service Summary will be IAW DAFI 63-138, Acquisition of Services, AFI 10-601 Operational Capability Requirements Documentation And Validation, and FAR Subpart 37.6 “Performance-Based Acquisition.” Quality requirements are as follows:

Performance Objective

PWS

Para Ref

Performance Threshold

PO-1: The Contractor shall apply any software patches to the PTT devices NLT three business days upon release.

5.1 5.3

No more than one discrepancy per year.

PO-2: The Contractor shall provide resolution for technical and/or troubleshooting issues NLT three business days after reporting.

5.1 5.3

No more than one discrepancy per month.

PO-3: The Contractor shall provide the COR a Monthly Summary Report (MSR) IAW the PWS.

6.5 Progress report shall be submitted

NLT 5th business day of the following month; no more than one late submission discrepancy every six months.

PO-4: The Contractor shall maintain operability on 80% of PTT devices (excluding MPMR) at each location 100% of the time and report as part of the MSR.

5.1

No more than 20% of the PTT devices at each location shall be inoperable.

PO-5: The Contractor shall assist students and instructors with effective use of the systems.

5.1 5.3

No more than two valid customer complaints per quarter.

PO-6: The Contractor shall collect user feedback as students use the systems and provide a bi-weekly report submitted to the COR as part of the

MSR.

5.1 5.3 6.5

No more than one valid discrepancy per quarter.

PO-7: Collect usage data at each operating location to include hours available, events scheduled per government scheduler, ITD utilization based on student selection of free flight or syllabus modes. and report as part of the MSR.

5.1, No more than one late discrepancy every six months.

PO-8: (Option) The Contractor shall maintain the TH-1H MPMR device operational availability rate at Fort Novosel of no less than 85% and report as part of the MSR.

5.3 No less than 85% Operational

Availability (OA) per month.

18.0. QUALITY ASSURANCE

Contractor performance will be compared to the Performance Objectives and performance threshold (specific standard). The Contractor shall provide and maintain an inspection system acceptable to the Government covering the services under this contract. Complete records of all inspection work performed by the contractor shall be maintained and made available to the Government during contract performance and for as long afterwards as the TO requires. The Government may use a variety of surveillance methods to evaluate the contractor’s performance to determine if it meets the performance objectives and performance threshold.

19.0. GOVERNMENT INSPECTIONS

The Government will evaluate the contractor’s performance under this contract in accordance with its Quality Assurance Surveillance Plan (QASP). Government methods of inspection other than those listed in the PWS (such as provided for by the Inspection of Service clause) may occur during the performance period of this contract. Such surveillance will be done according to standard inspection procedures or other contract provisions. Any action taken by the CO as a result of inspections will be according to the terms of this contract.

20.0. GOVERNMENT CONTRACTING OFFICER’S REPRESENTATIVE

The CO will appoint a Contracting Officer’s Representative (COR) and issue a COR Designation Letter stating the authority, as well as responsibilities and limitations of the COR especially with regard to changes in cost or price, estimates, or changes in delivery dates. The contractor will receive a copy of the written designation. The COR will monitor all technical aspects of the contract and assist in contract administration. The COR will provide technical assistance and clarification required for the performance of the contract. The COR will participate in project meetings, represent the CO in the technical phases of the work, and receive contract deliverables. The COR will not provide any supervision or instructional assistance to contractor personnel. The COR is not authorized to change any terms or conditions of the contract. Changes in the contract requirements, price or terms and conditions shall only be made by the CO via properly executed modifications to the contract.

21.0. RECORDS, FILES, AND DOCUMENTS.

All physical records, files, documents, and work papers maintained by the Contractor, provided and/or generated by the Government, or for the Government in performance of this PWS, shall be transferred or released to the Government or successor contractor, and shall become and remain Government property. These records shall be maintained and disposed of IAW AFMAN 33-363 “Management of Records;” AFI 33-364 “Records Disposition – Procedures and Responsibilities;”

the FAR; and the Defense Federal Acquisition Regulations (DFARS), as applicable. Nothing in this section alters the rights of the Government or the Contractor with respect to patents, data rights, copyrights, or any other intellectual property or proprietary information as set forth in any other part of this PWS.

22.0. PERFORMANCE OF SERVICES DURING A CRISIS.

IAW DoDI 1100.22, and DFARS 237.76, “Continuation of Essential Contractor Services,” unless otherwise directed by an authorized Government representative, it is determined that services as identified in this PWS are NOT essential for performance during a crisis. In the event of an unforeseen natural or military crisis (i.e., hurricane, insurrection, etc.), the Contractor’s primary responsibility is to safeguard the Contractor’s employees.

23.0. ORGANIZATIONAL CONFLICT OF INTEREST.

Contractor personnel performing work under this contract may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5, the Contractor shall notify the CO immediately whenever they become aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the CO to avoid or mitigate any such OCI. The Contractor shall provide a mitigation plan to the Government PM, COR, and CO NLT 10 business days after contract award. Acceptability is solely at the discretion of the CO. In the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the CO may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

24.0. INHERENTLY GOVERNMENTAL FUNCTIONS

In performing the tasks in this PWS, the contractor shall immediately stop work and notify the Government Contracting Officer in writing regarding situations where they believe, or have reason to believe, they have been tasked to perform an inherently governmental function (IGF) as defined by FAR Subpart 7.5.

25.0. NON-DISCLOSURE AGREEMENTS (NDA)

All prime and Sub-Contractor employees along with any corporate personnel who will have knowledge of the projects worked on under this contract, must provide a signed NDA to the COR prior to access of information regarding the projects. The signed NDA will serve as assurance that the personnel shall not disclose any information about potential or actual government requirements, cost estimates, etc., to any individual without the need to know as determined by the Government and by the NDA.

26.0. QUALITY CONTROL PLAN (QCP).

The Contractor shall be responsible for establishing, implementing, and maintaining a current QCP. The Contractor’s QCP shall identify the standards, processes, procedures, and checklists for all tasks performed. The QCP shall also identify, prevent, and correct any deficiencies for all services set forth in this PWS, and shall assure the requirements of this contract are provided as specified. The QCP must illustrate proposed method(s) of inspection, and actions to be taken to correct deficiencies discovered during the inspection process. The Contractor shall submit their QCP to the COR and CO NLT 10 business days after contract award. The plan will be reviewed by the Government and approval will be in writing via email. The Contractor shall monitor quality processes and perform technical audits and reviews IAW the QCP to verify adherence to organizational standards, processes, and procedures. Changes to the QCP during contract performance shall be submitted to the COR and CO for acceptance NLT 10 business days prior to implementation.

The Contractor's quality inspection documentation (i.e., metrics, reports, etc.) shall be made available to the COR NLT two business days after requested. The reports should provide information on the methods of inspection, what was inspected, discrepancies found, and actions taken to correct and preclude recurrence.

27.0. PASS AND IDENTIFICATION, AND COMPUTER ACCESS ITEMS

The Host Unit shall ensure the following pass and identification items required for contract performance are obtained for employees and non-Government owned vehicles:

a. Installation Access Pass (IAP) (DBIDS), Visitor/Vehicle Pass (DoDM 5200.08, Volume 3, “DoD Physical Security Program: Access to DoD Installations”, used for contracts for less than one year to include one-day visits (i.e., warranty work) and other credentials required for applicable facility/workspace access.

b. DoD Common Access Card (CAC) and other credentials required for applicable facility/workspace access. CAC applications shall be accomplished by Trusted Agents via the Trusted Agent Sponsorship System (TASS). The Contractor shall be required to obtain and maintain Common Access Card (CAC) for each employee for base and data system access.

The Contractor shall ensure each employee has a complete Access National Check and Inquiries (ANACI); Contractor employees seeking to obtain CAC shall submit personal background information for the purpose of a ANACI investigation. The Contractor employee will be authorized a CAC upon the adjudication of a favorable ANACI investigation. The contractor shall provide all CACs issued in performance of this contract to the COR at the end of the period of performance.

28.0. OBTAINING AND RETRIEVING IDENTIFICATION MEDIA.

As prescribed by the AFFARS 5352.242-9000, Contractor Access to Air Force Installations, the Contractor shall comply with the following requirements:

a. The Contractor shall obtain installation access passes for all contractor personnel who make frequent visits to or perform work on the Air Force installation(s) cited in the contract.

Contractor personnel are required to present the installation access pass while visiting or performing work on the installation.

b. The Contractor shall submit a written request on company letterhead to the COR, listing the following: contract number, location of work site, start and stop dates, names, and driver’s license numbers (incl. state of issue) for the Contractor employees needing access to a base, NLT 10 business days prior to contract commencement. The authorized security manager will endorse the request and forward it to the issuing installation pass and registration office or security forces for processing. Contractors will present government (state or federal) issued ID, before being issued a pass to enter the installation. Before being issued a pass to enter the installation, a criminal history check will be conducted for every individual requesting a pass.

c. Personnel employed by the Contractor and operating a motor vehicle on the installation must possess proof of the following:

● Liability Insurance

● Current License Plates

● Current State Inspection Sticker

● Valid State Driver License

● A phone number for sponsor on base

Upon completion or termination of the contract or expiration of the identification passes, the Contractor shall ensure that all base identification credentials issued to contractor employees are returned to the issuing office. If a contractor employee has been terminated, the credentials will need to be retrieved and returned to issuing activity so that employee does not have base access. If the Contractor fails to return the credential, then notify security forces so base access is not allowed.

Failure to comply with these requirements may result in withholding of final payment.

29.0. SECURITY CLEARANCE REQUIREMENTS.

The work being performed under this contract shall be Controlled Unclassified Information (CUI).

The Contractor may require access to Government computers and/or the Non-classified Internet Protocol (IP) Router Network (NIPRNet). The Contractor does not require access to classified information and will not require a facility security clearance.

The Contractor is responsible for the security, integrity, and authorized use of their systems interfacing with the Government and or used for the transaction of all Government business. The Government, at its discretion, may suspend or terminate the access and/or use of any or all Government access and systems for conducting business with any/or all Contractors when a security or other electronic access, use or misuse issue gives cause for such action. The suspension or termination may last until such time as the Government determines that the situation has been corrected or no longer exists.

30.0. ADDITIONAL SECURITY REQUIREMENTS.

IAW DoDM 5200.01 and AFI 16-1404, the Contractor shall comply with the following:

• Air Force Systems Security Instruction (AFSSI) 7700 Emission Security (EMSEC)

• Applicable Air Force COMSEC General Publications (AFKAGs)

• AFSSIs for Communications Security (COMSEC)

• AFI 10-701, Operation Security (OPSEC)

• DoD Standard 22-Level I Anti-Terrorism (AT) Awareness Training

• DoD Standard 13-Force Protection Condition Measures

• AFI 10-245-Air Force Anti-Terrorism

• DoDI O-2000.16V1_AFI 10-245-O, Anti-Terrorism (AT) Program Implementation

Level I AT Awareness training is available for Contractor personnel to complete at the Joint Knowledge Online website. By following the link below, individuals can register for the course and complete required training. After successful completion, individuals will type in their first and last name, save a copy of their certificate and provide to their entity’s security manager.

https://jko.jten.mil/courses/AT-level1/launch.html.

31.0. FREEDOM OF INFORMATION ACT PROGRAM (FOIA).

The Contractor shall comply with DoDM 5400.07 and DoD Freedom of Information Act (FOIA) Program requirements. The regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding CUI material. The Contractor shall comply with AFI 33-332, Air Force Privacy and Civil Liberties Program, when collecting and maintaining information protected by the Privacy Act of 1974 authorized by Title 10, United States Code, Section 8013. The Contractor shall remove or destroy official records only in accordance with AFI 33-322, Records Management and Information Governance Program.

32.0. REPORTING REQUIREMENTS.

The Contractor shall comply with AFI 71-101, Volume- 1, Criminal Investigations Program, and Volume-2, Protective Service Matters requirements. Contractor personnel shall report to an appropriate authority, any information or circumstances of which they are aware may pose a threat to the security of DoD personnel, contractor personnel, resources, and classified or unclassified defense information.

33.0. PHYSICAL SECURITY.

The Contractor shall safeguard all government property, including controlled forms, provided for contractor use. At the close of each work period, government training equipment, support equipment, and other valuable materials shall be secured. During increased Force Protection Conditions (FPCONs), Contractors may have limited access to the installation and should expect entrance delays.

34.0. HEALTHCARE.

Healthcare provided at the local military treatment facility on an emergency reimbursable basis only.

Appendix A: Travel Authorization Form

Contractor Travel Authorization Request Traveler Name: Employee #: Contract & Travel CLIN #: Request Date:

TRAVEL & COST DETAILS

All travel transportation and lodging arrangements should be made in accordance with Joint Travel Regulations (JTR).

Travel From (City, State): Travel To (City, State): Dates of Travel:

to

# of Days:

List Any Additional TDY Destinations:

Facility to be visited (Name and Location): Government Sponsor/Approver (Name, Title, Email, Phone No.):

Purpose/Justification of Travel:

Justification For Deviations (not choosing lowest fare, exceeding allowable lodging rate, larger car, any other non-standard travel arrangements):

Estimated Total Trip Cost:

Airfare Total:

M&IE (Rate/Total):

Lodging (Rate/Total):

Rental Car (Rate/Total):

Additional Travel Costs (Include items such as Hotel Taxes, Baggage Fees, Parking Fees, Mileage, Rental Car Fuel, Conference Fees, etc.

SEMINAR / TRAINING / CONFERENCE COORDINATION

Seminar/Training/Conference Title: Fee:

$ 0

Fee Deadline:

Description and Applicability to Task Order:

SECURITY INFORMATION

Visit Request Required: No, visit request not required

Yes, visit information included at right

Yes, previous request valid until

*Traveler will ensure VR is coordinated with appropriate agencies*

SMO Code:

Visit Access Level: Secret Top Secret

OCONUS Travel Only: Coordinate with contractor FSO before approval of this form

Yes No

GOVERNMENT APPROVAL

This travel or training is required to support the Task Order Performance Work Statement responsibilities, is necessary for contractor’s function in assigned work environment, and is a direct benefit to the government.

Government Sponsor/Approver: Signature:

Title/Office: Phone:

CONTRACTOR COORDINATION

Traveler: Signature:

Program Manager: Signature: