CAMMO_22_SOPS_Industry_Day_2014_Script.pdf

22 SOPS INDUSTRY DAY 2014

SCRIPT

Start of Briefing:

Title Slide: Electronic Scheduling Dissemination (ESD) Legacy

Slide 2: Air Force Satellite Control Network (AFSCN) operations require network management/scheduling functions

The AFSCN averages 450 satellite supports with 120+ real-time changes each day with 0 errors

The AFSCN supports 150+ satellites across 29 ops centers through 15 worldwide antennas

Of those 150+ satellites, the AFSCN supports 1300 possible configurations for all supports

The AFSCN scheduling process consists of a 7 day process

Pre-planned requests are submitted 7 days from support execution

AFSCN Network Scheduling executes a multi-day, priority-based de-confliction process

Priorities are based on individual satellite contact purpose and mission requirement

The AFSCN satellite schedule, known as the Network Tasking Order or NTO is published daily NLT 1900Z covering 1600Z to 1600Z for the next day

The NTO is always available to cover 21-45 hours of future operations

AFSCN scheduling performs real time changes during execution period for constellation management, response to outages, satellite launches, and satellite emergencies

AFSCN satellite operations effectiveness is assessed via user submitted mission impact reports post-execution of their satellite contact

Slide 3: The ESD legacy system allows AFSCN schedulers to de-conflict requirements, create the schedule, and publish the NTO out to the user community

ESD legacy provides 22 SOPS with a “smart interface”

ESD legacy for 22 SOPS enables views of satellite visibilities, Radio Frequency Interference issues, and resource conflicts

ESD legacy for 22 SOPS provides views of user requirements such as requested time windows and operational constraints

ESD legacy is built on disk operating system version 6.2.2 which does not afford the ability to create an automated satellite schedule

ESD legacy provides user interface to operation centers and Remote Tracking Stations known as RTSs

User and RTS views of the NTO and real-time changes are limited to text display only

ESD legacy at user locations and RTSs enables schedule requests, schedule changes, and allows RTSs to submit outage information of system/sub-system outages

Slide 4: Slide 4 illustrates the current ESD legacy architecture which consists of the core scheduling work stations, database servers, and peripheral equipment controllers, and remote user server.

ESD legacy for 22 SOPS uses a highly redundant architure

Primary Network Operations at Schriever AFB has 6 scheduling core work stations

The Temporary Network Operations Center on Schriever AFB has two workstations for immediate short term contingency actions only

The Alternate Network Operations Center is located at the Vandenberg Tracking Station which provides long term full redundancy

OPSCAP Yellow condition exists if 4 or less scheduling work stations are available or olny 1 of 2 peripheral controllers are available

OPSCAP Red condition exists if no scheduling workstations are available or no remote connectivity

OPSCAP determinations for the primary and alternate scheduling nodes are done independently

Slide 5: The current ESD legacy limitations consists of ESD working on archaic disk operating system, known as DOS with upper and lower memory limitations

Information Assurance vulnerabilities, and curtailed software and hardware sustainment

Slide 6: Electronic Scheduling Dissemination 3.0

Slide 7: ESD 3.0 will be replacing ESD legacy with a windows based system

ESD 3.0 will enable autonomous scheduling operations for users and with enhanced constellation management

ESD 3.0 was built from the SOC perspective to provide the ability for satellite users to have control over satellite operations

ESD 3.0 when fully fielded will support 1800+ users

ESD 3.0 is evolvable to allow “Lights out” operations from the SOC, comm and RTS elements

ESD 3.0 is anticipated to be operationally accepted in march of 2013

Slide 8: ESD 3.0 uses current technology hardware

As you can see pictured in the slide, the use of current dell technology computer work stations and monitors as well as blade servers

ESD 3.0 provides an increased reliability of 99.9%

ESD 3.0 in a dual node configuration allows equipment maintenance to be performed off line

Slide 9: This slide portrays the network topology layout of ESD 3.0 in a dual node configuration

Slide 10: Operational Switch Replacement – OSR, Distributed Communications Controller -

DCC

Slide 11: Distributed Communications Controllers are located throughout the AFSCN

The DCC creates connections between the Satellite Operations Centers (SOC) and the Remote Tracking Stations (RTS) through the Wide Area Network Interface Units (WANIU)

22 SOPS is highly reliant on a functioning DCC terminal as 22 SOPS is the AFSCN DCC link over-ride authority when an NTO violation occurs

Connection Types that are made are Primary & Backup Satellite Commanding, Primary & Backup Status-Echo which has ranging, Antenna Azimuth and Elevation, and station status.

Other connection types are Primary & Backup Satellite Telemetry/Payload, Inter-Range Instrumentation Group, otherwise known as timing, and Secure Voice Communications and ESD

Slide 12: Wide Area Network Interface Units (WANIU)

WANIUs establish source & destination port connections between SOC and RTS upon DCC request

WANIUs in essence are multiplexers/de-multiplexors and transports bi-directionally using Internet Protocol (IP) for routing to AFSCN CISCO routers

AFSCN CISCO Routers are CISCO Routers which provide the critical routing over primary and additional communications pathways between RTS and communication nodes at Schriever AFB and Vandenberg AFB

