Saturday, November 3, 2012

View Your Operator Readings in an Excel Pivot Table

A powerful new feature of the FieldData Pro solution is the ability to access the data collected by your staff in a MS Excel spreadsheet with a direct connection to the database that stores your historical data.


As shown in the image above, viewing your data in a pivot table allows you to perform more powerful analyses than in a standard spreadsheet.

In our example, with just a few clicks we filtered by:
  • Parameter (pH)
  • System Type (Cooling Tower)
  • Site
  • Year
We also sorted by:
  • System
  • Employee

All of this with just a few mouse clicks.

This data is data that was collected using FDPMobile, our mobile app designed for use with barcode scanners that run Windows Mobile.

This data used to be recorded on log sheets that were maintained at the cooling tower locations. Back then, if you wanted to analyze this data, you had to start by spending half a day collecting the log sheets, carrying them back to the desk and keying them into a spreadsheet. Now this data is available for analysis as soon as it is entered into the barcode scanner.

FieldData Pro helps you put your data to good use.

Explanation of a pivot table


For typical data entry and storage, data usually appear in flat tables, meaning that it consists of only columns and rows, as in the following example showing data on cooling tower water:




While tables such as these can contain a lot of data, it can be difficult to get summarized information from them. A pivot table can help quickly summarize the data and highlight the desired information. The usage of a pivot table is extremely broad and depends on the situation. The first question to ask is, "What am I looking for?" In the example here, let us ask, "How does water pH vary in each cooling tower over time?":




A pivot table usually consists of row, column and data (or fact) fields. In this case, the column is Observation Time, the row is Point of Interest and the data we would like to see is (average of) Observation Value. The pivot table allows you to quickly filter and summarize data. This allows you to run different scenarios, compare results under different conditions and identify trends. This type of analysis allows you to use your data to solve problems and improve your operations.

Thursday, November 1, 2012

Bacon Fried Turkey

How do take something great, like deep fried turkey, and make it better?

Wrap it in bacon, of course.

We did it this Thanksgiving and it tasted even better than it sounded. The turkey maintained its moist and tender texture while absorbing some of the bacon flavor. Both the kids and adults will fight over the chunks of bacon / skin that fall off in the bottom of the carving plate.

Here is what you need:

10 pound turkey, thawed
2 pounds bacon
3 gallons canola oil (peanut oil will work also)
cooking twine

You will also need a turkey setup.

In the kitchen, wrap the turkey in strips of bacon:


Tie up the turkey with cooking twine, securing the bacon to the turkey.



Set the turkey in the frying basket:



Preheat the oil to 400 F.

Slowly lower the turkey (in basket) into the oil.

Be careful here. The oil may splatter up and get you here. I recomend the following safety precautions be taken when lowering the turkey into the oil:

Long sleeve shirt
Leather gardening gloves
Safety glasses
Use a set of channel locks or pliers to grip the basket handle.

The turkey should cook for 3 1/2 minutes per pound.

You will need to monitor the oil temperature and maintain it at 350 F while it is cooking. This may require adjusting the flame every 5 minutes or so.


After the 35 minutes or so has passed, follow the same precautions you followed when you lowered the turkey into the oil (gloves, glasses, etc) and remove the turkey (in basket) from the oil. The turkey will stick a little to the sides of the basket. Jiggle it loose and slide the bird into a pan.


Remove the cooking twine, carve  and serve.

Delicious.

Sunday, October 28, 2012

Integrating Handheld Readings with SCADA Systems using OPC

SCADA systems are used by large facilities to monitor the conditions of various equipment and systems around the facility. Most of the data displayed in a SCADA (supervisory control and data acquisition) system is real time data sent to the system by measuring devices installed around the plant. This will often include various pressure, temperature, level or flow values. By pulling all of this data into one place, the people who operate the systems can make decisions on whether their systems are working as designed, or if adjustments need to be made.

Often times there is a need to view data that is collected manually alongside the data that is collected automatically by the SCADA system. We have developed a solution to this problem.

