A01-Solicitation_AMD_03.pdf

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

a. The purpose of this amendment is to remove FAR Clause 52.211-6 and to update Section L.

b. See Summary of Changes.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 7

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

16C. DATE SIGNED

BY 03-Feb-2016

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 W91RUS-16-R-0002

X 9B. DATED (SEE ITEM 11)

21-Dec-2015

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 is extended, X 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

03-Feb-2016

CODE

ACC-APG

MR. DANIEL OCTAVIANO 2133 CUSHING ST BLDG 618

FT HUACHUCA AZ 85613

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W91RUS-16-R-0002

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been added by full text:

SECTION L (REV 2)

Section L (Revision 2) Section L - Instructions, Conditions and Notices to Bidders

1. Instructions for Written Submittals: The Offeror shall submit its offer, individually titled, as set forth below via email to the Contract Specialist, Dan Octaviano, daniel.j.octaviano.civ@mail.mil no later than 10:00 AM (MST) 19 February 2016. Due to enterprise email file size restrictions, the Offeror may submit as separate emails.

It is requested that all questions pertaining to this solicitation and its attachments are sent in a Microsoft Word 2007 document via e‐mail to, daniel.j.octaviano.civ@mail.mil no later than 1:00 pm on 20 January 2016. The applicable Statement of Objectives (SOO) and/or Functional Requirements Document (FRD) paragraph number and solicitation reference shall precede all questions.

2. Proposal submission shall be as follows:

VOLUME

NUMBER CONTENTS

MAXIMUM

PAGES TITLE/FORMAT

1 GENERAL* N/A GEN1.DOC/GEN1.PDF

2 TECHNICAL 10 MS1.DOC

3 PRICE PROPOSAL** N/A PRICE.XLS/COST1.DOC

PAST PERFORMANCE

SUMMARY *** PAST1.DOC

*For any documents that need to be scanned and submitted as part of the proposal (i.e., SF 33 cover page, documents with signatures), ".PDF" format as prescribed above is encouraged, with the remaining narrative portions submitted as ".DOC" format.

**Narrative portion of the Price Proposal shall be submitted in ".DOC" format, and supporting price information for Schedule B (i.e., individual breakout with loadings and formulas) shall be submitted in ".XLS". During the evaluation, the Government may need to manipulate the worksheets, so worksheets should not be write protected. If they are write‐protected, then the offeror shall provide the Government with the write‐protection password.

***Past Performance Summary is limited to three pages per referenced contract.

a. The Technical Support Section must not contain any reference to the proposed costs/price.

b. Page Limitations & File Format: The Technical Support Section shall be limited to ten (10) pages. This is exclusive of Cover, Title Page, Table of Contents, and Table of Figures. The Technical Support section shall be submitted in Microsoft Word. The Pricing section shall be submitted in contractor’s own format using Microsoft Excel for calculations and Microsoft Word for any narrative. For the electronic submission, Microsoft Office 2007 products shall be used (acceptable MS Excel file extensions are .xls or .xlsx and acceptable MS Word file extensions are .doc or .docx).

c. The term “pages” includes pullout drawings, tables, diagrams, charts, indices, and tables. Paper size shall be 8‐ 1/2 x 11 inches, one sided typed. Print shall be single‐spaced with one‐inch margins on each side (top, bottom, left, right). Tables, charts, graphics, drawings, and diagrams will have a minimum font size of 10 point. All other narrative shall have a minimum font size of 12 point. Pullout drawings will be numbered and counted as multiple pages in relation to the 8‐1/2 x 11 inch size limitation. The pages composing the complete Technical Support proposal shall be numbered consecutively without regard to individual sub‐factors. Information not contained within the above limitations will not be evaluated.

d. The offeror shall include a statement indicating whether or not the Offeror intends to make use of any proprietary or patent information. In the event that use of such information is anticipated, the specific areas of use by the Offeror and its subcontractors must be clearly defined, including whether limited or unlimited rights are applicable. The offeror shall indicate the price to the Government for acquisitions of each and all proprietary information identified in the proposal.

e. The Offeror must submit a complete response to this solicitation using the sequence and format instructions provided in section 4. All information pertaining to the Technical and Price sections, shall be confined to the appropriate proposal section in order to facilitate independent evaluation. Proposals shall be clear and concise, logically assembled (with all pages appropriately numbered) and indexed and cross‐indexed to applicable parts of the Performance Work Statement or Request for Proposal, as appropriate. To reduce proposal size, the Offeror shall confine submission to essential matters sufficient to define the proposal, and provide an adequate basis for evaluation. No price information shall be presented in any part of the proposal except the price proposal. Proposal sections shall not contain classified data. NO ZIPPED FILES are permitted.

3. Submittal Contents (Volume 1 – General):

Proposal Transmittal Letter. A letter formally transmitting the proposal shall include the following:

a. Statement of Compliance. The Offeror shall include a statement indicating complete compliance with the solicitation, or detailed analysis of any objections, exceptions, contingencies, or additions.

b. Proprietary Information. The Offeror shall include a statement indicating whether the Offeror intends to make use of any proprietary or patent information.

c. Joint Venture/Teaming Arrangements. The Offeror shall provide, if applicable, a summary describing the Joint Venture/Teaming Arrangement established for this RFP and documentation evidencing the legal relationship among the joint venture/teaming parties.

d. Disclosure of Potential Organizational Conflicts of Interest. The Offeror shall disclose complete information of any work performed by their company that is in any way associated with the contemplated acquisition or which could result in a potential organizational conflict of interest.

e. Solicitation Documents. An authorized official of the firm shall sign the SF 1449. PDF versions of the signed documents shall be submitted as part of the electronic submissions. No changes of alterations shall be made to these sections of the solicitation. Offeror shall complete all the fill‐ins and signature blocks for the RFP items indicated below.

i. Section A. Standard Form 1449 (SF 1449), Solicitation, Offer and Award for Commercial Items. The Offeror shall submit a completed and signed SF1449.

ii. Representations, Certifications and Other Statements of Offerors (FAR representations, certifications and other statements of) shall be submitted on‐line in accordance with solicitation provision 52.204‐8.

iv. DFARS representations, certifications and other statements of Offerors shall be included with the solicitation documents and 252.209‐7999.

4. Factor 1 –Technical (Volume 2): This section shall be sufficiently specific, detailed, and complete as to demonstrate clearly and fully that the Offeror has a thorough understanding and knowledge of the complexities inherent in the development of this technical solution. Statements that the Offeror understands, can, or will perform the requirements of the SOO/FRD without supporting information or narratives are inadequate.

Paraphrasing the SOO/FRD or parts thereof, is similarly inadequate, as are phrases such as “standard procedures will be employed” or “well‐known techniques will be used.”

This section shall be written such as to enable evaluators to make a thorough evaluation as to whether the solution proposed adequately respond to the specific Government requirements. This part shall indicate the contractor’s capability in meeting the requirements by providing the information required below. Proposal shall be presented in narrative format, in a clear and logical manner. It must be confined to essential matters sufficient to permit a thorough analysis.

a. Technical Approach: The technical approach should identify the methodology and analytical techniques you will use to fulfill the requirements for each of the three subfactor functional areas. The technical approach shall include quality control. Proposals shall address the following areas:

Subfactor 1 – Integrated Solution. The – Integrated Solution evaluation provides an assessment of the offeror’s capability to satisfy the government’s requirements. To be rated “acceptable” an offeror’s proposal will demonstrate their understanding of and its ability to execute the functional requirements described Functional Requirement’s document as outlined below:

1. Pooled resources. The offeror’s solution will have the ability to execute flexible pooling of computing (processor and memory), storage, networking, and software resources. The offeror’s solution will have computing, storage, and network resources grouped in the same infrastructure environment to allow for reallocation of those resources on demand. This pooling helps deliver greater utilization and efficiency and is powered by virtualization, which abstracts the platform from the physical infrastructure. Multiple customers or multiple organizational units can share pooled resources, resulting in higher resource utilization and efficiency for both planners and users.

2. Customer Self-service. The solution will enable provisioning of basic resources for a customer such as services, virtual machines and user accounts without needing IT support intervention.

3. Usage Monitoring and auditing. The offeror’s solution will have the ability to capture metrics on resource consumption, report on installed services, and record data for comparative baseline analysis will aid in the efficient management of the enterprise across multiple sites.

4. Converged/Hyper-converged architecture goals. The offeror must have:

a. Support for multiple diverse workloads

b. Full end-to-end high-availability

c. 100% virtualization

d. 100% automation

e. Self Service Portal for Administration and Guests

f. Sub-system scale-out for the following:

1. Compute

2. Storage

3. Networking

g. Hardware platform independence

h. Just-in-time hardware provisioning

i. Hypervisor managed from a centralize location

1. Hypervisor is able to be managed by other vendor hypervisor

2. Hypervisor dynamic resource allocation

3. Rapid and High elasticity for adding VM’s

5. Faster deployment. The offeror must provide end-to-end architectural and deployment guidance. The offeror’s solution must provide enhanced functionality and automation through deep knowledge of infrastructure. The offeror’s solution must have integrated management for VM and infrastructure deployment at the enterprise level.

6. Shipment of Single Integrated System. The offer must provide a single integrated system in a shipment per installation site.

7. Lower total cost of ownership. The offeror must provide near-zero downtime with exceptional fault tolerance and high availability. The offeror must provide significant reduction in power, space and HVAC required for their solution versus traditional server centric solutions.

