DRAFT_SS_SE_Srvcs_SOW.pdf

STATEMENT OF WORK

SYSTEMS ENGINEERING SERVICES

INTRODUCTION

The Naval Air Warfare Center Aircraft Division (NAWCAD) Code AIR-4.1 is tasked to perform systems engineering, analysis, development, integration, testing, and fleet introduction and support of warfare systems into Naval Aircraft. This includes direct systems engineering support throughout the full life cycle of a weapon system from concept development to disposal, and is applied to all Naval

Aircraft (Tactical, Vertical Lift, Maritime, UAV's, Targets, and advanced weapons), Foreign Military

Sales (FMS), and support systems.

Aircraft Programs supported under this solicitation will include, but not be limited to, programs such as the Joint Strike Fighter (JSF), F/A-18, EA-6, AV-8, V-22, Navy Commercial Derivative Aircraft, Tactical Reconnaissance, Unmanned Air Systems (UAS), Aerial Targets Systems, E-2, C-130, KC-130, P-3, P-8, H-1, H-60, H-53, Scan Eagle UAS, Fire Scout UAS, Broad Area Maritime (BAMS) UAS, Shadow UAS, Joint Tactical Combat Training Systems, Night Vision Devices, Integral Cockpit

Lighting, Mission Planning, Advanced Avionics Technology Demonstration, Common Avionics, Communication, Navigation, Advanced Tactical Surveillance, Integrated Tactical Decision Aids, Weapon Engagement Rehearsal Aids (E&RA), Theater Ballistic Missile Defense, and Aircraft/Weapon

Integration, Joint Precision Approach Landing System (JPALS), Electro-Magnetic Aircraft Launch

Systems (EMALS) and other Externally Directed Programs. NAWCAD also supports Joint Service

Programs in addition to JSF, such as LH-X, Advanced Tactical Airborne Reconnaissance System, and

Operations Aircraft.

2.0 SCOPE

The Systems Engineering Department (AIR-4.1) requires systems engineering and technical efforts to be performed under this contract in the functional area of Systems Engineering Management (AIR-

4.1.1). These efforts are focused across a broad business base comprised of Integrated Program Teams

(IPT's), Externally Directed Teams (EDT's), and Enterprise Teams (ET's), which support all Naval Air

Programs.

The mission of AIR-4.1 is to apply systems engineering knowledge and skills to provide support to

Program Executive Offices (PEOs) and Program Manager, Air (PMAs) by providing assessments of

Aircraft, Weapon, and Integrated Systems’ technical performance, mission suitability, and associated acquisition risks throughout the full acquisition process and life cycle of a program. The program specific Assistant Program Managers for Systems Engineering (APMSE) are the primary tasking authorities for systems engineering support provided through this contract.

The Contractor shall support the Government by providing a multi-discipline, integrated technical baseline evaluation, engineering assessment of the program’s progress towards demonstrating and confirming completion of required developmental tasks and confidence that the technical baseline is mature enough for the next stage of development. Systems engineering support will include an overall technical assessment of cost, schedule, emerging technology, and maturity of design in support of the acquisition programs.

3.0 REQUIREMENTS

This Statement of Work (SOW) defines the overarching scope for AIR-4.1 Systems Engineering efforts. Each Task Order (TO) awarded under this contract will include a unique SOW with the detailed requirements that fit within the scope of the basic contract. The SOW will also define the appropriation type that will fund each task. SubCLINs will be established in the TO by appropriation and by customer.

The requirements under this SOW cover a broad spectrum of support to NAVAIR PEO and PMA activities. The Contractor shall provide support for integrated, capability-based warfighting assessments that will ultimately provide the analytic underpinning to support the acquisition of naval aviation systems and the Office of the Secretary of Defense (OSD) investment decisions.

The Contractor shall provide qualified personnel to be assigned to programs and/or projects under the technical direction of the Division Head. The following is a list of tasks associated with performing the systems engineering work.

3.1 CONTRACT PROJECT MANAGEMENT

The Program Manager shall be the primary point of contact within the company for the contract and shall establish a working relationship with the Procurement Contracting Officer (PCO), Contracting

Officer (KO), Contracting Officer’s Representative (COR), AIR-4.1 Lead Business Financial Manager

(BFM), and Contracts Specialist. The Program Manager is cognizant of the contract and aspects of the contract implementation within the prime Contractors’ organization. This role is not intended to circumvent company policy and when prime contract administrator to PCO / contract administer communication is required this does not seek to alter that. However, the Program Manager shall be cognizant, conversant, and up-to-date in the details of the contract. The Program Manager shall be the

Governments source for financial and technical progress data and status. The Program Manager shall call upon other departments within the company for data and status and will maintain and report this data to the Government. To facilitate the accuracy and timely delivery of this data to the Government, the Contractor shall maintain a staff from their Contracts and Financial departments in a secure contractor facility located within 20 miles of Naval Air Station (NAS) Patuxent River, Patuxent River, Maryland (NAS PAX).

The Program Manager shall provide processes for monitoring, tracking and reporting technical progress required by the monthly status reports for technical and financial progress. In addition, processes for the annual transition of contract years shall be established along with processes for adding, executing and removing tasks from the contract. A new process, when identified shall be established, executed and improved as required. The Program Manager shall provide reporting documents as specified by

CDRL A003.

Within 30 days of contract award, the Program Manager shall present a robust project management tool which tracks obligations and expenditures by customer, funding type, fiscal year, SOW paragraph, subcontractor, and person. (CDRL A002)

3.2 SYSTEMS ENGINEERING

The Contractor shall provide systems engineering functions to support the requirements of various projects in support of NAVAIR PMA Activities. The systems engineering functions include performance of the system analysis, functional allocations, synthesis, and evaluation efforts necessary to transform an operational need into an effective and affordable operational system. Included is the overall integration of all requirements in a manner that optimizes total system performance, quality, cost-effectiveness, and supportability. In support of the AIR-4.1 Division Head, the Contractor, using provided data, shall be required to perform the following systems engineering functions:

3.2.1 Technical Reviews. The Contractor shall support the NAVAIR technical review process to establish policy, outline the process, and assign responsibilities for the planning and conduct of Systems

Engineering Technical Reviews (SETRs) of NAVAIR programs in accordance with NAVAIRINST

4355.19 (NAVAIR Instruction – SETR Process). The Contractor shall research, analyze, collect, and develop presentations to support the technical review process for the air platforms, weapon systems, and related subsystems they will be supporting.

3.2.2 Requirements Management. Requirements Management includes requirements at the

Operational Requirements Document (ORD) / Capabilities Development Document (CDD) / Key

Performance Parameter (KPP) level. It also includes the performance or contracted specification, functional baseline requirements, allocated baseline requirements, preliminary product baseline requirements and the product baseline requirements. Software requirement specifications and software interface documents are also included. Change management processes are included in requirements management to include specification change notices and deviations. The Contractor shall support the requirements management process by researching, analyzing, collecting, and developing presentations in support the development of the technical requirements for the air platforms, weapon systems, and related subsystems they will be supporting.

3.2.3 Concept Definition. The Contractor shall research, analyze, collect, and develop reports/papers/data/presentations in support of the following:

1) The development of system performance requirements from approved Operational

Requirements Documents, provided by the Systems Engineering Competency

2) The application analysis of advanced technologies to meet system performance requirements.

