Army_EITaaS_PPON_15JULY2019-Amendment_0003.pdf

Army EITaaS – PPON, Instructions and Evaluation Criteria Version 1.0, 9 July 2019

Prototype Project Opportunity Notice (PPON) for Army Enterprise Information

Technology as a Service (EITaaS)

Solicitation Number: W15QKN-19-R-06JL

Army Contracting Command – New Jersey (ACC-NJ) Innovative Concepts Division (ACC-NJ-IC) Attn: Mr. Christopher Fotiadis Agreements Officer Building 10, Phipps Road, Picatinny Arsenal, NJ 07806-5000 Office: 973.724.8543

Version 1.0, 9 July 2019

Version 1.0, 5 July 2019 i

Table of Contents

SECTION 1 – EXECUTIVE SUMMARY

1.1 Purpose & Authority

1.2 Background

1.3 Acquisition Approach

1.4 Definitions

1.5 Eligibility

A – ACQUISITION PROCESS for Prototype Project Opportunity Notice (PPON)

B – PROPOSAL INSTRUCTIONS AND NOTICES TO OFFERORS

B.1 GENERAL INSTRUCTIONS

B.2 PROPOSAL PART 1 and PROPOSAL PART 2 FILE SUBMISSION

INSTRUCTIONS

B.3 PROPOSAL PART 1 AND PROPOSAL PART 2 ORGANIZATION INSTRUCTIONS

B.4 GATE AND PROPOSAL ORGANIZATION AND FORMAT

B.4.1 Proposal Organization

B.5 INSTRUCTIONS FOR PREPARATION OF PROPOSAL PART 1 AND PROPOSAL

PART 2 CONTENT:

B.5.1 Step 1: Proposal Part 1 Submission Content

B.5.2 Step 2: Upward Invite A –Proposal Part 2 Submission Content

B.5.2.1 Volume I: Factor 1 – Technical

B.5.2.1.1 Sub-factor 1 - Technical Approach

B.5.2.1.2 Sub-factor 2 – Solution Diagrams

B.5.2.1.3 Sub-factor 3 – Technical Schedule:

B.5.2.1.4 Sub-factor 4 – Solution Hardware/Software List (Attachment 0004)

B.5.2.2 Volume II: Factor 2 – Demonstrated Performance

B.5.2.3 Volume III: Factor 3 –Price Matrix (Attachment 0005)

B.5.2.4 Volume IV: Agreement Documentation ii

C – EVALUATION CRITERIA FOR PROPOSAL PART 1 SUBMISSION, EVALUATION

FACTORS AND CRITERIA FOR AWARD

C.1 GENERAL PROCESS

C.2 PROPOSAL PART 1 CRITERIA

C.2.1 Proposal Part 1 Minimum Acceptable Standards Defined:

C.2.2 Basis of Proposal Part 1 Evaluationfor Volume II, Factor 2 Demonstrated Performance:

C.3 FACTORS TO BE EVALUATED DURING STEP 2 AND STEP 3, ORDER OF

IMPORTANCE AND CONSIDERATION FOR AGREEMENT AWARD

C.3.1 Factors to be Evaluated:

C.3.2 Relative Order of Importance:

C.3.3 Consideration for Step 4 Agreement Award (FY19)

C.4 EVALUATION APPROACH

C.4.1 Evaluation Scope

C.4.2 Volume I: Factor 1 – Technical

C.4.2.1 Sub-Factor 1 – Technical Approach

C.4.2.2 Sub-factor 2 – Solution Diagrams

C.4.2.3 Sub-factor 3 – Technical Schedule

C.4.2.4 Sub-factor 4 – Solution Hardware/Software List (Attachment 0004)

C.4.2.5 Technical Factor Rating Definitions

C.4.3 Volume III: Factor 3 –Price

C.4.4 Volume IV – Agreement Documentation

SECTION 1 – EXECUTIVE SUMMARY

1.1 Purpose & Authority1

The purpose of this Prototype Project Opportunity Notice (PPON) is to award up to three prototype Other Transaction Agreements (OTAs) under the authority of 10 U.S.C. § 2371b, with each Awardee implementing a commercial approach to delivering enterprise network and core Information Technology (IT) solutions for the Army Enterprise to establish/validate a Proof of Concept.

1.2 Background

As the Army drives towards its 2028 Modernization Strategy and postures to the era of great power competition put forth in the National Defense Strategy, we must operate and defend our networks ruthlessly. The Army’s communications network is the foundational weapons platform for the entire force. All Army operations depend on timely, reliable delivery and transmission of data. Today, the Army owns and operates its entire IT network and long-distance communications. This model produces slow rates of change and technology adoption that diverges from similar commercial offerings.

The Army is exploring a new approach for delivering enterprise network and core IT services:

Enterprise Information Technology as a Service (EITaaS). The EITaaS pilot will assess the feasibility to deploy commercial solutions for data transport, end-user services, and collaborative data environments for selected Army installations.

An initial EITaaS pilot will allow the Army to evaluate commercial solutions and their ability to strengthen enterprise IT service delivery, improve user experience and integrate with existing government-only systems, architecture, processes and facilities, while maintaining an aggressive cybersecurity posture. Navy (USN) and Air Force (USAF) and National Security Agency (NSA) have already undertaken a similar EITaaS approach and several USAF pilot installations are presently undergoing EITaaS implementations. The Army will leverage USN, NSA and USAF lessons learned to shape its pilot implementation.

The specific purpose of this EITaaS Pilot is to partner with industry to reform existing and future Army IT operations and services delivery through commercial services in order to increase Army readiness, mission effectiveness and IT user efficiencies, and establish standardized, innovative IT services.

1.3 Acquisition Approach

The Government intends to award up to three independent fixed amount OTAs for EITaaS