Slide 13: This slide illustrates the OSR architecture between the two communications nodes and the RTSs

It illustrates the redundancy needed for successful satellite operations

The green lines portray the primary and additional communications pathways between the Vandenberg AFSCN node and the RTSs, while the blue lines portray the primary and additional communications pathways between the Schriever AFSCN node and the RTSs

Slide 14: This slide illustrates the user connectivity to both Vandenberg and Schriever AFSCN nodes. If you will notice we have AFSCN users that connect through the Schriever AFSCN node where some users are located on Schriever AFB, while others are located elsewhere in the US

This slide also illustrates those users that can connect to either node, and those users that connect through the Vandenberg node under deployed conditions such as 2, 3, and 4 SOPS

Slide 15: Orbital Analysis System OAS – Legacy

Slide 16: Orbital Analysis System - Legacy

OAS legacy is a classified system that provides satellite visibilities to the ESD satellite scheduling system, which was presented earlier in this briefing to enable contacts to be scheduled

OAS legacy delivers radio frequency interference (RFI) predictions for scheduled AFSCN supports

OAS legacy Is utilized for orbit determination

OAS legacy supports custom orbital and RFI products based on AFSCN user agency needsOAS Legacy will be replaced by OAS 3.0 at 4th quarter of 2014

Slide 17: Orbital Analysis System - Legacy consists of a training suite and an operational suite.

It is composed administration computers, operator interface computers, orbital analysis computers and servers. The system utilizes an Oracle 10g database and is connected to the SIPRNet backbone to ingest Cheyenne Mountain disseminated orbital information

Slide 18: This slide illustrates the OAS legacy architecture. As you can see in the slide, all workstations perform set independent functions but all work together through a central switch where the primary switch uplink is connected to the SIPRNet backbone.

Slide 19: Orbital Analysis System 3.0

The OAS legacy system will be replaced by OAS 3.0

OAS 3.0 will migrate existing OAS functionality into virtual environments

OAS 3.0 will use VMware coupled with an oracle 11g database

OAS 3.0 systems administrators will work with both Vmware and oracle 11g databases

OAS 3.0 will have a training suite as well as the live operational suite

Slide 20: This slide illustrates the new OAS 3.0 architecture

As you can see on the far left those workstations, which currently exist today as individual computer workstations and servers are virtualized and contained within a primary and backup VM server connected to a central switch. To the right of the switch are 4 computer workstations that will display and interface with the virtual machines via remote desktop applications.

Slide 21: AFSCN Link Protection System

Slide 22: AFSCN Link Protection System (ALPS)

ALPS provides 22 SOPS with real-time radio frequency spectrum situational awareness of all mission downlinks from all AFSCN antennas in the 2.2 to 2.3 GHz receive band

ALPS provides radio frequency interference alerts to the AFSCN Network Crew Commander necessary to direct NTO changes to mitigate loss of user mission data

ALPS provides situational awareness for all AFSCN supported launches and vehicle anomalies and emergencies

Slide 23: ALPS at the RTS consists of windows client computers and spectrum analyzer equipment which monitor mission antennas to include independent autonomous RF direction finders to protect the RTSs from unauthorized terrestrial and aerial emissions

ALPS at the Schriever node consists of a database server and analysis workstation running government off the shelf software to display mission antennas and direction finder RF spectrums, while running interference detection algorithms

ALPS at the RTSs communicates to the ALPS server and workstation over AFSCN OSR assigned communications ports managed by the 22 SOPS DCC computers

Slide 24: This slide illustrates the ALPS equipment at the RTSs and node. Starting on the left side is a typical Direction Finder antenna on top of a high precision rotator mounted on a re-enforced tripod assembly. Moving over to the right illustrates a typical ALPS equipment rack which houses high end spectrum analyzers, Dell rack mounted computers and associated KVM.

At the node, ALPS consists of a high end dell server which contains an oracle 11 g database and government off the shelf software. The server is supported by use of a rack mounted KVM.

Actual display of AFSCN mission downlinks are done via the ALPS data analysis work station with dual monitor configuration

Slide 25: This slide lays out the ALPS architecture. Starting on the right side are the ALPS equipment suites located at the RTSs where boundary protection routers are used on each link along with TCP/IP to serial data format used by the OSR WANIU AFSCN network and is routed back to Schriever AFB where TCP/IP is recovered from the serial data format and routed to the server and workstation for display and analysis.

Slide 26: Critical reporting

Slide 27: 22 SOPS Mission Systems Reporting

22 SOPS must up-channel to the Joint Space Operations Center (JSpOC) within 10 minutes of any OPSCAP/SYSCAP changes for ESD, OAS, and DCC weapon systems

22 SOPS must up-channel to the JSpOC within 30 minutes of any OPSCAP/SYSCAP changes for the AFSCN RTS enterprise

What this amounts to is contractor response to 22 SOPS Mission Outages

Contractor responsiveness to, and restoration of mission impacting outages is key to 22 SOPS executing the AFSCN NTO for its 16 user agencies across 29 satellite C2 complexes prosecuting National Strategic Objectives and National Security