Results for “configuration management” — Page 14

NASA NTRSDate not supplied

Autonomous Robotic Manipulator Software

Autonomous robotic manipulation requires a deep and wide stack of supporting software. This paper presents Autonomous Robotic Manipulator Software (ARMS), a software suite designed at NASA Langley Research Center to support research and development of different algorithms for In-space Servicing, Assembly and Manufacturing (ISAM). ARMS solves common challenges along the autonomous manipulation software stack. Various challenges, such as integration with commercial hardware, simulation, and path planning, are solved through the use of Robot Operating System 2 and its community-developed packages. Other challenges, such as configuration management and task definition, and execution are solved in software built on those tools. The result is a modular approach to robotic system definition, agent actions, and assembly task definitions. ARMS has been used in two ISAM projects at NASA Langley Research Center, the Precision Assembled Space Structures project and the Built On-orbit Robotically assembled Gigatruss project.

Collin J Cresta↗

NASA NTRSDate not supplied

Autonomous Robotic Manipulator Software (ARMS)

Autonomous robotic manipulation requires a deep and wide stack of supporting software. This paper presents Autonomous Robotic Manipulator Software (ARMS), a software suite designed at NASA Langley Research Center to support research and development of different algorithms for In-space Servicing, Assembly and Manufacturing (ISAM). ARMS solves common challenges along the autonomous manipulation software stack. Various challenges, such as integration with commercial hardware, simulation, and path planning, are solved through the use of Robot Operating System 2 and its community-developed packages. Other challenges, such as configuration management and task definition, and execution are solved in software built on those tools. The result is a modular approach to robotic system definition, agent actions, and assembly task definitions. ARMS has been used in two ISAM projects at NASA Langley Research Center, the Precision Assembled Space Structures project and the Built On-orbit Robotically assembled Gigatruss project.

Collin J Cresta↗

NASA NTRS1983

Vortical flow management for improved configuration aerodynamics: Recent experiences

Recent progress in vortex-control applications for alleviating the adverse consequences of three dimensional separation and vortical interactions on slender body/swept wing configurations is reported. Examples include helical separation trip to alleviate the side force due to forebody vortex asymmetry; hinged strakes to avoid vortex breakdown effects; compartmentation of swept leading edge separation to delay the pitch-up instability; under wing vortex trip and vortex trip and vortex flaps for drag reduction at high lift; and an apex-flap trimmer to fully utilize the lift capability of trailing-edge flaps for take off and landing of delta wings. Experimental results on generic wind-tunnel models are presented to illustrate the vortex-management concepts involved and to indicate their potential for enhancing the subsonic aerodynamics of supersonic-cruise type vehicles.

Rao, D. M.↗

NASA NTRS1973

Report to the administrator by the NASA Aerospace Safety Advisory Panel on the Skylab program. Volume 1: Summary report

Contractor and NASA technical management for the development and manufacture of the Skylab modules is reviewed with emphasis on the following management controls: configuration and interface management; vendor control; and quality control of workmanship. A review of the modified two-stage Saturn V launch vehicle which focused on modifications to accommodate the Skylab payload; resolution of prior flight anomalies; and changes in personnel and management systems is presented along with an evaluation of the possible age-life and storage problems for the Saturn 1-B launch vehicle. The NASA program management's visibility and control of contractor operations, systems engineering and integration, the review process for the evaluation of design and flight hardware, and the planning process for mission operations are investigated. It is concluded that the technical management system for development and fabrication of the modules, spacecraft, and launch vehicles, the process of design and hardware acceptance reviews, and the risk assessment activities are satisfactory. It is indicated that checkout activity, integrated testing, and preparations for and execution of mission operation require management attention.

Source record↗

NASA NTRS2020

Power and Propulsion Element for Gateway: Configuration and Data Management of the NASA Power and Propulsion Element MBSE Model(s)

The following will be presented: CM/DM implementation environment for MBSE, traditional construct of CM/MBSE, goal for power and propulsion element team for CM/MBSE, steps to bridge the gap between CM and MBSE, how we implemented the standard tenets of CM, realized efficiencies, encountered challenges, lessons learned, and current state, and forward/future work.

Parrott, Edith L.↗

NASA NTRS1980

Low-thrust chemical orbit to orbit propulsion system propellant management study

Propellant requirements, tankage configurations, preferred propellant management techniques, propulsion systems weights, and technology deficiencies for low thrust expendable propulsion systems are examined. A computer program was utilized which provided a complete propellant inventory (including boil-off for cryogenic cases), pressurant and propellant tank dimensions for a given ullage, pressurant requirements, insulation requirements, and miscellaneous masses. The output also includes the masses of all tanks; the mass of the insulation, engines and other components; total wet system and burnout mass; system mass fraction; total impulse and burn time.

Dergance, R. H.↗

NASA NTRS2001

Online Learning Flight Control for Intelligent Flight Control Systems (IFCS)

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.

Niewoehner, Kevin R.↗

NASA NTRS1991

Demonstration of automated proximity and docking technologies

An autodock was demonstrated using straightforward techniques and real sensor hardware. A simulation testbed was established and validated. The sensor design was refined with improved optical performance and image processing noise mitigation techniques, and the sensor is ready for production from off-the-shelf components. The autonomous spacecraft architecture is defined. The areas of sensors, docking hardware, propulsion, and avionics are included in the design. The Guidance Navigation and Control architecture and requirements are developed. Modular structures suitable for automated control are used. The spacecraft system manager functions including configuration, resource, and redundancy management are defined. The requirements for autonomous spacecraft executive are defined. High level decisionmaking, mission planning, and mission contingency recovery are a part of this. The next step is to do flight demonstrations. After the presentation the following question was asked. How do you define validation? There are two components to validation definition: software simulation with formal and vigorous validation, and hardware and facility performance validated with respect to software already validated against analytical profile.

Anderson, Robert L.↗

NASA NTRS1988

Intelligent Resource Management for Local Area Networks: Approach and Evolution

The Data Management System network is a complex and important part of manned space platforms. Its efficient operation is vital to crew, subsystems and experiments. AI is being considered to aid in the initial design of the network and to augment the management of its operation. The Intelligent Resource Management for Local Area Networks (IRMA-LAN) project is concerned with the application of AI techniques to network configuration and management. A network simulation was constructed employing real time process scheduling for realistic loads, and utilizing the IEEE 802.4 token passing scheme. This simulation is an integral part of the construction of the IRMA-LAN system. From it, a causal model is being constructed for use in prediction and deep reasoning about the system configuration. An AI network design advisor is being added to help in the design of an efficient network. The AI portion of the system is planned to evolve into a dynamic network management aid. The approach, the integrated simulation, project evolution, and some initial results are described.

Meike, Roger↗

NASA NTRS1990

Space Station Freedom pressurized element interior design process

The process used to develop the on-orbit working and living environment of the Space Station Freedom has some very unique constraints and conditions to satisfy. The goal is to provide maximum efficiency and utilization of the available space, in on-orbit, zero G conditions that establishes a comfortable, productive, and safe working environment for the crew. The Space Station Freedom on-orbit living and working space can be divided into support for three major functions: (1) operations, maintenance, and management of the station; (2) conduct of experiments, both directly in the laboratories and remotely for experiments outside the pressurized environment; and (3) crew related functions for food preparation, housekeeping, storage, personal hygiene, health maintenance, zero G environment conditioning, and individual privacy, and rest. The process used to implement these functions, the major requirements driving the design, unique considerations and constraints that influence the design, and summaries of the analysis performed to establish the current configurations are described. Sketches and pictures showing the layout and internal arrangement of the Nodes, U.S. Laboratory and Habitation modules identify the current design relationships of the common and unique station housekeeping subsystems. The crew facilities, work stations, food preparation and eating areas (galley and wardroom), and exercise/health maintenance configurations, waste management and personal hygiene area configuration are shown. U.S. Laboratory experiment facilities and maintenance work areas planned to support the wide variety and mixtures of life science and materials processing payloads are described.

Hopson, George D.↗

NASA NTRS1990

Space Station Freedom pressurized element interior design process

