04. Attch. 1- PWS.docx

PERFORMANCE WORK STATEMENT (PWS)

FOR

B61-12 TAIL KIT ASSEMBLY (TKA)

SURVEILLANCE AND SUSTAINMENT SUPPORT

(BTS3)

NUCLEAR WEAPONS INTEGRATION DIVISION

FA9422-21-D-6003

30 September 2020

1.0 INTRODUCTION: The Air Force Nuclear Weapons Center (AFNWC), Nuclear Weapons Systems Integration Division (NDS) is responsible for providing continuous support that maintains warfighter capability in the employment of gravity nuclear weapon systems, including the B61 nuclear weapons and all variants. Moreover, AFNWC/NDS is responsible for coordination of integration, surveillance, sustainment, and logistics efforts with USAF Major Commands (MAJCOM), aircraft delivery platforms, and National Nuclear Security Administration (NNSA) support elements associated with the gravity weapon stockpile.

1.1. MISSION: The mission of the B61-12 Life Extension Program (LEP) is to deliver an air-delivered nuclear gravity weapon that consolidates several B61 modifications (Mods 3, 4, 7 and 10) into a single Mod (B61-12) for use on USAF and allied non-US North Atlantic Treaty Organization (NATO) Dual Capable Aircraft (DCA).

The Air Force Nuclear Weapons Center, Air Delivered Capabilities Directorate (AFNWC/ND), in partnership with the National Nuclear Security Administration (NNSA), jointly develops, procures, deploys, sustains and evaluates (performs surveillance on) stockpile health and reliability of the B61-12 All-Up Round (AUR).

1.1.1. Air Delivered Capabilities (ND - Kirtland AFB): The Air Delivered Capabilities Directorate is responsible for integrating nuclear weapon/weapon system requirements and resources to deliver nuclear bomb and cruise missile capabilities and deterrence options for the nation. AFNWC/ND ensures safe, secure, and effective nuclear delivery systems, support equipment and infrastructure.

1.1.2. Air Delivered Capabilities, Nuclear Systems Integration Division (NDS - Kirtland AFB): The Air Delivered Capabilities, Nuclear Systems Integration Division is the primary technical and programmatic office for the coordination of air-delivered nuclear weapon-related activities between the Air Force (AF) and the National Nuclear Security Administration-Department of Energy (NNSA-DOE). In addition to being responsible for the sustainment of current AF air-delivered nuclear weapons, they are also responsible for leading life extension programs (LEPs) for the full spectrum of weapons under their purview. LEPs generally follow the 6.X process for nuclear weapon refurbishment but may also be subject to the rules of the DOD 5000 series acquisitions guidelines for some specific programs.

1.2. BACKGROUND: The TKA is a subassembly of the B61-12 AUR, and is mechanically and electrically connected to the nuclear Bomb Assembly (BA). The TKA provides the B61-12 AUR with a guidance capability (System 2), while retaining the legacy ballistic flight capability (System 1).

The “analog” System 1 mode of the B61-12 TKA remains unpowered during which the AUR follows an uncontrolled ballistic trajectory to the target, while the “digital” System 2 mode maintains electrical power which actuate fins post-release, steering the AUR using controlled fin movements. The B61-12 TKA provides the US and select NATO allies with multiple courses of action, raises perceived adversarial risk, and imposes the potential of unacceptable costs for a contemplated course of action to an adversary.

1.3. SCOPE OF WORK: The contractor shall provide the government with engineering services and technical expertise as needed across various disciplines for B61-12 TKA support. The required services and supplies specifically delineated in this Performance Work Statement (PWS) will meet the individual requirement needs for corresponding task/delivery orders. The contractor shall provide, but not be limited to, the following: (1) Flight Test Support Service; (2) Laboratory Test Support Services; (3) TKA Variant Production and Delivery; (4) TKA Variant and Equipment Maintenance and Repair Services; (5) Training and Training Material Services; (6) Sustainment Engineering Services; (7) Software Engineering Services; (8) Integrated Product Support (IPS) Services; (9) Program Management Support Services; (10) Cyber Security Support Services; and (11) NATO/Foreign Military Sales (FMS) Support Services and Supplies. Overview of the performance requirements for the required services is in Section 3.0 of this PWS.

2.0 General Requirements: This section describes the general requirements for this effort. The following sub-sections provide details of various considerations on this effort.

