1

C E T A SC E T A STriage Presentation, Date

Project NameProject location (city, county)

ODOT Key Number:

2

Project Team (limit to persons in attendance - list name, title, affiliation)

• ODOT Lead

• Local Jurisdiction point of contact

• Other present team members

3

Project Vicinity

• Include a vicinity map here (Oregon Map with a Star on it, or a Regional map with a star on it)

• Label nearest city or community• Label County and Highway names as appropriate

4

Area Context and Features

The information listed on the Area Context and Features slides may be included in the API map and simply described to the group if the area is small enough

• Urban or Rural?

• Highway Infrastructure and context

• Major geographical features

• Topography

5

Area Context and Features, cont.

• Land Use, Zoning, Park/Rec. Areas

• Land-owners (federal, county, private?)

• Surface water features

6

Area of Potential Impact

• Include a Project Area map here (with API outlined)• Label major roadways • Label major surface water features • Show city limits and urban growth boundaries

7

Transportation Problem

• A Problem Statement is provided in the Part 2 of the Prospectus, the Scoping Notes for the project, and/or the Part 3. This is the foundation for the P&N statement. A large aerial of the project corridor(s) should either be inserted into the Power Point presentation or posted on the wall to help facilitate this brief introduction to the transportation problem.

8

Draft Purpose and Need

• Draft Purpose Statement in full• Need (Summarize need in bullets)

– Safety– Congestion– Capacity– Connectivity– Failing bridge, etc.

9

Potential Solutions

• You can insert drawings (one per slide), or just list by name and describe (and provide hand-outs if needed). Naming alternatives with some sort of descriptive title rather than just 1,2,3 or A,B, C is useful.

10

Project Status

• Public involvement - Discuss known or potential controversy

• Early agency coordination/Site visits• Meetings – Stakeholder meetings, Steering Committee

meetings, etc.

• Planning history & other projects in area (that would be helpful for understanding the context within which the project is being developed)

• Environmental Work – Has reconnaissance report been completed? What environmental work is in progress – what is planned?

11

Known Constraints• After the Purpose and Need test is applied, these will constitute the

next level of screening criteria or the “pass/fail” test. • What, outside of the Purpose Statement, must an alternative

achieve to be considered “reasonable” or “practicable”? List those items. – Critical Community objectives– Access requirements– etc…

• What must an alternative avoid in order to be considered reasonable?– Elements that would preclude critical community objectives or access

requirements – Creating new safety problems– Unmitigated Superfund sites– etc…

12

Known Resources

• For each bullet, identify source and approximate date of information • If known, indicate how the resource could be impacted by the project• This is coarse-level information derived from most recently available

data/inventories and verified through expeditious ground-truthing.

• ESA species and critical habitat (designated and proposed)

• ORNHIC resources• Other important fish, wildlife, plant species• Wetlands / Estuaries• Riparian Zones

13

Known Resources, cont.

• Special Areas of Concern (incl. 303d listed waters)

• Unique or rare habitat features

• Water Resources/Coastal issues

• Historic and archaeological resources

• Section 4(f) and Section 6(f)(3) resources

14

Resource Maps

• This is optional, but recommended. • Archaeological resources should not be identified on maps. Rather,

a general location of archaeological resource areas to be avoided should be verbally described during the triage presentation.

• Provide Resource maps if any have been prepared as part of the reconnaissance effort. Such maps would show general locations of known environmentally sensitive areas (nests, wetlands, critical habitat, historic structures, etc.)

15

Land Use Issues

• Consistency with Oregon Highway Plan

• Consistency with State Planning Goals• Consistency with Regional and Local

Plans (for Metro areas, this would include the fiscally constrained RTP and TIP)

16

Schedule

• Anticipated schedule for project development and construction (just major milestones: EA/DEIS, decision, REA/FEIS, prelim/final plans, ROW acquisition, permits, bid let)

• Next Steps

17

CETAS issues and concernsThis should be a round robin raising issues and concerns and providing

input on how CETAS should participate. The CETAS coordinator should document “sound bites” from each CETAS member in the notes

• USACE• EPA• FHWA • USFWS• NMFS

• DSL• DEQ • ODFW• SHPO• DLCD

18

Follow up and Action Items

• Confirm next CETAS step(s)