thermal-cooling-connection-points#

Code

TC.002

Validator

latest+

Compatibility

other

Tags

🔑

Summary#

Cooling equipment must have connection point prims matching its piping interface types: CDUs require FWS and TCS connection points; CRAHs require liquid supply and return connection points.

Description#

This is a cross-domain check that reads aif:core:assetClass from the metadata domain and verifies that the corresponding connection point prims exist in the geometry domain. The check ensures that the piping interfaces declared in equipment metadata are actually represented as locatable geometry.

Why is it required?#

  • Ensures piping interfaces documented in metadata are spatially represented

  • Simulation runtimes use CP geometry to locate pipe connection points for fluid simulation

  • A CDU with metadata but no FWS/TCS CPs cannot be connected in a facility model

Required Connection Point Types#

Equipment Class

Required CP Type Prefixes

CDU

fws_supply, fws_return, tcs_supply, tcs_return

CRAH

liq_supply, liq_return

Examples#

# Valid CDU connection points
def Scope "ConnectionPoints" {
    def Mesh "acme_fws_supply_piping_connection_main" { ... }
    def Mesh "acme_fws_return_piping_connection_main" { ... }
    def Mesh "acme_tcs_supply_piping_connection_main" { ... }
    def Mesh "acme_tcs_return_piping_connection_main" { ... }
}

How to comply#

Ensure your ConnectionPoints scope contains at least one prim for each required type prefix. Follow the CP.004 naming convention: <vendor>_<type_prefix>[_<suffix>].

The name-based convention above applies to AIF 0.1.0. For AIF 0.2.0, FET202_AIF@0.2.0 uses the property vocabulary: prim names are arbitrary, and each required port has simready:connectionPoint:domain = "thermal". CDUs need both supply and return directions for each of systems FWS and TCS. CRAHs need thermal supply and return ports; their system token is not restricted to LIQ (for example, FWS is also used by CRAH assets). All property names use the simready:connectionPoint: prefix. The deprecated type alias for domain is read consistently with CP.011.

The shared checker selects this vocabulary when aif:core:simreadyVersion on the Properties-layer default prim is "0.2.0", as specified by AM.005. Older or unversioned assets retain the legacy name check. CP.010–CP.012 validate the structure and property data separately; TC.002 checks port completeness. UPS and compute-rack assets remain exempt from TC.002.

For More Information#