ALD_Instructions_Eval_Criteria_FINAL.pdf

ALD Instructions & Evaluation for Industry Response Distribution Statement A: Approved for Public

Release, Distribution is Unlimited

Version 1.0 24 April 2018

Army Leader Dashboard Instructions and Evaluation for

Industry Response to Prototype Project Opportunity

Notice (PPON) Solicitation Number: W15QKN-18-X-01K6

Army Contracting Command – New Jersey, Innovative Concepts Contracting Center (ACC-NJ-IC) Attn: Ms. Trisha Fitton Agreements Officer Building 10, Phipps Road, Picatinny Arsenal, NJ 07806-5000 Phone 973.724.1936 trisha.a.fitton.civ@mail.mil

24 April 2018

ALD Instructions & Evaluation for Industry Response

GENERAL INSTRUCTIONS for Prototype Proposal Opportunity Notice (PPON)

Section A. Administrative Details

A.1 Administrative Instructions to Offerors The Other Transaction (OT) acquisition process for this PPON includes six (6) Steps.

Steps one through four (1 – 4) lead to the Statement of Work Phase 1 Agreement Award. Steps five and six (5 and 6) lead to the SOW Phase 2 Agreement Award. Only those Offerors that receive an Upward Invitation will be eligible to move beyond Step 1, to the next Step:

A.1.1 Step 1: Oral Presentation and Software Demonstration (with corporate / public data)

A.1.2 Step 2: Upward Invitation – A:

Step 2.a. Submit (written) Prototype Proposal without price, receive Army Data and

Step 2.b. Conduct Software Demonstration (with provided Army Data)

A.1.3 Step 3: Upward Invitation – B:

Submit final Prototype Proposal, with Price and Conduct Software Demonstration to Senior Army Leaders (with provided Army Data)

A.1.4 Step 4: Agreement Award(s) for Statement of Work Phase 1 (up to 4 Offerors)

** The Government will provide (Step 5, Upward Invitation – C) Instructions and Evaluation Criteria in a separate document to those companies receiving an OT Award in Step 4 **

A.1.5 Step 5: Upward Invitation – C:

Submit (written) updated Prototype Proposal for SOW Phase 2 with price

A.1.6 Step 6: Agreement Award(s) for SOW Phase 2 Prototype Projects (up to 2 Offerors)

See Figure 1 below that provides an overview chart of the process of Steps 1 – 4 (only) for this acquisition, Steps 5 and 6 will be included in the Upward Invitation - C for Step 5.

Upon successful completion of the prototype projects, the Government may enter into a contract or agreement for the follow-on production of one (1) Army Leaders Dashboard.

Figure 1 - ALD Evaluation Steps 1 – 4 (of 6)

A.2 Response for each Step. Each Offeror shall submit only one (1) electronic response (with multiple files) that address the Government Requirements and Instructions for that Step.

A.2.1 Unclassified Process. For the proposal process, no information classified as “Confidential”, “Secret”, or “Top Secret” shall be submitted or included in any proposed Oral Presentation / Software Demonstration or the Prototype Project Proposals.

A.2.2 Offerors will 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

A.2.2.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 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."

A.2.2.2 Upload all response files using the following naming convention, in place of any blank spaces in the filename, use underscore “_” or dash “-“:

ALD_VendorName_FileName_W15QKN-18-X-01K6.xxx.

A.2.2.3 Once at the AMRDEC site, manually enter the below email address to submit response files to:

Agreements Officer: trisha.a.fitton.civ@mail.mil Agreements Specialist: melissa.e.chant.civ@mail.mil

A.2.2.4 After successfully uploading the proposal file(s), the SAFE site will send an e-mail 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 senders e-mail. The package 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.

A.2.2.5 After submitting through SAFE, send a separate notification e-mail stating that a response submission was made to the Points of Contact (Agreements Officer and Contracting Specialist) listed below with the following Subject:

“Vendor Name Notification Submitted PPON: W15QKN-18-X-01K6” The body of the note should be short and include the Offeror Point of Contact.

A.3 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 on time or late based on the Offerors last file “UPLOAD” date/time. The Government highly recommends that Offeror ensure the “UPLOAD” time is before the PPON submission date and time (Eastern Time).

A.3.1 Official Transmissions and Communications.

A.3.1.1 Any Government Amendments will be issued via FedBizOpps.

A.3.1.2 Government Points of Contact. The Agreements Officer (AO) and Agreements Specialist (AS) are the SOLE points of contact for this procurement:

Agreements Officer Ms. Trisha Fitton US Army Contacting Command - New Jersey, Innovative Concepts Contracting

Center, Building 10, Phipps Road, Picatinny Arsenal, NJ 07806-5000 Phone 973.724.1936 trisha.a.fitton.civ@mail.mil

Agreements Specialist:

Ms. Melissa E. Chant US Army Contracting Command - New Jersey, Innovative Concepts Contracting

Center Phipps Rd, Building 10 Picatinny Arsenal, NJ 07806-5000 Phone: 973.724.2886 melissa.e.chant.civ@mail.mil

A.3.1.3 Questions/Comments. Any questions and/or comments submitted regarding this solicitation shall refer to specific text of the solicitation in the following format:

E-mail Subject: VendorName_Q-Cmts_PPON_W15QKN-18-X-01K6.

Format the Questions/Comments in MS Excel (compatible with MS Excel 2013) file as an attachment with file naming convention:

VendorName_Q-Cmnts_PPON_W15QKN-18-X-01K6.xls.

Format the MS Excel file with all Questions/Comments as depicted in Table 1 with column headings at the top of each page when printing:

Table 1 - Question and Comment Format

Offeror Company Name:

Offeror POC Name, E-mail, Phone #

Item # Government File Name or Attch # Page # Para # /

Line Question/Comment Rationale

Questions/Comments and Answers. The AO and AS will field written questions to ensure that all inquiries have been addressed in advance of the response suspense date/time. It is preferred that only one set of questions be submitted by each Interested Party instead of submitting multiple sets of questions. The Government may respond with a compilation of frequently asked questions or a revised document (ex. Statement of Work) as time permits. See the FBO announcement page for the suspense date / time for any questions and / or comments.

SECTION 1 - STEP 1 – ORAL PRESENTATION AND SOFTWARE

DEMONSTRATION #1: Instructions, Evaluation Criteria and Basis of Selection for Upward Invitation

1.1 INSTRUCTIONS – Step 1

1.1.1. These instructions provide details for Step 1 only, response to the Competitive Prototype Proposal Opportunity Notice (PPON). Offerors shall submit the files and attachments defined in Table 2:

Table 2 - Offeror Response for Step 1 – Oral Presentation / Software Demonstration

# Response Item Response File Name Page Limit

1. Offeror Cover

Letter ALD_VendorName_Letter_W15QKN-18-X-01K6.pdf (Offeror letterhead and format with Oral / Demo Names)

1 Page

2. Attachment 001 OT Eligibility

ALD_Attch_001_VendorName_OT_Eligibility_W15QKN-18-X- 01K6.xlsx (Return Government posted file, completed and signed)

Return in Govt Format

3. Attachment 002 Offeror’s Software Solution

ALD_Attch_002_VendorName_Software_W15QKN-18-X- 01K6.xlsx (Return Government posted file, completed and signed)

Return in Govt Format

4. Offeror’s Oral Presentation

ALD_Attach_VendorName_Oral-Demo_Charts_W15QKN-18-X- 01K6.pdf (Offeror format)

20 Charts

5. Army Usage Data Agreement

ALD_VendorName_DUA_W15QKN-18-X-01K6.pdf (Return signed Government provided Data Usage Agreement)

Govt Format

6. Offeror’s Software Demonstration

No file submission, only a “Live” Software Demonstration #1 (with corporate / public data)

No Pages :60 Minutes

1.1.2. Step 1 Note: Offerors shall submit the responses in accordance with the date and time referenced in the PPON posted to FedBizOpps. The Offeror bears responsibility for submitting its offer by the specified date/time. Offerors are solely responsible for all expenses associated with responding to this PPON. No additional information, no written responses (no expansive text), and no cost information shall be submitted in the Step 1 response and any such information transmitted will not be accepted. All Offerors must allow their responses to be valid for a minimum of 365 days from the date submitted. The 365 days account for Source Selection (Software Demonstrations and Proposals), Phase 1 execution and consideration for Phase 2.

1.1.3. Cover Letter. 1 page limit, not evaluated. The content is at the discretion of the Offeror and shall include a table formatted as depicted in Table 3 below (remove the example row) that includes the names of the attendees at the Oral Presentation / Software Demonstration:

Table 3 - Oral Presentation and Software Demonstration Personnel

# NAME (Mr./Ms. First-Mi-Last) Company Affiliation ALD Support Role 0 EXAMPLE: Ms. Jane Q. Public DashboardSoft LLC Project Manager 1.

2.

3.

4.

1.1.4. Army Data Usage Agreement. The Army Data Usage Agreement (DUA) is Appendix 002 to the SOW. Offerors shall sign and return this Government document with no edits, comments or exceptions. Submit this document with the response for Step 2. This document is not evaluated. However, the Army provided data will not be issued until the Government receives this signed DUA. Any response submission that does not include the DUA will be considered incomplete and the Government will not evaluate the written proposal.

1.2 Go / No Go

1.2.1 OT Eligibility (Attch_001). No page limit. Will be screened using Go/No Go

Evaluation. Return Government posted file, signed and completed per the embedded instructions. Go / No Go criteria are in paragraph 1.4 below.

1.2.2 Offeror’s Software Solution (Attch_002). No page limit. Will be initially screened using Go/No Go Evaluation. Return Government posted file, completed per the embedded instructions and signed. Go/No Go and evaluation criteria are in paragraph 1.4 below.

1.3 Oral Presentation / Software Demonstration (with corporate / public data)

1.3.1 Who: Up to four (4) personnel. Offeror attendees / presenters shall not be temporary proposal consultants or business development staff and must be current employees for the Prime Offeror or designated Team Member. The presentation team shall be composed of the designated company personnel proposed as providing direct support to the ALD project effort. Only the proposed names in the Cover Letter may attend. Substitutions to submitted names should be directed to the Solicitation Agreements Officer and Specialist. Once started, there will be no substitutions and departures are permitted only for emergency events.

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

1.3.2 Location: The Oral Presentation / Software Demonstration will be held at a location to be designated in the Government Invitation letter. This is an in-person event and there will be no capability for Teleconference or Video Conference. Only Mobile

Hotspot (AT&T Unite Explore by Netgear™) grade/speed internet is available with a Wi- Fi connection. Offerors are permitted to bring their own Hotspot. Offerors shall assume all risk associated with reliance on any internet connection and/or the transmission speed of any Wi-Fi device. The room will have at least two (2) large monitors, with HDMI connections and cables long enough to reach the conference table (standard HDMI). At least one (1) monitor will be used by the Government to project the Oral Presentation Slides and at least one (1) other monitor will be available for the Offeror’s use for the Software Demonstration. Once confirmed, additional facility details and room information will be posted on www.fbo.gov or that detailed information will be included with the Government Invitation. For planning purpose, use these two Government office sites:

• Primary: 9531 Hall Rd, (Building 1456 PEO EIS), Fort Belvoir, VA 22206

• Alternate: 2530 Crystal Drive, Suite 1700B, Arlington, VA 22202

1.3.3 Date / Time: Offerors will be scheduled randomly and the Government will provide a date / time reservation (via an e-mail from the Agreements Officer) to each Offeror. See attached schedule for Government projected date of notifications. The Government projects that Offeror Oral Presentation / Software Demo #1 time slots will begin no earlier than 9:00 AM EDT on the date indicated in the attached schedule and continue until all Offerors are complete.

1.3.4 How / Details: 60-Minute limit for the combined Oral Presentation and Software Demonstration, with a 15-minute transition-in and setup before the start. The Government will control the start/stop time. See a tentative planning schedule in Table 4:

Table 4 Tentative Schedule for Step 1 Oral Presentation and Software Demonstration

Tentative Schedule (Based on 5 Offerors per day, will be adjusted upon receipt of proposals. Time allocation inside blocks at Offeror Discretion)

4 Personnel Offeror Team

Time TBD by Offeror Offeror #1 Team of 4 arrives at Demo Location and goes through building security 09:00 – 09:05 Govt escort meets Offeror Team and leads to Demo Room

09:05 – 09:20 :15 Min (max) Offeror Set Up Time / connect to large monitor provided by Government, Confirm Government has charts ready

09:20 – 10:20 :60 Min (max) Oral / Demo Time 10:20 – 10:25 :05 Min (max) Offeror packs up is escorted out of the room Time TBD by Offeror Offeror #2 Team of 4 arrives at Demo Location and goes through building security 10:30 – 10:35 Govt escort meets Offeror Team and leads to Demo Room

10:35 – 10:50 :15 Min (max) Offeror Set Up Time / connect to large monitor provided by Government, Confirm Government has charts ready

10:50 – 11:50 :60 Min (max) Oral / Demo Time 11:50 – 11:55 :05 Min (max) Offeror packs up is escorted out of the room 11:55 – 12:25 :30 Min Govt Break Time TBD by Offeror Offeror #3 Team … 12:30 – 12:35 Govt escort meets Offeror Team and leads to Demo Room

1.3.5 Oral Presentation. 20 chart limit. Overall, 60-minute limit, combined in the same time session with Software Demonstration. The allocation of time between the Oral Presentation and the Software Demonstration (and within the two) is at the discretion of the Offeror to cover the topics listed in Tables 5 and 6 below. The Government will project the Charts / Slides and the Offeror shall project the Software Demonstration.

See outline and chart format details below. This Oral Presentation is not a discussion.

The Government will listen to the presentation but will not interact (no questions) with the presenters. The only statements from the Government envisioned include: Time Starts, Repeat [a statement not heard] and Time Stops.

1.3.5.1 The content of the oral presentation shall address the topics outlined in Table 5 below:

Table 5 Oral Presentation Outline

ALD_Attach_VendorName_Oral-Demo_Charts_W15QKN-18-X-01K6.pdf (Offeror format)

20 Charts (Allocated by Offeror discretion)

Oral Presentation Outline

1. Introductions: The Offeror Company / Team

2. Technical Approach – Overview of the prototype solution including Visualization, Data Management, Interfaces, Cyber Security, User Provisioning, and any Features and Benefits

3. Hosting Approach – Overview of hosting and any details if proposing Hosting at Offeror facilities in any phase

4. Demonstrated Experience [of similar projects] of Prime and Participant Company(ies)

1.3.5.2 Oral Presentation Format and Charts (Pages) Limit: 20 Chart Limit. Pages counted as if printed from the file. Cover pages and any transition slides are included in the count of 20. Charts that are not directly addressed and presented in the Oral Presentation will not be considered by the Government. The Government is only issuing broad limitations or restrictions on chart format, font selection, font size, figure size and the mode of presentation:

a. Any text font, figures or objects determined as too small to be legible when printed on 8 x 11” paper (landscape) without assistive magnification will be dismissed as not relevant (as an example Arial font size 9 is acceptable, smaller is not acceptable).

b. The Offeror shall not use gimmicks, embedded videos, embedded apps, animation / motion or music in the Oral Presentation file.

c. The Oral Presentation shall be submitted in Adobe™ .pdf format.

d. The Government will project the submitted .pdf file during the Offeror’s Oral

Presentation / Software Demonstration appointment, using a Government laptop computer.

e. The Offeror shall not project any charts.

f. The Offeror shall not pass any paper to the Government during the Oral

Presentation / Software Demonstration (no slides, handouts, marketing materials or brochures).

g. The Oral Presentation evaluation criteria are provided in paragraph 1.4.3 below.

Table 6 - Software Demonstration Topics (time allocated at Offeror’s discretion)

# Software Demonstration Outline Proposed Approach

1. General User Interface / Visualization and Mobile Display (corporate / pubic data)/Features and Benefits Proposed Software

2. Data Display (representation) to leaders to inform decisions Proposed Software

3 Ease of Use – User Setup, User tools, Dynamic Search, Alerts, Ability to select and “drill down”

Proposed Software

1.3.6 Software Demonstration. Overall, 60-minute limit, combined in the same time session with Oral Presentation. The allocation of time between the Oral Presentation and the Software Demonstration (and within the two) is at the discretion of the Offeror to cover the topics listed in Tables 5 and 6 above. During and throughout the Demonstration, the Offeror shall clearly identify the Software (application) being displayed. The Offeror may refer to the Oral Presentation Charts / Slides that the Government projects, as part of the Software Demonstration. The Software Demonstration shall not contain gimmicks, embedded sound, music, videos, simulations or animations (unless the element is a feature in the released software, such as a “Show Me” or “Help Tool”). The evaluation criteria for the Software Demonstration are provided in paragraph 1.4.4 below.

1.4 EVALUATION CRITERIA – Step 1Go/No-Go Criteria

