Search NASASearch

Engineering topics

Lucord, Steven A.

Publications and source records attributed to Lucord, Steven A..

CCSDS SM and C Mission Operations Interoperability Prototype

This slide presentation reviews the prototype of the Spacecraft Monitor and Control (SM&C) Operations for interoperability among other space agencies. This particular prototype uses the German Space Agency (DLR) to test the ideas for interagency coordination.

Lucord, Steven A.

CCSDS Mission Operations Action Service Core Capabilities

This slide presentation reviews the operations concepts of the command (action) services. Since the consequences of sending the wrong command are unacceptable, the command system provides a collaborative and distributed work environment for flight controllers and operators. The system prescribes a review and approval process where each command is viewed by other individuals before being sent to the vehicle. The action service needs additional capabilities to support he operations concepts of manned space flight. These are : (1) Action Service methods (2) Action attributes (3) Action parameter/argument attributes (4 ) Support for dynamically maintained action data. (5) Publish subscri be capabilities.

Reynolds, Walter F.

OTF Mission Operations Prototype Status

Reports on the progress of the JSC/OTF prototype of a CCSDS SM&C protocol based communications link between two space flight operations control centers. Varied implementations using software architectures from current web enterprise venues are presented. The AMS protocol (CCSDS Blue Book standard 735.1) was used for messaging and link communications.

Reynolds, Walter F.

OTF CCSDS Mission Operations Prototype. Directory and Action Service. Phase I: Exit Presentation

This slide presentation describes the phase I directory and action service prototype for the CCSDS system. The project goals are to: (1) Demonstrate the use of Mission Operations standards to implement Directory and Action Services (2) Investigate Mission Operations language neutrality (3) Investigate C3I XML interoperability concepts (4) Integrate applicable open source technologies in a Service Oriented Architecture

Reynolds, Walter F.

OTF CCSDS Mission Operations Prototype Parameter Service. Phase I: Exit Presentation

This slide presentation reviews the prototype of phase 1 of the parameter service design of the CCSDS mission operations. The project goals are to: (1) Demonstrate the use of Mission Operations standards to implement the Parameter Service (2) Demonstrate interoperability between Houston MCC and a CCSDS Mission Operations compliant mission operations center (3) Utilize Mission Operations Common Architecture. THe parameter service design, interfaces, and structures are described.

Reynolds, Walter F.

OTF Proof of Concept: CCSDS Mission Operations Alert Services

Conclusions: Use of multiple vendor frameworks within a component creates thread lockups and fragility conflicts over the control of the main thread. Avoid closed vendor messaging frameworks. The MAL layer does isolate the data elements from the messaging framework but application work dispatch is heavily dominated by the framework chosen. API Language is a major factor in implementation. Message APIs with timeouts seem unavoidable in some environments (GUI). Language environment needs to support callbacks (or threads) from the messaging framework to deal with pub/sub management messages and status. Statusing of application communications demand a local broker agent per physical system or else the use of the AMSstyle registrar heartbeat.

Reynolds, Walt

OTF CCSDS SM and C Interoperability Prototype

A presentation is provided to demonstrate the interoperability between two space flight Mission Operation Centers (MOCs) and to emulate telemetry, actions, and alert flows between the two centers. One framework uses a COTS C31 system that uses CORBA to interface to the local OTF data network. The second framework relies on current Houston MCC frameworks and ad hoc clients. Messaging relies on SM and C MAL, Core and Common Service formats, while the transport layer uses AMS. A centralized SM and C Registry uses HTTP/XML for transport/encoding. The project's status and progress are reviewed.

Reynolds, Walter F.