OTA_PPON_GCSS-Army_DISCOPS_v1-0_2021_03_23.pdf

PPON – GCSS-Army DISCOPS Version 1.0, 23 March 2021

Prototype Project Opportunity Notice:

Global Combat Support System – Army Disconnected Operations (GCSS-Army DISCOPS)

Prototype

Solicitation Number: W15QKN-21-R-0G91

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

Table of Contents

SECTION 1 – EXECUTIVE SUMMARY

1.1 Purpose & Authority

1.2 Background

1.3 Acquisition Approach

SECTION 2 – DEFINITIONS and ELIGIBILITY

2.1 Definitions

2.2 Eligibility

SECTION A – ACQUISITION PROCESS

A.1 Acquisition Process Steps A.2 Notice of Advisory Support and Pre-Proposal / Pre-Award Requirements

B – GENERAL INSTRUCTIONS AND NOTICES TO OFFERORS

B.1 GENERAL INSTRUCTIONS

B.2 RESPONSE FILE SUBMISSION INSTRUCTIONS

B.3 Step 1 and Step 2 PROPOSAL ORGANIZATION AND FORMAT B.3.1 Step 1 and Step 2 Proposal Organization B.3.2 Page Limitations:

B.3.3 Page Size and Format:

B.3.4 Tables, Charts, Graphs, and Figures – to include Oral Presentation and the

Solution Diagrams in Subfactor 2:

B.3.5 Glossary/Acronym List:

B.3.6 Stand Alone Volumes:

B.3.7 Pricing Information Location:

B.3.8 Number of Copies and Digital File Format:

STEP 1: PROTOTYPE PROJECT OPPORTUNITY NOTICE (PPON) – Instructions and Evaluation Criteria for Oral Presentation and Technology Demonstration #1 with Corporate / Public Data

S.1. Instructions for Step 1:

S.1.1 Offeror Gate Information:

S.1.1.1 Offeror Letter – Page Limit:

S.1.1.2 Attachment 0001 – DD Form 2345:

S.1.2 Oral Presentation and Technology Demonstration #1 - Who:

S.1.3 Where:

S.1.4 When (Date / Time):

S.1.5 When (Details):

S.1.6 How and What (Oral Presentation):

SE.1 Step 1 Evaluation Criteria SE.1.1 Step 1: Evaluation of the Oral Presentation and Technology Demonstration #1

SE.1.2 The Oral Presentation will be evaluated to determine:

SE.1.3 The Technology Demonstration #1 will be evaluated to determine:

SE.1.4 Order of Importance and Basis of Selection for Step 2 (Upward Invite #1):

SE.1.5 Step 1 – Basis of Selection for Upward Invite #1 (move to Step 2):

STEP 2: UPWARD INVITE #1 – Instructions for and Evaluation Criteria for Written ii

Proposal S.2. Step 2 Instructions:

S.2.1 Volume I: Factor 1 – Technical Written Proposal Content Instructions S.2.1.1 Subfactor 1 - Technical Approach S.2.1.2 Subfactor 2 – Solution Diagrams S.2.1.3 Subfactor 3 – Technical Schedule:

S.2.1.4 Subfactor 4 – Solution Software List (Attachment 0003 GCSS-Army_Solution-

SW_List) S.2.2 Volume II: Factor 2 – Price Matrix (Attachment 0004 GCSS-Army_Price_Matrix)

S.2.3 Volume III: Agreement Documentation S.2.4 Technical Exchanges and/or Submit Final Proposals SE.2 Step 2: Written Proposal Evaluation Factors, Order of Importance and Basis of

Selection for Agreement Award SE.2.1 Step 2 – Written Proposal Evaluation Factors and Order of Importance SE.2.1.1 Order of Importance for the Written Proposal:

SE.2.2 Basis of Selection for Step 3 Agreement Award (FY21) SE.2.3 Written Proposal Evaluation Approach SE.2.3.1 Evaluation of Volume I: Factor 1 – Technical SE.2.3.1.1 Subfactor 1 – Technical Approach SE.2.3.1.2 Subfactor 2 – Solution Diagrams SE.2.3.1.3 Subfactor 3 – Technical Schedule SE.2.3.1.4 Subfactor 4 – Solution Software List (Attachment 0003 GCSS-

Army_Solution-SW_List) SE.2.3.1.5 Technical Factor Rating Definitions SE.2.3.2 Volume II: Factor 2 –Price SE.2.3.4 Volume III – Agreement Documentation

STEP 3: PROTOTYPE AGREEMENT AWARD

SE.3 STEP 3: AGREEMENT AWARD

STEP 4: PHASE 1 PROTOTYPE DEVELOPMENT AND TECHNOLOGY

DEMONSTRATION #2 – Instructions and Evaluation Criteria

S.4 Step 4: Prototype Phase 1 Instructions SE.4 Step 4: Prototype Phase 1 Tech Demo #2 Evaluation Criteria SE.4.1 Upward Invite #2 Phase 2 Start

STEP 5: PHASE 2 PROTOTYPE DEVELOPMENT AND TECHNOLOGY

DEMONSTRATION #3 – Instructions and Evaluation Criteria

S.5 Step 5: Prototype Phase 2 Instructions SE.5 Step 5: Prototype Phase 2 Tech Demo #3 Evaluation Criteria SE.5.1 Upward Invite #3 Phase 3 Start

STEP 6: PHASE 3 PROTOTYPE INTEGRATION ASSESSMENT AND PRODUCTION

AWARD – Instructions and Evaluation Criteria

S.6 Step 6: Prototype Phase 3 Instructions SE.6 Step 6: Prototype Phase 3 Integration Assessment Evaluation Criteria SE.6.1 Upward Invite #3 – Production Negotiations:

iii

Figure 1 GCSS-Army Prototype Project Source Selection Steps 1 – 3 Figure 2 GCSS-Army DISCOPS Prototype Project Source Selection Steps 4 – 6

Table 1 – Offeror Response Due Dates (All Time are 24hr Clock, Eastern Daylight Time

(EDT))

Table 2 – Agreement Points of Contact Table 3 – Question and Comment Format Table 4 –Step 1 & 2 File Submission, Organization & Page Limits Table 5 – Offeror Names: Oral Presentation & Tech Demo #1 Table 6 –Tentative Schedule: Oral Presentation & Tech Demo #1 Table 7 – Oral Presentation Outline Topics Table 8 – Technology Demonstration #1 Topics Table 9 – Technical Factor: Combined Technical/Risk Ratings Table 10 – Technical Factor: Risk Ratings

GCSS-Army DISCOPS – PPON

SECTION 1 – EXECUTIVE SUMMARY

1.1 Purpose & Authority1

The purpose of this Prototype Project Opportunity Notice (PPON) is to receive from Industry responses to the Government requirement for the Global Combat Support System – Army (GCSS- Army) Disconnected Operations Solution (DISCOPS) Prototype Project. This document provides the six Steps of the source selection process, the instructions for each Step, and the associated evaluation criteria. Please note that the instructions and criteria for Steps 2-6 are subject to change.

This document is broken up as follows: Sections 1-2 are the Executive Summary and Definitions & Eligibility. Section A provides an overview of the entire planned Acquisition Process. Section B provides the General Instructions to Offerors. Step 1 through Step 6 provide the detailed Step Instructions (S.1. – S.6.) and the Step Evaluation Criteria (SE.1. – SE.6.) for each Step.

This PPON Solicitation is a full and open competition. As described below, there are six Steps to this competitive process. To enter Step 1 requires the Offeror to submit an Oral Presentation and Technical Demonstration #1 (with Corporate/Public Data). To move from Step 1 – full and open – to Step 2 and beyond requires the Oral Presentation and Technical Demonstration #1 and later submissions to be determined to be the most beneficial to the Government at each Step in accordance with the Evaluation Criteria for that Step. Offerors that are determined to be the most beneficial to the Government at Step 1 will receive Upward Invite #1 to submit a Written Proposal in response to the Performance Work Statement (PWS). Those Offerors that receive Upward Invite #1, to submit a Written Proposal at Step 2, will receive an update of this document.

The Government intends to award one or more Other Transaction Agreements (OTA) under the authority of 10 U.S.C. § 2371b. Offerors are hereby notified that the Government will only provide funding of a “Not to Exceed (NTE) – Fixed Amount” per award for Prototype Development Phases 1 and 2, and Prototype Integration Phase 3 (totaled for Award Value). For Phase 1, the NTE is $2,500,000, Phase 2 the NTE is $3,300,000, and Phase 3 NTE $1,000,000 for a total value of NTE $6,800,000. Each Awardee selected will implement an approach using commercially available solution(s) to demonstrate a GCSS-Army DISCOPS prototype capability. [See Section 2.1 for a definition of “commercially available.”]

1.2 Background

The Global Combat Support System–Army (GCSS-Army) is one program comprised of two primary components—the GCSS-Army Enterprise Resource Planning (ERP) Solution and Army Enterprise Systems Integration Program (AESIP) Hub services. The GCSS-Army ERP Solution is an open architecture-based tactical logistics system that enhances combat effectiveness and ensures warfighting readiness. AESIP Hub directly supports the Army Business Strategy to establish a federated ERP environment, linking the GCSS-Army tactical level logistics system to the Logistics Modernization Program (LMP), which provides national level logistics. Together GCSS-Army, AESIP Hub services, and LMP provide an End-to-End (E2E) logistics capability.

The Army has documented the requirement in the Statement of Need (SoN): Global Combat Support

1 For additional information on Other Transactions in the Department of Defense (DoD), please refer to Other Transactions Guide, Version 1.0, dated November 2018 https://www.dau.mil/guidebooks/Shared%20Documents%20HTML/Other%20Transactions%20(OT)%20Guide.aspx

System – Army (GCSS-Army) Disconnected Operations Solution (DISCOPS) and will publish a Performance Work Statement (PWS) with Upward Invite #1 at Step 2. The SoN divides the Prototype Project into three phases: Phase 1 and Phase 2 Solution Development and Demonstration on a Closed Network, and Phase 3, Integration Assessment on an Army Network. The PWS will also divide the project into the same three phases and add performance tasks and metrics.

1.3 Acquisition Approach

The Government intends to award one or multiple Not To Exceed (NTE) - Fixed Amount OTAs for the GCSS-Army DISCOPS OTA. As stipulated above, the Government will only fund up to a defined NTE

- Fixed Amount per award for Phase 1, Phase 2, and Phase 3. This document defines the Six Steps in this acquisition approach. Steps 1 and 2 are represent the Proposal Steps. After Step 1, only the Offerors selected as most beneficial to the Government, in accordance with the evaluation criteria in Section SE.1.2 below, will be invited to each subsequent Step. Step 3 represents the Phase 1 Agreement Award(s). Step 4 represents Phase 1 Prototype Development, which is seven (7) months.

Step 5 represents Phase 2 Prototype Development which is nine (9) months. Step 6 represents Phase 3, which is two (2) months of performance. The total potential period of performance is estimated not to exceed 18 months.

Under the authority of 10 U.S.C. § 2371b(f), the Government is contemplating a single follow-on Production OTA award in FY23. See Section A.1.1 for additional information on follow-on Production.

SECTION 2 – DEFINITIONS and ELIGIBILITY

2.1 Definitions

“Agreement” references 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.

"Commercially Available" is a compilation of three definitions listed here:

"Commercial component'' means any component that is a commercial item.

"Commercial computer software" means any computer software that is a commercial item.

"Commercial item” means -

(1) any item, other than real property, that is of a type customarily used by the general public or by non-governmental entities for purposes other than governmental purposes, and-

(i) Has been sold, leased, or licensed to the general public; or

(ii) Has been offered for sale, lease, or license to the general public

(2) Any item that evolved from an item described in paragraph (1) of this definition through advances in technology or performance and that is not yet available in the commercial marketplace, but will be available in the commercial marketplace in time to satisfy the delivery requirements under a Government solicitation.

“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 (NTDC)” 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 are generally 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.

“Resource Share” includes any costs a reasonable person would incur to carry out (necessary to) Statements of Work requirements 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.

2.2 Eligibility

2.2.1 In accordance with 10 U.S.C. § 2371b(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.

2.2.2 Any agreement resulting from this PPON will include language requiring your company to confirm compliance with Section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L. 115-232). If you are unable to confirm compliance with the referenced law, the Government is unable to enter into an Agreement with your company.

SECTION A – ACQUISITION PROCESS

A.1 Acquisition Process Steps Section A provides an overview of the Acquisition Process. Section B provides the common set of Instructions and Notices to Offerors for submission of responses, and Sections Step 1 – Step 6 provide the Step Instructions (S.1 – S.6) and the Evaluation Process with the Evaluation Criteria (SE.1

– SE.6). Figures 1 and 2 below provide an overview of the process of Steps 1 – 6.

Only those Offerors that receive an Upward Invite at the end of a Step will be eligible to proceed to the next Step and remain eligible to receive an award. Each Upward Invite will be determined based on the criteria established in this document (Steps 1 – 6, paragraphs SE.1. - SE.6.).

Figure 1 GCSS-Army Prototype Project Source Selection Steps 1 – 3

NOTE: “Government Evaluation Criteria” in Figures 1 & 2 are summary statements, Offerors shall refer to Sections Step 1 – 6 for the detailed evaluation criteria

Figure 2 GCSS-Army DISCOPS Prototype Project Source Selection Steps 4 – 6

NOTE: “Government Evaluation Criteria” in Figures 1 & 2 are summary statements, Offerors shall refer to Sections Step 1 – 6 for the detailed evaluation criteria

A.1.1 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 and the Success Metrics, as defined in the Performance Work Statement (PWS), are met; or in the event that a particularly favorable or unexpected result is accomplished that justifies transition to production.

[The Government reserves the right to update the PWS published with Upward Invite #1]

A.1.1.1 For this GCSS-Army Disconnected Operations Solution Prototype, follow-on production is defined in the Statement of Need as: The complete solution set of software services/product(s) or license agreements, managed services, or other means that enable an Army enterprise service-wide implementation of the GCSS-Army Disconnected Operations Solution capability to support ~70,000+ total active system users (estimated at this time) or accomplish a particularly favorable or unexpected result that justifies the transition to production. This includes software installed on Government Furnished Equipment (GFE) to include those designated as Disconnected Enabled Devices (DED) and associated Army servers, any cloud hosted Software as a Service (SaaS), Platform as a Service (PaaS), or a hybrid-cloud approach as defined by the solution, that meets the DoD RMF cybersecurity requirements. If a PaaS or Hybrid solution is offered, the

Army requires a solution hosted in an approved Army enterprise cloud environment.

A.1.1.2 Subject to the Availability of Funding and Army Priorities: Although the Government intends to award one follow-on Production award during Fiscal Year 23, Offerors are advised that due to internal Government considerations, there could be a significant delay between the conclusion of the Prototype OTA activities and the 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.2 Notice of Advisory Support and Pre-Proposal / Pre-Award Requirements A.2.1 Notice of Advisory and Assistance Services (A&AS) Support.

A.2.1.1 All Offerors are advised that designated individuals from the firms identified below participated in the preparation of the PPON, the Statement of Need (SoN), and other requirements documents including, but not limited to, cost or budget estimates and will also serve as a non-government advisor supporting proposal evaluation(s). These designated individuals will be authorized access only to those portions of the proposal and discussions that are necessary to enable them to perform their respective duties. The firms identified below, as well as their parents, subsidiaries, and affiliates, may be prohibited from competing on this solicitation and/or providing any services or support to the contract(s) resulting from this solicitation:

• Logistics Management Institute,(a Large Business, provides on-site A&AS to PM ARDAP, PdM GCSS-Army and PEO EIS)

• Soliel LLC (an 8(a) Company, provides on-site A&AS to CASCOM)

A.2.1.2 By direction of the Agreements Officer, the designated individual support contractors, affiliated with the above-listed companies, have executed a Non-Disclosure Agreement 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 Offeror;

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

A.2.2 Organizational Conflict of Interest (OCI) Definitions A.2.2.1 Non-Public and Proprietary Information – Any Government or third-party information that;

a) Is exempt from disclosure under the Freedom of Information Act or otherwise protected from disclosure by statute, Executive order, or regulation; or

b) Has not been disseminated to the general public, and the Government has not yet determined whether the information can or will be made available to the public; or

