Literature Types and Labels
Literature Types
Items of literature (both uploaded documents or links) are grouped according to the type of information. This dictates the order in which the documents display on the listing and helps to group similar documents together.
When loading a document or creating a link you select a Type from the drop down list. The order in the list reflects the order that the information types appear on EBOSS. This places technical information (such as manual or technical statements) at the top, and other information (such as brochures or colour charts) further down.
A table below outlines the different literature types.
Labels
Once you have selected the literature type you can enter your own label for your literature. Labels are optional but are useful to customise your information.
Using labels helps make it clear to specifiers what information is available and where to find it.
Labels should be used to distinguish between literature of the same type, or where a more specific name is needed. For instance:
- If you have two items under the same type you should use a label to help clarity — A 'Technical Data Sheet' and a 'Span Table' would both have the type 'Data Sheet'
- Where the type covers a range of information, such as 'Appraisal, Accreditation, Certification and Testing'. Here a label is helpful to indicate the nature of the information, such as 'BRANZ Appraisal', 'Acoustic Testing' or 'Environmental Certification', etc.
Literature Types and Definitions
Product Assurance | |
---|---|
Drawings (hosted outside of EBOSS) | We encourage hosting drawings on EBOSS but this is an option to hyperlink to drawings hosted on your own website This is for URL links only. Drawing uploads should be made under the Drawings section. |
Technical/Design Manual | A larger document that compiles items relating to products or systems such as data sheets, drawings and installation information. |
Product Technical Statement | A PTS is an MBIE-encouraged document format that summarises key details relating to the scope, limitations and compliance of a building product or system in order to improve knowledge and transparency for everyone in the building process. Learn more |
Data Sheet | A document that summarises technical parameters of a product or system in sufficient detail to understand its role as a component in a building. Examples include: span tables, material safety data sheet |
Appraisal, Accreditation, Certification, and Testing | Any documentation summarising how a product or system has met standards by an external regulator/assessor, or test results and parameters that function as evidence of performance. Examples include: BRANZ Appraisal, CodeMark Certificate, Supplier Declaration of Conformity, Environmental Choice Licence |
Maintenance and Warranty | Warranty documentation and maintenance requirements for a product or system. |
Specification Clause/Guid | Assistance with compiling an explicit set of written requirements to be satisfied by a product or system for building documentation that cannot be conveyed in a drawing. Examples include Masterspec and Smartspec. |
Producer Statement | A document issued by a specialist author that gives evidence that design or building work complies, or will comply, with the Building Code which helps councils make a decision to issue a building consent or a Code Compliance Certificate (CCC). Learn more |
Installation and Operation | Documentation regarding the installation and end use of a product or system. (Note: this excludes installation drawings which should be added via the drawings interface) |
Other Literature | |
Brochure | A document focused more on the benefits and features of a product or system, typically covering less technical parameters than a technical/design manual. |
Options, Variations or Accessories | Information around things like profiles, configurations, colour ranges, supporting products or components. |
Pricing, Availability and Sample Requests | Information or channels regarding unit costs, supply availability and samples. |
Additional Information | Any documentation not covered by other types. Consider whether this is relevant for specifiers. |