Services API · New 2026-05-03
The third sibling domain alongside overhead and underground. A typed Universal Service Model, five analysis pillars, calculator + compliance check on each, and a clean handoff into the upstream transformer's thermal model. Voltage drop to motor-start flicker to phase balancing to route optimization, all on one shape.
voltage drop · flicker · transformer load · phase balance · routing
service-side reference standards
calculator + compliance check per pillar
sibling to UPM + UVM
Five pillars
Each pillar lands as a standalone calculator + a per-utility compliance check. Use them inside the chat agent, inside QA/QC bulk review, or via direct HTTP from your own tooling.
Per-segment + network-traversal voltage drop on a service-drop tree. Range A / Range B / out-of-range classification + per-service drop %. Catches layouts that need conductor upsizing before a customer ever calls.
ΔV/V at the bus from locked-rotor inrush + system short-circuit MVA. Looked up against the IEEE 1453 / GE flicker curve by repetition rate. Imperceptible / borderline / objectionable classifier with mitigation hints.
Sums the network's service-point loads, hands off to the upstream transformer's thermal model. Returns hottest-spot temperature, IEEE C57.91 loading condition tier, and the Arrhenius F_AA loss-of-life accelerator.
Per-phase load summation + NEMA % unbalance. Greedy reassignment optimizer that suggests service-to-leg moves to flatten an imbalanced secondary. Caller's network is never mutated; output is a reviewed plan.
Minimum-spanning-tree route from a transformer through every service point with lat/lon. Optionally voltage-drop-checked on the recommended topology so downstream conductor upsizing decisions are made from real numbers.
What sets it apart
A typed, normalized representation of services + secondary segments + transformer-as-source. Sibling to the Universal Pole Model (overhead) and Universal Vault Model (underground). One shape across every service-side analyzer.
Each pillar exposes two endpoints: a pure-physics calculator (no rule lookup, just engineering inputs) and a compliance check (joins utility-staged limits with regulatory floors). Use the calculators standalone in your own tools; the checks land in QA/QC.
When no utility-specific rule is staged, every pillar falls back to the published regulatory floor — ANSI C84.1 Range A 5%, IEC 61000-3-7 Pst 1.0 / Plt 0.65, NEMA MG 1 3% three-phase, IEEE C57.91 110°C hottest-spot. Useful out of the box, tighter once a utility ingest stages overrides.
A new service_voltage_drop_limits rule category lets utilities stage their own (service class × voltage × phase → max drop %) tables. The tightest match between staged rule and regulatory floor governs.
A ServiceNetworkRef on a Universal Pole Model links the pole-side transformer to the downstream secondary network. Engineers walking from a pole into its services keep full context.
Every endpoint is reachable over HTTPS via OIDC token. Same authentication pattern as the rest of the platform's analyzer surfaces — drop into an agent or call from your own automation without bespoke wiring.
Why it matters
Service-drop analysis sits between distribution engineering and customer experience — too far downstream for most pole-loading tools, too pole-anchored for a load-flow simulator. Result: utilities run voltage-drop math in spreadsheets, calibrate flicker on the back of envelopes, and rebalance phases by gut. Every misjudgment costs a customer call.
A 2026-05-03 capability-discovery audit across three real utility corpora (one IOU, one cooperative federal-bulletin baseline, one Gulf-coast IOU) surfaced service-side analysis as the largest universal cross-utility gap by combined rule count. This is the platform-level answer.
Standards covered
Pad-mount with a residential block? A commercial drop with a flicker complaint? An imbalanced secondary you've been meaning to rebalance? We'll run all five pillars on it in fifteen minutes.