Start: Tell Us About the Route You're Worried About

• Which fiber route or circuit ID are we discussing (site-to-site or coastal route name)?
• What is the primary business driver for this project: capacity exhaustion, new DCI, cost deferral, product launch, or regulatory/maintenance reasons? Options: Capacity exhaustion (wavelengths at risk), New Data Center Interconnect (DCI), Deferring fiber build / cost reduction, End-of-life equipment replacement, Regulatory or maintenance requirement, Other
• When do you expect the route to hit critical capacity or require new per-wavelength rates (pick the nearest range)? Options: Already critical, Within 3 months, 3–6 months, 6–12 months, 12–18 months, More than 18 months
• Who will be our primary technical contact for discovery (name, role, and preferred contact method)?
• How would you describe the commercial urgency on a scale—do you need a proposal now, in weeks, months, or is this exploratory? Options: Immediate (this week), Short (within 2–4 weeks), Medium (1–3 months), Long (3–6+ months), Exploratory / no timeline yet

Are We Ignoring a Looming Capacity Cliff?

• If nothing changes, what happens when the busiest route runs out of usable wavelengths—and who inside your organization bears the consequences?
• Which per-wavelength rates are currently in production and which rates do you expect to require over the next 18 months? Options: 100G, 200G, 400G, 600G, 800G, Other / custom
• How many physical fibers and usable fiber pairs are on the route today (best estimate)? Options: 1–2 pairs, 3–6 pairs, 7–12 pairs, 13+ pairs, Unknown / need to check
• Do you have traffic growth forecasts (by customer, service, or aggregate) that drive the need? If so, how granular are they? Options: Detailed by customer, By service type only, Aggregate forecast, High-level estimate only, No formal forecast
• Which SLAs, customers, or services would be directly impacted if we delay capacity expansion?

What's Really Breaking Your Nights?

• In the last 36 months, what specific failure modes or constraints on this route caused outages, degraded throughput, or surprise rework?
• Which amplifier types and inline equipment are deployed on this route (select all that apply)? Options: EDFA, Raman, Hybrid EDFA+Raman, Optical regenerators (OEO), Line-system vendor-managed amplifier, Unknown / need inventory
• Do you observe persistent spectral issues (gain tilt, notches), high span loss, or unusual PMD/dispersion that limit reach? Options: Yes—documented and quantified, Yes—observed but not fully quantified, Occasional/route-dependent, No
• How often do you experience service-impacting amplifier or coherent transponder interoperability issues (never, rarely, frequently)? Options: Never, Rarely, Occasionally, Frequently, Unknown / not tracked
• Tell us about a recent incident on this route—what happened, what troubleshooting steps were taken, and how did it feel for the teams involved?

Under the Hood: What's Really in the Fiber Plant?

• If you listed the physical inventory for this route, how complete is it (fiber type, span lengths, amplifier models, DWDM vendor and card families)? Options: Complete and up to date, Mostly complete, some gaps, Partial inventory, No inventory / unknown
• What is the dominant fiber type and band plan on the route (select all that apply)? Options: Standard single-mode (G.652), Low-loss fiber (G.654), C-band only, C+L band, Unknown / mixed
• Do you have span loss and amplifier gain profiles available for each span (per-span dB numbers)? Options: Full per-span data available, Summary statistics only, Some spans documented, No per-span data
• Which existing DWDM line-system and transponder vendors must we interoperate with on this route (select all that apply)? Options: Vendor A, Vendor B, Vendor C, Cisco/Acme-style line systems, In-house/custom line-system, Other / legacy vendor, Unknown
• Are there single points of failure (single amplifier sites, single fiber crossing) or regulatory constraints we should know about?

What Would ‘Good’ Look Like Across Your Teams?

• When you hear 'this is good enough' for this project, what concrete outcomes are you picturing for transport, planning, procurement, and operations?
• Which internal stakeholders/teams must sign off on 'good' (select all that apply)? Options: VP Transport Network Engineering, Director of Optical Planning, NOC/Operations, Procurement, Platform/Cloud teams, Regulatory/Compliance, Finance, Other
• What measurable success signals will you use (per-wavelength throughput, error floor/BER, margin dB, reach, spectral efficiency, OpEx savings)? Options: Per-wavelength throughput, BER / FEC margins, OSNR margin (dB), Reach at target rate, Total fiber capacity increase, Operational cost reduction, Other
• How much operational risk for live upgrades is acceptable—do you prefer fully non-disruptive paths, short maintenance windows, or are outages tolerable with notification? Options: Zero traffic impact—non-disruptive only, Short scheduled windows (minutes), Limited outage allowed (<1 hour), Outages acceptable with pre-notification, Depends on customer/circuit
• Who ultimately controls the budget and commercial approval—and what internal metrics (TCO, $/bit, amortization) do they care most about?

What Have You Tried — And What Fell Short?

• Describe prior upgrade attempts, trials, or vendor evaluations on this route and the primary reason each did not meet expectations.
• Have you trialed pluggable optics-only solutions here, and if so what operational or reach limitations did you encounter? Options: Tried and failed on long-haul, Worked for metro but not long-haul, Not tried—considered, Not considered
• Did earlier attempts trigger unexpected operational tasks (manual power balancing, per-channel tuning, amplifier retuning)? Options: Yes—significant manual work, Yes—some manual steps, Minimal extra work, No unexpected work
• Were there contractual, warranty, or support issues with previous vendors that influenced your decision to pause or stop? If yes, describe.
• If you could point to one change that would have turned those attempts into successes, what would that be (technical, commercial, or process)?

How Much Risk Is Too Much When Upgrading Live Traffic?

• If we propose an in-service upgrade requiring amplifier adjustments or mid-span work, what outage or degradation threshold would you accept (if any)? Options: No degradation tolerated, Very short scheduled impact (<5 min), Planned short outage (<1 hour), Outage acceptable with mitigation plan, Depends on circuit/customer
• Do you have named owners, shifts, or a war-room process for in-service upgrades (list roles or say 'not defined')? Options: Named individuals with contact info, Roles defined but not named, Ad-hoc team assembled for upgrades, No formal ownership defined
• What rollback capabilities and physical spares must be staged before any live-route upgrade proceeds (e.g., spare amplifiers, fiber splices, transponder spares)?
• Are runbooks and rollback SLAs already documented and tested for similar upgrades? Options: Fully documented and tested, Documented but untested, Partially documented, No runbooks in place
• How do you prefer final validation after a live upgrade: automated monitoring against lab benchmarks, a lab re-run for parity, traffic acceptance window, or manual sign-off? Options: Automated monitoring vs lab benchmarks, Lab re-test and parity check, Customer traffic acceptance window, Manual engineering sign-off, Combination

How Confident Are You in Lab-to-Field Translation?

• If lab interoperability and performance tests look positive, how confident are you that those results will map to every live span on this route? Options: Very confident, Somewhat confident, Not confident, Confidence varies by span
• Do you run formal lab interoperability tests today, and if yes, what is the usual scope (single-span, multi-span, end-to-end with legacy equipment)? Options: No formal lab tests, Single-span tests, Multi-span lab tests, End-to-end with legacy equipment, Third-party lab engagements
• What pass/fail metrics do you require from lab trials (choose all that matter)? Options: BER / FEC margin, OSNR margin (dB), Throughput at target rate, Latency and jitter, Channel tilt and per-channel power, Interoperability with specific vendor features, Other
• Who from your organization signs off on lab acceptance and what approval level is required to move from pilot to production? Options: Engineering lead, Transport VP, NOC and Engineering jointly, Procurement + Engineering, Executive committee
• Are there specific lab test durations or repeatability requirements you insist on (e.g., 72-hour soak, multi-temperature, single-fiber stress)? Options: 72-hour soak, 48-hour soak, Single run sufficient, Multi-configuration tests required, Other / specify

If We Built the Ideal Plan Together, What's the Minimum Deal to Start?

• What minimum commercial and technical commitments would make you comfortable to start lab testing and a pilot deployment?
• Which contractual terms are non-negotiable for you (select all that apply)? Options: Warranty duration, Repair and RMA SLAs, Performance guarantees (per-wavelength), Price lock for X years, Buyback or upgrade path, Penalty/credits for missed milestones, Other
• Which pricing model do you prefer for multi-year wavelength growth: fixed per-wavelength, tiered volume discounts, consumption-based, subscription, or hybrid? Options: Fixed per-wavelength, Tiered volume discounts, Consumption-based billing, Subscription / term-based, Hybrid model, Open to multiple
• What technical acceptance criteria must be met in lab and pilot to trigger a go/no-go for full deployment?
• When would you want the first lab test to start if we aligned commercial and technical terms? Options: Immediately, Within 2–4 weeks, Within 1–2 months, 3 months+, Unsure
• Who needs to be present for lab acceptance testing from your side (roles or names) and who will be responsible for capturing post-test sign-off?

Start with a Quick Route Snapshot

• Which route(s) are we mapping today (route name, endpoints, and any internal route ID)?
• Which of these best describes why this route matters right now? Options: Imminent wavelength exhaustion (<18 months), New DCI project requiring 400G+/wavelength, End-of-support for current line-system, Latency-sensitive traffic shift, Other
• Who is the commercial owner and who is the technical owner for this route (names + roles)?
• What is your target decision timeline for a recommended upgrade or remediation? Options: Within 30 days, 30–90 days, 90–180 days, More than 180 days, Undecided
• Roughly how many active wavelengths are currently lit on the busiest fiber in the route? Options: 1–8, 9–16, 17–32, 33–64, 65+
• Which business outcome would make you consider this effort an immediate priority? Options: Avoid new fiber build, Enable 800G per wavelength, Deflect large capital spend, Meet latency/throughput SLAs, Other

If This Route Fails Tomorrow, What Then?

• How would you describe the worst plausible failure on this route—complete dark fiber, amplifier cascade failure, or progressive OSNR collapse? Options: Complete fiber cut/dark fiber, Amplifier/EDFA failure cascade, DWDM line-system interoperability failure, OSNR/ nonlinear performance degradation, Other
• How often have you experienced customer-impacting outages on this route in the past 24 months? Options: None, 1, 2–3, 4–6, More than 6
• When an incident happens today, what is your typical MTTR for full capacity restoration? Options: <1 hour, 1–4 hours, 4–12 hours, 12–48 hours, >48 hours
• Who must be notified/approved during a high-impact outage on this route (roles and escalation path)?
• Which single-point-of-failure do you fear most on this route (e.g., single diverse path, amplifier site, vendor lock)? Options: Single physical fiber pair, Single amplifier site, Single vendor line-system, Single NOC/operator owner, Other
• Tell us about a past outage on this route—what failed, what was the root cause, and what was the business impact?

What Secrets Does the Fiber Hide?

• How confident are you that the published fiber plant records fully reflect what’s in the ground? Options: Completely confident, Mostly confident, Some gaps, Significant unknowns, Unknown
• What is the fiber type and core specification along this route (select all that apply and provide details if mixed)? Options: ITU-T G.652 (standard SMF), G.655 (NZ-DSF), G.656/G.657 variants, Submarine-grade fiber, Mixed/varied—see notes
• How many amplifier spans are there across the longest continuous live-route segment we’ll be upgrading? Options: 0–4 spans, 5–9 spans, 10–19 spans, 20–39 spans, 40+ spans
• What is the average span length and typical per-span loss (dB/km and typical connector/splice loss)?
• Do you have recent OTDR traces, PMD/Chromatic Dispersion measurements, and per-span loss that we can review in the lab? Options: All available (OTDR, PMD/CD, per-span loss), Partial set available, Only OTDR traces, No measured data available
• Are there known plant characteristics that degrade performance (e.g., many old splices, mixed fiber types, high bend-loss segments)?
• How old is the fiber plant on average on this route and how frequently has it been repaired or re-terminated? Options: <5 years, 5–10 years, 10–20 years, 20+ years, Varies widely

Where Capacity Suddenly Stops

• If we accept one blunt truth: what's the single technical bottleneck that’s forcing you to consider replacement or upgrade today? Options: Per-wavelength rate limit (e.g., 400G cap), Channel count/full spectral occupancy, Reach limitations due to amplifiers/noise, Vendor end-of-life/end-of-support, Operational complexity
• Which DWDM line system model(s) and vendor(s) are currently in-line on this route (list model and vendor per segment)?
• What per-wavelength rates does the current line system *practically* support today (not theoretical), and at what reach? Options: Up to 100G, Up to 200G, Up to 400G, Up to 400G with severe reach limits, Other—please specify
• How many guarded/reserved channels or dark slots remain in the spectrum for growth? Options: None, 1–4, 5–12, 13–32, 32+
• What percentage of total fiber capacity do you expect to be consumed by planned growth in the next 18 months? Options: <10%, 10–25%, 26–50%, 51–75%, >75%
• Please describe any operational practices that reduce usable capacity (e.g., conservative power margins, reserved guard bands, vendor constraints).

When Line Systems and Transponders Don’t Agree

• How often do you see interoperability surprises when introducing new coherent optics into this route’s line-system? Options: Never, Rarely, Occasionally, Often, Always
• What line-system features are present that materially affect interoperability (select all that apply)? Options: ROADM (colorless/flex), Fixed-grid ROADMs, In-line DCM, Raman amplification, Hybrid amplifiers (EDFA+Raman), No ROADMs / fixed pass-through
• Do you currently run any lab or field interoperability tests with 3rd-party transponders, and what were the outcomes? Options: Regular testing with documented results, Occasional tests with mixed outcomes, One-off tests only, No interoperability tests yet
• Which amplifier vendor/models and settings (gain tilt, output power) should we expect when planning a lab simulation?
• Have you observed degradation patterns tied to spectrum location (e.g., C-band vs L-band issues, edge-channel OSNR collapse)? Options: Yes—C-band edge, Yes—L-band edge, No clear pattern, Unknown
• Share an example of an interoperability issue that cost time or capacity—what happened and how was it mitigated?

