Attachment 2 Quality Assurance Surveillance Plan.docx

Quality Assurance Surveillance Plan

For

Intellectual Property and Technology Transfer Database Solicitation #: HT9425-24-R-0047 Contract # To Be Determined

Fort Detrick, Maryland

TABLE OF CONTENTS

Subject Page Number

1. Overview 3

2. Description of Services 3

3. Roles and Responsibilities 3

4. Contract Quality Requirements 4

5. Government Surveillance 4

6. Nonconformance Reports (NCRs) 5

7. Acceptance of Services 7

8. Contractor Performance Assessment Reporting System (CPARS) 7

9. Combating Trafficking In Persons 7

10. COR/Quality Assurance Surveillance Files 7

11. QASP Changes 7

1. Overview.

1.1. Purpose. The purpose of this Quality Assurance Surveillance Plan (QASP) is to identify the methods and procedures that the Government will use to ensure that it receives the services under this contract as identified in the Performance Work Statement (PWS).

1.2. Intent. The intent of this QASP is to: 1) ensure Contractor performance meets or exceeds contract terms, conditions and specifications; 2) hold the Contractor accountable for quality control; and 3) encourage the Contractor to take appropriate steps to control and improve quality. Accordingly, the Government will perform surveillance on the contract in accordance with this QASP, but reserves the right to monitor the contract in any manner necessary, at any times necessary, and at all places necessary to ensure that the rendered services conform to contract requirements. The Government also reserves the right to perform quality assurance at the Subcontractor level and perform quality assurance at the contractor's place of business, if applicable. Resolution of non-conforming services discovered at the Subcontractor level will be addressed with the prime Contractor.

2. Description of Services.

2.1. Scope of Work. The USAMRDC OSJA IP Group requires a Commercial-Off-The-Shelf (COTS) docketing and patent database software system along with associated customer support services, periodic software and system updates, training, and some flexibility for configuration and customization.

2.2. Type of Contract. Firm-Fixed Price (FFP) with COST Other Direct Cost (ODC) Contract Line Item Numbers.

3. Roles and Responsibilities.

3.1. Government.

3.1.1. Contracting Officer (KO). The KO is the only person with the authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government. Note: This is the only individual who can legally bind the Government.

3.1.2. Contracting Officer’s Representative (COR). The (COR) will be identified by a separate letter after contract award. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions; assure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor Contractor's performance and notify both the Contracting Officer and Contractor of any deficiencies; coordinate availability of Government furnished property, and provide site entry of Contractor personnel. A letter of designation will be issued to the COR, a copy of which will be sent to the Contractor, and will state the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

3.2. Contractor.

3.2.1. Contract Manager. This will be updated at time of award based upon Contractor proposal.

3.2.2. Project Manager. This will be updated at time of award based upon Contractor proposal.

3.2.3. Quality Manager. This will be updated at time of award based upon Contractor proposal.

4. Contract Quality Requirements.

4.1. Contractor’s Quality Control Program. The Contractor’s quality control program (IAW FAR Part 46 and applicable 52.246 Clause(s)) is the means by which the Contractor assures that work complies with the requirement of the contract. The Contractor shall ensure services are performed in accordance with this PWS. The Contractor shall identify, prevent, and ensure non-recurrence of defective services.

4.2. Government Quality Assurance. The Government shall evaluate the Contractor’s performance under this contract in accordance with this QASP. This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance and minimum acceptable defect rate(s).

5. Government Surveillance.

5.1. Methods of Surveillance. The following Methods of Surveillance will be utilized in monitoring the Contractors’ performance:

5.1.1. Random Sampling

5.1.2. Periodic Inspection

5.2. Surveillance Schedule. During contract performance, the COR anticipates performing random sampling at least quarterly and will perform periodic inspection on an ad hoc basis. In accordance with the Performance Work Statement, the COR expects to meet with the contractor biweekly (every other week) and will communicate negative findings resulting from this surveillance as early as possible. The COR and contractor may analyze whether the surveillance schedule is appropriate for the work being performed at any time. Additionally, the COR may rely upon the Procurement Integrated Enterprise Environment (PIEE), Surveillance Documents Section of the Contract File to establish a more formal surveillance schedule..

5.3. Surveillance Instructions/Checklists. Surveillance Checklists will be completed when surveillances are conducted and filed in the PIEE, SPM, Surveillance Documents Section of the Contract File using the Add Smart Form function.

