Attachment_J-04_BEWT_II_FAT_Procedure.docx

DOCX document 450 KB Posted

Attached to
Electronic Warfare Training Systems (EWTS) Federal contract opportunity
Solicitation number
N00024-18-R-5113
Issued by
Department of the Navy Naval Sea Systems Command

About this file

J-04 BEWT II FAT

View the file

Other files for this federal contract opportunity

Other files attached to Electronic Warfare Training Systems (EWTS), newest first.
File Type Posted
Questions_Round_3_Final.xlsx XLSX spreadsheet
18-R-5133_Amendment_3.pdf PDF
Attachment_L-02_Addressing_a_new_EW_Capability_Sample_Problem27JUNE2018.docx DOCX document
Attachment_L-03_AOEW_Capability_Design__Implementation_Sample_Problem27JUNE2018.docx DOCX document
18-R-5113_Amendment_2.docx DOCX document
Attachment_L-08_-_Cost_and_Price_Proposal_Tables_Amended_18JUN2018.xls XLS spreadsheet
N00024-18-R-5113_Bidders_Questions_Final.xlsx XLSX spreadsheet
Attachment_L-11_-_Employee_Qualifications_Form_Updated12JUN2018.xlsx XLSX spreadsheet
Bidders_Questions_and_Answers_FBO_Round_1.xlsx XLSX spreadsheet
18-R-5113_Amendment_1.pdf PDF
Attachment_L-08_-_Cost_and_Price_Proposal_Tables_Updated12JUN2018.xls XLS spreadsheet
Exhibit_A-1_EWTS_CDRLS_Information_Package.pdf PDF
Attachment_L-07_-_Past_Performance_Questionnaire.xlsx XLSX spreadsheet
Attachment_J-01-2_-_BEWT_II_ProductionTechnical_Data_Package.docx DOCX document
Attachment_J-01_-_GFI_List_18R5113.xls XLS spreadsheet
Attachment_J-01-5_-_BEWT_ISEA_Support_Technical_Information_Package.docx DOCX document
Attachment_L-09_-_Contractor_Award_Information.docx DOCX document
Attachment_J-03_IWS_1IT_ITS_SEP_1_Sept_2015.pdf PDF
Attachment_L-03_AOEW_Capability_Design__Implementation_Sample_Problem(18May2018_r1).docx DOCX document
Attachment_J-06_-_ITS_Portal_2010_Quick_Ref_Guide.pdf PDF
Attachment_J-05_IWS_Common_WBS_Structure.pptx PPTX presentation
N00024-18-R-5113_EWTS_RFP_5.30.18.pdf PDF
Exhibit_A_EWTS_CDRLs_14NOV2017.pdf PDF
Attachment_J-01-3_-_CIAT_Technical_Information_Package.docx DOCX document
Attachment_J-07_18-R-5113_DD254_Signed.pdf PDF
Attachment_J-01-1_-_SEWTT_Technical_Information_Package.docx DOCX document
Attachment_L-01_-_Cross_Reference_Matrix.xlsx XLSX spreadsheet
Attachment_L-02_Addressing_a_new_EW_Capability_Sample_Problem.docx DOCX document
Attachment_L-08_-_Cost_and_Price_Proposal_Tables.xls XLS spreadsheet
Attachment_J-02_TRM-BFTT_Tailored_Source_Selection_Sensitive.docx DOCX document
Attachment_L-04_-_Question_Submittal_Form.doc DOC document
Attachment_L-10_-_Facility_Checklist.xlsx XLSX spreadsheet
Attachment_L-05_-_Pre-Award_Accounting_System_Adequacy_Checklist.DOC DOC document
Attachment_J-01-4_-_NULKA_Technical_Information_Package.docx DOCX document
Attachment_L-11_-_Employee_Qualifications_Form.xlsx XLSX spreadsheet
Attachment_L-06_-_Previous_Contract_Effort_Narratives.docx DOCX document
Attachment_J-08_Consolidated_GFP_Attachment.xls.xlsx XLSX spreadsheet
Show all 37

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Attachment 04 – BEWT II Factory Acceptance Test Procedure N00024-17-NR-46544 The software required to perform the BEWT II Factory Acceptance Test (FAT) will be provided upon award of this contract.

