Bookmark and Share

Monday, 21 December 2009

Corizon introduction video

We've created a new video that provides an introduction to Corizon enterprise mashups and their use.

Please check it out and let us know what you think.






Labels: , , , , ,


Friday, 4 December 2009

Allowing for the human element

When people must work with business applications and processes, it seems there is continual need to strike a balance between completely rigid process definition (when people become pure input / output devices) and completely ad hoc behaviour (no repeatability, management etc.).

This is one of the themes being taken up in the BPM world at the moment. For example as Jim Sinur recently pointed out:
Today BPM is really into preplanned and rigid process models. While the underlying technologies are agile and explicit rules and processes are being leveraged, process models need to move from fixed to variable behavior. This will probably start with collaboration points in a mostly fixed process, work to loosely bound process snippets to dynamically created and executed flows that are bound by governance constraints. These kind of processes allow for BPM to extend its benefits to a larger group of work activity that is not so predictable. This will likely include collaboration across organizations and into value chains that touch different legal entities.
There is an interesting link to be made to some of the thinking published about how to improve quality and profitability in environments that rely on people interactions –such as customer service. For example Human Sigma looks at the effects of variability in the effectiveness of human customer-interactions

Human Sigma contends that as an organization tries to standardize processes and scripts for management teams to follow, scripting employee behavior does not really enhance the quality of the employee-customer interaction. In fact, it may worsen it by emphasizing the steps to do the job instead of the outcome the process is supposed to produce. [Six] Sigma followers look at the manufacturing world and conclude companies can improve processes and systems because the inputs they use to make things can be kept at predictable and repeatable levels. But human systems in business – such as the employee-customer encounter – do not conform to such predictable rules. Sales and service organizations in particular, with a high degree of direct employee-customer interaction, cannot expect to follow such conforming practices as those in the manufacturing world.
When we think about providing software solutions to support agent-customer interactions, there are therefore a number of important conclusions
  • We need to balance providing “enough” guidance to simplify and safeguard what a user such as an agent is doing, while leaving sufficient freedom for the user to be able to focus on the end goal- solving the customer’s issue - not the steps mandated.
  • The engagement level of the agent with the business has been shown to be key to quality and has a significant effect on the profitability of interactions. The desktop environment provides a very tangible example of how much the organization “cares” about its employees (or doesn’t).
  • Measurement and monitoring are key to understanding and improving the quality of interactions. The more we can do to understand the hard and soft aspects of customer service, the better chance we have of improving service and performance.
In fact this could almost be a manifesto for using enterprise mashups in the contact centre- building high quality desktops with the involvement of the business, guiding activities while providing freedom to act, providing the means to continually adjust!

Labels: , , , , ,


Thursday, 12 November 2009

Comment on "Enterprise Mashups in Transition"

Anthony Bradley from Gartner provided some interesting views on how he sees the enterprise mashup market developing this week in his blog posting: Enterprise Mashups in Major Transition.

The transition he has identified is chiefly concerned with a shift in the use cases he is seeing that drive demand. As Anthony says:

Just about everyone, including me was talking about enterprise mashups as a new paradigm for end user computing where business users would rapidly assemble and reassemble applications in a highly dynamic fashion.

And then…

… a shift in the need began. Instead of asking about end user empowerment, clients began inquiring about how to reduce integration costs with mashups. Some organizations were trying to use mashups to clear out their application integration backlog more quickly and at less cost. Others were facing new integration challenges due to mostly unexpected mergers and acquisitions.


This accords with what many of Corizon’s customers and partners are looking to enterprise mashups to provide in the first instance. I would add that this shift does not move the interest in enterprise mashups purely to the IT domain. Fixing integration problems does not only concern IT but also business unit leaders in that they have the potential to greatly impact the efficiency of their teams. In today’s environment, many businesses are looking for way to deliver a step up in people productivity with short and low risks projects: enterprise mashups are perfectly suited to that.

Finally, this type of pragmatic integrations will naturally create a pool of reusable mashable components if done with the right technology. Once created (and paid for) thanks to these projects, these components will make it easier for end users to create their own mashups in a safe way, with the buy in from IT. So the nirvana of end user empowerment is perhaps not as distant as Anthony fears!

Labels: , , , , ,


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: , , , , ,


Wednesday, 1 July 2009

Gartner SOA summit – pragmatism and innovation

I spent a great couple of days last week at the Gartner SOA and Application Development and Integration Summit in London, emerging encouraged by the combination of pragmatism and innovation that I heard discussed.