The process used to develop the on-orbit working and living environment of the Space Station Freedom has some very unique constraints and conditions to satisfy. The goal is to provide maximum efficiency and utilization of the available space, in on-orbit, zero G conditions that establishes a comfortable, productive, and safe working environment for the crew. The Space Station Freedom on-orbit living and working space can be divided into support for three major functions: (1) operations, maintenance, and management of the station; (2) conduct of experiments, both directly in the laboratories and remotely for experiments outside the pressurized environment; and (3) crew related functions for food preparation, housekeeping, storage, personal hygiene, health maintenance, zero G environment conditioning, and individual privacy, and rest. The process used to implement these functions, the major requirements driving the design, unique considerations and constraints that influence the design, and summaries of the analysis performed to establish the current configurations are described. Sketches and pictures showing the layout and internal arrangement of the Nodes, U.S. Laboratory and Habitation modules identify the current design relationships of the common and unique station housekeeping subsystems. The crew facilities, work stations, food preparation and eating areas (galley and wardroom), and exercise/health maintenance configurations, waste management and personal hygiene area configuration are shown. U.S. Laboratory experiment facilities and maintenance work areas planned to support the wide variety and mixtures of life science and materials processing payloads are described.

Hopson, George D.↗

NASA NTRS2005

Towards an Autonomic Cluster Management System (ACMS) with Reflex Autonomicity

Cluster computing, whereby a large number of simple processors or nodes are combined together to apparently function as a single powerful computer, has emerged as a research area in its own right. The approach offers a relatively inexpensive means of providing a fault-tolerant environment and achieving significant computational capabilities for high-performance computing applications. However, the task of manually managing and configuring a cluster quickly becomes daunting as the cluster grows in size. Autonomic computing, with its vision to provide self-management, can potentially solve many of the problems inherent in cluster management. We describe the development of a prototype Autonomic Cluster Management System (ACMS) that exploits autonomic properties in automating cluster management and its evolution to include reflex reactions via pulse monitoring.

Truszkowski, Walt↗

NASA NTRS1990

Aeropropulsion facilities configuration control: Procedures manual

Lewis Research Center senior management directed that the aeropropulsion facilities be put under configuration control. A Configuration Management (CM) program was established by the Facilities Management Branch of the Aeropropulsion Facilities and Experiments Division. Under the CM program, a support service contractor was engaged to staff and implement the program. The Aeronautics Directorate has over 30 facilities at Lewis of various sizes and complexities. Under the program, a Facility Baseline List (FBL) was established for each facility, listing which systems and their documents were to be placed under configuration control. A Change Control System (CCS) was established requiring that any proposed changes to FBL systems or their documents were to be processed as per the CCS. Limited access control of the FBL master drawings was implemented and an audit system established to ensure all facility changes are properly processed. This procedures manual sets forth the policy and responsibilities to ensure all key documents constituting a facilities configuration are kept current, modified as needed, and verified to reflect any proposed change. This is the essence of the CM program.

Lavelle, James J.↗

NASA NTRS1981

Management of the Galileo attitude and articulation control flight software development

Management concepts are presented for software development for a new technology area, i.e., real-time autonomous, computer-based spacecraft control. Flight computer selection and sizing are done initially to maximize performance within constraints of size, power, and cost. A higher order language is chosen to enhance productivity. Because the computer is embedded in the control systems hardware and is tied to the iterative design process of the spacecraft, the management and configuration control of the software is different from more typical applications. The development process must permit early coding but accept late changes. Margin management must be a continuing process in the development. Validation and verification is a special problem because it is not feasible to test the software in the actual operating environment prior to launch.

Pace, G. D.↗

NASA NTRS1986

System concept for the pinhole/occulter facility payload

The results of a study of the systems concept of the Pinhole/Occulter Facility (PDF) to fly on the Shuttle as a Spacelab payload are reported. In particular, attention is given to the POF configuration and structural/mechanical concepts; POF payload structural concept development; POF payload new baseline configuration; POF pointing requirements and the Spacelab Instrument Pointing System capabilities and limitations; and pointing control implementation approach. The discussion also covers POF command and data management system configuration; POF processor software assessment; and thermal design concept.

Srinivas, R.↗

NASA NTRS1984

Flight test configuration for verifying inertial sensor redundancy management techniques

