Propulsion Technology Lifecycle Operational Analysis

The paper presents the results of a focused effort performed by the members of the Space Propulsion Synergy Team (SPST) Functional Requirements Sub-team to develop propulsion data to support Advanced Technology Lifecycle Analysis System (ATLAS). This is a spreadsheet application to analyze the impact of technology decisions at a system-of-systems level. Results are summarized in an Excel workbook we call the Technology Tool Box (TTB). The TTB provides data for technology performance, operations, and programmatic parameters in the form of a library of technical information to support analysis tools and/or models. The lifecycle of technologies can be analyzed from this data and particularly useful for system operations involving long running missions. The propulsion technologies in this paper are listed against Chemical Rocket Engines in a Work Breakdown Structure (WBS) format. The overall effort involved establishing four elements: (1) A general purpose Functional System Breakdown Structure (FSBS). (2) Operational Requirements for Rocket Engines. (3) Technology Metric Values associated with Operating Systems (4) Work Breakdown Structure (WBS) of Chemical Rocket Engines The list of Chemical Rocket Engines identified in the WBS is by no means complete. It is planned to update the TTB with a more complete list of available Chemical Rocket Engines for United States (US) engines and add the Foreign rocket engines to the WBS which are available to NASA and the Aerospace Industry. The Operational Technology Metric Values were derived by the SPST Sub-team in the form of the TTB and establishes a database for users to help evaluate and establish the technology level of each Chemical Rocket Engine in the database. The Technology Metric Values will serve as a guide to help determine which rocket engine to invest technology money in for future development

Launch Vehicle Propulsion Life Cycle Cost Lessons Learned

This paper will review lessons learned for space transportation systems from the viewpoint of the NASA, Industry and academia Space Propulsion Synergy Team (SPST). The paper provides the basic idea and history of "lessons learned". Recommendations that are extremely relevant to NASA's future investments in research, program development and operations are"'provided. Lastly, a novel and useful approach to documenting lessons learned is recommended, so as to most effectively guide future NASA investments. Applying lessons learned can significantly improve access to space for cargo or people by focusing limited funds on the right areas and needs for improvement. Many NASA human space flight initiatives have faltered, been re-directed or been outright canceled since the birth of the Space Shuttle program. The reasons given at the time have been seemingly unique. It will be shown that there are common threads as lessons learned in many a past initiative

Space Transportation System Availability Requirement and Its Influencing Attributes Relationships

It is important that engineering and management accept the need for an availability requirement that is derived with its influencing attributes. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability. Also important to provide bounds of the variables providing engineering the insight required to control the system's engineering solution, e.g., these influencing attributes become design requirements also. These variables will drive the need to provide integration of similar discipline functions or technology selection to allow control of the total parts count. The relationship of selecting a reliability requirement will place a constraint on parts count to achieve a given availability requirement or if allowed to increase the parts count will drive the system reliability requirement higher. They also provide the understanding for the relationship of mean repair time (or mean down time) to maintainability, e.g., accessibility for repair, and both the mean time between failure, e.g., reliability of hardware and availability. The concerns and importance of achieving a strong availability requirement is driven by the need for affordability, the choice of using the two launch solution for the single space application, or the need to control the spare parts count needed to support the long stay in either orbit or on the surface of the moon. Understanding the requirements before starting the architectural design concept will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system

Space Transportation System Availability Requirements and Its Influencing Attributes Relationships

It is important that engineering and management accept the need for an availability requirement that is derived with its influencing attributes. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability. Also important to provide bounds of the variables providing engineering the insight required to control the system's engineering solution, e.g., these influencing attributes become design requirements also. These variables will drive the need to provide integration of similar discipline functions or technology selection to allow control of the total parts count. The relationship of selecting a reliability requirement will place a constraint on parts count to achieve a given availability requirement or if allowed to increase the parts count will drive the system reliability requirement higher. They also provide the understanding for the relationship of mean repair time (or mean down time) to maintainability, e.g., accessibility for repair, and both the mean time between failure, e.g., reliability of hardware and availability. The concerns and importance of achieving a strong availability requirement is driven by the need for affordability, the choice of using the two launch solution for the single space application, or the need to control the spare parts count needed to support the long stay in either orbit or on the surface of the moon. Understanding the requirements before starting the architectural design concept will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system

