Search NASA⌕ Search

SEARCH · Search NASA

Results for “architect”

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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS2005

Creating Communications, Computing, and Networking Technology Development Road Maps for Future NASA Human and Robotic Missions

For human and robotic exploration missions in the Vision for Exploration, roadmaps are needed for capability development and investments based on advanced technology developments. A roadmap development process was undertaken for the needed communications, and networking capabilities and technologies for the future human and robotics missions. The underlying processes are derived from work carried out during development of the future space communications architecture, an d NASA's Space Architect Office (SAO) defined formats and structures for accumulating data. Interrelationships were established among emerging requirements, the capability analysis and technology status, and performance data. After developing an architectural communications and networking framework structured around the assumed needs for human and robotic exploration, in the vicinity of Earth, Moon, along the path to Mars, and in the vicinity of Mars, information was gathered from expert participants. This information was used to identify the capabilities expected from the new infrastructure and the technological gaps in the way of obtaining them. We define realistic, long-term space communication architectures based on emerging needs and translate the needs into interfaces, functions, and computer processing that will be required. In developing our roadmapping process, we defined requirements for achieving end-to-end activities that will be carried out by future NASA human and robotic missions. This paper describes: 10 the architectural framework developed for analysis; 2) our approach to gathering and analyzing data from NASA, industry, and academia; 3) an outline of the technology research to be done, including milestones for technology research and demonstrations with timelines; and 4) the technology roadmaps themselves.

Bhasin, Kul↗
NASA NTRS2005

Middleware Evaluation and Benchmarking for Use in Mission Operations Centers

Middleware technologies have been promoted as timesaving, cost-cutting alternatives to the point-to-point communication used in traditional mission operations systems. However, missions have been slow to adopt the new technology. The lack of existing middleware-based missions has given rise to uncertainty about middleware's ability to perform in an operational setting. Most mission architects are also unfamiliar with the technology and do not know the benefits and detriments to architectural choices - or even what choices are available. We will present the findings of a study that evaluated several middleware options specifically for use in a mission operations system. We will address some common misconceptions regarding the applicability of middleware-based architectures, and we will identify the design decisions and tradeoffs that must be made when choosing a middleware solution. The Middleware Comparison and Benchmark Study was conducted at NASA Goddard Space Flight Center to comprehensively evaluate candidate middleware products, compare and contrast the performance of middleware solutions with the traditional point- to-point socket approach, and assess data delivery and reliability strategies. The study focused on requirements of the Global Precipitation Measurement (GPM) mission, validating the potential use of middleware in the GPM mission ground system. The study was jointly funded by GPM and the Goddard Mission Services Evolution Center (GMSEC), a virtual organization for providing mission enabling solutions and promoting the use of appropriate new technologies for mission support. The study was broken into two phases. To perform the generic middleware benchmarking and performance analysis, a network was created with data producers and consumers passing data between themselves. The benchmark monitored the delay, throughput, and reliability of the data as the characteristics were changed. Measurements were taken under a variety of topologies, data demands, and data characteristics, using several middleware products. All results were compared to systems using traditional point-to-point socket communication. By comparing performance results under Merent settings, inferences could be made about each middleware's ability to meet certain requirements of the GPM mission. The second phase simulated a middleware-based mission operations center. Actual mission support tools were either used or simulated to create real world demands on the middleware. Network and computer demands were watched closely to verify that no specific idiosyncrasies of mission operations activities would prove unsupportable by the middleware. In our presentation, we will address some commonly accepted misconceptions concerning middleware in mission support architectures. Specifically, we will focus on the perception that middleware solutions are too slow or impose too much overhead for real-time mission operations, and that middleware solutions are too expensive for small

Antonucci, Rob↗
NASA NTRS2004

Control System Architectures, Technologies and Concepts for Near Term and Future Human Exploration of Space

