FACILEX® ATOMIC

Design Basis Information Software for Nuclear Quality Assurance

Establish and maintain traceable design basis information connecting requirements, design inputs, calculations, structures, systems and components, and implementing documents.

Preserve the technical basis for facility configuration as designs evolve, modifications are implemented and source requirements change throughout the facility lifecycle.

Book a Meeting

The Challenge

Design basis information must remain connected to the facility it defines.

Nuclear facilities accumulate large volumes of requirements, calculations, specifications, drawings, analyses, equipment information and other technical records throughout their lifecycle.

The challenge is not simply controlling those documents. Organizations must understand which requirements apply, why particular design decisions were made, which structures, systems and components are affected, and where those requirements are implemented.

As modifications, regulatory commitments and operating experience introduce change, broken relationships between requirements, design information and physical configuration can create configuration-management vulnerabilities that may remain hidden until the information is needed.

Design Basis Information must answer:

What requirement or design input establishes the basis?
Why does the requirement exist?
Which structures, systems or components does it affect?
Where is the requirement implemented?
What analyses, calculations and documents support it?
Is the information consistent with the current facility configuration?

Why It Matters Now

▤

Requirements become traceable

Connect regulatory, safety, functional and design requirements to the information and SSCs they govern.

↔

Relationships survive document boundaries

Preserve technical relationships across calculations, specifications, drawings, procedures and equipment records.

◆

Design intent remains visible

Capture the technical basis and assumptions behind important requirements rather than relying on isolated documents.

✓

Configuration can be verified

Support comparison of design requirements, facility configuration and controlled implementing information.

△

Change impact becomes clearer

Identify related requirements, SSCs and documents that may require evaluation when a change is proposed.

◎

Knowledge remains accessible

Preserve structured engineering knowledge as projects transition into operation and experienced personnel change.

Design Basis Information Lifecycle

A configurable lifecycle establishes authoritative design basis information, validates its technical relationships and maintains alignment as requirements and facility configuration change.

Identify

Identify applicable requirements, design inputs and source information.

Establish

Define the design basis, assumptions, criteria and affected SSCs.

Validate

Confirm technical accuracy, completeness and supporting relationships.

Approve

Complete required technical review and authorization of the information.

Implement

Incorporate approved requirements into affected documents and configuration.

Verify

Confirm alignment between approved requirements and implementation.

Maintain

Preserve design basis integrity as requirements and configuration change.

Configured for the Way Your Program Operates

▤

Design Requirement Records

Capture requirements, design inputs, assumptions, criteria and their authoritative source information.

⌘

SSC Relationships

Associate design requirements with affected structures, systems, components and functional locations.

↔

Requirement Traceability

Maintain relationships from source requirements through design outputs and implementing information.

◆

Technical Basis & Assumptions

Preserve calculations, analyses, assumptions and engineering rationale supporting important design decisions.

△

Change Impact Identification

Surface related requirements, SSCs and documents when configuration changes are evaluated.

✓

Verification & Status Control

Track review, approval, implementation and verification status throughout the information lifecycle.

Regulatory & Program Anchors

Maintain the technical basis behind the approved configuration.

10 CFR 50 Appendix A

10 CFR 50 Appendix B

Criterion III — Design Control

ASME NQA-1

Design Control

Configuration Management

Design Requirements

Safety Basis

Design Basis Information Connects With

Design information becomes more valuable when its relationships remain intact.

FACILEX® ATOMIC connects design basis information with the configuration, safety functions, changes and regulatory requirements that depend upon it.

⌘

SSC Data Integration Connect requirements and design information to structures, systems and components.

◆

Credited Controls & Safety Functions Connect credited capability to its supporting design requirements and basis.

↔

Change Control Evaluate modifications against affected design requirements and assumptions.

Licensing & Regulatory Trace regulatory requirements and commitments into applicable design information.

One application. Part of one connected management system.

FACILEX® Design Basis Information is one of 21 configurable applications within FACILEX® ATOMIC. Design requirements can remain connected to SSCs, credited safety functions, regulatory requirements and configuration changes so that the technical basis evolves with the facility rather than becoming separated from it.

Explore all 21 FACILEX® ATOMIC applications →

See Design Basis Information in FACILEX® ATOMIC

Bring us your current process.

We can map your design requirements, design basis records, SSC relationships, source documents and configuration controls to a structured FACILEX® ATOMIC information model.