200 likes | 405 Views
Leveraging Documentum Through a Portal Framework Midwest Documentum User Group Meeting February 26, 2004 Brian Langellier PepsiCo Business Solutions Group. Agenda. Where we have been Lessons Learned Where we are going. Where We Have Been. Quaker Intranet Enhancement Project (Q4 2000)
E N D
Leveraging Documentum Through a Portal Framework Midwest Documentum User Group Meeting February 26, 2004 Brian Langellier PepsiCo Business Solutions Group
Agenda • Where we have been • Lessons Learned • Where we are going
Where We Have Been • Quaker Intranet Enhancement Project (Q4 2000) • Improve navigation • Improve content management process • Quaker B2E Portal Business Case (Q2 2001) • Approval to create an employee portal using: • Epicentric/Vignette Application Portal (portal framework) • Documentum (web content and document management) • Netegrity SiteMinder (security access control) • Verity (search)
Where We Have Been • PepsiCo Purchases Quaker (Q3 2001) • Quaker B2E Portal Pilot (Q4 2001) • Initial build out of infrastructure • Basic portal functionality • Repurposed existing content • No branding • Web Publisher template proof of concept • Tip-of-the-day • Job postings • Executive Dashboard • HR Policies • Data Summaries • Organization News Briefs
Where We Have Been • PEPtalk Release 1 (for pilot audience) (Q2 2002) • Increased capacity (high-availability and failover) • Full portal functionality • Content conversion to Web Publisher • Quaker Datacenter Relocation (Q3 2002) • Performance impact to content authors and users • WAN impact to Web Publisher
Where We Have Been • PEPtalk Full Rollout (Q4 2002) • All business unit content • All users (Quaker & Tropicana) • eRMS (Initial doc mgmt project) (Q1 2003) • WebTop Application
Where We Have Been • Web Publisher Stabilized (Q2 2003) • Required upgrades to eliminate WAN impact • Documentum v5 Upgrade Planning (Q2/3 2003) • Web Publisher Express Lifecycle (Q3 2003) • Provides automatic content publishing • Additional Doc Mgmt Initiatives (Q3/4 2003)
Lessons Learned – Start Simple • Start simple and add complex later: • Web Publisher workflow requirements involved too many steps for power publishers • Users did not want workflow – just wanted to pump content into the repository • Let power users publish – add workflow & approval later: • Retained TSG to write custom lifecycle and job to auto-promote content • Should have done express lifecycle from the start • One size does not fit all: • Just deployed the Web Publisher developer view: • Too complicated and powerful for average contributor • Only provided the standard OOB Web Publisher work flow
Where We Are Going • Adding new functionality for 2004 • Full integration with portal • User personalization and customizations • Collaborative document management projects • Looking to roll out more Web Top functionality within the portal rather than on standalone application • Workflow/Approval • Cabinet Navigation • Document Import • …..
Where We Are Going • Documentum v5 Upgrade (Q1 2004) • Getting rid of RightSite • Web Publisher becomes a Web Top application • Integration available with SiteMinder • Implementation of Documentum Portal Integration Kit • Vignette Application Portal/Documentum Adaptor • TSG Custom Portlets
Multiple Means to Add Content Web Publisher Contributor: Named Dctm User Consumer: Unknown to Dctm No Documentum Document Level Security Portal Search and Navigation Targeted Applications Static HTML/Document Templates Portal Integration Kit Contributor: Named Dctm User Consumer: Named Dctm User Documentum Document Level Security Dctm Search and Navigation Import Documents from Portal Workflow Targeted Applications Legal Marketing Information R&D
Summary • Start simple with Web Publisher • Provide both static (Web Publisher) and dynamic (Connector/PIK) content • Build required skill sets internally • Leverage integrators when necessary
Contact Information • Brian Langellier PepsiCo Business Solutions Group brian.langellier@pbsg.com