Category: APX


iStock_000011903357XSmallAs quarter end approaches once more, investment advisors gather their resolve and strive to implement new system enhancements to client statements before Q2 arrives. We all wish it could be different, but it is simply the nature of the business. Even firms with good-looking statements may rush to enhance them by incorporating new features such as blended indexes or minor report edits prior to quarter end.

Most of the systems implemented at investment advisories are run on a daily basis, but client statements are typically generated on a quarterly basis. Some investment managers produce monthly statements, but they are in the minority. In the near future, these types of periodic statements will become less relevant than an investor’s ability to generate meaningful client statements on demand.

Amending the quarterly reporting process and report packages requires a disciplined process of setting manageable goals, gaining approval, implementing changes, testing systems and resolving potential problems. Those responsible for creating the reports require approval from management, and until they get that final approval, the time necessary to comfortably implement the changes continues to slip away.

“THE ONLY CONSTANT IS CHANGE” -Heraclitus

As quarter end gets closer, it is not unusual for those involved in the project to get mixed messages about what needs to be done for this quarter. Operations staff juggle various responsibilities. Ad hoc requests, changing priorities and management decision delays inevitably create the need to do last-minute work or postpone the project until the next month, quarter, or even year. With these types of delays, it is a wonder that any progress towards creating better client statements is ever made.

At most larger firms, management is comprised of a number of voices that have a say in whether a firm adapts new systems and reports. The decision to change quarterly reports isn’t made in a vacuum. It is a decision that may depend on a firm’s dedication to their current portfolio management system or a need to allocate limited budget resources to other high-priority issues. Good quarterly reports also underscore a firm’s philosophy, so deep thought and considerable discourse can play a part in determining the content and appearance of client statements.

SOME AXYS USERS DO NOTHING WHILE OTHERS THINK ABOUT MAKING A DECISION.

Before you summarily dismiss all Axys users as being hopelessly outdated and technically inept because they haven’t upgraded to APX or moved to another more recently released Portfolio Management System (PMS), you should understand that there are many decent-sized firms out there that are still using Axys to manage hundreds of millions or billions in assets.  Though a small group of firms really do fit the preceding description, most firms do not. The majority are firms that understand the current shortcomings of Axys and the potential benefits of APX, but also value the simplicity, efficiency, and reliability of Axys.  These firms may have considered Advent’s other offerings: Black Diamond and Geneva, but haven’t managed to find a solution that works for their firm.

As a growing number of these Axys users may be questioning their commitment to Advent, it is only natural that they vacillate to some degree between putting more money into their existing platform or changing the platform altogether. I suspect that many of Advent’s Axys clients now fit into two categories: those who are indifferent and those facing decision paralysis.

Those who are indifferent use Axys like a calculator and will continue to do so until it becomes apparent that they cannot use it any more. Those facing decision paralysis will also continue to use Axys – albeit with some reservations – until another vendor steals them away or Advent makes a bold announcement to continue to support these lost souls with renewed vigor.

In the end, a firm’s need to keep pace with client expectations and technology by providing innovative reporting should win out whether that is achieved by spending money on their existing platform or embracing another. For now, like many in the industry, I continue to hurry up and wait for investment advisors and Advent Software to do something.

About the Author: Kevin Shea is President of InfoSystems Integrated, Inc. (ISI); ISI provides a wide variety of outsourced IT solutions to investment advisors nationwide.

For details, please visit isitc.com, contact Kevin Shea via phone at 617-720-3400 x202 or e-mail at kshea@isitc.com.

Account vs InflationReporting a portfolio’s comparative performance against representative benchmarks over various periods of time has been an widely implemented technique of investment advisors for decades.  Firms do this in a variety of different ways, and some methods are more meaningful than others.

Advisors may show the CPI as a baseline index against the portfolio and other indexes in an effort to illustrate how their investments have performed against inflation and hopefully point out the most basic benefit of investing with their firm versus keeping it under the mattress.

