Attachment 6 - Draft PWS IDIQ.docx

United States Air Forces in Europe United States Air Forces Africa

(USAFE-AFAFRICA)

Air Base Air Defense (ABAD) Indefinite Delivery/Indefinite Quantity (ID/IQ)

Performance Work Statement (PWS)

13 July 2020

1. DESCRIPTION OF SERVICES

1.1. General. This Indefinite Delivery Indefinite Quantity (ID/IQ) service contract is for supporting operations, maintenance, and integration of the United States Air Forces in Europe – Air Forces Africa (USAFE-AFAFRICA) Air Base Air Defense (ABAD) initiatives. This contract provides the full spectrum of ABAD capabilities for USAFE-AFAFRICA, as well as other strategic and operational partners throughout the United States European Command (USEUCOM) and the United States Africa Command (USAFRICOM) area of responsibility (AOR). Unless otherwise specified, all the requirements defined within this Performance Work Statement (PWS) shall be accomplished at the Task Order (TO) level.

1.1.1. While there is not a separate ABAD contract in place currently, a variety of products and analysis services, such as Advisory and Assistance Services (A&AS), the MITRE Corporation, and the Massachusetts Institute of Technology/Lincoln Laboratory (MIT/LL), provide the Government with the technical expertise necessary to complete all of the current ABAD requirements.

1.2. Mission. The United States Air Force (USAF) directs operations from forward deployed locations worldwide and throughout ten Geographic Commands. ABAD operations are conducted in, from, and through all domains (air, land, maritime, space and cyberspace), across all phases of operations and environments. The USAF is adapting its power-projection and defense concepts to operate under a greater threat of attack. The specific mix sensors, non-kinetic, and kinetic systems, etc., will vary depending on the political geography of the region, adversary capabilities, and United States (US) objectives. The ABAD effort requires the integration and fusion of multiple sensors, weapons systems across the entire spectrum of a mesh network to Find, Fix, Track, Target, Engage, and Assess (F2T2EA) a spectrum of threats, from small Unmanned Aircraft Systems (UAS) to Hypersonic. This enables real time information and response options for the Commander and Warfighter.

USAFE-AFAFRICA is a Combat Major Command responsible for supporting two geographic unified commands, USEUCOM and USAFRICOM. Its mission is forward projecting power across air, space, and cyber domains, defend US interests, demonstrate warfighting readiness, and forge strong partnerships in support of USEUCOM and USAFRICOM campaign objectives. USAFE-AFAFRICA supports a range of military operations which require the ABAD capabilities identified in this contract.

1.3. Scope. The ABAD ID/IQ shall provide persistent, cross-domain base defense capabilities that increase deterrence/engagement options, survivability, and increase base security/defense posture. This contract will support freedom of movement, increase partnership capacity and interoperability, and foster global security and stability throughout the AORs.

1.3.1. Phase 1. Support for ABAD Development at the Ramstein Air Defense Systems Integration Laboratory (RADSIL). The initial phase will be the support for the Government development systems and facilities of the air defense systems integration laboratory at Ramstein Air Base (the RADSIL). Support will be comprised of the maintenance and documentation of the RADSIL, specifically maintenance of the command and control (C2) information systems, network communication subsystems, and commercial off-the-shelf (COTS) sensor systems.

The RADSIL will use a mix of COTS, Government Furnished Equipment (GFE), and custom software to provide command and control. The computer hardware and software will embody modern techniques for automaton, for both operational C2 and system maintenance. The C2 system will employ techniques for distributed, networked computing to achieve robust and timely response to air threats.

It is anticipated that the RADSIL will incorporate GFE and other sensors, systems and data feeds not purchased through the RADSIL ABAD project. For those systems, the Contractor shall ensure the proper connectivity and integration of those systems, when available.

The Contractor shall participate in the ongoing development activities at the RADSIL to ensure the design of an effective and sustainable ABAD capability to be produced in subsequent phases for Ramstein and across the designated bases within the EUCOM/AFRICOM AOR. This will be accomplished through the delivery by the Contactor of a documentation package covering the construction and maintenance of the ABAD systems exemplified by those of the RADSIL. Further, the Contractor shall develop and document, in partnership with the Government, the measures of effectiveness, concepts of operation, training, testing, and instrumentation needed to support ongoing, high availability operations of those ABAD systems. Documentation of the facilities and infrastructure required by these systems will also be delivered.

The RADSIL shall provide an initial, limited ABAD capability as new systems are integrated and made available to current base defense personnel. [‘Fight with the prototype.’] Phase 1 work and the RADSIL facility will ultimately deliver end-to-end air defense C2 but may not represent the full and final laydown of material and personnel to support permanent full-scale, 24/7 operations. Any additional systems needed shall be documented as part of this work.

