DRAFT PWS for MTS-AGRA_V4 clean copy V2.pdf

FA9302-26-R-R006

Page - 1 - of 39

Quality, Schedule, AFTC Edwards Performance Work Statement (PWS)

Requirement Title: MTS AGRA Compatibility POC: Jonathan Denning, 412 RANS/ENR Requiring Organization: 412 TW/ Experimental Test Force Phone: 661-277-1327

Performance-Based Service Acquisition (PBSA)

Per the Federal Acquisition Regulation (FAR), PBSA means an acquisition structured around the results to be achieved as opposed to the manner by which the work is to be performed and a Performance Work Statement (PWS) means a statement of work for performance-based acquisitions that describes the required results in clear, specific and objective terms with measurable outcomes.

Minimum Mandatory PBSA Requirements

1. Performance requirements in the Service Summary shall align with Contractor Performance Assessment Reporting System (CPARS) categories.

2. Performance requirements define the work in measurable, mission-related terms; in terms of results required rather than the methods of performance of the work.

3. Use measurable performance standards (i.e., quality, quantity, timeliness) tied to performance requirements.

4. A Quality Assurance Surveillance Plan (QASP) describes how the contractor’s performance will be measured against the performance standards.

5. Specifies procedures for reductions of fee or for reductions to the price of a fixed-price contract when services are not performed or do not meet contract requirements.

6. Includes performance incentives where appropriate; positive and negative incentives shall be considered in connection with service contracts for performance of objectively measurable tasks when quality of performance is critical and incentives are likely to motivate the contractor.

Additional PBSA Components

1. An historic workload analysis is performed or estimated if historic data is unavailable, to aid in determining the performance requirements and standards, QASP, and incentives offered to contractors.

2. The solicitation and contract/task order convey a logical, easily understood flow among performance requirements, performance standards, QASP, and performance incentives.

3. Process-oriented requirements (e.g., job descriptions, education requirements, level-of-effort) and reports are eliminated to the maximum feasible extent.

4. Government Quality Assurance (QA) performance evaluators assigned to assess contractor performance are trained in PBSA.

5. Commercial and/or industry-wide performance standards, where available, are relied upon.

6. The marketplace and other stakeholders are provided the opportunity to comment on draft performance requirements and standards, the QASP, and performance incentives.

Page - 2 - of 39

FOR EDWARDS AFB CONTRACTING OFFICERS ONLY

Please ensure the following FAR Clauses are listed in the contract under the section titled, Clauses Incorporated by Reference or Clauses Incorporated by Full Text

FAR Clause Number Reference Only

Full Text

52.223-1: Biobased Product Certification 52.223-2: Affirmative Procurement of Biobased Products Under Service and Construction Contracts

52.223-3: Hazardous Material Identification and Material Safety Data 52.223-4: Recovered Material Certification 52.223-5: Pollution Prevention and Right-to-Know Information 52.223-7: Notice of Radioactive Materials 52.223-9: Estimate of Percentage of Recovered Material Content for EPA Designated Items

52.223-10: Waste Reduction Program 52.223-11: Ozone-Depleting Substances and High Global Warming Potential Hydrofluorocarbons

52.223-12: Maintenance, Service, Repair, or Disposal of Refrigeration Equipment and Air Conditioners

52.223-19: Compliance with Environmental Management Systems 52.223-20: Aerosols 52.223-21: Foams 52.223-22: Public Disclosure of Greenhouse Gas Emissions and Reduction Goals – Representation

52.223-23: Sustainable Products and Services DFAR Clause Number

252.223-7001: Hazard Warning Labels 252.223-7006: Prohibition on Storage, Treatment, and Disposal of Toxic or Hazardous Materials

252.223-7008: Prohibition of Hexavalent Chromium AFFAR Clause Number

5352.223-9001: Elimination of Use of Class I Ozone Depleting Substances (ODS)

7. If the size of the requirement justifies the resource expenditures, potential offerors are given the opportunity to learn more about the "as is" operation to facilitate their ability to develop intelligent proposals.

8. The contract/task order is fixed price and is completion type (vs. term type or level-of-effort).

9. Past performance evaluations are based on the results of contract QA measurements and incentives, and QA plans are consistent with past performance factors.

Page - 3 - of 39

PERFORMANCE WORK STATEMENT (PWS)

FOR

SOFTWARE DEVELOPMENT SERVICES: MISSION TERMINATION SYSTEM (MTS)

COMPATIBILITY WITH AUTONOMY GOVERNMENT REFERENCE ARCHITECTURE (A-GRA)

AT

EDWARDS AFB, CA.

7/27/2026

Page - 4 - of 39

Table of Contents

1.0 DESCRIPTION OF SERVICES ................................................................................................... - 5 -

2.0 SERVICE SUMMARY ................................................................................................................. - 9 -

3.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES ................................................. - 14 -

4.0 GENERAL INFORMATION ..................................................................................................... - 16 -

5.0 CONTRACT PERSONNEL ....................................................................................................... - 17 -

6.0 MISCELLANEOUS INFORMATION........................................................................................ - 19 -

7.0 GENERAL ................................................................................................................................. - 23 -

8.0 APPENDIX 1 ............................................................................................................................ - 31 -

9.0 APPENDIX 2 ............................................................................................................................ - 34 -

10.0 APPENDIX 3 ....................................................................................................................... - 35 -

11.0 APPENDIX 4 ....................................................................................................................... - 36 -

12.0 APPENDIX 5 ........................................................................................................................ - 38 -

Page - 5 - of 39

1.0 DESCRIPTION OF SERVICES

1.1 General Scope. This is a nonpersonal services contract requesting software development of Autonomy Government Reference Architecture (A-GRA) interfaces for the Mission Termination System (MTS), yielding a Technology Readiness Level 9 (TRL 9) product. MTS is a Run Time Assurance (RTA) tool based on the Testing Autonomy in Complex Environments (TACE) code base created by Johns Hopkins Applied Physics Lab (JHU APL). MTS is used at Edwards AFB to safely test autonomous control of small Unmanned Aerial Systems (sUAS). The government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the contractor who, in turn, is responsible to the government.

1.1.1 Description of Services/Objectives. The contractor shall provide all management, personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and nonpersonal services necessary to perform MTS/A-GRA software development as defined in this Performance Work Statement (PWS) except for those items specified as Government Furnished Property and services. The contractor shall perform to the standards in this contract. This includes the planning, coordination, and surveillance of the activities necessary to ensure disciplined work performance and timely resources application to accomplish all tasking under the contract. The contractor shall be responsible for maintaining communication with the contracting officer (CO) and the contracting officer’s representative (COR), and to immediately notify both the CO and the COR of any problems that would prevent timely performance of this contract. The contractor is responsible for and required to implement, and maintain management control systems necessary to plan, organize, direct, and control all activities under this contract.

1.2 Background. MTS is a tool to enable safe testing of autonomous UAS systems at Edwards AFB. The unmanned Collaborative Combat Aircraft (CCA) programs are testing right now at Edwards AFB and other UAS customers are on the horizon. Currently, MTS lacks the software connections/interfaces to integrate with CCA (and other future UAS’s) A-GRA software environment for mission/flight autonomies, among other functions. If MTS had A-GRA compatible interfaces, it could be used to enable valuable risk reduction for CCA and other UAS Mission autonomy testing through the use of smaller, cheaper surrogate aircraft

1.3 Inherently Governmental Function. The contractor shall not perform inherently governmental functions as defined in FAR Subpart 7.5 in relationship to this PWS.

1.4 Period of Performance. This is a 6-month contract.

Page - 6 - of 39

1.5 Place of Performance. The contractor shall perform the services in the PWS at Edwards Air Force Base, CA and/or their own software development facility, depending upon specific deliverable item in question.

1.6 Specific Tasks. The section below outlines desired outcomes/tasks to be accomplished by the contractor during the performance of the contract.

1.6.1 Delivered product shall integrate an A-GRA Autonomy Interface within the existing MTS architecture such that A-GRA is exposed as a selectable autonomy option within the MTS Mission Planner and service set framework, resides within the existing MTS codebase (e.g., Autonomy Interface Service and related components) using existing MTS patterns for external interfaces (e.g., Message Processor plugins and MUSIC (MUlti-project Software InfrastruCture) messaging) and maintains maximum practical consistency with current MTS build and runtime practices.

1.6.2 Delivered product shall include an A-GRA Message Processor that resides natively within the existing MTS Autonomy Interface Service as a MUSIC-compliant plugin and implements the external A-GRA communication behavior entirely. The A-GRA Message Processor shall translate between external A-GRA/UCI messages and internal MTS MUSIC messages (Protocol Buffers) without modifying the core MUSIC framework beyond what is strictly necessary for integration.

1.6.3 Delivered product shall integrate A-GRA autonomy interface into the existing MTS Service Set creation tool. Upon selection of A-GRA, the Mission Planner Autonomy UI must dynamically reconfigure connection parameter fields (e.g., IPs, Ports, Serial) to match the A- GRA interface format and auto-populate with appropriate default values. The delivered product shall include unique A-GRA–based service sets that preserve all existing autopilot and MTS configuration properties and differ only by using the A-GRA Autonomy Interface in place of legacy autonomy interfaces.

1.6.4 Delivered product shall maintain existing MTS Run Time Assurance (RTA) safety behaviors (e.g., geofencing, vehicle constraints, remediation) when A-GRA is the active autonomy provider and shall handle malformed or missing A-GRA/UCI messages without crashing or degrading RTA enforcement.

