Help
Posted by
Carl Marrelli 
Hello from Birmingham. We are here at our annual European Users Conference and I thought it might be good to post a quick entry regarding our first 2010 release. EchoSystem 2.5 Update 2 released on January 29. Many of you received an email announcement on Tuesday Feb 2.
You can find lots of details in the release notes, but honestly some of that technical stuff can get rather boring. I'd like to comment on a few particular highlights that we don't normally cover in such docs.
It is quite exciting to see EchoSystem put to it's paces. Several of us at Echo worked very closely with a well-known University in the states (hint: a mid-west university who knocked Ohio State out of possible championship contention this past season). While we had some bumps along the way, this particular deployment now boasts EchoSystem managing 300+ capture devices (mostly Podium capture devices) and tested up to 700 captures in a 3 hour window. I think that is rather cool. A free Echo360 pen for the first member to reply with the name of the customer ...
Equally exciting is observing the platform as it's evolved from early adoption into mission critical. Whether running 3 or 300 rooms, the overwhelming majority of our users tell us repeatedly how critical the system is to their infrastructure. This of course presents certain challenges, challenges we look forward to tackling this year with the product and our processes. The 2.5 Update 2 release introduced a new element in our release planning. This release was rolled out to 14 select customers around the world before going GA. This process proved effective as we were able to address one major issue that would have caused many of of you a bit of concern when rolling out. Special thanks to the customers who took on the preview release! You have served the entire Echo360 community quite well. You will all be hearing more about this process as we progress towards 2.6 delivery this summer and on Tom's blog.
Cheers,
Carl
You can find lots of details in the release notes, but honestly some of that technical stuff can get rather boring. I'd like to comment on a few particular highlights that we don't normally cover in such docs.
It is quite exciting to see EchoSystem put to it's paces. Several of us at Echo worked very closely with a well-known University in the states (hint: a mid-west university who knocked Ohio State out of possible championship contention this past season). While we had some bumps along the way, this particular deployment now boasts EchoSystem managing 300+ capture devices (mostly Podium capture devices) and tested up to 700 captures in a 3 hour window. I think that is rather cool. A free Echo360 pen for the first member to reply with the name of the customer ...
Equally exciting is observing the platform as it's evolved from early adoption into mission critical. Whether running 3 or 300 rooms, the overwhelming majority of our users tell us repeatedly how critical the system is to their infrastructure. This of course presents certain challenges, challenges we look forward to tackling this year with the product and our processes. The 2.5 Update 2 release introduced a new element in our release planning. This release was rolled out to 14 select customers around the world before going GA. This process proved effective as we were able to address one major issue that would have caused many of of you a bit of concern when rolling out. Special thanks to the customers who took on the preview release! You have served the entire Echo360 community quite well. You will all be hearing more about this process as we progress towards 2.6 delivery this summer and on Tom's blog.
Cheers,
Carl
3 Comments On This Entry
Page 1 of 1
It was great to meet you and the team in Birmingham. I hope to continue the work with you into the next year!
Graham
P.S. Purdue, I was listening