Jarrett House North: ITxpo

ITXpo Wrap Up

Tim Jarrett — Fri, 19 May 2006 01:31:00 GMT

I spent the day today bouncing back and forth between sessions that were a little closer to our product’s core functionality (service desk, asset management) and actually doing product demo. I had a demo via Webex that ended just twenty minutes before I had to check out of my hotel room.

An aside to the Gartner folks: please try not to stack the ITXpo on the same week as JavaOne again. There weren’t any non-smoking rooms available in any hotels, and my congestion is killing me after three nights (and one two-hour demo) in the sour stale smoke in my room at the Renaissance.

ITXpo: Jonathan Schwarz keynote

Tim Jarrett — Wed, 17 May 2006 19:30:40 GMT

Below is a partial transcript of new Sun Microsystems CEO Jonathan Schwarz’s Q and A at the Gartner Symposium.

Q: Let's talk about StorageTek -- loyal following but what's next?
A: Talked to a board member who lost their tapes. I said, "What's the big deal? The tapes are encrypted, right?" But tape data isn't encrypted. So the new StorageTek products support encryption, tie into the public key infrastructure...that seems like a simple requirement, a great synergy.
Q: Thumper (codename) is the best and worst of Sun. There are so many platforms in Sun that do what Thumper does.
A: Three weeks ago we moved into a new set of opportunities. the thing about Thumper is it runs across all Sun's R&D. and we want to see that happen over and over again--look at Southwest. They're the most successful airline because among other things they run only one airplane, the 737.
Q: What about your other businesses? Sparc and x86 and ... A: We have to meet our customers where they are.
Q: How do you characterize your customers? A: Developers don't buy things, they join things. They love creative disruption. It's like social experiment. IT has some of that too, but the difference between them and you is that you have money. Developers love free. You guys hear free and think "free puppy."
Q: If developers love free, how does that affect your business? A: Developers are the leading indicator. Java started with developers. Now it's in the enterprise.
Q: But how do you move from a billion handsets with Java and 5 million Solaris downloads to revenue? A: We will add value. The amount of value that Sun receives is directly tied to how many of you use our customers' services.
Q: What's the value of Java to Sun? A: What's the value of a standard plug in the wall to the generator business? Q: Oh but what about investment in R&D? A: GE doesn't have to worry about someone plugging in a vacuum cleaner that won't let its electricity expand. And Java is fundamentally the Internet, which drives all our business. Java is about modular architecture on millions of devices. The more handsets with Java, the more the Internet is important and the more they need our support to build the architecture. It's hard for the Street to understand, but revenue is a lagging indicator of the developer's adoption of Java. Q: How lagging? A: Well, the day someone starts using Java, Sun is relevant to you. Q: But how much will they pay you for Java?
A: There is a division in the world--those for whom IT is a competitive weapon and those for whom IT is THE competitive weapon. We want the latter, and they will pay to support the infrastructure that underlies that competitive weapon. Q: What about your former customers, those who are running Java but not on Solaris or Sparc? What is attractive about that to you?
A: If you look at the numbers for middleware and servers, we are the leading performance, the best reference platforms for Java. We can deliver a better developer environment. Secondly, OS consolidation. Every large enterprise has cats and dogs. we can offer Solaris that runs on every major platform and is remarkably scalable. Third, we can offer the systems infrastructure (Opteron and Niagara) to affect the productivity and efficiency of their data centers.
Lots of argument about whether Sun is giving away too much value. Q: How do you translate the value from Java into people writing checks? How do you translate the technology lead into marketing? A: You have to understand that while I am deeply focused on financial performance--I need to be focused on the long run.
Q: But Sun lingers too long on Solaris, on Linux... A: Do I get to play the new guy card now or later? Let's think about mainframes. I went to talk to a now-bankrupt large airline one time about their mainframe, and the guy said, "Son, we installed the mainframe before you were born and will retire it after you die." Infrastructure sticks around.
Q: But how does Sun manage to exploit its innovation? A: You look at the airplane industry. The engine makers mint money, the airplane manufacturers sometimes make money, and the carriers never make money. Money accrues to fundamental R&D.
So ZFS is a 128 bit file system--do you need 128 bits? Maybe not but you might need the 65th bit. Solaris with ZFS eliminates the need for RAID controllers...
Q: So let's talk about open sourcing Java. Why is open sourcing Java without forking so hard? A: Look at the history of standards. Volume is the primary driver and standards bodies are secondary. And Microsoft is the biggest platform out there and Java on Microsoft is rife with litigation. So we have to be concerned about forking if we open source. Interoperability is hugely important to our customers.
Q: Top three reasons that Sun will be more successful in two years? A: 1. Leading indicators--lots of new customer interest. 2. Market opportunity--the need for reliable scalable infrastructure and solid development platforms isn't going away. 3. Management team. And we have boomerangs coming back all over the place. I talked to Ed Zander yesterday on stage at JavaOne and asked if he wanted to come back, and he said, "You got a job for me?" Now I don't know if he was serious...

