Attachment 1 - BMS_Sources Sought_SOW - DRAFT.pdf

STATEMENT OF WORK

1.0 Scope

The Integrated Battlespace Simulation and Test (IBST) Department, Naval Air Warfare Center (NAWCAD) – Battlespace Division, is the Naval Air Systems Command’s (NAVAIR) center of excellence for modeling and simulation of the Battlespace environment. The Battlespace Division is one of three divisions within IBST and is responsible for simulation expertise and products for naval aviation systems and the Battlespace environment within which they operate. Battlespace, distributed simulation, and live-virtual-constructive events are used throughout the acquisition lifecycle to reduce risk and improve the quality of naval aviation systems. The Battlespace Division researches, designs, develops, implements, deploys, and maintains software applications, advanced real-time simulations, real-time interfaces, and tools to support Battlespace and distributed simulations. It conducts requirements analysis, test and evaluation, and trainer/training application developments across the Department of Defense (DoD) and for Foreign Military Sales (FMS) customers. The principal Battlespace simulation product developed and maintained by the Battlespace Division is the Next Generation Threat System (NGTS). NGTS is a synthetic environment generator used to support training, testing, analysis, and research and development. NGTS models threat and friendly aircraft, ground and surface platforms, and their corresponding weapons and subsystems.

NGTS is currently installed in multiple DoD training systems, distributed exercise centers, and international military training environments. Other distributed simulation products include the Architecture Management Integration Environment (AMIE) and the Joint Integrated Mission Model (JIMM). Support is also provided for standard protocols enabling battlespace simulation that include Distributed Interactive Simulation (DIS), High Level Architecture (HLA), and the Test and Training Enabling Architecture (TENA), and the Joint Simulation Environment (JSE).

The scope for this contract is for research, design, development, and associated engineering in support of Battlespace simulation and distributed simulation requirements. Support to be provided includes the research, development, and maintenance of Battlespace simulation tools, application of battlespace simulation tools to specific customer requirements, research and development of warfare scenarios, development and integration of Battlespace entity models and behaviors, and support for delivered Battlespace products. In each of the above task areas, there shall be Special Compartmentalized Information (SCI) requirements, but none of the deliverables shall contain SCI.

This contract is a single award indefinite delivery/indefinite quantity contract. Specific requirements will be derived from the scope of this SOW and documented through individual Task Orders (TO) or Delivery Orders. Individual Task Orders will be issued as non-performance based Level of Effort Cost Plus Fixed Fee. Delivery Orders will be issued as completion based Cost Plus Fixed Fee or Firm Fixed Price.

2.0 Applicable Documents

The Contractor shall conform to applicable Department of Defense (DoD), Department of the Navy (DoN), and IBST procedures and standards in the performance of this contract. The Contractor shall comply with the most current version of all applicable security standards and procedures.

2.1 Department of Defense Specifications

2.1.1 DoD 5220.22-M National Industrial Security Program Operating Manual, (NISPOM) 28 Feb

2.1.2 SECNAVINST 5510.36B DoN Information Security Program, 12 Jul 2019

2.1.3 DoDI 5200.48 Controlled Unclassified Information (CUI), 06 Mar 2020

2.1.4 DoDM 5400.07 DoD Freedom of Information Program, Chapter 3, 25 Jan 2017

2.1.5 DoDI 5230.24 Distribution Statements on Technical Documents, Change 3, 15 Oct 2018

2.1.6 SECNAV M-5510.30C DoN Personnel Security Program, 24 Jan 2020

2.1.7 OPNAV 3440.17A Navy Installation Emergency Management Program, 1 Aug 2014

2.1.8 OPNAV 5239/14 System Authorization Access Request Navy (SAAR-N), Sep 2011

2.1.9 DoDI 1035.01 Telework Policy, 4 Apr 2012

2.2 Department of Defense Standards

2.2.1 OPNAVINST 5239.1D US Navy Cybersecurity Program

2.2.2 SECNAVINST

5510.36B

DoN Information Security Program (ISP)

2.2.3 DoDI 5220.22 National Industrial Security Program (NISP), Change 2, 4 Sep 2020

2.2.4 NASPAXRIVERINST

