2.21.1 Introduction to Shopping Cart Processing for IT

Manual Transmittal

November 27, 2019

Purpose

(1) This transmits revised IRM 2.21.1, Shopping Cart Processing for Information Technology Products and Services, Introduction to Shopping Cart Processing for IT.

Material Changes

(1) The IRM reflects current process and procedures, references and links.

(2) The Terms/Definitions/Acronyms Listing has been updated to remove some definitions and to add 6 new acronyms.

(3) The Request Funding Section has been updated to include information on unfunded requests.

(4) Included in the IRM are the work step instructions on how to process a shopping cart returned by Procurement.

(5) Tier II Reviews are no longer required and have been removed from the IRM.

(6) Determine the Shopping Cart Routing Path Section has been restructured to reflect the supplemental guidance from the Delegation Order IT-2-1-1.

(7) The Delegation Order (DO) IT-2-1-1-A, Consent to Approval of Justifications for Other Than Full & Open Competition (JOFOCs), Justifications for an Exception to Fair Opportunity (JEFOs) and Limited Sources Justifications (LSJs) is referenced in the IRM

(8) The new Delegation Order (DO) IT-2-1-2, Authority to Approve Acquisition Plans, is covered in the IRM.

(9) “Prepare Shopping Cart” and the “Review and Approve Shopping Cart” sections have been revised to include the language on unfunded shopping carts details.

(10) Removed all obsolete policy statements and references.

Effect on Other Documents

IRM 2.21.1, dated July 1, 2019, is superseded.

Audience

All IRS personnel involved in the processing of shopping carts for IT products and services.

Effective Date

(11-27-2019)


Nancy A. Sieger
Acting Chief Information Officer

Program Scope and Objectives

  1. Purpose: The purpose of this IRM is to identify the policies, processes and information required to create a Procurement for Public Sector (PPS) shopping cart for IT products and services and the approvals required during the processing of the shopping cart.

  2. Audience: IRS personnel involved in the creation, review and approval of shopping carts for IT products and services.

  3. Policy Owner: Director, Strategic Supplier Management

  4. Program Owner: Program Management (an organization within IT, Strategy & Planning).

  5. Primary Stakeholders: Procurement; Privacy, Government Liaison and Disclosure (PGLD).

  6. Program Goals: Ensure that shopping carts for IT Products/Services have the following attributes:

    1. Required fields are completed accurately.

    2. Required acquisition documentation is attached.

    3. Required reviews are documented.

    4. Required approvals are obtained.

    5. Acquisition planning dates are met.

Background

  1. IRS IT is responsible for approving the expenditure of IT funding based on Delegation Order IT-2-1-1, Approval of Information Technology (IT) Requisitions.

  2. Internal IT organizations and stakeholders have reviews and approvals that need to be documented.

Authority

  1. IRM 1.2.41, Servicewide Policies and Authorities, Delegation of Authorities for IT Activities grants the Chief Information Officer (CIO) the authority to govern all areas related to Information Resources and Technology Management.

  2. Delegation Order IT-2-1-1, Approval of Information Technology (IT) Requisitions, provides IRS IT leadership with delegated signature authority for approving IT purchases of goods and services.

  3. IRM 1.2.1.3.4 (08-01-2019), Policy Statement 2-92, (1) Deviation from compatibility standards for Federal Information Processing (FIP) equipment and software requires CIO approval.

  4. IRM 1.2.1.3.5 (08-01-2019), Policy Statement 2-93, (1) Management and Control of Automated Data Processing (ADP) Property.

Roles and Responsibilities

  1. Technical Point of Contact (TPOC): The person who is responsible for working with the applicable IRS organization to transform the business requirement into a technical requirement and completing the acquisition package.

  2. Requestor: The person who enters a shopping cart into PPS and tracks it through the approval path to Procurement.

  3. Signatory Authority Approver: The person who has the responsibility to ensure the shopping cart is fully compliant with IRS requirements and has the authority to approve shopping carts up to a specified dollar amount as described in Delegation Order IT-2-1-1.

  4. Financial Plan Manager (FPM): The person who manages the overall spending within the financial plans under their control and approves shopping carts in accordance with IRM 1.35.24, Financial Accounting, Establishing Commitments and Obligations.

