RFP Attachment 01 - DRAFT SB 2024 PWS 3Feb2023.pdf

DRAFT

AIR FORCE SENSOR BEAM 24

SUPPORT

PERFORMANCE-BASED WORK STATEMENT

57th Intelligence Squadron (57 IS)

1 DESCRIPTION OF SERVICES

1.1 Introduction

1.2 Background

1.3 Scope

1.4 Ordering Period

2 SPECIFIC TASK……..………………………………………………………………..…7

2.1 Analysis Support

2.2 Production Support

2.3 Research Support

2.4 Technical Library Support

2.5 Computer System Administration and Software Development Support

2.6 Technical Data and Delivery Support

2.7 Training Support

2.8 IMD Production

3 SERVICES SUMMARY (SS)

4 GOVERNMENT FURNISHED PROPERTY (GFP) AND SERVICES

4.1 Accountability

4.2 Applicable Documents

4.3 Facilities

4.4 Secure Communications

4.5 Technical Site Library

4.6 Logging Tools

5 CONTRACTOR FURNISHED PROPERTY AND SERVICES

6 SPECIAL REQUIREMENTS/INSTRUCTIONS

7 GENERAL INFORMATION

7.1 Contractor Identification in the Government Workplace

7.2 Security

7.3 Information Systems Security

7.4 Operations Security

7.5 Physical Security

7.6 Key Control

7.7 Combinations and Codes

7.8 Privacy Act

7.9 Location(s) of Work

7.10 Hours of Operation

7.11 Conservation of Utilities

7.12 Records

7.13 Contractor Manpower Data Reporting

7.14 Environmental Controls

7.15 Safety Requirements

7.17 Special Training, Certifications, and Qualifications

7.19 Kick-off Meeting and Periodic Progress Meetings

7.20 Contractor Travel

8 DELIVERABLES

Appendix A – Acronyms and Abbreviations List………………………………………………30

Appendix B– Applicable Publications and Instructions ……………………………………….33

Appendix C– Maps and/or Site Plans …………………………………………….………….…37

Attachment 1. Primary Data Sources………………………………………………………….41

Attachment 2. Secondary Data Sources……………………………………………………

1 DESCRIPTION OF SERVICES

1.1 Introduction

1.1.1 This is a non-personal services contract. The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. The contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services. The contractor shall notify the

Contracting Officer (CO) immediately if they perceive any actions constitute personal services.

These services shall not be used to perform any Inherently Governmental Functions.

1.1.2 The contractor shall ensure cooperation with the Government Program Manager (GPM), Government Contracting Officer (CO) and Contracting Officer Representative’s (COR’s) or

Government section/shift lead to accomplish Government requirements, goals, and mission objectives as efficiently and effectively as possible; including sharing or coordinating information resulting from the work required within this PWS and working as a team to perform tasks in concert. The contractor shall ensure minimum duplication of effort in the execution of all work specified within this PWS and build upon work previously accomplished by the Government, the contractor, or other contractors to the fullest extent practical.

1.2 Background

1.2.1 This Performance Work Statement (PWS) provides general scope of the Government’s requirement for support. The 57th Intelligence Squadron (57 IS), Air Combat Command (ACC), is responsible for technically documenting United States (US) and friendly foreign electromagnetic systems parametric data, weapon system characteristics, performance and electronic fit, analysis and documentation of airborne target signatures. These responsibilities address the electronic warfare (EW) operational requirements mandated by Air Force Instruction (AFI) 10-703; the

Chairman of the Joint Chiefs of Staff (CJCSM) 3320.04 & CJCSI 3320.01D for Joint

Electromagnetic System Operations (JEMSO) including the US Electromagnetic Systems

Database (USELMS) and the Blue Airborne Target Signatures (BATS) database; and the formal tasking issued by the Defense Intelligence Agency (DIA) for the Intelligence Mission Data (IMD) production for unit’s entire mission.

1.2.2 The unit has been at the forefront of integrating the functional areas of Intelligence Mission

Data (IMD) for the Combat Air Force (CAF) and the Department of Defense (DoD). The

Intelligence Mission Data covers five pillars; however, the 57 IS’s mission is primarily concerned with these three pillars: Signatures, electromagnetic warfare integrated reprogramming (EWIR), and characteristics and performance (C&P) data. Over the last decade, the 57 IS has merged analytical processes, tasking, and products to provide EW reprogramming, acquisition, test and evaluation, mission planning, sensor fusion, tactics development, operational support customers and the 5th generation fighter community with multiple integrated sets of products. These products comprise the concept of IMD, support modern sensor fusion and integrated defensive aids suites requirements.

1.2.3 The 57 IS requires a contractor with an established IMD production infrastructure. This infrastructure shall include, but not limited to, the ability to generate USELMS files compatible with DoD Electromagnetic Warfare Integrated Reprogramming Data Base (EWIRDB) standards recognized by both EWIR producers and users to include Foreign Military Sales (FMS) and Five

Eye (FVEY) Partners. All analysts shall have expertise with EWIR tools, as specified in para 2.2.6 below, used to generate modernized, complex, simulation-ready Tier 1 Standard EWIR Reference

