N00421-18-R-0045-0001.docx

N0042118R0045

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 21-Sep-2018 03:00 PM to 04-Dec-2018 03:00 PM.

The solicitation issue date has changed from 19-Oct-2018 to 31-Oct-2018.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

STATEMENT OF WORK

The Surface/Aviation Interoperability Laboratory (SAIL) Research, Development, Test & Evaluation (RDT&E) Naval Air Warfare Center Aircraft Division (NAWCAD) 5.4

1.0 INTRODUCTION

This Statement of Work (SOW) defines the scope of engineering, technical, operator and logistics services in support of the Naval Air Warfare Center Aircraft Division (NAWCAD), Integrated Battlespace Simulation and Test (IBST) Department, Integrated Combat Environments (ICE) Division, Surface/Aviation Interoperability Laboratory (SAIL) Branch.

The SAIL is engaged in interoperable surface/aviation mission systems research, development, test and evaluation (RDT&E), fleet support, integration and interoperability testing. Experienced operators use actual ship and multi-mission helicopter systems in a national distributed network in support of battle group interoperability assessments.

The SAIL essentially functions as an operational U.S. Navy ship for aircraft in the Patuxent River MD area to test with and verify that the aircraft’s respective systems will be interoperable with shipboard systems before they are fielded and deployed. Historically, the SAIL has been closely linked with the SH-60B Light Airborne Multi-Purpose System (LAMPS) and MH-60R Multi-Mission Helicopter (MMH) programs. As such, SAIL maintains a considerable amount of related shipboard and airborne systems, but is now also a key test entity for numerous other aircraft including MQ-4C Triton, MQ-25 Stingray, P-8A Poseidon, EP-3E Aries, MQ-8B/C Fire Scout, F-35B/C Lightning II, F/A-18E/F Super Hornet, EA-18G Growler, E-2C/D Hawkeye, MV-22 Osprey, MH-60S Seahawk, UH-1Y Venom, and AH-1Z Viper.

SAIL also maintains and operates Roadhawk, which encompasses actual MH-60R Seahawk avionics subsystems, packaged in a mobile tractor/trailer combination. SAIL personnel travel from coast-to-coast supporting U.S. Navy ship combat systems checks for a variety of recurring events, including: Combat System Ship Qualification Trials (CSSQTs); post-construction combat systems checkouts; and after major combat systems upgrades. In addition, Roadhawk is often used at NAVSEA laboratories to test new combat system baselines before they are fielded.

SAIL is a major player in fleet technical demonstrations and exercises including Naval Innovative Science & Engineering (NISE) experimentation, Annual Naval Technology Exercises (ANTX), Netted Sensors (NS), and Fleet Tactical Grid (FTG) experiments. An anticipated growth area is supporting Joint Capability Technology Demonstrations (JCTDs) by providing an integration environment to check performance and interoperability of component technologies. SAIL assets are frequently used during Live, Virtual, and Constructive (LVC) events involving network connections with remote NAVAIR, NAVSEA, and SPAWAR laboratories.

1.1 SCOPE

This contract will provide engineering, technical, operational, test and logistics services in support of the SAIL efforts related to Joint and Navy research and development (R&D) programs; systems integration; simulation and stimulation systems development, test planning and conduct; command, control, communications, computers, intelligence, surveillance, and reconnaissance (C4ISR) systems interoperability; and, technology demonstration programs.

Support for necessary facilities testing and laboratory equipment, installed avionics and ship combat systems maintenance is also required, which includes purchase of necessary hardware, software, services, repairs, etc. The material and equipment purchases required includes for SAIL to conduct its mission, include complex Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) and Combat Systems (CS) equipment, miscellaneous material (cabling, connections, hardware, etc.) and contracted services needed for day-to-day operation (e.g., Tech. Assistant, Repair Specialist). All material purchases are contingent on Government authorization, as the Government has final acceptance authority for all products and services.

1.1 The scope of this contract includes experienced engineering, technical, operator, analysis and logistics services in the following technology areas:

· Acoustic Warfare Systems (AWS)

· Airborne Information Processing Systems (IPS)

· Analog and Digital Communication Systems

· Automatic Identification Systems (AIS)

· Antenna Systems

· Avionics Science and Technology

