Search NASA⌕ Search

SEARCH · Search NASA

Results for “Implementation Plan”

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 91 records · Page 5

Factors Influencing the Selection of the Systems Integration Organizational Model Type for Planning and Implementing Government High-Technology Programs

While there has been extensive research in defining project organizational structures for traditional projects, little research exists to support high technology government project s organizational structure definition. High-Technology Government projects differ from traditional projects in that they are non-profit, span across Government-Industry organizations, typically require significant integration effort, and are strongly susceptible to a volatile external environment. Systems Integration implementation has been identified as a major contributor to both project success and failure. The literature research bridges program management organizational planning, systems integration, organizational theory, and independent project reports, in order to assess Systems Integration (SI) organizational structure selection for improving the high-technology government project s probability of success. This paper will describe the methodology used to 1) Identify and assess SI organizational structures and their success rate, and 2) Identify key factors to be used in the selection of these SI organizational structures during the acquisition strategy process.

Thomas, Leann↗

Space Station redesign option A: Modular buildup concept

In early 1993, President Clinton mandated that NASA look at lower cost alternatives to Space Station Freedom. He also established an independent advisory committee - the Blue Ribbon Panel - to review the redesign work and evaluate alternatives. Daniel Goldin, NASA Administrator, established a Station Redesign Team that began operating in late March from Crystal City, Virginia. NASA intercenter teams - one each at Marshall Space Flight Center, Johnson Space Center, and Langley Research Center provided engineering and other support. The results of the Option A study done at Marshall Space Flight Center are summarized. Two configurations (A-1 and A-2) are covered. Additional data is provided in the briefing package MSFC SRT-001, Final System Review to SRT-002, Space Station Option A Modular Buildup Concept, Volumes 1-5, Revision B, June 10, 1993. In June 1993, President Clinton decided to proceed with a modular concept consistent with Option A, and asked NASA to provide an Implementation Plan by September. All data from the Option A redesign activity was provided to NASA's Transition Team for use in developing the Implementation Plan.

Source record↗

Software engineering and Ada (Trademark) training: An implementation model for NASA

The choice of Ada for software engineering for projects such as the Space Station has resulted in government and industrial groups considering training programs that help workers become familiar with both a software culture and the intricacies of a new computer language. The questions of how much time it takes to learn software engineering with Ada, how much an organization should invest in such training, and how the training should be structured are considered. Software engineering is an emerging, dynamic discipline. It is defined by the author as the establishment and application of sound engineering environments, tools, methods, models, principles, and concepts combined with appropriate standards, guidelines, and practices to support computing which is correct, modifiable, reliable and safe, efficient, and understandable throughout the life cycle of the application. Neither the training programs needed, nor the content of such programs, have been well established. This study addresses the requirements for training for NASA personnel and recommends an implementation plan. A curriculum and a means of delivery are recommended. It is further suggested that a knowledgeable programmer may be able to learn Ada in 5 days, but that it takes 6 to 9 months to evolve into a software engineer who uses the language correctly and effectively. The curriculum and implementation plan can be adapted for each NASA Center according to the needs dictated by each project.

Legrand, Sue↗

Introduction to: Atlantic Meridional Overturning Circulation(AMOC)