1.3.2. Phase 2. Air Defense Systems and Operations at Ramstein Air Base. The second phase of the ABAD work is the development and creation of a permanent air base air defense C2 capability for Ramstein Air Base, and the transition from provisional operations of the RADSIL system developed and documented in Phase 1. The Ramstein ABAD systems will use the RADSIL as a template and will be built, operated, and maintained in accordance with the documentation and plans developed in Phase 1. The network of distributed sensors and operator consoles developed in Phase 1 will be connected to the Phase 2 C2 fusion systems. Any additional sensors needed to scale from the initial phase to full capability (as defined by the work of Phase 1) shall be procured and installed by the Contractor in this phase as specified in the TOs.

Note that the RADSIL systems and data feeds will be maintained as part of Phase 2 but will be used only for off-line integration and test, rather than operations. The RADSIL shall remain connected to the sensors and data feeds, and so could act as a backup base air defense C2 facility. A physically separate operational backup C2 facility may be developed as part of this phase.

1.3.3. Phase 3. Air Base Air Defense for Additional Bases in the EUCOM/AFRICOM AOR. The final phase of air base air defense development will be the construction, operation, and maintenance of the systems for air defense of additional bases within the EUCOM/AFRICOM AOR. It is assumed that the architecture and metrics for effective base defense will be the same or similar for each of these bases. For example, the threat set, warning timelines, and the engagement sequence will be the same as those addressed in Phase 2 by the ABAD system developed for Ramstein AB. However, the physical layout and geography of each base will dictate a unique laydown of sensors to support the required effectiveness. Overlapping regions for coverage of sensors and communication systems around multiple bases shall be considered for efficiency. Likewise, the consolidation of operators and maintenance staff shall also be included in any proposed work for this phase.

1.4. This contract utilizes Firm-Fixed-Price (FFP), Fixed Price Incentive Firm (FPIF), Cost-Plus-Fixed-Fee (CPFF), Cost Plus Incentive Fee (CPIF), and Cost Reimbursable (CR) contract types. The scope of this ID/IQ contract includes Procurement, Integration, Operations, & Maintenance (O&M), and systems engineering of ABAD equipment and infrastructure throughout the EUCOM and AFRICOM combatant commands.

1.4.1. Performance locations will be throughout Europe and Africa. The Contracting Officer (CO) will issue TOs as the ordering mechanism for specific requirements. Any additional ABAD site specific requirements will be outlined within each individual TO.

1.4.2. Contractor support may fall into, but not be limited to, one of the following categories: 1) Program Management; 2) Operations; 3) Maintenance; 4) Air Base Air Defense Weapons System Delivery; 5) Integration of Weapon Systems, Sensors, and Command and Control Elements; 6) Systems Engineering and Special Studies; 7) Logistics Support and Services. Individual TOs shall define which of these support areas will be utilized.

1.4.3. The Contractor shall provide all personnel, supervision, equipment, tools, materials, transportation, and other items and services necessary to perform PWS requirements.

1.4.4. The Contractor shall perform necessary phase-in and phase-out requirements (to include a full Government property inventory) as needed and as directed by the Government.

2. GENERAL INFORMATION

2.1. Non-Personal Services

2.1.1. The ABAD ID/IQ is a non-personal services contract, defined by the Federal Acquisition Regulation (FAR 37.101) as, “a contract under which the personnel rendering the services are not subject, either by the contract’s terms or by the manner of its administration, to the supervision and control usually prevailing in relationships between the Government and its employees.”

2.1.2. The Government shall neither supervise contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual Contractor employees. It shall be the responsibility of the Contractor to manage its’ employees and to guard against any actions that are of the nature of personal services or give the perception of personal services. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor's responsibility to immediately notify the Procuring Contracting Officer (PCO).

2.2. Contract Administration and Management

2.2.1. The Contractor shall accomplish program management efforts to manage the overall program and individual Contract Line Item Number (CLIN) efforts consistent with this contract and all its exhibits and attachments. The Contractor shall maintain a program management structure with a Program Manager (PM) as a single point of contact (POC) responsible for program control and oversight to include establishing processes and administering all ABAD ID/IQ requirements. The Contractor’s POC shall work with the ABAD CO and Government PM as a single focal point for all ABAD Contractor and Government correspondence. The Contractor’s PM shall provide clear and consistent written and verbal response to the Government within 12 business hours of Government-initiated communication (e.g., return phone calls, emails, etc.). The Contractor’s PM shall perform any assigned duties from Ramstein Air Base unless otherwise agreed upon in writing by the CO.

2.2.2. The Contractor shall perform all necessary program management requirements. Program management shall include all organization, administration, control, direction, monitoring, reporting of system/program status, identification of technical/programmatic problems, and recommendations of options/solutions to problems and issues ensuring successful program execution as it relates to the ABAD mission. The Contractor shall provide the Government with timely reports. The Contractor shall participate in the development of work statements. All contractor and sub-contractor personnel supporting the programs shall be technically skilled and qualified, possess proper training, and hold the appropriate security clearances commensurate with their required and granted level of access.

