5' ,-. !% pw. 1 edt no 2. to: 3. from: (originating...

,-. PW. 1 01

1 EDT NO 6 1 4 7 1 8 2 !% ''5' ENGINEERING DATA TRANSMITTAL

2. To: (Receiving Organization)

Distribution

HSI 5 . Proj./Prog.lDept./Div.:

3. From: (Originating Organi;!ation) 4. Related EDT No.:

Sitewide Systems Engineering N/A

M. L . Grygiel N/A 6. Cog. Engr.: 7. Purchase Order No.:

I I I I I 16. K M

Disposition IHI & IO Approved 4. Reviewed nolcornrnent

5 . Reviewed wlmmment 6. Raeaipt acknowledged

2'. Approved wlmrnmsnt I. Disapproved wlmrnrnmt

IGI (HI gn.t"re*l

IKI Signature ILI Date IMI MSIN Diw. son

8. Originator Remarks:

11. Receiver Remarks:

- 19.

9 . Equip./Corrponent No.:

N/A

N/A

N/A

N/A

10. System/ELdg./FaciLity:

12. Major Assm. Dug. No.:

13. Perni t lPerni t Application No.:

14. Required Response Date:

Authorized Rapnaontstivs Date for Receiving Organization

DATA TRANSMITTED ( F ) ( G ) ( H ) Appmval Reason Origi-

IEl Ti le or Doscription of Data ,or "ator

NO. NO. Transmined nator Trans- Dispo- mind skion

161 Docurnent/Drawing NO.

WHC-SD-WM-SEMP- Site Systems N/A 1 1 004 Engineering !Systems

Engineering

21. DOE APPROVAL ( i f required) C t r l . No.

Cognidnt Manager

( 1 ) Rscoiv-

Dispo- sition

BD-7100-172-2 (04/94) GEF097

WHC-SD-WM-SEMP-004, Rev. 0

Site Systems Engineering Systems Engineering Management Plan

M. L. Gryg ie l Westinghouse Hanford Company, Richland, WI\ 99352 U. S. Department o f Energy Contract DE-AC06-87RL10930

EDT/ECN: 614718 uc : Org Code: 02100 Charge Code: Y21101 B&R Code: EW3120075 To ta l Pages: 5'4

Key Words: Systems Engineering, Hanford S i t e Technical Basel ine, I n t e r f a c e Contro l Documents, Document Hierarchy, Mul t i -Year Program Plan,

Abs t rac t : The S i t e Systems Engineering Elanagement Plan (SEMP) i s t h e Westinghouse Hanford Company (WHC) implementation document f o r t h e Hanford S i t e Systems Engineer ing P o l i c y , (RLPD 430.1) and Systems Eng ineer ing C r i t e r i a Document and Implementing D i r e c t i v e , (RLID 430.1). These documents d e f i n e the U.S. Department o f Energy (DOE), R ich land Operat ions O f f i c e (RL) processes and products t o be used a t Hanford t o implement t h e systems engineer ing process a t t h e s i t e l e v e l . Th i s SEMP descr ibes t h e products be ing prov ided by t h e s i t e systems engineer ing a c t i v i t y i n f i s c a l yea r (FY) 1996 and t h e associated schedule. I t a l s o i nc ludes t h e procedura l approach being taken by the s i t e l e v e l systems eng ineer ing a c t i v i t y i n t h e development o f these products and t h e in tended uses f o r t h e products i n the i n t e g r a t e d p lann ing process i n response t o t h e DOE p o l i c y and implementing d i r e c t i v e s .

k r i

TRADEMARK DISCLAIMER. trade name, tradenark, manufacturer, or otheruise, does not necessarily const i tu te or imply i t s endorsement, reconnerdation, or favoring by the United Stiites Govermnt or any agency thereof o r i t s contractors or subcontractors.

Reference herein t o any speci f ic ccmnercial product, process, or service by

Printed i n the United States of America. To obtain copier. o f t h i s docunent, contact: WHC/BCS Docunent Control Services, P.O. Box 1970, Mailstop H6-08, Richland UA 99352, Phone ( 5 0 9 ) 372-2420; Fax (509 ) 376-4969.

>L >A'; A Release Stamp Release Approval Date

Approved for Public Release

A-6400-073 ( 1 0 / 9 5 ) GEF321

WHC-SD-WM-SEMP-004 RIEV . 0

SITE SYSTEMS ENGINEEIRING SYSTEMS ENGINEERING MANAGEMENT PLAN

CONTENTS

1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . 2.0 SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.0 MAJOR PRODUCTS FOR FISCAL YEAR 1996 . . . . . . . . . . . . . . . .

3.1 THE HANFORD SITE TECHNICAL BASELINE . . . . . . . . . . . . . 3.2 THE DRAFT HANFORD SITE CLEANUP SPECIFICATION . . . . . . . . 3.3 INTERFACE CONTROL DOCUMENTS . . . . . . . . . . . . . . . . .

3.3.1 I n t r o d u c t i o n . . . . . . . . . . . . . . . . . . . . . 2 3.3.2 H ie ra rchy o f Documents . . . . . . . . . . . . . . . . 5

3.4 SITE SYSTEMS ANALYSES . . . . . . . . . . . . . . . . . . . . 11 3.5 ISSUE RESOLUTION AND TRACKING . . . . . . . . . . . . . . . . 11

3.5.1 I n t r o d u c t i o n . . . . . . . . . . . . . . . . . . . . . 11 3.5.2 D e s c r i p t i o n o f Process Steps . . . . . . . . . . . . . 14 3.5.3 D e f i n i t i o n s . . . . . . . . . . . . . . . . . . . . . 17

3.6 SITEWIDE SYSTEMS ENGINEERING INTEGRATION GROUP . . . . . . . . 17

4.0 PERFORMANCE LOGIC AND SCHEDULE . . . . . . . . . . . . . . . . . . . 17

5.0 INTEGRATION OF HSTB WITH THE MYPP PROCESS . . 5.1 INTRODUCTION . . . . . . . . . . . . . . 5.2 TECHNICAL BASELINE . . . . . . . . . .

5.2.1 P r o j e c t Miss ion . . . . . . . . 5.2.2 P r o j e c t Technical Ob jec t i ves . . 5.2.3 Forecast ing Data . . . . . . . . 5.2.4 D r i v e r s . . . . . . . . . . . . 5.2.5 P r o j e c t L i f e -Cyc le Requirements 5.2.6 P r o j e c t Issues and Assumptions .

. . . . . . . . . . . 20

. . . . . . . . . . . 20 . . . . . . . . . . . 20

. . . . . . . . . . . 20 . . . . . . . . . . . 20

. . . . . . . . . . . 22

. . . . . . . . . . . 24

. . . . . . . . . . . 24

. . . . . . . . . . . 25

iii

WHC-SD-WM-SEMP-004 Rev . 0

LIST OF FIGURES

1 Hanford S i t e Cleanup S p e c i f i c a t i o n Development . . . . . . . . . . . . 4

2 Hanford S i t e I n t e r f a c e Document Hierarchy . . . . . . . . . . . . . . 6

3 Hanford System H ie ra rchy . . . . . . . . . . . . . . . . . . . . . . . 12

4 Issue Reso lu t i on Process . . . . . . . . . . . . . . . . . . . . . . . 13

5 FY 1996 S i t e Technica l I n t e g r a t i o n Logic . . . . . . . . . . . . . . . 18

6 Develop S i t e S p e c i f i c a t i o n . . . . . . . . . . . . . . . . . . . . . . 19

7 Mul t i -Year Program Planning Guidance . Techniical Basel ine . . . . . . 21

LIST OF TABLES

1 S i tew ide Systems Engineer ing P r o j e c t L i s t . . . . . . . . . . . . . . 3

2 Hanford S i t e Cleanup I n t e r f a c e Contro l Documcmt M a t r i x . . . . . . . . 7

3 P r o j e c t Hanford and I n t e r f a c e Data Elements . . . . . . . . . . . . . 8

i v

WHC-SD-WM-SEMP-004 Rev. 0

SITE SYSTEMS ENGINEERING SYSTEMS ENGINEERING MANAGEMENT PLAN

1 .O INTRODUCTION

The Site Systems Engineering Management Plan (SEMP) is the Westinghouse Hanford Company (WHC) implementation document for the Hanford Site Systems Engineering Pol icy, (RLPD 430.1) and Systems Engineering Criteria Document and Implementing Directive, (RLID 430.1). These documents define the U.S. Department of Energy (DOE), Richland Operations Office (RL) processes and products to be used at Hanford to implement the systems engineering process at the site level. They are included in Appendix A to this SEMP. describes the products being provided by the site systems engineering activity in fiscal year (FY) 1996 and the associated schedule. It also includes the procedural approach being taken by the site level systems engineering activity in the development of these products and the intended uses for the products in the integrated planning process in response to the DOE policy and implementing directives. Plan [MYPP] preparation described in the WHC Budget Formulation Manual . )

This SEMP

