HC1019-19-R-0003_Amendment_0001.docx

HC101919R0003

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 31-May-2019 04:30 PM to 05-Jun-2019 04:30 PM.

SUPPLIES OR SERVICES AND PRICES

CLIN 0001

The CLIN extended description has changed from:

To:

Tasks 6.1-6.10

CLIN 0002

The CLIN description has changed from Task 6.8 OPTIONAL to RESERVED.

The pricing detail quantity has decreased by 12.00 from 12.00 to 0.00.

The unit of issue Months has been deleted.

The option status has changed from Option to No Status.

CLIN 0003

The CLIN description has changed from Task 6.9 OPTIONAL to RESERVED.

The pricing detail quantity has decreased by 12.00 from 12.00 to 0.00.

CLIN 0004

The CLIN description has changed from Task 6.10 OPTIONAL to RESERVED.

The pricing detail quantity has decreased by 12.00 from 12.00 to 0.00.

CLIN 1001

Task 6.1-6.7

CLIN 2001

CLIN 3001

CLIN 4001

DELIVERIES AND PERFORMANCE

The following Delivery Schedule item for CLIN 0002 has been changed from:

POP 30-SEP-2019 TO

29-SEP-2020

FOB: Destination

POP 30-SEP-2019 TO

The following Delivery Schedule item for CLIN 0003 has been changed from:

POP 30-SEP-2019 TO

POP 30-SEP-2019 TO

The following Delivery Schedule item for CLIN 0004 has been changed from:

POP 30-SEP-2019 TO

POP 30-SEP-2019 TO

The following have been modified:

ADDENDUM TO 52.212-1

Addendum to 52.212-1(b), Submission of Offers is tailored as follows:

(b) Submission of offers:

(12) Other Instructions

(i) General Information

(A) Points of Contact: The contracting officer (KO) and contract specialist (CS) are the sole points of contact for this procurement. Address any questions or concerns you may have to the KO/CS. Written requests for clarification must be sent to the KO/CS at katherine.a.jackson23.civ@mail.mil and kyle.s.kiyonaga.civ@mail.mil.

(B) Discrepancies: If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the KO in writing with supporting rationale. The Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

(C) Electronic Reference Documents: All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

(D) Communications: Exchanges of source selection information between Government and offerors will be controlled by the KO and CS. Email will be used to transmit such information to the offeror and will include “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line.

(ii) Offerors are requested to submit a written technical proposal and a price proposal in response to the attached Performance Work Statement (PWS) and Quality Assurance Surveillance Plan (QASP) (See Attachment 1). Offerors must complete Blocks 6, 7, and 8 of the DD Form 254 (See Attchment 2) with the appropriate information for their companies and any subcontractors (when applicable). The completed DD Form 254 must be submitted with your proposal. Information on submission of technical and price proposals is provided below. The proposal shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of statements asserted in the proposal. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume the Government has no prior knowledge of their facilities and capabilities and will base its evaluation on the information presented in the offeror's proposal. The offeror's proposal must include all data and information requested by the RFP and must be submitted in accordance with these instructions. The proposal should sufficiently address the requirements as stated in the PWS. Non-conformance with these instructions may result in removal of the proposal from further evaluation.

(iii) IAW DISA Acquisition Regulation Supplement (DARS), Organizational and Consultant Conflict of Interest (OCCI), each offeror shall specifically identify in its proposal whether or not any potential or actual OCCI, as described in Federal Acquisition Regulation (FAR) Subpart 9.5, exists for this instant procurement. If the offeror believes that no OCCI exists, the OCCI response shall set forth sufficient details to support such a position. If an offeror believes that an actual or perceived OCCI does exist on the instant procurement, the offeror shall submit an OCCI plan with the proposal, explaining in detail how the OCCI will be mitigated and/or avoided.

(iv) Page limitations, if applicable, are identified below and will be treated as maximums. If exceeded, excess pages will not be read or considered in evaluation of the proposal. The following items will not be considered when calculating page limits: cover page, table of contents, glossary, executive summary, generic resumes, past performances, and OCCI mitigation plans and Section 508 compliance. In the event any evaluation notices are issued, page limitations may also be placed on those. Page limitations shall not be circumvented by including inserted text boxes/pop-ups or internet links to additional information; such inclusions are not acceptable and will not be considered part of a proposal. The Government reserves the right not to consider for award any proposal that does not adhere to the administrative requirements of this RFP.

(v) Organization/Number of Copies/Page Limits. The offeror shall prepare the proposal as set forth in the Proposal Organization Table below. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified. The contents of each proposal volume are described in the information to offerors paragraph as noted in the table below. To the greatest extent possible, each volume shall be written on a standalone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Each volume may contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing may be used to identify sections.

Additionally, each volume may contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

Table 1 Proposal Organization

Number

