Atvero document management standardises project delivery

Atvero PIM software provides a powerful document management environment with a flexible central hub for managing all project deliverables, with company or industry standardisation at its core. Project data is stored on companies SharePoint tenancy, with the power of Microsoft security and data retention.

Atvero document management checklist:

  • ISO19650 Project naming as standard
  • Enforced naming compliance
  • Configurable to project or company standards
  • Configurable Project Summary Pages
  • Multiple naming schemes per project - name documents differently to drawings
  • Standardise Company and Project documentation
  • Quality Approval Checks to aid ISO9001 policies
  • Issue and Transmittal workflow with audit
  • Sheet issue register
  • Recorded Information Exchange
  • Automatic received file upload checking and association
  • Powerful, metadata filtering and search

Atvero provides managed file containers to ensure project consistency

Containers are created for each document or drawing, collecting all the different renditions and associated files per version. Examples of renditions are the DWG and PDF versions of a drawing. Associated files are documents such as mark-up or commented versions or source materials used to create a document. All renditions and associated files are attached to a specific revision so it's easy to always see the latest revision of a drawing but also all previous revisions and associated information.

A container can be created empty, ready to hold information brought in from design authoring tools or documents created through templates in Microsoft Office. This allows for project planning and delivery tracking.

Add-Ins such as the Revit integration allow authoring of information directly from the design tool into Atvero. Where an integration isn’t currently available, information can be exported from the tool as it is now (such as in a DWG or PDF format) and then simply uploaded. Atvero automatically sorts and stores uploaded files into the correct containers.

Third party information can also be stored within the Atvero environment. Documents such as product specification, planning guidelines etc. can be uploaded and tagged as information that is not authored by the user but is otherwise seen as internal information. Drawings and documents from collaborators on the project can also be uploaded into Atvero in the same away, this time being tagged as a received file and tagged to an external organisation and formally recorded in a received register.

Atvero uses powerful filtering and search to present the single set of information in a view that suits the user’s current work task using AEC specific metadata to create views filtered on zones, levels or classifications.

Atvero provides inbuilt processes for transmitting and recording the issue of information out to other project partners.

Documents or drawings that has passed quality assurance may be selected for issue. After adding a description and notes, the recipients of the issue are selected from the project contact book. Documents are bundled for issue, with an automatically generated transmittal sheet. The project issue register is also updated with the issue information.

Atvero leverages Office 365 to bring guarantees to the issue process. Issues can be made and recorded through email, SharePoint’s file sharing mechanism or through uploading to CDEs.

Atvero supports industry standards and best practice at every level

All internally generated documents and containers must follow the project’s naming scheme. This is completely customisable and can follow internal naming schemes or the one dictated by the project lead. Atvero provides ISO 19650 compliance as standard. The naming scheme will depend on the national annex of ISO 19650 being used. Containers can be tagged with UNICLASS 2015 classifications as metadata.

Atvero enables improved Quality Assurance to help implement ISO 9001 policies

New or updated drawings and documents can be held for quality checking and approval by a document controller before being made available for issue. Drawings that fail checks can be rejected with the uploader notified of the rejection and the reason for it. The status assigned to a document or drawing is locked and cannot be changed without further approval. Consistency of issues is maintained where the status of documents is checked for appropriateness.