(See Use of Technical Baseline Data in the Multi-Year Program

2.0 SCOPE

The scope of the systems engineering process described in this SEMP is to define a set of activities and products to be used at the site level during FY 1996 or until the successful Project Hanford Management Contractor (PHMC) is onsite as a result of contract award from Request For Proposal DE-RP06-96RL13200. Following installation of the new contractor, a long-term set of systems engineering procedures and products will be defined for management of the Hanford Project. the systems engineering process and the specific tools used are determined by the project's management.

The extent to which each project applies

3.0 MAJOR PRODUCTS FOR FISCAL YEAR 1996

In response to RLPD/RLID 430.1, the site systems engineering organization is developing five major products.

3.1 THE HANFORD SITE TECHNICAL BASELINE

The Hanford Site Technical Baseline (HSTB) is the core of the systems engineering activity at the site level. of the Hanford Project. This description consists of functional elements down to a selected project level, as well as input-output data among these elements (including waste type data where it exists), requirements derived both from the top down strategic level and rolled up from the requirements that exist in

It contains a technical description

1


the FY 1996 MYPP documentation, and schedule data relevant to the functional elements. above information will be mapped.

number of inconsistencies and disconnects in it. These result in issues to be resolved as described in Section 3.5 below.

The HSTB also contains the Project Hanford structure into which the

Because the information in the HSTB is still evolving, there are a

3.2 THE DRAFT HANFORD SITE CLEANUP SPECIFICATION

The Hanford Site Cleanup Specification fo,rms the basis of agreement between RL and the Contractors on the technical performance requirements for execution of the Site mission. It also forms tlhe basis for the development of the lower level project requirements documents. specification will contain a requirements set diarived from the strategic level documentation allocated to a subset of the Projlect Hanford structure shown in Table 1. It will also contain a rolled-up set of requirements derived from the existing project MYPP's.

The structure of the site specification and its relationship to lower level requirements is shown in Figure 1.

In FY 1996 the site

3.3 INTERFACE CONTROL DOCUMENTS

3.3.1 In t roduct ion

and project boundaries. management tool to:

Interfaces exist where wastes, materials, and facilities cross function Interface Control Documents (ICDs) are used as a

Formally define and control interfaces; Identify inconsistencies in assumptions between Projects; Identify and track material and waste flow between Projects; Integrate inter-Project planning input to the MYPPs; Support the integration and validation of the HSTB; Improve management and cost effectiveness of Project designs relative to interfaces between Projects.

At Hanford, ICDs will be used to link the Projects that make up Project Hanford by defining the physical interactions between Projects, as well as the Project critical needs for services and infrastructure. specific definitions of waste and material flows so that sending and receiving Projects have a common understanding of material,..quantity, and timing. will also contain physical property information such as concentrations and size. This information will comprise an integrated technical view of the Site for management purposes.

ICDs will contain

They

2

W

Table 1. Sitewide Systems Engineering Project List. May 1, 1996

Tank Safety Issue Resolution

Tank Farms Operations

Tank Uaste Retrieval

Lou Level lank Uaste

High Level lank Uaste

Tar& MStO Storwe cnd Dispwal

HLU Interim Storage

LLU Storage and Disposat

Cs & Sr Capsule Disposit ion

Non-shaded projects interfaces defined.

S o l i d Yaste

I I

*epresent the level at which Sitewide Systems Engineering data will

TECHNOLOGY MANAGEMENT

TECHNOLOGY DEVELOPMENT

be collected and

Specification

P

Purpose

Requirements k7 Requirements

I I I \ Sys Definition

Site Level Definitions and Requirements

Funct Rqmts I 1 -

Technical

hysical Rqmts Ops Rqmts I D&DRqmts

High Level Project Deiifiiibiis

Solid Waste

B%0100.12

WHC-SD-WM-SEMP-004 RIEV. 0

3.3.2 Hie ra rchy o f Documents

accommodate t h i s , a h i e r a r c h i c a l s t r u c t u r e o f i n fo rma t ion has been developed as shown i n F igu re 2. Th i s h ie ra rchy o f In ter f ,ace Documents c o n s i s t s o f :

The amount o f i n t e r f a c e i n fo rma t ion f o r P r o j e c t Hanford i s enormous. To

1. 2. Memorandums o f Understanding (MOUs) 3. Phys ica l ICDs.

Hanford S i t e Cleanup I C D M a t r i x (Super ICD)

The Super I C D w i l l be developed by Si tewide Systems Engineer ing (SWSE). and Physica l ICDs w i l l be developed and mainta ined by t h e Hanford P r o j e c t s .

Super I C D . f u n c t i o n a l i n t e r f a c e s . MOUs s h a l l be developed f o r each o f t h e unshaded areas. Phys ica l ICDs w i l l be developed a t t h e I J ro jec ts ' d i s c r e t i o n .

3.3.2.1 Hanford S i t e Cleanup I n t e r f a c e Con t ro l Document M a t r i x (Super ICD). The Super I C D i s a management t o o l and framework f o r i d e n t i f y i n g and managing i n t e r f a c e s f o r P r o j e c t Hanford. It i s a S i t e l e v e l index o f f u n c t i o n a l i n t e r f a c e s (da ta elements) as de f i ned i n the HSTB and i t p rov ides a m a t r i x o f da ta elements between p r o j e c t s f o r t he l i f e - c y c l e o f t h e Hanford Cleanup Miss ion.

The Super ICD w i l l con ta in t h e f o l l o w i n g : I n t r o d u c t i o n , d e f i n i t i o n o f terms, Hanford P r o j e c t s N2 Diagrams, and Data Element I n t e r f a c e i n f o r m a t i o n . For each ex te rna l and i n t e r n a l i n t e r f a c e (data element), t h e i n f o r m a t i o n descr ibed i n Table 1 w i l l be c o l l e c t e d .

MOUs

Table 2 con ta ins t h e minimum i n f o r m a t i o n t h a t w i l l be conta ined i n t h e Table 3 con ta ins the pr imary data elements and Pro jec ts t h a t have

The m a t r i x shows where MOUs are r e q u i r e d between Pro jec ts .

SWSE w i l l generate t h e t a b l e s o f i n fo rma t ion f o r t h e Super I C D from the The P r o j e c t rep resen ta t i ves are respons ib le f o r p r o v i d i n g the HSTB database.

requested i n fo rma t ion , rev iew ing t h e HSTB outputs , and ma in ta in ing t h e i n f o r m a t i o n c u r r e n t v i a change c o n t r o l .

3.3.2.2 Hanford S i t e Memorandums o f Understanding (MOUs). document t h e i n t e r f a c e agreements between Pro jec ts . Each f u n c t i o n a l i n t e r f a c e between P r o j e c t s s h a l l be documented by a MOU.

The P r o j e c t s are respons ib le f o r w r i t i n g MOUs accord ing t o t h e g u i d e l i n e s conta ined i n t h e e x i s t i n g Systems Engineering procedures. A "Graded Approach" should be used when implementing these procedures. general p r i n c i p l e t o fo l l ow i s t h a t t h e MOUs should be i n i t i a t e d by the sending P r o j e c t .

3.3.2.3 Hanford S i t e Phys ica l I n t e r f a c e .Controll Documents (Phys ica l ICDs). The Physica l ICDs are used t o document the phys l ca l implementation o f t h e i n te r face . fee l i s necessary t o e f f e c t i v e l y manage t h e f u n c t i o n a l i n t e r f a c e s . Phys ica l ICDs should be prepared wherever the P ro jec ts decide they are needed.

MOUs are used t o

The

These ICDs p rov ide the most d e t a i l e d i n f o r m a t i o n t h a t t h e P ro jec ts

5

i

Understanding - Physical

Interface Control

Documents

8960100.26

Super Interface Control

Document

I nl

1,

-2 a

Memorandum

Understanding

0 0

S e m 3 rt

n

- Memorandum

Introduction Definition of terms N2 Diagrams

* Data Element Information

I

Physical Interface Control

Documents

0

WHC-SO-WM-SEMP-004 R'ev. 0

IDENTIFIER

DESCRIPTION

TYPE

MANAGER

RECEIVING PROJECT

UBS #

This i s the unique naming idlenti f ier assigned t o the data element (e.g., Tank Uaste, Sol id Uaste)

This i s a descript ion of the Data Element

This f i e l d categorizes the date element. a function that i s performed by same colrponent wi th in a Project. Data e l m n t types include: Control, I n p l t , Output, o r Mechanism.

The nam of the Primary Data Element Manager. Program manager for the receiving Project

Receiving Project name frun Project Hanford r e p r t

Project UBS nlrnber that covers uork associated with t h i s data element

Data elements enter or e x i t

This i s t y p i c a l l y the

POINTS OF CONTACT (RL and Contractor)

DECOMPOSITION

TABLES

MW #

SENDING PROJECT

UBS #

POINTS OF CONTACT (RL and Contractor)

START AND F I N I S H DATE

VALUE

CONTEXT

I d e n t i f i e s other data elements that t h i s data element decomposes t o (e.g., Pretreated Uaste decorposes t o Pretreated LLU f o r I m b i l i z a t i o n and Pretreated HLU f o r l m b i l i z a t i o n ) .

The data element table provides a tabular format t o show the Function, Project, MW, and ICD relat ionships t o a data element. Table 1.1 i s an example data element table.

The nurber and t i t l e of the IUW that covers t h i s data element

The individuals u i t h i n an organization that coordinate the interfaces and information exchanges. Contractor Cognizant Engineer

Sending Project name frun Project Hanford report

Project UBS nunber that covers work associated with t h i s data element

The individual wi th in an organization that coordinates the interfaces and information exchanges. Contractor Cognizant Engineer

The year the data element s t a r t s being transferred and the year the data e l m n t s stops being transferred.

I d e n t i f i e s m i n i m , mean, and m a x i m values f o r the data element.

Ident i f ies references t o higher level data element that t h i s data element i s a consti tuent o f (e.g., Pretreated LLU for Imnobil izat ion i s a constituent o f Pretreated Uaste)

Typical ly the DOE monitor and the

TypicalLy the DOE monitor and the

7

Table 3 . P r o j e c t Hanford and I n t e r f a c e Data Elements.

=E I c) I

Tanks I VI PilIYL Building P F SYrvoit i l re snd

.Mainterawe

0 0 P

0


The P r o j e c t s are respons ib le f o r w r i t i n g Phys ica l ICDs accord ing t o t h e guide1 ines con ta ined i n t h e e x i s t i n g Systems Engineer ing procedures. A "Graded Approach" should be used when implementing these procedures. genera l p r i n c i p l e t o f o l l o w i s t h a t t he Phys ica l . ICDs should be i n i t i a t e d by t h e sending P r o j e c t .

The

3.4 SITE SYSTEMS ANALYSES

The S i t e Systems Analyses (SSA) i s a dynaimic s i m u l a t i o n o f t h e HSTB f o r I t adds t h e elements o f t ime t h e complete l i f e - c y c l e o f t he cleanup miss ion.

and resource in terdependencies t o t h e s t a t i c i n fo rma t ion i n t h e HSTB. used t o v e r i f y t h a t t h e HSTB i s v i a b l e i n t h a t c a p a b i l i t i e s and f a c i l i t i e s are a v a i l a b l e when needed and can handle t h e m a t e r i a l s needed i n t h e t ime requ i red . It a l s o v e r i f i e s the i n t e r f a c e s and other i n f o r m a t i o n i n t h e HSTB. The SSA w i l l be developed f o r t h e elements show8n i n F igu re 3 . As w i t h o t h e r p o r t i o n s o f t h e s i t e systems engineer ing a c t i v i t i e s i ncons is tenc ies i d e n t i f i e d i n t h e SSA w i l l r e s u l t i n issues t o be reso lved by t h e a f f e c t e d programs.

It i s

3.5 ISSUE RESOLUTION AND TRACKING

3.5.1 I n t r o d u c t i o n

and p r i o r i t i z a t i o n o f issues i d e n t i f i e d through the systems engineer ing process descr ibed i n t h i s document, as w e l l as issues i d e n t i f i e d through o t h e r p lann ing a c t i v i t i e s a t Hanford.

The cleanup miss ion a t Hanford i s very l a r g e and complex and t h e r e are a number o f obs tac les t h a t prevent Hanford from accomplishing t h e miss ion. These obstac les, c a l l e d issues, c u t across Hanford P ro jec ts and Serv ices, as w e l l as o t h e r DOE s i t e s . Whether the issues are s imple o r complex, t h e r e must be a c o n s i s t e n t and systemat ic process f o r r e s o l v i n g them. F igu re 4 shows t h e approach t h a t w i l l be used by t h e Si tewide Systems Engineer ing I n t e g r a t i o n Group (SWSEIG) t o t r a c k s i t e - l e v e l issues.

requi rements and p lann ing assumptions, omission:; i n p r o j e c t o r s e r v i c e basel ines, o r i n t e r f a c e c o m p a t i b i l i t y issues. Th is process w i l l be used t o r e s o l v e issues ( f i n a l dec i s ions ) o r e s t a b l i s h p lann ing assumptions ( i n t e r i m dec is ions ) assoc iated w i t h issues t h a t impact more than one major p r o j e c t o r se rv i ce . A l i m i t e d , s e l e c t number o f t echn ica l issues t h a t are n o t cross- c u t t i n g may be repo r ted on the Si tewide Issue Resolut ion Status Report (R isk Management L i s t [RML]). T y p i c a l l y , subord inate r i s k s and issues w i l l be i d e n t i f i e d and managed by t h e i n d i v i d u a l P r o j e c t o r Serv ice as necessary.

S i g n i f i c a n t o r c ross -cu t t i ng issues t h a t cannot be reso lved a t t h e P r o j e c t o r Se rv i ce l e v e l s h a l l be e leva ted t o the S i t e Management Board (SMB) f o r r e s o l u t i o n .

The i ssue r e s o l u t i o n and t r a c k i n g process prov ides a t o o l f o r t r a c k i n g

The focus o f SWSE i ssue r e s o l u t i o n i s on c o n f l i c t s o r d i s c o n t i n u i t i e s i n

11

Hantord Clnanup Syatem I

#

.

'

0 Major Sys tems -- Sys tems

S u b s y s t e m s

1 1 1

Solid Waste Remedlatlon System

Environmental Remediation System

Liquid Effluent System

8960100.16

12

0

> W a

* 0 0 I n E I v) I

0 v) I u I 3

T A

I I I I I I I ! I I I

I

i


3.5 .2 D e s c r i p t i o n o f Process Steps

F igu re 4 shows a step-by-step process f o r r e s o l v i n g t h e issues. The con ten ts o f each s tep w i l l vary w i t h t h e complex i ty o f t h e issue. The shaded steps are t h e r e s p o n s i b i l i t y o f systems engineer ing a t t h e approp r ia te l e v e l . The f o l l o w i n g sec t i ons desc r ibe each step.

3.5 .2 .1 I d e n t i f y Issue. There are severa l sources o f issues t h a t a f f e c t t h e HSTB and they a re i d e n t i f i e d i n many ways. are:

Some t y p i c a l sources o f issues

SWSE, Hanford S i t e I n t e g r a t e d Schedule, MYPPs, Base1 i n e Environmental Management Report, Hanford S t r a t e g i c Plan, Stakeholders, and Pro jec ts . As SWSE data i s developed and analyzed by P r o j e c t s o r Services, t h e SWSEIG, SWSE personnel, P lanning and I n t e g r a t i o n D i v i s i o n personnel, and others, issues r e q u i r i n g r e s o l u t i o n w i l l be i d e n t i f i e d . These may i n c l u d e issues impact ing m u l t i p l e P ro jec ts o r Serv ices o r an i ssue t h a t has a major impact on a s i n g l e P r o j e c t o r Serv ice.

Dur ing t h i s s tep t h e source o f t h e i ssue i s i d e n t i f i e d and t h e i ssue i s

