× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. BPCS-L
  3. October 2000

Re[2]: SSA GT Official Policies

     
     The attitude I see demonstrated below is typical of the see-no-evil, 
     hear-no-evil, speak-no-evil mentality that has allowed 
     customer-insensitive practices and products to persist at SSA and 
     prevented improvements for the better.  
     
     It's disappointing to see such an apparently high-ranking member of the 
     management team there still walking that walk.  Kari, you should open 
     your ears to what your customers are saying, not dismiss and distance 
     yourself from it.
     
     I would have been much happier to have hear about how your customers 
     were what kept you at SSA GT.  Your product-centric approach is the 
     same one that caused buggy-whip manufacturers to go out-of-business 
     upon the advent of the automobile (and resulted in the creation of 
     SSA GT, I submit).
     
     Kevin Catlin
     CYTEC Industries, Inc.
     (an SSA customer)
     
______________________________ Reply Separator _________________________________
Subject: Re: SSA GT Official Policies
Author:  BPCS-L@midrange.com at Internet 
Date:    10/13/2000 2:45 PM
     
     
     
I had promised an update to this list and had every intention of posting it to 
the entire list.  Quite frankly after the reaction I got from my CISC/RISC key 
response I have chosen not to post it.
     
All of us that have decided to stay with SSA GT did so because we believe in the
software and we believe there is a future here.  Staying with SSA GT was a very 
conscious decision on my  part.  So unfortunately, I take SSA GT  being called 
liars, cheats etc..   very personally .   I find the attacks on SSA GT by some 
of the individuals on this list, self serving, callus and destructive  (I am 
only speaking for myself now).  I  am therefore no longer willing to give out 
any information on this open forum.
     
 If you would like the update I have prepared, please send an e-mail to
kmiller@ssax.com.  In the email send me your name, the company you work for and 
a phone number, this is required information if I am to send you the update.  I 
want to be able to verify who I am sending the information to, I will not call 
you unless asked to.  If you have a specific question please send it along, if 
it is not addressed in my current response,  I will address it individually.  I 
travel a lot and have a lot of responsibilities so be patient, I will respond to
you as soon as I can.
     
Kari Miller
Director NA Business Consulting
SSA GT
     
     
     
     
     
     
"Chick Doe" <Cdoe@barton-instruments.com> on 10/12/2000 09:21:51 PM
     
Please respond to BPCS-L@midrange.com
     
To:   BPCS-L@midrange.com
cc:    (bcc: Kari Miller/SSA/US)
Subject:  Re: license contracts (was: Is it possible to crack the BPCS      Key
      logic?  )
     
     
     
dear ms novak
everything that you say about contacting the lawyers is correct as is your 
statement that the opinions stated in this forum are not official policies of 
SSA GT.
     
but there seems to be a noticeable silence from SSA GT as to what their official
polices are. we have had more than one posting from more than one alleged client
stating that SSA GT was reviewing / renegotiating  existing contracts. i have 
also been told that SSA GT has not renewed any affiliate contracts.  of probably
more immediate concern is that many clients probably have OGS contracts that 
have either expired or will be expiring soon. we are all in the process of 
preparing our 2001 budgets. where do we get information on OGS renewal options, 
prices, etc.? where do we get information on what has ben referred to as BPCS 
version 8?
     
i believe that SSA GT should take the initiative and give us a rather detailed 
statement of what the SSA GT organization looks like and what we should expect 
from it. as i mentioned before, the silence has been noticeable.
     
you claim to be 'just a techie' but somehow i suspect that you have a few 
informal lines of communication that you use to pas on this request. try it, 
let's see how customer oriented SSA GT really is.  this is in no way a personal 
attack. i do appreciate  the information that you offer this forum. but let's 
get the three piece suit guts involved!
     
sincerely
chick doe
barton instrument systems
     
>>> novakg@ssax.com 10/12/00 11:51AM >>>
RE: Is it possible to crack the BPCS Key logic?Hello,
     
Sorry to bore some of you with yet one more response on this threadbare thread, 
but if certain people keep tossing out lies and/or accusations about SSA GT and 
various contract legalities, they really should be corrected to avoid confusion.
I have a feeling the people doing these alarmist postings are NOT actual BPCS 
customers but are some very recently soured grapes. (Note the lack of full names
and/or company affiliation on their posts).
     
