Search NASA⌕ Search

SEARCH · Search NASA

Results for “Organizational Objectives”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Adaptive Planning: Understanding Organizational Workload to Capability/ Capacity through Modeling and Simulation

In August 2003, the Secretary of Defense (SECDEF) established the Adaptive Planning (AP) initiative [1] with an objective of reducing the time necessary to develop and revise Combatant Commander (COCOM) contingency plans and increase SECDEF plan visibility. In addition to reducing the traditional plan development timeline from twenty-four months to less than twelve months (with a goal of six months)[2], AP increased plan visibility to Department of Defense (DoD) leadership through In-Progress Reviews (IPRs). The IPR process, as well as the increased number of campaign and contingency plans COCOMs had to develop, increased the workload while the number of planners remained fixed. Several efforts from collaborative planning tools to streamlined processes were initiated to compensate for the increased workload enabling COCOMS to better meet shorter planning timelines. This paper examines the Joint Strategic Capabilities Plan (JSCP) directed contingency planning and staffing requirements assigned to a combatant commander staff through the lens of modeling and simulation. The dynamics of developing a COCOM plan are captured with an ExtendSim [3] simulation. The resulting analysis provides a quantifiable means by which to measure a combatant commander staffs workload associated with development and staffing JSCP [4] directed contingency plans with COCOM capability/capacity. Modeling and simulation bring significant opportunities in measuring the sensitivity of key variables in the assessment of workload to capability/capacity analysis. Gaining an understanding of the relationship between plan complexity, number of plans, planning processes, and number of planners with time required for plan development provides valuable information to DoD leadership. Through modeling and simulation AP leadership can gain greater insight in making key decisions on knowing where to best allocate scarce resources in an effort to meet DoD planning objectives.

Hase, Chris↗
NASA NTRS1984

The dynamics of software development project management: An integrative systems dynamic perspective

Rather than continuing to focus on software development projects per se, the system dynamics modeling approach outlined is extended to investigate a broader set of issues pertaining to the software development organization. Rather than trace the life cycle(s) of one or more software projects, the focus is on the operations of a software development department as a continuous stream of software products are developed, placed into operation, and maintained. A number of research questions are ""ripe'' for investigating including: (1) the efficacy of different organizational structures in different software development environments, (2) personnel turnover, (3) impact of management approaches such as management by objectives, and (4) the organizational/environmental determinants of productivity.

Vandervelde, W. E.↗
NASA NTRS2003

Using CASE to Adopt Organizational Learning at NASA

The research direction was articulated in a statement of work created in collaboration between two program colleagues, an outside researcher and an internal user. The researcher was to deliver an implemented CASE tool (CasewiseTM) that was to be used to serve non-traditional (i.e., not software development related) organizational purposes. The explicitly stated functions of the tool were the support of 1) ISO-9000 compliance in the documentation of processes and 2) the management of process improvement. The collaborative team consisted of the researcher (GT), a full-time accompanying student (CRO), and the user (JD). The team originally focused on populating the CASE repository for the purpose of solving the two primary objectives. Consistent with the action research approach, several additional user requirements emerged as the project evolved, needs became apparent in discussions about how the tool would be used to solve organizational problems. These deliverables were contained within the CASE repository: 1) the creation of a paradigm diagram 2) the creation of a context diagram 3) the creation of child diagrams 4) the generation of 73 issues relating to organizational change 5) a compendium of stakeholder interview transcripts All record keeping was done manually and then keyed into the CASE interface. An issue is the difference between an organization s current situation (action) and its collective ideals.

Templeton, Gary F.↗
DOE OSTI2025

Flower‐Type Organized Trade‐Wind Cumulus: A Multi‐Day Lagrangian Large Eddy Simulation Intercomparison Study

Shallow cumulus cloud fields in subtropical marine trade wind environments, particularly over the tropical Atlantic Ocean, show distinct organizational patterns. Among these, Flower‐type clouds are characterized by expansive stratiform cloud patches surrounded by regions of scattered convection. The objectives of this study were (a) to construct a case study of a time period during the EUREC 4 A/ATOMIC field campaign when Flower‐type organization was observed, (b) to evaluate the fidelity of a multi‐model ensemble of large eddy simulations of that case, and (c) to analyze the interaction between cloud and precipitation processes and mesoscale organization in the simulations. The simulations follow a quasi‐Lagrangian trajectory, allowing mesoscale features to develop over time in a domain that follows the boundary‐layer airmass. The results show a broad agreement in simulated thermodynamic properties across different LES codes, with Flower‐type cloud patches appearing within hours of each other. The consensus among models is consistent with observations made during the EUREC 4 A/ATOMIC field campaign on the specific day of interest. The cloud structure reveals three distinct peaks in the joint probability densities of cloud base and cloud top height, with the dominant peak at any given time influenced by the stage of cloud organization. The simulated cloud system evolution reveals consistent occurrence of maxima in liquid water path and rain rate before Flower reaches its maximum length scale. Targeted sensitivity tests reveal a weak relationship between Cloud Droplet Number concentration and the extent/degree/type of organization.

