KOR Onboarding: RS Implementation Phase
Implementation Phase
Once the deep dives have been completed and the Client has provided KOR with the necessary due diligence, the planning timelines can be finalized with greater accuracy. The next major step is for the Client to provide detailed mappings from their internal systems to KOR’s data elements, organized by data feed.
What the Client Does
- Provides mappings for all data expected to be reported, including all KOR-designated fields, and eligibility fields if applicable.
- May deliver mappings in intentional phases (e.g., transaction vs. valuation or collateral); however, it is strongly recommended to provide as much as possible upfront to minimize rework once KOR begins its configuration work.
- Ensures all mappings are submitted in the final format that will be used for production submissions.
- Makes subject matter experts available to answer any questions from KOR during the configuration process.
- Provides data samples for each permutation of data - including the following. Examples should be in a valid agreed format (e.g., json, csv), saved in a central location such as dropbox
- For each asset class + jurisdiction combination, at least 2 examples for:
- Each product type
- Each lifecycle event
- Each source system (where there may be multiple)
- Each venue (if applicable)
- Eligible example, non eligible example (if applicable)
- For each asset class + jurisdiction combination, at least 2 examples for:
What KOR Does
- Reviews all mappings provided by the Client.
- Identifies any potential issues or deficiencies in the mappings, including problems observed in current reporting.
- Configures all necessary rules in the system based on the approved mappings provided by Client. This includes notes of what was implemented and why as provided by the Client.
- Identifies any additional functionality required, and prioritizes the necessary technical development work accordingly.