SEARCH · Engineering Papers

Results for “key management”

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.

SourceResearch connectionFrom yearThrough year

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

At least 343 records · Page 19

All sources NASA NTRS DOE OSTI

NASA NTRS2001

Achieving QoS for TCP Traffic in Satellite Networks with Differentiated Services

Satellite networks play an indispensable role in providing global Internet access and electronic connectivity. To achieve such a global communications, provisioning of quality of service (QoS) within the advanced satellite systems is the main requirement. One of the key mechanisms of implementing the quality of service is traffic management. Traffic management becomes a crucial factor in the case of satellite network because of the limited availability of their resources. Currently, Internet Protocol (IP) only has minimal traffic management capabilities and provides best effort services. In this paper, we presented a broadband satellite network QoS model and simulated performance results. In particular, we discussed the TCP flow aggregates performance for their good behavior in the presence of competing UDP flow aggregates in the same assured forwarding. We identified several factors that affect the performance in the mixed environments and quantified their effects using a full factorial design of experiment methodology.

Durresi, Arjan↗

NASA NTRS2011

Nanosail-D: The Small Satellite That Could!

Three years from its initial design review, NanoSail-D successfully deployed its sail on January 20th, 2011. It became the first solar sail vehicle to orbit the earth and the second sail ever unfurled in space. The NanoSail-D mission had two main objectives: eject a nanosatellite from a microsatellite; deploy its sail from a highly compacted volume and low mass system to validate large structure deployment and potential de-orbit technologies. These objectives were successfully achieved and the de-orbit analysis is in process. This paper presents an overview of the NanoSail-D project and insights into how potential setbacks were overcome. Many lessons have been learned during these past three years and are discussed in light of the phenomenal success and interest that this small satellite has generated. NanoSail-D was jointly designed and built by NASA's Marshall Space Flight Center and NASA's Ames Research Center. ManTech/NeXolve Corporation also provided key sail design support. The NanoSail-D experiment is managed by Marshall and jointly sponsored by the Army Space and Missile Defense Command, the Von Braun Center for Science and Innovation and Dynetics Inc. Ground operations support was provided by Santa Clara University, with radio beacon packets received from amateur operators around the world.

Alhorn, Dean C.↗

NASA NTRSDate not supplied

Enabling Exchange and Adequate Use of Data for Observation Based Atmospheric Research

Systematic long-term field observations have played a vital role in advancing atmospheric research over the past several decades. The use of these observations has expanded from primarily characterizing atmospheric processes and trends to evaluating satellite measurements, assessing models, and improving air quality forecasts. Consequently, the demand for atmospheric chemistry observational data have dramatically increased in terms of scope and coverage of measurements (i.e., parameters/species, spatiotemporal extent). In addition to high quality measurements, certain data reporting standards need to be agreed to ensure the data can be readily exchanged and are sufficiently documented to enable adequate use in different research activities. To this end, WMO has developed and implemented measurement guidelines and community practices for meteorology, climatology, atmospheric and hydrological sciences. In addition, the WMO Expert Team on Metadata Standards manages and evolves the existing metadata standards for the WMO Information System WIS and WMO Integrated Global Observing System WIGOS to support consistent and interoperable data descriptions, ensure relevance to research, and to apply data science principles. This team draws on a wide range of expertise from the research community, including atmospheric measurements, modeling, data management, and data science. The current activities include development of key performance indicators, vocabularies for metadata and the evolution of metadata standards to lower the barrier of application to weather/climate/water/environment data for all communities and the weather enterprise. This presentation intends to promote awareness of ongoing progress and actively solicit community feedback.

Field Observations↗

NASA NTRS2021

Application of Micro-thrusters for Space Observatory Precision Attitude Control

This paper describes the results of a NASA investigation into the benefits of micro-thrusters compared to reaction wheels on future observatory-class missions with tight pointing stability requirements. Pointing repeatability and stability (i.e., jitter) requirements are key for space telescope missions of the future. For example, managing jitter is essential to being able to “image” planets orbiting distant stars. Jitter requirements for missions in this class are difficult to meet with current reaction wheel-based architectures. The reaction wheels are typically the largest pointing disturbance on the spacecraft. Disturbances from reaction wheels can be mitigated, typically by mechanically isolating the wheels, which imposes system complexity and cost. Thrusters capable of thrust forces in the micronewton (μN) range (referred to as micro-thrusters or micronewton thrusters) have been developed to support the Laser Interferometer Space Antenna (LISA) mission, which requires drag-free control to place a test mass in near-perfect free-fall Beyond the drag-free control application, micro-thrusters could be used as a substitute for reaction wheels or as a supplement to wheels for fine pointing control. Used in this fashion, micro-thrusters have potential for reducing the cost and technical risks of achieving demanding pointing stability performance on observatory-class missions.