1 For additional information please refer to the Department of Defense (DoD), Other Transactions Guide, Version 1.0, dated November 2018 https://www.dau.mil/guidebooks/Shared%20Documents%20HTML/Other%20Transactions%20(OT)%20Guide.aspx prototyping, with each Awardee being assigned up to three Pilot Sites to implement their solution. The duration for each prototype OTA is estimated to be three years.

Follow-on production award(s) is planned for FY22 and is discussed in Section A, below.

1.4 Definitions

“Agreement” reference the definition of “Other Transaction for Prototype Projects”.

“Agreements Officer (AO)” is the United States Army Contracting Command – New Jersey Contracting Activity warranted Officer with authority to enter into, administer, change or terminate OTAs.

“Agreements Specialist (AS)” is the United States Army Contracting Command – New Jersey Contracting Activity Specialist and designee of the AO for executing modifications, administrative matters, and financial aspects of the Agreement.

“Enterprise Information Technology as a Service” refers to Commercial delivery and management of protected IT services from the enterprise to the point of need (user) on the Department of Defense Information Network-Army (DODIN-A). Provides connect, protect, storage, computing, common IT services, hardware, software, and networking infrastructure.

“Fixed Amount” means an OTA under which an awardee agrees to complete a prototype project for an agreed upon total price and where payments are not based on amounts generated from the awardee’s financial or cost records.

“Nonprofit Research Institution” means a nonprofit institution, as defined in 15 U.S.C. 3703, and includes federally funded research and development centers, as identified by the National Scientific Foundation in accordance with the Government wide Federal Acquisition Regulation issued in accordance with section 1303(a)(1) of title 41 (or any successor regulation thereto).

“Nontraditional Defense Contractor (NDC)” An entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by DoD for the procurement or transaction, any contract or subcontract for the DoD that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section (see 10 U.S.C. 2302(9)).

"Other Transaction for Prototype Projects” refers to this type of OTA. This type of OTA is authorized by 10 U.S.C. 2371b for prototype projects directly relevant to enhancing the mission effectiveness of military personnel and the supporting platforms, systems, components, or materials proposed to be acquired or developed by the DoD, or for the improvement of platforms, systems, components, or materials in use by the armed forces.

This type of OTA is treated by DoD as an acquisition instrument, commonly referred to as an "other transaction" for a prototype project or a Section 2371b "other transaction". OTAs are acquisition instruments that generally, are not subject to the federal laws and regulations governing procurement (FAR based) contracts. As such, they are not required to comply with the Federal Acquisition Regulation (FAR), its supplements (i.e. DFARS) or laws that are limited in applicability to procurement contracts.

“Proposal Part 1” refers to the Demonstrated Performance volume that is required to be submitted in Step 1.

“Proposal Part 2” refers to the proposal submission that includes the Technical, Price and Agreement Documentation Volumes.

“Pilot Site” refers to a designated Army owned, operated or leased Installation/Base/Location/Fort/Camp.

“Resource Share” includes any costs a reasonable person would incur to carry out (necessary to) Statements of Work not directly paid for by the Government.

“Significant Participant” means an entity that makes a significant contribution to the prototype project. Examples of what might be considered a significant contribution include supplying new key technology or products, accomplishing a significant amount of the effort, or in some other way causing a material reduction in the cost or schedule, or increase in performance.

“Small Business” as defined by 10 U.S.C. 2371b means a small business concern as defined under section 3 of the Small Business Act (15 U.S.C. 632).

“Technical Exchanges” means communications between the Government and the Offeror after proposal submission.

1.5 Eligibility

In accordance with 10 U.S.C. 2371b paragraph d, Offerors shall meet one of the following conditions to be considered for an award:

(A) There is at least one nontraditional defense contractor or nonprofit research institution participating to a significant extent in the prototype project.

(B) All significant participants in the transaction other than the Federal Government are small businesses (including small businesses participating in a program described under section 9 of the Small Business Act (15 U.S.C. 638)) or nontraditional defense contractors.

(C) At least one third of the total cost of the prototype project is to be paid out of funds provided by sources other than the Federal Government.

In addition, Offerors must have a Dunn and Bradstreet (DUNS) number and must register in the System for Award Management (SAM) to obtain a Commercial and Government Entity (CAGE) code. This system verifies identity and ensures that payment is sent to the right party. In general, to invoice and receive payment after award of an OTA, Offerors must register in Wide Area Work Flow (WAWF) through the Procurement Integrated Enterprise Environment (PIEE). The Offeror must be considered a responsible party by the Agreements Officer, and is not suspended or debarred from such agreement by the Federal Government, and is not prohibited by Presidential Executive Order, or law from receiving such award.

Additionally, Offerors who attempt to circumvent the eligibility requirements/conditions may be excluded from consideration at the Agreements Officer’s discretion.

A – ACQUISITION PROCESS for Prototype Project Opportunity Notice (PPON) A.1 Acquisition Process Steps The Other Transaction (OT) acquisition process for this Prototype Project Opportunity Notice (PPON) includes Six Steps. Figure 1 below provides an overview chart of the process of Steps 1 – 6. Figure 2 below provides the Pilot Sites for the Army EITaaS Pilots.

Only those Offerors that receive an Upward Invite at the end of a Step will be eligible to proceed to the next Step and will remain eligible to receive an award. Each Upward Invite will be determined by a formal government decision and a corresponding Government Basis of Selection (BoS). Below is a summary of each Step.

A.1.1 Step 1 – is submission of the Proposal Part 1. This submission includes the documents listed in Section B.5.1. The submission will be evaluated in accordance with the criteria described in Section C of this document. If an Offeror’s Proposal Part 1 meets the minimum acceptable standards, they will receive an Upward Invite and the Offeror’s Proposal Part 2 will be evaluated during Step 2. If an Offeror’s Proposal Part 1 does not meet the minimum acceptable criteria the Proposal Part 2 will not be evaluated by the Government and will be eliminated from competition for an award. The Government will provide written notice of Upward Invite or Non-Selection at the conclusion of the Step 1 evaluation. Offerors can submit one Question Set during Step 1.

