HSI in the Program Life Cycle
Human Systems Integration (HSI) in the Systems Engineering Life Cycle and the six capability model for the integration of human concerns is presented.
Fitts, David J.↗
SEARCH · Search NASA
Results for “life cycle”
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.
Life Cycle Cost Analysis of Shuttle-Derived Launch Vehicles, Volume 1
The design, performance, and programmatic definition of shuttle derived launch vehicles (SDLV) established by two different contractors were assessed and the relative life cycle costs of space transportation systems using the shuttle alone were compared with costs for a mix of shuttles and SDLV's. The ground rules and assumptions used in the evaluation are summarized and the work breakdown structure is included. Approaches used in deriving SDLV costs, including calibration factors and historical data are described. Both SDLV cost estimates and SDLV/STS cost comparisons are summarized. Standard formats are used to report comprehensive SDLV life cycle estimates. Hardware cost estimates (below subsystem level) obtained using the RCA PRICE 84 cost model are included along with other supporting data.
Source record↗
Using Model-Based Systems Engineering To Provide Artifacts for NASA Project Life-Cycle and Technical Reviews
The ability of systems engineers to use model-based systems engineering (MBSE) to generate self-consistent, up-to-date systems engineering products for project life-cycle and technical reviews is an important aspect for the continued and accelerated acceptance of MBSE. Currently, many review products are generated using labor-intensive, error-prone approaches based on documents, spreadsheets, and chart sets; a promised benefit of MBSE is that users will experience reductions in inconsistencies and errors. This work examines features of SysML that can be used to generate systems engineering products. Model elements, relationships, tables, and diagrams are identified for a large number of the typical systems engineering artifacts. A SysML system model can contain and generate most systems engineering products to a significant extent and this paper provides a guide on how to use MBSE to generate products for project life-cycle and technical reviews. The use of MBSE can reduce the schedule impact usually experienced for review preparation, as in many cases the review products can be auto-generated directly from the system model. These approaches are useful to systems engineers, project managers, review board members, and other key project stakeholders.
SE Product↗
Addressing software security risk mitigations in the life cycle
The NASA Office of Safety and Mission Assurance (OSMA) has funded the Jet Propulsion Laboratory (JPL) with a Center Initiative, 'Reducing Software Security Risk through an Integrated Approach' (RSSR), to address this need. The Initiative is a formal approach to addressing software security in the life cycle through the instantiation of a Software Security Assessment Instrument (SSAI) for the development and maintenance life cycles.
software tools↗
Life Cycle Analysis of Dedicated Nano-Launch Technologies
Recent technology advancements have enabled the development of small cheap satellites that can perform useful functions in the space environment. Currently, the only low cost option for getting these payloads into orbit is through ride share programs - small satellites awaiting the launch of a larger satellite, and then riding along on the same launcher. As a result, these small satellite customers await primary payload launches and a backlog exists. An alternative option would be dedicated nano-launch systems built and operated to provide more flexible launch services, higher availability, and affordable prices. The potential customer base that would drive requirements or support a business case includes commercial, academia, civil government and defense. Further, NASA technology investments could enable these alternative game changing options. With this context, in 2013 the Game Changing Development (GCD) program funded a NASA team to investigate the feasibility of dedicated nano-satellite launch systems with a recurring cost of less than $2 million per launch for a 5 kg payload to low Earth orbit. The team products would include potential concepts, technologies and factors for enabling the ambitious cost goal, exploring the nature of the goal itself, and informing the GCD program technology investment decision making process. This paper provides an overview of the life cycle analysis effort that was conducted in 2013 by an inter-center NASA team. This effort included the development of reference nano-launch system concepts, developing analysis processes and models, establishing a basis for cost estimates (development, manufacturing and launch) suitable to the scale of the systems, and especially, understanding the relationship of potential game changing technologies to life cycle costs, as well as other factors, such as flights per year.
nanolaunch↗
Concepts for Life Cycle Cost Control Required to Achieve Space Transportation Affordability and Sustainability
Cost control must be implemented through the establishment of requirements and controlled continually by managing to these requirements. Cost control of the non-recurring side of life cycle cost has traditionally been implemented in both commercial and government programs. The government uses the budget process to implement this control. The commercial approach is to use a similar process of allocating the non-recurring cost to major elements of the program. This type of control generally manages through a work breakdown structure (WBS) by defining the major elements of the program. If the cost control is to be applied across the entire program life cycle cost (LCC), the approach must be addressed very differently. A functional breakdown structure (FBS) is defined and recommended. Use of a FBS provides the visibifity to allow the choice of an integrated solution reducing the cost of providing many different elements of like function. The different functional solutions that drive the hardware logistics, quantity of documentation, operational labor, reliability and maintainability balance, and total integration of the entire system from DDT&E through the life of the program must be fully defined, compared, and final decisions made among these competing solutions. The major drivers of recurring cost have been identified and are presented and discussed. The LCC requirements must be established and flowed down to provide control of LCC. This LCC control will require a structured rigid process similar to the one traditionally used to control weight/performance for space transportation systems throughout the entire program. It has been demonstrated over the last 30 years that without a firm requirement and methodically structured cost control, it is unlikely that affordable and sustainable space transportation system LCC will be achieved.
Rhodes, Russel E.↗
NASA's Robotics Mining Competition Provides Undergraduates Full Life Cycle Systems Engineering Experience
NASA has held an annual robotic mining competition for teams of university/college students since 2010. This competition is yearlong, suitable for a senior university engineering capstone project. It encompasses the full project life cycle from ideation of a robot design to actual tele-operation of the robot in simulated Mars conditions mining and collecting simulated regolith. A major required element for this competition is a Systems Engineering Paper in which each team describes the systems engineering approaches used on their project. The score for the Systems Engineering Paper contributes 25% towards the team's score for the competition's grand prize. The required use of systems engineering on the project by this competition introduces the students to an intense practical application of systems engineering throughout a full project life cycle.
Stecklein, Jonette↗
NASA's Robotic Mining Competition Provides Undergraduates Full Life Cycle Systems Engineering Experience
NASA has held an annual robotic mining competition for teams of university/college students since 2010. This competition is yearlong, suitable for a senior university engineering capstone project. It encompasses the full project life cycle from ideation of a robot design, through tele-operation of the robot collecting regolith in simulated Mars conditions, to disposal of the robot systems after the competition. A major required element for this competition is a Systems Engineering Paper in which each team describes the systems engineering approaches used on their project. The score for the Systems Engineering Paper contributes 25% towards the team’s score for the competition’s grand prize. The required use of systems engineering on the project by this competition introduces the students to an intense practical application of systems engineering throughout a full project life cycle.
Stecklein, Jonette↗
Using Model-Based Systems Engineering to Provide Artifacts for NASA Project Life-cycle and Technical Reviews
This paper is for the AIAA Space Conference. The ability of systems engineers to use model-based systems engineering (MBSE) to generate self-consistent, up-to-date systems engineering products for project life-cycle and technical reviews is an important aspect for the continued and accelerated acceptance of MBSE. Currently, many review products are generated using labor-intensive, error-prone approaches based on documents, spreadsheets, and chart sets; a promised benefit of MBSE is that users will experience reductions in inconsistencies and errors. This work examines features of SysML that can be used to generate systems engineering products. Model elements, relationships, tables, and diagrams are identified for a large number of the typical systems engineering artifacts. A SysML system model can contain and generate most systems engineering products to a significant extent and this paper provides a guide on how to use MBSE to generate products for project life-cycle and technical reviews. The use of MBSE can reduce the schedule impact usually experienced for review preparation, as in many cases the review products can be auto-generated directly from the system model. These approaches are useful to systems engineers, project managers, review board members, and other key project stakeholders.
MBSE↗
Ni-MH storage test and cycle life test
Gates Aerospace Batteries is conducting two long term test programs to fully characterize the NiMH cell technology for aerospace applications. The first program analyzes the effects of long term storage upon cell performance. The second program analyzes cycle life testing and preliminary production lot testing. This paper summarizes these approaches to testing the NiMH couple and culminates with initial storage and testing recommendations. Long term storage presents challenges to deter the adverse condition of capacity fade in NiMH cells. Elevated but stabilized pressures and elevated but stabilized end-of-charge voltages also appear to be a characteristic phenomenon of long term storage modes. However, the performance degradation is dependent upon specific characteristics of the metal-hydride alloy. To date, there is no objective evidence with which to recommend the proper method for storage and handling of NiMH cells upon shipment. This is particularly critical due to limited data points that indicate open circuit storage at room temperature for 60 to 90 days will result in irrecoverable capacity loss. Accordingly a test plan was developed to determine what method of mid-term to long-term storage will prevent irrecoverable capacity loss. The explicit assumption is that trickle charging at some rate above the self-discharge rate will prevent the irreversible chemical changes to the negative electrode that result in the irrecoverable capacity loss. Another premise is that lower storage temperatures, typically 0 C for aerospace customers, will impede any negative chemical reactions. Three different trickle charge rates are expected to yield a fairly flat response with respect to recoverable capacity versus baseline cells in two different modes of open circuit. Specific attributes monitored include: end-of-charge voltage, end-of-charge pressure, mid-point discharge voltage, capacity, and end-of-discharge pressure. Cycle life testing and preliminary production lot testing continue to dominate the overall technology development effort at GAB. The cell life test program reflects continuing improvements in baseline cell designs. Performance improvements include lower and more stable charge voltages and pressures. The continuing review of production lot testing assures conformance to the design criteria and expectations. This is especially critical during this period of transferring technology from research and development status to production.
Dell, R. Dan↗
Error Cost Escalation Through the Project Life Cycle
It is well known that the costs to fix errors increase as the project matures, but how fast do those costs build? A study was performed to determine the relative cost of fixing errors discovered during various phases of a project life cycle. This study used three approaches to determine the relative costs: the bottom-up cost method, the total cost breakdown method, and the top-down hypothetical project method. The approaches and results described in this paper presume development of a hardware/software system having project characteristics similar to those used in the development of a large, complex spacecraft, a military aircraft, or a small communications satellite. The results show the degree to which costs escalate, as errors are discovered and fixed at later and later phases in the project life cycle. If the cost of fixing a requirements error discovered during the requirements phase is defined to be 1 unit, the cost to fix that error if found during the design phase increases to 3 - 8 units; at the manufacturing/build phase, the cost to fix the error is 7 - 16 units; at the integration and test phase, the cost to fix the error becomes 21 - 78 units; and at the operations phase, the cost to fix the requirements error ranged from 29 units to more than 1500 units
Stecklein, Jonette M.↗
A model for a knowledge-based system's life cycle
The American Institute of Aeronautics and Astronautics has initiated a Committee on Standards for Artificial Intelligence. Presented here are the initial efforts of one of the working groups of that committee. The purpose here is to present a candidate model for the development life cycle of Knowledge Based Systems (KBS). The intent is for the model to be used by the Aerospace Community and eventually be evolved into a standard. The model is rooted in the evolutionary model, borrows from the spiral model, and is embedded in the standard Waterfall model for software development. Its intent is to satisfy the development of both stand-alone and embedded KBSs. The phases of the life cycle are detailed as are and the review points that constitute the key milestones throughout the development process. The applicability and strengths of the model are discussed along with areas needing further development and refinement by the aerospace community.
Kiss, Peter A.↗
A new concept for high-cycle-life LEO: Rechargeable MnO2-hydrogen
The nickel-hydrogen secondary battery system, developed in the early 1970s, has become the system of choice for geostationary earth orbit (GEO) applications. However, for low earth orbit (LEO) satellites with long expected lifetimes the nickel positive limits performance. This requires derating of the cell to achieve very long cycle life. A new system, rechargeable MnO2-Hydrogen, which does not require derating, is described here. For LEO applications, it promises to have longer cycle life, high rate capability, a higher effective energy density, and much lower self-discharge behavior than those of the nickel-hydrogen system.
Appleby, A. J.↗
Tracking Critical Thermal Metrics throughout the Life Cycle of a Large Observatory Thermal Model
Observatory thermal models for large, complex missions, such as the Wide Field InfraRed Survey Telescope (WFIRST) mission, produce an immense amount of data to be processed. Configuration management of the model throughout the project life cycle has mainly focused on which versions of the subsystem models form the current observatory level configuration. However, the results produced by the model are not nearly as well tracked and traceable. Given the various states of design maturity for each of the components in the WFIRST design, an updated component model is nearly ready to be integrated at the next higher level of assembly about every month or two. With each subsystem model delivery, the observatory model needs to remove the old component, integrate the new one, execute the model, and inspect the results. Usually, this inspection focuses primarily on the newly integrated component. Recently, a Metric Tracking Spreadsheet was developed to help provide a “big picture” view of the entire observatory highlighting key parameters critical to mission performance. This spreadsheet helps track impacts on subsystems by updates of other subsystems that were not intuitively obvious. Metrics tracked include: absorbed environmental loading (to determine effectiveness of sunshield), temperatures of critical avionics, electrical dissipations, heater power predictions, stability of critical optics, parasitic heat leaks in cryogenic region, high level heat flows between elements, and model run time. Producing this data for the same operational configuration with each model update has helped produce a trail of data to evaluate the impact of model updates. While the metrics selected are specific for WFIRST, other large, complex observatories could be well served to establish their own metrics early in the project life cycle to track to quickly assess the impact of any subsystem on other subsystems or the overall system itself.
Thermal Desktop↗
Addressing software security and mitigations in the life cycle
Traditionally, security is viewed as an organizational and Information Technology (IT) systems function comprising of firewalls, intrusion detection systems (IDS), system security settings and patches to the operating system (OS) and applications running on it. Until recently, little thought has been given to the importance of security as a formal approach in the software life cycle. The Jet Propulsion Laboratory has approached the problem through the development of an integrated formal Software Security Assessment Instrument (SSAI) with six foci for the software life cycle.
model checking↗
Addressing software security and mitigations in the life cycle
Traditionally, security is viewed as an organizational and Information Technology (IIJ systems function comprising of Firewalls, intrusion detection systems (IDS), system security settings and patches to the operating system (OS) and applications running on it. Until recently, little thought has been given to the importance of security as a formal approach in the software life cycle. The Jet Propulsion Laboratory has approached the problem through the development of an integrated formal Software Security Assessment Instrument (SSAI) with six foci for the software life cycle.
formal methods↗
Support for life-cycle product reuse in NASA's SSE
The Software Support Environment (SSE) is a software factory for the production of Space Station Freedom Program operational software. The SSE is to be centrally developed and maintained and used to configure software production facilities in the field. The PRC product TTCQF provides for an automated qualification process and analysis of existing code that can be used for software reuse. The interrogation subsystem permits user queries of the reusable data and components which have been identified by an analyzer and qualified with associated metrics. The concept includes reuse of non-code life-cycle components such as requirements and designs. Possible types of reusable life-cycle components include templates, generics, and as-is items. Qualification of reusable elements requires analysis (separation of candidate components into primitives), qualification (evaluation of primitives for reusability according to reusability criteria) and loading (placing qualified elements into appropriate libraries). There can be different qualifications for different installations, methodologies, applications and components. Identifying reusable software and related components is labor-intensive and is best carried out as an integrated function of an SSE.
Shotton, Charles↗
Life cycle tests monthly progress report, period ending 30 jun. 1965
Life cycle test data for nickel-cadmium, silver- zinc, and silver-cadmium cells
SILVER-CADMIUM BATTERY↗