The AIA State Government Network (SGN) gathered at AIA headquarters March 1 after joining other component leaders in the AIA Grassroots 2002 Government Affairs Day and Capitol Hill visits. Nearly 60 AIA members, component staff, and lobbyists representing 45 state components attended the meeting, which focused on core issues in state government facing the architecture profession. The network allows state components and their member-based government affairs committees to identify emerging and priority advocacy issues for architects.

AIA Codes Consultant David Collins, FAIA, gave the group the newest information about the unified building code and adoption updates from the states. The AIA Licensing Committee briefed participants on several hot licensure topics, including professional overlap, corporate practice, and digital signatures. Further discussions centered on security issues, liability concerns, taxes, and an overview of state budget and fiscal conditions.

Security
A working luncheon allowed participants to brainstorm ideas on how architects can provide resources and expertise on emerging security issues. They concurred that security is part of the design equation now and into the future. Participants mentioned that federal funds to provide project security enhancements might be available, but that these dollars may not be significant after other homeland security projects are funded. Participants also said state capital project budgets will suffer if they are cut to protect state revenue. They surmised that it would also result in lower corporate and individual tax collections from A/E firms.

Participants also said security design costs must be included as part of the project budget, not as add-ons as work progresses. They advocated that specific line items be placed in the budget before work starts. Advocacy of a strong, unified building code that employs security elements is a powerful message at this time, they said. The participants also indicated that although all architects may not be security experts themselves, their strength is knowing whom to bring to the table to make appropriate security decisions. Architects, they said, are the best players on the design/build team to handle this issue: they evaluate the whole picture and do not have a monetary stake in security products or upgrades.

SGN members also addressed the liability that architects may incur when working on security-improvement projects, or any project in which the security of a facility is compromised. They openly wondered if this would discourage architects from getting involved in security issues and what other risk management issues a more security-related practice would invite. For example, one participant asked, what happens if someone designs a parking garage, and then there is a security breach at the structure? Is the architect then liable? Participants expressed worry that failing to meet their community's expectations may result in a political and business liability.

Attendees reported that government officials responded very favorably to the AIA Building Security Through Design primer, which they presented to their local, state, and federal representatives. Many who had not made contact with their members of Congress during Grassroots or those who were unable to travel to Washington said they would contact their representatives and senators during upcoming district work periods. (See the reference sidebar for a link to the Congressional calendar.)

The SGN
The SGN was created in 1991 to increase government affairs outreach and legislative assistance. Meeting minutes will soon be posted on the Institute's MyAIA portal. In the meantime, AIA Government Affairs staff requests that all state components subscribe the State and Local Affairs team to their e-newsletters and fax alerts.

—Tracy F. Ostroff

Copyright 2002 The American Institute of Architects. All rights reserved.