I'm posting this again because I didn't see any responses to my 9/8 post (as a response to my own original post about APPA); might have been bad timing, huh? But in case anyone here is trying to quiz their local electricity distributor about readiness and contingency plans, this might be helpful to know. The APPA (who they report to) backed up my local utility's claim that having contingency plans ready wasn't part of being "Y2K Ready." Yet on the APPA's web site, the member's page, I found they state the opposite. - Judy

[From Sept. 8th, "APPA Response to my Query" thread]

Bonnie's diligence inspired me to do a little more searching, and I found the statement that led me to believe "contingency plans" were part of APPA's definition of being "Y2K Ready," in spite of their recent reply (posted above) that seems to deny this, and our local utility's unawareness of it. This APPA page, entitled "Member Services" (below) includes the statement:

"Part of being "Y2K ready" means having a contingency plan in case your systems go down. For example, you may have tested your substations and distribution control systems and are confident that your system will operate on Jan. 1, 2000, but if something malfunctions for your power supplier, you may find yourself without any power to distribute...."

This page is apparently intended for APPA members, rather than the public (requires a password from the APPA page), and I couldn't find it until I went through the Dept. of Energy's web page (http://cio.doe.gov/y2k/energy_sector/default2.htm). So I've copied the text of that whole page here in case that link gets changed [Note: this forum is one of the sources of "useful information" they recommend at the bottom of their page ...] - Judy

http://www.appanet.org/y2k.html

Public Power and the Y2K Computer Problem FACT SHEET

What's all the fuss?

Our modern computerized world may find itself scrambled on Jan. 1, 2000 when digital calendars turn from 12/31/99 to 1/1/00. Many computers and chips embedded in equipment may shut down or malfunction because lines of code in their programs will recognize 00 as the year 1900, rather than the year 2000. The potential impact on electric utility operations could be devastating. The Y2K problem has the potential to affect billing and customer information systems, distribution systems, transmission lines and generating plants.

What should each local utility do to address this problem?

Each utility needs to follow a four-step process: inventory, assess, test and remediation. First determine what equipment on your utility system may have a Y2K problem. Once your inventory is completed, assess which systems are most critical to your operations and test those first. Once tests indicate that a Y2K problem exists, make the fix--either by replacing parts or equipment or reprogramming, if possible. Testing computer systems is time-consuming and labor-intensive. For electric utilities, the potential problems caused by chips embedded in various kinds of electronic equipment in power plants and on distribution systems pose the greatest challenge.

Tests of single pieces of equipment often show that, in isolation, the equipment will work fine when the calendar turns at the end of next year. However, all equipment needs to be tested within the system, as data exchanges between two apparently Y2K-ready pieces of equipment could trigger data confusion and an equipment malfunction.

How can we address the embedded systems problem?

The Y2K problem on embedded systems is the biggest thorn.

Microprocessor and small computer chips have been inserted into millions of pieces of equipment ranging from elevators and fire detection systems to environmental control systems, lighting, postage machines and distribution equipment. Process control systems that monitor and regulate the flow of electricity could cause a shutdown of the electric delivery system. To address the problems, it is necessary to make an inventory of the embedded devices at your utility, to determine the impact of each device on your operations and to contact the manufacturer, if possible, to determine whether it will operate normally when the calendar turns.

Testing may still be required since some manufacturers have gone out of business and others are unsure of the Y2K status of systems produced years ago. Company mergers also contribute to confusion on the part of manufacturers about the readiness of equipment.

What does it mean to be "Y2K compliant?"

It's better to say you are "Y2K ready." In other words, there's no law to comply with here. You want to take all steps you can to be ready for the turn of the calendar by testing your systems and modifying or changing equipment, where necessary, to assure that systems will operate normally after Dec. 31, 1999. The pervasiveness of the problem requires each utility to establish priorities. Critical systems must be addressed first, non-critical systems take a lower priority.

For example, getting the distribution system ready for the year 2000 may take a higher priority than getting your summer peaking generator ready. Having backup generation ready to go on Jan. 1, 2000 may take a higher priority for your utility than operating a load management system. Part of being "Y2K ready" means having a contingency plan in case your systems go down. For example, you may have tested your substations and distribution control systems and are confident that your system will operate on Jan. 1, 2000, but if something malfunctions for your power supplier, you may find yourself without any power to distribute.

But haven't some regulatory authorities imposed some compliance rulings?

Yes. The Governmental Accounting Standards Board on Oct. 14, 1998 issued a technical bulletin requiring governmental entities to disclose information about their year 2000 compliance. The bulletin, Disclosures About Year 2000 Issues, affects financial statements for which the auditor's report is dated after Oct. 31, 1998. It requires government entities to disclose any significant resources committed to making computer systems and equipment ready for operation in the year 2000. Additonal information about the bulletin is available on GASB's Web site.

In addition, the Securities and Exchange Commission on Aug. 4, 1998 published in the Federal Register (Vol. 63, No. 149, pages 41394-41404) an interpretive release recommending that issuers of municipal securities provide information to their bondholders on their ability to meet financial obligations in light of potential year 2000 problems. The SEC also suggests that municipal issuers follow guidelines set forth for stockholder-owned companies. These include disclosing steps taken and costs incurred to prepare for the year 2000, risks presented by the Y2K problem and a description of contingency plans if outages occur. To read the interpretive release, go to the SEC's Web page.

Is Jan. 1, 2000 the only date we need worry about?

Not necessarily. Other dates that might trigger computer chip malfunctions include 1-1-99; 8-20-99 (for functions involving satellites), 9-9-99 and 2-29-00. In addition, organizations with a fiscal year that begins July 1, Oct. 1 or any other date prior to Jan. 1 may experience problems before Jan. 1, 2000.

How serious is the Y2K problem?

In terms of dollars, it has been estimated that addressing the year 2000 problem will cost $600 billion on a global basis. And the problem is a global one. It affects all businesses and industries, governments, schools, and countries around the world. According to a consultant for the North American Electric Reliability Council, there are 50 million devices worldwide with Y2K anomalies. One mid-sized electric utility in the United States has 170,000 devices that may fail when the calendar turns. Some economists have predicted that the worldwide problems caused by failed computerized systems on Jan. 1, 2000 could trigger a global recession worse than the 1973 oil embargo and a 30% drop in the stock market.

What is APPA doing to help its members address the Y2K problem?

APPA is working with the U.S. Department of Energy and several industry groups to address the problem. Under an agreement reached with DOE, the North American Electric Reliability Council is monitoring and reporting on progress on Y2K issues related to generation and transmission of electricity. APPA and its counterpart industry associations--the Edison Electric Institute and the National Rural Electric Cooperative Association--are monitoring and reporting on Y2K readiness as it pertains to distribution of electricity. APPA is responsible for monitoring all public power utilities--not just the 1,300 that are dues-paying members of the association. In June 1998, APPA surveyed all public power utilities to assess their awareness of the problem and their readiness to deal with it. In September, NERC reported industry-wide findings to DOE.

The association is preparing to set up a Y2K e-mail list serve network to facilitate exchange of information among APPA members and between utility members and APPA staff. To participate in this information-exchange group, send an e-mail to Mike Hyland:

mhyland@APPAnet.org.

In addition, APPA has published articles in Public Power magazine and Public Power Weekly newsletter providing information on resources available for addressing the problems. Experts on the topic have appeared at APPA meetings and workshops and information is posted on the APPA's Web site, visit the events section for more information.

Where can we go to get more information?

All information that APPA has prepared to assist its members on Y2K is available on this page. Utilities that need more information should call the association. Here are individuals to call:

Technical issues: industry assessment process: Mike Hyland, Director of Engineering Services, 202-467-2986, e-mail:

mhyland@APPAnet.org

Public relations and communications: Madalyn Cafruny, director of communications, 202/467-2952, e-mail: mcafruny@APPAnet.org

Congressional/legislative issues: Scott Defife, legislative representative, 202/467-2985; e-mail: sdefife@APPAnet.org

Attorneys/legal section: Dick Geltman, corporate counsel, 202/467-2934; e-mail: rgeltman@APPAnet.org.

There are also a number of other Web sites with useful information:

www.eei.org/EEI/press/y2k/ www.nerc.com/~y2k/y2k.html www.gao.gov/y2kr.htm www.kode.net www.euy2k.com/newsroom.htm www.year2000.com www.year2000.com/y2klawcenter.html www.y2kjournal.com www.nist.gov/y2k/ www.erols.com www.compinfo.co.uk/y2k www.tickticktick.com (the Y2K Quarterly News Letter) www.software.ibm.com/year2000/resource.html#cgp www.vendor2000.com www.y2k.gov www.sba.gov/y2k

Are there commercial resources available for helping address the Y2K problem?

Yes. APPA has not evaluated any of these commercial groups and does not endorse any. Listed below are a few vendors that are providing products and services to help electric utilities prepare address the year 2000 problem. As APPA receives suggestions from members or otherwise becomes aware of such commercial sources, we will add them to this list.

Electric Power Research Institute Tallahassee Training Institute TAVA/RWBeck Century Information Management Systems, Inc.

How should we respond when our customers and vendors ask how we are dealing with the Y2K problem?

Make no guarantees, as that is nearly impossible. Only indicate what you have done and are doing, but don't indicate future intentions that may not eventuate. If you are taking steps to address the problem in a systematic and responsible manner, you should indicate that.

What have Congress and the President done about the Y2K problem?

On Oct. 19,1998, President Clinton signed into law the "Year 2000 (Y2K) Information and Readiness Disclosure Act" This law provides limited liability protection to organizations that share information about solving the Y2K problem. The measure also creates a specific exemption from antitrust laws for entities that share information on Y2K solutions. It does not protect parties from damage claims related to a failure to make systems Y2K-ready. Nor does it cover statements by companies to individual consumers, as Congress and President Clinton believe it is important to protect consumers.

ADDITIONAL RESOURCES

Public Power Weekly Stories

NRC is Urged to Do More to Guard Against Y2K Mishaps (12/21) Wisconsin Public Power Sets Up a Y2K Database (12/14) Y2K Requirements Explained in Internet Articles (12/7) Problem is A Serious One for Utilities, Attorney Warns (11/16) Y2K Poses 'A Real Threat' Says APPA Report (11/2) Governmental Accounting Standards Board Requires Data About Year 2000 Readiness (10/26) Members of APPA Can Sign Up for New Y2K Computer Forum (10/19) Alliance Will Offer Y2K Support Services (10/12) Y2K Information-Sharing Bill Wins Congress' Swift Approval (10/12) NRC plans audits of 12 nuclear plants to ensure Y2K problems are addressed (9/28) Bill Seen Easing Y2K Information-Sharing (9/21) NERC Report Downplays Y2K Impact on Electric Utilities (9/21) Y2K computer problem draws international attention: Summit scheduled for London (9/14) Missouri PSC launches probe of Y2K readiness (9/7) EPA takes hard line on Y2K foul-ups (8/24) SEC takes action on Y2K computer problem (8/17) How Wisconsin Public Power tackled the Y2K problem (8/3) President Clinton says he'll introduce a bill to grapple with year 2000 computer problem (7/20) APPA offers information packet on year 2000 solutions (7/13) Tallahasse turns Y2K problem into an opportunity (6/29) Senate panel mulls over year 2000 computer problem (6/22) APPA gathering data about year 2000 computer problems (6/15)

Washington Report

Y2K, Ready or Not (August 1998) by Robert Varela

DISCLAIMER: This information is provided as a service of the American Public Power Association to its members. The information is gathered from the national trade press, state and regional associations and public power utilities.

This information is intended to be a starting point for further research and does not necessarily represent the latest research. The American Public Power Association shall have neither liability nor responsibility to any person or entity with respect to any loss or damage caused, or alleged to be caused, directly or indirectly by any information provided herein or through listed web site links. The American Public Power Association makes no endorsement of the accuracy, capability or functionality of any of the information, products or services mentioned.

ALL INFORMATION IS PROVIDED AS IS WITHOUT WARRANTY OR CONDITION OF ANY KIND. APPA EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

-- Anonymous, September 16, 1999

Answers

Judith,

When you reported that: "Part of being "Y2K ready" means having a contingency plan in case your systems go down." You are quite correct.

We decided early on that it would be useless to check that all of our own systems were compliant if the grid still failed due to any other companies inaction. Also we realised that although we may be 99.9% certain that all of our systems are OK, there is a chance that something may jump out to suprise us.

Therefore we have checked and tested our contingency plans. We have proved that we can operate all of our stations manually if required, and we have checked and practised our black start procedures in case our part of the grid does fail.

Another item that I have personally checked is to ensure that all of our generator tripping relays only accept inputs from other ancillary relays, and not from any PLC or other electronic device. I have also personally checked that should any tripping relay operate that it will display a flag at the source to indicate that it has operated, and that the causing relay will also show a flag indicating its operation. The tripping relay may output to the RTU and so indicate its operation on SCADA, but there is no way that a SCADA operation can cause a relay operation.

Thus I can be 100% sure that no Y2K issues at either of our hydro stations will cause a generator to trip, and that should any external influence cause a trip, then we can start again very quickly.

Malcolm

-- Anonymous, September 17, 1999

Malcolm,

Thanks very much for your informative reply. I'd like to forward your message to the Tennessee Valley Authority (TVA), the bulk electric company that provides power in our area, if you don't have any objections.

One question: Regarding a utility that does not generate, but simply distributes electricity, would any of these same contingency plans be appropriate, or would their needs be completely different? I'm guessing they would not need "black start procedures" or have "generator tripping relays," but I'm not sure about that, having no background in this subject. I'm just a neighborhood watch director trying to push for more local info and preparation, and concerned because our local "distribution" utility seems late in thinking about contingency plans. Any ideas on this would be appreciated.

Regards, Judy

-- Anonymous, September 17, 1999

Judy,

I can not answer for TVA as to what contingency plans might be appropriate. I imagine that they would probably roster additional staff to man any major substations in case of SCADA failure, but apart from that there probably isn't very much that they would need to do.

The control of transmission and distribution systems is not terribly complex. All lines are protected by relays (usually electro-mechanical), and therefore are unlikely to be at risk from Y2K issues. SCADA systems should not be able to have any input into any protection systems, and any circuit breaker operations due to SCADA should be direct to the tripping/closing coils in the circuit breakers. Thus SCADA can still be used to operate equipment, but not to protect it.

You could possibly ask to have a look through a substation, and once there look at the panels labled "xxx-yyy protection" where xxx and yyy are codes for either end of a transmission circuit. The panel itself may look complex with a number of relays and indicators, and will have additional lables such as "Distance Protection" or "Earth Fault Protection", but it is a stand-alone unit which has the sole task of detecting line faults and clearing them quickly. If you consider a transmission line to be like a generator in that both do carry electricty, then you can also see the relationship to the protection requirements.

Malcolm

-- Anonymous, September 18, 1999

Thanks for the information, Malcolm. A lot of it is over my head but I'm passing it along to some folks here who may be able to use it. The main thing I hear you saying is that the utilities that simply "distribute" electricity (rather than generating it) may not need much in the way of contingency plans, other than manning their substations. If that's the case, maybe our utility isn't so far behind after all, which is welcome news.

Regards,

Judy Hoskins

-- Anonymous, September 20, 1999