The submitted response will be first subject to a review against Go/No-Go criteria. The Government will review each submitted response and if all instructions / conditions are met, then the response will be accepted and assessed. The Agreements Officer may, at his/her discretion, contact the Offeror for a clarification. If the Agreements Officer determines that any condition is not met, then the response submission will be rejected and the Offeror will be notified. If rejected, the Offeror will not proceed into the oral presentations/demonstration step and will be eliminated from the competition. The Go / No Go items and the criteria are defined in Table 7 below:

Table 7 - Go / No Go Items and Criteria

Response Item Response File Name Go / No Go Criteria Attachment 001 OT Eligibility

ALD_Attch_001_VendorName_ OT_Eligibility_W15QKN-18-X- 01K6.xlsx (Return Government posted file)

Go = Attachment 001 form – Completed, signed and submitted No Go = Attachment 001 form - Not completed, signed or submitted

Attachment 002 Software Solution

ALD_Attch_002_VendorName_ Software_W15QKN-18-X- 01K6.xlsx (Return Government posted file)

Go = Software proposed meets the definition of Commercial Item (as defined in SOW) No Go = Does not meet the definition

1.4.2 PPON Response Evaluation Criteria

The Government will weigh the relative benefits and risks of each response with consideration of the two (2) items listed in Table 8 below:

Table 8 - Step 1. PPON Evaluated Items

Eval # Response Item Response File Name E.1 Offeror’s Oral Presentation ALD_VendorName_Oral_Charts_W15QKN-

18-X-01K6.pdf E.2 Offeror’s Software Demonstration (corporate / public data) No file submission, only a “Live” demonstration

1.4.3 Offeror’s Oral Presentation

Item E.1, the Offeror’s Oral Presentation, will be evaluated as follows:

a. Technical Approach: The extent to which the Technical Approach is considered sound, and clear as an integrated solution for the required topics (Offeror Company Team, Visualization, Data Management, Interface / Application Protocols, Cybersecurity, User provisioning (access)). The extent to which the Technical Approach is realistic, achievable and will meet the requirements of the Statement of Work, by Phase (Prototypes Phase 1 and Phase 2) with low risk and provides benefit(s) to the Army.

b. Hosting Approach: The extent to which the Hosting Approach gives the Government confidence that the Offeror will meet the requirements of the Statement of Work and can scale to solve the overall ALD problem (SOW paragraph 1.1) with low risk and provides benefit(s) to the Army. The extent to which proposed hosting at Offeror facility meets SOW paragraph 3.3. Security and Infrastructure requirements.

c. Demonstrated Experience: The extent to which the Demonstrated Experience for the Offeror and Team members gives the Government confidence that the Offeror will meet the requirements of the Statement of Work in the Prototype Phase and can scale to meet future requirements for additional data sources and users with low risk.

1.4.4 Offeror’s Software Demonstration (corporate / public data).

Item E.2, the Offeror’s Software Demonstration will be evaluated for three (3) Specific areas as follows:

a. General User Interface: The extent to which the visualization / presentation of data is generally appealing, modern, and informative. The extent to which the solution provides a usable Mobile Display.

b. Data Display (representation) for Corporate Executive Decisions: The extent to which the information presented is visualized in a logical manner that allows Corporate Executives to make informed decisions. The extent to which high risk/interest areas are easily identified.

c. Ease of Use: The extent to which the dashboard system appears intuitive in such a way that a Corporate Executive could easily navigate to gain situational awareness with little or no training. The extent to which the user can easily tailor the dashboard screen. The extent to which user tools permit dynamic search, provides alerts, provides the ability to select and “drill down” on data items.

NOTE for Step 1 - The Government will use a form similar to Appendix A: Oral Presentation and Software Demonstration Usability Assessment Form.

1.5 Basis of Selection at the end of Step 1 (move from Step 1 to Step 2.a. and 2.b.)

1.5.1 Order of Importance.

The Government considers the order of importance of the evaluation criteria for Step 1 to be:

E.2, Offeror’s Software Demonstration is more important than E.1, the Offeror’s Oral Presentation.

There are three Oral Presentation elements rated in descending order of importance: Technical Approach; Hosting Approach; Demonstrated Experience.

There are three Software Demonstration elements rated in equal order of importance: General User Interface; Data Display (representation) for Corporate Executive Decisions; Ease of Use.

1.5.2 Basis of Selection for Upward Invitation – A (move to Step 2): to submit a written Prototype Proposal and Conduct a Software Demonstration (with provided Army Data).

The Offerors that are determined to be most successful at addressing the elements required for the oral presentation and the software demonstration will receive Upward Invitation – A to Step 2.

Offerors that are selected for the Upward Invitation – A will be informed of the results of the evaluation of their Oral Presentation and Software Demonstration.

The Offerors not selected for an Upward Invitation - A will be notified in writing.

SECTION 2 - STEP 2 – WRITTEN PROTOTYPE PROPOSAL AND SOFTWARE

DEMONSTRATION #2 WITH ARMY DATA – Instructions, Evaluation Criteria and Basis of Selection

2.1 INSTRUCTIONS – Step 2

(NOTE: Items described below shall not be submitted as a response to Step 1:

Oral Presentation / Software Demonstration.)

2.1.1 These detailed instructions apply to Step 2 only, response to Upward Invitation

– A to submit a written Prototype Proposal and conduct a Software Demonstration (with provided Army Data).

2.1.2 Upward Invitation – A will include specific information regarding the Software Demonstration # 2 (with provided Army Data) and the due date and time for the written proposal. For the written proposal, the format (page size / font) is provided in paragraph

2.2 below. Submission instructions using the AMRDEC SAFE website are provided in Section A Administrative Details above. The items required for the Step 2 response are listed below in Table 9:

Table 9 - Offeror Response for Step 2:

Response Items for 2.a. Response File Name Page Limit

