Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Space Operations Center”

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 289 records · Page 16
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Tool for Forecasting Cool-Season Peak Winds Across Kennedy Space Center and Cape Canaveral Air Force Station

The expected peak wind speed for the day is an important element in the daily morning forecast for ground and space launch operations at Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS). The 45th Weather Squadron (45 WS) must issue forecast advisories for KSC/CCAFS when they expect peak gusts for >= 25, >= 35, and >= 50 kt thresholds at any level from the surface to 300 ft. In Phase I of this task, the 45 WS tasked the Applied Meteorology Unit (AMU) to develop a cool-season (October - April) tool to help forecast the non-convective peak wind from the surface to 300 ft at KSC/CCAFS. During the warm season, these wind speeds are rarely exceeded except during convective winds or under the influence of tropical cyclones, for which other techniques are already in use. The tool used single and multiple linear regression equations to predict the peak wind from the morning sounding. The forecaster manually entered several observed sounding parameters into a Microsoft Excel graphical user interface (GUI), and then the tool displayed the forecast peak wind speed, average wind speed at the time of the peak wind, the timing of the peak wind and the probability the peak wind will meet or exceed 35, 50 and 60 kt. The 45 WS customers later dropped the requirement for >= 60 kt wind warnings. During Phase II of this task, the AMU expanded the period of record (POR) by six years to increase the number of observations used to create the forecast equations. A large number of possible predictors were evaluated from archived soundings, including inversion depth and strength, low-level wind shear, mixing height, temperature lapse rate and winds from the surface to 3000 ft. Each day in the POR was stratified in a number of ways, such as by low-level wind direction, synoptic weather pattern, precipitation and Bulk Richardson number. The most accurate Phase II equations were then selected for an independent verification. The Phase I and II forecast methods were compared using an independent verification data set. The two methods were compared to climatology, wind warnings and advisories issued by the 45 WS, and North American Mesoscale (NAM) model (MesoNAM) forecast winds. The performance of the Phase I and II methods were similar with respect to mean absolute error. Since the Phase I data were not stratified by precipitation, this method's peak wind forecasts had a large negative bias on days with precipitation and a small positive bias on days with no precipitation. Overall, the climatology methods performed the worst while the MesoNAM performed the best. Since the MesoNAM winds were the most accurate in the comparison, the final version of the tool was based on the MesoNAM winds. The probability the peak wind will meet or exceed the warning thresholds were based on the one standard deviation error bars from the linear regression. For example, the linear regression might forecast the most likely peak speed to be 35 kt and the error bars used to calculate that the probability of >= 25 kt = 76%, the probability of >= 35 kt = 50%, and the probability of >= 50 kt = 19%. The authors have not seen this application of linear regression error bars in any other meteorological applications. Although probability forecast tools should usually be developed with logistic regression, this technique could be easily generalized to any linear regression forecast tool to estimate the probability of exceeding any desired threshold . This could be useful for previously developed linear regression forecast tools or new forecast applications where statistical analysis software to perform logistic regression is not available. The tool was delivered in two formats - a Microsoft Excel GUI and a Tool Command Language/Tool Kit (Tcl/Tk) GUI in the Meteorological Interactive Data Display System (MIDDS). The Microsoft Excel GUI reads a MesoNAM text file containing hourly forecasts from 0 to 84 hours, from one model run (00 or 12 UTC). The GUI then displays e peak wind speed, average wind speed, and the probability the peak wind will meet or exceed the 25-, 35- and 50-kt thresholds. The user can display the Day-1 through Day-3 peak wind forecasts, and separate forecasts are made for precipitation and non-precipitation days. The MIDDS GUI uses data from the NAM and Global Forecast System (GFS), instead of the MesoNAM. It can display Day-1 and Day-2 forecasts using NAM data, and Day-1 through Day-5 forecasts using GFS data. The timing of the peak wind is not displayed, since the independent verification showed that none of the forecast methods performed significantly better than climatology. The forecaster should use the climatological timing of the peak wind (2248 UTC) as a first guess and then adjust it based on the movement of weather features.

