LATTICE VW Plugin and iTwin BIS Bridge

To map IFC classes to BIS schemas from Vectorworks, the Skill validates the MCPBridge via `vw.ping`, parses IFC data using IfcOpenShell, and writes authoritative `bis_class` and `bis_subclass` values back to the Pixeltable ifc_elements table.

BIS class assignments are missing due to inconsistent IFC imports, but this Skill resolves the issue by automating Vectorworks-to-Pixeltable enrichment and applying controlled fallbacks for unknown IFC classes.

Vectorworks IFC enrichment requires a successful `vw.ping` health check to ensure the Python bridge is reachable before executing any MCP tool calls or writing BIS mappings back to Pixeltable.

To validate Vectorworks plant symbol naming, the Skill enforces `Genus_species_cultivar` conventions and rejects forbidden strings, ensuring no Revit, DGN, or cloud-bentley rules are violated during IFC ingestion.

You can use IfcOpenShell to parse IFC files and normalize EPSG coordinates, which is required before applying `itwin/bis-schemas/BisCore.ecschema.xml` mappings to update the lattice ifc_elements table.

The limitation of automated BIS class fallback is that unknown IFC elements receive a controlled default mapping rather than a precise BIS equivalent, which may require manual review for highly specialized Vectorworks geometry.