I don't have a list but I have some questions/comments..

Any tool that can call an EXE file local to the SQL Server can start an SSIS package. But as far as monitoring that isn't easy. In all of my SSIS packages I have some required steps, these steps capture start/end time, package version including build version, so I can tell if a package has been changed and a few other things. I originally built the framework for an ETL process and came to the conclusion that all packages should find this useful.

What OS are you using on your destop, I do know of an app that might be able to help but it is visually sketchy on Win2008/Vista/Win7.

CEWII