Chiang, Richard Y.↗

NASA NTRS2008

Reducing NPR 7120.5D to Practice: Preparing for a Life-Cycle Review

In March 2007, NASA issued revised rules for space flight project management, NPR 7120.5D, 'NASA Space Flight Program and Project Management Requirements.' Central to the new rules was the construct of Key Decision Points, maturity gates that the project team must pass in order to continue development. In order that the KDP decision be fully informed, the NPR required, as entrance criteria for the gate, the generation and delivery of specified planning, technical, and cost/schedule documents (gate products) and a life-cycle review, the Preliminary Design Review. Building on JPL experience on the Prometheus and Juno projects, the team successfully organized for and conducted these reviews on an aggressive schedule. Key actions were taken to proactively interact with the SRB, produce high-quality gate products with stakeholder review, generate review presentation materials, and handle a myriad of supporting logistical functions. A review preparation team was established, including a Review Captain and leads for documentation, information systems, and logistics, and their roles, responsibilities and task assignments were identified. Aids were produced, including a detailed review preparation schedule and a comprehensive gate products production table. Institutional support was leveraged early and often. Implementation strategy reflected the needs of a nationally-distributed team, as well as applicable export control and IT security requirements. This paper gives a brief overview of the GRAIL mission and its project management challenges, provides a detailed description of project PMSR and PDR preparation and execution activities, including positive and negative lessons learned, and identifies recommendations for future NASA (and non-NASA) project teams.

NPR 7120.5D↗

NASA NTRS1976

Data management in pattern recognition and image processing systems

Data management considerations are important to any system which handles large volumes of data or where the manipulation of data is technically sophisticated. A particular problem is the introduction of image-formatted files into the mainstream of data processing application. This report describes a comprehensive system for the manipulation of image, tabular, and graphical data sets which involve conversions between the various data types. A key characteristic is the use of image processing technology to accomplish data management tasks. Because of this, the term 'image-based information system' has been adopted.

Zobrist, A. L.↗

NASA NTRS2011

Engineering the System and Technical Integration

Approximately 80% of the problems encountered in aerospace systems have been due to a breakdown in technical integration and/or systems engineering. One of the major challenges we face in designing, building, and operating space systems is: how is adequate integration achieved for the systems various functions, parts, and infrastructure? This Contractor Report (CR) deals with part of the problem of how we engineer the total system in order to achieve the best balanced design. We will discuss a key aspect of this question - the principle of Technical Integration and its components, along with management and decision making. The CR will first provide an introduction with a discussion of the Challenges in Space System Design and meeting the challenges. Next is an overview of Engineering the System including Technical Integration. Engineering the System is expanded to include key aspects of the Design Process, Lifecycle Considerations, etc. The basic information and figures used in this CR were presented in a NASA training program for Program and Project Managers Development (PPMD) in classes at Georgia Tech and at Marshall Space Flight Center (MSFC). Many of the principles and illustrations are extracted from the courses we teach for MSFC.

Blair, J. C.↗

NASA NTRS1989

An intelligent user interface for browsing satellite data catalogs

A large scale domain-independent spatial data management expert system that serves as a front-end to databases containing spatial data is described. This system is unique for two reasons. First, it uses spatial search techniques to generate a list of all the primary keys that fall within a user's spatial constraints prior to invoking the database management system, thus substantially decreasing the amount of time required to answer a user's query. Second, a domain-independent query expert system uses a domain-specific rule base to preprocess the user's English query, effectively mapping a broad class of queries into a smaller subset that can be handled by a commercial natural language processing system. The methods used by the spatial search module and the query expert system are explained, and the system architecture for the spatial data management expert system is described. The system is applied to data from the International Ultraviolet Explorer (IUE) satellite, and results are given.

Cromp, Robert F.↗

NASA NTRS1989

An intelligent user interface for browsing satellite data catalogs

Cromp, Robert F.↗

NASA NTRS2004

The NASA Continuous Risk Management Process