Inevitably, much discussion centred on the economy and its implications. While technology –as Massimo Pezzini pointed out - might be seen as having helped the problem happen by “providing the infrastructure to enable the financial services sector to get into trouble faster than anyone expected”, I didn’t hear much discussion about what could (or should) be done to prevent that happening again! On the other hand there was lots of debate on how IT can help companies survive and reinvent themselves for the future. The (not surprising) prescription was to focus on strict cost control and alignment of IT projects with clear business cases, while keeping sufficient investment to foster innovation in key areas. In the short term for example, organizations need to use their resources to rapidly adapt sales and marketing patterns in response to changed customer behaviours. Longer term, much discussion centred on anticipated structural changes to industries (especially financial services) requiring better support for complex inter-company relationships and networks.

SOA adoption
The message I took on SOA – from both Paolo Malinverno’s opening keynote and much that followed - is that it has clearly taken root, especially in Europe and N. America. However there also seems no doubt that the recession is having a Darwinian effect, culling the projects without well-defined short term business benefits. Long term strategic business cases for SOA programmes are “out”, pragmatism in the form of prioritizing rapid payback from fixing business problems is “in”. As a result, lots of initiatives that have started bottom up with no focus on business problems (service enablement rather than SOA) risk being cut – one figure floated (and hotly disputed) was that this could kill up to 80% of the projects started thus far!

Enterprise mashups?
Given this background, where are enterprise mashups? Well there was certainly plenty of interest, with David Gootzit from Gartner talking about their having a key role to play as the “face of SOA” and becoming an important way to build composite applications. However, listening to talks and speaking with attendees confirmed to me that while a lot of vendors and users have focused on using enterprise mahups to build simple “dashboard” type single page applications, there is a huge need and interest in using them to address the new integration agenda of business focused pragmatism and innovation. The idea of using the mashup approach to rapidly build process based applications for different user groups and tasks, leveraging a wide range of enterprise IT assets is – to judge from the response we had – just the capability that many organizations need. It seems that there are many cases where business process improvements and flexibility are needed but custom application development is seen as too slow, expensive and hard to maintain, and full blown WS-* and BPM are not appropriate.

Conclusion? SOA isn’t dead, just growing up in a rather more austere environment than the one it was borne into. And enterprise mashups can make a massive contribution, so long as they focus on really changing the economics of building and using business applications.

Labels: , , ,


Thursday, 4 June 2009

Enterprise Mashups and Cloud Applications

Corizon’s recent launch of mashup extension packs for Siebel and eBusiness suite has prompted a number of conversations with journalists on the extent to which this value proposition transferred to enterprises adopting SAAS applications. I was surprised by the initial perception that enterprise mashups were required because of the difficulty of deploying applications on premise. Conversely there seem to be preconceptions that the need would be much less with on demand applications.

Enterprise mashup adoption is driven by the need to transform the economics of integrating applications to make people more efficient. The deployment of new applications, whether they are on-premise or in the cloud,increases the requirements for integration. The more new SAAS business applications are adopted, the more such integration will be required. This is exactly the experience reported by GE CIO Gary Reiner: implementation costs for applications:
“...they're largely around interfacing with existing systems, process changes and data cleansing, those three costs exist regardless of whether GE hosts that application or whether the supplier hosts that application.”
As a matter of fact, cloud computing is even more adapted to enterprise mashups. The key reason for this is that they promote the concept of keeping each functional application as vanilla as possible to reduce costs. Why re-invent a CRM package and not just adopt best industry practice? Differentiation is not gained by modifying each application but by integrating them to streamline your desired processes. For example superior end to end customer experience delivery is more likely to be achieved by seamlessly integrating the different applications required to support a particular customer journey (trouble ticketing, service diagnostics etc.) rather than customizing each application. This is where enterprise mashups play a critical role: by providing a quick and non intrusive way to create mashable components from existing applications and easily combining them to mashup a fit for purpose solutions that guide users to complete a task, they are perfectly suited to integrate your cloud with your on premise applications.

We are big proponent of service based applications at Corizon – this is where the company started! We also happen to believe they will be one of the key drivers to accelerate adoption of enterprise mashups. As enterprises adopt SAAS, they will be looking for new approaches to quickly, flexibly and cost effectively integrate their new cloud applications to allow people to do their jobs better. In the same way that enterprise mashups transform the economics of owning on premise enterprise applications, they will transform the economics of integrating cloud applications.

Labels: , , , , , , , ,


Tuesday, 5 May 2009

Contact centres are ripe for enterprise mashups

Spending time recently in a contact centre reminded me of a quip I heard from Lord Saatchi. He was talking to a senior director of a well know consumer brand and saying: “do you know the old saying about half of your marketing budget does not deliver but the issue is which half? Well for your company, I have worked it out: neither!”