A.1.2 Step 2 – is an Upward Invite – A: Submit (written) Proposal Part 2 (per the instructions included here). The Step includes the Government evaluation of the proposals, as described in Sections C.3 and C.4 of this document. The Government will provide written notice of Upward Invitation or Non-Selection at the conclusion of the Step 2 evaluation. If an Offeror receives a notice of Non-Selection at the conclusion of Step 2, the proposal will be eliminated from competition for award. Offerors can submit one Question Set during Step 2.

A.1.3 Step 3 – is an Upward Invite – B: Participate in Technical Exchanges and or Submit Final Proposal Part 2 (if determined necessary). If needed, this Step requires submission of a Final Proposal Part 2 based on updates to the evaluations of the proposals, using Sections C.3 and C.4 of this document. During Technical Exchanges the Government may, at least once, publish the Total Evaluated Prices of all proposals still in consideration for award. The Total Evaluated Prices will not contain any proprietary information, and will not be associated with a specific Offeror. Total Evaluated Prices will only be made known to those Offerors still in consideration for Award. Offerors will be given the opportunity to submit a revised Price Matrix after publication of all Total Evaluated Prices. Specific revised Price Matrix submission instructions will be provided after receipt of Initial Proposals. The Government will provide written notice of transition to Step 4 or Non-Selection at the conclusion of Step

3. If an Offeror receives a notice of Non-Selection at the conclusion of Step 3, the proposal will be eliminated from competition for award.

Note: only Offerors with proposals that are still in consideration for award will be invited to participate in Technical Exchanges.

A.1.4 Step 4 – is Agreement Award: for Up to three Prime Offeror Awards. Each planned award will include up to a total of three Pilot Sites, with only the first Pilot Site being designated and funded for Fiscal Year 2019 (FY19). Authority to implement the Awardee’s solution at additional Pilot Sites for FY20 and FY21 may be granted based on 1) Available Funding and 2) Army Priorities. For this Step 4, the proposals will be Rank Ordered, with the Best Value proposal that is Ranked #1 awarded the #1 Ranked Pilot Site Set. The Proposal ranked #2, will be awarded the priority #2 Pilot Site Set.

The Proposal ranked #3 will be awarded the priority #3 Pilot Site Set. The Proposal ranking will also identify up to a maximum of three “Standby Solutions”. Thus the Proposal rankings may identify up to six proposals as eligible for an award, ranked one through six.

** For those Offeror(s) that receive an Agreement Award at Step 4, the Government will provide updated Instructions and Evaluation Criteria for Production Award Consideration (for Step 5, Upward Invite – C and for Step 6 – Production Award) and in a separate document no later than Month 34 of the Period of Performance.**

