W56KGY-17-R-0026_(0004).pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting And Appropriation Data (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: The Changes Set Forth In Item 14 Are Made In

The Contract/Order No. In Item 10A.

B. The Above Numbered Contract/Order Is Modified To Reflect The Administrative Changes (such as changes in paying office, appropriation data, etc.) Set

Forth In Item 14, Pursuant To The Authority of FAR 43.103(b).

C. This Supplemental Agreement Is Entered Into Pursuant To Authority Of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name And Title Of Signer (Type or print)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

By (Signature of person authorized to sign) (Signature of Contracting Officer)

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

0004 2017OCT17

W56KGY

ACC-APG Division C (W56KGY)

6001 Combat Drive

APG, MD 21005-1846

PRETTINA BIEDENKAPP

EMAIL: PRETTINA.J.BIEDENKAPP.CIV@MAIL.MIL

W56KGY-17-R-0026

2017SEP28

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 13

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: PRETTINA BIEDENKAPP

Buyer Office Symbol/Telephone Number: CCAP CCC/(443)861-5392

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

1) The purpose of this Amendment (0004) to Solicitation W56KGY-17-R-0026 is to:

a) Incorporate revised language in Section L.

b) Incorporate revised attachments in Section J.

c) Correct Attachment name from Amendment (0003).

d) Incorporate additional instruction for contractors.

2) The following sub-sections in Section L are revised as follows:

a) L.2.3

b) L.2.2.3

3) Revised Attachment is incorporated in Section J:

a) Attachment 0001- Statement of Work CD-1 16 October 2017.

b) Attachment 0008- Product Demonstration Test Plan is For Official Use Only.

c) Attachment 0017- Product Demonstration Risk Reduction Information is For Official Use Only.

4) Please provide information/documents identified in DFARS 252.227-7028 - Technical Data or Computer Software Previously Delivered to the Government in Volume I - Executive Summary in Award Documents/Certifications/Representations.

5) The Government allows contractors to export PDF documents to Word format and vice versa.

6) Attachment 0017-Product Demonstration Risk Reduction Information is the correct attachment name that was incorrectly written out in

Section A of Amendment (0003).

*** END OF NARRATIVE A0005 ***

2 13

W56KGY-17-R-0026 0004

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION J - LIST OF ATTACHMENTS

List of Number List of Number

Addenda Title Date of Pages Transmitted By Addenda Title Date of Pages Transmitted By________________ ____________________________________________________________ _______________ ____________ _______________________________ ____________________________________________________________ _______________ ____________ _______________

Attachment 0001 STATEMENT OF WORK 16-OCT-2017 035 EMAIL

Attachment 0008 PRODUCT DEMONSTRATION PLAN 16-OCT-2017 019 EMAIL

Attachment 0017 PRODUCT DEMONSTRATION RISK REDUCTION INFORMATION 13-OCT-2017 015 EMAIL

3 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

Introduction

Offerors shall submit digital copies of proposals through the Federal Business Opportunities (hereby known as FedBizOpps) web portal.

Once proposals are submitted, the Government requests that Offerrors submit a confirmation email to the Contracting Officer at

James.E.Farnsworth8.civ@mail.mil and Contract Specialist at Prettina.J.Biedenkapp.civ@mail.mil. Offerors proposal shall consist of four

(4) volumes.

The Volumes are as follows:

I Executive Summary

II Technical

III Price

IV Past Performance

Offerors are cautioned that parroting of the Technical requirements or the SOW with a statement of intent to perform does not reflect an understanding of the requirement or capability to perform. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal. Proprietary information shall be clearly marked.

Offer and Award Documents and Certifications/Representations. Each proposal volume shall include the prescribed files identified in

Section L.2. Electronic submission of proposal is mandatory, in accordance with the Request for Proposals (RFP) due date listed in the solicitation, with the time of receipt of the required electronic proposal volumes to FBO serving as the compliance time for proposal.

The electronic proposal file submission to FBO will be the official submission used for evaluation purposes.

Files to be posted on FBO shall NOT contain CLASSIFIED data. The use of external hyperlinks in proposals is prohibited. The use of hyperlinks that link within a document, such as table of contents links, are allowed.

FBO Resources:

- The Uniform Resource Locator (URL) for FBO is:

