MES Employee ID Schema

Oh shoot, I should've remembered that. He was just the first John D.
that popped into my head. Regardless, using names in the ID is a bad
idea.

Brian

--- In vantage@yahoogroups.com, "Rudy Rodriguez" <rudy.rodriguez@...>
wrote:
>
> Just for the record.....
>
> John Denver is dead......plane crash 1997
>
> Great idea anyway Brian!
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of Brian Stenglein
> Sent: Wednesday, August 15, 2007 8:23 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: MES Employee ID Schema
>
>
>
> You're going to run into a problem with that convention as well.
> What happens when you hire John Denver for example. I think it is
> best to do what Todd described. We have a 5 character sequential
> numbering system for our employee ID's and padded the left with
0's.
> These also match the #'s in ADP.
>
> Brian Stenglein
> Clow Stamping Company
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
RSN
> <rsnsfi@> wrote:
> >
> > We started out using two letter initials for employee id and then
> found out that as our workforce grew that ran into some
redundancies.
> So now we use the same format as the Vantage Userid/network id
login
> format etc. to stay consistent- in our case (I don't approve of
this
> convention)- firstnameLastInitial. eg: John Doe would be JohnD .
Its
> best to stay consistent with an eye on the future.
> >
> >
> > ----- Original Message ----
> > From: mwi2527 <mwi2527@>
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Sent: Sunday, August 12, 2007 7:21:19 PM
> > Subject: [Vantage] MES Employee ID Schema
> >
> > We are doing a new implementation and looking for feedback on how
> > others have defined their employee ID's: all numbers - based on
> what
> > pattern, combination of first and last name (or portions of),
> > combination of alpha/numeric, etc.
> >
> >
> >
> >
> >
> >
> >
> __________________________________________________________
> ______________
> > Choose the right car based on your needs. Check out Yahoo! Autos
> new Car Finder tool.
> > http://autos.yahoo.com/carfinder/
<http://autos.yahoo.com/carfinder/>
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
We are doing a new implementation and looking for feedback on how
others have defined their employee ID's: all numbers - based on what
pattern, combination of first and last name (or portions of),
combination of alpha/numeric, etc.
We started out using two letter initials for employee id and then found out that as our workforce grew that ran into some redundancies. So now we use the same format as the Vantage Userid/network id login format etc. to stay consistent- in our case (I don't approve of this convention)- firstnameLastInitial. eg: John Doe would be JohnD . Its best to stay consistent with an eye on the future.


----- Original Message ----
From: mwi2527 <mwi2527@...>
To: vantage@yahoogroups.com
Sent: Sunday, August 12, 2007 7:21:19 PM
Subject: [Vantage] MES Employee ID Schema

We are doing a new implementation and looking for feedback on how
others have defined their employee ID's: all numbers - based on what
pattern, combination of first and last name (or portions of),
combination of alpha/numeric, etc.






____________________________________________________________________________________
Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool.
http://autos.yahoo.com/carfinder/

[Non-text portions of this message have been removed]
Sorry. Didn't see the message from Sunday night until recent response.
We use 4 digit numeric only sort of random next sequential number for new employees (we skip around a bit). If all numeric BE SURE to add leading zeros or start at 1xxx (depending on number of digits) because this is an alpha-numeric field and sorting by ID will be really messed up otherwise. We prefer numeric in order to use (if they want) the 10 key pad on keyboard when clocking in and our accountants doing labor entry really prefer it too so they don't have to switch to alpha keys. Exception to scheme is temporary employees from a temp service....these are assigned a T99 (T-number-number) ID for their duration and a log is kept of who had the number for what time period.
-Todd C.

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of mwi2527
Sent: Sunday, August 12, 2007 9:21 PM
To: vantage@yahoogroups.com
Subject: [Vantage] MES Employee ID Schema


We are doing a new implementation and looking for feedback on how
others have defined their employee ID's: all numbers - based on what
pattern, combination of first and last name (or portions of),
combination of alpha/numeric, etc.



________________________________
The information contained in this E-mail message and any documents which may be attached are privileged and confidential, and may be protected from disclosure.

Please be aware that any use, printing, copying, disclosure or dissemination of this communication may be subject to legal restriction or sanction. If you think you have received this message in error, please reply to the sender.

For more information please visit www.harveyvogel.com


[Non-text portions of this message have been removed]
We use First Init and last name, up to eight characters. If more than
1 init are the same we just ad the next letter in the spelling. So
John Doe & Jane Doe would be Jodoe & Jadoe. Last names get truncated
to fit the 8 character limit, so William Williamson becomes wwilliam
Office employees signs in using their names (per above) and shop
employees sign in using their clock numbers, yet the name from above
shows up when labor is reported. This way it is easy to tell who did
what without needing to cross-ref a numbers.

--- In vantage@yahoogroups.com, RSN <rsnsfi@...> wrote:
>
> We started out using two letter initials for employee id and then
found out that as our workforce grew that ran into some redundancies.
So now we use the same format as the Vantage Userid/network id login
format etc. to stay consistent- in our case (I don't approve of this
convention)- firstnameLastInitial. eg: John Doe would be JohnD . Its
best to stay consistent with an eye on the future.
>
>
> ----- Original Message ----
> From: mwi2527 <mwi2527@...>
> To: vantage@yahoogroups.com
> Sent: Sunday, August 12, 2007 7:21:19 PM
> Subject: [Vantage] MES Employee ID Schema
>
> We are doing a new implementation and looking for feedback on how
> others have defined their employee ID's: all numbers - based on what
> pattern, combination of first and last name (or portions of),
> combination of alpha/numeric, etc.
>
>
>
>
>
>
>
____________________________________________________________________________________
> Choose the right car based on your needs. Check out Yahoo! Autos
new Car Finder tool.
> http://autos.yahoo.com/carfinder/
>
> [Non-text portions of this message have been removed]
>
We use the employees ADP number.

stimpy7777 <terry.schulz@...> wrote: We use First Init and last name, up to eight characters. If more than
1 init are the same we just ad the next letter in the spelling. So
John Doe & Jane Doe would be Jodoe & Jadoe. Last names get truncated
to fit the 8 character limit, so William Williamson becomes wwilliam
Office employees signs in using their names (per above) and shop
employees sign in using their clock numbers, yet the name from above
shows up when labor is reported. This way it is easy to tell who did
what without needing to cross-ref a numbers.

--- In vantage@yahoogroups.com, RSN <rsnsfi@...> wrote:
>
> We started out using two letter initials for employee id and then
found out that as our workforce grew that ran into some redundancies.
So now we use the same format as the Vantage Userid/network id login
format etc. to stay consistent- in our case (I don't approve of this
convention)- firstnameLastInitial. eg: John Doe would be JohnD . Its
best to stay consistent with an eye on the future.
>
>
> ----- Original Message ----
> From: mwi2527 <mwi2527@...>
> To: vantage@yahoogroups.com
> Sent: Sunday, August 12, 2007 7:21:19 PM
> Subject: [Vantage] MES Employee ID Schema
>
> We are doing a new implementation and looking for feedback on how
> others have defined their employee ID's: all numbers - based on what
> pattern, combination of first and last name (or portions of),
> combination of alpha/numeric, etc.
>
>
>
>
>
>
>
__________________________________________________________
> Choose the right car based on your needs. Check out Yahoo! Autos
new Car Finder tool.
> http://autos.yahoo.com/carfinder/
>
> [Non-text portions of this message have been removed]
>






---------------------------------
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more.

[Non-text portions of this message have been removed]
You're going to run into a problem with that convention as well.
What happens when you hire John Denver for example. I think it is
best to do what Todd described. We have a 5 character sequential
numbering system for our employee ID's and padded the left with 0's.
These also match the #'s in ADP.

Brian Stenglein
Clow Stamping Company

--- In vantage@yahoogroups.com, RSN <rsnsfi@...> wrote:
>
> We started out using two letter initials for employee id and then
found out that as our workforce grew that ran into some redundancies.
So now we use the same format as the Vantage Userid/network id login
format etc. to stay consistent- in our case (I don't approve of this
convention)- firstnameLastInitial. eg: John Doe would be JohnD . Its
best to stay consistent with an eye on the future.
>
>
> ----- Original Message ----
> From: mwi2527 <mwi2527@...>
> To: vantage@yahoogroups.com
> Sent: Sunday, August 12, 2007 7:21:19 PM
> Subject: [Vantage] MES Employee ID Schema
>
> We are doing a new implementation and looking for feedback on how
> others have defined their employee ID's: all numbers - based on
what
> pattern, combination of first and last name (or portions of),
> combination of alpha/numeric, etc.
>
>
>
>
>
>
>
______________________________________________________________________
______________
> Choose the right car based on your needs. Check out Yahoo! Autos
new Car Finder tool.
> http://autos.yahoo.com/carfinder/
>
> [Non-text portions of this message have been removed]
>
Just for the record.....

John Denver is dead......plane crash 1997

Great idea anyway Brian!



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Brian Stenglein
Sent: Wednesday, August 15, 2007 8:23 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: MES Employee ID Schema



You're going to run into a problem with that convention as well.
What happens when you hire John Denver for example. I think it is
best to do what Todd described. We have a 5 character sequential
numbering system for our employee ID's and padded the left with 0's.
These also match the #'s in ADP.

Brian Stenglein
Clow Stamping Company

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , RSN
<rsnsfi@...> wrote:
>
> We started out using two letter initials for employee id and then
found out that as our workforce grew that ran into some redundancies.
So now we use the same format as the Vantage Userid/network id login
format etc. to stay consistent- in our case (I don't approve of this
convention)- firstnameLastInitial. eg: John Doe would be JohnD . Its
best to stay consistent with an eye on the future.
>
>
> ----- Original Message ----
> From: mwi2527 <mwi2527@...>
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Sent: Sunday, August 12, 2007 7:21:19 PM
> Subject: [Vantage] MES Employee ID Schema
>
> We are doing a new implementation and looking for feedback on how
> others have defined their employee ID's: all numbers - based on
what
> pattern, combination of first and last name (or portions of),
> combination of alpha/numeric, etc.
>
>
>
>
>
>
>
__________________________________________________________
______________
> Choose the right car based on your needs. Check out Yahoo! Autos
new Car Finder tool.
> http://autos.yahoo.com/carfinder/ <http://autos.yahoo.com/carfinder/>
>
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]
> You're going to run into a problem with that convention as well.
> What happens when you hire John Denver for example. I think it is
> best to do what Todd described. We have a 5 character sequential
> numbering system for our employee ID's and padded the left with 0's.
> These also match the #'s in ADP.

And what happens if someone gets married? (Or, much less frequently but
recently in my case, someone changes their name because of a change in
gender?) Names make poor database keys.

Mark W.
I work for a conglomerate with 70,000 users. We each have a unique id
number. After a recent security audit I was told to change all Vantage
user id's to match the corporate number. Lot's of fun, but corporate is
happy that our log file and transaction records now have id tags that
they can match to their database.



I'm implementing data collection now, and since plant floor also creates
transaction records I set up the employees using their corporate ID's as
employee ID's. I used a VB form field to enter the ADP number.



Steve Ashton

Database Specialist

Decoustics Limited

65 Disco Road

Toronto, Ontario

Canada M9W 1M2

T (416) 675-3983 x336

F (416) 679-8838

sashton@... <mailto:sashton@...>

Steve.Ashton2@...



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Wednesday, August 15, 2007 9:36 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: MES Employee ID Schema



> You're going to run into a problem with that convention as well.
> What happens when you hire John Denver for example. I think it is
> best to do what Todd described. We have a 5 character sequential
> numbering system for our employee ID's and padded the left with 0's.
> These also match the #'s in ADP.

And what happens if someone gets married? (Or, much less frequently but
recently in my case, someone changes their name because of a change in
gender?) Names make poor database keys.

Mark W.





[Non-text portions of this message have been removed]