Search NASA⌕ Search

SEARCH · Search NASA

Results for “scheduling software”

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 775 records · Page 43
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Application of Agile for Systems Engineering, Project Management and Modeling and Lessons Learned

The Systems Engineering team within the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has been transforming its development processes to be more efficient, robust,and responsive to change and to its stakeholders. To these ends, the Systems Engineering team trialed the integration of agile development techniques into existing and new processes. Agile development methods are well understood within the software development community. Outside ofsoftware development, however, how non-software project management (PM) and systems engineering (SE) teams implement agile development techniques is less well understood. In its transformation efforts, the ExMC SE team focused on three main areas: Improving the project communications among subsystem teams and stakeholders by adopting a scrum-like process, Changing the status and reporting mechanisms to improve schedule coordination between the subsystem team, SE leadership, and ExMC Element leadership, and Unifying the model-based SE workflow to improve understanding of Concepts of Operations across projects.This presentation highlights several of these transformations and what the SE team learned while undergoing the transformation.

S Lumpkins↗
NASA NTRSDate not supplied

Mission Operations, Cubed: NASA Marshall Operations Support for SmallSats

SmallSats have come a long way since the Huntsville Operations Support Center (HOSC) at NASA’s Marshall Space Flight Center supported its first “minisatellite” mission in 2010. And just as SmallSats themselves have evolved in those 12 years, so too has the HOSC’s mission support for SmallSats. Marshall Space Flight Center has a long history with payload and mission operations, including support for the Apollo missions to the moon, the Space Shuttle program, and 21 years of continuous around-the-clock science operations support for research aboard the International Space Station. Today, the HOSC is a multi-tenant facility, supporting not only ISS, but also NASA’s Commercial Crew program, the Space Launch System, the Hubble and Chandra observatories and others – including multiple SmallSat missions. Two SmallSat solar sail missions will be among those taking advantage of the HOSC’s resources for planning, training for and executing mission operations – the Near Earth Asteroid (NEA) Scout and Solar Cruiser missions. One of 10 6U CubeSats manifest on the Artemis I launch of NASA’s Space Launch System rocket this year, NEA Scout’s three-year mission will be supported through a more traditional operations concept, with a dedicated Flight Controller staff operating within the HOSC. Scheduled to launch as part of the Interstellar Mapping and Acceleration Probe (IMAP) in February 2025, Solar Cruiser’s 11-month mission will take a next-generation approach to operations by utilizing a multi-mission flight controller concept, as well as Marshall’s Telescience Resource Kit (TreK). TreK provides a suite of software applications and libraries that allow the Mission Operations Center to serve as an in-house ground system which incorporates remote and automation capability options for engineers and scientists. This presentation will compare the approaches the HOSC will use to support these two missions as a way of demonstrating the array of options NASA MSFC offers for operations support for CubeSat and SmallSat missions.

Darren S Wallace↗
NASA NTRS2016

Orion Entry Monitor

NASA is scheduled to launch the Orion spacecraft atop the Space Launch System on Exploration Mission 1 in late 2018. When Orion returns from its lunar sortie, it will encounter Earth's atmosphere with speeds in excess of 11 kilometers per second, and Orion will attempt its first precision-guided skip entry. A suite of flight software algorithms collectively called the Entry Monitor has been developed in order to enhance crew situational awareness and enable high levels of onboard autonomy. The Entry Monitor determines the vehicle capability footprint in real-time, provides manual piloting cues, evaluates landing target feasibility, predicts the ballistic instantaneous impact point, and provides intelligent recommendations for alternative landing sites if the primary landing site is not achievable. The primary engineering challenges of the Entry Monitor is in the algorithmic implementation in making a highly reliable, efficient set of algorithms suitable for onboard applications.

Smith, Kelly M.↗
NASA NTRS1998

Development and Testing of Automatically Generated ACS Flight Software for the MAP Spacecraft

