The recommended procedure for mapping existing asset, space and contract data into the GyroX resource ontology.
GyroX represents assets, facilities and spaces in a single resource ontology (instance + classification + dynamic schema + properties) rather than separate tables. The key during mapping is to absorb existing classifications as typeKeys without creating child tables.
Mapping checklist
- Normalize asset classes into typeKeys instead of new ASSET_CATEGORY codes.
- Absorb the 9-level space hierarchy into dynamic schema.
- Pass monetary fields through the single currency-conversion entry point.
- Set audit-column subjects to ACTOR (human, AI, system).
Before creating a new table or column for a feature, abstract two levels further to check if existing metadata can absorb it. New structures are the last resort.