HC108419R0002.pdf

SEE ADDENDUM

(No Collect Calls)

HC108419R0002 21-Dec-2018

b. TELEPHONE NUMBER

618-418-6231

8. OFFER DUE DATE/LOCAL TIME

10:00 AM 22 Jan 2019

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

HC10849. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

MICHAEL F. MORRIS

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

0 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

DISA/DITCO-SCOTT-PL84

2300 EAST DRIVE

SCOTT AFB IL 62225

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE H98272 16. ADMINISTERED BY

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

DISA ENTERPRISE SERVICES

1 OVERCASH AVENUE,

LETTERKENNY ARMY DEPOT

CHAMBERSBURG PA 17201-4123

DEANNA BAER

TEL: 717-267-9930 FAX:

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$38,500,000

NAICS:

511210

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT 41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

HC108419R0002

Section SF 1449 - CONTINUATION SHEET

EXHIBIT A PRODUCT LIST

Exhibit A Product List

Exhibit A - Product List (for Vendor Unit

EXHIBIT B DISA INVENTORY

Exhibit B DISA Inventory

Exhibit B 18 Dec 2018 DISA Inventory.

EXHIBIT C TECHNICAL STANDARDS

Exhibit C - Technical Standards CA Software Licensing and Maintenance

Contract Number:

Task Order Number:

1. Contracting Officer Representative (COR).

a. Primary.

Name: Deanna Baer Organization: DISA, Operations Center Logistics, OCL24 Address: 1 Overcash Ave, Bldg. 12 Chambersburg, PA

17201-4122 Phone Number: 717-267-9930 or DSN 570-9930 Fax Number: 717-267-8332 E-Mail Address: Deanna.J.Baer.civ@mail.mil

DODAAC: H98272

b. Alternate.

Name: Mona Anderson Organization: DISA, Operations Center Logistics, OCL24 Address: 1 Overcash Ave, Bldg. 12 Chambersburg, PA

17201-4122 Phone Number: 717-267-9410 or DSN 570-9410 Fax Number: 717-267-8332 E-Mail Address: Mona.L.Anderson.civ@mail.mil

DODAAC: H98272

2. Title. CA, Inc. (CA) Software Licensing and Maintenance Support

3. Background. Defense Information Systems Agency (DISA) is a Combat Support Agency comprised of 16,000 people – military, federal civilian, and our contractor partners. We connect the enterprise – the forces, users, and partners globally, from user to user – where information is produced and consumed at speeds and in quantities never before imagined. Together with our partners, we provide the network, computing infrastructure, and enterprise services to support information sharing and decision-making no matter where the information is located or sourced.

We facilitate use of real time intelligence, surveillance, and reconnaissance information to enable information exchange between the producer and the shooter. We work with our mission partners to provide technology and seamless exchange of information so that anyone who can connect to the network can provide and consume data and services anywhere on the network globally.

DISA's Operations Center (OC)/Services Directorate (SE) provides world-class processing capability, systems management, communications and storage in support of Department of Defense (DoD) services, agencies, and combatant commands located in secure facilities strategically located throughout the world; OC supports more than three million users of more than 2,800 applications. OC has become DoD's number one provider of personnel, payroll, logistics, accounting, and medical records processing.

OC continues to transform its processing environments and operations, which have streamlined DISA to become a more efficient computing services organization for the DoD. The streamlining approach was predicated upon several factors including revising processes and deploying best practices to improve the accountability and configuration of Information Technology (IT) assets while streamlining to fit within DoD reduced IT budgets.

In order to achieve the DISA and OC/SE mission, the Software Consolidated Licensing and Maintenance effort focuses on the need for cost-effective consolidated licensing and maintenance support for proprietary Commercial Off-the-Shelf (COTS) software products currently operating in the DISA mainframe and distributed environments.

OC/SE continues to support mainframe processing environments while aggressively validating requirements and reviewing current/potential contracts to determine who provides “the best product at the best price” with terms aligned to support DISA and DoD workloads. Mutually favorable contracts with contractors, who work with DISA to understand and address the unique challenges of the government and the DoD, assists DISA in reaching critical goals and objectives, such as:

• Establishing standardized DoD licensing models that provide flexibility and scalability

• Improving the management and control of costs and IT assets

• Improving the recapture of software investments

• Improving the usage of IT assets in coordination with the advances in hardware and processing technologies / methodologies

• Supporting DISA’s Assured Computing Environment (ACE) / Disaster Recovery operations

• Supporting DISA’s Information Technology Service Management (ITSM) and the Release Management Factory (RMF) centralized distribution processes

4. Objectives. The objective of this effort is to provide software licensing and maintenance to meet current and future mainframe workloads, security, and modernization requirements, while ensuring DISA customers receive uninterrupted, continuous access to their applications and data.

OC/SE requirements for Software Consolidated Licensing and Maintenance include:

• DISA software licensing use

• Software entitlements

• Software maintenance support

• Contract administration

• Information Technology Asset Management (ITAM)

• Software Investment Management (SIM)

• Product media requirements and technical documentation

The requirements stated within the contract provide the governance over the software to be procured or currently installed and supporting applications transmitted to or processed by DISA.

Consolidating and managing software licenses and maintenance under one contract per software contractor ensures DISA, and the DoD, avoids duplication of IT assets and functionality, avoids acquisition of excess software capacity, promotes centralized visibility of software assets, and improves inventory configuration management and control. Successful and effective contract management, ITAM, and SIM, assists in accomplishing these objectives for DISA and the DoD.

DISA leverages these principles to develop agreements beneficial to all parties; providing assured, uninterrupted computing services to the DoD and the warfighter, improving DoD ITAM, and establishes specific terms that allow DISA to maintain compliant and accurate IT asset configurations.

The OC/SE current platform consists of 20 mainframes (including 4 mainframes for ACE, numerous servers, and over 3000 network nodes located at numerous Enterprise Computing Centers. Hosted within these computing centers are thousands of software products that support hundreds of mission partner applications. The goal of this procurement provides the ability to acquire additional units, capacity and/or additional products to satisfy business requirements and standardization initiatives, allows for processing environment capacity increases and decreases, eliminates or decreases contractor-imposed inventory "floor" levels and growth factors, eliminates cost escalations, and affords DISA recapture and transfer mechanisms for managing software investments with the intent not to procure or maintain "shelf-ware".

5. Scope. The initial scope (Base year of the contract) addresses the baseline software inventory of CA products as identified in Exhibits A, CA Product List, and B, DISA Inventory. The scope for the option year periods may eventually include the procurement of additional licenses due to capacity changes, transfer of licenses due to data center consolidation, increases in software support, and the potential for consolidations of other CA software licensed within DISA’s computing services.

6. Technical Requirements.

6.1. Requirement 1 – Provide Software Maintenance Support

The contractor shall provide software maintenance support. All terms shall be in accordance with the requirements of the contract and associated addenda. The software maintenance costs and associated pricing models and calculations shall be clearly identified and will include:

o DoD software licensing o Software entitlements o Non-production software usage o Contract administration o ITAM o SIM o Product media requirements and technical documentation

6.2. Requirement 2 – Provide the Ability to Purchase Additional Licenses/Units, Capacity and/or Products, Provide the Ability For DoD Data Center Consolidation; and Provide the Ability to Incorporate Other DISA Contracts as Required

The contractor shall provide DISA the ability to purchase additional licenses/units/capacity.

The contractor shall also provide the ability to transfer in licenses from other DoD entities as a result of data center consolidation, as well as providing the ability to consolidate other DISA contracts. To facilitate this, the contractor shall provide an Addendum (Product List) reflecting their commercially available/generally available portfolio of products.

6.3. Requirement 3 – Provide the Ability to Recapture and Leverage Software Investments

The contractor shall propose investment recapture values (monetary value credits) or a calculation method with pricing for determining the investment value afforded to DISA for licensed software products and/or capacity levels that are not deployed and will not be redeployed, products lacking or absent of support for which DISA would like to remove from inventory, and for licensed software products purchased by DISA in good faith, but never deployed. The current list of “shelved” software products / licensed capacities in DISA’s inventory that requires the contractor to propose recapture values against at contract award are identified in Exhibit B, Excess tab. The recapture value of the products may be used by DISA at time of contract award to off-set contract costs and/or increase inventory requirements.

Contractor products designated as excess software investments will be identified by DISA prior to each option year renewal and sent to the contractor during the inventory reconciliation process. The investment recapture value(s) will be determined by the calculation method agreed upon between DISA and the contractor and incorporated into the contract. At DISA’s discretion, DISA shall have the right to apply the investment recapture credit at any time throughout the life of the contract to satisfy current costs of the contract and/or use the credit(s) to satisfy additional business requirements, including the purchase of additional products from CA commercially available/generally available portfolio of products. See Exhibit D, paragraph 2.4.4.2 for additional information.

7. Technical Standards.

ITEM OBJECTIVE Exhibit & Para

THRESHOLD

Provide Software Maintenance Support

6.1

Software Maintenance Support Exhibit D

– para 3.0

1. Software Keys - Routine Exhibit D

– para 2.2

100%, contractor shall provide software keys after initial request

2. Software Keys – Emergency Request

Exhibit D

– para 2.2.4

100%, contractor shall provide software keys after initial request

3. New software versions, releases, fixes, upgrades, options

Exhibit D

– para 3.2

100%, contractor shall provide new software versions, release, fixes, upgrades, options immediately upon availability

4. Notice of End of Life/End of Service (EOL/EOS)

Exhibit D

– para 3.3

100%, contractor shall provide 12 months notice of any product EOL/EOS

5. Escalation of errors Exhibit D

– para 3.7.1.3

100% for Severity Level 1 errors

6. Software Errors – Severity 1 Exhibit D

– para 3.7.2.1

100%, 24x7x365, 1 hour response, resolution immediately following error;

for current and previous release of software product

7. Software Errors – Severity 2 Exhibit D

– para 3.7.2.2

75%, 8X5 (Monday-Friday), 2 business hours response , resolution following error;

for current and previous release of software product

8. Software Errors – Severity 3 Exhibit D

– para 3.7.2.3

50%, 8x5 (Monday-Friday), 4 business hours response, resolution following error

9. Software Errors – Severity 4 Exhibit D

– para 3.7.2.4

25%, 8x5(Monday-Friday), 1 business day response, resolution following error

10. Asset Documentation Exhibit D

– para 4.1

95%, contractor shall provide up-to-date software documentation, product feature list, individual units in bundles

8. Remedies.

In the event that CA ceases providing support for any computer software, then contractor shall provide one of two possible solutions:

o A replacement CA computer software product (the "Replacement Software") which is

Generally Available to CA customers and which provides similar, equal or greater substantially equivalent features, functionality and pricing as the Unsupported Computer Program:

1. If DISA is unable to migrate to another product by the contractor identified EOL/EOS date, then the contractor will agree to temporarily extend support for EOS products to allow DISA additional time to upgrade to the supported version.

2. On a case-by-case basis, CA may extend support for EOS product by 1 year, if extended support is available for the EOS product, to allow DISA additional time to upgrade to the supported version.

9. DISA Locations. The CA software for this effort shall be able to perform on all processing environments where DISA maintains computing services responsibilities. The requirements identified do not require physical access by the contractor into DISA facilities or systems. When licensed, CA products may be used at any other DISA or DISA approved location worldwide where DISA may acquire an operational responsibility. DISA OC Enterprise Computing Centers include, but may not be limited to the following:

Chambersburg, Pennsylvania Columbus, Ohio Denver, Colorado Fort Meade, Maryland Jacksonville, Florida Mechanicsburg, Pennsylvania Montgomery, Alabama Ogden, Utah Oklahoma City, Oklahoma Pensacola, Florida San Antonio, Texas St. Louis, Missouri Warner Robins, Georgia Manama, Bahrain Pearl Harbor, Hawaii - ESC - PAC Patch Barracks, Vaihingen, Germany

10. Period of Performance (PoP). The PoP includes a 1-year base period beginning on March 31, 2019; and four 1-year option periods ending on March 30, 2024.

11. Delivery Schedule.

Require ment #

Requirement Title

CDRL

DID#

Due Date

Details of Requirement

Distrib ution

Frequency and Remarks

6.1, Task 1

Provide Software Maintenance Support

N/A Upon contract award and throughout the life of the contract

Contractor-provided software maintenance support for the Computer software products identified within the contract

N/A At contract award and renewed at DISA’s discretion during option years of the contract.

Terms shall be in accordance with the requirements of the contract

6.2, Task 2

Provide the Ability to Purchase Additional Licenses/Uni ts, Capacity, and/or Products as Required, to include DoD Data Center Consolidatio n and Incorporatio n of Other

DISA

Requirement s

N/A Exercised at DISA’s discretion throughout the life of the contract

Contractor shall provide DISA the ability to purchase additional licenses/units, additional capacity, and/or additional products from CA commercially available/generally available portfolio of products, as well as license transfer and resulting maintenance

N/A Exercised as an option at DISA’s discretion throughout the life of the contract as business requirements dictate.

Terms shall be in accordance with the requirements of the contract.

6.3, Task 3

Provide the Ability to Recapture and Leverage Software Investments

N/A Exercised at DISA’s discretion throughout the life of the contract

Provide DISA with investment recapture values (monetary value credits) and transfer methods as identified in section 6.3 (above) for contractor licensed software products and/or capacity levels not deployed

N/A At contract award and exercised as an option at DISA’s discretion throughout the life of the contract

12. Security. The contractor shall employ appropriate administrative, technical, and physical safeguards to protect any and all Government data, to ensure the confidentiality, integrity, and availability of government data. At a minimum, this shall include provisions for security as listed in the sections that follow:

12.1. Software Security. The most current version(s) of the applicable security guides, checklists, memos, and references shall be in accordance with the DISA Security Technical Implementation Guide (STIG) for the references listed below:

• OS/390 MVS Logical Partition STIG

• OS/390&z/OS STIG V6

• OS/390&x/OS STIG V6

• UNIX STIG

• UNIX Release Memo

• Database STIG

• Database Release Memo

• NSA Windows XP STIG

• Windows 2000/XP/2003 Addendum

• Windows 2000/XP/2003 Addendum Release Memo

12.2. Information Assurance. Shall be in accordance with the most recent DoD Directive 8500-1, “Information Assurance”.

13. Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI).

The contract is for DoD software licensing and software maintenance support and requires no GFE to be furnished to the contractor. Any GFI supplied to the contractor or acquired during contract renewal/negotiations or throughout the PoP will be strictly for establishing and executing the contract.

14. Other Pertinent Information or Special Considerations. The contractor’s proposal shall address the additional requirements in Exhibit D to satisfy the objectives, scope and details of the technical requirements.

a. Identification of Possible Follow-on Work. During the PoP, including all options, the scope allows for the procurement of additional licenses, software maintenance support, purchases of additional CA products/maintenance to accommodate capacity changes and incoming workload within DISA's computing centers and other locations for performance.

b. Identification of Potential Conflicts of Interest (COI). None

c. Identification of Non-Disclosure Requirements. The information shared with the contractor throughout the negotiations/renewal and execution of the contract may include access to sensitive or proprietary business, technical, financial, and/or source selection information belonging to the Government or other contractors. Proprietary information includes, but is not limited to, cost/pricing data, Government spend plan data, contractor technical proposal data, independent government cost estimates, negotiation strategies and contractor data presented in negotiations, contracting plans and statements of work.

Unauthorized disclosure, use or negligent handling of the information could cause irreparable injury to the owner of the information. The contractor’s personnel negotiating and servicing this contract shall sign a Non-Disclosure Agreement (NDA) understanding the impact and consequences for mishandling or disclosing sensitive or proprietary information belonging to the Government or other contractors.

d. Product Identification, Packaging, Packing and Shipping Instructions. All Licensed software shall be delivered via electronic download where available and conducive to the DISA mission. The media format of the releases and fixes/patches shall be the choice of DISA chosen from the commercially available formats offered by the contractor. For physical delivery, the contractor shall submit a schedule of supplies and services with clear identification of product names and configurations (e.g., version changes, bundling/unbundling of products, ratings, Tier classifications, etc.) with their proposal to be incorporated into the contract. Sixty (60) days prior to each option year renewal, the contractor shall provide to the designated DISA Contracting Officer’s Representative (COR) identified at contract award, an updated schedule of supplies and services with similar product identification.

Contractor product shipments shall include the following information:

• Shipping List – Contract Number, Product Number, contractor Point of Contact (POC) with phone and Fax numbers, along with a name and telephone number for the POC at the DISA central distribution site

• Software Labels – contractor, Product Name, Volume Serial Number, Creation Date, Release Number, Version Number.

Product Documentation and media shall be clearly marked and delivered in accordance with the terms of the contract. DISA’s centralized point of contact for Documentation, product media, and product keys / password requests are:

MAINFRAME & DISTRIBUTED

SOFTWARE:

DISA OPS DECC Mechanicsburg Attn: Ms. Lori Reedy 5450 Carlisle Pike Bldg 309 South Mechanicsburg, PA 17055-0975 Phone: 717-918-6276 E-mail: Lori.A.Reedy.civ@mail.mil

e. Inspection and Acceptance Criteria. Upon delivery, DISA will validate all information and verify compliance with the DoD Security and Technical Implementation Guides (STIGs). If any product is determined to be non-compliant, DISA will return the product to the contractor at the contractor’s expense. The products are expected to function as intended and in accordance with the technical and functional specifications published by the contractor.

15. Section 508 Accessibility Standards. Section 508 Accessibility Standards. The following Section 508 Accessibility Standard(s) (Technical Standards and Functional Performance Criteria) are applicable (if box is checked) to this acquisition. The Contractor shall comply with Section 508 Access Standards (Technical) 1194.21, and Section 508 Functional Performance Criteria, 1194.31, of the Rehabilitation Act of 1973; as provided in the Voluntary Product Accessibility Templates (VPATs) for the software licensed hereunder provided by Contractor to Customer. Such VPATs shall be deemed part of the software Documentation.

Contractor may not have VPATS for all software products licensed hereunder but will provide copies of VPATs as they become available. A full list of products that do not conform to Section 508 or do not have an associated VPAT will be provided to the Contracting Officer before contract award.

Technical Standards

1194.21 - Software Applications and Operating Systems

1194.22 - Web Based Intranet and Internet Information and Applications

1194.23 - Telecommunications Products

1194.24 - Video and Multimedia Products

1194.25 - Self-Contained, Closed Products

1194.26 - Desktop and Portable Computers

1194.41 - Information, Documentation and Support

The Technical Standards above facilitate the assurance that the maximum technical standards are provided to the offerors. Functional Performance Criteria is the minimally acceptable standards to ensure Section 508 compliance. This block is checked to ensure that the minimally acceptable electronic and information technology (E&IT) products are proposed.

Functional Performance Criteria

1194.31 - Functional Performance Criteria

EXHIBIT D DISA TERMS

Exhibit D Defense Information Systems Agency (DISA) Terms

As of December 6, 2018

1.0. SCOPE

1.1. This addendum, in association with the accompanying Technical Requirement states DISA’s requirements for:

• DISA software licensing

• Software entitlements

• Software maintenance support

• Non-production software usage

• Contract administration

• Information Technology Asset Management (ITAM)

• Software Investment Management (SIM)

• Product media requirements and technical documentation

1.2. In accordance with the terms of this contract, Contractor authorizes DISA operation of the CA Technologies (CA) software products on all DISA and DISA/contractor-supported platforms. Integration of these products into DISA’s infrastructure will assist supporting systems, networks and applications where DISA has the responsibility for computing services.

1.3. CA’s software products identified with the new contract, but licensed to other Department of Defense (DoD) and Federal agencies, may be transferred to DISA and incorporated under the contract to process workloads or mission assignments realigned to DISA at no cost to the government. CA software products procured through other methods outside of the contract (e.g., other contracts or contracting vehicles, Blanket Purchase Agreements (BPAs), or other government purchasing methods) and then added to the new contract after contract award may obtain software maintenance in accordance with the terms of this contract, at no cost to the government.

Prior to such license transfer CA will approve the transfer, resolving any license conversion, outstanding obligations, and potential transfer fees with the transferring customer. DISA will require a Letter of Approval from CA prior to accepting accountability for the transferred licenses showing the future date of transfer. At that point, DISA will respond to CA noting acceptance of the transferred licenses, add the transferred license to the contract inventory, and will manage as DISA inventory, under the terms of this contract. This process is intended to allow CA to directly deal with the accountable party to ensure a clear line of demarcation prior to the transfer.

2.0. DoD SOFTWARE LICENSING AND MAINTENANCE REQUIREMENTS

DISA’s current software licensing is on a “perpetual” basis. Unless otherwise designated, current licenses covered under the contract are perpetual and may be used without Contractor provided maintenance.

2.1. The Contractor shall ensure that the software products and any product enhancements associated with the products in this contract will support commercially available operating systems, hardware, and processing environment technologies including, but not limited to, 64-bit architecture, Sysplex environments, International Business Machines Corporation (IBM) System z hardware and software Operating System (OS), z Virtual Machine (VM), X-86 (Windows Server, Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Solaris, VMware); Itanium (Hewlett Packard-Unix, Hewlett Packard Virtual Server Environment (HP-UX, HP VSE)); Scalable Processor Architecture (SPARC), Solaris, Solaris 10 zones and Ldoms; IBM System p (Advanced Interactive eXecutive (AIX)) Logical Partitions (LPARs); and HP-UX, Sun Solaris, IBM AIX, RedHat Linux, SUSE Linux, and Windows Server Operating Systems and their associated follow-on operating systems.

2.1.1. The Contractor shall ensure or shall provide a good faith effort towards ensuring that all components are Internet Protocol Version 6 (IPv6) capable. This is defined as a system or product capable of receiving, processing and forwarding IPv6 packets and/or interfacing with other systems and protocols in a manner similar to that of IPv4.

Criteria to be considered IPv6 capable are: conformant with the IPv6 standards profile contained in the DOD Information Technology (IT) Standard Registry (DISR);

maintaining interoperability in heterogeneous environments and with IPv4;

commitment to upgrade s the IPv6 standard evolves; and availability of IPv6 technical support.

2.1.2. The Contractor shall ensure or shall provide a good faith effort towards ensuring that any components of this contract which use a hash function shall provide capabilities to do hashing using the Secure Hash Algorithm (SHA)-256 function as defined in Federal Information Processing Standards (FIPS) publication series 180 and published by the National Institute of Standards and Technology. This includes but is not limited to all cryptographic functions used in securing data, software integrity, digital signatures, secure communications, password protections and message authentication which requires a hashing function.

2.2. Software Keys

2.2.1. The Contractor shall provide a mainframe master key for each licensed product, which shall expire upon expiration of the full contract Term. Keys shall not be specific to physical location or hardware model/serial number.

2.2.2. If a master key is not available, or if new software is obtained, the Contractor shall provide a 24/7 vendor key support contact (primary and alternate).

2.2.3. After a software key request is submitted, the Contractor shall make a good faith effort to deliver the key not later than 24 hours after the initial request.

2.2.4. In the case of an emergency key request, the Contractor shall make a good faith effort to deliver the key not later than 2 hours after the initial request.

2.2.5. The Contractor shall send all keys to a central email box at:

disa.meade.se.list.lob-mainframe-license-keys@mail.mil mailto:disa.meade.se.list.lob-mainframe-license-keys@mail.mil

2.2.6. Currently, due to transformation, more than one account may be active for DISA software maintenance. To eliminate confusion and increase efficiency, CA shall standardize all DISA accounts to identify all products as being licensed by “DISA.”

2.3. “Floor” Levels. Due to decreasing IT budgets, increasing audits of funded requirements, and DoD policy, DISA requests the Contractor not impose minimum inventory levels of capacity / units (“floor” levels) to be maintained by DISA and shall not propose defined growth levels or growth percentages of inventory that must be maintained by DISA.

2.4. Calculating Software Usage. The Contractor shall provide a licensing and maintenance model that clearly states the units of measurement for software usage for both Mainframe and Distributed environments (where applicable) that can be standardized for the life of the contract. The contract defines how inventory units can be increased, decreased, transferred and/or aggregated across the Enterprise.

2.4.1. Mainframe. Mainframe-based software licensing and maintenance support proposed by the Contractor shall address the following:

2.4.2. Central Processing Unit (CPU) Rating. DISA and the Contractor shall recognize the Large System Performance Reference (LSPR) CPU ratings published by IBM as the agreed upon CPU ratings for determining the full processing capacity of DISA’s mainframes. Use of ratings other than IBM’s LSPR must be mutually agreed upon by DISA and the Contractor prior to contract award. In the event IBM would cease to publish CPU ratings or should a unit of measurement other than those published by IBM be selected, DISA and the Contractor shall mutually agree to an alternate source from which to obtain CPU ratings.

2.4.3. High 8 Hour Average LPAR Millions of Instructions Per Second (MIPS) Capacity. Capacity shall be expressed as High 8 Hour Average LPAR MIPS rounded to the nearest whole number. The High 8 Hour Average LPAR MIPS is calculated by averaging the High 8 Hour Average LPAR MIPS for each month of the 6 month period February 01 – July 31 and August 01 – January 31. Software license and maintenance costs are measured as High 8 Hour Average LPAR MIPS, which may be less than the total CPU capacity. Throughout the life of the contract, when acquiring capacity, DISA shall retain software usage rights up to the capacity threshold of all MIPS previously acquired. Where applicable, CPU-based or LPAR-based capacity pricing models proposed shall acknowledge a one-to-one conversion for the amount of MIPS in DISA’s baseline inventory (e.g., 25 CPU-based MIPS is equal to 25 High 8 Hour Average LPAR-based MIPS).

2.4.3.1. High 8 Hour Average LPAR MIPS are measured in the following manner.

2.4.3.1.1. There is no method to directly measure the number of instructions executed in an LPAR, instead IBM LSPR MIPS tables are used to provide average MIPS ratings for each mainframe in the inventory.

2.4.3.1.2. For z/OS LPARs, Resource Measurement Facility (RMF) data is used to calculate the average percent utilization of each LPAR for each hour of the month (weekday, non-holiday only). These percent utilization values are multiplied by the IBM LSPR MIPS rating to derive hourly MIPS values.

2.4.3.1.3. A similar method is used for the VM LPARs, but the source of data is VM Monitor instead of RMF.

2.4.3.1.4. Monthly averages are derived for each block of 8-hour windows.

There are 24 of these windows; specifically, hours 0-7, hours 1-8, hours 2- 9, etc.; ending with hours 23-6. The highest of these 24 averages is the "High 8 Hour Average MIPS" for the LPAR."

2.4.3.1.5. Following is an example using LPAR MSI (on Mechanicsburg's HOST06) for the month of August 2017: Host06 is an IBM zBC12-H13 2828-L06, with six processors and an IBM LSPR MIPS rating of 1006.

Analysis of MSI's CPU utilization data for August 2017 indicates that the High 8 Hour utilization was for hours 6 through 13 inclusive (M-F, non-holiday only). In this defined period, there were 184 hours (23 days times 8 hours per day) and during that time, MSI used 151 hours and 10 minutes of CPU time (151.167 hours).

2.4.3.1.6. For the average percent busy calculation, the total CPU time utilized by MSI for the month of August during the High 8 Hour window is divided by the total amount of time in the month during that window times the number of processors on the machine:

AVG_PCT_BUSY_IN_HIGH8_WINDOW =

CPU_TIME_IN_HIGH8_WINDOW / (TIME_IN_HIGH8_WINDOW X

NUMBER_OF_PROCESSORS). Average percent busy is then multiplied by the IBM LSPR MIPS for the machine on which MSI runs:

AVG_MIPS_IN_HIGH8_WINDOW =

AVG_PCT_BUSY_IN_HIGH8_WINDOW X IBM

LSPR_MIPS_RATING.

2.4.3.1.7. For the above example, the LPAR's High 8 Hour Average LPAR MIPS value would be (151.167 / (184 X 4) X 1006) = 137.75.

2.4.4. Capacity Increases. DISA shall have the right to increase the quantity of MIPS per software product, for MIPS based products set forth in Exhibits A and B (CA Product List and DISA Inventory), throughout the life of the contract as business requirements and funding levels dictate. Software product increases shall be acquired in actual High 8 Hour Average LPAR MIPS. The Contractor shall provide clearly stated pricing in the schedule of supplies for capacity increases.

2.4.4.1. Increases in utilization may require payment of additional fees, if excess licenses are not available.

2.4.4.2. Use of Excess. Excess MIPS licenses will carry forward from the current CA contract and placed in DISA’s excess perpetual license inventory and will remain perpetual (see Exhibit B, DISA Inventory, Excess tab).

Products removed from inventory will be placed in the excess perpetual license inventory. DISA’s excess perpetual licenses remain in inventory at no charge.

If DISA pulls these perpetual licenses from inventory, these licenses will begin to accrue maintenance charges at the next semi-annual reconciliation date.

DISA can pull product MIPS from this perpetual license inventory in lieu of paying license fees for utilization beyond the MIPS baseline for the like product. For example, if DISA increases its licensed capacity for CA-ACF2, DISA may use CA-ACF2 excess licenses to offset any license fees due to CA for the increase in capacity. Using this methodology DISA may use like excess licenses/units/additional capacity where the excess of the same is available.

2.4.4.3. Use of Growth MIPS. 1,716 Growth MIPS are being carried in from the previous contract. The excess 1,716 growth MIPS are not product specific and therefore may be used to offset license fees for increased utilization on any CPU upgrade until depleted. DISA will be responsible for payment of all applicable maintenance fees for the 1,716 MIPS as they are deployed.

The excess perpetual licenses have MIPS values associated with the licenses.

This inventory of product specific MIPS licenses is separate from the 1,716 excess growth MIPS inventory. Once the 1,716 MIPS are deployed in lieu of license fees for CPU upgrades (current contract use), these MIPS will become assigned to the respective products.

2.4.4.4. LPAR Additions. When an LPAR is added during the semi-annual period, average LPAR Capacity calculation will continue to be based upon the past 6 months, and payment will begin with the following semi-annual true-up.

For example, LPAR ‘X’ is added in month 4 of the semi-annual period. The High 8 Hour Average LPAR Capacity is 22 MIPS for month 4, 23 MIPS for month 5, and 21 MIPS for month 6. The 6-month average for LPAR ‘X’ is 11 MIPS [(22+23+21)/6 = 11]. Eleven MIPS maintenance of each CA product that is licensed for LPAR ‘X’ will be paid during the following semi-annual period.

2.4.5. Capacity Decreases. DISA shall have the right to decrease the quantity of MIPS per software product as reductions in business requirements and funding levels dictate. Software product decreases shall be deleted in actual High 8 Hour Average LPAR MIPS. MIPS capacity removed from production and placed into DISA’s excess / reserve inventory for redeployment later, referred to as a temporary decrease, shall not incur maintenance charges. MIPS capacity permanently removed from inventory, referred to as a permanent decrease, and not as a result of a functional replacement initiative, shall be assessed a monetary value and/or credit value (Investment Recapture) that can be used by DISA to offset contract costs or future requirements with the Contractor. As part of the proposed offerings, the Contractor shall provide a clear calculation method with associated pricing to address the investment recapture of permanent inventory decreases. Investment recapture and management of these software capacity decreases are necessary in preserving the defense dollars used for software investments** within the DoD.

**NOTE: See Section 5.0 for terms regarding DISA’s requirements for SIM.

2.4.5.1. LPAR Deletions. When an LPAR is deleted/decommissioned during the semi-annual period, the High 8 Hour Average LPAR Capacity calculation will continue to be based upon the past 6 months, and payment will continue until such time that the 6-month semi-annual period shows no activity for that LPAR.

For example, LPAR ‘X’ is decommissioned during month 3 of the semi-annual period. The High 8 Hour Average LPAR Capacity is 1- MIPS for month 1, 9 MIPS for month 2, and 5 MIPS for month 3. The 6-month average for LPAR ‘X’ is 4 MIPS [(10+9+5)/6 = 4]. Four MIPS maintenance of each CA product that was licensed for LPAR ‘X’ will be paid during the following semi-annual period.

2.4.6. Specialty Engines. Specialty engines, such as IBM System z Integrated Information Processors (zIIPs), System z Application Assist Processors (zAAPs), and Integrated Facility for Linux (IFLs) shall not be included in the chargeable usage or rated capacity of any mainframe processor to which they are attached unless specifically licensed for use in these engines. Production software installed on an IFL will be licensed specifically to the specialty engines as set forth in Addendum #.

2.4.6.1. The computing power (expressed in millions of instructions per second as published by IBM and accepted as industry standard) of the processors (or CPUs) of the mainframe computers that are designated as General Purpose Workload Engines (“GPWE”) located at the DISA sites. Notwithstanding the foregoing, MIPS Capacity will not include the MIPS of any GPWE that is installed but has not been activated by either the manufacturer or DISA and is not available for use to the Computer Software. Furthermore, processors or CPUs on any such mainframe computers (“Processor Engines”) that have been activated by either the manufacturer or DISA which is designated as an IFL, Internal Coupling Facility (ICF), P”) or zAAP shall be excluded from the MIPS

Capacity, provided that, such Processor Engine is not classified as a GPWE, and such Processor Engine does not execute the Z/OS (or successor) operating system in a GPWE mode. DISA agrees that any CA software installed and being used for its intended purpose on a specialty engine will be properly licensed and maintained, in accordance with pricing identified on Exhibit A, CA Product List.

2.4.6.2. Virtualization on IFLs. For non-mainframe products, where the Computer Software is used on multiple machines (physical and virtual ) each such use of that Computer Software shall be counted for the purposes of determining the Licensed Capacity for that Computer Software. A “virtual” PC and server environment is created where Virtual Machine Technology (which applies to both client and server hardware) is used to enable multiple instances of an operating system(s) to run on a single computer simultaneously

2.4.8. Distributed. Distributed-based (Server / Mid-Tier) software licensing and maintenance support proposed by the Contractor shall address the following:

2.4.8.1. Industry Standard. Software licensing and maintenance support units (capacity) shall be expressed in measurements recognized as industry standards (e.g., per Managed Server, per Site, per Tier, per CPU, per User) and rounded to the nearest whole number. Units shall be clearly defined and easily discernible by administrators of the contract.

2.4.8.2. Capacity Increases. DISA shall have the right to increase the quantity of units per software product throughout the life of the contract as business requirements dictate. The Contractor shall provide clearly stated pricing in the schedule of supplies for capacity increases. Pricing for capacity increases on distributed licenses is set forth in Exhibit A, CA Product List. Reference paragraph 2.4.4.2 regarding use of Excess for capacity Increases.

2.4.8.3. Capacity Decreases. DISA shall have the right to decrease the quantity of units (license/server/user/instance) per software product as reductions in business requirements dictate. Software units (license/server/user/instance) removed from production and placed into DISA’s excess / reserve inventory for redeployment later, referred to as a temporary decrease, shall not incur maintenance charges. Software units permanently removed from inventory, referred to as a permanent decrease, and not as a result of a functional replacement initiative, shall be assessed a monetary value and/or credit value (Investment Recapture) that can be used by DISA to offset contract costs or future requirements with the Contractor. As part of the proposed offerings, the Contractor shall provide a clear calculation method with associated pricing to address the investment recapture of permanent inventory decreases. Investment recapture and management of these software capacity decreases are necessary in preserving the defense dollars used for software investments** within the DoD.

Redeployed software shall not incur maintenance reinstatement fees; however the maintenance shall be calculated as part of the semi-annual utilization calculation.

2.4.8.4. Partitioning.

2.4.8.4.1. Software shall be licensed in a hard or soft (virtualized) partitioned operating environment based on the processor allocated to that environment. The number of processors are allocated within partitioned environments by a system administrator.

2.4.8.4.2. DISA can partition through either hard or soft partitioning.

DISA shall only pay for licenses for the partitions on which software programs are running. Licensing must be in whole numbers, and not a partial or fractional share. For example, Customer cannot license 3.69 of a 4-processor server. DISA shall never pay for more licenses than the maximum number of processors on the server.

2.4.8.4.3. Hard Partitioning. Hard Partition means to partition the server by physically separating the processors of a single server into distinct smaller servers, each of which acts as a physically independent, self-contained server, typically with its own dedicated CPUs, operating system, separate boot area, memory, input/output subsystem, and network resources.

2.4.8.4.4. DISA shall pay for licenses based upon the number of processors running products on the hard partition

2.4.8.4.5. Soft Partitioning (Virtualization). Soft Partition means to partition the operating system using system resource managers that limit the number of CPUs running programs. Soft Partitioning creates areas within the same operating system where CPU resources are specifically allocated to respective applications.

2.4.8.4.6. DISA shall pay for licenses based upon the number of processors running products on the soft partition.

2.4.8.4.7. CA shall provide full support for all products included in this agreement regardless of the partitioning/configuration.

2.5. Non-Production Software Usage. DISA shall have the right to use the licensed software to perform non-production business operations. These non-production business operations are critical to the success of computing services for the DoD and include, but are not limited to, the following areas:

• Quality Assurance / Quality Acceptance (QA) testing

• Release Management Factory (RMF) testing and distribution

• Disaster Recovery / Continuity of Operations (COOP) / ACE testing

2.5.1. Software versions, releases, and maintenance fixes will be subjected to a centralized installation compatibility assurance checkout on a test domain at a DISA managed / maintained facility. This test domain may or may not be on the same CPU on which the software is licensed. Software subjected to installation compatibility checkout will not be made available for production, development use, or execution on other than the test domain.

2.5.2. Software Copying and Distribution. DISA shall have the right to copy and distribute licensed copies of the CA software and documentation by means of a distribution process governed by an Enterprise Configuration Management process.

These managed processes assist in the adherence to software licensing compliance and usage throughout the Enterprise. This approach saves time and resources normally expended to install software from contractor-provided media (tapes, discs, or cartridges), and provides the Contractor with a more efficient way to accommodate DISA’s centralized software distribution requirement. DISA shall be entitled to all commercially available formats of the CA product documentation. DISA will reproduce all legends, logos, and proprietary notices and ensure that copy quality is maintained.

2.5.2.1. Centralized Distribution (Electronic). DISA shall have the right to distribute licensed products to systems where DISA maintains computing services responsibilities. DISA’s electronic distribution method is governed by a configuration management process supported by DISA Systems Support Branch (SEL14), RMF. For additional information on the RMF and process, see Centralized Software Distribution via the Release Management Factory (RMF) in section 8.0, Definitions.

2.5.2.2. Centralized Distribution (Physical). All requests by DISA for physical media (not downloaded or electronically acquired by DISA) of the CA software and/or documentation shall be addressed by the Contractor as the centralized physical distribution process, and shipments will be sent directly to the Central Distribution Site(s) as identified in the Exhibit C, Technical Standards, paragraph 14.d. In emergency situations, DISA will work with the Contractor to identify the emergency drop-shipment point and Point of Contact (POC).

Software can be copied, installed, and operated for backup, disaster recovery testing (COOP and ACE purposes.

++NOTE: See Section 8.0, DEFINITIONS, for more information on these business practices.

2.5.3.1. Non-Production Use. Backup and disaster recovery testing (COOP) refers to the use of installed software to perform production environment backup operations and disaster recovery testing (COOP) to ensure…