ML20079L379

From kanterella
Jump to navigation Jump to search
Forwards Implementation Plan for Emergency Response Data Sys.Util Intends to Complete Implementation of Sys,Per Rev 1 to NUREG-1394,by 930213
ML20079L379
Person / Time
Site: Nine Mile Point  Constellation icon.png
Issue date: 10/28/1991
From: Terry C
NIAGARA MOHAWK POWER CORP.
To:
NRC OFFICE OF INFORMATION RESOURCES MANAGEMENT (IRM)
References
RTR-NUREG-1394 NMP1L-0620, NMP1L-620, NUDOCS 9111060243
Download: ML20079L379 (16)
v • d • e


Text

-__ _ _ __ _ _

1 '

RJ V NIAGARA W

, uMOHAWK NIAGARA MOHAWK POWER CORPORATION 301 PL AIN!IllD fK1AD fi1HACULI . td v Irt?/li l t h6NL ( 41M 4 /41! 11 October 28, 1991 NMPIL 0620 U. S. Nuclear Regulatory Commission Attn Document Control Desk washington, D. C. 20555 Re: Nine Mile Point Unit 1 Nine Mile Point Unit 2 Docket No. 50-220 Docket No. 50-410 DPR-63 _ .HPF-69 Gentlement

SUBJECT:

EMERGENCY RESPONSE DATA SYSTEM (ERDS)

The Nuclear Regulatory Commission (NRC) has amended its regulations to require licensees of all operating nuclear power facilities, except Big Rock Point, to participate in the Emergency Response Data System (ERDS) program. The amended regulation 6:, in part, require ea::h licensee to develop and submit an ERDS implementation program plan to the NRC by October 28, 1991. Attachments "A" and "B" to this letter provide the program plans for Nine Mile Point Unit 1 and Unit 2, respectively. Please note that attachments "A" and "B" represent a proposed program plan (and schedule) and the dates provided should not be construed as NRC commitments. Niagara Mohawk does intend to complete implementation of the ERDS by February 13, 1993.

Very truly yours, ph -

( ;l8Cd?

C. D. Terry Vice President Nuclear Engineering JMT/krc 001895GG Enclosures xc: Regional Administrator, Region I Mr. R. A' . Capra, Project Director, NRR Mr. D. S. Brinkman e Senior Project Manager, NRR Mr. W. L. Schmidt, Senior Resident Inspector Mr. D. R. Haverke'- Chief, Reactor Projects Section No. 1B Mi . J. E. Menning, roject Manager, NRR Records fianagement 'L

()r(9 9111060243 911020 I i

FDR ADOCK 00000220

-. F FDR { { ,

iau

$ 5?

?

bTTAGEMENT A tt dMLRGENCY 9ESPONSE DATA SYbTEM (ERDS) IMPLEMENTATION PLAN h ,

INTRODUC 'JN y,. i . .

I Ni g ,s Nine 'lile Point Unit 1 (NMP1) Emergency Response Data hg.4l,(' ~  ?

,, ' tem (Tc""' will be designed to provide near real time plant h{j# - "7 data to :nalmar Regulatory Commission (NRC). The ERDS gy .

, implemecas w plan is delineated in Sections 4.0 and 5.0 of

  1. 5 n w w th' s attach.aent. Sections 4.0 and 5.0 address each item

' identified in xUREG-13a4, Rev. 1, appendix A, "ERDS 1

" #ed?f ' a Transmission /Recertion Plan" and rpe Administrative Implementetion Aequirements identified in NUREG-1394, Rev. 1, Section 3.6, respectively. ERDS is being implemented at NMP1 __

g.. under modification number M1-90-164.

u:

The NMP1 plant process computer host is a Honeywell 4400. "

Data points for the ERDS are contained in this processor. The

.s remaining data points required for ERDS are conteined in the

^9 Meteorological Computer, a Vax 4000. Presently, these systems are not connected. The implementation at NMP1 will involve the installetion of a network linking the two computers. it will then be possible to collect, format and transmit the dats from op- ource. The Personal Computer (PC) based ERDS interface developed by the NRC ERDS implementation contractor .,

will be used for this purpose, ,'

2.0 REFERENCES

  • Federal Register Notice, Augurt 13, 19J1

Impl ementa c' ion ,

' NMPlh 0449, C. D. Terry (NMPC) to NRC, dated November 2, 1989 Letter from M. Mr.suicca (NMPC) to W. Hurt (hUS), dated ,

August /, 1991 3.0 TERML sy

  • Component - refers t a specific hardware or software J portio' of the sirstem which meets the
  • intent .f tte project.

Host - refers to component which provides near real time data.

  • Concentrator - refers to component which coliccts data from host and stores it to support user functions.

User - refers to party which has estrblished need and requirements for the tunction (i.e. NEC).

4

'4 . 0 . ' IMPLEMENTATION OF ITEMS IDENTIFIED IN APPENDIX A TO NUREG-1394, REV. 1.

4.1 Step 1 - EMPC Recei_nt of Survey _ Questionnaire 4.1.1 Discussion The " ..s s 8 communication Descriptions and Survey Questionnaire" was received by UMP 1 in a letter from the NRC to R. Murney (NMPC) dated January 1, 1990. The sur"ey has been completed and returned o the NRC.

4.1.2 P_roposed schedule Task: Complete ERDS survey Status: Complete

. Schedul : N/A l

4.2 JU ,o 2 & 3 - NMPC Contact by NUS-EI - Site Visit 4.2.1 Discussion NMPC met with NUS-EI on June 20, 1991. The site survey questionnaire was reviewed and completed and NUS-EI's involvement discussed. Resolutions to questions raised durin9 the visit are detailed in a letter to W.2, Hurt 1991.

(NUS-EI) from M. Masuicca (NMPC) dated August Task: Contact by NUS-EI Status: Comple e Schedule: N/A 4.3 Step 4 - Site Phone Line tcutallation by NRC 4.3.1 Discussion The communication link to NRC ERDS will utilize a g dedicated telepitone line as required by NUREG-1394, Rev.

1. Installation of the phons l i t., will be coordinated by the appropriate NMFC and NRC representatives.

s.3.2 Proposed Schedule Task: Install Site Phone Line Scope: 1. Assign a NMPC responsible individual

2. Identify NRC contact individual
3. Determine ERDS location based on design input
4. Senedule installation Schedule: Start Date 1/31/92 End Date 3/31/92 I

I

- . . - ~ - . . _ _ - . ., - - - - - . -. . - - _ ... - .. .

4.4 Step 5 - NMPC Return Site Survey Containino Data Point Library (DP!! and Plant Attribute Librarv Questionnairp_s (PAL 1 4.4.1 Discussion The DPL'is a database residing in the NRC ERDS which def nes characteristics associated with the utilities parameter sele' tion data points. The PAL is a database residing in the NRC ERDS which defit.es communication information required to communicate with the utility ERDS. Appendix B of NUREG-1394, Rev. 1 provides the NRC communication requirements.

The DPL requirements have been completed by NMPC and reviewed by NUS-EI. The PAL has not been finalized at this time.

Engineering will complete the PAL based on the requisite engineering procedures and design input. The PAL is dependent on the proposed hardware and software configuration for 5e ERDS.

4.4.2 Proposed Schedule Task: Establish ERDS N-tabase, DPL and PAL Scope: 1. Finalize DPL and PAL between NMPC and NUS-EI 2 Create appropriate design documentation (i.e.,

conceptual design input, requirementL specification)

3. Transmit information to NRC Schedule: Start date 3/31/92 End Date 5/31/92
4. 5. Steo 6' -- NUS-EI Develop and Implement Customized ERDS Reception Software

-4.5.1 Discussion NMPC will utilize NRC ERDS communication prot::ols to Q fine requirements. NUS-EI_will develop and implement customized sof tware for the- NRC ERDS if: NMPC's design requirements dif fer from the " generic" protocols establithod in NUREG-1394, Rev. 1.

4.5.2 Proposed Schedule Task: Devetop customized protocols Scope: 1. NMPC will provide standard protocols

, 2. Custom protocols noted to NUS-EI Schedule: Start Date -6/1/92 End Date 8/31/92

i 4.6 Sten 7 - NMPC Design and Develpp_Da_ta Transmission Sof3_ ware 4.6.1 Discussion The software development phase will include the following tasks:

a. Formalize requirements into a specification,
b. Develop a detailed design specification.
c. Develop software programs and drivers,
d. Define operational and procedural requirements.

The requirements specification is based on functions and characteristics previously defined using NUREG-1394, Rev. 1.

The detailed design specification will be based on selected components and their functions. Hardware deFign will include components required to transmit and receive host, concentrator, and user data. The software design will include functional requirements for data collection, fermatting and transmission components. Project design will also identify requirements which_ establish user interface needs with ERDS.

4.6.2 Proposed Scdedule Task: Develop ERCS software and system Scope: 1. Identify all requirements

2. Create detailed design specification
3. Develop software programs
4. Identify changes to procedural, oparational and training programs
5. Implement configuration control requirements Schedule: Start Date 6/1/92 End Date 8/31/92

4.7 gigt8 - pleli mi nalylg f twa r e Te s ting pl_s_q1s sjpn 4.7.1 This is the coftware implementation and debuggdag period.

Test requirements will be established by reviewing the aesign documents associatad with the components to be tested. Test documents will include steps which validatu software functions. NMPC will verify test requirements and document as necessary. All design and development discrepancies will be resolved during pteliminary testing.

4.7.2 PLopogei p_qhrdals Task: Perform preliminary test'ng Scope: 1. NMPC defino and develop test documents _

2. Validate and verify ERDS operation Schedules Start Date 9/1/92 End Date 9/30/92 4.8 Sipp 9 - Cosmal Testipjg, NUS-EI 4.8.1 D i s_c_u_s _sjan This implementation stap will be started when the preliminary testing has been completed satisfactorily. This test ,ill be performed by NUS-EI and will verify successful data transmission from the NMPC. NMPC will support the testing effort as required.

4.8.2 ,PJ_gaqsed Schedule Task: Formal testing performed by N1S-EI Scope: 1. NUS-EI perform formal testing

2. NMPC support as required Schedule Start Date 10/1/92 4.9 Sten 10_ _Formpl Pre-gr_erational Test on_ERDS_qqmRuter p_t_the NR_C Operations 9"Dtel 4.9.1 DiscimpLon This implementation step will be performed after NUS-EI testing has been completed. Testing will be coordinated between the NMPC plant computer system and the NnC ERDS production computer. Test requirements will oe defined by NMPC design documents ano NRC requirements and be compiled in the pre-operational test procedure. Operations acceptance will indicate final approval of the NMPC ERDS.

l 4.9. 2 nqppsed Schedul e Task: Perform pre-operational test on ERDS Scope: 1. Complete pre-operational test with NRC ERDS

2. Review and approve test results as appropriate
3. Op3 rations Acceptance
4. NMPC system operational Schedule: Start Date: 10/16/92 End Date: 10/31/92 4.10 Step 11 - Utility _on-Line.

4.10.1 Discussion This implementation phase will be performed to ensure all (1 through 11) steps have been completed. The NMPC design process will complete closecut activities as required.

q 4.10.2 P:Jp_ojed Schedule Task: 'Jtility On-line Scope 1. NMPC will review and closecut design pr ;ess 2, NMPC will receive letter from the NRC signifying that the NMP1 ERDS is on-line Schedule: Start Date 11/1/92 End Date 12/30/92 5.0 IMPLEMENTATION OF ITEMS IDENTIFIED IN SECTION 3.6 OF NilFEG-1394, BEV. 1 (ADMINISTRATIVE IMPLEMENTATION :3CUIREMENTS)

The n.ncgency Plan Implementation procedures will be modified tc initiate tne ERDS as soon as possible within one hour of the Jaclaration of an alert or higher emergency classification level.

Configuration managemcnt will be implemented to ensure data integrity of ERDS hardware and software. This will include a review by the NRC of all changes that can impact data communication protocci prior to implementation. Also, DPL changes shall be submitted utilizing the Data Point Library Reference File Form from Appendix C, NUREG-1394, Rev. 1, within 30 days of the change.

Periodic testing of the ERDS data link wil.} be conducted to verify system connectivity. The initi.al testing wi)) 5e quarterly.

ATTACHMENT B NMP2 EMERGENCY RESPONSE DATA SYSTEM (ERDSl_1MPLEMENTATION PLAh

1.0 INTRODUCTION

The Nine Mile Point Unit 2 (NMP2) Emergency Response Data System (ERDS) will be designed to provide near real time plant data to the Nuclear Regulatory Commission (NRC). The ERDS implementation plan is delitieated in Sections 4.0 and 5.0 of this attachment. Sections 4.0 end 5.0 address each item identified in NUBEG-1394, Rev. 1, hppendix A, "ERDS Transmission / Reception Plan" and the Administrative Implementation Requirements identifled in NUREG-1394, Rev. 1, Section 3.6, respectively. ERDS is being implemented at NMP2 under modification PN2Y91MX0051,

2.0 REFERENCES

' Federal Register Notice, August 13, 1991

Implementation

  • NMPIL 0449, C. D. Terry (NMPC) to NRC, dated November 2, 1989 3.0 TERMS
  • Ccmponent - refers to a specific hardware or software portion of the system which meets the intent of the project.

Host - refers to component which provides neat real time "

data.

  • Concentrator - refers to component which collects data from host and stores it to support user functions.
  • User - refers to party which has established need ar.d .

requirements for the function (i.e. NRC).

4.0 IMPLEMENTATION OF ITEMS IDENTIFIED IN APP 3NDIX A TO NUREG-1394, REV.1 4.1 Sten 1 - NMPC Receipt of "urveE_ Questionnaire 4.1.1 Proposed Schedule Task: Complete ERDS rurvey Scopet 1. Review tarvey fr: required information and identify NMPC disciplines

2. Collect information from responsible dinciplines
3. Complete survey

- . . . . - - - ~ . . -.- . - - - . - ~ . ~. - . .. .- ..

4 7

s ,

i i .

Duration: 7 weeks

Beginning Date
1/2/92 Ending Date: 2/19/92 4.2 Stepf_2 - NiiPC Contact by NUS-EI i

j 4.2.1 Discussion 4

Niagara Mohawk will solicit input and assistance from NUS as recommended in NUREG-1394, Rev. 1. The NUS contact will be established simultaneously with the site survey questionnaire phase.

4.2.2 Proposed Schedule Task: Establish contact with NUS-EI F

i Scope: NUS-EI will support utility questions and concerns

with ERDS design issues.

-Duration: -Continuous 1:

Beginning Date: 1/92 Ending Date: On-going

  • i I
_4 . 3 Steo 3 - Site Visit it 4.3.1 Discussion A site visit is not! mandatory but will be considered prior _ to

.the return of the DPL and PAL to' minimize errors in answering

the questionnaire.

i.

-4.3.2 Proposed Schedule Task: Contact NUS-EI representative for scheduling site visit.

Scope: 1. Schedule meeting with NMPC and NUS-EI responsible U disciplines if deemed necessary. .

P 2. Hold meeting.

n 3. , Resolve survey concerns.

Duration: 5 weeks

! Beginn~ing Dates- 2/20/92

-Ending-Date
3/10/92 i

l ji i-

. m . . . . _ _ . _ m .__ _ _ . ~ . - . . _ _ _ . . . . _ _ . . _ . . _ _ . _ . _ _ . _ _ . _ . . _ . . . . . . . _ _ . _

4.4 #12P_4 - Silt __EhSDe_hiat_JJ1;dAll>J19R_tR_WK

' 4. 4'.1 DlaMP.FIRD The communication link to NRC ERDS will utilize a dedicated telephone line as required by NUREG-1394, H e 't . 1. Installation of phone line will be coordinated by apprcpriate NMPC and NRC representatives.

4. 4. 2 Er_oppagLscjutdule Taak Coordinate necessary activities for installation of phone line.

Scope 1. Identify NMPC responsible discipline

2. Identify NRC responsible discipline
3. Based on surve" results or previous design input, identify NMPC location of phone line.

4.- Perform scheduling Duration: 12 weeks Beginning Date: 3/23/92 Ending Date: 6/19/92 4.5 S.tapJ__NLMPj;._IMiyLILElt.gJWly_qy collielALOS_IMLtA.Z9311k_ldhiolY (DPL)_ARqi P1ani, A110thyte LLbrary_cli!sitionpALL9JL_LPAld 4.5.1 pheylplort The DPL is a database residing in the NRC ERDS which defines

. characteristics associated with the utilities parameter selection points. Each point requires.a detailed evaluation by 7

-NMPC to complete DPt reference file sheets.

The PAL is a database residing in the NRC ERDS which defines communication information required to communicate wit.h the utility ERDS. Appendix B of NUREG-1394, Rev. 1 provides NR('

communication requirements. The survey questionnaire (i.e.,

step 1) solicits Information-to define the PAL.

2 i

r

- **- - - . = - - - ._ _ . . _ . . _ - _ _ .___._-_-.._._____________.___.____.________...___.-_._d

l 4.5.2 E r o n s.e_d _ E g h e d_ g l e Task: Complete and return the DPL and FAL information to NRC.

Scope: 1. Review the DPL and PAL

2. Identify required NMPC disciplinas
3. Schedule forma't project meeting (s) as required to obtain information.
4. Finalize the DPL and PAL between NMPC Design and NRC representatives
5. Create appropriate design documentation (i.e.

conceptual, requirt-ments specification)

6. Send information to NRC Durations 11 weeks Beginning Date: 3/23/92 Ending Date: 6/5/92 4.6 Etep 6 - NRQ Cust_q,mized Software Development Requ,iremenAs 4.6.1 Discussion NMPC will utilize desired NRC ERDS communication protocols to define requirements. NUS-EI will develop and implement customized software for the NRC if NMPC's design requirements establish communication protocols different than thooe identified in NUREG-1394, Rev. 1.

4.6.2 Prop _o_sid Schedule Task: Provide customized protocols Scope: If NMPC protocols are considered " custom" then submit to NUS-EI representative.

Duration: 11 weeks ,

Beginning Date: 3/23/92 Endine DM e: 6/5/92

~

1 I

l

4. 7 = .Steo NMPQJpf tware Development - Data Transmission 4.7.1 giscussion This development phase will include the following intermediate steps:
a. Formalize requirements into a specificatien.
b. Develop a detailed design specification.
c. ' Develop software code.
d. Define operational and procedural requirements.

The requirements specification is based on functions and characteristics previously defined using NUREG-1394, nev. 1.

The detailed design specification is based on selected components and their functions needed to meet reqairements.

Hardware design.will include components required to 'ransmit and receive host and concentrator data. Required hardware is dependent on computer systems selected for the host and concentrator. ERDS parameters will be selected using the present database oi plant process computer systems, therefore, no major _ hardware upgrades are anticipated.

Software design will include functional requirements for data collection, foreatting-and transmission components. Certain-software. requirements are dependent on data collection and transmission hardware.

Requirements will be identified which establish operator interface with ERDS. These requirements will focus on training.

and procedural enhancements. Design Control methods will be identified to maintain. configuration of the ERDS.

-4.7.2 Proposed-Schedule Task: Develop. Software L Scope: 1. Identify all requirements _

L 2. Create detailed design specification

3. Design veritication
4. Develop softwate code
5. Identify changes to operational, training'and l procedural items j 6. Identify configuration control requirements l

Duration: 10 weeks

! - Beginnir- Date: 6/8/92 t'nding Date : 8/21/92 Note. Software development is inclusive with 10 week duration and should be completed by 7/31/92.

. - . .- -~ - . . . . .- _- -- - - . - - - - -

1

, 4.8- Step 8 - Preliminarv_ Software Testing 4 . 8 .1 - Discussion Thic implementation phase is performed after completion of software development and before incorporation into plant computer systems.

The Preliminary Software Test will include the following intermediate steps:

a. Review software documentation
b. Define tesc requirements
c. Create test documents
d. Tasc software components
e. Resolve problems and retest as necessary
f. Create " Preliminary" test' report Test requirements will be established by reviewing d, tgn documents associated with components being tested. Test documents will include steps which validate software functions associated;with test requirements. NMPC will verify test requirements and documents as necessary.

All design and development-errors should be resolved during preliminary testing. Since it is possible this testing will not occur on actual plant system, test- requirements may vary.-

Changes which may occur as a result of testing will be evaluated and controlled by NMPC.

4.8.2 Prooosed Schedule e Task: Perform preliminary testing Scope: 1. NMPC will perform review and testing of vendor developed software'for data collection and transmission components of SRDS.

l '2 Preliminary testing which requires ~ data transmission to NRC ERDS willHbe performe$'as necessary.

Duration: 3 weeks-Beginning Date: ' 8/3/92 Ending Date: 8/28/92 i

P l

l V gy- -- L--nu.

4~ r.y

-w 5 g n y

4.9 Step _9 - Formal Testino. NUS-FI 4.9.1 Di.seussion This implementation phase is performed after completion of preliminary _ testing (i.e. step 8). This phase is performed at NUS-EI prior to adding NMPC to the ERDS. NMPC will support formal testing as required. Changes which may occur as a result of testing will be evaluated and controlled by NMPC.

4.9.2 Proposed Schedule Task: Formal testing performed by NUS-EI Scope: NMPC will support formal testing as required by NUS-EI.

Duration: 2 weeks Beginning Dete: 8/31/92 Snding Date: 9/11/92 4.10 Sten 10 - Formal Testina. Operations Center 4.10.1 Discussion l

This implementation phase will be performed after formal testing

' by NUS-EI-is completed.- NMPC will finalize all design ,

documentation during this phase. Software and hardware $

components will be installed ir4 the plant computer systems upon completion of design. Testing will1be coordinated between NMPC i snd_the NRC _ Computer-Operationt-. Center.and test requirements will be established by NMPC based on design-documents and

-previous: test phase results. NMPC will create test documents based on test ' requirements and.in.accordance with applicable procadures. Changes which may occur as_a result of testing will-be evaluated and controlled by-NMPC. Operations acceptance will l signify-finaliapproval of'ERDS_ testing.

l; 14.10.2 Proposed _ Schedule Task: Perform final test on ERDS l Scope: 1. NMPC will complete _all design documents.

L 2._NMPC will define, create and. perform required l testing-to validate the function of ERDS

components.

l_ _3. NMPC will coordinate all necessary interfaces with l

NRC ERDS representatives.

L

Duration: 8 weeks Beginning Date: 9/14/92 Ending Date: 11/6/92 4.11 Step 11 - Utility On-Line

".11.1 Discussion This implementation phase is performed after comp.etion of formal testing by NMPC. All steps (1 through 11) will be evaluated this point to ensure each one was properly completed.

4.11.2 Proposed Schedule Task: Complete operations and design closecut.

Scope: 1. NMPC will evaluate all incorporation steps against ERDS design practices and requirements.

2. NMPC will close out all design ERDS documents.

Duration: 3 weeks Beginning Date: 11/9/92 Ending Date: 11/30/92 L 5.0 IMPLEMENTATION OF ITEMS IDENTIFIED IN SECTION 3.6 OF NUREG-1394, REV. 1 l (ADMINISTRATIVE IMPLEMENTATION REQUIREMENTS) 5.1.1 Discussion.

l Affected site procedures (i.e. administrative, technical L support, emergcncy planning) will be reviewed and enhanced to reflect required changes to satisfy specific user requirements.

This phase will start :t beginning cf ERDS implementation and continue as design and operational requirements are defined.

i Procedures will assign _and describe the following responsibilities:

a.: Initiation of ERDS b.-Maintenance of EROS

c. Periodic testing of EROS 4

l-

\

L 5.1.2 Proposed S.nhtd ylg Taski- Identify and incorporate operational procedural requirements.

Scope 1. NMPC will identify associated groups.

2. NMPC will identify procedural requirements.
3. NMPC will incorporate procedural requirements.

Duration: On-going

, Beginning Date: 2/l f 92 Ending Date: On-going thru ERDS implementation 5.2 Configuration Management _ Imp 1pmentation Reauiremente L

5.2.1 Discussir>n Configuration management is required to maintain continued design control.of ERDS. Affected Generation and Engineering procedures

-(i.e., administrative, technical, support) will be reviewed and I

enhanced to_ reflect required changes to satisfy configuration control requirements.- This_ phase will start at beginning of ERDS E implementation and continue as design and operational requirements ,

are defined.

Procedures will assign and define group responsibilities associated with the followings-a--:ERDS problem identification b.f ERD 5 design change requirements

c. NRC notification-requirements (i.e. time restraints)

~

l 5'2.2 I Proposed Schedule

(..

(~

Task: Identify and incorporate configuration management

' procedural-requirements.

l Sc::pe 1. NMPC will identify associated groups.

L 2. NMPC will-identify procedure requirements.

l- 3. NMPC will . incorporate procedure requirements, i

i . Duration: 'on-going-Beginning-Dater _ 2/1/92' Ending Date: On-going thru ERDS implementation 4-

. - - .- .. ..
Retrieved from "https://kanterella.com/w/index.php?title=ML20079L379&oldid=2758696"