ITXpo: And on the other side of the street...

Tim Jarrett — Wed, 17 May 2006 00:56:41 GMT

...across the street in the other part of the Moscone Center, to be more precise, Sun’s new CEO Jonathan Schwarz announced at the JavaOne conference that Sun will release the Java source code, and is asking developers for feedback on how to do that in the least disruptive way.

Wow. Cool. Guess I was at the wrong conference for Really Big News this morning.

ITXpo: Microsoft Vista and app dev

Tim Jarrett — Wed, 17 May 2006 00:47:40 GMT

Spent some time this afternoon looking at Vista and talking to the Microsoft team here (which includes some folks I know from my past life at Microsoft.com and my internship—hi Arvind! hi Peg!) about what’s coming down the pipe that our company needs to know about from an application development perspective. The guidance I got from the team there is that the major thing to pay attention to is the change in the privilege model—User Account Protection—and how that affects the installation and running of applications. Other than that, there are plenty of cool new features to take advantage of, of course. And the eye candy is impressive.

I also liked the built in RSS widget on the Sidebar. It does appear to be a little funky though—not in parsing the RSS, which is fine, but in loading it in chronological order rather than reverse-chronological order. I loaded my RSS feed for kicks on one of their Vista test machines and was surprised to see that the top entry was an old one—then surprised again to load the feed source in IE 7 and to see the same thing. Apparently the default XSLT+CSS orders the items oldest first. That kind of detracts from the usefulness for me. Maybe there’s a way to change it. I walked away with a beta CD and will check it out once I can install it on Virtual PC.

ITXpo: "Consumerization"

Tim Jarrett — Tue, 16 May 2006 20:19:57 GMT

If you know me, you already know one of my points about a few of the sessions that in a well-intentioned and generally thorough way address the question of “consumer” technologies in the enterprise. That’s the C-word itself. Our employees are not gullets that crap cash, and talking about technology expectations set by “consumer-grade” services like Google, desktop search, and IM that are all actually free brings some real cognitive conflict. How can it be consumer technology if there is no money changing hands?

The Docs (Searls and Weinberger) et al have done us a tremendous service in making us aware of the naming problem that the “consumer” label brings. I’m not sure they’ve done a good job of identifying alternative labels. “Producer” has been floated in the case of bloggers and other user-authored media creators, but it doesn’t generalize well; “human being” and “citizen” have the opposite problem—they’re too general. From a technology perspective, is there a useful way to talk about technologies that stand in opposition to the enterprise central-control model that doesn’t use the C word?

This is, I think, an important question. Anyone who has been around “consumer” driven businesses knows it can be like pulling teeth to get them to acknowledge that consumers are the same people who are inside enterprises, just seen at different times. And some of it has to do with the label. If IT organizations are to take “consumer” technologies seriously, as the Gartner mavericks suggest that they should, maybe finding a different word is a good starting point. The session I just was in, led by David Smith and Tom Austin, indirectly suggested one alternative: open market technologies. But of course this suggests that enterprise technologies are not open market.