By integrating the attitude determination and control system (ACS) analysis and design, flight software development, and flight software testing processes, it is possible to improve the overall spacecraft development cycle, as well as allow for more thorough software testing. One of the ways to achieve this integration is to use code-generation tools to automatically generate components of the ACS flight software directly from a high-fidelity (HiFi) simulation. In the development of the Microwave Anisotropy Probe (MAP) spacecraft, currently underway at the NASA Goddard Space Flight Center, approximately 1/3 of the ACS flight software was automatically generated. In this paper, we will examine each phase of the ACS subsystem and flight software design life cycle: analysis, design, and testing. In the analysis phase, we scoped how much software we would automatically generate and created the initial interface. The design phase included parallel development of the HiFi simulation and the hand-coded flight software components. Everything came together in the test phase, in which the flight software was tested, using results from the HiFi simulation as one of the bases of comparison for testing. Because parts of the spacecraft HiFi simulation were converted into flight software, more care needed to be put into its development and configuration control to support both the HiFi simulation and flight software. The components of the HiFi simulation from which code was generated needed to be designed based on the fact that they would become flight software. This process involved such considerations as protecting against mathematical exceptions, using acceptable module and parameter naming conventions, and using an input/output interface compatible with the rest of the flight software. Maintaining good configuration control was an issue for the HiFi simulation and the flight software, and a way to track the two systems was devised. Finally, an integrated test approach was devised to support flight software testing at both the unit- and build-test levels using the HiFi simulation to generate data for performance verification. Another benefit of the simulation and code-generation application used on the MAP project is that it supported bringing flight software and test data into the HiFi simulation environment. It was possible to integrate parts of the hand-coded flight software into the HiFi simulation, and also possible to import flight software test data for comparison and performance verification. This capability was used to incorporate the flight software Kalman filter into the HiFi simulation. This enabled us to greatly increase the amount of testing that could be done on the filter, because we could exert a greater degree of control over the software-only simulation than over the flight software test environment. Also, since the simulation could be used to run the Kalman filter faster than real time, our testing efficiency was greatly increased. We will conclude our discussion with a summary of the lessons learned thus far using automatically- generated code for the MAP project, and the spacecraft status as we work towards our scheduled launch in the year 2000.

ODonnell, James R., Jr.↗
NASA NTRSDate not supplied

Increasing Cognitive Ability/Reserve Using Software – Pilot (ICARUS-Pilot)

BACKGROUND This research study was competitively awarded under the 2022 JSC Innovation Charge Account (ICA) program administered by NASA Johnson Space Center’s Joint Technology Working Group. Study period of performance was May through September 2022, with a maximum allowed procurement budget of $10K. The study sought to quantify and assess the potential benefit of using commercial-off-the-shelf (COTS) cognitive training software to improve cognitive performance in an astronaut-like terrestrial population. METHODS Five volunteer research participants were recruited from the JSC employee population to mimic certain demographic characteristics of the NASA astronaut population (age, education/discipline). Participant cognitive performance was assessed before and after executing eighteen sessions of remote cognitive training executed nominally three times per week using six exercises within an adaptive app-based COTS software package (BrainHQ, Posit Science) on study-provided tablets. Pre- and post-training cognitive performance was measured using internal assessments in BrainHQ as well as Cognition Test Battery (CTB) version ISS B01 v3 (3.0.9-201710021500), an independent software test developed specifically for NASA and used currently in research studies on astronauts. BrainHQ exercises were posited to map well or partially to several CTB sub-tests. Participants provided feedback on their study experience formally via semi-structured interview at the conclusion of testing and informally throughout the study if they encountered issues. RESULTS The enrolled ICARUS-Pilot study participants generally matched Artemis crew demographic characteristics. Four of five participants have completed study training and assessment activities as of the writing of this abstract. These test participants complied well with desired training session frequency and duration yielding an average cumulative active training duration of 15 hours over an average of 45 days; participants showed 78% average improvement in metric performance for the six trained exercises, with an associated overall 33%ile ranking increase against performance of the entire BrainHQ subscribing population for internal pre/post assessment, agreeing with post-study survey self-reported performance increases. CTB overall feedback scoring, not corrected for learning effects, showed an average of 19% performance improvement across its 10 performance measures over the training period for the completed participants. Detailed analyses will be conducted once participant data collection for the study is complete and the resulting dataset is fully populated. DISCUSSION These preliminary results provide a positive trend for the effectiveness of the training approach, but further analysis will be needed to establish significance, investigate far transfer, and suggest the needed participant pool size for subsequent efforts to achieve statistically significant outcomes given similar results. The pilot study has already been helpful by allowing the study team to learn a great deal about the capabilities and limitations of the COTS software package that will be reflected in future proposals along with revised timelines for study execution and test participant management. From participant feedback, one common thread regarding the COTS training was that it felt overly repetitive – future proposals should reassess overall training duration, available levels for each trained exercise, and the behavior of the BrainHQ internal scheduler in determining which exercises should be trained and for how long. If the final analysis of this feasibility study ultimately supports it, the study team will recommend further investigation to fully evaluate this potential countermeasure and optimize its implementation. Future proposals would cite this feasibility study’s outcome and would seek to refine the training protocol and obtain statistically significant results for cognitive performance increases as well as retention data.

