IC-OUM-07000_2.0_B3.pdf

IC-OUM-07000 2.0

2/28/2018

Operator User Manual for Network Operations Center (NOC)

Date: 28 February 2018

Prepared by: Toan Vo

Operator User Manual for the Network Operations Center (NOC)

CHANGE LOG

CHANGE / REVISION RECORD

Revision Page(s) Description of Change Made By Date Approved By

1.0 All Initial Release Mike James

1.1 All Revision for Release

Andrew

Armstrong 2/6/2018

1.2 All

Additional Detail &

Formatting Toan Vo

2/27/2018

2.0 All Content change Jim DePersis 2/28/2018

Operator User Manual for the Network Operations Center (NOC)

Table of Contents

1. Introduction

1.1 General Information

1.1.1 Scope

1.1.2 Safety

1.1.3 Security

1.1.4 List of Abbreviations/Acronyms

1.2 Equipment Description

1.2.1 Equipment Characteristics, Capabilities, and Features

1.2.2 Equipment Data

1.3 Principles of Operation

2. Operating Instructions

2.1 Description and Use of Operator’s Controls and Indicators

2.2 Operation under Usual Conditions

2.2.1 Preparation for Operation

2.2.2 Operation

2.2.3 Termination

2.2.4 Removal

2.2.5 Preparation for Storage

2.2.6 Preparation for Shipment

2.3 Operation under Unusual Conditions

2.3.1 Unusual Environment

2.3.2 Emergency Procedures

3. Operator Maintenance Instructions

3.1 Troubleshooting

3.2 Maintenance Procedures

4. Special Tools/Installation Equipment

5. Appendix

Operator User Manual for the Network Operations Center (NOC)

Table of Figures Figure 1: NOC Racks 1 and 2 Figure 2: Radius Rack Figure 3: TAC Audio Recorder Figure 4: Typical Transit Cases Figure 5: Saiph's main interface Figure 6: Saiph RSOI Scanning Interface Figure 7: From left to right - CAC, EDI, FREDI & Scan Sheet Figure 8: RSOI with Status Indicators Figure 9: Saiph’s main interface Figure 10: Rigel interface Figure 11: Finding coordinates in Rigel Figure 12: Rigel Main Toolbar Figure 13: Entity Toolbar Figure 14: Rigel's Entity Table Figure 15: Rigel's Timeline Figure 16: Packager Figure 17: Take Home Package Builder Figure 18: Disc Burning Software Figure 19: Confirmation Window

List of Tables Table 1. NOC Clients and Servers

Operator User Manual for the Network Operations Center (NOC)

1. Introduction

1.1 General Information

1.1.1 Scope

The operator’s manual for the Network Operations Center (NOC) focuses on setting up the physical equipment, operating the included software, troubleshooting during an exercise, pack-out from exercise and general maintenance.

1.1.2 Safety

When moving the components of the NOC, most major items require a minimum of four personnel to lift.

The two main server racks require the use of a forklift or pallet jack for movement more than 1-2 meters distance. Take special care when trouble-shooting the systems to avoid electrical shock, which may cause serious injury and/or damage to the equipment. The Uninterruptable Power Supply (UPS) should be powered down and have the internal battery disconnected when being shipped.

1.1.3 Security

No part of the NOC’s hardware or software is classified. All personnel accessing the Network Operations Center will be required to check in with current staff and sign the visitors’ log. Computer access will be restricted to authorized users only that have access to an approved Smart Card and PIN for login. Use of backup firewire drives for post-exercise backup is restricted to the Ravenswood Solutions Network supervisors to ensure the proper safety and storage of exercise data.

1.1.4 List of Abbreviations/Acronyms

AAR After Action Review

AARP TL After Action Review Production Team Leader

CAC Common Access Card

COB Civilian On the Battlefield

DTHP Digital Take Home Package

DVR Digital Video Recorder

EDI Enhanced Dismount Instrumentation

Operator User Manual for the Network Operations Center (NOC)

FAE Field Application Engineer

FOB Forward Observation Base

FREDI First Responder Enhanced Dismounted Infantry

