AIR_4.3_N00421-15-R-0042_Draft_SOW.pdf

DRAFT STATEMENT OF WORK, N00421-15-R-0042

1.0 SCOPE

This Statement of Work (SOW) defines the effort required for engineering and technical services to support the development of advanced air vehicle technologies, primarily through the use of modeling and simulation. This

Indefinite Delivery Indefinite Quantity (IDIQ) contract vehicle will permit specific task orders to be issued, based on the tasking outlined in Requirements (Section 4.0). Performance-based (PB) and Non-Performance based (NPB) elements of the SOW shall be in effect, as identified herein.

1.1 Background

The Naval Air Systems Command (NAVAIR) Air Vehicle Engineering Department (AIR-4.3) mission requires specialized engineering / technical services in support of the development and operation of state-of-the-art air vehicle dynamic simulations and architecture, collision avoidance systems algorithm design, engineering analysis, and system acquisition. These services are required to support current and future piloted and desktop engineering simulation capabilities, aircraft trainer devices, and Department of Defense

(DoD) manned aircraft and Unmanned Air Vehicles (UAVs) in-service and acquisition programs. These efforts pertain to flight vehicle models and simulations, flight control systems, engine control systems, collision avoidance systems, flight test data analysis, and related engineering support.

2.0 APPLICABLE DOCUMENTS

2.1 Controls Analysis and Simulation Test Loop Environment (CASTLE ) User’s Guide Version 6

2.2 CASTLE

Developer’s Guide Version 6

2.3 Terrain Awareness Warning System (TAWS) Life Cycle Model (LCM)

2.4 TAWS Processes and Procedures (PROC-006: Combined Configuration Audit Procedure)

2.5 Integrated Battlespace Simulation and Test Department Security Standard Operating Procedures

3.0 REQUIREMENTS

The contractor shall provide engineering/technical services required to support the tasks specified herein. No personal services may be performed under this contract.

* Subparagraphs 3.1 through 3.9 and 3.11 are NPB tasks

* Subparagraph 3.10 is a PB task

3.1 Modeling of Aircraft and UAVs for use in Simulations

Models are used to support the Air Vehicle Engineering Department mission, and include simulations housed within the Naval Air Warfare Center-Air Division (NAWCAD) Manned Flight Simulator (MFS). These models are typically 6-Degree-of-Freedom (6-DOF), physics-based, verified against airframe manufacturer-provided check cases, and validated using available flight test and system design data. Models are developed, modified, and maintained in Fortran, C/C++, MATLAB/Simulink, and other programming languages. Models are used in both real-time and offline (desktop) simulations and include engineering simulators and aircraft trainers / flight simulators for developmental, and in-production platforms.

3.1.1 Modeling of Air Vehicles for use in Simulations

The contractor shall support development, production, and maintenance of new flight dynamics models or upgrade existing flight dynamics models using existing models, available flight test data, wind tunnel data, or analytic data (such as Computation Fluid Dynamics) used to generate force and moment coefficient data. The contractor shall support the development, production, and maintenance of code within existing

CASTLE

architecture. Models may include airframe, rotor, flight control, propulsion, landing gear, engine or aircraft system models. The contractor shall support the integration, modification and sustainment of these models into the simulation architecture and verify/validate the resulting simulation or simulation updates as described in Section 4.1.3. Models may be used for engineering simulations and aircraft trainers / flight simulators for developmental and in-production platforms.

3.1.2 Pilot Modeling

The contractor shall support development, production, and maintenance of pilot models using classical and/or modern/advanced techniques. Using the developed models, the contractor shall support the evaluation and improvement of display systems, the proposal of candidate flight test programs, and the performance of specification compliance evaluations. The contractor shall also support the identification of pilot sensitivity to system/subsystem performance and the conduct of overall closed-loop control system analyses. The models may be used to support engineering simulations and aircraft trainers / flight simulators for developmental, in-production, and in-service platforms.

3.1.3 Simulation Verification and Validation

The contractor shall support simulation verification and validation efforts, as below. Efforts may be in support of engineering simulations and aircraft trainers / flight simulators for developmental, in-production, and in-service platforms.

3.1.3.1 Verification

The contractor shall support the performance of simulation verification by comparing retrofitted and operational model outputs to simulation data provided by the aircraft manufacturer or other sources.

Wherever the models do not match within the prescribed tolerances, the simulation shall be analyzed to determine the source of the difference. The verification results shall be documented, including tables and plots, as needed, to demonstrate a match along with explanations for unresolved differences.

3.1.3.2 Validation

The contractor shall support the performance of simulation validation by comparing simulation outputs against flight test data, including both trim conditions and time history runs for both in-production and operational platforms. The flight test data shall be analyzed for kinematic consistency and instrumentation error. The simulation performance to the aircraft performance shall be documented with plots. The capability to compare the simulation to aircraft data shall be automated to the greatest extent possible.