If a firm manages equity they may show the the Dow Jones or the S&P 500 indexes.  If they manage international equities, or have a bond component they will likely show other representative indexes.  They may further isolate performance by asset class and show it with the corresponding indexes to facilitate a client’s ability to draw a direct comparison between the performance of like asset classes and underscore the value they add to the investing process of specific asset classes.

PROBLEMS WITH TOTAL PERFORMANCE BLENDS

Firms typically show total performance too, but many run afoul when trying to show a representative index to match total portfolio performance.  Portfolio management systems like Advent Axys and APX have long supported the ability to create blended indexes, but the actual implementation of the feature falls short of real-world requirements.  In the past, many advisors were content to create a blended index with static weights, but firms soon recognized that these ballpark blends weren’t good enough for their requirements because they didn’t accurately reflect the asset mix of their portfolios over time.

Advent Software initially supported the creation of blended indexes in their portfolio management systems (Proport and Axys) through a report that was engineered to create simple index blends.  This method of creating indexes was somewhat limited because index weights couldn’t be changed over time, but it allowed advisors to manage many indexes centrally through the use of scripts and macros, and it also created separate index (DEX) files.  Having separate files allowed clients to track and show a number of blends if they chose to.

Advent improved the feature to some degree by creating the synthetic index, which allows users to change index weights over time on an individual portfolio basis.  The synthetic index feature works best when used to create ad hoc indexes for selected portfolios, but when users try to scale the feature to be used for a large number of portfolios its usefulness tested.  The ability to change the index weights over time is a plus, but updating the info in an automated fashion is not a feature of the system.

AUTOMATED BLENDING SOLUTIONS

In the early 90s, we started working with advisors to create custom blends with dynamic index weights in order to match the ever changing asset mix of portfolios.  This was done by categorizing assets as fundamental asset types, and assigning those asset types to like indexes.  Once the infrastructure was created we created an extract containing the historic month end asset type weights for all portfolios and used those weights along their corresponding index returns over time to create a true blended index.  The process was automated with a combination of Axys reports, macros, scripts and Visual Basic.

Years ago, we  helped firms address the some of the short-comings of the synthetic index feature by creating a product dedicated to creating blended indexes and managing them.  This allowed users to manage the indexes centrally rather than at the portfolio level.

Last year, we revisited the problem of effectively managing custom index blends for Axys and APX users again.  This time we automated the process of refreshing the index weights stored in each portfolio’s corresponding performance file through a process that updates the synthetic weights by stripping the performance files of their synthetic weight values and rewriting them based on each portfolio’s asset mix and correspondingly assigned indexes.  The process builds monthly synthetic index weights for the inception-to-date period.

This most recent update to our index blending automation tool leverages Advent’s synthetic index capability, and adds the much needed automation that users require to implement the existing synthetic index feature in a way that makes more sense.  Unfortunately, there are still limits to the built-in blending functions of Axys and APX.  For example, synthetic indexes create a blend called simply “Blend”, and users trying to show multiple blends need to create those other blends somewhere else and then generate index files, so that they can be shown alongside synthetic blended indexes.

Thankfully, Advent’s import/export functions, scripting and macros allow savvy users to workaround these limitations as long as they are willing to roll up their sleeves and do a little work or know someone who can help.

About the Author: Kevin Shea is President of InfoSystems Integrated, Inc. (ISI); ISI provides a wide variety of outsourced IT solutions to investment advisors nationwide.

For details, please visit isitc.com, contact Kevin Shea via phone at 617-720-3400 x202 or e-mail at kshea@isitc.com.

In my role over the years as a designer and developer of client reporting packages for dozens of investment advisors, I typically work with decision-makers to facilitate the creation of new client presentations. Many of my clients already know what they want and just need help making it happen.

Though I have an excellent understanding of what is important to most investors and their clients, my opinion is seldom solicited. I speak up when an issue demands it, but most of the time I defer to advisors, listen, and do my best to create what my clients (investment managers) want. In many cases, the bulk of the project is spent on individual report exhibits with little emphasis on the way reports are organized and presented to clients.