EUREC4A↗
NASA NTRS1995

TRISTAR 1: Evaluation methods for testing head-up display (HUD) flight symbology

The first in a series of piloted head-up display (HUD) flight symbology studies (TRISTAR) measuring pilot task performance was conducted at the NASA Ames Research Center by the Tri-Service Flight Symbology Working Group (FSWG). Sponsored by the U.S. Army Aeroflightdynamics Directorate, this study served as a focal point for the FSWG to examine HUD test methodology and flight symbology presentations. HUD climb-dive marker dynamics and climb-dive ladder presentations were examined as pilots performed air-to-air (A/A), air-to-ground (A/G), instrument landing system (ILS), and unusual attitude (UA) recover tasks. Symbolic presentations resembled pitch ladder variations used by the U.S. Air Force (USAF), U.S. Navy (USN), and Royal Air Force (RAF). The study was initiated by the FSWG to address HUD flight symbology deficiencies, standardization, issue identification, and test methodologies. It provided the mechanism by which the USAF, USN, RAF, and USA could integrate organizational ideas and reduce differences for comparisons. Specifically it examined flight symbology issues collectively identified by each organization and the use of objective and subjective text methodology and flight tasking proposed by the FSWG.

Newman, R. L.↗
NASA NTRSDate not supplied

Gateway Implementation of Cybersecurity Requirements

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

Svetlana Hanson↗
NASA NTRSDate not supplied

Gateway Implementation of Cybersecurity Requirements

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

Cybersecurity↗
NASA NTRS1994

STS-59 Space Shuttle mission report

The STS-59 Space Shuttle Program Mission Report summarizes the Payload activities as well as the Orbiter, External Tank (ET), Solid Rocket Booster (SRB), Redesigned Solid Rocket Motor (RSRM), and the Space Shuttle main engine (SSME) systems performance during the sixty-second flight of the Space Shuttle Program and sixth flight of the Orbiter vehicle Endeavor (OV-105). In addition to the Orbiter, the flight vehicle consisted of an ET designated as ET-63; three SSME's which were designated as serial numbers 2028, 2033, and 2018 in positions 1, 2, and 3, respectively; and two SRB's which were designated BI-065. The RSRM's that were installed in each SRB were designated as 360W037A (welterweight) for the left SRB, and 360H037B (heavyweight) for the right SRB. This STS-59 Space Shuttle Program Mission Report fulfills the Space Shuttle Program requirement as documented in NSTS 07700, Volume 8, Appendix E. That document requires that each major organizational element supporting the Program report the results of its hardware evaluation and mission performance plus identify all related in-flight anomalies. The primary objective of the STS-59 mission was to successfully perform the operations of the Space Radar Laboratory-1 (SRL-1). The secondary objectives of this flight were to perform the operations of the Space Tissue Loss-A (STL-A) and STL-B payloads, the Visual Function Tester-4 (VFT-4) payload, the Shuttle Amateur Radio Experiment-2 (SAREX-2) experiment, the Consortium for Materials Development in Space Complex Autonomous Payload-4 (CONCAP-4), and the three Get-Away Special (GAS) payloads.

Fricke, Robert W., Jr.↗
NASA NTRS1994

STS-62 Space Shuttle mission report

