47QFSA23K0089_PWS_2024-03-28 draft.docx

RTIS Cover Page GSA Acquisition ID: 47QFSA23K0089 GSA Solicitation ID: TBD GSA Task Order ID: TBD

Date: 03/01/2024

GSA Senior Contracting Officer (CO):

Randi Williams Phone: 404-861-1364 Email: randi.williams@gsa.gov

GSA Contract Specialist (CS):

Dorothy “Hae” Monroe Phone: 720-468-8023 Email: dorothy.monroe@gsa.gov

Client Organization:

Air Force Research Laboratory (AFRL) Spectrum Warfare Division, AFRL/RYW Rapid Technology Integration Office (RTIO) Wright Patterson AFB, Dayton, OH

Contracting Officer’s Representative:

XXX

Phone: XXX Email: XXX

Project Name:

Rapid Technology Integration Support 3

GSA SIN: 54151S Information Technology Professional Services

NAICS: 541512 - Computer Systems Designs Services (SB size standard = $34M) PSC: DA01 - IT and Telecom – Business Application/Application Development Support Services – Labor.

Period of Performance:

Base Year (BY): 8/1/2024 – 7/31/2025 Option Year 1 (OY1): 8/1/2025 – 7/31/2026 Option Year 2 (OY2): 8/1/2026 – 7/31/2027 Option Year 3 (OY3): 8/1/2027 – 7/31/2028 Option Year 4 (OY4): 8/1/2028 – 7/31/2029 Extension of Services (EOS): 8/1/2029 – 1/31/2030

CLIN Structure:

X001 Labor X002 Travel X003 Order-Level Materials

Industry Partner:

XXX

POC:

XXX

Rapid Technology Integration Support 3 (RTIS3) Performance Work Statement (PWS)

1.0 INTRODUCTION.

Under this effort, work defined in this Performance Work Statement (PWS) is to be accomplished for the Air Force Research Laboratory (AFRL), Spectrum Warfare Division (RYW), Rapid Technology Integration Office (RTIO), Wright Patterson Air Force Base (WPAFB), Dayton, OH, through the General Services Administration (GSA), Federal Acquisition Service (FAS), Assisted Acquisition Services (AAS), APEX 2 Sector 1.

1.1 Organization.

AFRL/RYW, Bldg 620, 2241 Avionics Circle, Wright-Patterson AFB, OH 45433

1.2 Background.

AFRL Spectrum Warfare Division, AFRL/RYW, is charged with supporting the warfighter through the integration of various commercial off the shelf (COTS) components and government off the shelf (GOTS) components utilizing superior systems engineering principles to deliver unique capabilities that are both functional and secure. This technology integration includes the entire cycle, from assessment through production and sustainment. This task order focuses on technology integration at any phase, or all phases of the lifecycle as defined in the specific requirement.

Using over a decade of experience running the Rapid Technology Integration Office (RTIO), AFRL/RYW has found that advanced engineering analysis, coupled with direct interaction with the warfighter, is critical to delivering the best science and technology (S&T) necessary to successfully complete the United States mission. The RTIO’s mission is to provide agile stop-gap analysis, prototyping, and deployment support on a rapid timeline, on the order of days, to address emergent DoD capability gaps without an existing Program of Record (POR) to respond.

The customers of AFRL/RYW are composed of a wide spectrum of users that include Senior Leadership in the United States Government (USG), Combatant Commands, Intelligence Agencies, and other Department of Defense (DoD) entities. Deployment solution environments may include in-garrison, mobile use, traveling, austere locations, and wartime conditions. These environments may be permissive or denied depending on specific application and use case.

AFRL/RYW has found that adherence to its three security tenets produces the most effective solutions against threats that have been presented by the adversary. The security tenets are:

1.2.1. Minimize System Susceptibility

The contractor will minimize system susceptibility by focusing on what’s critical. Identify what is critical to protect and reduce the scope and number of critical system security elements and hence the overall system susceptibility. This has the effect of limiting the attack surface for the particular use-case.

1.2.2. Minimize Threat Accessibility

The contractor will minimize threat accessibility by moving critical elements “out-of-band.” Out-of-band refers to moving critical technology and security elements from the control of the operating system or the system’s general-purpose processor to a trusted processor or a trusted operating enclave. Minimizing the threat’s accessibility minimizes opportunity to exploit the system.

1.2.3. Reduce Threat Capability

