CAMMO_ATB_Script.pdf

ATB Brief – Intro

Welcome, before we begin the tour I would like to ask all of you to refrain from asking questions verbally. If you have any questions please write them down and submit them to Lt Dan Beckett utilizing the question submission form prior to 7 March

2014. Also as we walk through the labs please stay within the yellow borders of tape. If anyone has a beverage they can place them on this table (point to table), and collect it at the conclusion of the tour.

My name is Paul Hartmann from SMC/RNL and I will be walking you through our suite of labs and Government support infrastructure today. These labs are used to test, integrate, modify, and/or update our equipment and systems before we deploy changes to the Remote Tracking Stations (RTSs), and the Operational Control Nodes (OCNs), and other locations.

The AFSCN Test Bed (ATB) is composed of smaller more specific test beds. These test beds and support infrastructure systems are: the RISS, ADMTB, CSSTB, ESD 2.7, ESD 3.0, TRBC Pad, OAS lab , IACSM, UPS and crypto room. I will break down the title and purpose of each as we walk through.

Please follow me to our first lab. CSSTB, ADMF, HPAs, RISS1 and RISS unique then RISS II, Production areas, UPS

System, ESD3.0, TRBC Pad. OAS Lab, crypto Room.

ATB Brief – ESD 2.7

The 22nd Space Operations Squadron (22 SOPS) uses the Electronic Schedule Dissemination (ESD) system to manage and schedule resource requests received from various operational entities. The ESD system accepts and processes resource requests to create and disseminate AFSCN resource schedules, status information, and associated data to the AFSCN user community.

ESD 2.7 currently is not being updated in any way expect in the event of an emergency. The test bed will remain until 3.0 has achieved OMRT

ATB Brief – CSSTB

The Communications (Comm) Segment Sustainment Test Bed (CSSTB):

o The CSSTB is a sustainment test bed and not an operational AFSCN component.

o The CSSTB resides within the AFSCN Test Bed development and sustainment facility.

o The CSSTB provides a Communications Segment (CS) test bed environment simulating the operational communications links between two Operational Control Nodes (OCNs) and two Remote Tracking Stations (RTSs).

o The CSSTB contains: WANIUs, Routers, Switches, ATM and IP Clouds, DCC computers and test equipment, all for use in integrating, testing, software development and troubleshooting.

o All equipment is configured as close to the actual AFSNC communication segment equipment. This ensures the testing of equipment and software to be reliable which will reduce risk of software bugs being introduced to the field.

o The CSSTB interfaces with the RTS Block Change (RBC) Integration and Support Suite (RISS) and ESD 3.0 suites supporting integration and testing within the ATB. This allows end to end testing, where ESD can send different schedules to the RISS RBC Core via the CSSTB. Again it reduces risk when the software is deployed.

CSSTBs limitations are:

o The CSSTB relies on a simulated DISA Cloud.

o There is no connectivity to the AFSCN network, which limits troubleshooting and end to end testing.

o The CSSTB is unable to truly replicate the amount of traffic experienced within the AFSCN communication segment.

ATB Brief – ATB infrastructure equipment and IACSM

The ATB contains a LAN infrastructure tying the Test beds together and providing management of those Test beds.

Integration and Test Support Facility (I&TSF) Administrative Controls, Status, and Monitoring System (IACSM). (The name will eventually change) o Commercial Off-the-Shelf (COTS) management tools (hardware and software) that will provide control, status and monitoring of the ATB IP assets.

o The information collected includes asset and Configuration Management (CM) data for the ATB, Communications

Segment Sustainment Test Bed (CSSTB), Remote Tracking Station (RTS) Block Change (RBC) Integration Support Suite

(RISS), and any future IP-based network test beds. (expecting ESD 3.0 in the future) o IACSM contains Host Based Security System (HBSS) in the ATB and provides antivirus protection, Host Intrusion

Prevention System (HIPS), and Anti-Spyware protection.

o Additional tools include SolarWinds, and vCenter Configuration Manager (vCM), which provides continuous monitoring of all IP assets.