5.4. Surveillance Documentation. At least monthly, the COR will complete surveillance documentation which will be filed in the PIEE, SPM, Surveillance Documents Section. Surveillance documentation may include a COR Status Report, the Surveillance Schedule, all completed Surveillance Checklist(s) for the period the COR Status Report covers, Nonconformance Reports, if any, and Contractor Deliverables, if any.

COR Status Reports will provide a synopsis of the Contractor’s performance , a summary of: surveillances performed; Nonconformance Reports, if any; an analysis of the Contractors performance; recommended adjustments to surveillance schedules; and any other pertinent contract information.

6. Nonconformance Reports (NCRs). Nonconformance occurs when a Contractor fails to meet Contract terms, conditions and/or specifications or the services are defective in some manner. All instances of nonconformance will be documented via a Nonconfomance Report Worksheet, Attachment 2 and the Contracting Officer will notify the Contractor in writing of the nonconforming performance. Resolution of nonconformance discovered at the Subcontractor level will be addressed with the prime Contractor. Nonconformance is classified as either: Level 1 (Minor); Level 2 (Major); or Level 3 (Critical). NCRs may contain multiple nonconformances, each characterized by a level and type. The level of the NCR should normally correspond to the highest level of nonconformance listed in the NCR. For example, if a NCR had one Level 3, one Level 2, and three Level 1 nonconformances, the NCR level would be Level 3. The exception might be when the aggregate of multiple nonconformances considered in whole associate to a more serious type of nonconformance defined in FAR 46.101 (e.g. if a NCR had three Level 2 nonconformances but the definition of critical nonconformance better describes the impact/effect when considered in whole, the NCR level would be 3).

6.1. Level 1 (Minor). Level 1 nonconformances are those that are ‘minor’ in nature such that they can be promptly corrected by the contractor, present no need for root cause analysis or determination if other contract requirements are affected, present no need for further preventive action, and do not materially reduce the usability of the supplies, services, construction, or deliverables. While the contractor must correct the nonconformance, further actions and Government follow-up are not required, and no written response from the contractor is needed.

6.2. Level 2 (Major). Level 2 nonconformance(s) are those that are ‘major’ in nature such that they are not promptly correctable, and/or warrant root cause analysis and preventive action, and/or need action by the contractor to determine if other contract requirements are affected. These nonconformances are serious enough to warrant not only correction of the nonconformance, but also a written response from the contractor in the form of a Corrective Action Plan (CAP), and Government follow-up. The qualifying distinction between a Level 1 and Level 2 nonconformance is the need for a CAP and Government follow-up. A NCR identifying a Level 2 nonconformance may also be issued after repetitive Level 1 instances of the same or similar nonconformance demonstrate the contractor is failing to institute effective corrective action and/or failing to implement effective quality and/or internal control(s). Repetitive Level 1/minor nonconformance of the same or similar requirement(s) increases the risk to the Government that continued, repetitious, or cumulative failures may materially reduce the usability of the supplies, services, construction, work, or deliverables for their intended purpose or is an indicator that root cause analysis and a CAP is required to fix the underlying conditions creating the nonconformance. Further, serious individual contractor employee misconduct discovered by the Government and traceable to contract requirements should normally result in a Level 2 nonconformance because the serious nature of misconduct necessitates contractor management conduct root cause analysis, take preventive actions, and requires Government follow-up (characteristics of a Level 2 NCR). Further, issue a NCR with a Level 3 nonconformance for serious contractor employee misconduct only when there is a trend demonstrating a breakdown in contractor management or processes allowing serious misconduct to repetitively occur, or the misconduct poses a hazardous or unsafe condition for the personnel receiving the contracted supply, service, or construction, and misconduct can be traced to nonconformance of contract requirements.

6.3. Level 3 (Critical). Level 3 nonconformance(s) are those that are ‘critical’ in nature such that they represent a serious weakness in internal controls and/or have actual or potential significant impact(s) on contract performance and/or the supported unit/Government operations. For these nonconformance(s), the qualifying distinction between a Level 2 and Level 3 nonconformance is the seriousness of the issue prompting the need for higher level management to address the nonconformance and resulting corrective action. Due to the nature of a Level 3 nonconformance, these types of nonconformance are candidates for contract remedies. Therefore, before issuance of a NCR with a Level 3 nonconformance, consideration should be made whether an NCR or contract remedy is more appropriate. Issuing a Level 3 NCR in lieu of a contract remedy would normally be considered the Government’s final attempt to work with the contractor to resolve a contractual nonconformance before contractual remedies are used. However, issuance of a Level 3 NCR is not a requirement before using contractual remedies. A NCR identifying a Level 3 nonconformance (or a contract remedy) may be issued after repetitive Level 2 instances of the same or similar nonconformance demonstrate the contractor is failing to institute effective corrective action or failing to implement effective quality/internal controls. Repetitive major nonconformances with the same or similar requirement(s) increase the risk to the Government that continued, repetitious, or cumulative failures may significantly impact the mission, or may result in hazardous/unsafe conditions.

