Search NASA⌕ Search

SEARCH · Search NASA

Results for “building management 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 343 records · Page 19

2021 Corrective Measures Implementation and Interim Measures Annual Status Report: Summary of Biosparge System Operation and Maintenance, and Interim Groundwater Monitoring Mobile Launch Platform Rehabilitation Sites / Vehicle Assembly Building Area (SWMU 056) Kennedy Space Center, Florida

This report presents a summary of the Corrective Measures Implementation (CMI) and Interim Measure (IM) implementation activities that occurred from January 2021 through December 2021 at the Mobile Launch Platform Rehabilitation Sites (MLP)/Vehicle Assembly Building (VAB) Area, Solid Waste Management Unit 056 (SWMU 056), located at the John F. Kennedy Space Center, Florida. The following summaries briefly describe areas within SWMU 056 identified by historical site investigation activities where groundwater monitoring and remedial actions have been implemented to date.

Randall K. Sillan↗

2022 Through April 2023 Corrective Measures Implementation and Interim Measures Annual Status Report: Summary of Biosparge System Operation and Maintenance, Interim Measures and Monitoring Mobile Launch Platform Rehabilitation Sites / Vehicle Assembly Building Area (Swmu 056) Kennedy Space Center, Florida

This report presents a summary of the Corrective Measures Implementation (CMI) and Interim Measure (IM) implementation activities that occurred from January 2022 through April 2023 at the Mobile Launch Platform Rehabilitation Sites (MLP)/Vehicle Assembly Building (VAB) Area, Solid Waste Management Unit 056 (SWMU 056), located at the John F. Kennedy Space Center, Florida. The following summaries briefly describe areas within SWMU 056 identified by historical site investigation activities where groundwater monitoring and remedial actions have been implemented to date.

VOCs↗

Static Frequency Converter System Installed and Tested

A new Static Frequency Converter (SFC) system has been installed and tested at the NASA Glenn Research Center s Central Air Equipment Building to provide consistent, reduced motor start times and improved reliability for the building s 14 large exhausters and compressors. The operational start times have been consistent around 2 min, 20 s per machine. This is at least a 3-min improvement (per machine) over the old variable-frequency motor generator sets. The SFC was designed and built by Asea Brown Boveri (ABB) and installed by Encompass Design Group (EDG) as part of a Construction of Facilities project managed by Glenn (Robert Scheidegger, project manager). The authors designed the Central Process Distributed Control Systems interface and control between the programmable logic controller, solid-state exciter, and switchgear, which was constructed by Gilcrest Electric.

Brown, Donald P.↗

A Bioinformatics Facility for NASA

Building on an existing prototype, we have fielded a facility with bioinformatics technologies that will help NASA meet its unique requirements for biological research. This facility consists of a cluster of computers capable of performing computationally intensive tasks, software tools, databases and knowledge management systems. Novel computational technologies for analyzing and integrating new biological data and already existing knowledge have been developed. With continued development and support, the facility will fulfill strategic NASA s bioinformatics needs in astrobiology and space exploration. . As a demonstration of these capabilities, we will present a detailed analysis of how spaceflight factors impact gene expression in the liver and kidney for mice flown aboard shuttle flight STS-108. We have found that many genes involved in signal transduction, cell cycle, and development respond to changes in microgravity, but that most metabolic pathways appear unchanged.

Schweighofer, Karl↗

Mapping the User Journey: Building a User Persona and Story Repository to Improve NASA EOSDIS Application Development

Understanding the needs of the end user is vital to producing quality, usable software that solves real problems. Additionally, making sure those needs are communicated to managers, engineers, and designers at the project level is vital. On complex projects, it's important to build out resources for your team that make it easy to put yourself in the shoes of the specific user you're building for. NASA's Earth Observing System is a collection of data, applications, and a diverse user and scientific community that's trying to answer tough questions about our planet and its climate. Over the last few years, we've spoken to hundreds of users, performed many user testing sessions, and built a collection of user personas, user stories, and design assets that help guide new software and feature development within NASA EOSDIS. We've also developed methods for synthesizing this information and making it actionable for teams, and worked to foster a design first approach on new projects always starting from a core user need and working backward from interface development to software engineering. This process has allowed us to design better, more usable software and features that directly meet the needs of our user community.

