Most panel shops treat each custom build as a unique event. The order comes in, the panel gets built, the panel ships, the order closes. If the same customer comes back a year later wanting “the same panel as last time,” the shop pulls out the old invoice, looks at the BOM, and starts quoting from scratch. The wiring choices that the original builder made get re-made by a different builder. The component substitutions that happened because of supply-chain availability get re-decided. The result is two panels that are nominally the same but functionally different in ways the customer will discover months later, on a service call.
We don’t work that way. Every custom panel we ship is assigned a SKU, and that SKU stays in our system as long as the customer is a customer. The SKU isn’t a catalog number — it’s a permanent design record that captures everything required to reproduce that panel exactly. The practical consequence: if you order the same panel five years from now, it leaves our shop wired identically to the one you ordered today.
How a SKU is born
The SKU lifecycle on a typical custom build:
- Spec intake. The drawing, the bill of materials, the operational requirements, the environmental constraints all get logged against the project record.
- Engineering review. Our engineers cross-check the spec against the UL 508A envelope, code requirements, and any documented gotchas we’ve encountered with the proposed component mix. Substitutions surface here, before the build starts.
- CAD and BOM lock. Once the design is approved, the CAD drawings and the BOM are versioned and locked. Any change after this point creates a new revision against the same SKU — the original is preserved.
- Production. The panel is built by a single builder, against the locked CAD, with full torque-record and continuity-test logging.
- Burn-in. 48 hours of full-load testing in our lab. Results get tagged to the panel’s serial number, which is in turn tagged to the SKU.
- SKU finalization. Once the panel ships, the SKU record is considered closed for that build but open for future reorders. Anything that we’d want to know if you called back in five years is in that record.
Why this matters at scale
The single-panel benefit of an SKU system is obvious: when you reorder, you get the same panel. The benefits compound dramatically as panel counts grow.
Parts inventory
A facility manager running fifteen buildings with mixed-vintage BAS panels typically maintains a parts inventory measured in linear feet of shelving. Different contactors, different wire colors, different terminal-block styles, different I/O modules per panel generation. A service tech has to identify which panel they’re at before they can even pull the right spare.
The same facility with SKU-standardized panels needs one shelf. The contactor that fits panel 1 fits panel 200. The same goes for fuses, wire kits, terminal blocks, and the rest. The parts inventory shrinks by an order of magnitude. The bigger surprise is what happens to the service team: the techs don’t have to identify the panel generation before they start work. They already know what’s inside.
Field-tech training
The training cost on a field tech is the largest single cost of running a service operation. If every panel is different, training never finishes — every new generation of panels requires a new round of familiarization. If every panel is the same SKU family, training scales: a tech trained on panel 1 can service panel 200 the same day.
We’ve watched customers cut their training overhead by more than half once they had two years of SKU-standardized installs on the books.
Service speed
Time to resolution on a service call drops as a function of how many prior calls have been logged against the same SKU. The institutional knowledge accumulates. Diagnostic patterns get documented. Common failure modes get cataloged. By the time a SKU is in its fifth year of deployment, the average service call is resolved in a fraction of the time it took on year one.
For facility managers running multi-site portfolios, this is the biggest single operational lever.
A twelve-facility case study
A Fortune 500 customer of ours runs twelve manufacturing facilities across the central US. They were on their third major BAS retrofit when they engaged us. The first two retrofits had been field-built at each site by different local contractors. By the third retrofit, the company had:
- 47 different controller part numbers in inventory (across three generations and four vendors)
- 9 different panel-key patterns across the twelve sites
- A training program for service techs that ran six weeks per tech and still produced uneven results
- No documentation standard — each site’s panels had been documented (or not documented) by whoever built them
We retrofit the third building on a single SKU. We then deployed the same SKU across all twelve sites over the following 18 months. By the end of the deployment:
- One controller part number, one I/O module part number, one contactor part number, across all twelve sites
- One key pattern across all twelve sites
- A training program of two weeks per tech, with consistent outcomes
- One documentation standard, maintained by us against the SKU record
The TCO numbers came in on the spreadsheet over the next two years. The short version: parts inventory cost down 78%, service-call duration down 51%, training overhead down 64%. None of that came from a technology change. It came from the panels being the same panels.
What we keep on file
The SKU record is what makes the reorder math work. The contents of a typical SKU record include:
- The locked CAD drawings (as-designed and as-built, both versioned)
- The bill of materials with vendor part numbers, line by line
- Substitution history (if a component was unavailable and a replacement was approved, that decision is documented)
- Wiring color standards and terminal-block layouts as a tabular spec
- Torque records from production, per terminal
- Continuity test results
- 48-hour burn-in test results, including any anomalies caught and resolved
- Operational notes from service calls (with customer consent), so patterns surface across the install base
- The original spec source — typically the engineer or contractor who authored the build
If we get hit by a bus, that record is still there. If you call us ten years from now, it’s still there. The SKU outlives any individual employee on either side of the relationship.
What this costs versus what it returns
The honest answer is that maintaining a SKU system is expensive at the shop level. We pay engineers to do design reviews that other shops skip. We pay for the document-management overhead. The 48-hour burn-in cycle alone adds two days to every panel’s lead time.
The return is that our customers don’t pay those costs in the field — they don’t pay them in surprise service callbacks, in parts inventory, in re-engineering work three years later. The cost moves from the field side to the shop side, where it’s much cheaper to absorb, and the customer captures the difference in lower TCO over the asset life.
When you’re ready to start a SKU on a project, request a quote and we’ll walk through the design intake.