Search NASA⌕ Search

SEARCH · Search NASA

Results for “office building”

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 289 records · Page 16

Next Generation CTAS Tools

The FAA's Free Flight Phase 1 Office is in the process of deploying the current generation of CTAS tools, which are the Traffic Management Advisor (TMA) and the passive Final Approach Spacing Tool (pFAST), at selected centers and airports. Research at NASA is now focussed on extending the CTAS software and computer human interfaces to provide more advanced capabilities. The Multi-center TMA (McTMA) is designed to operate at airports where arrival flows originate from two or more centers whose boundaries are in close proximity to the TRACON boundary. McTMA will also include techniques for routing arrival flows away from congested airspace and around airspace reserved for arrivals into other hub airports. NASA is working with FAA and MITRE to build a prototype McTMA for the Philadelphia airport. The active Final Approach Spacing Tool (aFAST) provides speed and heading advisories to help controllers achieve accurate spacing between aircraft on final approach. These advisories will be integrated with those in the existing pFAST to provide a set of comprehensive advisories for controlling arrival traffic from the TRACON boundary to touchdown at complex, high-capacity airports. A research prototype of aFAST, designed for the Dallas-Fort Worth is in an advanced stage of development. The Expedite Departure Path (EDP) and Direct-To tools are designed to help controllers guide departing aircraft out of the TRACON airspace and to climb to cruise altitude along the most efficient routes.

Erzberger, Heinz↗

Scalable Asset Discovery, Vulnerability Scanning, and Penetration Testing for Remote Sites and Wireless Spectrums Utilizing an Embedded Linux Plug - PwniPlug and the Raspberry Pi B+ as a Sample Pen Test

All devices attached to the NASA KSC network are subject to security vulnerability scanning and/or penetration testing. In today's changing environment, vulnerable and/or unprotected systems can easily be overlooked. Systems that are not properly managed can become a potential threat to the operational integrity of our systems and networks. This includes all NASA (internal and external) information systems within NASA KSC Internet Protocol (IP) address space, and NASA KSC facilities. The Office of the Chief Information Officer (OCIO) recommends that all NASA Centers and information systems be subject to penetration testing on a regular interval in accordance with the guidelines identified by the National Institute of Standards and Technology (NIST). (ITS-HBK-2810.04-02A) Protecting information and equipment at NASA is an area of increasing concern. In addition to the CPU's on the network; Supervisory, Control and Data Acquisition (SCADA) systems are especially vulnerable because these systems have lacked standards, use embedded controllers with little computational power and informal software, are connected to physical processes, have few operators, and are increasingly also being connected to corporate networks. The scope of work is comprised of several individual components which together build upon previous work by Drew Branch, NASA KSC Intern. The Pwn Plug is the selected COTS (Commercial-Off-The-Shelf) device chosen to test simplification of mandatory IT Security tasks. The device will be utilized to provide services to NASA KSC and enable an assessment of infrastructure soundness and regulatory compliance in an efficient, economical, and business responsive manner. The Pwn Plug is designed as a pen testing appliance which provides a hardware platform that can support commercial penetration testing efforts at significantly reduced costs. The expected outcomes are: 1) External Penetration Testing, 2) Social Engineering, 3) Procedural Documentation, 4) Recommended Remediation Action Plan, 5) System Retest & Remediation Attestation and 6) Final Reports, out briefing and Presentation. Due to physical and material constraints beyond intern and mentor control, the project was redefined as a working pen-test scenario. Limitations of lab availability and tools dictated an academic exercise. This report was developed within the scenario guidelines suggested by the project mentor. The guidelines were to be creative in developing a Pen Test program for a client.

Penetration Testing↗

NASA Planning for Orion Multi-Purpose Crew Vehicle Ground Operations

