Search NASA⌕ Search

SEARCH · Search NASA

Results for “Ground support system”

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

IT Security Support for the Spaceport Command Control Systems Development Ground Support Development Operations

Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere was heightened from Airports to the communication among the military branches legionnaires. With advanced persistent threats (APTs) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated and secured state in a launch control system environment. FISMA is a law that is mandated by the government to follow when government agencies secure networks and devices. My role on this project is to ensure network devices and systems are in compliance with NIST, as outlined in FISMA. I will achieve this by providing assistance with security plan documentation and collection, system hardware and software inventory, malicious code and malware scanning and configuration of network devices i.e. routers and IDSsIPSs. In addition I will be completing security assessments on software and hardware, vulnerability assessments and reporting, conducting patch management and risk assessments. A guideline that will help with compliance with NIST is the SANS Top 20 Critical Controls. SANS Top 20 Critical Controls as well as numerous security tools, security software and the conduction of research will be used to successfully complete the tasks given to me. This will ensure compliance with FISMA and NIST, secure systems and a secured network. By the end of this project, I hope to have carried out stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, policies and procedures.

computer information security↗
NASA NTRS2014

IT Security Support for the Spaceport Command Control Systems Development Ground Support Development Operations

Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere has heightened from airports to the communication among the military branches legionnaires. With advanced persistent threats (APT's) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated and secured state in a launch control system environment. FISMA is a law that is mandated by the government to follow when government agencies secure networks and devices. My role on this project is to ensure network devices and systems are in compliance with NIST, as outlined in FISMA. I will achieve this by providing assistance with security plan documentation and collection, system hardware and software inventory, malicious code and malware scanning, and configuration of network devices i.e. routers and IDS's/IPS's. In addition, I will be completing security assessments on software and hardware, vulnerability assessments and reporting, and conducting patch management and risk assessments. A guideline that will help with compliance with NIST is the SANS Top 20 Critical Controls. SANS Top 20 Critical Controls as well as numerous security tools, security software and the conduction of research will be used to successfully complete the tasks given to me. This will ensure compliance with FISMA and NIST, secure systems and a secured network. By the end of this project, I hope to have carried out the tasks stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, as well as policies and procedures.

security↗
NASA NTRS1980

Multimission Modular Spacecraft Ground Support Software System (MMS/GSSS) state-of-the-art computer systems/ compatibility study

The compatibility of the Multimission Modular Spacecraft (MMS) Ground Support Software System (GSSS), currently operational on a ModComp IV/35, with the VAX 11/780 system is discussed. The compatibility is examined in various key areas of the GSSS through the results of in depth testing performed on the VAX 11/780 and ModComp IV/35 systems. The compatibility of the GSSS with the ModComp CLASSIC is presented based upon projections from ModComp supplied literature.

Source record↗
NASA NTRS2003

Case for Deploying Complex Systems Utilizing Commodity Components

This viewgraph representation presents a study of the transition of computer networks and software engineering at the Huntsville Operations Support Center (HOSC) from a client/server UNIX based system to a client/server system based on commodity priced and open system components. Topics covered include: an overview of HOSC ground support systems, an analysis for changes to the existing ground support system, an analysis of options considered for the transition to a new system, and a consideration of goals for a new system.

Bryant, Barry S.↗
NASA NTRS1986

An expert system for ground support of the Hubble space telescope

The Hubble Space Telescope is an orbiting optical observatory due to be launched by the Space Shuttle in late 1987. It is a complex, multi-instrument observatory whose resources will be available to the world-wide astronomical community. The 'Transformation' system is a hybrid system which utilizes a rule-based expert system to convert scientific proposals into pre-optimized linked hierarchies of spacecraft activities. These activities are generated in a format that can be directly scheduled by the planning and scheduling component of the Space Telescope ground support system. The Transformation system will be described in detail in this paper, with particular attention given to the rule base.

Rosenthal, Don↗
NASA NTRS2017

Development of Telecommunications Systems and Ground Support for EM-1 Interplanetary Cubesats Missions: Lunar IceCube and LunaH-Map

CubeSats are now providing an innovative way to explore space: they can be built by smaller teams in academic environments, and they generally require smaller budget than traditional missions. For this reason, a new trend has emerged in the last five years: interplanetary CubeSats. Interplanetary CubeSats take advantage of the CubeSat paradigm and of the availability of commercial components developed for Low Earth Orbit (LEO) missions, but they are specifically designed to explore deep space. As a result, interplanetary CubeSats are essentially very different from Low Earth Orbit CubeSats in at least three technological areas: propulsion, radiation tolerance and telecommunication. This paper is focused on telecommunication issues for interplanetary CubeSats which face harsher environments, longer path distances and have more navigation needs than the LEO CubeSats. For this reason, the design of telecommunication systems for interplanetary missions is extremely challenging and significant development is currently ongoing in the areas of radio design, antenna design and the design of ground support architectures. This presentation focuses on the design of the telecommunication and ground support systems for two of the interplanetary CubeSats missions that will be launched on NASA’s Space Launch System (SLS) Exploration Mission-1 (EM-1): Lunar IceCube and LunaH-Map. Given the commonalities between these missions, an effort is underway at JPL to develop a common set of telecommunication hardware systems to fit the envelope of the two missions’ goals. Additionally, Lunar IceCube and LunaH-Map will also share the use of the Deep Space Network antennas and of the Morehead State University 21 m station, which is currently being upgraded especially for this purpose. This presentation will provide a quick overview of the missions (including goals and telecommunication requirements) and it will also focus on the development of the telecommunication systems design with a particular focus on the current upgrades planned to the Morehead State University ground station.

Babuscia, Alessandra↗
NASA NTRS1983

Forecasting trends in NASA flight software development tools

The experience gained in the design and development of Shuttle flight and ground support embedded software systems along with projections of increasing role and size of software in the proposed Space Station and other future NASA projects provides the basis for forecasting substantial changes in the tools and methodologies by which embedded software systems are developed and acquired. Similar changes in software architectures and operator interfaces will lead to substantial changes in the approach and techniques involved in software test and system integration. Increasing commonality among different flight systems and between flight and supporting ground systems is projected, along with a more distributed approach to software acquisition in highly complex projects such as Space Station.

Garman, J. R.↗
NASA NTRS1995

The Adaptation of Industrial Protocols for a Space Messaging Service

A standard data system interface for space data systems will have a major impact on the cost of building spacecraft and the ground systems built to support their operation. Properly designed, a standard interface will provide a 'plug-and-play' environment for the construction of spacecraft and ground systems. Using the standard, commercial vendors of spacecraft devices, spacecraft instrumentation and ground support systems could build and market products that would be installed without the traditional software development effort.

Industrial Protocols↗
NASA NTRS2009

A Summary of NASA and USAF Hypergolic Propellant Related Spills and Fires

Several unintentional hypergolic fluid related spills, fires, and explosions from the Apollo Program, the Space Shuttle Program, the Titan Program, and a few others have occurred over the past several decades. Spill sites include the following government facilities: Kennedy Space Center (KSC), Johnson Space Center (JSC), White Sands Test Facility (WSTF), Vandenberg Air Force Base (VAFB), Cape Canaveral Air Force Station (CCAFS), Edwards Air Force Base (EAFB), Little Rock AFB, and McConnell AFB. Until now, the only method of capturing the lessons learned from these incidents has been "word of mouth" or by studying each individual incident report. The root causes and consequences of the incidents vary drastically; however, certain "themes" can be deduced and utilized for future hypergolic propellant handling. Some of those common "themes" are summarized below: (1) Improper configuration control and internal or external human performance shaping factors can lead to being falsely comfortable with a system (2) Communication breakdown can escalate an incident to a level where injuries occur and/or hardware is damaged (3) Improper propulsion system and ground support system designs can destine a system for failure (4) Improper training of technicians, engineers, and safety personnel can put lives in danger (5) Improper PPE, spill protection, and staging of fire extinguishing equipment can result in unnecessary injuries or hardware damage if an incident occurs (6) Improper procedural oversight, development, and adherence to the procedure can be detrimental and quickly lead to an undesirable incident (7) Improper materials cleanliness or compatibility and chemical reactivity can result in fires or explosions (8) Improper established "back-out" and/or emergency safing procedures can escalate an event The items listed above are only a short list of the issues that should be recognized prior to handling hypergolic fluids or processing vehicles containing hypergolic propellants. The summary of incidents in this report is intended to cover many more issues than those listed above.

Nufer, Brian M.↗
NASA NTRS2009

Lessons Learned Entry: Hypergolic Propellant Related Spills and Fires

The attached report is a compilation of all credible, unintentional hypergolic fluid related spills, fires, and explosions from the Apollo Program, the Space Shuttle Program, Titan Program, and a few other programs. Spill sites include the following government facilities: KSC, JSC, WSTF, VAFB, CCAFS, EAFB, Little Rock AFB, and McConnell AFB. The root causes and consequences of the incidents contained in this document vary drastically; however, certain "themes" can be deduced and utilized for future hypergolic propellant handling. Some of those common "themes" are summarized below: (1) Improper configuration control and complacency can lead to being falsely comfortable with a system (2) Communication breakdown can escalate an incident to a level where injuries occur and/or hardware is damaged (3) Improper propulsion system and ground support system designs can destine a system for failure (4) Improper training of technicians, engineers, and safety personnel can put lives in danger (5) Improper PPE, spill protection, and staging of fire extinguishing equipment can result in unnecessary injuries or hardware damage if an incident occurs (6) Improper procedural oversight, development, and adherence to the procedure can be detrimental and quickly lead to an undesirable incident (7) Improper local cleanliness or compatibility can result in fires or explosions The items listed above are only a short list of the issues that should be recognized prior to handling of hypergolic fluids or processing of vehicles containing hypergolic propellants. The summary of incidents in this report is intended to cover many more issues than those listed above that have been found during nearly the entire spectrum. of hypergolic propellant and/or vehicle processing.

Nufer, Brian↗
NASA NTRS1999

Lockheed Martin Skunk Works Single Stage to Orbit/Reusable Launch Vehicle

Lockheed Martin Skunk Works has compiled an Annual Performance Report of the X-33/RLV Program. This report consists of individual reports from all industry team members, as well as NASA team centers. This portion of the report is comprised of a status report of Lockheed Martin's contribution to the program. The following is a summary of the Lockheed Martin Centers involved and work reviewed under their portion of the agreement: (1) Lockheed Martin Skunk Works - Vehicle Development, Operations Development, X-33 and RLV Systems Engineering, Manufacturing, Ground Operations, Reliability, Maintainability/Testability, Supportability, & Special Analysis Team, and X-33 Flight Assurance; (2) Lockheed Martin Technical Operations - Launch Support Systems, Ground Support Equipment, Flight Test Operations, and RLV Operations Development Support; (3) Lockheed Martin Space Operations - TAEM and A/L Guidance and Flight Control Design, Evaluation of Vehicle Configuration, TAEM and A/L Dispersion Analysis, Modeling and Simulations, Frequency Domain Analysis, Verification and Validation Activities, and Ancillary Support; (4) Lockheed Martin Astronautics-Denver - Systems Engineering, X-33 Development; (5) Sanders - A Lockheed Martin Company - Vehicle Health Management Subsystem Progress, GSS Progress; and (6) Lockheed Martin Michoud Space Systems - X-33 Liquid Oxygen (LOX) Tank, Key Challenges, Lessons Learned, X-33/RLV Composite Technology, Reusable Cyrogenic Insulation (RCI) and Vehicle Health Monitoring, Main Propulsion Systems (MPS), Structural Testing, X-33 System Integration and Analysis, and Cyrogenic Systems Operations.

Source record↗
NASA NTRS1983

Application experience with the NASA aircraft interrogation and display system - A ground-support equipment for digital flight systems

The NASA Dryden Flight Research Facility has developed a microprocessor-based, user-programmable, general-purpose aircraft interrogation and display system (AIDS). The hardware and software of this ground-support equipment have been designed to permit diverse applications in support of aircraft digital flight-control systems and simulation facilities. AIDS is often employed to provide engineering-units display of internal digital system parameters during development and qualification testing. Such visibility into the system under test has proved to be a key element in the final qualification testing of aircraft digital flight-control systems. Three first-generation 8-bit units are now in service in support of several research aircraft projects, and user acceptance has been high. A second-generation design, extended AIDS (XAIDS), incorporating multiple 16-bit processors, is now being developed to support the forward swept wing aircraft project (X-29A). This paper outlines the AIDS concept, summarizes AIDS operational experience, and describes the planned XAIDS design and mechanization.

Glover, R. D.↗
NASA NTRS1994

Re-engineering Nascom's network management architecture

The development of Nascom systems for ground communications began in 1958 with Project Vanguard. The low-speed systems (rates less than 9.6 Kbs) were developed following existing standards; but, there were no comparable standards for high-speed systems. As a result, these systems were developed using custom protocols and custom hardware. Technology has made enormous strides since the ground support systems were implemented. Standards for computer equipment, software, and high-speed communications exist and the performance of current workstations exceeds that of the mainframes used in the development of the ground systems. Nascom is in the process of upgrading its ground support systems and providing additional services. The Message Switching System (MSS), Communications Address Processor (CAP), and Multiplexer/Demultiplexer (MDM) Automated Control System (MACS) are all examples of Nascom systems developed using standards such as, X-windows, Motif, and Simple Network Management Protocol (SNMP). Also, the Earth Observing System (EOS) Communications (Ecom) project is stressing standards as an integral part of its network. The move towards standards has produced a reduction in development, maintenance, and interoperability costs, while providing operational quality improvement. The Facility and Resource Manager (FARM) project has been established to integrate the Nascom networks and systems into a common network management architecture. The maximization of standards and implementation of computer automation in the architecture will lead to continued cost reductions and increased operational efficiency. The first step has been to derive overall Nascom requirements and identify the functionality common to all the current management systems. The identification of these common functions will enable the reuse of processes in the management architecture and promote increased use of automation throughout the Nascom network. The MSS, CAP, MACS, and Ecom projects have indicated the potential value of commercial-off-the-shelf (COTS) and standards through reduced cost and high quality. The FARM will allow the application of the lessons learned from these projects to all future Nascom systems.

Drake, Brian C.↗
NASA NTRS2005

Smart Sensors' Role in Integrated System Health Management

During the last decade, there has been a major effort in the aerospace industry to reduce the cost per pond of payload and become competitive in the international market. Competition from Europe, Japan, and China has reduced this cost to almost a third from 1990 to 2000. This cost has leveled in recent years to an average price of around $12,000/pound of payload. One of NASA's goals is to promote the development of technologies to reduce this cost by a factor of 10 or more Exploration of space, specially manned exploration missions, involves very complex launch and flight vehicles, associated ground support systems, and extensive human support during all phases of the mission. When considering the Space Shuttle Program, we can see that vehicle and ground support systems' processing, operation, and maintenance represent a large percentage of the program cost and time. Reducing operating, processing and maintenance costs will greatly reduce the cost of Exploration programs. The Integrated System Health Management (ISHM) concept is one of the technologies that will help reduce these operating, processing and maintenance costs. ISHM is an integrated health monitoring system applicable to both flight and ground systems. It automatically and autonomously acquires information from sensors and actuators and processes that information using the ISHM-embedded knowledge. As a result, it establishes the health of the system based on the acquired information and its prior knowledge. When this concept is fully implemented, ISHM systems shall be able to perform failure prediction and remediation before actual hard failures occurs, preventing its costly consequences. Data sources, sensors, and their associated data acquisition systems, constitute the foundation of the system. A smart sensing architecture is required to support the acquisition of reliable, high quality data, required by the ISHM. A thorough definition of the smart sensor architectures, their embedded diagnostic agents, and communication protocols need to be established and standardized to allow the embedding and exchange of health information among sensors and ISHM. This workshop is aimed to foster the exchange of ideas and lessons learned between government, industry and academia to aid in the establishment of ISHM (and smart sensors) standards and guidelines as well as to identify present technology gaps that will have to be overcome to successfully achieve this goal.

Perotti, Jose M.↗
NASA NTRS1981

Advanced Microwave Moisture Sounder (AMMS) for WB-57F CCOPE mission

The AMMS, flown on the WB-57F Cooperative Convective Precipitation Experiment (CCOPE), collected data at three bands on either side of the 183.3 GHz water vapor line at + or - 2.25, + or - 5.00, and + or - 8.75 GHz. Data were also collected simultaneously at a single low-loss atmospheric window channel near 94 GHz. The AMMS scanner imaged the scene below the WB-57F over an angular range of + or - 45 degree about nadir with beam-widths of 2 degree and 1 degree for the 94 GHz and 183 GHz sensors, respectively. The radiometer system operated under control of the onboard microcomputer used to: store radiometric data on the AMMS flight recorder, operate the stepper motor driven scanner, and collect pertinent housekeeping data for the system. A portable ground support system was used following each CCOPE flight to provide quick-look data analysis. The CCOPE flight logs and tape of the AMMS data were delivered to NASA.

Gagliano, J. A.↗