- Directions for navigating this Internet site are contained in FBO User Guide found at:

- For Technical assistance, The FedBizOpps help desk can be reached at , or 1-866-606-8220 (national), 1-334-206-7828 (international).

FedBizOpps registration and (active) System for Award Management (SAM ) account is required to submit proposals.

WARNING: Do not wait until the last minute to submit proposals. To avoid late proposal submissions, Offerors are encouraged to submit proposals 24 hours prior to the required due date and time.

Note: Offerors are offered the opportunity to participate in an open integration session at the MITRE building at APG in advance of the________________________________________________________________________________________________________________________________________ proposal submission date. Offerors are not required to participate, and the integration session will not be evaluated. For additional______________________________________________________________________________________________________________________________________ information, please refer to the PRODUCT DEMONSTRATION PLAN, Attachment 0008 of the Solicitation.__________________________________________________________________________________________________

L.2- Proposal Submission Requirements_____________________________________

The submission shall be clearly indexed and logically assembled. Each volume should be clearly identified and begin at the top of a page. All pages of each volume should be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer.

As indicated in Table A below (Filenames and Page Limits) all files shall be submitted as Microsoft Office Word (MS) no earlier than

2007 version, (.docx), Excel (.xlsx), and/or Acrobat (.pdf).

A table of contents should be created using the table of content feature in MS Word. MS Word (doc) files should use the following page setup parameters:

Font Size 12 Point Arial or Times New Roman (Tables and illustrations may be font size 8 or larger)

Margins Top, Bottom, Left, Right 1

Gutter 0

From Edge Header, Footer 0.5

Page Size, Width 8.5

4 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Page Size, Height 11

Any pages that are changed (as a result of negotiations or proposal revisions) shall have the changed information clearly marked by a vertical line in the right margin of the page, and underlining and/or strike-through of text shall be used to distinguish the changed information. The revised pages shall be dated to distinguish them from the original proposal and any other previous revised pages if multiple proposal revisions have been requested by the Government.

File Packaging. Offeror shall submit proposal files under the associated filenames and file format stated in Table A. If proposal files are compressed (zipped), using WinZip version 6.2 or later, into multiple zip files, each zip file must be clearly identified by

Volume, as per Table A instructions. Please note, Offerors are cautioned that large file sizes of proposals significantly delay submissions, or may not be permitted due to file size restrictions on FBO. High resolution graphics may greatly increase file sizes. Up to five (5) files can be uploaded at one time. The combined size of the five (5) files cannot exceed 100MB. Also note, self-extracting

.exe files will not be accepted. Additionally, the Government does not accept responsibility for the organization of electronic proposal submissions. If proposal files are missing or not identified per the instructions provided by this solicitation, the proposal may be eliminated from the competition. The Offeror is responsible for ensuring all appropriate files are included in the proposal submission. Proposal files may be submitted individually without compression at Offerors discretion.

Break attachments into smaller files or use the upload utility multiple times if files exceed the 100MB size limit. Filenames MUST be labeled as indicated in Table A.

Updated computer software virus protection is required, Offerors should not submit proposals absent updated computer virus protection software. Uploading files with viruses may jeopardize bid submission.

The Government will not accept any other submission methods in lieu of those permitted by the submission instructions provided by this

RFP.

The Offeror shall confine submissions to essential matters, sufficient to define the proposal and provide an adequate basis for evaluation. Offerors are responsible for including sufficient details, in a concise manner, to permit a complete and accurate evaluation of each proposal. Volumes I and II of the proposal shall consist of a Table of Contents, Glossary of Abbreviations and

Acronyms, Summary Section, and the narrative discussion. The Summary Section shall contain a brief abstract of the volume. Any proprietary information shall be clearly marked. No price information shall be presented in any part of the proposal except as provided in Volume I, Executive Summary and Volume III, Price Factor. Each volume shall be prepared on a standalone basis, so that its contents may be evaluated with minimum cross-referencing to another volume of the proposal. Each Table of Contents shall delineate the subparagraphs with that volume to the proposal content when applicable. The submission of alternate proposals shall not be allowed.

The titles and page limits requirements for each file are shown below:

TABLE A- FILENAMES and PAGE LIMITS__________________________________

