RCWG Report

1
RCWG Report ECS 04 Workshop Results

• Sheila Cisko, RCWG Chair
• Fermilab

2
Topics

• RCWG Report
• Description, charter and membership
• Recent activities
• Future activities
• Concerns
• Contact Information
• ECS 2004 Workshop Results
• Who, why, where how
• Session descriptions
• Recommendations
• Conclusions

3
RCWG Description

• Remote Collaboration Working Group is
  representative of DoE sites and universities
  which use ESnet Collaboration Service (ECS)
• Purpose is to interact between DoE collaboration
  community and ESnet Collaboration Services (ECS)
  staff

4
RCWG Charter

• Provide insight and requirements from DoE
  community to ECS for usage, problems and planning
  of services
• Provide organized testing, roll-out and feedback
  of new and/or revised services
• Provide an information exchange on new products
  and developments

5
RCWG FY05 Membership

• Sheila Cisko Chair FNAL
• Alan Sill Texas Technical University
• Art Bray SLAC
• Christian Helft IN2P3- LAL
• Clint Wadsworth ESnet Brooks Collins
  SLAC Deb Agarwal LBNL
• Ed Ritenour LBNL
• Hans Frese DESY
• Ivan Judson ANL
• Ivars Ambats ANLJanine Jensen PNNLJosh
  Stillerman MIT K. Estelle Dodson NASA Ames
  Research CenterStan Kluz ESnet Lori Abry
  ANL Marcy Santana ESnet
• Martin Jara LBNL
• Chris Masullo BNL Ed May ANL
• Mike Pihlman ESnet Philippe Galvez Caltech
  /VRVS.org
• Steven Goldfarb UMICH/CERN
• Thomas Baron CERN

6
RCWG Membership, contd

• Twenty-four members half actively participate
• Small number are real users not IT
  professionals
• Use ECS and collaborative tools for meetings
• RCWG members offer to their sites and/or the
  conferencing community
• operational support (room- and/or desktop-based)
• run services such as streaming and VRVS
• collaboration technology investigations
• but not primary job responsibility

7
Recent activities

• Small number of membership are authors of ECS
  2004 Workshop Report
• Continued technology tests
• Commercial products
• H.239 (parallel presentations and video)
• Instant Messaging
• VoIP
• recording and archived meetings
• interoperability
• VRVS service
• OpenSource clients

8
Recent activities (contd)

• Planned for deployment of new services such as
  streaming
• Participated in maintenance and upgrade tests of
  ECS components
• Provided test services for users
• Provided test services for non-82X services on
  MCUs
• Wiki created (credit C.Helft, LAL) for meeting
  agendas and notes, technical discussions,
  collaborative issues, Workshop notes news

9
Future RCWG activities

• Widen membership to include other DoE sites and
  university affiliates worldwide
• Conduct community survey targeting US
  laboratories and universities
• include users, IT professionals, support staff
• Continue interaction with other services for
  interoperability and RD efforts
• Plan for deployment of future ECS services
• participate in ECS Workshop 2006

10
Future RCWG activities contd

• Improve advertisement of ECS services and
  notification of technology changes
• Close the collaboration wizards gap
• by improving online documentation and
  instructions
• by offering tutorials live using ECS services
  and live or archived streaming
• Improve monitoring and metrics

11
Concerns

• ECS should be provided with resources to maintain
  current production services
• ECS should be provided with resources for
  upgraded production services
• ECS should be provided with resources for RD
• to interoperate with federated collaboration
  services from CNRS/IN2P3/CERN/INSERM, VRVS,
  Asia/KEK or others within the energy research
  community

12
Contact Information

• Contact Sheila Cisko scisko_at_fnal.gov
• to join RCWG Meetings
• Mondays 11amCDT
• email list
• RCWG_at_ES.net
• http//www1.es.net/escc/index.html
• follow Taskforces link

13
(No Transcript)
14
ECS 04 Workshop

• Workshop 04 Report
• www.es.net/events or
• hpcrd.lbl.gov/ESnetCollab/homepage.htm

15
ECS 04 Workshop

• Goals
• To plan for future direction for ECS
• To investigate emerging future technologies to
  enhance the way scientists communicate and work
• To gather current and anticipated requirements of
  our user community
• It will also provide the opportunity for users to
  discuss the role of ECS

16
ESC Workshop 04

• Motivation
• to exchange information between ECS and ECS users
  as an aid to planning future direction of ECS
• express concerns, review technologies
• Program and format
• overview of current state of collaboration
  services
• view of emerging technologies
• feedback and discussion leading to straw plan
  outlining future of ECS

17
Brief Session Descriptions

• Collaborative Services
• Current ECS services
• RCWG Report
• Future Production Research Directions
• Future ECS overview
• Access Grid
• VRVS
• Directions in collaborative tools
• User Feedback
• Collaboration directions
• Desires for future services

18
Specific Workshop Recommendations

• ECS should provide fundamental core services to
  build a variety of collaborative services
• Includes gatekeepers, MCUs, gateways, utilization
  statistics, websites
• ECS should be provided with resources materials
  to continue this work provide upgraded services
• Production services require maintenance on
  current h/w s/w components
• Increased bandwidth for higher quality service
• ECS should maintain a development test-bed system
  to evaluate plan future services
• Such as VoIP, SIP, High definition, IM

19
Specific Workshop Recommendations (contd)

• ECS should collaborate integrate services with
  other organizations and collaborative tools RD
  groups
• Coordinate services and interoperability with
  other organizations such as VRVS, Access Grid,
  CNRS/IN2P3/CERN/INSERM, ViDeNet, gatekeeper
  peering
• ECS should interact with experts users to
  ensure effective use, operation of services and
  tools
• Run annual workshop or conference to promote this
  goal and access future needs
• ECS should prepare yearly update a long range
  plan with time frames of 1, 3 and 5 years
• Some recommendations have been completed but
  others require additional funding, cooperation
  with other organizations or institutions and
  long-term planning

20
Conclusions

• Collaborative services help reduce costs for
  global collaborations
• Desktop systems and ad-hoc services further
  reduce costs
• Move to IP from ISDN further reduced costs for
  labs and universities
• In the future the need for ECS services will grow
  and broaden