On the agenda: Madras meeting — Data Center (Mar 17)

1. Meeting Materials
Documents:
CITY COUNCIL MEETING AGENDA 03-17-2026.PDF
CITY COUNCIL PACKET 03-17-2026 03-10-26_CC_PACKET.PDF

MADRAS CITY COUNCIL MEETING
Tuesday, March 10, 2026 at 6:00 PM
City Council Chambers, 125 SW “E” Street, Madras, OR 97741
Telephone (541) 475-2344 www.ci.madras.or.us
This meeting is open to the public. This agenda includes a list of the principal subjects anticipated to be considered
at the meeting. However, the agenda does not limit the ability of the Council to consider additional subjects.
Meetings may be canceled without notice. The chat feature in Zoom is only available during Public Comments
portions of the meeting. Zoom participants should use the “raise your hand” feature during these times to alert the
moderator that they would like to speak.
This meeting/event location is accessible. Sign and language interpreter services, assistive listening devices,
materials in alternate formats such as Braille, large print, electronic formats, language translations, or any other
accommodations are available upon advance request at no cost. Please contact the City Recorder at
[email protected] or 541-325-0302 no later than 48 hours in advance of the meeting. Providing at least 48
hours' notice will help ensure availability.

Join via Zoom:
https://us02web.zoom.us/j/2912614668?pwd=MIJ3ZzhOYzg0ZkhwOTZ0REgrWTFYdz09
Passcode: 5414752344
Join via teleconference:
From a cell phone: 971-247-1195
From a land line phone: 1-877-853-5257
Meeting ID: 291 261 4668#
Participant ID: #
Passcode: 541 475 2344#
I.

Call Meeting to Order

II.

Roll Call

III.

Changes/Additions to Regular Agenda

AGENDA

IV. Consent Agenda

All matters listed within the Consent Agenda have been distributed to every member of the City Council,
Commission, and/or Committee for reading and study, are considered to be routine, and will be enacted by
one motion. If separate discussion is desired, any item may be removed from the Consent Agenda and
placed on the Regular Agenda by request.

1.
V.

City of Madras - Accounts Receivable Report

Public Comments (Please limit to 3 minutes)

The Council, Commission, and/or Committee reserves the right to limit the number of speakers pertaining
to the same topic in the interest of meeting efficiency and expediency.

VI. Public Hearing(s)
1.

Page 1 of 2

Continued Public Hearing on Omnibus Development Code amendments, File: TA-25-1.
A. Open Public Hearing.
B. Declaration of Conflicts of Interest: Does any Commissioner/Councilor have any actual
economic conflict of interest to disclose?
C. Staff Report/Applicant Testimony.
D. Public Testimony.
E. Staff Comments.
Madras City Council Meeting

March 10, 2026

F. Deliberation (Motion to recommend approval, modification, denial, or continue the public
hearing to a date and time certain).
Nicholas Snead, Community Development Director
VII. Regular Agenda
1.

Repair AWOS Wind Indicator
Jeff Hurd, Public Works Director

2.

Authorization to submit State & Local Government Cybersecurity Grant.
Nicholas Snead, Community Development Director

3.

Designation of Administrative Approval Authority During City Administrator Vacancy
Keli Pollock, City Recorder

4.

Review and Approval of City Administrator Recruitment Position Profile
Keli Pollock, City Recorder

VIII. Additional Comments / Department Reports / Committee Reports
1.

If I Were Mayor Contest – Student Submission Review

IX. Executive Session
1.

ORS 192.660(2)(e) - To conduct deliberations with persons designated by the governing
body to negotiate real property transactions.
Note: Executive sessions are not open to the public and will not be held virtually.
Representatives of the news media wishing to attend must do so in person. No decisions are
made in Executive Session.

X.

Adjourn Meeting

Page 2 of 2

Madras City Council Meeting

March 10, 2026

rm
111,..111
TIIBCJTYOF

MADRAS CITY COUNCIL MEETING
Tuesday, March 10, 2026 at 6:00 PM
City Council Chambers, 125 SW “E” Street, Madras, OR 97741
Telephone (541) 475-2344 www.ci.madras.or.us

This meeting is open to the public. This agenda includes a list of the principal subjects anticipated to be considered
at the meeting. However, the agenda does not limit the ability of the Council to consider additional subjects.
Meetings may be canceled without notice. The chat feature in Zoom is only available during Public Comments
portions of the meeting. Zoom participants should use the “raise your hand” feature during these times to alert the
moderator that they would like to speak.
This meeting/event location is accessible. Sign and language interpreter services, assistive listening devices,
materials in alternate formats such as Braille, large print, electronic formats, language translations, or any other
accommodations are available upon advance request at no cost. Please contact the City Recorder at
[email protected] or 541-325-0302 no later than 48 hours in advance of the meeting. Providing at least 48
hours' notice will help ensure availability.

Join via Zoom:
https://us02web.zoom.us/j/2912614668?pwd=MIJ3ZzhOYzg0ZkhwOTZ0REgrWTFYdz09
Passcode: 5414752344
Join via teleconference:
From a cell phone: 971-247-1195
From a land line phone: 1-877-853-5257
Meeting ID: 291 261 4668#
Participant ID: #
Passcode: 541 475 2344#
AGENDA
I.

Call Meeting to Order

II.

Roll Call

III.

Changes/Additions to Regular Agenda

IV. Consent Agenda
All matters listed within the Consent Agenda have been distributed to every member of the City Council,
Commission, and/or Committee for reading and study, are considered to be routine, and will be enacted by
one motion. If separate discussion is desired, any item may be removed from the Consent Agenda and
placed on the Regular Agenda by request.

1.
V.

City of Madras - Accounts Receivable Report

Public Comments (Please limit to 3 minutes)
The Council, Commission, and/or Committee reserves the right to limit the number of speakers pertaining
to the same topic in the interest of meeting efficiency and expediency.

VI. Public Hearing(s)
1.

Page 1 of 2

Continued Public Hearing on Omnibus Development Code amendments, File: TA-25-1.
A. Open Public Hearing.
B. Declaration of Conflicts of Interest: Does any Commissioner/Councilor have any actual
economic conflict of interest to disclose?
C. Staff Report/Applicant Testimony.
D. Public Testimony.
E. Staff Comments.

Madras City Council Meeting

March 10, 2026

F. Deliberation (Motion to recommend approval, modification, denial, or continue the public
hearing to a date and time certain).
Nicholas Snead, Community Development Director
VII. Regular Agenda
1.

Repair AWOS Wind Indicator
Jeff Hurd, Public Works Director

2.

Authorization to submit State & Local Government Cybersecurity Grant.
Nicholas Snead, Community Development Director

3.

Designation of Administrative Approval Authority During City Administrator Vacancy
Keli Pollock, City Recorder

4.

Review and Approval of City Administrator Recruitment Position Profile
Keli Pollock, City Recorder

VIII. Additional Comments / Department Reports / Committee Reports
1.

If I Were Mayor Contest – Student Submission Review

IX. Executive Session
1.

ORS 192.660(2)(e) - To conduct deliberations with persons designated by the governing
body to negotiate real property transactions.
Note: Executive sessions are not open to the public and will not be held virtually.
Representatives of the news media wishing to attend must do so in person. No decisions are
made in Executive Session.

X.

Adjourn Meeting

Page 2 of 2

Madras City Council Meeting

March 10, 2026

CITY OF MADRAS
Request for Council Action

Meeting Date: March 10, 2026
To:

Mayor and City Council Members

From:

Jesse Chirukuri, Senior Account Analyst

Through:

Kate Knop, Finance Director

Subject:

City of Madras - Accounts Receivable Report
The City of Madras accounts receivable report for the airport and golf course
funds for January 2026.

TYPE OF ACTION REQUESTED:
Discuss
MOTION(S) FOR CONSIDERATION:
N/A
OVERVIEW:
The City of Madras accounts receivable (AR) aging totals for the airport and golf course.
STAFF ANALYSIS:
Staff continue communication efforts to collect airport and golf AR.
FISCAL INFORMATION:
No additional comments.
SUPPORTING DOCUMENTATION:
Airport & Golf Course AR for January 2026
STRATEGIC GOAL:
#4 - 3. Finance ensures fiscally responsible management of city funds.

Page 1 of 1

Request for Council Action

City of Madras
Airport and Golf Course Accounts Receivable Report
January 2026
Airport
Categories
Fuel
FIRE
Hanger
Heavy Hanger
AP Pads
Totals

Over 30 Days Over 60 Days Over 90 Days Over 120 Days Over 150 Days
$0.00
$0.00
$0.00
$0.00
$0.00
$0.00
$899.00
$75.00
$75.00
$0.00
$0.00
$2,530.73
$0.00
$0.00
$0.00
$0.00
$0.00
$400.00
$150.00
$100.00
$100.00
$1,400.00
$475.00
$1,124.00
$100.00
$100.00
$3,930.73
Comments
Hangars: Multiple customers have outstanding balances; the airport manager is following up.

AP Pads: Aircraft tie-down balances are pending; the airport manager is coordinating with customers.

Golf Course
Categories
Membership
Cart
Trail
Totals

Over 30 Days Over 60 Days Over 90 Days Over 120 Days Over 150 Days
$132
$897
$768
$520
$2,074
$20
$70
$70
$50
$170
$0
$0
$0
$0
$0
$152
$967
$838
$570
$2,244
Comments
Golf manager is working with customers to get the dues to current.

CITY OF MADRAS
Request for Council Action

Meeting Date: March 10, 2026
To:

Mayor and City Council Members

From:

Nicholas Snead, Community Development Director

Through:

Keli Pollock, City Recorder

Subject:

Continued Public Hearing on Omnibus Development Code amendments,
File: TA-25-1.

TYPE OF ACTION REQUESTED:
Approve
MOTION(S) FOR CONSIDERATION:
Direct the City Attorney and the Community Development Director to prepare the appropriate
adopting ordinance for the proposed Development Code amendments, as presented.
OVERVIEW:

The City Council has held public hearings (File: TA-25-1) on proposed amendments to the City’s
Development Code (Ch. 18). The purpose of the Code amendments is to:
1. Modernization for Data Centers and Advanced Tech
• Clearly permits technology-intensive and data-driven uses in I, AD, and LLI zones.
• Provides regulatory certainty for large-scale tech and traded sector employers.
2. Stronger Airport Compatibility
• Aligns terminology with FAA standards.
• Updates RPZ protections.
• Tightens glare, height, and interference controls.
3. Infrastructure and Phasing Discipline
• Requires utility and transportation analysis.
• Strengthens concurrency standards.
• Adds detailed phased site plan controls.
4. Clarified Landscaping Standards
• Regulates decorative rock use.
• Encourages fire-resistant and drought-tolerant plantings.
5. Refined Master Planning Framework
• Clarifies open space requirements.
• Strengthens procedural structure.
• Improves alignment with infrastructure plans.
Page 1 of 5

Request for Council Action

Staff will present the proposed Development Code changes at the March 10, 2025 City Council public
hearing. The proposed changes are summarized below. Staff will request that the City Council take
formal action to direct the City Attorney and the Community Development Director to prepare the
appropriate adopting ordinance for the proposed Development Code amendments, as presented.

STAFF ANALYSIS:

The City Council held public hearings on October 28, 2025, November 11, 2025, December 9, 2025,
and January 27, 2026. The October 28, 2025, public hearing was noticed in the Madras Pioneer on
August 18, 2025, and October 1, 2025. At each hearing, the City Council took formal action to continue
the public hearing to a date and time certain. In other words, the Council continued the hearings to
November 11, 2025, December 9, 2025, January 27, 2026, and February 24, 2026.
The proposed Development Code changes include:
1. New and Revised Definitions (Chapter 18.05)
The amendments significantly expand and clarify definitions related to airport operations and
technology/industrial uses:
Airport-Related Definitions:
• Adds or refines definitions for:
o Aeronautical Use
o Aeronautical Related Use
o Non-Aeronautical Use
o Airport
o Approach Surface
o Runway Protection Zone (RPZ) (replacing references to “Approach Safety Zone” in
several sections)
o Imaginary Surfaces
o Utility Runway
o Transitional Zones
• Aligns terminology more closely with FAA standards and airport planning documents (e.g.,
Airport Layout Plan, FAR Part 77 surfaces).
New Technology/Industrial Definitions:
• Adds:
o High-Tech Industrial
o Innovation and Data Use
o Technology and Data Services
• These definitions clearly establish categories for data centers, AI operations, cloud computing,
advanced manufacturing, and related tech uses.
Other Definitions:
• Adds definition of Decorative Rock for landscaping regulation.
• Refines Cottage Cluster and other minor terminology updates.
2. Expanded Allowances for Technology & Data Uses (I, AD, and LLI Zones)
A major theme of the amendments is expressly permitting data centers and advanced technology uses
in key employment zones.
Page 2 of 5

Request for Council Action

Industrial Zone (I) – 18.15.090:
• Adds as permitted uses (P):
o Technology and Data Services
o High-Tech Industrial
o Innovation and Data Use
• Retains 45-foot height limit (subject to Planning Commission and Council approval for greater
height).
• Maintains design review, landscaping, lighting, parking, and infrastructure standards.
Airport Development Zone (AD) – 18.15.120:
• Clarifies distinction between:
o Aeronautical & Related Uses
o Non-Aeronautical Uses
• Permits Technology and Data Services, High-Tech Industrial, and Innovation and Data Use in
designated subzones.
• Reinforces FAA compliance requirements.
• Updates height standards to ensure no penetration of airport imaginary surfaces.
• Updates glare and electromagnetic interference standards.
• Clarifies that uses must comply with Airport Layout Plan designations.
•
Large Lot Industrial (LLI) – 18.15.130:
• Adds Technology and Data Services, High-Tech Industrial, and Innovation and Data Use as
permitted uses (subject to subzone limitations).
• Reinforces airport compatibility and FAA compliance.
• Maintains:
o 50-acre minimum lot size (until traded sector use established)
o 45-foot max height or FAA-controlled height
• Refines master plan requirements, infrastructure analysis, and review procedures.
Overall effect:
The code now clearly supports data centers and advanced tech manufacturing as outright permitted
uses in primary industrial and airport-related employment areas.
3. Airport Overlay & RPZ Updates (18.15.140):
• Replaces “Approach Safety Zone” terminology with Runway Protection Zone (RPZ).
• Clarifies permitted and conditional uses within the RPZ.
• Tightens compatibility standards to prohibit:
o Electrical interference
o Bird strike hazards
o Light glare conflicts
o Uses attracting large numbers of people
• Aligns overlay language with FAA standards and the Airport Layout Plan.
4. Landscaping Revisions (18.25.170):
Decorative Rock Regulations
• Decorative rock may count toward landscaping but:
Page 3 of 5