If you have legal questions, accusations or rumors to confirm I suggest you 
contact the contractual departments (Finance and Administration) at SSA GT in 
Chicago. The main number is 312-258-6000. Take option 8 and you will go directly
to someone who can answer your questions. Please leave the techies on this list 
group alone. The people montitoring this list from SSA GT are mostly 
programmers, HelpLine, field application consultants and various R&D managers - 
not the contracts department or lawyers. If you want legal answers, I suggest 
you phone that department. This list server is NOT an official means of 
communication between SSA GT and our customers. Opinions express by SSA GT 
employees on this list are just that.
     
Unless you were otherwise informed, SSA GT has assumed the contract you had with
SSA. SSA GT must therefore honor those contracts.
     
Back to real matters of BPCS software and how it works (or doesn't work or 
should work) ....I now return you to your regularly scheduled list server......
     
Thanks
     
Genyphyr Novak
SSA GT
     
     
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com. 
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. 
| Questions should be directed to the list owner: dasmussen@aol.com
+---
     
     
     
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com. 
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. 
| Questions should be directed to the list owner: dasmussen@aol.com
+---
Received: from unknown-27-151.cytec.com. ([204.48.27.204]) by stnt01.cytec.com
with SMTP
  (IMA Internet Exchange 3.14) id 003356DB; Fri, 13 Oct 2000 16:16:21 -0400
Received: from mail-ewr-3.pilot.net (localhost [127.0.0.1]) by
unknown-27-151.cytec.com. with ESMTP id QAA27418; Fri, 13 Oct 2000 16:13:15
-0400 (EDT)
Received: from uucphost.mcs.net (Kitten2.mcs.com [192.160.127.90]) by
mail-ewr-3.pilot.net with ESMTP id QAA09250; Fri, 13 Oct 2000 16:13:15 -0400
(EDT)
Received: (from 66@localhost)
        by uucphost.mcs.net (8.9.3/8.9.3) with UUCP id PAA85949;
        Fri, 13 Oct 2000 15:12:12 -0500 (CDT)
        (envelope-from bpcs-l-owner)
X-Authentication-Warning: Kitten.mcs.net: 66 set sender to bpcs-l-owner using -f
Received: (from majordom@localhost)
        by linux.midrange.com (8.9.3/8.8.7) id OAA05292
        for bpcs-l-outgoing; Fri, 13 Oct 2000 14:45:12 -0500
Received: (from uucp@localhost)
        by linux.midrange.com (8.9.3/8.8.7) with UUCP id OAA05241
        for BPCS-L@midrange.com; Fri, 13 Oct 2000 14:45:05 -0500
From: kmiller@ssax.com
Received: from mailgate (firegate-ext.ssax.com [198.202.130.20])
        by uucphost.mcs.net (8.9.3/8.9.3) with SMTP id OAA81324
        for <BPCS-L@midrange.com>; Fri, 13 Oct 2000 14:39:24 -0500 (CDT)
        (envelope-from kmiller@ssax.com)
Received: from SMTP agent by mail gateway 
 Fri, 13 Oct 2000 14:29:55 -0600
Received: from ssaus1.chi.ssax.com (ssaus1.chi.ssax.com [192.168.8.55]) by
mailgate with SMTP (8.8.6 (PHNE_15509)/8.8.6) id OAA22998 for
<BPCS-L@midrange.com>; Fri, 13 Oct 2000 14:45:27 -0500 (CDT)
Received: by ssaus1.chi.ssax.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id
86256977.006A3FFE ; Fri, 13 Oct 2000 14:20:31 -0500
X-Lotus-FromDomain: SSA@SSANET
To: BPCS-L@midrange.com
Message-ID: <86256977.006A3E55.00@ssaus1.chi.ssax.com>
Date: Fri, 13 Oct 2000 14:45:16 -0500
Subject: Re: SSA GT Official Policies
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-bpcs-l@midrange.com
Precedence: bulk
Reply-To: BPCS-L@midrange.com
X-List-Name: BPCS Users Mailing List (BPCS-L@midrange.com)

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.