Search NASA⌕ Search

SEARCH · Search NASA

Results for “maturity model”

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 55 records · Page 3

Maturation of Dynamic Power Convertors for Radioisotope Power Systems

Dynamic Radioisotope Power Systems (DRPS) are being developed by NASA’s Radioisotope Power Systems (RPS) Program in collaboration with the U.S. Department of Energy (DOE) for space science and exploration missions. A development effort is currently underway to mature dynamic power convertors for infusion into a potential future flight generator. This convertor maturation effort was formulated by the RPS Program at NASA Headquarters based on successful maturation models and utilizes expertise from agency’s technology and mission centers to support requirements development and technology assessments. The effort is being executed by Glenn Research Center’s (GRC) DRPS Project and the Thermal Energy Conversion Branch. The Dynamic Power Convertor (DPC) contracts consist of three phases to enable design, fabrication, and independent assessment of prototypes after delivery to the government. The contracts are intended to gather data on candidate dynamic conversion technologies to fill knowledge gaps, support assessments of dynamic conversion technologies, and elicit generator requirements. The 110-watt Stirling Radioisotope Generator (SRG-110) and Advanced Stirling Radioisotope Generator (ASRG) flight development projects provided Stirling convertor demonstration units and engineering models to verify and validate convertors against performance specifications and mission requirements. These units utilize temperature resistant materials and non-contacting bearings to demonstrate wear-free, long-life operation. This maturation effort builds on past lessons-learned and new requirements focused on demonstrating convertor robustness to critical environments meant to stress key aspects of each convertor within the margins of the design. This effort seeks to realize the full potential of dynamic power conversion technologies for NASA’s space science and exploration missions.

Wilson, Scott↗

Maturation of Dynamic Power Convertors for Radioisotope Power Systems

Dynamic Radioisotope Power Systems (DRPS) are being developed by NASA's RPS Program in collaboration with the U.S. Department of Energy (DOE) for space science and exploration missions. A development effort is currently underway to mature dynamic power convertors for infusion into a potential future flight generator. This convertor maturation effort was formulated by the RPS Program at NASA Headquarters based on successful maturation models and utilizes expertise from agency technology and mission centers to support requirements development and technology assessments. The effort is being executed by Glenn Research Center's Dynamic Radioisotope Power Systems (DRPS) project and the Thermal Energy Conversion Branch. The Dynamic Power Convertor (DPC) contracts consist of three phases to enable design, fabrication, and independent assessment after delivery to the government. The contracts are intended to gather data on candidate dynamic conversion technologies to fill knowledge gaps, support assessments of dynamic conversion technologies, and elicit generator requirements. The SRG-110 (Stirling Radioisotope Generator) and ASRG (Advanced Stirling Radioisotope Generator) flight development projects provided Stirling convertor demonstration units and engineering models to verify and validate convertors against performance specifications and mission requirements. These units utilize temperature resistance materials and non-contacting bearings to demonstrate wear-free, long-life operation. This maturation effort builds on past lessons learned and new requirements focused on demonstrating convertor robustness to critical environments meant to stress key aspects of each convertor within the margins of the design. This effort seeks to realize the full potential of dynamic power conversion technologies for NASA's space science and exploration missions.

Wilson, Scott↗

SEP Forecasting from the Lunar Gateway

The European Radiation Sensor Array (ERSA) planned to fly onboard the Gateway lunar space station will include a Standard Radiation Environment Monitor (SREM) energetic particle detector. The SREM detector has a long heritage and has flown aboard the Earth-orbiting INTEGRAL and PROBA-1 satellites, the L2 experiments Herschel and Planck, and the inner solar system mission Rosetta. SREM measures energetic protons between 11 – 250 MeV, enabling it to detect proton and electron enhancements due to solar energetic particle (SEP) events, which are potentially hazardous for humans and hardware in space. The UMASEP model, developed by Marlon Nuñez at the University of Malaga, ingests energetic particle measurements to produce forecasts of time to threshold crossing and the maximum flux expected within a certain time window. UMASEP is a mature model that has been running in real time for many years and has demonstrated forecasting skill. We plan to develop a UMASEP-Gateway >30 MeV forecast module using historical INTEGRAL/SREM data so that the model may begin forecasting as soon as ERSA begins returning real time data. UMASEP-Gateway will use the environment at the habitat to produce forecasts. This work will enable forecasting using the in situ environment at the spacecraft and will additionally act as a first step towards producing SEP forecasts directly at the vehicle where humans reside, a key capability that will be needed for exploration missions beyond the Moon.