Technologies that facilitate the design and control of complex, hybrid, and resource-constrained systems are examined. This paper focuses on design methodologies, and system architectures, not on specific control methods that may be applied to life support subsystems. Honeywell and Boeing have estimated that 60-80Y0 of the effort in developing complex control systems is software development, and only 20-40% is control system development. It has also been shown that large software projects have failure rates of as high as 50-65%. Concepts discussed include the Unified Modeling Language (UML) and design patterns with the goal of creating a self-improving, self-documenting system design process. Successful architectures for control must not only facilitate hardware to software integration, but must also reconcile continuously changing software with much less frequently changing hardware. These architectures rely on software modules or components to facilitate change. Architecting such systems for change leverages the interfaces between these modules or components.

Boulanger, Richard↗
NASA NTRS2005

NASA Earth Sciences Data Support System and Services for the Northern Eurasia Earth Science Partnership Initiative

The presentation describes data management of NASA remote sensing data for Northern Eurasia Earth Science Partnership Initiative (NEESPI). Many types of ground and integrative (e.g., satellite, GIs) data will be needed and many models must be applied, adapted or developed for properly understanding the functioning of Northern Eurasia cold and diverse regional system. Mechanisms for obtaining the requisite data sets and models and sharing them among the participating scientists are essential. The proposed project targets integration of remote sensing data from AVHRR, MODIS, and other NASA instruments on board US- satellites (with potential expansion to data from non-US satellites), customized data products from climatology data sets (e.g., ISCCP, ISLSCP) and model data (e.g., NCEPNCAR) into a single, well-architected data management system. It will utilize two existing components developed by the Goddard Earth Sciences Data & Information Services Center (GES DISC) at the NASA Goddard Space Flight Center: (1) online archiving and distribution system, that allows collection, processing and ingest of data from various sources into the online archive, and (2) user-friendly intelligent web-based online visualization and analysis system, also known as Giovanni. The former includes various kinds of data preparation for seamless interoperability between measurements by different instruments. The latter provides convenient access to various geophysical parameters measured in the Northern Eurasia region without any need to learn complicated remote sensing data formats, or retrieve and process large volumes of NASA data. Initial implementation of this data management system will concentrate on atmospheric data and surface data aggregated to coarse resolution to support collaborative environment and climate change studies and modeling, while at later stages, data from NASA and non-NASA satellites at higher resolution will be integrated into the system.

Leptoukh, Gregory↗
NASA NTRS2004

Systematic Technology Planning: GSFC Perspective

This viewgraph presentation describes the experiences of Goddard Space Flight Center (GSFC) in integrating systematic technology investment planning into the process of architecting NASA space missions. The presentation uses the assessment of a lidar mission as a case study, and illustrates integration strategies through flow charts and dynamic systems models.

Steiner, Mark↗
NASA NTRS2004

The Center Master Plan For NASA Glenn Research Center

The Center Master Plan for NASA Glenn Research Center is a comprehensive survey of NASA Glenn's current facility assets and a vision of how we see the facilities will change over the next 20 years in order to support the changing NASA Mission. This Center Master Plan is a vital management tool used by all organizations for making near term decisions and in future planning. During the summer of 2004, I worked with Joseph Morris, the Chief Architect in the Facilities Division, on beginning this Center Master Planning Process. The previous Master Plan was completed by the Center in 1985 and contained general information on the background of the facility as well as maps detailing environmental and historic records, land use, utilities, etc. The new Master Plan is required for the Center by NASA headquarters and will include similar types of information as used in the past. The new study will provide additional features including showing how individual buildings are linked to the programs and missions that they serve. The Master Plan will show practical future options for the facility s assets with a twenty year look ahead. The Plan will be electronically retrievable so that it becomes a communications tool for Center personnel. A Center Master Plan, although required, is very beneficial to NASA Glenn Research Center in aiding management with the future direction of the campus. Keeping up-to-date information and future plans readily available to all of NASA Glenn will insure that future real property development efficiently and effectively supports the missions camed out and supported by the Center. A Center Master Plan will also facilitate coordination with Center supported programs, stakeholders, and customers. In addition, it will provide a basis for cooperative planning with local and other governmental organizations and ultimately ensure that future budgets include the Center program needs described in the plan. This will ensure that development plans are safe, practical, and cost effective. To properly formulate any future plans, background information and research are required. Before bringing in a consultant to tackle the three year process anticipated to prepare a Center Master Plan, my job was to gather information on different organizations contributions to the NASA mission, their facility needs, consistent trends they observe, etc. I conducted numerous interviews with personnel such as Directorate Representatives, Division Chiefs, Branch Chiefs, System Managers and Building Managers. I documented the information I received from them for future use. I used the information to create various color-coded maps layering the different data. This was done with the ending objective being to collect the information and place it in a database that will be linked with Aperture (a computer program that generates color-coded map layers from database information) and made electronically retrievable to the Planning Consultant, NASA personnel, program stakeholders, and other governmental agencies. My goal this summer was to gather information and ideas appropriate for use in NASA Glenn Research Center s Master Plan and organize them for future application by the Planning Consultant. By the end of the summer, after completion of my goal, I will utilize my knowledge and create an array of preliminary future plans for the facility that can be passed along as a guidance tool.