1.6.5 Product documentation (e.g., user guidance, configuration instructions, and build/install procedures) shall be delivered as part of this contract to describe how to enable, configure, and operate the A-GRA Autonomy Interface, A-GRA Message Processor, A-GRA service sets, and any other changes to MTS implemented under this effort, and shall clearly specify how the delivered product operates on existing MTS TACE Air and Ground hardware architectures at ETF and how it can be built, installed, and configured by government personnel using either the current MTS build/deployment process or a fully documented equivalent.

1.6.6 Training shall be conducted by the contractor to ensure government personnel can install, configure, and employ A-GRA–based service sets and the A-GRA Autonomy Interface for mission planning and execution without contractor support.

Page - 7 - of 39

1.6.7 Factory-acceptance testing, including both Software-in-the-Loop (SITL) and Hardware-in-the-Loop (HITL) testing, shall be conducted by the contractor prior to live flight testing at Edwards AFB. On-site acceptance testing shall be conducted, with government support, at Edwards AFB. This may include but not be limited to HITL/SITL ground checks on flight-representative UAS hardware and live flight testing within approved UAS Airspace.

1.7 Historical Data. The tasks described above have not been performed in the past by any full-time equivalent employees present at 412 TW, Edwards AFB, CA.

1.8 Minimum Qualifications.

1.9 Deliverables

1.9.1 Below is a list of deliverables under this contract.

Support Area Title Delivery Date/Description

Technical Report Planning Documents As required Technical Report Trip Report/ Meeting

Minutes As required

Test Results (Factory Acceptance Test/On-Site Test)

MTS/A-GRA Acceptance Testing

FAT delivered prior to live flight testing.

Final test results upon Delivery.

Training Materials MTS/A-GRA Training (Manuals/Files?)

Upon Delivery

Training/Instruction MTS Employee Training During on-site execution/Upon Software Code MTS/A-GRA Source Code Upon Delivery

Software Release Notes MTS/A-GRA S/W Release Notes

Upon Delivery

Autonomy Govt. Ref.

Implementation (A-GRI)

MTS A-GRI Test Instance Shall be ready for on-site UAS testing. Final version delivered upon completion of contract.

1.10 Service Contractor Reporting Information (SCR). If required of the contractor, SCR is addressed by contract clause. [Contracting Officer, see the prescription at DFARS 204.1705 (a) to include the clause at DFARS 252.204-7023 (or its Alternate 1, as appropriate) in solicitations, contracts and awards, that meet the threshold at DFARS 204.1703 (a) (i) and are services assigned any of the Product Service Codes listed at DFARS PGI 204.1703.]

Page - 8 - of 39

1.11 Data. The government has unlimited rights to all deliverables of this contract.

1.12 Inspection. Deliverables will be inspected by the government within 10 workdays of receipt.

Progress meetings may be held as required.

1.13 Contractor Travel. Contractor may be required to travel to/from Edwards AFB during the performance of this contract for on-site installation, integration, flight testing and fine-tuning (e.g., bug fixes) of A-GRA compliant MTS software. Contractor may be authorized travel expenses not contrary to FAR 31.205-46 at rates that shall not exceed rates set forth in the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires government approval/authorization and notification of the CO or, if delegated, the COR. All invoices for travel reimbursement shall be accompanied by supporting receipts.

1.14 Small Business Subcontracting Program. [Not required for Small Business Set Aside but required for full and open competition.] When a Subcontracting Plan required under an included small business subcontracting plan clause is submitted, it must include the elements identified in FAR 19.704 and the cognizant clause and use one of the three types of subcontracting plans identified in subparagraph 1.11.1.

1.14.1 Types of Subcontracting Plans. The contractor may use one of three types of plans:

subcontracting plan, commercial plan (for commercial items), and the DoD comprehensive (test) plan. (See FAR 19.704 for additional guidance.) An Individual Subcontracting Report (ISR) shall be submitted semi-annually during contract performance for the periods ending March 31 and September 30. Reports are due 30 days after the close of each reporting period, unless otherwise directed by the CO. A report is also required for each contract within 30 days of contract completion. Summary Subcontract Reports (SSR), including those submitted for comprehensive subcontracting plans under the DoD Small Business Subcontracting Plan (Test Program), shall be submitted semi-annually for the 6 months ending March 31 and the 12 months ending September 30. Reports are due 30 days after the close of each reporting period. For commercial plans, the SSR is due 30 days after the end of the government's fiscal year. For the CPARS rating, the government may use the most recent ISR and/or SSR that the contractor submitted that will not delay the evaluation if the rating period is different than the subcontracting reporting period.

Page - 9 - of 39

2.0 SERVICE SUMMARY

2.1 General. The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success but do not represent all contract performance requirements. All contract performance requirements in this PWS will be monitored.

2.2 Performance Evaluation. Performance of a service shall be evaluated to determine whether or not it meets the performance requirements of this contract. Re-performance of unacceptable services at no additional cost is the preferred course of action when appropriate. In the case of issued Corrective Action Reports (CARs), the Contracting Officer shall take appropriate measures according to inspection of services clause in the contract. Corrective Action Reports may categorize nonconformance as minor, major or critical IAW the following FAR 46.101 definitions:

2.2.1 “Minor nonconformance” means a nonconformance that is not likely to materially reduce the usability of the supplies or services for their intended purpose or is a departure from established standards having little bearing on the effective use or operation of the supplies or services.

2.2.2 “Major nonconformance” means a nonconformance, other than critical, that is likely to result in failure of the supplies or services, or to materially reduce the usability of the supplies or services for their intended purpose.

2.2.3 “Critical nonconformance” means a nonconformance that is likely to result in hazardous or unsafe conditions for individuals using, maintaining, or depending upon the supplies or services;

or is likely to prevent performance of a vital agency mission.

2.3 Performance Objective Summary Table:

Performance Objective PWS Paragraph

Performance Threshold

1) Program Management & Reporting:

Oversight, accountability, and regular status reporting for all software development activities and resources.

1.9.1 No more than 1 late status

report per quarter.

Customer or Contracting Officer's Representative (COR) inquiries are responded to and a resolution plan is established within 48 hours.

2) Software Design & Architecture: Delivery of the system architecture design detailing how MTS will seamlessly interface with A-GRA.

1.6.2 Zero late deliveries of

design documents.

Government comments/issues regarding A-GRA compatibility must be addressed and resolved

Page - 10 - of 39 within 5 business days of receipt.

3) Software Development & Integration: Development/modification of MTS interfaces to successfully communicate with A-GRA compliant UAS platforms.

1.6.1 Zero Critical or High-

severity (Severity 1 or 2) software defects present in core A-GRA messaging interfaces upon release to the Government test environment.

4) System Testing (SITL & HITL): Execution and support of Software-in-the-Loop (SITL) and Hardware-in-the- Loop (HITL) testing to validate safe mission termination functionality.

1.6.7 100% of safety-critical test scripts must pass prior to live flight testing. Any testing anomalies must be documented and a fix provided within 72 hours.

5) Training & Documentation: Delivery of system documentation and training to 412 TENG Experimental Test Force (ETF) personnel to enable independent operation.

1.6.5-1.6.6 All training materials and user manuals delivered 15 days prior to final acceptance. Zero unresolved training capability gaps prior to system handover.

6) Final Delivery & Acceptance (TRL 9): Delivery of the final software product achieving Technology Readiness Level 9 (TRL 9) for live flight operations.

1.6.7 Zero unresolved critical

or major defects (Severity 1 or 2 punch list items) remain unresolved prior to final project completion and Government acceptance.

Page - 11 - of 39