GPS Global Positioning System

GUI Graphic User Interface

HHV Hand Held Video

I&C Instrumentation and Communication

IED Improvised Explosive Device

Lane Referred to the geographical location training begins and ends

LOS Line Of Sight

MAARC Mobile After-Action Review Center

MGRS Military Grid Reference System

MILES Multiple Integrated Laser Engagement System

NOC Network Operation Center

NOTL Network Operations Team Leader

OC Observer/Controller

OPFOR Opposing Force

OUM Operators User Manual

PIN Personal Identification Number

PSOC Product Service Operation Center

RSOI Reception Staging Movement Integration

TAC Tactical Analysis Center

VTHP Video Take Home Package

XCTC eXportable Combat Training Capability

Operator User Manual for the Network Operations Center (NOC)

1.2 Equipment Description

The Network Operation Center is the heart of. All tracking information is first fed into the NOC before being sent to the Tactical Analysis Center for evaluation. The following components are common within a typical NOC:

Table 1. NOC Clients and Servers

Name Use

Gateway Servers (2) Controls network communications. one Primary, one backup

Logger Servers (2) Logs all Data. one Primary, one backup

Clients (4) Workstation to monitor network activities and to add/remove players.

Laptops (4) To provide offsite scanning during issuing of instrumentation

1.2.1 Equipment Characteristics, Capabilities, and Features

The NOC can contain as little as three server-grade computers to as many as 17 server-grade computers and four laptops, depending on the mission requirements. For the purposes of XCTC, it has been configured with no less than 17 computers and four laptops.

Operator User Manual for the Network Operations Center (NOC)

1.2.1.1 Functions of NOC Racks 1 & 2

Figure 1: NOC Racks 1 and 2

NOC Racks one and two contains up to six servers each for a total of 12 servers. These machines fall into three main groups:

a. Services: Gateway and Logger machines

b. Clients: Up to four client machines and four instrumentation issue laptops

c. Security: IPA, HBSS and Certificate Server

It is vitally important that only a supervisor, under the direction from the I&C Chief, can have access to computers within the Services or Security category. NOC Operators can and will be sitting in front of the Client computers to monitor the exercise, network, or to perform data entry.

Operator User Manual for the Network Operations Center (NOC)

1.2.1.2 Function of Radius Rack

Figure 2: Radius Rack

The Radius Rack contains the Radius Server, Network Firewall and a Cisco Switch. This is used to monitor the entire network and to remotely log into switches downrange. Under typical circumstances, this station should only be used by the supervisor. During setup or if the supervisors are not present, the Computer Operator may be asked by the supervisor to access the Radius server to report network status.

1.2.1.3 Function of Instrumentation Issue Laptops

The Instrumentation Issue Laptops, also known as the “RSOI laptops,” are used during the issue of instrumentations to soldiers prior to going down range. Their portability allows them to have direct access to the NOC via the network infrastructure while in a convenient location capable of accommodating a company of soldiers. The issuance of EDI/FREDI are usually perform inside the massive tent at Range Operations but offline issue can be done downrange. If so, the data is then taken back to the NOC for sync with the main database.

Operator User Manual for the Network Operations Center (NOC)

1.2.1.4 Function of Tactical Audio Recorder

Figure 3: TAC Audio Recorder

The Tactical Audio Recorder consist of a rack mounted server and associated audio equipment to record SINCGARS transmission. The recorder can record 16 channels of military tactical audio simultaneously.

1.2.1.5 Function of UPS

Each rack within the NOC contains its own UPS to provide emergency power in the event of a power outage. They are sealed lead-acid batteries with a voltage (in series) of up to 52V.

Operator User Manual for the Network Operations Center (NOC)

1.2.1.6 Transit Cases

Figure 4: Typical Transit Cases

The transit cases contain accessories such as mice, keyboard, monitors, TVs, DVD duplicator, printers and cables necessary to operate the NOC.

1.2.2 Equipment Data

Not Applicable

1.3 Principles of Operation

