Metroflow Playbook · Manufacturing & Logistics

Executive summary

Ingest IoT and ERP metadata into Metroflow. Certify OTIF and defect-rate across plants. Run blast-radius before schema migrations that could disrupt supply-chain reporting.

Factories generate sensor streams and ERP batches that rarely meet in one catalog. OT and IT silos mean OTIF is calculated five different ways and plant schema migrations cause unplanned downtime. Metroflow links sensor raw tables to supply-chain dashboards without moving operational data rows.

1OTIF definition across plants and logistics

OT/ITUnified metadata graph from sensor to dashboard

Pre-migrationImpact alerts before plant schema changes

01

What broken lineage costs you

Typical patterns at Manufacturing & Logistics organizations. Ranges, not guarantees.

OTIF calculated five ways

Weekly ops reviews spent reconciling plants

With Metroflow: One certified OTIF metric with plant-level lineage drill-down.

OT and IT never meet

Sensor data orphaned from ERP supply-chain models

With Metroflow: Unified graph: IoT ingest → staging → OTIF dashboards.

Plant schema migration

Unplanned reporting downtime across regions

With Metroflow: Pre-migration blast-radius on supply-chain and quality models.

Defect-rate audit gaps

Quality team cannot trace KPI to source sensors

With Metroflow: Certified defect-rate with path to plant_floor_sensors raw.

◇

Metadata only. Metroflow crawls schemas, job names, manifests, and dashboard definitions. Your production data rows never leave your network.

02

Your stack, one graph

Sector-specific constraints. Metroflow sits above the data path: unify compliance, velocity, and trusted metrics.

Trace plant_floor_sensors → stg_sensor_readings → fct_production_events → fct_otif → Supply Chain Dashboard. When iot_ingest_plant_a fails, see every OTIF and defect-rate tile affected.

03

Where are you today?

Most teams land at L1 or L2. Target L4 in 90 days.

L1Siloed docsWikis and spreadsheets disconnected from production.

L2Partial lineageSome tool lineage exists. Cross-layer gaps remain.

L3Unified graphOrchestration, warehouse, and BI in one map.

L4Certified metricsKPIs owned, enforced, and traced end-to-end.

L5Proactive opsPre-merge gates. Stale assets caught early.

Quick self-check

Answer "what breaks if X fails?" in under 15 minutes?
Cross-functional teams share one definition of core KPIs?
Incidents include downstream dashboard impact without Slack archaeology?
Changes include cross-layer impact checks before merge?
Named owners for certified metrics and critical pipelines?

0–2: Start Week 1 connect · 3–4: Certify metrics · 5: Add change gates

04

Choose your path

Every org is different. Pick the track closest to your context.

Discrete manufacturing

Plant IoT + ERP + regional warehouses

Priority: Certify first: OTIF, defect-rate, production yield

Logistics / 3PL network

Shipment events + carrier feeds + ERP orders

Priority: Certify first: on-time delivery and OTIF rollup

Multi-plant global ops

Different SCADA systems, unified analytics layer

Priority: Certify first: cross-plant OTIF normalization and lineage

05

Who owns what

Assign decision rights up front. Metric fights are governance problems.

Function	Owns	On Metroflow
Supply chain analytics	OTIF, fulfillment, inventory models	Own certified OTIF spec. Blast-radius on ERP and IoT failures.
Plant IT / OT	Sensor ingest, SCADA integrations	Register iot_ingest jobs. Link sensors to staging tables.
Quality engineering	Defect-rate, yield, audit reporting	Certified defect-rate with sensor-to-dashboard lineage.
Data platform	ERP exports, orchestration, migrations	Pre-migration impact queries. Plant schema change gates.

06

30 · 60 · 90 day rollout

A program with gates, not just a connector checklist.

Days 1–30

Unify OT/IT metadata

Connect IoT ingest + ERP + warehouse + BI
Map plant_floor_sensors to fct_otif path
First trace: sensor raw → OTIF dashboard

Gate: One plant with sensor-to-dashboard lineage

Days 31–60

Certify supply-chain KPIs

Publish OTIF and defect-rate specs
Normalize definitions across plants
Quality audit export template

Gate: Ops committee agrees on one OTIF number

Days 61–90

Migration guardrails

Pre-migration blast-radius program
Plant schema change approval workflow
Weekly freshness on tier-1 IoT and ERP DAGs

Gate: Zero unplanned supply-chain reporting outages from migrations

07

Incident runbook

