N00421-18-R-0035_DRAFT_RFP.docx

.N0042118R0035

Section A - Solicitation/Contract Form

GENERAL INFORMATION

Contract Specialist:

Greg Tollefsen

(301) 757-1584 greg.tollefsen@navy.mil

Contracting Officer:

Christopher Pennini

(301) 757-5980 Christopher.Pennini@navy.mil

CONTRACTING OFFICER REPRESENTATIVE: TO BE DETERMINED AT CONTRACT AWARD

(1) This solicitation is reserved for competition among small business concerns in accordance with FAR 52.219-8 Total Small Business Set-Aside. The resultant award will be a Single Award Indefinite Delivery/Indefinite Quantity contract.

(2) The Product/Service Code (PSC) for this procurement is AC14. The NAICS code is 541715 and the small business size standard is 1,500 employees.

(3) This contract includes Cost-Plus-Fixed-Fee (CPFF) contract line item numbers (CLINs) for labor and cost reimbursable (no fee) CLINs for Other Direct Costs (travel and material).

(4) This contract is for an ordering period of five (5) years.

(5) The contractor will not be authorized to access any classified information until a final DD Form 254 is incorporated as an Attachment to this contract.

(6) The offeror’s proposal may be incorporated into the contract upon award.

(7) Task orders may be issued under this single award Indefinite Delivery Indefinite Quantity (IDIQ) contract. NAVAIR clause 5252.211-9503 Level of Effort (Cost Reimbursement) (NAVAIR) (DEC 2012) will be included in applicable task orders.

Section B - Supplies or Services and Prices

CLIN PRICING

(1) CLINs 0002 through 0006 and 0008 through 0012 are not separately priced (NSP) at the IDIQ level, they will be priced when utilized at the task order level.

(2) All labor ceiling, inclusive of cost and fee, for CPFF CLINs 0002 through 0006 (NSP CLINs) is included in the overall ceiling for CLIN 0001.

(3) All other direct cost ceiling for COST CLINs 0008 through 0012 (NSP CLINs) is included in the overall ceiling for CLIN 0007.

Labor Ceiling for CLINs 0002-0006

CPFF

Cost Plus Fixed Fee (CPFF) Labor Ceiling for CLINs 0002-0006.

FOB: Destination

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNDEFINED

Labor- RDT&E Funding

Research Development Test & Evaluation (RDT&E) Labor in accordance with paragraphs 3.3.1 - 3.3.5.4 in the SOW. Not Separately Priced from CLIN 0001.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNDEFINED

Labor- O&M Funding

Operations and Maintenance (O&M) Labor in accordance with paragraphs 3.3.1 - 3.3.5.2 in the SOW. Not Separately Priced from CLIN 0001.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNDEFINED

Labor- NWCF Funding

Navy Working Capital Fund (NWCF) Labor in accordance with paragraphs 3.3.1 - 3.3.5.2 in the SOW. Not Separately Priced from CLIN 0001.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNDEFINED

Labor- Procurement Funding

Procurement Labor in accordance with paragraphs 3.3.1 - 3.3.5.2 in the SOW. Not Separately Priced from CLIN 0001.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNDEFINED

Labor- FMS Funding

Foreign Military Sales (FMS) Labor in accordance with paragraphs 3.3.1 - 3.3.5.2 in the SOW. Not Separately Priced from CLIN 0001.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

ODC Ceiling for CLINs 0008-0012

COST

Other Direct Cost (ODCs) Ceiling for CLINs 0008-0012 in accordance with paragraph 3.1.5 in the SOW.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

MAX COST

UNDEFINED

ODC- RDT&E Funding

Research Development Test & Evaluation (RDT&E) ODC in accordance with paragraphs 3.1.5 in the SOW. Not Separately Priced from CLIN 0007.

MAX COST

UNDEFINED

ODC- O&M Funding

Operations and Maintenance (O&M) ODC in accordance with paragraphs 3.1.5 in the SOW. Not Separately Priced from CLIN 0007.

MAX COST

UNDEFINED

ODC- NWCF Funding

Navy Working Capital Fund (NWCF) ODC in accordance with paragraphs 3.1.5 in the SOW. Not Separately Priced from CLIN 0007.

MAX COST

UNDEFINED

ODC- Procurement Funding

Procurement ODC in accordance with paragraphs 3.1.5 in the SOW. Not Separately Priced from CLIN 0007.

MAX COST

UNDEFINED

ODC- FMS Funding