3.2 CASTLE

Support

CASTLE

is the NAVAIR-owned, designed and developed simulation architecture for desktop engineering analysis and piloted real-time lab operation. CasView is the NAVAIR-owned, designed and developed suite of visualization software.

3.2.1 The contractor shall provide support to the CASTLE

development team through modification, maintenance and development of CASTLE code. The contractor shall support updates and/or rework and development of the CASTLE graphical user interface to enhance flexibility and operation. The contractor shall support updates and/or rework and develop physics-based models such as the equations of motion, atmosphere, winds, turbulence, gusts, terrain, targets, ship dynamics and ship airwake. The contractor shall support the modernization, development, and sustainment of tools such as the variable driver, trim, linear model extraction and plot tools. The contractor shall also support the modification, development, and sustainment of external interfaces to the CASTLE architecture, such as the MATLAB, Simulink, COM, CasView and lab interfaces. The contractor shall support the update and/or rework and development of the function table lookup capability used to interrogate, interpolate and extrapolate simulation data tables. Updates shall be coded in C++ and other programming languages as determined by the CASTLE development team. Support efforts may include development, modification, and maintenance for updates and/or rework of aircraft trainers/flight simulators.

3.2.2 The contractor shall provide support to the CASTLE

development team through development, modification, and maintenance of the CasView software suite. The contractor shall support the updates and/or rework and development of visualization software for generating pilot Heads Up Displays

(HUDs) for Navy and other aircraft as required. The contractor shall support the development, modernization, and update and/or rework of visualization software used for ship model integration including visualization of the ship physical model, the out-the-window visual model, and the ship airwake volumes and velocities generated by CFD or other methods. The contractor shall support the updates and/or rework and development of visualization software for generating an out-the-window visual scene for desktop or piloted simulation applications. This visualization software will include models of Navy and other aircraft as required and capabilities to customize the visual scene to support engineering analysis and accident/incident investigations. Updates and/or rework shall be coded in

C++ and other programming languages as determined by the CASTLE development team. Support may include reviewing and analyzing data and code to determine what changes may be required, coding, and performing verification and validation of the code updates and/or rework. Support efforts may include development, modification, and maintenance for updates and/or rework of aircraft trainers/flight simulators.

3.3 Ground Proximity Warning Systems (GPWS)/ Terrain Awareness Warning System (TAWS)/ Collision

Avoidance Systems (CAS)/ Mid-air Collision Avoidance Capability (MCAC)

3.3.1 The contractor shall provide support for the development, modification, integration, test and maintenance of GPWS, TAWS, CAS, and MCAC systems being developed by NAVAIR. The contractor shall support the analysis of simulator and flight test data to determine improvements to existing GPWS/TAWS algorithms, and update algorithms to address discrepancies identified during testing. The contractor shall support the recommendation of overall evolutional system improvements.

If required, the contractor shall support the development or improvement of flight models and simulations for aircraft platforms for which GPWS/TAWS/CAS/MCAC solutions are being developed.

Support may include solutions for developmental, in-production, and in-service platforms, as well as for training / flight simulators.

3.3.2 The contractor shall support development, modernization, and sustainment of sense-and-avoid capability for Unmanned Aerial Systems (UAS) integration into the National Airspace. The contractor shall support the analysis of airborne and ground based sensor systems for their capabilities with respect to sense-and-avoid applications. The contractor shall also support the identification of sensor data fusion techniques that can be applied to platforms that include multiple sensor systems. The contractor shall support the development, modification, and sustainment of sensor agnostic tracking algorithms compatible with air traffic scenarios representative of the National Airspace. If required, the contractor shall support the development, modification or improvement and/or rework of models of sensor characteristics and datalink signals for solutions that are being developed. Support may include solutions for developmental, in-production, and in-service platforms, as well as for training / flight simulators.

3.4 Lab Integration Support

The contractor shall support integration, modification, and evaluation of software and hardware into simulations housed at the MFS and other NAWCAD lab environments and facilities. Support may include solutions for developmental, in-production, and in-service platforms.

3.4.1 The contractor shall support integration, modification, and evaluation of airframe models into the lab environment, including the cockpit, control loader, aural cueing system, Out-the-Window

(OTW) visual system, motion base, Instructor Operator Station (IOS), and Hardware-in-the-Loop

(HWIL) components.

3.4.2 The contractor shall support simulation development, modification, and updates as required to maintain currency with changing lab hardware and software components as driven by customer requirements and Information Assurance (IA) requirements. The contractor shall support the generation of code updates and/or modifications to the simulation software and will support the performance of regression testing to ensure simulation functionality was not adversely impacted.