Siarto, Jeff↗

Satellite Servicing Capabilities Office Testing

While at the KSC, I was given the opportunity of assisting the Satellite Servicing Capabilities Office (SSCO) specifically the Propellant Transfer System (PTS) lead by my mentor, Brian Nufer. While waiting to test different components in the PTS, I was able to assist with testing for the Hose Management Assembly (HMA) and was able to work on a simulation in Labview. For the HMA, I was able to help with testing of a coating as well as to help test the durability of the pinch rollers in space. In Labview, I experimented with building a simulation for the PTS, to show where fluids and gases were flowing depending on which valves in the PTS were opened. Not all of the integrated parts required assembly level testing, which allowed me to test these parts individually by myself and document the results. I was also able to volunteer to assist project NEO, allowing me to gain some knowledge of cryogenic fluid systems.

PTS↗

Building a COTS archive for satellite data

The goal of the NOAA/NESDIS Active Archive was to provide a method of access to an online archive of satellite data. The archive had to manage and store the data, let users interrogate the archive, and allow users to retrieve data from the archive. Practical issues of the system design such as implementation time, cost and operational support were examined in addition to the technical issues. There was a fixed window of opportunity to create an operational system, along with budget and staffing constraints. Therefore, the technical solution had to be designed and implemented subject to constraint imposed by the practical issues. The NOAA/NESDIS Active Archive came online in July of 1994, meeting all of its original objectives.

Singer, Ken↗

Overview of Model-Based Systems Engineering Efforts to Evolve the Airspace Research Roadmap

NASA’s Air Traffic Management-Exploration (ATM-X) UAM Airspace Subproject is conducting research that evolves UAM airspace towards a highly automated and operationally flexible system of the future. The complexity of UAM airspace evolution requires a plan to effectively organize, integrate, and communicate NASA’s research and development. The planning tool, called the UAM airspace research roadmap, or just roadmap, is key to the execution of NASA’s UAM airspace research over the next ten years. Implemented through Model-Based Systems Engineering (MBSE) methodology, the roadmap will help to prioritize and coordinate research efforts, and to integrate results that build towards NASA’s research goals of evolving UAM airspace for integration of UAM operations into the National Airspace System (NAS). This paper presents an overview of on-going MBSE efforts to meet these overarching goals.

Model-Based Systems Engineering↗

NASA's Space Launch System Progress Report

Exploration beyond Earth will be an enduring legacy for future generations, confirming America's commitment to explore, learn, and progress. NASA's Space Launch System (SLS) Program, managed at the Marshall Space Flight Center, is responsible for designing and developing the first exploration-class rocket since the Apollo Program's Saturn V that sent Americans to the Moon. The SLS offers a flexible design that may be configured for the MultiPurpose Crew Vehicle and associated equipment, or may be outfitted with a payload fairing that will accommodate flagship science instruments and a variety of high-priority experiments. Both options support a national capability that will pay dividends for future generations. Building on legacy systems, facilities, and expertise, the SLS will have an initial lift capability of 70 metric tons (mT) and will be evolvable to 130 mT. While commercial launch vehicle providers service the International Space Station market, this capability will surpass all vehicles, past and present, providing the means to do entirely new missions, such as human exploration of asteroids and Mars. With its superior lift capability, the SLS can expand the interplanetary highway to many possible destinations, conducting revolutionary missions that will change the way we view ourselves, our planet and its place in the cosmos. To perform missions such as these, the SLS will be the largest launch vehicle ever built. It is being designed for safety and affordability - to sustain our journey into the space age. Current plans include launching the first flight, without crew, later this decade, with crewed flights beginning early next decade. Development work now in progress is based on heritage space systems and working knowledge, allowing for a relatively quick start and for maturing the SLS rocket as future technologies become available. Together, NASA and the U.S. aerospace industry are partnering to develop this one-of-a-kind asset. Many of NASA's space centers across the country will provide their unique expertise to the Space Launch System endeavor. Unique infrastructure to be used includes the Michoud Assembly Facility for tank manufacturing, Stennis Space Center for engine testing, and Kennedy Space Center for processing and launch. As this panel will discuss, the SLS team is dedicated to doing things differently-from applying lean oversight/insight models to smartly using legacy hardware and existing facilities. Building on the foundation laid by over 50 years of human and scientific space flight--and on the lessons learned from the Apollo, Space Shuttle, and Constellation Programs-the SLS team has delivered both technical trade studies and business case analyses to ensure that the SLS architecture will be safe, affordable, reliable, and sustainable.