Foreign Military Sales (FMS) - ODC in accordance with paragraphs 3.1.5 in the SOW. Not Separately Priced from CLIN 0007.

MAX COST

UNDEFINED

Technical Data

Technical Data in accordance with Exhibit A. Not Separately Priced.

NET AMT

CLAUSES INCORPORATED BY FULL TEXT

TO BE SPECIFIED IN INDIVIDUAL TASK ORDER

Section C - Descriptions and Specifications

STATEMENT OF WORK

1.0 Scope

The Integrated Battlespace Simulation and Test (IBST) Department, NAWCAD 5.4, is the Naval Air Systems Command’s (NAVAIR) center of excellence for modeling and simulation of the Battlespace environment. The Simulation Division (SD), NAWCAD 5.4.3, is one of five divisions within IBST and is responsible for simulation expertise and products for naval aviation systems and the Battlespace environment within which they operate. Simulation is used throughout the acquisition lifecycle to reduce risk and improve the quality of naval aviation systems.

The Simulation Division operates a number of laboratories, which are for activities that include research and development of requirements for aviation systems, supporting system development, providing developmental and operational flight test support, and providing life-cycle operational support to include system enhancement, procedure refinement, and accident investigations. Current Simulation Division laboratories include:

· Manned Flight Simulator (MFS) facility,

· E-2 Systems Test and Evaluation Lab (ESTEL),

· P-8 Systems Integration Lab (PAXSIL),

· Unmanned Air System (UAS) Integration Lab,

· Warfare Simulation Lab,

· Executive Helicopter Systems Integration Lab (SIL), and

· H-60 Data Reduction Lab.

These laboratories are also used to research, design, implement, deploy simulation initiatives that include common architectures and interfaces, cross-platform communications, Live Virtual Constructive (LVC) events, air system stimulation, simulation Verification, Validation and Accreditation (VV&A) activities and hardware in the loop RDT&E activities. Simulation Division laboratories interact with and provide simulation support for other laboratories, programs, and activities as required to meet customer requirements.

The scope for this contract is for research, design, development, integration, and associated engineering in support of Simulation Division laboratories, the projects supported by these laboratories, simulation based initiatives, and interconnectivity and support with other laboratories and activities.

2.0 Applicable Documents

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

2.1 Department of Defense Specifications

2.2 Department of Defense Standards

2.3 Simulation Division (5.4.3) Standards and Procedures

2.4 Industry Standards and Procedures

2.4.1

3.0 Requirements

3.1 General Requirements

3.1.1 Compatibility

The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government IT environment through the security classification of Unclassified. The current operating environment required for this contract includes:

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

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

3.1.2 Work Location and Facilities.

3.1.2.1 Work Location: It is anticipated that a minimum of 78% will be performed at Government site and up to 22% may be required to be performed at the contractor site. Government site is Patuxent River, Maryland. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks. Offsite contractor spaces shall be within 20 miles driving distance to Patuxent River NAS.

3.1.2.2 Meeting and conference room support: The Contractor shall have the capability to conduct meetings at the unclassified level. The meetings shall be capable of accommodating a minimum of 10 persons and have teleconference and videoconference capability (non-Government Furnished Equipment). The contractor shall be capable of projecting presentations during these meetings via projectors and/or TV displays, telephone(s); and computer(s) with compatible software as required in Paragraph 3.1.1. This support shall be provided at the Contractor’s location.

3.1.2.3 Government Furnished Property (GFP): A listing of Government Furnished Property to be made available to the Contractor at contractor facilities can be found in Attachment J5. The Government shall provide Unclassified Research Development Test & Evaluation (RDT&E) computers and computer network connectivity for off-site contractors providing direct full time technical support that requires RDT&E network access.

3.1.3 Contract Status Reporting.

The Contractor shall provide the following documentation. To be further detailed at the Task Order level.

3.1.3.1 Monthly Program Financial Summary. The Contractor shall provide a monthly financial summary report in accordance with Contract Data Requirements List (CDRL) A001. The monthly financial summary provides an overview of the status of the entire contracted effort.

3.1.3.2 Monthly Project Financial Summary. The Contractor shall provide a monthly project financial summary report in accordance with CDRL A002. Monthly project financial summaries provide detailed financial information for individual projects supported by the contracted effort.

3.1.3.3 Monthly Progress Report.

The Contractor shall provide a monthly progress report in accordance with CDRL A003. This report shall list the monthly accomplishments and upcoming project objectives for each project. Trips and significant events shall also be addressed.

3.1.3.4 Other Reporting. The Contractor may be required to provide additional reporting, documentation, and schedules in accordance with deliverable requirements (CDRLs) incorporated at the task order level. Reporting shall be in sufficient detail and quality to meet the requirement established in the individual task orders and shall be in compliance with the standards and guidelines in Section 3.0. Other reporting requirements may include, but are not limited to:

· Technical reports, documentation, requirements, data, evaluations and analysis.

· Software source code and executables.

· Manufacturing drawings, data, lists, procedures, and schematics.

· Maintenance requirements, guidelines, schedules, procedures, instructions, and corrective actions.

· Agendas, minutes and presentation materials for meetings, presentations, and conferences.

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

3.1.4.1 Work schedule: The Contractor shall provide the required services and staffing coverage during normal working hours. Core hours are 0900 -1500, Monday through Friday (except on the legal holidays specified in paragraph 3.1.4.3). Some supported Government offices have flexibility to start as early as 0500/0530 and end as late as 1900, Monday through Friday.

3.1.4.2 Compressed Work Schedule (CWS): If the Contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage as required by the Government to the Alternate Contracting Officer’s Representative (ACOR)/Contracting Officer’s Representative (COR).

3.1.4.3 Holidays: The Government observes the following holidays:

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

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

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

3.1.4.5 Overtime: Overtime as defined in this contract refers to hours worked by a contractor employee in excess of the employee’s normal work week. When support requirements outside of normal working hours occur, the Contractor shall ensure qualified personnel are available to support these requirements through the use of overtime. Overtime is authorized under this contract to the extent specified in individual task orders provided COR approval is obtained in advance of each occurrence. The COR may provide concurrence for overtime on a task, event, program, project, or general function basis. The total cost for overtime over the life of the contract cannot exceed the amount specified in clause 52.222-2 Payment for Overtime Premiums unless first approved in writing by the Chief of the Contracting Office.

3.1.5 Other Direct Costs.

3.1.5.1 Travel: Travel will be allowable only when it is essential to the performance of tasks detailed in Section 3.3. Reimbursement for travel performed shall be in accordance with NAVAIR Clause 5252.232-9509 Travel Approval and Reimbursement Procedures. Invoiced travel costs may include general and administrative expenses, but shall not include profit. Temporary travel to other locations in support of program tasking is required. In accordance with NAVAIR Clause 5252.232-9509 Travel Approval and Reimbursement Procedures, travel within a 50-mile driving distance of the Contractor’s regular worksite is considered the Contractor’s official station and therefore not subject to reimbursement. Temporary travel locations may include Continental United States (CONUS) and Outside Continental United States (OCONUS) locations. Travel authorization requests shall be submitted for COR approval 30 days in advance of required travel, when possible, but no less than 15 business days prior to travel.

3.1.5.2 Material: Purchase of materials shall be in accordance with NAVAIR Clause 5252.242-9515 (Variation) (JUN 2018), Restriction on the Direct Charging of Material. Invoiced material costs may include general and administrative expenses, but shall not include profit. The costs of general purpose business expenses required for the conduct of the Contractor’s normal business operations are not an allowable direct cost in the performance of this contract. General purpose business expenses include, but are not limited to, the cost for items such as telephones and telephone charges, reproduction machines, word processing equipment, personal computers and other office equipment and office supplies.

3.1.6 Subcontractors.

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

3.1.7 Management of Contractor Personnel.

The Contractor shall supervise its workforce and control the methods by which required tasks are performed. The Contractor shall assign tasks to and prepare work schedules for individual Contractor employees. The Contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services. All direction and clarification on work contained in this SOW shall come from the COR and/or the NAWCAD Contracts Office.

3.2 Security

3.2.1 Citizenship Requirements.

Only U.S. citizens may perform under this contract, unless waived. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

3.2.2 Investigative Requirements:

All Contractor personnel shall maintain a minimum security clearance eligibility of Secret throughout contract performance. Individual task orders may require additional security clearance requirements, depending on the nature of the task to be performed.

All personnel security clearances shall be obtained within 30 days of contract award. Interim clearances are acceptable. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

In accordance with the contract DD Form 254 Contract Security Specification (Attachment J4), the Contractor shall possess and maintain a Top Secret Facility Security Clearance. Individuals requiring Top Secret clearances, as identified in the Government’s labor hour estimate (Section L, paragraph 3.5.2), must be able to perform at the Top Secret level within 30 days of contract award.

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

