ECM: Documentum – .NET

---

Watched Developing with Documentum in a .NET Environment [10959] today which you can also review here:

http://mylearn.documentum.com/mgrCourse/courseSummary.cfm?id_course=10959&id=194419

Other threads in the forum talk about how to get a login onto this site.

I chose it because we continue to have clients talking to us about leveraging ECM investments they have made more fully. Integrating them into the transactional systems where it makes sense. Some of those clients are MSFT focused (two actually).

Note this webcast is a bit dated (6/2004) but the keys I took away was:

1. Old School EMC wins. Documentum had a very robust model at the time (2004) for enabling integration from Visual Studio. Better than what I see today w/ Stellent.

2. New School … Webservices … ?. Documentum was working on (in 2004) webservices. They didn’t have as good as an answer as Stellent had then. However thier strategy is the same (java patterns gen’d to wsdl). I expect Stellent keeps this lead or they are at par at this time.

Not worth listening to directly … my notes should suffice. The speaker didn’t elaborate much from the slides and wasn’t very dynamic either.

Here are the notes.

Quote:

EMC: Developing w/ Documentum in .NET……….○ NOTE GIVEN ON 6/24/04 — So might be dated. ……….○ ……….○ 2:00 — David Folk. Product Manager @ EMC for Documentum ……….○ 2:30 — MSFT Features Considered ………………..§ Support ………………..§ Scale ………………..§ Security ………………..§ API ………………..§ Migration (from MSFT or other platforms) ……….○ 4:00 — Goal is to be native in VS (plug ins, etc) ………………..§ Interop Assembly (Documentum Foundation Classes – DFC) ………………..§ Documentum ADO.NET Services (DAS) ………………..§ 7:30 — Best Practices and examples of .NET integration w/ Documentum is on developer site ………………..§ Business Object Framework ……….○ 8:45 — DFC Primary Interop Assembly (PIA) ………………..§ DFC = Documentum Foundation Class (the layer he is responsible for). Client API’s for accessing server. ………………..§ Java based API’s ………………..§ 100 interfaces about ………………..§ PIA allows seemless access from .NET of DFC ………………..§ Already had a COM library ………………..§ PIA uses COM code (bauer thought — overhead issue?) … layer 1 — DFV (Java), layer 2 — DFJB (COM) — layer 3 DFC PIE (.nET) …………………………□ Says there is no performance impacts from clients yet (bauer thought but PIA is new at this time) ………………..§ 14:00 – PIA .NET 1.1 based at this time …………………………□ Installed in global assembly cache …………………………□ IntelliSense and Object Browser support (bauer thought – sounds ‘simplier’ than Stellent) ………………..§ 17:00 – Full help support w/ intellisense (not the norm for other vendors) ………………..§ 17:30 – Object Browser – Full support. See interfaces in PIA. Methods per intfc. Online help. …………………………□ Without this you would have to translate the java doc ………………..§ 19:00 – Intfc upgrade can be separate (distinct policy file) ……….○ 19:20 – Data Access, .NET and Documentum ………………..§ Documentum ADO.NET Services (DAS) ………………..§ ADO.NET … supports disconnected and connected sessions ………………..§ If you are thinking Crystal Reports … ADO.NET can do more (as shown w/ EMC) ………………..§ ADO.NET is about getting access to data bound controls that can bind to a data structure (so EMC used that) ………………..§ Use widgets to interact with the data store (odbc, dfc, ado.net, jdbc, webDAV, ftp, file share, dfc) ………………..§ Performance (avoid layers mentioned above) … (bauer thought – I thought that wasn’t an issue [wink]) ………………..§ Use for Winforms, ASP.NET, and crystal ……….○ 25:30 – Arch of ADO.Net ………………..§ Shows how Documentum works through this …………………………□ Disconnected (data grid, listbox, combobox) — Data View, Data Table, XML, Data Set, Data Adapter, Connection. …………………………□ Connected — Data Reader, Command, Connection ………………..§ 28:00 – Standard Interfaces of ADO are supported ………………..§ Meta data access simplified here (via DAS) ……….○ 31:10 – ………………..§ ADO.NET will be foundation for reporting services (vs ODBC) ………………..§ Could speed up webpart development ……….○ 32:39 – Static Demo of DAS integration in VS. ………………..§ DocBase command ………………..§ 10 step process walked through ……….○ 35:00 – DAS is a value add (pay extra) product from Documentum ………………..§ Could do DAS functions w/ DFC … just makes it easier ……….○ 36:30 – Other products ………………..§ Webservices infrastructure for accessing business objects ………………..§ Release 5.3 planned – provide patterns implemented in java. Documentum provides tools to register that w/ a run time. (bauer comment — So it’s a wizard–similar to stellent) ………………..§ Important (even w/ java -> wizard -> wsdl) since webservices become the norm ………………..§ Longer term looking to show a library of webservices (versus having to gen from pattersn now). Acknowledge extending webservices will be very complex. ……….○ 41:00 – Looking ahead – Support ………………..§ O12 – xml, research pane, smart docs ………………..§ Webparts ………………..§ Smart clients (avalon) ………………..§ WinFS ………………..§ Yukon ……….○ 43:30 – Resources ………………..§ Developer site – http://customernet.documentum.com/developer/dotNET.html ………………..§ Disc Forums – http://forums.documentum.com/jive3/index.jspa ………………..§ Dev News – http://customernet.documentum.com/developer/newsletters/newsletter0104.htm ……….○ 44:00 Q&A ………………..§ David Robertson – Petro Canada – Liscensing. EMC: Developing w/ Documentum in .NET ……….○ NOTE GIVEN ON 6/24/04 — So might be dated. ……….○ ……….○ 2:00 — David Folk. Product Manager @ EMC for Documentum ……….○ 2:30 — MSFT Features Considered ………………..§ Support ………………..§ Scale ………………..§ Security ………………..§ API ………………..§ Migration (from MSFT or other platforms) ……….○ 4:00 — Goal is to be native in VS (plug ins, etc) ………………..§ Interop Assembly (Documentum Foundation Classes – DFC) ………………..§ Documentum ADO.NET Services (DAS) ………………..§ 7:30 — Best Practices and examples of .NET integration w/ Documentum is on developer site ………………..§ Business Object Framework ……….○ 8:45 — DFC Primary Interop Assembly (PIA) ………………..§ DFC = Documentum Foundation Class (the layer he is responsible for). Client API’s for accessing server. ………………..§ Java based API’s ………………..§ 100 interfaces about ………………..§ PIA allows seemless access from .NET of DFC ………………..§ Already had a COM library ………………..§ PIA uses COM code (bauer thought — overhead issue?) … layer 1 — DFV (Java), layer 2 — DFJB (COM) — layer 3 DFC PIE (.nET) …………………………□ Says there is no performance impacts from clients yet (bauer thought but PIA is new at this time) ………………..§ 14:00 – PIA .NET 1.1 based at this time …………………………□ Installed in global assembly cache …………………………□ IntelliSense and Object Browser support (bauer thought – sounds ‘simplier’ than Stellent) ………………..§ 17:00 – Full help support w/ intellisense (not the norm for other vendors) ………………..§ 17:30 – Object Browser – Full support. See interfaces in PIA. Methods per intfc. Online help. …………………………□ Without this you would have to translate the java doc ………………..§ 19:00 – Intfc upgrade can be separate (distinct policy file) ……….○ 19:20 – Data Access, .NET and Documentum ………………..§ Documentum ADO.NET Services (DAS) ………………..§ ADO.NET … supports disconnected and connected sessions ………………..§ If you are thinking Crystal Reports … ADO.NET can do more (as shown w/ EMC) ………………..§ ADO.NET is about getting access to data bound controls that can bind to a data structure (so EMC used that) ………………..§ Use widgets to interact with the data store (odbc, dfc, ado.net, jdbc, webDAV, ftp, file share, dfc) ………………..§ Performance (avoid layers mentioned above) … (bauer thought – I thought that wasn’t an issue [wink]) ………………..§ Use for Winforms, ASP.NET, and crystal ……….○ 25:30 – Arch of ADO.Net ………………..§ Shows how Documentum works through this …………………………□ Disconnected (data grid, listbox, combobox) — Data View, Data Table, XML, Data Set, Data Adapter, Connection. …………………………□ Connected — Data Reader, Command, Connection ………………..§ 28:00 – Standard Interfaces of ADO are supported ………………..§ Meta data access simplified here (via DAS) ……….○ 31:10 – ………………..§ ADO.NET will be foundation for reporting services (vs ODBC) ………………..§ Could speed up webpart development ……….○ 32:39 – Static Demo of DAS integration in VS. ………………..§ DocBase command ………………..§ 10 step process walked through ……….○ 35:00 – DAS is a value add (pay extra) product from Documentum ………………..§ Could do DAS functions w/ DFC … just makes it easier ……….○ 36:30 – Other products ………………..§ Webservices infrastructure for accessing business objects ………………..§ Release 5.3 planned – provide patterns implemented in java. Documentum provides tools to register that w/ a run time. (bauer comment — So it’s a wizard–similar to stellent) ………………..§ Important (even w/ java -> wizard -> wsdl) since webservices become the norm ………………..§ Longer term looking to show a library of webservices (versus having to gen from pattersn now). Acknowledge extending webservices will be very complex. ……….○ 41:00 – Looking ahead – Support ………………..§ O12 – xml, research pane, smart docs ………………..§ Webparts ………………..§ Smart clients (avalon) ………………..§ WinFS ………………..§ Yukon ……….○ 43:30 – Resources ………………..§ Developer site – http://customernet.documentum.com/developer/dotNET.html ………………..§ Disc Forums – http://forums.documentum.com/jive3/index.jspa ………………..§ Dev News – http://customernet.documentum.com/developer/newsletters/newsletter0104.htm ……….○ 44:00 Q&A ………………..§ David Robertson – Petro Canada – Liscensing.

