You are here: Home

EMC Momentum 2006 – SharePoint and Documentum working together, working better

Posted by unclaimed blog
No Comments »

To present about using SharePoint at EMC's flagship Documentum event is to really ruffle the feathers of the enterprise content management giant. I wasn't too sure of the reception that I would receive stood side by side with Microsoft's SharePoint product manager from the UK. As a customer of both Microsoft's and EMC's though it was plain to see that there was a lot of interest from partners, other customers and EMC themselves in what we had to say.

The crux of the presentation was about using Microsoft SharePoint to provide a more fitting interface into Documentum's content 'engine'. I acknowledge Documentum as a great content repository and the way that it manages the lifecycle of documents keeps EMC ahead in the ECM space (according to Gartner). But one thing that lets the product down and infact any product trying to manage the discipline that is content management is the way that users interact with it. Webtop, the main web-based UI into Documentum, has come on leaps and bounds over the last few years and I saw a presentation of what is to come in the D6 version. It continues to improve, but it's still 'separate' and distinct from where people do the vast majority of their information working with content – namely a corporate portal, the desktop and MS Office. To lift someone out of a corporate portal with the dashboard of information it provides into a different interface, different set of metaphors, different way of organising provides a barrier to adoption and usage. Having invested in a corporate portal, namely SharePoint in my case, and have it not provide a dashboard onto an information worker's worls is not reaping all the benefits. That said, SharePoint 2003 is no document mamagement system. The lack of item level security is enough to dismiss it in any serious document management practice. MOSS 2007 has improved and could meet the requirements of many organisations who need version control, check-in / check-out, security and simple retention policies. However, EMC are still ahead of the game and I still think they have a very strong product. Getting the two to work together, and not just screen-scraping Webtop into SharePoint, is an important task and supports a serious ECM effort.

So the majojrity of the presentation focused on the benefits of investing in technology and processes to provide a great compliance engine in Documentum, with the freeform collaborative and approachable platform that is SharePoint. The immediate benefits were around adoption. People just took to SharePoint faster. The important aspect is maintaining that adoption but still trying to weave in the discipline of document management – metadata, workflow, achiving, compliance. How can you leverage seamless integration into the creation toolset of Microsoft Office but still have documents that are treated as records from the outset. That is still the challenge, but products from companies such as Vorsite and Wingspan provide the key. Each have their merits, each have some drawbacks.

The presentation itself is avaialble at http://www.momentumlive.com/momentum2006/rome/home.aspx. You'll need to have attended the event to know the password.

There was a massive amount of interest in this topic so expect to see much more happening in this space. EMC themselves announced that in the D6 timeframe (sometime Q2 07) they will release their own SharePoint integrations to work with MOSS 2007. This shows that EMC are serious about working with Microsoft and MOSS rather than putting their head in the sand like they've done in the past. Dave DeWalt, head of EMC's software division and previously CEO of Documentum, mentioned in his keynote that a 'UI-less' approach from EMC was a key component of their strategy. To me this aligns with what Microsoft are doing with SAP with the Mendocino initiative and products such as Duet. Organisations acknowledge EMC and SAP as providing good 'engines' for content and business processes, but both of those companies provide shocking UI's. Adoption is weak at best and users can both make mistakes and waste time. Microsoft are currently not just kings of the desktop, but kings of the UI in the business arena. Microsoft Office is incredibly powerful in the way that users don't have to be trained to do basic operations. SharePoint and MOSS 2007 are similar in the portal world.

Lots of customers of EMC's came to talk to me offline after the presentation and feel them same way.

It began with Lotus Domino

Posted by unclaimed blog
No Comments »

Circa 1999 a small Intranet spawned in my organisation based on a single Lotus Notes database hosted on Domino. The team that supported the content and development of the Intranet were a small team of Lotus Notes developers. The Intranet was an IT project, somewhat of a pet project in the first instance. The business still primarily used Novell file shares to store documents and Lotus Notes for email.

The Intranet supported a number of small applications such as the Telephone Directory (also a Lotus Notes database) and various discussion forums and document libraries.

By the year 2000 the Intranet had started to gain some real traction as a communications tool providing daily news updates and information about the company. Still, it was a very simple system and required heavy IT involvement to make changes. Working together with the business, IT enhanced the Intranet to allow editing of certain content, delegating the responsibility to business people who were designated 'content managers'.

Shortly after this some fragmentation happened. One of the business units within the company decided to create their own Intranet. This was to be the 'intranet next generation' and was built from the ground up on the Microsoft platform of IIS and ASP3. This new Intranet was more attractive and was tailored to the purposes of the Sales business unit. It was, however, not part of the 'corporate' Intranet and did not contain the company information that was available on the Lotus Notes based Intranet.

As the Communications team strived to compete for the user populace and ensure that the corporate messages were available for all a new initiative was conceived to revamp the corporate Intranet. The new Intranet would be built from the ground up utilising the existing Lotus Domino infrastructure and supplementing it with ASP3 for certain applications. At this same time a shift began in the development teams behind the Intranet. The old guard of the Notes developers was on the decline and a new generation of ASP3 developers began on the ascendency. Most of the development team had been contractors and new ASP3 developers were brought in (contractors too) to bring fresh skills and begin the transition from Lotus Domino to a more IIS based web environment.

The new project which would deliver the first 'real' Intranet for the organisation had its own Project Manager and development team assembled. The new Intranet would be known as Origen.

A Portal, yeah a Portal… that sounds cool

Posted by unclaimed blog
No Comments »

“I want a Portal” the business says. “OK,” says IT, “What do you want it to do?” The business scratches its head for a moment. “Well, what can a Portal do?” the business asks.

It's a two fold process of analysts asking business people what they want and the business people responding by asking what they can have. Such is the classic chicken and egg scenario of requirements analysis. Technology occasionally drives opportunities for the business and then the business can make decisions about how to best use that technology supported by people from IS.

I make a keen distinction between IS and IT – systems and technology. In my experience what both camps often forget is that they have something in common and that's the 'I' in both IS and IT – Information. IT gets too bogged down in the technology and IS also tends to fall into that trap too. What they both need to remember is that it's the process that is vital. However the traditional "gather all of your requirements" and then go design and build something does not always work. The business, frankly, doesn't understand or like that method and in this day and age it's a little antiquated.

A large system implementation like a Portal needs partitioning and iteration. Neither IS nor the business really know what the end game is because there will be too many disruptive technologies and disruptive business practices along the way. Therefore thinking big but acting small is a very valid way of approaching Portal design. I particularly like Roger Session's article on Enterprise Architecture for this.

Portal implementations that I have been involved in have always fallen upon this method whether by design or not. `A picture paints a thousand words' goes the saying and this rings ever so true with getting the business to think about what it would like in its Portal. In fact even a whole Portal implementation provides a good basis on what the next version of the Portal should contain in terms of features, functionality, look and feel, performance and support.

So what has been my Portal journey then? Well it starts back in 1999.

Greetings and salutations

Posted by unclaimed blog
No Comments »

Hello. My plan with this blog is to provide some insight into how an organisation actually uses SharePoint rather than much technical debate and low-level code. I want to tell the story of my experiences with Portals and how organisations think about them.

By way of introduction I work as an Application Architect within a large multi-national company. My focus is on the U.K. and for one year now SharePoint Portal Server 2003 has provided us with a Portal.

The story of our Portal is a long a varied one. I'm probably one of the few people working in my organisation who remembers that far back. I'll relay the story of 'there to here' over the next few posts. Then I'll start on SharePoint in anger. :-)

Thanks and I hope you enjoy the tale.