5510.15R

Regulations Governing Admission to the Naval Air Station Patuxent River, Navy Outlying Field Webster, and Navy Recreation Center Solomon’s, Maryland, 18 Aug 2018

2.2.5 2.2.5

2.2.6 2.2.6

DoDI 8520.2

DoDI 8582.01

Public Key Infrastructure (PKI) and Public Key (PK), 24 May 2011

Security of Non-DoD Information Systems Processing Unclassified Son- Public DoD Information

2.3 Other Procedures, Standards, and Regulations

2.3.1 NIST SP 800-171 Special Publication: Protecting Controlled Unclassified Information in

Nonfederal Systems and Organizations

3.0 Requirements

3.1 General Requirements

3.1.1 Compatibility

The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government Information Technology (IT) environment through the security classification of Collateral SECRET.

The current operating environment required for this contract includes:

Microsoft Windows (latest version) Microsoft Project 2016 Microsoft Office Professional Plus 2016 Adobe Acrobat XI (reader) Internet access

Contractor owned computers for Software Developers may also require:

Visual Studio 2015 Git Repository Swift Source Tree Dynamic Object Oriented Requirements System (DOORS)

The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall maintain state of the art anti-virus software and ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and Local Area Network (LAN) communications with the IBST Department, Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the IBST Department, during working hours whether at Contractor work site or on travel.

3.1.2 Work Location, Facilities, and Telework.

3.1.2.1 Work Location: Approximately 20% of the work will be performed at Government site at Patuxent River, MD, 80% will be performed at the Contractor site(s) as defined in Section 3.1.2.2 for work at the SECRET or UNCLASSIFIED level. The Government site is in Patuxent River, Maryland. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks. Exact definition of tasking locations between Government site, contractor facilities inclusive of subcontractors and telework will be mutually agreed to at the task order level.

3.1.2.2 Contractor Facility Requirements/Meeting Support:

The Contractor shall provide at least one facility within the daily commuting distance of NAS Patuxent River that includes a GENSER Secret level laboratory space with at least 3000 ft2 of space and a Government or Contractor owned Secret level network with a minimum of 30 work-stations. A listing of Government Furnished Property to be made available to the Contractor at contractor facilities can be found in the Wide-Area Workflow GFP Module. The Government shall provide Unclassified and Classified Research, Development, Test, & Evaluation (RDT&E) computers and computer network connectivity for off-site contractors providing direct full time technical support that requires RDT&E network access. The contractor facility(s) shall support the prime contractor and associated sub-contractors as well as providing temporary work locations for Government personnel and other Government CSS support specific program RDT&E requirements.

In support of the tasking outlined in this SOW, the Contractor shall have the capability to host and conduct meetings at the classification levels up to the unclassified and GENSER secret level with the capacity to support a minimum of 10 persons and have contractor furnished telephone and VTC capability as well as sufficient equipment to conduct meetings with presentations including compatible software as required in Paragraph 3.1.1. This support shall be provided at the Contractor’s location.

3.1.2.3 Telework: The Contractor, upon notification to, and concurrence from, the Contracting Officer's Representative (COR) that the employees' work tasking is eligible for telework, may utilize alternate worksites/locations and telework to support continued performance of its contract in accordance with company policy. Contractor discretion is required when making alternate worksite and telework decisions based upon the nature of support provided by the employees. In the event telework is utilized, the Contractor remains responsible for performance, and compliance with any applicable cost accounting standards and contract cost principles/procedures.

3.1.3 Contract Status Reporting.

The Contractor shall provide the following documentation.

3.1.3.1 Monthly Progress, Financial Status, and Government Furnished Property Inventory Reports: The Contractor shall provide recurring reports in accordance with the Contract Data Requirement List (CDRLs A001, 2, 3, 5 and 6).

3.1.4 Work Schedule to include Compressed Work Schedule (CWS), overtime, holidays and installation closure.

3.1.4.1 Work Schedule: The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually 8.5 hour (including a 30-minute lunch break) encompassing the core hours of 0900-1500 each Monday through Friday (except on the legal holidays specified in paragraph 3.1.4.1.2). Some supported Government offices have flexibility to start as early as 0530 and end as late as 1830, Monday through Friday.

