ML20235R480

From kanterella
Revision as of 14:52, 20 March 2021 by StriderTol (talk | contribs) (StriderTol Bot change)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Case Answer to Applicants 870820 Motion for Establishment of Schedule.*
ML20235R480
Person / Time
Site: Comanche Peak  Luminant icon.png
Issue date: 09/28/1987
From: Ellis J
Citizens Association for Sound Energy
To:
Atomic Safety and Licensing Board Panel
Shared Package
ML20235R471 List:
References
OL, NUDOCS 8710080066
Download: ML20235R480 (33)


Text

_ _ _ _ _ _

l 3

90thtif.0 UsHHC 9/28/87 UNITED STATES OF AMERICA ,g g g g .g NUCLEAR REGULATORY COMMISSION BEFORE TIIE ATOMIC RAFETY AND LICENSING BOARD *p [^6 5tQtqAj{/

E11:4L& 4tNVNr.

DRANCM In the Matter of }{

}{

TEXAS UTILITIES ELECTRIC }{ Docket Nos. 50-445-OL COMPANY, et al. }{ and 50-446-OL (Comanche Peak Steam Electric }{

Station, Units 1 and 2) }{ (Application for an

}{ Operating License)

}{

CASE'S ANSWER TO APPLICANTS' 8/20/87 MOTION FOR ESTABLISHMENT OF SCHEDULE Pursuant to 10 CFR 2.730(c), Intervenor CASE hereby files its Answer to Applicants' 8/20/87 Motion for Establishment of Schedule /1/. For the reasons stated herein, CASE opposes Applicants' Motion for Establishment of Schedule at this time as being premature, misleading, impractical and inefficient, and inherently flawed. CASE also opposes the specifics of Applicants' proposed schedule and is of f ering its own proposal herein.

Background

In January 1985, the ongoing hearings were suspended, at Applicants' request /2/. Since that time the Applicants have embarked upon a series of complex, confusing, and iterative reinspection and corrective action programs affecting virtually every aspect of the Comanche Peak plant design and construction.

(l_/ This answer is~being filed today in accordance with the Board l Chairman's ruling during a 9/23/87 conference call among the parties. j 1

l

/2/ See letter from Robert Wooldridge to Judge Peter Elech, January J 30, 1985; and statement of Michael D. Spence, President 9f TUEC, at public meeting January 17, 1985.

8710000066 G70929 PDR ADOCK 05000445 1 0 PDR i

-^'

l \

The original reinspection program, the Comanche Peak Response Team ,

(CPRT), Rev. O, was initiated on October 8, 1984. Its stated purpose was to do a " thorough and complete review of the safety-related issues identified by the [NRC's] TRT, and to resolve those issues which would ffect the safe operation of the Comanche Peak units," (Rev. O, at 15). At the time the program began, Texas Utilities intended to rely on it only to prove "that a safety basis exists to support authorization for fuel loading and pre-critical testing at Comanche Peak Unit 1 .. ." (letter f rom M. Spence to D. Eisenhet, October 8, 1984, page 4).

Almost immediately, without NRC Staff approval of the plan, Texas Utilities began to implement reinspection under the CPRT umbrella.

Af ter receiving critical comments f rom CASE and the Staf f, the Applicants issued Revision 1 of the Program Plan and hired two allegedly independent companies to work on design review and construction 0A/0C review.

In January 1985, the NRC issued a letter to Texas Utilities identifying significant problems with the construction OA/QC program at the plant. The Applicants requested a suspension of the hearings and subsequently modified the CPRT again, issuing Revision 2 on June 28, 1985, and later issued Revision 3 on January 25, 1986. The NRC Staff still had not approved the Applicants' reinspection program, yet TUEC proceeded under the CPRT --

allegedly at their own risk, i

According to the Plan itself, the purpose of Revision 2 was as stated i in a June 28, 1985 cover letter from TUGCO's W. G. Counsil to NRC Staff's Vince Noonan:

The overall charge to the Comanche Peak Response Team (CPRT) is to advise TUEC management whether there is reasonable assurance that Comanche Peak can be operated without undue risk to the 2

i public. Additionally, CPRT shall respond to and recommend resolution for 1RT and ASLB issues and remaining open SSER, CAT, SIT, IAP and certain Region IV issues.

The June 28, 1985, version of the CPRT incorporated a self-initiated evaluation program that was being conducted for the purpose of:

l

. . . assuring TUEC management of the safety of the plant '

regardless of the extent to which issues might have been raised by External Sources. (I. INTRODUCTION - OBJECTIVES, Page 1 of 22.)

. . . The result of this work (the self-initiated effort in the quality of construction area] will be a global reassurance of no undetected safety-significant hardware deficiencies; while the effort is undertaken primarily so that CPRT can provide assurance to TUGC0 management, it will upon implementation moot any issue that has been or could have been raised about the quality of CPSES construction.

. . . The result of this work (the self-initiated effort in the design adequacy area) will be global reassurance of no undetected safety-significant design deficiencies. (IV. PROGRAM STRUCTURE AND METHODOLOGY, Page 14 of 22.)

Against this backdrop, the Applicants filed their first Mot' ion for Establishment of Schedule (March 21, 1986). Their March, 1986, motion requested that there be a self-executing schedule which would automatically go into effect upon the day any results report was made available to the parties and the documentation in support of the results report was made available for review.

The cotion was opposed by CASE, and ultimately the Board ruled that:

Fairness, however, dictates that CASE not be deprived of the right to control the presentation of its own case in its own way.

A reason fairness lies so clearly on CASE's side is that it has already twice prevailed in this proceeding. It prevailed in December 1983 when we found that the Applicants had not sustained the burden of proof with respect to the safety of design of their plant. It prevailed again when Applicants decided to withdraw all of their filings made purquant to their approved plan by which they were attempting to demonstrate the inadequacy of the Board's findings about design. At this point, procedural fairness requires that the side that has twice prevailed have the opportunity to suggest a workable schedule that will give it control over the presentation of its case. (Memorandum and Order (Scheduling of Hearings), June 12, 1986, at 2.)

3

i

.o s Following an August 18 and 19, 1986, prehearing conference and ruling i l

by the Board, CASE intended at that time to complete discovery on the CPRT regarding construction and QA/0C of construction within a short time period and write summary judgement motions on those portions or aspects of the plan which even if implemented properly would not resolve the issues before the Board regarding the construction and QA/0C of construction of the plant.

Between September 11 and 18,1986, CASE did file twelve sets of interrogatories to the Applicants and on September 22, 1986, to the Staff, and on September 23, 1986, did notice the depositions of certain individuals with relevant knowledge of the program plan and its implementation. CASE also did conduct discovery on ISAP's I.a.4. and I.b.2., and further did examine the results reports and supporting documentation of ISAP's as they became available throughout the spring and summer of 1986.

In the late summer of 1986, CASE received the quality instructions and attribute checklists that detail the procedures being followed under all aspects of the CPRT program.

Finally, CASE has received Applicants' answers to the Board's questions on all of the ISAP's for which answers have been provided g/.

]_3_/ The inference of the Applicants' pleading is that CASE has ignored l those ISAP's that have been issued beyond the first ten that were j examined. The inference is that CASE has had continuous access for j some time to most necessary information and documents (ignoring the '

fact that CASE has often had to fight to obtain information which we deemed important). It further gives the impression that the time is l therefore now ripe for hearings and that, unless a schedule for l hearings is immediately set forth and begun, unnecessary and extensive delay will occur.

The fact is that Applicants' programs and other activities are at j this time perhaps the most confused and confusing that they have ever l been in this already extremely compicx case, with neither the '

(Footnote continued on page 5) l 4

1

L

m in the spring of 1986, TU began a program on design issues described in eleven Generic lssues Reports. .The first of these was issued July 9, 1986.

These were~ envisioned,'at the time of their inception, to be " proposed methods for' assuring resolution to external source issues" (July 9, 1986, letter TXX-4898 from TUGCO's W. G. Counsil to NRC Staff's Vince S. Noonan, regarding pipe stress analysis and pipe support design, sent to Board under cover letter from Applicants' counsel Mr. Wooldridge dated July 9,1986).

Notwithstanding all the review of the CPRT, its adequacy or inadequacy and the resultant reports and conclusions, the Applicants began a new

/3/ . (continued from preceding page):

Intervenor nor the NRC Staff at all certain exactly what Applicants are doing, under what program they are doing it, how portions of the.

now-many various programs (some of which have only recently even been named, much less explained or documented) interface, what portions of the many various plans and/or their results will be relied upon by Applicants.to attempt yet again to prove their case for licensing Comanche peak. It is not at all clear what kind of mixed-up hybrid unapproved conglomeration they currently plan to rely on. Even more in doubt is what Applicants will rely on when the time is actually ripe

'for hearings. As recently as yesterday, the following public comments indicating a heretofore unannounced five-month slippage were attributed to Applicants' John Beck:

Beck said the reinspection is concluding, and that re-evaluation of the plant's design and engineering is expected to be finished by 1988. Work to correct problems found in the design and original construction is expected to be finished in August. Beck said the plant should then be ready to load fuel.

The repairs originally were scheduled for completion in March. Beck said it is possible some of the' time can be made up. But if the schedule slips any further, he said the l projected date of early 1989 for commercial operation of the plant's first unit will be impossible to meet. (FORT WORTH STAR-TELEGRAM, Sunday, September 27, 1987.)

Contrary to the inference of the Applicants, CASE has been diligently at work (as indicated in our Progress Reports). With regard to the ISAP's, much of the discovery which CASE would have had to undertake was reduced or eliminated by Applicants' Board-ordered answers.

5

t e

approach to the problems at Comanche Peak. They did so without informing the Board or the parties of the significance of their new approach. It was not until an April 2, 1987, meeting between the Applicants and the Staff that CASE first understood the significance of the new program. It should be noted that it was not the Applicants' af firmative disclosure about the significance of the program but rather the deduction by CASE about the new l

l program. That deduction was stated by CASE at the meeting as follows:

. . . 1 am going to leave this meeting under the assumption that the DVP has become or is going to be an integrated document which -

allows the utility to have assurance on both design and construction and to state that there is no generic implications on

-- coming out of that DVP, that have not been fully resolved and fed back into the program. If that's not the case, I would like to see that clarified, because that's the understanding that 1 now of (sic -- should be: have). Anything that you found along the way is now fed into the DVP. You are going to stand on the DVP to give reasonable assurance. (Statement of Ms. Garde, April 2, 1987, meeting, Tr. page 57.)

By this time, the additional roles of Stone & Webster, Ebasco, Impell, TERA, and other consulting firms -- all operating under their own procedures and procedural formats as well as TU's -- began to increase the complexity of the program beyond manageable and comprehensible dimensions.

In January 1987, two years after the suspension of hearings, after the majority of discovery on the CPRT Plan regarding construction and QA/0C f or construction was completed, Applicants formally acknowledged that there was to be a Revision 4 to the CPRT. That Revision was not published until June 18, 1987.

Significantly, Revision 4 changed the Plan's purpose f rom providing assurance that the plant has been designed and constructed in accordance with 10 CFR, Part 50, Appendix B, to providing assurance that all undetected and uncorrected safety significant deficiencies would be found and corrected such that the plant could operate without endangering public ,

6

t ,

. I health and safety (Revision 4, PROGRAM PLAN, FOREWORD TO REVISION 4, page 2 1

l of 8, and changes in Revision 4, passim).

1 (No revisions to the CPRT procedures were provided to CASE, so {

1 presumably the methodology the CPRT was employing to reach a different f

! l '

purpose was through implementation of the same procedures.)

The Applicants also began to informally discuss their Corrective Action Program (CAP), with the NRC Staff. In April 1987, the Applicants presented i

a description of the plan to the Staff. Although CASE representative Billie Garde received no direct answer to her questions on any subject, and indeed TU officials refused to answer (see transcript of April 2, 1987, meeting  :

between the Applicants and the Staf f, Tr. page 57), it became obvious to CASE at that meeting that the CPRT had basically concluded its work and that the only remaining work was writing the final results reports and winding up work on the writtea report of collective evaluations and root cause/ generic implications as contained in ISAP VII.c and Collective Significance /

Collective Evaluation Reports.

However, the Applicants began to describe a mammoth corrective action j l

program that had not in April 1987 been shown to or shared with anyone -- {

either CASE or the NRC Staff.

I It was clear at that meeting that the envisioned finality of the CPRT {

l program had been abandoned. In short, the CPRT was no longer the document '

(and program) upon which the plant would be licensed.

In May 1987, CASE tabled the motion for summary judgement work until receipt of Revision 4, until CASE could reach a better understanding of the 1

l new CAP and its various components /4/, and to determine whether further f

3 / It is not at all clear to us if CASE, even now, knows what all the components are, and it assuredly does not know how they all work l together.

7

. _ _ _ _ _ _ _ ______________ _ _- - _ _ _ __ i

s work on the CPRT Plan would be moot. CASE's actions in this regard were discussed in depth with the Applicants and the NRC Staff.

When Revision 4 arrived in late June 1987, CASE shortly thereafter completed its review of the programmatic changes relevant to the CPRT Plan regarding construction and QA/0C of construction. CASE anticipated that

=

there would be extensive discussion and clarification during a scheduled July 29 and 30 meeting between Applicants and the NRC Staff regarding Revision 4, and CASE was prepared to participate to the extent allowed and to formulate our plans for completion of the work on the motion for summary judgment based in large part upon what we learned at that meeting. But at the public meeting at the end of July, the Applicants presented to the Staff not an update of the CPRT progress as planned but an overview of the new Corrective Action Program (CAP), et al. This meeting confirmed that the CAP, et al., would be the basis upon which licensing decisions would be made.

CASE had proceeded on the basis of what Applicants had represented until that time that they would rely upon to attempt to prove their case (i.e., the CPRT). Once CASE deducted that Applicants were changing not just some details of the CPRT Plan but rather that they were changing -- once again -- their latest "get well" plan itself, CASE realized that we needed additional information before proceeding with the summary judgment motion.

We hoped to have this clarified at the July 1987 meeting, but instead Applicants basically skipped right over Revision 4 for the most part and discussed something totally different.

Unfortunately for everyone, the presentation was not very definitive and made references to programs and pieces of programs that were unheard of by the Staff and by CASE (see transcript of July 29 and 30,1987, meeting, 8

Volume 1, Tr. page 2 et seq.; see also attached DALLAS TIMES HERALD article dated August 1, 1987, " Comanche Peak rework plan baffles agency").

What is absolutely clear at this point is that Applicants are not going to rely principally on the CPRT Plan, and it is unknown what part of the CPRT they are going to rely on (whether it be essentially nothing but general overview, a specific part or a specific ISAP, Results Report VII.c, I

or exactly what). It is also clear that, whereas Applicants had previously said that they were going to rely on the CPRT to prove that the original program worked, they have now said that they are going to rely on the CAP to show only that undetected and uncorrected deficiencies have been found and are no longer going to try to prove that the original program worked. It appears obvious to CASE that it would be impossible for Applicants to prove that the original program worked because it did not, and Applicants now know that too (although they have not yet, and may never, admit it).

Subsequent to the meeting, the Applicants have providedjt:l the Staff (with one copy to Mrs. Ellis, but not to the Board or service list) three documents which purport to set forth the CAP and its various components, a description of the program, and a statement of how the program is envisioned to work in providing a basis of f acts on the safety of the plant upon which the Applicant is prepared to operate the plant in the event that it gets a license. Those documents, dated August 20, August 28, and September 8, 1987, were not served on the Board, the parties or the service list; they were among the five documents specifically recommended by CASE for the Board's consideration at page 10 of its 9/14/87 Progress Report (VII). And even during the final preparation of CASE's instant pleading, on Friday, September 25, 1987, CASE's Mrs. Ellis received one copy of an additional document attaching the " Post Construction Hardware Validation Program 9

f Attribute' Matrix." (Copies are attached hereto of the August 28 cover letter, the September 8 letter, and the September 25 cover letter.)

CASE has not had time to thoroughly review these documents and has at this time reviewed them primarily for preparing this response. None of the procedures or checklists or. attribute checklists or criteria were provided-bytheApplicantsinthefilingsf5/.

Against all of this. confusion about what the Applicants are doing and for what purpose, they have filed this Motion for Establishment'of Schedule.

1. The Motion Is Premature The Applicants' request suggests that the issues to be tried in this case have semehow changed over the past two-and-a-half years from the extent of the quality control / quality assurance breakdown, the causes for that breakdown, and the implications for that breakdown to something else. They have confused the interest of CASE to litigate the programmatic aspects of the CPRT with the intent of CASE to prove that the CPRT could not provide a basis of fact to overcome the evidence on the record that there had been a

]S/ CASE believes that much of the discovery which would normally be necessary and proper on this new and significant information can be cut I

down considerably -- assuming cooperation by the Applicants -- through the taking of depositions which were previously anticipated to be only  ;

on the scope of the CPRT. Such depositions now must include, and CASE assumes that the Applicants are prepared for CASE to inquire at the depositions, to what extent the CPRT is going to be relied on by the CAP and to what extent the CPRT and/or the CAP is going to perform a basis for licensing. CASE believes that it is absolutely essential (especially if we are to lessen what would otherwise have to be )

extensive discovery) that Applicants see to it that those individuals J CASE deposes will be so prepared to answer those questions. These depositions could provide CASE with the opportunity to discover (in an expedited fashion) to what extent our anticipated motion for summary judgment may be appropriate.

10

)

I pervasive breakdown in the OA/0C program at Comanche Peak such that it could not be licensed.

CASE's interest in this regard has been and continues to be, as we have repeatedly stated, to have the Board reach a determination on the extent of the breakdown, the causes of the breakdown, and the generic implication of those causes.

Short of a finding of some type, whether by admission or declaration, that there was a historical pervasive breakdown based on the evidence before the Board, CASE must insist on its rights to pursue such a finding by the Board. Prior to the continuation of that aspect of the hearing process it will be necessary for the Applicants to release all the data in their possession related to the extent and causes of the design, construction, and QA/QC breakdown. At that point CASE will complete its affirmative case on those issues and seek a' ruling that there has been a pervasive QA/QC breakdown in design and construction and that the Applicants have failed to establish that Comanene Peak was designed or constructed in accordance with regulatory standards.

1 If CASE fails to establish its case at that stage it will have lost on j those issues and there would be no point in going forward on those issues; however, if CASE prevails, the Applicants must come forward with their ,

rebuttal case on those issues. j i Presumably, the Applicants' rebuttal case will be, as they have 1

recently indicated, that the CAP and its results will prove their case:

4

. . . the CAP and its results will be a significant part of the basis for our request to the NRC for an operating license for CPSES . . . (Applicants' letter of August 28, 1987, to U. S. NRC, TXX-6675, copy attached.)

The CPRT Results Reports on individual ISAP's, and/or on root cause determination will be relevant only to the extent that they are to be relied l

11 c_-_____________________-____-__. _ -_ -

e upon by the Applicants, or used by CASE for demonstrating that there was a pervasive breakdown and/or that all the deficiencies have not been detected and/or corrected.

2. The Proposed Schedule is Illogical and Impractical The Applicants propose a " trigger date" schedule that activates a self-l propelling time schedule on each of the five types of reports that has been prepared over the past two years or that will be completed in the next six to eight months (pages 7 through 10 of Applicants' August 20, 1987, Motion s for Establishment of Schedule).

The schedule then moves forward to a hearing with a 10-day provision for the NRC Staff or CASE to move to defer the litigation in the event of the interdependence of the report on another report.

The proposed schedule puts the Staff on a 30-day time limit to evaluate the report and allows only 10 days for CASE to prepare and serve discovery on the Staff. The schedule anticipates that CASE will, on the 55th day after the trigger date, make a decision on whether to contest the report, how it intends to contest the report, and what position it takes on the matters in contention.

Following this 60-day hurdle, CASE is to prepare direct testimony and the rebuttal testimony, and wait for a hearing.

The schedule puts as equal 55 results reports of fairly narrow technical focus with which. CASE has some familiarity, has studied the procedures and programmatic aspects of the ISAP, and has answers to detailed Board questions, and probably was the direct or indirect source of the item in the first place, with major Project Status Reports which are incomplete, totally unknown to CASE, and based on a program which is also completely 12

l unknown, according *to procedures not yet disclosed.

Additionally, the proposed schedule assumes that CASE can absorb, digest, analyze, process, and take a position on conclusory documents in a matter of days, that the Applicants have taken years to prepare. Further, CASE is expected to take a position before discovery is adequately completed. (There is no reason to assume that the Applicants will provide access to documents any easier now than they have in the past, unless the new strategy is that they will dump "in process" data on CASE all at once in a manner that is humanly impossible to review. The Board has consistently promised that CASE would not be adversely impacted by Applicants' decision not to provide such data earlier in the process.)

The schedule does not provide a freeze date for non-compliance by the Applicants with discovery requests, or for the irability of the NRC Staff to comply with the imposed dates for completion of their evaluation f6/.

The Applicants apparently intend to rely principally on the Project Status Reports (PSR's) of the Corrective Action Program for licensing. The PSR's seem to rely on come of the results from the CPRT. However, we do not know what results or what role those results will play in the CAP.

Presumably the procedures and detailed programmatic descriptions of the CAP delineate which parts of the CPRT will be relied upon as a basis for TUEC's diverse efforts; however, until those portions of the CPRT are identified it is illogical and, therefore, inefficient to proceed to hearing with all if the new program is even remotely similar to the CPRT, it is safe to f6/ assume that the Staff, as well as CASE, will have numerous questions on the completed reports. (As recently as September 16, 1987, the NRC l Staff was requesting odditional information on ISAP Results Reports II.c and V.a; see letters dated September 16, 1987, from NRC's Christopher I. Grimes to TUEC's William. G. Counsil under subject:

Request for Additional Information on 1 SAP Results Report.)

13

4 the CPRT results reports as if they were going to be evidence offered in the case by Applicant or relied upon by CASE for rebuttal or impeachment in this case.

3. The Process from here to licensing must be based on finality and full disclosure.

CASE asserts that the moving target must stop. CASE has been at this juncture several times before. This is not new. (See, for instance, Board's Memorandum and Order (Scheduling of Hearings), June 12, 1986, portions of which are quoted at the bottom of page three of this pleading; see also Board's December-28, 1983, Memorandum and Order, LBP-83-81, 18 NRC 1410 et seq. f7/.)

CASE believes that all participants in these proceedings are ready for the next hearings to be the last setofoperatinglicensehearings/8/.

CASE adamantly opposed the " laissez faire" policies of the Staff and the Board in regards to the CPRT and the work done.under it, and the CAP, and the work being done under it. Nonetheless, the Board ruled that our Motion for an Evidentiary Standard was premature because the Applicants' program might be similar to what we were seeking (Board's March 12, 1985, Memorandum (CASE Motion for Evidentiary Standard)). Additionally, the Board 17/ CASE is not specifically addressing in this filing Applicants' continual harangue regarding design issues, since Applicants (although grudgingly) " acknowledge this Board to have previously ruled that design issues are also within the scope of Contention 5" (Footnote 7, i

page 4, Applicants' August 20, 1987, Motion for Establishment.of l

Schedule.) We do note, however, that CASE has previously addressed i this matter in some detail (see, for instance, CASE's 11/4/85 (Main Docket) Answer to Applicants' 10/21/85 Petition for Directed Certification of Licensing Board Order of October 2, 1985, pages 14 through 19).

/jl/ Applicants did not address, and CASE does not address here, the Construction Permit proceedings.

)

14 l

- - - _ - -__a

1 denied our plea for mandatory disclosure of all information on the basis of i the Applicants' "in process" argument.

Those decisions were all based on the theory that Applicants themselves asserted, that is, they are building the plant and can choose what evidence to submit to support their licensing request.

CASE, on the other hand, has a right to seek all available information on the extent, causes, and implications of the OA/0C breakdown to determine how it will prove that there was a prevasive breakdown such that a reasonable assurance finding is not possible, and why the current programs in place will not resolve these generic implications.

CASE's alternative schedule is based on the logical progression of the case, following the issues now before the Board, and the resolution of those issues in a logical and efficient manner. It does not include time / deadline dates because those dates are, at best, hypothetical and are controlled by the Applicants' release of reports and materials that will surely produce an impossible burden that CASE has diligently sought to avoid by its conscientious pursuit of facts.

Conclusion Applicants have once again moved this tribunal for a scheduling order which would propel the Board and the parties on the most expansive hearing schedule the NRC has ever undertaken. The impetus for the proposed schedule is the eminent completion of the CPRT and the responsive Corrective Action Program. The results of embarking on such a proposed schedule would be wave upon wave of discovery while CASE first tries to determine just what plant the Applicants want to license -- the plant as originally envisioned prior to the iterative design process, the plant as it was built, the plant 15

b. -- - . . _ . _ _ _ _____..m__ _ .2 _ _ 1.___.

as it has been redesigned, the plant that was reinspected, the plant as inspected by the NRC Staff, or the final plant which they intend to operate.

CASE requests that the Board ensure that there be only one final set of licensing hearings and that any schedule adopted by the Board and imposed upon the parties be consistent with reality, fairness, and finality. \

Respectfully submitted, Anthony Z. Roisman Suite 600 -

1401 New York Ave., NW Washington, DC 20005 202/628-3500 Co-Counsel for CASE Billie Pirner Garde, Esq.

104 E. Wisconsin Avenue - B Appleton, Wisconsin 54911-4897 414/730-8533 Co-Counsel for CASE JL/& bi President Os 7(Mrs.) Juanita Ellis, vCASE (Citizens Association for Sound Energy) 1426 S. Polk Dallas, Texas 75224 214/946-9446 Co-Representative for CASE 16

1 1

l 1

CASE's Proposed. Schedule 1 For Completion of Operating License Hearings

  • j On CAP and All Related Components )

Step 1. . Day O' Applicants identify that final design of the plant, the FSAR, construction of the plant, and QA/QC ,

of the plant that it intends to rely j upon to get a license. Applicants 1 must disclose specifically what f portions of the CPRT, CAP, et al., j they intend to rely on. Applicants I provide all ia.c.al information relevant to t'.c extent and causes of the 0A/0C bieakdown on discovery **. j d

Step 2. Day 1 (5 days after Board CASE files next phase of discovery rules on Proposed on design.

Schedule)*** 3 1

Step 3. Day 15 Applicants and Cygna respond to CASE's previously filed motions for summary disposition. ,

Step 4. Day 15 Applicants complete all design review and produce all documents  !

generated by it or any of its contractors, consultants, etc.,

related to the design review.

Step 5. Day 15 Staff responds to CASE's previously filed motions for summary disposition.

Step 6. Day ___ (10 days after CASE discovery to Staff and Step 5) Applicants based on responses to summary disposition motions. l l

Step 7. Day ,_,(30 days after Applicants and Staff respond to Step )

Step 6) 6 discovery.

