Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “security systems”

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 217 records · Page 12
All sourcesNASA NTRSDOE OSTI
NASA NTRS1997

Infrared Camera

A sensitive infrared camera that observes the blazing plumes from the Space Shuttle or expendable rocket lift-offs is capable of scanning for fires, monitoring the environment and providing medical imaging. The hand-held camera uses highly sensitive arrays in infrared photodetectors known as quantum well infrared photo detectors (QWIPS). QWIPS were developed by the Jet Propulsion Laboratory's Center for Space Microelectronics Technology in partnership with Amber, a Raytheon company. In October 1996, QWIP detectors pointed out hot spots of the destructive fires speeding through Malibu, California. Night vision, early warning systems, navigation, flight control systems, weather monitoring, security and surveillance are among the duties for which the camera is suited. Medical applications are also expected.

Source record↗
NASA NTRS1990

Development Status: Automation Advanced Development Space Station Freedom Electric Power System

Electric power system automation for Space Station Freedom is intended to operate in a loop. Data from the power system is used for diagnosis and security analysis to generate Operations Management System (OMS) requests, which are sent to an arbiter, which sends a plan to a commander generator connected to the electric power system. This viewgraph presentation profiles automation software for diagnosis, scheduling, and constraint interfaces, and simulation to support automation development. The automation development process is diagrammed, and the process of creating Ada and ART versions of the automation software is described.

Dolce, James L.↗
NASA NTRS2002

The D3 Middleware Architecture

DARWIN is a NASA developed, Internet-based system for enabling aerospace researchers to securely and remotely access and collaborate on the analysis of aerospace vehicle design data, primarily the results of wind-tunnel testing and numeric (e.g., computational fluid-dynamics) model executions. DARWIN captures, stores and indexes data; manages derived knowledge (such as visualizations across multiple datasets); and provides an environment for designers to collaborate in the analysis of test results. DARWIN is an interesting application because it supports high-volumes of data. integrates multiple modalities of data display (e.g., images and data visualizations), and provides non-trivial access control mechanisms. DARWIN enables collaboration by allowing not only sharing visualizations of data, but also commentary about and views of data. Here we provide an overview of the architecture of D3, the third generation of DARWIN. Earlier versions of DARWIN were characterized by browser-based interfaces and a hodge-podge of server technologies: CGI scripts, applets, PERL, and so forth. But browsers proved difficult to control, and a proliferation of computational mechanisms proved inefficient and difficult to maintain. D3 substitutes a pure-Java approach for that medley: A Java client communicates (though RMI over HTTPS) with a Java-based application server. Code on the server accesses information from JDBC databases, distributed LDAP security services, and a collaborative information system. D3 is a three tier-architecture, but unlike 'E-commerce' applications, the data usage pattern suggests different strategies than traditional Enterprise Java Beans - we need to move volumes of related data together, considerable processing happens on the client, and the 'business logic' on the server-side is primarily data integration and collaboration. With D3, we are extending DARWIN to handle other data domains and to be a distributed system, where a single login allows a user transparent access to test results from multiple servers and authority domains.

Walton, Joan↗
NASA NTRS2005

NASA's Research in Aircraft Vulnerability Mitigation

Since its inception in 1958, the National Aeronautics and Space Administration s (NASA) role in civil aeronautics has been to develop high-risk, high-payoff technologies to meet critical national aviation challenges. Following the events of Sept. 11, 2001, NASA recognized that it now shared the responsibility for improving homeland security. The NASA Strategic Plan was modified to include requirements to enable a more secure air transportation system by investing in technologies and collaborating with other agencies, industry, and academia. NASA is conducting research to develop and advance innovative and commercially viable technologies that will reduce the vulnerability of aircraft to threats or hostile actions, and identify and inform users of potential vulnerabilities in a timely manner. Presented in this paper are research plans and preliminary status for mitigating the effects of damage due to direct attacks on civil transport aircraft. The NASA approach to mitigation includes: preventing loss of an aircraft due to a hit from man-portable air defense systems; developing fuel system technologies that prevent or minimize in-flight vulnerability to small arms or other projectiles; providing protection from electromagnetic energy attacks by detecting directed energy threats to aircraft and on/off-board systems; and minimizing the damage due to high-energy attacks (explosions and fire) by developing advanced lightweight, damage-resistant composites and structural concepts. An approach to preventing aircraft from being used as weapons of mass destruction will also be discussed.

