Codes

Codes for construction of buildings are there for a good reason. As stated in many building codes, the purpose is to provide minimum standards to safeguard life and limb, health, property, and public welfare. This can be best accomplished by regulating and controlling the design, construction, quality of materials, use and occupancy , location, and maintenance of all buildings, structures, and certain equipment within the jurisdiction. From building a garage in Malibu, California, to building the Sears Tower in Chicago, codes prevent people from taking shortcuts, using inferior materials, ignoring basic human safety, and knowingly or unknowingly creating an unsafe structure. If there were no codes, buildings would catch fire and fall down a lot more often.

Who do we have to thank for building codes? Hammarabi, the Babylonian emperor, developed the first building code more than four thousand years ago. It was not the quagmire of codes in use today, but it stated in simple terms that if a building fell down and killed the owner, the builder would be put to death. Apparently it was up to the builder to decide what materials should be used to make a safe house for his client. Since his life was at stake, some real thought went into the structural design. The concern for building for the safety of the human occupants , at least, has continued and has developed into the complex swamp of codes used today.

However, there still is no universal code or set of codes that builders can follow throughout the world. There are, in fact, any number of codes, combinations of codes, and variations of codes, international, national, and local.

You have just stepped into the quagmire.

The Quagmire of Codes

There are several building code organizations within the United States that have created their own set of codes. For example, there is Building Officials and Code Administrators International, Inc. (BOCA), International Conference of Building Officials (ICBO), and Southern Building Code Congress International, Inc. (SBCCI). For fire codes, there is the International Fire Code (IFC), which is coordinated with the International Building Code (IBC). However, there is also the National Fire Protection Association (NFPA) who develop and publish NFPA 75 Standard for the Protection of Electronic Computer/Data Processing Equipment and NFPA 1 Fire Prevention Code 2000 .

There are other codes that must be considered when designing a data center. Below is a listing of the types of codes, though this does not represent all possible codes.

• Building codes

• Plumbing codes

• Mechanical codes

• Electrical codes

• Fire codes

• Fire sprinkler ordinances

• Energy conservation codes

• Sewage codes

All of the codes listed could be considered building codes in that they relate to the construction or remodeling of a site. Many of these codes are interdependent, and one code might refer to another code. One code might mention that you must have a 1- hour fire rated wall, but that the specifications for this are in another code. Your local code authority might say "Yes, the specs are in that code but you should use the specs in this code instead." The two codes that give these specifications might or might not be the same. Another possibility is that you would need to use more than one code to determine what your local inspector will agree is a 1-hour fire rated wall.

Also, some codes are identical, but masquerade under different names . For example, NFPA 70 is the same as the National Electrical Code.

The International Fire Code is yet another part of the quagmire. It is coordinated with the International Building Code. But it is maintained by a separate organization, the International Fire Code Institute. The IBC is published by BOCA. Even though BOCA publishes the IBC, they also publish state-specific building codes for Kentucky, Michigan, Ohio, and Virginia. Why it is called the International Building Code when even separate states in the U.S., not to mention other countries , might use a different building code? That's hard to answer. Just because something says it is international doesn't make it so.

There is also the NFPA that develops and publishes NFPA 75 Standard for the Protection of Electronic Computer/Data Processing Equipment as well as the NFPA 1 Fire Prevention Code 2000. They publish NFPA 70 which, while widely adopted in the U.S. and elsewhere in the world, is like any of the above code: subject to interpretation.

So, the problem facing the data center designer is: Which building codes must you adhere to? You should be concerned with the codes used in the jurisdiction in which the data center will be constructed , keeping in mind that these codes are subject to the interpretation of the building authorities in the jurisdiction where the data center will be built.

A case in point: A company decided to put power distribution units (PDUs) beneath the raised floor in data centers in San Diego, California, and Austin, Texas. No problem! The local code was interpreted in such a way that putting PDUs beneath the raised floor tiles was within code. The same company also considered putting PDUs under the raised floor in their facility in Hillsboro, Oregon. However, the electrical engineering firm and the project management firm, knowledgeable about the way things work in Hillsboro, said they didn't think the code authorities in the area would approve the use of PDUs under a raised floor. The electrical engineering firm and the project management firm met with the building officials in the area and proposed a good case for using PDUs under raised floor. However, code officials maintained that the use of PDUs under the floor would not get code approval. In the way these officials interpreted the code, PDUs under the raised floor would not pass code. It is also important to note that these discussions occurred before construction of the data center started, during the design phase. This forward thinking was also a money saver, because these determinations were made before PDUs had been ordered.

Whatever codes have been adopted for your local jurisdiction, they are all subject to interpretation by the local code authorities.

Codes and the Law

It is understandable that people would be confused about the differences between code and law, because they seem to be similar. They are both rules that must be adhered to. In the U.S., these building codes are not United States law, or even state law. This is why there are so many versions of the same code scattered about the U.S. and internationally. In fact, there's no law that says what code must be used. A jurisdiction might even adopt an older version of a code instead of the latest revision.

Code might not be law, but the consequences of ignoring code could result in legal action, particularly if people or property is damaged as a result. Quite simply, you must follow code to get sign-off approval by the building inspectors for the legal right to occupy the building. Occupying a building without the appropriate permits is a violation of law. This is how it works in the U.S. If you are planning to build in another country, make sure you find out how it works there, because other rules (or no rules) could apply.

So, what if you happen to be building in an area where the code restrictions are lax? Maybe you aren't required to meet certain codes such as NFPA 75. Leaving out those expensive fire doors would be a lot cheaper. However, your company might decide that, to create a data center that is safe for employees and equipment, you should build to standards beyond what the local codes require.

Who Can Help?

It is unrealistic to expect data center designers to know all the codes, along with their numerous permutations and interpretations. But designers should know which codes will be used. Again, designers are not working in a vacuum , but have many talented and knowledgeable people on their team, including outside contract professionals. Project management firms, architects , structural, HVAC, and electrical engineers are usually familiar with what code is used in that area and how to work with the local code officials and inspectors.

But how do you really know that these people will give you accurate information? Data center designers should know something about the codes and which codes will be used for their data center. Unfortunately, sometimes sections of these codes can be used to make "black hole" explanations for why things cannot be done or must be done more expensively. It would seem that working with reputable and ethical building professionals, the black hole problem should not occur. However, it could be a policy of a contract firm to interpret code in their favor, adding time and cost to a project. The data center designer should, at the very least, know to question the code and ask for specifics. Which code? Which section of the code? What, exactly, does it specify? Why is it interpreted that way? Armed with a few simple questions, you show that you are not willing to be taken advantage of, you might save the company a pile of money, and it will help you decide on the outside firms with whom you want to develop honest working relationships.