For each object type in SPF, access to the object is based on matching the organization of the user to those specified on the object. Different properties on the object specify a different kind of access permitted for the listed organizations. Document revisions for instance have receiving organization(s) that permits listed organizations to find the revision, while the controlling organization can both find and edit the revision. Functions available based on find, edit, as well as some others, are listed in the permissions matrix: 40001-IS-GDL-60049.
|
SPF Object Type
|
Object Properties
|
|
Document Revision
|
Organization (a.k.a. Originating Organization)
|
|
|
The name of the organization authoring the document; where authoring refers to that organization updating the content on a specific revision of the document. This type of organization is provided with read/write access to specific revisions of the document.
|
|
|
Controlling Organization
|
|
|
The name of the organization (ESP) responsible for facilitating the author to manage the revision of the document in SPF. Examples include: creation of SPF objects like the document container / revision, facilitating to upload files to the document containers, reviewing and updating revision metadata. This type of organization is provided with read/write access to specific revisions of the document.
|
|
|
Receiving Organization
|
|
|
The name of the organization(s) to which the document revision is addressed. This includes any organizations that would need to see the revision if for review or simply for information. This type of organization is provided with read only access to specific revisions of the document.
|
|
Transmittals and TQs
|
Organization (a.k.a. From Organization)
|
|
|
The name of the organization authoring the object; where authoring refers to that organization creating the content. This type of organization is provided with read/write access.
|
|
|
To Organization
|
|
|
The name of the organization(s) to which the object is addressed. This includes any organizations that would need to see the item for review, response, or simply for information. This type of organization can respond to workflow actions or otherwise, is provided with read only access.
|
|
Packages
|
Organization
|
|
|
The name of the organization(s) to which the object is shared. This includes organizations that are adding content to the package. This type of organization is provided with the ability to associate content to the object.
|
|
Tags and Model IDs
|
‒There are no organizational controls on CDW Tags and Model IDs
|
|
|
‒There are no organizational controls on CTA Tags; however, these are not visible to third party contractors and vendors
‒While not influential on access control, tags do have additional organization properties established from the BHP class library. These properties are integrated across the design tools and described here.
|
Notes:
-
ESPs have access to information from ALL organizations within the Plant/Project in which they are acting as an ESP .
-
The originating, controlling and receiving organizations are set on creation of the revision object in SPF.
-
Publishing revisions from a design tool instantiates or updates the originating, controlling, and receiving organizations.
-
The receiving organizations are automatically updated with the transmittal’s To Organizations field on approval by document control in the transmittal workflows. This means that access to a revision is automatically provided to third parties by transmitting the information to them. Should a transmittal be cancelled, reversal of the access must be performed manually. You may need to request help from Document Control to revert third party access to a document revision.
-
Document control and PIM can update organizational access at any time.
-
Properties are otherwise set through the standard use of objects within the system.
|