Singer, Joan A.↗

The SEL Adapts to Meet Changing Times

Since 1976, the Software Engineering Laboratory (SEL) has been dedicated to understanding and improving the way in which one NASA organization, the Flight Dynamics Division (FDD) at Goddard Space Flight Center, develops, maintains, and manages complex flight dynamics systems. It has done this by developing and refining a continual process improvement approach that allows an organization such as the FDD to fine-tune its process for its particular domain. Experimental software engineering and measurement play a significant role in this approach. The SEL is a partnership of NASA Goddard, its major software contractor, Computer Sciences Corporation (CSC), and the University of Maryland's (LTM) Department of Computer Science. The FDD primarily builds software systems that provide ground-based flight dynamics support for scientific satellites. They fall into two sets: ground systems and simulators. Ground systems are midsize systems that average around 250 thousand source lines of code (KSLOC). Ground system development projects typically last 1 - 2 years. Recent systems have been rehosted to workstations from IBM mainframes, and also contain significant new subsystems written in C and C++. The simulators are smaller systems averaging around 60 KSLOC that provide the test data for the ground systems. Simulator development lasts up to 1 year. Most of the simulators have been built in Ada on workstations. The SEL is responsible for the management and continual improvement of the software engineering processes used on these FDD projects.

Pajerski, Rose S.↗

Accrued Delay Application in Trajectory-Based Operations

The air traffic management system lacks integration among its elements often due to using inconsistent information, models, and metrics about the traffic. Transitioning to trajectory-based operations, whereby flights are managed by full trajectories in space and time, will enable more integration, with the help of increased automation. Building on trajectory-based operations, an "accrued delay" metric is proposed, which continuously measures the amount of delay that a flight has accumulated up to the current time, including delays incurred during the current flight and inherited from previous flights through the turnaround process. Through a time-based metering and scheduling example, we show how using accrued delay as a metric can help integrate the decision-making across multiple decision horizons, leading to more efficient and balanced access to airspace services. We show that when prioritizing flights that have already accrued high delay because of a constrained runway resource, significant gains are achieved in terms of reducing total delay and its variance. We studied the sensitivity of these gains to numerous factors, such as time-based versus distance-based horizons, horizon size, and errors in conformance to scheduled times.

delay; trajectory-based operations; time-based flo↗

Accrued Delay Application in Trajectory-Based Operations

The air traffic management system lacks integration among its elements often due to using inconsistent information, models, and metrics about the traffic. Transitioning to trajectory-based operations, whereby flights are managed by full trajectories in space and time, will enable more integration, with the help of increased automation. Building on trajectory-based operations, an "accrued delay" metric is proposed, which continuously measures the amount of delay that a flight has accumulated up to the current time, including delays incurred during the current flight and inherited from previous flights through the turnaround process. Through a time-based metering and scheduling example, we show how using accrued delay as a metric can help integrate the decision-making across multiple decision horizons, leading to more efficient and balanced access to airspace services. We show that when prioritizing flights that have already accrued high delay because of a constrained runway resource, significant gains are achieved in terms of reducing total delay and its variance. We studied the sensitivity of these gains to numerous factors, such as time-based versus distance-based horizons, horizon size, and errors in conformance to scheduled times.

Idris, Husni↗

Advanced eLectrical Bus (ALBus) CubeSat: From Build to Flight