Request for Council Action

o Hardscape + decorative rock may satisfy no more than 65% of required landscaping.
o Decorative rock alone may not exceed 50% of required landscaped area.
• Must be:
o 1–3 inches in size
o Natural/earth-tone colors
o Installed over weed barrier
o Maintained weed-free
• Construction aggregates (road base, decomposed granite) prohibited.
Other Updates
• Clarifies plant spacing and coverage standards.
• Encourages drought-tolerant and fire-resistant landscaping.
• Allows stormwater facilities to count if landscaped.
• Adds formal waiver/modification procedure (Type II).
5. Outdoor Lighting Update (18.25.160)
• Updates language to reference the Runway Protection Zone (RPZ).
• Prohibits lighting projecting into runway, taxiway, or RPZ unless required for safe air travel.
6. Site Plan Review Revisions (18.40.020):
Significant procedural refinements:
• Expands submittal requirements:
o Utility demand analysis (water, sewer, stormwater, power, telecom, gas)
o Transportation assessment or TIA
o Phasing plan (for multi-building projects)
• Clarifies Site Plan Committee authority.
• Adds detailed phased site plan approval process:
o 1-year expiration for first phase
o 5-year total approval limit
o Strict expiration if phases lapse
• Clarifies approval criteria and condition authority.
This strengthens infrastructure concurrency and phasing enforcement.
7. Large-Scale Building Standards (18.40.040):
• Reaffirms applicability to buildings over 30,000 sq. ft.
• Maintains 150,000 sq. ft. cap in most zones except I, LLI, AD, and OS/PF.
• Ensures large industrial/tech facilities are not subject to retail-style size caps in industrial
zones.
8. Master Planned Development Changes (18.55):
Key updates include:
• Expanded submittal requirements:
o Utility infrastructure analysis
o Phasing schedule
o Traffic study
• Clarifies open space requirements:
o 8% residential
Page 4 of 5

Request for Council Action

o 5% nonresidential
o No open space required for purely industrial master plans
• Clarifies approval process:
o Type II if no zoning/use changes
o Type III if changes proposed
• Adds phasing initiation requirements tied to plat recording.
• Clarifies housing mix requirements for large residential master plans.
9. Decision Classification Updates (18.80.090):
• Clarifies when master plans are Type II vs. Type III.
• Confirms Director discretion to elevate decisions.
• Refines appeal pathways.
FISCAL INFORMATION:
N/A
SUPPORTING DOCUMENTATION:
TA-25-1 Omnibus Amendments
STRATEGIC GOAL:
Economic Development

Page 5 of 5

Request for Council Action

EXHIBIT A
AMENDMENTS
Language added
Language deleted

18.05.030

Definitions

Aeronautical Use - means any use that involves, makes possible, or is required for the
operation of aircraft or that contributes to or is required for the safety of such operations. The
term includes, but is not limited to: air taxi and charter operations; scheduled or nonscheduled
air carrier services; pilot training; aircraft rental and sightseeing; aerial photography; crop
dusting; aerial advertising and surveying; aircraft sales and service; aircraft storage; sale of
aviation petroleum products; repair and maintenance of aircraft; sale of aircraft parts;
parachute activities; ultralight activities; sport pilot activities; and military flight operations.
“Aeronautical Related Use” means a use that benefits from the proximity to the airport and
airport businesses. Uses may include aviation manufacturing, aviation maintenance, storage, or
businesses that support activity on the airport.
“Airport” means a tract of leveled land where aircraft can take off and land, usually equipped
with hard surfaced landing strips, a control tower, hangars, and accommodations for
passengers and cargo.
(a) Approach Safety Zone. A surface longitudinally centered on the extended runway centerline
and extending outward and upward from each end of the primary surface. The inner edge of
the approach surface is the same width as the primary surface and extends to a width of:
(i) 1,250 feet for a utility runway having only visual approaches;
(ii) 1,500 feet for a runway other than a utility runway having only visual approaches;
(iii) 2,000 feet for a utility runway having a nonprecision instrument approach; and
(iv) 3,500 feet for a nonprecision instrument runway other than utility, having visibility
minimums greater than three-fourths (3/4) of a statute mile.
The airport approach safety zone extends for a horizontal distance of 5,000 feet at a slope of 20
feet for each foot upward (20:1) for all utility and visual runways and 10,000 feet at a slope of 34
feet for each one foot upward (34:1) for all nonprecision instrument runways other than utility.
“Approach Surface” means a surface longitudinally centered on the extended runway centerline
and extending outward and upward from each end of the primary surface. An approach
surface is applied to each end of each runway based upon the type of approach available or
planned for that runway end.

Page 1 of 37

(i) The inner edge of the approach surface is the same width as the primary surface and it
expands uniformly to a width of: (A) 1,250 feet for that end of a utility runway with only visual
approaches. (B) 1,500 feet for that end of a runway other than a utility runway with only visual
approaches. (C) 2,000 feet for that end of a utility runway with a non-precision instrument
approach. (D) 3,500 feet for that end of a non-precision instrument runway other than utility,
having visibility minimums greater than three-fourths statute mile. (E) 4,000 feet for that end of
a non-precision instrument runway, other than utility, having a non-precision instrument
approach with visibility minimums as low as three-fourths statute mile. (F) 16,000 feet for
precision instrument runways.
(ii) The approach surface extends for a horizontal distance of: (A) 5,000 feet at a slope of 20 to 1
for all utility and visual runways. (B) 10,000 feet at a slope of 34 to 1 for all non-precision
instrument runways other than utility. (C) 10,000 feet at a slope of 50 to 1 with an additional
40,000 feet at a slope of 40 to 1 for all precision instrument runways.
(iii) The outer width of an approach surface to an end of a runway will be that width prescribed
in this subsection for the most precise approach existing or planned for that runway end.
…
(f) Imaginary Surfaces. Those imaginary areas in space which are defined by the airport
approach safety runway protection zone, transitional zones, horizontal zone, clear zone, and
conical surface and in which any object extending above these imaginary surfaces is an
obstruction.
…
(l) “Runway Protection Zone” (RPZ) means an area off the runway end to enhance the protection
of people and property on the ground. The Runway Protection Zone is trapezoidal in shape and
centered about the extended runway centerline. The RPZ dimension for a particular runway
end is a function of the type of aircraft and approach visibility minimum associated for that
runway end.
(a) The RPZ extends from each end of the primary surface, as defined in
Attachment 1, Section 10, for a horizontal distance of:
(A) 1,000 feet for all utility and visual runways.
(B) 1,700 feet for all non-precision instrument runways other than utility;
(C) 2,500 feet for all precision instrument runways.
(l) (m) Transitional Zones. Extended one foot upward for each seven feet outward (7:1),
beginning on each side of the primary surface, which point is the same elevation as the runway
surface, and from the sides of the approach surfaces thence extending upward to a height of
150 feet above the airport elevation (horizontal surface).
(m) (n) Utility Runway. A runway that is constructed for and intended to be used by propellerdriven aircraft of 12,500 pounds maximum gross weight or less.

Page 2 of 37

“Decorative Rock” means clean, washed, or natural stone material such as river rock, crushed
basalt, or other similar materials that are visually appealing, durable, and intended for
landscaping purposes. Decorative rock does not include construction-grade aggregate or
aggregates otherwise used for construction.
Dwelling” means a building or part thereof designed for and/or used for residential occupancy
and containing one or more dwelling units.
…
(e) “Cottage cluster” means a grouping of cottages with a common courtyard dwelling units that
are detached or attached in subgroupings of up to four units per subgroup in any configuration
and have a common courtyard.
…
“High-Tech Industrial” means a low-impact industrial use focused on the research,
development, testing, or assembly of high-technology products or systems, including software,
electronics, robotics, biotechnology, and telecommunications. Activities may include limitedscale fabrication, clean rooms, laboratories, and technical offices. Operations are typically
conducted indoors.
“Innovation and Data Use” means a flexible land use category intended to accommodate
emerging technology uses, such as artificial intelligence operations, cloud-based computing,
digital media processing, and advanced data analytics. Uses may include data centers,
collaborative workspaces, and other technology-supportive facilities.
“Non-aeronautical Use” means any use of airport land that is not related to aeronautical
purposes. This includes activities such as storing nonaeronautical items in facilities designated
for aeronautical use, which must comply with FAA regulations. Specifically, non-aeronautical
use may include storage of vehicles, maintenance activities, or other uses that do not interfere
with the aeronautical utility of the hangar or airport facilities.
“Technology and Data Services” means a facility primarily engaged in the operation,
management, and maintenance of computer servers, storage systems, and digital networking
equipment used for data processing, storage, and distribution. This includes data centers,
server farms, cloud computing facilities, and similar operations. Facilities may include ancillary
office space, power supply and cooling systems, and security infrastructure.

Page 3 of 37

18.15.090 Industrial (I).
(1) Purpose. The purpose of the Industrial Zone is to fulfill the industrial and economic
development policies of the Madras Comprehensive Plan and support a diverse economy
in a business-friendly environment. The zone is intended to provide suitable locations for a
range of light and heavy industrial uses and jobs in the core economic sectors of
agricultural and mining industries, aviation and aeronautics, trucking and transportation,
warehousing, manufacturing of wood, high-tech electronics, and other products. Industrial
Zone development standards are intended to guide orderly development and provide
appropriate design elements to enhance the community and create a quality environment
for employees.
(2) Uses.
(a) Types of Uses. For the purposes of this section, there are three types of uses:
(i) A permitted use (P) is a use which is permitted outright subject to site plan approval and
to all of the applicable provisions of this section. If a use is not listed as a permitted use, it
may be held to be a similar unlisted use under the provisions of MDC 18.80.320.
(ii) A conditional use (C) is a use which must be approved at the discretion of the Planning
Commission and subject to site plan approval. The approval process and criteria are set
forth in Chapter 18.65 MDC. If a use is not listed as a conditional use, it may be held to be a
similar unlisted use under the provisions of MDC 18.80.320.
(iii) A prohibited use (X) is one which is expressly prohibited in the zone. In addition, uses
not specifically listed as permitted or conditional in MDC Table 18.15.090-1 or deemed to
be similar uses pursuant to MDC 18.80.320 are also prohibited.
(b) Use Table. A list of permitted, conditional, and prohibited uses in the Industrial Zone is
presented in MDC Table 18.15.090-1.
Table 18.15.090-1. Uses in the Industrial Zone (I)
Use

Type of Use (P, C, X)

Electronics firms and high-tech industry

I

Manufacturing and production, secondary processing,
fabricating, assembly, processing, packaging or storage,
repairing, distribution, and warehousing of the
following:
Wood products and secondary wood products
Steel and structural steel products, foundries, and
machine shops

Page 4 of 37

I

P

I

ID
P

I

P

D
P

I

Food processing, including canning, freezing, drying,
dairy products and similar food processing and
preserving, and beverage bottling facilities, but
excluding processes which involve the slaughter of
animals
Textile mill products, including apparel and other
finished products made from fabrics and similar
materials
Recreation and sporting goods equipment

P

□
P
P

Furniture and fixtures, including retail wood products

P

Printing and publishing and allied industries

P

Rubber and miscellaneous plastics

P

Leather and leather goods, excluding a tannery

P

Cement, glass, clay, and stone products

P

Fabricated metal products

P

Electrical and electronic equipment, machinery, and
supplies, but excluding batteries
Energy-related products
Measuring, analyzing, and controlling instruments;
photographic, medical, dental, orthopedic and optical
goods; watches and clocks
Freight terminals, including loading docks, storage,
warehousing and wholesale distribution, cold storage
lockers, and commercial storage facilities
Experimental, research, testing, or development
facilities
Warehouse and freight movement, transportation
terminals, trucking and freight yards
Corporation headquarters and business offices directly
related to industry
Aircraft service, maintenance, and aviation-related
industry
Public or semi-public uses, including fire, police, or
other governmental buildings
Public utility facilities (does not include communication
towers)
Automotive repair, body and fender works, paint, and
upholstery shops

Page 5 of 37

D
P

I

P

I

□
□
P

P

D
D
D
D
D
D
D
P
P
P
P
P
P
P

Lumber yards and building material yards; contractor’s
yards
Ancillary uses (i.e., deli, tavern, mini-market, food carts
in accordance with City standards, and retail sales
subordinate to a permitted use) must:
Be comprised of less than 30% of the total square
footage of a building located in the Industrial zoning
district; and
Be secondary to the primary use of the building; and
Be primarily for the use and convenience of the
employees who work in the industrial area
Call centers
Building roof and wall-mounted antennas for cellular,
personal communications service, and similar radio
services
Marijuana production facility, marijuana processing
facility, marijuana wholesale
Marijuana businesses must meet the applicable
requirements of MDC 18.30.140.
Industrial hemp processing and Production
Industrial hemp uses must meet the applicable
requirements of MDC 18.30.150.
Lumber yards and building material yards; contractor’s
yards
Technology and Data Services
High-Tech Industrial
Innovation and Data Use
Incidental and necessary services such as child care
facilities and recreational facilities for persons working
in the Industrial zoning district, when conducted within
an integral part of a main structure and having no
exterior display or advertising
Asphalt, redi-mix operations, concrete or concrete
products manufacturing, including storage yards
Communication towers (see MDC 18.30.130)
Chemical or glue manufacturing or storage, including
farm chemicals
Reduction, refining, smelting, or alloying of metals,
petroleum products, or ores
Page 6 of 37

D
P

□
□
P

I

D
I

P

I
I

□
P

D
D
D
D
P

I

P

I

P

I
I
I

-P I
-P I
-P I
C

D
D
D
C

I

C
C
C

I

Processing of recycled materials

C

Vehicle storage yards or wrecking yards

C

Explosives manufacturing or storage

X

Garbage, offal, or dead animal reduction or dumping

X

Residential

X

Housing

X

(3) Design Review. All industrial development is subject to the Design Review Standards.
(4) Outdoor Storage. Except for storage of large-scale and bulky products such as lumber
and steel pipe, outside storage areas must be obscured from sight from the primary public
street serving the development by a six-foot sight-obscuring fence, decorative wall, or
landscaping that obscures the materials being stored.
(5) Lot Size Requirements.
(a) The minimum lot area is 5,000 square feet.
(b) The minimum lot width is 50 feet.
(6) Setback Requirements. None, unless:
(a) Front and Rear Setbacks. The minimum depth of a proposed structure from the front or
rear setback is 10 feet where abutting a residential zone.
(b) Side Setbacks. The minimum depth of a proposed structure from a side setback is five
feet where abutting a residential zone.
(c) Corner Setback. For a lot with more than one property line abutting a street, proposed
structures must be at least 10 feet from the property lines.
(7) Height of Building. No structure may exceed a height of 45 feet without prior
authorization from the Planning Commission and City Council.
(8) Design Review. All development in the I Zone must comply with the Design Review
Standards and, as applicable, the supplemental standards in MDC 18.40.040.
(9)(8) Parking Regulations. Parking must be provided in accordance with the requirements
of MDC Table 18.25.050-1 in MDC 18.25.050 and the requirements of MDC 18.25.040
through 18.25.070.

Page 7 of 37

(10)(9) Sanitation Regulations. Before any structure receives a certificate of occupancy, it
must be connected to the City sewer system where the structure is within 300 feet of an
existing City sewer.
(11)(10) Water Regulations. Before any structure receives a certificate of occupancy, it must
be connected to the City water system unless authorized by the City for connection to an
adjoining water system.
(12)(11) Lighting. All lighting must comply with the outdoor lighting standards.
(13)(12) Landscaping. All landscaping must comply with the landscaping standards. [Ord.
933 § 3.9, 2019.]

18.15.120

Airport Development Zone (AD).

(1) Purpose. The purpose of the Airport Development Zone is to provide land adjacent to
airport facilities for future commercial and industrial uses that may be dependent on air
transportation. The permitted uses in the AD zone include common airport activities such
as hangar development, FBO services, and fuel storage. Several compatible Non-Aeronautical
uses such as manufacturing, offices, warehousing, agricultural processing/storage, call centers,
High-Tech Industrial, and data and related and supportive technology uses are also allowed in
the zone.
(2) Permitted Uses. Permitted uses in the AD Zone are those identified in Table 18.15.120 below.
(a) Air cargo terminals.
(b) Aircraft sales, repair, service, storage, and schools related to aircraft operations, and
facilities essential for the operation of airports, such as fuel storage, hangar use, and fixed
base operator (“FBO”) offices.
(c) Terminals (passenger – air, taxi, and bus).
(d) Public and semi-public buildings, structures, and uses essential to the welfare of an
area, such as fire stations, pump stations, and water storage.
(e) Ancillary uses with a total floor area no larger than 1,000 square feet.
(f) Uses where the ongoing operations must be directly dependent upon and associated
with the airport.
(g) Assembly and manufacture of goods.
(h) Assembly, repair, and storage of heavy vehicles and machinery.
(i) Storage and processing of agricultural products.
(j) Warehouse and freight terminal operations.
(k) Professional offices.
(l) Public utility facilities.
(m) Call centers.
Table 18.15.120
Use
AD Zone
Aeronautical & Related Uses1:
Air cargo terminals
P
Page 8 of 37

Aircraft sales, repair, service, storage, and schools related to aircraft
operations, and facilities essential for the operation of airports,
such as fuel storage, hangar use, and fixed base operator (“FBO”)
offices.
Terminals (passenger – air, taxi, and bus)

P

P
P
P

Ancillary uses with a total floor area no larger than 1,000 square
feet.
Uses where the ongoing operations must be directly dependent
P
upon and associated with the airport.
Assembly and manufacture of goods related to aviation
P
Assembly, repair, and storage of heavy vehicles and machinery for
P
aviation purposes
Communication towers to support aeronautical uses
P
Warehouse and freight terminal operations related to aviation
P
Professional offices related to aviation
P
Public Utility Facility (does not include communication towers)
P
1
Non-Aeronautical Uses :
Call centers
P
Public and semi-public buildings, structures, and uses essential to
P
the welfare of an area, such as fire stations, pump stations, and
water storage.
Storage and processing of agricultural products.
P
Technology and Data Services
P
High-Tech Industrial
P
Innovation and Data Use
P
Public Utility Facility (does not include communication towers)
P
1: Aeronautical and Related Uses are permitted in areas designed in the map attached to
Ordinance No. 977 as Exhibit B as either “Aeronautical Use Only Subzone” or “Aeronautical
and Non-Aeronautical Use Subzone”. Non-Aeronautical Uses are only permitted in areas
designated in the foregoing map as “Aeronautical and Non-Aeronautical Use Subzone”.
2: Subject to 18.30.130
(3) Conditional Uses. None.
(4) Limitations of Use. In the AD Zone, the following conditions shall apply:
(a) Liquid and Solid Wastes. Storage of animal, vegetable, or other wastes which attract
insects, rodents, or birds or otherwise create a health hazard is prohibited.
(b) Discharge Standards. Emissions of smoke, flying ash, dust, vapor, gases, or other forms
of air pollution that may cause nuisance or injury to human, plant, or animal life, or to
property, or that may conflict with any present or planned operations of the airport are
prohibited.
Page 9 of 37

(5) Lot Area Requirements.
(a) Minimum street frontage of lots: 50 feet.
(6) Setback Requirements. None, except:
(a) No building may be closer to a farm zone than the height of the building in the AD
Zone. 20 feet or the height of the structure, whichever is greater, from all abutting
properties or rights-of-way
(7) Height of Building.
(a) Maximum height: Two stories or 30 feet, whichever is less, if not equipped with a
sprinkler system. Three stories or 45 feet or a height that does not penetrate any airport
imaginary surfaces, whichever is less, if equipped with sprinkler system approved by the
Fire Marshal. Structures on the airport property necessary that are for Aeronautical Uses
the operation of the airport may be approved for a greater height as part of site plan
approval and subject to FAA approval.
(8) Glare and Electromagnetic Interference.
(a) Building materials must not produce glare which may conflict with any present or
planned operations of the airport, as permitted by the Federal Aviation Administration.
(b) No use may produce electromagnetic interference which may conflict with any present
or planned operations of the airport, as permitted by the Federal Aviation Administration.
(9) Design Review. All development in the AD Zone is subject to the Design Review Standards
and, as applicable, the supplemental standards in MDC 18.40.040.
(10) Parking Regulations. (Requirements of MDC 18.25.040 through 18.25.070 also apply).
(a) Site plan(s) submitted with an application for a building permit must include a parking
plan which shows the location and number of parking spaces, circulation patterns, and
ingress and egress provisions.
(b) All industrial and commercial uses within an Airport Development Zone must comply
with MDC Table 18.25.050-1.
(c) All parking lots must have an all-weather surface.
(d) Adequate provisions for safe and convenient circulation, ingress and egress must be
provided. All development in the AD Zone is subject to MDC 18.25.040 to 18.25.070

and 18.25.090

(11) Sanitation Regulations. Before any structure receives a certificate of occupancy, it must be
connected to the City sewer system where the structure is within 300 feet of an existing City
sewer.
(12) Water Regulations. Before any structure receives a certificate of occupancy, it must be
connected to the City water system unless authorized by the City for connection to an adjoining
water system.
Page 10 of 37

(13) Flood Hazard Areas. Any structure proposed to be located in the flood hazard area must
meet the standards of the Federal Emergency Management Agency (FEMA) and Chapter 18.45
MDC.
(14)(13) Lighting. All lighting must comply with the outdoor lighting standards in MDC 18.25.160
and the applicable Federal Aviation Administration regulations.
(15)(14) Landscaping. Landscaping must comply with the landscaping standards.
(16)(15) Federal Aviation Administration. Any use or development in the AD Zone must meet all
standards as set forth by the Federal Aviation Administration.
[Ord. 933 § 3.12, 2019.]

Page 11 of 37

18.15.130
Large lot industrial (LLI).
(1) Purpose. The Large Lot Industrial Zone is intended to provide opportunities for the
development of traded sector uses and implement the Central Oregon Regional Large Lot
Industrial Needs Analysis.
(2) Permitted Uses.
(a) Allowed Uses. Uses allowed in the LLI Zone are listed in Table 18.15.130-1, which
includes uses permitted outright (P), uses permitted as accessory to the primary permitted
use (A), uses permitted conditionally (C), and prohibited uses (X). The Planning
Commission may approve uses not listed in the table in accordance with MDC 18.80.320.
Table 18.15.130-1. Allowed Uses
Use

Review

1. Traded sector uses.

P

2. Subordinate industrial uses that support a primary traded sector use
located in the LLI Zone.

P(1)

3. Service commercial and retail uses.

P(1)

4. Public or semi-public uses including municipal, police, fire, other related
governmental uses and buildings.

P

5. Temporary uses subject to MDC 18.30.010.

P

Technology and Data Services

P(2)

High-Tech Industrial

P(2)

Innovation and Data Use

P(2)

Public Utility Facility (does not include communication towers)

P(2)

Communication Tower

C(3)

6. Residential Uses

X

1: These uses are not permitted until a traded sector use is established and can only be sited in an
area subject to an approved LLI master plan.
2: These uses shall only be permitted in Non-Aeronautical areas as identified in the City’s
current Airport Layout Plan, except as otherwise allowed herein. are only permitted in areas
designated on the map Ordinance No. 977 as Exhibit B as “Aeronautical and Non-Aeronautical
Use Subzone”.
3: Subject to 18.30.130

(3) Development Standards. The following development standards apply to all
development within the Large Lot Industrial (LLI) Zone. These standards ensure that the
public health, safety and general welfare are protected and the general interest of the
public is served. The standards provide for originality, flexibility and innovation in site
Page 12 of 37

planning and development to promote traded sector uses. Development in the LLI Zone
shall comply with the industrial design review standards in MDC 18.40.030. Uses in the LLI
zone also are subject to the development standards in Table 18.15.130-2. When there are
differences between standards in MDC 18.40.030 and Table 18.15.130-2, the standards in
Table 18.15.130-2 shall apply.
Table 18.15.130-2. LLI Development Standards
Standard

Unit

1. Lot Standards
a. Minimum Size

50 acres1

b. Maximum Size

None

c. Street Frontage

50' minimum, unless otherwise approved by
the City of Madras Public Works Director

2. Site Development
a. Setbacks
1. Front Minimum

20' or height of the structure, whichever is

2. Front Maximum

None

3. Side

None, unless the lot or parcel abuts a
residential or exclusive farm use zone, in
which case the setback shall be 50'

4. Rear

None, unless the lot or parcel abuts a
residential or exclusive farm use zone, in
which case the setback shall be 50'

greater

b. Lot Coverage
1. Maximum

85% of the property or lease area

2. Landscaping

10% minimum. Natural features including,
but not limited to, jurisdictional wetlands,
rock outcroppings, and Goal 5 resources
may be used to meet landscaping
requirements, but may not be substituted
for landscape in parking areas, building
frontages, and entryways. Natural features
need not be irrigated but must be
maintained for their functional condition
and to limit wildfire danger to adjoining
properties.

c. Parking

The number of off-street parking spaces
shall be consistent with Table 18.25.050-1.
Page 13 of 37

Standard

Unit

d. Buildings
1. Height

The maximum building height shall be 45' or
a height that does not penetrate an airport
imaginary surface, whichever is less unless

there are specific compelling needs related
to the manufacture or fabrication of goods
and services related to a traded sector use
or a supporting use that necessitate a
deviation from this limit. In no case shall the
height of a building exceed the
requirements of the Federal Aviation
Administration.
2. Orientation

Buildings shall be oriented to the street or to
a primary drive aisle.

e. Outdoor Storage

Outdoor storage areas shall be sited out of
public view or behind a sight-obscuring
fence.

1: The minimum lot size is fifty (50) acres until such time as a traded sector use is
established. After a traded sector use is established, the remaining land within the LLI
master planned area may be divided or reconfigured to accommodate supporting
industrial and commercial uses. The minimum lot size shall be one acre for supporting
industrial and commercial uses.
(4) Other Requirements. All development in the LLI Zone is subject to compliance with the
following special regulations:
(a) Aviation Regulations. Development applications must comply with applicable Federal
Aviation Administration (FAA) regulations concerning building heights, lighting, emissions,
water features, and other land development and use limitations. The Madras Community
Development Director shall be consulted to establish the list of applicable FAA
regulations.
(b) Floodplains. Development in a floodplain must meet Federal Emergency Management
Agency (FEMA) and related City Zoning Ordinance regulations for development in identified
hazard areas.
(c) All land uses and development in the LLI Zone shall be consistent with the following
plans:
(i) The current Madras Municipal Airport Master Plan.
Page 14 of 37

(ii) The current City of Madras Wastewater Master Plan.
(iii) The current City of Madras Transportation System Plan.
(iv) The current Industrial Site Readiness Plan.
(db) Natural Features. Natural features including, but not limited to, jurisdictional
wetlands, rock outcroppings, and Goal 5 resources shall not be developed.
(e) Master Development Plan. Each traded sector use within the LLI Zone on a site ten (10)
acres or larger must first prepare and secure approval for an LLI master plan meeting the
requirements of this section. Subsequent site plan applications within the LLI master
planned area must either adhere to the approved LLI master plan or submit an amendment
to the LLI master plan.
(i) Required Elements.
(A) Development Narrative. The applicant shall supply a narrative describing the proposed
traded sector use, site needs, the area to be included within the LLI master plan, and any
other development proposed or contemplated within the proposed master plan area.
(B) Master Plan Map. The applicant shall provide a map of the master planned area
showing the proposed configuration of lots within the master planned area, the location of
proposed uses, the location of natural features to be designated as protected open space,
and the configuration of streets, driveways, and other transportation facilities. The master
plan map shall require an amendment if a different use, transportation layout, lot
configuration, or other significant deviations are proposed.
(C) Street Connectivity and Trail Networks. A transportation plan for local streets, bicycle
routes, pedestrian paths, and other transportation facilities within the LLI master planned
area shall be prepared. The transportation plan shall be consistent with both the City and
County transportation system plans, adopted as part of their respective comprehensive
plans, and shall provide connections to planned or existing transportation facilities on
properties adjacent to the LLI master planned area.
(D) Utility Needs Analysis. The plan shall include an analysis of the anticipated utility
demand for all planned development in the LLI master planned area for wastewater,
stormwater, potable water, power, telecommunications, natural gas. The applicant shall
also prepare a utility plan setting forth the utility infrastructure, with locations and
specifications meeting the Public Improvement Standards, necessary to support
development proposed as part of the LLI master plan.
(E) Transportation Analysis. The applicant shall submit a transportation impact analysis
consistent with the requirements set forth in the TSP demonstrating that the proposed
Page 15 of 37

development can be safely and efficiently served by existing or proposed transportation
facilities.
(ii) Approval Criteria.
(A) The uses proposed are permitted within the LLI Zone.
(B) Proposed lots within the LLI master planned area meet the development standards in
Table 18.15.130-2.
(C) There is adequate capacity in existing facilities (water, sewer, stormwater, and
transportation), or sufficient upgrades or new facilities are proposed, to serve proposed
development within the LLI master planned area.
(D) The LLI master plan is consistent with the requirements in subsection (4)(a) through (c)
of this section.
(iii) Review Procedure. The LLI master plan shall be reviewed at a public hearing before
the Planning Commission, who will make a final decision. Amendments to the LLI master
plan that do not create additional lots, affect the amount of designated open space, or
increase the overall intensity of development permitted under the LLI master plan may be
approved administratively by the Community Development Director. Any other
amendments, or at the election of the Community Development Director for changes
subject to administrative review, shall follow the procedure for adoption of the LLI master
plan. The approval criteria for a modification shall be limited to those approval criteria for
the LLI master plan that require different findings on account of the proposed modification.
(iv) Conditions of Approval. The City may impose any conditions of approval necessary to
achieve compliance with the approval criteria or to otherwise protect the health, safety,
and welfare of the community.
(v) Subsequent Development. Any structures developed or modified (with the exception of
incidental accessory structures such as sheds, utility enclosures, etc.), change of use, or
outdoor use proposed within the master planned area LLI site shall be subject to site plan
approval pursuant to Section 4.8 and shall be evaluated for compliance with Section 4.8,
the LLI approved master plan if any, and the standards set forth in this section. Partition,
subdivision, or property line adjustment approvals will also be required to divide or
reconfigure the lots within the LLI site subject to any master planning approval requirements
in MDC 18.55.010(2) master planned area.
(fe) No land zoned LLI may be rezoned to another City zone within ten (10) years of its
initial LLI designation.

Page 16 of 37

(5) Design Review. Development in the LLI Zone shall comply with the design review
criteria for industrial development set forth in MDC 18.40.030 and, as applicable, the
supplemental standards in MDC 18.40.040.
(6) Conditions of Approval. In addition to any conditions of approval imposed as part of
LLI master plan, site plan, conditional use, or any other concurrent approval, the following
shall be mandatory conditions of approval for all development and uses within the LLI
Zone:
(a) At all times:
(i) Development and uses will not adversely affect or interfere with airport operations and
will be subject to applicable FAA regulations and any other federal airport authority,
including, without limitation, the City’s grant assurances and requirements under 14
C.F.R. Part 77, as amended, and any applicable airport rules and regulations.
(ii) Development and uses will be subordinate to, and conducted in a manner that will not
adversely affect and/or interfere with, airport-related flight operations and/or contribute to
flight hazards, including, without limitation, the following: (A) emitting electronic
interference with aircraft radio communications or electronic navigational aids; (B)
inhibiting pilot visibility through, among other things, emission of smoke or vapor, the use
of glaring lights, the use of lights that resemble a layout or color of a landing area, or the
use of search lights or flash-type advertising signs; (C) creation of hazards which are
dangerous to the safety of aircraft or flying in the vicinity of the airport; and/or (D) creating
attractants of birds or wildlife that are hazardous to aircraft.
(iii) The City and the public shall have a right of flight for passage of aircraft in the airspace
above the subject land together with the right to cause noise, vibration, dust, fumes,
smoke, vapor, and other effects inherent in the navigation or flight of aircraft and/or
operation of the airport.
(iv) Development and uses will not interfere with the operation and/or activities of the
Airshow of the Cascades during airshow days and will otherwise comply with applicable
airshow regulations.
(b) Prior to issuance of a certificate of occupancy:
(i) All buildings with bathroom facilities shall be connected to the City sewer system; or
where applicable, connected to an approved septic drain field or alternative wastewater
treatment system. Development that occurs within 300 feet of an existing City sewer must
connect to the City sanitary sewer. Any structures requiring a building permit shall connect
to the City water system and demonstrate compliance with fire-flow and fire protection
requirements for the building. The City may authorize connections to an adjoining water
system.
Page 17 of 37

(ii) The development shall be connected to a permitted and operational on-site or off-site
stormwater management system.
(iii) All required on-site and off-site transportation improvements have been completed.
[Ord. 898 § 3 (Exh. D), 2017.]

18.15.140 Airport overlay designation (AO).
This overlay designation is depicted on the Airport Approach and Clear Zone Map prepared
by Tenneson Engineering Corporation and dated July, 1986 FAR Part 77 Airspace Plan View
map adopted as part of City’s Airport Master Plan.
…
(3) Permitted and Conditional Uses in the Airport Overlay. Except as provided in MDC
18.15.140(4), permitted and conditional uses in the AO zone are those permitted and
conditional uses allowed in the underlying zone.
(3) (4) Permitted Uses Within the Airport Approach Safety Zone Runway Protection Zone.
The Runway Protection Zone is depicted in Airport Layout Plan adopted as part of City’s
Airport Master Plan.
(a) Permitted Uses. Notwithstanding the underlying zoning designation, only the following
uses are permitted within the portion of the AO Zone designated as Runway Protection
Zone subject to subsection (b) below.
(a)(i) Landscape nursery, cemetery, or recreation areas which do not include buildings or
structures.
(b)(ii) Roadways, parking areas, and storage yards located in such a manner that vehicle
lights will not make it difficult for pilots to distinguish between landing lights and vehicle
lights or result in glare, or in any way impair visibility in the vicinity of the landing approach.
Approach surfaces must clear these areas by a minimum of 15 feet.
(c)(iii) Pipeline.
(d)(iv) Underground utility wire.
(4) Conditional Uses within the Airport Approach Safety Zone.
(a)(v) Commercial and industrial uses, when authorized in the primary zoning district.
(b)(vi) Public service or utility facilities requiring no structures.
(b) Uses in the Runway Protection Zone Airport Approach Safety Zone are subject to the
following additional , provided the use does may not include any elements, or be operated
in any manner, that would not result in any of the following:
Page 18 of 37

(i) Creating electrical interference with navigational signals or radio communication
between the airport and aircraft.
(ii) Making it difficult for pilots to distinguish between airport lights or others.
(iii) Impairing visibility.
(iv) Creating bird strike hazards.
(v) Endangering or interfering with the landing, taking off, or maneuvering of aircraft
intending to use the airport.
(vi) Attracting large numbers of people.

…
18.25.170
Landscaping standards.
(1) General Standards. Unless otherwise specified for a specific use or zone in this
Development Code, the minimum amount of landscaping is established by zone as
follows:
R-1:
15%
R-2:

15%

R-3:

15%

C-1:

15%

C-2:

10% of off-street parking
area

C-3:

15% of off-street parking
area

NC:

15%

I:

10%

LLI:

10%

MUE:

15%

OS/PF:

25%

AD:

10%

MO:

15%

CPUD:

15%

(2) Specific Standards. Landscaping shall comply with the following standards:
(a) Plant Selection. Native vegetation shall should be preserved or planted where
practical and will be counted towards required landscaping requirements. A combination
of live nonnative deciduous and evergreen trees, shrubs and ground covers, including
Page 19 of 37

lawn, shall be used for all planted areas (i.e. must use at least one item from each
category). Drought-tolerant plantings are encouraged. Fire-resistive plants should be
planted in areas or on slopes where necessary to reduce the risk of fire spreading to
structures. As necessary, soils shall be amended to allow for healthy plant growth.
Coverage for planting is measured based on the size of plants at maturity or after two years
of growth, whichever comes sooner. Ground cover plants must be sized and spaced in the
following manner: planted at a rate of at least one plant per 36 inches on center, in
triangular spacing based on plant habitat (growth rate) with an expected coverage of 50
percent within two years of the time of planting.
(b) Hardscape Features.* Ground-level areas for passive use, such as patios, decks,
plazas, paved dining areas, etc., may cover up to fifteen percent (15%) of required
landscaping area; swimming pools, sports courts and similar active recreation facilities
may not be counted toward fulfilling the landscaping requirement.
(c) Stormwater Facilities. Stormwater facilities (e.g., detention/retention ponds and
swales) that are landscaped can be counted in the required amount of landscaped area on
the site. Planting of broadleaf canopy trees is encouraged as effective surface water
interceptors.
(d) In the R-1, R-2, and R-3 zones, at least fifty percent (50%) of the required landscaping
must be located in the front yard setback or otherwise between the structure and the front
property line.
(e) Landscaped areas must be appropriately irrigated. Xeriscaping may be unirrigated at
the discretion of the Community Development Director.
(f) Required landscaping must be continuously maintained. Plants or trees that die or are
damaged must be replaced and maintained similar to initially installed landscaping.
Hardscaping used to meet required landscaping requirements must be replaced if
damaged and otherwise maintained similar to initially installed hardscaping.
(g) Surface drainage must be managed in accordance with the Public Improvement
Standards.
(h) Ground-level areas for passive use, such as patios, decks, etc., may cover up to fifteen
percent (15%) of the required landscaping area; swimming pools, sports courts, and
similar active recreation facilities may not be counted toward fulfilling the landscape
requirement.
(h)

Decorative Rock.
(i) Maximum Coverage. Decorative rock may be used as required landscaping but,
together with hardscaping, may only satisfy 65% of the applicable minimum
Page 20 of 37

landscaping requirement (i.e. at least 35% of required landscaping must be
vegetative landscaping). Large areas of decorative rock should be broken up with
vegetative landscaping or other hardscaping. Notwithstanding anything to the
contrary, in no event will total decorative rock coverage for the entire site exceed
50% of the required landscape area for the subject property regardless of whether
or not decorative rock is proposed to meet landscaping requirements.
(ii) Size and Color: Decorative rock must be between one (1) inch and three (3)
inches in diameter and shall consist of natural or earth-tone colors. Bright or
fluorescent-colored materials are prohibited unless approved by the Planning
Director for specific design intent.
(iii) Installation Requirements: Decorative rock must be installed over a weed
barrier fabric. Decorative rock being used as ground cover must be installed to a
minimum depth of one (1) inch to ensure adequate coverage.
(iv) Prohibited Materials. Crushed aggregate, road base, or decomposed granite
used for road construction, or similar materials, are not decorative rock and are
otherwise prohibited as ground cover.
(v) Maintenance. Decorative rock must be maintained in a clean and weed-free
condition and must be replenished or refreshed as needed to maintain coverage
and appearance.
(i) Waivers or Modifications. The Community Development Director may waive or modify
any landscaping standard if the Community Development Director finds that: (i) the waiver
or modification will not harm or will be beneficial to the public in general; and (ii) the waiver
or modification is not inconsistent with the general purpose, or any City plans or policies,
of promoting attractive landscaping. The application for a waiver, modification, or deferral
must be in writing submitted as part of a development application, shall be subject to
applicable fees established by the City Council, and shall require that the application be
subject to a Type II procedure if not already subject to a Type II or higher procedure. The
application must specify the nature of the requested waiver or modification and how the
criteria listed in this subsection are met. The Community Development Director may
impose any condition of approval necessary to satisfy the purposes of this section,
including, without limitation, requiring that the applicant exceed one particular standard in
lieu of meeting another particular standard.

Page 21 of 37

18.25.160 Outdoor lighting standards.
…
(2) Outdoor Lighting Standards.
…
(b) Unless necessary for safe and convenient air travel, outdoor lighting must not project
directly into the airport runway, taxiway, or approach safety zone Runway Protection Zone.

Page 22 of 37

