Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Ground System”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 739 records · Page 41

The First Development of Human Factors Engineering Requirements for Application to Ground Task Design for a NASA Flight Program

The National Aeronautics and Space Administration has long applied standards-derived human engineering requirements to the development of hardware and software for use by astronauts while in flight. The most important source of these requirements has been NASA-STD-3000. While there have been several ground systems human engineering requirements documents, none has been applicable to the flight system as handled at NASA's launch facility at Kennedy Space Center. At the time of the development of previous human launch systems, there were other considerations that were deemed more important than developing worksites for ground crews; e.g., hardware development schedule and vehicle performance. However, experience with these systems has shown that failure to design for ground tasks has resulted in launch schedule delays, ground operations that are more costly than they might be, and threats to flight safety. As the Agency begins the development of new systems to return humans to the moon, the new Constellation Program is addressing this issue with a new set of human engineering requirements. Among these requirements is a subset that will apply to the design of the flight components and that is intended to assure ground crew success in vehicle assembly and maintenance tasks. These requirements address worksite design for usability and for ground crew safety.

Dischinger, H. Charles, Jr.↗

Using Pilots to Assess the Value and Approach of CMMI Implementation

At Goddard Space Flight Center (GSFC), we have chosen to use Capability Maturity Model Integrated (CMMI) to guide our process improvement program. Projects at GSFC consist of complex systems of software and hardware that control satellites, operate ground systems, run instruments, manage databases and data and support scientific research. It is a challenge to launch a process improvement program that encompasses our diverse systems, yet is manageable in terms of cost effectiveness. In order to establish the best approach for improvement, our process improvement effort was divided into three phases: 1) Pilot projects; 2) Staged implementation; and 3) Sustainment and continual improvement. During Phase 1 the focus of the activities was on a baselining process, using pre-appraisals in order to get a baseline for making a better cost and effort estimate for the improvement effort. Pilot pre-appraisals were conducted from different perspectives so different approaches for process implementation could be evaluated. Phase 1 also concentrated on establishing an improvement infrastructure and training of the improvement teams. At the time of this paper, three pilot appraisals have been completed. Our initial appraisal was performed in a flight software area, considering the flight software organization as the organization. The second appraisal was done from a project perspective, focusing on systems engineering and acquisition, and using the organization as GSFC. The final appraisal was in a ground support software area, again using GSFC as the organization. This paper will present our initial approach, lessons learned from all three pilots and the changes in our approach based on the lessons learned.

Godfrey, Sara↗

Automatic frequency control of voltage-controlled oscillators

Optical-capacitive coupling is used for isolation of control voltages, such as the high-voltage level of a klystron control electrode that is not referenced to ground, to serve as error voltages referenced to system ground so that the magnitude and sense of correction may be transferred.

Kolbly, R. B.↗

LANDSAT D operations control center study

Various aspects of the planned LANDSAT D system are discussed. LANDSAT D incorporates the Thematic Mapper (TM) as a sensor, it utilizes the Multi-mission Modular Spacecraft (MMS), it makes use of the Tracking and Data Relay Satellite System (TDRSS) and it employs a more advanced ground system. Each of these represent significant improvements in the state-of-the-art.

Alexander, L.↗

Lessons Learned In Developing Multiple Distributed Planning Systems for the International Space Station

The planning processes for the International Space Station (ISS) Program are quite complex. Detailed mission planning for ISS on-orbit operations is a distributed function. Pieces of the on-orbit plan are developed by multiple planning organizations, located around the world, based on their respective expertise and responsibilities. The "pieces" are then integrated to yield the final detailed plan that will be executed onboard the ISS. Previous space programs have not distributed the planning and scheduling functions to this extent. Major ISS planning organizations are currently located in the United States (at both the NASA Johnson Space Center (JSC) and NASA Marshall Space Flight Center (MSFC)), in Russia, in Europe, and in Japan. Software systems have been developed by each of these planning organizations to support their assigned planning and scheduling functions. Although there is some cooperative development and sharing of key software components, each planning system has been tailored to meet the unique requirements and operational environment of the facility in which it operates. However, all the systems must operate in a coordinated fashion in order to effectively and efficiently produce a single integrated plan of ISS operations, in accordance with the established planning processes. This paper addresses lessons learned during the development of these multiple distributed planning systems, from the perspective of the developer of one of the software systems. The lessons focus on the coordination required to allow the multiple systems to operate together, rather than on the problems associated with the development of any particular system. Included in the paper is a discussion of typical problems faced during the development and coordination process, such as incompatible development schedules, difficulties in defining system interfaces, technical coordination and funding for shared tools, continually evolving planning concepts/requirements, programmatic and budget issues, and external influences. Techniques that mitigated some of these problems will also be addressed, along with recommendations for any future programs involving the development of multiple planning and scheduling systems. Many of these lessons learned are not unique to the area of planning and scheduling systems, so may be applied to other distributed ground systems that must operate in concert to successfully support space mission operations.