3.4.3 The contractor shall support integration, modification, and evaluation of actual aircraft Flight

Control Computer (FCC) and engine control (e.g., FADEC) hardware, as well as avionics hardware

(e.g., mission computers) with existing simulators. The contractor shall support the development or update and/or modification of code that interfaces the hardware with simulation airframe model. The contractor shall support the verification that the hardware has been integrated correctly by running check cases and/or tests and comparing with data provided by the hardware vendor.

3.5 Simulation Execution

The contractor shall support both piloted and desktop simulation execution, as follows:

3.5.1 The contractor shall support the operation of pilot-in-the-loop simulations for customers. The contractor shall support the evaluation and troubleshooting of issues, the documentation of problems in the appropriate platform discrepancy report database and the administration of simulation session data to the customer. The contractor shall support the modification and/or update of simulation operational guides, which describes how to perform various functions as a simulation operator, and the simulation software configuration database, which documents the versions of the various software components of the simulation. Support may include simulation operation for developmental, production support services, and training platforms.

3.5.2 The contractor shall support the development, modernization, and execution of desktop (i.e., batchmode) simulation runs. The contractor shall support the development and modification of settings files, facility files, scripts and macros necessary to perform multiple runs repeatedly. The contractor may also support the analysis of such runs, as driven by customer requirements. Support may include execution for developmental, production support services, and training platforms.

3.6 Flight Test Data Analysis

The contractor shall support aircraft flight test data analysis, as follows:

3.6.1 Flight Test Data Instrumentation Corrections

The contractor shall support analysis of flight test data to verify kinematic consistency of the aircraft sensors and determine frequency response limitations of the onboard instrumentation during developmental and in-production processes. Contractor shall support the application of system identification methodology to the flight test data for purposes of verifying kinematic consistency.

The contractor shall support the administration of recommendations for the correction of any instrumentation system deficiencies and/or those pertaining to flight test maneuvers developed to evaluate the adequacy of the instrumentation system. The contractor shall support the presentation of information required to correct instrumentation system deficiencies and new instrumentation system development plans/recommendations. Corrections may be required in support of developmental, production support services, and training platforms.

3.6.2 System Identification

The contractor shall support the use of system identification methods to determine simulation model structure and parameter estimates for complex non-linear aerodynamic, engine, flight control, and other aircraft vehicle and system models during developmental and in-production processes. The contractor shall support the review of available flight test data for suitability of System Identification analysis. If necessary, the contractor shall support the issuance of a recommended test program structure matrix and the suggestion of flight test maneuvers to be used to enhance the validity of the aerodynamic and/or propulsion system databases. The contractor shall support the assessment of flight test data and the identification of maneuvers suitable for system identification analysis. The contractor shall support the conversion of the flight test data to a format suitable for use with system identification analysis software and identify models and parameters. Analysis may be required in support of developmental, production support services, and training platforms.

3.7 Flight Control System Support

3.7.1 The contractor shall support Flight Controls Systems analysis. The contractor shall support the analysis of software development and life cycle support documentation and test requirements, and support the administration of recommendations and/or modifications to ensure adequacy/currency of software support documentation and test plans, as well as support flight incident, engineering investigation and software deficiency data. Analysis may be required in support of developmental, production support services, and training platforms.

3.7.2 The contractor shall support reviews and evaluations of flight control system software documentation such as plans, modifications, requirements, design specifications and test procedures.

The contractor shall provide evaluations and recommendations on incidents and other fleet support issues encompassing flight control system software. Reviews and evaluations may be required in support of developmental, production support services, and training platforms.

3.8 Incident Investigation

3.8.1 The contractor shall support aircraft incident, accident, and mishap investigations to include developing model updates and/or rework for recreating the failure mode in a simulation. The contractor shall provide support for producing/generating visualization of the flight path, pilot controls, and cockpit displays by driving visualization software (e.g., NAVAIR CasVisuals) with actual aircraft data or other provided data. Support may be required in support of developmental, production, or in-service platforms.

3.9 Training Systems Development Support

3.9.1 The contractor shall support the development and modifications of fixed and rotary wing trainer software and hardware including airframe models, avionics models, interfaces and tools, software patches, cockpits, prototypes, visual systems and motion bases. Software will be written in Fortran, C/C++, or other languages as specified by the Integrated Product Team (IPT). Development may be in support of prototype or fleet training aircraft simulators or to modify existing simulators.

3.9.2 The contractor shall provide support in the evaluation of deficiencies of trainer software using

Trainer Deficiency reports and make recommendations for their resolution. Evaluations may be in support of prototype or fleet training aircraft simulators or to modify existing simulators.

3.9.3 The contractor shall support training device acceptance testing. The contractor shall support the coordination with NAVAIR test engineers and test pilots to certify the device for instrument flight, and provide test support by collecting, reducing, and publishing trainer test data in required formats.