3.2.3.1 SAAR-N: All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training in accordance with NAVAIR Clause 5252.204-9505. New employees must submit their SAAR-N forms within thirty (30) days before their first day of work. Instructions for processing the SAAR-N forms are available at: http://www.public.navy.mil/surfor/ccsg11/Documents/CCSG11_OPNAV_5239_14SAAR_N.pdf. SAAR-N forms shall be submitted to the Contracting Officer’s Representative (COR), Government Technical Point of Contact (TPOC), or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Associate.

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

3.2.3.3 DD-254: The Contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the Contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled in accordance with the appropriate designation (Controlled Unclassified Information; For Official Use Only; Covered Defense Information). Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the COR of this contract for approval.

3.2.4 Information Security.

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

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

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

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

3.2.5 Operational Security (OPSEC).

The Contractor shall comply with activity OPSEC program instructions, guidance and contribute to organization-level OPSEC efforts. The Contractor shall include OPSEC as part of its ongoing security awareness program and take all required activity OPSEC training. The Contractor shall protect identified critical information, sensitive unclassified information and activities, which, if divulged, could further compromise classified or sensitive information or operations, or degrade the planning and execution of operations performed by the Requiring Office and contractor in support of the mission

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

The Contractor shall develop, implement, and maintain an OPSEC plan (CDRL A004) to protect classified and sensitive information to be used at a contractor's and subcontractor's facilities during the performance of this contract. The Contractor is responsible for subcontractor implementation of the OPSEC program requirements for this contract.

3.2.6 Anti-Terrorism Force Protection and Emergency Management.

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

3.3 Detailed Support Requirement

3.3.1 Development and Engineering Support (CLINs 0002, 0003, 0004, 0005, 0006)

The Contractor shall provide the following support, to be further detailed at the Task Order level:

3.3.1.1 Electrical Engineering. Perform electrical engineering planning, analysis, design, drafting and technical-documentation for the research, development and upgrade of Simulation Division laboratory systems, facilities, projects and equipment. Applications include simulation systems, hardware-in-the-loop racks, and developmental test-benches, and supporting modifications and maintenance. Tasks include, but are not limited to:

· Analysis of aircraft systems to be replicated in a physical and virtual simulation environment.

· Power distribution design.

· System inputs/outputs design.

· Integration of aircraft avionics into hardware-in-the-loop systems.

· Real-time audio and video systems design.

· Real-time digital data networks design and interfacing design.

· Interconnections between systems, laboratories, and facilities worldwide.

3.3.1.2 Mechanical Engineering. Perform mechanical engineering planning, analysis, design, and technical documentation for the research, development and upgrade of Simulation Division laboratory systems, facilities, projects, and equipment. Applications include simulation systems, hardware-in-the-loop racks, and developmental test-benches, and supporting infrastructure modifications and maintenance. Tasks include, but are not limited to:

· Aircraft and aircraft system replication.

· Support structure design.

· Analysis of aircraft structures and systems to be replicated in a physical or virtual simulation environment.

· Control loading and visual display system design and integration.

· Electronic rack design.

· Instructor / operator station design.

· Mobile simulator enclosures integration.

3.3.1.3 Drafting. Develop and maintain mechanical and electrical drawings, bills of material, and related design documentation. Drafting is in accordance with American Society of Mechanical Engineers (ASME) standards ASME Y14 and applicable Simulation Division standards. Develop 3D mechanical models and detailed designs.

3.3.1.4 Air Vehicle Mission System Simulation Engineering. Perform research, design, development, testing, modification and maintenance of laboratory infrastructures, methods, equipment, technologies to support simulation models of air vehicles, mission systems, sensor interactions, and air vehicle sub-systems. Tasks include, but are not limited to:

· Researching and analyzing aircraft mission systems and components to collect the information needed to develop associated modeling and simulation infrastructure, methods, models and tools.

· Research and develop system simulation models using a prescribed program language and/or Matrix Laboratory (MATLAB). Modeling includes, but is not limited to, flight performance characteristics, engine modeling, controls, landing gear, electrical and hydraulic sub-systems, and engine control units.

· Research, design and implement interfaces for equipment, models and systems with other simulation assets and infrastructure, such as shared memory systems, avionics, simulation systems, and distributed simulations and laboratories.

3.3.1.5 Avionics Modeling. Perform research, design, development, testing, modification and maintenance of simulation models of air vehicle avionics, mission systems, and weapons systems. Provide support to interface, integrate and stimulate and test aircraft avionics. Tasks include, but are not limited to:

· Applying expertise on sensors (radar, EO/IR, acoustic), mission computers, electronic support measures (ESM), communication, navigation, identification systems, data links, and weapons systems to the development of simulations.

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

· The contractor shall provide software modeling for models of remote sensing devices, such as Radar, Forward Looking Infrared Radar and Synthetic Aperture Radar.

· Designing and programming avionics models using a prescribed programming language.

· Interface models with simulation components and equipment, including shared memory systems, simulation systems software, distributed simulations interfaces, and data links to aircraft and test equipment.

· Develop prototype simulated displays.

· Develop tools to run, analyze, and test avionics models and related simulation systems.

3.3.1.6 Simulation Systems Software Development. Perform research, design, development, modification, integration, interfacing, testing, operation, and maintenance of real-time simulation and stimulation systems. Tasks include, but are not limited to:

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

· Interfacing to simulation hardware systems including image generators, visual display systems, aural cueing systems, control loading systems, shared memory systems, motion platform and cueing systems, video switchers, operator stations, and networking equipment.

· Developing software to interface, operate, monitor, and test simulation and stimulation systems, such as simulation operator software, control executives, runtime tools, environment controllers, and data bus traffic monitors.

· Developing software for simulation recording, playback, presentation and post-execution analysis.

· Developing interfaces to aircraft systems using military and commercial data bus standards.

· Developing interfaces and tools to support distributed simulations using Distributed Interactive Simulation (DIS), High Level Architecture (HLA), Test-Training Enabling Architecture (TENA) and Battlespace modeling.

· Database development and manipulation tools.

· Software to establish connectivity and interoperability between SD systems and facilities and other live, virtual and constructive systems, labs and facilities.

3.3.1.7 Flight Test Data Analysis and Processing. Design, develop, modify, test, and operate software tools to collect, process, reduce, analyze, format and display air vehicle flight and ground test data. Software operation shall include all steps between collection of raw flight test data and final delivery of data products for test reports.

3.3.1.8 RDT&E Software Development. Perform research, design, development, integration, testing and operation of RDT&E government software efforts for Simulation Division projects. Tasks include, but not limited to:

· Development of software to interface flight test data into simulation and analysis systems.

· Creating software interfaces to RDT&E systems and military hardware.

· Providing support of NAVAIR/DoN software standardization, process and open architecture initiatives.

· Development of software to support NAVAIR RDT&E infrastructure, connectivity, and processes.

· Analysis, evaluation, and testing of software in support of RDT&E programs.

3.3.1.9 Enterprise Software Programming. Develop, maintain, and upgrade enterprise tracking, planning, and management databases, programs and web-based tools to maximize the efficiency of the operation and management of the IBST organization and supported activities. Support includes, but is not limited to:

· Material inventory, tracking, and shipping systems.

· Workforce and workload tracking and analysis software.

· Test asset scheduling systems.

· Workflow tracking tools.

· Assist requirements definition and tracking tools.

· Financial management tools.

3.3.2 Specialized Technical Support (CLINs 0002, 0003, 0004, 0005, 0006)

The Contractor shall:

3.3.2.1 Technical Expertise. Provide subject matter expertise (SME) for a broad range of military matters including air-vehicles, sensors systems (RADAR, SONAR, etc.), weapons systems, communication systems, air-vehicle simulation and training, Live, Virtual and Constructive (LVC) simulations, and aircraft and aircraft system testing, and Modeling and Simulation Verification Validation and Accreditation. Tasks include, but are not limited to:

· Development of technical specifications based on an in-depth knowledge of the fleets operations and requirements.

· Research and analysis of requirements in support of simulation model and scenario development.

· Researching and developing requirements for simulation models and LVC environment scenarios to software developers and/or participating in model development.

· Evaluating and testing simulation models and LVC scenarios.

· Evaluating and analyzing flight test data.

· Interfacing with customers and system operators.

· Supporting, planning, and/or operating simulation and test events in support of test and training objectives.

· Operating model entities in distributed simulation events.

3.3.2.2 Tracking Expertise. Provide tracking engineering and subject matter expertise in support of platform testing, analysis, development, and investigation requirements. Tasks include, but are not limited to:

· Maintaining knowledge of naval aviation tracking mission computer software and algorithms pertinent to the local sensor tracking (LST) design and requirements, Link-16, and CEC functions relevant to tracking performance.

· Support the development of test plans with the development of test objectives, test conditions, and data requirements.

· Providing support for the execution of test events; primarily using ground/laboratory assets.

