CHAC PWS.pdf

FA9304-24-R-5002

Page - 1 - of 29

Quality, Schedule, AFTC

Performance Work Statement (PWS) Template

FOR EDWARDS AFB CONTRACTING OFFICERS ONLY

Requirement Title: ________________________ POC: _____________________

Requiring Organization: ____________________ Phone: ____________________

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.

3. 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. If the acquisition is either critical to agency mission accomplishment or requires relatively large expenditures of funds, positive and negative incentives are tied to the QASP measurements.

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.

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 - 2 - of 29

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-15: Energy Efficiency in Energy-Consuming Products

52.223-17: Affirmative Procurement of EPA-Designated Items in Service and

Construction Contracts

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

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)

Page - 3 - of 29

PERFORMANCE WORK STATEMENT

FOR

COUNTER-HYPERSONIC / AIRCRAFT C3

AT

Edwards AFB, CA

1 February 2024

Page - 4 - of 29

CHAC Services

Table of Contents

1.0 SECTION I: DESCRIPTION OF SERVICES

1.1 General Scope

1.2 Background

1.3 Inherently Governmental Function

1.4 Period of Performance

1.5 Place of Performance

1.6 Specific Tasks

1.7 Historical Data

1.8 Deliverables

1.9 Contractor Travel

1.10 Contractor Phase-In and Phase-Out Transition

2.0 SECTION II: SERVICE SUMMARY

2.1 General

2.2 Performance Evaluation

2.3 Government Quality Assurance

2.4 Performance Assessment

2.5 Quarterly Progress Meetings

2.6 Contracting Officer’s Representative

2.7 Quality Control Plan

2.8 Contractor’s Performance

3.0 SECTION III: GOVERNMENT FURNISHED PROPERTY and SERVICES

3.1 Government Furnished Services

3.2 Government Furnished Facilities

3.3 Government Furnished Property to include Equipment and Material

3.4 Contractor Furnished Property and Services

4.0 SECTION IV: GENERAL INFORMATION

4.1 Contractor Personnel

4.2 Continuation of Essential DoD Contractor Services During Crisis

4.4 Conservation of Utilities

4.5 Environmental Protection

4.6 Miscellaneous Paragraph

4.7 Security

4.8 Safety

5.0 SECTION V APPENDICES & EXHIBITS - TBD

APPENDIX 1 Definitions, Abbreviations, and Acronyms

APPENDIX 2 Government Furnished Facilities

APPENDIX 3 Applicable Publications and Forms

Page - 5 - of 29

Page - 6 - of 29

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General Scope. This is a contract to provide development and operations of the Digital Integrated Air Defense System (DIADS) in support of Counter-Hypersonic / Aircraft C3 (CHAC) for the 772d Test Squadron (TS). The Government will 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 non-personal services necessary to perform development and operations of DIADS in support of CHAC 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. The DIADS mission is to provide a realistic, mission level, high-fidelity threat

Integrated Air Defense System (IADS) environment to test blue force mission effectiveness.

DIADS is a high-fidelity mission level simulation environment that models threat IADS.

DIADS supports a wide variety of test, training, and analysis customers by assessing blue force mission effectiveness and providing a realistic training environment. It includes software representations of the sensors, command and control (C2), fusion algorithms and weapons used by modern threats. Blue aircraft and electronic attack (EA) can be represented inside of DIADS and DIADS can interact with external systems, models, and hardware in the loop (HITL) components via standard interfaces. The simulation can be run faster than real-time or in real-time for man-in-the-loop operation. The real-time operation enables extensive interface capabilities and flexible support for a wide variety of live, virtual, and constructive (LVC) simulations.

The DIADS program office is part of the 772d Test Squadron (TS) and has both program office and test organization responsibilities. The program office manages multiple improvement and modernization programs for the DIADS software model. The TIPP funded HADES program will expand the threat spectrum in DIADS and add multiple new classes of threat systems. Improvement projects sponsored by

Test and Evaluation Threat Resource Activity (TETRA) will increase integration efforts with intelligence center threat models. The DIADS program office supports a wide variety of test, training, and analysis customers. This customer support includes software development, integration at customer facilities, training support, test planning, test execution, analysis, reporting, and general operations of

