Engineering topics

Rackley, Michael

Publications and source records attributed to Rackley, Michael.

4 records

NASA NTRS2001

Current Level of Mission Control Automation at NASA/Goddard Space Flight Center

NASA is particularly concerned with reducing mission operations costs through increased automation. This paper examines the operations procedures within NASA Mission Control Centers in order to uncover the level of automation that currently exists within them. Based on an assessment of mission operations procedures within three representative control centers, this paper recommends specific areas where there is potential for mission cost reduction through increased automation.

Maks, Lori↗

NASA NTRS2001

Alternative Approaches to Mission Control Automation at NASA's Goddard Space Flight Center

To meet its objective of reducing operations costs without incurring a corresponding increase in risk, NASA is seeking new methods to automate mission operations. This paper examines the state of the art in automating ground operations for space missions. A summary of available technologies and methods for automating mission operations is provided. Responses from interviews with several space mission FOTs (Flight Operations Teams) to assess the degree and success of those technologies and methods implemented are presented. Mission operators that were interviewed approached automation using different tools and methods resulting in varying degrees of success - from nearly completely automated to nearly completely manual. Two key criteria for successful automation are the active participation of the FOT in the planning, designing, testing, and implementation of the system and the relative degree of complexity of the mission.

Rackley, Michael↗

NASA NTRS1994

Re-engineering the mission life cycle with ABC and IDEF

The theory behind re-engineering a business process is to remove the non-value added activities thereby lowering the process cost. In order to achieve this, one must be able to identify where the non-value added elements are located which is not a trivial task. This is because the non-value added elements are often hidden in the form of overhead and/or pooled resources. In order to be able to isolate these non-value added processes from among the other processes, one must first decompose the overall top level process into lower layers of sub-processes. In addition, costing data must be assigned to each sub-process along with the value the sub-process adds towards the final product. IDEF0 is a Federal Information Processing Standard (FIPS) process-modeling tool that allows for this functional decomposition through structured analysis. In addition, it illustrates the relationship of the process and the value added to the product or service. The value added portion is further defined in IDEF1X which is an entity relationship diagramming tool. The entity relationship model is the blueprint of the product as it moves along the 'assembly line' and therefore relates all of the parts to each other and the final product. It also relates the parts to the tools that produce the product and all of the paper work that is used in their acquisition. The use of IDEF therefore facilitates the use of Activity Based Costing (ABC). ABC is an essential method in a high variety, product-customizing environment, to facilitate rapid response to externally caused change. This paper describes the work being done in the Mission Operations Division to re-engineer the development and operation life cycle of Mission Operations Centers using these tools.

Mandl, Daniel↗

NASA NTRS1993

SAMPEX payload operation control center implementation

The Solar Anomolous and Magnetospheric Explorer (SAMPEX) satellite was launched in July 1992. It was the first in the NASA Small Explorer (SMEX) series. In building the real-time control center facility, several new mission support challenges had to be met: CCSDS telemetry and command format, 900 Kbps telemetry data, and shorter turn-around time for control center development than previous missions. The SAMPEX Payload Operations Control Ccnter (POCC) was also the first control center for a new satellite to be based on the Transportable Payload Operations Control Center (TPOCC) system architecture and methodology. This approach has both guided the implementation of the SAMPEX control center and provided some of the building blocks. By using the TPOCC architecture to build the SAMPEX POCC, the real-time operations area was miniaturized into one room, whereas previous missions needed multiple large rooms. The development cost of the SAMPEX POCC was reduced from previous missions and will provide for further cost savings in the future SMEX satellites. This paper describes the system as built and some of the enhancements in progress to create this teleoperations environment.

Mandl, Daniel↗