# DLAD PGI PART 4 – ADMINISTRATIVE MATTERS

- DLAD PGI PART 4 – ADMINISTRATIVE MATTERS

- PGI SUBPART 4.70 – UNIFORM PROCUREMENT INSTRUMENT IDENTIFICATION NUMBERS

- PGI 4.7004-90 Supplementary procurement instrument identification numbers.

- PGI SUBPART 4.71 – UNIFORM CONTRACT LINE ITEM NUMBERING SYSTEM

- PGI 4.7104 Contract subline items.

- PGI 4.7104-1(b)(90) Format of sub-CLIN.

DLAD PGI PART 4 – ADMINISTRATIVE MATTERS

PGI SUBPART 4.70 – UNIFORM PROCUREMENT INSTRUMENT IDENTIFICATION NUMBERS

(Revised December 21, 2011 through PROCLTR 2012-13)

PGI 4.7004-90 Supplementary procurement instrument identification numbers.

(a) Corporate contracts.

(1) For existing (or legacy) corporate contracts, delivery orders for items in Enterprise Business System (EBS) shall be issued using the procurement instrument identification number (PIIN) designated by the issuing inventory control point (ICP) as the true basic contract PIIN. In addition, for legacy issued (existing) corporate contracts, the contract administrator for the basic contract may issue an administrative modification to advise the vendor that future delivery orders may be received from different ordering office with the same PIIN.

(2) Once all items on a corporate contract have converted from legacy to EBS, non-awarding ICP PIINs for corporate contract outline agreements, with two or more option years remaining shall be changed in SAP to be compliant with 4.7003-90. The contractor shall be informed of the PIIN change in the modification or letter to exercise the option.

(3) The contracting officer of the basic corporate contract, at the time of award, shall immediately disseminate a copy of the contract to each ICP that has items on the contract. The copy of the basic contract shall be provided to the acquisition specialist at each ICP who manages the outline agreement in SAP.

(4) For corporate contracts covered by SAP outline agreements, a separate outline agreement shall be loaded in the system by each ICP that issues a delivery order against the corporate contract. Each ICP will be responsible for loading and managing their outline agreement. The number and management responsibilities of outline agreements loaded into the system shall have the approval of the basic contract administrative contracting officer and of the supervisor of the acquisition specialist whose workload is affected.

(5) Acquisition specialists shall ensure that all supply planners, within their supply chains, who have items on the contract, are informed of the contract terms for ordering, including any minimum or maximum order quantities, dollar values or any special terms needed for ordering.

(6) Modifications to the basic contract shall only be made by the contract administrator of the awarding activity for the basic contract. The contract administrator of the basic shall inform and supply a copy of all modifications to the contract administrators at the other ICPs. If a contract administrator at one of the other ICPs has a need for a modification to the basic contract, that contract administrator should send that request to the contract administrator of the basic contract.

(7) When the acquisition specialist determines that there may be a need for more than one PIIN (other than exhaustion of SPIINs), the specialist will coordinate with the procurement systems and procedures division to determine if there is a solution to the situation. Results will be documented in the contract file. Exceptions to the single PIIN rule (other than exhaustion of SPIINs) must be approved by the Chief of the Systems and Procedures Division.

PGI SUBPART 4.71 – UNIFORM CONTRACT LINE ITEM NUMBERING SYSTEM

PGI 4.7104 Contract subline items.

PGI 4.7104-1(b)(90) Format of sub-CLIN.

The following sub-CLIN to CLIN format shall be used for solicitation and award documents in EBS, BSM and BSM BOSS.

Legacy CLIN/sub-CLIN | BSM CLIN
0001 | 0001
0001AA | 0002
0001AB | 0003
0002 | 0004
0002AA | 0005