Predictika · Enterprise software support orders

An AI sales agent's Rimini Street support order, checked before it goes out

An AI sales agent prepares a third-party support order for a company that runs Oracle, SAP or VMware software: the software, a Rimini plan (Support, Manage or One), the services to add, the number of production instances and environments, the countries and the term. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the offering and returns a verdict and every reason.

Scope: Rimini Street support orders for Oracle, SAP and VMware software: plan, services, instances, environments, countries and term (no prices). See everything this validator covers

This validator models Rimini Street support orders, not just the scenarios shown below.

  • Software and plan — Oracle (E-Business Suite, Database, Hyperion, JD Edwards, Fusion Middleware), SAP (ECC, S/4HANA, HANA Database, BusinessObjects) and VMware (vSphere, vSAN, Horizon) software, Rimini Custom software, and the Rimini Support, Rimini Manage and Rimini One plans that sit over them.
  • Services — security, interoperability, global tax, legal and regulatory updates, license advisory, and Rimini Govern for AI, and which plan and software each one goes with.
  • Capacity and term — production instances, non-production environments, countries covered, the length of the term, and the points at which an order goes to a person for review.

Any Rimini Street support order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices, and services outside the list above. Public versus modeled: the product and plan names, the supported Oracle, SAP and VMware software and the named service categories follow Rimini Street's public pages; the plan limits, the dependencies between plan, software and services, the term rules and the approval thresholds are modeled by Predictika from comparable offerings and are not published by Rimini Street. No prices are modeled.

The AI sales agentBuilds the support 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
Services that depend on the plan and the softwareOnly with care
Security, interoperability and Govern for AI each need a particular plan, and tax updates and the Manage plan each need particular software, so every service needs a rule that looks at fields chosen elsewhere in the order.
The software, plan and services are fields of one order and are checked together on every call.
Limits that follow the planOnly with workarounds
The instances and countries an order may have depend on the plan, so a stored table or a script has to look up the limit and compare it with the order.
The limit for the chosen plan is computed inside the validator and compared with the order on every call.
Review thresholds across several fieldsOnly with workarounds
A one-year term, many instances and many countries each need their own review route, usually outside the order.
Each review is a finding of the same call, listed next to the blocks.
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 order; approval findings need a person to sign off; everything else is computed.

1Global tax, legal and regulatory updates are modeled for ERP software (Oracle E-Business Suite, JD Edwards, SAP ECC, S/4HANA) only.
2Interoperability services need Rimini Manage or Rimini One.
3Security solutions and services need Rimini Manage or Rimini One.
4Security solutions and services are modeled for Oracle, SAP and VMware software, not for Rimini Custom software.
5Rimini Govern for AI is modeled with the Rimini One plan only.
6The Rimini Manage managed services are modeled for Oracle and SAP software, not VMware or Rimini Custom software.
7A term of 6 years is outside the 1 to 5 years modeled.
8A term of 0 years is outside the 1 to 5 years modeled.
9A one-year term is reviewed by a person before it is released.
106 production instances is over the 5 the plan takes.
1121 non-production environments is more than four per production instance (5 instances).
12Support in 4 countries is over the 3 the plan takes.
1311 production instances is over the 10 the plan takes.
1411 production instances need a scoping review by a person.
1525 production instances need a scoping review by a person.
16Support in 40 countries needs a regional coverage review by a person.
1726 production instances is over the 25 the plan takes.
1826 production instances need a scoping review by a person.
19Support in 41 countries is over the 40 the plan takes.
20Support in 41 countries needs a regional coverage review by a person.
21Support in 21 countries needs a regional coverage review by a person.
22The order states a limit of 10 production instances; this plan is modeled at 5.
23The order states a limit of 5 production instances; this plan is modeled at 10.
247 production instances is over the 5 the plan takes.
2540 non-production environments is more than four per production instance (7 instances).

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. VMware order, services and capacity: A VMware vSphere order on Rimini Support with tax, security and interoperability services, 7 production instances and 40 environments

The agent's request. Please quote the Rimini Support plan for VMware vSphere support with global tax, legal and regulatory updates, security services and interoperability services for 7 production instances and 40 non-production environments in 2 countries on a 3-year term. It is ready to send.

