Predictika · Optical networking

An AI sales agent's ROADM node order, checked before it goes out

An AI sales agent prepares an order for a ROADM node built from Lumentum TrueFlex parts: a Twin WSS for each degree, an add/drop stage (direct, colorless-directionless with Twin MxN, or contentionless with the Twin 8x16 Multicast Switch) and TrueFlex optical channel monitors. Before it goes out, the agent sends it to Predictika, which checks it and returns a verdict and every finding at once.

Scope: A TrueFlex route-and-select ROADM node: Twin 1x20 or Twin 1x35 WSS, Twin MxN, Twin 8x16 Multicast Switch and 1, 2 or 4 port OCMs, with the node sizing rules below. See everything this validator covers

This validator models a node order built from the TrueFlex building blocks Lumentum describes publicly, not just the scenarios shown below. The product names, the one-Twin-WSS-per-degree route-and-select design, the 20 and 35 port counts, the Twin MxN port total (21, or up to 36 on the Twin 1x35) and the OCM port options come from Lumentum's public product brief and product page; the node sizing rules below are modeled by Predictika from comparable ROADM designs and are not Lumentum rules.

  • WSS ports per degree — each degree needs one Twin WSS, with ports for express traffic to the other degrees plus add/drop access, so a node that needs more ports than a Twin 1x20 has is caught, and a stated Twin WSS count that differs from the degree count.
  • Add/drop stage — Twin MxN units for a colorless-directionless stage and Twin 8x16 Multicast Switches (16 transceivers each, at most 8 degrees) for a contentionless stage, sized to the transceiver count; equipment the chosen architecture does not use goes to a person.
  • Monitoring and node size — one OCM port per degree, at least 2 degrees, at most 64 transceivers on one add/drop stage, and nodes of 6 degrees or more go to a person for engineering review.

Any ROADM node order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (none are modeled, so this validator produces no price build-up), amplifiers and other Lumentum optical products, L-band and C+L designs, ROADM-on-a-Blade and integrated subsystems, and the optical performance (loss, reach) of the node.

The AI sales agentBuilds the node order from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based CPQPredictika
Ports that run out per degreeOnly with workarounds
Express ports to the other degrees plus add/drop access must fit the ports of the WSS chosen; a rules-based CPQ needs a formula per WSS model and per add/drop type.		The ports a node needs are computed from the degree count and compared with the WSS quoted.
Add/drop stage sized to the transceiversOnly with care
The number of Twin MxN units or Multicast Switches depends on the transceiver count and the degrees; a CPQ often lets the rep type the quantity without checking it.		The units needed are computed and compared with the units quoted.
Figures a quote statesOnly with workarounds
A stated Twin WSS count is printed from what the rep typed; nothing compares it with the degree count.		The stated count is compared with the one the design needs.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order is saved or a step is completed, so a rep often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

    
1A ROADM node needs at least 2 degrees; the order has 1.
2A node with 8 degrees needs an engineering review of the node design.
3The node needs 21 ports on each Twin WSS (express to the other degrees plus add/drop access); the quoted WSS has 20.
4Direct colorless add/drop needs at least 1 add/drop port on each Twin WSS; the order has 0.
5The order states 8 Twin WSS units; a route-and-select node needs one Twin WSS per degree, which is 4.
6A CD or CDC add/drop stage needs at least 1 transceiver; the order has 0.
70 Twin MxN unit(s) are quoted; 1 are needed for the transceivers.
8The order has 65 transceivers on one add/drop stage; this model allows at most 64.
92 Twin MxN unit(s) are quoted; 3 are needed for the transceivers.
101 Twin MxN unit(s) are quoted; 2 are needed for the transceivers.
111 Twin 8x16 Multicast Switch(es) are quoted; 2 are needed for the transceivers (16 per switch).
12The Twin 8x16 Multicast Switch has 8 line-side ports; a CDC node can have at most 8 degrees, the order has 9.
13A node with 9 degrees needs an engineering review of the node design.
141 OCM unit(s) are quoted and the node has 4 degrees; each degree needs one monitor port.
15The quote includes Twin MxN or Multicast Switch units that the chosen add/drop architecture does not use; a person should confirm.
16A node with 6 degrees needs an engineering review of the node design.

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Contentionless node: An 8-degree node with 40 transceivers, one Multicast Switch and one OCM

    
The agent's request. Please quote a 8-degree TrueFlex ROADM node on the Twin 1x20 WSS with contentionless (Twin 8x16 Multicast Switch) add/drop for 40 transceivers, with 1 Twin 8x16 Multicast Switch(es) and 1 4 port OCM(s). The quote states 6 Twin WSS units. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated Twin WSS count does not match. The order states 6 Twin WSS units; a route-and-select node needs one Twin WSS per degree, which is 8.
    • 
      
  • Not enough Multicast Switches. 1 Twin 8x16 Multicast Switch(es) are quoted; 3 are needed for the transceivers (16 per switch).
    • 
      
  • Not enough OCM ports. 1 OCM unit(s) are quoted and the node has 8 degrees; each degree needs one monitor port.
    • 
      
  • High-degree node. A node with 8 degrees needs an engineering review of the node design.
    • 
    

    
