Analysis of EMC Predictions

I have just discovered the Technology Services Group (TSG) blog. It has some really great posts in it. The Technology Services Group work with ECM technologies, and their posts describe how they apply these.

On December 10 they published a post titled “Predictions for EMC Documentum in 2013“. While their other posts have had some great material in them, the above mentioned post didn’t impress me.

TSG made predictions such as “Webtop Installations will start to Fade“, “Lots of Interface Evaluations“, and “Slowly Upgrading to D7“. These predictions are not very hard to make. Whenever any software company brings out new versions of their software (often which makes the earlier version obsolete), companies start considering, and evaluating the new software, Sorry – that’s a no-brainer.

Further to that, there were predictions that, in 2013, “Performance will be a hot topic” (when isn’t performance a ‘hot topic’? I’ve never heard anyone say “performance is slow, but that’s ok”), “Mobile Demands continue to grow“, and “Cloud Discussions, but Slow Adoption“. For these last two, there is nothing really surprising about them (“wow - did you know that people will be wanting to use an EMC app on their mobile device?!”).

The second to last prediction “SharePoint Discussions are Dead” reinforces what others are also saying (Even Gartner has ranked MS SharePoint lower this year in their Magic Quadrants, and you can read more on this in Herman Prasad’s post)

This leads me to the last prediction: “Maintenance Costs Increasing“….<speechless>

TSG – I’m not trying to be mean. You have written some great stuff, but these predictions are hardly that.

 

Promise #11 – FirstDoc and D2

Refer14 Unfulfilled Promises

Background

In my post “FirstDoc & D2″ I told you all (breathlessly) that there was going to be a webinar where CSC were going to discuss their plans regarding EMC’s D2 interface.

Verdict

Unable to Fulfil Due to a family commitment I was unable to attend this webinar. I had contacted with some people at CSC beforehand to to see if it would be recorded. The answer I got was “Yes”, but since then I have been advised that, because of the commercially sensitive nature of the webinar, it wasn’t. I certainly understand that that decision has been made. As such, though, I am not able to actually deliver on this promise.

FirstDoc & D2 – getting funky together

In an earlier post I discussed how EMC’s are now licencing D2 technology from C6, and that this meant that CSC are having to change their user interface strategy.

Well…on Tuesday, 6th of March, there is a webinar that will reveal what has been going on “behind the scenes”.

Some of my favourite CSC people will be discussing CSC’s “new, improved” customer interface strategy as “FirstDoc embraces D2″ (their words, not mine).

I’ve been following this with interest for awhile, and I’ve registered for the webinar.

I’ll let you know all about it after the 6th.

Related articles

CSC has had to change their plans…

In my earlier post about the FirstDoc User Group conference that was held in Vienna earlier this year, I wrote about CSC’s User Interface strategy.

To recap – CSC produce technology that provides a compliance layer for content management systems. Although available for SharePoint systems (under the name “FirstPoint), the predominant application is “FirstDoc” which is built to work with, and integrate into, EMC’s Documentum.

The native FirstDoc client application is interwoven into Documentum’s client application and, as a result, CSC need to ensure that they shadow any architecture decisions EMC makes.

Over the last few years EMC have been making it clear that their way forward (with regards to their client applications) was to be with a technology called xCP. This would allow developers to create applications through configuring and then assembling components. The core idea is that “complex solutions are composed from interaction of Documentum objects with business processes”. Initially it was made clear that this technology was for case-based applications, but, the later versions were being promoted as the “interface solution”. (You can download EMC’s whitepaper on xCP here).

At the same time, EMC have announced that they had made plans to retire their current client application “WebTop”, and the idea was to replace it with xCP technology. CSC had been invited to be involved with version 2.1 of xCP to ensure that FirstDoc functionality could be tightly integrated with it.

At this year’s Momentum, however, EMC announced that they had licenced D2 technology from a French company called C6. (You can read the announcement here.) C6 have been EMC partners for a long time, and I recall seeing them at many previous Momentum conferences, where they have certainly caught people’s attention.

C6′s products work on the basis of “configuration“, and will be technology for “content-centric” applications.

C6 have also released x3, which is a “widget-based, agnostic browser, client interface that enables to extend the use of D2 Client to various browsers such as: Firefox, Safari, Chrome, Opera.”.

 Obviously this will offer incredible advantages. Especially in this mobile-age, and especially for industries (such as Pharma), that, because of strict compliance requirements (and the overarching mindset that that brings with it), have not been as ”agile” as they could.

