> My Dear Mr. Mattias,
> snip <If "no schedule received"  is a critical thing for Mr. Garwick's 
> firm, I
> have to suggest it would be "less than optimal" to rely on "some person"
> remembering to check> snip
>
> Ah, but that is their job.
>
> There are a number of problems with automated "alerts"

Well, well, well.  We may just have to politely agree to disagree, before I 
have a Dan Ackroyd-Jane Curtin Weekend Update moment.

> Problem one:
> "alerts" make people lazy

Perhaps they allow people to concentrate on more important things, and only 
be interrupted when necessary?

> Problem two
> "alerts" go to a person - does not solve the "out, on vacation, quit, 
> etc."

You need to get out more often.   You don't send alerts to *one specific* 
person. You send to a department, or to "Susie *AND* Susies's backup just in 
case Susie is gone today.

> Problem three
> a computer can't tell that you're not going to get data this week because 
> {list of lame excuses}

No, but the computer tells you SOMETHING is 'different' this week, and 
attention by one of your beloved human beings is required.

> Problem four
> real "alerts" get ignored along with the numerous false ones..

Um, don't send false alerts?  (See # 2 re getting out more often).

> Problem five
> computers do crash, upgrades happen and things l(ike alerts) get missed, 
> changes
> are made which can interfere with "alerts" (among other things) then your
> "dependent" user never knows he's missing anything and life goes on until 
> you
> shut your customer down and then, pink slip for all of you.

Um,  this is neither your problem nor mine; this is a general management 
problem. (See #4 and  #2 re getting out more often).

> Problem four (and, to some extent one and two) resulted in the crash of a 
> NW
> flight killing all on board except one small child.  ... Give me a person 
> any day.

Problem Four?  Following Problem  Five? You hopeless romantics can't add?

You know, you just might fit right in with Osama bin Laden and his ilk... 
considering you both clearly long for the Good Old Days of the Twelfth 
Century

MCM




------------------------------------

...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix.Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply via email to