J-5 Processor PWS Template revised 19 Sep 11 AM007.docx

Acquisition Sensitive Attachment J-5

HC1028-11-R-0104

Amendment 0007

Acquisition Sensitive Attachment J-5

HC1028-11-R-0104

PERFORMANCE WORK STATEMENT (PWS)

as of dd/mmm/yyyy

TEMPLATE SUBMITTED AS A DRAFT FOR OFFEOR TO WORK FROM

1.0 Contracting Officer Representative (COR).

a. Primary COR or TM. See Clause 52.204-9000

Organization:

Department of Defense Activity Address Code (DODAAC):

H98272

Address:

Phone Number:

Fax Number:

E-Mail Address:

b. Alternate COR or TM. See Clause 52.204-9000

Organization:

Address:

Phone Number:

Fax Number:

E-Mail Address:

2.0 Contract Title. DISA, Computing Services Processor Capacity Services.

3.0 Background. DISA Computing Services (CSD) is a provider of information technology solutions for the Department of Defense (DoD). DISA’s DoD customers require processing for a variety of applications. DISA CSD must have the ability to provide cost-effective processing capacity in a timely manner whenever and wherever the requirements occur.

The purpose of this contract is to provide state-of-the-art processing capacity to meet new and emerging customer requirements and the ability to replace existing DISA processing capacity that has exceeded its technical life as determined by the Government.

DISA is required by the DoD to enhance communications effectiveness through improved information interoperability. The Assistant Secretary of Defense for Networks and Information Integration (ASD/NII) has articulated a vision for transforming the information environment in the DoD. This vision calls for a move from the centralized thinking and planning currently reflected in the Task, Process, Exploit, Disseminate (TPED) paradigm, to an edge-centered Task, Post, Process, Use (TPPU) approach to information sharing and availability. The envisioned changes represent a fundamental paradigm shift from providing platform centric applications to platform independent, web-enabled, Net-Centric services requiring the support of a diverse processing environment, that meets the requirements of the end users, and which is highly available, secure, and reliable. As a result of the shift to Net-Centric services, DISA-CSD will also need to provide processing capabilities at DISA-owned and other approved processing locations.

4. 0 Objectives. The objective of this contract is to obtain reliable, responsive, and cost effective processor infrastructure services of “on-demand” processing capabilities for specified chipset architecture in both DISA and other DISA-approved locations, which are both in the continental United States (CONUS) and outside of the continental United States (OCONUS). DISA's goal is to obtain a dynamically scalable processing capability utilizing an on-demand service approach, for new equipment, that will readily adjust to changes in processing and throughput requirements, both increases and decreases, and is priced on a utility ("as used") basis or tiered structure.

The service provider will acquire, install, deinstall, transport, configure, and provide the necessary hardware (including cabinets/racks/cabling/cable management/PDUs), hardware maintenance, operating system software, VMWare, as well as, any other software required for the Contractor solution to operate, and services to support the processor infrastructure associated with this contract. The Government will maintain day-to-day operational control of the processing environment and complete oversight responsibility. This operational control includes the installation of all software updates after the initial delivery. However, all operating system software, VMWare, as well as, any other software required for the Contractor solution to operate, including software maintenance and licensing shall be included under this contract.

5.0 Scope. The Contractor will design, deliver, install, and maintain processor capacity infrastructure in concert with the Government, at any of the current DISA CSD computing facilities or future DISA CSD computing facilities in the continental US (CONUS), the Government, DISA CSD outside CONUS (OCONUS) and other DISA or DISA approved locations worldwide where DISA CSD may acquire an operational responsibility.

5.1 The hardware/Chipset and the operating systems software, required to deliver processor capability for DISA are:

5.1.1 IBM System z (IBM z/OS, IBM z/VM, Red Hat Enterprise Linux, SUSE Linux Enterprise Server)

5.1.2 X-86 (Windows Server, Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Solaris, VMware vSphere Enterprise Plus)

5.1.2.1 VMWare is only required for the X-86 chipset.

5.1.3 Itanium (HP-UX)

5.1.4 SPARC (Solaris )

5.1.5 IBM System p (AIX)

5.1.6 Any other operating system software that DISA may require in the future.

5.2 This initiative will support controlled unclassified and classified including SCI level environments.

5.3 The objective is for the Contractor to provide processor services using a “utility contract concept”. This utility concept requires that the Contractor provide all assets needed for the processor service. These assets shall include, but are not limited to, hardware, software, software maintenance and licensing, design capabilities, logistical support, field maintenance, and systems engineering.

5.4 After contract award, all requirements must be staffed through the Contractor and Government Program Management Offices. Any contractual requirement obtained via another source (i.e., sales) will not be addressed.

Offeror should discuss solution for order processing, to include points of contact for program management, engineering, technical support, and invoicing.

5.5 Current Environment – DISA CSD currently provides processor services at 15 computing facilities in the CONUS, located at:

· Chambersburg, PA,

· Columbus, OH,

· Dayton, OH,

· Denver, CO

· Fort Meade, MD

· Huntsville, AL,

· Jacksonville, FL

· Pensacola, FL

· Mechanicsburg, PA,

· Montgomery, AL,

· Ogden, UT,

· Oklahoma City, OK,

· San Antonio, TX,

· St Louis, MO,

· Warner Robins, GA

5.5.1 Three (3) OCONUS locations are:

· Patch Barracks, Vaihingen, Germany

· Pearl Harbor, Hawaii

· Manama, Bahrain

5.5.2 Future locations. Contractor shall have the ability to support DISA or DISA approved locations worldwide where DISA CSD may acquire an operational responsibility.

5.6 DISA will afford Contractor protection under the Department of Defense’s Status of Forces Agreement with all OCONUS Host countries. DISA will hold Contractor harmless from any and all local taxes, value-added taxes, excise taxes, and/or other tariffs imposed by the Host country on goods and services entering the country in support of this contract. Should DISA not be able to afford Contractor protection from these taxes and tariffs, DISA will reimburse Contractor for any and all reasonable and customary taxes and/or tariffs.

5.7 All locations may require a NIPR, SIPR and the potential for a Sensitive Compartmented Information Facility (SCIF) environment.

5.7.1 Unclassified, Classified, SCI Level Environments. Where required under this contract, Contractor will provide engineering and maintenance support personnel with the appropriate clearance for DISA’s classified and unclassified environments. (See para 13 for individual personnel security requirements). Contractor will deploy separate equipment for classified and unclassified environments and will provide all assets needed for the processor infrastructure regardless of environment (classified or unclassified).

Provide Offeror solution.

6.0 Performance Requirements.

6.1 Task 1 - Operating Chipset Architecture/Operating Systems.

6.1.1 Subtask 1.1 - Technical Requirements and Architecture.

The hardware/Chipset and the operating systems software* required to deliver processor capability for DISA:

6.1.1.1 IBM System z (IBM z/OS, IBM z/VM, Red Hat Enterprise Linux, SUSE Linux Enterprise Server)

6.1.1.2 X-86 (Windows Server, Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Solaris, VMware vSphere Enterprise Plus)

6.1.1.2.1 VMWare is only required for the X-86 chipset.

6.1.1.3 Itanium (HP-UX)

6.1.1.4 SPARC (Solaris)

6.1.1.5 IBM System p (AIX)

6.1.1.6 *Any other operating system software that DISA may require in the future.

6.1.1.7 Provisioning Management Infrastructure. The offeror will provide a management infrastructure solution to include provisioning capabilities, hardware diagnostics, hardware monitoring, virtualization management, event logging, image repositories or additional back office processes required to reside in the CSD infrastructure to support the offeror’s technical solution. This offeror-provided infrastructure will be managed and maintained by the offeror, and will be subjected to DIACAP accreditation processes as well as relevant DISA STIG and security policies. Accreditation must be accomplished before the first order can be placed under this contract.

Provide Offeror solution.

Deliverable/s: Delivery and ease of implementation of technical hardware/chipset.

6.1.2 Subtask 1.2 – OS Requirements. For Operating system listed under each chipset, the Contractor will provide the most current operating system; additionally provide solution to support two versions back. The Government defines the most current version as N and the two proceeding versions as minus two (-2). Therefore N-2 is used to describe an OS current version and two major releases back (supportable by the OEM). An example being for the RHEL (Red Hat) 6, RHEL 5, and RHEL 4.

VMware is exempt from "N -2" versioning. The Government's sustainment strategy for VMware is limited to "N" and "N-1" only for the time it takes to migrate from "N-1" to "N".

6.1.2.1 Subtask 1.3 – OEM Technical Support. The Contractor will provide a methodology/process for the Government to access OEM technical support (including VMWare) for the operating systems being utilized.

Provide Offeror solution.

6.1.2.2 Provide high availability options for OS (clustering) at the local site for tying hardware together.

Provide Offeror solution.

Deliverable/s: Delivery, management and maintenance of specified O/S versions, access to OEM technical support and high availability options.

6.1.2.3 Subtask 1.4 – Image. Provide an “image” of the CSD operating environment. The “image” will not run on the capacity services hardware. The “image” will be purchased for customers in the IT development stage prior to transitioning their projects to CSD. Purchase of the “image” for customers is intended to reduce transition issues. This image should include all operating system software, monitoring software, etc that would normally be provisioned via service. This service should be priced as a one-time purchase.

Provide Offeror solution.

Deliverable/s: Provide “image” that will be used on Government systems only when hardware is provisioned.

6.1.3 Subtask 1.5 – Additional Hardware Components. The Government will require utility service methods for adding generic add on devices or peripherals to the vendor-provided hardware. These additional components are special use requirements that do not fit into a standard service offering (for example: Crypto card, fax card, MUX card, etc.). The Government would provide the components for these special use cases and the vendors only obligation would be to provide installation of these components.

Provide Offeror solution.

Deliverable/s: Ability to define and deliver generic additional hardware components and integrate/install requested components.

6.1.4 Subtask 1.6 – Virtual Environments. Provide solution that recognizes VMware/vSphere Enterprise Plus 5.0 or higher as the standard infrastructure for the x86 virtual environment. The x86 virtual software (VMWare/VSphere Enterprise Plus 5.0 or higher) will be included in the processor utility service. VMware VSphere 5.0 or higher must be provided with all Tier 1 and Tier 2 X-86 orders.

6.1.4.1 Virtualization for Unix environments will be accomplished using native virtual capabilities for HP-UX, Solaris, and AIX. For native virtual capabilities, offeror will provide comparable native virtualization management tools and infrastructure for Government management of virtual operating environments.

6.1.4.2 Offeror will provide Virtual Server Standard (4 ea) for NIPR, SIPR, NIPR-Back-up, & SIPR-Back-up as well as 24x7x365 support for as part of their infrastructure and include in the processor utility service. The Government support staff will manage the virtual hosts, placements, relocating environments (vmotion), through vCenter Server Standard toolset provided by the offeror.

6.1.4.3 vCenter Server Standard, as well as, 24x7x365 support should also be available to order under a separate orderable SLIN on the B-Table so the Government can order if necessary for future requirements.

6.1.4.4 Tier pricing should also include virtual OE licensing for Microsoft operating systems, Redhat Linux operating systems, SUSE Linux operating systems, and switching infrastructure components.

Deliverable/s: Provide tools, licensing and infrastructure capabilities to support virtualized environments.

6.1.4.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 2 separate physical Host Bus Adapter (HBA) cards. All communications switch equipment must be able to support the use of VLANs, as well as any other standard technologies and protocols. The proposed solution should also integrate into existing processing infrastructure with minimal disruption or reconfiguration of network infrastructure.

Provide Offeror solution.

Deliverable/s: Provide all OEs (physical or virtual) with connectivity for a minimum of 4 network ports supporting ethernet traffic and two separate ports for fiber storage connectivity, as well as, support VLANS and any other standard technologies and protocols.

6.1.5 Subtask 1.7 - Software. For all software provided in the Contractor solution, including operating system software, VMWare, as well as, any other software required for the Contractor solution to operate, Contractoris responsible to ensure they have documentation that confirms software entitlements and annual/current support/maintenance levels. In the event of an audit, the Contractor will be required to defend any audit discrepancy found against all software products that the Contractor has acquired in support of this contract.

Provide Offeror solution.

Deliverable/s: Provide software license and maintenance documentation to confirm software entitlements and maintenance levels, as required by the Government.

6.1.6 – IBM System z: 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.1.6.1 Subtask 1.8 – Operating System Console Management Hardware. The Contractor will provide operating system console management hardware. DISA requires:

6.1.6.1.1 The flexibility to replace an OS console environment at both a site level (all at once) and at a mainframe level.

6.1.6.1.2 Capability to connect gateways with multiple mainframes utilizing FICON or OSA channels.

6.1.6.1.3 Capability to support multiple (minimum of 10) OS sessions per console.

6.1.6.1.4 Capability to support IP connections for Remote Console support.

6.1.6.1.5 Capability to support IP connections for message consolidation management solutions (currently IO Concepts).

6.1.6.1.6 Required fiber optic cabling and connectors as necessary for connectivity to peripherals such as FICON switches, Storage devices, Communications devices, Integrated Coupler, Channel to Channel, etc. Offeror should provide a scalable solution for fiber optic cables. All cable costs should be included in the tier pricing.

Provide Offeror solution.

Deliverable/s: Operating System Console Management Hardware.

6.2. Task 2 - Performance/Availability.

6.2.1 Subtask 2.1 - 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 is identified below.

Performance Measure 1: Operating Platform Availability 99.95%

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

1. Availability Objective: 24x7x365 minus Measurement Exception (see definition below).

1. Standard: Satisfactory = 99.95%

1. Contractor Escalation Solution: Provide solution.

1. Contractor Responsibility: Maintain operating platform, operating system software (with exception of z-series OS), and related operating equipment in operating condition at a level to meet or exceed 99.95%.

1. Measurement: (Total available hours for 30 days – Measurement Exceptions – Time server is unavailable) / (Total available hours for 30 days – Measurement Exceptions )*100=“Service Level Attained”. Total available hours = 24x7x365 for each orderable system for each 30 day period.

Measurement Exception: Measurement Exception: DISA or customer initiated downtime, Vendor Preventative maintenance (not break fix or hardware/software repair) that is appropriately 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.

1. Performance Measure 2: Operating Platform Availability 99.999%

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

1. Availability Objective: 24x7x365 minus Measurement Exceptions (see definition below).

1. Standard: Satisfactory = 99.999%

1. Contractor Escalation Solution: Provide solution.

1. Contractor Responsibility: Maintain operating platform, operating system software (with exception of z-series OS), and related operating equipment in operating condition at a level to meet or exceed 99.999%.

· Measurement: 2A (summary): (Total available hours for 30 days – Measurement Exceptions – Time server is unavailable) / (Total available hours for 30 days – Measurement Exceptions)*100=“Service Level Attained”. Total available hours = 24x7x365 averaged over all five nine’s orderable systems.

1. Measurement 2B(per system): (Total available hours for 30 days – Measurement Exceptions – Time server is unavailable) / (Total available hours for 30 days – Measurement Exceptions)*100=“Service Level Attained”. Total available hours = 24x7x365 for each five nine’s orderable system for each 30 day period.

Measurement Exception: Measurement Exception: DISA or customer initiated downtime, Vendor Preventative maintenance (not break fix or hardware/software repair) that is appropriately 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.

1.

Provide Offeror solution.

Deliverable/s: Processor Performance/Availability of 99.95% or exceed for each operating platform deployed.

6.2.1.1 Subtask 2.2 - Provide 24x7/365 problem escalation/resolution support for hardware, operating system software, VMWare, as well as, any other software required for the Contractor solution to operate, and service management infrastructure.

Provide Offeror solution. At the least, offeror solution will address help desk process, POCs, phone numbers, and escalation chart. Solution will address management level escalation procedures to address any issues that may arise and that may impact operation of the provided services.

Deliverable/s: Processor Performance/Availability of 99.95% or exceed for each processor deployed.

6.2.1.2 Subtask 2.3 - Provide ability to validate and view HW features and components installed.

Provide Offeror solution.

Deliverable/s: Ability to validate and view HW features and components installed.

6.2.1.3 Subtask 2.4 - Provide central management capability and reporting to include hardware utilization, error diagnostics of installed hardware components, and environmental telemetry information to measure power consumption and HVAC impact to CSD facilities and infrastructure.

Provide Offeror solution.

Deliverable/s: Central management capability and reporting to include hardware utilization, error diagnostics of installed hardware components, and environmental telemetry information to measure power consumption and HVAC impact to CSD facilities and infrastructure.

6.2.2 Subtask 2.5 - Maintenance. Contractor shall provide all Preventative maintenance actions as required by the OEM, Predictive and Remedial Maintenance, on all equipment delivered as a part of this contract. Solution will include provider’s ability to 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 current DISA dedicated management network. All maintenance requirements are included in the “utility” pricing.

6.2.2.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.

Provide 24x7x365 problem escalation/resolution support for hardware, operating system software, and capacity management. The contractor will provide a multi-level solution for response time after being notified by the Government, to commence remedial maintenance for hardware, operating system software, VMWare, as well as, 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.

Provide Offeror solution.

Deliverable/s: Response after being notified by Government to commence remedial maintenance for hardware, operating system software, VMWare, as well as, any other software required for the Contractor solution to operate. Processor Performance/Availability of 99.95% or exceed for each processor deployed.

6.2.2.2 Predictive Maintenance. Contractor shall monitor equipment/component performance using diagnostics defined in paragraph 6.2.2.5 for the purpose of identifying whether equipment is operating in accordance with established specifications. This includes hardware, operating system software, VMWare, as well as, any other software required for the Contractor solution to operate. Upon determining equipment/component is about to fail or is operating outside OEM specifications, initiate action to effect repair even though no call for remedial maintenance has been initiated by the managing site service desk or shift supervisor.

6.2.2.2.1 Contractor shall call the managing site service desk to inform them they are coming in for predictive maintenance and request a Form 7 be generated and coordinated with the physical site. Upon arrival at the physical site, the Contractor ’s technician shall report to the site help desk or shift supervisor in order to comply with reporting requirements – see paragraph 13.9, ADPE Maintenance Records/DISA CSD Form 7.

Provide Offeror solution.

Deliverable/s: Processing capacity that delivers a minimum of 99.95% or exceed availability per orderable system with options to provide up to 99.999 % availability per orderable system.

6.2.2.3 Remedial Maintenance. Calls will be initiated by the site help desk or shift supervisor to the Contractor ’s toll free help desk service. Contractor shall respond and repair, or when necessary, obtain required OEM support, in accordance with this specification. The Contractor shall complete remedial maintenance and maintain the processor capacity availability per orderable system IAW paragraph 6.2.2.1. Upon arrival on site, Contractor ’s technician shall report to the site help desk or shift supervisor in order to comply with reporting requirements. This includes hardware, operating system software, VMWare, as well as, any other software required for the Contractor solution to operate.

Provide Offeror solution.

Deliverable/s: Processor Performance/Availability of 99.95% or exceed for each processor deployed.

6.2.2.4 Preventative Maintenance. Preventative maintenance shall be scheduled with the managing site POC, local site support, and the contractor. If deemed necessary by the DISA managing site POC, the preventative maintenance action could require coordination with the customer base of the affected system. In this scenario, the managing site POC will take required actions to schedule an Authorized Service Activity/Authorized Service Interruption and coordinate the date and time with the affected customers and vendor. This includes hardware, operating system software, VMWare, as well as, any other software required for the contractor solution to operate. The Contractor shall submit in writing its preventive maintenance schedule for equipment to the Contracting Officer (KO) within 30 days after contract award. Submission of the schedule shall be in accordance with Contractor format. The preventive maintenance schedule may be modified at no cost by mutual agreement of both parties. The Contractor ’s proposed schedule shall not be less than that recommended by the OEM and shall include, as a minimum, the following information:

· Nomenclature of hardware item.

· Model.

· Serial Number.

· Remote diagnostics and reporting capabilities

· Frequency and duration of preventive maintenance, and type of service to be performed.

6.2.2.4.1 The Contractor shall commence preventative maintenance IAW the approved preventative maintenance schedule within 30 days after award for all maintenance equipment. Preventative maintenance shall be scheduled outside the prime system operating hours.

6.2.2.4.2 If during the course of preventative maintenance, an equipment malfunction is identified, the Contractor shall report the malfunction to the managing site service desk.. The malfunction shall be corrected as a Remedial Maintenance Service (see paragraph 6.2.2.3) and comply with and maintain the processor capacity availability per orderable system IAW paragraph 6.2.2.1 processor capacity availability.

Provide Offeror solution.

Deliverable/s: Processor Performance/Availability of 99.95% or exceed for each processor deployed.

6.2.2.5 Remote Diagnostics. Permanent recorded system errors must be immediately reported to remote service center(s). This includes hardware, operating system software, VMWare, as well as, any other software required for the Contractor solution to operate. The Contractor shall provide written confirmation that reports and remote diagnostics support for applicable equipment exist within 7 calendar days after contract performance start.

6.2.2.5.1 Verbal contact between the local maintenance technician and an off-site support technician is not acceptable for remote diagnostics. There shall be a diagnostic system usable by the remote technician.

6.2.2.5.2 The dial-in feature can be used, but ONLY with site authorization. The feature must be capable of disabling and set up to provide the site the ability to enable the feature upon request from the Contractor .

Provide Offeror solution.

Deliverable/s: Processor Performance/Availability of 99.95% or exceed for each processor deployed.

6.2.3 – Reserved.

6.2.4 Subtask 2.6 - Delivery and Installation. The Contractor shall provide processor hardware necessary to support contract requirements. The Contractor will acquire, install, uninstall, transport, provide the necessary hardware (including cabinets/racks), hardware maintenance, operating systems software, VMWare, as well as any other software required for Contractor solution to operate, and services to support the processor infrastructure associated with the contract.

6.2.4.1 DISA CSD will determine the need for additional processor equipment.

6.2.4.2 Subtask 2.6.1 Delivery of equipment must occur within 30 calendar days of the acceptance of the call order by the contractor.

Provide Offeror solution.

Deliverable/s – Delivery within 30 calendar days of acceptance of the call order.

6.2.4.3 Subtask 2.6.2– Equipment Report. Once an order has been placed, and before delivery, the contractor will send a report containing equipment information to include serial numbers, worldwide names, mac addresses, etc to the installation mail group (csd-installations@csd.disa.mil)). This enables the Government to prepare for equipment receipt. The Contractor shall provide the report 3-10 working days prior to equipment delivery.

Provide Offeror solution.

Deliverable/s: Provide report of equipment information 3-10 working days prior to equipment delivery.

6.2.4.4 Subtask 2.6.3 – Normal equipment delivery/installations/uninstalls. Normal equipment installations should be accomplished during normal business hours, 0600-1800 local time, Monday through Friday.

Provide Offeror solution. At the least, solution must address reduced risk of disruption to the production environment during both initial implementation and during subsequent modifications.

Deliverable/s: Delivery/installation/uninstalls of new orders delivered as required by the Government to ensure no disruption to processing service.

6.2.4.4.1 Subtask 2.6.4 – Under certain conditions, the Contractor may be required to perform delivery/installation/upgrades/uninstalls after normal business hours during evenings and weekends. Although the Government will try to minimize this requirement, the contractor must plan to work after hours, weekends, and or holidays for delivery/installation/upgrade/uninstalls of new or updated orders. All installation requirements should be included in the “utility” pricing.

6.2.4.4.1.1 Under certain conditions, the offeror may be required to be available on “stand by” after hours, weekends, and/or holidays. All “stand by” hours will be included in the technical assistance and consulting support pricing. “Stand by” includes having a field engineer available on-site during a facility power upgrade.

Provide Offeror solution. At the least, solution must address reduced risk of disruption to the production environment during both initial implementation and during subsequent modifications.

Deliverable/s: Delivery/installation/upgrade/uninstalls of new orders delivered as required by the Government to ensure no disruption to processing service.

6.3 Task 3 - Capacity.

6.3.1 Subtask 3.1 - Provide processing capacity that is scalable to adjust to increases and decreases in required workload. This includes but is not limited to, CPU utilization, MIPs, memory utilization, network interfaces (i.e. OSA, HBA, and network interface cards (NIC)), sysplex hardware, channels and channel infrastructure).

Provide Offeror solution.

Deliverable/s: Utility service with ability to increase and decrease as required. Billing must reflect increases and decreases.

In addition, this includes the following:

6.3.2 Subtask 3.2 - Provide provisioning servers to support the infrastructure. These servers must be provided by the Contractor in order to image hardware with the current agreed upon images. Provisioning cannot be accomplished via the wide area network (WAN).

Provide Offeror solution.

Deliverable/s: Solution to locally or remotely provision using DISA and Contractor provided infrastructure with or without WAN capability.

6.3.3 Subtask 3.3 - Provide processing capacity that is priced on a utility (as used) basis and tier size as defined in ATTACHMENT ONE and ATTACHMENT TWO.

Deliverable/s: Utility service with ability to increase and decrease as required. Billing must reflect increases and decreases.

6.3.4 Subtask 3.4 - Provide IBM Mainframe Capacity Backup (CBU) feature for the temporary activation of Central Processors for Disaster Recovery. Annually, DISA routinely conducts 100-140 days of testing for disaster recovery. Testing days will be included in the processor utility service. Invocation fees will be identified and priced separately.

Provide Offeror solution.

Deliverable/s: CBU feature for temporary activation of Central Processors for Disaster Recovery.

6.3.5 Subtask 3.5 - Provide processing capacity for Classified workloads. This must be separate hardware infrastructure including channels and networks, not sharing components as instructed by DISA Security Technical Implementation Guides (STIGs) http://iase.disa.mil/stigs/stig/index.html. This requirement does not have any impact on the security clearance provisions of the solicitation.

Provide Offeror solution.

Deliverable/s: Provide methodology and plan to support provision in classified environments.

6.3.6 Subtask 3.6 - Provide processor capacity that does not adversely impact existing production workload.

Provide Offeror solution.

Deliverable/s: Ability to provision and configure without impact to current production environment and infrastructure.

6.3.7 Subtask 3.7 - Provide processing capacity that is moveable. If this requires the movement of equipment the first move of each piece of equipment shall be at no cost to Government. Movement is defined as the transfer of equipment within the same DISA site or from one DISA site to another DISA site within CONUS and OCONUS. There will be a “Relocation Services” CLIN to support this requirement. Once the free move has been used for specific hardware, subsequent moves are billable via a call order.

Provide Offeror solution.

Deliverable/s: Methodology to relocate processing capacity without disruption to normal operations.

6.3.8 Subtask 3.8 - Capacity requirements can be cancelled at any time at no cost to the Government

Provide Offeror solution.

Deliverable/s: Utility service with ability to increase and decrease as required. Billing must reflect increases and decreases.

6.4 Task 4 - Integration/Interfaces. All equipment provided must work with the existing DISA infrastructure and network.

Provide Offeror solution.

Deliverable/s: Provide components and firmware releases that match DISA requirements and ability to revise/update components to match DISA infrastructure and network changes.

6.4.1 Subtask 4.1 – The Contractor shall provide training/familiarization to DISA system administrators for provided infrastructure; all training requirements should be included in the utility price.

Provide Offeror solution.

Deliverable/s: Methodology for training DISA personnel on technology changes provided in Contractor offering and utility pricing.

6.4.2 Subtask 4.2 – The offeror will provide infrastructure that does not disrupt, conflict,or interfere with DISA's specified enterprise systems management (ESM) architecture. The ESM environment is identified in ATTACHMENT THREE.

Deliverable/s: Interoperability with DISA ESM infrastructure without disruption to current ESM infrastructure.

6.4.3 Subtask 4.3 – The Contractor shall provide solution to ensure all infrastructure components provided are capable of being managed remotely via a dedicated DISA management network.

Deliverable/s: Ability to manage infrastructure remotely and to provide centralized reporting repository.

6.4.4 Subtask 4.4 – The Contractor shall ensure all infrastructure components provided are capable of being backed-up via a dedicated backup network.

Provide Offeror solution.

Deliverable/s: Ability to interface with multiple special purpose networks.

6.4.5 Subtask 4.5 – The offeror will ensure all infrastructure components provided are compatible with and operate seamlessly with DISA’s processor and storage infrastructure. While "boot from SAN" is the preferred technical solution, the Government may have requirements for "Mirrored boot disks" that will need to be provisioned. Configuration will be either "boot from SAN" OR "Mirrored boot disks", but not both.

Provide Offeror solution.

Deliverable/s: Interoperability with DISA processor and storage infrastructure.

6.4.6 Subtask 4.6 – The Contractor shall ensure all infrastructure components provided are coordinated with and concurred by DISA before introduction into the processing environment.

Provide Offeror solution.

Deliverable/s: Methodology to ensure DISA approval is received prior to any component introduction into the processing environment.

6.4.7 Subtask 4.7 - Ensure all components are 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 IT Standard Registry (DISR); maintaining interoperability in heterogeneous environments and with IPv4; commitment to upgrade as the IPv6 standard evolves; and availability of IPv6 technical support.

Provide Offeror solution.

Deliverable/s: Interoperability and support for IPv6.

6.5 Task 5 – Release Management. The Contractor will work closely with the Government to field and test OS releases and upgrade packages. The Government develops standard documentation on version levels in line with change and configuration management programs. The Contractor will package the initial and upgrade OS releases. Initial OS releases are only deployed by the Contractor on capacity hardware; however, 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.5.1 Subtask 5.1 – Package OS.

6.5.1.1 Government will lead the operational acceptance testing with Contractor support. The Contractor does release of new OS's and upgrade packaging for all upgrades with exception of Mainframe OS software which is owned, licensed, and supported by the Government. Server OS software is owned and licensed by the Contractor, with the Government having right to use through the capacity services contract.

6.5.1.2 Upon receipt of a base line 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 CSD infrastructure. Items to be validated by the Government include introduction of new hardware, patches, or firmware versions to the enterprise; new or upgraded software; and tool integration and functionality such as ESM agents, HBSS, Veritas, driver compatibility, IAVA compatibility and level, and STIGing to the current DISA level.

Provide Offeror solution.

Deliverable/s: Initial OS and upgrade OS releases that are enterprise compatible.

6.5.2 Subtask 5.2 - Manage the OS repository, mainframe and server. The Contractor manages the OS software repository and will be used as a central repository for approved OS version baselines. The Government will be able to pull and install the OS upgrade package for testing on capacity hardware in use under this contract, and will return validated OS packages for support of general provisioning and upgrade processes.

Provide Offeror solution.

Deliverable/s: OS Repository and availability for Government to execute OS upgrades.

6.6 Task 6 - Installation/Configuration. All installation, uninstalls, and power-up configuration will be completed by the contractor based upon Government approval. The Government will perform final configuration as required.

Provide Offeror solution.

Deliverable/s: Install, uninstall, provide power-up configuration within 30 days of acceptance of the call order by the contractor.

6.7 Task 7 - Security. Comply with all applicable security directives, including the DoD Directive 8500.1, "Information Assurance (IA)"; DoD Instruction 8500.2, "Information Assurance (IA) Implementation"; DoD Directive 8570.1, Information Assurance Training, Certification, and Workforce Management; DoD Manual 8570.01-M, Information Assurance Workforce Improvement 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.7.1 Subtask 7.1 – The contractor shall ensure personnel are trained and certified. The contractor will be responsible for training and certification testing as well as any certification maintenance requirements. In addition, the contractor will ensure the appropriate Operating System, Operating Environment, or Virtual Environment and Security certifications are met and maintained, in accordance with Government guidance (IAW DoD 8570.01-M Information Assurance Workforce Improvement Program). Certification must be gained within six months of contractor personnel commencing service. Certification reporting will occur bi-annually.

Provide Offeror solution. At the least, Offeror will discuss solution for reporting certifications and certification status of all contractor personnel performing information assurance functions as described in DoD 8570.01-M, Information Assurance Workforce Improvement Program. Provide solution for ensuring certifications are in compliance with the manual and are identified, documented, and tracked.

Deliverable/s: Bi-annual IA certification reporting. (Bi-annual based on rate of employee turnover in IT field and new technologies emerging)

6.7.2 Subtask 7.2 – Provide solution for ensuring all provided hardware and software are in compliance with DISA Security Technical Implementation Guides (STIGs).

Provide Offeror solution.

Deliverable/s: Fully compliant STIG hardware and software.

6.8 Task 8 – Facilities - Racks. The Contractor s must follow the stated standard power and rack details as identified in ATTACHMENT FIVE.

The Government reserves the right to choose the basic rack solution or the “spot” cooling rack solution at the time of order based on workload and infrastructure requirements specified at the time of the order.

6.8.1 Subtask 8.1 - Provide solution for standard rack and power specifications as detailed in ATTACHMENT FIVE

Include discussion of the following:

6.8.1.1 Contractor shall allow the Government the flexibility to modify rack configurations as necessary to install cooling scheme, this allows for cooling infrastructure modeled per site dynamics by the Government.

6.8.1.2 Contractor shall include ancillary equipment such as MPDUs, grommets, blanking panels.

6.8.13 Equipment will be connected to BAS system for control and monitoring.

6.8.1.4 Grounding capability must be provided.

6.8.1.5 Each server/enclosure/cabinet must include some form of Cable Management that allows for the server/enclosure/cabinet to slide on the rails without binding or causing interference to airflow.

6.8.1.6 Offeror will also include any manufacturer/vendor equipment required to meet their own mounting and/or warranty standards.

Provide Offeror solution.

Deliverable/s: Provide standard racks with configurations IAW DISA standards for rack and power specifications.

6.8.2 Subtask 8.2 - Provide solution for high density cooling configurations. Include discussion of the following:

6.8.2.1 Contractor must allow the Government the flexibility to modify rack configurations as necessary to install cooling scheme, this allows for cooling infrastructure molded per site dynamics by the Government.

