CT Document Association

[SergejMuhic]

Review whether:

• IfcExternalReference.Identification
• IfcExternalReference.Location
• IfcExternalReference.Name
• IfcDocumentReference.ReferencedDocument
• IfcDocumentReference.Description
• IfcDocumentInformation.Purpose
• IfcDocumentInformation.Revision
• IfcDocumentInformation.Name
• IfcDocumentInformation.Scope
• IfcDocumentInformation.Identification
• IfcDocumentInformation.Location

require a RuleID.

See also #322

[billeast]

During the course of design and construction projects, the majority of information needed for Facility Maintenance tasks is captured in document-based formats. Typical file formats would include, but are certainly not limited to, PDF, JPG, and DWG. The primary goal for the FMH-EM project is to link manufacturer documents (or eventually manufacturer provided data files) to those IfcElementTypes such as pumps, fans, or fixtures installed in the project. However, there are also documents provided that describe specific IfcElements, aggregations such as systems or zones, or to individual spaces.

The types of external information that may be included is quite broad and could include drawings, bim models, change orders, photos of submittal samples, and photos of jobsite progress. Having a common index to the underlying IfcElementType, IfcElement or other IFC object (ifcSpace, IfcSystem, IfcZone) and allowing that information to be updated through the project life-cycle is a major driver of the FMH-EM project.

It is also the case that the documents that must be captured are processed through a number of different types of design, construction, and commissioning processes. These processes such as the construction submittal process are NOT typically supported by design-oriented BIM software. To ensure the link between the document as it is presented through an Ifc-based lens and through a database supporting construction submittal process (or related admin/QC/commissioning processes) information is also needed to allow systems integrators to create the needed linkages.

The expected information to be included in this Concept Template, from the point of view of IfcDocument is:

Name IfcRelation reference IfcRelation reference ReferencedDocument.Purpose Note: for IFC2X3, use: ReferenceToDocument[0].Purpose ReferencedDocument.Revision Note: for IFC2X3, use: ReferenceToDocument[0].Revision ReferencedDocument.Location Note: for IFC2X3, use: ReferenceToDocument[0].Name Description or ReferencedDocument.Description Note: for IFC2X3, use: ReferenceToDocument[0].Description ReferencedDocument.Scope Note: for IFC2X3, use: ReferenceToDocument[0].Scope Identification Note: for IFC2X3, use: ItemReference Location

[libalschwarzd]

In the concept the IfcDocumentReference.ReferencedDocument should be extended with IfcDocumentInformation in order to show how to connect the file supplied with the model.

[SergejMuhic]

IfcRelAssociatesDocument.OwnerHistory shall cover the revision data. The Document Association template might have to be updated or in mvdxml 1.2 could be used to reference both templates in one usage on objects requiring document association versioning.

[SergejMuhic]

SpecificationSection - IfcDocumentReference.Identification