c) All information designated as proprietary in accordance with law and regulation, and held in confidence or disclosed under restriction to prevent uncontrolled distribution.

A.2.2.2 Competition Sensitive Information – Information relating to the services to be performed by the GCSS-Army DISCOPS Prototype OTA Awardee or, a Subcontractor or any of the Support Service Contractor under the GCSS-Army DISCOPS Prototype Project, the disclosure of which may give a contractor an unfair competitive advantage and undermine the integrity of the Government’s procurement.

A.2.3 OCI Pre-Proposal and Pre-award Requirements All Offerors shall inform the Agreements Officer, prior to the submission of the Offeror’s Step 1 Proposal:

IF the Prime Offeror or any of its affiliates possess or has access to any non-public information relevant to the GCSS-Army Disconnected Operations Solution Prototype Notice ID # W15QKN-21-R-0G91, provided by the Government, either directly or indirectly;

THEN the Offeror shall advise the Agreements Officer of any Organizational Conflict of Interest (OCI) Mitigation Plan actions that the Offeror has taken or proposes to take to resolve the situation.

- or

IF an approved OCI Mitigation Plan documented organizational separation “firewall” has been implemented to mitigate the impact of access to non-public information, the Offeror represents, to the best of its knowledge and belief, that the firewall was implemented as agreed, and was not breached during the preparation of this Offer, THEN the Offeror shall submit a statement citing the OCI Mitigation Plan Non-Disclosure Agreement to the Agreements Officer.