Program Management and Review

  1. Program Reports

    1. PPS Report: This report shows shopping carts generated from PPS that are en-route to Procurement.

    2. IT Contract Tracker (ITCT) Reports: In FY20, the ITCT replaced the report formerly known as the $150K list. Data in the ITCT is maintained by the CORs. The reports are used in monthly meetings with each ACIO and Procurement to discuss critical contract actions and shopping carts of concern.

    3. Acquisition Timeliness: The date that shopping carts reached Procurement is compared to Procurement’s Acquisition Planning Due Dates for the fiscal year to determine if they are timely. Strategic Supplier Management (SSM) provides a report to measure each ACIO’s timeliness of shopping carts.

  2. Program Effectiveness:

    1. This IRM is reviewed annually to ensure that the information about required reviews and the shopping cart creation process are current. Feedback on the effectiveness of the required reviews is shared with the responsible stakeholder organizations for consideration as part of the annual IRM review process.

Program Controls

  1. Program Controls help SSM to oversee the status of shopping carts for the ACIOs.

    1. Data calls are sent by SSM throughout the fiscal year for ITCT updates to be made by the ACIO Acquisition Program Managers (APMs) and Contracting Officer’s Representatives (CORs). The IT areas are responsible for updating their shopping carts entries in the IT Contract Tool (ITCT).

    2. Monthly meetings are held in quarters 1-3 of the FY with Procurement, Financial Management Services (FMS) and APMs to discuss the status of shopping carts. The frequency of these meetings changes to biweekly in the 4th quarter.

Terms/Definitions/Acronyms

  1. Defined Terms

    Term Definition
    Financial Plan Manager (FPM) verifies that there is adequate and appropriate funding available; is in approval path
    Requestor initiator of shopping cart
    Shopping Cart used to request external goods and services and to secure the necessary approval and funding for those goods and services prior to the request being submitted (formerly called a requisition)
    Signatory Authority Approver the person under IT-2-1-1 who has the authority to sign up to a specified dollar amount and who ensures that the shopping cart is fully compliant with IRS requirements prior to forwarding it to the FPM
  2. Defined Acronyms

    Acronym Definition
    ACIO Associate Chief Information Officer
    ADP Automated Data Processing
    APs Acquisition Plans
    APM Acquisition Program Manager
    BU Business Unit
    CIO Chief Information Officer
    CO Contracting Officer
    COR Contracting Officer’s Representative
    DCIOs Deputy Chief Information Officers
    DME Development, Modernization and Enhancement
    EA Enterprise Architecture
    EIT Electronic and Information Technology
    ESP Enterprise Standards Profile
    FMS Financial Management Services
    FPM Financial Plan Manager
    IGCE Independent Government Cost Estimate
    IRSAP Internal Revenue Service Acquisition Procedures
    IT Information Technology
    ITCT Information Technology Contract Tool
    JEFOs Justifications for an Exception to Fair Opportunity
    (JOFOCs) Justifications for Other Than Full & Open Competition
    LSJs Limited Sources Justifications
    O&M Operations and Maintenance
    PA Privacy Act
    PGLD Privacy, Government Liaison and Disclosure
    PII Personally Identifiable Information
    PPS Procurement for Public Sector
    PWS Performance Work Statement
    SAM Software Asset Management
    SBU Sensitive But Unclassified
    S&P Strategy and Planning
    SIW Senior Executive Service in Waiting
    SOW Statement-of-Work
    SSM Strategic Supplier Management
    TCV Total Contract Value
    TPOC Technical Point of Contact
    UWR Unified Work Request
    WRMS Work Request Management System