Acceptance testing may be in support of prototype or fleet training aircraft simulators or to modify existing simulators.

3.10 UAVs and UASs (PB)

3.10.1 The contractor shall support the development, integration, testing, sustainment, and modification of UAV software and hardware including, but not limited to the following: aerodynamic models, avionics simulation models, Tactical Control Stations (TCS), data collection, developing test plans, presentation & analysis tools, tactical and other mission capable simulation models, database development and manipulation tools, and standard airborne computer modifications, patches and tools, airframes and cockpits. Software shall be written in Fortran, C/C++, MATLAB/Simulink or other languages as specified by the platform Integrated Product Team (IPT).

3.10.2 The contractor shall support the development and operation of systems that can be used to support the integration of DoD UAS into the National Airspace.

3.11 Project Management, System Engineering and Management Analyst Support

3.11.1 The contractor shall provide support for project management functions as required for the department and for Naval acquisition programs. The contractor shall provide support for execution of projects or programs by defining and assigning tasking, developing schedules, and executing to project/program milestones and budget. Efforts may be in support of developmental, production, or in-service platforms.

3.11.2 The contractor shall provide system engineering support. The contractor shall provide technical analysis, evaluation, and reports as required to support the preparation department or program documentation and technical management plans. The contractor shall support the development of department or program briefings. The contractor shall support technical reviews, including support for planning and preparing for the review, conducting the review, and performing follow-up actions to close out the review. Efforts may be in support of developmental, production, in-service, or Foreign Military Sales (FMS) platforms.

3.11.3 The contractor shall provide management analyst support as required for the department and for

Naval acquisition programs. The contractor shall provide support to administrative, business and financial management activities. The contractor shall provide project management and/or accounting support to the department or program.

4.0 ANTICIPATED APPROPRIATIONS

SOW

Para.

Description

Research

Develop-ment

Procure-ment

Operatio ns &

Mainten-ance

Foreign

Military

Sales

Working

Capital

Fund

3.1 Modeling of Aircraft and UAVs for

use in Sims

X X X

3.1.1 Modeling of Air Vehicles for use

in Simulations

X X X

3.1.2 Pilot Modeling X X X

3.1.3 Simulation Verification and

Validation

X X X

3.2 CASTLE Support X X X

3.2.1 CASTLE Code Development X X X

3.2.2 CasView Development X X X

3.3 GPWS/TAWS/CAS/MCAC X X X

3.3.1 GPWS/TAWS/CAS/MCAC

Solutions

X X X

3.3.2 UAS Sense-and-Avoid X X X

3.4 Lab Integration Support X X

3.4.1 Lab Environment Integration X X

3.4.2 Lab-driven Updates X X

3.4.3 Lab Hardware Integration X X

3.5 Simulation Execution X X

3.5.1 Pilot-in-the Loop Operation X X

3.5.2 Desktop Sim Execution X X

3.6 Flight Test Data Analysis X X

3.6.1 Flight Test Data Instrumentation

Corrections

X X

3.6.2 System Identification X X

3.7 Flight Control System Support X X

3.7.1 Flight Controls Systems Analysis X X

3.7.2 FCS Software Documentation

Review

X X

3.8 Incident Investigation X X X

3.8.1 Incident, Accident, Mishap

Investigation Support

X X X

3.9 Training Systems Development

Support

X X

3.9.1 Training Systems Development X X

3.9.2 Evaluation of Deficiencies X X

3.9.3 Training Device Acceptance

Testing

X X

3.10 UAV and Unmanned Aerial

Systems (UAS) Support

X

3.10.1 UAV Software and Hardware

Support

X

3.10.2 UAS into National Airspace X

3.11 Project Management, Systems

Engineering and Management

Analyst Support

X X X X X

3.11.1 Project Management Support X X X X

3.11.2 System Engineering Support X X X

3.11.3 Management Analyst Support X

5.0 TRAVEL, MATERIAL, AND ACCESS TO SPACES

5.1 Travel

In support of this contract, the contractor will, on occasion, be required to travel to other Navy, contractor or

DoD facilities, other government agency offices (e.g. Federal Aviation Administration, NASA, test ranges, operational activities, project / program offices, and intelligence & support activities), simulation conferences, seminars, and training classes. The contractor shall travel, as required, during the performance of this contract.

The Government shall reimburse the contractor for allowable travel costs, exclusive of fee, incurred by the contractor in performance of the contract in accordance with FAR Subpart 31.2 and with rules set forth for temporary duty travel in the Department of Defense Joint Travel Regulations, Volume II, for civilian personnel.