A.1.4.1 Standby Solutions: These represent proposals that the Government may elect to negotiate an Agreement award with under certain circumstances. In the event that the Government makes a determination that an Initial Awardee’s (i.e. Awardee #1, #2 or #3) performance at Pilot Site #1 (i.e. AFC, Fort Polk or Camp Roberts) has not demonstrated satisfactory progress towards a successful prototype solution, the Government may terminate the existing Agreement and may elect to enter Technical Exchanges for a Standby Solution to replace the Initial Awardee at Pilot Site #1. The Standby Solution will include all of the same Phases as described in the Statement of Objectives (SOO). All terms, conditions and provisions of this PPON will remain the same. The Standby Solutions will only be valid for 24 months/730 days from the date of the initial award. At the conclusion of the validity period, if Technical Exchanges for terms of award for a Standby Solution have not begun the Standby Solution will no longer be considered for Agreement award.

A.1.5 Step 5 – is Upward Invite – C: Submit Performance Work Statement (PWS) for Consideration for Production. Not later than month 34 of the 36 Month Period of Performance, the Government will review the EITaaS Providers’ (that received the Agreement Award) demonstrated performance as measured by the Pilot Success Metrics (SOO paragraph 4.) at each of the Awarded Sites (SOO Figure 3, Row A, B or C). Those Offerors that are determined to meet all of the success metrics will be invited to submit a PWS for Government review and evaluation for consideration of a follow-on production award(s). Although it is the Government’s intention to award production follow-on Agreements or Contracts during Fiscal Year 22, Offerors are advised that due to internal government considerations there could be a significant delay between the conclusion of the OTA and award of a follow-on production Agreement or Contract.

Further, the government at its sole discretion reserves the right not to proceed into production.

A.1.6 Step 6 – is Production Award: Up to three Awards (one per Awardee). To support the Award decision, the Offerors’ Performance Work Statements will be reviewed and prioritized, (in the same manner as the Proposals in Step 2), for a determination for a Production Award based on Funding and Army Priorities. The Government will determine if this award will be a follow-on OT Agreement or Federal Acquisition Regulation (FAR) Contract.

A.1.7 Follow-on Production Notice: In accordance with 10 U.S.C. § 2371b(f), this competitively awarded Agreement may lead to follow-on production activities if the Key Technical Goals, as defined in the SOO, are met; or in the event that a particularly favorable or unexpected result is accomplished that justifies transition to production.

A.1.8 Production Scale: The EITaaS follow-on production Agreement(s) can scale to provide support to up to all of the Army Installations within the Continental United States (CONUS) and Outside CONUS (OCONUS). This includes designated geographically separated facilities (owned or leased) and support to uniformed military, Government civilian and Government on-site support contractors at those facilities.

Figure 1 below provides an overview chart of the process of Steps 1 – 6. Figure 2 below provides the Pilot Site Sets for the Army EITaaS OTAs.

Figure 1 Army EITaaS Steps to Award

Figure 2 - Army EITaaS Planned Pilot Site Sets

A.1.9 Unclassified Process. For this proposal process, no information classified as “Confidential”, “Secret”, or “Top Secret” shall be submitted or included in any proposed Gate submission or Pilot Project Proposals.

*** END OF A – ACQUISITION PROCESS for Prototype Proposal Opportunity Notice (PPON) ***

B – PROPOSAL INSTRUCTIONS AND NOTICES TO OFFERORS

B.1 GENERAL INSTRUCTIONS

B.1.1 The Offeror’s proposal shall be signed and submitted by an individual having authority on behalf of the Offeror to enter into an Agreement based on the submitted proposal. The Offeror’s proposal shall be written in the English language and conform to the instructions below. Based on the Prototype Proposal Opportunity Notice (PPON) requirements, the Offeror shall submit a proposal in accordance with these Proposal Submission Instructions.

B.1.2 Proposal Quality:

B.1.2.1 Proposal Part 1: The Government may not enter Technical Exchanges for the Step 1 Submission before moving to Step 2, however may seek clarification for minor irregularities. Therefore Offerors are encouraged to only submit Proposal Part 1 information that clearly meets the defined acceptable standard. Offerors are reminded that in order to be considered for Step 2, the Proposal Part 1 must receive an adjectival rating of ‘Satisfactory Confidence’ or ’Substantial Confidence’. The Government may waive any informalities and minor irregularities in Proposal Part 1 submissions in order to proceed to the next Step.

B.1.2.2 Proposal Part 2: For those Offerors in receipt of Step 2 Upward Invite A – Submit Proposal, The Offeror’s initial proposal should contain the Offeror’s best approach from a technical and price perspective. The Government may waive any informalities and minor irregularities in Proposals received in order to proceed to the next Step.

B.1.3 IMPORTANT NOTE: Proposal Part 1 submissions may not be evaluated in entirety prior to the Proposal Part 2 Due Date. Offerors are advised that a Proposal Part 2 that is submitted by the Due Date WILL NOT BE EVALUATED BY THE GOVERNMENT and the Offeror will be eliminated from competition if the Proposal Part 1 submission does not meet the minimum acceptable standards. It is not anticipated that the Proposal Part 2 Submission Due Date will be extended.

B.2 PROPOSAL PART 1 and PROPOSAL PART 2 FILE SUBMISSION INSTRUCTIONS

B.2.1 General Proposal Submission Guidelines:

B.2.1.1 The costs of preparing, submitting, and participating in proposal efforts are not considered an allowable direct charge to any Agreement.

B.2.1.2 A separate submission is required for the Proposal Part 1 and Proposal Part 2 and/or Final Proposal Part 2. All Proposal submissions shall be made through the AMRDEC Safe Access File Exchange (SAFE) website.

B.2.1.3 Due Dates:

A. Proposal Part 1 Question Sets are due the by 1300 EST on the 12 July 2019 (3 days after PPON is published).

B. Proposal Part 1 submissions are due by 1300 EST 19 July 2019 (10 days after the

PPON is published). Offerors are encouraged to submit an approved, active DD2345 as soon as the release date of this PPON in accordance with the instructions located in Section B.2.3, using the AMRDEC SAFE Site.

C. Proposal Part 2 Question Sets are due by 1300 EST 23 July 2019 (14 days after the PPON is published).

D. Proposal Part 2 submissions are due by 1500 EST on 9 August 2019. (31 days after PPON is published.

E. If Final Proposal Part 2 submissions are required, the Due Date will be determined after the Government’s evaluation of the Initial Proposal Part 2 submission.

B.2.1.4 Late Submission:

Any Questions Set or Proposal submission (Part 1 or Part 2) received by the Government after the exact time specified in B.2.1.3 A-D will be determined as late and may not be considered.

B.2.1.5 Official Transmissions:

A. Amendments will be issued via the FBO Combined Synopsis/Solicitation page.

B. Points of Contact. The Agreements Officer (AO) and Agreement Specialist (AS) are the SOLE points of contact for this procurement. All communications must be sent, in writing, to both:

Table 1 – Agreement Points of Contact

Agreements Officer (AO): Agreements Specialist (AS):

Mr. Christopher W. Fotiadis christopher.w.fotiadis.civ@mail.mil

Ms. Yolie M. Davila yolie.m.davila.civ@mail.mil

C. Questions/Comments Format. Any questions and/or comments submitted regarding this PPON shall be submitted in writing by e-mail to the POCs listed above in Table 1 and shall refer to specific text of the PPON in the following format:

E-mail Subject: VendorName Questions/Comments Solicitation No. W15QKN-19-R-

06JL

Format the Questions/Comments as depicted in Table 2:

Each Question/Comment shall be on one row.

Offerors shall NOT INSERT BLANK ROWS between each Question/Comment

Column headings shall appear at the top of each page when printing

Submit Questions and Comments file in MS Excel (compatible with MS Excel 2013) as an attachment with file naming convention:

VendorName_Qs_PPON_W15QKN-19-R-06JL.xls.

Table 2 - Questions and Comment Format

Offeror Company Name:

Offeror POC Name, E-mail, Phone #:

Item # Government File Name Page # Para # / Line #

Question/Comment Rationale

(Example)

1.

Army_EITaaS_Statement_Of_ Objectives_2019_06_13.pdf 3 Figure 1

Will the Army consider contractor proposed Pilot Sites for FY20?

Planning

B.2.1.6 Questions/Comments and Answers:

The Government will only accept written questions to ensure that all Offeror inquiries have been addressed in advance of the proposal suspense date/time. Each Offeror shall submit only one set of questions for the Proposal Part 1 requirements, and one set of questions for Proposal Part 2 requirements. This limitation excludes Technical Exchanges that may be required in Step 3.

The Government may respond with a compilation of frequently asked questions or a revised document (i.e. these Instructions, attachments, enclosures) as time permits. See paragraph B.2.1.3 for the suspense date / time for any questions and / or comments.

B.2.1.7 Notification of use of non-Government Advisors:

Offerors are advised that designated individuals from the firms identified in Attachment 0007, Army Enterprise Information Technology as a Service (EITaaS) Non-Government Advisors Non-Disclosure Agreement Notice, File Name: “Attch_0007_EITaaS_Non- Govt_Advisors_NDA_Notice_2019_06_22” have provided on-site support as Advisory and Assistance Services that included participation in the preparation of the SOO and other requirement documents and will also serve as non-government advisors supporting proposal evaluations. These individuals will be authorized access only to those portions of the proposal data and evaluation team exchanges that are necessary to enable them to perform their respective duties.

By direction of the Agreements Officer, the designated individual support contractors, have executed a Non-Disclosure Agreement (will be updated to list the Offerors proposing) that in summary, states the support contractor will:

Have read, understand and will abide by the requirements of Section 27 of the Office of Federal Procurement Policy Act (41 USC 423) Affirm that there is no direct or indirect personal or family financial interest in the interested/proposing Offerors;

Protect the Offerors proposal information from unauthorized use or disclosure for as long as it remains proprietary; and Refrain from using the proprietary information for any purpose other than that for which it was furnished.

The firms listed in Attachment 0007 are expressly prohibited from competing on the subject acquisition as an Offeror, or as a subcontractor, and are prohibited from providing any form of services or support to potential Offerors (prime and subcontractors) resulting from this solicitation.

B.2.2 Proposal Part 1 and Proposal Part 2 Submission: Each Offeror shall submit a total of two electronic proposals:

One submission for Step 1 – Proposal Part 1 Submission Volume II (Demonstrated Performance) and

One submission for Step 2 – Proposal Part 2 Submission Volumes I (Technical), III (Price) and IV (Agreement Documents)

All such proposals shall address the Government requirements outlined in the PPON. The Offeror bears responsibility for submitting its offer by the specified date/time.

All Offerors shall allow their proposals to be valid for at least 24 Months/730 Days, or the proposal will not be eligible for consideration for award or as a Standby Solution.

B.2.3 Submission of Proposal Part 1 and Proposal Part 2: Offerors shall submit electronic response files through the Aviation and Missile Research, Development and Engineering Center (AMRDEC) Safe Access File Exchange (SAFE) website. Access to SAFE is available through the website at:

https://safe.amrdec.army.mil/safe/Welcome.aspx

Submission steps include the following:

(1) Instructions for GUEST and CAC (Common Access Card) users are provided at the website. SAFE is accessible to anyone as a GUEST with a valid commercial e-mail address.

SAFE supports file sizes up to 2 gigabytes (GB) for uploading. Per the AMRDEC instructions: "You may add up to 25 files per package, so long as the file size does not exceed 2GB."

(2) Upload all response files using the naming convention identified in each Step; in place of any blank spaces in the filename, use underscore “_” or dash “-”

(3) Once at the AMRDEC site, manually enter the below email address to submit response files to:

Agreements Officer (AO): christopher.w.fotiadis.civ@mail.mil

Agreements Specialist (AS): yolie.m.davila.civ@mail.mil

(4) After successfully uploading the proposal file(s), the SAFE site will send an email to the GUEST user or CAC user: “Subject: VERIFICATION IS REQUIRED - AMRDEC Safe Access File Exchange Submittal Notice - VERIFICATION IS REQUIRED”. Follow the instructions in that note to VERIFY the sender’s e-mail. The package (uploaded files) will only be sent after the VERIFICATION step, which provides a LINK and PASSWORD to VERIFY and “send” the package to the Points of Contact.

(5) After submitting through SAFE, send a separate notification e-mail stating that a response submission was made to the Points of Contact (AO and AS) listed above in Table 1 with the following Subject:

Step 1: “VendorName Part 1 Submitted PPON: W15QKN-19-R-06JL”

Step 2: “VendorName Part 2 Submitted PPON: W15QKN-19-R-06JL”

The body of the note shall be short and include the Offeror Point of Contact.

Response submissions that are uploaded to the SAFE site will be assigned a date/time (in Central Time) by the SAFE system. The Government will consider a response to be on time or late based on the Offerors last file “UPLOAD” date/time. All Offerors shall ensure the “UPLOAD” date and time is before the PPON submission date and time (Eastern Time).

Attach all proposal files using the following naming convention:

VendorName_Vol_#_W15QKN-19-R-06JL

(Example: EITaaS_Experts_Inc_Vol_1_W15QKN-19-R-06JL)

B.3 PROPOSAL PART 1 AND PROPOSAL PART 2 ORGANIZATION INSTRUCTIONS

B.3.1 This section provides Offerors general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. To be considered for award, the Offeror's submission/proposal must include all data and information requested by the PPON and must be submitted in accordance with these instructions. The submission/proposal shall be compliant with the requirements as stated.

B.3.2 The Government reserves the right to reject any proposal that does not comply with proposal preparation instructions.

B.3.3 The proposal shall be clear, concise and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government requirements, but shall provide convincing rationale to address how the Offeror intends to meet these requirements.

B.3.4 Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will, with the exception of Demonstrated Performance, base its evaluation on the information presented in the Offeror's proposal. For the Demonstrated Performance information only, the Government may verify the information provided by contacting the named points of contact or validating the performance through other public/Government records.

B.4 PROPOSAL ORGANIZATION AND FORMAT

B.4.1 Proposal Organization

The Offeror shall prepare the Proposal Part 1 and Part 2 as set forth in Table 3 below.

Table 3 – Proposal Part 1 and Part 2 File Organization & Page Limits

STEP 1: Proposal Part 1

Proposal Part 1 Submission: Filename and Page Count

Offeror submits Part 1 information:

A. Offeror Letter B. Attachment 0001 – DD Form 2345 C. Attachment 0002 – Affirmation of

Business Status Certification

(ABSC)

D. Cloud Service Provisional Authorization Memo(s) (PA) with Impact Level 5 for proposed solution

E. If a reseller, certification of designation as a “Preferred Provider” in the highest tier for the Cloud Offeror.

Return with Filename(s):

VendorName_Gate_W15QKN-19-R-06JL.pdf

Page limit by section.

A. Offeror Letter = Offeror format, 2 Page limit B. Attachment 0001 – DD Form 2345 = Submit completed Government Form C. Attachment 0002 – ABSC = Submit completed

Government Form D. PA Memo(s) = Offeror Format, No Page limit E. Certification of “Preferred Provider” qualification

= Offeror Format, No Page limit

F. Attachment 0003 – Demonstrated Performance Record

Return with Filename(s):

VendorName_Attch_0002_Perf_W15QKN-19-R- 06JL.pdf

F. Attachment 0003 = Submit completed Tables 1

& 2 = 6 Page limit, allocated as Table 1 Qualifications = 2 Page limit Table 2 Demonstrated Performance Record = 4 Page limit (maximum of 4 records)

STEP 2: Upward Invite A – Submit Proposal Part 2

Proposal Volume: Filename and Page Count

Volume I, Technical:

Filename: VendorName_Vol_1_Tech_W15QKN- 19-R-06JL.pdf Page limit by section.

Cover, and Glossary / Acronym List

Cover = 1 Page, Offeror Format not included in count.

Glossary / Acronym List = No page limit (Not included in 20 page Count – Not evaluated).

Table of Contents (Not Required) will not be included in 20 page count.

Volume I Factor 1 Technical:

Subfactor 1 Technical Approach Subfactor 2 Solution Diagrams Subfactor 3 Technical Schedule

Page Count by Subfactor: (Table of Contents, which are not required, do not count towards page limitation)

1. Technical Approach = 20 pages, allocation of

Subfactor 4 Solution HW/SW List (Attachment 0004 – Offeror Solution) pages at Offeror’s discretion.

2. Solution Diagrams = 4 pages total

Network Flow Diagram Non-classified Internet Protocol (IP) Router Network (NIPRNet) = 1 page Network Flow Diagram Secret Internet Protocol Router Network (SIPRNet) = 1 page Systems, Services Diagram NIPRNet = 1 page Systems, Services Diagram SIPRNet = 1 page

3. Technical Schedule = 1 page (Gantt View)

4. Solution HW/SW List = 10 pages (Govt

Attachment 0004 – Offeror Solution)

Volume II, Factor 2 Demonstrated Performance

No Additional Submission:

Files carried forward from Part 1 for Factor 2.

Volume III, Factor 3 Price:

Filename(s):

VendorName_Attch_0005_Price_W15QKN-19-R- 06JL.xlsx

Attachment 0005 – Price Matrix:

Attachment 0005 – Price = Submit Government provided format. No page limit to supporting Excel worksheets.

Volume IV, Agreement Documentation

Offeror Cover Letter, Teaming Agreements, Terms and Conditions, and other content as defined in these instructions

Return with Filename(s):

VendorName_Vol_IV_Docs_W15QKN-19-R- 06JL.pdf

No page limit.

B.4.2 Page Limitations:

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read, and will not be considered in the evaluation of the proposal. Table 3 above contains the page limitations. Any Table of Contents (which are not required) will not count against page count.

B.4.3 Page Size and Format:

Two Page Formats are defined:

Format 1: Each face of an 8.5 x 11 inches sheet of paper, with the digital submission viewed in print format.

Format 2: Each face of an 8.5 x 14 inches sheet of paper, with the digital submission viewed in print format. This format is designated for .xlsx Attachments, Offeror Solution Diagrams and the Technical Schedule only.

Each volume shall be clearly identified and the text shall begin at the top of each page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date, and PPON number in the header and/or footer.

Format 1: Adobe or Microsoft Word (.pdf, .doc or .docx file extensions) files shall use the following page set-up parameters:

Margins (Top, Bottom, Left, Right) = 1.0 inch

From Edge Header, Footer = 0.5 inches Page Size, Width = 8.5 inches Page Size, Height = 11 inches Paragraphs = Separated by at least one blank line

Format 2: Microsoft Excel (.xls or .xlsx file extensions), Solution Diagram files (.pdf) and Technical Schedules shall use the following page set-up parameters:

Margins (Top, Bottom, Left, Right) = 1.0 inch From Edge Header, Footer = 0.5 inches Page Size, Width (Maximum) = 11 inches Page Size, Height (Maximum) = 14 inches

Except when specifically addressed in the instructions for an Attachment, the reproduced sections of the PPON document and the items in B.4.4, the font type shall be Arial and text size shall be no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Pages shall be numbered sequentially by volume. For electronic submissions, page limitations shall be calculated as though the document were printed as a hard copy proposal.

B.4.4 Tables, Charts, Graphs, and Figures – to include Solution Diagrams in Subfactor 2:

These displays shall be uncomplicated, legible, and where they exceed one page, shall follow B.4.3 Page Size standards. For tables, charts, graphs and figures, the text shall be no smaller than 10 point font size. For electronic submissions, page limitations shall be calculated as though the document were printed as a hard copy proposal. For the Solution Diagrams only – font and sizes may be different (as small as 8) but must be legible, B.4.5 Glossary/Acronym List: Each non-price volume shall contain a Glossary/Acronym List of all abbreviations/acronyms used and a definition for each within that volume. Glossaries of abbreviations and acronyms do not count against the page limitations for their respective volumes.

B.4.6 Stand Alone Volumes: Each volume shall be written on a stand-alone basis so that its contents may be evaluated with no 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. Within a proposal volume, cross-referencing is permitted where its use would conserve space without impairing clarity.

B.4.7 Pricing Information Location: Pricing information of any kind shall NOT be included in Volume I – Technical, Volume II – Demonstrated Performance, and Volume IV – Agreement Documentation; it shall only appear in Volume III –Price.

B.4.8 Number of Copies and Digital File Format:

The Proposal shall be submitted in electronic (searchable) format and organized as defined in B.4.1. Self-extracting .exe files, hyperlinks, and ZIP files are not acceptable. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office or searchable Adobe Acrobat (.pdf). Use separate files to permit rapid location of all portions, including Factors, Attachments, exhibits, and annexes, if any.

B.5 INSTRUCTIONS FOR PREPARATION OF PROPOSAL PART 1 AND PROPOSAL

PART 2 CONTENT:

Offerors shall submit a complete response to instructions for Step 1 information no later than the response date and time specified in paragraph B.2.1.3.A.

Step 2: Upward Invite A – Submit (written) Proposal Part 2: Offerors shall submit a proposal, containing all volumes, documents and attachments, by the date and time specified in paragraph B.2.1.3.D.

B.5.1 Step 1: Proposal Part 1 Submission Content.

The Offeror shall submit the Proposal Part 1 information in compliance with stated instructions below.

A. Offeror Letter: Offeror shall provide a Cover Letter – Page Limit: 2 Pages, and shall include:

1) Name for the Prime Company proposed along with the following information:

point of contact (name, phone, and e-mail), corporate address, DUNS, CAGE Code and confirmation for SAM.gov registration for NAICS 518210 and Small Business Administration Size Category.

2) Facility Clearance Level (of Prime) and Security Management Office (SMO) Code. (See Attachment 0006 DD 254 for additional Security Details)

