Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Hacm Reporting Public Safety topic
No spam. Unsubscribe anytime.
Committee adopts resolution for biannual HACM status reports; MPD and DNS ask to narrow scope
Summary
The Steering and Rules Committee adopted a resolution asking HACM leadership to report biannually on finances, public safety and recovery plans, while Milwaukee Police Department and Department of Neighborhood Services requested clearer scope and a narrower focus on multi-unit/high-rise properties.
MILWAUKEE — The Common Council's Steering and Rules Committee on Feb. 17 adopted a resolution (file 241590) asking the Housing Authority of the City of Milwaukee (HACM) to meet with city leadership twice a year to review finances, public safety and the agency's recovery plan. Committee members and city departments said the written resolution needs to be refined before council consideration to limit the reporting burden.
Alderman Robert Baumann, the resolution's sponsor, said the intent is to "codify the communication between our leadership and the HACM leadership to come biannially and talk about the status of affairs at HACM," including public safety and finances. He moved adoption and the committee recorded the adoption after further discussion.
City departments raised concerns about the draft's scope. Heather Huff, chief of staff for the Milwaukee Police Department, told the committee she needs clarity on what MPD would be asked to provide and warned the request could be onerous if applied to every HACM unit. "If this is a requirement for us to pull something every 6 months for all HACM properties, which is over 4,000, it may be a minus 1," Huff said, adding that MPD analysts could accommodate targeted pulls if the committee supplies a defined set of addresses.
Jessa Mila Roylobega, Commissioner with the Department of Neighborhood Services, said DNS does annual life-safety inspections and can provide robust reports on orders and enforcement, but the phrase "quality index" in the resolution needs a clearer definition before the department can commit to creating one. "The quality index is a little bit harder in regards to calculations and ratios," Roylobega said, and the department asked to meet with the resolution's author to refine expectations before council day.
Committee members said they expect to narrow the resolution's scope to major multi-unit or high-rise HACM properties, rather than scatter-site or every unit, and to provide MPD and DNS with a specific list of addresses for reporting. Alderman Baumann moved adoption again later in the meeting after reconsideration; the committee adopted the resolution without objection and the sponsor said he will submit a revised file for council consideration.
Votes and next steps: The resolution (241590) was adopted by committee, and the author plans to limit required reporting to identified multi-unit properties and supply those addresses to MPD and DNS prior to council day. The resolution also schedules HACM to present at a March 14 meeting as part of the planned follow-up.
Ending: Departments and committee staff will work with the resolution sponsor to narrow the reporting request, clarify metrics (for example what DNS should include in a "quality index") and confirm the specific addresses MPD should use for calls-for-service pulls.