2.4 Government Quality Assurance. The government shall inspect and evaluate the contractors’ performance to ensure services are received in accordance with requirements set forth in this contract. The COR will use the contractor’s work schedule, or modified version thereof, to record validation results. Results of the validation then become the official Air Force record of the contractor’s performance. Government surveillance of tasks not listed in the PWS Service Summary or by methods other than those listed in the PWS (such as provided for by the Inspection of Services 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 surveillance or otherwise in connection with nonconforming supplies or services of the contractor will be according to the terms of this contract and in accordance with FAR 46.102, FAR 46.407, DFARS 46.407 and DFARS PGI

46.407 which specify procedures for reductions of fee or for reductions to the price of a fixed-price contract when supplies are nonconforming or services are not performed or do not meet contract requirements.

2.4.1 The government will periodically evaluate the contractor’s performance in accordance with the Quality Assurance Surveillance Plan (QASP). The government may inspect each task as completed and increase the number of quality assurance inspections if deemed appropriate because of repeated failures discovered during surveillance inspections or because of repeated customer complaints. Likewise, the government may decrease the number of quality assurance inspections if performance dictates.

2.4.2 When an observation indicates defective contractor performance, the COR will require the contractor’s Contract Manager or representative at the site to initial the observation. The formal process is, when a performance threshold has not been met or contractor performance has not been accomplished, the COR will initiate and provide the CO a Corrective Action Report (CAR) for issuance to the contactor. The contractor shall respond to the CAR IAW instructions provided and in the CAR. While the formal process of this paragraph to address unacceptable contractor performance is always available, the Government reserves the right to initiate a less formal process involving the contractor, the COR and the CO meeting together at no additional cost to the Government regarding unacceptable contractor performance.

2.5 Performance Assessment

2.5.1 Periodic Surveillance. This method requires the COR to employ a “spot check” style of evaluation based on the contractor’s services. Periodic surveillance will be conducted on a scheduled basis (daily, weekly, monthly, quarterly, semi-annual or annually) and may be adjusted, based on quality trends.

Page - 12 - of 39

2.5.2 Customer Complaints. The COR will receive and investigate all complaints. The COR will be responsible for validating customer complaints. The CO shall make final determination of the validity of customer complaint(s) in cases of disagreement with the COR and the contractor.

Validated customer complaints shall be reperformed, if possible, within 3 business days of notification at no additional cost to the Government IAW the inspection clause of the contract and the direction of the Contracting Officer.

2.5.3 Review of Audits. COR reviews results of the contractor’s accepted quality management system audits and related quality metrics.

2.5.4 100 Percent Inspection. This method requires the COR to do 100 percent inspection on all tasks performed. Appropriate for tasks that occur infrequently. Usually only deals with Safety and/or Security, unless mandated by an Air Force Instruction (AFI) or industry standard.

2.6 Quarterly Progress Meetings. The CO, the Government Project Manager (GPM), COR, other government personnel as appropriate, and the contractor shall meet quarterly to discuss the contractor’s performance.

The following issues, at a minimum, shall be discussed:

- Opportunities to improve the contract,

- Any modifications required of the contract,

- Unsatisfactory inspections,

- Valid customer complaints against each performance objective observed, and

- Steps taken by the contractor to prevent occurrences in the future.

The contractor shall provide a summation of unsatisfactory inspections and customer complaints and provide insight into any identified trends.

2.6.1 Minutes. The minutes of these meetings will be reduced to writing, signed by the CO and any other signatures as deemed appropriate, distributed to the functional area and the contractor.

Should the contractor not concur with the minutes, the contractor will provide a written notification within 5 working days to the CO identifying areas of non-concurrence for resolution.

2.7 Contracting Officer’s Representative (COR). CORs are representatives of the CO and will participate in the administration of this contract. After award of the contract, the contractor will be provided a letter identifying the COR and setting forth their duties and authorities. The COR is not authorized to change any of the terms and conditions of the contract/task order.

Page - 13 - of 39

2.7.1 Acquisition Team Meetings. The contractor’s Contact Manager (CM) with the CO, Contract Administrator (CA), COR, and other government personnel constitute an acquisition team [See FAR 1.102 (c)] and shall meet on a regular basis. The Acquisition Team will establish how often meetings are needed based on contract complexity. As a subset of the Acquisition Team, Government members of the Acquisition Team are often referred to as the Multi- Functional Team (MFT) and may meet as determined by the MFT. The contractor may request a meeting with the CO when the contractor believes such a meeting is necessary. If the CO or CA deems necessary, written minutes of any such meetings shall be recorded by the CA in the contract file and signed by the GPM and the CO or CA. If the contractor does not concur with any portion of the minutes, such nonconcurrence shall be provided in writing to the CO within 10 calendar days following receipt of the minutes.

2.8 Quality Control. In compliance with the applicable contract inspection clause(s), develop and maintain an effective quality control program to ensure services are performed IAW this PWS, applicable laws and regulations and IAW best commercial practices.

2.8.1 Quality Control Plan (QCP). The contractor shall be required to submit and maintain an acceptable QCP. Within [Insert number of days] days after contract award and within 14 days after any need for changes to an existing QCP, the contractor shall submit a QCP to the CO. The CO will notify the contractor of acceptance or required modifications to the plan. The contractor shall make appropriate modifications and obtain acceptance of the plan by the CO within [Insert number of days] days. The contractor’s QCP shall contain, at a minimum, the following descriptive items:

2.8.1.1 a. The inspection system to cover all services. Description shall include specifics as to the areas to be inspected on a scheduled and unscheduled basis, frequency of inspections, and the title and organizational placement of the inspector(s).

2.8.1.2 b. The methods to be used for identifying and preventing defects in the quality of services performed.

2.8.1.3 c. How the records will be kept. Records must document all inspections and corrective or preventive actions taken.

2.9 Contractor’s Performance. The government assesses a contractor’s performance on an on-going basis, both positive and negative, and provides a record on a given contract during a specified period of time.

Page - 14 - of 39

2.9.1 Past Performance Information (PPI). PPI can be provided to other government agencies, as requested.

2.9.2 Contractor Performance Assessment Report (CPARS). Depending on the estimated value of the contract, formal assessment and reporting of contractor performance is required and is documented using the CPARS system. An assessment usually provided on an annual basis is sent to the contractor’s representative for their comment. The contractor will have up to 60 days to review and comment on the assessment.

3.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.1 Government Furnished Services (Base Support). The government will provide a Coordination/Project Management Point of Contact (POC) to provide assist contractor employees with base access and travel/access to appropriate areas (e.g., North Base ETF facility) where contract work will be performed. Temporary office/desk/meeting spaces will be available to confer with ETF and Range personnel during contract work. The government will provide a Technical/UAS Operations (POC) for coordination of all Edwards AFB onsite integration and testing activities. The government will provide access to all hardware and materials necessary for the onsite integration and testing of the delivered product during the contract. This includes, but may not be limited to: ETF sUAS (Group 1-3) and their subcomponents (e.g., autopilots, autonomy agents, etc.), MTS/TACE Ground and Air hardware/software components, lab

3.2 Automated Data Processing Equipment. The government will not provide computers for use on the local area network (LAN), email, and the internet for work related to this contract.

3.3 Emergency Medical Services. Edwards AFB will provide emergency medical services for contractor personnel in performance of services under this contract IAW AFMAN 41-210 Chapter 2. The contractor shall ensure that the Government is reimbursed at the full-reimbursement rate for emergency medical services provided. The contractor shall provide to the 412th Medical Group, the name of a physician and/or hospital to which injured personnel can be transferred for further treatment and care after receiving initial emergency treatment on base. All mishaps will be promptly reported to the base safety office through the COR.

3.4 Security Police and Fire Protection. Phone number for Security Forces Squadron, [Insert local Security Forces Squadron’s number]; Fire Protection, 911.

3.5 Government Furnished Facilities. The government will provide temporary access to facilities noted in 3.1 above for the purposes stated.

3.6 Government Furnished Property (to include equipment and material). The 412 TW (ETF/RANS) will provide the contractor with MTS software code and A-GRA/A-GRI resources if the contractor does not already have access to them via an approved code repository and/or at their own facility.

Page - 15 - of 39

3.7 Government Furnished Property (GFP). The contractor shall establish GFP accountability under this contract in accordance with the included Government Property clauses, if any. This may include conducting a joint inventory with the Government if deemed necessary by the Government’s Property Administrator (Property Administrator). If GFP is being transferred from a previous contract with the same contractor, the Property Administrator may waive the requirement for a full physical inventory based on the reliability of existing records and condition of the property. However, the contractor must validate and document all GFP to ensure contract-specific accountability is accurately reflected in PIEE; accepting a formal transfer of GFP within the PIEE GFP Module may suffice as record validation when authorized by the Property Administrator. The contractor shall sign receipt for all equipment provided by the government.

The contractor shall determine and certify the working order and condition of all equipment.

Items of equipment missing or not in working order shall be recorded. If the contractor does not elect to participate in the inventory within the timeframe listed above, the contractor must accept as accurate, the listing and stated condition of equipment provided by the government. If the contractor participates in the inventory but does not agree with the government representative's determination as to the working order of the equipment, the equipment will be turned in as excess or the matter will be turned over to the CO for resolution. The contractor shall designate a property custodian throughout the life of the contract to receipt and account for all GFP. By completion or extension of each yearly option of the contract, an inventory of GFP shall be conducted by the contractor and an audit performed by the government Property Administrator (PA). All equipment in need of repairs/maintenance shall be repaired/maintained by the government, depending on contract type and clauses elected for use in contract or unless the damage was caused by willful negligence of contractor.

3.8 Contractor Furnished Property and Services. Except for those items or services specifically stated to be government-furnished in Section III and any appendixes, the contractor shall furnish everything required to perform this contract in accordance with all of its terms. The following mentioned requirements are not all inclusive of the contractor furnished items and services required in the performance of this contract.

Page - 16 - of 39

4.0 GENERAL INFORMATION

[The general information section covers any other area of concern and will vary greatly depending on the requirement. Select the paragraphs below that apply to the instant acquisition and adjust the paragraph numbers accordingly.

A note about training required of contractor personnel: To avoid complications and the potential for additional costs, all training required of contractor personnel under this contract, regardless of provider, should be described in the various sections of this PWS. When training is required under authority of a rule or regulation, that specific reference should be cited in the PWS language requiring that training.]

4.1 The contractor shall perform the services required under this contract during the following hours: 0800-1630 Monday thru Friday except Federal holidays or when the government facility is closed due to local or national emergencies, administrative closings, or similar government directed facility closings. For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. On occasion, an employee will be required to work on weekends and Federal holidays. The government will notify the contractor within 24 hours of such occurrence.

4.2 Recognized Federal Holidays: Contractor is not required to perform work on recognized Federal holidays.

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

*If the holiday falls on a Saturday, it will be observed on the preceding Friday. If the holiday falls on Sunday, it will be observed on the following Monday.

Page - 17 - of 39

5.0 Contract Personnel

5.1.1 Contract Manager (CM). The contractor shall provide a contract manager and alternate(s) who are knowledgeable of [Insert the requirement]. The contractor shall submit the name, address, telephone number and a resume of the CM to the CO within 2 days of contract start date. The list shall be kept current throughout the life of the contract. The CM or alternate(s) shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The CM or alternate(s) shall be available within [Insert amount of time] to meet on the installation with government personnel designated by the CO to discuss problem areas.

The CM and alternate(s) shall be able to read, write, and speak English. The CM shall be able to effectively communicate with contractor employees. Qualifications for the CM are listed below:

5.1.2 Personnel Roster. The contractor may be required to provide a personnel roster consisting of names and other pertinent personnel data to the requiring activity for the purposes of 100% accountability real-world and exercise situations. The personnel roster shall be updated as individuals are removed and added.

5.1.3 Contractor Employees:

5.1.4 [The following 4 paragraphs are optional. If not applicable, please delete. If applicable, please fill in a paragraph number]

5.1.5 Certifications. Contractor employees shall have current and valid professional certifications and licenses required to perform the work in this PWS, prior to contract award. All certification and licensing requirements by Federal, State, and local agencies shall be complied with at the contractor's expense.

5.1.6 Contractor Qualifications. The contractor shall utilize employees possessing adequate training, skills, and knowledge to perform the requirements of this contract.

5.1.7 Employee Training. The contractor shall give all training required to meet requirements of the PWS unless otherwise specified within the PWS or as otherwise approved by the CO. The contractor shall maintain training and experience records for each employee during the period of this contract that reflect sufficient personnel are qualified to accomplish all tasks required by this contract. Provide status of employee training upon the government’s request.

Page - 18 - of 39

5.1.8 English Language. Employees who deal directly with customers will be required to communicate clearly and concisely with the customers in English. This requirement is strictly for the purpose of efficiently performing the contract tasks.

5.1.9 Use of Government Employees. The contractor shall not employ any person who is an employee (either military or civilian) of the U.S. Government if employing that person would create a conflict of interest. In addition, the contractor shall not employ any person who is an employee (either military or civilian) of the Department of the Defense if such employment would be contrary to the policies contained in DAFI 64-106 – Contracting – Contractor Labor Relations Activities - Chapter 3, Employment of Off-Duty Government Personnel.

5.1.10 Employment of Spouses/Dependents. The contractor shall not employ any person who is a spouse or dependent child of a Department of Defense employee (either military or civilian) when such employee would be placed in a conflict of interest or appearance of a conflict of interest by virtue of such employment.

5.1.11 Identification of Contractor Employees. All contract personnel attending meetings, answering government telephones, in other telephone conversations and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of others that they are government officials. They must also ensure that all documents, reports produced by contractors and formal or informal correspondence are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor employees shall be required to wear badges or other visible identification for meetings with Government personnel. [The drafter may want to edit the previous sentence so as to include the particular form of required contractor identification whether Badges, a uniform or other visible identification…Some appropriate means of contractor identification is required, so as to avoid the prohibited and unauthorized practice of personal services contracting; the elements of contractor identification in this PWS Template subparagraph are informed by the characteristics and descriptive elements of personal services contracting described at FAR 37.104; see the prohibition at FAR 37.104(b) and also see DFARS 211.106.]

Page - 19 - of 39

5.2 Conflicts of Interest

5.2.1 Organizational Conflict of Interest (OCI). Contractor and subcontractor 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 OCI as defined in FAR Part 9.5. Any potential instance of OCI must be reported to the CO immediately.

5.2.2 Personal Conflict of Interest (PCI). The term "PCI" means that a contractor employee assigned to the contract has interests which (i) may diminish his/her capacity to give impartial, technically sound, objective assistance and advice in performing this contract, (ii) may otherwise result in a biased work product under this contract, or (iii) may result in an unfair competitive advantage. Any potential instance of PCI must be reported to the CO immediately.

6.0 MISCELLANEOUS INFORMATION

6.1 Freedom of Information Act (FOIA). All official government records affected by this contract are subject to the provisions of the FOIA (5 U.S.C. 552/DoDM 5400.07_AFMAN33- 302). Any request received by the contractor for access/release of information from these records to the public (including government/contractor employees acting as private citizens), whether oral or in writing, shall be immediately brought to the attention of the CO for forwarding to the Base FOIA Manager to ensure proper processing and compliance with the Act.

6.1.1 Controlled Unclassified Information (CUI). The contractor shall comply with DoD Instruction 5200.48_Department of the Air Force Instruction 16-1403 Controlled Unclassified Information (CUI), and the CUI requirements in this contract. The CUI regulation cited in this paragraph sets policy, assigns responsibilities, and prescribes procedures for CUI in the identification, creation, sharing, marking, safeguarding, storage, dissemination, decontrol, disposition, destruction, and records management of CUI documents and materials and establishes training required. [When CUI is included in a requirements package, COs should evaluate the extent to which the requiring activity has fulfilled their responsibilities for submission of CUI contractor requirements in accordance with DFARS PGI 204.7303-1, Safeguarding Covered Defense Information and Cyber Incident Reporting. The Contracting Officer should include this paragraph [4.6.2. (1) & (2)] as applicable and ensure that CUI under the contract is addressed and handled according to regulation and, if included, the clause(s) prescribed at DFARS PGI 204.403 and DFARS 204.404-70.]

6.1.2 Any contractor employee CUI training required under DoDI 5200.48 _Department of the Air Force Instruction 16-1403 Controlled Unclassified Information including initial and annual CUI training shall be accomplished following coordination with the COR/cognizant local CUI authority.

Page - 20 - of 39

6.2 Notification of Debarment/Suspension Status. The contractor shall provide immediate notice to the CO in the event of being suspended, debarred or declared ineligible by any other federal department or agency, or upon receipt of a notice of proposed debarment from another DoD Agency, during the performance of this contract.

6.3 Correspondence. The government singularly identifies each project with a contract number at time of award. The contract number is a unique identifier to purposely and permanently represent an awarded project. The government issued contract number is to be referenced on all official communication starting upon notice of award.

6.4 Post Award Conference. The contractor agrees to attend any post award conference convened by the CO IAW FAR Part 42.5. These meetings shall be at no additional cost to the government.

6.5 Privacy Act. Work on this contract may require that personnel have access to information protected by the Privacy Act. Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations when handling such information.

6.6 Records. All records created and received by the contractor in the performance of this contract shall be maintained and readily accessible. Records shall remain the property of the government. The contractor must maintain and dispose of records following the requirements established in Air Force Instruction 33-322, Records Management, and Information Governance Program, specifically Chapters 1,2, 3, 4 Section 6.1 of Chapter 6 and Attachment 1. The contractor must turn over all records to the Government upon completion of the contract unless otherwise directed by the Contracting Officer. The contractor may contact the Edwards AFB Records Management Office at 661-277-3015 for training on records management at no cost as contractor ensures compliance with federal, DoD and Air Force record keeping requirements.

6.7 Insurance. The contractor shall obtain the necessary insurance as required by FAR part 28.3.

The minimum amounts of insurance will be maintained IAW FAR 28.307-2.

6.8 Subcontracting. [If applicable] The contractor shall ensure that any subcontractor providing services on behalf of the contractor has been approved by the CO prior to any such performance.

The subcontractor shall not have a negative performance history or be suspended or otherwise prohibited from doing business with the government.

6.9 Data Rights. The government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be government owned and are the property of the government with all rights and privileges of ownership/copyright belonging exclusively to the government. These documents and materials may not be used or sold by the contractor without written permission from the CO. All materials supplied to the government shall be the sole property of the government and may not be used for any other purpose. This right does not abrogate any other government rights.

Page - 21 - of 39

6.10 Fire Prevention. The contractor shall take all necessary precautions to prevent fires in the units and contractor-furnished and government-furnished facilities while performing any work under this contract. In the event fires do occur, the contractor shall immediately notify the Base Fire Department at 911. The contractor shall then notify the requiring activity and the CO. The contractor shall brief and document its employees monthly in fire safety issues and procedures in reporting fires.

6.11 Flightline Driving. Contractor personnel, prior to operating a vehicle on the airfield, must meet the requirements of DAFI 13-213, Airfield Driving, and must pass all required tests prior to issuance of an AF Form 483 and possess a valid state issued driver’s license and valid AF Form 483 while driving on the Airfield IAW DAFI 13-213 paras. 2.10., 3.3, & 3.4.. Contractor shall maintain records of this training and make them available upon COR or CO request.

6.12 Hazardous Materials

6.12.1 All Safety Data Sheets (SDS) – Safety Data Sheet submissions accompanied by a completed Contractor Hazardous Material Approval Form are required for chemicals/materials not sourced from an installation HAZMART and must be approved by the Edwards AFB Hazardous Material Program including the initial submission by the apparently successful offeror prior to award, and prior to use for any subsequent SDS submissions by the contractor during performance of the contract. [Contracting Officer, in coordination with the Government Program Manager, you will want to determine if hazardous chemicals/materials are being procured and if so include FAR clause 52.223-3 in full text, as prescribed at FAR 23.304(a)(1);

this clause in connection with this PWS subparagraph will give the Contracting Officer the ability to consider the apparently successful offeror non-responsible and ineligible for award if the apparently successful offeror fails to submit the required HM documents (Safety Data Sheets and HM Approval Forms) or does not obtain the required approval of HM document submissions prior to award. If HM usage will be significant, you might want to consider Hazardous Materials as a topic of solicitation instructions and Evaluation Criteria for award.]

6.12.2 The Contractor shall utilize the Contractor Hazardous Materials Usage Form to capture monthly usage data for hazardous chemicals/materials not sourced from an installation HAZMART that were used on the installation in performance of this contract. The Contractor shall submit the usage form to the Contracting Officer identified COR/Government Project Manager (GPM) by the 5th of the following month during performance and at completion of work.

6.12.3 The Point of Contact for questions concerning Hazardous Materials or SDS submissions prior to award is the Contracting Officer. After award and during contract performance, contact the Edwards AFB Environmental Management Office at (661) 277-1401 (for AFRL, call (661) 277-5135) or email 412CEG.CEVC.HMWorkflow@us.af.mil, for the HM exempt list and guidance regarding HM regulatory, usage, and tracking form requirements.

mailto:412CEG.CEVC.HMWorkflow@us.af.mil

Page - 22 - of 39

6.12.4 Any products that meet the criteria of “Hazardous Waste” must be tracked until permanently removed from government property. Criteria for identifying hazardous waste are contained in Subpart C of 40 CFR Part 261 and Chapter 11, Articles 1-5, of 22 CCR.