A striking conclusion of the Intergovernmental Panel on Climate Change 2007 report is the crucial role that the Atlantic Meridional Overturning Circulation (AMOC) may play in anthropogenic climate change. However, these IPCC coupled climate simulations show a broad range of uncertainty in the magnitude and timing of AMOC transport change ranging from none to nearly complete collapse within the 21st century. The potential consequences of large changes in the characteristics of AMOC have motivated the creation in the United States of an interagency program and implementation plan to develop monitoring and prediction capabilities for the AMOC This program parallels the development of substantial monitoring efforts by European, South American and African countries -- notably the UK Rapid and Rapid-Watch programs. The papers contained in this volume are derived from presentations at the First U.S. Atlantic Meridional Overturning Circulation (AMOC) Meeting held 4 - 6 May, 2009 to review the US implementation plan and its coordination with other monitoring activities. The Atlantic Meridional Overturning Circulation consists of multiple components illustrated in an attached figure. Water enters the South Atlantic at upper and intermediate depths through both western and eastern routes (where eddy transport is especially important) and is transported northward across the equator, where it recirculates within the northern subtropical and subpolar gyres. The northern end is defined by the sinking regions of the Nordic Seas and the Labrador Sea where the waters that eventually form the upper and lower branches of North Atlantic Deep Water are conditioned. High surface salinities, the result of high net evaporation in the tropics and subtropics (including the Mediterranean Sea), and presence of regions of the Arctic Ocean that remain ice-free even in winter allow for the rapid cooling and thus densification of surface water. This dense surface water becomes the source of deep water formation in the sinking regions. In addition to transporting mass, the AMOC transports roughly half of the total amount of heat carried northward through the northern subtropics (down the temperature-gradient) by the ocean. In contrast in the Southern Hemisphere AMOC transports heat up-gradient from the cool Circumpolar Current to the warm tropics. Paleoevidence suggests that AMOC heat transport in the two hemispheres has varied over time in ways intimately tied to millennial changes in the Earth's climate. In one example, the abrupt Younger Dryas spell of cold weather over the North Atlantic, which began 13,000 years ago, has generally been linked to a millennial shutdown of the AMOC as a result of massive freshwater discharge from the North American continent. The current AMOC monitoring array consists of a series of instrumented transects located across key passages (see Cunningham et al., 2010 for a recent review). In the Arctic and sub-Arctic, transects cross Fram Strait, Denmark Strait and the Faroe Channel (connecting Greenland, Iceland, and the United Kingdom), as well as the entrance to the Labrador Sea. Further south and extending outwards from the east coast of North America there are a series of monitoring arrays including arrays of the Canadian Atlantic Zone Monitoring Program, deployments of the Rapid Western Atlantic Variability Experiment (WAVE), Line W at 39 N, as well as the Rapid-MOC moored array. The latter spans the entire Atlantic basin along 26.5 N. At tropical latitudes we have the Meridional Overturning Variability Experiment (MOVE) array at 16 N, while in the Southern Hemisphere a corresponding basin-spanning transect is being established at the latitude of Cape of Good Hope, complemented by arrays at Drake Passage.

Hakkinen, Sirpa↗

Central station market development strategies for photovoltaics

Federal market development strategies designed to accelerate the market penetration of central station applications of photovoltaic energy system are analyzed. Since no specific goals were set for the commercialization of central station applications, strategic principles are explored which, when coupled with specific objectives for central stations, can produce a market development implementation plan. The study includes (1) background information on the National Photovoltaic Program, photovoltaic technology, and central stations; (2) a brief market assessment; (3) a discussion of the viewpoints of the electric utility industry with respect to solar energy; (4) a discussion of commercialization issues; and (5) strategy principles. It is recommended that a set of specific goals and objectives be defined for the photovoltaic central station program, and that these goals and objectives evolve into an implementation plan that identifies the appropriate federal role.

Source record↗

Phase 2 STS new user development program. Volume 1: Executive summary

A methodology for developing new users for STS other than NASA and DoD, thereby maximizing the use of the STS system was developed. The approach to user development, reflected in the implementation plan, and attendant informational material to be used were evaluated by conducting a series of test cases with selected user organizations. These test case organizations were, in effect, used as consultants to evaluate the effectiveness, the needs, the completeness, and the adequacy of the user development approach and informational material. The selection of the test cases provided a variety of potential STS users covering industry, other government agencies, and the educational sector. The test cases covered various use areas and provided a mix of user organization types. A summary of the actual test cases conducted is given. The conduct of the test cases verified the general approach of the implementation plan, the validity of the user development strategy prepared for each test case organization and the effectiveness of the STS basic and user customized informational material.

Mcdowell, J. R.↗

Mission to Planet Earth. Strategic enterprise plan, 1995-2000

Mission to Planet Earth (MTPE) provides long-term understanding of the earth system needed to protect and improve our environment, now and for future generations. This MTPE Strategic Enterprise Plan states how NASA intends to meet its responsibility to the Nation for developing a long-term, integrated program of environmental observation in support of informed decision-making. This plan implements the NASA Strategic Plan for the MTPE Enterprise; it is the first version of a rolling 5-year plan that will be updated annually. It is consistent with the interagency program developed by the Committee on Environment and Natural Resources of the National Science and Technology Council and implemented in large part through the U.S. Global Change Research Program. This report consists of the following sections: (1) introduction; (2) scientific foundation; (3) mission (destination and purposes); (4) principle of operation (ethical and quality assurance standards); (5) customer base (to ensure that the right products and services are delivered); (6) internal and external assessments; (7) assumptions; (8) goals, objectives, and strategies; (9) linkages to other strategic enterprises; and (10) summary.

Source record↗

NASA/ESA CV-990 Spacelab simulation. Appendixes: C, data-handling: Planning and implementation; D, communications; E, mission documentation

