ECSS Structural — PFCI Screening (space-systems/ecss/pfci-screening)
Use when the task is to identify which structural items and GSE must be
treated as Potentially Fracture Critical Items (PFCIs) under ECSS-E-ST-32C
clause 6.1, using the Figure 6-1 decision-tree to determine the PFCI or
non-PFCI status of each item before fracture control analysis begins.
Domain quick reference
- An item becomes a PFCI when all five conditions are satisfied: it
performs a structural function, its failure would be catastrophic or
critical, it carries tensile loads, it is made of a material susceptible
to fracture, and its minimum cross-section meets the dimension threshold.
The first condition that fails screens the item out as non-PFCI; that
gate is recorded as the disqualifying gate.
- GSE is in scope provided the GSE item is engaged in a critical
operation — one whose failure could cause loss of flight hardware or a
crew safety hazard. GSE not engaged during a critical operation is
excluded from fracture control scope before the five-gate check is
applied. The GSE pre-check is auditable and distinct from Gate 1.
- The minimum dimension threshold (programme default: 1.27 cm²) is the
cross-sectional area below which an item is too small to sustain a
fatigue-initiating flaw of consequence. Programmes may apply a tighter
threshold; the default applies when no programme-level override is
specified.
- Material susceptibility covers all metallic alloys, composites,
ceramics, and glass. A highly ductile material may be declared
non-susceptible only when supported by approved fracture-toughness data
and authorised by the fracture control authority.
Workflow
- Collect the item inventory: assemble the full list of candidate
structural items and GSE, each identified by a unique item ID, name,
structural role flag, worst-case failure-effect category (catastrophic,
critical, marginal, negligible), tensile-load flag, material
susceptibility flag, minimum cross-section area (cm²), and — for GSE
— whether it is engaged in a critical operation.
- Apply the GSE pre-check: for each GSE item, confirm it supports a
critical operation. Exclude it as non-PFCI (gate: GSE-CRITICAL-OPERATION)
if it does not; carry it forward otherwise.
- Apply Gate 1 — Structural role: exclude items that perform no
load-bearing structural function (gate: GATE-1-STRUCTURAL).
- Apply Gate 2 — Failure effect: exclude items whose worst-case failure
effect is marginal or negligible (gate: GATE-2-FAILURE-EFFECT).
- Apply Gate 3 — Tensile-load presence: exclude compression-only or
unloaded items that carry no tensile stress component capable of driving
crack growth (gate: GATE-3-TENSILE-LOAD).
- Apply Gate 4 — Material susceptibility: exclude items whose material
holds an approved non-susceptibility declaration (gate: GATE-4-MATERIAL).
- Apply Gate 5 — Minimum dimension: exclude items whose minimum
cross-section is below the threshold (gate: GATE-5-DIMENSION).
- Items that survive all five gates are PFCI. Compile the PFCI list and
the per-item gate trail for handover to fracture control analysis.
Pitfalls
- Omitting GSE from the screening inventory: GSE items that interface
with flight hardware during critical operations (lifting, transport,
mechanical test fixtures) must enter the screening process; their
absence silently understates the fracture control programme scope.
- Recording a non-PFCI outcome without a disqualifying gate: the gate
trail is auditable evidence; an item screened out without a recorded
gate cannot be verified during fracture control reviews.
- Applying the minimum-dimension gate before the failure-effect or
tensile-load gates: the five-gate order is not arbitrary — applying
Gate 5 first can incorrectly exclude an item that would have been
screened in at Gate 2 by a programme-level override.
- Conflating "no catastrophic failure mode" with "no fracture concern at
all": an item with a critical (non-catastrophic) failure mode still
satisfies Gate 2 and must proceed through the remaining gates.
- Allowing a GSE item to inherit its critical-operation status from its
parent assembly: each GSE item is assessed individually on whether its
own failure during the operation could cause the critical outcome.
Behavior contract (gate 3)
The GSE pre-check, all five screening gates, batch-screening aggregation,
and input-validation error paths are exercised by the gate 3 contract
test: scripts/test_pfci_screening.py against scripts/pfci_screening_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_pfci_screening.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: pfci-screening3description: "Use when identify the Potentially Fracture Critical Items (PFCIs) within a structural assembly or ground support equipment (GSE) set under ECSS-E-ST-32C clause 6.1: screen each item through the Figure 6-1 decision tree by checking structural role, worst-case failure effect, tensile-load presence, material fracture susceptibility, and minimum dimension threshold; determine whether each item is a PFCI requiring fracture control or a non-PFCI; and record the first gate where non-PFCI items are screened out. GSE items engaged in critical operations are included in the screening scope. Trigger: ecss, e-st-32-structures-scope, pfci, fracture-control, structural-screening, gse, fracture-critical, pfci-list."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/pfci-screening15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-32-structures-scope, pfci, fracture-control, structural-screening, gse, fracture-critical, figure-6-1]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Structural — PFCI Screening (space-systems/ecss/pfci-screening)2324Use when the task is to identify which structural items and GSE must be25treated as Potentially Fracture Critical Items (PFCIs) under ECSS-E-ST-32C26clause 6.1, using the Figure 6-1 decision-tree to determine the PFCI or27non-PFCI status of each item before fracture control analysis begins.2829## Domain quick reference3031- An item becomes a PFCI when all five conditions are satisfied: it32 performs a structural function, its failure would be catastrophic or33 critical, it carries tensile loads, it is made of a material susceptible34 to fracture, and its minimum cross-section meets the dimension threshold.35 The first condition that fails screens the item out as non-PFCI; that36 gate is recorded as the disqualifying gate.37- GSE is in scope provided the GSE item is engaged in a critical38 operation — one whose failure could cause loss of flight hardware or a39 crew safety hazard. GSE not engaged during a critical operation is40 excluded from fracture control scope before the five-gate check is41 applied. The GSE pre-check is auditable and distinct from Gate 1.42- The minimum dimension threshold (programme default: 1.27 cm²) is the43 cross-sectional area below which an item is too small to sustain a44 fatigue-initiating flaw of consequence. Programmes may apply a tighter45 threshold; the default applies when no programme-level override is46 specified.47- Material susceptibility covers all metallic alloys, composites,48 ceramics, and glass. A highly ductile material may be declared49 non-susceptible only when supported by approved fracture-toughness data50 and authorised by the fracture control authority.5152## Workflow53541. Collect the item inventory: assemble the full list of candidate55 structural items and GSE, each identified by a unique item ID, name,56 structural role flag, worst-case failure-effect category (catastrophic,57 critical, marginal, negligible), tensile-load flag, material58 susceptibility flag, minimum cross-section area (cm²), and — for GSE59 — whether it is engaged in a critical operation.602. Apply the GSE pre-check: for each GSE item, confirm it supports a61 critical operation. Exclude it as non-PFCI (gate: GSE-CRITICAL-OPERATION)62 if it does not; carry it forward otherwise.633. Apply Gate 1 — Structural role: exclude items that perform no64 load-bearing structural function (gate: GATE-1-STRUCTURAL).654. Apply Gate 2 — Failure effect: exclude items whose worst-case failure66 effect is marginal or negligible (gate: GATE-2-FAILURE-EFFECT).675. Apply Gate 3 — Tensile-load presence: exclude compression-only or68 unloaded items that carry no tensile stress component capable of driving69 crack growth (gate: GATE-3-TENSILE-LOAD).706. Apply Gate 4 — Material susceptibility: exclude items whose material71 holds an approved non-susceptibility declaration (gate: GATE-4-MATERIAL).727. Apply Gate 5 — Minimum dimension: exclude items whose minimum73 cross-section is below the threshold (gate: GATE-5-DIMENSION).748. Items that survive all five gates are PFCI. Compile the PFCI list and75 the per-item gate trail for handover to fracture control analysis.7677## Pitfalls7879- Omitting GSE from the screening inventory: GSE items that interface80 with flight hardware during critical operations (lifting, transport,81 mechanical test fixtures) must enter the screening process; their82 absence silently understates the fracture control programme scope.83- Recording a non-PFCI outcome without a disqualifying gate: the gate84 trail is auditable evidence; an item screened out without a recorded85 gate cannot be verified during fracture control reviews.86- Applying the minimum-dimension gate before the failure-effect or87 tensile-load gates: the five-gate order is not arbitrary — applying88 Gate 5 first can incorrectly exclude an item that would have been89 screened in at Gate 2 by a programme-level override.90- Conflating "no catastrophic failure mode" with "no fracture concern at91 all": an item with a critical (non-catastrophic) failure mode still92 satisfies Gate 2 and must proceed through the remaining gates.93- Allowing a GSE item to inherit its critical-operation status from its94 parent assembly: each GSE item is assessed individually on whether its95 own failure during the operation could cause the critical outcome.9697## Behavior contract (gate 3)9899The GSE pre-check, all five screening gates, batch-screening aggregation,100and input-validation error paths are exercised by the gate 3 contract101test: scripts/test_pfci_screening.py against scripts/pfci_screening_logic.py102(stdlib unittest, offline). Run:103python3 scripts/test_pfci_screening.py104105## Compliance106107- ECSS standards are freely downloadable (ESA); cite the source and108 paraphrase per standards-map.yaml.109- compliance: STANDARDS-REF, gated: false.