Related Resources

  1. Acquisition Planning Due Dates

  2. Form 14775, Security Compliance Review Checklist for IT Acquisitions

  3. IRM 2.15.1, Enterprise Architecture (EA), EA Overview

  4. IRM 10.8.1, IT Security, Policy and Guidance

  5. Section 508

  6. IRM 11.3.24, Communications & Liaison, Disclosure of Official Information Disclosures to Contractors

  7. IRSAP Section w1039.9001 Software Development Prerequisites

  8. IT-2-1-1-A, Consent to Approval of JOFOCs, JEFOs and LSJs

  9. IT-2-1-2, Delegation Order Authority to Approve Information Technology (IT) Acquisition Plans

  10. IRS Procurement - Acquisition Package Document Checklist (IT and Non-IT)

  11. IT Shopping Cart Checklist

  12. Procurement 101

  13. Procurement for Public Sector (PPS)

  14. Process Returned Shopping Cart - Business Unit

  15. PPS Work Step Instructions

Determine if an Acquisition is Needed

  1. In-house: If the IT organization can provide the needed IT products or services, develop a work request as described in IRM. 2.22.1, Business Planning & Risk Management (BPRM), Unified Work Request (UWR) Process.

  2. Outsource: If the IT organization cannot provide the needed IT products or services, plan an acquisition as described in the next section.

Acquisition Planning

  1. The TPOC or COR, serving in the TPOC role, plans the acquisition and produces the documents needed by Procurement. The required documents are described in the IRS Procurement - Acquisition Package Checklist (IT and Non-IT).

  2. The following clarification is provided for the Authority to Approve IT Acquisition Plans (APs):

    1. In accordance with Treasury Department Memorandum for Bureau Chief Information Officers (CIOs), dated March 15, 2019, the IRS CIO is responsible for approving all IT Acquisition Plans (APs) for contracts with a Total Contract Value (TCV) greater than $250K or with periods of performance greater than five years. This responsibility will be implemented as follows:

    • All IT APs with a TCV greater than $50M or with periods of performance greater than five years will be reviewed and approved by the IRS CIO after all required Procurement reviews.

    • All IT APs with a TCV greater than $20M and less than $50M will be reviewed and approved by an IRS DCIO after all required Procurement reviews.

    • All IT APs with a TCV greater than or equal to $10M and less than $20M will be reviewed and approved by the IRS ACIO Strategy & Planning (S&P) after all required Procurement reviews.

  3. Requests for CIO, DCIO, S&P signature of IT APs will be sent to the Director, Strategic Supplier Management (SSM) or designee. The signature authorities and delegations are covered in Delegation Order IT-2-1-2, for IT Acquisition Plans.
    All IT APs with a TCV less than $10M will be reviewed and approved by Program Managers (PM) or Contracting Officer’s Representatives (COR).
    All IT APs with a TCV greater than or equal to $68M or with periods of performance greater than five years will be forwarded to the Treasury CIO for review and approval after all required Procurement reviews and IRS CIO signature approval.

  4. Acquisitions should be planned to meet Procurement’s Acquisition Planning Due Dates.

  5. A shopping cart is required to exercise an option.

    Note:

    If a justification for other than full and open competition is required, after the shopping cart is forwarded to Procurement, the justification will be approved in accordance with Delegation Order IT-2-1-1-A.

