Distribution Pole Surveys Are an Engineering Exercise, Not a Census
The difference between a pole count and a pole survey is the difference between knowing you have 4,200 poles in the Jabar network and knowing which of them are concrete, which are wood, which are carrying more SR service pulls than their engineering specifications support, and which have construction codes that put them in the wrong line class for the conductor size they're currently running. Only one of those datasets supports load planning, maintenance scheduling, and grid reinforcement proposals.
The Record That Captures What Matters at Each Pole
No Tiang — pole number — and Dari Sumber No Tiang — source pole number — together establish the network topology chain. Every pole in a radial LV network is downstream from something. Capturing both the pole's own identifier and the pole it's fed from means each record carries its network position, not just its physical attributes. When a fault is isolated to a specific section of feeder, the topology chain tells you how many poles — and how many service connections — are affected, without reconstructing the network from a separate map.
Jumlah tarikan SR — number of SR service pulls — is the load accumulation field. An SR pull is a service connection running from the pole to a customer's premises. A pole engineered for eight SR pulls that's now carrying seventeen is a violation of the design standard, regardless of whether it's showing visible signs of stress. That number, recorded at survey and updated when new connections are added, is what makes the network's actual load distribution visible to planning engineers. Without it, load calculations are based on connection counts from billing records, which lag behind physical reality by months.
Jenis Tiang (pole material type) and Tipe Tiang (pole configuration type) define what you're actually working with. Concrete and wood poles have fundamentally different inspection frequencies, replacement criteria, and climbing requirements. A wooden pole in a coastal area needs a condition inspection cycle that a concrete pole in the same location doesn't require with the same urgency. Tracking these as separate structured fields rather than a combined description field allows the maintenance schedule to be generated from the database rather than from someone's institutional knowledge of the network.
Kode Konstruksi — construction code — is the engineering specification that governs what the pole is designed to carry: which conductor type, which span length, which loading class. When a construction code doesn't match the actual conductor and span in place, you have an as-built deviation that needs engineering review. That deviation is invisible without the construction code on the record.
Kondisi Tiang — pole condition — is the field inspection assessment. Structural integrity of the pole itself: plumb, cracked, leaning, corroded at the ground line, split at a former climbing spike. This isn't a technical spec — it's the surveyor's direct observation, captured at the time of the visit, before memory degrades and impressions blur.
Jurusan, GPS, and Two Surveyors
Jumlah Jurusan (number of directions the pole feeds) and Nama Jurusan (direction names) capture the topological branching at each pole. A pole that feeds a single downstream span is architecturally different from a pole at a junction that feeds three separate residential lanes. The junction pole carries load from multiple branches and failure at that point has wider outage consequences. Recording the number and names of directions makes junction poles immediately identifiable in the dataset.
Online (GPS) and Offline (Lat,Lon) provide the coordinate capture with a fallback. In dense built-up areas, GPS acquisition can be unreliable under tree cover or between tall buildings. The offline text field allows manual coordinate entry in formats that can be geocoded later, ensuring no pole survey record comes back without a spatial anchor.
Surveyor 1 and Surveyor 2 close the record with named accountability. A pole survey completed by two named individuals is a verifiable field inspection. A record without names is an unverifiable data entry.