3) The development of alternative conceptual system and subsystem designs

4) The analysis of alternative conceptual system performance

5) The threat analysis, test and evaluation (T&E), and fleet survey analysis to determine both near and far term System requirements, i.e., determine System parameters required to meet the threat and assets required for training, T&E, and operational readiness.

3.2.4 Operational Concepts Analysis. The Contractor shall provide support in preparing, from approved operational requirement documents, a detailed operational concept describing the system life cycle from concept development through system disposal. This document shall include requirements for the overall system, associated subsystems, and support systems. The Contractor shall provide support in performing a detailed performance requirements analysis using operational and mission scenarios. The objective of this analysis will be to determine operational utilization, system performance requirements, interoperability, operational concerns and support system requirements.

3.2.5 Reserved.

3.2.6 Interface Management. Interface management includes hardware and software interfaces, interfaces with Government Furnished Equipment (GFE), pilot interfaces, operator interfaces, maintainer interfaces, and supportability interfaces. Interfaces include external interfaces as well as system constraints such as shipboard interfaces and air transportability interfaces. The Contractor shall support the interface management process by analyzing the applicable air platforms, weapons systems, and subsystems and managing the interface between the applicable systems of the program they support.

3.2.7 Integrated Product Teams (IPT) / Working Groups. The Contractor shall support IPT, working groups, tiger teams and any other group or team assembled to evaluate and/or solve technical issues by attending working group meetings, providing technical expertise and feedback for the applicable air platforms, weapons systems, and subsystems they are supporting.

3.2.8 Earned Value Management (EVM). The Contractor shall provide EVM support for system engineering competency programs and Navy Field Activities. The Contractor shall assess the system engineering programs and Field Activities being considered for EVM implementation and provide

EVM needs assessment, implementation planning, informal training to competency personnel, software definition, system interface development, management control system documentation, report development and analysis, and validation/readiness support. The Contractor shall provide support in the establishment of Performance Measurement Baselines (PMB) for engineering aspects of system engineering competency programs including detailed review of program Integrated Master Schedules

(IMS) for proper activity relationships, resources, and EV integration techniques so that engineering objectives can be met. The Contractor shall review the IMS/EV program to ensure all contract scope is properly accounted for as well as verify that relationships leading up to design milestones are compliant with contract and competency execution controls associated with major design milestones such as

Preliminary Design Review (PDR), Critical Design Review (CDR), and software design reviews. The

Contractor shall provide support in the periodic evaluation of the contractors engineering related IMS and EVM data to assess progress relative to program IMS and EVM baselines. The Contractor shall also provide support in the preparation for and the conduct of Integrated Baseline Reviews (IBR), Schedule Risk Analyses (SRA) and other program IMS/EVM events, as required.

3.2.9 Flight Clearance. The Contractor shall support the flight clearance process in accordance with

NAVAIRINST 13034.14. The Contractor shall coordinate flight clearance inputs with competency engineers. The Contractor shall manage the process, track data products and report progress.

3.2.10 Program Assessments. The Contractor shall support program reviews, IBRs, OSD Program

