HC108425R0004 AMD01 RELEASED.pdf

HC108425R0004

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

This Solicitation Amendment 0001 is to:

A. Update Performance Work Statement.

B. Update Section L.

C. Update Section M Evaluation Factors.

D. Add Attachment L1 – Non-Disclosure Agreement (NDA) for Non-Government Personnel.

E. Provide responses to Attachment L2 - Solicitation Question and Answ er.

F. Update KO/CS POC information in G1 and 52.233-2.

Proposal submission extended to Monday, June 23, 2025 at 10am CST.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 65

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 10-Jun-2025

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HC108425R0004

X 9B. DATED (SEE ITEM 11)

19-May-2025

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

10-Jun-2025

CODE

DISA/DITCO-SCOTT-PS84

2300 EAST DRIVE

SCOTT AFB IL 62225

HC1084 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SARA A. VOGELGESANG / CONTRACTING OFFICER

667-891-4236 sara.a.vogelgesang.civ@mail.mil

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

Award/Mod Effective Version Date

Award

Contract Number: TBD

Task Order Number: TBD

Contractor Name TBD

Tracking Number: 842470493

Follow-on to Previous Contract and Task

Order Number:

HC102818D0042

1. Contracting Officer’s Representative (COR).

a. Primary COR. See Points of Contact in Contract Administration Data

Name:

Organization: Defense Information Systems Agency (DISA)

DODAAC: H98272

Address: One Overcash Ave., Bldg 3, Letterkenny Army Depot

Chambersburg, PA 17201

Phone Number:

E-Mail Address:

b. Alternate COR. See Points of Contact in Contract Administration Data

Name: TBD

Organization: Defense Information Systems Agency (DISA)

DODAAC: H98272

Address: One Overcash Ave., Bldg 3, Letterkenny Army Depot

Chambersburg, PA 17201

Phone Number: TBD

E-Mail Address: TBD

c. Property Administrator.

Name:

Organization: Defense Information Systems Agency (DISA)

DODAAC: H98272

Address: J4/FL14, HQ, Fort Meade, MD 20755

Phone Number:

Mail Address: disa.meade.j4.mbx.fl31-industrial-property@mail.mil,

2. Contract Title. Processor Capacity Services (PCS) Z Series Chipset Contract.

3. Background. DISA is a provider of information technology (IT) solutions for the

Department of Defense (DoD). DoD customers require IT processing, storage, and communications services. DISA must have the ability to provide processor capacity services to the Government and mission partners. The purpose of this contract is to provide processor infrastructure capacity to meet new and emerging customer requirements and the ability to replace existing DISA processor capacity that has exceeded its technical or economic life, as determined by the Government. Throughout this PWS, the term Processer is used to describe the process of using technology to transfer information from point to point.

4. Objective. The Government’s goal is to obtain a dynamically scalable processor capability using an on-demand service approach that will readily adjust changes, both increases and decreases in processor requirements and is and is priced on a utility (as used) basis for the total lifecycle of the contract. This utility concept requires that the contractor provide all assets needed for the managed service. These assets will include new hardware, software, software maintenance and licensing, and all associated design capabilities, logistical services, field maintenance, and systems engineering. The capability will meet the requirements of security, availability, scalability, and modernization of the processor infrastructure.

5. Scope. The scope of this contract includes procuring, delivering, installing, deinstalling, transporting, configuring, and providing the hardware, the Linux operating software, technical support services, and operational control required to deliver to the hardware / chipset required to deliver processor capability for IBM System Z (IBM z/OS, IBM z/VM, Red Hat Enterprise Linux, SUSE Linux Enterprise Server).

a. Processor Capabilities: The Processor capability includes all hardware (including cabinets/racks/cabling), hardware maintenance, operating system software, VMWare, and all other software required for the contractor’s solution to operate, and services for the operation of the processor infrastructure associated with this contract remote access availability, the ability to access hardware and software equipment and management services to monitor and manage processor resources at Government approved locations.

b. Processor Equipment: The Processor equipment includes hardware (including cabinets/racks/cabling), hardware maintenance, operating system software, VMWare, and other software required for contractor solution to operate, and services for the processor infrastructure associated with this contract and other devices needed for the operation of the overall processor infrastructure.

c. Processor Infrastructure: The Processor infrastructure includes hardware and software equipment including operating system software, VMWare, and any other software required for the contractor’s solution to operate, services, and other required devices in DISA and other DISA-approved locations to ensure DISA customers receive uninterrupted, continuous access to information technology equipment and networks.

d. Provisioning Servers: The contractor shall provide infrastructure servers for the operation of this contract.