6.4. Documenting NCRs. Use/fill out the Nonconformance Report Worksheet, Attachment 2, when nonconforming performance is identified. Documentation, as a minimum, will include: the Contract number; reference to the specific contract requirement; the specific discrepancy to the requirement; where it was discovered; the date and time it was discovered; and the Contractor representative who was notified. Also, include a suspense date for Contractor response/corrective action for Level 2 and Level 3 NCRs. The Contracting Officer must ensure appropriate level review and approval of the NCR Worksheet and then addresses the NCR in Letter Format to the applicable level of Contractor management based on the seriousness of the nonconformance.

6.5. Tracking and Resolving NCRs. All NCRs will be included in the COR’s Status Report. The Government considers Level 1 nonconformance closed as of the issuance of the Letter to the Contractor. However, your attention to address Level 1 Minor nonconformance is still required. Repetitive nonconformance of the same or similar requirement would be an indication the contractor failed to institute effective corrective action and/or failed to implement effective quality control and may result in a Level 2 NCR requiring submission of a CAP to the Government. The COR and KO shall track Level 2 and Level 3 NCRs to ensure the Contractor identifies and takes appropriate corrective action to the root cause and the specific nonconformance is corrected within the required timeline. The KO will make a final written determination of the Government’s remedies if the non-conformance is not corrected by the Contractor after receiving notice and a reasonable opportunity to correct the work.

7. Acceptance of Services. When all services have been deemed acceptable and there is documented objective quality evidence to support acceptable performance, the COR will accept the services provided and authorize payment of the Contractor. This is accomplished by approving the Contractor’s Receiving Reports in PIEE, WAWF.

8. Contractor Performance Assessment Reporting System (CPARS). Documented surveillance data (COR Status Reports, Completed Surveillance Checklists, Customer Feedback, Deliverables, if any, and Nonconformance Reports, if any) will be used to support CPARS ratings. CPARS will be completed in accordance with FAR Subpart 42.15 and DFARS Subpart 242.15 – Contractor Performance Information. The COR shall document that CPARS, if required, was completed in the COR Status Report for the month in which the CPARS was completed.

9. Combating Trafficking In Persons (CTIP). In accordance with PGI 222.17 and FAR 52.222-50, the KO will be notified immediately of any information from any source that alleges a Contractor employee, subcontractor and/or subcontractor employee has engaged in conduct that violates the United States Government “zero” tolerance policy regarding trafficking in persons.

10. COR/Quality Assurance Surveillance Files. The official COR/Quality Assurance Surveillance File will be maintained in PIEE, SPM IAW DoDI 5000.72, DoD Standard for COR Certification.

11. QASP Changes. This QASP is a living document and, as such, may be changed as needed based on ongoing government and Contractor communications and contract modifications, etc. The COR will send any recommended changes to the KO for approval and the KO must approve all changes.

ATTACHMENTS:

1. Performance Requirements Summary (PRS)

2. Nonconformance Report Worksheet

Attachment 1: Performance Requirements Summary (PRS)

Minimum Essential Characteristics and Capabilities

(PWS para 3.)

Obtain all necessary authorizations for Operation and Access by the End User

(PWS para 3.1.(e); and 5.1.)

The Contractor shall obtain all necessary authorizations within 4 months after contract award 100% Inspection

Install, Implement, Configure and Test System

(PWS para 5.2.)

The Contractor shall implement any requested configurable database fields and creation of reports required by the Government.

100% Inspection

Perform Data Audit, Upload Legacy Data and Validate Data (PWS para 5.3.)

Only accurate and corrected data shall be uploaded into the new system. The Contractor shall perform any necessary customization of fields required to receive uploaded data. Contractor shall perform any necessary conversion of data for migration or customization of fields required to receive uploaded data.

It is anticipated that the Contractor and USAMRDC shall reach a consensus on the merging of the any duplicate data.

100% Inspection

Customer Support (PWS para 5.4.)