Who’s Holding the Anchors?

• Where do the biggest non-technical delays live in your process—procurement, lab approvals, maintenance windows, or organizational alignment? Options: Procurement/contracting, Lab scheduling and approvals, Maintenance window scarcity, Internal alignment across teams, Other
• Who are the decision-makers that must sign off on a lab interoperability plan and a live upgrade plan (names/roles)?
• How do you prefer risk to be framed for stakeholders—probability, monetary impact, or operational impact (select primary and secondary)? Options: Probability of failure, Monetary impact, Operational/MEF/SLA impact, Time-to-repair impact
• What internal governance or committee will approve a go/no-go for live upgrades, and how frequently do they meet? Options: Weekly, Bi-weekly, Monthly, Ad-hoc, No committee
• On a scale from 1–5, how comfortable are your NOC and field teams with rolling upgrades on live wavelengths? Options: 1 - Not comfortable, 2 - Somewhat uncomfortable, 3 - Neutral, 4 - Somewhat comfortable, 5 - Very comfortable
• Who should we list as the primary technical contact, secondary contact, and escalation contact for this engagement?

What Would Make a Live Upgrade Feel Safe?

• What is the single non-negotiable acceptance criterion that would give you confidence to allow a live upgrade on this route?
• Which of the following acceptance metrics are required post-cutover (select all required)? Options: OSNR threshold per channel, BER / FEC margin, Throughput at agreed rates, Interoperability tests passed, No customer-impact incidents during window
• How long a maintenance window do you typically allow for a live wavelength upgrade on this route? Options: <1 hour, 1–4 hours, 4–8 hours, 8–24 hours, No scheduled window—must be hot swap
• What rollback criteria would trigger immediate revert to the pre-upgrade state?
• Do you require a full lab sign-off and field dry-run before any live upgrade, or are limited field pilot sites acceptable? Options: Full lab sign-off + dry-run required, Lab sign-off sufficient, Pilot field sites acceptable, Depends on route risk
• How do you quantify acceptable operational risk for live upgrades (examples: max allowed dropouts, customer SLA degradation %)?

Let’s Capture the Data We’ll Need to Simulate Success

• Which of these artifacts can you share right now to model the route in our lab (select all that apply)? Options: OTDR traces, Span loss tables, PMD/CD reports, Amplifier configurations, DWDM channel plan, No artifacts available yet
• Do you have a recent channel plan that shows power/take/drop and channel allocations across the C+L band? Options: Yes—detailed, Yes—partial, No
• Can we get a fiber sample or a splice list for the most challenging segment to replicate lab conditions? Options: Yes—sample available, Yes—splice list only, No
• What are the permitted launch power and channel power rules for testing on this route in-field (if any)?
• Who can provision lab cross-connections or provide remote access to your test harness during interoperability trials?
• How soon could you provide the required artifacts and access for an initial lab simulation? Options: Within 1 week, 1–3 weeks, 3–6 weeks, Longer than 6 weeks

When Interop Goes Wrong: Stories, Impact, and Root Causes

• Think of your most painful interoperability incident—what was the failure mode and what impact did it cause?
• Which root causes have recurred across incidents (select all that apply)? Options: Vendor-specific line system quirks, Inaccurate plant data, Amplifier tilt/unknown settings, Unmodeled non-linear effects, Operational error during cutover
• How much extra capacity or margin do you currently reserve to avoid these failures (percent or channels)? Options: No reserve, 5–10%, 11–25%, 26–50%, 50%+
• What mitigations have been effective in the past (e.g., lab pre-test, conservative power, staged rollouts)?
• If we were to guarantee one thing to reduce your interoperability anxiety, what should that guarantee be?

Next Steps: Who Does What and When

• Based on this conversation, what are the top three risks you want us to address first?
• Which of the following next steps would you prioritize (select up to three)? Options: Immediate lab simulation, Field pilot on a low-risk segment, Comprehensive plant audit, Procurement/commercial modeling, Executive briefing on ROI
• Who should receive the lab simulation results and who must approve the follow-up field pilot (names/roles)?
• When would you be ready to schedule a lab slot for a 2–3 week interoperability & reach test? Options: Within 1 week, 1–3 weeks, 3–6 weeks, Later—need alignment
• What would success look like from your perspective after the first lab run (specific pass/fail criteria or measurable signals)?
• Is there anything we haven’t asked that you think is critical for us to know before we model or test this route?

Getting Oriented — The Route You Want to Fix

• Quick orientation: which fiber route, service name, or DCI project should we focus on in this conversation?
• Who on your team owns the capacity forecast and who will be our day-to-day technical contact for this route? Options: Network Planning / Forecasting, Optical Engineering, NOC, Site/Field Engineering, Procurement, Other
• What is the simple story in one sentence that best describes why this route matters to your business?
• What is the current transport stack on this route (line-system vendors, coherent vendors, amplifier types, C/L band usage)?
• What timeline are we working toward for a capacity lift or new DCI go-live? Options: <3 months, 3–6 months, 6–12 months, 12–18 months, >18 months

Is Waiting to Upgrade Really Working for You?

• What would it cost you—operationally and commercially—if the busiest fiber route exhausts usable wavelengths within 18 months?
• How confident are you that current per-wavelength capacity will meet peak demand without a major intervention? Options: Very confident, Somewhat confident, Unsure, Not confident at all
• Which of these outcomes worries you most if capacity runs short: forced rewrites of traffic, emergency fiber builds, expensive dark fiber leases, or revenue loss? Options: Forced traffic rehome, Emergency fiber build, Dark fiber leasing, SLA penalties/revenue loss, Other
• How long have you been operating with the current upgrade approach (defer/patch/replace), and what have you accepted as 'normal' risk during that time?
• If we could remove one repeated pain from your capacity planning process today, what would that be?

What's the Real Risk When You Push Live Upgrades?

• When you think about upgrading spans that carry live traffic, what’s the worst thing you expect could happen operationally? Options: Traffic outage, Degraded performance, Unexpected interoperability failure, Extended rollback time, Other
• Tell us about any recent live-upgrade where outcomes were worse than expected—what exactly went off-script and why?
• How do your teams currently validate a live upgrade end-to-end (lab validation, staged field test, shadow traffic, cutover window)? Options: Full lab interoperability, Staged field test, Shadow traffic/cutover, Rolling upgrade with rollback plan, Other
• Who is empowered to abort a cutover if optics or performance metrics deviate, and how quickly can they act? Options: Site Engineer, NOC Lead, Transport Engineering Manager, On-call Ops, Other
• What would reduce your fear of a live upgrade enough that you’d greenlight a tighter schedule?

What Would 'Enough Capacity, Now' Actually Look Like?

• If you could wave a wand and change the technical outcome, what per-wavelength bit-rate and reach would solve your near-term problem? Options: 400G, 600G, 800G, Multi-rate mix (e.g., 400/800G), Unsure
• How should success be measured at 30/90/180 days after deployment (e.g., wavelengths lit, throughput, error rates, latency, margin vs lab)? Options: Wavelengths lit, End-to-end BER/Q-Factor, Throughput per wavelength, Latency, Optical margin vs lab, Other
• What timeline would make you feel confident this solution is future-proof (ability to grow without hardware swaps)? Options: 1–2 years, 3–5 years, 5+ years, Unsure
• Which commercial outcome would matter most: lower $/bit today, deferred fiber build, simpler operations, or better spectral efficiency? Options: Lower $/bit, Defer fiber build, Simpler operations, Higher spectral efficiency, Other
• If we met your technical goals but required a phased deployment, what sequencing constraints would be non-negotiable?

Where Does Tech Reality Diverge From Your Wishlist?

• Which fiber characteristics best describe this route: older SMF with unknown history, modern SSMF, mixed spans with patched segments, or submarine-grade fiber? Options: Older/unknown SMF, Modern SSMF/ITUT G.652, Mixed spans/patches, Submarine fiber, Other
• How many amplifier spans and what amplifier types (EDFA, Raman, hybrid) are typical between regenerators on this route? Options: 1–5 spans, 6–10 spans, 11–20 spans, 20+ spans
• What existing DWDM vendors and coherent line systems must we interoperate with on this route?
• What known failure modes or chronic impairments (e.g., high PMD, high attenuation spans, connector losses) have constrained your upgrades historically?
• Have you quantified how non-linear penalties or span penalties change the achievable per-wavelength rate today vs in lab conditions? Options: Yes, we have detailed margin reports, Partial estimates, No, not quantified, Unsure what this means

How Do You Want Interoperability to Feel?

