ECSS Structures — DRD Alignment Budget (space-systems/ecss/drd-alignment-budget)
Use when the task is to determine and verify the structural alignment budget
for a spacecraft or instrument mounting interface, following ECSS-E-ST-32C
Annex L. The budget accounts for all sources of angular or linear misalignment
and checks the total against a specified pointing or interface requirement.
Domain quick reference
- The structural alignment budget (SAB) aggregates every contributor that
shifts a physical reference frame away from its nominal position. ECSS-E-ST-32C
Annex L requires the budget to account for five canonical contributor types:
manufacturing tolerances (dimensional variation from production), thermoelastic
distortion (temperature-induced deformation between on-ground and on-orbit thermal
states), gravity-release deformation (shape change between the 1-g ground state
and the 0-g on-orbit state), load-induced deflection (quasi-static deformation
under design limit loads), and measurement uncertainty (metrological error in
alignment measurements and surveys).
- Each contributor is assigned a sensitivity coefficient that converts the raw
magnitude into an effective error at the reference interface. A coefficient
of 1.0 means the error propagates without amplification; values above 1.0
indicate a mechanical amplification path.
- Contributions are combined by one of two methods: root-sum-square (RSS)
treats contributors as statistically independent and random — the method
is appropriate when sources are uncorrelated; worst-case arithmetic sums
absolute values and is appropriate when contributors are systematic or
when correlation cannot be demonstrated. Mixing methods within the same
budget level is not permitted.
- Every alignment-critical interface must carry an explicit allowable value
derived from the pointing or interface requirement. A budget without a
recorded allowable is not assessable; this is itself a finding, not a pass.
Workflow
- Identify every interface or pointing reference to be budgeted. For each
interface, record the applicable requirement (pointing accuracy, alignment
tolerance) that drives the allowable error.
- For each interface, enumerate all contributor types that apply. Each contributor
is recorded with its type (one of the five canonical types), raw magnitude,
and sensitivity coefficient. Reject any contributor whose type is not
recognized before it enters the budget.
- Compute the effective error for each contributor by multiplying its raw
magnitude by its sensitivity coefficient.
- Combine all effective errors at the interface using the selected method:
RSS for independent random contributors, or worst-case arithmetic for
systematic or correlated contributors. Document the method choice and its
justification.
- Compare the combined total against the interface allowable. Record the
result as compliant (total does not exceed allowable), exceeded (total
exceeds allowable — record the exceedance margin), or missing-budget
(no allowable is on record — flag as an open finding).
- Repeat for every alignment-critical interface. The budget is closed only
when every interface is compliant and all allowables are on record.
Pitfalls
- Omitting the sensitivity coefficient step and applying raw contributor
magnitudes directly as effective errors — a contributor routed through a
mechanical lever or kinematic amplification path deposits a larger error
at the reference than its measured magnitude, and ignoring the coefficient
understates the total.
- Mixing RSS and worst-case arithmetic within a single interface budget
without documented justification — selecting the more conservative method
for some contributors and the less conservative for others is not
permitted; the method must be applied uniformly or split into clearly
separate sub-budgets with explicit combination at the top level.
- Treating a missing allowable as a compliant result — an interface without
a recorded allowable has not been assessed against any requirement; it
must be flagged as an open finding and resolved before the budget is closed.
- Computing the budget only for the on-orbit thermal state and ignoring the
on-ground (pre-launch) state — alignment surveys and acceptance tests are
performed on the ground, and the gravity-release and thermoelastic
contributors must be shown to be within allowable in both states.
Behavior contract (gate 3)
The contributor-categorization, sensitivity-application, RSS-combination,
worst-case-combination, and budget-check logic is exercised by the gate 3
contract test: scripts/test_drd_alignment_budget.py against
scripts/drd_alignment_budget_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_drd_alignment_budget.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: drd-alignment-budget3description: "Use when determine the structural alignment budget for a spacecraft or instrument mounting interface under ECSS-E-ST-32C Annex L: identify every contributor to alignment error — manufacturing tolerances, thermoelastic distortion, gravity-release deformation, load-induced deflection, and measurement uncertainty — assign sensitivity coefficients, combine contributions by root-sum-square or worst-case arithmetic, and verify the resulting total against the pointing or interface alignment requirement. The budget must cover both on-ground and on-orbit alignment states and record each contributor's type, magnitude, and sensitivity coefficient. Flag any exceedance or missing allowable before closing the budget. Trigger: ecss, e-st-32c, e-st-32-structures-scope, alignment-budget, structural-alignment, thermoelastic, gravity-release, pointing-budget, interface-alignment."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/drd-alignment-budget15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-32c, e-st-32-structures-scope, alignment-budget, structural-alignment, thermoelastic, gravity-release, pointing-budget, interface-alignment]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Structures — DRD Alignment Budget (space-systems/ecss/drd-alignment-budget)2324Use when the task is to determine and verify the structural alignment budget25for a spacecraft or instrument mounting interface, following ECSS-E-ST-32C26Annex L. The budget accounts for all sources of angular or linear misalignment27and checks the total against a specified pointing or interface requirement.2829## Domain quick reference3031- The structural alignment budget (SAB) aggregates every contributor that32 shifts a physical reference frame away from its nominal position. ECSS-E-ST-32C33 Annex L requires the budget to account for five canonical contributor types:34 manufacturing tolerances (dimensional variation from production), thermoelastic35 distortion (temperature-induced deformation between on-ground and on-orbit thermal36 states), gravity-release deformation (shape change between the 1-g ground state37 and the 0-g on-orbit state), load-induced deflection (quasi-static deformation38 under design limit loads), and measurement uncertainty (metrological error in39 alignment measurements and surveys).40- Each contributor is assigned a sensitivity coefficient that converts the raw41 magnitude into an effective error at the reference interface. A coefficient42 of 1.0 means the error propagates without amplification; values above 1.043 indicate a mechanical amplification path.44- Contributions are combined by one of two methods: root-sum-square (RSS)45 treats contributors as statistically independent and random — the method46 is appropriate when sources are uncorrelated; worst-case arithmetic sums47 absolute values and is appropriate when contributors are systematic or48 when correlation cannot be demonstrated. Mixing methods within the same49 budget level is not permitted.50- Every alignment-critical interface must carry an explicit allowable value51 derived from the pointing or interface requirement. A budget without a52 recorded allowable is not assessable; this is itself a finding, not a pass.5354## Workflow55561. Identify every interface or pointing reference to be budgeted. For each57 interface, record the applicable requirement (pointing accuracy, alignment58 tolerance) that drives the allowable error.592. For each interface, enumerate all contributor types that apply. Each contributor60 is recorded with its type (one of the five canonical types), raw magnitude,61 and sensitivity coefficient. Reject any contributor whose type is not62 recognized before it enters the budget.633. Compute the effective error for each contributor by multiplying its raw64 magnitude by its sensitivity coefficient.654. Combine all effective errors at the interface using the selected method:66 RSS for independent random contributors, or worst-case arithmetic for67 systematic or correlated contributors. Document the method choice and its68 justification.695. Compare the combined total against the interface allowable. Record the70 result as compliant (total does not exceed allowable), exceeded (total71 exceeds allowable — record the exceedance margin), or missing-budget72 (no allowable is on record — flag as an open finding).736. Repeat for every alignment-critical interface. The budget is closed only74 when every interface is compliant and all allowables are on record.7576## Pitfalls7778- Omitting the sensitivity coefficient step and applying raw contributor79 magnitudes directly as effective errors — a contributor routed through a80 mechanical lever or kinematic amplification path deposits a larger error81 at the reference than its measured magnitude, and ignoring the coefficient82 understates the total.83- Mixing RSS and worst-case arithmetic within a single interface budget84 without documented justification — selecting the more conservative method85 for some contributors and the less conservative for others is not86 permitted; the method must be applied uniformly or split into clearly87 separate sub-budgets with explicit combination at the top level.88- Treating a missing allowable as a compliant result — an interface without89 a recorded allowable has not been assessed against any requirement; it90 must be flagged as an open finding and resolved before the budget is closed.91- Computing the budget only for the on-orbit thermal state and ignoring the92 on-ground (pre-launch) state — alignment surveys and acceptance tests are93 performed on the ground, and the gravity-release and thermoelastic94 contributors must be shown to be within allowable in both states.9596## Behavior contract (gate 3)9798The contributor-categorization, sensitivity-application, RSS-combination,99worst-case-combination, and budget-check logic is exercised by the gate 3100contract test: scripts/test_drd_alignment_budget.py against101scripts/drd_alignment_budget_logic.py (stdlib unittest, offline). Run:102103python3 scripts/test_drd_alignment_budget.py104105## Compliance106107- ECSS standards are freely downloadable (ESA); cite the source and108 paraphrase per standards-map.yaml.109- compliance: STANDARDS-REF, gated: false.