METHODOLOGY
How Live Pulse interprets observable supply chain signals.
LogiPass Live Pulse uses observable data, traceable sources and predefined monitoring rules to translate selected operational indicators into a simple situational-awareness framework.
Observe. Validate. Interpret. Document.
Four principles guide the monitoring framework.
The methodology is designed to remain understandable, reproducible and cautious about what the available data can — and cannot — support.
OBSERVABLE FIRST
Monitoring starts with measurable operational indicators rather than headlines, sentiment or unverified claims.
TRACEABLE SOURCES
Data used in monitoring should be attributable to identifiable sources, with official and primary sources prioritized wherever practical.
RULE-BASED INTERPRETATION
State changes are based on predefined monitoring logic rather than ad hoc judgment made after an event occurs.
SIGNAL AND CONTEXT SEPARATION
Operational signals and external events are assessed separately. An external event may add context, but does not automatically determine a node state.
From source data to an operational state.
Each monitored node follows a defined sequence from data acquisition to state interpretation.
01 — SOURCE
Identify suitable, traceable data sources for the monitored node.
02 — COLLECT
Retrieve selected operational indicators at a defined observation interval.
03 — VALIDATE
Check freshness, completeness and source health before interpreting the data.
04 — INTERPRET
Apply node-specific monitoring rules to observable changes and persistence.
05 — STATE
Present the resulting condition as NORMAL, WATCH or ALERT.
The monitoring framework is common across Live Pulse, while observable indicators and thresholds may differ by node according to source availability and operating context.
Data quality before interpretation.
A signal is only as useful as the data behind it. Live Pulse evaluates source availability and data freshness separately from the operational state of a monitored node.
SOURCE HEALTH
Source Health reflects whether the underlying monitoring source is available, accessible and operating as expected.
Healthy source ≠ normal operations.
DATA FRESHNESS
Freshness reflects whether the available data is recent enough to support the current monitoring cycle.
Stale data ≠ operational alert.
State assignment is based on observed change and persistence.
NORMAL, WATCH and ALERT are assigned through node-specific monitoring rules. The framework considers observable changes, persistence and the reliability of the underlying data before presenting a state.
CHANGE
Has a monitored indicator moved meaningfully from its expected operating pattern?
PERSISTENCE
Does the observed change persist long enough to warrant greater attention?
CONFIDENCE
Is the source sufficiently healthy and the data sufficiently fresh to support interpretation?
A state transition is intended to reflect observable operating conditions, not a prediction of what will happen next.
Monitoring rules evolve — historical meaning should remain clear.
Live Pulse monitoring frameworks may be refined as data coverage improves, operating conditions change or validation produces new evidence. Material rule changes are documented so historical states can be interpreted in the context of the methodology used at the time.
RULE VERSIONING
Each material monitoring change is associated with a defined rule version, helping distinguish changes in operating conditions from changes in methodology.
HISTORICAL INTERPRETATION
Historical NORMAL, WATCH and ALERT states should be understood using the monitoring rules and source conditions that applied when those states were produced.
Past states are not silently redefined when current monitoring rules change.
External hazards provide context — not automatic conclusions.
Major external events can affect supply chain conditions, but the occurrence of an event does not by itself establish operational disruption.
DETECT
Identify major external events with potential relevance to monitored logistics regions.
ASSESS EXPOSURE
Consider geographic proximity, affected infrastructure and potential supply chain relevance.
KEEP SIGNALS SEPARATE
External hazard information may increase attention, but node-level WATCH or ALERT states remain based on observed operational indicators.
Earthquake detected ≠ port disruption confirmed.
Methodology has boundaries.
Live Pulse provides a selective, evidence-based view of monitored logistics conditions. Coverage, data availability and monitoring precision vary by node, and no monitoring framework can capture every source of supply chain disruption.
SELECTIVE COVERAGE
Live Pulse monitors selected logistics nodes and does not represent the full global supply chain.
SOURCE DEPENDENCE
Monitoring quality depends on the availability, continuity and quality of underlying data sources.
SITUATIONAL AWARENESS
Live Pulse supports operational awareness and informed judgment. It does not replace operational, commercial, financial or investment decision-making.
LIVE MONITORING
See the methodology in action.
View current operational states across monitored Live Pulse nodes.