You get the picture: blinding rain, dangerous flooding, relentless winds that blow down trees and overturn cars. Plus, no electricity, unsanitary water, and survivors on the prowl for dry shelter and food. Does this sound apocalyptic? It should. We are living this reality with increasing intensity provided by global financial crisis.
If you knew the monsoon (tornado, hurricane, tremor—take your pick) were coming, what would you do that was prudent? Gather matches, dry food, blankets, and first-aid kit. Find sturdy shelter in which to hide until the super-storm subsides. And add a couple of other items…radio with fresh batteries, a Swiss Army knife with umpteen tools including screwdriver, file, mini-saw, corkscrew. (Corkscrew?)
Nobody, at least not today, is surprised to learn that IT is severely curtailing purchases of capital equipment. Make that “goods and services.” But, we don’t hear a total cancellation of all purchasing. In fact, Analysts, among others, have adopted a new guidance topic: “The purchases that make sense in today’s Global economy.” Some talk about organizations buying assets that enhance worker collaboration. Others recommend buying only those systems and software that enable better corporate decisions. Still others propose buying what delivers stronger security.
Few have explicitly stated, but all point to the phrase: “Buy only what is essential.” That “essential” is a descriptor which we have typically not, until late 2008, associated with buying any item—whether as personal consumer, or IT decision-maker. For years, most IT orgs bought systems with a variety of motivations. Sometimes those newly acquired platforms supported core business processes. Other times, servers were acquired just because they represented “cool” technology with interesting potential. Today/this minute, the dominant purchase question becomes, “Do we really need ‘this’ or can it wait til our business recovers?”
Which brings us to IBM’s System z. If ever there were a time the word, essential, applied to the new mainframes, it is now. Think this statement overstates the case?
- Is your organization’s intellectual capital as safe as it needs to be?
- Does your customer data ever appear at risk of invasion?
- Do your systems run at full or near-full capacity? Is Utilization where you want it?
- As your workloads spike up and down, do the costs for delivering IT services?
- Can your business sustain a systems outage, especially now?
- Do you want to provision more quickly and according to specific business needs?
- When you think, “IT Investment,” what type of system comes to mind?
- How green is your datacenter; how much energy expense do you now need to save?
- Where does “sprawl” fit into your portrait of your IT resources/physical space?
- What type of single system do you need to execute multiple, mixed workloads?
- When did you last closely consider today’s mainframe for cost-savings?
Obviously, every answer to these 11 is intended to point to IBM System z. Why? Because the word, “essential” applies to systems that, at minimum, enable service levels to be met, if not exceeded—at the lowest possible cost. Nobody needs risk, especially now. Nobody wants to invest in resources with short shelf-lives or whose architectures are not forwards and backwards compatible. Essential equates with “must have,” versus “nice to have.” Essential applies to the foundation, the core, the nucleus of IT operations.
This COMMON SENSE version is not intended as a lecture on prudence in a storm….or is it? What we want you to understand—and discuss with us if you don’t—is how IBM System z10, both Enterprise Class (EC) and Business Class (BC) more than meet the criteria that firmly establish an IT resource as essential.
Super-stability of System z saves on outage costs, helps retain customers and reinforces service-level predictability. Government Security certifications reinforce z’s risk management leadership in this vital category. Who can absorb the shock of stolen confidential information, and exposed military plans and defense systems? When could systems unplanned (and even planned) outages be worse to maintaining business continuity?
Fear-mongering runs rampant on Wall Street and other global financial centers. Fear generates irrational decisions about what to buy, what to sell. System z was built to overcome concerns about the ability of any system to perform to customer requirements…including dynamic needs fueled by a variety of dangerous circumstances. With an MTBF design point of greater than three decades, you can expect System z to exceed your availability expectations. With Gartner Group ratings that put System z at the top of Consolidation platforms, you can expect System z to take sprawl and put it in its place.
Bottom line: we can juxtaposition Global economics and their implications with System z until we are tired of keyboarding…or you stop reading. We prefer that you prepare a list of your “must haves” for the next 18-24 months of your IT operations. Then, let us meet with you, go over your list, and provide factual evidence of how System z can be essential to the well-being of your IT—especially during a Monsoon.
System z’s reputation was not built on fabricated stories, false claims, or price-gouging. We have proven we are essential to the major financial institutions, government agencies and other industry sectors. With the z10BC version, we are now essential to small-medium business.
Just one example of savings and value: The IBM System z10 Business Class has the capacity of up to 232 x86 servers (1) with an 83% smaller footprint (2), up to 93% lower energy costs(3), and a much higher level of security, control and automation – allowing for up to 100% utilization.
Let’s talk now. We welcome your toughest questions and support your concerns.
- Source: all performance information was determined by IBM in a controlled environment. Actual results may vary.
- Source: 1 quad-core z10 BC running 10 IFL's takes up 30 square feet. Compared to 232 single core x86 rack servers which takes up 150 square feet.
- Source: 1 quad-core z10 BC with 2 I/O drawers running 10 IFL's uses 4.5 killowats of power. Compared to 232 single core x86 servers which use 67.0 killowats of power.