cognitive training↗
NASA NTRSDate not supplied

Increasing Cognitive Ability/Reserve Using Software – Pilot (ICARUS-Pilot)

Background: This research study was competitively awarded under the 2022 JSC Innovation Charge Account (ICA) program administered by NASA Johnson Space Center’s Joint Technology Working Group. Study period of performance was May through September 2022, with a maximum allowed procurement budget of $10K. The study sought to quantify and assess the potential benefit of using commercial-off-the-shelf (COTS) cognitive training software to improve cognitive performance in an astronaut-like terrestrial population. Methods: Five volunteer research participants were recruited from the JSC employee population to mimic certain demographic characteristics of the NASA astronaut population (age, education/discipline). Participant cognitive performance was assessed before and after executing eighteen sessions of remote cognitive training executed nominally three times per week using six exercises within an adaptive app-based COTS software package (BrainHQ, Posit Science) on study-provided tablets. Pre- and post-training cognitive performance was measured using internal assessments in BrainHQ as well as Cognition Test Battery (CTB) version ISS B01 v3 (3.0.9-201710021500), an independent software test developed specifically for NASA and used currently in research studies on astronauts. BrainHQ exercises were posited to map well or partially to several CTB sub-tests. Participants provided feedback on their study experience formally via semi-structured interview at the conclusion of testing and informally throughout the study if they encountered issues. Results: The enrolled ICARUS-Pilot study participants generally matched Artemis crew demographic characteristics. Four of five participants have completed study training and assessment activities as of the writing of this abstract. These test participants complied well with desired training session frequency and duration yielding an average cumulative active training duration of 15 hours over an average of 45 days; participants showed 78% average improvement in metric performance for the six trained exercises, with an associated overall 33%ile ranking increase against performance of the entire BrainHQ subscribing population for internal pre/post assessment, agreeing with post-study survey self-reported performance increases. CTB overall feedback scoring, not corrected for learning effects, showed an average of 19% performance improvement across its 10 performance measures over the training period for the completed participants. Detailed analyses will be conducted once participant data collection for the study is complete and the resulting dataset is fully populated. Discussion: These preliminary results provide a positive trend for the effectiveness of the training approach, but further analysis will be needed to establish significance, investigate far transfer, and suggest the needed participant pool size for subsequent efforts to achieve statistically significant outcomes given similar results. The pilot study has already been helpful by allowing the study team to learn a great deal about the capabilities and limitations of the COTS software package that will be reflected in future proposals along with revised timelines for study execution and test participant management. From participant feedback, one common thread regarding the COTS training was that it felt overly repetitive – future proposals should reassess overall training duration, available levels for each trained exercise, and the behavior of the BrainHQ internal scheduler in determining which exercises should be trained and for how long. If the final analysis of this feasibility study ultimately supports it, the study team will recommend further investigation to fully evaluate this potential countermeasure and optimize its implementation. Future proposals would cite this feasibility study’s outcome and would seek to refine the training protocol and obtain statistically significant results for cognitive performance increases as well as retention data.

cognitive training↗
NASA NTRS2016

Human-in-the-Loop Assessment of Alternative Clearances in Interval Management Arrival Operations

Interval Management Alternative Clearances (IMAC) was a human-in-the-loop simulation experiment conducted to explore the Air Traffic Management (ATM) Technology Demonstration (ATD-1) Concept of Operations (ConOps), which combines advanced arrival scheduling, controller decision support tools, and aircraft avionics to enable multiple time deconflicted, efficient arrival streams into a high-density terminal airspace. Interval Management (IM) is designed to support the ATD-1 concept by having an "Ownship" (IM-capable) aircraft achieve or maintain a specific time or distance behind a "Target" (preceding) aircraft. The IM software uses IM clearance information and the Ownship data (route of flight, current location, and wind) entered by the flight crew, and the Target aircraft's Automatic Dependent Surveillance-Broadcast state data, to calculate the airspeed necessary for the IM-equipped aircraft to achieve or maintain the assigned spacing goal.

Baxley, Brian T.↗
NASA NTRS2013

MPST Software: grl_pef_check

