Search NASA⌕ Search

SEARCH · Search NASA

Results for “Ground Systems Development and Operations”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

Real-Time Kennedy Space Center and Cape Canaveral Air Force Station High-Resolution Model Implementation and Verification

Customer: NASA's Launch Services Program (LSP), Ground Systems Development and Operations (GSDO), and Space Launch System (SLS) programs. NASA's LSP, GSDO, SLS and other programs at Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS) use the daily and weekly weather forecasts issued by the 45th Weather Squadron (45 WS) as decision tools for their day-to-day and launch operations on the Eastern Range (ER). For example, to determine if they need to limit activities such as vehicle transport to the launch pad, protect people, structures or exposed launch vehicles given a threat of severe weather, or reschedule other critical operations. The 45 WS uses numerical weather prediction models as a guide for these weather forecasts, particularly the Air Force Weather Agency (AFWA) 1.67 kilometer Weather Research and Forecasting (WRF) model. Considering the 45 WS forecasters' and Launch Weather Officers' (LWO) extensive use of the AFWA model, the 45 WS proposed a task at the September 2013 Applied Meteorology Unit (AMU) Tasking Meeting requesting the AMU verify this model. Due to the lack of archived model data available from AFWA, verification is not yet possible. Instead, the AMU proposed to implement and verify the performance of an ER version of the AMU high-resolution WRF Environmental Modeling System (EMS) model (Watson 2013) in real-time. The tasking group agreed to this proposal; therefore the AMU implemented the WRF-EMS model on the second of two NASA AMU modeling clusters. The model was set up with a triple-nested grid configuration over KSC/CCAFS based on previous AMU work (Watson 2013). The outer domain (D01) has 12-kilometer grid spacing, the middle domain (D02) has 4-kilometer grid spacing, and the inner domain (D03) has 1.33-kilometer grid spacing. The model runs a 12-hour forecast every hour, D01 and D02 domain outputs are available once an hour and D03 is every 15 minutes during the forecast period. The AMU assessed the WRF-EMS 1.33-kilometer domain model performance for the 2014 warm season (May-September). Verification statistics were computed using the Model Evaluation Tools, which compared the model forecasts to observations. The mean error values were close to 0 and the root mean square error values were less than 1.8 for mean sea-level pressure (millibars), temperature (degrees Kelvin), dewpoint temperature (degrees Kelvin), and wind speed (per millisecond), all very small differences between the forecast and observations considering the normal magnitudes of the parameters. The precipitation forecast verification results showed consistent under-forecasting of the precipitation object size. This could be an artifact of calculating the statistics for each hour rather than for the entire 12-hour period. The AMU will continue to generate verification statistics for the 1.33-kilometer WRF-EMS domain as data become available in future cool and warm seasons. More data will produce more robust statistics and reveal a more accurate assessment of model performance. Once the formal task was complete, the AMU conducted additional work to better understand the wind direction results. The results were stratified diurnally and by wind speed to determine what effects the stratifications would have on the model wind direction verification statistics. The results are summarized in the addendum at the end of this report. In addition to verifying the model's performance, the AMU also made the output available in the Advanced Weather Interactive Processing System II (AWIPS II). This allows the 45 WS and AMU staff to customize the model output display on the AMU and Range Weather Operations AWIPS II client computers and conduct real-time subjective analyses. In the future, the AMU will implement an updated version of the WRF-EMS model that incorporates local data assimilation. This model will also run in real-time and be made available in AWIPS II.

Numerical Weather Prediction↗
NASA NTRS2017

Environmental Control Systems for Exploration Missions One and Two

In preparing for Exploration Missions One and Two (EM-1 & EM-2), the Ground Systems Development and Operations Program has significant updates to be made to nearly all facilities. This is all being done to accommodate the Space Launch System, which will be the world’s largest rocket in history upon fruition. Facilitating the launch of such a rocket requires an updated Vehicle Assembly Building, an upgraded Launchpad, Payload Processing Facility, and more. In this project, Environmental Control Systems across several facilities were involved, though there is a focus around the Mobile Launcher and Launchpad. Parts were ordered, analysis models were updated, design drawings were updated, and more.

EM-2↗
NASA NTRSDate not supplied

