Extreme Networks Logo

Facility Communications Procurement Checklist: From Southwire Cable to Cordless Handsets

Who This Checklist Is For

If you're outfitting a facility with structured cabling and an office phone system at the same time—or replacing both—this is for you. I run quality and brand compliance for a communications infrastructure firm. Roughly 180 equipment orders pass my desk every month. In 2024, I rejected about 12% of first deliveries because the spec sheet didn't match what showed up on the dock.

The list below has seven steps. It covers Southwire cable procurement, CAGE code verification, SIMpull aluminum specs, cordless phone selection, and the lock-reset procedures that facilities teams always seem to figure out at 5 p.m. on a Friday. Work through them in order the first time. After that, pull individual steps as needed.

Step 1: Lock the Scope Before You Request Quotes

Most procurement mistakes happen before the first phone call. Write down what you're actually buying in plain terms: how many runs, what cable types, what handset count, what mounting hardware. Then read it back to yourself as if you were the vendor.

I said "as soon as possible" on a cable order last year. The vendor heard "whenever convenient." Result: a two-week gap I didn't plan for and a crew standing around. (Note to self: never use vague timing language in a PO again.)

Your scope doc should list:

  • Cable types and lengths, down to the foot
  • Phone handset models and quantities (cordless and corded)
  • Any specialty items, like clear phone enclosures for industrial areas
  • Installation labor and who owns it
  • Documentation requirements (CAGE code, spec sheets, test reports)

If it's not on that list, it doesn't exist. That's harsh, but it saves arguments.

Step 2: Verify the Southwire CAGE Code and Compliance File

The CAGE code is a five-character identifier used by government and defense buyers to link a product to a specific supplier. Southwire's CAGE code matters most when you're buying through a GSA schedule or a federal contract. If you haven't verified it, you can't claim compliance.

We didn't have a formal verification step in 2022. Cost us when an auditor flagged three POs that referenced a distributor's code instead of the manufacturer's. The fix was one page—a simple checklist—but the audit delay ran six weeks.

Here's what to keep in the compliance file:

  • The manufacturer's CAGE code, printed on the PO or attached as a screenshot
  • The distributor's authorization letter (current year)
  • Product spec sheets with revision dates
  • Country of origin, if the contract requires it

Honestly, I'm not sure why some distributors still send CAGE codes that don't match the manufacturer's records. My best guess is they're pulling from an old database and nobody's checked in years. Either way, verify—don't assume.

Step 3: Spec Southwire SIMpull Aluminum With the Right Tolerances

SIMpull aluminum is a different animal from copper. The insulation is engineered for pulling without lubricant, which is a real advantage—but it also means your installation crew needs the right equipment. If they're set up for copper, you'll hear about it on day one.

When you spec SIMpull aluminum, nail down:

  • Conductor size and stranding
  • Insulation thickness and temperature rating
  • Pulling tension limits (they're lower than copper)
  • Bend radius, especially in tight conduit

In a blind test with our install team, we ran the same conduit path with copper and aluminum SIMpull. About 70% identified the aluminum run as "cleaner to pull" without knowing which was which. The cost difference was roughly 30% per foot. On a 2,000-foot run, that's real money—but only if your crew knows how to handle it.

This was accurate as of Q4 2024. Material prices move, so verify current rates before you budget.

Step 4: Match the Cable to Your Phone System

Structured cabling and phone systems aren't the same thing. If you're running new cable for voice, you need to know whether the system is analog, digital, or VoIP. Each one has different cable requirements, and getting it wrong means re-pulling.

For most modern office deployments, Cat5e or Cat6 handles both voice and data. But if you're supporting legacy analog phones—or clear phone models that use standard analog lines—you may want to keep a few runs of Cat3 on the plan. It's cheap insurance.

Check with your phone system vendor before you finalize the cable schedule. I've seen two projects where the cabling was ordered before the phone system was selected. Both ended with change orders. (Ugh, again.)

Step 5: Vet Cordless and Clear Phone Handsets

Cordless phones in a B2B setting are different from what you'd buy at a retail store. You're looking for DECT or similar enterprise-grade systems, not consumer handsets. Range, battery life, and security protocols all matter more when you're deploying 50+ units across a warehouse or office floor.

Clear phone enclosures are a specialty item. They're used in industrial settings, clean rooms, or anywhere you need to see the internal components at a glance. If you need them, order early—lead times run longer than standard handsets, and return policies are usually stricter.

What to check before you buy:

  • DECT certification (or equivalent)
  • Battery life under real-world conditions, not datasheet conditions
  • Compatibility with your PBX or VoIP platform
  • Warranty terms and replacement lead times

To be fair, some facilities teams skip the vetting and buy whatever's on the approved list. That works until it doesn't. Budgets are real, but a handset that drops calls in the warehouse is a $200 paperweight.

Step 6: Write a Reset Procedure for Locked Phones

Someone will lock a phone. Probably during a shift change, probably when the IT person is at lunch. If you don't have a documented procedure for how to reset a phone that is locked, you'll be improvising.

For most enterprise cordless systems, the reset is a combination of:

  1. Power cycle the base station
  2. Reset the handset to factory defaults (if the vendor allows it)
  3. Re-pair the handset to the base
  4. Verify the extension assignment

Write this down, print it, and tape it inside the phone closet. Include the vendor's support number and your account number. The first time a locked phone costs you a half-day of downtime, you'll understand why.

I learned this in 2023, after a warehouse supervisor locked three handsets in one morning. We didn't have a written procedure. The fix took 20 minutes once we found the manual. The downtime cost was closer to $4,000 in lost picking time.

Step 7: Run Acceptance Checks and Archive the File

When the delivery arrives, don't sign for it until you've done a visual and documentation check. I'm not talking about opening every box—that's not realistic—but you should verify:

  • Part numbers match the PO
  • CAGE code documentation is present
  • Spec sheets match the revision you approved
  • Quantities match the packing slip
  • No visible damage to cable reels or handset packaging

Then archive the whole file—PO, compliance docs, spec sheets, acceptance notes—in a folder that's easy to find. You'll need it when the next audit hits or when a warranty claim comes up. Looking back, I should have started this archive two years earlier. But given how informal our process was, I didn't know what I didn't know.

Common Mistakes

A few things I see repeatedly:

  • Mixing up distributor and manufacturer codes. They're not interchangeable, and auditors notice.
  • Specifying SIMpull aluminum without checking the pulling equipment. The cable is fine; the crew's setup might not be.
  • Buying cordless phones before the phone system is selected. You'll pay for it in change orders.
  • No written reset procedure. Every locked phone becomes an emergency when it doesn't have to be.
  • Archiving after the project closes. Archive during, not after. Audit requests don't wait for you to be ready.

None of these are complicated. They just require someone to write it down and check it twice. That's the whole job, honestly.

Leave a Reply

Your email address will not be published. Required fields are marked *