As an intern this summer in the GRC Risk Management Office, I have become familiar with the NASA Continuous Risk Management Process. In this process, risk is considered in terms of the probability that an undesired event will occur and the impact of the event, should it occur (ref., NASA-NPG: 7120.5). Risk management belongs in every part of every project and should be ongoing from start to finish. Another key point is that a risk is not a problem until it has happened. With that in mind, there is a six step cycle for continuous risk management that prevents risks from becoming problems. The steps are: identify, analyze, plan, track, control, and communicate & document. Incorporated in the first step are several methods to identify risks such as brainstorming and using lessons learned. Once a risk is identified, a risk statement is made on a risk information sheet consisting of a single condition and one or more consequences. There can also be a context section where the risk is explained in more detail. Additionally there are three main goals of analyzing a risk, which are evaluate, classify, and prioritize. Here is where a value is given to the attributes of a risk &e., probability, impact, and timeframe) based on a multi-level classification system (e.g., low, medium, high). It is important to keep in mind that the definitions of these levels are probably different for each project. Furthermore the risks can be combined into groups. Then, the risks are prioritized to see what risk is necessary to mitigate first. After the risks are analyzed, a plan is made to mitigate as many risks as feasible. Each risk should be assigned to someone in the project with knowledge in the area of the risk. Then the possible approaches to choose from are: research, accept, watch, or mitigate. Next, all risks, mitigated or not, are tracked either individually or in groups. As the plan is executed, risks are re-evaluated, and the attribute values are adjusted as necessary. Metrics are established and monitored as tools for risk tracking. Also a trigger or threshold should be set on the metric data that indicates when an action is needed. Results of this tracking are usually evaluated and reported in a relevant format at weekly or monthly meetings. Choosing controls is the subsequent step, which involves the effects of the tracking. The three basic controls are: close, continue tracking, and re- plan. Finally communicate & document is the last step, but occurs throughout the process. It is vital that main risks, plans, changes, and progress are known by everyone in the project. A good way to keep everyone updated and inform other projects of common issues is by thoroughly documenting project risks. NASA sees value in risk management and believes that projects have greater probability or success by using the NASA Continuous Risk Management Process.

Pokorny, Frank M.↗

NASA NTRS2024

Workshop on the Role of Design Assurance in System-Wide Safety’s Safety Demonstrator Series

This report summarizes a three-hour hybrid in-person/online workshop on June 7, 2024 on the topic of design assurance and the Safety Demonstrator Series (SDS), which was held at NASA Ames Research Center. The SDS provides an operational demonstration of, and recommendations for, requirements and standards necessary to monitor, assess, and mitigate risks to assure safety in disaster-oriented operations. Over sixty NASA personnel participated in the workshop. Four main topics were discussed: (1) assurance needs for the Safety Demonstrator Series, (2) assurance and the In-Time Aviation Safety Management System (IASMS), (3) in-time assurance: existing efforts and future opportunities, and (4) demonstrating assurance tools in the Safety Demonstrators. Key takeaways are as follows: 1. Design assurance tools can be used to assure an In-Time Aviation Safety Management System, the systems that comprise it, and other systems or missions. Assurance must consider both systems and components and include the interactions between elements in both a systems/aircraft context and a systems-of-systems/airspace context. 2. Design-time assurance activities can support the identification of monitors needed for operational assurance activities (i.e., the “monitor” function in the monitor-assess-mitigate paradigm at the heart of the IASMS concept). 3. A major opportunity for design-time assurance tools to contribute to the IASMS concept is to support rapid re-validation of systems. This will be particularly important for (1) supporting novel operations in the IASMS, where operational data may disprove design-time assumptions (motivating re-analysis of system safety) and (2) adapting technologies (e.g., AI/ML for autonomous operations) to new operational domains, where there may be new or different safety considerations not included in the initial scope of operations. 4. There are several design assurance tools under development in the System-Wide Safety project that can support assurance of Services, Functions, and Capabilities (SFCs) in the Safety Demonstrators. Transitioning these tools from one-off research projects into a functioning part of IASMS assurance will require closer integration between these tools. 5. It is not clear whether the role of design assurance tools is primarily as a part of IASMS architecture or as an external check on IASMS. The workshop consisted of four discussion topics initiated via four lightning talks by System-Wide Safety researchers. Discussions utilized Mural to engage both in-person and online participants in the hybrid format. Polls and surveys were also utilized to gather participant input. The workshop closed with a reflection activity for participants, as well as new ideas for collaboration and coordination of ongoing System-Wide Safety research.

