SCT Luminis

1. SCT Luminis Geneva PEPC April 2003

2. Campus Pipeline • Founded in 1998 as a portal product positioned exclusively for higher education • Long-term strategic partnership with SCT • Dot-com business model survivor • 250 customer institutions today • First vendor to provide enterprise web platform for higher education (Sun ONE, Documentum, etc.)

3. SCT Acquisition • Four year CP partner • Strategic technology acquisition • Portal, user mgmt, ECM, “integration” • Strategic human capital acquisition • Two Senior VP’s • 40 SLC-based developers • Divestiture of business units not in higher education (mfg, utilities, gov’t) • CP was the third recent education-focused acquisition

4. Transforming Technology for Higher Education • User-centric • Interoperable & extensible • Open, standards-based • Multiple platforms & devices • Total solution • Department-centric • Disparate, static systems • Closed, proprietary • Platform & device rigidity • Fragmented solutions

5. Where to Focus Your Efforts? Can you identify the areas that will deliver maximum benefit? • Portals • Content Management • Web Applications • Single Sign-on • Data Integration 90 80 70 60 50 40 30 20 10 0 Paper Campus Digital Campus

6. What is a Digital Campus? A Digital Campus is a unified network in which disparate systems, communications and individuals interact in a seamless, secure, personalized atmosphere for learning and achievement. SCT Luminis unifies the Digital Campus.

7. The Unified Digital Campus Promise Benefits Costs

8. Academic & Business Value of a Portal • Integrate all of your applications and information sources into a single secure interface • Communicate with your school’s constituents • Speed your web-based applications and legacy applications to your users • Implement 24x7 personalized self-service • Provide access to communication and collaboration tools • Maximize the value of your existing IT investments • Powerful tools for content and brand management

9. Portals: A New Paradigm • Traditional HE content contributors • Less than 5% of employees • CM central to role • Cost effective to train in CM tools • Portal-empowered contributors • Potentially 100% of employees • CM peripheral to focus of role • Zero training cost required

10. Digital Campus “Quick Benefits” What: One University reduced Web site publishing time from 30 minutes per listing (40 per day) to 2-3 minutes; “Time-to-Web” cut from 2-3 days to 2 or less hours. How: • Enable users to publish their own content, allowing technical staff to work on site infrastructure. • Universities have discovered that by implementing a web content management system, they can scale their technical team without adding new resources. • This is accomplished by reallocation of publishing tasks to the content experts, which frees technical staff to build new applications.

11. SCT Luminis Product Family

12. Why uPortal? Early SCT Campus Pipeline Solutions Software

13. Why uPortal? • We had a need for better end-user portal customization capabilities • Other portal server choices limited the OS platforms on which SCT Luminis would run • Java based utilizing latest J2EE technologies: JSP, JDBC, EJB, XML • Advanced presentation through XML/XSLT • Complimentary visions • Developed by education for education = GREAT FIT

14. What we’re doing with uPortalTechnical Integration • Integrated uPortal 2.1 into the SCT Luminis technology platform • Sun One Directory Server for user, group, role, access control data, which is synchronized with the SIS • Runs within Sun One Web Server 6.0 with other Luminis code • Created channels • Hooked in system administration features • Linked in existing applications (email, calendar, group portal, course portal, targeted announcements, etc.) • Modified default XSLT • For consistent look and feel • Integrated with existing UI customization admin • Streamlined preferences UI • Augmented uPortal functionality • Frame set support • Aggregated Layout Management (v.1) • CAR file support • Testing, bug fixing, performance tuning • Channel development kit (CDK)

15. What we’re doing with uPortalChannel Development

16. What we’re doing with uPortalNew Channels Email Calendar* Not Pictured: My Courses* My Groups* *Part of Luminis 3.1 release

17. What we’re doing with uPortalSCT Banner Channels

18. What we’re doing with uPortalAggregated Layout Management (ALM) • ALM provides institutions the ability to associate some elements that appear in a user’s layout with different owners and grant to these owners the ability to restrict in some way what end users can do with them. • ALM provides a mechanism for defining rules by which these externally owned elements are included automatically into a user’s final layout if they meet the criteria defined in the rules.

19. Tabs = Columns Channels What we’re doing with uPortalAggregated Layout Management What is a layout fragment?

20. What we’re doing with uPortalAggregated Layout Management How it works Layout Fragments Personal Institution Department Composite View

21. What we’re doing with uPortalAggregated Layout Management Portal Customization Spectrum End User High ALM allows the institution to decide where along the spectrum they want their portal to be. Degree of control Low Institution

22. What we’re doing with uPortalChannel Development Kit (CDK) • CDK assists portal developers with: • Channel development • Bringing into the portal access to external web-based applications and content • Portal customization

23. What we’re doing with uPortalChannel Development Kit (CDK) The CDK includes: • Documentation (over 200 pages and growing) • uPortal overview of “how it works” • Prerequisites for using the CDK • Installing the CDK • Creating channels • Deploying channels • Installing/distributing channels as CARs • Content framing techniques • Other reference materials • CAR file support • Sample code