Format (SERF)-based products; and the Mission Planning Software (MPS) data production toolset used in creating Combat Support Database (CSDB) files. Further IMD files shall include, but are not limited to: Characteristics and Performance (C&P) data; Signatures data such as Radar Cross

Sections (RCS), electro-optical/infrared (EO/IR) studies, and antenna pattern information using electromagnetic codes (such as, but not limited to, XFdtd, XGTD, Wavefarer, Echo, Matlab/Simulink, Apatch, and Xpatch); Support the Order of Battle (OB) mission area through

Defense Intelligence Agency Equipment (DIEQP) Codes; and Platform electronic-fit data.

1.3 Scope

1.3.1 The contractor shall provide qualified personnel and material necessary to perform the

Government requirement. The contractor shall perform all tasks required to research, produce computer aided design (CAD) models, predictive analysis, engineering analysis, customer service, data delivery, build scientific technical documents, perform studies and reviews for the electromagnetic systems, software evaluations, support both physical signature measurements and modeling, scanning documentation, archiving extracted data, extracting data to delivery to customers, monitor and manage requests for information (RFI) and requests for production (RFP), events, and signatures specified by the 57 IS. These tasks shall include but are not limited to:

analytical and feasibility studies; certification evaluation of ranges and facilities to gather signatures data; quality reviews; system management studies; computer system administration;

relational database management system administration; database management; software development; development and update of analysis tools and methods; and all tasks required to perform complete studies of systems, events, and signatures.

1.3.2 Systems shall include but are not limited to: passive and active radar systems; other passive detection systems; Missile Warning Receivers; Electronic Counter Measures (ECM) systems;

Electro-optical and Infrared (EO/IR) systems; Communications Systems; Surface-to-Air Missiles

(SAMs); Anti-aircraft Artillery (AAA); and Air Defense Artillery (ADA).

1.3.3 Tasks, events, and signature descriptions shall include, but are not limited to: identification, targeting and signature events; RCS; antenna patterns; EO/IR signatures of airborne targets (i.e., aircraft, missiles, and physical countermeasures); acquisition of information; analysis of specific and non-specific data items; and technical documentation of engineering data into established formats.

1.3.4 Examples of established data formats and standards shall include those associated with:

United States Electromagnetic Systems Database (USELMSDB), Electromagnetic Warfare

Integrated Reprogramming Database (EWIRDB), Combat Support Database (CSDB), Blue

Airborne Target Signatures Database (BATS), and the NATO Emitter Database (NEDB).

1.3.5 Most services shall be performed in the contractor’s facilities; however, some tasks shall be performed in 57 IS workspaces. Computer systems support shall include, but is not limited to, automated information systems based on Microsoft (MS) Windows and various UNIX and UNIX-like operating systems. Computer systems support shall include all actions to complete all tasks associated with enabling and sustaining the information technology infrastructure, including hardware and software required to accomplish the mission areas enumerated in this PWS. The contractor shall support risk management framework certification and accreditation for software, hardware, and network systems with the 57 IS.

1.3.6 The contractor shall minimize interruptions or delays to work in progress during the contractor transition periods. It is essential the contractor plan for the transfer of work control, delineating the method for processing and assigning tasks during the phase-in/phase-out periods.

The contractor shall ensure there are no negative mission impacts.

1.4 Ordering Period

The Ordering Period for this contract shall be for one (1) five-year base period with one (1) five-year option period. This is an Indefinite Delivery/Indefinite Quantity (IDIQ) contract with Firm

Fixed Price (FFP) and Cost-Plus Fixed Fee (CPFF) subordinate task orders (TOs). Specific services shall be requested by TOs issued by the CO. A TO is required for the contractor to initiate any work under this contract.

1.5 Task Order Period of Performance (POP)

The specific POP for each TO under this IDIQ shall be specified at the award of the TO. TOs must be issued and awarded prior to the expiration of the ordering period. After the term of this

IDIQ expires, the IDIQ contract will remain an active contract until the final TO is closed out and shall govern the terms and conditions with respect to active TOs to the same extent as if it were completed during the term of this IDIQ. TO’s performance period may not go beyond one

(1) year after the ordering period expires. TOs shall be priced according to the applicable year rates for the TO’s period of performance.

1.6 Task Order Instructions

Requirements in the PWS shall be implemented and directed by task orders, issued by the

Contracting Officer (CO) except under extenuating circumstances. The contractor shall not proceed with the work until the cost is negotiated. Task orders shall describe the work to be performed, the total cost, and the performance schedule. Funds will be obligated by each task order but may be incrementally funded. Prior to issuance of task order, the Government will issue a request for proposal that includes: a detailed description of the work to be accomplished, the period of performance, a list of deliverable CDRLs, the contractor’s response date, and additional data as appropriate to assist the contractor in understanding the task. The contractor shall submit a detailed technical and cost proposal. Proposals shall be submitted to the contracting office no later than the stated contractor’s response date.

2 SPECIFIC TASKS

The following provides a broad scope of tasks for each functional area and may not be all inclusive.

A more detailed tasks will be provided on a separate PWS associated to a specific TO. The contractor shall perform tasks to be specified in each individual Task Order (TO), in the areas identified below and shall furnish the services and support required by the Government. The contractor shall prioritize, manage, and support simultaneous TOs at various stages of development and completion at any given time throughout the life of this IDIQ.

