1. Novell Teaming Customer Use Cases Rob Luhrs Consultant , Novell Teaming [email_address] Tracy Smith Product Manager, Novell Teaming [email_address]

2. Team Challenges – Dispersed Teams – Information Overload – Finding Information – Leveraging Resources GW TM CN IM GroupWise Teaming Conferencing Instant Messenger

3. Customizable Workspaces Relevance Dashboard Social Tools Robust Workflows Content Management Components User-based Access Control Teaming 2

4. Teaming: Key Success Areas Knowledge Repository Document Management Project Collaboration Process Automation New: Intranet Replacement/Augmentation Customer Themes / Profiles Distributed Teams, Security and Identity, Knowledge Retention, Collaboration vs Sharing, Cost, Support, Experience, Open & Flexible

5. Validation “ Teaming brings very strong capabilities for workspaces and collaborative application development, particularly in the area of workflow” — The Forrester Wave™: Collaboration Platforms, Q3 2009 Rob Koplowitz , Forrester Analyst, United States Novell Teaming 2 Named a Leader in Forrester Wave Report

7. Foster collaboration between E&P experts,

8. Increase the efficiency of operations worldwide.

10. Enhanced information gathering and sharing

11. Improved project management

12. Accelerated progress on project issues

15. Some people raise questions on the issues they are facing, while others offer solutions that can be directly applied to help achieve resolution. All questions are posted in a “high traffic” area. On average, a question posted will generate three or four answers within 24 hours. After 30 days the questions and answers are archived according to subject matter, creating knowledge bases that get populated and updated automatically by the community through their Q&A process.

16. In fact, encouraging users to search the archives, their knowledge base, works as their first step toward getting answers to questions or gaining insight for resolving issues.

21. Because it (Teaming) was a new tool (have tied many) it was hard to get people to try it.

26. Really looking forward to Calendar and Task sync with GW

27. Wants survey improvements to replace Survey Monkey

28. Improve land page layout and functionality

29. eGuide functionality

30. Plan to replace Wordpress Intranet with Teaming

31. Implementing ifolder very soon. Teaming and ifolder are mobile strategy.

32. Joint collaborative efforts between police departments.

33. Be nice to create temporary user accounts that expire. Want to keep their content but don't need a unique license for them.

35. The county is 30+ companies in one

36. Need a central place that can span agencies

37. Need a more affective way to share and collaborate information

38. Its not only our agencies, but others: Office of emergency, committee that provides input from outside people, cities agencies, state agencies, public, air pollution control

40. Need a way to pull all the file shares together.

41. Need to provide a more mobile solutions to allow people to log in from home

42. Need to get a handle on the information, quality, storage, version, official, what is the latest

43. Hundreds of thousands of files just in IT, operational support guides, project doc, support stuff, processes and more

44. Geographic issues – over 400 sites

46. Primary Purpose for Teaming is Doc Asset Library

47. This helps with the mobile goals – allows people to log in from home

48. Use the system to manage projects and will work with the librarians who will have the only access to edit the documents

49. In the workspaces there are controlled documents then more open area that the team contributes to

50. Each team site will have an area, that now includes discussion groups.

51. Have their own version method and does not use the Teaming version feature.

52. Personal workspace, calender, files folder (f drive), task, limited personal data and doc review process.

54. They were getting ready to role it out but really felt like they had to give up just way too much was being sacrificed.

55. They even had some AD issues, got it working at some point but different password and user name and required domain name because of the system set up

56. It just was not feasible to go forward with the solution that they had built with SP. It just was not working for their core need which was Doc Management

57. If Teaming was not there, they were prepared to completely dump all the SP work and look at something else.

58. They bought designer, and then was trying do everything with the free version SP

60. This business proposal process touches nearly every aspect within the agency, thus it was critical that the solution fully satisfy business process needs across the entire organization.

62. Event notification and message management with guaranteed and often simultaneous delivery

63. An interconnected document management/retrieval system, which supports multiple standard document formats

64. Easily accessible audit, status, and metric reporting, including notification for out-of-bounds conditions

65. A search engine to provide knowledge management capabilities and support record/data research

67. Novell providing the software, installation, training, and implementation consulting services required to install, deploy, and maintain the system.

68. Has resulted in the 18 month process being cut down to a 3 month process.

69. Future work is underway, to enrich the Implementation process as well as the reporting capabilities of the software.

70. Novell Teaming Library www.novell.com/teaming_library See complete library at:

72. Customizable look and feel

73. Tight Novell product integrations

74. File system integrations

75. 3 rd Party product integrations

76. Off-line Access

77. Distributed environment

78. Enterprise Search

79. Document and Records THE NEXT 3 YEARS Note: Shorter Release Cycles

82. Novell Conferencing

84. Entry versioning

85. Entry access controls

86. Novell Teaming “Durango” End of Summer 2010

88. Unpublished Work of Novell, Inc. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.