Policies are the internal laws of an organization. Enterprise policies shape the behavior of business units into a common cooperative effort. Just like legislation, policies are often developed in response to a disaster
Although some policies are unique to an organization, there are often many commonalities between policies in different organizations. We find it helpful to divide policies into three categories: strategic, tactical and operational.
Time to strategize.
Strategic policies define the overall business imperatives. Think of the U.S. Constitution: Strategic policies are analogous to the Bill of Rights. There should be just a few, and all other policies should be assessed in light of them. Strategic policies are going to vary less from company to company. Here are some common examples:
Standardization. Storage services shall conform to a defined set of offerings, except in extraordinary circumstances.
Centralization. All storage shall be provisioned and managed by the centralized storage management group. No business may run its own storage infrastructure.
Service level agreements (SLAs). Storage shall be provided to internal customers according to negotiated SLAs.
Cost accounting. Business units shall be responsible for their portion of the cost of delivering storage services.
You can see that strategic policies would provide discipline to govern the business units and IT team. Storage would be standardized and cost accounting ensures customer requests don't get out of control. SLAs force IT to come to terms with what levels of service it can really deliver.
Strategic policies like these result in the alignment of the perspectives of the various parties at the negotiating table. IT managers often fear that if they offer solutions that are too costly, users might walk away and create their own infrastructure.
We call this the CompUSA argument: "If I can buy a Pentium 4 PC at CompUSA with a terabyte of storage, why shouldn't I?" This is a red herring, but tends to be rehashed. Strategic policies let everyone focus on negotiating the right level of service from the perspective of the provider and the consumer. Without alignment at the strategic level, efforts to create and enforce tactical and operational policies likely will fail. Without setting ground rules, tactical and operational policies can exacerbate any misalignment by forcing the IT organization and business units into a straightjacket of rules that are not in the best interest of either party.
Time for tactics.
Tactical policies put the strategy into practice, governing the management of the storage infrastructure. They must be set within the framework of the strategic policies. Strategic policies are likely to look similar regardless of your business, but tactical policies will often look different. The following policies would support the goal of standard service levels:
It should be obvious that these are much more implementation-specific. The number of tiers or protection options will vary depending on technology and business needs. This would be the place to specify exactly how metrics would be gathered and data would be protected.
The key to success is to make tactical policies as specific as possible. We've spent hours in meetings listening to storage administrators and application owners discussing whether or not to use a certain tool. These discussions can be preempted if the specific tools have been determined and documented ahead of time.
For the rest of the tip, go to: http://storagemagazine.techtarget.com/strgColumn/1,291266,sid35_gci954802,00.html
For more information:Tip: How to build a storage management practice
Tip: The best practices of storage management
Tip: Defining critical storage mangement functions
Stephen Foskett is a senior consultant at GlassHouse Technologies in Framingham, MA, specializing in storage management strategies and integration. He has also done extensive work in storage area network design and integration and Unix systems management.
This was first published in April 2004