Future Codes

The ability to take a 3D design of a building and enter it into a program that can check it against the building code has been discussed for years. The ability to do so will likely revolutionize the industry. There has been extensive research on how software programs can take the building codes and check a design, but these programs are often limited to specific portions of the code because of the code’s complexity.

Essentially, codes will need to change if the complexity becomes too great for the current methods of plans review, or if users demand better code checking software.

The question is, what will happen first?

Unlike some technologies that come and go, building codes are likely here to stay, but the way they are used is almost certainly going to change. As demonstrated the complexity within building codes is increasing, and reducing complexity in them appears to be necessary if the industry stays with the current methods. However, based on the extensive research into computer checking designs, it appears the shift away from traditional methods is on the horizon. The concept of blockchain or some other new technology may provide additional support for the transition. Blockchain is already being considered as a way to electronically handle construction contracts, and it is likely that other new concepts will be generated as a result. The ability to capture building drawings in the cloud is not new, but retrieval is still complicated. The ability to access old building plans is important after issues with previous building codes are discovered, but the ability to access drawings can be difficult once properties are bought/sold.

There are similarities in the complexity issues of current codes and with the codes necessary to computer check a design, but not all issues will be the same. Future work will be necessary to determine the differences and identify where complexity exist within the new codes. Computers have the ability to handle vast amounts of data, which means the complexity of the news codes can unquestionably be higher, but inevitably the engineers who implement the new codes must understand the limitations.

References

1. Wilcox, C., B. Nuttall, and T. Barnett. "Connection Details—Practicing Engineers and the Code." 2011 Structures Congress. 2011.

Bibliography

ACI Committee 318. "Building Code Requirements for Structural Concrete (ACI 318-14): An ACI Standard: Commentary on Building Code Requirements for Structural Concrete (ACI 318R-14), an ACI Report." American Concrete Institute, 2015.

ACI Committee 318. "Building Code Requirements for Structural Concrete (ACI 318-14): ACI 318-11 to ACI 318-14 and ACI 318.2-14, Transition Key." American Concrete Institute, 2015.

Arlani, A. G., and A. S. Rakhra. "Building code assessment framework." Construction Management and Economics 6.2 (1988): 117-131.

Benzarti, Youssef. "How taxing is tax filing? Leaving money on the table because of hassle costs." Browser Download This Paper (2015).

Building Code Requirements for Structural Concrete: (aci 318-71). Farmington Hills, Mich: American Concrete Institute, 1971.

Building Code Requirements for Structural Concrete: (aci 318-95) ; and Commentary (aci 318r-95). Farmington Hills, Mich: American Concrete Institute, 1999.

Building Code Requirements for Structural Concrete: (aci 318-05) ; and Commentary (aci 318r-05). Farmington Hills, Mich: American Concrete Institute, 2005.

Building Code Requirements for Structural Concrete: (aci 318-11) ; and Commentary (aci 318r-11). Farmington Hills, Mich: American Concrete Institute, 2011.

Bulleit, William M. "Structural building codes and communication systems." Practice Periodical on Structural Design and Construction 17.4 (2012): 147-151.

Cowan, Nelson. "The magical mystery four: How is working memory capacity limited, and why?." Current directions in psychological science 19.1 (2010): 51-57.

Cross, Hardy. Engineers and ivory towers. McGraw-Hill, 1952.

DeFriez, C., “How Code Complexity Harms Our Profession”, Structure Magazine, (July, 2014): 50.

DeFriez, C., “How Code Complexity Harms Our Profession, Part 2”, Structure Magazine, (Sept., 2014): 74.

Deschamps, Denise, Building Code Development and Enforcement: Impact on Accessibility for Persons with Disabilities, 2010.

Dimyadi, Johannes, and Robert Amor. "Automated Building Code Compliance Checking–Where is it at." Proceedings of CIB WBC (2013): 172-185.

Donohue, Sean. Email to the Author, 2014.

Field, Charles G., and Steven R. Rivkin. The building code burden. Lexington Books, 1975.

Gallotti, Riccardo, Mason A. Porter, and Marc Barthelemy. "Lost in transportation:

Information measures and cognitive limits in multilayer navigation." Science advances 2.2 (2016): e1500445.

Galvan, Sara C. "Rehabilitating rehab through state building codes." The Yale Law Journal (2006): 1744-1781.

Ghosh, Satyendra K. "Significant changes from the 2011 to the 2014 edition of ACI 318." PCI Journal 61.2 (2016

Han, Charles S., John C. Kunz, and Kincho H. Law. "A Hybrid Prescriptive/Performance Based Approach to Automated Building Code Checking." International Computing Congress. 1998.

International Code Council, et al. International building code. International Code Council, 2003.

International Code Council, et al. International building code. International Code Council, 2015.

King, Leonard William. The code of Hammurabi. Netlancers Inc, 2014.

Krause, Kate. "Tax complexity: Problem or Opportunity?." Public Finance Review 28.5 (2000): 395-414.

Kunreuther, Howard. "Mitigating disaster losses through insurance." Journal of risk and Uncertainty 12.2 (1996): 171-187.

Laffer, Arthur B., Wayne H. Winegarden, and John Childs. "The economic burden caused by tax code complexity." Austin: The Laffer Center, Texas Public Policy Foundation. Available online: http://www. laffercenter. com/2011/04/the-economic-burden-caused-by-tax-code-complexity (2011).

Lee, Jae Min. Automated checking of building requirements on circulation over a range of design phases. Georgia Institute of Technology, 2010.

MacGregor, J. G. "A Simple Code-Dream or Possibility?." Special Publication72 (1981): 199-218.

Martín, Carlos. "Response to" Building Codes and Housing" by David Listokin and David B. Hattis." Cityscape (2005): 253-259..

Mathews, D. D. "Towards a European Code for Concrete–Can Concise Codes be Comprehensible and Comprehensive?." The Structural Engineer 54.12 (1976):

476-477.

McConnaughey, John S. An economic analysis of building code impacts: a suggested approach. Washington, DC: US Department of Commerce, National Bureau of Standards, 1978.

McGuire, W. "Computers and steel design." Modern Steel Construction 32.7 (1992):

39-2

Mitchell, Melanie. Complexity: A guided tour. Oxford University Press, 2009.

Morgan, Jessica L. "Have wind design provisions become too complicated? a look at the progression of design provisions for mid-rise buildings." (2009).

National Fire Protection Association. NFPA 101 Life Safety Code. National Fire Protection Association, 2015.

National Fire Protection Association. NFPA 101 Life Safety Code. National Fire Protection Association, 2012.

National Fire Protection Association. NFPA 13: Standard for the Installation of Sprinkler Systems. National Fire Protection Association, 2016.

Nawari, Nawari O. "Automating codes conformance." Journal of architectural engineering 18.4 (2012): 315-323.

Nawari, Nawari O., and Adel Alsaffar. "Understanding Computable Building Codes." Civil Engineering and Architecture 3.6 (2015): 163-171.

Pearson, Cynthia, and Norbert Delatte. "Ronan point apartment tower collapse and its effect on building codes." Journal of Performance of Constructed Facilities 19.2 (2005): 172-177.

Peer, S. "Streamlining the Building Permit Process." Journal of Management in Engineering 2.4 (1986): 265-271.

Pence, E., “Code Complexity and Information Overload”, Structure Magazine, (Oct.

2006): 7.

Petroski, Henry. To engineer is human. New York: St. Martin's Press, 1985.

Pierson, D., “Who Hijacked My Building Code?”, Structure Magazine, (April, 2016):

66.

Pierson, D., “Changing Building Codes – Are They Really That Bad?”, Structure Magazine, (May, 2013): 58.

Pitt, P. H. "Towards a simplified code of building control." The Journal of the Royal Society for the Promotion of Health 99.1 (1979): 3-7.

Poston, Randall W., and Charles W. Dolan. "Reorganizing ACI 318." Concrete international 30.7 (2008): 43-47.

Salama, Jerry J., Michael H. Schill, and Martha E. Stark. Reducing the Cost of New Housing Construction in New York City. New York University School of Law, Center for Real Estate and Urban Policy, 1999

Scott, J. G. (1997). Architectural building codes: A graphic reference. New York: Van Nostrand Reinhold.

Searer, Gary R. "Poorly worded, ill‐conceived, and unnecessary code provisions." The Structural Design of Tall and Special Buildings 15.5 (2006): 533-546.

Searer, G., et all. 2007. “Are we really learning from Earthquakes? Declining Quality and Increasing Complexity of Modern Building Codes”. In Proceedings of the 9th Canadian Conference on Earthquake Engineering. Ottawa, Canada, June, 2007.

Shapiro, Stuart. "Degrees of freedom: the interaction of standards of practice and engineering judgment." Science, technology, & human values 22.3 (1997): 286-316.

Siess, Chester P. “The 1971 ACI Building Code Too complicated, too complex or both?” ACI Journal (1974)

Sporns, Olaf. Networks of the Brain. MIT press, 2010.

Stubbs, M. Stephanie "The Widening Web of Codes and Standards." Doors and Hardware (1988).

Tan, Xiangyang, Amin Hammad, and Paul Fazio. "Automated code compliance checking for building envelope design." Journal of Computing in Civil Engineering 24.2 (2010): 203-211.

Thompson, George N. "The problem of building code improvement." Law & Contemp.

Probs. 12 (1947): 95.

Title 26 – Internal Revenue Code (2016)

Title 26 – Internal Revenue Code (1954)

Uniform Building Code. Whitter, Calif. (5360 South Workman Mill Rd., Whitter 90601: International Conference of Building Officials, 1970

Uniform Building Code. Whitter, Calif. (5360 South Workman Mill Rd., Whitter 90601: International Conference of Building Officials, 1982

Uniform Building Code. Whitter, Calif. (5360 South Workman Mill Rd., Whitter 90601: International Conference of Building Officials, 1997

Vaughan, Ellen, and Jim Turner. "The value and impact of building codes."

Environmental and Energy Study Institute White Paper (2013).

Wight, James. Email to the Author, October 2, 2013

Wilcox, C., B. Nuttall, and T. Barnett. "Connection Details—Practicing Engineers and the Code." 2011 Structures Congress. 2011.

Yang, Q. Z., and Xingjian Xu. "Design knowledge modeling and software implementation for building code compliance checking." Building and Environment 39.6 (2004): 689-698.

APPENDIX A: METRIC DEVELOPMENT

New Engineer/New Code  Mid‐Level Senior Engineer Electronic Time (m) Electronic Time (m) Electronic Time (m)

SDI‐1 1.75 SDI‐1 1.3 SDI‐1 1

SDI‐2 3 SDI‐2 2 SDI‐2 1

MDI‐1 5 MDI‐1 3 MDI‐1 2

MDI‐2 10 MDI‐2 4 MDI‐2 3

MDI‐3 15 MDI‐3 2 MDI‐3 1

New Engineer/New Code  Mid‐Level Senior Engineer

Paper Time (m) Paper Time (m) Paper Time (m)

SDI‐1 2 SDI‐1 1.5 SDI‐1 1

SDI‐2 5 SDI‐2 2 SDI‐2 2

MDI‐1 10 MDI‐1 5 MDI‐1 3

MDI‐2 15 MDI‐2 7 MDI‐2 5

MDI‐3 20 MDI‐3 3 MDI‐3 1

Figure A.1: The different types of codes, levels of engineers and the time associated with the classifications of interconnectedness

APPENDIX B: SAMPLE GRAPHS - IBC CHAPTER 9

Figure B.2: Complete list of provisions within the IBC Chapter 9

Figure B.3: Complete intended hierarchical structure of the IBC Chapter 9 with associated edges

Figure B.4: Complete intended hierarchical structure of the IBC sub-section 903

Figure B.5: Complete intend hierarchical structure of the IBC sub-section 903 with all references.

APPENDIX C: SUPPORTING GRAPHS

Figure C.6: Chapter 5 of the ACI 318 1995 edition. The graph is a representation of the intended hierarchical structure.

Figure C.7: Chapter 5 of the ACI 318 1995 edition. The graph is a representation of the intended hierarchical structure as well as the references made within the Chapter to other sections of the

Code and other Codes.

Figure C.8: A representation of a code network. Colored dots represent codes.