--- sourceDocument: Australia Platform Analytics sourceDocumentLink: https://www.servicenow.com/docs/r/australia/now-intelligence Release : - australia ft:locale : - en-US ft:publication_title : - Australia Platform Analytics ft:clusterId : - par bundleId : - par workflow : - Platform --- # Meter-based guardrails and controls # Meter-based guardrails and controls {#ariaid-title1} Release version: Australia Updated August 18, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Meter-based guardrails and controls Meter-based guardrails and controls help ServiceNow customers monitor and manage their record usage to avoid unexpectedly exceeding their entitled record count during process mining activities. These controls apply specifically to subscriptions using meter-based or AI Native SKUs, ensuring mining operations stay within license limits. Show full answer Show less ## Key Features * **Table-level guardrails:** Administrators can set mandatory filter conditions on tables (e.g., limiting cases to those resolved in the last 12 months). These filters are enforced on all projects using that table, ensuring projects cannot bypass essential constraints, although project creators may add additional filters. * **Entitlement enforcement:** The system blocks mining in several scenarios: when a project's record count exceeds remaining entitlement, when full entitlement for the contract period is used, or when record counts with crop or transition conditions exceed five times the entitlement. Otherwise, mining proceeds. * **Usage measurement and reporting:** Usage is tracked per table and per day for AI Native SKU customers, offering granular insight into which areas consume capacity. Usage resets annually on the contract anniversary date. Records filtered out by crop or transition conditions do not count toward usage. * **Administrative overrides:** Administrators can disable entitlement checks entirely via a system property (promin.meteredusage.allowunrestricted), allowing unrestricted mining with the understanding that any overages will be billed at contract end. * **Grace on first overage:** The first time mining results push usage over the entitlement, the system only counts records up to the remaining entitlement and discards the excess without charging. Subsequent attempts are blocked until entitlement is renewed. ## Practical Application ServiceNow administrators should create table-level guardrails with mandatory filter conditions to prevent inefficient or excessive mining configurations that consume unnecessary record capacity. Understanding entitlement enforcement rules helps avoid blocked mining attempts and potential overage charges. Monitoring usage by table enables better governance and resource allocation across departments or use cases. Meter-based guardrails and controls help you in identifying situations when you unexpectedly exceed your entitled record count. ## How it works {#meter-based-guardrails__section_how_it_works} There are two types of guardrails: * Table-level guardrails: An administrator can define one mandatory filter condition per table (for example, "only cases resolved in the last 12 months"). Once active, this condition is automatically applied to every project built on that table. The person creating the project can add their own filters on top, but can't remove or edit the administrator's condition. * Entitlement enforcement: This only applies if your subscription uses a meter-based or AI Native SKU. If you're on a different license type, the platform's existing licensing checks apply instead. When you mine a project, the system checks your project's scope against your remaining entitlement: * If the project's total record count already exceeds your entitlement, mining is blocked. * If you've already used your full entitlement for the current contract period, mining is blocked, regardless of project size. * If your project uses a crop or transition condition and its record count is more than 5 times your entitlement, mining is blocked. * In every other case, mining is allowed. ## How your usage is measured and reported {#meter-based-guardrails__section_usage_reporting} An administrator can override the block entirely using the system property (promin.metered_usage.allow_unrestricted). This disables entitlement checks and allows unrestricted mining (with the understanding that overages will be billed at the end of the contract period). For more information on promin.metered_usage.allow_unrestricted, see [Process Mining properties](https://www.servicenow.com/docs/YFBGZfo3RKe0RYgcwwLYpw#po-properties "System properties control system behavior. The properties in this section are specific to the Process Mining application."). If mining is allowed but the results would put you over your entitlement for the first time, the system doesn't charge you for the overage. It counts records toward your usage only up to your remaining entitlement, and quietly discards the rest. The next time you try to mine, you will have 0 remaining records and will be blocked. If you're on the AI Native SKU, your consumption is tracked per table, per day; not just as a single monthly total. This gives you visibility into which tables (and by extension, which departments or use cases) are driving your consumption. This is useful if your organization mines records across multiple areas, such as ITSM and HR, at the same time. Your usage resets on your contract anniversary date. The date your current contract term began, recalculated each year your contract renews, rather than on a rolling 365-day lookback. This is the same anniversary date used to determine your remaining entitlement when you mine a project. If your project uses a crop or transition condition, only the records that remain after that condition is applied count toward your usage. * **[Create a table-level guardrail](https://www.servicenow.com/docs/UBUU2T4ODrnRCidhpFdA6g)** Define a mandatory filter condition for a table to prevent projects from being configured in ways that consume more mining capacity than necessary. **Related tasks** * [Create a table-level guardrail](https://www.servicenow.com/docs/UBUU2T4ODrnRCidhpFdA6g "Define a mandatory filter condition for a table to prevent projects from being configured in ways that consume more mining capacity than necessary.")