ML18087A748

From kanterella
Jump to navigation Jump to search
Rev 4 to Insp Order Program.
ML18087A748
Person / Time
Site: Salem  PSEG icon.png
Issue date: 02/05/1982
From:
Public Service Enterprise Group
To:
Shared Package
ML18087A720 List:
References
AP-10, NUDOCS 8303160618
Download: ML18087A748 (12)
v • d • e


Text

SET NO. _ _ _ _ _ _ _ __

J ADMINISTRATIVE PROCEDURE NO. 10 REVISION NO. 4 INSPECTION ORDER PROGRAM

~8303160618- -830314 - - -------

PDR ADOCK 05000272 S PDR 11.P-l I

Form AP-l-l Rey. ll

TABLE OF CONTENTS SECTION TITLE PAGE

1. 0 PURPOSE 1 2.0 SCOPE 1 3.0 RESPONSIBILITIES. 1
4. o* IMPLEMENTATION 2 s.o SYSTEM REPORTS 3 6.0 RECORDS 4 Attachment 1 Instructions for Completing an I.O. Request Form Attachment 2 Determination of I.O. Tasks When Computer is Inoperable AP-10 i Rey. 4
    • ADMINISTRATIVE PROCEDURES SALEM GENERATING STATION ADMINISTRATIVE PROCEDURE NO. 10 INSPECTION ORDER PROGRAM 1.0 PURPOSE This proc;:edure describes the program to provide timely notification to departments of required tasks of a recurring nature, including: inspections, surveillance and preventative maintenance.

2.0 SCOPE 2.1 The Inspection Order (I.O.) System shall inform the responsible department of the details of the particular task (i.e., procedure .number, tolerance for completion, etc.)

2.2 The I.O. System shall provide the station management with a list of outstanding and overdue inspection orders.

3.0 RESPONSIBILITIES 3.1 The Technical Department (I&C) shall maintain the I.O. System and shall:

\

3.1.l Enter I.O. requests into the computer file*.

3 .1.2 Issue the I.O. cards to the responsibl~ department head.

  • a) The I.O.'s for il Unit shall be printed on blue cards, #2 Unit on yellow cards and all others on white cards.

3.1.3 Update the computer as completed I.O. cards are returned.

3.1.4 Inform station management of overdue inspection orders once per week.

3.1.5 Take the necessary action to enable station personnel to perform tasks pursuant to regulatory requirements (i.e., those items having an entry in Box 12 of Form AP-10-l} when the computer is inoperable (see Section 4.4).

3.2 Departments utilizing the I.O. system shall:

3.2.1 Execute the tasks and return the I.O. cards to the Technical Department (I&C) immediately upon completion.

3.2.2 Request new orders or revisions to existing orders as needed .

3.2.3 Insure proper record retention per Section 6.0.

,AP-10 P~ge t of 4 Rev. 4

  • 4.0 IMPLEMENTATION 4.1. Initiation 4.1.1 Department supervisors shall request I.O. cards by filling out the Inspection*

Order Request Form (AP-10-1) legibly, accurately and completely (see Attachment 1 for instructions and samples).

4.1.2 The department head or his designee shall approve the request and forward it to the Senior Technical Supervisor (I&C).

NOTE A supervisor of one department may submit an I.O. request for an activity to be performed by another department provided he has the written approval of the department head who shall be responsible for performing the task.

4.1.3 The Technical Department (I&C) shall assign the request a unique number and take the necessary action to enter it into the computer file.

4.2 Completion

  • 4.2.l Once each week the Technical Department (I&C) shall call out from the computer all of the order cards due for the following week, an outstanding list and an overdue list. The order cards and the overdue and outstanding list shall be forwarded to each responsible department head by Friday.

NOTE The overdue and outstanding lists shall be forwarded to the Station Quality Assurance Engineer and General Manager - Salem Operations.

4.2.2 The department head shall:

al Forward the new I.O. cards to their responsible supervisors for completion .

bl Be responsible for investigating overdue orders and for taking appropriate action.

4.2.3 The cognizant supervisor and the person completing the work shall:

al Sign and date copy 2, signifying that requirements have been satisfactorily completed, and return it to the Senior Technical Supervisor (I&C) for computer updating *

    • bl If required by Section 6.1, sign and date copy 1 and retain in departmental file.

I

u>-10 Page 2 of 4 ~ev. 4
    • 4.3 Revisions Revisions to existing orders shall be made using the Inspection Order Request Form and are subject to the same review and approval requirements as the original inspection order. Only the I.O. number, unit number and the information to be revised need be entered on the request form.

4.4 Notification - Computer Inoperable If the cards for the new period are not issued by Friday, the following steps shall .*.I be taken:

4.4.1 Department heads shall be notified in writing by the Technical Manager that the \

I.O. system is not operational.

4.4.2 Each department shall determine what I.O.'s are outstanding and when they are due using the last outstanding list.

4.4.3 Each department shall use the dates on the current summary list to determine what tasks should be completed during the next week (see Attachment 2 for instructions).

4.4.4 A record of all I.O. 's completed shall be maintained to update the computer records when the system is restored.

5.0 SYSTEM REPORTS The following is a description of the computer reports available upon request from the Senior Technical Supervisor (I&C). The reports include all information on the Inspection Order Request Form, as well as the next issue date, due date and the last completion date.

5.1 Inspection Order summary Report This report provides a numerical listing of all inspection orders presently in the computer file.

5.2 Inspection Order System Summary Report This report gives the same information as 5.1 except the orders are listed by System Code rather than numerical (i.e., all orders performed on the Reactor Coolant System are listed together).

5.3 Inspection Order Outstanding Report This report lists only the orders that are outstanding at the time of report issue .

  • 5.4 Inspection Order overdue Report This report lists only the orders that are overdue at the time of report issue.

AP-10 Rev. 4

  • 5.5 NOTE The outstanding and overdue reports are issued weekly per Section 4.2.1.

Inspection Order Forecast Report This report lists by Inspection Order number the orpers to be issued for some specified period of time in the future. The report may be used as a planning tool.

The report may include any frequency of issue (i.e., all I.O.'s with frequency of issue greater than one month or all I.O. 's to be issued prior to the next refueling outage)

  • 6.0 RECORDS 6.1 Inspection Order cards used to document the completion of tasks where no data sheet or procedure check-off sheet exists (i.e., annual reviews of manuals or procedures by department heads or lubrication of pumps and valves), shall be maintained by the department completing them for five years. The cards shall be filed numerically.

6.2 Inspection Order cards shall not be used as a document of record to:

6.2.l Verify completion of .tasks requiring data; to show compliance with regulatory requirements. A completed procedure, check-off sheet or data sheet shall be retained in .accordance with AP-11, Record Retention Program. Retention of I.O. cards issued for these requirements is optional.

6. 2. 2 Verify calibrat_ion of instruments and controls. Instrument Calibration Data Cards (.ICD) or other means of _documenting instrument calibrations are required.

Retention of I.O. cards issued for these requirements is optional

  • AP-10 Page 4 of 4 .Rev. 4
  • 1. Initiator ATTACHMENT l INSTRUCTIONS FOR COMPLETING AN I.O. REQUEST FORM (Form AP-10-1)

Enter the appropriate number in the block for the type of request.

2a. Initiator Enter the code number of the department who shall be responsible to perform the work.

  • 2b. Technical Departrnent-I&C For new I.O. 's the Technical Department-I&C shall assign a number to the I.O. then enter it on the form.

or Initiator For revisions to or deletions of existing I.O.'s enter the numbers starting at the right (I.O. #400372 would be 00372).

2c. Technical Departrnent-I&C Enter check digit in accordance with departmental procedure.