Travel and subsistence are authorized for travel beyond a 50-mile radius of the contractor's office whenever a task assignment requires work to be accomplished at a temporary alternate work site. Travel other than local travel must receive prior written authorization by the Contracting Officer’s Representative (COR). The contractor is responsible for making all travel arrangements for its personnel. Contractor required access to

Government owned facilities will be authorized with the proper clearances and visit requests. The costs associated with obtaining passports for contractor personnel shall not be billed as a direct charge to this contract. The Government shall reimburse the contractor for travel expenses incurred in accordance with

NAVAIR clause 5252.232-9509 including applicable indirect burdens (general and administrative, etc.), excluding profit or fee. Mission requirements for specific programs occasionally require travel to offsite facilities. Those anticipated travel locations include, but are not limited to: San Diego, CA, Philadelphia, PA, Hampton, VA, Orlando, FL, Rancho Bernardo, CA, and Seattle, WA.

5.2 Material

The contractor shall only provide incidental material as necessary to support the tasking. Any Information

Technology (IT) material purchased shall have prior IT approval in accordance with the Clinger-Cohen Act of

1996. The contractor shall purchase material, as required, during the performance of this contract. The contractor shall obtain approval from the Contracting Officer’s Representative (COR) at the individual task order level prior to the purchase of any material. All material purchased by the contractor under this item becomes the property of the Federal Government. The Government shall reimburse the contractor for allowable material costs, exclusive of fee, incurred by the contractor in performance of the contract in accordance with

NAVAIR clause 5252.242-9515 Restriction on Direct Charging of Material (NAVAIR)(July 1998).

5.3 Access to Spaces

In general, access to MFS, other laboratory spaces, equipment and computer facilities will be available to the contractor on a not-to-interfere basis in supporting the requirements of the SOW. During integration tests, the contractor shall schedule for access to laboratories as required.

6.0 GOVERNMENT FURNISHED PROPERTY (GFP)

The Government will provide all NMCI services; to include IT related hardware, software, and support, necessary for the performance of this contract/order. Coordination of these services shall be conducted through the COR. The Government will also provide workspace accommodations for on-site support and access to

Government RDT&E networks as necessary.

7.0 WORKPLACE AND SCHEDULE

7.1 Compressed Work Schedule (CWS)

7.1.1 The contractor shall provide the required services and staffing coverage during normal working hours (NWHs). NWHs are usually 8.5 hours (including a 30-minute lunch break), from 0730-1600 each

Monday through Friday (except on the legal holidays specified elsewhere). Some supported

Government offices have flexibility to start as early as 0600/0630 and end as late as 1800, Monday through Friday. Services and staffing shall be provided for at least 8 hours per day (during the 8.5 hour workday which includes the 30-minute lunch break).

7.1.2 Government employees are allowed to voluntarily work a "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.

7.1.3 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.

7.1.4 The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other. The contractor awarded this contract, with agreement by the COR, may allow its employees to work a CWS schedule. The contractor is advised that Friday is the only day allowed as the weekday not worked by employees on a CWS schedule.

7.1.5 Any contractor that chooses to allow its employees to work a CWS schedule in support of this contract agrees that 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.

7.1.6 All contractors shall comply with the requirements of the Fair Labor Standards Act and particularly with Section 7 regarding compensatory overtime.

7.1.7 The CWS schedule shall not prevent contractor employees from providing necessary staffing and services coverage when required by the Government facility.

7.2 Overtime

7.2.1 The contractor may be required to provide labor hours in excess of 40 hours per week to include holidays, weekends and/or irregular times and shifts based upon travel and OCONUS requirements, operations or emergencies. The COR may authorize use of pre-approved overtime in accordance with

Federal Acquisition Regulations (FAR) clause 52.222-2 as necessary at the basic and task order level.

8.0 LABOR QUALIFICATIONS

The contractor is required to provide personnel having professional and technical experience, to ensure accomplishment of the tasks specified in this SOW. All personnel (both key and non-key) shall meet and maintain the corresponding labor category qualifications throughout the performance of the contract. Key labor categories are those categories for which the contractor agrees to assign personnel for performance of this contract who have been approved in writing by the Government in accordance with NAVAIR clause 5252.237-

9501– Addition or Substitution of Key Personnel (Services). The Key labor categories are identified below. The contractor shall agree that during the term of this contract, no key personnel will be substituted unless necessitated by compelling reasons in accordance with NAVAIR clause 5252.237-9501. The specified experience included as part of the required qualifications shall have been obtained in the fields of endeavor indicated, and unless stated otherwise experience must have been obtained within the last ten years. The contractor is encouraged to strive for technical experience beyond these qualifications.

The contractor must be capable of obtaining and maintaining a secret security clearance during the performance of the contract. In addition, a current secret security clearance is required upon issuance of specific orders and during the performance on the individual task order SOW. Experience must be relevant to the functional area.