1. Land Use 2. M a t e r i a l D i s p o s i t i o n 3. Newly rece ived o f f s i t e waste 4. Other s i t e miss ions.

Land Use and M a t e r i a l D i s p o s i t i o n ca tegor ies are f u r t h e r d i v i d e d i n t o

ca tegor i zed . A t t h e s i t e l e v e l t h e r e are f o u r major ca tegor ies o f issues.

sub-categories t h a t are a l i gned w i t h the Hanforld P r o j e c t s t o ensure proper assignment o f r e s p o n s i b i l i t i e s .

Th i s i s use fu l because i f a top - leve l i ssue i s inot reso lved and i s f a i r l y f l u i d , r e s o l u t i o n o f l ower - l eve l issues i s more d i f f i c u l t .

3.5 .2 .2 Def ine and P r i o r i t i z e Issue. A c l e a r ( d e f i n i t i o n o f t h e i ssue i s e s s e n t i a l t o develop the r e s o l u t i o n requirements. The d e f i n i t i o n s h a l l i n c l u d e a concise statement o f t he issue, background t h a t c rea ted t h e issue, r e s o l u t i o n requirements, and requ i red dec i s ion . The ex ten t and p o t e n t i a l s e v e r i t y of consequences r e l a t e d t o the i ssue slhall be def ined. programmatic, cos t , sa fe ty , and o the r impacts w i l l be descr ibed. Based upon t h e programmatic and cos t impacts, t he p r i o r i t y and t i m i n g f o r t h e i ssue r e s o l u t i o n w i l l be de f i ned .

The SWSE group w i l l determine i f t h e issuia i s s i g n i f i c a n t enough t o i n c l u d e i n t h e t r a c k i n g system and what l e v e l o f t r a c k i n g i s app rop r ia te .

3.5 .2 .3 Define Ad hoc I ssue Reso lu t i on Team. 'The owner, champion, and a f f e c t e d s i t e P r o j e c t s o r Serv ices w i l l be i d e n t i f i e d by t h e SWSEIG and inc luded i n t h e ad hoc i ssue r e s o l u t i o n team. 'The P r o j e c t o r Se rv i ce t h a t takes t h e l e a d f o r t h e r e s o l u t i o n w i l l ass ign a "champion" who w i l l be respons ib le f o r t h e i ssue r e s o l u t i o n and c losu re . team leader and i s respons ib le f o r i n v o l v i n g the c r o s s - c u t t i n g P r o j e c t s o r

The ca tegor ies p rov ide a h ie ra rchy framewjork f o r i ssue p r i o r i t i z a t i o n .

Technica l ,

The champion i s t h e ad hoc

14


Serv ices t h a t are impacted by the issue. members o f t h e ad hoc team w i l l be made t o the SWSEIG.

o rgan iza t i on (s ) , o t h e r a f f e c t e d p r o j e c t ( s ) rep resen ta t i ves , SWSE rep resen ta t i ve , and technology development rep resen ta t i ve . Th is team w i l l be respons ib le fo r : 1) ass ign ing a p r i o r i t y t o t h e issue, based upon es tab l i shed c r i t e r i a ; 2) p repar ing a dec i s ion package f o r t h e dec i s ion maker, and 3 ) p r o v i d i n g a d d i t i o n a l i n fo rma t ion i f requestesd by t h e d e c i s i o n maker. Each ad hoc team w i l l be dissembled a f t e r t h e dec i s ion i s made and implemented.

3 .5 .2 .4 Mon i to r I ssue Resolut ion. SWSE w i l l mon i to r t h e i ssue r e s o l u t i o n work us ing t h e RML. month ly s t a t u s r e p o r t on t h e c r i t i c a l issues w i l l be prov ided t o t h e SMB.

3 .5 .2 .5 Risk Management L i s t . The Si tewide Issue Reso lu t i on Status Report (RML) w i l l be mainta ined as p a r t o f t h e HSTB. The l i s t w i l l be p r i n t e d from t h e database on an as-needed bas i s . The HSTB i s mainta ined under c o n f i g u r a t i o n c o n t r o l i n accordance w i t h the gu id ing procedure. by SWSE as issues are added, changed, o r completed. RML a t t h e s i t e and P r o j e c t i n t e r f a c e l e v e l s . ma in ta in t h e i r own RML f o r i n t e r n a l issues.

t h e s t a t u s o f each issue. The m a t r i x inc ludes i n fo rma t ion on t h e p r i o r i t y ( impacts) , champion, owner, due date, and s ta tus o f t h e issues. The RML may c o n t a i n two l e v e l s o f issues: t he C r i t i c a l RML, and t h e RML. The C r i t i c a l RML w i l l be sent t o t h e RL SMB monthly w i t h s i g n i f i c a n t changes o r de l i nquenc ies noted.

3 .5 .2 .6 Mod i f y Hanford S i t e Technica l Basel ine. When a d e c i s i o n i s made, t h e implementat ion i nc ludes p repar ing a change request t o t h e HSTB. Completed r e s o l u t i o n s w i l l be c a r r i e d on the RML u n t i l t he HSTB i s mod i f i ed w i t h an approved change request . The champion i s respons ib le f o r p repar ing t h e change request and g e t t i n g i t approved and SWSE w i l l update the database from t h e change request .

3 .5 .2 .7 Decis ion. Issues are reso lved us ing t h e RL dec i s ion management process and t h e r e are m u l t i p l e rou tes t o a dec i s ion i n RL depending on t h e d e c i s i o n t o be made and t h e approp r ia te decision-making a u t h o r i t y o r a u t h o r i t i e s .

Requests t o change leadersh ip o r

Th is team w i l l c o n s i s t o f t h e champion(s) from t h e respons ib le

Progress w i l l be repo r ted r o u t i n e l y t o t h e SWSEIG and a

It i s updated SWSE w i l l ma in ta in t h e

Each P r o j e c t and Serv i ce may

The RML i s a m a t r i x ( t a b l e ) t h a t l i s t s a l l t he c u r r e n t issues and shows

The approach f o r SWSE-related dec i s ions i s n o t t o p r e s c r i b e s p e c i f i c procedures t o be fol lowed, b u t t o recognize the ex i s tence o f m u l t i p l e v a l i d paths and focus on t h e pa th t o o b t a i n a corporate rev iew o f a s p e c i f i c i ssue and d e c i s i o n where t h a t rev iew i s supported by a member o f t h e RL SMB.

schedule t o r e s o l v e t h e issue. The champion s h a l l prepare a package f o r t h e d e c i s i o n maker(s) t h a t w i l l i nc lude t h e d e f i n i t i o n , p r i o r i t y , and urgency o f t h e issue. A recommended dec is ion, based on an a l t e r n a t i v e ana lys i s s h a l l be inc luded.

The ad hoc team w i l l determine the approp r ia te course o f a c t i o n and

15


The decision maker(s) has the authority and responsibility to provide a clear decision. interim decision may be accepted with a closure date on the final decision. The decision maker(s) shall provide the reason for not reaching the final decision and support additional work required f'or that decision. always be a closure date based upon the pri0rit.y.

omissions within 60 days or at a minimum, develop an acceptable set of planning assumptions for the integrated baseline. To transform an issue and the associated planning assumption to a valid requirement, the ad hoc team should consider the management, technical, cost, schedule, and mission risks and their likelihood of occurrence in determining the course of action.

If the decision cannot be made within the required time, an

There must

The ad hoc team shall attempt to resolve (conflicts, discontinuities, or

The course of action and schedule determined by the ad hoc team shall be When an action plan reported to the SWSEIG and updated for tracking purposes.

is completed to resolve an issue, the results shall be reported to the SWSEIG and appropriate basel i ne change requests prepared.

include: The general types of decision-making processes and documentation in RL

f)

Manager or Deputy Manager decisions made within authority limits.

Assistant Managers or direct report:; to the Manager including: Project and Service Manager decisions made within authority limits.

Memorandums, letters, or policies documenting a decision made that are sent through concurrence to the appropriate authority for signature.

Contract decisions including basel ine changes documented through a concurrence chain to the appropriate authority for signature.

Agreements and decisions made between Assistant Managers or other direct reports to the Manager on issues within the individual or collective authorities.

Decisions made or recommended to a higher authority by RL SMB.

If a decision is made that affects the HSTB including technical basel ines with associated schedule information, requirements, planning assumptions, budgets, cost estimates, interface requirements, performance specifications, regulatory requirements, or other significant items it can be brought to the RL SMB for reconsideration if a member of the SMB sponsors the reconsideration item for the agenda. shall provide sufficient facts, analysis, and justification for the reconsiderati on discussion.

3.5.2.8 Implement Decision. The champian and owner are responsible to implement the decision and to communicate it with all of the affected organizations.

The proponents of the reconsideration

16


3 .5 .2 .9 Plan Required Analyses. d e c i s i o n and request a d d i t i o n a l analyses, t h e assigned o rgan iza t i on (champion) needs t o prepare a p l a n f o r t i m e l y complet ion o f t h e r e q u i r e d work. d e c i s i o n maker(s) must approve a d d i t i o n a l work and suppor t i t through a change i n workscope.

3 .5 .2 .10 Prepare Change Request. dec i s ion , t h e o r g a n i z a t i o n assigned t o per form ,addi t ional analyses w i l l p repare a change request and communicate i t t o the o t h e r a f f e c t e d o rgan iza t i ons .

I f the decisi lon maker(s) cannot reach a

The

Based upon t l i e p r i o r i t y o f t h e r e q u i r e d

3 .5 .3 D e f i n i t i o n s

'Issue It i s an obs tac le t h a t prevents a p r o j e c t from ach iev ing i t s goa ls . s tage o f t he p r o j e c t cyc le .

An example o f an i ssue i s t h e l a c k o f d e c i s i o n a t any

Charnoion

A person who i s assigned the r e s p o n s i b i l i t y t o o b t a i n r e s o l u t i o n o f an i ssue from the P r o j e c t t h a t i s a f f e c t e d t h e most from t h e i ssue . Th is person has t h e r e s p o n s i b i l i t y t o de f i ne , p r i o r i t i z e , and evaluate a l t e r n a t i v e s f o r r e s o l v i n g t h e issue.

Person who has t h e a u t h o r i t y t o make a d e c i s i o n f o r t h e r e s o l u t i o n o f an issue.

3.6 SITEWIDE SYSTEMS ENGINEERING INTEGRATION GROUP

The SWSEIG i s t h e o v e r a l l s t e e r i n a qrouD f o r t h e s i t e svstems eng ineer ing e f f o r t . RLID 430.1.

I t s a c t i v i t i e s are-descr;bttd i n Sect ion 2.5 o f

Membership c o n s i s t s o f DOE and c o n t r a c t o r rep resen ta t i ves o f t h e Hanford The SWSEIG meets weekly and serves as t h e p r i n c i p a l P r o j e c t s and con t rac to rs .

forum f o r o b t a i n i n g p r o j e c t support and ac t i ons f o r s p e c i f i c i tems e v o l v i n g from s i t e w i d e systems engineer ing a c t i v i t i e s . formed t o address r e q u i r e d ac t i ons as agreed t o by t h e SWSEIG membership.

I\s necessary, ad hoc teams are

4.0 PERFORMANCE LOGIC AND SCHEDULE

The l o g i c f o r FY 1996 a c t i v i t i e s t o develop and implement t h e products descr ibed above i s shown i n F igure 5. implement t h e l o g i c .

F igure 6 i s t h e associated schedule t o RL receives a weekly s ta tus o f these a c t i v i t i e s .

17


F igu re 5. FY 1996 S i t e Technical I n t e g r a t i o n Logic . Davdop S m Spdt lut Ion

Track Rasolutlon d 511. I.."..

18

"I. .,

WHC-SD-WM-SEMP-004 RE!v. 0

Figure 6. Develop Site Specification.

P

19


5.0 INTEGRATION OF HSTB WITH THE MYPP PROCESS

5.1 INTRODUCTION