The Redundant Strapdown Inertial Measurement Unit presently tested in flight configuration consists of a semioctahedral array of four dynamically tuned, two-degree-of-freedom (TDOF) gyros and four TDOF accelerometers which can provide dual, fail-operational performance for integrated avionics systems. Attention is given to the multilevel algorithm used for the detection and isolation of three ranges of sensor failure in an integrated avionics context. A technique for the generation of accelerometer and gyro error thresholds which is sensitive to dynamic sensor errors and separation effects is presented, together with simulation results. Emphasis is placed on the ensuring of highly reliable data for flight control/navigation functions, while minimizing false or missed alarms.

Bryant, W. H.↗

NASA NTRS2018

An Integrated Platform for Mission Performance: Goddard Space Flight Center's Meta Information System

Successful management of NASA Goddard Space Flight Centers portfolio of mission projects (i.e. spacecraft, spacecraft instruments / subsystems, and ground systems) depends upon numerous processes, data and information resources coming together throughout the life-cycle of the projects to enable sound decision-making, risk reduction, conformance with requirements and continual improvement. In the summer of 2012, GSFC SMA management recognized that the set of legacy data systems used to support the SMA mission and responsibilities at GSFC were not effective, integrated nor on par with best practices. Accordingly, GSFC SMA management launched a project to transform the GSFC electronic management system to create and deploy an integrated, state-of-the-market information system for process performance, data management and analytics that is currently operating in support of GSFC overall mission performance. The information system, known as Meta, provides controlled, process-based applications, integrated data management, and analytics for a robust set of integrated applications. Since the inception of the project, a lean, award-winning SMA project team has thus far designed, configured and managed the system to serve as an integrated platform for 18 applications that support key processes for GSFC and the Science Mission Directorate at NASA headquarters, such as internal Management System assessments, Supplier Assessments, Supplier Research & Analysis, Problem Reporting for in-house mission projects, On-orbit Anomaly Reporting for GSFC-operated spacecraft, GSFC Project Life-Cycle Reviews, Risk Management and Reporting, and SMA Project Team Reporting. The system has experienced steady growth in utilization with 1,917 users (NASA employees and support contractor personnel) and 44 gigabytes of data and related files managed by the system as of the end of April 2018. Overall, Meta has achieved increasing levels of process management and real-time data / information integration to enable improved process performance, richer analytics and informed decision-making. This paper will present and examine the need, goals, approach and design driving the management and operation of the Meta information system and its ongoing growth as an integrated platform for advancing NASA mission performance.

Integration↗

NASA NTRS2009

Internet Protocol Display Sharing Solution for Mission Control Center Video System

With the advent of broadcast television as a constant source of information throughout the NASA manned space flight Mission Control Center (MCC) at the Johnson Space Center (JSC), the current Video Transport System (VTS) characteristics provides the ability to visually enhance real-time applications as a broadcast channel that decision making flight controllers come to rely on, but can be difficult to maintain and costly. The Operations Technology Facility (OTF) of the Mission Operations Facility Division (MOFD) has been tasked to provide insight to new innovative technological solutions for the MCC environment focusing on alternative architectures for a VTS. New technology will be provided to enable sharing of all imagery from one specific computer display, better known as Display Sharing (DS), to other computer displays and display systems such as; large projector systems, flight control rooms, and back supporting rooms throughout the facilities and other offsite centers using IP networks. It has been stated that Internet Protocol (IP) applications are easily readied to substitute for the current visual architecture, but quality and speed may need to be forfeited for reducing cost and maintainability. Although the IP infrastructure can support many technologies, the simple task of sharing ones computer display can be rather clumsy and difficult to configure and manage to the many operators and products. The DS process shall invest in collectively automating the sharing of images while focusing on such characteristics as; managing bandwidth, encrypting security measures, synchronizing disconnections from loss of signal / loss of acquisitions, performance latency, and provide functions like, scalability, multi-sharing, ease of initial integration / sustained configuration, integration with video adjustments packages, collaborative tools, host / recipient controllability, and the utmost paramount priority, an enterprise solution that provides ownership to the whole process, while maintaining the integrity of the latest technological displayed image devices. This study will provide insights to the many possibilities that can be filtered down to a harmoniously responsive product that can be used in today's MCC environment.

Brown, Michael A.↗