design assurance↗

NASA NTRS2008

The Project Manager Who Saved His Country

George Meade defeated Robert E. Lee, one of the greatest military leaders of all time. How did he do it? By using the skills he had learned as a project manager and outperforming Lee in all aspects of project management. Most project managers are familiar with the Project Management Institute's "Guide to the Project Management Body of Knowledge" (PMBOK), which identifies the skills and knowledge crucial to successful project management. Project managers need to make sure that all the elements of a project work together. They must develop and execute plans and coordinate changes to those plans. A project manager must define the scope of the work, break it into manageable pieces, verify and control what work is being done, and make sure that the work being done is essential to the project. Every project manager knows the challenges of schedule and the value of schedule slack. Project managers must get the resources they need and use them effectively. Project managers get the people they need and use their talents to achieve mission success. Projects generate huge amounts of information. A key to project success is getting sufficient and accurate information to the people who need it when they need it. Project managers must identify and quantify the risks that jeopardize project success and make plans for dealing with them. Studying Meade and Lee's performances at Gettysburg can help modern project managers appreciate, develop, and use the skills they need to be good project managers. The circumstances may be different, but the basic principles are the same. This dramatic event in American history shows how the skills of project management can be used in almost any situation. Former project manager George Meade used those skills to change the tide of the Civil War.

Baniszewski, John↗

NASA NTRS2018

Technologies and Methods Used at the Laboratory for Atmospheric and Space Physics (LASP) to Serve Solar Irradiance Data

The Laboratory for Atmospheric and Space Physics (LASP) at the University of Colorado in Boulder, USA operates the Solar Radiation and Climate Experiment (SORCE) NASA mission, as well as several other NASA spacecraft and instruments. Dozens of Solar Irradiance data sets are produced, managed, and disseminated to the science community. Data are made freely available to the scientific immediately after they are produced using a variety of data access interfaces, including the LASP Interactive Solar Irradiance Datacenter (LISIRD), which provides centralized access to a variety of solar irradiance data sets using both interactive and scriptable/programmatic methods. This poster highlights the key technological elements used for the NASA SORCE mission ground system to produce, manage, and disseminate data to the scientific community and facilitate long-term data stewardship. The poster presentation will convey designs, technological elements, practices and procedures, and software management processes used for SORCE and their relationship to data quality and data management standards, interoperability, NASA data policy, and community expectations.

Pankratz, Chris↗

NASA NTRS1998

Power Management and Distribution System Developed for Thermionic Power Converters

A spacecraft solar, bimodal system combines propulsion and power generation into a single integrated system. An Integrated Solar Upper Stage (ISUS) provides orbital transfer capabilities, power generation for payloads, and onboard propulsion to the spacecraft. A key benefit of a bimodal system is a greater payload-to-spacecraft mass ratio resulting in lower launch vehicle requirements. Scaling down to smaller launch vehicles increases space access by reducing overall mission cost. NASA has joined efforts with the Air Force Phillips Laboratory to develop enabling technologies for such a system. The NASA/Air Force bimodal concept uses solar concentrators to focus energy into an integrated power plant. This power plant consists of a graphite core that stores thermal energy within a cavity. An array of thermionic converters encircles the graphite cavity and provides electrical energy conversion functions. During the power generation phase of the bimodal system, the thermionic converters are exposed to the heated cavity and convert the thermal energy to electricity. Near-term efforts of the ISUS bimodal program are focused on a ground demonstration of key technologies in order to proceed to a full space flight test. Thermionic power generation is one key technology of the bimodal concept. Thermionic power converters impose unique operating requirements upon a power management and distribution (PMAD) system design. Single thermionic converters supply large currents at very low voltages. Operating voltages can vary over a range of up to 3 to 1 as a function of operating temperature. Most spacecraft loads require regulated 28-volts direct-current (Vdc) power. A combination of series-connected converters and powerprocessing boosters is required to deliver power to the spacecraft's payloads at this level.

Baez, Anastacio N.↗

NASA NTRSDate not supplied

Exploring the Landscape of Earth and Space Science Informatics using Latent Topic Modeling

