Lecture

Cryogenic Tanks for Bi-Liquid Propulsion

Graph Chat

Chat with Graph Search

Ask any question about EPFL courses, lectures, exercises, research, news, etc. or try the example questions below.

DISCLAIMER: The Graph Chatbot is not programmed to provide explicit or categorical answers to your questions. Rather, it transforms your questions into API requests that are distributed across the various IT services officially administered by EPFL. Its purpose is solely to collect and recommend relevant references to content that you can explore to help you answer your questions.

In course

ME-314: Concurrent engineering project

L'étudiant apprend à appliquer les compétences acquises en travaillant dans une équipe responsable d'une portion d'un projet plus vaste. ...

Description

This lecture covers the design and manufacturing process of cryogenic tanks for bi-liquid propulsion, including material selection, geometry design, and safety requirements. The tanks are assembled using carbon fiber tubes and cryogenic resistant adhesive epoxy, with a focus on using aluminum alloy, stainless steel, and carbon fiber reinforced polymer. The manufacturing steps involve capillary machining, welding, winding with carbon filaments, and testing for safety.

This video is available exclusively on Mediaspace for a restricted audience. Please log in to MediaSpace to access it if you have the necessary permissions.

Watch on Mediaspace

Official source

Related concepts (11)

Business requirements

Business requirements, also known as stakeholder requirements specifications (StRS), describe the characteristics of a proposed system from the viewpoint of the system's end user like a CONOPS. Products, systems, software, and processes are ways of how to deliver, satisfy, or meet business requirements. Consequently, business requirements are often discussed in the context of developing or procuring software or other systems. Three main reasons for such discussions: A common practice is to refer to objectives, or expected benefits, as 'business requirements.

Non-functional requirement

In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviours. They are contrasted with functional requirements that define specific behavior or functions. The plan for implementing functional requirements is detailed in the system design. The plan for implementing non-functional requirements is detailed in the system architecture, because they are usually architecturally significant requirements.

Carbon fibers

Carbon fibers or carbon fibres (alternatively CF, graphite fiber or graphite fibre) are fibers about in diameter and composed mostly of carbon atoms. Carbon fibers have several advantages: high stiffness, high tensile strength, high strength to weight ratio, high chemical resistance, high-temperature tolerance, and low thermal expansion. These properties have made carbon fiber very popular in aerospace, civil engineering, military, motorsports, and other competition sports.

Requirements analysis

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements. Requirements analysis is critical to the success or failure of a systems or software project.cite book |editor1= Alain Abran |editor2=James W.

Requirements traceability

Requirements traceability is a sub-discipline of requirements management within software development and systems engineering. Traceability as a general term is defined by the IEEE Systems and Software Engineering Vocabulary as (1) the degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or primary-subordinate relationship to one another; (2) the identification and documentation of derivation paths (upward) and allocation or flowdown paths (downward) of work products in the work product hierarchy; (3) the degree to which each element in a software development product establishes its reason for existing; and (4) discernible association among two or more logical entities, such as requirements, system elements, verifications, or tasks.

Related lectures (49)

Systems Engineering: Requirements, Architecture, and Standards

Explores the history, definitions, and challenges of Systems Engineering, emphasizing the importance of requirements in system design and architecture.

Requirements Definition

Explores the fundamentals of requirements definition in systems engineering, emphasizing the importance of clear and concise requirements for successful system design.

Medical Devices Regulation: Market Authorization and Compliance

Explores the regulation of medical devices in Europe, covering market authorization, risk classification, conformity assessment, and post-market surveillance.

Collaborative Robots in the Wild: Challenges and Future Directions

Explores challenges and future directions of collaborative robots in real-world scenarios from a human-centric perspective.

Systems Engineering: Introduction and Stakeholders