Maxwell, Theresa G.↗

Lessons Learned in Developing Multiple Distributed Planning Systems for the International Space Station

The planning processes for the International Space Station (ISS) Program are quite complex. Detailed mission planning for ISS on-orbit operations is a distributed function. Pieces of the on-orbit plan are developed by multiple planning organizations, located around the world, based on their respective expertise and responsibilities. The pieces are then integrated to yield the final detailed plan that will be executed onboard the ISS. Previous space programs have not distributed the planning and scheduling functions to this extent. Major ISS planning organizations are currently located in the United States (at both the NASA Johnson Space Center (JSC) and NASA Marshall Space Flight Center (MSFC)), in Russia, in Europe, and in Japan. Software systems have been developed by each of these planning organizations to support their assigned planning and scheduling functions. Although there is some cooperative development and sharing of key software components, each planning system has been tailored to meet the unique requirements and operational environment of the facility in which it operates. However, all the systems must operate in a coordinated fashion in order to effectively and efficiently produce a single integrated plan of ISS operations, in accordance with the established planning processes. This paper addresses lessons learned during the development of these multiple distributed planning systems, from the perspective of the developer of one of the software systems. The lessons focus on the coordination required to allow the multiple systems to operate together, rather than on the problems associated with the development of any particular system. Included in the paper is a discussion of typical problems faced during the development and coordination process, such as incompatible development schedules, difficulties in defining system interfaces, technical coordination and funding for shared tools, continually evolving planning concepts/requirements, programmatic and budget issues, and external influences. Techniques that mitigated some of these problems will also be addressed, along with recommendations for any future programs involving the development of multiple planning and scheduling systems. Many of these lessons learned are not unique to the area of planning and scheduling systems, so may be applied to other distributed ground systems that must operate in concert to successfully support space mission operations.

Maxwell, Theresa G.↗

Bion 11 mission: primate experiments

A summary is provided of the major operations required to conduct the wide range of primate experiments on the Bion 11 mission, which flew for 14 days beginning December 24, 1996. Information is given on preflight preparations, including flight candidate selection and training; attachment and implantation of bioinstrumentation; flight and ground experiment designs; onboard life support and test systems; ground and flight health monitoring; flight monkey selection and transport to the launch site; inflight procedures and data collection; postflight examinations and experiments; and assessment of results.

NASA Discipline Musculoskeletal↗

ICESat-2 Constraint Analysis and Monitoring System (CAMS)

The Ice, Cloud and land Elevation Satellite-2 was launched on 15 September 2018 with mission goals of collecting surface elevation data that can precisely measure ice sheet topography, cloud and aerosol heights, land topography, as well as vegetation height for ecosystems studies. The Constraint Analysis and Monitoring System (CAMS) was implemented as an ICESat-2 ground system element to perform Mission Planning and Spacecraft Safety Monitoring. Mission Planning requires CAMS to serve as an interface between the Project Science Office, the Instrument Support Facility and the Mission Operation Control Center. By ingesting inputs received from all three groups, the CAMS builds an optimized and deconflicted timeline of science and instrument activities. Based upon the timeline of activities, the CAMS utilizes a sophisticated set of algorithms to model and predict the location and pointing of the spacecraft instrument relative to the Earth and Sun. From the predicted position and pointing, the CAMS provides precise monitoring of instrument health, and performs space asset laser conjunction detection. Furthermore, the CAMS determines alternative plans to prevent detected health constraint violations or mitigate potential laser conjunctions. This paper provides an overview of the CAMS and presents the operational performance of planning science and instrument activities, the monitoring of instrument constraints for health and safety, and the space asset laser conjunction screening and mitigation process.

ICESat-2↗

Hardware and Software Engineering

The Launch Control System (LCS) is a part of the system used to launch the Space Launch System (SLS). It monitors and control of both vehicle and ground systems for SLS. My internship this spring was focused both on the hardware and software aspects of the command and control system. During my internship I worked in two groups, the Record and Playback Subsystem (RPS) and Kennedy Ground Control Subsystems (KGCS). During my time on RPS, I worked on automating the updating of displays and engineering reports. While on KGCS I worked on creating a power distribution diagram of the Control System Development Lab (CDL) and a new trainer for new interns or employees to gain an understanding of Programmable Logic Controllers (PLCs).