I n o rde r f o r t h e i n fo rma t ion developed by t h e s i t e systems engineer ing a c t i v i t i e s t o be u s e f u l i t i s t o be i n t e g r a t e d w i t h t h e annual f i n a n c i a l p lann ing process as t e c h n i c a l i n p u t t o t h e MYPP. Th i s i n t e g r a t i o n process i s shown i n F igu re 7. The HSTB i s the source f o r s i t e l e v e l t e c h n i c a l base l i ne i n fo rma t ion . r e p o r t i n g requi rements as shown i n F igure 7 (e.g., RDS, BEMR). It forms t h e bas i s f o r t h e p r o j e c t l e v e l t echn ica l basel ines which w i l l con ta in t h e t e c h n i c a l da ta r e l e v a n t t o each i n d i v i d u a l p r o j e c t . These t e c h n i c a l base1 ines w i l l be r e v i s e d and mainta ined by making changes t o t h e HSTB from which they are de r i ved . t e c h n i c a l base l i nes w i l l be t h e bases f o r t he techn ica l content o f t h e MOUs and ICDs descr ibed i n Sect ion 3.3. The techn ica l con ten t o f t h i s i n f o r m a t i o n i s descr ibed i n Sec t i on 5.2 below.

I t has the p o t e n t i a l t o be used t o support t h e numerous

I n a d d i t i o n t h e q u a n t i t a t i v e data conta ined i n these p r o j e c t

5.2 TECHNICAL BASELINE

The t e c h n i c a l base l i ne descr ibes t h e work t o be accomplished and t h e t e c h n i c a l standards t h a t govern the work. The HSTB w i l l be used t o p rov ide t h e f o l l o w i n g i n f o r m a t i o n i n the P r o j e c t Technical Basel ine s e c t i o n o f t h e MYPP: 1) P r o j e c t Miss ion, 2) P r o j e c t Technical Object ives, 3) Summary Level Forecast ing Data (waste type, nuc lea r ma te r ia l , f a c i l i t y and i n f r a s t r u c t u r e needs), 4) D r i v e r s (key miss ion and regu la to ry ) , 5) P r o j e c t L i f e -Cyc le Requirements, and 6 ) P r o j e c t Issues and Assumptions.

5.2.1 P r o j e c t M iss ion

Th is s e c t i o n con ta ins a n a r r a t i v e d e s c r i p t i o n o f t h e end r e s u l t ( s ) o r end s t a t e t h a t t h e P r o j e c t w i l l achieve, supported by t h e pr imary p r o j e c t r e s p o n s i b i l i t i e s . It r e f l e c t s t h e P r o j e c t s ' c o n t r i b u t i o n t o DOE'S miss ion a t t he Hanford S i t e , as descr ibed i n the M iss ion D i r e c t i o n Document (MDD) and t h e Hanford S i t e Cleanup S p e c i f i c a t i o n , as w e l l as i n c l u d i n g r e l a t i o n s t o o t h e r P ro jec ts , as descr ibed i n t h e ICDs. Th is forms the bas i s f o r d e f i n i n g i n te rmed ia te products and sequence o f events t o achieve d e s i r e d r e s u l t s . Where t h e f i n a l c o n d i t i o n s are n o t complete ly diaveloped o r understood, s p e c i f i c a c t i v i t i e s are i d e n t i f i e d t h a t w i l l be accomplished t o d e f i n e these f i n a l c o n d i t i o n s .

5.2.2 P r o j e c t Technica l Ob jec t i ves

Hanford S i t e P r o j e c t (HSP) and MDD, suppor t ing the bas i s f o r ex i s tence o f t he P ro jec t , a re c l e a r l y l i n k e d t o the P r o j e c t o b j e c t i v e s and performance measures.

Each MYPP w i l l ensure t h a t t he s p e c i f i c goals and s t r a t e g i e s o f t h e

20

N c.

i

Activity D&& Sheet

Sobmitfal Activity Data

Sheet Call u d

/ RiskData

Sheet Call ,’ Submiff& Risk Data Sh@&

Strategic Analyses

L I

Technical Baseline

. Fy WiPPE * P r o w ICDs . PropciMOUs

Approved Change Document

Risk Management

I .?:A- ,.,:a- I -11c W V I U C :

- Objectives . Forecasting Data Drivers

* Life Cyda Requirements 9 Issues . Assumptions

Multi-Year

Guidance Policy/Process

Related Direction - Program ‘Ian

* Technical Data Call . ICD Format . ICD Data Needs

Multi-Year Multi-Year Program Plan Program Plan Preparation - Workshops - Technical Baseline ~ Hanford Site Integrated

Schedule - CostEstimata

New Technical Baseline Information

Program Plan

B960100.18b

WHC-SD-WM-SEMP-004 R e v . 0

The s i g n i f i c a n t goals, end p o i n t s , o r c o n d i t i o n s t o be achieved i n accompl ish ing t h e P r o j e c t miss ion s h a l l be i d e n t i f i e d . Th is s h a l l i n c l u d e general and s p e c i f i c ob jec t i ves , de l i ve rab les , o r a c t i v i t i e s t h a t are e s s e n t i a l t o t h e P r o j e c t miss ion. Th is w i l l p rov ide an overview o f t h e a c t i v i t i e s and d e l i v e r a b l e s t h a t are conta ined i n p r o j e c t schedules. p r o j e c t o b j e c t i v e s a re n o t c lea r , then the MYPP techn ica l l o g i c , suppor t i ng schedules, and c o s t es t ima te s h a l l i nc lude a c t i v i t i e s t h a t l a y o u t a p l a n f o r d e f i n i t i o n o f t h e end o b j e c t i v e s and requirements.

I f t h e

5.2.3 Fo recas t i ng Data

The P r o j e c t i n p u t s and outputs (wastes and nuc lea r m a t e r i a l s ) s h a l l be i d e n t i f i e d and descr ibed on Stream In fo rma t ion Sheets. The P r o j e c t f a c i l i t i e s w i l l be t racked v i a F a c i l i t y I n fo rma t ion Sheets and t h e P r o j e c t i n f r a s t r u c t u r e needs w i l l be i d e n t i f i e d and descr ibed on 1nfra:;tructure Needs Sheets.

Each I n f o r m a t i o n Sheet s h a l l be completed f o r t he e n t i r e l i f e - c y c l e o f each f a c i l i t y and p r o j e c t by the HSP MYPP po in t - -o f - con tac t .

5.2.3.1 Waste Type Data ( S o l i d Waste, Tank Waste, L iquid E f f l u e n t s , Specia l Case Waste). Waste i nven to ry and volume p r o j e c t i o n data are an i n t e g r a l p a r t o f t h e t e c h n i c a l bas i s f o r t he p lanning, schedulling, and budget ing process. The schedul ing and budget ing o f work f o r a p r o j e c t must r e f l e c t t h e p lans f o r d i s p o s i t i o n o f waste. The DOE, stakeholders, arid general p u b l i c expect waste d i s p o s i t i o n i n f o r m a t i o n t o be conta ined i n DOE r e p o r t s .

The waste t ype data i s used t o t r a c k the waste through generat ion, t r a n s f e r , r e c e i p t , s torage, and d i s p o s i t i o n i n an e f f i c i e n t and c o s t e f f e c t i v e manner. The f o l l o w i n g o b j e c t i v e s support t h i s goa l :

.

I d e n t i f y a l l waste i n v e n t o r i e s ons i te , -

- Each source o f e x i s t i n g waste w i t h i n a p r o j e c t s h a l l r e p o r t a c t i v i t i e s separate ly . A l l e x i s t i n g waste sources w i t h i n a p r o j e c t need t o be i n v e n t o r i e d f o r f u t u r e t rack ing , even though no near-term a c t i v i t i e s are planned f o r process ing a waste source.

Q u a n t i f y t h e volume o f waste,

Prepare annual p lans f o r waste d i s p o s i t i o n ,

Document t h e cha in o f custody f o r waste types between p r o j e c t s ,

Develop methods i n us ing waste data t o v a l i d a t e the bas i s f o r p r o j e c t and p r o j e c t p lanning,

Improve the i n t e g r a t i o n o f data between p r o j e c t s ,

Enhance waste da ta r e p o r t i n g format .

22


Th is i n f o r m a t i o n w i l l be used t o t r a c k t h e t r a n s f e r and d i s p o s i t i o n of waste between, n o t w i t h i n p r o j e c t s , w i t h t h e except ion o f t h e Tank Waste Remediation System (TWRS) P r o j e c t ( s i n g l e and double-shel l tanks) , which r e p o r t waste separa te l y .

5.2.3.2 Nuclear M a t e r i a l s (Specia l Nuclear Ma te r ia l s , Nuclear Fuel, Cesium capsules, S t ron t i um capsules). Nuclear m a t e r i a l s i nven to ry and volume p r o j e c t i o n da ta are an i n t e g r a l p a r t o f t h e techn ica l bas i s f o r t h e p lanning, scheduling, and budget ing process. p r o j e c t must r e f l e c t t he p lans f o r d i s p o s i t i o n o f nuc lea r m a t e r i a l s .

The nuc lea r m a t e r i a l s data i s used t o t r a c k the nuc lea r m a t e r i a l s through t r a n s f e r , r e c e i p t , storage, and d i s p o s i t i o n i n an e f f i c i e n t and c o s t e f f e c t i v e manner.

The schedul ing and budget ing o f work f o r a

The f o l l o w i n g o b j e c t i v e s support t h i s goal :

I d e n t i f y a l l nuc lea r m a t e r i a l s i n v e n t o r i e s o n s i t e , - - A l l e x i s t i n g nuc lear m a t e r i a l s sources w i t h i n a p r o j e c t need

Each source o f e x i s t i n g nuc lea r m a t e r i a l s w i t h i n a p r o j e c t s h a l l r e p o r t a c t i v i t i e s separate ly .

t o be i n v e n t o r i e d f o r f u t u r e t rack ing , even though no near- term a c t i v i t i e s are planned f o r process ing a nuc lea r m a t e r i a l s source.

Prepare annual p lans f o r nuc lea r m a t e r i a l s d i s p o s i t i o n ,

Q u a n t i f y t h e volume o f nuc lear m a t e r i a l s ,

Document t h e cha in o f custody f o r nuc lea r m a t e r i a l s between p r o j e c t s ,

Develop methods i n us ing nuc lear m a t e r i a l s data t o v a l i d a t e t h e bas i s f o r p r o j e c t and p r o j e c t p lanning,

Improve t h e i n t e g r a t i o n o f data between p r o j e c t s ,

Enhance nuc lea r m a t e r i a l s data r e p o r t i n g format .

Th i s i n fo rma t ion w i l l be used t o t r a c k t h e t r a n s f e r and d i s p o s i t i o n o f nuc lea r m a t e r i a l s between, n o t w i t h i n p r o j e c t s .

5.2.3.3 F a c i l i t i e s (Excess and Deact ivated) . I F a c i l i t y deac t i va t i on , decontaminat ion and decommissioning, and c losu re are an i n t e g r a l p a r t o f t h e t e c h n i c a l b a s i s f o r t h e p lanning, scheduling, and budget ing process. The schedul ing and budget ing o f work f o r a p r o j e c t must r e f l e c t t he p lans f o r d i s p o s i t i o n o f excess and deac t i va ted f a c i l i t i e , ; . f a c i l i t y s h a l l i n c l u d e t h e key events when a f a c i l i t y t r a n s i t i o n s through i t s l i f e - c y c l e (e.g., dec lared excess, when t h e f a c i l i t y i s deact ivated, when t h e f a c i l i t y i s decontaminated and decommissioned, and when t h e f a c i l i t y i s c losed) .

The schedule f o r each

when t h e f a c i l i t y begins operat ions, when t h e f a c i l i t y i s

23


The f a c i l i t y d a t a i s used t o t r a c k t h e f a c i l i t y through a c q u i s i t i o n , opera t ions and maintenance, d e a c t i v a t i o n , decontaminat ion and decommissioning, and c l o s u r e i n an e f f i c i e n t and cos t e f f e c t i v e manner. o b j e c t i v e s suppor t t h i s goal :

The f o l l o w i n g

. I d e n t i f y major f a c i l i t i e s w i t h i n each Pro jec t .

Prepare annual p lans f o r f a c i l i t y d i s p o s i t i o n .

Document t h e chain-of-custody f o r each f a c i l i t y between p r o j e c t s .

Develop methods i n us ing f a c i l i t y da ta t o v a l i d a t e the bas i s f o r p r o j e c t and p r o j e c t p lann ing .

Improve t h e i n t e g r a t i o n o f da ta between p r o j e c t s .

Enhance f a c i l i t y da ta r e p o r t i n g format

5.2.3.4 I n f r a s t r u c t u r e (e.g., Power, Steam, Walter, Roads, Ra i l road, S a n i t a r y Waste). p lace t o support t h e P r o j e c t s ' cleanup miss ions . Each p r o j e c t s h a l l i d e n t i f y t h e s e r v i c e s ( i n f r a s t r u c t u r e ) t h a t a re necessary t o achieve t h e p r o j e c t m i s s i on.