The NOC is the nexus feeding live data from soldiers and vehicles downrange to client stations Tactical Analysis Center and Common Operating Picture stations located in the Exercise Support Cell (ESC) and Range Operations. It is also where all incoming traffic from EDIs and FREDIs, including MILES data, is stored. Data recorded in the NOC is used by the TAC to create annotated packages for use in the Instrumented After-Action Review (AAR) at the Mobile After Action Review Centers (MAARCs).

2. Operating Instructions

The Network supervision will oversee the initial setup and training, of NOC operators

Operator User Manual for the Network Operations Center (NOC)

2.1 Description and Use of Operator’s Controls and Indicators Not Applicable

2.2 Operation under Usual Conditions

Under usual conditions, the NOC will operate in an air-conditioned building for approximately 1-2 months.

During setup period at an XCTC event, the NOC s usually operates for several hours and is turned off in the evening. Once RSOI commences and there is live tracking of soldiers and vehicles, the NOC will be on constantly except for scheduled maintenance. The scheduled maintenance can only be approved by the I&C Chief if deemed absolutely necessary to mission success. Otherwise, the NOC is expected to operate for the duration of the sustainment period of an exercise without shutting off.

2.2.1 Preparation for Operation

Carefully lower the NOC Racks and transit cases from the trailer with a forklift. Make sure the forklift operator is licensed. Once lowered, move the NOC racks and transit cases into the designated NOC building or trailer. If a trailer is used for the NOC, a forklift is required to lift the racks into the entrance.

Once inside the building, arrange the NOC racks in accordance with guidance from the. Network supervision will designate the location of each NOC rack for easy access to power and to lay network cables. Prior to installation, perform an inventory of the NOC racks and transit cases’ contents to confirm that the serial numbers and quantity matches what’s currently on the included hand receipt Form 2062.

2.2.1.1 Installation...

Once the inventory is completed, the Network supervision will provide detailed instruction on how to set up the NOC. The general steps are as follows:

a. Connect the UPS battery by opening the front panel secured by two Philips screws and power the UPS from the wall outlet

b. Plug peripherals such as mice, keyboards and monitors into their designated computers

c. Connect NOC TVs if necessary

d. Setup RSOI laptops for testing or training

Once major components of the NOC are in place, the Network supervision will provide instructions on how to network all NOC components together in addition to linking the NOC to the rest of the network.

2.2.1.2 Power-up and Initialize

Before turning on the NOC computers for the first time or during normal use, obtain a smart card and PIN from the Network supervision. Also, as a requirement, all NOC operators must complete the Cyber Awareness Training during the first week of setup.

a. Turn on a NOC Client or Laptop.

b. When prompted, enter the Hard Drive password to allow the computer to load the operating system. The Network supervision will provide the necessary passwords.

c. Once the operating system finishes loading, a Graphical User Interface (GUI) will appear asking for a user name and password. At this point, insert the smart card into the smart card reader and when prompted, enter the PIN.

2.2.2 Operation

Up to this point, the NOC operator has turned on the Client computers, decrypted the hard drive and successfully logged into the operating system using the assigned smart card and PIN. The following is an introduction to the Orion suite of software and how it applies to the NOC and its day to day operations

Orion is a software suite utilized across all three major departments such as the NOC, TAC and MAARC.

Specific applications within Orion will be installed on the various computer systems based on their functions. Within the NOC Client machines, Saiph is used to enter soldier and vehicle information to the database. Rigel is utilized to view live data and 3D avatars down range and the Take Home Package Builder is used to create the Digital Take Home Package (DTHP).

2.2.2.1 Saiph

To start Saiph, click on Applications > Orion > Saiph. It can take a few minutes to load. Once fully loaded, the Saiph interface will look like the following figure:

Operator User Manual for the Network Operations Center (NOC)

Figure 5: Saiph's main interface

2.2.2.1.1 Saiph during Instrumentation Issue

During RSOI, Saiph can be launched on the laptops to facilitate the scanning of soldiers CACs. To do so,

a. Select the “Update Interval” drop down menu and select the appropriate update interval. The Network supervision will provide this value, in milliseconds. The standard value equals three epics.