The Contractor shall organize and lead bi-weekly meetings with the Government to review the status of all open issues (e.g., helpdesk tickets).

100% Inspection

Training (PWS para 5.5.)

All training sessions shall take place within the Government's live system and utilizing Government data, without exception (no sample data sets). The Contractor shall provide an outline of each scheduled training session and any relevant digital materials in accordance with the deliverables requirements. The Contractor shall ensure any required training preparation time is conducted prior to scheduled training sessions to ensure normal functionality of the system and live data sets.

100% Inspection

The incentive for all Performance Objectives included in the table above is a Positive Past Performance Evaluation(s).

Attachment 2: Nonconformance Report Worksheet image1.emf

NCR Worksheet 5_Oct_18_Final_Blank

Please wait...

If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.

You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.

For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

\\redstoneapp13\acchomedir$\david.groell\My Pictures\ACC Logo.jpg

Nonconformance Report Worksheet

\\redstoneapp13\acchomedir$\david.groell\My Pictures\DA Seal.jpg

NCR Tracking number

1_Oct_2018

11.0.0.20130303.1.892433.887364

Awarding Contracting Agency

Contract Awarded after 1 Oct 2018?

Order Awarded after 1 Oct 2017?

Task/Delivery Order (Refer to FAR Subpart 4.16 )

52.212-4 Clause Included in Contract?

Contractor required to have Quality Management and/or Quality Control Plan?

Commercial Contract

Contact Information for individual who identified nonconformance

Contact Information for individual reviewing nonconformance

Contact Information for individual to Issue nonconformance

NC Tracking Number

Date Nonconformance Observed

Is there intentions to have pictures, examples, or other supporting evidence attached?

Reviewer Concurs

Complete section below for Major (Level 2) and Critical (Level 3)

Contractor Corrective Action Plan (CAP) received by Due Date?

Has Contractor requested an extension ?

Received CAP acceptable to Government ?

Was Corrective Action Successful?

Does this NCR need to be cancelled? (only when applicable)

Does this NCR need to have overall level adjusted? (only when applicable)

From Level to

Please ensure to generate an updated letter to contractor

OfficeDoDAAC:

DatofObs_YR:

Sequential number will be provided by Lead who is responsible for tracking the Organization Non conformances: 0001

Rating:

ClrForm:

command:

organization:

office:

DoD:

Non_DoD:

ODCYNS: --0001

Yes_Contract_Award_Post_1Oct18:

No_Contract_Award_Post_1Oct18:

ContractNbr_DODAAC:

ContractNbr_FY:

ContractNbr_Type:

ContractNbr_Unique:

Non_DoD_ContractNbr:

Yes-OrderPost1Oct17:

No_OrderPost1Oct17:

Subpart 4.16—Unique Procurement Instrument Identifiers

4.1600 Scope of subpart.

This subpart prescribes policies and procedures for assigning unique Procurement Instrument Identifiers (PIID) for each solicitation, contract, agreement, or order and related procurement instrument.

4.1601 Policy.

(a) Establishment of a Procurement Instrument Identifier (PIID). Agencies shall have in place a process that ensures that each PIID used to identify a solicitation or contract action is unique Government wide, and will remain so for at least 20 years from the date of contract award. The PIID shall be used to identify all solicitation and contract actions. The PIID shall also be used to identify solicitation and contract actions in designated support and reporting systems (e.g., Federal Procurement Data System, System for Award Management), in accordance with regulations, applicable authorities, and agency policies and procedures.)

(b) Transition of PIID numbering. No later than October 1, 2017, agencies shall comply with paragraph (a) of this section and use the requirements in 4.1602 and 4.1603 for all new solicitations and contract awards. Until an agency’s transition is complete, it shall maintain its 2013 PIID format that is on record with the General Services Administration’s Integrated Award Environment Program Office (which maintains a registry of the agency unique identifier scheme). The 2013 PIID format consisted of alpha characters in the first positions to indicate the agency, followed by alpha-numeric characters; the 2017 format instead has the AAC in the beginning 6 positions.

(c) Change in the Procurement Instrument Identifier after its assignment.

(1) Agencies shall not change the PIID unless one of the following two circumstances apply:

(i) The PIID serial numbering system is exhausted. In this instance, the contracting officer may assign a new PIID by issuing a contract modification.

(ii) Continued use of a PIID is administratively burdensome (e.g., for implementations of new agency contract writing systems). In this instance, the contracting officer may assign a new PIID by issuing a contract modification.

(2) The modification shall clearly identify both the original and the newly assigned PIID. Issuance of a new PIID is an administrative change (see 43.101).

4.1602 Identifying the PIID and supplementary PIID.

(a) Identifying the PIID in solicitation and contract award documentation (including forms and electronic generated formats). Agencies shall include all PIIDs for all related procurement actions as identified in paragraphs (a)(1) through (a)(5) of this section.

(1) Solicitation. Identify the PIID for all solicitations. For amendments to solicitations, identify a supplementary PIID, in conjunction with the PIID for the solicitation.

(2) Contracts and purchase orders. Identify the PIID for contracts and purchase orders.

(3) Delivery and task orders. For delivery and task orders placed by an agency under a contract (e.g., indefinite delivery indefinite quantity (IDIQ) contracts, multi-agency contracts (MAC), Government wide acquisition contracts (GWACs), or Multiple Award Schedule (MAS) contracts), identify the PIID for the delivery and task order and the PIID for the contract.

(4) Blanket purchase agreements and basic ordering agreements. Identify the PIID for blanket purchase agreements issued in accordance with 13.303, and for basic agreements and basic ordering agreements issued in accordance with subpart 16.7. For blanket purchase agreements issued in accordance with subpart 8.4 under a MAS contract, identify the PIID for the blanket purchase agreement and the PIID for the MAS contract.

(i) Orders. For orders against basic ordering agreements or blanket purchase agreements issued in accordance with 13.303, identify the PIID for the order and the PIID for the blanket purchase agreement or basic ordering agreement.

(ii) Orders under subpart For orders against a blanket purchase agreement established under a MAS contract, identify the PIID for the order, the PIID for the blanket purchase agreement, and the PIID for the MAS contract.

(5) Modifications. For modifications to actions described in paragraphs (a)(2) through (a)(4) of this section, and in accordance with agency procedures, identify a supplementary PIID for the modification in conjunction with the PIID for the contract, order, or agreement being modified.

(b) Placement of the PIID on forms. When the form (including electronic generated format) does not provide spaces or fields for the PIID or supplementary PIID required in paragraph (a) of this section, identify the PIID in accordance with agency procedures.

(c) Additional agency specific identification information. If agency procedures require additional identification information in solicitations, contracts, or other related procurement instruments for administrative purposes, separate and clearly identify the additional information from the PIID.

4.1603 Procedures.

(a) Elements of a PIID. The PIID consists of a combination of thirteen to seventeen alpha and/or numeric characters sequenced to convey certain information. Do not use special characters (such as hyphens, dashes, or spaces).

(1) Positions 1 through 6. The first six positions identify the department/agency and office issuing the instrument. Use the AAC assigned to the issuing office for positions 1 through 6. Civilian agency points of contact for obtaining an AAC are on the AAC Contact list maintained by the General Services Administration and can be found at http://www.gsa.gov/graphics/fas/Civilian_contacts.pdf. For Department of Defense (DoD) inquiries, contact the service/agency Central Service Point or DoDAAC Monitor, or if unknown, email DODAADHQ@DLA.MIL for assistance.

(2) Positions 7 through 8. The seventh and eighth positions are the last two digits of the fiscal year in which the procurement instrument is issued or awarded. This is the date the action is signed, not the effective date if the effective date is different.

(3) Position 9. Indicate the type of instrument by entering one of the following upper case letters in position nine. Departments and independent agencies may assign those letters identified for department use below in accordance with their agency policy; however, any use must be applied to the entire department or agency.

(vi) Task orders, delivery orders or calls under–

□ Indefinite-delivery contracts (including Federal Supply Schedules, Government wide acquisition contracts (GWACs), and multi-agency contracts);

□ Blanket purchase agreements; or

(4) Positions 10 through 17. Enter the number assigned by the issuing agency in these positions. Agencies may choose a minimum of four characters up to a maximum of eight characters to be used, but the same number of characters must be used agency-wide. If a number less than the maximum is used, do not use leading or trailing zeroes to make it equal the maximum in any system or data transmission. A separate series of numbers may be used for any type of instrument listed in paragraph (a)(3) of this section. An agency may reserve blocks of numbers or alpha-numeric numbers for use by its various components.

(5) Illustration of PIID. The following illustrates a properly configured PIID using four characters in the final positions:

(b) Elements of a supplementary PIID. Use the supplementary PIID to identify amendments to solicitations and modifications to contracts, orders, and agreements.

(1) Amendments to solicitations. Number amendments to solicitations sequentially using a four position numeric serial number added to the 13-17 character PIID beginning with 0001.

