Semi-wireless instruments, failures, historian costs
Readers weigh in and ask questions about articles and multi-media
Re: Back to Basics: Using 'semi-wireless’ instrumentation, Nov. 2009
I recently completed a semi-wireless installation and my research had revealed exactly what you discussed in your column. I was hoping to find a total wireless solution for a radar level transmitter on a remote fuel oil tank. Because of the power requirements of radar level transmitters, a complete wireless solution was not economical considering the cost of a solar panel and rechargeable battery setup. Fortunately, an existing 120 Vac circuit ran underground past the tank to receptacles at the unloading platform.
The power source originates from an unmanned pump house located about 200 feet from the tank. This project was prompted by a safety concern for steam plant operators who had to trudge out to the tank once a shift, often through knee-deep or higher snow, climb the stairs to the top and 'stick’ it.
Scott A. Somers, process control engineerKatahdin Paper, East Millinocket, ME
Get what you pay for
Re: Opinion: Do you need a $60,000 process historian? One SQL expert says no, 03/26/2009 News
I would like to know who’s process historian are you buying for $5k and how many tags. I doubt you are going to buy a historian with a “full blown” SQL Server 2005 for $5k from Rockwell, OSI PI, GE, Wonderware, or any of the other people that play in the large process area. So, give some examples.
Darren Ash, engineer, Birmingham, AL
The way I see it, it’s a matter of choice: On one hand there are proprietary historians that have made most of the important choices for you, leaving a few “wizards” and dialog boxes to complete a configuration. This is a perfectly valid pick for companies that have minimal requirements and just want to plug it in and move on. On the other hand is the increasing number of tech-savvy companies that want their historian integrated deeply and seamlessly in their corporate processes. Sure it takes a little more up-front effort, but such companies realize that the dividends pay out perpetually, making the additional effort extremely rewarding.
Dennis Runo, system integrator, Mesa, AZ
Nice try but I think you missed the mark with this one. A process historian can be had for as little as $5,000 and that includes a full copy of MS SQL Server 2005. But the author oversimplifies the effort involved in creating and maintaining a process historian. How long would it take to create 10,000 tag references in his $5,000 system? What happens if the applications in the field change? Sure you can create your own database and use SQL inserts but there is a value in having an optimized data schema. It’s like comparing a little red wagon to a minivan. If a company’s data is so insignificant that it is only willing to invest in a wagon, it should reconsider why it’s collecting the data in the first place.
Customer investment is difference
Re: How to avoid project failure, Nov. 2009
My company was the system integrator for a network of military-deployed communication vehicles. While [the prototype] stage was a success, the effort was ultimately scaled back and put on hold. Of the reasons you listed, two stuck in my mind. First was a lack of client involvement and second was frequent changes in requirements and specifications. The client was flaky and non-committal to some decisions early on, and it was reflected in the constant revision of system documentation and the comments after reviews. Even after prototyping, key components were still being hashed out. This, of course, describes the second point of changing requirements and specifications. At the time, our engineers’ fingers were pointed at our customer. I realize now, through the experience and as a pupil of project management, that the burden of failure fell just as equally, if not more so, on our own management. Failure to take some of the steps you describe diminished our ability to work with the customer effectively and define project goals. I wish my managers had a crystal ball, or this article.
Domenic De Rubis
Video tutorials provide basics
Re: CEtv Video instrumentation tutorials
I really appreciate your videos in basic principles for sensing, measurement, and control. They clearly demonstrate concepts useful for those entering a field or just needing an occasional refresher.
Kim Fowler, president
IEEE Instrumentation & Measurement Society
Case Study Database
Get more exposure for your case study by uploading it to the Plant Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.
These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.
Click here to visit the Case Study Database and upload your case study.
Annual Salary Survey
In a year when manufacturing continued to lead the economic rebound, it makes sense that plant manager bonuses rebounded. Plant Engineering’s annual Salary Survey shows both wages and bonuses rose in 2012 after a retreat the year before.
Average salary across all job titles for plant floor management rose 3.5% to $95,446, and bonus compensation jumped to $15,162, a 4.2% increase from the 2010 level and double the 2011 total, which showed a sharp drop in bonus.