Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “building management systems”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

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

At least 919 records · Page 51

Automated Management of Small Unmanned Aircraft System (UAS) Communications and Navigation Contingency

The number of small Unmanned Aircraft System (sUAS) operating in the low-altitude of the National Airspace System (NAS) has been rapidly increasing in the past few years and this number is expected to grow in the future. However, aside from a few special cases, all sUAS must fly within visual line-of-sight (VLOS) of their operators and this limitation is blocking highly anticipated beyond visual line-of-sight (BVLOS) sUAS applications such as package delivery from practice. To enable routine low-altitude BVLOS operations, there needs to be a traffic management ecosystem that complements the FAA’s Air Traffic Management (ATM) system, which does not provide air traffic services under 400 feet above ground level (AGL). NASA has been pioneering research and development of this ecosystem under UAS Traffic Management (UTM) project since 2015 in a series of Technical Capability Levels (TCL) activities that are increasingly complex. In TCL1, completed in 2015, visual line-of-sight operations such as agriculture, firefighting, and infrastructure monitoring were addressed with a focus on geofencing and operations scheduling. Technologies and requirements needed for BVLOS operations in sparsely populated areas were examined in TCL2 in 2016, and those for operations over moderately populated areas in TCL3 in 2017 and 2018. TCL4 is building on the earlier TCLs and focuses on technologies and requirements for operations in higher-density urban areas for tasks such as newsgathering and package delivery and for managing large-scale contingencies. To coordinate and facilitate the incremental implementation of the UTM ecosystem in the NAS, a Research Transition Team (RTT) has been formed between the FAA, NASA, and industry. The RTT is divided into four subgroups, concept and use case development, data exchange and information architecture, sense and avoid, and communications and navigation (C&N). This paper focuses on C&N subgroup activities, in particular about the development of automated sUAS communications and navigation contingency management. The goal of this development is to prepare sUAS to display predictable behavior while handling C&N off-nominal events. It is expected that the adoption of the presented automated contingency management by the sUAS community will accommodate and inform rulemaking towards governing low-altitude BVLOS operations.

Unmanned Aviation Systems (UAS) Traffic Management↗

Making Sense of Rocket Science - Building NASA's Knowledge Management Program

The National Aeronautics and Space Administration (NASA) has launched a range of KM activities-from deploying intelligent "know-bots" across millions of electronic sources to ensuring tacit knowledge is transferred across generations. The strategy and implementation focuses on managing NASA's wealth of explicit knowledge, enabling remote collaboration for international teams, and enhancing capture of the key knowledge of the workforce. An in-depth view of the work being done at the Jet Propulsion Laboratory (JPL) shows the integration of academic studies and practical applications to architect, develop, and deploy KM systems in the areas of document management, electronic archives, information lifecycles, authoring environments, enterprise information portals, search engines, experts directories, collaborative tools, and in-process decision capture. These systems, together, comprise JPL's architecture to capture, organize, store, and distribute key learnings for the U.S. exploration of space.

knowledge management organizational learning NASA ↗

An intelligent energy router for managing behind-the-meter resources and assets

With increase in distributed energy resources (DERs) and smart loads, each energy resource and load need a separate power conversion system leading to complex coordination and interaction, reduced energy conversion efficiency, coordinating compliance to grid standards (IEEE 1547) from multiple sources, reduced security. Also, multiple vendors with legacy system designs and proprietary communications interfaces result in redundancy and increase in cost of power electronics systems. This paper presents an energy router concept for buildings applications which provides autonomous power flow between sources and loads with a novel agent-based software interface.

Chinthavali, Madhu Sudhan↗

Human Exploration System Test-Bed for Integration and Advancement (HESTIA) Support of Future NASA Deep-Space Missions

The Engineering Directorate at the NASA - Johnson Space Center is outfitting a 20-Foot diameter hypobaric chamber in Building 7 to support future deep-space Environmental Control & Life Support System (ECLSS) research as part of the Human Exploration System Test-bed for Integration and Advancement (HESTIA) Project. This human-rated chamber is the only NASA facility that has the unique experience, chamber geometry, infrastructure, and support systems capable of conducting this research. The chamber was used to support Gemini, Apollo, and SkyLab Missions. More recently, it was used to conduct 30-, 60-, and 90-day human ECLSS closed-loop testing in the 1990s to support the International Space Station and life support technology development. NASA studies show that both planetary surface and deep-space transit crew habitats will be 3-4 story cylindrical structures driven by human occupancy volumetric needs and launch vehicle constraints. The HESTIA facility offers a 3-story, 20-foot diameter habitat consistent with the studies' recommendations. HESTIA operations follow stringent processes by a certified test team that including human testing. Project management, analysis, design, acquisition, fabrication, assembly and certification of facility build-ups are available to support this research. HESTIA offers close proximity to key stakeholders including astronauts, Human Research Program (who direct space human research for the agency), Mission Operations, Safety & Mission Assurance, and Engineering Directorate. The HESTIA chamber can operate at reduced pressure and elevated oxygen environments including those proposed for deep-space exploration. Data acquisition, power, fluids and other facility resources are available to support a wide range of research. Recently completed HESTIA research consisted of unmanned testing of ECLSS technologies. Eventually, the HESTIA research will include humans for extended durations at reduced pressure and elevated oxygen to demonstrate very high reliability of critical ECLSS and other technologies.

Marmolejo, Jose↗

District-Scale Analysis of Electricity Load and Strategies to Improve Energy Reliability Using Prototype District Models

Projected increases in electricity demand in the U.S. highlight the urgent need for effective load management to ensure grid reliability. As the building sector accounts for approximately 75% of electricity usage, enhancing energy efficiency and flexibility in this sector is crucial. Adopting district-level approaches offers significant advantages over traditional individual building analyses by enabling shared infrastructure and economies of scale. To navigate the data and computational challenges associated with modeling energy at the district level, prototype district models have been proposed as holistic, system-level solutions that capture complex interactions within typical configurations. This study presents these models as a reference tool for analyzing district-scale energy systems across various climate zones in the U.S. Developed with input from stakeholders, these models integrate varied building characteristics, inter-building connections, and energy system interactions. A case study utilizing the Urban Edge prototype district model, implemented on the URBANopt™ platform, evaluates multiple demand scenarios and the impact of distributed energy resources such as fuel-fired backup generators, photovoltaic systems, and batteries. Findings suggest that while new electric systems can significantly reduce annual energy use, they may also elevate peak electricity loads, with a notable 43% increase in heating-dominant climate zone 5B. The optimal backup power solutions vary based on location, influenced by factors such as utility rates and incentives. For example, PV and batteries perform well in high-cost regions like New York City, while diesel backup generators are more suitable for backup needs in climate zone 3A, such as Atlanta. Thus, this research highlights the importance of prototype district models for future district-scale energy planning.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Integrated Surface Power Strategy for Mars

A National Aeronautics and Space Administration (NASA) study team evaluated surface power needs for a conceptual crewed 500-day Mars mission. This study had four goals: 1. Determine estimated surface power needed to support the reference mission; 2. Explore alternatives to minimize landed power system mass; 3. Explore alternatives to minimize Mars Lander power self-sufficiency burden; and 4. Explore alternatives to minimize power system handling and surface transportation mass. The study team concluded that Mars Ascent Vehicle (MAV) oxygen propellant production drives the overall surface power needed for the reference mission. Switching to multiple, small Kilopower fission systems can potentially save four to eight metric tons of landed mass, as compared to a single, large Fission Surface Power (FSP) concept. Breaking the power system up into modular packages creates new operational opportunities, with benefits ranging from reduced lander self-sufficiency for power, to extending the exploration distance from a single landing site. Although a large FSP trades well for operational complexity, a modular approach potentially allows Program Managers more flexibility to absorb late mission changes with less schedule or mass risk, better supports small precursor missions, and allows a program to slowly build up mission capability over time. A number of Kilopower disadvantages-and mitigation strategies-were also explored.

Rucker, Michelle↗

Radiological Recovery Logistics Tool - 20161

Argonne is building and testing a tool, the Radiological Recovery Logistics Tool (RRLT), that can be used during the response and recovery from a radiological or nuclear incident to effectively allocate appropriate commercial and public works equipment to mitigate, remove, and contain radiological contamination. The requirements for this tool - as well as development of the resulting software - is overseen by a steering committee of stakeholders from DHS's National Urban Security Technology Laboratory (NUSTL), the Federal Emergency Management Agency (FEMA), and the Environmental Protection Agency (EPA). One essential requirement is for RRLT to support the efficient and appropriate allocation of resources for a radiological response. Subsequent discussions between ANL and stakeholders have solidified the nature of this support to include identification of the types of resources to be allocated. The study reported in this paper has both factored fundamental concepts and connections out of this identification process and created a Knowledge Base detailing support goals, response scenarios, and efficacy information on dozens of equipment types. In short, RRLT will dynamically apply these findings to situational conditions surrounding contamination incidents. RRLT's Domain, the model of elements, ideas and relationships with which the tool will work, draws concepts from technical reports and stakeholder vocabularies to connect response goals and scenarios to types of equipment that offer utility towards those goals in those scenarios. RRLT's Knowledge Base will contain details on dozens of equipment types and facilitate the operator's discovery and consumption of these details most pertinent to a dynamically selected subset of goals. The core of its Domain Model is based on a report authored by this team. This report [1] contains a comprehensive list of proposed equipment to accomplish various missions or scenarios that might arise after a large-scale radiological contamination incident in an urban environment or critical infrastructure. The report divides potential response and recovery efforts into five support goals: Survey and monitoring of the contaminated area; Mitigation of received dose to first responders: Decontamination (gross and final) of buildings, vehicles, roadways, parks, and other surfaces: Waste management of solid waste generated during recovery operations: and Containment of wastewater and other waste generated during the response and recovery phases. RRLT's development is driven by use cases. A use case is an intention with which a user approaches the software. Use cases are grouped into delivery increments to schedule development, testing, and presentation to stakeholders. This model partitions the system into seven increments: User Arrival and Authentication, Search and Navigation, Equipment Recommendation, Plan Management, Content Management, and Expanded Access. Once a user 15 authenticated, RRLT will present the user with a dashboard that allows them to explore or search RRLT's content. The dashboard will also include a 'Plan' panel for collecting decisions and relevant observations about an incident at hand to facilitate development of an equipment list. RRLT will offer three general modes of access to items in the knowledge base: - Keyword search for direct discovery of items, - Navigation along predetermined paths from recovery goal towards equipment types, and - Interactive guidance towards equipment types by an autonomous software agent: the Equipment Recommendation Wizard. This presentation will detail progress in the development of the RRLT and also discuss opportunities for those interested in providing feedback on its content and functionality. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Software to model AXAF image quality

This draft final report describes the work performed under this delivery order from May 1992 through June 1993. The purpose of this contract was to enhance and develop an integrated optical performance modeling software for complex x-ray optical systems such as AXAF. The GRAZTRACE program developed by the MSFC Optical Systems Branch for modeling VETA-I was used as the starting baseline program. The original program was a large single file program and, therefore, could not be modified very efficiently. The original source code has been reorganized, and a 'Make Utility' has been written to update the original program. The new version of the source code consists of 36 small source files to make it easier for the code developer to manage and modify the program. A user library has also been built and a 'Makelib' utility has been furnished to update the library. With the user library, the users can easily access the GRAZTRACE source files and build a custom library. A user manual for the new version of GRAZTRACE has been compiled. The plotting capability for the 3-D point spread functions and contour plots has been provided in the GRAZTRACE using the graphics package DISPLAY. The Graphics emulator over the network has been set up for programming the graphics routine. The point spread function and the contour plot routines have also been modified to display the plot centroid, and to allow the user to specify the plot range, and the viewing angle options. A Command Mode version of GRAZTRACE has also been developed. More than 60 commands have been implemented in a Code-V like format. The functions covered in this version include data manipulation, performance evaluation, and inquiry and setting of internal parameters. The user manual for these commands has been formatted as in Code-V, showing the command syntax, synopsis, and options. An interactive on-line help system for the command mode has also been accomplished to allow the user to find valid commands, command syntax, and command function. A translation program has been written to convert FEA output from structural analysis to GRAZTRACE surface deformation file (.dfm file). The program can accept standard output files and list files from COSMOS/M and NASTRAN finite analysis programs. Some interactive options are also provided, such as Cartesian or cylindrical coordinate transformation, coordinate shift and scale, and axial length change. A computerized database for technical documents relating to the AXAF project has been established. Over 5000 technical documents have been entered into the master database. A user can now rapidly retrieve the desired documents relating to the AXAF project. The summary of the work performed under this contract is shown.

Ahmad, Anees↗

What is the Right Size for a Residential Building Parcel Locker?

Common-carrier parcel lockers present a solution for decreasing delivery times, traffic congestion, and emissions in dense urban areas through consolidation of deliveries. Multi-story residential buildings with large number of residents, and thus a high volume of online package orders, are one of the best venues for installing parcel lockers. But what is the right size for a residential building locker that would suit the residents’ and building managers’ needs? Because of the novelty of parcel lockers, there is no clear guideline for determining the right locker size and configuration for a residential building given the resident population. A small locker would result in packages exceeding capacity and being left in the lobby, increasing the building manager’s workload and confusing and inconveniencing users. On the other hand, a large locker is more expensive, more difficult to install, and unappealing to residents. To answer this question, we installed a common-carrier parcel locker in a residential building in downtown Seattle, WA, U.S.A. Through collecting detailed data on locker usage from the locker provider company, we studied and quantified carriers’ delivery patterns and residents’ online shopping and package pickup behaviors. We then used this information to model the locker delivery and pickup process, and simulated several locker configurations to find the one that best suits the delivery needs of the building. These findings could aid urban planners and building managers in choosing the right size for residential building lockers that meet delivery demand while minimizing costs and contributing to environmental benefits.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Final Report: MaRSPlus Sensor System Electrical Cable Management and Distributed Motor Control Computer Interface

The success of JPL's Next Generation Imaging Spectrometer (NGIS) in Earth remote sensing has inspired a follow-on instrument project, the MaRSPlus Sensor System (MSS). One of JPL's responsibilities in the MSS project involves updating the documentation from the previous JPL airborne imagers to provide all the information necessary for an outside customer to operate the instrument independently. As part of this documentation update, I created detailed electrical cabling diagrams to provide JPL technicians with clear and concise build instructions and a database to track the status of cables from order to build to delivery. Simultaneously, a distributed motor control system is being developed for potential use on the proposed 2018 Mars rover mission. This system would significantly reduce the mass necessary for rover motor control, making more mass space available to other important spacecraft systems. The current stage of the project consists of a desktop computer talking to a single "cold box" unit containing the electronics to drive a motor. In order to test the electronics, I developed a graphical user interface (GUI) using MATLAB to allow a user to send simple commands to the cold box and display the responses received in a user-friendly format.

data cubes↗

An Approach for Defining IASMS Services, Functions, and Capabilities

Assuring safety in the NAS with the inclusion of new entrants, such as Advanced Air Mobility (AAM), will require overcoming unique safety challenges that result from combining innovative technologies with novel airspace concepts for moving people and cargo using autonomous vehicles. The focus of the In-time Aviation Safety Management System (IASMS) is to overcome AAM’s safety assurance challenges. The IASMS Concept of Operations (ConOps) describes an interconnected set of services, functions, and capabilities (SFCs) designed to manage operational risks, identify unknown risks, and inform system designs. This paper describes an approach for defining SFCs based on technology trends in research, assessment of known and unknown risks in voluntary safety reports, and causal and contributing factors in aviation accidents and incidents. This approach would identify potential SFCs that further expand the Monitor, Assess, and Mitigate (M-A-M) functionality that represents the enabling framework of the IASMS. Safety implications that will result from integration of AAM in the transformation of the National Airspace System (NAS) were addressed in National Academies committees reports on AAM and IASMS. Development of a ConOps for IASMS was a top recommendation and can be represented as a reframing of safety assurance that builds on real-time alerting such as the Traffic Alert and Collision Avoidance System, and adds the more encompassing in-time temporal parameter in recognition of the different timelines for collecting and assessing safety data for risk mitigations. For example, mining for safety trends from data sources such as the Aviation Safety Information Analysis and Sharing system occurs over a longer time period. Research on AAM operations poses that SFCs can be designed to monitor the safety margin appropriate for AAM including with regards to the distance between current flight parameters and nominal ideal conditions. These in-time comparisons will become more complex as the density of operations increases at least in certain areas and can include planned and actual 4D trajectory, and in-time comparisons having implications on conflict modeling and prediction including expected and actual departure time, fix/waypoint crossing times, and arrival time. These comparisons would be integrated as part of SFCs that redefine and inform new safety margin. An increased safety margin improves management of operational risks while reducing the potential for anomalies. An increased safety margin also has implications for operator confidence in the certainty of its operations and trust in automation. Technology trends in research could be used to refine existing SFCs and define needs for additional SFCs that provide safety improvements to the design and operation of vehicles, airspace design, and operator performance requirements. NASA is developing innovative approaches to safeguard against major accidents and incidents that have occurred in the NAS and those anticipated with the inclusion of envisioned AAM operations. The innovations use operational performance data to monitor, detect, and predict flight variations exceeding safe nominal patterns, such as would be caused by navigational error, severe weather complications, or hijacking of UAS controls. These innovative approaches have high potential to prevent accidents and incidents in the new AAM era. It is anticipated that elements of the innovations will evolve into SFCs for the IASMS. Voluntary safety reports can be monitored to identify anomalies related to design or operational performance risks. Reports could be periodically monitored and assessed for specific topics. Reports might serve as weak signals or precursors indicative of emergent risk such as when combined with other safety information. The architecture could include SFCs that are based on voluntary safety reports recognizing the periodic temporal nature of data analysis. As previously mentioned, aviation accidents with their causal and contributing precursors can inform the need for SFCs in the IASMS. Accidents and incidents at San Francisco International Airport such as Asiana 214 and Air Canada 759 illustrate how combinations of different factors lead to increased risk. These types of precursors and different factors have implications on the types of SFCs that could be needed to monitor and manage different sources and types of design and operational risk. Continuing to assure the safety of AAM as designs and operations gain in complexity can be accompanied by defining SFCs that also increase in complexity. These SFCs can leverage information from findings and recommendations synthesized across on-going research, voluntary safety reports, and accident and incident reports. These SFCs can serve to refine accuracy of algorithms and resolve limitations with current practices. The IASMS architecture represents the framework for the SFCs and their critical role in safety assurance.

In-Time Aviation Safety Management System↗

NASA's Space Launch System: Moving Toward the Launch Pad

The National Aeronautics and Space Administration's (NASA's) Space Launch System (SLS) Program, managed at the Marshall Space Flight Center, is making progress toward delivering a new capability for human space flight and scientific missions beyond Earth orbit. Developed with the goals of safety, affordability, and sustainability in mind, the SLS rocket will launch the Orion Multi-Purpose Crew Vehicle (MPCV), equipment, supplies, and major science missions for exploration and discovery. Supporting Orion's first autonomous flight to lunar orbit and back in 2017 and its first crewed flight in 2021, the SLS will evolve into the most powerful launch vehicle ever flown, via an upgrade approach that will provide building blocks for future space exploration and development. NASA is working to develop this new capability in an austere economic climate, a fact which has inspired the SLS team to find innovative solutions to the challenges of designing, developing, fielding, and operating the largest rocket in history. This paper will summarize the planned capabilities of the vehicle, the progress the SLS program has made in the 2 years since the Agency formally announced its architecture in September 2011, and the path the program is following to reach the launch pad in 2017 and then to evolve the 70 metric ton (t) initial lift capability to 130-t lift capability. The paper will explain how, to meet the challenge of a flat funding curve, an architecture was chosen which combines the use and enhancement of legacy systems and technology with strategic new development projects that will evolve the capabilities of the launch vehicle. This approach reduces the time and cost of delivering the initial 70 t Block 1 vehicle, and reduces the number of parallel development investments required to deliver the evolved version of the vehicle. The paper will outline the milestones the program has already reached, from developmental milestones such as the manufacture of the first flight hardware and the record-breaking testing of the J-2X engine, to life-cycle milestones such as the vehicle's Preliminary Design Review. The paper will also discuss the remaining challenges in both delivering the 70 t vehicle and in evolving its capabilities to the 130 t vehicle, and how the program plans to accomplish these goals. As this paper will explain, SLS is making measurable progress toward becoming a global infrastructure asset for robotic and human scouts of all nations by harnessing business and technological innovations to deliver sustainable solutions for space exploration

Creech, Stephen D.↗

Ibis Networks/WattIQ (IN2 Final Report)

Ibis Networks is a full-stack cleantech company that provides plug-level energy monitoring and control to solve energy and asset management problems for the enterprise. During DATES – DATES, an NREL research team worked with the Ibis team to validate their product, the InteliSocket. The Ibis InteliSocket is a pass-through plug-load energy monitor and controller that is designed to reduce energy wasted by common 120 V plug-in devices in commercial office buildings, such as computer peripherals, conference room AV equipment, and break-room appliances. The system can shut off supply power to these end uses via remote control, manual switches, pre-set schedules, or automated control algorithms. The scope of this IN2 project was the development and refinement of “smart” learning behavior algorithms (LBAs), which could help installation processes and dramatically expand the sockets’ capabilities and energy-saving potential by suggesting suitable control schedules that are based on monitored use patterns. While Ibis has the analytical and software expertise for algorithm development, the lack of test data, both in a controlled laboratory setting and in real-life deployment scenarios, represented a key barrier toward commercialization of the product. Assistance through the IN2 program provided an opportunity to conduct the needed “trial and error” algorithm development. The project included baseline field-data collection, laboratory testing, and field validation components, all of which were conducted at the NREL campus between April 2017 and July 2019.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Changes and challenges in the Software Engineering Laboratory

Since 1976, the Software Engineering Laboratory (SEL) has been dedicated to understanding and improving the way in which one NASA organization, the Flight Dynamics Division (FDD), develops, maintains, and manages complex flight dynamics systems. The SEL is composed of three member organizations: NASA/GSFC, the University of Maryland, and Computer Sciences Corporation. During the past 18 years, the SEL's overall goal has remained the same: to improve the FDD's software products and processes in a measured manner. This requires that each development and maintenance effort be viewed, in part, as a SEL experiment which examines a specific technology or builds a model of interest for use on subsequent efforts. The SEL has undertaken many technology studies while developing operational support systems for numerous NASA spacecraft missions.

Pajerski, Rose↗

Montana Water Resources II: Enhancing a Moisture Index for Drought and Flood Monitoring in the Missouri River Basin

The Missouri River Basin is a major global breadbasket, containing large amounts of agricultural land. Recent devastating weather events have motivated regional organizations to dedicate efforts to drought and flood monitoring and early warning systems. The DEVELOP team partnered with the following organizations: Montana Climate Office, NOAA National Weather Service (NWS) Missouri Basin River Forecast Center, NOAA Regional Climate Services of the Central Region, NOAA Physical Sciences Laboratory, and the US Army Corps of Engineers' Missouri River Basin Water Management Division. The team collaborated with the partners in their efforts to monitor flood and drought by enhancing a composite moisture index (CMI) for the Missouri River Basin. The CMI leverages NASA Earth observations to derive snow cover data from the Terra Moderate Resolution Imaging Spectroradiometer (MODIS) mission and snow water equivalent and snowdepth datasets from the NOAA NWS National Operational Hydrologic Remote Sensing Center’s Snow Data Assimilation System (SNODAS). Building upon this framework, the team added groundwater storage data from the Gravity Recovery and Climate Experiment (GRACE) and GRACE Follow-On missions, soil moisture data from Soil Moisture Active Passive (SMAP), and United States Geological Survey in situ streamflow data to the CMI. To test the tool’s validity, the team compared the CMI results to historically extreme dry and extreme wet years, March 2017 and March 2019, respectively. The CMI accurately reflects both 2017 and 2019 climate conditions in the Missouri River Basin. The refined CMI enhances the understanding of antecedent soil moisture conditions and improves flood and drought forecasting in the Missouri River Basin before the growing season.

Chloe Schneider↗

Engineering in Cyber Resilience with Cyber-Informed Engineering

Engineers have super powers to provide cybersecurity resilience with deterministic engineering solutions and to protect systems from the most catastrophic consequences that a cyber saboteur could cause. Come to this session to learn how to use engineering risk management skills to harden your engineered systems from cyberattacks. Objective 1 Identify what system functions could be digitally induced to cause undesired high-impact consequences. Objective 2 Analyze how loss or instability of digital controls in a subsystem could lead to high-impact consequences. Objective 3 Analyze how loss or instability in the digital connectivity between systems could lead to high-impact consequences. Objective 4 Identify engineering controls which could build resilience by eliminating digital loss or instability pathways or reduce the impact of digital loss or instability. This presentation will introduce Cyber-Informed Engineering, described below, and walk participants through specific engineering use cases to show how engineers can consider the potential for cyber sabotage in their existing system designs and enact deterministic engineering-based controls which eliminate pathways for attack or mitigate specific consequences. A wide variety of application use cases will be considered so that audience members can align the material with familiar engineering applications. CIE is an engineering approach that integrates cyber resilience into the conception, design, build, and operation of any physical system that has digital connectivity, sensors, monitoring, or control. CIE offers the opportunity to use engineering to eliminate or mitigate avenues for cyber attack—starting from the earliest stage of design and continuing throughout the system’s lifecycle. Today, engineers and industrial control system (ICS) technicians build engineered systems with specific goals for safety, reliability, and functionality. While systems engineering includes considerable safety and failure mode analysis, cybersecurity risks are often not specifically addressed—particularly the risks of intentional cyber compromise, exploitation, and misuse. Cyber-Informed Engineering pairs well with traditional cyber defenses and offers an extra designed-in protection to eliminate the most catastrophic consequences which can be realized by an adversary should traditional cyber defenses fail.

42 ENGINEERING↗

NASA's Space Launch System: Moving Toward the Launch Pad

The National Aeronautics and Space Administration's (NASA's) Space Launch System (SLS) Program, managed at the Marshall Space Flight Center (MSFC), is making progress toward delivering a new capability for human space flight and scientific missions beyond Earth orbit. Designed with the goals of safety, affordability, and sustainability in mind, the SLS rocket will launch the Orion Multi-Purpose Crew Vehicle (MPCV), equipment, supplies, and major science missions for exploration and discovery. Supporting Orion's first autonomous flight to lunar orbit and back in 2017 and its first crewed flight in 2021, the SLS will evolve into the most powerful launch vehicle ever flown via an upgrade approach that will provide building blocks for future space exploration. NASA is working to deliver this new capability in an austere economic climate, a fact that has inspired the SLS team to find innovative solutions to the challenges of designing, developing, fielding, and operating the largest rocket in history. This paper will summarize the planned capabilities of the vehicle, the progress the SLS Program has made in the 2 years since the Agency formally announced its architecture in September 2011, the path it is following to reach the launch pad in 2017 and then to evolve the 70 metric ton (t) initial lift capability to 130-t lift capability after 2021. The paper will explain how, to meet the challenge of a flat funding curve, an architecture was chosen that combines the use and enhancement of legacy systems and technology with strategic new developments that will evolve the launch vehicle's capabilities. This approach reduces the time and cost of delivering the initial 70 t Block 1 vehicle, and reduces the number of parallel development investments required to deliver the evolved 130 t Block 2 vehicle. The paper will outline the milestones the program has already reached, from developmental milestones such as the manufacture of the first flight hardware, to life-cycle milestones such as the vehicle's Preliminary Design Review (PDR). The paper will also discuss the remaining challenges both in delivering the 70-t vehicle and in evolving its capabilities to the 130-t vehicle, and how NASA plans to accomplish these goals. As this paper will explain, SLS is making measurable progress toward becoming a global infrastructure asset for robotic and human scouts of all nations by harnessing business and technological innovations to deliver sustainable solutions for space exploration.

Creech, Stephen D.↗

Defining Tolerance: Impacts of Delay and Disruption when Managing Challenged Networks

Challenged networks exhibit irregularities in their communication performance stemming from node mobility, power constraints, and impacts from the operating environment. These irregularities manifest as high signal propagation delay and frequent link disruption. Understanding those limits of link disruption and propagation delay beyond which core networking features fail is an ongoing area of research. Various wireless networking communities propose tools and techniques that address these phenomena. Emerging standardization activities within the Internet Research Task Force (IRTF) and the Consultative Committee for Space Data Systems (CCSDS) look to build upon both this experience and scalability analysis. Successful research in this area is predicated upon identifying enablers for common communication functions (notably node discovery, duplex communication, state caching, and link negotiation) and how increased disruptions and delays affect their feasibility within the network. Networks that make fewer assumptions relating to these enablers provide more universal service. Specifically, reliance on node discovery and link negotiation results in network-specific operational concepts rather than scalable technical solutions. Fundamental to this debate are the definitions, assumptions, operational concepts, and anticipated scaling of these networks. This paper presents the commonalities and differences between delay and disruption tolerance, including support protocols and critical enablers. We present where and how these tolerances differ. We propose a set of use cases that must be accommodated by any standardized delay-tolerant network and discuss the implication of these on existing tool development.

mobility drivers↗