Claude Skills by ashfordeOU

Audit the device verification control document of ECSS-E-ST-20-40C clause 5.1.5 as the controlled record it is meant to be: check the issue and revision that identify the baseline, place every requirement against the qualification, acceptance, pre-launch and in-orbit stages in that order, refuse a stage recorded closed while an earlier applicable stage is still open, report a closure carrying no evidence reference, keep not-applicable stages out of the denominator while counting them, and rep...

Assess whether the evidence gathering method allocated to each device requirement can actually settle it, under ECSS-E-ST-20-40C clause 4.2: fold test, analysis, similarity, review of design and inspection onto one set, derive the admissible methods from the kind of requirement and whether it carries a number, rule on a similarity claim only against a named heritage item qualified to at least the severity now claimed, and report every requirement left with no method or with evidence that woul...

Assess whether the complete device verification plan is actually ready at the start of the design phase, as ECSS-E-ST-20-40C clause 5.4.2 requires: judge each entry on all five fields it needs to be executable, treat a field reading TBD or TBC as empty and name it, keep a requirement carrying no entry inside the completeness denominator, and refuse a plan still at draft however full its entries look. Use when a design phase is about to open on a verification plan, or when plan readiness is ch...

Assess a device verification plan against the strategy, methods and coverage goals ECSS-E-ST-20-40C Annex C makes mandatory: confirm the strategy names an approach and the levels verification runs at, place every requirement at one of those levels, check that the methods nominated can actually answer that kind of requirement, and compare the coverage each method reaches against the goal the plan committed to, counting requirements with no method rather than dropping them. Use when a verificat...

Audit a device experience summary report against the required contents of ECSS-E-ST-20-40C Annex I when the development effort closes. Use when the closing report has to carry the lessons the project paid for in a form the next one can act on: confirm each lesson states an observation, a cause, a recommendation and an owner, trace every anomaly raised during development to the lesson that captures it, compute the severity-weighted traceability the report achieves, form the occurrence-by-impac...

Determine whether the device Experience Summary Report is owed at all and, when it is, whether it actually captures the development. Use when an ECSS-E-ST-20-40C clause 5.8.4 lessons record is being settled: decide applicability from the customer request before grading anything, check every mandated topic is written, trace each development event into the topic that owns its kind, separate events carried nowhere from events misfiled and events sent to an unwritten topic, weight significant eve...

Assess a device feasibility and risk report against the required contents of ECSS-E-ST-20-40C Annex F at the close of the definition phase. Use when the report has to show that each feasibility question is answered on evidence and that every risk behind it is scored, mitigated and stated as a residual: form the severity-by-likelihood magnitude of each risk before and after mitigation, band both into the declared risk categories, measure the reduction the mitigation actually buys, close a feas...

Verify that the closing versions of the documents used to apply and to procure the device can actually be released. Use when an ECSS-E-ST-20-40C clause 5.8.5 document set is being issued: resolve what the procurement route owes, check each document is present, at final issue and approved, compare every revision against the one carried from the previous phase to catch a reissue that never advanced or went backwards, confirm each names the delivered article, and report the application and procu...

Evaluate whether the definitive device Support and Maintenance Plan can be agreed at delivery. Use when an ECSS-E-ST-20-40C clause 5.8.3 plan is being settled: resolve which commitments the device type actually owes, measure each against the contracted post-delivery support period, report the shortfall in months, find the shortest commitment that caps the whole plan, weigh the technology obsolescence horizon and treat a declared mitigation as what lifts that cap, check the agreed anomaly resp...

Draft the early device data sheet ECSS-E-ST-20-40C clause 5.4.5 puts in front of readers outside the development: group every characteristic, demand a unit on every numeric figure so a bare number cannot travel, hold each figure inside the range the sheet itself declares while letting a value landing exactly on a bound stay inside, refuse a figure called confirmed while its basis is still an estimate or a simulation, demand a plain description an outside reader can act on, and report the mand...

Assess the preliminary ESCC detail specification a device owes at the close of layout under ECSS-E-ST-20-40C clause 5.6.7. Use when the task is deciding whether a device routed towards formal part evaluation owes an early component specification at all, confirming the draft carries every content block a procurement specification needs, checking each electrical characteristic is stated with a bound, a test condition and a temperature, verifying the recommended operating range sits inside the a...

Plan the post-delivery support ECSS-E-ST-20-40C clause 5.2.5 asks a supplier to think through while the device is still being defined: size the support window in months, report a maintenance task whose interval is so long it never falls due inside it, turn operating hours and mean time between failures into an expected spares demand and compare it with what is actually held, find the parts whose end of life lands inside the support window with no mitigation behind them, size a lifetime buy ag...

Assess the preliminary verification and validation strategy ECSS-E-ST-20-40C clause 5.2.4 asks for while the device is still being defined: give every requirement a provisional method and an article to run it on, keep that article inside the model set the development plan declares, give every validation objective an activity deep enough to answer it, keep validation objectives from being restated as verification lines, and report the maturity the two plans reach against the target the phase g...

Evaluate a device support and maintenance plan against the required contents of ECSS-E-ST-20-40C Annex E before delivery is accepted. Use when the plan has to state the after-delivery service, the upkeep regime and the obsolescence position across a stated service life: grade each response-time commitment against the contracted one, compute how often every upkeep task falls due over that life, measure the years a part stands unsupported beyond its last-time-buy date, size the lifetime-buy qua...

Determine which baseline requirements a device actually carries once its type and criticality category are known, under ECSS-E-ST-20-40C clause 5.1.2: fold the category and device type spellings onto ordered sets, keep each requirement whose type reach covers the device and whose criticality floor its category meets, confirm the baseline is monotonic so raising a category never drops a requirement, then overlay the project delta and report each unjustified removal, each removal of a non-remov...

Verify that the verification and validation plans were genuinely refreshed once the device architecture settled, as ECSS-E-ST-20-40C clause 5.3.3 requires: compare the architecture revision each plan cites against the current one, prove the plan's own revision actually moved rather than being re-dated, reconcile entries against the current requirement and block sets in both directions, and catch an entry left pointing at the block a requirement was moved away from. Use when plan updates are r...

Assess whether the device Validation Plan is genuinely closed out so validation activities can formally begin. Use when an ECSS-E-ST-20-40C clause 5.7.4 implementation phase is ending: trace every requirement owing validation to a case, catch cases that trace nothing, flag cases carrying no pass criterion or no named environment, detect cases still written against a superseded build instead of the final implementation baseline, grade each mandated plan section on the maturity ladder, and comb...

Evaluate whether a completed device clears the final validation, qualification and acceptance review of ECSS-E-ST-20-40 clause 5.8.6. Use when the three evidence streams have to be closed out together and somebody must say whether the gate opens, opens against actions, or is held. Scores closure per stream, rejects a result claimed on a model the stream does not admit, confirms the qualification level envelopes the acceptance level by the declared ratio, refuses a waiver with no approved devi...

Allocate and track the thermal control subsystem budgets of ECSS-E-ST-31C clause 4.4.2. Use when hot-case dissipation, cold-case heater demand and thermal hardware mass each have to be rolled up against an allocation rather than estimated: load every budget line with the contingency its design-maturity category earns, roll raw and loaded totals separately, apply the system-level margin, grade dissipation against the radiator rejection capacity at its hot-case and sink temperatures, grade heat...

Verify a cryogenic control system against its agreed objectives and setups per ECSS-E-ST-31C clause 4.5.2.2. Use when a cooler, cold stage, thermal strap or cryo-radiator has to be shown compliant at the level the programme agreed: compute heat-lift margin at the operating point, peak-to-peak stability across the observation window, cooldown slack and the parasitic-load roll-up against its allocation, then confirm each objective closed at a level at least as detailed as agreed and by the agre...

Evaluate a thermal control item operating below two hundred kelvin against the cryogenic design constraints of ECSS-E-ST-31 clause 4.2.3 and its cryogenic annex: confirm the temperature sensor still resolves the cold end with usable sensitivity, decide whether a mechanical thermostat is qualified that low or must be replaced by an electronic controller, hold the interface gradient inside its allowable, and widen every material property by the scatter it acquires below the boundary before a he...

