Risk Shell Custom Data

Custom Assets in Risk Shell

As a hedge fund investor, you're well aware that numerous hedge funds refrain from reporting to external data providers. To analyze such funds, it becomes imperative to collect their performance data directly and manually input it into the system. Additionally, there are instances where you might need to generate custom instruments, like proxies, for testing purposes. In response to these challenges, Risk Shell provides an all-encompassing set of tools designed for the creation and management of user-defined assets, ensuring a comprehensive and tailored approach to your investment analysis needs.

Key Benefits

• Instantly create custom instruments including both performance and descriptive data
• Set up your own virtual asset database within the Risk Shell environment
• Share your custom assets with your colleagues
• Create and maintain custom user-defined descriptive fields

Maintaining Custom Assets: Key Features

• Effortless integration of custom assets with vendor data
• Asset Return Adjustment Framework
• Convenient Excel copy & paste data input functionality
• Unlimited descriptive fields
• Optional predefined field values for streamlined input
• Integrated Bloomberg Data feed

Return Adjustment Framework

Many hedge fund investors collect data directly from managers to mitigate reporting delays in vendor databases. However, this approach can lead to potential data conflicts between the fund's records and vendor-provided data. To resolve this challenge, Risk Shell incorporates the Return Adjustment Framework, enabling the management of multiple return series for a single fund. This feature allows users to seamlessly switch between these series instantly, ensuring accurate and synchronized data representation.

• Maintain cloned database assets to adjust performance manually
• Switch between cloned assets and vendors' by a single click
• Maintain a secondary layer of performance data coming from managers directly
• Adjust return estimates and eliminate vendor data inconsistencies