Showing posts with label enterprise web 2.0. Show all posts
Showing posts with label enterprise web 2.0. Show all posts

Friday, February 1, 2008

Crisis 2.0: Menace or Turning Point?

There’s a crisis, you say? We are witnessing crises taking hold in many verticals including housing, financial services, manufacturing and others. There's the housing crisis. The bond crisis. The gas crisis. And these macro-crises are event beginning to put pressure on IT, where we're seeing something of a mini-crisis of confidence with IT pros pondering what might happen to IT projects like SOA.

Why is crisis good? Because it’s in the proverbial pressure-cooker that real innovation occurs. Darwin wrote it. Kanye West sang it. Most recently, Ron Tolido at Capgemini blogged it in “Crisis! Hurray, Crisis!”. Ron makes a very defensible case that companies that face crises are more apt to look for innovative solutions to truly help them leapfrog the status quo and solve longstanding problems that had been previously ignored or solved by long-term, big-ticket investments.

On a more personal level, we have witnessed an upsurge of interest in mashup technologies in the last few months and, to be candid, we weren’t quite certain there was any single cause. But Ron’s post led me to my AHA! moment. Mashups are front-and-center for many of today’s most innovative enterprise leaders because they need innovations like mashups to hack a path back to stability, growth and profitability. In fact, some have begun to posit that service-driven solutions have the opportunity to really shine instead of being a victim of those cutbacks that are so common in times of crisis.

This reminds me of a saying attributed to Jawarhalal Nehru, one of the leaders for independence in 1940’s India:

“A leader or a man of action in a crisis almost always acts subconsciously and then thinks of the reasons for his action.”

Innovative leaders are now hearing that little voice in back of their head that’s demanding different approaches and technologies than what they did in the past. If crisis drives need and need drives adaptation, then crisis is good.

Read More...

Wednesday, January 23, 2008

Welcome to the Party IBM!

Wow, two big weeks in a row for enterprise software. Last week was all about the now-passe Oracle/BEA/Sun/MySQL acquisitions. This week is another big week for enterprise software: IBM announced ‘Lotus Mashups’ at LotusSphere this week.

This is a major milestone for ‘Web 2.0 for the Enterprise’. Sure upstarts like JackBe talk about this stuff. But when leading-edge technologies like enterprise mashups are productized by a tried-and-true software provider like IBM, you know that your conservative, non-early-adopter type of CIO has gotta ask ‘what’s that and do I need it?’. I think Ian White at ComputerWeekly summed it up best: “Using browser based technology Mashup will enable internal and external business objects to be deployed and connected by end users. This will create a new generation of self service applications defined by end users and connecting processes and data at the glass in a way that suit the business not just IT. Potentially this is a very exciting announcement.”

And this should also be a wakeup call for the rest of the big enterprise software providers who don’t have a concise enterprise mashup offering (I’m talking about companies like SAP, Salesforce, Oracle, CA and HP). Soon these guys will realize what IBM already knows: enterprise mashups are the face of a SOA platform for the business user. How can you not have that as part of your enterprise software portfolio?

IBM’s Rod Smith and David Boloker have been spearheading mashups at IBM for well over a year and we grudgingly admit they’ve done justice to the concept (we like their alphaWorks QEDWiki site). And we think JackBe and IBM are not just aligned in its marketing-speak, but also aligned in our overall architectural view of the enterprise mashup space. Check out the architectural similarities between Lotus Mashups and JackBe’s Presto. It's qualities like this that [we think] make mashups enterprise-ready and enterprise-grade:

  • Lightweight and server-based;
  • Built around security and governance;
  • Dynamically driven;
  • Consumes multiple data sources;
  • Gets data to the user quickly;
  • Let’s the user tag, search and share mashups.

You probably know that IBM has five major software brands: DB2, Lotus, Tivoli, Rational, WebSphere. If you know what these brands encompass then you’d probably agree it makes sense they’re putting mashups under the Lotus brand. Lotus is the most ‘user-centric’ of the 5. And I think it is also a testament to the fact that enterprise mashups can actually be about the user, not the developer or some back-office middleware software. This is, of course, exactly what we mean with our now semi-infamous tagline, ‘The User is the Killer App’.

And we hope that continued focus on the business user can remove some of the FUD (that ‘fear, uncertainty, and doubt’ for you non-warrior types out there) concerning user-facing/user-driven Web 2.0 technologies like enterprise mashups, wikis, and blogs. I think Ross Mayfield expressed these concerns best: “The new [Lotus Mashups] tool gives users an easy way to build composite applications that they can share with others and publish to their own or a shared workspace. One analyst said he wondered if IT administrators would be concerned by the possible security and management implications that may arise.”