3.1.4.1.1 Compressed Work Schedule (CWS): CWS is an alternative work schedule to the traditional five 8.5 hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period of time: Eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one weekday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other.

The Contractor may allow its employees to work a CWS schedule provided the requirements of this SOW are met.

If the contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage as required by the Government to the ACOR/COR.

3.1.4.1.2 Holidays: The Government observes the Federal holidays identified on the Office of Personnel Management (OPM) website: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview. With the exception of the events in section 3.1.4.5 below, the Contractor is permitted to observe Federal holidays IAW its corporate policy.

3.1.4.1.3 Installation closure: When Federal facilities are closed by the Government, or when Federal employees are officially excused from work due to a holiday, special event, severe weather, security threat, or any other Government facility related event that prevents Federal personnel from working at the Government facility, contractor personnel assigned to work at that facility in support of such Federal employees shall follow their parent company’s policies.

While generally, contractor personnel may not perform work on-site at a Government facility without Federal personnel present, in very limited circumstances, work being performed by contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer must concur with any determination that work being performed by contractor personnel is mission essential. Mission essential services, if any, will be identified at the task order level.

3.1.4.2 Overtime: Overtime as defined in this contract refers to hours worked by a contractor employee in excess of the employee’s normal workweek. When support requirements outside of normal working hours occur, the Contractor shall ensure qualified personnel are available to support the requirements through the use of overtime.

Overtime is authorized under this contract to the extent specified in individual task orders, provided COR approval is obtained in advance of each occurrence. The COR may provide concurrence for overtime on a task, event, program, project, or general function basis. The total cost for overtime over the life of the contract cannot exceed the amount specified in clause 52.222-2 Payment for Overtime Premiums unless first approved in writing by the Chief of the Contracting Office.

3.1.5 Subcontractors and Consultants.

Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this SOW shall flow down to subcontractors providing support under this contract, as appropriate. For the purpose of this contract, all consultants are to be considered subcontractors.

3.1.6 Management of Contractor Personnel.

The Government will neither supervise contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will the Government assign tasks to, or prepare work schedules for, individual contractor employees. The Contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services.

3.1.7 The Contractor’s overall transition out strategy shall be built around maintaining the mission of the program/division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Prior to the termination or expiration of the contract, the contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The contractor shall submit a Transition Out Plan, to include the minimum elements listed below in accordance with CDRL A007.

- Work Turnover. The contractor shall provide a plan of action to effectively transfer tasked work that is in http://www.opm.gov/policy-data-oversight/pay-leave/federal-http://www.opm.gov/policy-data-oversight/pay-leave/federal-process at the expiration or termination of the contract to the successor company. Establish and maintain effective communication with the incoming contractor or Government personnel for the period of transition via weekly status meetings.

- Quality Assurance. The contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.

- Risk Mitigation Strategies. The contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

- Data/Information Transfer. The contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.

3.1.8 IBST and Battlespace Policies.

In the performance of this contract, the Contractor shall utilize all appropriate IBST and Battlespace Division Stand Operating Procedures, policies, desk guides, etc. as defined by the TPOC and/or COR at the order level.

3.1.9 Transition Out Strategy

The Contractor’s overall transition out strategy shall be built around maintaining the mission of the program/division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Prior to the termination or expiration of the contract, the contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The contractor shall submit a Transition Out Plan, to include the minimum elements listed below in accordance with CDRL A007.

- Work Turnover. The contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the contract to the successor company. Establish and maintain effective communication with the incoming contractor or Government personnel for the period of transition via weekly status meetings.

- Quality Assurance. The contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.

- Risk Mitigation Strategies. The contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

- Data/Information Transfer. The contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.

3.2 Security

3.2.1 Citizenship Requirements.

Only U.S. citizens may perform under this contract, unless waived. If the Contractor cannot find qualified U.S.

citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

a. The individual's name, date and place of birth, position title, and current citizenship.

b. A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

c. A statement of the unusual expertise possessed by the applicant.

d. A statement that access will be limited to a specific government contract (specify contract number).

e. A statement that the Contractor has obtained an export license for the information required to perform the contract.