I have worked with firms who have wanted to do the bare minimum for their clients (appraisal, and invoice) as well as clients that go above and beyond their duty to report. However, even those with the best reporting intentions can err by including a level of complexity and detail that will not benefit their clients.

On occasion, I am lucky enough to work with investment professionals who are modern thinkers and savvy marketers. The combination of these important characteristics leads to engaging projects and sophisticated report packages. These advisors apparently understand what their clients want to see, and are determined to make the desired reports a reality.

Instead of reporting only what is required, these advisors are trying to exceed the reporting expectations of their clients, and in doing so they engender trust. Their reports are comprehensive and transparent. As such, they have the possibility of highlighting poor performance, but that is a risk that needs to be taken by most advisors. The significance of disclosing this level of information is recognized by investors’ clients and should improve client communications.

In terms of presentation, reports should be bound, with a cover and/or table of contents and well-organized. When a client opens the report up, the most important things are first, and less important details follow. For example, there is a hierarchy to the way the reports are organized in the package such that the relationship is reported first and individual account reports later.  You can view a full report sample illustrating this approach here. In this specific example, the physical report package opens to display pages two and three of the PDF document, which are a relationship summary. The pages that follow provide account-level information.

Reports are typically bound electronically (i.e. PDFs) for those who deliver reports through portals or encrypted email, but firms send most their reports out on paper due to low adoption rates. Paper copies should look professional, and there are cost-efficient options to make this possible whether it is done through printing report packages on 11×17 stock with a saddle stitch or via manual binding of reports after they have been printed. Some of the manual binding options are fairly quick, but shops with hundreds or thousands of reports should not bind reports manually.

Another key to producing impressive report packages is the one-page summary, which allows a client to look at a single page if that is all they want to see. Usually, it is an exhibit that shows them where their investments are, how much they are worth, how they have grown, and how they have performed over various time periods. One-page summaries are also produced to provide information about specific asset types and performance. The idea is to create an executive summary. Clients really want a concise overview of their investments, and rarely look at all the other details that get sent to them on a quarterly basis.

How will you know if your reports have made an impression?

You will hear it from your clients. Even hard-to-please clients should appreciate these types of report improvements. So get to work now, and your new report packages could be ready for next quarter.

About the Author: Kevin Shea is President of InfoSystems Integrated, Inc. (ISI); ISI provides a wide variety of outsourced IT solutions to investment advisors nationwide.

For details, please visit isitc.com, contact Kevin Shea via phone at 617-720-3400 x202 or e-mail at kshea@isitc.com.

iStock_000007871357XSmallYour firm has just completed its implementation of APX. All systems are go including a small collection of SSRS reports, which meet some but probably not all of your firm’s requirements. You have new reporting capabilities, and now the question is “will your firm ever use these new features?” SSRS is also known as Microsoft Reporting Services, which sounds a little less complicated. No matter what the name is, SSRS is a beast – the following issues will challenge your firm’s ability to embrace and leverage SSRS technology for the foreseeable future.

1. TOOL INSTALLATION – SSRS tools like Report Builder and Business Intelligence Development Studio (BIDS) will not be installed on most of your PCs. They are kept at an arms-length from most users, and rightfully so. Though SQL Server Manager and SSRS reporting tools can be accessed on the database server, it currently isn’t Advent Software’s policy to install the applications that give users access to these tools on all users’ PCs. Assuming you have someone at your office with relevant report-writing experience, getting their system configured to make SSRS reports and/or modifications is special request. I have worked with many APX users. By default, most of them do not have access to the tools, so they could not use them or even see them. Some firms using APX 3.x do not even have access to SSRS reports because they have not been installed.

2. ENVIRONMENTAL COMPLEXITY – Once the tools have been installed, the collection of SSRS reports is open to users’ review and modification, but the infrastructure and understanding it requires is cumbersome. Most APX users do not have the skills necessary to create SSRS reports, and very few of those who do are interested in doing it. For those unfamiliar with SSRS and other similar report-writing tools, seemingly simple reporting modifications can be a pain if datasets aren’t designed with your specific reporting needs in mind. Those writing reports need to make frequent backups. Occasionally, reports can become corrupted and cause their writers to lose hours of work.

3. TIME – Compared to creating compound reports and building reports using Advent Report Writer Pro, developing reports using SSRS and other similar report writers like Crystal takes much more time. This is the norm, but not the rule. There are specific report-writing tasks that SSRS is more efficient at performing, but overall report-writing with SSRS is exponentially more complex than using Advent’s standard report-writing tools. This is due to the fact that SSRS development and modifications are the domain of Business Intelligence (BI) professionals and other system integrators who do it for a living. Report Writer Pro and compound reporting were developed by Advent to be used by investment operations end-users with limited technical know-how. SSRS was created by Microsoft, and is not designed with these same users in mind. Some simple SSRS reports take minutes to create, but it is much more likely for users to spend hours, weeks or even months working on reports.

4. COST – Since your firm is unlikely to have BI report developer resources internally, you will need to hire outside resources to develop your reports. That sounds familiar, right? Assuming that you, like many Advent APX clients, spend somewhere around 100k to 200k annually on APX, you can expect to pay at least another 15k to 30k annually to get the reports you want and keep them maintained by qualified third-party resources. You may be able to get the work done cheaper, but anyone delivering reporting services on a platform this complex at a significantly lower price will not be in business for long.

5. AVAILABILITY OF QUALIFIED RESOURCES – Since SSRS is still relatively new to Advent users, there are very few BI resources available with specific experience working for APX users. The learning curve is steep. Significant integration and reporting work needs to be done for individual firms to fully embrace SSRS as their reporting platform, and short-term that leads to a smaller pool of available resources to do the work.

RUNNING WITH SSRS
Due to the complexity inherent in combining various data elements via SSRS and workflow automation, some APX users may still be better off using the REPLANG and compound report functionality first introduced in Axys. Standardizing your firm’s reports using SSRS on Advent’s APX platform could be tough. For many users, standardizing will mean trying to make standard (REPLANG) reports look like they were created in SSRS, or worse, completely reengineering those reports in SSRS.

Advent deserves credit for implementing SSRS. It is a progressive move aimed at satisfying the enterprise users for which APX was designed, but some firms using APX should ask themselves whether they truly are an “enterprise” before they start implementing tools designed for enterprises. (In the near future, I will be blogging on the issue of firm identity and the role it plays in the success or failure of technology implementations.)

Long-term, there is good news for many APX users. Though creating reports can be very complex, the format of SSRS reports is extremely portable, which should eventually lead to more report sharing among APX users. Unfortunately, while this may be good news for APX users, BI developers and integrators like ISITC have to be more concerned with the portability of their end product.

One could literally spend hundreds of hours developing a report and have someone walk away with it. In other stickier environments, reports might be developed at a discount, but an integrator’s sunk costs could easily be recouped through a nearly guaranteed long-term maintenance agreement. Given concerns regarding portability, you should expect to pay a premium to have SSRS reports developed for your firm.

Firms making a significant investment to develop distinctive reports in APX now should be equally concerned with maintaining those reports in the future. Advent and third parties that create reporting solutions regularly make updates to address bugs and/or add functionality to reports. Though APX users may not realize it, this environment is still fairly sticky. Those unfamiliar with specific reports can easily perform the simplest modifications, but firms will do well to retain those that write their SSRS reports to address more complex modifications in the future.

About the Author: Kevin Shea is President of InfoSystems Integrated, Inc. (ISI); ISI provides a wide variety of outsourced IT solutions to investment advisors nationwide. For details, please visit isitc.com, contact Kevin Shea via phone at 617-720-3400 x202 or e-mail at kshea@isitc.com.