· Configuration Management (CM)

· Common Data Links (CDL)

· Cross Domain Information Systems

· Cyber Warfare

· Data Handling and Display Systems

· Electro Optic (EO) and Infrared (IR) Systems

· Electronic Warfare (EW) Systems

· Ground Based Information Processing Systems

· Imagery and Video Systems

· Logistics

· Multi-Level Security Information Systems

· Navigation Systems

· Networks

· Network Centric Warfare (NCW)

· Radio Frequency (RF) Sensor Systems

· Radar Systems

· Satellite Communications

· Software Development

· Ship Information Processing Systems

· Ship Electronic Systems Science and Technology (S&T)

· Tactical Data Links (TDL)

· Tactical Data Processing Systems

· Unmanned Airborne Systems (UAS)

· Ground Station Command and Control (C2)

· Payload Command and Control (C2)

· Unmanned Airborne Vehicles (UAV)

· Unmanned Ground Vehicles (UGV)

· Unmanned Surface Vehicles (USV)

· Unmanned Undersea Vehicles (UUV)

· Wireless Communications Science and Technology

1.1.2 The services to be provided under this contract shall be performed by experienced personnel and are categorized into the following functional service areas that are further defined in section 3.3 below:

· Engineering, Systems Engineering, and Process Engineering Services

· Modeling, Simulation, Stimulation and Analysis Services

· Software Engineering, Development, Programming and Network Services

· Configuration Management Services

· Information System (IS), Information Assurance (IA) and Information Technology (IT) Services

· Interoperability, Test and Evaluation, Trials Services

· Logistics Services

· Fleet Services

· Program Services

· Administrative Services

2.0 APPLICABLE DOCUMENTS

2.1 In the performance of this contract, the most current version of the applicable documents listed below shall be used. Additional documentation (e.g., Commercial Standards, newly developed specifications) may be required in support of systems interoperability, integration or development. Unless otherwise specified, the latest revision level and date for each specification, standard, procedure, and instruction cited within this SOW, or provided in support of programs initiated during the period of performance, shall be utilized. However, nothing in this document supersedes applicable laws and regulation unless a specific exemption has been obtained.

1) Ship Processor Operational Program and Avionics Operational Program Interface Design Specification (IDS), 84-31, (Series).

2) NAST Avionics System Specifications, LAMPS MK III, SH-60B, FI-23.0.

3) MH-60R Weapon System Manual, A1-H60RA-NFM-010. (Series)

4) MH-60R Test and Evaluation Master Plan No. 189-05 (Series)

5) Waveform Specification for the Standard Common Data Link (CDL) (Series). Specification Number 7681990

6) MMH WSSA Ship/Air Interoperability Test Procedures and Data Sheets

7) Logistics Management Information, MIL-PRF-49506

8) Software Requirements Specification for LAMPS MK III Shipboard Processor Operational Program, AN/SQQ-28 (V) SDPU, NUWC, (Series)

9) Interface Design Specification for LAMPS MK III with Ship NTDS (76-49), (Series).

10) LAMPS MK III Data Link System Operability Specification (Confidential); IBM Document NO. 6953625; (Series)

11) Procurement Specification for Radio Terminal Set AN/SRQ-4 (U) Production (Confidential); IBM Document No. 62273010000H; (Series)

12) Procurement Specification for Radio Terminal Set AN/ARQ-44 (U) Production (Confidential); IBM Document No. 6226501P; (Series)

13) AN/SQQ-89 (V) Functional Baseline for ASW System Integration; NAVSEA PMS-411-SPS-001E SCN 4, (Series)

14) INSURV Instruction 13100.1D; (Series); INSURV Aircraft Trials

15) FTEGINST 5213.1 (Series); Flight Test and Engineering Report Writing Guide,

16) EKMS-1 Phase 4, (Series)

17) OPNAVINST 4790.4D Series; Ships’ Maintenance and Material Management (3-M) Manual, (Series)

18) NAVAIRINST 3960.4B, Project Test Plans for Tests of Air Vehicles, Weapons, and Installed Systems, (Series)

19) LAMPS MK III Weapon System Information Manual, A1-H60BB-NFM-010, (Series)

20) MIL-HDBK-454A, General Guidelines for Electronic Equipment, (Series)