3) Table that lists: Proposed Team Member Company Names, DUNS, CAGE and as applicable the status as Small Business Category, Nonprofit Research Institute, with designation as a Non-traditional or Traditional Defense Contractor.

4) Include the appropriate statement as applicable:

“The EITaaS Solution proposed includes a Cloud Solution approved with a Provisional Authority at Impact Level 5.”

Or “The EITaaS Solution proposed does not include a Cloud Solution.”

5) Proposal is valid for a minimum of 24 months/730 days

6) Authorized Offeror Representative(s) POC(s) and signature(s)

B. Attachment 0001 – DD Form 2345: Complete per the instructions on the form. This form, when properly filled out and submitted, permits the release of the Government Pilot Site Survey Data (SOO Enclosures 0003a1-4, 0003b1-4, 0003c, 00003d1-2) and “as-is” Network Diagrams to the Data Custodian name(s) on the form.

NOTE 1: Offerors are encouraged to submit an approved, active DD2345 as soon as the release date of this PPON in accordance with the instructions located in Section B.2.3, using the AMRDEC SAFE Site.

NOTE 2: An approved DD2345 must be submitted for all team members (individual entities) that require access to Pilot Site Fact Sheets using the AMRDEC SAFE Site.

C. Attachment 0002 – Affirmation of Business Status Certification (ABSC) Form:

Complete per the instructions on the form. This form, when properly filled out by each Prime (Offeror) and Team Member and submitted provides the Government with the information required in accordance with 10 U.S.C. § 2371b to determine that the Offeror (and Team members) are eligible to receive an OT Agreement Award.

D. Cloud Service Provisional Authority Memo(s) for the Proposed Solution: The Offeror must first identify if an on-premises or Cloud-based solution is contemplated. If proposing a Cloud component as part of the EITaaS Solution, the Offeror shall provide a copy of the Department of Defense (DoD) Provisional Authority memo(s) and/or certificate(s) from the Defense Information Systems Agency (DISA) with Cloud Security Information Impact Level 5 (IL 5) for the proposed Cloud Service Offerings (e.g., Infrastructure as a Service (IaaS), Platform as a Service (PaaS), or Software as a Service (SaaS) cloud service models). No Page Limit.

E. External (3rd Party) Certification or Designation as a top tier “Managed Service Provider” for a DoD Cloud Service Offering: If proposing a Cloud component as part of the EITaaS Solution as a Cloud reseller, the Offeror shall provide a designation as a top/highest tier Vendor from the Cloud Provider. No page limit.

F. Attachment 0003 Demonstrated Performance Record: Complete per the instructions in Attachment 0003. The “Proof Point” is defined as: A claim of performance supported with objective evidence. A statement/example that offers objective and verifiable evidence of the claim, be it for quality, importance or uniqueness of a capability, of a product or of a service delivery.