2. Contentionless node: The agent resubmits after fixing the errors

    
The agent's request. Please quote a 8-degree TrueFlex ROADM node on the Twin 1x20 WSS with contentionless (Twin 8x16 Multicast Switch) add/drop for 40 transceivers, with 3 Twin 8x16 Multicast Switch(es) and 2 4 port OCM(s). The quote states 8 Twin WSS units. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • High-degree node. A node with 8 degrees needs an engineering review of the node design.
    • 
      
  • Order summary. 8-degree node on Twin 1x20 WSS, CDC add/drop, 40 transceivers, 8 Twin WSS units.
    • 
    

    
3. Contentionless node: The agent reduces the node to 5 degrees

    
The agent's request. Please quote a 5-degree TrueFlex ROADM node on the Twin 1x20 WSS with contentionless (Twin 8x16 Multicast Switch) add/drop for 40 transceivers, with 3 Twin 8x16 Multicast Switch(es) and 2 4 port OCM(s). The quote states 5 Twin WSS units. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 5-degree node on Twin 1x20 WSS, CDC add/drop, 40 transceivers, 5 Twin WSS units.
    • 
    

    
4. Colorless-directionless node: A 4-degree node with 45 transceivers, two Twin MxN units and one 2-port OCM

    
The agent's request. Please quote a 4-degree TrueFlex ROADM node on the Twin 1x20 WSS with colorless-directionless (Twin MxN) add/drop for 45 transceivers, with 2 Twin MxN unit(s) and 1 2 port OCM(s). The quote states 4 Twin WSS units. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Not enough Twin MxN units. 2 Twin MxN unit(s) are quoted; 3 are needed for the transceivers.
    • 
      
  • Not enough OCM ports. 1 OCM unit(s) are quoted and the node has 4 degrees; each degree needs one monitor port.
    • 
    

    
5. Colorless-directionless node: The agent resubmits after fixing the errors

    
The agent's request. Please quote a 4-degree TrueFlex ROADM node on the Twin 1x20 WSS with colorless-directionless (Twin MxN) add/drop for 45 transceivers, with 3 Twin MxN unit(s) and 2 2 port OCM(s). The quote states 4 Twin WSS units. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 4-degree node on Twin 1x20 WSS, CD add/drop, 45 transceivers, 4 Twin WSS units.
    • 
    

    
6. Direct add/drop: A 5-degree node with 18 direct add/drop ports per WSS on Twin 1x20

    
The agent's request. Please quote a 5-degree TrueFlex ROADM node on the Twin 1x20 WSS with direct colorless add/drop, 18 add/drop ports per WSS, with 2 4 port OCM(s). The quote states 5 Twin WSS units. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Not enough WSS ports per degree. The node needs 22 ports on each Twin WSS (express to the other degrees plus add/drop access); the quoted WSS has 20.
    • 
    

    
7. Direct add/drop: The agent switches to the Twin 1x35 WSS

    
The agent's request. Please quote a 5-degree TrueFlex ROADM node on the Twin 1x35 WSS with direct colorless add/drop, 18 add/drop ports per WSS, with 2 4 port OCM(s). The quote states 5 Twin WSS units. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 5-degree node on Twin 1x35 WSS, Direct add/drop, 0 transceivers, 5 Twin WSS units.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares an order for a ROADM node built from Lumentum TrueFlex parts: a Twin WSS for each degree, an add/drop stage (direct, colorless-directionless with Twin MxN, or contentionless with the Twin 8x16 Multicast Switch) and TrueFlex optical channel monitors. Before it goes out, the agent sends it to Predictika, which checks it and returns a verdict and every finding at once.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote a 8-degree TrueFlex ROADM node on the Twin 1x20 WSS. The quote states 6 Twin WSS units. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with three findings and one approval, all in one answer. The order states 6 Twin WSS units; a route-and-select node needs one Twin WSS per degree, which is 8. 1 Twin 8x16 Multicast Switch(es) are quoted; 3 are needed for the transceivers (16 per switch). 1 OCM unit(s) are quoted and the node has 8 degrees; each degree needs one monitor port.
    6. 
      
  6. The validator returned three blocking findings and one approval in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
    7. 
      
  7. What this shows: for ports that run out per degree, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the twin 8x16 Multicast Switches to 3, the OCMs to 2 x 4 port and the Stated Twin WSS units to 8.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Not blocked, but held for a person.
    12. 
      
  12. The three blocking findings are cleared; one approval remains for a person: high-degree node.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the degrees to 5 and the Stated Twin WSS units to 5.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared.
    18. 
      
  18. Four problems caught in one call, fixed in two passes, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    19.