The question of what to call it (reluctantly) put aside, the idea that systematically bringing non-enterprise technologies inside the enterprise could drive real benefits—not just to the end user but to the enterprise as a whole—is I think worth taking seriously. The speakers cited a case study of a company (which I think was Ford) which hardened its internal systems, then piloted an approach in which rather than providing a corporate desktop it gave its users a stipend with which they could buy their own—shifting the burden of administering and supporting the desktop to the end user, but also allowing them to take advantage of rapidly shifting consumer technology. They also discuss possible worlds where the base OS on an office machine is a consumer OS, and that the standard corporate desktop runs as an image inside a virtualization environment. How silly it is, they point out, to be a consumer service like Google or Ebay and to say that you can’t do business with me unless you have an approved, hardened browser that I provide and can guarantee is secure.

What I found interesting about all of these scenarios, and what they pointed out toward the end of the discussion, is that these trends could open the door for players like Apple—not iPods but Macs—to be dragged into the enterprise by end users who are comfortable and productive with them and can do most if not all of their jobs on them, once the users are given the leeway to provide their own desktop machine. Now that’s interesting.

ITXpo: Business service management

Tim Jarrett — Tue, 16 May 2006 19:02:14 GMT

One of the pitfalls (or blessings, depending on your perspective) of being a small software company is that you get laser-like focus on your core business problem out of necessity. For me as a vendor, one of the real value points about the Gartner show is getting exposed to other market segments that touch ours that I might not run across otherwise. That’s the case with the session I just attended on BSM (Business Service Management).

BSM is essentially a live dependency map, integrated to monitoring tools, that escalates only the monitoring events that have a real impact on the business and presents them in a business-consumable format. This is a goal for a lot of IT organizations—I know the Microsoft.com operations team was trying to implement something like this using the Microsoft server product stack plus homegrown tools about five years ago before the BSM market was grown, and knowing them they now have a complete solution. What was interesting to me was how BSM seems to dovetail with the work that my company has done in the last year on the CMDB, which really is about creating and documenting the service dependency map that BSM needs as a starting point.

When you combine a good CMDB with robust change management, and then tie in a good monitoring API and logic about how component status rolls up (or doesn’t) to the status of a service, then all of a sudden the time and effort spent on building that CMDB has paid some unexpected dividends.

Gartner ITXpo 2006

Tim Jarrett — Tue, 16 May 2006 17:21:03 GMT

I’m back at Gartner’s ITXpo after liveblogging parts of it last year. I’ve decided this year to pseudo-live-blog—to take notes during the session and post them later. Pulling out a laptop during one of the keynotes last year just felt too weird. Blogger culture hasn’t totally permeated the IT universe, and I drew too many stares.

However, I did notice a blogger’s lounge is available on the show floor alongside all the media lounges. So maybe things are changing... albeit really slowly.

It will be interesting to see if this year’s official conference blog actually writes anything about any of the sessions, rather than the conference events.

ITxpo: Keynote with Eric Schmidt of Google

Tim Jarrett — Wed, 18 May 2005 22:20:47 GMT

The keynote interview with Dr. Eric Schmidt, CEO of Google, was as interesting for what he didn’t reveal as what he said. Eric has a bracingly dry sense of humor about his business and the industry, but he is deadly serious about the company and its responsibilities and challenges. He is also skilled at the art of offering insightful answers that do not directly answer the questions he is asked, so be forewarned as you read my notes. (Unless noted, everything below that is not a question is a paraphrase or direct quote of Eric.)

Q:Has the Internet leveled the playing field such that the dominant players in the industry can’t exercise their power? A:You know, “dominant” has a specific legal meaning...

There have been a lot of changes in the industry over the last 10-15 years. Back then, email was something you had to get in the car and drive to the office to do. I’d drop my daughter off, go to the office, do email, finish email and then hop in the car and go home...

(On how Google solves the performance and responsiveness issues that other companies might face online:) The problems are easier for Google because our data tends to be more static and lends itself to being replicated, as opposed to transaction based data that changes frequently.

