DEWIT SOW - DRAFT 22 March 2021 (Source Sought).docx

FA5000-09-R-0033

STATEMENT OF WORK (SOW)

FOR

DEVELOPMENT OF ELECTRONIC WARFARE INTEGRATED TEST CAPABILITIES

(DEWIT)

772d Test Squadron

Edwards AFB, CA

16 March 2021

Development of Electronic Warfare Integrated Test Capabilities Table of Contents

1. DESCRIPTION OF SERVICES

1.1. General Scope. This is a non-personnel services Research and Development contract to provide Development of Electronic Warfare Integrated Test Capabilities (DEWIT) for the 772d Test Squadron (TS). The DEWIT effort, which primarily consists of the Improvement and Modernization (I&M) upgrade/development programs, is an evolutionary acquisition in which requirements, design, implementation, test, and delivery may be done incrementally. Each upgrade/development program or incremental release adds to the overall system capability. The DEWIT contract will be constructed such that any appropriately funded in-scope project can be executed under the DEWIT contract. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1.1. Except for those items or services specifically stated to be government-furnished, the Contractor shall furnish everything required to perform DEWIT services IAW this Statement of Work (SOW) and IAW all terms and conditions of the contact. This includes management, planning, oversight 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 Government Program Manager (GPM), and to immediately notify both the CO and the GPM of any problems that would prevent timely performance of this contract. The Contractor is required to implement, and maintain management control systems necessary to plan, organize, direct, and control all activities under this contract.

1.2. Background. The 772 TS operates and maintains the Benefield Anechoic Facility (BAF), located within the Avionics Test and Integration Complex (ATIC), 412th Electronic Warfare Group (EWG), 412th Test Wing (TW), Air Force Test Center (AFTC), Edwards AFB CA. The BAF is host to numerous electronic warfare (EW) Test and Evaluation (T&E) capabilities, including radio frequency (RF) threat signal simulators, Communication, Navigation and Identification (CNI) simulators, and avionics systems stimulators. Under the current concept of operations, a System Under Test (SUT) can be placed inside the BAF chamber, which provides a controlled and secure test environment, and then stimulated with multiple signals found in the electromagnetic environment that the test article could experience in flight.

1.2.1. The 772 TS requires continuous improvement in test methodologies and development of EW test capabilities in order to maintain its posture as the Center of Excellence (COE) for EW T&E. The 772 TS is dedicated to meeting test program challenges in risk management, cost savings, and improved capabilities by providing the expertise and facilities needed to field both hardware and software intensive EW test and support systems. These efforts are primarily funded through 3600 I&M funds from Air Force Test and Evaluation (AFTE) Test Investment Program and Planning (TIPP) and Department of Defense (DoD) Central Test and Evaluation Investment Program (CTEIP).

1.3. Purpose. The DEWIT effort will support the research and development (R&D) and procurement of capability enhancements to the BAF test environment by providing increased simulator fidelity and signal density throughout the electromagnetic spectrum, modern radar simulators upgrade/development programs including signal transmission, software generation, monitoring, and analysis, as well as improving efficiencies with regard to real-time test execution, environment monitoring techniques, and data capture and processing.

1.3.1. The DEWIT effort is an acquisition approach in which requirements, design implementation, test, and delivery may be done incrementally. Each incremental release adds to the overall system capability. The DEWIT contract will be constructed such that any appropriately funded in-scope project can be executed under the DEWIT contract. While these efforts may require the occasional research into available technologies, DEWIT will focus primarily on the development and procurement of these enhancements based on research completed by government intelligence agencies, the BAF Technical Experts, and engineering teams.

1.4. Inherently Governmental Function. The Contractor shall not perform inherently governmental functions as defined in FAR Subpart 7.5 in relationship to this SOW.

1.5. Mission Essential Service. In Accordance With DoDI 1100.22, (12 Apr 2010) Continuation of Essential DoD Contractor Services During Crises, DFARS 237.76, and the Air Force implementation thereof, unless otherwise directed by the CO or COR, it is determined that the services as identified in this SOW ARE NOT essential for performance during a crisis.

1.6. Period of Performance. This is a five (5) year contract.

1.7. Place of Performance. The Contractor shall perform the services in the SOW at either the Contractor occupied facility, a subcontractor facility, Edwards AFB, CA, or at other designated locations, as appropriate for the level of system maturity, in order to make the most effective use of personnel and other resources. Similarly, system testing will be accomplished at either the Contractor occupied facility, a subcontractor facility, Edwards AFB, CA, or at a designated location, as appropriate. All classified work will be accomplished at Edwards AFB, CA or other designated site.

1.8. Program Tasks. The overall DEWIT effort is to provide a means to develop, integrate, and enhance funded capabilities along with any other programs that may utilize DEWIT in the future. The DEWIT effort will provide upgrades, threat improvements, as well as support to other customers that identify unique requirements for mission simulation or installed test.

1.8.1. Engineering tasks. Close coordination with the Program Integrated Product Team (IPT) is required to develop and integrate other EW test capabilities for the existing BAF infrastructure. Many of the needed EW capabilities and technologies are software intensive. Contractor must demonstrate a successful software development process that meets recognized Institute of 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. On-time software development projects that meets all user requirements, including cost and schedule is required. Contractors must also be prepared to handle any type of hardware development task that could be needed in the area of EW technologies. Contractor must demonstrate practical hardware design knowledge to ensure functionality for new and/or existing EW technologies. Contractors will be required to provide source and executable files for all software developed. Software tools and other technologies, including software source code, firmware, etc. will be considered the property of the Government at all times unless specifically excluded in the associated task order.

1.8.2. DEWIT Development Tasks: to include design, systems engineering, integration and development as detailed below to provide the Government requested capabilities.

1.8.2.1. Prepare and present project schedules (at project start) and provide updates when requested. Changes to schedule will be coordinated and approved by the GPM. Potential impacts to schedule will be identified immediately to the GPM. Immediately is interpreted as when first recognized by the Contractor.

1.8.2.2. Perform systems engineering analysis of existing capabilities and customer requirements to achieve a sound technical understanding of the EW problem area.

1.8.2.3. Document technical requirements, designs and design decisions, plans, and procedures in written documentation, and submit for Government approval. The Government will identify required documentation, primarily taken from the DEWIT Contract Data Requirements List (CDRL) for each development activity. This includes engineering documents and drawings in support of system development and integration activities, and in support of user operations, maintenance, modification, and programming.

1.8.2.4. Prepare and present technical reviews (e.g., In-Progress Reviews (IPRs), Preliminary Design Review (PDR), and Critical Design Review (CDR)) on technical requirements, design, plans, and procedures. Hold technical interchange meetings (TIMs) to resolve specific program issues requiring additional attention and discussion.

1.8.2.5. Develop real-time software and resolve real-time programming constraints; perform hardware/software integration; develop real-time data processing and display systems; develop user interfaces; develop storage, cataloging, and reporting tools for use with large sets of data; develop report generation tools for stored data.

1.8.2.6. Execute a phased development and delivery process to the scale of the project and providing a useable deliverable at the conclusion of each phase.

1.8.2.7. 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 for the capabilities being delivered; detailed design documentation for the components and configuration items (CIs) being developed; any integration and test plans; test procedures; performance of qualification tests; test reports; and system operations and maintenance manuals.

1.8.2.8. Perform test plan development for newly developed and integrated systems and components, develop test procedures according to test plans, and compile test reports for tests that have been conducted. Provide all files necessary for software compilation and linking, and provide command procedures developed to support operation and test of software.

1.8.2.9. Perform planning and coordination of site installation, integration, activation and test such that ATIC personnel, facilities and resources are effectively utilized and ATIC-based activities are executed smoothly.

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

1.8.2.11. Contractors must be prepared to handle any type of hardware and software development task that could be needed in the area of EW technologies.