21) NAVAIRINST 3960.2C, Test and Evaluation, (Series)

22) NAVAIRINST 4130.1C, Naval Air Systems Command Configuration Management Policy, (Series)

23) NAVAIRINST 4355.19C, Systems Engineering Technical Review Process, (Series)

24) LAMPS MK III EW Operators’ Handbook, (Series)

25) Department of Defense Directive, DODD 8500 (Series)

26) NAVSUP Instruction 4440.179A Report of Discrepancy (ROD) Manual

27) SECNAV M-5239.1 DoN Information Assurance Program; Information Assurance Manual

28) SECNAV M-5329.2 DoN Cyberspace Information and Cybersecurity Workforce Management and Qualification Manual

29) Navy IA Pub 5239-02 --Terms, Abbreviations, and Acronyms

30) CJCSI 6211.02 (series) --Defense Information System Network (DISN): Policy Responsibilities and Processes of 31 July 2003

31) CJCSI 6212.01 (series) --Interoperability and Supportability of Information Technology and National Security Systems

32) CJCSI 6250.01(series) --Satellite Communications

33) CJCSI 6215.01 (series) --Policy for Department of Defense Voice Networks

34) DoDD 8100.1--Global Information Grid (GIG) Overarching Policy

35) DoDD 8500.1--Information Assurance

36) DoDI 8500.2--Information Assurance Implementation

37) DoDI 8510.bb--DoD Information Assurance certification and Accreditation Process (DIACAP) (DRAFT)

38) DoDI M-8510.1--DoD Information Technology Security Certification and Accreditation Process (DITSCAP) Application Manual

39) DoDI 5200.40, “DoD IT Security Certification and Accreditation (C&A) Process (DITSCAP),” 30 Dec 1997

40) CNO N614/HQMC C4--Navy-Marine Corps Unclassified Trusted Network Protection (UTN-Protect) Policy, Version 1.0, 31 October 2002”

41) Program Management Air (PMA) 299 Ship Air Upgrade (SAU) 07000 Interface Design Specification

42) IBST Security Standard Operating Procedure (SOP v3.2 (July 22, 2013)

43) Clinger-Cohen Act (CCA) of 1996

44) DoDI 5000.2 – Defense Acquisition System

45) SECNAV M-5000.2C – Acquisition and Capabilities Guidebook

46) NAVTESTWINGLANTINST 3710.1

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 IT environment through the security classification of SECRET. The current operating environment required for this contract includes:

Microsoft Windows 10 Microsoft Project 2010 Microsoft Office Professional Plus 2010 Microsoft Visio 2010 Adobe Acrobat XI (reader) Internet access

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 ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with the SAIL. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the SAIL during working hours whether at Contractor work site or on travel.

3.1.2 Work Location and Facilities

3.1.2.1 Work location: Approximately one-hundred percent (100%) of work will be performed on-site at NAWCAD SAIL (Naval Air Station (NAS) Patuxent River, Building 2641) and surrounding area within the compound, as well as various travel locations as needed to support test requirements. The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this contract. 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.

3.1.3 Contract Reporting. The Contractor shall provide the following documentation.

3.1.3.1 Monthly Funds Status Reports: The Contractor shall provide a monthly funds status report in accordance with (IAW) Contract Data Requirements List (CDRL) A001.

3.1.3.2 The Contractor shall provide the following deliverables in accordance with the CDRLs specified below. Electronic submission is acceptable to the extent specified in the applicable CDRL.

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 hours (including a 30-minute lunch break), from 0730 to 1600 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 0600/0630 and end as late as 1800, Monday–Friday. Tasking may occasionally require personnel to work outside normal working hours.

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.

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 when required by the Government. Due to the criticality of their tasking, it may not be feasible for key contractor personnel to work a CWS schedule even if the remaining employees are permitted to do so.

3.1.4.1.2 Holidays: The Government observes the following holidays:

New Year’s Day, January 1 Martin Luther King’s Birthday, the third Monday in January President’s Birthday, the third Monday in February Memorial Day, the last Monday in May Independence Day, July 4 Labor Day, the first Monday in September Columbus Day, the second Monday in October Veteran’s Day, November 11 Thanksgiving Day, the fourth Thursday in November Christmas Day, December 25