Barrett, Joe H., III↗
NASA NTRS1992

Introduction to Space Station Freedom

NASA field centers and contractors are organized to develop 'work packages' for Space Station Freedom. Marshall Space Flight Center and Boeing are building the U.S. laboratory and habitation modules, nodes, and environmental control and life support system; Johnson Space Center and McDonnell Douglas are responsible for truss structure, data management, propulsion systems, thermal control, and communications and guidance; Lewis Research Center and Rocketdyne are developing the power system. The Canadian Space Agency (CSA) is contributing a Mobile Servicing Center, Special Dextrous Manipulator, and Mobile Servicing Center Maintenance Depot. The National Space Development Agency of Japan (NASDA) is contributing a Japanese Experiment Module (JEM), which includes a pressurized module, logistics module, and exposed experiment facility. The European Space Agency (ESA) is contributing the Columbus laboratory module. NASA ground facilities, now in various stages of development to support Space Station Freedom, include: Marshall Space Flight Center's Payload Operations Integration Center and Payload Training Complex (Alabama), Johnson Space Center's Space Station Control Center and Space Station Training Facility (Texas), Lewis Research Center's Power System Facility (Ohio), and Kennedy Space Center's Space Station Processing Facility (Florida). Budget appropriations impact the development of the Space Station. In Fiscal Year 1988, Congress appropriated only half of the funds that NASA requested for the space station program ($393 million vs. $767 million). In FY 89, NASA sought $967 million for the program, and Congress appropriated $900 million. NASA's FY 90 request was $2.05 billion compared to an appropriation of $1.75 billion; the FY 91 request was $2.45 billion, and the appropriation was $1.9 billion. After NASA restructured the Space Station Freedom program in response to directions from Congress, the agency's full budget request of $2.029 billion for Space Station Freedom in FY 92 was appropriated. For FY 93, NASA is seeking $2.25 billion for the program; the planned budget for FY 94 is $2.5 billion. Further alterations to the hardware configuration for Freedom would be a serious setback; NASA intends 'to stick with the current baseline' and continue planning for utilization.

Kohrs, Richard↗
NASA NTRS2013

Objective Lightning Probability Forecasts for East-Central Florida Airports

The forecasters at the National Weather Service in Melbourne, FL, (NWS MLB) identified a need to make more accurate lightning forecasts to help alleviate delays due to thunderstorms in the vicinity of several commercial airports in central Florida at which they are responsible for issuing terminal aerodrome forecasts. Such forecasts would also provide safer ground operations around terminals, and would be of value to Center Weather Service Units serving air traffic controllers in Florida. To improve the forecast, the AMU was tasked to develop an objective lightning probability forecast tool for the airports using data from the National Lightning Detection Network (NLDN). The resulting forecast tool is similar to that developed by the AMU to support space launch operations at Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS) for use by the 45th Weather Squadron (45 WS) in previous tasks (Lambert and Wheeler 2005, Lambert 2007). The lightning probability forecasts are valid for the time periods and areas needed by the NWS MLB forecasters in the warm season months, defined in this task as May-September.

Crawford, Winfred C.↗
NASA NTRS2024

Concept, Design, & Implementation of a Remote Vehicle Operations Center for Autonomous Missions