1. Offeror RSVP Letter to Invitation A – Prototype Proposal

ALD_VendorName_RSVP-A_W15QKN-18-X-01K6.pdf (Offeror letterhead and format, with demo team names)

1 Pages

2. Prototype Proposal

- Technical Approach

ALD_VendorName_Tech_Approach_W15QKN-18-X-01K6.pdf 15 Pages

Response Items for 2.b.

3. Offeror’s Software

Demonstration No file submission, only a “Live” Software Demonstration #2 (with provided Army Data) – Delivered on the schedule date/time

No pages, :30 Minutes

2.1.3 Offerors are solely responsible for all expenses associated with responding to this Upward Invitation – A. The Offeror’s written Prototype Proposal shall follow the format described in paragraph 2.2 below. Evaluation and selection from Step 2 to Step 3, Upward Invitation – B will be conducted based on the criteria in paragraph 2.3 below.

2.2 RESPONSE FOR STEP 2.a. – Detailed Instructions for the written Prototype Proposal. (NOTE: Instructions for 2.b. the Software Demonstration #2 are in paragraph

2.4 below)

2.2.1 Offeror RSVP Letter Invitation – A, Prototype Proposal and Software Demo # 2. 1 page limit, not evaluated, this is the “Cover Letter” for Step 2. The content is at the discretion of the Offeror and shall include a table formatted as depicted in Table 10 below, (remove the example row), with a list of the names of the Offeror attendees at the Software Demonstration (See paragraph 2.4.3 “Who”):

Table 10 - Software Demonstration # 2 (with provided Army Data) Offeror Personnel

# NAME (Mr./Ms. First-Mi-Last) Company Affiliation ALD Support Role 0 EXAMPLE: Ms. Jane Q. Public DashboardSoft LLC Project Manager 1.

2.

2.2.2 The following general formatting requirements apply to the written Prototype Proposal:

• Page limit for the Technical Approach is fifteen (15) pages, (cover sheet not counted)

• 1 Page = when printed, 1 single-sided sheet, 8.5 by 11 inches

• Font = Arial 11 (or larger) single-spaced

• Font in figures and tables = Arial 9 (or larger), but shall be clearly legible

• Margins on all sides (top, bottom, left, and right) shall be at least 1 inch

• Headers and footers within the margins may contain administrative data

2.2.3 Prototype Proposal Technical Approach. 15 page limit, evaluated in accordance with the criteria in paragraph 2.3 below, and shall include a cover sheet with a table (not counted toward the page limit) that includes the contents of Table 11, (see instructions below Table 11):

Table 11 - Prototype Proposal Technical Approach Cover Sheet Summary Table

Prototype Proposal Technical Approach Summary Solicitation Number W15QKN-18-X-01K6 Prime Company / Team Subcontractor / Joint Team Vendor (list each) Proposed Software (major commercial items)

- Visualization Software

- Data Management Software

- Other Software Offeror Point of Contact (name, e-mail, phone) Signature (with date)

Instructions for Table 11:

• Prototype Proposal Technical Approach Summary = Heading, no entry

• Solicitation Number = Use Government provided number

• Prime Company / Team = Name of prime or team

• Subcontractor / Joint Team Vendor (list each) = List each separate legal entity, add rows as needed

• Proposed Software (major commercial items) = Heading, no entry o Visualization Software = Commercial Item name(s) o Data Management Software = Commercial Item name(s) o Other Software = Commercial Item name(s)

• Offeror Point of Contact = Printed response Point of Contact name, e-mail, phone

• Signature (with date) = Legal binding signature and date

2.2.4 Prototype Proposal Outline for: Technical Approach.

The Technical Approach shall contain, as a minimum, the topics listed in Table 12 below (in order) addressing the ALD Statement of Work with the allocation of pages at the Offeror’s discretion:

Table 12 - Offeror Outline for: Technical Approach

Prototype Proposal Outline for: Technical Approach 15 Pages (Allocated by Offeror discretion)

Prototype Proposal Technical Approach Cover Sheet (Not Counted in Page Count)

1. Introduction: The Offeror Company / Team & rationale for selection

2. Technical Approach – Description of the prototype solution including Visualization, Data Management and Interfaces

3. Hosting Approach

4. Cybersecurity Approach – Overview of steps for Risk Management Framework and Initial Authorization to Test (IATT)

5. Demonstrated Experience [of similar projects and scale] of Prime and Participant Company(ies)

2.3 EVALUATION CRITERIA for Step 2.a. – Prototype Proposal

The Government will conduct an evaluation Prototype Proposals(s) submitted in response to Step 2, Upward Invitation – A.

2.3.1 Step 2.a. Evaluation Criteria

Table 13 - Offeror Response for Step 2.a:

Eval # Response Item File Name E.3 Prototype Proposal -

Technical Approach ALD_VendorName_Tech_Approach_W15QKN-18-X-01K6.pdf

2.3.2 Item E.3 Offeror’s Prototype Proposal – Technical Approach.

The Offeror’s submission for E.3 will be evaluated as follows:

a. Technical Approach: The extent to which the Technical Approach, including the rationale for team selection, and the description of the prototype solution is considered sound, realistic, achievable, and presents an integrated approach to meet the requirements of the Statement of Work, by Phase (Prototypes Phase 1 and Phase 2). The extent to which the solution solves the overall ALD problem (SOW paragraph 1.1) with low risk while providing benefit(s) to the Army.

b. Hosting Approach: The extent to which the Hosting, (Phase 1, Phase 2 and enduring solution) is realistic, achievable, and presents an integrated approach to meet the requirements of the Statement of Work and can scale to solve the overall ALD problem (SOW paragraph 1.1) with low risk and provides benefit(s) to the Army.

c. Cybersecurity Approach: The extent to which the proposed approach and hosting facility meets cybersecurity requirements in SOW paragraph 3.3. Security and Infrastructure requirements.

d. Demonstrated Experience: The extent to which the Demonstrated Experience for the Offeror and Team members gives the Government confidence that the Offeror will meet the requirements of the Statement of Work in the Prototype Phase and can scale to meet future requirements for additional data sources and users with low risk. The extent to which the Offeror and Team members have experience relevant to the overall technical, general and reporting requirements stated in the

SOW.

STEP 2.b – Conduct Software Demonstration #2 (with provided Army Data)

2.4 INSTRUCTIONS – for Step 2.b.

2.4.1 For Step 2.b – Conduct a Software Demonstration (with provided Army Data).

Upward Invitation – A will include details about how, when and where the Offeror will be issued (sign for) an encrypted portable hard drive (with a standard USB connector) which contains the Army Data. All invited Offerors will get the exact same data and supporting documentation to include generic “Army use cases” that shall be included in the demonstration. From the date the data is delivered, Offerors will be given at least 10 calendar days to work with the data prior to their scheduled Software Demonstration # 2.

2.4.2 Offerors have no files to submit and shall only conduct a Live Software Demonstration as defined in Table 14:

Table 14 - Offeror Response for Step 2.b:

Response Item Limit

1. Offeror’s Software

Demonstration No file submission, only a “Live” Software Demonstration (with provided Army Data), at designated date/time.

:30 Minutes

2.4.3 Who: Up to four (4) personnel, and may be different from the initial Software Demonstration (with corporate / public data). Offeror attendees / presenters shall not be temporary proposal consultants or business development staff and must be current employees for the Prime Offeror or designated Team Member. The presentation team shall be composed of the designated company personnel proposed as providing direct support to the ALD project effort.

2.4.4 Location: The Software Demonstration (with provided Army Data) will be held at a location to be announced in the Government Invitation letter. This is an in-person event and there will be no capability for Teleconference or Video Conference. Only Mobile Hotspot (AT&T Unite Explore by Netgear™) grade/speed commercial internet is available with a Wi-Fi connection. Offerors are permitted to bring their own Hotspot.

Offerors shall assume all risk associated with reliance on any internet connection and/or the transmission speed of any Wi-Fi device. The room will have at least one (1) large monitor, with HDMI connections and cables to reach the conference table (standard HDMI). Only one (1) monitor will available for the Offeror’s use for the Software Demonstration. Once confirmed, additional facility details and room information will be included with the Government Invitation. For planning purpose, use these two Government office sites:

• Primary: 9531 Hall Rd, (Building 1456 PEO EIS), Fort Belvoir, VA 22206

2.4.5 Date / Time: Offerors will be scheduled randomly and the Government will publish a date / time reservation to each Offeror in accordance with the attached schedule. Presentation time slots will begin no earlier than 9:00 AM EDT on the date indicated in the attached schedule and will continue until all are complete.

2.4.6 How / Details: 30-Minute time limit for the Software Demonstration (with provided Army Data), with a 15-minute transition-in and setup before the start. See Table 15 for a tentative schedule. The Offeror’s Software Demonstration shall cover the topics in Table 16 below. There will not be any allocation of time for an Oral Presentation (No Charts/Slides permitted). The Government will control the start/stop time. Within the Software Demonstration, the allocation of time is at the discretion of the Offeror. During and throughout the Demonstration, the Offeror shall clearly identify the Software (application) being displayed. The Software Demonstration shall not contain gimmicks, embedded sound, music, videos, simulations, or animations (unless the element is a feature in the released software, such as a “Show Me” or “Help Tool”).

The evaluation criteria are in paragraph 2.5 below.

Table 15 Tentative Schedule for Step 2.b Software Demonstration # 2

Tentative Schedule (will be adjusted upon receipt of proposals) (Time allocation inside blocks at Offeror Discretion)

4 Personnel Offeror Team

Time TBD by Offeror Offeror #1 Team of 4 arrives at Demo Location and goes through building security

09:00 – 09:05 Govt escort meets Offeror Team and leads to Demo Room (Door Opens) 09:05 – 09:15 :15 Min (max) Offeror Set Up Time / connect to large monitor provided by Govt 09:20 – 09:50 :30 Min (max) Demo Time 09:50 – 09:55 :05 Min (max) Offeror packs up is escorted out of the room

Time TBD by Offeror Offeror #2 Team of 4 arrives at Demo Location and goes through building security

10:00 – 10:05 Govt escort meets Offeror Team and leads to Demo Room (Door Opens) 10:05 – 10:20 :15 Min (max) Offeror Set Up Time / connect to large monitor provided by Govt 10:20 – 11:50 :30 Min (max) Demo Time 11:50 – 10:55 :05 Min (max) Offeror packs up is escorted out of the room Etc… Offeror #3 Team

Table 16 - Software Demonstration (with provided Army Data) Topics

# Software Demonstration Outline Proposed Approach

1. General User Interface / Visualization and Mobile Display (of Army Data)/ Features and Benefits Proposed Software

2. Data Display (representation) of Army data to Army Leaders to inform decisions (includes responses to Army Use Cases) Proposed Software

3.

Ease of Use – User Setup, User tools, Dynamic Search, Alerts, Ability to select and “drill down” from a Strategic Army View of Units to an Individual Soldier and a single Weapon System

Proposed Software

2.5 EVALUATION CRITERIA for Step 2.b – Software Demonstration #2 (with provided Army Data)

2.5.1 Step 2.b – Software Demonstration #2 (with provided Army Data) Evaluation Items and Criteria

The Government will weigh the relative benefits and risks of each response with consideration of the one (1) item listed in Table 17 below:

Table 17 - Items for Evaluation and consideration for Step 2.b

Eval # Item E.4 Offeror’s Software Demonstration # 2