The Advanced eLectrical Bus (ALBus) CubeSat project is a technology demonstration mission of a 3-U CubeSat with an advanced, digitally controlled electrical power system capability and novel use of Shape Memory Alloy (SMA) technology for reliable deployable solar array mechanisms. The objective of the project was to advance the state of power management and distribution (PMAD) capabilities to enable future missions requiring flexible and reliable power systems with higher output power capabilities. The goals of the mission were to demonstrate 100W distribution to a target electrical load, respond to continuous and fast transient power requirements, and show reliable deployment of solar arrays and antennas utilizing re-settable SMA mechanisms. The power distribution function of the ALBus PMAD system is unique in the total power to target load capability. Power is distributed from batteries to provide 100W of power directly to a resistive load. The deployable solar arrays utilize NASA Glenn Research Center’s Nickel-Titanium-Palladium-Platinum high-temperature SMAs for the retention and release mechanism, and a super-elastic binary NiTi alloy for the hinge component. The deployable solar array hinge design features the utilization of SMA material properties for a dual purpose. First, the hinge uses the super-elastic SMA properties to provide the spring force to deploy the arrays. Second, the electrical conductivity properties of the SMA enables the design to provide clean conduits for power transfer from the deployable arrays to the power management system. This eliminates the need for electrical harnesses between the arrays and the PMAD system in the ALBus system design. The uniqueness of the SMA retention and release mechanism design is the ability to reset the mechanism and reuse the same hardware. This allow functional tests of the mechanisms before flight with no degradation of performance and flying the hardware that is tested. The project launched as part of the CubeSat Launch Initiative Educational Launch of Nanosatellites (ELaNa) XIX mission on Rocket Lab’s Electron in December 2018. This paper summarizes the final launched design of ALBus and lessons learned from the technology and overall project from development through flight.

Deboshri Sadhukhan↗

NASA Agile Community of Practice 2024-2026 Report

This 2024-2026 report provides a summary of the products and activities executed by the NASA Agile Community of Practice (CoP) during its second and third years. Building on the foundation established in its inaugural year, the CoP continued to advance Agile values and principles across NASA centers. The report highlights key initiatives, including specialized framework training, AI integration in Agile toolkits, and active participation in agency-wide project management and systems engineering workshops.

Agile↗

A Review of Diagnostic Techniques for ISHM Applications

System diagnosis is an integral part of any Integrated System Health Management application. Diagnostic applications make use of system information from the design phase, such as safety and mission assurance analysis, failure modes and effects analysis, hazards analysis, functional models, fault propagation models, and testability analysis. In modern process control and equipment monitoring systems, topological and analytic , models of the nominal system, derived from design documents, are also employed for fault isolation and identification. Depending on the complexity of the monitored signals from the physical system, diagnostic applications may involve straightforward trending and feature extraction techniques to retrieve the parameters of importance from the sensor streams. They also may involve very complex analysis routines, such as signal processing, learning or classification methods to derive the parameters of importance to diagnosis. The process that is used to diagnose anomalous conditions from monitored system signals varies widely across the different approaches to system diagnosis. Rule-based expert systems, case-based reasoning systems, model-based reasoning systems, learning systems, and probabilistic reasoning systems are examples of the many diverse approaches ta diagnostic reasoning. Many engineering disciplines have specific approaches to modeling, monitoring and diagnosing anomalous conditions. Therefore, there is no "one-size-fits-all" approach to building diagnostic and health monitoring capabilities for a system. For instance, the conventional approaches to diagnosing failures in rotorcraft applications are very different from those used in communications systems. Further, online and offline automated diagnostic applications are integrated into an operations framework with flight crews, flight controllers and maintenance teams. While the emphasis of this paper is automation of health management functions, striking the correct balance between automated and human-performed tasks is a vital concern.

Patterson-Hine, Ann↗

Gateway Implementation of Cybersecurity Requirements

Cybersecurity threats are a constant present-day reality for any type of business -- Space exploration is not excluded from these threats either. The Gateway Program is one of NASA’s latest initiatives that extend space exploration beyond low earth orbit. Gateway allows for NASA to prove technologies and mature systems necessary to live and work on another celestial body before embarking on multi-year missions to Mars. The Gateway is a small, human-tended space station in orbit around the Moon. With the increased autonomy, distance and criticality of systems, cybersecurity is a critical discipline that touches and integrates with most if not all subsystems of the Gateway. Building a gateway to the lunar orbit is no simple task. In this presentation, we outline an approach that the Gateway team adopted in creating a cyber safe and robust vehicle to support operations and assure protection of the critical functions. Gateway Program is required to implement National Institute of Standards and Technology (NIST) guidelines to adhere to the Federal Information Security Modernization Act (FISMA). NIST provides a framework for managing and controlling cybersecurity risks by defining cybersecurity controls and methodologies for implementation. The NIST framework is based upon the system, data within the system, integrations with external systems, and risk assessments to determine impacts for each of those systems. The goals and objectives are to identify appropriate security controls that fulfil and map to the NIST 800-53 framework. The implementation process involves developing an organizational understanding to manage cybersecurity risk to systems, people, assets, data, and capabilities. NIST Security controls are interpreted and defined within the Gateway vehicle requirements subsystems specifications. This paper details the approach, implementation, and challenges faced during the development and design phases to address cyber threats during the Gateway vehicle operations.

