Predictika · Mainframe platform and software orders

An AI sales agent's ClearPath Forward MCP order, checked before it goes out

An AI sales agent prepares a monthly order for a Unisys ClearPath Forward MCP environment, with a Libra system or MCP Software Series platform, a software tier, capacity in MIPS, partitions, MCP Developer Studio seats, a support level, a term and the monthly charge the order states. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the platforms, tiers and order rules and returns a verdict, every reason and the monthly charge it computed.

Scope: Unisys ClearPath Forward MCP orders: Libra 4591, 6591 and 8591 systems and MCP Software Series on VMware, Hyper-V or a public cloud, the Bronze to Titanium software tiers, capacity, partitions, MCP Developer Studio, support, term and the monthly charge. See everything this validator covers

This validator models ClearPath Forward MCP orders, not just the scenarios shown below.

  • Platform, tier and capacity — the capacity steps from 50 to 8,000 MIPS, the MIPS limit of each software tier and of each platform, and the partitions each platform supports with at least 50 MIPS in each.
  • Restrictions between choices — MCP Software Series in a public cloud needs the Gold tier or higher, the Libra 8591 is not sold with the entry tiers, Premium support is not offered with Bronze, and each MCP Developer Studio edition goes with certain tiers and needs seats.
  • Approvals, term and charge — large capacity, many partitions, a 60-month cloud term and more than 50 developer seats need a person to sign off, and the monthly charge the order states must match the charge computed from the order.

Any ClearPath Forward MCP order that touches these rules is in scope — not only the scenarios pictured here. Not covered: Dorado systems, services work, hardware maintenance and other Unisys products. The product names (Libra 4591, 6591 and 8591, MCP Software Series, the Bronze to Titanium tiers and MCP Developer Studio) come from public Unisys material; the capacity steps, tier and platform limits, partition limits, restrictions, approval thresholds and every price are modeled from comparable products and are not published by Unisys, so all figures are illustrative.

The AI sales agentBuilds the ClearPath Forward MCP 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.

6 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
Limits that depend on the platform and the tierOnly with care
Capacity has one maximum per software tier and another per platform, and partitions have a third, so each limit needs its own list and the lower one must win.
The platform, tier, capacity and partitions are in one request and every limit is checked together on every call.
Choices that are not sold togetherOnly with care
Cloud with entry tiers, the largest system with entry tiers, Premium support with Bronze and each Developer Studio edition with certain tiers are all pairs, so each pair needs a rule that looks at both sides.
All the choices are in the request, so every pair is checked on every call whatever order they were made in.
Seats that need an edition, and an edition that needs seatsOnly with workarounds
The seats and the edition are chosen on different steps, so a rule has to wait until both are known and then check them against each other in both directions.
Edition and seats are fields of the same request and are checked against each other on every call.
Approvals that depend on size, partitions, term and platformOnly with workarounds
Each approval has its own trigger and some depend on two choices at once, such as the cloud platform and a 60-month term, so they have to be kept apart from the blocks.
Blocks and approvals are separate findings returned together, so the order is never both stopped and approved by mistake.
A stated monthly charge that must match the computed chargeOnly with workarounds
The charge is built from the platform, capacity, partitions, seats, support and term, so a separate rule must recompute it and compare it with the stated figure.
The stated charge is a field of the request and is compared with the computed charge on every call, together with every other finding.

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 order; approval findings need a person to sign off; everything else is computed.

1600 MIPS is not an offered capacity step; capacity is ordered from 50 to 8,000 MIPS in the listed steps.
2300 MIPS is above the 200 MIPS limit of the selected software tier.
34,000 MIPS is above the 3,000 MIPS limit of the selected platform.
48,000 MIPS is a large configuration and needs a solution architect review.
5A Libra 8,591 system is sold with the Gold, Platinum or Titanium tier; the order has Bronze.
6MCP Software Series in a public cloud needs the Gold tier or higher; the order has Silver on the cloud platform.
7A 60-month term on the cloud platform needs a finance check on the cloud provider commitment.
83 partitions is more than the 2 the selected platform supports.
9The order needs at least one partition; it has 0.
106 partitions need a capacity planning review before they are quoted.
1150 MIPS cannot be shared by 2 partitions; each partition needs at least 50 MIPS.
12The order has 10 MCP Developer Studio seats but no edition is selected.
13A Developer Studio edition is selected but the order has 0 seats.
14The Titanium edition of MCP Developer Studio goes with the Platinum or Titanium software tier; the order has Gold.
15The Platinum edition of MCP Developer Studio goes with the Gold tier or higher; the order has Silver.
1651 Developer Studio seats is above the usual team size and needs a sales manager sign-off.
17Premium support is not offered with the Bronze tier; the order has Bronze.
18The order states a monthly charge of 1,000 cents; the quote computes 2,530,000 cents.

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. Platform, tier and capacity limits: A Libra 4591 Bronze order with 6,000 MIPS, seven partitions, Premium support and 60 Titanium Developer Studio seats

The agent's request. Please quote a ClearPath Forward MCP order on Libra 4591, Bronze tier, with 6,000 MIPS in 7 partitions, Premium support, a 36-month term, and MCP Developer Studio Titanium edition for 60 seats, for a monthly charge of $50. It is ready to send.