Support Reviews, Navy Gate Reviews and other reviews required to support the program in accordance with DoDINST-5000.02 (Operation of the Defense Acquisition System). The Contractor shall research, analyze, collect, and develop presentations to support these reviews. The Contractor shall provide assistance to ensure these reviews are well organized and well run. The Contractor shall perform trade-off analysis, engineering approach analyses and recommend the specific systems development / engineering efforts, facilities and task requirements necessary to meet program test objectives and milestones. The Contractor shall decompose and describe specified operational requirements, integrated test and evaluation requirements, and test plans.

3.2.11 Cost Estimates. The Contractor shall support the development of the project and/or program cost estimates. The Contractor shall research, analyze and develop cost estimates. The Contractor shall write the Cost Analysis Requirements Description (CARD) in accordance with AIR-4.2 processes.

3.2.12 Acquisition Milestone Documentation. The Contractor shall support the development of documentation for the acquisition milestone and briefing material for the review. Development of plans and strategies shall include, but are not limited to: Systems Engineering Plan, Program Protection Plan, Acquisition Strategy, Technology Development Strategy, and Test and Evaluation Master Plan. The

Contractor shall support the Technology Readiness Assessment (TRA) process by developing the documentation to support the TRA review.

3.2.13 Program Planning / Future Planning. The Contractor shall provide support in the preparation of a Plan of Action and Milestones (POA&M) for programs based on inputs from the

Program leadership or requirements documentation. The Contractor shall also identify major milestones, schedules and relevant information on resource requirements for the applicable Life Cycle phase per the latest DoD 5000 series instructions. The Contractor shall prepare and deliver a POA&M

(CDRL A001), as required. The Contractor shall provide:

1) Schedule – organized by functional area, subsystems, and task requirements.

2) Milestones – corresponding to tangible products and procurement cycle requirements.

3) Resources – including: level of manpower, hardware or software required to achieve the final and intermediate milestones associated with each task.

4) A Systems Engineering Plan (SEP) or revisions of an existing SEP.

5) Test and Evaluation Master Plan (TEMP) implementation using Systems Engineering

Competency-provided data.

3.2.14 Analysis of Engineering Change Proposals (ECP). The Contractor shall provide technical development planning; perform trade-off analysis, engineering approach analysis for integration of subsystems, new functions, modes, architectures or modifications as specified in ECPs. Based on these analyses, the Contractor shall recommend specific system development / engineering efforts and task requirements necessary to meet program upgrade and second source objectives and milestones. The

Contractor shall provide support in performing trade-off studies and prepare position papers, including risk assessments, for alternative system considerations.

3.2.15 Engineering Investigations (EI). The Contractor shall support EIs, which includes on-site support, by performing engineering analysis, testing, data review and report writing. EIs will be conducted for the applicable air platforms, weapons systems, and subsystems they are supporting to determine cause and effect of any malfunction, failure, lifecycle limitations, and any other technical issue that requires analysis. The Contractor shall support the analysis of the EIs to support potential corrective, preventive, and technical actions for the applicable air platforms, weapons systems, and subsystems they are supporting.

3.2.16 Configuration Management (CM). The Contractor shall perform CM for systems engineering. The Contractor shall implement the six primary CM disciplines as follows:

1) CM planning

2) Configuration identification

3) Configuration control

4) Interface management

5) Configuration audits

6) Configuration status accounting

The Contractor shall define, organize, and establish all processes, procedures, and support systems required to accomplish this task. The Contractor shall formulate CM requirements, including programmatic and procurement aspects, for new start developments and modification programs in accordance with the criteria of NAVAIRINST 4130.1D, MIL-STD-973 and appropriate CM commercial standards. The effort shall include evaluation of Government furnished documentation and subsequent maintenance of prepared documentation. The Contractor shall prepare and deliver

Program’s CM Plan – Technical Reports (CDRL A002), as required.

3.2.17 Aircraft Systems / Subsystems Integration. The Contractor shall perform engineering analysis pertaining to systems and system controls considered for inclusion into the various platforms.

This analysis shall provide prediction data relative to the anticipated performance of the platform with the system and system controls. It shall also provide a definition of the required new or upgraded system functions.

The Contractor shall perform engineering reviews and analyses of government furnished data pertaining to new or modified avionics and/or sensors to determine the optimal approach to incorporate changes, enhancements, planned product improvements, and new capabilities into test bed and production platforms. This shall include, but not be limited to, combining independent components or subsystems on particular configurations of aircraft. The review and analysis shall include interfaces, modes of operations of equipment, mission computers, protocols, power, signal conditioning, sensors, controls and displays, and electromagnetic interference (EMI) issues. The Contractor shall provide prediction data relative to the anticipated platform performance configured with the new or modified avionics/sensor suite. The analysis shall also provide a definition of the required new or upgraded system functions. The Contractor shall prepare and deliver Technical Reports (CDRL A003), as required.

3.2.18 Air Platform Technology Insertion. The Contractor shall do an assessment on the application of avionics technology to subsystems and systems for Navy airborne platforms concerning available technology; technology maturity; technical, cost and schedule risk; and platform applicability. This assessment shall be required to compare and select current and potential components, devices, units, subsystems, or systems built up from low level pieces. The assessment shall consider, at a minimum, the application of commercial off-the-shelf (COTS) hardware and signal processing equipment, degree of platform commonality, technology availability, maturity and stability, interfaces, protocols, and support requirements for a wide range of avionics technologies, including integrated avionics, night vision devices, microwave, low probability of intercept, sensors (Electro-optical/Infrared

(EO/IR)/Radar), communications, and tactical decision aids. These technology areas shall include hardware and signal processing used for specifications development, device implementations, integration, test and validation, documentation development and maintenance, and performance monitoring.

The Contractor shall supply technical information on a wide range of platform and avionics equipment.

Platform specific recommendations and option papers shall be prepared to validate specific technology insertion objectives. The analysis shall be based on an in-depth understanding of the technology and its impact upon the platform system under consideration. The Contractor shall provide inputs for position papers, schedules, and implementation plans as part of this requirement. Both independent technology considerations and cross-platform uses and commonality efficiencies shall be included in the analysis.

An important aspect is the determination of the optimal use of a technology by a specific configuration of platform components with emphasis on out-year growth, interoperability, capability, and supportability. The Contractor shall prepare and deliver Technical Reports (CDRL A002), as required.

3.2.19 Mission Planning Requirements Analysis. The Contractor shall review the mission planning requirements of various weapons systems to determine which requirements can be supported by available mission planning systems and databases and which requirements require system modifications and/or additional database development. The Contractor shall identify tasks and schedules for mission planning system development to meet the needs of weapons systems. These weapon systems may include:

1) Manned and unmanned air vehicles

2) Air-to-ground and air-to-air guided weapons

3) Airborne reconnaissance systems (Tactical Airborne Reconnaissance Pod System (TARPS))

4) Electronic warfare systems (ALE-47, ALR-67/ASR)

5) Communications systems (Joint Tactical Information Distribution System (JTIDS))

6) Navigation systems (Global Positioning System (GPS))

7) Ground-based weapons system trainers

3.2.20 Functional and Design Requirements Analysis. The Contractor shall perform systems engineering for the purpose of recommending functional and design requirements. The Contractor shall perform functional requirements analyses. The analysis shall be based upon the detailed operational scenario and mission timeline data. The system functional analysis will be used to analytically derive operator, hardware and software functionality. The Contractor shall develop system performance requirements. The Contractor shall perform detailed performance requirements analyses using the operational scenario and the system functional requirements as a baseline. The performance analysis will identify the specific airframe and avionics capabilities required at the system and subsystem levels.

The analysis will also include the review of proposed airframe modifications which will impact the flying qualities of the aircraft or impact overall mission performance. The Contractor shall prepare and deliver Technical Reports (CDRL A002), as required.

3.2.21 Specifications. The Contractor shall conduct engineering analysis to support development/ review of specifications for the air platforms, weapon systems, and related subsystems they will be supporting. Examples of those specifications are:

1) Type Specifications

2) Detailed Specifications

3) System Specifications

4) Performance Specifications

5) Interface Design Specifications

6) Software Interface Specification

7) Software Program Performance Specification

8) Test Specifications

9) Production Specifications

3.2.22 Simulation Facility Studies and Analysis. The Contractor shall prepare simulation facility requirements and associated planning information to support the integration and evaluation of advanced technologies into the air platforms, weapon systems, and related subsystems they will be supporting.

The Contractor shall provide support in preparing a simulation facility plan addressing the need for evaluation of advanced system concepts including multi-sensor correlation. The plan shall include simulator functional definition, task plans, schedules, resources, and interfaces with existing simulation facilities.

3.2.23 T&E Support – Requirements, Plans and Procedures. The Contractor shall develop engineering test plans and schedules required to support certification flight tests by the Operational Test and Evaluation Force (OPTEVFOR). The Contractor shall provide on-site test support to respond to trouble reports and hardware problems, as required. The Contractor shall prepare a test and evaluation requirements analysis that identifies the test activities required to verify attainment of all functional and performance requirements of the platform. This analysis shall include all levels of testing from technology concept demonstration through laboratory and system flight test including retest requirements due to the implementation of engineering changes. As part of this analysis the Contractor shall develop a test and evaluation matrix that identifies the system functional requirements and the test activities that demonstrate satisfactory compliance. An optimization process shall be performed that will identify where individual tests may satisfy multiple requirements. The Contractor shall provide detailed test plans and procedures. For test plans and procedures developed by other activities, the

Contractor shall analyze these test plans and procedures to insure the requirements of the test matrix are being tested.

3.2.24 Non-Cooperative Target Identification (NCTI), Multi-Sensor Integration. The Contractor shall collect and analyze radar data, develop improved radar target identification algorithms, integrate target identification techniques into operational airborne radar systems, conduct T&E of target identification processors, and provide NCTI planning and technical documentation. The Contractor shall provide support in the development of airborne multi-sensor integration for various aircraft, including the design of algorithms, support for the integration and flight tests, and analyses of intermediate data and flight test data. The Contractor shall support the development of advanced Multi-

Sensor Integration (MSI) techniques, and apply them to advance and existing Navy platforms.

3.2.25 Independent Validation and Verification (IV&V) Support. The Contractor shall provide support personnel to operate and maintain systems during validation and verification. This will be accomplished by becoming familiar with the platform and/or systems being evaluated, learning the operation of the systems, and being capable operating those systems during IV&V. The Contractor shall also provide systems engineering support required to test and validate the functions of the system in accordance with a government-developed IV&V test plan by utilizing the test procedures within the test plan (CDRL A004).