ATTACHMENT 01-4 UNCLASSIFIED BEWT II BL 4.1 FC-ANSLQ32-TI1403-FAT

(U) TABLE OF CONTENTS

SectionTitlePage
1.0(U) Scope5
1.1(U) Identification5
1.2(U) BEWT II System Overview5
1.2.1(U) BEWT II System Architecture5
1.2.2(U) BFTT System Overview6
1.2.3(U) NCTE System Overview7
1.2.4(U) AN/SLQ-32 Overview7
1.3(U) Document Overview8
2.0(U) APPLICABLE DOCUMENTS9
2.1(U) Government Documents9
2.1.1(U) Specifications9
2.1.2(U) Standards9
2.1.3(U) BFTT Documents9
2.2(U) Non-Government Documents9
3.0(U) FAT Test preparations10
3.1(U) BEWT II System Preparations10
3.1.1(U) Hardware Prerequisites10
3.1.2(U) Software Prerequisites10
3.1.3(U) Test Personnel10
3.1.4(U) FAT Testing Environment10
3.2(U) FAT Test List12
3.2.1(U) FAT-01: System Hardware Verification Test12
3.2.2(U) FAT-02: Integrated Training Verification Test12
4.0(U) FAT TEST DESCRIPTIONS13
4.1(U) FAT-01: System Hardware Verification Test13
4.1.1(U) Prerequisite Conditions13
4.1.2(U) Test Inputs13
4.1.3(U) Assumptions and Constraints13
4.1.4(U) Expected Test Results13
4.1.5(U) Criteria for Evaluating Test Results13

(U) TABLE OF CONTENTS (Continued)

Section Title Page

4.1.6(U) Test Procedures13
4.1.7(U) Pass/Fail Declaration19
4.2(U) FAT-02 Integrated Training Verification Test20
4.2.1(U) Prerequisite Conditions20
4.2.2(U) Test Inputs20
4.2.3(U) Assumptions and Constraints20
4.2.4(U) Expected Test Results20
4.2.5(U) Criteria For Evaluating Test Results20
4.2.6(U) Test Procedures20
4.2.7(U) Pass/Fail Declarations24
5.0(U) Acronyms and Abbreviations25

(U) LIST OF FIGURES

FigureTitlePage
Figure 1.2.1-1. (U) BEWT II Interconnections6
Figure 3.1.4-1. (U) BEWT II FAT Connections11

(U) LIST OF TABLES

Table Title Page

Table 4.1.6-1. (U) FAT-01 Test Procedures13
Table 4.1.7-1. (U) FAT-01 Pass/Fail Declaration19
Table 4.2.6-1. (U) FAT-02 Test Procedures20
Table 4.2.7-1. (U) FAT-02 Pass/Fail Declarations24

i

(U) Scope

(U) This Factory Acceptance Test (FAT) defines the environment and objectives for verifying proper functionality of the Battle Force Electronic Warfare Trainer (BEWT) II BL 4.1 FC. This FAT applies to the current software release developed and configured for the BEWT II.

(U) Identification

(U) BEWT II is a training support capability under development for Naval Sea Systems Command (NAVSEA) Program Executive Office Integrated Warfare Systems Training Systems Directorate (PEO IWS 7C) under contract number N00024-10-C-5129.

(U) BEWT II System Overview

(U) BEWT II is an Electronic Warfare (EW) training support capability that provides both independent (stand-alone) and integrated (e.g., Battle Force Tactical Training (BFTT)) tactical training to the operators of AN/SLQ-32A and AN/SLQ-32B variants that are fielded or in development. BEWT II provides tactical stimulation to AN/SLQ-32 and interfaces with the BFTT Synthetic Theater of War (STOW) Local Area Network (LAN) and the BFTT Training LAN for combat team training exercises.

