FSAR Configuration Control at PPL Susquehanna, LLC. 2000 CMBG Tarrytown, NY. Keith A. Reinsmith
Susquehanna FSAR Maintenance and Control History • Maintained solely by Licensing organization. • Sections/ Figures/ Tables (S/F/Ts) affected by changes updated biannually for release to NRC. • All tracking and storage of changes done hardcopy within Licensing group. • Limited access to “as-built” FSAR outside Licensing.
Rationale for Change • Create a control system utilizing our existing Configuration Control Data Base (CCDB) to provide for real time configuration control of FSAR contents and changes. • Make FSAR and changes more accessible to users. • Allow levelizing of resources required to maintain the FSAR.
Approach • Control contents of the FSAR at the S/F/T level rather than as a whole document. • Issue and track changes (Licensing Document Change Notices, LDCNs) uniquely against each affected S/F/T. • Use our CCDB to track this information. • Update S/F/T on an ongoing basis rather than biannually.
Tools • Nuclear Information Management System (NIMS) Document Management Database (our CCDB) • MSWord • Filenet Digital Imaging System • CAD System
Process Prerequisites • Create a unique record in CCDB (NIMS) for each FSAR S/F/T. • Link the Filenet digital image for each S/F/T to the appropriate CCDB record. • Link the MSWord file for each S/F/T to the CCDB record. • Create unique records in the CCDB for each LDCN and link to each S/F/T affected.
Process Prerequisites (Cont.) • For already issued LDCNs, scan and link the LDCN image to each associated LDCN record in the CCDB. • Status LDCN records in NIMS based on where each LDCN currently is in the workflow (Preliminary, Issued, Posted, Incorporated.)
New Process • Generate change records in CCDB at point of LDCN initiation. Track against each affected S/F/T. Status each LDCN record as “Preliminary”. • When LDCN is completed, update CCDB to add/delete/modify any LDCN records affected. • Approved non-mod changes are scanned and statused as “Posted”.
New Process (cont.) • Mod related LDCNs are statused as “Issued” pending installation of the Mod and scanned for viewing in Filenet. • Mod related LDCNs are “Posted” only after the mod is declared operational (as-built). • Mod and non-mod LDCNs will be physically incorporated in affected S/F/T’s when statused as “Posted”
New Process (cont.) • Revised S/F/T will be issued independently on an ongoing basis. • S/F/Ts will be issued in electronic form (raster image and Word File) for users access through NIMS. • Full scale FSAR revision to the NRC will be a snapshot of the latest rev of S/F/Ts at the time of FSAR publication.
Benefits to New Process • FSAR will be managed like other configuration controlled information sources (drawings, procedures). • Users will have ready access to contents of FSAR and changes. S/F/Ts and LDCNs are viewable and text searchable in NIMS.
Benefits to New Process (cont.) • Updates will be more easily done and cost to issue major revisions reduced. • Process will allow more frequent publication of the FSAR to the NRC.
Future Plans • Develop ability to issue FSAR updates to NRC in electronic form (initially CD). • Implement process to issue updates to NRC on more frequently than biannual update cycle. • Investigate improvements in information search/ retrieval for FSAR contents.