• Registration is manually approved during the forum's testing period Регистрация одобряется вручную на период тестирования форума

Maintaining custom MagiCAD products when a manufacturer item is missing

web3d

Administrator
Staff member
On a project we needed a manufacturer’s inline unit that wasnt in the available product database. I can make a generic object for the model, but then the product data, connectors, and schedules are either lost or need hand-maintaining.

What is your approach for building a custom MagiCAD product so it behaves like a useful design object, not just a graphic placeholder?

  • Which parameters do you treat as essential for calculations and schedules?
  • How do you set up connectors and flow direction so the object works in a connected system?
  • Do you keep a source file or naming scheme that makes later revisions manageable?
  • How do you check that custom items remain distinguishable from manufacturer products in reports?

I’d like to compare practical workflows, especially where a local product library is shared by several designers. What has made custom content dependable for your team?
 
We’ve run into this on almost every project that isn’t 100 % catalogue. A generic family is a last resort; we treat the custom MagiCAD product as a real calculation object from the start.

Essential parameters we always fill: connection sizes and types, flow/capacity range, pressure drop (or Kv / k-factor / equivalent length), power and heat load if relevant, weight, and the MagiCAD system and product class so it lands in the right calculations and schedules. If we only have a single duty point we still enter a conservative constant drop rather than leaving it blank. Classification and a “Source = Custom” parameter go in as well.

Connectors are matched to the real geometry (round/rect, flanged, etc.) and given explicit flow direction and system type. The flow parameter is linked so MagiCAD sees a continuous network. For devices we mark a primary connector; for in-line units both ends get the same size and opposite flow so balancing and sizing don’t break.

Naming and source: prefix CUST_ or LOC_, then type-size-revision (CUST_AHU-450-R02). Original datasheet and a short note live in a folder next to the product definition. We never overwrite a manufacturer dataset.

In reports we filter on Manufacturer = “Project Custom” plus the Source parameter so custom items never mix with catalogue products.

Shared library: one owner (or a tiny group) maintains a network folder with a simple changelog. Designers pull, they don’t edit. That, plus the naming and Source flag, is what has kept custom content dependable for us.
 
Back
Top