Consistency Check

Check the consistency between Revit files and spine Projects . Check for missing or inconsistency data.
Consistency Check Tutorial (Video English)

1. Synchronization Configuration and process line

  1. Select Revit categories to be checked
  2. Click OK
  3. Number of issues
  1. Bold text indicate the current step
  2. The blue color indicate that there is still issues to be considered
  3. The green color indicate that all issues has been handled
2. CCS Classes

Objects without a CCS Class

  1. Type in a synonym for the class
  2. Select a class
  3. Click Apply
A: Toggle 'Classification by instance' to add classes as instance parameters
B: If an object have a class from another standard, the dropdown display suggested CCS classes
3. CCS Type ID
Objects with a CCS Class , but without a CCS Type
  1. The Revit Type is linked to a CCS Type in another file, and that type is suggested
  2. The Revit Type has been linked to the CCS Type [L]%ULD3, which no longer exist in the spine Project . Select a new CCS Type
  3. The drop-down display CCS Types within the CCS Class
  4. Tick types to be linked
A: See Revit Type in the model
B: Go to classification
4. Recognized Single Level ID
Single Level ID's in the current model with a mismatch in relations.
If an ID appears multiple times in a document , it is displayed in cursive and orange and the relation can only be added to one of the objects.
A - No relations
ID Code was found in the spine project, but has no relations to any documents .
Add Relation:
Adds a new relation between Revit object and spine object. Relations to other models or applications remains.
Create new Id Code: Creates a new Id Code with next available number. Current Id Code will be replaced with the newly created.
No action: Revit object will not be related to a spine object.


  1. Add Relation: 'Corridor 06' is related to spine object [A]#100
  2. Create new Id Code: 'Corridor 13' is related to a new spine object [A]#3, and spine object [A]#101 is not related to the current model
  3. No action: Nothing happens to 'Corridor 23'
  4. 'Corridor 24' and 'Corridor 30' has the same CCS Single Level ID value [A]#103. Select one to be related to spine object [A]#103 and one to get a new ID Code
    Create new Id Code: 'Corridor 24' is related to new spine object [A]#4
    Add Relation: 'Corridor 30' is related to spine object [A]#103
5. Single Level ID
Objects with a CCS Class , but without a Single Level ID
  1. Tick objects to be assigned a Single Level ID
  2. Click apply
6. Objects deleted in spine
Objects deleted in the spine Projects , that still exist in the current Revit file .
Reassign a Single Level ID or delete the object in the Revit file.
  1. Tick objects to be deleted in the Revit file
  2. Tick objects to be reassigned a Single Level ID
  3. Click apply
A: Display objects in the model
7. Objects deleted in Revit
Objects found in the spine Project , which no longer exist in the current Revit file .
  1. Tick objects to be deleted in the spine Project
  2. Click apply
A: Display objects in the spine Desktop & Viewer
8. Properties
  1. Download property values from the spine Project to the Revit file
  2. Upload propertie values from the Revit file to the spine project
  3. Copy CCS classification to instances
  4. Click apply

9. Consistency Check Tutorial (Video English)


Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.