The NASA Orion Ground Processing Team was originally formed by the Kennedy Space Center (KSC) Constellation (Cx) Project Office's Orion Division to define, refine and mature pre-launch and post-landing ground operations for the Orion human spacecraft. The multidisciplined KSC Orion team consisted of KSC civil servant, SAIC, Productivity Apex, Inc. and Boeing-CAPPS engineers, project managers and safety engineers, as well as engineers from Constellation's Orion Project and Lockheed Martin Orion Prime contractor. The team evaluated the Orion design configurations as the spacecraft concept matured between Systems Design Review (SDR), Systems Requirement Review (SRR) and Preliminary Design Review (PDR). The team functionally decomposed prelaunch and post-landing steps at three levels' of detail, or tiers, beginning with functional flow block diagrams (FFBDs). The third tier FFBDs were used to build logic networks and nominal timelines. Orion ground support equipment (GSE) was identified and mapped to each step. This information was subsequently used in developing lower level operations steps in a Ground Operations Planning Document PDR product. Subject matter experts for each spacecraft and GSE subsystem were used to define 5th - 95th percentile processing times for each FFBD step, using the Delphi Method. Discrete event simulations used this information and the logic network to provide processing timeline confidence intervals for launch rate assessments. The team also used the capabilities of the KSC Visualization Lab, the FFBDs and knowledge of the spacecraft, GSE and facilities to build visualizations of Orion pre-launch and postlanding processing at KSC. Visualizations were a powerful tool for communicating planned operations within the KSC community (i.e., Ground Systems design team), and externally to the Orion Project, Lockheed Martin spacecraft designers and other Constellation Program stakeholders during the SRR to PDR timeframe. Other operations planning tools included Kaizen/Lean events, mockups and human factors analysis. The majority of products developed by this team are applicable as KSC prepares 21st Century Ground Systems for the Orion Multi-Purpose Crew Vehicle and Space Launch System.

Letchworth, Gary↗

Adaptive Curation at NASA Johnson Space Center: Preparing for Artemis Samples by Leveraging Proven Practices and Innovative Solution

The proper curation of returned astromaterial samples is essential to ensure that high-quality scientific investigations can be conducted for decades, enabling future generations to address evolving research questions. The Astromaterials Acquisition and Curation Office at NASA Johnson Space Center (hereafter JSC Curation) is responsible for curating all of NASA’s extraterrestrial samples. Under the governing document, NASA Procedural Requirement (NPR) 7100.5 “Curation of Extraterrestrial Materials”, JSC Curation is charged with “The curation of all extraterrestrial material under NASA control, including future NASA missions.” The Directive goes on to define Curation as including “...documentation, preservation, preparation, and distribution of samples for research, education, and public outreach.” JSC Curation has a long-standing legacy of curating extraterrestrial materials, including but not limited to Apollo and Luna lunar samples, Genesis solar wind samples, Stardust comet samples, asteroid samples (Hayabusa1, Hayabusa2, and OSIRIS-REx), and Antarctic Meteorite samples from a variety of parent bodies. Building on this foundation, the Artemis program introduces new challenges and opportunities for sample curation, requiring both the application of proven practices and the development of innovative solutions. The Artemis Collection will be curated using established protocols refined through decades of experience with Apollo and subsequent sample collections, including but not limited to the utilization of cleanrooms, custom nitrogen gloveboxes, specialized storage containers and tools; all of which have strict material utilization and prohibition requirements. These practices provide a robust framework for contamination control, documentation, and long-term preservation. However, Artemis samples may present unique scientific and operational requirements, including enhanced contamination control measures (relative to Apollo) driven by evolving science objectives. To meet these needs, JSC Curation is actively developing new technologies and protocols that extend beyond traditional approaches, ensuring that the integrity of samples is maintained under increasingly stringent standards. One critical area of innovation is the development of cold sample curation capabilities. Certain Artemis samples, particularly those from Permanently Shadowed Regions (PSRs) and cold environments, are expected to contain ices and volatile components that require preservation and handling at sub-zero or even cryogenic temperatures. JSC Curation is leveraging best practices from the cold and cryogenic sample industries, as well as other government agencies and academic experts, to design facilities and handling procedures that maintain sample integrity while enabling scientific access. The goal is to develop capabilities to allow researchers to investigate volatiles and other temperature-sensitive materials while minimizing chemical and physical alterations from their returned state. In summary, adaptive curation at JSC combines the reliability of proven methodologies with forward-looking innovations to meet the scientific and operational demands of Artemis. Through enhanced contamination control, advanced cold curation capabilities, and an understanding of known and evolving future science priorities, NASA is preparing to maximize the scientific return from Artemis samples and preserve their value for generations of researchers.

Andrea D Harrington↗

Building Supply Chain Visibility for Risk Management: Illuminating the COVID-19 Pandemic Impact Upon NASA Suppliers

NASA mission projects rely upon global supply chains subject to an array of risks that threaten to disrupt or deny the timely, affordable provision of products and services as required for mission success. Visibility into these supply chains is key to the management of risks, such as those stemming from the coronavirus pandemic and its associated effects upon suppliers. Accordingly, the Supplier Research and Analysis (SRA) Program within Goddard Space Flight Center’s Safety and Mission Assurance (SMA) Directorate produced the COVID-19 pandemic/NASA suppliers dashboard as part of the NASA Meta Information System. The dashboard provides visibility and situational awareness to aid risk assessment, planning and decision-making over the course of the pandemic recovery phase. The approach of integrating data and information into visual dashboard displays has also been employed by the SRA Program to focus on specific risks pertaining to foreign-based suppliers. This webinar is presented by the NASA Office of SMA and its Supply Chain Risk Management Program, in collaboration with the NASA Safety Center and Goddard’s SMA Directorate.

supplier research and analysis, supply chain risk ↗

The foundations of reusability: Successful experience and important conclusions from planning and scheduling of space operations

NASA's Office of Space Communications is sponsoring a combined technical and management initiative to dramatically decrease the cost of preparing for and conducting space operations. The authors present their successful experience and important conclusions from producing generalized and readily reusable solutions and systems for planning and scheduling applications. While generality by itself should enable reuse, generality alone may not produce the desired cost savings. Generality achieved by accumulating numerous special cases within a software system often increases the complexity of the software to the extent that maintenance costs overtake development savings. Because of this phenomenon, the authors have insisted on simplicity, as well as generality, to achieve cost-effective operation reusability. Simplicity and generality can be accomplished simultaneously when the basic 'Building Blocks' for a problem domain, in this paper, planning and scheduling, are discovered and implemented with reuse in mind. The Building Blocks for planning and scheduling are described. The authors also present examples of how these Building Blocks have accommodated various scenarios that were previously treated as mission-peculiar. Two case histories are presented to demonstrate operational reusability and cost effectiveness.

Hornstein, Rhoda Shaller↗

NASA Orbital Debris Radar Measurements by the Haystack Ultra-wideband Satellite Imaging Radar (HUSIR)

For many years, the NASA Orbital Debris Program Office (ODPO) has partnered with the U.S. Department of Defense and the Massachusetts Institute of Technology Lincoln Laboratory (MIT/LL) to collect data on the orbital debris environment using the Haystack radar. These measurements are used to characterize the small debris environment in low Earth orbit (LEO), down to a noise-limited size of approximately 5 mm—depending on altitude. The Haystack radar operated by MIT/LL underwent upgrades starting in May 2010, with operations resuming in 2014 as the Haystack Ultra-wideband Satellite Imaging Radar (HUSIR). HUSIR is the primary source of data used by the ODPO to statistically sample orbital debris in the 5-mm to 10-cm size regime in LEO and is a key source of data to build and validate the NASA Orbital Debris Engineering Model. In this presentation, we will present recent HUSIR results and show how NASA uses them to understand the orbital debris environment.

Mark Matney↗

Sustainable Development in Algeria’s Urban Areas: Population Growth and Land Consumption

We analyzed the urban development sustainability in five major urban areas of Algeria by the standard of the UN Sustainability Development Goal indicator SDG 11.3.1, which focuses on the ratio of land consumption rate to population growth rate. We utilized the annual global artificial impervious area (GAIA) dataset to characterize land-use and population data from the two censuses carried out by the National Office of Statistics (ONS) for 2008 and 2018. We discuss the prevailing relationship between urban land consumption rate and population growth rate at the smallest territorial and population census unit scale. We confirm that the indicator SDG 11.3.1 is nonlinear and that while, for example, the wilaya of Tlemcen as a whole appears to be on a sustainable path, twenty-one of its communes are not. We found that overall, and for most of its communes, the wilaya of Oran seems to have an urban land use commensurable to its population growth, but in the wilaya of Algiers, out of fifty-seven communes, only fourteen have a tendency towards sustain-able development. However, the latter wilaya hosts the country’s capital and includes government buildings that are uninhabited but are accounted for as land consumed, and as such, the relationship between urban land consumption and population growth is biased. The wilaya of Annaba showed large discrepancies in terms of land use and population growth rates, and the evolution of these quantities is not homogenous across communes and not sustainable. In the Saharan wilaya of Ghardaia, the development is not homogeneous in all communes, with smaller communes undergoing buildup increases of more than 150% over the decade. Finally, in all communes where population growth exceeded urban land growth, there will be overcrowding, an aspect neither the SDG 11.3.1 nor the impervious surface per capita indicator captures. This result, in addition to other limitations, makes SDG 11.3.1 incomplete for the determination of the sustainable development in urban areas.

Algeria↗

Bion-11 Spaceflight Mission

The Sensors 2000! Program, in support of the Space Life Sciences Payloads Office at NASA Ames Research Center developed a suite of bioinstrumentation hardware for use on the Joint US/Russian Bion I I Biosatellite Mission (December 24, 1996 - January 7, 1997). This spaceflight included 20 separate experiments that were organized into a complimentary and interrelated whole, and performed by teams of US, Russian, and French investigators. Over 40 separate parameters were recorded in-flight on both analog and digital recording media for later analysis. These parameters included; Electromyogram (7 ch), Electrogastrogram, Electrooculogram (2 ch), ECG/EKG, Electroencephlogram (2 ch), single fiber firing of Neurovestibular afferent nerves (7 ch), Tendon Force, Head Motion Velocity (pitch & yaw), P02 (in vivo & ambient), temperature (deep body, skin, & ambient), and multiple animal and spacecraft performance parameters for a total of 45 channels of recorded data. Building on the close cooperation of previous missions, US and Russian engineers jointly developed, integrated, and tested the physiologic instrumentation and data recording system. For the first time US developed hardware replaced elements of the Russian systems resulting in a US/Russian hybrid instrumentation and data system that functioned flawlessly during the 14 day mission.

Skidmore, M.↗

Application of the Life Safety Code to a Historic Test Stand

NASA has conducted a study to assess alternatives to refurbishing existing launch vehicle modal test facilities as opposed to developing new test facilities to meet the demands of a very fiscally constrained test and evaluation environment. The results of this study showed that Marshall Space Flight Center (MSFC) Test Stand (TS) 4550 could be made compliant, within reasonable cost and schedule impacts, if safety processes and operational limitations were put in place to meet the safety codes and concerns of the Fire Marshall. Trades were performed with key selection criteria to ensure that appropriate levels of occupant safety are incorporated into test facility design modifications. In preparation for the ground vibration tests that were to be performed on the Ares I launch vehicle, the Ares Flight and Integrated Test Office (FITO) organization evaluated the available test facility options, which included the existing mothballed structural dynamic TS4550 used by Apollo and Shuttle, alternative ground vibration test facilities at other locations, and construction of a new dynamic test stand. After an exhaustive assessment of the alternatives, the results favored modifying the TS4550 because it was the lowest cost option and presented the least schedule risk to the NASA Constellation Program for Ares Integrated Vehicle Ground Vibration Test (IVGVT). As the renovation design plans and drawings were being developed for TS4550, a safety concern was discovered the original design for the construction of the test stand, originally built for the Apollo Program and renovated for the Shuttle Program, was completed before NASA s adoption of the currently imposed safety and building codes per National Fire Protection Association Life Safety Code [NFPA 101] and International Building Codes. The initial FITO assessment of the design changes, required to make TS4550 compliant with current safety and building standards, identified a significant cost increase and schedule impact. An effort was launched to thoroughly evaluate the applicable life safety requirements, examine the context in which they were derived, and determine a means by which the TS4550 modifications could be made within budget and on schedule, while still providing the occupants with appropriate levels of safety.

Askins, Bruce↗

The Experimental Regional Ensemble Forecast System (ExREF): Its Use in NWS Forecast Operations and Preliminary Verification

The Experimental Regional Ensemble Forecast (ExREF) system is a tool for the development and testing of new Numerical Weather Prediction (NWP) methodologies. ExREF is run in near‐realtime by the Global Systems Division (GSD) of the NOAA Earth System Research Laboratory (ESRL) and its products are made available through a website, an ftp site, and via the Unidata Local Data Manager (LDM). The ExREF domain covers most of North America and has 9‐km horizontal grid spacing. The ensemble has eight members, all employing WRF‐ARW. The ensemble uses a variety of initial conditions from LAPS and the Global Forecasting System (GFS) and multiple boundary conditions from the GFS ensemble. Additionally, a diversity of physical parameterizations is used to increase ensemble spread and to account for the uncertainty in forecasting extreme precipitation events. ExREF has been a component of the Hydrometeorology Testbed (HMT) NWP suite in the 2012‐2013 and 2013‐2014 winters. A smaller domain covering just the West Coast was created to minimize band‐width consumption for the NWS. This smaller domain has and is being distributed to the National Weather Service (NWS) Weather Forecast Office and California Nevada River Forecast Center in Sacramento, California, where it is ingested into the Advanced Weather Interactive Processing System (AWIPS I and II) to provide guidance on the forecasting of extreme precipitation events. This paper will review the cooperative effort employed by NOAA ESRL, NASA SPoRT (Short‐term Prediction Research and Transition Center), and the NWS to facilitate the ingest and display of ExREF data utilizing the AWIPS I and II D2D and GFE (Graphical Software Editor) software. Within GFE is a very useful verification software package called BoiVer that allows the NWS to utilize the River Forecast Center's 4 km gridded QPE to compare with all operational NWP models 6‐hr QPF along with the ExREF mean 6‐hr QPF so the forecasters can build confidence in the use of the ExREF in preparing their rainfall forecasts. Preliminary results will be presented.

Reynolds, David↗

Probabilistic Survivability Versus Time Modeling

This presentation documents Kennedy Space Center's Independent Assessment work completed on three assessments for the Ground Systems Development and Operations (GSDO) Program to assist the Chief Safety and Mission Assurance Officer during key programmatic reviews and provided the GSDO Program with analyses of how egress time affects the likelihood of astronaut and ground worker survival during an emergency. For each assessment, a team developed probability distributions for hazard scenarios to address statistical uncertainty, resulting in survivability plots over time. The first assessment developed a mathematical model of probabilistic survivability versus time to reach a safe location using an ideal Emergency Egress System at Launch Complex 39B (LC-39B); the second used the first model to evaluate and compare various egress systems under consideration at LC-39B. The third used a modified LC-39B model to determine if a specific hazard decreased survivability more rapidly than other events during flight hardware processing in Kennedy's Vehicle Assembly Building.

Operational Hazards↗

MDP: Reliable File Transfer for Space Missions

This paper presents work being done at NASA/GSFC by the Operating Missions as Nodes on the Internet (OMNI) project to demonstrate the application of the Multicast Dissemination Protocol (MDP) to space missions to reliably transfer files. This work builds on previous work by the OMNI project to apply Internet communication technologies to space communication. The goal of this effort is to provide an inexpensive, reliable, standard, and interoperable mechanism for transferring files in the space communication environment. Limited bandwidth, noise, delay, intermittent connectivity, link asymmetry, and one-way links are all possible issues for space missions. Although these are link-layer issues, they can have a profound effect on the performance of transport and application level protocols. MDP, a UDP-based reliable file transfer protocol, was designed for multicast environments which have to address these same issues, and it has done so successfully. Developed by the Naval Research Lab in the mid 1990's, MDP is now in daily use by both the US Post Office and the DoD. This paper describes the use of MDP to provide automated end-to-end data flow for space missions. It examines the results of a parametric study of MDP in a simulated space link environment and discusses the results in terms of their implications for space missions. Lessons learned are addressed, which suggest minor enhancements to the MDP user interface to add specific features for space mission requirements, such as dynamic control of data rate, and a checkpoint/resume capability. These are features that are provided for in the protocol, but are not implemented in the sample MDP application that was provided. A brief look is also taken at the status of standardization. A version of MDP known as NORM (Neck Oriented Reliable Multicast) is in the process of becoming an IETF standard.

Rash, James↗

MDP: Reliable File Transfer for Space Missions

This paper presents work being done at NASA/GSFC (Goddard Space Flight Center) by the Operating Missions as Nodes on the Internet (OMNI) project to demonstrate the application of the Multicast Dissemination Protocol (MDP) to space missions to reliably transfer files. This work builds on previous work by the OMNI project to apply Internet communication technologies to space communication. The goal of this effort is to provide an inexpensive, reliable, standard, and interoperable mechanism for transferring files in the space communication environment. Limited bandwidth, noise, delay, intermittent connectivity, link asymmetry, and one-way links are all possible issues for space missions. Although these are link-layer issues, they can have a profound effect on the performance of transport and application level protocols. MDP, a UDP (User Datagram Protocol)-based reliable file transfer protocol, was designed for multicast environments which have to address these same issues, and it has done so successfully. Developed by the Naval Research Lab in the mid 1990s, MDP is now in daily use by both the US Post Office and the DoD (Department of Defense). This paper describes the use of MDP to provide automated end-to-end data flow for space missions. It examines the results of a parametric study of MDP in a simulated space link environment and discusses the results in terms of their implications for space missions. Lessons learned are addressed, which suggest minor enhancements to the MDP user interface to add specific features for space mission requirements, such as dynamic control of data rate, and a checkpoint/resume capability. These are features that are provided for in the protocol, but are not implemented in the sample MDP application that was provided. A brief look is also taken at the status of standardization. A version of MDP known as NORM (Nack Oriented Reliable Multicast) is in the process of becoming an IETF (Internet Engineering Task Force) standard.

Rash, James↗

Probabilistic Survivability Versus Time Modeling

This technical paper documents Kennedy Space Centers Independent Assessment team work completed on three assessments for the Ground Systems Development and Operations (GSDO) Program to assist the Chief Safety and Mission Assurance Officer (CSO) and GSDO management during key programmatic reviews. The assessments provided the GSDO Program with an analysis of how egress time affects the likelihood of astronaut and worker survival during an emergency. For each assessment, the team developed probability distributions for hazard scenarios to address statistical uncertainty, resulting in survivability plots over time. The first assessment developed a mathematical model of probabilistic survivability versus time to reach a safe location using an ideal Emergency Egress System at Launch Complex 39B (LC-39B); the second used the first model to evaluate and compare various egress systems under consideration at LC-39B. The third used a modified LC-39B model to determine if a specific hazard decreased survivability more rapidly than other events during flight hardware processing in Kennedys Vehicle Assembly Building (VAB).Based on the composite survivability versus time graphs from the first two assessments, there was a soft knee in the Figure of Merit graphs at eight minutes (ten minutes after egress ordered). Thus, the graphs illustrated to the decision makers that the final emergency egress design selected should have the capability of transporting the flight crew from the top of LC 39B to a safe location in eight minutes or less. Results for the third assessment were dominated by hazards that were classified as instantaneous in nature (e.g. stacking mishaps) and therefore had no effect on survivability vs time to egress the VAB. VAB emergency scenarios that degraded over time (e.g. fire) produced survivability vs time graphs that were line with aerospace industry norms.

Joyner, James J., Sr.↗

Independent verification and validation for Space Shuttle flight software

The Committee for Review of Oversight Mechanisms for Space Shuttle Software was asked by the National Aeronautics and Space Administration's (NASA) Office of Space Flight to determine the need to continue independent verification and validation (IV&V) for Space Shuttle flight software. The Committee found that the current IV&V process is necessary to maintain NASA's stringent safety and quality requirements for man-rated vehicles. Therefore, the Committee does not support NASA's plan to eliminate funding for the IV&V effort in fiscal year 1993. The Committee believes that the Space Shuttle software development process is not adequate without IV&V and that elimination of IV&V as currently practiced will adversely affect the overall quality and safety of the software, both now and in the future. Furthermore, the Committee was told that no organization within NASA has the expertise or the manpower to replace the current IV&V function in a timely fashion, nor will building this expertise elsewhere necessarily reduce cost. Thus, the Committee does not recommend moving IV&V functions to other organizations within NASA unless the current IV&V is maintained for as long as it takes to build comparable expertise in the replacing organization.

Source record↗

Open Innovation for a NASA Architecture Library

NASA’s Center of Excellence for Collaborative Innovation (CoECI) uses open innovation, or “crowdsourcing”, to access the global public to find ideas, concepts, designs, or solutions that meet a previously unmet need possibly resulting in significant advances in performance. The Center of Excellence for Collaborative Innovation was launched at the request of the White House Office of Science and Technology Policy. This is both a non-traditional method of innovation and a non-traditional method of outreach to the public to involve them in space technologies and programs. It has been used often for software development and new hardware technology. In this case we applied it to innovate with systems engineering tools for creating space architectures. The challenge was sponsored by NASA Engineering and Safety Center Systems Engineering Technical Fellow as part of a program for NASA’s adoption of MBSE. It was a trial to see if there would be as much participation or quality submissions with this more specialized topic and skill. The challenge sought space architecture representations and decompositions to create a library of modeled parts in a system modeling language (SysML). Mission architects mostly start from scratch to build model elements representing the functional and physical architecture of a system in SysML. There are a few beginning libraries, but these are also local to a program or group. A common library will save system engineers a large amount of time, will allow project stakeholders to recognize common graphics and quickly understand the architecture options. The challenge was promoted internationally, especially through professional organizations and universities with a systems engineering focus. It was open for 4 months, purposefully over the winter holiday break time to allow participants extra time outside of work or school. The challenge was designed so that expertise in space hardware was not necessary but getting to play with models of space architecture could provide motivation to participate. We did not receive as many entries as other broader outreach challenges, but the ones we received were extremely thorough and high quality. Solutions came from individuals and teams, students and professional consultants from the United States and Europe. We learned a few lessons about how to engage with the public and what characteristics of a problem result in good crowdsourcing results. The outreach challenge produced several useful ideas and modeled space elements, and the group will be engaging the winners to learn more about their new approaches.

innovation↗

Orbital Debris Radar Measurements from the Haystack Ultra-Wideband Satellite Imaging Radar (HUSIR): 2014-2017

For many years, the NASA Orbital Debris Program Office (ODPO) has partnered with the U.S. Department of Defense and the Massachusetts Institute of Technology Lincoln Laboratory (MIT/LL) to collect data on the orbital debris environment using the Haystack radar. These measurements are used to characterize the small debris environment in low Earth orbit (LEO), down to a noise-limited size of approximately 5 mm—depending on altitude. The Haystack radar operated by MIT Lincoln Lab underwent upgrades starting in May 2010, with operations resuming in 2014 as the Haystack Ultra-wideband Satellite Imaging Radar (HUSIR). Hence, the data collected beginning in 2014 represents the first dataset available from this upgraded sensor. HUSIR is the primary source of data used by the ODPO to statistically sample orbital debris in the 5-mm to 10-cm size regime in LEO and is a key source of data to build and validate the NASA Orbital Debris Engineering Model. In this paper, we will present recent results from measurements performed during the US Government fiscal years 2014 – 2017. Using the NASA Size Estimation Model, a method based on laboratory radar measurements of debris, we will compare the size distributions of selected orbital debris populations over this 4-year period and flux measurements of orbital debris greater than 1 cm.

Murray, James↗