Return to menu

Notes from

National Alliance Technology Task Force

November 15, 2001 - 1 p.m. to 5 p.m.

Washington Dulles Airport Marriott

 

A.     Attendees

The following organizations/governmental jurisdictions were represented:  (See Attachment A for representatives and contact information.)

 

American Institute of Architects

City of San Jose, California

Commonwealth of Pennsylvania

Fairfax County, Virginia

FIATECH

International Alliance for Interoperability

International Code Council

National Association of State Chief Information Officers

NCSBCS

National Governors Association

National Institute of Building Sciences

National Institute of Standards and Technology

 

B. Bob Wible, NCSBCS, gave an update on current activities of the National Alliance for Building Regulatory Reform in the Digital Age and the role of the Technology Task Force.

 

C. Greg Lindsay, NCSBCS, went over the goals, tasks, and milestones for the Task Force as set out in the Action Agenda established at the national forum and follow-up meeting of co-sponsors (see Attachment B). The purpose of this first meeting of the task force is to assemble a mission statement; identify the needs of the task force (information and resources); develop a preliminary plan, and identify issues needing to be resolved by other project committees.

 

D.     Representatives from the following organizations provided information on their current projects:

National Association of State Chief Information Officers - Cheryl Edwards, IT Architecture Issues Coordinator

International Alliance for Interoperability - Rich Geissler, Executive Director

FIATECH - Barbara Newland, Chief, Marketing & Membership

City of San Jose, California– Amal Sinha, Deputy Director/Chief Building Official

Fairfax County, Virginia– Stephen Garnier, Code Enforcement Coordinator

National Institute of Building Sciences– David Harris, President

 

E. The following list of issues were discussed as potential work products for the task force. Most can be categorized as “low hanging fruit”. This list will be sent out for members to prioritize. 

Near-term products (low hanging fruit)

·        Inventory of I.T. being used – what is out there and associated costs (HUD PATH initiative)

·        NASCIO architecture work product

·        Model legislation for Uniform Electronic Transactions (electronic signatures)

·        Federal e-government task force – Find out if it is relevant to this project.  (Mark Forman at OMB)

·        NCSBCS Streamlining initiative – case studies/models.  Focus on streamlining I. T. programs.

·        NCSBCS I. T. survey – Where are they in process; barriers encountered

·        Resources to look at procurement for a system, i.e., use of IFC’s. 

·        National model standardized application form

·        Summarize what is available elsewhere in the world and how it works.

 

Long-term products

·        Have a group provide alternative models to look at the building regulatory process in different ways.

·        How to rationalize (expedite)  the permit process  -- quality assurance  --public health and safety process.

 

F.  Other subjects discussed:

Identify who needs to be at this table, i.e., Mortgage Bankers Association (financial); Owners Alliance (headed by Bill Hoy); Realcom (Rich Geissler to talk with them); software association/companies.

Quantify “better, safer, and at less cost” .  This would provide the impetus for change.

 

G.     Date and Location of Next Task Force Meeting

IAI invited the Technology Task Force to a meet in Atlanta December 12.  Rich Geissler said he would host the meeting and provide demonstrations of IFC technlogy that would aid jurisdictions in implementing a program of receiving and approving commercial building plans.  These demonstratons would be made by special guests from Germany, England, and Singapore to present work being done in their countries to initiate such programs.  A show of hands indicated that five or six members might be able to attend.

The meeting adjourned at 5:15 p.m.

Appendix B

Members

  • Existing public and private sector partnerships and consortia
  • IT Forum sponsors, co-sponsors and participants 
  • Officials from code jurisdictions  
  • Goals - Technology Task Force  
  • Develop and maintain a mission statement  
  • Institute a system-level national architecture for the building regulatory environment  
  • Research ways to integrate IT in the the construction industry  
  • Share Outcome  
  • Component sharing repository  
  • Standards registry  
  • Committee Work Products
  • National secure database repository for building regulatory product environment

 

Short-term Tasks and Milestones:

l3 to 12 months

  • Compile listing of known technology solutions used in the building regulatory environment - Feb ‘02 
  • Produce comparison analysis of available solution - Feb ‘02  
  • Identify Interoperability needs and solutions - Nov ‘01 
  • Identify interface problems - Jan ‘02  
  • Define technical performance requirements - Dec ‘01

 

Long-term Tasks and Milestones

1 to 5 years

  • Develop of building element properties and requirements - Feb ‘03  
  • Develop hazard scenarios for use in simulations - May ‘03  
  • Develop simulation techniques - June ‘03  
  • Develop risk analysis techniques - May ‘03  
  • Predict outcomes and consequences of regulatory reform scenarios - June ‘04

 

Today’s Objective 

- Assemble a mission statement

- Identify the needs of the Technology Task Force
  • Information
  • Resources 

- Develop preliminary plan

  • Agenda
  • Schedule
  • Assignments  

- Identify issues needing to be resolved by other committees