Three-Phase Phase-Loss Detection Planner

 Estimate phase-loss margin from current asymmetry, compare it against a detection threshold, and highlight the lowest-current phase.

Input Model for New Users

Paste one row with the three phase-current magnitudes, their phase angles, an effective phase resistance, an equipment current limit, and a threshold value used here as phase-loss sensitivity. Current magnitudes matter most, but the shared row format keeps phasor and limit context attached so the scenario can be reused in other diagnostics. The threshold should represent the percentage loss from average current that your monitoring or relay logic is expected to treat as a phase-loss condition.

What the Tool Calculates and Why It Matters

The planner compares the weakest phase current to the average of the three phases, converts that difference into a loss gap, and reports margin to the entered detection threshold. This matters because simple current-low alarms often trip too late or too early when they are not tied to actual feeder behavior. By expressing the condition as a gap from average phase loading, the tool gives a more defensible first-pass basis for choosing or reviewing phase-loss detection sensitivity.

End-to-End Example Workflow

A maintenance team investigating intermittent motor stress enters measured phase currents from a suspect feeder and sees that one phase repeatedly falls below the expected threshold margin. The team then compares that result with breaker status and voltage data before tightening the phase-loss alarm logic. After a loose termination is repaired, the same row format is populated with the new readings to verify that the lowest phase current now sits comfortably above the trip boundary.

Advanced Domain Use Cases

The tool is useful for MCC feeders, pump stations, rooftop package units, and standby-generator branches where current-based phase-loss detection is common but often under-documented. It is also helpful when a plant wants to justify relay setting changes with a concrete load-ratio argument rather than trial and error. Teams can compare seasonal loading cases or different motor sizes using the same threshold logic and keep the reasoning explicit.

Failure Modes and Recovery Patterns

The usual failure mode is setting the threshold from memory instead of from the actual device logic or process tolerance. Another is interpreting temporary current dip events as full phase-loss evidence without checking timing and repetition. Recover by validating the threshold against real relay settings, using stable measurement windows, and reviewing current imbalance together with voltage status and contactor behavior. If the result remains ambiguous, collect event data across several start-stop cycles before changing protection logic.

Copy and Paste Examples

Use the following baseline template to test the Three-Phase Phase-Loss Detection Planner endpoint quickly. Replace sample values with your production-like payload.

Input Template

Sample input for Three-Phase Phase-Loss Detection Planner

Operation Checklist

- Average-versus-minimum phase-current comparison
- Current-loss gap derivation against a detection threshold
- Lowest-phase and utilization reporting for detection planning

Expected Output Shape

Deterministic output report for Three-Phase Phase-Loss Detection Planner

Frequently Asked Questions

What is the main purpose of Three-Phase Phase-Loss Detection Planner?

Estimate phase-loss margin from current asymmetry, compare it against a detection threshold, and highlight the lowest-current phase.

What input should I provide?

Provide clean source data that matches the operation you select. Typical operations include: Average-versus-minimum phase-current comparison, Current-loss gap derivation against a detection threshold, Lowest-phase and utilization reporting for detection planning.

What errors should I expect?

Most failures come from malformed input, type mismatches, or rule conflicts. Common patterns: Normal low-load imbalance is treated as a missing phase event, Thresholds are copied from another feeder with different motor or load behavior, One weak current channel drives the decision without checking measurement health.

How should I use this tool in production workflows?

Treat output as a deterministic validation step and pair it with test fixtures. Best practices: Tune thresholds using real normal-operation imbalance data, Compare the weakest phase against both average current and feeder rating, Pair current-based detection with voltage or breaker status when the consequence of a miss is high.

Need hands-on validation? Open the live tool.