SEARCH · Search NASA

Results for “Vehicle assignment”

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 199 records · Page 11

All sources NASA NTRS DOE OSTI

NASA NTRS2006

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and Their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative a requirement to standardize and control the naming conventions of very disparate systems and technologies are emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation Initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation Initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and birds of a feather activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another

Bradford, Robert N.↗

NASA NTRS2006

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative, a requirement to standardize and control the naming conventions of very disparate systems and technologies is emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and Birds of a Feather (BoF) activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another standards body or technologies that are currently not standardized. For activities one through three, we will provide the analysis by either discipline or technology with rationale, identification and brief description of requirements and precedence. For activity four, we will provide a list of current standards bodies e.g. IETF and a list of potential candidates.

Bradford, Robert N.↗

NASA NTRS1999

Tracking the Relative Motion of Four Space Payloads Launched from a Sub-Orbital NASA Rocket

One problem, which is comparatively new in the field of GPS applications, is the determination of the relative trajectories of space vehicles. Applications include the docking of spacecraft, collision avoidance in the area of space stations, and trajectory reconstruction of multiple payloads. The required precision in any of these applications will vary, according to the requirements of the task and abilities of GPS to cope with the environment and the dynamics. This paper describes the post-mission reconstruction of the relative trajectories of four GPS receivers attached to four payloads jettisoned from a Black Brant XII rocket. This vehicle was launched by the National Aeronautics and Space Administration (NASA) in January 1999 from the Poker Flats Research Range near Fairbanks, Alaska. The Black Brant XII is a sub-orbital rocket designed to carry payloads of 100 to 500 kg into the upper atmosphere. Flight time is generally in the order of 10-20 minutes. In this experiment, a GPS receiver and antenna was attached to each of the four payloads. One of the GPS receivers was assigned as the "base station", while the other 3 receivers were designated as remotes. GPS time, code and phase measurements were telemetered to a ground station for real-time processing and storage. The object of the mission was to re-compute the position and velocity of the remote units with respect to the base station during the launch phase and after the payloads separated. During the launch segment the 3 baseling distances between the 4 antennas are known from plans and are constant values until each payload is released. On the fly ambiguity determination was used to establish local coordinates from the base antenna to each of the other 3 GPS units during flight. Distance computations were made from the GPS-derived coordinates and compared to plan distances. Using this methodology an error analysis of the relative GPS accuracies has been presented and in addition a description given of the respective payload behaviour following separation from the vehicle.

Martell, Hugh↗

NASA NTRS2020

Guidelines for Assessing the Toxic Hazard of Spacecraft Chemicals and Test Materials

This document describes the criteria and procedural guidelines used by the NASA/JSC Toxicology Office (JSCSTO), to perform toxicological evaluations. The JSCSTO is responsible for conducting toxicological assessments and assigning toxic hazard levels (THLs) for essentially all chemicals and test materials to be used in or transported to the habitable areas of U.S. spacecraft, non‐U.S. spacecraft inhabitaed by U.S. crew members or habitable areas of off‐Earth habitats where U.S. crew members would be present, including chemicals carried by visiting spacecraft(visiting vehicles) to and from the International Space Station (ISS). Biohazard assessments for biological materials used in payload experiments are performed by the NASA Biosafety Review Board. Radioactive materials are assessed by the Space Radiation Analysis Group for radiation hazards; the flammability rating on flammable materials is assessed by the JSC Materials and Processes Branch, ES4. This document will focus on the assessment of chemically‐induced toxicity hazards. The toxicological assessments, together with assessments on radioactive, biological, physical, and flammability hazards, are incorporated into a mission‐specific Hazardous Materials Summary Table (HMST).

Valerie Elizabeth Ryder↗

DOE OSTI2022

Providing curb availability information to delivery drivers reduces cruising for parking