- or

IF an approved OCI Mitigation Plan “firewall” was not implemented or was breached, THEN the Offeror Shall provide additional explanatory information separately (from the proposal) to the Agreements Officer.

- or

IF there was no access to or use of non-public information in the development of the proposal, THEN there is no requirement to inform the Agreements Officer.

*** END of Section A – ACQUISITION PROCESS ***

B – GENERAL INSTRUCTIONS AND NOTICES TO OFFERORS

B.1 GENERAL INSTRUCTIONS

B.1.1 The Offeror’s Written 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 submissions shall be written in the English language and conform to the instructions below.

B.1.2 This document will be updated, potentially at each Upward Invite or preceding the next Step with revised requirements and details for upcoming evaluated Demonstrations and other required submissions to include an updated ROM for Production.

B.1.3 Quality of Response Submissions:

B.1.3.1 Step 1 Oral Presentation and Technology Demonstration #1 Response: All Offeror submissions should represent the Offeror’s best understanding of the required Oral Topics and demonstrate an achievable technical solution.

B.1.3.2 Step 2 Written Proposal Response: For those Offerors that receive Upward Invite #1 – Step 2, Submit Written Proposal – the Offeror’s Written Proposal should contain the Offeror’s best approach to meet the solicitation requirements and instructions while addressing the evaluation criteria.

B.1.3.3 To be considered for award, the Offeror's Step 1 submission of an Oral Presentation / Technical Demonstrations and Step 2 submission of a Written Proposal shall include all data and information requested by these instructions and shall be submitted in accordance with these instructions. The submission of any Step 1 Oral Presentation / Technical Demonstrations and Step 2 Written Proposal shall be compliant with the requirements as stated.

B.1.3.4 The Government reserves the right to reject any Step 1Oral Presentation / Technology Demonstrations or Step 2 Written Proposal that does not comply with these preparation instructions.

B.1.3.5 The submitted Step 1 Oral Presentation / Technology Demonstrations and the Step 2 Written Proposal shall be clear, concise and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The submitted Offeror response shall not simply rephrase or restate the Government requirements, but shall provide convincing rationale to address how the Offeror intends to meet these requirements.

B.2 RESPONSE FILE SUBMISSION INSTRUCTIONS

(with Steps 2 – 6 subject to change) B.2.1 General Proposal Submission Guidelines:

B.2.1.1 The costs of preparing, submitting, and participating in Proposal efforts, to include the Oral Presentation and Technology Demonstration #1, are not considered an allowable direct charge to any Agreement.

B.2.1.2 Separate submissions are required for the Offeror's submission of: the Step 1 Oral Presentation / Technical Demonstration and Step 2 Written Proposal. The Step 1 Oral Presentation with the Associated Gate File(s), and the Step 2 Written Proposal submissions shall all be made through the DoD Safe Access File Exchange (SAFE) website, the details of which are provided below in B.2.4.

B.2.1.3 Offeror Due Dates:

See beta.SAM.gov Solicitation Notice ID W15QKN-21-R-0G91 for Proposal Submission date and time. A reference for the projected dates is in Table 1 below:

Table 1 – Offeror Response Due Dates (All Time are 24hr Clock, Eastern Daylight Time (EDT)) Response Item Due Date (24hr Clock, EDT) A. DD Form 2345 Military Technical Data

