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 : Discuss Year 2000 Issues -- Ignore unavailable to you. Want to Upgrade?


To: John Mansfield who wrote (3045)12/26/1998 4:57:00 AM
From: John Mansfield  Read Replies (1) | Respond to of 9818
 
'PRODIGY,AOL,COMPUSERVE,ETC Y2K THREATENED? COMPLIANT?

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

Sorry if this has already been answered elsewhere,but I didnt find it. Does anyone know if power and
phones survived, would the internet service providers be up and running? Any word on how Y2K
affects them and how they are progressing if it does? Also, will non compliant customer computers
endanger their service or websites that the non compliant computer visits?

-- Ann Fisher (zyax55b@prodigy.com), December 26, 1998

Answers

Not a simple question to answer. I do not know the Y2K compliance status of AOL, Compuserve, et
al. However, we are all in the same boat. That is, it is not enough for a company to be internally
compliant (and the definition that I'm choosing to use here simply means that enough of their internal
systems are functional to provide continuity of service -- all other factors being ignored). Their 'mission
critical' vendors of products and services must also be compliant (same definition).

Companies like AOL (like most companies) are 100% reliant upon their vendors. Imagine a scenario
where electricty and telecommunications stay on but banking has serious disruptions. They process
thousands of credit card transactions daily. If this system fails, how long can AOL continue to operate? I
would imagine they could get by for at least a few days. Maybe alternate sources of banking services
will be available. Maybe not. Maybe they could even survive an complete operational outage for a few
days. Customers would probably not leave them in droves if they could reasonably be expected to be
back online within a week or two. On the other hand, if AOL were to experience a 3 month outage
while Joe's ISP down the street was humming along fine, well, I think you know what this would mean.

Imagine another scenario where electricity stays on everywhere EXCEPT for a where their major
operations headquarters is located (Virginia say). If this were an isolated outage of short duration, you're
looking at a minor inconvenience. If the outage were prolonged, then other arangements would need to
made. Moving a major operations center is a huge job even during 'normal' times. It might be impossible
during Y2K. If a prolonged outage occurs in an isolated region (say the DC and Virginia area),
EVRYONE will be attemping to move their operations (if only temporarily) to a more viable area.

Another scenario can be imagined where electricity, telecom and banking all continue to function but
where other problems have occurred resulting in civil unrest making it dangerous for employees to come
to work. No employees, no service.

There are just too many unknowns here to make prognostications on a specific company. Certainly the
'iron triangle' (electricity, telecom, banking) is absolutely essential. Lose any of the three for a prolonged
period and all bets are off. But there are numerous other problems which could occur short of that,
either regionally or locally which, while not catastrophic to the general population, could indeed be fatal
to businesses in that location.

If one telecom provider in my area fails and another can provide service, and if the failed one cannot
seize their window of opportunity to recover, the business whose service didn't fail will reap a harvest of
new customers. Of course, if thousands of customers in single location suddenly want to switch
providers, it could still take months to get your phone service restored. I think the same thing holds true
for the large ISPs as well.

The future of any one single company which is itself reasonably compliant (internally) will be determined
by the compliancy of its vendors, the regional problems which actually occur, the size of the company,
the number of outside vendors it uses, the availability of alternate source for products and services, the
market it serves, the reaction of its customer base, it own contingency planning, the reaction of the
general population in its theatre of operation, the reaction of the government, how well it is organized,
how well it can execute contingency plans within its window of opportunity, etc, etc, etc, It is an
equation with 10,000 variables and 1 million unknowns. This is the ugly, intertwined nature of the beast.

All other things being equal (which they are not) I think the larger, more technologically dependent
companies will see the most trouble here. It's an economy of scale thing. If my business consists of 3
people, 6 mission critical suppliers and I can move one county to the north and continue operating. I'll
have a much better chance of doing so quickly than will a company with 100,000 employees and 5,000
suppliers. The problem here is that many small and medium sized businesses have adopted (either
explicitly or implicitly) a 'fix on failure' approach to Y2K. Some larger businesses have been addressing
the issue for longer (though not nearly long enough). Still, it's much, much easier to turn a small bass boat
quickly than an aircraft carrier. Ask IBM.

-- Arnie Rimmer (Arnie_Rimmer@usa.net), December 26, 1998.

# # # 19981226

Dear, Ann Fisher:

My last Y2K project ( 3-months duration ) involved ~$300,000,000 revenue dependent upon
CompuServe connectivity. My client declined ( IOW: brushed off [ Troll Maria ] ) stern warnings about
CompuServe not responding adequately to their corporate Y2K-readiness and electric( Detroit
Edison-DTE )/telephone utility SEC 10-Q's.

I was ( ethically ) compelled to include these documents and my opinions ( captured in my notes from
meetings and telephone conversations ) for the Y2K-archives of this Fortune 500 company. One can
only do so much.

What more does one have to say ( document ) in order to demonstrate corporate "don't want to hear it"
shortsightedness? It is anathema to spoil the "smiley face," "rosey outlook," and DWGI outlook for the
fortunes of the Fortune 500 stock values.

I can only *sigh* at the ineptitude by management to perceive ( via denial ) real Y2K-risks to their
business and employees.

Regards, Bob Mangus # # #

-- Robert Mangus (rmangus@mail.netquest.com), December 26, 1998.

Think about it, some ISP's provide lousy service, dial-ups as is. What happens if the phones go down in
certain areas, no postal service, intermittent power etc? Any ISP's that stay up will be swamped by
users IMHO. Ergo lock-up, things grind to a halt. Remember AOL 2 years ago??? Try phoning abroad
today, Xmas day??? No chance.

-- Andy (2000EOD@prodigy.net), December 26, 1998.

Contribute an answer to "PRODIGY,AOL,COMPUSERVE,ETC Y2K THREATENED? COMPLIANT?"

greenspun.com



To: John Mansfield who wrote (3045)12/26/1998 5:09:00 AM
From: John Mansfield  Respond to of 9818
 
'SUBSCRIBE TO RECEIVE THIS FREE DAILY EMAIL:
y2k-links.com

'From:
y2klinks@y2k-links.com
vr 14:58

Subject:
Credit Unions Make Plans for Y2K Bank Runs

SUBSCRIBE TO RECEIVE THIS FREE DAILY EMAIL:
y2k-links.com

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Gary North's Y2K Links and Forums - Newest Links
(feel free to mail this page)

If you are unable to click on these links, please copy and paste them into
your web browser

Updated Category Subject

24-Dec Banking y2k-links.com
Credit Unions Make Plans for Y2K Bank Runs
y2k-links.com New!

24-Dec Banking y2k-links.com
FED Changes the Rules: More Liquidity in Late 1999
y2k-links.com New!

24-Dec Government y2k-links.com
Seattle Will Face a Public Utility Crisis if It Misses the Deadline
y2k-links.com New!

24-Dec Noncompliant_Chips
y2k-links.com
Most Buildings May Be OK, We Hope, Says Management Group
y2k-links.com New!

24-Dec Welfare_Payments
y2k-links.com
Threat to State Unemployment Programs Begins on Jan. 4, 1999
y2k-links.com New!

24-Dec Martial_Law y2k-links.com
Joseph Farah Warns of the Problem of Martial Law
y2k-links.com New!

24-Dec Stock_Market y2k-links.com
De Jager on the Stock Market: No Big Problem
y2k-links.com New!

24-Dec Programmers'_Views
y2k-links.com
De Jager in Scientific American: Bumpmonth
y2k-links.com New!

24-Dec Martial_Law y2k-links.com
U.S. Government Has Scheduled Y2K War Games
y2k-links.com New!

24-Dec Litigation y2k-links.com
Coporations Are Scared into Silence by Their Lawyers
y2k-links.com New!

23-Dec Introduction y2k-links.com
FUD-TV: Why TV Will Fuel the Panic
y2k-links.com

23-Dec Litigation y2k-links.com
IBM Faces Class Action Lawsuit
y2k-links.com

23-Dec Litigation y2k-links.com
More Software Companies Are Sued; One Settles
y2k-links.com

23-Dec Litigation y2k-links.com
Microsoft Gets Sued for Y2K Issue
y2k-links.com

23-Dec Banking y2k-links.com
Alabama Banks Will Be Compliant in Just 10 Days. Really!
y2k-links.com

23-Dec Testing y2k-links.com
Why Testing Will Be Short-Changed in 1999
y2k-links.com

23-Dec Testing y2k-links.com
The Need for (Nonexistent) Independent Testers
y2k-links.com

23-Dec Domino_Effect y2k-links.com
A Very Good List of Things You Should Do
y2k-links.com

23-Dec Power_Grid y2k-links.com
Y2K Is not on Top Priority List of Utilities' Senior Computer Executives
y2k-links.com

23-Dec Power_Grid y2k-links.com
Not One Compliant U.S. Utility, According to Filings
y2k-links.com

23-Dec Domino_Effect y2k-links.com
Running the World Without Middle Eastern Oil
y2k-links.com

23-Dec Too_Late y2k-links.com
At Least 31 Nations Have Y2K Web Sites
y2k-links.com

23-Dec Government y2k-links.com
FBI Will Set Up Y2K-Related Anti-Terrorism Unit
y2k-links.com

23-Dec No_Big_Problem y2k-links.com
Canadian Bank Econoimist Predicts Golden Year: 2000
y2k-links.com

23-Dec Power_Grid y2k-links.com
Petition to the NRC: Enforce Your Own Rules
y2k-links.com

Return to Main Categories y2k-links.com
Return to Home Page y2k-links.com
Search This Site y2k-links.com

This message is subject to the following disclaimer:
y2k-links.com
All statements made herein, and made since October of 1998, are Year 2000
Statements and are retroactively protected as Year 2000 readiness disclosures
under the Good Samaritan Act



To: John Mansfield who wrote (3045)12/26/1998 6:09:00 AM
From: John Mansfield  Respond to of 9818
 
'Gary North wrote this today about the below petition submitted to
the NRC (US Nuclear Regulatory Commission):

"An environmental organization has petitioned the Nuclear
Regulatory Commission, asking it to enforce its own rules.
Specifically, the petition directs the NRC to demand a shutdown
of any noncompliant power plant on December 1, 1999.

The NRC has yet to say how it will enforce its rules. The
petition asks the NRC to go public with its proposed sanctions
against noncompliant power plants.

As y2k draws closer, there will be many such petitions and formal
pressures placed on the NRC to enforce its rules. The bureaucrats
will be facing pressures to delay doing anything from the
industry, which is nowhere near compliance, and rival set of
pressures from a determined public interest pressure group, which
knows the rules and is willing to use them to force the NRC to
shut down the industry.

To this will be added Congress, which will be pressured by these
groups to ensure that the NRC guarantee public safety.

This is only the first warning shot across the bow of the NRC.
The war has begun."

garynorth.com

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

nirs.org
December 10, 1998

Nuclear Regulatory Commission

Washington, DC 20555

Attention: Chief, Docketing and Service Branch

Petition for Rulemaking re: shutdown of nuclear facilities not
compliant with Y2K issues

The Nuclear Information and Resource Service (NIRS) submits the
following petition for rulemaking under 10 CFR 2.802.

Although NIRS normally believes in and advocates ample public
comment periods, the nature of this petition and the
date-specific issue it addresses require that this petition be
placed on an expedited schedule. Therefore, we respectfully
request that the NRC file this petition immediately and that
public comment be limited to 30 days.

The purpose of this petition is to provide reasonable assurance
that date-sensitive computer-related issues (popularly known as
Y2K) will not cause failure of nuclear safety systems and related
environmental damage and destruction and will not pose a threat
to the public's health and safety.

NIRS requests that the NRC adopt the following text as a rule:

"Any and all facilities licensed by the Nuclear Regulatory
Commission under 10 CFR Parts 30, 40, 50 and 70 shall be closed
by 12 PM Eastern Standard Time, December 1, 1999 unless and until
each facility has a) fully and comprehensively examined all
computer systems, embedded chips and other electronic equipment
that may be date-sensitive to ensure that all such systems that
may be relevant to safety are Y2K compliant; b) repaired,
modified and/or replaced all such systems that are found not to
be Y2K compliant; c) have made available to the public all
information related to the examination and repair, modification
and/or replacement of all such systems; d) have determined,
through full-scale testing, that all repairs, modifications,
and/or replacements of all such systems are in fact Y2K
compliant."

Discussion

As identified in NRC Generic Letter 98-01, the Year 2000 computer
problem, also known as Y2K, pertains to the potential for
date-related problems that may be experienced by a system or an
application. These problems include not representing the year
properly, not recognizing leap years, and improper date
calculations. An example of a date-related problem is the
potential misreading of "00" as the year 1900 rather than 2000.
These problems can result in the inability of computer systems to
function properly by providing erroneous data or failing to
operate at all. The Y2K problem has the potential of interfering
with the proper operation of computer systems, hardware that is
microprocessor-based (embedded software), and software or
databases relied upon at nuclear power plants. Consequently, the
Y2K problem could result in a plant trip and subsequent
complications on tracking post-shutdown plant status and recovery
due to a loss of emergency data collection. Of additional concern
to the petitioners, the power grids providing offsite power to
nuclear stations could be impacted resulting in localized to
widespread grid failures. There are numerous other dates
potentially impacting computers and embedded software; a list is
attached.

The NRC has recognized the potential severe safety and
environmental problems that could be caused by date-sensitive
electronic systems suddenly failing to operate or providing false
information to nuclear facility operators, or to other electronic
systems. These potential problems run the gamut from inaccurate
operations logs to full reactor core meltdowns. For these
reasons, the NRC has required that atomic reactor and major fuel
cycle facilities report to the NRC by July 1, 1999 on their
programs to ensure compliance with Y2K issues.

However, the NRC has not made explicit how it will define
compliance with Y2K issues nor what it plans to do about those
facilities that cannot prove compliance.

The text in this petition for rulemaking defines compliance with
Y2K issues as evaluation of all potential problems that may be
safety-related, repair of all such problems, and full-scale
testing of all solutions. The petition also requires full public
disclosure of all evaluation, repair and testing data, so that it
may be examined by independent experts and the public. The date
(December 1, 1999) specified in the petition is to allow time for
independent evaluation of all such data.

The text in this petition also makes clear that nuclear
facilities that cannot reach this hurdle will be closed until
such time as they can prove full compliance with Y2K issues.
While NIRS' primary concern is, as is the NRC's, with atomic
reactors and major fuel cycle facilities, the text of this
petition also makes clear that the NRC will require such
compliance from all of its licensees, not a limited subsection.

The NRC has the power and the obligation to act decisively to
protect the public health and safety and the environment.
Allowing nuclear facilities to operate without absolute proof of
Y2K compliance---in essence, to simply hope that everything would
be ok--would be a serious breach of that obligation. Anything
short of this approach is insufficient to assure public health
and safety. Thus, we believe this petition is noncontroversial,
that the NRC will support this petition for rulemaking and will
adopt it as soon as possible.

Respectfully submitted,

Michael Mariotte

Executive Director



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

Roleigh Martin ourworld.compuserve.com
( easy to remember alias is: webalias.com )