1 / 13

Enterprise Approach to Environmental Management Tools

NAS Patuxent River Environmental Department. Enterprise Approach to Environmental Management Tools. April 2004. Larry Donmoyer, Ph.D. Env. Compliance Division Director NAS Patuxent River Environmental Dept. Larry.Donmoyer@navy.mil. What is an Enterprise Approach?.

kailani
Download Presentation

Enterprise Approach to Environmental Management Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. NAS Patuxent River Environmental Department Enterprise Approach to Environmental Management Tools April 2004 Larry Donmoyer, Ph.D. Env. Compliance Division Director NAS Patuxent River Environmental Dept. Larry.Donmoyer@navy.mil

  2. What is an Enterprise Approach? • Develop tools, data and processes that support the entire Enterprise – vice, stove piped solutions • Functional approach: develop a Compliance process at Pax River that fits within CNI vision • Technical approach: develop web based solution to comply with: • NMCI • Task Force Web • FAM

  3. A Little Background • NAS Patuxent River – the NAVAIR RSIP Program was the leader among Navy claimants in the area of Enterprise-wide installation and environmental management • Commander, Naval Installations (CNI) • Consolidated all major claimants • Currently in a significant application rationalization program • Near completion selecting enterprise environmental program requirements app • Will soon address compliance and other environmental functions NAS Patuxent River Environmental Department &

  4. Command-Level Environmental Business Scope Source: 2003 N46/NIPSO Environmental BCA Decision Brief Provide Environmental Compliance Plan & Program Budget Execute • Assess requirements • POM – request funding to satisfy requirements • Develop approved projects list • Emergent projects? • Rank projects • Submit budget request to comptroller • Distribute funding to region • Execute • Collect obligation and expenditures NAS Patuxent River Environmental Department &

  5. Facility-Level Environmental Business Scope (at Patuxent River NAS) Achieve/Maintain Environmental Compliance Plan & Program Budget Execute • Identify and prioritize requirements • Develop POAM • Submit budget request/justify need • Leave room for emergent projects • Execute tasks via work items • Evaluate executed vs. planned We try to fit the CNI vision

  6. Plan & Program • Plan = Compliance Tracking Tool used for identifying and prioritizing Compliance tasks. • Program = Develop a schedule or plan of action and milestone (POAM) NAS Patuxent River Environmental Department &

  7. Compliance Tracking Tool • Helps with reasonable decision making, work execution • Process for conforming to Compliance budget requirements • Identify and prioritize tasks • Recurring vs. Non recurring • Define tasks in terms of what work (steps/actions) needs to be done NAS Patuxent River Environmental Department &

  8. Budget • Scheduled tasks require resources. • If resources don’t come, must “re-program” • All based on Compliance • Are we Compliant? • What tasks must be completed? • Can we live with budget? NAS Patuxent River Environmental Department &

  9. Execute • Create work item to complete task • Evaluate how we did = compare to planned & programmed NAS Patuxent River Environmental Department &

  10. Compliance feedback loop Plan &Program Budget Execute If resources not provided Evaluate executed vs. planned – how did we do? NAS Patuxent River Environmental Department &

  11. Challenges of developing in enterprise environment • Difficult to develop sound improvements in a continuously changing environment • New requirements emerge • Mitigation: Define existing and anticipate future requirements before applying the technical solutions • Should we wait to develop when change decreases? • Mitigation: Implement improvements that offer the highest return on investment

  12. Lessons Learned in Enterprise Environment • May not be able to grow when resources reduced, but opportunities for improvement still exist • Focus on increasing efficiencies (i.e. decrease job time) • Continue to gather data that will justify resources • Compliance priorities • Get into planning mode • Proactive instead of reactive • Maintain bigger picture approach (Enterprise) • Develop a “common vision” of the functional requirements • Long term vision favors web based environments

  13. Benefits of Enterprise Approach • Updated technology based on common, recognizable processes • Improved justification of environmental budget requirements • Planning = prevention instead of reaction • Informed decisions based on reasonable data • New development critical to environmental performance and across enterprise

More Related