Dear HENRIETTA TWITTLEWHEEZE

The Software Assurance (SA) portion of the current three year UC Microsoft Select license agreement will expire on January 31, 2008.

Select SA coverage provides you with the right to upgrade to newer versions released during the term in which you own SA. SA is valid for the term of the agreement, purchased in one, two or three year increments depending on when during the three year agreement period you purchase the license with SA. Renewals are all for the full three year period. SA also provides you with certain learning tools and trainings that Microsoft makes available to customers who own SA.

If you purchased or renewed Select SA coverage at any time from January 2005 through December 2007 and wish to renew that coverage, *you will need to submit your renewal order to CDWG by February 26, 2008* to ensure process time before the deadline with Microsoft.

Your order(s) that need to be renewed are:
Q5877392

Items ordered were
ACAD MS SEL VIRTUAL PC MAC LIC/SA 1Y

I think I can speak for the majority of our departments when I say: Huh?

What happened here is that the department (often unwittingly) purchased a license for Microsoft software that includes Software Assurance (SA) for one year. (That’s what “SA 1Y” means at the end of the license). Usually this was unintentional and caused by the confusing CDW-G price lists. What it means is that you purchased the right to upgrade your software to the latest version, for a period of up to one year. (Actually, it’s not really a full year; it’s whatever portion of the year was left until January 31, and it’s not pro-rated). If you renew your SA (by paying an additional license fee), you’ll continue to have the right to upgrade to the latest version; if you don’t renew, you’ll have to buy a new license when you want to upgrade.

Our general recommendation on SA is, don’t buy it unless there’s a specific reason to. The way the pricing works is that you pay almost double the stand-alone license cost for the right to upgrade to a future version you don’t even know you’ll want. Better just to buy the stand-alone license, and buy another one when you know you want to upgrade. (Back in the old days, you could buy a cheaper upgrade, but Microsoft and most other software companies have done away with upgrade pricing.)

But, if you got one of these messages, you already bought SA, so what should you do? First of all, you should make sure you have the most recent version of the software; you’ve purchased the rights to it, so grab it before your rights expire. If you already have the latest version, you probably don’t need to renew SA; you can just buy a new license when the time comes.

Licensing is one of the issues we’re examining as we develop a strategic plan; this situation highlights the high cost of managing and keeping track of software licenses the way we currently do. I would like to move to a model where a standard suite of software licenses is paid for centrally or included in our yearly rates, so that departments don’t have to spend so much energy on these kinds of issues. It will take a fairly significant reworking of how computing in L&S is funded, but I think we can do it.

However, coordinating the bulk purchases has been challenging. The vendors give me pretty tight timelines, so there’s not much opportunity to publicize the deal before the deadline for the discount expires. I always get requests from managers the day after the deal expires. And the rest of the year, managers have to decide whether to buy a computer when they need one, or wait for the bulk purchase to save a little money.

So this year, I’m trying something new. In collaboration with The Scholar’s Workstation, I’ve managed to get a web page for L&S computer recommendations placed on the TSW web site. This page will include Dell desktops, and Apple desktops and notebooks, with discounted pricing and our configuration recommendations. I plan to add Windows laptop configurations as well. We will keep the page current, so you’ll be able to get our recommendation and pricing any time during the year, not just during a two-week period in September.

I think this will work a lot better for L&S than the bulk purchase program did; the challenge will be keeping up with the changes in products and technology.

(Aside: I would prefer that our customers view us as peers and partners. We do make an effort to behave that way: for example, we locate our folks in departmental space rather than moving off-campus to an office where we could all sit together. We’d rather be closer to the users. But looking at the survey and interview results so far, it seems we have a ways to go to really be seen as integral by most of our customers.)

The report was done as part of ITLP, which is a leadership program for IT folks in higher ed. The program included folks from Berkeley, UDub, Minnesota, and Penn State, and the report we did surveyed people in distributed and centralized IT at all four of those universities. Because they’re all large public research institutions, the issues tend to be pretty similar.

My presentation (.ppt) focused on the communication and collaboration challenges. We have a ton of meetings, but we spend too much time presenting to each other and not enough time talking to each other. Our communications tend to be along accepted and formalized lines, and we often gloss over or ignore the underlying issues which keep us from moving forward. And yes, there is an irony that I was making this point via a PowerPoint presentation; however, the most important part of my presentation was a break-out session where I got the folks from each campus to talk to each other about the pressures or barriers they are facing in their local organization. I think it went well; the room got noisy enough that it was hard to hear, which I took as a good sign.

The report (.doc) addresses the above issue of communication and collaboration, and also has a number of recommendations to make the user experience better in specific technical areas (desktop support, email, and information systems).

We need a communication mechanism that has a better signal-to-noise ratio than email (what percentage of your incoming email did you actually read today?), but less formality than our web site. Fortunately, technology has already helped us out with this one; blog software is easy to install and use (we’re using WordPress), and it’s easier to be informal in a blog context. Plus, the ability for readers to add comments can create an open dialog that saves everyone from having to ask the same questions over and over.

I’ll be posting news, announcements, and random thoughts about computing in L&S on a regular basis. Pretty soon (once it goes through our editorial process!) we’ll have an advice article on how to subscribe to blogs using RSS, which can keep you updated without the notices getting lost in your email.

We’re also planning to offer blog space to any departments who use our server for their web site; if the department chair or IT manager wants a blog, it’s easy for us to add a new blog to fit into your existing web site.

On Wednesday, 7/18, LSCR will be participating in an off-site retreat (at the Headlands Institute in Marin) to synthesize some of the information we have gathered. Our focus will be to come up with some specific action plans and strategic goals which will guide the next phases of the process. We expect that in calendar 2008, we will have some concrete proposals to improve computing in L&S.

The retreat will require the participation of our entire staff, so we will be operating with a skeleton crew on 7/18. We will have someone watching our queues and able to contact us by cell phone if necessary, but we’d like to ask you to limit your requests on Wednesday to obviously urgent calls, or indicate whether the call can be deferred until we’re back at full staff on Thursday.

Thank you for your patience as we try to find ways to better meet the needs of our customers and the college.