The National Aeronautics and Space Administration is supporting research to develop a prototype remote vehicle operations center at Langley Research Center to explore current and future advanced air mobility operations using small unmanned aerial systems vehicles as surrogates for future, larger-scale passenger carrying vehicles. The prototype facility known as the Remote Operations for Autonomous Missions (ROAM) Unmanned Aerial Systems (UAS) Operations Center is being used to explore different roles and responsibilities of remote operators managing multiple autonomous vehicles, with the goal of exploring human-autonomy teaming concepts that enable m:N operations (i.e., m operators managing N vehicles). ROAM has developed into a world-class research, development, and technology (RD&T) environment that can support both the collection of human factors data and the command and control of remote vehicles in beyond visual line of sight conditions. ROAM provides a key capability to enable full end-to-end hardware- and human-in-the-loop simulation testing, connecting with simulated small-UAS and creating a seamless Live-Virtual-Constructive (LVC) environment. This report describes the development of the ROAM UAS Operations Center from concept through design, culminating in the current implementation at NASA’s Langley Research Center.

CERTAIN↗
NASA NTRS2013

Conducting Research on the International Space Station Using the EXPRESS Rack Facilities

Eight "Expedite the Processing of Experiments to Space Station" (EXPRESS) Rack facilities are located within the International Space Station (ISS) laboratories to provide standard resources and interfaces for the simultaneous and independent operation of multiple experiments within each rack. Each EXPRESS Rack provides eight Middeck Locker Equivalent locations and two drawer locations for powered experiment equipment, also referred to as sub-rack payloads. Payload developers may provide their own structure to occupy the equivalent volume of one, two, or four lockers as a single unit. Resources provided for each location include power (28 Vdc, 0-500 W), command and data handling (Ethernet, RS-422, 5 Vdc discrete, +/- 5 Vdc analog), video (NTSC/RS 170A), and air cooling (0-200 W). Each rack also provides water cooling (500 W) for two locations, one vacuum exhaust interface, and one gaseous nitrogen interface. Standard interfacing cables and hoses are provided on-orbit. One laptop computer is provided with each rack to control the rack and to accommodate payload application software. Four of the racks are equipped with the Active Rack Isolation System to reduce vibration between the ISS and the rack. EXPRESS Racks are operated by the Payload Operations Integration Center at Marshall Space Flight Center and the sub-rack experiments are operated remotely by the investigating organization. Payload Integration Managers serve as a focal to assist organizations developing payloads for an EXPRESS Rack. NASA provides EXPRESS Rack simulator software for payload developers to checkout payload command and data handling at the development site before integrating the payload with the EXPRESS Functional Checkout Unit for an end-to-end test before flight. EXPRESS Racks began supporting investigations onboard ISS on April 24, 2001 and will continue through the life of the ISS.

Thompson, Sean W.↗
NASA NTRS2016

Conducting Research on the International Space Station using the EXPRESS Rack Facilities

Eight "Expedite the Processing of Experiments to Space Station" (EXPRESS) Rack facilities are located within the International Space Station (ISS) laboratories to provide standard resources and interfaces for the simultaneous and independent operation of multiple experiments within each rack. Each EXPRESS Rack provides eight Middeck Locker Equivalent locations and two drawer locations for powered experiment equipment, also referred to as sub-rack payloads. Payload developers may provide their own structure to occupy the equivalent volume of one, two, or four lockers as a single unit. Resources provided for each location include power (28 Vdc, 0-500 W), command and data handling (Ethernet, RS-422, 5 Vdc discrete, +/- 5 Vdc analog), video (NTSC/RS 170A), and air cooling (0-200 W). Each rack also provides water cooling for two locations (500W ea.), one vacuum exhaust interface, and one gaseous nitrogen interface. Standard interfacing cables and hoses are provided on-orbit. One laptop computer is provided with each rack to control the rack and to accommodate payload application software. Four of the racks are equipped with the Active Rack Isolation System to reduce vibration between the ISS and the rack. EXPRESS Racks are operated by the Payload Operations Integration Center at Marshall Space Flight Center and the sub-rack experiments are operated remotely by the investigating organization. Payload Integration Managers serve as a focal to assist organizations developing payloads for an EXPRESS Rack. NASA provides EXPRESS Rack simulator software for payload developers to checkout payload command and data handling at the development site before integrating the payload with the EXPRESS Functional Checkout Unit for an end-to-end test before flight. EXPRESS Racks began supporting investigations onboard ISS on April 24, 2001 and will continue through the life of the ISS.