(U) The following sections describe BEWT II, BFTT, the Navy Continuous Training Environment (NCTE), and AN/SLQ-32.

(U) BEWT II System Architecture

(U) BEWT II is a training support capability designed to provide stimulation to onboard tactical EW systems, exclusive of the Specific Emitter Identification (SEI), High Gain High Sensitivity (HGHS), and AN/ALQ-210, giving afloat operators the ability to train for tactical operations using organic equipment. BEWT II provides the onboard training team with the ability to exercise individual, team, combat team and force level operational scenarios.

(U) BEWT II is a training support capability designed to provide AN/SLQ-32 stimulation and post-exercise operator assessment in both independent (stand-alone) and integrated (i.e., BFTT and NCTE via BFTT controlled) training configurations. The BEWT II Independent Training State represents the performance grouping associated with BEWT II stand-alone or non-integrated training exercises in which BEWT II stimulates the AN/SLQ-32 without input from the BFTT. BEWT II provides scenario generation and control capabilities in support of independent EW tactical training. The BEWT II Integrated Training State represents the performance groupings associated with training exercises controlled by either BFTT or NCTE via BFTT. The BEWT II software provides an interface between BFTT and the AN/SLQ-32 by stimulating the AN/SLQ-32 using input from BFTT via the BFTT Training LAN or the STOW LAN. In the case of an NCTE controlled exercise, BFTT acts as an intermediary for NCTE, providing BEWT II with transparency to the exercise source. Figure 1.2.1-1, BEWT II Interconnections, shows how BEWT II interconnects with the various trainer and shipboard systems.

Figure 1.2.1-1. (U) BEWT II Interconnections

(U) BEWT II is developed utilizing Open Architecture technical principles and approaches. The system design will provide capability enhancements by designing for modular growth, portable and reusable software, commercial standards, non-proprietary elements and published interfaces. BEWT II is an obsolescence update to the existing BEWT system, which will take advantage of Commercial Off-The-Shelf (COTS) and Non-Developmental Items (NDI) to the maximum extent possible, consistent with achieving the performance requirements identified in this document and providing a system suitable for shipboard use.

(U) BFTT System Overview

(U) The BFTT System AN/USQ-T46 is a highly flexible, interactive unit and group/force level tactical combat training system. The mission of the BFTT system is to provide training capabilities for fleet personnel to achieve and maintain combat readiness with the surface forces. The BFTT system supports joint/allied exercise interoperability and provides Commanding Officers, the Afloat Training Groups (ATGs) and Battle Group/Battle Force (BG/BF) commanders with the ability to conduct coordinated, realistic, high stress combat system training for developing war fighting proficiency and maintaining combat readiness. A major thrust of the BFTT system is to provide a dynamic interactive war fighting environment that includes all naval force elements. The BFTT system supports worldwide training of the full command and decision line including multiple warfare areas for vessels in port and staffs ashore or embarked.

(U) NCTE System Overview

(U) The NCTE is a Fleet Forces Command initiative to develop an infrastructure for linking simulations and real-world combat systems. The goal is to develop a coherent virtual environment where full-spectrum operations can be executed; for example using multiple carrier strike groups in real-time. The NCTE infrastructure brings together systems built for separate purposes, technologies from different eras, products from various vendors, and platforms from various services, and permits them to interoperate. The coherent virtual environment must be distributed across a wide area network. Each platform and command participating in the exercise operates in the same battle space regardless of their physical location in the real world. Each individual system that ties into the NCTE should share battle space information to the maximum extent possible without sacrificing simulation/stimulation accuracy and fidelity. NCTE changes the paradigm of training requirement specification to be more reactive to changes in Fleet operations.

(U) AN/SLQ-32 Overview

(U) The AN/SLQ-32A(V) performs all control and monitoring functions including control of Electronic Support Measures (ESM) and Electronic Countermeasures (ECM) resources, derivation of emitter parameters, threat identification, emitter tracking, reporting to the shipboard Combat Direction System (CDS), and control and monitoring of the Light Airborne Multi-Purpose System (LAMPS) ESM system.

