Results for “administration tool” — Page 6

NASA NTRS2018

Database Tool for Master Console Operators

The Spaceport Command and Control System (SCCS) is the National Aeronautics and Space Administration's (NASA) launch control system for the Orion capsule and Space Launch System, the next generation manned rocket currently in development. This large system requires highly trained and knowledgeable personnel. Master Console Operators (MCO) are currently working on familiarizing themselves with any possible scenario that they may encounter. An intern was recruited to help assist them with creating a tool to use for the process.

Ferrell, Sean↗

NASA NTRSDate not supplied

Developing Geology Sampling Tools for the Artemis Program

Humans are set to return to the Moon for the first time since 1972 with the National Aeronautics and Space Administration’s (NASA) Artemis Program. One of the primary objectives will be the collection and return of lunar samples. To support this objective, the Extravehicular Activity (EVA) Tools Team at the Johnson Space Center (JSC) has started developing the next generation of lunar geology sampling tools. The EVA Tools Team are experts in the hardware certification process for space hardware and have been working on planetary surface tools for nearly a decade. Funded by the EVA Office at JSC, the Artemis tools project began on October 1, 2019 with an initial set of eight tools. That initial set of tools was brought to a Preliminary Design Review (PDR) on October 30, 2020. An additional 17tools have been proposed to support geology sampling operations, with the development of a subset of that list beginning on October 1, 2020.Additional tools may also be considered in the future should the science requirements drive this need. This abstract describes how this project is defining requirements, what tools are being developed, and the schedule for this work.

Artemis↗

NASA NTRS1985

Concepts and Tools for the Software Life Cycle

The tools, techniques, and aids needed to engineer, manage, and administer a large software-intensive task are themselves parts of a large softwaare base, and are incurred only at great expense. The needs of the software life cycle in terms of such supporting tools and methodologies are highlighted. The concept of a distributed network for engineering, management, and administrative functions is outlined, and the key characteristics of localized subnets in high-communications-traffic areas of software activity are discussed. A formal, deliberate, structured, systems-engineering approach for the construction of a uniform, coordinated tool set is proposed as a means to reduce development and maintenance costs, foster adaptability, enhance reliability, and promote standardization.

Tausworthe, R. C.↗

NASA NTRS1985

Concepts and tools for the software life cycle

The tools, techniques, and aids needed to engineer, manage, and administer a large software-intensive task are themselves parts of a large software base, and are incurred only at great expense. The needs of the software life cycle in terms of such supporting tools and methodologies are highlighted. The concept of a distributed network for engineering, management, and administrative functions is outlined, and the key characteristics of localized subnets in high-communications-traffic areas of software actively are discussed. A formal, deliberate, structured, systems-engineering approach for the construction of a uniform, coordinated tool set is proposed as a means to reduce development and maintenance costs, foster adaptability, enhance reliability, and promote standardization.

Tausworthe, R. C.↗

NASA NTRS2018

Hybridized Agile Software Development of Flight Control Team Tools for International Space Station's Payload Operations Integration Center

Ground systems operations at the National Aeronautics and Space Administration's (NASA) Payload Operations and Integration Function (POIF) is increasing, via the High Operations Tempo (HOT) initiative, its ability to support more science activities with a fourth crew member on the International Space Station (ISS). The Flight Control Team's need to support this increased crew presence mandated the need for a series of software tools to better handle the increasing pace of payload science operations. The overall need was clear from the outset, but the full scope and user experience for each tool, were not as well understood, so establishing a fixed set of initial requirements was not feasible. An Agile Software Development (ASD) paradigm takes advantage of uncertainty, and plans for it, so it was deemed the most appropriate approach to create room for exploring novel concepts, and to mount a rapid and flexible response to inevitiably changing requirements. It facilitated the need for unprecedented collaboration between the Product Team (i.e. users from the Flight Control Team) and the Development Team (i.e. POIC systems engineers, developers, testers). This is a process shift in the development, test, and release of software from one that is prescriptive to one that is adaptive, which is necessary for these tools to have longevity. The application of ASD to the product development lifecycle permitted the timely incorporation of customer feedback, and, allowed for continuous quality improvements. This resulted in a suite of tools that are efficient, user-friendly, and enable POIF ground systems to support the increasing pace of payload science operations. ASD is not as much a set of prescriptive processes as it is a shift in mindset; one that moves from planning against change, to planning for change, thereby iteratively growing software towards user-defined value.

