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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 307 records · Page 17

All sources NASA NTRS DOE OSTI

NASA NTRS1981

Portable appliance security apparatus

An apparatus for securing a small computer, or other portable appliance, against theft is described. It is comprised of a case having an open back through which the computer is installed or removed. Guide members in the form of slots are formed in a rear portion of opposite walls of the case for receiving a back plate to cover the opening and thereby secure the computer within the case. An opening formed in the top wall of the case exposes the keyboard and display of the computer. The back plate is locked in the closed position by a key-operated plug type lock. The lock is attached to one end of a hold down cable, the opposite end thereof being secured to a desk top or other stationary object. Thus, the lock simultaneously secures the back plate to the case and retains the case to the stationary object.

Kerley, J. J.↗

NASA NTRS2015

Securing the Global Airspace System Via Identity-Based Security

Current telecommunications systems have very good security architectures that include authentication and authorization as well as accounting. These three features enable an edge system to obtain access into a radio communication network, request specific Quality-of-Service (QoS) requirements and ensure proper billing for service. Furthermore, the links are secure. Widely used telecommunication technologies are Long Term Evolution (LTE) and Worldwide Interoperability for Microwave Access (WiMAX) This paper provides a system-level view of network-centric operations for the global airspace system and the problems and issues with deploying new technologies into the system. The paper then focuses on applying the basic security architectures of commercial telecommunication systems and deployment of federated Authentication, Authorization and Accounting systems to provide a scalable, evolvable reliable and maintainable solution to enable a globally deployable identity-based secure airspace system.

Communications↗

NASA NTRSDate not supplied

In-Depth Modeling and Simulation Analysis of Artemis Missions Using the Impact Probabilistic Risk Assessment Tool

BACKGROUND The Artemis campaign is a Moon exploration program with a series of six planned missions, five of which will be crewed. These five crewed missions will contain a single mission segment (space flight), or multiple mission segments involving space flight (Orion), lunar landing (LTV) and/or space habitat (Gateway). Each crewed segment faces the risk of unique medical conditions, necessitating medical sets/kits tailored to those specificities. To support and enable a data-driven and evidence-based decision-making process through out a mission’s life cycle, a software tool called IMPACT was developed. Using probabilistic risk assessment (PRA) methodologies, IMPACT (Informing Mission Planning via Analysis of Complex Tradespaces) is a novel tool built for analyzing the possibility of encountering complex medical risks during space flight, and for identifying the medical resources and capabilities needed to treat those potential at-risk medical conditions. IMPACT achieves this by performing hundreds of thousands of Monte Carlo simulations of missions to build aggregate pictures of medical risk. During an extended simulation modeling phase, IMPACT generated analytical results for medical risks, and the medical resources and capabilities to address those risks, for every segment of every crewed Artemis mission. This presentation will highlight the reliability, consistency and validity of IMPACT’s computational modeling techniques and will showcase the library of analytical outcomes generated for the Artemis missions. OVERVIEW During the early stages of IMPACT’s design, architecture and technical requirements collection, “scenarios” (use cases) - achievement goals required for acceptance testing, were identified by stakeholders. IMPACT successfully completed the scenario testing requirements and undertook an extensive operational run phase utilizing a wide range of input combinations with a goal of delivering a cohesive, trustworthy, reliable, vast, and diverse body of evidence. The intent of these modeling runs was to validate consistency in output, ensure solidity of executable operations and to streamline processes by identifying areas requiring efficiency improvements. Using the many missions of Artemis, IMPACT ran variations of operational runs to assess the output for acceptable, as well as unusual characteristics. This rigorous long-term “shakedown” analysis was implemented to help build a collective body of evidence to aid in securing a high level of confidence, reliability, and validity in the output, whether from the applicational components of IMPACT, or the entirety of the operational process. ANTICIPATED ANALYSIS AND CONCLUSION This presentation will discuss the various categories of input criteria; the comparisons in the application of these input criteria to various Artemis missions; the preparation and collection of the body of evidence, and reliability of the computational modeling techniques. This paper serves as an initial analytical overview of IMPACT’s probabilistic risk assessment (PRA) medical risk outputs covering Artemis missions and is not intended to be deemed the official medical response for the Artemis campaign.

Crew Composition↗

NASA NTRS2003

Space-based Operations Grid Prototype

The Space based Operations Grid is intended to integrate the "high end" network services and compute resources that a remote payload investigator needs. This includes integrating and enhancing existing services such as access to telemetry, payload commanding, payload planning and internet voice distribution as well as the addition of services such as video conferencing, collaborative design, modeling or visualization, text messaging, application sharing, and access to existing compute or data grids. Grid technology addresses some of the greatest challenges and opportunities presented by the current trends in technology, i.e. how to take advantage of ever increasing bandwidth, how to manage virtual organizations and how to deal with the increasing threats to information technology security. We will discuss the pros and cons of using grid technology in space-based operations and share current plans for the prototype. It is hoped that early on the prototype can incorporate many of the existing as well as future services that are discussed in the first paragraph above to cooperating International Space Station Principle Investigators both nationally and internationally.

Bradford, Robert N.↗

NASA NTRS2002

Adapting Digital Libraries to Continual Evolution

In this paper, we describe five investment streams (data storage infrastructure, knowledge management, data production control, data transport and security, and personnel skill mix) that need to be balanced against short-term operating demands in order to maximize the probability of long-term viability of a digital library. Because of the rapid pace of information technology change, a digital library cannot be a static institution. Rather, it has to become a flexible organization adapted to continuous evolution of its infrastructure.

Barkstrom, Bruce R.↗

NASA NTRS2007

Pressure Sensitive Tape in the Manufacture of Reusable Solid Rocket Motors

ATK Launch Systems Inc. manufactures the reusable solid rocket motor (RSRM) for NASA's Space Shuttle program. They are used in pairs to launch the Space Shuttle. Pressure sensitive tape (PST) is used throughout the RSRM manufacturing process. A few PST functions are: 1) Secure labels; 2) Provide security seals; and 3) Protect tooling and flight hardware during various inert and live operations. Some of the PSTs used are: Cloth, Paper, Reinforced Teflon, Double face, Masking, and Vinyl. Factors given consideration for determining the type of tape to be used are: 1) Ability to hold fast; 2) Ability to release easily; 3) Ability to endure abuse; 4) Strength; and 5) Absence of adhesive residue after removal.

Champneys, Jeff↗

NASA NTRS2015

Application of a Novel Long-Reach Manipulator Concept to Asteroid Redirect Missions

A high priority mission currently being formulated by NASA is to capture all or part of an asteroid and return it to cis-lunar space for examination by an astronaut crew. Two major mission architectures are currently being considered: in the first (Mission Concept A), a spacecraft would rendezvous and capture an entire free flying asteroid (up to 14 meters in diameter), and in the second (Mission Concept B), a spacecraft would rendezvous with a large asteroid (which could include one of the Martian moons) and retrieve a boulder (up to 4 meters in diameter). A critical element of the mission is the system that will capture the asteroid or boulder material, enclose it and secure it for the return flight. This paper describes the design concepts, concept of operations, structural sizing and masses of capture systems that are based on a new and novel Tendon- Actuated Lightweight In-Space MANipulator (TALISMAN) general-purpose robotic system. Features of the TALISMAN system are described and the status of its technology development is summarized. TALISMAN-based asteroid material retrieval system concepts and concepts-of-operations are defined for each asteroid mission architecture. The TALISMAN-based capture systems are shown to dramatically increase operational versatility while reducing mission risk. Total masses of TALISMAN-based systems are presented, reinforcing the mission viability of using a manipulator-based approach for the asteroid redirect mission.

Dorsey, John T.↗

NASA NTRS2016

Landsat 8: The Plans, the Reality, and the Legacy

Landsat 8, originally known as the Landsat Data Continuity Mission (LDCM), is a National Aeronautics and Space Administration (NASA)-U.S. Geological Survey (USGS) partnership that continues the legacy of continuous moderate resolution observations started in 1972. The conception of LDCM to the reality of Landsat 8 followed an arduous path extending over nearly 13 years, but the successful launch on February 11, 2013 ensures the continuity of the unparalleled Landsat record. The USGS took over mission operations on May 30, 2013 and renamed LCDM to Landsat 8. Access to Landsat 8 data was opened to users worldwide. Three years following launch we evaluate the science and applications impact of Landsat 8. With a mission objective to enable the detection and characterization of global land changes at a scale where differentiation between natural and human-induced causes of change is possible, LDCM promised incremental technical improvements in capabilities needed for Landsat scientific and applications investigations. Results show that with Landsat 8, we are acquiring more data than ever before, the radiometric and geometric quality of data are generally technically superior to data acquired by past Landsat missions, and the new measurements, e.g., the coastal aerosol and cirrus bands, are opening new opportunities. Collectively, these improvements are sparking the growth of science and applications opportunities. Equally important, with Landsat 7 still operational, we have returned to global imaging on an 8-day cycle, a capability that ended when Landsat 5 ceased operational Earth imaging in November 2011. As a result, the Landsat program is on secure footings and planning is underway to extend the record for another 20 or more years.

Loveland, Thomas R.↗

NASA NTRS2019

Development of a Point of Care Technology for Military Medical Applications in Austere Environments

NASA, Lawrence Livermore National Laboratory (LLNL) and the Department of Defense (DoD) share a common interest in compact medical diagnostic technologies—also known as “point of care testing” (POCT) technologies. For NASA, the need is to take care of astronauts on deep space missions. For LLNL, the focus is on technologies needed to support homeland security applications. For DoD, the need is to support warfighters in military theaters of operation, especially for prolonged field care and en route care. A recently patented technology, “Portable Medical Diagnosis Instrument” (U.S. Patent 9824870), co-invented by NASA and LLNL, is being developed further in a partnership between NASA, LLNL and Travis Air Force Base, with a focus on military applications. This instrument, the NASA-LLNL Medical Tricorder, can be used for a wide range of clinical samples including breath, saliva and blood. One component of the Tricorder is the NASA E-Nose, a carbon nanotube-based chemical sensor, integrated into a hand-held smart phone, that can detect and measure “breath biomarkers” in the gas phase of exhaled breath. The response of the NASA E-Nose is rapid, which makes it possible to detect various gas-phase substances in real time. The NASA E-Nose, with modification, can also be used for breath condensate analysis. Another component of the Tricorder is a miniaturized microfluidic analyzer, under development by LLNL, that does not require any pumps. The microfluidic analyzer can detect and measure biomarkers in liquid samples, such as blood, saliva and breath condensate. This microfluidic system requires small quantities of liquid sample and can perform analysis very rapidly (seconds to minutes), which makes it possible to detect relevant biomarkers in near real time in the field. The Clinical Investigation Facility (CIF) at Travis Air Force Base is currently conducting research with the goal to develop improved field-able technologies and procedures for the emergency response to life threatening injuries soldiers may receive in theater. This work includes experimental large animal systems and comprehensive collection of clinical specimens and physiological data. NASA and LLNL are partnering with Travis to test and further develop the Tricorder technology for high priority military applications, initially focused on lung injury models and traumatic brain injury.

Loftus, David J.↗

NASA NTRS2014

Virtualization - A Key Cost Saver in NASA Multi-Mission Ground System Architecture

With science team budgets being slashed, and a lack of adequate facilities for science payload teams to operate their instruments, there is a strong need for innovative new ground systems that are able to provide necessary levels of capability processing power, system availability and redundancy while maintaining a small footprint in terms of physical space, power utilization and cooling.The ground system architecture being presented is based off of heritage from several other projects currently in development or operations at Goddard, but was designed and built specifically to meet the needs of the Science and Planetary Operations Control Center (SPOCC) as a low-cost payload command, control, planning and analysis operations center. However, this SPOCC architecture was designed to be generic enough to be re-used partially or in whole by other labs and missions (since its inception that has already happened in several cases!)The SPOCC architecture leverages a highly available VMware-based virtualization cluster with shared SAS Direct-Attached Storage (DAS) to provide an extremely high-performing, low-power-utilization and small-footprint compute environment that provides Virtual Machine resources shared among the various tenant missions in the SPOCC. The storage is also expandable, allowing future missions to chain up to 7 additional 2U chassis of storage at an extremely competitive cost if they require additional archive or virtual machine storage space.The software architecture provides a fully-redundant GMSEC-based message bus architecture based on the ActiveMQ middleware to track all health and safety status within the SPOCC ground system. All virtual machines utilize the GMSEC system agents to report system host health over the GMSEC bus, and spacecraft payload health is monitored using the Hammers Integrated Test and Operations System (ITOS) Galaxy Telemetry and Command (TC) system, which performs near-real-time limit checking and data processing on the downlinked data stream and injects messages into the GMSEC bus that are monitored to automatically page the on-call operator or Systems Administrator (SA) when an off-nominal condition is detected. This architecture, like the LTSP thin clients, are shared across all tenant missions.Other required IT security controls are implemented at the ground system level, including physical access controls, logical system-level authentication authorization management, auditing and reporting, network management and a NIST 800-53 FISMA-Moderate IT Security plan Risk Assessment Contingency Plan, helping multiple missions share the cost of compliance with agency-mandated directives.The SPOCC architecture provides science payload control centers and backup mission operations centers with a cost-effective, standardized approach to virtualizing and monitoring resources that were traditionally multiple racks full of physical machines. The increased agility in deploying new virtual systems and thin client workstations can provide significant savings in personnel costs for maintaining the ground system. The cost savings in procurement, power, rack footprint and cooling as well as the shared multi-mission design greatly reduces upfront cost for missions moving into the facility. Overall, the authors hope that this architecture will become a model for how future NASA operations centers are constructed!

Ground System Architecture↗

NASA NTRSDate not supplied

Corridor Design and Analysis for UAM Operations

The Urban Air Mobility (UAM) concept is a part of Advanced Air Mobility (AAM), a joint initiative between the Federal Aviation Administration (FAA), NASA, and industry to develop an air transportation system that uses new electric (i.e., green) air vehicles in geographical areas previously underserved by traditional aviation. Market forecast studies predict that there will be demand for alternate modes of air transportation using electric Vertical Take-off and Landing aircraft. UAM expands transportation networks by introducing short flights to move people and goods around metropolitan areas. UAM is expected to improve mobility for the public, decongest road traffic, reduce trip time, and decrease strain on existing public transportation networks. Various challenges exist to make the introduction of UAM operations successful in the U.S. National Airspace System (NAS). These include but are not limited to integration with existing airports and airspace, provision of air traffic services (e.g., separation), vehicle design and certification, and community acceptance. The focus of this paper is on integration of UAM operations into the NAS via introduction of new airspace structures. UAM will operate within a regulatory, operational, and technical environment that is incorporated into the NAS. As per the UAM Concept of Operations (ConOps), the FAA retains regulatory authority and is responsible for establishing operational parameters and maintaining oversight. The FAA’s UAM ConOps describes flights at low altitudes (below 5,000 ft) with minimal disruption to established conventional aircraft traffic and limited voice interactions with the Air Traffic Control (ATC). Early stages of UAM may use existing procedures to safely integrate UAM with conventional flights. This would involve flying under Part 91 Visual Flight Rules (VFR) and using voice for communications. The initial UAM ecosystem will utilize the current infrastructure such as routes, helipads, and ATC services, where practicable. A NASA study explored the use of existing helicopter routes in Dallas Fort Worth (DFW) airspace for initial UAM operations with a Letter of Agreement (LOA) that included procedures to request a Class B (controlled airspace) clearance. The research showed that the chosen approach was feasible for near-term, low-demand UAM traffic, but was not scalable. The growth of operations in today’s aviation system has resulted in airspace reorganization and procedures to ensure safety and efficiency as traffic rates increase. One proposed operating innovation that can help with the scalability of UAM is establishing routes and corridors. This may look similar to the Area Navigation (RNAV) procedures used today to streamline operations into busy airports. However, instead of FAA automation systems and ATC managing the flow of traffic, some UAM concepts envision a third-party service provider performing this role as part of the Provider of Services for UAM (PSU) network. The FAA’s UAM ConOps posits that new airspace structures such as UAM corridors include the following design criteria: 1) Minimal impact on existing NAS operations, 2) no or minimal additional ATC services, 3) public interest considerations such as noise, safety, and security, and 4) customer needs. The airspace available in urban environments is limited by the height of buildings, the effect of weather including wind gusts, privacy needs, and a clearance envelope. The new airspace structure would need to be designed around large airports and urban areas where the initial market demand is likely to exist. NASA has started evaluating airspace in the Dallas Fort Worth area to design new airspace structures, keeping the first two design criteria in mind. It is assumed that there will be an on-board pilot-in-command, and the flights will operate under VFR in Visual Meteorological Conditions. Corridors will be required in controlled airspace, whereas UAM operations can fly in uncontrolled Class G and E airspace using current day rules. Keeler et. al identified factors and heuristics for development of routes for UAM operations for integration with airspace close to large airports such as Dallas Fort Worth and Dallas Love Field. This paper describes the heuristics applied to define the corridors, analyzes them with respect to legacy traffic and presents key results.

Urban Air Mobility↗

NASA NTRS1993

Mission planning for Shuttle Imaging Radar-C (SIR-C) with a real-time interactive planning software

The Shuttle Imaging Radar-C (SIR-C) mission will operate from the payload bay of the space shuttle for 8 days, gathering Synthetic Aperture Radar (SAR) data over specific sites on the Earth. The short duration of the mission and the requirement for realtime planning offer challenges in mission planning and in the design of the Planning and Analysis Subsystem (PAS). The PAS generates shuttle ephemerides and mission planning data and provides an interactive real-time tool for quick mission replanning. It offers a multi-user and multiprocessing environment, and it is able to keep multiple versions of the mission timeline data while maintaining data integrity and security. Its flexible design allows one software to provide different menu options based on the user's operational function, and makes it easy to tailor the software for other Earth orbiting missions.

Potts, Su K.↗

NASA NTRS2005

Modular Software Interfaces for Revolutionary Flexibility in Space Operations

To make revolutionary improvements in exploration, space systems need to be flexible, realtime reconfigurable, and able to trade data transparently among themselves and mission operations. Onboard operations systems, space assembly coordination and EVA systems in exploration and construction all require real-time modular reconfigurability and data sharing. But NASA's current exploration systems are still largely legacies from hastily-developed, one-off Apollo-era practices. Today's rovers, vehicles, spacesuits, space stations, and instruments are not able to plug-and-play, Lego-like: into different combinations. Point-to-point dominates - individual suit to individual vehicle, individual instrument to rover. All are locally optimized, all unique, each of the data interfaces has been recoded for each possible combination. This will be an operations and maintenance nightmare in the much larger Project Constellation system of systems. This legacy approach does not scale to the hundreds of networked space components needed for space construction and for new, space-based approaches to Earth-Moon operations. By comparison, battlefield information management systems, which are considered critical to military force projection, have long since abandoned a point-to-point approach to systems integration. From a system-of-systems viewpoint, a clean-sheet redesign of the interfaces of all exploration systems is a necessary prerequisite before designing the interfaces of the individual exploration systems. Existing communications and Global Information Grid and middleware technologies are probably sufficient for command and control and information interfaces, with some hardware and time-delay modifications for space environments. NASA's future advanced space operations must also be information and data compatible with aerospace operations and surveillance systems being developed by other US Government agencies such as the Department of Homeland Security, Federal Aviation Administration and Department of Defense. This paper discusses fundamental system-of-systems infrastructure: approaches and architectures for modular plug-and-play software interfaces for revolutionary improvements in flexibility, modularity, robustness, ease of maintenance, reconfigurability, safety and productivity. Starting with middleware, databases, and mobile communications technologies, our technical challenges will be to apply these ideas to the requirements of constellations of space systems and to implement them initially on prototype space hardware. This is necessary to demonstrate an integrated information sharing architecture and services. It is a bottom-up approach, one that solves the problem of space operations data integration. Exploration demands uniform software mechanisms for application information interchange, and the corresponding uniformly available software services to enhance these mechanisms. We will examine the issues in plug-and-play, real-time-configurable systems, including common definition and management and tracking of data and information among many different space systems. Different field test approaches are discussed, including the use of the International Space Station and terrestrial analog mission operations at field sites.

Glass, Brian↗

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 NTRS2007

System for Secure Integration of Aviation Data

The Aviation Data Integration System (ADIS) of Ames Research Center has been established to promote analysis of aviation data by airlines and other interested users for purposes of enhancing the quality (especially safety) of flight operations. The ADIS is a system of computer hardware and software for collecting, integrating, and disseminating aviation data pertaining to flights and specified flight events that involve one or more airline(s). The ADIS is secure in the sense that care is taken to ensure the integrity of sources of collected data and to verify the authorizations of requesters to receive data. Most importantly, the ADIS removes a disincentive to collection and exchange of useful data by providing for automatic removal of information that could be used to identify specific flights and crewmembers. Such information, denoted sensitive information, includes flight data (here signifying data collected by sensors aboard an aircraft during flight), weather data for a specified route on a specified date, date and time, and any other information traceable to a specific flight. The removal of information that could be used to perform such tracing is called "deidentification." Airlines are often reluctant to keep flight data in identifiable form because of concerns about loss of anonymity. Hence, one of the things needed to promote retention and analysis of aviation data is an automated means of de-identification of archived flight data to enable integration of flight data with non-flight aviation data while preserving anonymity. Preferably, such an automated means would enable end users of the data to continue to use pre-existing data-analysis software to identify anomalies in flight data without identifying a specific anomalous flight. It would then also be possible to perform statistical analyses of integrated data. These needs are satisfied by the ADIS, which enables an end user to request aviation data associated with de-identified flight data. The ADIS includes client software integrated with other software running on flight-operations quality-assurance (FOQA) computers for purposes of analyzing data to study specified types of events or exceedences (departures of flight parameters from normal ranges). In addition to ADIS client software, ADIS includes server hardware and software that provide services to the ADIS clients via the Internet (see figure). The ADIS server receives and integrates flight and non-flight data pertaining to flights from multiple sources. The server accepts data updates from authorized sources only and responds to requests from authorized users only. In order to satisfy security requirements established by the airlines, (1) an ADIS client must not be accessible from the Internet by an unauthorized user and (2) non-flight data as airport terminal information system (ATIS) and weather data must be displayed without any identifying flight information. ADIS hardware and software architecture as well as encryption and data display scheme are designed to meet these requirements. When a user requests one or more selected aviation data characteristics associated with an event (e.g., a collision, near miss, equipment malfunction, or exceedence), the ADIS client augments the request with date and time information from encrypted files and submits the augmented request to the server. Once the user s authorization has been verified, the server returns the requested information in de-identified form.

Kulkarni, Deepak↗

NASA NTRS2022

The Mars 2020 Ground Data System Architecture

The Mars 2020 Mission’s primary objective is to collect 20 geographically unique samples during its prime mission of one and a quarter Martian years, or just over 2 Earth years. Mission planners determined the project needed to develop a system that would enable the operations team to analyze engineering and science data, make science decisions, select viable rover targets at a millimeter resolution and validate an uplink bundle for a car sized rover with more complex science instruments than any previous Mars surface mission. All this had to be done within a five hour time frame. Doing this with a small team would be a challenge, but this had to be accomplished by a large team of engineers and scientists located across North America and Europe. Achieving this level of operational efficiency was unheard of in the prime mission. In addition, the mission had another set of requirements that had nothing to do with surface operations; the Mars 2020 Ground Data System (GDS) was also expected to comply with a new set of security requirements to keep up with the ever changing cybersecurity landscape. The Mars 2020 Ground Data System (GDS) is a re-architected version of the Mars Science Laboratory GDS. The primary goal was to integrate the lessons learned from previous Mars surface missions, accommodate a set of new requirements and capabilities required to ensure mission success, and comply with a new set of cybersecurity controls. The new architecture includes several unique qualities including a data lake, language-agnostic system-wide event-based operations, containerization, automated deployment, network segmentation, infrastructure-as-code, API-driven interfaces, and the first Mars surface GDS to operate primarily in the cloud. The new architecture enabled greater access to the system’s data, tighter integration with the operations team, and a higher level of traceability. The availability of the data also enabled a new set of capabilities previously not possible on surface missions. These new capabilities include an autonomous data to information, pipeline for downlink analysis, horizontal scaling of science data processing capabilities, autonomous round trip data tracking of science and engineering data, integration of flight system state into the tactical planning cycle, high fidelity targeting utilizing kinematic data, and hierarchical image and 3d meshes data representations. This paper will introduce the requirements for the Mars 2020 Mission, the heritage architecture, and the rationale for the changes to achieve the new architecture. The paper will continue to describe the fundamental changes made to the GDS architecture, how these changes enabled a more tightly integrated GDS, and the new capabilities that were enabled by the new architecture. The paper will conclude with the lessons learned from the process of rearchitecting a heritage GDS system and from the first 200 days of operations supporting over 800 users from around the world.

Lopez-Roig, Reynaldo↗

NASA NTRS2015

Technical Challenges and Opportunities of Centralizing Space Science Mission Operations (SSMO) at NASA Goddard Space Flight Center

The NASA Goddard Space Science Mission Operations project (SSMO) is performing a technical cost-benefit analysis for centralizing and consolidating operations of a diverse set of missions into a unified and integrated technical infrastructure. The presentation will focus on the notion of normalizing spacecraft operations processes, workflows, and tools. It will also show the processes of creating a standardized open architecture, creating common security models and implementations, interfaces, services, automations, notifications, alerts, logging, publish, subscribe and middleware capabilities. The presentation will also discuss how to leverage traditional capabilities, along with virtualization, cloud computing services, control groups and containers, and possibly Big Data concepts.

Science↗

NASA NTRS1989

The internet worm

In November 1988 a worm program invaded several thousand UNIX-operated Sun workstations and VAX computers attached to the Research Internet, seriously disrupting service for several days but damaging no files. An analysis of the work's decompiled code revealed a battery of attacks by a knowledgeable insider, and demonstrated a number of security weaknesses. The attack occurred in an open network, and little can be inferred about the vulnerabilities of closed networks used for critical operations. The attack showed that passwork protection procedures need review and strengthening. It showed that sets of mutually trusting computers need to be carefully controlled. Sharp public reaction crystalized into a demand for user awareness and accountability in a networked world.

Denning, Peter J.↗