VOLUME I - EXECUTIVE SUMMARY____________________________

Title: Proposal Synopsis

Filename: PROPSYN.docx or PROPSYN.pdf

Page Limit: 10 pages

Title: Commercial Item Assertions

Filename: COMMITEMASSERT.docx or COMMITEMASSERT.pdf

Page Limit: No Page Limit

Title: Glossary of Abbreviations and Acronyms

Filename: GLOSSARY.docx or GLOSSARY.pdf

Page Limit: No Page Limit

Title: Award Documents/Certifications/Representations

Filename: AWARDDOCS_FILENAME.docx or AWARDDOCS_FILENAME.pdf or AWARDDOCS_FILENAME.xlsx

Page Limit: No Page Limit

Title: Commercial Plan or Subcontracting Plan (For Large Business Primes only)

Filename: SBP.docx, SBP.pdf, CSP.docx, or CSP.pdf

Page Limit: No Page Limit

VOLUME II - TECHNICAL FACTOR____________________________

5 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Title: Technical Solution Narrative

Filename: TECHNARRATIVE.docx or TECHNARRATIVE.pdf

Page Limit: No Page Limit

Title: Requirement Cross Reference Matrix

Filename: CRM.xlsx

Page Limit: No Page Limit

Title: Data Assertions

Filename: DATAASSERT.xlsx

Page Limit: No Page Limit

Title: Usability Maturity

Filename: USABILITYMATURITY.docx or USABILITYMATURITY.pdf

Page Limit: No Page Limit

VOLUME III - PRICE FACTOR_________________________

Title: Total Evaluated Price (TEP) Worksheet

Filename: Total_Evaluated_Price.xlsx

Page Limit: No Page Limit

Title: Price/Cost Supporting Documentation

Filename: PCSUPP_FILENAME.docx or PCSUPP_FILENAME.pdf or PCSUPP_FILENAME.xlsx

Page Limit: No Page Limit

VOLUME IV - PAST PERFORMANCE FACTOR___________________________________

Title: Past Performance Factor

Filename: PASTPERF.docx or PASTPERF.pdf

Page Limit: No Page Limit

Offerors are advised that employees of the firms identified below may serve as non-government advisors in the proposal evaluation process. These individuals will be authorized access only to those portions of the proposal data and discussions that are necessary to enable them to perform their respective duties. These individuals are non-voting members of the evaluation team. The points of contact listed below are individuals responsible for executing the agreement, and not evaluators themselves.

MITRE Corp

Mr. Robert A. Orlosky

The MITRE Corporation CAGE: 7L030

21 W. Lee Street

Baltimore, MD 21201-2455

703-983-7622 rorlosky@mitre.org

Booz Allen Hamilton Inc.

Mr. Ryan Ludwig

Booz Allen Hamilton, Inc. CAGE: 17038

8283 Greensboro Drive

McLean, VA 22102-3830

732-936-3539

Ludwig_ryan@bah.com

Millennium

Ms. Susan Han

Millennium Corporation CAGE: 3VQP8

1400 Crystal Drive Suite #400

Arlington, VA 22202-3289

571-527-2233

Susan.Han@millgroupinc.com

6 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Alliance

Ms. Jennifer Stroh

Alliance Consulting Services, LLC. CAGE: 60J54

21 W. Lee Street

Baltimore, MD 21201-2455 jen@consultalliance.net

In accomplishing their duties related to the Technical Factor evaluation and negotiation process, the aforementioned firms may require access to proprietary information contained in the Offerors proposals. Therefore, pursuant to FAR 9.505-4(b), these firms must execute an agreement with each Offeror that states that they will (1) protect the Offerors information from unauthorized use or disclosure for as long as it remains proprietary, and (2) refrain from using the information for any purpose other than that for which it was furnished. To expedite the evaluation process, each offeror must contact the above companies to effect execution of such an agreement prior to the submission of proposals. Each offeror shall submit copies of the agreement with their proposal. Please provide this document in Volume I-Executive Summary (4)-Award Documents/Certifications/Representations.

Note- In order to participate in the Phase 0 integration session opportunity, offerors must have their completed agreements submitted to the contracting officer prior to the date their session is set to begin. See L.2.2.1.3 and Attachment 0008 for additional detail regarding the Phase 0 integration session.

