Away from my posts here, I've got a day job at one of Datawatch's European customers, where we run 20 end user Monarch licences, a DataPump server and a Monarch BI server. I've got the lucky job of "looking after" the entire stack - from configuring access rights for the browser-based BI users, to clearing out the job log files from the DataPump server, and making sure that the end users have got enough training to manage what they need to do in Monarch.
We've come a long way in a few years - when I arrived there were two Monarch users - and I know, from conversations here on the forum and from many of you who've emailed me offline, that while your organisation might not have installed the server products from Datawatch, you share some of the same challenges when scaling up Monarch from one desktop to many. How do you make sure that users don't duplicate effort rebuilding the same model? How do you enforce some sort of real audit trail?
When I heard about the user conference, I thought it might be helpful to talk about this experience, so I proposed a topic to Datawatch on "Managing Monarch". I would be really grateful if any of you could share some experiences - either here or by email - which would help me make the presentation relevant to as many of you as possible. I'm very happy to keep any contributions confidential as well.
Now, I'm a big fan, as I'm sure many of you are, of the Dilbert cartoon strip (www.dilbert.com[/url]), featuring the adventures of an intrepid software engineer and his battles with management, personified by his "pointy haired boss". While the pointy haired boss might be interested in "Managing Monarch", Dilbert (and me) would would rather be building models.
To that end, I'm also presenting a talk on "Invisible Data" - which will be an updated (v11) version of the webinar I gave a year or two ago. This is all about the tricky Report functions (File, ID, Rowno, Recno, Page, Line, Column and Textline) which tend to get skipped over in regular Monarch classes but are really helpful for dealing with difficult data.
I do hope to see you in Vegas,