Search NASA⌕ Search

SEARCH · Search NASA

Results for “Policy support”

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 235 records · Page 13

The National Space Science Data Center: An operational perspective

The National Space Science Data Center (NSSDC) manages over 110,000 data tapes with over 4,000 data sets. The size of the digital archive is approximately 6,000 GBytes and is expected to grow to more than 28,000 GBytes by 1995. The NSSDC is involved in several initiatives to better serve the scientific community and improve the management of current and future data holdings. These initiatives address the need to manage data to ensure ready access by the user and manage the media to ensure continuing accessibility and integrity of the data. This paper will present an operational view of the NSSDC, outlining current policies and procedures that were implemented to ensure the effective use of available resources to support service and mission goals, and maintain compliance with prescribed data management directives.

Blitstein, Ronald↗

Upper Atmospheric Research Satellite (UARS) ground data system - The first operational data system for the Mission to Planet Earth

The initiation of the National Aeronautics and Space Administration (NASA) Mission to Planet Earth was realized with the activation of the Upper Atmosphere Research Satellite (LIARS) in mid-September 1991 following deployment from the Shuttle Transport System (STS) - 48. The UARS provides the first comprehensive study of the chemistry and dynamics of the upper atmosphere. The UARS ground data system provides the capabilities required to support upper atmospheric studies in a timely and flexible manner. The UARS ground data system policy and implementation plan incorporated by the UARS Project team provided the flexibility necessary to be able to respond to changing priorities and requirements and to permit the ground data system to evolve far beyond initial expectations. This paper describes the policies and plans in place during the initial design and implementation phases and provides an overview of the UARS ground data system. The paper then addresses the changing UARS ground data system design and implementation priorities, the early mission experiences instrumental in the achievement of higher than expected goals, and a brief look at the future for UARS, the first Mission to Planet Earth.

Herring, Ellen L.↗

The structure of the clouds distributed operating system

A novel system architecture, based on the object model, is the central structuring concept used in the Clouds distributed operating system. This architecture makes Clouds attractive over a wide class of machines and environments. Clouds is a native operating system, designed and implemented at Georgia Tech. and runs on a set of generated purpose computers connected via a local area network. The system architecture of Clouds is composed of a system-wide global set of persistent (long-lived) virtual address spaces, called objects that contain persistent data and code. The object concept is implemented at the operating system level, thus presenting a single level storage view to the user. Lightweight treads carry computational activity through the code stored in the objects. The persistent objects and threads gives rise to a programming environment composed of shared permanent memory, dispensing with the need for hardware-derived concepts such as the file systems and message systems. Though the hardware may be distributed and may have disks and networks, the Clouds provides the applications with a logically centralized system, based on a shared, structured, single level store. The current design of Clouds uses a minimalist philosophy with respect to both the kernel and the operating system. That is, the kernel and the operating system support a bare minimum of functionality. Clouds also adheres to the concept of separation of policy and mechanism. Most low-level operating system services are implemented above the kernel and most high level services are implemented at the user level. From the measured performance of using the kernel mechanisms, we are able to demonstrate that efficient implementations are feasible for the object model on commercially available hardware. Clouds provides a rich environment for conducting research in distributed systems. Some of the topics addressed in this paper include distributed programming environments, consistency of persistent data and fault-tolerance.

Dasgupta, Partha↗

Optimizing space constellations for mobile satellite systems

Designing a mobile satellite system entails many complex trade-offs between a great number of parameters including: capacity, complexity of the payload, constellation geometry, number of satellites, quality of coverage, etc. This paper aims at defining a methodology which tries to split the variables to give rapidly some first results. The major input considered is the traffic assumption which would be offered by the system. A first key step is the choice of the best Rider or Walker constellation geometries - with different numbers of satellites - to insure a good quality of coverage over a selected service area. Another aspect to be addressed is the possible altitude location of the constellation, since it is limited by many constraints. The altitude ranges that seem appropriate considering the spatial environment, the launch and orbit keeping policy and the feasibility of the antenna allowing sufficient frequency reuse are briefly analyzed. To support these first considerations, some 'reference constellations' with similar coverage quality are chosen. The in-orbit capacity needed to support the assumed traffic is computed versus altitude. Finally, the exact number of satellite is determined. It comes as an optimum between a small number of satellites offering a high (and costly) power margin in bad propagation situation and a great number of less powerful satellites granting the same quality of service.

Roussel, T.↗

Acquisition of and Access to Research Omics Data

Omics data are essential for understanding the myriad and complex effects of space environments on humans. To assure maximum benefit from these kinds of data, the NASA Human Research Program Data Management Plan stipulates that human omics data should be archived within and accessed through the NASA Life Sciences Portal (NLSP). The NLSP has the capability to acquire and provision access to omics (and other kinds of) research results for individual and ad-hoc groups of subjects at the direction of institutional review boards, or other authorizing bodies or individuals, per institutional, program and investigation-specific policies and procedures. However, because some single-subject omics data, like CT scans and other kinds of large, complex biomedical data, could be used to identify heretofore unknown risks to the subject’s health, or, in certain cases, be used to identify a subject, NASA Policy Directive 7170.1 describes various policies regarding the management of and access to “research genetic testing” data, which includes many kinds of omics data. For example, NPD 7170.1 prohibits access to human research genetic data by NASA personnel who make employment decisions for the subjects from whom the data were obtained. To meet the objective of acquiring research omics data for NLSP in compliance with the policies in NPD 7170.1 and other applicable NASA policies, we designed NOMADS (the NLSP Omics Multimodal Acquisition of Data System), a new component that supports the transfer of large research data files, including research genetic testing data, using one of several different transfer mechanisms. The choice of mechanism is made by the submitter of the data, with guiding information from the system, and is likely to often be determined in large part by the nature and source location of the data. For example, for small files where the source data files are not already stored in a cloud storage system, users are likely to prefer to transfer their data to the NLSP via a web browser. Conversely, for large sets of files already organized and stored in a cloud storage system, users may opt for NOMAD’s cloud-to-cloud transfer method. All omics datasets targeted for the NASA Life Sciences Data Archive must pass a variety of quality checks to ensure data integrity and adherence to the standards defined by the LSDA Data Submission Guidelines (DSG) (see https://nlsp.nasa.gov/explore/lsdahome/datasubmit). These include requirements that data are consistent with open standards established by the omics community. Non-compliant data will not be accepted however archivists are available to advise submitters on how to revise data submissions and re-submit until compliance is achieved. Following compliance with the LSDA DSG, omics data next undergo a variety of additional quality checks to ensure the data meet omics community standards. Domain specific Omics data quality control tools and techniques are continually evolving and linked to the advancements in omics assays utilized and thus, the tools and techniques utilized by the LSDA for data quality control and validation will need to be sustained accordingly. All human omics data will be access controlled according to the policies described above, and requiring IRB approval for any additional access grants once the data are acquired (including access for analysis using the NLSP workspace tools).

Omics↗

Acquisition of and Access to Research Omics Data

Omics data are essential for understanding the myriad and complex effects of space environments on humans. To assure maximum benefit from these kinds of data, the NASA Human Research Program Data Management Plan stipulates that human omics data should be archived within and accessed through the NASA Life Sciences Portal (NLSP). The NLSP has the capability to acquire and provision access to omics (and other kinds of) research results for individual and ad-hoc groups of subjects at the direction of institutional review boards, or other authorizing bodies or individuals, per institutional, program and investigation-specific policies and procedures. However, because some single-subject omics data, like CT scans and other kinds of large, complex biomedical data, could be used to identify heretofore unknown risks to the subject’s health, or, in certain cases, be used to identify a subject, NASA Policy Directive 7170.1 describes various policies regarding the management of and access to “research genetic testing” data, which includes many kinds of omics data. For example, NPD 7170.1 prohibits access to human research genetic data by NASA personnel who make employment decisions for the subjects from whom the data were obtained. To meet the objective of acquiring research omics data for NLSP in compliance with the policies in NPD 7170.1 and other applicable NASA policies, we designed NOMADS (the NLSP Omics Multimodal Acquisition of Data System), a new component that supports the transfer of large research data files, including research genetic testing data, using one of several different transfer mechanisms. The choice of mechanism is made by the submitter of the data, with guiding information from the system, and is likely to often be determined in large part by the nature and source location of the data. For example, for small files where the source data files are not already stored in a cloud storage system, users are likely to prefer to transfer their data to the NLSP via a web browser. Conversely, for large sets of files already organized and stored in a cloud storage system, users may opt for NOMAD’s cloud-to-cloud transfer method. All omics datasets targeted for the NASA Life Sciences Data Archive must pass a variety of quality checks to ensure data integrity and adherence to the standards defined by the LSDA Data Submission Guidelines (DSG) (see https://nlsp.nasa.gov/explore/lsdahome/datasubmit). These include requirements that data are consistent with open standards established by the omics community. Non-compliant data will not be accepted however archivists are available to advise submitters on how to revise data submissions and re-submit until compliance is achieved. Following compliance with the LSDA DSG, omics data next undergo a variety of additional quality checks to ensure the data meet omics community standards. Domain specific Omics data quality control tools and techniques are continually evolving and linked to the advancements in omics assays utilized and thus, the tools and techniques utilized by the LSDA for data quality control and validation will need to be sustained accordingly. All human omics data will be access controlled according to the policies described above, and requiring IRB approval for any additional access grants once the data are acquired (including access for analysis using the NLSP workspace tools).

Omics↗

Hurricane Preparedness and Control Plan

This plan establishes policy and sets forth guidance, responsibilities and procedures utilized by Federal Electric Corp., communications department in support of the KSC Emergency Preparedness Plan, Annex A, Hurricane Control Plan (GP-355) dated 27 May 1971. This plan covers all FEC communications department personnel, facilities, and equipment situated at the Kennedy Space Center that are the responsibility of FEC contract NAS 10-4967.

Source record↗

Space Station Software Recommendations

Four panels of invited experts and NASA representatives focused on the following topics: software management, software development environment, languages, and software standards. Each panel deliberated in private, held two open sessions with audience participation, and developed recommendations for the NASA Space Station Program. The major thrusts of the recommendations were as follows: (1) The software management plan should establish policies, responsibilities, and decision points for software acquisition; (2) NASA should furnish a uniform modular software support environment and require its use for all space station software acquired (or developed); (3) The language Ada should be selected for space station software, and NASA should begin to address issues related to the effective use of Ada; and (4) The space station software standards should be selected (based upon existing standards where possible), and an organization should be identified to promulgate and enforce them. These and related recommendations are described in detail in the conference proceedings.

Voigt, S.↗

Safety policy and requirements for payloads using the space transportation system

The safety policy and requirements are established applicable to the Space Transportation System (STS) payloads and their ground support equipment (GSE). The requirements are intended to protect flight and ground personnel, the STS, other payloads, GSE, the general public, public-private property, and the environment from payload-related hazards. The technical and system safety requirements applicable to STS payloads (including payload-provided ground and flight supports systems) during ground and flight operations are contained.

Source record↗

The National Space Science Data Center: An operational perspective

The National Space Science Data Center (NSSDC) manages over 110,000 data tapes with over 4,000 data sets. The size of the digital archive is approximately 6,000 GBytes and is expected to grow to more than 28,000 GBytes by 1995. The NSSDC is involved in several initiatives to better serve the scientific community and improve the management of current and future data holdings. These initiatives address the need to manage data to ensure ready access by the user and manage the media to ensure continuing accessibility and integrity of the data. An operational view of the NSSDC, outlining current policies and procedures that have been implemented to ensure the effective use of available resources to support service and mission goals, and maintain compliance with prescribed data management directives is presented.

Blitstein, Ronald↗

How Public Private Partnerships Enable NASA Future Space Communication Needs

The NASA Space Communications and Navigation (SCaN) Program is responsible for providing communication and navigation services to scientific and human space exploration missions. SCaN's current Space Network provides radio frequency (RF) relay services to near Earth space missions via Tracking and Data Relay Satellites (TDRS). SCaN plans to offer a new generation of relay services beginning in 2025, including the addition of optical communications capabilities and enhanced RF capabilities. The primary drivers behind the development of these next generation relay network services are to enhance communication and navigation services with significantly reduced development and operational costs. Several approaches being considered for implementation of these services are through government owned capabilities, through commercial service providers, or a combination of the two. One approach receiving a great deal of attention is the use of Public-Private Partnerships (PPP) to develop and provide capabilities or services. Utilizing Public-Private Partnerships allows NASA and commercial entities to share the investment, standards, and risks of developing and testing new or enhanced capabilities which can benefit both NASA and the commercial space communication industry. The capabilities developed under the PPP can then be used to support the growth of the commercial satellite communications industry while simultaneously being introduced into NASA operations to provide service to future NASA missions as part of the NASA Next Generation Architecture. Partnerships formed for this purpose can also serve as the basis for further NASA acquisition activities where government and industry can continue to share the cost, risk, and benefits of space communications capability development and operations. This objective is consistent with the 2010 National Space Policy stated principles: "The United States is committed to encouraging and facilitating the growth of a U.S. commercial space sector that supports U.S. needs, is globally competitive, and advances U.S. leadership in the generation of new markets and innovation-driven entrepreneurship." [1]NASA has conducted several internal studies as well as externally funded studies with industry to define the next generation space communication architecture. NASA has approached the commercial industry through a Request for Information (RFI) to define further the next generation architecture and has conducted numerous internal and external studies. The results are promising and are shaping the approach to utilize Public Private Partnership to achieve NASA's objectives while reducing costs. The commercial satellite industry has begun to deploy high performance, high throughput global satellite constellations which have the potential to provide communication services to NASA Missions. Commercial satellite manufacturers have advanced their processes to rapidly design, build, and deliver, reliable communication satellites using minimum government oversight. In this paper, we will 1) describe the NASA Next Generation Architecture, Concept of Operations (ConOps), and salient characteristics; 2) Discuss the rational of Public-Private Partnerships to achieve NASA’s next generation communication architecture; and 3) Summarize the preliminary analysis performed to date and describe the path forward.

Stegeman, James↗

AstroMail: Electronic mail for the astrophysics community

As part of the NASA Science Internet User Support Services program, NASA Goddard was interested in R&D which could extend the SolarMail system developed by members of the Wilcox Space Observatory at Stanford University to support a larger astrophysics user community. Specific objectives of the R&D effort were to include: a clone of the existing SolarMail system with additional documentation, enabling a parallel mail system to be established by populating the database; a cloned version of SolarMail functioning with a user database similar to that of the High Energy Astrophysics Division (HEAD) of the American Astronomical Society; a report on the status and surveyed usage of SolarMail and its clones into an extendable distributed mail system to serve as the basis for AstroMail, including a draft declaration of policy; a prototype AstroMail system based on the above specifications and including at least SolarMail and one of its clones supporting a set of astronomy user databases as subsets; and a report on the status of the prototype AstroMail with recommendations for future modifications to AstroMail.

Scherrer, Phillip H.↗

A study of characteristics of intercity transportation systems. Phase 1: Definition of transportation comparison methodology

Decision making in early transportation planning must be responsive to complex value systems representing various policies and objectives. The assessment of alternative transportation concepts during the early initial phases of the system life cycle, when supportive research and technology development activities are defined, requires estimates of transportation, environmental, and socio-economic impacts throughout the system life cycle, which is a period of some 40 or 50 years. A unified methodological framework for comparing intercity passenger and freight transportation systems is described and is extended to include the comparison of long term transportation trends arising from implementation of the various R & D programs. The attributes of existing and future transportation systems are reviewed in order to establish measures for comparison, define value functions, and attribute weightings needed for comparing alternative policy actions for furthering transportation goals. Comparison criteria definitions and an illustrative example are included.

English, J. M.↗

Hydrologic and Agricultural Earth Observations and Modeling for the Water-Food Nexus

In a globalizing and rapidly-developing world, reliable, sustainable access to water and food are inextricably linked to each other and basic human rights. Achieving security and sustainability in both requires recognition of these linkages, as well as continued innovations in both science and policy. We present case studies of how Earth observations are being used in applications at the nexus of water and food security: crop monitoring in support of G20 global market assessments, water stress early warning for USAID, soil moisture monitoring for USDA's Foreign Agricultural Service, and identifying food security vulnerabilities for climate change assessments for the UN and the UK international development agency. These case studies demonstrate that Earth observations are essential for providing the data and scalability to monitor relevant indicators across space and time, as well as understanding agriculture, the hydrological cycle, and the water-food nexus. The described projects follow the guidelines for co-developing useable knowledge for sustainable development policy. We show how working closely with stakeholders is essential for transforming NASA Earth observations into accurate, timely, and relevant information for water-food nexus decision support. We conclude with recommendations for continued efforts in using Earth observations for addressing the water-food nexus and the need to incorporate the role of energy for improved food and water security assessments

Food Security↗

Know Before You Go: A Community-Derived Approach to Planning for and Preventing Sexual Harassment at Oceanographic Field Sites

Sexual harassment is a pervasive problem on oceanographic research vessels and while conducting fieldwork in general. A variety of factors contribute to inadequate protection against sexual harassment, such as poor training in prevention, support, and response; the remoteness of field sites; academic hierarchies that reinforce uneven power dynamics that extend to fieldwork; and multi-institutional teams with distinct policies or reporting structures that can lead to confusion in reporting and responding to incidents in the field. In compromising individuals’ physical and mental health, sexual harassment can negatively affect research expeditions. For example, harassed individuals may decide to refrain from working on complicated team-based tasks, which can be a safety issue. A broader concern is that sexual harassment deters talented people from pursing or maintaining employment in ocean science. Harassment must be treated with the same gravity as research misconduct and safety policy infringements. When planning a research expedition, science team leaders are responsible for the safety of their team and other colleagues aboard and would benefit from resources aimed at helping team leadership create a plan to ensure safety and inclusivity. To address this resource gap and support consistent safety preparedness, 18 participants in the Workshop to Promote Field Safety in Ocean Sciences, convened by the Consortium for Ocean Leadership and held May 17-18, 2022, in Washington, D.C., developed a checklist for use by scientific leaders and others to assist in planning for participant safety and to prevent harassment the field. The checklist specifies the timing of, and who is responsible for, specific actions that should be taken to improve safety while conducting fieldwork, whether on a research vessel or on land. It also provides additional resources and suggestions for leaders on how to amend the checklist to address their specific fieldwork situations.

Oceanography↗

NASA support for commerce in space - Broadening opportunities

The status of the NASA Office of Commercial Program's initiatives to implement the 1988 commercial space policy and expand industrial interest in the commercial development of space in the post-Challenger era is presented. Specific objectives have been developed to capture the drive and creativity of the private sector, for increasing NASA's effectiveness in conducting business with industrial firms, and impacting the commercial space market. An aggressive, comprehensive, and forward-looking program has been defined which provides the type of infrastructure and organization required to bring industry into the mainstream of space activities.

Stone, Barbara A.↗

TAVERNS and the space station software support environment

The Space Station Information System (SSIS) provides the data processing capability for the Space Station Program (SSP). The Software Support Environment (SSE) System for the SSP is the collection of software, procedures, standards, hardware specification, documentation, policy, and training materials. The Ada programming language was baselined by the Space Station Program Office as the language for development and maintenance of all space station software including the software of the SSE itself. The Test And Validation Environment for Remote Networked Systems (TAVERNS) is a distributed philosophy for development and validation of Ada applications software for the space station and as such is closely related to the SSE. An overview of the system is provided.

Howes, Norman R.↗

International Space Station operations: New dimensions - October 13, 1987

One of the principal goals of the participants in the International Space Station program is to provide a management support structure which is equitable and fair to all participants, responsive to the needs of users, responsible to other partners, and mutually supportive to the participation of other partners. Shared-utilization, shared-cost, and shared-operations policies considerations are discussed. Special attention is given to the methodology for identifying costs and benefits of this program, in which each partner should be provided with benefits in proportion to his contribution, and no partner would be forced to share in cost the inefficiencies introduced by other partners. The Space Station hierarchy of operations functions are identified, and the recommended framework planning and control hierarchy is presented.

Paules, Granville E.↗