REG NASA-LLIS-0762-2000 Lessons Learned - Systems Design Analysis Applied To Launch Vehicle Configurations.pdf

《REG NASA-LLIS-0762-2000 Lessons Learned - Systems Design Analysis Applied To Launch Vehicle Configurations.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-0762-2000 Lessons Learned - Systems Design Analysis Applied To Launch Vehicle Configurations.pdf（6页珍藏版）》请在麦多课文档分享上搜索。

1、Best Practices Entry: Best Practice Info:a71 Committee Approval Date: 2000-04-06a71 Center Point of Contact: MSFCa71 Submitted by: Wilson HarkinsSubject: Systems Design Analysis Applied To Launch Vehicle Configurations Practice: Use design management improvements such as matrix methods, quality tech

2、niques, and life cycle cost analyses in a systematic approach to systems analysis.Programs that Certify Usage: This practice has been used on Saturn I, IB and V, Space Shuttle Main Engine (SSME), Space Shuttle External Tank (ET), Space Shuttle Solid Rocket Booster (SRB), Hubble Space Telescope (HST)

3、, High Energy Astronomy Observatory (HEAO), Lunar Roving Vehicle (LRV), Skylab, and many others.Center to Contact for Information: MSFCImplementation Method: This Lesson Learned is based on Reliability Practice No. PD-ED-1230; from NASA Technical Memorandum 4322A, NASA Reliability Preferred Practice

4、s for Design and Test.The use of advanced design management methods in each program phase of major launch vehicle developments will maximize reliability and minimize cost overruns. Significant improvements in user satisfaction, error-free performance, and operational effectiveness can be achieved th

5、rough the use of these methods.Implementation Method:Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Introduction: As emphasis in the aerospace industry shifts from maximum performance to low life cycle cost and high reliability, the rate of major te

6、chnological design advancement is giving way to design management improvements. Common to these evolving improvements are the principles and tools of total quality management as applied to systems design analysis. This practice reviews successful systems engineering methodology as it applies to engi

7、neering design analyses for launch vehicles, and identifies total quality management applications that provide reliable, low cost aerospace designs. Since designing to high reliability can be correlated to reductions in the long-term cost of failures and spares, cost emerges as the systems common de

8、nominator.Systems management, systems design, and other systems approaches are well-established processes in the aerospace communities for developing all or any part of large, complex systems. The systems design process provides an orderly transformation of mission objectives into a detailed system

9、design through three continuous and correlated phases: concept formulation, definition, and design. Effective use of these design phases has advanced design practice from an earlier single option procedure to the development of multiple options for trading and selecting optimum performance of missio

10、n systems.A total system decomposes into tiers of systems, elements, and components throughout the concept formulation, definition, and design phases. Each tier decomposes further into design parameter tasks which expand and interact with systems, elements, or components of the respective tier. Task

11、s identify design parameter requirements, develop design options to satisfy requirements, perform trades, and formulate criteria by which the best option leading to final design, specifications and plans can be selected. Total quality management procedures consisting of matrix methods, quality techn

12、iques, and life cycle cost analyses can be applied within the systems design analysis process throughout all design phases to achieve the simultaneous goals of high reliability and low life-cycle costs.Matrix Methods: A system is a set of parts whose behavior depends on the behavior of other parts.

13、The need to flow scheduled information in a complex system often results in decisions based on limited analyses and understanding of user requirements and the complex relationship among interacting systems. Matrix methods are used to make these relationships more orderly, visible, and understandable

14、. While the work breakdown structure (WBS) is a hierarchical relationship, it is still one-dimensional and, as such, cannot depict the many interactions between a systems subsystems, components, and parts. Matrices, however, can be multidimensional, and can interact with each other in much the same

15、way they do in a relational data base. As an example, Figure 1 shows a multidimensional matrix progression for payload and launch vehicle subsystem analysis.Payload requirements, listed as rows in matrix 1(a), are determined by the characteristics of payload packages A, B, C, or D, which are arrange

16、d in columns. Each payload package, transferred to rows in matrix 1(b), can be accommodated by selected vehicle concepts arranged in columns E, F, G, and H. The varying vehicle parameters of each of the vehicle concepts can be displayed in a third matrix 1(c), showing the concepts impact on each lau

17、nch vehicle system.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-In a three-dimensional matrix, shown on 1(d), the impact on each system element can be assessed. These matrices, which can progress down further into components and parts, permit inte

18、ractive assessment of requirements flow-down and buildup as the design evolves for a launch vehicle that can accommodate a family of payloads. This arrangement is uniquely adaptable to computer-aided analysis.refer to D descriptionD Quality Techniques: Typical quality techniques applicable to system

19、s design phases are quality leverage, quality function deployment, concurrent engineering, and Paretos principle. Quality leverage, as shown on Figure 2, is greater during the earlier phases of a project. The earlier the control of objectives, the more timely and efficient are the solutions and modi

20、fications.refer to D descriptionDConcurrent or simultaneous systems engineering is a team effort in which all essential disciplines participate in the analysis and selection of concepts, components, materials, manufacturing processes, and major operations. Concurrent engineering is initiated during

21、the concept phase and may expand and branch into systems and element Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-integration working groups as required during the design phases. Team success depends on the adoption of the best available practices

22、, avoidance of previously unsuccessful practices, and on a creative environment fostered by the teams technical leadership.Paretos principle observes that 20 percent of parameters cause 80 percent of results. A reasonable approach for setting priorities to improve products or resolve problems is to

23、first address the top 20 percent of the most significant parameters. These parameters are identified through histograms of their relative sensitivities to goals, e.g., ideal performance and lowest cost. The principle may also help specify hierarchic reliabilities.Life Cycle Cost Analyses: While user

24、 requirements and their accommodations represent one side of the balance, cost to implement them represents the other weighing pan. Judging from past projects, cost goals have not been achieved too well by the space industry. A major overrun cause is stretching the program to match fiscal appropriat

25、ions. But aside from programmatics, designers have a unique responsibility to minimize overruns by completing design analyses at each design phase, controlling requirements buildup through all design phases, and reducing sources of engineering bottlenecks. The cheapest design changes are early paper

26、 changes.Cost models are the mechanisms for assessing trades and for tracking and controlling requirements buildup. They are initiated in the concept phase and expanded through all phases and levels of solutions. Models provide the basis for identifying cost driving requirements (Paretos principle)

27、and sensitivities in support of exploring innovative methods and concepts for reducing cost or for assessing vehicle evolution requirements. They provide the source and basis for making initial high leverage cost decisions and for setting development priorities on critical tasks. Cost models serve t

28、o formulate budget controls, detect cost overruns, and pace efforts relative to prevailing funds. Good cost estimates throughout the systems design analysis are the balance and enforcers of successful projects.Design Phases: The analytical design tools and principles described in the preceding parag

29、raphs are used throughout the engineering analysis process with increasing intensity as greater detail is generated about the final product. In cost-constrained environments, the analytical tools and principles should be used to derive specifications and requirements in a “reverse-engineering“ proce

30、ss which designs the system to a life cycle cost target. The following paragraphs describe the activities in each phase that will result in the best design product.The concept phase is a first-order activity having the greatest quality leverage and, perhaps, is the most critical for the success of t

31、he mission. It is first and foremost a marketing phase which analyzes promising demands and competition for access to and for operation in space. It identifies a potential class of user needs, and it scopes missions within doable schedules and costs. Results of this phase Provided by IHSNot for Resa

32、leNo reproduction or networking permitted without license from IHS-,-,-are a set of select, top-level design specifications of customer needs and mission concepts to satisfy them. It includes a comprehensive set of mission requirements and constraints; first-order definition of vehicle configuration

33、, systems, and elements; operation scenarios; and a basis for estimating costs. Subsequent phases peel the systems and elements to lower hierarchies, and expand the systems process of requirements, solutions, and selections.The definition phase is a detailed continuation of the concept process in id

34、entifying design parameters and requirements of the selected vehicle concept, and in developing solution options and selection criteria leading to a vehicle configuration and to system, element, and component preliminary designs. Results encompass a detailed definition of total vehicle systems and s

35、ystem elements including flight hardware, support equipment, software, and personnel, and the complete operational use definition, configuration description, preliminary design, and systems operational plans. Requirements identified in this phase are documented as vehicle specifications. A total lif

36、e cycle cost of elements is also required. Concurrent engineering teams develop selection criteria and select and verify solutions. Teams include flight, propulsion, structures, avionics and facilities systems, and should have representation from the mass properties, reliability, manufacturing, veri

37、fication, operations, safety, and costing disciplines.The design phase is the final systems analysis phase and perhaps the most consequential because its detailed design must fit and function as an integrated whole. It is also in the realm of lowest design quality leverage. This phase must proceed w

38、ith detailed bottoms-up costing adjustments. The systems analysis must penetrate all final component designs for compliance with all tiers of specifications and requirements, and to amend emanating deficiencies through relevant upstream design phases. It must assess and assure that integration confl

39、icts and issues are identified and resolved through all levels of components and systems. It must further analyze and modify detailed component designs and their integrations for (1) high quality performance, (2) manufacture, (3) verification, and (4) operations at lowest cost.Technical Rationale:Ma

40、ny years of experience in developing launch vehicles, propulsion systems, and payloads, have been combined with emerging design management techniques to formulate a rigorous methodology for developing low cost, high reliability, launch vehicle for space applications. Greater detail in employing this

41、 methodology than presented here can be found in the references, and in the recent classic literature on total quality management, project management, and systems engineering. Conscientious application of these latest methods, coupled with the use of emerging computer-based analysis and simulation t

42、ools, cannot only improve product reliability and cost effectiveness, but also reduce the cost and time required for the design process itself.References1. Ryan, Robert, and Verderaine, V.: “System Design Analysis Applied to Launch Vehicle Provided by IHSNot for ResaleNo reproduction or networking p

43、ermitted without license from IHS-,-,-Configuration,“ NASA Technical Paper #3326, Marshall Space Flight Center, Alabama, 1993.2. Steward, D.V.: “Systems Analysis and Management,“ Petrocelli Books, Inc., New York, 1981.3. Blanchard, Benjamin S.: “System Engineering Management,“ John Wiley & Sons, Inc

44、., New York, 1991.4. Hopkins, J.: “Approaches to Reduced Launch Operations Costs,“ SAE 901877, Aerospace Technical Conference, October 1990.5. Rutledge, William S.: “Launch Vehicle Cost Trends,“ Aerospace America, June 1994.Impact of Non-Practice: Failure to effectively use the methods and tools des

45、cribed in this practice could result in excessive project development time or cost, and failure to attain the highest achievable reliability.Related Practices: N/AAdditional Info: Approval Info: a71 Approval Date: 2000-04-06a71 Approval Name: Eric Raynora71 Approval Organization: QSa71 Approval Phone Number: 202-358-4738Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-