April 27, 2007

My Network World column and outside links on network neutrality

Oops! It turns out Network World ran my column on network neutrality and Tariff Rebate Passthrough on April 23, not April 30 as I previously believed. So I should have gotten my list of outside links together sooner. Sorry. Confusing matters further, my post on Jeffersonet vs. Edisonet got Slashdotted, without me having provided a link to the column itself. Well, here goes.

April 17, 2007

Link list for network neutrality

My April 30 Network World column is scheduled to be on network neutrality, with this post linked out as a guide to further research.

Some of my own writings on the subject include:

I’ll supply some outside links on the subject later on.

April 17, 2007

The two Internets, Jeffersonet and Edisonet, and why they need to be regulated differently

Edit: This post was Slashdotted, along with Richi Jennings’ reply.

In a way, proponents and opponents of network neutrality are both correct! That is, they are each correct about different aspects of the Internet.

Net neutrality is both necessary and workable for what I call Jeffersonet, which comprises the “classical”, bandwidth-light parts of the Internet. Thus, it includes e-mail, instant messaging, much e-commerce, and just about every website created in the first 13 or so years of the Web. Jeffersonet is the greatest tool in human history to communicate research, teaching, news, and political ideas, or to let tiny businesses compete worldwide. Any censorship of Jeffersonet – even if just of the self-interested large-enterprise commercial kind – would be a terrible loss. Net neutrality is workable for Jeffersonet because – well, because it’s already working just fine. Jeffersonet doesn’t need anything beyond current levels of bandwidth and reliability. So there’s no reason to mess with what’s working, other than simple profit-hungry greed.
Read more

April 7, 2007

Check Point Systems UTM-1 and Crossbeam Systems – resolving the confusion

When Check Point Systems first briefed me on their new midrange UTM-1 appliance, they neglected to mention that their hardware designs were first worked out by Crossbeam Systems. Actually, it turns out that they even buy the hardware through Crossbeam. It took a comment here from Crossbeam’s Chris Hoff for me to realize the true story. Today, I connected with Paul Kaspian of Check Point to straighten things out. Here’s the scoop. Read more

April 3, 2007

Business intelligence — technology and vendor strategy

The most recent Monash Letter – exclusively for Monash Advantage members — spells out some ideas on BI technology and vendor strategy. Specifically, it argues that there are at least four major ways to think about BI and other decision support technologies, namely as:

  1. A specialized application development technology. That’s what BI is, after all. Selling app dev runtimes isn’t a bad business. Selling analytic apps hasn’t gone so well, however.
  2. An infrastructure upgrade. That’s what the BI vendors have been pushing for some years, as they try to win enterprise vendor-consolidation decisions. To a first approximation, it’s been a good move for them, but it also has helped defocus them from other things they need to be doing.
  3. A transparent window on information. As Google, Bloomberg, and Lexis/Westlaw all demonstrate, users want access to “all” the possible information. BI vendors and management theorists alike have erred hugely in crippling enterprise dashboards via dogmas such as “balanced scorecards” and “seven plus-or-minus two.”
  4. A communication and collaboration tool. Communication/collaboration is as big a benefit of reporting as the numbers themselves are. I learned this in the 1980s, and it’s never changed. But BI vendors have whiffed repeatedly at enhancing this benefit.

The Letter then goes on to suggest two areas of technical need and opportunity in BI, which may be summarized as:

Good launching points for my other research on these subjects are this recent post on analytic technology marketing strategies and two high-concept white papers available here.

March 30, 2007

When and why to virtualize

In one of the best Slashdot threads I’ve seen in ages, a number of posters chime in with their personal experiences of virtualization. (Usage hint: Set the general threshold = 5 to filter out the dreck, using Advanced Context Controls.) The rough consensus appears to be:

Makes sense to me.

March 29, 2007

More on Shai Agassi and SAP

Sramana Mitra has a little bit of a different take on Shai Agassi’s departure than mine. At first blush, it’s a distinction almost without a difference. In essence, she argues that Shai was frustrated because he couldn’t make big needed changes fast enough. That’s pretty close to my view that change simply wasn’t happening quickly or completely enough.

But the thing is — I think SAP’s overall technology roadmap has remained too incomplete. In essence — and I know some of my friends there will dispute this — SAP is still too focused on delivering software for how people should work, and doesn’t properly support the way they actually do — or realistically would like to — work.

Yes, it’s great that Dennis Moore and Dan Rosenberg are at SAP. But nobody — and this includes Shai — seems to be driving a real software re-think down into the individual products. The move to portal-based technology needs to be the beginning of the software functionality redesign, not the end. Josh Greenbaum thinks that Duet is all that and more, but I don’t see it that way.

March 28, 2007

Shai Agassi – a contrarian view

Shai Agassi is leaving SAP because, in essence, the old guard didn’t want to turn over the reins to him as fast as he would have liked.* Often, this kind of departure is a bad thing (e.g., Ray Lane at Oracle). But I suspect that SAP may actually be improved by Shai’s leaving.

*His other stated reasons include two very good and highly admirable ones – working on energy technologies and improving matters in Israel.

SAP’s technical strategy has three core elements:

  1. Automate business processes.
  2. Provide the technical infrastructure for automating business processes.
  3. Encapsulate process and data at the object/process level.

This strategy has been heavily developed and refined on Shai’s watch, with major contributions from lots of other folks. The issue isn’t vision any more. What SAP needs to do better is execute on the vision.

Read more

March 23, 2007

Great news for Openwave

Dave Peterschmidt is out as CEO of Openwave, and this is a very good thing. Even better, the company is being shopped. Best news: Jerry Held is on the committee doing the shopping. Not that I agree with Jerry on everything, but on the whole he’s pretty astute.

Openwave will probably find a buyer at a decent price. Dave’s bad, but he doesn’t completely destroy companies; there should still be some value there.

March 19, 2007

Three ways to market analytics-related technology

“Decision support”, “information centers”, “business intelligence”, “analytic technology”, and “information services” have been around, in one form or other, for 35+ years. For most of that time, there have been two fundamental ways to sell, market, and position them:

More recently – especially the past five years – there’s been a third way:

as early-generation implementations get replaced by newer ones.

At the 50,000 foot level, here’s some of what I see going on:

Related links

← Previous PageNext Page →

Feed including blog about enterprise technology strategy and public policy Subscribe to the Monash Research feed via RSS or email:

Login

Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.