Earth resources technology satellites. Volume 9 - Configuration management plan Final report
Configuration management plan for Earth Resources Technology Satellite
SEARCH · Search NASA
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.
Configuration management plan for Earth Resources Technology Satellite
SEPAC Software Configuration Control Plan and Procedures are presented. The objective of the software configuration control is to establish the process for maintaining configuration control of the SEPAC software beginning with the baselining of SEPAC Flight Software Version 1 and encompass the integration and verification tests through Spacelab Level IV Integration. They are designed to provide a simplified but complete configuration control process. The intent is to require a minimum amount of paperwork but provide total traceability of SEPAC software.
The payload development support system (PDSS) configuration control plan and procedures are presented. These plans and procedures establish the process for maintaining configuration control of the PDSS system, especially the Spacelab experiment interface device's (SEID) RAU, HRM, and PDI interface simulations and the PDSS ECOS DEP Services simulation. The plans and procedures as specified are designed to provide a simplified but complete configuration control process. The intent is to require a minimum amount of paperwork but provide total traceability of PDSS during experiment test activities.
This is the configuration management Plan for the AdaNet Repository Based Software Engineering (RBSE) contract. This document establishes the requirements and activities needed to ensure that the products developed for the AdaNet RBSE contract are accurately identified, that proposed changes to the product are systematically evaluated and controlled, that the status of all change activity is known at all times, and that the product achieves its functional performance requirements and is accurately documented.
This plan describes methods and procedures Aerojet will follow in the implementation of configuration control for each established baseline. The plan is written in response to the GSFC EOS CM Plan 420-02-02, dated January 1990, and also meets he requirements specified in DOD-STD-480, DOD-D 1000B, MIL-STD-483A, and MIL-STD-490B. The plan establishes the configuration management process to be used for the deliverable hardware, software, and firmware of the EOS/AMSU-A during development, design, fabrication, test, and delivery. This revision includes minor updates to reflect Aerojet's CM policies.
This Standard Operating Procedure (SOP) describes the requirements and methodology for preparation of an Operation & Configuration Control Plan (OCCP) as required by JPR 1710.13 to assure safe ground pressurization and pressurization during aircraft operations of “Category B” Pressure Vessels/Systems (PV/S) at Johnson Space Center (JSC), Ellington Field (EFD) and associated NASA spaceflight/aircraft operations facilities. An OCCP is a written assessment showing that a “Category B” PV/S is safe for ground pressurization and pressurization during aircraft operations, within the bounds established by the OCCP.
The tools and methods used for the configuration management of the artifacts (including software and documentation) associated with the Guidance and Control Software (GCS) project are described. The GCS project is part of a software error studies research program. Three implementations of GCS are being produced in order to study the fundamental characteristics of the software failure process. The Code Management System (CMS) is used to track and retrieve versions of the documentation and software. Application of the CMS for this project is described and the numbering scheme is delineated for the versions of the project artifacts.
The purpose of this plan is to identify the baseline to be established during the development life cycle of the integrated AMSU-A, and define the methods and procedures which Aerojet will follow in the implementation of configuration control for each established baseline. Also this plan establishes the Configuration Management process to be used for the deliverable hardware, software, and firmware of the Integrated AMSU-A during development, design, fabrication, test, and delivery.
The Crystal Growth Furnace (CGF) system configuration for the First United States Microgravity Laboratory (USML-1) mission is reviewed, and the planned on-orbit experiments are briefly described. The CGF is configured to accommodate four scientific experiments involving crystal growth which are based on the classical Bridgman method and CVT method, including vapor transport crystal growth of mercury cadmium telluride; crystal growth of mercury zinc telluride by directional solidification; seeded Bridgman growth of zinc-doped cadmium telluride; and Bridgman growth of selenium-doped gallium arsenide.
A preflight analysis of the ALT separation reference trajectories for the tailcone on, forward, and aft cg orbiter configurations is documented. The ALT separation reference trajectories encompass the time from physical separation of the orbiter from the carrier to orbiter attainment of the maximum ALT interface airspeed. The trajectories include post separation roll maneuvers by both vehicles and are generated using the final preflight data base. The trajectories so generated satisfy all known separation design criteria and violate no known constraints. The requirement for this analysis is given along with the specifications, assumptions, and analytical approach used to generate the separation trajectories. The results of the analytical approach are evaluated, and conclusions and recommendations are summarized.
Attention is given to the Crystal Growth Furnace (CGF) currently in the Level IV integration cycle at the Kennedy Space Center in preparation for its maiden flight on the first United States Microgravity Laboratory (USML-1) mission to be launched in May 1992. CGF was developed for NASA under the Microgravity Science and Application division programs at NASA Headquarters. An overview of the CGF system and the system configuration for the USML-1 mission are presented, and the planned on-orbit experiments are described. The four important scientific experiments selected from industry and educational institutions for the CGF USML-1 mission will enable a better understanding of the complex phenomena inherent in materials processing that will lead to the ultimate improvement of both processes and materials. Crystal growth by chemical vapor transport has resulted in improved growth conditions with crystal morphology, lower defect densities, and higher growth rates than terrestrially observed.
The Crystal Growth Furnace (CGF) is currently undergoing modifications and refurbishment and is currently undergoing modifications and refurbishment and is manifested to refly on the Second United States Microgravity Laboratory (USML-2) mission scheduled for launch in September 1995. The CGF was developed for the National Aeronautics and Space Administration (NASA) under the Microgravity Science and Applications Division (MSAD) programs at NASA Headquarters. The refurbishment and reflight program is being managed by the Marshall Space Flight Center (MSFC) in Huntsville, Alabama. Funding and program support for the CGF project is provided to MSFC by the office of Life and Microgravity Sciences and Applications at NASA Headquarters. This paper presents an overview of the CGF system configuration for the USML-2 mission, and provides a brief description of the planned on-orbit experiment operation.
Methods for evaluating and implementing air traffic management tools and approaches for managing and avoiding an air traffic incident before the incident occurs. A first system receives parameters for flight plan configurations (e.g., initial fuel carried, flight route, flight route segments followed, flight altitude for a given flight route segment, aircraft velocity for each flight route segment, flight route ascent rate, flight route descent route, flight departure site, flight departure time, flight arrival time, flight destination site and/or alternate flight destination site), flight plan schedule, expected weather along each flight route segment, aircraft specifics, airspace (altitude) bounds for each flight route segment, navigational aids available. The invention provides flight plan routing and direct routing or wind optimal routing, using great circle navigation and spherical Earth geometry. The invention provides for aircraft dynamics effects, such as wind effects at each altitude, altitude changes, airspeed changes and aircraft turns to provide predictions of aircraft trajectory (and, optionally, aircraft fuel use). A second system provides several aviation applications using the first system. Several classes of potential incidents are analyzed and averted, by appropriate change en route of one or more parameters in the flight plan configuration, as provided by a conflict detection and resolution module and/or traffic flow management modules. These applications include conflict detection and resolution, miles-in trail or minutes-in-trail aircraft separation, flight arrival management, flight re-routing, weather prediction and analysis and interpolation of weather variables based upon sparse measurements. The invention combines these features to provide an aircraft monitoring system and an aircraft user system that interact and negotiate changes with each other.
The Los Alamos Neutron Science Center (LANSCE) is located at Technical Area 53 (TA-53) at Los Alamos National Laboratory (LANL) in Los Alamos, New Mexico. LANSCE is driven by an 800 megaelectronvolt (MeV) proton accelerator that delivered its first beam in 1972. The LANSCE accelerator is unique in that it accelerates both H– (to full energy of 800 MeV) and H+ ions (up to 100 MeV currently but has accelerated high-power H+ beam to 800 MeV in the past) and supports five separate experimental areas that operate simultaneously, with each having different timing and beam current requirements. Many of the LANSCE accelerator front-end components date back to original commissioning in 1972, including the ion sources, Cockcroft-Walton (CW) generators, and the Drift Tube LINAC (DTL), which accelerates the beam up to 100 MeV.
Explore the source record for details and available documents.
A model of Univac 1108 work flow has been developed to assist in performance evaluation studies and configuration planning. Workload profiles and system configurations are parameterized for ease of experimental modification. Outputs include capacity estimates and performance evaluation functions. The U1108 system is conceptualized as a service network; classical queueing theory is used to evaluate network dynamics.
The research accomplishments for the cooperative agreement 'Online Learning Flight Control for Intelligent Flight Control Systems (IFCS)' include the following: (1) previous IFC program data collection and analysis; (2) IFC program support site (configured IFC systems support network, configured Tornado/VxWorks OS development system, made Configuration and Documentation Management Systems Internet accessible); (3) Airborne Research Test Systems (ARTS) II Hardware (developed hardware requirements specification, developing environmental testing requirements, hardware design, and hardware design development); (4) ARTS II software development laboratory unit (procurement of lab style hardware, configured lab style hardware, and designed interface module equivalent to ARTS II faceplate); (5) program support documentation (developed software development plan, configuration management plan, and software verification and validation plan); (6) LWR algorithm analysis (performed timing and profiling on algorithm); (7) pre-trained neural network analysis; (8) Dynamic Cell Structures (DCS) Neural Network Analysis (performing timing and profiling on algorithm); and (9) conducted technical interchange and quarterly meetings to define IFC research goals.
Document Configuration Management (DCM) is the ongoing process of identifying and managing changes to deliverables and other work products. ALDW’s Document Configuration Plan provides a systematic, standardized process for the configuration management of documents to ensure that the most current and/or appropriate documents are being used, that any canceled or superseded document is properly processed, and that both a clear history and traceability of previous revisions are available.