Uniclass sections

In Uniclass work sections content sets, Chorus creates ‘sections’ for clauses that have the same parent Uniclass code. This is so you can work on closely related content all in a single section, just as we do in CAWS work sections, CMS, SureSpec etc. 

When you add a Uniclass clause to a bundle, Chorus will also bring in all the clauses for that section.  

For example, if you add Ss_25_30_20_25 Doorset systems to a bundle: 

• Chorus will actually add the section Ss_25_30_20 Door, shutter and hatch systems to your bundle. 
• This section will contain: 
  • All the ‘addable’ clauses whose codes start with Ss_25_30_20: 
    • The clause you added - Ss_25_30_20_25 Doorset systems. 
    • Uniclass siblings of the clause you added, e.g. Ss_25_30_20_22 Door assembly systems. 
    • Any template clauses for Uniclass codes in this section that don’t have authored NBS content, e.g. Ss_25_30_20_16 Collapsible gate and grilled doorset systems.
  • All the general guidance for the section Ss_25_30_20: 
    • This is attached to the section title. 
  • All the ‘/’ clauses whose codes start with the section code Ss_25_30_20: 
    • System performance clauses, e.g.  Ss_25_30_20/205 Design submittals 
    • Execution and completion, e.g. Ss_25_30_20/805 Removal of samples
      
      
       
• This section will not contain: 
  • Any clauses from the same Uniclass table but with a different starting code. 
  • Any linked /xxx clause (performance, execution) with a different starting code. 
    • For example: If a /xxx clause is shared by multiple Uniclass sections, it will only be available to edit in the section related to its code: 
      • Installation of valves generally appears in Pr_65_54_95 Water services valves.
      • The other sections contain clauses that reference Installation of valves generally. 
      • Any newly authored clauses can link to Installation of valves generally even though it's in a different section. 
    • Once published, any edits to a shared clause will visible to all clauses that link to it, even if they were not updated in the same bundle. 
  • Any clauses from a different Uniclass table. 
    • For example: Ss_25_30_20_22 Door assembly systems links to Aluminium door frames product, but this clause is not part of the same Uniclass section as it belongs to the Pr table. To edit that product clause, you need to add it to your bundle. This will bring in the Uniclass section Pr_30_59_23 Door frames and leaves.
    • For example: Some of the old Create system outline clauses map to the Activities table. If you want to edit the old  25-20-30/190 Fencing maintenance system in Chorus, you need to add Ac_85_10_30 Fencing maintenance to your bundle. 

For more on clauses in general, and Uniclass work sections template clauses in particular, see the Clauses support article.

General guidance

As with CAWS, the Uniclass general guidance is attached to the section title. 

For more on working with general guidance, see Guidance for sections support article.

If general guidance was in 1 location in the old Create Word documents, but was mapped to multiple Uniclass locations, it is already duplicated in Chorus. 

• Updating or deleting general guidance in one Uniclass section will only update the general guidance in that section.
• The same general guidance content in any other Uniclass sections will be unchanged unless you have also edited it directly.
• If there is duplicated general guidance that is now irrelevant to your current location, you can safely delete any irrelevant guidance.

Example of duplicated general guidance 

The old Create section 25-20-30 contained a system outline clause that has been mapped to the Activity table: 190 Fencing maintenance system. 

If you add Ac_85_10_30 Fencing maintenance to a bundle, you can see all the fencing general guidance has been duplicated: 

If you then add any fencing system from the Ss table to the bundle, you will see this general guidance is duplicated: 

You can now update the general guidance in both places to be specific to their new Uniclass context. 

Note: If you remove, retitle or remove general guidance parts, remember to also update the display text of any links to those parts. Chorus cannot update that for you yet.

Shared supporting clauses 

Each supporting clause (performance, execution, etc.) belongs to a single Uniclass section. This clause can be shared across multiple Uniclass sections, including sections from a different table. 

• Where general guidance has been merged together from more than one NBS Create Word document, you will need to manually: 
  • Remove any duplicated content. 
  • Renumber the general guidance parts. 
  • Update the display text of any general guidance links that now reference renumbered, or deleted parts. 
• Where a single NBS Create clause was shared by multiple Uniclass work sections, the shared clause will now live in a single Uniclass section. To update this clause in Chorus, you will need to add this parent section.
• It can be hard to find the code for supporting clauses in bundles. We suggest: 
  • Add the clause to a spec to find the code, e.g. Ss_25_30_20/205 Design submittals. 
  • Add the section for that code to your bundle, e.g. Ss_25_30_20 Door, shutter and hatch systems.