Environmental Engineering Reference
In-Depth Information
Spacecraft
Paging
System
Control
Center
LOGOS
Log
GenSAA/
Genie
Log
I/F Agent
SysMM
Agent
Pager
I/F Agent
FIRE
Agent
GenSAA/
Data Server
GenSAA
I/F Agent
User
I/F Agent
LOGOS
UI
AGENT COMMUNITY
USER
MOPSS
I/F Agent
DB I/F
Agent
Archive
I/F Agent
VisAGE
I/F Agent
MOPSS
=External
System
LOGOS
DB
VisAGE
Archive
=Agent
=Data
Archive
Fig. 4.4.
Lights out ground operations system (LOGOS) agent architecture
performed services for the other agents in the community, and others inter-
faced with an analyst or operator. All agents could communicate with any
other agent in the community, though not all of the agents were required to
communicate with other agents.
The System Monitoring and Management Agent (SysMMA) kept track
of all of the agents in the community and provided addresses of agents for
other agents requesting services, similar to the ISA in AFLOAT. Each agent
when started had to register with SysMMA to register their capabilities and
to obtain addresses of other agents whose services it needed.
The Fault Isolation and Resolution Expert (FIRE) agent resolved satellite
anomalies. FIRE was notified of anomalies during a satellite pass. It contained
a knowledge base of potential anomalies and a set of possible fixes for them.
If it did not recognize an anomaly or was unable to resolve it, it then sent the
anomaly to the user interface agent to be forwarded to a human analyst for
resolution.
The User Interface Agent (UIFA) was the interface between the agent
community and the graphical user interface that the analyst or operator used
to interact with the LOGOS agent community. UIFA received notification of
anomalies from the FIRE agent, handled login of users to the system, kept
the user informed with reports, routed commands to be sent to the satellite,
and performed other maintenance functions. If the attention of an analyst was