ECM: Documentum – .NET (2)

Watched Developing with Documentum in a .NET Environment [10959] today which you can also review here:

http://mylearn.documentum.com/mgrCourse/courseSummary.cfm?id_course=10959&id=194419

Other threads in the forum talk about how to get a login onto this site.

I chose it because we continue to have clients talking to us about leveraging ECM investments they have made more fully. Integrating them into the transactional systems where it makes sense. Some of those clients are MSFT focused (two actually).

Note this webcast is a bit dated (6/2004) but the keys I took away was:

1. Old School EMC wins. Documentum had a very robust model at the time (2004) for enabling integration from Visual Studio. Better than what I see today w/ Stellent.

2. New School … Webservices … ?. Documentum was working on (in 2004) webservices. They didn’t have as good as an answer as Stellent had then. However thier strategy is the same (java patterns gen’d to wsdl). I expect Stellent keeps this lead or they are at par at this time.

Not worth listening to directly … my notes should suffice. The speaker didn’t elaborate much from the slides and wasn’t very dynamic either.

Here are the notes.

Quote:

EMC: Developing w/ Documentum in .NET……….○ NOTE GIVEN ON 6/24/04 — So might be dated. ……….○ ……….○ 2:00 — David Folk. Product Manager @ EMC for Documentum ……….○ 2:30 — MSFT Features Considered ………………..§ Support ………………..§ Scale ………………..§ Security ………………..§ API ………………..§ Migration (from MSFT or other platforms) ……….○ 4:00 — Goal is to be native in VS (plug ins, etc) ………………..§ Interop Assembly (Documentum Foundation Classes – DFC) ………………..§ Documentum ADO.NET Services (DAS) ………………..§ 7:30 — Best Practices and examples of .NET integration w/ Documentum is on developer site ………………..§ Business Object Framework ……….○ 8:45 — DFC Primary Interop Assembly (PIA) ………………..§ DFC = Documentum Foundation Class (the layer he is responsible for). Client API’s for accessing server. ………………..§ Java based API’s ………………..§ 100 interfaces about ………………..§ PIA allows seemless access from .NET of DFC ………………..§ Already had a COM library ………………..§ PIA uses COM code (bauer thought — overhead issue?) … layer 1 — DFV (Java), layer 2 — DFJB (COM) — layer 3 DFC PIE (.nET) …………………………□ Says there is no performance impacts from clients yet (bauer thought but PIA is new at this time) ………………..§ 14:00 – PIA .NET 1.1 based at this time …………………………□ Installed in global assembly cache …………………………□ IntelliSense and Object Browser support (bauer thought – sounds ‘simplier’ than Stellent) ………………..§ 17:00 – Full help support w/ intellisense (not the norm for other vendors) ………………..§ 17:30 – Object Browser – Full support. See interfaces in PIA. Methods per intfc. Online help. …………………………□ Without this you would have to translate the java doc ………………..§ 19:00 – Intfc upgrade can be separate (distinct policy file) ……….○ 19:20 – Data Access, .NET and Documentum ………………..§ Documentum ADO.NET Services (DAS) ………………..§ ADO.NET … supports disconnected and connected sessions ………………..§ If you are thinking Crystal Reports … ADO.NET can do more (as shown w/ EMC) ………………..§ ADO.NET is about getting access to data bound controls that can bind to a data structure (so EMC used that) ………………..§ Use widgets to interact with the data store (odbc, dfc, ado.net, jdbc, webDAV, ftp, file share, dfc) ………………..§ Performance (avoid layers mentioned above) … (bauer thought – I thought that wasn’t an issue [wink]) ………………..§ Use for Winforms, ASP.NET, and crystal ……….○ 25:30 – Arch of ADO.Net ………………..§ Shows how Documentum works through this …………………………□ Disconnected (data grid, listbox, combobox) — Data View, Data Table, XML, Data Set, Data Adapter, Connection. …………………………□ Connected — Data Reader, Command, Connection ………………..§ 28:00 – Standard Interfaces of ADO are supported ………………..§ Meta data access simplified here (via DAS) ……….○ 31:10 – ………………..§ ADO.NET will be foundation for reporting services (vs ODBC) ………………..§ Could speed up webpart development ……….○ 32:39 – Static Demo of DAS integration in VS. ………………..§ DocBase command ………………..§ 10 step process walked through ……….○ 35:00 – DAS is a value add (pay extra) product from Documentum ………………..§ Could do DAS functions w/ DFC … just makes it easier ……….○ 36:30 – Other products ………………..§ Webservices infrastructure for accessing business objects ………………..§ Release 5.3 planned – provide patterns implemented in java. Documentum provides tools to register that w/ a run time. (bauer comment — So it’s a wizard–similar to stellent) ………………..§ Important (even w/ java -> wizard -> wsdl) since webservices become the norm ………………..§ Longer term looking to show a library of webservices (versus having to gen from pattersn now). Acknowledge extending webservices will be very complex. ……….○ 41:00 – Looking ahead – Support ………………..§ O12 – xml, research pane, smart docs ………………..§ Webparts ………………..§ Smart clients (avalon) ………………..§ WinFS ………………..§ Yukon ……….○ 43:30 – Resources ………………..§ Developer site – http://customernet.documentum.com/developer/dotNET.html ………………..§ Disc Forums – http://forums.documentum.com/jive3/index.jspa ………………..§ Dev News – http://customernet.documentum.com/developer/newsletters/newsletter0104.htm ……….○ 44:00 Q&A ………………..§ David Robertson – Petro Canada – Liscensing. EMC: Developing w/ Documentum in .NET ……….○ NOTE GIVEN ON 6/24/04 — So might be dated. ……….○ ……….○ 2:00 — David Folk. Product Manager @ EMC for Documentum ……….○ 2:30 — MSFT Features Considered ………………..§ Support ………………..§ Scale ………………..§ Security ………………..§ API ………………..§ Migration (from MSFT or other platforms) ……….○ 4:00 — Goal is to be native in VS (plug ins, etc) ………………..§ Interop Assembly (Documentum Foundation Classes – DFC) ………………..§ Documentum ADO.NET Services (DAS) ………………..§ 7:30 — Best Practices and examples of .NET integration w/ Documentum is on developer site ………………..§ Business Object Framework ……….○ 8:45 — DFC Primary Interop Assembly (PIA) ………………..§ DFC = Documentum Foundation Class (the layer he is responsible for). Client API’s for accessing server. ………………..§ Java based API’s ………………..§ 100 interfaces about ………………..§ PIA allows seemless access from .NET of DFC ………………..§ Already had a COM library ………………..§ PIA uses COM code (bauer thought — overhead issue?) … layer 1 — DFV (Java), layer 2 — DFJB (COM) — layer 3 DFC PIE (.nET) …………………………□ Says there is no performance impacts from clients yet (bauer thought but PIA is new at this time) ………………..§ 14:00 – PIA .NET 1.1 based at this time …………………………□ Installed in global assembly cache …………………………□ IntelliSense and Object Browser support (bauer thought – sounds ‘simplier’ than Stellent) ………………..§ 17:00 – Full help support w/ intellisense (not the norm for other vendors) ………………..§ 17:30 – Object Browser – Full support. See interfaces in PIA. Methods per intfc. Online help. …………………………□ Without this you would have to translate the java doc ………………..§ 19:00 – Intfc upgrade can be separate (distinct policy file) ……….○ 19:20 – Data Access, .NET and Documentum ………………..§ Documentum ADO.NET Services (DAS) ………………..§ ADO.NET … supports disconnected and connected sessions ………………..§ If you are thinking Crystal Reports … ADO.NET can do more (as shown w/ EMC) ………………..§ ADO.NET is about getting access to data bound controls that can bind to a data structure (so EMC used that) ………………..§ Use widgets to interact with the data store (odbc, dfc, ado.net, jdbc, webDAV, ftp, file share, dfc) ………………..§ Performance (avoid layers mentioned above) … (bauer thought – I thought that wasn’t an issue [wink]) ………………..§ Use for Winforms, ASP.NET, and crystal ……….○ 25:30 – Arch of ADO.Net ………………..§ Shows how Documentum works through this …………………………□ Disconnected (data grid, listbox, combobox) — Data View, Data Table, XML, Data Set, Data Adapter, Connection. …………………………□ Connected — Data Reader, Command, Connection ………………..§ 28:00 – Standard Interfaces of ADO are supported ………………..§ Meta data access simplified here (via DAS) ……….○ 31:10 – ………………..§ ADO.NET will be foundation for reporting services (vs ODBC) ………………..§ Could speed up webpart development ……….○ 32:39 – Static Demo of DAS integration in VS. ………………..§ DocBase command ………………..§ 10 step process walked through ……….○ 35:00 – DAS is a value add (pay extra) product from Documentum ………………..§ Could do DAS functions w/ DFC … just makes it easier ……….○ 36:30 – Other products ………………..§ Webservices infrastructure for accessing business objects ………………..§ Release 5.3 planned – provide patterns implemented in java. Documentum provides tools to register that w/ a run time. (bauer comment — So it’s a wizard–similar to stellent) ………………..§ Important (even w/ java -> wizard -> wsdl) since webservices become the norm ………………..§ Longer term looking to show a library of webservices (versus having to gen from pattersn now). Acknowledge extending webservices will be very complex. ……….○ 41:00 – Looking ahead – Support ………………..§ O12 – xml, research pane, smart docs ………………..§ Webparts ………………..§ Smart clients (avalon) ………………..§ WinFS ………………..§ Yukon ……….○ 43:30 – Resources ………………..§ Developer site – http://customernet.documentum.com/developer/dotNET.html ………………..§ Disc Forums – http://forums.documentum.com/jive3/index.jspa ………………..§ Dev News – http://customernet.documentum.com/developer/newsletters/newsletter0104.htm ……….○ 44:00 Q&A ………………..§ David Robertson – Petro Canada – Liscensing.