Step 8. Day __,(30 days after com- CASE reply, if any, to Applicants pletion of Step 7) and Staff responses to summary l 1

disposition motions.

Step 9. Day ___ (45 or 120 days after Parties file final discovery on completion of Step 4)**** design other than requests for admissions and depositions.

Step 10. Day ___ (30 days after Applicants and Staff respond to Step Step 9) 9, including Staff final position on design issues.

I 1

_ _ __ - _ - _ --._.__ _-_ ____ _ - .=_ - . _._. - ._- . _ _- _-,_ - .

1 I

-. j 1

i 1

Step 11. Day __,(60 days after com- Parties identify issues for hearings J pletion of Step 10) (or depositions in lieu of hearings) and file requests for admissions.

)

i Step 12. Day ___ (15 days after Staff Depositions in lieu of hearings and Applicants respond to commence.

requests for admissions)

Step 13. Day ___ (30 days after com- Parties file prefiled testimony for pletion of Step 12) hearings and all documents upon which that testimony relies identified and produced (if not already produced).

Step 14. Day ___ (20 days after com- Hearings begin, and, following their pletion of Step 13) completion, and proposed initial decision is issued on design issues.

Step 15. Day ,__ (30 days after All parties file final discovery completion of Step 14) other than depositions and admissions relevant to CPRT/ CAP, e_t, al,., edequacy.

Step 16. Day ___ (10 days after All parties respond to Step 15.

completion of Step 15)

Step 17. Day ___ (10 days after Step All parties commence depositions in 14 or 16, whichever is lieu of hearings on CPRT/ CAP, et later) al., adequacy.

Step 18. Day ___ (10 days after avai3- All parties file requests for ability of transcripts from admissions, motions for summary Step 17 in the PDR in D.C.) disposition, identify issues for hearings, and file preliminary proposed findings of fact and conclusions of law.

Step 19. Day ___ (10 days after Prefiled testimony of all parties Step 18) with all documents relied upon in preparing testimony identified and produced (if not previously produced).

Step 20. Day __ (4 days after com- Hearings begin, and, following their pletion of Step 19) conclusion, an Initial Decision is issued.

Step 21. On the days Applicants Applicants make available all release each Results Report documents generated by it or any contractor, consultant, and the like in preparation of the Results Report and all documents reviewed in preparing the RR.

2

Step 22. 60 days after completion of CASE and Staff file their analyses Step 21 for each RR, with and critiques of each Results total time being at least Report.

30 days for each RR released Step 23. 10 days after completion of Parties file discovery as to each Step 22 for each RR Results Report except depositions and admissions.

Step 24. 15 days after completion of Parties begin depositions in lieu of Step 23 for each RR, or 30 discovery on each Results Report.

days after completion of Step 20, whichever is later Step 25. Day ___ (10 days after avail- All parties file requests for ability of transcripts from admissions, motions for summary Step 24 in the PDR in D.C.) disposition, identify issues for hearings, and file preliminary proposed findings of fact and conclusions of law.

Step 26. Day __,(10 days after Prefiled testimony of all parties Step 25) with all documents relied upon in preparing testimony identified and produced (if not previously produced).

Step 27. Day ___ (4 days after Hearings begin, and, following their Step 26) completion, an initial decision is issued.

i Step 28. Day ___ (15 days after com- All parties file any final discovery pletion of Step 27) with respect to remaining issues in Phase IV.

Step 29. Day __,(30 days after com- All parties file requests for pletion of Step 28) admissions, motions for summary disposition, identify issues for hearings, and file preliminary proposed findings of fact and conclusions of law.

Step 30. Day __ (10 days after Prefiled testimony of all parties Step 29) with all documents relied upon in preparing testimony identified and produced (if not previously produced).

Step 31. Day ___ (4 days after Hearings begin, and, upon their Step 30) completion, an initial decision is issued.

l 3 1

L This schedule is similar to that filed by CASE on June 30, 1986, because at this point it still seems the most logical. Because Applicants have held back so-called "in process" documents from the design review, the CPRT, and more recently the CAP and other related components, and depending on the volume of material, timing of release of design reviews and Results Reports and production of relevant documents, and the extent to which the design reviews and Results Reports are flawed, it is not clear when this schedule can be completed. This is wholly the result of Applicants' refusal to share documents with CASE when they come into existence and their constantly changing "get well" plan. This Board has previously ruled that the delay in producing available documents will not prejudice CASE by forcing CASE to read and analyze the documents in less time than it would have had if the documents had been timely produced. This schedule is based on our best judgment of the time we will need and the time to which we are entitled. In many instances we propose less time than rigid application of the day-for-day-of-delay principle would allow. This is an accommodation within the context of the proposal and not a waiver of the right to apply that principle should the schedule proposed not be adopted.

This schedule does not include any further discovery on the adequacy of the CPRT Program Plan for construction and construction QA/0C, which will hopefully be completed with the completion of the depositions (see further more detailed discussion at Footnote 5 on page 10 of this pleading).

Including, but not limited to, all expert analyses by all of the owners (including the minority owners) regarding the condition of the plant, the design, construction and/or QA/0C of the plant, and the extent and causes of the breakdowns.

      • " Day" is the date on which the step is to be commenced and/or completed. Some items like depositions or hearings will commence on one day and conclude in an indefinite future. Other dates may slide depending upon how quickly and thoroughly Staff or Applicants respond to discovery. Some dates or series of dates may change depending upon agreement of the parties.

Assuming Applicants produce all design documents when they come into existence and when each part of the design work is finished, then the time in Step 8 could be as little as 45 days. However, if all documents are held until all design work is completed, then 120 days is a minimum time required and more may be necessary depending on the volume of the material.

4

D

)

I i

' Dallas Times Herald Saturday, August 1,1987 B3

]

Comanche Peak rework plan baffles agency Esocurro mtss complex plant on record and of Fort Worth, is scheduled to said utility officials muddied begin commercial operation in Two days of explanations the waters further with some of 1989, nine years later than ex-have not helped the Nuclear their explanations. pected.

llegulatory Commissior under. The NRC must approve the stand a massive rework plan at TU Electric orncials said the plant's operating license. rework program is about two the Comanche Peak power The outlines of Comanche rnonths behind schedule, but plant. agency orncials said. Peak's reinspection and rework "Qinte frankly, we still can't that the plant's opening proba-program became a little clearer, bly will not be delayed because see the whole picture " said however, during this week's or it, Christopher Grimes, head of meetings requested by the the Comanche Peak division of NItc. 'I,he rework plan for Coman-the agency's Office of Special Officials for TU Electric said che Peak was rnassive wien it Projects, that in addition to reinspecting was begun two years ago. It has The multimillion dollar rein- all design work related to safe- expanded continually, however, spection and rework program ty, they are challenging the as TU Electric and outside con-was designed to make the plant quality of almost every piece of sultants found more and more near Glen Rose safe to operate, safety related construction problems.

The plant, being built by TU work in the $7.7 billion plant. Last August, the company Electric, is years past its The plant's original archi- announced that the design and planned opening and millions tect engineer has been taken off engineering of all safety related of dollars over budget. all design and engineering portions of the plant would be NRC officials this week work. One construction subcon- re-evaluated, and that what had called the Comanche Peak tractor also has been replaced. been built would be changed to plant the most complicated and The plant,45 miles southwest c9rry out the corrected design.

l l

1 mumsmeaummum Log

1UELECTRIC wah c. cme August 28, 1987 nerussa var nes,sem U. S. Nuclear Regulatory Commission Attn: Document Control Desk Vashington, D.C. 20555

SUBJECT:

COMANCHE PEAK STEAM ELECTRIC STATION (CPSES)

DOCKET NOS. 50-445 AND 50 446 CORRECTIVE ACTION PROGRAM (CAP)

DESCRIPTION AND FLOW DIAGRAMS Centlemen:

TU Electric is determined to take all necessary actions to provide reasonable assurance that CPSES has been properly designed and constructed and can be safely operated. The TU Electric approach in taking these actions is to strive for excellence and not be satisfied with simply meeting minimum regulatory requirements. The CAP exemplifies the TU Electric approach in taking action providing and is assurance.

reasonable a vital and fundamental element of the oversal plan in Because the CAP and its results will be a significant part of the basis for our request to the NRC for an operating license for CPSES, it is imperative that we provide a clear understanding of the CAP to the NRC staff. The public meeting held on July 29 and 30,1987, between TU Electric and the NRC, revealed a need for TU Electric to provide additional detail on the CAP.

Accordingly, enclosed is material, including flow diagrams, which is organized to individually address each of the eleven units of the CAP.

Should you desire additional information on the CAP, please contact me.

Very truly yours, N. $. Cme =?

W. G. unsil By: 4-A-

  • L. D. Nace Vice President, Engineering and Construction RSB/mlh Enclosure c - Mr. C. I . Crimes Mr. H. E. Schierling Mr. R. D. Martin, Region IV Resident Inspectors, CPSES (3) )

]

400 North Olwe Street L.B 81 Dallast Tenas 75201 i

l "l' ,

er. -

M Log = TXX-6712 -

F9 File

  • 10004 illELECTR':

wmam c. counia ept uber 8, H37 ve.utu ne unwam U. S. Nuclear Regulatory _ Commission Attn: Document Control Desk' Washington, D.C. 20555

SUBJECT:

COMANCHE PEAK STEAM ELECTRIC STATION (CPSES)

DOCKET N05. 50-445 AND 50-446 ,

POST CONSTRUCTION HARDWARE VALIDATION PROGRAM (PCHVP)

ENGINEERING EVALUATION METHODOLOGY

REFERENCE:

1) TV Electric Letter TXX-6631 from W. G. Counsil to tne NRC dated August 20, 1987
2) TV Electric Letter TXX 6675 from W. G. Counsil to the NRC dated August 28, 1987 Gentlemen:

At the public meeting 'on July 29 and 30, 1987, between TV Electric and the NRC, TU Electric presented the Post Construction Hardware Validation Program (PCHVP) as the element of TU Electric's Corrective Action Program (CAP) which validates the final acceptance attributes for safety-related and selected non-safety related hardware. TV Electric indicated that this validation of attributes defined in an attribute matrix, developed frcm the validated design specifications, would be implemented via physical validations (Quality Control Reinspection / Engineering Walkdowns) or engineering evaluations. Discussions at the public meeting of this methodology focused on the engineering evaluations. These discussions indicated to TV Electric that additional detail with respect to the conduct of engineering evaluations during tne PCHVP might be beneficial to the NRC staff.

TV Electric is submitting the attached executive summary of the engineering evaluation methodology that will be implemented during the conduct of the i PCHVP. The information in this executive summary is intended to supplement ed expand upon information provided to the NRC staff at the public meeting a Q via the above referenced letters submitted to the NRC staff subsequent to the public meeting.

i If you have any huestions in this regard, please do not hesitate to ask.

Very truly yours,

^/  ?

I W. G. Counsil RSB/mlh Attachment M Mnh Oine Street LB 81 Dallas. Teus '!.'01 I

. I L _ - - - - _ _ - - - - - - - - -

]

i t

TXX-6712 September 8, 1987  !

Page 2 /'

c - Mr. C. I. Grimes Mr. H. E, Schierling ,

Mr. R. D. Martin, Region IV Resident inspectors, CPSES (3) r-q l

!p

/ i

/

I f

f

./

'\

r o

i 1

I I

/ i a .

)'

