Search NASA⌕ Search

SEARCH · Search NASA

Results for “System Administration”

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 379 records · Page 21

Launch Control System / Spaceport Command and Control System

National Aeronautics and Space Administration (NASA) is currently developing the next generation launch vehicle that will take American astronauts, from American soil, even further into space. Our project for this semester dealt with the Spaceport Command and Control System (SCCS). SCCS provides a means of communication between the Firing Rooms and ground support equipment for the vehicle on the launch pad. For this internship, we became part of the Computer Systems Hardware Team. This team of engineers handle the computer and networking aspects of SCCS. During this internship, we learned about Linux operating systems and network configuration.

Ferrell, Sean P.↗

A Review of Tribomaterial Technology for Space Nuclear Power Systems

The National Aeronautics and Space Administration (NASA) has recently proposed a nuclear closed-cycle electric power conversion system for generation of 100-kW of electrical power for space exploration missions. A critical issue is the tribological performance of sliding components within the power conversion unit that will be exposed to neutron radiation. This paper presents a review of the main considerations that have been made in the selection of solid lubricants for similar applications in the past as well as a recommendations for continuing development of the technology.

Stanford, Malcolm K.↗

Fermented Cerasus humilis fruits protect against high‐fat diet induced hyperlipidemia which is associated with alteration of gut microbiota

Abstract BACKGROUND Hyperlipidemia is regarded as a public health matter, and its effective prevention and treatment are urgently required. However, the treatment of hyperlipidemia is still relatively scarce. RESULTS Fermented Cerasus humilis fruit (FCHF) had higher total flavonoid, total phenolic, procyanidin, and organic and free amino acid content, and lower total sugar content, than non‐fermented C. humilis fruit (NFCHF). Both FCHF and NFCHF treatment significantly prevent putting on weight. Furthermore, FCHF administration ameliorated hyperlipidemia and cholesterol over‐accumulation. In addition, FCHF administration activated the antioxidase system and decreased the malondialdehyde content to relieve oxidative stress, and showed more efficaciously than NFCHF administration. FCHF treatments significantly reverse the fat deposition in high‐fat diet rat liver. FCHF supplementation can relieve the dysbacteriosis induced by hyperlipidemia, and regulate the composition of rat gut microbiota by increasing the abundance of Prevotella and norank_f_Muribaculaceae . CONCLUSION Lactobacillus plantarum and Saccharomyces cerevisiae fermentation enhanced the antihyperlipidemic property of C. humilis fruits by promoting gut microbiota regulation. © 2022 Society of Chemical Industry.

Wang, Yu↗

Data Management as a Cluster Middleware Centerpiece

Through earth and space modeling and the ongoing launches of satellites to gather data, NASA has become one of the largest producers of data in the world. These large data sets necessitated the creation of a Data Management System (DMS) to assist both the users and the administrators of the data. Halcyon Systems Inc. was contracted by the NASA Center for Computational Sciences (NCCS) to produce a Data Management System. The prototype of the DMS was produced by Halcyon Systems Inc. (Halcyon) for the Global Modeling and Assimilation Office (GMAO). The system, which was implemented and deployed within a relatively short period of time, has proven to be highly reliable and deployable. Following the prototype deployment, Halcyon was contacted by the NCCS to produce a production DMS version for their user community. The system is composed of several existing open source or government-sponsored components such as the San Diego Supercomputer Center s (SDSC) Storage Resource Broker (SRB), the Distributed Oceanographic Data System (DODS), and other components. Since Data Management is one of the foremost problems in cluster computing, the final package not only extends its capabilities as a Data Management System, but also to a cluster management system. This Cluster/Data Management System (CDMS) can be envisioned as the integration of existing packages.

Zero, Jose↗

Flight Tests of the Turbulence Prediction and Warning System (TPAWS)