The contractor will reduce threat capability by denying attack vectors and tools through the use of detect and react security elements operating inside the threat’s Observe, Orient, Decide, and Act (OODA) loop. OODA stands for “Observe, Orient, Decide, and Act”, a concept originally proposed by Col John Boyd. To SPI, being ‘inside the threat’s OODA Loop’ means autonomic protection technology that can detect and react to threat reverse engineering activities by imposing hard penalties before the threat can observe, orient, decide, or react.

1.3 Periods of Performance

This task order includes options for additional periods of performance in accordance with FAR 52.217-8 and FAR 52.217-9.

2.0 GENERAL SCOPE

The Contractor shall provide a Rapid Technology Integration Center of Excellence through a turn-key capability, composed of both facilities and personnel, to seek out, analyze, design, fabricate, modify, test and deploy the integration of non-traditional technical solutions that are at a minimum innovative, and ideally disruptive to support the AFRL/RYW Rapid Technology Integration Mission. This center of excellence, to be known as the Rapid Technology Integration Center, will be responsible for coordinating and understanding customer requirements, designing and developing warfighting solutions, fielding and supporting the solutions in operational pilots, and collecting and analyzing data from the implementation, deployment, and support of rapid technology integration enabled systems. Specific performance requirements are listed below.

2.1 Task Order Objectives.

The overall objective of this task is to operate and maintain a fully functional center of excellence information technology facility including classified laboratories, office, and conference environments in direct support of the AFRL/RYW Rapid Technology Integration Support (RTIS) mission. This Performance Work Statement (PWS) describes the capabilities that AFRL/RYW requires for establishing a center of excellence for information technology professional solutions in the rapid integration of commercial off-the-shelf (COTS) systems for warfighter needs.

AFRL/RYW, in the Spectrum Warfare Division, is charged with rapid delivery of novel systems that provide immediate value, but may have a limited performance lifetime, thus requiring short time to market and frequent product turn as in the commercial marketplace. Like the commercial marketplace, AFRL/RYW must deliver new and disruptive technologies at a near real-time pace and foster emerging technological solutions that may cannibalize even recently deployed solutions, to remain relevant and effective. As such, these solutions must move from initial concept to prototype deployment in exceedingly short time frames, and cannot encounter delays due to:

· Lack of innovative concepts,

· Risk adverse thinking,

· Sluggish procurement,

· Lack of on-site testing capability,

· Lack of on-site fabrication capability,

· Inability to meet varied security requirements,

· Inflexibility due to organizational size or structure, and

· Inexperience delivering rapid innovation AFRL/RYW requires a Center of Excellence that can deliver items quickly. This center of excellence will analyze, design, test and deploy numerous systems, primarily based on or adapted from COTS items or systems. Inherent in this effort is the ability to interact and respond to a wide range of U.S. government agencies and customers, and the ability to deliver the utmost in total system security across a wide range of information spectra (including optical, audible, radio frequency, infrared and physical) while simultaneously delivering the maximum capability to the war fighter. The goal of this effort, simply stated, is to provide the war fighter with a nation’s best technical center of excellence that can perform at the speed and innovation of the commercial marketplace while at the same time providing secure solutions.

Of specific interest is the blended solution of COTS components with enhanced hardware/firmware/software that transforms the commercial grade solution into a military grade solution, while maintaining ease of use, leveraging of the rapid technology cycles of COTS electronics, and preserving the economies of the COTS marketplace. Further, mobility and flexibility are essential attributes of this effort. The center of excellence and hence this task should support the RTIS functional mission areas of deploying COTS products integrated into military grade solutions through innovation of disruptive technologies for the Department of Defense (DoD) war fighter across multiple domains; non-traditional deployment of solutions that do not readily align with traditional Certification and Accreditation (C&A) guidelines; verification and validation of deployed techniques; analysis of the value proposition of such technologies in the strategic DoD portfolio; and education of the DoD community on RTI technologies and processes.

2.2 Location / Place of Performance.

The place of performance shall be the contractor’s location which must be located within 50 miles of 2241 Avionics Circle, Wright Patterson AFB, OH 45433. The contractor’s facility must have a Facility Clearance (FCL) at the Top Secret/Sensitive Compartmented Information (TS/SCI) level and shall be fully accredited throughout contract award.

The Contractor shall support AFRL/RYW engineering assessment development and other government processes needed to perform the AFRL/RYW mission. The contractor’s facility shall incorporate comprehensive security in depth and novel techniques to provide the highest level of integrity and availability of the program and consider both external and insider threats. In addition to providing the requisite support for this part of the AFRL/RYW mission, integrated Information Technology (IT) and physical security support shall be provided to ensure AFRL/RYW mission effectiveness.