Another f o r e c a s t i n g goal i s t o ensure ;adequate i n f r a s t r u c t u r e i s i n

5.2 .4 D r i v e r s

i d e n t i f i e d . These s h a l l i nc lude Key and Regulatory Dr i ve rs .

5 . 2 . 4 . 1 Key D r i v e r s . The Pro jec t Miss ion Ob jec t ives s h a l l be d e r i v e d from and l i n k e d t o key documents (e.g., MDD) and t h e key documents s h a l l be l i s t e d i n t h e MYPPs.

5.2 .4 .2 Regu la to ry Dr i ve rs . The pr imary r e g u l a t i o n s t h a t govern execut ion o f t h e P r o j e c t Miss ion s h a l l be i d e n t i f i e d .

The miss ion o b j e c t i v e s and r e g u l a t i o n s thist d r i v e t h e P r o j e c t s h a l l be

5.2 .5 P r o j e c t L i f e - C y c l e Requirements

cyc le phase. Requirements s h a l l be i d e n t i f i e d and assigned f o r each Pro jec t l i f e -

I n a d d i t i o n general management requirements s h a l l be i d e n t i f i e d .

5 . 2 . 5 . 1 Management Requirements. Management requirements a re g e n e r a l l y key dates, P r o j e c t performance mi lestones, and i n t e r f a c e d e f i n i t i o n s . They may inc lude technology needs. requirements f o r f u t u r e technology t h a t i s necessary t o meet t h e p r o j e c t ' s mission, goals, and o b j e c t i v e s . I f technology needs are i d e n t i f i e d , ensure t h a t t h e r e i s a c l e a r l i n k a g e o f these needs w i t h programmatic techn ica l base1 i n e produc ts o r requirements.

5.2 .5 .2 A c q u i s i t i o n Requirements. Requirements t h a t must be met d u r i n g t h e a c q u i s i t i o n phase s h a l l be i d e n t i f i e d (e.g., Environmental Impact Statements, Resource Conservat ion and Recovery Act o f 1976 I:RCRA] Permi ts ) .

Th is g i ves t h e P ro jec t an a r e a t o i d e n t i f y

24


5.2 .5 .3 Operat ions Requirements. The requirements t h a t must be s a t i s f i e d by t h e P r o j e c t s d u r i n g the operat ions phase s h a l l be i d e n t i f i e d (e.g., r e t r i e v e , t r e a t , s to re , and d ispose o f X m3 o f waste).

5.2.5.4 Maintenance Requirements. The maintenance requi rements s h a l l be i d e n t i f i e d , i n c l u d i n g avai 1 ab i 1 i t y and maintainiabi 1 i t y requirements.

5.2.5.5 D e a c t i v a t i o n Requirements. Requiremenlts t h a t must be s a t i s f i e d d u r i n g t h e d e a c t i v a t i o n phase s h a l l be i d e n t i f i e d (e.g., e s s e n t i a l s a f e t y systems must be i d e n t i f i e d and mainta ined opera t i ona l ) .

5.2 .5 .6 Decontamination and Deac t i va t i on Requirements. Requirements t h a t must be s a t i s f i e d d u r i n g t h e decontamination and d e a c t i v a t i o n phase s h a l l be i d e n t i f i e d (e.g., a l l r ad ionuc l i des must be renioved o r s t a b i l i z e d ) .

5.2 .6 P r o j e c t Issues and Assumptions

The issues t h a t must be reso lved by the P ro jec ts s h a l l be i d e n t i f i e d . These i n c l u d e P r o j e c t - s p e c i f i c issues, as w e l l as t h e S i t e l e v e l issues t h a t have been assigned t o the P r o j e c t f o r r e s o l u t i o n .

The assumptions t h a t are used as a bas i s f o r t h e development o f Object ives, Technica l Requirements, P r o j e c t Logic, P r o j e c t Schedule, and Cost Estimates s h a l l be documented. t o w i t h RL and are c u r r e n t l y i n p lace f o r p r o j e c t p lanning. s h a l l be t raceab le t o a s p e c i f i c requirement o r issue. The MDD, Hanford S i t e Cleanup S p e c i f i c a t i o n , and ICDs s h a l l be the s t a r t i n g p o i n t f o r p lann ing assumptions. The assumptions descr ibed i n the MYPP s h a l l i n c l u d e those conta ined i n t h e MDD, S i t e S p e c i f i c a t i o n , and t h e ICDs i n a d d i t i o n t o more d e t a i l e d assumptions.

I d e n t i f y key assumptions t h a t have been agreed A l l assumptions

25


APPENDIX A

RLPD 430.1 HANFORD SITE SYSTEMS ENGINEERING POLICY

A- 1

WHC-SD-WM-SEMP-004 Flev. 0

Department o f Energy Richland Operations O f f i c e

Number : RLPD 430.1 E f f e c t i v e Date: 01-31-96 Prepared by: Pa e: 1 o f 3

TITLE: HANFORD S I T E SYSTEMS ENGINEERING POLICY

A-2


1.0 PURPOSE

This directive establishes the policies for the application of systems engineering principles in defining and controlling the technical basis for accomplishing Hanford Work. This includes top-level technical definition and technical integration of project/services work for the Environmental Management mission conducted at the Hanford Site.

2.0 APPLICABILITY

This policy applies to all Hanford project and service workscopes and contractors involved in the site cleanup, environmental remediation, environmental restoration, facility deactivation, waste management activities, and sitewide services requiring facilities and physical infrastructure. This policy applies across the entire project/service life cycle (i .e. design, construction, test, operation and decommissioning). infrastructure/landlord services necessary to support PNNL.

For PNNL, the policy applies to I'NNL cleanup projects and the

3.0 POLICY

Systems engineering principles shall be used at the mission level and, as appropriate, at the project/services level such that the technical basis for work is defensible, traceable and controlled. The overview for this approach as shown in Figure 1 will:

- Provide a high level technical baseline and associated schedule information with consistent traceability from the strategic plan to the projects/services.

Establish an iterative process to achieve a consistent top down set of integrated technical documents for site management purposes.

Produce useable results and products that support site-wide technical integration and physical systems management.

Bound the extent and scope of the sitewide systems engineering activity to: define and manage requirements, issues and assumptions, interface control between projects and infrastructure, waste stream datal, and provide a high level technically sound base1 ine for Project Hanfordl.

Require projects to continue the application of systems engineering principles to the extent required.

-

-

-

-

A-3


Department o f Energy Rich1 and Operations O f f i c e

Number: RLPD 4 3 0 . 1 E f f e c t i v e Date: 01-31-96 Prepared by: Pa e : 2 o f 3

TITLE: HANFORD S I T E SYSTEMS ENGINEERING POLICY

A-4

WHC-SD-WM-SEMP-004 R.ev. 0

- Establish, operate and maintain a Sitewide Systems Engineering Integration Group (SWSEIG) which will assist in identifying the data set and attributes used by sitewide systems engineering (SWSE), identification of impacts and issues, and interface management between major site projects.

Establish a process to identify, prioritize and facilitate the resolution of major sitewide issues to assure accomplishment of the Hanford clean-up mission.

-

Additional information on implementation of this pollicy can be found in the RLID 430.1 Systems Engineering Criteria and Document Implementiing Directive.

4.0 REFERENCES

1. DOE/RL-96-15 Hanford Management Plan, February 1996.

2. DOE Order 430.1, Life Cycle Asset Management Guide lo., Project Execution and Management Planning

5.0 RESPONSIBI LIT1 ES

Project/Services DOE and Contractor responsibilities (AMF, AMW, TWRS, AMT, AME, ESH)

Participates on SWSEIG with RL and contractor members. (DOE and Contractor) Participate in development of necessary and sufficient minimum data requiremen for the site technical specification and interface management (i .e Integrated Site Technical Baseline Document). (DOE and Contractor)

- Provide updates, continuously at the time base'line data is revised, to the required Sitewide Technical database. (Contractor)

- Assume management and resource responsibility for the resolution of identified SWSE issues. (DOE)

- - S

- Provide documentation for and perform project/service systems engineering at the level of detail appropriate for the dollar value of the project, complexity, sensitivity to changes, and impacts on other projects or services using DOE Order 430.1 on Life Cycle Asset Management and its Management Guides for guidance. (Contractor)

- Perform all detailed project/service analysis, all trade studies,all SWSE issue analysis, and initial change management of SWSE data. (Contractor)

- Assist in analysis of SWSE data for issues. (O'OE and Contractor)

A- 5


TITLE: HANFORD SITE SYSTEMS ENGINEERING POLICY

Department o f Energy Rich1 and Operations O f f i c e

Number: RLPD 430.1 E f f e c t i v e Date: 01-31-96 Prepared by: PMD Page: 3 o f 3

A-6


Site Management Board (SMB):

- Provide decisions requested on cross-cutting significant issues identified through SWSE that cannot be resolved by individual projects/services.

CFO/PID Responsibilities:

- Manage Hanford Strategic Planning process. (H,anford Strategic Plan, Mission Direction Document)

- Manage Site Baseline process. - Manage Sitewide Change Control process. - Manage site baseline planning and integration process and conduct analyses o f

sitewide data. - Assist SWSE process

Sitewide Systems Engineering (AMF/PMD) Responsibil iities:

- Manage Sitewide Systems Engineering Database '(SWSEDB) process. - Manage SWSE interface control process. - Manage SWSE issue resolution process. - Manage SWSE Integration Group. - Assist in analyses o f SWSE data for issues.

A- 7


RLID 430.1 SYSTEMS ENGINEERING CRITERIA DOCUMENT AND IMPLEMENTING DIRECTIVE

A-8



Number: R L I D 4 3 0 . 1 /I TITLE: SYSTEMS ENGINEERING CRITERIA DOCUMENT AND E f f e c t i v e Date: 01-31 -96 IMPLEMENTING DIRECTIVE Prepared by: PMD

A-9


1.0 PURPOSE I1 This RLID and associated attachments provides implementing direction for the Systems Engineering process at Hanford.

2.0 CANCELLATION

None.

3.0 APPLICABILITY

This direction applies to all Hanford project and service workscopes and contractors involved in the site cleanup, environmental remediation, environmental restoration, facility deactivation, waste management activities, and sitewide services requiring facilities and physical infrastructure. This direct.ive applies across the entire project/service life cycle (i.e. design, construction, test, operation and decommissioning). infrastructure/landlord services necessary to support PNNL.

For PNNL, the policy applies to F'NNL cleanup projects and the

4.0 REFERENCES

See Attachment A, Section 1.1 for reference information.

5.0 DEFINITIONS

5.1 ACRONYMS

All applicable acronyms are defined, as necessary, within the attached documents

5.2 DEFINITION OF TERMS

All terms and definitions are either obvious from context or given specifically within the attachments provided.

6.0 RESPONSIBILITIES

All roles and responsibilities are discussed in Section 2.0 of Attachment A.

A-IO


TITLE: SYSTEMS ENGINEERING CRITERIA DOCUMENT AND IMPLEMENTING DIRECTIVE


Number: R L I D 430.1 E f f e c t i v e Date: 01-31-96 Preoared bv: PMD

A-11

WHC-SO-WM-SEMP-004 Rev. 0

7.0 GENERAL CONTENT

A description of specific criteria and implementing requirements are provided in the attachments.

8.0 ATTACHMENTS

The following Attachments to this RLID provide implementing direction for the details ' associated with further definition and implementation of Systems Engineering Program a Hanford.

A - Attachment - Systems Engineering Criteria and Implementation Plan (11 pages, 4 Figures)

B - Attachment - Sitewide Systems Engineering Risk Management Plan (2 pages) C - Attachment - Sitewide Systems Engineering Decision Management Plan (1 page) D - Attachment - Sitewide Systems Engineering Information Management Plan (1

page)

A-I2


ATTACHMENT A SYSTEMS ENGINEERING CRITERIA AND IMPLEMENTATION PLAN

TABLE OF CONTENT!;

1.0 PRINCIPLES AND IMPLEMENTATION

1.1 BACKGROUND INFORMATION 1 . 2 SYSTEMS ENGINEERING PRINCIPLES AT HANFORD 1 . 3 IMPLEMENTATION

2.0 SITEWIDE SYSTEMS ENGINEERING MANAGEMENT

2.1 ORGANIZATIONAL STRUCTURE 2 . 2 OVERALL SYSTEMS ENGINEERING GOALS AND OBJECTIVES 2 . 3 SITEWIDE TECHNICAL INTEGRATION FRAMEWORK, DOCUMENT HIERARCHY, AND

PROCESS 2.3.1 ROLES AND RESPONSIBIL IT IES 2 . 3 . 2 INTEGRATION APPROACH 2 . 3 . 3 DOCUMENT HIERARCHY 2 . 3 . 4 HANFORD SYSTEMS ENGINEERING PROCESS

2 . 4 MAJOR DELIVERABLES 2 . 4 . 1 S I T E TECHNICAL BASELINE

2 . 4 . 1 . 1 S I T E TECHNICAL SPECIFICATION 2 .4 .2 .1 S I T E INTERFACE CONTROL DOCUMENTS

2 . 4 . 2 ISSUE IDENTIFICATION, TRACKING AND RESOLUTION

2 .5 .1 SWSEIG CHARTER 2 . 5 . 2 SWSEIG MEMBERSHIP 2 .5 .3 SWSEIG ROLES AND RESPONSIBIL IT IES

2.5 SITEWIDE SYSTEMS ENGINEERING INTEGRATION GROUP

3.0 REPORTING REQUIREMENTS

FIGURES :

F i g u r e 1:

F i g u r e 2 : S i t e w i d e S y s t e m s E n g i n e e r i n g T e c h n i c a l D o c u m e n t H i e r a r c h y

F i g u r e 3 :

S i t e w i d e S y s t e m s E n g i n e e r i n g F r a m e w o r k

S i t e w i d e S y s t e m s E n g i n e e r i n g P r o c e s s D o c u m e n t H i e r a r c h y

F i g u r e 4 : H a n f o r d S y s t e m s E n g i n e e r i n g (SE) P r o c e s s

A-13

WHC-SD-WM-SEMP-004 R~Pv. 0

1.0 PRINCIPLES AND IMPLEMENTATION

1.1 BACKGROUND INFORMATION

RL Hanford S i t e Management recognizes t h e need t o i n t e g r a t e t h e t e c h n i c a l workscope f o r t h e Hanford P ro jec t . The a p p l i c a t i o n o f systems eng ineer ing p r i n c i p l e s i s essen t ia l t o pl,an and p r i o r i t i z e t h e s i t e a c t i v i t i e s and cleanup schedule. The p r i n c i p l e s p rov ide a t e c h n i c a l management t o o l t o i n f l u e n c e and d e f i n e requirements f o r a l l programs and p r o j e c t s . t h e a p p l i c a t i o n o f systems engineer ing p r i n c i p l e s can s i g n i f i c a n t l y i n f l u e n c e t h e Hanford S t r a t e g i c Plan and t h e i n d i v i d u a l p r o j e c t s . I n genera l , i n t e g r a t e d work can be accomplished more e f f e c t i v e l y and w i t h more conf idence when t h e c o r r e c t scope i s be ing addressed.

I n 1992 t h e Defense Nuclear F a c i l i t i e s Safety Board (DNFSB) issued Recommendation 92-4 t o t h e Secretary o f Energy. concerns rega rd ing t h e techn ica l i n t e g r a t i o n a c t i v i t i e s f o r t h e Tank Waste R e t r i e v a l System and recommended t h a t DOE employ "systems engineer ing" t o reso lve these problems.

The i d e n t i f i c a t i o n and r e s o l u t i o n o f major issues through

DNFSB 92-4 addressed

I n response t o 92-4, RL committed f o r s i t ew ide systems engineer ing t o p rov ide a management p l a n and implementation p lan, i n c l u d i n g s p e c i f i c d e l i v e r a b l e s , which would desc r ibe the ac t i ons t o be taken a t t h e s i t e l e v e l t o manage techn ica l workscope d e f i n i t i o n , and i n t e g r a t i o n . Th is c r i t e r i a and implementation p lan, and t h e associated p o l i c y statement, f u l f i l l t h a t commitment.

A d d i t i o n a l background documents and guide'l i nes f o r " s i t e w i d e systems engineer ing" are conta ined i n several general re ferences.

While these references address, i n broad terms, t h e use o f "systems engineer ing" i n t h e p lann ing and execut ion o f t h e Hanford Miss ion, t hey c o n t a i n no d e t a i l e d s p e c i f i c requirements o r s p e c i f i c a l l y d e f i n e d "systems engineer ing" methodology. These major guidance documents are:

- DOE-HQ: DOE Order 430.1, L i f e Cycle Asset Management P r o j e c t

- T r i - P a r t y Agreement (TPA):

Management Guide - 10 (no s p e c i f i c requirements, gu ide on ly )

General comniitment t o i n t e g r a t i o n w i t h o u t s p e c i f i c d e t a i l s/mechanics.

- OMB: Recommends use o f systems engrneer ing w i t h o u t s p e c i f i c s rega rd ing methodology.

Because o f t h e guidance and general na tu re o f t he c u r r e n t l y a v a i l a b l e documentation on "systems engineer ing" , RI. has adopted systems eng ineer ing methods and a process which i s compat ib le w i t h t h e c u r r e n t Hanford Management Plan and the d i ve rse na tu re o f t he d i f f e r e n t t e c h n i c a l a c t i v i t i e s a t Hanford.

A-I4

WHC-SO-WM-SEMP-004 R~zv. 0

1.2 SYSTEMS ENGINEERING PRINCIPLES AT HANFORD

The fundamental p r i n c i p l e s f o r systems engineer ing a c t i v i t i e s a t Hanford are captured i n t h e f o l l o w i n g b u l l e t s :

System engineer ing p r i n c i p l e s are n o t a s u b s t i t u t e f o r good p r o j e c t management.

Because o f t h e d i ve rse elements and complex i ty o f t h e Hanford P ro jec t , t h e m u l t i t u d e o f p r e e x i s t i n g phys i ca l systems, and pre- e x i s t i n g agreements and processes d r i v i n g p r o j e c t / s e r v i c e s p lanning, textbook Systems Engineer ing processes w i l l n o t be u n i f o r m l y r e q u i r e d o r implemented across t h e e n t i r e s i t e .

S i tew ide Systems Engineering (SWSE) w i l l d e f i n e and manage requirements, issues, assumptions, imd i n t e r f a c e s f o r s i t e w i d e a c t i v i t i e s r e q u i r i n g phys i ca l f a c i l i t i e s and t h e boundary i npu ts /ou tpu ts requirements f o r pro,jects. A l l operable u n i t s are considered phys i ca l f a c i l i t i e s . It i s a framework f o r t h e p r o j e c t / s e r v i c e systems engineer ing (see F ig . 1 - Framework).

SWSE w i l l be l i m i t e d t o t h e h igh l e v e l s i t e techn ica l base l i ne w i t h nomina l l y 500 o r l e s s major t echn ica l and associated schedule i n f o r m a t i o n f o r t h e s i t e . SWSE data c o l l e c t i o n w i l l n o t be done lower than t h e major p r o j e c t / s e r v i c e l e v e l where s p e c i f i c respons ib le P r o j e c t Managers can be i d e n t i f i e d .

P ro jec t /Se rv i ce Systems Engineer ing w i l l be done by t h e p r o j e c t s and se rv i ces a t t h e l e v e l o f d e t a i l app rop r ia te f o r t h e d o l l a r va lue o f t he p r o j e c t , complexity, s e n s i t i v i t y t o changes, and impact on o t h e r p ro jec ts / se rv i ces . D e t a i l e d ana lys i s , a l l t r a d e s tud ies , and i n i t i a l change management o f SWSE da ta i s done a t t he p r o j e c t / s e r v i c e l e v e l . Management and i t s management guider; w i l l be u t i l i z e d as approp r ia te .

DOE Order 430.1 on L i f e Cycle Asset

System Engineer ing p r i n c i p l e s are a support system f o r development o f t h e base l i ne work p lans and budget submi t ta l s .

System Engineer ing scope w i l l be 1 i n i i t e d t o t h e Environmental Management phys i ca l p r o j e c t work and overhead/services r e q u i r i n g phys i ca l f a c i l i t i e s and i n f r a s t r u c t u r e .

A t P a c i f i c Northwest Nat ional Laboratory (PNNL) t h e r e q u i r e d System Engineer ing scope w i l l be l i m i t e d t o t h e Environmental Management M iss ion and the i n f r a s t r u c t u r e / l a n d l o r d se rv i ces necessary t o support o the r PNNL a c t i v i t i e s .

A-15


1.3

- System Engineer ing a p p l i c a t i o n s are no t :

- A p r o j e c t management system f o r cos t and schedule.

- A budget system: budget issues/priorities/schedules are a separate area fo r p r o j e c t s / s e r v i c e s and t h e RL Budget D i v i s i o n .

- A technology needs and development system: a t Hanford t h a t f u n c t i o n i s performed by the S i t e Technology Coord ina t i on Group (STCG).

A d e t a i l e d composite t o t a l s i t e systems engineer ing network i s n o t requ i red . A s i t ew ide systems enginjeering database w i l l be developed f o r t he s i t e l e v e l system d e s c r i p t i o n and mainta ined by SWSE. The p r i n c i p l e v e h i c l e f o r coo rd ina t i on o f t h i s i n f o r m a t i o n w i l l be t h e Si tewide Systems Engineer ing I n t e g r a t i o n Group (SWSEIG). Key phys i ca l i n t e r f a c e s lbetween p r o j e c t s and se rv i ces w i l l be i d e n t i f i e d through SWSE.

P ro jec ts /Serv i ces are n o t requ i red t o use t h e same sof tware o r l e v e l o f d e t a i l i n t h e i r a p p l i c a t i o n o f SE. P r o j e c t s and se rv i ces are r e q u i r e d t o be ab le t o i n t e r f a c e e l e c t r o n i c a l l y w i t h t h e SWSE da ta base f o r t h e t r a n s f e r and r e v i s i o n o f data. se rv i ces can implement the systems (engineering p r i n c i p l e s and c r i t e r i a as needed t o g e t t he r e s u l t s des i red f o r t h e p r o j e c t / s e r v i c e and the i n fo rma t ion r e q u i r e d f o r s i t e l e v e l systems engineer ing.

s tud ies , ana lys i s o f cos t savings, contingency ana lys i s , s i n g l e and mu l t i - a rea v u l n e r a b i l i t y ana lys i s , and i ssue r e s o l u t i o n , as requ i red .

- The s i t e w i d e systems engineer ing da ta w i l l be updated con t inuous ly through t h e change management proce:;s i n develop ing t h e work p lan, budgets, f und ing changes, and eva lua t i ons . Hard copies, i f requ i red , w i 11 be pub1 i shed p e r i o d i c a l 1 y .

IMPLEMENTATION

-

-

P r o j e c t s and

- Pro jec ts / se rv i ces w i l l per form s i n g l e and mu l t i - a rea t r a d e

The issuance o f t h e Hanford Systems Engineering P o l i c y and Implementing D i r e c t i v e s r e l e c t s t h e elements approved by DOE-RL S i t e Management Board on December 11, 1995, and f o r m a l l y implements these requirements.

A-16


2.0 SYSTEMS ENGINEERING MANAGEMENT

2.1 ORGANIZATIONAL STRUCTURE

The Hanford organizations involved in SWSE, technical integration and systems management include the following entities:

- DOE-RL Lead Organization for SWSE: AMF/PMD

- DOE-RL Lead Organization for Integration:

- Contractor Lead Organization: WHC Site Integration Group

- DOE-RL Projects/Programs: AMT, AMW, AME, AMF, ESH, TWRS

- Contractor Projects/Programs:

CFD/PID

As required to support and perform the DOE Projects/Programs involvements and systems engineering efforts.

Further details on roles and responsibilities is given in Section 2.3.

2.2 OVERALL SYSTEMS ENGINEERING GOALS AIND OBJECTIVES

The overall Goals and Objectives of the systems engineering effort are as follows:

- Produce a Hanford Site Technical Baseline that provides a consistent traceable linkage connecting strategic level documents to the project baseline documents. process will be used (i .e. bottom-up, top-down, issue identification).

Produce SWSE products and reslults that are useable and support projects and sitewide services. deliverables are given on Section 2.4.

* Requirements * Issues and assumptions * Interfaces Control between IProjects, Infrastructure * Waste Stream Data tracked ti2 the intra-project level

Projects/services utilizing systems engineering principles as necessary to develop meaningful, integrated baseline work plans .

An iterative

- Major products and

- Define and manage, at the SWSIE Level:

-

A-17


2.3 S I T M I D E TECHNICAL INTEGRATION FRAMEWORK, DOCUMENT HIERARCHY, AND PROCESS

2.3.1 ROLES AND RESPONSIBILITIES

Pro jec t /Se rv i ces DOE and Contractor R e s p o n s i b i l i t i e s (AMF, AMW, TWRS, AMT, AME, ESH):

- P a r t i c i p a t e s on SWSEIG w i t h RL and c o n t r a c t o r members. (DOE and Contractors)

- P a r t i c i p a t e i n development o f necessary and s u f f i c i e n t minimum data requirements f o r t h e s i t e t e c h n i c a l s p e c i f i c a t i o n and i n t e r f a c e management ( i .e I n t e g r a t e d S i t e Technical Base1 i n e Document). (DOE and Con t rac to rs )

- Prov ide updates, con t inuous ly a t t he t ime base l i ne data i s rev ised, t o t h e requ i red Si tewide Technical database. (Contractor)

- Assume management and resource r e s p o n s i b i l i t y f o r t h e r e s o l u t i o n o f i d e n t i f i e d SWSE issues. (DOE)

Prov ide documentation f o r and per form p r o j e c t / s e r v i c e systems engineer ing a t t h e l e v e l o f d e t a i l app rop r ia te f o r t h e d o l l a r va lue o f t h e p r o j e c t complex i ty , s e n s i t i v i t y t o changes, and impacts on o the r p r o j e c t s o r se rv i ces us ing DOE Order 430.1 on l i f e Cycle Asset Management and i t s Management Guides f o r guidance. (Con t rac to r )

- Perform a l l d e t a i l e d p r o j e c t / s e r v i c e ana lys i s , a l l t r a d e s t u d i e s , a l l SWSE i ssue ana lys i s , and i n i t i a l change management o f SWSE data. (Cointractor)

-

- A s s i s t i n ana lys i s o f SWSE data f o r issues. Con t rac to r )

(DOE and

CFO/PID R e s p o n s i b i l i t i e s :

- Manage Hanford S t r a t e g i c Planining process. (Hanford S t r a t e g i c Plan, Miss ion D i r e c t i o n Document)

- Manage S i t e Basel ine process.

- Manage Si tewide Change Contro l process.

- Manage s i t e base l i ne p lann ing and i n t e g r a t i o n process and conduct analyses o f s i t ew ide (data.

A-18


- A s s i s t SWSE process.

S i tew ide Systems Engineering (AMF/PMD) R e s p o n s i b i l i t i e s :

- Manage Si tewide Systems Engineer ing Database (SWSEDB) process.

- Manage SWSE i n t e r f a c e c o n t r o l process.

-

- Manage SWSE I n t e g r a t i o n Group.

-

Manage SWSE i ssue r e s o l u t i o n process.

A s s i s t i n ana lys i s o f SWSE data f o r issues.

S i t e Management Board (SMB):

- Prov ide dec i s ions requested on c r o s s - c u t t i n g o r s i g n i f i c a n t issues i d e n t i f i e d through SWSE t h a t cannot be reso lved i n accordance w i t h the SWSE Decis ion Management Plan i n Attachment C o f RLID 430.1.

2.3.2 INTEGRATION APPROACH

The Hanford Systems Engineering/Tecihnical I n t e g r a t i o n Process i s a combined e f f o r t where s i t ew ide supp,ort and l i n e o rgan iza t i ons f u n c t i o n as a team t o achieve t h e s i t e ob jec t i ves . The S i tew ide Systems Engineer ing (SWSE) f unc t i ons managed by AMF/PMD and t h e CFO/PID group p rov ide ana lys i s o f tlhe s i t e w i d e da ta and are s e r v i c e o rgan iza t i ons t o the S i t e I n t e g r a t o r o r l i n e customers. The SWSE and P I D e f f o r t s w i l l n o t assume l i n e a u t h o r i t y o r r e s p o n s i b i l i t y f o r t he a p p l i c a t i o n o f system engineer ing p r i n c i p l e s a t t h e program/pro ject l ieve l . SWSE and P I D w i l l p r o v i d e t h e "4-Cs": coo rd ina t i on , iconsol i d a t i o n , cons is tency, and consul t a t i o n .

The framework model f o r t he SWSE a c t i v i t i e s a t Hanford i s r e f l e c t e d i n F igu re 1.

The SWSE work a t RL w i l l focus on cap tu r ing and managing t h e boundary requi rements f o r s i t ew ide serv ices and t h e boundary i n p u t / o u t p u t requirements and assumptions f o r p r o j e c t s / s e r v i c e s . D e t a i l e d Systems Engineering w i l l b a done by t h e p r o j e c t s / s e r v i c e s a t t h e l e v e l o f d e t a i l app rop r ia te For t h e work, complex i ty , s e n s i t i v i t y t o changes and impact om o t h e r p r o j e c t s / s e r v i c e s (graded approach). change management i s done a t t he p r a j e c t / s e r v i c e l e v e l .

D e t a i l e d ana lys i s , t r a d e s tud ies , and i n i t i a l

A-19


2.3.3 DOCUMENT HIERARCHY

The Hanford technical document hierarchy is given in Figure 2. The key technical products of the sitewide technical integration effort are the Site Technical Baseline and,the site Technical Issues Management list. given in Figure 3.

2.3.4 HANFORO SYSTEMS ENGINEERING PROCESS

The Hanford Site Systems Engineering Process is summarized as follows (see Figure 4):

The SWSE process document hierarchy is

- The minimum practical data elements and definitions for the

- Specific physical performance requirements are noted at the sitewide and the project/service level. project/service defines its additional requirements through its own tailored SE or equivalent process. requirements might include sitewide services, design, construction, start-uppest and/or operational (e.g. S/RID), and decommi ssi oni ng/stabi 1 i zat i on, decontamination, and demo1 i tion requirements.

which includes systems enginesering principles, develop the raw data required for SWSE.

SWSE consolidates the data and includes appropriate site level physical performance requirments and interface data and sends information back to the projects/services and to PID for analysis.

SWSE effort is determined and revised as needed.

Each

These

- The projects/services, in performing their planning process

-

- The information is analyzed by the projects/services to verify the planning basis and by SWSE and PID for consistency of assumptions and baseline information. Cost savings opportunities and teclinical issues are identified.

- In a risk management/issues resolution process, SWSE and major project/service issues ,are identified. project/service and impacted parties are identified for an ad hoc issue resolution team. The issues are resolved through agreed planning assumptions or analysis to determine appropriate requirements.

Then a lead

- In a decision management process issues are resolved and the confirmed SWSE data is provided to SWSE and PID.

A-20

.-. .,


- I n an i t e r a t i v e process, t he p r o j e c t s / s e r v i c e s r e s o l v e issues and r e v i s e the SWSE data as needed. when the issues are reso lved through ana lys i s o r adopt ion o f an acceptable se t o f assumptions, s i t ew ide i n t e g r a t i o n has been achieved.

As t h e p r o j e c t s / s e r v i c e s con t inue w i t h work execut ion they implement base1 i n e change c o n t r o l , eva lua t i ons , and budget/funds management. w i l l be prov ided t o SWSE and P I D through t h e approp r ia te change c o n t r o l process as necessary.

SWSE w i l l con t i nuous ly update t h e SWSE database and make i t a v a i l a b l e i n e l e c t r o n i c form f o r rev iew /e tc .

I n any c y c l e

- Any changes t o t h e SWSE ou tpu ts

-

D e t a i l s o f SWSE d e l i v e r a b l e s are g i ven i n Sect ion 2.4.

2 .4 MAJOR DELIVERABLES

2 .4 .1 SITE TECHNICAL BASELINE

The s i t ew ide techn ica l document h ie ra rchy i s shown i n F igu re 2. Major d e l i v e r a b l e s are s p e c i f i c a l l y addressed i n t h e f o l l o w i n g t e x t .

The S i t e Technica l Basel ine i s a major product o f t h e s i t e w i d e systems i n t e g r a t i o n e f f o r t . The base l i ne i nc ludes t h e f o l l o w i n g :

- S i t e Technical S p e c i f i c a t i o n

- S i t e I n t e r f a c e Contro l Documents

S i tew ide Systems Engineering Products

(A) S i t e Technical S p e c i f i c a t i o n

Consol idated P ro jec t /Se rv i ces Phys ica l Performance Requirements/Assumptions * By p r o j e c t / s e r v i c e * S p e c i f i c phys i ca l performance requirements o f

Technica l Basel ine Elements * High l e v e l t y p i c a l l y l e s s than 500 a c t i v i t i e s by WBS.

Schedule In fo rma t ion * High l e v e l t y p i c a l l y l e s s than 500 a c t i v i t i e s by WBS.

s i t e / p r o j e c t / s e r v i c e s composite.

A-21


Consol idated I n t e r f a c e ( Input /Output ) Requirements * By WBS t o major sub-pro ject l e v e l as i d e n t i f i e d by SWSE. * Inc lude p o i n t s o f con tac t f o r c o n t r a c t o r and DOE f o r each

sub-pro ject and data element. * De f ine da ta elements o f i n p u t / o u t p u t i n f o r m a t i o n t o be

gathered. * De f ine P ro jec t /Se rv i ce "manager" f o r each da ta element. * De f ine c h a r a c t e r i s t i c s o f each data elements r e q u i r e d a t t he

minimum p r a c t i c a l l e v e l f o r t h e user o f t h e data. - Could be yes/no w i thou t q u a n t i f i c a t i o n . - Could be o n l y p r o j e c t e d change from e x i s t i n g l e v e l s . - Could be ac tua l q u a n t i t i e s and f u t u r e q u a n t i t i e s . - Could be ca tegor ies such as t ype o f waste, t ype o f

a n a l y t i c a l t e s t . - Waste stream data elements should i n c l u d e d i s p o s i t i o n

pa th even i f i n t e r n a l t o tlhe sub-pro ject . De f ine approp r ia te f u t u r e p r o j e c t i o n s f o r p lann ing es t ima te pe r iods matched t o economic l i f e o f asset /data element. - Current need. - 5 year and 20 year p r o j e c t i o n s f o r i n f r a s t r u c t u r e . - Known f u t u r e l a r g e needs l i k e tank waste v i t r i f i c a t i o n . De f ine q u a l i t y o f i n fo rma t ion f o r data element a t source o f need i n p u t . - Actual r e a l data. - Design est imate. - Knowledgeable guesstimate (SWAG). Report p r o v i d i n g consol idated s i t ew ide t o t a l s f o r needed da ta elements w i t h sub-repor ts by data element showing needs by sub-pro ject .

*

*

*

(6) SWSE I n t e r f a c e Contro l Documents

- Def ines SWSE i n t e r f a c e s

-

- Def ines c u r r e n t s t a t u s o f i n t e r f a c e

Defines P ro jec t /Se rv i ce "manager" o f i n t e r f a c e

Th is i n fo rma t ion w i l l comprise a i n t e g r a t e d t e c h n i c a l view o f t h e s i t e f o r s i t e management purposes. The S i t e Technica l Basel ine w i 11 be c o n t r o l 1 ed.

(C) S i tewide Issue Resolut ion S ta tus Report

- Def ines SWSE issues t o be reso lved

- Def ines P ro jec t /Se rv i ce w i t h lead r o l e t o manage r e s o l u t i o n o f t he i ssue

A-22


- Def ines schedule f o r r e s o l u t i o n

2.4.2 ISSUE IDENTIFICATION, TRACKING AND RESOLUTION

A l i s t o f SWSE major p r o j e c t t echn ica l issues w i l l be assembled as p a r t o f t h e s i t e techn ica l i n t e g r a t i o n and base l i ne p repara t i on workscope.

The issues w i l l be p laced i n a database and assigned t o the respons ib le p r o j e c t s / s e r v i c e s f o r r e s o l u t i o n .

SWSE w i l l t r a c k and r e p o r t a c t i o n p lans and s t a t u s on these SWSE and major t echn ica l issues. The DOE-RL S i t e Management Board w i l l be updated on a r o u t i n e bas i s .

A-23

WHC-SD-WM-SEMP-004 R I ~ v . 0

2.5 SITEWIDE SYSTEMS ENGINEERING INTEGRATION GROUP (SWSEIG)

2 . 5 . 1 SWSEIG CHARTER

Th is team s h a l l a s s i s t i n i d e n t i f y i n g the SWSE data sets , d e t a i l e d da ta a t t r i b u t e s , major t echn ica l issues and impacts, and major i n t e r f a c e s between s i t e p ro jec ts / se rv i ces .

2.5 .2 SWSEIG MEMBERSHIP

Th is team w i l l i nc lude key DOE-RL and Contractor p a r t i c i p a t i o n from each o f t h e f o l l o w i n g program/pro ject e n t i t i e s :

- TWRS, F a c i l i t y T r a n s i t i o n , Spent Nuclear Fuel , S o l i d Waste, L i q u i d Waste, L i q u i d E f f l u e n t , Environmental Res to ra t i on , S i t e I n f r a s t r u c t u r e , Program [n teg ra t i on , ES&H, Science & Technology, Regulatory Analys is , and A n a l y t i c a l Serv ices.

Changes t o the agreed t o membership, f o r whatever reasons, must be communicated t o PMD i n w r i t i n g by the respons ib le RL D i v i s i o n D i r e c t o r .

2.5 .3 SWSEIG ROLES AND RESPONSIBILITIES

DOE and Contractor Project /Servici? R e s p o n s i b i l i t i e s : - P a r t i c i p a t e i n SWSEIG.

- Serve as SWSE p o i n t o f con tac t f o r P r o j e c t and communicate SWSE i n fo rma t ion t o app rop r ia te p r o j e c t personnel i n c l u d i n g schedu'l e and budget groups.

- Represent P r o j e c t technica'l p o s i t i o n ( s ) .

- Prov ide i n p u t t o the S i t e Technical Basel ine database.

- A s s i s t i n d e f i n i t i o n o f SWSE i n t e r f a c e data s e t .

- A s s i s t i n i d e n t i f i c a t i o n o f SWSE issues and de te rm ina t ion of p ro jec ts l sys tems impacted by r e s o l u t i o n .

A s s i s t i n i d e n t i f i c a t i o n o f p r o j e c t / s e r v i c e w i t h l e a d r e s p o n s i b i l i t y f o r i ssue r e s o l u t i o n and i tems t o be considered.

Communicate and coo rd ina te needed pro ject /program response f o r i ssue r e s o l u t i o n .

Prov ide i n p u t and update d,ita t o e s t a b l i s h and ma in ta in SWSE da ta se ts ( s i t e s p e c i f i c a t i o n , ICD's, s i t e i ssues ) .

-

-

-

SWSE R e s p o n s i b i l i t i e s :

A-24


- Maintain SWSE data base (SWSEDB).

- Consolidate project/service input to the SWSEDB.

- Track resolution of SWSE and major project/service technical issues in database.

- Coordinate SWSEIG activities.

- Maintain data sets for SWSE Interface Control Documents ( ICDs) .

3.0 REPORTING REQUIRERENTS AMF/PID will establish the types and frequency of reporting requirements for SWSE work.

A-25


ATTACHMENT B SITEWIDE SYSTEMS ENGINEERING

RISK MANAGEMENT PLAN

1.0 RISK MANAGEMENT PLAN

The risk management approach for SWSE is an issues management process for issues that have major impact beyond a major project or service. general, the focus will be on resolving conflicts or discontinuities, omissions in project/service baselines, interface compatibilities, and conflicts in requirement/planning assumptions. and resolution process will be used to transform planning assumptions with major impacts into defined requirements. A limited, select number of technical issues that are not cross-cutting may be reported on the Sitewide Issue Resolution Status Report. Typically, subordinate risks/issues will be identified and managed by the individual project/service as necessary. Significant or cross cutting issues that cannot be resolved at the project/service level should be elevated to the Site Management Board (SMB) for resolution.

In

The issue identification

2.0 SWSE ISSUE IDENTIFICATION AND DEFINITION

As SWSE data is developed and analyzed by projects/services, the SWSEIG, SWSE personnel, PID personnel, and others, potential issues for resolution may be identified. multiple projects/services or major singlse project/service issues. When identified, the extent and potential severity o f consequences raised by the issue should be defined as well as th'e cross-cutting projects/services impacted. The SWSE grolup will determine if the issue is of significance enough to include in tlhe tracking system at any level. The tracking system and Sitewide Issue Resolution Status Report may contain two levels of issues: the Critical Issues Management List, and the Issues Management List.

These may include issues impacting

3.0 ISSUE RESOLUTION TEAM ASSIGNMENT

The SWSEIG group will make a preliminary ,assignment of a lead project/service and other affected projects/services to an ad hoc team for the resolution of the issue. members of the ad hoc team will be made to the SWSE group.

Requests to change leadership or

4.0 ISSUE RESOLUTION AND TRACKING

The ad hoc team will determine a course O F action and schedule to resolve the issue. The team shall attempt to resolve conflicts, discontinuities or omissions within 60 days or at a minimum, develop an acceptable set of planning assumptions foir the integrated baseline. an issue set up to transform a planning assumption to a valid requirement, the ad hoc team should consider the management, technical, cost, schedule, and mission risks and their likelihood of occurrence in determining the course of action. determined by the ad hoc team should be reported the SWSE group and

For

The course of action and schedule

A-26


updated f o r t r a c k i n g purposes. When an ac t ion p lan i s completed t o reso lve an issue , t h e r e s u l t s should be repor ted t o t h e SWSE group and appropr ia te base l ine change cont ro l processes u t i 1 i z e d as necessary. Issues a r e reso lved using t h e RL dec is ion management process.

A-27

WHC-SD-WM-SEMP-004 RIZV. 0

ATTACHMENT B

5.0 SITEWIDE ISSUE STATUS REPORTING

The S i tew ide Issue Resolut ion Status Report w i l l be mainta ined as an a d m i n i s t r a t i v e l y c o n t r o l l e d document by t h e SWSE group. It w i l l be updated e l e c t r o n i c a l l y by the SWSE group (3s add i t i ons , changes, o r completed r e s o l u t i o n s occur. Monthly i t w i l l be sent t o t h e RL S i t e Management Board w i t h s i g n i f i c a n t changes o r de l inquencies noted. Completed r e s o l u t i o n s w i l l be c a r r i e d on t h e r e p o r t u n t i l any r e q u i r e d change c o n t r o l process i s completed.

A-28

WHC-SD-WM-SEMP-004 R I ~ v . 0

ATTACHMENT C SITEWIDE SYSTEMS ENGINEERING

DECISION MANAGEMENT IPLAN

1.0 DECISION MANAGEMENT APPROACH

There a re m u l t i p l e rou tes t o a dec i s ion i n DOE-RL depending on t h e d e c i s i o n t o be made and t h e approp r ia te dec i s ion making a u t h o r i t y o r a u t h o r i t i e s . The approach f o r SWSE r e l a t e d dec i s ions i s n o t t o p r e s c r i b e s p e c i f i c procedure making processes t o be fo l lowed, b u t t o recognize t h e ex i s tence o f m u l t i p l e v a l i d paths and focus on t h e pa th t o o b t a i n a co rpo ra te rev iew o f a s p e c i f i c dec i s ion / i ssue where t h a t rev iew i s supported by a member o f t h e DOE-RL S i t e Management Board.

2.0 DOE-RL DECISION MAKING PROCESSES AND DOCUMENTATION

The genera l types o f dec i s ion making processes and documentation i n DOE-RL are:

a)

b)

c)

ManagerlDeputy Manager dec i s ions made w i t h i n a u t h o r i t y l i m i t s .

A s s i s t a n t Managers o r d i r e c t report:; t o t h e Manager i n c l u d i n g : P ro jec t /Se rv i ce Manager dec i s ions made w i t h i n a u t h o r i t y l i m i t s .

Memorandums/Letters/Pol i c i e s documenting a d e c i s i o n made t h a t are sent through concurrence t o the approp r ia te a u t h o r i t y f o r s igna tu re .

Contract dec i s ions i n c l u d i n g base l i ne changes documented through a concurrence chain t o t h e approp r ia te a u t h o r i t y f o r s igna tu re .

Agreements and dec i s ions made between Ass i s tan t Managers and/or o t h e r d i r e c t r e p o r t s t o the Manager on issues w i t h i n t h e i n d i v i d u a l o r c o l l e c t i v e a u t h o r i t i e s .

Decis ions made o r recommended t o a h ighe r a u t h o r i t y by t h e DOE-RL S i t e Management Board.

d)

e)

f )