Key Labor Categories

Senior Engineer/Scientist (KEY)*

Functional Description:

Leads the execution of complex tasks. Applies and integrates engineering principles to investigate, analyze, plan, design, develop, implement, test or evaluate military weapons systems. Reviews and prepares engineering and technical analyses, reports, change proposals, and other technical documentation. Applies engineering experience to perform functions such as system integration, configuration management, quality assurance testing, or acquisition and resource management. Analyzes designs, develops, implements, tests, or evaluates software related to engineering or functional requirements of military weapons systems, associated support systems.

Education:

MS or MA degree in Engineering, Logistics, Science or aerospace/aeronautical engineering, electrical engineering, mechanical engineering, or computer science. ALLOWABLE SUBSTITUTION: A BS or BA degree and an additional four (4) years of experience can be substituted for an MS or MA degree.

Experience:

At least ten (10) years of experience in an engineering position in one of the technical disciplines below, three

(3) of which must be directly related to Naval systems. Demonstrated knowledge in the area of flight simulation, flight mechanics, guidance and control expertise.

Non-Key Labor Categories

Manager

Functional Description:

Acts as the overall lead, manager and administrator for the contracted effort in support of a Navy program or project. Serves as the primary interface and point of contact with Government program authorities and representatives on technical and program/project issues. Oversees contractor personnel program/project operations by developing procedures, planning and directing execution of the technical, programming, maintenance and administrative support effort and monitoring and reporting progress. Manages acquisition and employment of program/project resources and controls financial and administrative aspects of the program/project with respect to contract requirements.

Education:

BS or BA degree. An AS or AA degree and an additional four (4) years of experience may be substituted for a

BA/BS or an additional eight (8) years of experience (without Associates degree) may be substituted for a

BA/BS.

At least six (6) years of professional experience in the Defense acquisition, and three (3) years of experience in support of Navy Acquisition management. Knowledgeable of acquisition policies and procedures.

Demonstrated knowledge of and experience with the requirements of the DOD 5000 series. Demonstrated ability to work with large and diverse teams and the ability to effectively provide guidance, direction, and supervision in all areas of contracted effort such as program management, systems engineering, major system acquisitions, and financial management.

Journey Level Engineer/Scientist

Applies engineering principles to investigate, analyze, plan, design, develop, implement, test, or evaluate military weapons systems. Reviews and prepares engineering and technical analyses, reports, change proposals, and other technical documentation. Applies engineering experience to perform functions such as system integration, configuration management, quality assurance testing, or acquisition and resource management.

Analyzes, designs, develops, implements, tests, or evaluates software, components, or systems related to engineering or functional requirements of military weapons systems, associated support systems, or management information systems.

Education:

BS or BA degree in aerospace/aeronautical engineering, electrical engineering, mechanical engineering, computer science or mathematics.

At least three (3) years of experience in the area of flight simulation, flight mechanics, or guidance and control.

Must have experience with programming.

Junior Engineer/Scientist

Applies engineering principles to investigate, analyze, plan, design, develop, implement, test, or evaluate military weapons systems. Reviews and prepares engineering and technical analyses, reports, change proposals, and other technical documentation. Applies engineering experience to perform functions such as system integration, configuration management, quality assurance testing, or acquisition and resource management.

Analyzes, designs, develops, implements, tests, or evaluates software, components, or systems related to engineering or functional requirements of military weapons systems, associated support systems, or management information systems.

BS or BA degree in aerospace/aeronautical engineering, mechanical engineering, electrical engineering, engineering mechanics, computer science or mathematics.

None required.

Subject Matter Expert

Applies expertise to support program development, project execution, business and technical operation, strategic initiatives, workforce development, or as required to support technical and organizational tasks.

Requires a High School diploma or GED; Technical training in engineering, physics, mathematics, or computer science.

At least ten (10) years of hands-on experience in one of the following areas: System Requirements, Operational

Requirements, or Test & Evaluation. Recognized expert who has demonstrated industry and public service leadership in aeronautics, aviation, or Naval Aviation weapon systems development/acquisition.

Senior Computer Scientist

Applies knowledge of computer science concepts and techniques, mathematics, and methods of statistical analysis to develop and apply automated solutions to engineering, scientific, or business data acquisition and management problems. Uses mathematical, statistical, and scientific logic to identify conceptual or theoretical solutions to problems of automated data processing (ADP) hardware or software systems design and operations.

Analyzes and formulates architectural and functional specifications, interfaces, and data structures. Researches applications for ADP hardware, software, and operating systems. Writes, modifies, and adapts computer programs in machine level, assembly, and third or fourth generation programming languages. May act as team leader or supervisor, developing project plans, guidelines, or controls, and directing the work of other computer scientists, specialists, and technicians.