Albers, Cerese M.↗

NASA NTRS2011

Reduced Uncertainties in the Flutter Analysis of the Aerostructures Test Wing

Tuning the finite element model using measured data to minimize the model uncertainties is a challenging task in the area of structural dynamics. A test validated finite element model can provide a reliable flutter analysis to define the flutter placard speed to which the aircraft can be flown prior to flight flutter testing. Minimizing the difference between numerical and experimental results is a type of optimization problem. Through the use of the National Aeronautics and Space Administration Dryden Flight Research Center's (Edwards, California) multidisciplinary design, analysis, and optimization tool to optimize the objective function and constraints; the mass properties, the natural frequencies, and the mode shapes are matched to the target data, and the mass matrix orthogonality is retained. The approach in this study has been applied to minimize the model uncertainties for the structural dynamic model of the aerostructures test wing, which was designed, built, and tested at the National Aeronautics and Space Administration Dryden Flight Research Center. A 25 percent change in flutter speed has been shown after reducing the uncertainties.

Pak, Chan-Gi↗

NASA NTRS1976

MCC/shuttle test plan. Volume 1: Philosophy and guidelines

The Mission Control Center/Shuttle Test Plan is defined from development through operations to a level of detail which will support the National Aeronautics and Space Administration and contractor management in the following areas: test management, test tool development, and resource and schedule planning.

Source record↗

NASA NTRS1985

Advanced research and technology programs for advanced high-pressure oxygen-hydrogen rocket propulsion

A research and technology program for advanced high pressure, oxygen-hydrogen rocket propulsion technology is presently being pursued by the National Aeronautics and Space Administration (NASA) to establish the basic discipline technologies, develop the analytical tools, and establish the data base necessary for an orderly evolution of the staged combustion reusable rocket engine. The need for the program is based on the premise that the USA will depend on the Shuttle and its derivative versions as its principal Earth-to-orbit transportation system for the next 20 to 30 yr. The program is focused in three principal areas of enhancement: (1) life extension, (2) performance, and (3) operations and diagnosis. Within the technological disciplines the efforts include: rotordynamics, structural dynamics, fluid and gas dynamics, materials fatigue/fracture/life, turbomachinery fluid mechanics, ignition/combustion processes, manufacturing/producibility/nondestructive evaluation methods and materials development/evaluation. An overview of the Advanced High Pressure Oxygen-Hydrogen Rocket Propulsion Technology Program Structure and Working Groups objectives are presented with highlights of several significant achievements.

Marsik, S. J.↗

NASA NTRS1985

Advanced research and technology program for advanced high pressure oxygen-hydrogen rocket propulsion

A research and technology program for advanced high pressure, oxygen-hydrogen rocket propulsion technology is presently being pursued by the National Aeronautics and Space Administration (NASA) to establish the basic discipline technologies, develop the analytical tools, and establish the data base necessary for an orderly evolution of the staged combustion reusable rocket engine. The need for the program is based on the premise that the USA will depend on the Shuttle and its derivative versions as its principal Earth-to-orbit transportation system for the next 20 to 30 yr. The program is focused in three principal areas of enhancement: (1) life extension, (2) performance, and (3) operations and diagnosis. Within the technological disciplines the efforts include: rotordynamics, structural dynamics, fluid and gas dynamics, materials fatigue/fracture/life, turbomachinery fluid mechanics, ignition/combustion processes, manufacturing/producibility/nondestructive evaluation methods and materials development/evaluation. An overview of the Advanced High Pressure Oxygen-Hydrogen Rocket Propulsion Technology Program Structure and Working Groups objectives are presented with highlights of several significant achievements.

Marsik, S. J.↗

NASA NTRS2004

Advanced Technology Lifecycle Analysis System (ATLAS)

