BPC Utilities
: Universal Transaction Set
: Market Simulator
: Server Load Simulator

The Relationship Hierarchy component offers a flexible, solid foundation from which to construct real-time applications. The Relationship Hierarchy provides the means to:

• permit many-to-many user-to-user and user-to-account relationships
• model various real-world schemas of organization
• organize users and accounts to facilitate deployment and administration
• dynamically customize behavior based on identity, role, and context
• permit fine-grained partitioning of access and control
• support logically separate implementations within a single system

The Relationship Hierarchy component provides the business context for applications and serves as the basis for customer and account data aggregation.

A configurable 'enterprise' relationship hierarchy is highly adaptable to any existing organizational structure, permitting the definition of any number of scopes of access and varying levels of functionality within each scope of access (user entitlements). Firms are able to precisely tailor the sharing or restriction of account access, trade entry, system administration, reporting, and oversight functions to existing operational processes.

A highly flexible, low-overhead user-account model permits many-to-many bi-directional mapping between users and accounts. Role-based entitlement determines the range of functionality that a given user may apply to the other users and accounts to which they have access.

The Relationship Hierarchy supports dynamic discovery of properties (inheritance) and partitioning of application behavior. Properties are used throughout the BPC Suite to set various configuration options. Examples of partitioned behavior include multiple algorithms for commission calculation, pre-trade compliance tests, and trade routing.

The Relationship Hierarchy is designed for large-scale enterprise deployment and supports logically separate implementations (namespaces) within a single system image. Data and users within one namespace are securely segregated from all others.