Archive for January, 2008

Measuring Flow

Saturday, January 19th, 2008

We need to measure the flow of a liquid through a pipe at work. This seems easy enough on the surface. I’m thinking…just “click” off the liquid in some measurement as it goes by…right? Well, it could be…maybe. In reality, it turns out that it may not be all that simplistic. There are other things to consider. What kind of meter should you use? There are many. What exactly are you trying to measure? What’s the density or viscosity of the liquid? Are these variable during the process? Are you actually trying to ‘regulate’ flow or ‘meter’ flow or both?

During the consideration of this task of measuring the flow of a liquid, we would need to define ‘flow’. The straight-forward definition is… the flow of material past a given location. When we dig into it further and look at actual formulas for measuring flow, it starts getting more complex.

For instance, look at this formula for ‘Flow Rate’ (FRV). This is a volume per unit time or ‘volumetric’…

FRV = V x A, where A equals the cross-sectional area of the inlet pipe and V is the average velocity of the liquid being measured. Now consider this formula in practice. We have liquid flowing through a pipe that has 2 square meters of cross-sectional area, traveling at an average velocity of 2 meters per second. So, I have a flow rate of 4 cubic meters per second.

Next, look at this formula for ‘Flow Rate’ (FRM). But this time, we will deal with ‘mass per unit time’ or a ‘mass metric’…

FRM = FD x FRV, where FD is the fluid density and FRV is our volumetric product from the first example. So, if 4 cubic meters per second of fluid is flowing through a pipe, with a density of 2 kilograms per cubic meter, your FRM is 8 kilograms per second.

Do you want to measure flow in terms of a ‘mass’ or ‘volume’? It depends on your application. In some instances the process may have a limit on the ‘volume per unit time’ measurement it can accept. Some examples might be…filling a tank, painting widgets, etc. Other processes may have a limit on the ‘mass per unit time’ it can accept…like mixing chemicals or measuring chemicals for sale.

You can see that a person can purchase a meter that measures flow in terms of volume or mass. I found that you can even buy meters that ‘infer’ volume and mass using a similar formula to ~ ‘1/2 FD x V x V’. These meters are commonly referred to as ‘head flow meters’. But, further reading indicates that this ‘inference’ approach is problematic and can introduce errors when calculating ‘mass’ flow.

Careful consideration of what you really intend to measure about ‘flow’ should lead you in the right direction when purchasing a meter. Do you want to measure velocity, mass, volume or inferential values of each?

Wade Stankich
Information Technology Manager

View Wade Stankich's Profile at Spoke

Digital Evidence and the System Admin…watch out!

Sunday, January 13th, 2008

Many companies and organizations are increasingly being faced with having to collect digital evidence in response to situations like fraud, child pornography, intellectual property theft, sexual harassment…etc. These are all examples of cyber-crimes that are happening inside, as well as outside corporate walls. This means system administrators are finding themselves having to be constantly educated on current legal issues and laws concerning the reporting and collection of evidence concerning cyber-crimes in their companies. Not only do system administrators need to preserve and collect digital evidence in these situations, but they also have to recover quickly from an incident to minimize losses.

System administrators can be caught in a potentially career damaging position. Take this scenario for instance…finding child pornography on a computer in your workplace. If you simply delete the material, this may be interpreted as being criminally negligent. If the system administrator were to alert authorities to the material before getting the support of his/her’s employer, the system administrator could find themselves fighting the company, with their own money, time and lawyer. Ultimately, this could lead to the loss of the system administrator’s job.

Even well intentioned attempts to investigate child porongraphy allegations, have left the system administrators being prosecuted for downloading and possessing this material themselves! In light of these potential hazards, companies should have clear policies and procedures that outline how to properly deal with these situations.

These procedures should inform system administrators how to handle and preserve digital evidence of this kind. The companies policies should formally state the company’s position regarding illegal digital material. Employ the help of technically competent attorneys to aid in forming your policies and continue to have them review the policies periodically to stay up to date with technological changes.

Wade Stankich
Information Technology Manager

View Wade Stankich's Profile at Spoke

Bridging the Gap Between Maintenance and I.T.

Saturday, January 5th, 2008

Over the years, it seems that past traditional roles of the maintenance department and the information technology department of a manufacturing company are (or have been) changing. The lines are getting blurred. Those guys in the ’shop’ with the wrenches need to be just as versed in techno-jargon as ‘those geeks’ in the computer room. The I.T. guys also need to understand plant operations and maintenance concepts and the language that goes along with it, too. Why?…plant automation.

Most backplanes you see on the plant floor have a multitude of different modules plugged into them besides just the PLC. Today, usually a person will find an ethernet module plugged into them. For the I.T. department this is another network device on their network. Many times an electrical engineer deploying a new machine with an ethernet module gives no consideration to an IP address that fits with the companies current scheme. They may not give consideration to broadcasting issues that can potentially bring a network to it’s knees.

Conversely, a typical I.T. department doesn’t give enough attention to what basically amounts to another I.T. department within maintenance. Most of the machines maintenance deals with have processors and can be networked today. The engineers in maintenance are skilled at programming ladder logic, and once that task is complete…it simply goes out. I.T. should be working with this department to help them successfully roll out there machinery and take on the more global considerations of the company’s network.

This cooperation of two departments, that are so different on the surface, is sometimes easier said than done. It can be a huge cultural shift for some companies. This cultural divide usually is established from the beginning because of typical organizational structures and the resulting presumptions. What I mean is, that typically the maintenance department falls under Operations and the I.T. department falls under Finance. Foundationally, the wall of separation is “…I.T. is administrative, and Maintenance is production.” This may have worked 30 years ago, but it is no longer a valid structure that serves it’s company well, or to the fullest potential.

The Maintenance department and the I.T. department need to be solidly joined at some level. Neither, falling exclusively under Operations or Finance, but working somewhere in the middle for the global good of the company. It starts with communication. Project managers of both departments meeting once a week to review projects would be a good start. At some point along the way each will realize they both share the same copper wires.

Wade Stankich
Information Technology Manager
View Wade Stankich's Profile at Spoke