If you are importing an NBS Create specification into Chorus with the aim of re-using the content in a live project there are a number of things we recommend doing:


After you import:

  1. Review the import report to identify any parts of the specification that were not imported. For detailed information about the report please see Understanding the NBS Create import report.

    Please note Project Management (00 and 05) clauses are not imported. For details about what is imported please see Importing from NBS Create - What will and will not be imported?

  2. Review the report to identify parts of the spec that could not be updated to Uniclass. This step can be ignored if you are choosing to keep the NBS Create clause codes and titles.

    For clauses that were not converted to Uniclass there are two options:
    1. Change the code – using the import report, find the imported clauses in Chorus. You can change the clause codes in the specification editor.

    2. Replace them – with the proper Uniclass clause from the content set.
      • Search the NBS Chorus content for a suitable replacement clause for something that has not been updated automatically to Uniclass. This may involve using a Template Clause where there is not currently any NBS content available. You should bring in and update any suitable Uniclass clauses and then delete the unchanged NBS Create clause. For more information see  Importing from NBS Create - What will and will not be imported?.

  3. Run the Chorus Spec check report to locate empty values.

    Empty values are clauses that have incomplete rows. After you import an NBS Create file and before you issue it from Chorus we recommend you run the Spec check report to find and deal with any empty values.

    Empty values can exist in files imported from Create for 3 reasons:
    1. They were empty in NBS Create.

    2. The whole clause was parked in NBS Create. While clauses can be parked in Create they cannot be parked in Chorus. So parked clauses found in a Create file will be imported as an unparked clause in Chorus.

      We recommend either completing these clauses, removing them, or turning them into placeholders. More about placeholders.

      Examples below, see Figures 1(a) and 1(b).

  4. Save a record to your Chorus publish history - for Chorus Pro and above subscribers revisions are displayed in the published specification when you compare what you are publishing now with a record in your Chorus publish history.


    To establish a record in your history to compare against we recommend publishing your specification after you import it and saving the record to your publish history. It is best to do this before working on the spec so you can publish the revisions you have made since importing it into Chorus.


    Supporting information about Chorus revisions is found in the Revisions and publish history section.


Example screenshots:


Figure 1(a) - screenshot of parked clause 15-65-75/245 from NBS Create.


Figure 1(b) - screenshot of clause 15-65-75/245 imported into NBS Chorus. The clause is not parked.