Allen, Cheryl L.↗
NASA NTRS2005

Software to Manage the Unmanageable

In 1995, NASA s Jet Propulsion Laboratory (JPL) contracted Redmond, Washington-based Lucidoc Corporation, to design a technology infrastructure to automate the intersection between policy management and operations management with advanced software that automates document workflow, document status, and uniformity of document layout. JPL had very specific parameters for the software. It expected to store and catalog over 8,000 technical and procedural documents integrated with hundreds of processes. The project ended in 2000, but NASA still uses the resulting highly secure document management system, and Lucidoc has managed to help other organizations, large and small, with integrating document flow and operations management to ensure a compliance-ready culture.

Source record↗
NASA NTRS2009

Proceedings of the Third International Workshop on Proof-Carrying Code and Software Certification

This NASA conference publication contains the proceedings of the Third International Workshop on Proof-Carrying Code and Software Certification, held as part of LICS in Los Angeles, CA, USA, on August 15, 2009. Software certification demonstrates the reliability, safety, or security of software systems in such a way that it can be checked by an independent authority with minimal trust in the techniques and tools used in the certification process itself. It can build on existing validation and verification (V&V) techniques but introduces the notion of explicit software certificates, Vvilich contain all the information necessary for an independent assessment of the demonstrated properties. One such example is proof-carrying code (PCC) which is an important and distinctive approach to enhancing trust in programs. It provides a practical framework for independent assurance of program behavior; especially where source code is not available, or the code author and user are unknown to each other. The workshop wiII address theoretical foundations of logic-based software certification as well as practical examples and work on alternative application domains. Here "certificate" is construed broadly, to include not just mathematical derivations and proofs but also safety and assurance cases, or any fonnal evidence that supports the semantic analysis of programs: that is, evidence about an intrinsic property of code and its behaviour that can be independently checked by any user, intermediary, or third party. These guarantees mean that software certificates raise trust in the code itself, distinct from and complementary to any existing trust in the creator of the code, the process used to produce it, or its distributor. In addition to the contributed talks, the workshop featured two invited talks, by Kelly Hayhurst and Andrew Appel. The PCC 2009 website can be found at http://ti.arc.nasa.gov /event/pcc 091.

Ewen, Denney, W.↗
NASA NTRS2016

Information Management Platform for Data Analytics and Aggregation (IMPALA) System Design Document

The System Design document tracks the design activities that are performed to guide the integration, installation, verification, and acceptance testing of the IMPALA Platform. The inputs to the design document are derived from the activities recorded in Tasks 1 through 6 of the Statement of Work (SOW), with the proposed technical solution being the completion of Phase 1-A. With the documentation of the architecture of the IMPALA Platform and the installation steps taken, the SDD will be a living document, capturing the details about capability enhancements and system improvements to the IMPALA Platform to provide users in development of accurate and precise analytical models. The IMPALA Platform infrastructure team, data architecture team, system integration team, security management team, project manager, NASA data scientists and users are the intended audience of this document. The IMPALA Platform is an assembly of commercial-off-the-shelf (COTS) products installed on an Apache-Hadoop platform. User interface details for the COTS products will be sourced from the COTS tools vendor documentation. The SDD is a focused explanation of the inputs, design steps, and projected outcomes of every design activity for the IMPALA Platform through installation and validation.

Carnell, Andrew↗
NASA NTRS2017

Virtualized Multi-Mission Operations Center (vMMOC) and its Cloud Services

His presentation will cover, the current and future, technical and organizational opportunities and challenges with virtualizing a multi-mission operations center. The full deployment of Goddard Space Flight Centers (GSFC) Virtualized Multi-Mission Operations Center (vMMOC) is nearly complete. The Space Science Mission Operations (SSMO) organizations spacecraft ACE, Fermi, LRO, MMS(4), OSIRIS-REx, SDO, SOHO, Swift, and Wind are in the process of being fully migrated to the vMMOC. The benefits of the vMMOC will be the normalization and the standardization of IT services, mission operations, maintenance, and development as well as ancillary services and policies such as collaboration tools, change management systems, and IT Security. The vMMOC will also provide operational efficiencies regarding hardware, IT domain expertise, training, maintenance and support.The presentation will also cover SSMO's secure Situational Awareness Dashboard in an integrated, fleet centric, cloud based web services fashion. Additionally the SSMO Telemetry as a Service (TaaS) will be covered, which allows authorized users and processes to access telemetry for the entire SSMO fleet, and for the entirety of each spacecrafts history. Both services leverage cloud services in a secure FISMA High and FedRamp environment, and also leverage distributed object stores in order to house and provide the telemetry. The services are also in the process of leveraging the cloud computing services elasticity and horizontal scalability. In the design phase is the Navigation as a Service (NaaS) which will provide a standardized, efficient, and normalized service for the fleet's space flight dynamics operations. Additional future services that may be considered are Ground Segment as a Service (GSaaS), Telemetry and Command as a Service (TCaaS), Flight Software Simulation as a Service, etc.

