Content Framework for Operational Environmental Remote Sensing Data Sets: NPOESS Concepts
Integrated Multi-Missions Remote Operational Management …
Transcript of Integrated Multi-Missions Remote Operational Management …
Overview
Hardware Architecture
Future Missions Support
Objectives
Software Architecture
Mission Separation–OWL Overview
NSOF IMMS Rack
1 HU A42
A1A2A3A4A5A6A7A8A9A10A11A12A13A14A15A16A17A18A19A20A21A22A23A24A25A26A27A28A29A30A31A32A33A34A35A36A37A38A39A40A41
A42 3PAR Service Processor
A32 DL320e GOES Dev Host
Vertical PDUs are 20-outlet strips
attached to the rack frame in the rear and
powered by circuits separate from the
c7000 chassis
73.50
40.25 (approx.)
GFE equipment to be installed after rack is received from HP.
23.5"
79.0
B03L H5M
58A PD
UB24L H
5M58A
PDU
B03R H5M
58A PD
UB24R H
5M58A
PDU
A31 DL320e POES Dev Host
A27 Space for CAC Reader
A21 KVM w/Console
A403PAR 7400 2-n Storage Base
A38 M6710SAN Disk Enclosure
A1HP c7000 Blade
Chassis
A14 DL385pGOES Data Aggregator
Empty/Blank Panels
Empty/Blank Panels
Empty/Blank Panel
Empty/Blank Panel
Empty/Blank Panel
A18 DL385pPOES Data Aggregator
A16 DL320e POES OWL Xmtr
A12 DL320e GOES OWL XmtrA11 Cable Feedthru Panel
Empty/Blank Panel
2 HU
2 HU
8 HU
1 HU
7 HU
1 HU1 HU
2 HU
1 HU1 HU
2 HU
1 HU1 HU1 HU
10 HU
Rollups File Manager Bridge
Log File Watcher Bridge
EPOCH Trends Bridge
EPOCH Events Bridge
Retriever Server
Back Orbit Webic Server
Back Orbit Watcher Bridge
Noti�cation Bridge
Rollups Bridge
Archive Manager
File Monitor OWL File Catch
EPOCH Points BridgeUser Session
Admin Portlet
Retention File Utility
Events Catcher Bridge
Webic Server
Points Catcher Bridge
Realtime
Realtime
Introduce
Files
Files MySQL
OW
L
OW
L
Historical Trend Translation
Bridge
pointthrow_pacsor
pointthrow
GOES or POES Mnemonics De�nition
File Generator
OWL File Throw
Historical Events Translation
Plug-in
Historical Points Translation
Plug-in
Webic Server
Processing Server
IMMS/CITS Cell Mission Cell
OWL Send Card
Other Sources
Admin LAN Users Storage
AD Domain/ Security Servers
Web VPN Access Piont
GTACS Servers
Data Aggregator
S/W Thrower
S/W Thrower
S/W Thrower
S/W Thrower
S/W Thrower
OWL-blue
Other Sources
TCS Servers
Data Aggregator
OWL-blue
OWL-red- �ber
OWL-red- �ber
GOES N-P
Non-IMMS LAN
POES
r/t stream 1
r/t stream 2
r/t stream n
Tlm File
Src(s)
Event File
Src(s)
Trend File
Src(s)
User File(s)
Processing
Webic
Processing
Attached Storage
Webic
Processing
Webic
Processing
Webic
External Users
VPN Access Point
Admin LAN Users
CITS AD/ Sec Servers
DA
BLUE OWL
RED OWL RED OWL RED OWL RED OWL
Phase 1 Mission 1
r/t stream 1
r/t stream 2
r/t stream n
Tlm File
Src(s)
Event File
Src(s)
Trend File
Src(s)
User File(s)
DA
BLUE OWL
Phase 1 Mission 1
r/t stream 1
r/t stream 2
r/t stream n
Tlm File
Src(s)
Event File
Src(s)
Trend File
Src(s)
User File(s)
DA
BLUE OWL
Future Mission
r/t stream 1
r/t stream 2
r/t stream n
Tlm File
Src(s)
Event File
Src(s)
Trend File
Src(s)
User File(s)
DA
BLUE OWL
Future Mission
IMMS (CITS LAN)
OWL Send Card
Optical Fiber
Air Gap
SOURCE Gateway
SOURCE Network
DESTINATION Gateway
DESTINATION Network
OWL Receive Card
©2017 ERT, Inc. All Rights Reserved
ERT, Inc.14401 Sweitzer Lane, 300Laurel, MD 20707 www.ertcorp.com
Integrated Multi-Missions Remote Operational Management System
Ye Men, Rob Haynes, Rachid Dahmani, Shahram Tehranian
�� Make spacecraft mission telemetry, events, trends and files available for remote access to authenticated, pre-authorized users�� Preserve the self-contained environment and high security posture of each spacecraft mission by transferring data across the mission boundary via a secure, one-way transfer link
�� Each mission cell incorporates a Data Aggregation (DA) Server to collect file and real-time mission data�� The DA Server forwards the data to the IMMS CITS servers for processing and storage�� Each mission is separated from the CITS LAN via a one-way link (OWL) security device�� Data only flows out of the mission cell�� The Processing Server receives and manages incoming mission data and services data requests from Webic�� Webic Server processes and displays data and requests from the user�� All historical data stored on IMMS CITS storage hardware
�� Well-defined data interfaces allowing seamless modular expansion to missions�� Horizontal linearly scalable HP Blade Chassis and SAN hardware architecture �� VMware virtualization enabling vertical scaling of compute resource expansion �� COTS Webic software with customization only dedicated to each unique mission mnemonic and data
�� Current delivery incorporates the GOES and POES missions�� Future phases able to expand to include other missions�� POES follows general IMMS architecture�� GOES throwers reside on the GTACS servers and send real-time telemetry straight through the OWL�� Other GOES file data flows through DA�� Current IMMS CITS hardware includes blade chassis
CITS servers for each mission:�� A blade server is dedicated for each mission Webic Server VM host and Processing Server VM host
Webic:�� Webic is a web-based thin client for presenting and controlling data sources�� Webic multi-source displays can create an integrated view of the operational environment�� Provides high performance display components to support data-rich displays across multiple pages�� Leverages a drag-and-drop, in-browser page builder�� Webic assures data integrity even on high-latency connections�� Webic applications are added through the Liferay Portal, which is an enterprise web platform for building and interacting with Webic pages
Archive Manager:�� Archive Manager (AM) is designed to manage archive files from a satellite system�� AM can automatically generate product files (DMF, EMF, TMF, and RAW) to be used for analysis, in Webic, of spacecraft and ground system data�� Handles both short term (cache) and long-term (scratch) storage requirements�� AM is available on both Windows and Linux platforms
�� Source gateway will be a stand-alone computer on mission side with the OWL send card�� Destination gateway will be a computer on CITS LAN with the OWL receive card installed in a non-virtualized blade server�� IMMS will utilize this for real-time TCP/file transfers�� OWL Secure Network Transfer System (SNTS) software does not pass IP address information across the link�� Source IP information is configured by an administrator and mapped to an OWL channel number in a table on the send-only platform�� In the receive-only platform the corresponding channel number is mapped to the destination IP address
�� Real-time data in a timely manner so that the mission data can be monitored for performance and troubleshooting purposes�� Agile and cost effective scalable enterprise platform for future missions
�� A blade server along with expansion blade server is dedicated for the red OWL Windows VM host and Red OWL receiving PCI cards
All-purpose use:�� A blade server is reserved for system management�� Additional blade slots available to be allocated for future missions�� 25 Webic Licenses will be allocated as 15 licenses per GOES, 10 licenses per POES unless directed otherwise