(vi) Electronic Offers. The offeror shall submit volumes I through V in electronic format via email and must include “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. Each volume shall be a separate file. If files are compressed, the necessary decompression program must be included. Proposals shall be submitted to the KO/CS identified below:

Katherine A. Jackson (Contract Specialist) – katherine.a.jackson23.civ@mail.mil Kyle S. Kiyonaga (KO) – kyle.s.kiyonaga.civ@mail.mil

(vii) Proposal Organization:

(A) Volume I Executive Summary. In the executive summary volume, the offeror shall describe the significant attributes and theme of its proposal. It should be concise, to include addressing any significant risks, and highlighting any key or unique features, excluding price. Any summary material presented in the Executive Summary shall not be considered as meeting the requirements for any portions of other volumes of the proposal. Include a master table of contents for the entire proposal.

(B) Volume II – Technical/Management. The technical/management volume should be specific and complete, and will be evaluated against the technical/management subfactors defined in FAR 52.212-2, Evaluation – Commercial Items. The technical portion of the proposal is to be submitted as a Microsoft (MS) Word 2007 document. The page format shall have a 1 inch margin using no smaller than an 11 point Ariel, Times New Roman, or Courier New font for all text to include any text contained in a table. The file size of each document shall not exceed 2MB. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying the factors/subfactors.

In the Technical/Management volume, address your proposed approach to meeting or exceeding the minimum performance or capability requirements of each technical/management factor/subfactors, as well as any risks in your proposed approach in terms of technical/performance, price, and/or schedule. Address any technical/management risk by identifying those aspects of the proposal you consider to have the potential for disruption of schedule, increased cost, poor performance, the need for increased Government oversight, and/or the likelihood of unsuccessful contract performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (e.g., PWS/SOW or specification requirements), whether or not those requirements are identified as subfactors. Propose a realistic "workaround" or risk mitigation for identified risks that will eliminate or reduce risk to an acceptable level. Identify any new risks introduced by such risk mitigation.

Volume II - Technical/Management shall be organized as follows:

-Table of Contents -List of Table and Drawings -Glossary -Subfactor One -Subfactor Two -Subfactor Three -All other aspects of the PWS

(C) Volume III – Price. The price proposal spreadsheet shall be submitted in MSExcel 2007 format. Table of contents and any other information is to be submitted in MS Word. All formulas shall remain present in the spreadsheet for verification. The file size of each document shall not exceed 2MB. Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your price. All information relating to the proposed price, including all required supporting documentation must be included in the section of the proposal designated as the Price Volume. The eventual awardee will be authorized to invoice monthly for all approved travel costs incurred and approved by the COR. Under no circumstances shall the information and documentation from the Price Volume be included elsewhere in the proposal other than Volume III, Price Volume and Volume V, Contract Documentation, which includes CLIN pricing.

See Attachment 3 RFP CLIN Pricing Worksheet

The labor rates input into the Pricing Worksheet shall include fully-burdened hourly rates for each labor category that may be required throughout the life of this effort. All labor related costs are part of the fully burdened labor rates and shall be priced at the Government or Contractor site IAW the PWS. Labor and labor related costs shall not be reimbursed as an ODC.

Government Site Fixed Price Rates. When performing at Government sites, the contractor shall furnish fully-burdened personnel rates.

Contractor Site Fixed Price Rates. Contractor site rates shall also include contractor provided facilities, furniture, equipment, supplies, tool kits, employee training (which includes training course costs/fees, related travel and location travel costs), and overhead amounts required for the work for Contractor Site Rates. This includes but is not limited to: telephones, computers, facsimile machines and their telecommunications lines, copiers, personal computers, postage (to include courier services such as Federal Express), ordinary business software, such as word processors, spreadsheets, graphics, etc., normal copying and reproduction costs.

Volume III – Price shall be organized as follows:

-Table of Contents -Pricing information, Labor Rate Table and supporting data, to include estimating methodology.

-Other information such as Government Furnished Property/Government Furnished Equipment (GFP/GFE), long lead costs, termination costs, development/production schedule, inflation rate summary and explanation, life cycle cost, and special tooling/test equipment. In response to the solicitation, no terms, conditions, or assumptions will be entertained. If terms, conditions, or assumptions are included in a proposal, the proposals may be excluded on grounds that it failed to comply with the solicitation’s instructions.

(D) Volume IV – Past Performance. Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 4 Past and Present Performance Information.

(E) Volume V - Contract Documentation. The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file.

1. You must complete blocks 30 a, b, and c of the SF Form 1449 and return this form with your proposal. Signature by the offeror on the SF1449 constitutes an offer, which the Government may accept.

2. You must provide completed pricing information in the CLIN spreadsheet.

3. You must provide FAR 52.212-3 Alt I (completed representations, certifications, acknowledgments and statements).

4. Complete Block 6, 7 and 8 of the DD Form 254 and return with your proposal.

5. Provide the completed Past Performance References sheet.

6. OCCI Mitigation Plan or a statement that OCCI does not exist.

7. Authorized Offeror Personnel. Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government. Contractor Point of Contract information will be used for the clause at G1, Points of Contact.

8. Company/Division Address, Identifying Codes, and Applicable Designations. Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other locations. List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

52.212-1(c), Period for Acceptance of Offers is tailored as follows:

(c) Period for acceptance of offers. The offeror agrees to hold the prices in its offer firm until September 30, 2019 or completion of any protests unless otherwise withdrawn. The offeror shall make a clear statement in the proposal documentation volume that the proposal is valid through this date.

(End of provision revisions)

ADDENDUM TO 52.212-2(A)

Addendum to 52.212-2(a), Evaluation-Commercial Items is tailored as follows:

a. Basis for Contract Award Award will be made to the responsible offeror whose proposal is determined to represent the overall best value to the Government using a best value tradeoff evaluation process. The technical proposal should include all information the offeror wants the Government to consider and evaluate regarding its ability to perform all required tasks and conform to all required terms and conditions. To be eligible for award, the offeror’s proposal must sufficiently address all aspects of the PWS. Failure to comply with the terms and conditions of the solicitation may result in the offeror being ineligible for award.

With regard to the best value analysis for the award decision, the below evaluation factors and subfactors will be used in the best value trade off analysis. Section 508 Accessibility Standards do not apply to this requirement.

b. Evaluation Factors and Subfactors

(1) The following evaluation factors and subfactors will be used to evaluate each proposal.

Factor 1: Technical/Management

(a) Subfactor 1: Technical The contractor demonstrates a plan to fully meet or exceed the following subtasks from the Performance Work Statement (PWS):

· Task 3, Subtask 1 Contractor will architect and engineer a Virtualized Multi-Tenant Data Center and various secure hybrid Cloud Computing solutions, virtualized storage, networks, and desktops in the Pacific Theater or other theater-wide DoD deployments to include server-accelerating RAM-based VDI data storage, with server RAM as the primary storage tier, virtualized server acceleration and SecureView. Provide oversight on all engineered solutions and architectural diagrams.

· Task 3, Subtask 21 Transform client experience from physical to Desktop as a Service (DaaS) utilizing a VMware vSphere, VMware Horizon View, Cisco UCS and Nexus environment. Provide configuration recommendations on current environment to provide expansion capabilities based on mission needs and projected growth. Provide backend tiered-storage solutions on EMC VNX series, Elastic Cloud Storage (ECS), Data Domain and XTremIO arrays to meet expected application performance.

(b) Subfactor 2: Technical The contractor demonstrates a plan to fully meet or exceed the following subtasks from the Performance Work Statement (PWS):

· Task 9, Subtask 1 Architect and engineer Client Hosted Virtualization (CHV) on a designated SecureView Client in accordance with AFRL processes and procedures and deploying Hypervisors that are used to logically split a physical machine into many independent virtual machines.

· Task 9, Subtask 3 Engineer and deploy SecureView Outer and Inner VPN Concentrators, workstations which include a SIPR Thin VM, NIPR Thin/Thick VM, Inner VPN Appliance (StrongSwan), Outer VPN Appliance (AnyConnect), and Network Driver Appliance.

(c) Subfactor 3: Management The contractor's proposal provides the appropriate mix of skill levels, and demonstrates a comprehensive management approach that ensures fully-trained, top-quality personnel are provided to meet all requirements of the PWS. In addition to any information provided in the technical proposal, in evaluating offerors' proposed staffing plans, the Government will review sanitized versions of offerors' price proposals (i.e., removing prices, but leaving in hours and labor categories). Contractor's proposal shall include a staffing plan that identifies each position, supplemented with generic resumes for review.

Factor 2: Past Performance

Offerors will be evaluated on performance under existing and prior contracts for similar products or services. Offerors shall submit no more than three recent past performance efforts for evaluation. Recent efforts are those which have been performed during any portion of the last three years, including those efforts currently being performed. Recent efforts submitted will be reviewed for relevancy and quality, and then an overall confidence assessment will be given for the past performance factor IAW the attached evaluation tables. Cited past performance efforts shall not exceed two pages for each past performance effort. A current point of contact for each past performance effort shall be provided by completing the embedded Past Performance Reference sheet and including it with your proposal. References other than those identified by offerors may be contacted by the Government, and the information received may be used in the past performance evaluation. The Government reserves the right to obtain information relative to present and past performance on its own, in addition to that provided by the offeror. Past performance information may be obtained through the Contractor Performance Assessment Reporting System (CPARS), through interviews with program managers on past efforts, or any other sources known to the Government.

See RFP Attachment 4 Past Performance References

Factor 3: Price