Verdict: Blocked.

  • Capacity above the tier limit. 6,000 MIPS is above the 200 MIPS limit of the selected software tier.
  • Capacity above the platform limit. 6,000 MIPS is above the 1,000 MIPS limit of the selected platform.
  • Too many partitions for the platform. 7 partitions is more than the 2 the selected platform supports.
  • Titanium Developer Studio on a lower tier. The Titanium edition of MCP Developer Studio goes with the Platinum or Titanium software tier; the order has Bronze.
  • Premium support on the Bronze tier. Premium support is not offered with the Bronze tier; the order has Bronze.
  • Stated monthly charge does not match. The order states a monthly charge of 5,000 cents; the quote computes 28,433,200 cents.
  • Capacity of 5000 MIPS or more. 6,000 MIPS is a large configuration and needs a solution architect review.
  • Six or more partitions. 7 partitions need a capacity planning review before they are quoted.
  • More than 50 developer seats. 60 Developer Studio seats is above the usual team size and needs a sales manager sign-off.

2. Platform, tier and capacity limits: The agent resubmits after fixing the errors

The agent's request. Please quote a ClearPath Forward MCP order on Libra 8591, Titanium tier, with 4,000 MIPS in 4 partitions, Standard support, a 36-month term, and MCP Developer Studio Titanium edition for 20 seats, for a monthly charge of $119,104. It is ready to send.

Verdict: Allowed.

  • Order summary. 4,000 MIPS in 4 partition(s); modeled monthly charge 11,910,400 cents, contract value 428,774,400 cents.

3. Cloud platform and Developer Studio: A cloud order on the Silver tier with 2,000 MIPS, Team Developer Studio and a 60-month term

The agent's request. Please quote a ClearPath Forward MCP order on MCP Software Series in a public cloud, Silver tier, with 2,000 MIPS in 2 partitions, Standard support, a 60-month term, and MCP Developer Studio Team edition for 0 seats, for a monthly charge of $61,680. It is ready to send.

Verdict: Blocked.

  • Capacity above the tier limit. 2000 MIPS is above the 500 MIPS limit of the selected software tier.
  • Capacity above the platform limit. 2000 MIPS is above the 1,500 MIPS limit of the selected platform.
  • Cloud deployment on an entry tier. MCP Software Series in a public cloud needs the Gold tier or higher; the order has Silver on the cloud platform.
  • Developer Studio edition without seats. A Developer Studio edition is selected but the order has 0 seats.
  • Cloud platform on a 60-month term. A 60-month term on the cloud platform needs a finance check on the cloud provider commitment.

4. Cloud platform and Developer Studio: The agent resubmits after fixing the errors

The agent's request. Please quote a ClearPath Forward MCP order on MCP Software Series in a public cloud, Gold tier, with 1,000 MIPS in 2 partitions, Standard support, a 36-month term, and MCP Developer Studio Team edition for 5 seats, for a monthly charge of $28,670. It is ready to send.

Verdict: Allowed.

  • Order summary. 1,000 MIPS in 2 partition(s); modeled monthly charge 2,867,000 cents, contract value 103,212,000 cents.

5. System limits and edition pairing: A Libra 4591 order with 1,500 MIPS, three partitions, Premium support and Titanium Developer Studio on the Gold tier

The agent's request. Please quote a ClearPath Forward MCP order on Libra 4591, Gold tier, with 1,500 MIPS in 3 partitions, Premium support, a 36-month term, and MCP Developer Studio Titanium edition for 5 seats, for a monthly charge of $51,556. It is ready to send.

Verdict: Blocked.

  • Capacity above the platform limit. 1,500 MIPS is above the 1,000 MIPS limit of the selected platform.
  • Too many partitions for the platform. 3 partitions is more than the 2 the selected platform supports.
  • Titanium Developer Studio on a lower tier. The Titanium edition of MCP Developer Studio goes with the Platinum or Titanium software tier; the order has Gold.
  • Stated monthly charge does not match. The order states a monthly charge of 5,155,600 cents; the quote computes 5,275,600 cents.

6. System limits and edition pairing: The agent resubmits after fixing the errors

The agent's request. Please quote a ClearPath Forward MCP order on Libra 6591, Platinum tier, with 1,500 MIPS in 3 partitions, Premium support, a 36-month term, and MCP Developer Studio Titanium edition for 5 seats, for a monthly charge of $55,496. It is ready to send.

Verdict: Allowed.

  • Order summary. 1,500 MIPS in 3 partition(s); modeled monthly charge 5,549,600 cents, contract value 199,785,600 cents.

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 a monthly order for a Unisys ClearPath Forward MCP environment, with a Libra system or MCP Software Series platform. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the platforms, tiers and order rules and returns a verdict, every reason and the monthly charge it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote a ClearPath Forward MCP order on Libra 4591, Bronze tier, with 6,000 MIPS in 7 partitions, Premium support. It is ready to send. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with six findings and three approvals, all in one answer. 6,000 MIPS is above the 200 MIPS limit of the selected software tier. 6,000 MIPS is above the 1,000 MIPS limit of the selected platform. 7 partitions is more than the 2 the selected platform supports. The other three are on screen.
  6. The validator returned six blocking findings and three approvals 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 order are checked against each other.
  7. What this shows: for a stated monthly charge that must match the computed charge, a rules-based CPQ can do this only with workarounds.
  8. Now the agent resubmits.
  9. The corrected request. It changes the platform to Libra 8591, the software tier to titanium, the capacity to 4,000 MIPS, the partitions to 4 and the monthly charge stated on the order to $119,104. Two more changes are on screen.
  10. It calls the validator again.
  11. This time the validator clears it.
  12. All nine earlier findings are cleared.
  13. Nine problems caught in one call, fixed in one pass, and a clean order. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.