CSSTB

CSSTB

001 002 003 004 005 006 007 008 009 010 011 013

011 012 013013

105 101100102103

0717060504030201

104 616

New Rack (616)

Installed under

WA 10-128

Network Cables to I&TSF

ATB Brief – ADMTB

The Automated Remote Tracking Station (ARTS) Development and Modification Test Bed (ADMTB)

Formally called ARTS Development and Modification facility (ADMF)

The ADMTB is a derivative of the ARTS/ARS core configuration and will provided for modification and development testing.

This complement of hardware, software and firmware shall consist of the ARTS core configuration and a simulator to provide replicated electrical and software interface of an ARTS antenna.

The ADMF is used as follows: as a test bed to develop the ARTS design; to support step 2 testing; to test repaired Line

Replaceable Units (LRUs) in full ARTS configuration; for training; to develop system modifications and most importantly to test IRON database changes o IRON, Inter Range Operation Number, is a set of about 100-200 parameters that the ARTS system needs to be told so it will setup the equipment properly to interface with the satellite and comm segment.

The ADMTB CI shall include an antenna simulator and a high-speed Local Area Network (LAN) for interconnect.

The ADMTB also provides the capability to interface to other AFSCN systems that are located within the ATB.

o Legacy HPA o RISS

ADMTB’s limitations are:

o There is not an actual antenna connected to the ADMTB o The ADMTB uses a SOC/SIM to test responses to SOC commands.

o The ATB does not contain a triple or Quad HPA for system testing o No connection to the CSSTB, limits comm interface testing.

ATB Brief – RBC HPA and Legacy HPA

The RBC HPA o The RBC HPA is connected to all RBC Production and RISS core equipment through the RISS unique racks.

o The HPA is the same model as the site RBC HPAs

The RBC HPA Limitations o The HPA does not connect to an antenna but is used by transmitting into a dummy load.

The Legacy HPA o Legacy HPA connects to both RISS, RBC production areas and the ADMF via RISS unique Racks o This HPA can be used to test out HPA books prior to returning them to supply

The Legacy HPA Limitations o The HPA cannot test the unique pieces of equipment that are used in the triple HPAs or the Quad HPA.

o It does function as a single HPA by transmitting into a dummy load o The Legacy HPA is a single HPA, the network does have triples and a Quad HPA

ATB Brief - RISS

The Remote Tracking Station (RTS) Block Change (RBC) Integration and Support Suite (RISS) o The RISS is the test bed to support software development, hardware upgrades, testing and troubleshooting of AFSCN anomalies.

o The RISS is also used to test IRON changes/updates. IRON, Inter Range Operation Number, is a set of about 200-300 parameters that the RBC system needs to be told so it will setup the equipment properly to interface with the satellite and comm. segment.

o The RISS provides a semi-automated and automated capability to test hardware and software for RBC production, maintenance, new capability development, and technology refresh.

o The RISS will provide a common design and functionality to support all of the RBC configurations, including the fixed

RTS, the Eastern Vehicle Checkout Facility (EVCF), and the TRBC.

