09. Collaborative workspaces

Moderated by Michael Sampson

Organised thus:
1 Server vs p2p
2 new capabilities: presence
3 activity-based collaboration
4 example of threading in capabilities to enterprise apps
5 case study: lessons from the financial services sector

1 - Mike Fitzmaurice, Microsoft

  • Server focus = integration of search, managed infrastructure, context & presence
  • p2p focus = bridge to enterprise if required via one / more of the peers. For teams working together.
  • The difference?
  • Down to deployment, what IT will manage
  • Nature of business issue
  • Mobile work forces
  • Scaling / quantity of data
  • 2 - Andy Fox, Sitescape
  • Integration = context
  • Integration = recording the artifacts (annotations, IM logs etc)
  • Consolidation of commercial and enterprise IMs
  • 3 - David Marshak, IBM
  • Object-focussed presence
  • Object-focussed activities, drag & drop support in Activity Explorer
  • Everything logged in activity threads
  • Ability to bring in people at different levels of the threads
  • 4 - Lance Shaw, EMC Documentum
  • Avoiding file silos for effective collaboration & compliance requirements
  • eRoom allows design 'internal' and 'external' threads
  • 5 - Thomas Fredell, Intralinks
    Secure exchange between organisations (started with bank syndicates for limiting liability on large loans). Lessons learned:
    • Neutral 3rd party is a must for trust etc.
    • Confidentiality has to be comprehensive:
    • People: NDAs, background checks
      Process: SAS70 audits
      Technology: DRM, encryption
    • The concept works, and saves money
    • Technology is critical, but not enough
    • Heterogenous user environments need to be supported
    • Compliance records are mandatory
    • 'Domain knowledge' is essential