Developing credible mass and cost estimates for space exploration and development architectures require multidisciplinary analysis based on physics calculations, and parametric estimates derived from historical systems. Within the National Aeronautics and Space Administration (NASA), concurrent engineering environment (CEE) activities integrate discipline oriented analysis tools through a computer network and accumulate the results of a multidisciplinary analysis team via a centralized database or spreadsheet Each minute of a design and analysis study within a concurrent engineering environment is expensive due the size of the team and supporting equipment The Advanced Technology Lifecycle Analysis System (ATLAS) reduces the cost of architecture analysis by capturing the knowledge of discipline experts into system oriented spreadsheet models. A framework with a user interface presents a library of system models to an architecture analyst. The analyst selects models of launchers, in-space transportation systems, and excursion vehicles, as well as space and surface infrastructure such as propellant depots, habitats, and solar power satellites. After assembling the architecture from the selected models, the analyst can create a campaign comprised of missions spanning several years. The ATLAS controller passes analyst specified parameters to the models and data among the models. An integrator workbook calls a history based parametric analysis cost model to determine the costs. Also, the integrator estimates the flight rates, launched masses, and architecture benefits over the years of the campaign. An accumulator workbook presents the analytical results in a series of bar graphs. In no way does ATLAS compete with a CEE; instead, ATLAS complements a CEE by ensuring that the time of the experts is well spent Using ATLAS, an architecture analyst can perform technology sensitivity analysis, study many scenarios, and see the impact of design decisions. When the analyst is satisfied with the system configurations, technology portfolios, and deployment strategies, he or she can present the concepts to a team, which will conduct a detailed, discipline-oriented analysis within a CEE. An analog to this approach is the music industry where a songwriter creates the lyrics and music before entering a recording studio.

O'Neil, Daniel A.↗

NASA NTRS2016

Commercial Application of In-Space Assembly

In-Space assembly (ISA) expands the opportunities for cost effective emplacement of systems in space. Currently, spacecraft are launched into space and deploy into their operational configuration through a carefully choreographed sequence of operations. The deployment operation dictates the arrangement of the primary systems on the spacecraft, limiting the ability to take full advantage of launch vehicles volume and mass capability. ISA enables vastly different spacecraft architectures and emplacement scenarios to be achieved, including optimal launch configurations ranging from single launch and assembly to on-orbit aggregation of multiple launches at different orbital locations and times. The spacecraft can be visited at different orbital locations and times to effect expansion and maintenance of an operational capability. To date, the primary application of ISA has been in large programs funded by government organizations, such as the International Space Station. Recently, Space Systems Loral (SSL) led a study funded by the Defense Advanced Research Projects Agency (DARPA), called Dragonfly, to investigate the commercial applicability and economic advantages of ISA. In the study, it was shown that ISA enables SSL to double the capability of a commercial satellite system by taking advantage of alternate packaging approaches for the reflectors. The study included an ultra-light-weight robotic system, derived from Mars manipulator designs, to complete assembly of portions of the antenna system using a tool derived from DARPA orbital express and National Aeronautics and Space Administration (NASA) automated structural assembly experience. The mechanical connector that enables robotic ISA takes advantage of decades of development by NASA from the 1970's to 1980's during the Space Station Freedom program, the precursor to the ISS. The mechanical connector was originally designed for rapid astronaut assembly while also providing a high quality structural connection with linear load deflection response. The paper will discuss the business case for ISA, the general approach taken to exploit on-orbit assembly in the GEO communication satellite market, and the concept of operations associated with the ISA approach, thus laying the foundation for ISA to become an accepted operational approach for commercial in-space operations.

Lymer, John↗

NASA NTRS2018

Hybridized Agile Software Development of Flight Control Team Tools for International Space Station's Payload Operations Integration Center

Ground systems operations at the National Aeronautics and Space Administration's (NASA) Payload Operations and Integration Center (POIC) at Marshall Space Flight Center (MSFC) recently increased via a High Operations Tempo (HOT) initiative, in order to support more science activities with a fourth crew member on the International Space Station (ISS). The Flight Control Team's (FCT) need to support this increasing pace of payload science operations was the impetus for creating a series of new tools. While their need was clear, the full scope and user experience for each tool was not as well-understood, thus establishing a fixed set of initial requirements was not feasible. A hybridized Agile Software Development (ASD) paradigm was created to take advantage of this uncertainty, plan for it, permit the exploration of novel concepts, and also facilitate a rapid and flexible response to inevitably changing requirements. The POIC's hybridized ASD approach places preeminent focus on providing customer value through the delivery of high quality, customer-focused solutions in short timeframes. This has been successfully achieved through creating unprecedented modes of cooperation and collaboration between operations and software development teams, frequent user evaluations of the software with well-defined feedback mechanisms, increased human factors involvement, and a dedication to successful outcomes by the whole of the POIC. Since space science operations and software development are not typically so closely linked, this paper discusses an approach that offers an optimal way to provide an increased return on investment and a faster time-to-completion than traditional software development paradigms, while aiming at delivering high quality products and customer-driven value.