Bigach, Kristin M.↗
NASA NTRS2005

ASK Magazine; No. 21

THIS ISSUE FEATURES A VISUAL DEPICTION OF THE ACADEMY of Program and Project Leadership (APPL). I imagine a variety of initial reactions to the drawing. One might be, "What is a cartoon doing in a magazine about project management?" Or perhaps, "Wow, nice colors-and fun." Another may be to closely search the image for signs, symbols and meaning. Still another, to read a new level of innovation and creativity into the picture. Undoubtedly, some readers will raise questions about the cost. Of course, any reaction is a sign of engagement. The stronger, the more energized the emotional and cognitive processing, the better. It is a sign of attention and interaction. For I've heard it said, "You only need to worry if they don t care one way or the other." So what is the point of the picture? To stimulate interest, raise questions, promote discussion, and maybe raise a smile.. .That, at least, was my initial reaction when I was introduced to the work of Nancy Hegedus, who helps to create these drawings for Root Learning Inc. At the NASA PM Conference, I was first shown the work Nancy had been doing with the help of Goddard s Knowledge Management Architect, Dr. Ed Rogers. I was immediately drawn into the power of visualization as a tool for more effective learning, communicating, and conveying complex knowledge concepts. We need new tools in today s world, where information and data overwhelms by sheer volume. There are articles, pamphlets, communications, and white papers-all aiming to convince and influence. Reactions to these tend to be either avoidance or mind-numbing, heavy-eyed consent; the message never registers or enters the soul. That s one of the reasons that APPL s Knowledge Sharing Initiative (KSI) has turned to storytelling as a memorable way of transfer- ring knowledge, inspiring imitation of best practices, and spurring reflection. ASK Magazine s recent fourth birthday marks an important milestone in APPL s continuing quest to provide ongoing support to project managers and to promote mission success. And similar to storytelling, the power of visualization is receiving increasing attention in recent years as a way to stimulate engagement. Pictures and visual graphs are viewed as one of the most effective ways for displaying, describing, and generating discussion about quantitative and technically complex information. Prototypes, models, and simulations are considered essential for stimulating innovation through open and engaging discussions. There has also been extensive writing on the use of visual graphics, pictures, and cartoons to facilitate memory, creativity, openness, attention-and even well-being. For many of these reasons, I am excited to have a colorful visual depiction of the APPL world included in ASK. Without the addition of text or slides, the intent is to invite people into the world of the APPL mission-as well as its products, services, customers, and partners- in a fun and engaging manner. As project leaders strive to find ways to encourage engagement, learning, and transmission of knowledge, traditional technologies are proving to be as valuable as modern technologies. (But for those who want more information in the form of texts and slide presentations, we certainly have an abundance of those as well.)

Laufer, Alexander↗
NASA NTRS2006

NASA Earth Sciences Data Support System and Services for the Northern Eurasia Earth Science Partnership Initiative