(2) Modifications to contracts, orders, and agreements. Number modifications to contracts, orders, and agreements using a six position alpha or numeric, or a combination thereof, added to the 13-17 character PIID. For example, a modification could be numbered P00001. This would be added to the end of the 13-17 character PIID illustrated in (a)(5) of this section.

(i) Position 1. Identify the office issuing the modification. The letter P shall be designated for modifications issued by the procuring contracting office. The letter A shall be used for modifications issued by the contract administration office (if other than the procuring contracting office).

(ii) Positions 2 through 6. These positions may be alpha, numeric, or a combination thereof, in accordance with agency procedures.

Each office authorized to issue modifications shall assign the supplementary identification numbers in sequence (unless provided otherwise in agency procedures). Do not assign the numbers until it has been determined that a modification is to be issued.:

Subpart 4.16—Unique Procurement Instrument Identifiers

4.1600 Scope of subpart.

This subpart prescribes policies and procedures for assigning unique Procurement Instrument Identifiers (PIID) for each solicitation, contract, agreement, or order and related procurement instrument.

4.1601 Policy.

(a) Establishment of a Procurement Instrument Identifier (PIID). Agencies shall have in place a process that ensures that each PIID used to identify a solicitation or contract action is unique Government wide, and will remain so for at least 20 years from the date of contract award. The PIID shall be used to identify all solicitation and contract actions. The PIID shall also be used to identify solicitation and contract actions in designated support and reporting systems (e.g., Federal Procurement Data System, System for Award Management), in accordance with regulations, applicable authorities, and agency policies and procedures.)

(b) Transition of PIID numbering. No later than October 1, 2017, agencies shall comply with paragraph (a) of this section and use the requirements in 4.1602 and 4.1603 for all new solicitations and contract awards. Until an agency’s transition is complete, it shall maintain its 2013 PIID format that is on record with the General Services Administration’s Integrated Award Environment Program Office (which maintains a registry of the agency unique identifier scheme). The 2013 PIID format consisted of alpha characters in the first positions to indicate the agency, followed by alpha-numeric characters; the 2017 format instead has the AAC in the beginning 6 positions.

(c) Change in the Procurement Instrument Identifier after its assignment.

(1) Agencies shall not change the PIID unless one of the following two circumstances apply:

(i) The PIID serial numbering system is exhausted. In this instance, the contracting officer may assign a new PIID by issuing a contract modification.

(ii) Continued use of a PIID is administratively burdensome (e.g., for implementations of new agency contract writing systems). In this instance, the contracting officer may assign a new PIID by issuing a contract modification.

(2) The modification shall clearly identify both the original and the newly assigned PIID. Issuance of a new PIID is an administrative change (see 43.101).

4.1602 Identifying the PIID and supplementary PIID.

(a) Identifying the PIID in solicitation and contract award documentation (including forms and electronic generated formats). Agencies shall include all PIIDs for all related procurement actions as identified in paragraphs (a)(1) through (a)(5) of this section.

(1) Solicitation. Identify the PIID for all solicitations. For amendments to solicitations, identify a supplementary PIID, in conjunction with the PIID for the solicitation.

(2) Contracts and purchase orders. Identify the PIID for contracts and purchase orders.

(3) Delivery and task orders. For delivery and task orders placed by an agency under a contract (e.g., indefinite delivery indefinite quantity (IDIQ) contracts, multi-agency contracts (MAC), Government wide acquisition contracts (GWACs), or Multiple Award Schedule (MAS) contracts), identify the PIID for the delivery and task order and the PIID for the contract.

(4) Blanket purchase agreements and basic ordering agreements. Identify the PIID for blanket purchase agreements issued in accordance with 13.303, and for basic agreements and basic ordering agreements issued in accordance with subpart 16.7. For blanket purchase agreements issued in accordance with subpart 8.4 under a MAS contract, identify the PIID for the blanket purchase agreement and the PIID for the MAS contract.

(i) Orders. For orders against basic ordering agreements or blanket purchase agreements issued in accordance with 13.303, identify the PIID for the order and the PIID for the blanket purchase agreement or basic ordering agreement.

(ii) Orders under subpart For orders against a blanket purchase agreement established under a MAS contract, identify the PIID for the order, the PIID for the blanket purchase agreement, and the PIID for the MAS contract.