(U) The Surface Electronic Warfare Improvement Program (SEWIP) Block 1 program provides enhanced EW capability to existing ship combat systems to improve Anti Ship Missile Defense (ASMD), counter-targeting and counter-surveillance capabilities, as well as improved battlefield situational awareness.

(U) SEWIP Block 1A adds increased systems processing capability and improved Human Systems Integration (HSI). These improvements were accomplished by replacing the existing digital processor and digital presorter units with a COTS based processor, the Electronic Surveillance Enhancement (ESE), as well as firmware extensions to the ESE to allow communication with an Improved Console and Display (ICAD). The ICAD is a modified Navy Standard AN/UYQ-70 Console and replaces the aging AN/SLQ-32 console.

(U) SEWIP Block 1B is composed of three sequential sub-blocks: Block 1B1, Block 1B2 and Block 1B3. Block 1B1 provides SEWIP with the SEI capability in a stand-alone configuration. Block 1B2 incorporates the Block 1B1 SEI's controls and displays into the ICAD subsystem that was originally fielded in SEWIP Block 1A system. Additionally, Block 1B2 increases the functionality of the Block 1A system by adding EW Operator Embedded Training (ET), and a Net-Centric Warfare Electronic Support (NCWES) capability. The NCWES capability provides the EW Operator with a Common Operational Picture (COP) display capability via connectivity to the Global Command and Control System-Maritime (GCCS-M). Block 1B3 federates HGHS capability for special signals to allow the system to keep pace with the threat and increase situational awareness.

(U) Document Overview

(U) This FAT document is organized as follows:

· Section 1.0 Scope - Identifies the purpose of this document and presents the system overviews.

· Section 2.0 Applicable Documents - Lists additional documents that provide information with respect to this document.

· Section 3.0 FAT Test Preparations - Describes environment and other specifications required for FAT to proceed.

· Section 4.0 FAT Test Procedures - This section provides the procedures for performing FAT testing.

· Section 5.0 Acronyms and Abbreviations - Contains an alphabetical listing of all acronyms and abbreviations used in this document that aid in the understanding of this manual.

(U) APPLICABLE DOCUMENTS

(U) The following documents provide additional information with respect to this BEWT II FAT document.

(U) Government Documents

(U) Specifications BEWT II-TI1403-SSS-F System/Subsystem Specification (SSS) For The Battle Force Electronic Warfare Trainer (BEWT) II Final

(U) Standards

(U) None.

(U) BFTT Documents

(U) None.

(U) Non-Government Documents

(U) None.

(U) FAT Test preparations

(U) The following paragraphs identify and describe the test environment preparations for the hardware, software, and firmware resources necessary to perform FAT on the BEWT II System at the contractor’s test site.

(U) BEWT II System Preparations

(U) The system preparation section provides the steps to verify that the system hardware is present and configured properly at the contractor’s test site to perform the FAT. A depiction of the FAT environment for the BEWT II system is illustrated in Figure 3.1.4-1, BEWT II FAT Connections.

(U) Hardware Prerequisites

(U) Prior to FAT, the system needs to be constructed following all build procedures. Build tests must be passed prior to performing FAT. The Audio/Video Generator (AVG) board needs to pass all board qualification tests. The Power Distribution Board (PDB) and Astrodyne power supply must have passed testing after installation into Interface Management Unit (IMU) enclosure. The latches on the IMU enclosure need to have been adjusted to fit the laptop being paired with the enclosure.

(U) As FAT begins, the BEWT II System parts are considered joined. If FAT fails and one or more parts need to be replaced, the system reverts back to the build phase and must pass associated build tests before going back to FAT.

(U) Software Prerequisites

(U) The current version of BEWT II Software will be installed as part of the FAT procedures..

(U) Test Personnel