Flight tests of the National Aeronautics and Space Administration's Turbulence Prediction And Warning System (TPAWS) were conducted in the Fall of 2000 and Spring of 2002. TPAWS is a radar-based airborne turbulence detection system. During twelve flights, NASA's B-757 tallied 53 encounters with convectively induced turbulence. Analysis of data collected during 49 encounters in the Spring of 2002 showed that the TPAWS Airborne Turbulence Detection System (ATDS) successfully detected 80% of the events at least 30 seconds prior to the encounter, achieving FAA recommended performance criteria. Details of the flights, the prevailing weather conditions, and each of the turbulence events are presented in this report. Sensor and environmental characterizations are also provided.

Hamilton, David W.↗

NASA's Space Launch System: One Vehicle, Many Destinations

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 exploration beyond Earth orbit. Developed with the goals of safety, affordability, and sustainability in mind, the SLS rocket will start its missions in 2017 with 10 percent more thrust than the Saturn V rocket that launched astronauts to the Moon 40 years ago. From there it 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. The International Space Exploration Coordination Group, representing 12 of the world's space agencies, has created the Global Exploration Roadmap, which outlines paths toward a human landing on Mars, beginning with capability-demonstrating missions to the Moon or an asteroid. The Roadmap and corresponding NASA research outline the requirements for reference missions for all three destinations. This paper will explore the capability of SLS to meet those requirements and enable those missions. It will explain how the SLS Program is executing this development within flat budgetary guidelines by using existing engines assets and developing advanced technology based on heritage systems, from the initial 70 metric ton (t) lift capability through a block upgrade approach to an evolved 130-t capability. It will also detail the significant progress that has already been made toward its first launch in 2017. The SLS will offer a robust way to transport international crews and the air, water, food, and equipment they will need for extended trips to explore new frontiers. In addition, this paper will summarize the SLS rocket's capability to support science and robotic precursor missions to other worlds, or uniquely high-mass space facilities in Earth orbit. As this paper will explain, the SLS is making measurable progress toward becoming a global infrastructure asset for robotic and human scouts of all nations by providing the robust launch capability to deliver sustainable solutions for space exploration.

May, Todd A.↗

NASA's Space Launch System Development Status

Development of the National Aeronautics and Space Administration's (NASA's) Space Launch System (SLS) heavy lift rocket is shifting from the formulation phase into the implementation phase in 2014, a little more than 3 years after formal program establishment. Current development is focused on delivering a vehicle capable of launching 70 metric tons (t) into low Earth orbit. This "Block 1" configuration will launch the Orion Multi-Purpose Crew Vehicle (MPCV) on its first autonomous flight beyond the Moon and back in December 2017, followed by its first crewed flight in 2021. SLS can evolve to a130t lift capability and serve as a baseline for numerous robotic and human missions ranging from a Mars sample return to delivering the first astronauts to explore another planet. Benefits associated with its unprecedented mass and volume include reduced trip times and simplified payload design. Every SLS element achieved significant, tangible progress over the past year. Among the Program's many accomplishments are: manufacture of core stage test barrels and domes; testing of Solid Rocket Booster development hardware including thrust vector controls and avionics; planning for RS- 25 core stage engine testing; and more than 4,000 wind tunnel runs to refine vehicle configuration, trajectory, and guidance. The Program shipped its first flight hardware - the Multi-Purpose Crew Vehicle Stage Adapter (MSA) - to the United Launch Alliance for integration with the Delta IV heavy rocket that will launch an Orion test article in 2014 from NASA's Kennedy Space Center. The Program successfully completed Preliminary Design Review in 2013 and will complete Key Decision Point C in 2014. NASA has authorized the Program to move forward to Critical Design Review, scheduled for 2015 and a December 2017 first launch. The Program's success to date is due to prudent use of proven technology, infrastructure, and workforce from the Saturn and Space Shuttle programs, a streamlined management approach, and judicious use of new technologies. The result is a safe, affordable, sustainable, and evolutionary path to development of an unprecedented capability for future missions across the solar system. In an environment of economic challenges, the nationwide SLS team continues to meet ambitious budget and schedule targets. This paper will discuss SLS Program and technical accomplishments over the past year and provide a look at the milestones and challenges ahead.

