5,013
edits
No edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
A Team's Service Area refers to the geographic area within which a NET administers their Operations Plan; it can be thought of as their "turf" and the area they plan to respond inside of in the event of a disaster. Most Service Areas conform with neighborhood boundaries, while others include multiple neighborhoods or a part of a neighborhood. Service Areas are proposed to PBEM by Team Leaders, and PBEM provides final approval. Service Area boundaries shall not overlap with each other | A Team's Service Area refers to the geographic area within which a NET administers their Operations Plan; it can be thought of as their "turf" and the area they plan to respond inside of in the event of a disaster. Most Service Areas conform with neighborhood boundaries, while others include multiple neighborhoods or a part of a neighborhood. Service Areas are proposed to PBEM by Team Leaders, and PBEM provides final approval. Service Area boundaries shall not overlap with each other; "enclaved" Service Areas are acceptable., but "exclaved" service areas are not.<span style="color:#ffffff">...mm</span> | ||
__TOC__ | __TOC__ | ||
<p><span style="color:#ffffff">...</span></p> | <p><span style="color:#ffffff">...</span></p> | ||
== Background == | |||
Service Area policies changed several times since Portland NET started in 1994, often reflecting the reach of the program and interests of volunteers. In the first years of NET, Service Areas conformed with [[Portland Fire & Rescue|Portland Fire & Rescue fire management areas]] (FMAs). As the number of NET volunteers increased over the years, Service Area boundaries shifted to follow Portland's neighborhood system. That is how most Service Areas boundaries are drawn today, but PBEM encourages teams to reconsider their boundaries and "right size" them to match resources and team priorities. Creating more nuanced boundaries is also more plausible than in past years thanks to the use of GIS mapping systems. |