CSC have announced that they are working together with EMC to ensure that the tight integration between CSC’s FirstDoc client interface, and D2, will be maintained.

I am watching this space with interest…

Momentum – another year – another set of announcements

As mentioned – I didn’t get a chance to go to Momentum in Berlin this year.

However I was able to get a pretty good idea of what was covered thanks to the great streaming video that EMC had, as well as the great tweets that be “tweeted”, and the excellent blog posts that were written.

I’ve been to a few Momentum’s now, and while they are a great opportunity to really “talk” with the EMC people, and their partners, I always had the feeling that the things I heard, I had, more or less, heard at the previous Momentum, or that what was big one year, suddenly falls to the wayside.

Now I realise that changes to strategy get made all the time, and that new technology takes more than one year to design, develop and integrate, and it’s great to see that EMC is: a) responsive to changes in the market environment, b) keeping its customers well informed of the progress that they are making, but to mention a few examples…

  1. Centerstage – in 2009 this was being hawked as the new Documentum interface. Now where is it?
  2. XPlore – really glad to see that EMC have been busy with their own search engine. And I have been following this with interest. However has there been anything new over the last couple of Momentums?
  3. SharePoint – also really interested in this but, again, are we hearing anything new with regards to the EMC offering for integration with SharePoint?

It wasn’t until I spoke with a colleague, who made a similar comment, that I started to really think about this. Then I saw this tweet from Jed Spink that I realised that others also had the same thought.

I appreciate that my view might not be a perfect one, and that there might be situations where I am wrong.

I want to hear what you think? Am I right? Or am I totally wrong?…

Europe Momentum 2011 – Resources for those who couldn’t be there…

This year’s EMC’s European Momentum is being was held in Berlin.

The Momentum conference is something I have always tried to attend. It  is a great opportunity to:

  • find out what EMC’s strategies are.
  • Attend great sessions to learn more
  • Meet great people
  • Share ideas & experiences,
  • etc, etc.
So – what if you can’t couldn’t attend?
I’m trying to put together a list of resources that will give you the opportunity to follow Momentum online.

Hopefully I will be adding to this page as I find more excellent ways to “be there” (virtually).

Also check out my Google+ stream. I’ll post regular updates there as well. (https://plus.google.com/u/0/110973870217970854594/posts)

Blogs

  • More to come…

Facebook

Official site

Images and Videos from the Conference

Tweets


Presentations


SPX Series – A little bit of history

This is part of the SPX Series

Previous post: SPX Series – SharePoint eXperience – (aka SPX) – Series Introduction

First off – I want to explain that I am, in no shape or form, an SPX “expert”. I’m just a guy who has been using SPX since it was first released. I’m not a coder, so can’t tell you all the cool ways that the web parts can be tweaked, or made to dance. I am able to share with you the some of the “lessons learned”, and tips . that I have picked up over time. Some of what I write might be incorrect. Please feel free to let me know if that is the case.

And, where possible, if there are other resources that explain something better than I can, I’ll point you to it.

So without further delay I will launch into today’s SPX post…”A little bit of history“.

SharePoint

In 2007 Microsoft introduced SharePoint 2007.

As well as providing the ability to store content in its own repositories (doclibs, lists), it also provided web sites that could be populated with web parts that allowed users to interact with internal content (lists and SharePoint repositories), as well as external content. This included other LOB enterprise systems (such as SAP, Siebel, etc). There was no native way to connect SharePoint and Documentum though.

Wingspan

A company called Wingspan had also developed technology that provided Web Services connectivity to Documentum.  This consists of the Docway Server, and Docway “Portlets”, (and for SharePoint – Webparts), and allowed for single sign-on,  cross-docbase browsing, as well as the ability for users to access, create & update content from a Portal.

SPX

CSC’s FirstDoc, provides a layer that sits on top of Documentum, and allows for compliance with many of the Pharmaceutical regulatory requirements imposed by the various regulatory authorities (FDA, EMA,  MHRA, etc.)

Using Wingspans technology, CSC (or, at the time, FCG), were able to create special webparts that allowed users to interact with their FirstDoc system from a SharePoint Portal. These offered about 85% percent of the functionality provided by the native FirstDoc application.

4.3

The first version was released in the 2nd half of 2007, and had the moniker “version 4.3“. This was to keep the version inline with the (then current) version of FirstDoc. It was compatiable with version 5.3 of Documentum.

There were 17 webparts available. These included webparts for browsing cabinets, listing the logged-on users checked-out documents, displaying the Home Cabinet, an inbox webpart, an very handy object-view webpart that could be configured to display one particular folder, or cabinet), an also handy query-view webpart that allowed content to be displayed based on a query, as well as an assortment of other functional webparts, and administration webparts.

