When you import a file from NBS Create you are sent an email. The email contains an attached MS Excel spreadsheet which is a record of what was imported.
This article explains the report and what we recommend checking.
When you import a live project file into Chorus we recommend saving the import report for your records.
Reading the report
- The report is split into two halves; ‘NBS Create’ and ‘NBS Chorus.
- It shows what clauses the file contained in NBS Create and what was imported into Chorus.
Checking the report for what has not been imported
1. Clauses that were not imported
It is important to check the report for any clauses that did not get imported.
The ‘Imported’ column will be set to TRUE for clauses that have been imported and FALSE for clauses that were not.
Chorus has been developed to import NBS and user-authored clauses so it unlikely clauses will not be imported but it is important to check. Chorus does not import NBS Create Project Management (00 and 05) clauses.
2. Clauses that are not up-to-date
It is important to check the report for any clauses which could contain out-of-date technical information. However, depending on the project, it may be your intention to bring in historical technical information.
The import report indicates when a clause contained update notifications from NBS Create in the ‘Up-to-date’ column. Each row will contain one of three entries; ‘Updates pending. Check guidance’, ‘No updates pending', 'Updates stopped' or it will be empty.
Updates pending. Check guidance – means the clause was an NBS clause in Create and it was imported as an NBS clause in Chorus. The clause had updates pending in Create.
In this situation, it is important to check the technical currency of your clauses yourself. To help, you should compare the clause against the guidance in Chorus. The guidance will be the latest guidance available in Chorus for that clause. An example of something to check would be if a standard cited in the imported clause is different from what is in the guidance.
The 'Update last checked' column is the date and time when updates for the file were last checked in Create.
No updates pending – means the clause was an NBS clause in Create and it was imported as an NBS clause in Chorus. There were no updates pending against the clause in Create. This could be because the clause was up-to-date or that all of the content updates were actioned by the specifier while in Create.
The 'Update last checked' column is the date and time when updates for the file were last checked in Create.
Updates stopped – means clause update notifications were suspended in Create. In Create the specifier could choose to stop receiving clause content update notifications. Create Administrators could also disable clause content update notifications in the office settings. When updates are stopped Chorus cannot determine the status of a clause. Again, we recommend checking the clause currency by comparing the clause to the clause guidance in Chorus.
The 'Update last checked' column is the date and time when updates were stopped.
Empty – means the clause was imported as a user clause in Chorus. You need to check the clause is correct but NBS cannot offer any support here. Clauses are imported as user clauses when;
a) They were authored from scratch by the specifier in Create.
b) They originated from NBS clauses and are no longer present in the NBS content set.