My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
INSPEC43150
DRMS
>
Back File Migration
>
Inspection
>
INSPEC43150
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/2/2012 8:32:01 AM
Creation date
11/18/2007 11:30:19 AM
Metadata
Fields
Template:
Non-Permit Documents
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
5
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
~~. <br />nearly finalized. DMG will complete its review of draft, and get our comments to Larry Kline. <br />OSM will generate a clean copy which will be sent over to the Colorado Mining Association <br />(CMA) for their comment. They will have ten days to comment. Any comments they have will <br />be incorporated, and the final letter sent out. Larry Kline and Susan Burgmaier will iron out <br />final details on presentation of the letter -joint letterhead, no letterhead, etc. <br />EY 1997 Plan <br />DMG presented topics selected by DMG staff for special focus in EY 1997. They were: <br />Category: Successful Reclamation <br />Topic: Topsoil Conservation <br />Category: Successful Reclamation; Protection of Public Health <br />Topic: Mine Waste; Waste Piles <br />Category: Public Participation <br />Topic: Public Meetings and Workshops <br />The Team agreed that it would strive to have the EY 1997 plan in place by October 1, 1996. <br />Permitting Oversi ht rogrammatic Issues <br />DMG expressed the view that permitting oversight is not in the plan for EY 1996, and that <br />permitting reviews could be addressed by selecting specific topics for upcoming evaluation years. <br />OSM expressed the view that DMG's approach "ties OSM's hands" when there are concerns with <br />programmatic issues. <br />OSM stressed the importance of the Team establishing a mutual understanding, there being trust <br />within the team, being able to air bad feelings, and having the ability to discuss issues informally. <br />The team discussed the difference between "technical" and "programmatic" issues. OSM's <br />description of each term was: <br />Technical -Division decisions with which OSM might not agree, but are not contrary to <br />approved program. OSM does not need to be involved in techmcal matters, other than <br />as a feedback mechanism. A technical issue would not carry the weight of a <br />programmatic issue. <br />Programmatic -outside of the approved program; e:g. Division did not make a required <br />finding, operator did not provide required information. <br />The team discussed means of communicating and resolving issues, and decided that the following <br />approach would be implemented. <br />When OSM identifies issues, they are forwarded to Mitch Rollings. Mitch can then <br />discuss them at Oversight Team meetings, or forward them to Susan Burgmaier. <br />The type of res onse expected from DMG will vary - <br />- Technical rssues will be provided to DMG to respond when convenient, or <br />be provided for DMG's information only, requiring no response. <br />Programmatic issues will be identified as such by OSM, with an indication <br />of the expected response timeframe. If the DMG response is not <br />
The URL can be used to link to this page
Your browser does not support the video tag.