Preparations for Quesst Acoustics Validation

- Acoustic Validation Goals & Objectives - Overview and Concept of Operations - New Ground Systems Development - State-of-the sonic boom ground recording system - Unattended recording system trigger - X-59 sonic boom flight path planning tool - Real-time sonic boom prediction display - New Airborne Systems Development - Airborne near field probing system - In-flight, full-scale shockwave imagery systems - Real-time relative position pilot display - Acoustic Validation Test Approach

Larry J. Cliatt, II↗
NASA NTRS2009

Spaceflight Systems Training: A Comparison and Contrasting of Techniques for Training Ground Operators and Onboard Crewmembers

When developing techniques and products for instruction on manned spaceflight systems, training organizations are often faced with two very different customers: ground operators and onboard crewmembers. Frequently, instructional development focuses on one of these customers with the assumption that the other s needs will be met by default. Experience teaches us that differing approaches are required when developing training tailored to the specific needs of each customer. As a rule, ground operators require focused instruction on specific areas of expertise. Their knowledge should be of the details of the hardware, software, and operational techniques associated with that system. They often benefit from historical knowledge of how their system has operated over its lifetime. Since several different ground operators may be interfacing with the same system, each individual operator must understand the agreed-to principles by which that system will be run. In contrast, onboard crewmembers require a more broad, hands-on awareness of their operational environment. Their training should be developed with an understanding of the physical environment in which they live and work and the day-to-day tasks they are most likely to perform. Rarely do they require a deep understanding of the details of a system; it is often sufficient to teach them just enough to maintain situational awareness and perform basic tasks associated with maintenance and operation of onboard systems. Crewmembers may also develop unique onboard operational techniques that differ from preceding crews. They should be taught what flexibility they have in systems operations and how their specific habits can be communicated to ground support personnel. This paper will explore the techniques that can be employed when developing training for these unique customers. We will explore the history of International Space Station training development and how past efforts can guide us in creating training for users of future manned spaceflight efforts.

Balmain, Clinton↗
NASA NTRS1991

Ground Systems Development Environment (GSDE) interface requirements analysis: Operations scenarios

This report is a preliminary assessment of the functional and data interface requirements to the link between the GSDE GS/SPF (Amdahl) and the Space Station Control Center (SSCC) and Space Station Training Facility (SSTF) Integration, Verification, and Test Environments (IVTE's). These interfaces will be involved in ground software development of both the control center and the simulation and training systems. Our understanding of the configuration management (CM) interface and the expected functional characteristics of the Amdahl-IVTE interface is described. A set of assumptions and questions that need to be considered and resolved in order to complete the interface functional and data requirements definitions are presented. A listing of information items defined to describe software configuration items in the GSDE CM system is included. It also includes listings of standard reports of CM information and of CM-related tools in the GSDE.

Church, Victor E.↗
NASA NTRS1999

Lockheed Martin Skunk Works Single Stage to Orbit/Reusable Launch Vehicle

Lockheed Martin Skunk Works has compiled an Annual Performance Report of the X-33/RLV Program. This report consists of individual reports from all industry team members, as well as NASA team centers. This portion of the report is comprised of a status report of Lockheed Martin's contribution to the program. The following is a summary of the Lockheed Martin Centers involved and work reviewed under their portion of the agreement: (1) Lockheed Martin Skunk Works - Vehicle Development, Operations Development, X-33 and RLV Systems Engineering, Manufacturing, Ground Operations, Reliability, Maintainability/Testability, Supportability, & Special Analysis Team, and X-33 Flight Assurance; (2) Lockheed Martin Technical Operations - Launch Support Systems, Ground Support Equipment, Flight Test Operations, and RLV Operations Development Support; (3) Lockheed Martin Space Operations - TAEM and A/L Guidance and Flight Control Design, Evaluation of Vehicle Configuration, TAEM and A/L Dispersion Analysis, Modeling and Simulations, Frequency Domain Analysis, Verification and Validation Activities, and Ancillary Support; (4) Lockheed Martin Astronautics-Denver - Systems Engineering, X-33 Development; (5) Sanders - A Lockheed Martin Company - Vehicle Health Management Subsystem Progress, GSS Progress; and (6) Lockheed Martin Michoud Space Systems - X-33 Liquid Oxygen (LOX) Tank, Key Challenges, Lessons Learned, X-33/RLV Composite Technology, Reusable Cyrogenic Insulation (RCI) and Vehicle Health Monitoring, Main Propulsion Systems (MPS), Structural Testing, X-33 System Integration and Analysis, and Cyrogenic Systems Operations.

Source record↗
NASA NTRS1994

Mission Operations Centers (MOCs): Integrating key spacecraft ground data system components

In an environment characterized by decreasing budgets, limited system development time, and user needs for increased capabilities, the Mission Operations Division (MOD) at the National Aeronautics and Space Administration Goddard Space Flight Center initiated a new, cost-effective concept in developing its spacecraft ground data systems: the Mission Operations Center (MOC). In the MOC approach, key components are integrated into a comprehensive and cohesive spacecraft planning, monitoring, command, and control system with a single, state-of-the-art graphical user interface. The MOD is currently implementing MOC's, which feature a common, reusable, and extendable system architecture, to support the X-Ray Timing Explorer (XTE), Tropical Rainfall Measuring Mission (TRMM), and Advanced Composition Explorer (ACE) missions. As a result of the MOC approach, mission operations are integrated, and users can, with a single system, perform real-time health and safety monitoring, real-time command and control, real-time attitude processing, real-time and predictive graphical spacecraft monitoring, trend analysis, mission planning and scheduling, command generation and management, network scheduling, guide star selection, and (using an expert system) spacecraft monitoring and fault isolation. The MOD is also implementing its test and training simulators under the new MOC management structure. This paper describes the MOC concept, the management approaches used in developing MOC systems, the technologies employed and the development process improvement initiatives applied in implementing MOC systems, and the expected benefits to both the user and the mission project in using the MOC approach.

Harbaugh, Randy↗
NASA NTRS2008

GSFC Technical Outreach: The Capitol College Model

In February 2005, as part of the National Aeronautic and Space Administration (NASA) Technical Outreach Program, Goddard Space Flight Center (GSFC) awarded Capitol College of Laurel, Maryland an Educational Grant to establish a Space Operation academic curriculum to meet the future needs of mission operations engineers. This was in part due to the aerospace industry and GSFC concerns that a large number of professional engineers are projected to retire in the near term with evidence showing that current enrollment in engineering schools will not produce sufficient number of space operation trained engineers that will meet industry and government demands. Capitol College, under the agreement of the Educational Grant, established the Space Operations Institute (SOI) with a new curriculum in Space Operations that was approved and certified by the State of Maryland. The SO1 programs focuses on attracting, recruiting, and training a pipeline of highly qualified engineers with experience in mission operations, system engineering and development. The selected students are integrated as members of the engineering support team in any of the missions supported by the institute. The students are mentored by professional engineers from several aerospace companies that support GSFC. Initially, the institute was involved in providing console engineers and mission planning trainees for the Upper Atmosphere Research Satellite (UARS), the Earth Radiation Budget Satellite (ERBS) and the Total Ozone Mapping Spectrometer mission (TOMS). Subsequently, the students were also involved in the technology refresh of the TOMS ground system and other mission operations development. Further mission assignment by GSFC management included participation in the Tropical Rainfall Measuring Mission (TRMM) mission operations and ground system technology refresh. The SOI program has been very successful. Since October 2005, sixty-four students have been enrolled in the SOI program and twenty-five have already graduated from the program, nineteen of whom are employed by company's supporting GSFC. Due to the success of the program, the initial grant period was extended for another period of two years. This paper presents the process that established the SOI as a viable pipeline of mission operations engineers, the lessons learned in the process of dealing with grants, and experience gained in mentoring engineering students that are responsible for particular areas of expertise and functionality. This paper can also be considered a case study and model for integrating a student team with government and industry professionals in the real world of mission operations.

Marius, Julio L.↗
NASA NTRS2011

Interplanetary Overlay Network Bundle Protocol Implementation

The Interplanetary Overlay Network (ION) system's BP package, an implementation of the Delay-Tolerant Networking (DTN) Bundle Protocol (BP) and supporting services, has been specifically designed to be suitable for use on deep-space robotic vehicles. Although the ION BP implementation is unique in its use of zero-copy objects for high performance, and in its use of resource-sensitive rate control, it is fully interoperable with other implementations of the BP specification (Internet RFC 5050). The ION BP implementation is built using the same software infrastructure that underlies the implementation of the CCSDS (Consultative Committee for Space Data Systems) File Delivery Protocol (CFDP) built into the flight software of Deep Impact. It is designed to minimize resource consumption, while maximizing operational robustness. For example, no dynamic allocation of system memory is required. Like all the other ION packages, ION's BP implementation is designed to port readily between Linux and Solaris (for easy development and for ground system operations) and VxWorks (for flight systems operations). The exact same source code is exercised in both environments. Initially included in the ION BP implementations are the following: libraries of functions used in constructing bundle forwarders and convergence-layer (CL) input and output adapters; a simple prototype bundle forwarder and associated CL adapters designed to run over an IPbased local area network; administrative tools for managing a simple DTN infrastructure built from these components; a background daemon process that silently destroys bundles whose time-to-live intervals have expired; a library of functions exposed to applications, enabling them to issue and receive data encapsulated in DTN bundles; and some simple applications that can be used for system checkout and benchmarking.

Burleigh, Scott C.↗
NASA NTRS1996

The MARS pathfinder end-to-end information system: A pathfinder for the development of future NASA planetary missions

The development of the Mars pathfinder is considered with emphasis on the End-to-End Information System (EEIS) development approach. The primary mission objective is to successfully develop and deliver a single flight system to the Martian surface, demonstrating entry, descent and landing. The EEIS is a set of functions distributed throughout the flight, ground and Mission Operation Systems (MOS) that inter-operate in order to control, collect, transport, process, store and analyze the uplink and downlink information flows of the mission. Coherence between the mission systems is achieved though the EEIS architecture. The key characteristics of the system are: a concurrent engineering approach for the development of flight, ground and mission operation systems; the fundamental EEIS architectural heuristics; a phased incremental EEIS development and test approach, and an EEIS design deploying flight, ground and MOS operability features, including integrated ground and flight based toolsets.

Cook, Richard A.↗
NASA NTRS2016

Tailoring NIST Security Controls for the Ground System: Selection and Implementation -- Recommendations for Information System Owners

The National Aeronautics and Space Administration (NASA) invests millions of dollars in spacecraft and ground system development, and in mission operations in the pursuit of scientific knowledge of the universe. In recent years, NASA sent a probe to Mars to study the Red Planet's upper atmosphere, obtained high resolution images of Pluto, and it is currently preparing to find new exoplanets, rendezvous with an asteroid, and bring a sample of the asteroid back to Earth for analysis. The success of these missions is enabled by mission assurance. In turn, mission assurance is backed by information assurance. The information systems supporting NASA missions must be reliable as well as secure. NASA - like every other U.S. Federal Government agency - is required to manage the security of its information systems according to federal mandates, the most prominent being the Federal Information Security Management Act (FISMA) of 2002 and the legislative updates that followed it. Like the management of enterprise information technology (IT), federal information security management takes a "one-size fits all" approach for protecting IT systems. While this approach works for most organizations, it does not effectively translate into security of highly specialized systems such as those supporting NASA missions. These systems include command and control (C&C) systems, spacecraft and instrument simulators, and other elements comprising the ground segment. They must be carefully configured, monitored and maintained, sometimes for several years past the missions' initially planned life expectancy, to ensure the ground system is protected and remains operational without any compromise of its confidentiality, integrity and availability. Enterprise policies, processes, procedures and products, if not effectively tailored to meet mission requirements, may not offer the needed security for protecting the information system, and they may even become disruptive to mission operations. Certain protective measures for the general enterprise may not be as efficient within the ground segment. This is what the authors have concluded through observations and analysis of patterns identified from the various security assessments performed on NASA missions such as MAVEN, OSIRIS-REx, New Horizons and TESS, to name a few. The security audits confirmed that the framework for managing information system security developed by the National Institute of Standards and Technology (NIST) for the federal government, and adopted by NASA, is indeed effective. However, the selection of the technical, operational and management security controls offered by the NIST model - and how they are implemented - does not always fit the nature and the environment where the ground system operates in even though there is no apparent impact on mission success. The authors observed that unfit controls, that is, controls that are not necessarily applicable or sufficiently effective in protecting the mission systems, are often selected to facilitate compliance with security requirements and organizational expectations even if the selected controls offer minimum or non-existent protection. This paper identifies some of the standard security controls that can in fact protect the ground system, and which of them offer little or no benefit at all. It offers multiple scenarios from real security audits in which the controls are not effective without, of course, disclosing any sensitive information about the missions assessed. In addition to selection and implementation of controls, the paper also discusses potential impact of recent legislation such as the Federal Information Security Modernization Act (FISMA) of 2014 - aimed at the enterprise - on the ground system, and offers other recommendations to Information System Owners (ISOs).

GOVERNANCE↗
NASA NTRS2014

Facility Systems, Ground Support Systems, and Ground Support Equipment General Design Requirements

KSC-DE-512-SM establishes overall requirements and best design practices to be used at the John F. Kennedy Space Center (KSC) for the development of ground systems (GS) in support of operations at launch, landing, and retrieval sites. These requirements apply to the design and development of hardware and software for ground support equipment (GSE), ground support systems (GSS), and facility ground support systems (F-GSS) used to support the KSC mission for transportation, receiving, handling, assembly, test, checkout, servicing, and launch of space vehicles and payloads and selected flight hardware items for retrieval. This standards manual supplements NASA-STD-5005 by including KSC-site-specific and local environment requirements. These requirements and practices are optional for equipment used at manufacturing, development, and test sites.

Ground Support Systems↗
NASA NTRS1994

The Advanced Orbiting Systems Testbed Program: Results to date

The Consultative Committee for Space Data Systems (CCSDS) Recommendations for Packet Telemetry (PT) and Advanced Orbiting Systems (AOS) propose standard solutions to data handling problems common to many types of space missions. The Recommendations address only space/ground and space/space data handling systems. Goddard Space Flight Center's (GSFC's) AOS Testbed (AOST) Program was initiated to better understand the Recommendations and their impact on real-world systems, and to examine the extended domain of ground/ground data handling systems. The results and products of the Program will reduce the uncertainties associated with the development of operational space and ground systems that implement the Recommendations.