Each web part offered a user the ability to further interact with an object via a context menu that showed extra functionality depending on the type of object that was clicked upon.

Courtesy of CSC

This first version was an excellent step towards greater flexibility in creating interfaces for users that better matched their daily work style. For the 80% of users who rarely log into FirstDoc, it provided a quick and easy way to get to specific documents. Links to specific documents could be sent via e-mail, and when a user clicked on it, the document would automatically be opened, without having to go through a process of logging into a client and searching for a document.

But there were also several shortcomings. There was the 20% of hard-core users that quickly discovered that there was still a lot of functionality that was not available. Also the SPX interface did not offer the same flexibility that WebTop did. You couldn’t easily change the columns that you wanted displayed, the search functionality when compared to the WebTop search was very limited, and the way of interacting with the documents was different. The context menu was not found in WebTop.  Performance was also a bit sluggish especially when using the webparts over a WAN.

To be fair, CSC were also restrained by the limitations of the underlying Docway technology.
(However, Wingspan have been making continual improvements to their technology and CSC have been able to take advantage of this).

5.0

CSC listened to the concerns that the hard core users (as well as the administrators) were having. Version 5.0 of SPX was released in the middle of 2008, with Product Alias Search functionality, the ability to limit search results, and also the ability to add multiple documents to a workflow. Version 5.0 was also compatible with Documentum 6.0

6.0

Then later that year, version 6.0 was released. This was based on Documentum 6.5, and an upgraded version of Docway(6.1). It had been designed to be backwards compatible (with configuration, it could work with version 4.3 of FirstDoc). This allowed SPX to work over multiple docbases of different versions. As well as this, the Inbox and Query webparts were tweaked so that values could be automatically passed on the URL. Menu selection was made configurable. A quicklink capability was added that allows a link to be configured that will launch FirstDoc functionality, and the ability to View Relationships, and Audit Trail reports was added.

6.1

Then, in the later part of 2009, version 6.1 was released with even more functionality – Virtual Documents could now be viewed, multiple files could be imported, a new :”My Views” webpart was available, as well as the ability to view the Workflow Status report. Importing related documents was now, also possible. A version 6.1.1. was also released but this was a correction to a limitation that was previously believed to be uncorrectable.

Courtesy of CSC

6.2

In 2010, version 6.2 and 6.2.1 were released. The only difference was that 6.2.1 was certified for use with SharePoint 2010. Both versions also used Docway 7.0.  And there was a bundle of new features and functionality. These included: the ability to register interest, the availability of the WebTop Search app as a webpart, a single-box search (“Google-like”), Saved Searches, the ability to display custom properties in the web parts, clipboard tools, subscription notifications, as well as other functionality.

Future

CSC are working on the next release of  SPX, and it looks like they’ll be adding even more functionality to close the gap between SPX and WebTop.

FirstDoc doesn’t have its own client application – it extends the functionality of the EMC Documentum native client – “WebTop”. EMC has announced that they will be phasing out this out sometime soon.  As a result CSC are dedicated to ensuring that SPX is ready to be a replacement.

So – that’s the end of my “A little bit of history” post. If have made mistakes anywhere, please feel free to let me know.

AIIM’s CMIS Product Guide!!!

AIIM CMIS

Wow – call me Happy and knock me to the ground.

AIIM have just released their standards based Product Guide focused on CMIS. Being an AIIM Professional Member I was quick to download a copy.

For those of you unfamiliar with CMIS (Content Management Interoperable Services), one of my earlier posts “Small Brain Notes on CMIS” explains it more in detail.

About 9 months ago I started writing a blog post that would give an overview on the CMIS market at that stage. A lot of Vendors had recognised the real benefit of CMIS and were all making plans to implement it one way, or another.

My post did have some promise. (Click here if you’d like to view it in it’s unfinished glory). However I was not happy with the incompleteness of it, and decided, at the stage not to publish it.