Produce and grade the thermal control deliverable set of ECSS-E-ST-31C clause 4.9 and its annexes A to F. Use when a programme has to show which thermal documents exist, what each one carries and when it issues: hold the model specification, model description, analysis report, interface control document, balance test specification and detailed design description as one register, name the content sections each owes, compute schedule slack in days against the review it is due at, and refuse a p...

Derive the thermal-control interface requirements towards the power and attitude-control subsystems under ECSS-E-ST-31C clauses 4.3.3 and 4.3.4. Use when heater power has to be allocated and the attitude side needs thermal disturbance inputs: size every heater circuit at the top of the regulated bus where power and current are worst case, grade switch current against its derated rating, build the peak and duty-weighted orbit-average demands with redundant branches counted only when both can b...

Evaluate a thermal-protection item running above four hundred and seventy kelvin against the high-temperature design constraints of ECSS-E-ST-31 clause 4.2.2 and its thermal-protection annex: compare the uncertainty-inflated peak against the material maximum use temperature, spend the recession allowance over the exposure and check what thickness is left, carry the remaining thickness into a bondline temperature the substrate can survive, and walk the surface optical properties out over the r...

Verify high-temperature thermal protection items by the thermal tests and analyses agreed for them, per ECSS-E-ST-31C clause 4.5.2.3. Use when a nose cap, leading edge, flap or heatshield tile has to be shown adequate: derive the qualification temperature as predicted peak plus agreed margin and grade material capability against that, size the required thickness from recession rate, exposure and scatter plus insulation and manufacturing tolerance, grade the bondline against its own far lower ...

Define the on-orbit thermal monitoring, in-service verification and product assurance interface a thermal control system owes under ECSS-E-ST-31C clauses 4.7 and 4.8. Use when the design is frozen and the question turns to flight: size sensor count and independent acquisition chains, derive the telemetry interval from the thermal time constant, place the alarm limit inside the operational-to-design band and report where in it, compare the flight maximum with the prediction as a signed model d...

Define the thermal-control interfaces to the launch vehicle, ground support equipment and crew life support under ECSS-E-ST-31C clauses 4.3.7 to 4.3.9. Use when fairing conditioned air, a test cooling loop or a crew-reachable surface has to be specified: take the air temperature rise the pre-launch dissipation adds and grade the item against its non-operating limit, hold the supply dew point clear of the coldest surface, subtract thermal growth and deflection from the dynamic envelope clearan...

Evaluate the end-of-life case of a thermal control design against ECSS-E-ST-31C clauses 4.4.3 to 4.4.5. Use when a radiator coating, a materials list or a parts list has to be shown good at end of life and not only at beginning of life: ageing the solar absorptance and the infrared emittance of each thermal-optical surface through its ultraviolet, atomic-oxygen and contamination exposure, re-forming the absorptance-to-emittance ratio and the extra absorbed power it costs, screening every vacu...

Define the thermal-control to structure mechanical interface requirements of ECSS-E-ST-31C clause 4.3.2. Use when a unit baseplate, bracket or radiator mount has to be specified rather than assumed: turn bolt preload and contact area into a contact pressure, read the declared filler conductance off its pressure curve, compare the conductance the joint offers against the one the dissipation and the allowed baseplate rise demand, convert the expansion-coefficient mismatch over the qualification...

Define the mission-phase breakdown a thermal control subsystem is designed against under ECSS-E-ST-31 clause 4.1: enumerate every phase from ground handling and pre-launch through ascent, transfer, docking, operations, descent and post-landing, check the timeline for gaps and overlaps, then attach to each phase the environment inputs its role demands - sink temperature, solar flux, albedo, planetary infrared, aerothermal heating and conducted interface loads. Use when a phase list has to be b...