DIADS. The program office manages the DIADS software release schedule and is the configuration control agent for all DIADS software development.

Page - 7 - of 29

The DIADS program office is co-located with the Mission Simulation Laboratory (MSL). The MSL is a multi-tier security domain that can easily be configured to support a variety of constructive and virtual simulation customer needs. The MSL also serves as a classified development environment for a variety of customer programs and is used to perform acceptance testing on new releases of DIADS.

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 9-year contract with 6-month option timeline.

1.5 Place of Performance. The Contractor shall perform the services in the PWS as required at Edwards AFB, Lackland AFB, the Contractor’s facility, various DIADS customer facilities, customer facilities, DoD facilities, various DoD Contractor facilities, and international customer sites. Work at customer locations will be on an as needed temporary basis.

1.6. Specific Tasks.

1.6.1 DIADS Capability Development Requirements:

1.6.1.1 Perform system engineering analysis of existing capabilities, customer requirements and intelligence trends to achieve a sound technical understanding of the Electronic Warfare (EW) problem area.

1.6.1.2 Perform system engineering, integration, development, and maintenance to provide the Government requested capabilities.

1.6.1.3 Execute a phased development and delivery, if appropriate. To provide a useable capability at the conclusion of each phase.

1.6.1.4 For each phase provide: detailed testable requirements for each capability being delivered; mapping of development requirements to system level requirements; revisions, if needed, to the overall system architecture; detailed design documentation for the items being developed; integration and test plans;

test procedures; performance of qualification tests; test reports; verification and validation reports;

and system operations, maintenance, and training manuals.

1.6.1.5 Prepare and deliver documentation on technical requirements, design and design decisions, plans, and procedures in written technical documentation. The Government will identify and approve required documentation taken from the Contract Data Requirements List (CDRL) list for each development activity.

1.6.1.6 Prepare and present technical reviews (e.g., Preliminary Design Review (PDR), Critical Design Review

(CDR)) on technical requirements, design, plans, and procedures. Perform technical interchange meetings (TIMs) to resolve specific program issues requiring additional attention and discussion.

1.6.1.7 Prepare and present technical training on newly developed capabilities and systems.

1.6.1.8 Prepare and present project schedules (at project start) and update when needed. Changes to schedule will be coordinated and approved by the Government Program Manager (PM). Pending impacts to schedule will be identified immediately to the PM. Immediately is interpreted as when first identified by the Contractor.

Page - 8 - of 29

1.6.2 DIADS Software Development Requirements:

1.6.2.1 Development of new DIADS features will be software intensive. The Contractor must demonstrate an inherent, successful software development capability that meets recognized Institute Electrical and

Electronics Engineers (IEEE), International Organization for Standardization (ISO), and Software

Engineering Institute (SEI) standards and guidelines. This includes the goal of achieving a Capability

Maturity Model Integration (CMMI) rating minimum of IV, on the SEI scale of I to V or equivalent in a comparable system. The Contractor should have a demonstrated history of on-time software development projects.

1.6.2.2 Provide Configuration Management (CM) of DIADS software versions for the duration of the contract.

1.6.2.3 Provide resolution of user-generated Change Requests (CRs); build and maintain a log of all CRs;

investigate and analyze reported problems; generate descriptions of proposed solutions; upon approval of the appropriate Configuration Control Board (CCB), implement and document corrective actions.

Prioritize all uncorrected CRs. Provide descriptions, priorities and status of all CRs.

1.6.2.4 Coordinate with the CCB for approval of all DIADS software release content.

1.6.2.5 Release and distribute new DIADS versions as approved by the CCB.

1.6.2.6 Maintain one baseline version of DIADS and additional branches as necessary. New capabilities are generally targeted for the main baseline, their maturity, or a variety of other reasons that may prevent their inclusion. The Contractor should be prepared to maintain additional DIADS development or production branches as required.

1.6.2.7 Maintain all external interfaces to provide compatibility with customer integration efforts. Current interfaces include Distributed Interactive Simulation (DIS), All Purpose Structured Eurocontrol