The AIIM document is not comprehensive (which AIIM states clearly in the Introduction). It covers 13 vendors, and describes the CMIS enabled product of each of them along with more detailed information on the use of the product as well as (where possible) the CMIS capability support of the product.

Products covered in AIIM’s Report:

  • Alfresco Web Quick Start
  • Alfresco Activiti
  • CMIS Export for Kodak Capture
  • Content View
  • Documentum Content Management Interoperable Service
  • Fresh Docs
  • IBM Connections 3.0.1
  • IBM Content Manager Enterprise Edition 8.4.3
  • IBM FileNet Content Manager 5.0
  • IBM Lotus Quickr 8.5
  •  Nuxeo Document Management
  • Open Text ECM Suite 1.0
  • SharePoint 2010
  • WeWebU Open Workdesk

The authors hope that later versions of the guide will contain more vendors.

In the start of the Guide there is a very good introduction, and an article by David Choy (chair, OASIS CMIS Technical Committee). David Choy has also recorded a brilliant video, awhile ago, in which he explains CMIS. This was a great tool when I was trying to understand what CMIS was all about. (You can view the video here.)

After the vendor review, there are a couple of articles by Laurance Hart (@piewords) and Stephan Waldhauser (@WeWebU).

Following the articles, there is an excellent list of CMIS Resources, which I am going to look through when I get some time.

Taking into account that (at AIIM’s own admission) the Guide is not comprehensive, it is still a very handy document to give a better understanding of the CMIS landscape.

My only criticism is: Guys – when you are creating a PDF – do it properly. Get each section properly bookmarked, as well as the TOC hyperlinked to the corresponding page. It’s not hard to do; it makes the Guide a lot more usable (when viewing on screen).

Click on CMIS in the tag cloud for my other CMIS posts.

CMIS is here … but where?

Note – this post is in a draft format. It was written in June 2010 and was never published. The information in this post is not complete.
I have released it now as part of my AIIM CMIS Product Guide post.

CMIS 1.0 was ratified in the beginning of May 2010. This is the standard that will allow interoperability between the various content management systems that are currently on the market. For more information on CMIS, refer my Small Brain Notes on CMIS. Go and read it now, and when you are finished, click on the back button. I’ll be waiting…

Ok – now that you understand a bit of what CMIS will offer, let’s ask the question – when will it be available in these disparate content electronic content management systems?

Let’s look at the list of companies that were associated with the creation on CMIS 1.0

And…who is ready for CMIS?

Founders

These three  were there in the beginning, and developed the initial draft.

Reviewers

The following companies also played a part in the moulding and shaping of the CMIS standard:

  • Alfresco – Version 3.3 (available now)
  • Open Text,
  • Oracle,
  • SAP

Others Adapting their systems to be CMIS compliant:

  • ASG Software Solutions
  • Content Technologies ApS
  • Day Software
  • Ektron
  • ESoCE-NET
  • Exalead, Inc.
  • FatWire
  • Flatiron Solutions Corporation
  • Greenbytes GmbH
  • Harris Corporation
  • Nuxeo
  • Saperion AG
  • Sun Microsystems
  • Vignette Corporatio

Here is a list of the vendors with regards CMIS compliance.

Vendor Product CMIS Support Timeline
Alfresco Alfresco 3.2 Available for testing
EMC Documentum First half of 2010
IBM Content Manager Second First half of 2010
IBM FileNet P8 Second First half of 2010
KnowledgeTree KnowledgeTree 3.7 Available for testing
Microsoft SharePoint Server 2010 First half of 2010
Nuxeo Nuxeo DMS 5.3 Available for testing
Open Text Enterprise Library Services (ELS-Beta) CMIS connector available now
Open Text Open Text ECM 10 Mid 2010
Oracle Oracle Universal Content Management Not known
SAP SAP DMS Not known
Sense/Net Sense/Net 6.0 Available for testing

FirstDoc User Group 2011 – a look back at the conference – Part 4

Previous post: FirstDoc User Group 2011 – a look back at the conference – Part 3

EMC FirstDoc User Group FDUG

In Part 3 of the FDUG 2011 series, I described the afternoon session of the first day, which included CSC’s Cloud offering, their UI Strategy, Performance and the social event. In this post, I’ll cover the sessions that took place on the last day.

Feedback

The morning started with feedback. The points compiled from yesterday User session were presented to CSC. These were graciously received, and even a few suggestions where made by CSC staff about ways they, themselves,  could address the concern.

SPX in use