3.2.26 Technology Transfer Program Support. The Contractor shall prepare, review, or edit project support documentation papers, publications, handbooks, brochures, or newsletters. The Contractor shall coordinate the development of exhibit materials including displays and handouts and prepare camera-ready copy of technology transfer publications including brochures, flyers, product descriptions, and intellectual property assets. The Contractor shall develop new or modify existing database systems in order to support the collection and dissemination of information regarding the technology transfer program. The Contractor shall attend Technology Transfer Meetings, prepare meeting minutes for select meetings, and distribute meeting minutes and action item status reports to selected participants.

3.2.27 Network Centric Warfare (NCW). The Contractor shall support the NCW initiative in concept through operational deployment. The Contractor shall provide the engineering, hardware, software and operation research expertise along with operational experienced personnel in the planning

/ coordination, force control and engagement stages through the use of technology, development of organizations and doctrine and evaluation of tactics. The Contractor shall conduct research and analysis of the Electromagnetic Spectrum Supportability Policies and initiatives, IT initiatives, as well as Electronic Warfare (EW) initiatives that support NCW concepts or doctrines. The Contractor shall provide support in analyzing the effective use of intelligence, surveillance and reconnaissance information along with command and control to obtain a common picture and provide real-time and authenticated precision targeting knowledge. The Contractor shall use the government modeling and simulation facilities and recommend updates and changes to most effectively evaluate proposed NCW models.

3.1.28 Mission Planning System Design, Integration and Evaluation. The Contractor shall provide systems engineering and laboratory support to identify, integrate, test and evaluate mission system hardware components. These components typically include processors, tape drives, mass memory devices, data transfer modules, interface cards, printers, color copiers, etc. The Contractor shall be required to define prototype designs of advanced systems which may be developed utilizing commercial equipment-separately procured by the Navy, assemble and integrate all components of the system, and develop and execute a detailed test procedure to provide a comprehensive evaluation for proposed advanced mission planning systems.

3.1.29 Mission Scenario / Time Line Analysis. Using approved operational requirements documents, the Contractor shall provide support in the preparation a detailed mission scenario and time line analysis by analyzing established mission requirements with platform/mission capabilities.

The Contractor shall support the Systems Engineering Competency review of the scenario data with operational activities including, but not limited to, Naval Strike and Air Warfare Center, VX-9, and fleet squadrons through review of the Operational Requirements Document (ORD) and interfacing and communicating directly with fleet operators.

3.3 DELIVERABLES AND DOCUMENTATION. Deliverables shall be task dependent and may include one or more of the following:

A001 Plan of Action & Milestones (POA&M)

A002 Technical Reviews, Reports & Papers

A003 Management Plans

A004 Validation & Verification (V&V) Documentation

A005 Incurred Cost CDRL

A006 Non-Disclosure Agreement (Company)

A007 Non-Disclosure Agreement (Individual)

A008 Information Technology Personnel Security Reports (COR)

A009 Information Technology Personnel Security Reports (NAVAIR Security)

A00A Operational Security (OPSEC) Plan

3.4 OTHER DIRECT COSTS (ODC): TRAVEL AND MATERIAL

ODCs necessary for performance of this contract shall be reimbursed in accordance with NAVAIR clauses 5252.232-9509, Reimbursement for Travel, Per Diem, and Special Material Costs, and clause

5252.242-9515, Restrictions on the Direct Charging of Material. ODCs may include G&A expenses as allowed by the Contractor’s accounting standards, but shall not include profit. Any material remaining after completion of the contract, the cost of which has been reimbursed by the Government, will remain

Government property and disposition instructions will be sought from the PCO.

3.4.1 Travel. Continental United States (CONUS) and Outside the Continental United States

(OCONUS) travel may be required in support of this contract to perform services at other DoD, industry and related locations as approved by the government in individual tasks. OCONUS travel may be required to the following countries: Canada, England, France, Germany, Italy, Sweden, Denmark, Israel, Turkey, Japan and Australia. The number and types of trips, including the number of persons traveling shall be limited to the minimum required to accomplish work requirements and shall be coordinated with, and approved by the Government Technical Point of Contact (TPOC) and the COR for each individual trip prior to travel. Costs associated with travel and lodging shall be reimbursed in accordance with Federal Joint Travel Regulations (JTR).

3.4.2 Material. Per NAVAIR clause 5252.242.9515, Material may be purchased incidental to the tasking. The material costs may include such items as: photocopying, postage, office supplies, briefing materials, and video and voice conferencing services. Contracting Officer (KO) approval shall be obtained for all material purchases.

4.0 INFORMATION TECHNOLOGY (IT)

The Government will provide all necessary reference documents not generally available to the

Contractor as required. Throughout the life of the contract, if any instruction or document is replaced or superseded, the replacement or superseding instruction or document shall be applicable to the requirements defined in this SOW.

The Contractor shall not purchase any IT equipment on behalf of NAVAIR in support of this Contract, which reports to PBIS-IT, without a Naval Air Systems Command (NAVAIR) Command Information

Officer (CIO) approved NAV-IDAS ITPR.

4.1 CLINGER-COHEN ACT

In 1996, Congress enacted the Clinger-Cohen Act (CCA) requiring agencies to use a disciplined capital planning and investment control process to acquire, use, maintain and dispose of information technology. In accordance with the following Department of Defense Directive (DoDD), Department of Defense Instruction (DoDI), Office of the Secretary of Defense (OSD) memo, and Secretary of the

Navy Instruction (SECNAVINST), CCA compliance is required for all programs that contain IT, including National Security Systems (NSS). NSS are defined in National Institute of Standards and

