Talk:Wisconsin/WI-LAM Discussion History

< Talk:Wisconsin
Revision as of 21:30, 24 April 2017 by Lonewolf147 (talk | contribs) (Created new page describing the WI LAM role)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The state of Wisconsin has initiated a program called Large Area Manager (LAM), which is an accepted program in the Great Lakes Region (GLR).

This initiative divides the state into five "zones", closely related to the state DOT regional areas. The zones for each state are designed by the SM and RC, and while using the DOT regions as a starting point, they may not be applicable to a state’s needs. The zones need to have an overlap with surrounding zones of 5 to 10 miles to ensure cohesive coverage. You can view those areas on this map Wisconsin LAM Areas

To qualify for a LAM role, an editor must already be an Area Manager for 60 days. They must be of rank 3 or higher, and be recommended by the SM and approved by the RC. To remain a LAM you must maintain activity on the map and in the community on a monthly basis.

The roles of a LAM is more than just an Area Manager (AM) with a larger editing area. Although they maintain all the same responsibilities of an AM, several new ones are described below.

Establish Baseline

  • Update segments with unknown direction/clearly-incorrect names (segments from initial basemap import are very common in rural portions of the state even to this day)
  • Implement proper Functional Classification for all segment based on national guidance (the majority of counties have never been brought into compliance)
  • Ensure all segments are locked to minimum lock level appropriate for their segment type (and requesting uplock for those that they cannot currently lock themselves)

Regular Upkeep

  • UR/MP Management: perform frequent, regular User Report/Map Problem passes over their entire area in accordance with the recently-standardized UR Management System (may need to be logged into the wiki to see the new content, use your WME username/password)
  • Unlock/Update forum response: monitor Unlock/Update forum for any posts in their zone, service directly or escalate if needed
  • Construction/Closures: responsible for staying current on all major construction projects, ensuring real-time closures are entered into the system as needed. Encouraged to establish ongoing relationships with municipal/county/ODOT representatives in their zones
  • Mentoring/outreach: proactively seek out new editors and encourage them to join the community, stay in regular contact with existing editors who work within their zone and work to help them improve/expand skill sets and knowledge bases
  • Rapid Response: lead the response coordination effort for unplanned traffic disruptions in their zones (e.g., freeway closure due to major accident)


Any LAM zone can have multiple LAM’s assigned to it. Co-LAM’s have all the same basic requirements of the role and all the same responsibilities. Primary LAM's should be from the same state. Co-LAM's can be from any state. If there are no appropriate candidates for a primary LAM in the state, the SM and RC can look outside the state, and with the approval/recommendation of the other states SM.

LAM Area multi-state overlap

When determining an area it must consist of only 4 geopoints. This may cause coverage into surrounding states. LAM's are expected to get permission from that other state's SM if they wish to edit in that area. Otherwise, LAM's should remain in the state they are assigned.

Thanks to the following editors for their input and advice on the LAM initiative in helping design this policy: TerryPurdue, poweruser10, Ruggles76, dchary2418, Jdeyoung, DaveKS14, HawkeyGoal, EdFromOhio, bill473, WarhawkTrombone, AJS17, PhoenixHawke, SWG201, Tango259