(with provided Army Data) No file submission, only a “Live” demonstration, 30-Minutes

2.5.2 Evaluation Item E.4, Offeror’s Software Demonstration (with provided Army data).

The Offeror’s submission for E.4 will be evaluated as follows:

a. General User Interface (with provided Army data): The extent to which the visualization / presentation of data is generally appealing, modern, and informative.

The extent to which the solution provides a usable Mobile Display.

b. Data Display (representation) for Army Leader Decisions: The extent to which the information presented is visualized in a logical manner that allows Army Leaders to make informed decisions. The extent to which high risk/interest areas are easily identified. The extent to which the demonstration adequately addressed the Army (provided) use cases in a manner that allows Army Leaders to make informed decisions. NOTE: These use cases will be different than the Demo to Senior Leaders (Step 3).

c. Ease of Use: The extent to which the dashboard system appears intuitive in such a way that an Army Leader could easily navigate Army Data to gain situational awareness with little or no training. The extent to which the user can easily tailor the dashboard screen. The extent to which user tools permit dynamic search, provides alerts, provides the ability to select and “drill down” on data items from a Strategic Army View of Units to an Individual Soldier and a single Weapon System.

NOTE: For Step 2.b - The Government will use a form similar to Appendix B: Software Demo # 2 & # 3 Software Usability Assessment Form, in addition to other notes, to support the evaluation of E.5.

2.5.3 The Government reserves the right to conduct exchanges with offerors prior to completion of this step should the Government determine that the exchanges are necessary to ensure the information conveyed is understood. Any such exchange(s) will be scheduled and controlled by the Agreements Officer.

2.6 Basis of Selection at the end of Step 2 (move from Step 2 to Step 3)

2.6.1 Order of Importance

The Government considers the order of importance of the evaluation criteria for Step 2 to be: E.4, Offeror’s Software Demonstration is more important than E.3, the Offeror’s Prototype Proposal - Technical Approach.

There are three Prototype Proposal – Technical Approach elements rated in descending order of importance: Technical Approach; Hosting Approach;

Cybersecurity Approach; Demonstrated Experience.

There are three Software Demonstration elements rated in equal order of importance: General User Interface/Visualization and Mobile Display; Data Display (representation) of Army data to Army Leaders to inform decisions; Ease of Use.

2.7 Basis of Selection for Upward Invitation – B (move from Step 2 to Step 3).

The Government perform an integrated evaluation based on the results from: Step 2.a.

written Prototype Proposals – Technical Approach and Step 2.b. the Software Demonstration (with provided Army Data). The Offerors that are determined to be most successful at addressing the elements required for 2.a and 2.b will receive an Upward Invitation – B, Step 3 to submit a Final Proposal and to conduct a Software Demonstration to Senior Army Leaders with Army Data.

2.7.1 Offerors not selected for Upward Invitation - B will be notified in writing.

2.7.2 Offerors that are selected for the Upward Invitation – B will be informed of the results of the evaluation of their Technical Approach and the software usability assessment of Demonstration #2.

SECTION 3 - STEP 3 – FINAL PROTOTYPE PROPOSAL, TO INCLUDE PRICE, AND

SOFTWARE DEMONSTRATION #3 TO ARMY SENIOR LEADERS (WITH PROVIDED

ARMY DATA) - Instructions, Evaluation Criteria and Basis of Selection

3 INSTRUCTIONS – Step 3

3.1 For Step 3 –Final Prototype Proposal, to include Price, and Software Demonstration #3 to Army Senior Leaders (with provided Army Data) (same data as provided in Step 2), Offerors shall submit the files and conduct Software Demonstration #3 as defined in Table 18:

Table 18 - Offeror Response Items for Step 3: Upward Invitation – B

Response Item Response File Name Page Limit

1. Offeror RSVP

Invitation B – Senior Leader Demo

ALD_VendorName_RSVP2_W15QKN-18-X-01K6.pdf (Offeror letterhead and format with Demonstration Names)

1 Page

2. Final Prototype Proposal - Technical Approach

ALD_VendorName_Final_Tech_Approach_W15QKN-18-X- 01K6.pdf

20 Pages

3. Prototype Proposal

– Price

ALD_VendorName_Price_W15QKN-18-X-01K6.xlsx

No Limit

4. Offeror’s Software Demonstration

No file submission, only a “Live” Software Demonstration #3 to Army Senior Leaders (with provided Army Data)

:30 Minutes

Submit the files for Items 1, 2 & 3 following the AMRDEC instructions at Section A.

3.1.1 Offeror RSVP Invitation B – Senior Leader Demo. 1 page limit, not evaluated. The content is at the discretion of the Offeror and shall include, formatted as depicted in Table 19 below, the names of the attendees at the Software Demonstration to Senior Leaders (with provided Army Data) (see paragraph 3.1.4.1 “Who”):

Table 19 - Software Demonstration to Senior Leaders (with provided Army Data) Personnel List

# NAME (Mr/Ms. First-Mi-Last) Company Affiliation ALD Support Role 0 EXAMPLE: Ms. Jane Q. Public DashboardSoft LLC Project Manager 1.

2.

3.1.2 Final Prototype Proposal – Technical Approach.

20 page limit, submitted in Adobe .pdf format. For the response for Step 3. - Final Prototype Proposal - Technical Approach: Follow the detailed Instructions for the written Prototype Proposal found above in paragraph 2.2 RESPONSE FOR STEP 2.a. – Detailed Instructions for the written Prototype Proposal. The format (see paragraph

2.2.2 for page size, font etc.) remains the same. The page count is adjusted from 15 to 20.

3.1.2.1 Highlight all new/revised text in Yellow. For changed or new figures charts or tables, only highlight titles in Yellow. Deleted text, figures, charts or tables shall not be shown. Other similar edit marking methods are acceptable as long as the edits are clearly marked.