Agreement (Approved by the Defense Logistics Agency, required to receive Controlled Unclassified Information

(CUI))

Optionally on or after 25 March Submit “early” on or soon after the day the Government posts this PPON to beta.SAM.gov, by e-mail to the Solicitation POCs in Table 2.

Required (in addition to any optional submission) 13:00 EDT, 30 April 2021 Submit in the Step 1 GATE File as defined in Table 4 (Step 1 submission date also posted on beta.SAM.gov)

B. Questions for: Step 1 Oral Presentation & Tech Demo #1 (1 Set per Prime)

13:00 EDT, 5 April 2021

C. Presenter/Attendee Names 13:00 EDT, 26 April 2021 (Submit by direct e-mail to Table 2)

D. Step 1 GATE File and Oral Presentation Charts, for Oral Presentation and Tech Demo #1

13:00, EDT, 30 April 2021 (Submission date also announced on the beta.SAM.gov page)

E. Step 1 Oral Presentation and Tech Demo #1 (via Government Commercial Virtual Remote environment)

Time/Date assigned 4 – 10 May: Government will set the scheduled Times/Dates (See Table 6)

F. Questions for: Invite #1 Step 2 Proposal (1 Set per Prime)

13:00, Date TBD (estimated as 7 June 2021).

G. Step 2 Proposal and associated files 13:00, Date TBD, (estimated as 21 June 2021)

B.2.1.4 Late Submission:

Any Questions Set, Oral Presentation, Technology Demonstration or Written Proposal submission received by the Government after the exact date and time specified by the Government will be determined as late and may not be considered.

B.2.1.5 Official Transmissions:

a) Amendments to this PPON will be issued via the beta.SAM.gov Combined Synopsis/Solicitation Notice ID W15QKN-21-R-0G91.

b) Official Points of Contact. The Agreements Officer (AO) and Agreement Specialists (AS) are the only Official points of contact for this acquisition process. All communications must be sent, in writing, to both:

Table 2 – Agreement Points of Contact Agreements Officer (AO) Agreements Specialist (AS)

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

Mr. Austin M. Alpaugh austin.m.alpaugh.civ@mail.mil

c) Questions/Comments Format. Any questions and/or comments submitted regarding this

PPON or the posted files shall be submitted in writing by e-mail to the POCs listed above in Table 2 in the format of Table 3 below and shall refer to Subject and Notice ID in the following format:

E-mail Subject: Vendor Name Questions/Comments Notice ID: W15QKN-21-R-0G91 Format the Questions/Comments as depicted in Table 3:

• 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_DISCOPS_Qs_W15QKN-21-R-0G91.xlsx.

Table 3 – Question and Comment Format Offeror Company Name:

Offeror POC Name, E-mail, Phone #:

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

Question/Comment Rationale

(Example) 1.

Rq_Statement_of_Need_GCSS- Army_DISCOPS_2021_03_23.pdf

3 2.3

Will the Army accept a deployable server already approved in the Command Post Computing Environment (CPCE) as part of the solution?

Planning

B.2.1.6 Questions/Comments and Government Responses:

The Government will only accept written questions to ensure that all Offeror inquiries have been addressed either directly or as a compilation of Frequently Asked Questions. Each Offeror shall submit only one set of questions for each Step.

See Section B.2.1.3, Table 1 for the suspense date/time for any questions and/or comments.

B.2.2 Proposal Submission Limits: Offeror responses are limited to one submission per Prime as indicated below:

a) Full and Open to all Offerors: One submission of the Written Response and the associated files

b) Offerors in receipt of Upward Invite #1: One submission of the Step 2 Written Proposal – Volumes I (Technical), II (Price) and III (Agreement Documents).

c) All Offerors shall allow their submitted Proposal to be valid for at least 12 Months/365 Days, or the proposal will not be eligible for consideration for award.

B.2.3 Controlled Unclassified Information (CUI) (On 6 March 2020, DoDI 5200.48, Controlled Unclassified Information (CUI), replaced the DoDM 5200.01 V4 making "FOUO" and other DoD/Federal Government markings obsolete). The Statement of Need Enclosure E, Instructions for Government Furnished Equipment (GFE) & Applied Research Lab (ARL) (Provides details for connection to the GCSS-Army ECC at the Applied Research Lab (Pennsylvania State University)) is marked CUI. To receive the GCSS-Army DISCOPS Enclosure E, CUI file: See PPON Attachment

0001, sample DD Form 2345 Militarily Critical Technical Data Agreement. Offerors that request to receive the CUI GCSS-Army DISCOPS file shall follow the process to first submit and receive an approved DD Form 2345 by coordinating directly with the Defense Logistics Agency Joint Certification Office (JCO). Instructions and the digital form are available at:

https://www.dla.mil/HQ/LogisticsOperations/Services/JCP/DD2345Instructions/

Once a JCO approved form is in hand, see Table 1 to Optionally Submit the Form “early” by e-mail to the Agreement Points of Contact in Table 2 (Agreements Officer and Specialists) and as Required, Submit in the GATE File as defined in Table 4 on the Day the Proposed Step 1 Files are due, (date as defined by beta.SAM.gov). The Government will issue the CUI materials through DoD file transfer website following the process in B.2.4.