While we at JackBe agree there are issues like security and governance to consider (and we’d like to think we have a pretty good handle on them), the real impediment to ‘user-driven’ enterprise solutions seems to simply be our 25+ years of inwardly-focused IT efforts. This makes it easy to forget that the average business user is more-and-more technically-inclined and self-sufficient every day. You can thank the constant flow of consumer-type sites like FaceBook, Digg, and NetVibes for that. ‘Born Digital’ has an entirely new meaning now.

So, if you are a Lotus customer, congratulations! You have something to look forward to. But, if you’re like many companies who don’t have Lotus, come give JackBe’s Presto a look.

I can't wait to see what next week brings...

Read More...

Thursday, January 17, 2008

Interesting Times

‘May you live in interesting times.’ It may be real a curse from ancient China or merely something invented by an imaginative book editor. Either way, it fits the world of enterprise software. In case you missed it yesterday, approximately nine BILLION in cash and stock went from Oracle and Sun to BEA and MySQL, respectively.

Here at JackBe we love Oracle and Sun. And not just because they give me a couple of gazillion dollar corporate acquisitions to talk about during my guest appearance on Fox Business News last night, but because we’re close partners with both companies and we have over a dozen Oracle/Sun alumni. So it’s no surprise that we follow both companies closely. In my opinion, both acquisitions are biggies for the acquirers, the acquirees, and the enterprise software industry in general.

In case you didn’t know, Sun already has two database products. JavaDB is based on Derby and is all Java. Maybe it’s not an enterprise-grade database but it’s there. And back in 2002, Sun acquired Clustra, a high-performance clustered database. Many of us at Sun at the time thought this was the Oracle competitor but it didn’t seem to go anywhere. So, I bet you’re thinking what I’m thinking: what the hell is Sun going to do with MySQL? Is Sun onto something here? Are they the one to bring some fresh perspective into the database space? Boy, I hope so. This is certainly their chance. Here are a couple of possible outcomes:

  1. Sun offers a shrink-wrapped ‘DB-in-a-Box’. For a few million you get a high-performing Sun E25K server optimized and bundled with MySQL.
  2. Sun creates the first database on a chip. If anyone can do it, Sun can. They own the hardware and the operating system. It’s right up their alley.
  3. (My Favorite) They service-enable MySQL and make it their entry into the Web 2.0 space. Quoting directly from Sun’s press release: “This broad penetration coupled with MySQL's strength in Web 2.0, Software as a Service (SaaS), enterprise, telecom and the OEM embedded market make it an important fit for Sun.’ Sun, if you’re reading this, we’re here to help.

As for Oracle, a quick Google search on the phrase ‘Oracle acquisition’ will confirm what you probably already know: Oracle has done a lot of acquiring and BEA isn’t likely to be the last one. So, ho-hum, another part of the enterprise-solution pie is now owned by Oracle. Interestingly, in one odd way the Oracle acquisition parallels the Sun acquisition: Oracle will now have 4 distinct portal solutions (Oracle Portal, Oracle Webcenter, BEA WebLogic Portal, and the Plumtree products that are now under BEA AquaLogic brand). The Oracle Fusion and BEA AquaLogic feature sets also have a great deal of overlap. It kinda makes Oracle the 800-pound gorilla of portals and SOA.

Are you a Portal/Fusion/WebLogic/AquaLogic user who is now a little concerned about the future? This screams for consolidation of the portal and SOA product lines. And as we’ve written in the recent past, this becomes yet another Oracle-owned property that has only marginal tangible integration to other Oracle products for the immediate future. Sure, Fusion will fix it all but that’s not a journey that will be completed anytime soon. Oracle, if you’re reading this, we’re here to help.

Finally, here’s a result of these acquisitions that hasn’t gotten as much attention as it should: Sun and Oracle become real software competitors. MySQL has nibbled a $50M hole in Oracle’s database pie already. And once you remember that Sun sells a lot of hardware that runs Oracle databases (especially the big boxes that sell for up to $4M), you’ve got to wonder how these moves might impact the lucrative Sun-Oracle server-database relationship. On the portal front, Oracle’s portal domination could also impact Sun’s portal, Sun Java System Portal Server. Do you turn to a low-cost Sun alternative to avoid the confusion of the Oracle portals? Perhaps it’s too soon to tell.

Interesting times indeed. And it’s only January 17. It’s shaping up to be quite a year!

Read More...

Friday, January 4, 2008

Web 2.0 in 2008: What's Out, What's In

Some of us are ready for the Web 2.0 wave that is now breaking over us, and some of us are not. The McKinsey Quarterly just put out an insightful article, “Eight Business Technology Trends to Watch” (registration required), that outlines eight unique business trends that will be enabled by the Web 2.0 technology wave. With apologies to the guys at McKinsey for oversimplifying their detailed work, here’s my brief synopsis of their ‘Big 8’:

McKinsey’s Eight Business Technology Trends to Watch

  • Distributing co-creation’: Let everyone in your supply chain create.
  • Using consumers as innovators’: Let the people who consume your product also customize and extend your product.
  • Tapping into the world of talent’: It’s not plausible to hire all experts as full-time employees. It’s becoming more effective to hire experts for specific jobs as needed.
  • Extracting more value from interactions’: Tacit interactions are becoming more valuable and will be core to the workforce by 2015.
  • Expanding the frontiers of automation’: Continue to give more and more visibility to customers and supply chain.
  • Unbundling production from delivery’: Treat your IT systems as a platform and not only a destination so other companies can “plug-in”.
  • Putting more science into management’: Syndicate analytics to partners and customers so they can analyze and provide better information back into the system.
  • Making business from information’: Innovate above raw innovation to create higher value information systems.
After reading this I was inspired to create my own ‘What’s In and What’s Out for the Knowledge Worker in 2008’. I expect some of these will resonate with you no matter what your role is in your enterprise.

JackBe’s What’s Out and What’s In for Knowledge Workers in 2008

  • Out: Big IT, In: Big User - Don’t grow IT to help the knowledge workers. Grow the ability to help the users create (mashups).
  • Out: Integration, In: Collaboration - Don’t integrate systems, put collaborative tools in the hands of users so they can connect information in their own unique ways.
  • Out: Consumer Mashups, In: Enterprise Mashups - Tired of Google Maps as the premier mashup? Enterprise mashups based upon real ERP/CRM/SFA/homegrown data help drive dramatic competitive advantage.
  • Out: Big SAP, In: Little SAP - Help users have “smaller” access to their SAP data. No single user needs it all; most want it in bite-size chunks.
  • Out: Integrate Everything, In: Let the User Mashup - Knowledge workers need ad-hoc and situational data which is dynamically integrated in small amounts. Provide the tools to let the users integrate (mashup).
  • Out: LinkedIn the Website, In: LinkedIn in your Enterprise - Professional networks are growing quickly. Enterprises need this capability within the enterprise, as users are coming to expect this kind of empowerment.
  • Out: All-in-One Web Destinations, In: Embeddable Mashup Applications - Users will increasingly resist going to a new one-size-fits-all Web destination every-time they need information. Instead, provide capability for users to embed mashup applications in their own portal, application and even their iPhone.
  • Out: B2B, In: U2B - When you think B2B, you think EDI. When you think EDI, you're thinking about lots of time and cost. Instead of trying to integrate disparate businesses using B2B, promote User-to-Business access to information. Don’t push information to the user, notify them and let them have access to the amount of information they need.
  • Out: Emailing Excel Spreadsheets, In: Mashing in Excel - Copy and paste into Excel and emailing the spreadsheet is Mashup 1.0. Let the user mashup in Excel and collaborate by pushing out parts of Excel information as shared data services.
  • Out: Portals, In: Portals - Portals will certainly be around for a while. 2008 is a good time to re-assess your portal 1.0 technology and start moving to an agile and lightweight portal 2.0 technology like Netvibes and PageFlakes.

This is a lot for any enterprise to embrace but the paybacks can be massive. So, is your enterprise ready?

Read More...

Wednesday, August 29, 2007

Who is Person of the Year at your Company?

When it comes to software, these are interesting times for both techies and non-techies alike. Witness Time Magazine's Person of the Year for 2007: "You". This is a savvy reference to users' interaction with "the new Web" or "Web 2.0", with...

"...community and collaboration on a scale never seen before. It's about the cosmic compendium of knowledge Wikipedia and the million-channel people's network YouTube and the online metropolis MySpace. It's about the many wresting power from the few and helping one another for nothing and how that will not only change the world, but also change the way the world changes.

The tool that makes this possible is the World Wide Web. Not the Web that Tim Berners-Lee hacked together (15 years ago, according to Wikipedia) as a way for scientists to share research. It's not even the overhyped dotcom Web of the late 1990s. The new Web is a very different thing. It's a tool for bringing together the small contributions of millions of people and making them matter. Silicon Valley consultants call it Web 2.0, as if it were a new version of some old software. But it's really a revolution."

Wikipedia, YouTube, MySpace. Exciting stuff to be sure. Not to mention Flickr, Google Maps, Twitter, Pandora, Last.FM, digg, del.icio.us and the multitudes of other Web 2.0 sites out there. Hard to argue with the idea that these sites are changing the way we interact with technology and the resulting benefits. But one important aspect of this "revolution" that the Time feature fails to point out is that this transformation is currently restricted almost entirely to the consumer space. The benefits of this "world-changing" experience largely disappear as these same users enter their corporate workplace each day and use their business applications.

In the workplace, instead of sharing these next generation Web experiences, users typically find themselves interacting with different siloed software applications that are often poorly integrated with each other and whose UIs do not enable the sort of interactivity, configurability, and customization they desire.

