Attachment 0004d - Operator Procedures For IFMC GSIL.docx
DOCX document 2 MB Posted
- Attached to
- RFP for Integrated Battle Command System (IBCS) LRIP/FRP Federal contract opportunity
- Solicitation number
- W31P4Q-20-R-0015
About this file
This is a request for proposal for a hardware low rate initial production/full rate production effort for the Integrated Battle Command System. The Army seeks to produce IBCS hardware end items in accordance with supplied technical data packages and specifications. Engineering changes may be required for obsolescence, new capabilities, and export considerations. Questions are due by December 10, 2020 at 4pm Central Standard Time. This RFP is only for contractors who met entrance criteria on SAM and were approved by the IFMC Project Office.
View the file
Other files for this federal contract opportunity
Show all 50
RFP for Integrated Battle Command System (IBCS) LRIP/FRP has more files on GovTribe.
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
W31P4Q-20-R-0015 ATTACHMENT 0004d
Operator Procedures For the Integrated Fires Mission Command
(IFMC)
Government System Integration Laboratory
(GSIL)
Prepared for:
United States Army Program Executive Office Missiles and Space Army IAMD Project Office Building 5250 Redstone Arsenal, AL 35898
15 July 2020
DISTRIBUTION STATEMENT F: Further dissemination only as directed by the SFAE-MSLS-IAMD-SI or higher DOD authority.
UNLESS OTHERWISE APPROVED BY THE ARMY INTEGRATED AIR AND MISSILE DEFENSE PROJECT OFFICE, ALL ENGINEERING TECHNICAL DATA, SOFTWARE AND COST DATA SHALL BE SUBJECT TO
EXPORT RESTRICTIONS AS FOLLOWS:
WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751et. Seq.) or the Export Administration Act of 1979, as amended. Title 50, U.S.C., app 2401 et. Seq. Violation of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DOD Directive 5230.25.
DESTRUCTION NOTICE - For classified documents, follow the procedures in DOD 5200.22-M, National Industrial Security Program Operating Manual (NISPOM), Chapter 5, Section 7, or DOD 5200.1-R, Information Security Program Regulation, Chapter IX. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.
Operator Procedures
1. Create Daily File Structure
1.1 To Create the File Structure
2. iMon
2.1 iMon Start of Day Procedures
2.2 To Start Recording iMon Data for Each Run
2.3 To Stop Recording iMon Data and Increment the Run Number
2.4 iMon End of Day Procedures
3. ABITTS
3.1 ABITT Start of Day Procedures
3.2 To Start ABITTs Recording Prior to Each Run
3.3 To Stop and Harvest ABITT Data After Each Run
3.4 ABITT End of Day Procedures
4. NSITE
4.1 NSITE Start of Day Procedures
4.2 To Start NSITE Recording Prior to Each Run
4.3 To Stop NSITE After Each Run
4.4 NSITE End of Day Procedures
5. LOTN
5.1 LOTN Start of Day Procedure
5.2 To Start LOTN for Each Run
5.3 Reloading Launchers and Changing State Modes
5.3.1 Reloading Launchers
5.3.2 Changing State Modes
5.4 LOTN End of Run Harvesting
5.5 LOTN End of Day Procedures
6. WRAITH
6.1 WRAITH Start of Day Procedures
6.2 WRAITH Start of Run Procedures
6.3 WRAITH End of Run Procedures
6.4 WRAITH End of Day Procedures
7. MIDS
7.1 Powering On MIDS
7.2 Loading Crypto into MIDS
7.3 Initializing GW EOC MIDS
7.4 Initializing External L16 MIDS
7.5 Powering MIDS off at End of Day
8. IES
8.1 IES Start of Day Procedure
8.2 To Start IES Prior To Each Run
8.3 To Stop IES After Each Run
8.4 IES End of Day Procedures
9. EOC
9.1 EOC Start of Day
9.1.1 To Set or Clear Gateway Node
9.1.2 To Check Status of EOC Software
9.1.3 To Stop EOC Software
9.1.4 To Fix Disabled CIs
9.1.5 To Clean Logs on the EOC
9.2 EOC Start of Run Procedures
9.2.1 To Load, Wipe, and Snap Priors on the EOC
9.2.2 Start EOC Software
9.2.3 To Check Status of EOC Software
9.3 Start CWMI
9.3.1 Start CWMI Application
9.3.2 Start Video Capture on Each Workstation Using CWMI
9.4 Log in to Roles on CWMI
9.5 Activate Defense Plan from CWMI
9.6 Change EOC Operation Mode
9.7 Sensors
9.7.1 RIU
9.7.1.1 Initialize RIUs from Pre-Created Database on the RIU
9.7.1.2 Initialize RIUs via Mission Planning
9.7.1.3 Loading Priors on an RIU
9.7.1.4 Radiating the RIU
9.7.2 Sentsim
9.7.2.1 Loading Priors on a Sentsim
9.8 Launchers
9.8.1 Emplacing Launchers
9.8.1.1 Automatic Emplacement of Multiple Launchers
9.8.1.2 Automatic Emplacement of a Single Launcher
9.8.1.2 Manual Emplacement of Single Launcher
9.8.2 Changing State Mode of a Launcher
9.9 EOC End of Run Procedures
9.9.1 EOC Shutdown Procedures
9.9.2 To Check Status of EOC Software
9.9.3 To Fix Disabled CIs
9.9.4 Harvesting EOC Data
9.9.5 Cleaning EOC Logs After Harvest
10. Relay
10.1 Relay Start of Day
10.1.1 To Check the Status of Relay Software
10.1.2 To Stop Relay Software
10.1.3 To Fix Disabled CIs
10.2 Relay Start of Run Procedures
10.2.1 Start Relay Software
10.2.2 To Check Status of Relay Software
10.3 Relay End Of Run Procedures
10.3.1 Relay Software Shutdown
10.3.2 To Check Status of Relay Software
10.3.3 To Fix Disabled CIs
10.3.4 Harvesting Relay Data
10.3.5 Cleaning Relay Logs
11. ADSI
11.1 To Start ADSI Run
11.2 To Stop Run and Harvest Run Data
11.3 ADSI End of Day Procedures
12. LINK
12.1 To Start the LINK Box
12.2 To Stop the LINK Box
13. L2
13.1 L2 Start of Day Procedures
13.2 To Start L2 for Each Run
13.3 To Stop the L2 for Each Run
14. Sentsim
14.1 Sentsim Start of Day Procedures
14.2 To Start the Sentsim Application for Each Run
14.3 To Stop the Sentsim Application
14.4 To Harvest Sentsim Data
15. RIU
15.1 RIU Start of Day Procedures
15.2 FMS/D Startup
15.2.1 FMS/D Application Start
15.3 WINPIP Procedures
15.4 FMS/D End Of Run Procedures
15.5 FMS/D End Of Day Procedures
16. RTDRIU
16.1 RTDRIU Start Of Day Procedures
16.2 RTDRIU Application Startup
16.3 To Start RTDRIU Software
16.4 To Stop RTDRIU Software
16.5 RTDRIU End Of Day Procedures
17. VEST
17.1 VEST Start of Day Procedures
17.2 To Start VEST Application
17.3 To Start VEST Run
17.4 To Stop VEST Run
17.5 VEST End Of Day Procedures
18. ELIB
18.1 ELIB Start Of Day Procedure
18.2 To Start ELIB Application
18.3 To Start ELIB Application for a Run
18.4 To Stop ELIB Application for a Run
18.5 ELIB End Of Day Procedures
19. MARSNT
20. CDS/BFT
21. F-35
22. GRTTC
22.1 GRTTC Start Of Day Procedures
22.2 GRTTC Application Startup
22.3 GRTTC Scenario Start
22.4 To Stop GRTTC During a Scenario
23. TL3 SOD/EOD Procedures
24. EOC Shutdown Procedures
25. Relay Shutdown Procedures
This Page Was Left Intentionally Blank
1. Create Daily File Structure Create Daily File Structure
| Step Number: |
| Action: |
| Notes: |
1.1 To Create the File Structure
| 1 |
| Navigate to GSIL share on any classified machine. |
On windows, open a file explorer and double click on gsil_share.
On Linux system, open a terminal and type:
cd /mnt/gsil
| 2 |
| Run file creation batch file. |
| This step will create the file structure for the day. |
On windows, double click createfilestructure.bat
On windows, in the terminal type:
start createfilestructure.bat
2. iMon iMon Operations
| Step Number: |
| Action: |
| Notes: |
2.1 iMon Start of Day Procedures
| 1 |
| Navigate to correct machine(s) depending on the test line you are on through the KVM and log in. |
Test Line 1: super06 (dell140)
Test Line 2: GSIL-TL2-IMON
Test Line 3: GSIL-TL3-IMON
Test Line 4: GSIL-TL4-IMON
Test Line 5: GSIL-TL5-IMON
| 2 |
| Double click on the start_iMon icon on the Desktop and wait on the browser to populate with the servers being monitored. |
| Check with the TC to ensure you are monitoring all stations that need monitoring. |
| 3 |
| Verify run date is correct on the iMon browser. |
2.2 To Start Recording iMon Data for Each Run
| 1 |
| Verify run number is correct on the iMon server. |
| Check with the TC to ensure run number for current run. |
| 2 |
| Verify all servers being monitored do not have red errors highlighted. |
| If anything is highlighted red, notify TC and or other SMEs to fix before proceeding. |
| 3 |
| Click on "Start Recording" in the upper right-hand corner. |
2.3 To Stop Recording iMon Data for Each Run and Increment the Run Number
| 1 |
| Make sure all software is stopped on all test tools and IBCS. |
| 2 |
| Give the browser a minute to update and verify that the run number automatically increments to the next run. |
2.4 iMon End of Day Procedures
| 1 |
| Wait for the browser to update from stopping the previous run and then click "Shutdown iMon" at the bottom of the screen. |
| 2 |
| In the next browser, click "Shutdown all Servers and Clients" |
| This shuts iMon down for the day. |
| 3 |
| If any terminals do not close, close them automatically. |
3.
ABITTs
ABITT
| Step Number: |
| Action: |
| Notes: |
3.1 ABITT Start of Day Procedure
| 1 |
| Navigate to correct machine(s) depending on the test line you are on through the KVM and log in. |
Test Line 1: GSIL-TL1-ABITT1 (for EOCs)
Test Line 1: GSIL-TL1-ABITT2 (for Relays)
Test Line 2: GSIL-TL2-ABITT1
Test Line 2: GSIL-TL2-ABITT2
Test Line 3: GSIL-TL3-ABITT1
Test Line 3: GSIL-TL3-ABITT2
Test Line 4: GSIL-TL4-ABITT1
Test Line 5: GSIL-TL5-ABITT1
| 2 |
| Start the iMon client on each box you are collecting data on by double clicking on the start_imon_client.bat icon on the desktop. |
| 3 |
| Double click on Wireshark and open an instance of Wireshark per MEI you need to record data on. |
| Ask the TC how many MEIs you have per line. |
For example, on Test Line 1:
Open three Wireshark instances on GSIL-TL1-ABITT1 for each of the three EOCs.
Open six Wireshark instances on GSIL-TL1-ABITT2 for each of the six relays.
3.2 To Start ABITTs Recording Prior to Each Run
| 1 |
| For each MEI that needs to be recorded, select the corresponding Wireshark and click the shark fin ("Start Recording") icon. |
| Ask the TC which ABITTs need to be started each run. |
3.3 To Stop and Harvest ABITT Data After Each Run
| 1 |
| For each ABITT Wireshark that was started, select the Wireshark instance and: |
Click the red square to stop recording.
Click File-->Save As
When the "Save As" box pops up on the screen, navigate to the correct file saving location:
/mnt/gsil/GTL#/YYYYMMDD/GSIL/abitt
Save file in the above location with the file name:
MMDD-RR_ABITT_<MEI TYPE><MEI NUMBER>
Where:
MM = Month of the Year (ex. 05-May)
DD = Day of the Year (ex. 20)
YYYY = Full Year (ex. 2020)
RR = Run Number (ex. 01)
<MEI TYPE> = Relay or EOC (ex. EOC)
<MEI Number> = Number of the MEI (ex. 51601)
Where our example would be named:
0520-01_ABITT_EOC51601
Would be saved in the folder:
/mnt/gsil/GTL1/20200520/GSIL/abitt
Click on Save
3.4 ABITT End of Day Procedure
| 1 |
| Close out all Wireshark instances that you have open on each of the ABITT boxes. |
4. NSITE
NSITE
| Step Number: |
| Action: |
| Notes: |
4.1 NSITE Start of Day Procedures
| 1 |
| Navigate to correct machine(s) depending on the test line you are on through the KVM and log in. |
Test Line 1: GSIL-TL1-NSITE
Test Line 2: GSIL-TL2-NSITE
Test Line 3: GSIL-TL3-NSITE
Test Line 4: GSIL-TL4-NSITE
Test Line 5: GSIL-TL5-NSITE
| 2 |
| Start the iMon client by double clicking on the start_imon_client.bat icon on the desktop. |
| 3 |
| Start the NSITE application by clicking on the NSITE.exe icon on the Desktop |
| This application may take a while to load. Be patient. |
| 4 |
| Open the DIS.cfg file by clicking File--->DIS.cfg |
| 5 |
| Start the TL3DMS visual aid by clicking the "Globe" icon on the NSITE application in the icon bar. |
| 6 |
| Once map opens, click the "Electrical Plug" icon on the icon bar that says "Auto Connect" when it is hovered over on the TL3DMS application. |
4.2 To Start NSITE Recording Prior to Each Run
| 1 |
| On the NSITE application, right click in the main window on the line that is titled "DIS", then select "Properties". |
| 2 |
| A window will pop up and there are two places to edit the run number. |
| After changing these file names, click "OK". |
Log File Name: MMDD-RR_NSITE.log
DB/DERG/Error File Name: MMDD-RR_NSITE.err
| 3 |
| On the NSITE application screen, change the "Status" bubble on the left from "IDLE" to "Real Time" |
| This starts the application recording. |
| 4 |
| On the TL3DMS application, load the correct view by clicking File--> <View> |
| Ask the TC which part of the world you are in and select the corresponding view file. |
4.3 To Stop NSITE After Each Run
| 1 |
| On the NSITE application screen, change the "Status" bubble on the left from "Real Time" to "IDLE" |
| 2 |
| On the TL3DMS application, click the "Refresh" button that when hovered over says "Purge Tracks" and click "OK" on the pop up. |
4.4 NSITE End of Day Procedure
| 1 |
| Close out of the NSITE and the TL3DMS applications. |
| 2 |
| On the desktop, click the "End of Day Data Move" batch file. |
| 3 |
| Verify that all data has been moved to the NSITE folder on the gsil share under: |
/mnt/GSIL/GTL#/YYYYMMDD/GSIL/nsite
Where:
MM = Month of the Year (ex. 05-May)
DD = Day of the Year (ex. 20)
YYYY = Full Year (ex. 2020)
RR = Run Number (ex. 01)
5. LOTN
LOTN
| Step Number: |
| Action: |
| Notes: |
5.1 LOTN Start of Day Procedure
| 1 |
| Navigate to correct machine(s) on the KVM depending on the test line you are on and the software you are wanting to use and log in. |
| Normally, TL1 LOTN1 has the current baseline lockdown software. TL1 LOTN2 will have debug versions and checkout versions before it is formally released to be installed across the fleet. |
Test Line 1: GSIL-TL1-LOTN1
Test Line 1: GSIL-TL1-LOTN2
Test Line 2: GSIL-TL2-LOTN
Test Line 3: GSIL-TL3-LOTN
Test Line 4: GSIL-TL4-LOTN
Test Line 5: GSIL-TL5-LOTN
| 2 |
| Open a terminal and start Wireshark by typing: |
sudo wireshark -B 64 -s 1532
| 3 |
| Open a terminal and start the LOTN application by typing: |
lotn
5.2 To Start LOTN for Each Run
| 1 |
| In the Wireshark window, start recording the DIS VLAN (nic with the x.y.30.z address) by: |
Click Capture-->Options
Select the nic with the x.y.30.z IP address and click "Start"
| 2 |
| In the LOTN application, open the correct laydown file by: |
| Ask the TC which laydown file to use. |
Click File-->Open
Navigate to the location of the laydown files:
/home/lotn_user/IV14_Configs
Click on correct file as told by the TC and click "Open"
| 3 |
| Once the correct file is open, you then must set the run parameters by: |
Click Run-->Data Collection Parameters
Change:
Run Number = MMDD_RR
Julian Date = JJJ
Where:
MM = Month of the Year (ex. 05-May)
DD = Day of the Year (ex. 20)
RR = Run Number (ex. 01)
JJJ = Julian Date (ex. 095)
Click "OK" to exit out of dialog.
| 4 |
| Once you have edited the Data Collection Parameters, you must then save the file. To do this: |
Click File-->Save
| 5 |
| After saving the file, you can then start the LOTN application by: |
Click Run-->Start
5.3 Reloading Launchers and Changing State Modes
During some runs, you will be asked to reload the launchers or change a state mode on LOTN.
| 1 |
| To reload a launcher: |
Select launcher on the LOTN GUI.
Ensure launcher "State" is in "LOCAL"
If launcher is not in "LOCAL" state, either:
Ask EOC operator to put launcher in "Local" state or
Select the launcher in the LOTN GUI and click on the "Local" button at the bottom of the GUI.
With launcher in "Local" state, select the launcher on the LOTN GUI
Click on the "Reload" button on the bottom of the LOTN GUI.
If the launcher type is a PAC3 or MSE, you must restart the launcher now. Refer to the LINK or L2 section on how to do this.
Once LINK or L2 is powered down, or launcher type is PAC2, click on launcher and change "State" to "Remote_Enabled" by clicking on the "Remote_Enable" button at the bottom of the LOTN GUI.
If launcher type was a PAC3 or MSE, you can now restart that launcher following the steps in the LINK or L2 section.
| 2 |
| To change state modes of a launcher: |
Select launcher on the LOTN GUI.
If you are instructed to take launcher to "Local" click the "Local" button on the bottom of the LOTN GUI.
If you are instructed to take launcher to "Remote Standby" click the "Remote_Enable" button on the bottom of the LOTN GUI.
5.4 LOTN End of Run Harvesting Procedures
| 1 |
| In the LOTN application, stop the LOTN run by: |
| Do not save file after the run if prompted to do so. |
Clicking Run--->Stop
| 2 |
| In the Wireshark application, stop the run by: |
Click the red square to stop recording.
Click File-->Save As
When the "Save As" box pops up on the screen, navigate to the correct file saving location:
/mnt/gsil/GTL#/YYYYMMDD/GSIL/lotn
Save file in the above location with the file name:
MMDD-RR_LOTN_wireshark
Where:
MM = Month of the Year (ex. 05-May)
DD = Day of the Year (ex. 20)
YYYY = Full Year (ex. 2020)
RR = Run Number (ex. 01)
<MEI TYPE> = Relay or EOC (ex. EOC)
<MEI Number> = Number of the MEI (ex. 51601)
Where our example would be named:
0520-01_LOTN_wireshark
Would be saved in the folder:
/mnt/gsil/GTL1/20200520/GSIL/lotn
Click on Save
5.5 LOTN End of Day Procedures
| 1 |
| Close out of Wireshark and the LOTN applications and log out of the LOTN server. |
6. WRAITH
WRAITH
| Step Number: |
| Action: |
| Notes: |
6.1 WRAITH Start of Day Procedures
| 1 |
| Navigate to correct machine(s) on the KVM depending on the test line you are on and the software you are wanting to use and log in. |
Test Line 1: GSIL-TL1-WRAITH
Test Line 2: GSIL-TL2-WRAITH
Test Line 3: GSIL-TL3-WRAITH
Test Line 4: GSIL-TL4-WRAITH
Test Line 5: GSIL-TL5-WRAITH
| 2 |
| Open two terminals from the WRAITH desktop. |
In both terminals, type:
cd ~
6.2 WRAITH Start of Run Procedures
| 1 |
| In the first terminal, start TIE by typing: |
./runTIE
| 2 |
| In the second terminal, start the graphic visualizer by typing: |
./runFX
6.3 WRAITH End of Run Procedures
| 1 |
| In the first terminal, stop TIE by hitting: |
CTRL + c
| 2 |
| In the second terminal, stop the graphic visualizer by hitting: |
CTRL + c
6.4 WRAITH End of Day Procedures
| 1 |
| Close both terminals. |
| 2 |
| Open new terminal and type: |
cd /home/tactoff/TacoData/Replays
| 3 |
| In terminal type: |
cp -rp in-YYYY-MM-DD* /mnt/gsil/GTL#/YYYYMMDD/GSIL/wraith
Where:
MM = Month of the Year (ex. 05-May)
DD = Day of the Year (ex. 20)
YYYY = Full Year (ex. 2020)
RR = Run Number (ex. 01)
| 4 |
| Verify data is moved then in the terminal type: |
rm -rf *
| 5 |
| Close terminal and log out of the WRAITH server. |
7. MIDS
MIDS
| Step Number: |
| Action: |
| Notes: |
7.1 Powering On MIDS
| 1 |
| On the left side of the MIDS, there is a toggle switch in between multiple cables. Flip the switch up to allow power to the MIDS. |
| 2 |
| On the right side of the MIDS by the LED screen, there is a rotary switch in the shape of a tear. Push in and rotate that switch into the "ON" position. |
7.2 Loading Crypto Into MIDS
| 1 |
| Access the COMSEC safe and get the red SKL, a loading cable, and paper work. This SKL contains the classified Crypto keys. |
| These steps require being COMSEC briefed. |
| 2 |
| Log into the SKL. |
| 3 |
| Once logged in to the SKL, select "Equipment" then select "MIDS" |
| 4 |
| Connect the loading cable to the SKL and the MIDS loading port which is located in the center of the MIDS toward the bottom. |
| 5 |
| Click on the "Load" icon in the very top right-hand corner of the SKL. |
| 6 |
| Click "OK" or "Next" when the screen to load pops up. |
| 7 |
| Wait on a confirmation window that should say "8 SUCCESSFUL". |
| 8 |
| Click "OK" |
| 9 |
| If you need to load another MIDS, change loading cable to the other MIDS and repeat from step 6. |
| 10 |
| If you are done loading, select "No" on the pop-up window. |
| 11 |
| Save database by selecting File-->Save Database |
| 12 |
| Exit out of SKL software after saving database by selecting File-->Exit |
7.3 Initializing Gateway EOC MIDS
| 1 |
| Connect Gateway EOC MIDS to the IES on your test line. |
| Use patch panel connections to connect GW MIDS to IES |
Test Line 1: GSIL-TL1-IES
Test Line 2: GSIL-TL2-IES
Test Line 3: GSIL-TL3-IES
Test Line 4: GSIL-TL4-IES
Test Line 5: GSIL-TL5-IES
| 2 |
| Log in to the IES server to which you patched your GW MIDS. |
| 3 |
| On the IES server, start the CUI application by clicking on the CUI icon on the desktop. |
| 4 |
| On the "Link 16 Application Controller" screen, select "GW EOC MIDS" and press the "Start" button. |
| 5 |
| A window called "Terminal Control" will pop up. Wait until the "Connection Status" at the bottom of this window says "OK". |
| This can take up to 15 seconds. |
| 6 |
| On the "Terminal Control" window, select "IDL Load" |
| 7 |
| Navigate to /mnt/gsil_share/Test Tools/IES Folder/ADSI Load Files/High Track Load IDL |
| 8 |
| In this folder, select "USAT0041C_REV_00_IBCS_J1.PLJ" |
| 9 |
| On the next pop up window, click "Load" |
| 10 |
| Wait for the load file to load and a "Quick Net Entry" window to pop up. |
| This can take up to 15 seconds. |
| 11 |
| In the "Own Unit" box, type in the EOCs JU. (ex. 54) |
| Our GW EOCs are set to JU 54. |
| 12 |
| In the "Antenna Position" box, in the "Latitude" field, set your latitude. (ex. N 36) |
| These three fields set where your GW EOC with transmit its PPLI from. |
| 13 |
| In the "Antenna Position" box, in the "Longitude" field, set your longitude. (ex. W 086) |
| 14 |
| In the "Antenna Position" box, in the "Altitude" field, set your altitude. (ex. 190.0) |
| 15 |
| In the "Network Participation" box, check the box by "Network Time Reference" and click ok in the pop-up confirmation box. |
| 16 |
| In the "Network Participation" box, check the box by "Start Net Entry" |
| 17 |
| In the "Network Time" box, select "Set Terminal Time" |
| 18 |
| Set time to a time in the future. (~5-10 seconds in the future) |
| 19 |
| Approximately one second before the time you set arrives, hit the "Apply" button at the bottom of the "Quick Net Entry" window. |
| 20 |
| Exit out of the "Quick Net Entry" window. |
| 21 |
| On the "Terminal Control" window, verify: |
Sync State = Fine
TQ and Network Parameter = 15 | NTR
| 22 |
| Exit out of "Terminal Control" window. |
| 23 |
| Patch GW EOC MIDS back into GW EOC 60 VLAN on Patch Panel |
7.4 Initializing External L16 MIDS
| 1 |
| Connect External L16 MIDS to the IES on your test line. |
| Use patch panel connections to connect External L16 MIDS to IES |
Test Line 1: GSIL-TL1-IES
Test Line 2: GSIL-TL2-IES
Test Line 3: GSIL-TL3-IES
Test Line 4: GSIL-TL4-IES
Test Line 5: GSIL-TL5-IES
| 2 |
| Log in to the IES server to which you patched your External L16 MIDS. |
| 3 |
| On the IES server, start the CUI application by clicking on the CUI icon on the desktop. |
| 4 |
| On the "Link 16 Application Controller" screen, select "IES MIDS" and press the "Start" button. |
| 5 |
| A window called "Terminal Control" will pop up. Wait until the "Connection Status" at the bottom of this window says "OK". |
| This can take up to 15 seconds. |
| 6 |
| On the "Terminal Control" window, select "IDL Load" |
| 7 |
| Navigate to /mnt/gsil_share/Test Tools/IES Folder/ADSI Load Files/High Track Load IDL |
| 8 |
| In this folder, select "USAT0041C_REV_00_IES_J1.PLJ" |
| 9 |
| On the next pop up window, click "Load" |
| 10 |
| Wait for the load file to load and a "Quick Net Entry" window to pop up. |
| This can take up to 15 seconds. |
| 11 |
| In the "Own Unit" box, type in the EOCs JU. (ex. 33) |
| Our IES scripts set the to JU 33. |
| 12 |
| In the "Antenna Position" box, in the "Latitude" field, set your latitude. (ex. N 36) |
| These three fields set where your External L16 with transmit its PPLI from. |
| 13 |
| In the "Antenna Position" box, in the "Longitude" field, set your longitude. (ex. W 086) |
| 14 |
| In the "Antenna Position" box, in the "Altitude" field, set your altitude. (ex. 190.0) |
| 15 |
| In the "Network Participation" box, make sure the box by "Network Time Reference" is unchecked. |
| 16 |
| In the "Network Participation" box, check the box by "Start Net Entry" |
| 17 |
| In the "Network Time" box, select "Set Terminal Time" |
| 18 |
| Set time to a time in the future. (~5-10 seconds in the future) |
| 19 |
| Approximately two to three second before the time you set arrives, hit the "Apply" button at the bottom of the "Quick Net Entry" window. |
| 20 |
| Exit out of the "Quick Net Entry" window. |
| 21 |
| On the "Terminal Control" window, verify: |
| TQ may fluctuate between 10 and 15 but verify you are in FINE sync or your radios will not pass data. |
Sync State = Fine
TQ and Network Parameter = 15 | Non-NTR
| 22 |
| Exit out of "Terminal Control" window. |
7.5 Powering MIDS off at End of Day
| 1 |
| On the right side of the MIDS by the LED screen, there is a rotary switch in the shape of a tear. Push in and rotate that switch into the "OFF" position. |
| 2 |
| On the left side of the MIDS, there is a toggle switch in between multiple cables. Flip the switch down to power the MIDS off. |
8. IES
IES
| Step Number: |
| Action: |
| Notes: |
8.1 IES Start of Day Procedure
| 1 |
| Navigate to correct machine(s) depending on the test line you are on through the KVM and log in. |
Test Line 1: GSIL-TL1-IES
Test Line 2: GSIL-TL2-IES
Test Line 3: GSIL-TL3-IES
Test Line 4: GSIL-TL4-IES
Test Line 5: GSIL-TL5-IES
| 2 |
| Start the iMon client on each box you are collecting data on by double clicking on the start_imon_client.bat icon on the desktop. |
8.2 To Start IES Prior to Each Run
| 1 |
| Launch the IES application by click on the IES icon with the correct version number in the icon title. |
| Ask the TC which IES version you should use. |
| 2 |
| Start data recording by clicking Data Recording-->Data Recording Control |
| 3 |
| In the pop-up window, fill out the following fields: |
| To set the recording file name, click on browse and type in your filename in the "Save As" pop-up. |
Recording Control = B - Begin
Recording File Name = MMDD-RR_IES.REC
Where:
MM = Month of the Year (ex. 05-May)
DD = Day of the Year (ex. 20)
RR = Run Number (ex. 01)
| 4 |
| Click start in the "Data Recording Control" window. |
| 5 |
| Start scenario file in IES by clicking Script-->Script Control |
| 6 |
| In the "Script Control" pop-up window, select your script file: |
| Ask the TC which script file to use. |
NEA_TQ8.ist
WSMR_TQ8.ist
| 7 |
| Select "OK" to run the script file and wait on the script to finish running. |
| 8 |
| If using the GR_Aircraft file, wait until the scenario starts and all tracks as a PPLI changing "TN" field and "STN" number for each track. |
| Ask a SME to show you the first time. |
8.3 To Stop IES After Each Run
| 1 |
| After each run, simply exit out of the IES application. |
8.4 IES End of Day Procedures
| 1 |
| At the end of the day, you must process the data using the IES application with the same version you used for the run. To process the data: |
Launch the IES application by click on the IES icon with the correct version number in the icon title.
Select Data Recording-->Off-line DX Control
Select the following files:
Input File: MMDD-RR_IES.REC
Output File: MMDD-RR_IES.RED
Click "OK" to proceed with data processing.
Repeat for each run completed for the day.
| 2 |
| Move the data to the gsil share using the "move_data_ies_v_x.x.x" batch file. |
| This moves .rec file, .red files, .log files, and .exp files. |
| 3 |
| Exit out of IES application and sign off of the IES box. |
9. EOC
EOC
| Step Number: |
| Action: |
| Notes: |
9.1 EOC Start of Day
| 1 |
| Log in to an EOC workstation. |
| 2 |
| Open a terminal. |
| 3 |
| If you logged into an account without admin privileges, become and admin by typing: |
sudo oone
| 4 |
| Open as many terminals as you have EOCs and type: (per EOC) |
ssh -Xo serverkeepaliveinterval=60 oone@2600:0:c:xxxx::17 (go51601)
9.1.1 To Set or Clear Gateway Node
| 1 |
| To set EOC as gateway node (node where external Link 16 data comes in), in the terminal as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
/opt/integ/tools/setGateway (setGateway)
| 2 |
| To clear EOC as gateway node, in the terminal as admin, type: |
| Only 1 Gateway EOC allowed per task force. |
/opt/integ/tools/clearGateway (clearGateway)
9.1.2 To Check Status of EOC Software
| 1 |
| To check status of C2 software, in terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/statusIBCS (status)
| 2 |
| To check status of B-Side software, in terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/statusBside (statusb)
| 3 |
| Verify all Cis are un-instantiated. If not stop software by following the steps in the Stop EOC Software section. |
| 4 |
| Verify all Cis are enabled. If not, fix the CI that is not enabled by following the steps in the Fix EOC Software section. |
9.1.3 To Stop EOC Software
| 1 |
| To stop C2 software, in the terminal, as admin, type: |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/stopIBCS (cstop)
| 2 |
| To stop B-Side software, in the terminal, as admin, type: |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/stopBside (cstopb)
9.1.4 To Fix Disabled CIs
| 1 |
| To fix disabled C2 CIs, in the terminal, as admin, type: |
| Report disabled CIs to the TC |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/os_control.sh repaired <CI> (fixdisabled <CI>)
| 2 |
| To fix disabled B-Side CIs, in the terminal, as admin, type: |
| Report disabled CIs to the TC |
ssh -Xo serverkeepaliveinterval=60 localadmin@standin3 (gostandin3)
Once you are on Standin3, type:
/opt/integ/tools/os_control.sh repaired <CI> (fixdisabled2 <CI>)
9.1.5 To Clean Logs on the EOC
| 1 |
| To clean EOC logs, in the terminal, as admin, type: |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/cleanLogs -b (cleanlog)
9.2 EOC Start of Run Procedures
9.2.1 To Load, Wipe, and Snap Priors on the EOC
| 1 |
| To load priors on the EOC, in the terminal, as admin, type: |
| Ask TC which priors you need to load prior to each run. |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
(loadlongtermdb)
| 2 |
| To wipe priors on the EOC, in the terminal, as admin, type: |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
(wipelongtermdb)
| 3 |
| To snap priors on the EOC, in the terminal, as admin, type: |
| Snapping of priors are done after every GR run. |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
(snaplongtermdb)
9.2.2 Start EOC Software
| 1 |
| Once the TC gives you the go ahead, you can start software on the EOCs and Relays. To start the C2 software on the EOCs, in the terminal, as admin, type: |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/startIBCS (cstart)
| 2 |
| Once the TC gives you the go ahead, you can start software on the EOCs and Relays. To start the B-Side software on the EOCs, in the terminal, as admin, type: |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/startBside (cstartb)
9.2.3 To Check Status of EOC Software
| 1 |
| To check status of C2 software, in terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/statusIBCS (status)
| 2 |
| To check status of B-Side software, in terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/statusBside (statusb)
| 3 |
| Verify all Cis are instantiated and enabled. |
9.3 Start CWMI
9.3.1 Start CWMI Application
| 1 |
| Once all software is instantiated and enabled, you can start the CWMI application. To do so, click Applications--> IBCS--> IBCS from the menu bar on the EOC workstation. |
9.3.2 Start Video Capture on Each Workstation Using CWMI
| 1 |
| Once you start the CWMI application, you need to start a video capture for each CWMI instance in the task force. To do so, first open up the VLC Media Player software by clicking Applications -->Sound and Video-->VLC Media Player |
| 2 |
| Once the "VLC Media Player" window pops up, you must set your options for video recording. To do so, click Media-->Options. |
| 3 |
| Set the following settings in the pop-up window. |
Capture Mode = Desktop
Frames per Second = 10.00 f/s
| 4 |
| Check and fix settings inside convert. To do so, click the arrow beside "Play" and select "Convert" from the dropdown. |
| 5 |
| Set the following settings in the pop-up window: |
Verify CODEC is set to:
Video-H.264 + AAC (MP4)
Select "Browse" and navigate to /opt/ibcs/logs/ui/iuicli and save file with the name MMDD-RR_EOCxxxxx_STzz
Where:
MM = Month of the Year (ex. 05-May)
DD = Day of the Year (ex. 20)
RR = Run Number (ex. 01)
XXXXX = EOC Number (ex. 51601)
ZZ = Workstation Number (ex. 05)
| 6 |
| Start Recording by clicking "Start" |
9.4 Log in to Roles on CWMI
| 1 |
| Once the CWMI application has started, you will see a black screen and a small box in the upper left corner. You must select an operator role to continue loading CWMI. |
| Each EOC should have at least 1 FCO. |
| 2 |
| Select your operator role, click "OK", confirm on the next pop-up and wait on the CWMI to load completely. This is usually signaled by the loading of the map. |
| This can take up to 3 minutes. |
9.5 Activating a Defense Plan from CWMI
| 1 |
| To activate a defense plan, you must open the IDD tab at the top of the CWMI screen. To do so, click on the "IDD" tab on the top of CWMI. |
| 2 |
| You must now open "File Manager" by clicking on the "File Manager" button on the left-hand side of the "IDD" tab. |
| 3 |
| Once the "File Manager" window pops up, navigate to the desired defense plan and highlight it. |
| Get the desired defense plan name from the TC. |
| 4 |
| If the defense plan hasn't been approved, approve it by highlighting the plan and click the "Approve" button on the top of the "File Manager" pop-up. |
| 5 |
| If the defense plan has been approved, verify the defense plan name with the TC, highlight the defense plan, and click the "Activate" button on top of the "File Manager" pop-up. |
9.6 Change EOC Operation Mode
| 1 |
| To change the EOC operation mode, you must open up the "EOC Manager" window. To do so, select the "Equipment" tab and click "EOC Manager" |
| 2 |
| When the "EOC Manager" window pops up, select the "Settings" tab. |
| 3 |
| Change the EOC to the desired operation mode by clicking Edit and set the following settings: |
| The mode tells the software if your EOC is ready to participate in the battle or not. |
State = Operations
Mode = AMD_Operations
9.7 Sensors
| 1 |
| To verify you have sensors and/or launchers in the network, you must open "Health and Status". To do so, click on the "Equipment" tab on top of CWMI and then click on "Health and Status". |
| 2 |
| Verify green sensors on the “Health and Status" window. |
9.7.1 RIU
9.7.1.1 Initialize RIUs from Pre-Created Database on the RIU
| 1 |
| To initialize the RIU from a pre-created database, you must open up the "Sensor Manager" window. To do so, select the "Equipment" tab and click "Sensor Manager" |
| 2 |
| In the "Sensor Manager" window, select the RIU you wish to initialize from the pre-created databases in the RIU. |
| 3 |
| With the sensor selected, select the "Patriot Initialization" tab for that RIU. |
| 4 |
| On the "Patriot Initialization" tab, change the "Initialization Method" dropdown to "Load Database" and click on the "Load Database" button. |
| 5 |
| In the pop-up window, select the TACI database you want to load and click the "Load" button. Confirm the TACI and wait until you receive a "State Mode Transition" pop-up window. |
| This step will take between 30 seconds and 2 minutes. |
| 6 |
| When the "State Mode Transition" window pops up, select the RIU and click the "Proceed" button. |
| You only have 5 minutes to proceed or you will have to restart the RIU. |
| 7 |
| Verify on the "Health and Status" window that the RIU has transitioned to "Remote_Standby" |
9.7.1.2 Initialize RIUs via Mission Planning
| 1 |
| To initialize the RIU via mission planning, you must open up the "Sensor Manager" window. To do so, select the "Equipment" tab and click "Sensor Manager" |
| 2 |
| In the "Sensor Manager" window, select the RIU you wish to initialize via mission planning. |
| 3 |
| With the sensor selected, select the "Patriot Initialization" tab for that RIU. |
| 4 |
| Ensure that the defense plan you have chosen has all RIU buffer parameters populated. |
| 5 |
| On the "Patriot Initialization" tab, change the "Initialization Method" dropdown to "Buffer Transfer" and click on the "Send Initialization Data" button. |
| The buffer transfer begins immediately. |
| 6 |
| Observe RIU Initialization status (checkmarks) on the "Patriot Initialization" tab. |
| 7 |
| Select "Confirm Initialization" on the Patriot Initialization Screen |
| The ends the buffer transfer. |
| 8 |
| Wait until you receive a "State Mode Transition" pop-up window. |
| This step will take between 30 seconds and 2 minutes. |
| 9 |
| When the "State Mode Transition" window pops up, select the RIU and click the "Proceed" button. |
| You only have 5 minutes to proceed or you will have to restart the RIU. |
| 10 |
| Verify on the "Health and Status" window that the RIU has transitioned to "Remote_Standby" |
9.7.1.3 Loading Priors on an RIU
| 1 |
| To load priors on an RIU, you must open up the "Sensor Manager" window. To do so, select the "Equipment" tab and click "Sensor Manager" |
| 2 |
| In the "Sensor Manager" window, select the RIU you wish to load priors on. |
| 3 |
| Select the "Geodetic Registration" tab on the RIU you wish to load priors on. |
| 4 |
| Scroll to the bottom of the "Geodetic Registration" tab and click on the "Manage Priors" button. |
| 5 |
| In the "Manage Priors" window inside "Sensor Manager", click the type of priors you wish to load from the dropdown and click "Initialize" and click "Confirm" on the confirmation pop-up window. |
9.7.1.4 Radiating the RIU
| 1 |
| To radiate an RIU, you must open up the "Sensor Manager" window. To do so, select the "Equipment" tab and click "Sensor Manager" |
| 2 |
| In the "Sensor Manager" window, select the RIU you wish to radiate. |
| 3 |
| Select the "Settings" tab on the RIU you wish to radiate. |
| 4 |
| On the "Settings" tab, click the "Edit" button and set the following, apply, and confirm: |
Platform Mode = Remote_Active
| 5 |
| Verify with RIU operator that no one is in the area of the radar. |
| This is done for the Real RIU with a real radar. |
| 6 |
| On the "Settings" tab, click the "Edit" button and set the following, apply, and confirm: |
Sensor Mode = Radiating_ABT_TBM
Passive Search = Off
ECCM = On
GLIF = Horizon
TWS = Auto
Helo Discrimination = On
| 7 |
| On the "Sensor Manager" tab, select "Diagnostic and Maintenance" |
| 8 |
| Select "Continuous Diagnostics" and set to "On" |
9.7.2 Sentsim
9.7.2.1 Loading Priors on Sentsim
| 1 |
| To load priors on a Sentsim, you must open up the "Sensor Manager" window. To do so, select the "Equipment" tab and click "Sensor Manager" |
| 2 |
| In the "Sensor Manager" window, select the Sentsim you wish to load priors on. |
| 3 |
| Select the "Geodetic Registration" tab on the Sentsim you wish to load priors on. |
| 4 |
| Scroll to the bottom of the "Geodetic Registration" tab and click on the "Manage Priors" button. |
| 5 |
| In the "Manage Priors" window inside "Sensor Manager", click the type of priors you wish to load from the dropdown and click "Initialize" and click "Confirm" on the confirmation pop-up window. |
9.8 Launchers
| 1 |
| To verify you have sensors and/or launchers in the network, you must open "Health and Status". To do so, click on the "Equipment" tab on top of CWMI and then click on "Health and Status". |
| 2 |
| Verify green launchers on the “Health and Status" window. |
9.8.1 Emplacing Launchers
9.8.1.1 Automatic Emplacement of Multiple Launchers
| 1 |
| To emplace launchers, you must open up the "Launcher Manager" window. To do so, select the "Equipment" tab and click "Launcher Manager" |
| 2 |
| Multi-select all launcher you wish to emplace. |
| 3 |
| Select the "Emplacement" tab and click "Auto-Emplace". |
| 4 |
| Wait for launcher to provide data back to the EOC and CWMI. |
| This step will take approximately 2 minutes and up to 4 minutes. If after 4 minutes you have not gotten data back for all launchers, continue to the next step and go back and single emplace remaining launchers. |
| 5 |
| Observe "Data Received" for all selected launchers in Emplacement Data Status. Click "Confirm Auto-Emplacement" to emplace all launchers. |
| If all launchers didn't give you values back, the launchers that did not receive emplacement data will need to be handled individually and on a case by case basis |
9.8.1.2 Automatic Emplacement of a Single Launcher
| 1 |
| To emplace a launcher, you must open up the "Launcher Manager" window. To do so, select the "Equipment" tab and click "Launcher Manager" |
| 2 |
| Select the launcher you want to emplace in the "Launcher Manager" tab. |
| 3 |
| Ensure that the automatic radio button is selected and click the "Begin" button. |
| 4 |
| Verify there are values in the Latitude and Longitude boxes and click "Confirm" |
| 5 |
| Wait for launcher emplacement HAVCO on the bottom of the launcher manager screen. DO NOT CLICK OFF OF THIS LAUNCHER. |
| This step will take approximately 2 minutes and up to 4 minutes. If after 4 minutes you have not gotten data back for all launchers, continue to the next step and go back and single emplace remaining launchers. |
| 6 |
| When you receive the HAVCO, verify that you have received data by confirming data is populated. |
| Verify that Lat., Lon., Alt., and Az. Fields are non-zero values. |
| 7 |
| Click "Emplace Launcher" to emplace the launcher. |
9.8.1.3 Manual Emplacement of a Single Launcher
| 1 |
| To emplace a launcher, you must open up the "Launcher Manager" window. To do so, select the "Equipment" tab and click "Launcher Manager" |
| 2 |
| Select the launcher you want to emplace in the "Launcher Manager" tab. |
| 3 |
| Ensure that the manual radio button is selected and click the "Begin" button. |
| 4 |
| Manually enter emplacement data in the Latitude, Longitude, Altitude, Azimuth, Roll, and Cross Roll fields |
| 5 |
| Click "Emplace Launcher" to emplace the launcher. |
9.8.2 Changing State Mode of a Launcher
| 1 |
| To change state mode of a launcher, you must open up the "Launcher Manager" window. To do so, select the "Equipment" tab and click "Launcher Manager" |
| 2 |
| Select the launcher(s) you want to change the state mode of in the "Launcher Manager" tab. |
| 3 |
| In the "Launcher Manager" tab, select the "Settings" window of the launcher(s) you wish to change the state mode of and click "Edit". |
| 4 |
| Change the "State Mode" dropdown to "Remote Active", click "Apply" and "Confirm" |
9.9 EOC End of Run Procedure
9.9.1 EOC Shutdown Procedure
| 1 |
| To stop C2 software, in the terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/stopIBCS (cstop)
| 2 |
| To stop B-Side software, in the terminal, as admin, type: |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/stopBside (cstopb)
9.9.2 To Check Status of EOC Software
| 1 |
| To check status of C2 software, in terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/statusIBCS (status)
| 2 |
| To check status of B-Side software, in terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/statusBside (statusb)
| 3 |
| Verify all Cis are un-instantiated. If not stop software by following the steps in the Stop EOC Software section. |
| 4 |
| Verify all Cis are enabled. If not, fix the CI that is not enabled by following the steps in the Fix EOC Software section. |
9.9.3 To Fix Disabled CIs
| 1 |
| To fix disabled C2 CIs, in the terminal, as admin, type: |
| Report disabled CIs to the TC |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/os_control.sh repaired <CI> (fixdisabled <CI>)
| 2 |
| To fix disabled B-Side CIs, in the terminal, as admin, type: |
| Report disabled CIs to the TC |
ssh -Xo serverkeepaliveinterval=60 localadmin@standin3 (gostandin3)
Once you are on Standin3, type:
/opt/integ/tools/os_control.sh repaired <CI> (fixdisabled2 <CI>)
9.9.4 Harvesting EOC Data
| 1 |
| To harvest EOC data, in the terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/runHarvester -v -A -d <loc>_mmdd-rr (harvest <loc>_mmdd-rr)
Where:
MM = Month of the Year (ex. 05-May)
DD = Day of the Year (ex. 20)
RR = Run Number (ex. 01)
<loc> = Test Line (ex. GTL1)
| 2 |
| Verify Harvest runs correctly and there are no errors in the terminals. |
9.9.5 Cleaning EOC Logs After Harvest
| 1 |
| To clean EOC logs, in the terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 oone@bs1 (go bs1)
Once you are on BS1, type:
/opt/integ/tools/cleanLogs -b (cleanlog)
10 RELAY
Relay
| Step Number: |
| Action: |
| Notes: |
10.1 Relay Start of Day
| 1 |
| Log in to an EOC workstation. |
| 2 |
| Open a terminal. |
| 3 |
| Open as many terminals as you have Relays and type: (per relay) |
ssh -Xo serverkeepaliveinterval=60 localadmin@2600:0:c:xxxx::xx (go6xxxx)
10.1.1 To Check Status of Relay Software
| 1 |
| To check status of Relay software on Standin4 server, in terminal, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
type /opt/integ/tools/statusIBCS (statusr)
| 2 |
| Verify all Cis are uninstantiated. If not stop software by following the steps in the Stop Relay Software section. |
| Inform the Test Conductor of what Cis are un-instantiated |
10.1.2 To Stop Relay Software
| 1 |
| To stop Relay software, in the terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 localadmin@2600:0:c:xxxx::xx (go6xxxx)
Once you are on Standin4, type:
/opt/integ/tools/stopIBCS (cstopr)
| 2 |
| Verify all Cis are enabled. If not, fix the CI that is not enabled by following the steps in the Fix Relay Software section. |
| Inform the Test Conductor of what Cis are un-instantiated |
10.1.3 To Fix Disabled CIs
| 1 |
| To fix disabled Relay CIs, in the terminal, type: |
| Report disabled CIs to the TC |
ssh -Xo serverkeepaliveinterval=60 localadmin@2600:0:c:xxxx::xx (go6xxxx)
Once you are on Standin4, type:
/opt/integ/tools/os_control.sh repaired <CI> (fixdisabledr <CI>)
10.2 Relay Start of Run Procedures
10.2.1 Start Relay Software
| 1 |
| Once the TC gives you the go ahead, you can start software on the Relays. To start the Relay software, in the terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 localadmin@2600:0:c:xxxx::xx (go6xxxx)
Once you are on Standin4, type:
/opt/integ/tools/startIBCS (cstartr)
10.2.2 To Check Status of Relay Software
| 1 |
| To check status of Relay software on Standin4 server, in terminal, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
type /opt/integ/tools/statusIBCS (statusr)
| 2 |
| Verify all Cis are uninstantiated. If not stop software by following the steps in the Stop Relay Software section. |
| Inform the Test Conductor of what Cis are un-instantiated |
10.3 Relay End of Run Procedure
10.3.1 Relay Shutdown Procedure
| 1 |
| To stop C2 software, in the terminal, as admin, type: |
ssh -Xo serverkeepaliveinterval=60 localadmin@2600:0:c:xxxx::xx (go6xxxx)
Once you are on Standin4, type:
/opt/integ/tools/stopIBCS (cstopr)
10.3.2 To Check Status of Relay Software
| 1 |
| To check status of Relay software on Standin4 server, in terminal, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
type /opt/integ/tools/statusIBCS (statusr)
| 2 |
| Verify all Cis are uninstantiated. If not stop software by following the steps in the Stop Relay Software section. |
| Inform the Test Conductor of what Cis are un-instantiated |
| 3 |
| Verify all Cis are enabled. If not, fix the CI that is not enabled by following the steps in the Fix Relay Software section. |
10.3.3 To Fix Disabled CIs
| 1 |
| To fix disabled Relay CIs, in the terminal, as admin, type: |
| Report disabled CIs to the TC |
ssh -Xo serverkeepaliveinterval=60 localadmin@2600:0:c:xxxx::xx (go6xxxx)
Once you are on Stanidn4, type:
/opt/integ/tools/os_control.sh repaired <CI> (fixdisabledr <CI>)
10.3.4 Harvesting Relay Data
| 1 |
| To harvest Relay data, in the terminal, as admin, type: |
| Type in path or if you have aliases on the EOC, you can type in the alias that is in (). |
ssh -Xo serverkeepaliveinterval=60 localadmin@2600:0:c:xxxx::xx (go6xxxx)
Once you are on Standin4, type:
/opt/integ/tools/runHarvester -v -A -d <loc>_mmdd-rr (harvest <loc>_mmdd-rr)
Where:
MM = Month of the Year (ex. 05-May)
DD = Day of the Year (ex. 20)
RR = Run Number (ex. 01)
<loc> = Test Line (ex. GTL1)
| 2 |
| Verify Harvest runs correctly and there are no errors in the terminals. |
10.3.5 Cleaning Relay Logs after Harvest
| 1 |
| To clean Relay logs, in the terminal, as admin, type: |
ssh -Xo serverkeepaliveinterval=60 localadmin@2600:0:c:xxxx::xx (go6xxxx)
Once you are on Standin4, type:
/opt/integ/tools/cleanLogs -b (cleanlogr)
11 ADSI
ADSI
| Step Number: |
| Action: |
| Notes: |
11.1 To Start ADSI RUN
| 1 |
| Log into any CWMI workstation, with the exception of the AMDWS, on the EOC you are wanting to use the ADSI on and open a terminal. |
| 2 |
| Log onto BS2 by typing: |
| These two steps can be combined by using the (goadsi) alias. |
ssh -X bs2
| 3 |
| Remote Desktop into the ADSI by typing: |
xfreerdp -g 90% --no-nla xxx.xxx.xx.111
| 4 |
| Log into the ADSI using the username and password provided. |
| 5 |
| Once logged in, start the ADSI software by clicking on the V15 icon on the Desktop. |
| Verify that both System Manager and DXview opens |
| 6 |
| Click Start in lower right hand window of the system manager window. |
Wait for Data Links to go “OPER” and turn green
| 7 |
| Load the correct site data by clicking on the Site Data tab and clicking Load Site. |
Select the correct site in the pop up window and select load.
| 8 |
| Set the data recording by selecting the DX Control tab and set the following: |
Data Links C2 Host: OFF
Data Links TDLG: OFF
Data Links GREEN Links: MSG
Intel/Secondary Links IBCS: MSG
Click Apply
11.2 To Stop Run and Harvest Run Data
| 1 |
| To stop the data recording for the run, in the DX View window, select D10 icon to start new recording for the next run. |
| 2 |
| Create directory if not already done by clicking on the ADSI.bat file on the Desktop and following prompts. |
| 3 |
| Harvest data to directory by clicking on the ADSI.bat file on the Desktop and following the prompts. |
11.3 End of Day ADSI Procedures
| 1 |
| To stop the ADSI software, click stop in lower right hand corner of the System Manager window. |
| 2 |
| Once it has stopped close all ADSI applications: |
System manager
DX View
TacViewC2
| 3 |
| Move all harvested data to BS1 by selecting the ADSI.bat file on the Desktop of ADSI and following prompts. |
| 4 |
| Close ADSI Remote Desktop |
12 LINKS
LINK
| Step Number: |
| Action: |
| Notes: |
12.1 To Start the LINK Box
| 1 |
| Verify that LOTN is up and running. |
| 2 |
| Verify which LINK(s) the TC needs you to start. |
| 2 |
| Locate the LINK box(es) to be started and flip the POWER toggle switch from OFF-->ON. |
12.2 To Stop the LINK Box
| 1 |
| Locate the LINK box(es) to stop and flip the POWER toggle switch from OFF-->ON. |
13 L2 L2
| Step Number: |
| Action: |
| Notes: |
13.1 L2 Start of Day Procedure
| 1 |
| Navigate to correct machine(s) depending on the test line you are on through the KVM and log in. |
Test Line 1: GSIL-TL1-L2A
GSIL-TL1-L2B
GSIL-TL1-L2C
GSIL-TL1-L2D
GSIL-TL1-L2E
Test Line 2: GSIL-TL2-L2A
GSIL-TL2-L2B
Test Line 3: GSIL-TL3-L2A
GSIL-TL3-L2B
Test Line 4: GSIL-TL4-L2A
Test Line 5: GSIL-TL5-L2A
GSIL-TL5-L2B
| 2 |
| Clear the processes in case and L2 process is running on the server by clicking the FIX icon on the Desktop. |
| 3 |
| Open the L2 Application by clicking on the L2 Icon on the Desktop. |
13.2 To Start L2 for Each Run
| 1 |
| Edit the following by selecting Run-->Data Collection Parameters from the L2 GUI: |
Run Number
Julian Date
Output Directory
| 2 |
| Verify that the LOTN application is up started. |
| 3 |
| Verify which L2(s) the TC wishes for you to start. |
| 4 |
| Power on the L2(s) needed by clicking on Power-->Power On on each L2 instance needed. |
13.3 To Stop the L2 Application
| 1 |
| To power off the L2(s), on the L2 Application, click Power-->Power Off on each L2 instance you wish to power off. |
14 SENTSIM
Sentsim:
| Step Number: |
| Action: |
| Notes: |
14.1 Sentsim Start of Day Procedure
| 1 |
| Navigate to correct machine(s) depending on the test line you are on through the KVM and log in. |
Test Line 1: GSIL-TL1-SSIM1
GSIL-TL1-SSIM2
GSIL-TL1-SSIM3
GSIL-TL1-SSIM4
Test Line 2: GSIL-TL2-SSIM1
GSIL-TL2-SSIM2
Test Line 3: GSIL-TL3-SSIM1
GSIL-TL3-SSIM2
Test Line 4: GSIL-TL4-SSIM1
Test Line 5: GSIL-TL5-SSIM1
GSIL-TL5-SSIM2
| 2 |
| Start iMon by clicking on the start_imon_win.bat icon on the Desktop. |
| Terminal window should launch and connect to iMon server |
14.2 To Start the Sentsim Application for a Run
| 1 |
| Verify which Sentsim(s) and which Sentsim locations are needed for the run from the TC. |
| 2 |
| Set the Sentsims location by clicking the change_sentsim_location.bat file on the Desktop and following prompts. |
| 3 |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .