Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operations Security”

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 163 records · Page 9

Skylab Experiment M516 - Crew Activities/Maintenance Study

Skylab required daily movement about the interior of a 340 cu m vehicle and the handling and transfer of numerous loose items. Planned and unplanned maintenance tasks were also included in the daily routine of activity. Experiment M516, Crew Activities/Maintenance Study, involved an investigation of crew activity during routine daily operations. The overall objective was to secure in-flight data relevant to the performance of tasks in the weightless environment. This paper will present an evaluation of man's ability to handle and transport items of various sizes and masses (logistics management) and to make equipment repairs (maintenance). Results and conclusions are based on subjective crew comments, motion-picture film, and television transmissions.

Bond, R. L.↗

Guidelines for contingency planning NASA (National Aeronautics and Space Administration) ADP security risk reduction decision studies

Guidance is presented to NASA Computer Security Officials for determining the acceptability or unacceptability of ADP security risks based on the technical, operational and economic feasibility of potential safeguards. The risk management process is reviewed as a specialized application of the systems approach to problem solving and information systems analysis and design. Reporting the results of the risk reduction analysis to management is considered. Report formats for the risk reduction study are provided.

Tompkins, F. G.↗

Systems integration for the Kennedy Space Center (KSC) Robotics Applications Development Laboratory (RADL)

A laboratory for developing robotics technology for hazardous and repetitive Shuttle and payload processing activities is discussed. An overview of the computer hardware and software responsible for integrating the laboratory systems is given. The center's anthropomorphic robot is placed on a track allowing it to be moved to different stations. Various aspects of the laboratory equipment are described, including industrial robot arm control, smart systems integration, the supervisory computer, programmable process controller, real-time tracking controller, image processing hardware, and control display graphics. Topics of research include: automated loading and unloading of hypergolics for space vehicles and payloads; the use of mobile robotics for security, fire fighting, and hazardous spill operations; nondestructive testing for SRB joint and seal verification; Shuttle Orbiter radiator damage inspection; and Orbiter contour measurements. The possibility of expanding the laboratory in the future is examined.

Davis, V. Leon↗

Operational support considerations in Space Shuttle prelaunch processing

This paper presents an overview of operational support for Space Shuttle payload processing at the John F. Kennedy Space Center. The paper begins with a discussion of the Shuttle payload processing operation itself. It discusses the major organizational roles and describes the two major classes of payload operations: Spacelab mission payload and vertically-installed payload operations. The paper continues by describing the Launch Site Support Team and the Payload Processing Test Team. Specific areas of operational support are then identified including security and access, training, transport and handling, documentation and scheduling. Specific references for further investigatgion are included.

Schuiling, Roelof L.↗

Monte Carlo simulations of precise timekeeping in the Milstar communication satellite system

The Milstar communications satellite system will provide secure antijam communication capabilities for DOD operations into the next century. In order to accomplish this task, the Milstar system will employ precise timekeeping on its satellites and at its ground control stations. The constellation will consist of four satellites in geosynchronous orbit, each carrying a set of four rubidium (Rb) atomic clocks. Several times a day, during normal operation, the Mission Control Element (MCE) will collect timing information from the constellation, and after several days use this information to update the time and frequency of the satellite clocks. The MCE will maintain precise time with a cesium (Cs) atomic clock, synchronized to UTC(USNO) via a GPS receiver. We have developed a Monte Carlo simulation of Milstar's space segment timekeeping. The simulation includes the effects of: uplink/downlink time transfer noise; satellite crosslink time transfer noise; satellite diurnal temperature variations; satellite and ground station atomic clock noise; and also quantization limits regarding satellite time and frequency corrections. The Monte Carlo simulation capability has proven to be an invaluable tool in assessing the performance characteristics of various timekeeping algorithms proposed for Milstar, and also in highlighting the timekeeping capabilities of the system. Here, we provide a brief overview of the basic Milstar timekeeping architecture as it is presently envisioned. We then describe the Monte Carlo simulation of space segment timekeeping, and provide examples of the simulation's efficacy in resolving timekeeping issues.

Camparo, James C.↗

From Research to Operations: Integrating Components of an Advanced Diagnostic System with an Aspect-Oriented Framework

This paper presents some of the challenges associated with bringing software projects from the research world into an operationa1 environment. While the core functional components of research-oriented software applications can have great utility in an operational setting, these applications often lack aspects important in an operational environment such as logging and security. Furthermore, these stand-alone applications, sometimes developed in isolation from one another, can produce data products useful to other applications in a software ecosystem.

Fletcher, Daryl P.↗

Manual adjustable probe tool for friction stir welding

A friction stir welding tool is provided generally comprising three parts: a rotatable welding tool body (22) that has an outer threaded surface (32) and a probe (24) extending from a distal end of the body, a shoulder (26), which has a threaded inner surface (40) and a bore (36) at a distal end of the shoulder, and a jam nut (28), which has a threaded inner surface (42). The shoulder is threaded onto the tool body such that the probe extends from the shoulder through the bore by a preferred length. The jam nut is then threaded onto the tool body to secure the shoulder. The tool is operatively connected to a drive motor for rotating the tool body. The shoulder may include a knife edge projecting from the distal end (38) thereof adjacent the bore. The knife edge inhibits the weld material from migrating along the probe to intrude inside the shoulder, where it may prevent separation of the tool body and the shoulder when readjustment of the tool is necessary.

Oelgoetz, Peter A.↗

Advanced Utilization of the Payload Executive Processor (PEP) Ethernet Port to Support JSL Based Payloads

Increased interest by Payload Developers in utilization of the Joint Station LAN (Local Area Network) (JSL) for command and data transactions has driven the investigation of providing bi-directional Ethernet communication with PEP (Payload Executive Processor). Ethernet-only payload developers are interested in taking advantage of the services provided by PEP. Enabling Ethernet communications within PEP requires more than just turning on the hardware. PEP contains no Operating System (OS) or Ethernet stack so it does not inherit any built in functionality for Ethernet support. Both hardware drivers and application software must be developed from scratch. In the absence of an OS (Operating System) the design must address security issues in terms of access and data transferred, i.e. blocking unauthorized users and preventing denial of service. Developing a design to process Ethernet data within the existing real-time constraints of PEP requires a few compromises: data rates, supported protocols, custom packet format and limited client connections to name a few. Integration of the light weight internet protocol (LwIP). Ethernet stack provides a customizable solution for the embedded real-time environment. As utilization of the JSL increases, the successful implementation of an Ethernet interface enhances the utilization of PEP, and provides a new path for future Ethernet-only payloads to gain access to around the clock command and data services.

Guyette, Greg↗

Enabling Affordable Communications for the Burgeoning Deep Space Cubesat Fleet

The low costs of development and launch, coupled with new propulsive technologies, have made CubeSats increasingly popular for use in science investigations beyond geosynchronous orbit. As this deep space CubeSat fleet grows in size, the challenge of trying to provide affordable communications for it grows commensurately. The mass, power, and volume constraints inherent to CubeSats limit the antenna size and transmit power that they can use to close the deep space link. As a consequence, CubeSats need to rely more heavily on ground antennas that are characterized by large aperture, low noise temperatures, and relatively high-power transmitters. Such antennas are not in great abundance, nor are they inexpensive to build. For this reason, NASA’s Deep Space Network has been advocating a three-pronged approach to meeting anticipated CubeSat demand: development of simultaneous, shared-beam multi-spacecraft communications capabilities, development of large-antenna cross-support arrangements with other agencies and universities, and development of less uplink-intensive navigation techniques. This paper focuses on the pursuit of simultaneous, shared-beam multi-spacecraft communications capabilities. While the Multiple Spacecraft per Antenna (MSPA) technique has existed for over a decade, it has generally been limited to supporting downlink for just two in-beam spacecraft at a time. This limitation has largely been a function of the number and cost of available receivers. A relatively new technique that potentially overcomes this limitation is Opportunistic MSPA (OMSPA). Instead of relying on additional receivers, OMSPA makes use of a digital recorder at each ground station that is capable of capturing the intermediate frequency (IF) signals from every spacecraft in the antenna beam within the frequency bands of interest. When CubeSat projects see one or more opportunities for their CubeSat(s) to intercept the traditionally scheduled antenna beam of a “host” spacecraft, they can arrange for the CubeSat(s) to transmit open loop during those opportunities. Via a secure Internet site, the CubeSat mission operators can then retrieve the time- and frequency-relevant portions of the digital recording for subsequent demodulation and decoding, or subscribe to a service that does it for them. This “opportunistic” use of a host spacecraft’s ground antenna beam potentially enables CubeSat projects to make use of large ground antennas for downlink without having to compete with bigger, better-funded missions for antenna time in the formal scheduling process. In so doing, it also potentially enables CubeSat projects to avoid the aperture fees associated with formally scheduled downlink time - fees that factor into the “bottom-line” of competitively-bid NASA missions and that actually get charged to non-NASA missions. Taking advantage of these potential OMSPA benefits, however, will require CubeSat projects to pursue mission designs that ensure at least periodic in-beam operations relative to a “host” spacecraft. In the case of a constellation of CubeSats with inter-spacecraft distances that do not extend outside of the beam-width of the desired ground antenna at the given range, one CubeSat can serve as the “host” and have a formally scheduled downlink while the rest of the CubeSats can downlink essentially for “free” via OMSPA. Deep space CubeSats, of course, will need uplink in addition to downlink. Beyond commanding, this need is driven by the use of two-way ranging and Doppler for navigation. While OMSPA may not directly facilitate uplink, it does have the potential to free up antennas for those spacecraft that periodically require formally scheduled links for commanding and two-way radio metrics. NASA is also exploring the physical feasibility of an in-beam, simultaneous multi-spacecraft uplink technique. As with OMSPA, if successful, it will require little new equipment, further enabling affordable deep space CubeSat communications.

Abraham, Douglas S.↗

Reliable, Secure, and Scalable Communications, Navigation, and Surveillance (CNS) Options for Urban Air Mobility (UAM)

The Aeronautics Research Mission Directorate directed a study to identify, evaluate, and recommend viable communications, navigation, and surveillance systems and technologies to enable safe, secure, and efficient Urban Air Mobility operations in US cities. The focus is on UML-4, when commercial air taxi operations take place in all weather, are widespread, and include autonomous systems. This report recommends technologies for independent navigation, collaborative communication, and surveillance, based on capacity, availability, precision, and update rate, size, weight, power, cost and other values. Recommendations for maturing and implementing the technologies are included.

Virginia L. Stouffer↗

DRF: A Software Architecture for a Data Marketplace to Support Advanced Air Mobility

Advanced Air Mobility is a new aviation vision, where unmanned aerial systems will trans- port passengers and cargo across urban and rural areas. Critical to the realization of this vision is the development of a digital marketplace, which allows service providers and consumers operating in the airspace ecosystem to securely exchange data and reasoning insights. In this paper, we present the architecture of a decentralized data marketplace that connects data and reasoning service providers to vehicles and other service consumers along the cloud-to-edge continuum. We also present two example use cases to demonstrate the value of our approach.

Autonomy↗

NASA Capture, Containment, and Return System: Bringing Mars Samples to Earth

The Capture, Containment, and Return System (CCRS) project is NASA’s last step in bringing back Mars samples. CCRS will close a decades-long multi-mission and multi-agency effort to bring Mars surface samples back to Earth for scientific studies. CCRS will launch in 2027 on the European Earth Return Orbiter (ERO) spacecraft, which will provide communications relay for the Mars Sample Return ground missions, Perseverance rover and the Sample Retrieval Lander (SRL) (to be launched in 2028). The main mission for CCRS begins when the first-ever orbital planetary capture operation occurs with CCRS catching and securing the Orbiting Sample (OS)in low Mars orbit. From this point, the system will perform additional "firsts": it will autonomously contain the OS with heat-shrink-fit, sterilize the outside surface, and assemble the Earth entry capsule, named Earth Entry System (EES), in orbit around Mars using a gantry mechanism. At approximately 2.8 Lunar distances from Earth, or 3-days from entry into Earth’s atmosphere, CCRS will open its micrometeoroid shield and release the EES on a ballistic trajectory to Earth. The EES is designed to be a fully passive system that will enter the atmosphere and land without parachute at the Utah Test and Training Range (UTTR).

Mars mission, Sample return, Mission design↗

WEDDS: The WITS Encrypted Data Delivery System

WEDDS, the WITS Encrypted Data Delivery System, is a framework for supporting distributed mission operations by automatically transferring sensitive mission data in a secure and efficient manner to and from remote mission participants over the internet.

public key cryptography encryption authentication ↗

A Blockchain Case Study for Urban Air Mobility Operational Intent

To realize the potential of Urban Air Mobility (UAM), an assurance of cybersecurity is critical for public acceptance. UAM is a concept that proposes to develop short-range, point-to-point transportation systems in metropolitan areas using vertical takeoff and landing (VTOL) aircraft to overcome increasing surface congestion. The growth in the development of UAM systems, and the associated data exchange and service interactions will be at risk due to numerous types of cybersecurity attacks. The intent of this work is to leverage a permissioned blockchain to simulate secure data exchange and storage for the UAM operational intent use case. In this case study, two vehicle operators are operating in the same airspace. Their intent is to fly vehicles that land at a shared vertiport, securely.

Urban Air Mobility↗

Concept of Operations for an In-time Aviation Safety Management System (IASMS) for Upper E Airspace

The National Airspace System undergoes continuous change including in the Upper Class E airspace involving increasingly complex operations and a widening diversity of vehicles. To secure a safe future system, the National Academies recommended an In-time Aviation Safety Management System (IASMS) that is extensible to Upper E. Current Air Traffic Management is not cost-effective to scale for future Upper E operations and diversity of vehicles so the Federal Aviation Administration developed an Upper E Traffic Management ConOps to safely integrate the diverse operations and vehicles having different performance characteristics and flight missions without disrupting current operations including space launch and reentry, suborbital flights, supersonic and hypersonic flights, slow moving or stationary unmanned balloons, and long endurance fixed wing vehicles that are slow, stationary, or high speed. IASMS integrates state-of-the-art predictive modeling with reactive and proactive analytics to detect hazards and mitigate risk precursors for Upper E operators. IASMS identifies emergent safety risks exposed by transformation of the NAS with new and increasingly complex operations. Safety intelligence will also expand the data available and offer insight to new approaches for implementing safety improvements to mitigate risk with more seamless “in-time” integration across the policy, risk management, safety assurance, and promotion pillars of SMS.

K Ellis↗

Architecture of High-Altitude Operations (HAO) Discovery and Synchronization Service (DSS)

The aviation industry is evolving at an unprecedented pace, necessitating the development of efficient, secure, and interoperable systems to manage increasingly complex air traffic. Moreover, the demand for High-Altitude Operations (HAO) is increasing. Furthermore, air traffic control services are limited in HAO environments. HAO industry participants will need airspace access and flexibility to perform their missions in this airspace that provides provisions for scalability. The Discovery and Synchronization Service (DSS) will be a cornerstone of the HAO ecosystem, enabling the effective sharing of critical airspace data, including operational intent, aircraft trajectories, and airspace usage among various stakeholders and operators. The DSS architecture addresses these challenges with a distributed, decentralized, and interoperable system that facilitates seamless integration across diverse airspaces. It prioritizes secure data exchange while safeguarding data ownership. This white paper presents the vision, architecture, and benefits of the DSS for HAO, underscoring its potential to streamline operations, reduce redundancies, and establish a foundation for safe and efficient airspace management.

HAO↗

Hot melt adhesive attachment pad

A hot melt adhesive attachment pad for releasably securing distinct elements together is described which is particularly useful in the construction industry or a spatial vacuum environment. The attachment pad consists primarily of a cloth selectively impregnated with a charge of hot melt adhesive, a thermo-foil heater, and a thermo-cooler. These components are securely mounted in a mounting assembly. In operation, the operator activates the heating cycle transforming the hot melt adhesive to a substantially liquid state, positions the pad against the attachment surface, and activates the cooling cycle solidifying the adhesive and forming a strong, releasable bond.

Fox, R. L.↗