This innovation is a tool used to verify and validate spacecraft sequences at the predicted events file (PEF) level for the GRAIL (Gravity Recovery and Interior Laboratory, see http://www.nasa. gov/mission_pages/grail/main/index. html) mission as part of the Multi-Mission Planning and Sequencing Team (MPST) operations process to reduce the possibility for errors. This tool is used to catch any sequence related errors or issues immediately after the seqgen modeling to streamline downstream processes. This script verifies and validates the seqgen modeling for the GRAIL MPST process. A PEF is provided as input, and dozens of checks are performed on it to verify and validate the command products including command content, command ordering, flight-rule violations, modeling boundary consistency, resource limits, and ground commanding consistency. By performing as many checks as early in the process as possible, grl_pef_check streamlines the MPST task of generating GRAIL command and modeled products on an aggressive schedule. By enumerating each check being performed, and clearly stating the criteria and assumptions made at each step, grl_pef_check can be used as a manual checklist as well as an automated tool. This helper script was written with a focus on enabling the user with the information they need in order to evaluate a sequence quickly and efficiently, while still keeping them informed and active in the overall sequencing process. grl_pef_check verifies and validates the modeling and sequence content prior to investing any more effort into the build. There are dozens of various items in the modeling run that need to be checked, which is a time-consuming and errorprone task. Currently, no software exists that provides this functionality. Compared to a manual process, this script reduces human error and saves considerable man-hours by automating and streamlining the mission planning and sequencing task for the GRAIL mission.

Call, Jared A.↗
NASA NTRS2022

Validation of the Mars 2020 Fault Protection Design: Navigating the Infinity of the Off-Nominal

On July 30th 2020, the Mars 2020 mission successfully launched out of Cape Canaveral, Florida, passed through the Earth’s shadow, and began its short cruise to Mars. Less than seven months later, the Perseverance rover touched down safely in Jezero Crater to begin its ambitious mission that includes looking for signs of ancient life and collecting samples for future return to Earth. Getting to the successful landing, or “Tango Delta Nominal,” could not have been achieved without also considering the off-nominal. One of the teams supporting this ambitious mission is the fault protection (FP) team. This team is tasked with assessing the various failures, or faults, that could prevent mission success and with ensuring that the autonomous behaviors built into the software and hardware can detect faults and recover the vehicle to a safe state. As part of its charter, the FP team designed a test campaign to provide confidence in the system’s robustness to off-nominal scenarios across all of Mars 2020’s mission phases. The greatest challenge associated with designing such a validation campaign was reducing the infinite number of anomalous scenarios into a finite test suite. In addition, the tests needed to be executed efficiently in order to utilize the team’s limited test venue access, but still needed to maintain a level of rigor that guaranteed confidence in the test outcomes. Given that each test scenario generated massive amounts of data, the team also developed methods for quickly ascertaining whether the autonomous fault protection behaviors maintained vehicle safety in the presence of an anomaly. This paper summarizes the processes that the Mars 2020 fault protection team employed to execute its off-nominal validation campaign. It captures both the methods of generating a suite of off-nominal tests, as well as reducing it to a subset that can be realistically executed within schedule and resource constraints. It also describes the various processes and philosophies that the team utilized to execute the tests efficiently, including creating a standardized procedure template, keeping the test cases modular so that they could be easily interchanged, and capturing common fault injections in a change-controlled database. Finally, it will describe the tools and processes for assessing the test data, focusing in particular on a tool that evaluated vehicle state using “secondary” sources of data to validate that the software had truly configured the spacecraft to the expected safe state.

Morantz, Chaz↗
NASA NTRS1977

Discovery and repair of software anomalies

The average time required to discover and repair anomalies which appear randomly in the end-to-end tests performed after program completion is evaluated. A model which explains anomaly discovery and repair phenomena when applied to variations in work load and multiple-stage testing is presented. The theory shows that estimates of anomaly levels and team capability can be predicted after a significant fraction of the anomalies have been found, and indicates procedures for applying these figures to schedule estimation and work-load assignment. Of particular interest is the demonstration that end-to-end testing of programs in other than the operational environment is not generally cost effective.

Tausworthe, R. C.↗
NASA NTRS1987

Command/response protocols and concurrent software

A version of the program to control the parallel jaw gripper is documented. The parallel jaw end-effector hardware and the Intel 8031 processor that is used to control the end-effector are briefly described. A general overview of the controller program is given and a complete description of the program's structure and design are contained. There are three appendices: a memory map of the on-chip RAM, a cross-reference listing of the self-scheduling routines, and a summary of the top-level and monitor commands.

Bynum, W. L.↗
DOE OSTI2024

Analysis and Grading of the Test Performance of PS Modules for the CMS Phase-2 Outer Tracker Upgrade

The Outer Tracker of the CMS experiment provides information about the trajectory of charged particles produced in proton-proton collisions at the LHC. During the High Luminosity LHC upgrade, scheduled for the late 2020s, the Outer Tracker will be replaced with new modules capable of transmitting data to the L1 Trigger. These modules are being assembled at several facilities around the world, including Fermilab, necessitating coordinated standards of module quality. Here I discuss the development of POTATO (Phase-2 Outer Tracker Analyzer of Test Outputs), a C++ software which provides a standardized procedure for analyzing and grading test results of the Outer Tracker modules. The particular focus of this poster is on the analysis and grading of the PS (pixel-strip) modules in POTATO.

Riggall, Caroline↗
NASA NTRS1971

The handling qualities simulation program for the augmentor wing jet STOL research aircraft.

Description of a program in which a complete STOL research aircraft (modified de Havilland C8-A Buffalo) was simulated to determine final design values for control systems and devices which augment aircraft control. Program objectives, computer requirements, and the simulation software and hardware are outlined together with the organization of the digital operations. The simulation program in combination with simulator hardware provided test pilots a realistic representation of the aircraft, with the result that various control and stability augmentation systems were evaluated using pilot handling qualities ratings. Final design parameters were then found for the aircraft which is scheduled for flight test in early 1972.

Cleveland, W. B.↗
NASA NTRS1990

Managing Information On Costs

Cost Management Model, CMM, software tool for planning, tracking, and reporting costs and information related to costs. Capable of estimating costs, comparing estimated to actual costs, performing "what-if" analyses on estimates of costs, and providing mechanism to maintain data on costs in format oriented to management. Number of supportive cost methods built in: escalation rates, production-learning curves, activity/event schedules, unit production schedules, set of spread distributions, tables of rates and factors defined by user, and full arithmetic capability. Import/export capability possible with 20/20 Spreadsheet available on Data General equipment. Program requires AOS/VS operating system available on Data General MV series computers. Written mainly in FORTRAN 77 but uses SGU (Screen Generation Utility).

Taulbee, Zoe A.↗
DOE OSTI2024

Analysis and Grading of the Test Performance of PS Modules for the CMS Phase-II Outer Tracker Upgrade

The Outer Tracker detector of the Compact Muon Solenoid (CMS) experiment provides information about the trajectory of charged particles produced in proton-proton collisions at the Large Hadron Collider (LHC). During the High Luminosity LHC upgrade, scheduled for the late 2020s, the Outer Tracker will be replaced with new modules capable of transmitting data to the L1 Trigger. These modules are being assembled at several facilities around the world, including Fermilab, necessitating coordinated standards of module quality. Here I discuss the development of POTATO (Phase-II Outer Tracker Analyzer of Test Outputs), a C++ software which provides a standardized procedure for analyzing and grading test results of the Outer Tracker modules. The particular focus of this paper is on the analysis and grading of the PS (pixel-strip) modules in POTATO.

43 PARTICLE ACCELERATORS↗
NASA NTRS1999

Aerospace Safety Advisory Panel

This report covers the activities of the Aerospace Safety Advisory Panel (ASAP) for calendar year 1998-a year of sharp contrasts and significant successes at NASA. The year opened with the announcement of large workforce cutbacks. The slip in the schedule for launching the International Space Station (ISS) created a five-month hiatus in Space Shuttle launches. This slack period ended with the successful and highly publicized launch of the STS-95 mission. As the year closed, ISS assembly began with the successful orbiting and joining of the Functional Cargo Block (FGB), Zarya, from Russia and the Unity Node from the United States. Throughout the year, the Panel maintained its scrutiny of NASA's safety processes. Of particular interest were the potential effects on safety of workforce reductions and the continued transition of functions to the Space Flight Operations Contractor. Attention was also given to the risk management plans of the Aero-Space Technology programs, including the X-33, X-34, and X-38. Overall, the Panel concluded that safety is well served for the present. The picture is not as clear for the future. Cutbacks have limited the depth of talent available. In many cases, technical specialties are 'one deep.' The extended hiring freeze has resulted in an older workforce that will inevitably suffer significant departures from retirements in the near future. The resulting 'brain drain' could represent a future safety risk unless appropriate succession planning is started expeditiously. This and other topics are covered in the section addressing workforce. The major NASA programs are also limited in their ability to plan property for the future. This is of particular concern for the Space Shuttle and ISS because these programs are scheduled to operate well into the next century. In the case of the Space Shuttle, beneficial and mandatory safety and operational upgrades are being delayed because of a lack of sufficient present funding. Likewise, the ISS has little flexibility to begin long lead-time items for upgrades or contingency planning. For example, the section on computer hardware and software contains specific findings related to required longer range safety-related actions. NASA can be proud of its accomplishments this past year, but must remain ever vigilant, particularly as ISS assembly begins to accelerate. The Panel will continue to focus on both the short- and long-term aspects of risk management and safety planning. This task continues to be made manageable and productive by the excellent cooperation the Panel receives from both NASA and its contractors. Particular emphasis will continue to be directed to longer term workforce and program planning issues as well as the immediate risks associated with ISS assembly and the initial flights of the X-33 and X-34. Section 2 of this report presents specific findings and recommendations generated by ASAP activities during 1998. Section 3 contains more detailed information in support of these findings and recommendations. Appendix A is a current roster of Panel members, consultants, and staff. Appendix B contains NASA's response to the findings and recommendations from the 1997 ASAP Annual Report. Appendix C details the fact-finding activities of the Panel in 1998. During the year, Mr. Richard D. Blomberg was elected chair of the Panel and Vice Admiral (VADM) Robert F Dunn was elected deputy chair. VADM Bernard M. Kauderer moved from consultant to member. Mr. Charles J. Donlan retired from the Panel after many years of meritorious service. Ms. Shirley C. McCarty and Mr. Robert L. ('Hoot') Gibson joined the Panel as consultants.

Source record↗
NASA NTRS2011

NASA Technology Demonstrations Missions Program Overview

The National Aeronautics and Space Administration (NASA) Fiscal Year 2010 (FY10) budget introduced a new strategic plan that placed renewed emphasis on advanced missions beyond Earth orbit. This supports NASA s 2011 strategic goal to create innovative new space technologies for our exploration, science, and economic future. As a result of this focus on undertaking many and more complex missions, NASA placed its attention on a greater investment in technology development, and this shift resulted in the establishment of the Technology Demonstrations Missions (TDM) Program. The TDM Program, within the newly formed NASA Office of the Chief Technologist, supports NASA s grand challenges by providing a steady cadence of advanced space technology demonstrations (Figure 1), allowing the infusion of flexible path capabilities for future exploration. The TDM Program's goal is to mature crosscutting capabilities to flight readiness in support of multiple future space missions, including flight test projects where demonstration is needed before the capability can transition to direct mission The TDM Program has several unique criteria that set it apart from other NASA program offices. For instance, the TDM Office matures a small number of technologies that are of benefit to multiple customers to flight technology readiness level (TRL) 6 through relevant environment testing on a 3-year development schedule. These technologies must be crosscutting, which is defined as technology with potential to benefit multiple mission directorates, other government agencies, or the aerospace industry, and they must capture significant public interest and awareness. These projects will rely heavily on industry partner collaboration, and funding is capped for all elements of the flight test demonstration including planning, hardware development, software development, launch costs, ground operations, and post-test assessments. In order to inspire collaboration across government and industry, more than 70% of the TDM funds will be competitively awarded as a result of yearly calls for proposed flight demonstrators and selected based on possible payoff to NASA, technology maturity, customer interest, cost, and technical risk reduction. This paper will give an overview of the TDM Program s mission and organization, as well as its current status in delivering advanced space technologies that will enable more flexible and robust future missions. It also will provide several examples of missions that fit within these parameters and expected outcomes.

Turner, Susan↗
NASA NTRS2011

Draper Station Analysis Tool

Draper Station Analysis Tool (DSAT) is a computer program, built on commercially available software, for simulating and analyzing complex dynamic systems. Heretofore used in designing and verifying guidance, navigation, and control systems of the International Space Station, DSAT has a modular architecture that lends itself to modification for application to spacecraft or terrestrial systems. DSAT consists of user-interface, data-structures, simulation-generation, analysis, plotting, documentation, and help components. DSAT automates the construction of simulations and the process of analysis. DSAT provides a graphical user interface (GUI), plus a Web-enabled interface, similar to the GUI, that enables a remotely located user to gain access to the full capabilities of DSAT via the Internet and Webbrowser software. Data structures are used to define the GUI, the Web-enabled interface, simulations, and analyses. Three data structures define the type of analysis to be performed: closed-loop simulation, frequency response, and/or stability margins. DSAT can be executed on almost any workstation, desktop, or laptop computer. DSAT provides better than an order of magnitude improvement in cost, schedule, and risk assessment for simulation based design and verification of complex dynamic systems.

Bedrossian, Nazareth↗