The STS-62 Space Shuttle Program Mission Report summarizes the Payload activities as well as the Orbiter, External Tank (ET), Solid Rocket Booster (SRB), Redesigned Solid Rocket Motor (RSRM), and the Space Shuttle main engine (SSHE) systems performance during the sixty-first flight of the Space Shuttle Program and sixteenth flight of the Orbiter vehicle Columbia (OV-102). In addition to the Orbiter, the flight vehicle consisted of an ET designated as ET-62; three SSME's which were designated as serial numbers 2031, 2109, and 2029 in positions 1, 2, and 3, respectively; and two SRB's which were designated BI-064. The RSRM's that were installed in each SRB were designated as 360L036A (lightweight) for the left SRB, and 36OWO36B (welterweight) for the right SRB. This STS-62 Space Shuttle Program Mission Report fulfills the Space Shuttle Program requirement as documented in NSTS 07700, Volume 8, Appendix E. That document requires that each major organizational element supporting the Program report the results of its hardware evaluation and mission performance plus identify all related in-flight anomalies. The primary objectives of the STS-62 mission were to perform the operations of the United States Microgravity Payload-2 (USMP-2) and the Office of Aeronautics and Space Technology-2 (OAST-2) payload. The secondary objectives of this flight were to perform the operations of the Dexterous End Effector (DEE), the Shuttle Solar Backscatter Ultraviolet/A (SSBUV/A), the Limited Duration Space Environment Candidate Material Exposure (LDCE), the Advanced Protein Crystal Growth (APCG), the Physiological Systems Experiments (PSE), the Commercial Protein Crystal Growth (CPCG), the Commercial Generic Bioprocessing Apparatus (CGBA), the Middeck Zero-Gravity Dynamics Experiment (MODE), the Bioreactor Demonstration System (BDS), the Air Force Maui Optical Site Calibration Test (AMOS), and the Auroral Photography Experiment (APE-B).

Fricke, Robert W., Jr.↗
NASA NTRS1994

STS-61 Space Shuttle mission report