space weather↗

Code and Solution Verification Assessment of the CTF Thermal Hydraulic Subchannel Code

CTF is a thermal-hydraulics subchannel code jointly developed by Oak Ridge National Laboratory and North Carolina State University. Over the past seven years, the Consortium for Advanced Simulation of Light Water Reactors (CASL) has made a significant investment in developing CTF so it can be used to model light water reactors, including nominal operating conditions, departure from nucleate boiling analysis, and transients ranging from loss of flow to reactivity insertion accidents. In addition to implementing new modeling capabilities and developing the user input and output interface, extensive work has been performed to improve the code’s quality assurance program, resulting in a development process that conforms with NQA-1 requirements. The CASL program follows the Predictive Capability Maturity Model (PCMM) approach for assessing code quality, which emphasizes performing code verification(ensuring the code converges to the correct answer) and solution verification (ensuring the code converges for the intended application). Code and solution verification are used to identify uncertainty errors introduced by numerical approximations in the code and are important for demonstrating that the model is coded without error, which is an important aspect of the Best Estimate plus Uncertainty method. This paper presents a comprehensive overview of the code and solution verification testing that has been performed on CTF. A top-down approach is taken in which the intended CTF applications are presented, followed by the code features required for their modeling. These features are then linked to the applicable code and solution verification tests that demonstrate proper functioning. Past testing efforts are summarized, and new tests are added to help close gaps in the presented test matrix. Rather than performing “one-off” exercises, these tests are added to the automated CTF regression test suite to ensure continual code quality.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

Lunar soil evolution processes and Apollo 16 core 60013/60014

Soils of the 62-cm deep Apollo 16 double drive tube 60013/14 are mature at the top and submature at the bottom. Modal analyses of 5529 grains from the 90-150 micrometers and the 500-1000 micrometers fractions from 12 levels of the core show that, in general, agglutinate abundance increases somewhat monotonically to the top and mimics the Is/FeO profile. There is a general decrease in the modal abundance of monomineralic fragments towards the top, suggesting that agglutinates were formed in part at the expense of monomineralic grains, especially feldspars, which are by far the most abundant mineral in these soils. In detail, the top 27 cm of the core differs from the bottom 21 cm, and the middle 14 cm is intermediate in its properties. In the upper segment, variations in the abundances of feldspars correspond with those of feldspathic fragmental breccias and cataclastic anorthosites; in the bottom segment, a similar but weak correspondence between feldspars and crystalline matrix breccias is observed. Mixing of the comminuted products of these three rock types likely produced the bulk of the core material. Many single feldspars in all size fractions are remarkably fresh, show no damage from shock, and are similar in appearance to the large feldspars in anorthosites and feldspathic fragmental breccias, which we consider to be the primary sources of single feldspars in this core. Major (Na, Al, Si, K, Ca) and minor (Fe, Ba) element analyses of 198 single feldspar grains indicate the presence of only one population of feldspars, which is consistent with our interpretation of feldspar provenance. Classification of 890 monomineralic feldspar, olivine, pyroxene, and glass spherules on the basis of the presence or absence of thin brownish coating--related to reworking at the surface--shows that coated grains are much more abundant in the top segment than in the bottom segment. A comparison with the mixing and maturation model (McKay et al., 1977) of soils in the core 60009/10, some 60 m away from 60013/14, shows that mixtures of an immature, nearly pure plagioclase soil (dominant in 60009/10) and another immature, crystalline breccia-rich soil (dominant in 60013/14) may have matured through in situ reworking to produce the soils under investigation. We conclude that the soils in this core are products of mixing along soil evolution Path 2 of McKay et al. (1974). Superimposed on that soil column is the reworking of the upper part, which has evolved more recently along Path 1. This core thus represents a consanguineous column of the lunar regolith with an upper reworked segment.

short duration↗

The experience factory: Can it make you a 5? or what is its relationship to other quality and improvement concepts?

The concepts of quality improvements have permeated many businesses. It is clear that the nineties will be the quality era for software and there is a growing need to develop or adapt quality improvement approaches to the software business. Thus we must understand software as an artifact and software as a business. Since the business we are dealing with is software, we must understand the nature of software and software development. The software discipline is evolutionary and experimental; it is a laboratory science. Software is development not production. The technologies of the discipline are human based. There is a lack of models that allow us to reason about the process and the product. All software is not the same; process is a variable, goals are variable, etc. Packaged, reusable, experiences require additional resources in the form of organization, processes, people, etc. There have been a variety of organizational frameworks proposed to improve quality for various businesses. The ones discussed in this presentation include: Plan-Do-Check-Act, a quality improvement process based upon a feedback cycle for optimizing a single process model/production line; the Experience Factory/Quality Improvement Paradigm, continuous improvements through the experimentation, packaging, and reuse of experiences based upon a business's needs; Total Quality Management, a management approach to long term success through customer satisfaction based on the participation of all members of an organization; the SEI capability maturity model, a staged process improvement based upon assessment with regard to a set of key process areas until you reach a level 5 which represents a continuous process improvement; and Lean (software) Development, a principle supporting the concentration of the production on 'value added' activities and the elimination of reduction of 'not value added' activities.

Basili, Victor R.↗

Credibility Framework (CF) v.1.0

Credibility Framework provides tools such as PIRT (Phenomena Identification and Ranking Table) and PCMM (Predictive Capability Maturity Model) configurable by non-programmers through simple Excel spreadsheets for tailoring the credibility process to meet the needs of the analysis provider organizations, customers and regulatory agencies. Sandia National Laboratories is a multimission laboratory managed and operated by National Technology & Engineering Solutions of Sandia, LLC, a wholly owned subsidiary of Honeywell International Inc., for the U.S. Department of Energy’s National Nuclear Security Administration under contract DE-NA0003525. SAND2020-10230 M

Clay, RobertL.↗

Facility Cybersecurity Framework Best Practices

Federal facilities are increasingly adopting automation and connecting to the Internet creating an energy-internet-of-things environment that converges operational technology (OT) and information technology (IT). Today's buildings increasingly weave together networked sensors and cyber and physical systems that enable data to be collected, aggregated, exchanged, stored and monetized in new ways. Building technological advances have created new energy technology, services, markets and value creation opportunities (e.g. transactive energy, two-way grid communications, machine learning, and increased use of renewable and distributed energy resources). But as larger data sets are being exchanged at faster speeds between an increasing number of OT systems, it becomes more difficult to protect the security of the data lifecycle and the physical equipment it interacts with. These challenges are especially difficult to overcome because the economic and environmental gain (interoperability, big data, social networks and ubiquitous information sharing) are driving these prominent trends in the digital age. Often cybersecurity is an afterthought. The U.S. Department of Energy’s (DOE) Federal Energy Management Program (FEMP) funded the Pacific Northwest National Laboratory (PNNL) to develop various cybersecurity tools, trainings, and reports to aid federal facility managers – and other building owners and operators – in better applying frameworks and lessons learned from the National Institute of Standards and Technology (NIST) Cybersecurity Framework (CSF), risk management framework (RMF), DOE’s cybersecurity capability maturity model (C2M2), and a wide variety of industry best practices and guidance documents (i.e., NIST 800 series, Department of Defense United Facilities Criteria). This set of tools, collectively known as the FEMP Facility-Related Control System Cyber Toolkit (FRCS Cyber Toolkit)2, is focused on cybersecurity concerns from facility-related control systems and other operational technology (OT), such as industrial control systems (ICS). The FRCS Cyber Toolkit can be applied across six of the sixteen critical infrastructure sectors designated by the Department of Homeland Security, including government facilities, healthcare and public health, commercial facilities (e.g., public assembly, offices, lodging), financial services (e.g., banking and insurance), emergency services (e.g., fire and police stations), and information technology. With increasingly converged IT and OT systems, it is crucial to address OT cybersecurity considerations and assess how the seam of these two systems could impact the overall cybersecurity posture of a facility. The objective of this report is to provide an overview of the best possible method to use FRCS Cyber Toolkit (section 2.0) and distilled cybersecurity best practices for the federal facilities to address growing non-linear cyber threats (section 3.0). Recommendations in this document are aggregated from several NIST and other documents (see Appendix A for additional details).

97 MATHEMATICS AND COMPUTING↗

Development of an Energy Services Interface for the EGoT

The Energy Services Interface (ESI) is a set of rules that ensure private, secure, and trustworthy information exchange between Grid Service Providers (GSPs) and utility customers. Large-scale adoption of Distributed Energy Resources (DERs) will be necessary for GSPs to dispatch effective grid services, and to stimulate technological innovations in DER and DERMS (DER Management Systems) technologies, as well as novel grid service programs. The ESI promotes these objectives by advancing a set of rules and interoperability requirements that define bi-directional, service-oriented, logical interfaces between GSPs and customers’ DERs, with expectations for privacy, security, and trust. The ESI rules and interoperability requirements establish boundaries between customers and GSPs that delineate the functions and responsibilities that must be implemented by the developers of Energy Grid of Things (EGoT) ecosystem products. These rules impose constraints on the implementation of a DERMS. The ESI interoperability requirements are based on the Interoperability Maturity Model (IMM), developed by the Grid Modernization Laboratory Consortium. By emphasizing private, secure, and trustworthy information exchange, and by mandating a service-oriented and interoperable architecture, the ESI promotes the development of an EGoT ecosystem that motivates customer participation and technological innovation. Interoperability will encourage innovation by reducing barriers to entry and increasing confidence of stakeholders. Customers will be willing to participate in DER service programs that establish trust and emphasize customer choice. Large-scale customer participation ensures GSPs have ample DER resources to provide grid services that have significant impact on grid reliability and reduce electricity cost for consumers. This in turn signals economic opportunities that encourage innovation, resulting in the development of a robust EGoT ecosystem.

24 POWER TRANSMISSION AND DISTRIBUTION↗

PSU ESI Review

A guide to developing an Energy Service Interface (ESI) was created as part of the Grid Modernization Laboratory Consortium 2.5.2 ESI project. The approach applies device-agnostic and service-oriented ESI principles and leverages documents such as the Interoperability Maturity Model and Common Grid Service Definitions to provide a methodology to review, develop, and update standards and profiles to engage distributed energy resources (DER) to provide grid services. This document evaluates the ESI developed by Portland State University’s Power Engineering Group under the Electric Grid of Things project funded by the U.S. Department of Energy. The evaluation explores the compliance of this specific implementation with the GMLC ESI principles to provide an example of an ESI profile and gap analysis.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Process improvement as an investment: Measuring its worth

This paper discusses return on investment (ROI) generated from software process improvement programs. It details the steps needed to compute ROI and compares these steps from the perspective of two process improvement approaches: the widely known Software Engineering Institute's capability maturity model and the approach employed by NASA's Software Engineering Laboratory (SEL). The paper then describes the specific investments made in the SEL over the past 18 years and discusses the improvements gained from this investment by the production organization in the SEL.

Mcgarry, Frank↗

Process maturity progress at Motorola Cellular Systems Division

We believe that the key success elements are related to our recognition that Software Process Improvement (SPI) can and should be organized, planned, managed, and measured as if it were a project to develop a new process, analogous to a software product. We believe that our process improvements have come as the result of these key elements: use of a rigorous, detailed requirements set (Capability Maturity Model, CMM); use of a robust, yet flexible architecture (IEEE 1074); use of a SPI project, resourced and managed like other work, to produce the specifications and implement them; and development of both internal and external goals, with metrics to support them.

Borgstahl, Ron↗

Software Past, Present, and Future: Views from Government, Industry and Academia

Views from the NASA CIO NASA Software Engineering Workshop on software development from the past, present, and future are presented. The topics include: 1) Software Past; 2) Software Present; 3) NASA's Largest Software Challenges; 4) 8330 Software Projects in Industry Standish Groups 1994 Report; 5) Software Future; 6) Capability Maturity Model (CMM): Software Engineering Institute (SEI) levels; 7) System Engineering Quality Also Part of the Problem; 8) University Environment Trends Will Increase the Problem in Software Engineering; and 9) NASA Software Engineering Goals.

Holcomb, Lee↗

A Matrix Approach to Software Process Definition

The Software Engineering Laboratory (SEL) is currently engaged in a Methodology and Metrics program for the Information Systems Center (ISC) at Goddard Space Flight Center (GSFC). This paper addresses the Methodology portion of the program. The purpose of the Methodology effort is to assist a software team lead in selecting and tailoring a software development or maintenance process for a specific GSFC project. It is intended that this process will also be compliant with both ISO 9001 and the Software Engineering Institute's Capability Maturity Model (CMM). Under the Methodology program, we have defined four standard ISO-compliant software processes for the ISC, and three tailoring criteria that team leads can use to categorize their projects. The team lead would select a process and appropriate tailoring factors, from which a software process tailored to the specific project could be generated. Our objective in the Methodology program is to present software process information in a structured fashion, to make it easy for a team lead to characterize the type of software engineering to be performed, and to apply tailoring parameters to search for an appropriate software process description. This will enable the team lead to follow a proven, effective software process and also satisfy NASA's requirement for compliance with ISO 9001 and the anticipated requirement for CMM assessment. This work is also intended to support the deployment of sound software processes across the ISC.

Schultz, David↗

Using Pilots to Assess the Value and Approach of CMMI Implementation

At Goddard Space Flight Center (GSFC), we have chosen to use Capability Maturity Model Integrated (CMMI) to guide our process improvement program. Projects at GSFC consist of complex systems of software and hardware that control satellites, operate ground systems, run instruments, manage databases and data and support scientific research. It is a challenge to launch a process improvement program that encompasses our diverse systems, yet is manageable in terms of cost effectiveness. In order to establish the best approach for improvement, our process improvement effort was divided into three phases: 1) Pilot projects; 2) Staged implementation; and 3) Sustainment and continual improvement. During Phase 1 the focus of the activities was on a baselining process, using pre-appraisals in order to get a baseline for making a better cost and effort estimate for the improvement effort. Pilot pre-appraisals were conducted from different perspectives so different approaches for process implementation could be evaluated. Phase 1 also concentrated on establishing an improvement infrastructure and training of the improvement teams. At the time of this paper, three pilot appraisals have been completed. Our initial appraisal was performed in a flight software area, considering the flight software organization as the organization. The second appraisal was done from a project perspective, focusing on systems engineering and acquisition, and using the organization as GSFC. The final appraisal was in a ground support software area, again using GSFC as the organization. This paper will present our initial approach, lessons learned from all three pilots and the changes in our approach based on the lessons learned.

Godfrey, Sara↗

Improving the Agency's Software Acquisition Capability

External development of software has oftc n led to unsatisfactory results and great frustration for the assurE 7ce community. Contracts frequently omit critical assuranc 4 processes or the right to oversee software development activitie: At a time when NASA depends more and more on software to in plement critical system functions, combination of three factors ex; cerbate this problem: I ) the ever-increasing trend to acquire rather than develop software in-house, 2) the trend toward performance based contracts, and 3) acquisition vehicles that only state softwar 2 requirements while leaving development standards and assur! ince methodologies up to the contractor. We propose to identify specific methods at d tools that NASA projects can use to mitigate the adverse el ects of the three problems. TWO broad classes of methoddt ~ols will be explored. The first will be those that provide NASA p ojects with insight and oversight into contractors' activities. The st cond will be those that help projects objectively assess, and thus i nprwe, their software acquisition capability. Of particular interest is the Software Engineering Institute's (SEI) Software Acqt isition Capability Maturity Model (SA-CMMO).

Hankinson, Allen↗

Prototype Tool Support for SEI Process and Risk Knowledge

We have developed a prototype of tool support for risk assessment that uses selected components of the Software Engineering Institute (SEI) information, specifically: Capability Maturity Model (CMM) process activities, CMM process goals and the SEI taxonomy of software project risks.

risk management risk assessment SEI CMM software r↗

Seven Processes that Enable NASA Software Engineering Technologies

This slide presentation reviews seven processes that NASA uses to ensure that software is developed, acquired and maintained as specified in the NPR 7150.2A requirement. The requirement is to ensure that all software be appraised for the Capability Maturity Model Integration (CMMI). The enumerated processes are: (7) Product Integration, (6) Configuration Management, (5) Verification, (4) Software Assurance, (3) Measurement and Analysis, (2) Requirements Management and (1) Planning & Monitoring. Each of these is described and the group(s) that are responsible is described.

Housch, Helen↗