Technology (NIST) Special Publication (SP) 800-59. Six factors are used to identify NSS, one of which is IT in weapons and weapons system programs. The law provides authority to the agency’s Chief

Information Officer (CIO) to manage IT resources effectively and ensure cybersecurity and interoperability. The authority to grant compliance with CCA as a statutory milestone program document resides at either first echelon or second echelon. The level of the Acquisition Category

(ACAT) or designation as an Abbreviate Acquisition Program (AAP) determines which echelon has this authority. ACAT III and below acquisition programs CCA compliance assertion confirmation approval authority is delegated to the second echelon Command Information Officers. ACAT I and

ACAT II acquisition programs CCA compliance assertion confirmation approval resides at DON CIO

(First echelon). Approval of interoperability standards compliance for all acquisition programs resides at DON CIO. Approval of the Cybersecurity Strategy (formerly Acquisition Information Assurance

Strategy) is a component of CCA compliance however it is approved separately. Approval authority is divided among the DoD, and DON CIOs as well as the second echelon Command Information Officers.

See Table 1 for allocation of approval authorities.

ACAT Review and

Endorsement by

Command

Information

Officer

Approval by as Command

Information

Officer

Review and

Endorsement by

DASN

(C I&Space)

Review and

Endorsement by

DON CIO

Approval by DON

CIO

Approval by DoD

CIO

IC X X X

ID X X X X

IAM X X X X

IAC X X X X

II X X X

III X

IV X

AAP X

See Interim DoD 5000.02 Enclosure 11, Section 6.b.(1): For ACAT ID, IAM, and IAC programs, the DoD CIO will review and approve the Cybersecurity Strategy prior to milestone decisions or contract awards.

Table 1: Allocation of Cybersecurity Strategy Approval Authorities

Cybersecurity Strategy approval process begins after the Program Manager signs the Cybersecurity

Strategy and puts it forward to the Command Information Officer. The final approved Cybersecurity

Strategy is an appendix to the Program Protection Plan (PPP) as well as an element of CCA compliance

(Interim DoDI 50000.02, Tables 2 and 9).

a. Interim DoD Instruction 5000.02, “Operation of the Defense Acquisition System”, November 25,

b. OSD Memo, Clinger-Cohen Act Compliance Policy, Mar 8 2002

c. SECNAVINST 5000.2E, Implementation and Operation of the Defense Acquisition

4.2 SYSTEM SOFTWARE / APPLICATION COMPLIANCE

All Information Technology Systems or software/application development, modification or support shall be performed in accordance with Defense Business Transformation guidance (formerly Business

Management Modernization Program (BMMP)), Department of the Navy (DON)/Naval Air Systems

Command (NAVAIR) Functional Area Manager (FAM) Policies and Guidance, Network and Server

Registration, and Web Enablement mandates.

4.3 WEB SITES, WEB ENABLEMENT AND APPLICATION / SYSTEM

DEVELOPMENT, MODIFICATION, AND MAINTENANCE SUPPORT SERVICES

All Information Technology systems, software, and website development, modification or support shall be performed in accordance with all applicable Federal, DoD, DON, and NAVAIR policy, guidance, standards, and strategies, and should be integrated within the NAVAIR Enterprise portal and collaboration environment whenever possible. Any Web sites/servers hosted/located in contractor facilities, or outside NAVAIR enclave, will transition to NAVAIR architecture and infrastructure in accordance with Legacy Shutdown guidance. Policies include, but are not limited to:

a. Office of Management and Budget Management of Federal Information Resources, OMB

CIRCULAR NO. A-130 Revised.

b. OMB Policies for Federal Agency Public Websites, OMB M-05-04 http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-04.pdf

c. Section 508 Amendment to the Rehabilitation Act of 1973 http://www.section508.gov/

d. Department of Defense Web Policies and Guidelines http://www.defense.gov/webmasters

e. Navy Information Operations Command (NIOC) Norfolk Web Risk Assessment Team Website http:www.public.navy.mil/fcc-c10f/nionorfolk/Pages/AboutWRA.aspx

f. DON Policy for Content of Publicly Accessible World Wide Web Sites SECNAVINST 5720.47B www.navy.mil/navydata/internet/secnav5720-47b.pdf

g. NAVAIR CIO Website (NAVAIR specific policy and guidelines) To request this policy contact the

NAVAIR CIO office – 7.2.2 Applications Integration team – Web Manager: Shane Malamphy at

301- 342-1825

h. Defense Information Systems Agency (DISA) Hosting of All Navy Websites (NAVADMIN

061/08) http://www.public.navy.mil/bupers‐ npc/reference/messages/Documents/NAVADMINS/NAV2008/NAV08061.txt

i. Consolidation of Navy Web Sites - Reduction of IM/IT Footprint NAVADMIN 145/07 http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-04.pdf http://www.section508.gov/ http://www.defense.gov/webmasters http://www.public.navy.mil/fcc-c10f/nionorfolk/Pages/AboutWRA.aspx http://www.public.navy.mil/fcc-c10f/nionorfolk/Pages/AboutWRA.aspx http://www.navy.mil/navydata/internet/secnav5720-47b.pdf http://www.public.navy.mil/bupers‐ http://www.public.navy.mil/bupers-npc/reference/messages/Documents/NAVADMINS/NAV2007/NAV07145.txt

