subtier-shortage

Trace sub-tier supply shortages up multi-level BOMs and price mitigation options.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill subtier-shortage-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subtier-shortage
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/business-workflows/subtier-shortage
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill subtier-shortage-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A tier-N risk feed flags a fire, force majeure, or shutdown at a sub-tier supplier, but nothing links that event to your finished products until the shortage surfaces in the PO book weeks later, when the cheap mitigation window is half gone. This Skill runs the multi-level BOM trace, sizes the exposure by week and revenue-at-risk, and prices mitigation options so a human can decide before tier-1 confirmation. ## Core Features & Use Cases - Multi-level BOM pegging: Resolve a flagged sub-tier node to purchased materials and run a where-used explosion up to affected finished SKUs, classifying each peg as confirmed, inferred, or speculative. - Exposure sizing: Compute weeks of cover, exposure week, revenue-at-risk, and penalty exposure per SKU using on-hand, in-transit, and time-phased demand from SAP and Kinaxis. - Priced mitigation options: Rank pre-buy, qualify-alternate, reallocate, expedite, and absorb options by expected value with a downside-protection tie-breaker, gated for human approval. - Use Case: A tier-3 resin plant halts on force majeure and Everstream flags it before any tier-1 PO shows impact. The Skill pegs the resin to three finished SKUs, sizes $8.4M revenue-at-risk plus a $320K penalty, and recommends a $280K pre-buy for the risk lead to approve. ## Quick Start Ask the assistant to trace the sub-tier shortage flagged by the risk feed and size which finished SKUs and revenue are at risk.

Frequently Asked Questions about subtier-shortage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace a sub-tier supplier shortage to my finished products?

Resolve the flagged sub-tier node to purchased materials using the tier-N risk map and your AVL, then run a multi-level where-used BOM explosion from raw material through components to finished SKUs. Aggregate exposure at the end-item level so shared nodes are not double-counted.

How is revenue-at-risk calculated for a supply shortage?

For each affected SKU, compute units short per week as demand minus available supply, then multiply by the committed price per customer tier. Penalty-bearing commits are flagged separately as penalty rate times commit value.

When should I pre-buy versus wait for tier-1 confirmation?

Pre-empt when the mitigation window closes before expected tier-1 confirmation and P_real times revenue-at-risk plus penalty exceeds mitigation cost. Otherwise hold and watch, expediting only if the event confirms.

Does this Skill work with Everstream, Resilinc, or Interos risk feeds?

Yes, it reads the event and sub-tier map from tier-N risk systems like Everstream, Resilinc, or Interos, but treats your PLM and AVL as authoritative for which parts you actually buy. Coverage comes from SAP and demand from Kinaxis.

Can the Skill act on an unconfirmed shortage signal automatically?

No, it is advise-only. It traces, sizes, and prices options unattended, but every write such as risk-register entries, plan flags, and notifications holds for human approval, and outbound contact stays internal until the event confirms.

What happens if the BOM sub-tier links are incomplete?

The peg is classified as inferred or speculative, exposure is reported as a range rather than a point number, and the gap is escalated for supplier attestation. The Skill never reports no exposure when the trace has gaps.