Ido, Haisam Kassim↗
NASA NTRS2019

NASA’s Optical Communications Programs

The way we communicate in space and how we stay connected on Earth is experiencing a change: while we traditionally use radio frequency communication methods from satellites to ground stations, there is a growing interest in laser communication connections back to Earth, but also in the space environment. Meanwhile, the need for higher data rates also push for a shift in the use of frequency bands, with new bands such as high-power KA, KU, Q and V being developed.These changes require new technologies and new issues need to be addressed. Bringing together satellite operators, satellite manufacturers, and component suppliers, this panel will discuss the following questions and topics: (1)New technology requirements for different communication bands: from antennas to optimized ground systems; (2) New technology challenges when implementing new communication systems: from smaller spaces, to 'noise on the line' and radiation issues; (4) How can we leverage safely what is already out there?; (5) How to ensure communication system resiliency and security?

Edwards, Bernard L.↗
NASA NTRS2018

Reduced Gravity Airborne Mobility Testbed

Working in conjunction with the NASA Ames research center the goal of this senior design project was to develop a mobile test apparatus to enable wheel-soil interaction in a reduced gravity environment. In addition to collecting accurate wheel-soil interfacing data, a method of maintaining the density of the soil being used during the testing was developed to allow for repeatable testing conditions In order to meet these goals an annular testbed was design and built, providing an alternative to NASA’s linear rover wheel design. The circular design allowed for a smaller footprint and lighter device. The team found it was possible to set the desired slip ratio by rotating the both the annular testbed and wheel at different speeds. The Drawbar Pull force on the wheel was then measured with a torque sensor. Future work to be done includes improving the timing belt system, more robust control system, and more secure testbed base.

Liz Barrett↗
NASA NTRS2017

Managing Cyber Risk: from the Ground to the Air and Beyond Out There

Experts from the aerospace sector with the focus of presenting current state-of-the-art in aviation cyber security and discussing major challenges, requirements, and developments. A variety of topics will be addressed by the panel, including: Aviation cyber security regulations, standards, and best practices Aviation information sharing and analysis challenges Aircraft systems and avionics cyber security challenges Airline and airport stakeholder cyber perspectives CNSATM cyber security challenges UAS cyber security and privacy requirements Military aviation cyber security issues in the NAS

Davis, Jerry L.↗
NASA NTRS2018

Reliable and Secure Surveillance, Communications and Navigation (RSCAN) for Unmanned Air Systems (UAS) in Controlled Airspace

The aviation industry faces a rapidly-emerging need for integrating Unmanned Air Systems (UAS) into the national airspace (NAS). This trend will present challenging questions for the safe operation of UAS in controlled and uncontrolled airspaces based on new Communications, Navigation and Surveillance (CNS) technologies. For example, can wireless communications data links provide the necessary capacity for accommodating ever increasing numbers of UAS worldwide? Does the communications network provide ample Internet Protocol (IP) address space to allow Air Traffic Control (ATC) to securely address each UAS? Can navigation and surveillance approaches assure safe route planning and safe separation of vehicles even in crowded skies?Under NASA contract NNA16BD84C, Boeing is developing an integrated CNS architecture to enable UAS operations in the NAS. Revolutionary and advanced CNS alternatives are needed to support UAS operations at all altitudes and in all airspaces, including both controlled and uncontrolled. These CNS alternatives must be reliable, redundant, always available, cyber-secure, and affordable for all types of vehicles including small UAS to large transport category aircraft. Our approach considers CNS requirements that address the range of UAS missions where they will be most beneficial and cost-effective.A cybersecure future UAS CNS architecture is needed to support the NASA vision for an Unmanned Air Traffic Management (UTM) system in uncontrolled airspace and a cooperative operation of manned and unmanned aircraft in the controlled global Air Traffic Management (ATM) system. The architecture must, therefore, support always-available and cyber secure operations. This paper presents UAS CNS architecture concepts for large UAS operating in the ATM system in controlled airspace. Future companion works will consider small UAS operating in the UTM system in uncontrolled airspace.