· Compiling, processing, and analyzing test data and using the results to develop required test end products, including metrics, test reports, and deficiency reports.

3.3.2.3 Verification, Validation and Accreditation (VV&A). Apply VV&A policies and guidance in the demonstration and documentation for the credibility of models, simulations, and systems. Tasks include, but are not limited to:

· Reviewing, developing, and updating accreditation materials, including intended use statements, model requirement assistance, acceptance criteria, accreditation methodology, draft Accreditation Plans, Accreditation Reports, Accreditation Support Packages (ASP), and Accreditation Letters.

· Collecting and reviewing modeling and simulation data.

· Conducting and documenting assumptions, limitations, capabilities and risk assessments.

· Reviewing V&V related documentation, requirements and acceptance criteria, and assessing any gaps in the information available in support of an accreditation decision.

· Documenting final acceptance criteria.

· Conducting M&S verification efforts in accordance with accreditation and/or V&V plans. This may include use of computer aided software engineering (CASE) tools or other software testing tools or procedures.

· Conducting M&S validation efforts in accordance with accreditation and/or V&V plans. This may include planning and participation in testing of the system being simulated, benchmarking against other M&S, and subject matter expert review of M&S results.

· Documenting verification and validation results in V&V reports and/or the ASP format.

· Facilitating and documenting the results of subject matter expert reviews.

· Providing audit, validation, and verification review of simulation resources, products and processes in accordance with Simulation Division VV&A processes.

3.3.3 General Requirements (CLINs 0002, 0003, 0004, 0005, 0006)

3.3.3.1 Software language and tool requirements for each project shall be in accordance with the current SD standards, or as otherwise specified in individual task orders.

The Contractor shall:

3.3.3.2 Support technical tours of Simulation Division facilities and provide capability presentations to customers and tour groups. All tours and capability briefs must have prior approval of the COR.

3.3.3.3 Provide visitor escort support to individuals who have an approved requirement to be in the Simulation Division supported restricted spaces, but do not have the appropriate security clearance. Escorting is an auxiliary function that may be required periodically from any contractor. A contractor will typically escort individuals working on efforts they are supporting. Escorting of visitors shall be in accordance with the IBST Security SOPs listed in paragraph 2.3 current NAVAIR and NAWCAD instructions, and NAS Patuxent River directives.

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

3.3.3.5 Test and Training Support. Provide engineering support for scheduled test and training events, including system operation, trouble-shooting, event setup, and debriefing.

3.3.3.6 Technical Support. Provide on-site and off-site technical support to other teams, organizations, and facilities both internal and external to the Simulation Division in support of project objectives.

3.3.3.7 Technical Research Studies. Perform technical research and design studies to define performance, operational or user requirements, evaluate new technologies, or improve the capability, efficiency, or reliability of Simulation Division products, projects, laboratories, infrastructure, operations and facilities.

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

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

3.3.1.10 Event Support. Provide support to prepare for and conduct simulation-based testing and training events to include hardware in the loop system testing, distributed battlespace simulations and Live, Virtual, Constructive (LVC) exercises.

3.3.4 Program and Project Management Support (CLINs 0002, 0003, 0004, 0005, 0006)

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

The Contractor shall:

3.3.4.1 Program Management. Manage the contracted effort by providing best-value program performance within cost objectives. Ensure effective management of contracted program and project resources as well as the financial and administrative aspects of the program with respect to the contract. General and Operations Manager shall serve as the primary point of contact with the COR for the contract and oversee the production of deliverables. General and Operations Manager shall review and recommend the development and/or modification of program management plans, strategies, schedules and milestones.

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

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

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

· Ensuring project controls and applicable standards are adhered to.

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

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

· Developing, reviewing, and modifying program management and technical reports, presentations, brochures, white papers and deliverable documentation to support project objectives.

· Meeting with customers.

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

3.3.4.4 Requirements Tracking. Collect, track, establish traceability, communicate and report project requirements. Collect and organize requirements using customer specifications and assist Simulation Division IPT’s with development and tracking of derived requirements.

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

3.3.5 Project Support (CLINs 0002, 0003, 0004, 0005, 0006)

The Contractor shall:

3.3.5.1 Configuration Management. Maintain a Configuration Management (CM) program for documents, software, hardware, and commercial off the shelf (COTS) and government off the shelf (GOTS) documentation in support of SD projects and operations in accordance with established procedures. Maintain a Government owned multimedia technical data library that consists of technical documents, technical data and reports, software, and product user licenses. Tasks include, but are not limited to:

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

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

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

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

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