For Table 1, each Qualification # 1 – 8, information provided shall be:

Verifiable from the information provided or from public information

Relevant to the EITaaS SOO paragraph identified (in the Proof Point)

For Table 2, each Demonstrated Performance Record # 1 – 4 (up to 4), and specifically any “Proof Point” information provided with the record shall be:

Verifiable from information provided or public information

Relevant to the EITaaS SOO paragraph identified (in the Proof Point).

Relevance is defined in Section C.

F.1 All Demonstrated Performance Records shall represent relevant performance as a Prime under Federal / Department of Defense (DoD) (e.g. Department of Home Land Security, Army, Navy, Air Force, Marine Corps, Defense Logistics Agency (DLA)) Contracts, Task Orders, Agreements and/or projects or as a Prime under Commercial Contract / Agreement. Records from Team Members are acceptable as long as the Record clearly shows that they were the Prime on the Record Performance.

NOTE: The Government reserves the right to use data obtained from other Government sources (i.e. the Contractor Performance Assessment Reporting System (CPARS) or Virtual Contracting Environment (VCE)) and public sources, in addition to the data provided in the Offerors proposal. However, the Government is under no obligation to search for additional information in order to identify contract/agreement demonstrated performance record references.

B.5.2 Step 2: Upward Invite A –Proposal Part 2 Submission Content

B.5.2.1 Volume I: Factor 1 – Technical

This Volume shall describe the Offeror’s proposed technical approach and solution for meeting the performance and capability requirements specified in this PPON and the SOO, to include its supporting documents. Responses will be evaluated as defined in Section C - Evaluation Factors for Award. This submission includes four Sub-factors:

A. Sub-factor 1 – Technical Approach (Format in accordance with these instructions)

B. Sub-factor 2 – Solution Diagrams (Offeror format)

C. Sub-factor 3 – Technical Schedule (Offeror format, Gantt View)

D. Sub-factor 4 – Solution Hardware / Software List (Return Government Attachment 0004)

B.5.2.1.1 Sub-factor 1 - Technical Approach The Offeror shall provide an introduction that includes any Technical Approach assumption(s). The Technical Approach narrative shall include (Offeror shall identify the SOO Paragraphs as they are addressed):

A. Describe how the Offeror’s proposed EITaaS Solution and associated enabling technologies will meet the requirements of the SOO paragraph 3 Scope.

B. Describe the proposed EITaaS Solution and associated enabling technologies that currently meet and/or will meet the Objectives (functional and technical requirements) provided in SOO paragraphs 4.1 Available, 4.2 Resilient, 4.3 Secure, with the associated metrics in SOO paragraph 4.8, Success Metrics and Performance Thresholds, Table 1 and other SOO paragraphs as appropriate.

C. Describe the proposed EITaaS Solution and associated enabling technologies that currently meet and/or will meet the Objectives (functional and technical requirements) provided in SOO paragraphs 4.4 End User Experience with the associated metrics in SOO paragraph 4.8, Success Metrics and Performance Thresholds, Table 1 and other SOO paragraphs as appropriate.

D. Describe the proposed EITaaS Solution and associated enabling technologies that currently meet and/or will meet the Objectives (functional and technical requirements) provided in SOO paragraphs 4.5 Ability to Scale with the associated metrics in SOO paragraph 4.8, Success Metrics and Performance Thresholds, Table 1.

E. If necessary, Offerors should submit updated ABSC(s). These will not count against page limitations.

B.5.2.1.2 Sub-factor 2 – Solution Diagrams Provide four Solutions Diagrams, formatted in Landscape view, with content as instructed below. Within each Diagram (Network Flow and Services) for the EITaaS Solution and support, include all three FY19 Pilot Sites: Army Futures Command Headquarters (AFC HQ), Austin TX; Fort Polk, LA and Camp Roberts, CA (SOO Figure 1, for evaluation purposes).

A. Network Flow Diagrams: Provide two logical Network Flow Diagrams, one Non-classified Internet Protocol (IP) Router Network (NIPRNet), and one Secret Internet Protocol Router Network (SIPRNet) depicting, at a minimum:

A.1 Logical network flow for ICAN and WAN that connect to services depicted in SOO Figure 2 and to existing other Government and non-Government sites.

A.2 How the EITaaS Solution will integrate with any existing network infrastructure for the initial Pilot Site, designated as Ft Polk (for evaluation purposes).

A.3 How the EITaaS Solution extends or scales to support the remaining two Pilot Sites designated as AFC HQ, Austin TX; and Camp Roberts, CA.

A.4 Include all switches, routers, security components (e.g., firewalls, Intrusion Detection Systems (IDS), Intrusion Prevention System (IPS), Wireless Intrusion Detection Systems (WIDS), or proxies) and other network components (e.g., load balancers, wireless access points, circuits) for wire and wireless network infrastructure.

B. Logical Systems and Services Diagrams: Provide two Logical Systems and Services Diagrams (one NIPRNet, and one SIPRNet) depicting, at a minimum:

B.1 How the EITaaS Solution delivers the systems and services depicted in SOO Figure 2 and to existing services provided by other Government or non- Government providers.

B.2 How the EITaaS Solution how will integrate with any existing infrastructure for the initial Pilot Site, designated as Ft Polk (for evaluation purposes).

B.3 How the EITaaS Solution extends or scales to support the remaining two Pilot

Sites designated as AFC HQ, Austin TX; and Camp Roberts, CA.

B.4 Include all servers, storage devices and locations, End user devices, mobile devices, video collaboration, telephony and unified communications systems.

B.5 Identify access management systems and their integration on the ICAN and

WAN.

B.5.2.1.3 Sub-factor 3 – Technical Schedule:

A. Provide a proposed Technical Schedule (Gantt View, landscape layout) for the EITaaS Solution tasks and support to meet the SOO requirements for the Phases I – V, 36 month period of performance at Fort Polk, LA (SOO Figure 3, Row B).

B. At a minimum, include in the schedule the tasks associated with SOO performance paragraphs 4.0, 4.1 – 4.8. Within the schedule, identify any known critical path, dependencies (internal and external to the Offeror/Team or EITaaS Solution) and constraints in meeting SOO Table 1 Success Metrics, Definitions and Performance Thresholds. Within the schedule include all other tasks within the SOO as appropriate for the proposed EITaaS Solution. For Government evaluation purposes only (to provide all Offerors with the same start date), the Technical Schedule shall reflect dates based on Days After Agreement Award, with the Award date of 1 September 2019.

B.5.2.1.4 Sub-factor 4 – Solution Hardware/Software List (Attachment 0004) A. Follow the instructions within the Attachment 0004 at Tab 1. Definitions are provided at Tab 2.

B. Submit the list of EITaaS Solution Hardware and Software at Tab 3. At a minimum, provide the EITaaS Solution Hardware and Software components to meet the SOO requirements at all three FY19 Pilot Sites: AFC HQ, Austin, TX; Fort Polk, LA; and Camp Roberts CA (SOO Figure 1, for evaluation purposes). Within Tab 3. For Columns F. Commercial Items, G. Deployed in Government, and I. Accredited / Approved by the Government: Any Responses of “No” shall be accompanied by text in Column I.

Additional Comments.

B.5.2.2 Volume II: Factor 2 – Demonstrated Performance Attachment 0003 Carried forward from Proposal Part 1…