Data collected with FDPMobile,  our handheld data collection software, can be integrated into SCADA systems by using OPC technology.

OPC stands for OLE for Process Control.

Using an OPC server, any data that is entered in our database can be viewed in the SCADA system. When the data is updated in the FieldData Pro application, the data will be updated on the SCADA system. 

This does not only apply to data collected with the handheld device. Our web application also has a web based data entry portal. This is often used to enter data from paper sources, such as utility bills or lab testing results.

Once this data is in the SCADA system, out of spec conditions of this data can be managed in the same manner that the plant manages out of spec conditions for all the SCADA system data. If your plant uses an alarm notification system such as WIN-911 from Spector Instruments, you can send out email or text messages notifying key people of out of spec events.

Monday, October 22, 2012

Integrating Handheld Readings with CMMS

FieldData Pro data collection software is designed to compliment any Computerized Maintenance Management System (CMMS). There are many good CMMS out there, and when an organization decides to implement one they normally intend to use it for a long time. You may have implemented a CMMS several years ago and it meets most of your needs, but now you wish it had mobile data collection capabilities that are just not offered. That is where we come in.

Our solution is a stand alone data management system that works well alongside most any CMMS.

In the FieldData Pro solution the primary transactional data that is collected are called Observations. Each Observation has the following properties:

  • Point of Interest ID - Defines the data point being observed
  • Observation Time - Time and date that the Observation was made
  • Observation Value - Numerical value of the Point of Interest at the time the Observation was made
  • Employee ID - Identity of the employee making the Observation

These Observations can be mapped to several different locations within a CMMS. Examples include:

  • Meter Readings
  • Inventory Levels
  • Task Completion
There are currently over 400 different CMMS types in service at organizations around the world. We have very talented data base programmers that can look at your system and write the code that puts the data collected with our data colletion software into your CMMS.



Tuesday, October 2, 2012

A Simple Naming Convention for Data Points, Assets and Equipment

Over the last 20 years I have been involved with the implementation of several CMMS and SCADA systems, as well as many data management systems like our own FieldDataPro solution.

Without fail, one hurdle that shows up early in every project is what should we can the assets, in the case of a CMMS, and what do we call the data points that describe these assets in the SCADA or data management system.

Any naming convention should have the following goals:


  • The names should be intuitive. A user should be able to look at one asset or data point name and be able to tell what it is describing. The user should also be able to look at an asset name and guess what the name of a similar asset is.
  • The name should include hierarchical references to locate where the asset or data point is in the system.
  • The name must be distinct. 


There are several standardized naming conventions in use today in industry, but none of them met our requirements, so the FDP Naming Convention was created.

The FDP Naming convention creates names by concatenating abbreviations the following parts:

Location (Either site or building, whichever is appropriate)
System (Everything is a part of a system)
Equipment (if necessary)
Parameter (for data point naming)
Parameter Descriptor (if needed to help identify the Parameter)

The parts of the name are separated by either underscores(dashes or periods may also be used).

For example, on our North Campus we have a chilled water system. This system has several chillers. If we wanted to create an asset name for the first chiller on the system, it would be:

NC_CHW_Chiller1

The chilled water inlet temperature for this chiller would be:

NC_CHW_Chiller1_T_In


The chilled water Outlet temperature for this chiller would be:

NC_CHW_Chiller1_T_Out

Many data points describe the system as a whole as opposed to individual assets that are part of the system. In these cases we leave out the Equipment portion of the name. Following our example above, the name for the pH of the chilled water in this system would be:

NC_CHW_pH

Some data points describe properties of the site as a whole. In these cases we would leave out the System portion of the name. Following our example above, the name for the outside air dewpoint for the entire campus would be:

NC_DP_OA


Adopting this naming convention, or a similar convention, makes using your CMMS, SCADA or data management system easier for the end user. It is easier to search for data. It is also easier to identify which data is being represented in a trend, which asset is being referred to on a work order.

Including the hierarchical information in the name also makes it easier to relate different assets together, and to relate data points to assets to systems to locations.


Friday, April 27, 2012

