SUBPART 39.90 – PROCEDURES, APPROVALS AND TOOLS

(a) The requiring activity shall coordinate all mid-tier requirements with DLA Information Operations, and other organizations as needed, prior to submission to the contracting office. “Mid-tier” refers to equipment that is in the range between individual workstations and mainframe computers. Mid-tier uses include client servers, network controllers, process controllers, and dedicated single application processors.

(b) DLA Contracting Services Office (DCSO) is the single DLA procuring organization with authority to procure office document devices and associated maintenance support. These devices include network and stand-alone copiers, printers, multi-functional devices, scanners, fax machines, and related support services. The DCSO CCO has authority to approve requests for waivers to this mandate.

(c) DCSO is responsible for acquiring IT services, supplies, equipment, training, and subscriptions for DLA. Non-DCSO procuring organizations may award contracts or orders for IT if the total value of the contract or order (including options) does not exceed $500,000.

(d) DCSO shall procure requirements with a value exceeding $500,000, unless the DCSO CCO approves a request for procurement authority from a non-DCSO procuring organization. Non-DCSO procuring organizations shall submit requests in writing to the DCSO CCO.

(e) Unless submitted through DCSO and authorized in writing by the DLA CIO, all DLA IT procurements shall use Defense Information Systems Agency defense enterprise integration services contracts.

(f) The DLA CIO shall staff all requirements to be acquired using the GSA federal systems integration and management program through the DCSO for informational purposes and investment accountability.

(g) The contracting officer shall comply with 4.1302 when acquiring personal identity verification products and services.

(h) Prior to acquiring commercial software or software maintenance, the contracting officer shall review DFARS Subparts 208.74 and 227.72, the DLA Issuance, Smartbuy, and Enterprise Software Initiative (ESI) Enterprise Service Agreements (ESA), which is accessible through eWorkplace, and the DLA Information Technology Solutions Document. The contracting officer shall submit requests for waiver (reference DFARS PGI 208.7403 and DFARS 227.72) to DLA Information Operations.

(i) The contracting officer shall coordinate any requirements for contractors to develop, store, process, display, or transmit information that is used in any DLA business process with DLA Information Operations in the acquisition planning stage.

(j) The contracting officer shall consult the DLA Information Technology Solutions Document in DLA eWorkplace under DLA Information Operations to ensure that there are no existing IT solutions that can meet the acquisition requirement.

(1) The contracting officer shall ensure compliance with all procurement requirements when using sources listed in the DLA Information Technology Solutions Document. Contracting officers shall consider the competitive process (reference FAR 6.1), and sole source and limited source justifications (reference FAR Subpart 6.3 and FAR 8.405-6), including brand name situations, economies of scale, and scope of the listed sources.

(2) The contracting officer shall contact DLA Information Operations to request the addition of a new solution to the document.

(k) For telecommunications equipment and services:

(1) The contracting officer shall ensure capital investment funding is used for capital investment requirements valued $250,000 or greater. Contracting officers shall coordinate questions concerning the appropriate type of funding with DLA Finance and Office of Counsel.

(2) The contracting officer shall sign Communication Services Authorities or other communications services orders or agreements.

(l) Internal Use Software (IUS).

(1) As defined in Statement of Federal Financial Accounting Standards (SFFAS) Number 10, Accounting for IUS, IUS is software used to operate a federal entity’s programs (e.g., financial, administrative, and project management software) and to produce the entity’s goods and services. DLAM 5000.76, Accountability of Capital Internal Use Software (IUS) contains IUS procedures.

(2) Requiring activity program managers (PMs) shall—

(i) Determine whether to classify a software procurement as IUS.

(ii) Structure software requirement deliverables in accordance with the IUS number structure guidelines stated in the IUS SOP.

(iii) State in the SOO, SOW, or PWS the IUS item that corresponds to the tasks required, which will be confirmed by the offeror in its proposal.

(iv) Prepare the IUS acknowledgement form.

(3) Contracting officers shall—

(i) Acknowledge that the IUS information was inserted into the SOO, SOW, PWS in accordance with the IUS SOP.

(ii) Sign the IUS acknowledgement and place it in the contract file.

(iii) Ensure contractors submit invoices in accordance with the IUS number structure. The contracting officer may delegate this responsibility to the contracting officer representatives (COR).

(iv) Ensure that CORs accept contractor deliverables and invoices consistent with invoiced IUS number structure.

(a) The requiring activity shall include the following in the acquisition package sent to the contracting officer:

(1) A statement clearly describing why the IT is needed and the program, project, Automated Information System being supported by the IT procurement.

(2) A description of what is being acquired. Identify the product (including its intended purpose, if unclear from the product name), manufacturer, model number, version number, quantity, unit cost, and any other attributes, such as essential physical characteristics. For support services, include a SOO, SOW, or PWS, as applicable.

(3) The exact location where the IT items and services are needed and points of contact with commercial and DSN telephone numbers.

(4) A copy of the market survey for each recommended source (reference FAR Part 10).

(5) A copy of the funding documentation.

(6) For sole source (e.g., only one source, specific make or model, or compatibility-limited), documentation to support a justification for other than full and open competition or limited source justification (reference FAR 6.3 and 8.405-6) and brand name situations (reference FAR 11.105).

(7) Copies of any additional information and support documentation necessary.

(b) The requiring activity shall—

(1) Prepare additional documentation or Business Case Analysis (BCA) as part of the contract file for an acquisition as needed.

(2) Submit acquisitions valued below $50,000 in accordance with local procedures, or as appropriate for the complexity of the requirement.

(3) Outline and compare the status quo method of business with three alternatives for acquisitions greater than or equal to $50,000 and less than $250,000.

(4) In addition to the requirements of (b)(2) above, provide a comparison of expected costs, benefits, impacts, and risks that would result from implementing alternative IT investments for acquisitions greater than or equal to $250,000 and less than $1,000,000.

(5) In addition to the requirements of (b)(2) and (b)(3) above, conduct a more in-depth analysis for acquisitions greater than or equal to $1,000,000 or having a significant impact on DoD logistics operations. The analysis shall include a study of the impact on DLA as a whole, as well as the quantitative and qualitative ramifications of the alternatives described within the investment; and consider the broad implications of the implementation of each alternative, including local and global implications, as well as immediate and future costs and savings.