Bookmark and Share

Thursday, 17 September 2009

Mashup solution patterns

Enterprise mashups transform the way organisations combine IT applications to make people and processes more effective. However, in common with most new ideas, if they remain an abstract concept, or if people form preconceptions based on isolated examples (such as the ubiquitous map based mashup), then those who stand to benefit most may find it hard to get a feel for their power or relevance. In my experience, the missing link is a set of examples or usage patterns that make these possibilities concrete.

Gartner have taken a step in this direction by setting out “Five Mashup Application Types”:
  1. Personal dashboards – allowing individual users to choose the gadgets they need
  2. Packaged application extension – providing a flexible alternative to application customisation
  3. Location awareness – allowing spatial distribution of data and assets to be visualized and explored
  4. Panoramic awareness – bringing together a single view of an “object” of interest from different sources (such as a customer, competitor or place).
  5. Situational awareness – allowing events and data relevant to a “situation”, to be tracked and responded to.
While these are helpful (and Corizon supports all these categories, most frequently being used in categories 2 and 4) – they don’t go far enough to bring real-life use cases to life. Likewise, the patterns recently set out by Michale Ogrinz offer a great set of possibilities – but almost too many and slanted towards the developer.

Specific examples of how the mashup can be deployed to increase user productivity in the context of known integration and development challenges are required to bring the potential of mashups to life for both the line of business and IT.

As a result we have developed some key deployment patterns that we see again and again. We find that these (1) really help to explain how enterprise mashups deliver fast payback in familiar situations and (2) get over what you can do with a mashup platform that creates streamlined process based applications (vs one that is focused on combining data and creating dashboards and would not be suitable for these patterns).

Here are some examples – let us know what you think and what else can be added:

New web application: Rapidly build and easily change “standalone mashup” that combines enterprise applications and services to deliver new streamlined, process-based application

"Integration without customization" Embed mashups to extend packaged enterprise applications – on premise or SAAS – with new, integrated user activities. Avoids delays, overhead and upgrade problems of customisation.

Extend legacy application UI. Rapid, reusable alternative to trying to change unsupported or end of life applications to support integrated user activities.

Extending interaction management and CTI applications Create interaction based desktops for call centre agents that streamline and simplify customer service processes.

Self service expansion. Expand scope of self service portals for employees, customers and partners with integrated, process-based applications.

Support interactive activities in BPMS solutions: Add streamlined, integrated UI to support and simplify human steps in long running business processes.

Labels: , , , , ,


Thursday, 11 June 2009

Are mashups lipstick on a pig?

One of the debates currently going on is regarding the lifespan and role of mashups (cpettey/Gartner). Are mashups just tactical, throw away applications for short lived micro-requirements that come and go in the business (aka situational requirements) with the associated business case challenges? Are they just good to temporarily paper over a gap while your systems catch up with user requirements? In other words, are enterprise mashups short lived either for the simplest of “applications” or simply as lipstick on a pig as suggested to me recently by the CIO of a very large telco?

One of the great values of enterprise mashups is that they can deliver in very quick time frames by leveraging exiting systems and applications to streamline processes for people. This can be to address a “situational requirement” such as a dashboard, combining RSS feeds for data reporting etc. They can also help mop up legacy applications before retirement i.e. provide lipstick on your old architecture while you deliver the new one. They can prepare for the deployment of packaged application such as CRM or ERP. This provides the value of quickly testing in real time, with real users the required “user process” (i.e. the set of steps a user need to go through to complete a task). This can even be implemented in the look and feel of the enterprise application. Users will then not be disrupted by the deployment of the enterprise app while deployment will be speeded up by “learning” from the tested user process implemented in the mashup. Once the enterprise application catches up, then the mashup can evolve to do less, be retired itself or remain to provide the flexible, process driven UI that would continuously require updating. This will depend on architectural decision.

It is in the flexible delivery of process driven UI that enterprise mashup become a key part of modern architectures and are destined to power solutions that will remain in use for a long time. Why? Because modern architectures need lipstick as much as the old ones! With WOA, SOA or any component based approach, user-centric applications are still required when a business process need surfacing to a user and those end up being built bespoke for each user group. This is because user interfaces are not service enabled, not turned into re-usable components. This is where enterprise mashups play a key part: with the creation of visual, mashable components that can easily and quickly be mashed up into user centric solutions, they provide a “face” to web services and deliver the flexibility and process adaptation required at the user level to deliver flexible architectures from top to bottom.

The answer to the lifespan and role is that enterprise mashups provide real value when they address real process pain point, have a role to play in legacy and modern architectures and can endure for considerable periods of time while the content and function continually evolve.

What do you think? Do you see the same trends?

Labels: , , , , ,


Friday, 15 May 2009

Integration without customization for Oracle E-Business Suite

I repeatedly hear from our customers about the challenges they face in creating integrated user experiences around their investments in CRM and ERP applications.  They find themselves constrained by long release cycles, full workstacks and the expense and scarcity of skilled resources.  As a result, users have to carry on “swiveling” between applications on the desktop – bad news for the reputation of the applications and for efficiency, accuracy and costs.

Fixing this problem is a great use case for enterprise mashups, replacing complex customization projects with the much more lightweight and portable mashup process.  We call it “integration without customization”.  A while ago we announced a toolkit to be able to easily embed our mashups in the user workflow of Siebel applications; this week we have followed this up with our “extension pack” for Oracle E-Business Suite.  The pack overcomes the challenge of embedding web UI in the EBS forms UI.  By providing everything an EBS developer would need to be able to get a mashup deployed and launched within the EBS application, it cuts a task that could take many days into hours.   As a result EBS owners can extend and integrate user desktops with minimal cost and effort.

We believe integration without customisation is a killer “mashup pattern”, especially in a economy where the focus is on getting more from existing investments like major enterprise applications.  Through the rest of 2009 we will be working with our customers and partners to understand where else pre-built capabilities of this sort can smooth the process, so let us know where you see the clearest need.

Labels: , , , , , , ,


Monday, 1 December 2008

There’s enough complexity already: The need for integration without customization

You hear a lot about how long and complicated Siebel deployments can be, but often this is just mud-slinging by rival vendors. Siebel is a great software solution – if it wasn’t, hundreds of thousands of users wouldn’t be relying on it today.  

Siebel implementations *can* get bogged down, though, when organizations want to build in additional custom functionality or integrate other enterprise applications with it. These bespoke integration projects can create long delays in the Siebel rollout process – especially if the new functionality is found to have a lot of bugs that need fixing.

If this sounds like your experience, Corizon has good news. Our new Corizon for Siebel solution greatly reduces the cost and time needed to integrate applications into Siebel. Essentially, it lets you ‘mash up’ the applications you want to incorporate into Siebel into one composite application, which you can then test and modify (and re-use) independently of the Siebel environment. Once you’re happy with it, you can incorporate the composite application directly and seamlessly into the Siebel desktop. 

It’s an approach that’s serving Siebel users very well. BT’s Broadband Helpdesk Change Manager, Roger Buck, told us that Corizon has significantly eased the process of incorporating additional functionality into Siebel. “Our investment in Corizon’s software has delivered full ROI in less than 12 months – remarkable when looking at enterprise software on this scale,” he said.

At Corizon we’re all about making life easier: easier customisations, easier access to vital customer data; and easier deployments of business-critical CRM systems.  By removing complexity, we reduce our customers’ costs and increase the speed, flexibility and power of their CRM software. That’s not just business sense – it’s common sense.

Labels: , , ,