DLAD PGI PART 39 – ACQUISITION OF INFORMATION TECHNOLOGY
PGI SUBPART 39.90 – PROCEDURES, APPROVALS, AND TOOLS
PGI 39.9003 IT Miscellaneous portals and tools.
The following provides links to IT laws and regulations (for FAR and DFARS links, see the beginning of DLAD Part 39), policy and procedures in alphabetical order. In addition, various IT tools are located here (If the reader has knowledge of additional information that should be added to this coverage or becomes aware of obsolete or revised coverage, they are encouraged to bring it to the attention of the DLAD webmaster):
Brand Name Specification acquisitions have special posting, solicitation, documentation and approval requirements (see FAR 5.102 and 11.105). Concerning Federal Supply Schedules(FSS), see FAR 8.405-1 and 8.405-6; for non-FSS see FAR 6.302-1, 13.106-1 or 13.501. See 39.9001 (i)(1) and 39.9002 (a)(6).
Information Technology Capability Request (ITCR) web form managed within the DLA IT Investment Portfolio. The ITCR captures a description of required capability, mission need, capability gaps, market research, funding information, security and compliance.
Defense Acquisition Guidebook – The purpose of the Guidebook is to provide members of the acquisition community and our industry partners with an interactive, on-line reference to policy and discretionary best practice. Consider the Guidebook a valuable resource as you design your program.
DLA Information Technology Solutions Document – IT Solutions are components that are identified and used as common building blocks across DLA to provide services that support the DLA mission. The objectives of these solutions are to: reduce acquisition costs, increase security, ensure interoperability, and promote information sharing. Common IT solutions represent solutions that have been widely accepted both within the market and within DLA. The purpose of presenting solutions as part of the DLA Information Technology Architecture is to simplify procurement decisions at all levels and to promote seamless interoperability both within DLA and between DLA and the greater Department of Defense community. While there will always be niche, specialized requirements, the common support solutions presented here should satisfy about 95 percent of user’s functional information technology requirements. Section 2 of this document identifies a set of minimum configurations for various types and classes of computing platforms used within the Agency. The remaining sections describe common support solutions in four broad categories: web environment solutions, corporate applications solutions, infrastructure solutions, and solutions related to specific DoD level systems. Solutions must respond to a myriad of complex functional requirements depending upon the specific organization environment and mission needs. Elements of one solution may also be part of other solutions. For example, Microsoft Outlook 2003 is part of the Productivity solution in the office environment. It is also the solution to workflow and group scheduling. See 39.9001 (i).
DLA One Book – Documents DLA policies, processes, and procedures on a single web site. DLAD 5025.30, a major component of the DLA Issuances System, is comprised of many process chapters. See 39.9001 (g) and 39.9002 (b).
DLA One Book Chapter on IT Requirements Analysis:
The purpose of this chapter is to document the steps involved in introducing Enterprise IT requirements and solutions into the Agency and performing a capabilities analysis prior to approval and implementation. It describes mandatory and discretionary steps, and management controls for analyzing proposed IT investments and requirements.
DoD 5000 Series – The DoD Directive 5000.1, Defense Acquisition System, the DoD Instruction 5000.2, Operation of the Defense Acquisition System and much more.
DoD Directives 8500.1 and 8500.2 – Information Assurance and Implementation.
DoD Enterprise Integration Toolkit – Contains a Roadmap for you to follow in the development of your component architecture and COTS acquisition and implementation projects. It includes more than 150 templates, checklists, and other tools to help your project be successful.
DoD Enterprise Software Initiative (ESI), SmartBuy, and Enterprise Resource Planning. See 39.9001(g).
The Enterprise Software Initiative (ESI) is a joint initiative designed to implement an enterprise software management process within the Department of Defense (DoD). All software purchases within DoD, regardless of the dollar amount or payment method, must be made via an Enterprise Software Agreement (ESA), if one exists covering the requirement (see DFARS 208.74 and DFARS PGI 208.7403), unless the acquiring activity obtains a waiver from ESI per DFARS 208.74 and DFARS PGI 208.7403(5)(iii). ESAs are agreements negotiated by the DoD ESI team with software vendors for the DoD and often for the GSA SmartBUY program as well. The Navy is the Executive Agent for ESI but each participating Component has a designated technical area of responsibility for contracting activities. By pooling software requirements and presenting a single negotiating position to leading software vendors, ESI provides pricing advantages not otherwise available to individual Services and Agencies. Over the course of seven years, ESI has resulted in over a billion dollars in savings attributable to cost avoidance.
SmartBUY is a federal government-wide software enterprise-licensing project developed by the General Services Administration (GSA), in coordination with the Office of Management and Budget. Its purpose is to consolidate the purchasing power of the federal government by focusing volume requirements to obtain optimal pricing and preferred terms and conditions for widely used commercial-off-the-shelf software. This effort was formally begun on June 5, 2003, with the release of the OMB SmartBUY letter to all agencies. GSA is the Executive Agent for SmartBUY, and is leading the interagency team in negotiating government-wide licenses for software.
Enterprise Resource Planning (ERP) is most commonly referenced in the context of commercially available software systems. ERP systems provide an integrated suite of information technology applications that support the operations of an enterprise; they are not limited to planning functions. The activities supported by ERP systems include all core functions of an enterprise, including financial management, human resources management, and operations. Increasingly, ERP vendors are offering “bolt-on” products that provide specialized functionality to augment the core, such as Advanced Planning and Scheduling and Customer Relationship Management.
Escrow Service Agreements – Triparty agreements in which a third party holds the source code of software in escrow and only releases it to either other party based on specific terms of the agreement. Here is a sample escrow service agreement.
General Services Administration (GSA) – Here is a link to the GSA, which provides many services and functions. Specifically, it provides for GSA contracts (including IT contracts) and schedules (Multiple Award Contracts and Federal Supply Schedules) See 39.201 (b) and 39.9001 (b).
Privacy Act - The Act requires that when an agency contracts for the design, development, or operation of a system of records on individuals on behalf of the agency to accomplish an agency function the agency must apply the requirements of the Act to the contractor and its employees working on the contract. Review FAR 24.1 and DFARS 224.1.