Abstract Delivery vehicle drivers are experiencing increasing challenges in finding available curb space to park in urban areas, which increases instances of cruising for parking and parking in unauthorized spaces. Policies traditionally used to reduce cruising for parking for passenger vehicles, such as parking fees and congestion pricing, are not effective at changing delivery drivers’ travel and parking behaviors. Intelligent parking systems that use real-time curb availability information to better route and park vehicles can reduce cruising for parking, but they have never been tested for delivery vehicle drivers. The current study tested whether providing real-time curb availability information to delivery drivers reduces the travel time and distance spent cruising for parking. A curb parking information system deployed in a study area in Seattle, Wash., displayed real-time curb availabilities on a mobile app called OpenPark. A controlled experiment assigned drivers’ deliveries in the study area with and without access to OpenPark. The data collected showed that when curb availability information was provided to drivers, their cruising for parking time significantly decreased by 27.9 percent, and their cruising distance decreased by 12.4 percent. These results demonstrate the potential for implementing intelligent parking systems to improve the efficiency of urban logistics systems.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

NASA NTRS1988

An application of eigenspace methods to symmetric flutter suppression

An eigenspace assignment approach to the design of parameter insensitive control laws for linear multivariable systems is presented. The control design scheme utilizes flexibility in eigenvector assignments to reduce control system sensitivity to changes in system parameters. The methods involve use of the singular value decomposition to provide an exact description of allowable eigenvectors in terms of a minimum number of design parameters. In a design example, the methods are applied to the problem of symmetric flutter suppression in an aeroelastic vehicle. In this example the flutter mode is sensitive to changes in dynamic pressure and eigenspace methods are used to enhance the performance of a stabilizing minimum energy/linear quadratic regulator controller and associated observer. Results indicate that the methods provide feedback control laws that make stability of the nominal closed loop systems insensitive to changes in dynamic pressure.

Fennell, Robert E.↗

DOE OSTI2024

Collision avoidance based on traffic management data

A system for determining a travel direction that avoids objects when a vehicle travels from a current location to a target location is provided. The system determines a travel direction based on an attract-repel model. The system accesses external object information provided by an external object system. The external object information may include, for each of a plurality of objects, location, type, and constraint. The system assigns a repel value to the location of each object based on the type of and constraint on the object. The system assigns an attractive value to the target location. The system calculates a cumulative force based on the attractive and repulsive forces and sets the travel direction based on the cumulative force.

Beer, N. Reginald↗

NASA NTRS1992

Preliminary structural design of a lunar transfer vehicle aerobrake

An aerobrake concept for a Lunar transfer vehicle was weight optimized through the use of the Taguchi design method, structural finite element analyses and structural sizing routines. Six design parameters were chosen to represent the aerobrake structural configuration. The design parameters included honeycomb core thickness, diameter to depth ratio, shape, material, number of concentric ring frames, and number of radial frames. Each parameter was assigned three levels. The minimum weight aerobrake configuration resulting from the study was approx. half the weight of the average of all twenty seven experimental configurations. The parameters having the most significant impact on the aerobrake structural weight were identified.

Bush, Lance B.↗

NASA NTRS2009

Lunar Surface Operations: Surface Duration - Part 2

The objectives of this slide presentation are to review the activities on the lunar surface during the stay. The objectives include (1) Summarize Lunar Module Basics emphasizing module layout and storage. (2) Identify the primary activities occurring during each of the lunar s urface timelines, (3) List the EVA Prep tasks, (4) Identify the EVA Objectives, (5) Identify the activities associated with Post EVA (6) Describe the lessons learned during both EVA and Non EVA activities. Included are overview drawings of the Lunar Roving Vehicle, pictures of the tools, and sample return containers. There are also time lines for the Apollo 11, and Apollo 12 through 14, Apollo 15, Apollo 16 and Apollo 17. Diagrams of the EVA suits are shown, including the Liquid Cooling Garment, and the Pressure Garment Assembly. The activity prior to the EVA are reviewed. The science mission assignments of each mission are viewed. The activities after the EVA are reviewed

Interbartolo, Michael↗