A l l of t h e above rou tes t o a dec i s ion e f f e c t i n g SWSE i tems may be u t i 1 i zed.

3.0 DOE-RL RECONSIDERATION OF DECISIONS

I f a d e c i s i o n i s made t h a t a f f e c t s t h e SWSE database i n c l u d i n g t e c h n i c a l base1 ines w i t h associated schedule i n fo rma t ion , requi rements/p lanning assumptions, budgets/costs, i n t e r f a c e requirements, performance s p e c i f i c a t i o n s , r e g u l a t o r y requirements o r o the r s i g n i f i c a n t i tems i t can be brought t o t h e DOE-RL S i t e Management Board (SMB) f o r recons ide ra t i on i f a member o f t h e SMB sponsors t h e recons ide ra t i on i t e m f o r t h e agenda. The proponents o f t he recons ide ra t i on should p rov ide

A-29


sufficient facts, analysis, and justification for the reconsideration discussion.

.-

A-30

WHC-SD-WM-SEMP-004 Flev. 0

ATTACHMENT 0 SITEWIOE SYSTEMS ENGINEERING INFORMATION MANAGEMENT PLAN

1.0 INFORMATION MANAGEMENT APPROACH

The information management approach for SWSE is to provide maximum flexibility to the projects/services to define and implemenlt information management systems but retain the ability to electronically transfer SWSE data and update the SWSE database.