BS or BA degree in Computer Science.

At least three (3) years of computer science experience. At least one (1) year of the foregoing experience shall have been as a team leader or supervisor. At least one (1) year of the foregoing experience shall have consisted of performing computer scientist functions, including the design, development, testing and documentation of software in a real-time simulation architecture such as flight training devices. Experience in FORTRAN and

C/C++ languages; Windows, Linux, and UNIX operation systems desired.

Computer Specialist

Applies knowledge of computer science principles, information management principles, ADP functions, hardware and software systems structures and operation, and computer programming languages and techniques to solve automation problems. Applies scientific, engineering or business objects by writing, modifying, or adapting computer programs in machine level, assembly and third or fourth generation programming languages.

Interfaces with and uses minicomputer and mainframe computer systems in addressing project objectives. Uses standard or conventional approaches, methods, and techniques to define, plan, organize, design, develop, modify, test and integrate database or data processing systems, computer hardware systems and simulation models. Assists in formulating architectural design, functional specifications, interfaces and documentation of hardware or software systems. Uses detailed specification and adapts standardized techniques, methods, criteria and precedents to develop or modify portions of a system or program. Responsible for segments or phases of broader, more complex projects.

BS or BA degree in Computer Science, Information Systems Management, Mathematics, Operations Research, Statistics, or Engineering.

At least three (3) years of recent relevant experience. At least one (1) year of the total experience shall have consisted of performing computer specialist functions in a simulation laboratory environment.

Management Analyst I

Provides financial and/or accounting support to the activity Accounting Department, Budget Department, Financial Systems Department or Business Operations Department, and other organization support elements and other activities. Assists in a variety of administrative, business and financial management activities, including, but not limited to cost and financial data analysis, workload forecasting and planning, reengineering initiatives, statistics and metrics, impact analysis of financial, acquisition and other regulatory changes, coordination and review of command-wide activities and preparation of budget and financial reports. Utilizes

Navy ERP to extract data necessary in performing management and financial analysis and report preparation.

Requires BS or BA degree in Business or related field. ALLOWABLE SUBSTITUTION: An additional six

(6) years of experience can be substituted for a BS or BA degree.

At least four (4) years in Management Analyst position.

Project Support Specialist

Performs basic activities in support of program functions such as budgeting, auditing, forecasting funding expenditures. Collects and reviews program financial data from various databases and other sources. Creates, maintains, and updates program databases and spreadsheets, and generates various reports as required.

Performs basic financial analysis of program areas as assigned. Prepares reports and presentation material.

Maintains appropriate records and documentation. Supports assigned managers in managing, tracking, monitoring, and reporting financial data as required. Ensures compliance with internal policies and procedures as well as DAR, FAR, and other government policies and regulations. May act as program coordinator following up on pending details and coordinating program meetings. Participates in special projects as required.

High School diploma or GED.

At least one (1) year of related experience in financial, accounting or business analysis.

Senior Systems Engineer

Has programmatic or technical leadership roles in an organization identifying, formulating, designing and/or testing practical solutions to engineering problems and guide the engineering development of modern complex systems; and to employ systems engineering methods and tools in the development of advanced complex systems, and when appropriate, conduct research in applied systems engineering to advance the field.

MS or MA degree in Engineering, Logistics, Science. ALLOWABLE SUBSTITUTION: A BS or BA degree and an additional four (4) years of experience can be substituted for an MS or MA degree.

At least ten (10) years of experience in an engineering position, three (3) of which must be directly related to

Naval systems. Demonstrated knowledge in area of engineering expertise.

9.0 DELIVERABLES

9.1 Program Progress Report

The contractor shall provide a program progress report listing the monthly accomplishments and upcoming objectives for each project and/or task order. The Contractor shall submit the document to the Government in accordance with Contract Data Requirement List (CDRL), Exhibit A, DD Form 1423, item CDRL A001.

9.2 Performance and Cost Report

The contractor shall provide a performance and cost report which will include the project status, man hours expended, labor, material, travel, and other costs. The reporting period will be in conjunction with billing period of each invoice. The report will be subdivided by each assigned task order and will list the total cost of the specific project, the amount funded (by CLIN), the amount expended (by CLIN and labor category), and the total amount remaining to be expended. The report will detail the monthly labor hours and charges per each individual on that project, and the total material items (and their cost) will be listed. The Contractor shall submit the document to the Government for approval in accordance with CDRL A002.

9.3 Technical Report

The contractor shall provide a technical report if and/or when they are tasked to complete work under SOW paragraph 3.10 and writing a technical report is a normal part of completing a task, or if the contractor is tasked to write a specific technical report. The Contractor shall submit the document to the Government for approval in accordance with CDRL A003.

9.4 Operations Security (OPSEC) Plan