The presentation describes the recently awarded ACCESS project to provide data management of NASA remote sensing data for the Northern Eurasia Earth Science Partnership Initiative (NEESPI). The project targets integration of remote sensing data from MODIS, and other NASA instruments on board US-satellites (with potential expansion to data from non-US satellites), customized data products from climatology data sets (e.g., ISCCP, ISLSCP) and model data (e.g., NCEP/NCAR) into a single, well-architected data management system. It will utilize two existing components developed by the Goddard Earth Sciences Data & Information Services Center (GES DISC) at the NASA Goddard Space Flight Center: (1) online archiving and distribution system, that allows collection, processing and ingest of data from various sources into the online archive, and (2) user-friendly intelligent web-based online visualization and analysis system, also known as Giovanni. The former includes various kinds of data preparation for seamless interoperability between measurements by different instruments. The latter provides convenient access to various geophysical parameters measured in the Northern Eurasia region without any need to learn complicated remote sensing data formats, or retrieve and process large volumes of NASA data. Initial implementation of this data management system will concentrate on atmospheric data and surface data aggregated to coarse resolution to support collaborative environment and climate change studies and modeling, while at later stages, data from NASA and non-NASA satellites at higher resolution will be integrated into the system.

Leptoukh, Gregory↗
NASA NTRS2006

Generative Representations for Computer-Automated Evolutionary Design

With the increasing computational power of computers, software design systems are progressing from being tools for architects and designers to express their ideas to tools capable of creating designs under human guidance. One of the main limitations for these computer-automated design systems is the representation with which they encode designs. If the representation cannot encode a certain design, then the design system cannot produce it. To be able to produce new types of designs, and not just optimize pre-defined parameterizations, evolutionary design systems must use generative representations. Generative representations are assembly procedures, or algorithms, for constructing a design thereby allowing for truly novel design solutions to be encoded. In addition, by enabling modularity, regularity and hierarchy, the level of sophistication that can be evolved is increased. We demonstrate the advantages of generative representations on two different design domains: the evolution of spacecraft antennas and the evolution of 3D objects.

Hornby, Gregory S.↗
NASA NTRS2005

Structural Analysis Made 'NESSUSary'

Everywhere you look, chances are something that was designed and tested by a computer will be in plain view. Computers are now utilized to design and test just about everything imaginable, from automobiles and airplanes to bridges and boats, and elevators and escalators to streets and skyscrapers. Computer-design engineering first emerged in the 1970s, in the automobile and aerospace industries. Since computers were in their infancy, however, architects and engineers during the time were limited to producing only designs similar to hand-drafted drawings. (At the end of 1970s, a typical computer-aided design system was a 16-bit minicomputer with a price tag of $125,000.) Eventually, computers became more affordable and related software became more sophisticated, offering designers the "bells and whistles" to go beyond the limits of basic drafting and rendering, and venture into more skillful applications. One of the major advancements was the ability to test the objects being designed for the probability of failure. This advancement was especially important for the aerospace industry, where complicated and expensive structures are designed. The ability to perform reliability and risk assessment without using extensive hardware testing is critical to design and certification. In 1984, NASA initiated the Probabilistic Structural Analysis Methods (PSAM) project at Glenn Research Center to develop analysis methods and computer programs for the probabilistic structural analysis of select engine components for current Space Shuttle and future space propulsion systems. NASA envisioned that these methods and computational tools would play a critical role in establishing increased system performance and durability, and assist in structural system qualification and certification. Not only was the PSAM project beneficial to aerospace, it paved the way for a commercial risk- probability tool that is evaluating risks in diverse, down- to-Earth application

Source record↗
NASA NTRS2002

Making Sense of Rocket Science - Building NASA's Knowledge Management Program

The National Aeronautics and Space Administration (NASA) has launched a range of KM activities-from deploying intelligent "know-bots" across millions of electronic sources to ensuring tacit knowledge is transferred across generations. The strategy and implementation focuses on managing NASA's wealth of explicit knowledge, enabling remote collaboration for international teams, and enhancing capture of the key knowledge of the workforce. An in-depth view of the work being done at the Jet Propulsion Laboratory (JPL) shows the integration of academic studies and practical applications to architect, develop, and deploy KM systems in the areas of document management, electronic archives, information lifecycles, authoring environments, enterprise information portals, search engines, experts directories, collaborative tools, and in-process decision capture. These systems, together, comprise JPL's architecture to capture, organize, store, and distribute key learnings for the U.S. exploration of space.

knowledge management organizational learning NASA ↗
NASA NTRS2005

Architectural prospects for lunar mission support

