SPF Organizations

 
SPF Organizations serve to fulfill a couple of important roles: They control access to information and are found among different properties defined by the BHP Class Library.  Refer to Information Access Control for details on how they control user access.  This section identifies how SPF Organizations satisfy specific properties of the BHP Class Library.  The table lists those tags attributes for which an SPF Organization is relevant. 
 
Attribute
Intention
Examples
SPF List Identifiers
Tag Owning Organization (Creation Organization)
Used for filtering out BHP tags from project deliverables: On creation of a tag in CTA an organization is specified; When tools publish tags this value is NULL but understood to be "HBJV"
HBJV, or BHP
N/A
Equipment Vendor Name
In this context the vendor means that vendor that is supplying the item when the project (i.e. HBJV) procures the item.
 
All Orgs
Supplier Name
Name of the intermediate vendor that the tagged item was procured from.
Distributed by Lakeside
All Orgs
OEM Name
The name of the Original Equipment Manufacturer (OEM) that produces the item.  Note:  This could be an SSA supplier/vendor
Rosemount instrument
All Orgs and Manufacturers
Originating Contractor
The originating contractor associated with the design of the equipment/item
Designed by HBJV, STANTEC,  DMC, TRL, or Filter Box
All Orgs and Originating Contractors
Construction Contractor Name
The contractor associated with the installation of the equipment/item
Installed by PCL or KDM
All Orgs and Construction  Contractors
 
Understanding what properties has been configured for an organization
The X tile (To Be Developed) in SPF shows a searchable list of organizations in the system and whether the organization has been identified as a Manufacturer, Originating Contractor, and/or Construction Contractor.  These identifiers determine whether the use for that property has been configured in SPF.  Since all organizations are included in the All Orgs list, they are all available for use under the Equipment Vendor Name and Supplier Name properties in SPF. 
 
The configuration in SPF and the Design Tools is independent and while the configuration may have been completed in SPF, it may not have been finalized in the design tools.  Conversely, it is possible to configure an organization in a design tool without having requested the organization for SPF.  Procedurally, the systems teams are working collaboratively to register organizations in SPF first and relay the information back to the other teams to complete the integrated configuration.  Ensuring that SPF is updated first is key to avoiding issues with duplicated organizations and problems with integration.
 
Requests for organizations (new or modification to existing)
On request to add or modify SPF Organizations, the relevant SPF List Identifiers should be included with the request to ensure that the appropriate technical objects and mappings are instituted.  Request shall be channeled to the SPF Team to first check for uniqueness of the name.  As the work is completed in SPF, the information will be passed along to the BHP, EDS, and integration teams so that they can complete the remaining work as required.