A Dashboard for any Imagine Implementation
A Q&A with Michael Moncada
Imagine’s I/O Services are an indispensable command line tool that invokes Imagine’s APIs for uploading, processing, and downloading data. This tool is a critical component of virtually every client’s use of Imagine, providing nearly one hundred different services. But have you heard about the SITKA I/O Services Dashboard? Mike Moncada, Senior Implementation Specialist for Imagine, says, “I would use this with any implementation.” We sat down with Mike to ask him a few questions about the dashboard.
Hey Mike, what is the SITKA I/O Services Dashboard and why would you use it so broadly?
It is a one-stop command center for running, monitoring, and reviewing results of I/O Services jobs. It is powerful, lets you come away from viewing the long and somewhat tedious batch files, and gives you a tool for setting up jobs and monitoring them. A partner of Imagine, Sindex Financial Systems, wrote this dashboard management program for our I/O Services.
Wait, what’s the problem with batch files?
Some people (like me) like using commands like this:
“%absPath%..\..\..\Bin\IOServiceClient.exe” -f %inpFile% -o %outFile% -ios %service% -log %logFile% -d
But I understand there are people who don’t care for that, and this tool lets them avoid that entirely. Here’s a screenshot of what they would get instead:
What else does the Dashboard offer other than an escape from batch commands?
Lots of things. For example, it:
- helps you set up new jobs, with search-as-you-type, to find the right I/O service,
- gives you sample templates to help get the input files right with clickable links to online support for detailed help,
- allows you to watch the progress that jobs are making, each input that’s successfully processed, or each item that’s rejected,
- shows you the history of each job complete with when it ran, the input, output, and log files for that job,
- and lets you re-run jobs by copying their setup with a single click.
In times of stress in the markets, not only does volatility increase for individual assets, cross-asset correlations can increase dramatically as well. This results in a “double whammy” for a typical portfolio because the portfolio’s volatility increases due to both effects.
Those responsible for maintaining a margin system often feel that they are drowning in data management issues. In part two of this series we discuss ways to make margin calculations far more efficient and meet the firm’s need for answers in real-time.