ACC Issues is positioned as a central system of record, but today there is a gap in how external issue data can be brought into ACC with spatial fidelity. Both BCF (2.1) and Excel are widely used, open interchange formats for issue data coming from coordination and review tools such as Navisworks, Revizto, Solibri, Resolve, and others. These formats already contain rich spatial information, including viewpoints, camera positions, and coordinates, yet that information is not consistently translated into model‑based issue placement when imported into ACC.
Excel imports create list‑based issues without model pins, and while BCF files can be consumed by tools like Navisworks, issues published onward to ACC do not reliably recreate the original viewpoint or placement in the ACC model viewer. In both cases, the spatial intent of the issue is lost, requiring manual re‑pinning and re‑creation of context. This adds friction, increases the risk of mis‑location, and discourages teams from using ACC as the authoritative coordination platform.
Providing parity between BCF and Excel imports—so that both can optionally include model‑based placement when spatial data is present—would significantly improve interoperability. If an issue includes a viewpoint, camera, or coordinate reference, ACC should be able to interpret that data and place the issue directly in the model viewer upon import. This could be optional and backward‑compatible, preserving existing workflows while enabling higher‑value ones.
Supporting spatially aware imports for both BCF and Excel would reduce manual rework, preserve intent from upstream coordination tools, and strengthen ACC’s role as the hub for model‑based issue tracking across the project lifecycle.
