Re: Let us go ahead with life - (and no more code cracking)

Input for the new release came from the Guide Groups.  The guide groups are in
the following veritcals Pharma, Automotive, and  CPG.  We also went to some of
our General Manufacturing base.  Finally we went to the BMR system and reviewed
all of the Enhancement BMRS.

Not everything everyone wanted got in, we did as much as we could with the time
frame and resources we had.

Kari





DAsmussen@aol.com on 10/18/2000 12:47:54 AM

Please respond to BPCS-L@midrange.com

To:   BPCS-L@midrange.com
cc:    (bcc: Kari Miller/SSA/US)
Subject:  Re: Let us go ahead with life - (and no more code cracking)



Sundaram,

In a message dated 10/17/00 6:11:02 AM Eastern Daylight Time,
r.sundaram@jotundxb.co.ae writes:

<<snip good stuff>>
> Let us say if SSA GA is coming out with the new version 8. What would we
like
>  it to look like, including platforms, hardware, screens, software etc
>  etc........Brain storming?????????
>  Do you think the inputs we all can pour in will help all of us so that we
make
>  BPCS more efficient and humming?
<<snip more good stuff>>

Unfortunately, the time for V8 input is past and they didn't ask us.  I would
gladly offer this forum up for frank discussion of V8.1 if SSA would take the
opportunity.  What tangible benefits will we receive from V8?  I can almost
guarantee they'll _not_ be the ones your company was looking for.

If I might make a "left-handed" public apology to SSA without having anyone
else at SSAX.COM wimp, uh - bail out, I would do so now.  I have been quite
critical lately -- perhaps too much so.  A combination of long-unresolved
BMR's, pressure from my current client over those BMR's, and uncertainty over
the fate of a company in which my own future has a large stake have lead to
this.  As I intimated, but apparently failed to use the proverbial
"two-by-four" to get attention, I regret some statements that I made in the
heat of recent discussions.  I've chilled out, but so should those writing
things like "I  am therefore no longer willing to give out any information on
this open forum" from SSA.

What SSA _MUST_ understand, though, is that my small consulting firm is but a
microcosm of their customer base.  While I have some powerful clients, they
are but a few among the total SSA client base and could hardly shift SSA GT
corporate policy on their own.  SSA's customers have the same fears about the
future of SSA GT that I (and others like me) do, and the new owners of SSA
have certainly not been forthcoming about that future to _any_ of us.  We all
received far more information about the management "formerly known as new"
than we have about the Gores ownership.  I spoke well of the latter mainly
because of that new fount of information from it, which stood in stark
contrast to the Covey years.  Lack of information leads to speculation,
rumors,  and (originally) this list and others like it.

SSA members on this list also need to realize that the BPCS-L listserv is not
a mutual admiration society for SSA GT.  There are _going_ to be criticisms,
especially when information is not forthcoming from whence it should --
namely, SSA GT and/or Gores.  They also need to understand that we out here
feel _every bit_ as passionately about their products as they do.  Most
earlier criticisms here bemoaned the fact that BPCS was not as stable as it
was in the 4.x and lower days -- but few were expressing an interest in
dropping BPCS altogether.  Last, but certainly not least, SSA members need to
understand that a few bad postings from people either having a bad day or a
bad life are not the end of the world.  The latter are the price you pay for
participating in a public forum, but the rewards of that participation are
far greater -- if you'll listen to what we're saying here.

FINALLY --  Anyone else asking to "crack the code" after 10/17 that is a
member of BPCS-L at this time will be banned from this list in perpetuity.  I
_THOUGHT_ that I had made myself clear on that subject.  On the day that
there is no longer a viable entity available to support BPCS, I will post
that code here myself along with the workarounds for the KRSO objects.  Until
that day, which I _seriously_ doubt will come, I will reiterate that this
list is _NOT_ a forum on which you can circumvent your license fees.  Pay
your fee like everyone else, and _CEASE AND DECIST_ discussing this issue.
You have been warned...

Regards,

Dean Asmussen
BPCS-L List Administrator
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com

"Happiness is doing what others say you cannot do." -- Walter Bagehot
+---
| 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
+---