AGU Earth and Space Science Informatics (ESSI) is at the forefront of data management, analysis, large scale experimentation, and infrastructure development pertaining to Earth and Space Science interests. The key topics of interest within ESSI are also evolving and diversifying over time. We aim to observe and quantify the various topics covered in ESSI, analyze their trends over time, and identify the contributors’ affiliations to gain an understanding of the landscape of ESSI and the direction of the research and management. The data for this work are abstracts submitted to AGU’s ESSI Fall meeting; They serve as a proxy for key research and development areas within ESSI. We use an unsupervised topic modeling technique called Latent Dirichlet Allocation to observe the underlying topics covered in ESSI and their trends over time. With this presentation, we showcase our results from the analysis and insights gained.

Muthukumaran Ramasubramanian↗

NASA NTRS2017

Management by Trajectory Trade Study of Roles and Responsibilities Between Participants and Automation Report

This report describes a trade study of roles and responsibilities associated with the Management by Trajectory (MBT) concept. The MBT concept describes roles, responsibilities, and information and automation requirements for providing air traffic controllers and managers the ability to quickly generate, evaluate and implement changes to an aircraft's trajectory. In addition, the MBT concept describes mechanisms for imposing constraints on flight operator preferred trajectories only to the extent necessary to maintain safe and efficient traffic flows, and the concept provides a method for the exchange of trajectory information between ground automation systems and the aircraft that allows for trajectory synchronization and trajectory negotiation. The participant roles considered in this trade study include: airline dispatcher, flight crew, radar controller, traffic manager, and Air Traffic Control System Command Center (ATCSCC) traffic management specialists. The proposed allocation of roles and responsibilities was based on analysis of several use cases that were developed for this purpose as well as for walking through concept elements. The resulting allocation of roles and responsibilities reflects both increased automation capability to support many aviation functions, as well as increased flexibility to assign responsibilities to different participants - in many cases afforded by the increased automation capabilities. Note that the selection of participants to consider for allocation of each function is necessarily rooted in the current environment, in that MBT is envisioned as an evolution of the National Airspace System (NAS), and not a revolution. A key feature of the MBT allocations is a vision for the traffic management specialist to take on a greater role. This is facilitated by the vision that separation management functions, in addition to traffic management functions, will be carried out as trajectory management functions. This creates an opportunity for flexibility, allowing the traffic management specialist to carry out tasks that today can only be carried out by the controller currently in contact with the aircraft. This additional tasking for the traffic management specialist comes with requirements for workload management. An increased role for the Data-side (D-side) controller relative to the Radar-side (R-side) controller is a potential approach to mitigating workload for the traffic management specialist, as the D-side controller would have similar ability to perform separation management functions in what today might be considered the "trajectory management" timeframe. This analysis did not distinguish between the D-side and R-side controllers since in many cases the R-side controller works unassisted.

Fernandes, Alicia D.↗

NASA NTRS1994

Process maturity progress at Motorola Cellular Systems Division

We believe that the key success elements are related to our recognition that Software Process Improvement (SPI) can and should be organized, planned, managed, and measured as if it were a project to develop a new process, analogous to a software product. We believe that our process improvements have come as the result of these key elements: use of a rigorous, detailed requirements set (Capability Maturity Model, CMM); use of a robust, yet flexible architecture (IEEE 1074); use of a SPI project, resourced and managed like other work, to produce the specifications and implement them; and development of both internal and external goals, with metrics to support them.

Borgstahl, Ron↗

NASA NTRS1998

X-33/RLV System Health Management/ Vehicle Health Management

To reduce operations cost, the RLV must include the following elements: highly reliable, robust subsystems designed for simple repair access with a simplified servicing infrastructure and incorporating expedited decision making about faults and anomalies. A key component for the Single Stage to Orbit (SSTO) RLV System used to meet these objectives is System Health Management (SHM). SHM deals with the vehicle component- Vehicle Health Management (VHM), the ground processing associated with the fleet (GVHM) and the Ground Infrastructure Health Management (GIHM). The objective is to provide an automated collection and paperless health decision, maintenance and logistics system. Many critical technologies are necessary to make the SHM (and more specifically VHM) practical, reliable and cost effective. Sanders is leading the design, development and integration of the SHM system for RLV and X-33 SHM (a sub-scale, sub-orbit Advanced Technology Demonstrator). This paper will present the X-33 SHM design which forms the baseline for RLV SHM. This paper will also discuss other applications of these technologies.

Garbos, Raymond J.↗