The Functional Breakdown Structure (FBS) and Its Relationship to Life Cycle Cost

The Functional Breakdown Structure (FBS) is a structured, modular breakdown of every function that must be addressed to perform a generic mission. It is also usable for any subset of the mission. Unlike a Work Breakdown Structure (WBS), the FBS is a function-oriented tree, not a product-oriented tree. The FBS details not products, but operations or activities that should be performed. The FBS is not tied to any particular architectural implementation because it is a listing of the needed functions, not the elements, of the architecture. The FBS for Space Transportation Systems provides a universal hierarchy of required functions, which include ground and space operations as well as infrastructure - it provides total visibility of the entire mission. By approaching the systems engineering problem from the functional view, instead of the element or hardware view, the SPST has created an exhaustive list of potential requirements which the architecture designers can use to evaluate the completeness of their designs. This is a new approach that will provide full accountability of all functions required to perform the planned mission. It serves as a giant check list to be sure that no functions are omitted, especially in the early architectural design phase. A significant characteristic of a FBS is that if architecture options are compared using this approach, then any missing or redundant elements of each option will be ' identified. Consequently, valid Life Cycle Costs (LCC) comparisons can be made. For example, one architecture option might not need a particular function while another option does. One option may have individual elements to perform each of three functions while another option needs only one element to perform the three functions. Once an architecture has been selected, the FBS will serve as a guide in development of the work breakdown structure, provide visibility of those technologies that need to be further developed to perform required functions, and help identify the personnel skills required to develop and operate the architecture. It also wifi allow the systems engineering activities to totally integrate each discipline to the maximum extent possible and optimize at the total system level, thus avoiding optimizing at the element level (stove-piping). In addition, it furnishes a framework that wifi help prevent over or under specifying requirements because all functions are identified and all elements are aligned to functions

Commercial Space with Technology Maturation

To provide affordable space transportation we must be capable of using common fixed assets and the infrastructure for multiple purposes simultaneously. The Space Shuttle was operated for thirty years, but was not able to establish an effective continuous improvement program because of the high risk to the crew on every mission. An unmanned capability is needed to provide an acceptable risk to the primary mission. This paper is intended to present a case where a commercial space venture could share the large fixed cost of operating the infrastructure with the government while the government provides new advanced technology that is focused on reduced operating cost to the common launch transportation system. A conceivable commercial space venture could provide educational entertainment for the country's youth that would stimulate their interest in the science, technology, engineering, and mathematics (STEM) through access at entertainment parks or the existing Space Visitor Centers. The paper uses this example to demonstrate how growing public-private space market demand will re-orient space transportation industry priorities in flight and ground system design and technology development, and how the infrastructure is used and shared

Shuttle Shortfalls and Lessons Learned for the Sustainment of Human Space Exploration

Much debate and national soul searching has taken place over the value of the Space Shuttle which first flew in 1981 and which is currently scheduled to be retired in 2010. Originally developed post-Saturn Apollo to emphasize affordability and safety, the reusable Space Shuttle instead came to be perceived as economically unsustainable and lacking the technology maturity to assure safe, routine access to low earth orbit (LEO). After the loss of two crews, aboard Challenger and Columbia, followed by the decision to retire the system in 2010, it is critical that this three decades worth of human space flight experience be well understood. Understanding of the past is imperative to further those goals for which the Space Shuttle was a stepping-stone in the advancement of knowledge. There was significant reduction in life cycle costs between the Saturn Apollo and the Space Shuttle. However, the advancement in life cycle cost reduction from Saturn Apollo to the Space Shuttle fell far short of its goal. This paper will explore the reasons for this shortfall. Shortfalls and lessons learned can be categorized as related to design factors, at the architecture, element and sub-system levels, as well as to programmatic factors, in terms of goals, requirements, management and organization. Additionally, no review of the Space Shuttle program and attempt to take away key lessons would be complete without a strategic review. That is, how do national space goals drive future space transportation development strategies? The lessons of the Space Shuttle are invaluable in all respects - technical, as in design, program-wise, as in organizational approach and goal setting, and strategically, within the context of the generational march toward an expanded human presence in space. Beyond lessons though (and the innumerable papers, anecdotes and opinions published on this topic) this paper traces tangible, achievable steps, derived from the Space Shuttle program experience, that must be a part of any 2l century initiatives furthering a growing human presence beyond earth