• If a new coherent platform must work with legacy line systems, what level of interoperability risk is acceptable: full plug-and-play, limited modes with lab proof, or only if a line swap is performed? Options: Plug-and-play required, Accept lab-proven limited modes, Line swap only, Undecided
• Which interoperability tests matter most to you in the lab: optical reach curves, channel spacing and tilt, amplifier gain tilt, OPM vs distance, or vendor cross-compatibility? Options: Reach curves, Channel spacing/tilt, Amplifier gain tilt, OPM vs distance, Vendor cross-compatibility, Other
• How would you like test evidence presented to satisfy both engineering and procurement (raw logs, summarized KPIs, pass/fail)? Options: Raw logs + summary, Executive KPI summary, Pass/fail checklist, Interactive lab session, Other
• What internal approvals or lab-demonstration gates must be cleared before you’ll accept field deployment?
• Have you previously paused a vendor selection because lab interoperability didn’t match field behavior? If yes, what broke trust? Options: Yes—performance shortfall, Yes—unexpected failure mode, No, Prefer not to say

How Close Are You to Making a Buying Decision?

• What are the top three evaluation criteria that will determine your final vendor choice? Options: Per-wavelength rate/reach, Interoperability, OpEx savings, Multi-year pricing/growth, Operational tooling/automation, Other
• How do you rank lab testing, field trials, and commercial terms in your procurement weighting? Options: Lab testing highest, Field trials highest, Commercial terms highest, Balanced across all
• What procurement timeline and internal checkpoints do we need to map to keep within your 6–12 month purchasing cycle? Options: <3 months, 3–6 months, 6–12 months, >12 months
• Do you prefer a phased commercial commitment (pilot first, expand later) or an integrated multi-year growth commitment up-front? Options: Pilot then expand, Integrated multi-year, Hybrid approach, Undecided
• Who signs commercial terms for multi-year growth—procurement, finance, or business unit—and who drives technical acceptance? Options: Procurement, Finance, Business unit, Transport Engineering

What Would Make an Upgrade Feel Safe and Predictable?

• What are your non-negotiable pre-deployment items (e.g., named rollback owner, verified spares, dedicated test harness, formal access windows)? Options: Named rollback owner, Verified fiber spares, Dedicated test harness, Formal access windows, Change control signoff, Other
• How many planned maintenance windows per month or quarter can you realistically schedule for phased upgrades? Options: Multiple per month, Monthly, Quarterly, Rare/Only emergency
• Who will own on-site coordination during a cutover (field lead, transport engineer, vendor PM), and who is the escalation contact? Options: Field Lead, Transport Engineer, Vendor PM, NOC Lead, Other
• What rollback criteria would require an immediate revert (BER threshold, unlit wavelengths, latency spike, unexpected errors)? Options: BER/Q-factor drop, Unlit wavelength, Latency spike, Unexpected alarms, Other
• Do you have on-hand spares and cross-connect rights for emergency swaps, or do we need to provision spares as part of the project? Options: We have spares on-hand, We need vendor-provided spares, Mixed/depends on site, Unsure

Who Needs to Be in the Room to Say Yes?

• Who are the decision-makers who must sign off on scope, pricing, and go/no-go for deployment (names and roles if possible)?
• Which stakeholders will prioritize technical outcome vs commercial terms vs operational risk (e.g., optical engineering vs procurement vs NOC)? Options: Optical Engineering, Network Planning, Procurement, NOC/Operations, Finance, Other
• What internal governance cadence do you use for critical network changes (weekly review, change advisory board, executive approval)? Options: Weekly review, Change Advisory Board, Executive approval, Ad-hoc
• Are there external partners or vendors (subsea operator, third-party maintainer) who must be coordinated with for cutovers? Options: Yes—subsea operator, Yes—third-party maintainer, No, Unsure
• What communication protocol and SLAs do you expect from a vendor during a high-risk cutover (response time, on-call engineer, status cadence)? Options: Immediate on-call engineer, 30-min status cadence, Hourly updates, Daily summary

Let’s Make Validation Concrete — How Will We Know It Worked?

• What are the must-have lab benchmarks we should hit to accept field deployment (Q-factor, OSNR margin, BER, throughput)? Options: Q-factor, OSNR margin, BER, Throughput, Latency, Other
• Post-deployment, which metrics will you log and for how long before declaring the upgrade successful? Options: 30 days, 90 days, 6 months, Other
• How will interoperability failures be triaged between your team and the vendor (joint war room, vendor-led remediation, escalation to engineering leads)? Options: Joint war room, Vendor remediation, Escalation to leads, Other
• Which acceptance artifacts do you require: raw test traces, lab-to-field comparison report, signed acceptance checklist, or on-site witness test? Options: Raw test traces, Lab-to-field report, Signed checklist, On-site witness test, Other
• If some wavelengths meet spec and a minority don’t, what remediation path do you prefer: immediate rollback, phased retry, or targeted troubleshooting and re-test? Options: Immediate rollback, Phased retry, Targeted troubleshooting, Depends on impact

