Cinergy's Creately. Diagramming workflows and business processes, as well as adding business logic to those images is hardly a new technology. But Creately introduces a couple twists to the mix. One is the ability to work on such process flows collaboratively in real time via the Web. The other is the ability to create your own workflows and then share their components so that others can build workflows reusing previous efforts. Think of it as SOA for business process modelling. Grade: B.
CoreTrace Bouncer. The highly connected world of the Internet has turned out to be a great way to cause damage through malware, and everyone knows that the typical approach of blocking threats is an impossible task given their speed and ever-changing scale. So why not take the time-honored approach of whitelisting: Only let in those you have approved (think secret-society handshakes, gated communities, and club entry lists). That's what Bouncer does: Only approved applications can be installed on users' Windows PCs. What's interesting is that Bouncer recognizes the real world isn't black-and-white, and permissions shouldn't be either. So IT can specify apps or vendors as OK to install; thus, if Adobe has a new app or version, it's preapproved for installation. Better, IT can also give users different permission levels: no installation beyond the specific list for that computer, installation of anything on the enterprise approval list, and installation of anything (for those users you trust, though Bouncer still tells IT what they installed so that you can override their judgment when it fails). This approach reduces risk, keeps IT overhead low, and doesn't treat all users like morons. Grade: A.
DocCenter's DocLanding. Distributed workgroups make it harder to keep current on documents, and endless e-mail threads don't work very well. DocLanding proposes to address that by letting you create repositories called points that you can open up to other users at varying levels of control -- taking typical permission-based management and applying them to the Web environment. For example, you could give clients the ability to review and comment on documents (for which you can black out material you don’t want to share). But you can go further and let points overlap, so different teams can collaborate on a set of documents "owned" by one point. That allows cross-team and even cross-organizational collaboration when useful, while retaining control over permissions and versioning. My question is, How many collaboration services can you sign up for and manage to handle the various aspects of project collaboration? Grade: C.