L.2.1- Volume I Executive Summary _________________________________

The Offeror shall utilize this volume to provide an overview of the proposal and summarize pertinent information contained in all volumes of the proposal. The information contained in this volume must be consistent with data in the other volumes. References to the proposal locations providing substantiating data shall be given as appropriate. The information contained in this volume is not an evaluation factor, but is required for award.

This volume shall be organized into the following sections:

(1) Proposal Synopsis: _________________

The Offeror shall utilize this section of the Executive Summary to summarize pertinent information contained in all volumes of the proposal. The Offeror is free to submit this section of the Executive Summary in any format desired, subject to the limitations previously set forth above, and to include any and all information it believes will support its proposal. Offerors are reminded that the Executive Summary is an introductory summation of the proposal. Therefore, no information shall be in the Executive Summary that does not appear elsewhere in the proposal.

(2) Commercial Item Assertions: ___________________________

The Offeror shall provide documentation to support that its solution is a commercial item. The commercial item assertions should explicitly detail how the proposed solution fits the definition of a commercial item as stated in FAR 2.101.

If the offeror does not provide sufficient evidence that its solution is a commercial item, then the Government may determine that the offeror is not eligible for award.

(3) Glossary of Abbreviations and Acronyms: ________________________________________

The Executive Summary shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. The glossary of abbreviations and acronyms does not count towards the page limits contained in Table A.

(4) Award Documents/Certifications/Representations: _______________________________________________

The Offeror shall provide any Award Documents, Certifications, and/or Representations to accompany the proposal submission as required by the solicitation under representations, certifications, and other statements of offerors.

The prime Offeror shall have an approved Secret facility clearance and Secret safeguarding for classified material and property in effect at time of award, based on the DCGS-A DoD Security Classification Specification, DD Form 254, PM DCGS-A requirements.

The following information must be provided to verify the secure facility clearance:

- Contractor Name

- Commercial and Government Entity (CAGE) Code

7 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

- Corporate Mailing Address

- Classified Mailing Address

- Security Office Information including:

i. Name

ii. Title

iii. E-mail address

iv. Telephone Number

If prime Offeror does not have an approved Secret facility clearance at time of proposal, Offerors shall submit a plan with timeline to achieve those requirements within 180 days from time of initial award.

(5) Small Business Subcontracting Plan: ___________________________________

Other than U.S. Small Business Offerors shall submit either a commercial plan as defined at FAR 19.701, or a Small Business

Subcontracting Plan meeting the requirements of FAR 52.219-9 and DFARS 252.219-7003, or DFARS 252.219-7004, if the Offeror has ____________ _ _ a comprehensive subcontracting plan. Other than U.S. Small Businesses must submit acceptable subcontracting plans to be eligible for award. The Subcontracting Plan or Commercial Plan will be IDIQ level attachments, applicable to all Delivery

Orders. The requirements in this paragraph are for compliance purposes and shall not be considered as an evaluation factor during the Governments award selection trade-off analysis.

(6) Data and Software Rights Assertions ____________________________________

In accordance with the content and formatting requirements for Data and Software Rights Assertions (set forth in DFARS 252.227-

7017), the Contractors Data and Software Rights Assertions shall comply with the following requirements:

- The Contractor shall not assert license restrictions on items, component, or processes themselves. The asserted license restrictions shall pertain to software or technical data that relates to items, components, or processes.

- The Contractors Assertions shall not include technical data or software that will not be furnished to the Government under this Contract.

- The Contractor shall provide a concise (but specific) description of the technical data and software deliverables that will be furnished to the Government with restrictions, rather than generically asserting license restrictions in technical data or technology.

- The Contractor is responsible for ensuring that Data and Software Rights Assertions from its subcontractors comply with the aforementioned content and formatting requirements (in accordance with DFARS 252.227-7017).

- Contractors shall provide Data/Software Rights Assertions in a tabular format prescribed in DFARS 252.227-7017. However, in addition to the content and formatting requirements set forth in DFARS 252.227-7017, the Contractors Data/Software Rights

Assertions table shall list technical data and software items that the Contractor intends to furnish to the Government with and without license restrictions. Thus, the Data/Software Rights Assertions table may include technical data and software items that are provided to the Government with an unlimited rights license. In the Contractors identification of technical data and software license rights, the Contractor shall reference any applicable commercial software license agreement related to proposed commercial software deliverables.