1.8.3. Other Engineering Support Tasks:

1.8.3.1. Provide engineering development and modification support to developers of existing systems in the BAF if required to accommodate DEWIT development and integration tasks.

1.8.3.2. Identify, develop, and document new system, subsystem, and configuration item requirements.

1.8.3.3. Perform system interface development and integration of sometimes dissimilar third party systems.

1.8.3.4. Identify and document interface requirements; design hardware and software interface approaches; and manage the implementation of interfaces through final test.

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

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

1.8.4. Tasks Common to All Activities. The primary engineering objective is to ensure the Contractor utilizes a well-organized, disciplined engineering approach for all development and integration activities. This approach should mirror recognized IEEE, ISO standards for engineering practices. The Contractor shall:

1.8.4.1. 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.8.4.2. Utilize a design approach that emphasizes modularity and open architecture to facilitate future system expandability.

1.8.4.3. Support the inspection (e.g., functional configuration audit, physical configuration audit) and acceptance of each block delivery.

1.8.4.4. Provide updates to existing and base-lined system documents and data where appropriate.

1.8.4.5. Perform security engineering for all development activities, coordinate security requirements with Government security specialists, and assist as required with the certification of systems for classified operations.

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

1.8.4.7. Provide data and technical support for validation efforts.

1.8.4.8. Provide configuration management of system baselines until responsibility is relinquished formally to the Government; afterward, maintain configuration management of the version(s) under development.

1.8.4.9. Provide database management for all efforts and databases, including maintenance of archive copies of the data, documentation of all changes to the database, documentation of the pedigree of the data incorporated in the database, and other tasks.

1.8.4.10. Provide resolution of user-generated System Trouble Reports (STRs) and Change Requests (CRs); build and maintain a log of all STRs/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 STRs/CRs. Provide descriptions, priorities and status of all STRs/CRs.

1.8.4.11. Develop recommended spare parts lists for systems developed. Provide spares and replacement parts according to Government identified requirements.

1.8.4.12. Provide system risk identification, assessment, tracking, mitigation, and management for all program activities.

1.8.4.13. Perform safety engineering as required to ensure the safe installation and operation of systems.

1.9. Management Tasks. The primary management objectives are to ensure that 1) the Contractor has in place robust plans, controls, and procedures to guarantee successful system development and integration, 2) the Government has clear insight into the development process, and 3) all development activities involving external organizations are fully coordinated. Specific management requirements include:

1.9.1. Provide a Proposal, Work Breakdown Structure (WBS), Contract Data Requirements List (CDRL) items and subcontracting plans in response to Government tasking. Upon start of any effort, after contract or task order (TO) award, an initial kick-off meeting will be held to insure a complete understanding of the work scope and objectives.

1.9.2. Create and maintain an overarching project management plan to coordinate the activities of systems engineering, systems test, quality assurance, risk management, and configuration and data management.

1.9.3. 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.9.4. Establish any subcontracts and associate Contractor agreements required to ensure satisfactory task completion.

1.9.5. Accomplish all work within the budget approved and authorized by the Government.

1.9.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 Statement of Work (SOW) for each TO.

1.9.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.9.8. Provide documentation called out in the DEWIT CDRL (Paragraph 1.10 below).

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

1.9.10. Provide for the receipt, generation, and storage of classified items in accordance with the contract DD Form 254.

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

1.9.12. 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.9.13. 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.9.14. Define and conduct reviews for major level development milestones to present and demonstrate progress.

1.9.15. Participate in project-related management and technical meetings with the Government and other Contractors. 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 772 TS.

1.10. Deliverables. The Contractor shall be required to provide all documentation and/or deliverables indicated in DEWIT CDRL list as well as in DEWIT tasks sections 1.8 and 1.9.

1.10.1. The Contractor will be required to develop and provide documentation to support requirements analysis, design, development, test, training and operational use of the DEWIT capabilities, including information about the operation of the DEWIT in conjunction with ATIC facilities and possible interoperability with other test capabilities. Each TO will have a CDRL requirement which will be derived from the overall DEWIT CDRL list. This could include up to all items listed in the DEWIT CDRL list.