With the exception of the events in section 3.1.4.1.3 below, the Contractor is permitted to observe the above Holidays in accordance with its corporate policy.

3.1.4.1.3 Installation closure: When Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, contractor personnel assigned to work at that facility performing non-mission essential work 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.

3.1.4.1.4 Overtime: Overtime is authorized under this contract, provided COR approval is obtained in advance of each occurrence. The total cost for overtime over the life of the contract, including the base and option periods, cannot exceed the amount specified in clause 52.222-2 unless first approved in writing by the Chief of the Contracting Office.

3.1.4.1.5 Telework: The Contractor may allow its employees to telework on a case by case basis depending on the nature of support provided by the Contractor’s employee. Department of Defense Instruction 1035.01 of 4 April 2012 may be used as a guide for determining situations where teleworking is feasible. The Government reserves the right to prohibit telework where the Contracting Officer determines that the requirements of the agency, including security requirements, cannot be met if telecommuting is permitted.

3.1.5 Other Direct Costs: The COR approval shall be obtained prior to the purchase of any material or travel expenses.

3.1.5.1 Travel: Travel will be allowable only when it is essential to the performance of the tasks detailed in Sections 3.3. Contractor personnel shall travel as required when necessary to provide needed tasks through off-site meetings; training; conferences; design, installation, integration, maintenance, or system test; and to support field experiments, tests, evaluations, or events. As part of this travel, contractor personnel may be required to travel within the Continental United States (CONUS), Outside the Continental United States (OCONUS), or serve onboard ships and/or aircraft for extended periods of time. Planning for, approval of and reimbursement for travel performed shall be in accordance with NAVAIR Clause 5252.232-9509 Travel Approval and Reimbursement Procedures, the Federal Acquisition Regulation (FAR), the Defense Federal Acquisition Regulation Supplement (DFARS), and applicable Department of the Navy regulations and instructions. The COR shall approve all travel performed in support of this contract prior to the commencement of the travel. Travel may include general and administrative expenses, but shall not include profit. Temporary travel to other locations in support of program tasking is occasionally required. Temporary travel locations may include: Dahlgren, VA; Washington DC; Norfolk, VA; Mayport, FL; and San Diego, CA. This list is not all inclusive, as locations may change over the life of the contract. Travel authorization request shall be prepared and submitted for COR approval 30 days in advance of the required travel date, when possible, but no less than five business days prior to travel. Upon completion of each travel, the Contractor shall submit a trip report detailing the Contractor’s contribution to the meeting/work and related that contribution to the progress of a particular task. Trip Reports shall be submitted IAW CDRL A009.

3.1.5.2 Material: Prior written approval of the COR shall be required for all purchases of materials. Any material provided by the Contractor is subject to the requirements of NAVAIR Clause 5252.242-9515 Restriction on the Direct Charging of Material, the FAR, DFARS, and applicable Department of the Navy regulations and instructions. All materials not depleted during the performance of this contract shall become Government property upon completion of this contract. The Contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Other Direct Charges may include general and administrative expenses but shall not include profit.

The costs of general purpose business expenses required for the conduct of the Contractor’s normal business operations are not an allowable direct cost in the performance of this contract. General purpose business expenses include, but are not limited to, the cost for items such as telephones and telephone charges, reproduction machines, word processing equipment, personal computers and other office equipment and office supplies.

3.1.6 Subcontractors: Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this PWS/SOW shall flow down to subcontractors providing support under this contract

3.1.7 Management of Contractor Personnel: 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. 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.8 Transition Strategy

The overall strategy shall be built around maintaining the mission of the SAIL with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Upon 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 A003.

· 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 REQUIREMENTS

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 shall 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