Surveillance Information Exchange (ASTERIX), Test and Training Enabling Architecture (TENA), and

Google Protocol Buffer (ProtoBuf).

1.6.2.8 Provide source and executable files for all software developed. Provide files necessary for software compilation and linking and provide command procedures developed to support operation and test of software.

1.6.2.9 Ensure DIADS is capable of meeting real-time and faster-than-real-time run time requirements.

Measuring faster-than-real-time requirements will be based on a standardized laydown of no less than twenty IADS players and no less than 2 blue aircraft, with one providing noise jamming against no less than 3 IADS early warning radars. Hardware for such a test will utilize one server using Contractor recommended CPU, GPU, and RAM. A quarterly report of DIADS run speed using the latest release will be submitted to the government.

1.6.2.10 Update DIADS functional requirements as capabilities are added to DIADS.

1.6.2.11 Update DIADS factory acceptance test (FAT) procedures to account for software changes. Execute

FAT procedures prior to distribution of new DIADS versions and document results in a FAT report.

1.6.3 MSL Support Requirements:

1.6.3.1 Install new releases of DIADS in the MSL and conduct site acceptance testing.

Page - 9 - of 29

1.6.3.2 Provide system administration support to the MSL. The MSL has Microsoft Windows and Linux system administration duties on local networks at multiple classification levels.

1.6.3.3 Support generation of Risk Managed Framework (RMF) documents and system security posture.

Support the implementation of appropriate controls.

1.6.3.4 Provide support in the development and modification of DIADS scenarios, laydowns and DIADS player library databases utilizing appropriate intelligence sources and support Government personnel in the operations and maintenance of the DIADS model.

1.6.3.5 Develop new DIADS players from various sources of information including intelligence data, blue systems specifications, test data, open-source references, or other applicable references.

1.6.3.6 Develop and maintain software tools to assist in the output and analysis of DIADS data.

1.6.3.7 Plan, develop, and present training courses on the design, maintenance, and operation of the delivered systems.

1.6.4 DIADS Customer Support Requirements:

1.6.4.1 The DIADS Program Office supports a wide variety of test, training and analysis customers. The

Contractor must be knowledgeable in these areas and be ready to support additional DIADS customers.

1.6.4.2 Support the development and planning of customer programs.

1.6.4.3 Support the development and delivery of customer test plans as required.

1.6.4.4 Develop software to support customer needed features such as interfaces or new model capabilities.

These new features are generally targeted for the main DIADS baseline software through the release process, though the Contractor should be prepared to support customer-specific software branches.

1.6.4.5 Implement players and scenarios in DIADS needed to meet customer objectives and maintain configuration control on the customer specific players.

1.6.4.6 Support the deployment, integration, and maintenance of DIADS at customer facilities.

1.6.4.7 Support the DIADS execution component of customer programs.

1.6.4.8 Analyze DIADS simulation results and deliver reports of the results.

1.6.4.9 Provide customers with verification and validation (V&V) reports as tasked. These V&V reports may cover general DIADS V&V areas or customer specific V&V topics.

1.6.4.10 Compare customer test data to modeling and simulation (M&S) results from DIADS and report on the results.

1.6.5 DIADS General Requirements:

Page - 10 - of 29

1.6.5.1 Support the verification and validation of the DIADS model. Develop or update V&V plans as model changes require. Execute those plans and provide a report on the results. The testing and documentation should be configuration controlled and automated to the greatest extent practical.

1.6.5.2 Provide engineering development and upgrade support to all DIADS programs.

1.6.5.3 Provide support to Government personnel in the setup, testing and operation of DIADS systems.

1.6.5.4 Recommend fixes and improvements to the DIADS model.

1.6.5.5 Identify trade-spaces in new designs and perform sufficient engineering analysis to propose best-case tradeoffs for new capabilities.

1.6.5.6 Perform cost-trade analyses, as required, of technical alternatives for all design and integration options.

Present the results of these analyses to the Government.

1.6.5.7 The Contractor should maintain a complete CMMI systems engineering process for all modifications to