NASA NTRS2014

NASA Space Launch System Operations Outlook

The National Aeronautics and Space Administration's (NASA) Space Launch System (SLS) Program, managed at the Marshall Space Flight Center (MSFC), is working with the Ground Systems Development and Operations (GSDO) Program, based at the Kennedy Space Center (KSC), to deliver a new safe, affordable, and sustainable capability for human and scientific exploration beyond Earth's orbit (BEO). Larger than the Saturn V Moon rocket, SLS will provide 10 percent more thrust at liftoff in its initial 70 metric ton (t) configuration and 20 percent more in its evolved 130-t configuration. The primary mission of the SLS rocket will be to launch astronauts to deep space destinations in the Orion Multi-Purpose Crew Vehicle (MPCV), also in development and managed by the Johnson Space Center. Several high-priority science missions also may benefit from the increased payload volume and reduced trip times offered by this powerful, versatile rocket. Reducing the life-cycle costs for NASA's space transportation flagship will maximize the exploration and scientific discovery returned from the taxpayer's investment. To that end, decisions made during development of SLS and associated systems will impact the nation's space exploration capabilities for decades. This paper will provide an update to the operations strategy presented at SpaceOps 2012. It will focus on: 1) Preparations to streamline the processing flow and infrastructure needed to produce and launch the world's largest rocket (i.e., through incorporation and modification of proven, heritage systems into the vehicle and ground systems); 2) Implementation of a lean approach to reachback support of hardware manufacturing, green-run testing, and launch site processing and activities; and 3) Partnering between the vehicle design and operations communities on state-ofthe- art predictive operations analysis techniques. An example of innovation is testing the integrated vehicle at the processing facility in parallel, rather than sequentially, saving both time and money. These themes are accomplished under the context of a new cross-program integration model that emphasizes peer-to-peer accountability and collaboration towards a common, shared goal. Utilizing the lessons learned through 50 years of human space flight experience, SLS is assigning the right number of people from appropriate backgrounds, providing them the right tools, and exercising the right processes for the job. The result will be a powerful, versatile, and capable heavy-lift, human-rated asset for the future human and scientific exploration of space.

Hefner, William Keith↗

NASA NTRS2014

NASA Space Launch System Operations Outlook

The National Aeronautics and Space Administration's (NASA) Space Launch System (SLS) Program, managed at the Marshall Space Flight Center (MSFC), is working with the Ground Systems Development and Operations (GSDO) Program, based at the Kennedy Space Center (KSC), to deliver a new safe, affordable, and sustainable capability for human and scientific exploration beyond Earth's orbit (BEO). Larger than the Saturn V Moon rocket, SLS will provide 10 percent more thrust at liftoff in its initial 70 metric ton (t) configuration and 20 percent more in its evolved 130-t configuration. The primary mission of the SLS rocket will be to launch astronauts to deep space destinations in the Orion Multi- Purpose Crew Vehicle (MPCV), also in development and managed by the Johnson Space Center. Several high-priority science missions also may benefit from the increased payload volume and reduced trip times offered by this powerful, versatile rocket. Reducing the lifecycle costs for NASA's space transportation flagship will maximize the exploration and scientific discovery returned from the taxpayer's investment. To that end, decisions made during development of SLS and associated systems will impact the nation's space exploration capabilities for decades. This paper will provide an update to the operations strategy presented at SpaceOps 2012. It will focus on: 1) Preparations to streamline the processing flow and infrastructure needed to produce and launch the world's largest rocket (i.e., through incorporation and modification of proven, heritage systems into the vehicle and ground systems); 2) Implementation of a lean approach to reach-back support of hardware manufacturing, green-run testing, and launch site processing and activities; and 3) Partnering between the vehicle design and operations communities on state-of-the-art predictive operations analysis techniques. An example of innovation is testing the integrated vehicle at the processing facility in parallel, rather than sequentially, saving both time and money. These themes are accomplished under the context of a new cross-program integration model that emphasizes peer-to-peer accountability and collaboration towards a common, shared goal. Utilizing the lessons learned through 50 years of human space flight experience, SLS is assigning the right number of people from appropriate backgrounds, providing them the right tools, and exercising the right processes for the job. The result will be a powerful, versatile, and capable heavy-lift, human-rated asset for the future human and scientific exploration of space.

