Field names
Usesnake_case with the unit at the end:
Examples
Process data
reactor_temp_set_C— Target temperaturereactor_temp_C— Measured temperatureglucose_feed_vol_L— Volume of glucose addedfilter_inlet_press_lim_bar— Pressure limit
Manufacturing & QC
housing_length_mm— Measured lengthscrew_torque_lim_Nm— Torque specificationleak_test_result— Pass/Fail observation
Clinical & patient data
patient_weight_kg— Body weightsys_BP_mmHg— Vital sign (systolic blood pressure)pain_score— Patient-reported outcome
Choosing a naming standard
External standards (Allotrope, CDISC, ISA-88)
These standards are optimized for data exchange between systems, not daily usage. They prioritize universal definitions over specific context. For example, an ontology defines “Temperature,” but your process needs to distinguishinlet_temp from outlet_temp. Using abstract codes (like AFO_0000123) strips away this context, making data analysis harder and increasing the risk of interpretation errors.
Best practice: Use descriptive, functional names inside Seal for clarity and safety. If you need to export to external standards (Allotrope, CDISC, etc.), speak to your solutions consultant—Seal can set up the appropriate transformations for your workflows.
Templates
BR_MAB_Upstream, SOP_Deviation_Handling
See Template prefixes for the full list.
Versioning is handled automatically by Seal—don’t add _v1 to names.
Instances
Naming depends on whether the entity is a process (happening in time), a resource (physical), or a document (static).Process (time-based)
Resource (physical)
Document (static)
Tip: Don’t repeat the product or process name in the instance (e.g.,
MAB_Upstream_B-2024-001). That metadata comes from the Template.