ENGINEERING CHANGE NOTICE BO PW.1 d2-g L

2. ECN Category 3. Or ig ina ta r t s Name, Organization MSIN, 4. Us9 Required? 5. Date (mark one) and Telephone NO. 3 7 3 - 7 5 2 5 Supplemental DS SCHERMERHORN , 3 2 3 3 0 , L 6 - 0 4 [I Yes [ X I NO 1 1 - 1 5 - 9 6 D i rec t Revision % 6. Pro ject Title/No./Wark order No. Change ECN Temporary Standby Supersedure Cancel/Void

7. Bldg./Sys./Fac. NO. 8. Approval Designator

t1

I; [, 300 AREA LEF NA 9

9. Document Numbers Changed by t h i s ECN ( inc ludes sheet no. and rev.)

Bur- kJ%SD-L045H-CSCM-002 I?(&# NA NA

10. Related ECN No($). 11. Related Po No.

12a. Mod i f i ca t i on Work 12b. Work Package 12c. Modi f icat ion Work Complete 12d. Restored t o Or ig ina l Condi- t i o n (Temp. or standby ECN only)

[ ] Yes ( f i l l out Elk. NA NA NA [ X I NO (NA Elks. 12b.

No.

12b)

12c. 12d) Design Authority/Cog. Engineer

Signature & Date Design Authority/Cag. Engineer

Signature E Date

1 . E C " N O 6 19562

p& ......................................

13a. Descr ip t ion of Change DO 13b. Design Baseline Docunent? [ ] Yes

REPLACE ' I;:u fl I@-- d * , Z A

QQ P

I $ C o r r e c t i o n s t o SD# a n d R e v i s i o n , p e r t e l e c o n w/OS S c h e r m e r h o r n - 14a. J u s t i f i c a t i o n (mark one)

C r i t e r i a Change [ X I Design Improvement [ ] Environmental [ ] F a c i l i t y Deact ivat ion [ ] As-Found [ ] F a c i l i t a t e Const [ ] Const. Error/Cmission [ ] Design Error lomiss ion [ ] 14b. J u s t i f i c a t i o n De ta i l s USE I P - 1 0 0 0 WORK PLAN FOR PLANT TEST OF SOFTWARE TO U T I L I Z E E X I S T I N G A D M I N I S T R A T I V E PROCEDURAL CONTROLS, REPLACE i i ~ ~ ~ ENGINEER" WITH'~OFTWARE ENGINEER" ALLOW MAINTENANCE OF BACKUP SOFTWARE COPIES IN PASSWORD PROTECTED FILE SERVERS TO PRO~IDE MORE SECURE STORAGE, E L L I M I N A T E U N R E A L I S T I C ARBITRARY T I M E BARRIERS FOR SOFTWARE RELEASE AND DOCUMENTATION.

KJ HAGERTY L 6 - 0 4 (1) DR SCHELL L 6 - 0 5 (1) :ENTRAL F I L E S A 3 - 8 8 ( O R I G )

____ ___-_ 1, . /\-7900-013-2 (05/96) GEF095

A-790001 3 1

Qb ENGINEERING CHANGE NOTICE Page 2 of 1s

[ I I 1

Improvement

Delay [ I $ [ I $

Addit ional

Savings

that w i l l be affected by the change described i n Block 13.

[ I $ [ I $

Add i t iona l

savings [ I Yes

[ X I No 19. Change Impact Revieu:

SDDiDD

Ind icate the re la ted docunents (other than the engineering dacunents i d e n t i f i e d on Side 1) Enter the affected docunent nunber i n Block 20.

1. ECN (use no. from pg. 1)

619562

Functional Design Criteria

Operating Specification

Criticalny Specification

Conceptual Design Repolt

Equipment Spec.

conrt. spec.

Procurement Spec.

Vendor Information

OM Manual

FSARISAR

Safety Equipment List

Radiation Work Permit

Environrnenfal Impact Statement

Environmental Report

Environmental Permit

16. Design V e r i f i c a t i o n Required

SeiimiciStress Analysis

StreislDedign Report

Interface Control Drawing

Calibration Procedure

installation Procedure

Maintenance Procedure

Engineering Procedure

Operating 1natruction

Operating Procedure

Operational Safety Requirement

IEFD Drawing

Cell Arrangement Drawing

Essential Material Specification

Fac. Proc Samp Schedule

Inspectlo" Plan

Inventory Adjustment Request

18. Schedule Impact (days) 17. Cost Impact

ENGINEERING CONSTRUCTION

~ ~~

Tank Calibration Manual

Health Physics Procedure

Spares Multiple Unit Listing

Test Proceduresispscification

Component Index

ASME Coded Item

Human Factor consideration

computer sonware

Electric Circuit Schedule

ICRS Procedure

Process Control ManualiPlan

Process Flow Chart

Purchase Requisition

Tickler File

..

L J [ I 20. Other A f fec ted Documents: (NOTE: D o c m n t s l i s t e d belou u i l l not be revised by t h i s ECN.) Signatures below

ind icate that the s ign ing organization has been n o t i f i e d of other a f fec ted documents l i s t e d belou. Document NmberlRevision Document NumberlRevision Docunent Number Revision

21. Approvals

Signature Design Author i ty

Cog. Eng. K J HAGERTY

Cog. Mgr. D

QA DR SCHE

Safety

Signature Design Agent

PE

QA

Safety

Design

Environ.

Other

DEPARTMENT OF ENERGY

Signature or a Control Number that tracks the Approval Signature

ADDIT IONAL

Date

A-7900-013-3 (05l96) GEF096

nNw

P P H-SD-L045H-CSCM-002, Rev. 2 ,f

300 AREA LIQUID EFFLUENT FACILITIES COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN

DS SCHERMERHORN RUST FEDERAL SERVICES OF HANFORD I N C . , Richland, WA 99352 U.S. Department o f Energy Contract DE-AC06-+3~-lOEt1396RL13200 P EDT/ECN: 619562 Org Code: R2330000 B&R Code: EW3130020

UC: 506 Charge Code: A231N To ta l Pages: 16

Key Words: Con f igu ra t i on p lan, Software, 300 Area, LEF, L i q u i d E f f l u e n t F a c i l i t i e s , Computer

Abs t rac t : sof tware c o n f i g u r a t i o n management p lan.

Th is i s t he 300 area l i q u i d e f f l u e n t f a c i l i t i e s computer

TRADEMARK DISCLAIMER. Reference here in t o any spec i f i c c o m r c i a l product, process, or s e r v ~ c e by t rade name, trademark, manufacturer, or otherwise, does not necessar i ly cons t i t u te o r ~ m p l y I t s endorsement, recommendation, or favor ing by the United States Government o r any agency thereof or i t s cont ractors or subcontractors.

P r in ted i n the United States of America. To obta in copies of t h i s document, contact. WHC/BCS Docunent Control Services, P.O. Box 1970, Mai ls top H6-08, Richland UA 99352, Phone (509) 372 2420; Fax (509) 376 4989. r,=;% ;-\ P""

4 - 'I

I

I - a 7- 9 7 . ..I

-7,m-

Date Release stamp

Approved for Public Release

A-6400.073 (10/95) GEF321

RECORD OF REVISION

I

W W l f - S D - L O 4 5 H - I ' Page I P CSCM-on7

I I ~

1

- t

A-7320-005 (08/91) WEF168

p

HNF- dC-SD-L045H-CSCM-002 P R E V W p

300 AREA LIQUID EFFLUENT FACILITIES COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN.

&-SD-L045H-CSCM-002 REV?,d300 AREA L I Q U I D EFFLUENT F A C I L I T I E S COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN.

PAGE 1 o f 14

AUTHOR DS SCHERMERHORN DATE: 1-7-97

Mid-SD-L045H-CSCM-002 REVS#300 AREA L I Q U I D EFFLUENT F A C I L I T I E S COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN

TABLE OF CONTENTS

PAGE 2 of 14

1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.4 Definitions 3 1.5 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.0 MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1 Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2 Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.3 Interface Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.4 Implementation . . . . . . . . . . . . 5

3.0 SOFTWAREiAPPLICATION CONFlGU 5 3.1 Configuration Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.2 Configuration Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.3 Application Change Requests and Problem Reports (ACR) . . . . . . . . . . . . . . . 6 3.4 Audits and Reviews . . . . . . . . . . . . . 3.5 Application Version ldentification . 3.6

3.8 Application Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5.0 SUPPLIER CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.7 BackupandRecovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.0 TOOLS, TECHNIQUES, AND METHODOLOGIES . . . . . . . . . . . . . . 9

6.0 RECORDS COLLECTION AND WTENTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Figure 1 Application Change Request and Problem Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Figure 2 ACR Continuation Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Figure 3 ACR Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4 ACR Log . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . 13 . . . . . . . . . . . . . . . . . . . . . . . . . . 14

-SD-L045H-CSCM-002 REV z i 3 0 0 AREA L I Q U I D EFFLUENT I L I T I E S COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN.

1.0 INTRODUCTION

1.1 Purpose

PAGE 3 o f 14

This Computer Software Configuration Management Plan (CSCM) provides instructions for control of the 300 Area Liquid Effluent Facilities (LEF) plant process software and associated plant process applications.

1.2 Scope

The LEF process software consists of the commercially available (off the shelf) products ‘InTouch’ produced by Wonderware Inc., ‘TISOFT’ produced by Siemens Inc and ‘DELPHI’ produced by Borland Inc. The source code for the software products is proprietary and is controlled and maintained by the vendor.

InTouch is a trademark of Wonderware Inc. TISOFT is a trademark of Siemens Inc. DELPHI is a trademark of Borland Inc.

The LEF process application consists of files produced by the commercial software as a result of input from process engineers. The process engineer input is in the form of graphical commands using a pointing device or by use of cursor control keys. The use of a typical programming language such as ‘C’ or ‘FORTRAN’ is not used, the application is entirely ‘self documenting’ as a result of a strictly graphical interface.

1.3 Overview

The LEF currently consists of several diverse facilities located throughout the 300 area. The two major components of LEF are the 300 area Treated Effluent Disposal Facility (TEDF) and the 300 area waste handling facility commonly referred to as the 340 facility. Other facilities include the 300 area waste retention facility commonly reffered to as the basins and the waste diverter stations located in the various buildings in the 300 area. This CSCM will automatically assume control of any future LEF software applications resulting from facility assignment changes ( i t . construction, expansion, reassignment etc).

1.4 Definitions

TEDF Treated Effluent Disposal Facility

300 LEF or LEF Liquid Effluent Facilities. The organization responsible for the collection and disposal of the 300 area process liquid waste.

BASINS Waste collection basins located next to the 340 complex.

340 Common name for the 340 complex located in the 300 area.

HLAN The Hanford reservation local area network.

ELAN The LEF local area network.

SOFTWARE For the purposes of this CSCM the term software refers to the object code files that comprise the commercial software products utilized to generate the application files. The source code is not distributed with the products.

APPLICATION For the purposes of this CSCM the term application refers to the output files that result from utilizing the commercial software. The files are not text editable and can only be changed by using the associated vendors software.

APPLICATION CHANGE REQUEST and PROBLEM REPORT (ACR) The administrative form used for conveying and tracking needed application corrections or enhancements. The form is not used for requesting changes in the commercial software. This CSCM does not present a formal method of requesting a change in vendor software because of the prohibitive costs of customized products.

SYSTEM CUSTODIAN The person assigned as softwareiapplication custodian.

BENCH TEST / PLANT TEST See section 3.8

1.5 Requirements

The requirements for this CSCM are from HNF-CM-4-2 QUALITY ASSURANCE 19.0 section 4.4 and HNF-CM-3-10 SOFTWARE PRACTICES 4.2 sections 3.2 and 3.3.

p

2.0 MANAGEMENT

2.1 Organization

.N&-SD-LO45H-CSCM-002 REV 2 d 3 0 0 AREA L I Q U I D EFFLUENT F A C I L I T I E S COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN.

PAGE 5 o f 14

The 300 LEF Engineering (LEFE) organization will be the custodian of the LEF Process Software and Process Applications.

2.2 Responsibilities

LEFE COG MANAGER The cog manager assigns and directs the engineer designated as the software / application custodian.

LEFE SOFTWARE/APPLICATION CUSTODIAN Note: To avoid numerous ‘software/application’ repetitions the software and application custodian will hereafter be referred to as the ‘system custodian’.

The system custodian is responsible for the following: 1. SofiwareiApplication control and storage. 2. Application maintenance. 3. Application documentation. 4. Application release. 5. Review & approval of ACR’s. 6 . Application testing.

2.3 Interface Control The LEF Operations department will be notified via the ACR form of all intended software changes that directly affect plant operation, operator training or operating procedures.

2.4 Implementation This plan will be implemented immediately upon approval

3.0 SOFTWARE/APPLICATION CONFIGURATION MANAGEMENT ACTIVITIES

3.1 Configuration Identification

3.1.1

3.1.2

3.1.3

Application documentation will be identified by using the HNF SD or drawing release system.

Software media is identified by each vendor by affixing their label to the media.

Application files are maintained in the ‘C:\LEF’ directory on each of the plant control computers hard disks. Backup application files

are maintained internally on a password protected file server in the ‘C:\LEFBU’ directory. At the present time all application file storage and transfer is done internally via the plants computer network thus removable media would only be utilized for special circumstances and if utilized would be identified by a label ‘LEF APPLICATION REV X.Y’.

3.1.4

3.1.5

Hard copy reports are identified by the source and the date. The LEF records specialist maintains a file of all reports. At the present time only one daily letter size report is produced by the plant control system, however future reports may be required.

Removable computer media utilized for data collection is identified with the source and date. The date may be blank if the media is intended to be immediately reinserted into the computer At the present time all data collection, storage, and transfer is done internally via the LEF computer network thus removable media would only be utilized for special circumstances.

3.2 Configuration Control

3.2.1

3.2.2

The configuration of the software and application will be controlled per this CSCM..

Application documentation is released and changed per WHC-CM-3-10 SP-6.1.

3.2.3 The system custodian, system cog. engineer(s) and cog manager are the approval authority for application changes.

3.3 Application Change Requests and Problem Reports (ACR)

This section contains the procedure for reporting, processing and approving application change requests and problem reports.

3.3.1 Anyone in the LEF organization may submit an ACR.

3.3.2 The submitter may submit the information via the ACR form (fig 1) or via a cc: mail, written or verbal message to the cog engineer or cog manager. The ACR continuation sheet (fig 2) may be used for expanding on the problem or for any other reason pertaining to the ACR.

p

3.3.3 For non ACR submissions (i.e via cc:, DSI, telephone etc.) the system custodian will complete the “submitter” portion of the ACR and attach a copy of any memos, DSI’s, cc: ifprovided.

The instructions for completing the ACR form are contained in the ACR instruction sheet (fig 3).

The next sequential ACR number and short ACR description is entered on the ACR log (fig 4) by the system custodian. The number is then recorded on the ACR form used for tracking the change or problem. The system engineer may maintain a suitable database as a substitute for figure 4.

3.3.4

3.3.5

l id-SD-L045H-CSCM-002 REV 2 2 3 0 0 AREA LIQUID EFFLUENT F A C I L I T I E S COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN

PAGE 7 o f 14

3.4 Audits and Reviews

No audits to verify that the products match the requirement specifications are deemed necessary at this stage of software lifecycle. Assessments to determine compliance with this CSCM will be performed periodically when considered necessary by the System Custodian or QA. Review of the changes identified on the ACR’s is a continuous process and reviewers will be assigned in accordance with CM-3-5, section 12.7.

3.5 Application Version ldentification

3.5.1 l h e ACR log contains the version number for the current configuration of the application. Version numbers follow the X.Y format with sub revisions following the X.Y.Z format.

3.6 Access Control

3.6.1 Application change access will be restricted by the system custodian and cog manager to authorized personnel.

3.6.2 Application passwords will be maintained in a normally locked cabinet by the LEF activity coordinator. The system custodian will maintain the actual password file on each plant computer.

Application backup files will be maintained by the system custodian on a password protected plant file server. This is a minimum requirement, actual backup practices may be expanded by the system engineer as deemed necessary ( i t . backup network tape drives or direct HLAN file server backup etc.). If removable media is utilized for backups the media will be identified as: LEF APPLICATION BACKUP VERSION X.Y (or X.Y.Z). If

3.6.3

p

3.8 Application Testing

l d -SD-L045H-CSCM-002 R E V 2 . 6 3 0 0 AREA L I Q U I D EFFLUENT F A C I L I T I E S COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN.

PAGE 8 o f 14

This section contains instructions for testing any changes made to the application.

TESTING DEFINITIONS

BENCH TEST _.__ A bench test consists of tests performed on the application in a desktop setting. Plant equipment and operators are not involved in the test. Bench testing is usually performed by the system custodian or other knowledgeable person.

PLANT TEST _.._ A plant test consists of tests performed in the plant using actual plant equipment and utilizing members of the operations department. Actual plant inputs are used to activate software logic. A bench test usually preceedes a plant test.

3.8.1 The system custodian will determine the type of testing to be performed. The following requirements will be adhered to.

a. Application changes that do not impact equipment control or data handling ( is . display, recording etc.) do not require testing. Examples of such changes are: typographical errors, graphical corrections (i.e. line or object misalignment etc.).

b.

C.

Application changes that impact equipment control or data handling require a bench test prior to installation in the plant. Bench testing must always be performed prior to plant testing.

Application changes that impact equipment control or data handling require a plant test unless bench testing can prove conclusively that plant testing is not warranted. If bench

-L045H-CSCM-002 REV 2X300 AREA L I Q U I D EFFLUENT TIES COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN.

test results are not conclusive then a plant test must always be performed. Plant testing is always required for complex sequence application changes (for example backwash or leadilag pump logic) regardless of bench test results.

In the case of plant testing the system custodian will supply required test instructions via the LEF work plan administrative system identified in IP-1000 section 3.1 ‘Technical Procedure Control Process’. The following content guidelines will be used to develop the instructions, however the work plan format will not be changed to accommodate the content.

3.8.2

PAGE 9 o f 14

TEST TYPE TEST SCOPE TEST EQUIPMENT REQUIREMENTS TEST PERSONNELL REQUIREMENTS SPECIAL PLANT MODE REQUIREMENTS TEST ACCEPTANCE CRITERIA TEST PREREQUISITES TEST INSTRUCTIONS TEST RECOVERY

3.8.3 BENCH TESTING ... The system custodian will perform all bench testing and initiate actions to correct any deficiencies. Bench test performance completion is documented on the ACR form.

3.8.4 PLANT TESTING ... The system custodian will observe all plant tests and initiate actions necessary to correct any test defficiencies. The system custodian may sign all plant test acceptance criteria steps if directly observed, however signature by the performing operator or shift operations manager is preferred.

4.0 TOOLS, TECHNIQUES, AND METHODOLOGIES

4.1 There are no special tools, techniques or methods that are used for accomplishing this CSCM.

5.0 SUPPLIER CONTROL

5.1 There are currently no plans or need for contract-developed software. If such a need arises in the future the software will be developed, tested, accepted and controlled per WHC-CM-3-10,

p Aid-SD-L045H-CSCM-002 REVz.?300 AREA L I Q U I D EFFLUENT F A C I L I T I E S COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN

PAGE 10 o f 14

3. DESCRIPTION OF PROBLEMIREOUEST OK ATTACH: II

4 REQUESTED COMPLETION DATE 5 EMERGENCYIPRIORITY 0 Yes 0 No

8 EMERGENCYIPRIORITY CHANGE AUTHORIZA rlON DATE. II ~~

10 TEST DESCRIPTION ATTACHED DATE

11 TRAINING REQUIRED (0 Yes 0 No) DATE

9. TEST REOUIRED (0 Bench 0 Plant 0 NA): DATE: II

I

SYSTEM CUSTODIAN

COG MGR

ENV

SYSTEM COG

12. TRAINING DESCRIPTION ATTACHED: DATE: II

SAFE ry

QA

OPS MGR

13. PROCEDURE CHANGE REQUIRED (0 Yes U No).

14. PROCEDURE CHANGE DESCRIPTION ATTACHED.

15. U S 0 REQUIRED (U Yes 0 No):

DATE:

DATE:

DATE:

16 U S 0 REVIEW ATTACHED DATE. II 17 APPROVAL SIGNATURES OBTAINED DATE

18 BENCH TEST COMPLETED DATE

19 APPLICATION READY FOR PLANT TESTING DATE ~~

20 PLANT TEST COMPLETED DATE

21 BACKUP FILE CREATED DATE

22 VERSION NUMBER ASSIGNED ro THIS CHANGE- DATE

23 ACR COMPLEIED DATE

Mf-SD-L045H-CSCM-002 R E V d 300 AREA L I Q U I D EFFLUENT F A C I L I T I E S COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN.

PAGE 12 o f 14

Figure 3 ACli Instructions

5C I :: SC

Iftraining IS required (see hlock I I ) then entcr signature signifying that training dcscription IS attached

Detrmme 11 operating or maiiitensncc procedurc changes are reqiiirrd and sign block

14 SC

I S SC

I6 SC

llproccdure change\ are required then attach procedure change description and sign block

Detcrmine 11 U S 0 screening IS required and enter signature

If U S 0 screening I S required (see block I S ) tlwi enter sgnalure signifLmg that completed US0 w c c i i i n ~ form IS allached

~~ ~

17

obtaining approval \ignatures Sign block wlien all signatures are present

I f applicable enter rignilturc when bench testing IS completed (see block 9)

I nter vgnaturc whcn application changes are installed and application IS ready for testing

llapolicable enter \ixnatur~ when plant tcstiiiE IS completed (see block 9)

18 sc

19 7c

20 SC

21 SC

22 SC Enter version numhcr asssigned to this applicvtion change

Ltldl s,gnvturc M h C I l hvc lup appllcatlon files are 111 place

I 2 3 sc 1:nter q q i l t i i r c w h c n ACll IS completed

24 APPROVERS Appropriate approval signatures are entered lherc whcn blocks 1-16 have been completed

y H-SD-L045H-CSCM-002 REV 2 6 3 0 0 AREA L I Q U I D EFFLUENT F A C I L I T I E S COMPUTER SOFTWARE CONFIGURATION MANAGEMENT PLAN.

PAGE 14 o f 14