DIADS and give the Government insight into CMMI practices and artifacts as requested.

1.6.5.8 Utilize a design approach that emphasizes modularity and an open architecture to facilitate future system growth.

1.6.5.9 Maintain flexibility to utilize common simulation, test, and training interfaces.

1.6.5.10 Perform security engineering for all development activities, coordinate security requirements with

Government security specialists, and assist as required with the applicable certification of systems for classified operations.

1.6.5.11 Develop operations and maintenance requirements and sustainment plans for the life-cycle support of systems.

1.6.5.12 Create and maintain documentation for the operation of DIADS, technical documentation, verification and validation tests, model architecture, training and other applicable documentation as required.

1.6.5.13 Provide quality assurance processes for all development activities which will be documented to the

Government in a Quality Control Plan (QCP). This QCP will be submitted for Government review and approval.

1.6.6 DIADS Management Requirements:

1.6.6.1 Provide a PWS, Work Breakdown Structure (WBS), CDRL items and subcontracting plans in response to Government tasking. Upon start of any effort after award, an initial kick-off meeting will be held to ensure a complete understanding of the work scope and objectives.

1.6.6.2 Create and maintain a generalized program management plan to coordinate the activities of systems engineering, systems test, quality assurance, risk management, and configuration and data management.

Provide a more detailed plan at the individual task order level(s). Submit to the CO for approval no later than sixty days after contract award.

1.6.6.3 Create project execution plans for each task order based on the Statement of Work (SOW).

Page - 11 - of 29

1.6.6.4 Plan, staff, and execute all work under this contract in accordance with approved program plans and operating procedures, current security requirements, applicable policies and procedures, and approved schedules.

1.6.6.5 Establish any subcontracts and associated Contractor agreements required to ensure satisfactory task completion.

1.6.6.6 Provide monthly cost and schedule reporting for all work performed under this contract. The WBS level for reporting will be specified in the specific SOW.

1.6.6.7 Provide a monthly status summary of all technical accomplishments, potential problems, and plans for all work performed under this contract. Include all active delivery orders in a single monthly report.

1.6.6.8 Provide documentation called out in the CDRLs.

1.6.6.9 Provide data management of all contract documentation. Provide for control and tracking of document revisions and versions.

1.6.6.10 Provide for the receipt, generation, and storage of classified material in accordance with the contract DD

Form 254.

1.6.6.11 Coordinate with the 412 EWG security office to support system accreditation and certification.

1.6.6.12 Establish an Operations Security (OPSEC) program for all activities on this program. This program must be documented and forwarded to the 412 EWG security office and cleared as sufficient.

1.6.6.13 Provide general support related to general customer activities such as users’ groups, conferences, working groups and other related meetings and activities.

1.6.6.14 Conduct periodic program schedule and cost status reviews to ensure that the Government maintains program visibility and problems are identified immediately for quick and satisfactory resolution.

Develop, present, and lead discussions on critical performance, cost, and schedule data. Maintain records of the meetings, including minutes and Action Items (AIs). Track AIs and report status changes in subsequent management reviews.

1.6.6.15 Conduct TIMs as required on specific technical issues. Maintain records of these meetings, including minutes and AIs. Track AIs and report status changes in subsequent TIMs and management reviews.

1.6.6.16 Define and conduct reviews for major level development milestones to present and demonstrate progress.

1.6.6.17 Participate in project related management and technical meetings with the Government and other

Contractors on an as-needed basis. Report on the substance of each meeting and any Ais allocated to, or potentially effecting, Government organizations and other Contractors. Identify and describe all issues of concern to the 412 EWG.

1.7 Historical Data. The tasks described above have been performed in the past by 30-40 full-time equivalent employees.

1.8 Deliverables.

Page - 12 - of 29

1.8.1 Below is a list of deliverables under this contract.

Support Area Title Delivery Date/Description

Management Monthly Status Reports 15 days after EOM

Management Management Plan As required

Management Report/record of meeting minutes Monthly as needed

Management/ Technical Funds and hour expenditure Report 15 days after EOM