The STS-61 Space Shuttle Program Mission Report summarizes the Hubble Space Telescope (HST) servicing mission as well as the Orbiter, External Tank (ET), Solid Rocket Booster (SRB), Redesigned Solid Rocket Motor (RSRM), and the Space Shuttle main engine (SSME) systems performance during the fifty-ninth flight of the Space Shuttle Program and fifth flight of the Orbiter vehicle Endeavour (OV-105). In addition to the Orbiter, the flight vehicle consisted of an ET designated as ET-60; three SSME's which were designated as serial numbers 2019, 2033, and 2017 in positions 1, 2, and 3, respectively; and two SRB's which were designated BI-063. The RSRM's that were installed in each SRB were designated as 360L023A (lightweight) for the left SRB, and 360L023B (lightweight) for the right SRB. This STS-61 Space Shuttle Program Mission Report fulfills the Space Shuttle Program requirement as documented in NSTS 07700, Volume 8, Appendix E. That document requires that each major organizational element supporting the Program report the results of its hardware evaluation and mission performance plus identify all related in-flight anomalies. The primary objective of the STS-61 mission was to perform the first on-orbit servicing of the Hubble Space Telescope. The servicing tasks included the installation of new solar arrays, replacement of the Wide Field/Planetary Camera I (WF/PC I) with WF/PC II, replacement of the High Speed Photometer (HSP) with the Corrective Optics Space Telescope Axial Replacement (COSTAR), replacement of rate sensing units (RSU's) and electronic control units (ECU's), installation of new magnetic sensing systems and fuse plugs, and the repair of the Goddard High Resolution Spectrometer (GHRS). Secondary objectives were to perform the requirements of the IMAX Cargo Bay Camera (ICBC), the IMAX Camera, and the Air Force Maui Optical Site (AMOS) Calibration Test.

Fricke, Robert W., Jr.↗
NASA NTRS1994

STS-60 Space Shuttle mission report

The STS-60 Space Shuttle Program Mission Report summarizes the Payload activities as well as the Orbiter, External Tank (ET), Solid Rocket Booster (SRB), Redesigned Solid Rocket Motor (RSRM), and the Space Shuttle main engine (SSME) systems performance during the sixtieth flight of the Space Shuttle Program and eighteenth flight of the Orbiter vehicle Discovery (OV-103). In addition to the Orbiter, the flight vehicle consisted of an ET designated at ET-61 (Block 10); three SSME's which were designated as serial numbers 2012, 2034, and 2032 in positions 1, 2, and 3, respectively; and two SRB's which were designated BI-062. The RSRM's that were installed in each SRB were designated as 360L035A (lightweight) for the left SRB, and 360Q035B (quarterweight) for the right SRB. This STS-60 Space Shuttle Program Mission Report fulfills the Space Shuttle Program requirement as documented in NSTS 07700, Volume VIII, Appendix E. That document requires that each major organizational element supporting the Program report the results of its hardware evaluation and mission performance plus identify all related in-flight anomalies. The primary objectives of the STS-60 mission were to deploy and retrieve the Wake Shield Facility-1 (WSF-1), and to activate the Spacehab-2 payload and perform on-orbit experiments. Secondary objectives of this flight were to activate and command the Capillary Pumped Loop/Orbital Debris Radar Calibration Spheres/Breman Satellite Experiment/Getaway Special (GAS) Bridge Assembly (CAPL/ODERACS/BREMSAT/GBA) payload, the Auroral Photography Experiment-B (APE-B), and the Shuttle Amateur Radio Experiment-II (SAREX-II).

Fricke, Robert W., Jr.↗
NASA NTRS2018

Progress Towards Integrating the Finite-Volume Cubed-Sphere (FV3) Dynamical Core Tangent Linear and Adjoint Models into JEDI

The Joint Effort for Data assimilation Integration (JEDI) -- led by the Joint Center for Satellite Data Assimilation (JCSDA) -- is an inter-organizational endeavor to develop a common framework for performing data assimilation. This extensive framework will ultimately provide solvers, observation operators, interpolation and model interfaces using object oriented modeling. Two partners involved in JEDI use or plan to use the Finite Volume Cubed-Sphere (FV3) dynamical core to produce weather forecasts; these are NASA's Global Modeling and Assimilation Office and NOAA's National Center for Environment Prediction. In this work we present an update on ongoing efforts to integrate the FV3 tangent linear and adjoint models into the prototype JEDI framework. We setup and run a simple cycled data assimilation experiment using 4DVAR on the cubed sphere grid and with the FV3 tangent linear and adjoint models. Development of the observation operators for JEDI is separately underway. Instead of using real observations a simplified set of simulated observations will be used. We discuss the steps required to bring the FV3 linearized model into the object oriented framework and consider what would be the computational requirements of running this configuration for an operational system. FV3 uses a small time-step to ensure that small scales are well resolved, however this presents design challenges when running 4DVAR with the adjoint. An approach to storing the FV3 model trajectory has been developed that maintains the flexibility of using automatic differentiation. We discuss how this approach is incorporated into the framework. Other important uses of adjoint models include computing observation impacts and singular vectors, we consider how these tools can be included in JEDI.

Holdaway, Daniel↗
NASA NTRS1994

Annual program analysis of the NASA Space Life Sciences Research and Education Support Program

The basic objectives of this contract are to stimulate, encourage, and assist research and education in NASA life sciences. Scientists and experts from a number of academic and research institutions in this country and abroad are recruited to support NASA's need to find a solution to human physiological problems associated with living and working in space and on extraterrestrial bodies in the solar system. To fulfill the contract objectives, a cadre of staff and visiting scientists, consultants, experts, and subcontractors has been assembled into a unique organization dedicated to the space life sciences. This organization, USRA's Division of Space Life Sciences, provides an academic atmosphere, provides an organizational focal point for science and educational activities, and serves as a forum for the participation of eminent scientists in the biomedical programs of NASA. The purpose of this report is to demonstrate adherence to the requirement of Contract NAS9-18440 for a written review and analysis of the productivity and success of the program. In addition, this report makes recommendations for future activities and conditions to further enhance the objectives of the program and provides a self-assessment of the cost performance of the contract.

Source record↗
DOE OSTI2020

Understanding Structures of Cyber Competition in an Era of Major Power Rivalry

Over the past two decades, the cyber domain has emerged and evolved into a key strategic domain for nations across the globe. Security strategies are espoused by heads of state that focus on how to manage the increasingly enormous, crosscutting impact that the cyber domain has on national security across economic, military, intelligence, intellectual property, and countless other facets. These strategies frequently evolve, and even change entirely, as leaders adapt to new technologies and administrations change. Even if these strategies did not change at all, they would take inordinate amounts of time to effectively implement within the organizational structures of government. The time required to go from setting department and agency-level goals, to the time small teams have well-oiled processes and expertise to accomplish tactical objectives that meet the strategic vision is lengthy. With near certainty, by the time objectives and vision are implemented, the landscape, strategy, or both has changed entirely. While this churn will likely never cease due to the rapidly changing nature of the cyber domain, this problem raises an important question: can governmental structures be organized to rapidly adapt to changing cyber strategies? As offices responsible for particular missions in cyberspace shuffle about within the bureaucracy, are technical capabilities enabled or enhanced? No matter how advanced a particular technical capability is or how adept the staff is at solving problems, they will be ineffective if placed haphazardly within the organization: the right authorities may not exist for their office, the correct lines of interpersonal communication may not be established properly, or insufficient resources have not been allocated to effectively deploy a brilliant technical solution. This concept of organizational agility in the context of national cyber capabilities is important when taking into account the National Defense Strategy’s emphasis on cyber capability and the ability of the United States to compete and rapidly adapt to new challenges posed by rivals. As a nation, we are at a point where technology evolves rapidly enough to warrant thoughtful and nimble changes to the bureaucratic structures that support how cyber operations are carried out. Taking these questions and cross-comparing them to the organizational structures across China, Russia, and the United States provides for an interesting thought experiment. As non-democratic regimes, China and Russia have differing priorities and internal power dynamics than the United States and thus organize their governments differently. By combining known and broadcasted strategies of these nations with the observed technical capabilities demonstrated in the public domain, we can begin to see how organizational structures map to strategic goals and directly enable technical capabilities. Insight can be gained by introducing organizational structures into traditional analysis focusing solely around strategies and capabilities; additionally, otherwise unknown capabilities or intents might be discovered or inferred by analyzing organizational structures alone. Analyzing cyber operations from this oft-overlooked perspective could potentially provide useful insight and more concrete actions that can be undertaken to realize the National Defense Strategy’s goals.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗
DOE OSTI2023

Establishment of an Intertribal Technical Energy Providers Network (Final Technical Report)

The Midwest Tribal Energy Resources Association (MTERA) embarked on a 5-year (extended to 7-year) initiative aimed at advancing Tribal energy resilience and sustainability through intertribal collaboration. By bringing together Tribes in Minnesota, Wisconsin, and Michigan (EPA Region 5 Tribes), the project's scope encompassed organizational growth, governance and management formalization and enhancement, and the planning and deployment of energy-related services to Member Tribes. MTERA strategically pursued four key objectives to fulfill its mission: 1. Clearinghouse Development: Creation of a centralized hub offering valuable information, education, and outreach for Tribal communities and their neighbors. 2. Policy Liaison: Serving as a vital link between federal and state agencies to contribute to the formulation of inclusive energy policies that ensure both Tribal and regional energy success. 3. Energy Planning and Research: Providing essential support for energy planning, researching financing opportunities, and exploring effective procurement strategies. 4. Training Support: Facilitating training and apprenticeship initiatives to empower the Tribal workforce and enhance community capabilities.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗
NASA NTRS2006

The NASA Constellation University Institutes Project: Thrust Chamber Assembly Virtual Institute

This paper documents key aspects of the Constellation University Institutes Project (CUIP) Thrust Chamber Assembly (TCA) Virtual Institute (VI). Specifically, the paper details the TCA VI organizational and functional aspects relative to providing support for Constellation Systems. The TCA VI vision is put forth and discussed in detail. The vision provides the objective and approach for improving thrust chamber assembly design methodologies by replacing the current empirical tools with verified and validated CFD codes. The vision also sets out ignition, performance, thermal environments and combustion stability as focus areas where application of these improved tools is required. Flow physics and a study of the Space Shuttle Main Engine development program are used to conclude that the injector is the key to robust TCA design. Requirements are set out in terms of fidelity, robustness and demonstrated accuracy of the design tool. Lack of demonstrated accuracy is noted as the most significant obstacle to realizing the potential of CFD to be widely used as an injector design tool. A hierarchical decomposition process is outlined to facilitate the validation process. A simulation readiness level tool used to gauge progress toward the goal is described. Finally, there is a description of the current efforts in each focus area. The background of each focus area is discussed. The state of the art in each focus area is noted along with the TCA VI research focus in the area. Brief highlights of work in the area are also included.

Tucker, P. Kevin↗
NASA NTRS1979

Overview of Federal wind energy program

The objectives and strategies of the Federal wind energy program are described. Changes in the program structure and some of the additions to the program are included. Upcoming organizational changes and some budget items are discussed, with particular emphasis on recent significant events regarding new approvals.

Ancona, D. F.↗
NASA NTRS1986

X-29A technology demonstrator flight test program overview

An overview of the X-29A functional flight program and concept evaluation program is presented, including some of the unique and different preparations for the first flight. Included are a discussion of the many organizational responsibilities and a description of the program management structure for the test team. Also discussed are preflight ground, flight functional envelope expansion, and flight research test objectives and qualitive results to date for both a limited-envelope flight control system and an expanded-envelope system. The aircraft, including the instrumentation system and measurements, is described. In addition, a discussion is included regarding the use of major support facilities, such as ground and flight simulators, the NASA Western Aeronautical Test Range and mission control center, and the Grumman automated telemetry station. An overview of the associated real-time and postflight batch data processing software approaches is presented. The use of hardware-in-the-loop simulation for independent verification and validation and mission planning and practice is discussed. Also included is a description of the flight-readiness review, the airworthiness and flight safety review, work scheduling, technical briefings, and preflight and postflight crew briefings. The configuration control process used on the X-29A program is described, and its relationship to both simulation and aircraft operations is discussed. An X-29A schedule overview is presented with an outline of a proposed follow-on program.

Sefic, W. J.↗