2025-09-22 14:54:12 -04:00
|
|
|
.. need to design a way to bring in multiple glossary data sources
|
|
|
|
|
so that we can use the global shared glossary + our project
|
|
|
|
|
specific glossary
|
|
|
|
|
|
|
|
|
|
#########
|
|
|
|
|
Glossary
|
|
|
|
|
#########
|
|
|
|
|
|
|
|
|
|
Glossary
|
|
|
|
|
|
|
|
|
|
.. glossary::
|
|
|
|
|
|
2025-12-12 09:40:02 -05:00
|
|
|
Configuration Management
|
|
|
|
|
The process of identifying and documenting the characteristics of a
|
|
|
|
|
facility's structures, systems and components (including computer
|
|
|
|
|
systems and software), and of ensuring that changes to these
|
|
|
|
|
characteristics are properly incorporated into the facility
|
|
|
|
|
documentation. :cite:p:`agencyInformationTechnologyNuclear2010`
|
|
|
|
|
|
|
|
|
|
Controlled document
|
|
|
|
|
Documents whose content is maintained uniform among the copies by an
|
|
|
|
|
administrative control system. The goal of controlling documents is to
|
|
|
|
|
ensure that work is performed using approved current information, not
|
|
|
|
|
obsolete information. Important documents to be controlled are uniquely
|
|
|
|
|
identified (including revision number, date, and specific copy number),
|
|
|
|
|
and distribution is formally controlled. Revisions to controlled
|
|
|
|
|
documents are uniquely tracked and implemented, including mandatory page
|
|
|
|
|
replacements and receipt acknowledgment. Controlled documents typically
|
|
|
|
|
include procedures for operations, surveillance, and maintenance, and
|
|
|
|
|
safety basis documents such as the SAR, and hazard and accident
|
|
|
|
|
analyses. :cite:p:`agencyInformationTechnologyNuclear2010`
|
|
|
|
|
|
|
|
|
|
Design basis
|
|
|
|
|
The range of conditions and events taken explicitly into account in the
|
|
|
|
|
design of a facility, according to established criteria, such that the
|
|
|
|
|
facility can withstand them without exceeding authorized limits by the
|
|
|
|
|
planned operation of safety systems.
|
|
|
|
|
:cite:p:`agencyInformationTechnologyNuclear2010`
|
|
|
|
|
|
|
|
|
|
Design control
|
|
|
|
|
Measures established to ensure that the information from design input
|
|
|
|
|
and design process documents for structures, systems, and components is
|
|
|
|
|
correctly translated into the final design.
|
|
|
|
|
:cite:p:`agencyInformationTechnologyNuclear2010`
|
|
|
|
|
|
2025-09-22 14:54:12 -04:00
|
|
|
Document
|
|
|
|
|
A written collection of information, instructions, drawings,
|
|
|
|
|
specifications, etc. that is *maintained* throughout the
|
|
|
|
|
design/operation/decommissioning of the facility. Differs from a
|
|
|
|
|
*record* in that it is expected to be *maintained* by revisions as
|
|
|
|
|
needed. See :need:`R_APPB_45`
|
|
|
|
|
|
|
|
|
|
Record
|
|
|
|
|
A written collection of information providing evidence of
|
|
|
|
|
work that was done at a specific time. Records are expected
|
|
|
|
|
to be *retained* for a certain retention period, e.g.
|
|
|
|
|
for the lifetime of the plant or for a given number of years.
|
|
|
|
|
See :need:`R_APPB_79`
|
|
|
|
|
|
|
|
|
|
|