3.1.2.2 This final submission permits the Offeror to clarify any details and to address the results of the Government evaluation of the written Prototype Proposal and Software Demonstration #2 provided in the Upward Invite – B.

3.1.3 Prototype Proposal Price.

No page limit, MS Excel .xlsx format (2013 or newer). The objective of the Price Proposal is to provide sufficient information to substantiate that the overall proposed price is realistic, reasonable and complete for the proposed work. The Price Proposal should provide enough information to ensure that a complete and fair evaluation of the reasonableness and realism of the price can be conducted and reflect the best price for the Project. Offeror shall perform a price analysis on all team members/subcontractors and confirm to the Government that their proposed costs found to be fair and reasonable. This analysis shall be provided as part of the submitted proposal.

Offerors shall propose Prices for Phase 1 and Phase 2, to include a narrative for each associated Cost Element. Include, at a minimum, the contents of Table 20 in TAB 1 of the Submission, further breakout of price is acceptable:

Table 20 - ALD Cost Elements Summary (Submit as TAB 1)

Cost Element

Phase 1 Price

Phase 2 Price

Short Description

Cost Short Description

Cost

Prime Contractor Labor $ $

Material/Equipment $ $

Software License (List by License)

Hosting and Managed Services

Other Direct Costs $ $

Subcontractor/Consultant Labor (List by Subcontractor company)

Travel $ $

Indirect Costs $ $

Profit/Fee $ $

Proposed Cost Share (if applicable)

Total Solution Price $ $

3.1.3.1 Offerors shall provide Price Narratives with a separate discussion for each Cost Element by Prototype Phase 1, Phase 2 and Production. Tabs behind TAB 1 shall include, at a minimum, a narrative with details on the following Cost Element categories:

a. Labor Rates (Separate for Prime / Subcontractor). Include the basis for which the estimated total labor hours were calculated. (i.e. Labor Category position titles and estimated rates and hours for those individuals)

b. Material/Equipment. Provide a list of the materials/equipment required to meet the Technical Approach as described in the written proposal and the estimated cost.

c. Software License Cost. Provide an itemized list of each license and the cost.

d. Hosting (including managed services). Provide a narrative of the services provided.

e. Other Direct Costs. Provide a narrative for Other Direct Costs and provide data as appropriate supporting how the estimate was calculated. This section should include a breakout of any estimated costs that do not fit into the cost categories above.

f. Travel. The Offeror must provide details for the travel required for the proposed effort broken out by participant (i.e. Offeror’s and any team member’s / consultant’s travel schedule). The Offeror shall provide the number of people, trips, per diem, airfare, rental car and any other incidental costs proposed as necessary in performance of this requirement. Travel costs shall be in accordance with Joint Travel Regulations (JTR).

g. Indirect Costs. Provide an estimate of the indirect costs and provide data to support your indirect cost rates by one of the following methods:

(1) Provide a copy of certification from a Federal agency indicating these indirect rates are approved by the Federal agency; or

(2) Provide a letter from your Administrative Contracting Officer, in lieu of a rate certificate, stating these indirect rates are approved by a Federal agency; or

(3) If you do not have approved rates, provide detailed supporting data to include pools of expenses and allocation bases for the base year and out years, if applicable for:

(a) indirect rates and all pricing factors that were used;

(b) methodology used for determining the rates (e.g., current experience in your organization or the history base used) and,

(c) all forecasted rates, by year, applied to derive the proposed rates should be based on assumptions and or facts. If computer usage is determined by a rate, identify the basis and rational used to derive the rate.

h. Profit/Fee. Fee/Profit is allowable for the effort being conducted when cost share is not being contributed by the contractor.

3.1.3.2 Production Rough Order of Magnitude

Offerors shall include a ROM for Production. For purposes of this ROM, production is considered a twelve (12) month period of performance, with the Offeror providing access (licenses) to the solution in a Offeror Hosted facility. Support shall include all support and maintenance, for 6,000 users, for all Phase 1 and Phase 2 Authoritative Data Sources.

3.1.4 Software Demonstration # 3 to Army Senior Leaders (with provided Army Data).

3.1.4.1 Who: Up to four (4) personnel, who may be different from those who participated in the earlier Software Demonstration # 1, (with corporate / public data) and/or the Software Demonstration # 2 (with provided Army Data). Offeror attendees / presenters shall not be temporary proposal consultants or business development team members and must be current employees for the Prime Offeror or designated Team Member. The presentation team shall be composed of the designated company personnel proposed as providing direct support to the ALD project effort.

3.1.4.2 Location: The Software Demonstration (with provided Army Data) will be held at a location to be announced in the Government Invitation letter. This is an in-person event and there will be no capability for Teleconference or Video Conference.

Additional details about the location will be included in the invitation. For planning purposes only, use these two Government office sites:

• Primary: Pentagon, Pershing (Army) Conference Room, Washington, DC

3.1.5 Date / Time: Offerors will be scheduled randomly and the Government will publish a date / time reservation to each Offeror approximately in accordance with the attached schedule. Presentation time slots will begin no earlier than 9:00 AM EDT on the date indicated in the attached schedule and will continue until all are complete.

3.1.5.1 How / Details: 30-Minute time limit for the Software Demonstration (with provided Army Data), with a 15-minute transition-in and setup before the start. See Table 21 for a tentative schedule. The Offeror’s Software Demonstration shall cover the topics in Table 22 below. The Offeror shall allocate time (amount at their discretion) and shall be prepared to respond to “Ad-Hoc” Army use cases and questions from the Senior Leaders during their demonstration that may expand upon the Army use case(s) or any other topic. Similar to Demonstration # 2, (no Oral Presentation, no Charts/Slides permitted).

3.1.5.2…