Thompson, Sean W.↗
NASA NTRS2017

Upgrades to Common Data Acquisition System Software Development for NASA's Rocket Propulsion Test Facilities and Software Reuse

Approximately five years ago, the National Aeronautics and Space Administration (NASA) Stennis Space Center (SSC) resumed operation of its large rocket engine test facilities after thirty years of contractor control. During this period, contactors used their own proprietary Data Acquisition System (DAS) to record and process rocket propulsion test data. The transition from a contractor managed facility to a NASA managed facility posed a difficult challenge. In order to support the commercial space launch initiative, SSC needed to develop a software replacement for the contractor proprietary DAS. This replacement software would enable SSC to operate propulsion test facilities more cost effectively and to be more readily able to adapt software for reuse, while at the same time provide internal and external customers with reliable population test data. Therefore, SSC developed in-house, a non-proprietary software suite of applications to replace the previously used proprietary DAS. The requirements for the DAS suite included recording and processing propulsion test data. This capability eliminates the necessity for customers to provide a DAS or rely on a competitor's DAS. An additional benefit of owning the software suite included enabling the ability to add additional features and functionality at a lower cost. The Rocket Propulsion Test (RPT) Program Office reviewed consideration for funding this project with the caveat that development of the software included availability for use with minimal modifications to all SSC test facilities and RPT centers: Marshall Space Flight Center (MSFC), White Sands Test Facility (WSTF), and Glenn Research Center (GRC) Plum Brook Station. Based upon this guideline, SSC created the NASA Data Acquisition System (NDAS) software suite. The ability to use the software at multiple centers, even though each field center uses differing DAS hardware with different capabilities, drove a requirement that the software design be portable with minimal modifications to the software. Then, with software release requirements, evaluations, and approvals completed, the NDAS software suite could also become available to other government agencies, corporations, universities, and the general United States public.

Herbert, Phillip W., Sr.↗
NASA NTRS2006

Medical Operations Console Procedure Evaluation: BME Response to Crew Call Down for an Emergency

International Space Station (ISS) Mission Operations are managed by multiple flight control disciplines located at the lead Mission Control Center (MCC) at NASA-Johnson Space Center (JSC). ISS Medical Operations are supported by the complementary roles of Flight Surgeons (Surgeon) and Biomedical Engineer (BME) flight controllers. The Surgeon, a board certified physician, oversees all medical concerns of the crew and the BME provides operational and engineering support for Medical Operations Crew Health Care System. ISS Medical Operations is currently addressing the coordinated response to a crew call down for an emergent medical event, in particular when the BME is the only Medical Operations representative in MCC. In this case, the console procedure BME Response to Crew Call Down for an Emergency will be used. The procedure instructs the BME to contact a Surgeon as soon as possible, coordinate with other flight disciplines to establish a Private Medical Conference (PMC) for the crew and Surgeon, gather information from the crew if time permits, and provide Surgeon with pertinent console resources. It is paramount that this procedure is clearly written and easily navigated to assist the BME to respond consistently and efficiently. A total of five BME flight controllers participated in the study. Each BME participant sat in a simulated MCC environment at a console configured with resources specific to the BME MCC console and was presented with two scripted emergency call downs from an ISS crew member. Each participant used the procedure while interacting with analog MCC disciplines to respond to the crew call down. Audio and video recordings of the simulations were analyzed and each BME participant's actions were compared to the procedure. Structured debriefs were conducted at the conclusion of both simulations. The procedure was evaluated for its ability to elicit consistent responses from each BME participant. Trials were examined for deviations in procedure task completion and/or navigation, in particular the execution of the Surgeon call sequence. Debrief comments were used to analyze unclear procedural steps and to discern any discrepancies between the procedure and generally accepted BME actions. The sequence followed by BME participants differed considerably from the sequence intended by the procedure. Common deviations included the call sequence used to contact Surgeon, the content of BME and crew interaction and the gathering of pertinent console resources. Differing perceptions of task priority and imprecise language seem to have caused multiple deviations from the procedure s intended sequence. The study generated 40 recommendations for the procedure, of which 34 are being implemented. These recommendations address improving the clarity of the instructions, identifying training considerations, expediting Surgeon contact, improving cues for anticipated flight control team communication and identifying missing console tools.