9.4.1 The contractor shall provide Operations Security (OPSEC) protection for all classified information (as defined by FAR 4.401) and sensitive information (as defined by Section 3(d)(4) of PL 100-235 (101 Stat

1727)), pursuant to the National Security Decision Directive 298 of 22 January 1988 and Defense Federal

Acquisition Regulations Supplement (DFARS) clause 252.239-7016. In order to meet this requirement, the contractor shall develop, implement and maintain a facility level OPSEC program to protect classified and sensitive information to be used at a contractor's and subcontractor's facilities during the performance of this contract.

9.4.2 The OPSEC Plan will protect classified and 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’s OPSEC program is to be described in a facility level OPSEC planning document. The Contractor will submit one OPSEC Plan, applicable collectively to this Agreement and to each delivery order placed hereunder. The Contractor shall submit the document to the Government for approval in accordance with CDRL A004.

9.4.3 The Contractor is responsible for subcontractor implementation of the OPSEC program requirements for this contract.

9.5 Non-Disclosure Agreement (NDA) / Organizational Conflict of Interest (OCI)

9.5.1 In the performance of the contract, the Contractor may have access to non-public proprietary information. The Contractor shall require that any employee performing services under the contract execute a

NDA satisfactory to the Procuring Contracting Officer (PCO). The NDA shall acknowledge the Contractor and employee’s duties with respect to non-public information and promise to comply with those obligations.

9.5.1.1 The Contractor shall provide the Government an executed “Company” non-disclosure agreement (for prime subcontractor companies) in accordance with CDRL A005. An attached statement found included with this CDRL shall be signed and accompany CDRL A005 upon submission.

9.5.1.2 The Contractor shall provide the Government an executed “Individual” non-disclosure agreement for each employee in accordance with CDRL A006. An attached statement found included with this CDRL shall be signed by each employee and accompany CDRL A006 upon submission.

9.5.2 Consistent with the terms and conditions of NAVAIR clause 5252.209-9510(e)(5) Organizational

Conflicts of Interest (Services), with respect to proprietary data of third parties, and DFARS clause 252.227-

7025 Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive

Legends, with respect to technical data, the Contractor shall not use, modify, reproduce, release, perform, display, and disclose any nonpublic information provided to or obtained by the Contractor in the course of performing the contract for other than Government purposes, and shall not do so for any commercial or personal purpose. In the event that the Contractor knows of or identifies that it has a commercial interest in the subject matter of any proposed or on-going agreement with regard to the services to be performed, the Contractor shall consider such interest a potential conflict of interest (Services), and promptly disclose it to the Contracting

Officer in Attachment 6, Organization Conflict of Interest List.

9.5.2.1 The contractor shall be responsible to comply with the NAVAIR clause 5252.209-9510, to ensure that no unfair competitive advantage develops over other parties and that no biases occur because of its current or planned interests pertaining to the work under this contract. The contractor shall ensure that each subcontractor performing work relative to this contract are also in compliance with NAVAIR clause 5252.209-9510 and that its subcontracts affected by the provisions of the clause include the necessary language contained in it.

9.5.2.2 The contractor and its subcontractor(s) shall comply with NAVAIR clause 5252.209-9510 during all anticipated travel requirements listed under SOW paragraph 5.1, as well as any additional locations added during the 5-year ordering period per the individual task order SOW.

10.0 INFORMATION TECHNOLOGY (IT)

The contractor may be required to access Government IT Systems. Contractor personnel requiring access to

Government IT Systems shall comply with NAVAIR clause 5252.204-9505.

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 Task order without a NAVAIR Command Information Officer (CIO) signed "IT" approval.

It is the Government's responsibility to ensure that any "IT" procurement (hardware/hardware maintenance, software/software maintenance, support services, web services, telecommunications, etc.) procured by the

Contractor under the scope of this Contract/Task Order that contains "IT" meet the following requirements:

10.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 IT in weapons and weapons system programs. The law provides authority to the agency’s Chief Information Officer (CIO) to manage IT resources effectively. The authority to grant compliance with CCA and approve the Information

Assurance (IA) strategy depends on the Acquisition Category (ACAT).

a. DoDD Number 5000.01 “The Defense Acquisition System,” May 12, 2003, Certified Currentas of

November 20, 2007

b. DoDI 5000.02, “Operation of the Defense Acquisition System,” December 8, 2008

c. OSD Memo, “Clinger-Cohen Act Compliance Policy,” Mar 8 2002

d. SECNAVINST 5000.2D, “Implementation and Operation of the Defense Acquisition System and the

Joint Capabilities Integration and Development System,” October 16, 2008

10.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)/ NAVAIR Functional Area Manager

(FAM) Policies and Guidance, Network and Server Registration, and Web Enablement mandates."

10.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…