Prerequisites for Getting Started

Enterprise Management is available for the centralized management of OPERA Cloud configuration across all chains, brands and properties within a single enterprise. Using Enterprise Management you can create and update standardize configuration and then efficiently distribute configuration to properties across multiple locations, ensuring consistency and accuracy of the configuration. Enterprise Management can be used for the provisioning of new properties or for distributing configuration updates to existing properties on an on-going basis. OPERA Cloud Central and OPERA Cloud Loyalty OPERA Controls are also available to manage in templates for distribution to properties.

Enterprise Management uses templates in a two-level hierarchy to manage configuration across your enterprise.

• Enterprise Templates - Define standard configurations across all properties in a chain (for example, chain-wide standard configuration).

  • For each template created, a Manage Enterprise Template sub task is auto-created in the Enterprise Template task group; assign this task to user groups for user access to the template.

  • Global (chain-level) configuration, applying to all properties in a chain, is indicated with and can only be configured in an Enterprise Template.

  • Global and property-specific OPERA Cloud Central and OPERA Cloud Loyalty OPERA Controls are available. Global OPERA Controls are indicated with

  • Any dependent configuration is fetched from the enterprise template.

  • Any seeded configuration types and configuration values required in OPERA Cloud are indicated, for example the various Preference Groups and the PM Room Type.

• Custom Templates - Linked to an enterprise template, custom templates define standard configuration for a subset of properties (for example, brand-specific or region-specific configuration).

  • For each template created, a Manage Custom Template sub task is auto-created in the Custom Template task group; assign this task to user groups for user access to the template.

  • Any dependent configuration is fetched from both the enterprise template and custom template.

  • Property-specific OPERA Cloud Central and OPERA Cloud Loyalty OPERA Controls are available.

    • When property-specific OPERA Controls are setup in both enterprise and custom templates, the setup from the custom template takes precedence.

For each template you create, start by selecting the various configuration types, then adding the configuration items (entries) for these options. The configuration types available for selection is dependent on the lowest version at your properties. For example, a configuration type added in 25.x will not be enabled for selection if some properties are currently operating 24.x. Configuration types with dependencies on other configuration types are indicated, for example - Market Codes is dependent on Market Groups.

Once configuration types are selected in a template, configuration can be entered; either directly in Enterprise Management or imported from a CSV template file. Configuration values have a Pending status initially, and must be approved by a user with the Approve Configuration task assigned. Configuration values can be rejected and configuration values no longer required are updated to Archive status to prevent distribution to new properties. You can export the configuration values in a template to CSV files for import elsewhere. You also have the option to import all supported configuration from an OPERA Cloud property into an enterprise template.

In order to distribute configuration to properties, a custom templates is linked one or more properties; resulting in the configuration from both the enterprise template and the custom template being distributed and upsert (update or insert) in OPERA Cloud. When the Multi Property OPERA Control is active, configuration is upsert to both the template (where applicable) and the properties.

When distributing configuration dependent on an OPERA Control (for example, Alerts Messages for the Alerts OPERA Control), distribution fails when the OPERA Control is inactive at the property. Distribution logs will indicate "<property> does not support <configuration type>".