Predictika · NetApp Keystone storage-as-a-service

An AI sales agent's Keystone subscription or change, checked before it goes out

An AI sales agent prepares a NetApp Keystone request: a new subscription or a change to an existing one, with the platform, service level, committed capacity per instance, burst limit, billing frequency and term. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of NetApp's published Keystone rules and returns a verdict, every reason, and the total commitment and burst limit it computed.

Source and independence. The rules come from NetApp's public Keystone documentation: the service levels, capacity requirements, supported storage capacity and pricing pages. NetApp is not involved in this demonstration and has not endorsed it. The customer is fictional. This validator produces no prices and no line-item quote: NetApp does not publish Keystone rates, so any payment amount a request carries is supplied by the customer's own system and is labeled that way.

Scope: NetApp Keystone STaaS subscriptions: service level by platform, committed capacity, burst limit, billing and changes to a subscription. See everything this validator covers

This validator handles any new Keystone subscription or change request on these platforms — not just the scenarios shown below.

  • Service level by platform — Extreme and Premium on AFF A-Series and ASA A-Series, Standard on AFF C-Series and ASA C-Series, Value on FAS, Extreme on AFX, Standard on StorageGRID SGF6112, Value on StorageGRID SG6160, and Cloud Volumes ONTAP. (Service levels)
  • Minimum and step — The minimum committed capacity for each platform and a capacity step, taken from NetApp's tables. Assumption: the validator applies a 25 TiB step to every service level; NetApp publishes that step for some levels and different figures for AFX, StorageGRID and Cloud Volumes ONTAP, so the step is an assumption to check against NetApp's current terms. NetApp's current Keystone documentation also groups storage as Unified, Block-optimized, AFX and Object; this validator uses the Extreme, Premium, Standard and Value names. (Service levels, capacity requirements)
  • Capacity type — Logical or physical for unified and block-optimized storage; physical only for AFX and object storage; logical for Cloud Volumes ONTAP. The commitment is per performance service level instance (PSLI) for unified and block-optimized storage, per AFX cluster, or per order, as NetApp publishes it. NetApp's pages do not define a PSLI in terms of HA pairs; this validator simply counts the instances the request states.
  • Burst — Burst limits of 20, 40 or 60 percent of the commitment (40 and 60 percent for unified and block-optimized storage only), the 60-day burst waiver from the start date, and usage above the limit flagged as “Above burst limit”. (Supported storage capacity, pricing)
  • Billing frequency — Monthly, quarterly, semi-annual or annual. (Pricing)
  • Changes — Increases (not within the last 90 days before expiry unless renewing), moving to a higher service level (allowed) or a lower one (not allowed), and reductions (Annual in Advance on-premises only, term of at least 24 months, written notice at least 60 days, the number of reductions by term length, at most 25 percent of the commitment, the platform minimum, annual payments of at least $200,000 after the reduction, and none for cloud services). (Capacity requirements)
  • Stated figures — The total commitment and burst limit stated in the request are compared with the ones computed.

Not covered: Keystone rates and prices, true-up, renewal terms and Keystone Sovereign, because NetApp does not publish them; hardware purchases; and NetApp's own order system. Inputs supplied by the customer rather than published by NetApp: the expected consumption, the annual payment after a reduction, the days left to expiry and the reductions already used. The cases here are examples; the rules are NetApp's.

The AI sales agentBuilds the Keystone request from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed commitment and burst limit.

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
Minimum and 25 TiB step by platform and service level, with a different unit per platform (service level instance, AFX cluster, order)Only with care
A product rule per platform. It works, but each platform adds a minimum, a step and a unit that must be kept in step with NetApp's tables.		One platform table; the checks follow from the platform chosen, in any order.
A reduction that must satisfy seven conditions together: Annual in Advance, term of at least 24 months, 60 days' notice, the number allowed by term, 25 percent cap, platform minimum and the $200,000 payment floorOnly with workarounds
Several of the inputs, such as notice given and reductions already used, are not on the quote and have to be added as fields, and the rules interact. Usually built as separate validation rules that report one at a time.		All seven are checked on every call and every failure comes back together.
Increase blocked in the last 90 days before expiry unless renewingOnly with workarounds
Days to expiry live on the contract, not the quote, so the rule needs the contract date copied onto the quote.		The days left and the renewal flag travel with the request and are checked with everything else.
Total commitment and burst limit stated in the request vs the ones the rules produceOnly with care
A validation rule can compare a stated figure with a calculated one, but only if the stated figure is a field on the quote, which it rarely is.		The stated figures travel with the request and are compared with the computed ones on every call.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote 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 request; warnings and notes are returned with it.

    
1The Keystone Value performance service level is not offered on AFF A-Series; AFF A-Series offers the Extreme and Premium levels.
2A committed capacity of 150 TiB per AFX cluster is below the 200 TiB minimum for AFX.
3A committed capacity of 150 TiB per AFX cluster is not a multiple of the 100 TiB increment for AFX.
4AFX capacity is committed and metered as physical capacity; logical capacity was selected.
5A burst limit of 40 percent is available only for unified and block-optimized storage; AFX offers only the default 20 percent.
6A committed capacity of 550 TiB per order is not a multiple of the 100 TiB increment for StorageGRID SG6160.
7A committed capacity of 3 TiB per order is below the 4 TiB minimum for Cloud Volumes ONTAP.
8Cloud Volumes ONTAP capacity is committed and metered as logical capacity; physical capacity was selected.
9A burst limit of 50 percent is not offered; the choices are 20, 40 or 60 percent.
10Committed capacity cannot be increased in the last 90 days before the subscription expires unless it is being renewed; 60 days left.
11An increase must raise the commitment; 100 TiB per instance is not above the current 100 TiB.
12Committed capacity for cloud services cannot be reduced during the subscription term.
13A reduction applies only to subscriptions on the Annual in Advance payment model; this subscription is billed monthly.
14A reduction needs a subscription term of at least 24 months; this term is 12 months.
15A 36-month term permits 1 reduction in total; 1 already used.
16A reduction cannot take the committed capacity to 45 TiB per service level instance, below the 50 TiB minimum.
17Annual payments after the reduction must stay at or above $200,000; the payment stated is $150,000.
18The Keystone Premium performance service level is not offered on FAS; FAS offers the Value level.
19Moving to a lower performance service level is not permitted; Premium is below Extreme.
20A reduction of 35 percent exceeds the 25 percent limit per request.
21A reduction request must reach NetApp in writing at least 60 days before the next annual period; 45 days of notice was given.
22The request states 240 TiB committed in total; the validator computes 250 TiB.
23The request states a burst limit of 288 TiB; the validator computes 300 TiB.

  

  

    
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. Reducing a commitment: Reduction from 60 to 40 TiB with 45 days of notice

    
The agent's request. Please reduce the Extreme subscription on AFF A-Series from 60 to 40 TiB per service level instance (1 instance), billed annually in advance on a 36-month term, with 45 days of written notice. Annual payments after the reduction will be $150,000. The customer expects to use about 44 TiB. The request states 40 TiB total committed and a burst limit of 48 TiB. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Reduction above 25 percent. A reduction of 33.33 percent exceeds the 25 percent limit per request.
    • 
      
  • Below the published minimum. A reduction cannot take the committed capacity to 40 TiB per service level instance, below the 50 TiB minimum.
    • 
      
  • Reduction notice too short. A reduction request must reach NetApp in writing at least 60 days before the next annual period; 45 days of notice was given.
    • 
      
  • Annual payments below the floor. Annual payments after the reduction must stay at or above $200,000; the payment stated is $150,000.
    • 
    

    
2. Reducing a commitment: The agent resubmits after fixing the errors

    
The agent's request. Please reduce the Extreme subscription on AFF A-Series from 60 to 50 TiB per service level instance (1 instance), billed annually in advance on a 36-month term, with 45 days of written notice. Annual payments after the reduction will be $260,000. The customer expects to use about 44 TiB. The request states 50 TiB total committed and a burst limit of 60 TiB. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Reduction notice too short. A reduction request must reach NetApp in writing at least 60 days before the next annual period; 45 days of notice was given.
    • 
    

    
3. Reducing a commitment: The agent resubmits after fixing the errors

    
The agent's request. Please reduce the Extreme subscription on AFF A-Series from 60 to 50 TiB per service level instance (1 instance), billed annually in advance on a 36-month term, with 75 days of written notice. Annual payments after the reduction will be $260,000. The customer expects to use about 44 TiB. The request states 50 TiB total committed and a burst limit of 60 TiB. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Subscription summary. 1 service level instance of 50 TiB committed on AFF A-Series at the Keystone Extreme performance service level, with a burst limit of 60 TiB (20 percent above the commitment), billed annually in advance on a 36-month term.
    • 
    

    