Hardware↗

Space Station ground data management system

KSC is planning a Space Station Ground Data Management System (GDMS) for support of functional interface verification, integration and test of Space Station modules and elements. This computer system, planned for initial operational support in 1992, currently is entering a definition and prototyping stage. This paper provides an overview of the GDMS system concept. It synopsizes system functional capabilities, and discusses software and hardware architectural approaches currently under evaluation. It identifies programmatic constraints and their influence upon the concept, as well as specific technical issues planned for study or evaluation via prototyping.

Heuser, Jan↗

Considerations in development of expert systems for real-time space applications

Over the years, demand on space systems has increased tremendously and this trend will continue for the near future. Enhanced capabilities of space systems, however, can only be met with increased complexity and sophistication of onboard and ground systems. Artificial Intelligence and expert system techniques have great potential in space applications. Expert systems could facilitate autonomous decision making, improve in-orbit fault diagnosis and repair, enhance performance and reduce reliance on ground support. However, real-time expert systems, unlike conventional off-line consultative systems, have to satisfy certain special stringent requirements before they could be used for onboard space applications. Challenging and interesting new environments are faced while developing expert system space applications. This paper discusses the special characteristics, requirements and typical life cycle issues for onboard expert systems. Further, it also describes considerations in design, development, and implementation which are particularly important to real-time expert systems for space applications.

Murugesan, S.↗

Earth and ocean dynamics satellites and systems

An overview is presented of the present state of satellite and ground systems which are used for studies concerning the dynamics of the solid earth and the oceans. It is pointed out that very good progress has been made in the area of earth and ocean dynamics since the described program was initiated in 1969. Construction of the mathematical models needed for data interpretation and analyses for earth dynamics phenomena and for ocean dynamics are in progress.

Vonbun, F. O.↗

Earth and ocean dynamics satellites and systems

An overview is presented of the present state of satellite and ground systems making observations of the dynamics of the solid earth and the oceans. Emphasis is placed on applications of space technology for practical use. Topics discussed include: satellite missions and results over the last two decades in the areas of earth gravity field, polar motions, earth tides, magnetic anomalies, and satellite-to-satellite tracking; laser ranging systems; development of the Very Long Baseline Interferometer; and Skylab radar altimeter data applications.

Vonbun, F. O.↗

MOS 2.0: Modeling the Next Revolutionary Mission Operations System

Designed and implemented in the 1980's, the Advanced Multi-Mission Operations System (AMMOS) was a breakthrough for deep-space NASA missions, enabling significant reductions in the cost and risk of implementing ground systems. By designing a framework for use across multiple missions and adaptability to specific mission needs, AMMOS developers created a set of applications that have operated dozens of deep-space robotic missions over the past 30 years. We seek to leverage advances in technology and practice of architecting and systems engineering, using model-based approaches to update the AMMOS. We therefore revisit fundamental aspects of the AMMOS, resulting in a major update to the Mission Operations System (MOS): MOS 2.0. This update will ensure that the MOS can support an increasing range of mission types, (such as orbiters, landers, rovers, penetrators and balloons), and that the operations systems for deep-space robotic missions can reap the benefits of an iterative multi-mission framework.12 This paper reports on the first phase of this major update. Here we describe the methods and formal semantics used to address MOS 2.0 architecture and some early results. Early benefits of this approach include improved stakeholder input and buy-in, the ability to articulate and focus effort on key, system-wide principles, and efficiency gains obtained by use of well-architected design patterns and the use of models to improve the quality of documentation and decrease the effort required to produce and maintain it. We find that such methods facilitate reasoning, simulation, analysis on the system design in terms of design impacts, generation of products (e.g., project-review and software-delivery products), and use of formal process descriptions to enable goal-based operations. This initial phase yields a forward-looking and principled MOS 2.0 architectural vision, which considers both the mission-specific context and long-term system sustainability.

ground support systems↗

Annual Report by Aerospace Safety Advisory Panel

Elements of the shuttle program that directly affect the mission success and crew safety were investigated. These elements included the shuttle orbiter, the main engine, the solid rocket boosters, avionic system, ground support equipment and the approach and landing operations. The thermal protection systems were studied in detail. Crew training and ground simulation test procedures were reviewed.

Source record↗