--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Automation projects # Automation projects {#ariaid-title1} Release version: Australia Updated August 27, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Automation projects Automation projects in ServiceNow's LEAP enable teams or business units to independently analyze sets of incident data for tailored automation insights. Each project is configured with its own scope, filters, taxonomies, and schedules, allowing multiple projects to run concurrently without impacting each other. This approach facilitates focused incident grouping, analysis, and automation opportunity generation based on specific criteria such as assignment groups, time periods, or business needs. Show full answer Show less ## Key Features * **Independent Analysis:** Multiple projects can analyze different incident subsets concurrently, supporting team-specific or regional automation strategies. * **Flexible Taxonomy Configuration:** Choose one or more taxonomies per project to align incident grouping with your team's classification requirements. * **Project-specific Dashboards:** Access real-time metrics, reports, and automation opportunities unique to each project. * **Configurable Analysis Scheduling:** Set independent job frequencies for each project to automate periodic data analysis. * **Default Automation Project:** A read-only baseline project exists for legacy setups, managed via the AI Admin Workspace. * **Opt-in Capability:** Automation projects are optional and can be added without impacting existing configurations or running jobs. ## Practical Use Cases * **Per-Team Automation:** Separate projects for different IT teams to address unique incident patterns and automation needs. * **Per-Region Automation:** Distinct projects for geographic regions to accommodate variations in ticket volume and service levels. * **Per-Service-Tier Automation:** Dedicated projects for critical services, isolating important incidents from general cases. * **Pilot Testing:** Isolated projects for trial runs before broader automation rollout, ensuring controlled evaluation. * **Business Unit Isolation:** Projects scoped by assignment groups to provide business units with relevant, non-overlapping automation recommendations. * **Sandbox Testing:** Use filtered, smaller datasets in separate projects to safely test changes without impacting production data. ## Automation Project Lifecycle * **Create Project:** Define project parameters including filters, taxonomies, and schedule. * **Start Grouping Job:** Run analysis jobs to generate automation insights; project settings are locked during analysis. * **Review and Act:** Examine automation opportunities, create resolution steps, and measure impact. * **Switch Projects:** Easily toggle between projects to view different data sets and corresponding automation results. * **Edit Configurations:** Modify project settings when analysis jobs are not running or have completed. ## Configuration Considerations * Taxonomy selection supports multiple values, enabling overlapping incident groupings across projects. * Filter queries are limited to 300 characters; filters returning no records are invalid. * This release supports analysis only on the incident table. * Prediction logic runs on the Default project for all incidents plus any projects matching the incident's assignment group. Use Automation projects to analyze multiple sets of incident data independently, so different teams or business units can derive separate insights and automation opportunities. An Automation project defines the scope and configuration for LEAP analysis. Each project runs independently and can target specific assignment groups, time periods, or filtered sets of incidents. By creating multiple Automation projects, you can analyze different categories of incidents separately and generate automation opportunities tailored to each context. ## Benefits of Automation projects {#automation-projects-leap__section_benefits} Automation projects provide the following benefits: * Team-specific insights: Different teams or business units can work on separate projects concurrently without affecting each other's analysis, metrics, or automation opportunities. * Analyze multiple data sets independently: Create separate projects to analyze different groups of incidents based on assignment groups, time periods, or other criteria. For example, analyze the last 6 months of Human Resources incidents in one project while creating a focused project for last month's spike in cases. * Flexible taxonomy configuration: Select one or more taxonomies per project to group incidents according to your team's classification needs. Multiple projects can use the same taxonomy when analyzing different subsets of data. * Real-time dashboard views: Switch between projects to view project-specific metrics, reports, and automation opportunities in the dashboard. * Configurable analysis schedule: Schedule analysis jobs to run at specified frequencies for each project independently. Each Automation project has its own independent configuration: incident, filter, grouping column, taxonomy selection, job frequency, and settings. Projects run without affecting each other. ## When to use Automation projects {#automation-projects-leap__section_use_cases} The following examples illustrate common scenarios where creating multiple Automation projects provides more relevant and actionable results than a single shared project. Per-team automation : A large IT organization wants Network team incidents grouped and automated separately from Database team incidents. Because issue patterns, root causes, and resolution steps differ significantly between teams, each team gets its own project instead of a single mixed pool of recommendations. Per-region automation : A global company wants automation tuned separately for APAC and EMEA support teams. Ticket volume, categories, and SLAs vary by region, so separate projects confirm that grouping and recommendations reflect each region's specific incident patterns. Per-service-tier automation : A customer wants to separate automation for critical Tier-1 services, such as banking systems and core infrastructure, from general Tier-2 and Tier-3 services. Keeping high-priority incidents in a dedicated project prevents lower-priority noise from diluting the grouping and resolution logic for business-critical systems. Controlled pilot before a wider rollout : A customer wants to try LEAP automation on one team's data first before expanding to the rest of the organization. Creating a separate project for the pilot team keeps the trial isolated from the default project that is already running in production. Business unit isolation : A company with multiple business units, each using ServiceNow with different assignment groups, wants each unit to see automation results relevant only to their own incidents. Separate projects scoped by assignment group ensure that each business unit's recommendations are not mixed with those of other units. Testing and sandbox configuration : An administrator wants to test grouping or filter changes safely before applying them to the production setup. A separate project scoped to a small filtered set of records acts as a sandbox, leaving the default project and its running jobs unaffected. ## Default Automation project {#automation-projects-leap__section_default_project} The Default Automation project is shipped with the LEAP. The Default project represents the existing pre-multi-project setup and has no taxonomy configuration and is read-only. You can view its configuration but can't edit it from the Automation project details page. To change the default configuration, use the AI Admin Workspace. Note: * The initial setup experience for LEAP remains unchanged. When you first activate LEAP, you must still configure the default project through the AI Admin Workspace. Automation projects is an additional capability that is available after the default project is set up. * Skill activation occurs in the AI Admin workspace. Automation projects are an opt-in capability. Existing deployments continue to work without modification. You don't have to migrate your current configuration to use Automation projects. Adding a new project does not change the Default Automation project or any currently running analysis jobs. ## Automation project lifecycle {#automation-projects-leap__section_project_lifecycle} Managing Automation projects involves creating new projects, running analysis jobs, and switching between projects to view different automation opportunities. The following workflow describes the complete lifecycle: 1. Create the project: Define the project name, description, table, filter, grouping column, topic column, taxonomy/assignment group, and job frequency. The project is created in a ready (editable) state and can be viewed directly on the projects details screen or the homepage. No analysis runs at this point. 2. Start the grouping job: After the project configuration is complete, start the analysis job. Starting the job clones the required skills in the back end and activates the scheduled job. Once analysis begins, the project configuration can't be edited until the job completes or the job status is *ready* or *failed*. 3. Review automation opportunities: After the analysis completes, review automation opportunities, create resolution steps, and measure impact. The day-to-day experience is the same as the standard LEAP workflow. 4. Switch between projects: Switch between projects to view different sets of automation opportunities. Switching between projects updates data on every page and the LEAP value dashboard to reflect the selected project's data set. 5. Edit project configurations: Edit project configurations as needed. You can only edit a project when its job status is *ready* or *failed*. ## Configuration constraints {#automation-projects-leap__section_constraints} When configuring an Automation project, be aware of the following constraints: * The taxonomy field is multi-select. You can select one or more taxonomies to define which incident groups the project analyzes. * Multiple projects can use the same taxonomy. When an incident matches multiple projects, playbooks from all matching projects are displayed. * Filter queries are limited to 300 characters. Filters that return zero records are marked as an error before the project is saved. * This release supports only the incident table. ## Taxonomy filtering {#automation-projects-leap__section_taxonomy_filtering} Selected taxonomies dictate the filter query for an Automation project. For example, if you select assignment groups AG1 and AG2, the system creates a filter where the assignment group is one of AG1 or AG2. ## Prediction logic {#automation-projects-leap__section_prediction_logic} When an incident is created or updated, LEAP determines which Automation projects run predictions based on the incident's assignment group: * The Default Automation project always runs predictions regardless of the assignment group. * If an incident has a specific assignment group, predictions run on the Default project plus any Automation projects that match that assignment group.