Jake 11.27 note - info taken from below:
\\thenest\users\jmathews\DOC Team\RDC_PRICING CENTER\JIRAs\DOC-1625_Engine Processing
The ultimate goal of RDC Prices is to produce Gold Copy Price records for a given effective date and a fixed set of securities out of raw prices received from multiple vendors, or by using prior day Gold Copy prices. To achieve this goal, RDC Prices uses Data Strategies, and the concepts of a Main Engine and Rule Engines, to process activity.
...
Data Strategies maintain their own security criteria.
Data Strategies can reference one or more security holdings (Portfolios), each with their own selection criteria.
The final set of securities subject to processing by a Pricing Data Strategy is determined by first applying the Data Strategy Security Criteria against the Securities database, then applying all Holdings security criteria to the resulting set when the Holdings criteria is selected to be applied. If holdings are not specified in the filtering criteria, all eligible securities resolved will be included.
...
Data Strategies reference a Source Hierarchy where all participating vendor sources are arranged in order of importance.preferred selection. The lowest value in the hierarchy is processed when validated during the compositing of the Gold Copy
The Prior Day Gold Copy source is optional, and usually assigned the lowest level in the hierarchy for Data Management clients or in when actively using Accounting, the lowest level is set as Price at Cost.
...
Data Strategies use Validation Rules to validate source prices during the Validation Phase.
Each Validation Rule has its own Selection Security Criteria that is used against the set of securities that was used to generate demand.
If a vendor price record fails validation, then it cannot be is not used later in Gold Price compositing unless the validation error is corrected and validation rerun.
Validation rules can be Global or Regular:
Global rules are applied to every Data Strategy using global validation rules
Alternatively, Data Strategies can declare use of specific regular validation rules while ignoring global rules to target specific validation tests
Compositing and Release Phases
For each security, the direct outcome of the Validation Phase is the Best Vendor Source Price record
The Best Vendor Source Price record is chosen based on the validation results and established source hierarchy rules.
During the Compositing and Release Phases, the Best Price record is converted into the Gold Copy Price record
Data Strategies can use specified Enrichment Rules that are applied to the Best Price record as part of the compositing process.
...
The maximum number of securities processed by a single rule engine is limited through system configuration
Within RDC > Setup > System Settings > System Setting, there is a value for the Data Keys Limit, sys item 4. This value sets the default for the Rule Engine processing.
Using RDC Data Keys System Settings Limit to Manage Engine Performance
One Rule engine can only process one Validation Rule per Data Strategy
A typical set of input parameters includes data strategy identification, effective date, specific phase identification, and a security alias selector. The security alias selector is either a range of security aliases, or a list of values.
Jake note - would it help to have an example here, or reference the system configuration that determines the maximum number of securities processed by a single rule engine?
Add label