phase two: what’s next for life sciences and enterprise content management
TRANSCRIPT
![Page 1: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/1.jpg)
1
What’s Next for Life Sciences and Enterprise Content
Management June 25th, 2008
![Page 2: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/2.jpg)
2
Agenda
• TSG Background• “What’s next” Client Examples and Best
Practices
![Page 3: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/3.jpg)
3
TSG Background
• TSG founded in 1996 as content management solutions consulting firm
• Global 2000 clients across Pharmaceutical, Financial Services, High tech and Manufacturing
• Offices in Chicago and Kansas City• 90% of our Work involves Documentum
– 35 trained Documentum consultants– Coordinate Midwest Documentum User Group (www.mwdug.com)– Active in all Momentum/EMC World events– Active in Documentum Certification Programs and Beta’s
• Partial Major Client List;– Life Sciences: – Other Clients:
![Page 4: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/4.jpg)
4
ECM Consultants – How TSG is different
• Majority of clients are mature Implementers– Have installed out of the box– Looking for innovative solutions for “What’s Next” or “What’s missing”
• Long-Term Relationship Model– Not expensive (but not cheap) resources– Focus on “Hire and Train” rather than just “Hire”– Mix of on-site and off-site development– Small projects but consistent resources across projects
• Many clients leverage us only part-time• Open Source
– Provide software but share in an Open Source model rather than commercial software model– Can provide jump start for “what’s next” without having to purchase software
• Innovative Solutions Examples– Development in Microsoft and Java Environments– Web Services (Services Orientated Architectures)
• Sharepoint/Portal Integrations– Open Source Alternatives
• Forms/Workflow, PDF Manipulation, Migration…– Viewing Alternatives
![Page 5: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/5.jpg)
5
TSG Open Source for Documentum/Alfresco - FAQ
• Why Open Source?– Commercial Model not viable for consulting firms– Promote our brand of services by giving away
great software• How Open Source
– Take “what’s next” solutions for clients– Rework to be generic– Use at new clients– Release to all as Open Source– Incorporate client and third party thoughts into
source
![Page 6: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/6.jpg)
6
So “What is next” for Life Sciences and Enterprise Content Management
• Consumer Application• Validation Impacts• Dynamic Workflow• Extranet access• Migration• Service Orientated Architecture (SOA)• High Performance Interface• Sharepoint Connectivity• Dynamic Property Display
• Time permitting – software selection Best Practices
![Page 7: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/7.jpg)
7
Consumer Application
• Spend lots of effort building a robust interface for authors and approvers…
• But often it is too much for people just looking to view and print (typically a majority of the user community)
![Page 8: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/8.jpg)
8
Consumer Application – Best Practices
• Develop quick application outside of repository for access to content and data
• Synchronization with content management to keep both systems up to date
• Benefits– High Performance - Significantly reduce time spent retrieving
documents– Simplified interface reduces training– Reduce load, both processing and licensing, on main
document management system– Independent of Content Management releases– Provide business continuity
• Clients –
![Page 9: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/9.jpg)
9
Consumer Application
Demo
![Page 10: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/10.jpg)
10
Business Continuity
Main Docbase Consumer InterfaceDatabase and File Server
Publish Job Publish
`
`
Consumers
1st Tier Continuity(Consumer Interface available even if Main system is down)
Site 1Local Host
Site 2Local Host
Main System
`
Site 1 Users
`
Site 2 Users
Copy
Copy
2nd Tier Continuity(Site Users have access to local
copy of Data and Content)
OpenSource
![Page 11: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/11.jpg)
11
Validation Impacts
• Most efforts – validation effort is the majority of project costs (40% - 60% average TSG client)
• System developed with user requirements but user requirements change over time– Changes that require revalidation are very expensive– Complex validation means long delay between releases
• Dissatisfied Users– Complex validation can mean trying to add “as much as
possible” to current release – impact to cost
![Page 12: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/12.jpg)
12
Best Practices for Validation – Configurable Applications
• Write system and system documentation to allow for configuration updates (not validation)– Add a new document type– Add a new property– Search and Search Results configurations– Update Forms – Update Workflow Templates or Rules
• Develop system to allow for configurable changes (no code)
Demo
![Page 13: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/13.jpg)
13
Workflow: Culture Challenge
Why do we roll-out Document Managementfunctionality quickly but workflow takes so much time?
• Unlike document management where some can use the system and get benefits, workflow requires all to use the system to achieve the business process benefit– Everyone needs to be in the process or it slower than
manual process– Everyone has to embrace the process or could back-slide
into quick needs going paper– Everyone has to complete the process accurately or
reliability of the system will be questioned.
![Page 14: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/14.jpg)
14
Workflow Challenges
![Page 15: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/15.jpg)
15
Workflow Best Practices
• To address complexity – make workflow process simpler– Simplify Workflow Creation
• Reduce number of user decisions• Build intelligence in the system rather than in the user• Allow workflow to change and adapt easily with business
process without having to have the user change and adapt
– Simplify Workflow Approval• Inbox• Approval
![Page 16: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/16.jpg)
16
Best Practices Workflow Example – Change Request
• Challenges– How do I fill this form out?– Form is complex… trying to handle multiple
situations– Who needs to approve?– Where is the form at in the process?– What do I approve – form or attached documents?– Frequent changes to the form
• Solution– Build on a configurable framework to enable
changes to business logic without revalidation
![Page 17: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/17.jpg)
17
Change Request - Configurable Form
• A “Forms Wizard” to Complete the Form (i.e. TurboTax)– System will generate the form when
finished– System would make sure correct fields
populated– Simplified user interface to reduce training
and improve data entry
Demo
![Page 18: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/18.jpg)
18
Change Request - Configurable Workflow
• A “Dynamic Workflow” to build the routing from the data on the form– Reduce need of user to “pick” or “build” a
workflow template– Reduce user decisions
• Form determines routing• Consistency in approval and business policies• Reduced errors and rerouting
Demo
![Page 19: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/19.jpg)
19
Change Request – Robust Approval Interface
• A Robust Approval Interface– Seeing all data to make approve/reject
decision– Seeing additional functional
• Delegate• Reassign
– Seeing customized approval• Discipline
Demo
![Page 20: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/20.jpg)
20
Active Wizard
• Combines Form and Workflow– Simplify Workflow Creation
• Reduce number of user decisions• Build intelligence in the system rather than in the user• Allow workflow to change and adapt easily with business
process without having to have the user change and adapt– Simplify Workflow Approval
• Inbox• Approval
– Certified by Documentum and supports both 5.x and 6.x• Clients Include:
– – Additional large clients by end of 2008
![Page 21: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/21.jpg)
21
Extranet for Documentum
• E-Submissions Example– e-Submissions leverages third-party medical
writers and medical investigators (CRO)– Current issues being faced when dealing with third
party authors:• Lack of an audit trail of third party activity and actions• Confidential documents residing in third party email
accounts and local hard drives• Third party authors not utilizing the latest e-Submission
document templates• The need to email documents to third party authors• The need to send hard copies of documents• The need to scan-in hard copy signature pages
![Page 22: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/22.jpg)
22
Extranet – Client Example
Standards, Templates, Processes Site 1
Site 2
Publishing COERepository
To Regulatory AgenciesStandards, Templates, Processes
CRO
Data Import
Extranet Application
![Page 23: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/23.jpg)
23
Infrastructure – Extranet
AbbottAuthor
Firewall
Web Server&
Docbase
Extranet Application
External3rd Party
User
DMZ Citrix
Internal Citrix
e-Submissions
Internal Citrix
![Page 24: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/24.jpg)
24
Extranet – Best Practices
• Should be included in Content Management Vision– External Users– Internal Users working remotely
• Simplified Interface– Reduce Training and risk of Errors
![Page 25: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/25.jpg)
25
Migration – Not a One Time Thing
• Initial Load– From a file system– From a database
• Ongoing– Add a new business application– On Going Bulk Loads
• Seen often for submission systems
– Future Upgrades– Consolidate due to Acquisitions/Mergers
![Page 26: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/26.jpg)
26
Best Practice – Migration Infrastructure
• Consistent (validated) tool for migrating one-time as well as ongoing migrations
• Configurable to adapt to new document types and data sources
• Simple to allow user to repeat the process for ongoing migration needs
• Able to apply business logic throughout the migration process
• Should be able to address failed documents/data that did not migrate
• Should evaluate with overall content management decisions
![Page 27: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/27.jpg)
27
Migration Example
Content&
XML index file
e-Subs Docbase
Validate & import
Staging Area
Migration Utility
export
1. Accept input from multiple sources and formats (Data Staging)2. Import data into Documentum in a batch approach3. Allow for configurable business rules to be applied to the
imported batch
![Page 28: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/28.jpg)
28
OpenMigrate
• OpenMigrate– Certified by EMC in September of 2006
• Released for D6– Multiple Implementations including:
• • • • • • • • • • Others shortly…..
– Demos and Source Code available from our website
![Page 29: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/29.jpg)
29
Service Orientated Architecture (SOA)
• Common ECM Pain Points– Upgrade multiple places (server and application)– Support and Maintenance– Duplication of code and business logic– Hard to ensure standards and best practices– Testing
• Benefits of Web Services (SOA)– Allows development of re-usable logic– Installed in a single location, accessible to multiple applications– Reduces upgrade effort– Reduces testing effort– Reduces support and maintenance effort– Platform independent
![Page 30: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/30.jpg)
30
TSG Web Services for Documentum Architecture
Login
1a(login
credentials)
1b(store ticket and Dctm
Session Mgr)
2f(query results)
3a(ticket, doc id)
3d(content,
properties)
2d(query criteria)
1c (ticket)
2a(ticket, query criteria)
DFC
Content Server / Docbase
Web Application
Documentum Web Services
SOAP Implementation
2e (DQL)
Authentication Service
ContentService
QueryService
DctmSession Factory
DctmQuery Factory
Query Results
Quer
y Cr
iteria
Document View
Prop
ertie
s
![Page 31: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/31.jpg)
31
Benefits of TSG Web Services
• Separation from Documentum– Web Services are not installed in docbase– Application can be developed with no reference to DFC or DQL– Reduced need for Documentum trained developers
• Ability to provides additional functionality not available with Documentum Web Services– Open Source– Example – calls to other systems, audit trails, autonumbering…..
• Support between Documentum releases due to DFC ties rather than BOF or WDK (5.1, 5.2.5, 5.3, 6.0, ???)
• Available in both .NET and Java Platforms (REST Now available)
• Clients – …• Demos and Downloads on our Website
![Page 32: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/32.jpg)
32
Why the need for a High Performance Interface for Content Management Applications?
• Typical Content Management Interface is built as a “one size fits all”– Either focused on library or collaboration– High Functionality requires training to correctly use– Business process requires consistent taxonomy/foldering – cost of
an error is high• Business needs quick access to simplified capabilities
– Inbox Access– Dual Document Display without having to size/position windows– Ability to quickly add or read Folder Notes– Quick list of “what to do next” actions
• Business needs simplified interface to realize business benefits (transaction throughput and reduced errors)– Insurance, Accounts Payable, Legal
![Page 33: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/33.jpg)
33
Typical Content Management Interface
![Page 34: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/34.jpg)
34
TSG Client Examples - Inbox
![Page 35: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/35.jpg)
35
TSG Client Example - Interface
![Page 36: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/36.jpg)
36
TSG Client Example - Double Pane View
![Page 37: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/37.jpg)
37
How are clients building High Performance Interfaces for content management?
• Best practice – isolation of content management system specifics from application– Library Calls or Web Services (Todd add more as necessary)– Allows development flexibility
• No need for Alfresco/Documentum developers for application• Consistent Support with other Web Development effort
• Develop system to allow for configurable changes (no code)– Can use for one application but can configurable for
additional applications• Add a new document type• Add a new property• Search and Search Results configurations
![Page 38: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/38.jpg)
38
Sharepoint Integration
• Microsoft is a major player– More and more integration with Office Suite– Significant price point with Sharepoint for
Microsoft customers– Issues with portal versus ECM
• Which one is Sharpoint – is it both?
![Page 39: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/39.jpg)
39
Two Approaches
• Sharepoint as ECM Tool• Sharepoint as Portal
– With connectivity to ECM Tool
![Page 40: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/40.jpg)
40
Sharepoint/Documentum Integration - Portal
• Oil and Gas Customer• Reviewed Documentum Offering
– Vorsite• Reviewed Wingspan Offering• Developed Open Source SOA approach
leveraging OpenContent
• Results can be found on TSG Web site as well as Whitepaper
Demo
![Page 41: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/41.jpg)
41
Properties on Documents
• Typical paper based method is to add properties in header/footer of word document– Version, Effective Date, Title, Status
• With Content Management, these items are also managed systematically as properties (attributes) on the document as well
• Compliance and usability issues if the attributes in the repository differ from the attributes on the document– How to add things over time on document like approval date
or electronic signature signoff?
![Page 42: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/42.jpg)
42
Best Practice - Dynamic Properties Display
• User does not enter properties within the document.• System automatically generates header, footer,
watermark for viewed content– Simple
• Dynamically display property values on document• Can include signature elements as well
– Advanced Features• Controlled Printing• Generation of Master Batch Record• Complex Rules used to determine which watermark to display• Multiple page sizes
![Page 43: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/43.jpg)
43
Dynamic Properties: Client Example
![Page 44: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/44.jpg)
44
PDF Aqua Alternative
• PDF Aqua Issues– Own Servers– Difficult Support– License Fees– Long term concern about development
• Software Alternatives– Multiple consulting firms developing– Open Source PDF Manipulation with iText– TSG has implemented Open Overlay at J&J, APP and
Astellas– Software and Demo on our website
Demo
![Page 45: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/45.jpg)
45
Trends affecting ECM
• Big get bigger– Documentum bought by EMC and dominate within the industry– IBM buys FileNet– Niche Players (Novasoft, OpenText) fading
• Sharepoint and SAP– Microsoft is a major player– SAP is other that we see in this area– Minimal concern regarding Oracle/Stellant
• Extranet options– To support both remote workforces as well as third-party relationships
• Open Source– Could be the disruptor, as add-ons to other repositories or as the
repository itself • Minimal internal IT development efforts
– Looking for configurable COTS approach or outside vendors (outsource)
![Page 46: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/46.jpg)
46
Software Selection
• Requirements Gathering– Develop list of requirements– Develop weighting for requirements
• % based rather than point system• Let the data lead the group to the solution
• Scoring– Review potential solutions– Work with users on weightings– Entire Group should agree on weightings
![Page 47: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/47.jpg)
47
Software Selection: Example – Novasoft versus Documentum
![Page 48: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/48.jpg)
48
Best Practice - Content Management Software Selection
• Items To Focus On– Future Vision– Ability to fulfill their vision– Back End Architecture – how will the application be
constructed?• Items of Less Importance
– Look and feel of current interface– Specific functionality requirements
• Key - HOW YOU USE THE DATA– Don’t let seasoned sales reps and a sharp interface
influence your decision• Interface will change over time• Interface was least important for Abbott Diagnostic
![Page 49: Phase Two: What’s Next for Life Sciences and Enterprise Content Management](https://reader035.vdocument.in/reader035/viewer/2022070516/5870eb9c1a28abcf288b6d23/html5/thumbnails/49.jpg)
49
Questions/Follow Up
• Dave Giordano– 312-372-7777 x221– [email protected]
• Ellen Ryan– 312-372-7777 x256– [email protected]