1.10.2. Software tools and other technologies, including software source code, firmware, etc. will be considered the property of the Government at delivery unless specifically excluded in the associated task order. The contractor shall detail the additional costs associated with these deliverables.

1.10.3. In order to protect the rights of both the government and the contractor, the contractor shall explicitly call out and describe any and all intellectual property being used in any proposed task order effort to include drawings, designs, software, or hardware. The contractor shall define boundaries between contractor intellectual property and government purpose or unlimited rights, IAW DFARS 252.227-7013, 252.227-7014, 252.227-7017 and DFARS 252.227-7028, as applicable. If no rights are asserted, it will be assumed that the government will have unlimited rights to the work in the effort.

1.10.4. The contractor shall create and maintain a Master Document List (MDL) that includes all documents, whether the document is a deliverable or not, which are prepared during the course of the TO. This includes, but is not limited to correspondence, requests for information, material submittals, schedule submittals, status reports, schedule updates, etc. The MDL will include the dispatch/receipt date, any suspense for each document, and the final disposition of those suspenses. The MDL and its documents shall be maintained in libraries readily available for submittal to the Government.

1.10.5. The contractor shall prepare and submit the following technical reports as identified in each TO. All of the following technical reports may not be required at the TO level. Those that are required will be specified as such in each individual TO.

A. Technical Report B. Cost Estimates C. Status Reports D. Design Drawings E. Engineering Drawings and/or As-built Drawings F. Design Specifications G. Quality Assurance/Quality Control Surveillance Plan H. Training Manuals I. Test Inspection Report

1.10.6. Inspection. Deliverables will be inspected by the Government within three (3) workdays of receipt. Progress meetings may be held as required.

1.10.7. Data Collaboration. The contractor shall establish a Data Collaboration with real-time worldwide access available to persons authorized by the CO. The site may include, but not be limited to, the submittal register, submittals, a Request for Information (RFI) tracker, a change order tracker, a photo log, quality control reports, daily reports with complete record of activities and on-site personnel, and other relevant project correspondence. The site must be demonstrated to the Government and approved by the CO prior to any submittals being submitted. The site shall be tailored to the individual projects and close-out documentation shall include an electronic copy of the site documentation, provided in electronic copy of the site documentation, provided in electronic format – digital video disc (DVD) for historical information. Data Collaboration Site data shall be in accordance with 1.13.2 Protecting Unclassified DoD Data..

1.11. Minimum Performance Qualifications. The Contractor will be required to develop capabilities within the constraints of the fiscal year funding profile and within the constraints of the Task Order SOW. Integration and installation of the systems must be carefully coordinated with the government Task Order PM to accommodate on-going test programs completed by the 772nd Test Squadron at the BAF; contractor must remain flexible and adapt to changes to the BAF test schedule and resource requirements.

1.11.1. System designs should reuse existing software and hardware, as much as feasible. Existing software and hardware will be treated as Government Furnished Property (GFP) to the project in question and incur no additional cost to the contract. System designs will take into account, and interface with, the appropriate components of the BAF infrastructure, as well as existing stimulators, monitoring systems, display systems, and data processing facilities, to include the Advanced Radar Environment Simulator (ARES), the Infrared Sensor Stimulator (IRSS), the Combat Electromagnetic Environment Simulator (CEESIM), the Radar Air to Ground Environment (RAGE) and the Communications, Navigation and Identification (CNI) systems. All software and hardware will be designed to meet Information Assurance (IA) and other secure use and operations requirements.

1.11.2. The Contractor shall evaluate the cost-effective use of open, distributed architecture designs and standard interfaces to allow: (1) connection to existing and future customer system-specific equipment; (2) connection to existing and future simulation and electronics laboratory bench test facilities, (3) synchronization of test assets and (4) future incorporation of multi-spectral upgrades.