Johnson-Troop↗
NASA NTRS2003

Universal Payload Information Management

As the overall manager and integrator of International Space Station (ISS) science payloads, the Payload Operations Integration Center (POIC) at Marshall Space Flight Center has a critical need to provide an information management system for exchange and control of ISS payload files as well as to coordinate ISS payload related operational changes. The POIC's information management system has a fundamental requirement to provide secure operational access not only to users physically located at the POIC, but also to remote experimenters and International Partners physically located in different parts of the world. The Payload Information Management System (PIMS) is a ground-based electronic document configuration management and collaborative workflow system that was built to service the POIC's information management needs. This paper discusses the application components that comprise the PIMS system, the challenges that influenced its design and architecture, and the selected technologies it employs. This paper will also touch on the advantages of the architecture, details of the user interface, and lessons learned along the way to a successful deployment. With PIMS, a sophisticated software solution has been built that is not only universally accessible for POIC customer s information management needs, but also universally adaptable in implementation and application as a generalized information management system.

Elmore, Ralph B.↗
NASA NTRS2011

Kennedy Space Center Orion Processing Team Planning for Ground Operations

Topics in this presentation are: Constellation Ares I/Orion/Ground Ops Elements Orion Ground Operations Flow Orion Operations Planning Process and Toolset Overview, including: 1 Orion Concept of Operations by Phase 2 Ops Analysis Capabilities Overview 3 Operations Planning Evolution 4 Functional Flow Block Diagrams 5 Operations Timeline Development 6 Discrete Event Simulation (DES) Modeling 7 Ground Operations Planning Document Database (GOPDb) Using Operations Planning Tools for Operability Improvements includes: 1 Kaizen/Lean Events 2 Mockups 3 Human Factors Analysis

Letchworth, Gary↗
NASA NTRSDate not supplied

Reducing Barriers in Space Weather Research and Operations with Next-Generation Simulation Services at the Community Coordinated Modeling Center (CCMC)

