EWIC_DRAFT_PWS_23_MAY_18.pdf

FA9304-19-R-0002

PERFORMANCE WORK STATEMENT

FOR

ELECTRONIC WARFARE IMPROVEMENT CAPABILITIES

(EWIC)

772d Test Squadron

Edwards AFB, CA

23 May 2018

Electronic Warfare Improvement Capabilities Table of Contents

1.0 SECTION I: DESCRIPTION OF SERVICES

1.1 General

1.2 Background

1.3 Inherently Governmental Function

1.4 Period of Performance

1.5 Place of Performance

1.6 Purpose

1.7 Scope of Work

1.8 Program Tasks

1.9 Management Tasks

1.10 Historical Data

1.11 Deliverables

1.12 Minimum Qualifications

1.13 Contract Personnel

1.14 Contractor Manpower Reporting Application (eCRMA)

1.15 Security Requirements

1.16 Meetings, Review, and Travel

1.17 General Information

1.18 Miscellaneous Tasks

1.19 Small Business Subcontracting Program

1.20 Contractor Phase-In and Phase-Out Transition

2.0 SECTION II: SERVICE SUMMARY

2.1 General

2.2 Performance Evaluation

2.3 Government Quality Assurance Program

2.4 Performance Assessment

2.5 Quarterly Progress Meeting

2.6 Contracting Officer Representative

2.7 Multifunction Team

2.8 Quality Control

2.9 Quality Control Plan

2.10 Contractor’s Performance

3.0 SECTION III: GOVERNMENT FURNISHED PROPERTY and SERVICES

3.1 Government Furnished Services

3.2 Government Furnished Facilities

3.3 Government Furnished Equipment

4.0 SECTION IV: GENERAL INFORMATION

4.1 Hours of Operation

4.2 Contractor Personnel

4.3 Safety

4.4 Miscellaneous Paragraphs

4.5 Fire Prevention

4.6 Inclement Weather

5.0 SECTION V: SECURITY REQUIREMNTS

5.1 Controlled Area Badges

5.2 Base Access

SECTION VI APPENDICES & EXHIBITS

APPENDIX 1 Definitions, Abbreviations, and Acronyms

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General Scope. This is a non-personnel services contract to provide Electronic Warfare Improvement Capabilities (EWIC) for the 772d Test Squadron (TS). The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

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

1.2 Background. The 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 EWIC effort will support the research and development (R&D) and procurement of capability enhancements to this environment by providing increased simulator fidelity and signal density throughout the electromagnetic spectrum, as well as improving efficiencies with regard to real-time test execution, environment monitoring techniques, and data capture and processing.

1.2.2 The EWIC effort primarily consisting of modern radar upgrade/development programs including signal transmission, software generation, monitoring, and analysis, is an evolutionary acquisition approach in which requirements, design implementation, test, and delivery are done incrementally. Each incremental release adds to the overall system capability. The EWIC contract will be constructed such that any appropriately funded in-scope project can be executed under the EWIC contract.

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

1.4 Period of Performance. This is a five (5) year contract with a six month option.

1.5 Place of Performance. The Contractor shall perform the services in the PWS 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.

1.6 Purpose. This PWS identifies objectives for the EWIC contract effort. 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.

1.7 Scope of Work. The Contractor shall provide all personnel, transportation, supervision, and services necessary to develop the required EW capabilities for the 772 TS as defined in this PWS. The EWIC 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 are done incrementally.

Each incremental release adds to the overall system capability. The EWIC contract will be constructed such that any appropriately funded in-scope project can be executed under the EWIC contract.

1.8 Program Tasks. The overall EWIC effort is to provide a means to develop, integrate, and enhance funded capabilities along with any other programs that may utilize EWIC in the future. The EWIC effort will provide upgrades, threat improvements, and BAF mission level laboratory support, 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. 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. The vendor should price these into the contract and detail the additional costs associated with these deliverables.

1.8.2 EWIC Development Tasks:

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

b. Perform design, systems engineering, integration and development to provide the Government requested capabilities.

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

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

e. 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 EWIC Contract Data Requirements List (CDRL) for each development activity.

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

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

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