18.40.020 Site plan review.
Purpose. To determine compliance with this Development Code for development not subject to
zoning review.
(1) Applicability. Site plan review is required for the following:
(a) All new or modified conditional uses.
(b) All new nonresidential development.
(c) Apartments.
(d) All new or modified outdoor uses of 3,000 square feet or greater.
(e) Any expansion or modification of an existing nonresidential or apartment or residential
mixed-use development in excess of 3,000 square feet or that requires a new or modified point
of access.
(f) All townhome developments.
(g) Cottage cluster developments.
(2) Site Plan Committee.
(a) The Site Plan Committee shall consist of:
(i) Community Development Director;
(ii) Public Works Director;
(iii) Fire Marshal; and
(iv) Building Official.
These individuals shall carry out the duties as set forth in this section.
(b) The Site Plan Committee shall review the proposal subject to site plan review of the
Development Code. Once the Site Plan Committee members have submitted their comments to
the Community Development Director, the Community Development Director may approve a
proposal with conditions if minimal modification will permit the proposal to comply with
Page 23 of 37

requirements of this Development Code. The Community Development Director may refer any
site plan application to the Planning Commission for determination.
(3) Procedures.
(a) Before any building permit is issued for any development subject to a site plan review, a site
plan application shall be submitted for determination.
(b) Prior to filing a site plan application, the applicant is encouraged to confer with the
Community Development Department concerning the requirements of a formal application.
(c) The site plan application shall be filed on a form provided by the Community Development
Department.
(d) The site plan shall be drawn to scale and shall indicate the following:
(i) Location, size, and height of all existing or proposed structures.
(ii) Location, size, and dimension of existing and proposed setbacks, and all spaces between
buildings.
(iii) Adjoining streets and rights-of-way.
(iv) Points of access and circulation patterns, loading and maneuvering spaces.
(v) Off-street parking; showing location of parking areas, number of parking spaces including
accessible parking, and type of surface.
(vi) Existing and proposed landscaping, sSidewalks, patios, courtyards, and decks.
(vii) Storm drainage system, including, but not limited to, draining and grading plan, existing
topography, and elevations.
(viii) Fences, screens, and retaining walls, including heights and materials.
(ix) Existing and proposed utilities (e.g., electric, gas, power lines).
(x) Exterior lighting (show location and general nature).
(xi) Sanitary sewer system or location of septic tank and drain field (if still using and not
connected to City sewer), and the distance the lot is from the nearest sewer connection.
Page 24 of 37

(xii) Water supply (showing size of main, water flow, and size of water line).
(xiii) Location of existing and, if any, proposed fire hydrants with size and flow data.
(xiv) Identify any existing or proposed easements.
(xv) Proposed public improvements.
(xvi) Sign (if existing, location and size). Signs are subject to the provisions of Chapter 18.35
MDC.
(xvii) Give intended type of occupancy for the structure (e.g., assembly, educational,
manufacturing, processing, storage and type of contents).
(xviii) List all existing or proposed conditions that could be hazardous to life and property from
fire or explosion (e.g., storage of: liquefied petroleum gas, flammable or combustible liquids,
explosives and blasting agents).

(e) If required by the Public Works Director, a site plan application must include an analysis
of the anticipated demand for wastewater, stormwater, potable water, power,
telecommunications, and natural gas and a utility plan setting forth the utility
infrastructure, with locations and specifications meeting the Public Improvement
Standards, proposed to support the proposed development.

(f) A site plan application must include a transportation assessment letter or
transportation impact analysis as required by MDC 18.25.180.
(g) Developments with more than one proposed building must be a phased development
and submit a phasing plan concurrently with the site plan review application. Nothing
herein shall preclude a proposal that all proposed buildings will be completed in a single
phase.
(h) (e) Within thirty (30) days, the Community Development Director shall deem the application
complete or notify the applicant of the deficiencies in the application.
(4) Approval Criteria for Other Than Needed Housing and Needed Housing on Discretionary
Track.
(a) Approval of a site plan for other than needed housing shall be based on the following
criteria:
Page 25 of 37

(i) Allowed Use. The proposed land use is a permitted or conditional use in the zoning district.
Conditionally permitted uses require approval of a conditional use permit.
(ii) Zoning Standards. The proposal complies with the applicable standards of the applicable
zoning district(s) in which it is located.
(iii) Safety. The proposed development can meet applicable building and fire code standards.
The proposed development does not present, or adequately mitigates, any unique safety
hazards.
(iv) Special Needs of the Disabled. When deemed appropriate, the site plan shall provide for
the special needs of disabled persons, such as ramps for wheelchairs, drop curbs, and disabled
parking stalls.
(v) Preservation of the Natural Landscape. The landscape and existing grade shall be preserved
to the maximum practical degree, considering development constraints and suitability of the
landscape or grade to serve the applicant’s functions. Preserved trees and shrubs shall be
protected during construction.
(vi) Pedestrian and Vehicular Circulation and Parking. The location and number of points of
access to the site, sidewalks, the interior circulation patterns, designs of parking areas, and the
separation between pedestrians and moving and parked vehicles shall be designed to promote
safety and avoid congestion on adjacent streets.
(vii) Buffering and Screening. Areas, structures, and facilities for storage, machinery and
equipment, services (main, refuse, utility wires, and similar materials), parking and loading, and
similar accessory areas and structures shall be designed, located, buffered, or screened to
minimize adverse impacts on the site and neighboring properties.
(viii) Public Improvements. The proposal demonstrates compliance with the Public
Improvement Standards.
(ix) Public Facilities. All required public facilities have adequate capacity, as determined by the
City, to serve the proposed use including, without limitation, the transportation, sewer,
stormwater, and water systems.
(x) Supplementary Provisions. All applicable provisions in Chapter 18.25 MDC are satisfied.

Page 26 of 37

(xi) Special Standards for Certain Uses. All applicable provisions in Chapter 18.30 MDC are
satisfied.
(xii) Master Plan Compliance. The proposal is in substantial conformance with any applicable
approved master plan, master facilities plan, refinement plan, and/or special planned district.
(5) Approval Criteria for Needed Housing.
(a) Approval of a site plan for needed housing shall be based on the following criteria:
(i) Allowed Use. The proposed land use is an allowed use in the zoning district.
(ii) Zoning Standards. The proposal complies or can comply with the applicable standards of
the applicable zoning district(s) in which it is located.
(iii) Safety. The proposed development complies or can comply with applicable building and fire
code standards.
(iv) Special Needs of the Disabled. The proposed development complies or can comply with the
Americans with Disabilities Act and its implementing regulations.
(v) Public Improvements. The proposal demonstrates compliance with the Public Improvement
Standards.
(vi) Public Facilities. All required public facilities have adequate capacity, as determined by the
City, to serve the proposed use including, without limitation, the transportation, sewer,
stormwater, and water systems.
(vii) Supplementary Provisions. All applicable provisions in Chapter 18.25 MDC are satisfied.
(viii) Special Standards for Certain Uses. All applicable provisions in Chapter 18.30 MDC are
satisfied.
(ix) Master Plan Compliance. The proposal is in substantial conformance with any applicable
approved master plan, master facilities plan, refinement plan, and/or special planned district.
(6) To ensure that a development proposal satisfies applicable criteria, and mitigates identified
impacts, the City may impose conditions of approval including, but not limited to, the following:
(a) An increase in the required setback(s).

Page 27 of 37

(b) Modifications to pedestrian and vehicular circulation patterns, parking provisions, the
location and number of points of access to the site, sidewalks, and designs of parking areas.
(c) Additional off-street parking.
(d) Limitations on the size, location, and number of outdoor lights.
(e) Limitations on the number and location of curb cuts.
(f) Dedication of land for the creation or enlargement of streets where the existing street
system will be impacted by or inadequate to handle the additional burden caused by the
proposal.
(g) Dedication of land or an easement for the creation or extension of access corridors for
pedestrian and bicycle travel.
(h) Improvements, including, but not limited to, paving, curbing, installation of traffic signals,
construction of sidewalks, striping bike lanes, or other improvements to the street system
which serves the subject property where the existing street system will be burdened by the
applicant’s proposal or the proposal would create health or safety issues if unmitigated.
(i) Improvement or enlargement of utilities serving the subject property where the existing
utilities system will be burdened by the proposal. Improvements may include, but shall not be
limited to, extension of utility facilities to serve the proposed use and installation of fire
hydrants.
(j) Landscaping shall comply with the appropriate zoning district’s landscape requirements
within the Development Code.
(k) Transit facility or an easement for bus pullout if on a mass transit route.
(l) Location or orientation of buildings and entrances closer to the street to serve pedestrians,
bicyclists, and/or mass transit use.
(m) Any other limitations or conditions necessary to achieve the purpose of this Development
Code.
(7) Review Process. The Community Development Director may (at his/her discretion) elevate
the application to a Type III application and review process.

Page 28 of 37

(8) Appeal. The applicant or any interested person may appeal a decision of the Site Plan
Committee to the City Council, in accordance with the procedures of MDC 18.80.240.
(9) Revisions. Revisions made by the applicant to an approved site plan shall be made pursuant
to the procedures set forth in this section. Where required site plan approval has been granted,
it shall be unlawful for any person to cause or permit the proposed construction, alteration,
improvement, or use in any manner except in complete and strict compliance with the
approved site plan.
(10) Time Limit on Site Plan Approval. Unless approved as a phased development,

aAuthorization of site plan approval shall become void after one year after approval decision
becomes final unless a building permit has been obtained and remains valid and active or an
extension has been granted under MDC 18.80.280.
(11) Phased Site Plan Review. Developments with multiple buildings may be approved as
phased site plan as follows:
(a) The submitting phasing plan must demonstrate how each phase will comply with
applicable approval criteria including, without limitation, utilities, public improvements,
parking, and landscaping, all of which must be constructed in conjunction with or prior to
the applicable phase. A phased development must not result in requiring the City or other
property owners to construct public improvements that are required as part of the
approved underlying development proposal.
(b) The first phase of a phased site plan review approval expires one year after the site plan
approval becomes final, and the total approval period for all phases must not be greater
than five years from the date the site plan approval becomes final. The first and final phase
of a phased site plan review approval expires according to the approved schedule, unless:
(i) A building permit for vertical construction for the building(s) shown on the phase has
been issued;
(ii) If a building permit for vertical construction is not required for the phase, a building
permit for a remodel or change of use/occupancy has been issued for the approved use in
the phase; or

Page 29 of 37

(iii) An extension is granted under MDC 18.80.280 provided that only one extension will be
granted per phased development (i.e. not one extension per phase) and any extension
granted will apply to the current and all subsequent phases.
(c) Notwithstanding anything in this subsection to the contrary, if a phase of a phased site
plan approval expires, each subsequent phase also expires.
(d) Construction of initial phases of a phased site plan review does not vest future phases
if the phased site plan review approval expires.

18.40.040 Design review standards for buildings greater than 30,000
gross square feet (large-scale buildings).
(1) Purpose. The purpose of these regulations is to mitigate potential impacts of large-scale
buildings (those containing more than 30,000 gross square feet and infrastructure that
supports such structures). The provisions set out below promote development that is
compatible with, and does not detract from, the City’s unique character, scale, and sense of
place and encourage a mixture of uses and sizes of structures that facilitate a safe and
comfortable pedestrian scale environment. Large-scale buildings and supporting infrastructure
shall be kept in good condition and shall be the responsibility of the property owner or building
owner. The standards in this section shall apply in addition to the standards of MDC 18.40.030.
In case of a conflict, the more restrictive standards shall prevail.
(2) Applicability. These standards apply in addition to any Design Review Standards for all
structures greater than 30,000 square feet in any zone.
(3) Size and Mass. Except for development in the I, LLI, AD, and OS/PF Zones, no single
structure greater than 150,000 gross square feet is permitted. Notwithstanding the foregoing, a
structure may be larger than 150,000 gross square feet outside of the I, LLI, AD, and OS/PF

Zones so long as no single separately rentable space within the structure exceeds 150,000
gross square feet.
…

Page 30 of 37

18.55.010 Master planned development approval process.
(2) Applicability. Unless the entirety of a site is fully site plan approved for a single use, a
master development plan is required prior to dividing (or otherwise causing an existing

property to fall below 10 acres) or otherwise developing any site five (5) acres or greater for
nonresidential and mixed-use developments, ten (10) acres or greater for residential
developments, or any development proposing twelve (12) or more townhomes.
Notwithstanding the foregoing, larger sites may be divided or reconfigured; provided, that all
resulting lots or parcels are at least ten (10) acres in size or greater and a deed restriction is
recorded requiring a master plan prior to further division of the resulting parcels. In addition, a
developer may voluntarily seek a master development plan for any property or group of
contiguous properties two acres in size or greater or any development containing townhomes.

3) Master Development Plan Submittal Requirements. The master development plan
application must include maps, studies, and written materials that show and/or contain all
required information listed below. Maps may be in schematic form, but must be clearly and
legibly drawn to a scale sufficient to enable the decision authority to have an adequate
understanding of the proposal.
(a) A title report that includes a legal description of the master planned development.
(b) An existing conditions map depicting the topographic character of the land and any
important natural features of the site, including without limitation streams, rivers, wetlands,
trees over six inches DBH, and rock outcroppings.
(c) A schematic depiction of the master planned development that includes types and general
locations of proposed uses, character, and overall range of density of the development,
proposed roadways, parks/open spaces, pedestrian or recreational amenities, utility
connections, and other information necessary to convey the concept of the overall master
planned development.
(d) A vicinity map showing the relationship of the proposed master planned development to
adjoining developments, streets, storm drainage, sewer, water, and utility services.
(e) Proposed development regulations if different from the regulations in the underlying zones
or specific use.
Page 31 of 37

(f) A street plan that includes the location, width, and design of streets, and the relationship of
streets to any existing or proposed streets as shown in the City’s transportation system plan.
(g) A traffic study which addresses impacts of the buildout of each phase of the master
development plan on affected County, City, and state road systems, and transportation
improvements necessary to mitigate any such impacts (including suggested timing for
construction of mitigating improvements).

(h) An analysis of the anticipated demand for wastewater, stormwater, potable water,
power, telecommunications, and natural gas and a utility plan setting forth the utility
infrastructure, with locations and specifications meeting the Public Improvement
Standards, proposed to support the master planned development.

(h)(i) Any reconfiguration of the zoning if proposed. A zone change may be required to achieve
desired configuration.
(i)(j) Alternative design review standards if proposed.
(j)(k) An estimated development phasing schedule indicating:
(i) The approximate date when construction of the project can be expected to begin; and
(ii) The phases in which the project is expected to be built, including estimated dates of
construction for each phase.
(k)(l) A narrative setting forth the applicable approval criteria with discussion supported by
evidence included in the submittal of how the proposal satisfies each applicable approval
criterion.
(4) Approval Criteria for Other Than Needed Housing and Needed Housing on a Discretionary
Track. The review body may approve the master development plan, or approve with conditions
if appropriate, if the master development plan satisfies the following criteria:
(a) The master development plan is designed to avoid or reasonably minimize potentially
adverse effects on surrounding lands (both the natural and built environment). A variety of
measures can be used to accomplish this, including, but not limited to, landscaping, buffers,
fencing, or the arrangement of uses, structures, service facilities, open spaces, or
improvements within the master development plan.
Page 32 of 37

(b) Public facilities and services, including, but not limited to, water, sewer, transportation,
parks, police service, fire protection, and schools, are adequate, or will be adequate at the time
of occupancy, to accommodate the master development plan and are consistent with the City’s
infrastructure master plans.
(c) The master development plan is designed to efficiently use the land, including preserving
the overall value of natural features such as streams, wetlands, wooded cover, and rock
outcroppings if practicable.
(d) The uses and densities must be consistent with the Zoning Map designations. If the
applicant proposes to rearrange or change the underlying zoning as part of the master
development plan application, the applicant must satisfy the criteria for a zone change
pursuant to MDC 18.75.030. The review body may approve additional or different uses if the
review body determines that the additional or different uses are compatible with the uses
otherwise allowed in the applicable zone and that the trip generation rate of the additional or
different uses does not exceed the trip generation rate of the highest intensity outright
permitted use in the zone as determined by the latest edition of the Trip Generation Manual
produced by the Institute of Transportation Engineers, or a similar publication.
(i) Notwithstanding anything in the code to the contrary, when more than fifty percent (50%) of
the residentially zoned portion of a site proposed for a master planned development consists
of slopes of ten percent (10%) or more, a minimum density of four units per gross acre is
permitted within residentially zoned portions of the master plan development site.
(e) The applicant must demonstrate that minimum lot size, width, depth, street frontage,
setbacks, height, and other applicable requirements for proposed lots are or could be met.
Approval is based on applicable standards in the Madras Development Code or alternative
standards proposed by the applicant.
(f) At least eight percent (8%) of the gross acreage of a residential master planned development
and five percent (5%) of the gross acreage of a nonresidential master planned development
must be open space. Notwithstanding the foregoing, no open space is required for an industrial
master planned development (i.e., entirely located within the AD, I, MUE, or LLI zones). If a
mixed-use master planned development is proposed, the foregoing open space requirement
will apply but the total amount of required open space will be proportionate to the acreage of
each use category (based on zoning) in the proposed master planned development (i.e., eight
percent (8%) of residential gross acreage plus five percent (5%) of nonresidential/nonindustrial
Page 33 of 37

gross acreage). Improved or usable open space is encouraged. Open space may be publicly or
privately owned and includes the use of land focusing on natural areas, trails (meeting the City’s
standards), parks, golf courses, community gardens, or public squares. Required landscaping
on individual lots, planter strips along rights-of-way, and similar areas is not considered open
space. For townhome developments subject to this chapter, the townhome development will
provide the greater amount of open space between this subsection and MDC 18.30.190(4)(f)
and will otherwise comply with MDC 18.30.190(4)(f).
(g) Proposed streets meet or can meet the Public Improvement Standards and the design and
construction standards unless waivers or modifications are proposed as part of the master
planned development. Any modifications or waivers must be coordinated with and approved by
the Public Works Director and the Fire Marshal.
(h) Any proposed modifications to otherwise applicable standards for development within the
master planned development must be appropriate for the type and scale of development
proposed, must not inhibit the ability to serve the subject property with urban services, and
must otherwise assure the health, safety, and welfare of the subject property and adjacent
properties.
(i) The applicant must demonstrate that commonly owned property, private streets, and other
private amenities/infrastructure will be maintained through an owner’s association,
maintenance agreement, or other arrangement acceptable to City.
(j) Master plans for any site proposed to be developed with fifty (50) or more dwellings must
include a mix of at least two housing types, and master plans for sites proposed to be
developed with one hundred (100) or more dwellings must include a mix of at least three
housing types permitted or conditionally permitted in the applicable zones (i.e., accessory
dwelling units, detached single-family dwellings, attached single-family dwellings, duplexes,
triplexes and apartments). Where a mix of housing units is required, no more than eighty
percent (80%) of the total dwelling units may be the same housing type.
…
(6) Master Development Plan Approval Process.
(a) Master development plan applications will be reviewed as follows:

Page 34 of 37

(i) through a Type II process, the Community Development Director may review any master
plan development that does not propose any changes to existing zoning of site, uses not
permitted in the applicable pursuant MDC 18.55.010(4)(d), or modification to applicable
standards under MDC 18.55.010(4)(h).
(ii) the Planning Commission must review any the master development plan that is not subject
to review by the Community Development Director at a public hearing conducted in
accordance with the applicable provisions of Chapter 18.80 MDC.

(b) The approval of the master development plan is valid for a period of three years, unless the
review body approves, at its discretion, an alternative phasing plan, which must not exceed ten
(10) years in the aggregate. However, extensions to the master development plan, or any phase
thereof, may be approved in accordance with MDC 18.80.290. A master development plan, or
any individual phase thereof, will not be considered initiated unless and until a plat is recorded
for the master development plan, or any individual phase thereof, which must occur prior to
expiration of the approval or in accordance with the phasing plan. Notwithstanding anything
herein to the contrary, a plat that merely establishes a future development tract for an
individual phase is not sufficient to initiate the individual phase.
(c) Notice of the review process and opportunities for comment must be provided to all
properties within five hundred (500) feet of the boundaries of the proposed master planned
development.

18.80.090Classification of decisions.
All land use approvals and planning reviews shall be processed based on the decision
classification hierarchy set forth below. Except where the classification is expressly prescribed
in this Development Code, the Community Development Director shall have discretion as to
how a particular application, request, or review shall be classified and which review procedures
will be used, which shall not be an appealable decision.
(1) Type I Decisions.
(a) A Type I decision may be handled administratively by the Community Development Director
without public notice or hearing because a Type I decision is neither a land use decision nor a
limited land use decision under ORS 197.015.

Page 35 of 37

(b) The Community Development Director has discretion to elevate a Type I decision to a Type
II procedure but must elevate a Type I decision to a Type II procedure when there is a need to
interpret this Development Code or any other applicable standard, exercise policy or legal
judgment, or apply discretionary land use standards.
(c) Type I decisions are not subject to appeals.
(2) Type II Decisions.
(a) Type II decisions are made by the Community Development Director following public notice
and an opportunity for parties to comment, but without a public hearing.
(b) Applications for a partition, site plan approval, minor variance, master planned

development that does not propose to change permitted uses, development standards, or
zoning, and such other applications as prescribed by this Development Code may shall be
processed as Type II decisions.
(c) The Community Development Director has discretion to elevate an application for a Type II
decision to a Type III decision.
(d) If appealed, Type II decisions are reviewed by the Planning Commission and the Planning
Commission’s decision may be appealed to the City Council subject to the City Council’s
discretion to hear the appeal.
(3) Type III Decisions.
(a) Type III decisions are made by the Planning Commission after a public hearing following
quasi-judicial hearings procedures set forth in this chapter.
(b) Applications for a subdivision, planned unit development, conditional use, major variance,
quasi-judicial zone change, master development plan that proposes to change permitted

uses, development standards, or zoning, and such other applications as prescribed by this
Development Code may shall be processed as Type III decisions.
(c) If appealed, Type III decisions may be appealed to the City Council subject to the City
Council’s discretion to hear the appeal.

Page 36 of 37

Page 37 of 37

CITY OF MADRAS
Request for Council Action

Meeting Date: March 10, 2026
To:

Mayor and City Council Members

From:

Jeff Hurd, Public Works Director

Through:

Jeff Hurd, Public Works Director

Subject:

Automated Weather Observing System
Wind Indicator Repair

TYPE OF ACTION REQUESTED:
Approve
MOTION(S) FOR CONSIDERATION:
Council approve the repair to the Automated Weather Observing System (AWOS) wind indicator
in the amount of $8,954.59.
OVERVIEW:
Staff identified that a hawk had begun perching on the AWOS wind indicator assembly. The
dowel previously installed on the unit was removed to discourage perching. Mylar tape was
temporarily installed as an additional deterrent; however, it interfered with the proper function of
the wind indicator and was subsequently removed.
Despite these efforts, the hawk caused damage to the ultrasonic wind indicator components. The
damage has rendered the unit inoperable, and replacement of the affected component is now
required.

STAFF ANALYSIS:
The Automated Weather Observing System (AWOS) wind indicator experienced operational
issues after a hawk was observed at the site. The hawk had been perching on the assembly,
prompting staff to remove a previously installed dowel that had been in place on the unit. Mylar
tape was installed as a deterrent; however, it negatively affected the accuracy and function of the
wind indicator and was removed.
Subsequent inspection confirmed that the hawk caused damage to the ultrasonic wind indicator
components. The damage has compromised the reliability and functionality of the wind
measurement system. Because the AWOS provides critical wind data for aviation safety,
maintaining accurate and operational equipment is essential.

Page 1 of 2

Request for Council Action

Replacement of the ultrasonic wind sensor component is required to restore full functionality. The
cost to replace the damaged ultrasonic wind indicator component is $8,954.59. This amount
reflects the purchase price of the replacement sensor and associated components necessary to
restore the Automated Weather Observing System (AWOS) to full operational status.

FISCAL INFORMATION:
$8,954.59 - Airport Operations Fund Repairs and Maintenance 509-090-520-2207
SUPPORTING DOCUMENTATION:
Attached quote and PO
STRATEGIC GOAL:

Page 2 of 2

Request for Council Action

Reorder From:

FPO· REV. 9/ 14

5
■1,~ .....1
T .l.ftLJ
__ __..

PURCHASE ORDER

~"!,..__0...,.._l\_
~'
Jl"_TJL.-HE-nC-ITY_RA_O_F
iiMfU

t;JCO r i ant - Workflow Solulion s (541 ) 306-4842 • www.e-co riant.com

I

125 SW "E" Street • Madras, OR 97741
(541) 475-2344 • www.ci.madras.or.us

11738

Name:
Dept:
Phone/Email:

$

Code Payment To:
Fund :

t\'°'~Dif

SHIPPING AND/OR CONTINGENCY $

GL Description: ~BR~~~ W\tJO \NO •
GL Code: - - - . - - - . - - - . - - - -

$

If costs are coded to various GL Codes, please either
write in space below or attach a detailed breakdown
of costs to each GL Code.

City of Madras is an equal opportunity provider.

Director

Date

City Administrator

Date
ORIGINAL COPY

I

~CVO~E'MA-'f<,

?- /~o l::2_Ja

TRANSPORTAIIO!, SERVICES

Quotation confirmation: 20000294
Please remit to :
DBT Transportation Services LLC
P.O. Box 25221
New York, NY 10087-5221

DBT Transportation Services LLC
1065 National Drive , Suite 1
Sacramento, CA 95834
Tel. : +1 844-343-8328

Page:
Sold To Party:1102661
City of Madras B KS33
125 SW E Street
Madras OR 977 41

Quotation Date:

0000-00-00T00: 00: 00

Customer Number:
ADBS contact name:

1102661
linda veasman
linda.veasman@adbsafegat
e.com
MDJ
Jan 22, 2026
Feb 21, 2026

ADBS contact email:

Contact Person:
Phone:

Airport code:
Valid From:
Valid To:

Lorraine Martinelli
+15415612020

Ship To Party:2104655
Madras Municipal Airport S KS33
2028 NW Berg Dr
Madras OR 97741
Note: Parts to be installed during next contracted site visit.
Pay
Item

Contract Item
Item

10

Product

Description

237889SP

Cable 26M - WMT
Sensor

Delivery ex-works:

15

Jan 27 , 2026

WMT702-VCVD

Delivery ex-works:

17
Delivery ex-works:

Payment Terms:
lncoterms:
Shipment Type:
FOB:
Freight paid by:

Net Value

1 EA

812 .96
USO/ 1 EA

812 .96 USO

Confirmed Quantity:

Net Due in 30 Days

1 EA

Confirmed Quantity:

8,091 .63
USO/ 1 EA

8,091 .63 USO

1 EA

1 EA

FREIGHT
Feb 9, 2026

1 EA

Confirmed Quantity:

50.00
USO/ 1 EA

50.00 USO

1 EA

Total Net Amount

8,954.59 USO

Total

8954.59 USD

ADB Best Way
Origin
NO

General :

FED ID: 81 -2865699
DUNS : 06-430-4214

Net Price

WMT702 WIND
SENSOR FOR VCND
AWOS

Jan 27, 2026

FREIGHT

Quantity

DBT Transportation Services LLC EFTACH & Wire:
Bank: JP Morgan Chase Bank
Address : New York, NY
Account name: DBT Transportation
Services LLC
Routing/ABA#: 021000021 - Account#:
827803880
SWIFT# (int'I) : CHASUS33
Remit details to: [email protected]

1/2

TH/\NSPORTAriON SER'IICCS

Quotation confirmation: 20000294

Page:

2/2

Our general terms and conditions apply to all sales and purchases. The English language version may be
downloaded from our website :
https://adbsafegate.com/abouUcorporate/terms-cond itions/
RESERVATION CLAUSE:
Purchaser acknowledges that ADB SAFEGATE Americas is required to comply with export applicable laws and
regulations relating to the sale, exportation ,transfer ,assignment, disposal and usage of the Equipment
provided under the Contract, including any export license requirements . Purchaser agrees that such Equipment
shall not at any time directly or indirectly be used, exported, sold, transferred, assigned or otherwise disposed
of in a manner which will result in non-compliance with such applicable export laws and regulations. It shall be
a condition of the continuing performance by ADB SAFEGATE Americas of its
obligations hereunder that compliance with such export laws and regulations be maintained at all times.
PURCHASER AGREES TO INDEMNIFY AND HOLD ADB SAFEGATE Americas HARMLESS FROM ANY
AND ALL COSTS, LIABILITIES, PENALTIES, SANCTIONS AND FINES RELATED TO NON-COMPLIANCE
WITH APPLICABLE EXPORT LAWS AND REGULATIONS.
To Reorder call: 800-545-4157 ADB SAFEGATE

FED ID: 81-2865699
DUNS: 06-430-4214

DBT Transportation Services LLC EFTACH & Wire:
Bank: JP Morgan Chase Bank
Address : New York, NY
Account name: DBT Transportation
Services LLC
Routing/ASA#: 021000021 -Account#:
827803880
SWIFT# (int'I) : CHASUS33

CITY OF MADRAS
Request for Council Action

Meeting Date: March 10, 2026
To:

Mayor and City Council Members

From:

Nicholas Snead, Community Development Director

Through:

Keli Pollock, City Recorder

Subject:

Authorization to submit State & Local Government Cybersecurity Grant.

TYPE OF ACTION REQUESTED:
Approve
MOTION(S) FOR CONSIDERATION:
Authorize the City of Madras to submit a Phase 2 State & Local Government Cybersecurity Grant
to the Oregon Office of Emergency Management and authorize the Mayor to sign all related
documents on behalf of the City.
OVERVIEW:
The Oregon Office of Emergency Management (OEM) is soliciting grant proposals for the State
and Local Government Cybersecurity Grant program. Grant proposals are accepted on a
quarterly basis. The City is proposing funding to modernize outdated infrastructure that increases
cybersecurity risk and to strengthen foundational protections across local government systems.
The City’s IT contractor has identified the scope of work and provided a cost estimate of
$18,248.14, which is the amount of grant funding the City is requesting from OEM. Staff requests
authorization for the City of Madras to submit a Phase 2 State & Local Government
Cybersecurity Grant to the Oregon Office of Emergency Management and authorize the Mayor to
sign all related documents on behalf of the City.
STAFF ANALYSIS:
The City of Madras is proposing Phase 2 of its Firewall Modernization Initiative to strengthen the
internal network systems that support secure operations across City Hall, the Airport, Public
Works (B Street), the Golf Course, and the Wastewater South Plant. While Phase 1 focuses on
upgrading perimeter firewall equipment (currently pending award), Phase 2 will improve the
City’s internal network infrastructure to ensure consistent, secure connectivity within and
between facilities.
The project includes installation of updated network switches, deployment of managed wireless
access points with centralized controls, improved fiber backbone connectivity, installation of
protected power distribution equipment, and deployment of a secure wireless bridge at Public
Works. These improvements will create a standardized and secure internal network environment
across all facilities.
By completing Phase 2, the City will reduce cybersecurity risk, improve reliability of essential
systems, and ensure upgraded firewall protections can operate effectively across all facilities.
FISCAL INFORMATION:
Page 1 of 2

Request for Council Action

18,248.14, Information Technology Fund, A budget resolution to recognize revenue and
expenditures will be needed if grant funding is awarded.
SUPPORTING DOCUMENTATION:
OEM Project Overview
2026 SLCGP Application – Phase 2
STRATEGIC GOAL:

Page 2 of 2

Request for Council Action

City of Madras
State and Local Cybersecurity Grant Program (SLCGP)
Phase 2 Firewall Enhancement Project

Part I – Applicant Information
Legal Name of Organization: City of Madras
Physical Address: 125 SW E Street, Madras, OR 97741
County: Jefferson
Unique Entity ID (UEI): C1V2KNTZ3FY1
Organization Type: Other – Community Development
Organization Mission
The City of Madras serves the public by providing essential municipal services that support
the health, safety, and well-being of residents, businesses, and visitors. These services
include city administration, public works, wastewater operations, airport services, parks
and recreation, and critical infrastructure maintenance. The City is responsible for
maintaining reliable public systems, ensuring access to services, and safeguarding public
resources while supporting community growth and economic vitality. Secure and reliable
information systems are essential to delivering these services.
Formal Cyber Assessment Performed: No
Formal Cybersecurity Plan in Place: No
Mandatory Systems Currently Implemented
•

Advanced Endpoint Protection (AEP) – Yes

•

Domain Migration Services (.gov) – Yes

•

Immutable Data Backup & Recovery Testing – Yes

•

Multifactor Authentication (MFA) – Yes

Part II – Project Details
Selected Service
Tier 2 – Enhanced Network Protection – Firewall Services

Project Description
The City of Madras is proposing Phase 2 of its Firewall Modernization Initiative to
strengthen the internal network systems that support secure operations across City Hall,
the Airport, Public Works (B Street), the Golf Course, and the Wastewater South Plant.
While Phase 1 focuses on upgrading perimeter firewall equipment (currently pending
award), Phase 2 will improve the City’s internal network infrastructure to ensure
consistent, secure connectivity within and between facilities.
The project includes installation of updated network switches, deployment of managed
wireless access points with centralized controls, improved fiber backbone connectivity,
installation of protected power distribution equipment, and deployment of a secure
wireless bridge at Public Works. These improvements will create a standardized and
secure internal network environment across all facilities.
By completing Phase 2, the City will reduce cybersecurity risk, improve reliability of
essential systems, and ensure upgraded firewall protections can operate effectively
across all facilities.
Quotes Received: Yes

Project Budget (POETE)
Planning: $0
Organization: $0
Equipment: $18,248.14
Training: $0
Exercises: $0
Total Amount Requested: $18,248.14

Alignment with Oregon Cybersecurity Plan
This project supports Oregon’s Cybersecurity Plan by modernizing outdated infrastructure
that increases cybersecurity risk and by strengthening foundational protections across
local government systems. It aligns with:
•

Strategic Goal 2: Risk Management

•

Strategic Goal 3: Mature Cybersecurity Capabilities

•

Tier 2 – Enhanced Network Protection – Firewall Services

The project advances statewide objectives to improve system resilience, reduce
vulnerabilities, and protect the confidentiality, integrity, and availability of public systems.

Part II – Risk
Threat
On January 2, 2025, the City’s managed security monitoring service identified a brute-force
login attempt targeting a City-issued device exposed through a mobile broadband
connection. While no breach occurred, the incident confirmed that City systems are
actively targeted.
Local governments nationwide remain targets of ransomware, credential harvesting, and
intrusion attempts. Without modernized internal infrastructure, a compromised device
could allow lateral movement across facilities.

Vulnerabilities
The City is susceptible to disruption due to aging and inconsistent internal network
infrastructure. Outdated switching and wireless systems limit segmentation, reduce
internal visibility, and increase risk of lateral movement between facilities.
Without standardized controls, a compromised device or account could impact
administrative systems, wastewater operations, public works, or airport services. Limited
staffing further increases recovery risk.

Potential Consequences
A successful cyberattack could result in network outages, encrypted data, disruption of
wastewater monitoring, delays in public works coordination, loss of financial system
access, and compromised sensitive data.
Extended downtime would require emergency response, forensic investigation, system
restoration, and could erode public trust. For a rural local government, impacts could be
prolonged and costly.

Part III – Solutions and Services
Section 1 – Internal Network Infrastructure Modernization
Vulnerability:
Aging internal network switching infrastructure limits segmentation and increases
susceptibility to lateral movement.
Solution:
Replace outdated switches and strengthen backbone connectivity across all major City
facilities.
Equipment Included:
•

Aruba 48-port PoE Switch (Airport, City Hall)

•

Aruba 24-port PoE Switch (City Hall, Wastewater South Plant)

•

Aruba 12-port PoE Switch (Golf Course)

•

Aruba SFP+ Modules (City Hall)

•

Fiber Optic Patch Panels (City Hall)

•

Network Switched PDU Boosters (All facilities)

Quantity: 17 infrastructure components
Total Cost: $13,121.50

Section 2 – Secure Wireless & Inter-Facility Connectivity
Vulnerability:
Inconsistent wireless management and inter-facility connectivity increase risk of
unauthorized access and lateral movement.
Solution:
Deploy centrally managed wireless systems and encrypted point-to-point connectivity.
Equipment Included:
•

Ubiquiti CloudKey+ (Airport, City Hall, Golf Course, Public Works, Wastewater)

•

UniFi U7 Pro WAP Systems (All facilities)

•

UniFi NanoBeam AC Wireless Bridge (Public Works)

Quantity: 17 wireless/connectivity components
Total Cost: $5,165.65

Part IV – Milestones
1. Project Kickoff and Final Design – 4 weeks
2. Procurement and Equipment Delivery – 6 weeks
3. Installation and Configuration – 8 weeks
4. Testing and Project Closeout – 4 weeks

Measurable Outputs and Outcomes
Outputs:
•

Installation and configuration of all switches, wireless access points, controllers,
secure connectivity components, and protected power equipment.

•

Documented segmentation and standardized configurations.

•

Completed system testing and validation.

•

Finalized technical documentation.

Outcomes:
•

Elimination of aging internal network equipment.

•

Improved network reliability and performance.

•

Strengthened internal traffic controls.

•

Reduced cybersecurity risk across all facilities.

Project Team
Project Lead: Todd Golditch, Radcomp Technologies
Technical Lead: Bryan Brady
Service Oversight: Chad Chiesa

Procurement: Christopher Elisea
City Point of Contact: Nick Snead

Sustainability
The City’s managed service provider will maintain the upgraded systems through routine
updates, monitoring, configuration reviews, and license renewals. Standardized
documentation developed during implementation will ensure long-term operational
sustainability.

Project Name
Phase 2 Firewall Project

State and Local Cybersecurity Grant Program Applica�on
Part I, Applicant informa�on: [Pass/Fail]
Please iden�fy the following:
•

Legal Name of Organiza�on seeking funding:
City of Madras

•

•
•

•

Physical Address:
o Street 125 SW E Street
o City Madras
o State OR
o Zip 97741
o County/Tribe Jefferson
Unique En�ty ID (UEI): C1V2KNTZ3FY1
Primary Organiza�on type: Other
If Other or Special District, Describe:
Community Development
Please briefly describe your organiza�on’s mission or func�ons with respect to
suppor�ng or serving the public:

The City of Madras serves the public by providing essential municipal
services that support the health, safety, and well-being of residents,
businesses, and visitors. These services include city administration, public
works, wastewater operations, airport services, parks and recreation, and
critical infrastructure maintenance. The city is responsible for maintaining
reliable public systems, ensuring access to services, and safeguarding
public resources while supporting community growth and economic vitality.
In carrying out these functions, the city relies on secure and reliable
information systems to manage operations, deliver services, protect
sensitive information, and communicate with the public. Maintaining the
integrity, availability, and security of these systems is essential to fulfilling
the City’s

•

Has the jurisdiction performed a formal cyber assessment?
No

•

If the jurisdiction has not performed a formal cyber assessment, does the
jurisdiction have a formal cyber security plan/strategy?
No

•

Which mandatory systems or items do you currently have in place or fully
implemented. Select all that apply

✔ Advanced Endpoint Protection (AEP)*
✔ Domain Migration Services (Migration to .gov)*
✔ Immutable Data Backup and Recovery Testing*
✔ Multifactor Authentication Capability (MFA)

Part II. Project Details
Which Cybersecurity service will you be perusing with this grant? (select one)
[1]
Advanced Endpoint Protection (AEP)*
Domain Migration Services (Migration to .gov)*
Immutable Data Backup and Recovery Testing*
Multifactor Authentication Capability (MFA)*
Albert Sensors
Information Security Awareness Training
URL/Web/Content filtering
Vulnerability Management Services & Scanning
Consulting and Planning Services
[2]
Converged Endpoint Management (XEM)
Cyber Security Risk Assessment Services
DNS Filtering
Email security gateway
Enhanced Network Protection - Firewall Services
Identity & Access Management Solutions
Mobile Device Management (MDM) Solutions
Penetration Testing Services
Privileged Access Management (PAM)
Web Application Firewall (WAF)

✔

[3]
Application Security Services
Security Information and Event Management (SIEM) Technology
MDR/XDR Solutions

Describe the project. What will this project do? Please be as clear and direct as possible
in your first paragraph. Supporting details may be provided in 2nd or 3rd paragraphs.
The City of Madras is proposing Phase 2 of its Firewall Modernization Initiative to
strengthen the internal network systems that support secure operations across City
Hall, the Airport, Public Works (B Street), the Golf Course, and the Wastewater South
Plant. While Phase 1 focuses on upgrading perimeter firewall equipment (currently
pending award), Phase 2 will improve the City’s internal network infrastructure to
ensure consistent, secure connectivity within and between facilities. This phase will
replace aging equipment, improve wireless reliability, and strengthen how City systems
connect and communicate.
The project includes installing updated network switches to improve reliability and
security, deploying managed wireless access points with centralized controls to ensure
secure and authenticated Wi-Fi access, improving fiber connectivity to strengthen
network backbone performance, and installing protected power distribution equipment
to safeguard critical network hardware. At Public Works, the city will also implement a
secure wireless bridge to ensure reliable communication between facilities. These
improvements will create a consistent and standardized network environment across all
major City locations.
By completing Phase 2, the City will reduce cybersecurity risk, improve reliability of
essential systems, and ensure that upgraded firewall protections can operate
effectively across all facilities. This project strengthens protection for services that
residents depend on daily, including wastewater operations, public works functions,
airport services, and administrative systems. The investment aligns with the Enhanced
Network Protection Firewall Services Tier 2 category under the Oregon SLCGP Service
Catalog and supports the City’s long-term goal of building sustainable and resilient
cybersecurity infrastructure.