(U) The Tester must have a basic operating knowledge of the following devices connected to the BEWT II IMU: Fully Automated Computer System (FACS)/Junction Box (JBOX), AN/SLQ-32, and BFTT.

(U) FAT Testing Environment

(U) The BEWT II System will be connected as shown in Figure 3.1.4-1 BEWT II FAT Connections.

ATTACHMENT 04 UNCLASSIFIEDBEWT II BL 4.1 FC-ANSLQ32-TI1403-FAT

Figure 3.1.4-1. (U) BEWT II FAT Connections

UNCLASSIFIEDBEWT II BL 4.1 FC-ANSLQ32-TI1103-FAT-D

(U) FAT Test List

(U) FAT-01: System Hardware Verification Test

(U) FAT-01 provides the steps to verify that the BEWT II system is built properly with proper power distribution and functions correctly as evidenced by internal diagnostic tools.

(U) FAT-02: Integrated Training Verification Test

(U) FAT-02 provides the steps to run an integrated training scenario (DEMO) testing communications on all BEWT II interfaces.

(U) FAT TEST DESCRIPTIONS

(U) This section describes each test case required to test the operation of a BEWT II System.

(U) FAT-01: System Hardware Verification Test

(U) FAT-01 provides the steps to verify that the BEWT II system is built properly with proper power distribution and functions correctly as evidenced by internal diagnostic tools.

(U) Prerequisite Conditions

(U) All conditions described in Section 3.1 are met. The test will go more smoothly with all the devices that interface with the BEWT II System running before the FAT procedures are started (AN/SLQ-32A and AN/SLQ-32B, FACS, 802.1X and NTP, Gateway, BOPC).

(U) Test Inputs

(U) None.

(U) Assumptions and Constraints

(U) All devices that interface with the BEWT II System (ie, AN/SLQ-32, FACS, BFTT Operator Console (BOPC)) are assumed to be functioning properly.

(U) Expected Test Results

(U) The expected test results to be verified include:

_____1. All connections to IMU are physically secure.

_____2. The laptop fits tightly onto the IMU and the latches are able to close fully with adequate pressure.

_____3. The laptop draws power from the power supply appropriately.

_____4. All system diagnostics pass.

(U) Criteria for Evaluating Test Results

(U) The test will be considered passed if all expected test results shown in Section 4.1.4 are proven true.

(U) Test Procedures Table 4.1.6-1. (U) FAT-01 Test Procedures

STEP
DESCRIPTION
P/F
DISCREPANCIES
1.
Record the Serial Numbers for the following:

Laptop:______________________________ Laptop Power Supply:__________________

IMU: __________________

BEWT II Software Version:______________