i. 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 On-Site Technical Support Tasks. Provide on-site technical support for the integration and operation of EW capabilities at Edwards AFB CA. The support tasks includes installation, integration, operational use, maintenance, modifications, test and evaluation support, analysis, training site supervision, site management and security. The Government will furnish standard office furniture and equipment (including computer hardware and software, facsimile machine, reproduction machine, and office supplies), telephone service (on-base, WATS and DSN), local area network access (maintenance will be provided by the Air Force), test facility equipment and supplies to support these activities. A predicted number of on-site visits should be programmed into the contract, but sufficient reserve should be provided for some unanticipated on-site activities.

1.8.4 Other Engineering Support Tasks:

a. Develop and install new releases of software at the 772 TS and conduct site acceptance testing.

b. Provide system administrative support for software at the 772 TS, to include system administrative support for workstations running both Microsoft Windows and Red Hat Linux.

c. Provide engineering development and modification support to all systems in the BAF associated with EWIC Programs.

d. Provide support in the development and modifications of scenarios and laydowns, and player library databases utilizing appropriate intelligence sources and support Government personnel in the operations and maintenance of the program model.

e. Provide general purpose software tools (scripts and patches) for use with models as part of the analysis and exercise support; the development of scripts for the automatic retrieval of data from Department of Defense (DoD) databases and reformatting any needed data; the development of scripts to extract post-mission data from the model and display it with a visualization program; the development of software to interface during runtime and provide interim patches for software deficiencies.

f. Provide support to Government personnel in the setup, testing and operation of systems; test/exercise support to include system architecture development, scenario development, testing, player development, and post-test/exercise analysis.

g. Provide network support for test, exercise, and development networks; administrative and operational support for simulations interfaced at various off-site model locations.

h. The 772 TS supports test and analysis activities by developing test requirements, preparing test plans and scenarios, conducting tests, performing data reduction and analysis, preparing test reports, identifying and recommending fixes and improvements.

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

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

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

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

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

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

o. Develop the integration solutions into new BAF systems utilizing the simulator interface processor (SIP) approach to interfacing the simulators/stimulators. The systems are required to operate synchronously and be coherent for certain type of test configurations.

p. Perform directives as tasked.

q. Provide development and technical support for various customers that include F-22, F-35, Red Flag, Miniature Air Launch Decoy (MALD-J) and others for software integration, upgrades, troubleshooting, interfaces, and test support for difficult and complex situations as a minimum, for the duration of the applicable task order.

1.8.5 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:

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

Present the results of these analyses to the Government.

b. Perform interface identification, design, control and management for all development activities.

c. Utilize a design approach that emphasizes modularity and open architecture to facilitate future system expandability.

d. 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. Perform system testing for each deliverable.

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

f. Develop engineering documents and drawings in support of system development and integration activities, and in support of user operations, maintenance, modification, and programming.

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

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

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

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

k. Provide data and technical support for validation efforts.

l. Perform site installation and checkout of systems at the ATIC. 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.

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

n. Provide Database Management (DBM) 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.

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

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

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

r. 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:

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

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

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

d. Establish any subcontracts and associate Contractor agreements required to ensure satisfactory task completion.

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

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

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

h. Provide documentation called out in the EWIC CDRL (Paragraph 1.11 below).

i. Provide Data Management of all contract documentation. Provide for control and tracking of document revisions and versions.

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

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

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

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

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

o. 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 Historical Data. Tasks performed in sections 1.8 and 1.9 have been performed in the past by both the VIEWS and VIEWS II contracting vehicles and are proven to be well established.

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

1.11.1 The Contractor will be required to develop and provide documentation to support requirements analysis, design, development, test, training and operational use of the EWIC capabilities, including information about the operation of the EWIC 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 EWIC CDRL list. This could include up to all items listed in the EWIC CDRL list.

1.12 Minimum Qualifications. The Contractor will be required to develop capabilities within the constraints of the fiscal year funding profile and within the constraints of the PWS. Integration and installation of the systems must be carefully coordinated with on-going test programs at the Edwards facility; they must also be flexible to adapt to changes to the facility test schedule and resource requirements.

1.12.1 System designs should reuse existing software and hardware, as much as feasible, to satisfy desired performance requirements. Any reuse 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), 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.12.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.12.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.12.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.13 Contractor Personnel.

