Skip to main content

Reusable Libraries & Per-line Specifications

This page covers two productivity features: saving your own materials, sections, specifications, and soil profiles to a personal library that loads into any project, and applying different design conditions (including design code) to different lines in the same model.

Per-line Specifications

A Specification is a named bundle of design conditions you can assign to individual pipe elements, so one model can contain lines at different pressures, temperatures — and even different design codes.

A spec can override any of:

FieldInherits from (if blank)
Design Code (B31.3 / B31.1 / AS 4041)global Settings
Cycles, N (expansion factor f)global Settings
Design Pressureglobal Settings
Design / Install / Min Temperatureglobal Settings
Corrosion Allowance, Mill ToleranceSection / global Settings
Fluid Densityglobal Settings

Workflow

  1. Open the Specs tab → + Add Spec, fill in only the fields you want to override, and Save. Blank fields fall back to global Settings.
  2. Open the Assign tab, select an element (or range), and choose the spec from the Specification dropdown. Elements with no spec use the global Settings.
  3. Run the analysis. Each element is checked against its own resolved design code, cycle factor, and allowables (Sh, Sc, SA). The Results table's Govern column shows which check governs per element.
note

The liberal-allowable toggle, weld-joint factor E, and Y coefficient stay global (project-wide). Material allowables (Sh / Sc) live on the material, so to vary allowables per line, assign a different material.

My Library (cross-project reuse)

Each tab for Materials, Sections, Specifications, and Soil profiles has a 📚 My Library panel. It lets you save the entry you're editing to your private library and load it into any future project — no more re-typing the same data.

  • 💾 Save current — saves the entry currently in the editor to your library (re-saving the same name updates it).
  • 📚 My Library ▸ — expands your saved entries; Load drops one into the current project, deletes it from your library.

Your library is private to your account and available in every project you open. This is separate from the built-in read-only catalogs (the Import from Database dropdowns for materials and pipe schedules), which remain available to everyone.

One-time setup

The personal library requires a Supabase table. A project administrator applies the migration in supabase/migrations/20260530_user_library.sql once (Supabase → SQL Editor). Until then, the My Library panel will report "Library unavailable." Saving/loading within a single project (and the built-in catalogs) work regardless.