Technical System/Subsystem Specifications As required

Technical System/Subsystem Design Description As required

Technical Software Design Description As required

Technical Interface Design Description As required

Technical Software Test Description As required

Technical Software Version Description As required

Technical Computer Software Product As required

Technical Report Software Test Plan As required

Technical Report Software Test Report As required

Technical Report Software User Manual As required

Technical Report Training Materials As required

Technical Report Study/Services As required

1.8.2 Inspection. Deliverables will be inspected by the Government within 15 workdays of receipt. Progress meetings may be held as required.

1.9. Contractor Travel.

1.9.1 Contractor will be required to travel during the performance of this contract to support customer requirements, test and training events, meetings, technical interchanges, and conferences. Contractor will be authorized travel expenses at rates that shall not exceed those set forth in the Joint Travel

Regulation (JTR) and the limitation of funds specified in this contract. All invoices and supporting receipts submitted to DCAA for travel reimbursement shall also be made available to the COR for review at any time.

1.10 Contractor Phase-In and Phase-Out Transition.

1.10.1 Contractor Phase-In: No phase-in is required as this a follow-on contract.

1.10.2 Contractor Phase-Out: If a different contractor is selected for the CHAC follow on, the outgoing

Contractor shall allow the incoming Contractor to interview for employment, the outgoing Contractor’s personnel, if work interruption time is reasonable.

1.10.2.1 The outgoing Contractor shall provide sixty calendar days of on-the-job training (OJT) to the incoming

Contractor. The outgoing Contractor shall integrate the incoming Contractor personnel into the regular work schedule to maximize OJT benefits. Contractor personnel to be trained shall possess, prior to training, all required special skills needed to perform the specific tasks in this PWS. The training objective is to enhance technical skills so that the transfer of responsibilities will be efficient.

1.10.2.2 During the sixty-day calendar day training period, the outgoing Contractor shall perform all requirements in the PWS.

Page - 13 - of 29

SECTION II

2.0 Service Summary (SS)

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, i.e., FAR 52.246-4, 52.246-5, or 52.212-4(a). Corrective Action

Reports may categorize nonconformance as minor, major or critical IAW the following FAR 46.101 definitions:

“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.

“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.

“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.

SS#

Performance Objective

[The Service required— usually a shall statement]

PWS Section

Performance Threshold

[This is the maximum acceptable error rate ]

Rating Criteria

(Based on Findings before

Re-performance unless otherwise noted)

Quality

The Contractor shall maintain

100% of current available external interfaces unless deemed unnecessary by the government.

1.6.2.7 All interfaces maintained 100% = Satisfactory

<100% = Unsatisfactory

The contractor shall provide a quarterly efficiency report to the government to measure faster-than-real-time capabilities of the DIADS software.

1.6.2.9 Maintain >8x faster-than-

real-time using the test described in para. 1.6.2.9

>32x = Exceptional

32x to >16x = Very Good

16x to >8x = Satisfactory

8x to >4x = Marginal

<=4x = Unsatisfactory

Page - 14 - of 29

Schedule

Deliver Task Order (TO) requirement IAW Period of

Performance

1.5.4 Deliver TO requirement

on time, no more than two late submissions per quarter unless waived.

0 - Exceptional

1 - Very Good

2 - Satisfactory

3 - Marginal

>4 - Unsatisfactory

Cost Control

The contractor shall not have any task order costs over run the agreed upon amount.

1.6.1.8

1.6.6.1

1.6.6.6

0 task over runs. 100% = Satisfactory

<100% = Unsatisfactory

The contractor shall not have any task order under run

>10%.

1.6.1.8

1.6.6.1

1.6.6.6

No TOs deviate >10% from projected cost for all factors within contractor control.

- 3% = Exceptional

- 5% = Very Good

- 10% = Satisfactory

>- 10% to -15% = Marginal

>- 15% = Unsatisfactory

Management

The contractor shall provide monthly status briefing on subcontractor performance as applicable.

4.4.9 No more than 3 delayed

annually.

12 = Exceptional

11 = Very Good

10 = Satisfactory