2.2.2.1. The Contractor shall provide a monthly status report no later than (NLT) 15 calendar days after the end of each month to be submitted to the CO and the ABAD Program Manager (PM). The Contractor shall include any changes to company affiliations monthly. The report shall include: 1) changes to company affiliations, 2) summarized accomplishments of the previous month, 2) discussion of major issues and/or concerns with recommended solutions, 3) discussion of Contractor personnel assignment, 4) summarization of current financial billing profile to include projected shortfalls or over-runs/under-runs and 5) a profile of manpower usage. (CDRL A001)

2.2.2.2. The Contractor shall retain and keep all current official files, manuals, charts, drawings, technical orders, and electronic documents required for the performance of this contract in accordance with AFMAN 33-363, AFI 33–364, and DoD 5015.02–STD. Furthermore, the Contractor shall transfer all official documentation and files created, managed, and received to the follow–on contractor or Government personnel during the next contract phase-in period or at the request of the CO or COR. The Contractor shall dispose of operational records and data as directed by the COR if disposal guidance is not provided within other directives.

2.2.3. The data to be delivered because of performing the tasks described within this PWS are specified in the Contract Data Requirements List (CDRL) in Attachment 9. The Government shall review and comment on all data and documentation before Government acceptance, as specified in each applicable CDRL. The Contractor shall provide all CDRL items in accordance with Attachment 9 and on each individual TO as specified.

2.2.3.1. At the beginning of each new fiscal year the Contractor shall begin a sequential numbering of each letter submitted to the Government. Depending on the nature of the correspondence (i.e. Contract issues, operations, or maintenance issues, etc.) a copy of all such correspondence shall be sent to the COR at the Ramstein ABAD site. All submissions shall have a unique fiscal year sequential numbering system specific to the submission. In the instance where a submission is generated by more than one location the numbering system will reference the location. All report submissions shall have a unique sequential numbering system referencing the documents listed in Attachment 9.

2.2.4. The Contractor shall provide the Government with all non-CDRL data which was developed in part or in whole at Government expense via a contractor generated and Government approved Data-Accession-List (DAL). DAL item reproduction and delivery shall be provided via the DATA CLIN within 30 calendar days of Government request, with the administrative effort to do so covered by the CLIN under which the associated effort was accomplished. (CDRL A002)

2.2.4.1. All updated DAL data shall be delivered to the Government within thirty (30) working days (M-F) of Government request. Sixty (60) calendar days prior to the end of this contract the Contractor shall solicit Government direction for the disposition of all program documentation not otherwise dispositioned in the contract. The DAL and associated data shall be updated IAW Attachment 9.

2.2.5. The Contractor shall provide all required financial management, to include demonstrated effectiveness in forecasting, managing, and controlling costs, for this contract and for each TO. The Contractor shall provide monthly Contract Funds Status Reports (CFSR) for all CLINs not more than fourteen (14) calendar days after the monthly accounting close (CDRL A003).

2.3. Subcontractor Management

2.3.1. The Contractor shall be responsible for all management of its subcontractor employees. The prime contractor shall manage work distribution to ensure there are no Organizational Conflicts of Interest (OCI) considerations. Contractors may add subcontractors to their team after notification to the PCO and COR. For all services outside the United States, the Contractor and its subcontractors shall abide by Host Nation laws and the Supplementary Agreement to the North Atlantic Treaty Organization (NATO) Status of Forces Agreement (SOFA).

2.3.2. The Contractor shall enter into Associate Contractor Agreements (ACA) (Attachment 3) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirements as applicable (AF PGI 5317.9000 Associate Contractor Agreements). The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the ABAD system, to ensure the greatest degree of cooperation for the development of the program to meet the terms of this contract. A copy of such agreements shall be provided to the CO for review before execution of the document by the cooperating contractors, as well as after the agreement. All costs associated with the agreements are included in the negotiated cost of this contract. Agreements may be amended as required by the Government during the performance of this contract.

2.3.2.1. ACAs shall include the following general information:

(1) Identify the associate contractors and their relationships.

(2) Identify the program involved and the relevant Government contracts of the associate contractors.

(3) Describe the associate contractor interfaces by general subject matter.

(4) Specify the categories of information to be exchanged or support to be provided.

(5) Include the expiration date (or event) of the ACA.

(6) Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

2.3.2.2. The contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

2.3.2.3. Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement rests with the parties to the agreement, and not the Government.

2.4. Contractor Personnel Qualifications