Assess whether a thermal control design is predictable, testable, robust to uncertainty and reachable at integration, against ECSS-E-ST-31C clauses 4.4.6 to 4.4.8. Use when a thermal design has to be judged on its properties rather than its predicted temperatures: weighting how much of the heat path is characterised by measurement instead of assumed, combining the uncertainty contributors and the parameter sensitivities into a bounding excursion and grading the widened prediction against the ...

Audit the production, manufacturing and contamination controls a thermal control item owes under ECSS-E-ST-31C clause 4.6. Use when a radiator, MLI outer layer or optical surface moves through procurement, manufacture, cleanliness, integration, marking, the declared heat-treatment operation, storage and repair: turn the molecular and particulate allocation into end-of-life absorptance and emittance, size the radiator area growth that follows, roll the per-stage allocations up against the budg...

Evaluate the dependability provisions of a thermal control design against ECSS-E-ST-31C clauses 4.4.9 to 4.4.13. Use when the question is whether the heater chain survives a single failure rather than whether it is warm enough: building the mission reliability of redundant heater lines from their element failure rates, comparing a series thermostat stack against a parallel one for the failure that is actually hazardous, grading a spare unit's interface parameters for interchangeability withou...

Determine whether a thermal balance test met its success criteria under ECSS-E-ST-31C clause 4.5.3.2. Use when predicted and measured temperatures are both in hand and the campaign needs a defendable verdict rather than a plot: applying the per-sensor correlation tolerance band, spending the exceedance budget by sensor weight instead of by headcount, grading the weighted bias and the spread separately so a model that is right on average and wrong everywhere still fails, and refusing an exclud...

Verify a thermal control subsystem by analysis under ECSS-E-ST-31C clauses 4.5.1 and 4.5.2.1. Use when the verification evidence is a thermal mathematical model rather than a test report: closing the steady-state radiative balance for a hot and a cold case, sizing the radiator area the rejected load needs at its temperature limit, integrating the lumped-capacitance transient with a step size the stability limit allows, and correlating the model against measured temperatures by forming per-sen...

Structure the general thermal control design-to-requirements process of ECSS-E-ST-31C clause 4.4.1. Use when predicted temperatures have to become design, acceptance and qualification limits and the subsystem design drivers have to be named: turn thermal model maturity into the uncertainty margin a prediction carries, walk the hot and cold temperature stacks in the direction each case pushes, grade the design temperature against its requirement in kelvin, confirm each worst case combines cons...

Allocate every item of flight hardware to the cryogenic, conventional or high-temperature range under ECSS-E-ST-31 clauses 3.2, 4.2.1 and 4.2.4, then capture its allowable temperature limits and the uncertainty attached to each prediction, and turn the pair into the margin the thermal control subsystem is actually designed to. Use when a hardware list must be grouped by range before design rules are picked, when an item straddles two ranges and needs both rule sets, or when a predicted temper...

Define and grade the performance of a thermal balance test under ECSS-E-ST-31C clause 4.5.3.1 and its annex on test cases. Use when a thermal vacuum campaign needs its balance phases written down and run: checking the case set brackets the mission with a hot and a cold case, sizing the compensation heater power that makes a chamber shroud and a lamp bank reproduce the flight heat flow, deciding steady state from the measured drift rate over a long enough window rather than by eye, and coverin...

Define the thermal telemetry, commanding and on-board software interface requirements of ECSS-E-ST-31C clauses 4.3.5 and 4.3.6. Use when thermistor channels and software heater loops have to be specified against the data handling subsystem: turn span and converter width into a quantisation step, combine it root-sum-square with sensor and chain error into the temperature knowledge a channel delivers, grade sampling against the item thermal time constant, sum the channel bit rates against the t...

Evaluate a two-phase heat transport flight article against the acceptance principles of ECSS-E-ST-31-02 clause 4.5 and its permitted-change table: grade every proposed difference from the qualified design as accepted as is, permitted against a delta acceptance test, or outside acceptance altogether, take the most onerous grade as the one that governs, build the acceptance test set the permitted changes oblige, and confirm the acceptance levels sit inside the qualified envelope. Use when a hea...