Monthly Testing of Emergency Lights

Background

Section 1910.36 of the Occupational Safety and Health Act requires among the other things: In every building or structure equipped for artificial illumination adequate and reliable illumination shall be provided for all exit facilities.

Testing Requirements

Testing requirements for emergency lights are defined in NFPA - 101 Life Safety Code Section 7.9.3 Periodic Testing of Emergency Lighting Equipment.

This section includes provisions for equipment that must be tested manually as well as self-testing / self-diagnostic equipment. For equipment that requires manual testing, a functional test shall be conducted on every required emergency lighting system at 30-day intervals for a minimum of 30 seconds. An annual test shall be conducted for the 1-1/2 hour duration. Equipment shall be fully operational for the duration of the test. Written records of visual inspections and tests shall be kept by the owner for inspection by the authority having jurisdiction."

It has been our experience that the primary failure mode for emergency lights involves the batteries. The minimum 30 second test duration is important because many times a light with bad batteries will illuminate initially when the test button is pressed, but fail within 30 seconds. Also, the focus of the 1-1/2 hour annual test is to determine if your batteries are strong enough to illuminate during an extended emergency period.

Frequency

As described in the paragraph above, 30 second functional testing shall be conducted at 30 day intervals.

Functional testing shall be conducted monthly with a minimum of 3 weeks and a maximum of 5 weeks between tests.

1-1/2 hour duration testing shall be conducted annually.

Testing Instructions

The following is an example of how the task instructions may be written in your computerized maintenance management system (CMMS).

  1. Visually inspect emergency light for signs of damage.
  2. Press test button and hold for 30 seconds.
  3. Verify that emergency light illuminates for entire time test button is pressed.
  4. Record inspection results.
  5. Initiate corrective action for deficiencies identified during inspection.
Required Tools and Supplies

Barcode scanner to quickly record inspection results
Stick to press hard to reach test buttons (optional)
Step ladder (optional)

Labor Time Requirements

It should take less than 1 minute to actually conduct a monthly functional test. However, the following must be considered when estimating labor time requirements for conducting monthly testing:

  • Labor estimates should include travel time to each emergency light.
  • In our experience, 5 minutes per emergency light, including travel time, is a good initial estimate for most commercial buildings. This estimate can be refined using actual data after the testing has been conducted a few times.
  • If a step ladder is required the labor estimates will need to be higher than with no step ladder.
  • Emergency light testing may also be combined with Lighted Exit Sign testing, which has very similar requirements.
  • Some organizations assign this testing to electricians, however it can be conducted by any conscientious employee who has been trained to perform the testing correctly.
Recording Test Results Using FieldDataPro

Managing the testing of emergency lights scattered around a large facility or campus can be challenging. FieldDataPro can help you use barcode technology to track when each unit is inspected and more importantly, identify units that are not inspected or have deficiencies that need to be corrected.

When collecting emergency light test data with FieldDataPro you can use either the Detailed method or the Pass/Fail method. Either method makes effective management of the testing easy and eliminates paperwork and manual record keeping.

With the Detailed method, the tester records the status of each inspection point for each unit as shown in the image below.



With the Pass/Fail method, the tester creates a timestamped record indicating that the device was tested, and whether it passed inspection or was found to have deficiencies.



For a more detailed description of how FieldDataPro can help you manage Safety Inspection data, see this blog post (how it works).


Call us at (919) 323-3703 to set up a demonstration.

For more information, email us at info@fielddatapro.com.

http://www.fielddatapro.com/

Thursday, April 26, 2012

OSHA Fines Manufacturer $46,000 for Fire Extinguisher, Emergency Exit Sign

In a June 20, 2011 news release, the US Department of Labor OSHA announced that they had cited Spears Mattress Co. in Rome, Ga for 14 serious safety violations. Penalties totaled $45,850.

The violations included improper storage of oxygen and acetylene compressed gas cylinders, fire extinguishers not mounted or identified, a malfunctioning emergency exit sign, walking and storage areas cluttered with flammables and heavy equipment, missing machine guards on equipment, a drill press that was not secured to prevent movement during operation, improperly adjusted bench grinders and allowing an employee to operate a forklift with non functioning emergency brakes. There were also several electrical code violations identified.