Albers, Cerese M.↗

NASA NTRS2004

Mobile Autonomous Humanoid Assistant

A mobile autonomous humanoid robot is assisting human co-workers at the Johnson Space Center with tool handling tasks. This robot combines the upper body of the National Aeronautics and Space Administration (NASA)/Defense Advanced Research Projects Agency (DARPA) Robonaut system with a Segway(TradeMark) Robotic Mobility Platform yielding a dexterous, maneuverable humanoid perfect for aiding human co-workers in a range of environments. This system uses stereo vision to locate human team mates and tools and a navigation system that uses laser range and vision data to follow humans while avoiding obstacles. Tactile sensors provide information to grasping algorithms for efficient tool exchanges. The autonomous architecture utilizes these pre-programmed skills to form human assistant behaviors. The initial behavior demonstrates a robust capability to assist a human by acquiring a tool from a remotely located individual and then following the human in a cluttered environment with the tool for future use.

Diftler, M. A.↗

NASA NTRS2019

Simulating Fleet Noise for Notional UAM Vehicles and Operations in New York

This paper presents the results of systems-level simulations using Metrosim that were conducted for notional Urban Air Mobility (UAM)-style vehicles analyzed for two different scenarios for New York (NY). UAM is an aviation industry term for passenger or cargo-carrying air transportation services, which are often automated, operating in an urban/city environment. UAM-style vehicles are expected to use vertical takeoff and landing with fixed wing cruise flight. Metrosim is a metroplex-wide route and airport planning tool that can also be used in standalone mode as a simulation tool. The scenarios described and reported in this paper were used to evaluate a fleet noise prediction capability for this tool. The work was a collaborative effort between the National Aeronautics and Space Administration (NASA), Intelligent Automation, Inc (IAI), and the Port Authority of New York and New Jersey (PANYNJ). One scenario was designed to represent an expanded air-taxi operation from existing helipads around Manhattan to the major New York airports. The other case represented a farther term vision case with commuters using personal air vehicles to hub locations just outside New York, with an air-taxi service running frequent connector trips to a few key locations inside Manhattan. For both scenarios, the trajectories created for the entire fleet were passed to the Aircraft Environmental Design Tool (AEDT) to generate Day-Night Level (DNL) noise contours for inspection. Without data for actual UAM vehicles available, surrogate AEDT empirical Noise-Power-Distance (NPD) tables used a similar sized current day helicopter as the Baseline, and a version of that same data linearly scaled as a first guess at possible UAM noise data. Details are provided for each of the two scenario configurations, and the output noise contours are presented for the Baseline and reduced noise DNL cases.

Glaab, Patricia↗

NASA NTRS2010

Reduced Uncertainties in the Flutter Analysis of the Aerostructures Test Wing

Tuning the finite element model using measured data to minimize the model uncertainties is a challenging task in the area of structural dynamics. A test validated finite element model can provide a reliable flutter analysis to define the flutter placard speed to which the aircraft can be flown prior to flight flutter testing. Minimizing the difference between numerical and experimental results is a type of optimization problem. Through the use of the National Aeronautics and Space Administration Dryden Flight Research Center s (Edwards, California, USA) multidisciplinary design, analysis, and optimization tool to optimize the objective function and constraints; the mass properties, the natural frequencies, and the mode shapes are matched to the target data and the mass matrix orthogonality is retained. The approach in this study has been applied to minimize the model uncertainties for the structural dynamic model of the aerostructures test wing, which was designed, built, and tested at the National Aeronautics and Space Administration Dryden Flight Research Center. A 25-percent change in flutter speed has been shown after reducing the uncertainties

Pak, Chan-gi↗

