Automation | mc Help Center

Last modified: 2026-01-23

Module description

Automation is a license-based VCOM module designed to automate recurring Operations & Maintenance (O&M) processes, such as scheduling routine maintenance tasks, calculating yield loss due to curtailments, and creating tickets based on alarms.

Automation is included in the package for premium partners and is available to other partners as an additional paid module.

Scope and purpose

Key features of the Automation module include:

Automatically create tickets for all your systems simultaneously.
Automation types:
Can be used in conjunction with CMMS and the O&M app. In this case, the Automation module replaces the Regular events portlet.

Target group

The Automation module is intended for O&M managers, service technicians, and service teams.

Automation overview

	Name	Description
1	New automation	Create new automation.
2	Further actions	Activate: To pause an automation, deactivate the toggle next to the name of the automation in the overview. Reactivate the toggle to restart the automation. Edit: Select Edit to customize an existing automation to work even more efficiently. In the window that appears, select the desired entry in the overview to make changes. For example, select Ticket to edit the ticket settings. Delete: Select Further actions > Delete to delete an automation. Rename: Select Further actions > Rename. Edit the title of the automation and select Save.
3	View	Automation is read-only if the user is not the creator.
4	Filters	Sort the list of automations by location, device, etc.
5	Configure columns	Choose which columns are displayed in the automation overview.

Automation permissions

Access: Only users in the admin, operations, and technician groups can open the Automation overview and create automations.
Editing: By default, only the automation creator can edit an automation. Exception: Master admins (“Partner admins”) can view and edit all automations within their partner account.
Viewing: Other users in the admin, operations, and technician groups can view (but not edit) an automation if it affects at least one system in their portfolio. In the Automation overview, they see only the automations affecting systems in their own portfolio.