(COBIE-ER-12) Exchange Project Handover - Warranty
NBIMS Development Stage
| Stage | Name | Status |
|---|---|---|
| 0 | Draft, not yet approved as NBIMS project | |
| 1 | Part of a 'pilot' project | |
| 3 | Part of a project out for 'consensus' review | |
| 4 | Part of an operational standard | |
| 5 | Superseded by: | |
| 6 | Retired |
Note: For information on the specific stages of NBIMS project development, please visit www.nbims.org.
Project Stage
| Stage | Name | Valid |
|---|---|---|
| 0 | Portfolio requirements | |
| 1 | Conception of need | |
| 2 | Outline feasibility | |
| 3 | Substantive feasibility | |
| 4 | Outline conceptual design | |
| 5 | Full conceptual design | |
| 6 | Coordinated design and procurement | |
| 7 | Production information | |
| 8 | Construction | |
| 9 | Operation and maintenance | |
| 10 | Disposal |
Note: While the information exchange described in the COBIE project occurs following construction during building handover, as noted in the table above, the data contained in this particular exchange requirements is generally applicable throughout the facility life-cycle.
Overview
COBIE contains information information describing the operations, maintenance, and assets in capital facilities. The authoritative sources for this information include designers, builders, installers, and manufacturers. On the design side of the exchange, BIM-based design tools may be used to capture COBIE data. From construction, information about approved submittals are included in COBIE exchanges. Builders identify products to be installed. Manufacturers provide operating and maintenance information. Installers provide serial and tag numbers. Quality Control/Assurance staff provide test and certification reports. All these parties can capture building handover data through the COBIE standard, tying their diverse set of software together for the purpose of providing a consistent data set of operations, maintenance, and asset management to building staff.
This exchange requirement defines method by which warranty data is provided by the manufacturer and provided to the facility operator/maintainer in the construction-operation information exchange. The information typically flows through the general contractor to the owner as part of exchange of paper handover documents. An example scenario for this stage is shown in the table below:
| Task | Scenario |
|---|---|
| Warranty | A set of tasks is provided by the manufacturer that identify standard preventive maintenance activities to be completed. |
| Warranty (Duration) | Start and End dates for the warranty period. Typically start begins upon installation of the material, product, or equipment |
| Product (Reference) | Identifies the system, product or equipment for which the warranty applies. |
| Guarantor (Reference) | Identification of one or more parties responsible to execute the terms of the warranty |
| Documents (Reference) | Identifies document containing warranty certificate or other related terms. |
The COBIE exchange requirements fully recognize the "maturity model" approach to the transformation of information within image-based e-paper documents and meta-data. Given the critical nature of the warranty information, however, warranty meta-data is required for COBIE exchanges.
The information provided through this exchange will reflect information provided by the manufacturer. The data provided here is typically provided at the conclusion of construction, however, some information should be provide following beneficial occupancy. Information related to the warranty that may be exchanged include:
- Warranty Guarantor
- Start and end dates
- Document(s) containing additional information about the constraint
- Applicable products and/or systems
The following information auditing is also required for all COBIE file exchanges that occur in a batch file transfer mode. Software that mediates that transmission of COBIE data may capture this data automatically based on process model implementations:
- The party who created the data provided. This is required for individual record.
- The full history of all changes to the data must be included in the data file.
The authoritative source for this information is the manufacturer. Ultimately the goal is to have a manufacturer to directly provide the information related to the material, product, and equipment warranties.
Information Requirements
| Context | Information Needed | MAN | REC | OPT | Actor Supplying | Functional Part |
|---|---|---|---|---|---|---|
| Precursor | Product Name for each material, product, or equipment to be installed in the facility must be identified before it can be associated with specific warranty terms. | Designer or Constructor | fp_model_inventory(asset) | |||
| Precursor | Documentation for individual warranty certificate. | Manufacturer | fp_associates_document | |||
| Precursor | Identification of one or more guarantors for each warranty. | Manufacturer | fp_assigns_to_actor | |||
| Warranty Terms | Manufacturer provided warranty start and end dates. | Manufacturer | fp_set_warranty | |||
| Authoritative Source | The user responsible for creating the project wrapper data set. | Constructor or Manufacturer | fp_apply_owner_history | |||
| History | All versions of information captured during the project will be provided in the file. Superseding data is explicitly identified. | Constructor or Manufacturer | fp_apply_owner_history |