The contractor’s facility must include Sensitive Compartmented Information Facility(ies) (SCIFs) that support multiple concurrent non-overlapping compartments with distinct security measures and access control(s). The contractor’s facility must have a SCIF that supports fabrication, testing, and evaluation of SCI hardware. The SCIF must accommodate storage of items larger than 16" x 16" x 16". In addition, the facility must include a secure multi-bay garage capable of receipt and modification of large commercial items including multiple full-size vehicles and/or trailers not to exceed 30’ in length or 10’ in height.

AFRL/RYW requires classified meeting space for up to 50 participants for technical interchanges under their rapid technology assessment mission. The contractor shall provide meeting space at the Top-Secret level for this number of participants with 48 hours prior notice for active task orders. AFRL/RYW also requires classified meeting space at the TS/SCI level for up to 15 participants and the Contractor shall provide required space within 48 hours prior notice. The Government anticipates approximately two (2) meetings per month.

Due to the security considerations and system utilization, it is anticipated that some work (approximately 10% or less) associated with this task order will be performed at Government facilities.

2.3 Facility Security Clearance

The Government considers the requirement for TS/SCI level facility clearances a definitive responsibility matter. The contractor shall provide proof of current facility credentials for themselves and any teaming/subcontracting partners which must be maintained throughout contract performance. The security requirements are outlined in the accompanying DD254.

Failure to comply with FCL requirements is cause for task order termination.

2.4 Specified Labor.

The Contractor shall accomplish task orders utilizing qualified personnel IAW the CLIN requirements. Personnel must possess the appropriate combinations of education, training, trustworthiness determination/security clearance and experience/skills required. Personnel with higher skill levels may be substituted during performance at no additional cost.

The services for this task order are principally for services performed by labor categories considered bona-fide executive, administrative, and professional. The Contractor is fully responsible to ensure compliance with the Department of Labor regulations regarding pay and benefits for all employees working on this task order or any other federal contract.

Required Skills and Capabilities.

All Contractor employees shall possess the current and necessary training, qualifications, experience, and clearances to accomplish the PWS requirements. The following is a sample list of the skills/capabilities/equipment knowledge contractor employees shall possess to perform services on this task order:

· Mobile device programming (i.e., Android phones and tablets) at the kernel and application levels

· Linux kernel programming

· Reverse Engineering (hardware and software)

· Internet Protocol Stack

· Expertise in communication systems to include voice, video, and data

· Radio frequency shielding knowledge

· Antenna design

· Fabrication to include design, packaging, and milling

· Small circuit board design/fabrication

· Circuit board rework capability

· Cryptography systems (i.e., inline encryptors, data at rest encryptors) Personnel Clearances All prime and subcontractor employees working on this task order shall possess a TS clearance prior to performance on this task order. The contractor shall submit validation that individual employees of the contractor (or subcontractor) meet this requirement prior to performance on this task order. Where SCI level clearance is required, the contractor shall submit validation prior to employee performance (contractor or subcontractors) against the TS/SCI requirement.

2.5 Key Personnel.

The Contractor shall identify key personnel for the task order. Key personnel may not be substituted, added, or removed by the contractor unless approved by the Contracting Officer (CO) in writing. Any substitution of personnel must be of equally or better qualified individuals as those identified in the task order quote. The contractor’s written request to substitute, add, or remove key personnel must be submitted at least 15 calendar days (unless the CO provides written exception) prior to personnel actions.

The contractor must identify at least one contractor employee by name and position (and duties, as applicable) who will be the liaison with the Government regarding the task order issues.

2.6 GSA MAS SIN / Professional Services

The services required by this task order are principally for services performed by labor categories considered bona-fide executive, administrative, and professional. The contractor is fully responsible to ensure compliance with Department of Labor regulations regarding pay and benefits for all employees working on this task order or any other federal contract.

The GSA Multiple Award Schedule (MAS) Special Item Number (SIN) for these services is 54151S Information Technology Professional Services.

2.7 DD Form 254 – Contract Security Classification Specification The contractor shall comply with the requirements of the DD Form 254 “Contract Security Classification Specification” and any addendums/supplements for this task order. The DD254 will be in draft form prior to award and a signed version will be incorporated into the award via modification.

Prior to performance on this task order, all prime and subcontractor employees assigned to this task order shall possess a TS clearance. Validation of employees’ clearance is required prior to performance against task order requirements. Where SCI level clearance is required, employees’ clearance (contractor or subcontractor) shall be verified prior to performance against the SCI requirement.