Verdict: Blocked.

  • Tax updates on non-ERP software. Global tax, legal and regulatory updates are modeled for ERP software (Oracle E-Business Suite, JD Edwards, SAP ECC, S/4HANA) only.
  • Interoperability services on Support plan. Interoperability services need Rimini Manage or Rimini One.
  • Security services on Support plan. Security solutions and services need Rimini Manage or Rimini One.
  • Production instances over the plan. 7 production instances is over the 5 the plan takes.
  • Too many non-production environments. 40 non-production environments is more than four per production instance (7 instances).

2. VMware order, services and capacity: The agent resubmits after fixing the errors

The agent's request. Please quote the Rimini One plan for VMware vSphere support with security services and interoperability services for 7 production instances and 28 non-production environments in 2 countries on a 3-year term. It is ready to send.

Verdict: Allowed.

  • Order summary. The plan takes up to 25 production instances and 40 countries; this order has 7 instances and 2 countries.

3. Rimini Custom order, plan and term: A Rimini Custom order on Rimini Manage with Govern for AI, security, a 6-year term and 12 countries

The agent's request. Please quote the Rimini Manage plan for Rimini Custom software support with security services and Rimini Govern for AI for 2 production instances and 4 non-production environments in 12 countries on a 6-year term. It is ready to send.

Verdict: Blocked.

  • Security services on Rimini Custom. Security solutions and services are modeled for Oracle, SAP and VMware software, not for Rimini Custom software.
  • Rimini Govern for AI off Rimini One. Rimini Govern for AI is modeled with the Rimini One plan only.
  • Rimini Manage on VMware or Custom software. The Rimini Manage managed services are modeled for Oracle and SAP software, not VMware or Rimini Custom software.
  • Term outside 1 to 5 years. A term of 6 years is outside the 1 to 5 years modeled.
  • Countries over the plan. Support in 12 countries is over the 10 the plan takes.

4. Rimini Custom order, plan and term: The agent resubmits after fixing the errors

The agent's request. Please quote the Rimini One plan for Rimini Custom software support with Rimini Govern for AI for 2 production instances and 4 non-production environments in 12 countries on a 5-year term. It is ready to send.

Verdict: Allowed.

  • Order summary. The plan takes up to 25 production instances and 40 countries; this order has 2 instances and 12 countries.

5. SAP S/4HANA order, capacity and review: An SAP S/4HANA order on Rimini Support with tax updates, 6 production instances in 4 countries and a one-year term

The agent's request. Please quote the Rimini Support plan for SAP S/4HANA support with global tax, legal and regulatory updates for 6 production instances and 20 non-production environments in 4 countries on a 1-year term. It is ready to send.

Verdict: Blocked.

  • Production instances over the plan. 6 production instances is over the 5 the plan takes.
  • Countries over the plan. Support in 4 countries is over the 3 the plan takes.
  • One-year term to confirm. A one-year term is reviewed by a person before it is released.

6. SAP S/4HANA order, capacity and review: The agent resubmits after fixing the errors

The agent's request. Please quote the Rimini Manage plan for SAP S/4HANA support with global tax, legal and regulatory updates for 6 production instances and 20 non-production environments in 4 countries on a 3-year term. It is ready to send.

Verdict: Allowed.

  • Order summary. The plan takes up to 10 production instances and 10 countries; this order has 6 instances and 4 countries.

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 third-party support order for a company that runs Oracle, SAP or VMware software: the software, a Rimini plan (Support, Manage or One), the services to add, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the offering and returns a verdict and every reason.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote the Rimini Support plan for VMware vSphere support with global tax, legal and regulatory updates, security services and interoperability services for 7 production instances and 40 non-production environments in 2 countries on a 3-year term. It is ready to send.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with five findings, all in one answer. Global tax, legal and regulatory updates are modeled for ERP software (Oracle E-Business Suite, JD Edwards, SAP ECC, S/4HANA) only. Interoperability services need Rimini Manage or Rimini One. Security solutions and services need Rimini Manage or Rimini One. The other two are on screen.
  6. The validator returned five blocking findings 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 services that depend on the plan and the software, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the plan to Rimini One and the non-production environments to 28. It removes the tax and regulatory updates.
  10. It calls the validator again.
  11. This time the validator clears it.
  12. All five earlier findings are cleared.
  13. Five 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.