4. Minimum commitment: Standard on AFF C-Series below the published minimum

    
The agent's request. Please set up a Keystone Standard subscription on AFF C-Series: 2 service level instances at 75 TiB each, committed on logical capacity, 20 percent burst limit, billed annually, 36-month term. The customer expects to use about 230 TiB. The request states 150 TiB total committed and a burst limit of 180 TiB. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Below the published minimum. A committed capacity of 75 TiB per service level instance is below the 100 TiB minimum for AFF C-Series.
    • 
      
  • Expected use above the burst limit. Expected consumption of 230 TiB is above the burst limit of 180 TiB; usage above the limit is flagged as Above burst limit.
    • 
    

    
5. Minimum commitment: The agent resubmits after fixing the errors

    
The agent's request. Please set up a Keystone Standard subscription on AFF C-Series: 2 service level instances at 125 TiB each, committed on logical capacity, 20 percent burst limit, billed annually, 36-month term. The customer expects to use about 230 TiB. The request states 250 TiB total committed and a burst limit of 300 TiB. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Subscription summary. 2 service level instances at 125 TiB each, 250 TiB committed in total on AFF C-Series at the Keystone Standard performance service level, with a burst limit of 300 TiB (20 percent above the commitment), billed annually in advance on a 36-month term.
    • 
    

    
6. Capacity steps: Premium on ASA A-Series, capacity not in 25 TiB steps

    
The agent's request. Please set up a Keystone Premium subscription on ASA A-Series: 3 service level instances at 130 TiB each, committed on logical capacity, 20 percent burst limit, billed annually, 36-month term. The customer expects to use about 340 TiB. The request states 390 TiB total committed and a burst limit of 468 TiB. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Capacity not in 25 TiB steps. A committed capacity of 130 TiB per service level instance is not a multiple of the 25 TiB increment for ASA A-Series.
    • 
    

    
7. Capacity steps: The agent resubmits after fixing the errors

    
The agent's request. Please set up a Keystone Premium subscription on ASA A-Series: 3 service level instances at 125 TiB each, committed on logical capacity, 20 percent burst limit, billed annually, 36-month term. The customer expects to use about 340 TiB. The request states 375 TiB total committed and a burst limit of 450 TiB. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Subscription summary. 3 service level instances at 125 TiB each, 375 TiB committed in total on ASA A-Series at the Keystone Premium performance service level, with a burst limit of 450 TiB (20 percent above the commitment), billed annually in advance on a 36-month term.
    • 
    

  

  

    
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 NetApp Keystone request: a new subscription or a change to an existing one. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of NetApp's published Keystone rules and returns a verdict, every reason, and the total commitment and burst limit it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please reduce the Extreme subscription on AFF A-Series from 60 to 40 TiB per service level instance (1 instance), billed annually in advance on a 36-month term. Annual payments after the reduction will be $150,000. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with four findings, all in one answer. A reduction of 33.33 percent exceeds the 25 percent limit per request. A reduction cannot take the committed capacity to 40 TiB per service level instance, below the 50 TiB minimum. A reduction request must reach NetApp in writing at least 60 days before the next annual period; 45 days of notice was given. The other one is on screen.
    6. 
      
  6. The validator returned four 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 request are checked against each other.
    7. 
      
  7. What this shows: for a reduction that must satisfy seven conditions together: Annual in Advance, term of at least 24 months, 60 days' notice, the number allowed by term, 25 percent cap, platform minimum and the $200,000 payment floor, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the committed capacity per instance to 50 TiB, the annual payments after the reduction to $260,000, the quoted total committed to 50 TiB and the quoted burst limit to 60 TiB.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with one finding, all in one answer. A reduction request must reach NetApp in writing at least 60 days before the next annual period; 45 days of notice was given.
    12. 
      
  12. Three findings cleared; still blocked on reduction notice too short.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the written notice to 75 days.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared, and the validator's figure matches the request.
    18. 
      
  18. Four problems caught in one call, fixed in two passes, and a clean request. That is the value of Predictika's validator: catching mistakes before the action runs.
    19.