2.
Verify that all connections to the IMU are physically secure. Locking connectors (ie. DB-9) should lock appropriately. Friction fit connectors (ie. USB) should be tight.
3.
Verify that the laptop fits tightly onto the IMU. The latches should required adequate force to close, but should latch fully.
4.
Verify that the power switch on front of IMU glows when switched on. Turn on laptop.
5.
Verify the light beneath the charging symbol on the laptop (to the right of the touchpad) is illuminated.
6.
Log in as user bewt2. Password bewtIIqwer#1234
7.
Close the BEWT II application.
8.
If not already installed, install the latest version of the BEWTII software. Place the CD containing the current version of BEWT II software into the CDROM drive. On the desktop, open the Utilities folder and double-click on Load CD. A CD Icon will be displayed on the desktop. Right click on the desktop and open a Terminal window. At prompt type cd /media/dvdrw then bash install_bewt.sh. Answer all questions with /home/bewt2 as folder and correct BEWT software version. When asked to enter My slq password, enter B2admin#1234. Close the terminal window. Then eject the CD.
9.
Open BEWT II Diagnostics Window. These first tests assume that during installation SLQ-A and DIS was chosen as the defaults. (Later tests will change to SLQ-B and HLA to check diagnostics for all interfaces.)
10.
Insert the BFTT removable HDD into the Dell Server and power on the server.
11.
After the server has booted up, double click on the NTP 802.1X icon to start. At the log-in prompt enter Bewt2 as user and BewtII as the password. After the 802.1X routine is running, locate the BFTT 3.5.1 version Icon and expand to show both the BFTT BOPC and Gateway. Double click on the Gateway first and wait until it has started before double-clicking on the BOPC Icon. On the BOPC window, enter PONC as the user and ponc ponc as the password. BFTT operator window will be displayed.
12.
On the BEWT II laptop, exit BEWT II software. On the desktop, double-click on BEWT II Diagnostics Icon.
13.
Click on Run Automatic Tests. Follow the on-screen instructions.
14.
Select the Fault Isolation Tab.
15.
Click Run Automatic Tests. Verify all tests passed.
16.
Disconnect the BFTT cable from the back of the BEWT II IMU.
17.
Click on the Fault Isolation Tab. Run the BFTT STOW PING Test. The test should fail.
18.
Reconnect the cable and re-run the BFTT STOW PING Test. Wait approx. 60 seconds after reconnecting the cable before re-running this test. The test should pass.
19.
Disconnect the SLQ-32A cable from the back of IMU. Cable is upper DB9 connection (J3).
20.
Select the Standard Tab. Run the AN/SLQ-32A-B Digital Stim Interface Test. The test should fail.
21.
Reconnect the SLQ-32A/B Digital Stim cable to the upper DB9 connection (J3) on the back of the BEWT II IMU.
22.
Re-run the AN/SLQ-32A-B Digital Stim Interface Test. The test should pass.
23.
Power off the IMU by pressing the Main Power CB1 switch located in the front of the IMU.
24.
Run the following tests – Tactical Stim Port, Emitter Video USB, Emitter Video Generator, and AN/SLQ-32A Operator Action Port. These tests should fail.
25.
Power on the IMU and re-run the four tests in the previous step. The tests should pass.
26.
Run the AN/SLQ-32A Operator Action Test. But click OK without pressing the SEQ FAB on the SLQ-32 DCC. The test should fail.
27.
Run the AN/SLQ-32A Operator Action Test. Follow the directions on the screen. The test should pass.
28.
Turn off the FACS. Run the AN/SLQ-32A FACS Interface test. The test should fail.
29.
Turn FACS on and wait for it to boot up. Run the AN/SLQ-32A FACS Interface test again. The test should pass. (If the SLQ was running, it may need to be rebooted after the FACS was turned off.)
30.
Select Exit to close the Diagnostics window.
31.
The following steps will check SLQ-32B and HLA tests. BFTT needs to be connected and running.
32.
From a Terminal window, at the command prompt, type

cd /home/bewt2/scripts and hit Enter.

33.
At the command prompt, type

bash setup_bewt.sh and hit Enter.

34.
At command prompt, type

/home/bewt2 and hit Enter.

35.
Enter the current BEWTII software baseline, select “no” to the question about SLQ-32A, and choose Training over STOW when prompted
36.
Place removable HDD in PC designated for use as AN/SLQ-32B emulator. Turn power on.
37.
On log-in screen enter icad as user name and icad.. as password. Select Enter.
38.
Right click on desktop and open a terminal window.
39.
At prompt line type start_all and Enter.
40.
After software loads, at top of window, Left click on Status/Controls.
41.
Left click on State/Mode
42.
Under training, select Embedded and Left click on Apply.
43.
Enter sewip for user and sewip..ET#12345 as Password.
44.
Left click on 32B Operator course.
45.
Choose Lesson 6.1
46.
Choose Topic 5
47.
Left click on Start button.
48.
Minimize windows to show SEWIP/SLQ-32B Main display.
49.
Open BEWT II Diagnostics Window.
50.
Run the following tests under the Standard Tab -Training LAN Port test, AN/SLQ-32B Operation Action, Download Shipboard Training RID file, Download Shipboard Training FED file, and Training LAN XMS Interface. These tests should pass.
51.
Unplug the BFTT cable from the IMU. Run the Download Shipboard Training RID file, Download Shipboard Training FED file, and Training LAN XMS Interface tests again. These tests should fail.
52.
Reconnect the BFTT cable back into the IMU. Run the tests from the previous step again. These tests should pass.
53.
Click on the Fault Isolation Tab.
54.
Run the following tests – AN/SLQ-32B Operation Action Port, SLQ-B MTM Ping, and Training LAN Ping. These tests should pass.
55.
Unplug the SLQ cable in the IMU J6. Run the SLQ-B MTM Ping test. The test should fail.
56.
Reconnect the cable back into the IMU and run the test from the previous step again. This test should pass.
57.
Close Diagnostic Window.
58.
From a Terminal window, at the command prompt, type
59.
At the command prompt, type
60.
At command prompt, type
61.
Enter the current BEWTII software baseline, select “yes” to the question about SLQ-A, and choose STOW over Training when prompted.

