Document title: Interface Management Plan · The objective of this Interface Management Plan (IMP) is to establish the Hanford Tank Waste Treatment and Immobilization Plant (WTP)

Document title: Interface Management Plan

Document number: 24590-WTP-PL-MG-01-001, Rev 10

Contract deliverable number: 1.4

Contract number: DE-AC27-01RV14136

Department: Project Management

Issue status: Approved All One System concurrence signatures on the following page are obtained prior to submission of this document for final concurrence and approval.

24590-WTP-PL-MG-01-001, Rev 10

Interface Management Plan

Page iii

History Sheet

Rev Date Reason for revision Revised by A 27 Jun 2001 Initial issue for ORP concurrence T Brown B 14 Dec 2001 Incorporate ORP concurrence T Brown 0 28 Jan 2002 Issued for implementation T Brown 1 01 Jul 2003 Issued for use. This is a complete rewrite; therefore, no

revision bars are used to indicate changes. T Brown

2 18 Jan 2007 Complete rewrite. No revision bars are used to indicate changes.

I Papp

3 17 Mar 2009 Complete rewrite. No revision bars are used to indicate changes, though descriptions of changes are provided in Revision Descriptions section for clarity. Incorporated changes in accordance with Letter from ORP, received by WTP PDC on August 4, 2008 (CCN 183784) and further changes from ORP as a result of the meeting held on 11/18/2008.

M Pell

4 11 Aug 2010 Clearly define the roles and responsibilities of the current WTP Interface Partners.

M Pell

5 29 Nov 2011 This is a complete rewrite; therefore, no revision bars are used to indicate changes. Restructured the WTP Interface Management Plan to accommodate Interface Partner contractual concerns and to clarify the method by which WTP interfaces are to be optimized.

M Pell

6 12 July 2012 This is a focused changed to implement DNFSB 2010-2 IP Deliverable 5.7.3.2 as follows: • Strengthens roles, responsibilities, authorities, and

accountabilities for identifying, tracking, managing, and allocating the technical, regulatory and safety-related risks that span the tank farms/WTP interface.

• Establishes a disciplined process to systematically evaluate items to determine their impact on design (i.e., functional and performance requirements) and nuclear safety (i.e., safety basis documents).

• Incorporates decision making tools for managing emerging technical and safety issues.

• Provides enhanced methods for identification and resolution of contract misalignments.

M Pell and S Arm

7 20 Apr 2015 Complete rewrite. Major changes are provided in the Revision Description section.

B Taki

8 16 Jun 2015 Major changes included the following: • Replaced ORP approval of IMP with concurrence. • Removed title of APM for a particular facility. • Added RL concurrence signature on ICDs when

appropriate.

B Taki

9 14 Oct 2016 Major changes to incorporate recommendations from Six Sigma Kaizen event and other process improvements as follows: • Limited the use of “interface partners”; others are

included as “interface organizations”.

D Reinemann

24590-WTP-PL-MG-01-001, Rev 10


Page iv

• Added RL, PRC, and MSC to Section 2. • Replaced Interface Owner Groups with Interface

Manager and Interface Owner role in Section 3. • Removed ICD Team Lead role and added ICD Preparer.

Changed ICD Review Team leadership to WTP Interface Owner. Separated role of WTP Interface Owner from WTP Contractor ICD Approver.

• Added ICD development process in Section 4.4 with specifics for scope definition and review. Updated the concurrence and approval process. Changed use of ICD Revision Checklist to optional.

• Revised the scope and process for Interface Change Forms in Section 4.5.1.

• Simplified ICD issue identification process in Section 5.2.

• Discontinued use of ICD Actions in Section 5.7. • Revised Appendix A to accurately reflect WTP Contract

requirements. • Deleted Appendix C.

10 Mar 2018 Editorial revision to align organizational titles with current BNI-WTP One System organization.

D. Reinemann

24590-WTP-PL-MG-01-001, Rev 10


Page v

Revision Description Section Description

General Replaced “WTP” with “BNI-WTP” where applicable to clarify organizational responsibility. (“WTP Contract” and “WTP Contractor” do not need further clarification.)

Cover sheet Added form 24590-RAPR-F09000 as new cover sheet IMP cover sheet Deleted author, checker, and approver signatures.

1.6 Replaced “for managing ICDs” with “management of ICDs”. 2.3 Paragraph 2, last bullet: replaced ICD issue and open item list with ICD Action Item List. 3.2.5 2nd bullet: inserted (ICD Action Item List) 3.2.7 Heading: replaced Operations Manager with Interface Manager. 3.2.7 Paragraph 1: replaced Operations Manager with Interface Manager. 3.2.7 Deleted Note. 4.4 Deleted “under development” after ICD procedure document number. 4.4.3 Paragraph 2: replaced Operations Manager with Interface Manager. 4.5.1 Paragraph 4: replaced Operations Manager with Interface Manager. 8 Added the reference for the Interface Control Document procedure. 8 Updated the Hanford Site Interface Management Plan to MSA 2017 and Rev. 5.

24590-WTP-PL-MG-01-001, Rev 10


Page vi

Contents Acronyms .................................................................................................................................... viii 1 Introduction ...........................................................................................................................1

1.1 Objective ................................................................................................................................................. 1 1.2 Scope ........................................................................................................................................................ 1

1.3 BNI-WTP Interface Partners ................................................................................................................ 1

1.4 Approvals and Concurrences ................................................................................................................ 2

1.5 BNI-WTP Interface Management Program Relationship to Contracts ............................................ 2

1.6 One System Organization ...................................................................................................................... 2

2 Organizational Roles, Responsibilities, Authorities, and Accountabilities ......................3

2.1 U.S. Department of Energy Office of River Protection ....................................................................... 3

2.2 U.S. Department of Energy Richland Operations Office .................................................................... 3

2.3 Hanford Tank Waste Treatment and Immobilization Plant Contractor .......................................... 3

2.4 Tank Operations Contractor ................................................................................................................. 4

2.5 Plateau Remediation Contractor .......................................................................................................... 5

2.6 Mission Support Contractor ................................................................................................................. 5 2.7 One System ............................................................................................................................................. 5

3 Management Approach .........................................................................................................6

3.1 Overview ................................................................................................................................................. 6

3.2 Interface Control Document Review Teams ........................................................................................ 7

3.3 Interface Managers .............................................................................................................................. 12

3.4 U.S. Department of Energy Office of River Protection ..................................................................... 12

4 Interface Control Documents .............................................................................................12

4.1 Overview ............................................................................................................................................... 12 4.2 Interface Definition Development ....................................................................................................... 12

4.3 Interface Control Document Content ................................................................................................. 12

4.4 Interface Control Document Development ........................................................................................ 13

4.5 Interface Control Document Change Management .......................................................................... 15

5 Interface Control Document Issue Management ..............................................................15

