ML20248B873
| ML20248B873 | |
| Person / Time | |
|---|---|
| Site: | Davis Besse  |
| Issue date: | 05/22/1998 |
| From: | Jeffery Wood CENTERIOR ENERGY |
| To: | NRC OFFICE OF INFORMATION RESOURCES MANAGEMENT (IRM) |
| References | |
| 2535, NUDOCS 9806020007 | |
| Download: ML20248B873 (13) | |
Text
'g.
=0
- 9" nE" Davis-Besse Nuclear Power Station E EE.
5501 North State Route 2 m
Oak Harbor Ohio 43449 9760 Jahrs K. Wood 419-249-2300 Vice President - Nuclear Fax:419-321-8337 Docket Number 50-346 License Number NPF-3 Serial Number 2535 May 22, 1998 Document Control Desk U. 3. Nuclear Regulatory Commission Washington, D. C. 20555-0001
Subject:
Y ar 2000 Readiness Issues Ladies and Gentlemen:
The Toledo Edison Company is the operator and a licensee of the Davis-Besse Nuclear Power Station (DBNPS) Unit Number 1. Toledo Edison is currently determining what impact the Year 2000 (Y2K) computer issues will have on the DBNPS. This determination is part of the DBNPS's Y2K program under the document NEI/NUSMG 97-07, " Nuclear Utility Year 2000 Readiness."
Toledo Edison has determined the NRC has supplied DBNPS either computer software or hardware with embedded software used to calculate the radiation dose rate of site personnel.
However, Toledo Edison can not determine if the software is Y2K ready or what impact can be expected if it is not Y2K ready. In order far Toledo Edison to accurately determine the impact of the Y2K issues relating to the DBNPS, please complete the attached forms and return them within 60 days of receipt to the addressee indicated on the forms.
Should you have any questions concerning this matter, please comact Mr. James L. Freels, Manager - Regulatory Affairs, at (419) 321-8466.
l Ve truly yours,
/
j uod
... v l
S/laj A00-(i cc: A. B. Beach, Regional Administrator, NRC Region III S. J. Campbell, NRC Region III, DB-1 Senior Resident Inspector A. G. Hansen, NRC/NRR Project Manager Utility Radiological Safety Board 9006020007 980522 PDR ADOCK 050003467 P
PDR i
_ ____ _a
,Page1of3 Vendor Y2K Assessment Privileged and Confidential Product Name:
SAbbE Mob 9-Software, current release version in use: \\/ l. O Hardware, Model Number:
Section A: Company GeneralInformation Responder's Name:
Phone Number:
Responder's Address:
Web Site: http: //
Contact Name (If different than Responder's):
Phone Number:
E-Mail Address:
Fax Number:
Section B: Year 2000 Readv?
- 1. To the best of your knowledge,is this product Year 2000 ready including leap year readiness?
O Yes O No la. If yes, please check basis for answer:
O No date/ time dependencies in product CCode analysis performed O 4-digit year is used (ccyy)
O Date encoding is used (Convert yy from decimal to hexadecimal, etc.)
O windowing technique is used (yy less than 50 means cc equals 20)
O Century indicator is used (I digit where 0 = cc of 19 and I = cc of 20)
O Product has been tested and is proven to be ieady (attached documentation including test plans and results and written confirmation of readiness.)
O oser:
Note: Ifyes, return allrequested documentation to addressee on bottom ofform. Ifno, continueprocessing assessmentform.
Ib. If no, do you have a solution to make the product Year 2000 ready?
O Yes Scheduled release number:
Scheduled release date of ready product:
Indicate what method will be used:
O 4-digit year (ccry)
D Date encoding O Date encoding is used (convert yy from decimal to hexadecimal, etc.)
O windowing technique is used (yy less than 50 means cc equals 20)
O Century indicator is used (I digit where 0 = cc of 19 and I = cc of 20)
O Other:
O No O No plan exists at this time O Patch available/being developed for limited readiness Scheduled release number:
Scheduled release date of patch product (mm/ccyy)
Page 2 of 3 Ib._(Continued)
O Replace existing product. No further support of this product is planned beyond 2000.
Recommended replacement:
Section C: Strateev/ Solution Identification for Year 2000 Readiness l
- 1. Will there be an additional charge for the upgrade?
O yes cost -
0 No O undecided
- 2. Willinstallation of the Y2K compliant release require upgrades to the operating environment?
O Yes O No
- 3. Willinstallation of the Y2K compliant release require modification to existing application?
O Yes O No O Don't Know If yes, conversion utility will be supplied O Yes O No 4.
Will the changes implemented in the Y2K compliant release have any performance impact?
O Yes O No O Don't know If yes, please describe:
Section D: Readiness Details / Checklist for Determining Year 2000 Readiness
- 1. Expected Fail Date?
O N/A When will the product be impacted by the year 2000 date field (mm/dd/ccyy)?
- 2. Does the product represent the year using 4 digits?
On Screens O Yes O No O Don't Know On Reports O Yes O No O Don't Know Within Programs O Yes O No O Don't Know Within Databases O Yes O No O Don't Know
- 3. Do date fields require expansion from 2 digits to 4 digits?
On Screens O Yes O No O Don't Know On Reports O Yes O No O Don't Know Within Programs O Yes O No O Don't Know Within Databases O Yes O No O Don't Know
- 4. Does this product perform date calculations? O Yes O No O Don't Know If yes, please describe:
- 5. Does this product perform logical ordering / sequencing of dates? O Ves O No O Don't Know If yes, please describe:
- 6. Does this product have date fields or date-related variables in the programming code?
O Yes O No O Don't Know If yes, please describe:
, P:g; 3 of 3
- 7. Does the product's files / databases contain 1-or 2-byte indicators to indicate the century?
O Yes O No O Don't Know If yes, please describe:
)
l l
i
- 8. Are there identifier fields that use dates embedded within the field?
j (e.g. Policy Number X3700121096) O Yes O No O Don't Know If yes, please describe:
j
- 9. Are there hard-coded dates (e.g. 99,01,19) within the product?
(e.g. product uses 19 as century and /or 99 as an end-of. file indicator).
O Yes O No O Don't Know if yes, please describe:
- 10. Does the product use the computer operating system date wit'ain calculations or comparisons?
)
O Yes O No O Don't Know
- 11. Does the product use common date routines? O Yes O No O Don't Know
- 12. Does the product currently process dates beyond the Year 200?
O Yes O No O Don't Know
- 13. Does this product interface with other vendors' products? O Yes O No 13a. lf yes, what are they and has e the interfaces been tested?
Product:
Tested: 0 Yes O No Product:
Tested: 0 Yes O No Product:
Tested: 0 Yes O No Product:
Tested: 0 Yes O No RETURN COMPLETED FORMS AND ALL DOCUMENTATION TO:
Karen Dunn Davis-Besse Nuclear Power Station Mail Stop 3105 5501 North State Route 2 Oak Harbor, Ohio 43449 l
I
Page1of3 Vendor Y2K Assessment Privileged and Confidential Product Name:
$bDN Software, current release version in use:
Y I.O Hardware, Model Number:
l Section A: CompanV GeneralInformation Responder's Name:
Phone Number:
Responder's Address:
Web Site: http: //
Contact Name (If different than Responder's):
Phone Number:
E-Mail Address:
Fax Number:
Section B: Year 2000 Ready?
- 1. To the best of your knowledge,is this produc' Year 2000 ready including leap year readiness?
O Yes O No
- a. If yes, please check basis for answer:
O No date/ time dependencies in product Ocode analysis perrormed O 4-disit ye2r is used (ccyy)
O Date encodina ls used (convert yy from decimal to hexadecimal, etc.)
)
O Windowing technique is used (yy less than 50 means cc equals 20) j O century indicator is used (I digit where 0 - cc of 19 and 1 - cc of 20)
O Product has been tested and is proven to be ready (attached documentation includine test plans and results and written confirmation of readiness.)
O Other:
Note: Ifyes, return all requested documentation to addressee on bottom ofform. Ifno, continurprocessing assessmentform.
Ib. If no, do you have a solution to make the product Year 2000 ready?
O Yea Scheduled release number:
Scheduled release date of ready product:
Indicate what method will be used:
O 4-digit year (ccyy>
0 Dateencoding O Date encoding is used (convert yy from decimal to hexadecimal, etc.)
O Windowing technique is used (yy less than 50 means cc equals 20) 1:
O ces.tury indicator is used (I digit where 0 = cc of 19 and 1 - cc of 20) i O Other:
i O No O No plan exists at this time O Patch available/being developed for limited readiness Scheduled release number:
Scheduled release date of patch product (mm/ccyy)
Page 2 0f 3 Ib. (Continued)
O Replace existing product. No further support of this product is planned beyond 2000.
Recommended replacement:
Section C: Strateev/ Solution Identification for Year 2000 Readiness
- 1. Will there be an additional charge for the upgrade?
O Yes cost -
0 No O undecided
- 2. Willinstallation of the Y2K compliant refer.se require upgrades to the operating environment?
O Yes O No
- 3. Willinstallation of the Y2K compliant release require modification to existing application?
O Yes O No O Don't Know if yes, conversion utility will be supplied O Yes O No 4.
Will the changes implemented in the Y2K compliant release have any performance impact?
O Yes O No O Don't know if yes, please describe:
Section D: Readiness Details / Checklist for Determining Year 2000 Readiness
- 1. Expected Fall Date?
O N/A When will the product be impacted by the year 2000 date field (mm/dd/ccyy)?
- 2. Does the product represent the year using 4 digits?
On Screens O Yes O No O Don't Know On Reports O Yes O No O Don't Know Within Programs O Yes O No O Don't Know Within Databases O Yes O No O Don't Kno v
- 3. Do date fields require expansion from 2 digits to 4 digits?
On Screens O Yes O No O Don't Know On Reports O Yes O No O Don't Know Within Programs O Yes O No O Don't Know Within Databases O Yes O No O Don't Know
- 4. Does this product perform date calculations? O Yes O No O Don't Know l
If yes, please describe:
l
- 5. Does this product performlogical ordering / sequencing of dates? O Yes O No O Don't Know If yes, please describe:
- 6. Does this product have date fields or date-related variables in the programming code?
O Yes O No O Don't Know If yes, please describe:
l
Page 3 of 3
- 7. Does the product's files / databases contain 1-or 2-byte indicators to indicate the century?
O Yes O No O Don't Know If yes, please describe:
- 8. Are there identifier fields that use dates embedded within the field?
(e.g. Policy Number X3700121096) O Yes O No O Don't Know if yes, please describe:
- 9. Are there hard-coded dates (e.g. 99,01,19) within the product?
(e.g. product uses 19 as century and /or 99 as an end-of file indicator).
O Yes O No O Don't Know if yes, please describe:
- 10. Does the product use the computer operating system date within calculations or comparisons?
O Yes O No O Don't Know
- 11. Does the product use common date routines? O Yes O No O Don't Know
- 12. Does the product currently process dates beyond the Year 200?
O Yes O No O Don't Know
- 13. Does this product interface with other vendors' products? O Yes O No 13a. lf yes, what are they and have the interfaces been tested?
Product:
Tested: 0 Yes O No Product:
Tested: 0 Yes O No Product:
l Tested: 0 Yes O No Product:
Tested: 0 Yes O Na RETURN COMPLETED FORMS AND ALL DOCUMENTATION TO:
Karen Dunn Davis-Besse Nuclear Power Station Mail Stop 3105
.5501 North State Route 2 Oak Harbor, Ohio 43449 I
l l
P ge1 of3 Vendor Y2K Assessment Privileged and Confidential
\\/AR5Ktd Product Name:
Software, current release version in use:
V t.O Hardware, Model Number:
MN Section A: Company GeneralInformation Responder's Name:
Phone Number:
Responder's Address:
Web Site: http: //
Contact Name (If different than Responder's):
Phone Number:
E-Mail Address:
Fax Number:
Section B: Year 2000 Ready?
- 1. To the best of your knowledge,is this product Year 2000 ready including leap year readiness?
O Yes O No la. If yes, please check basis for answer:
O No date/ time dependencies in product DCode an iysis performed O 4-digit year is used (ccyy)
O Date encoding is used (Convert yy from decimal to hexadecimal, etc.)
O Windowing technique is used (yy less than 50 means cc equals 20)
O Century indicator is used (I digit where 0 = cc of 19 and 1 = cc of 20)
O Product has been tested and is proven to be ready (attached documentation including test plans and results and written confirmation of readiness.)
O other:
Note: Ifyes, return allrequested documentation to addressee on bottom ofform. Ifno, continueprocessing assessmentform.
Ib. If no, do you have a solution to make the product Year 2000 ready?
O Yes Scheduled release number:
Scheduled release date of ready product:
Indicate what method will be used:
O 4-digit year (ccyy)
D Dateencoding O Date encoding is used (Convert yy from decimal to hexadecimal, etc.)
t O Windowing technique is used (yy less than S0 means cc equals 20)
O Century indicator is used (1 digit where 0 = cc of 19 and I = cc of 20)
O Other:
O No O No plan exists at this time O Patch available/being developed for limited readiness Scheduled release number:
Scheduled release date of patch product (mm/cc)7)
Page 2 of 3 Ib.(Continued)
O Replace existing product. No further support of this product is planned beyond 2000.
Recommended replacement:
Section C: Strateev/ Solution Identification for Year 2000 Readiness
- 1. Will there be an additional charge for the upgrade?
O Yes cost -
0 No O underided
- 2. Willinstallation of the Y2K compliant release require upgrades to the operating environment?
O Yes O No
- 3. Willinstallation of the Y2K compliant release require modification to existing application?
O Yes O No O Don't Know If yes, conversion utility will be supplied O Yes O No 4.
Will the changes implemented in the Y2K compliant release have any performance impact?
O Yes O No O Don't know If yes, please describe:
Section D: Readiness Details / Checklist for Determining Year 2000 Readiness
- 1. Expected Fall Date?
O N/A When will the product be impacted by the year 2000 date field (mm/dd/ccyy)?
- 2. Does the product represent the year using 4 digits?
On Screens O Yes O No O Don't Know On Reports O Yes O No O Don't Know Within Programs O Yes O No O Don't Know Within Databases O Yes O No O Don't Know
- 3. Do date fields require expansion from 2 digits to 4 digits?
On Screens O Yes O No O Don't Know On Reports O Yes O No O Don't Know Within Programs O Yes O No O Don't Know Within Databases O Yes O No O Don't Know
- 4. Does this product perform date calculations? O Yes O No O Don't Know If yes, please describe:
- 5. Does this product performlogical ordering / sequencing of dates? O Yes O No O Don't Know If yes, please dercribe:
- 6. Does this product have date fields or date-related variables in the programming code?
O Yes O No O Don't Know If yes, please describe:
Pege 3 of 3
- 7. Does the product's files / databases contain 1-or 2-byte indicators to indicate the century?
O Yes O No O Don't Know If yes, please describe:
- 8. Are there identifier fields that use dates embedded within the field?
(e.g. Policy Number X3700121096) O Yes O No O Don't Know If yes, please describe:
- 9. Are there hard-coded dates (e.g. 99,01,19) within the product?
(e.g. product uses 19 as century and /or 99 as an end-of-file indicator).
O Yes O No O Don't Know If yes, please describe:
- 10. Does the product use the computer operating system date within calculations or comparisons?
O Yes O No O Don't Know
- 11. Does the product use common date routines? O Yes O No O Don't Know
- 12. Does the product currently process dates beyond the Year 200?
' O Yes O No O Don't Know
- 13. Does this product interface with other vendors' products? O Yes O No 13a. If yes, what are they and have the interfaces been tested?
Product:
Tested: 0 Yes O No Product:
Tested: 0 Yes O No Product:
Tested: 0 Yes O No Product:
Tested: 0 Yes O No 1
l RETURN COMPLETED FORMS AND ALL DOCUMENTATION TO:
Karen Dunn i
Davis-Besse Nuclear Power Station 1
Mail Stop 3105 5501 North State Route 2 Oak Harbor, Ohio 43449 I
J Page1of3 Vendor Y2K Assessment j
Privileged and Confidential i
\\f bbbbb
- Mbb2, j
Product Name:
1 Software, current release version in use:
Y l,O Hardware, Model Number:
Mk l
l Section A: ComDa3v GeneralInformation
)
l I
(
Responder's Name:
Phone Number:
Responder's Address:
Web Site: http: //
i Contact Name (if different than Responder's):
j Phone Number:
E-Mail Address:
Fax Number:
l Section B: Year 2000 Ready?
l
- 1. To the best of your knowledge,is this product Year 2000 ready including leap year readiness?
O Yes O No i
la. If yes, please check basis for answer-0 No date/ time dependencies in product OCode anaiysis perrormed O 4-digit year is used (ccyy)
O Date encoding is used (Convert yy from decimal to hexadecimal, etc.)
O Windowing technique is used (yy less than 50 means cc equals 20)
O Century indicator is used (I digit where 0 = cc of 19 and 1 = cc of 20)
O Product has been tested and is proven to be ready (attached documentation including test plans and results and written confirmation of readiness.)
O Other:
Note: Ifyes, return all requested documentation to addressee on bottom ofform. Ifno, continueprocessing assessmentform.
Ib. If no, do you have a solution to make the product Year 2000 ready?
O Yes Scheduled release number:
Scheduled release date of ready product:
Indicate what method will be usedt O 4-disityear(ccry)
O Date encodias O Date encoding is used (Convert yy som decimal to hexadecimal, etc.)
O Windowing technique is used (yy less than 50 means cc equals 20) l-O Century indicator is used (1 digit where 0 = cc of 19 and 1 = cc of 20)
O Other:
O No.
O No plan exists at this time O Patch available/being develooed for limited readiness Scheduled release number:
Scheduled release date of patch product (mm/ccyy)
Page 2 of 3 1b. (Continued)
O Replace existing product. No further support of this product is planned beyond 2000.
Recommended replacement:
Section C: Strateev/ Solution Identification for Year 2000 Readiness
- 1. Will there be an additional charge for the upgrade?
O Yes Cost =
0 No O Undecided
- 2. Willinstallation of the Y2K compliant release require upgrades to the operating environment?
O Yes O No
- 3. Willinstallation of the Y2K compliact release require modification to existing application?
O Yes O No O Don't Know If yes, conversion utility will be supplied O Yes O No 4.
Will the changes implemented in the Y2K compliant release have any performance impact?
l 0 Yes O No O Don't know l
If yes, please describe:
l Section D: Readiness Details / Checklist for Determining Year 2000 Readiness
- 1. Expected Fall Date?
O N/A When will the product be impacted by the year 2000 date field (mm/dd/ccyy)?
- 2. Does the product represent the year using 4 digits?
On Screens O Yes O No O Don't Know On Reports O Yes O No O Don't Know Within Programs O Yes O No O Don't Know Within Databases O Yes O No O Don't Know
- 3. Do date fields require expansion from 2 digits to 4 digits?
On Screens O Yes O No O Don't Know On Reports O Yes O No O Don't Know Within Programs O Yes O No O Don't Know Within Databases O Yes O No O Don't Know
- 4. Does this product perform date calculations? O Yes O No O Don't Know If yes, please describe:
- 5. Does this product perform logical ordering / sequencing of dates? O Yes O No O Don't Know j
If yes, please describe:
i
- 6. Does this product have date fields or date-related variables in the programming code?
O Yes O No O Don't Know If yes, please describe:
P ge 3 of 3
- 7. Doei. the product's files / databases contain 1-or 2-byte indicators to indicate the century?
O Yes O No O Don't Know If yes, please describe:
- 8. Are there identifier fields that use dates embedded within the field?
(e.g. Policy Number X3700121090 0 Yes O No O Don't Know If yes, please describe:
- 9. Are there hard-coded dates (e.g. 99,01,19) within the product?
(e.g. product uses 19 as century and /or 99 as an end-of-file indicator).
O Yes O No O Don't Know if yes, please describe:
- 10. Does the product use me computer operating system date within calculations or comparisons?
O Yes O No O Don't Know
- 11. Does the product use common date routines? O Yes O No O Don't Know
- 12. Does the product currently process dates beyond the Year 200?
O Yes O No O Don't Know
- 13. Does this product interface with other vendors' products? O Yes O No 13a. If yes, what are they and have the interfaces been tested?
Product:
Tested: 0 Yes O No h oduct:
Tested: 0 Yes O No Product:
I Tested: O Yes O No Product:
Tested: O Yes O No i
l 1
RETURN COMPLETED FORMS AND ALL DOCUMENTATION TO:
I Karen Dunn Davis-Besse Nuclear Power Station Mail Stop 3105 5501 North State Route 2 Oak Harbor, Ohio 43449
(
l l
l 4
1.
]