1.11.3. Thorough knowledge of EW testing, RF/Infrared (IR)/CNI/radar target simulators, simulation software, real-time processing, EW data products, and the simulation-based test process is required. Previous experience with both RF and IR simulation processes and engineering analysis as it pertains to the performance evaluation of systems under test (SUTs) is critical. Previous experience with threat simulator design, implementation, validation, and electronic warfare theoretical analysis, as it relates to the evaluation of EW systems, is required.

1.11.4. Personnel must have a final U.S. Government issued TOP SECRET security clearance and be DCID 6/4 eligible with a current Single-Scope Background Investigation (SSBI). Security requirements as outlined in the contract DD Form 254, Department of Defense Security Classification Specification, will be followed. Compliance with Operations Security requirements as contained in Air Force Instruction (AFI) 10-701 is required. Personnel must be able to be cleared into special access programs on an as needed basis.

1.12. Program Management

1.12.1. The Contractor shall provide program management functions to ensure the technical requirements in this SOW are met. The Contractor shall provide an effective, responsive, management methodology to organize, staff, lead, plan, coordinate, and control resources to meet SOW requirements. The organization structure must provide effective lines of communications and interfaces between Contractor’s management/supervisory and technical staffs, with Government personnel, other Government support Contractors, and Government customers. The Contractor shall submit accurate and timely cost, schedule and performance reports as required by the task orders. In those reports Contractors will provide the overall status, supported by the data in the report, that they are behind schedule, on-schedule, or ahead of schedule. If behind schedule, the Contractor will provide detailed reasons as why they are behind and mitigations that will allow them to be on-schedule by next report period.

1.12.2. Contractor Employees. The Government reserves the right to restrict the employment, under this contract, of any Contractor employee, or prospective Contractor employee who is identified as a potential threat to health, safety, security, general wellbeing, or the operational mission of the installation and its population. Contractor shall perform background checks, at Contractor's expense, to ensure that said employee has not been convicted of any felony.

1.13. Security Requirements.

1.13.1. Security Program. The Contractor will be required to provide all clearances needed for essential personnel involved in both traveling and performing on-site service support. The Contractor shall adhere to program security requirements in accordance with DD Form 254.

1.13.2. Protecting Unclassified Data. All DoD and Government data that is shared, stored or created on non-DoD information systems must be protected and any breach or loss of that data must be reported. The contractor shall comply with the security requirements defined in DoD Instruction 8582.01.

Contractor agrees to comply with all applicable laws that require the notification of individuals in the event of unauthorized release of personally identifiable information or other event requiring notification. In the event of a breach of any of contractor’s security obligations, or other event requiring notification under applicable law, contractor agrees to:

a. Notify CO by telephone and e-mail of such an event within 24 hours of discovery, and

b. Notify the US-CERT of such an event within 24 hours of discovery, and

c. Assume responsibility for informing all such individuals in accordance with applicable law, and

d. Indemnify, hold harmless and defend the United States, its trustees, officers, enlisted, and employees from and against any claims, damages, or other harm related to such event.

1.13.3. 412 EWG Access. The Contractor shall obtain a contractor badge for all personnel from the 412 EWG for entrance to restricted areas prior to commencing work under this contract. If in the event a “free zone” is not established prior to contract execution, Contractor personnel will require Government escorts to be provided by the 412 EWG.

1.13.4. Edwards AFB Access. All Contractor’s accessing Edwards AFB, CA are subject to a criminal history background check IAW AFMAN 31-113, Installation Perimeter Access Control, as stipulated in the Installation Commander’s memorandum to the 412th Security Forces Office dated 23 Apr 2015 (the AFMAN and memorandum are both limited access documents but more details on the requirements/process in terms of background checks can be provided by the Contracting Office upon request). Vehicle registration, proof of insurance, and a valid driver's license must be presented for vehicles. Installation Commanders may deny access and credentials based on information obtained during identity vetting that indicates the individual may present a threat to the good order, discipline, and morale of the installation.

1.13.5. Visitors/Contractors with driver’s licenses from ME, MN, MO, MT, and WA (exceptions are EDL-Enhanced driver’s licenses from MN & WA) will not be able to obtain Base access without another form of identification as an identity proofing document. The list of authorized IDs can be found in the REAL ID Act of 2005. Please visit the Department of Homeland Security’s (DHS) website to get the latest information, https://www.dhs.gov/current-status-states-territories.

1.13.6. The Contractor shall comply with all base security and traffic regulations.

1.13.6.1. The Contractor shall comply 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.

1.13.6.2. Contractors are prohibited from possessing weapons, firearms or ammunition, on themselves or within Contractor or privately-owned vehicle while on Edwards AFB.

1.13.7. The Contractor is responsible for safeguarding all government furnished property, equipment and materials provided for Contractor use. At the end of each work period, all Government facilities, equipment, and materials shall be secured.

1.13.8. Long-Term and Frequent Base Access. Contractor personnel requiring long-term and frequent access to Edwards AFB, CA may request a long-term Base access via an Air Force Materiel Command (AFMC) Form 496, Application for AFMC Identification Card, IAW Air Force Federal Acquisition Regulation Supplement (AFFARS) Clause 5352.242-9000, Contractor Access to Air Force Installations.

1.13.9. The Prime Contractor shall submit a written request on company letterhead to the CO with the following information (prior to submitting a request for Base access via an AFMC Form 496): 1) contract number, 2) location of work, 3) expiration date (must be on or before contract’s expiration date), and 4) names of employees/ subcontractor employees needing access to the base, to include each employee’s company name.

1.13.9.1. It is recommended that the Prime Contractor provide a copy of the request letter to each employee for verification purposes when the employee goes to the 412 EWG Security Office to get their AFMC Form 496 signed. Employees for which no request letter can be found or provided will result in the employee being asked to return on another date/time so verification can be made.

1.13.10. Base passes will be limited to the length of the contract not to exceed 3 years from the date the AFMC Form 496 is submitted to the Contracting Office for signature.

1.13.11. The AFMC Form 496 will be reviewed/approved by the CO, then taken by the Contractor employee to the Edwards AFB Pass & Registration Office in Building 3000 for the security portion and issuance of the Base pass.

1.13.12. The Contractor shall be responsible for prompt return of credentials and vehicle passes for: 1) any employee who no longer requires access to the work site; 2) upon request by a CO; and 3) upon completion or termination of the contract. The Prime Contractor shall ensure that all Base identification passes issued to employees and subcontractor employees are returned to the issuing office. Failure to comply with these requirements may result in withholding of payment.

1.13.13. Level I - Antiterrorism Awareness Training. The Contractor will be offered Level I - Antiterrorism Awareness Training by the Government. This training provides Contractor employees with the requisite knowledge necessary to remain vigilant for possible terrorist threats. Coordination for training should be done by the requiring unit Antiterrorism Representative (ATR) after contract award. AT Level I training can be taken at https://jkodirect.jten.mil/Atlas2/faces/page/login/Login.seam for non-CAC holders. Tracking for each Contractor or subcontractor employee is the responsibility of the GPM or unit ATR

1.13.14. The Contractor shall report suspicious activity (refer to Edwards AFB Contractor Antiterrorism Awareness pamphlet) to Security Forces at (661) 277-3340 in a timely manner.

1.14. Miscellaneous Requirements.

1.14.1. Meetings and Reviews. The Contractor shall participate in program reviews, TIMs, and Test Planning Working Groups (TPWGs).

1.14.2. Travel. The Contractor may be required to perform travel to locations that are associated with but not limited to Edwards AFB, CA, as required in accomplishment of tasks. The Contractor shall be responsible for obtaining all passenger transportation, lodging, and subsistence, both domestic and international, required in the performance of this contract consistent with FAR Part 31. Contractor may be required to travel during the performance of this contract to attend meetings, conferences, and training. The contractor may be required to travel to off-site training locations and to ship training aids to these locations. Contractor may 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 travel requires government approval/authorization and notification of the CO or, if delegated, to the COR. All invoices for travel reimbursement shall be accompanied by supporting receipts with invoices submitted to the Procurement Integrated Environment (PIEE) system.