1.13.1 Contract Manager (CM). The Contractor shall provide a contract manager and alternate(s) who are knowledgeable of the requirements of this PWS. The Contractor shall submit the name, address, telephone number and a resume of the Project Manager to the CO within two (2) days of contract start date. The list shall be kept current throughout the life of the contract. The contract manager or alternate(s) shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The contract manager or alternate(s) shall be available within two hours of notification to meet on the installation with Government personnel designated by the CO to discuss problem areas. The contract manager and alternate(s) shall be able to read, write, and speak English. The contract manager shall be able to effectively communicate with Contractor employees.

Qualifications for the Contract Manager are listed below.

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

1.13.3 Subcontract Management. The Contractor shall manage all subcontracted efforts in a manner consistent with the requirements of the PWS.

1.13.4 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 sexual crime or any crime against children.

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

1.13.6 Employee Training. The Contractor shall give all training required to meet requirements of the PWS unless otherwise specified within the PWS or as otherwise approved by the CO or the COR. 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.

1.14 Contractor Manpower Reporting Application (eCMRA). The Contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via the secure data collection site (i.e. eCMRA). The Contractor shall register in eCMRA within 30 days of contract award. The Contractor is required to completely fill in all required data fields using the following web address http://www.ecmra.mil. Reporting inputs will be for the labor executed during the period of performance during 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 above eCMRA help desk. 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. Data for Air Force service requirements must be input at the Air Force eCMRA link. However, user manuals for Government personnel and Contractors are available at the eCMRA link at http://www.ecmra.mil.

1.15 Security Requirements.

1.15.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.15.2 COMPUSEC. When applicable the Contractor shall comply with established Computer Security (COMPUSEC) policies and procedures to protect classified, sensitive, and unclassified information processed in information systems which are furnished to, and operated by, the Contractor.

1.15.3 OPSEC. When applicable the Contractor shall comply with established Operations Security (OPSEC) policies and procedures to protect classified, sensitive, and unclassified information and/or equipment which is furnished to and operated by the Contractor.

1.15.4 Security. The Contractor shall abide by the terms set forth in AFFAR clause 5352.242-9000 and requirements contained in DD Form 254. Additionally, the Contractor shall comply with all security and force protection requirements at Edwards AFB CA. All personnel requiring access to the Edwards Unclassified Local Area Network must have a minimum of a favorable National Agency Check (NAC) IAW AFI 31-501. Applicable personnel shall complete the Infocon and Information System User Computer Based Training (CBT). The reference for the CBT requirement is AFI 33-204, and AFI 33-115 VII.

1.16 Meetings, Review, and Travel. The Contractor shall participate in program reviews, TIMs, and Test Planning Working Groups (TPWGs). Travel may be required in order to perform required tasks.

1.17 General Information. Performance of Services During Crisis Declared by the National Command Authority.

IAW DFARs 237.76 (Continuation of Essential DoD Contractor Services During Crisis) and aforementioned Air Force implementation, unless otherwise directed by an authorized Government representative, it is determined that services as identified in this PWS are NOT essential for performance during a crisis.

1.18 Miscellaneous Tasks.

1.18.1 Travel. The Contractor may be required to perform travel to locations that are associated with but are 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 the Government’s Joint Travel Regulations (JTR).

1.18.2 Environmental Controls. The Contractor shall perform the requirements of this PWS in an environmentally acceptable manner in accordance with all applicable Occupational Safety and Health Administration (OSHA), AF, DoD, federal, state, and local environmental protection and health laws and regulations.

1.18.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 Government PM. The Contractor shall return all applicable residual materials to the Government upon completion or termination of this contract.

1.18.4 Deliverables. 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 vendor should price these into the contract and detail the additional costs associated with these deliverables.

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

1.18.6 Inspection. Deliverables will be inspected by the Government within two (2) workdays of receipt.

Progress meetings may be held as required.

1.19 Small Business Subcontracting Program. The Contractor shall submit a subcontracting plan for small business, small disadvantaged businesses, Historically Under-utilized Business Zones (HUBZones), women-owned small businesses, service disabled veteran owned small businesses, veteran-owned small businesses, historically black colleges and universities and minority institutions, and Alaska Native corporations and Indian Tribes. 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.19.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.