One of the things that a Facility Manager may find significant with this story is that it was a pop-in inspection by OSHA. There is a belief that OSHA only shows up after an incident, but that was not the case here. OSHA began this inspection as part of its Site-Specific Targeting Program, which focuses enforcement efforts on industries that report higher-than-average injury rates.

It has been this author's experience from participating (as a facility owner) in OSHA and EPA audits, that having your documentation in order is an absolute necessity for surviving these audits.

Three of the findings that this manufacturer was cited for were things that should be on periodic safety equipment inspections. These include forklifts (daily or at the beginning of each shift), fire extinguishers (monthly) and Emergency Exit Signs (monthly).

Forklifts inspections are typically documented using logbooks stored on the forklift. A great source for forklift logbooks (or any other type of logbook) is http://www.logbooks.com/. These inspections can also be documented using FDPMobile our handheld data collection software.

Managing inspections of safety devices that are spread out around a facility, such as emergency lights, lighted exit signs, fire extinguishers and eyewash safety showers is made very easy by using a mobile software like FDPMobile. Inspection results are entered into the mobile device at the time of the inspection, then uploaded to an easy to use web application, where missed inspections or deficiencies that were identified during inspections can be easily tracked. To see a case study of how the FieldDataPro solution is used to manage safety inspections follow the link below.

http://www.fielddatapro.com/case_studies/FieldDataPro_CaseStudy_book.pdf

Wednesday, April 25, 2012

Monthly Testing of Lighted Exit Signs

Background

Section 1910.36 of the Occupational Safety and Health Act requires among other things: In every building or structure equipped for artificial illumination adequate and reliable illumination shall be provided for all exit facilities.

Testing Requirements

Section 7.10.9.1 of NFPA 101 requires that lighted exit signs be visually inspected for operation monthly:

"7.10.9.1 Inspection. Exit signs shall be visually inspected for operation of the illumination sources at intervals not to exceed 30 days or shall be periodically monitored in accordance with 7.9.3.1.3 (7.9.3.1.3 discusses both manual testing of lighting as well as self-testing / self-diagnostic equipment)."

Section 7.10.9.2 of NFPA 101 dictates that exit signs with battery backup be tested monthly following the same standards as applied to emergency lighting, which are described in Section 7.9.3.

Section 7.9.3 of NFPA 101 requires that a functional test be conducted on this equipment at 30-day intervals for a minimum of 30 seconds. An annual test shall be conducted for the 1-1/2 hour duration. Equipment shall be fully operational for the duration of the test. Written records of visual inspections and tests shall be kept by the owner for inspection by the authority having jurisdiction.

It has been our experience that the primary failure mode for emergency lights involves the batteries. The minimum 30 second test duration is important because many times a light with bad batteries will illuminate initially when the test button is pressed, but fail within 30 seconds. Also, the focus of the 1-1/2 hour annual test is to determine if your batteries are strong enough to illuminate during an extended emergency period.

Frequency

Functional testing shall be conducted monthly with a minimum of 3 weeks and a maximum of 5 weeks between tests.

1-1/2 hour duration testing shall be conducted annually.

Testing Instructions

The following is an example of how the task instructions may be written in your computerized maintenance management system (CMMS).
  1. Visually inspect lighted exit sign for signs of damage.
  2. Press test button and hold for 30 seconds.
  3. Verify that sign illuminates for entire time test button is pressed.
  4. Record inspection results.
  5. Initiate corrective action for deficiencies identified during inspection.
Required Tools and Supplies

Barcode scanner to quickly record inspection results
Stick to press hard to reach test buttons (optional)
Step ladder (optional)


Labor Time Requirements