ECM: Documentum – Imaging

Digging around in EMC’s ‘myLearn’ site this morning. Decided to watch this webcast around BPM and Imaging given the ongoing activity in pipeline around process automation. You find it by loggin in here:

http://documentum.myLearn.com

searching for “BPM and Imaging – KOPC 2006”. FYI, search the forums for instructions on how to get a working login

http://wis-demo.gr.com/phpbb2/viewtopic.php?p=8607#8607

At 10,000 feet the core message I heard was:

Quote:

1. Nice Overview of an ECM solution 7 minutes in. Wove via four areas. We should leverage similar in position of any ECM (Sharepoint, NW, Stellent, Documentum). 2. Excellent example of collaboration integration to thier business process automation efforts 31 minutes in. In short they create workflow steps that create a collobration space (eRoom in thier lingo) that has defined activities that need to be completed at which point the collaboration room rengages the workflow and archives itself into the process with the other docs being manipulated.

Here are my detail notes:

Quote:

• BPM and Imaging – KOPC 2006 Pasted from <http://mylearn.documentum.com/mgrCourse/launchCourse.cfm?id_registrant=193270&id_host=325&id_course=18973&gt; • Solution: Document and Image Processing • 2:14 – Paper Management Problem ………..○ Still see customers w/ this problem ………..○ Manual ………..○ Official files can only be sequentially handles ………..○ Compliance controls are hard on paper ………..○ Customer service issues on paper • 4:00 ROI easy on paper ………..○ Copies ………..○ Filing/Retrieve ………..○ Avg stats – 19 copies of doc, $20 to file, $120 to search for misfiled, lose 1 out of 20 docs, 25 hours to recreate lost docs, $8 to process invcs (70% is doc handling) • 5:12 EMC acquires captiva (capture software). ………..○ Over holidays • 7:00 Imaging Vision – Technology View ………..○ Focuses (industry) ………………….§ Mortgage, Insurance Claims, New Account, Invc Processing ………..○ Process Services ………………….§ Colloboration Workspaces ………………….§ Business Process Automation ………..○ Content Services ………………….§ Docs, Forms, Rich Media, Web, Images, Msgs, Reports ………………….§ Capture / Edit ………………….§ Library ………………….§ Transformation ………………….§ Classification ………………….§ Search ………………….§ Publish/Distribute ………..○ Repository Services ………………….§ Compliance / Retention ………………….§ Policy Mgmt ………………….§ Archival ………………….§ Intelligent Storage ………..○ Integration Services • 10:00 — Acartus Acquired ………..○ That plus Captiva gives them end-to-end focus • 11:00 — Three Focuses ………..○ Capture ………..○ Process ………..○ Archive • 12:00 – Capture ………..○ Captiva Focus – Products – InputAccel (base platform), FormWare, Dispatcher, InputAccel(invcs), eInput ………..○ Devices: Scan, Fax, Multifunction, etc ………..○ Extract / Validate information from the document (OCR) ………..○ Doc Types Handled: Structured (all same), Semi Structured (different by vendor but large groups similar), Unstructured (each doc diff) ………..○ 17:15 – Dtl review of InputAcel ………………….§ 18:30 talk of extracting data from images and how ………..○ 20:00 – ABM-AMRO Customer Example ………………….§ 800,000 images a day processed ………………….§ Multi-Function devices at branch submits to a central solution ………..○ 22:00 – Captiva remains separate, continues to sell for FileNET’s and Stellents of the world • 24:30 – Process ………..○ Real value add is streamlining processes ………..○ They call it “Business Process Management” ………..○ See four steps ………………….§ Model / Simulate ………………….§ Deploy / Execute ………………….§ Monitor / Manage ………………….§ Analyze / Optimize ………..○ Products they offer: ………………….§ Required ……………………………□ Process Engine (model/simulate) ……………………………□ Business Process Engine (deploy/execute) ………………….§ Optional ……………………………□ Business Process Services (Webservices layer) ……………………………□ Collaborative Edition ……………………………□ Formlet user lisc ……………………………□ Process connectors for: iLog (rules eng), IDS Sheer (Simulator), Cognos (Reporting) ………..○ 29:30 – High Volume Process Enablement ………………….§ Queues, Queue management, workflow around queues ………………….§ Part of Documentum 5.3 (10/2005) ………..○ 31:00 – Collaboration Integration ………………….§ Manage collaboration objects as part of record ………………….§ Part of all Documentum areas (web, outlook, etc) ………………….§ Design Business Process … certain steps can be flagged as requiring collaboration. Talk to collaborative edition (eRoom) … create room, add data, add people, trigger alerts back to room, have exits on room that retrigger process. ………..○ 34:00 – Process Specific BPM Templates ………………….§ Use in pre-sales ………………….§ Offer to clients as starting point ………………….§ Loan Origination, Claims Processing, New Account Setup (late 2006) ………..○ 34:30 – Recent Deals (q4) on BPM ………………….§ Auto Insurer. Field adjusters loading content files to HQ. BPS used to receive and route uploads to be processed. ………………….§ Chip MFG. Contract management. ………………….§ Credit Card Operator. Dispute Management Application. Rules engine • 38:00 – Archive ………..○ Store / Archive / Retain ………..○ Focus: End of life transactions and assoc docs, COLD ………..○ Compliance / Retention functionality is top of mind for the business right now ………..○ ILM? Image Lifecycle Management ………………….§ Steps: Create/Capture, Change, Route, Approve, Publish, Retire ………………….§ Claim routing/High availability ………………….§ Large Volume ………………….§ Process focus ………………….§ Clear need for ways for better usage of storage (huge storage keys) ………………….§ Strong compliance / retrieval needs ………..○ 42:00 – Example – Cincinnati Financial ………………….§ Processes Enabled: Underwriting, Marketing/New Product, Legal/Compliance, Policy Creation / Admin, Claims Admin, Customer Service • 44:00 – Key Imaging Applications ………..○ Horizontal Apps (PO, Invc, Mail Room) ………..○ Fin Svcs ………..○ Gov ………..○ Life Sci (Patient, Case Rpts, HIPPA, Product Research/Trial Docs) • 48:30 Competitive Positioning (per EMC) ………..○ IBM – ………………….§ Strong – Viable vendor, MQ ………………….§ Weak – Legacy Platform, Complex, ………..○ FileNET ………………….§ Strong: Well established in FS vertical, strong partners ………………….§ Weak: Not complete, migration to p8 is still a fee and hard ………..○ Mobius ………………….§ Strong: Known COLD vendor ………………….§ Weak: No breadth, imaging, or BPM ………..○ Others (Stellent, Hummingbird, Interwoven) ………………….§ Message: Full ECM platform and EMC vendor. ………………….§ Interesting didn’t talk to Strength and Weakness