2.0 INFORHATION MANAGEMENT CRITERIA

The following information management criteria are established for SWSE:

a)

b)

A detailed composite total site systems engineering network is not required.

Projects/Services are not required to use the same software or level of detail in their application of systems engineering principles.

Projects/Services are required to be able to interface electronically with the SWSE database for the transfer and revision of data.

c)

A-31

To

D i s t r i b u t i o n

R. P. Angulo, Jr. K. B. B a i l e y S. S. Bath P. A. Baynes J. 0. Berger R. R. Bo r i sch S. T . Burnum R. F. Chr is tensen D. L. C l a r k R. L. Clendenon A. J. Colburn J. L. D a i l y I 1 C. R. DeLannoy S. E. D i e t e r l e W. T. Dixon S. C. Foelber H. L. Gar r i son T. M. Greager M. L. Gryg ie l R. L. G u i l l e n W. A. Hesser K. L. Hladek L. K. Hol ton, Jr. A. B. Hubbard 8. A. Jackson M. E. Johnson P. M. Knollmeyer D. C. Langs ta f f A. K. Lee S. S. Lowe D. P. Lund J. L. Madsen 6. W . McNair T. 0. Merk l i ng M. A. Norman T . J. Parkes 8. G. Place T. A. Quayle J. E. Rasmussen C. A. Rinne D. T. Romine V . L. Salad in S. E. Seeman M. J. Simpson S . T. Smith

From Page 1 o f %

H S I Date 05/01/96

A5- 11 H6-33 H6-33 H6-33 H6-34 R3-56 A2-45 K8-50 A5-55 HO- 12 A5-18 A5-58 A5-52 63-05 H6-21 HO-09 H6-33 T3-01 H6-33 A2-45 K6-51 T3-01 K9-73 H6-33 H6-33 63-21 S7-41 K8-50 H6-33 H6-29 R3-56 A4-35 P7-75 R3-09 61-75 A4-35 T3-01 H6-22 A5- 15 63-10 HO-18 K6-51 H6-33 K7-97 H6-33

Project Title/Work Order WHC-SD-WM-SEMP-004 Rev. 0

X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X

EDT No. 614718 ECN No.

A-6000-135 (01/93) UEF067

Name Text Text Only Attach./ EDT/ECN

MSlN With All Appendix Only Attach. Only

o f 2

R e v i s i o n 0

EDT-514718 'IHC-SD-WM-SEMP-004

DISTRIBUTION SHEET

J . 0. Thomson H6-33 x W. E. Toebe H6-22 x D. E. T r a d e r K8-50 x M. B. T r i p l e t t K9-09 x C . F. Wagner A2-45 x J . L. W a i t e H6-33 X S. H. W i s n e s s A5-18 X J . C. Womack R3-86 X C e n t r a l F i l e s A3-8P x

A-6000-135 (01/93) UEF067