2.4.1. The Contractor shall provide the necessary resources and infrastructure to manage, perform, and administer the contract. As specified, the Contractor shall provide fully qualified personnel In Accordance With (IAW) the ABAD ID/IQ labor category list (Attachment 4). Qualified personnel shall possess the required security clearances and certifications as specified within each TO. The Contractor shall accomplish tasks by providing qualified personnel possessing the appropriate education, training, trustworthiness determination/security clearance and experience/skills IAW the PWS requirements. Additionally, the Contractor shall provide qualified replacement/substitute personnel which meet or exceed the same position standards. The Contractor shall conform to the contract requirements, specifications, and standards of good workmanship (technical, professional, environmental, safety and health standards).

2.4.1.1. The Contractor shall use a labor mix that will allow them to best complete the requirements of this contract and all follow-on TOs. The Contractor shall ensure the labor categories as defined in Attachment 4, labor category list, and man-hours utilized in the performance of each TO (PWS line item) issued hereunder shall be the minimum necessary to accomplish the tasks. The Contractor shall maintain fully qualified/cleared personnel throughout each TO’s period of performance. The Government shall not reimburse the Contractor for training required to maintain technical proficiency and/or certifications.

2.4.2. Government-required training shall be pre-approved by the CO and will be paid on a cost-reimbursable basis, to include travel and per diem costs IAW the Federal Travel Regulations (FTR) if travel outside of the commuting area is required. The Government may provide a funded amount per TO or the estimated number of personnel and course/conference registration information. The training shall be scheduled to ensure mission disruption is at a minimum, which may require alternate work schedules. Contractors shall attend all training required for in-processing and shall maintain annual training requirements. Any further required Contractor training, qualifications and certifications shall be identified at the TO level. Contractor training shall include, but is not limited to, continued job proficiency training, organizational conflict of interest training, information assurance, anti-terrorism, computer and telecommunication equipment, individual readiness training, force protection and operational security (OPSEC) training.

2.5. Key Personnel

2.5.1. The following shall be designated as “Key” positions. The Government does not intend to dictate the composition of the ideal team to perform this ID/IQ, however the Government reserves the right to specify required labor categories on each TO. Key Personnel shall be assigned for the duration of each TO as applicable.

2.5.1.1. Program Manager (PM)

2.5.1.1.1. The Contractor shall identify a PM by name who shall oversee the management, direction, administration, quality assurance, and leadership execution of the overall ID/IQ. The PM shall be an employee of the prime contractor.

2.5.1.1.2. The PM shall meet the following qualifications:

2.5.1.1.2.1. Authority to commit the prime contractor’s organization.

2.5.1.1.2.2. A Top Secret (TS) clearance with access to Sensitive Compartmented Information (SCI) based on a Single Source Background Investigation (SSBI).

2.5.1.1.2.3. Current Project Management Institute (PMI) Project Management Professional, Program Management Professional (PgMP), or Defense Acquisition Workforce Improvement Act (DAWIA) Level III Program Management certification.

2.5.1.1.2.4. Working knowledge of SOFA requirements, DoD Contractor Personnel Office (DOCPER) regulations, and processes within the AORs identified in this TO.

2.5.1.1.3. It is desired that the PM has the following qualifications:

2.5.1.1.3.1. Experience managing performance-based projects and/or programs with multiple OCONUS performance locations.

2.5.2. The Contractor shall perform program management and deployment coordinator activities as described in Attachment 4. TOs will specify any unique performance requirements outside of the position descriptions.

2.5.3. Employee Conduct: The Contractor shall telephonically notify the COR within 24 hours after the occurrence of any incidents of misconduct by its employees, which violate laws of the US or Host Nation which could impact clearances, base access, or general safety or result in international problems between the US and the Host Nation. The Contractor shall follow up this verbal report, in writing, within 5 working days after the telephone notification. (CDRL A004)

2.6. Location and Hours of Work

2.6.1. The primary place of performance will take place within Government facilities located in USAFE or USAREUR outside the continental United States (OCONUS). Each TO will identify the place of performance. Performance may take place within the continental United States (CONUS) at the Contractor’s facility. If performance is required at other worldwide Government locations on a temporary basis, travel will be included at the TO level.

2.6.2. The Government standard work hours under this contract are Monday through Friday except US Federal holidays and other Government-observed days. A typical work week is eight (8) hours per day, 40 hours per week. All locations may have varying start times between 0600-1730. Notwithstanding holidays and Government closures, the Contractor shall perform IAW the terms established in this PWS and within each individual TO.

The following federal holidays are observed under this contract:

* If date falls on a weekend, the holiday is typically observed on the closest weekday. In addition to the days designated as holidays, the Government may also observe any day designated by federal statute, executive order, or proclamation by the President of the United States.

2.6.2.1. If the duty location is closed, no Contractor services shall be provided unless authorized by the CO in writing. The Contractor shall be responsible for notifying its employees of installation closures.

2.6.2.2. Individual work schedules shall be coordinated with the COR to satisfy overall mission requirements. If the Contractor requests a work schedule for any employee partially or entirely outside the Government’s standard work hours, this shall be approved or disapproved in writing by the COR; any resulting approval shall be at no additional cost to the Government. If Contractor personnel are required to work outside the Government standard work hours, these instances will be specified in each individual TO.

2.6.2.3. If applicable, the Contractor shall propose expected overtime hours in the individual TO proposals. Individual work schedules shall be coordinated with the COR to satisfy overall mission requirements.

2.6.3. Contractor personnel may be required to participate in exercises (approximately two per year). The extent of participation may include role-playing, reacting to exercise injects based on the situation or exercise objectives.

2.6.4. Contractor employees' work may be interrupted or delayed due to safety or security drills, exercise participation, special events, training, or actual emergencies. Contractor employees shall participate in all safety and security training or drills conducted onsite during work hours.

2.6.5. Modified Work Schedules and Locations. The existence of emergency situations, contingency operations, special events, exercise participation, severe weather or any other similar circumstances may require Contractor employees to operate on a modified work schedule (>8 hours per day and/or 40 hours per week), including weekends and legal holidays. If outlined in the TO, Contractor employees may be required to work extended or curtailed hours, depending on events and conditions. These situations may also necessitate teleworking when the work permits it. The COR may approve teleworking by providing written approval to the Contractor specifying the personnel for which teleworking is allowed. This notification will include any limitations on teleworking, to include but not to be limited to the length of time, days of the week, and equipment allowed to be taken offsite. Any requested teleworking approved by the COR shall be at no additional cost to the Government.

2.7. Travel Requirements

2.7.1. Travel within the local area or place of performance to attend meetings, conferences, seminars or perform work shall be considered a cost of doing business and shall not be separately reimbursed as a travel expense. Local area travel is defined as within a 120-kilometer radius of the primary place of performance.

2.7.2. All Contractor travel shall be approved by the COR prior to its occurrence. All travel shall be paid on a cost reimbursable basis IAW the Federal Travel Regulation (FTR). Contractor employees may be required to travel to various locations within the CONUS and OCONUS in performance of TOs. Contractor personnel shall maintain a valid passport throughout the entirety of their involvement in this contract. Estimated travel requirements shall be included in each TO. The Government may provide a funded amount per TO or the estimated times, places, and number of personnel to travel for each TO. Cost estimates will be calculated on a TO basis using the current rates posted on http://www.defensetravel.dod.mil/.

2.7.3. Travel 120 kilometers or more outside the Government’s assigned work areas shall be performed using official Letters of Identification (LOIs). LOIs shall be prepared by the Contractor for coordination, approval, and funding by the COR. Funding shall include per diem in accordance with the FTR. The Contractor shall generate a Travel Authorization Request (TAR) and forward it to the COR for approval prior to Contractor travel. Upon completion of travel, the Contractor shall submit a trip report detailing the meeting/survey/briefing and activities that occurred. (CDRL A010)

2.7.4. The Contractor shall also submit a copy of the completed travel payment request, to the COR for approval prior to invoicing electronically via Wide Area Workflow (WAWF). The travel payment request shall be submitted within 60 days of completed travel.

2.7.5. The estimated number of trips and locations of travel shall be detailed at the individual TO level.

2.8. Contractor Support of Contingency Operations

2.8.1. For this contract, contingency is defined as an unknown event, terrorist attack, natural disaster or other unanticipated event that requires additional support. Deployment is defined as unplanned travel of unknown duration in support of operations or in response to events such as terrorist attacks or natural disasters that involve an operation, location, command, or duty location that is different from the normal duty location. The Government shall utilize applicable operating instructions in planning for contingency and deployed operations when Contractor support is required.

2.8.2. At contract award, there are no known contingency or deployment operation requirements; however, if a contingency or deployment situation arises, the Contractor shall support as outlined in each individual TO. The TO will outline the full requirements and any additional considerations (e.g., hardship differential, danger pay, etc.).

2.9. Conflict of Interest.

2.9.1. The Contractor shall not employ, hire, or contract with employees of the US Government or the DoD, either military or civilian, if such employment would create a conflict of interest. The Contractor shall not employ any person who is an employee of the DoD, unless such person receives prior approval, in writing, from the CO. The Contractor shall ensure that its employees receive training, with no less than annual refresher training, on how to avoid organizational conflicts of interest (OCI).

2.9.2. As identified in each individual TO, Contractor employees may be required to have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.). The Contractor shall notify the CO immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the CO to avoid or mitigate any such OCI. The Contractor’s mitigation plan (IAW Attachment 5) will be determined to be acceptable solely at the discretion of the CO, and in the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the CO may affect other remedies as necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