5.1 Contractor Responsibilities. The contractor shall procure, deliver, install, deinstall, transport, configure, and provide the necessary hardware (which may include cabinets/racks/cabling/cable management/PDUs), hardware maintenance, processor operating system software, all other software required for the contractor’s solution to operate, and service to provide the processor infrastructure associated with this contract as a

Capacity Service. The contractor shall provide cabinets, racks, cables, and other infrastructure items as supply items to be owned and retained by the Government. The contractor shall clearly identify the make and model that is being proposed to satisfy all requirements, including hardware or software, to meet the requirements of this PWS as defined in PWS Section 6. Performance Requirements.

5.2 Government Responsibilities: The Government is responsible for the day-to-day operational control of the environment where the communication equipment will reside.

Operational control includes monitoring activities, configuration changes based on changing requirements and ensuring that required updates to operating software are received from the contractor and applied.

5.3 Processor Capacity Services. The contractor is to provide processor capacity services using a utility use concept. All capacity assets needed for the service shall be provided by the contractor. Assets provided as a utility shall include the hardware and software listed in the

PWS, software maintenance and licensing, logistics, field maintenance, and systems engineering as requested by DISA.

5.4 Hardware. The Contractor is required to provide new hardware that is not currently installed in DISA data centers to satisfy the initial provisioning or vendor management stack requirements of this contract. All hardware to support the capacity service brought into

DISA locations identified in Section 9. Place of Performance, for the first time must be new hardware. The Government will make the determination if hardware can be reutilized from a decommissioned call order for a new call order if the hardware has only been utilized on

DISA networks, Government approval is requested and received, and it is not a product that the Original Equipment Manufacturer (OEM) has withdrawn from support, end-of-service life (EOSL) and/or has not been otherwise designated as end-of-life (EOL).

5.5 Processor Infrastructure. The purpose of this contract is to cover both present and future requirements for communication infrastructure solutions. As technology performance and capabilities improve, the communication infrastructure will provide advances in improvement to performance or capabilities at the awarded Sub-Line-Item

Number (SLIN) at no cost to the Government. The Government will make the final determination on when or if the SLIN configurations will be updated.

5.6 Unclassified and Classified Level Environments. All locations may require a NIPR and

SIPR environment for IBM System Z and all supported Operating Systems. Where required under this contract, the contractor shall provide engineering and maintenance personnel with the appropriate clearance for the Government’s classified and unclassified environments.

Refer to Section 11 for individual personnel security requirements. The contractor shall deploy their separate equipment for classified and unclassified environments and will provide all assets needed for the processor infrastructure regardless of environment, classified or unclassified.

5.7 Storage. The contractor shall ensure all processor infrastructure components provided are compatible with and operate seamlessly with the Government’s processor, communication, and storage infrastructure. The Government currently requires the capability to Boot from SAN and mirrored internal storage. The contractor’s solution must provide both capabilities. All tier pricing shall be based on a Boot from SAN configuration, and the

Government will order internal storage separately when it is required. The internal storage

SLINs are comprised of an individual storage device. The Level One storage device is the smallest available mainstream, high volume, commercially available drive for the given chipset. The Level Two storage device is the largest mainstream, high volume, commercially available storage device for the given chipset. The Level One storage device shall increase in size when the current size is no longer commercially available from the hardware vendor.

The Level Two storage device shall increase in size three months after the release of a new, larger storage device. The two levels of storage device must be of a similar type and form factor.

5.8 Memory. The contractor shall provide three levels of mainstream, high volume, commercially available Dual Inline Memory Module (DIMM) for Power chipsetsSystem

Z. Level 3 is the highest-level DIMM commercially available.

Level 2 is the next highest-level DIMM commercially available. Level 1 is the third highest-level DIMM commercially available. Each memory SLIN will be comprised of one pair of

DIMMs. The Government views the following as the current individual DIMM sizes for each chipset, the SLINs will be comprised of two of these individual DIMMs.

Level Power

One 64GB

Two 128GB

Three 256GB

5.9 Processor Type. As processor technologies advance, the processors shall remain within the new generation at the same position or better as the previous generation at time of contract award.

6. Performance Requirements.

6.1 TASK 1 Processor Capacity.

New processor capacity shall be provided as an ‘on-demand’ service capable of readily adjusting to changes in requirements, including both increases and decreases. The

Government will determine the need for additional capacity and/or processor requirements.

The contractor shall provide flexible, highly scalable, solutions that are nondisruptive.

6.1.1. Technical Requirements and Enterprise Architecture The contractor shall provide a processing solution that can be delivered, installed, implemented, scaled, reconfigured, and maintained through the lifecycle at an optimum level of performance according to the Original Equipment Manufacturer (OEM) best practices without service disruption.

