AF Satellite Control Network Architectural Approach

AF Satellite Control Network Architectural Approach

• • AIR

FOR

CE SATELLITE CONTROL NETW

ORK

SATELLITE CONTROL NETWORK CONTRAC

T

•

••

• A F S P C S M C CW

• B

OOZ A

LLEN

HAMILTON • HONEYWELL • INTEGRAL SYSTEMS

SPARTA • L-3 COMMUNICATIONS • NORTHROP GRUMMAN •

IIT

C •

Presented by:Richard A. Russel

SCNC Chief ArchitectNorthrop Grumman Mission Systems

Ground System Ground System Architectures Workshop Architectures Workshop

March 2003March 2003

22 CFR 125.4(b)(13) applicable (Div Ref #012-03, Log #2446)

VIAM INVENIENTUS

2 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •

22 CFR 125.4(b)(13) applicable (Div Ref #012-03, Log #2446) UNCLASSIFIED

Current ArchitectureCurrent Architecture

CloudDISN

WANIUOSR

WANIUOSR

WANIUOSR

CloudBII

CloudBII

CloudBII

SOCSOCSOCSOC

SOCSOC

SOCSOCSOCSOC

SOCSOC

Sched

Orbit

Comm

RemoteTrackingStations

ARTS

Net OpsCenter

Scheduling

New RTSBlock Change

New OrbitAnalysis

VIAM INVENIENTUS

3 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


AFSCN Evolution ObjectivesAFSCN Evolution Objectives

•Maintain operations and current capabilities while upgrading

•Shift network system boundary from within SOC to outside SOC

• Integrate user interface to all functional elements (comm, scheduling, RTS)

• Increase use of terrestrial network (vs. SATCOM links)

VIAM INVENIENTUS

4 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


AFSCN Evolution Objectives, AFSCN Evolution Objectives, ContinuedContinued

•Reduce development through use of standards and COTS products

• Increase interoperability and broaden customer base

VIAM INVENIENTUS

5 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


Use of Architecture MethodsUse of Architecture Methods

• Integrate Requirements Analysis

•Create C4ISR views of current system and its evolution

•Define Integrated Network Management Database

•Create project roadmap to guide budgeting and prioritization (POM)

VIAM INVENIENTUS

6 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


HQ Operational Req’s Doc (ORD)User Req’s Doc’s (PRD)Operator Change Requests

System SPEC

RangeSegment

Comm Segment

NetworkManagementSegment

CommandAnd ControlSegment

CustomerRequirements

Revised SystemRequirements

New SegmentRequirements

• A complete requirements traceability is being conducted usingRational requirements tools

Requirements Flowdown Requirements Flowdown ProcessProcess

VIAM INVENIENTUS

7 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


Architecture Analysis

InitialEngineering

Analysis

Project Definition

RD1 RD2 RD3

NewReq’sCustomer

Requirements

BaselineAnalysis

SustainmentReq’s

SustainmentTasks

ECP ProjectsSystem

Baseline System Specification

Segment Specifications

CI / Performance Specifications

InterfaceSpecifications

OperatorChange

Requests

Component

Requirements Analysis and Requirements Analysis and Project DefinitionProject Definition

VIAM INVENIENTUS

8 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


Range NMSComm CCS

Antenna Wan I/FTransmit Data

Monitoring & Control

SOCMonitoring & Control

Antennasetup

WAN I/FTransmit Data

WAN Transmit data

D0001D0002D0003D0004

Monitor & ControlD0005D0006D0007D0008

Monitor & ControlD0009D0010D0011D0012

RTSControl Antenna

D0020D0021

USE CASE Analysis Notional USE CASE Analysis Notional Activity Diagram ExampleActivity Diagram Example

USE Cases are being developed at all levels of requirements

VIAM INVENIENTUS

9 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


C4ISR System View 1C4ISR System View 1

VIAM INVENIENTUS

10 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


SOC Interface EvolutionSOC Interface Evolution

• Now have separate— Schedule— Comms— RTS Control workstations— Bitstream telem/command— AFSCN unique formats

• Future will integrate— Schedule— Comms— RTS Control functions— Offer packet

telem/command— Standard

formats/protocols

VIAM INVENIENTUS

11 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


Transport-able

OrbitAnalysis Scheduling

•NORAD•SOCs

SV ContactsLook AnglesNORAD Vectors

RBCRBC

SOCSOCSOCSOC

Schedule Requests

Comm Status

SOCNOC/NCCPerformance

Analysis

24 hr scheduleUpdates

Orbit Data

RTS Status, Logs

Integrated DB

RTS

Integrate Database Access Integrate Database Access Across ProjectsAcross Projects

VIAM INVENIENTUS

12 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


--Single RBC Summary

--Space for additional displays(DCC, RBC, ETC.)

--Multi-RBC SummaryProvides roll up summaryof 16 RBCs

--RBC Schedule Execution

Provides High LevelSchedule monitoring for 16RBCs on one display

Gives the operator thecapability to drill down toa single RBC displayOperator can effectively

monitor G/Y/R status bywatching the color of theantenna icons

Status of RBC EquipmentStatus of RBC Equipment

•The NOC, SOCs, and the RBC Operators have full status of RBC equipment enabling remote operations

VIAM INVENIENTUS

13 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


UNMET DRIVING RQMTS FROM:

SustainmentRBC

OAS F/OSSSNMS

‘O2 SCS ORDCRFSPRDs

Allocate to Existing/ New Projects

Incorporate into AFSCN Architecture

DoD/Other Govt/Commercial Satellite

NetworkManagement

WANService AFSCN

RTS

CommercialRTS

Other GovtRTS

SOCs

Commercial

Other Govt

Schedule

DedicatedRTS

DedicatedRTS

• High Level CAIV

• Technical Trades

ConductArchitectural

Analyses

Create ProjectDescriptions

Prioritize with HQ& Incorporate into

AFSCNRoadmap

POM Input

NewProject

All requirements will be assigned All requirements will be assigned projects and be placed on Roadmapprojects and be placed on Roadmap

VIAM INVENIENTUS

14 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


AFSCN Evolution PlanAFSCN Evolution Plan

2000 2001 2002 2003 2004 2005 2006 20071999

ATM Comm Upgrades

Orbit Analysis

Scheduling

Comm

NetworkManagement

WAN Services and SLE

RTS Block ChangeUSB Uplink RTS Control and Status BW Efficiency

RemoteGroundStations

USB Uplink RTS Control Onboard GPS Packet Mode

Studies and Test Beds

SOC& SV

Civil/Commercial Interoperability Demo’s

External User Comm

Net Mgmt Infrastructure

Antenna Replacement

VIAM INVENIENTUS

15 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


Future ArchitectureFuture Architecture

CloudDISN

WAN I/F

WAN I/F

WAN I/F

CloudBII

CloudBII

CloudBII

SOCSOCSOCSOC

SOCSOC

SOCSOCSOCSOC

SOCSOC

Sched

Net MgmtOrbit

Civil &Commercial

RBC

NOC

"Plug & Use" Architecture

CCSDS/SLEX, Ku, Ka

Band

Space BasedCommunications

IntegratedNet Interface,Other Users

Supports AF,Civil, and

Commercial

"BandwidthOn Demand"

WANIU OSRretired

PhasedArray

VIAM INVENIENTUS

16 AS OF: 3/26/2003

• • AIR

FOR


ORK


T

•

••


• B

OOZ A

LLEN



I IT

C •


Architecture SummaryArchitecture Summary

• SCNC is using strong architecture processes to go from requirements to projects

• AFSCN will evolve to a Network Management System with an integrated database access

• AFSCN will provide remote control and status information, allowing reduced staffing

• AFSCN will support open data transport standards and increased interoperability

Acknowledgements: SMC-CW and SCNC Team!

Documents

AF Satellite Control Network Architectural Approach