2.1. Non-Personal Services: The contractor shall provide the government with professional, non-personal services (as defined in FAR 37.101) during the execution of all tasks described in the individual task orders. 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 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 notify the Procuring Contracting Officer (PCO) immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions relative to programs supported by the Contractor shall be the sole responsibility of the Government.

2.2. Business Relations: The contractor shall successfully integrate and coordinate all activity needed to execute the requirement. The contractor shall manage the timeliness, completeness, and quality of problem identification. The contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors. The contractor shall seek to ensure customer satisfaction, as well as professional and ethical behavior of all contractor personnel.

2.3. Contract Administration and Management.

2.3.1. Contract Administration: Contractor shall establish processes and assign appropriate resources to effectively administer the requirement and shall respond to government requests for contractual actions in a timely fashion. Duties include, but are not limited to: responding to government requests for contractual actions in a timely fashion; having a single point of contact between the government and contractor personnel assigned to support contracts or task orders; and assigning work effort and maintaining proper and accurate time keeping records of personnel assigned to work on the requirement.

2.3.2. Contract Management: Contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. Contractor must maintain continuity between the support operations at customer locations and the contractor's corporate/business offices.

2.4 Contractor Personnel, Disciplines, and Specialties: The contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience. The Contractor shall determine the number of personnel and shall ensure they assign personnel with the appropriate skill sets to accomplish the requirements in each task order.

2.5 Key and Non-Key Personnel. The contractor shall ensure that all key/non-key personnel are kept current in the latest training and technology certifications to maintain and advance the expertise and experience outlined in this PWS. All assigned employees shall be US citizens; no foreign participation is authorized.

2.5.1 Key Personnel: The Contractor shall ensure key personnel are qualified to complete all requirements detailed in this and all Task Order PWS’. The Contractor shall notify the Contracting Officer, in writing, prior to the departure of any individual assigned to a key personnel position and shall provide their proposed replacement approach. The Contractor shall minimize vacancy of Key Personnel and provide to the Government a status update via email every two weeks until position is filled. Contract will not allow for positions to be vacant for more than 3 months.

2.5.1.1 B61-12 TKA Chief Engineer: In support of the AFNWC functions outlined in this PWS, the contractor shall, at a minimum, provide a personnel staffing level (B61-12 TKA Chief Engineer) for management of activities under this sustaining contract to include, but not limited to, task planning, scheduling, tracking, monthly reporting progress/status, and financial reports review.

2.5.1.2 Program Manager: In support of the AFNWC functions outlined in this PWS, the contractor shall, at a minimum, provide a Core Program Manager with project manager experience, including experience in personnel supervisory and/or personnel resource allocation experience and/or contract management.

2.5.2 Non-Key Personnel: The contractor shall ensure that non-key personnel have adequate education and experience to complete the requirements detailed in the PWS. Requirement areas include design, application of statistical methods, problem-solving skills, and technical writing. All of the following knowledge, skills, attributes or experience requirements shall be met by "Non-Key Personnel:

a. Convey information in a clear and concise manner via verbal presentations, producing written products, or otherwise informing senior stakeholders at the senior executive level.

b. Prior experience working on cross-functional teams in a fast-paced and dynamic matrix management environment.

c. Experience with the Microsoft Office product suite, and the ability to learn new production and statistical software.

d. Ability to understand a wide variety of advanced technical information, acquisition and procurement processes, and systems integration concepts.

e. Demonstrate at least basic skills to conduct data analysis, and present data in graphic, tabular, and narrative forms.

2.6 Subcontract Management: The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The prime contractor will manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations. Any potential concerns of subcontractor OCI will be brought to the attention of the CO immediately. At the direction of the CO, a subcontractor mitigation plan may be required. FAR 52.244-2(d) specifies what types of subcontracts require CO consent prior to placement.

2.7 Location, Hours of Work, Federal Holidays, and Emergency Situations: Contractor shall provide for alternate work options according to their corporate policy regarding Government office closures, during designated Government non-work days or other periods where Government offices are closed due to weather, security conditions, Installation Commanders Directive, or other shelter in place scenarios.

2.7.1 Location: The majority of the performance of this PWS will take place at the contractor’s facilities. However, the contractor personnel may be required to perform on government installations and select overseas locations. Contractor work locations are listed in Table 2 and in individual task orders.

2.7.2 Hours of Work. Accomplishment of the results contained in this PWS requires work at various contractor, subcontractor, and Government facilities (mainly in the continental United States). Normal workdays are Monday through Friday except US Federal Holidays. Normal hours of work are from 0700 to 1700 daily. Contractor's staff typically work eight (8) hours per day, 40 hours per week. All employees are expected to be available during normal hours. Contractor work hours should not exceed 40 hours per week without express written consent of the CO. This does not preclude the contractor from performing at other times or days when reasonably necessary to accomplish the objectives described herein and where specified in individual task orders.

