Lexicon Systems, LLC Blog

lex'•i•con: the vocabulary of a branch of knowledge. Thoughts on environment, health & safety (EHS), sustainability and information technology to support them.


Leave a comment

Energy sector looks to integrated EHS IT solutions to manage risk in a complex operational and regulatory enironment

We are in the midst of a 21st Century energy boom. It has created thousands of jobs and reduced the U.S. dependence on imported crude oil. New technologies like horizontal drilling and hydraulic fracturing (fracking) create new opportunities as well as risks. In light of recent offshore and onshore incidents in the energy and chemical industries, regulatory agencies are in the midst of making new policies and rules. How do organizations keep up with this complex, dynamic business environment?

“Risk is an integral component of a safety culture. It must be the lens through which we view the interaction between technology and the human element.”
–Brian Salerno, BSEE Director

Most organizations use spreadsheets, email and documents to manage environment, health & safety (EH&S or EHS) data. Even those that use more robust information technology (IT) platforms admit that they do not use IT to its fullest.

To better collect, manage, and use EHS information, many energy companies are migrating to integrated EH&S software applications for the first time. Others are taking a hard look at replacing legacy systems with more robust IT platforms.

The latest IT Insight column, 21st Century Energy Boom and Greater Risk Awareness Drive EH&S Software Initiatives, describes the pressure that the energy industry faces in managing mountains of EHS data while also minimizing the risks associated with everyday business. The column describes lessons learned in the Gulf of Mexico and a new risk management approach that is taking hold. Read the full article here.

Advertisements


Leave a comment

Learn from the experts and share best practices at September Sustainable Performance Forum

I am pleased to announce my upcoming presentation, “Business Requirements and Software Selection Best Practices” at the Sustainable Performance Forum, 25-26 September in Chicago, IL. The #Enablon #SPF Americas 2014 program features thought leaders on environment, health & safety (EHS) and sustainability, information technology (IT), and Risk. 

Former NASA astronaut, navy fighter pilot and test pilot and Boeing Chief Technical Pilot John O. Creighton will deliver the keynote talk on risk.

The Keynote panel features senior executives from industry, leading EHS subject matter experts and industry analysts. Author and writer Anna M. Clark will moderate the panel. Enablon CEO Dan Vogel, CTO Marc Vogel, Vice President Pascal Gaude and Enablon North America CEO Philippe Tesler will present their vision and company roadmap.

The Enablon team will lead program tracks on six different Enablon software solutions. Each track will include a session on issues & trends and a case study, in addition to presentations on the solution set and product road map.

Customers will have the opportunity to collaborate with subject matter experts and Enablon on future product enhancements. 

The program features two new tracks this year, beyond solution tracks and software training:

  • Technology Enablers–cross-platform, innovative information technologies
  • Implementation Strategies–best practices for business requirements and software selection; implementation, and more.

SPF also offers networking opportunities like industry roundtables and a gala dinner, and Lunchtime Expert series talks. Learn more here.


Leave a comment

$Dollars still drive EHS software decisions

A large manufacturing client of mine recently completed a software evaluation and selection process. The project stakeholders used a set of objective evaluation and selection criteria to arrive at a decision. Interestingly, these criteria did NOT include cost. If in, the final evaluation two software solutions were rated equal, then cost could be a deciding factor. My client and the software vendor were excited to move forward with implementation at warp-speed, as the clock was ticking towards internal deadlines.

Since the EHS business and IT sponsors kept the executive suite updated, it looked as if formal approval would be easy. The company had strong business drivers regardless of the project cost. Of course, no project has unlimited funds. In the end, the project was approved–only after a lot of number-crunching and many revisions to the executive presentation.

Why? Executives run the business using performance-based metrics. Most C-level executives are trained to value a project based on “hard numbers” metrics such as cost saving, cost avoidance and Return on Investment. Often, they dismiss the value of compelling “soft numbers” associated with benefits that are harder to quantify, such as making decisions based upon solid data, the ability for users to adopt (and gladly use) the software, data entry at the point of activity, and productivity gains from EHS process automation, self-service reports and dashboards.

Image

Dollars, Euros, Pounds, Yen

Prepare a compelling business case based upon a good understanding of your business. While this does not require exhaustive research, you need to know where to look.

  1. Keep it simple. Find 2-3 relevant “hard numbers” cost avoidance and cost savings examples.   These savings alone could pay for the project in 3-5 years.
  2. Consider the total cost of ownership (TCO). This includes software license/subscription, maintenance and implementation fees PLUS the cost of internal EHS and IT resources, external consultants, hardware and other expenses over the lifetime of the software. Many organizations have tunnel vision and compare only license and implementation costs; TCO allows a more realistic and credible evaluation.
  3. Avoid selecting the low-cost option just to save a few dollars. If the software fits current, near-term and long-term needs, then it may be a good option. Reread item 2 above. You may wish that you had chosen a more “expensive” option, as it would save effort and money over the life of the software.
  4. When in doubt, seek expert advice. Seek assistance if you lack the know-how to prepare a business case for C-level or Board approval. The skills needed to develop a business case are very different from the skills needed to administer the software after implementation. This expertise may lie within or outside of your organization.

While dollars still drive EHS software decisions, look at the bigger picture. You will be glad you did!


Leave a comment

Welcome to our weblog!

Welcome to the Lexicon Systems, LLC weblog. The lexicon blog  provides insights on sustainability and  environment, health & safety (EHS) issues, and the information systems and technologies that support them.

Jill Barson Gilbert, QEP
President & CEO
Lexicon Systems, LLC

©2002-2012 Lexicon Systems, LLC.