General Operations Security (OPSEC) procedures, policies and awareness are required to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the life cycle of the task order. The Critical Information List (CIL) will be provided upon request by the Sensors Directorate Information Protection Office. While working on the government installation, OPSEC guidance will be provided by the Sensors Directorate Information Protection Office.

The contractor must receive Government approval prior to disclosure of classified information to subcontractors.

2.8 Security Directives

The Contractor (and/or any subcontractor) and its employees shall comply with Homeland Security Presidential Directive (HSPD)-12, Policy for a Common Identification Standard for Federal Employees and Contractors, OMB M-05-24, and FIPS 201, Personal Identity Verification (PIV) of Federal Employees and Contractors. For additional information, see HSPD-12 policy at: https://www.dhs.gov/homeland-security-presidential-directive-12).

Reference Identification and Identity of Contractor Personnel for additional information.

2.9 Transport

The Contractor and its employees shall be accountable and document all activities associated with the transport of government information, devices, and media transported outside controlled areas and/or facilities. These include information stored on digital and non-digital media (e.g., CD-ROM, tapes, etc.), mobile/portable devices (e.g., USB flash drives, external hard drives, and SD cards).

All information, devices and media must be encrypted with DOD-approved encryption mechanisms to protect the confidentiality, integrity, and availability of all government information transported outside of controlled facilities.

2.10 Contractor Personnel Conduct and Performance.

Contractor personnel assigned to this task order must adhere to appropriate standards of conduct and performance. The Contractor management shall provide sufficient oversight and supervision to ensure employees (direct or subcontracted) are fulfilling their technical responsibilities and doing so in the best interest of the Government. If the conduct of any employee of the contractor or subcontractor conflicts with the best interests of the Government, the contractor/employer shall take prompt corrective action including, but not limited to, removing the employee from performing services on this task order.

If the Government determines that a contractor or subcontractor employee poses a threat to the safety, security, or welfare of government installations, personnel, or operations, that employee may be immediately removed from performing services/projects on this contract or removed and/or barred from a government installation. Employment and staffing difficulties shall not be justification for failure to meet established schedules, and if such difficulties impair performance, the Contractor may be subject to termination.

3.0 PERFORMANCE REQUIREMENTS

3.1 Facility Support for Innovation of Disruptive Technologies The Contractor’s center of excellence shall support AFRL/RYW engineering development and other government processes needed to perform the AFRL/RYW mission. The center shall incorporate comprehensive security in depth and novel techniques to provide the highest level of integrity and availability of the program and consider both external and insider threats. In addition to providing the requisite support for this part of the AFRL/RYW mission, integrated Information Technology (IT) and physical security support shall be provided to improve AFRL/RYW mission effectiveness in at least 3 of the 4 mission areas (technology discovery, analysis, design/fabricate/test, and deployment). The Contractor shall provide a monthly briefing detailing status, accomplishments and issues. The monthly briefing shall consist of a presentation and verbal discussion.

3.2 Technical Interchange Support

AFRL/RYW frequently requires classified meeting space for up to 50 participants for technical interchanges under their rapid technology integration mission. The Contractor shall provide meeting space at the Top-Secret level for this number of participants with 48 hours prior notice during the task term. AFRL/RYW also requires classified meeting space at the Top Secret/Sensitive Compartmented Information level for up to 15 participants and the Contractor shall provide required space with 48 hours prior notice. The meeting space facility shall be located within 50 miles of the Dayton, OH/Wright Patterson AFB area. The Government anticipates approximately two (2) meetings per month. The Contractor shall record and provide Technology Interchange Meeting (TIM) minutes to the Government three (3) working days after the completion of each TIM. The TIM minutes shall accurately reflect discussions, questions, and lessons learned during the TIM. Also, any action items resulting from the TIM shall be enumerated in the minutes for tracking to completion or deletion by the Government. In addition, the Contractor shall provide a monthly briefing detailing status, accomplishments and issues. The monthly briefing shall consist of a presentation and verbal discussion.

3.3 Support for Non-traditional Deployments

