Onboarding
      Back to home
      1. Knowledge Base
      2. Administration & Onboarding
      3. Onboarding

      Deep Dive: Configuration Mappings

      This article outlines the step-by-step process for creating a standardized template to document configurations. This ensures consistency, clarity, and traceability in system configurations across different asset classes and jurisdiction

      Who should attend the meeting

      Client

      • Regulatory Reporting/Reference Data SMEs

      KOR

      • Client Success

      Note: This is a general list of topics covering various jurisdictions, asset classes, and client types. Some may not be applicable to you and can be skipped.

      For clients onboarding multiple jurisdictions sequentially, it is beneficial to anticipate potential hurdles in future jurisdictions. However, each deep dive session will focus only on the jurisdictions currently in the implementation phase, with discussions on future jurisdictions deferred until their respective implementation begins.

      Creating a Standard Template for Documenting Configurations

      Step 1: Download the Airtable Tech Spec View

      • Identify and download the applicable Airtable Tech Spec view (e.g., CFTC transactions).
        • Make sure the view is filtered to only submittable fields
        • Remember just because a field is marked as optional, that does not mean it is not required for submission when applicable to the trade
        • If you are only trading in limited asset classes you can first filter on the applicable asset classes before downloading.
      • Extract the first column, which contains key configuration elements.
      • If additional columns are relevant, include them in the extracted dataset.
      • KOR recommends separate tabs for each data feed (e.g., transactions, collateral, valuations, entity static, product static)

      Step 2: Download the Sample Configuration Document Format (LINK)

      • Obtain the Sample Configuration Document Format.
      • Export the sample document to a CSV file.
      • Create a standard spreadsheet template based on this format.
      • Save the spreadsheet in the designated shared drive for centralized access.

      Step 3: Populate the Configuration Template Populate the standard spreadsheet with the following columns:

      1. KOR Field Name (from Airtable Tech Spec)
      2. Data Feed Type
      3. Client Source System/Data Feed
      4. Client Field Name (XML Path)
      5. Configuration Type
      6. Configuration Logic Details
      7. Notes (for UI Documentation)
      8. Assignee
      9. Status
      10. Open Questions
      11. Open Questions (Details)
      12. Last Updated
      13. Jurisdiction
      14. Asset Classes

      Guidance on Data Entry:

      • If different mappings exist per asset class, repeat the row and specify the asset class in the Asset Classes column.
      • The Notes column should document any decisions or rationale that need to be tracked for historical reference in the KOR system.
      • Assign appropriate owners in the Assignee column for accountability.
      • Keep the Status column updated to reflect progress and changes.
      • Clearly state unresolved inquiries in the Open Questions section.
      • You do not have to send fields one for one they can be concatenated or derived or pulled from other logic.

      Conclusion Following this process ensures that configurations are well-documented, standardized, and easily accessible. Maintaining detailed notes and historical decisions allows for better tracking and compliance in configuration management across different jurisdictions and asset classes.

      For further guidance, please refer to the shared drive for examples and templates.