(On Google’s internal systems:) When I got to Google we were going to build our own financial system because we were frustrated with the limitations of Intuit’s Quickbooks and its five-user license. Seriously. So I said that isn’t going to work exceptionally well when it comes to Sarbanes Oxley and auditing. We implemented Oracle Financials and put it in a box, and said “we aren’t going to change this.” Then we built a system around it to manage the business’s contact with it and we change that frequently.

Our focus is on personalization and comprehensiveness. For instance, you can see Google internet search results, your intranet (with the Google search appliance), and your hard drive all in one results list. Of course that brings in the issue of privacy, and that is where the “don’t be evil” corporate culture comes in. ...Anyone can pull the ripcord and say “that’s evil” from an end user perspective and stop the train. [And no, Dave, I didn’t get a chance to ask him about autolinking, and he didn’t volunteer an opinion.]

We’re not in the information technology business, we’re in the information business. We have only digitized a very small percentage of all available content. There is a lot of room in the market.

(On advertising:) We don’t run the business as an advertising business. We run it based on end user satisfaction. If we keep our users satisfied, we keep our ad inventory up, which keeps advertisers happy. Q: You’ve taken away ad revenue from magazines and other traditional content players.... A: I prefer to think we’ve grown the market. There is a growing shift to more contextual ads and we are playing in that market. Q: You also seem to be important to a very large base of very small companies.... AIt is scary to understand that you are fundamentally in the revenue chain of a small business. We disseminate that information across the company and use it in planning products.

Q: You hired the lead developer of Firefox. Are you going to build a browser? A: We decided a long time ago that we would pursue a browser independence strategy, so that our services would work well on all browsers. These people, like the one you mentioned, are working on that, and do important work with the open source community as well.

Respecting your customers

Tim Jarrett — Wed, 18 May 2005 17:33:27 GMT

Catching up on non-ITxpo related topics this morning, two things caught my eye. First, my delayed reaction to the announcement that the New York Times will be putting some of its content, notably op-ed columns, behind a for-pay wall starting in September. This is of course brilliant because the Times’s editorial opposite number, the Wall Street Journal, has its constellation of right wing editorial columnists available for free. So now there will be even less of an opposing voice online. What’s most depressing as a user and reader of the Times is that this move comes after a history of reader-and-blogger-friendly decisions, including RSS support. So long, NYT, we’ll miss you. Is there an editorial forum out there that wants to stay on the record, and stay in the conversation? (For straight news, the BBC is looking better all the time.)

Second, the announcement from Microsoft about their new ID infrastructure, InfoCard. On the surface, the announcement sounds a lot like Apple’s Keychain; a local system solution to hold identity information such as login names, passports, and certificates. The difference is that InfoCard, like its failed Passport predecessor, can also hold credit card information. The shift in Microsoft’s identity management strategy, from central control to user application, represents a clear victory for Microsoft’s customers, and may be a pretty good indication that Microsoft is doing a better job of listening than it was four years ago. (More information about InfoCard, including a description of the user experience and some underlying technology notes, courtesy Johannes Ernst.)

Connection? Your customers will be the people who tell you whether your new business plans will succeed or fail. Learning to listen to them is an essential skill that must be mastered if you are to compete.

—Which gets me nice and warmed up for the final session I’ll attend at ITxpo, Are Your Customers and Users Revolting?, where three Gartner analysts will discuss customer collaboration and communication technologies and the implications for enterprises. I’m going to see if I can arrange some sort of connectivity in the room so I can blog the session, but otherwise I’ll take notes and post later.

ITxpo: Cisco and IBM

Tim Jarrett — Tue, 17 May 2005 20:38:27 GMT

Charles Giancarlo and Steve Mills are on a panel with two Gartner officers. Giancarlo defines “complexity” as anything that causes customers headaches in implementation. Customers want simplicity, by which they mean that solutions are thoroughly tested for their environment, not fewer features. He points out that we simplify the mundane (networking protocols) and then build greater complexity atop the newly simplified stack. He also correctly points out that the desire for differentiation is a big source of complexity.