2.7.3 Federal Holidays: Contractor shall not have staff present at the government installation facilities on federal holidays, unless otherwise authorized. The federal holidays observed are as follows: New Year’s Day, Birthday of Martin Luther King, Jr., President's Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving Day, and Christmas Day. On occasion, the President has been known to declare a federal holiday on a day that is not recognized in this PWS. If such an occasion arises, the contractor shall provide alternate work options for employees according to their corporate policy regarding government office closures. Federal Holiday dates are given in Table1.

Table 1 Federal Holidays

2.7.4 Emergency Situations: Under circumstances where work is required at a government facility in support of individual Task Orders, contractor shall provide alternate work sites for personnel during local emergency situations when a government facility has declared an emergency and has stated personnel should not report to or should leave the facility during a workday. Contractor shall follow guidance of the installation containing their place of performance to determine reporting schedules due to a facility closure, inclement weather, or shelter-in-place scenarios.

2.8 Travel: Travel to other government facilities or other contractor facilities may be required and will be specified in each task order. All travel requirements (including plans, agenda, itinerary, and dates) will be approved (via e-mail) by the Task Order Program Manager and is on a strictly cost reimbursable basis, no fee is authorized. Costs for travel shall be billed in accordance with the regulatory requirements in the Public Law 99-234 and FAR 31.205-46 Travel Costs. Contractor access to base installations shall occur in accordance with clause 5352.242-9000, Contractor Access to Air Force Installations found in Section I, Contract Clauses.

2.8.1 The contractor shall be required to travel to support the task requirements, such as attendance at meetings, working group meetings, and test execution. The number of contractor personnel authorized to travel will be approved by this COR or PM.

2.8.2 The contractor shall be able to travel to the following locations as shown in Table 2, in support of this PWS:

Table 2 Travel Locations

Other locations as requested by the USAF

2.8.3 The contractor shall be able to support travel requirements as specified in each PWS Task Order. The contractor shall use only the minimum number of travelers and rental cars needed to accomplish the task(s). Travel shall be scheduled during normal duty hours whenever possible. Airfare will be reimbursed for actual common carrier fares which are obtained by the most reasonable and economical means.

2.8.4 The government will identify the need for a Trip Report (if required) when the request for travel is submitted. The contractor shall keep a summary of all long-distance travel, to include, at a minimum, the name of the employee, location of travel, duration of trip, and POC at travel location (Table 6, CDRL A003).

2.8.5 The contractor may invoice monthly on the basis of cost incurred for travel in support this PWS CLIN(s). The invoice shall include the period of performance covered by the invoice and the CLIN number. In addition, the contractor shall provide the following detailed information for each invoice submitted, as applicable. Separate worksheets, in MS Excel format, shall be submitted for travel with separate columns for the following:

2.8.5.1 Project Total Travel: This will identify all current and past travel on the project and their total Project costs billed. The listing shall include separate columns and totals for the following information concerning the current invoice period and the project to date:

Table 4 Travel Identifiers

· Current invoice period

· Names of persons traveling

· Number of travel days

· Dates of travel

· Number of days per diem charged

· Per diem rate used

· Total per diem charged

· Transportation costs

· Other charges

· Total charges

2.8.5.2 CLIN/Task Total Travel: This will identify all current and past travel on the project and their total CLIN/Task costs billed. The listing shall include separate columns and totals for the current invoice period and the project to date:

Table 4 CLIN Total Travel

· Current invoice period

· Names of persons traveling

· Number of travel days

· Dates of travel

· Number of days per diem charged

· Per diem rate used

· Total per diem charged

· Transportation costs

· Other charges

· Total charges

All cost presentations provided by the contractor shall also include Overhead Charges and General and Administrative Charges.

2.9 Environmental Requirements: The contractor shall comply with all environmental requirements imposed by the Federal Government, the Air Force, and at locations where services are being performed. Such requirements are delineated in AF Policy Directive 32-70, "Environmental Controls, and other laws and regulations”.

2.10 Invoices: Contractor shall follow invoicing instructions per Section G of the contract.