2.1 Analysis Support shall include, at a minimum, the following tasks:

2.1.1 The contractor shall develop stand-alone technical documentation and analysis tools to improve the analytical and technical documentation and analytical process.

2.1.1.1 Software. Technical software documentation, software tools, software prioritization, software modifications to existing Government-owned software tools, or software tools to which the Government has unlimited rights, newly developed software tools, and software modifications developed shall grant the government unlimited rights in the said documentation, tools, and modifications. (CDRLs A005-A012)

2.1.1.2 Reference Materials. All reference materials procured, obtained, or otherwise acquired Government sponsorship, or Government means under this contract to perform these analyses shall remain Government property or the property of the original data owner(s) if the Government has limited data rights. Data rights to the above reference materials shall not convey to the contractor. The code/software/solution provided/developed in the performance of this requirement is the property in perpetuity of the United States Government and shall be delivered to the Government as a complete and working copy with no financial encumbrance or license restrictions. Any software, commercial or custom, necessary for the successful operation of the application/solution/system becomes the property of the Government with no licensing restrictions or further or additional cost to the Government.

2.1.2 The contractor shall conduct studies to include requirements definition, cost performance analysis, feasibility studies, long-range analysis, and other studies into aspects of the 57 IS assigned mission areas. The contractor shall provide reports which document the problem aspect(s) studied, the methodology investigated, and the results of investigatory effort. (CDRLs A001, A003-A005)

2.1.3 The contractor shall support the organization, execution, preparation, and presentation of material for various committee meetings, seminars and conferences. This shall include but is not limited to the annual Electromagnetic Warfare Integrated Reprogramming Data Base (EWIRDB)

Forum, EWIRDB Standardization Committee Working Group, Intelligence Mission Data

Committee (IMDC) Working Group, the Allied IMD Signatures Working Group, IMDC Surveys, IMDC Signatures Life-cycle Survey and IMD Production, and various sub-groups within the

Mission Planning Interface Control Working Group (ICWG). (CDRLs A004, A005, A014)

2.1.4 The contractor shall provide support in the form of oral and written presentations, program and project reviews, meeting preparation and attendance at such times and places as required by the Government. The contractor shall prepare studies, program plans, and publications for 57 IS dissemination (in formats designated by the 57 IS). (CDRLs A003-A006, A014)

2.2 Production Support shall include, at a minimum, the following tasks:

2.2.1 The contractor shall create, replace, update, and delete USELMSDB, EWIRDB, NEDB, BATS, CSDB, platform characteristics and performance, IMD, and TechSIGINT related studies in accordance with (IAW) the corresponding study creation process, quality control processes and guidance given by 57 IS. The contractor shall migrate specified 57 IS IMD data product information to USELMSDB, EWIRDB, CED, CSDB, BATSDB, and NEDB compatible formats as directed by 57 IS. The contractor shall identify similar systems to be combined in an effort to conserve time and avoid report duplication. USELMSDB, EWIRDB, BATSDB, and CSDB file production shall be completed simultaneously to economize the production effort. The number and types of file and data production will be set by subordinate TOs issued under this contract. A rough order of magnitude (ROM) estimate, not binding on the Government, for these production types is 100 USELMSDB/EWIRDB studies, 300 CSDB studies, 100 platform characteristics and performance studies, and 12 NEDB files per TO per year, depending on immediate Government needs and available funding. The number of external RFIs* per year is highly variable. (CDRLs

A001, A003)

2.2.2 The contractor shall use appropriate researched information and the laws and principles of electromagnetic science when there is a lack of information available on an assigned system. The contractor shall consult with the COR concerning questions dealing with the accuracy or validity of the data entries and the adherence to analysis and technical standards of practice. The contractor shall respond to the COR concerning questions dealing with the accuracy or validity of the data entries and the adherence to analysis and technical documentation strategies.

2.2.3 The contractor shall document all methods and procedures used for acquisition of data, analysis of the data, quality control of data, and procedures and methods used for de-conflicting various sources of data in the analyst’s notes section of the individual studies. The contractor shall ensure the Government will have access to the metadata concerning technical quality of specified, measured, and predicted data. (CDRL A001)

2.2.4 The contractor shall, after analyzing each electromagnetic system, prepare a finished report

IAW applicable standards listed in this PWS and shall include all appendices and attachments.

(CDRLs A001, A003)

2.2.5 The contractor shall monitor and track system folder analysis status within (a) Government approved database(s). The Government may request copies of this data on up to a weekly basis.

(CDRL A003)

2.2.6 The contractor shall create, replace, update, and delete multiple data formats required by the unique models, tools, and standards prescribed by the IMD, Mission Planning, EW, and

TechSIGINT communities. The contractor shall ensure produced system studies meet community guidelines and the systems shall successfully load in standard USELMS, SAVANT Architecture, and OPANA toolsets (i.e., EIM/OEEM generation) and shall include STRIKE FORCE+, KEYSTONE, TOPAZ, Joint Analytical Data Editor (JADE), and NightHawk Editor.

2.2.7 The contractor shall support 57 IS analysts in responding to RFIs, production requirements, and problem reports pertaining to EWIRDB, USELMSDB, Platform, Signatures, BATS, and

CSDB systems and their use. Final delivered format is dependent on the specifics of each RFI and

