The EXFO Fiber Test Equipment Procurement Checklist: FTB-1, C300, and 6300

I've been a procurement manager at a 340-person fiber-optic contracting company for eight years. I manage roughly $180,000 a year in test-equipment spend, and I've negotiated agreements with more than a dozen suppliers. This article is the checklist I use when someone puts EXFO fiber test gear on a requisition and asks me to sign.

It's a six-step process. No fluff. Use it in order.

Step 1: Start with the cable plant, not the product name

'We need an EXFO FTB-1' is not a requirement. It's a guess. My first job is to get the requester to describe the network, not the tool.

I ask for link lengths, fiber types, wavelength plans, and what measurements matter. A crew that installs 10 km metro rings does not need the same OTDR module as a group testing 120 km long-haul spans. Same platform, different cost profile.

In Q2 2024, a team asked for an upgraded module because they wanted 'better characterization.' Their typical span was 28 km. The existing module handled it. We documented the actual span lengths, and the upgrade disappeared from the budget. The surprise wasn't the price difference. It was how much money we saved simply by writing down real distances.

Step 2: Build a TCO model before you compare prices

Sticker price is not cost. I compare total cost of ownership, and I do it before I call a supplier.

When I audited our 2023 spending, I found that 18% of equipment costs came from things that weren't in the original quote. Calibration surcharges. Overnight shipping. 'Necessary' software options. That's exactly why I use a spreadsheet with these rows:

• Purchase price
• Modules and accessories required for the actual job
• Calibration and repair cost over five years
• Technician training time
• Software updates and licenses
• Warranty extensions
• Resale or trade-in value
• Cost of a failed test in the field

That last row is the one people ignore. We once bought a budget OTDR that worked fine in the office and then produced inconsistent traces on a dirty connector in the field. Redo cost us three days and a client conversation nobody wants. The cheap unit ended up being the expensive one. (Which, honestly, I should have predicted.)

In Q2 2024, a vendor quoted $6,200 for a module. Another quoted $5,900. The second seemed like the better deal until I added the calibration plan: the $5,900 module needed a $1,100 calibration package before it matched the first vendor's scope. That $300 saving became an $800 overrun.

According to EXFO's product documentation on exfo.com, the FTB-1 is designed as a modular field platform. I read that as a warning: the chassis price is only the beginning. The total cost lives in the modules and service plan.

Step 3: Compare the whole platform, not just the headline unit

The FTB-1 is often the first line on a purchase request. Fine. But the final cost is in the ecosystem around it. If the job requires the C300 or a 6300-series option, those are part of the same decision. Do not approve a chassis and treat the rest as a surprise.

The C300 and 6300-series options are not necessarily interchangeable. They answer different test questions. That's why the Step 1 requirements matter.

I separate line items into two buckets:

• Mandatory: needed to perform the tests described in Step 1
• Deferred: useful, but not needed this quarter

The deferred list goes into the quote notes. If someone asks for the same item next quarter, we budget for it. This keeps the scope honest and prevents the 'while we're buying it' syndrome.

Step 4: Count setup and integration time

Test equipment is not plug-and-play, even when the brochure says it is. When we added the FTB-1 to our workflow, I budgeted two days of setup and training. It was more like two days before the units were configured correctly, and three weeks before the field techs stopped double-checking every setting.

The hidden cost was configuration time—not the tool itself. Things like the correct launch fiber for a specific span, the right averaging time, and the right trace settings. (Not that the manual helped.)

If you can, send one technician to a training session before final approval. That person becomes the internal expert and reduces the cost of every future mistake. It's a small line item that saves a large amount of time later.

Step 5: Do not turn 'EXFO Networks vs Cisco' into a false choice

I've sat in procurement meetings where someone described the decision as 'EXFO Networks vs Cisco.' That comparison doesn't hold up. Cisco builds network infrastructure. EXFO's testing and service assurance tools verify that infrastructure. In many projects, you need both.

Putting them side by side as substitutes creates a confusing RFQ and vendor responses that are impossible to compare. Instead, define the role each purchase plays:

• Infrastructure: switches, routers, optical transport gear (Cisco and others)
• Validation: test equipment, monitoring, troubleshooting, assurance (EXFO and others)

Each row gets its own TCO analysis. Don't let a good price on a switch justify skipping the test tools that prove the network meets its SLA. We tried that once, just mentally, and the thought of explaining to a client why we couldn't verify latency was enough to kill the idea.

I get why people want a one-line answer. Procurement loves a side-by-side comparison. But a false comparison is worse than no comparison.

Step 6: Write the 'what if we don't buy it' paragraph

Before I approve any equipment purchase, I write one paragraph: what happens if we don't buy this? It forces the request into a real cost context.

For example, 'We can't bid on the countywide fiber project because the RFP requires iOLM reporting' is a concrete argument. 'It would be nice to have better visibility' is not. If the paragraph is vague, the purchase goes back to the requester.

For a $4,200 annual contract, I once approved a purchase based on one sentence: 'Without this, we cannot generate the test reports the contract requires.' That sentence was enough. The request didn't need charts.

Common mistakes I still see

A few things keep showing up in budget reviews:

• Ignoring calibration intervals. A calibration fee is not a one-time cost; it's a recurring one.
• Replacing connectors, boots, and launch cables more often than expected. Add a spares line.
• Forgetting software license renewals. Some quotes look cheaper until you see the annual fee.
• Assuming 'same spec' from a different vendor means identical field results. It does not.

I learned never to assume the specs represent the real-world use case. A dynamic range number says nothing about how the unit handles a dirty connector or a particular fiber type. The only way to know is to test with your own typical fiber, before you sign.

The short version

Buy the capability you need, calculate total cost, compare the full platform, count training time, separate infrastructure from validation, and write down the consequence of not buying. That's the checklist. Pricing and package details change, so verify current options and calibration plans on EXFO's official site before you present the final number.

I still second-guess big purchases. That's healthy. But after nine years of tracking invoices and field errors, I've learned that the most expensive words in procurement are 'let's just get it.' Run the checklist first. You can thank me later. (Or at least buy the good launch cables.)