(5) Modifications. For modifications to actions described in paragraphs (a)(2) through (a)(4) of this section, and in accordance with agency procedures, identify a supplementary PIID for the modification in conjunction with the PIID for the contract, order, or agreement being modified.

(b) Placement of the PIID on forms. When the form (including electronic generated format) does not provide spaces or fields for the PIID or supplementary PIID required in paragraph (a) of this section, identify the PIID in accordance with agency procedures.

(c) Additional agency specific identification information. If agency procedures require additional identification information in solicitations, contracts, or other related procurement instruments for administrative purposes, separate and clearly identify the additional information from the PIID.

4.1603 Procedures.

(a) Elements of a PIID. The PIID consists of a combination of thirteen to seventeen alpha and/or numeric characters sequenced to convey certain information. Do not use special characters (such as hyphens, dashes, or spaces).

(1) Positions 1 through 6. The first six positions identify the department/agency and office issuing the instrument. Use the AAC assigned to the issuing office for positions 1 through 6. Civilian agency points of contact for obtaining an AAC are on the AAC Contact list maintained by the General Services Administration and can be found at http://www.gsa.gov/graphics/fas/Civilian_contacts.pdf. For Department of Defense (DoD) inquiries, contact the service/agency Central Service Point or DoDAAC Monitor, or if unknown, email DODAADHQ@DLA.MIL for assistance.

(2) Positions 7 through 8. The seventh and eighth positions are the last two digits of the fiscal year in which the procurement instrument is issued or awarded. This is the date the action is signed, not the effective date if the effective date is different.

(3) Position 9. Indicate the type of instrument by entering one of the following upper case letters in position nine. Departments and independent agencies may assign those letters identified for department use below in accordance with their agency policy; however, any use must be applied to the entire department or agency.

(vi) Task orders, delivery orders or calls under–

□ Indefinite-delivery contracts (including Federal Supply Schedules, Government wide acquisition contracts (GWACs), and multi-agency contracts);

□ Blanket purchase agreements; or

(4) Positions 10 through 17. Enter the number assigned by the issuing agency in these positions. Agencies may choose a minimum of four characters up to a maximum of eight characters to be used, but the same number of characters must be used agency-wide. If a number less than the maximum is used, do not use leading or trailing zeroes to make it equal the maximum in any system or data transmission. A separate series of numbers may be used for any type of instrument listed in paragraph (a)(3) of this section. An agency may reserve blocks of numbers or alpha-numeric numbers for use by its various components.

(5) Illustration of PIID. The following illustrates a properly configured PIID using four characters in the final positions:

(b) Elements of a supplementary PIID. Use the supplementary PIID to identify amendments to solicitations and modifications to contracts, orders, and agreements.

(1) Amendments to solicitations. Number amendments to solicitations sequentially using a four position numeric serial number added to the 13-17 character PIID beginning with 0001.

(2) Modifications to contracts, orders, and agreements. Number modifications to contracts, orders, and agreements using a six position alpha or numeric, or a combination thereof, added to the 13-17 character PIID. For example, a modification could be numbered P00001. This would be added to the end of the 13-17 character PIID illustrated in (a)(5) of this section.

(i) Position 1. Identify the office issuing the modification. The letter P shall be designated for modifications issued by the procuring contracting office. The letter A shall be used for modifications issued by the contract administration office (if other than the procuring contracting office).

(ii) Positions 2 through 6. These positions may be alpha, numeric, or a combination thereof, in accordance with agency procedures.

Each office authorized to issue modifications shall assign the supplementary identification numbers in sequence (unless provided otherwise in agency procedures). Do not assign the numbers until it has been determined that a modification is to be issued.:

Subpart 4.16—Unique Procurement Instrument Identifiers

4.1600 Scope of subpart.

This subpart prescribes policies and procedures for assigning unique Procurement Instrument Identifiers (PIID) for each solicitation, contract, agreement, or order and related procurement instrument.

4.1601 Policy.

(a) Establishment of a Procurement Instrument Identifier (PIID). Agencies shall have in place a process that ensures that each PIID used to identify a solicitation or contract action is unique Government wide, and will remain so for at least 20 years from the date of contract award. The PIID shall be used to identify all solicitation and contract actions. The PIID shall also be used to identify solicitation and contract actions in designated support and reporting systems (e.g., Federal Procurement Data System, System for Award Management), in accordance with regulations, applicable authorities, and agency policies and procedures.)