Ponchak, Denise S.↗
NASA NTRS2014

NASA Unmanned Aircraft (UA) Control and Non-Payload Communication (CNPC) System Waveform Trade Studies

Unmanned Aircraft Systems (UAS) represent a new capability that will provide a variety of services in the government (public) and commercial (civil) aviation sectors. The growth of this potential industry has not yet been realized due to the lack of a common understanding of what is required to safely operate UAS in the National Airspace System (NAS). To address this deficiency, NASA has established a project called UAS Integration in the NAS (UAS in the NAS), under the Integrated Systems Research Program (ISRP) of the Aeronautics Research Mission Directorate (ARMD). This project provides an opportunity to transition concepts, technology, algorithms, and knowledge to the Federal Aviation Administration (FAA) and other stakeholders to help them define the requirements, regulations, and issues for routine UAS access to the NAS. The safe, routine, and efficient integration of UAS into the NAS requires new radio frequency (RF) spectrum allocations and a new data communications system which is both secure and scalable with increasing UAS traffic without adversely impacting the Air Traffic Control (ATC) communication system. These data communications, referred to as Control and Non-Payload Communications (CNPC), whose purpose is to exchange information between the unmanned aircraft and the ground control station to ensure safe, reliable, and effective unmanned aircraft flight operation. A Communications Subproject within the UAS in the NAS Project has been established to address issues related to CNPC development, certification and fielding. The focus of the Communications Subproject is on validating and allocating new RF spectrum and data link communications to enable civil UAS integration into the NAS. The goal is to validate secure, robust data links within the allocated frequency spectrum for UAS. A vision, architectural concepts, and seed requirements for the future commercial UAS CNPC system have been developed by RTCA Special Committee 203 (SC-203) in the process of determining formal recommendations to the FAA in its role provided for under the Federal Advisory Committee Act. NASA intends to conduct its research and development in keeping with this vision and associated architectural concepts. The prototype communication systems developed and tested by NASA will be used to validate and update the initial SC-203 requirements in order to provide a foundation for SC-203's Minimum Aviation System Performance Standards (MASPS).

Aircraft Communications↗
NASA NTRS2006

Dynamic Tunnel Usability Study: Format Recommendations for Synthetic Vision System Primary Flight Displays

A usability study evaluating dynamic tunnel concepts has been completed under the Aviation Safety and Security Program, Synthetic Vision Systems Project. The usability study was conducted in the Visual Imaging Simulator for Transport Aircraft Systems (VISTAS) III simulator in the form of questionnaires and pilot-in-the-loop simulation sessions. Twelve commercial pilots participated in the study to determine their preferences via paired comparisons and subjective rankings regarding the color, line thickness and sensitivity of the dynamic tunnel. The results of the study showed that color was not significant in pilot preference paired comparisons or in pilot rankings. Line thickness was significant for both pilot preference paired comparisons and in pilot rankings. The preferred line/halo thickness combination was a line width of 3 pixels and a halo of 4 pixels. Finally, pilots were asked their preference for the current dynamic tunnel compared to a less sensitive dynamic tunnel. The current dynamic tunnel constantly gives feedback to the pilot with regard to path error while the less sensitive tunnel only changes as the path error approaches the edges of the tunnel. The tunnel sensitivity comparison results were not statistically significant.

Arthur, Jarvis J., III↗
NASA NTRS2014

Modernization of the Cassini Ground System