Hefner, William Keith↗

DOE OSTI2021

Quantitative Evaluation of Autonomous Driving in CARLA

There has been a great deal of recent advancements in end-to-end imitation and reinforcement learning for self-driving vehicles. Despite this, there is a severe lack of standardized metrics for evaluating the performance of autonomous self-driving agents. Existing metrics are generally lacking in their ability to capture a wide range of driving behaviors and compare the severity of different failure cases. In this work, we introduce the Quantitative Evaluation for Driving metric, or QED, which assigns a quantitative score from 0-100 that captures the quality of driving for any driving agent. Our QED metric assesses different aspects of driving behavior including the ability to stay in the center of the lane, avoid weaving and erratic behavior, follow the speed limit, and avoid collisions, and it can be used under a wide range of driving scenarios. To show the effectiveness of our QED metric, we compare the scores generated by QED against scores assigned by human evaluators on a total of 30 different drivers and 6 different towns in the CARLA driving simulator. In ``easy'' evaluation scenarios, where it is relatively straightforward to distinguish better drivers from worse drivers, QED attains an average Pearson correlation of 0.96 and average Spearman correlation of 0.97 when compared against human evaluators. In ``hard'' evaluation scenarios, where it is far more ambiguous how to rank/score different types of bad driving behavior, QED attains an average Pearson correlation of 0.82 and average Spearman correlation of 0.75 when compared against human evaluators, which are both slighter higher than when we compare human evaluators against each other. While QED may not capture every characteristic that defines good driving, we consider it an important foundation for reproducibility and standardization in the community.

Gao, Shang↗

DOE OSTI2022

PyChargeModel (Oriented Programming Based Electric Vehicle and Electric Vehicle Supply Equipment Charging Model in Python) [SWR-22-39]

The PyChargeModel creates two classes called "ElectricVehicles" and "evse_class", which can be used to create multiple instances of electric vehicles (EVs) and electric vehicle supply equipment (EVSE or charging ports) and simulate charging behavior. These objects can be instantiated with several properties such as battery chemistries, battery pack sizes, cell sizes, charging port power, dc or ac chargers etc. The objects can communicate with each other by calling different methods built within the classes. Through these methods, each EV object can be assigned to an EVSE, charged either using a default protocol or using setpoint values communicated from a site controller via the EVSE object.

Mishra, Partha↗

NASA NTRS1986

Independent Orbiter Assessment (IOA): Analysis of the elevon subsystem

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA approach features a top-down analysis of the hardware to determine failure modes, criticality, and potential critical items. To preserve independence, this analysis was accomplished without reliance upon the results contained within the NASA FMEA/CIL documentation. This report documents the independent analysis results for the Orbiter Elevon system hardware. The elevon actuators are located at the trailing edge of the wing surface. The proper function of the elevons is essential during the dynamic flight phases of ascent and entry. In the ascent phase of flight, the elevons are used for relieving high wing loads. For entry, the elevons are used to pitch and roll the vehicle. Specifically, the elevon system hardware comprises the following components: flow cutoff valve; switching valve; electro-hydraulic (EH) servoactuator; secondary delta pressure transducer; bypass valve; power valve; power valve check valve; primary actuator; primary delta pressure transducer; and primary actuator position transducer. Each level of hardware was evaluated and analyzed for possible failure modes and effects. Criticality was assigned based upon the severity of the effect for each failure mode. Of the 25 failure modes analyzed, 18 were determined to be PCIs.

Wilson, R. E.↗

NASA NTRS1991

Dynamics Explorer-1 (DE-1)