Lyles, Garry↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASAs Space Launch System

The engineering development of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS) requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The nominal and off-nominal characteristics of SLS's elements and subsystems must be understood and matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex systems engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model-based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model-based algorithms and their development lifecycle from inception through FSW certification are an important focus of SLS's development effort to further ensure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. To test and validate these M&FM algorithms a dedicated test-bed was developed for full Vehicle Management End-to-End Testing (VMET). For addressing fault management (FM) early in the development lifecycle for the SLS program, NASA formed the M&FM team as part of the Integrated Systems Health Management and Automation Branch under the Spacecraft Vehicle Systems Department at the Marshall Space Flight Center (MSFC). To support the development of the FM algorithms, the VMET developed by the M&FM team provides the ability to integrate the algorithms, perform test cases, and integrate vendor-supplied physics-based launch vehicle (LV) subsystem models. Additionally, the team has developed processes for implementing and validating the M&FM algorithms for concept validation and risk reduction. The flexibility of the VMET capabilities enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS, GNC, and others. One of the principal functions of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software test and validation processes. In any software development process there is inherent risk in the interpretation and implementation of concepts from requirements and test cases into flight software compounded with potential human errors throughout the development and regression testing lifecycle. Risk reduction is addressed by the M&FM group but in particular by the Analysis Team working with other organizations such as S&MA, Structures and Environments, GNC, Orion, Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission (LOM) and Loss of Crew (LOC) probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses to be tested in VMET to ensure reliable failure detection, and confirm responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - the ARINC 6535-partitioned Operating System, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by FSW. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure their effectiveness and performance in the exterior FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗

Comparison of early reactions of the blood system in rats to immobilization, the action of hypoxia and the administration of erythopoietin

Three series of experiments were simultaneously carried on rats with the purpose of studying the action of different stimulants on the blood system; rats were subjected to immobilization, hypoxic hypoxia and erythropoietin administration. Changes in various cellular forms in the bone marrow, the thymus and the spleen were studied. A unitypical reaction, as in stress, was noted during the first hours; a reduction of the cell count in the lymphoid organs, a reduction of granulocytes and an increase of lymphoid cells in the bone marrow. The differences were chiefly quantitative. This was followed by stimulation of myelo and erythropoiesis determined by the specific features of the action applied. Nonspecific blood reaction was apparently due to activation of the adaptation mechanisms.

Gorizontov, P. D.↗

Preliminary Thermal-Hydraulic Analysis of the UTA–2 Subcritical Linear Accelerator–Driven System

The National Nuclear Security Administration’s mission includes establishing a reliable supply of 99 Mo without highly enriched uranium. Oak Ridge National Laboratory (ORNL) supports this objective through collaborative research and development with industrial partners. Niowave Inc., a current partner, is currently designing a subcritical linear accelerator-driven system (ADS) and preparing for the US Nuclear Regulatory Commission’s licensing process. Niowave’s system has the potential to efficiently supply medical radioisotopes. The technology includes a superconducting electron accelerator and a pile of both natural and low-enriched uranium (LEU) targets. The process fissions uranium and many valuable isotopes can then be extracted from the targets. Niowave is currently iterating through conceptual and detailed design processes for several system sizes. This report discusses UTA–2, which is at the demonstration stage. UTA–2 will validate numerical modeling results with experimental measurements before progressing to the detailed design of UTA–3, the commercial-sized ADS. The thermal-hydraulic behavior of the UTA–2 core design was numerically investigated using STAR-CCM+, as described in this report. STAR-CCM+, a state-of-the-art computational fluid dynamics (CFD) software that was commercially developed by Siemens, has an extensive user base and a set of validation studies. It is also compliant with the American Society of Mechanical Engineers’ Nuclear Quality Assurance 1 standard. Three cases are investigated in this report. Case 1 quantified the temperature field within the UTA–2 assembly and water tank using only conduction as the method of thermal energy transport. This simplified approach was overly conservative and yielded wetted cladding temperatures above the coolant saturation temperature. In this case, the maximum temperature of the wetted cladding surface of the highest power rod exceeded the saturation temperature of water by 63.8°C. Because of the overly conservative approach taken in Case 1 and its negative subcooled margin, buoyancy-driven natural circulation flow physics were implemented in Case 2. Adding coolant motion significantly distributed the thermal energy of the system through convective heat transfer. This relatively small amount of convective heat transfer significantly reduced system temperatures and increased the subcooled margin from –63.8 to 61.3°C. This margin confirmed that no boiling was expected during normal operation of UTA–2 at 230 W. Case 3 had no additional physics models but considered an overpower event during which the power of each LEU and natural uranium rod was at its respective peak values. This resulted in a study with the total assembly power equal to 176% of the nominal power of 230 W considered in Cases 1 and 2. The resulting natural circulation flows were slightly enhanced. The subcooled margin decreased slightly to 46.3°C, which is still a significant margin to local boiling of the water within the tank. This margin confirmed that no boiling was expected during an abnormal operation of UTA–2 at 406 W.

07 ISOTOPE AND RADIATION SOURCES↗

NASA's Space Launch System and Deep Space Opportunities for Smallsats

Designed to provide the significant capability required for human deep-space exploration, the National Aeronautics and Space Administration's Space Launch System (SLS) also provides an exceptional opportunity for lower-cost deep-space science in the form of small-satellite (smallsat) secondary payloads. This opportunity will be leveraged beginning with the rocket's first flight; a launch of the SLS's Block 1 configuration, capable of delivering greater than 26 metric tons (t) to Trans-Lunar Injection (TLI), which will see the Orion crew vehicle travel around the Moon and return to Earth. On that flight, SLS will also deploy 13 6U-class CubeSat secondary payloads to multiple destinations including deep space. Preparations are already under way for future vehicle configurations, with the more capable Block 1B, able to deliver 40 metric tons to TLI. That configuration will have the capability to carry large payloads co-manifested with the Orion spacecraft, or to utilize an 8.4-meter (m) fairing to carry payloads several times larger than are currently possible. SLS will evolve to its full Block 2 configuration, with a TLI capability of greater than 45 metric tons. This paper will provide a status of the SLS development and outline the progress being made toward flying smallsats on SLS, and discuss future opportunities for smallsats.

Bookout, Paul S.↗

Tailoring NIST Security Controls for the Ground System: Selection and Implementation -- Recommendations for Information System Owners

The National Aeronautics and Space Administration (NASA) invests millions of dollars in spacecraft and ground system development, and in mission operations in the pursuit of scientific knowledge of the universe. In recent years, NASA sent a probe to Mars to study the Red Planet's upper atmosphere, obtained high resolution images of Pluto, and it is currently preparing to find new exoplanets, rendezvous with an asteroid, and bring a sample of the asteroid back to Earth for analysis. The success of these missions is enabled by mission assurance. In turn, mission assurance is backed by information assurance. The information systems supporting NASA missions must be reliable as well as secure. NASA - like every other U.S. Federal Government agency - is required to manage the security of its information systems according to federal mandates, the most prominent being the Federal Information Security Management Act (FISMA) of 2002 and the legislative updates that followed it. Like the management of enterprise information technology (IT), federal information security management takes a "one-size fits all" approach for protecting IT systems. While this approach works for most organizations, it does not effectively translate into security of highly specialized systems such as those supporting NASA missions. These systems include command and control (C&C) systems, spacecraft and instrument simulators, and other elements comprising the ground segment. They must be carefully configured, monitored and maintained, sometimes for several years past the missions' initially planned life expectancy, to ensure the ground system is protected and remains operational without any compromise of its confidentiality, integrity and availability. Enterprise policies, processes, procedures and products, if not effectively tailored to meet mission requirements, may not offer the needed security for protecting the information system, and they may even become disruptive to mission operations. Certain protective measures for the general enterprise may not be as efficient within the ground segment. This is what the authors have concluded through observations and analysis of patterns identified from the various security assessments performed on NASA missions such as MAVEN, OSIRIS-REx, New Horizons and TESS, to name a few. The security audits confirmed that the framework for managing information system security developed by the National Institute of Standards and Technology (NIST) for the federal government, and adopted by NASA, is indeed effective. However, the selection of the technical, operational and management security controls offered by the NIST model - and how they are implemented - does not always fit the nature and the environment where the ground system operates in even though there is no apparent impact on mission success. The authors observed that unfit controls, that is, controls that are not necessarily applicable or sufficiently effective in protecting the mission systems, are often selected to facilitate compliance with security requirements and organizational expectations even if the selected controls offer minimum or non-existent protection. This paper identifies some of the standard security controls that can in fact protect the ground system, and which of them offer little or no benefit at all. It offers multiple scenarios from real security audits in which the controls are not effective without, of course, disclosing any sensitive information about the missions assessed. In addition to selection and implementation of controls, the paper also discusses potential impact of recent legislation such as the Federal Information Security Modernization Act (FISMA) of 2014 - aimed at the enterprise - on the ground system, and offers other recommendations to Information System Owners (ISOs).

GOVERNANCE↗

Application of Objectives-Driven Assurance Cases to System Development in an Evolving Acquisition Model

System properties such as “safety” and “dependability” cannot, in practice, be proven, and must be argued in an “assurance case” aimed at supporting risk-acceptance decisions that have to be made by system acquirers and/or regulatory authorities. The paper is concerned with applications of the “assurance case” idea early in design and development of new systems, when (apart from dedicated testing) the only available operating experience information derives from previous (non-identical) systems. Much of the discussion is based on an evolving acquisition model at the US National Aeronautics and Space Administration; previously, most major systems were developed in-house, but some major systems will now be developed by and acquired from commercial providers. Key points discussed include the following. (1) By promoting a particular kind of focused discussion between acquirers and providers, the use of assurance cases should be particularly valuable under the new acquisition model. (2) In principle, objectives-driven (sometimes called “performance-based”) approaches to assurance of performance have significant advantages in cases where they are applicable. (3) For truly novel systems, completeness of the safety analysis is a significant issue; it is important for the assurance case to include a commitment by the provider (or applicant) to seriously pursue analysis of operating experience, so that previously unrecognized hazards can be identified and addressed. (4) Inquiries into major accidents often point to deficiencies in management oversight in all parts of the life cycle; management processes need to be addressed in the formulation and the implementation of an assurance case. Under the new acquisition model, these considerations imply a serious reconsideration of the way in which the development process is managed by both providers and acquirers.

Objectives-driven↗

APPLICATION OF OBJECTIVES-DRIVEN ASSURANCE CASES TO SYSTEM DEVELOPMENT IN AN EVOLVING ACQUISITION MODEL

System properties such as “safety” and “dependability” cannot, in practice, be proven, and must be argued in an “assurance case” aimed at supporting risk-acceptance decisions that have to be made by system acquirers and/or regulatory authorities. The paper is concerned with applications of the “assurance case” idea early in design and development of new systems, when (apart from dedicated testing) the only available operating experience information derives from previous (non-identical) systems. Much of the discussion is based on an evolving acquisition model at the US National Aeronautics and Space Administration; previously, most major systems were developed in-house, but some major systems will now be developed by and acquired from commercial providers. Key points discussed include the following. (1) By promoting a particular kind of focused discussion between acquirers and providers, the use of assurance cases should be particularly valuable under the new acquisition model. (2) In principle, objectives-driven (sometimes called “performance-based”) approaches to assurance of performance have significant advantages in cases where they are applicable. (3) For truly novel systems, completeness of the safety analysis is a significant issue; it is important for the assurance case to include a commitment by the provider (or applicant) to seriously pursue analysis of operating experience, so that previously unrecognized hazards can be identified and addressed. (4) Inquiries into major accidents often point to deficiencies in management oversight in all parts of the life cycle; management processes need to be addressed in the formulation and the implementation of an assurance case. Under the new acquisition model, these considerations imply a serious reconsideration of the way in which the development process is managed by both providers and acquirers.

99 GENERAL AND MISCELLANEOUS↗

Application of Objectives-Driven Assurance Cases to System Development in an Evolving Acquisition Model

System properties such as “safety” and “dependability” cannot, in practice, be proven, and must be argued in an “assurance case” aimed at supporting risk-acceptance decisions that have to be made by system acquirers and/or regulatory authorities. The paper is concerned with applications of the “assurance case” idea early in design and development of new systems, when (apart from dedicated testing) the only available operating experience information derives from previous (non-identical) systems. Much of the discussion is based on an evolving acquisition model at the US National Aeronautics and Space Administration; previously, most major systems were developed in-house, but some major systems will now be developed by and acquired from commercial providers. Key points discussed include the following. (1) By promoting a particular kind of focused discussion between acquirers and providers, the use of assurance cases should be particularly valuable under the new acquisition model. (2) In principle, objectives-driven (sometimes called “performance-based”) approaches to assurance of performance have significant advantages in cases where they are applicable. (3) For truly novel systems, completeness of the safety analysis is a significant issue; it is important for the assurance case to include a commitment by the provider (or applicant) to seriously pursue analysis of operating experience, so that previously unrecognized hazards can be identified and addressed. (4) Inquiries into major accidents often point to deficiencies in management oversight in all parts of the life cycle; management processes need to be addressed in the formulation and the implementation of an assurance case. Under the new acquisition model, these considerations imply a serious reconsideration of the way in which the development process is managed by both providers and acquirers.

99 GENERAL AND MISCELLANEOUS↗

Development of a Portfolio Management Approach with Case Study of the NASA Airspace Systems Program

A portfolio management approach was developed for the National Aeronautics and Space Administration s (NASA s) Airspace Systems Program (ASP). The purpose was to help inform ASP leadership regarding future investment decisions related to its existing portfolio of advanced technology concepts and capabilities (C/Cs) currently under development and to potentially identify new opportunities. The portfolio management approach is general in form and is extensible to other advanced technology development programs. It focuses on individual C/Cs and consists of three parts: 1) concept of operations (con-ops) development, 2) safety impact assessment, and 3) benefit-cost-risk (B-C-R) assessment. The first two parts are recommendations to ASP leaders and will be discussed only briefly, while the B-C-R part relates to the development of an assessment capability and will be discussed in greater detail. The B-C-R assessment capability enables estimation of the relative value of each C/C as compared with all other C/Cs in the ASP portfolio. Value is expressed in terms of a composite weighted utility function (WUF) rating, based on estimated benefits, costs, and risks. Benefit utility is estimated relative to achieving key NAS performance objectives, which are outlined in the ASP Strategic Plan.1 Risk utility focuses on C/C development and implementation risk, while cost utility focuses on the development and implementation portions of overall C/C life-cycle costs. Initial composite ratings of the ASP C/Cs were successfully generated; however, the limited availability of B-C-R information, which is used as inputs to the WUF model, reduced the meaningfulness of these initial investment ratings. Development of this approach, however, defined specific information-generation requirements for ASP C/C developers that will increase the meaningfulness of future B-C-R ratings.

Neitzke, Kurt W.↗