(b) Transition of PIID numbering. No later than October 1, 2017, agencies shall comply with paragraph (a) of this section and use the requirements in 4.1602 and 4.1603 for all new solicitations and contract awards. Until an agency’s transition is complete, it shall maintain its 2013 PIID format that is on record with the General Services Administration’s Integrated Award Environment Program Office (which maintains a registry of the agency unique identifier scheme). The 2013 PIID format consisted of alpha characters in the first positions to indicate the agency, followed by alpha-numeric characters; the 2017 format instead has the AAC in the beginning 6 positions.

(c) Change in the Procurement Instrument Identifier after its assignment.

(1) Agencies shall not change the PIID unless one of the following two circumstances apply:

(i) The PIID serial numbering system is exhausted. In this instance, the contracting officer may assign a new PIID by issuing a contract modification.

(ii) Continued use of a PIID is administratively burdensome (e.g., for implementations of new agency contract writing systems). In this instance, the contracting officer may assign a new PIID by issuing a contract modification.

(2) The modification shall clearly identify both the original and the newly assigned PIID. Issuance of a new PIID is an administrative change (see 43.101).

4.1602 Identifying the PIID and supplementary PIID.

(a) Identifying the PIID in solicitation and contract award documentation (including forms and electronic generated formats). Agencies shall include all PIIDs for all related procurement actions as identified in paragraphs (a)(1) through (a)(5) of this section.

(1) Solicitation. Identify the PIID for all solicitations. For amendments to solicitations, identify a supplementary PIID, in conjunction with the PIID for the solicitation.

(2) Contracts and purchase orders. Identify the PIID for contracts and purchase orders.

(3) Delivery and task orders. For delivery and task orders placed by an agency under a contract (e.g., indefinite delivery indefinite quantity (IDIQ) contracts, multi-agency contracts (MAC), Government wide acquisition contracts (GWACs), or Multiple Award Schedule (MAS) contracts), identify the PIID for the delivery and task order and the PIID for the contract.

(4) Blanket purchase agreements and basic ordering agreements. Identify the PIID for blanket purchase agreements issued in accordance with 13.303, and for basic agreements and basic ordering agreements issued in accordance with subpart 16.7. For blanket purchase agreements issued in accordance with subpart 8.4 under a MAS contract, identify the PIID for the blanket purchase agreement and the PIID for the MAS contract.

(i) Orders. For orders against basic ordering agreements or blanket purchase agreements issued in accordance with 13.303, identify the PIID for the order and the PIID for the blanket purchase agreement or basic ordering agreement.

(ii) Orders under subpart For orders against a blanket purchase agreement established under a MAS contract, identify the PIID for the order, the PIID for the blanket purchase agreement, and the PIID for the MAS contract.

(5) Modifications. For modifications to actions described in paragraphs (a)(2) through (a)(4) of this section, and in accordance with agency procedures, identify a supplementary PIID for the modification in conjunction with the PIID for the contract, order, or agreement being modified.

(b) Placement of the PIID on forms. When the form (including electronic generated format) does not provide spaces or fields for the PIID or supplementary PIID required in paragraph (a) of this section, identify the PIID in accordance with agency procedures.

(c) Additional agency specific identification information. If agency procedures require additional identification information in solicitations, contracts, or other related procurement instruments for administrative purposes, separate and clearly identify the additional information from the PIID.

4.1603 Procedures.

(a) Elements of a PIID. The PIID consists of a combination of thirteen to seventeen alpha and/or numeric characters sequenced to convey certain information. Do not use special characters (such as hyphens, dashes, or spaces).

(1) Positions 1 through 6. The first six positions identify the department/agency and office issuing the instrument. Use the AAC assigned to the issuing office for positions 1 through 6. Civilian agency points of contact for obtaining an AAC are on the AAC Contact list maintained by the General Services Administration and can be found at http://www.gsa.gov/graphics/fas/Civilian_contacts.pdf. For Department of Defense (DoD) inquiries, contact the service/agency Central Service Point or DoDAAC Monitor, or if unknown, email DODAADHQ@DLA.MIL for assistance.

(2) Positions 7 through 8. The seventh and eighth positions are the last two digits of the fiscal year in which the procurement instrument is issued or awarded. This is the date the action is signed, not the effective date if the effective date is different.

(3) Position 9. Indicate the type of instrument by entering one of the following upper case letters in position nine. Departments and independent agencies may assign those letters identified for department use below in accordance with their agency policy; however, any use must be applied to the entire department or agency.

(vi) Task orders, delivery orders or calls under–

□ Indefinite-delivery contracts (including Federal Supply Schedules, Government wide…