(U) Pass/Fail Declaration

(U) Verify Expected Results Table 4.1.7-1. (U) FAT-01 Pass/Fail Declaration

DECLARATION
STEP NUMBER(s)
DETAILED COMMENTS

_______Pass

_______Pass with Exception(s)

_______Fail

(U) FAT-02 Integrated Training Verification Test

(U) FAT-02 provides the steps to run an integrated training scenario thereby testing communications on all BEWT II interfaces.

(U) Prerequisite Conditions

(U) All conditions described in Section 3.1 are met.

(U) FAT-01 has been successfully passed.

(U) Test Inputs

(U) None.

(U) Assumptions and Constraints

(U) All devices that interface with the BEWT II System (ie, AN/SLQ-32, FACS, BOPC) are assumed to be functioning properly.

(U) Expected Test Results

(U) The expected test results to be verified include:

_____1. BEWT II is able to communicate with AN/SLQ-32.

_____2. BEWT II is able to receive operator actions.

_____3. BEWT II is able to communicate with BFTT.

_____4. BEWT II is able to produce audio through AN/SLQ32.

(U) Criteria For Evaluating Test Results

(U) The test will be considered passed if all expected test results shown in Section 4.2.4 are proven true.

(U) Test Procedures Table 4.2.6-1. (U) FAT-02 Test Procedures

STEP
DESCRIPTION
P/F
DISCREPANCIES
1.
Open a terminal window on the BEWTII laptop.
2.
At prompt type ntpq –p. Make sure there is an * beside the remote name address. (This may take a few minutes. Keep retrying the command until you get the *)
3.
At the prompt type ntpstat. Verify that it says “synchronised”
4.
Leave the NTP_802.1X machine running and on the BFTT BOPC locate and start the Integrated Scenario Demo.
5.
On the BEWT II laptop, start the BEWT II software if it is not already running.
6.
Select Tools->Configuration and verify that DIS is selected.
7.
From the Maintenance State, select Training from the main menu. From the drop-down menu, select Enter Integrated Training.
8.
Click on the Green Run arrow. A count-down window is display on the display.
9.
On the AN/SLQ-32A, accept the training request.
10.
On the AN/SLQ-32A, enable bands 2 and 3.
11.
On the BEWT II laptop place the cursor over the Tab button labeled Emission Modeling and select. The Emission Modeling window is displayed. Change the fields to reflect the following:

Choose Flat_Earth Volume_Isotrophic Change the slider bars to adjust emission settings.

Select OK to close the window.

