Forest Environmental Management Systems

Another Support System: EMS Webware

Earlier this week I began my exploration of and about GreenWare Environmental Systems. I first dug up a few names at EPA. My intial (and so far only) contact in EPA asked me whether I found anyone actually using GreenWare. The idea I got was that while the file management package at GreenWare was very good, the system they had tried a couple of years ago was quite restrictive and not very forgiving as to documents/records developed elsewhere.

Then they told me about another group called EMS Webware (affiliated with Univ. of Massachusetts, Lowell) who had worked up a system that was perchance more flexible and adaptable. So I called them and they reiterated the same story, and suggested that they had only begun to develop EMS Webware when they found off-the-shelf systems too confining.

In their Feb. 2005 commencial software announcement the EMS Webware folks say:

…The program helps organizations build and implement an environmental management system (EMS) to enhance environmental performance.

University developers from the offices of Environment Health and Safety and Commercial Ventures and Intellectual Property office worked together to create EMS WebWare.

“It provides the tools required from beginning an EMS, to building teams, tracking documents, creating documents, providing links, to providing the security and IT support,” explained Rich Lemoine, director of the Environment Health and Safety office.

EMS programs were introduced by the EPA to promote environmental policy at universities and other public agencies. The International Organization for Standardization (ISO) recommends a model for environmental performance called ISO 14001, which is used by large corporations and from which EMS Webware is modeled.

Conservative business projections have the software bringing in some $750,000 to the university over five years, according to Susu Wong, UMass Lowell's licensing associate and chief marketer of software. Customers would likely include other universities, as well as municipalities and EMS training providers.
UMass Lowell says Beta testers included the city of Lowell, the University of Rhode Island and the Toxics Use Reduction Institute.

“It had to be user-friendly. It had to adapt to any organization,” said Lemoine. “Basically what the system does is say, ‘Here are 17 templates and you can bring in any documents.'”
UMass started working on Webware in 2001 after finding difficulties implementing its own EMS on campus.

“The other systems out there, they weren't flexible, and they weren't going to meet the needs of our institution,” Lemoine said.

UMass Lowell provides all technical support for the software package and its server will host and retain all information organizations might need for future audits or agendas, he said.

So although we will still work to better understand GreenWare, we are in the process of looking further into EMS Webware too. It may be that GreenWare was never as inflexible as the UMass folks say, or it may be the it was but no longer is. In any case we want to investigate at least these two systems and hope to find more. Clearly we need 'something.'

EMS Support Systems: What do we use? What should we use?

A couple of days ago I saw a copy of a spreadsheet tracking legal and other requirements for EMS. What struck me, other than the immense size, was the interrelationship between that document and operational controls and other elements of the ISO standard. Then it hit me, again: Why aren't we using relational databases in our EMS work? Everything is tightly linked together, and trying to sort out all relevant linkages every time something is changed will likely prove futile, or at minimum very expensive and time-consuming. Why are we are cobbling together random spreadsheets, word documents, etc. with little thought given to their interconnectedness?

I remembered that Chris Miller, from the CAT (Content Analysis Team) had suggested that I look at a software package by GreenWare Enviornmental Systems that has been used by many:

Sample Client List:
• Environmental Protection Agency (40 Sites)
• Royal Dutch Petroleum Company (Shell)
• TRW
• ITT Automotive
• Environment Canada
• Tri-County Metropolitan Transportation Authority
• Texas Natural Resource Conservation Commission
• Solvay Polymers, Inc.
• Toshiba International Corporation
• Dupont Canada Inc.
• Dell Computer
• US Department of National Defense
• Inco Ltd.
• Local/municipal governments

GreenWare Government Clients:
• Air Armament Center
• Atlantic Canada Opportunities Agency
• U.S. Department of Energy - BWXT Pantex
• Canadian Forces Base Kingston
• Canadian Forces Support Unit
• Clean Water Services
• Defence Construction Canada
• Department of Homeland Security - Customs and Border Protection
• Department of National Defence HQ
• Environment Canada
• Fort Riley Directorate of Environment and Safety
• Greater Pretoria Metropolitan Council (GPMC)
• Ontario Ministry of Environment and Energy
• Public Works and Government Services Canada
• U.S. EPA (40 Facilities)