NASA NTRS2017

Predicting the Operational Acceptability of Route Advisories

NASA envisions a future Air Traffic Management system that allows safe, efficient growth in global operations, enabled by increasing levels of automation and autonomy. In a safety-critical system, the introduction of increasing automation and autonomy has to be done in stages, making human-system integrated concepts critical in the foreseeable future. One example where this is relevant is for tools that generate more efficient flight routings or reroute advisories. If these routes are not operationally acceptable, they will be rejected by human operators, and the associated benefits will not be realized. Operational acceptance is therefore required to enable the increased efficiency and reduced workload benefits associated with these tools. In this paper, the authors develop a predictor of operational acceptability for reroute advisories. Such a capability has applications in tools that identify more efficient routings around weather and congestion and that better meet airline preferences. The capability is based on applying data mining techniques to flight plan amendment data reported by the Federal Aviation Administration and data on requested reroutes collected from a field trial of the NASA developed Dynamic Weather Routes tool, which advised efficient route changes to American Airlines dispatchers in 2014. 10-Fold cross validation was used for feature, model and parameter selection, while nested cross validation was used to validate the model. The model performed well in predicting controller acceptance or rejection of a route change as indicated by chosen performance metrics. Features identified as relevant to controller acceptance included the historical usage of the advised route, the location of the maneuver start point relative to the boundaries of the airspace sector containing the maneuver start (the maneuver start sector), the reroute deviation from the original flight plan, and the demand level in the maneuver start sector. A random forest with forty trees was the best performing of the five models evaluated in this paper.

route advisories↗

NASA NTRS2017

Predicting the Operational Acceptability of Route Advisories

NASA envisions a future Air Traffic Management system that allows safe, efficient growth in global operations, enabled by increasing levels of automation and autonomy. In a safety-critical system, the introduction of increasing automation and autonomy has to be done in stages, making human-system integrated concepts critical in the foreseeable future. One example where this is relevant is for tools that generate more efficient flight routings or reroute advisories. If these routes are not operationally acceptable, they will be rejected by human operators, and the associated benefits will not be realized. Operational acceptance is therefore required to enable the increased efficiency and reduced workload benefits associated with these tools. In this paper, the authors develop a predictor of operational acceptability for reroute advisories. Such a capability has applications in tools that identify more efficient routings around weather and congestion and that better meet airline preferences. The capability is based on applying data mining techniques to flight plan amendment data reported by the Federal Aviation Administration and data on requested reroutes collected from a field trial of the NASA developed Dynamic Weather Routes tool, which advised efficient route changes to American Airlines dispatchers in 2014. 10-Fold cross validation was used for feature, model and parameter selection, while nested cross validation was used to validate the model. The model performed well in predicting controller acceptance or rejection of a route change as indicated by chosen performance metrics. Features identified as relevant to controller acceptance included the historical usage of the advised route, the location of the maneuver start point relative to the boundaries of the airspace sector containing the maneuver start (the maneuver start sector), the reroute deviation from the original flight plan, and the demand level in the maneuver start sector. A random forest with forty trees was the best performing of the five models evaluated in this paper.

operational acceptability↗

NASA NTRS1986

Transportability, distributability and rehosting experience with a kernel operating system interface set

For the past two years, PRC has been transporting and installing a software engineering environment framework, the Automated Product control Environment (APCE), at a number of PRC and government sites on a variety of different hardware. The APCE was designed using a layered architecture which is based on a standardized set of interfaces to host system services. This interface set called the APCE Interface Set (AIS), was designed to support many of the same goals as the Common Ada Programming Support Environment (APSE) Interface Set (CAIS). The APCE was developed to provide support for the full software lifecycle. Specific requirements of the APCE design included: automation of labor intensive administrative and logistical tasks: freedom for project team members to use existing tools: maximum transportability for APCE programs, interoperability of APCE database data, and distributability of both processes and data: and maximum performance on a wide variety of operating systems. A brief description is given of the APCE and AIS, a comparison of the AIS and CAIS both in terms of functionality and of philosophy and approach and a presentation of PRC's experience in rehosting AIS and transporting APCE programs and project data. Conclusions are drawn from this experience with respect to both the CAIS efforts and Space Station plans.

Blumberg, F. C.↗