b. Click on “Scan New Entity” button in the top left corner to bring up the scan screen. At this point, a laser scanner must be attached to the RSOI laptops or client computer.

c. A screen will appear with five items to scan:

1. CAC barcode belonging to the solider receiving the tracker. The soldier’s name and rank will appear once scanned.

2. EDI or FREDI Barcode

3. EDI or FREDI net corresponds to the color dot next to the EDI/FREDI’s barcode. Once identified, scan the appropriate net on the scan sheet, provided by the Network supervision.

Operator User Manual for the Network Operations Center (NOC)

4. Type refers to the avatar intended for the solider. For example, if SGT George Armes is carrying an M4 to RSOI, select the “US-m-m4” barcode from the scan sheet which refers to US uniform, Male, M4. Check with Network supervision for the appropriate avatar for OP-FOR (Soldiers playing the opposing force or bad guys).

5. Scan either Save or Cancel on the scan sheet.

Figure 6: Saiph RSOI Scanning Interface

Operator User Manual for the Network Operations Center (NOC)

Figure 7: From left to right - CAC, EDI, FREDI & Scan Sheet

Once all necessary barcodes have been scanned, do not release the solider until the system indicate their tracker is reporting appropriate status as seen in the figure below:

Operator User Manual for the Network Operations Center (NOC)

Figure 8: RSOI with Status Indicators

There are five status indicators as seen in the top right corner of the figure above.

C = Communications. Established with a tower.

I = Initialization. Device is properly entered into the system.

T = Tracking. GPS signal established

K = Kill (Life Status). MILES is dead or alive.

M= MILES Status. System can read MILES PID

All indicators must be green before sending a soldier to the next station.

Operator User Manual for the Network Operations Center (NOC)

2.2.2.1.2 Saiph for Client computers

As seen in the beginning of Section 2.2.1, there are two primary ways to enter entities into the database either by scanning during RSOI or manually, as will be shown in this section. Saiph is also used to swap trackers in case a fault, defect, or damage was encountered downrange.

2.2.2.1.2.1 To Manually add a new Entity

Figure 9: Saiph’s main interface

In the main Saiph window,

• Click New

• Enter FREDI or EDI ID number in “Instrument ID” field.

• In the “Network ID” dropdown menu, select the correct net.

• In the Type drop down menu, select if it’s a human or vehicle and then select the appropriate models (avatar)

• Enter name and callsign in the appropriate field

Operator User Manual for the Network Operations Center (NOC)

• Select the soldier or vehicle’s proper unit (down to the platoon level) and click save.

• Verify C-I-T-K-M values are green in the entity table

2.2.2.1.2.2 Manually remove and swap entity

Verify with the FAE before attempting to deactivate any trackers currently down range.

• Click on Units tab

• Verify no units are hidden and select the tracker’s assigned unit (Platoon, Company, etc.)

• In entity table, type Ctrl + F and enter the tracker number to be removed. Notate all relevant info such as name, rank, and units.

• Once it shows up, deactivate the tracker

• Once deactivated, delete the tracker by clicking delete. Alternatively, rename the tracker and move to “Unknown” folder for troubleshooting. See guidance from Network supervision.

Repeat section 2.2.2.1.2.2 to add a new entity as a replacement. Range Ops will provide replacement tracker info including name and rank.

2.2.2.2 Rigel for Client Computers

NOC operators use Rigel to view entities currently down range, verify their 3D avatar or to assist TAC operators in troubleshooting network issues. The NOC operator should simply observe and not make any modification to the database or create any annotations unless specifically asked by TAC operators, AARPTL, Network supervision. For a more in-depth overview of Rigel, please refer to the TAC OUM (IC- OUM-8001) or ask the Network supervision during setup.

To start the Rigel Interface, click on Applications > Orion > Rigel. It can take several minutes to fully load this application.

Operator User Manual for the Network Operations Center (NOC)

Figure 10: Rigel interface

If a TV is connected to one of the Client computers, it’s desirable to move the map to the TV for a better view. Click File > External Map and this will remove the map from the main screen to an external window.