1.14.3. Material/Equipment. The Contractor may be required to purchase various materials to include hardware and or software as required to accomplish tasks during the performance of this contract. Any material purchases, on the contract, will be coordinated with GPM. The Contractor shall return all applicable residual materials to the Government upon completion or termination of this contract.

1.14.4. Contract Manpower Reporting. The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the 412th Electronic Warfare Group on a secure data collection site, System for Award Management – SAM site at https://sam.gov), specifically where (1) period of performance indicates that performance occurred during the FY, (2) the product service code (PSC) reported is in one of the identified category management areas, (3) were in excess of $3M in obligations or deobligations reported during previous FY. If applicable, the contractor is required to completely fill in all required data fields in the SAM database. Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the SAM help desk. Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data. User Manuals: Data for Air Force service requirements must be inputted at the SAM link, please refer to the Service Contract Reporting (SCR) Guidebook for more information. If not readily available in the SAM database, the most recent guidebook and frequently asked questions on reporting can be provided by the procurement contracting officer (PCO) at the contractor’s request.

1.15. Small Business Subcontracting Program. The Contractor shall submit a subcontracting plan for small business (including ANCs and Indian tribes), veteran-owned small businesses, service-disabled veteran-owned small business, HUBZone small business, small disadvantaged business (including ANC’s and Indian tribes), and women-owned small business concerns, unless an exception applies. The plan shall contain goals for each of the categories, as well as 10 other elements identified (11 total) in FAR 19.704 and FAR Clause 52.219-9. This rating element assesses the contractor's performance in meeting the requirements of the plan and achievements against the negotiated goals.

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

2. CONTRACT PERFORMANCE

2.1. General. The Government shall monitor the Contractors’ performance to ensure services are received IAW the requirements set forth in this contract. Past Performance Information can be provided to other Government agencies, as requested.

2.2. Contractor Performance Assessment Report (CPARS). Depending on the estimated value of the contract, formal assessment and reporting of Contractor performance is documented using the CPARS system. The Contractor will be provided a copy of their assessment 365 days from contract award. 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”

2.3. Quarterly Progress Meetings. The CO, GPM, and other Government personnel as appropriate, and the Contractor shall meet quarterly to discuss the Contractor’s performance.

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

2.3.1.1. Opportunities to improve the contract,

2.3.1.2. Any modifications required of the contract,

2.3.1.3. Unsatisfactory performance,

2.3.1.4. Valid customer complaints against each performance objective observed, and

2.3.1.5. Steps taken by the Contractor to prevent occurrences in the future.

2.3.2. The Contractor shall provide a summation of unsatisfactory performance and customer complaints and provide insight into any identified trends.

2.3.3. The minutes of these meetings will be reduced to writing, signed by the GPM 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.4. Multifunction Team (MFT). The Contractor’s manager with the CO, Contract Administrator (CA) and other Government personnel shall meet on a regular basis. The MFT will establish how often meetings are needed based on contract complexity. The Contractor may request a meeting with the CO when the Contractor believes such a meeting is necessary. If the CO or CA deems necessary, written minutes of any such meetings shall be recorded by the CA in the contract file and signed by the GPM and the CO or CA. If the Contractor does not concur with any portion of the minutes, such nonoccurrence shall be provided in writing to the CO within 10 calendar days following receipt of the minutes.

2.5. Quality Control. In compliance with the applicable contract clauses FAR 52.246-4 thru FAR 52.246-5, entitled, “Inspection of Services (Fixed Price and Cost-Reimbursement),” develop and maintain an effective quality control program to ensure services are performed IAW this SOW, applicable laws and regulations and IAW best practices.

