Sign up Calendar Latest Topics Donate
 
 
 


Reply
  Author   Comment  
RustyCas

Avatar / Picture

Admin
Registered:
Posts: 1,810
Reply with quote  #1 
In another thread Vibe-rater suggested “It pays to standardise for this reason. Perfect a machne and copy after that.”

How many of you have developed a database of “standard machines” that you simply copy from when setting up new routes? I have sort of done this, but have not been rigorous about it. Is this sort of thing something that we could share, as to machine, parameter, and alarm setup?


__________________
"The trend is your friend"
Barry

Avatar / Picture

Member / Supporter
Registered:
Posts: 132
Reply with quote  #2 
Rusty for the most part I worked alone but an engineer with acess to the bata bases did a lot of tinkering and thatwould creat havoc. I would many times delete things he did and start over. We had many of the same pumps all over the site and I felt as if they need their own TLC. Then came time for me to attemp to train my replacements. His method was to discard me and call CSI ( had to do it steickley by the book) and they would tell him he must drop the hammer and that creates more problems if have a need for more changes.
Long story short IMHO if a Good analysts is taking data for himself like you do you will know the machines you can copy and the ones that need to tweaked.
I also have gotten the feeling from your comments and like of responds from my post no one reads them so share this if you will.
PS: It you are a good analyst it should no matter what units used cpm, Hz or orders.

__________________
Barry
Vibe-Rater

Avatar / Picture

Sr. Member / Moderator / Supporter
Registered:
Posts: 1,397
Reply with quote  #3 
Rusty,
I have not set up a specific database of standard machines.

I do roam through my memory and imo "standard" setups.  As you know it is easy to have a lot of databases with CSI and it is NOT easy to standardise AP / AL sets across them.  So we end up with a difficult situation.

I started off with an enormous reply but thought better of it.  Simplicity is almost always better.  

The GM standard and the TA preferred method or what ever they call it.  Feel free to try but did not work for me. Combined cost (to create those standards) would have been many millions of dollars. How I made a mistake with working for myself. I would have earned more sitting at a desk.

So my simple aproach has been for many years.

Make a call. Retrieve bearing or component and check if it matches what I thought. If OK then use what you learnt next time.

SOOO many do not retrieve bearings and components and get buried in theory.  Don't get caught in that.  As I know you do not.
Curran919

Avatar / Picture

Sr. Member / Supporter
Registered:
Posts: 599
Reply with quote  #4 
Quote:
Originally Posted by Vibe-Rater

SOOO many do not retrieve bearings and components and get buried in theory.  Don't get caught in that. 


Oooh, oooh, that's me! [wave]
Danny Harvey

Sr. Member / Moderator / Supporter
Registered:
Posts: 1,402
Reply with quote  #5 
I have made several standard machines that I add to a database for the inevitable occasion when someone wants me to add something to a route while I'm collecting data.  That way I don't have to go through setting up a new machine on the data collector and then merging it into the database.

I also made standard AP and AL sets that we used in most all databases.

When I would create a route, I would use RBMWizard to get all the configuration data into the right place (it does a great job on this), then delete all the AP and AL sets assigned (it does a terrible job on this) and replace them with mine.

I'll copy machines from time to time but building new ones is so easy doing this that I never really tried using standards. They almost always require some sort of modifications anyway.
RRS_Dave

Sr. Member / Supporter
Registered:
Posts: 216
Reply with quote  #6 
I do basically same as Danny. I have a “standard”setup for most all machine types, and use them as generic when customer wants something extra added or “check this one on your way by” scenario. A lot of times I use them to set up initial database when I don’t know anything about machines other than type and name. As I collect data, I’ll photograph (use to be pen and notepad) the nameplate data, machine itself, and add notes on any other pertinent thing I may see, and then make changes at home as I review each reading. A lot of times I change a bunch from initial setup, but at least I have one set of data and lot of info to add after one trip around. Since I use Odyssey, alarms are pretty simple to set up, and collection specs are also so it doesn’t take a lot of time to tweak
D
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.