Ground Autonomy Evolution - Autonomous and Autonomic Systems - page 70

EP S/C

Mission
Operations
Control
Center
(MOCC)

Tape Archive

Raw
Telemetry

Agents

Through
TDRSS and
NASCOM

60 Mbytes

Raw
Data

Requests

of Raw
Telemetry
(Binary) on an
HP
Workstation

Decommutate d
DB (Binary)

EAS
Software

Mnemonics'
Extraction and Data
Merging Software

List of Extracted
Mnemonics

Data Quality Report

(ASCII Data)

MNEMONICS
DATABASE

PMNB1CHG PMNB1DSC PMNSAELO CST1VPS1 CST1BST1 CTAM1ROL EDFRAMECNT EDFMATID

Battery
Net
Charge

C/D
Ratio

Solar
Array
Temp.

Fixed
Head
Star Tr.
Status

Gyro
Drift
Bias

Tape
Recorder-
Performance

Transpon
der-
Performance

Parameters

Solar
Arrays

Trans-
ponder

Gyros ............

Components

Batteries

MACS

CDHS

Sub-systems MPS

KEY
EAS - Engineering
Analysis
Software

Uses
Simulated
Real-time
Data

EP Subsystem
Monitoring

EP Weekly
Reporting

Uses off-line
Data Current

Build

Fig. 4.2. A taxonomy of Explorer Platform (EP) satellite system and data extrac-
tion process

4.1.2 Implementation Architecture for AFLOAT Prototype

An architecture definition for AFLOAT is shown in Fig. 4.3 . The multia-
gent system (MAS) employed direct communication between agents without a
mediator. All external requests, from either a user or a remote client, entered
the AFLOAT system through the Interface Services Agent (ISA), which then
forwarded them to appropriate agents. The Systems Services Agent (SSA)
maintained a database of agents' names, skills, and locations (i.e., TCP/IP
socket address). It also monitored the health and status of each agent, and
provided essential resources for agent migration.