---
title: "Scheduling"
canonical: "https://ai-docs.certero.com/space/CXCM/171278347/Scheduling"
format: markdown
---
Organizations often have non-production VMs which are not used at night or on weekends, and so running these VMs during these times may be incurring unnecessary costs. Use CerteroX FOCUS **Scheduling **reporting to analyse environments & usage and use CerteroX [Resource Schedules](https://certero.atlassian.net/wiki/spaces/CXCM/pages/108299407) to reduce spend by automatically restricting uptime of non-production VMs to permitted hours.

The FOCUS Scheduling reporting is for exploring and identifying VMs that are running full-time or for periods longer than required or expected; for example, in non-production environments where power scheduling may be implemented to reduce costs.

Use **Perspectives **and Perspective filtering to isolate VMs of interest, e.g. non-production subaccounts. Or simply set the **vtag.NonProd** filter to **True**.

Your selection in the **Minimum Hours **filter will restrict the chart columns to only count VMs that have been billed (i.e. been running) for a number of hours greater than the selection. Selecting zero will show all VMs with any billing greater than zero.

The Minimum Hours filter options include hints about their usefulness. The **(daily) **selections are most useful when the chart interval is daily, and the items like **50 hrs (10x5)** will ONLY display data for monthly intervals, because there's only 24 hours in a day.

Selecting **50 hrs (10x5)**, for example, corresponds to the 50 hours amassed by running a VM for 10 hours a day, 5 days a week (e.g. not weekends); so, selecting this and scoping on non-production indicates VMs running longer than 50 hours a week that may require power scheduling optimisation.

Similarly, filtering on non-prod, selecting **168 hrs (25x7)**, and choosing the weekly interval shows you non-prod VMs running 24x7.

> ℹ️ The non-production vtag (**vtag.NonProd**) is provided “out of the box” to identify non-prod environments. Rules for vtags can be fine-tuned, updated, replaced, etc.