In this world, it might be more accurate to say that the corporate ERP system or the ubiquitous-but-annoying Portal software is 'person' of the year! This is not to disparage the vendors of these software packages (much), but to highlight the fact that change often comes more slowly to the corporate environment and is limited or throttled by these tools.

By now you know well that our goal at JackBe is to bring the benefits of Web 2.0 to the Enterprise and make "You" (The User) the person of the year inside the workplace. Our approach to bringing the benefits of Web 2.0 to the Enterprise is to create the premier Enterprise Mashup Platform (which we call Presto).

At JackBe we believe that Mashups are user-driven, user-focused and ad-hoc in nature. But as we've discussed in the recent past, what differentiates our approach to Mashups from what you'll encounter in the consumer space is an approach that embraces (yet does not displace) existing Enterprise infrastructure and middleware. And as heterogeneous, disparate data sources are the norm, enterprise mashups must meet the need of bringing these hetergenous sources together elegnatly. Finally, I can attest personally that any good Enterprise Mashup Platform must also be built to deploy securely (with the proper governance and access control policies) and safely (with capabilities for high-availability and real-time monitoring).

Remember, we're no longer not talking eye-candy technology to connect restaurant listings with Google maps. We're building solutions to critical, often sensitive, business needs. Serious features for security and safety are unsexy-but-vital capabilities you've got to have in your Enterprise Mashup platform.

If you are a Enterprise Architect in a Fortune 2000 company, these are capabilities to live by. I'll be discussing topics like enterprise mashup security and reliability in great detail in my next few posts. And that's the kind of stuff that would make YOU into Person of the Year in your company.

Read More...

Sunday, July 22, 2007

Defining Mashups

Over the last year, the term mashup has become extremely popular not only in the consumer software space, but also in enterprise software. It has been a little more than a year since I joined JackBe as VP of Engineering responsible for executing our vision. Over this time, I and our team at JackBe has been busy creating our enterprise mashup platform, which is a unique innovative offering in enterprise software today, by combining the benefits of RIA technologies such as Ajax/RIA, Web Services, Service Oriented Architecture and Mashups.

At an internal technology briefing last week, my team and I presented and demonstrated the features of Presto, JackBe’s enterprise mashup family of products, to 25 developers and consultants. One of the important areas of discussion was around what we mean by a mashup and how the term 'mashup' has evolved over the last year to mean almost anything. For example, the following is the definition of the term mashup on Wikipedia:

A mashup is a website or application that combines content from more than one source into an integrated experience.
The problem with this definition from my perspective is that it allows you to practically label anything as a mashup, including a portal application, composite application, and what have you that brings disparate content onto a single web page.

I don’t think I want to disagree with this or any other definition of a mashup floating around in the industry. However, I feel that all the existing definitions and explanations are lacking something so important about the real intent of these mashups. This was also apparent at the discussion a few weeks ago at the IBM Mashup Ecosystem Summit. So, now I feel compelled to offer you what we at JackBe mean by a mashup:
A mashup is a shareable software block created by a user, encapsulating ad-hoc user driven processing of disparate data sources, delivered with a user focused view.
Allow me to elaborate further using the following characteristics:
  1. Mashups are made up of user-driven micro-orchestrations. In other words, when I access some data or service, I am performing small operations on the way data is computed and rendered in a very informal and iterative manner. For example, consider how one uses a spreadsheet which is a great example of a canvas where mashups happen in the enterprise when a user pulls in data from different sources, combines, sorts, computes, filters and visualizes by iteratively processing it until he gets the desired results. If you really think about it, what the user is doing is really orchestrating getting data from different sources and processing using one or more operations to yield an integrated view of the data.
  2. Mashups are user-focused, i.e. they are primarily created by the user for the user. They are not the product of some developer or IT guy writing a lot of code. However, current examples of mashups that we see are primarily developer oriented, it is just the beginning. The real value of mashups comes when we enable and empower our end users to perform these mashups the way they want to do it without having to call and rely on IT needs.
  3. Mashups are ad-hoc creations and are very situational based on users immediate short term needs. They are designed by the user to meet a specific need. These mashups have a very short life span varying from hours to days. This is the reason that the users cannot wait and demand IT to create and deliver these mashups.
  4. Mashups can be visual and non-visual. The most common kind of mashup that is out there is probably something that overlays some information on some kind of a map. However, there is more to mashups than just displaying pins on a map. I can mashup disparate data to create an integrated data view. I can mashup processes to create a new process. I can mashup domain models of different application domains to create a new application domain model.
  5. And finally, mashups can be performed on the client side and on the server side. However, I think the best value of a mashup is when we combine both client side and server side mashup functions since we can defer heavy lifting to the server and build intelligent clients that can enhance, complement and focus on user experience.


Before I conclude, I would like to emphasize a few points.
  1. Whether we do visual or non-visual, client-side or server-side, mashups must be user driven and user focussed.
  2. Just because mashups are user driven and user focussed does not mean that we no longer need IT. IT is still a critical part of the whole mashup infrastructure in an enterprise. However, instead of the users going to IT for every little thing they need which can be transient, situational and ad-hoc, they should be able to accomplish what they need without having to rely on traditional IT and experienced programmers to build what they need. For example, imagine what would happen if Microsoft Excel users needed IT help to write a macro or to create a chart from a table of data they put together. Mashups in the enterprise must address these kind of needs of enterprise users accessing disparate data and services to create and share new information in the Enterprise Web 2.0 world.
In my next blog entry, I will discuss more about our work in creating our comprehensive enterprise mashup platform that encompasses the above characteristics. It finally feels great to be able to talk about what we have been obsessively building over the past year!

What do you think? I am really interested to hear other opinions and thoughts around this.

(Editorial note: Since I've been asked about this a few times, I've submitted this blog to Digg. You are welcome to add your Digg here.)

Read More...

Sunday, June 17, 2007

Faster, Better, Stronger

Did you notice our blog has a new look? That's because this evening JackBe launched a new edition of its website. Normally, my cynical personality would respond to such an announcement with a ‘great, even more marketing sludge to ignore’. (I’m the guy who runs marketing!) But I expect this time it’s different because our new site isn't just more pleasing to the eye, it's easier to use and has a lot more information.

Most importantly, JackBe has set up an Evaluation Download of Presto, our Enterprise Web 2.0 Mashup Platform. It's an easy way to get started with enterprise mashups, SOA virtualization, and Ajax applications.

And, as we’ve posted in the past, we know it isn’t necessarily easy to wrap your arms around the 'Enterprise Web 2.0' thing. So we’ve added ‘Getting Started’ roadmaps for techies and non-techies.

We’ve also added new ‘See It In Action’ videos, new hands-on demos, new whitepapers, and some new case studies of Enterprise Web 2.0 in the real world. A complete list of new stuff can be found here.

Send us a note if you can’t find what you need. If you think it’s important, others might too. And isn’t collaboration what Web 2.0 is all about?

Read More...

Tuesday, June 12, 2007

Differences in 2.0's Continued

Wow, we received fantastic feedback on our the last post, Differences in 2.0's. In particular, we received emails asking for more clarification about the difference of Enterprise Web 2.0 and Enterprise 2.0. I created a pic (see below) that I hope will help.

First, let me attempt to relate Enterprise 2.0 to Ford, the car company. We could draw parallels to Enterprise 2.0 and what Henry Ford did with manufacturing. In this case we could say Ford created an 'assembly plant 2.0' which changed the core of the whole organization; organizational processes & relationships with said processes, the workforce, their roles, relationships with partners and customers, and how all of these parts interact with each other. This is a stretch but what I am trying to convey is that the core of the enterprise, down to how its business & peoples operate, changes and doesn’t resemble that of the organization before. This change resembles more of a social diagram tied together by Web 2.0 social tools and loosely coupled web apps capable of being composed or customized by each node at a moments notice to respond to whatever need arises using inputs(data & information) from around and out of the network.

