Nice article. I did a similar thing a few years ago using shared schedules. Avoids hard coding the GUID into stored procs.

I wrote it as one big mad post on the forums:

http://www.sqlservercentral.com/Forums/Topic576337-150-1.aspx

It describes how to setup shared schedules for the 'events' you want to trigger reports.

I then use a synonym to point to the report server. A new stored proc "runReportServerSchedule" is created that takes an 'event' name aka 'shared schedule' name.

Then all you do is subscribe reports using the shared schedule names and in your SSIS packages call the runReportServerSchedule with the schedule names as required. I used this in several systems with great success to allow users to get reports when data loads complete, fail, have validation problems etc.

Give it a read.