It should take less than 1 minute to actually conduct a monthly functional test. However, the following must be considered when estimating labor time requirements for conducting monthly testing:
  • Labor estimates should include travel time to each exit sign.
  • In our experience, 5 minutes per exit sign, including travel time, is a good initial estimate for most commercial buildings. This estimate can be refined using actual data after the testing has been conducted a few times.
  • If a step ladder is required the labor estimates will need to be higher than with no step ladder.
  • Emergency light testing may also be combined with emergency light testing, which has very similar requirements.
  • Some organizations assign this testing to electricians, however it may be conducted by any conscientious employee who has been trained to perform the testing correctly.

Recording Test Results Using FieldDataPro

Managing the testing of safety devices scattered around a large facility or campus can be challenging. FieldDataPro can help you use barcode technology to track when each unit is inspected and more importantly, identify units that are not inspected or have deficiencies that need to be corrected.

When collecting lighted exit sign test data with FieldDataPro you can use either the Detailed method or the Pass/Fail method. Either method makes effective management of the testing easy and eliminates paperwork and manual record keeping.

With the Detailed method, the tester records the status of each inspection point for each unit as shown in the image below.




With the Pass/Fail method, the tester creates a timestamped record indicating that the device was tested, and whether it passed inspection or was found to have deficiencies.



For a more detailed description of how FieldDataPro can help you manage Safety Inspection data, see this blog post (how it works).


Call us at (919) 323-3703 to set up a demonstration.


For more information, email us at info@fielddatapro.com.


Thursday, April 12, 2012

Structured Troubleshooting by Plant Operators

To make your Operator Rounds or Inspections meaningful, you need to:

  1. Establish criteria for each reading that defines what is acceptable and what is not acceptable.
  2. Ensure that each reading is compared to the acceptance criteria (high and low limits) each time it is recorded.
  3. Define what should be done if any out of limits conditions are discovered.

FDPMobile is a mobile application that helps Plant Operators collect data and troubleshoot problems they may find during their inspections.


In FDPMobile, for each data collection point you may establish acceptance criteria in the form of high and low limits.


High and Low Limits are displayed to Operator. All data entered is automatically compared to the limits set up for the data point.

For each data collection point you may establish up to four condition based messages that will be displayed to the Operator if data is entered that is outside high or low limits for that data point. These messages are customizable and can include instructions that you would like the Operator to follow when they find things that are not the way they ought to be.


When we work with clients to implement FDPMobile and FDP Plant (the web application that works with the mobile application), we are often asked what should the content of the error messages should be. We respond by telling them to imagine themselves as a Plant Engineer receiving a phone call at 2:00 AM from an Operator who just encountered a problem on a very critical system. What three steps would you ask them to take while they are waiting for you to get dressed and get to the plant.

By putting this information at the Operators fingertips while they are in performing their rounds we are enabling them to solve problems quickly and safely.


Tuesday, April 10, 2012

FieldData Pro Adds Ad Hoc Charting and Data Analysis

Our customers can now build ad hoc charts to easily analyze the readings collected by their plant operators.


With a few simple clicks you can analyze your data over time. Any number of Points of Interest may be trended against each other so you can see how the variables interact with each other.

Each chart is summarized with a table that details the average, min , max and count of each Point of Interest included in the chart. These charts are easily exported for inclusion in reports, emails or other documents.


FDPChart is now a standard feature of the FieldData Pro data management solution.

Wednesday, April 4, 2012

How Accurate are Your Pressure Gauges?

Almost once a week I find myself troubleshooting a problem with a water system. The majority of the times I am using pressure gauge readings as part of the troubleshooting. I have learned the hard way to be very skeptical of the accuracy of pressure gauges installed in the field. I estimate that 30% of the gauges I have encountered in the field are not accurate.

Often times the gauges I find to be inaccurate are the same ones that our plant operators record each day during their Operator Rounds. This puts into question the accuracy of much of the historical data for that gauge reading.



It is very good practice to verify the accuracy of your pressure gauges at least annually. Verifying the accuracy of gauges attached to a pump could be made part of the PM tasks for that pump.

The level of accuracy you require is up to the user. It can range from a quick check to verify that the gauge is functional and returns to zero when all pressure is removed. Or you may require the gauge to be accurate to within tenths of a pound using a test pump and an electronic calibrator like a Beamex.

Once you have verified its accuracy you should put a dated sticker on the back of the gauge to show when it was last tested.
Periodically verifying the accuracy of your pressure gauges will help ensure your operators have accurate data when troubleshooting or assessing the performance of your power plant or process system.

Monday, April 2, 2012

Operator Rounds vs. SCADA -The Cost of Adding Points to SCADA System

Plant operations professionals are routinely faced with the decision of whether to add a data point to the plant monitoring system (SCADA, BAS, etc) or add it to the Operator Rounds. For example, a manufacturing plant has been having trouble with a cooling tower pump periodically losing prime. To help troubleshoot the problem, they decide to start tracking the suction pressure of the pump. They can either add the pressure to the Operator Rounds, or add instrumentation to add it as a point to the plant SCADA system.

There are a number of factors to consider in each of these decisions. These include:

How critical is the data point?
What are the consequences if this data point goes out of spec?
Is continuous monitoring with out of spec alarming required?
Or is it a data point that if it goes out of spec for a few days will not cause costly damage?

These are very important questions and are the basis of processes like Reliability Centered Maintenance (RCM). This article does not address these questions.

This article addresses determining the cost of the SCADA vs Operator Rounds options. These decisions should always be business decisions, where a cost / benefit analysis is performed  of each option then used to help select the option that is best for the plant.

It is our opinion that the costs of both of these options are routinely under-estimated. I hope this article helps you make accurate cost estimates that are useful in making the right decision.
What Goes Into the Cost of Adding a New Point to SCADA System

For this example we will be adding a pressure sensor to the suction side of the cooling tower pump. Our plant uses a SCADA system to monitor critical system. Field devices send their signals back to the SCADA server using a plant Ethernet system. The following are items that may go into the cost of installing a new data point to a SCADA system:
  1. Cost of the measurement device. In this example we are adding an pressure transmitter ($350 - $3,000 depending on your plants requirements).
  2. Wire and conduit to get the signal from the measuring device to the sending device ($200 to $500).
  3. Power wiring for the measuring device (if needed) ($200 - $500)
  4. Cost of the sending device (if needed). If we have a PLC nearby with an available I/O then we are in luck. If not we will need to add either a PLC ($1500) or Remote I/O module with Ethernet connection($300).
  5. Wire and conduit to get from sending device to Ethernet drop (if needed). ($800 - $1500)
  6. Power wiring for the measuring device (if needed) ($200 - $500)
  7. Configure new data point in SCADA system. Assume it will take in house person 1 hour (if you have one) to add the point and configure the low and high limits ($50), contractor ($250).
  8. Add new data point to graphic screen in SCADA system. Again in house ($50), contractor ($250).
  9. Miscellaneous engineering costs. Include 4-6 hours for selecting and procuring  the correct measurement device, selecting and procuring the correct sending device, routing power and communication wiring, establishing high and low limits and implementing response protocols. ($300)
The costs quoted above are very rough estimates. Actual costs will vary at each plant. But at the very least, each of those items listed should be considered when calculating your costs for adding a point to a SCADA system.

What Goes Into the Cost of Adding a New Point to Operator Rounds