6.1.1.2 Provisioning Management Infrastructure. The contractor shall provide a management infrastructure solution that includes provisioning capabilities, hardware diagnostics, hardware monitoring, event logging, image repositories and additional back-office processes required to reside in a DISA environment to provide the contractor’s technical solution. The contractor-provided infrastructure will be managed and maintained by the contractor DISA and will be subject to Risk Management Framework (RMF) accreditation processes and DISA Security Technical Implementation Guides (STIGs, https://cyber.mil/stigs/) and security policies. RMF accreditation must be accomplished prior to the contract award.

6.1.1.3 Original Equipment Manufacturer Technical Support. The contractor shall provide a methodology/process for the Government to access OEM technical support for the operating systems being utilized. Maximum use of OEM commercial documentation will be used (examples could include operator instructions, maintenance manuals, trainer publications) to provide the contractor’s solution.

6.1.1.4 Additional Hardware Components. The Government may require the installation of generic add-on devices or peripherals to the contractor-provided hardware. These additional components are special use requirements that do not fit into a standard service offering (for example: Crypto card, fax card, etc.). The Government will provide the components for these special use cases and the vendor’s only obligation will be to provide installation of these components.

6.1.1.5 All operating environments whether physical (rack mount or blade) or virtual, must be able to provide connectivity for a minimum of 4 network ports supporting Ethernet traffic, and two separate ports for fiber storage connectivity. Two network ports are utilized for production traffic, one network port is utilized for out of band (OOB) network connections, and one port is required for enterprise backup network (EBN) connectivity. Due to this requirement the four communications network ports must be distributed across 4 separate physical communication switches. Ports for fiber storage connectivity must be distributed across a minimum of 2 Host Bus Adapter (HBA) ports. Fiber channels shall support both 8 and 16 Gbps capabilities. All communications switch equipment must support the use of

Virtual Local Area Networks and any other standard technologies and protocols. The proposed solution shall also integrate into existing processing infrastructure with minimal disruption or reconfiguration of network infrastructure.

6.1.1.6 Software. For all software provided in the contractor’s solution, including operating system software, and any other software required for the contractor solution to operate, the contractor is responsible for ensuring they have documentation that confirms software licenses and annual/current maintenance levels. In the event of an audit, the contractor shall be required to defend any audit discrepancy found against all software products that the contractor has acquired for this contract.

6.1.1.7 IBM System Z Software: The System Z operating system is not required for this contract. The Contractor will not provide any Z Series operating system software. DISA will provide and maintain all Z Series operating system software.

6.2 TASK 2 - Performance/Availability.

6.2.1 Processor Capacity Availability. Processor capacity shall deliver 99.95% availability per orderable system with options to deliver up to 99.999 % availability per orderable system. The definitions and performance measurement are identified below.

Performance Measure 1: Operating Platform Availability 99.95%

• Explanation: The percentage of time each system is available for productive use.

• Measurement: (Total available hours for number of calendar days in reporting month –

Measurement Exceptions – Time server is unavailable, unable to perform core function, or core function is significantly degraded) / (Total available hours for number of calendar days in reporting month – Measurement Exceptions)

*100= Service Level Attained. Total available hours = 24x number of calendar days in reporting month for each orderable system.

Measurement Exception: DISA or customer-initiated downtime, Vendor Preventative maintenance (not break fix or hardware/software repair) that is properly coordinated through the Authorized Service Activity (ASA)/Authorized Service Interruption (ASI) process with DISA and the customer, and environmental failures not attributed to the vendor.

• Availability Objective: 24x number of calendar days in reporting month minus

Measurement Exception (reference definition above).

• Standard: Satisfactory = 99.95%

• Contractor Responsibility: Maintain operating platform, operating system software), and related operating equipment in operating condition at a level to meet 99.95%.

Performance Measure 2: Operating Platform Availability 99.999%

• Explanation: The percentage of time each system is available for productive use.

Measurement: 2A (summary): (Total available hours for number of calendar days in reporting month – Measurement Exceptions – Time server is unavailable, unable to perform core function, or core function is significantly degraded) / (Total available hours for number of calendar days in reporting month – Measurement Exceptions)

*100= Service Level Attained. Total available hours = 24xnumber of calendar days in reporting month averaged over all five nine’s orderable systems.

Measurement 2B (per system): (Total available hours for number of calendar days in reporting month – Measurement Exceptions – Time server is unavailable, unable to perform core function, or core function is significantly degraded) / (Total available hours for number of calendar days in reporting month – Measurement Exceptions)

*100=Service Level Attained. Total available hours = 24x number of calendar days in reporting month for each five nine’s orderable system.