In my preliminary look at their approach to EMS, I found that not only does the GreenWare system appear to be entirely compatible with our approach to EMS, but it even includes a "guidebook" or "manual" as they call it to conveniently co-locate all elements of the standard to serve as a basis for working the EMS. It even has spreadsheets for proving up on significance of environmental aspects. Furthermore there is a fully integrated calendar to help schedule all. Finally it seems relatively inexpensive.

So why won't we use it, or another compatible off-the-shelf system (or use one that is primarily off-the-shelf with a contract for enhancement)? Maybe we will, someday. But there seems to be little overt attention being placed to the acquisition of such software right now. Or at least there is little attention that I know about. Why not?

Are so steeped in "event mentality" – doing things once, postponing thought until after "the event" about continued do-ability of whatever it is we are attempting – that we forget that some things need to be designed simply, and inter-connectedly so that we can continue to use them (and improve them) from the moment they are turned on.

Have we been trained by forest planning and other nearly endless "events" that we have forgotten that organizations run best when run simply, while recognizing the complexity of the surrounding environment?

In any case, Why aren't we talking a lot about the urgent need to acquire or devleop adequate system-support for EMS?

For more, see Chris Miller's post in our EMS Support Systems blog.

Blogging in Government: Catch the Wave

Andy Budd is a blogger in the UK. He recently shared his "take" on Blogging in Government (Dec. 8, 2005). Here are Budd's key findings:

• …weblogs were great for internal communication and a way of cutting down the huge weight of email most large companies are drowning in.
  
• …weblogs were essentially free (or very cheap), lightweight and disposable content management systems.
  
• …blogs could be used for internal knowledge management, by encouraging key staff to blog their collective knowledge rather than keeping it locked up.
  
• …benefits of blogging to management ... how staff blogs could help managers know what was going on in their organisation. Conversely, it would also let staff know what their manager was doing.
  
• …governments could use external blogs to connect with the people they served. An external blog could really help demystify the workings of government, while at the same time creating a sense of empathy and trust.

Read "the rest of the story" for Budd's advice on prudent use and managment of blogs and bloggers:

Thoughts on Public Outreach and Information Systems

On the National EMS conference call yesterday I heard talk of Region 2 public outreach for EMS. That is a move in the right direction, as I understand the NFMA Rule. In my reading, the collaboration mandates of the 2005 Rule do not bypass any EMS we may establish. The Rule requires our EMS to include "the land management process." This reading is why I believe that forest plan evaluation and monitoring will be addressed in the EMS as well, adding a findings of significant aspects, etc. to whatever we might have otherwise envisioned E & M. We have our work cut out for us, in order to make our work meaningful and ever-better while not once-again over promising and under delivering which will keep us in court battle Hell.

I also heard talk of setting up an intranet repository for EMS documents, spreadsheets, etc. This brings up an interesting predicament. The Data Quality Act requires that our methods, data, etc. be open to inspection, suggesting internet data and information systems. Why would we have both? Sure we’ll be exposing some half-baked stuff to public spotlights, but that might help the public better understand the complex and emergent nature of our work. It might actually help us tell our story instead of hindering us, as many likely believe. I maintain that personnel records, some archeological records, etc. ought to be the stuff of our intranet and all else ought to live in an open fishbowl of public access and engagement.

Last week I was discussing our penchant for secrecy with Steve Ruddell at our EMS training. I noted that public interest groups are always suspicious of our secrecy. Collaboration practitioners often lampoon such secrecy as Jack in the Box public involvement—where a government agency holds a public meeting, plays some music prior to popping out of box to announce something, then gathers information and feedback, only to go back into the box and pop out later to repeat the process. I think that open is better. What do you think?

Minor quibble: While we are addressing inter- v. intranet, I might as well air a concern that came to mind recently. I noticed that some files now stored in team rooms are labeled “proprietary,” owned by some of our contractors but made available to government employees via special agreement. I suspect there are moral, if not legal questions associated with the keeping of so-called proprietary information on government data storage systems. I wonder how such will fare in the court of public opinion? In the court under FOIA? Maybe what we are doing on this front is fine and good, but at least we ought to talk about it. Why not have the contractors store such on their sites, and find means of allowing some restricted access?