3.2.2 Investigative Requirements.

All Contractor personnel shall maintain a security clearance eligibility commensurate with the level of classification of the work performed as noted by the DD254 in Section J throughout contract performance. Individual task orders may require additional security clearance requirements, depending on the nature of the task to be performed.

With the exception of Key Personnel as defined by Section 3.4, all personnel security clearances shall be obtained prior to performance start. Interim clearances are acceptable. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoD 5220.22, National Industrial Security Program Operating Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

The Contractor shall possess and maintain Facility Security Clearance commensurate with the contract DD Form 254, Contract Security Specification.

In accordance with the contract DD Form 254 Contract Security Specification, the Contractor shall possess and maintain a clearance commensurate with the level of classification of the work performed as noted by the DD254 in Section J. With the exception of Key Personnel, individuals requiring Top Secret clearances, as identified in the individual task order, must be able to perform at the Top Secret level within 30 days of performance start unless otherwise defined at the task order level. Additional investigative requirements apply for all personnel supporting TS/SCI tasking; reference Section 3.2.12.2.

3.2.3 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR-N).

3.2.3.1 SAAR-N: All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training in accordance with NAVAIR Clause 5252.204- 9505. New employees must submit their SAAR-N forms within thirty (30) days before their first day of work.

Instructions for processing the SAAR-N forms are available at:

https://www.cnic.navy.mil/content/dam/cnic/hq/pdfs/Homepage/Command%20and%20Staff/OPNAV_5239_14_Re v_9_2011.pdf or the most recent version. SAAR-N forms shall be submitted to the Contracting Officer’s Representative (COR), Government Technical Point of Contact (TPOC), or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Associate.

3.2.3.2 CAC/Local Badges: Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government site. The Contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to NASPAXRIV Instruction 5510.15R or the most current version of this instruction. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department issuing the credential following completion of the contract, relocation, or termination of an employee, or upon request from the Contracting Officer’s Representative. The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with all applicable security procedures and regulations for these facilities.

3.2.3.3 DD-254: The Contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the Contractor accesses shall be handled at the appropriate classification level.

Unclassified information shall be handled in accordance with the appropriate designation (Controlled Unclassified Information; Covered Defense Information). Distribution is authorized to the requiring office's organization and supported activity only. Other requests for deliverables under this contract shall be referred to the COR of this contract for approval.

3.2.4 Information Security.

If the work is performed at the Contractor’s facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with DoD 5220.22-M (NISPOM) and SECNAV M-5510.36. If the work is performed at the Government’s facility, the Contractor shall comply with the DoN Automated Data Processing (ADP) Security Program outlined in OPNAVINST 5239.1D, or the most current version of this instruction.

3.2.4.1 Marking: All information generated by the Contractor shall be properly marked. CUI including Covered Defense Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoD Instruction 5200.48, Controlled Unclassified http://www.cnic.navy.mil/content/dam/cnic/hq/pdfs/Homepage/Command%20and%20Staff/OPNAV_5239_14_Re http://www.cnic.navy.mil/content/dam/cnic/hq/pdfs/Homepage/Command%20and%20Staff/OPNAV_5239_14_Re http://www.cnic.navy.mil/content/dam/cnic/hq/pdfs/Homepage/Command%20and%20Staff/OPNAV_5239_14_Re

Information (CUI) available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF.

Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings IAW DODM 5220.22-M – National Industrial Security Program Operating Manual (NISPOM), SECNAV M-

5510.36 – Information Security Program, and program Security Classification Guidance. Any product containing Covered Defense Information shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DODI 5230.24 (Distribution Statements on Technical Documents); and have this statement displayed per DODI 5230.24, Enclosure 3.

3.2.4.2 Public Release for Classified and Unclassified Information: No information pertaining to this contract shall be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by the appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release through the IBST Department Public Affairs Office.

3.2.4.3 Loss, Compromise, and/or Electronic Spillage of Classified or Controlled Unclassified Information: All instances of loss, compromise and electronic spillage of classified or controlled unclassified information shall be reported to the COR, TPOC, and Government Security Office within 24 hours of the incident occurring.

3.2.4.4 Compliance to NIST 800-171