Develop Requirements

  1. Procurement 101 provides guidance on developing requirements. Treasury policy and standard forms are also located on the Acquisition Gateway in the Treasury Hub.

  2. Privacy Act (PA)/Personally Identifiable Information (PII): If the acquisition involves the creation, collection, use, processing, storage, maintenance, dissemination, disclosure, or disposal of information that is linked or linkable to an individual, contact the *Privacy mailbox for a pre-award review for compliance with privacy and disclosure requirements. See IRM 11.3.24, Disclosures to Contractors for further information.

    1. Caution: A contractor and its employees are not considered employees of the Department of the Treasury for purposes of the Privacy Act 5 USC § 552a. Therefore, PA protected records cannot be disclosed to contractors pursuant to 5 USC § 552a(b)(1). Disclosures of such records to contractors may be made only if one of the statutory disclosure provisions applies. The most commonly applicable disclosure provisions are 1) a published “routine use” in the appropriate system of records notice and 2) written consent to the disclosure from the individual whose records are at issue.

    2. Caution: A contractor and its employees are subject to the PA’s criminal penalties pursuant to 5 USC § 552a(m)(1) if the contract is to operate a system of records for the agency. The IRS routinely includes disclosure prohibitions in contracts that authorize contractor access to PA protected records.

    3. Caution: For tax returns and return information, IRC § 6103 preempts the PA. Disclosure of tax returns and return information is controlled by IRC § 6103. Returns and return information may not be disclosed to a contractor unless the requirements of IRC § 6103 are met (regardless of whether the PA authorizes disclosure). See IRM 11.3.24 for tax returns and return information contract requirements pertaining to disclosure and IRM 11.3.14.8.1 for privacy requirements. A general nondisclosure clause is not sufficient to meet 6103 (n) requirements to authorize disclosure.

  3. Sensitive But Unclassified (SBU) Information: All IRS IT hardware, software and files are designated as SBU based on the potentially sensitive information they contain. Accordingly, all IT acquisitions for appropriate Disclosure terms and Conditions in the contract can be via the IRM 11.3.24, Disclosures to Contractors.

    Note:

    Post-award compliance contract reviews are conducted to monitor conformity with Disclosure, Privacy Act and Safeguard policies and procedures.

Request Funding

  1. Request funding for the requirement. The FPM must validate funding and accounting string information.

    Note:

    Do not use a purchase card for Electronic and Information Technology (EIT), as EIT is on the Restricted Purchase List.

    When Funding is not in budget and is required, an Unfunded Needs Request form must be completed, signed by the requesting ACIO/designee and submitted to FMS. FMS reviews the request with the CIO and obtains approval or disapproval. This is for Operations and Maintenance (O&M) and Development, Modernization and Enhancement (DME) items.

  2. For unfunded shopping carts, obtain the accounting codes from TPOC or Project Manager and include them on the Funding Template.

  3. Procurement may return an approved unfunded shopping cart to the FPM to add funding.

    1. If changes have been made to the acquisition package that require additional levels of approval, the shopping cart must go through the same approvals as a new requirement.

    2. If no changes have been made that require a difference level of approval, the FPM will send the shopping cart directly back to Procurement once the funds are added.

  4. When an unfunded shopping cart is submitted, Procurement must be notified of the pending acquisition need and that funding is not available yet. An acquisition package must be sent to Procurement so the Acquisition Planning Due Date is met, especially when the acquisition need is for the first quarter of the next fiscal year.