Next Steps That Don’t Stall — Practical Path to Decision

• What would a sensible first pilot look like on this route (single-span lab-validated, one live wavelength trial, or full-channel pilot)? Options: Single-span lab-validated, One live wavelength trial, Full-channel pilot, Other
• What budgetary or procurement milestones must we align with to start lab testing and field validation?
• How quickly can you provide necessary artifacts for lab validation (fiber specs, span loss maps, amplifier configs, vendor PN/serials)? Options: Immediately, Within 2 weeks, Within a month, Longer
• Who should we schedule the initial technical deep-dive with and what outcome do you want from that meeting?
• If we delivered a clear lab report, field test plan, and a named deployment owner within two weeks, how likely would you be to move to a pilot? Options: Very likely, Somewhat likely, Unlikely, Need more info

Getting Our Bearings — who’s in the room and what keeps you up at night

• Who will be the primary stakeholders we should engage for technical, commercial, and operational decisions? Options: VP Transport Network Engineering, Director Optical Planning, Optical Engineer/Planner, NOC Manager, Field Operations Lead, Procurement/Sourcing, Other
• What single sentence best describes the business trigger for this project (e.g., busiest route exhausts wavelengths in 12 months; new DCI requiring 400G reach)?
• Which routes or fiber assets are the highest priority for this program right now?
• What is your target decision/take-action date for the first live upgrade (or go/no-go)? Options: Within 30 days, 30–90 days, 3–6 months, 6–12 months, Longer/Unknown
• How does your organization define success for a transport upgrade project (cost per bit, time-to-service, zero customer impact, etc.)? Options: Per-wavelength throughput, Total fiber capacity, Zero-service-impact cutover, Per-bit cost reduction, Time to deploy, Other

If our lab numbers don’t match your fiber, what will you notice first?

• Tell us the precise fiber profile for the routes in scope (fiber type, span lengths, number of EDFAs, C+L band availability, splice count).
• Which of the following best describes your current installed line-system vendor environment on those routes? Options: Single vendor line system, Multiple vendor mix, Pluggable-only systems, Legacy vendor nearing EoL, Unknown / need to audit
• How many amplifier spans (approx.) and what is the longest contiguous amplifier span on the critical route(s)? Options: <5 spans, 5–10 spans, 11–15 spans, 16–20 spans, >20 spans, Unsure
• What measured fiber impairments do you expect will constrain reach or rate (e.g., high OSNR loss, high PMD, elevated SRS/FRD, high splice loss)? Options: OSNR loss, High PMD, High splice/loss, Nonlinear penalties (SRS/XPM), Chromatic dispersion extremes, Other/Unknown
• Can you upload or summarize recent OTDR/IL/PMD/ASNR measurements for these spans (or indicate if we need to schedule a fiber audit)? Options: We will upload measurements, We need you to schedule a fiber audit, Measurements available but require redaction, Not available

Are we comfortable pushing software-defined rates on live traffic?

• How comfortable is your operations team with in-service upgrades that change modulation or baud while traffic is live? Options: Very comfortable, Somewhat comfortable, Prefer scheduled outages, Not comfortable / never
• When you run live upgrades today, what is the most common failure mode or fright (e.g., unexpected BER spike, slow rollback, vendor support latency)?
• What is an acceptable impact window for an upgrade step on a live route (milliseconds of packet loss, minutes of impaired service, scheduled window)? Options: Sub-second/no impact, Seconds, Minutes, Scheduled outage acceptable, Depends by customer SLAs
• Who must be on-call or approve a rollback during live upgrades (roles and escalation contact tiers)?
• Which mitigation strategies do you already use or will require for live upgrades? Options: Traffic grooming/reservation, Protection routes/N+1, Pre-staged spares, Live lab verification, Automated rollback scripts, Other

What would change if you could count on 800G on the route you care about?

