<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<channel rdf:about="https://yse.yabesh.ir/std/handle/yse/76">
<title>NASA - National Aeronautics and Space Administration (NASA)</title>
<link>https://yse.yabesh.ir/std/handle/yse/76</link>
<description/>
<items>
<rdf:Seq>
<rdf:li rdf:resource="https://yse.yabesh.ir/std/handle/yse/232311"/>
<rdf:li rdf:resource="https://yse.yabesh.ir/std/handle/yse/232256"/>
<rdf:li rdf:resource="https://yse.yabesh.ir/std/handle/yse/232128"/>
<rdf:li rdf:resource="https://yse.yabesh.ir/std/handle/yse/232005"/>
</rdf:Seq>
</items>
<dc:date>2026-04-20T07:31:39Z</dc:date>
</channel>
<item rdf:about="https://yse.yabesh.ir/std/handle/yse/232311">
<title>NASA-LLIS-0124</title>
<link>https://yse.yabesh.ir/std/handle/yse/232311</link>
<description>NASA-LLIS-0124; Lessons Learned - Payload Bay Duct Heater Overtemp
NASA - National Aeronautics and Space Administration (NASA)
&lt;strong&gt;Description of Driving Event:&lt;/strong&gt; &lt;br&gt;The payload bay duct heater adds measured quantities of heat independently to each duct system. This raises the temperature of the process air from the cooling coils to the desired interface temperature leaving the portable purge unit and engine control system room. With no overtemp switches installed, excessive heat from the payload bay duct heaters burned through the duct insulation, causing severe damage with a potential for orbiter damage.
</description>
<dc:date>1992-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="https://yse.yabesh.ir/std/handle/yse/232256">
<title>NASA-LLIS-1123</title>
<link>https://yse.yabesh.ir/std/handle/yse/232256</link>
<description>NASA-LLIS-1123; Lessons Learned - Aero-Space Technology/X-Vehicle Range Safety/Authority
NASA - National Aeronautics and Space Administration (NASA)
&lt;strong&gt;Description of Driving Even:&lt;/strong&gt; &lt;br&gt;Lack of NASA Range Safety Authority for X-33 and X-34 Programs
</description>
<dc:date>1999-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="https://yse.yabesh.ir/std/handle/yse/232128">
<title>NASA-LLIS-1715</title>
<link>https://yse.yabesh.ir/std/handle/yse/232128</link>
<description>NASA-LLIS-1715; Lessons Learned - The Pitfalls of "Engineering-by-Presentation" (2005)
NASA - National Aeronautics and Space Administration (NASA)
&lt;strong&gt;Abstract:&lt;/strong&gt; &lt;br&gt;Formal documentation of requirements, resolutions, and decisions was once a standard NASA practice. However, the increased use of informal documentation such as viewgraphs and e-mail may be inhibiting the ability of NASA projects to reference the basis for technical decisions and to validate or verify engineering designs. Produce a record of technical decisions and supporting information within technical reports and memos as a standard practice across the institution, with a defined process for review, approval, and records management.
</description>
<dc:date>2005-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="https://yse.yabesh.ir/std/handle/yse/232005">
<title>NASA-LLIS-1485</title>
<link>https://yse.yabesh.ir/std/handle/yse/232005</link>
<description>NASA-LLIS-1485; Lessons Learned – The Risk Reduction From ?Two-fers? (Multiple Sister Spacecraft) May Outweigh the Incremental Cost (2002)
NASA - National Aeronautics and Space Administration (NASA)
&lt;strong&gt;Abstract:&lt;/strong&gt; &lt;br&gt;NASA elected at the end of MER Phase A to build a second Mars Exploration Rover at an estimated cost of $243 million. In addition to potentially doubling science return from Mars and mitigating the program impact were a rover to fail, this "two-fer" approach proved helpful in controlling development risks. Consider the benefits to system development and I&amp;T that may accrue from building a "sister" spacecraft and from maintaining multiple testbeds.
</description>
<dc:date>2004-01-01T00:00:00Z</dc:date>
</item>
</rdf:RDF>