Request for Production (RFP). (CDRLs A001, A003)

2.2.8 The contractor shall perform special research projects pertaining to parametric data, signature data and events, system C&P and associated electronic fit. Final delivered format is dependent on the specifics of each research project. (CDRLs A001, A003, A005)

2.2.9 Contractor Field Test Measurement Support. The contractor shall attend and participate in field test measurements; report on attendance, lessons learned, recommended techniques, and data pedigree; and, work as liaison to obtain measurement signature data The contractor shall report to the Government of any obstacles and issues in acquiring the data and include recommendations and possible solutions documented in a technical report.

2.2.10 The Government has unlimited data rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting

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

2.2.11 For data file and model production, the contractor shall use existing software and tools for which the Government has unlimited rights. Additionally, the contractor shall provide software development and modification services to replicate pre-existing code, programs, and applications produced from other external customers, such as, but not limited to Special Program Offices and

Joint Program Offices to implement methodologies to meet mission requirements. The contractor shall provide parametric data to perform analysis using the Electromagnetic Antenna Tool

(EMAT) and similar Multi-beam Antenna Tool. The contractor shall acquire the requisite Altova

MapForceR 2021 license for use with the NightHawk to Military Equipment and Parametric

Engineering Database (MEPED) data translator update tool. As a minimum, the contractor shall conduct monthly technical interchange meetings with the Contracting Officer, Government Program

Manager, and 57 IS to ensure the NightHawk to MEPED software tool correctly functions to meet mission requirements as well as ensure that parametric data for EMAT and the Multi-Beam tools is being properly provided. The contractor shall deliver the Nighthawk to Military Equipment and

Parametric Engineering Database (MEPED) data translator software tools to the 57 IS within 12 months of contract award. The Nighthawk to MEPED translator will be provided as Government

Furnished Equipment (GFE). (CDRL A001)

2.3 Research Support shall include, at a minimum, the following tasks:

2.3.1 The contractor shall locate and obtain the data required to complete research on all assigned

BATS, CSDB, and USELMS systems for inclusion in the research input package. The contractor shall document the research results in the research tracking system used by the 57 IS. The contractor shall notify the GPM, CO and COR when International Organization for

Standardization (ISO) recommends developments which would be advantageous to the 57 IS. The contractor shall notify the Government when insufficient data is available to complete the study being tasked immediately upon discovery. The contractor shall be responsible for examining all required primary data sources and networks (Attachments 1 and 2). The contractor shall obtain official endorsement demonstrating need-to-know from the GPM, CO and COR to complete the assigned system research.

2.3.2 The contractor shall provide on-site BATS, CSDB, and USELMS researchers with the required expertise to perform all levels of research tasking and with the appropriate security clearances. The contractor shall staff the off-site technical library with qualified personnel to provide the appropriate technical research required in support of the 57 IS and this contract. Staff analysts shall provide research support. The contractor shall locate and provide all requested documents within 24 hours after receipt of notice.

2.4 Technical Library Support shall include, at a minimum, the following tasks:

2.4.1 A technical library is required in the performance of this contract. The Government will provide the initial technical library. The contractor shall accept and maintain technical site library

(at the local contractor’s facility) at the beginning of the performance period but no later than 30 days after the start of the TO POP of this contract, whichever is shorter. The contractor shall respond to all automated systems prompts from Technical Order (TO) changes to update and maintain all documentation gathered in support of this contract. These documents shall be maintained in the Technical Site Library unless otherwise coordinated with the GPM and COR.

Upon receipt, the contractor shall post all changes within 30 calendar days in required locations.

Documents will be classified up to SECRET//NOFORN and may be proprietary in nature. The contractor shall provide access to the technical library in contractor spaces on short notice including after hours and on weekends. The portion of the library, which consists of Air Force technical orders and documents belonging to the Air Force and Department of Defense (DoD) agencies, shall be maintained IAW Air Force and DoD instructions. The contractor shall not release any data to another Government agency or contractor without the written permission of the

57 IS. The technical site library contents shall be properly inventoried and returned upon completion of the contract. The contractor shall reference paragraph 7.24 to this PWS for the

Technical Library Phase-Out/Phase-In Plan.

2.4.2 The contractor shall maintain a Government approved record system, such as the library database, for the technical site library from which the Government may request abstracts, inventories, document locations, and other reports. The contractor shall provide a record system

(compatible with the 57 IS technical library) for these bibliography references. The Government may request copies of this data on up to a weekly basis. The contractor shall provide a current monthly listing of all publications contained in the technical site library to the COR. (CDRL A002)

2.4.3 The contractor shall use the technical site library to gather and maintain information on assigned systems. The contractor shall perform limited research on designated topics in the 57 IS library when coordinated with the 57 IS research personnel.

2.4.4 The baseline technical site library collection will be transferred by the Government to the contractor in accordance with paragraph 7.24. Technical site library transfer shall begin once the required facility clearance has been awarded to the contractor by the cognizant security office

(Reference 7.24). References shall be maintained at the contractor facility to aid analytical and research capabilities. The contractor shall have appropriate on-line and other data sources as required by the Government. The 57 IS will provide the contractor’s need-to-know and approval for access when required for the above on-line sources.

