The conference schedule for our Fall Content Management Technologies event, November 28-30 at the Westin Copley in Boston, is available at: . Topics to be covered in-depth include:
* Web Content Management (WCM)
* Enterprise Content Management (ECM)
* Collaboration, Enterprise Wikis & Blogs
* Enterprise Search & Search-based Applications
* Enterprise Digital Rights Management (eDRM)
* Automated Publishing
* Enterprise User Case Studies
Conference track descriptions are available at:
Speakers and complete session descriptions coming soon.
Year: 2006 (Page 10 of 43)
Update 7/24: Let the talks begin… With the review of the Symphony bid now officially postponed, the door widens for what could be an interesting bidding war in the ECM market. Asking for at least 10 cents more per share than OpenText has offered, Hummingbird has rescheduled the Symphony bid review for August 18th while negotiations take place. Considering both suitors are shareholders, (OpenText’s 22.3% versus Symphony’s 18%) it is unlikely that either will back out without some amount of drama.
Update 7/13: According to a press release, the Hummingbird Board of Directors will not issue a recommendation on the OpenText bid before July 25. Until that time, it is advising Hummingbird shareholders to “take no action,” and support the Symphony acquisition. Interestingly, the review of the Symphony deal will take place July 21. We’ll keep you posted.
Clearly the door was open. Altough I called myself “stunned” that the bid for Hummingbird was not a technology to technology play, I remain so given that OpenText was not the player I thought “most likely to acquire.” In fact, it was no secret that OpenText was one of the players “most likely to be acquired!” I’m thinking the final yearbook for the class of 2006 may have more surprises.
The OpenText bid is a “lock-up” agreement, which according to Information World Review, means that Hummingbird shareholders agree to a deposit from OpenText and not to withdraw from the deal. (Subject to timing and regulatory compliance issues.)
Aside from the many debates to be had on the consolidation effect of this deal, Hummingbird shareholders and financial analysts must certainly be gratified at the 20% increase in the OpenText versus Symphony bids. More at Image and Data Manager Online, CMS Watch, and Bloomberg.
Whether this deal happens is still up for grabs. OpenText’s bid is due by the end of the week. We’ll keep you posted.
I could have sworn they already announced this, but in any case it was inevitable. The whole controversy is now simply not all that interesting. IT organizations need to understand the translation issues, but choosing one format over another is just not that big a deal. Many organizations have more complex issues to deal with, like integrating XML content from custom applications or other enterprise apps that don’t map to either ODF or Open XML directly. We have lots more background on this.
As a former glue person, I spent numerous hours trading acronyms and definitions with IT analysts on the subject of data and process modeling in the content versus data worlds. Circa 1999, my friend Bob Boeri and I even went so far as to relate logical data models and data dictionaries to DTD structures, using Near and Far Designer as analogous to the more entrenched data modeling tools.
Our goal was to create “common ground” between IT’s deep but solely data-centric view of business applications and the needs of various business units whose focus was decidedly document-centric. Once our “data is content and content is data” analogy was mantra, we had an easier time with subsequent process modeling discussions; i.e. “what we want our content to do with your data” and vica versa. (Reminiscent of those “how did your chocolate get into my peanut butter commercials”)
In the ECM and BPM intersection, those discussions are once again becoming commonplace as more and more complex business processes require hybrid combinations of unstructured content, structured XML content and traditional data from back-end systems. Hence, information analysts that work with IT and business units must define a common knowledge base of process modeling requirements, flows, and techniques.
More than simple workflow (a.k.a “create, edit, approve, publish”), process models for functions such as compliance, claims processing, and contract management need to combine data-centric techniques with the content-centric, human-driven interactions these functions require. In fact, just as data sources are now hybrids, so too are the processes that require, manipulate, and share them. The BPM suite market is increasingly adding simple document management functionality at the business monitoring level to account for content-centric requirements.
More interesting is the market’s approach to workflow, which still appears either data-centric or document/content-centric in terms of standards modeling languages. In fact, a BPM suite vendor’s architecture choice for process modeling and execution is also a clue to their data versus content strengths via support for XPDL (XML Process Definition Language) versus BPEL (Business Process Execution Language). Highlights:
- XPDL – initiated and managed by the Workflow Management Coalition (WfMC), XPDL is decidedly human workflow-centric and more oriented for document-driven processes. No surprise that workflow, document management pure-plays, and some ECM players with BPM modules have strong XPDL modeling and processing engines. More info at
- BPEL – originally submitted to OASIS from IBM, Microsoft and BEA, BPEL is decidedly data-centric and more oriented for straight-through processing. No surprise that platform and middleware vendors entering the BPM suite market have strong BPEL modeling and processing engines. More info at BPELSource and
- OASIS One of the more significant questions at the ECM and BPM intersection is, “Where is the best of both worlds in terms of process modeling for complex workflow that is a human and data-driven hybrid?”
Forrester has published one of their “Wave Evaluations” on blogging platforms. Charlene Li has a summary of the report along with the associated Wave graphic on her blog. The full report is available for sale at Forrester. Note that this report does not cover Wikis, although some of the platforms covered also have Wiki functionality. As we have suggested before, in the enterprise space, the line between blog and wiki platforms blurs in many cases. This is of course truer for collaboration and intranet-oriented deployments than for outward facing, e.g., PR-oriented communication.
As Tim Bray says “Wow”. Here is the announcement post with a huge number of comments. This is discouraging. As I have argued before, we need the kinds of capabilities WinFS was striving for to make the next leap in managing information. I remain skeptical that database platforms are a sufficient solution for effective object management – they may be the necessary next step, but they are certainly not the ultimate answer.
There are no doubt many easier, shorter-term ways to get return on software development than a radically different operating system, but hopefully at some point there will be sufficient recognition by all the software infrastructure vendors that working together to build a modern OS would be worth it. On the other hand, perhaps what has happened to WinFS is really a sign that the days of huge operating systems are numbered. The problems are really bigger than any one platform. What kind of cross-platform infrastructure is feasible to accomplish the fluid, granular and meaningful interchange of content and behavior we know we need? This is a more interesting question than whether WinFS itself is dead.
UPDATE: There is a lot of commentary out there, but as usual Jon Udell has a view worth reading.
Nora Barnes has released the results of research into blogging from the Center for Marketing Research at UMass Dartmouth, where she is the Director and a Professor. This is a welcome addition to the sparse collection of research that has been conducted to date. The published report is free and is available (as a 1.3mb PDF) here, or from the Center, where there is also a link to a podcast of an interview with Nora, and links to comments from others on the study.
We’ve been monitoring acitivity in the BPM market with an eye on the connections between ECM and BPM technologies as they apply to content-centric business processes and applications. The evolution of BPM suites has been particularly interesting and in many ways, analogous to the patterns that formed the current ECM suite market. Technology convergence, vendor consolidation, a full slate of interchangeable acronyms, and rising levels of market confusion surrounding the definitive list of suite-level components are all evident as the BPM suite market continues to define itself. Sound familiar?
BPM suites are clearly an emerging market. Broadly defined as the ability to model, execute, simulate, and optimize business processes, the market consolidates technologies such as analytical modeling, rules design and execution, workflow, data aggregation, and process optimization into a single platform vision. Numerous pure-play BPM providers within each technology segment are evolving toward “the vision” in different ways.
I am positive that this is not a “never the twain shall meet” situation when it comes to content strategies and ECM technologies. Process and content are siblings; it is only a matter of time before many of the isolated technologies that support both will merge in a more tangible manner than simple workflow. This kind of ECM and BPM intersection is more complex than the traditional integration of the BPM market’s straight-through processing (STP) expertise with data-centric, transactional content. Rather, it will be an emerging focus on what we view as process content, or content that travels through a complex, human-driven, interactive, and iterative lifecycle.
EMC’s acquisition of ProActivity is a tangible indicator of this evolving intersection, demonstrated as well by BEA’s acquisition of Fuego, FileNet’s ongoing investment in its BPM components, the progression of DM/BPM players such as Global 360 and Hyland Software, and Lombardi Software’s integration with Microsoft Office. Stay tuned for more as the market heads toward cohesive vertical and horizontal solutions — critical for both traction and helping the user community understand implementation value. We’ll keep you posted.