Classified: All contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the contract’s DD-254, Contract Security Specification. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 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.

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. New employees shall submit their SAAR forms within thirty (30) days after their first day of work. Instructions for processing the SAAR-N forms are available at: “http://www.public.navy.mil/surfor/ccsg11/Documents/CCSG11_OPNAV_5239_14SAAR_N.pdf”.

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 Command Access Cards (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 comply with IBST Security Standard Operating Procedure (SOP v3.2) (July 22, 2013), to include furnishing all requested information required to facilitate issuance of identification badges in conformance with the SOP. All CACs and identification badges issued to contractor employees shall be returned to the Government Security Department at the Government site in accordance with the IBST Security SOP v3.2 (July 22, 2013), section 3.2 following completion of the contract, relocation or termination of an employee, or upon request from the Contracting Officer’s Representative.

3.2.2.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 as “For Official Use Only”. 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 IBST Security SOP v3.2 (July 22, 2013).

3.2.4.1 Marking: All information generated by the Contractor shall be properly marked. For Official Use Only information generated and/or provided under this contract shall be marked in accordance with DoDM 5200.01. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings in accordance with DoDD 5230.24 and program Security Classification Guidance

3.2.4.2 Public Release: 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 by the NAWCAD Integrated Battlespace Simulation & Test (IBST) Department and the NAVAIR Public Affairs Office (PAO) via the COR/Contracting Officer prior to release.

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 and Government Security Office within 24 hours of the incident occurring.

3.2.5 Operations Security (OPSEC): The Contractor shall comply with activity OPSEC program instructions, guidance and contribute to organization-level OPSEC efforts. The Contractor shall include OPSEC as part of its ongoing security awareness program and take all required activity OPSEC training. The Contractor shall protect identified critical information, sensitive unclassified information and activities, which, if divulged, could further compromise classified or sensitive information or operations, or degrade the planning and execution of operations performed by the RO and contractor in support of the mission. The Contractor shall submit an OPSEC plan IAW CDRL A011.

While performing aboard NAVAIR or NAVAIR sites, the Contractor shall: (1) comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts; (2) include OPSEC as part of its ongoing security awareness program and take all required Agency training; (3) be responsive to the Supporting OPSEC Manager on a non-interference basis; and (4) protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the RO and the Contractor in support of the mission.

3.2.6 Anti-Terrorism Force Protection and Emergency Management: The work performed on this contract is not 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. 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 official’s 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 Government Transportation/Vehicles: Government transportation/vehicles (e.g., Roadhawk, Humvee, Lab truck) may be provided for contractor use when the Contractor is required to deliver materials to support core aspects of their work. When operating Government vehicles, the Contractor shall ensure the following:

a. Possession of a current and valid operator's license (i.e., Roadhawk requires a CDL) for all vehicles;

b. Compliance with all state and federal laws pertaining to operating motor vehicles;

c. Compliance with NAWCAD command policies when operating a vehicle (i.e., no cell phone use, stopping at runway crossing, etc.);

d. Use of the most cost-effective means to fuel vehicles (i.e., NAWCAD fuel farms);

e. Operation of the vehicles in a safe manner and in accordance with the vehicle/equipment user/operator manual.

f. Operators shall comply with licensing requirements of country, state, and local Non-Tactical Vehicle (NTV) laws.

g. The COR and Contracting Officer are to be provided evidence of NTV liability insurance covering bodily injury and property damage protecting the Contractor and DoD against third-party claims arising from the ownership, maintenance or use of a NTV IAW FAR 28.307-2(c).

The Contractor shall report any known or realized accidents involving Government vehicles to the Contracting Officer's Representative (COR) and the Contracting Officer; and shall provide an accident report within 48 hours.

3.3 DETAILED REQUIREMENTS

The itemized tasks and descriptions supplied in the following paragraphs represent a high level set of support elements describing typical tasking which may be assigned to the Contractor. The functional areas to be supported under this contract are described in the sections below.

3.3.1 ENGINEERING SERVICES

This functional area consists of applying engineering disciplines and systems engineering processes to support existing Naval capabilities; technical development of new systems; development of significant alterations to existing systems; integration, interface and interoperability of existing equipment or software into different applications or platforms to support the war-fighter; or evaluation of foreign or non-developmental systems, equipment and technologies. Support is required for systems and process-engineering disciplines to analyze requirements; perform logical analysis to derive solution sets; synthesize and evaluate alternative concepts; derive and propose alternative design solutions; and generate system specifications.

Specifically, the Contractor shall provide systems engineering, engineering and process engineering services as delineated below:

(a) Provide engineering services in the design, development, procurement, production, and support of SAIL products and programs. Engineering services shall include Avionics and Ship Mission Systems Integration, Mechanical, Radio Frequency (RF), Antenna, Transmitter and Receiver Design, Digital and Analog Communications, Network design, software design, and other shipboard and/or aircraft system integration. The Contractor shall have in place and deliver a formal brief of the Systems Engineering process to be utilized IAW CDRL A005.

(b) Investigate emerging technologies to identify concepts, system configuration, and architecture and applicability to modular open system architectures. The Contractor shall conduct trade-off studies to assess and recommend technology alternatives and risks, including life cycle costing and report results IAW CDRL A005.

(c) Maintain all avionics, ship and commercial electronic equipment required for SAIL site operation and collection of performance data relative to the systems under test. Maintenance services shall include both routine and preventative maintenance in accordance with accepted Navy Planned Maintenance System (PMS) procedures. Personnel assigned SAIL maintenance shall be onsite full time and available as required to support scheduled events. The Contractor shall perform all required corrective maintenance, including system isolation, troubleshooting, and repair or replacement of failed components. The Contractor shall troubleshoot equipment, isolate faults, initiate appropriate requests through designated Government sources to obtain their repair, and repair the SAIL systems. Standard Navy procedures shall be used for reporting SAIL systems status, failures, and corrective actions. SAIL system status reports shall be provided IAW CDRL A002.

(d) Maintain a standard Preventative Maintenance System (PMS) file containing the current Maintenance Index Pages (MIP) and Maintenance Requirement Cards (MRC). The Contractor shall report the status of PMS on a quarterly basis IAW CDRL A002, outlining any updates or revisions. The Contractor shall immediately report failures using the standard Maintenance and Material Management (3M) system 4790-2K failure report, for Government submission into the 3M system IAW CDRL A005.

(e) Provide installation engineering and fabrication planning necessary to configure SAIL with advanced, or current and future fleet equipment and systems. The Contractor’s installation planning shall accommodate any special conditions or restrictions which are imposed by the shore based nature of the SAIL and shall utilize existing simulation programs and equipment where appropriate. The Contractor shall identify all material prior to purchase to the respective Government lead to determine the most appropriate procurement process. The Contractor shall design and install equipment that meets TEMPEST requirements. The Government will provide access to common tools. Plans shall be provided IAW CDRL A005.

(f) Ensure that systems remain fully operational for the duration of complex exercises during which concurrent operation of all mission and data equipment associated with the site may be required. The Contractor shall prepare and maintain SAIL system configurations, and ensure that all equipment and systems required for each test scenario are verified and reported fully functional at least one hour prior to the scheduled event. The Contractor shall initialize all site equipment and be present during its operation. When equipment failures occur during site operation, the Contractor shall provide immediate response, notify the appropriate Government Engineer, and conduct a fault analysis. When the defective or failed component is identified, the Contractor shall determine its availability from the on-site spares inventory. If not in the inventory, the Contractor shall determine availability and cost from the Federal Stock Supply System and /or commercial sources then notify the Government of the need to order the component.

(g) Utilize the SAIL site to simulate and resolve anomalies and deficiencies associated with electronic equipment required for SAIL operation identified by sponsoring activities and/or fleet units. Report results IAW CDRL A005.

(h) Identify test criteria, develop test plans, and conduct evaluations of replacement modules and components proposed for SAIL related equipment. The Contractor shall develop and document test plans and procedures and report the evaluation results in a technical report. Test plans, procedures and reports shall be submitted upon completion for review and approval to the appropriate Government Engineer IAW CDRL A005.

(i) Plan, develop technical drawings, fabricate, and implement hardware required for test data extraction, storage, quantification, and measurement to support evaluation of software, integrated ship/air system performance, shipboard electronics systems, combat systems, avionics systems, and associated peripherals. The Contractor shall provide this service for all activities associated with the SAIL. Technical drawings shall be submitted to the appropriate Government Engineer for approval prior to fabrication IAW CDRL A006. Technical Data Packages shall be submitted to the Government IAW CDRL A004.

(j) Personnel performing critical assembly, inspection and test operations shall be certified to have the requisite skills and experience or training to satisfactorily complete the operation. The standard of workmanship on all items fabricated or assembled by the Contractor for delivery shall meet the requirements of MIL-HBK-454A.

(k) Coordinate SAIL technician, operator and engineering activities to provide maximum efficiency of SAIL operation. This shall include providing technician inputs to the operations lead for monthly reports, providing technician input data to the SAIL Operations database, coordinating site planning, providing technician backup support to operations where the technician is qualified, and providing engineering analysis by qualified technicians.

(l) Provide Mechanical Engineering design and analysis services for communications, sensor, and mission systems equipment installation. These services shall include engineering work in the following disciplines: structure finite element analysis (FEA), aerodynamic, structural design, acoustic, thermal, and electric power. Written reports of results and technical drawings shall be submitted IAW CDRLs A005 and A006. Technical Data Packages for equipment design shall be submitted IAW CDRL A004.

(m) Perform engineering studies and analysis for the purpose of generating functional and design requirements for SAIL subsystems. The system functional analysis will be used to analytically derive operator, hardware, and software function partitioning in order to develop system performance parameters and requirements. Written reports and specific requirements shall be submitted IAW CDRL A005.

(n) Provide engineering services to support the procurement of airborne, surface and ground based electronic systems. Procure necessary hardware to accomplish the installation, checkout and test of these systems to determine interoperability between airborne and surface platforms.

(o) The Contractor shall assist with the preparation or modification of the following specifications, plans, or reports as required in accordance with CDRL A004:

-System/Subsystem Specifications -Initial Capability Documents, Capability Development Documents, Capability Production Documents and Joint Capability Documents -Interface Design Specifications and Interface Control Documents -System Design Documents -System Specification Documents -Software Requirements Specifications -Interface Requirements Specifications -Interface Exchange Requirements -Software Design Description -Test Plans, Test Support Plans, Test Procedures, Test Descriptions and Test Reports -Interface Design Description -Technical Reports

3.3.2 MODELING, SIMULATION, STIMULATION AND ANALYSIS SERVICES

This functional area consists of the application of standardized, rigorous, structured methods to create and validate physical, mathematical, or otherwise logical representations of systems, entities, phenomena, or processes. This area involves the use of models (including emulators, prototypes, simulators and stimulators) either statically or dynamically, to develop data as a basis for making managerial, technical, strategic, or tactical decisions.

Specifically, the Contractor shall provide modeling, simulation, stimulation, and analysis services as delineated below:

(a) Design, fabricate, install, test, and maintain computer devices and software applications required for the collection and interpretation of systems, evaluation of system and subsystem performance, and modification of weapon and control systems. This shall include the support of modeling and simulation, training and fleet support interconnectivity protocols such as Distributed Interactive Simulation (DIS and High-Level Architecture (HLA). Procure materials necessary to support the advancement of modeling and simulation technologies. These materials include the parts, equipment, hardware and information technology resources including equipment and software. The majority of computer devices and software fabricated or procured shall be microprocessor based and shall integrate with existing and proposed NAWCAD assets. Supporting documentation shall be provided IAW CDRL A005.

(b) Participate in design reviews for these developments, by providing and discussing system descriptions and documentation, functional and block diagrams, source code and operating and maintenance procedures. Minutes of presentations obtained from design reviews shall be provided IAW CDRL A009.

3.3.3 SOFTWARE ENGINEERING, DEVELOPMENT, PROGRAMMING AND NETWORK SERVICES

This functional area consists of applying the engineering and scientific disciplines to perform technical analysis of, technically support development of, or selection of hardware and computer software, or modification to existing hardware and software for systems, test facilities, or training facilities. This also consists of software engineering efforts and programming required to implement software in systems, sub-systems, and components utilizing computer, electronics, and software. Planning, designing, coding, testing, integrating, supporting, and delivering algorithms, software (source code and executables), computer programs are the inherent activities of this functional area. Commercial Off-The-Shelf (COTS) solutions and product modifications (e.g., software tools, licensing, and associated hardware) which are incidental to the overall support service efforts are considered with the scope of this functional area. Generally, the software development processes used for software development under this contract shall be, as a minimum, assessed at Software Engineering Institute (SEI) Capability Maturity Model Integration (CMMI) Level (3) or equivalent.

Specifically, the Contractor shall provide software engineering, development, programming and network services as delineated below:

(a) Provide engineering design services to develop and maintain classified, unclassified, cross domain, and multi-level security network structures for applications based on Modular Open Systems Architectures in accordance with all applicable DoD security guidelines. This includes engineering for mixed operating system environments, and integration of GOTS/COTS targeting, sensor, data fusion, and communication systems. Design results will be reported IAW CDRL A005.

(b) Develop software products that will run on designated computers. Services include analysis, design planning, designing, coding, testing, integrating, debugging and delivering algorithms, software source code and executables. Acceptance of the software will be based on successful testing at the Contractor’s or Government’s test facility. These acceptance tests will be conducted according to contractor generated functional, interface, and system level test procedures. Prior to the delivery of software to the Government, the Contractor shall conduct functional and interface tests with other platform software products as required. The procedures and test results shall be approved by the Government. All rights, related to software and technical data rights, will be governed by the clauses incorporated into this contract. Software products will be delivered IAW CDRL A008.

(c) Manage configuration and quality assurance of all the software and documentation generated during development of SAIL software products. Following acceptance of SAIL software products, the Contractor will provide all the source code files, data rights, build procedures, test results and procedures as well as a list of all standard and off-the-shelf tool sets necessary to rebuild the executable software products for submission into the SAIL configuration management system. In addition, the Contractor will provide the executable software that was used during acceptance tests so that duplicate copies can be made for Fleet release. Delivery will be IAW CDRL A008.

3.3.4 CONFIGURATION MANAGEMENT SERVICES

This functional area consists of applying engineering and analytical disciplines to identify, document and verify the functional performance, and physical characteristics of systems, to control changes and non-conformance, and to track actual configurations of systems and platforms.

Specifically, the Contractor shall provide configuration management (CM) services as delineated below:

(a) Develop and maintain CM plans and related planning documents. Efforts shall include the identification of problem areas; generation of plans for problem resolution; the derivation, evaluation and presentation of potential solutions; and recommendations for the generation of necessary policies, briefs, plans, instruction and operating procedures to effect the selected solution. Areas of review, study and program resolution encompassing the entire system life cycle shall include but not be limited to: system change control; planning for modernization; integration of engineering and logistics configuration baselines and documentation; baseline control of equipment; and control of conjunctive equipment/computer program; firmware changes in an operating environment. Provide reports IAW CDRL A005.

(b) Review, analyze and update CM business processes to identify areas for potential improvements and provide recommendations for process changes to include an assessment of the impact on existing business rules, processes and resources. Provide recommendations IAW CDRL A005.

(c) Provide Configuration Item (CI) management, including participation in Configuration Management Working Groups, Configuration Control Boards, and maintaining a database of all Configuration Items. Perform technical liaison with Government, industry, and other contractor personnel to ensure issues are resolved.

(d) Attend technical reviews, change review meetings, working groups, briefings and conferences for the purpose of providing technical support relative to configuration data and status. Provide details of meetings IAW CDRL A009.

(e) Participate in Physical Configuration Audits (PCA) and Functional Configuration Audits (FCA) as necessary to support system upgrades and modernization programs. Provide results of PCA & FCA meetings IAW CDRL A009.

(f) Maintain technical library and ensure currency of documents by logging receipts, transmittals and on-site library content. Maintain file of receipt/transmittal records, documentation records, problem reports and change documents.

(g) Prepare change documents (Engineering Change Proposals (ECP), Program Trouble Reports (PTR), and others as required, for submittal to review boards, and coordinate follow-up investigations on impact assessments. Maintain and/or monitor the status of these documents.

(h) Conduct physical and functional configuration audits of locally maintained media (Tapes, Removable Interchangeable Media Modules (RIMM), Compact Disks, Optical Disks, etc.) semiannually.

(i) Develop maintain and update laboratory configuration diagrams (CDRL A006), as well as Standard Operating Procedures (SOP), quality assurance plans and emergency action plans (CDRL A005) as required.

(j) Maintain a master index of deficiencies on site, organized by project in soft copy form. Index will be available to the Government as required.

(k) Maintain and modify a computer relational database tracking system on site to capture project/program requirements, deficiencies and status information. The database will be available to the Government as required.

3.3.5 INFORMATION SYSTEM (IS), INFORMATION ASSURANCE (IA) AND…