Determine whether the burst test of a two-phase heat transport item satisfies ECSS-E-ST-31-02C clause 5.6.7. Use when the task is forming the burst requirement from maximum design pressure and the minimum burst factor, correcting it for a test temperature whose material allowable differs from the design point, grading the ramp method and whether the article had already been through its life cycling, computing the achieved burst factor, and building the leak-before-burst case from hoop stress,...

Verify the performance evidence behind a capillary driven two-phase loop or loop heat pipe under ECSS-E-ST-31-02C clause 5.5.5.2d. Use when the task is grading a start-up demonstration against the minimum start heat load with the qualification thermal mass attached, fitting how that start load moves with added evaporator mass, checking evaporator-inlet subcooling, closing the capillary pressure budget against liquid, vapour and groove losses plus the adverse tilt head, grading the unpowered h...

Maintain the declared materials, mechanical parts and processes lists ECSS-E-ST-31-02 clause 5.2 and its content table require of two-phase heat transport equipment: group every entry into its own list, reject a reused item identifier, test each entry against the mandatory fields that list owes, demand a recorded compatibility basis from anything the working fluid wets, and track approval separately from completeness so a refused item and an unfinished one are not confused. Use when a heat pi...

Verify a diode heat pipe against its forward transport, reverse heat-leak and mode-switch requirements under ECSS-E-ST-31-02C clause 5.5.5.2c. Use when the task is reading forward capability off a temperature curve, deriving forward and reverse conductance from measured heat and temperature difference, grading the diodicity ratio the pair produces, bounding the heat a reversed pipe still passes backwards into the cold side, timing how long the pipe takes to settle into reverse mode from a sam...

Verify that a heat pipe still carries its required power once operating temperature, bend layout and adverse tilt have each been taken off the nameplate figure, per ECSS-E-ST-31-02C clause 5.5.5.2a. Use when the task is reading transport capability off a temperature curve without extrapolating past its ends, converting a power-length rating into a power at the pipe's effective length, subtracting the capability an adverse evaporator elevation consumes, applying the knockdown each bend costs a...

Define the leak test of a two-phase heat transport item under ECSS-E-ST-31-02C clause 5.6.8. Use when the task is deriving the acceptance leak rate from the fluid inventory the item may lose over its life rather than quoting one, picking a method whose sensitivity actually resolves that rate, converting a helium tracer reading to the working fluid through the inverse square root of molar mass, and grading the converted rate against the acceptance value while separating a real measurement from...

Define and grade the resonance search, sinusoidal and random vibration runs of ECSS-E-ST-31-02C clause 5.6.10 for two-phase heat transport hardware. Use when vibration levels are set or a run is assessed against the applicable level tables, which are supplied as data: bracketing the first mode in the searched band and comparing the before and after sweeps for the frequency shift that signals damage, interpolating a sine profile on its log-log segments, sizing each sweep from its rate in octav...

Define the pressure cycling fatigue test of a two-phase heat transport item under ECSS-E-ST-31-02C clause 5.6.6. Use when the task is turning a service cycle count and a life scatter factor into whole test cycles, checking that the applied pressure range envelops the service range at both ends instead of only at the peak, bounding the cycle and ramp rates so the run stays a mechanical duty cycle rather than a heating run, holding the declared temperature band, and closing acceptance on the po...

Define the proof pressure test of a two-phase heat transport item under ECSS-E-ST-31-02C clause 5.6.5. Use when the task is turning a maximum design pressure and a proof factor into the pressure to apply, correcting that pressure for a test temperature whose material allowable differs from the design point, grading the applied pressure as a window between the proof target and the yield of the article rather than as a floor, checking the hold duration, and closing acceptance on no leakage and ...

Evaluate how each qualification requirement for two-phase heat transport equipment is verified and whether the generic performance demonstration actually closes, per ECSS-E-ST-31-02C clauses 5.5.3, 5.5.4 and 5.5.5.1. Use when the task is allocating test, analysis or analysis-supported-by-test to a requirement and rejecting a proposal weaker than the requirement warrants, sizing the governing mechanical design load and its margin of safety, comparing demonstrated cycles against a scatter-facto...