ML20235S021
| ML20235S021 | |
| Person / Time | |
|---|---|
| Issue date: | 08/14/1987 |
| From: | Mike Williams NRC OFFICE FOR ANALYSIS & EVALUATION OF OPERATIONAL DATA (AEOD) |
| To: | Mauck J Office of Nuclear Reactor Regulation |
| References | |
| NUDOCS 8710080277 | |
| Download: ML20235S021 (3) | |
Text
-.
AUG l i 16 l
MEMORANDUM FOR: Jerry L. Mauck, Acting Chief Instrumentation and Control System Branch j
Division of Engineering and Systems Technology, NRR FROM:
Mark H. Williams, Chief Trends and Patterns Analysis Branch Division of Safety Programs, AE0D
SUBJECT:
NPRDS INSTRUMENTATION REPORTING REQUIREMENTS AND I
IDENTIFIER CODES
REFERENCES:
- 1. Memorandum, J. L. Mauck to M. H. Williams, " Review Request of Combustion Engineering NPRDS Instrumentation Scoping Guidance Model," July 21, 1987.
- 2. Memorandum, M. H. Williams to D. F. Sullivan and i
J. L. Mauck, " Combustion Engineering NPRDS Instrumentation Scoping Guidance," June 11, 1987.
Thank you for your response (Ref.1) to our request (Ref. 2) to review INP0's proposed CE instrumentation scoping guidance for NPRDS reportable instruments-tion ccmponent failures. You indicated that the proposed CE instrumentation guidance did not provide code identifiers for subcomponents that are part of the interconnections between components of a measuring system (e.g., cables, connectors, terminal blocks, and limit switches).
For your information, we have attached information regarding other guidance that pr tently exists in the NPRDS Reporting Procedure Manual that provides code identifiers and reporting l
requirements for these subcomponent types.
j We hope that the enclosed information resolves your request as to the appropriate code identifiers and document from which these code i
identifiers can be obtained.
If you have any questions, please contact l
G.L. Plumlee III at x24492.
h Mark H. Williams, Chief Trends and Patterns Analysis Branch Division of Safety Programs, AE0D
Enclosure:
As stated cc:
D. Sullivan Distribution:
J. Vora TPAB RF/CF A. Thadani GLPlumlee V. Thomas RLDennig R. Simard, INP0 MWilliams PDR
- See previous concurrence OFC :TPAB
- TPAB
- C/TPA NAME :GLPlumlee:rw:RLDennig*
- MWill s
____.:...___......:.....______.:...d.
DATE :8/// /87
- 8///87
- 8/ D/8 OFFICIAL RECORD COPY 8710080277 870814 PDR TOPRP ENVC-E C
......... J
gog 14 ifM1-MEMORANDUM FOR: Jerry L. Mauck, Acting Chief Instrumentation and Control System Branch Division of Engineering and Systems Technology, NRR FROM:
Mark H. Williams, Chief Trends and Patterns Analysis Branch Division of Safety Programs, AE00
SUBJECT:
NPRDS INSTRUMENTATION REPORTICG REQUIREMENTS AND IDENTIFIER CODES
REFERENCES:
- 1. Memorandum, J. L. Mauck to M. H. Williams, " Review Request of Combustion Engineering NPRDS Instrumentation Scoping Guidance Model," July 21, 1987.
- 2. Memorandum, M. H. Williams to D. F. Sullivan and J. L. Mauck, " Combustion Engineering NPRDS Instrumentation Scoping Guidance," June 11, 1987.
We have received your response (Ref. 1) to our request (Ref. 2) to review INP0's proposed CE instrumentation scoping guidance for NPRDS reportable instrumentation component failures.
You indicated that the proposed CE instru-mentation guidance did not provide code identifiers for subcesponents that are part of the interconnections between components of a measuring system (e.g.,
cables, connectors, terminal blocks, and limit switches). As indicated in the Enclosure, other guidance presently exists in the NPRDS Reporting Procedure Manual that provides code identifiers and reporting requirements for these sub_
component types.
We hope that the enclosed information resolves your request as to the appropriate code identifiers and document from which these code identifiers can be obtained.
If you have any questions, please contact G.L. Plumlee III at x24492.
Mark H. Williams, Chief Trends and Patterns Analysis Branch Division of Safety Programs, AEOD
Enclosure:
As stated cc:
D. Sullivan Distribution:
J. Vera TPAB RF/CF A. Thadani GLPlumlee V. Thomas RLDennig R. Simard, INP0 MWilliams PDR A /)fi 0FC :TPAB
.V' 'TQD
- C/TPAB
.....:...........:...f,[...)....:............:............:............:............:.....__....
NAME :GLPlumlee:rw:Rb0ennig
- MWilliams DATE:8/f/87
- 8/h/87
- 8/ /87 0FFICIAL RECORD COPY
,m I
i ENCLOSURE NPRDS REPORTING OF CERTAIN INSTRUMENTATION SUBCOMPONENTS 1
1 l
1.
Cables -
- a. Normally reported under the engineering code ELECON = Electrical Conductors consisting of the following types:
A - Bus B - Control Cable l
C - Power Cable l
D - Signal Cable E - Thermocouple Extension Wire X - Other
- b. Engineering reports are only required to be submitted upon component failure, therefore, the NPRDS data base will not contain an engineering data record of all such components.
- c. Two failure reports may be submitted:
- 1) One failure report for the component affected by(the cable failure, with a cause code of J = Other Devices a failure attributable to a failure or misoperation of another component orsystem),and
- 2) Another report for the failed cable (ELECON).
2.
Connectors -
- a. Reporting method is a judgement call.
- 1) The connector may either be reported as part of me panel (mostly reported as part of the panel, i.e., the component it is coming from) or as part of the cable, e.g., failure of the cable (ELECON) was reported with a cause of J = Other Devices, or
- 2) It may be reported under the engineering code ELECON as a type A = Other Type electrical conductor.
- b. Engineering reports for connectors are also required to be reported to the NPRDS only upon component failure.
3.
Terminal Blocks -
- a. Should be reported as a failure of the component it came from with a cause code of J = Other Devices.
4.
Limit Switches -
- a. Limit switches (e.g., valve position limit switches) used for position indication only are not required to be reported to the NPRDS.
- b. However, switches that provide a control function (e.g., bistables, 4
l mechanical or electronic) are reportable under the engineering code IBISSW = Instrumentation, Bistable / Switch.
- c. Some specific bistable switches and their respective code identifiers were provided in the proposed CE guidance.
i