The Contractor shall provide support for the deployment of technologies that pose unusual challenges to the traditional C&A process. Where novel or disruptive IT solutions are fielded by AFRL/RYW, C&A often dominates the deployment timeline. The Contractor shall seek to address, and where possible, minimize or eliminate these delays. Familiarity with the C&A process is a prerequisite, but innovative consideration of the underlying requirements of the process, coupled with parallel development of both the technology itself and the associated C&A responses, shall be employed to find ways to streamline the C&A process. Beyond finding ways to lessen the time burden of C&A, the Contractor shall also examine in detail alternate ways to meet the underlying requirements of Federal Information Security Management Act (FISMA). In addition to providing the requisite support for this part of the AFRL/RYW mission, E&S support shall be provided to improve AFRL/RYW mission effectiveness in both of the mission areas (C&A process efficiencies and alternative ways to meet FISMA). The Contractor shall provide an Alternative Certification and Accreditation Methodologies Report fifteen (15) working days after each integration or deployment activity with either a new protection technology or a new customer. This report shall present techniques and strategies to comply with existing certification and accreditation policies while minimizing the timeline to achieve necessary approvals to deploy technologies. Leveraging of existing authorities and accreditations while enhancing the functionality of a system is desired. In addition, the Contractor shall provide a monthly briefing detailing status, accomplishments and issues. The monthly briefing shall consist of a presentation and verbal discussion.

3.4 Data Gathering, Analysis and Evaluation

The Contractor shall provide an integrated IT services solution to support DoD wide reporting and analysis of data from the implementation, deployment, and support of rapid technology integration enabled systems. The Contractor solution shall include provisions for a help desk like function that directly supports the AFRL/RYW mission in gathering, collating, and analyzing adoptability and sustainability data. The Contractor solution shall incorporate novel physical security and computer security measures to support the collection and analysis of classified performance data of the AFRL/RYW mission. The Contractor shall provide a Technology Adoption and Sustainment Report, which shall explain the support effort, describe problems and the approach the Contractor took to resolve those problems and report on lessons learned from the technology development and demonstration, insertion, and support activities. It shall cover all technologies supported. The report is due fifteen (15) working days after each 2-month period. In addition, the Contractor shall provide a monthly briefing detailing status, accomplishments and issues. The monthly briefing shall consist of a presentation and verbal discussion.

3.5 Rapid Technology Integration

Under this task order, the Contractor shall be responsible for completing 4-6 technology integration projects per year. It is estimated that each technology integration project will consist of a prototype and from 1 to 20 deployed units.

A typical project would begin with a technical interchange between government personnel and the contractor to understand customer requirements and then rapid development of an initial prototype for field testing. Upon user feedback, a prototype would be modified until accepted by the customer. Upon customer acceptance, deployment units would be rapidly procured/developed and undergo operational fielding and testing. Logistics support during the task period would be required for minor technology alterations and maintenance failures. The RTIS project deliverables shall provide a workable solution for the end user in the appropriate operational environment and enable the transition of the developed technology to a third party if desired. The Contractor shall provide RTI Project hardware, software, and associated documentation within thirty (30) working days after end user acceptance of the initial prototype. Documentation shall include user manuals, maintenance manuals, and, if appropriate, network diagrams and hardware schematics of equipment developed. Documentation should be sufficient for a third party to recreate the technology with minimal effort. In addition, the Contractor shall provide a monthly briefing detailing status, accomplishments and issues. The monthly briefing shall consist of a presentation and verbal discussion.

An example project would be to provide a secure end node device that can communicate on a private network utilizing COTS hardware in a battlefield environment. This end node must be able to withstand advanced logical attacks and basic physical access attacks. An unclassified case study artifact is available to demonstrate an RTI project completed under a previous task order.

4.0 DELIVERABLES

Deliverables identified in the d Deliverable Table (4.0) and Performance Matrix (5.5) shall be delivered securely via email to the Contracting Officer’s Representative (COR), Contracting Officer (CO), Contract Specialist (CS), and when appropriate, to the RTIO’s client. Unclassified deliverables are to be uploaded into ASSIST as a Post Award Collaboration (PAC), select “deliverable” as the collaboration type, no later than the dates specified in the Deliverable Table (5.0). Other deliverables shall be submitted as required by the COR. The required Government approvals are identified in the “Deliver To” column; evidence of the approved deliverable shall be in ASSIST. All deliverables become property of the U.S. Government. The deliverables may include monthly briefings, quarterly reports, annual reports, self-assessments, and the reports such as protection technology demonstration reports, technology insertion and deployment reports, and adoption and sustainment reports. There shall be a monthly briefing and then a quarterly report for the last month of the quarter. There shall be three quarterly reports; an annual report shall summarize the three quarterly reports and the last quarter of the year. Additional briefings and reports will be associated with meetings and projects. Reports shall be submitted to the Government as electronic documents in Microsoft Office or Adobe PDF. All hardware, software, and associated documentation to include user manuals, maintenance manuals, etc. for all RTI projects developed under this task shall be delivered to the Government.