5.1 Interface Control Document Issue Definition .................................................................................... 15 5.2 Interface Control Document Issue Identification .............................................................................. 16

5.3 Interface Control Document Issue Allocation ................................................................................... 17

5.4 Interface Control Document Issue Tracking ..................................................................................... 17

5.5 Interface Control Document Issue Resolution ................................................................................... 17

5.6 Incorporation of Interface Control Document Issue Closure ........................................................... 18

24590-WTP-PL-MG-01-001, Rev 10


Page vii

5.7 ICD Actions .......................................................................................................................................... 18

6 Open Item Management .....................................................................................................18

6.1 Open Item Definition ........................................................................................................................... 18

6.2 Open Item Identification ..................................................................................................................... 19

6.3 Open Item Allocation ........................................................................................................................... 19

6.4 Open Item Tracking ............................................................................................................................. 19 6.5 Open Item Closure ............................................................................................................................... 19

7 Organizational Implementation .........................................................................................19

7.1 Management Responsibilities .............................................................................................................. 19

7.2 Senior Management Participation ...................................................................................................... 19

7.3 Procedures ............................................................................................................................................ 19

7.4 Personnel ............................................................................................................................................... 20 7.5 Resources .............................................................................................................................................. 20

8 References ............................................................................................................................21 Appendices Appendix A Interface Control Document Content ................................................................ A-i Appendix B Interface Owner Interface Control Document Revision Checklist .................. B-i Tables Table 1 WTP Contractor and TOC Nuclear Safety Leads and Regulatory Leads ................ 10 Figures Figure 1 BNI-WTP Interface Control Documents Management Triad ...................................... 7

24590-WTP-PL-MG-01-001, Rev 10


Page viii

Acronyms APM Area Project Manager BNI Bechtel National, Inc. CCN correspondence control number DFLAW direct feed low-activity waste DOE U.S. Department of Energy ICD Interface Control Document ICDRT Interface Control Document Review Team ICF interface change form IM Interface Manager IMP Interface Management Plan IO Interface Owner MSA Mission Support Alliance, LLC MSC Mission Support Contractor NSL Nuclear Safety Lead ORP U.S. Department of Energy Office of River Protection ORP-TF U.S. Department of Energy Office of River Protection, Tank Farms Project ORP-WSC U.S. Department of Energy Office of River Protection, WTP Startup,

Commissioning and Integration ORP-WTP U.S. Department of Energy Office of River Protection, WTP Project O/S One System OSRMT One System Risk Management Team PADC Project Archives and Document Control PRC Plateau Remediation Contractor RL U.S. Department of Energy, Richland Operations Office SME subject matter expert TL Technical Lead TOC Tank Operations Contractor WTP Hanford Tank Waste Treatment and Immobilization Plant

24590-WTP-PL-MG-01-001, Rev 10


Page 1

1 Introduction 1.1 Objective

The objective of this Interface Management Plan (IMP) is to establish the Hanford Tank Waste Treatment and Immobilization Plant (WTP) interface management program. This plan assures documentation and management of shared responsibilities for: (1) transfer of energy, data, or materials; and (2) development, operation, and maintenance of physically compatible facilities and subsystems. The program created by this plan is designed to achieve functional, physical, and administrative compatibility among all external interrelated system elements that are required to support the efficient and timely design, construction, startup, commissioning, and operation of the WTP. This plan provides governance of the program that is executed by a series of interface control documents (ICD). The WTP contractual requirements for managing ICDs are specified by the US Department of Energy (DOE) Office of River Protection (ORP) in the DOE Contract DE-AC27-01RV14136 (DOE 2000). 1.2 Scope

This plan governs the definition, development, management, issue resolution, approval, and documentation of external interfaces between the WTP Contractor (Bechtel National, Inc. [BNI]) and the BNI-WTP interface partners. These interfaces are for energy, data, or materials transferred between the WTP Contractor and other Hanford Site contractors that are not controlled through other means (e.g., Memorandum of Agreement controlled services, such as Fire and Emergency Response Services, and Badging). This plan does not address the internal interfaces of any BNI-WTP interface partner. This plan performs the following functions: • Defines the scope of the BNI-WTP interface management program • Describes the processes through which the BNI-WTP interface management program is implemented • Identifies the BNI-WTP interface partners • Defines the roles and responsibilities of all BNI-WTP interface organizations • Describes the content for ICDs including scope, requirements, controls, and applicable source

documents • Describes the means to identify and resolve ICD issues • Describes the means to identify and track resolution of open items • Describe operational interfaces including applicable operational procedures. 1.3 BNI-WTP Interface Partners

The organizations listed below are the BNI-WTP interface partners. As such, each organization has a particular role to play in the development and management of the BNI-WTP interfaces. Each organization has different and distinct prime contract1 responsibilities that collectively need to be administratively aligned to achieve success in making the BNI-WTP interfaces correctly function. These BNI-WTP-specific roles and responsibilities are described in detail in Section 2. 1 The use of a lowercase “contract” in this document can refer to contracts other than the WTP Contract (e.g., the

Tank Operations Contract) unless noted otherwise.

24590-WTP-PL-MG-01-001, Rev 10


Page 2

• ORP • WTP Contractor • Tank Operations Contractor (TOC) “Interface organizations” as used in this document includes the BNI-WTP interface partners, the U.S. Department of Energy Richland Operations Office (RL), and other Hanford Site contractors. Due to the unique nature of the TOC, its relationship to the WTP Contractor, and the existence of multiple Hanford Site contractor service providers, specifics on interface management between Hanford Site contractors are addressed in the Hanford Site Interface Management Plan, MSC-IMP-00001 (MSA 2017). The roles of RL, the Plateau Remediation Contractor (PRC), and the Mission Support Contractor (MSC) for WTP interfaces are described in Section 2. 1.4 Approvals and Concurrences

The ORP approval of this plan constitutes approval of the BNI-WTP interface management program between the BNI-WTP interface partners. By approving this plan, ORP agrees that the prime contractors under their management control are committed to supporting the WTP startup and operations objectives through their contract performance. The WTP Contractor and TOC concurrence signatures in this plan signify agreement to fully support the objectives of the BNI-WTP IMP, within the boundaries and constraints of their prime contracts. 1.5 BNI-WTP Interface Management Program Relationship to Contracts

The ICDs provide a mechanism to define specific details required to implement inter-contractor interfaces, which are consistent with the prime contracts of interface organizations. Incompatibilities between the baselines of interface organization contracts across a BNI-WTP interface are identified as ICD issues in an appendix of each ICD. The ICD issues must be resolved via the affected interface organization’s approved contract change process prior to incorporation into the ICD scope of work to be performed (i.e., the appendix containing ICD issues is not approved ICD scope). Approval and concurrence signatures on ICDs do not constitute approval for performance of ICD issue scope. Section 5 of this IMP documents the process for identification and management of ICD issues prior to incorporation into ICD scope. 1.6 One System Organization

One System Charter, 24590-WTP-CH-MGT-11-008, was developed and issued to integrate WTP Contractor and TOC activities to complete the Hanford tank waste treatment and disposal mission, including alignment of roles and management of ICDs. Managing ICDs under the One System Charter aids the implementation of a mission-focused approach and provides an effective connection between the WTP Contractor and the TOC for coordinating their respective contracts.

24590-WTP-PL-MG-01-001, Rev 10


Page 3

2 Organizational Roles, Responsibilities, Authorities, and Accountabilities

2.1 U.S. Department of Energy Office of River Protection

The ORP is responsible for ensuring that viable interfaces between BNI-WTP interface partners are established, maintained, and reflected in prime contracts in accordance with site funding priorities. The ORP works with BNI-WTP interface partners to resolve questions regarding conduct of the process. The ORP has the following responsibilities in its role as the client for the WTP Contract: • Monitor interfaces between the WTP Contractor and the TOC to ensure interfaces remain functional,

optimized, and aligned with Hanford Site funding priorities.

• Provide approval of this plan for managing the designated WTP external interfaces and the program that this plan describes.

• Provide interface team members to participate in the production and maintenance of the ICDs.

• Provide signatures for all new or revised ICDs in order to signify the concurrence of the ORP Interface Owners (IO) and approval of the ORP Tank Farms Project (ORP-TF) Assistant Manager; the ORP WTP Startup, Commissioning, and Integration (ORP-WSC) Assistant Manager; and the ORP WTP Project (ORP-WTP) Assistant Manager.

• Maintain a continuing awareness of the state of each interface.

The ORP One System organization supports the following, as applicable:

• Act as an Interface Manager (IM) or IO.

• Participate in ICD Review Team (ICDRT) meetings.

• Coordinate with RL to support ICD development.

The ICDs are WTP Contract deliverables; therefore, ORP has the ultimate authority over ICD content. 2.2 U.S. Department of Energy Richland Operations Office

RL is responsible for ensuring that viable interfaces between the WTP Contractor and the Hanford Site contractors are established, maintained, and reflected in prime contracts. Responsibilities for RL as an interface organization are discussed in Hanford Site Interface Management Plan (MSA 2017). 2.3 Hanford Tank Waste Treatment and Immobilization Plant Contractor

The WTP Contractor assumes the following responsibilities in accordance with the WTP Contract: • Lead IMP development, sign to signify concurrence and commitment to the plan, and obtain

concurrence signatures from the TOC. Submit this plan to ORP for review and approval.

24590-WTP-PL-MG-01-001, Rev 10


Page 4

• Participate in the definition, development, management, issue resolution, approval, and documentation of the interfaces.

• Provide resources to implement its ICD commitments within the WTP Contract baseline.

• Author and maintain the resulting ICDs to ensure the documents accurately reflect the following WTP Contractor elements:

- Baseline scope - Roles and responsibilities - Forecasted services and infrastructure interfaces - Milestones - Technical requirements related to external interfaces - Physical and administrative interfaces - Acceptance criteria

• Ensure all contract or baseline incompatibilities associated with an ICD have been identified as an ICD issue for that ICD. (Section 5 describes ICD issue management.)

• Provide ICDs to ORP for review and approval, and provide implemented ICDs to ORP.

• Approve by signing the ICDs to authorize issuance through the BNI-WTP records management system. (Refer to Section 4.4.3.) Following approval, the ICDs are submitted to BNI-WTP Project Archives and Document Control (PADC) for issuance. Upon receipt of a transmittal letter, PADC distributes the issued ICDs to the BNI-WTP interface partners.

The WTP Contractor is responsible for making the following interface control documentation, as a minimum, readily available to all interface organizations: • Current IMP • ICDs • List of ICDRT members • ICD revision target schedule • ICD Action Item List

The WTP Contractor is accountable to ORP for performance of the ICD process under the WTP Contract. 2.4 Tank Operations Contractor

The TOC assumes the following responsibilities in accordance with the Tank Operations Contract, DE-AC27-08RV14800 (DOE 2008):

• Participate in the development of this plan and sign to signify concurrence and commitment to the

plan.

• Participate in the definition, development, management, issue resolution, approval, and documentation of the interfaces.

• Provide resources to implement its ICD commitments.

24590-WTP-PL-MG-01-001, Rev 10


Page 5

• Collaborate with authors and sign the ICDs to signify concurrence of the TOC IO that the documents accurately reflect the following TOC elements:

- Baseline scope - Roles and responsibilities - Forecasted services and infrastructure interfaces - Milestones - Technical requirements related to external interfaces - Physical and administrative interfaces - Acceptance criteria

• Concur that all contract or baseline incompatibilities associated with an ICD have been identified as ICD issues for that ICD. (ICD issue management is described in Section 5.)

The TOC is accountable to ORP for its performance under the Tank Operations Contract. Additional responsibilities for the TOC are discussed in Hanford Site Interface Management Plan (MSA 2017). 2.5 Plateau Remediation Contractor

The PRC provides waste treatment and disposal services to support the WTP as specified in Section J.3 of the PRC contract and reflected in the ICDs. Responsibilities for the PRC as an interface organization are discussed in Hanford Site Interface Management Plan (MSA 2017). 2.6 Mission Support Contractor

The MSC provides infrastructure, utilities, and services to support the WTP as specified in Section J.3 of the MSC contract and reflected in the ICDs. Responsibilities for the MSC as an interface organization are discussed in Hanford Site Interface Management Plan (MSA 2017). 2.7 One System

The One System (O/S) organization implements a mission-focused approach to provide an effective connection between the TOC and the WTP Contractor. The O/S organization serves to integrate the WTP Contractor and TOC organizations and coordinate WTP interfaces in accordance with the scope of their respective contracts. The ICD-related responsibilities for the O/S organization are as follows:

• Facilitate identification and coordinate resolution of all interfacing WTP Contractor and TOC

technical issues.

• Maintain the BNI-WTP interface management program for all ICDs.

• Maintain and update this IMP and the BNI-WTP ICD procedure.

• Generate the ICD revision target schedule and transmit it to the BNI-WTP interface partners.

24590-WTP-PL-MG-01-001, Rev 10


Page 6

• Monitor performance against the ICD revision schedule and ICD issue/open item resolution.

• Coordinate the revision of all BNI-WTP ICDs as necessary with applicable IOs and Technical Leads (TL). Also coordinate with BNI-WTP Prime Contract and TOC Prime Contract Management to ensure revisions are within the scope of the WTP Contract and Tank Operations Contract, respectively.

• Plan and coordinate BNI-WTP support activities of interface organizations.

• Identify, track, and elevate issues for management review in the Monthly Status Report. The O/S organization is also responsible for managing and maintaining a register of common and interface risks through its One System Risk Management Team (OSRMT). The purpose, scope, and objectives of the OSRMT are defined in the One System Risk Management Team (OSRMT) Charter (24590-WTP-CH-MGT-12-001) and the One System Charter.

3 Management Approach 3.1 Overview

The overall structure of BNI-WTP interface management is made of three distinct levels, with each level having specific functions and organizations responsible for coordinating these functions (Figure 1). The three levels of BNI-WTP ICD management are as follows:

• ORP

Final decision authority (as stated in Section 3.4).

• Interface Managers and Interface Owners

IMs and IOs are the decision makers for specific ICDs (as described in Section 3.3 and Section 3.2.1).

• ICD Review Teams

One ICDRT is formed for each active ICD (as outlined in Section 3.2).

24590-WTP-PL-MG-01-001, Rev 10


Page 7

Figure 1 BNI-WTP Interface Control Documents Management Triad

These groups and their specific roles, responsibilities, accountabilities, and authorities are discussed in the following sections. 3.2 Interface Control Document Review Teams

The ICDRTs are responsible for the technical, regulatory, nuclear safety, contractual, and administrative accuracy of the interface. The team consists of personnel from each BNI-WTP interface partner responsible to implement the interface and may include representatives from other Hanford Site contractors affected by the interface, including the following (as appropriate for each ICD and interface scope): • IO or designated representative • TLs and other subject matter experts (SME) • Regulatory Leads and other SMEs • Nuclear Safety Leads (NSL) and other SMEs • ORP Interface Manager • BNI-WTP Prime Contract representative • WTP Contractor ICD Approver or designated representative • ICD Coordinator • ICD Preparer

24590-WTP-PL-MG-01-001, Rev 10


Page 8

The ICDRTs may be either standing teams that hold periodic meetings or teams created for a specific purpose of limited duration. The ORP provides oversight for ICDRT activities. Most comments and questions received from ICD team members can be resolved at ICDRT meetings with the resolutions recorded in ICD meeting minutes. Other questions or comments may lead to ICD meeting actions, which are recorded and tracked by the ICD Coordinator. The WTP Contractor is responsible for issuing and maintaining ICDs and provides administrative leadership for coordinating ICDRT activities. The WTP Contractor, TOC, and ORP are present at all ICDRT meetings. The WTP Contractor IO is the ICDRT leader and chairs ICDRT meetings. The requirement for a quorum at an ICDRT meeting is considered to be satisfied if each BNI-WTP interface partner is represented by its IO or at least one individual that is authorized by the IO to speak for their organization. If a quorum is not established, the WTP Contractor IO determines the course of action. The ICD Coordinator is responsible for scheduling ICDRT meetings and for recording and distributing meeting minutes.

3.2.1 Interface Owners

The IOs are designated project representatives responsible for the primary area affected by the interface. The IO is the primary organizational point of contact. Each interface organization designates an IO who is accountable to the organization’s IM for the performance of ICD-related responsibilities. In their role, IOs assume the following responsibilities:

• Ensure a TL, Regulatory Lead, and NSL are appointed for each ICD as applicable to their

organization’s scope in consultation with other managers within their organization.

• Ensure the ICDs accurately reflect their organization’s contract baseline and that exceptions falling outside their organization’s contract baseline are captured as ICD issues and are not included in the ICD scope of work until resolved via the approved contract change process when resolution requires a contract change.

• Ensure all ICDs and interface change forms (ICF) affecting their organization are evaluated by their applicable Regulatory Lead, NSL, TL, respective SMEs, and Contracts, and ensure any identified regulatory, nuclear safety, technical, and contract issues are tracked as ICD issues.

• Ensure reviews of ICDs are completed within the designated review cycle and are focused on the scope of the changes. Ensures review comments are consolidated.

• Ensure the resolution of all comments is completed to the satisfaction of the applicable TL, Regulatory Lead, NSL, respective SMEs, and Contracts before signing ICDs and ICFs. Determine if the IO ICD Revision Checklist (Appendix B) is appropriate to document concurrence of Leads.

• Identify and evaluate ICD issues and initiate any necessary contract or baseline changes needed to drive the issue to resolution.

• Manage the ICD issues, including the approach to resolve ICD issues based on the recommendations from the TL, Regulatory Lead, NSL, and respective SMEs as applicable.

• Sign completed ICDs and ICFs to signify concurrence.

• Understand each interface and monitor its compatibility. This may be accomplished through reports from team representatives or direct participation in the interface process. The IOs are responsible for ensuring a compatible and viable interface exists. Either the interface is within the contract baseline,

24590-WTP-PL-MG-01-001, Rev 10


Page 9

permits, and authorization basis of the contractor, or the incompatibility is accurately identified as an ICD issue, and the process used to follow the issue to resolution is documented.

• Inform their respective IM of all pertinent details of an ICD issue that cannot be resolved by the ICDRT so that the ICD issue may be brought before the IMs and IOs for resolution.

• Participate in IM/IO meetings as applicable to address ICD issues that have not been resolved in the course of routine ICDRT meetings (more detail on ICD issue resolution is described in Section 5).

• Assess the impact of ICD changes to functions and requirements applicable to their organization.

The WTP Contractor IO is a One System manager and is the leader of the ICDRT. The WTP Contractor IO informs the ICD Approver of the progress of ICD or ICF development.

3.2.2 Technical Lead

The TLs are technical SMEs that are designated as appropriate by the IOs in consultation with other managers within their organization. The WTP Contractor and TOC assign TLs for each ICD. ORP, RL, PRC, and MSC may appoint TLs at their discretion. There may be multiple technical SMEs from one organization for a single ICD that are appropriately qualified to systematically evaluate the ICD content for technical and design impacts to interfacing systems and to identify technical risks and issues. The TLs and technical SMEs are accountable to their respective IOs for performance of the following ICD-related responsibilities: • Provide input to defining and developing interface details.

• Participate in ICDRT meetings.

• Review ICDs and ICFs for technical accuracy, including evaluation of system technical and design impacts.

• Identify potential technical incompatibilities as ICD issues

3.2.3 Nuclear Safety Lead

The NSLs are nuclear safety SMEs designated as appropriate to the ICD and the interface scope by the IOs with necessary concurrence from functional management. The WTP Contractor and TOC assign NSLs as specified in Table 1. ORP, RL, PRC, and MSC may appoint NSLs at their discretion. There may be multiple nuclear safety SMEs from one organization for a single ICD that are appropriately qualified to systematically evaluate the ICD content for nuclear safety impacts to interfacing systems and to identify nuclear safety issues. The NSLs and nuclear safety SMEs are accountable to their respective IOs for performance of the following ICD-related responsibilities: • Participate in ICDRT meetings.

• Complete a technical review and/or safety evaluation of proposed ICD changes and ICFs to evaluate alignment with and determine the impact to safety basis documents.

• Identify potential nuclear safety incompatibilities as ICD issues

3.2.4 Regulatory Lead

Regulatory Leads are regulatory SMEs designated as appropriate to the ICD and the interface scope by the IOs with necessary concurrence from functional management. The WTP Contractor and TOC assign

24590-WTP-PL-MG-01-001, Rev 10


Page 10

Regulatory Leads as specified in Table 1. ORP, RL, PRC, and MSC may appoint Regulatory Leads at their discretion. There may be multiple regulatory SMEs from one organization for a single ICD that are appropriately qualified to systematically evaluate the ICD content for regulatory impacts to interfacing systems and to identify regulatory issues. Regulatory Leads and regulatory SMEs are accountable to their respective IOs for performance of the following ICD-related responsibilities: • Participate in ICDRT meetings.

• Review ICD revisions and ICFs for regulatory accuracy, including the evaluation of system regulatory impacts.

• Identify regulatory incompatibilities as ICD issues.

Table 1 WTP Contractor and TOC Nuclear Safety Leads and Regulatory Leads

ICD NSL Required Regulatory Lead

Required ICD 1, ICD for raw water No Yes

ICD 2, ICD for potable water No Yes

ICD 3, ICD for radioactive solid wastes Yes Yes

ICD 5, ICD for non-radioactive, non-dangerous liquid effluents No Yes

ICD 6, ICD for radioactive, dangerous liquid effluents Yes Yes

ICD 9, ICD for land for siting No Yes

ICD 11, ICD for electricity Yes Yes

ICD 12, ICD for roads No Yes

ICD 14, ICD for immobilized high-level waste Yes Yes

ICD 15, ICD for immobilized low-activity waste Yes Yes

ICD 19, ICD for waste feed Yes Yes

ICD 23, ICD for waste treatability samples Yes Yes

ICD 28, ICD for pit 30 aggregate supply for construction No Yes

ICD 29, ICD for waste sodium No Yes

ICD 30, ICD for direct LAW feed Yes Yes

ICD 31, ICD for DFLAW effluent returns to double-shell tanks Yes Yes

3.2.5 WTP Contractor ICD Coordinator

The ICD Coordinator is part of O/S and accountable to the WTP Contractor Interface Manager for performance of the following ICD-related responsibilities:

• Maintain the BNI-WTP Interface Team List and transmit it to all ICDRT members.

• Maintain a consolidated list of ICD issues and open items (ICD Action Item List) and distribute it for periodic review.

24590-WTP-PL-MG-01-001, Rev 10


Page 11

• Act as a single point of contact for organizations external to BNI-WTP for exchanging information regarding this IMP, the ICDs, and any ICF.

• Assist in identifying all outstanding issues and comments when preparing a scope document for an ICD change.

• Schedule and attend all ICDRT meetings.

• Record, submit for review, and issue all ICDRT meeting minutes. Manages the resolution of meeting actions identified by the ICDRT and documents the actions, status, and closure of meeting actions in the minutes.

• Coordinate distribution of ICDs, ICFs, and review comments during the review cycle.

• Coordinate signatures for ICDs and ICFs with interface organizations.

3.2.6 WTP Contractor ICD Preparer

The ICD Preparer is the principal author of a new or revised ICD or an ICF. The ICD Preparer is knowledgeable about the specific ICD and is appointed by the WTP Contractor IO with concurrence from the appropriate organization management. The ICD Preparer is accountable to the WTP Contractor IO for the following responsibilities:

• Prepare new ICDs, ICD revisions, and ICFs and manages all changes to working drafts.

• Maintain the native document files

• Ensure the ICD reflects the current state of physical and administrative interfaces

• Participate in ICDRT meetings

• Disposition review comments with input from the ICDRT as needed

• Sign the final draft as an indication to the interface organizations that the document is ready for concurrence and approval.

3.2.7 WTP Contractor Design Authority and One System Interface Manager

The ICDs with complex acceptance criteria also require the signature of the WTP Contractor Design Authority and WTP Contractor O/S Interface Manager on completed ICDs and ICFs to signify concurrence. These ICDs include the following: • ICD 14, ICD for immobilized high-level waste • ICD 15, ICD for immobilized low-activity waste • ICD 19, ICD for waste feed • ICD 30, ICD for direct LAW feed • ICD 31, ICD for DFLAW effluent returns to double-shell tanks

3.2.8 WTP Contractor ICD Approver

The WTP Contractor ICD Approver is BNI-WTP Area Project Manager (APM) for the WTP facility affected by the interface and has overall responsibility for the content of the corresponding ICD. Final approval for each new ICD, ICD revision, and ICF is provided by the appropriate BNI-WTP APM, and

24590-WTP-PL-MG-01-001, Rev 10


Page 12

this responsibility may not be delegated unless the APM is unavailable. The ICD Approver or designated representative attends the ICDRT meetings. The ICD Approver supports development of the ICD scope document. 3.3 Interface Managers

Interface managers are accountable to their senior management for performance of the following interface management responsibilities: • Attend ICDRT meetings at their discretion or delegate attendance to a subordinate manager.

• Ensure that all ICD issues raised from the ICDRT have adequate support from their staff and management. (Additional detail on ICD issue resolution is provided in Section 5.)

• Ensure that all interface management processes described in this plan remain functional and responsive.

The WTP Contractor provides the administrative leadership for coordinating IM/IO meetings. The ICD Coordinator is responsible for scheduling all IM/IO meetings and for recording and distributing meeting minutes. ORP provides oversight for IM/IO activities. 3.4 U.S. Department of Energy Office of River Protection

The WTP Contract, Standard 1 (b)(1)(i) states: “The interface management plan shall recognize the DOE [ORP] role as the owner of the WTP and as the final decision authority for any interface issues that are not resolved between the other parties.”

4 Interface Control Documents 4.1 Overview

The external interfaces related to energy, data, or materials transferred between the WTP Contractor and other interface organizations are defined and documented in ICDs. The purpose of the ICDs is to define WTP interfaces, including the identification and resolution of contract adjustments needed to accomplish each WTP interface. 4.2 Interface Definition Development

The ICDs identify baseline requirements and responsibilities associated with WTP interfaces. Specific ICDs are identified by the WTP Contract and are reflected in the J.3 Matrix shared by the TOC, PRC and MSC. If any of the BNI-WTP interface partners identify a need for a new interface affecting WTP, the affected IO recommends the new WTP interface to the TOC prior to proposing its potential incorporation into the WTP Contract to ORP as a new BNI-WTP ICD. 4.3 Interface Control Document Content

Interface definitions are documented in ICD text, graphics, tables, issues, and references to other documents or drawings. The definition has adequate detail to ensure compatibility between organizations sufficient for safe and compliant design, construction, and operation. The ICDs describe organizational roles and responsibilities for the interface, requirements, details of the physical interface, details of the

24590-WTP-PL-MG-01-001, Rev 10


Page 13

administrative interface, and applicable controls. ICDs reflect all interfaces and services needed in the construction and performance testing phases and projected interfaces and services needed for the future commissioning and operating phases. Any incompatibility between the technical, regulatory, or nuclear safety baselines of interface organization contracts across a WTP interface is documented as an ICD issue with the interface organization tracking mechanism identified. Where appropriate, the acceptable criteria for the transfer of the energy, data, or material across the interface is described. Minimum content for ICDs is described in Section C.9 of the WTP Contract (see Appendix A of this plan). The content of the ICDs is jointly developed by the interface organizations through use of the ICDRTs. Each interface organization’s management monitors and participates in the team effort when necessary. Agreement needs to be achieved between the affected IOs (or their designated representative) present at the ICDRT meetings. Key interface milestone events are identified to mark activities or project2 phases when significant interactions between interface organizations begin and are included on each interface organization’s baseline project schedule. Specific milestone dates are not listed in the ICDs to avoid conflict with project schedules. As the project develops, and greater detail regarding the sequence and timing of project milestones is discovered, changes to the milestones are possible. These changes are incorporated as part of the ICD revision process. Open ICD issues are listed in Appendix A of each ICD. This appendix shows the issue number, the corresponding tracking number, and a brief description of the issue. The ICD Appendix A indicates for each interface organization if the issue is inside the contract technical, regulatory, or nuclear safety baseline; outside the contract baseline; or not applicable. The entry lists pages within the ICD affected by the issue. The ICD issues that have closed since the last revision of the ICD are listed in Appendix B of each ICD. This appendix shows the issue number, the corresponding tracking number, the closure date for the issue, and a brief description of the resolution. 4.4 Interface Control Document Development

The formal process for preparing a new or revised ICD is presented in the BNI-WTP ICD procedure (24590-WTP-GPP-RAOS-OS-0001). The entire BNI-WTP ICD revision and approval process is subject to ORP monitoring, audit, and review at any time. 4.4.1 Scope Definition

The initial phase of ICD development is scope definition. The purpose of scope definition is to define the scope of ICD development or revision and to focus ICDRT activities on that specific scope. Concerns raised that are outside the scope may be deferred.

The WTP Contractor IO is responsible for developing a scope definition, which includes the following:

• Purpose and principal objectives • Key schedule dates for review and approval • New and revised requirements

2 The use of a lowercase “project” in this document can refer to projects other than the WTP Project (e.g., Tank

Farms Project) unless noted otherwise.

24590-WTP-PL-MG-01-001, Rev 10


Page 14

• Identification of interface organization IOs

The ICD Coordinator and ICD Preparer assist the WTP Contractor IO in identifying all proposed changes and outstanding comments associated with the ICD. The WTP Contractor IO meets with the interface organization IOs and the ICD Approver to review and obtain concurrence with the scope of the ICD so the IOs can support the ICD effort. If the scope impacts WTP technical requirements, the BNI-WTP Design Authority is included with the review and concurrence. The ICD Coordinator documents this concurrence. Based on the defined scope, the ICD Preparer develops the initial ICD draft. 4.4.2 Review

After the initial ICD draft is completed, it is distributed to the interface organization IOs for review. The IOs are responsible to determine the appropriate reviewers within their organization. The IOs limit distribution of the initial draft to the designated reviewers. The IOs instruct the reviewers to focus comments to the scope of the revision. IOs ensure that the review is completed within the time period of 10 working days. The reviewers submit comments to the IO or the IO’s delegate for consolidation of comments before comments are returned to the WTP Contractor. ICDRT meetings are held to address comments as needed. Comments that impact multiple interface organizations are brought to the ICDRT for resolution. The ICD Preparer may choose to distribute updated drafts to communicate comment disposition. The final draft is distributed prior to concurrence, but another formal review is not conducted. 4.4.3 Concurrence and Approval

When the final ICD draft is completed with incorporation of review comments, the ICD Preparer signs the ICD signature page signifying that the ICD is complete and ready for signatures. Concurrence signatures on an ICD signify that the ICD accurately reflects the current contract technical, regulatory, and nuclear safety baseline for each interface organization, except for ICD issues identified in Appendix A of the ICD. The contractor IOs and the BNI-WTP Prime Contract Manager sign the ICD signature page to indicate their concurrence with the ICD. The IOs may choose to use the optional IO ICD Revision Checklist (Appendix B of this plan) to document concurrence from their organization’s TL, Regulatory Lead, and NSL. The ICD Preparer includes any ICD Revision Checklists submitted by the IOs in the review package. The WTP Contractor Design Authority and the WTP Contractor One System Interface Manager sign the ICD signature page for the ICDs identified in Section 3.2.7 to indicate their concurrence with the ICD contents. After the contractor IO signatures are completed, the WTP Contractor coordinates with ORP-One System to obtain signatures from the ORP IOs, the RL IO when applicable, and the ORP assistant managers listed in Section 2.1. After ORP signatures are added, the ICD is forwarded to the WTP Contractor ICD Approver for final approval. The WTP Contractor approval signature indicates that the document is approved for issuance

24590-WTP-PL-MG-01-001, Rev 10


Page 15

on the basis that each interface organization concurs with the ICD contents and the ICD accurately reflects the contract baseline for each interface organization, except as noted above. Following approval, the ICD Coordinator submits the ICD to BNI-WTP PADC for issuance. After the ICD is issued, the ICD Coordinator ensures a letter of transmittal is sent to ORP. The ICD Coordinator ensures copies (either electronic or hard copy) of the issued ICD are available to the ICDRT. 4.5 Interface Control Document Change Management

Changes to ICDs can be implemented by ICFs or by ICD revision. Extensive changes to ICDs are achieved through revision. Smaller, more focused changes to an ICD can be implemented by means of an ICF. 4.5.1 Interface Change Forms

The purpose of the ICF is to implement small, focused changes to the ICD. An ICF should only be used for a specific subject, editorial corrections, and administrative changes. ICFs are not used for extensive changes or changes that affect a contract technical, regulatory, or nuclear safety baseline. ICFs can be used to implement changes from closing ICD issues, provided the process in Section 5.5 is completed first. The ICF describes the proposed change and the reason for the proposed change. An ICF that affects the content of an ICD (other than editorial or administrative changes) may use the scope definition process described in Section 4.4.1. An ICF is reviewed by the interface organizations for the affected ICD. The ICF uses the same review process described in Section 4.4.2. When the final draft of the ICF is completed, the ICD Preparer signs the ICF. The contractor IOs and the BNI-WTP Prime Contract Manager sign the ICF to indicate their concurrence. The IOs are responsible to verify concurrence from their TL, NSL, and Regulatory Lead, as appropriate. The WTP Contractor Design Authority and the WTP Contractor One System Interface Manager sign the ICFs identified in Section 3.2.7. The WTP Contractor coordinates with ORP-One System to obtain signatures from the ORP IOs and the RL IO when applicable. The WTP Contractor ICD Approver then signs the ICF. Following approval, the ICD Coordinator submits the ICF to BNI-WTP PADC for issuance. When the ICF is issued, it becomes part of the currently authorized ICD. A maximum of five ICFs can be written against a single ICD before the ICD is revised to incorporate all outstanding ICFs. 4.5.2 Interface Control Document Revision

Changes that fall outside the ICF scope are implemented with an ICD revision. An ICD revision follows the scope, review, and concurrence and approval process described in Section 4.4.

5 Interface Control Document Issue Management 5.1 Interface Control Document Issue Definition

The BNI-WTP ICD issues are defined as follows:

24590-WTP-PL-MG-01-001, Rev 10


Page 16

• An incompatibility between the technical, regulatory, or nuclear safety baselines of interface organization contracts across a WTP interface.

OR • An incomplete WTP interface. An incomplete WTP interface is defined as follows: • A contract requirement that is not currently being met. OR • A perceived need that is not currently in the technical, regulatory, or nuclear safety baselines of any

interface organization contract; however, the following conditions are met:

- The perceived need has been validated by a rigorous engineering evaluation.

AND - All of the IOs for the affected systems have concurred the perceived need must be met to achieve

mission success.

OR - The perceived need must be met to comply with state or federal law.

The ICD issues would be considered ICD risks if their consequences have an impact on cost and/or schedule that exceed a threshold as determined by the OSRMT. 5.2 Interface Control Document Issue Identification

The ICD issues are identified via two pathways. 1. During an ICD review cycle, the members of the ICDRT evaluate the ICD for its impact on design,

regulatory compliance, and nuclear safety and identify potential ICD issues. The ICDRT members forward potential ICD issues to their respective IO, who then forwards the potential issue to the WTP Contractor IO.

2. Outside an ICD review cycle, a member of the ICDRT may identify a potential ICD issue according

to the organization’s established practice for evaluating design, regulatory, and nuclear safety impacts. The ICD member forwards potential ICD issues to the respective IO, who then forwards the potential issue to the WTP Contractor IO.

When a potential ICD issue is identified, the WTP Contractor IO works with the ICD Coordinator to schedule meetings of the ICDRT to discuss the potential ICD issue.

The ICDRT discusses all aspects and implications of the potential ICD issue. The ICDRT considers identification of the driver of the issue, the urgency for resolution, and the date the resolution is needed. If an ICD issue is identified by agreement between the affected IOs (or designated representative) present at the meeting, the ICD Coordinator records the identification of an ICD issue in the meeting minutes.

ICD issues are communicated to the OSRMT by the WTP Contractor IO for evaluation of whether they pose a significant project (cost or schedule) risk. If significant project risks are identified, the OSRMT

24590-WTP-PL-MG-01-001, Rev 10


Page 17

then tracks the risks according to One System Risk Management Team (OSRMT) Charter. The OSRMT risk identifier is also included in the ICD with any action tracking identifiers.

5.3 Interface Control Document Issue Allocation

The ICD issues are allocated to interface organizations by agreement between the affected IOs. 5.4 Interface Control Document Issue Tracking

Each ICD issue is described in the ICD Appendix A (with a tracking number or schedule ID) by the affected IO. The affected IO is responsible for ensuring the issue is entered into the assigned/affected interface organization’s action tracking system and/or project schedule as applicable. When an ICD issue is owned by more than one interface organization, the ICD issue is tracked in each interface organization’s tracking system and/or project schedule, and recorded in the ICD with multiple tracking numbers. Progress on closing ICD issues is tracked at ICDRT meetings. The ICD Coordinator is responsible for maintaining a consolidated list of ICD issues and open items. The ICD Coordinator distributes the ICD Action Item List to the ICD IOs for periodic review. 5.5 Interface Control Document Issue Resolution

The overall strategy for resolution of ICD issues affecting interface organizations relies upon the three-level management approach identified below: • ORP (as described in Section 3.4) • IMs and IOs (as described in Section 3.3 and Section 3.2.1) • Individual ICDRTs for each ICD (as described in Section 3.2)

The method to resolve ICD issues is as follows: 1. Having implemented the interface organization’s tracking mechanism for identified and allocated

ICD issues, the affected IO is responsible for forming and leading a team to resolve the scope of the ICD issue. The affected IO team can consist of the TL, Regulatory Lead, and NSL as appropriate to the ICD and the affected IO scope. The affected IO team periodically presents its findings at ICDRT meetings. The ICD issues are resolved by agreement between the affected IOs (or designated representative) present at the meeting.

• If agreement can be reached between the affected IOs present at an ICDRT meeting, the resolution is recorded in the meeting minutes.

• If agreement cannot be reached between the affected IOs present at the ICDRT meeting and further actions are not considered viable, the ICD Coordinator records this in the meeting minutes and notifies the WTP Contractor IO that the ICD issue is elevated to the appropriate IMs/IOs.

2. The ICD Coordinator schedules a meeting with the appropriate IMs/IOs and includes the issue on the agenda. If resolution of the ICD issue is urgent, the ICD Coordinator calls a timely meeting of the affected IMs/IOs.

24590-WTP-PL-MG-01-001, Rev 10


Page 18

• If the IOs are successful in reaching a consensus resolution among all IM/IO members at the meeting, the ICD Coordinator records the resolution in the meeting minutes for distribution to the entire ICDRT.

• If a consensus resolution cannot be reached among all IM/IO members at the meeting, the ICD Coordinator records this in the meeting minutes. For ICD issues that affect the WTP Contractor, the ICD Coordinator notifies the WTP Contractor IM that the ICD issues are elevated to ORP for resolution. For ICD issues that affect TOC, the issue resolution process in the Hanford Site Interface Management Plan (MSA 2017) is followed.

Although ICD issues may be declared resolved, they are not considered closed until ORP has made that determination and the applicable contract changes have been authorized by the Contracting Officer. Following needed changes to project baseline documentation and/or the contract, the appropriate IO recommends ICD issue closure and provides the closure strategy to ORP. The document from ORP granting approval to close the ICD issue is given a BNI-WTP CCN to be referenced in the closure comments of the action tracking system item or the project schedule item.

The resolution of ICD issues affecting Hanford Site contractors is discussed in Hanford Site Interface Management Plan (MSA 2017). 5.6 Incorporation of Interface Control Document Issue Closure

If time allows, closure of an ICD issue is incorporated into the next scheduled revision of the affected ICD. If the ICD issue closure needs to be incorporated sooner, an ICF may be used to implement changes related to the ICD issue closure, as long as the scope of the ICF meets the criteria in Section 4.5.1. The next revision of the affected ICD incorporates the ICF and reflects actions taken and conditions established as a result of the ICD issue closure. 5.7 ICD Actions

As of the effective date of revision 9 of this plan, ICD actions are no longer used. Any activity that does not meet the definition of an ICD issue is managed as an open item per Section 6. Existing ICD actions (as listed in Appendix A of each ICD) are closed by agreement between the affected IOs present at an ICDRT meeting. The agreement to close an ICD action is recorded in the meeting minutes. Closed ICD actions are moved to Appendix B if the ICD, which includes the action number, the associated tracking number, the closure date, and a brief description of the resolution.

6 Open Item Management 6.1 Open Item Definition

Members of an ICDRT may want to track items that may not meet the definition of ICD issues. An open item is an activity or determination that is expected to influence or complete interface elements but is not completed at the time of ICD issuance. For example, an ongoing engineering study undertaken by an interface organization would be noted in the ICD as an open item and include a tracking number or schedule ID that would serve to track completion of the study. An open item can be used to track information needed to make a determination on a potential ICD issue.

24590-WTP-PL-MG-01-001, Rev 10


Page 19

New open items are added to each ICD revision as Appendix C and are removed in the next revision following their introduction. 6.2 Open Item Identification

Open items are identified in a similar way to ICD issues, as described in Section 5.2. If an open item is accepted by agreement between the affected IOs (or their designated representative) present at an ICDRT meeting, the ICD Coordinator records identification of the open item in the meeting minutes. 6.3 Open Item Allocation

Open items are allocated by agreement between the affected IOs (or their designated representative) present at the ICDRT meeting. The affected IO identifies a responsible person for the closure of the open item. 6.4 Open Item Tracking

New open items are added to Appendix C of each ICD. The affected IO is responsible for ensuring any open items are entered into the assigned interface organization’s action tracking system and/or project schedule. The affected IO provides the tracking number to the ICD Coordinator. Progress on closing open items is discussed at ICDRT meetings. The ICD Coordinator is responsible for maintaining a consolidated list of ICD issues and open items. 6.5 Open Item Closure

The applicable IO determines the best means of closing open items. In the example provided in Section 6.1, no additional activities are required because the ICDRT monitors the ongoing engineering study. However, some open items may require additional activities to make a determination on a potential ICD issue.

7 Organizational Implementation 7.1 Management Responsibilities

The WTP Contractor and the TOC are responsible for establishing and maintaining an interface management program that integrates the requirements of this plan with the organization’s internal work control processes and procedures. 7.2 Senior Management Participation

Senior management for each BNI-WTP interface partner is responsible for ensuring the interface management process is established and active in sufficient measure so that compatible and viable interfaces are created and maintained. 7.3 Procedures

The WTP Contractor will issue a procedure to implement this plan in accordance with the WTP Contract.

24590-WTP-PL-MG-01-001, Rev 10


Page 20

Procedures for Hanford Site contractors, including the TOC, are discussed in Hanford Site Interface Management Plan (MSA 2017). The O/S staff are responsible for following their organization’s procedures (WTP Contractor or TOC); there are no specific O/S ICD-related procedures applicable to both the WTP Contractor and TOC staff. 7.4 Personnel

Each BNI-WTP interface partner will designate participants for this plan. 7.5 Resources

Each BNI-WTP interface partner is responsible for providing the resources necessary to maintain each interface in which they participate. If resources are required that are not currently in a contractor’s baseline, they are to be requested from ORP through the appropriate baseline change process. The WTP Contractor and TOC are individually responsible for assigning resources to the O/S organization consistent with the WTP Contract and Tank Operations Contract.

24590-WTP-PL-MG-01-001, Rev 10


Page 21

8 References 24590-WTP-CH-MGT-11-008 (RPP-51471), One System Charter. Bechtel National, Inc., Richland, WA.

24590-WTP-CH-MGT-12-001 (RPP-52149), One System Risk Management Team (OSRMT) Charter. Bechtel National, Inc., Richland, WA.

24590-WTP-GPP-RAOS-OS-0001, Interface Control Documents, Bechtel National, Inc., Richland, WA.

DOE. 2000. Hanford Tank Waste Treatment and Immobilization Plant, Contract DE-AC27-01RV14136. U.S. Department of Energy, Office of River Protection, Richland, WA.

DOE. 2008. Tank Operations, Contract DE-AC27-08RV14800. U.S. Department of Energy, Office of River Protection, Richland, WA.

MSA. 2017. Hanford Site Interface Management Plan, MSC-IMP-00001, Rev. 5. Mission Support Alliance, LLC, Richland, WA.

24590-WTP-PL-MG-01-001, Rev 10


Page A-i

Appendix A Interface Control Document Content

24590-WTP-PL-MG-01-001, Rev 10


Page A-1

Appendix A Interface Control Document Content Per Section C.9 of the WTP Contract, Interface Control Documents (ICD) include details of the following topics consistent with the complexity, maturity, and phase (design, construction, operation) of the project: • Physical aspects of the interfaces that contain the following, as appropriate:

- Location and description of each interface point - Interface block diagrams and schematics that clearly define organizational responsibilities for

each interface (such as ownership, construction, and maintenance) - Type, quantity, and material composition - Packaging requirements - Design drawings - Operation and maintenance requirements

• Administrative aspects of the interfaces, including the following:

- Procedures that define the administrative transfer of interface items (such as who, what, when, where, and how)

- Linkage to the integrated RPP and individual contractor project baselines; baseline schedules and logic must contain a level of detail that demonstrates key ICD events or milestones are achievable

- Documentation necessary for official exchange of interface items - Authorization basis and permitting integration

• Acceptance criteria for official transfer of items across the interface

In addition to the above, ICDs may include the following:

• Summary level description of the interface

• Key functional requirements for each participating contractor necessary to implement and operate the interface

• Specific details that further break down the functional requirements into discrete items that can be referenced as the source of specific design requirements or programmatic commitments

• Forecasted services and infrastructure requirements

- Precise description of the required service and/or infrastructure

- Quantity of service and infrastructure required. If the quantity of service and infrastructure varies over time, a best estimate forecast will be generated by the WTP Contractor, including a time versus quantity estimate. This time versus quantity estimate should run as far into the future as practical, up to and including the commissioning and operating phases.

• Description of interface technical, regulatory, nuclear safety or contractual incompatibilities between contractors (contract misalignments)

• Description of the method for closing incompatibilities

• Identification of key baseline document references from all affected participants defining the interface boundaries and parameters

24590-WTP-PL-MG-01-001, Rev 10


Page B-i

Appendix B Interface Owner Interface Control Document Revision Checklist

24590-WTP-PL-MG-01-001, Rev 10


Page B-1

Appendix B: Interface Owner Interface Control Document Revision Checklist