2.6. Quality Control Plan (QCP). The Contractor shall be required to submit a QCP within thirty (30) days after contract 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 by the CO within fifteen (15) days.

2.6.1. The Contractor’s QCP shall contain, at a minimum, the following descriptive items:

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

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

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

3. BASE SUPPORT SERVICES AND GOVERNMENT FURNISHED PROPERTY.

3.1. Base Support Services. The Government will provide the following services when tasks necessitate contractor employees to perform services on Edwards AFB:

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

3.1.2. 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 contract.

3.1.3. Computer Access. The Government will provide workspace consisting of computers and a printer for use on the local area network. The Government will provide and maintain the ECP and ensure restroom facilities are accessible. Work location in building 1030 and restroom located in building 1030.

3.1.4. Emergency Medical Services. Edwards AFB will provide emergency medical services for Contractor personnel in performance of services under this contract base IAW Air Force Instruction (AFI) 41-115 Chapter 1. The Contractor shall reimburse the Government for treatment provided at the current reimbursement rate for non-authorized user IAW AFH 41-114, paragraph 42. The Contractor shall provide to the 412 EWG Medical Group, the name of a physician and/or hospital to which injured personnel can be transferred for further treatment and care after receiving initial emergency treatment on base. All mishaps will be promptly reported to the base safety office through the GPM.

3.1.5. Security Police and Fire Protection. Phone number for Security Forces Squadron, 661-277-3340/3341; Fire Protection, 911.

3.1.6. Insect and Rodent Control. The Government will provide insect and rodent control services. Services will be furnished upon request to the facility manager.

3.1.7. Refuse Collection. The Government will provide refuse collection services. The Contractor shall take refuse to the nearest dumpster on a regular basis. The Contractor shall comply with all installation recycling programs, refuse volume reduction programs, and hazardous waste collection policies IAW base policies.

3.2. Government Furnished Property. Government Furnished Property (GFP), to include equipment and materials and Contractor Acquired Property (CAP), will be specified in each TO, to include delivery, management, accountability and disposition. FAR 52.245-1 defines Government Property and the procedures for accounting for and disposition of property. Defense Contract Management Agency (DCMA) instructions for reporting of and including in the Plant Clearance Automated Reutilization Screen System (PCARSS) will be followed for any Government Property remaining at the end of the project.

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

4. GENERAL INFORMATION.

4.1. Hours of Operation. Normal hours of operation for government employees is 0730 to 1630 PST Monday thru Friday except Federal holidays or when the government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. For other than firm fixed price contracts, the Contractor will not be reimbursed when the Government facility is closed for the above reasons. On occasion, an employee will be required to work on weekends and Federal holidays. The Government will notify the Contractor within 24 hours of such occurrence. Overtime is not be worked unless previously authorized by the Contracting Officer on a per Task Order basis.

4.2. Recognized Holidays. The Contractor is not required to perform services on public holidays as established by Federal law 5 U.S.C. 6103. If the holiday falls on a Saturday, it will be observed on the preceding Friday. If the holiday falls on Sunday, it will be observed on the following Monday.

4.3. Inclement Weather. If the base closes due to inclement weather while performing work on base, the Contractor will be released, by the installation commander, with the general population of the base at no decrement to contract price. The Contractor will follow the local procedures for reporting in inclement weather as advertised on local television and radio stations.

4.4. Contract Personnel.

4.4.1. Training. The Contractor shall ensure employees receive Government directed and provided training to include, but not limited to, information assurance, security, anti-terrorism, fire prevention, voluntary protection program and safety. All employees must be current on all required training for performance of services to include all security training as noted in AFI 16-1404. The contractor shall give all training required to meet requirements of the SOW unless otherwise specified within the SOW 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.4.2. Contract Manager (CM). The contractor shall provide a contract manager and alternate(s) who are knowledgeable of [Insert the requirement]. The contractor shall submit the name, address, telephone number and a resume of the CM to the CO within 2 days of contract start date. The list shall be kept current throughout the life of the contract. The CM or alternate(s) shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract.