News Updates - December 31, 2009
HB 3462 – Certification legislation - is getting completed in stages
The administrative rules to implement the changes to building official and inspector
certifications in House Bill 3462 are in their final stages. On December 16, 2009,
a public hearing was held to receive oral and written testimony regarding the adoption
of a new rule establishing the requirement of renewing inspector certifications every
three years. Other changes to OAR chapter 918, division 98 call for an Oregon Inspector
Certification (OIC) for all building officials, inspectors, and plan reviewers. Those
who were grandfathered in (Oregon Code Certification holders) when the OIC was developed
in 2005 will be issued an OIC by July 1, 2010 by the division at no charge. The application
and renewal fee will be set at $125 for a three year certification. The first renewal
cycle for all OICs will begin on Nov. 1, 2010 under these new rules. These new rules
take effect July 1, 2010.
The division plans to begin the second phase of implementing HB 3462 that creates
a pilot training program beginning in January. BCD will be soliciting members for
a committee to work on this portion of the legislation at the beginning of the new
year and hope to have local building department involvement.
We would like to ask for your help in the first steps of developing the pilot program
called for in HB 3462. The bill was designed to provide greater flexibility to jurisdictions
in staffing their building departments by the creation of specialized training certifications.
The division needs input from local building departments on the types of specialized
certifications that would provide the greatest benefit. Please consider the following
questions when examining your programs and determining how this new certification
program would be most helpful for you:
1. Are there inspection programs that you currently contract out that could be
serviced by your existing staff if they were to obtain additional training under
the specialized certification program? What programs and scope of work is normally
contracted out in your jurisdiction?
2. Instead of looking for fee increases to cover costs associated with contracting
out to provide required service levels, which certification areas could best help
you to use your existing staff to provide backup or in-house coverage for all your
Please give us your feedback on these questions and any other comments you would
like to include by contacting policy and technical services manager Chris Huntington
Status of 2010 OSSC Adoption
During the public comment period on the proposed 2010 Oregon Structural Specialty
Code (OSSC), the division received a request to extend the comment period. The division
extended the comment period to the close of business December 11, 2009 allowing additional
information to be submitted. Based on both the information received through the public
hearing and comment period, the division has additional code amendments to present
at the next Building Codes Structures Board meeting. The next board meeting is currently
scheduled for February 3, 2010. The additional code changes will be available in
the board packet in advance of the meeting. The division still anticipates the printed
and online versions of the 2010 OSSC will be available in early spring.
Manufactured Dwelling Installation Specialty Code
A new manufactured dwelling installation code is very close to adoption. The process
of revising the manufactured dwelling installation code, which originally started
over two years ago, but was delayed by new federal regulations and existing national
standards, is on track to finish up in early 2010. In the past four months the division's
Manufactured Structures Program has been very busy working with industry, local government,
and the Manufactured Structures and Parks Board to review and approve the code.
The current code is the 2002 Oregon Manufactured Dwelling & Parks Specialty Code
(MD&P) for manufactured dwelling installations. Since its adoption, only minor amendments
have been made to this code and it is being used to develop the 2010 Oregon Manufactured
Dwelling Installation Specialty Code (MDISC). The division hopes to achieve the following
goals with the 2010 MDISC:
- Stay within the statutory framework for manufactured dwelling installations.
- Align Oregon's code with federal installation requirements.
- Provide a uniform and consistent Chapter 1 (Administration).
- Separate manufactured dwelling park requirements from the installation code.
(The requirements in the 2002 MD&P will remain in effect for manufactured dwelling
The 2010 MDISC will be reduced down to the minimum requirements necessary for a
typical manufactured dwelling installation. There were certain requirements adopted
to meet HUD standards. Other provisions previously found in the 2002 MD&P, such as
alternate uses, changes in use, and alterations will be adopted by administrative
The new code will become effective April 1, 2010. Printed versions will be available
for purchase from the Oregon Manufactured Housing Association. BCD will have an online
version available on our Web site before the April effective date. Additionally,
the division will be offering code change classes for the new code, including an
training. Schedules and more information on this code change training will be announced
If you have any questions regarding this article please feel free to contact Albert
Endres at 503-378-5975 or firstname.lastname@example.org.
In our last newsletter we talked a lot about the ePermitting team creating the
base template tool, the Oregon permit Model (OPM), The OPM is used as the foundation
for developing individualized systems for participating cities and counties. Now
we want to continue that conversation and go into more detail about the steps to
create these unique systems. To create a system that meets a jurisdiction's individual
needs, the ePermitting team will carefully analyze and plan modifications to the
OPM template's configuration and workflow. Configuration is the process of modifying
the computer system to meet the permitting needs of an adopting city or county. Workflow
is the life-cycle and process of each permit or project determining what happens
at each stage of the process. Let's take a more in depth look at these parts of the
Configuring the system involves the careful analysis and review of items such as
those listed below, followed by the modification of the OPM to meet the jurisdiction's
needs. Items considered in configuration include:
- Collecting and reviewing the necessary data needed for a specific record or
application type. This could include items such as floor area, construction type,
occupancy group, school district, transportation district, or any other information
necessary to process a record or application.
- Determining what types of permits a city or county issues. The OPM will include
a standard set of Case Application Permits (CAP) or record types. However, this
list may need to be expanded or altered to meet the city or county's individual
- Including each city or county's fees in the system. Even with the standardized
fee methodology for some permit types, every city or county charges differing amounts
and those fees that have not been standardized may use unique calculation methods.
Furthermore, fees like system development charges are also included as part of
this project and they are truly unique to each city or county.
- Establishing the list of required inspections for each jurisdiction. While the
focus group has been working on developing a standardized list of inspections by
establishing inspection names and Interactive Voice Response (IVR) codes over the
last couple of months, there may be some unique inspections not included on that
list. Each of these inspections will need to be addressed individually.
- Evaluating system security and user interface. Every participating city or county
will need to identify which employees get to see and update what information. In
addition, the information shown on the various work screens or consoles can differ
from work section to work section. For example, a city or county might want a permit
technician to have a different view of the system than an inspector; and, a manager
or supervisor will likely have a different system view than either of those groups.
All of these decisions will need to be entered into the system.
Let's give you an example of what workflow is. Below you will find the basic process
used when designing a workflow, or life cycle, for a permit on a new single family
- Application acceptance
- Completeness review
- Plan review (which could include a concurrent review by building, planning, public
works departments, etc.)
- Permit issuance
- Required inspections
Throughout this life-cycle, situations must be identified and choices made to determine
what triggers the permit or project to progress to the next step in the process.
The specific data that is collected at each stage and at what point the process loops
back are all decision that need to be made. Each record or CAP type must have a workflow
associated with it that is established in the ePermitting system. While the ePermitting
team will provide a generic workflow for some record types, each city or county will
need to analyze the workflows for completeness and accuracy based on the needs of
their jurisdiction. Once necessary changes are identified, the generic models will
be modified to meet the city or county's specific needs.
As you can see, there is a lot that goes into making each system work properly
for a specific city or county. Even with the template, many individual pieces must
be added to complete the puzzle.
If you have questions or need more information please contact Lori Graham at email@example.com
Summary of enforcement cases presented
to the State Plumbing Board
Summary report: These cases were
resolved by the division's enforcement section without going to a contested case
hearing. No action was required by the State Plumbing Board.
Happy New Year
The Oregon Department of Consumer and Business Services Building
Codes Division wants to wish you the best in 2010. We hope your New Year sparkles!