L.2.2- Volume II Technical Factor__________________________________

The volume shall be organized into the following sections:

L.2.2.1- Subfactor 1: Technical Product Demonstration_____________________________________________________

L.2.2.1.1 Demonstration_______________________

Offerors shall participate in a technical product demonstration as part of the proposal response, whereby the offeror demonstrates its product solution. The technical product demonstration is where the Offeror will demonstrate whether its solution can accomplish the tasks defined in the Product Demonstration Plan (PDP). (Attachment 0008). The product demonstration will be conducted at Aberdeen

Proving Ground (APG), MD and will not exceed two (2) business days consisting of one day of System Set-up and Configuration and one day

(Day 2) for the Product Demonstration. This period includes time for configuration/set-up, system overview, requirement demonstration, and teardown. The Offeror will be required on site at the Government designated facility (Aberdeen, MD) for this demonstration and is allotted three (3) Offeror personnel, to include a system operator. The Contractor shall bring up to two (2) workstations. The Offerors system operator will perform all tasks on the system in accordance with the PDP (Attachment 0008).

8 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.2.2.1.2 Sample Data Available Upon Request____________________________________________

Product Demonstration Sample Data is available upon request. Please see attachment 0009- BN GFI list for a summary of the information that will be provided. In order to receive a copy of the GFI, the offeror shall send an email with a completed PM DCGS-A and PM Mission

Command (MC) Software Product_(SWP) Request_Form (Attachment 0010) to the contracting officer. Once the Government is in receipt of this

DCGS-A SWP_Request_Form, the offeror shall then send a vendor provided 1 Terabyte (TB) hard drive. A return shipping label, as well as the delivery notification document, shall be included in the package with the hard drive in order to track the delivery. Once shipped, please send us, via email, the Serial Number and tracking number info for the package.

Delivery Address below:

UNCLASS

PM DCGS-A CM

Bldg 6006 Combat Drive

Floor B5-101

Aberdeen Proving Ground, MD 21005

Attn: Stephanie Comer (443) 861-4146// Daniela Caraway (443) 861 3738//Joe Duarte (443) 861-3739 //

L.2.2.1.3_________

As stated in the Product Demo Plan, Attachment 0008, all offerors are offered the opportunity (but not requirement) to participate in an open Phase 0 integration session at the MITRE building at APG prior to the proposal submission date. Offerors are not required to participate, and the integration session will not be evaluated by the Government. The purpose of the Risk Reduction Integration is to reduce risk to the Government by allowing offerors the opportunity to integrate with the Government configuration in advance of the product demonstration. For full details of the Phase 0 Risk Reduction Session, see Attachment 0008.

In accordance with par. L.2, offerors must submit their non-disclosure agreements with the non-government advisors to the contracting officer James.E.Farnsworth8.civ@mail.mil prior participating in the Phase 0 integration session. If an offeror chooses to participate in the Phase 0 Integration Risk Reduction Event, it must complete it's agreement with MITRE beforehand. Phase 0 is scheduled from 16-20

October.

L.2.2.2- Subfactor 2: Usability Maturity________________________________________

The Offeror shall include a written narrative that demonstrates that the Offerors solution meets the following requirements:

CATEGORIES__________

PROGRAM USABILITY MATURITY___________________________

Requisite Skillsets Offeror shall provide evidence of a minimum of 1 Usability professional having a minimum of 2 years practical experience with all stages of a user-centric-design (UCD) or alternative process. In lieu of the foregoing, the Government will also consider a minimum of 1 non-usability professionals with usability related background that have a minimum of 4 years of experience with all stages of the UCD or alternative process.

USER RESEARCH METHODS AND MATURITY___________________________________

Understanding the User population - Offeror shall produce at a minimum one artifact/practical example of any of the following: context of use, task analysis, operational environment descriptions, or alternative completed for the Offerors proposed solution that validates user research was conducted by the Offeror to understand the user population.