There are costs associated with adding a data point to Operators Rounds. This is true whether your operators use a clipboard and pencil or handheld data collection software like FDPMobile(http://tinyurl.com/3qykyvb) to record their readings.

 These costs include:

  1. Add new data point to paper log sheet or to handheld data collection software like FDPMobile. Assume it will take an in house person 1 hour to setup the new point and, if using paper log sheets, publish the new log sheet ($50).
  2. Operator labor time required to collect the data. This cost can vary greatly depending on frequency of data collection and location. If you can add the reading to an established set of Operator Rounds and the new point is along the route then you may consider the costs to be negligible. If this new data point can not be added to an existing set of Operator Rounds then you need to quantify the labor hours required to collect this data. In an extreme example, if the pressure gauge is in a confined space that requires 1.5 labor hours to do a confined space entry each time you read it, it could cost thousands of dollars per year to get this data.
Just like with the SCADA system, the cost of adding a data point to Operators Readings varies greatly depending on the application and the specific plant.

Conclusion

When plant operations professionals are deciding whether to add a data point to a SCADA system or to plant Operator Rounds installation and on-going costs should be considered.

Adding a point to a SCADA system can cost from just over $1000 to over $10,000, but with continuous monitoring and alarming capability can greatly improve the reliability of the system.

Adding a point to Operator Rounds can range in cost from $50 to several thousand dollars per year. When added to a well designed Operator Rounds program, the new data point can add to the plant operator's knowledge base and improve his or her ability to identify and correct potential problems.

________________________________________

Our software solution, which includes mobile data collection software FDPMobile and web application FDP Plant, was designed by plant operators to solve some of the challenges faced daily by operators. It is designed to be complementary to any SCADA system. If you would like more information please visit us at http://www.fielddatapro.com/ or email info@fielddatapro.com .

Thursday, March 1, 2012

Mobile Computers for Health Care

The line of mobile computers that FDPMobile is optimized to run on is the Motorola MC55. The MC55 comes in a version designed for use in Healthcare facilities. This versitile mobile computer comes in a version that is lightweight yet rugged; built for year-round use in nearly any environment; can be sanitized with common medical disinfectants to help prevent the spread of bacteria and disease.



If you have critical data that you need collected in a healthcare environment, then FDPMobile on the Motorola MC55-HC is the combination for you.

For more information, email info@fielddatapro.com.

Thursday, February 16, 2012

Cooling Tower Drift to Be Treated as Particulate Matter by EPA PM 10

Ken Hennon from Clean Air Engineering gave a nice presentation at the Cooling Technology Institute Annual Conference about new EPA standards for particulate pollution and their application to cooling tower drift.

When most people think of particulate pollution, the image of black smoke coming off the stack on a diesel engine comes to mind. But,  cooling tower drift will soon be considered in that same category. As Ken explained it, when the water in the droplets of tower water that leave the towers as uncontrolled drift evaporate, they leave behind their salts. These salts include hardness from the make up water source, residual water treatment chemicals and any solids that the tower has scrubbed from the air.

These solids that are left behind form particles that will be considered particulate pollution per the EPA standards. For more information visit the link below:

http://www.epa.gov/airtrends/aqtrnd95/pm10.html

Friday, February 10, 2012

FieldData Pro Goes to CTI Annual Conference

For the second straight year FieldData Pro participated in the Cooling Technology Institute's Annual Conference. This years conference was in Houston, Texas and was well attended by both owner operators and equipment manufacturers.

FieldData Pro's software was featured in the presentation, "Going it Alone: Lessons Learned from Managing Our Own Water Treatment Program". In this presentation, it was shown how using FieldData Pro's data management system, one comapny was able to save money and do a better job managing the water treatment program at a large manufacturing plant.

Email john_young@fielddatapro.com for more information on this application.

Thursday, January 19, 2012

Eliminate Travel Time Required for EHS Inspections


Many inspections required for environmental (RCRA Tanks, SPCC Inspections, etc) or safety (eyewash, Emergency Lights, etc) compliance require very little time, maybe a minute or two, to complete.


Often, the bulk of the time committed to these inspections is the travel time to and from the individual inspected devices. These devices are typically scattered around the plant or campus. The technician performing these inspections may spend 5 to 10 minutes getting to each device, only to spend 1 minute to perform the actual test or inspection.


FieldDataPro has developed a way to eliminate the travel time required for these inspections. We have integrated mini barcode scanners, the size of automobile keyless entry devices, into our solution.

One scan of these devices, along with our Smart Barcoding System, can capture detailed inspection results that include:
  • Inspection Result (Pass / Fail)
  • Name of Person Completing Inspection
  • Date and Time of Inspection
  • Measured Value (Numerical)
Our miniscan devices cost less that $150, so it does not  break the bank to outfit each of your staff members with one.

Here's How Our System Works

As the EHS staff travels around the plant carrying out their normal duties, they perform inspections on devices at locations they pass by.

Lets say your technician has to meet a customer in the Chemical Storage Building. Why not have her inspect the satellite waste storage location in that area. She can record her results with her mini scanner.

Have a meeting in the Physical Science Building? Go ahead and test the emergency lights in the stairwell. Record your results with your mini scanner.

Using the mini scanner eliminates the need to go back to the office to get the clipboard. With it you are prepared to record your inspections at any time.

When you get back to your desk, simply plug the mini scanner in to the charging cable and your inspection results are automatically uploaded to our easy to use web application.

Each week a report can be run detailing which devices have been inspected, which devices failed inspection and any devices that have not been inspected.

A schedule report can also be run periodically, detailing for each device:
  • Last Inspection Date
  • Next Due Date
  • Days Past Due
Use our detailed reports to actively manage your inspections.

Towards the end of each period(week, month, quarter) our reports help identify which devices were not inspected over the course of the period.
The FieldData Pro system greatly reduces the time required to complete your regulatory inspections. And by using our system you will do a much better job of managing and documenting your inspections. 


Every organization I come in to contact with is facing the same challenges, more regulatory requirements, less people to do the work. At FieldData Pro, we help organizations do a better job managing their environmental and safety inspections while using less resources.

Monday, January 16, 2012

Send Safety Home with Your Employees

As a manager do you encourage your employees to take personal protective equipment home for personal use?

Do you even allow it?

I beleive  that encouraging employees to use company issued PPE at home can help improve safety performance at work. It accomplishes this by helping instill a safety mindset in your employees.
Reinforce Positive Behavior

A safety conscious employee gives thought before each endeavour and considers the safety risks associated with the job. This employee breaks the job down into it's steps, identifies the hazards associated with the step, identifies the precautions to mitigate the hazard and ensures these precautions are taken before proceeding.

Consider the potential hazards associated with household tasks:
  • Lawn mowing - Hearing Damage, Eye Injury
  • Cleaning Gutters - Fall Hazard
  • Painting - Inhalation hazards

This is just a fraction of the potentially hazardous tasks your employees can perform at home. By encouraging employees to use their safety glasses or ear plugs at home your will help make safe work practices habits that they will take to work with them.

Minimize Negative Reinforcement

The flip side of the previous example is to minimize the reinforcement of negative behaviour. One of the biggest impediments to safe work practices is the confidence some employees have in their ability to perform tasks without being injured even without following safe work practices. How many electricians do you know who are comfortable working 120 V or 480 V hot, without gloves, glasses and arc resistant clothing because they have done it hundreds of times before without incident.

Every time they "get away" with doing it the wrong way, their confidence in those methods grows. Interrupt this cycle by make it easier for them to do it the "right" way whether they are working at home or at work.

Create a Safety Conscious Family Environment

My kids wont let me or my wife drive a car without a seat belt on. They start hollering the instant we try to do it. That is because riding in a vehicle with a belt on has been the only way they have ever known. They don't know that seat belts were optional when we were growing up. And we are better off for that.

Develop that same safety conscious attitude in them towards household work. If your children see you wearing safety glasses and ear plugs when mowing the lawn, they will adopt that practice when it it their turn to mow the lawn. If they see you put a lockout device on the light switch when you are changing a light ballast, they will ask you why. Explain to them that you don't want Uncle Billy to accidentally electrocute them when he stops by unexpectedly and throws the light switch. Make it easy for your employees to create a safety conscious family environment by encouraging to use their company issued PPE at home.
Guidelines and Expectations

Of course you will have to set guidelines and expectations. The expectation should be that the equipment come back to the workplace and be in good condition. Guidelines should include notification to the supervisor that they will be borrowing the equipment. A simple email to the supervisor on a Friday afternoon letting them know that the employee will be using their electrical gloves at home over the weekend protects the employee from being accused of theft and helps the employer keep up with the equipment it provides.
In the end both the employer, the employee and their family will be safer and better off.