Otranto, John F.↗
NASA NTRS1995

A Systems Engineering Approach to the Analysis of a Planetary Mission Ground System in Terms of Science Objectives

The most fundamental objective of all planetary missions is to return data. To accomplish this, a spacecraft is fabricated and built, software is planned and coded, and a ground system is designed and implemented. However, a systems engineering approach to determine how the collection of data drives ground system capabilities has received little attention.This paper defines a technique by which science objectives can be quantitatively evaluated. For illustrative purposes, it will be applied to NASA's Cassini Mission. This mission, to be launched in 1997, is an international endeavor designed to orbit Saturn for four years.The results of this systems engineering approach will show which science objectives drive specific ground system capabilities. In addition, this technique can assist system engineers in the selection of the science payload during pre-project mission planning; ground system designers during ground system development and implementation; and operations personnel during the mission.

systems engineering, ground systems↗
NASA NTRS1994

Small satellite space operations

CTA Space Systems has played a premier role in the development of the 'lightsat' programs of the 80's and 90's. The high costs and development times associated with conventional LEO satellite design, fabrication, launch, and operations continue to motivate the development of new methodologies, techniques, and generally low cost and less stringently regulated satellites. These spacecraft employ low power 'lightsat' communications (versus TDRSS for NASA's LEO's) and typically fly missions with payload/experiment suites that can succeed, for example, without heavily redundant backup systems and large infrastructures of personnel and ground support systems. Such small yet adaptable satellites are also typified by their very short contract-to-launch times (often one to two years). This paper reflects several of the methodologies and perspectives of our successful involvement in these innovative programs and suggests how they might relieve NASA's mounting pressures to reduce the cost of both the spacecraft and their companion mission operations. It focuses on the use of adaptable, sufficiently powerful yet inexpensive PC-based ground systems for wide ranging user terminal (UT) applications and master control facilities for mission operations. These systems proved themselves in successfully controlling more than two dozen USAF, USN, and ARPA satellites at CTA/SS. UT versions have linked with both GEO and LEO satellites and functioned autonomously in relay roles often in remote parts of the world. LEO applications particularly illustrate the efficacy of these concepts since a user can easily mount a lightweight antenna, usually an omni or helix with light duty rotors and PC-based drivers. A few feet of coax connected to a small transceiver module (the size of a small PC) and a serial line to an associated PC establishes a communications link and together with the PC constitute a viable ground station. Applications included geomagnetic mapping; spaceborne solid state recorder validation; global store-and-forward data communications for both scientific and military purposes such as Desert Storm; UHF transponder services for both digital data and voice using a constellation; remote sensor monitoring of weather and oceanographic conditions; classified payloads; and UHF spectrum surveillance. Ground processing has been accomplished by automatic unattended or manual operation. Management of multiple assets highlights the relative ease with which two constellations totaling nine satellites were controlled from one system including constellation station keeping. Our experience in small end-to-end systems including concurrent design, development, and testing of the flight and operational ground systems offers low cost approaches to NASA scientific satellite operations of the 1990's.