12.
Verify the simulated tactical display populates with platform icons in configuration similar to the BOPC display.
13.
Hook an emitter on the AN/SLQ-32A. Verify sound of emitter coming from speakers of AN/SLQ-32A.
14.
Open the Operator Action Log (OAL) Tab in BEWT II Software application. Press sequence on the AN/SLQ-32A. Verify those keystroke data is displayed in the OAL window on BEWT II.
15.
Open the Emitter Tab in BEWT II Software application. Select an active emitter displayed in Green and then click on Preview Emitter Audio. Verify you can hear the emitter audio.
16.
On BEWT II place cursor over Red Stop button and select. SLQ-32 is taken out of training.
17.
Close Integrated Training. Select Quit BEWT II.
18.
Select Independent Training. Select an Independent Training scenario.
19.
Open and Run the scenario. Verify platform motion and emitter parameters on the AN/SLQ-32A are compatible with what is displayed on the BEWT II laptop.
20.
When finished select Stop.
21.
Close Training and Quit BEWT II.
22.
Close Gateway and BOPC 3.5.1 on virtual machine and start Gateway and BOPC 5.0 virtual machines. Start Demo scenario.
23.
On BEWT II open a Terminal window, at the command prompt, type
24.
At the command prompt, type
25.
At command prompt, type
26.
Enter the current BEWTII software baseline and select “no” to the question about SLQ-A when prompted and “Training” over Stow.
27.
Double click on BewtII icon.
28.
On BEWT II GUI, select Training, then Integrated Training.
29.
Left click on Green Run arrow located upper right of window.
30.
On AN/SLQ-32A initiate training.
31.
On BEWT II, Left click on BFTT Tab.
32.
Verify that Training LAN interface is displayed with BFTT_HLA.
33.
On BEWT II, Left click on OAL Tab.
34.
On AN/SLQ-32B emulator, Left click on Sequence button several times. Check the OAL window on BEWT II GUI is populated with operator action logs.
35.
Hook an emitter symbol. Right click and select Drop Emitter. Check that the OAL window indicates operator action.
36.
Upon completion on BEWT II, Left click on Red Stop button and exit training.
37.
Quit BEWT II.
38.
From a Terminal window, at the command prompt, type
39.
At the command prompt, type
40.
At command prompt, type
41.
Enter the current BEWTII software baseline and select “yes” to the question about SLQ-A when prompted and “STOW” over Training.
42.
Verify that all CDs have been removed from the laptop and shut it down.
43.
Stop Scenario running on BFTT and shutdown BFTT, Gateway, and NTP_802.1X virtual machines.

(U) Pass/Fail Declarations Table 4.2.7-1. (U) FAT-02 Pass/Fail Declarations

DECLARATION
STEP NUMBER(s)
DETAILED COMMENTS

_______Pass

_______Pass with Exception(s)

_______Fail

UNCLASSIFIEDBEWT II BL 4.1 FC-ANSLQ32-TI1103-FAT-D

(U) Acronyms and Abbreviations

ASMDAnti Ship Missile Defense
ATGAfloat Training Group
AVGAudio Video Generator
BEWTBattle Force Electronic Warfare Trainer
BFTTBattle Force Tactical Training
BG/BFBattle Group/Battle Force
BOPCBFTT Operator Console
CDSCombat Direction System
COPCommon Operational Picture
COTSCommercial-Off-The-Shelf
ECMElectronic Countermeasures
ESEElectronic Surveillance Enhancements
ESMElectronic Support Measures
ETEmbedded Training
EWElectronic Warfare
FACSFully Automated Computer System
FATFactory Acceptance Test
GCCS-MGlobal Command and Control-Maritime
HGHSHigh Gain High Sensitivity
HMIHuman Machine Interface
HSIHuman Systems Integration
ICADImproved Control And Display
IMUIneterface Management Unit
JBOXJunction Box
LAMPSLight Airborne Multi-Purpose System
LANLocal Area Network
NAVSEANaval Sea Systems Command
NCTENavy Continuous Training Environment
NCWESNet-Centric Warfare Electronic Support
NDINon-Developmental Items
OALOperator Action Log
PDBPower Distribution Board
SEISpecific Emitter Identification
SEWIPSurface Electronic Warfare Improvement Program

ACRONYMS AND ABBREVIATIONS (Continued)

SSSSystem/Subsystem Specification
STOWSynthetic Theater of War
UUnclassified

image1.emf

Microsoft_Visio_2003-2010_Drawing.vsd Computer

Enter Text

BFTT

BEWT II

image2.png oleObject1.bin

File details come from the government source that posted it.