Transcript Sample Title

MWDUG
2005 Market Trends:
Building Business Success with ECM
Jeetu Patel – Executive Vice President
February 18, 2005
Objectives
MWDUG
• Understand where business is today
• Look at the year ahead
• What actions can you take today to reach your
2005 goals
2
© Doculabs 2005
Agenda
•
•
•
•
•
•
3
MWDUG
About Doculabs
Market Trends
Impact of mainstream IT players in the ECM space
Plan for success with ECM architecture
Other key trends
Tackling 2005
© Doculabs 2005
MWDUG
About Doculabs
4
© Doculabs 2005
About Doculabs
Who is Doculabs?
MWDUG
Definition
Doculabs is a technology consulting firm backed by research and
extensive client experience that lowers the business risk of technology
decisions. Our services lower the business risk of technology decisions
through client specific recommendations, objective analysis and in-depth
research.
This approach is based on our fundamental belief that in order to protect a
client’s long-term interest, technology advisors shouldn’t be implementers.
Quick Facts
5
•
•
•
•
Founded in 1993
Headquartered in Chicago
Privately held
Served over 350 customers
© Doculabs 2005
About Doculabs
Our Key Differentiators
Client Specific Experience
Objectivity
In-depth Knowledge
6
MWDUG
Recommendations based on the
needs of your firm, not the
industry at large
Analysis without the bias of
integration services or vendor
preferences
Unique research on suppliers’
capabilities and customers’ best
practices
© Doculabs 2005
MWDUG
Market Trends
7
© Doculabs 2005
Market Trends
Enterprise Content Management Market
8
MWDUG
© Doculabs 2005
Market Trends
Increasing Complexity
Increasing complexity in a quickly growing market
•
Migration from niche applications to infrastructure
platforms
•
Applications are getting more complex and
providers are expanding their products to match
these needs
EDMS
Organize
Web Content Mgmt
ERM/COLD
Digital Asset Mgmt
Portals
Taxonomy and Search
Collaborate
Collaboration
Process Mgmt
Forms
Records Management
Store and
Distribute
Archival and Storage
Print and Distribute
9
© Doculabs 2005
Content Integration
(Imaging, Workflow,
Document Mgmt)
Security (Document, Perimeter)
•
MWDUG
Market Trends
M & A Activity
MWDUG
FileNet  Watermark, Saros, Greenbar, eGrail, Shana
1995/96, 2002/03
1997
Eastman Software  Wang Software
1997
iManage  FrontOffice
2001
2001-04
2002-03
2001-04
2003/04
EMC  Legato,
Documentum
Open Text  Gauss,
IXOS, Artesia, Quest
Documentum  Box Car, eRoom, BullDog, TrueArc, AskOnce
IBM  Tarian, Green Pastures, Venetica
eiStream  Eastman Software, Viewstar, Keyfile, Identitech (BPM)
Stellent  InfoAccess, INSO, Kinecta, Ancept, Optika
1999-2004
10
2003
Microsoft  NCompass Labs
Adobe  Q-Link
2004
Interwoven  iManage, Software Intelligence
2003
Hummingbird  PC DOCS, EDUCOM
1999
Vignette  Epicentric
Intraspect, TOWER Tech
2003/04
2004
Veritas  KVS
2004
Oracle  Collaxa
2004
2004
Mobius  eManage
Captaris  IMR
2004
HP  Persist
Next 3 to 5 years…
© Doculabs 2005
MWDUG
Impact of Mainstream IT players in the ECM space
11
© Doculabs 2005
Impact of Mainstream IT players on ECM
Why all the fuss over ECM
MWDUG
1. Organizations are
struggling to integrate
structured and
unstructured data
2. Constant struggle with
the permanent reality of
a heterogeneous
environment
3. The change from
product-focused to
layer-focused market
definition
4. But this market evolution
will take time
12
© Doculabs 2005
Impact of Mainstream IT players on ECM
Market Giants
MWDUG
• EMC
– Combines EMC dominance in storage management with Documentum
dominance in content management for “ILM”
– ApplicationXtender significant contender for midmarket
– Directly faces key ECM issues of the day: how to do ILM, how to do mid-scale
ECM
• IBM
– Current positioning: provides ECM capabilities tied to WebSphere, DB2
– Strengths include dominant IT presence, WebSphere centrism, great ECM
potential, content integration to other data sources, global reach
– Most implementations are highly customized
13
© Doculabs 2005
Impact of Mainstream IT players on ECM
Market Giants
MWDUG
• Microsoft
– Addressing ECM challenge with operating environment (Longhorn), Office,
SharePoint and Content Manager
– Will address enterprise ECM, “small time” ECM – and be a disruptor for the rest
• Oracle
– Not just Metadata, but also the unstructured content physically resides in a
structured store
– The basis of their position is that all data is better off being stored in a
structured store, i.e. “the database”
– They are not trying to win the feature war, rather trying to compete on simplicity
and scalability
14
© Doculabs 2005
MWDUG
Plan for success with ECM architectures
15
© Doculabs 2005
Key Market Trends
Understanding the ECM Evolution
Inception
Phases 
Chaos
MWDUG
B
Rationalization
Stabilization
C
Performance
Surplus
Functionality
Customers’ capacity to
ingest functionality
1985
• Market definition
16
A
Point at which industry
wide standards reached
adequate maturity, e.g..
XML, Web services, SOA,
Performance
Deficit
Point where customer
requirements have been
met by vendor functionality
developed in a nonmodular approach
Modular
functional
development
Self-sufficient
functional
development
Redirect this
investment towards
modular architectures
Time
1995
• First round of
consolidation
begins
• Budgets still
remain at the
departmental
level
2000
2002
Component object
model initiatives
undertaken, but
failures persisted
due to standards
not being practical
enough
2005
• SOA goes
mainstream
• ECM is an enterprise
architecture based
decision
• DB vendor market
share now at risk
Partial Source:
Innovator’s Solution
by Clayton Christianson and Michael
Reynor
© Doculabs 2005
ECM Architectures
Doculabs’ ECM Strategy Methodology
MWDUG
Conceptual Design,
Enterprise Requirements
Current State
Definition
ECM
Methodology
17
1
2
3
Selection and
Consolidation
Strategy
Analysis and
Recommendation
Analysis
4
Taxonomy
Development
Deployment Strategy
Candidate Solution
Business Case
Assessment
Metadata
Reference Architecture
Future State Definition
5
6
7
© Doculabs 2005
8
ECM Architectures
Importance of an ECM Architecture
Conceptual Design,
Enterprise Requirements
Definition
Current State
Assessment
ECM
Methodology
1
2
MWDUG
Reference Architecture
Future State Definition
Candidate Solution
Business Case
Analysis and
Analysis
Recommendation
3
4
Metadata
Deployment Strategy
5
Taxonomy Developmen
Selection and
Consolidation
Strategy
6
7
+
Enterprise Reference
Architecture
18
Organizational Readiness
Framework
© Doculabs 2005
8
ECM Architectures
Content Management Reference Architecture
MWDUG
Content Presentation/Access Services
Capture
Event
Aggregation
Imaging
Delivery
Optical Character
Recognition
Forms
Protocol
Translation
Navigation
Document
Syndication
Rights
Management
Presentation
Renditioning
Client
Detection
Process and Collaborative Services
Event
Sequencing
Workflow
Process Management
Document
Event Notification
Content Delivery
Encoder
Enterprise
Rules Engine
Analytics
Prioritization
Content
Retention
Event Analytics
Packaging
Routing
Content Lifecycle
Content Analytics
Escalation
General
Computer
Aided Design
Presentation
Charting
Spreadsheet
Forms
Collaboration
Approval
Management
Escalation
Word
Processing
Messaging
Publication
(Push/Pull)
File Sharing
Whiteboard
Discussion
Project Management
Desktop
Publishing
Web Content
Style Sheet
XML
General Analytics
Content and Process Event Services
Taxonomy
Content Middleware Services
Security
Perimeter Security
Identity Management
Firewall
Encryption
Anti-Virus
Authentication
Virtual Private
Network
Authorization
Directory
Taxonomy
User
Auto-Categorization
Ontology
Metadata
Storage
Federated
Search
Data Integration
Unstructured Content
Structured Content
Adapters
Adapters
Abstraction
Interface
Extract,Transform,
Load
Design
Translation
Simulation
Electronic Forms
Dynamic Composition
Metadata
Utility Services
Translation
Retrieval
Aggregation
Dynamic Content Publishing
Version Control
Distribution
Publishing
Indexing
Assembly
Rendering
Natural Language
Transformation
Style Formatting
Bundling/
Sequencing
Linking/
Indexing
Addressing
Deployment
Event Monitoring
Data Management Services
Infrastructure Management
Repositories
Storage
Process / Workflow
Structured
Event
Correlation
Unstructured
Management
Location
Migration
Primary
Design
Relational Database
Object Relational DB
File System
E-Mail
Optimization
OLAP
Real-Time Event
Processing
Metadata
Document
Collaboration
Backup
Near Line
Recovery
Distributed Cache
Simulation
Report Design
19
© Doculabs 2005
Content Creation and Management Services
Schema
Design
ECM Architectures
Sample Roadmap: ERA in Practice
MWDUG
Key Design Goals
•
•
•
•
20
Service-oriented
Event-driven
Clean abstraction layers
Focus on Security,
Portals, ECM and BPM
related technologies
© Doculabs 2005
ECM Architectures
Sample Roadmap: Current State
21
MWDUG
•
Provides an
assessment of current
environment related to
ECM technology
•
Is a baseline for ongoing measurement of
changes towards the
desired goals
•
Is organized using the
preferred architectural
model for these
technologies
© Doculabs 2005
ECM Architectures
Sample Roadmap: Future State
22
MWDUG
•
Represents the desired
future state that will help
achieve strategic goals
•
Areas in white represent
areas that are not
required to achieve goals
© Doculabs 2005
ECM Architectures
Sample Roadmap: Resource Requirements
23
MWDUG
•
Shows how much relative
effort in time, money, and
staff resources will be
required to move from the
current state to the
desired future state
•
Red circles represent
defined projects that will
lead to improvement for
that particular area
© Doculabs 2005
ECM Architectures
Sample Roadmap: Deployment Schedule
MWDUG
• Provides a timeline to achieve tactical success that leads to
a successful strategic implementation
• Percentages in each phase represent portion of total costs
that should be expected to be expended during the phase
24
© Doculabs 2005
ECM Architectures
Sample Roadmap: Deployment Strategy Summary
25
© Doculabs 2005
MWDUG
ECM Architectures
Making ECM Black and White (and Grey)
ECM is technologies and
services that directly
affect the creation or
capture, update or
management, delivery or
syndication, and longterm storage and
archival of information.
ECM is sometimes
technologies that
support or make it easier
to work with information
or to access it.
26
MWDUG
Content
Integration
Document
Management
Image Capture
Process
Automation
Collaboration
Web Content
Management
Portal
Records
Management
Workflow
Library Services
Security
Enterprise
Application
Integration
Search
ERP
Application
Services
© Doculabs 2005
MWDUG
Other Key Trends
27
© Doculabs 2005
Other Key Trends
Taxonomy Development
MWDUG
• It’s a significant undertaking… and can pull you under if you’re
not careful
• Three approaches: Buy it, build it manually, build it somewhat
automatically
• Three kinds of tools: manual tools, automation tools, portals
and ECM products with metadata tools
28
© Doculabs 2005
Other Key Trends
Information Lifecycle Management
MWDUG
• Currently in a “high visibility” phase
• ILM = “proactive management of storage/archive that is
business-centric, unified, policy-based, heterogeneous, and
aligns storage resources with data value” (ECM)
• But adoption is primarily application-specific, and adopters are
reassessing advantages
• Challengers in pursuit
29
© Doculabs 2005
Other Key Trends
Enterprise Content Integration (ECI)
MWDUG
• Best used as a strategic option in cases where:
– Content resides in multiple or specialized repositories or applications
– Complex integration is required up- or downstream from repositories
– Effort is perceived as too high to consolidate in single repository,
while ECI integration is perceived as acceptable
– RM requirements (retention, disposition, audit holds) are perceived
as low or are under control of existing repositories
• Meeting risk reduction requirements is a primary advantage
of unified archival over ECI
– Virtual records management is resource-intensive and frequently
problematic
– Unified strategy supported by ILM
30
© Doculabs 2005
Other Key Trends
Email Management
MWDUG
• Email management implementations and vendor capabilities
continue to improve
– Necessary for Defense” and operational/IT drivers; less necessary for
Offense)
– Primary requirements: 1) scalability, 2) archival, and 3) advanced
records management capabilities for e-mail (e.g. differential
attachment processing); few vendors adequately address all three
– Some advanced capabilities require complementary technologies
(auto-classification, business rules engine, granular access control,
filtering for review)
• Key vendors include pure play solutions, RM vendors, ECM
vendors, storage/ILM vendors
– But gaps still remain
• In scalability, e-mail-specific RM functionality, integration with other
electronic RM systems, integration with ECM systems to address
Offensive requirements
31
© Doculabs 2005
MWDUG
Conclusion
32
© Doculabs 2005
Conclusion
Suggested Strategy for 2005
MWDUG
• Determine if your organization has an enterprise IT strategy
that incorporates ECM, and plan accordingly
– If it does…
– If it doesn’t…
– If it does, but by the time it’s executed we’ll all be long dead… (so
you need an interim strategy)
• “In the future all ECM vendors will offer frameworks or
modules that fit in frameworks” (and what that means)
• Your organization will always be heterogeneous
33
© Doculabs 2005
Conclusion
Thanks and Good Luck
MWDUG
• Doculabs methodologies helps clients develop successful
plans for building and implementing ECM strategies
• Detailed views of presented visualizations contact
• Contact Jeetu Patel – [email protected]
34
© Doculabs 2005