Enculturation of User Involvement - Offeror shall produce artifacts/practical examples of user involvement in the design and development of the proposed solution. At a minimum, the Offeror shall provide one of the following artifacts/practical examples: surveys, focus group transcripts, interview transcripts, usability test results or alternative artifacts that validates user involvement. A description shall accompany the artifact, describing how the user involvement results/data impacted design decisions for the Offerors proposed solution.

DESIGN OF THE USER INTERFACE____________________________

9 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

User Analysis - Offeror shall produce, at a minimum, one artifact/practical example of any of the following: use cases, task analysis, storyboards, personas, or alternatives that were used during the design of the Offerors proposed solution.

Conceptualization of Initial UI Design - Offeror shall produce, at a minimum, one artifact/practical example of any of the following:

wireframes, sketches, prototypes, or alternative used in the design of the Offerors proposed solution.

UI Design Standards Compliance Offeror shall describe how the Offerors proposed solution adhered to User Interface design standards/best practices and provide, at a minimum, one product artifact/practical example of any one of the following: heuristic evaluations, checklists, design guideline.

Collaboration, Transformation, and Construction - Offeror shall describe/explain how software developers were involved in the generation of prototypes, wireframes, etc. Offeror shall produce, at a minimum, one artifact/practical example of any one of the following: Meeting transcripts, design documentation, or alternative.

Usability Testing - Offeror shall produce evidence of usability testing on the Offerors proposed solution. At a minimum, the Offeror may provide any one of the following artifacts/practical examples that illustrates usability testing: usability plans, test data, etc.

Final UI Design - Offeror shall produce a final design from Offerors proposed solution and describe how it met its intended use. At a minimum, the Offeror may provide any one of the following artifacts/practical examples: requirements checklist, spec sheets, final testing data, etc. can serve as evidence.

SUSTAIN AND USER ACCEPTANCE___________________________

Feedback loops Offeror shall describe customer feedback mechanisms and how customer feedback impacted the Offerors proposed solution.

At a minimum, the Offeror shall provide any of the following artifacts/practical examples: feedback databases, bug reports, telemetry, utility metrics, etc. can serve as evidence.

L.2.2.3- Subfactor 3: Technical Solution Narrative__________________________________________________

The Offeror shall provide a completed Cross Reference Matrix (CRM) (Attachment 0005) that maps the proposed BN solution capabilities to the requirements outlined in the Performance Requirements Document (PRD) (Attachment 0003). The matrix shall clearly indicate whether the proposed solution meets or does not meet each requirement defined in the PRD, along with a brief description detailing how (with reference to existing documentation such as slick sheets, user guides, product specifications, etc.). The Offeror shall provide the referenced documentation as an appendix (ces) and provide a hyperlink in the CRM to the referenced documentation.

Additionally, the Offeror shall provide a proposed implementation plan. At a minimum the plan shall address the following minimum requirements of the SOW:

- Detailed description of how the Offeror will execute the recurring requirements in SOW paragraphs 3.4, 3.5, 3.6, and 3.7 and their sub-paragraphs.

- Detailed description on how the Offerors proposed solution will comply with SOW paragraph, 3.1.5, Army Interoperability Certification

(AIC).

- Detailed description of hardware requirements and specification, to include purchase approach, plan to rapidly acquire and field during initial fielding phase, and warranty plan, per the SOW, paragraph 3.8. Inclusion of the MIL STD-810G profiles detailing what the proposed hardware solution has been tested against.

L.2.3- Volume III Price Factor_______________________________

The Offeror shall submit pricing for all CLINs identified in the Total Evaluated Price (TEP) Worksheet. Offerors shall not re-format or remove cells from the spreadsheet. Submission of the pricing data shall be complete and accurate. All prices will be provided as a

Firm-Fixed Price, therefore all proposed prices shall be inclusive of all direct (i.e., direct labor, material, travel, and other direct costs) and associated indirect costs plus profit related to each CLIN.

The proposed unit prices in the TEP Worksheet shall be the Offerors intended Firm-Fixed-Price contract ceiling unit prices for each base and option year CLIN and specified range quantity. Upon award, the TEP Worksheet will become a firm contract requirement, attached in

Section J.

Please Note: Contractors shall not propose unit prices in response to any order RFP that exceeds the ceiling prices established in the

TEP Worksheet. In response to any order RFP, the contractors may propose a discounted unit price which is lower than the ceiling prices established in TEP Worksheet (Attachment 0012).