NOTE: The CUI files will only be sent to the Data Custodian name and e-mail listed on the approved DD Form 2345, this is not the typical Offeror Proposal Team or Contracts Point of Contact.

B.2.4 Receipt of Government GCSS-Army DISCOPS CUI Files, plus Submission of Step 1 Files (Oral Presentation Slides and associated file) and Step 2 (Written Proposal): Offerors shall receive the Government GCSS-Army DISCOPS file(s) marked as CUI and submit all digital response files through the Department of Defense (DoD) Secure Access File Exchange (SAFE) website, available at: https://safe.apps.mil/

a) Instructions for Authenticated DoD CAC (Common Access Card) holders and guests (unauthenticated 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 8 gigabytes (GB) total for “Drop-off” (upload).

b) To receive a file, Guests (Non-CAC Holders) must request a Drop-off Request Code, no earlier than 14 days prior to the submission due date, by sending an e-mail to the Agreement POCs in Table 2 above.

c) One of the Agreement POCs will generate the DoD SAFE e-mail that will initiate the submission steps:

1) When ready to submit, click on the link within the e-mail that includes the website and the

Drop-off Request Code.

2) Manually enter the other POC e-mails above (Agreements Officer and Specialists).

3) Write a short note describing the files.

4) Select the box “Send me an e-mail when each recipient picks up the files”.

5) Add your response files. Ensure to use the naming convention identified in each Step; in place of any blank spaces in the filename, use underscore “_” or dash “-”

6) Add your files and add a description of the file.

7) Select “Drop-off Files”

8) For your records, print the “Drop-Off Completed” confirmation page.

d) If needed, go directly to the website link above and select the “Help” icon for additional information. Once within Help, a list of frequently asked questions appears. A link to a users’ guide is available at the bottom of the list of menu items, select “+ Where can I find a DoD SAFE user’s guide?” Available at:

https://dl.dod.cyber.mil/wp-content/uploads/dcs/pdf/unclass-DOD_SAFE_User_Guidev0_2d1.pdf

B.3 Step 1 and Step 2 PROPOSAL ORGANIZATION AND FORMAT B.3.1 Step 1 and Step 2 Proposal Organization The Offeror shall submit the Written Proposal as set forth in Table 4 below.

https://www.dla.mil/HQ/LogisticsOperations/Services/JCP/DD2345Instructions/ https://safe.apps.mil/ https://dl.dod.cyber.mil/wp-content/uploads/dcs/pdf/unclass-DOD_SAFE_User_Guidev0_2d1.pdf

Table 4 –Step 1 & 2 File Submission, Organization & Page Limits STEP 1: Oral Presentation and Technology Demonstration #1 with Corporate / Public Data

Oral Presentation / Demo Submission: Filenames and Page Count

Offeror submits the following Gate information thru the DoD SAFE Site:

Offeror Letter

Attachment 0001 – DD Form 2345

Attachment 0002 – Affirmation of Business Status Certification (ABSC)

Return as a combined file with Filename:

VendorName_Gate_W15QKN-21-R-0G91.pdf Page limit by section (Offeror Letter, DD Form(s) 2345 and Form(s) ABSC):

Offeror Letter = Offeror format, 2 page limit Attachment 0001 – DD Form 2345 = Submit a completed and Approved Form 2345. See Instructions – this may ALSO be submitted early to receive CUI data Attachment 0002 – ABSC = Submit a completed and signed Government Form, 2 page limit per entity, no limit to number of entities

Offeror E-mail Tech Demo #1 Names E-mail four names

GCSS-Army DISCOPS Oral Presentation and Tech Demo #1 - Charts

Return with Filename:

VendorName_OralPres_W15QKN-21-R-0G91.pdf Page limit = 20 (including any cover).

Conduct Oral Presentation and Technology Demonstration #1 with Corporate / Public Data

Conduct Oral Presentation and Tech Demo #1 (60 Minutes) in accordance with the detailed instructions provided with the Invite 1.

Use only the charts submitted. No additional files.

STEP 2: Upward Invite #1 – Submit Written Proposal in response to the Performance Work Statement (PWS)

Written Proposal Volume Submission: Filename and Page Count

Volume I, Technical:

Filename:

VendorName_Vol_I_Tech_W15QKN-21-R-0G91.pdf Page limit by section.

Cover and Glossary / Acronym List

Cover = 1 Page, Offeror format not included in 20 page count

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

Table of Contents (Not Required) = No page limit (Not included in 20 page count – Not evaluated).

Volume I, Factor 1 Technical:

Subfactor 1 Technical Approach Subfactor 2 Solution Diagrams Subfactor 3 Technical Schedule Subfactor 4 Solution Software List (Attachment 0003 GCSS-Army_Solution-SW_List)

Page Count by Subfactor:

1. Technical Approach = 20 pages, allocation of pages at Offeror’s discretion.

2. Solution Diagrams = 4 pages total

GCSS-Army DISCOPS Prototype Data Flow Diagrams:

-- Non-classified Internet Protocol (IP) Router Network (NIPRNet) Data Flow Diagram = 1 page -- Systems & Services Diagram NIPRNet = 1 page

3. Technical Schedule = 1 page (MS Project Gantt View)

4. Solution Software List = 10 pages (Govt Attachment 0003 GCSS-Army_Solution-SW_List) Return with Filename:

VendorName_SW_List_W15QKN-21-R-0G91.pdf

