equipment-class-template-compliance#

Code

AM.007

Validator

Compatibility

Tags

Summary#

All aif:spec:* attributes defined in the equipment-class schema (determined by aif:core:assetClass) must be present on the default prim.

Description#

Each equipment class has a JSON schema in config/aif-equipment-<class>.json defining all required aif:spec:* attributes. The validator reads aif:core:assetClass to select the appropriate schema and checks that every property key in that schema is present on the default prim.

Supported classes and their schemas:

  • CDU → aif-equipment-cdu.json (~65 attributes)

  • CRAH → aif-equipment-crah.json (~31 attributes)

  • UPS → aif-equipment-ups.json (~32 attributes)

  • compute rack / gb300 → aif-equipment-gb300-rack.json (~18 attributes)

Why is it required?#

  • Ensures simulation runtimes have all data needed to model equipment behavior

  • Equipment-specific attributes (cooling curves, pump specs, battery specs, power profiles) are critical for thermal/electrical simulation

  • Single check covers all equipment-specific metadata without a separate requirement per attribute

Examples#

# CDU asset with aif:spec:* attributes present
def Xform "CW375" {
    string aif:core:assetClass = "CDU"
    float aif:spec:nominalCoolingCapacity = 375.0
    float aif:spec:maximumCoolingCapacity = 400.0
    float aif:spec:nominalFlow = 60.0
    int aif:spec:numberOfPumps = 2
    float aif:spec:nominalVoltage = 400.0
    float aif:spec:powerRating = 15.0
    float aif:spec:frequency = 50.0
    # ... all remaining CDU aif:spec:* attributes
}

How to comply#

Use the AIF pipeline metadata tools to generate a template for your equipment class:

aif-pipeline metadata create --type cdu --output my_cdu_metadata.json

Then apply it to your asset:

aif-pipeline metadata apply my_cdu_metadata.json --output AssetName_Properties.usda --prim RootPrimName

For More Information#