SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Year 2000 (Y2K) Embedded Systems & Infrastructure Problem -- Ignore unavailable to you. Want to Upgrade?


To: John Mansfield who wrote (401)5/23/1998 2:00:00 PM
From: John Mansfield  Read Replies (2) | Respond to of 618
 
[YOURDON] INTERESTING! Background of ABC interviews

In the meantime, if you have any "smoking gun"
information, or if you know any "Deep Throat" contacts,
please let me know (use an anonymous email, if you
want, which you can obtain through hotmail or juno or
any of the other freebie email services), and I will help
put you in touch directly with Mr. Walker at ABC.


________

'NEWS ALERT

asked in the TimeBomb 2000 (Y2000) Q&A Forum

ABC News is doing a story tomorrow on Y2K
"escapists." I wonder how they'll attempt to make those
people look. Like NUTS perhaps?

Asked by zered (zered@my-dejanews.com) on May 20, 1998.

Answers

Yes, the story did run on the May 21st edition of the
"ABC News with Peter Jennings" national news program.
The reporting was done by James Walker, who also put
together ABC's first major Y2K story a couple months
ago -- the one that opened with a video clip of a
premature baby in a hospital, and the ominous news
about Y2K problems in hospitals, etc., and which
featured Ed Yardeni's comment on the possibility of a
Y2K-induced recession.

The story behind last night's brief (2-3 minutes) news
segment is interesting: Mr. Walker and his crew travelled
to Missoula, MT to interview Steve Hock about the
murkey Y2K disclosures that have been mandated by the
SEC; then to northwestern Arkansas to chat with Gary
North; then to northern New Mexico to talk to me. They
spent nearly 3 hours with me, and taped enough material
to fill the entire 30-minute news program; I assume they
did the same with Hock and North, too. All of it was
then boiled down to the few minutes of material you saw
-- all in all, a very expensive and time-consuming activity
on the network's part, in order to present a brief
sound-bite to the general public.

For what it's worth, James Walker is very
knowledgeable, very informed, very ethical and
professional, and very determined to get the "real" story
on Y2K in a form that can be presented to, and
understood by, the general public. He has been all over
the country, and has interviewed just about everyone you
can imagine -- from Senators and Congressmen, to
CEO's of corporations, to people like Gary North and
Ed Yardeni and others who are voicing concerns about
Y2K. On camera, he does his best to be scrupulously
objective, neutral, and even-handed (so that viewers can
make up their own minds), but on a personal level, I think
he is fully convinced that there will be serious Y2K
problems.

His biggest frustration, which other journalists share, is
that they haven't yet found a "smoking gun" (to put it in
Nixon-Watergate terms) which they can use to "prove"
the seriousness of the Y2K problem to a non-technical
audience that doesn't understand abstract issues about
computer software. Everything they've got, so far, is
"could be", "might be" kinds of warnings about Y2K
problems. They hear that Y2K could be a serious
problem at XYZ Corp, but when they interview the CEO
of XYZ, they get stonewalled; they hear that various
agencies of the US Federal Gov't are far behind schedule
on Y2K repairs, but when they interview all of the official
spokesmen, they get official statements of optimism and
confidence that Y2K will be fixed in time. Those
expressing concern -- e.g., Congressmen Horn and
Morella, and Senators Bennett and Moynihan -- are
unable to "prove," with 100% certainty that Y2K will
cause a serious problem.

The TV people would love to find a "Deep Throat"
source within a major company or government agency
who could help them establish some credible proof of
impending disaster, but their attempts thus far have been
unsuccessful: most programmers are still scared of being
fired or sued. I have a similar problem, and I'm sure that
people like Peter de Jager and Bill Ulrich and Leon
Kappelman and others do, too: we are privy to
confidential information, which we've received only after
signing tight non-disclosure agreements. We are ethically
and legally constrained from discussing details, and we
would be sued into oblivion if we did ...

I suggested to Mr. Walker that as long as the Y2K
problems are confined to private corporations, and are
relatively modest, the general public won't care. Even the
big satellite problem of this week (the one that knocked
out 90% of the pagers) occupied public attention for only
a day or two; now it's history, replaced by the awful
news of the school shooting in Oregon.

But if/when Y2K problems begin affecting the delivery of
services from the government, THEN we'll see a reaction
from the general public. I think there is a good chance of
this occurring on April 1, 1999 -- for the simple reason
that the State of New York, the government of Canada,
and the government of Japan all begin their 1999-2000
fiscal year on that date.
On July 1, 1999, another 46
states begin their 1999-2000 fiscal year; then there's
Texas on September 1st, and the U.S. federal
government (plus the states of Michigan and Alabama, I
think) on October 1. If any one of these states fails to
send out pension checks, or unemployment checks, or
welfare checks, etc, then I think you'll see large mobs
marching on the state capitol -- and the TV crews will be
right there with them.


In the meantime, if you have any "smoking gun"
information, or if you know any "Deep Throat" contacts,
please let me know (use an anonymous email, if you
want, which you can obtain through hotmail or juno or
any of the other freebie email services), and I will help
put you in touch directly with Mr. Walker at ABC.
I trust
Mr. Walker, and intend to do the same myself, with
whatever appropriate information I come across.

Ed

Answered by Ed Yourdon (yourdon@worldnet.att.net) on May 22,
1998.

greenspun.com



To: John Mansfield who wrote (401)5/23/1998 2:06:00 PM
From: John Mansfield  Respond to of 618
 
'pharmaceutical production


asked in the TimeBomb 2000 (Y2000) Q&A Forum

I have a software company which automates engineering
test documents. We have dozens of clients in the
pharmaceutical field.

Here's an interesting fact about pharmaceutical
production lines: they are required by the FDA to be
thoroughly tested and documented as to their ability to
produce, label, and package their drug products properly
and consistently.

The testing process, called 'validation', is difficult,
expensive, and time-consuming. And, it has to be
repeated whenever significant changes are made to the
production line. If it is not done properly, or if the
validation shows problems, then the FDA can, and will,
shut down the production line.

The upshot is this: fixes to 'embedded systems' in
pharmaceutical manufacturing have a much higher
regulatory burden of testing and documentation than
similar repairs elsewhere, and will in fact take longer.

The obvious ramification here is interruptions in our drug
supply.

This problem is just now coming into focus for a lot of
pharmaceutical engineers. I'm starting to ask questions of
my customers. I'm getting guarded answers.

Can anyone else out there shed any light on this subject?

Asked by Brady Wiseman (BradyWiseman@compuserve.com) on
May 21, 1998.

greenspun.com



To: John Mansfield who wrote (401)5/24/1998 5:10:00 AM
From: John Mansfield  Respond to of 618
 
[MANUFACTURING] INTERESTING New Y2k website

manufacturing.net



To: John Mansfield who wrote (401)5/24/1998 5:17:00 AM
From: John Mansfield  Respond to of 618
 
Y2K and Warehousing

' May 1, 1998

Y2K and Warehousing:
Could this lead to out-of-this-world storage charges?
Steve Salkin, Web Editor
For some businesses, the issues that arise with the turn of
the century are just entering the minds of top executives.
For others, the issue was recently resolved or a process
to become Year 2000 (Y2K) compliant has begun. For
most in the warehousing industry, however, the process is
already finished -- or at least should be.

Failure to be compliant could result in a warehouse
management system (WMS) interpreting a contract that
began in 1999 as 99 years old in 2000, which could lead
to out-of-this-world storage charges and a lot of unhappy
customers. The WMS may also designate certain
inventory as obsolete due to the large time lapse (or
vice-versa). Add in the fact that 2000 happens to be a
leap year, and the potential for trouble multiplies.

"For warehousing and logistics, 2000 isn't the magic
date," says International Warehouse Logistics Association
(IWLA) President Mike Jenkins. "The magic date has
come and gone due to the number of customers with
date-sensitive products that expire after 2000."
Warehouses storing products such as food or
pharmaceuticals fall into this category.

There are also warehouses that store products that cannot
be sold until a certain date. Certain chemical products
need time to incubate before they can be sold. Margarine
is one example of this type of product. Instead of an
expiration date, these products have a "first sell" date.

Regardless of what they store, warehouses that store and
distribute date-sensitive products should have already
addressed the Y2K issue. Those that haven't will need
"some sort of heroic intervention," Jenkins says.

Handling It All
Warehouses have Y2K considerations absent in other
industries. Warehousing managers not only need to worry
about whether their own systems are compliant, but their
customers' as well.

Warehouse Education and Research Council (WERC)
Executive Director Tom Sharpe says that while
warehouses may be ready, it's only half the battle: "A
warehouse could have a totally compliant system, but
interface with customers who aren't, which still means
trouble for the warehouse. I'm not convinced anyone can
say `If I take care of all my systems, I'm safe.' It won't
do any good if you're isolated."

Warehouses have to be ready for anything. This is
especially so for the public and contract warehouses that
make up IWLA's membership. "Most public and contract
warehouses are ready while their customers either aren't
or haven't even thought of it yet," Jenkins says.

A warehouse also has to consider contracts and
agreements it is involved with, such as real estate,
equipment and inventory deals. A warehouse may have a
lease that runs month-to-month. There may be an
agreement to house a customer's inventory indefinitely, or
buy a certain number of a manufacturer's lift trucks for the
next 10 years. These sort of agreements need to be
reexamined to ensure that they do not reflect a 1999
expiration (unless of course they're supposed to).

If You're Not Ready.
But what about those warehouses that have not yet dealt
with Y2K issues?

IWLA is working with a few WMS providers to keep
informed of what they are doing to retrofit and upgrade
their systems. Most software developers are including a
Y2K fix with a generic upgrade. Some are charging more
for these upgrades because of the fix, but those in it for
the long-haul "are being heads-up and classy about it,"
Jenkins says. "But there are always companies out there
trying to make a buck."

WERC has made Warehouse Systems and the Year
2000: What You Need to Do Now!, a special report
authored by Dr. Kevin Boberg, associate professor of
marketing and transportation at New Mexico State
University, available for free on its web site
(www.werc.org/year2000). The report details the
dimensions of the Y2K problem and sets out some key
dates and transactions warehouses need to know. WERC
is offering this report, initially available only to members,
to the general public, "because our board felt we have an
ethical obligation to share this information."

Warehousing as a whole is on top of the Y2K problem.
But then again, staying on the leading edge of technology
is nothing new for warehouses. Jenkins compared the
Y2K situation with other technologies that saw initial
acceptance in the warehouse, such as barcoding and
radio frequency identification. While less than half of
IWLA members' customers are barcode-capable, he
says, most of the warehouses are.

manufacturing.net