When iot_ingest_plant_a is in trouble. Follow this timeline.

T+0 · Detect

Plant A sensor ingest failing

SCADA alert or stale stg_sensor_readings. Open Metroflow.

T+5 min · Blast radius

Run impact query

"Trace OTIF calculation to source plant sensor tables: which dashboards break?"

T+15 min · Communicate

Notify supply chain and quality

Slack template with affected plants and dashboards.

T+45 min · Fix

Remediate ingest

Plant IT restarts pipeline. Platform confirms ERP sync unaffected.

T+2h · Verify

Confirm OTIF dashboard fresh

Re-run lineage. Log for quality audit if defect-rate window active.

Slack template

[INCIDENT] iot_ingest_plant_a failing: sensor data stale Impact: plant_floor_sensors not updating · fct_otif lagging for Plant A Affected: Supply Chain Dashboard, Plant A defect-rate report, Regional OTIF rollup Owner: @plant-it-oncall · ETA 90m Supply chain: hold Plant A OTIF commit until lineage verified Metroflow blast-radius: [paste link]

08

Metric certification pack

Copy into your governance doc. One definition. One owner. Full lineage.

OTIF (weekly)

Certify first

Formula: Orders delivered on-time and in-full / total orders shipped, per plant, ISO week.

Source: erp_shipments + fct_production_events → fct_otif

Owner: Supply chain analytics + Plant ops

Lineage: plant_floor_sensors → production events → OTIF → Supply Chain Dashboard

Defect-rate (daily)

Certify first

Formula: Defective units detected / total units produced, by line and shift.

Source: stg_sensor_readings → fct_quality_events

Owner: Quality engineering

Lineage: Sensor QC station → defect model → Quality audit report

Production yield (daily)

Certify second

Formula: Good units output / total units started, excluding planned maintenance.

Source: fct_production_events

Owner: Plant ops + Analytics

09

Daily workflows

Four situations you will hit every week.

🏭

Weekly ops review

Certified OTIF
All plants on same definition?
Plant drill-down
Lineage to sensor and ERP sources.
IoT freshness
Any ingest lagging?

🔧

Before plant schema migration

Impact query
Supply-chain and quality downstream.
Notify owners
Regional ops and quality leads.
Rollback plan
Document in change ticket.

📋

Quality audit prep

Defect-rate trace
Sensor to dashboard path.
Export report
Audit-ready provenance.
Cross-plant compare
Normalize definitions.

🚨

IoT ingest failure

Blast radius
OTIF and defect dashboards affected.
OT/IT comms
Plant IT + supply chain analytics.
ERP check
Confirm order data still flowing.

10

Copy-paste queries

Company Brain or lineage search. Context included.

OTIF trace

"Trace OTIF calculation to source plant sensor tables."

Plant failure

"What dashboards break if iot_ingest_plant_a fails?"

Defect provenance

"Show lineage for defect-rate from plant_floor_sensors to the quality report."

Cross-plant reconcile

"Why does Plant B OTIF differ from Plant A methodology?"

Schema migration

"What supply-chain models depend on erp_shipments if we migrate schema?"

OT/IT map

"List all IoT ingest jobs linked to fct_otif in Metroflow."

11

Glossary

Plain English. "Why it matters" tells you when to care.

OTIF

On-time in-full: orders delivered complete and on schedule.

Why: Calculated five ways until certified across plants.

OT/IT convergence

Linking operational technology sensor data with IT analytics.

Why: Metroflow unifies metadata without merging siloed networks.

plant_floor_sensors

Raw IoT tables from SCADA and shop-floor devices.

Why: Starting point for defect-rate and production lineage.

Defect-rate

Share of produced units failing quality thresholds.

Why: Quality audits require traceable sensor provenance.

Schema migration

Structural change to plant or ERP source tables.

Why: High risk for supply-chain reporting downtime.

Company Brain

Plain-English queries across IoT and ERP metadata.

Why: Ops reviews without switching between OT and IT tools.

12

Outcomes checklist

Measure if the program is working.

Success metric	90-day target
Plants on certified OTIF definition	100%
OTIF and defect-rate traced to sensor sources	100% certified KPIs
Plant schema migrations with pre-impact review	100%
IoT ingest failures with proactive dashboard comms	100% tier-1 plants

Ready to put this playbook to work?

Week 1: connect your stack and run your first blast-radius query. Week 4: certify your first KPI. Week 8: operationalize the runbook.

Try the live demo Self-host Talk to us