The Contracting Officer has determined there is a high probability of adequate price competition on this acquisition. However, if at any

10 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

time during this acquisition the Contracting Officer determines that adequate price competition no longer exists; Offerors may be required to submit information to the extent necessary for the contracting officer to determine the reasonableness of price.

Additionally, all information related to pricing shall be included in the section of the proposal defined as Volume III Price Factor.

In the event the Contracting Officer determines additional information is necessary in order to determine the reasonableness of price, information such as the below may be requested:

- Catalog Pricing- Relevant Offeror commercial catalog, its date, catalog prices, and related discounts. Include an explanation of any differences between the offered price, the established catalog price, and price of recent sales in quantities similar to the proposed quantities.

- Market Pricing- Description of the nature of the relevant market and how that market affects the offered price including the source and date or period of any relevant market quotation or other basis for market price, the base market price, and applicable discounts or other price adjustments.

- Other evidence of prices charged- Evidence of prices charged other customers under similar circumstances. For example, the firm could provide copies of contracts with other customers to document the prices charged.

Unbalanced Pricing - If the Offerors unit prices appear unbalanced when comparing them from quantity range to quantity range or ordering period to ordering period, the Offeror shall provide documentation, including calculations and supporting rationale, explaining the apparent unbalanced pricing.

For proposal preparation purposes only, the expected or approximate date for initiation of contract performance is 31 March 2018. The actual performance dates may vary.

L.2.4- Volume IV Past Performance Factor

a) Offerors shall provide information on recent and relevant contracts for the Offeror, and the Offerors proposed major subcontractor(s). Major subcontractors are defined as members of an Offerors overall team who are anticipated to perform more than twenty (20) percent of the proposed Total Evaluated Price. The Offeror shall submit only those recent and relevant contracts for itself and its major subcontractor(s) for identical or similar efforts to the requirements of this RFP. These may include Federal, state, and local Government efforts. Recent includes performance of contracts occurring within thirty-six (36) months of the date of issuance of this solicitation. Relevant past performance is defined as past performance that demonstrates knowledge or experience with information systems deployed in tactical environments.

b) Contract Information: The Offeror shall complete a Relevant Past Performance Information form, solicitation attachment 0006, for a minimum of two (2) and no more than five (5) contracts for the Prime Offeror, and no more than five (5) contracts with a minimum of one

(1) for each of the Offerors proposed major subcontractor(s), that demonstrates knowledge or experience with similar information systems deployed in tactical environments. In order to be considered relevant, the offeror must demonstrate for each proposed contract that it, or its major subcontractor, performed a minimum of 33% of the dollar value of the contract.

a. Offerors shall also provide a copy of any Cure Notices or Show Cause Letters recieved on each contract listed in addition to the information inserted in Item 31 of the Relevant Past Performance Information form. If available, the offeror shall attach the most recent Contractor Performance Assessment Reporting System (CPARS) evaluation (Block 15) for relevant past performance.

b. Offeror shall ensure that the references cited in Blocks 24 through 7 of the Relevant Past Performance Information Form are current and accurate.

c. The Offeror shall forward the Past Performance Quuestionnaire forms, solicitation Attachment 00007, directly to the

Technical Point of Contact (TPOC) identified in the Relevant Experience Form. The Government requests TPOCs return the Past Performance

Questionnaire forms prior to close of the solicitation date directly to Army Contracting Command - Aberdeen Proving Ground (ACC-APG)

Contracts via e-mailing the Procurring Contracting Specialist at prettina.j.biedenkapp.civ@mail.mil. The Government reserves the right to contact references for verification or to obtain additional information.

d. The Offeror is not allowed to evaluate itself, it's teaming partners, major subcontractors or predecessor organizations or corporations. The offeror shall not request that any such entity submit a response to a Past Performance Questionnair for the purpose of responding to this RFP.

e. If the Offeror or it's major subcontractor(s) submit a contract from a related entity (for example, under a different CAGE code), to include a predecessor company, then the Offeror shall clearly explain in it's proposal why the past performance should be attributed to the Offeror or it's major subcontractor(s).

11 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

c) The Offeror shall briefly describe the specific work activity to be performed by itself, as the prime Offeror, and by each of its major partners/subcontractors/ teammates in addition to providing the Commercial and Government Entity (CAGE) code and DUNS number for itself and its Major Subcontractors.