2.5 Computer System Administration and Software Development Support shall include, as a minimum, the following tasks:

2.5.1 The contractor shall provide systems support for MS Windows and UNIX-based systems.

System support shall include troubleshooting hardware, software, and networking problems that arise in those systems and returning same to operation. The contractor shall possess an in-depth knowledge of a variety of operating systems which shall include, but not limited to, those required for MS Windows, various UNIX and UNIX-like operating systems, and other computer systems introduced during the life of the contract. The contractor shall support users in solving problems caused by the addition of hardware or software.

2.5.2 The contractor shall evaluate and integrate Commercial Off-The-Shelf (COTS)/Government

Off-The-Shelf (GOTS) software for the 57 IS IntraWeb and other networks. The contractor shall address inter-relationship issues of webservers, databases, and Computer Graphics Interface (CGI) programming technology and the workings of the operating systems at the machine administration level. The contractor shall install, test, evaluate, and integrate COTS/GOTS hardware and software.

The contractor shall support the network user in solving problems related to networking, computer hardware, operating systems, and application software. The contractor shall develop and integrate newly developed code to meet 57 IS requirements when the Government GOTS/COTS solutions are not acceptable. (CDRLs A006- A012)

2.5.3 The contractor shall provide planning, design, development, testing, prioritization, and implementation of SENSOR BEAM databases which require COTS relational database software tools. This shall include such COTS items such as ORACLE, SYBASE, or PostgreSQL relational database management systems software tools in UNIX or MS Windows client/server workstation configurations, and other configurations involving MS Windows compatible workstations.

(CDRLs A004-A012)

2.5.4 The contractor shall provide planning, design, development, testing, and implementation of modernized software tools associated with the population and modification of SENSOR BEAM databases and distribution means such as web sites. Such tools shall include platform-independent software applications that expand capabilities and increase ease-of-use for both producers and users of the SENSOR BEAM databases. Such applications shall include but are not limited to analysis, logging, management, data delivery (export) support, and database tools. (CDRLs A004-

A012)

2.5.5 The contractor shall support risk management framework (RMF) certification and accreditation for software, hardware, and network systems on behalf of the 57 IS. The contractor shall provide planning, development, and review of certification and accreditation packages for all hardware, software tools, database configurations, and web interfaces deployed on Government networks. (CDRLs A006, A007, A009, A011)

2.6 Technical Data and Delivery Support shall include, at a minimum, the following tasks:

2.6.1 The contractor shall create, replace, update, and delete analytical studies in accordance with paragraph 2.2.1 above. The contractor shall successfully complete all technical data studies through the analysis process and shall produce quality control (QC) reports for each TO requirement. These reports shall consist results of parametric comparison, signature, and event data entries against each other and the data standards for reasonable values. When available, other databases (e.g., EWIR, CED) shall be used for comparison; and updated when required. The contractor shall maintain consistent format. The step-by-step procedures used by the contractor to maintain the quality of the data shall be defined in the QC report. Upon completion of contractor

QC, the Government will review the data for proper formatting and data accuracy and will provide written notice to contractor of the Government’s acceptance review. (CDRL A001, A003)

2.6.2 The contractor shall prepare and deliver parametric data shipments. Shipments shall be scheduled or ad hoc depending on data consumer requirements and data criticality. Scheduled quarterly CSDB shipments and monthly USELMS updates shall ensure the production infrastructures are periodically synchronized. Shipment of completed analysis studies shall include both inside and outside of the 57 IS. This shall vary and is based on data type and end user requirements. This will be specified in subordinate TOs. These shipments shall originate directly from the contractor’s facility or through the mail room in building 2000, JBSA Lackland, Texas.

(CDRL A001)

2.6.3 The contractor shall prepare and deliver monthly status reports and monthly status and funds reports for each individual task order in accordance with the CDRL list. Each task order report shall accurately reflect all task activities conducted in the previous month. (CDRL A013)

2.6.4 The contractor shall prepare a final status report upon completion of each task order. This shall include an electronic version of all monthly and trip reports generated under each task order. (CDRL A013)

2.6.5 The contractor shall transport classified and unclassified materials between the contractor and 57 IS facilities. The contractor shall adhere to all applicable Government security regulations, including courier qualifications and regulations governing the couriering and transportation of classified material.

2.6.6 The contractor shall provide sufficient space to accommodate up to two Government personnel at contractor site for quality reviews, acceptance reviews, analytical exchanges, US Air

Force (USAF) network administration, software beta testing, document review and other purposes.

Appropriate equipment shall be made available to accomplish these tasks in this space.

2.6.7 The contractor shall attend meetings, guidance interchanges, and working groups as outlined in individual TOs. The contractor shall provide minutes of all forums, meetings, and other venues attended pursuant to this contract to the SENSOR BEAM Government Program Manager and the COR. (CDRL A014)

2.6.8 The contractor shall attend a quality review meeting 30 working days prior to submission of the final report on each Task Order, unless waived by the COR. This meeting shall be used to discuss discrepancies found in previous contractor work, to provide guidance for future tasking, and for the contractor to outline any plans, suggestions, or problems with past or future tasking.

The contractor shall develop and provide minutes for all meetings. (CDRL A014)

