PowerWeb provides the following pre-configured document types. Each type is based on the business purpose of the document, which determines its configurable options such as: document naming convention, revision numbering convention, templates, workflow, properties, file type associations, and data links. They can be created from predefined templates and can be of any file format.
Learn which document properties are supported and mandatory per document type.
For customers where the workflow lockdown setting is enabled, and the document type is Facility, Transmission, or any type derived from these document types, the following functionality is not allowed:
-
Quick Change
-
Editing document properties for released documents
This restriction is for PowerWeb only.
If the document type is one of the above AND an e-signature is required, Workflow Shortcuts are not allowed.
-
Facility Document type
Documents that contain engineering information about part of a facility, for example, master drawings. They are either imported or created in projects but primarily used after a project is completed. They can be imported as new master documents, new revisions, or as new content for placeholders that were created in advance.
-
Project Document type
Documents that contain engineering information that is only relevant within the scope of a project but are not related to the facility breakdown structure, for example, project management, reports, and schedules. They are either imported or created in projects. They can be imported as revisions or as new content for placeholders that were created in advance.
-
Transmission Document type
Documents that contain engineering information about linear assets . For example: transportation pipelines, glass fiber communication lines, and high voltage electricity lines. Transmission documents are described by the Transmission Type, Sub-Type, and Transmission ID. Transmission Document Types do not use the Facility Information and Functional Location properties. They are either imported or created in projects but primarily used after a project is completed. They can be imported as new master documents, new revisions, or as new content for placeholders that were created in advance.
-
Generic Document type
Documents that exist outside the scope of projects and have no relationship to the facility breakdown structure, for example, SOPs, templates and so on.
The following table compares the document types.
|
Feature |
Facility Document |
Transmission Document |
Project Document |
Generic Document |
|---|---|---|---|---|
|
Facility breakdown structure |
Yes |
No |
No |
No |
|
Linked to asset tags |
Yes |
Yes |
No |
No |
|
Managed change |
Yes |
Yes |
No |
No |
|
Vault branch |
Projects,
|
Projects,
|
Projects |
Documentation |
|
Archived |
Yes |
Yes |
Yes |
Yes |