Space weather forecasting capabilities are becoming increasingly important to the health of advanced technological infrastructure. The Community Coordinated Modeling Center (CCMC, https://ccmc.gsfc.nasa.gov) serves as a key liaison in the US space weather program between the research and operations communities by providing a wide range of tools and capabilities that help to evaluate, compare, exercise, and archive the results of simulations of a growing list of space weather models. With its unique toolset, CCMC supports space weather research and model development that advances our understanding of space weather phenomena and improves forecasting skill, while also facilitating development of space weather applications and deployment of operational capabilities. Guided by experience from over 20 years of providing simulation services, feedback from its research, operational and educational users world-wide, recommendations from CCMC Advisory Group and Programmatic Review Panel, the CCMC has begun work on the next generation system for its simulation services and model output archives. The new system has been envisioned to employ state-of-the-art technologies and standards to provide a user-oriented experience while improving ease of access, transparency, interoperability with partner systems, and enhancing reliability by incorporating advanced automation for performance monitoring and intelligent failover. In the presentation, we will give an overview of the current CCMC ecosystem and discuss updates to some of the key services of the system, including Runs-on-Request, Instant Runs, and Continuous Runs. We will also describe how a planned expansion and standardization of data archival activities will enhance the role of CCMC as a world-class provider of heliophysics information for the research and analysis of space weather. It is our hope that this evolution of the services can further reduce the barriers and burdens on researchers, forecasters and decision makers who rely on CCMC for their daily research and operations.

Space Weather↗
NASA NTRS2019

Utilization of Unsupervised Anomalies Detector as a Tool for Managing the TDRS Constellation at GSFC

NASA’s Goddard Space Flight Center (GSFC) operates a constellation of ten geosynchronous Tracking and Data Relay Satellites (TDRS). The mission of the TDRS constellation is to provide relay communications from low-earth orbiting spacecraft to the primary ground station at the White Sands Complex in Las Cruces, New Mexico. Major customers include the International Space Station and Hubble Space Telescope. The NASA Space Network project office at GSFC manages the constellation of spacecraft. The constellation is over 30 years old, and a wide range of technologies and manufacturing techniques are represented on-orbit. Since 1983, the TDRS constellation has recorded thousands of gigabytes of telemetry data. Spacecraft telemetry data has changed throughout the three generations of TDRS spacecraft, however each spacecraft has the same basic functions with some generational enhancements. The constellation includes several spacecraft that have significantly outlived the manufacturer's projected lifetime. This has provided NASA with a significant benefit in terms of return on investment, however it places a burden on efficient management of the assets for maximum life without permitting a TDRS spacecraft to become stranded in its geosynchronous orbital slot. Consequently, the highest level of attention is paid to systems whose failure could strand a TDRS spacecraft in orbit. In this paper, we proposed two stages of analyzing spacecraft anomalies using data mining (DM) to enhance on-going predictions of spacecraft life, subsystem performance, and analysis of subsystem anomalies. The first stage conducts the unsupervised anomaly detector to detect potential anomalies in real-time telemetry data. The second stage introduced telemetry weight (TW) to each telemetry parameter to determine which parameter caused the strongest anomaly. We will present case studies of some of these analyses and how the data can impact decisions on the management of the constellation.

Ma, Kenneth Y.↗
NASA NTRS1989

Research and technology at Kennedy Space Center

As the NASA Center responsible for assembly, checkout, servicing, launch, recovery, and operational support of Space Transportation System elements and payloads, Kennedy Space Center is placing increasing emphasis on the Center's research and technology program. In addition to strengthening those areas of engineering and operations technology that contribute to safer, more efficient, and more economical execution of current mission, the technical tools are developed needed to execute Center's mission relative to future programs. The Engineering Development Directorate encompasses most of the laboratories and other Center resources that are key elements of research and technology program implementation and is responsible for implementation of the majority of the projects in this Kennedy Space Center 1989 Annual Report.

Source record↗
NASA NTRS1980

DSN Monitor and Control System, Mark III-80

The Deep Space Network monitor and control system, Mark III-80 is described. The major implementations required to evolve from the Mark III-78 to the Mark III-80 configuration are identified. The affected facilities are the deep space stations and the network operations control center (NOCC). At the deep space stations a stand-alone host processor is implemented. Included are software (host software) changes which provide downline loading to the stand-alone host processor from a disc unit of any idle data system computer. At deep space stations with a 34 m antenna, the microwave subsystem is provided with an interface which allows remote configuration selection at the central monitor and control operator's position. In the NOCC, software changes are implemented to provide precision power monitor and GCF monitor displays.

Leflang, J. G.↗
NASA NTRS1987

Research and technology 1987 annual report of the Kennedy Space Center

As the NASA Center responsible for assembly, checkout, servicing, launch, recovery, and operational support of Space Transportation System elements and payloads, Kennedy Space Center is placing increasing emphasis on the Center's research and technology program. In addition to strengthening those areas of engineering and operations technology that contribute to safer, more efficient, and more economical execution of our current mission, we are developing the technological tools needed to execute the Center's mission relative to future programs. The Engineering Development Directorate encompasses most of the laboratories and other Center resources that are key elements of research and technology program implementation, and is responsible for implementation of the majority of the projects of this Kennedy Space Center 1987 Annual Report.

Source record↗