j. DON Web Presence Policy: The Registration, Compliance of, and Investment in, All Unclassified

Web Sites and Uniform Resource Locators http://www.doncio.navy.mil/ContentView.aspx?ID=577

k. Policy and Procedures for Web Risk Assessment (WRA) of Publicly Accessible Navy Sites

(ALCOM 129/09) http://www.public.navy.mil/fcc‐c10f/niocnorfolk/Documents/NTD‐08‐09.txt

4.4 SOFTWARE DEVELOPMENT / SERVER PROCUREMENT

Any tools developed that will be hosted by the Navy Marine Corps Intranet (NMCI) or run on NMCI workstations will be certified for NMCI and comply with NMCI policy. Additionally, any servers supporting this effort will be transitioned to meet the requirements of the current NAVAIR Server

Consolidation effort.

4.5 CYBERSECURITY

NAVAIR’s Cybersecurity Program is a unified approach to protect unclassified, sensitive or classified information, and is established to consolidate and focus efforts in securing that information, including its associated systems and resources. Cybersecurity is required operationally throughout the DON. The

DON CIO is responsible for IT within the Navy, as mandated by the Clinger-Cohen Act, and is the lead for departmental compliance with the Federal Information Security Management Act of 2002.

All Cybersecurity shall be in compliance with the following listed instructions:

a. ASD (NII) Directive-Type Memorandum (DTM) 08-027 – Security of Unclassified DoD

Information on Non-DoD Information Systems, 31 July 2009

b. Chairman of the Joint Chiefs of Staff Instruction CJCSI 3170.01H (series), Joint Capabilities

Integration and Development System, 10 January 2012

c. CJCSI 6211.02D Defense Information System Network (DISN): Policy and Responsibilities, 24 Jan

d. CJCSI 6212.01F Net Ready Key Performance Parameter (NR KPP), 21 March 2012

e. CJCSI 6251.01D Narrowband Satellite Communications Requirements, 30 Nov 2012

f. CJCSI 6510.01F, Information Assurance (IA) and Support to Computer Network Defense (CND), 09 Feb 2011, certified current 10 Oct 2013

g. Chairman of the Joint Chiefs of Staff Manual CJCSM 6510.01B – Incident Handling Program 10

July 2012

h. Chief of Naval Operations/Headquarters, United States Marine Corps CNO N614/HQMC C4 –

Navy-Marine Corps Unclassified Trusted Network Protection (UTN- Protect) Policy, Version 1.0, 31 October 2002

i. Defense Acquisition Guidebook – Chapter 7, Acquiring Information Technology, Including

National Security Systems, Section 7.5 Information Assurance (IA) http://www.public.navy.mil/bupers-http://www.public.navy.mil/bupers-http://www.doncio.navy.mil/ContentView.aspx?ID=577 http://www.public.navy.mil/fcc

j. DoD 5220.22-M, National Industrial Security Program Operating Manual, February 28, 2006

(NISPOM)

k. DoD 8570.01-M, Information Assurance Workforce Improvement Program, 19 Dec 2005

(Incorporating Change 3, 24 Jan 2012)

l. DoDD 8000.01 Management of the Department of Defense Information Enterprise, 10 February

m. DoDD 8100.02, Use of Commercial Wireless Devices, Services, and Technologies in the

Department of Defense (DoD) Global Information Grid (GIG), 14 April 2004, Certified Current as of 23 April 2007

n. DoDD 8570.01 Information Assurance Training, Certification, and Workforce Management, 15

August 2004, Certified Current as of 23 April 2007

o. DoDI 4630.8, Procedures for Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS), 30 June 2004

p. DoDI 8500.1, Cybersecurity, 14 March 2014

q. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 12

March 2014

r. DoDI 8520.2, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, 01 April 2004

s. DoDI 8551.1, Ports, Protocols, and Services Management (PPSM), 13 August 2004

t. DoDI 8580.1, Information Assurance in the Defense Acquisition System, 9 July 2004

u. DoDI 8581.01, Information Assurance (IA) Policy for Space Systems Used by the Department of

Defense, 8 June 2010

v. DON CIO Memo 02-10, Department of the Navy Chief Information Officer Memorandum 02-10

Information Assurance Policy Update for Platform Information Technology, 26 April 2010

w. DON letter 5239 NAVAIR 726/2322 of 18 Feb 09, NAVAIR Data at Rest Policy

x. Federal Information Processing Standards Publications (FIPS PUB) http://www.nist.gov/itl/fips.cfm

y. National Security Telecommunications and Information Systems Security Policy NSTISSP No. 11, Revised Fact Sheet National Information Assurance Acquisition Policy, July 2003

z. Office of the Chief of Naval Operations OPNAV INST 5239.1C, Navy Information Assurance (IA)

Program, 20 Aug 08

aa. SECNAV M-5239.1, Department of the Navy Information Assurance Program; Information

Assurance Manual, November 2005

bb. SECNAVINST 5230.15, Information Management/Information Technology Policy for Fielding of http://www.nist.gov/itl/fips.cfm

Commercial Off the Shelf Software, 10 April 2009

cc. SECNAVINST 5239.3B, Department of the Navy Information Assurance Policy, 17 June 2009

dd. SECNAVINST 5239.19, Department of the Navy Computer Network Incident Response and

Reporting Requirements, 18 March 2008

ee. The National Security Act of 1947