Following the user session, there was a panel discussion involving three of CSC’s clients that had implemented SPX in their environment. For more on SPX, click here (PDF).

It seems that while there was a lot of interest in the technology, and implementing it, this came from a very small group of people. This group, however, were very interested in a number of things, and many questions were still being asked after the session had ended.

eTMF

After the coffee break, another CSC customer gave a presentation on their journey from a manual system for managing their Trial Master Files (TMF) to an electronic system.

This was packed with some very interesting information, and it is always good to learn from others.

Total Clinical Solution

As discussed in earlier “Look back” posts, CSC are offering “Total Solutions”. The “Total Regulatory Solution” has been  discussed, and now we had a chance to learn more about the “Total Clinical Solution”. Fransiska Darma (who I had met the night before) gave this presentation.

Often, in clinical trials, the research is outsourced to a Clinical Research Organisation CRO), and involves collaboration between the CRO and the pharma company. In other word – moving documents between the external CRO, and the internal groups involved.

To achieve this requires being able to capture document, and somehow allow the external party to upload it to the pharma company’s EDMS. Further to this, to allow for an increase in reporting and tracking, documents need to have an expansive amount of metadata.

As with CSC’s Total Regulatory Solution, CSC are trying to leverage the fact that they now have a full range of products to implement these “Total” solutions. For their “Total Clinical Solution” this includes making use of FirstDoc (on Documentum), along with SPX (on SharePoint), as well as other tools that facilitate planning and managing, tracking and reporting, and the auditing process.

Usability

This was another customer presented session. It was very, very interesting. In this case, the customer had done an Usability Assessment of FirstDoc 6.1.

The presenter started off asking why, when we search for, review & order something on a site like Amazon, we can do it easily, without any real effort, while, when do something similar inside a business, a 3 hour training course is required.

The presenter followed this up with the statement that “solutions should not require user to change their way of working for the sake of the system.”

To assess their own system (based on FirstDoc 6.1) the customer did 2 assessments, each time where 28  normal employees (i.e. not specially trained testers), were asked to perform a specific task – review & approve a document.

Using a tool that allowed the user’s mouse movements to be tracked, along with a camera that allowed the user’s face to be seen, gave the testers a good insight into how a new user uses an interface.

Some of the findings were shared with us.

These include the fact that the steps required to accomplish the actual task were not obvious. We were shown a film of the mouse movements of one of the testers as they tried to work out the steps required to complete the task. At the same time, a small screen showed the user face and body. There was  a lot of “i know that feeling” laughter amongst the audience as we watched.

This particular customer had also created a mock-up of an improved design. This included less “clutter” and prompts that would guide the user.

On the one hand, having guidance can be very useful for users who are not familiar with the steps required for the task. And often, even after doing the task for a couple of times, if the same user did not repeat the actions for several months, then that same “learning time” is required. On the other hand, users who perform the task multiple times a day can get frustrated with guidance. In this case, what would be good is if the application had a “dummy mode” for new, or infrequent users, and an “expert mode” for those more “experienced” users. (This was something that was introduced into WebTop – a “simple” user interface, and a more detailed one.)

EMC & Record Management

Tim Marsh from EMC gave us a presentation on Records Management, and Information Governance, and the solutions and tools that EMC has in the area.

Validation

The last session of the day was presented by Peter Branstetter, a Senior Consultant from Arcondis.

Peter’s presentation was a very educational trip through validation. Starting with GAMP5 (Good Automated Manufacturing Process) he touched upon Risk-based approach,  and the GAMP V model. Included in the journey we got to see example of this in use.

CSC offer a Validation Package which contains all the components needed to meet compliance. This allows the customer to fill in the details as required.

This session generated some very interesting discussions. It seems that “what”, or “how much” is required to meet compliance can vary depending on who is making the company policy. As such, the answers to some of the “do I need to do x,y, or z” questions were often – “that depends on what your QA department wants.”

This was the last session of the conference – about a quarter of the participants had already left. However, this topic, whether we love it, or curse it, was something that a lot of people wanted to know about, and Peter definitely seemed knowledgeable about it.

End of Session

So – that was the end of the FirstDoc User Group – Europe Conference. For me, this was one of the best FDUG conference that I have been too. I got a lot of value out of the sessions.

The FirstDoc User Group conference is organised by the FDUG – Europe Steering Committee This is made up of 3 representative from CSC Life Sciences customer base.

They did a really good job this year!