The Cassini Spacecraft and its ground system have been operational for over 16 years. Modernization presents several challenges due to the personnel, processes, and tools already invested and embedded into the current ground system structure. Every mission's ground system has its own unique complexities and challenges, involving various organizational units. As any mission from its inception to its execution, schedules are always tight. This forces GDS engineers to implement a working ground system that is not necessarily fully optimized. Ground system challenges increase as technology evolves and cyber threats become more sophisticated. Cassini's main challenges were due to its ground system existing before many security requirements were levied on the multi-mission tools and networks. This caused a domino effect on Cassini GDS tools that relied on outdated technological features. In the aerospace industry reliable and established technology is preferred over innovative yet less proven technology. Loss of data for a spacecraft mission can be catastrophic; therefore, there is a reluctance to make changes and updates to the ground system. Nevertheless, all missions and associated teams face the need to modernize their processes and tools. Systems development methods from well-known system analysis and design principles can be applied to many missions' ground systems. Modernization should always be considered, but should be done in such a way that it does not affect flexibility nor interfere with established practices. Cassini has accomplished a secure and efficient ground data system through periodic updates. The obstacles faced while performing the modernization of the Cassini ground system will be outlined, as well as the advantages and challenges that were encountered.

Razo, Gus↗
NASA NTRS2014

Modernization of the Cassini Ground System

The Cassini Spacecraft and its ground system have been operational for over 16 years. Modernization presents several challenges due to the personnel, processes, and tools already invested and embedded into the current ground system structure. Every mission's ground system has its own unique complexities and challenges, involving various organizational units. As any mission from its inception to its execution, schedules are always tight. This forces GDS engineers to implement a working ground system that is not necessarily fully optimized. Ground system challenges increase as technology evolves and cyber threats become more sophisticated. Cassini's main challenges were due to its ground system existing before many security requirements were levied on the multi-mission tools and networks. This caused a domino effect on Cassini GDS tools that relied on outdated technological features. In the aerospace industry reliable and established technology is preferred over innovative yet less proven technology. Loss of data for a spacecraft mission can be catastrophic; therefore, there is a reluctance to make changes and updates to the ground system. Nevertheless, all missions and associated teams face the need to modernize their processes and tools. Systems development methods from well-known system analysis and design principles can be applied to many missions' ground systems. Modernization should always be considered, but should be done in such a way that it does not affect flexibility nor interfere with established practices. Cassini has accomplished a secure and efficient ground data system through periodic updates. The obstacles faced while performing the modernization of the Cassini ground system will be outlined, as well as the advantages and challenges that were encountered.

Razo, Gus↗
NASA NTRS2012

ELaNa - Educational Launch of Nanosatellite Providing Routine RideShare Opportunities

Since the creation of the NASA CubeSat Launch Initiative (NCSLI), the need for CubeSat rideshares has dramatically increased. After only three releases of the initiative, a total of 66 CubeSats now await launch opportunities. So, how is this challenge being resolved? NASA's Launch Services Program (LSP) has studied how to integrate PPODs on Athena, Atlas V, and Delta IV launch vehicles and has been instrumental in developing several carrier systems to support CubeSats as rideshares on NASA missions. In support of the first two ELaNa missions the Poly-Picosatellite Orbital Deployer (P-POD) was adapted for use on a Taurus XL (ELaNa I) and a Delta n (ELaNa III). Four P-PODs, which contained a total eight CubeSats, were used on these first ELaNa missions. Next up is ELaNa VI, which will launch on an Atlas V in August 2012. The four ELaNa VI CubeSats, in three P-PODs, are awaiting launch, having been integrated in the NPSCuLite. To increase rideshare capabilities, the Launch Services Program (LSP) is working to integrate P-PODs on Falcon 9 missions. The proposed Falcon 9 manifest will provide greater opportunities for the CubeSat community. For years, the standard CubeSat size was 1 U to 3U. As the desire to include more science in each cube grows, so does the standard CubeSat size. No longer is a 1 U, 1.5U, 2U or 3U CubeSat the only option available; the new CubeSat standard will include 6U and possibly even 12U. With each increase in CubeSat size, the CubeSat community is pushing the capability of the current P-POD design. Not only is the carrier system affected, but integration to the Launch Vehicle is also a concern. The development of a system to accommodate not only the 3U P-POD but also carriers for larger CubeSats is ongoing. LSP considers payloads in the lkg to 180 kg range rideshare or small/secondary payloads. As new and emerging small payloads are developed, rideshare opportunities and carrier systems need to be identified and secured. The development of a rideshare carrier system is not always cost effective. Sometimes a launch vehicle with an excellent performance record appears to be a great rideshare candidate however, after completing a feasibility study, LSP may determine that the cost of the rideshare carrier system is too great and, due to budget constraints, the development cannot go forward. With the current budget environment, one cost effective way to secure rideshare opportunities is to look for synergy with other government organizations that share the same interest.

Skrobot, Garrett Lee↗