3. :X:nitiator Enter code for type of I.O. being requested. The types of I.O.'s available are:

I Inspection; To order work required by department or Station Procedures. overdue notification is provided.

s surveillance; To order work required by regulatory agencies (i.e., N.R;C., D.R.B.C., etc.). Overdue notification is provided. If "S" is chosen, 6c shall be "C" and Item 12 shall be completed .

  • 4. Initiator L

W Lubrication; To order lubrication of plant equipment in accordance with the Station Lubrication Manual.

overdue notification is provided.

Work Memo; To order work where no overdue notifica-tion is desired.

Designate on which unit the I.O. is to be performed. If identical tasks are to be performed on more than one unit, separate request forms for each unit are required.

5. Initiator Print the name of the system to which the equipment (item 13) belongs on the two lines provided.

Technical pepartrnent-I&C Enter the numerical code for the system into the 4 boxes.

6a. Initiator Enter the number of units selected in 6b between issues of this inspection order. For example, if 6b is days and you enter 31 for 6a, card will be issued every 31 days.

6b. Initiator Specify the unit interval for the I.O. in conjunction with 6a.

. 6c. Initiator Enter the code for the appropriate basis for issuance. The available bases are:

C - Calendar - Orders will be issued on the same frequency each time regardless of completion date

(_i.e., every 30 days.l

  • NOTE All surveillance orders, i.e., those having an "S" in Box 3, shall be "C" .
  • I - Interval - Orders will be issued on the same frequency after the last completion date (i.e.,

a monthly order will be issued 31 days after completion of the last one.

AP-10 P<l~e 1 of 5 ll,ey. 4

  • 6d.

7.

Initiator Initiator Specify the number of days after the order has been issued that will become overdue. Mark N.A. for work memo's.

Optional - Estimate the total manhours required to complete the task. This estimate will be printed only on the summary lists to be used for planning purposes.

8. Initiator Specify if the I.O. task requires an outage to perform. For inspection orders that can only be accomplished with the plant in a shutdown condition, a scheduled outage should be designated. Orders required to be done during refueling outages should be designated refueling.
  • This will allow designated outage requirements to be pulled from the computer in a single program call out. Orders will also appear on routine callout if their issue dates fall due.
9. Initiator New requests only, designate the first date the order should be issued. This will key the computer to dates to issue the order (i.e., if the first issue date is 12/5/78 and the order is monthly, the order will be issued on 12/5/78 and every 31 days thereafter) *
10. Initiator If the I.O. request is a mode dependent Technical Specifica-tion requirement place an "X" in the box for each mode the surveillance is required. For all non-mode dependent I.O.

requests leave the boxes blank.

11. Initiator Specify the procedure which will be used to perform the task.

only one procedure should be used.

12. Initiator Specify the applicable agency, the document and section that requires this task to be performed. This section shall be completed for all inspections, maintenance actions, tests, etc., which are performed to comply with Federal, State, NRC, NJDEP, DRBC, Insurance and QA Program requirements. All request forms having an entry in this section shall be Surveillance Orders (i.e., an "S" shall be. entered in box 3, form AP-10-1) *
13. Initiator Specify the piece .of equipment or type of equipment (i.e.,

Ill Safety Injection Pump, or Safety Injection Pumps).

Describe the task to be performed (i.e., Perform Channel Functional Test on Loop lPT-516)

  • Any other information desired should be added in this section, space permitting.

COMPANY LOCATION Initiator Enter Salem SUBMITTED BY Initiator Sign and date request APPROVED BY Initiator's Department Head Sign and date request Attachment 1 AP-10 Page 2 of 5 Rev. 4

~

I

  • FORM NUMBER _ _ OF _ __

INSPECTION ORDER SYSTEM 0

INSPECTION ORDER REQUEST FORM ACCOUNT No. EP- SALU - POI

~ TYPE OF REQUEST I 1 NEW INSPECTION ORO£~ KCYPU~H INSTRUCTIONS: DUPLICATE COLUMNS I THAU 1. ONLY CAROS

'I I 071 Z : CHANGE TO AN EXISTING llJrtSPECTIO,. ORDER

3.
  • 0£LETtOH Of AN EXISTING INSPECTtON ORDER HAVING ENTRIES ARE TO BE PUNCHE.0. ALL CARDS PUNCHED Will HAVE 0

ITEM©°TYPE OF R(OUEST DUPLICATED IN COLUMN 11. THC CARO NUMBER WILL BE PUNCHED IN COLUMN 70 AS INDICATED lfrf RIGHT MOST Ball.

CARD NUMBER [ _

COLU.... 70 ~

0 INSPECTION ORDER NUMBER 0 TYPE OF INSPECTION ORDER G UNIT NUMBER 0

  • 0 I INSPECTION I *UNIT I

~

I l?l D£PT. CODE PREFIX 5

  • PERFOllMAHCE I Hll/ftC J SEOUEMCE NUMllU IONUMllER INTEGRITY

[3 s I SURVEILLANC[ 2 *UPitlT 2 IIIIII D I

  • OPERATIOOIS l 1 WBRICATION 5 *UNIT S P£RF DEPT. CHECK DIGIT 9

~ 2

  • MAINT[NANC£ ** QUALITY ASSURANCE W* WORK MEMO Q1CO... OH ENTERS NUMlllE ..

5* SAFETY 11 Q.[RICAl. OFFICE 2 5 4 5 8 FOR NEW IO'S.

4* PERFORIUHCE (It CJ 8* CHIEF ElfOIHEER 9* ntAININO SYSTEM 0 TO BE ISSUED EVERY:

RE/JC.Tot? 0*No OF UNITS . G) ..!!!!'!!__ ON Tl'E BASIS f7 : 0* OYE~OUE 11111 AND AFTEft 0

  • DAYS c

~DAYS I (CALENDAR) 10 II IZ 13 (COO[ ENTERED UY PERFORMANCE DEPT. J M

  • MONTHS FROM LAST ISSUE y I YEARS I I I INTEFNAL J 17 18 FROM LAST COMPLETIOfl 19 20 21 FROM ISSUE M*EsTIMATED

\.!.__) TASK MANHOURS

(;;\OUTAGE

\::J REQUIREMENT 0* FIRST ISSUE DATE rj()\

V SURVEILLANCE MODES ~ PROCEDURE NUMBER I 4 fL1

~~~~DD 1111111 blqlz@ 111'° 5

  • SCHEDULED

~ ..

  • REFUELING Z2 23 24 N* ~T:c~~~l~OUIR£D ~ 26 Z1 28 29 3() 31 32 33 34 35 !ii 37 38 39 40 41 42 43 44 4~ 46 47 48 49 Pl.ACE "x" IN APPLICABlE
  • USE RIGlfT MOST COl.Utolfl FlftST - FILL IN Ill.INKS WITH ZEROS - lo. 2 M'r.I WOULD BE WRITTEN IN Sd AS 002 MODE BOXIESI

@ REGULATORY REQUIREMENT

@ LIST EQUIPMENT FOi.LOWED BY A SLASH (/J F'OLLOWED DY THE TASK DESCRIPTION

. SPECIFY DOCUMENT ANO NOTES: DO NOT SPLIT WORDS BETWEEN LINES UNLESS ABSOLUTELY REOUIRED. USE A 5""CE FOR PtmCTUATION SECTION NUMBER ANO ALLOW A SPACE FOft BLANKS BETWEEN WORDS.

[!oft SURVEILLANCE Io's ONLY] CMSTINGUISH BETWEEN LETTERS ANO NUMBERS: 9,I

  • LETTERS i 0, l
  • NUMBERS V\i .( ll ~ 1r~ t/' 3, z; I vtW1F'I IEIH!. fl

.2 ill I b. ('.. TI OlN

.3 31-1>-1-J.-J.-l--+-l--l--l--l--l-.J--l--l-lf--l-+-l--l--l--l--l--l-+-+-t--l--4~-+-+-+--+--++--+--+--+-+-t-t--r-l-+-+-+-t---t---t--t-t

.4

~l--l--l--l--ll--ll--lf--1f--1-+-+-+-J.-l--l--l--l--l--l--l--l--l--+--+--+--+--+--+--+--+-+-+-+--l-+-+-+-+-+-+-+-+-t--t--t--1f--l-+-+-t-;

.5 10 COMPANY LOCATION SUBMITTED BY _

REVIEWED f'OR AP-tO f'OMI Al'-10-1 REV. 2: AWROVEO BY CORRECT FOR'-IAT PERF DEPT (INITIAL J

~I

...... R>ftM NUMBER _ _ OF _ _ INSPECTION ORDER SYSTEM 0

INSPECTION ORDER REQUEST FORM ~T No. EP- SM.II - POI

~ TYPE OF REQUEST .

I

  • NEW INSl'ECTION OR0£11 KEYPUNCH INSTRUCTIONS : DUPLICATE COLUMNS I THAU 1. ONLY CARDS I

~ I 2 1 CHANG£ 1U AN E*ISTUrfG 1"5PECTI°" ORDER HAVING ENTRIES ARE TO BE PUNCHED. All CARDS PUNCHED '#Ill HAV[ CARD NUllBEll l_

5.
  • DELETION Of AN EXISTING INSP£CTION ORDEll ITUl@'TYP£ Of REQUEST' DUPLICATED IN COLUMN TI. THE CARD NUMBER COLUMN 70 I WILL BE PUNCHED IN COLUMN 1D AS INDICATED IN RIGHT MOST IOX.

TI .

0 INSPECTION ORDER NUMBER 0 TYPE OF INSPECTION ORDER 0 UNIT NUMBER 0 0* 0 I

  • INSPECTION I I UfflT I

[§ ~

ot:n. CODE PllUIX 5#.QUCNCE HUMBEi! ;DNUMllEll S

  • SURVEILLANCE 2*Utt1T I r.:J s. l'EAfQllllAHC[ I HR/RC I

~~~I~~

I

  • OP£RATIONS INTEGRITY D S *UNfT !

l

  • WBRICATIOH PERF. DEPT. CHECK DIGIT 9

~ t

  • 11a1NTENANC£ *
  • au.lurv ASSURANCE ENTERS NUllllt:ll

'I W* WORK MEMO O*COWON

!* SAJ"ETY 1

  • Q.ERICAL OFFICE 2 5 4 s s FOR NEW IO*s.

4

  • PEllfOIHIANCE (I f CI I* CHIEF EMOIHEER I TttAINtNO 0

I SYSTEM 0 TO BE ISSUED EVERY :

0I:o lktJc.:f'oR- Coo1...1111J T ©*No Of UNITS 0 ...!!!!!!._ 0 ON THE BASIS Of : 0* AND OVERDUE AfTEll C * (CALENDAR I

~ ~om DI DAYS 10 11 12 13 I COOE ENTERED BT P£RFOAM~CE DEPT.)

(g9lJ 14 IS 16 M *MONTHS Y

  • YEARS 18 FROM LAST ISSUE I
  • I INTERVAL I FROM LAST COllPl.ETION 17 19 20 21 FROM ISSUE r:1°ESTIMATEO

\J_) TASK MANHOURS

(;;'\OUTAGE

\V REQUIREMENT 0* FIRST ISSUE DATE Q

l\J SURVEILLANCE MODES ~ PROCEDURE NUMBER z ' s e cr1 rn rn 4

22 25

~ ::~:~:TREOUIRED 24 10 ACCOMPLISH 25 28 27 21 29 so

~0~~00 51 52 55 54 5S 541 Pl.ACE .)(.. IN APPLICABl.E I 1111111,,,19!0?~ 111 J1 58 59 40 41 42 45 44 45 46 47 48 49 so 1:l 0

c:

~US#. lllGHT MOST COlUllN FIRST - fill IN ILANKS WITH ZEROS - It. 2 DAYS WOULD BE WRITTEN IN 6d AS 002 MOOE eox (ES)

..en, t'1 REGULATORY REQUIREMENT SPECIFY DOCUMENT AHO LIST [OUIPllENT FOLLOWED IT A SLASH (/I FOLLOWED BT TN[ TASK DESCRIPTION NOTES: DO NOT SPLIT WOADS BETWEEN LINES UNLESS ABSOLUTELY REQUIRED. USE A SPllCE FOii PUNCTUATION SECTION NUMBER AND ALLOW A SPACE FOR BLANKS BETWEEN WORDS.

(_,oR SURVEILLANCE ro's ONLY] DISTINGUISH BETWEEN LETTERS AND NUMllERS: 9, I

  • LETTERS I O, I
  • NUMBERS

,. r-r /;: I IP

~~ c.. s-r 5 1 J-1

  • J. ,J.. I~ i II c. To[~ Co (J J.._ Arr.I -r ',p v ,,.. fJ I vE Rt t:[y t= IJ CH l,p "

111 /J c: o4l 2

.2 p. ,b. IC UnJ O't ~ IF I! EK; i) :1:: It (., l/ ,c. c: {Ii /J I 1-f (r:> ~ 3 2 Afti l,)"' 0 J: ~ \) 0 J... h'1A Gt fl (Ii /)

4

.3 3 5

.4 6

.!I ID 20 21 2S 50 55 4U 4> so 5S 60 6S COMP>\NY 0 ti I LOCATION --<V..u.a,_,,.i.._.E.~-~(Yl'-'-'----- DATE lfia 1129

,_,,_to f°"M A~-10-1 "fV.2 DATE I( / O:J ..L2.!l REVIEWED FO" CORRECT fOftMAT P["f [)[PT. (INITIAL J

FORM NUMBER _ _ OF _ __ INSPECTION ORDER SYSTEM INSPECTION ORDER REQUEST FORM ACCOIMT Mo. EP* SALM - POI TYPE OF REQUEST I

  • t-tEW INSPECTION OROCR ME'l'PUNCH INSTRUCTIONS: DUPLICATE COLUMNS I H~RU 1. ONLY CARDS I

I TI 2 1 CHANGE TO AN EXISTING INSPECTION ORDER

3. I 0£LETION Of AH [)USTING INSPf.CTION OROEA HAVING ENTRIES ARE TO BE PUNCHED. All CARDS PUNCHED Will HAVE ITEM©'TYPE OF REQUEST' DUPLICATED IN COLUMN 11. THE CARO NUMBER Will OE PUNCHED IN COLUMN 10 AS INDICATED IN RIGHT MOST BOX I CARO NUMBER COLUMN 10 I 0 INSPECTION ORDER NUMBER 0 TYPE OF INSPECTION ORDER 0 UNIT NUMBER 0 0 I s INSPECTION I *UNIT I DEPT. COOE PREFIX 5
  • PERFORMANCE I HR/~C I
  • SEQUENCE NUMBER 111°1"191~

~

D S *SURVEILLANCE D :l*UNIT 2 1-1 z

~

INTEGRITY D

I

  • OPERATIONS l
  • LUBRICATION 5 *U"'IT 3 PERF DEPT. [I) 2 *MAINTENANCE 6* QUALITY ASSURANCE CHECK DIGIT 9 ENTERS NUMBER W 1 W()qt( MEMO O*CQM1ilON 'tl 3* SAFETY f 1 O..ERICAL OFFIC{ 2 3 4 5 6 FOf! NEW !O'S. hJ

()

4* PERfORMANCE (lfC) 11!1* CHIEF ENGINEER 8 9* TRAINING H 0 SYSTEM 0 TO BE ISSUED EVERY:

0 z

0*No G) © ©*ANDOVER~

0

~

Il Il I OF UNITS UNITS ON TH£ llASIS OF :

t1 tO II 12 13 I COOC ENTERED BY PERfORMANCE DEPT.)

ill]

.. I~ 16 D 17 0

y I

.. I I

DAYS MONTHS YEARS D18 c I I CALENDAR I J1 FROM LAST ISSUE (INTERVAL)

FROM LAST CQUPLETIOf4 ill]

19 20 21 FROM ISSUE DAYS

'1, t1 M

t"'

(/)

s:

'U

~*ESTIMATED 0* Ii()\

M

>-3 t-4

~z fn\ SURVEILLANCE M

~

OUTAGE FIRST ISSUE DATE

\.!__) TASK MANHOURS V REQUIREMENT V MODES PROCEDURE NUMBER 0 H

w rn I 2 3 8 22 23 D24 9

  • SCHEDULED A
  • REFUELING N
  • OUTAGE NOT REOUIRm TO ACCOMPLISH 2' 26 27 28 29 30 DD DODD 31 32 PLACE 33
  • x" IN 34 3~

APP\.ICABLE 3G 111111111111111 J1 38 39 40 41 42 43 44 45 46 47 48 49  !()

0

~

c:

M

  • USE RIGHT MOST COLUMN flRST - FILL IN l!LANKS WITH ZEROS - It. 2 DAYS WOULD llE WRITTEN IN 6d AS 002 MOOE BOX(ES) (/)

REGULATORY REQUIREMENT 0 LIST EQUIPMENT FOLLOWEO BY A SLASH I/I RlLl.OWED BY THE TASK DESCRIPTION

>-3 tn

. SPECIFY DOCUMENT ANO SECTIO"t NUMBER NOTES: 00 NOT SPLIT WOROS BETWEEN LINES UNLESS ABSOLUTELY REOUIREO.

ANO ALLOW A SPACE FOR BLANKS BETWEEN WORDS.

USE A Sl'llCE FOR PUNCTUATION

~

t"'

[roR SUltVEILLANCE Io's OtfLY] lllSTINGUISH BETWEEN LETTERS ANO NUMBrns: 9,l

  • LETTERS; 0, I. NUMBERS 11! M 2

l-+-f-+-+-+-+-+-+-+-+-+-+-+---1.1 3

4

.3,_..__.,.__,__,__,.___,_......_.__,~,__._..___,_~.3

!I Al-+-+-1--<i--<._j._j-l--l--l--l--l-~-l4 6

60 6~ 10 I~ 3~ *~

~o ~

~~

21 30 40 SUl!MITTEOe*_ DATE l_!_j_o/ 180 "EVICWCO fOflt a11-t0 H,,.M AP-10-1 R[V Z APPftOVEO ll!IY I - --:- I /".. --- - ~-* > OAT£/ .!__Lo_ll.Q_ 0 CORRfC T FORMAT PERF DEPT. I INITIAL I I tf J

  • Example 1 ATTACHMENT 2 DETERMINATION OF I.O. TASKS WHEN COMPUTER IS INOPERABLE A calendar issue I.O. cycle of one month was issued on 790201. When the I.O. is completed the next issue date would be one month from the last issue date or 790301.

Example 2 An interval issued I.O. that has a cycle of one month is issued on 790201. When the I.O.

is completed, the next issue date would be one month from the completion date. If the completion date was 790215 the next issue would be 790315 .

AP-10 Page 1 of 1 ~ev. 4

Retrieved from "https://kanterella.com/w/index.php?title=ML18087A748&oldid=2411271"