2.6.9 The contractor shall develop a front-line customer-service department for the entire squadron. The contractor shall be responsible for administrative duties such as customer requests, following up with customers to define requirements, delivery schedules, and coordination with production flights, COLISEUM, AIRVIEW, and other such requirement processes. Contractor shall take questions and feedback from customers. Contractor shall serve as a requirements manager, gather data, and manage customer requests. Contractor shall be responsible for providing guidance to users on how to navigate the 57 IS website, find the right product, or point the user to the right people (i.e., Flight) to contact, and document the entire process. Contractor shall attend measurement exercises and follow up with testers, thereby building relationships in order to bring back data for all squadron databases. Contractor shall be responsible for resolving issues on data and coordinate with 57 IS leadership.

2.7 Training Support shall include, as a minimum, the following tasks:

2.7.1 The contractor shall possess and maintain the expertise and capability to support the 57 IS representatives in developing, producing, and delivering 57 IS training courses. Contractor shall be responsible for resolving issues on data and develop, produce, and deliver training courses and provide instruction in analysis, quality control of parametric and signatures studies and other activities as specified in the TOs. These courses shall be developed for the 57 IS analysts and other customers (to include representatives of foreign nations in accordance with Section 10 of the

National Industrial Security Program Operating Manual (NISPOM) and 22 CFAR 120 – 130 of the

International Traffic in Arms Regulations (ITAR). These courses shall be taught in the United

States of America (USA) and other countries as required by the 57 IS. The contractor shall negotiate and maintain Technical Assistance Agreements (TAAs) with key US allies to provide training and familiarization in accordance with the ITAR. (CDRLs A004, A005, A012)

2.8 IMD Production

2.8.1 Production Analysts shall have expertise in producing Electromagnetic Warfare Integrated

Reprogramming (EWIR) files in all the three (3) different IMD Tier levels (e.g., I, II, and III) and combinations of complexity level (e.g., 1 through 4). File production shall consist of basic information gathering, data reduction, product preparation, database production, and data export functions for related parametric products and models such as: Electronic Intelligence (ELINT)

Intercept Model and Observed ELINT Engineering Model (EIM/OEEM); Radar Threat Model

(RTM) and Transition Logic Maps (TLM); North Atlantic Treaty Organization (NATO) Emitter

Database (NEDB); Foreign Military Sales (FMS) variants; Military Equipment Parametrics and

Engineering Database (MEPED); Combat Support Database (CSDB); Blue Airborne Target

Signatures (BATS); Improved Many-on-Many (IMOM) Model; Threat-On-The-Fly (TOTF) and the Common Low Observable AutoRouter (CLOAR); Air Force Mission Support Systems

(AFMSS); Joint Mission Planning System (JMPS); Portable Flight Planning System (PFPS); and the Combined Emitter Database (CED).

2.8.1 Signatures Analysts shall have expertise in producing Radar Cross Sections (RCS) (3D and

Bowtie), Antenna Patterns, Electro-optical and Infrared (EO/IR), Acoustics, Joint Electromagnetic

(JEM), and high range resolution (HRR data).

3 SERVICES SUMMARY (SS)

3.1 The contract service requirements are summarized in performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimally acceptable levels of service required for each requirement. The Services Summary (SS) provides information on contract requirements and the expected level of contractor performance to be successful. These thresholds are critical to mission success. Procedures as set forth in the applicable Services Inspection Clause in the contract and will be used to remedy all deficiencies.

The Government retains the right to inspect any item included in the contract. Task Order (TO) specific Service Summaries will be included with each specific TO.

PERFORMANCE OBJECTIVE

PWS

PARAGRAPH

PERFORMANCE THRESHOLD

SS # 1.

The contractor shall ensure that databases have the most current versions of all system analysis files within ten (10) business days of file availability. The contractor shall ensure back-ups occur no less every seven (7) days. The contractor shall ensure database content and structure summaries are available within five

(5) business days of request.

2.2.5, 2.2.6 Excellent: Meeting timeline requirements

100% - 95% of the time

Very Good: 90% - 94%

Satisfactory: 85% - 89%

Unsatisfactory: Less than 84%

SS # 2. 2.2.7 Excellent: compliance with delivery schedule and consistency of information

The contractor shall maintain a log of RFI’s and acknowledge receipt of an RFI to COR or

Government representative within ten (10) business days.

The contractor shall provide answers to RFIs within the assigned timelines, consistent with available information / intelligence (if not contradictory) to meet the customers’ needs.

Very Good: One (1) schedule breech per month or one (1) inconsistency event:

Satisfactory: Two (2) schedule breeches and or two (2) inconsistency events per month

Unsatisfactory: Three (3) or more schedule breeches and or inconsistency events per month

NOTE: For additional issues, the contractor shall notify the COR within 48 hours of the RFI detailing the estimated timeline for submission and issues causing the delay.

SS # 3.

The contractor shall ensure all shipments of existing data are formatted, packaged, tested, and shipped within five (5) business days of a routine or ad hoc update. The contractor shall maintain a current and accurate shipment log.

2.2.1 Excellent: Shipments from 98% to 100%

on time with 98%-100% accurate shipment log

Very Good: Shipments 95% - 97% on time and/or 95% - 97% accurate shipment log

Satisfactory: Shipments 90% -94% on time and / or 90% - 94% accurate shipment log

Unsatisfactory: Shipments less than 90% and / or multiple shipment log error; or non-performance

SS # 4.

The contractor shall perform engineering-level analysis and quality control on various military and commercial electromagnetic systems, documenting the characteristics of each system in the analysis study and quality control file.

2.2.1, 2.2.4, 2.2.7, 2.2.8

The contractor shall ensure completed files contain all required information and adhere to 57IS USELMS, CSDB standards, format, and technical requirements of the relevant production definitions, guides, Quality control, General purpose, and analyst notes.

For the below quality expectations, Pass

Rate is defined as the percentage of files that make it through government acceptance review without being sent back to the “Fix” process point. They will be evaluated on a per file type basis.

For USELMS Platforms and

Communications analysis quality expectations are as follows:

Excellent: 95% and higher Pass rate

Very Good: 90% - 94% Pass rate

Satisfactory: 85% Pass rate

For all remaining USELMS analysis, quality expectation are as follows:

Excellent: 95% and higher Pass rate

Very Good: 85% - 94% Pass rate

Satisfactory: 75% Pass rate

For CSDB analysis, quality expectation are as follows: For weapons (AAA, MSL, DEW, etc.), sensors, platform, and communication systems (future development)

Excellent: 95% Pass rate

Very Good: 90% Pass rate

Satisfactory: 85% Pass rate

For CSDB analysis, quality expectation are as follows: For all radar systems

Excellent: 95% Pass rate and higher

Very Good: 85% - 94% Pass rate

Satisfactory: 75% Pass rate

SS # 5

The contractor shall develop and maintain a security program to effectively meet all the security rules and requirements, including the

Defense Security Service (DSS) requirements of this IDIQ and subsequent Task Order(s).

Clearances and background checks shall be completed in accordance with an agreed upon schedule.

6.2, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8

If clearances and background checks are:

Excellent: Completed on schedule, or early

Very Good: 1-2 late per month

Satisfactory: 3-4 late per month

Unsatisfactory: >5 late per month or non-performance

SS # 6

The contractor shall maintain 24/7 access to a secure facility within 25 miles of the 57 IS.

The contractor shall provide access to analyst workstations and library within one (1) hour of a telephone notification of COR visit.

2.4.1, 5.1 Access to analyst workstation and library:

Excellent: within an hour or less

Very Good: within 1.5 hours

Satisfactory: within 2 hours

Unsatisfactory: >2 hours or non-performance

SS # 7

The contractor shall accept and maintain a technical reference library for use by analysts and researchers.

Library shall retain, track, and be able to locate

100% of the documents used for an existing or in-work system analysis by the engineers within eight (8) hours of request.

2.3.2, 2.4.1, 2.4.2

If the document or data is provided:

Excellent: within 8 hours

Very Good: within 9-10 hours

Satisfactory: within 11- 12 hours

Unsatisfactory: >13 hours or non-performance

SS # 8

The contractor shall install and maintain updates of all shared software applications.

All software updates and accreditation shall be installed within ten (10) business days of availability.

2.5.1, 2.5.2, 2.5.3

Software updates are delivered:

Excellent: 10 days or less

Very Good: 11-12 days

Satisfactory: 13 – 14 days

Unsatisfactory: >15 days or non-performance

SS # 9

Produce Blue/White radar cross section signature data and data files.

Signature data files shall meet the Joint

Mission Planning System’s Interface Control

Document (ICD) Appendix K.

Signature data files shall conform to 57 IS’ 3-dimensional, BowTie, “. RCS”, and “. POL”, and HRR

2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.2.6

Signature data files meet JMPS ICD

Appendix K and conform to specs:

Excellent: Compliance-no errors

Very Good: One (1) event per month

Satisfactory: Two (2) events per month

Unsatisfactory: More than three (3) non-compliant files per month; or non-performance

SS # 10

Generate computer-aided design (CAD) models for usage in electro-magnetic modeling and simulation tools such as

Xpatch.

CAD models shall not contain overlaps nor intersects.

Within 30 business days after the validation process, CAD models shall be delivered and government accepted/verified that it runs in

Xpatch or similar electro-magnetic prediction codes.

The contractor shall apply software smoothing techniques as needed or provide engineering assessments on the significant output differences.

1.3.1, 4.72 CAD modeling in Xpatch (or specified simulation tool) and does not contain overlaps nor intersects. Gov accepted/and verified for correct operation; provide smoothing techniques or engineering assessments for unique data within 30 business days of validation.

Excellent: Meets 30 business day suspense and all requirements

Very Good: Meets 30 business day suspense with one (1) of the following per month: An overlap or intersect; no software smoothing applied; missing engineering assessment for significant output differences.

Satisfactory: Meets 30 business day suspense with two (2) of the following per month: An overlap or intersect; no software smoothing applied; missing engineering assessment for significant output differences.

Unsatisfactory: Exceeds 30 business day suspense or three (3) of the following per month: An overlap or intersect; no software smoothing applied; missing engineering assessment for significant output differences. Non-performance

SS # 11

Research and acquire material properties, signature data, for airborne platforms, countermeasures, and munitions.

Provide monthly report of sources/locations researched, as well as material that was acquired. Report shall be delivered no later than 10 days after the end of the month.

Please see QASP Paragraph 9.2.1 for additional information.

2.1.1, 2.1.1.2, 2.1.2, 2.1.3

Provide a monthly report per Contract

Data Requirement List (CDRL) and deliver:

Excellent: 10 days or sooner after the end of the month (EOM)

Very Good: 11-12 days after EOM

Satisfactory: 13-14 days after EOM

Unsatisfactory: >15 days or non-performance

SS # 12

Develop, test, and evaluate software applications.

The contractor shall conduct a quarterly capability demonstrations with COR to verify and validate government software requirements.

Please see QASP Paragraph 9.2.1 for additional information.

2.5.2 Contractor conducts a quarterly capability

demo to validate software requirements:

Excellent: Conducted quarterly

Very Good: A demo that is up to two (2) weeks late with advanced notification to

COR

Satisfactory: Demo up to one (1) month late, with adv notification to COR

Unsatisfactory: >One (1) month late and/or no advanced COR notification; or, non-performance

SS # 13

Produce Technical Reports:

The requested documentation shall be delivered within six (6) weeks of request, with formats pre-coordinated with the 57IS.

As a minimum, the report(s) shall have the following sections: introduction, methodology, findings, and a summary.

Please see QASP Paragraph 9.2.1 for additional information.

2.1.1, 2.2.2, 2.6.8

Requested technical documentation provided:

Excellent: Within six (6) weeks of request in specified format

Very Good: Within six (6) weeks but contains one or two format errors

Satisfactory: Within seven (7) weeks and/or contains less than 3 format errors

Unsatisfactory: >Seven (7) weeks and/or contains more than four (4) formatting errors; or, non-performance

SS # 14

The contractor shall perform engineering-level analysis and quality control on various military and commercial signature data

(measured or modeled); documenting the characteristics of each system in the analysis study and quality control file.

Requested documentation shall be delivered within six (6) weeks of request from 57IS.

As a minimum, engineering-level analysis studies and/or quality control files shall have the following sections: introduction, methodology, findings and summary.

Please see QASP Paragraph 9.2.1 for additional information.

2.2.1, 2.2.4, 2.2.7, 2.2.8

Contractor provided Engineering-level analysis and quality control along with documented characteristics of each system requested:

Excellent: Within six (6) weeks of request in specified format

Very Good: Within six (6) weeks but contains one or two format errors

Satisfactory: Within seven (7) weeks and/or contains less than 3 format errors

Unsatisfactory: >Seven (7) weeks and/or contains more than four (4) formatting errors; or non-performance

SS # 15

Administer databases

Ensure all databases up to date with required patches as directed by 57IS within ten (10) business days of patch releases.

The contractor shall implement required changes based upon mission requirements within six (6) weeks of requirement.

Please see QASP Paragraph 9.2.1 for additional information.

2.5 Databases are up to date with patches:

Excellent: Implemented in ten (10) business days, or less, and addresses mission requirement changes within six

(6) weeks of requirement

Very Good: Within11-12 business days and mission requirement changes within

(6) weeks

Satisfactory: Within 13-14 business days and mission requirement changes within six (6) weeks

Unsatisfactory: >15 business days and/or greater than six (6) weeks for mission requirement changes; or non-performance

SS # 16

Design databases

Achieve single sign on capabilities for database, through web applications, validated

2.5.2 Contractor achieves a single sign on, through web applications, and validate / approve customer’s request.

and approved within 10 business days of customer request for access.

The contractor shall ensure that all data within database must be searchable and retrievable.

When conducting a search, all related records shall be available.

Please see QASP Paragraph 9.2.1 for additional information.

The contractor ensures that all data must be searchable and retrievable; all records shall be available.

Excellent: Ten (10) business days or less

Very Good: 11-12 business days of request

Satisfactory: 13-14 business days of request

Unsatisfactory: >15 business days of request and/or database search errors; or non-performance

SS # 17

Represent the 57 IS in community forums and working groups.

Per COR direction, contractor shall present up-to-date information concerning 57 IS

Signatures production and contact information within 30 business days upon returning from each forum, venue, or working group.

2.7.1 The contractor provides current

information on 57 IS Signatures production and contact information:

Excellent: Within 30 business days of return from each forum, venue, or working group. Very

Good: Within 35 business days of return from each forum, venue, or working group.

Satisfactory: Within 40 business days or return from each forum, venue, or working group.

Unsatisfactory: Greater than 45 business days of return from each forum, venue, or working group, or non-performance.

3.2 Performance Evaluation: Contractor performance is subject to surveillance by a

Government PM and/or COR to ensure compliance with PWS.

3.3 Quality Assurance Surveillance Plan (QASP): The Service Summary(ies) will be used as the baseline to develop a Government QASP. The contractor shall update the Government on Service Summary status during a monthly meeting or Technical Interchange Meeting. The

QASP will identify the audit methods and procedures the Government will use to evaluate the contractor’s performance.

3.4 Surveillance: The Government reserves the right to surveil all services and requirements called for in the PWS to determine whether the contractor is meeting performance objectives and goals.

4 GOVERNMENT FURNISHED PROPERTY (GFP) AND SERVICES

4.1 Accountability

4.1.1 The GPM, CO and COR must approve all Government Furnished Property activities.

Government Furnished…