Management Plan

5.0 QUALITY CONTROL

5.1 Quality Control.

The Contractor shall provide and maintain a Quality Control Plan (QCP) that contains, as a minimum, the items listed below to the GSA Contracting Officer (CO) for acceptance not later than ten workdays after award. 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 within thirty calendar days from the date of award or prior to performance start whichever is earlier.

The QCP shall include the following minimum requirements:

· A description of the inspection system to cover all major services and deliverables. The description shall include specifics as to the areas to be inspected on both a scheduled and unscheduled basis, frequency of inspections, and the title of inspectors.

· A description of the methods to be used for identifying and preventing defects in the quality of service performed.

· A description of the records to be kept to document inspections and corrective or preventative actions taken.

All records of inspections performed shall be retained and made available to the Government upon request throughout the task performance period, and for the period after task completion, until final settlement of any claims under this task.

5.2 Management Plan

Pursuant to paragraphs 3.0 – 3.5 above, the Contractor shall submit a Management Plan (MP) within 30 days of task award, and then provide updates as required. The MP should provide a breakout of how each of the tasks under this task will be supported, to include tracking and assessing progress on each task. This plan should provide ongoing insight into project status and accomplishments and help to ensure that schedules and deliverables for each task are being met.

5.3 Inspection and Acceptance

The Government will evaluate the Contractor’s performance of this task order utilizing the Contractor’s approved QCP, the Government’s Quality Assurance Surveillance Plan (QASP) and the PWS requirements. The Government maintains the right to inspect any service or deliverable in accordance with the Inspection clauses applicable in the basic contract and this task order. Government surveillance of tasks not listed in the Performance Matrix or by methods other than those listed in the Performance Matrix (such as provided in the Inspection clauses) may occur. For those tasks listed in the Performance Matrix, the COR or other designated evaluator will follow the method of surveillance specified in this task order (i.e. 100 percent inspection). Government personnel will record all surveillance observations. When an observation indicates defective performance, the COR or other designated evaluator will require the Contractor manager or representative at the site to initial/sign the observation. The initialing/signing of the observation does not necessarily constitute concurrence with the observation. It acknowledges that the Contractor has been made aware of the non-compliance. Any action taken by the CO as a result of surveillance will be according to the terms of the task order and/or basic contract.

5.3.1. Unacceptable Performance.

Unless otherwise directed by the Government, the Contractor shall immediately take action to correct or replace all non-conforming services or deliverables at no additional cost to the Government. If the Contractor fails to perform at an acceptable quality level, the Government may issue a Task Discrepancy Report (TDR) to the Contractor. The Contractor shall complete their portion of the TDR and provide any supporting documents to support their response. The TDR response and supporting documents shall be submitted NLT the required due date established by the Government. The TDR response and supporting documents will be submitted in ITSS along with the Government’s evaluation of the response and any actions the Government deems appropriate.

5.3.2. Problem Resolution.

The Contractor shall build a quality culture that self-identifies problems or areas for improvement. The Contractor shall strive to proactively identify problems, or potential issues, affecting performance and proactively work to resolve them. The Contractor shall report these items to the COR as soon as possible. Verbal reports will be followed up with written reports when directed by the COR, or the Contractor may submit a written report to identify the issue and how it was resolved in order to record these actions for the Government’s consideration. Identified discrepancies in which the Contractor has proactively taken action to remedy the discrepancy and provide confidence of future compliance, the Government COR may determine that a formal task discrepancy report will not be issued. The Contractor remains responsible to correct problems/issues that need resolution. The Contractor shall work cooperatively with the Government to resolve issues as they arise.

5.4 Quality Assurance Surveillance Plan (QASP)

A Quality Assurance Surveillance Plan (QASP) is developed to evaluate contractor actions while implementing this Performance Work Statement (PWS). It is designed to provide an effective surveillance method of monitoring contractor performance for each listed objective on the Services Summary. The QASP provides a systematic method to evaluate the services the contractor is required to furnish on a quarterly basis.

Government surveillance may occur at any time during the performance period.

5.5 Performance Requirements Summary (PRS)

This Performance Requirements Summary (PRS) identifies critical success factors for the contract. It identifies both the performance objectives for those factors and the performance threshold required for each performance objective. The Government reserves the right to surveil all services called for in the contract to determine whether the performance objectives were met.

· The PRS contains performance objectives the Government will monitor.

· The absence of any contract requirement from the PRS shall not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract.