Volume II, Factor 2 Price (Attachment 0004 GCSS-Army_Price_Matrix)

Return with Filename:

VendorName_Vol_II_Price_W15QKN-21-R-0G91.xlsx

No page limit.

Attachment 0004 GCSS-Army_Price_Matrix = Submit Government provided format. No page limit to supporting Excel worksheets.

Volume III, 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-21-R-0G91.pdf

No page limit.

B.3.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 4 above contains the page limitations.

Covers are limited to 1 page, any Glossary, Acronym List and/or Table of Contents (which are not required) will not count against page count. For these digital file submissions, page limitations shall be calculated as though the document were printed as a hard copy proposal. Pages shall be numbered by Volume in the Written Proposal.

B.3.3 Page Size and Format:

a) Two Page Formats are defined:

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

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

b) Each Volume of the Written Proposal shall be clearly identified, and the text shall begin at the top of each page. All pages of each shall be appropriately numbered and identified by the complete company name, date, and PPON number in the header and/or footer. Two File Formats are defined:

File 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

File Format 2: Microsoft Excel (.xls or .xlsx file extensions), Solution Diagram files (.pdf) and the Technical Schedule 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 = 14 inches When placed in Landscape Orientation, Width = 14 inches, Height = 8.5 inches

c) Fonts: Text size shall be 12 point Arial Font or larger. Fonts for Headers and Footers shall be 10 Point or larger in any submission. Exceptions for different sizes are when specifically addressed in the instructions for an Attachment, the reproduced sections of the PPON document and the items in B.3.4. Tracking (the space between groups of letters), kerning, (the spacing between letters or characters) and leading values (spacing between line) shall not be changed from the default values of the word processing or page layout software.

B.3.4 Tables, Charts, Graphs, and Figures – to include Oral Presentation and the Solution

Diagrams in Subfactor 2:

These displays shall be uncomplicated, legible, and where they exceed one page, shall follow Section B.3.3 Page Size standards. For tables, charts, graphs, and figures, in the Written Proposal the text shall be no smaller than 10 point font size. For the Solution Diagrams only – font and sizes may be different (as small as 8). The size of any corporate, brand, product, legal entity or other logo artwork, to include embedded fonts may be submitted as per the corporate standard.

B.3.5 Glossary/Acronym List:

Each non-price volume may 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.3.6 Stand Alone Volumes:

Each proposal 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.3.7 Pricing Information Location:

Pricing information of any kind shall NOT be included in Volume I – Technical. Pricing information shall only appear in Volume II –Price and Volume III – Agreement Documentation.

B.3.8 Number of Copies and Digital File Format:

One digital copy of the Step 1 and Step 2 associated files shall be submitted in digital (searchable) format and organized as defined in Section B.3.1, Table 4. Self-extracting .exe files, hyperlinks, and

ZIP files embedded or posted separately are not acceptable. The digital 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.

*** END of Section B – INSTRUCTIONS AND NOTICES ***

STEP 1: PROTOTYPE PROJECT OPPORTUNITY NOTICE (PPON) – Instructions and Evaluation Criteria for Oral Presentation and Technology Demonstration #1 with Corporate / Public Data

S.1. Instructions for Step 1:

Offerors respond to the Prototype Project Opportunity Notice (PPON): Submit the files required below (also listed in Table 4) and Conduct an Oral Presentation and Technology Demonstration #1 using Corporate and or Public Data (this includes any Government data that is publicly available or any Corporate Data “made up” to appear like Government data)). Criteria in Section SE.1.1 will be used to evaluate the Oral Presentation and Technology Demonstration #1. While in Step 1, the Government reserves the right to conduct Technical Exchanges with all active Offerors. In response to PPON - Offerors shall submit a response by the date and time specified in the PPON that includes:

Up to four names of the presenters and the charts in compliance with stated instructions below.

S.1.1 Offeror Gate Information: Return as a combined file with Filename:

VendorName_Gate_W15QKN-21-R-0G91.pdf. Page limit by section (Offeror Letter, DD Forms 2345 and Form ABSC).

S.1.1.1 Offeror Letter – Page Limit: Submit within the Gate File, 2 Pages that shall include:

a) 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 www.SAM.gov registration for NAICS 541690 - Other Scientific and Technical Consulting Services and the Small Business Administration Size Category.

b) 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.

c) Include the appropriate statement as applicable:

“The GCSS-Army Disconnected Operations Prototype Solution proposed includes a Cloud

Solution approved with a Provisional Authority at Impact Level 5.”

Or – “The GCSS-Army Disconnected Operations Prototype Solution proposed includes a

Cloud Solution approved with a Provisional Authority at Impact Level 4 with the capability to achieve IL5.”

Or – “The GCSS-Army Disconnected Operations Prototype Solution proposed includes a Cloud Solution approved with a Provisional Authority at Impact Level ‘#’ [insert approved level], with a plan and to achieve IL 5.”

Or – “The GCSS-Army Disconnected Operations Prototype Solution proposed does not include a Cloud Solution.”

d) Proposal Validity Date for 12 months / 365 days.

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

f) A statement acknowledging acceptance of the Terms and Conditions (minor revisions will be considered).