[...pause after that mouthful...and we're back...]

In this stretch example, the change creates a Ford company that looks and operates much differently (better) than other enterprises around it still assembling cars the pre-Ford way. This is due to the relationships between the people, data, and the collaborative nature of the new organization.

I expanded a portion of this new picture to incorporate the two facets of Web 2.0 (The social collaborative paradigm shift & the Web 2.0 technology enablers that make this possible), how these once implemented correctly make up the Enterprise Web 2.0 infrastructure, and lastly how with the addition of a Enterprise collaborative paradigm shift, all make up Enterprise 2.0.

You’ll notice that the nodes here state ‘The User’ but this user could be one person, a team, or even a business unit. The connecting lines can be thought of as the social construct or Web 2.0 paradigm that I talked about in the last post, and the Web 2.0 bubbles as Web 2.0 technology enablers connecting Users with systems and other Users.

So, simply stated (I hope) Enterprise Web 2.0 is a technology solution made up of Web 2.0 and Enterprise 2.0 is the organizational paradigm shift that leverages these solutions which, by EW2.0's very nature, must be deeply embedded in the organization to work, creating a much different 2.0 organization as a result. This transition takes time as the whole organization re-roots strategically around the embedded Enterprise Web 2.0 infrastructure. Now one could raise the point of why go through all of this -- benefits of Enterprise Web 2.0 adoption? But this is an entirely new post all of its own. Here are a couple of posts that might help if interested.

I hope this helps. Although I am not a graphic artist, I think it pretty much summarizes the connection and relationships of all four 2.0’s we touched on in the last post sums up how I put all these pieces together. As always I am open and would like to hear your thoughts. mike@jackbe.com

Read More...

Sunday, June 3, 2007

Differences of 2.0's

A lot of people ask us here at JackBe about the definitions and or differences between Web 2.0, Enterprise Web 2.0 and Enterprise 2.0. So here are some of my thoughts simplified for a blog post.

Web 2.0 – There are two parts to this one which will make sense when I get into the difference between Enterprise Web 2.0 and Enterprise 2.0.

1. Web 2.0 – the user-driven paradigm shift. Youtube, blogs, wikis, RIAs with greater self-service capabilities… all of these are examples of a paradigm shift from older HTML static, mostly one way communication of ideas and information to a new User-Driven web model which enables you and me to more easily contribute content, share information and collaborate with each other through the web.

2. Web 2.0 - technology enablers. This user-driven shift has been made possible in part by new or now accepted technologies and techniques which have gained greater penetration as web application tools. Such include: Ajax, proprietary RIA tools like Flex and Lazlo and now Silverlight, Service Orientated Architecture (SOA), Ruby on Rail and other lightweight dev models, Web Services like REST and RSS, Mashups (data and visual) and Tagging. Of course this is not an exclusive list but I think you get my point.

Enterprise Web 2.0 – the Web 2.0 technologies mentioned above put into practice in the enterprise. For example: richer, more productive customer self-service apps, inter-department collaboration through bogs, and wikis. But simply ‘slapping’ these technologies into a rooted organization will not bring about the same successes and value that Web 2.0 apps have enjoyed in the public domain. Enterprises have too many constraints and need a mind and culture shift along with deep embedment of these 2.0 tools into its processes to have any kind of a definable impact.

Enterprise 2.0 – The Enterprise 2.0 is analogous to #1 above in that it represents a user orientated paradigm shift of the enterprise makeup itself. It embraces the decentralized organization built around disparate data and information with users empowered to create new information built around and on top of others ideas through sharing, and collaboration. An organic organization loosely designed and constructed to empower knowledge workers to do what they do best by giving them what they need, when the need it and how they need it by enabling them with 2.0 technologies and nurturing this new paradigm mind set internally. Here enterprises reap the benefits of 2.0 through network effects from its user’s contributions and collaboration and realize success that increases proportionally as more users contribute to the organism creating a potentially indefinable value proposition to stakeholders.

Each of these could be expanded in much more detail but why make it more complicated as this? If you have any thoughts please feel free to share or contact me. That is after all the point.

Read More...

Tuesday, May 8, 2007

Enterprise Web 2.0 and the Department of Defense

As we've mentioned in the past in this blog, the Defense Intelligence Agency (DIA) is a JackBe customer and an avid adopter of Web 2.0 technologies. Just this past week I had the pleasure to speak on the CTO Panel at DODIIS Worldwide Conference in Chicago, the IT show sponsored by the DIA. It only took a few minutes on the exhibit floor to appreciate the emergence of Web 2.0 as a important initiative in government.

One of the mandates of John Howard, Deputy Associate Director of National Intelligence for Intelligence Community Enterprise Services (the title is very telling in itself!), is that users need to get information in their hands as quickly as possible without government red tape getting in the way. Executive mandates aside, the interest in Enterprise Web 2.0 within this community is not very surprising when you consider that Intelligence analysts are defacto Tacit workers. They are a great example of ad-hoc workers that do something different every day and benefit from correspondingly dynamic and adaptable supporting software systems.

Specifically, this community has shown great interest in using Ajax as an interaction technology and SOA as a business functionality-sharing technology. There's also a lot of buzz around mashups because, I believe, they see the value of ad-hoc integration. Two other issues that were frequently discussed were security and governance. How does an organization, government or not, support common credential authentication and propagation? And these aren't merely rhethorical questions. We heard one speaker give a great practical example: they will support DEERS, a DOD X.509 common credential and attribute service, which is key for any workable multi-service consumption or mashup use. As each service has its own set of user credential, users would have to login to each service which would be unusable.

And like a lot commercial enterprises, the DOD is struggling with other strategic issues related to Web 2.0 technologies like SOA. As the CTO from JFCOM put it, they are already experiencing "SOA silos". Best practices and implementation rubrics are becoming crucial to avoid these kinds of problems. That might sound obvious but most of the big SOA vendors want to own the entire stack and 'integratation' often stops at their own product set. As Scott McNealy (CEO of Sun Microsystems and a keynote speaker at the Conference) said, "Integratable" is important. I couldn't agree more.

As always, the DIA (and the DOD in general) has a lot to teach us commercial folks.

Read More...

Friday, May 4, 2007

Making Web 2.0 'Meaningful and Achievable' in the Enterprise

JackBe firmly believes that Enterprise Web 2.0 software must be user-centric, web-driven solutions that enable ad-hoc, user-driven collaboration and integration. Recently, I had the pleasure of speaking at the CSC Leading Edge Forum on "Making Web 2.0 Meaningful and Achievable". (If you're interested in the presentation, the slides and audio are available here.) It is always interesting to see how new, innovative concepts from the consumer world are adopted and adapted to the enterprise.

If Web 2.0 is about empowering users to share and collaborate, then how will this principle be worked into the enterprise? Interestingly, both the Economist ('Serious business: Web 2.0 goes corporate') and McKinsey ('How businesses are using Web 2.0') have given Enterprise Web 2.0 some of their attention recently. These reports are definitely worth reading. Based upon their surveys of architects and CIOs, the first wave of Web 2.0 projects in the enterprise will focus upon wikis and mashups (and some supporting service-enablement efforts). That's good, practical stuff.

Read More...

Sunday, March 18, 2007

Mashups Give SOAs a New Life via Forward Integration

I've been saying for while that we have to consider that Services within an SOA become 'instant legacy' and this is not a bad thing. Users don't own the services and generally cannot request changes to Services. Plus, future applications will be based on a sea of services, so you might as well get used to not being able to ask for any changes to the services. So, users and business developers must assume that services are forever immutable. So what's a user to do?

Mashups to the rescue. Mashups let the user do things forward of the Services to get the data in a form they can use. With transforms, conditions, filters and scripting, users can 'virtualize' the service and make the services much more useful to themselves. And, these new virtualized services are instantly reusable services themselves, serving as potential inputs to the next round of mashing.

This is very much the old airline reservation mainframe model. You can't mess with the 30 year old mainframes, so the innovation has to happen forward of the legacy.

I like to call this "Forward Integration". More on this later...

Read More...

Tuesday, March 13, 2007

Ajax is for real in 'Real-World Ajax'

There are a couple of new books on Enterprise 2.0 you may want to check out. First, from Sandy Carter at IBM, is ‘The New Language of Business: SOA & Web 2.0’. It's a good look at what makes SOA projects work. But more important, as Joe McKendrick at ZD Net points out, the book elevates Web 2.0 to true enterprise-grade status. I couldn't agree more.

But we'd would be remiss if I didn’t give equal time to ‘Real-World Ajax’, a substantial effort from our friends Dion Hinchcliffe and Kate Allen. This type of work just proves that Ajax is ready for prime in the enterprise. Once you read it, we expect you'll agree. (In the interest of full disclosure: Yes, we are a bit biased, as there’s a nice section in there on JackBe’s Ajax Bank demo.)

Read More...

Monday, March 12, 2007

Business Value Continued….Enterprise Mashups and Total Cost of Ownership Part 2

Well I’m back with some more ideas and thoughts about Web 2.0, the enabling technologies driving it, and the potential benefits for enterprises. I tend to focus on the technologies and the enterprise aspect of Web 2.0 simply because I get tired (am tired) of people defining it as simply a “social collaborative” movement. Although this is true, and great for my girlfriend who can blog and share her photos, this says little to the strategic impact that the underlying technologies, that make capable the social aspects, can have on the enterprise. Here are a few real universal business situations or rather timeless barriers to a better bottom line that technologies such as Ajax, Mashups, and a SOA can positively affect.

Quickly adapt to Changing Business Needs.

When organizations mandate a business process rule, such as a limit on the size of a particular type of business transaction, it is typically embedded deep within the application code. Finding, adjusting, and maintaining consistency with other systems can be error-prone and extremely time consuming and error-prone processes. By deploying such rules in a separate but integrated environment, organizations can empower business executives via a user interface to achieve extreme agility and oversight.

Effectively Monitor and Continuously Improve the Business

Systems information and transactional flows capture critical interactions that may be required for financial, contractual, regulatory, and business governance. Tracing and reporting audit data are tedious tasks and tenuously contingent on predefined conditions, including monitoring servers and client devices, coding predetermined subroutines to capture processing metrics, running batch routines for replication and reporting, and so forth. Due to the complexity of pulling this information together across a whole business process, the effort is often only made when critical issues arise. To avoid business risk, ongoing monitoring can be automatically captured by the abstracted process layer, which can trigger alerts, alternate process flows, provide automated reporting, and expose many other intelligence metrics. By reacting to early warnings a business can preempt situations that may cause undue and costly mistakes. Organizations may also seek to implement Six Sigma or regulatory initiatives via this type on mechanism.

Simplify Business Integration Efforts

Integration points that are incorporated and managed in close context to specific business processes will provide significantly more value. In the example, enterprise procurement activities are often scattered across multiple systems, where the collating, parsing, and regrouping of items to be sourced are typically very manual and labor-intensive processes. However, these processes can be centralized and automated into a composite application or mashup that avoids these inefficiencies.

Reduce Costs and Risks of Manual Processing

Many organizations still struggle trying to automate manual or paper-based transactions. Highly document-intensive composite application processes are very common targets for Web services. In the procurement example, a user may intervene in multiple places, introducing the potential to corrupt the process flow. With an orchestrated composite application, automated triggers engage users where and when necessary, removing the need for each individual to know every activity in the process required to continue the flow of a specific transaction.

Leverage Existing Systems and Resources

Reusability of code not only saver resource efforts in development and maintenance, it also impacts application quality and security. By utilizing a standardized framework, companies can focus skills development across a variety of systems and solutions to prevent these effects.

Again, these are just a few examples but I and JackBe believe it is these types of scenarios that are not as highly publicized at the moment (overshadowed by the Youttube/myspace buzz) but will at the end of the day drive real business value to the mass.

Read More...

Tuesday, March 6, 2007

Enterprise Mashups and Total Cost of Ownership

What is all the Web 2.0, Ajax, Enterprise 2.0, SOA buzz in the driving towards? What does it mean for the line-of-business manager or the enterprise itself? I thought I’d take a moment at breaking down how the approaches/ideas and supporting technologies could positively impact the underlying business books. As to not make this to vague, I’ll take the latest hallmark of Enterprise 2.0, Enterprise Mashups, and a classic financial benchmark Total Cost of Ownership (TCO), and we’ll deconstruct how this latest set of technologies and techniques stands up against an old benchmark.

The TCO of a solution must take into account the initial and ongoing costs of the solution, relative to the solution it replaces. Enterprise Mashups (which are closely related to composite applications if not the same depending on one’s definition) are based upon a SOA and have the potential to lower TCO in several ways, including:

  • Managing the Services in an SOA is less expensive and complex than managing the interfaces in a traditional integration solution.
  • By leveraging the Web Services standards, mashups can lower the cost of proprietary technologies. Standards level the competitive playing field for vendors by lowering prices generally, and also simplify the task of integration, lowering costs directly.
  • Business analysts and technical business users are able to compose applications without the involvement of more expensive IT personnel.
  • The more complex a business change is, the more effective SOA-based mashups can be at reducing the TCO of the solution because of their inherently flexible nature.

Fundamentally, a SOA provides business an “agility quotient” – the more complex the underlying infrastructure and the more dynamic the business environment, the greater the benefit of an agile architecture to the business. SOAs provide the ability for business users to create enterprise mashups, thus creating and managing business processes.

Where am I going with all of this and how does it fit into the world of Ajax, RIA, or JackBe for that matter? There is one important piece yet missing – the user interface itself. If the tools that users interact with aren’t agile themselves, the benefits of these enterprise mashups to the organization risk being lost. The services that contribute to a mashup can now be consumed by light-weight client models thanks to Ajax. This is why the integration layer will be driven by those who are experienced with client side models. The back-end can do their part, expose the services, which they have or are doing so, but they aren’t going to be able to create what is truly needed for the consumption because this is not there expertise. The services are moving out farther-the power of the apps as well-to the client so it only makes sense that the driver of this integration will be through the client tier experts and more specifically, those skilled in Ajax.

Later, I’ll attempt to address the benefits of incorporating SOA, Ajax, and Mashups into the enterprise to more strategic business benefits. Please feel free to leave your comments and opinions.

Read More...

Monday, March 5, 2007

'REA is to RIA as Enterprise Web 2.0 is to Web 2.0' Returns!

I posted this a little while back, and the thoughts were expanded by our CTO, John Crupi in TechNewsWorld. Rich Enterprise Applications enable developers to create new situational applications that can offer improved usability and flexibility for the end user, and can deliver them faster than was possible using traditional approaches. This can empower users to easily assemble situational applications in response to rapid changing business requirements. Click the link to read the full article.

2007 is the year enterprises will start to more aggresively push for ways to realize the benefits of the Web 2.0 paragim shift and bring these efficiencies into the enterprise construct. In short, to empower users to consume, compose, and collaborate in ways that still adhere to enterprise standards and requirements.

Original post.....
Tuesday, October 03, 2006

REA is to RIA, as Enterprise Web 2.0 is to Web 2.0

MikeWagner
JackBe coined the term Rich Enterprise Applications (REA) as an evolution of Rich Internet Applications (RIA). RIA is to Web-grade applications as REA is to Enterprise-grade applications. The side pic. is my personal attempt to illustrate this visually. Some like it; some don’t, so comments are more than welcomed.
So What is Enterprise Grade?

Enterprises require tighter control, security, and reliability. In short they require a degree of governance that the average user building a Google Maps Mashup while sitting at their kitchen table doesn’t need. This should be no surprise to anyone who has worked for large organizations.

Read More...

Friday, February 23, 2007

Web 2.0 in the Top Secret world

One of JackBe's customers, the Defense Intelligence