· The PRS along with the Deliverables Table in 4.9 will be used as the baseline to develop a QASP. The QASP will identify the surveillance methods the Government will use to evaluate the Contractor’s performance.

· Methods of surveillance can change after contract award based upon, but not limited to:

· Acceptance of a contract or QC plan, and

· Performance Performance of a service will be evaluated to determine whether it meets the performance threshold. Re-performance is the preferred method of correcting any unacceptable performance. The Contractor shall provide the COR and TPOC a written response as to why the performance threshold was not met, how performance will be returned to acceptable levels, and how recurrence of the cause will be prevented in the future.

5.6 Performance Matrix

Standard (s)

Documentation shall be submitted to the Government in Microsoft Office or Adobe PDF electronic format.

The minutes presented shall accurately reflect events during TIMs.

On-time delivery to performance standard at 98% level 100% Inspection

Documentation shall be submitted to the Government in Microsoft Office or Adobe PDF electronic format.

The report must describe the C&A strategy completely and clearly. Submit documentation to the Government in Microsoft Office or Adobe PDF electronic format.

On-time delivery to performance standard at 98% level 100% Inspection

Documentation shall be submitted to the Government in Microsoft Office or Adobe PDF electronic format.

Submit documentation to the Government in Microsoft Office or Adobe PDF electronic format.

On-time delivery to performance standard at 98% level 100% Inspection

Documentation should be sufficient for a third party to recreate the technology with minimal effort.

Documentation shall be submitted to the Government in Microsoft Office or Adobe PDF electronic format.

Documentation shall be submitted to the Government in Microsoft Office or Adobe PDF electronic format.

Report complete, accurate and reflective of efforts and previous reports for that year.

On-time delivery to performance standard at 98% level 100% Inspection

5.7 Past Performance Information