Obtain Requirements Reviews and Approvals

  1. Enterprise Systems Management Review (ESMRVW) – Software acquisitions must be approved by Enterprise Architecture (EA), with the exception of Common Operating Environment (COE) above-baseline software purchased for the desktop environment. You can find additional references and guidance in IRM 2.15.1, Enterprise Architecture (EA), EA Overview.

    1. If the requirement is for the purchase of any software product, check the Enterprise Standards Profile (ESP) to see if it is already approved and available in the catalog.

    2. If you can’t find the product or standard for the software product in the ESP, submit an EA ESP Change Request.

      Note:

      This submission requires access to the Work Request Management System (WRMS). Direct questions to the EA Office’s Standards and Technology Management at *EA Change Requests.

  2. Technical Tier III Review: This tier consists of end-user computing-related hardware, software, maintenance and related services, including desktops, laptops and personal communications devices.
    i. Requests for software purchases/maintenance should be submitted to the User and Network Services (UNS) Software Asset Management (SAM) group with the purchase details (e.g., software name, version, quantity, cost) using the *IT T3 Software Review mailbox or email IT.T3.Software.Review@irs.gov.
    ii. If the acquisition is for Tier III IT hardware/maintenance and related purchases, the Statement-of-Work (SOW)/Performance Work Statement (PWS) must be sent to *IT Asset Management Review mailbox or email IT.EUES.AM.Req@irs.gov to be reviewed and to prepare for proper hardware asset barcoding, tracking, management and shipment confirmation.
    iii. Once approval has been obtained, the applicable review completion/approval e-mail(s) must be attached to the shopping cart.

  3. Security Compliance Review: This review applies to the following:

    1. any acquisition for the procurement of an IT system, or IT products; any IT hardware and/or software, telecommunications, equipment, maintenance or service.

    2. acquisition of any consulting services, commercial service provider, out-sourcing or cloud provider that will operate, manage, access or use any IRS IT system and/or data, including SBU, PII and/or IRS taxpayer data.

    Complete and submit IRS Form 14775, Security Compliance Review Checklist for IT Acquisitions must be completed and submitted for approval. Once approval has been obtained, the approved Form 14775 must be attached to the shopping cart.

    Note:

    PerIRM 10.8.1, IT Security, Policy and Guidance, any vendor that will operate, manage or use any IRS IT system and/or data, including SBU, PII and/or IRS taxpayer data, must follow the guidance of IRS. IRS Publication 4812, Contractor Security Controls for any contractor operated system and is subject to the IRS contractor site review/assessment process.

  4. Section 508 Compliance: for information technology purchased, developed and maintained, the technology must be compliant with Section 508 of the Rehabilitation Act and Section 255 of the Act.

    Note:

    Section 508 does not apply if state and local entities are the supplier.

Determine the Shopping Cart Routing Path

  1. IT shopping carts initiated by an IT ACIO area must be routed to the appropriate manager, per Delegation Order IT-2-1-1, for review and approval.

    Note:

    Each ACIO may have their own internal management review process, which may require adding reviews prior to the Signatory Authority Approver.

  2. Signature Authority Approver: The signature authorities and associated re-delegations supported by Delegation Order IT-2-1-1, apply to shopping carts for purchases of IT products and services.

  3. FMS Financial Plan Manager approves IT shopping carts in accordance with IRM 1.35.24, Financial Accounting, Establishing Commitments and Obligations.

  4. IT shopping carts, initiated by a non-IT BOD, must be routed to the Appropriate ACIO for review and approval only after FMS has approved funding.

Strategic Supplier Management (SSM) Approval

  1. The SSM Director or designee approval is required on shopping carts for:

    1. Bailment agreements, no cost demonstrations, Request for Information (RFI), Market Research Requests or evaluation agreements for software, hardware, managed services and “cloud” based services, regardless of dollar value;

    2. “Pilot IRS” regardless of dollar value;

    3. Infrastructure acquisitions (e.g., servers, mainframes, network/telecom, managed services, “cloud” based services) and infrastructure-related services with an Independent Government Cost Estimate (IGCE) greater than or equal to $1,000,000. Infrastructure related services are services supporting the delivery, installation and initial configuration of the new infrastructure;

    4. Software acquisitions with an IGCE greater than or equal to $1,000,000.

  2. For clarity, shopping carts in the following categories do not require SSM approval:

    1. Services supporting application development, middleware configuration and operation, instrumentation and other work performed above the network layer; and

    2. Services supporting non-infrastructure related work, such as cyber analysis, data analysis, business process improvement and other services not directly related to IT infrastructure installation or configuration.

  3. SSM review will be conducted prior to ACIO/Director/Senior Manager approval of the shopping cart via Procurement for Public Sector (PPS) routing. The review will determine if similar, in-place agreements or capabilities should be used or if requirements could be combined to improve economies of scale to reduce costs to the IRS.

  4. In support of this review, Program/Project Managers, Acquisition Program Managers (APMs) and TPOCs/CORs are encouraged to contact SSM as soon as upcoming requirements are identified. SSM reviews will be completed within the following timeframes:

    1. 8 working days after approval request for shopping carts with an IGCE value less than $4,000,000; or

    2. 15 working days after approval request for shopping carts with an IGCE value from $4,000,000 to $10,000,000; or

    3. Case-by-case basis as determined by Director, SSM or designee, for shopping carts with an IGCE value greater than $10,000,000.

Signature Authority Approval

  1. Each ACIO may have their own internal management review process, which may require adding reviewers prior to the Signatory Authority Approver.

  2. IT shopping carts initiated by a non-IT BOD must be routed to the appropriate ACIO for review and approval only after FMS has confirmed there is approved funding.

  3. The signature authorities and associated redelegations supported by Delegation Order IT-2-1-1 apply to shopping carts for purchases of IT products and services.

    1. Signature authority up to $50,000 for shopping carts/purchase card transactions that support non-IT goods or administrative services (court reporters, movers, executive certificate framing, fax/printer toner, general office supplies) and IT operating costs specifically associated with telecommunications recurring billing (i.e., local/long distance phone service) may be approved by the senior manager or frontline manager.

    2. This authority cannot be redelegated and acting managers are not approved as proxies. The contract writing system (PPS) record must include the approval of the signature authority. Signature authority for shopping carts greater than $50,000 (cumulative) revert to standard IT shopping cart signature authority.

    3. The Delegation and Signature sheet called Shopping Cart Signature Authority List outlines each level of funding authority. This sheet is updated monthly or whenever an executive change occurs. Due to the length and frequency of senior manager and frontline manager changes, it is not feasible to include these names in the Shopping Cart Signature Authority List.

  4. Shopping Cart Proxy, Actors and Executive Officers or SES in Waiting (SIW) - Situations arise when executives cannot electronically approve shopping carts due to non-system access such as vacations or conferences.

    1. Executive Officers or SES in Waiting (SIW) in Executive Positions: Executive Officers or SES in Waiting (SIW) are employees who are performing in Executive positions but have not completed their executive certification. These candidates are authorized to sign as approvers commensurate with the level of the position they are filling.

    2. Proxies for Executives: Executives who cannot electronically approve shopping carts due to non-system access (such as computer downtime) can designate a proxy staff member on an as-needed basis to perform the electronic signature. The staff person is responsible for obtaining and retaining electronic approval of the proxy delegation (via e-mail) for audit purposes. The staff person performing the proxy action must state in the PPS approval comments section: "Proxy (name) Approved and signed by (title and name) on (date). The e-mail approval of shopping cart is on file."

    3. Executives Appointing Actors with Same Funding Authority: Executives, who will be unavailable for specific periods, can appoint another executive to "act" in their position. Non-executive staff personnel cannot be given acting authority in terms of approving shopping carts. To clarify the process, the designating executive is the unavailable executive and the executive appointed will be called an actor.
      When the designating executive and the actor have the same funding level authority, the shopping cart routing path should be changed to the actor’s name instead of the designating executive name. This should be completed before the shopping cart reaches the designating executive in PPS or the document routing becomes an issue in the electronic system. The only remedy when this occurs is for the helpdesk to redirect the shopping cart. Contact the helpdesk via phone (240-613-8540).

    4. Executives Appointing Actors with Lower Funding Authority: When a designating executive’s funding authority is higher than the actor, a formal "acting" document must be generated and retained for audit purposes. This documentation will allow the acting executive to approve shopping carts at the designating executive's higher funding authority.
      • This formal acting authorization must be in a memo or email. The authorization must contain the actor’s authority for a specific period. This authorization must be retained by the actor for audit purposes.
      • When the actor approves a shopping cart, an additional statement must be inserted in the PPS approval comment section. The comment should state "Acting for (name) from (date) to (date). Acting documentation on the file with the Acting Executive."

    5. Proxies and Actors for Senior Managers and Frontline Managers: There is no authorization for a senior manager or frontline manager to designate a proxy or an actor to approve shopping carts. Senior manager or frontline manager unavailability requires approval at a higher level.

  5. Approval of $0.00 Shopping Carts for Accounting Code Changes: IT Strategy & Planning, Financial Management Services, Senior and Frontline Managers may approve $0.00 shopping carts for accounting codes changes if they do not serve as an initiator of the shopping cart or as the Financial Plan Manager.

    Note:

    For shopping carts associated with purchase card transactions, consult the Purchase Card Guide for any associated dollar limits.