In accordance with DOD INSTRUCTION 8582.01 SECURITY OF NON-DOD INFORMATION SYSTEMS PROCESSING UNCLASSIFIED NONPUBLIC DOD INFORMATION, the Contractor shall implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 1) (NIST SP 800-171), or establish a System Security Plans (SSP) and Plans of Action and Milestones (POAM) that varies from NIST 800-171 only in accordance with DFARS clause 252.204- 7012(b)(2), for all covered contractor information systems affecting this contract.

The Contractor shall, at a minimum, meet the Basic Safeguarding Requirements as follows to meet the comparable security requirements of the NIST SP 800-171 as indicated.

Basic Safeguarding Requirement NIST SP 800-171 Requirement

Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems)

3.1.1

Limit information system access to the types of transactions and functions that authorized users are permitted to execute

3.1.2

Verify and control/limit connections to, and use of, external information systems

3.1.20

Control information posted or processed on publicly accessible information systems

3.1.22

Identify information system users, processes acting on behalf of users or devices

3.5.1

Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems

3.5.2

Sanitize or destroy information system media containing nonpublic DoD information before disposal or release for reuse

3.8.3

Limit physical access to organizational informational systems, equipment, and the respective operating environments to authorized individuals

3.10.1 http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF

Escort visitors and monitor visitor activity; maintain audit logs of physical access; and control and manage physical access devices

3.10.3, 3.10.4 and 3.10.5

Monitor, control, and protect organizational communications (i.e. information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems

3.13.1

Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks

3.13.5

Identify, report, and correct information and information system flaws in a timely manner

3.14.1

Provide protection from malicious code at appropriate locations within organizational information systems

3.14.2

Update malicious code protection mechanisms when new releases are available

3.14.4

Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened or executed

3.14.5

The Government may, in its sole discretion, conduct reviews at the Contractor’s site to verify compliance. The Government will conduct such reviews at least every three (3) years (measured from the date of contract award) and may conduct such reviews at any time upon thirty (30) days’ notice to the Contractor.

If the Government determines that the security controls do not adequately implement the requirements of NIST 800- 171, then the Government shall notify the Contractor of each identified deficiency. The Contractor shall correct any identified deficiencies within thirty (30) days of notification by the Government. The contracting officer may provide for a correction period longer than thirty (30) days and, in such a case, may require the Contractor to submit a plan of action and milestones (POAM) for the correction of the identified deficiencies. The Contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.

Upon the conclusion of the correction period, the Government may conduct a follow-on review at the Contractor’s facilities. The Government may continue to conduct follow-on reviews until the Government determines that the Contractor has corrected all identified deficiencies.

3.2.5 Operational Security (OPSEC).

The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. This program may include Information Assurance and Communications Security (COMSEC). The OPSEC program shall be in accordance with National Security Decision Directive (NSDD) 298, and at a minimum shall include:

1) Assignment of responsibility for OPSEC direction and implementation.

2) Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

3) Establishment of OPSEC education and awareness training.

4) Provisions for management, annual review, and evaluation of OPSEC programs.

5) Flow down of OPSEC requirements to subcontractors when applicable

While performing aboard NAVAIR or NAVAIR sites, the Contractor shall:

a. Comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts;

b. Include OPSEC as part of its ongoing security awareness program and take all required Agency training;

c. Be responsive to the Supporting OPSEC Manager on a non-interference basis;

d. Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the Requiring Office and contractor in support of the mission.

3.2.6 Anti-Terrorism Force Protection and Emergency Management.

Anti-Terrorism Force Protection and Emergency Management: The work performed on this contract is not anticipated to be Emergency Essential in accordance with OPNAVINST 3440.17A and Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans and directives. Unless otherwise authorized in accordance with section 3.1.4.1.3, Contractor personnel shall not report for work at Government facilities upon declaration of Force Protection Condition CHARLIE or in any event or emergency where Government officials direct curtailment of operations to “Mission Essential Only”. All Contractor personnel assigned to a Government facility shall complete annual Antiterrorism (Level One) and Active Shooter training.

3.2.7 Cyber Incident Response