Simply drag the new map Window over to the TV.

One excellent feature of the map is if a tracked person or vehicle’s location is needed, simply place the curser on the map and the coordinates will appear at the bottom left corner in lat/long and MGRS.

Operator User Manual for the Network Operations Center (NOC)

Figure 11: Finding coordinates in Rigel

2.2.2.2.1 Home toolbar

The Home Toolbar under the Home tab at the top contains tools mostly for map manipulation. The descriptions below are for the icons from left to right.

Figure 12: Rigel Main Toolbar

• Activate Measuring tool – Click this icon, then on two points on the map. This will draw a line and have the measurement of the distance between the two points.

• Clear measuring points – This icon will clear any measuring points on the map. Another way is to right-click a measuring point and remove individual ones.

• Zoom to Sector – Click this icon and the click on the map and draw a square over an area to zoom. The computer will do its best to zoom in on the selected area.

• MRGS Location –Manually enter in a MRGS location and the map will drop a red pin and zoom into

Operator User Manual for the Network Operations Center (NOC)

2.2.2.2.2 Entity Toolbar

The Entity toolbar under the Entity tab provides tools for manipulating the appearance of the 3D entities on the map.

Figure 13: Entity Toolbar

• Track - Selecting an entity on the map or in the Entity Table and clicking on this icon. The entity will be centered on the map and followed.

• History - Selecting an entity on the map or in the entity table and clicking on this icon will create a dotted line of where this unit has been (good for tracking movement). Multiple entities can have their history displayed but must be enabled one at a time.

• Clear History – This will clear all the History lines shown on the map.

• All Entity Labels – This will show or hide all of the Entity labels on the map.

• Selected Entity Label – This will show or hide the Entity label of the selected entity.

• Info Box – This will show or hide the information box of the selected entity.

• Model Size – This menu changed the size of the models. It will be easier to track the models when the map is zoomed out but entity will not be to scale unless left at default.

• Force Color – This will change the color of the 3D model of the entity to its force color for easy distinction. Best used for close contact between friendly and opposing forces

• LOS – When an entity is selected, clicking this icon will show its line of sight.

• Kill Entity – When an entity is selected, clicking on this icon will change the entity’s status to killed. If an entity is attached to MILES, it will kill the MILES too.

• Resurrect Entity – This will resurrect the selected entity. It will also resurrect any MILES vest attached to the entity.

• Mount Entity – If the entity is a dismount, has a vehicle assigned to it, and has auto-mount turned off, this will mount the entity to the vehicle it is assigned to.

• Dismount Entity – This will make an entity dismount any vehicle it is in if auto-mount is turned off.

2.2.2.2.3 Entity Table

The bottom toolbar contains the Entity Table. The Entity table has a list of all the entities that are currently in the database.

Operator User Manual for the Network Operations Center (NOC)

Figure 14: Rigel's Entity Table

• The default selection is all, but can be narrowed down when a specific unit his selected in the Unit Selection menu.

• Any hidden units will not show up. Check Unit Selection tool.

• Any column can be sorted. Also, a nested sorted list can be accomplished by shift clicking the next column.

• To find an EDI quickly, click the entity table and press CTRL+F. This will open the find menu. Type in a name or an EDI number to narrow the results down to the desired EDI. Click the clear button to the right to have the list back to normal.

• Shows Communication, Initialization, Tracking, Kill and MILES status for all trackers within a selected unit.

2.2.2.2.4 Timeline

Next to the Entity Table is the Timeline which has DVR-like features and where live MILES events, emergencies or annotations are shown. One can go back in time to view previous events during the same Rigel session.

Operator User Manual for the Network Operations Center (NOC)

Figure 15: Rigel's Timeline

• Annotation – Any annotations created will show up here. Clicking on the annotation will cause the map to zoom into the location and start time of that annotation.

• Hit – If there were any shot lines recorded by the NOC, they would appear here. This is the victim of the shot. There might be unpaired shot lines, where the victim is known but not a shooter.

These are usually admin kills.