Reiss, Keith↗
NASA NTRS2006

Achieving Operability via the Mission System Paradigm

In the past, flight and ground systems have been developed largely-independently, with the flight system taking the lead, and dominating the development process. Operability issues have been addressed poorly in planning, requirements, design, I&T, and system-contracting activities. In many cases, as documented in lessons-learned, this has resulted in significant avoidable increases in cost and risk. With complex missions and systems, operability is being recognized as an important end-to-end design issue. Never-the-less, lessons-learned and operability concepts remain, in many cases, poorly understood and sporadically applied. A key to effective application of operability concepts is adopting a 'mission system' paradigm. In this paradigm, flight and ground systems are treated, from an engineering and management perspective, as inter-related elements of a larger mission system. The mission system consists of flight hardware, flight software, telecom services, ground data system, testbeds, flight teams, science teams, flight operations processes, procedures, and facilities. The system is designed in functional layers, which span flight and ground. It is designed in response to project-level requirements, mission design and an operations concept, and is developed incrementally, with early and frequent integration of flight and ground components.

ground systems↗
NASA NTRS2007

XML Flight/Ground Data Dictionary Management

A computer program generates Extensible Markup Language (XML) files that effect coupling between the command- and telemetry-handling software running aboard a spacecraft and the corresponding software running in ground support systems. The XML files are produced by use of information from the flight software and from flight-system engineering. The XML files are converted to legacy ground-system data formats for command and telemetry, transformed into Web-based and printed documentation, and used in developing new ground-system data-handling software. Previously, the information about telemetry and command was scattered in various paper documents that were not synchronized. The process of searching and reading the documents was time-consuming and introduced errors. In contrast, the XML files contain all of the information in one place. XML structures can evolve in such a manner as to enable the addition, to the XML files, of the metadata necessary to track the changes and the associated documentation. The use of this software has reduced the extent of manual operations in developing a ground data system, thereby saving considerable time and removing errors that previously arose in the translation and transcription of software information from the flight to the ground system.

Wright, Jesse↗
NASA NTRS2017

Materials Science Corrosion Internship Overview

The overarching purpose of this semester-long internship at the National Aeronautics and Space Administration's (NASA) John F. Kennedy Space Center (KSC) was to study the impacts of corrosion regarding the development of ground support equipment (GSE), launch support structures, and flight hardware in aid of the Space Launch System (SLS) and Orion program. Environmental corrosion is known as one of the largest material degradation issues for any structure comprised of metal on the Space Coast and requires the initiation of special protective measures for proper corrosion mitigation. The four (4) projects to be described were conducted with NASA Civil Servants and NASA Contractors who provided necessary resources to ensure the highest quality of data acquisition and knowledge transfer. The main objective shared between all four (4) of the following projects was to assess the modes by which corrosion takes place in multiple environments as well as the methods by which these modes of corrosion can be reduced for the enhancement of the mechanical, structural, and chemical compatibility of those respective environments with different candidate metals. A multitude of test methods were performed over the duration of this internship to assess the corrosive properties of these different candidate metals.

Ground Systems Development and Operations↗