24. What we’re doing with uPortalCAR File Support • Channel ARchive (CAR) files provide: • Handy packaging and distribution mechanism used when developing channels • Enhanced portability of channels between portal instances CAR file packaging SCT Luminis @ School A Developed channels uPortal @ School B SCT Luminis @ School C Facilitates packaging, distribution and installation

25. Working with open source Customer request Competitive analysis Benchmarking Enhancement request • Should we volunteer to develop it? • Who is developing the feature? • When is it scheduled? • Should we contribute to design, etc.? • Or do we just wait for the feature? Marketing Requirement Is this on the uPortal roadmap? YES Requires Collaboration Facilitates Influence NO • Is this something we can develop on our own? • Is this applicable to uPortal? • Is this a feature we can/should contribute to uPortal

26. Working with open source Main line code base 2.0 2.1 2.x CARs, Bug Fixes, etc. SCT Luminis Product Release SCT Luminis Product Release Complex features that span multiple releases CP withheld or unwanted (by uPortal) code (ALM) Time

27. SCT Luminis Value Total Cost of Ownership Horizontal Portal Products (e.g., Oracle, PSFT, Epicentric) High Effort to develop, deploy and maintain Low High Low Software licensing cost

28. SCT Luminis Value Opportunity Costs Longer Horizontal Portal Products (e.g., Oracle, PSFT, Epicentric) Time to Live, Successful Deployment Shorter Infrastructure End-user Targeted Services Focus of IT Resources

29. SCT Luminis Value • We’ve created a solution for institutions that want: • Rich higher education-focused feature set • High level of support • Quick “install-to-live-rollout” (with full populations) • Focused IT resources developing value added services targeted at their end users • Lower level of effort to deploy, maintain, and upgrade • Plus all the benefits inherent in the uPortal framework = Best of both worlds!

30. Luminis Demo

31. Luminis Architecture

32. Luminis Architecture

33. Luminis IS Components • Starter Edition • Enterprise Edition • Integration Adapters • Adapter CustomizationServices

34. SDK General Availability and Early Access of SDKs

35. Unifying the Digital Campus through Content Why Higher Education Needs Web Content Management

36. Portals Need Content Management “Why do portals and content management go hand in hand? Because portals require content that is: • Relevant and easy to find… • Maintained by business users… • Accurate and standardized… “ — Nicholas Wilkoff, Forrester Research, May, 2002

37. WWW Definition: Web Content Management Seamless Integration of People, Content and Processes at Internet Speed People Documents (content) BusinessProcesses

38. Portals Websites Applications Luminis Content Management

39. Web Content Management is Higher Education Critical Structured • Over 80% of enterprise content is unstructured (Fulcrum Research) • Content Volume is growing by over 200% per year (Forrester Research) Unstructured Other Output Web Content Code • Documents, Web content and rich media assets represent the vast majority of unstructured enterprise content Documents Digital Assets

40. Content Content Alumni Portals Course info / Schedules Edu Sites E-Procurement Content Content Content Wireless Delivery Digital Asset Management Content Content Multiple Campuses Campaigns Content Content Compliance The Content Challenge Student Services Collaboration

41. .EDUSites Course Info / Schedules Employee Portals A common content platform that powers multiple applications Wireless Delivery E-Procurement Marketing Student Services Collaboration Compiance Digital Assets Multiple Campuses The Solution

42. Key CMS Takeaways • The Luminis / Documentum solution is a core requirement for: • Automating the process ofcreating, managing, adding intelligence and delivering content for multi-channel delivery • Empoweringnon-technical business usersto easily publish content to the Web withno additional training required • Achieving maximum ROIbyeliminating IT bottlenecksand accelerating time-to-Web

43. Luminis Does Not Stand Alone

44. Implement Plan Assess ImplementationFollow a process In our case, we’ve created a process called: Recommended Success Formula • Assessment of the institution’s state of affairs with regard to a unified digital university • A Visioning Workshop and Planning sessions with key decision makers on campus • Training Certification • Technical planning, consulting and training Communicate Support

45. ImplementationRecommended Success Formula Assess Plan Implement • Visioning Workshop • Project Planning • Technical Planning • System Administration • Campus Readiness Review • Focus Groups/Surveys • Technical Assessment • Trainer Certification • End User Training • Power User Training • Instructor Orientation I N S T A L L A T I O N • Impact: • Identify readiness and viability of all technical systems • Assess and prioritise needs of all business units and users • Anticipate and identify project critical issues and risks • Impact: • Create comprehensive project plan for all technical and functional requirements • Ensure campus-wide buy-in for Digital Campus Initiative by involving cross functional team • Achieve familiarity (Sys. Admin.) • Recognise need for communication and feedback processes • Impact: • Ensure user competence and confidence • Market benefits of Digital Campus across the organisation • Prepare for and train ongoing support resources

46. Three Things to Remember • Every day the Digital Campus becomes a more integral part of how the world experiences your institution. • Portal-platform solutions can be a source of pain or solution for pain. • SCT Luminis solutions offer unprecedented scope, choice and flexibility for your Digital Campus today and tomorrow.

47. Thank You for Joining Us! • For further information, visit us at: http://www.sct.com/ • Or contact: Jono Smith - jsmith@sct.com+1.202.236.1079Mike Zackrison – mzackris@sct.com+1.801.257.4230