r

  • - * ,. ' ~_ "w',~ ,n(( 'I M de ) EMJ --

mp, , 7g 1 ,

i

['flN4 +

ANa$1Sntt[Td6722 Sepfember8,'LI937 Page 2 dl % '>

I

. EXECU18VE

SUMMARY

OF THE PDS CONSTRUCTION HARDWARE VALIDATION PROGRAM ENGINEERlHG EVALUATION METHODOLOGY

?

i

1.0 INTRODUCTION

' x The Post Centruction Hardware Validation Program (PCHVP) is that element of TU Eltctric's Corrective Action Program (CAP) which validates the final accepterce attributes for safety-related and selected non-safety related hardware. The PCHVP meets regulatory requirements and

'; has been developedt to be consistent withthe high' standards of

j. t excellence expected by TV Electric. >

The initial input parameters to the.FCHVP are contained in the installation specifications. The Wtallation specifications implement the licensing commitments and design criteria of the Design Basis l Documents (DBDs), which were developed during the CAP contractors' i p,. Design Validation process. /

l Final acceptance inspection req'uirements identified in the validated

) installation specifications were used to develop the PCHVP attribute 1 l matrix. This matrix is a complete set of finai acceptance attributes identified for installed hardware. {

l The PCHVP by either physical validations (not discesed in this executive summary) or through an engineering evaluation methodology, i assures that each of the attributes defined in the attribute matrix is

/f validated. This program will provide reasonable assurance that the

,/ validated design has been effectively implemented for safety-related and selected non-safety related hardware.

The PCHVP engineering evaluation is procedurally controlled to guide the responsible engineer through the evaluation of each item on the attribute matrix to be dispositioned by the engineering evaluation method. Dispositions of each attribute will be clearly documented. If the technical disposition of the final acceptance attribute is "not acceptable" or the attribute cannot.be dispositioned based on available information, an alternate plan consisting of additional evaluations, testing, inspections /walkdowns or modification as necessary will be developed to demonstrate and document the acceptability of the attribute. The currently availa,orocedure ble on site controlling thisreview.

for NRC staff engineering evaluation The purpose is

.of the Executive Summary is to provide, for the NRC staff's review, sufficient detail to adequately describe the engineering evaluation method of validation. Quality Control reinspection / engineering walkdowns are controlled by the appropriate Field Verification Method and are not described herein. ,

f r

i

_ n: 0

' t . '

. ittar,hment to W K-6712 September 8,1987 PageIgf6 2.0 DETAR5 # '

l Figure 1 illustrates the process that is being used in the PCHVP engineering evaluations. Each attribute identified in the attribute matrix is dispositioned. Appropriate aspects of the engineering, qality, and oversight organiza!. ion are involved in this disposition.

Recommendations from the Comanche Peak Response Team (CPRT) effort comprise a sigr.iMcant portion of this evaluation. A major component of the CPRT program ha's been the reinspection of a comprehensive, random sample of existing hardware using an independently derived set of inspection attributes. The reinspection was performed and the results evaluated by third party personnel per Appendix E to the CPRT Program Plan (submittal from TU Electric via letter TXX-6540 from W. G. Counsil to the NRC dated June 25,1987). The scope of the reinspection covered 100% of the then final quality accepted installed hardware by segregating the hardware into homogeneous populations (by virtue of the work activities which produced the finished product). These populations were sample reinspected to at least a 95/5 confiderce level on an attribute basis per Appendix D to the CPRT Prograin Plan.

"B '

Corrective .ction recommendations were made to the TU Electric project y' - based on the evaluated findings when a) a. Construction Deficiency existed, b) an Adverse Trend existed, or rd an Unclassified Trend existed, all 3s defined per Appendix E to the CPRT Program Plan.

' The PCHVP assures that all CPRT recommendations are properly dispositioned.

Figure 1 illustrates that, during the engineering evaluation of a given attribute from the PCHVP attribute matrix, the initial task of the ,

I responsible engineer is to determine if any of the following statements are true:

l

a. The attribute was recommended for reinspection by the CPRT.
b. Design Validation resulted in a change to design (e.g.,'any design  !

document, Corrective Action Request (CAR), Significant Deficiency l Analysis Report (SDAR), etc.) or acceptance attribute .that is more stringent than the original acceptance criteria,

c. Design Validation resulted in new work, including modification to existing hardware.

i

(

= - - - _ _ - _ _ _ _ - _

.o .

Attachment to TXX-6712 September 8, 1987 Fage 3 of 6 If the CPRT had no recommendations and items b or c, above, do not apply, the attribute under consideration will be accepted. This conclusion is justified by the comprehensive coverage of the CPRT reinspection and the consistently conservative evaluation of each finding from both a statistical and adverse trend perspective. The attribute natrix is then updated to indicate that neither engineering walkdown nor quality control reinspection of the attribute is necessary.

A completed evaluation package is prepared and forwarded to the Comanche Peak Engineering (CPE) organization for concurrence. The evaluation package is vaulted after CPE concurrence is obtained.

If any of the three statements are true, it is assumed that the final acceptance attribute must be further evaluated as follows:

2.1 Determine Attribute Accessibility The responsible engineer will determine if the attribute is accessible as defined in the implementing procedure. If the attribute is accessible, a field validation of the item's acceptability will be performed and documented in accordance with an approved Field Verification Method (FVM).

If the responsible engineer reaches the conclusion that the attribute is inaccessible, an engineering evaluation will be conducted by technical disposition of available information.

After completing the attribute accessibility review, the responsible engineer will update the attribute matrix as necessary I to reflect the results of that review.

2.2 Technical Disposition The responsible engineer identifies the data to be considered during the subsequent technical disposition process. Examples of such items used in this disposition may include, but are not limited to:

o Historical Documents (e.g. Specifications, Procedures, i

Inspection Results);

o External Source Issues; o Construction Practices; I o Quality Records; o Test Results; o Audit Reports; I

o Authorized Nuclear Inspector (ANI) Records; o Surveillance Reports;

Attachment to TXX-6712

. September 8, 1987

(

Page 4 of 6 o NCRs, DRs, SDARs and CARS; o Reinspection conducted to date; o Results of Third Party Reviews; o Purchasing Documents; o Construction Packages; and o Receipt Inspections.

After compiling the data identified as pertinent to the attribute, the technical disposition will be performed. The actual steps and secuence of actions required for each technical disposition will differ; however, the tangible results from each technical disposition will be consistent. These results will include as a minimurs:

a. a written description of the attribute;
b. a written justification by the responsible engineer and approved by the responsible engineer's management for acceptance of the attribute;
c. a written explanation of the logic utilized to conclude that the attribute need not be field validated;
d. a chronology demonstrating that the attribute has not been significantly altered by redesign;
e. all documents viewed to support the disposition; and
f. concurrence of the acceptance of the attribute's validity by CPE.

If the responsible engineer concludes that the data evaluated represents evidence of the attribute's acceptability, the conclusion will be documented in an Attribute Evaluation Report.

The report and supporting documentation will be reviewed and approved by CPE Management and vaulted. If the responsible engineer determines that the data reviewed does not provide evidence of the attribute's acceptability, the Attribute Evaluation Report will explain why the attribute cannot be validated and recommend an alternate course of action. The

' alternate course of action may take various forms; such as, making the attribute accessible and reinspecting it, or testing to support the attribute's acceptability. This alternate plan, after approval by CPE Management, will be implemented to validate the attribute.

- - " ^ - ~ - - ~ ^ ' " ' ' ^ ^ ^ ^

.4. . .

E*

. September 8, 1987

,' Page 5 of 6 3.0

SUMMARY

The. process above describes a comprehensive process by which each attribute in the PCHVP attribute matrix is validated to the validated design. The TU Electric Quality Assurance Technical. Audit Program will audit the PCHVP. This audit program is complemented by the Engineering Functional Evaluation being performed by an independent team comprised

. of Stone and Webster, -Impell and Ebasco engineering personnel working ur. der the Stone and Webster QA Program and subject to oversight directed by the CPRT's' Senior Review Team.

This combination of audit and independent oversight provides assurance that the PCHVP has been effectively implemented.

G ... September,8, 1987 e Page 6 of 6

  • ~

FIGURE 1

.POHVP ENGINEERING ......-....

EVALUATION METHODOLOGY g MATRIX DEVELOPMENT l

'l IDENTIFY ATTRIBUTE I s l l l l l l l COMPILE ATTRlBUTE I MATRlx '

I j l

...;...... I

, ENGINEERING EVALUATION I I I CPRT I

_ TRUE

, RECOMMENDS I g

RE -IN S P E CTION 1 1 I I I FALS E I '

I I I I I I DE SIC N g I

-- 7pyr- - VA LID ATIO N

? i I g

'N!

SiSUg!#gCMANCEDa@ l l 8 i FALSE g I IDENTIFY r AND g l

1 l

COMPILE

- E5 N g DATA I VA IDA 10 N l

,TRUE M (q[N MOD. k g I

I y

l PE RFORM

'* E xlSTIN C g TE CHN! CAL I RDWARE OtS PC $1 TIC N

~

g l UPDATEI* i i FALSE g MATRIX 1 I I I l PE S U LTS ND ACCEPTABLE g I

T g

I g 1 l

, ( YE S T I COMPLETE DEVELOP I g

  • EVALUATION ALTERNATE I 15 PACKA;g PLAN g ATTRIBUTE N3 0 g

ACCESSIBLE *

? g I g r i YE5 g I 1'

l CPE I l l UPDATE M ATRIX l  ; -

CONCURRENCE I g  ? l I I

_ UPDATE YES g MATRIX L = . . . . . . . .

1 l g {

l VAULT l i FvM g i i

i TiETD~  !

g VAh!D,ATjoN , ,j l

l

_ _. __ _,J

,, o LOG I TXX-6783 File # 10004 mmmmmm mmmme

._=

e-

_ ~

TUELECTRIC Milliam f. ( ournit t w. .a,, , i ,. . i,.~da September 23, 1987 U. S. Nuclear Regulatory Comunission Attn: Doctusent Control Desk Washington, D. C. 20555

SUBJECT:

COMANCHE PEAK STEAM ELECTRIC STATION (CPSES)

DOCKET NOS. 50-445 AND 50-446 POST CONSTRUCTION HARDWARE VALIDATION PROGRAM A'ITRIBUTE MATRIX Gentlemen:

Enclosed is the Post Construction Hardware Validation Program (PCHVP)

Attribute Matrix. The PCHVP Matrix, which has been discussed in recent submittals involving the Corrective Action Program, has been issued in accordance with our procedure EC 9.04, " Post Construction Hardware Validation Program."

TU Electric has delegated the responsibility for maintenance of the PCHVP Attribute Matrix to Stone and Webster Engineering Corp.

(SWEC) using input from the Lead Contractor organizations as specified in procedure EC 9.04. Procedure EC 9.04 (in conjunction with SWEC procedure PP-220) establishes the measures for production, revision and control of the PCHVP Attribute Matrix.

The PCHVP Attribute Matrix is a dynamic document which may need to be revised periodically. An updated copy of this PCHVP Attribute Matrix will be available onsite for your audit and, at your request, will be provided to onsite NRC personnel.

Very truly yours,

.l

^f7 /7l?&

W. C. Counsil RSBial Enclosure c- Mr. C. I. Crimes Ms. M. Malloy Mr. R. D. Martin, Region IV Resident inspectors, CPSES (3) l u %,rth Oine Ntreet i H >f Dauam le w 'S, '

i

.,y,,.*

800KET E UbHRC -

TT E:T -5 P4:44 UNITED STATES OF AMERICA NUCLEAR REGULATORY COMMISSION .$ fiY G C f.'

BEFORE THE ATOMIC SAFETY AND LICENSING BOARD AN

'In the Matter of }{

}{

TEXAS UTILITIES. ELECTRIC- }{ Docket Nos. 50-445 COMPANY, et a_l, . }{ and 50-446 (Comanche Peak Steam Electric }{

Station, Units 1.and 2) }{

CERTIFICATE OF SERVICE By my. signature below, I hereby certify that true and correct copies of CASE's Answer to Applicants' 8/20/87 Motion for Establishment of Schedule have been sent to the names listed below this 28th day of September ,19S 7, by: Federal Express where indicated by

  • and First Class Mail elsewhere.

Administrative Judge Peter B. Bloch

  • Thomas G. Dignan , J r. , Esq .

U. S. Nuclear Regulatory Commission Ropes & Gray Atomic Safety & Licensing Board 225 Franklin Street Washington, D. C. 20555 Boston, Massachusetts 02110

  • Geary S. Mizuno, Esq.

Judge Elizabeth B. Johnson Office of Executive Legal Oak Ridge National Laboratory Director P. O. Box X, Building 3500 U. s. Nuclear Regulatory Oak Ridge, Tennessee 37830 Commission Maryland National Bank Bldg.

Dr. Kenneth A. McCollom  ;

- Room 10705 1107 West Knapp Street 7735 Old Georgetown Road Stillwater, Oklahoma 74075 Bethesda, Maryland 20814 l

Dr. Walter H. Jordan Chairman, Atomic Safety and Licensing 881 W. Outer Drive Board Panel l, Oak Ridge, Tennessee 37830 U. S. Nuclear Regulatory Commission 1 Washington, D. C. 20555 1

- - _ - _ - _ _ - - - _ _ - _ _ - - _ - - - - _ _ - - _ - _ - - - _ _ _ _ _ _u

g 4o" Chairman Renea Hicks, Esq.

Atomic Safety and Licensing Appeal Assistant Attorney General Board Panel Environmental Protection Division U. S. Nuclear Regulatory Commission Supreme Court Building Washington, D. C. 20555 Austin, Texas 78711 Mr. Robert Martin Anthony Z. Roisman, Esq.

Regional Administrator, Region IV 1401 New York Ave., N.W., Suite 600 U. S. Nuclear Regulatory Commission Washington, D. C. 20005 611 kyan Plaza Dr., Suite 1000 Arlington, Texas 76011 Mr. Herman Alderman Lanny A. Sinkin Staff Engineer Christic Institute Advisory Committee for Reactor 1324 North Capitol Street Safeguards (MS H-1016)

Washington, D. C. 20002 U. S. Nuclear Regulatory Commission Washington, D. C. 20555 Dr. David H. Bolt:

2012 S. Polk Dallas, Texas 75224 Robert A. Woold ridge , Esq.

Worsham, Forsythe, Sampels William Counsil, Vice President & Wooldridge Texas Utilities Generating Company 2001 Bryan Tower, suite 3200 Skyway Tower Dallas, Texas 75201 400 North Olive St., L.B. 81 Dallas, Texas 75201 Robert A. Jablon, Esq.

Spiegel & McDiarmid Docketing and Service Section 1350 New York Avenue, N.W.

(3 copies) Washington, D. C. 20005-4798 Office of the Secretary U. S. Nuclear Ecgulatory Commission Ms. Nancy H. Williams Washington, D. C. 20535 Project Manager Cygna Energy Services  ;

Ms. Billie P. Garde 2121 N. California Blvd., Suite 390 f Government Accountability Project Walnut Creek, California 94596 ]

Midwest Office l 104 E. Wisconsin - B William H. Burchette, Esq. i I

Appleton, Wisconsin 54911-4697 Heron, Burchette, Ruckert & Rothwell 1025 Thomas Jefferson Street, N.W.,

Mr. Christopher 1. Grimes, Suite 700 Director, Comanche Peak Washington, D. C. 20007 Project Division, Office of Special Projects James R. Bailey l Mail Stop EWW 302 P. O. Box 7000 U. S. Nuclear Regulatory Commission Bryan, Texas 77805 Washington, D. C. 20555 i I//a-at dt) W  !

f(Mis.) Juanita Ellis, President p

tetASE (Citizens Association for Sound Energy) i 1426 S. Polk Dallas, Texas 75224 i i 214/946-9446 l l

2 l

. _ _ _ _ _ _ _ _ _