SEARCH · Search NASA
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.
Spacecraft extended mission coverage does not generally carry a high priority, but Helios was fortunate in that a combination of separated viewperiods and unique utilization of the STDN Goldstone antenna have provided a considerable amount of additional science data return, particularly at key times such a perihelion and/or solar occultation.
The crop calendars produced for the Large Area Crop Inventory Experiment (LACIE) and crop calendar samples for Colorado, Iowa, Kansas, Minnesota, Montana, Nebraska, North Dakota, South Dakota, and Texas are presented. These calendars are based on weekly crop reporting district level observations of the percentage of various crops at several growth stages. A sample of the statistical treatments of the weekly data is provided. Four to five years of 50-percent dates for stages on a crop reporting district level for Arkansas, Iowa, Kentucky, Louisiana, Michigan, Mississippi, Ohio and Wisconsin are also given.
Development of a given technology for national defense and large systems developments when the task is too large or risky for entrepreneurs, yet is clearly in the best interest of the nation are discussed. Advanced research to identify areas of interest was completed. Examples of commercial opportunities are the McDonnell-Douglas Corporation purification process for pharmaceutical products and the Microgravity Research Associates process for growing gallium arsenide crystals in space.
This addendum to the final report provides a description of the work performed under the subject contract. This report describes the work that was performed by SRS Technologies from Jan. 1992 - Jan. 1993. The work that was performed included the following: (1) a study of the Space Station Freedom (SSF) Preliminary Design Review (PDR) data package and an identification of the maintenance concept, structure, implementation plans, training plan, and the LSAR approach; development of a working ability with the ALSTAR and DATA Express software; (3) a review of the SSF maintenance concept; and (4) an update of the ALSTAR data base.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Substantial progress has been made toward the goals of this research effort in the past six months. A simplified rotor model with a flexible shaft and backup bearings has been developed. The model is based upon the work of Ishii and Kirk. Parameter studies of the behavior of this model are currently being conducted. A simple rotor model which includes a flexible disk and bearings with clearance has been developed and the dynamics of the model investigated. The study consists of simulation work coupled with experimental verification. The work is documented in the attached paper. A rotor model based upon the T-501 engine has been developed which includes backup bearing effects. The dynamics of this model are currently being studied with the objective of verifying the conclusions obtained from the simpler models. Parallel simulation runs are being conducted using an ANSYS based finite element model of the T-501.
Progress over the past year includes the following: A simplified rotor model with a flexible shaft and backup bearings has been developed. A simple rotor model which includes a flexible disk and bearings with clearance has been developed and the dynamics of the model investigated. A rotor model based upon the T-501 engine has been developed which includes backup bearing effects. Parallel simulation runs are being conducted using an ANSYS based finite element model of the T-501. The magnetic bearing test rig is currently floating and dynamics/control tests are being conducted. A paper has been written that documents the work using the T-501 engine model. Work has continued with the simplified model. The finite element model is currently being modified to include the effects of foundation dynamics. A literature search for material on foil bearings has been conducted. A finite element model is being developed for a magnetic bearing in series with a foil backup bearing.
The test indicate that "an indiscriminate single application of the Southwell method (for analyzing Exp. Observations in problems of elastic stability)--can result in definite and measurable errors" The test also indicate "that the effect of curvature due to bending on the critical load for the compression flange material of a box beam is probably small and can be neglected." We have not found this to be true in our tests. It is believed that the effect of curvature, together with a small amount of fixity at the ribs, tends to force the stiffeners to bow in each bay thus effectively increasing their end fixity and thereby raising their allowable loads.
Hurricane Katrina was responsible for trapping 25,000 people in the New Orleans Superdome and isolating many others throughout Louisiana and Mississippi. The transport of these evacuees to the Reliant Park (Houston, Texas) used 500 buses each containing about 55 people. Processing the arriving evacuees included addressing their health status and medical needs as follows: an initial triage at disembarkation, a secondary triage in the Reliant Astrodome and Center, and definitive clinical care in the Reliant Arena "Katrina" Clinic. Baylor College of Medicine (BCM) physicians boarded buses and identified the sickest for emergency transport to Harris County Hospital District (HCHD) hospitals. BCM departments represented included pediatrics, family and community medicine, internal medicine, radiology, obstetrics and gynecology, orthopedics, surgery, and psychiatry. Astrodome and Center triage was managed by BCM physicians and staffed by HCHD Nurses and volunteers from Texas and beyond. The Reliant Astrodome, Center and Arena reached peak headcounts of 15,000,4500, and 2500, respectively Most evacuees visiting the triage sites in the Astrodome and Center were treated using "over-the-counter" medications with the remaining being transported to the "Katrina" clinic. The clinic was equipped with a lab, pharmacy, digital X-ray, and ultrasound machines in addition to electronic patient records created using 80 computer terminals. The Katrina clinic saw more than 15,000 patients during 15 days of operations (2,000 on the first full day), administered 10,000 tetanus shots, and filled thousands of prescriptions. At the peak of operations, the clinic saw 150 patients/hour with 25 physicians scheduled for each 12-hour shift. Approximately 900 people were transported to hospital emergency rooms. Within 3 weeks of arriving at the Reliant Park facilities, more than 90% of the families found permanent housing, enrolled children in schools, and found work. Using data obtained from manual and electronic medical records, this presentation will document the major milestones and lessons learned from this extraordinary project to help the Katrina evacuees.
Juniperus spp. pollen is a significant aeroallergen that can be transported 200-600 km from the source. Local observations of Juniperus spp. phenology may not be consistent with the timing and source of pollen collected by pollen sampling instruments. Methods: The Dust REgional Atmospheric Model (DREAM)is a verified model for atmospheric dust transport modeling using MODIS data products to identify source regions and quantities of dust. We successfully modified the DREAM model to incorporate pollen transport (PREAM) and used MODIS satellite images to develop Juniperus ashei pollen input source masks. The Pollen Release Potential Source Map, also referred to as a source mask in model applications, may use different satellite platforms and sensors and a variety of data sets other than the USGS GAP data we used to map J. ashei cover type. MODIS derived percent tree cover is obtained from MODIS Vegetation Continuous Fields (VCF) product (collection 3 and 4, MOD44B, 500 and 250 m grid resolution). We use updated 2010 values to calculate pollen concentration at source (J. ashei ). The original MODIS derived values are converted from native approx. 250 m to 990m (approx. 1 km) for the calculation of a mask to fit the model (PREAM) resolution. Results: The simulation period is chosen following the information that in the last 2 weeks of December 2010. The PREAM modeled near-surface concentrations (Nm-3) shows the transport patterns of J. ashei pollen over a 5 day period (Fig. 2). Typical scales of the simulated transport process are regional.
Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere was heightened from Airports to the communication among the military branches legionnaires. With advanced persistent threats (APTs) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated and secured state in a launch control system environment. FISMA is a law that is mandated by the government to follow when government agencies secure networks and devices. My role on this project is to ensure network devices and systems are in compliance with NIST, as outlined in FISMA. I will achieve this by providing assistance with security plan documentation and collection, system hardware and software inventory, malicious code and malware scanning and configuration of network devices i.e. routers and IDSsIPSs. In addition I will be completing security assessments on software and hardware, vulnerability assessments and reporting, conducting patch management and risk assessments. A guideline that will help with compliance with NIST is the SANS Top 20 Critical Controls. SANS Top 20 Critical Controls as well as numerous security tools, security software and the conduction of research will be used to successfully complete the tasks given to me. This will ensure compliance with FISMA and NIST, secure systems and a secured network. By the end of this project, I hope to have carried out stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, policies and procedures.
Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere has heightened from airports to the communication among the military branches legionnaires. With advanced persistent threats (APT's) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated and secured state in a launch control system environment. FISMA is a law that is mandated by the government to follow when government agencies secure networks and devices. My role on this project is to ensure network devices and systems are in compliance with NIST, as outlined in FISMA. I will achieve this by providing assistance with security plan documentation and collection, system hardware and software inventory, malicious code and malware scanning, and configuration of network devices i.e. routers and IDS's/IPS's. In addition, I will be completing security assessments on software and hardware, vulnerability assessments and reporting, and conducting patch management and risk assessments. A guideline that will help with compliance with NIST is the SANS Top 20 Critical Controls. SANS Top 20 Critical Controls as well as numerous security tools, security software and the conduction of research will be used to successfully complete the tasks given to me. This will ensure compliance with FISMA and NIST, secure systems and a secured network. By the end of this project, I hope to have carried out the tasks stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, as well as policies and procedures.
No abstract available
The Ares I design and development program made the determination early in the System Design Review Phase to utilize DoD ILS and LSA approach for supportability engineering as an integral part of the system engineering process. This paper is to provide a review of the overall approach to design Ares-I with an emphasis on a more affordable, supportable, and sustainable launch vehicle. Discussions will include the requirements development, design influence, support concept alternatives, ILS and LSA planning, Logistics support analyses/trades performed, LSA tailoring for NASA Ares Program, support system infrastructure identification, ILS Design Review documentation, Working Group coordination, and overall ILS implementation. At the outset, the Ares I Project initiated the development of the Integrated Logistics Support Plan (ILSP) and a Logistics Support Analysis process to provide a path forward for the management of the Ares-I ILS program and supportability analysis activities. The ILSP provide the initial planning and coordination between the Ares-I Project Elements and Ground Operation Project. The LSA process provided a system engineering approach in the development of the Ares-I supportability requirements; influence the design for supportability and development of alternative support concepts that satisfies the program operability requirements. The LSA planning and analysis results are documented in the Logistics Support Analysis Report. This document was required during the Ares-I System Design Review (SDR) and Preliminary Design Review (PDR) review cycles. To help coordinate the LSA process across the Ares-I project and between programs, the LSA Report is updated and released quarterly. A System Requirement Analysis was performed to determine the supportability requirements and technical performance measurements (TPMs). Two working groups were established to provide support in the management and implement the Ares-I ILS program, the Integrated Logistics Support Working Group (ILSWG) and the Logistics Support Analysis Record Working Group (LSARWG). The Ares I ILSWG is established to assess the requirements and conduct, evaluate analyses and trade studies associated with acquisition logistic and supportability processes and to resolve Ares I integrated logistics and supportability issues. It established a strategic collaborative alliance for coordination of Logistics Support Analysis activates in support of the integrated Ares I vehicle design and development of logistics support infrastructure. A Joint Ares I - Orion LSAR Working Group was established to: 1) Guide the development of Ares-I and Orion LSAR data and serve as a model for future Constellation programs, 2) Develop rules and assumptions that will apply across the Constellation program with regards to the program's LSAR development, and 3) Maintain the Constellation LSAR Style Guide.
In 2014, the Inter-agency Operations Advisory Group (IOAG) chartered a multi-agency team effort to study how to best handle spacecraft emergency as part of cross support among network assets. The original intent is to put in place for the first time a process and guidelines to make emergency support as part of a permanent cross-support capability between space agencies. From the perspective of space communications service providers, a few key issues, common to all agencies, concerning the Spacecraft Emergency Cross Support (SECS) have been explored. They are: context of emergency support, provision of emergency support under a cross-support agreement, provision of emergency support with no cross-support agreement, legal and liability issues, response time, support priority, services provided, sustaining emergency support capabilities, and charge for the support. The positions of the various participating agencies with respect to these issues have been collected, analyzed, and finally harmonized to form the recommended IOAG positions. A central challenge most communications service providers are facing is that since the spacecraft emergency is an unplanned critical event, it typically requires fast response to the emergency call, hence lacking an international standard process for the operational interfaces seems to exacerbate the difficulty in providing SECS. For reducing the response time, i.e. from the time of accepting a request for SECS to the readiness for support, it is recommended that a “cross-support emergency system” be established by IOAG member agencies. Along with it, the IOAG core services, just-in-time ground communications line, cross support service management (CSSM), and standard operations procedures (SOP) for operational interfaces form the basic foundation of the “cross support emergency system”. Of the above, new to the cross support conducted thus far in the IOAG community is the concept of the SOP specifically for the interfaces between the service provider and service user during the SECS. Use cases, salient features, and definition of the key operational activities/tasks relevant to the interfaces are addressed by the effort. Underpinning such a system is the availability of the RF license granted by the local authority, at national and/or regional level, for a given ground station to communicate with and track the spacecraft in emergency mode at the uplink and downlink frequencies assigned to that spacecraft. That means it is critical for the IOAG member agencies to obtain a priori all-band licenses (for the entire X-band or S-band) for some, if not all, of their ground stations that are most capable of or likely to provide SECS. It is also recommended that certain prior arrangements be made with the relevant local licensing authorities for a process that will allow expedited authorization to transmit/receive signals to/from the declared spacecraft over the declared ground stations specifically and solely for the emergency case. Our analysis of the SECS has also uncovered a few fundamental programmatic issues. Recognizing any IOAG positions reached on these issues do not necessarily lead to any binding authority, it is recommended that they, along with those key attributes of the cross support emergency system, be explicitly stated as multi-agency guidelines to guide the implementation and provision of the SECS. The paper will present the results of the working group on Spacecraft Emergency Cross Support and, in particular, its findings, products and recommendations. It will also identify the next steps of this work that may include the production of some international standards as an extension of this work, or the process to make this emergency system usable by other spacecraft operators beyond the space agencies.
In 2014, the Inter-agency Operations Advisory Group (IOAG) chartered a multi-agency team effort to study how to best handle spacecraft emergency as part of cross support among network assets. The original intent is to put in place for the first time a process and guidelines to make emergency support as part of a permanent cross-support capability between space agencies. From the perspective of space communications service providers, a few key issues, common to all agencies, concerning the Spacecraft Emergency Cross Support (SECS) have been explored. They are: context of emergency support, provision of emergency support under a cross-support agreement, provision of emergency support with no cross-support agreement, legal and liability issues, response time, support priority, services provided, sustaining emergency support capabilities, and charge for the support. The positions of the various participating agencies with respect to these issues have been collected, analyzed, and finally harmonized to form the recommended IOAG positions. A central challenge most communications service providers are facing is that since the spacecraft emergency is an unplanned critical event, it typically requires fast response to the emergency call, hence lacking an international standard process for the operational interfaces seems to exacerbate the difficulty in providing SECS. For reducing the response time, i.e. from the time of accepting a request for SECS to the readiness for support, it is recommended that a “cross-support emergency system” be established by IOAG member agencies. Along with it, the IOAG core services, just-in-time ground communications line, cross support service management (CSSM), and standard operations procedures (SOP) for operational interfaces form the basic foundation of the “cross support emergency system”. Of the above, new to the cross support conducted thus far in the IOAG community is the concept of the SOP specifically for the interfaces between the service provider and service user during the SECS. Use cases, salient features, and definition of the key operational activities/tasks relevant to the interfaces are addressed by the effort. Underpinning such a system is the availability of the RF license granted by the local authority, at national and/or regional level, for a given ground station to communicate with and track the spacecraft in emergency mode at the uplink and downlink frequencies assigned to that spacecraft. That means it is critical for the IOAG member agencies to obtain a priori all-band licenses (for the entire X-band or S-band) for some, if not all, of their ground stations that are most capable of or likely to provide SECS. It is also recommended that certain prior arrangements be made with the relevant local licensing authorities for a process that will allow expedited authorization to transmit/receive signals to/from the declared spacecraft over the declared ground stations specifically and solely for the emergency case. Our analysis of the SECS has also uncovered a few fundamental programmatic issues. Recognizing any IOAG positions reached on these issues do not necessarily lead to any binding authority, it is recommended that they, along with those key attributes of the cross support emergency system, be explicitly stated as multi-agency guidelines to guide the implementation and provision of the SECS. The paper will present the results of the working group on Spacecraft Emergency Cross Support and, in particular, its findings, products and recommendations. It will also identify the next steps of this work that may include the production of some international standards as an extension of this work, or the process to make this emergency system usable by other spacecraft operators beyond the space agencies.