(a) Price proposals will be evaluated to determine if they are reasonable and complete. The offeror shall submit pricing for the base period and all option periods, including option pricing for an additional 6-month period that may be authorized IAW FAR 52.217-8. The Government reserves the right, but is not obligated, to conduct a realism analysis. The total evaluated price will consist of the offeror’s proposed price for the base period, all option periods, option pricing for an additional 6-month period that may be authorized IAW FAR 52.217-8.

Price proposals will be evaluated to determine if they are reasonable and complete. The Government will determine price reasonableness using price analysis techniques defined in FAR 15.404. The Government will determine completeness of the offeror’s quote by verifying that all solicitation requirements have been priced, figures are correctly calculated, and prices are presented in a clear and useful format. The price quote shall be submitted as a separate document from the technical/management portion and utilizing the format provided in Attachment 5, CLIN Pricing Worksheet. The offeror shall submit pricing for the base period and all option periods, including option pricing for an additional 6-month period that may be authorized IAW FAR 52.217-8 . See FAR 52.217-8 which authorizes the Government to require continued performance of any services within the limits and at the rates specified in the contract. The pricing proposal shall include a separate line item for the additional 6-month period IAW FAR 52.217-8. These prices shall be identical to the quoted pricing in the 6 months prior to expiration of the base period, or the final option period, if option periods are present. The total evaluated price will consist of the contractor’s proposed price for the base period, all option periods, the option pricing for the additional 6-month period, and surge pricing as requested below. The Technical/Management Approach Factor is more important than the Price Factor

Completeness: The Government will determine completeness of an offeror’s price proposal by verifying that all solicitation requirements have been priced, figures are correctly calculated, and prices are presented in a clear and useful format.

Reasonableness: Proposals will be evaluated using one or more of the techniques defined in FAR 15.404 to determine price reasonableness.

(b) Offerors should ensure price proposals include detailed information regarding the resources required to accomplish the task (e.g., labor categories, labor hours, number of employees for each labor category, rates, etc.).

(c ) Due to the likely inability of any offeror to accurately estimate travel and associated with this requirement, the Government is providing plug numbers to be used by all offerors when proposing ODCs. Offerors are instructed to propose plug numbers for Travel ODCs in the following EXACT amounts, however actual travel shall be authorized by the COR in writing prior to performance and will be paid IAW FAR Part 31.205-46.

Travel ODCs Base Year: $49,600.00 Opt Year 1: $49,600.00 Opt Year 2: $49,600.00 Opt Year 3: $49,600.00 Opt Year 4: $49,600.00 6 Month Extension: $24,800.00 Total: $272,800.00

These EXACT amounts shall include all audited markups and burdens and shall not be rounded or adjusted based upon independent decisions regarding actual anticipated ODCs. A proposal that fails to bid the plug numbers EXACTLY as provided may be excluded from further consideration.

(2) Relative Importance of Factors and Subfactors. The relative importance of each factor and subfactor is as follows: Within the Technical/Management factor, the subfactors are of equal importance. The Past Performance Factor is equal to the Technical/Management Approach Factor. All non-price evaluation factors, when combined, are more important than price.

c. Ratings

(1) Each technical/management subfactor will receive one of the ratings described in Table 1. The subfactor ratings will not be rolled up into an overall color rating for the Technical/Management factor.

The combined technical-management/risk rating includes consideration of risk in conjunction with the strengths, weaknesses, and deficiencies in determining technical ratings. Combined technical/risk evaluations shall utilize the combined technical/risk ratings listed in Table 1. Table 2 provides a definitions relating to the technical evaluation rating process.

Technical/Risk Ratings for Factor 1. The technical-management/risk rating provides an assessment of the offeror’s proposed solution for satisfying the Government’s requirements.

See RFP Attachment 5 BVTO Eval Table w Full PP Rating

d. Evaluation of Options

The offeror shall submit pricing for the base period and all option periods, including option pricing for an additional 6-month period that may be authorized IAW FAR 52.217-8. See FAR 52.217-8 which authorizes the Government to require continued performance of any services within the limits and at the rates specified in the contract. The pricing proposal should include a separate line item for the additional 6-month period IAW FAR 52.217-8. These prices shall be identical to the proposed pricing in the 6 months prior to expiration of the base period, or the final option period, if option periods are present. Evaluation of options shall not obligate the Government to exercise the option(s).

e. Discussions

The Government intends to evaluate proposals and award a contract without exchanges. However, the Government reserves the right to conduct exchanges or seek clarifications if the KO determines they are necessary. If exchanges are required, the number of proposals being competitively considered may be narrowed to all of the most highly rated proposals. The Government further reserves the right to reduce the number of proposals being competitively considered to the greatest number that will permit efficient competition among the most highly rated proposals. Additionally, should the Government open discussion the Government reserves the right to limit the competitive range to the top three proposals considering all evaluation factors to include non-price and price factors. If an offeror’s proposal is removed from further consideration for award, written notice of the removal will be provided to the offeror. In the event issues pertaining to the solicitation cannot be resolved to the KO's satisfaction, the Government reserves the right to withdraw and cancel the solicitation. In such event, offerors will be notified in writing.