• What per-wavelength line rates would materially alter your network planning and procurement decisions (select all that apply)? Options: 100G, 200G, 400G, 600G, 800G
• For the busiest routes, what is the traffic timeline we should optimize for (wavelengths likely to be at risk within 18 months, 36 months, etc.)? Options: Within 6 months, 6–12 months, 12–18 months, 18–36 months, No urgent risk
• What measurable acceptance signals will make you say the upgrade delivered value (e.g., achieved BER, margin vs lab, per-wavelength throughput, spectral efficiency)? Options: BER/FER targets, OSNR margin vs lab, Confirmed reach at X Gbps, Packet loss latency metrics, Operational simplicity
• If you could choose one strategic outcome from this project besides capacity (e.g., deferred fiber build, lower OpEx, simplified multi-vendor support), what would it be? Options: Defer new fiber build, Lower per-bit OpEx, Simplify operations, Reduce vendor lock-in, Faster capacity growth
• How would meeting that outcome change your team’s priorities or budget decisions for the next 24 months?

Where interoperability has surprised you — tell us the stories that still sting

• Have you experienced interoperability failures between transponders and line systems in the field? If yes, briefly describe the last incident and its impact. Options: Yes — major impact, Yes — minor impact, No
• Which vendor combinations and equipment generations are present in the routes we’re targeting?
• How do you currently validate multi-vendor interoperability before field upgrades (lab testing, field pilots, staged rollouts)? Options: Full lab interoperability test, Limited lab + field pilot, Field pilot only, No formal interoperability testing
• What’s the maximum tolerable time from discovery of an interoperability issue to vendor-assisted resolution before it’s considered a project blocker? Options: <24 hours, 24–72 hours, 3–7 days, >7 days, Depends on severity
• Which interoperability test artifacts do you require to sign acceptance (test logs, PCS/OTN stats, captured waveforms, OTDR traces)? Options: Test logs/line rates, OTN/PCS statistics, Captured oscilloscope waveforms, OTDR/IL traces, All of the above, Other

How will you decide we crossed the finish line (and who will sign it?)

• Which specific lab benchmark metrics must the deployed system meet or exceed to proceed to production (e.g., X dB OSNR margin, BER threshold, reach at 800G)?
• Who holds final acceptance authority for lab tests and field cutovers (role/title), and what documentation do they require?
• Do you require staged acceptance (lab → pilot route → full route) and what are the go/no-go gates between stages? Options: Lab → pilot → full route, Lab → selective production, Pilot only then full route, Other
• What KPIs will you track for 30/90/180 days post-deployment to declare success (e.g., no unplanned outages, throughput per wavelength, latency/SLA adherence)? Options: No unplanned outages, Per-wavelength throughput, Latency/SLA metrics, Customer experience metrics, Operational overhead reduction
• How would you like interoperability issues and enhancement requests tracked post-acceptance (ticket system, joint war room, weekly cadence)? Options: Ticketing system (JIRA/ServiceNow), Joint weekly war-room, Ad-hoc escalation, Monthly review

What would make a live cutover feel confidently reversible right before we pull the trigger?

• What pre-staged rollback capabilities must be in place before any live route upgrade (spare wavelengths, pre-configured ports, golden-configuration images)? Options: Spare wavelengths/ports, Pre-configured rollback scripts, Golden configurations backed up, Reserve maintenance windows, Other
• How much fiber spares/inventory do you maintain for critical routes and where are they located? Options: On-site at headend, Regional spares, Centralized warehouse, Minimal/none
• What is your required notification and escalation process during a cutover if performance deviates from expected thresholds? Options: Immediate phone + ticket, Phone → ticket → exec if unresolved, NOC handles first, then escalation, Other
• Who will own the post-cutover verification steps (optical validation, traffic acceptance, interoperability logs) and what timelines do they expect?
• If a cutover needs reversal, what maximum time-to-rollback keeps your SLAs intact? Options: Immediate/sub-second, Under 5 minutes, Under 30 minutes, Under 2 hours, Depends on route

If we commit to a tight test and deployment plan, what would make you move faster?

• What immediate artifacts or data do you need from us to start internal approvals (detailed lab test plan, cost model, interoperability checklist, risk register)? Options: Lab test plan, Commercial cost model, Interoperability checklist, Risk register and rollback plan, All of the above
• What is the realistic procurement and budget approval timeline on your side once we present a mutually agreed solution? Options: <30 days, 30–60 days, 2–3 months, 3–6 months, Longer/unsure
• Which members of your team should be invited to the initial lab test planning session, and what is their availability window?
• Would you prefer a staged lab engagement (we run tests and share results) or a joint on-site lab session with your engineers in the loop? Options: Staged — we run tests and report, Joint — your engineers in lab, Hybrid — some joint sessions
• Beyond the technical work, what commercial terms or guarantees would make you comfortable moving to Mutual Commit (pricing horizon, volume guarantees, escalation SLAs)?