Prerequisites for Getting Started

Use Enterprise Management to centrally manage OPERA Cloud and Cruise SPMS configuration across all chains, brands and properties within a single enterprise. In Enterprise Management, you create and update standardized configurations and then efficiently distribute them to properties across multiple locations, ensuring consistency and accuracy. Enterprise Management can be used for provisioning new properties or distributing configuration updates to existing properties on an on-going basis.

Multiple modes are available depending on which Oracle Hospitality solution you are working with. See Switching Modes for details.

Enterprise Management Templates

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 Controls are available.

    • Global OPERA Controls are indicated with

    • Complimentary functions are indicated with in the Complimentary column.

  • Any dependent configuration is fetched from the enterprise template.

• 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 Controls are available.

    • Complimentary functions are indicated with in the Complimentary column.

    • 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. Any seeded entries are populated when the configuration type is selected for a template. See OPERA Cloud Seeded Configuration for details.

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 to an unconfigured enterprise template. You can export the configuration entries in a template to CSV files for use externally.

Distributing Configuration

In order to distribute configuration to properties, a custom template 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>". OPERA Controls selected and activated in templates are distributed prior the configuration entries in the templates.