Have you received quotes for the costs of the items, training, or services described
above?
Yes

POETE Areas
Planning

Development of policies, plans, procedures, mutual aid aweements, strateqies, and
other publications; also involves the collection and analysis of intelliqence and
information

Organization

Individual teams, an overall orqanizalional structure, and leadership at each level in
the structure

Equipment

Equipment, supplies, and systems that comply with relevant standards

Training

Content and methods of delivery that comply with relevant training standards

Exercises

Exercises and actual incidents that provide an opportunity to demonstrate, evaluate,
and improve the ability of core capabilities to perform assiqned missions and tasks
to standards

Project Budget Defined by POETE
Planning

$

Organization

$

Equipment

$

Training

$

Exercises

$

18,248.14

Total amount of funds requested in this applica�on: $ 18,248.14
Clearly describe how the project ties to Oregon’s SLCGP Cybersecurity Plan.

This project directly supports the Oregon Cybersecurity Plan’s strategy to modernize and hard

The project aligns with Strategic Goal 2: Risk Management and Strategic Goal 3: Mature Cyber

Part II: Risk: [60 points total]
As you consider your project to fill capability gaps to address Cyber Security, what threats,
vulnerabilities and Consequences do you face as a result of this gap? Be specific to the service
area you selected above.
a) Threat [20pts]: In considering a cyber threat, please describe the iden�fica�on and
substan�a�on of specific threats or atacks against your organiza�on or a closely related
organiza�on, network, or cell. Descrip�on can include findings from a threat or risk
assessment, police report(s), and/or insurance claims specific to the loca�on being
applied for including dates of specific threats.
The City of Madras has experienced documented cyber threat activity that demonstrates ongoing risk to municipal systems. On January
2, 2025, the City’s managed security monitoring service identified a brute-force login attempt targeting a City-issued device that was
externally exposed through a mobile broadband connection. The activity involved repeated unauthorized login attempts from remote IP
addresses targeting common and administrative accounts. While no breach occurred, the incident confirmed that City systems are
actively targeted and that exposed or insufficiently segmented systems present credible entry points for attackers.
In addition to this documented event, the city operates interconnected systems across multiple facilities, including City Hall, the Airport,
Public Works, the Golf Course, and the Wastewater South Plant. These systems rely on aging switching and wireless infrastructure that
limits internal segmentation and consistent security enforcement. Across Oregon and nationally, local governments remain frequent
targets of ransomware, credential-harvesting campaigns, and network intrusion attempts that exploit outdated internal infrastructure and
misconfigured wireless environments. The FBI, MS-ISAC, and CISA continue to report increased targeting of municipal utilities and
public-sector operational technology systems, including water and wastewater facilities.
Because Phase 2 addresses internal network protections under the Enhanced Network Protection Firewall Services category, the
relevant threat is not only external intrusion at the perimeter, but also unauthorized lateral movement once access is gained. Without
modernized switching infrastructure, standardized wireless management, and secure site-to-site connectivity, a single compromised
device could allow an attacker to move across facilities and impact critical services. The documented attempted intrusion and the City’s
current internal infrastructure limitations substantiate a credible and ongoing cyber threat to essential municipal operations.

b) Vulnerabili�es [20pts]: Please describe the organiza�on’s suscep�bility to destruc�on,
incapacita�on, or exploita�on by a cyber-atack.
The City of Madras is susceptible to exploitation and service disruption due to aging and
inconsistent internal network infrastructure across multiple facilities. While perimeter protections
are being addressed through a separate firewall modernization effort, internal switching,
wireless, and connectivity components remain outdated and unevenly configured. This limits
the City’s ability to enforce consistent security controls, segment network traffic appropriately,
and monitor internal activity effectively.
Several City facilities rely on older network switches and unmanaged wireless environments
that do not fully support modern security standards. Without standardized internal network
controls, a compromised user account or infected device could allow an attacker to move
laterally between systems and facilities. The lack of consistent segmentation increases the risk
that sensitive administrative systems, operational systems supporting wastewater and public
works, and other municipal services could be accessed or disrupted from a single point of
compromise. Additionally, aging backbone connectivity and limited visibility into internal traffic
reduce the City’s ability to quickly detect suspicious activity and isolate affected systems.
These vulnerabilities increase the City’s susceptibility to ransomware, credential misuse, and
network-based attacks that could degrade or incapacitate essential services. For a small local
government with limited IT staffing, recovery from such an incident would require significant
time and external support, potentially prolonging service disruption. Until internal network
infrastructure is modernized and standardized, the City remains at elevated risk of exploitation
and operational impact from a cyberattack.

c) Poten�al Consequences [20pts]: Please describe the poten�al nega�ve effects on the
organiza�on's assets, systems, and/or func�on if damaged, destroyed, or disrupted by a
cyber-atack because of the iden�fied vulnerabili�es.
If the identified vulnerabilities were exploited, the City of Madras could experience
significant disruption to essential municipal operations across multiple facilities. A
successful cyberattack leveraging weaknesses in internal network infrastructure could
allow an attacker to move laterally between systems, resulting in loss of network
availability, shutdown of critical applications, or encryption of municipal data. Such
disruption would directly affect operations at City Hall, Public Works, the Airport, the
Golf Course, and the Wastewater South Plant.
Operational impacts could include interruption of wastewater monitoring systems,
disruption of public works coordination, delays in airport administrative functions, and
loss of access to financial, payroll, or records management systems. Even temporary
downtime could impair the City’s ability to deliver services residents rely on daily.
Extended outages could require manual workarounds, emergency technical support,
and diversion of limited staff resources, significantly increasing operational costs.
In addition to operational disruption, a cyber incident could result in compromise or
loss of sensitive information, including employee records, financial data, infrastructure
documentation, and system configurations. Recovery efforts could involve forensic
investigations, system restoration, equipment replacement, and potential regulatory
reporting requirements. Beyond financial and technical impacts, service disruption
could erode public trust in the City’s ability to safeguard critical infrastructure and
maintain reliable operations. For a rural local government with limited redundancy and
staffing capacity, the consequences of a successful cyberattack could be prolonged,
costly, and highly disruptive to the community.

Part III: Solu�ons and Services [50pts] – Cybersecurity
In this section, consider your solution from the approved service catalog list above, to the risks
identified in Part II
a) iden�fy the vulnerability (as selected in Sec�on II-B) to be addressed,
b) describe each proposed ac�vity or investment (solu�on) to address the vulnerability.
c) For each solu�on, include the ac�on, item quan�ty, plan, plan development, and es�mated
price.

Vulnerability

Solu�on / Services

Quan�ty

Total costs

Internal Network Infrastructure
17
13121.50
Modernization :The City of Madras
faces elevated cybersecurity risk
due to aging and inconsistent
internal network switching
infrastructure that limits
segmentation, reduces internal
The City will implement Tier 2 – Enhanced Network Protection improv
traffic visibility, and increases
susceptibility to lateral movement if
a device or account is compromised.

The City will deploy secure, centrally
17
5,165.65
managed wireless infrastructure and
encrypted point-to-point connectivity to
ensure authenticated wireless access
Secure Wireless & Inter-Facility
ConnectivityThe City’s wireless and inter-facility connectivity environ
and protected
communications
between facilities.

-------------

Totals

Part IV: Milestones, Project Management and Sustainability [20pts]
Please list at least 4 milestones and es�mated �me (number of days, or weeks, or months)
required to complete that milestone.
Milestone
Project Kickoff Final Design

Time to complete
4 weeks

Procurement and Equipment Delivery

6 weeks

Installation and Configuration

8 weeks

Testing and Project closeout

4

a) Please describe the measurable outputs and outcomes that will indicate that this
Investment is successful at the end of the period of performance.
The success of this investment will be measured by the full deployment and operational status of upgraded network infrastructure across City Hall, the Airport,
Public Works (B Street), the Golf Course, and the Wastewater South Plant. Measurable outputs include installation and configuration of all identified switches,
wireless access points, controllers, secure connectivity components, and protected power distribution equipment; documented network segmentation and
standardized configurations; completed system testing; and finalized technical documentation.
Measurable outcomes include elimination of aging internal network equipment, improved network reliability and performance, strengthened internal traffic
controls, and consistent security enforcement across facilities. The City will demonstrate reduced cybersecurity risk through improved network stability, enhanced
visibility into internal activity, and the ability to sustain the upgraded environment through ongoing managed service monitoring and maintenance beyond the
grant period.

b) Please describe the project team, their contact informa�on, and their roles in
comple�ng this project.
The City of Madras will implement this project through a coordinated team consisting of City staff and its managed service provider, Radcomp Technologies. Todd Golditch, Senior Client Account
Manager at Radcomp Technologies, will serve as the Project Lead, responsible for overall project coordination, scheduling, milestone tracking, and compliance with SLCGP requirements. Bryan
Brady, Project Technical Lead, will oversee the technical design, installation, configuration, testing, and validation of the firewall systems, while Chad Chiesa, Service Manager, will provide
operational oversight to ensure long-term support and sustainability.
Christopher Elisea, Radcomp Procurement Specialist, will manage equipment and licensing procurement in accordance with grant requirements. On behalf of the City, Nick Snead will serve as
the City of Madras Project Point of Contact, providing internal coordination, approvals, and communication between City departments and the project team. This structure ensures clear
accountability, technical expertise, and effective project delivery.

c) Please describe how this capability will be maintained.
This capability will be maintained through ongoing management, monitoring, and support
provided by the City of Madras’s managed service provider. Routine activities will include regular
security updates, configuration reviews, license renewals, and continuous monitoring to ensure
the firewall systems remain current and effective against evolving threats. Documentation and
standardized configurations developed during the project will support consistency over time, and
City staff will remain engaged through coordination with the service provider to ensure the
solution continues to operate securely and reliably beyond the grant period.

d) In 2 or 3 words, name your project: Phase 2 Firewall Project

Email your applica�on to [email protected]. Applica�ons will be pulled
and reviewed quarterly.

~end~

CITY OF MADRAS
Request for Council Action

Meeting Date: March 10, 2026
To:

Mayor and City Council Members

From:

Keli Pollock, City Recorder

Through:
Subject:

Designation of Administrative Approval Authority During City Administrator
Vacancy

TYPE OF ACTION REQUESTED:
Approve
MOTION(S) FOR CONSIDERATION:
That the Council designate the Mayor (or alternate) as the administrative approval authority for
City Administrator direct report functions, including timesheet approvals, leave requests, and PCard expense approvals, during the City Administrator vacancy.
OVERVIEW:
With the recent vacancy in the City Administrator position, several routine administrative
approvals that are normally completed by the City Administrator currently lack a designated
approval authority.
These functions primarily include the review and approval of timesheets, leave requests (sick
and vacation), and P-Card expense reports for staff who would normally report directly to the City
Administrator. Establishing a temporary approval authority will ensure administrative continuity
and allow routine operational processes to continue without delay during the vacancy.
Council may choose to designate an approval authority until such time as an interim or
permanent City Administrator is appointed.
STAFF ANALYSIS:
The City Administrator typically serves as the approving authority for administrative functions
related to direct reports. In the absence of a City Administrator, staff are requesting Council
direction on how these approvals should be handled during the vacancy.
Designating a temporary approval authority will provide clarity for staff, maintain appropriate
internal controls, and ensure routine administrative processes such as payroll processing and
expense reconciliation continue in a timely manner.
FISCAL INFORMATION:
N/A
SUPPORTING DOCUMENTATION:
None
Page 1 of 2

Request for Council Action

STRATEGIC GOAL:

Page 2 of 2

Request for Council Action

CITY OF MADRAS
Request for Council Action

Meeting Date: March 10, 2026
To:

Mayor and City Council Members

From:

Keli Pollock, City Recorder

Through:
Subject:

Review and Approval of City Administrator Recruitment Position Profile

TYPE OF ACTION REQUESTED:
Approve
MOTION(S) FOR CONSIDERATION:
• That the Council approve the proposed City Administrator Position Profile as presented;
or
• That the Council approve the Position Profile with edits discussed by Council and direct
the City Recorder to coordinate with Prothman to finalize and release the Position Profile
for recruitment.

OVERVIEW:
As part of the City’s recruitment process for the City Administrator position, the City has engaged
Prothman, a professional executive recruitment firm, to assist with the development and
administration of the recruitment.
A key step in the recruitment process is the preparation of a Position Profile. The Position Profile
serves as the primary recruitment document and includes information about the community, the
organization, the position responsibilities, desired qualifications, and recruitment timeline. This
document will be used by Prothman to market the position and provide information to prospective
applicants.
Prothman prepared the draft Position Profile based on discussions with City representatives and
information about the City of Madras organization and community. Council review and approval
of the Position Profile is requested prior to the recruitment being formally launched and
applications being accepted.
STAFF ANALYSIS:
Reviewing and approving the Position Profile allows Council to ensure the document accurately
reflects the expectations, priorities, and qualifications desired for the City Administrator position.
Once approved, Prothman will finalize the document and begin the recruitment process,
including advertising the position, distributing the profile to potential candidates, and accepting
applications.
Page 1 of 2

Request for Council Action

Council may approve the document as presented or provide edits and direction for staff to
coordinate with Prothman to finalize the Position Profile prior to release.
The draft City Administrator Position Profile is currently undergoing final edits with Prothman and
is not included in the published packet. Once the updated document is received, the packet will
be updated and reposted to include the attachment. If timing does not allow for reposting prior to
the meeting, the document will be provided to Council for consideration at the meeting.
FISCAL INFORMATION:
SUPPORTING DOCUMENTATION:
Attachment Pending - Draft Position Profile
STRATEGIC GOAL:

Page 2 of 2

Request for Council Action