FMS Financial Plan Manager Approval

  1. FMS Financial Plan Manager approves IT shopping carts in accordance with IRM 1.35.24, Financial Accounting, Establishing Commitments and Obligations.

Prepare Shopping Cart

  1. The Requestor creates the shopping cart using the following guidance to ensure all fields are completed properly:

    1. IT Shopping Cart Checklist, which is used to guide the Requestor through entering information in the various tabs in PPS (e.g., General Data tab, Account Assignment tab and Item tab) and the required approval path. This must be completed during the shopping cart creation and added to the shopping cart attachments.

    2. Work Step Instructions, which are available for detailed guidance on completing the shopping cart fields.

      Note:

      In case of a Government shutdown, the information contained in the Contingency Contract the following fields must be completed: Contingency Contact information, Supports Essential Function, Lapse Plan Exception Code and Lapse Plan Justification.

  2. For software development acquisitions, the Request must indicate in the Description field of the PPS record that the shopping cart is for software development and describe the nature of the software development to be performed. This information notifies the Contracting Officer that required clauses must be incorporated into the contract. See Internal Revenue Service Acquisition Procedures (IRSAP) Section 1039.9001 Software Development Prerequisitesfor more information.

  3. An unfunded shopping cart is needed when funding is not available and one of the following is true:

    • the Acquisition Planning Due Date must be met

    • the acquisition need is for the first quarter of the next fiscal year

    • an option is being exercised


      i. A price, quantity and cost center data must be entered in the Item Overview line.
      ii. The Accounting Assignment Category must be changed from Cost Center to Unfunded.

  4. The Requestor attaches the required documents. as identified in the IRS Procurement - Acquisition Package Document Checklist (IT and Non-IT), to the shopping cart.

    Note:

    The IRS Procurement - Acquisition Package Document Checklist (IT and Non-IT) is not used for exercising an option, extensions or incremental funding. Please see the Procurement 101 Reference Guide for more details on "Exercising an Option" .

  5. Once all required documents are attached, the completed IRS Procurement - Acquisition Package Document Checklist (IT and Non-IT) is attached to the shopping cart to be used by shopping cart reviewers.

    Note:

    This checklist and all applicable documentation must be attached to the approved shopping cart in PPS to be considered a complete package. Many documents are collaborative; however, TPOCs/CORs must complete as much of the required information as possible and include signatures where applicable to avoid delays in processing.

  6. The Requestor validates the field entries and attaches the completed IT Shopping Cart Checklist to the shopping cart.

    Note:

    The IT Shopping Cart Checklist is not used for exercising an option, extensions or incremental funding.

  7. The Requestor submits the shopping cart for approval.

Review and Approve Shopping Cart

  1. Reviews are conducted in PPS sequentially. Reviewers may approve, edit or reject the shopping cart.

  2. The FPM validates availability of funds and releases the shopping cart to Procurement.

Process a Shopping Cart Returned by Procurement

  1. If an approved shopping cart is returned by Procurement, the Requestor follows the Work Step Instruction: Process Returned Shopping Cart - BusinessUnit.