Cybersecurity↗

Regenerative (Regen) ECLSS Operations Water Balance

In November 2008, the Water Regenerative System racks were launched aboard Space Shuttle flight, STS-126 (ULF2) and installed and activated on the International Space Station (ISS). These racks, consisting of the Water Processor Assembly (WPA) and Urine Processor Assembly (UPA), completed the installation of the Regenerative (Regen) ECLSS systems which includes the Oxygen Generator Assembly (OGA) that was launched 2 years prior. With the onset of active water management on the US segment of the ISS, a new operational concept was required, that of "water balance." Even more recently, in 2010 the Sabatier system came online which converts H2 and CO2 into water and methane. The Regen ECLSS systems accept condensation from the atmosphere, urine from crew, and processes that fluid via various means into potable water which is used for crew drinking, building up skip-cycle water inventory, and water for electrolysis to produce oxygen. Specification rates of crew urine output, condensate output, O2 requirements, toilet flush water and drinking needs are well documented and used as a general plan when Regen ECLSS came online. Spec rates are useful in long term planning, however, daily or weekly rates are dependent on a number of variables. The constantly changing rates created a new challenge for the ECLSS flight controllers, who are responsible for operating the ECLSS systems onboard ISS. This paper will review the various inputs to rate changes and inputs to planning events, including but not limited to; crew personnel makeup, Regen ECLSS system operability, vehicle traffic, water containment availability, and Carbon Dioxide Removal Assembly (CDRA) capability. Along with the inputs that change the various rates, the paper will review the different systems, their constraints and finally the operational means by which flight controllers manage this new challenge of "water balance."

Tobias, Barry↗

Predicting Airport Runway Configurations for Decision-Support Using Supervised Learning

One of the most challenging tasks for air traffic controllers is runway configuration management (RCM). It deals with the optimal selection of runways to operate on (for arrivals and departures) based on traffic, surface wind speed, wind direction, other environmental variables, noise constraints, and several other airport-specific factors. It affects the efficiency of the National Airspace System (NAS) and both surface and airspace operations can benefit from better understanding future runway configurations. In this paper, we present a comprehensive implementation of predictive models for runway configuration estimation from large volumes of historical data. Specifically, operational data from two full years (2018 and 2019) is collected, analyzed, and fused together to build the data product used in this work. The data set differs from prior work in the field in terms of its scope, resolution, and variety of factors collected and considered. Meteorological data is collected from two different sources – current weather conditions from METAR (Meteorological Terminal Aviation Routine Weather Report) and forecast weather conditions from Localized Aviation MOS Program (LAMP). Operational data from the Federal Aviation Administration (FAA) Aviation System Performance Metrics (ASPM) related to scheduled and actual number of arrivals and departures, average taxi times, etc. are collected. NASA’s Sherlock Data Warehouse is used to identify critical information such as go-arounds, and other events that might impact RCM decision-making. All data is collected and aggregated over 15-minute intervals throughout the two years. This provides a resolution like the timescales that might be necessary for runway configuration management decision-making. A variety of supervised learning algorithms are tested including Support Vector Machine, Random Forest, Gradient Boosting, etc. including tuning of the model hyperparameters. The modeling process is applied and presented on two representative U.S. airports – Charlotte Douglas International Airport (KCLT) and Denver International Airport (KDEN). The two airports present different levels of complexity in terms of the total number of configurations used and provide a balanced perspective on the generalizability of the developed approach to other airports in the NAS. Initial results are promising (F1 score of 0.91 at KCLT and 0.83 at KDEN) for data in the test set. The final paper will contain a comprehensive comparison between different models and model building strategies as well as further refined results. Most important predictors for each airport will be identified along with a discussion and recommendations on adapting the framework to other scenarios.

Tejas G Puranik↗