The Pemutus field — the single-choice that records whether a pole carries an LBS, Recloser, CO, SSO, or nothing at all — is the field that determines how fast a fault response crew can work.
Without that field populated consistently across every No Tiang in the network, a dispatcher working a feeder isolation sequence is flying partially blind. They know where the fault is. They may not know which upstream pole has a working LBS in the CLOSE position that can sectionalize the load.
When the Register Doesn't Match the Field
Medium voltage pole inventories fail in predictable ways. The initial survey logs the obvious: pole type, height, location. Then a recloser gets installed on a pole that was previously bare, and nobody updates the register. Or a pole with KONDISI TIANG: MIRING gets flagged and then quietly forgotten because the work order to straighten it stayed in someone's queue too long. By the third revision cycle, the physical network and the documented network have diverged enough that the register is no longer a reliable operational reference.
The specific damage from this divergence is asymmetric — it doesn't show up during normal operations. It surfaces during faults, during storm response, during the two-hour window when a crew needs to know exactly what switching options exist on feeder K-17 between pole TM-SRG-089 and the substation. That's when a register with six months of unlogged changes becomes a liability.
The Survey Tiang Ke field is the correction mechanism — logging iteration 1, 2, 3, or 4 against each pole record forces the explicit acknowledgment of when each entry was last verified. A pole still sitting at Survey Ke 1 while the rest of the network is on Ke 3 is a visible data quality problem, not a hidden one.
Three Fields That Define Operational Intelligence
Kode Konstruksi (1B through 14B) is not an administrative tag. Each construction code maps to a specific pole rigging standard that determines mechanical load limits, crossarm configuration, and the hardware spec for conductor attachment. When a field crew is doing emergency work after a tree-strike and needs to know whether the pole they're working on can carry a temporary TWISTED conductor bypass, the construction code is the first thing they check. Absent that information, they're guessing at structural margins.
Tkt 1 / Tkt 2 / Tkt 3 Luas Penampang — the cross-sectional area in mm² per conductor tier — determines continuous ampacity. A 70mm² A3C on the main run feeding a high-load rayon and a 150mm² A3C are operationally different during peak demand periods. An asset register that collapses all conductor information into a generic "overhead line" label has lost the engineering data that matters most for capacity planning.
The dual coordinate capture — GPS Online field plus text Offline (Lat,Lon) — is field-reality design. Surveyors working in areas with unreliable network coverage document offline coordinates manually and reconcile them later. Relying only on live GPS would leave gaps in the register for exactly the remote poles that are hardest to reach when they eventually fail.
The Pole That Exists Off the Map
Rayon Serang, afternoon. Feeder fault. Petugas 1 is tasked with confirming the LBS position on a pole flagged as carrying a motorized LBS.
The record loads: Jenis Tiang TIANGTM, Tinggi Tiang 12 meters, Kode Konstruksi 7B, Kondisi Tiang BAIK. LBS: Ada. Nama LBS populated. No Seri LBS populated. Jenis LBS: MOTORIZE. Posisi Switch LBS: Close. Kondisi LBS: BAIK. Photo LBS present.
The surveyor who last ran Survey Ke 2 logged everything. Petugas 1 has a full picture of what they're walking up to before the truck turns off the highway. The LBS is in the register as motorized and in the closed position — the dispatcher has already issued the remote open command from the control room, and Petugas 1 is there to visually confirm execution.
That confirmation is only possible because someone filled in Jenis LBS correctly during the last survey cycle.