I was wondering what you may think of this feedback on adding addition elements to check in the Archibus model checker. As clients are using the Archibus Model Checker, they still come across issues we learned so the model checker seems to be more focused on data readiness but there’s also an element of model readiness which Smart Client verifies before publishing. An example is a publishing error like this:

************** Exception Text **************
Autodesk.Revit.Exceptions.InvalidOperationException: The color represents an invalid or uninitialized color.
at Autodesk.Revit.DB.Color.get_Red()
at ARCHIBUS.SmartClient.Overlay.Revit.Publish.PublishableModelCreator.InitCategoryColors(Document document)
at ARCHIBUS.SmartClient.Overlay.Revit.Publish.PublishableModelCreator.Create(Document document, View view, String folder, String shortSymbolNamePrefix, IList`1 layersToIgnore, Boolean useExportSetupColors, String optionsOverrideName)

However, this isn’t clear if it’s a certain line type or a highlight or model line that is causing this. And with Revit, folks could have hid whatever this is so it’s not visible. It’s quite a bit of work to go into all the visibility settings and look at every possible thing that can contribute to this issue.

Many clients do transition from AutoCAD to Revit or other imports over to Revit so as a result, it could be a lot of things to check for to find out what item is red or some other color in the wrong place. We can try using a bunch of other model checkers but some may be checking for things that are irrelevant.

Here’s an example of FM systems’ model checker which goes into checking line type and other features. I was wondering if you may want to include a bit more than just data readiness like what they did.