3.0 PERFORMANCE REQUIREMENTS: This contract will require classified/sensitive acquisition, product support, integration, test, surveillance, logistics and sustainment/software and cybersecurity engineering services and supplies for TKA associated elements of the AFNWC/NDS B61-12 portfolio. Specific performance services will be delineated in individual task orders. The contractor shall perform the efforts identified in Task Order PWS’ and classified addendums, as applicable. In conducting these performance requirements, the contractor shall act under the guidance and at the behest of the Government, and make technical recommendations to the Government who makes all final acceptance, selection, and procurement decisions. The contractor shall have a continuing obligation to inform the Government of known problems and issues, and make disclosure of known risks associated with the activities to be conducted under these tasks. Deliverables and recommendations shall be provided for Government review and approval and provided only for the environments and specified conditions for which they were intended and/or tested. All efforts under this task shall be conducted in accordance with established contractor quality assurance procedures. The contractor shall develop a kick-off presentation and conduct the kickoff meeting no later than 30 days after award of each Task Order (CDRL A01 and A03). Typical performance requirements anticipated to be issued through individual task orders will include, but not be limited to, the following CDRLs in Table 6.

3.1. Flight Test Support Services: The Contractor shall maintain the capability to support the B61-12 weapon, and multiple delivery platform programs, with integration and flight test activities. Flight test support will be required for ongoing B61-12 aircraft integration, nuclear compatibility certification, NucWSEP and other test missions on current and future delivery platforms. The Contractor shall provide the technical expertise to execute flight test activities. Flight test activities will include the buildup of flight test vehicles, logistical planning and execution, preflight checkouts on the TKA asset, support “Go, No-go” decisions, real-time monitor and control during test, post flight TKA asset checkouts, data download and storage, and post-test data analysis and reporting. Specific requirements will be determined by the Government and furnished via individual Task Order PWS'.

3.2. Laboratory Test Support Services: The contractor shall maintain the capability to support platform integration labs, and other labs as outlined in this PWS. System Integration Lab (SIL) test support will be required for ongoing platform Operational Flight Program (OFP) development. The contractor shall provide TAWS-4 and ELX technical expertise in the areas of operation, sanitization, Launch Acceptable Region (LAR) modeling, software, and hardware. In addition, the contractor shall facilitate software updates and uploads onto the TAWS-4s and ELX. B61-12 JILT (Joint Integrated Laboratory Test) and TKA AFCLT (Air Force Component Laboratory Test) test support will also be required during surveillance test activities. In this context, the contractor shall provide technical expertise on the functionality of the TKA, the TKA’s subcomponents, OFP, and associated TKA test equipment if JILT and/or AFCLT is contracted to another entity. The contractor shall provide technical expertise to address TKA related questions during test. Specific requirements will be determined by the Government and furnished via individual Task Order PWS.

3.2.1. If the Government determins that no other entity can effectively perform AFCLT, then the contactor shall execute AFCLT, which includes determining test location(s), procuring and maintaining test equipment, execution of test procedures and analysis of test results

3.3. TKA Variant Planning, Production and Delivery: The contractor shall assist the government with the development of a procurement plan by defining the requirements for each TKA variant. Additionally, the contractor shall identify obsolescence issues and impacts to requirements and/or schedule. The contractor shall produce (build, document, inspect, deliver) B61-12 TKA Test Variants, test equipment and trainers. The contractor shall ensure compliance with applicable product specifications. The contractor shall produce long-lead and life of type buy (LOTB) components and materiel in sufficient time to meet TKA Test Variant, test equipment and TKA trainer production and delivery schedules; support test asset, test equipment, and trainer maintenance and repair (see para. 3.4); and to mitigate obsolescence and Diminishing Manufacturing Sources and Material Shortages (DMSMS) (see para. 3.8). Specific requirements will be determined by the Government and furnished via individual Task Order PWS'.

3.4. TKA Variant and Equipment Maintenance and Repair Services: NOTE: WR TKAs, TKA trainers and SATS will not be repaired under this contract if covered under the term and condition of the B61-12 Production Contract (FA2103-19-C-0061). The contractor shall inspect, maintain and repair returned War Reserve (WR) B61-12 TKAs, TKA Trainers, TKA Test Variants, TIKs, SATS and Test Tools. The contractor shall provide the technical expertise to recommend and expedite repair and maintenance actions. The contractor shall recommend repair and maintenance schedules on flight test hardware and lab hardware. TKA maintenance and repair to include diagnostic and recalibration of the IMV TKA. The contractor shall monitor GFE production test support equipment, all B61-12 TKA test variants and test support tools items for serviceability and maintainability (see para.3.4.1) and recommend recapitalization if warranted. Repair and Maintenance Services will be documented IAW: Repair and Maintenance Work Order Form. A high level overview of the process flow of such services is detailed below. Specific requirements will be determined by the Government and furnished via individual Task Order PWS'.

