Upon importing an NBS Create specification you will receive an email containing a report which details what has and has not been imported. For detailed information about the report please see Understanding the NBS Create import report.
 

What does get imported:

  • All work section clauses with codes 10-XX-XX through to 90-XX-XX (including user-created clauses)
  • All of the information entered into these clauses including:
    • Entered text
    • Hyperlinks 
    • User added clause items (rows)
    • Parked status
    • Clause suffix
    • Links to external standards
    • Links to related clauses
    • 'Shared by' relationships between clauses


These clauses will be indicated by a TRUE in the Imported column of the report.


What does not get imported:

Anything that currently does not have a home in NBS Chorus will not be imported:

  • Any project management (00) or whole building performance (05) sections - Uniclass Preliminaries are available within NBS Chorus, however, the Project management or Whole Building Performance sections from NBS Create can not be imported at this time.
  • Milestones
  • User Guidance Notes (saved against that specification in NBS Create.)
  • Saved Custom Reports 
  • General Details tab information - Subtitle, Locations, Project Description, Building Type and Project Type.
  • Clause Properties (the name of the last person to edit and the date.)
  • Clause order - the clause order may be different in a system outline in NBS Create compared with NBS Chorus
  • Any update notifications against a clause that have not been actioned in NBS Create prior to import
  • Any text formatting from NBS Create
  • Office master - Office master clauses are imported as regular NBS or user clauses and do not retain their link to the NBS Create office masters.


Clauses that are not imported will be indicated by a FALSE in the Imported column of the report.


Scenarios where the code in NBS Create is not updated to Uniclass:


  1. User created clauses - these will be identified as user in the Source column of the import report.
  2. When the NBS Create clause is an old NBS clause that has since been removed from the content set and does not have an equivalent in Uniclass.
  3. When you choose to keep the NBS Create clause codes and titles - please see support article Keep NBS Create clause codes and titles.


These clauses will be imported into NBS Chorus but they retain the code and title that they held in NBS Create. 

See Recommended steps for importing an NBS Create specification (.spex) for guidance on options for this situation.


Scenarios where the title is different in Uniclass to what it was previously in NBS Create:


1) An un-edited title of a clause in NBS Create may alter slightly when converted to Uniclass (e.g. pluralization)

2) If you have manually amended the title of a clause in NBS Create but this is identified as being able to convert to Uniclass by Chorus, the NBS Create amended title is not retained and the Uniclass title is applied.


As a rule of thumb, where clause titles are concerned, Uniclass will always be applied as the default when converting from NBS Create.