The Contractor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the 72-hour reporting period, reference https://dibnet.dod.mil/portal/intranet/) deliver all data used in performance of the contract that the Contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact.

Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3), reference https://www.dc3.mil/Organizations/DIB-Cybersecurity/DIB-Cybersecurity-DCISE/. In delivery of the incident data, the Contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.

If the Contractor subsequently identifies any such data not previously delivered to DC3, then the Contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identification.

The contracting officer will approve or disapprove the request after coordination with DC3.

3.2.8 NCIS/Industry Monitoring

In the event of a cyber incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Naval Criminal Investigative Service (NCIS), which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, subcontractor or vendor logs that show network activity, including any additional logs the contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor and NCIS will work together to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the Contractor's information systems or information technology assets. The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the Contractor.

In all cases, the collection or provision of data and any activities associated with this statement of work shall be in accordance with federal, state, and non-US law.

3.2.9 Additional Security Requirements

http://www.dc3.mil/Organizations/DIB-Cybersecurity/DIB-Cybersecurity-DCISE/

3.2.9.1 TS/Special Compartmentalized Information: This contract includes Special Compartmentalized Information performance requirements. These requirements include access to SCI materials and information and do not include SCI deliverables. All performance at the TS/SCI will be performed at the Government site. All contractor personnel supporting SCI requirements must obtain a Top Secret clearance with a fully adjudicated investigation in accordance with Intelligence Community Directive (ICD) 704 prior to starting any SCI level work

3.3 Detailed Support Requirement

IBST provides integrated testing of aircraft systems during the acquisition’s engineering / development phases.

IBST’s simulated flight environments allow systems-of-systems to be thoroughly tested as they would during flight operations. Systems can be tested with “Hardware-In-The-Loop” (HWIL) allowing aircraft hardware or software to be fully integrated and electronically stimulated without ever leaving the ground. Any level of HWIL software or hardware ground testing can be performed through use of Live, Virtual, Constructive (LVC) modeling and simulation techniques. Models range in complexity from the simplistic to fully validated Digital Systems Models (DSM) of complex avionics systems and subsystems, including systems and circuitry for HWIL testing. The contractor shall research, analyze, develop, integrate, and maintain avionic, aerodynamic, tactical and other mission capable simulation models, databases, and tools for IBST.

3.3.1 General Requirements

Software language and tool requirements for each project shall be in accordance with the current Battlespace Division standards, or as otherwise specified in individual task orders. Standards can be provided upon request after award. Individual task orders will include more specific tasking in the SOWs.

The Contractor shall:

3.3.1.1 Event Support. Provide support to prepare for and conduct simulation-based testing and training events to include distributed Battlespace simulations and LVC exercises.

3.3.1.2 Technical Research Studies. Perform technical research and design studies to define performance, operational or user requirements, evaluate new technologies, or improve the capability, efficiency, or reliability of Battlespace Division products and activities.

3.3.1.3 Documentation. Develop and maintain engineering documentation to support the research, development, operation, accreditation, maintenance, and modification of Battlespace Division products and events. Documentation includes, but is not limited to, diagrams, schematics, concepts of operations, source code, technical manuals, test procedures, test results and reports, and user’s manuals.

3.3.1.4 Test and Training Support. Provide technical support for scheduled test, training, and demonstration events, to include system operation, trouble-shooting, event setup, and debriefing.

3.3.1.5 Technical Support. Provide on-site and off-site technical support to other organizations, including Battlespace Division customers and collaborators.

3.3.1.6 Technical Exchanges. Attend user group meetings, symposia as approved by the COR, technical meetings and exchanges, working groups, and System Engineering Technical Reviews (SETR) events to meet program objectives. Develop presentation materials to support technical reviews and meetings.

3.3.1.7 Training. Provide technical support for training on simulation technologies and methodologies, the Battlespace Division and IBST capabilities and practices, and related subjects. Tasks include the development of training manuals, preparation of classroom and facilities, curriculum development, and class instruction.

3.3.1.8 Tours. Support technical tours of Battlespace Division facilities and demonstration of Battlespace and distributed simulation products and capabilities.

3.3.1.9 Visitor Escort. Provide visitor escort support in classified Battlespace Division spaces as required when supporting contract requirements. Escorting of visitors shall be in accordance with the local facility instructions, current NAVAIR and NAWCAD instructions, and NAS Patuxent River directives.

3.3.2 Program and Project Management Support

Note: For the purpose of this work statement, “Program” is defined as the entire contract effort, managed, administered and operated by the Contractor. A “Project” is defined as an effort performed within the Program to meet specific technical and operational requirements for the Battlespace Division and its customers executed by Integrated Product Teams (IPTs) consisting of contractors, government, and military employees. The Contractor shall:

3.3.2.1 Program Management. Manage the contracted effort by providing best-value program performance within cost objectives. Ensure effective management of contracted program and project resources as well as the financial and administrative aspects of the program with respect to the contract. The Manager/Operations Manager shall serve as the primary point of contact with the COR for the contract and oversee the production of deliverables. The Manager/Operations Manager shall review and recommend the development and/or modification of program management plans, strategies, schedules and milestones. The Project Management Specialist (Deputy PM) serves under the Manager/Operations Manager (PM) to assist as needed in the direction and management of the program.

3.3.2.2 Program Support. Administer and provide financial tracking for the contracted effort. Produce monthly financial reports in accordance with contract reporting requirements (See Section 3.1.3). Analyze financial program performance to project funding issues. Coordinate with Business Financial Manager (BFM) on the allocation and expenditure of funds committed to contract. Support program and project managers with management and tracking of financial and contract administrative data.

3.3.2.3 Project Management Support. Develop, analyze, modify, and monitor the implementation of processes, standards, plans, and requirements for Battlespace Division operations and projects. Tasks include, but are not limited to:

• Reviewing, revising, analyzing, and recommending changes to project management plans and strategies.

• Ensuring project controls and applicable standards are adhered to.

• Defining, developing, tracking, managing, and reporting project requirements.

• Managing cost and schedule to ensure the timely delivery of products to the customer.

• Meeting with customers.

• Issue resolution efforts.

• Develop and update documentation/presentation materials such as view graphs, brochures, display booths and other briefing materials to support program/project objectives and business development.

• Providing support for product-user community meetings and conferences.

3.3.2.4 Physical Security Support. Physical security of the MSEA office space. Will provide security orientation and badges for new employees, track employee-seating locations, conduct IT spot checks as necessary, ensure offices are properly opened in the mornings and secure for closing in the evenings. Tasks include, but are not limited to:

• Support tracking/scheduling seat moves, preparing for seat moves

• Add arrivals and departures for facility guests

• Help with facility administrative needs

• Support planning and organizing events

• Emptying shredders

• Escorting visitors through the facility

• Submitting JIRA tickets, preparing new workspace

• Escort support for IT and Security requests

• Daily access log inspections

3.3.2.5 Requirements Tracking. Collect, track, establish traceability, communicate and report project requirements.

Collect and organize requirements using customer specifications and assist Battlespace Division IPT’s with development and tracking of derived requirements.

3.3.2.6 Scheduling/Earned Value Management (EVM). Develop and maintain project schedules and EVM data for projects based on project and customer requirements. Develop and maintain Integrated Master Schedules (IMS) with Work Breakdown Structures (WBS) and resource-loaded schedules using Microsoft Project with inputs from Project Managers and team members. Identify and communicate schedule conflicts and irregularities and work with project teams to mitigate schedule issues. Track project costs, cost estimates, and cost projections. Work with project managers to communicate schedule and cost information to customers.

3.3.3 Project Support

The Contractor shall:

3.3.3.1 Configuration Management. Maintain a Configuration Management (CM) program for documents, software, Commercial Off-The-Shelf (COTS), and Government Off-The-Shelf (GOTS) documentation in support of Battlespace Division projects and operations in accordance with established procedures. Maintain a Government owned multimedia technical data library that consists of technical documents, technical data and reports, software, and product user licenses. Tasks include:

• Tracking and reporting on the status of project documentation, change documentation (discrepancy reports, change requests, etc.), and deliverable items.

• Supporting design reviews and Configuration Control Board (CCB) meetings. Tracking action items from CCB meetings.

• Assuring approved configuration management standards and procedures are adhered to.