The Government provides and records Past Performance Information for acquisitions over $250,000 utilizing the Contractor Performance Assessment Reporting System (CPARS). The CPARS process allows contractors to view and comment on the Government’s evaluation of the contractor’s performance before it is finalized. The contractor is required to register in CPARS (https://www.cpars.gov/) and review and comment on past performance reports submitted through CPARS within the required timeline(s).

5.8 Annual Performance Assessment

The Contractor is strongly encouraged to provide an annual self-assessment report no later than 14 calendar days before the end of the PoP. The self-assessment report can be submitted in the contractor’s format and should discuss performance relative to Quality, Schedule and Management during the preceding 11 months. The Contractor should provide the annual self-assessment report to the COR, CS and CO via email. If the Contractor identifies accomplishments that exceeded any contractual standards (for example, delivering a higher quality product or service, or submitting ahead of schedule), the Contractor's self-assessment must include all associated facts and clearly describe how those accomplishments translated into a direct benefit to the Government from a project/program perspective.

6.0 CONTRACT ADMINISTRATION

6.1 Contracting Officer

The CO is the sole and exclusive Government official with actual authority to take actions that bind the Government under this contract.

The right to issue contract modifications, change terms and conditions, and terminate the contract is reserved solely for the CO.

The Contractor is responsible for ensuring that all Contractor personnel are notified of the responsibilities, authority and/or limitations of the CO, Contract Specialist (CS), Contracting Officer’s Representative (COR), and Technical Points of Contact (TPOC).

Changes, whether within or out of scope of this task order, performed by Contractor personnel without specific prior written authorization from the CO shall not be binding on the Government, nor shall the Government be obligated to pay any costs associated therewith. The Contractor assumes liability for any and all costs resulting directly or indirectly from the performance of unauthorized work by Contractor personnel.

6.2 Contract Specialist (CS)

The CS is a key liaison between the contracting officer, the client, and the contractor. The CS assists the contracting officer in ensuring contractual requirements are met. The CS may draft and initiate contract documents, research contractual issues, coordinate meetings, oversee compliance, review regulatory requirements, initiate CPARS, review and pay invoices, prepare task order and contract closeouts, and other government contracting functions.

6.3 Contracting Officer’s Representative (COR)

A COR is an individual authorized in writing by the CO to provide technical direction within the scope of this task order and perform other specific technical or administrative functions. The CO may issue a COR appointment letter stating the authority for the COR in accordance with DFARS 252.201-7000. The Contractor will receive a copy of the written COR designation and the COR’s responsibilities.

The COR is responsible for monitoring performance for the client agency and GSA. Management of this task order will primarily be performed by GSA through the COR. The COR may participate in project meetings, represent the CO in the technical phases of the work, and receive deliverables. The COR may provide technical assistance and clarification required for the performance of this task along with Technical Points of Contact (TPOC). The COR will not provide any supervision or instructional assistance to contractor personnel. The COR is not authorized to make any commitments or changes that will affect the scope (price, work quality, quantity, delivery, or any other term or condition of the task order). The COR is not authorized to change any terms or conditions of the task order. Changes in the contractual or task order requirements, price or terms and conditions can only be made by the CO via properly executed modifications to the task order.

The COR is responsible for coordinating all task-related matters within the client organization, for ensuring client-supplied items specified for task order performance are available when needed, and for apprising the GSA Contracting Officer of any problems that may affect delivery or costs of completed work.

6.4 Technical Point of Contact (TPOC)

The funding or requiring organization may assign TPOC for identified performance requirements. TPOCs may participate in project meetings and receive task order deliverables. The TPOC may provide technical assistance and clarification required for the performance of certain tasks. The TPOC will not provide any supervision or instructional assistance to contractor personnel. The TPOC is not authorized to change any terms or conditions of the task order. Changes in the contractual task order requirements, price or terms and conditions can only be made by the CO via properly executed modifications to the contract or the impacted task order(s).

6.5 Contractor Representative

The contractor shall establish processes and assign appropriate resources to effectively administer the contract. The contractor shall respond to Government requests for contractual actions within two business days. The contractor shall designate and maintain a single point of contact between the Government and contractor personnel assigned to support the contract.

6.6 System for Award Management (SAM) and the Excluded Parties List System (EPLS) The offeror must have an active registration status in the SAM with a Commercial and Government Entity (CAGE) Code and Unique Entity Identifier (UEI) throughout contract and task order performance. If the prime contractor and/or any known individual contractor personnel and/or any subcontractors have “Active Exclusions” in the Excluded Parties List System (EPLS), the government may consider discontinuing the contractual relationship with the prime and/or require the prime to discontinue services on this task order from the identified individuals and/or subcontractors. At a minimum, SAM registration and the EPLS will be reviewed prior to award and modifications of the task order.

6.7 Changes

Any change to this contract or a resulting task order shall be made in writing, and such change shall be executed by modification of the contract or the task order(s) by the CO. The contractor is responsible for ensuring that all contractor personnel are notified of this contract provision. All changes, whether within or out-of-scope of this contract, performed by contractor personnel without specific prior written authorization from the CO are not considered to be authorized by the Government and shall not be binding on the Government, nor shall the Government be obligated to pay any costs associated therewith. The contractor assumes liability for any and all costs resulting directly or indirectly from the performance of unauthorized work by contractor personnel.

6.8 Order of Precedence

This task order is subject to the terms and conditions in the Multiple Award Schedule (MAS) contract as well as those outlined within the Task Order. The Contractor's Quote is hereby incorporated by reference. In the event of an inconsistency between documents, the following order of precedence shall apply:

1. MAS Contract: XXXXX

2. This PWS

3. Task Order Attachments, drawings, etc.

4. Contractor's Task Order Quote NOTE: In the event of a discrepancy between the Contractor's Task Order Quote and any of the aforementioned documents, the MAS Contract and Task Order language shall take precedence. In particular, only in extremely rare circumstances can the language in a task order supersede the language in the basic Schedule contract. Any such instance shall be clearly indicated in the resulting task order award.

Betterments, if any, in the Contractor's Quote which exceed the minimum performance requirements identified in the PWS and associated documents shall be considered the new "minimum" performance requirements upon award and shall be met by the Contractor.

6.9 Proprietary Information

Unless disclosure is otherwise required by law, any proprietary information will be treated as confidential. Any proprietary information must be identified clearly and marked.

6.10 Kick-Off Meeting

Unless otherwise extended in writing by the CO, within ten workdays following the task order award, the Contractor shall schedule and attend a “kick-off” meeting to review the task order requirements. (If the contractor is required to travel, travel and all associated costs for this meeting will not be reimbursable.) The meeting location will be determined after award; the CO and CS may attend virtually. The Contractor shall provide meeting minutes to the CO no later than seven workdays after the meeting.

6.11 Transition Out

At the conclusion of this task order, the Contractor shall provide all reasonable information and services required to transition capabilities developed under the task order to a sustainment posture. The Contractor shall ensure an orderly transition and minimize any impact on operational readiness of the AFRL Spectrum Warfare Division RTIO. The contractor shall provide the new contractor access to the site and to all technical documentation and publications, while not interfering with any ongoing services.