1.20 Contractor Phase-In and Phase Out Transition.

1.20.1 Contractor Phase-In. To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during the phase in/ phase out periods. The incoming Contractor’s personnel shall receive fourteen (14) calendar days of On-the-Job Training (OJT) by the incumbent Contractor. Incoming Contractor personnel to be trained by the incumbent Contractor shall possess, prior to training, all special skills, licenses, and certifications needed to perform the specific tasks in this PWS.

The training will cover unique features of all systems and equipment. The OJT may be augmented by any applicable instruction from manuals and/or other mediums. Contractor phase-in will not be necessary for an incumbent Contractor.

1.20.2 Contractor Phase-Out. The outgoing Contractor shall allow the incoming Contractor to interview for employment the outgoing Contractor’s personnel, provided that work interruption time is reasonable.

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

1.20.4 During the fourteen (14) calendar day training period, the outgoing Contractor shall perform all requirements in this PWS.

SECTION II

2.0 SERVICE SUMMARY (SS)

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

2.2 Performance Evaluation. Performance of a service shall be evaluated to determine whether or not it meets the performance requirements of this contract. Re-performance of unacceptable services at no additional cost is the preferred course of action when appropriate. In the case of issued Corrective Action Reports (CARs), the Contracting Officer shall take appropriate measures according to inspection of services clause in the contract, i.e., FAR 52.246-4, 52.246-5, or 52.212-4(a).

SS

Performance Objective (The Service required— usually a shall statement)

PWS

Paragraph

PERFORMANCE THRESHOLD (THIS IS THE MAXIMUM

ERROR RATE. IT COULD POSSIBLY BE “ZERO

DEVIATION FROM STANDARD”)

SS-1 Contract Tasks The Contractor shall perform all development, technical and engineering support, management, and common tasks as identified in this PWS. Performance threshold is based on the Contractor finishing the task on schedule for a satisfactory rating.

1.8.2a-i 1.8.3 1.8.4a-q 1.8.5a-r 1.9a-o

The Contractor shall complete tasks by assigned date associated with future task orders (TO).

Exceptional = Greater than 2 work days ahead of scheduled need date.

Very Good = 1 – 2 work days ahead of scheduled need date.

Satisfactory = On scheduled need date.

Marginal = 1 – 3 work days behind scheduled need date.

Unsatisfactory = Greater than 3 work days behind scheduled need date.

SS-2 Contract Deliverables The Contractor shall be required to provide all documentation and deliverables indicated in CDRL list. Performance threshold is based upon the delivery of documentation by contract date for a satisfactory rating.

1.11

The Contractor shall complete and deliver documentation by contracted date.

Exceptional = Greater than 2 work days ahead of scheduled need date.

Very Good = 1 – 2 work days ahead of scheduled need date.

Satisfactory = On scheduled need date.

Marginal = 1 – 3 work days behind scheduled need date.

Unsatisfactory = Greater than 3 work days behind scheduled need date.

SS-3 Program Management The Contractor shall ensure program management, subcontract management, and employee requirements within this PWS are identified and met.

Performance threshold is based upon schedule and costs.

1.13

The Contractor shall ensure Program Management process is effective by ensuring tasks are met in a timely and efficient manner.

Very Good = Ahead of schedule, within budget Satisfactory = On schedule, within budget.

Marginal = Behind schedule, within budget OR on schedule, over budget.

Unsatisfactory = Behind schedule, over budget.

SS-4 Security Requirements The Contractor ensures all employees adhere to all of security requirements.

Performance threshold is based all Contractor employees adhere to all of security requirements with 0 security incidents for a satisfactory.

1.14.1- 1.14.4

Contractor shall ensure all employees adhere to all of security requirements with 0 security incidents.

Satisfactory = 0 security incidents Marginal = 1 or more security incidents Unsatisfactory = 1 or more security infractions

SS-5 Subcontracting Plan The Contractor shall submit a subcontracting plan for small businesses and other groups identified in this PWS. The plan shall contain goals and other elements included in FAR 19.704 and FAR Clause 52.219-9. Both an Individual Subcontracting Report (ISR) and Summary Subcontract Reports (SSR), shall be submitted semi-annually during contract performance for the periods ending March 31 and September 30.

