Technology
›
Telecom, Media & Entertainment
›
Telecom Equipment Sales
Optical Networking
Complex platform, content, and network decisions where revenue, rights, and customer experience intersect.
Example organizations in this space:
Ciena
Infinera
Cisco
Lumentum
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Pre-Sales
Qualify and diagnose before investing in a full evaluation cycle.
-
Qualification
Confirm budget window, decision-makers, procurement constraints, and timeline before investing in full technical discovery.
Qualification Questions
Capacity and route fit (quick readiness check)
- Does your capacity forecast show the busiest fiber route will exhaust usable wavelengths within 18 months?
- Is the project driven by the existing DWDM system being unable to support the required per-wavelength data rate without a full line-system upgrade?
- What best describes the route or fiber plant you need to address?
Interoperability and operational constraints
- Will the new equipment need to interoperate with live line systems or transponders from other vendors during evaluation or deployment?
- Are there operational constraints that limit in-service upgrades or staged cutovers, such as no maintenance windows or strict blackout periods?
Budget and procurement posture
- Is there an allocated budget or a budget window for this program?
Decision authority and timing
- Who signs the purchase order and who else materially influences the decision?
- If there are procurement constraints or required approvals we should know about, please briefly describe them.
- What is your target procurement decision or go live timeframe?
-
Technical Discovery
Map fiber routes, DWDM inventory, traffic forecasts, physical fiber characteristics, and stakeholder success criteria.
Discovery Questions
Quick route snapshot and urgency
- How soon does your busiest fiber route require additional wavelength capacity?
- Describe the specific route endpoints, fiber type, and approximate total span length that are driving this need
- Which traffic types consume the majority of capacity on that route?
- Who in your organization makes the final go or no go decision for a line system upgrade?
- Walk me through the last major capacity upgrade on this route, what went well and what surprised your team
Where the current line system falls short
- If your current DWDM runbooks are accurate, why are you still forecasting a wavelength shortfall within your stated window?
- Provide the most recent measured fiber attenuation, chromatic dispersion, PMD, amplifier spacing, and span count you have for the route
- Name the legacy line systems and amplifier vendors that appear along this route
- How complete and recent are your OTDR and span loss records?
- What single measured fiber parameter or route constraint would make you stop the project immediately?
Lab tests versus field reality
- Lab pass results often hide field fragility, tell me why a lab success would still leave your operations team unconvinced
- Provide recent OTDR or span loss sheets and the latest amplifier inventory you can share for lab planning
- List the exact line cards and transponder families we must interoperate with during testing
- What acceptance criteria will you require for field validation, for example BER, OSNR margin, or latency stability?
- List the people or roles who must sign off separately on lab test results and on field verification
- A field test that misses your acceptance thresholds by more than 1 dB margin often kills deals, would you pause procurement in that case?
Commercial tradeoffs that accelerate or stall procurement
- Would a per-wavelength price that materially lowers your per-bit cost be sufficient to delay a planned fiber build, or do contractual terms matter more?
- Which commercial terms matter most when you evaluate long-haul optical platforms?
- What procurement timeline and internal budget cycle must this opportunity align with?
- Who owns the contract negotiation and final signatory role for optical transport purchases?
- If pricing meets your target but there is no multi-year capacity commitment, would your team proceed?
Where upgrades have derailed in the past
- What operator or schedule risk has historically killed similar upgrades in your network?
- Which of these risks concerns you most for this project?
- Tell me about a past upgrade that produced unexpected downtime, what caused it and what did you change afterwards
- How many full-time engineers will be available to support planning, lab tests, and staged cutovers during this engagement?
- What single dependency, if unresolved, would stop this project from moving forward?
The other options your team is weighing
- If staying with your current vendor avoids near-term risk, what would have to be true for you to keep them instead of switching?
- Which alternatives are you actively evaluating right now?
- Who inside your organization has argued for solving this internally rather than engaging an external vendor?
- What proof points or outcomes would your team require to choose the internal path instead of a vendor-led upgrade?
- If an internal path could be executed within your target window and budget, would that end the vendor evaluation?
Operational readiness and constraints
- If the upgrade requires two week maintenance windows at multiple sites and dedicated engineers, can your team provide those windows and resources?
- List the third-party systems that must integrate for this project, for example your NMS, OSS, ticketing system, or dark fiber lease platform
- Do you own and can you provide OTDR traces, span loss data, and amplifier inventory before lab testing begins?
- Who owns internal change control and has authority to approve emergency rollback during live cutovers?
- Are there regulatory approvals, landlord access permissions, or cross-jurisdiction permits that could gate the timeline?
- If your team cannot provide accurate span loss and amplifier inventory within the first two weeks, would you delay lab planning?
Acceptance criteria that would trigger production and contract
- If a pilot confirms 800G per wavelength at your target reach, what remaining contractual checks or technical verifications would still block a purchase?
- Which acceptance metrics should trigger an automatic go or no-go decision?
- Who must be on the production acceptance and commercial sign-off committee?
- What timeline do you require between a successful pilot and a production deployment start date?
- Name the one remaining blocker that would prevent a signature within 30 days after a successful pilot
Owners, scheduling, and next steps
- If we schedule a lab interoperability window, what is the earliest date your team can commit the required ports and engineers?
- Which internal stakeholders should be included in validation planning and weekly status calls?
- Who will be the day to day technical owner responsible for coordinating tests and delivering documents?
- What cadence and format for status updates would your team prefer during discovery and lab testing?
- If we can meet your earliest window and your acceptance criteria, are you prepared to allocate budget and move to solution scoping?
-
-
Solution Evaluation
Run lab interoperability tests and field validation against the buyer's fiber characteristics with explicit acceptance criteria and performance measurement.
- decision_readiness
- current_state
- stakeholders
- gaps
- desired_state
- success_criteria
- desired_state
- success_criteria
- gaps
- current_state
- decision_readiness
- stakeholders
- stakeholders
- decision_readiness
- current_state
- desired_state
- success_criteria
- gaps
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
-
Solution Scope
Define hardware and software modules, channel plan, per-wavelength rates, upgrade path, responsibilities, and measurable acceptance criteria.
Scope Configuration
- Deliver coherent transponder units (up to 800G)
- Install reconfigurable optical add-drop multiplexers (ROADMs)
- Deploy line-system optical amplifiers and C+L band filters
- Provision per-wavelength software-defined modulation profiles
- Configure channel plan and frequency grid
- Perform fiber span power balancing and gain-tilt control
- Calibrate DSP, FEC, and receiver equalization per route
- Integrate with existing DWDM line-system controls
- Execute hitless cutover and live-traffic migration support
- Provide multi-year wavelength capacity licensing and upgrades
- Supply spare parts kits and field-replaceable modules
- Train operations team on day‑1 monitoring and alarms
Scope Questions
Deliver coherent transponder units (up to 800G)
- How many wavelengths do you plan to provision with coherent transponders on this route?
- Select the per-wavelength line rates you will require from transponders (select all that apply).
- Provide the maximum span length between inline amplifiers or sites on the target route (km).
- Do you require pluggable client modules or chassis-based transponders?
- Specify your acceptance thresholds for transponder performance (for example required OSNR in dB, pre-FEC BER) for each route.
- List any rack units, available power per rack (kW), or cooling limits at the sites where transponders will be installed.
Install reconfigurable optical add-drop multiplexers (ROADMs)
- For each site, list required ROADM degree and add/drop port counts (use site codes).
- Will you require colorless, directionless, contentionless (CDC) ROADM capability at any site?
- Indicate the wavelength range ROADMs must support (C-band, C+L, or specify nm range).
- Which client protection and grooming behaviors are required (for example 1+1 protection, hitless grooming)?
- Who will perform fiber patching and local site cross-connect work during ROADM installation?
- Are there optical connector or fiber type constraints at sites (for example G.652.D single-mode, connector polish type)?
Deploy line-system optical amplifiers and C+L band filters
- Provide the number of amplifier spans and the average span loss in dB for the planned route.
- Which inline amplifier classes are currently deployed (EDFA, Raman-assisted, hybrid) and model families if known?
- Do you require full-route C+L amplification or only C+L in specific segments?
- List any site power constraints or hazardous area classifications that affect amplifier placement.
- Specify the maximum allowable output power per channel (dBm) and composite ASE budget you require.
- What measurable acceptance criteria will confirm correct amplifier gain-tilt and passband performance (state gain flatness tolerance in dB across C+L)?
Provision per-wavelength software-defined modulation profiles
- Select the modulation formats you intend to use on this route (for example 16QAM, 64QAM, probabilistic constellation shaping).
- Is adaptive modulation per wavelength required based on real-time OSNR or Q-value?
- Indicate the control-plane interface preferred for commissioning modulation changes (NETCONF/YANG, REST API, CLI).
- How will you verify modulation profile changes in the field (OSNR/BER measurements, live traffic throughput tests, lab validation)?
- Identify any regulatory spectral masks or per-channel power limits that constrain modulation choices on this route (cite regional mask or operator policy).
- State acceptable latency for in-service modulation reconfiguration commands from your OSS/NMS (ms or minutes).
Configure channel plan and frequency grid
- Choose the ITU grid spacing required for the channel plan on this route.
- Enter the planned channels per fiber pair at launch and at 24 months.
- Are there existing spectrum allocations occupied by third-party equipment that must be preserved? If yes, list occupied slots by wavelength or frequency.
- State the desired spectral guard band between amplified blocks or third-party channels (GHz or nm).
- Describe the target per-wavelength rate and spectral efficiency objectives to be reflected in the channel plan.
- Who will approve the final frequency assignments and master channel-plan document within your organization?
Perform fiber span power balancing and gain-tilt control
- Have you obtained recent OTDR traces and span loss reports for each fiber span (attach or reference document ID)?
- Enter the maximum span loss (dB) and typical splice count per span on the route.
- Choose the preferred in-line equalization method (EDFA gain-tilt, variable optical attenuator, Raman pre-emphasis, combination).
- Identify any legacy inline devices (for example gain flats or tilt compensators) that limit adjustment range; list device type and location.
- Define the acceptable power variance per channel at receiver input (dB) that your operations require.
- Name the party responsible for on-site fiber patching and jumper management during balancing activities.
Calibrate DSP, FEC, and receiver equalization per route
- Detail the forward error correction (FEC) modes you require or support on this route.
- Is per-route DSP calibration in the lab required prior to field commissioning?
- Define the post-FEC performance metric threshold that must be met for route acceptance (for example post-FEC BER or Q-value threshold).
- How will you coordinate firmware and FPGA image versions for DSP across sites to avoid interoperability issues?
- Attach any documented legacy receiver equalizer settings to replicate or avoid (reference IDs or document names).
- Detail which test patterns and line rates should be used during calibration (for example PRBS31, 64‑QAM test vector).
Integrate with existing DWDM line-system controls
- Describe the control protocols in use on your existing DWDM (for example TL1, SNMP, NETCONF/YANG).
- Confirm whether NMS/EMS integration is required for inventory, alarms, telemetry, or full control.
- What authentication method and certificate policy must the integration endpoint accept (for example X.509, API token, SSH key)?
- Name the expected ramp schedule for integration testing with legacy ROADM and amplifier control (dates or phases).
- What alarm mapping or object identifier (OID) translations must be preserved for alarm correlation with your NMS?
- Share the primary contact for SNMP traps, NMS testing, and cutover coordination (name, role, email).
Execute hitless cutover and live-traffic migration support
- Confirm if hitless cutover capability is required for service classes carrying live customer traffic.
- What maintenance windows are available per site for cutover operations (local time and duration)?
- Outline rollback threshold metrics that will trigger automatic rollback during cutover (for example BER increase, packet loss percentage).
- Designate who will provide traffic engineering support and cross-connect changes during cutover at each POP.
- Flag whether you require a stepwise capacity ramp with tenant validation after each stage.
- Include details of mission-critical services (by service ID or circuit ID) that must be excluded from any service-impacting operations.
Provide multi-year wavelength capacity licensing and upgrades
- How many licensed wavelengths do you require initially and what is the expected annual growth?
- Pick preferred contract term horizon for multi-year pricing.
- Opt for a licensing model: software-defined pay-as-you-grow, fixed-port annual license, or hybrid.
- Note any budget approval cycles or procurement windows that constrain license deployment dates (provide calendar windows).
- Share the authorized signer or procurement contact for multi-year agreements (name, role, contact).
- If capacity growth exceeds contracted thresholds, what automatic upgrade path do you want (auto-increase with notice, fee-based uplift, or renegotiation)?
-
Mutual Commit
Finalize commercial terms, multi-year capacity pricing, SLAs, delivery milestones, and contractual dependencies for procurement.
Agreement Modules
- Commercial Term Sheet
- Purchase Agreement
- Order Confirmation
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Service Level Agreement (SLA)
- Multi-Year Capacity Pricing Addendum
- Delivery, Acceptance & Milestone Schedule
- Change Order Agreement
- Commercial Dependencies & Interoperability Schedule
- Software License & Support Agreement
- Export Control & Regulatory Compliance Addendum (conditional)
-
Deployment
Operationalize rollout with readiness checks, execution, and outcome validation.
-
Pre-Deployment Readiness
Lock owners, maintenance windows, test windows, access credentials, and operational constraints required for an in-service upgrade.
Pre-Deployment Questions
Environment and site access
- Which production sites/environments will the in-service upgrade touch? List one site code or location per line (so we can plan per-site tasks).
- Are physical site access and network access permissions approved for all listed sites?
Data and configuration
- Who is the authoritative owner of the final channel plan and per-wavelength assignments (name and role)? This owner will approve live configuration changes.
- Are the authoritative configuration backups and source-of-truth files accessible to the deployment team?
People and ownership
- Provide the primary technical owner for cutover operations (name, role, contact) who has authority to approve rollbacks and emergency decisions.
- Are the buyer's maintenance, NOC, and on-call teams committed and scheduled to support the proposed windows?
Timing and constraints
- Confirm the approved maintenance window(s) for each site (start date/time and end date/time, local timezone), or indicate if rolling windows apply (so we can build the Gantt).
- Are rollback checkpoints, test windows (layer-1 traffic validation, smoke tests), and their gate owners pre-authorized for the upgrade?
-
Configuration Details
Capture exact channel plans, amplifier and power settings, transponder configurations, software images, and integration endpoints for execution.
Configuration Details
Environments & Integration Endpoints
- Enter the production management endpoint URL (format: https://host[:port]/path). Leave blank if no in-band management endpoint will be used for this deployment.
- Select required integration endpoint types for this deployment (multi-select). The deployment will configure connectors matching these types.
- Enter the non-secret integration endpoint identifier (exact value consumed verbatim; e.g., API client ID, sysName, or connector name). Do NOT paste credentials or secrets.
- Enter the credential owner for integration endpoints (role or team name; e.g., 'NetOps Team' or 'Platform Integrations'). The actual secrets will be exchanged via your secrets manager at handoff.
Channel Plan & Spectral Assignment
- Select spectral band to deploy (Default: C+L band). The deployment will allocate spectrum in the selected band.
- Primary channel plan — enter EXACT single value in this format (consumed verbatim): <center-frequency in THz>@<baud in GBd> — e.g., 193.100THz@75GBd
- Select spectral grid spacing to apply (Default: 50 GHz). If you choose 'Custom', provide the numeric GHz value in a follow-up configuration item outside this sheet.
Amplifiers, Power & Span
- Select the primary amplifier type used on spans for this route (single value). The deployment will apply span templates for the selected class.
- Enter amplifier target per-channel launch power in dBm (numeric — Default: 0). Example: 0 or -2.5
Transponder, Software & Monitoring
- Enter the transponder firmware/software image tag or filename to install (exact value consumed verbatim; e.g., release-2026-06). Do NOT paste keys or secrets.
- Select modulation format to provision on the transponder (single value). If 'Adaptive' is chosen, the device will negotiate the final format per reach at provision time.
- Enter the monitoring integration endpoint address (format: protocol://host:port or IP:port — e.g., http://10.0.0.5:9090 or 192.0.2.10:514). This value is consumed verbatim; do NOT paste credentials.
-
Deployment
Execute staged cutover and upgrades with Gantt sequencing, rollback plans, and real-time monitoring to minimize traffic disruption.
-
Go-Live Acceptance
Verify post-cutover performance against acceptance criteria, confirm monitoring handover, and complete designated rollback checkpoints before declaring success.
Checklist items
- Receive post-cutover performance test report
- Validate live-traffic per-wavelength carriage
- Confirm rollback checkpoint capture and storage
- Execute and document rollback restore test
- Handover monitoring access and alert subscriptions
- Deliver operational runbooks and escalation matrix
- Validate SLA metric ingestion and baseline publication
- Close or create remediation plans for all critical post-cutover issues
- Obtain formal go-live acceptance sign-off
-
-
Success
Review measured outcomes against success metrics, track issues and enhancement requests, and plan capacity-growth milestones.
Success Reviews
- Go-Live Health Check (weeks 1-4)
- First Measurement Review (weeks 4-10)
- 90-Day Realization Review and Incumbent Wind-Down
- Quarterly Operational Review
- Annual Success Assessment
Issues & Enhancements
- Capacity-growth milestones in Mutual Commit are confirmed with any required changes to lead times documented.
- Provide a short focused dataset (link-level telemetry and test traces) for each failing span to support root-cause work.
- Present 90-day outcome metrics
- Aggregate usable capacity and open critical incident count are validated against Solution Scope targets and any remaining gaps have fixed remediation dates.
- The incumbent system is either formally decommissioned or retained read-only with data archived, and no active operational work remains in the old system.
- Publish the 90-day realization report showing metric trends, remediation status, and the incumbent decommission certificate or retained-read-only plan.
- Create a monitoring runbook addendum capturing alarm ownership and escalation steps for the next 12 months.
- Outstanding incidents and MTTR review
- Enhancement backlog and priority incidents are triaged with a clear set of next-quarter deliverables.
- Re-confirm delivery checklist and owners
- Publish the prioritized enhancement backlog with estimated delivery windows for the next quarter.
- Document any changes to capacity provisioning lead times and circulate an updated milestone calendar.
- Yearly performance vs commitments
- Annual metrics demonstrate whether the solution met the year-one commitments in Mutual Commit and Solution Scope, with deviations documented and plans to remediate.
- All long-running operational items have a closure plan with dates or are formally accepted as deferred with rationale.
- Deliver the year-end operational summary and archive test data and runbooks in the shared workspace.
- Produce a documented remediation schedule for any annual metric shortfalls with target completion quarters.
- All critical post-cutover validation checks are confirmed complete or have an agreed remediation plan with target dates.
- Monitoring handover is verified and baseline alarm thresholds are published for ongoing review.
- Publish a one-page post-cutover status summary with outstanding issues and target resolution dates.
- Schedule targeted troubleshooting sessions for any unresolved high-severity alarms within 48 hours.
- Present measured outcomes vs Solution Scope targets
- Measured per-wavelength throughput and aggregate lit capacity are assessed against Solution Scope targets, with deviations documented and diagnosed.
- A concrete remediation plan with dates is agreed to close any gaps before the acceptance window.
- Deliver a remediation playbook listing configuration changes, lab validation steps, and field test windows with completion dates.
- Deployment and cutover validation
- Enhancement request backlog and prioritization
- Remediation closure review
- Root-cause analysis for gaps
- Long-running issues and SLA performance
- Capacity-growth milestone alignment
- Incumbent decommission checkpoint
- Capacity-growth milestone check
- Agree corrective actions and timeline
- Early operational signals
- Risk and contingency review
- Short actions and next-step commitments
- Operational handover and monitoring confirmation
- Open issues and blockers
- Annual artifact delivery
- Immediate remediation actions