ML17089A131: Difference between revisions
StriderTol (talk | contribs) (Created page by program invented by StriderTol) |
StriderTol (talk | contribs) (Created page by program invented by StriderTol) |
||
Line 17: | Line 17: | ||
=Text= | =Text= | ||
{{#Wiki_filter:From: To: DeSalvo. | {{#Wiki_filter:From: To: DeSalvo. Andrew FOIA Resource CASE NO: 2017-0416 DATE REC'D: 03/20/2017 SPECIALIST: | ||
Andrew FOIA Resource CASE NO: 2017-0416 DATE REC'D: 03/20/2017 SPECIALIST: | |||
RELATED CASE: | RELATED CASE: | ||
==Subject:== | ==Subject:== | ||
[External_Sender] | |||
[External_Sender] | |||
FOIA REQUEST; Assigning Severity level (Level I, II, III, or IV; and, green, white, yellow, or red) for TPN UHS NOED and O*ONOP-.011.1, in 2014. Oate: Friday, March 17, 2017 1:55:18 PM Attachments: | FOIA REQUEST; Assigning Severity level (Level I, II, III, or IV; and, green, white, yellow, or red) for TPN UHS NOED and O*ONOP-.011.1, in 2014. Oate: Friday, March 17, 2017 1:55:18 PM Attachments: | ||
Rnal Resoonse.pdf Andrew DeSalvo (b) (6) March 17, 2017 Freedom ofinfonnation, Privacy & Information Collections Branch Customei* | Rnal Resoonse.pdf Andrew DeSalvo (b) (6) March 17, 2017 Freedom ofinfonnation, Privacy & Information Collections Branch Customei* | ||
Line 31: | Line 29: | ||
==SUBJECT:== | ==SUBJECT:== | ||
Freedom oflnformation Act Request; As.'ligued Severity Level (Level I, II, III. or IV; and, green, white, yellow, or red) for TPN UHS NOED and O-ONOP-.011. | Freedom oflnformation Act Request; As.'ligued Severity Level (Level I, II, III. or IV; and, green, white, yellow, or red) for TPN UHS NOED and O-ONOP-.011. | ||
: l. in 2014. To whom it may concem: I would like to make a Freedom ofinfonnation Act Request: | : l. in 2014. To whom it may concem: I would like to make a Freedom ofinfonnation Act Request: DESCRIPTION OF THE REQUESTED RECORDS: Region II Enforcement and Investigations Assigned Severity Level (Severity Level I, II, III, or IV: and, green. white, yellow, or red) for pm-poses of detennining the potential radiological or other hazards associated with continued operation. | ||
DESCRIPTION OF THE REQUESTED RECORDS: | for Tm*key Point Nuclear Reactor 3 & 4 Action for Teclmical Specification (TS) 3. 7.4, ultimate Heat Sink (l!'fIS) Notice of Enforcement Discretion (NOED) which increased tlie ultimate heat sink temperature from 100 degrees F to 103 degrees F and prevented the shutdown ofboth units: and, O-ONOP-.011.l (Intake Canal Low Level Jr High Temperature) entered 22 times prior to the event" in the year 2014 Yoms sincerely. | ||
Region II Enforcement and Investigations Assigned Severity Level (Severity Level I, II, III, or IV: and, green. white, yellow, or red) for pm-poses of detennining the potential radiological or other hazards associated with continued operation. | |||
for Tm*key Point Nuclear Reactor 3 & 4 Action for Teclmical Specification (TS) 3. 7.4, ultimate Heat Sink (l!'fIS) | |||
Notice of Enforcement Discretion (NOED) which increased tlie ultimate heat sink temperature from 100 degrees F to 103 degrees F and prevented the shutdown ofboth units: and, O-ONOP-.011.l (Intake Canal Low Level Jr High Temperature) entered 22 times prior to the event" in the year 2014 Yoms sincerely. | |||
ANDREW DeSAL VO (b) (6) l Attachments 32KB PDF Final Response.pdf 32KB enclosure CITE NRC Enforcement Policy (SRM-15-0163). | ANDREW DeSAL VO (b) (6) l Attachments 32KB PDF Final Response.pdf 32KB enclosure CITE NRC Enforcement Policy (SRM-15-0163). | ||
ML16271A446 11/07/2016 01:33 PM EST 11/01/2016 486.06 Kb See Attachments PDFML16271A446.pdf488KB REFERENCE Severity level designations reflect different degrees of significance depending on the activity area in which the severity level is designated. | ML16271A446 11/07/2016 01:33 PM EST 11/01/2016 486.06 Kb See Attachments PDFML16271A446.pdf488KB REFERENCE Severity level designations reflect different degrees of significance depending on the activity area in which the severity level is designated. | ||
Line 43: | Line 37: | ||
: a. SL I violations are those that resulted in or could have resulted in serious safety or security consequences (e.g., violations that created the substantial potential for serious safety or security consequences or violations that involved systems failing when actually called on to prevent or mitigate a serious safety or security event). b. SL II violations are those that resulted in or could have resulted in significant safety or security consequences (e.g., violations that created the potential for substantial safety or security consequences or violations that involved systems not being capable, for an extended period, of preventing or mitigating a serious safety or security event). c. SL III violations are those that resulted in or could have resulted in moderate safety or security consequences (e.g., violations that created a potential for moderate safety or security consequences or violations that involved systems not being capable, for a relatively short period, of preventing or mitigating a serious safety or security event). NRC Enforcement Policy 12 d. SL IV violations are those that are less serious, but are of more than minor concern, that resulted in no or relatively inappreciable potential safety or security consequences (e.g., violations that created the potential of more than minor safety or security consequences). | : a. SL I violations are those that resulted in or could have resulted in serious safety or security consequences (e.g., violations that created the substantial potential for serious safety or security consequences or violations that involved systems failing when actually called on to prevent or mitigate a serious safety or security event). b. SL II violations are those that resulted in or could have resulted in significant safety or security consequences (e.g., violations that created the potential for substantial safety or security consequences or violations that involved systems not being capable, for an extended period, of preventing or mitigating a serious safety or security event). c. SL III violations are those that resulted in or could have resulted in moderate safety or security consequences (e.g., violations that created a potential for moderate safety or security consequences or violations that involved systems not being capable, for a relatively short period, of preventing or mitigating a serious safety or security event). NRC Enforcement Policy 12 d. SL IV violations are those that are less serious, but are of more than minor concern, that resulted in no or relatively inappreciable potential safety or security consequences (e.g., violations that created the potential of more than minor safety or security consequences). | ||
: e. Minor Violations are those that are less significant than a SL IV violation. | : e. Minor Violations are those that are less significant than a SL IV violation. | ||
Minor violations do not warrant enforcement action and are not normally documented in inspection reports. | Minor violations do not warrant enforcement action and are not normally documented in inspection reports. However, minor violations must be corrected. | ||
copyright 2017 Andrew DeSalvo Ownership and Intellectual Property: | copyright 2017 Andrew DeSalvo Ownership and Intellectual Property: | ||
The OWNER and cited sources retain all right, title, and interest in and to all of the copyrights, database rights, patent rights, trademarks, trade secrets, and all other propriety right in the CONTENT. | The OWNER and cited sources retain all right, title, and interest in and to all of the copyrights, database rights, patent rights, trademarks, trade secrets, and all other propriety right in the CONTENT. No rights are granted to the CONTENT. Any right, title or interest arising in any compilation or derivative work created using any CONTENT shall not entitle the RECIPIENT to use any CONTENT. The RECIPIENT does not acquire any copyright ownership or equivalent rights in, or to, any CONTENT or any other property of the OWNER or sources of CONTENT. Confidentiality Statement: | ||
No rights are granted to the CONTENT. | This electronic message, and any attachment, contains privileged and confidential information from Andrew J. DeSalvo, intended for the use of the individual or entity named above. If you are not the intended RECIPIENT, immediately and permanently delete the message and any attachment from your system. Disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. | ||
Any right, title or interest arising in any compilation or derivative work created using any CONTENT shall not entitle the RECIPIENT to use any CONTENT. | |||
The RECIPIENT does not acquire any copyright ownership or equivalent rights in, or to, any CONTENT or any other property of the OWNER or sources of CONTENT. | |||
Confidentiality Statement: | |||
This electronic | |||
If you have received this email in error, please notify promptly by telephone at (b) (6) or by email reply. ---On Fri, 3/17117, Admin, Admin <foia resource@nrc.gov> | If you have received this email in error, please notify promptly by telephone at (b) (6) or by email reply. ---On Fri, 3/17117, Admin, Admin <foia resource@nrc.gov> | ||
wrote: > From: Adrnin, Admin <foia.resource@nrc.gov> | wrote: > From: Adrnin, Admin <foia.resource@nrc.gov> | ||
Line 60: | Line 47: | ||
==Subject:== | ==Subject:== | ||
FOIA/PA-2017-0122A Final Appeal Response | FOIA/PA-2017-0122A Final Appeal Response >To: (b) (6) > Cc: Scott.Britt@nrc.gov | ||
>To: (b) (6) > Cc: Scott.Britt@nrc.gov | |||
>Date: Friday, March 17, 2017, 1:37 PM > | >Date: Friday, March 17, 2017, 1:37 PM > | ||
==Dear Mr. DeSalvo:== | ==Dear Mr. DeSalvo:== | ||
>Please find attached NRC's final response to your FOIA >request, FOIA/P A-2017-00122A. | |||
>Please find attached NRC's final response to your FOIA >request, FOIA/P A-2017-00122A. | > Please take a moment to help us improve our FOIA processes, > and let us know what your experience has been. Just click > on this embedded link: http"Uwww nrc goy/reading-rm/foia/foia-user-suryey html. > Once you have completed the survey, just dick the > "SUBMIT" button and your survey response will be > returned to us. > > > >Thank you, > Freedom oflnformation, Privacy & Information Collections | ||
> Please take a moment to help us improve our FOIA processes, | |||
> and let us know what your experience has been. Just click > on this embedded link: http"Uwww nrc goy/reading-rm/foia/foia-user-suryey html. > Once you have completed the survey, just dick the > "SUBMIT" button and your survey response will be > returned to us. > > > >Thank you, > Freedom oflnformation, Privacy & Information Collections | |||
>Branch > >Customer Service Division, Office of the Chieflnformation | >Branch > >Customer Service Division, Office of the Chieflnformation | ||
>Officer | >Officer > > Mail Stop: T-5F09 > >U.S. Nuclear Regulatory Commission | ||
> > Mail Stop: T-5F09 > >U.S. Nuclear Regulatory Commission | |||
> >Washington, D.C. 20555-0001 | > >Washington, D.C. 20555-0001 | ||
> FOIA.Resource@nrc.gov | > FOIA.Resource@nrc.gov | ||
>Ph: 301-415-7169 Fax: 301-415-5130}} | >Ph: 301-415-7169 Fax: 301-415-5130}} |
Revision as of 23:29, 7 July 2018
ML17089A131 | |
Person / Time | |
---|---|
Site: | Turkey Point ![]() |
Issue date: | 03/17/2017 |
From: | DeSalvo A - No Known Affiliation |
To: | NRC/OCIO |
Shared Package | |
ML17089A119 | List: |
References | |
FOIA/PA-2017-0416 | |
Download: ML17089A131 (3) | |
Text
From: To: DeSalvo. Andrew FOIA Resource CASE NO: 2017-0416 DATE REC'D: 03/20/2017 SPECIALIST:
RELATED CASE:
Subject:
[External_Sender]
FOIA REQUEST; Assigning Severity level (Level I, II, III, or IV; and, green, white, yellow, or red) for TPN UHS NOED and O*ONOP-.011.1, in 2014. Oate: Friday, March 17, 2017 1:55:18 PM Attachments:
Rnal Resoonse.pdf Andrew DeSalvo (b) (6) March 17, 2017 Freedom ofinfonnation, Privacy & Information Collections Branch Customei*
Ser.ice Division.
Office of the Chieflnfonuation Officer Mail Stop: T-5F09 U.S. Nuclear Regulatory Commission Washington.
D.C. 10555-0001 FOIA.Resom*ce@mc.gov Ph: 301-415-7169 Fax: 301-415-5130
SUBJECT:
Freedom oflnformation Act Request; As.'ligued Severity Level (Level I, II, III. or IV; and, green, white, yellow, or red) for TPN UHS NOED and O-ONOP-.011.
- l. in 2014. To whom it may concem: I would like to make a Freedom ofinfonnation Act Request: DESCRIPTION OF THE REQUESTED RECORDS: Region II Enforcement and Investigations Assigned Severity Level (Severity Level I, II, III, or IV: and, green. white, yellow, or red) for pm-poses of detennining the potential radiological or other hazards associated with continued operation.
for Tm*key Point Nuclear Reactor 3 & 4 Action for Teclmical Specification (TS) 3. 7.4, ultimate Heat Sink (l!'fIS) Notice of Enforcement Discretion (NOED) which increased tlie ultimate heat sink temperature from 100 degrees F to 103 degrees F and prevented the shutdown ofboth units: and, O-ONOP-.011.l (Intake Canal Low Level Jr High Temperature) entered 22 times prior to the event" in the year 2014 Yoms sincerely.
ANDREW DeSAL VO (b) (6) l Attachments 32KB PDF Final Response.pdf 32KB enclosure CITE NRC Enforcement Policy (SRM-15-0163).
ML16271A446 11/07/2016 01:33 PM EST 11/01/2016 486.06 Kb See Attachments PDFML16271A446.pdf488KB REFERENCE Severity level designations reflect different degrees of significance depending on the activity area in which the severity level is designated.
For example, the imme.diacy of any hazard to the public associated with SL I in reactor operations is not directly comparable to that associated with SL I violations in facility construction.
- a. SL I violations are those that resulted in or could have resulted in serious safety or security consequences (e.g., violations that created the substantial potential for serious safety or security consequences or violations that involved systems failing when actually called on to prevent or mitigate a serious safety or security event). b. SL II violations are those that resulted in or could have resulted in significant safety or security consequences (e.g., violations that created the potential for substantial safety or security consequences or violations that involved systems not being capable, for an extended period, of preventing or mitigating a serious safety or security event). c. SL III violations are those that resulted in or could have resulted in moderate safety or security consequences (e.g., violations that created a potential for moderate safety or security consequences or violations that involved systems not being capable, for a relatively short period, of preventing or mitigating a serious safety or security event). NRC Enforcement Policy 12 d. SL IV violations are those that are less serious, but are of more than minor concern, that resulted in no or relatively inappreciable potential safety or security consequences (e.g., violations that created the potential of more than minor safety or security consequences).
- e. Minor Violations are those that are less significant than a SL IV violation.
Minor violations do not warrant enforcement action and are not normally documented in inspection reports. However, minor violations must be corrected.
copyright 2017 Andrew DeSalvo Ownership and Intellectual Property:
The OWNER and cited sources retain all right, title, and interest in and to all of the copyrights, database rights, patent rights, trademarks, trade secrets, and all other propriety right in the CONTENT. No rights are granted to the CONTENT. Any right, title or interest arising in any compilation or derivative work created using any CONTENT shall not entitle the RECIPIENT to use any CONTENT. The RECIPIENT does not acquire any copyright ownership or equivalent rights in, or to, any CONTENT or any other property of the OWNER or sources of CONTENT. Confidentiality Statement:
This electronic message, and any attachment, contains privileged and confidential information from Andrew J. DeSalvo, intended for the use of the individual or entity named above. If you are not the intended RECIPIENT, immediately and permanently delete the message and any attachment from your system. Disclosure, copying, distribution, or use of the contents of this message is strictly prohibited.
If you have received this email in error, please notify promptly by telephone at (b) (6) or by email reply. ---On Fri, 3/17117, Admin, Admin <foia resource@nrc.gov>
wrote: > From: Adrnin, Admin <foia.resource@nrc.gov>
>
Subject:
FOIA/PA-2017-0122A Final Appeal Response >To: (b) (6) > Cc: Scott.Britt@nrc.gov
>Date: Friday, March 17, 2017, 1:37 PM >
Dear Mr. DeSalvo:
>Please find attached NRC's final response to your FOIA >request, FOIA/P A-2017-00122A.
> Please take a moment to help us improve our FOIA processes, > and let us know what your experience has been. Just click > on this embedded link: http"Uwww nrc goy/reading-rm/foia/foia-user-suryey html. > Once you have completed the survey, just dick the > "SUBMIT" button and your survey response will be > returned to us. > > > >Thank you, > Freedom oflnformation, Privacy & Information Collections
>Branch > >Customer Service Division, Office of the Chieflnformation
>Officer > > Mail Stop: T-5F09 > >U.S. Nuclear Regulatory Commission
> >Washington, D.C. 20555-0001
> FOIA.Resource@nrc.gov
>Ph: 301-415-7169 Fax: 301-415-5130