f. Questions

Questions should be addressed to katherine.a.jackson23.civ@mail.mil and kyle.s.kiyonaga.civ@mail.mil. Please provide any questions, in writing using the provided template, no later than May 16, 2019 at 4:30pm (HST). The Government reserves the right to not answer questions submitted after this time.

(End of provision revisions)

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

as of 23 May 2019

Contract Number:

Task Order Number:

Contractor Name

1. Contracting Officer’s Representative (COR).

a. Primary COR.

Name:

Organization:

Department of Defense Activity Address Code (DODAAC):

Address:

Phone Number:

Fax Number:

E-Mail Address:

b. Alternate COR.

Name:

Organization:

DODAAC:

Address:

Phone Number:

Fax Number:

E-Mail Address:

2. Contract Title. Pacific Air Force (PACAF) Enhanced Cyber Resiliency Experienced Workforce (CREW)

3. Background. PACAF's continually changing missions require a high demand for new technology that enables quick mobility of user data, secure collaboration between US and coalition partners, and the ability to push mission data in real-time to places not possible before. In order for operations to succeed a transformation of the data delivery systems must occur and meet all DOD testing along with acceptance testing inherent to the AF on-boarding process. End-User Computing (EUC) requires a seamless access point, meshed with other data centers to provide transparent and consistent experiences for all PACAF users across the Enterprise. Some of the challenges that the Air Force faces are Mobile devices becoming a more prevalent part of DoD business, while cloud-based services are bringing realities of highly available and resilient data services to users. These new services are offering mobility while being more efficient and productive to name a few enhanced characteristics required by todays End-users. In order to meet the challenges a transformation strategy to incorporate a new generation of computing must be formulated, while securely managing data across a broad array of computing platforms. The technical and program management skills required to accomplish those tasks is not inherently available or part of the duty description for military or government personnel, necessitating contract support to fill the void.

4. Objectives. PACAF A36C requires a theater-level team to upgrade/enhance/maintain the EUC environment through the utilization of technological advances, software consolidation, and implementation of Virtual Infrastructures from the Data Center to the Edge. This includes designing, engineering, architecting, implementing, and maintaining a Virtual Desktop Infrastructure (VDI) solution for Windows 10 on SIPRNet and NIPRNet across the PACAF theatre. Provide a comparable solution to the Air Operations Center that will support CENTRIX/MNIS, enable SecureView, and provide a multi-level client architecture, all in support of the Core Business Systems platforms.

Maintaining SIPRNET and upgrading infrastructure to be compliant and in-line with current NIPR architecture and prepare it for AF Network (AFNet) Migration to create a single domain and name space will help ensure PACAF mission needs are being meet. PACAF's theater team will also sustain a Data Protection/Disaster Recovery solution that includes off-site replication, enterprise archiving and Object Storage. Skills required involve certification, accreditation, contracting, networking, storage, servers, client services, applications, program management, project management, client services, and the virtualization-specific security enhancements that protect both the data, along with network experience for deploying a host of technologies in an overseas Disconnected-Intermittent-Low Bandwidth (DIL) environment.

These are specific implementation-based tasks and not an augmentation of existing roles and responsibilities within the staff. Contractor resources will have years of experience and the skills required to execute the unprecedented merger of servers, storage, networking, data centers, DoD component commands, and end-user devices into a virtual environment that allows users access from anywhere and any device. These contractor resources will be experienced in deploying technologies in PACAFs unique environment.

5. Scope. Contractor will provide a theater-level team to upgrade/enhance/maintain the EUC environment through the utilization of technological advances, software consolidation, and implementation of Virtual Infrastructures from the Data Center to the Edge. This includes designing, engineering, architecting, implementing, and maintaining a Virtual Desktop Infrastructure (VDI) solution for Windows 10 on SIPRNet and NIPRNet across the PACAF theatre. Provide a comparable solution to the Air Operations Center that will support CENTRIX/MNIS, enable SecureView, provide a multi-level client architecture all in support of the Core Business Systems platforms. The theater team will also assist with Contingency Operating Bases, design and review PACAF’s Joint Information Environment (JIE) build-up specifications along with continuous modernization of NIPRNet and SIPRNet infrastructure.

SIPRNet is the Warfighting Network where COMPACAF directs forces, provides critical information, and disseminates the Air Tasking Order (ATO) enabling and directing forces across the PACAF AOR. Current C2 technologies and systems are at risk of not functioning optimally and new initiatives (i.e. Secure Mobile and Virtual Desktops) with their robust security protocols are not supported on the existing platforms. Contractor provided theater crew will enable changes necessary to bring SIPR in line with NIPR and prepare it for AF Network (AFNet) Migration to create a single domain name space as well as support for complete Windows 10 migration.

Contractor will be experienced with the technical solutions required to support the Joint Regional Security Stack (JRSS), the Mission Partner Environment (MPE), and deploying solutions in a Degraded Intermittent and Low Bandwidth (DIL) environment. PACAF is lead for the design of Data Centers for PACOM and designated (SAF/A6) as lead for the deployment of the VDI and charged with developing this solution for the Air Force and DoD. This effort involves deployments at multiple bases simultaneously in the Pacific theater to meet mission timelines as well as contract requirements.

· Task Area 8 – Enterprise Network Engineer SME (2 OPTIONAL)

• Task Area 9 – Multi-Enclave/Commercial Solutions for Classified (CSfC) SME (1 OPTIONAL)

· Task Area 10 – Advanced Integration SME (1 OPTIONAL)

6. Performance Requirements. Contractor shall provide a theater-level team to upgrade/enhance/maintain the EUC environment through the enhancement of the PACAF Enterprise Virtual Environment. This includes designing, engineering, architecting, implementing, and maintaining a VDI solution for Windows 10 on SIPRNet and NIPRNet across the PACAF theatre. Designing, engineering, architecting and implementing a VDI solution for the AOC NIPRNet/SIPRNet to support CENTRIX/MNIS. Implementing SecureView, multi-level client architecture all in support of the Core Business Systems platforms. The theater team will also assist with Contingency Operating Bases, design and review PACAF’s Joint Information Environment (JIE) build-up specifications. This also includes continuous modernization of SIPRNet infrastructure.

Each staffing position is for one full time equivalent (FTE). Number of FTEs required per position annotated in Section 5 in parenthesis after each Task Area. Each FTE shall be 1920 hours per year.

6.1 Task 1 – Senior Program Manager. The contractor shall manage High Level Engineers and Associate Program Managers in the deployment of complex theater-wide joint enterprise projects on a virtualized platform. The Senior Program Manager shall:

6.1.1 Subtask 1: Manage the life cycle of a project from architectural design services to hand-off to customer support using the standards of Project Management Model (PM2). Determine organizational and unit needs and developing technical solutions and Project Support Agreements (PSA) in support of critical cyber requirements. Provide a combined monthly status report providing clear oversight of all project management. Daily status reports will be provided as required during deployment operations.

6.1.2 Subtask 2: De-conflict the simultaneous projects to include the demonstrated skill of management and tracking of equipment shipping, licenses, personnel travel, scheduling, cost analysis, and budget analysis to ensure a turn-key solution under-budget and on-time. Project plan and milestone plan will outline de-conflicting projects.

6.1.3 Subtask 3: Manage and Prepare System, Hardware, and Software Accreditation Packages to include eMASS, and EITDR inputs. Coordinatewith Base Information Assurance Managers (IAMs) and PACAF Cyber Surety to ensure systems and applications are approved for connection to the AF and DISA Networks and inclusion in the base enclaves.

6.1.4 Subtask 4: Develop and implement a VDI Operational Test/Checklist and VDI System Test Plan to include SecureView, System Stability Test, Zero Client Power Test, Functionality of Email, SharePoint, Task Management Tool, Server Power Test, and operational checklists.

6.1.5 Subtask 5: Provide direct customer support and troubleshooting for SecureView and VDI client hardware and software and coordinate with Government Network Operations Centers and Higher Headquarters.

6.1.6 Subtask 6: Develop VDI Joint Information Environment (JIE) Metrics for Joint and Higher AF Headquarters.

6.1.7 Subtask 7: Lead a team in the deployment of virtual capabilities in an austere, and disconnected, disadvantaged and intermittent location where bandwidth and access creates unique challenges. This includes areas that are disconnected and separated from major DoD installations.

6.1.8 Subtask 8: Lead a team of engineers and project managers for on-site multi-datacenter installations in a large overseas theater to include scheduling projects and migrations, coordinating equipment shipments, scheduling travel, coordinating with overseas bases for access, and coordinating installation times with base personnel. Incorporate detailed engineered solutions and architectural diagrams into Project Plan.

6.1.9 Subtask 9: Lead an engineering team in the design, deployment, and management of Virtual Servers, Networks, Storage Arrays, and Virtual Desktops on a secure/non-secure network throughout a large DoD overseas environment. Experience should include provisioning of these devices for Unified Computing (i.e. virtual call managers), and Thin/Zero Client deployments to include SecureView, and SharePoint deployments.

6.1.10 Subtask 10: Lead an architecture and engineering team in the deployment of Virtualized Multi-Tenant Data Center and various secure hybrid Cloud Computing solutions. Demonstrated experience in leading the deployment of virtualization and virtual desktops in the Pacific Theater or other theater-wide DoD deployments to include server-accelerating RAM-based VDI data storage, with server RAM as the primary storage tier and virtualized server acceleration. Experience in guiding the development of Hyper-Converged and Converged Infrastructure technologies whether in a lab or real-world deployment.

6.1.11 Subtask 11: Contractor shall lead an experienced team in the deployment of network, server, and storage on SIPRNet to include configuration of said equipment to Air Force specifications. Experience should include leading a team in the seamless connection to a Virtual Desktop Environment.

6.1.12 Subtask 12: Manage training of AF personnel in virtual desktop site surveys, network and encryption devices requirements, equipment procurement (i.e. Zero/Thin Clients) and installation, and desktop configurations to include SecureView. Create training plans to be handed off after training.

6.1.13 Subtask 13: Must be familiar with host nation sensitivities and be able to work well within the constraints of host nation military and business environment.

Deliverables: Monthly Status Report Daily Status Report Project Plan Project Milestones Detailed Engineered Solutions Architectural Diagrams Budget/Cost Analysis Operational Checklist Test Plan Training Plan Deploy new technologies to PACAF Bases

6.2 Task 2 - Associate Program Manager: Manage engineers in the deployment of complex theater-wide joint enterprise projects on a virtualized platform. The Associate Program Manager will support the Senior Program Manager and shall:

6.2.1 Subtask 1: Manage the life cycle of a project from architectural design services to hand-off to customer support using the standards of PM2. Experienced in determining organizational and unit needs and developing technical solutions and PSA in support of critical cyber requirements.

6.2.2 Subtask 2: De-conflict the simultaneous projects to include the demonstrated skill of management and tracking of equipment shipping, licenses, personnel travel, scheduling, cost analysis, budget analysis to ensure a turn-key solution under-budget and on-time. Assist with Monthly and Daily status reports, and Project Milestones as outline by Senior PM.

6.2.3 Subtask 3: Coordinate with outside vendor Project Managers and Base PMs to ensure the project schedule and deliverables are adhered to.

6.2.4 Subtask 4: Provide detailed project plans and timelines, while coordinating with outside contractor engineers and project managers to refine the solutions; manage the projects from cradle to grave; and other responsibilities as defined by the Senior Program Manager.

6.2.5 Subtask 5: Lead a team of engineers for multi-datacenter installations in a large overseas theater to include scheduling projects and migrations, coordinating equipment shipments, scheduling travel, coordinating with overseas bases for access, and coordinating installation times with base personnel. Combine detailed engineered solutions.

6.2.6 Subtask 6: Lead an engineering team in the design, deployment, and management of Virtual Servers, Networks, Storage Arrays, Virtual Desktops on a secure/non-secure network throughout a large DoD overseas environment. Experience should include provisioning of these devices for Unified Computing (i.e. virtual call managers), Thin/Zero Client deployments, and SharePoint deployments.

6.2.7 Subtask 7: Lead an architecture and engineering team in the deployment of Virtualized Multi-Tenant Data Center and various secure hybrid Cloud Computing solutions. Demonstrated experience in leading the deployment of virtualization and virtual desktops in the Pacific Theater or other theater-wide DoD deployments to include server-accelerating RAM-based VDI data storage, with server RAM as the primary storage tier and virtualized server acceleration. Experience guiding the development of Hyper-Converged and Converged Infrastructure technologies whether in a lab or real-world deployment. Assist with incorporation of architectural diagrams and operational checklists into Project Plan.

6.2.8 Subtask 8: Lead a team in the deployment of virtual capabilities in an austere, and disconnected, disadvantaged and intermittent location where bandwidth and access creates unique challenges. This includes areas that are disconnected and separated from major DoD installations.

6.2.9 Subtask 9: Contractor shall lead an experienced team in the deployment of network, server, and storage on SIPRNet to include configuration of said equipment to Air Force specifications. Experience should include leading a team in the seamless connection to a Virtual Desktop Environment.

6.2.10 Subtask 10: Provide direct customer support and troubleshooting for VDI client hardware and software and coordinating with Government Network Operations Centers and Higher Headquarters.

6.2.11 Subtask 11: Must be familiar with host nation sensitivities and be able to work well within the constraints of host nation military and business environment.

Deliverables: Monthly Status Report Daily Status Report Project Plan Project Milestones Detailed Engineered Solutions Architectural Diagrams Budget/Cost Analysis Operational Checklist Test Plan Training Plan Deploy new technologies to PACAF Bases

6.3 Task 3 - Virtualization Lead Engineer/Advanced Subject Matter Expert: Serves as the architect working directly with senior PACAF/DoD/PACOM staff and the Project Managers. Lead Engineer will be experienced in working with DoD/AF personnel in the Pacific Theater in architecting and deploying solutions in the Pacific Theater. The Lead Engineer shall:

6.3.1 Subtask 1: Contractor will architect and engineer a Virtualized Multi-Tenant Data Center and various secure hybrid Cloud Computing solutions, virtualized storage, networks, and desktops in the Pacific Theater or other theater-wide DoD deployments to include server-accelerating RAM-based VDI data storage, with server RAM as the primary storage tier, virtualized server acceleration and SecureView. Provide oversight on all engineered solutions and architectural diagrams.

6.3.2 Subtask 2: Determine technical requirements to support AF/DoD mission-sets, planning, coordinating, and build of operational checklists for virtualization configurations with enterprise technicians to include storage, memory, compute, and network infrastructure configurations with the local base. Plan and coordinate server migrations from physical to virtual by engaging with base enterprise technicians and primary staff as required.

6.3.3 Subtask 3: Contractor will engineer and deploy technologies in coordination with and technically in line with the Air Force (AF) current enterprise Microsoft-centric environment and the Air Force Base Area Network Functional Specification, which is a part of the continuing evolution of the common-user data network, into a fully unified, Air Force-centric enterprise. In-depth understanding of unclassified common-user internet protocol network that plays a key role in enabling the convergence of other stovepipe networks into a single, common IP environment.

6.3.4 Subtask 4: Perform engineering and deploying technologies in coordination and technically in line with the AF Reference Architecture Designs. This includes Network Normalization, Mobility, Core Data Centers (CDC) and Installation Processing Nodes (IPN) reference architectures, which include a virtualization baseline from data center to desktop/mobile device.

6.3.5 Subtask 5: Deploy virtual capabilities, to include the storage, network, server (applications and databases) aspects, and the software required to centrally manage this architecture. Software may include VMWare vSphere, Citrix Xen, and Microsoft Hyper-V platforms and extends to desktop management and deployment of the VDI otherwise referred to Thin, Zero, Multi-Level, or Trusted Thin Clients.

6.3.6 Subtask 6: Develop test and training plans for Airmen to manage the complex backend virtual environment to include Cisco’s Unified Computing Systems (UCS), EMC VNX storage area network, VMware vCenter, and VMware Horizon View

6.3.7 Subtask 7: Contractor will be sizing, engineering, deploying and managing storage area networks (SAN) to include EMC, with the broad understanding of other SAN leaders to include NetApp, Dell Compellent, and XTremIO. Should possess the broad understanding of Hyper-Converged solutions such as Nutanix and EVO. Should possess a broad understanding of pure flash storage VDI-specific solutions such as Tintri and Nimble Storage.

6.3.8 Subtask 8: Provision virtual servers to support Unified Computing (i.e. virtual call managers) and SharePoint deployments to include the conversion from Physical-to-Virtual (P-to-V) on a virtualized data center platform.

6.3.9 Subtask 9: Deploy networks, servers, and storage on SIPRNet to include configuration of said equipment to Air Force specifications. Experience should include leading a team in the seamless connection to a Virtual Desktop Environment.

6.3.10 Subtask 10: Provide training for Airmen to provision, Zero/Thin/Multi-level/Trusted Thin Clients to include experience in deploying this capability on existing infrastructure (category 5e cable and fiber).

6.3.11 Subtask 11: Assist with the technical development and implementation of a VDI Operational Test/Checklist and VDI System Test Plan, to include System Stability Test, Zero Client Power Test, Functionality of Email, SharePoint, Task Management Tool, and Server Power Test.

6.3.12 Subtask 12: Deploy virtual capabilities in an austere, and disconnected, disadvantaged and intermittent location where bandwidth and access creates unique challenges. This includes large areas and land masses that are disconnected and separated.

6.3.13 Subtask 13: Provide customer support and troubleshooting for Virtual Servers and VDI client hardware and software and coordinating with Government Network Control Centers and Higher Headquarters

6.3.14 Subtask 14: Plan and coordinate virtualization configurations with enterprise technicians and network infrastructure configurations with the local base. Plan and coordinate servers chosen for physical to virtual at the base with base enterprise technicians and A3/6 personnel.

6.3.15 Subtask 15: Contractor will deploy Teradici PC over Internet Protocol (PCoIP) technologies. The PCoIP compresses, encrypts and rapidly transports image pixels to PCoIP end-user devices. They in turn decrypt, decompress and display the image on a screen. Includes adding new devices, updating firmware, adding policies

6.3.16 Subtask 16: Perform daily VDI Health Checks which includes the systematic and daily monitoring of the backend infrastructure and desktop performance. This includes demonstrated proficiency with Stratusphere or like technologies. Stratusphere provides the visibility required to more effectively manage desktop performance and the user experience. Stratusphere provides the visibility necessary for machine boot and login process troubleshooting and optimization, health checks, platform validation, and more streamlined management functionality of the host environment.

6.3.17 Subtask 17: Perform installation, configuration, and management of Atlantis iLio or like technologies.