3.4.1. Government sends item with Repair and Maintenance Work Order Form to Contractor

3.4.2. Contract receives item and begins diagnostics. Once diagnostics is complete, they send the report to the Government along with a plan to repair the item.

3.4.3. Government will review diagnostics report and plan of repair and determine if they want proceed. If the Government does not want to process, the Contractor will ship the item back.

3.4.4. If the Government proceeds with the repair. The Contractor will execute the repair plan, documents the process. Once complete, the Contractor will send the item back to the Government.

3.5. Training and Training Material Services: The contractor shall provide B61-12 TKA training and training materials when specified by task order. Specific requirements will be determined by the Government and furnished via individual Task Order PWS'.

3.6. Sustainment Engineering Services: The contractor shall provide the engineering services through severable and non-severable tasks to address specific systems engineering activities related to applicable AFNWC/NDS supported programs when specified by task order. Specific requirements will be determined by the Government and furnished via individual Task Order PWS'.

3.7. Software Engineering Services: The contractor shall provide technical expertise to support TKA OFP updates, as required. TKA OFP updates to include OFP software for all TKA variants. The contractor shall provide the technical expertise to support compatibility issues discovered during platform or bomb assembly software development (e.g. platform OFP). The contractor shall also support the sustainment of software needed to operate the SATS, TKA ELX, TKA trainers, and updates to the TKA Fly-Out-Model (FOM). Specific requirements will be determined by the Government and furnished via individual Task Order PWS'.

3.8. Integrated Product Support (IPS) Services: The contractor shall provide integrated product support for applicable AFNWC/NDS B61-12 programs. Integrated Product Support (IPS) services shall consist primarily of life cycle planning activities, technology roadmap development, support for diminishing manufacturing sources/vanishing vendors and parts obsolescence, TKA Variant and equipment disposition and disposal. The specific elements of IPS are as follows: product support management; supply support; packaging, handling, storage and transportation; maintenance planning and management; design interface; sustaining engineering; technical data; IT systems continuous support; facilities and infrastructure; manpower and personnel; support equipment; and training and training support. Compliance with NWRM FAR and Air Force policies is a critical area of WR B61-12 TKA IPS. Proper protection and accountability of non-NWRM test TKAs, TAWS, and other sensitive unclassified and classified B61-12 associated end items, components and software is also required. Additionally, the contractor shall establish and maintain a support function within JDRS to assist with program deficiency resolutions as needed IAW 00-35D-54. Specific requirements will be determined by the Government and furnished via individual Task Order PWS'.

3.9 Technical Program Management Support Services: The Contractor shall establish and maintain a program management office in support of all work performed under this contract. As part of the establishment of such an office, the Contractor shall identify a Core Program Manager responsible for planning, organizing, staffing, administering, integrating and oversight across multiple active task orders under this contract. Efforts include program cost, schedule, risk and technical performance management functions and reporting technical, schedule and financial management data in the Contractor’s Progress Status and Management Report (CPSMR) (Table 6, CDRL A011).

3.9.1 The contractor shall assign and identify a Program Manager for each individual task order who will plan, organize, staff, administer, and control all task order activities and to ensure cost, schedule, and technical objectives are achieved. The contractor shall attend/support task order level management meetings as deemed necessary by the government program office. The contractor shall produce all deliverables and close all action items generated during reviews, audits and/or performance assessments before the government will consider the Task Order Performance Work Statement to be fulfilled (Table 6).

3.9.2 The contractor shall be responsible for personnel and operations on multiple active task orders across the contract. The contractor shall have the ability to manage all aspects of program and program personnel including engineers, consultants, and administrative personnel. The contractor shall determine the number of personnel and shall ensure they assign personnel with the appropriate skill sets to accomplish the requirements in each task order, as well as that these skill sets are leveraged throughout the workforce to meet the contract requirements. All assigned employees shall be US citizens; no foreign participation is authorized

3.9.3 The Contractor shall provide programmatic updates, including, but not limited to, information on current delivery orders and tasks. Earned Value Management (EVM) shall be used when required by the TO and LOE hours as identified below. For TOs exceeding $20M the contractor shall have a validated Earned Value Management System (EVMS) in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 252.234-7001, DFARS 252.234-7002, and the EVMS guidelines contained in ANSI/EIA-748. Programmatic updates shall be provided as described below:

3.9.3.1 Weekly Front Office Group (FOG) telecoms (as required)

3.9.3.2 Weekly engineering telecoms (as required)

3.9.3.3 Monthly Tech Services Reviews to include all TOs.

3.9.3.4 Separate EVM charge lines shall be established internally to collect costs by major tasks under TO requirement sections (except tasks greater than $20M as subject to 3.9.1) and reviewed in contractor format during Monthly Tech Services Reviews.

3.9.3.5 Program Protection Plan (as required) (CDRL A002. Program Protection Plan)

3.10 Cyber Security Support Services: The contractor shall provide Information Assurance/Cyber Security/Information System Cybersecurity Engineering support as required to meet government requirements for the TKA, associated test variants and equipment, and platform integration. Some of the requirements pertain to annual TKA audits, annual Authorization to Operate (ATO) assessment for the TKA and SATS, a re-validation of the ATO for the TKA and SATS every 3 years, and Program Protection Plan.

3.11 NATO/Foreign Military Sales (FMS) Support Services and Supplies: NOTE: Tasks in support of individual FMS Cases will mirror select elements of paragraphs 3.1 – 3.10 and associated services and supplies, as outlined in this PWS and specific Task Orders. The Contractor shall provide support to FMS-funded flight test, laboratory test, TKA variant hardware production (including Special Defense Acquisition Fund (SDAF) funded requirements), delivery, maintenance and repair, training and training material, sustainment engineering services, software engineering services, IPS, program management and administrative support, and cyber security. Additionally, the contract shall provide support to establish TAAs and other applicable export requirements as needed.

4.0 SPECIAL REQUIREMENTS

4.1. Security: This section describes the security requirements for this effort. The following sub-sections provide details of various considerations on this effort. Task Orders (TOs) may provide more specific security requirements.

4.1.1 DD Forms 254.

Overarching security requirements and contractor access to classified information shall be as specified in the basic DD Form 254. Specific security requirements will be further identified in the DD Form 254 for each Task Order, as necessary. The Contractor shall not employ persons for work on this contract if such employee is a potential threat to the health, safety, security, and general well-being or operational mission of the installation and its population. The Contractor shall not employ any person who is a former employee of the United States Government if the employment of that person would create a conflict of interest, nor shall the Contractor employ any person who is a former employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval in accordance with the Joint Ethics Regulation. All contract personnel with access to unclassified information systems, including e-mail, shall have at a minimum a favorable National Agency Check (NAC). Contractor personnel having access to classified documents, studies, reports, and other documentation and information shall have a minimum of a SECRET clearance adjudication. Contractor personnel assigned under this PWS must hold US citizenship. Government will require the Contractor to communicate and access SIPRNET.

4.1.2 Visitor Group Security Agreement. The contractor shall sign a Contractor Visitor Group Security Agreement to protect classified information involved in performance under this contract and/or Task/Delivery Order(s). The Agreement will outline responsibilities in the following areas: contractor security supervision; standard practice procedures; access, accountability, storage, and transmission of classified material; marking requirements; security education; personnel security clearances; reports; security checks; security guidance; emergency protection; protection of government resources; DD Forms 254; periodic security reviews; and other responsibilities, as required.

4.1.3 Personnel Security Clearances: The contractor will initiate the appropriate level of security clearance background investigation to result in issuance of a Department of Defense Secret security clearance. Information gathered, developed, analyzed, and produced under this contract and/or Task/Delivery Order(s) remains the property of the U.S. and shall be protected from unauthorized or inadvertent modification, disclosure, destruction, or use. Prior to the arrival of any contractor employee to commence work under this contract and/or Task/Delivery Order(s) at any government site, the contractor must provide advance notice to the government for visitor control purposes and verification of security clearance. All Contractor personnel shall maintain their clearances throughout the life of the contract and/or Task/Delivery Order(s) and comply with security requirements per DoD 5200.1-R and Air Force Instruction (AFI) 31-401. Any exceptions to the minimum clearance requirements will be made on a case-by-case basis and agreed upon in writing by the CO. All assigned employees shall be U.S. citizens; no foreign participation is authorized. The contractor is responsible for obtaining and maintaining the requisite clearances at no additional expense to this contract. All contractor employees occupying positions requiring security access and with the need to know shall have the appropriate clearance(s) at award of the basic contract and any subsequent Task/Delivery Order(s) award.

4.1.4 Security Classification Guides: This project and the work being proposed are classified and Need-To-Know (NTK). The following Security Classification Guides (SCGs) will be followed:

a. CG-W-5, Joint DOE/DoD Nuclear Weapon Classification Policy Guide, 16 Oct 1995

b. CG-SNL/NM-B61 (Mod 12)-1, Classification Guide for the B61-12, 11 June 2014.

4.1.5 Security Awareness. The Contractor shall develop a method to establish and maintain a level of security awareness by the personnel who are assigned to this contract and/or Task/Delivery order(s) who use and maintain the system. The training shall be designed to ensure that on-site personnel are trained in the use and management of the security mechanisms, processes, and procedures required to secure the systems infrastructure.

4.1.6 Facility Clearance Requirements: Contractor shall possess, at minimum, a SECRET (S) level facility clearance. Contractor shall be capable of processing and storing data at the SECRET collateral level. Caveats including Restricted Data (RD), Formerly Restricted Data (FRD) and Critical Nuclear Weapons Design Information (CNWDI), Special Access Required (SAR), Special Access Programs (SAP), and other service programs may be required, but shall not be processed or stored at the contractor facility, unless authorized by Defense Security Service (DSS). Facility clearance requirements will be cited in each Task Order.

4.1.7 Operations Security (OPSEC): Contractor shall comply with OPSEC requirements specified in DoD 5220.22-M, “National Industrial Security Program Operating Manual (NISPOM”) and “AFNWC OPSEC Operating Instructions”. The COR and the AFNWC OPSEC Coordinator will identify for contractor the following information: organization's critical information, adversaries collection threat information as it applies to the organization's mission and the contract, OPSEC, and/or specific OPSEC measures the organization requires (as appropriate)..The contractor shall ensure OPSEC is incorporated into the appropriate area of the contract IAW DoD Directive 5205.02E, DoD Operations Security (OPSEC) Program and AFI 10-701 Air Force OPSEC program. The contractor shall flow down all OPSEC requirements to subcontractors that handle Critical Information (CI). CI is defined as specific facts about friendly intentions, capabilities, or activities needed by adversaries to plan and act effectively against friendly mission accomplishment.

4.1.7.1 OPSEC Program Plan: The Contractor shall safeguard all government critical information as identified within the OPSEC Program Plan Contractor shall update the OPSEC program plan to address how the contractor plans to protect critical and sensitive contracted information, and upon government acceptance, implement the OPSEC program plan. The OPSEC program plan will be updated and submitted on an annual basis IAW applicable government instructions.

4.1.7.2 OPSEC Training: Contractor shall ensure their employees receive OPSEC training and training materials from the AFNWC OPSEC Coordinator within 90 days of contract employee assignment to this requirement. Contractor (and subcontractor) employees working on this requirement with access to government computers and networks shall complete annual ADLS Security Administration (formerly Information Protection Training) and complete event-driven/annual training distributed by the COR.

4.1.8 Security Procedures/Information Protection. The Contractor shall take appropriate measures to ensure the protection of data to specified levels for the duration of the contract. The Contractor shall follow all appropriate security procedures regarding identification badges, entry control cards, and vehicle passes. The Government shall direct the Contractor of the necessary avenues required acquiring the appropriate identification badges, entry control cards, and vehicle passes. The Contractor shall return all issued badges and passes to the Government at the end of the contract or individual employment, whichever comes first, before final payment is made

4.1.8.1 ITAR. This effort is subject to the International Traffic in Arms Regulations (ITAR), 22 C.F.R. Parts 120-130 or the Export Administration Regulation (EAR), 15 C.F.R. Parts 730-774, which control the export of sensitive technical data. Foreign citizens designated as US Persons are not permitted to perform work under a classified award. Foreign citizens (i.e., those holding non-US Passports) will at no time be allowed to work on Air Force installations. The Contractor is required to complete annual Air Force and DoD Information Protection training to maintain government computer access.

4.2. Privacy and Privilege: Contractor employees may be exposed to data that is subject to the Privacy Act of 1974, Arms Export Control Act or the Export Administration Act of 1979, and Safety Privileged data. All contractor employees assigned to this task shall be required to take appropriate action to prevent disclosure of this information. Employees shall abide by the guidance in DoDI 6055.07 and any applicable AFNWC instruction. Completion of non-disclosure statements will be required by on-site contractor employees to ensure information that is considered sensitive, proprietary, or privileged is not compromised.

4.3 Contractor Identification in a Government Facility. All Contractor and Subcontractors (if applicable) personnel shall distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, Contractor and/or Subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors and/or Subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation.