ff. Title 40/Clinger-Cohen Act

gg. Title 44/ Federal Information Security Management Act

All IT procured on behalf of this contract shall meet all DoD/DON and NAVAIR IA polices. Failure to follow these policies will result in denied access to NMCI, One Net, Integrated Shipboard Network

System (ISNS) and other DON, DoD and Joint Networks. These IA policies are standard across the

Department and ensure IA compatibility and interoperability.

IT systems and or networks operated by contractors pursuant to a NAVAIR contract, regardless of the level of data processed, shall be operated in accordance with the NISPOM.

Contractor-owned equipment shall be permitted connections to NAVAIR/DoD networks in order to carry out the performance of this contract. All Contractor-owned hardware and/or software shall meet

DoDI 8500.2 Cybersecurity Controls, is subject to validation scanning and must be approved by the

NAVAIR site IA Manager prior to connection.

The following specific criteria must be met before the contractor may be connected to any DoD or

NAVAIR network in support of this contract. Requirements include:

a. Network Vulnerability Scanning. NAVAIR Deputy CIO for Information Assurance maintains authorized auditing tools and shall provide for firewall/port scans, device discovery scan, vulnerability assessment, and other requirements as required to ensure secure interoperability with

DoD Contracts. The contractor shall be responsible for the remediation of any equipment that fails these audits prior to the connection the system to the networks; Results of approvals shall be documented via Memorandum of Agreement with the Facility Security officer and the Defense

Security Service Representative for that contractor;

b. Extent of Validation Scanning. To prevent scanning of corporate assets, all such networks, equipment and connections shall be physically segregated from any government/contractor corporate networks that are not in direct support of DoD contracts;

c. Circuit Provisioning. Any circuit or connection between NAVAIR and/or DoD site and the contractor site shall be provisioned via the Defense information Security Agency and comply with

CJCSI 6211.02C (series), Defense Information System Network (DISN): Policy and

Responsibilities, 9 July 2008;

d. Servicing Systems from a Remote Contractor Site. Remote Access Service connections that allow off-station operation and/or administration of contractor owned systems, located at any NAVAIR facility or site, shall not be permitted, with the exception of those systems connecting to the

Command via the Outreach Services identified in Section 7, Enterprise Architecture;

e. Memorandum of Agreement and Inter-connection Agreements. An Information Assurance

Memorandum of Agreement (MOA) between the contractor owning the equipment and AIR-7.2.6 shall be developed and signed before the equipment can be connected to NAVAIR networks.

Failure to comply with the signed MOA shall be grounds for disconnection from the network.

4.6. ENTERPRISE ARCHITECTURE

a. Contractor Networks and Connections. Contractor-owned and operated networks are prohibited on any Naval Air Systems Command (NAVAIR) facility or site in support of this contract. The contractor may access non-government, external IP space via the NAVAIR-provided Virtual Private

Network (VPN) Outreach service or NAVAIR CIO approved Internet Protocol (IP) service.

b. Architecture Compliance. The contractor shall ensure all IT solutions, including database solutions, comply with the appropriate NAE Enterprise Architecture, and are verified by the NAVAIR

Enterprise Architect (AIR-7.2.3) prior to build out.

c. Disclosure of pre-existing networks, circuits or connections. Any and all networks, circuits or connections between the contractor and any NAVAIR site related to previous contracts shall be identified in the MOA. Failure to comply and subsequent discovery of an unregistered network, circuit or connection shall be grounds for immediate disconnection.

5.0 SECURITY

5.1 SECURITY CLEARANCES

The Contractor shall have the capability to perform work up to the TOP SECRET level and shall employ security protection and ensure security for all efforts. The facility clearance and level of safeguarding required is TOP SECRET. The Contract Security Classification Specifications are set forth in the attached DD Form 254. On site access to the Secret Internet Protocol Router Network

(SIPRNET) will be required to perform a significant level of tasking under this contract. (CDRLs A006 and A007).

5.2 OPERATIONAL SECURITY (OPSEC) PLAN

The Contractor is required to provide OPSEC protection for all sensitive information (as defined in

Title 15, United States Code, Section 278g-3(d)(4). Use OPNAVINST 34321.1 and National Security

Decision Directive (NSDD) 298 for the concept of OPSEC, and apply the framework for telecommunications security in Defense Federal Acquisition Regulation Supplement (DFARS) Clause

252.239-7016, as appropriate. The Contractor shall apply to meet and use Distribution Statements following the provisions of Exhibit 8A, SECNAVINST 5510.36. In order to meet this requirement, the

Contractor shall develop, implement and maintain a facility level OPSEC program to protect sensitive information to be held, provided, used, handled, discussed, processed, stored, transmitted, or delivered at a Contractor's or Subcontractor's facilities during performance of this contract. The Contractor shall submit the document in MS Word 6.0 (or later) format on floppy or compact disk and in hard copy to the Government (AIR-7.4.4) for approval. (CDRL A008)

5.3 IDENTIFICATION (ID) BADGES

The Contractor shall furnish all requested information required to facilitate issuance of identification badges, as required, and shall conform to all applicable regulations concerning their use and possession.

ID media is U.S. Government property and shall be surrendered to the Pass and ID Office upon expiration or termination of employment. The Government will not check out Contractor personnel unless all media, including Common Access Cards (CACs), are returned in accordance with

NASPAXRIV Instruction…