Data handling, communications, and documentation aspects of the ASSESS mission are described. Most experiments provided their own data handling equipment, although some used the airborne computer for backup, and one experiment required real-time computations. Communications facilities were set up to simulate those to be provided between Spacelab and the ground, including a downlink TV system. Mission documentation was kept to a minimum and proved sufficient. Examples are given of the basic documents of the mission.

Reller, J. O., Jr.↗

NASA-evolving to Ada: Five-year plan. A plan for implementing recommendations made by the Ada and software management assessment working group

At their March 1988 meeting, members of the National Aeronautics and Space Administration (NASA) Information Resources Management (IRM) Council expressed concern that NASA may not have the infrastructure necessary to support the use of Ada for major NASA software projects. Members also observed that the agency has no coordinated strategy for applying its experiences with Ada to subsequent projects (Hinners, 27 June 1988). To deal with these problems, the IRM Council chair appointed an intercenter Ada and Software Management Assessment Working Group (ASMAWG). They prepared a report (McGarry et al., March 1989) entitled, 'Ada and Software Management in NASA: Findings and Recommendations'. That report presented a series of recommendations intended to enable NASA to develop better software at lower cost through the use of Ada and other state-of-the-art software engineering technologies. The purpose here is to describe the steps (called objectives) by which this goal may be achieved, to identify the NASA officials or organizations responsible for carrying out the steps, and to define a schedule for doing so. This document sets forth four goals: adopt agency-wide software standards and policies; use Ada as the programming language for all mission software; establish an infrastructure to support software engineering, including the use of Ada, and to leverage the agency's software experience; and build the agency's knowledge base in Ada and software engineering. A schedule for achieving the objectives and goals is given.

Source record↗

Overview of the Solar-B Mission

The Solar-B mission is a collaboration between the Japan Aerospace Exploration Agency, Institute of Space and Astronautical Science, the National Aeronautics and Space Administration (NASA) and the Particle Physics and Astronomy Research Council (PPARC) of the United Kingdom and the European Space Agency. The principal scientific goals of the mission are to understand the processes of magnetic field generation, transport and ultimate dissipation of solar magnetic fields and how the release of magnetic energy is responsible for the heating and structuring of the chromosphere and corona. The scientific payload consists of three instruments: the Solar Optical Telescope that consists of the Optical Telescope Assembly and the Focal Plane Package (FPP), the X-ray Telescope and the EUV Imaging Spectrometer Each instrument is a result of the combined talents of all the members of the international team and their design and performance is described in separate papers in this session. The instruments are designed to work together as an 'observatory' simultaneously studying the target, at which the spacecraft is pointed, at different levels in the atmosphere. The spacecraft is scheduled for launch in September 2006 from the Uchinoura Space Center into a 600 km circular, sun-synchronous, polar orbit with a nominal elevation of 97.9 degrees. The orbit provides at least two morning and two evening contacts in Japan. Morning contacts are used for recovering quick look science data and the evening contacts for uploading commands. In addition ESA will provide 15 contacts per day from the Norwegian high latitude (78deg 14' N) ground station at Svalbard. The data downloads are transmitted to the ISAS Sirius database. They will be reformatted into FITS files and archived as Level 0 data on the ISAS DARTS system and made available to the scientific community. Scientific operations will be conducted from the IS AS facility located in Sagamihara, Japan. They are separated into planning, implementation and archiving. The planning process involves monthly, weekly and daily planning meetings. All scientific data will be made available after the first six month approximately one week after its collection.

Davis, John M.↗

The Planning and Implementation of Test Facility Improvements

As engineering programs develop, and product testing begins, ideas for process improvement soon become obvious. Engineers envision new holding and handling fixtures. Additional custom-made support equipment may be needed. Perhaps modifications to the building or modifications to facility hardware are the order of the day. This is where a flexible creative test organization is needed. We need not be content with the status quo. All of these desired test innovations can make the difficult easy and improve the work flow. At times, implementing these new ideas demands more time or specialized expertise than test team members have. Through the coordinated use of labor resources, the needed improvements can still be made and in a timely fashion that supports program schedules. This presentation provides practical advice and a method whereby test personnel can creatively develop facility improvements and manage them from start to finish. You can control just how much time you invest and what part of your concepts you will personally design. By wisely defining the requirements and presenting them to the appropriate help sources (vendors, contractors, coworkers, and support departments), you can get the help you need to bring the improvements you have conceived, into fruition. Aspects of this presentation include defining requirements for test facility improvements, choosing labor resources, writing a statement of work, determining cost and benefits, securing department approval, coordinating procurement, managing the project, and training the end users. The process of successfully implementing test facility improvements is thoroughly explained. It has been tried, proven and improved over nearly 25 years of use. Whether considering a $50 improvement or a $50 million dollar improvement, this discussion will provide helpful pointers. Examples of improvements made through this process and their illustration will be included.

Oberlander, Larry↗

Implementing Strategic Planning Capabilities Within the Mars Relay Operations Service

Throughout this development and deployment process we have followed a few guiding principles: (1) Ensure ubiquitous access through ReSTful and web interfaces; (2) Design a system that is mission and even planet agnostic so that future missions may be added with little hassle, and the system itself may be redeployed for other planetary relay networks; (3) Accept constant input and feedback between mission operators and the development team to ensure that there is a useful product that may be used for years to come.

software development↗

Implementing Strategic Planning Capabilities Within the Mars Relay Operations Service

Since the Mars Exploration Rovers (MER), Spirit and Opportunity, began their travels across the Martian surface in January of 2004, orbiting spacecraft such as the Mars 2001 Odyssey orbiter have relayed the majority of their collected scientific and operational data to and from Earth. From the beginning of those missions, it was evident that using orbiters to relay data to and from the surface of Mars was a vastly more efficient communications strategy in terms of power consumption and bandwidth compared to direct-to-Earth means. However, the coordination between the various spacecraft, which are largely managed independently and on differing commanding timelines, has always proven to be a challenge. Until recently, the ground operators of all these spacecraft have coordinated the movement of data through this network using a collection of ad hoc human interfaces and various, independent software tools. The Mars Relay Operations Service (MaROS) has been developed to manage the evolving needs of the Mars relay network, and specifically to standardize and integrate the relay planning and coordination data into a centralized infrastructure. This paper explores the journey of developing the MaROS system, from inception to delivery and acceptance by the Mars mission users.

tactical planning↗

GOES-R L1b Readiness Implementation and Management Plan

A complement of Readiness, Implementation and Management Plans (RIMPs) to facilitate management of post-launch product test activities for the official Geostationary Operational Environmental Satellite (GOES-R) Level 1b (L1b) products have been developed and documented. Separate plans have been created for each of the GOES-R sensors including: the Advanced Baseline Imager (ABI), the Extreme ultraviolet and X-ray Irradiance Sensors (EXIS), Geostationary Lightning Mapper (GLM), GOES-R Magnetometer (MAG), the Space Environment In-Situ Suite (SEISS), and the Solar Ultraviolet Imager (SUVI). The GOES-R program has implemented these RIMPs in order to address the full scope of CalVal activities required for a successful demonstration of GOES-R L1b data product quality throughout the three validation stages: Beta, Provisional and Full Validation. For each product maturity level, the RIMPs include specific performance criteria and required artifacts that provide evidence a given validation stage has been reached, the timing when each stage will be complete, a description of every applicable Post-Launch Product Test (PLPT), roles and responsibilities of personnel, upstream dependencies, and analysis methods and tools to be employed during validation. Instrument level Post-Launch Tests (PLTs) are also referenced and apply primarily to functional check-out of the instruments.

Validation Readiness↗

Liquid rocket booster study. Volume 2, book 3, appendices 2-5: PPIP, transition plan, AMOS plan, and environmental analysis

This Preliminary Project Implementation Plan (PPIP) was used to examine the feasibility of replacing the current Solid Rocket Boosters on the Space Shuttle with Liquid Rocket Boosters (LRBs). The need has determined the implications of integrating the LRB with the Space Transportation System as the earliest practical date. The purpose was to identify and define all elements required in a full scale development program for the LRB. This will be a reference guide for management of the LRB program, addressing such requirement as design and development, configuration management, performance measurement, manufacturing, product assurance and verification, launch operations, and mission operations support.

Source record↗

High performance processors for real-time flight simulation

In order to meet the requirements of the NASA Langley Research Center for simulating the increased complexity and higher performance of modern aircraft, a flight simulation computing system with very high scalar performance is needed. The requirements and proposed response, probable areas of difficulty, planned implementation, and current status and plans are reviewed. A solution utilizing centralized minisupercomputers coupled with a proven real-time network technology will provide engineers and research scientists with the tools required for high-performance flight simulation. Subsequent to testing and verification of the initial simulation, general-purpose configuration management software with a nonconfiguration dependent serial highway driver software will be integrated to support any arbitrary combination of simulation sites.

Cleveland, Jeff I., II↗