• Shot – This is the shooter of the shot line. When the time reaches this event, a shot line between the shooter and victim will be drawn on the map.

• Emergency Events – If the emergency beacon on a FREDI is activation, it would show up here.

• The Play line section is to navigate through the timeline. Clicking on this will take the user to that particular point in time.

• Play/Pause – Start or pause the live recording. If currently pause, for example when creating an annotation, click the button next to the play button will jump to current time (live).

• Rate – The operator can increase or decrease the play rate of the recorded data.

• Advance – Specify a jump time in the drop-down menu and click the corresponding arrows to just that amount of time into the past or future, up to current time.

• Jump to Time – If there is a specific time that is desired, type it in here and click the arrow.

• Annotations – The operator can narrow down the annotations in view on the Timeline by selecting the user who made it and the unit assigned.

2.2.2.2.5 Packager

Normally, NOC Operators do not create data packages while the exercise is live. However, in case of a complete power failure in the TAC, a NOC Client can be used to create a data package to take to an AAR.

When this happens, the NOC operator must work closely with the TAC Chief and TAC operators to create the correct data package. Always alert the Network supervision or Computer Operator IV if this happens as they can help bring the TAC online as quickly as possible.

Figure 16: Packager

• To create a package, start by clicking on the packager tab on the right. This will open the packager menu

• Set the date and time for the start and end point of the training iteration and then click Add. If there are multiple start and end times with large gaps in between, enter in the first start and end time, click add, then enter in any additional times and add after each one.

• Under the options menu, select the particular unit tracked by the operator for the AAR. Be sure to select any Vehicle unit, OPFOR Unit, Observer Unit and Neutral Unit relevant to that event.

• Under the Users options, select any TAC stations that were keeping track of this unit. This will copy any annotations during the time specified on those TAC stations.

• Under the Audio Channels option, select the correct Tactical Audio channel that was assigned for that TAC. If unsure, check with TAC Chief or AARPTL.

• Once all options are set correctly, click Create Package. This might take some time to create depending on length of iterations and how many units have been selected. If the package fails to create, notify the Network supervision or Computer Operator IV.

• Once the package passes, insert the media that it will be copied to for transport to the MAARC tent. Media might be a DVD or an external hard drive. Once it has been copied, pass the media off to the TAC Operator or AARPTL for verification before it is sent to the MAARC.

Once again, package creation at the NOC by NOC Operators are only for emergencies that warrants alerting the Network supervision to resolve.

2.2.2.3 Take Home Package Builder

A Digital Take Home Package (DTHP) is a DVD generated by the NOC of each package created in the TAC for they correspond to a unit and their instrumented AAR. This DVD contains the necessary executables to run Rigel on a Windows computer. It is assumed most soldiers at their home station will use computers running Windows. After installing the DTHP on to their computers, the soldiers can review the captured location and MILES data, through Rigel, from the comfort of their own home. This DTHP, used in conjunction with the Video Take Home Package (VTHP) available on the XCTC website can be powerful tools to reinforce learning objectives.

Click Application > Orion > Take Home Package Builder

Figure 17: Take Home Package Builder

A window similar to the figure above will open listing every package created by TACs or Client computers.

With information provided by the TAC Chief or AARPTL,

• Select the appropriate package. For example, Tac2.local-15 which is the 15th package created by Tac2 and the timestamp is at the front of the file name.

• Click create package.

Figure 18: Disc Burning Software

After the data is ready to burn, another application will open with a window like the figure above. Simply place a new DVD that has the XCTC Exercise information pre-printed and click burn at the bottom right corner.

Operator User Manual for the Network Operations Center (NOC)

Figure 19: Confirmation Window

Another window will open as show above. Verify the proper box have been ticked and click burn again.

Finally, take this DVD, which is now the master for that DTHP and use the DVD duplicator to create more copies, per the guidance of the Network supervision.

2.2.3 Termination

At the end of an exercise, the Network supervision will begin to backup contents from the services and client computers. Once that is completed, the NOC Operators under the supervision of the FAE and NOC Chief will perform a full inventory of the NOC and all accessories. As items are being counted, they will be unplugged, packed and palletized.

2.2.4 Removal

The Network supervision will provide a plan for pack-out in addition to assigning tasks to individual NOC Operators.

2.2.5 Preparation for Storage

Other than securely palletizing the NOC equipment and loading the trailers under the supervision of the NOTL and Field Service Representative (FSR), storing the NOC will be the responsibility of the personnel at the Products and Services Operations Center (PSOC) upon return to Fremont, California.

Operator User Manual for the Network Operations Center (NOC)

2.2.6 Preparation for Shipment

Not Applicable. Once items are palletized, see FSR for instructions on trailer load plan.

2.3 Operation under Unusual Conditions

The NOC, specifically, can be operated in inclement weather. The Network supervision and senior exercise leadership are responsible for providing an adequate structure to deploy a NOC station with a reliable power source such as a generator. When in doubt, follow the guidance of exercise leadership, range control or local authorities during severe weather to ensure safety.

Care should be taken to ensure the room or building where the NOC is located is air-conditioned at a comfortable temperature for NOC personnel as multiple NOC servers can generate a considerable amount of heat. Avoid operating the NOC when the ambient temperature is above 100 degrees F as the excessive heat generated by the NOC may cause premature failure in sensitive electronics, particularly the hard drive, memory modules and processor. Avoid operating the NOC stations at low temperatures below 40 degrees F or in extremely humid conditions.

2.3.1 Unusual Environment

Not Applicable

2.3.1.1 Lightning

Not Applicable

2.3.1.2 Strong Winds

Not Applicable

2.3.1.3 Cold

Not Applicable

2.3.2 Emergency Procedures

In an emergency, the first priority is to prevent injury to personnel working in the NOC and to see medical attention. If the emergency is technical in nature, alert the NOC Chief or FAEs if it is during their scheduled work hours. Otherwise, directly contact the NOTL.

In the event of a power failure and with consent from the NOTL, begin shutting down all but one client computers, IPA, HBSS, Logger 2 and Gateway 2 machines. This will reduce the power draw on the UPS, therefore increasing the chance of the power being restored without losing live tracking data.

Operator User Manual for the Network Operations Center (NOC)

3. Operator Maintenance Instructions In general, all field maintenance and troubleshooting will be done or supervised by the FAE at that particular exercise. In the event that a FAE is not available, the Computer Operator IV can perform basic troubleshooting. Under no circumstance is the NOC Operator allowed to open the case of the computer, remove/replace hardware or uninstall/reinstall software without prior approval from the Network supervision. At minimum, a FAE or a Computer Operator IV must be present to supervise any troubleshooting and to maintain proper custody of replacement parts.

3.1 Troubleshooting

The NOC is the most important piece in the network infrastructure. Therefore, during the sustainment portion of the exercise, report any faults and issues to Network supervision immediately. Do not attempt to troubleshoot the Services or Security servers without a FAE present. Do not attempt any troubleshooting on Saiph other than re-initializing or re-entering an EDI/FREDI that has been out of coms for more than three minutes. If Saiph indicates all services machines and all relevant processes are running and a particular Client machine is being slow, then it is acceptable to reboot it. Only troubleshoot faulty peripherals such as monitor, keyboards or mice and then inform the FAE to obtain spare parts if necessary.

3.2 Maintenance Procedures

Once shipped back to the Products and Services Operations Center (PSOC), each TAC station will be scheduled for general maintenance and cleaning, to be completed by the FAE team. General maintenance includes:

• Removing dust from case and racks

• Backup of data

• Reinstall new version of Linux and Orion for testing.

• Replace defective hardware components (RAM, Hard Drives, Video Cards) after diagnostic tests

• Evaluate run time of UPS batteries and replace if necessary

• Replace defective, end-of-life, or missing peripherals

4. Special Tools/Installation Equipment

• Phillips head screw drivers

• Multi-tool

• Pen

• Notebook

• Work gloves

5. Appendix Not Applicable

1.2.2 Equipment Data

1.3 Principles of Operation

2.3.2 Emergency Procedures