4.4. Standards of Conduct. The Contractor shall take appropriate measures to ensure protection of data to specified levels for the duration of the contract. The Contractor shall not divulge any information regarding files, data, processing activities or functions, user IDs, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all government rules, procedures, and standards of conduct. Contractors requiring access to government Automated Information Systems (AIS) shall have background investigations and security awareness training completed after contract award, but prior to AIS access. . When the period of performance is complete or Contractor personnel leave work on this project, they will have seven (7) working days to terminate all their network user accounts and to return all access cards and base identification badges. The Contractor is required to complete annual Air Force and DoD Information Protection training to maintain government computer access.

4.5 Release or Removal of Information. Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for information shall be forwarded to the Government PM, COR and the CO who, in turn, will authorize the approval.

4.6 Contractor Compliance. The Contractor and its Subcontractors (if applicable) shall comply with Public Law 91-596 (Occupational Safety and Health Act (OSHA)) and DODD 4715.1E (Environmental, Safety, and Occupational Health (ESOH)). These requirements shall be incorporated into the contractor's safety and health program. The DoD participates in the OSHA Voluntary Protection Program (VPP). Contractor personnel performing services on a DoD installation shall participate in the local VPP. Information on the VPP is available at http://www.osha.gov/dcsp/vpp/index.html.

4.7 Computer Security. The Contractor employees are prohibited from attaching any computer hardware to the Air Force network, or running any computer software unless it has been certified and accredited according to current USAF Instructions. Any such requests for reconfiguration or addition of computer software must be approved by a USAF Authorizing Official (AO) office. Contractor employee use of computer modems, thumb drives, and external hard drives on any machine attached to the Air Force network is prohibited.

4.8 Software and Database Classifications. Databases, software and underlying source code developed, operated, or sustained under the scope of this acquisition should be kept at the Unclassified / For Official Use only (U/FOUO) classification whenever reasonably possible or when deemed required by the Government. The inputs to the model will be unclassified and the outputs may be classified as either Secret or Top Secret. Prior to inputting any data into a database, the Contractor will specify what the expected classification of the compilation of data will be. If the expected classification of the database is higher than Secret, the Government will specify where the database should reside. The databases and inputs/outputs that the software will use for given analyses and storage may be at a higher classification level, typically Secret or above.

4.9 Mishap Notification and Investigation. The Contractor and its Subcontractors (if applicable) shall promptly report pertinent facts regarding mishaps involving Government property damage or injury to Government personnel and to cooperate in any resulting safety investigation. The Contractor shall notify (via telephone) the CO, the COR, and/or other applicable members within four (4) hours of all mishaps or incidents. The Government person notified by the Contractor will in-turn notify the Safety office. Contractor notifications made after duty hours shall be reported to the appropriate installation Command Post. If requested by the CO, the COR, and/or the PM, the Contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records until released by the investigating safety office. If the Government investigates the mishap, the contractor and the subcontractors shall cooperate fully and assist the Government personnel until the investigation is completed. The Contractor shall take all reasonable steps and precautions to prevent accidents and preserve the health and safety of Contractor and Government personnel performing or in any way coming in contact with the performance of this contract. The CO may direct Air Force Occupational Safety and Health Standards and/or Health and Safety Standards, as may be required, in the performance of this contract. Any adjustments resulting from such direction shall be made in accordance with the Changes clause of this contract. Any violation of these health and safety rules and requirements, unless promptly corrected as directed by the CO, shall be grounds for termination of this contract in accordance with the Default clause of this contract.

4.10 Personnel Health Hazards. The Contractor shall identify and evaluate system safety and health hazards, define risk levels, and establish a program that manages the probability and severity of all hazards associated with contractual tasks. Safety and health hazards shall be managed consistently with mission requirements. All inherent hazards shall be identified, evaluated and either eliminated or controlled to ensure minimum risk to the environment and personnel. Records shall be kept for the life of the contract plus two years. These records shall be provided to the Government upon request.

4.10.1 System Health Hazards. The Contractor shall establish a process for the identification, elimination, and control of hazards and integrated hazards throughout the complete life cycle of systems, equipment, materials, operations, and processes before introducing them into the work environment. All hazards shall be traceable from the initial identification through its resolution and any updates, using a continuous risk management approach. The Contractor shall develop a system safety approach to include both quantitative and qualitative analytical methods, as appropriate, to assess system and subsystem hazards of critical and mission essential systems and equipment and other hazardous systems.

4.11…