The Structure of Procurement and Contract Packages in SPF
Figure 1: Complete procurement package in SPF
Figure 1 illustrates the structure of a procurement package within SPF. For every package defined, a root package (black tile) is created in accordance with the prescribed naming convention for the project. Every root package has several sub-packages. Commercial and technical sub-packages (blue tiles) collect items created by the contracting party for commercial and technical information respectively. In support of the pre-award processes, the yellow sub-packages represent submissions from various bidders (one sub-package per bidder). In support of the post-award processes, the orange sub-package supports the vendor as information is provided back to the contracting party.
SPF forms the structure by defining relationships between the objects in question. Some relationships are automated while others need to be managed by different users through the relationship builder. Refer to Creating Relationships between Objects.
The files belonging to bid submissions are automated by the bid import process (refer to Importing Bid Submissions). The vendor-to-document relationships should be established by the contracting party when allocating documents (placeholders) in SPF for the vendor to use.
Figure 2: Contract package in SPF
Each CWP is related to the contract using the relationship builder. Refer to Creating Relationships between Objects. With exception to a current limitation, the CWPs are included as part of the technical information when determining the items available for transfer to SMat.
