Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “team”

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 1,441 records · Page 80

Northwest Combined Heat and Power Technical Assistance Partnership: Final Scientific/Technical Report

During the years of 2018 through 2023, The Washington State University Energy Program (WSU EP) operated the Northwest Combined Heat and Power Technical Assistance Partnership under contract to the US Department of Energy’s Advanced Manufacturing Office (AMO), a part of DOE’s larger Office of Energy Efficiency and Renewable Energy. This contract provided direction and funding for providing technical outreach, information and technical/economic analysis services in support of expanding development of Combined Heat and Power (CHP) over a four state region in the Pacific Northwest. The states served included Alaska, Idaho, Oregon and Washington. During the duration of this contract, the WSU EP delivered performed specific assigned tasks and provided services of various generally prescribed types, with the overall goal of increasing adoption of CHP as an efficient heat and power supply in the region. Indications – though not formally evaluated to our knowledge – are that this goal was achieved. Over many years, the WSU team has provided support for CHP developments in these states under similar previous Department of Energy contracts, and many such projects have been built. While the early-phase outreach, education and techno-economic assessments that the NW CHP TAP provides rarely immediately result in project construction, there is no doubt that the WSU EP team has had substantial influence in the construction of a number of important CHP projects in the region. Examples of projects implemented directly under the current team’s guidance and services during this contract cycle include an 875 kilowatt biomass fueled CHP system installed at the University of Idaho, and 5 megawatt natural gas fueled CHP system at the University of Montana ( UM Breaks Ground on New Power Facility, Slashes Emissions 30% (umt.edu) ). Many other CHP systems recently installed are also either directly or at least partially the result of information and technical services provided by the team. Finally, though much more difficult to quantify and less glamorous, the team has helped countless organizations to understand CHP and determine whether and how CHP may be a fit for them, before they consider paying for engineering services. Whether the ultimate outcome has been to include CHP or not, the expert skills provided by the NW CHP TAP team have provided real value to these organizations considering this relatively complex technology. Over the duration of the contract our team provided 71 Initial Technical Assessments and 17 Advanced Technical Assessments; 53 End-User Engagements and 33 Stakeholder Engagements of various types; 42 Technical Profiles (Project Profiles, Program Profiles and Policy Profiles), and produced 14 technical articles for the Department of Energy. Unfortunately, these quantities provide no measure of the value that the team has provided. Only our clients can judge that, and we are confident that they are pleased with the benefits we have offered them.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

DECOVALEX-2023: Task E Final Report

This is the Task E final report for DECOVALEX-2023. Task E is focused on understanding thermal, two-phase hydrological, and mechanical (TH2M) processes, especially related to predicting brine migration in the excavation damaged zone around a heated excavation in salt. Salt is attractive as a disposal medium for radioactive waste because it is self-healing and is essentially impermeable and essentially non-porous in the far field (away from excavations). Investigation of the short-term (days to years) near-field (centimeters to tens of meters) behavior of salt is important for radioactive waste disposal because this early period strongly controls the amount of brine in a salt repository. Brine leads to corrosion of waste forms and waste packages, and possible dissolution of radionuclides with brine transport being a potential transport vector to the accessible environment. The main test case used in Task E is the ongoing Brine Availability Test in Salt (BATS) heater test located underground at the Waste Isolation Pilot Plant (WIPP) near Carlsbad, New Mexico, USA. The Task was divided into a series of Steps. Step 0 was an introduction to processes in salt, that included matching historical unheated brine inflow data from boreholes at WIPP and matching temperature observations during BATS heater test 1a. Step 1 included validation of models against a thermo-poroelastic analytical solution relevant to heated boreholes in salt, and two-phase flow around an excavation in salt. Step 2 required all the individual components covered in steps 0 and 1 to come together to match observed brine inflow behavior during the BATS 1a heater test. There were a range of approaches from the teams, from mechanistic to prescriptive. Given the uncertainties in the problem, some teams used one- or two-dimensional models of the processes, while other teams included more geometrical complexity in three-dimensional models. The key learning points from Task E have been: • Heat conduction through salt typically requires non-linear thermal conductivity (as a function of temperature), but most models do a good job matching observations, given appropriate adjustments to the applied power and some thermocouple locations. • Thermal pressurization requires coupled thermal-hydrological-mechanical (THM) responses that consider the thermal expansion of the fluid and solid phases. • Initialization of two-phase flow models around a borehole or excavation in salt are more realistically represented as “wetting up”, rather than “drying down” (i.e., the initial state after excavation is mostly dry, rather than mostly wet). • The BATS 1a heater test includes a significant release of brine after the end of heating, which requires a large increase in permeability to recreate. Task E has been a great learning experience for all the teams involved, and feedback from the modeling teams has led to changes in the design of follow-on BATS experiments, which are now ongoing underground at WIPP. There was a balance throughout the task between freedom to model phenomena how each team saw fit, and prescriptiveness in problem design to bring the modeling teams closer together to allow attribution of smaller differences between models to different modeling choices. The modeling approaches seem to go through two phases: an early phase of discovery or testing, and a later phase of refinement and improvement. In future modeling efforts, different field data could be used (e.g., BATS 2) and more time should be included in the processes for teams to make multiple model refinement or even significant changes to their conceptual model or setup, based on lessons learned from the modeling exercise.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

DECOVALEX-2023: Task F1 Final Report

DECOVALEX-2023 Task F is a comparison of models and methods for post-closure performance assessment (PA) of a deep geologic repository for radioactive waste. The general aims of Task F are to build confidence in the models, methods, and software used for PA and to stimulate additional research and development in PA methodologies. The task objectives are to motivate development of PA modelling skills and capabilities, to examine the influence of model choices on calculated repository performance, and to compare the uncertainties introduced by model choices to other sources of uncertainty. Task F involves no actual experiment or site. It is a PA modelling exercise that requires the conceptual development of hypothetical repository designs and geologic settings. Because three of the teams were interested in salt and the rest of the teams were interested in crystalline rock, Task F was split into two branches: Task F1 for crystalline rock and Task F2 for salt. This report is for Task F1, crystalline rock. Teams from seven countries (Canada, Czech Republic, Germany, Korea, Sweden, Taiwan, and United States) participated in Task F1. The teams worked together to define the features, events, and processes of the reference case repository and established a set of performance measures. In addition, they defined a set of benchmark problems designed to test and compare modelling capabilities for fracture flow and transport at different scales. The repository design and benchmark problems are documented in a Task Specification that evolved over time as the group honed the specifications. The benchmark problems verified that each team can aptly model flow and transport in fractured media in 1-, 2-, and 3-dimensions. Two general approaches were used for the 3-dimensional benchmarks: discrete fracture network (DFN) and equivalent continuous porous medium (ECPM). DFN modelling involves explicit meshing of each fracture while ECPM modelling aims to capture the effective porosity and directional permeability of each cell in a space-filling mesh as affected by intersecting fractures. In some models, a combination of the two is used, i.e., DFN for large known fractures and ECPM for the rest of the domain. Transport is solved by using either the advection-dispersion equation or particle tracking. Although some variation is observed among model breakthrough curves in the benchmark problems, there is strong agreement in breakthrough behaviour up to at least the 75 th percentile for all benchmarks. At the 90 th percentile, breakthrough results show larger differences, suggesting several models retain substantially higher fractions of tracer in regions of slower moving water. In addition to the flow and transport benchmarks, several teams completed the source term benchmark, verifying capabilities for modelling radionuclide decay and ingrowth, waste package breach, instant release fractions, fuel matrix degradation rates, and radionuclide solubility limitations. The reference case is conceptualized as a generic spent fuel repository at a depth of 450 m in fractured crystalline rock. The repository has 50 parallel backfilled drifts, each with 50 deposition holes 6 m apart. Each deposition hole contains a 4-PWR waste package and bentonite buffer. The rock domain is 5 km in length, 2 km in width, and 1 km in depth. It has 6 deterministic fractured deformation zones and a multitude of stochastic fractures. Teams generally used the ECPM approach for the entire rock or a hybrid approach in which the deterministic fracture zones are modelled with a DFN and the rest of the rock is modelled by ECPM. Of the reference case problems specified, only the results of the initial reference case problem are compared in this report. The initial problem focuses on transport from the deposition holes to the surface, i.e., it neglects waste package performance. Tracers are released at all waste package locations at time zero and tracked for their releases to the near field and ground surface. The water fluxes calculated at the ground surface entry and exit regions of the domain are similar for all models except for two that have considerably lower fluxes. For tracer transport, large differences are observed among models in the magnitude of tracer transported. Much of the difference appears to be due to how the repository is implemented and hence the different degrees of repository simplification. Models that exclude the drifts, buffer, and backfill from the domain tend to show greater release of tracers and radionuclides from the repository. The initial study presented here indicates that major differences in modelling important processes within the repository (e.g., diffusion through buffer and backfill) can produce broadly different release and transport results, especially when those processes are excluded. Even for the models that included all specified features, events, and processes, the results show significant differences and demonstrate the importance of examining multiple modelling approaches in performance assessment. The differences in results observed in this study are expected to motivate teams to either increase complexity in future versions of the reference case models or to improve methods to account for the effects of simplified features and processes. Either way, future improvements in these models are expected to produce results that more closely agree.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Wholly Sustainable, Cost-Effective Carbon Fiber-Nylon Compounds CRADA 592 (Final Report)

Carbon fiber composites have attracted considerable attention due to the potential for substantial mass savings, with many examples now implemented in the low-volume luxury car market. However, migration to higher volume applications has been hindered by: (a) high material cost, (b) high processing times, and (c) perception of low Sustainability. This project will address all three of these barriers: (a) carbon fiber material to replace aluminum in structural components at a cost penalty of no more than $5/Kg-saved (aka weight buy), (b) fitting into high-rate processes for automotive production like injection molding, and (c) end-to-end Sustainable material – based on post industrial waste carbon fiber and nylon 66 and ability to recycle end-of-life auto parts. The opportunity lies in combining DowAksa capabilities in carbon fiber manufacturing, resin chemistry intermediate production with the unique testing capabilities inherent within PNNL. The teams from PNNL and DowAksa held several meetings virtually and in-person in Michigan and at PNNL, including a lab tour at PNNL. Throughout, the teams discussed DowAksa material sources, commercially available recycled base materials, and preliminary material properties. The teams also engaged in multiple discussions and evaluations of potential automotive applications based on the ideas suggested by PNNL. The teams discussed several potential automotive applications in which recycled carbon fiber and recycled PA resin can be used. The PNNL team identified 38 cast aluminum components that can potentially be assessed for redesign using the DowAksa materials system. The PNNL team also identified 27 polyamide components. The teams discussed the lists and narrowed it down to a handful of applications that are exterior and interior to common vehicle architectures. The team also considered semi-structural and structural components and short-listed the highest potential candidates, such as cross-car-beam. The cross-car beam was considered to be highly suitable and potentially viable demonstration applications based on the properties of the materials as well as the weight savings potentials and the reduction in embodied energy by utilizing wholly sustainable materials, since both materials, carbon fiber and resin, were derived from recycled materials. The next step was to reach out to potential OEMs and/or Tier1s who were interested in exploring such technology for future applications. However, the project was terminated, and no further discussions or exchange of information took place. No new data were generated, including no IP and no publications.

36 MATERIALS SCIENCE↗

Pawnee Nation Energy Option Analyses

In 2003, the Pawnee Nation leadership identified the need for the tribe to comprehensively address its energy issues. During a strategic energy planning workshop a general framework was laid out and the Pawnee Nation Energy Task Force was created to work toward further development of the tribe’s energy vision. The overarching goals of the “first steps” project were to identify the most appropriate focus for its strategic energy initiatives going forward, and to provide information necessary to take the next steps in pursuit of the “best fit” energy options. Based on the request of Pawnee Nation’s Energy Task Force the research team, consisting Tribal personnel and Summit Blue Consulting, focused on a review of renewable energy resource development potential, funding sources and utility organizational along with energy savings options. Elements of the energy demand forecasting and characterization and demand side options review remained in the scope of work, but were only addressed at a high level. Description of Activities Performed Renewable Energy Resource Development Potential The research team reviewed existing data pertaining to the availability of biomass (focusing on woody biomass, agricultural biomass/bio-energy crops, and methane capture), solar, wind and hydropower resources on the Pawnee-owned lands. Using these data, combined with assumptions about costs and revenue streams, the research team performed preliminary feasibility assessments for each resource category. The research team also reviewed available funding resources and made recommendations to Pawnee Nation highlighting those resources with the greatest potential for financially-viable development, both in the near-term and over a longer time horizon. Energy Efficiency Options While this was not a major focus of the project, the research team highlighted common strategies for reducing energy use in buildings. The team also discussed the benefits of adopting a building energy code and introduced two model energy codes Pawnee Nation should consider for adoption. Summary of Current and Expected Future Electricity Usage The research team provided a summary overview of electricity usage patterns in current buildings and included discussion of known plans for new construction. Utility Options Review Pawnee Nation electric utility options were analyzed through a four-phase process, which included: 1) summarizing the relevant utility background information; 2) gathering relevant utility assessment data; 3) developing a set of realistic Pawnee electric utility service options, and 4) analyzing the various Pawnee electric utility service options for the Pawnee Energy Team’s consideration. III. Findings and Recommendations Due to a lack of financial incentives for renewable energy, particularly at the state level, combined mediocre renewable energy resources, renewable energy development opportunities are limited for Pawnee Nation. However, near-term potential exists for development of solar hot water at the gym, and an exterior wood-fired boiler system at the tribe’s main administrative building. Pawnee Nation should also explore options for developing LFGTE resources in collaboration with the City of Pawnee. Significant potential may also exist for development of bio-energy resources within the next decade. Pawnee Nation representatives should closely monitor market developments in the bio-energy industry, establish contacts with research institutions with which the tribe could potentially partner in grant-funded research initiatives. In addition, a substantial effort by the Kaw and Cherokee tribes is underway to pursue wind development at the Chilocco School Site in northern Oklahoma where Pawnee is a joint landowner. Pawnee Nation representatives should become actively involved in these development discussions and should explore the potential for joint investment in wind development at the Chilocco site.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

100-KE REACTOR CORE REMOVAL PROJECT ALTERNATIVE ANALYSIS WORKSHOP REPORT

On December 15-16, 2009, a 100-KE Reactor Core Removal Project Alternative Analysis Workshop was conducted at the Washington State University Consolidated Information Center, Room 214. Colburn Kennedy, Project Director, CH2M HILL Plateau Remediation Company (CHPRC) requested the workshop and Richard Harrington provided facilitation. The purpose of the session was to select the preferred Bio Shield Alternative, for integration with the Thermal Shield and Core Removal and develop the path forward to proceed with project delivery. Prior to this workshop, the S.A. Robotics (SAR) Obstruction Removal Alternatives Analysis (565-DLV-062) report was issued, for use prior to and throughout the session, to all the team members. The multidisciplinary team consisted ofrepresentatives from 100-KE Project Management, Engineering, Radcon, Nuclear Safety, Fire Protection, Crane/Rigging, SAR Project Engineering, the Department of Energy Richland Field Office, Environmental Protection Agency, Washington State Department of Ecology, Defense Nuclear Facility Safety Board, and Deactivation and Decommission subject matter experts from corporate CH2M HILL and Lucas. Appendix D contains the workshop agenda, guidelines and expectations, opening remarks, and attendance roster going into followed throughout the workshop. The team was successful in selecting the preferred alternative and developing an eight-point path forward action plan to proceed with conceptual design. Conventional Demolition was selected as the preferred alternative over two other alternatives: Diamond Wire with Options, and Harmonic Delamination with Conventional Demolition. The teams preferred alternative aligned with the SAR Obstruction Removal Alternative Analysis report conclusion. However, the team identified several Path Forward actions, in Appendix A, which upon completion will solidify and potentially enhance the Conventional Demolition alternative with multiple options and approaches to achieve project delivery. In brief, the Path Forward was developed to reconsider potential open air demolition areas; characterize to determine if any zircaloy exists, evaluate existing concrete data to determine additional characterization needs, size the new building to accommodate human machine interface and tooling, consider bucket thumb and use ofshape-charges in design, and finally to utilize complex-wide and industry explosive demolition lessons learned in the design approach. Appendix B documents these results from the team's use ofValue Engineering process tools entitled Weighted Analysis Alternative Matrix, Matrix Conclusions, Evaluation Criteria, and Alternative Advantages and Disadvantages. These results were further supported with the team's validation of parking-lot information sheets: memories (potential ideas to consider), issues/concerns, and assumptions, contained in Appendix C. Appendix C also includes the recorded workshop flipchart notes taken from the SAR Alternatives and Project Overview presentations. The SAR workshop presentations, including a 3-D graphic illustration demonstration video have been retained in the CHPRC project file, and were not included in this report due to size limitations. The workshop concluded with a round robin close-out where each member was engaged for any last minute items and meeting utility. In summary, the team felt the session was value added and looked forward to proceeding with the recommended actions and conceptual design.

36 MATERIALS SCIENCE↗

Aircraft digital flight control technical review

The Aircraft Digital Flight Control Technical Review was initiated by two pilot induced oscillation (PIO) incidents in the spring and summer of 1992. Maj. Gen. Franklin (PEO) wondered why the Air Force development process for digital flight control systems was not preventing PIO problems. Consequently, a technical review team was formed to examine the development process and determine why PIO problems continued to occur. The team was also to identify the 'best practices' used in the various programs. The charter of the team was to focus on the PIO problem, assess the current development process, and document the 'best practices.' The team reviewed all major USAF aircraft programs with digital flight controls, specifically, the F-15E, F-16C/D, F-22, F-111, C-17, and B-2. The team interviewed contractor, System Program Office (SPO), and Combined Test Force (CTF) personnel on these programs. The team also went to NAS Patuxent River to interview USN personnel about the F/A-18 program. The team also reviewed experimental USAF and NASA systems with digital flight control systems: X-29, X-31, F-15 STOL and Maneuver Technology Demonstrator (SMTD), and the Variable In-Flight Stability Test Aircraft (VISTA). The team also discussed the problem with other experts in the field including Ralph Smith and personnel from Calspan. The major conclusions and recommendations from the review are presented.

Davenport, Otha B.↗

A systems engineering initiative for NASA's space communications

In addition to but separate from the Red and Blue Teams commissioned by the NASA Administrator, NASA's Associate Administrator for Space Communications commissioned a Blue Team to review the Office of Space Communications (Code O) Core Program and determine how the program could be conducted faster, better, and cheaper, without compromising safety. Since there was no corresponding Red Team for the Code O Blue Team, the Blue Team assumed a Red Team independent attitude and challenged the status quo. The Blue Team process and results are summarized. The Associate Administrator for Space Communications subsequently convened a special management session to discuss the significance and implications of the Blue Team's report and to lay the groundwork and teamwork for the next steps, including the transition from engineering systems to systems engineering. The methodology and progress toward realizing the Code O Family vision and accomplishing the systems engineering initiative for NASA's space communications are presented.

Hornstein, Rhoda S.↗

Upward appraisal as a means for improving supervisory performance and promoting process improvement, with long-term implications for organizational change

This study represents the implementation phase of an organizational development project which was initiated last year in the Management Support Division (MSD) at Langley Research Center to diagnose organizational functioning. As a result of MSD survey data from last year's effort, a Quality Action Team was created to address the responses compiled from the MSD Organizational Assessment Questionnaire and Follow-Up Questionnaire. The team was officially named the MSD Employee Relations Improvement Team (MERIT). MERIT's goal was to analyze major concerns generated by the questionnaires and to present feasible solutions to management which would improve supervisory performance, promote process improvement; and ultimately, lead to a better organization. The team met weekly and was very disciplined in following guidelines needed to ensure a fully functioning team. Several TQM tools were used during the team process, including brainstorming and the cause and effect diagram. One of the products produced by MERIT was a 'report card', more formally known as an upward appraisal system, to evaluate supervisory performance in the division office, its three branches, and in teams. Major areas of emphasis on the 47 item report card were those identified by employees through the previously administered questionnaires as needing to be improved; specifically, training, recognition, teamwork, supervision and leadership, and communication. MERIT created an enlarged and modified version of the report card which enabled scores for each individual supervisor to be recorded on a separate form, along with summary results and employee comments. Report card results have been compiled and fed back to the Division Chief and Assistant Division Chief. These individuals will in turn, feed the results back to the remaining supervisors and the team leaders. Although results differ among supervisors, some similarities exist. Communication generally appears to be adequate, which represents an improvement over last year. In contrast, recognition and teamwork are the two major areas where improvement in supervisory performance seems to be most needed. The initial report card results will serve as a baseline against which future performance ratings will be compared. Once supervisors have been presented with their data and given an opportunity to analyze and discus the results, they will be assisted in developing an action plan for improving their performance and work processes. They will be provided with ongoing support from management in following through with the action plan.

Siegfeldt, Denise V.↗

Verification and validation of a reliable multicast protocol

This paper describes the methods used to specify and implement a complex communications protocol that provides reliable delivery of data in multicast-capable, packet-switching telecommunication networks. The protocol, called the Reliable Multicasting Protocol (RMP), was developed incrementally by two complementary teams using a combination of formal and informal techniques in an attempt to ensure the correctness of the protocol implementation. The first team, called the Design team, initially specified protocol requirements using a variant of SCR requirements tables and implemented a prototype solution. The second team, called the V&V team, developed a state model based on the requirements tables and derived test cases from these tables to exercise the implementation. In a series of iterative steps, the Design team added new functionality to the implementation while the V&V team kept the state model in fidelity with the implementation through testing. Test cases derived from state transition paths in the formal model formed the dialogue between teams during development and served as the vehicles for keeping the model and implementation in fidelity with each other. This paper describes our experiences in developing our process model, details of our approach, and some example problems found during the development of RMP.

Callahan, John R.↗

Toward fidelity between specification and implementation

This paper describes the methods used to specify and implement a complex communications protocol that provides reliable delivery of data in multicast-capable, packet-switching telecommunication networks. The protocol, called the Reliable Multicasting Protocol (RMP), was developed incrementally by two complementary teams using a combination of formal and informal techniques in an attempt to ensure the correctness of the protocol implementation. The first team, called the Design team, initially specified protocol requirements using a variant of SCR requirements tables and implemented a prototype solution. The second team, called the V&V team, developed a state model based on the requirements tables and derived test cases from these tables to exercise the implementation. In a series of iterative steps, the Design team added new functionality to the implementation while the V&V team kept the state model in fidelity with the implementation through testing. Test cases derived from state transition paths in the formal model formed the dialogue between teams during development and served as the vehicles for keeping the model and implementation in fidelity with each other. This paper describes our experiences in developing our process model, details of our approach, and some example problems found during the development of RMP.

Callahan, John R.↗

Low Cost Rapid Response Spacecraft, (LCRRS): A Research Project in Low Cost Spacecraft Design and Fabrication in a Rapid Prototyping Environment

The Low Cost Rapid Response Spacecraft (LCRRS) is an ongoing research development project at NASA Ames Research Center (ARC), Moffett Field, California. The prototype spacecraft, called Cost Optimized Test for Spacecraft Avionics and Technologies (COTSAT) is the first of what could potentially be a series of rapidly produced low-cost satellites. COTSAT has a target launch date of March 2009 on a SpaceX Falcon 9 launch vehicle. The LCRRS research system design incorporates use of COTS (Commercial Off The Shelf), MOTS (Modified Off The Shelf), and GOTS (Government Off The Shelf) hardware for a remote sensing satellite. The design concept was baselined to support a 0.5 meter Ritchey-Chretien telescope payload. This telescope and camera system is expected to achieve 1.5 meter/pixel resolution. The COTSAT team is investigating the possibility of building a fully functional spacecraft for $500,000 parts and $2,000,000 labor. Cost is dramatically reduced by using a sealed container, housing the bus and payload subsystems. Some electrical and RF designs were improved/upgraded from GeneSat-1 heritage systems. The project began in January 2007 and has yielded two functional test platforms. It is expected that a flight-qualified unit will be finished in December 2008. Flight quality controls are in place on the parts and materials used in this development with the aim of using them to finish a proto-flight satellite. For LEO missions the team is targeting a mission class requiring a minimum of six months lifetime or more. The system architecture incorporates several design features required by high reliability missions. This allows for a true skunk works environment to rapidly progress toward a flight design. Engineering and fabrication is primarily done in-house at NASA Ames with flight certifications on materials. The team currently employs seven Full Time Equivalent employees. The success of COTSATs small team in this effort can be attributed to highly cross trained engineering team. The engineers on the team are capable of functioning in two to three engineering disciplines which allows highly efficient interdisciplinary engineering collaboration. NASA Ames is actively proposing mission concepts to use the COTSAT platform to accomplish science. If the COTSAT team validates this approach, it will allow the possibility for remote sensing missions to produce a high science yield for minimal cost and reduced schedule. Another aim of this approach is to yield an accelerated pathway from a Phase A study to mission launch. Leaders in the aerospace industry have shown interest in this methodology. Several visits and tours have been given in the lab. Although the concept of low-cost development is initially met with skepticism from some within the prohibitive aerospace industry, the project's efforts have been highly praised for the accomplishments met within a limited time and budget. Overall the development has progressed tremendously well and the team is answering critical questions for current and future low-cost small satellite developments. COTSAT subsystems are not limited to a specific weight class and could be adapted to produce smaller platforms and to fit various launch vehicles.

Spremo, Stevan↗

GeoLab: A Geological Workstation for Future Missions

The GeoLab glovebox was, until November 2012, fully integrated into NASA's Deep Space Habitat (DSH) Analog Testbed. The conceptual design for GeoLab came from several sources, including current research instruments (Microgravity Science Glovebox) used on the International Space Station, existing Astromaterials Curation Laboratory hardware and clean room procedures, and mission scenarios developed for earlier programs. GeoLab allowed NASA scientists to test science operations related to contained sample examination during simulated exploration missions. The team demonstrated science operations that enhance theThe GeoLab glovebox was, until November 2012, fully integrated into NASA's Deep Space Habitat (DSH) Analog Testbed. The conceptual design for GeoLab came from several sources, including current research instruments (Microgravity Science Glovebox) used on the International Space Station, existing Astromaterials Curation Laboratory hardware and clean room procedures, and mission scenarios developed for earlier programs. GeoLab allowed NASA scientists to test science operations related to contained sample examination during simulated exploration missions. The team demonstrated science operations that enhance the early scientific returns from future missions and ensure that the best samples are selected for Earth return. The facility was also designed to foster the development of instrument technology. Since 2009, when GeoLab design and construction began, the GeoLab team [a group of scientists from the Astromaterials Acquisition and Curation Office within the Astromaterials Research and Exploration Science (ARES) Directorate at JSC] has progressively developed and reconfigured the GeoLab hardware and software interfaces and developed test objectives, which were to 1) determine requirements and strategies for sample handling and prioritization for geological operations on other planetary surfaces, 2) assess the scientific contribution of selective in-situ sample characterization for mission planning, operations, and sample prioritization, 3) evaluate analytical instruments and tools for providing efficient and meaningful data in advance of sample return and 4) identify science operations that leverage human presence with robotic tools. In the first year of tests (2010), GeoLab examined basic glovebox operations performed by one and two crewmembers and science operations performed by a remote science team. The 2010 tests also examined the efficacy of basic sample characterization [descriptions, microscopic imagery, X-ray fluorescence (XRF) analyses] and feedback to the science team. In year 2 (2011), the GeoLab team tested enhanced software and interfaces for the crew and science team (including Web-based and mobile device displays) and demonstrated laboratory configurability with a new diagnostic instrument (the Multispectral Microscopic Imager from the JPL and Arizona State University). In year 3 (2012), the GeoLab team installed and tested a robotic sample manipulator and evaluated robotic-human interfaces for science operations.

Evans, Cynthia↗

Domain-Specific Languages and Diagram Customization for a Concurrent Engineering Environment

A major open question for advocates of Model-Based Systems Engineering (MBSE) is the question of how system and subsystem engineers will work together. The Systems Modeling Language (SysML), like any language intended for a large audience, is in tension between the desires for simplicity and for expressiveness. In order to be more expressive, many specialized language elements may be introduced, which will unfortunately make a complete understanding of the language a more daunting task. While this may be acceptable for systems modelers, it will increase the challenge of including subsystem engineers in the modeling effort. One possible answer to this situation is the use of Domain-Specific Languages (DSL), which are fully supported by the Unified Modeling Language (UML). SysML is in fact a DSL for systems engineering. The expressive power of a DSL can be enhanced through the use of diagram customization. Various domains have already developed their own schematic vocabularies. Within the space engineering community, two excellent examples are the propulsion and telecommunication subsystems. A return to simple box-and-line diagrams (e.g., the SysML Internal Block Diagram) are in many ways a step backward. In order allow subsystem engineers to contribute directly to the model, it is necessary to make a system modeling tool at least approximate in accessibility to drawing tools like Microsoft PowerPoint and Visio. The challenge is made more extreme in a concurrent engineering environment, where designs must often be drafted in an hour or two. In the case of the Jet Propulsion Laboratory's Team X concurrent design team, a subsystem is specified using a combination of PowerPoint for drawing and Excel for calculation. A pilot has been undertaken in order to meld the drawing portion and the production of master equipment lists (MELs) via a SysML authoring tool, MagicDraw. Team X currently interacts with its customers in a process of sharing presentations. There are several inefficiencies that arise from this situation. The first is that a customer team must wait two weeks to a month (which is 2-4 times the duration of most Team X studies themselves) for a finalized, detailed design description. Another is that this information must be re-entered by hand into the set of engineering artifacts and design tools that the mission concept team uses after a study is complete. Further, there is no persistent connection to Team X or institutionally shared formulation design tools and data after a given study, again reducing the direct reuse of designs created in a Team X study. This paper presents the underpinnings of subsystem DSLs as they were developed for this pilot. This includes specialized semantics for different domains as well as the process by which major categories of objects were derived in support of defining the DSLs. The feedback given to us by the domain experts on usability, along with a pilot study with the partial inclusion of these tools is also discussed.

Cole, Bjorn↗

The Suomi National Polar-Orbiting Partnership (SNPP): Continuing NASA Research and Applications

The Suomi National Polar-orbiting Partnership (SNPP) satellite was successfully launched into a polar orbit on October 28, 2011 carrying 5 remote sensing instruments designed to provide data to improve weather forecasts and to increase understanding of long-term climate change. SNPP provides operational continuity of satellite-based observations for NOAA's Polar-orbiting Operational Environmental Satellites (POES) and continues the long-term record of climate quality observations established by NASA's Earth Observing System (EOS) satellites. In the 2003 to 2011 pre-launch timeframe, NASA's SNPP Science Team assessed the adequacy of the operational Raw Data Records (RDRs), Sensor Data Records (SDRs), and Environmental Data Records (EDRs) from the SNPP instruments for use in NASA Earth Science research, examined the operational algorithms used to produce those data records, and proposed a path forward for the production of climate quality products from SNPP. In order to perform these tasks, a distributed data system, the NASA Science Data Segment (SDS), ingested RDRs, SDRs, and EDRs from the NOAA Archive and Distribution and Interface Data Processing Segments, ADS and IDPS, respectively. The SDS also obtained operational algorithms for evaluation purposes from the NOAA Government Resource for Algorithm Verification, Independent Testing and Evaluation (GRAVITE). Within the NASA SDS, five Product Evaluation and Test Elements (PEATEs) received, ingested, and stored data and performed NASA's data processing, evaluation, and analysis activities. The distributed nature of this data distribution system was established by physically housing each PEATE within one of five Climate Analysis Research Systems (CARS) located at either at a NASA or a university institution. The CARS were organized around 5 key EDRs directly in support of the following NASA Earth Science focus areas: atmospheric sounding, ocean, land, ozone, and atmospheric composition products. The PEATES provided the system level interface with members of the NASA SNPP Science Team and other science investigators within each CARS. A sixth Earth Radiation Budget CARS was established at NASA Langley Research Center (NASA LaRC) to support instrument performance, data evaluation, and analysis for the SNPP Clouds and the Earth's Radiant Budget Energy System (CERES) instrument. Following the 2011 launch of SNPP, spacecraft commissioning, and instrument activation, the NASA SNPP Science Team evaluated the operational RDRs, SDRs, and EDRs produced by the NOAA ADS and IDPS. A key part in that evaluation was the NASA Science Team's independent processing of operational RDRs and SDRs to EDRs using the latest NASA science algorithms. The NASA science evaluation was completed in the December 2012 to April 2014 timeframe with the release of a series of NASA Science Team Discipline Reports. In summary, these reports indicated that the RDRs produced by the SNPP instruments were of sufficiently high quality to be used to create data products suitable for NASA Earth System science and applications. However, the quality of the SDRs and EDRs were found to vary greatly when considering suitability for NASA science. The need for improvements in operational algorithms, adoption of different algorithmic approaches, greater monitoring of on-orbit instrument calibration, greater attention to data product validation, and data reprocessing were prominent findings in the reports. In response to these findings, NASA, in late 2013, directed the NASA SNPP Science Team to use SNPP instrument data to develop data products of sufficiently high quality to enable the continuation of EOS time series data records and to develop innovative, practical applications of SNPP data. This direction necessitated a transition of the SDS data system from its pre-launch assessment mode to one of full data processing and production. To do this, the PEATES, which served as NASA's data product testing environment during the prelaunch and early on-orbit periods, were transitioned to Science Investigator-led Processing Systems (SIPS). The distributed data architecture was maintained in this new system by locating the SIPS at the same institutions at which the CARS and PEATES were located. The SIPS acquire raw SNPP instrument Level 0 (i.e. RDR) data over the full SNPP mission from the NOAA ADS and IDPS through the NASA SDS Data Distribution and Depository Element (SD3E). The SIPS process those data into NASA Level 1, Level 2, and global, gridded Level 3 standard products using peer-reviewed algorithms provided by members of the NASA Science Team. The SIPS work with the NASA SNPP Science Team in obtaining enhanced, refined, or alternate real-time algorithms to support the capabilities of the Direct Readout Laboratory (DRL). All data products, algorithm source codes, coefficients, and auxiliary data used in product generation are archived in an assigned NASA Distributed Active Archive Center (DAAC).

remote sensing↗

Identification and Classification of Common Risks in Space Science Missions

Due to the highly constrained schedules and budgets that NASA missions must contend with, the identification and management of cost, schedule and risks in the earliest stages of the lifecycle is critical. At the Jet Propulsion Laboratory (JPL) it is the concurrent engineering teams that first address these items in a systematic manner. Foremost of these concurrent engineering teams is Team X. Started in 1995, Team X has carried out over 1000 studies, dramatically reducing the time and cost involved, and has been the model for other concurrent engineering teams both within NASA and throughout the larger aerospace community. The ability to do integrated risk identification and assessment was first introduced into Team X in 2001. Since that time the mission risks identified in each study have been kept in a database. In this paper we will describe how the Team X risk process is evolving highlighting the strengths and weaknesses of the different approaches. The paper will especially focus on the identification and classification of common risks that have arisen during Team X studies of space based science missions.

Risk Identification↗

Digital Model-Based Engineering: Expectations, Prerequisites, and Challenges of Infusion

Digital model-based engineering (DMbE) is the use of digital artifacts, digital environments, and digital tools in the performance of engineering functions. DMbE is intended to allow an organization to progress from documentation-based engineering methods to digital methods that may provide greater flexibility, agility, and efficiency. The term 'DMbE' was developed as part of an effort by the Model-Based Systems Engineering (MBSE) Infusion Task team to identify what government organizations might expect in the course of moving to or infusing MBSE into their organizations. The Task team was established by the Interagency Working Group on Engineering Complex Systems, an informal collaboration among government systems engineering organizations. This Technical Memorandum (TM) discusses the work of the MBSE Infusion Task team to date. The Task team identified prerequisites, expectations, initial challenges, and recommendations for areas of study to pursue, as well as examples of efforts already in progress. The team identified the following five expectations associated with DMbE infusion, discussed further in this TM: (1) Informed decision making through increased transparency, and greater insight. (2) Enhanced communication. (3) Increased understanding for greater flexibility/adaptability in design. (4) Increased confidence that the capability will perform as expected. (5) Increased efficiency. The team identified the following seven challenges an organization might encounter when looking to infuse DMbE: (1) Assessing value added to the organization. Not all DMbE practices will be applicable to every situation in every organization, and not all implementations will have positive results. (2) Overcoming organizational and cultural hurdles. (3) Adopting contractual practices and technical data management. (4) Redefining configuration management. The DMbE environment changes the range of configuration information to be managed to include performance and design models, database objects, as well as more traditional book-form objects and formats. (5) Developing information technology (IT) infrastructure. Approaches to implementing critical, enabling IT infrastructure capabilities must be flexible, reconfigurable, and updatable. (6) Ensuring security of the single source of truth (7) Potential overreliance on quantitative data over qualitative data. Executable/ computational models and simulations generally incorporate and generate quantitative vice qualitative data. The Task team also developed several recommendations for government, academia, and industry, as discussed in this TM. The Task team recommends continuing beyond this initial work to further develop the means of implementing DMbE and to look for opportunities to collaborate and share best practices.

Hale, J. P.↗

Collaborative Systems Engineering in the Ascent Abort-2 Crew Module/Separation Ring Project

Generally speaking, systems engineering (SE) tool-sets face a dilemma balancing power and accessibility. High-powered SE tools (MagicDraw, Cradle, Core, etc.) tend to be specialized and are available only to highly trained Systems Engineers, and/or through the use of a 'back room' developer team making the output products available to the broader team. On the other hand, highly accessible tools (MS Word, Excel, etc.) do not have the power to implement SE in a rigorous manner. NASA has to test all aspects of the new human-rated Orion Multi-Purpose Crew Vehicle spacecraft prior to its first crewed mission. The test program includes uncrewed launch abort flight tests to demonstrate the capability to save the crew in the event that a launch failure occurs. Orion's second abort flight test will be a low-altitude flight test known as "Ascent Abort 2 (AA-2)." This test is currently scheduled to be carried out at Cape Canaveral Air Force Station's Space Launch Complex 46 (SLC-46) in Florida in 2019. NASA's in-house AA-2 Crew Module and Separation Ring (CSR) Team is producing the crew module and separation ring. Operating jointly as both an Advanced Exploration Systems (AES) Project and an Orion Project, the CSR project charter includes development of innovative, streamlined and generally more efficient practices for creation of flight hardware and software. One result of this tasking has been development of a collaborative and data-centric systems engineering environment within the team's shared web environment (Microsoft SharePoint). Through the use of built-in, 'out of the box capabilities' present in MS SharePoint, the CSR Systems Engineering team has created (with some limited developer support) a data-centric architecture for the project's SE implementation, including functional and interface analysis, requirements development and management, risk management, verification planning and management, test results, and end item management. Data elements are linked between data structures so as to define and control relationships between item types, link requirements to parents and children, and link tests to the requirements that they verify. The overall project team integration is increased by also linking SE content to project management content over the project life cycle, including team communication, action items, configuration management, decisional and meeting materials, and life cycle reviews. This presentation will provide an overview of the collaborative SE environment, showing how it provides the power for a number of SE tasks while still providing the accessibility and transparency to allow the full project team to collaborate and succeed. Given the project phase, we'll be able to present a nearly full lifecycle discussion, from concept through verification and approaching delivery.

Systems Engineering environments↗