Jake 12.8 note
Data Strategy section info taken from RDC Pricing Architecture powerpoint in below:
\\thenest\product Management\RDC Pricing\Project_Administration\Presentations
Engine section info taken from below:
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 reference a Source Hierarchy where all participating vendor sources are arranged in order of preferred selection from 1 to N. 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.
...
The processes that load vendor data into the database need to know define which prices are expected to be sourced for a specific Data Strategy.
The Demand Phase is executed in order to create “shell” records for each combination of security, source from the source hierarchy, exchange and effective date.
The Demand Phase also creates a Gold Copy “shell” record for each combination of security and effective date.
...
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 is not used later in Gold Price compositing, unless the validation error is corrected and the 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 and bypass global rules
Compositing and Release Phases
...
An engine is a basic execution thread used by PACE servers to perform a specific task concurrently with others. Each engine has independent access to the database , and other resources. RDC Prices uses the concepts of a Main Engine and Rule Engines.
...
Data Strategies are always executed by a single instance of the main Main engine. The PACE server launches the main Main engine when it detects a request to execute a Data Strategy. Main engines perform the following tasks:
Interpret data strategy security criteria to produce a list of security aliases subject to processing
Determine which Data Strategy phases to be executed. For example, Demand, Validation, or Composite.
Launch Rule engines for each phase, using a predetermined order and established system configurations
Perform necessary rule engine synchronizations
Exception Orchestrate exception handling and cleanup
A typical set of input parameters includes data strategy identification, effective date, and the list of requested phases.
...
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?
LA - added above link
Add label