o The RISS is also required to maintain existing configurations until all sites have been updated to the new configurations. (Note: it is typically the responsibility of the individual o RISS also contains RISS unique racks that support the development and test efforts. Some are:

RITA Rack, RISS information Assurance Test Assembly, used to setup and test LRU IA

Antenna Simulator

DEU SIM

SOC/SIM

Depot Checkout Rack, for building and testing production Servers

Interface racks, used to interface with production areas, HPAs, and simulators.

RBC legacy Pre Obsolesce upgrade Racks o RBC Production areas, there are 2 areas to assemble the RBC Core racks for test and checkout prior to deploying to site.

o TRBC, connect to the RISS unique racks for test and checkout o EVCF has unique LPA rack, The RISS contains two independent sets of RBC Core racks for use in testing and troubleshooting. RISS I and RISS II

The RISS also provides the capability to interface to other AFSCN systems that are located within the I&TSF.

o Legacy HPA- used to test RBCs that may connect to a legacy HPA o RBC HPA- Allows the RISS I, RISS II and Production areas to share connections to the RBC HPA.

o CSSTB for testing RBC with Comm. segment o ESD 2.7 o ESD 3.0 via Comm. Segment o IACSM- Controls and monitors the RISS internal LAN o TRBC PAD

Finally, the RISS contains a suite of hardware and software to provide a supporting environment for sustaining the RBC software, databases and scripts. Some tools are Test-manager and Clear case.

RISSs limitations are:

o There is not an actual antenna connected to the RISS. It relies on an antenna and DEU Simulator o There is not antenna servo controllers to connect to the DEU o The DEU connected has simulator software to allow the functions of the DEU to think there is an antenna attached.

ATB Brief – Production areas

2 RBC Production areas exist to build out the core racks, integrate and test prior to shipping to site. (See above RISS diagram)

A set of RF and control cables run under the floor to the RISS unique racks for interconnectivity to the RISS simulators, test-manager, DEU and HPAs.

Other production racks exist to build/image servers needed in the field. Rack 611 and Software production area near ESD 2.7

(See Below)

Production area limitations are:

o RBC areas connect to RISS simulators and HPAs which can only be used by one system at a time.

If RISS is in formal testing and using the HPA then all other cores are locked out o RBC areas estimate cable length and loss, which will need to be adjusted when they are installed at an actual site.

ATB Brief – UPS

The UPS system resides in the ATB high bay and provides uninterrupted power to all Test beds within the ATB. A minimum of 15 minutes of electrical service in the event of degraded commercial power or loss was established as the primary requirement. The UPS system accommodates all of the sustainment systems, but only a portion of the development systems.

Status and control are provided via the Facility Management Control System (FMCS) and Local Area Network (LAN).

The UPS system consists primarily of the UPS cabinet, two battery banks, a transfer switch, and alarm panels.

The UPS produces a nominal value of 480VAC/280 kVA, ATB Brief – TRBC Pad

TRBC Antenna System Configuration Item (CI)

Transportable High-Power Amplifier (HPA) Subsystem.

TRBC Core Electronics CI- The trailer here is the RTSR van, it is the same configuration as the TRBC core Van.

o Currently the RTSR van is not part of the AFSCN baseline, if this changes in the future all parties will be notified through appropriate channels.

The equipment for the Transportable Core Electronics and Transportable HPA subsystems will be housed in shelters that are essentially box trailers welded to an underframe that includes tandem axles with air ride suspension, a fifth wheel compatible with commercial tractors, and front and rear leveling jacks. The Antenna CI is mounted on its own open be trailer.

The TRBC Core Electronics CI deployed to interface and operate with a fixed site RBC Antenna System CI (Configuration 1).

The TRBC Antenna System CI deployed to interface and operate with the fixed site RBC Core Electronics CI (Configuration

2).

The TRBC Core Electronics CI deployed to interface and operate with the TRBC Antenna System CI (Configuration 3).

The TRBC Core Electronics CI deployed to interface and operate with the EVCF interface (Configuration 4).

The TRBC Core Electronics CI deployed to support the Factory Compatibility Test (FCT) interface (Configuration 5).

Portable F/O Communications Subsystem

An Input /Output (I/O) panel will become an extension of the RISS, and is an I/O panel to which the TRBC will connect for testing with the RISS.

The TRBC is required to be able to connect to the RISS for testing and troubleshooting. The TRBC interfaces with the RISS unique racks similar to the production areas. A parking PAD is required to accommodate three semi-trailers.

TRBC Pad limitations are:

o Although the TRBC has an antenna, active supports are not typically allowed at a contractor’s facility.

ATB Brief – ESD 3.0

The 22nd Space Operations Squadron (22 SOPS) uses the Electronic Schedule Dissemination (ESD) system to manage and schedule resource requests received from various operational entities. The ESD system accepts and processes resource requests to create and disseminate AFSCN resource schedules, status information, and associated data to the AFSCN user community.

ESD 2.7 currently is not being updated in any way expect in the event of an emergency. The test bed will remain until 3.0 has achieved OMRT

ESD 3.0 is currently in development and is scheduled to turnover to sustainment tin FY15.

The Electronic Schedule Dissemination Test Bed (ESDTB) supports maintenance of the Electronic Schedule Dissemination

(ESD) by providing a platform to test software updates.

The ESDTB provides suites of ESD 3.0 hardware and software networked together to reflect a portion of the currently deployed ESD 3.0 architecture. The ESDTB software baseline includes COTS infrastructure software (e.g., Windows, Lightstreamer, Oracle) in addition to the developed application software. The ESDTB only models a subset of the full architecture: the primary and backup scheduling control nodes, a baseline user (i.e., a SOC co-located with a scheduling node), an RTS and an external remote user (i.e., a SOC not co-located with a scheduling node). The approximately 39 remaining ESD 3.0 users are not modeled in the ESDTB.

The ESDTB contains 1 high-level Environment: the ESD 3.0 Laboratory Environment encompassing 4 functional suites for use in integrating, testing and troubleshooting ESD 3.0 system. The ESD 3.0 Laboratory Environment’s 4 functional suites are: Test suite, Development suite, Performance suite, and Lab Demo suite.

The ESDTB is located in a single physical location dedicated to the ESD 3.0 system. The ESDTB interfaces with other

AFSCN test beds located in the same facility. The other AFSCN test beds are hosted in or near the Integration & Test Support

Facility (I&TSF), a room about 40m from the ESDTB. Other AFSCN test beds include the Communications Segment test bed, the RBC Integration & Support Suite (RISS) 1, the RBC Integration & Support Suite (RISS) 2 and the Transportable RBC

(TRBC) pad.

The ESDTB's limitations include the inability to accurately model the realistic behavior of the communications segment (e.g., to model the impact of ongoing stochastic changes in the long haul communications bandwidth during nominal and off-nominal ESD 3.0 operations), the inability to model the entire 44 site architecture, and the inability to model the realistic communication bandwidth usage of ESD 3.0 network management-related traffic.

ATB Brief – OAS Secure Lab

The Orbital Analysis Subsystem (OAS) provides satellite tracking and early launch support products to the Satellite Operations

Centers (SOCs), the Electronic Schedule Dissemination (ESD) system, and other users.

The OAS Test bed is to support software development, hardware upgrades, testing and troubleshooting of AFSCN anomalies.

To support testing the lab is provided data from 22SOPS which requires the lab to be classified secrete and must be accredited by the DAA.

OAS system contains:

o Administration and Access Control Server (AAS) o Orbit Interface Workstation (OIW) o Orbit Analysis Workstation (OAW) o Database (DB) Server Group

ATB Brief – Crypto Room

The crypto room houses three types of encryption devices. Encryption devices sit at the end of the AFSCN baseline and encrypt or decrypt AFSCN traffic before and after it enters/exits the DISN cloud.

There are three types of devices to encrypt three different types of traffic: KIV 17M for Serial traffic, KG 75 for Asynchronous

Transfer Mode (ATM) traffic, and finally KG 175D for Internet Protocol (IP) traffic.

The serial devices were recently updated from outdated devices

The ATM traffic is being phased out of the AFSCN, once it has been completely phased out the KG 75s will no longer be needed in the lab.

The crypto devices are issued from the Depot in San Antonio, Texas. COMSEC procedures are used to ensure the integrity of the devices are safeguarded.

KIV 7M for Serial Traffic

KG 75 for ATM Traffic KG 175D for IP Traffic

ATB Brief – Closing

That concludes the tour of the lab. As a reminder, if you have any questions please be sure to write them down utilizing the question submission form and submit them to Lt. Dan Beckett prior to 7 March 2014. We will review all questions and post the answers on the FedBizOpps website at a later date.

We will now walk to the entry of the building and get your badges turned back in. Thank you, and follow me.