Measurement Exception: DISA or customer-initiated downtime, Vendor Preventive maintenance (not break fix or hardware/software repair) that is properly coordinated through the Authorized Service

Activity (ASA)/Authorized Service Interruption (ASI) process with DISA and the customer, and environmental failures not attributed to the vendor.

• Availability Objective: 24x number of calendar days in reporting month minus

Measurement Exceptions (reference definition above).

• Standard: Satisfactory = 99.999%

• Contractor Responsibility: Maintain operating platform, operating system software (and related operating equipment in operating condition at a level to meet

99.999%.

6.2.2 The contractor shall provide management level escalation procedures to address any issues that may arise and may impact the operation of the services provided.

6.2.3 The contractor shall provide the ability to validate and view HW features and components installed.

6.2.4 The contractor shall provide the central management capability and reporting to include hardware utilization, and error diagnostics of installed hardware components.

Deliverable/s: Central management capability and reporting to include hardware utilization and error diagnostics of installed hardware components.

PWS

Task#

Deliverable

Title

Format Due Date Distribution/Copies Frequency and Remarks

6.2.4 Central

Management

Reporting

Contractor -

Determined Format

Minimum of

Monthly

Standard

Distribution*

Monthly

*Standard Distribution: 1 copy of the transmittal letter with the deliverable to the Primary COR.

6.3 TASK 3 - Maintenance.

The contractor shall perform all Preventive Maintenance actions required by the OEM, including Predictive and Remedial Maintenance, on all equipment delivered as a part of this contract. The contractor must schedule and perform maintenance with no disruption to production operating environment. Day-to-day operations management of the hardware does not require Contractor intervention. Software components are capable of remote management and compatible with the current DISA dedicated management network. All maintenance requirements are included in the utility pricing. SIPR access is required for all personnel that will be performing maintenance on equipment components for current and future customer workloads that reside on the SECRET/SIPR network.

6.3.1 Maintenance Repair and Response Time. Provide processing capacity that delivers

99.95% availability per orderable system with options to deliver up to 99.999% availability per orderable system. Response and repair times for CONUS will be 2-hour response/4-hour repair, unless otherwise agreed to by DISA. The time for responses will begin when the contractor is notified and will end when the contractor contacts DISA. The time for repairs will be measured beginning when the contractor is notified and will end when the repair is completed, and the equipment is available for use in its original state prior to the outage.

Contractor response times do not change the requirements but represent requirements to repair components which might be causing a degraded state. The contractor shall address solution failures of redundant components which might not impact system availability but do create performance issues or introduce single points of failure in systems.

The contractor shall provide 24x7x365 problem escalation/resolution for hardware, operating system software, and capacity management. The contractor shall provide a multi-level solution for response time after being notified by the Government, to commence remedial maintenance for hardware, operating system software and, any other software required for the contractor solution to operate. Each orderable system will be identified to a level of response based on Government need. All maintenance requirements are included in the utility pricing.

6.3.2 Predictive Maintenance. Services rendered for the purpose of avoiding equipment failure. This maintenance includes the process of monitoring equipment error activity using automated identification and reporting systems, alert mechanisms, and diagnostic routines.

When error or event thresholds are exceeded, repairs are applied prior to an actual equipment failure. The contractor shall monitor equipment/component performance using diagnostics defined in PWS Section 6.2.1 for the purpose of identifying whether equipment is operating in accordance with established specifications. This includes hardware, operating system software, and any other software required for the contractor’s solution to operate. Upon determining equipment/component is about to fail or is operating outside OEM specifications, the contractor shall initiate action to effect repair even though no call for remedial maintenance has been initiated by the Government.

6.3.3 Remedial Maintenance.

Remedial maintenance includes all unscheduled maintenance to diagnose and repair malfunctioning equipment or equipment failures. The contractor shall initiate maintenance procedures which include the Government hardware incident ticket using the procedures that will be provided after the contract award. Calls may be initiated by the Government to the contractor’s toll-free help desk service. The contractor must respond and repair, and/or obtain required OEM engagement. The contractor must perform remedial maintenance within the response and repair times required to meet the minimum availability requirements identified in PWS Section 6.3.1, Maintenance Repair and Response Time. This includes hardware, operating system software, and any other software required for the contractor’s solution to operate. The contractor shall provide a monthly report of all remedial maintenance actions, including actual response/repair times for each, within five business days after the previous month ends.

6.3.4 The contractor shall call or email the Global Service Desk (GSD) to notify them that they are going on site for predictive or remedial maintenance and request an incident ticket be generated and coordinated with the physical site. Upon arrival at the physical site, the contractor’s technician shall comply with reporting and identification requirements. The contractor technician shall not enter a production environment or perform any maintenance actions without prior coordination with the physical site. Failure to obtain a properly completed incident ticket prior to accessing a production environment or performing any maintenance action could result in the contractor technician being permanently barred from all DISA processing centers. Service is coordinated with the DISA Global Service Desk

Mailbox Enterprise Services Ticket Request disa.global.servicedesk.mbx.enterprise-services-ticket- request@mail.mil or telephone 844-347-2457. The contractor technician shall be prepared to provide the following information:

DISA Site Location:

Site Point of Contact (POC) (ITSM+ group):

Serial Number:

Vendor:

Vendor Phone Number and PIN:

Vendor Case Number:

Date/Time Engineer expected:

Barcode:

Floor Location:

Physical Address:

Short Description of Malfunction:

Contract Number:

6.3.5 Preventive Maintenance.

Preventive maintenance includes all regularly scheduled maintenance to maintain equipment in fully operating order as recommended by the OEM contractor. This is accomplished using the contractor-provided system monitoring devices or other monitoring systems that do not adversely impact operations to predict impending equipment failure. Preventive maintenance shall be scheduled with the Government POC, local Government site, and the contractor.

The Government may determine that the preventive maintenance action requires coordination with the customer base of the affected system. In this scenario, the Government POC will schedule an Authorized Service Activity (ASA)/Authorized Service Interruption (ASI) and coordinate the date and time with the affected customers and the contractor. The contractor shall begin preventive maintenance IAW the approved schedule within 90 calendar days after the date of the contract award. Preventive maintenance shall be scheduled outside of the normal business hours, 0600-1800 local time. For all PWS references to local time, local time is determined by the time zone of the specific Government location. The contractor must submit the preventive maintenance schedule for their equipment in writing to the Contracting

Officer (KO) and COR within 90 calendar days after the date of the contract award. The preventive maintenance schedule will be modified if or when needed at no cost to the

Government by mutual agreement of both the contractor and the Government. The contractor’s proposed preventive maintenance schedule shall not be less than the preventive maintenance recommended by the OEM and at a minimum shall include the following information:

Nomencla ture of hardware item

Model

Serial Number

Remote diagnostics and reporting capabilities

Frequency and duration of preventive maintenance and type of service to be performed

Authorized Service Activity (ASA): An action that is being taken where no disruption to service is anticipated. Authorized Service Interruption (ASI): An outage that will impact the customer system causing unavailability. Deliverable/s: Preventive Maintenance schedule within 90 calendar days of contract award.

PWS

Task#

Deliverable

Title

Format Due Date Distribution/Copies Frequency and Remarks

6.3.5 Preventive Contractor - 90 calendar days Standard Contract

Maintenance Determined Format after contract Distribution* award and

Schedule award modifications when required

*Standard Distribution: 1 copy of the transmittal letter with the deliverable to the Primary COR.

6.3.5.1 Preventive Maintenance Malfunctions. If during preventive maintenance an equipment malfunction is identified, the contractor shall report the malfunction to the

Government. The malfunction shall be corrected as Remedial Maintenance defined in

PWS Section 6.3.3 in compliance with maintaining the capacity availability requirements per orderable system as defined in PWS Section 6.2.1, Processor Capacity

Availability.

6.3.6 Remote Diagnostics. The Government requires that all processor solutions be supported by remote diagnostics, administration, and tools that communicate over the DISA management network. System errors will be immediately reported to remote tools servers and service center(s). The contractor shall provide written confirmation that capacity devices delivered can be supported by remote diagnostics within 30 calendar days after the start of performance. Verbal contact between the local maintenance technician and an off-site technician is not acceptable for remote diagnostics. There shall be a diagnostic system usable by the remote technician. The dial-in feature for remote access to equipment can be used, but only after receiving authorization from the Government. The feature must be capable of disabling and set up to provide the Government with the ability to enable the feature upon request from the contractor.

Deliverable/s: Written confirmation that reports and remote diagnostics for applicable equipment exist within 30 calendar days of contract award.

Deliverable

Title

Format Due Date Distribution/Copies Frequency and Remarks

6.3.6 Remote

Diagnostics

Contractor -

Determined Format

30 calendar days after contract award

Standard

Distribution*

Contract award and as ordered.

*Standard Distribution: 1 copy of the transmittal letter with the deliverable to the Primary COR.

6.4 TASK 4 - Delivery, Installation, Deactivation and Removal.

The contractor shall provide the processor hardware infrastructure necessary to provide contract requirements. The contractor shall acquire, install, deinstall, transport, provide the necessary hardware (including cabinets/racks), hardware maintenance, operating systems software, and all software required for the contractor’s solution to operate, and services to provide the processor infrastructure associated with the contract. The contractor may be required to install hardware in DISA and/or Mission Partner owned racks. DISA will ensure those racks meet the documented rack requirements defined in Appendix 7. DISA will determine the need for additional processor equipment. Unless otherwise mutually agreed upon, equipment deliveries, installations, deinstallations shall be accomplished during normal business hours, 0600-1800 local time, Monday through Friday.

6.4.1 Delivery. Equipment shall be packaged to prevent damage and marked to allow CSC identification (ID) at the docks to include manufacturer and call order number, contract and delivery order number, and site point of contact. Site POC will be contacted to coordinate installation activities. The Government reserves the right to consider an alternative delivery schedule. Delivery and installation of equipment must occur within 30 calendar days from the acceptance date of the call order by the contractor.

6.4.2 Installation. The contractor is responsible for installing the ordered capacity.

Installation tasks include rack placement, power on and check for operational status. The contractor shall install, power up, and confirm operational status of processor capacity.

6.4.3 Power-up Configuration. The contractor shall complete power-up configuration as detailed by the Government. The Government shall perform final configuration.

6.4.4 Government acceptance. The written or electronic acceptance of new capacity by the

Government starts the billing cycle for this service. The Government requires the ability to place orders for new technology throughout the Period of Performance (PoP) for this contract.

The contractor shall work with DISA to develop an acceptance testing methodology and smoothly transition the new (unless approved by the Government) equipment into the DISA production environment.

6.4.5 Deactivation, Deinstall and Removal of Equipment. The contractor shall conduct any deinstall and removal of contractor-owned hardware items on this contract upon request by the Government both during and at the end of the contract, at no additional cost to the

Government. Deactivation, deinstallation and removal of hardware from the DISA site shall occur within 30 calendar days after the date of the acceptance of the deactivation call order by the contractor. Removal of all Contractor owned equipment will be coordinated with the

Government site Accountable Property Custodian (APC) or property management group.

Deactivation and removal of equipment will be scheduled during normal business hours, 0600-1800 local time, Monday through Friday.

Components and/or writeable media being removed from the site (tapes, hard drives, mass storage devices, etc.) will be sanitized or may be retained by the Government for destruction in accordance with the Assistant Secretary of Defense Memorandum, Subject: Disposition of

Unclassified DoD Computer Hard Drives, June 4, 2001. DISA Security guidance at no cost to the Government. The contractor must be aware that the sanitation process is to prevent any compromise of classified and/or controlled unclassified data and may render the system components and/or writeable media unserviceable and/or destroyed. The Government will make the determination as to whether drives can be sanitized or destroyed.

6.4.6 Contract Performance outside normal business hours. The contractor may be required to perform delivery, installation, upgrades, uninstalls and equipment removal outside of normal business hours during evenings and weekends. Although the Government will attempt to limit this requirement, the contractor must plan to work after hours, weekends, and or federal holidays. After hours are defined as before 0600 local time, after

1800 local time, weekends, and federal holidays.

Recognized federal holidays recurring annually (Reference 5 U.S.C. § 6103):

● New Year’s Day – January 1

● Martin Luther King Jr.’s Birthday – the third Monday in January

● President’s Day – the third Monday in February

● Memorial Day – the last Monday in May

● Juneteenth National Independence Day – June 19

● Independence Day – July 4

● Labor Day – the first Monday in September

● Columbus Day – the second Monday in October

● Veterans Day – November 11

● Thanksgiving Day – the fourth Thursday in November

● Christmas Day – December 25

6.4.7 Standby. The contractor may be required to be available on standby after hours, weekends, or federal holidays. All standby hours will be included in the technical assistance pricing and approved in advance with an accepted call order. Standby will include having a field engineer available on-site as requested by the Government.

6.4.8 Equipment Report. After an order has been placed, and before delivery, the contractor shall send a report containing equipment information to include serial numbers, worldwide names, MAC addresses, etc. to the Government via email. Email address(es) will be provided at contract award. This action allows the Government to prepare for equipment receipt. The contractor shall provide the report 10 business days prior to equipment delivery.

Deliverable/s: Provide report of equipment information 10 business days prior to equipment delivery.

Task#

Deliverable

Title

Format Due Date Distribution/Copies Frequency and Remarks

6.4.8 Equipment

Report

Contractor -

Determined Format

10 business days prior to equipment delivery

Standard

Distribution*

When required for each delivery

*Standard Distribution: 1 copy of the transmittal letter with the deliverable to the Primary COR.

6.5 TASK 5 - Processing Capacity.

6.5.1 The contractor shall provide processing capacity that is scalable to adjust to increases and decreases in the required workload. This includes Central Processing Unit (CPU), memory utilization, network interfaces (network interface cards (NIC), etc.). The contractor shall provide processing capacity with no adverse impact on the existing production workload.

6.5.2 The contractor shall provide a process for increasing and decreasing capacity for CPU, memory, network interfaces, (network interface cards (NIC), etc.), and sysplex within a tier.

The contractor shall provide a process to collaborate with the Government to modify hardware provided within tier(s) as technology advances, chipset performance improves, or other new hardware-based technologies are introduced, without any impact to the awarded

SLIN pricing.

6.5.3 The contractor shall provision servers for the infrastructure at no additional cost.

These servers must be provided by the contractor to image hardware with the current agreed upon images (reference PWS 6.1.1.6). Provisioning cannot be accomplished via the Wide Area Network (WAN). The contractor’s solution shall include automation capabilities to provide efficiencies in provisioning and automation to streamline recurring vendor and Government tasks. Automation capabilities may be utilized by both the contractor and the Government in sustainment of provisioned infrastructure.

6.5.4 The contractor shall provide processing capacity that is priced on a utility (as used) basis and tier size as defined in Appendix 1.

6.5.5 The contractor shall provide processing capacity for unclassified and SECRET workloads. Where required under this contract, the contractor shall maintain

Performance/Availability standards on all hardware, operating system software, and any other software required for the contractor’s solution to operate. The contractor shall provide engineering and maintenance personnel with the appropriate clearance for DISA’s classified and unclassified environments. SIPR access is required for all personnel that will be maintaining current and future customer workloads that reside on the SECRET/SIPR network. There must be separate hardware infrastructure including channels and networks and do not share components as instructed by DISA STIGs. This requirement has no impact on the security clearance requirements in PWS Section 11.

6.6 TASK 6 - Integration/Interfaces.

All equipment provided under this contract shall fully function with the existing DISA infrastructure and network.

6.6.1 The contractor shall provide training and familiarization to the Government System

Administrators for the Contractor-provided infrastructure solution. The contractor’s training plan shall provide all or a combination of the following elements: OEM documentation guides, Computer Based Training (CBT) manuals, training hours and in- person/virtual classroom training at Government and/or Contractor facilities. Technical training will be recurring as new hardware or capabilities are introduced into the processing environment for the Government engineering and operations teams. Technical training will be provided as part of the total managed service The contractor shall provide a plan 10 business days prior to the initial capacity deployment demonstrating how they will provide training to employees prior to capacity being deployed for the first time. Training costs shall be included in the SLIN pricing.

Deliverable/s: Provide training plan 10 business days prior to the initial capacity deployment.

Deliverable

Title

Format Due Date Distribution/Copies Frequency and Remarks

6.6.1 Training Plan Contractor -

Determined Format

10 business days prior to initial capacity deployment

Standard

Distribution*

When required for each delivery

*Standard Distribution: 1 copy of the transmittal letter with the deliverable to the Primary COR.

6.6.2 The contractor shall provide infrastructure that does not disrupt, conflict, or interfere with the Government’s specified Enterprise Systems Management (ESM) architecture.

6.6.3 The contractor shall ensure all infrastructure components provided in support of the contract are capable of being managed remotely via a dedicated Government management network.

6.6.4 The contractor shall ensure all infrastructure components provided in support of the contract are capable of being backed up via a dedicated backup network. Infrastructure components provided must be compatible with and operate seamlessly with DISA’s communications and storage infrastructure.

6.6.5 The contractor shall ensure all infrastructure components provided in support of the contract are coordinated with and agreed to by the Government before introduction into the processing environment.

6.6.6 The contractor shall ensure all components are IPv6 capable. Criteria to be considered

IPv6 capable are conformant with the IPv6 standards profile contained in the National

Institute of Standards and Technology (NIST) USG IPv6 guidance, NIST SP 800-119, Guidelines for the Secure Deployment of IPv6; maintaining interoperability in heterogeneous environments and with IPv4; commitment to up-grade as the IPv6 standard evolves; and availability of IPv6 technical support.

6.7 TASK 7 - Release Management.

DISA will provide and maintain all Z Series operating system software.

The contractor shall work with the Government to test and field Operating System (OS) releases and upgrade packages. The Government develops standard documentation on version levels in line with change and configuration management programs. The contractor shall package the initial and subsequent upgrade OS releases. Initial OS releases are only deployed by the contractor on capacity hardware; but the initial OS release must be tested, coordinated, and documented with the Government to ensure all images are enterprise compatible. The contractor manages the OS software repository. This repository will be available to the Government to execute OS upgrades.

6.8 TASK 8 - Package OS.

The Government will lead the operational acceptance testing with Contractor. The contractor shall provide the release of new OS's and upgrade packaging for all upgrades. Server OS software is owned and licensed by the contractor, with the Government having the right to use for the life of the capacity services contract. After receiving an image from the contractor, the Government will install, test, and validate image for adherence to standards, perform integration testing, provide release documentation, or image corrections necessary for seamless integration into the DISA infrastructure. Items to be validated by the

Government include the introduction of new hardware, patches, or firmware versions to the enterprise; new or upgraded software; and tool integration and functionality such as ESM agents, Blade Logic, HBSS, Veritas, driver compatibility, IAVA compatibility and level, and

STIG to the current Government required level as applicable to the platform.

6.8.1 Manage the OS repository and Availability. The contractor shall manage the OS software repository with the availability for the Government to execute OS upgrades. The repository will be used as a central repository for approved OS version baselines. The

Government must be able to pull and install the OS upgrade package for testing on capacity hardware in use under this contract and will return the validated OS packages for general provisioning and upgrade processes.

6.9 TASK 9 - Security.

The contractor shall comply with all applicable security directives, including the DoD

Directive 8140.01, Cyberspace Workforce Management, and DoDM 8140.03, Cyberspace

Workforce Qualifications and Management Program; the Assistant Secretary of Defense

Memorandum, Subject: Disposition of Unclassified DoD Computer Hard Drives, dated June

4, 2001; DISA Security Technical Implementation Guides (STIGs).

6.9.1 All contractor-provided hardware and software solutions shall comply with DISA

STIGs. The contractor’s management solution and infrastructure provided must be compatible with Government authentication, CAC (Common Access Card) or PIV (Personal

Identity Verification) enabled.

6.10 TASK 10 – Facilities.

SIPR access is required for all personnel that will be installing and maintaining current and future customer workloads that reside on the SECRET/SIPR network.

6.10.1 Racks. The contractor shall provide a solution that complies with the standard rack and power specifications as detailed in Appendix 4 and Appendix 6. Each rack shall be supplied with two (2) each three phase modular power distribution units (MPDU’s) that mount vertically into the rear access/cabling spaces of the rack and provide a Simple

Network Management Protocol (SNMP) interface or Modbus external port capability.

6.10.1.2 The contractor shall allow the Government the flexibility to modify rack configurations if necessary to install the cooling scheme that provides the cooling infrastructure. The contractor shall provide a solution for high density cooling configurations.

Additional high density cooling technologies may be proposed. Rack height dimensions will be permitted to exceed maximum height specified if the high-density rack cooling solution is attached to the rack and fits within the applicable dimensions.

6.10.2 Ancillary Equipment. The contractor shall include ancillary equipment such as

MPDUs, grommets, and blanking panels. Each server/enclosure/cabinet must include Cable

Management that allows for the server/enclosure/cabinet to slide on the rails without binding or causing interference to airflow. The contractor shall include any manufacturer and vendor equipment required to meet their own mounting and warranty standards.

6.10.3 Grounding. The contractor shall provide grounding capability.

6.10.4 Energy Star Requirement. The contractor shall provide hardware that meets the

Energy Star requirements. See:

https://www.energystar.gov/ia/partners/product_specs/program_reqs/eps_prog_req.pdf

6.11 TASK 11 - Technology Refresh (TR) Program.

The processor technology continues to advance, and this contract shall require incorporation of these advances during the life of the contract. The Government will make the final determination on when or if the SLIN configurations will be updated. The TR program is designed to replace aging and outdated processor hardware to minimize obsolescence in advance of loss of service or a hardware failure. SIPR access is required for all personnel that will be installing and maintaining current and future customer workloads that reside on the

SECRET/SIPR network.

6.11.1 Technology Update. When an OEM makes available for sale a newer technology listed in PWS Section 6.1, the contractor must make this technology available to the

Government on this contract within six months. The newer technology shall replace the current SLIN offering for all new orders at the same or lower current year SLIN pricing. If the contractor’s current solution reaches end-of-sale and the product or model is no longer available from the manufacturer, the contractor must replace it with the manufacturer’s replacement product or model at the same or lower current year SLIN pricing.

6.11.2 Technology Refresh. The contractor shall develop a program to replace aging and outdated technology to minimize obsolescence before loss of support, loss of service or failure occurs. During the lifecycle of the contract as technology used for the contractor’s solution reaches EOL and becomes unsupportable by the manufacturer or becomes obsolete as technology advances, the contractor must provide new solutions to replace older solutions without a price increase or uplift charge.

If a call order for capacity has been in production for five years, the Government may refresh the capacity. The Technology Refresh Program will replace the oldest processor equipment, but generally processor hardware will have a five-year service life. The Government may refresh hardware based on functionality and technology updates, at any point in time during the first five years.