PowerShell Module Reference
The GENESIS PowerShell interface provides one module per provider. This topic lists the modules, the command prefix that each one uses, and the configuration it manages, so you can find the right module for a task. For background on how the commands work, see the PowerShell Interface Overview; for how command names are formed, see the Command Naming Reference.
Every command belongs to exactly one module, and the command prefix—the text immediately after the verb, such as Ac in New-AcEquipment—identifies that module's provider. The prefix is the link between a command and its module: if you know a command name, its prefix tells you which module it comes from; if you know the module, its prefix tells you how its commands are named.
The command prefix is not always identical to the module name. For example, the HHPowershell module uses the HH prefix, and MelPowershell uses the Melco prefix. List the modules installed on your own system with Get-Module -ListAvailable -Name *Powershell; the present set depends on which products are installed and licensed.
Provider Modules
|
Module |
Command Prefix |
Configures |
|---|---|---|
|
|
|
Assets—the asset model: equipment, levels, classes, properties, and units. |
|
|
|
Data Historian—historical data logging tags, collector groups, and logging groups. |
|
|
|
Triggers—data, time, alarm, file, event, and database trigger items and folders. |
|
|
|
Unified Data Manager—registers, expressions, value sets, groups, and alarm subscriptions. |
|
|
|
Global Aliasing—global aliases and themes. |
|
|
|
Language Aliasing—language aliases and translations. |
|
|
|
Security—users, account policies, access control entries, and passwords. |
|
|
|
FrameWorX—server and network aliases and active configuration files. |
|
|
|
Databases—database connectivity, data sources, and transactions. |
|
|
|
BI Server—data flows, models, columns, and relations. |
|
|
|
Bridging—data bridging configurations and transactions. |
|
|
|
Data Historian Importer—data collection folders, plugins, and tags. |
|
|
|
Reports—report commands and configurations. |
|
|
|
Recipes. |
|
|
|
Schedules—schedules and holiday tags. |
|
|
|
Alarm Server—alarm server areas and equipment property sources. |
|
|
|
Alarm Historian—logging collections, collectors, and dataset definitions. |
|
|
|
Alert Notifications—email, SMS, and Microsoft Teams notification configurations. |
|
|
|
Fault Detection—device models, conditions, causes, and asset diagnostics. |
|
|
|
Connected Field Service—contacts, groups, and mobile health configurations. |
|
|
|
HMI layouts—layouts, devices, icons, and groups. |
|
|
|
Internet of Things—aggregate groups and IoT configurations. |
|
|
|
Application profiles—profile applications, items, owners, and properties. |
|
|
|
Web Services connector—REST methods, parameters, and refresh triggers. |
|
|
|
BACnet connectivity—channels and devices. |
|
|
|
Modbus connectivity—channels and devices. |
|
|
|
OPC UA connectivity—global discovery servers. |
|
|
|
SNMP connectivity—devices. |
|
|
|
Mitsubishi Electric FA—device folders and devices. |
|
|
|
File operations—file archives and transfers. |
Utility Modules
These modules provide cross-cutting commands rather than a single provider's entities.
|
Module |
Configures |
|---|---|
|
|
Workbench project management—the target host ( |
|
|
Configuration import and export ( |
Related Topics: