Page 1 Of

1 . m ~ 6 1 5 7 3 9 'f' 3 ENGINEERING DATA TRANSMITTAL [e,!

Y

2. To: (Receiving Organization)

Dis t r i bu t i on

5. Proj./Prog./Dept./Div.:

Engineering/ I n te r im S tab i l i za t i on Project/Tank Farm Trans i t ion Projects 8. Originator Remarks:

Approval/Rel ease

3. From: (Originating Organization)

Media Systems Appl ication/Media Management Systems / BCSR

John H. Huber/WHC 6. Cog. Engr.:

11. Receiver Remarks:

4. Related EDT No.:

Ni*I 7. Purchase Order No.:

9. Equip./Component No.:

ID. System/BLdg./Faci Lity:

VIDON 12. Major Assm. Owg. No.:

13. PermitlPermit Application No.:

14. Required Response Date:

18.

Authorized Representative Date f Signature of ED Originator for Receiving Organization

21. DOE APPROVAL (if required)

t1 Approved t1 Approved rlcomnents

CtrL. No.

ED-7400-172-2 (04/94) GEF097

BD-7-172-1

WHC-SD-WM-SUP-013, Rev. 0

Visual Image Digital Object Network (VIDON) Software Project Management Plan

B.D. Byron Westinghouse Hanford Company/Boeing Computer Services Richland Richland, WA 99352 U.S. Department of Energy Contract DE-AC06-87RL10930

EDT/E.CN 615739 U C UC-2030 Org Code: 67100 B&RCode: YNOlOOOOO TotalPagcs: 20

Kcy Words: Software, Project, Mamgcmcnl

Charge Code: MPS00

Abstract: T h i s doeument, the Software Project Ma~gemtnt Plan (SPMP), describer lhe management and implemenlalion amtegy for Visual Image Object Network (VIDON) Project, an Approval Designator 3Q rymem. It ir intended to be used as guideline by the customer, the management, and lhc VDON development team to define the VlDON xopc of work and to pmvide a detailed plan on how lhc work is to bc accomplirhed.

Trademark:

MioroSotiPmjeet is II trademark of MicmsoR Corporation. WordPcrfect if a trademark of WordPcrfcct Corporation.

Release Appmval Release Stamp

Approved for PubIic ReIease A 4 4 W 7 3 (10/95) GEF321

WHC-SD-WM-SOP-013, Rev. 0

VISUAL IMAGE DIGITAL OBJECT NETWORK (VIDON)

FY96

SOFTWARE PROJECT MANAGEMENT PLAN (SPMP)

October, 1995

Administrative Project Lead: Barry Byron

Document Consultant: Laurie M. O l le ro

1

WHC-SD-WM-SDP-013, Rev. 0

SIGN OFF:

3-;,s.c& VIDON WHC Cogrhzant Manager s ignature Date

A

3 l zd9 6 VIDON WHkkognizant E n m e r and Customer POC s ignature Date

VIDON BCSR Proj$t Owner s ignature Date

VIOON B k d Technicdl Manager s ignature Date

d/ 96 @C Qua l i ty Assurance s ignature Date

2

WHC.SD.WM.SDP.013, Rev . 0

CONTENTS

1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 PURPOSE OF THE SOFTWARE PROJECT MANAGEMENT PLAN . . . . . . . . 1.2 SCOPE OF THE SOFTWARE PROJECT MANAGEMENT PLAN . . . . . . . . . 1.3 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.1 P r o j e c t P u r p o s e / P r o b l e m D e f i n i t i o n . . . . . . . . . . . 1.3.2 P r o j e c t B a c k g r o u n d H i s t o r y . . . . . . . . . . . . . . . 1.3.3 P r o j e c t S c o p e . . . . . . . . . . . . . . . . . . . . . 1.3.4 P r o j e c t O b j e c t i v e s . . . . . . . . . . . . . . . . . . . 1.3.5 P r o j e c t S t r a t e g y . . . . . . . . . . . . . . . . . . . . 1.3.6 P r o j e c t D e l i v e r a b l e s . . . . . . . . . . . . . . . . . .

1.4 EVOLUTION OF THE SOFTWARE PROJECT MANAGEMENT PLAN . . . . . . . 1.5 ACRONYMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . 1.6 DEFINIT IONS . . . . . . . . . . . . . . . . . . . . . . . . . .

2.0 PROJECT ORGANIZATION . . . . . . . . . . . . . . . . . . . . . . . . 2.1 PROJECT PROCESS MODEL . . . . . . . . . . . . . . . . . . . . .

2.1.1 P r o j e c t P r o c e s s M o d e l . . . . . . . . . . . . . . . . 2.2 ORGANIZATIONAL STRUCTURE . . . . . . . . . . . . . . . . . 2.3 ORGANIZATIONAL BOUNDARIES AND INTERFACES . . . . . . . . 2.4 PROJECT RESPONSIB IL IT IES . . . . . . . . . .

3.0 MANAGERIAL PROCESS . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 MANAGEMENT OBJECTIVES AND PRIORIT IES . . . . . . . . . . . . . 3.2 ASSUMPTIONS. DEPENDENCIES AND CONSTRAINTS . . . . . . . . . . .

3.2.1 A s s u m p t i o n s . . . . . . . . . . . . . . . . . . . . . 3.2.2 D e p e n d e n c i e s . . . . . . . . . . . . . . . . . . . . . 3.2.3 C o n s t r a i n t s . . . . . . . . . . . . . . . . . . . .

3.3 R I S K MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . 3.4 MONITORING AND CONTROLLING MECHANISMS . . . . . . . . . . . . . 3.5 STAFFING PLAN . . . . . . . . . . . . . . . . . . . . . . 3.6 ACCEPTANCE CRITERIA . . . . . . .

4.0 TECHNICAL PROCESS . . . . . . . . . . 4.1 METHODS. TOOLS AND TECHNIQUES . . 4.2 SOFTWARE DOCUMENTATION . . . . . 4.3 DATA MANAGEMENT . . . . . . . . .

5.0 SCHEDULE AND BUDGET . . . . . . . . . . . . .

. .

. .

. .

. .

5 5 5 5 5 5 6 6 6 7 7 7 8

9 9 9 9 9 11

13 13 13 13 14 14 14 15 16 16

17 17 17 17

17

6.0 SOFTWARE VERIFICATION AND VALIDATION PLANNING . . . 17

3

WHC.SD.WM.SDP.013. Rev . 0

7 . 0 REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

LIST OF FIGURES

2 - 1 Organization Chart . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 -1 Staffing Plan f o r the VIOON Project . . . . . . . . . . . . . . . . 16

5 - 1 VIDON Project Work Breakdown Structure . . . . . . . . . . . . . . . 19

4

WHC-SD-WM-SDP-013, Rev. 0

VISUAL IMAGE DIGITAL OBJECT NETWORK

1.0 INTRODUCTION

1.1 PURPOSE OF THE SOFTWARE PROJECT MANAGEMENT PLAN

This document, the Software Project Management Plan (SPMP), describes the management and the implementation strategy f o r the Visual Image D i g i t a l Object Network (VIDON) Project , an Approval Designator 3Q system. It i s intended t o be used as a guidel ine by both the customer, the management, and the VIDON development team t o def ine the VIDON scope o f work and t o provide a de ta i led plan on how the work i s t o be accomplished.

1.2 SCOPE OF THE SOFTWARE PROJECT MANAGEMENT PLAN

This SPMP covers the overal l p ro jec t object ives, strategy, del iverables, organization, management process, technical process, schedule,. budget, and v e r i f i c a t i o n and va l ida t ion (V&V) a c t i v i t i e s f o r the VIDON Project . The scope includes a l l a c t i v i t i e s associated w i th the VIDON. Project . including, but not l i m i t e d t o j u s t the software.

i

i I i

1.3 OVERVIEW

1.3.1 Project Purpose/Problem De f in i t i on

The purpose o f the VIDON p ro jec t i s t o develop and implement a d i g i t a l photography l i b r a r y on the Hanford Local Area Network (HLAN)for the Tank Waste Remediation System Divis ion (TWRS) I n Tank Imaging a c t i v i t i e s . The VIDON capab i l i t y w i l l eventually be expanded t o a Sitewide service. The VIDON process w i l l a lso replace the current manual processes f o r co l l ec t i ng and s to r ing waste tank images (photographs, video simple frame grabs).

1.3.2 Project Background H is to ry

The VIDON software was o r i g i n a l l y created as an Advanced Revelation System i n 1992 t o provide a b i l l i n g and job t racking capab i l i t y f o r the

5

WHC-SD-WM-SDP-013, Rev. 0

Photo/Audio Visual Organization w i th in Boeing Computer Services, Richland (BCSR). The system was l a t e r expanded t o provide an image capture and r e t r i e v a l data base capab i l i t y u t i l i z i n g a SOL sequel server plat form. budget constraints on cap i ta l expense, the computer hardware required t o operate the system was not purchased, and the new capab i l i t i es were not act ivated. When the TWRS I n Tank Imaging a c t i v i t i e s surfaced the requirement t o capture and re t r i eve photo and video images, a BCSR/WHC team was formed t o evaluate the requirements. The team recommended using the V I D O N SQL data base as pa r t o f a four phase plan (see 1.3.5 Project Strategy).

Due t o

1.3.3 Pro jec t Scope

The short term scope o f the VIDON Project i s t o capture and control physical media (photo and video images) and provide an automated image capture and r e t r i e v a l data base system f o r the TWRS I n Tank Image a c t i v i t y . The long term scope o f the VIDON p ro jec t i s t o develop and implement a Sitewide d i g i t a l photography 1 i brary avai 1 ab1 e through the HLAN.

1.3.4 Pro jec t Objectives

The object ives o f the VIDON Project are t o provide TWRS w i th the fo l lowing:

conf igurat ion control o f physical waste tank images (photo and video)

0 the automated process t o capture and re t r i eve waste tank images (photo and video simple frame grabs)

0 provide a Sitewide d i g i t a l image l i b r a r y capab i l i t y ava i lab le through the HLAN.

1.3.5 Project Strategy

The overa l l VIDON p ro jec t strategy i s t o , p r i o r i t i z e such as inventory ex i s t i ng photos and meta data. Project phases are used t o i d e n t i f y a l l a c t i v i t i e s o f the VIDON Project . ex i s t i ng photo and meta data, p u l l and capture re la ted photo negatives, rep1 ace missing photos, determi ne customer and BCSR requi red expenditures, and create a con t ro l led process f o r the ongoing capture o f waste tank physical image data photo.

Phase I was i n i t i a t e d t o inventory the

Phase I1 i s intended t o u t i l i z e the SQL data base and

6

WHC-SD-WM-SDP-013. Rev. 0

create a working prototype tha t would provide immediate but l i m i t e d customer capab i l i t i es . VIDON SQL data base i n order t o provide f u l l customer capab i l i t i es . Phase I V w i l l be determined by customer spec i f i c requirements (software modif icat ions) and usage needs (hardware upgrades) w i th the i n ten t i on t o po ten t i a l l y provide a Commercial Of f - the-she l f product. so lu t ion f o r video VHS storage and refurbishing video inventory and meta data and image capture. This p ro jec t w i l l be scheduled t o be completed i n FY96. I f the pro jec t grows i n t o a mult i -year p ro jec t , t h i s SPMP w i l l be revised each f i s c a l year t o update the plan and schedule t o comply w i th the mul t i -year plan.

Phase I11 t o perform a software app l ica t ion upgrade t o the

This phase would provide a long term

1.3.6 Project del iverables

0 Working prototype system 0 Working production system 0 Project management plan 0 User documentation.

1.4 EVOLUTION OF THE SOFTWARE PROJECT MANAGEMENT PLAN

A l l changes or revis ions t o t h i s SPMP w i l l be reviewed and approved by the VIDON Project Team, which consists o f the WHC Customer Organization Cognizant Engineer and POC, the BCSR VIDON Project Owner, the BCSR V I D O N Technical Manager, the BCSR VIDON Senior Technical Advisor, the BCSR V I D O N Administrat ive Lead, the BCSR VIDON Document & Records Management Lead, the BCSR VIDON Software Development/Database Lead, the BCSR V I D O N Software Engineer, the BCSR V I D O N Photo Processing Lead and the BCSR VIDON Video Processing Lead. These changes w i l l be sent out as a cc:mail message, which w i l l document the proposed change and the act ion taken, o r as a review comment record (RCR), which w i l l be used f o r fu tu re rev is ion o f the SPMP. These messages and RCRs w i l l be kept i n the VIDON p ro jec t f i l e . Weekly status reports w i l l keep the customer and the VIDON Project Team up t o date.

1.5 ACRONYMS AND ABBREVIATIONS

BCSR CAP DAC DSA ECN

Boeing Computer Services, Richland, Inc. Cost Account P1 an Data Administration Council Data Standards and Administration Engineering Change Notice

7

WHC-SD-WM-SDP-013. Rev. 0

EDT HLAN POC QA RCR SACS SPMP SRS TWRS V&V VIDON WHC

Engineering Data Transmittal Hanford Local Area Network Point o f Contact Qua l i t y Assurance Review Comment Record Surveil lance Analysis Computer System Software Project Management Plan Software Requirements Speci f icat ion Tank Waste Remediation System Ver i f i ca t i on and Val i da t i on Visual Image D ig i ta l Object Network Westinghouse Hanford Company

1.6 DEFINITIONS

A c t i v i t y i s a major u n i t o f work t o be completed i n achieving the object ives o f a software pro jec t . An a c t i v i t y has precise s ta r t i ng and ending dates, incorporates a set o f tasks t o be completed, consumes resources, and resu l ts i n work products. An a c t i v i t y may contain other a c t i v i t i e s i n a h ie rarch ica l manner.

- BCSR i s a subcontractor t o the Westinghouse Hanford Company. the Information Resource Management tasks.

Customer i s the ind iv idua l o r organization tha t speci f ies and accepts the pro jec t del iverables. The customer may be in te rna l o r external t o the parent organizat ion o f the pro jec t , and may or may not be the end user o f . t h e software product. A f inanc ia l t ransact ion between customer and developer i s not necessar i ly impl ied.

Oual i tv A f fec t i ns Software i s software tha t has been confirmed t o comply w i th spec i f ied requirements (WHC-CM-4-2, Section QR 19 .0) i n an operation/ production envi ronment .

Oua l i t v Assurance (QA) i s the systematic actions necessary t o provide adequate confidence t h a t a mater ia l , component, system, process, o r f a c i l i t y performs s a t i s f a c t o r i l y , o r as planned i n service.

Software Pro.iect Manasement Plan (SPMP) i s the control 1 i ng document t h a t i d e n t i f i e s a l l technical and managerial p ro jec t functions, a c t i v i t i e s and tasks associated w i th a software pro jec t .

BCSR performs

a

WHC-SD-WM-SDP-013, Rev 0

Software Reaui rements Speci f i cat1 on (SRS) documents essenti a1 requirements (functions, performances, design constraints, and attributes) of the software and i t s external interfaces

Verification and Validation ( V & V ) i s the process o f assuring the quality of the Software Development Life Cycle products.

Westinqhouse Hanford Companv (WHC) i s the current s i t e operations contractor for the Hanford s i t e .

2.0 PROJECT ORGANIZATION

2.1 PROJECT PROCESS MODEL

The project process model for the VIDON Project follows the s tandard systemlsoftware l i f e cycle model contained i n WHC-CM-3-10

I

I 2.2 ORGANIZATIONAL STRUCTURE 1

Organizational chart, page 10, Figure 2 2

2.3 ORGANIZATIONAL BOUNDARIES AND INTERFACES

Milestone tracking and reporting of the VIDON Project will be accomplished via scheduled VIDON Project Team meetings, minutes of the scheduled project meetings, scheduled milestone tracking in the project meetings, and periodic briefings t o BCSR Senior management and the WHC Cognizant Manager. system development is necessary t o assure a l l individuals are kept well informed of upcoming milestones and are aware of the tasks expected t o be completed.

1 Close communication among a l l departments involved in the

9

VIDON Development Project Structure

BCSR MSA H. A. Wixson

W H CITWRIT FP

BCSR ISS L. M. Ollero

.-....~ N. E. Kenny

VlDON Project Owner

BCSR VIS 0. K. Griswold

VlDON Technical Manager VlDON Senior Technical Advisor ViDON Customer POC

8. H. McMiiian J. R. Phillips J. H. Huber

BCSR MSA

VlDON Document & Records

BCSR DRM K. M. GatherumIS. G. Gelchell S. S. Upson 8. M. Sullivan E. G. Quarnstrom

VlDON Software Engineer SACS Interlace

10/4/95

P c

WHC-SD-WM-SDP-013, Rev. 0

2.4 PROJECT RESPONSIBILITIES

Project respons ib i l i t i es as re la ted t o the VIDON Project are l i s t e d bel ow.

CUSTOMER ORGANIZATION :

WHC Coanizant Manaaer ( M . J . Holm)--The WHC Cognizant Manager f o r t he I n Tank Imaging a c t i v i t i e s i s responsible f o r : necessary WHC p ro jec t funds f o r the VIDON Project , both expense and cap i ta l ; review and approval o f WHC p ro jec t funds and milestones (schedules) v ia the WHC Cost Account Plan (CAP); and review and approval o f supporting documentation.

WHC Coanizant Enaineer and Customer POC ( J . H. Huber)--The WHC Cognizant Engineer and Customer Point o f Contact (POC) f o r the I n Tank Imaging a c t i v i t i e s i s responsible f o r : (schedules); providing status and report ing milestones and CAP costs t o WHC; reviewing and approving supporting documentation; approving changes t o operational documentation and conf igurat ion; ensuring t h a t appropriate Approval Designators are i d e n t i f i e d f o r a l l a c t i v i t i e s : in te r fac ing w i t h VIDON team; attending weekly status review meetings w i th the VIDON team; i d e n t i f y i n g follow-on a c t i v i t i e s : i n i t i a t i n g CAP change requests and providing system acceptance a t p ro jec t completion.

obtaining

p r i o r i t i z i n g VIDON p ro jec t milestones

PERFORMING ORGANIZATION:

VIDON Pro.iect Owner ( D . K . Griswoldl--The VIDON Project Owner i s responsible f o r : the overal l VIDON p ro jec t completion; being the po in t o f contact customer in te r face , BCSR management and supporting organizations; obtaining necessary BCSR p ro jec t funds, both expense and cap i ta l ; approval o f supporting documentation, budgets, milestones (schedules); resource a l loca t ion and u t i l i z a t i o n . When changes a f fec t projects tha t VIDON interfaces w i th , the VIDON Project Owner i s responsible f o r contacting the af fected user contact and obtaining t h e i r approval regarding proposed changes i n design or operation.

VIDON Technical Manaaer ( B . H. McMil1an)--The V I D O N Technical Manager i s responsible f o r the overal l software development and in teg ra t i on o f the VIDON Project , including software, hardware and physical data; providing labor resources and administrat ive support; preparing a cost , schedule, resource estimate re la ted t o the overa l l i n teg ra t i on of the pro jec t .

11

WHC-SD-WM-SDP-013, Rev. 0

VIDON Senior Technical Advisor ( J . R . Phi l l iDs)--The VIDON Senior Technical Advisor i s responsible f o r providing ADP technical hardware, software and system archi tecture consul tat ion.

VIDON Administrative Pro.iect Lead ( 6 . D. Bvron)--The VIDON Administrat ive Project Lead i s responsible f o r administering the cost plan, creat ing and con t ro l l i ng the schedule/milestones. scheduling the weekly p ro jec t review meetings, documenting the meeting minutes and d i s t r i bu t i ng act ion items, con t ro l l i ng the project . f i l e s and resources o f the pro jec t , maintaining supporting documents i n a current status and coordinating the w r i t i n g o f the pro jec t documents.

VIDON Document & Records Manasement Lead (6. M. Sul l ivan)--The V I D O N Document & Records Management Lead i s responsible f o r establ ishing a working master f i l e . This w i l l be accomplished by establ ishing the i n i t i a l baseline inventory o f photographs cur ren t ly under the j u r i s d i c t i o n o f the customer; establ ishing a secured loca t ion f o r photo f i l e s i n the 200E Area; secure, maintain, inventory, update and control the t racking o f photos t o customer f o r t h e i r use based upon the de l i very o f said photos by the Photo Processing Organization.

VIDON Software Develoment/Database Manaaement Lead ( E , G . 0uarnstrom)--The VIDON Software Development/Database Management Lead i s responsible f o r the design, coding, u n i t t es t i ng o f the software implementation, production tes t ing , and overa l l qua l i t y o f the system del iverables. Includes actual software coding tasks as wel l as input t o a l l del iverable documents. Coordinates the BCSR s t a f f i n work assignments and serves as a po in t o f contact between the user organization and the VIDON development team.

VIOON Software Enaineer (H . A . Wixsonl--The VIDON Software Engineer i s responsible f o r the design, coding and u n i t t es t i ng o f the software. Tasks also include the formulation o f a l l del iverable documents and ongoing m a i ntenance o f customer software.

V I D O N Photo Processins Lead ( K . M . Gatherum/S. G . Getchel1)--The VIDON Photo Processing Lead i s responsible f o r implementation o f production systems re la t i ng t o photo images and the development o f desk procedures f o r photo image capture and associated data entry.

VIDON Video Processins Lead (S . S . Upson)--The VIDON Video Processing Lead i s responsible f o r implementation o f production

12

WHC-SD-WM-SDP-013, Rev. 0

systems re la t i ng t o video images and the development o f desk procedures f o r video image capture and associated data entry

SACS In te r face ( L . M . 0 l le ro ) - -The SACS In te r face Representative i s responsible f o r assuring t h a t design decisions made i n t h i s p ro jec t do not preclude an in te r face t o SACS.

OTHER SUPPORTING PERSONNEL/ORGANIZATIONS:

Data Standard and Administration (DSAl--The DSA provides communication w i th the Data Administration Council (DAC) and assists the VIDON Project i n compliance w i th the WHC Data Administration Standards.

Oual i t v Assurance--The Qual i ty Assurance person i s responsible f o r reviewing and approving software documentation i n accordance w i t h WHC Standard Engineering Practices, WHC Qual i ty Assurance, and WHC Software Practices f o r Approval Designator 3Q systems.

3.0 MANAGERIAL PROCESS

3.1 MANAGEMENT OBJECTIVES AND PRIORITIES

The VIDON Project i s viewed as a h igh -p r io r i t y p ro jec t by BCSR/WHC due t o the customer's requirement t o capture and re t r i eve visual images as pa r t o f the I n Tank Imaging a c t i v i t i e s and i t s Approval Designator 3Q status. Management Requirements and Procedures, WHC-CM-1-3, MRP 5.46 and MRP 5.43 the V I D O N Project i s determined t o have an Approval Designator o f 3Q.

Per

The VIDON Project i s reviewed monthly by the BCSR Media Management Systems management and undergoes scheduled pro jec t team meetings w i th the WHC customer and BCSR. Both the administrat ive and technical p ro jec t managers meet regu la r ly w i th BCSR management on the VIDON p ro jec t status.

3.2 ASSUMPTIONS, DEPENDENCIES, AND CONSTRAINTS

3.2.1 Assumptions

The fol lowing are the basic assumptions o f the pro jec t :

13

WHC-SD-WM-SDP-013, Rev. 0

0 The ad hoc query tools t h a t interface t o the selected relational database will be available

0 The budget for the VIDON Project will be available

0 The current hardware will be used for Phase I and Phase I1 of the VIDDN system

0 Additional hardware and software upgrades will be provided for development acti v i t i e s when needed.

3.2.2 Dependencies

The following have been identified as the external dependencies of the project:

0 Fulfilled commitment dates made by supplying vendors for equipment

0 Continued communication between VIDON workstations and Hanford Local Area Network (HLAN)

0 Continued funding for the project until completion

3.2.3 Constraints

There are no current resource, budget, schedule or technical constraints a t this time.

3.3 RISK MANAGEMENT

The development risks listed below have been'identified for the VIDON Project. The occurrence of any of these risks could impact the timely completion of the project and/or customer acceptance of the system.

0 Availability of resources (software. hardware, and training) necessary t o support deli verables.

Contingency Plan: and borrow hardware from other organizations.

Submit change request t o get more project funding

14

WHC-SD-WM-SDP-013. Rev. 0

0 Avai 1 abi 1 i ty of resources (personnel 1 necessary t o support deliverables.

Contingency Plan: personnel needed for the project and t o gain time for project act ivi t ies .

Use high management project profile t o gain

0 Reorganization of WHC customer and/or BCSR performing organizations.

Contingency Plan: organization.

Make the project independent of a single

0 Major changes i n user needs, requirements, and/or scope of work.

Contingency Plan: requi rements, project schedule, and/or scope of work.

Submit change request t o change user's needs,

0 Unanticipated diff icul t ies i n technical areas.

Contingency Plan: Use premium technical support from vendor company and attend training courses for those technical areas.

Changes in project funding

Contingency Plan: Submit change request t o get project funding requi red.

3.4 MONITORING AND CONTROLLING MECHANISMS

The monitoring and the control 1 i ng of the project development wi 11 be accompl i shed through the V&V act ivi t ies , peer reviews by BCSR and Westi nghouse personnel, and scheduled project meeting minutes. The scheduled project meeting minutes will summarize the progress of the VIDON schedules and tasks.

Changes t o documentation as well as requirements, design and software are documented, evaluated and approved. change information will be documented, evaluated and approved.

Software development problems and detai 1

15

WHC-SD-WM-SOP-013. Rev. 0

3.5 STAFFING PLAN

The S ta f f i ng Plan describes the Performing Organization and Supporting Organization personnel who are d i r e c t l y involved i n the V I D O N Project . The pos i t ions i n the below s t a f f i n g Plan are described i n Section 2.2, Organizational Structure, and Section 2.4, Project Responsi b i 1 i t i e s .

Figure 3-1. S ta f f i ng Plan f o r the VIDON Project .

I NUMBER OF PERSONS I POSITION

I 1 1 BCSR Manager

I 1 I BCSR Administrative Project Lead

I 1 I BCSR Technical Project Manager

I 2 I BCSR Software Engineers

I 1 (par t t ime) I DSA

I 1 (par t t ime) Qual i ty Assurance

Safety

BCSR Senior Technical Advisor

BCSR DRM Lead

El(pai t time) I BCSR Photo Processing Lead

I 1 (par t time) I.BCSR Video Processing Lead

I 1 ( P a r t t ime) I SACS Interface

3.6 ACCEPTANCE CRITERIA

The acceptance c r i t e r i a w i l l be contained i n the SRS document.

I f there are any changes t o the acceptance c r i t e r i a , a OS1 w i l l be wr i t t en t o describe these changes, then approved and signed o f f by the customer and performing organizations , inserted w i t h the acceptance c r i t e r i a D S I i n the Project F i l e e n t i t l e d Acceptance C r i t e r i a , and revised i n the SRS.

These changes w i 11 be documented,

16

WHC-SD-WM-SDP-013. Rev. 0

4.0 TECHNICAL PROCESS

4.1 METHODS, TOOLS AND TECHNIQUES

The VIDON Project w i l l use a var ie ty o f too ls f o r the administrat ive and technical port ions o f the p ro jec t . o f the software packages t o be used f o r p ro jec t management. A combination o f Visual Basic language, SQL server and Image Kni fe are the technical t oo l s f o r the pro jec t .

Wordperfect and MicroSoft Project are some

4.2 SOFTWARE DOCUMENTATION

VIDON w i 11 be documented according t o WHC Qua 7 i ty Assurance (WHC-CM-4-2, Section QR 19.0). WHC Software Practices (WHC-CM-3-10), A l l documentation w i l l be released using the WHC Engineering D a t a Transmittal (EDT) o r Engineering Change Notice (ECN) system and procedures as ou t l ined i n Standard Engineering Pract ices, WHC-CM-6-1. Sect ion EP-1.7, "Engineering Document Approval and Release Requirements.

4.3 DATA MANAGEMENT

The V I D O N Project fo l lows the Data Administration Standards, WHC-CM-2-6, Section 4 .0 , "Data Administrat ion System Review Process" and Software Pract ices, WHC-CM-3-10. Section 5 .0 , "Data Management, " f o r compliance purposes.

5.0 SCHEDULE AND BUDGET

See page 19 f o r Figure 5.1, V I D O N Project Work Breakdown Schedule

6.0 SOFTWARE VERIFICATION AN0 VALIDATION PLANNING

Peer reviews and formal t es t i ng reviewed by QA w i l l be performed.

17

WHC-SD-WM-SDP-013. -Rev. 0

7.0 REFERENCES

WHC-CM-3-10, Software Practices, by Westinghouse Hanford Company.

WHC-CM-4-2, QR 19.0, Oual i tv Assurance, by Westinghouse Hanford Company.

18

0

2

3

- 4

5

8

- 7

8

0

> E

Dellver working prolotype

Place TWRS hard copy photos under conflgunillon conlrol

Complete lnvenlory of exlsllng In-Tank pholos

lnlegrale VIDON prololype lnlo M R S envlronment

lnslall new file server/caplure slallor equlpmenl .

Input photo baseline lnlo VlDON syslem

Establish DRM electronic check In/oul servlce

System test and acceptance

m 0 I a

v, I x n

n

7 v, I

V I 3

10 lnslall VIDON producllon syslem 1

September

\;I

811

October I November I December

115

April

3/29

2

3/29

! i

I , i !

. .. . .... - . .. . .-,-,-..,I .. -