Nu-Logos
Contact

Platform A shared engineering information layer, without replacing your tools.

Nu-Logos builds a traceable digital structure across engineering information that already lives in different tools and organizations. It does not replace analysis codes, CAD/CAE tools, or engineering judgment. Through connectors, it generates the inputs each tool needs and imports the results, preserving the lineage of every design decision.

Diagram with Nu-Logos at the center as the single source of truth, connecting five domains: requirements, thermal-hydraulics, geometry and configuration, safety analysis, and structural integrity. Each domain exchanges inputs, results, or synchronization with its tools: requirements management (e.g., DOORS, Polarion), thermal-hydraulic codes (e.g., MARS-KS, SPACE), 3D CAD (e.g., CATIA, SolidWorks), safety analysis codes (e.g., RELAP5, TRACE), and structural analysis codes (e.g., ANSYS, ABAQUS).

From requirements to verification, unbroken

Requirement and regulatory traceability

Links each requirement to the systems, components, parameters, analyses, and verification evidence that support it.

Engineering data lineage

Tracks where an engineering value came from, which model and version produced it, and where it is used.

Change impact analysis

Identifies the elements, analyses, and evidence that may be affected when a design parameter changes.

Engineering tool connectors

Connects existing engineering tools and analysis codes to a common information structure.

Verification evidence

Links inputs, model versions, calculations, results, reviews, and verification status as structured evidence.

Controlled engineering baseline

Maintains the relationships between current data, reviewed information, approved values, and their supporting evidence.

Connect engineering knowledge without centralizing proprietary assets.

Each organization keeps its detailed CAD/CAE data, proprietary solvers, internal methods, and manufacturing know-how in its own private domain. Nu-Logos does not copy source files to a central server. It connects only the engineering context the project has agreed to share: common identifiers, interfaces, approvals, verification status, evidence references, versions, and baselines.

The Nu-Logos shared engineering information layer at the center, connected in both directions through connectors to a system/plant designer, an analysis organization, an equipment supplier, and an owner/EPC, each keeping its own private domain.
System / Plant Designer
Private Domain
CAD / CAE / System Models / IP
Analysis Organization
Private Domain
Models / Solvers
Methods / IP
Nu-Logos
Shared Engineering Information Layer
Common IDs / Interfaces / Approvals
Verification Status / Evidence / Baselines
Equipment Supplier
Private Domain
Component Design
Manufacturing Data / QA
Owner / EPC
Private Domain
Requirements / Configuration / Records
Connector
Connector
Connector
Connector

We are looking for engineering workflows to validate together.

We welcome inquiries about pilot projects, technology partnerships, and anything else by email.

Email us contact@nu-logos.com