Where a generic CV loses supply-chain meaning
Cost, inventory, service, lead time, capacity, and resilience outcomes depend on where a role sits across planning, sourcing, production, warehousing, transport, and fulfillment. A generic operations CV can report a metric without showing the network constraint, decision horizon, trade-off, or operational ownership behind it.
What the dedicated schema must capture
The schema is being designed to distinguish planning, procurement, manufacturing, logistics, warehouse, analytics, and transformation roles. It must connect decisions to network scope, service level, working capital, risk exposure, systems, and measurable operational outcomes.
What it must never infer
The schema must not invent savings, service levels, inventory impact, supplier ownership, geographic scope, or resilience gains. Metrics must retain their baseline, boundary, and candidate-supported attribution.