7-9 = Marginal

1-6 = Unsatisfactory

The contractor shall conduct monthly change request status briefings.

1.6.2.3

1.6.2.4

No more than 3 delayed annually.

12 = Exceptional

11 = Very Good

10 = Satisfactory

7-9 = Marginal

1-6 = Unsatisfactory

2.3 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 becomes the official Air Force record of the contractor’s performance. Government surveillance of tasks not listed in the PWS 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 will be according to the terms of this contract.

2.3.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.3.2 When an observation indicates defective performance, the COR will require the contractor’s Contract

Manager or representative at the site to initial the observation. When a performance threshold has not been met or contractor performance has not been accomplished, the COR will initiate and provide the CO

Page - 15 - of 29 a Corrective Action Report (CAR) for issuance to the contactor. The contractor shall respond to the CAR

IAW instructions provided and in the CAR.

2.4 Performance Assessment.

2.4.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 quarterly basis and may be adjusted, based on quality trends.

2.4.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.4.3 Review of Audits. COR reviews result of the contractor’s accepted quality management system audits and related quality metrics.

2.4.4 100 Percent Inspection. This method requires the COR to do 100 percent inspection on all task 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.5 Quarterly Progress Meetings. The CO, Government’s Program Manager (PM), 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.5.1 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.6 Contracting Officer 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.

2.6.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

Page - 16 - of 29

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 PM and the CO or CA. If the contractor does not concur with any portion of the minutes, such nonoccurrence shall be provided in writing to the CO within 10 calendar days following receipt of the minutes.

2.7 Quality Control Plan (QCP). The contractor shall be required to submit and maintain an acceptable QCP.

Within 60 days after contract award or within 14 days after the need for changes to an existing QCP, the contractor will 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 30 days. The contractor’s QCP shall contain, at a minimum, the following descriptive items:

2.8 Contractor’s Performance. The government assesses a contractor’s performance on a quarterly basis, both positive and negative, and provides a record on a given contract during a specified period.

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

2.8.2 Contractor Performance Assessment Report (CPARS). Formal assessment and reporting of contractor performance 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 shall have up to 60 days to review and comment on the assessment. Past Performance assessment reports will be protected by all parties and treated by government personnel as marked “Controlled Unclassified Information

(CUI)/Source Selection Sensitive Information in accordance with FAR 2.101, 3.104 and 42.1503”.

Page - 17 - of 29

SECTION III

3.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.1. Government Furnished Services (Base Support). The Government will provide limited office space for permanently stationed employees at Edwards AFB. The Government will provide standard office accommodations and access to Government IT systems. Seating is limited and exact number of desks should be negotiated with the DIADS Program Manager. The Government will also provide base access and Air Force network access to a select number of Contractor employees.

Custodial Service. The government shall provide custodial services for restroom facilities in base facilities IAW the current base custodial contract. All inquiries regarding scheduling and level of custodial services will be directed to the COR.

Postal/Installation Distribution. The Base Information Transfer System is available for official government mail, messages, and information pickup distribution point at 15 N Muroc, Bldg 3502.

Security Police and Fire Protection. Phone number for Security Forces Squadron: (661) 277-2465, (661)

277-3340, (661) 277-3341.Fire Protection, (661) 277-4540, (661) 277-4541, 911.

Telephone Service. The government will provide local and DSN telephone services FOR OFFICIAL

USE ONLY use at no cost to the contractor. Commercial long-distance calls shall be at the contractor’s expense.

Utilities. The government will provide all electricity, water and sewage at no additional cost to the contractor. The contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities, which include turning off the water faucets or valves after using the required amount to accomplish requirements under this PWS.

3.2 Government Furnished Facilities. The government will provide office space in the DIADS MSL.

3.3 Government Furnished Property (to include equipment and material). The Government will provide limited items necessary for the Contractor to effectively accomplish the requirements of this PWS.

These include Disc Producers, and secure shredder. The Contractor must effectively interface with and comply with applicable, current Government directives and protocols to effectively utilize these services and material.

3.4 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.

SECTION IV

4.0 GENERAL INFORMATION