6.8.2.2 Contractor must include ancillary equipment such as MPDUs, grommets, blanking panels.

6.8.2.3 Equipment will be connected to Building Automation System(BAS) for control and monitoring.

6.8.2.4 Grounding capability must be provided.

Provide Offeror solution.

Deliverable/s: Provide high density cooling solution upon order.

6.9 Task 9 - CSD “Green” Initiatives. The Contractor will support CSD "green" initiatives by providing data, reports and, analysis of environmental telemetry data for contractor -provided hardware to validate and monitor facilities impact to data center environment. This information would be utilized to monitor actual power requirements, heat generation and cooling load to data center and facilitate a partnership between contractor and CSD Infrastructure planning for management of facilities requirement. Provide method and plan Contractor proposes to provide environmental telemetry information and minimizing impact to CSD facilities and infrastructure. The Contractor should provide description of metrics delivered and ability to interface with CSD standard tools for event correlation.

6.9.1 Subtask 9.1 – Provide quarterly reports for environmental telemetry data for contractor-provided hardware.

Provide Offeror solution.

Deliverable/s: Provide quarterly reporting and supporting data to demonstrate power consumption and heat generation for Contractor -supplied hardware solutions

6.9.2 Subtask 9.2 – Provide analysis for power/heat load mitigation.

Provide Offeror solution.

Deliverable/s: Provide quarterly analysis of environmental telemetry data for contractor-provided hardware and supporting data to demonstrate methodology for power/heat load mitigation.

6.10 Task 10 - Technology Refresh Program. The Technology Refresh Program (Tech Refresh) is a consolidated DISA effort to select, acquire, and install processor hardware and software on a scheduled basis to prevent obsolescence and increase data processing and functionality within DISA’s NIPR and SIPR networks.

Tech Refresh Program is designed to replace aging and out of date processors hardware in order to minimize obsolescence in advance of loss of service or hardware failure. DISA estimates the Tech Refresh Program will replace the oldest processor equipment as required, but generally processor hardware will have a 3 year service life. The Government can decide to refresh hardware based on functions and technology updates, at any point in time during the first five years. This is not common place but the flexibility must be available. Likewise, technical or cost efficiencies and advantages on keeping hardware for longer than 3 years should be clearly defined. Without a viable Tech Refresh Program, DISA will be at risk due to the fact that the processors equipment cannot be serviced beyond its lifecycle. No new equipment will be ordered, or added to the list, by the incumbent in the option years since they will be treated as a transition and exit period. It is the Government’s desire that the option years will be exercised for sustainment only. However, the Government can place new orders on the new contract in the extension years should the need arise for the following purposes the existing contract ends, the equipment is technically refreshed, or the equipment is no longer required by the Government.

Discuss any technical or cost efficiencies and advantages, if any, for keeping hardware longer than 3 years.

Deliverable/s: Support of CSD Tech Refresh Program.

6.11 Task 11 - Transition and Exit Strategy. The transition and exit strategy will begin at the end of the base contract. The Governments goal is that there will be a follow on contract in place by the end of the base period. It is the Governments desire that the option years will be exercised for sustainment of all orders. However, the Government can place new orders against the new contract in the extension years should the need arise for the following purposes: the existing contract ends, the equipment is technically refreshed, or the equipment is no longer required by the Government. At the end of the option years of the contract, or cancelling a call order, the Contractor shall be responsible for the removal of all their Contractor owned equipment related to this contract at no cost to the Government.

Deliverable/s: Removal of all contractor owned equipment related to this contract at no cost to the Government.

6.12 Task 12 - Removal of Equipment. The contractor shall conduct any necessary uninstallation and removal of hardware items on this contract upon request by the Government both during and at the end of the contract, at no cost to the Government. Removal of all vendor equipment will be coordinated with the site Accountable Property Custodian (APC) or Property management group.

Deliverable/s: Uninstalls and removal of hardware items on this contract upon request by the Government at no cost to the Government.

6.13 Task 13 - Quality Program. Ensure contractor quality program uses Information Technology Infrastructure Library (ITIL) fundamentals.

Provide Offeror solution. At the least, Offeror will discuss established processes for Change Management, Configuration Management, Asset Management, and Release Management and how the processes will integrate into DISA processes.

Deliverable/s: Methodology for ensuring established quality processes are used for Change Management, Configuration Management, Asset Management, and Release Management and integration is seamless in the DISA processes.

6.13.1 Industry Standard. Implementation of components of the Information Technology Infrastructure Library (ITIL) will improve overall management of DISA’s processor infrastructure. Companies and Government agencies that have followed the methodologies of these models have improved their service and reliability of their processor infrastructure reducing their long-term costs. The following ITIL principles should be included in the contract:

· Change Management,

· Configuration Management,

· Asset Management,

· Release Management.

6.13.2 Change Management. An established process for handling change to the processor infrastructure on a continual basis shall be developed.