Propulsion System Choices and Their Implications

In defining a space vehicle architecture, the propulsion system and related subsystem choices will have a major influence on achieving the goals and objectives desired. There are many alternatives and the choices made must produce a system that meets the performance requirements, but at the same time also provide the greatest opportunity of reaching all of the required objectives. Recognizing the above, the SPST Functional Requirements subteam has drawn on the knowledge, expertise, and experience of its members, to develop insight that wiIJ effectively aid the architectural concept developer in making the appropriate choices consistent with the architecture goals. This data not only identifies many selected choices, but also, more importantly, presents the collective assessment of this subteam on the "pros" and the "cons" of these choices. The propulsion system choices with their pros and cons are presented in five major groups. A. System Integration Approach. Focused on the requirement for safety, reliability, dependability, maintainability, and low cost. B. Non-Chemical Propulsion. Focused on choice of propulsion type. C. Chemical Propulsion. Focused on propellant choice implications. D. Functional Integration. Focused on the degree of integration of the many propulsive and closely associated functions, and on the choice of the engine combustion power cycle. E. Thermal Management. Focused on propellant tank insulation and integration. Each of these groups is further broken down into subgroups, and at that level the consensus pros and cons are presented. The intended use of this paper is to provide a resource of focused material for architectural concept developers to use in designing new advanced systems including college design classes. It is also a possible source of input material for developing a model for designing and analyzing advanced concepts to help identify focused technology needs and their priorities

Discourses of student orientation to medical education programs

Background: Although medical students’ initial orientation is an important point of transition in medical education, there is a paucity of literature on the subject and major variations in the ways that different institutions orient incoming medical students to their programs. Methods: We conducted a discourse analysis of medical education orientation in the literature and on data from a survey of peer institutions’ approaches to orientation. Results: These two discourses of orientation had clear similarities, in particular, the critical role of ceremony and symbols, and the focus on developing professionalism and physician identities. There were also differences between them, in particular, in the way that the discourse in the literature focused on the symbolic and professional aspects of orientation; something we have called ‘cultural orientation’. Meanwhile, those who were responsible for orientation in their own institutions tended to focus on the practical and social dimensions. Conclusion: By examining how orientation has been described and discussed, we identify three domains of orientation: cultural, social, and practical. These domains are relatively distinct in terms of the activities associated with them, and in terms of who is involved in organizing and running these activities. We also describe orientation as a liminal activity system on the threshold of medical school where incoming students initially cross into the profession. Interestingly, this state of ambiguity also extends to the scholarship of orientation with only some of its aspects attracting formal enquiry, even though there is a growing interest in transitions in medical education as a whole. We hope, therefore, that this study can help to legitimize enquiry into orientation in all its forms and that it can begin to situate the role of orientation more firmly within the firmament of medical education practice and research

Bridging Alone: Religious Conservatism, Marital Homogamy, and Voluntary Association Membership

This study characterizes social insularity of religiously conservative American married couples by examining patterns of voluntary associationmembership. Constructing a dataset of 3938 marital dyads from the second wave of the National Survey of Families and Households, the author investigates whether conservative religious homogamy encourages membership in religious voluntary groups and discourages membership in secular voluntary groups. Results indicate that couples’ shared affiliation with conservative denominations, paired with beliefs in biblical authority and inerrancy, increases the likelihood of religious group membership for husbands and wives and reduces the likelihood of secular group membership for wives, but not for husbands. The social insularity of conservative religious groups appears to be reinforced by homogamy—particularly by wives who share faith with husbands