4.1. Contract Personnel

Page - 18 - of 29

4.1.1. 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.

4.1.2 Contractor Employees:

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

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.

4.1.3 Use of Government Employees.

The contractor shall not employ any person who is an employee 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 of the Department of the Defense if such employment would be contrary to the policies contained in AFI 64-106, Chapter 1, Industrial Labor Relations Activities.

4.1.4 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.

4.1.5 Identification of Contractor Employees. All contract personnel attending meetings, answering government telephones, 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 members of the public that they are government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

4.2 Conservation of Utilities. The contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities.

4.3 Environmental Protection. The contractor shall comply with all applicable federal, state and local laws, regulations and standards that are or may become applicable to contractor’s activities in performance of this PWS.

4.4 MISCELLANEOUS PARAGRAPHS:

4.4.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.

4.4.2 Controlled Unclassified Information (CUI).

Page - 19 - of 29

(1) 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.

(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.

4.4.3 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.

4.4.4 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.

4.4.5 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.

4.4.6 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.

4.4.7 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.

4.4.8 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.

4.4.9 Subcontracting. 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. The contractor shall provide monthly status meetings detailing the performance of the subcontractor.

4.4.10 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.

4.4.11 Inclement Weather. If the base closes due to inclement weather, the contractor will be released, by the installation commander, with the general population of the base at no decrement to contract price. The

Page - 20 - of 29 contractor will follow the local procedures for reporting in inclement weather as advertised on local television and radio stations.

4.4.12 Section 508 Compliance. The contractor shall support the government in its compliance with Section

508 throughout the development and implementation of the work to be performed. Section 508 of the

Rehabilitation Act of 1973, as amended (29 U.S.C. 794d) requires that when federal agencies develop, procure, maintain, or use electronic information technology, federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who do not have disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

4.5 Security

4.5.1 General:

4.5.1.1 The contractor shall comply with all base security regulations and with actions dictated by force protection condition changes/measures. For real-world situations/exercises, changes to force protection conditions could impact contractor performance of work and can include denial of access to the installation to perform work.

4.5.1.2 The contractor and its employees shall comply with all base traffic regulations.

4.5.1.3 Contractor employees are prohibited from possessing weapons, firearms, or ammunition, on themselves or within contractor-owned or privately owned vehicle while on Air Force installations.

4.5.1.4 The contractor shall report suspicious activity to Security Forces at (661) 277-4009 in a timely manner.

4.5.2 Required Training

4.5.2.1 Contractor shall maintain and make available to the COR, within 30 days after award, records of any training of contract employee and subcontract employee required by DFARS Clause 252.204-7004

Antiterrorism Awareness Training for Contractors, both initially and annually thereafter. Level I -

Antiterrorism Awareness Training may be taken at https://jkodirect.jten.mil/Atlas2/faces/page/login/Login.seam or as Coordinated by the COR with the requiring unit Anti Terrorism Representative (ATR).

4.5.2.2 Contract employees requiring a Common Access Card (CAC) shall receive documented Information

Assurance (IA) training, by the government, prior to receiving access to the local area network (LAN).

Authorized users will receive initial IA orientation and annual awareness training to ensure they know, understand, and apply the IA requirements of Air Force information and IAs. The minimum orientation and awareness requirements for users are outlined in DoD 8570.01-M. IA Program. The contractor shall comply with the established Command, Control, Communication, and Computers (C4) Systems IA program to integrate security education, training, and awareness covering the Communications Security

(COMSEC), Computer Security (COMPUSEC), and Emissions Security (EMSEC) disciplines.

4.5.3 Security Clearance Levels. Contractor personnel performing work under this contract may need as high as a Top Secret clearance at time of contract award, and must maintain the level of security required for https://jkodirect.jten.mil/Atlas2/faces/page/login/Login.seam

Page - 21 - of 29 the life of the contract. Exact clearances required will be discussed with the CO/COR and managed by

412 EWG Security. The security requirements are in accordance with the DD254.

4.5.4. Additional Security Requirements:

4.5.4.1 Physical Security. The contractor shall be responsible for…