OPERA Cloud Customer with Multiple Enterprise IDs

Customers with multiple Enterprise IDs typically operate OPERA Cloud environments across different geographical regions with each region having:

• Its own regional Enterprise ID.
• A dedicated OCI IAM Identity Domain.

This approach is generally chosen when the customer entities do not wish to share business data across regions.

Pros of Multiple Enterprise IDs

• Duplicate Property Codes Allowed:

  Same property codes can be used across different regions as each Enterprise operates independently.

• Regional Security Separation:

  Each OPERA Cloud environment maintains complete security isolation with its own OCI IAM Identity Domain.

• Limited Impact in Case of Outage:

  Any issue in a regional OCI IAM Identity Domain will only impact the specific regional environment, not the entire customer footprint.

Cons of Multiple Enterprise IDs

• No Access to OPERA Cloud Central Features:

  Customers cannot leverage connected data experience or centralized identity and access management.

• Duplicate HQ Users Across Enterprises:

  HQ users must be manually recreated in each regional OCI IAM Identity Domain.

• User Recreation on Transfers:

  When transferring employees between regions, user accounts must be recreated in the target region’s enterprise.

• IAM Configuration Overhead:

  Identity Federation, Multi-Factor Authentication, and IP-based access controls must be configured separately for each regional enterprise.

• Complex SCIM API Integration:

  Multiple SCIM connections are required — one per regional enterprise.

• Fragmented Enterprise Management:

  Configuration must be handled separately for each enterprise with no centralized management.

• No Unified Reporting:

  GraphQL APIs of R&A cannot provide a consolidated view across multiple enterprises.

• Complex OHIP Partner Integration:

  OHIP Partners need separate client credentials for the same chain if that chain is present across multiple enterprises.