A top-level architectural approach facilitates the provision of communications and navigation support services to the anticipated lunar mission set. Following the time-honored principles of systems architecting, i.e., form follows function, the first step is to define the functions or services to be provided, both in terms of character and degree. These will include communication as well as trackin and navigation services.

communications↗
NASA NTRS2005

A model to assess the Mars Telecommunications Network relay robustness

The relatively long mission durations and compatible radio protocols of current and projected Mars orbiters have enabled the gradual development of a heterogeneous constellation providing proximity communication services for surface assets. The current and forecasted capability of this evolving network has reached the point that designers of future surface missions consider complete dependence on it. Such designers, along with those architecting network requirements, have a need to understand the robustness of projected communication service. A model has been created to identify the robustness of the Mars Network as a function of surface location and time. Due to the decade-plus time horizon considered, the network will evolve, with emerging productive nodes and nodes that cease or fail to contribute. The model is a flexible framework to holistically process node information into measures of capability robustness that can be visualized for maximum understanding. Outputs from JPL's Telecom Orbit Analysis Simulation Tool (TOAST) provide global telecom performance parameters for current and projected orbiters. Probabilistic estimates of orbiter fuel life are derived from orbit keeping burn rates, forecasted maneuver tasking, and anomaly resolution budgets. Orbiter reliability is estimated probabilistically. A flexible scheduling framework accommodates the projected mission queue as well as potential alterations.

Mars Telecommunications Orbiter (MTO)↗
NASA NTRS2006

NASA Langley Research Center Systems Analysis & Concepts Directorate Participation in the Exploration Systems Architecture Study

The NASA Langley Research Center (LaRC) Systems Analysis & Concepts Directorate (SACD) began studying human exploration missions beyond low Earth orbit (LEO) in the year 1999. This included participation in NASA s Decadal Planning Team (DPT), the NASA Exploration Team (NExT), Space Architect studies and Revolutionary Aerospace Systems Concepts (RASC) architecture studies that were used in formulating the new Vision for Space Exploration. In May of 2005, NASA initiated the Exploration Systems Architecture Study (ESAS). The primary outputs of the ESAS activity were concepts and functional requirements for the Crewed Exploration Vehicle (CEV), its supporting launch vehicle infrastructure and identification of supporting technology requirements and investments. An exploration systems analysis capability has evolved to support these functions in the past and continues to evolve to support anticipated future needs. SACD had significant roles in supporting the ESAS study team. SACD personnel performed the liaison function between the ESAS team and the Shuttle/Station Configuration Options Team (S/SCOT), an agency-wide team charged with using the Space Shuttle to complete the International Space Station (ISS) by the end of Fiscal Year (FY) 2010. The most significant of the identified issues involved the ability of the Space Shuttle system to achieve the desired number of flights in the proposed time frame. SACD with support from the Kennedy Space Center performed analysis showing that, without significant investments in improving the shuttle processing flow, that there was almost no possibility of completing the 28-flight sequence by the end of 2010. SACD performed numerous Lunar Surface Access Module (LSAM) trades to define top level element requirements and establish architecture propellant needs. Configuration trades were conducted to determine the impact of varying degrees of segmentation of the living capabilities of the combined descent stage, ascent stage, and other elements. The technology assessment process was developed and implemented by SACD as the ESAS architecture was refined. SACD implemented a rigorous and objective process which included (a) establishing architectural functional needs, (b) collection, synthesis and mapping of technology data, and (c) performing an objective decision analysis resulting in technology development investment recommendations. The investment recommendation provided budget, schedule, and center/program allocations to develop required technologies for the exploration architecture, as well as the identification of other investment opportunities to maximize performance and flexibility while minimizing cost and risk. A summary of the trades performed and methods utilized by SACD for the Exploration Systems Mission Directorate (ESAS) activity is presented along with how SACD is currently supporting the implementation of the Vision for Space Exploration.

Keyes, Jennifer↗
NASA NTRS1978

Solar Meter

