From Staking Sheet to GIS + Jargon

11 min · difficulty 3/10

Five steps of a feeder extension are shuffled on the table: construction, staking, GIS update, work order, as-built. A crew is ready to roll trucks. Before reading on, put them in order and name the one step that has to happen first, before anyone touches a pole. Most newcomers reach for the work order or jump straight to construction. The correct first step is staking, and the order it sits in tells you how every distribution job actually moves.

A job runs as a loop. Staking comes first: a planner walks or models the route and marks where poles, transformers, and equipment go, producing a staking sheet with locations, framing, and a material list. That feeds the work order, the authorization and bill of material that releases the job and the crew. Then construction builds it. When the crew is done, they record what they actually set, the as-built, because field reality never matches the plan exactly. Finally the as-built is captured into GIS, the geographic system of record, so the company map agrees with the poles standing in the ground. The as-built into GIS is the last step, and skipping it leaves the map lying about the system.

From staking sheet to GIS: the work-order loop A left-to-right workflow ribbon of five stages, each a labeled box with a one-line description, connected by action-orange arrows: Staking (engineer marks the design in the field) feeds Work Order (the job is issued to the crew), which feeds Construction (the crew builds it), which feeds As-Built (field captures what was actually built), which feeds GIS (the map of record is updated). A feedback arrow loops from GIS back to Staking, labeled as-built updates the map of record, showing that the next design starts from a current map. From staking sheet to GIS the work-order loop that keeps the map true Staking engineer marks the design in the field Work Order job issued to the construction crew Construction crew sets poles and strings the line As-Built crew records what was really built GIS map of record is updated as-built updates the map of record
A construction job flows from staking to work order to construction to as-built, and the as-built loops back into GIS so the map of record stays true.

The reason the loop matters is that everyone downstream trusts GIS. The next planner stakes the next job off that map, the operator switches off it during an outage, and the engineer pulls loads from it. If the as-built never closes the loop, every later decision is made against a map that does not match the field. That is how a crew gets sent to open a switch that was moved two spans over and never recorded.

The same job is full of field jargon that gates the conversation, so learn the words. A riser is where underground cable transitions up a pole to the overhead line. A getaway is the first cable section leaving a substation or other source. N.O. marks a normally-open switch, the tie point held open until someone needs it. On the equipment side, LTC is a Load Tap Changer, the mechanism that shifts a transformer tap under load to hold voltage. On the buying side, the RFQ (Request for Quote) goes only to suppliers on the AVL (Approved Vendor List), and a big unit usually ships only after it passes a FAT (Factory Acceptance Test) at the plant. Miss one of these and you misread the print or the purchase order.

Reading a single-line diagram is the first step to writing a defensible RFQ. DistroForge report editions apply that same fluency to real bid packages: supplier capacity, lead times, and spec language that survives an OEM’s substitution clause.

Question 1 of 4

A new feeder extension has to be built. Which step comes LAST, the one that closes the loop so the map matches reality?

Educational material only. This is not engineering, safety, or procurement advice. Confirm any value against manufacturer documentation and a licensed professional before specifying equipment.