Attachment_L-5_-_Initial_Task_Order_SOW.pdf

Attachment L-5 Task Order Competition 1

Contract No.: Page 1 of 4

STATEMENT OF WORK

Distributed Simulation Support for IWS-1 Enterprise Testbeds

1.0 INTRODUCTION

The purpose of this Task Order is to provide Systems Engineering in support of NRL Code 5770’s Distributed Simulation Infrastructure. Work under this Task Order is broadly covered by Tasks I and III of the Base Statement of Work; specifics for this Task Order are described below. The Period of Performance (PoP) for this Task Order will be for eighteen (18) months from date of award.

2.0 BACKGROUND

The Naval Research Laboratory Code 5770 is the integrator for a series of distributed simulation testbeds used to support Test and Evaluation (T&E) for new ship classes and major combat system baseline upgrades. A Testbed is a High Level Architecture (HLA) Federation, consisting of Virtual Range elements, such as scenario geography, environment, and background platforms and emitters; Ownship elements, consisting of ship platform, sensors, hard and soft kill weapons, and integrating combat systems; and Threat System representations. Support is sought for systems engineering tasks in defining simulation requirements, establishing standards, providing support for the verification and validation of the Testbed, designing test plans, and other related systems engineering tasks. Support is also sought for Testbed integration and simulation network maintenance, to include meeting Information Assurance (IA) requirements, software tools development, operation of the Testbed, and quick look analysis following the completion of simulation runs.

3.0 TASK DESCRIPTIONS

3.1 TASK 1 Systems Engineering for Modeling and Simulation Testbed

3.1.1 The Contractor shall provide Research and Development to PEO/IWS-1 systems engineering and management of the T&E Enterprise Testbed including technical leadership for the systems engineering, infrastructure, and integration of the Testbed.

3.1.2 The Contractor shall perform technical investigation of M&S issues including architecture, application of technical standards, middleware and support tools, Testbed runtime performance, Testbed configuration, visualization, security classification, common scenarios definition, and re-use of Testbed simulations for other IWS and Ship Class applications.

3.1.3 The Contractor shall participate in Enterprise Testbed Federation Design activities and meetings, Enterprise T&E IPT and associated working group activities, technical design review and program reviews, and the Enterprise Configuration Management Board.

3.1.4 The Contractor shall manage the configuration baseline for the Enterprise Testbed by adhering to industry accepted configuration management processes.

3.1.5 The Contractor shall develop and document the Enterprise Testbed system engineering products including:

Enterprise Testbed Master Requirements; Enterprise Testbed Capabilities Matrix; Enterprise Testbed Capability Design Build Strategies; Federation Object Model; Federation Agreements Document; Integration and Configuration Management Master Plan; and, Risk tracking. Documentation shall comply with PEO IWS M&S Instructions.

Contract No.: Page 2 of 4

3.1.6 The Contractor shall coordinate M&S use between Enterprise T&E and constituent systems programs to ensure that Program Offices are kept appraised of results from T&E simulation studies and to gain concurrence for publication of results.

3.1.7 The Contractor shall participate in the quarterly PEO IWS M&S IPT and associated focus group meetings, quarterly Threat Representation Working Group meetings, Threat M&S Working Group meetings, and Enterprise PRA Testbed Threat Scenario Working Group meetings.

3.1.8 The Contractor shall provide input to IWS M&S standards and guidelines.

Work under this task will be performed primarily off-site of NRL, at both contractor and other government facilities such as the Naval Sea Systems Command facilities in the Washington DC metropolitan area, and the Naval Air Warfare Center Weapons Division facility in Ridgecrest, CA.

3.2 Task 2. Federation Infrastructure

3.2.1 The Contractor shall assist in the achievement of federated computer EW simulation objectives through the development of methods for configuration, synchronization and coordination of federated simulations across both local area networks (LAN) and wide area networks (WAN).

3.2.1.1 The Contractor shall monitor the interaction of federated simulations to ensure the coordinated functionality and quality of those computer simulations.

3.2.1.2 The Contractor shall develop automated systematic methods and mechanisms for the initialization and start of distributed EW computer simulations across a WAN in order to run multiple iterations of scenarios in batches. These methods should enable batches of scenarios to be run while unattended, and provide for individual scenario run termination at completion or due to fault conditions.

3.2.1.3 The Contractor shall perform research into the handling and compartmentalizing of secure or proprietary data for a multi-level security infrastructure to allow for greater interoperability. It is anticipated that the simulations of some future programs will drive the requirement to run the federation at a higher security level and it is desired to maintain the highest level of commonality between different versions of the Testbed.

3.2.1.4 The Contractor shall conduct research into interoperability improvements such as automated distributed simulation coordination and synchronization across multiple sites to increase the number of simulation runs performed in a given period of time, thereby increasing productivity.

3.2.1.5 The Contractor shall prepare all necessary documentation for distributed simulation networks necessary to meet DoD and Navy Information Assurance requirements.

3.2.2 The Contractor shall develop HLA simulation interface software.

3.2.2.1 The Contractor shall develop Testbed integration software.

3.2.2.2 The Contractor shall analyze HLA simulation inputs and outputs to determine the pertinence and validity, perform corrective action or coordinate corrective action among other federation participants as required.

3.2.2.3 The Contractor shall develop software and scripts to sort, analyze, parse, and report data.

3.2.2.4 The Contractor shall develop a plan to log on, access, and run classified software from a remote site on a classified network.

Contract No.: Page 3 of 4

3.2.2.5 The Contractor shall establish methodologies for consistent and repeatable random number generation across multiple simulations on a distributed network to support statistical analyses. This is required to ensure that given the same random number on different runs produces the same simulation output.

3.2.2.6 The Contractor shall research the handling and compartmentalization of secure data from simultaneous distributed simulations using the HLA Run-Time Infrastructure (RTI).

3.2.2.7 The Contractor shall provide prototype software tools as needed, such as: HLA interface prototypes for new system development, SIMDIS plug-in prototypes, US Navy system simulation prototypes, and portable testbed prototypes.

3.2.2.8 The Contractor shall define the basis for the exchange of data and events between simulations using HLA/RTI while maintaining simulation interoperability and portability across computing platforms, operating systems and communications systems.

3.2.3 The Contractor shall execute Testbed simulation runs, review and analyze output data and verify run results. The Contractor shall document the outcome of HLA simulations.

3.2.3.1 The Contractor shall provide support for Testbed events as defined in the AW Enterprise T&E Master Schedule, and other Testbed events as directed by IWS-1, to include the replication of Self-Defense Test Ship (SDTS) and Integrated Combat System Test (ICST) at-sea test events in the Testbed.

3.2.3.2 The Contractor shall conduct a weekly telephone conference with all Testbed implementation personnel to discuss Testbed status, current issues, run schedules, and other related technical issues. Minutes of these teleconferences will be disseminated to all participants within two working days following the teleconference.

3.2.3.3 The Contractor shall conduct daily “Quick Look” analyses, provide key event summaries, and disseminate the results to all Testbed participants. Runs identified as “No-test” runs will be rescheduled.

Work under Task 2 will be performed primarily on site at NRL Code 5770 facilities.

4.0 DELIVERABLES

Monthly Financial, Labor (On-site and Off-site) and Technical Progress reports will be required for each Task Order issued under the base contract.

4.1 Task 1 Deliverables

1. Enterprise Testbed Master Requirements

2. Enterprise Testbed Capabilities Matrix

3. DT/OT ET15 LHA 6 PRA Assessment Accreditation Package

4. DT/OT ET15 HW Configuration Matrix

5. ET15 Test Readiness Review

6. ICST TDAWG Proceedings

7. Common FAD/FOM Documents

4.2 Task 2 Deliverables

1. Information Assurance Documentation, to include Federation Network Diagrams, hardware lists, software lists, router configurations, and any other documentation necessary to support IA Accreditation.

2. Integration and Configuration Management Master Plan

3. Weekly teleconference minutes

4. Daily test execution quick look analysis/key events summaries

5. Federation Data Extraction Tool updates

Contract No.: Page 4 of 4

5.0 SECURITY

Paragraph 4.1 and the DD254 of the Base SOW define the Security requirements for this task. It is anticipated that personnel working Task 1will routinely require access to Secret information, and may be required occasionally to have access to Top Secret/SCI information. It is anticipated that personnel working Task 2 will routinely require access to Secret material.