Multi-Tasking, The Easy Way

Simo Koncalovic
By Simo Koncalovic | January 3, 2012
Application Engineer

Every time you collect data, are you selecting all types of charts and click, click, clicking away before you can even start? Do you have to perform many different types of tests on a sample at several different workstations? Is your index finger beginning to develop a twitch? Well, ProFicient may have a solution for you. It may be your only chance to combat that carpal tunnel syndrome!

A little feature called "Last Saved Database Value" can be your best friend. You can use this feature to keep track of some of your descriptors that you use to describe a specific sample. It becomes a very useful tool when you collect data on samples at different workstations at different times, while also allowing you to collect data on other samples on that same workstation in different orders.

The process works best if there is a specific test which is always performed first. This will be the beginning of the end of your constant reselection of descriptors and other items that need to be selected before data collection can begin. The first data entry configuration or project will require the selection or creation of all the necessary descriptors. Then you can proceed onto collecting your first set of data for the sample.

The subgroup for that sample can now be used to eliminate future selection of items. In other words, all of the other data entry configurations that are required for that sample can now look back at that subgroup and use the same descriptors. Although you may still have to select a couple of items, such as Part and Process, all the other items will now come along for the ride instead having to be reselected.

This is accomplished by going into all the other data entry configurations and setting the descriptors to use the last saved database value that can be filtered by currently selected Part and Process (or other things such as Lot). You would, for example, leave Part and Process as selectable by user and then apply the last saved database value to any other descriptors or items that are required prior to data entry.

All you have to do then is select the Part and Process and Proficient will look back into the InfinityQS database to find the last saved database value and write the descriptor value to the same value that was used in that prior subgroup.

By doing this you can select the descriptors on the first set of tests and have them follow you around while you add other sets of tests. This can be very useful in a lab type environment when you might have multiple samples of different parts that have many descriptors and require different tests at different workstations.

A good example would be if your sample requires a weight test that is done at one workstation and then moves to another for dimensional checks. After that it moves to yet another workstation for a pull test. Instead of selecting your descriptors 3 times you can input them once at your weight station and they will automatically appear at your dimensional and pull testing workstations.

This also allows you to measure other samples from other machines or other part numbers at the same workstations without losing your descriptors for a specific sample. You can also measure any sample in any order at the dimensional and pull test workstations without mixing up your descriptors for the samples.

This can be very useful, and can also get you rave reviews from your colleagues, since anytime you can reduce clicks or work you generally get good feedback. This principle also minimizes the elusive "fat-finger" effect by minimizing the chances for error, and improving your data integrity.

InfinityQS Fact Checking Standards

InfinityQS is committed to delivering content that adheres to the highest editorial standards for objective analysis, accuracy, and sourcing.

  • We have a zero-tolerance policy regarding any level of plagiarism or malicious intent from our writers and contributors.
  • All referenced articles, research, and studies must be from reputable publications, relevant organizations, or government agencies.
  • Where possible, studies, quotes, and statistics used in a blog article contain a reference to the original source. The article must also clearly indicate why any statistics presented are relevant.
  • We confirm the accuracy of all original insights, whether our opinion, a source’s comment, or a third-party source so as not to perpetuate myth or false statements.



Never miss a post. Sign up to receive a weekly roundup of the latest Quality Check blogs.