Ka-band wide-bandgap solid-state power amplifier technology
Explore the source record for details and available documents.
Ka-band↗
SEARCH · Search NASA
Results for “programmatic presentation”
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.
Ka-band wide-bandgap solid-state power amplifier technology
Explore the source record for details and available documents.
programmatic presentation↗
Satellite Power Systems (SPS) concept definition study (Exhibit D). Volume 6, part 1: Cost and Programmatics
A summary of the cost data reviewed as well as conclusions and recommendations are presented. Cost and programmatic aspects of Rockwell's SPS CR-2 reference configuration were based on the results of several contracts with NASA and independent company-sponsored activities by the Space Operations and Satellite Systems Division of Rockwell International.
Hanley, G. M.↗
Space station needs, attributes and architectural options study. Volume 4: Architectural options, subsystems, technology and programmatics
Space station architectural options, habitability considerations and subsystem analyses, technology, and programmatics are reviewed. The methodology employed for conceiving and defining space station concepts is presented. As a result of this approach, architectures were conceived and along with their supporting rationale are described within this portion of the report. Habitability consideration and subsystem analyses describe the human factors associated with space station operations and includes subsections covering (1) data management, (2) communications and tracking, (3) environmental control and life support, (4) manipulator systems, (5) resupply, (6) pointing, (7) thermal management and (8) interface standardization. A consolidated matrix of subsystems technology issues as related to meeting the mission needs for a 1990's era space station is presented. Within the programmatics portion, a brief description of costing and program strategies is outlined.
Source record↗
Commercially Hosted Government Payloads: Lessons from Recent Programs
In a commercially hosted operational mode, a scientific instrument or operational device is attached to a spacecraft but operates independently from the spacecraft s primary mission. Despite the expected benefits of this arrangement, there are few examples of hosted payload programs actually being executed by government organizations. The lack of hosted payload programs is largely driven by programmatic challenges, both real and perceived, rather than by technical challenges. Partly for these reasons, NASA has not sponsored a hosted payload program, in spite of the benefits and visible community interest in doing so. In the interest of increasing the use of hosted payloads across the space community, this paper seeks to alleviate concerns about hosted payloads by identifying these programmatic challenges and presenting ways in which they can be avoided or mitigated. Despite the challenges, several recent hosted payload programs have been successfully completed or are currently in progress. This paper presents an assessment of these programs, with a focus on acquisition, costs, schedules, risks, and other programmatic aspects. The hosted payloads included in this study are the Federal Aviation Administration's Wide Area Augmentation System (WAAS) payloads, United States Coast Guard's Automatic Identification System (AIS) demonstration payload, Department of Defense's IP Router In Space (IRIS) demonstration payload, the United States Air Force's Commercially Hosted Infrared Payload (CHIRP), and the Australian Defence Force's Ultra High Frequency (UHF) payload. General descriptions of each of these programs are presented along with issues that have been encountered and lessons learned from those experiences. A set of recommended approaches for future hosted payload programs is presented, with a focus on addressing risks or potential problem areas through smart and flexible contracting up front. This set of lessons and recommendations is broadly applicable to future hosted payload programs, whether they are technology demonstrations, communications systems, or operational sensors. Additionally, we present a basic cost model for commercial access to space for hosted payloads as a function of payload mass
Andraschko, Mark A.↗
Programmatic risk balancing
This paper presents the first tool demonstration and assessment for balancing programmatic risk.
programmatic risk integration↗
The EOS AURA Tropospheric Emission Spectrometer (TES): Status of the Program
This slide presentation is a programmatic overview covering some of the highlights of the mission and serve as an introduction to the accompanying presentations at the workshop. It reviews the goals and the products of the TES experiment, a simplified chemistry of ozone in both the stratosphere and troposphere, a description of the instrument, and the TES operational modes. Included are graphs showing some of the results of TES analysis of the key constituents of the tropospheric chemistry and the inter-regional transport.
Fourier Transform Infrared (FTIR)↗
Introduction to Message-Bus Architectures for Space Systems
This course presents technical and programmatic information on the development of message-based architectures for space mission ground and flight software systems. Message-based architecture approaches provide many significant advantages over the more traditional socket-based one-of-a-kind integrated system development approaches. The course provides an overview of publish/subscribe concepts, the use of common isolation layer API's, approaches to message standardization, and other technical topics. Several examples of currently operational systems are discussed and possible changes to the system development process are presented. Benefits and lessons learned will be discussed and time for questions and answers will be provided.
Smith, Dan↗
NASA Activities: SpaceWire Working Group Meeting
This brief presentation highlights the efforts of the SpaceWire working group. The European Space Agency (ESA) contracted with the University of Dundee (UoD) to develop a prototype SpaceFibre Codec, which UoD has been demonstrated in hardware. UoD released a SpaceFibre Outline Specification which NASA plans to evaluate using a SpaceFibre sub-orbital demonstration (in development). Comments, questions and recommendations for ESA and UoD are provided here to generate discussion and expand participation. General findings are that the system level behavior of SpaceFibre is missing from the SpaceFibre Outline Specification, there is a need to understand how SpaceWire maps to SpaceFibre (and vice versa), and there is a need to clarify user interface to resolve inconsistencies. Architecture, virtual channel and programmatic recommendations are presented.
Rakow, Glenn↗
Modular space station phase B extension period executive summary
A narrative summary is presented of technical, programmatic, and planning information developed during the space station definition study extension period. The modular space station is emphasized, but tasks pertaining to shuttle sorties missions and information management advanced development are included. A series of program options considering technical, schedule, and programmatic alternatives to the baseline program are defined and evaluated.
Tischler, A. A.↗
Study for identification of Beneficial Uses of Space (BUS). Volume 2: Technical report. Book 1: Sections 1 through 4
Consolidated information is presented for the study whose purpose was to identify products, processes, and services to be produced in future spacecraft environments for direct utilization on earth. Discussion of methodology for selecting from among potential space processing approaches, definition of requirements for experiments and tests needed to acquire sufficient knowledge for proof testing of selected processes, formulation of research and development schedules to achieve proof testing, and documentation of the decision processes involved in the programs are presented. Technology and programmatics are reported for the following select studies: (1) surface acoustic wave components; (2) transparent oxides; (3) high purity tungsten X-ray targets; and (4) high specificity isoenzymes.
Source record↗
Space station accommodations for life sciences research facilities. Phase 1: Conceptual design and programmatics studies for Missions SAAX0307, SAAX0302 and the transition from SAAX0307 to SAAX0302. Volume 2: Study results
Lockheed Missiles and Space Company's conceptual designs and programmatics for a Space Station Nonhuman Life Sciences Research Facility (LSRF) are presented. Conceptual designs and programmatics encompass an Initial Orbital Capability (IOC) LSRF, a growth or follow-on Orbital Capability (FOC), and the transitional process required to modify the IOC LSFR to the FOC LSFR. The IOC and FOC LSFRs correspond to missions SAAX0307 and SAAX0302 of the Space Station Mission Requirements Database, respectively.
Source record↗
Considerations for Micro- and Nano-scale Space Payloads
This paper collects and summarizes many of the issues associated with the design, analysis, and flight of space payloads. However, highly miniaturized experimental packages are highly susceptible to the deleterious effects of induced contamination and charged particles when they are directly exposed to the space environment. These two problem areas are addressed and a general discussion of space environments, applicable design and analysis practices (with extensive references to the open literature) and programmatic considerations are presented.
Altemir, David A.↗
Overview of SBMD, NMSD and AMSD
For the past several years, NASA has conducted a coordinated mirror technology development program via SBIR's and contracts. This presentation provides a programmatic overview of three specific projects: SBMD (Subscale Beryllium Mirror Demonstrator), NMSD (NGST Mirror System Demonstrator) and AMSD (Advanced Mirror System Demonstrator). Specific emphasis will be given to technical constraints and objectives.
Stahl, H. Philip↗
An Introduction to Message-Bus Architectures for Space Systems
This course presents technical and programmatic information on the development of message-based architectures for space mission ground and flight software systems. Message-based architecture approaches provide many significant advantages over the more traditional socket-based one-of-a-kind integrated system development approaches. The course provides an overview of publish/subscribe concepts, the use of common isolation layer API's, approaches to message standardization, and other technical topics. Several examples of currently operational systems are discussed and possible changes to the system discussed and time for questions and answers will be provided.
Smith, Danford↗
Gateway Autonomy for Enabling Deep Space Exploration
The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.
Molly Anderson↗
Gateway Autonomy for Enabling Deep Space Exploration
The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.
Molly Anderson↗