So which half of your IT budget works in the call centre? Neither. You just have to look at how many applications call centre agents have to deal with during a call! Research shows on average 6 but in our experience the number is usually much higher. This is despite years of investment in technology in call centres. The reason for the failure? Each time a new requirement for the agent emerged, a new application would be built or an existing one would be modified. This lead to a proliferation of applications on the desktop, making the job of maintaining them (and integrating them) harder and harder for IT. No wonder release cycle of enterprise applications on the desktop can now be measure in months or years! This results in inefficient processes with dramatic economic consequences: high cost to serve customers while delivering, in a majority of cases, a poor customer experience. No wonder so many companies decided to give up on call centres and outsourced them despite the fact they are one of the most important (and inescapable) windows to customers.

This is why call centre is such a ripe environment for the deployment of enterprise mashups. By changing the economics of building and maintaining integrated solutions to call centre agents, they address the application proliferation issue, reduce dramatically the cost to serve customers by making agents more efficient and deliver clearly measurable ROI in short time frames. This is where we think the real value of enterprise mashup can be realized: in delivering real composite applications to address immediate business needs but in a way that is repeatable and complements modern architectures. A theme I will come back to regularly in this blog.

Labels: , , , ,


Friday, 13 March 2009

Enterprise Mashup as a Capability

Why do we need Enterprise Mashups as a capability of IT? As Dion Hinchcliffe explains in this post, there is a lot unmet software demand due to small projects not being economically viable:
... almost any IT system is going cost in the hundreds of thousands or low millions even to get off the ground. This means that many smaller, niche demands, which statistically, are very likely to be larger than the demand for big IT systems in an organization (The Long Tail), are actually continuing to go dramatically underserved ...
As he further explains, Enterprise Mashups are in a perfect position to enable the business to fulfill this demand. What is not talked about, are the different deployment options of these mashups. Depending on the context of the functionality it delivers and the type of user it delivers it to, the deployment pattern of the mashup should change. For an "ad-hoc" pattern, you might want to deploy the mashup as a gadget on the desktop. For a "project" pattern you will want to deploy it inside a project portal, while for a "process" pattern you will want the mashup to be deployed as an extension to an Enterprise Application.

Choosing the wrong deployment pattern of a Enterprise Mashup could restrict its benefit and in some case dramatically increase the number of applications on the desktop. Especially when deploying an "ad-hoc" pattern where a "process" pattern would have been more appropriate, the user will suddenly need to become aware of what mashup are relevant to which task and where to find it. He or she will have to copy data to and from an Enterprise Application and mashups. The ultimate swivel chair nightmare!

So what does it mean to extend Enterprise Applications with mashup capabilities? It means facilitating the embedding of mashups inside these applications so that the business is able to add functionality to them for their specific "long tail" needs, e.g. extending a CRM application with a Network Diagnostics Mashup for the customer's region to enable the agent to anticipate and analyse possible causes of connectivity problems. By providing this capability the short lived, specific requirements of a business division can become part of the same application that is serving the long term requirements of an entire enterprise. But this time, it can deliver this to a specific user groups and for a specific process only, without requiring changes to the underlying application. This is what we at Corizon call "Integration without Customisation".

Labels: , , , ,


Wednesday, 25 February 2009

Data vs Process Mashups

In a recent blog Deepakalur from JackBe proposes a new tier for Enterprise Mashup. In this architecture an additional logical layer is introduced, the mashup layer, which sits between the business and presentation logic: Assuming that the presentation logic includes the application logic, this architecture makes sense for the types of mashup he is discussing, i.e. data mashup. It isn't however applicable to all types of mashups.

Ron Schmelzer from ZapThink hilightes the difference between data mashups and process mashups as the different answers to the requirement for different levels of situationality and levels repeatabilty, with process mashups deemed more appropriate for repeatable processes that require some level of situationality. At its core, process mashup are about introducing a level of agility into the process of stringing together services into an application, or SOBAs as Ron calls them:
Situationality, therefore, is not always a priority with mashups, as situationality is less important than repeatability for most automated processes. After all, the reason you'd want to automate a business process in the first place is because you expect to run the process many times, otherwise automation would never be cost-effective. Situationality and repeatability, however, are two ends of a spectrum; the interesting processes from our standpoint are the ones that fall in the middle somewhere. Such processes have a level of variability that requires a measure of situationality to the applications that implement them, while being sufficiently repeatable to warrant automation. It is such processes that process mashups (and SOA in general, for that matter) are particularly well suited for.

At Corizon we have introduced this approach to support agile development of user facing application. In this approach user requirements are met by stringing together UI Services into User Processes, as discussed here in detail. For this, a new architecture is required, one that is built to support easy rewiring of UI functions, without rebuilding the UI.

In this architecture the, different user groups can combine UI functions as they see fit, without having to create many variations of the same UI. This is critical for the succesful deployment of a process mashup.

Different types of mashups solve different problems and each of these require different architectures. So when you're embarking onto the Enterprise Mashup journey, make sure you pick the right tool for the right problem.

Labels: , ,