Musings on personal and enterprise technology (of potential interest to professional technoids and others)

Showing posts with label TCO. Show all posts
Showing posts with label TCO. Show all posts

Monday, November 30, 2009

Google Patent for Data Center Cooling Innovations - Data Center Knowledge

A diagram of an 'air wand' indicating the location of cooling vents in wand, a key feature of a patent application by Google data center engineers:






It's nice to see that Google is dedicating not only significant engineering but also legal resources, towards patenting innovative data center cooling techniques. Hopefully, this will lead to an affordable, reusable solution that can help organizations similarly optimize their cooling. As has been documented, cooling typically contributes to up to 50% of a data center's total energy costs (e.g. see for example The Greening of IT: How Companies Can Make a Difference for the Environment by John Lamb, p. 136), so of course cooling innovations can be quite significant towards reducing both carbon footprint and operating costs..

"Google Patent Reveals Data Center Innovations
November 30th, 2009 : Rich Miller

Google has revealed some of the secret technology inside its mighty data centers, but its engineers are busy cooking up new secrets.

An example: Google is seeking to patent an advanced data center cooling system that provides precision cooling inside racks of servers, automatically adjusting to temperature changes while dramatically reducing the energy required to run chillers.

The cooling design, which could help Google slash the power bill for its servers, reinforces Google’s focus on its data centers as a competitive advantage in its battle with Microsoft and other rivals for leadership in cloud computing. The company has customized much of the operation of its data centers, which serve as the engines powering its massive Internet business. Google builds its own servers and networking switches, and now appears to be customizing the racks that hold them.

Precision Cooling via ‘Air Wands’

The innovative rack cooling design features an adjustable piping system, including “air wands” that provide small amounts of cold air to components within a server tray. The chilled air enters the top of a rack through two vertical standpipes, which branch off into air wands – long, thin pipes lined with vents that release cold air.

The air wands can pivot to target cold air on specific components, or be swung to one side to allow equipment to be removed from the rack. Dampers on each standpipe can open and close to regulate the volume of air flowing into the pipe and air wands, while the vents on each individual air wand can be adjusted to point up or down, allowing for a highly configurable system..."

Full Article from
Data Center Knowledge: http://www.datacenterknowledge.com/archives/2009/11/30/google-patent-reveals-data-center-innovations/

Friday, September 25, 2009

Measurement + Monitoring of Data Centre Energy Use Immature Through 2011: Gartner

As previously posted, "cheap" servers really aren't cheap at all (Infoworld 5/2008), since recurring server operational costs are often as large or larger than the initial hardware capital investment. Below is a related update from Gartner, reminding us that "you can't manage what you can't measure". Here is Gartner's explanation of the importance of metrics for reducing data-center energy consumption [emphasis mine]:

Gartner Says Measurement and Monitoring of Data Centre Energy Use Will Remain Immature Through 2011:
“...when asked which energy management metrics they will use in the next 18 months, 48 per cent of respondents have not even considered the issue of metrics. However, without metrics it is impossible to get accurate data, which is essential to evaluating basic costs, proportioning these costs to different users and setting policies for improvement.

'These metrics form the bedrock for internal cost and efficiency programmes and will become increasingly important for external use', said Mr Kumar. 'Organisations that want to publicise their carbon usage through green accounting principles will need to have their basic energy use continuously monitored.'

Mr Kumar also urged organisations not to rely on internal metrics saying that evaluating server energy needs to be done in an open and transparent manner...”


hat tip / source: http://twitter.com/Gartner_inc/statuses/4339604501

Monday, August 10, 2009

MS Exchange2007/WinServer2008 compatibility issues

Seems that waiting for Exchange Server 2010 - rather than upgrading now to Exchange Server 2007 - may make sense for many organizations currently running Exchange Server 2003 [or earlier]. Although this seems somewhat inconvenient, I expect many organizations can deal with this successfully in several ways, given sufficient planning. This sort of constraint reminds me of the situation approximately 4 years ago, when some Microsoft shops wanted to wait until MS SQL Server 2005 became available for purchase, rather than immediately purchasing a SQL Server 2000 license. In fact, the Software Assurance up-front purchase (to purchase SQL Server 2000 with SA that would include upgrade to SQL Server 2005) might have seemed logical at the time for many organizations.... But of course, evaluating the full TCO of a subsequent upgrade to SQL Server 2005 would have involved more than the initial hard cost of purchasing Software Assurance. So perhaps the best decision (then and now) as to whether to invest in Software Assurance depends on the particular upgrade and change management capabilities for the specific organization.

The recent Exchange2007/WinServer2008 issue was explained in the recent Microsoft Exchange Team blog posting explaining that Exchange Server 2007 won't run on upcoming Windows Server 2008 R2. Further insights available from SearchITChannel.com: Dilemma: Exchange Server 2007 won't run on next Windows Server:

"...Customers upgrading to Windows Server 2008 R2, due later this year, will have to upgrade to Exchange Server 2010, which is also due this year. This news, disclosed in the fourth bullet point in a July 17 Microsoft Exchange Team Blog post, means Microsoft partners have to sell Exchange Server 2007 without the promise of support on future OSes and without Windows Server 2008 R2 interoperability with Exchange Server 2007... said Planet Technologies lead infrastructure engineer Mike Crowley: "If people stick with Exchange 2007 on Windows 2008 because 'it works,' I wouldn't expect them to want to upgrade the underlying OS just because a new one is available."

Wednesday, July 22, 2009

Gartner's 6/09 Magic Quadrant for IT Project & Portfolio Management

Source: Gartner (June 2009) .

Gartner have recently updated their "Magic Quadrant for IT Project and Portfolio Management".


As Gartner explains, "Project and portfolio management (PPM) applications can provide visibility into the current state of organizational initiatives, resources, and spending through the centralized collection of data from multiple sources and perspectives. Integration across multiple business and IT process domains through PPM system functions provides multidimensional views of this data for better visibility and understanding of resource supply versus project (and other work) demand in IT and other project environments.."

There seems to be some healthy competition among a group of strong leaders, visionaries, and challengers (including SAP, Innotas, and BMC), as detailed in this Gartner report. A related May, 2009 Gartner report (which unlike the aforementioned Magic Quadrant is not available to browse online for free) at http://www.gartner.com/DisplayDocument?ref=g_search&id=986223 , entitled "Market Share: Project and Portfolio Management Software, Worldwide, 2008", summarizes as follows: "After a banner year in 2007 with 24% growth, the worldwide project and portfolio management software market growth slowed to 7.4% in 2008 for a total of $1.2 billion. Among PPM vendors, Primavera, Microsoft, CA, Oracle and Agresso hold the largest market share."

As per my recent post regarding the US Federal CIO office, it is nice to see that PPM and related tools can be used in the real world with significant impact - e.g. to decide which projects should be permitted to proceed, vs. which should be halted in case they are significantly overrunning costs without yielding expected business benefits.

However, it is probably worth noting that even the best PPM tools do not add any meaningful value, unless the key business stakeholders contribute to its success by keeping relevant information and metrics up to date. Which is just another way of saying that even though the expected value / ROI may be large for a PPM undertaking, one should consider the full investment / TCO required: Not just the hard costs for licensing the software and related deployment requirements, but the full organizational commitment, training, and change required to make effective use of the PPM system and methodology.

Friday, July 17, 2009

Project Portfolio Management in action: US temporarily halts 45 IT projects (budgeted @$200 million)

As per Demian Entrekin's excellent blog on http://it.toolbox.com/blogs/ppmtoday , the US National CIO Vivek Kundra has embarked on an impressive and BIG IT project portfolio management and reporting initiative ( accessible via http://www.usaspending.gov/ ).

Today (Friday July 17th), a formal announcement on the related blog http://it.usaspending.gov/?q=content/blog confirms that 45 major federal IT projects are actually being temporarily halted. So the major USA federal PPM initiative is not merely a reporting tool, it is actually being used for taking meaningful and consistent action when project overruns are detected:

"Friday, July 17, 2009

Evidence-based decisionsVivek Kundra, Federal CIO

Today, the Department of Veterans Affairs (VA), under the leadership of Secretary Shinseki and VA CIO Roger Baker, announced that it will temporarily halt 45 IT projects which are either behind schedule or over budget and work to determine whether these programs should be continued. We’re not talking about a trivial sum here—the Fiscal Year 2009 combined budget for the 45 projects is approximately $200 million. The worst offender of the bunch was 110% over budget and 17 months behind schedule.

We were able to catch these contracts, in part, thanks to our new tool, the "IT Dashboard” which helped shed light on the performance of projects across the federal government.

During the next few weeks, the VA will audit these 45 projects to determine whether additional resources or new management teams can get them back on schedule.

If they can’t be fixed, the projects will be canceled.If you are just hearing about the IT Dashboard for the first time, it allows you to see which IT projects are working and on-schedule (and which are not), offer alternative approaches, and provide direct feedback to the chief information officers at federal agencies.

Given the size and complexity of the federal IT portfolio, the challenges we face are substantial and persistent. The dashboard is not a substitute for good management. Its value comes from leaders who use the information to make tough, evidence-based decisions on the future of IT investments.

The VA’s announcement is part of a broader effort by the Administration to make the federal government more transparent and to boost accountability and drive better performance. From IT accountability to personnel and contracting reforms, the administration is committed to providing better value, efficiency, and effectiveness for taxpayers’ dollars."

Hat tip: http://twitter.com/nytimesbits/statuses/2690095160

Sunday, June 7, 2009

Safire: Who is a 'Straw Man'? vs. Brooks: 'Pilot System'

William Safire has penned an excellent piece regarding the phrase "Straw Man", in his New York Times "On Language" column, On Language - Who is a 'Straw Man'? - NYTimes.com:

"Accepting the Democratic nomination in a huge football stadium way back in the presidential campaign of ’08, Senator Barack Obama displayed his oratorical talent by using one of his favorite tried-and-true devices in argument: “Don’t tell me that Democrats won’t defend this country!”

Who was telling him that? To be sure, his opponents were claiming that a Republican administration would be stronger on defense, but nobody was telling him or the voters that Democrats preferred abject surrender. At the time, reviewing that speech, I noted the rhetorical technique: “By escalating criticism, he knocked down a straw man, the oldest speechifying trick in the book.”..."

Safire explains these fascinating origins of "Straw Man" in the context of political speeches. Those of us involved in technology and other business projects, know that a "Straw Man" can also be used in a business context, typically to refer to the first attempt at documenting a project's initial charter and/or requirements, or even a preliminary prototype of a proposed new or enhanced system's user interface.

As explained nicely on mindtools.com:

"When you begin a project or start looking into a problem, you often have incomplete information to work with. So you can spend time gathering facts and data until you are ready to build a really strong argument or plan, or, you can get going straight away and jump in with a not-so-complete solution, with the intention of finding a much better one, as you learn more and more.

That's the premise behind building a straw man - creating a first draft for criticism and testing, and then using the feedback you receive to develop a final outcome that is rock solid..."

A similar, and very concise definition of "Straw Man" can be found in J. LeRoy Ward's excellent Dictionary of Project Management Terms :

"Working draft copy circulated for comments or suggested changes."

Finally, I would like to suggest a connection between the idea behind a "Straw Man" in business and technology, to the very similar concept in Software Engineering, as originally explained brilliantly in the classic Fred Brooks work: The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition):

"The management question, therefore, is not whether to build a pilot system and throw it away. You will do that [anyway]."

Thus, Brooks suggests that one may wish to "plan to throw one away", since it is quite possible that you will, anyhow. And by building this "pilot system" into the plan as an explicit milestone, communication is simpler, and expectations are more realistic from the start.

So perhaps, although not identical, Safire's "straw man" and Brooks' "pilot system" are both trying to capture the same notion: That we sometimes need to start with something we know is imperfect, in order to be able to proceed from there to a truly excellent result.

Sunday, April 5, 2009

Is There a Sub-Subnotebook in Your Future?, NYTimes, 12/1992 :)

Dell's tiny-footprint Netbooks seem to be selling nicely... This, despite concerns as to whether a full set of traditional corporate standard software (including anti-virus, anti-malware etc.) can run and be managed efficiently on a relatively modestly powered machine. Some say the Netbook's success to date, is partially due to the current economic situation ( see for example, CNet's "Faltering economy boosting Netbooks" ). Hopefully for Dell, the success of the Netbook will continue regardless of the economy.

In case there was any doubt however, this is definitely not the first attempt at making a popular "Sub-Subnotebook"... One example was written up nicely by Peter H. Lewis of the New York Times in December of 1992:

Is There a Sub-Subnotebook in Your Future?:

"... Taking advantage of recent advances in miniaturization, computer makers are creating portable computation and communications devices that can easily be carried in one hand or tucked into a coat pocket. But at some point the usefulness of small systems comes into question: Most information is still entered by typing, and no one has yet managed to miniaturize executive fingers.

That hasn't stopped some companies... from creating personal computers that are about the size of a calculator..."

Wednesday, May 21, 2008

Green IT numbers don't lie - Sustainable IT, Ted Samson, InfoWorld 2008.05.15

Some interesting metrics on server operational costs... Indeed, the TCO is way higher (e.g. several hundred percent over a 3-year lifespan), than the hardware invoice ;-)

And the dollar figures, if they tend to follow gasoline, are only going up

Green IT numbers don't lie , May 15, 2008, Ted Samson, Sustainable IT, InfoWorld: "...$1,870 - The annual operating expense for powering and cooling a single midtier ($2,500) server in a tier III datacenter. The number is $1,320 for a tier II datacenter, and it reaches $2,020 in a tier IV datacenter. According to the report, 'servers are often housed in a higher tier datacenter than necessary, further driving facility costs.' The point, of course, is that 'cheap' servers really aren't cheap at all, so the 'throwing hardware at the problem' approach isn't particularly sustainable..."

Sunday, January 20, 2008

A Pragmatist's Guide to Structuring IT Asset Data, Scott Parkin, eWeek, 2008-01-18

A nice article describing the real-world ILM challenges for IT asset management. The ITSM benefits of of linking the asset's service-incident history to the incident-management system, including hard and soft costs per outage, seem significant. However, this does not seem common among the vast majority of the COTS helpdesk systems I have seen over the years, and certainly not among the Service Management modules of major ERP systems, let alone with integrated continuous auto-discovery/maintenance of all hardware and software assets found on the network... sigh....

Here is a snippet from the full eWeek article :



"... Track initial acquisition costs, including asset purchase, required peripheral or supporting devices, operating system and software (as needed), and service contracts:

Most of this data will come from purchase orders; some will need to be calculated as a pro-rata share of a bulk purchase or license agreement.

For new purchases, update your purchasing process to include calculating and tracking this data in your asset record; for existing assets you will need to create a project to go back and aggregate/calculate this information and add it to your asset records.

Track ongoing maintenance costs, including annual service contracts, upgrade or replacement parts and the costs associated with Service Desk incidents for each device.
Ideally, this information is collected at the time of purchase or service and is immediately attached to the asset's service history record as a function of your established process. You should update your Incident management process to support this, whether you update the asset record manually or through automated technology.
This can be the single most daunting task in the mix; extracting and aggregating historical data for existing assets is a gargantuan task. Many organizations choose to simply start tracking this data as of a specific date and leave existing data unstructured. This is a good method for those organizations that are resource-constrained and willing to wait for highly qualified data.
Identify replacement costs for hardware, software and infrastructure elements. Remember to include both disposal costs for existing assets and install/deployment costs for new assets.
For commodity items such as end-user hardware (desktop, laptop) and software, these costs should be predictable within a range and will tend to be updated once a year as new contracts are negotiated.
For high-impact or high-value items, the cost of purchase may only be a small part of the total costs, and those costs may be difficult to estimate. This data is intended for planning purposes and should be reviewed at the time of planning, so supply a best estimate with supporting documentation to be used as a starting point for further research, not as an authoritative declaration.
The key benefit here is being able to quickly view approximate costs for individual assets, to aggregate that data by department or cost center and to use that data in research and planning efforts...."

Wednesday, November 7, 2007

CA Introduces End-User Self Service BlackBerry Administration | RIMarkable

An interesting concept... however ROI appears unclear unless this would obviate lots of ongoing blackberry support (i.e. why bother with Yet Another System to manage, unless it is beyond the initial setup on BES etc...)

CA Introduces End-User Self Service BlackBerry Administration | RIMarkable | The official, unofficial BlackBerry Weblog: "...The key point here for BlackBerry end-users is that they can go buy a new device, go to a web page, and hook their BlackBerry up to their work email without having to call the helpdesk."

Tuesday, October 30, 2007

Charging More for Printers and Less for Ink - New York Times

Another sign of the "greening" of IT (it will be interesting to see how this turns out :-)

Charging More for Printers and Less for Ink - New York Times:

'...Xerox is unveiling a costly solid-ink printer for businesses that will print color pages at the same price as black and white. The printer, which can handle 30 pages a minute, will cost $2,499, about $900 more than laser printers that operate at similar speeds.

The cost of ink to print 14,000 black-and-white ink pages is about $216, in line with the price for a page from laser printers using toner.

But the cost of printing in color will be the same, $72 each for the three ink sticks needed for a wide-color spectrum. Laser toner to print the same number of color pages could cost five times as much.

“That model, pricing color sticks at one-third of black, is going to be disruptive in this industry,” predicted David R. Spencer, president of Spencer & Associates Publishing, which consults for printers and helped Xerox test the new product.

There is no question about which industry behemoth Xerox hopes to disrupt. According to IDC, the market consultants who track industry sales, Hewlett-Packard commanded almost 40 percent of the global market for color laser printers last year, up from 33 percent in 2005. Xerox’s share held steady at 10 percent in that period. And Angele Boyd, an IDC vice president who specializes in imaging and printing, doubts Xerox will gain much ground.

“The bulk of the market still wants low-cost hardware, so it’s not like this will catapult Xerox ahead of H.P., or even help it nip harder at H.P.’s heels,” she said. “But it could help Xerox sustain its position.” ...

Tuesday, October 23, 2007

Virtualization vs. Security - Information Security Magazine

Another nice grain of salt to keep in mind re: TCO of virtualization:

Seven Winners, One Mission - Information Security Magazine: "...People are looking for less footprint and more computing power. On the business side, CIOs are looking at cost savings, then think about security. One side of the market is centralizing with thin, dumb clients, and using hosted software as a service and Ajax applications, dispersing processing power to the edge. The two intersections are never secured. Virtualization is fantastic: it does great things for cost, horrible things for security. But I think we're making progress on this portion of the uphill slant. Look at the classes of problems we have; we haven't eliminated any, we're creating more. Ajax is an example, and we're at odds of how business and technology are approaching these problem sets. We've put all this power in users' hands and we yank it back because we never engineered proper security in the first place. it's not right..."