d) The Offeror shall sanitize the information relative to classified contracts.

e)The Offeror shall indicate if it has no past performance, and, if applicable, shall clearly state this on the page immediately following the cover page of its submitted Past Performance Volume submission.

f) In no event shall the Offeror request or require the TPOC or any other representative of the TPOCs organization, entity or company to provide it with a copy of the completed questionnaire, nor shall the Offeror accept or receive any information concerning the content of the completed questionnaire from the TPOC or any other representative of the TPOCs organization, entity or company.

g) The Government reserves the right, but is not obligated, to contact references provided by the offeror. The Government may also decide to contact references other than those provided by the Offeror including sources outside the Government.

h) Corporate Entities: If any contract, listed as part of the Relevant Past Performance Information Factor submission was performed by a corporate entity or division other than the corporate entity or division that would perform work under this solicitation, the Offeror shall identify them and indicate which entity will perform this effort. The Offeror shall also clearly explain in its proposal why the past performance should be attributed to the Offeror or its major subcontractor(s). If applicable, this information shall be included in Block 4 of the applicable Relevant Past Performance Information Continuation Sheet.

i) Predecessor Companies: If the Offeror, or its subcontractor(s), only have relevant and recent performance history as a part of a predecessor company, the Government may consider that past performance in its evaluation of past performance. If applicable, the

Offeror shall provide the information for those recent, relevant contracts of that predecessor company. Offerors shall also provide sufficient information to show the corporate history from the predecessor company and why the past performance information of the predecessor is applicable to the new entity. This information shall be included in Block 4 of the applicable Relevant Past Performance

Information Continuation Sheet.

j) Contacting References: Offerors are advised that the Government may contact any of the references that the Offeror provides or any third parties of the Governments choosing. The Government reserves the right to use any past performance information so gathered as part of its evaluation.

k) Major Subcontractors Written Consent for Disclosure to Offeror: The Offeror shall include in its proposal the written signed and authorized consent of its proposed major subcontractors to allow the Government to discuss the major subcontractor's past performance with the Offeror.

l) Major Subcontractors Letters of Commitment: The Offeror shall include written Letters of Commitment of each major subcontractor(s) in order for the subcontractors past performance to be considered.

m) Complete Information. The Government is not required to search for data to cure problems it finds in proposals. While the Government may elect to consider data obtained from external sources other than the proposal, such as from the Past Performance Information

Retrieval System (PPIRS) or CPARS, the burden on providing thorough and complete past performance information rests with the Offeror.

n) Small Business Participation Past Performance: All Offerors shall submit information substantiating the Offerors past performance in complying with FAR 52.219-8, Utilization of Small Business, maximizing opportunities for U.S. small business subcontractors. Offerors shall also provide a statement indicating whether any negative information has been reported in the past six years concerning the

Offerors past compliance with FAR 52.219-8. If any such negative information has been reported, the Offeror may submit explanations or comments responding to such negative information. Offerors with no prior contracts containing FAR 52.219-8 shall certify the same.

L.3- Discussions________________

1. The Government intends to award without discussions in accordance with FAR 52.215-1. Offeror proposals, therefore, should be in final form when submitted to the Government. Offerors are notified that the Government may not conduct clarifications or discussions to resolve issues with offeror proposals, in which case offeror proposals that require clarifications or discussions may not be considered for award.

Notwithstanding the foregoing, the Government reserves the right to enter into discussions if the Government deems them to be necessary or beneficial to the Government. If the Government enters into discussions with offerors then the Government may decide to conduct written discussions with respect to all factors and subfactors, including the Technical Product Demonstration subfactor. In which case, the Offerors may provide written responses. The Government is not required to repeat the Product Demonstration Plan in the

Technical Product Demonstration subfactor, but reserves the right to do so if deemed necessary or beneficial to the Government. If the

Government determines to repeat the Technical Product Demonstration, then all Offerors shall be given the opportunity to re-submit their solution for demonstration testing. Any offerors that elect not re-submit their solution for demonstration testing shall be evaluated

12 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

based on the results of the prior demonstration test.

*** END OF NARRATIVE L0001 ***

13 13