New electric service: request to energized meter

Interviewer: Before we start — quick heads up, I'm recording this, and I've got Sapeum open alongside me, so it's drawing the process flow live on screen as you talk me through it. We're just capturing how a new service connection works today. That okay?

Coordinator: Yeah, that's fine. Where do you want me to start?

Interviewer: Right at the top — what kicks one of these off?

Coordinator: Somebody needs power where there isn't any. A builder putting up a house, a developer with a strip mall, sometimes the electrician calling for the homeowner. They request new service through our portal, or they call in, or the builder drops paperwork at the counter. If it's paper or phone, somebody on my side keys it into the system by hand.

Interviewer: And what do you need from them first?

Coordinator: The site and the load — where it is, when they need power on, and the electrical side: how big a service, what voltage, single- or three-phase, where the panel and meter sit. That last bit matters more than people think — it drives where we have to bring the line.

Interviewer: Does every request go down the same path?

Coordinator: No, and that's the first big fork. A standard residential service is templated, it moves fast. But commercial or industrial — a warehouse, a manufacturing site — needs an engineering load study first, validating the connected load and demand against what the local circuit can carry. Residential skips that entirely.

Interviewer: So commercial goes to engineering. Then what?

Coordinator: Somebody goes out for a site visit — where's the nearest line, where's the meter going, how far to our facilities. You can't design it from a desk. And out of that comes the make-or-break decision: can we reach this site with what's already in the ground or on the poles? If existing facilities are right there, it's a simple service drop or lateral. If not, we're talking a line extension, maybe a new transformer, maybe setting a pole and running primary. Completely different job, cost, and timeline.

Interviewer: And that drives what it costs the customer.

Coordinator: Exactly. We price the job and figure out cost responsibility. A utility allowance covers part; whatever's beyond it, the customer pays — the contribution-in-aid-of-construction, the CIAC. A hookup near existing facilities might be little or nothing. A long line extension out to nowhere can be a big CIAC bill, and that's where I get the gasps.

Interviewer: What happens when they see that number?

Coordinator: We send the agreement and deposit invoice, they sign and pay. But sometimes they balk — too high, so they relocate the building, shrink the service, or we rework the design to bring it down. Sometimes the job dies right there. Until that's signed and the deposit's in, nothing moves.

Interviewer: Let me press on that — chasing all this across engineering, the customer, the crews. How much of your day is that?

Coordinator: Honestly, most of it. I'm the human glue. Every job's stuck in some stage — waiting on a study, a signature, a crew date — and there's no single place that shows me all of it. I'm pinging engineering, calling the builder, checking a crew calendar, re-keying the same details between billing, the design tools, and GIS, because they don't talk. If our work management — we run Maximo — tied the design, crew scheduling, and status into one view, I wouldn't be shepherding two hundred jobs through email. That's the piece that's killing me.

Interviewer: Okay. The customer's signed and paid. What's next?

Coordinator: Permits and the municipality. The electrician pulls the electrical permit, and we coordinate road crossings, easements, municipal work. It runs alongside everything else but gates construction — I can't put a crew out until permitting's lined up. Once it's paid and permitted, I schedule the line crew for whatever the design called for — the extension, the transformer, the pole. Materials get staged, the crew builds it. A simple hookup is barely anything; an extension is the big lift.

Interviewer: Before the meter goes on, is there a sign-off?

Coordinator: Yes — the electrical inspection. The AHJ inspector checks the customer's wiring and panel and issues the clearance we need to connect. If it fails — wrong panel, a grounding issue — they fix it and call the inspector back. Re-inspect. That loop costs days and holds up the meter set, which makes the customer think we're the holdup when it's their side.

Interviewer: And once it passes?

Coordinator: The crew makes the final connection — the drop or lateral to the panel — and sets the meter. Then we energize. Power's flowing, service is live.

Interviewer: That's the finish line?

Coordinator: For the customer, basically. But not for me — actually, let me back up, because I made the meter set sound like the last thing and it isn't. After we energize, billing has to activate the account — link it to the meter and the rate so usage gets billed. Miss that and somebody's pulling power and not getting charged. The meter being live and the account being live are two different things.

Interviewer: And is there anything after the account's set up?

Coordinator: The records. Field as-builts come back into our mapping — the new transformer, line, pole, service point. And — wait, let me correct something I said earlier. I called the re-keying between billing and GIS just an annoyance, but it's worse: when as-builts get entered wrong or late, the map doesn't match what's in the ground, and the next crew plans against bad data. That's not paperwork, it's a safety and rework problem. A lot of the duplicate entry would go away if the design, the CIS — we're on Oracle's CC&B — and ArcGIS shared one service-point record instead of three.

Interviewer: Last question — what do people get wrong about this?

Coordinator: They think it's like flipping a switch — power's already there, we just come turn it on. They've no idea there might be a transformer to size, a line to extend, a pole to set, a permit, an inspection, and a cost conversation in between — and that the long pole isn't the wiring, it's the coordination. Every job is a little construction project handed across four or five teams that don't share a system, and somebody — me — carries it the whole way by hand. Get the design and cost call right early and the rest flows. Get it wrong and you're back at square one after the customer's already counting on a date. That's the part nobody sees.

Interviewer: That's a great place to wrap. Thanks for walking me through it.

Coordinator: Anytime. Seeing it laid out like that, the spots where I'm the glue are pretty obvious.