8. Elasticity and the Perception of infinite capacity. The offeror’s solution must provide that from the user’s perspective, services should appear to have infinite capacity. End users can consume as much or as little of the service as needed, just as they consume electricity. This principle helps achieve greater balance between the cost of unused capacity and the desire for agility. The offeror’s solution must include the ability to add new resources and services that is flexible and customizable to each organization’s mission need. Operations can better handle surging demands and peak usage through the tailoring of resources from computing power, virtual machines, storage, and bandwidth utilization.

9. Perception of continuous availability. The offeror’s solution must provide that from the user’s perspective, services should always be available when needed. The consumer should never experience an interruption in IT services, even if failures occur within the cloud infrastructure. The offeror must provide the ability to achieve this continuous availability, the private cloud architecture must deliver a highly automated environment in which infrastructure redundancies, such as failover clustering, are complemented by intelligent automation and management capabilities.

10. Minimum specifications. The offeror’s solution must provide the following minimal specifications:

a. Compute.

a. Servers: 4-64 (4 Cluster nodes)

b. CPU: dual socket 10 cores for a total of 20 cores (20 pCPU/320 vCPU)

c. RAM: 256 GB per node

d. Network 10 GbE – 3 Total (2 for all traffic, 1 for management)

e. TPM encryption 2.0 or later

b. Storage:

a. Array: Shared array with cloud fabric, 70 TB

b. Storage connectivity: Connectivity for all hosts with host and switch redundancy

c. Network:

a. Ports: 10 GbE connectivity

b. Sufficient 10 GbE connectivity/port density to support all hosts with host and switch redundancy, support for VLANs(tagging, truncking, etc.)

Subfactor 2 – Implementation/Interoperability. The Implementation/interoperability evaluation provides an assessment of the offeror’s capability to satisfy the government’s requirements. To be rated “acceptable” an offeror’s proposal will demonstrate their understanding of and its ability to perform implementation at each site and post implementation tasks as outlined below:

1. Reduced risk. The offer must provide documentation to ensure that the equipment is tested end-to-end interoperability for computing, storage, and networking. The offeror’s solution must have a high degree of service availability through automated load balancing.

2. Implementation. The offeror must deliver, configure and integrate into the site architecture a solution to include site network connectivity, training and physical setup. Management of the virtual capacity will be performed by the Theater Regional Cyber Centers (RCC). The offeror must provide sufficient connectivity, configuration, documentation and training for the RCCs to accept responsibility for the solution.

3. Integration. The offeror must provide the ability to integrate both at the hardware and software level with currently implemented solutions within the enterprise. This includes but is not limited to JRSS, NETOPs toolset, Active Directory and Microsoft System Center 2012r2.

4. Interoperability. The offeror must provide the ability to operate with other deployed solutions within the Army to form a seamless view of virtual environment regardless of the hardware vendors in support of the Software defined infrastructure. This includes but is not limited to the ability to see storage from different vendors and present it to the environment as a usable resource.

Subfactor 3 - Support. The Support evaluation provides an assessment of the offeror’s capability to satisfy the government’s requirements. To be rated “acceptable” an offeror’s proposal will demonstrate their understanding of and its ability to provide support for the fielded solution as outlined below:

1. Warranty. The offeror must provide a warranty for the hardware to include next business day replacement of failed components for a minimum of 3 years.

2. Any supporting licenses not otherwise included to the government under separate agreements will be provided by the offeror.

NOTE: DO NOT submit a Quality Control Plan with your proposal. A comprehensive Quality Control Plan supporting the RFQ requirements will be required after contract award.

5. Factor 2 ‐‐ Price Proposal Section (Fixed Price with Reimbursable Line Items) (Volume 3): Offerors shall submit pricing for all Contract Line Item Numbers (CLINs) as formatted in SF1449 continuation sheet. This part shall include a spreadsheet in the contractor’s own format that details the labor calculation of its proposed monthly fixed prices for services. The Offeror shall submit pricing for each Contract Line Item Number (CLIN) which requires unit prices in order to be considered for award. The Offeror shall submit the total price for CLINs as formatted in SF1449 continuation sheet. The Offeror shall enter the proposed unit pricing in U.S. Dollars (rounded to the nearest cent and no more than 2 decimal places).

6. Factor 3 ‐‐ Past Performance (Volume 4): Submit a narrative no more than three pages describing up to three relevant contracts that are similar in size, scope, and complexity that you have performed as a prime contractor or subcontractor during the last three years. The contractor will demonstrate its experience by current and recent performance of contracts for customers such as Federal Government, agencies of State and local government, or commercial customers. Information pertaining to each of the contracts shall be provided (e.g., description of service, type of contract, period of performance, contract number and/or name, dollar value).

The following have been deleted:

SECTION L (REV 1)

52.211-6 Brand Name or Equal AUG 1999

(End of Summary of Changes)