• Working with project IPTs to determine the schedule, content, and delivery of project base-lines and releases. Supporting the creation, verification, documentation and distribution, and tracking of data package releases.

• Verifying proper use of the approval process for the release of hardware engineering drawings and data lists to manufacturing.

• Maintaining Government-owned physical and computer data libraries. Implementing procedures to ensure the restoration of software products and digital data in the event of a system failure or disaster.

• Assisting with the definition and improvement of CM-related processes and procedures. Documenting, maintaining, and implementing project-level CM plans.

3.3.3.2 Technical Writing Support. Provide technical writing support to develop product documentation (user manuals, technical manuals, and logistics reports), project documentation (project standards, status reports, meeting minutes, and action items), test definition and results reports, and organization policy and procedure documentation.

Support includes researching, writing, editing, and proofreading deliverable logistical and project support documentation in accordance with applicable customer specifications and Battlespace Division standards.

Communicate with project team members to develop, collect, and process information required for writing assignments.

3.3.3.3 Testing Support. Develop materials for verification, validation, and acceptance of developed software and systems. Coordinate and facilitate government-run system evaluations. Monitor and report on compliance with product requirements for performance, compliance with standard testing processes and procedures, and compliance with system level hardware and software plans. Tasks include, but are not limited to:

• Analyzing, evaluating, and extrapolating system and project requirements.

• Developing, maintaining, and implementing test plans, procedures, and mission scenarios.

• Working with the project IPT and the customer(s) to refine and obtain approval of test plans.

• Supporting informal and formal SETR events and meetings.

• Generating test result reports and creating discrepancy reports to document and communicate test results and the level of system maturity.

3.3.4 Development and Engineering Support

The Contractor shall:

3.3.4.1 Avionics Modeling. Perform research, design, development, integration, and testing of simulation models of sensor systems, communications systems, identification systems, and weapons systems. Tasks include, but are not limited to:

• Research, development, test, and evaluation of mission system models for Electronic Warfare Systems, Sensor Fusion, Countermeasures Effectiveness, Software Validation, Interoperability of System/ Subsystem/Components, Workload Measurement, and Flight Test Refinement.

• Software modeling for models of remote sensing devices, such as Radar, Forward-Looking Infrared Radar, and Synthetic Aperture Radar.

• Model development, modification, and integration into a battlespace environment.

• Integrating and interfacing with third party models, systems, and servers.

• Support interfacing, stimulating, and testing aircraft avionics.

• Model testing and evaluation.

• Development of operator physical and graphical user interfaces.

3.3.4.2 Battlespace Modeling. Perform research, design, development, modification, testing, and operation of

Battlespace simulation modeling, including Battlespace entity models, environments, and software. Tasks include, but are not limited to:

• Performing research, developing, interfacing, and operating warfare simulation environments.

• Developing Battlespace simulation entity and environment models through independent research and analysis of data from sources such as the Electronic Warfare Integrated Reprogramming Database

(EWIRDB).

• Developing Battlespace simulation operation and visualization graphical user interfaces.

• Designing, using, and maintaining simulation database development and manipulation tools.

• Supporting and operating multi-site mission level simulation exercises.

• Developing and maintaining simulation generation processes that permit user scenario development.

• Testing, analysis, evaluation, and reporting on Battlespace simulation software, models, and test events.

3.3.4.3 Simulation Systems Software Development. Perform design, development, modification, integration, interfacing, testing, operation, and maintenance of simulation systems. Tasks include, but are not limited to:

• Virtual environmental database modeling, to include the construction and maintenance of complex virtual environments in multi-spectral display formats. These virtual environments shall be correlated with other complex software systems for the purpose of distributed missions and exercises of a similar nature.

• Interfacing to simulation hardware systems including image generators, visual display systems, aural cueing systems, shared memory systems, operator stations, and networking equipment.

• Developing software to interface, operate, monitor, and test simulation and stimulation systems, such as simulation operator software, control executives, and runtime tools.

• Developing software and interfaces for recording, playback, presentation, and post-execution analysis.

• Developing interfaces and tools to support distributed simulations using DIS, HLA, TENA, and Battlespace modeling.

• Database development and…