2.10. Installation Access and Physical Security. The Contractor shall ensure all Contractor employees authorized to perform work under this contract obtain installation access as required by USAREUR Regulation 190-16, Installation Access Control. Contractor employees and property may be subject to search and seizure upon entering and leaving Government installations and facilities. Government furnished identification shall be returned to the Government upon termination of an employee. Contractor employees shall comply with Government physical security plans in effect at Government facilities. The Contractor shall be responsible for keys (and accountable for their use) that are provided to the Contractor by the Government. Contractor employees shall not duplicate or provide keys to unauthorized personnel and shall implement procedures to prevent loss or misplacement.

2.11. Restricted Entry Requirements. The Contractor shall arrange for entry into restricted areas, base entry, vehicle passes, and other requirements in conjunction with notification of the Government security activity.

2.12. Local Area Network (LAN). All Contractor employees requiring access to the Government unclassified computer network shall have a valid National Agency Check (NAC) verified through Joint Personnel Adjudication System (JPAS). No Contractor employee will be provided access to unclassified computer network or its inherent capabilities (i.e., internet access, electronic mail, file, and print services, etc.) without a valid NAC. The Contractor shall be aware of and abide by all Government regulations concerning the authorized use of the Government’s computer network including the restriction against using the network to recruit Government personnel or advertise job openings.

2.13. Disclosure of Information. In the performance of this contract, the Contractor will have access to data and information proprietary to a Government agency or to another Government Contractor, or of such nature that its dissemination or use, other than as specified in this contract, would be illegal or otherwise adverse to the interests of the Government or others. The Contractor and its personnel shall not divulge, or release data or information developed or obtained under performance of this contract, except to authorized Government personnel or upon written approval of the CO. The Contractor and its Contractor personnel shall not use, disclose, or reproduce proprietary information bearing a restrictive legend, other than as specified in the contract.

2.13.1. Non-Disclosure Agreement (NDA). Each Contractor employee, including Contractor program management staff, shall sign an NDA (Attachment 6) which certifies that the individual has read the non-disclosure agreement, is familiar with the directives and policies governing the disclosure of sensitive information, and that the individual agrees to fully and completely observe these directives and shall not disclose such information to any unauthorized person, to include the company or affiliates under which the individual is employed, or use any information obtained for private use or gain. The Contractor shall provide the COR or Government designated representative a copy of the signed NDA within 5 workdays of the Contractor employee’s start date.

2.13.2. Disclosure of information regarding operations and services of the activity to persons not authorized to receive it, or failure to safeguard any classified information that may come to the Contractor (or any persons under the Contractor’s control) in connection with work under this contract, may subject the Contractor, Contractor’s agent, or employees to criminal liability under Title 18, Sections 793 and 798 of the United States Code. Neither the Contractor nor the Contractor’s employees shall disclose or cause to be disseminated, any information concerning the operations of the activity that could result in, or increase the likelihood of, the possibility of a breach of the activities’ security or interrupt the continuity of operations.

2.13.3. The Contractor shall not release any information (including contact lists, photographs, files, public announcements, statements, denials, or confirmations) on any part of the subject matter of this contract, or any phase of any program hereunder, without the prior written approval of the CO. Any documentation showing individuals’ names or other personal information shall be controlled and protected.

2.14. Logistical Support. The Government may provide logistical support (e.g., Relocation Costs, Overseas Education Differential) to authorized Contractor employees and their dependents to the extent that these services are available at the location where the contract is to be performed and as authorized by current applicable Air Force, Army and OCONUS theater regulations, by current applicable international agreements and arrangements, by current policies, and the local Installation Commander. Lack of availability of any logistical support shall not serve as a basis for claims by the Contractor against the Government for increased cost of contract performance. If logistical support is available, it will be identified at the TO level.

2.14.1. Further guidance on cost reimbursable relocation and DoD dependent education benefits can be found in Attachment 8, Logistical Support for Europe.

2.14.2. Germany. For Germany, a full-time employee is defined in Army in Europe Regulation 600-700. A civilian employee must meet the definition to be eligible to receive Individual Logistic Support (ILS) privileges. The full range of ILS is detailed in Chapter 2 of AER 600-700 followed by the exceptions for Contractor personnel in Chapter 9. DoD Contractor Personnel Office (DOCPER) will apply the same standard to contracted employees applying for North Atlantic Treaty Organization (NATO) SOFA status. It should be noted, however, that under the requirements of the Exchange of Notes, a contracted employee accorded NATO SOFA status must exclusively serve the US Forces. No additional employment outside the US Forces or self-employment is permitted.

2.14.3. Italy. For Italy, an authorized Contractor employee is defined as an employee who has been hired because of this contract and is employed at least 40 hours per week on this contract. Procedures must be in accordance with the Memorandum of Understanding Between the Ministry of Defense of the Republic of Italy and The Department of Defense of the United States of America Concerning Use of Installations/Infrastructure by US Forces in Italy, signed 2 February 1995. The final authority to determine whether an employee qualifies for Technical Representative status is the United States Sending State Office (USSSO). The full range of ILS is detailed in Chapter 2 of AER 600-700 followed by the exceptions for Contractor personnel in Chapter 9.

2.14.4. United Kingdom. For the United Kingdom (UK), the Office of the Special United States Liaison Officer, American Embassy London, UK has not approved this requirement as eligible for the UK Civilian Component Stamp, under the terms of the Special Memorandum of Understanding, dated 7 July 1987. Consequently, the Contractor may be responsible for payment of Contractor employee British income tax, British council tax, and import tax on privately owned vehicles. Other taxes could also pertain, as well as any relevant obligations required under UK labor law. Moreover, ILS, as available at a location, in the UK may be limited in application to United States companies, and ILS may not be afforded to a non-US national Contractor employee.

2.14.5. Other NATO countries. Any logistic support for other than NATO countries must comply with the International Agreement of the host nation.

2.14.6. Abuse of Privileges. The Contractor shall include a provision in employment agreements with employees to provide for disciplinary action, or discharge for cause, of the employee for any abuse of privileges authorized to herein. The US Government retains the right to withdraw privileges because of Contractor employee abuse at no additional cost to the US Government. This provision will in no way prohibit disciplinary action or legal prosecution by either the US Government or the host country Government. Services or privileges may be denied on an individual basis at the discretion of the Installation Commander.

2.14.7. Termination/Transfer of Employees. The Contractor shall ensure that upon termination or transfer of any employee who is granted logistic support, action is taken simultaneously with the termination of employment to ensure that said employee ceases to have access to the services granted under logistic support. The Contractor shall ensure that identification passes or other documents pertinent to or peculiar to the contract and privileges there under are turned over to the issuing office upon the termination or transfer of any employee. The Contractor shall require a written receipt of such return and shall immediately forward a copy to the CO.

2.14.7.1. The Contractor shall turn in Common Access Cards (CACs) to the issuing office and provide written/signed documentation, by the Contractor PM or equivalent, of the date CACs were returned.

2.15. Material Acquisition/Equipment Purchase

2.15.1. The Contractor shall provide all materials necessary to meet ABAD requirements, except for the Government Furnished Property (GFP) provided to the Contractor as identified in each TO. Materials or equipment required for performance of this contract may be procured under the cost reimbursable CLIN, subject to COR approval.

2.16. Support Agreements. The Contractor shall provide coordination, as requested, on any Host–Tenant Support Agreement (HTSA), Inter-Service Support Agreement (ISSA), Memorandum of Understanding (MOU), Acquisition and Cross-Servicing Agreements (ACSA), leases and local agreements. Coordination shall include contractor review, evaluation, and feedback on draft agreements.

3. PERFORMANCE REQUIREMENTS

3.1. Personnel. The Contractor shall be required to perform all aspects of management, operational, and professional activities IAW the ABAD ID/IQ labor category list (Attachment 4).

3.1.1. Program Management. The Contractor shall provide personnel with qualifications as identified below and in each individual TO. Personnel shall be required to support a variety of program management duties such as, but not limited to:

3.1.1.1. Assist with the development, execution, and implementation of ABAD plans and procedures

3.1.1.2. Plan, direct, formulate, interpret, and coordinate all contract operations

3.1.1.3. Ensure recruitment, placement, retention, and utilization of personnel skillsets

3.1.1.4. Ensure experience are aligned with, and execute the responsibilities of, organizational roles as described within and on individual TOs

3.1.1.5. Provide program technical direction with respect to hardware and software definition, design, development, test, implementation, and maintenance for the specific customer site

3.1.1.6. Identify future technical requirements

3.1.1.7. Develop strategies to provide the required technical related resources in a timely manner to meet the DoD mission

3.1.1.8. Provide guidance and advice on the design, development, fielding, and maintenance of telecommunication and weapon systems

3.1.1.9. Represent the ABAD program as contractor focal point at senior level technical briefings

3.1.1.10. Identify technical personnel requirements for new program positions

3.1.1.11. Oversee the application of corporate and Government policies and procedures at all program locations

3.1.1.12. Solicit feedback from the top leaders/managers in the customer community to determine the quality of performance of this contract and takes necessary actions to correct deficiencies

3.1.2. Operations Management. Operations conducted by the Contractor on behalf of the Government may consist of employing Government-Furnished or Contractor provided/leased equipment to be determined on each individual TO. The Contractor shall provide the Government with the option to purchase any leased equipment as determined at the TO level. Purchase options for leased equipment shall include the option to purchase leased equipment and the equipment to run the lease equipment at any time. Purchase options shall be defined at the TO level. Personnel shall be required to support a variety of operations duties such as, but not limited to:

3.1.2.1. Assist with identifying, preparing, planning, activating, operating, (commonly referred to as pre-deployment, deployed, post-deployment, and re-deployment site support) base defense operational sites.

3.1.2.2. Aid in training support initiatives as requested by the Government in relation to ABAD initiatives. This includes routine US military training and exercises and bilateral and multilateral exercises and training involving NATO allies and partners. Training shall provide customers with operational training in platforms, platform systems, and other capabilities in various simulated training environments.

3.1.3. Frequency clearance. Frequency clearance is required to conduct operations and training activities. Approvals shall be requested from the USAFE spectrum management at least 90 days prior to activity. The Contractor shall designate a primary and alternate frequency authorization/clearance monitor as part of (CDRL A006). The frequency monitor shall coordinate with the host base spectrum management office to request and maintain temporary and permanent authorizations of the ground frequencies necessary to operate Radio Frequency (RF) radiating devices assigned under the contract. The frequency monitor shall as a minimum:

3.1.3.1. Maintain and update at least monthly a current radio frequency authorization listing to include additions, deletions, and modifications of frequency assignments for all US systems.

3.1.3.2. Retain a copy of all licenses and/or documents identifying cleared or denied frequencies.

3.1.3.3. Submit temporary, new, and reoccurring frequency clearance requests in support of all operations.

3.1.3.4. Track frequency clearance requests with documented follow-ups to occur every 30 days after submission until request is either approved or denied.

3.1.3.5. Notify the host base spectrum manager in writing at least six months prior to any frequency expiration.

3.1.3.6. Provide the above data upon request by the Government.

3.1.4. Maintenance. The Contractor shall coordinate and complete the maintenance of all infrastructure and ABAD equipment as described below to support the functional areas IAW the ABAD ID/IQ labor category list (Attachment 4). Personnel shall be required to support a variety of maintenance duties such as, but not be limited to:

3.1.4.1. Maintenance and sustainment of ABAD hardware and software architecture to include returning to system to full mission capability during any hardware or software failures. Modern techniques for provisioning COTS and custom software shall be used.

3.1.4.2. The Government requires flexibility to support changing mission requirements. The Contractor shall support all ABAD operations, as required/requested for. In addition, the Contractor shall support threat system/equipment modifications, upgrades, modernizations, additions, replacements, or removals.

3.1.4.3. The Contractor shall adapt to new techniques and technology to keep ABAD capabilities abreast of mission requirements.

3.1.4.4. Day–to-day ABAD operations and maintenance of equipment and infrastructure maintenance services.

3.1.4.5. The Contractor shall be aware of and adhere to Government mandated Information Technology (IT) security policies, and best industry security practices.

3.1.5. Maintenance requirements may differ for each TO. Certain ABAD sites may require the Contractor to fully manage and maintain the Infrastructure of the site without Government assistance while other sites may have dedicated Government support.

3.1.5.1. Infrastructure in the context of this PWS shall be defined as the necessary elements of facilities that render them suitable for use, such as electrical systems, lighting, plumbing, and heating, Ventilation and Air Conditioning (HVAC), in support of this PWS.

3.1.6. The Contractor shall develop and provide to the Government an Obsolescence Management plan to mitigate future obsolescence with the threat detection systems and counter threat systems.

(CDRL A007)

3.1.6.1. The Contractor shall notify the Government NLT 30 days in advance of a hardware or software obsolescence issue and advise the Government of the impact of obsolescence and recommend solution.

3.1.7. Department of Defense Real Property. The Contractor shall utilize and coordinate support from existing infrastructure support services provided by the Host Installation, such as the HVAC shop or the Electric shop of the 786th Civil Engineering Squadron (CES). Real Property. If required at the TO level the Contractor shall develop, implement, and maintain a program to monitor the care and upkeep of all facilities and real property. The Contractor shall ensure a safe, clean, and presentable appearance, IAW host base facility management guidance/checklists, for offices, facilities, and areas the Contractor uses under this contract.

3.1.8. TOs issued against this contract shall specify in detail associated facilities and facility characteristics, however the Government may introduce additional facilities during the life of the contract as is necessitated by mission and/or operational requirements.

3.2. ABAD Platform Systems Delivery. The Contractor shall provide a broad spectrum of ABAD platforms, platform systems, and associated services that enable ABAD operations to be conducted in, from, and through all domains (air, land, maritime, space and cyberspace). These systems shall be either procured by the Contractor on behalf of the government to become GFE, or leased from the Contractor to the Government with or without the option to purchase at the end of the lease agreement, or some other financing arrangement, as defined in the TO. The decision to either lease, procure, or both will be made at the TO level. The Government shall make the final decision as to what equipment, platforms, and platform systems shall be incorporated into ABAD. The equipment to be provided shall be specified at the TO level.

3.2.1. The objective of this task area is to provide customers with a menu of capabilities that can satisfy the mission requirement.