1.18

Maintain at a minimum 51% -70% of small business goals. Measured at the end every option period.

Reports are due 30 days after the close of each reporting period, unless otherwise directed by the Contracting Officer.

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.

1.8

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.

1.8

The Contractor shall report ALL Contractor labor hours (including subcontractor labor

1.14 The Contractor shall completely fill in all required data fields using the following web address

2.3 Government Quality Assurance.

2.3.1 The Government shall inspect and evaluate the Contractors’ performance to ensure services are received in accordance with requirements set forth in this contract. The COR will use the Contractor’s work schedule, or modified version thereof, to record validation results. Results of the validation then becomes the official Air Force record of the Contractor’s performance. Government surveillance of tasks not listed in the PWS or by methods other than those listed in the PWS (such as provided for by the Inspection of Services clause) may occur during the performance period of this contract. Such surveillance will be done according to standard inspection procedures or other contract provisions. Any action taken by the CO as a result of surveillance will be according to the terms of this contract.

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

2.3.3 When an observation indicates defective performance, the COR will require the contract manager or representative at the site to initial the observation. The initialing of the observation does not necessarily constitute concurrence with the observation, only acknowledgment that he or she has been made aware of the defective performance. When a performance threshold has not been met or Contractor performance has not been accomplished, the COR will initiate and provide the CO a Corrective Action Report (CAR) for issuance to the Contactor. The Contractor shall respond to the CAR IAW instructions provided and return it to the CO within 10 calendar days of receipt.

2.4 Performance Assessment.

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

2.4.2 Customer Complaints. The COR will receive and investigate all complaints. The COR shall be responsible for validating customer complaints. The CO shall make final determination of the validity of customer complaint(s) in cases of disagreement with the COR and the Contractor. Validated customer complaints shall be corrected within 2 hours of notification. CO will validate corrective action.

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

2.4.4 100 Percent Inspection. This method requires the COR to do 100 percent inspection on all task performed.

Appropriate for tasks that occur infrequently. Usually only deals with Safety and/or Security, unless mandated by an AFI or industry standard.

2.5 Quarterly Progress Meetings. The CO, PM, Functional Services Manager (FMS), COR, other Government personnel as appropriate, and the Contractor shall meet quarterly to discuss the Contractor’s performance.

hours) required for performance of services provided under this contract via http://www.ecmra.mil.

http://www.ecmra.mil. All data shall be reported no later than October 31 of each calendar year.

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

a. Opportunities to improve the contract,

b. Any modifications required of the contract,

c. Unsatisfactory inspections,

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

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

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

2.5.2 The minutes of these meetings will be reduced to writing, signed by the CO and any other signatures as deemed appropriate, distributed to the functional area and the Contractor. Should the Contractor not concur with the minutes, the Contractor will provide a written notification within 5 working days to the CO identifying areas of non-concurrence for resolution.

2.6 COR. CORs are representatives of the CO and will participate in the administration of this contract. After award of the contract, the Contractor will be provided a letter identifying the COR and setting forth their duties and authorities. The COR is not authorized to change any of the terms and conditions of the contract/task order.

2.7 Multifunction Team (MFT). The Contractor’s manager with the CO, Contract Administrator (CA), COR, 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 PM and the CO or CA. If the Contractor does not concur with any portion of the minutes, such nonoccurrence shall be provided in writing to the CO within 10 calendar days following receipt of the minutes.

2.8 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),” or FAR 52.212-4(a) Commercial Terms and Conditions Inspection/Acceptance, develop and maintain an effective quality control program to ensure services are performed IAW this PWS, applicable laws and regulations and IAW best commercial practices.

2.9 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. The Contractor’s QCP shall contain, at a minimum, the following descriptive items:

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

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

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

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

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

2.10.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 60 days to review and submit comments for the evaluation activity’s consideration before the assessment is made final. Past Performance assessment reports will be protected by all parties and treated by Government personnel as “For Official Use Only/Source Selection Information in accordance with FAR 2.101 and 3.104”.

SECTION III

3.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3.1 Government Furnished Services. The Government will provide the following services:

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