<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dokAAPp xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../../../../prj/bin/GuidICS/dokAAPp.xsd">
    <author>
        <individual>
            <ind firstName="Paweł" ini="pb" org="NIK" role="drafting" surName="Banaś"/>
            <ind firstName="Biljana" ini="BiBul" org="SAI Montenegro" role="review" surName="Bulatović"/>
        </individual>
        <organization>
            <org kraj="USA" nm="US Government Accountability Office" skr="GAO" www="www.gao.gov"/>
        </organization>
    </author>
    <about caseNumber="9" file="NASAprojects" folder="C:\pb\Algorytm\SAI_robo\US\2026\NASAprojects" id="US2026NASAprojects" issueYear="2026" waga="341" wagaDepth="9" wagaBreadth="32">
        <tyt>
            <tx file="NASAprojects.pdf" l="en" nm="NASA Assessments of Major Projects" typDok="summary"/>
        </tyt>
        <portfolio>
            <pfl zn="innovation"/>
        </portfolio>
        <ver put="202609202021" stage="final"/>
    </about>
    <part id="lead">
        <tyt>
            <tx l="en" nm="Stable portfolio, concentrated risk"/>
        </tyt>
        <narrative>
            <narr l="en">
                <ak nr="1">The GAO's 18th annual review of NASA's major projects finds a portfolio of 36 projects, worth at least 70 billion dollars in life-cycle costs, that is broadly under control: only 4 of 18 projects in development reported new cost or schedule overruns this year. That aggregate stability, however, conceals two concentrated sources of risk that dominate the individual case findings below - a wholesale restructuring of the Artemis lunar-return architecture triggered by a December 2025 executive order, which is forcing simultaneous re-design across half a dozen interdependent projects; and a 22 percent cut to NASA's civil-servant workforce in 2025, whose effects on specific projects are only now surfacing. A handful of individual project assessments - Commercial Crew's Starliner anomaly, Dragonfly's power-source shortfall, Mars Sample Return's cancellation - further illustrate internal-control weaknesses that cut across categories.</ak>
            </narr>
        </narrative>
    </part>
    <part id="background" v="01">
        <tyt>
            <tx l="en" nm="Background"/>
        </tyt>
        <part id="scale">
            <tyt>
                <tx l="en" nm="Scale"/>
            </tyt>
            <narrative>
                <narr l="en">
                    <ak tp="li">$70 billion is the estimated total life-cycle cost of NASA's portfolio of 36 major projects (each over $250 million).</ak>
                    <ak tp="li">18 projects are in development, 17 in formulation, and 1 (Commercial Crew Program) has no set baseline.</ak>
                    <ak tp="li">NASA's civil-servant workforce fell nearly 22 percent in 2025, affecting 25 of the 36 projects.</ak>
                </narr>
            </narrative>
        </part>
        <part id="compliance">
            <tyt>
                <tx l="en" nm="Compliance"/>
            </tyt>
            <narrative>
                <narr l="en">
                    <ak tp="li">A NASA procedural requirement defines the project life cycle, key decision points, and cost-category thresholds.</ak>
                    <ak tp="li">A federal statute triggers a mandatory replan and congressional notification once development cost growth reaches 15 percent or a milestone slips 6 months.</ak>
                    <ak tp="li">A congressional appropriations mandate established GAO's standing annual major-projects reporting requirement.</ak>
                    <ak tp="li">Two 2025 executive orders separately drove this year's workforce reductions and the Artemis mission restructuring.</ak>
                </narr>
            </narrative>
        </part>
        <part id="perfromance">
            <tyt>
                <tx l="en" nm="Performance"/>
            </tyt>
            <part id="economy">
                <tyt>
                    <tx l="en" nm="Economy"/>
                </tyt>
                <narrative>
                    <narr l="en">
                        <ak tp="li">Portfolio cumulative cost growth rose to about $4.7 billion, up $311 million from last year.</ak>
                        <ak tp="li">Two Artemis projects - Orion and SLS Block 1B - drove nearly all of the year's overruns.</ak>
                        <ak tp="li">Orion's 2026 exit will remove about $3.5 billion, 73 percent of the portfolio's cumulative cost overruns.</ak>
                    </narr>
                </narrative>
            </part>
            <part id="efficiency">
                <tyt>
                    <tx l="en" nm="Efficiency"/>
                </tyt>
                <narrative>
                    <narr l="en">
                        <ak tp="li">Portfolio cumulative schedule delay grew 11 months, to 14 years.</ak>
                        <ak tp="li">Only 2 of 18 projects in development slipped this year, by 1 month each.</ak>
                        <ak tp="li">A replan is triggered at 15 percent cost growth or a 6-month slip - the threshold Orion and SLS Block 1B crossed.</ak>
                    </narr>
                </narrative>
            </part>
            <part id="effectiveness">
                <tyt>
                    <tx l="en" nm="Effectiveness"/>
                </tyt>
                <narrative>
                    <narr l="en">
                        <ak tp="li">Testing worked as intended where it ran its course: Roman caught two design flaws pre-orbit, and GRACE-C stayed on schedule.</ak>
                        <ak tp="li">The SLS program at Marshall lost almost 20 percent of its civilian workforce in 2025.</ak>
                        <ak tp="li">GAO's recommendation to stop approving risk-compounding decisions remains only partly addressed.</ak>
                    </narr>
                </narrative>
            </part>
        </part>
    </part>
    <part id="cases" v="01">
        <tyt>
            <tx l="en" nm="Cases"/>
        </tyt>
        <ctsy>
            <gr gn="area">
                <cts id="aerospace"/>
            </gr>
            <gr gn="ins">
                <cts id="government-agency"/>
                <cts id="private-company"/>
            </gr>
            <gr gn="control">
                <cts id="coordination"/>
                <cts id="communication"/>
                <cts id="reporting"/>
                <cts id="design"/>
                <cts id="responsibility"/>
                <cts id="guidance"/>
                <cts id="monitoring"/>
                <cts id="testing"/>
                <cts id="results_review"/>
                <cts id="handover"/>
                <cts id="process_optimization"/>
            </gr>
            <gr gn="value">
                <cts id="community"/>
                <cts id="regulatory_system"/>
                <cts id="finance"/>
                <cts id="human_capital"/>
                <cts id="asset"/>
                <cts id="nature"/>
                <cts id="domain_knowledge"/>
            </gr>
            <gr gn="fun">
                <cts id="projectMethodology"/>
                <cts id="planning"/>
                <cts id="finance"/>
                <cts id="humanResources"/>
            </gr>
            <gr gn="quality">
                <cts id="clearObjectives"/>
                <cts id="adequateResourcesCompetences"/>
                <cts id="reliableInformationBase"/>
                <cts id="costControlValueForMoney"/>
                <cts id="soundRiskManagement"/>
            </gr>
            <gr gn="sta">
                <cts id="supplier"/>
                <cts id="partner"/>
            </gr>
        </ctsy>
        <part id="commercialCrewProgramStarliner">
            <tyt>
                <tx l="en" nm="Commercial Crew Program - Starliner anomaly investigation"/>
            </tyt>
            <narrative>
                <narr l="en">
                    <ak nr="2" ref="draft draft" tp="xm" zn="US2026NASAprojects">NASA's own root-cause report on Boeing's 2024 crewed Starliner flight test found 'a complex interplay of hardware failures, qualification gaps, leadership missteps, and cultural breakdowns that collectively posed risks to crew safety' (p.61), rooted in NASA's own incomplete systems knowledge of the spacecraft and Boeing's inadequate systems engineering and subcontractor oversight. This is the richest single case in the report: a Testing gap (insufficient thruster testing) compounded by a Responsibility failure (subcontractor oversight) and a Communication breakdown between agency and contractor, with direct exposure to Community trust in human-spaceflight safety.</ak>
                </narr>
            </narrative>
            <ctsy>
                <gr gn="control">
                    <cts id="testing"/>
                    <cts id="responsibility"/>
                    <cts id="communication"/>
                </gr>
                <gr gn="value">
                    <cts id="community"/>
                </gr>
                <gr gn="fun">
                    <cts id="projectMethodology"/>
                </gr>
                <gr gn="quality">
                    <cts id="soundRiskManagement"/>
                    <cts id="adequateResourcesCompetences"/>
                </gr>
                <gr gn="sta">
                    <cts id="supplier"/>
                </gr>
            </ctsy>
        </part>
        <part id="artemisArchitectureOverhaulCascades">
            <tyt>
                <tx l="en" nm="Artemis architecture overhaul cascades across interdependent projects"/>
            </tyt>
            <narrative>
                <narr l="en">
                    <ak nr="3" ref="draft draft" tp="xm" zn="US2026NASAprojects">A December 2025 executive order and NASA's February-March 2026 decisions paused Gateway, canceled SLS Block 1B, and halted Mobile Launcher 2, forcing Orion, HLS and EGS to redesign interfaces simultaneously. GAO states plainly: 'managing the changes described in the table presents a significant acquisition management challenge to NASA... changes to one project may have cascading effects on another' (p.24). This is a Regulatory system shock (a government strategy set by executive order) that exposes a Coordination and Design weakness across a tightly interdependent project family.</ak>
                </narr>
            </narrative>
            <ctsy>
                <gr gn="control">
                    <cts id="coordination"/>
                    <cts id="design"/>
                </gr>
                <gr gn="value">
                    <cts id="regulatory_system"/>
                </gr>
                <gr gn="fun">
                    <cts id="planning"/>
                </gr>
                <gr gn="quality">
                    <cts id="clearObjectives"/>
                    <cts id="soundRiskManagement"/>
                </gr>
            </ctsy>
        </part>
        <part id="workforceReductionsErodeProject">
            <tyt>
                <tx l="en" nm="Workforce reductions erode project continuity (DAVINCI)"/>
            </tyt>
            <narrative>
                <narr l="en">
                    <ak nr="4" ref="draft draft" tp="xm" zn="US2026NASAprojects">The 2025 deferred-resignation program cost the DAVINCI project at Goddard Space Flight Center its program-management and engineering leads with no backfill: 'DAVINCI lost critical team members with leadership roles in program management and engineering to the deferred resignation program and was unable to backfill the positions in fiscal year 2025' (p.32), forcing it to rescope planned risk-reduction work. A direct hit to Human capital (skills and knowledge retention), triggered by a government strategy (the workforce-reduction executive order) and answered, in part, by a new Guidance directive to rebuild in-house technical roles.</ak>
                </narr>
            </narrative>
            <ctsy>
                <gr gn="control">
                    <cts id="guidance"/>
                </gr>
                <gr gn="value">
                    <cts id="human_capital"/>
                    <cts id="regulatory_system"/>
                </gr>
                <gr gn="fun">
                    <cts id="humanResources"/>
                </gr>
                <gr gn="quality">
                    <cts id="adequateResourcesCompetences"/>
                </gr>
            </ctsy>
        </part>
        <part id="romanSpaceTelescopeTesting">
            <tyt>
                <tx l="en" nm="Roman Space Telescope - testing catches design flaws before launch"/>
            </tyt>
            <narrative>
                <narr l="en">
                    <ak nr="5" ref="draft draft" tp="xm" zn="US2026NASAprojects">Thermal vacuum testing on the Nancy Grace Roman Space Telescope caught two design flaws before shipment: 'project officials said, during the SCIPA thermal vacuum testing, they identified cryogenic frost (microscopic ice) buildup on the WFI detectors' (p.80), and unexpectedly high sun-shield-harness temperatures. Both were mitigated pre-launch. A positive counter-example to the Starliner case: the same Testing function working exactly as intended, followed by Process optimization (new decontamination-cycle procedures) in response.</ak>
                </narr>
            </narrative>
            <ctsy>
                <gr gn="control">
                    <cts id="testing"/>
                    <cts id="process_optimization"/>
                </gr>
                <gr gn="fun">
                    <cts id="projectMethodology"/>
                </gr>
                <gr gn="quality">
                    <cts id="soundRiskManagement"/>
                </gr>
            </ctsy>
        </part>
        <part id="dragonflyExternalAgencyS">
            <tyt>
                <tx l="en" nm="Dragonfly - an external agency's data invalidates the operating plan"/>
            </tyt>
            <narrative>
                <narr l="en">
                    <ak nr="6" ref="draft draft" tp="xm" zn="US2026NASAprojects">The Department of Energy, which supplies Dragonfly's radioisotope power source, told NASA after the design was set that 'the MMRTG will produce less thermal power than the project requires under the current concept of operations' (p.66), forcing a rework of the lander's surface-recharge planning. An Asset risk NASA does not itself control, surfacing a Domain knowledge gap at the boundary with the body that supplies the component rather than within NASA's own engineering.</ak>
                </narr>
            </narrative>
            <ctsy>
                <gr gn="value">
                    <cts id="asset"/>
                    <cts id="domain_knowledge"/>
                </gr>
                <gr gn="fun">
                    <cts id="planning"/>
                </gr>
                <gr gn="quality">
                    <cts id="reliableInformationBase"/>
                </gr>
                <gr gn="sta">
                    <cts id="supplier"/>
                </gr>
            </ctsy>
        </part>
        <part id="rosalindFranklinSupportFunding">
            <tyt>
                <tx l="en" nm="Rosalind Franklin Support - a funding lapse delays a nuclear license"/>
            </tyt>
            <narrative>
                <narr l="en">
                    <ak nr="7" ref="draft draft" tp="xm" zn="US2026NASAprojects">A government shutdown delayed launch-vehicle selection for ROSA, which in turn delayed the start of the nuclear launch-authorization process for the rover's radioisotope heaters: 'ROSA's top risk is the delay in receiving nuclear launch authorization... The selection was delayed by 3 months because of the government shutdown' (p.81). A macro-level Regulatory system event (an appropriations lapse) propagating into a specific technical Coordination risk with the Department of Energy's licensing process.</ak>
                </narr>
            </narrative>
            <ctsy>
                <gr gn="control">
                    <cts id="coordination"/>
                </gr>
                <gr gn="value">
                    <cts id="regulatory_system"/>
                </gr>
                <gr gn="fun">
                    <cts id="planning"/>
                </gr>
                <gr gn="quality">
                    <cts id="soundRiskManagement"/>
                </gr>
            </ctsy>
        </part>
        <part id="marsSampleReturnCancelled">
            <tyt>
                <tx l="en" nm="Mars Sample Return - cancelled before alternatives were evaluated"/>
            </tyt>
            <narrative>
                <narr l="en">
                    <ak nr="8" ref="draft draft" tp="xm" zn="US2026NASAprojects">Mars Sample Return was cancelled as unaffordable and staff drawn down before NASA finished comparing cheaper NASA-led and commercial lander architectures that could have cut cost and schedule substantially: 'NASA began closing out the program before it completed its assessment of these options' (p.73). A Handover and Results review weakness - closeout initiated ahead of the analysis meant to inform it - compounding a Human capital loss (engineering expertise dispersed mid-decision) and a Finance-driven (affordability) cancellation.</ak>
                </narr>
            </narrative>
            <ctsy>
                <gr gn="control">
                    <cts id="handover"/>
                    <cts id="results_review"/>
                </gr>
                <gr gn="value">
                    <cts id="human_capital"/>
                    <cts id="finance"/>
                </gr>
                <gr gn="fun">
                    <cts id="finance"/>
                </gr>
                <gr gn="quality">
                    <cts id="clearObjectives"/>
                    <cts id="costControlValueForMoney"/>
                </gr>
            </ctsy>
        </part>
        <part id="orionDominatesPortfolioWide">
            <tyt>
                <tx l="en" nm="Orion dominates portfolio-wide cost and schedule metrics"/>
            </tyt>
            <narrative>
                <narr l="en">
                    <ak nr="9" ref="draft draft" tp="xm" zn="US2026NASAprojects">Orion's overruns account for 52 percent of the portfolio's annual cost overruns (p.16), and its departure from the portfolio after its April 2026 launch will remove 'approximately 3.5 billion dollars in development cost overruns - or 73 percent of the current portfolio's total development cost overruns' (p.19). A single project this dominant distorts aggregate Reporting - portfolio-level figures can mask, rather than reflect, the other 17 projects - and underlines why Finance baselines need to be read project-by-project, not only in the aggregate.</ak>
                </narr>
            </narrative>
            <ctsy>
                <gr gn="control">
                    <cts id="reporting"/>
                </gr>
                <gr gn="value">
                    <cts id="finance"/>
                </gr>
                <gr gn="fun">
                    <cts id="finance"/>
                </gr>
                <gr gn="quality">
                    <cts id="reliableInformationBase"/>
                </gr>
            </ctsy>
        </part>
        <part id="earthScienceInstrumentsFunding">
            <tyt>
                <tx l="en" nm="Earth-science instruments under funding and currency pressure"/>
            </tyt>
            <narrative>
                <narr l="en">
                    <ak nr="10" ref="draft draft" tp="xm" zn="US2026NASAprojects">Climate and environmental-monitoring missions GRACE-C and SBG-TIR face both cancellation proposals and, for GRACE-C, an unusual cost risk: 'the project is also tracking a risk to its cost reserves due to the exchange rate between the U.S. dollar and the euro, which is increasing the cost of work completed by European contractors' (p.69). These are jointly delivered missions - DLR on GRACE-C, ASI on SBG-TIR - and the currency exposure arises precisely because a substantial share of the work sits on the partner side of the arrangement. A case that ties directly to Nature (the missions monitor water, ice mass and land-surface change), with Finance exposure running through the partnership rather than through domestic budget alone.</ak>
                </narr>
            </narrative>
            <ctsy>
                <gr gn="value">
                    <cts id="nature"/>
                    <cts id="finance"/>
                </gr>
                <gr gn="fun">
                    <cts id="finance"/>
                </gr>
                <gr gn="quality">
                    <cts id="costControlValueForMoney"/>
                </gr>
                <gr gn="sta">
                    <cts id="partner"/>
                </gr>
            </ctsy>
        </part>
    </part>
</dokAAPp>