Mills says that complexity in software is a reflection of the desire for more autonomy from central IT control, and stems in some respect from the decentralization of IT infrastructure starting with the shift to minicomputers in the 1970s. He also says that software will continue to get more complex: “software developers, given enough resources in time, will reinvent the work of everyone who’s come before them.” He suggests that encouraging reuse and adoption of open source can help to simplify the stack by not encouraging the development of new code, and that bloat is primarily caused by a cultural issue among software programmers. Giancarlo agrees: if improvement in software code doesn’t directly drive customer benefit, then it isn’t worth doing.

Mills says that defeating the developer’s cultural tendency toward re-creating the wheel requires: time-boxing, or defining short-term incremental projects; starving the team for resources; and embracing user-centered design.

(My battery is dying; more to come.)

Later: In discussing how to improve reliability in the face of proliferating software versions, Mills talked about reducing redundancy in code and reproducing known configurations and feature paths in the test environment. Giancarlo talked about lessons learned from integrating Linksys’s consumer business in creating a balance between complexity and functionality.

Causes: infrastructure is cumulative (earlier today someone said applications never die; the consensus appears to be that retiring outdated IT offerings is almost impossible). One thing that might help is, following Drucker, to continue to push good ideas down into silicon so that they move lower in the stack. Unfortunately, says Giancarlo, complexity grows organically: today’s skunkworks project is tomorrow’s killer competitive advantage, so it adds to the complexity. The wrong thing to do is to try to remove complexity from new products; rather, look at them when they provide comparatively less value and try to remove complexity then. Also, the multiplicity of architectures can be a political issue.

Why to reduce complexity through SOA: Mills: money is lost in the cracks between all the handoffs between different legacy systems. You need to add some IT complexity in end-to-end monitoring to enable the business to reclaim the money lost in its patchwork of pre-SOA systems. Governance is one of the most important solutions for reducing complexity.

ITxpo side note: blogging

Tim Jarrett — Tue, 17 May 2005 20:26:31 GMT

One thing I find interesting is the small number of bloggers in attendance at the conference. I’m currently sitting next to the only other blogger on the conference blogroll, Boris Pevzner of Centrata (and of MIT Course 6 mid-90s). Feedster and Technorati don’t turn up many hits for ITxpo; in fact, Feedster notes that this site is the biggest contributor and helpfully offers to scope the search relative to this site, which is a little scary. Likewise, most of the hits in Technorati are follow-ups to press releases or announcements made at the symposium. Is there so little of value that happens at the ITxpo that no one has thought to do it before, or is it just that the sort of organizations that have embraced blogging are under-represented among the attendees?

Certainly the logistics have a way to go before the conference becomes truly blog-friendly, with none of the socratic dialog (or good WiFi) that characterize the best of the unconferences I’ve attended. But the presence of the conference blog is a nice first step.

ITxpo: Real Time Enterprises

Tim Jarrett — Tue, 17 May 2005 19:39:20 GMT

Ken McGee is speaking about real time enterprises. He claims that with real time enterprises, which represents IT moving beyond its traditional boundaries into adding real value through real time monitoring and modeling of events in the company, that business uncertainty becomes “unnecessary and unavoidable.” The talk is an expansion on Ken’s book, Heads Up. The idea is to monitor, capture, and analyze root causes and overt events and use them to make near real time decisions.

One way to leverage the benefits of real time decision making, McGee suggests, is to publish financial information more frequently, which not only mitigates compliance risks (a la Sarbanes Oxley) but also has the side benefit of attracting investors eager to get more frequently updated information about the performance of their portfolio. Another is to investigate dynamic pricing. Both of these are predicated on taking known IT capabilities to the next level. In the case of dynamic pricing, this includes supply chain management, sales, electronic ink (for retail price display), wireless, and future demand prediction.

McGee also discusses decision criteria for what should be monitored in real time: only choose the information that, upon receiving it, would make a decision maker change her course of action (this does not include most “dashboard” information), and where such a decision would have a positive effect on the top ten revenue-generating (or cost) business processes. This turns out to yield a very small number of real time factors.

But he also says that IT people are going to be the most likely to block real time data gathering efforts. He doesn’t dive into this deeply enough, in my opinion. This is the area that might really yield some insight into the dynamic between decision making and IT.

ITxpo: Service desk best practices and methodologies

Tim Jarrett — Tue, 17 May 2005 18:32:52 GMT

This morning’s first session for me, Excellence in IT Service and Support, was a review of best practices in service desk management. A few interesting data points came out in the context of the talk, including informal survey results (of Gartner Data Center conference attendees) indicating that about 62% of respondents intend to adopt ITIL, either alone or with other methodologies; the number for ITIL alone was 31%.

This was interesting to me because the further in ITIL one gets away from service desk and incident and problem management processes, the more the coverage of the standard starts to overlap with other well-defined process libraries. For instance, processes in ITIL, including release management and change management, dealing with internally developed applications have a natural overlap with the Capability Maturity Model Integration (CMMI), which has software development as its focus. Organizations with internally developed applications need to consider not only which portions of ITIL, but also which portions of other methodologies, they may need to adopt as they carry out process improvements.

ITxpo: IBM announcement press

Tim Jarrett — Tue, 17 May 2005 18:10:04 GMT

Some follow up links on IBM/Tivoli’s ITSM announcements yesterday.

CNET: IBM’s Tivoli tackles IT processes: “The majority of application failures are due to changes that get introduced to a working system, said Bob Madey, vice president of strategy and business development for Tivoli.”

ComputerWorld: IBM unveils Tivoli systems management software. “The idea of having a centralized database for tracking IT assets in an organization arises from long-standing recommendations by the Information Technology Infrastructure Library (ITIL) and other systems management groups. BMC has already announced a centralized database, but IBM believes a federated approach makes more sense because many companies have infrastructure databases already, Madey said.”

The MarketWire release talks about the expansion of IBM’s Open Process Automation Library aka Orchestration and Provisioning Automation Library(OPAL) to IT service management, a point I failed to capture yesterday because I need to know more about it before I fully understand the implications.

ITxpo Monday wrap-up: blogger meeting call

Tim Jarrett — Tue, 17 May 2005 04:36:11 GMT

Well, that’s it for my first day at ITxpo. I’m off to Toronado.

Hey, a quick thought to other bloggers at the conference: while Gartner is mediating a networking breakfast on blogging on Thursday, I’ll be heading out on Wednesday night. If you’re interested in having an impromptu blogging meet-up on Tuesday or Wednesday—in or out of the scope of the conference—ping me.

Afternoon impressions: CMDB conquers all

Tim Jarrett — Tue, 17 May 2005 04:15:20 GMT

After the posting flurry of the morning, my battery (laptop and biological—damned jet lag) ran out, so I caught a nap before heading back to the Moscone for the afternoon sessions and the opening of the ITxpo floor. The sessions that I attended after the IBM presentation were complementary, so I’m going to wrap my notes up in one post.

The session on ITSM and IT Operations was a good overview, discussing the IT Management Process Maturity Model (an IT-centric take on the CMM), with an emphasis on building the service portfolio and treating it as a marketing document. The session on Configuration Management focused on tools that map dependencies between assets (hardware, networking, software and software components); this sort of approach is required if you are to provide effective support for an end-to-end service in the enterprise.

Both sessions had a fairly grim assessment of the move toward service-oriented IT service management. The ITSM session stated that through 2008, 65% of organizations will be focused on non-service-focus metrics like availability of individual servers, rather than end to end availability; and that it would take about five years for application development to start mapping service dependencies as part of the development process. Both sessions agreed that at least for the next year to 18 months, configuration management was going to be a largely manual activity.

It seems, with the proliferation of tools that provide configuration management for some piece of the IT puzzle, that the opportunity is for someone to provide a general standards-based interface to span across multiple CMDBs and to create connections and integrate key ITIL processes, particularly change management. But the cost could be dear: Ray Paquet estimates that, depending on the scope of your configuration tracking, you could have as many as 100,000 assets in a moderate-sized organization, and that the number of relationships that could be tracked scales exponentially. The challenge is to provide intelligent oversight across these databases but to provide drillthrough where required so one solution isn’t holding all the data.

IBM: Making ITIL actionable

Tim Jarrett — Mon, 16 May 2005 21:25:44 GMT

IBM unveils a stack of IT Service Management products, including new products and fourteen enhanced products. Key is an open federated configuration management database. Positioning as helping provide tools and practices to make ITIL more implementable. More coming...

IBM says that they’re uniquely positioned to bridge development and infrastructure, between Rational and Tivoli. This positions them to help make IT services more manageable.

Organizations have choices: implement lots of point solutions to fix specific problems, adding complexity; outsource, possibly losing a competitive strength; or apply ITSM. Customer testimonial from Patty Medhurst at Royal Bank of Canada. Complex environment, automated testing, etc. First step to ITIL is documenting the service catalog, which is a “gruesome but necessary” process; next step is automating key services.

Steve McMillan, leader of IBM Integrated Technology Services: moving from resource management to systems management to services management. In services management, need models: business reference model, process reference model for IT, and implementation reference model for IT. Business reference model: uses Component Business Model from PwC; move those into IT Process Reference Models and then into a Unified Process Model. (Aside: So far this is about architecture and modeling, not management...)

Customer testimonial 2: Don Woodward, American Express. He talks about using simulation tools (WebSphere Integrator) to build a simulation of the end to end infrastructure and to model the effects of process improvement on cycle time.

Now, focus on change management. Existing products fit in different steps. Now the new IBM Change and Configuration Management Database (CCMDB) maps changes in relationships and business data, plus policy and workflow actions. IBM IT Service Management: new platform in IBM Tivoli CCMDB. IT Process Managers: workflow capability, customize workflow, enable application of IBM/Tivoli technology to each step of process. Plus of course services.

IBM Tivoli Unified Process: process reference model for IT, aligned with ITIL. “Customers don’t have the sophistication or capability to map their processes, so here’s this online tool to help you do that...” And OPAL: expanding to auto-discovery. The process modeler is graphical, providing detailed workflow and activities for each step.

Other points: enhancing Tivoli Configuration Manager and Provisioning Manager with patch management and autodiscovery; new Federated Identity Manager, enabling extension of Tivoli Identity Manager out across the supply chain and to customers.

(Incidentally, here’s the press release—took quite a few clicks to find it.)

The CCMDB: Integrates supporting products and higher level processes, includes a process workflow and modeling engine, supports policy administration, provides support for configuration items and relationships, autodiscovery, reconciliation of discovered data, data federation. Works with Peregrine and Remedy.

Focus for Tivoli Process Solutions: Release Management, Availability Management, Integration Life-Cycle Management.

ITxpo: Web Services lead presentation

Tim Jarrett — Mon, 16 May 2005 21:09:28 GMT

Web Services in the Enterprise (Frank Kenney): Not about having services but about controlling them. Theme emerging from conference so far: important thing is to ensure that what is provisioned is supported. Show customers (partners, end users) that management layer is in place. Kenney discusses ESBs, APS and middleware, as well as vendor strategy, in considering the management of web services. (Wonder what Radovan Janecek at Systinet would say about the ESB point.)

I’m going to diverge from Frank’s talk for a second and bring it back into an IT Services Management framework. ITIL would say that there are several processes that connect to a hypothetical web service: service level management, configuration management, and availability management are key. Unfortunately a lot of ITIL implementations begin with a focus on incident/inquiry management and (if you’re lucky) problem and change management. This is good, but it’s still a reactive situation. If you’re managing proactively, you’re monitoring your services so that you can actively gauge when you’re meeting your service levels, not reacting when someone tells you you’re out of compliance, at which point it’s too late.

The issue is that there are tradeoffs in how you monitor the services. Frank covers that, but also has some interesting insights about the market as a whole: considering 12 major vendors in the market, there’s less than $50 million in 2004 revenue across all of them and fewer than 100 production customers. Also consider that many of the firms are on their second or third rounds of funding, and consider their exit strategy — likely acquisitions — before you buy.

Implementing ITIL

Tim Jarrett — Mon, 16 May 2005 19:50:38 GMT

Implementing ITIL (Shafqat Azim): suggestions include defining service catalog up front, defining dependencies (messaging systems, reporting systems); manage communications about benefit of process up to management and out to users; have a clear taxonomy and way of describing the scope of your initiative; have a clear vision of where you're going; look at a reference model with enough depth to know the challenges and dependencies that you will be facing. Consider the level of maturity of processes on which you are dependent. Focus your effort on a handful of processes to refine, but consider how to mitigate the weaknesses of the other processes.

Validate process through use cases of particular issues—implementing a server, responding to change, etc.

Once you have the organizational requirements and use cases, think about tools. The process comes first; tools come second. (Is this ever not true?) Use use cases to develop matrix of functionality for automation, and have a bake-off.

This is all fine, but: I wonder where the trade-off is between process paralysis and avoiding useless tool expenditures.

ITxpo Keynote: managing complexity

Tim Jarrett — Mon, 16 May 2005 19:25:51 GMT

The opening Gartner keynote is a tad condescending in the opening (who told Gartner’s CEO to cite “portal software” as an example of complex new IT challenges?), but quickly gets more interesting and starts delivering some insights, including: a quote attributed to Ezra Pound (“Man is an overcomplicated organism. If he is doomed to extinction it will come from a want of simplicity”—source?) and a citation of the Law of Requisite Variety. Complexity is a bell curve; claims there is an inflection point beyond which if you make a system more complex value diminishes rather than increasing. They suggest a consideration for review and acceptance of technology: “positive return on complexity.”

They make a very strong case that one way to mediate complexity is through process. Sounds good to me—that’s what ITIL is all about. Also useful: consider where to place complexity: away from the users. Don’t make IT’s life easier at the expense of the end user experience.

There’s a tradeoff between business needs and managing complexity. Also deep relationship between complexity and change management. Framework for understanding n-order change (this is when people start leaving): understand interaction between cultural systems (org structure, people) and technology systems (technology and tasks). First order change: tasks affected. Second order change: tasks and people. Third order change: affects every single variable, e.g. ERP. Fourth order: affects partners, customers, and other external connections.

Here comes the sale: there is a Gartner decision framework that helps you think across the strategic issues in managing complex new projects.

(Aside: wonder if there is a point to be made that blogging got adopted and is a profoundly transformative technology precisely because it’s less complex than other knowledge management tools?)

Managing complexity checklist:

Standardization: can reduce complexity or increase capacity to manage more complexity. One consideration: number of vendors and products, but be careful of lock-in.
Automation: from the traditional (adding additional tools to replace human labor) to augmentation (e.g. expert systems). Can hide complexity, but frequently not from IT; also raises the bar for IT staffing and pay.
Best practices:
1. Don't do everything at once.
2. Buy what you need, not what you might need.

Remember process! This is the connection between the organization and technical complexity.

Gartner blogging

Tim Jarrett — Mon, 16 May 2005 16:48:04 GMT

I don’t know how much blogging I’ll be doing at the Gartner conference, but apparently the conference organizers have already beaten me to it: check out the official conference blog. And they are offering to point to other blogging coverage from attendees. Cool. Next thing you know they’ll be rockin’ it unconference style. Or not. All I know is, if there isn’t a backchannel for this conference I may have to start one.

Go Gartner, go west

Tim Jarrett — Wed, 04 May 2005 23:00:31 GMT

It appears I’ll be in San Francisco in a few weeks for Gartner’s Symposium/ITxpo 2005, along with Eric Schmidt and, hopefully, a few of you. Are any of my readers going to be there? Or any bloggers at all? I’ll be the only person attending from my firm.