S.1.1.2 Attachment 0001 – DD Form 2345: Within the Gate File, submit completed and DLA Approved DD Form(s) 2345 for each entity that will be given access to the CUI Data Statement of Need Enclosure E, Instructions for Government Furnished Equipment (GFE) & Applied Research Lab (ARL) (Provides details for connection to the GCSS-Army ECC at the Applied Research Lab (Pennsylvania State University)). See Attachment 0001 Instructions. Note: The DD Form(s) may ALSO be submitted early to receive CUI data as soon as the Government releases this information. See Table 1 and Table 2 for early submission times and method.

S.1.1.3 Attachment 0002 – ABSC: Within the Gate File, submit a completed and signed Government Form, 2 page limit per entity, no limit to number of entities.

S.1.1.4 Four Names for Oral Presentation Presenters: Submit by e-mail to the Solicitation POCs no later than the date/time announced in the PPON Table 1.

S.1.1.5 Oral Presentation Charts: Submit by DoD SAFE Site to the Solicitation POCs no later than the date/time announced in the PPON Table 1 (also posted on beta.SAM.gov page).

S.1.1.6 Conduct Oral Presentation: Conduct the Presentation on the date/time scheduled by the Solicitation POCs.

S.1.2 Oral Presentation and Technology Demonstration #1 - Who:

a) The Offer Presentation Team shall consist of up to four Offeror personnel. Offeror attendees / presenters must be current employees for the Prime Offeror or designated Team Member.

b) Only the names submitted in the Response to Oral Presentation & Tech Demo #1 date/time assignment e-mail may attend.

c) Any substitutions to the submitted names should be directed to the Agreements Officer and Specialist before the presentation.

d) Once the Oral Presentation is started, there will be no substitutions and departures will only be permitted for emergency events. Submit the names and data in accordance with Table 5:

Table 5 – Offeror Names: Oral Presentation & Tech Demo #1 # NAME (Mr./Ms. First-Mi-Last) Company Affiliation GCSS-Army

DISCOPS Support Role

1. EXAMPLE: Ms. Jane Q. Public Best Global Logistics Software Inc Project Manager 2.

3.

4.

Note: The Government attendees will include designated Support Contractors (advisors) who have signed the appropriate Non-disclosure agreement. (See Section A.2)

S.1.3 Where:

The Oral Presentation / Technology Demonstration #1 will be held at a location to be designated in the Government Invitation letter. At the time of these instructions, this is planned as an online, virtual event (MS Teams).

S.1.4 When (Date / Time):

Offerors will be scheduled in a random order and the Government will provide a date / time reservation (via an e-mail from the Agreements Officer). See PPON Schedule for Government projected date of notifications. The Government projects that Offeror Oral Presentation / Technology Demonstration #1 time slots will begin no earlier than 9:00 AM EDT on the date indicated in the schedule and continue until all Offerors are complete.

S.1.5 When (Details):

Offerors will have a 60-Minute limit for the combined Oral Presentation and Technology

Demonstration #1, with an up to10-minute transition-in and setup before the start, a (up to) 10 Minute Government Questions Session and a 5-minute exit. The Government will control the start/stop time. See a tentative planning schedule in Table 6:

Table 6 –Tentative Schedule: Oral Presentation & Tech Demo #1

Tentative Schedule (Based on 4 Offerors per day, will be adjusted based on the volume of requests. Time allocation inside blocks at Offeror Discretion) 4 Person Offeror Team 09:00 – 09:05 Govt host greets Offeror #1 Team in a designated MS Teams meeting 09:05 – 09:10 :05 Min Offeror Set Up and Audio / Video test Time 09:10 – 10:10 :60 Min (max) Oral / Demo Time (Recorded) 10:10 – 10:20 :10 Min (Not to exceed) Govt Q&A 10:20 – 10:25 :05 Min (max) Offeror signs out of meeting 10:25 – 10:45 :20 Min Govt Team Time 10:45 – 10:50 Govt host greets Offeror #2 Team in a designated MS Teams meeting 10:50 – 10:55 :05 Min (max) Offeror Set Up and Audio / Video test Time 10:55 – 11:55 :60 Min (max) Oral / Demo Time (Recorded) 11:55 – 12:05 :10 Min (Not to exceed) Govt Q&A 11:55 – 12:00 :05 Min (max) Offeror signs out of meeting 12:40 – 13:00 :20 Min Govt Team Time 13:00 – 14:00 :60 Min Govt Break

14:00 – 14:05 Govt host greets Offeror #3 Team in a designated MS Teams meeting 14:05 – 14:10 :05 Min (max) Offeror Set Up and Audio / Video test 14:10 – 15:10 :60 Min (max) Oral / Demo Time (Recorded) 15:10 – 15:20 :10 Min (Not to exceed) Govt Q&A 15:20 – 15:25 :05 Min (max) Offeror signs out of meeting 15:25 – 15:45 :20 Min Govt Team Time 15:45 – 15:50 Govt host greets Offeror #3 Team in a designated MS Teams meeting 15:50 – 15:55 :05 Min (max) Offeror Set Up and Audio / Video test 15:55 – 16:55 :60 Min (max) Oral / Demo Time (Recorded) 16:55 – 17:05 :10 Min (Not to exceed) Govt Q&A 17:05 – 17:10 :05 Min (max) Offeror signs out of meeting 17:10 – 17:30 :20 Min Govt Team Time

S.1.6 How and What (Oral Presentation):

20 chart limit. Overall, 60-minute limit, combined in the same time session with…