The instrument pictured is an inexpensive solar meter which is finding wide acceptance among architects, engineers and others engaged in construction of solar energy facilities. It detects the amount of solar energy available at a building site, information necessary to design the most efficient type of solar system for a particular location. Incorporating technology developed by NASA's Lewis Research Center, the device is based upon the solar cell, which provides power for spacecraft by converting the sun's energy to electricity. The meter is produced by Dodge Products, Inc., Houston, Texas, a company formed to bring the technology to the commercial marketplace.

Source record↗
NASA NTRS2004

The Pulse Width Modulator ASIC for Deep Space Missions

The Jet Propulsion Laboratory has started the development of a Pulse Width Modulator Application Specific Integrated Circuit (PWMA). This development is leveraging the previous development of the Switch Control ASIC (SCA). The purpose of the development is to provide the control for a selected range of power converter topologies and to meet the stringent environmental requirements of deep space missions. The PWMA will include several power control functions that are not normally included on the off-the-shelf components available today. One key functional requirement is the ability to implement an N + K redundant power converter with the ability to control the charging of a battery. Other applications will be the typical point of load isolated and non-isolated power converters. The purpose the development is not only to provide a much needed flight part, but also to accelerate the engineering process by using a standard cell library from previous ASIC developments. Under previous developments with Boeing and Lockheed Martin, JPL has produced three ASICs. Each ASIC has been implemented by using an analog standard cell library. One such development was the SCA, which is design to provide a floating power switch control. The functional verification of this ASIC has been completed and the cells used have been targeted for the new development of the PWMA. The primary function of the PWMA is to provide the control function of a point of load power converter. The design is an isolated 60 W converter with a 33 V output. In architecting the design, several functions were left up to the power converter design in order to make the ASIC more generic. The ASIC can be used for several power converter topologies and power levels. Some additional features have been added to the ASIC to provide the interfaces for multi-phase topologies and battery control functions. An N+K fault tolerant strategy has been implemented in order to provide the battery control functions. The PWMA has been developed to provide an ASIC with several functions not normally available in the off the shelf controllers. These functions have been added to enable the power converter designers to achieve fault tolerant designs and battery control functions.

Pulse Width Modulator Application Specific Integra↗
NASA NTRS2008

In-situ Resource Utilization (ISRU) to Support the Lunar Outpost and the Rationale for Precursor Missions

One of the ways that the Constellation Program can differ from Apollo is to employ a live-off-the-land or In-Situ Resource Utilization (ISRU) supported architecture. The options considered over the past decades for using indigenous materials have varied considerably in terms of what resources to attempt to acquire, how much to acquire, and what the motivations are to acquiring these resources. The latest NASA concepts for supporting the lunar outpost have considered many of these plans and compared these options to customers requirements and desires. Depending on the architecture employed, ISRU technologies can make a significant contribution towards a sustainable and affordable lunar outpost. While extensive ground testing will reduce some mission risk, one or more flight demonstrations prior to the first crew's arrival will build confidence and increase the chance that outpost architects will include ISRU as part of the early outpost architecture. This presentation includes some of the options for using ISRU that are under consideration for the lunar outpost, the precursor missions that would support these applications, and a notional timeline to allow the lessons learned from the precursor missions to support outpost hardware designs.

Simon, Thomas M.↗
NASA NTRS2007

Mars Reconnaissance Orbiter Mission: Systems Engineering Challenges on the Mars Reconnaissance Orbiter Mission

MRO project is a system of systems requiring system engineering team to architect, design, integrate, test, and operate these systems at each level of the project. The challenge of system engineering mission objectives into a single mission architecture that can be integrated tested, launched, and operated. Systems engineering must translate high-level requirements into integrated mission design. Systems engineering challenges were overcome utilizing a combination by creative designs built into MRO's flight and ground systems: a) Design of sophisticated spacecraft targeting and data management capabilities b) Establishment of a strong operations team organization; c) Implementation of robust operational processes; and d) Development of strategic ground tools. The MRO system has met the challenge of its driving requirements: a) MRO began its two-year primary science phase on November 7, 2006, and by July 2007, met it minimum requirement to collect 15 Tbits of data after only eight months of operations. Currently we have collected 22 Tbits. b) Based on current performance, mission data return could return 70 Tbits of data by the end of the primary science phase in 2008.

systems engineering↗