The Dynamics Explorer (DE) mission is designed to study the Earth's electromagnetic fields at varying heights up to 4 Earth radii. The DE-1 was launched on a Delta 3913 launch vehicle from the Western Test Range and was placed in a 561 x 23279 km orbit with a 90 degree inclination. The Deep Space Network (DSN) began to support this extended mission on February 1, 1985. Coverage consists of five passes per day that last for 45 minutes each. Information is given in tabular form for DSN support, frequency assignments, telemetry, command, and tracking mission responsibility.

Gordon, F.↗

NASA NTRSDate not supplied

Development of the BOLT II Roughness Experiment for Flight

BOLT II is a sounding rocket research project with the goal of studying hypersonic boundary layer transition and turbulence. The BOLT II research vehicle is based on a three-dimensional geometry (a slightly longer version of BOLT) with concave surfaces and swept leading edges that provides two separate and distinct, also redundant, flow paths for conducting measurements. One side of BOLT II is dedicated to smooth surface transition and turbulence, to better study the natural instability processes, while the other has been assigned to study forced transition and turbulence using discrete roughness trips. The present paper is intended to document the primary drivers and decisions made leading up to finalizing the roughness side experiment for the BOLT II flight.

Hypersonic↗

NASA NTRSDate not supplied

Development of the BOLT II Roughness Experiment for Flight

hypersonic↗

NASA NTRS2025

Provider of Services for Urban Air Mobility (PSU) Prototype Simulation (X5) Final Report

Urban Air Mobility (UAM) is a new air transportation service concept to carry passengers or cargo in metropolitan areas, leveraged by innovative aircraft and air traffic automation technologies. NASA has conducted a series of simulations, called the X-series simulation, to evaluate the UAM concept of operations and support the development of airspace procedures and services for UAM operations. The simulation called “X5” was conducted in 2023 to test a Provider of Services for UAM (PSU) prototype developed by NASA for UAM flight planning, strategic conflict management support, and data exchange between UAM operators. In this simulation, two strategic conflict management capabilities, Demand-Capacity Balancing and Sequencing and Scheduling, were further investigated. This document describes the UAM system architecture modeled, the X5 simulation environment to be executed (e.g., traffic scenario and UAM airspace construct), and the strategic conflict management processes developed and evaluated in this study. Then, the simulation results are provided using several system performance metrics, such as the number of operations planned and activated, demand-capacity imbalances detected and resolved, and pre-departure delays. Based on these metrics, the test findings and lessons learned from this simulation are discussed. NASA developed a PSU prototype as part of a reference implementation of UAM system architecture and evolved strategic conflict management capabilities for UAM operations from the previous collaborative simulations with industry partners. Below is the summary of the achievements: - Aligned NASA’s UAM reference architecture with the FAA’s UAM ConOps notional architecture - Extended UAM airspace management capabilities to include 1) Demand-Capacity Balancing (DCB) to ensure operators coordinate planned usage of shared vertiports, and 2) Sequencing and Scheduling (S&S) at UAM corridor entry and exit points to help facilitate an orderly flow of traffic - Defined the PSU information exchange APIs and requirements towards informing industry standards - Developed and tested a NASA PSU prototype as reference implementation to validate the requirements and APIs - Developed a prototype service connecting NASA’s PSU and the FAA system for testing future PSU-ATM interface requirements - Tested NASA-developed assumptions for UAM operations such as airspace design, procedures, vehicle performance, and strategic conflict management methods to inform future Cooperative Operating Practices (COPs) development with industry - Evaluated system performance metrics such as number of simultaneous operations and ground delays that can help define system-level requirements. The simulation results showed that the UAM traffic demand could be managed to minimize the needs of tactical separation provision with ground delays assigned by DCB and S&S. These accomplishments and the lessons learned from the PSU Prototype X5 simulation activities will be valuable inputs for the Air Mobility Pathfinders (AMP) project, which is NASA’s new project to create and evaluate a reference architecture for safe, secure, and scalable UAM operations.

Simulation↗