B08_W15P7T-21-R-0001_ Amendment 0002_Signed_06 Jan 2021.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

0002 2021JAN06

W15P7T

ARMY CONTRACTING CMD-APG

6565 SURVEILLANCE LOOP

APG, MD 21005-1846

DIONNA P. BRITTEN

EMAIL: DIONNA.P.BRITTEN.CIV@MAIL.MIL

W15P7T-21-R-0001

2020NOV16

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 28

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: DIONNA P. BRITTEN

Buyer Office Symbol/Telephone Number: CCAP-CCB/(443)861-4942

Type of Contract 1: Firm Fixed Price

Type of Contract 2: Cost Plus Fixed Fee

Kind of Contract: Other

*** End of Narrative A0000 ***

Amendment 0002 to Solicitation number W15P7T-21-R-00012, is hereby issued to:

a. remove the usage of the Acquistition Source Selection Interactive Support Tool (ASSIST) for this acquisition as previously outlined in section L21;

b. add language regarding Government Furnished Property. Refer to Section L24.5.3, L25.2, and M2.1 for details;

c. update the solicitation DD254 found in Section J, attachment 0011; and

d. update Section L24.1.1, Demonstrations, to remove the hosting of in person demonstrations.

All other terms and conditions contained in the original solicitation, shall remain unchanged and in full force and effect.

*** END OF NARRATIVE A0002 ***

2 28

W15P7T-21-R-0001

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 0011 DD FORM 254 16-DEC-2020 016 EMAIL

3 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

SECTION L- INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS OR RESPONDENTS

General Instructions

L1.This section of the Instructions to Offerors provides general guidance for preparing proposals, as well as, specific instructions on the format and content of the proposal. The Offerors proposal shall include all data and information requested by the Request for

Proposal (RFP) and shall be submitted in accordance with (IAW) these instructions. The Offeror shall address the requirements outlined in the Engineering Development Performance Work Statement (PWS), Program Management Statement of Work (SOW), Contract Data Requirements

Lists (CDRLs), NGLD-M System Requirements Document (SRD), Technical Security Requirements Document (TSRD), and the Information Assurance

Security Requirements Directive (IASRD). Non-conformance with the instructions provided in this Instructions to Offerors may result in removal of the Offerors proposal from further evaluation.

L2. The proposal shall be clear, concise, and shall include sufficient detail for Government evaluation and for substantiating the validity of stated claims addressing how the Offeror intends to meet the Governments requirements. Offerors shall assume that the

Government has no prior knowledge of their capabilities and experience and will base its evaluation on the information presented in the

Offeror's proposal.

a. Elaborate brochures or documentation, binding, detailed artwork, internet hyperlinks, or other embellishments are unnecessary and will not be considered during evaluations.

b. The Offeror shall make a clear statement in Volume I cover page that the proposal is valid for a minimum of 180 days from the proposal due date.

c. IAW Federal Acquisition Regulation (FAR) Subpart 4.8 (Government

Contract Files), the Government will retain one digital copy of all unsuccessful proposals.

d. Portions of the successful Offerors proposal may be incorporated into the contract as an attachment in Section J.

L3. Non-Government advisors will be used on the source selection evaluation team. The non-Government advisors will NOT sit on the

Source Selection Evaluation Board (SSEB). The non-Government advisors will be available to the SSEB offering answers or clarifications regarding any topics within their expertise. These advisors shall be utilized only for clarity of information or requirements. Non-

Government advisors will either respond telephonically or via in person meeting to answer or clarify information or requirements. These non-Government advisors will only speak with the SSEB for the amount of time required to relay their answers or clarification and nothing more. The non-Government personnel will not have access to entirety of the offerors proposal but may review excerpts or limited content of the technical proposal. Additionally, the non-Government personnel will not know the identity of the offeror. The non-government advisors are from the following companies:

1. Sev1Tech, 12700 Black Forest Lane, Suite 306, Woodbridge, VA 22192

Peter J. Eck, PMP, peter.eck@sev1tech.com

2. Booz Allen Hamilton (BAH), 4694 Millennium Drive #200, Belcamp, MD 21017

POC: David McManus, McManus_David@bah.com

Offerors are advised that employees of the companies identified above may serve as non-Government advisors in the source selection process as outlined in the aforementioned paragraph. If the offeror requires a non-disclosure agreement (NDA) from the non-government advisor then the offeror shall include the signed NDA in the proposal. If Offeror objects to the companies listed as advisors to the

SSEB, the Offeror must submit their objection to the contracting office point of contact immediately. If the offeror believes that any type of conflict of interest exists the offeror will submit an Organization Conflict of Interest (OCI) letter to the contracting officer. The Government will not consider submission of OCI letters concerning the non-Government advisors after close of the solicitation period.

L4. Points of Contract

The Procuring Contracting Officer (PCO) and the Contract Specialist (CS) are the sole points of contact for this procurement. Address any questions or concerns to the PCO and CS. Written requests for clarification must be sent to the PCO and CS at the email address located below:

PCO: Shannon.M.McBride6.civ@mail.mil

4 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

CS: Dionna.P.Britten.civ@mail.mil

L5. Debriefings

The PCO will notify Offerors of any decision to exclude them from the competitive range, if established; whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing, or they may choose to wait until after the source selection decision to request a post-award debriefing. However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The PCO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR

15.505 or 15.506, as applicable.

L6. Discrepancies

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing.

L7. Electronic Reference Documents

All non-classified referenced documents for this solicitation are available on the BetaSAM.gov web site at https://beta.sam.gov/

. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation. The NGLD-M classified documents are available upon request and delivered by overnight mail via electronic media.

L8. Communications and Proposal Submission

The PCO or CS will control exchanges of source selection information between Government and Offerors. No information concerning this solicitation or requests for clarification will be provided in response to Offeror initiated telephone calls. All such requests must be made in writing and submitted as directed above. All questions/comments provided in a timely manner will be answered in writing and provided to all Offerors. Questions/comments are due no later than 5:00 pm(ET) on 27 November 2020. Questions submitted after the deadline may not be answered. The timeframe for submitting inquiries will not be extended as a result of an extension to the due date for the receipt of offers unless authorized by the PCO.

L9. Award without Discussions

The Government reserves the right to evaluate proposals and award a contract without discussions with offerors. Therefore, the offerors initial proposal should contain the offerors best approach/terms for 1) Technical, 2) Cost, 3) Past Performance, and 4) Small Business

Participation; however, despite this intent, the Government reserves the right to conduct discussions if the PCO determines they are necessary. If the PCO determines that discussions are necessary, a competitive range may be established. In the event issues pertaining to a proposed contract cannot be resolved to the SSA's satisfaction, the Government reserves the right to withdraw and cancel the solicitation without incurring any cost for proposal fees. In such event, offerors will be notified in writing.

L10. Organizational and Consultant Conflict of Interest (OCCI)

Each Offeror shall specifically identify in its proposal whether or not any potential or actual OCCI, as described in FAR Part 9, Subpart 9.5, exists for this procurement. If the Offeror believes that no OCCI exists, the OCCI response shall set forth sufficient details to support such a position. If an Offeror believes that an actual or perceived OCCI does exist on this procurement, the Offeror shall submit an OCCI plan with the proposal, explaining in detail how the OCCI will be mitigated and/or avoided.

L11. DD254, DoD Contract Security Classification Specification

Offerors must complete Block 6 of the attached DD254 with the appropriate information for their companies. Completed DD254s must be submitted with proposals provided in Section J. Security classification requirements must be met at time of proposal submission.

L12. Organization/Number of Copies/Page Limits

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1 below). The titles and contents of the volumes shall be as defined in Table 1, all of which shall be within the required page limits as specified. The Integrated Master

Schedule (IMS) shall be considered separate and not confined to page limitations of the proposal and shall be included as an appendix to

Volume III.The IMS shall cover the work required to complete the initial task order, which includes the NGLD-M Engineering Development

PWS and NGLD-M Program Management SOW. The contents of each proposal volume are described in the information to Offerors paragraphs as noted in Table 1 below.

Volume I:

Title:Executive Summary

5 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

File Name:xxxxEXESUMxxxx.docx (or PDF) *

Notes: 3 pages

Volume II:

Title:Technical

Sub-Factor 1.1: Hardware and Application Programming Interface(API) Intergration/Description Approach

Sub-Factor 1.2: UAS Approach/KMI Implementation

Sub-Factor 1.3: Management

Sub-Factor 1.4: Production

File Name:xxxxTECHxxxx.docx(or PDF) *

Notes: 60 pages not inclusive of certifications

Volume III:

Title: Cost Narrative

File Name: xxxxCOSTNARRxxxx.docx (or PDF)*

Notes: No Page Limit

Title: Cost Proposal

File Name: xxxxCOSTxxxx.xlsx*

Notes: Cost Proposal - Offerors shall use the format found at Federal Acquisition Regulation (FAR) 15.408, Table 15-2 format. The Cost

Proposal (xxxx COST.xlsx) SHALL be submitted in Excel format (.xlsx) with all formulas visible in each cell with a value.

Title: Sanitized Cost Proposal

File Name: xxxxSANITIZEDxxxx.xlsx

Notes: Sanitized Cost Proposal It shall be the same as the cost proposal but with all costs/prices deleted.

Volume IV:

Title: Past Performance

File Name: xxxxPASTPERFxxxx.docx (or PDF) *

Notes: No page limit, limited to 5 examples

Voulme V:

Title: Small Business Participation

File Name: xxxxSBxxxx.docx (or PDF) *

Notes: 25 pages ; Not inclusive of the SB Subcontracting Plan and SBPCD supporting documentation.

Volume VI:

Title: Contract Documentation

File Name: xxxxCONTRACTDOCxxxx.docx(or PDF) *

Notes: No page limit

*Offerors shall replace xxxx with the Offerors name and the date of the proposal. For example: OfferorACOST03202020.xlsx.

L13. Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations may be placed on responses to evaluation notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. Page limitations shall not be circumvented by including inserted hyperlinked text boxes/pop-ups, internet links to additional information or embedded documents; such inclusions are not acceptable and will not be considered part of the proposal. The Government reserves the right not to consider for award any proposal that does not adhere to the administrative requirements of this solicitation. Each page shall be counted except the following: cover pages, tables of contents, glossaries, OCCI mitigation plans, and 508 compliance information. These limitations shall apply to both electronic and hard copy.

L14. Page Size and Format

A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single spaced/typed. Except for the reproduced sections of the solicitation document, the text size shall be no less than 10-point Times New Roman font for all text. Although exempt from the text size requirement, reproduced documents, which could include but is not limited to letters or certifications, must be legible. The format of the Government provided templates shall remain unchanged and submission is exempt from the format requirements defined in this paragraph. The technical volume of the proposal shall be submitted as either a Microsoft Word

2013 or newer file, and as an Adobe PDF document. Tracking, kerning, and leading values shall not be changed from the default values of

6 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

the word processing or page layout software. Use at least 1-inch margins on the top and bottom and 1 inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs. It is the sole responsibility of the

Offeror to ensure that the electronic files submitted are virus free, and can be opened and read by the Government. Proposal submissions shall not be locked, encrypted, or otherwise contain barriers to opening. The Government is under no obligation to seek clarification regarding electronic proposal submissions if submissions cannot be opened or accessed.

L15. Tables, Charts, Graphs and Figures

Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics; not for pages of text. For tables, charts, graphs, and figures, the text shall be no smaller than 8 Times New

Roman font for all text included in a table.

L16. Cost or Pricing Information

All cost or pricing information shall be addressed ONLY in the Cost/Price Proposal Volumes. Cost trade-off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.

L17. Cross Referencing

To the greatest extent possible, each volume shall be written on a stand alone basis, so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation, which is not found in its designated volume, will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

L18. Cross Reference Matrix

The Offeror shall prepare a Cross Reference Matrix, cross referencing all RFP requirements to the location of the Offerors responses in their proposal. The Cross Reference Matrix provides reference information but is not evaluated. The Offerors format is acceptable. The

Offeror shall include the Cross Reference Matrix as an Appendix to the Technical volume which will not count against the page limitations defined in L12.

L19. Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing or

Microsoft Word Table of Contents formatting shall be used to identify sections.

L20. Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each.

L21. Electronic Offers-Submitting proposals via the worldwide web

Proposals shall include only unclassified information and be addressed to the PCO. All proposal submission must be received in DoD

Secure Access File Exchange (SAFE) before the deadline specified in Section A of this solicitation in order to be considered timely.

All proposals shall be submitted in a single transmission, if possible, to the Government. Multiple SAFE transfers are acceptable if the total proposal file size exceeds 8,000,000,000 bytes. In order to use DoD SAFE offerors must provide a company point of contact

(POC) that will receive a DoD SAFE drop off request to shannon.m.mcbride6.civ@mail.mil and dionna.p.britten.civ@mail.mil. The POC will receive an email with instructions and a pin (valid for 14 days). When the files are dropped off in DoD SAFE, a notification will be received by the Government that the files are available and a confirmation of receipt will be sent to the offeror. The offeror is still solely responsible to ensure that the proposal, and any related files and materials, are received by the Government and can be opened/accessed without issue prior to the due date and time listed above. The Government will consider the proposal submitted based on the time stamped automatically generated by SAFE. It is the Offerors responsibility to confirm receipt of the proposal by the

Government through email.

a. Prior to submitting proposals, the Offeror shall be registered with System for Award Management (http://www.betaSAM.gov ).

b. All proposal volumes shall be submitted in either Microsoft Word

2013 or newer file, and as Adobe Acrobat, Portable Document Format

7 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(Adobe PDF), Version XI; except the Pricing Proposal, which shall be submitted in Microsoft Excel 2013 or newer file. Note: There shall be no page markings with restrictive legend prohibiting the copying and pasting of text for Government use specific to this acquisition.

c. Due Date/Time. The time specified In Section A, is in

Eastern Standard Time (EST). Any proposal, modification, or revision that is received at the ACC-APG Solicitation and Uploads web site specified within this section after the exact time specified for receipt of proposals in Section A is late and will be handled in accordance with FAR 15.208(b) and subparagraphs thereto.

d. Proposals, files, or documents submitted after the closure of the solicitation period will not be considered. .

e. The Offeror shall prepare a readme file, included in Volume I, which describes the proposal organization and layout of the files in its electronic submission. The file shall describe the names of each file included therein. The readme file does not count towards the page limitations defined in paragraph L12 Table 1. The readme file provides descriptive information and is not evaluated.

f. Efforts by the Government to clarify or expedite installation of electronic proposal submissions, in accordance with FAR 15.207(c), will not be considered discussions.

L22. Distribution

Proposals shall be submitted through DoD Secure Access File Exchange (SAFE) and addressed to the PCO and CS.

L23. Volume I Executive Summary

In the executive summary volume, the Offeror shall provide the following information: Narrative Summary and Table of Contents.

L23.1. Narrative Summary

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost and price. The significant features should tie in with Section M evaluation factors/sub-factors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

L23.2 Table of Contents

Include a master table of contents of the entire proposal

L24. Volume II Technical

L24.1 General

The Technical volume should be specific and complete. Responses will be evaluated against the Technical factor defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology to be used for accomplishing/satisfying these factors. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

In the Technical volume, address the proposed approach to meeting or exceeding the minimum performance or capability requirements of each technical sub-factors. A concise and comprehensive proposal is desired. Organization, clarity, accuracy of information, relevance and completeness are prime importance. Cursory responses or responses which merely reiterate or reformulate solicitation language will not be considered as satisfying the requirements of the RFP, or as demonstrating the ability to perform. Elaborate brochures or other presentations beyond that sufficient to present a complete and effective proposal are not desired. Elaborate artwork and expensive visual or other presentation aids are not necessary and will not be considered.

L 24.1.1 Demonstrations

The Government is permitting Offerors, at their request, the option to provide a demonstration of their ability to meet the NGLD-M

8 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

requirements to designated members of the Government evaluation team. The Government will only support virtual demonstrations for this solicitation. The Government will use the demonstration as supplemental information to assist in determining the combined technical/risk adjectival rating only for sub-factor 1.1 Hardware and API Integration/Description approach and sub-factor 1.2 UAS/KMI Implementation approach of the Technical proposal. The Government intends to begin demonstrations fifteen (15) business days after the close of the solicitation period and close ten business days thereafter. If desired, the Offeror shall request a demonstration to the Government at submission of the proposal For virtual demonstrations, the Offeror must provide the medium to support the virtual demonstration and conduct a communications check with the Government at least one day prior to the demonstration. The communications check will not be evaluated but will ensure everyone can connect to the communication medium prior to the actual demonstration. Demonstrations will be limited to one hour in duration and will be timed by the Government. When an hour is complete the demonstration will end and no further information will be considered by the government. During the demonstration, the Government will only observe the information provided by the Offeror and will not ask any questions. The Offeror shall focus the demonstration on the criteria defined in Sub-Factor 1.1

Hardware and API Integration/Description Approach and/or Sub-Factor 1.2 User Application Software (UAS)/KMI Implementation Approach. The

Offeror can allocate as much or as little time for each element. Offerors can use a Microsoft PowerPoint presentation but the information can only be an excerpt from the Technical Volume of the Proposal.

L24.2 Format and Specific Content

The Technical volume has been divided into four sub-factors: 1) Hardware and API Integration/Description Approach, 2) UAS Approach/KMI

Implementation Approach, 3) Management, 4) Production. The Offeror has the option of applying any number of pages to each of the four factors so long as the total page limit for the Technical volume does not exceed the overall page limit. The Offeror shall submit any certification documentation as an appendix to the technical volume, which will not count towards the page limitations defined in Table

1. The Technical volume shall comply with the guidance in paragraph L14 Page Size and Format. The Contractor shall include any Data

Assertion Tables as an Appendix to the Technical volume which will not count towards the Technical volume page limit.

L24.3 Sub-Factor 1.1 Hardware and API Integration/Description Approach

L24.3.1 Element 1.1.1: Physical Design

The Offeror shall describe it's proposed NGLD-M physical design to a level of detail that provides the Government confidence that the proposed design will meet Size, Weight and Power (SWAP), display, environmental, safety and occupational health, TEMPEST, external interface and battery requirements or other objective requirements listed in the SRD. The Offeror shall identify any significant up-front risks associated with meeting these requirements, based on their proposed physical design.

L24.3.2 Element 1.1.2 API Integration/Description

The Offeror shall specify whether they will be developing their own UAS or if they plan on using the government developed User

Application Software. If the Offeror chooses to use the government developed UAS, the Offeror shall describe their approach on how it will integrate the government defined APIs for the UAS with their proposed solution.

If the Offeror chooses to develop their own UAS, the Offeror shall provide details regarding the System Requirements Document (SRD) requirements such as ease of programming /re-programmability, maintainability, operating system constraints (e.g., licensing requirements, patching, upgradability), and expandability. The Offeror shall describe the Application Programming Interface (API) of the proposed implementation for compliance with modularity.

L24.3.3 Element 1.1.3 Security

The Offeror shall describe their experience and plan for implementing the security requirements for NSA certified devices and DoDI

8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), Mar 2014. The Offeror shall describe how cybersecurity concerns will be addressed throughout the duration of the contract. The Offeror shall describe any third party utilities that will be leveraged in the design and validate that they are free of supply-chain security concerns.

L24.3.4 Element 1.1.4 Sustainment Strategy

The Offeror shall describe the system life cycle approach and maintenance concept of the fielded NGLD-M to include warranty strategy, logistics, reliability attributes, and Government organic sustainment strategy for the proposed design.

The Offeror shall describe their approach for developing training materials that appropriately addresses the operational and maintainability tasks necessary to sustain the NGLD-M. The Offeror shall address plans for modularity, ease of loading and maintenance.

The Offeror shall explain how its proposal facilitates competitive procurement of NGLD-M software and hardware maintenance, sustainment, and integration services from third parties (i.e., contractors other than the original manufacturer or developer) by the Government using the technical data and software deliverables under this contract. Specifically, the Offeror shall demonstrate understanding of the technical data and computer software rights under this contract in a tabular format prescribed in DFARS 252.227-7017 above and explain how its proposal facilitates competitive procurement of NGLD-M software and hardware maintenance/sustainment services for technical data and software deliverables, in any instances where the Government will only be provided Limited Rights, Restricted Rights, or other restrictions (such as restrictions in commercial software license agreements). If the Offeror will be providing the Government

9 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

with broader license rights in technical data and software deliverables than the Government is normally entitled to under DFARS 252.227-

7013, DFARS 252.227-7014, or the standard commercial software license agreements, and there will be additional costs incurred by the

Government for these broader license rights, then the Offeror shall provide an itemized list of these additional costs in the Pricing section of the Offerors Cost Proposal.

L24.3.4.1 Data Rights Assertion

Pursuant to the requirements set forth in DFARS 252.227-7017, Offerors are required to specifically identify Data/Software Rights

Assertions related to technical data and software deliverables (at the base contract level and task order level). As indicated in DFARS

252.227-7017(e), an Offeror's failure to submit, complete, or sign the aforementioned Data and Software Rights Assertions with its offer may render the offer ineligible for award. In accordance with the content and formatting requirements for Data and Software Rights

Assertions (set forth in DFARS 252.227-7017), the Offeror's Data and Software Rights Assertions shall comply with the following requirements:

1) The Offeror 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.

2) The Offeror's Assertions shall not include technical data or software that will not be furnished to the Government under this

Contract.

3) The Offeror 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".

4) The Offeror 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).

Offerors 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 Offerors Data/Software Rights Assertions table shall list technical data and software items that the Offeror 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 Offerors identification of technical data and software license rights, the Offeror shall use the prescribed categories of license rights referenced in DFARS 252.227-7014 and DFARS 252.227-7015 (e.g,. Limited Rights, Government

Purpose Rights, Unlimited Rights, Unrestricted Rights, or Commercial Software License Agreement).

L24.4 Sub-Factor 1.2. UAS Approach/KMI Implementation

Use of the Government UAS relieves the Offeror from providing any additional information for this sub-factor, apart from a statement that the Offeror will utilize the Government UAS. If the Offeror is choosing to develop and deliver their own UAS solution, the Offeror shall describe the proposed NGLD-M UAS design from perspectives aligned with the below Elements. This description shall be at a level of detail that provides the Government confidence that the Offeror has a design that will allow this UAS to satisfy the SRD requirements, incorporates KMI capabilities and management design requirements, takes non-functional requirements into consideration, and ensures fulfilment of all security requirements.

L24.4.1 Element 1.2.1: Interface Description

The Offeror shall describe each NGLD-M physical and logical interfaces and its procedural exchange with varied external components. The

Offeror shall explain the process from both the system and user perspectives providing a detailed explanation of all device interface(s) and all external component(s).

L24.4.2 Element 1.2.2: Internal Product Management and Maintenance

The Offereor shall describe how the NGLD-M plans to process varied COMSEC content retrieved via each interface described in the

Interface Description section. This description shall include details of each authenticator and encryptor required to process COMSEC content, and how the NGLD-M will maintain each authenticator and encryptor.

L24.4.3 Element 1.2.3: Architecture Design

The Offeror shall describe the NGLD-M UAS architecture design identify how the design incorporates the following characteristics:

Compatibility / Portability

Interoperability

Usability

Adaptability

Maintainability / Sustainment

Performance

10 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L24.4.4 Element 1.2.4: Security Design

The Offeror shall describe the NGLD-M UAS architecture and the methodology to incorporate the security requirements to accommodate the

Security Requirements for NSA Certification and Authority To Operate (ATO) on DoD networks Risk Management Framework (RMF) guidelines.

L24.5 Sub-Factor 1.3: Management

L24.5.1 Element 1.3.1 Management Approach

The Offeror shall describe their proposed approach for meeting the programmatic, engineering, quality and sustainment services and management requirements, as specified in the NGLD-M ID/IQ PWS, Management Task Order (TO) and Engineering Development TO. The Offeror shall describe the major management activities, to include their approach to managing subcontractors, planned to ensure NGLD-M requirements and risks are properly defined, assessed and tracked throughout the programs development cycle, and that products and services are delivered per contractual requirements. The Offeror shall describe any activities incorporated into the Offerors proposed approach that will lead to risk reduction in terms of overall program performance and schedule.

L24.5.2 Element 1.3.2 Systems Engineering

The Offeror shall describe their proposed Systems Engineering approach for the design, development, test, production, fielding, sustainment and improvement of the NGLD-M. The Offeror shall describe any advantages associated with their planned use of industry standards (not already required by this solicitation) to be used during analysis, design, development, integration and production of the

NGLD-M. The Offeror shall describe how their proposed systems engineering approach leads to a design that can be cost effectively and supported throughout the systems life cycle (from program initiation to system retirement).

L24.5.3 Element 1.3.3 Property Management Plan

The Offeror shall provide a Property Management Plan, in accordance with FAR 52.245-1(f)(1)(i-x), describing its approach to managing government property throughout the performance of the Delivery Order. The Property Management Plan shall be included as an appendix to

Volume II and will not count against the total page count (two-page limit). The Offeror shall provide a brief overview addressing the following ten outcomes:

1) Acquisition. How property acquisitions are documented, per FAR 52.245-1(f)(1)(i).

2) Receipt. How property receipt is documented, recorded, and identified per FAR 52.245-1(f)(1)(ii).

3) Records of Government Property. How property records are created and maintained, per FAR

52.245-1(f)(1)(iii).

4) Physical Inventory. Methods to perform, record, and disclose physical inventory results, per FAR 52.245-1(f)(1)(iv).

5) Subcontractor Control. Whether contractual terms and conditions are flowed down to subcontractors, per FAR 52.245-1(f)(1)(v)(A); how subcontracts are properly administered; and, when reviews of subcontractor Property Management Systems are performed, per FAR 52.245-

1(f)(1)(v)(B).

6) Reports. The process to create and provide property-related reports, per FAR 52.245-1(f)(1)(vi).

7) Relief of Stewardship Responsibility and Liability. The process to recognize, investigate, and report losses of Government property, per FAR 52.245-1(f)(1)(vii).

8) Utilization. How Government property is to be used, consumed, moved, and stored, per FAR 52.245-1(f)(1)(viii).

9) Maintenance. How Government property is to be maintained, and when property requiring replacement and/or capital rehabilitation is to be reported to the Property Administrator, per FAR 52.245-1(f)(1)(ix).

10) Property Closeout. How property closeout is performed and when it is reported to the Property Administrator, per FAR 52.245-

1(f)(1)(x).

L24.6 Sub-Factor 1.4: Production

The Offeror shall describe their Production Capacity (i.e., facilities and equipment); Production Proficiency (i.e., skill sets, manufacturing process certifications and complex systems integration experience); and Material Management processes (e.g. supply-chain management); and how each of these will be applied to satisfy NGLD-M production requirements for Prototypes, certified Pre-Production

Units (PPUs), Low Rate Initial Production (LRIP) and Full Rate Production (FRP).

11 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L24.7 Volume Organization The Technical Volume shall be organized according to the following general outline:

1) Table of Contents

2) Glossary

3) Sub-Factor 1.1: Hardware and API Integration/Description Approach

a. Element 1.1.1: Physical Design

b. Element 1.1.2: API Integration/Description

c. Element 1.1.3: Security

d. Element 1.1.4 Sustainment Strategy

4) Sub-Factor 1.2: UAS Approach/KMI Implementation Approach

a. Element 1.2.1 Interface Description

b. Element 1.2.2 Internal Product Management and Maintenance

c. Element 1.2.3 Architecture Design

d. Element 1.2.4 Security Design

5) Sub-Factor 1.3: Management

a. Element 1.3.1 Management Approach

b. Element 1.3.2 Systems Engineering

6) Sub-factor 1.4: Production

L25. Volume III Cost

L25.1. General Instructions

This section is to assist Offerors in submitting cost or pricing data that is required to evaluate the reasonableness, completeness, realism, and balance of the proposed cost. The Government will verify that all solicitation requirements have been priced, figures are correctly calculated, and prices are presented in a clear and useful format. Note that unrealistically low or high proposed costs, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the Offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally, unbalanced costs pose an unacceptable risk to the

Government and may be a reason to reject an Offerors proposal. Cost submissions should be sufficiently detailed and provide supporting documentation to demonstrate their reasonableness and be adequate enough to support and sustain a DCAA audit. The Offeror shall propose its approach to staffing this requirement. It is the sole responsibility of the Offeror to propose labor mix and hours sufficient to perform the work as detailed in the PWS or SOW.

L25.2. Price and Cost Narrative

The offeror shall describe their methodology used to establish their cost and price.

Each Offeror shall provide whatever information is necessary to help the Government understand why the proposed costs are realistic in the xxxxCOSTNARRxxxx.docx (or PDF). Additionally, each Offeror shall ensure any proposed cost-reimbursement subcontractors provide whatever information is necessary to help the Government understand why the proposed subcontractor costs are realistic in the subcontractors xxxxCOSTNARRxxxx.docx (or PDF). Each Offeror's cost proposal shall contain sufficient quantitative and narrative documentation to adequately support and explain the costs proposed, to include subcontractor proposed costs.

The Offeror shall state if it will require the use of Government property in the performance of the contract other than that specified in Section J. If Government property is required, the Offeror shall include a table in its cost narrative containing: 1) what property is needed, 2) the acquisition cost of each item, and 3) the duration (in months) that the GFP would be in the possession of the Offeror for the performance of this effort.

Each Offeror shall identify all proposed subcontractors and the contract type the Offeror has with each subcontractor in its xxxxCOSTNARRxxxx.docx (or PDF). IAW FAR 15.404-3(b), the prime contractor or subcontractor shall: (1) Conduct appropriate cost or price analyses to establish the reasonableness of proposed subcontract costs/prices; and (2) Include the results of these analyses and methodology utilized in these analyses in the cost/price proposal. The Offeror or subcontractor shall identify whether it relied upon its approved purchasing system to establish its subcontracts; if the Offeror relied up on its approved purchasing system it shall provide documentation of its approved purchasing system (including date of approval) within its xxxxCOSTNARRxxxx.docx (or PDF) (see FAR

15.404-3).

Reference FAR 15.404-3: If the Offeror is unable to obtain the required documentation from its subcontractors in order to conduct the appropriate cost or price analysis as required, then the subcontractor shall provide the information directly to the Government following the exact submission instructions of this RFP. In this scenario, the Offeror shall provide the rationale detailing exactly why the Offeror is unable to conduct the subcontractor price or cost analysis required by FAR 15.404-3 in its xxxxCOSTNARRxxxx.docx (or

PDF). For example: if it is required for a subcontractor to provide a price/cost analysis that has a breakout of the individual cost

12 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

elements, but the subcontractor is unable to provide its proprietary data to the Offeror, then the Offeror may conduct a total price analysis, according to FAR 15.404-1(b), and the subcontractor shall submit its proprietary cost breakout directly to the Government.

In support of the proposed direct labor rates, the Offeror and its subcontractor(s) shall provide documentation of the most recent direct labor rates, to include at least one (1) of the following (a, b, c, or d):

a. Forward Pricing Rate Agreements (FPRA), Forward Pricing Rate Recommendations (FPRR) from Defense Contract Audit Agency (DCAA) or

Defense Contract Management Agency (DCMA), Forward Pricing Rate Proposal (FPRP) or

b. Letter(s) of Intent (LOIs), which include, at a minimum, the following:

i. Position;

ii. Direct hourly rate;

iii. Submitted on offerors or subcontractors letterhead;

iv. Signed by the employer and prospective employee; and

v. A statement that the LOI is for RFP W15P7T-20-R-0011

c. Payroll records and/or paystubs showing rate of pay, and referenced to the labor category in the proposal.

d. Salary survey data to include copies or screen shots of the actual salary survey data, which at a minimum, shall include the following:

i. Source of data;

ii. Job title and description;

iii. Geographic location; and

iv. Range of salary amounts with reference to applicability of amounts.

Note 1: If using salary survey data to support direct labor rates, the Offeror shall not propose any direct labor rates below the 50th percentile for any labor category requiring Top Secret clearance and should not propose any direct labor rates below the 25th percentile for all other labor categories. Proposed rates below those percentiles may be found unrealistic.

Note 2: If the rates proposed are not fully supported and/or the Government is unable to determine the realism of proposed labor rates, the Government may use salary survey data from Economic Research Institute or other sources to make necessary adjustments.

In support of the proposed indirect expense rates, offeror and its subcontractor(s) shall provide documentation of the most recent indirect expense rates, to include at least one (1) of the following (a, b, c, d, e, or f):

a. Most recent FPRA(s) with DCAA or DCMA

b. Most recent FPRR(s) from DCAA or DCMA

c. Most recent Forward Pricing Rate Proposal (FPRP)

d. Approved Provisional Rates Proposal

e. Other statement of current rates

f. If an entity cannot include A-C above because it restructured or is a new entity, that company shall provide proof to include the date it restructured or the date the new entity was formed. The offeror shall also include the pools and bases as well as all historical data detailing pools and bases information (by expense account) which validates the calculation from the date of the restructuring.

Note for paragraphs c, d, and e: If an Offeror supports proposed indirect rates utilizing documentation options c-e above, the offeror shall include forecasted pools and bases for the current year (by expense account). Additionally, the Offeror shall support these rates with three years historical actual pools and bases (by expense accounts) information that validates the calculations.

NOTE 1: The rates reflected in the FPRA, FPRR, FPRP, Approved Provisional Rates Proposal or other statement of current rates should directly match the rates proposed by the Offeror or subcontractor. If the rates do not match, the Offeror or subcontractor shall provide sufficient detail explaining how the proposed rates are realistic.

NOTE 2: The Government defines experience levels for proposed labor categories as follows: Intern 0-1 year; Junior 2-4 years;

Intermediate 3-6 years; and Senior 7+ years.

If the Offerors proposal includes accounting approaches that deviate from standard industry accounting practices or caps proposed indirect rates, the Offeror shall include documentation from the Defense Contract Management Agency (DCMA)/ the Defense Contract Audit

Agency (DCAA) showing that the Offerors accounting system/cost accounting standards allow for the deviation and/or rate cap. Approved deviations and/or rate caps will be incorporated into the resulting task order.

Each offeror and any subcontractor(s) shall include in its cost narrative a CAGE Code, DCAA and DCMA point of contact name, telephone

13 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

number and email address.

Offerors shall structure their xxxxCOSTxxxx.xlsx document IAW the CLIN structure in Section B of the RFP.

Offerors shall include a summary tab in their xxxxCOSTxxxx.xlsx broken out by cost element as specified in FAR 15.408, Table 15-2 for the total proposed price. Included in the summary tab shall be a column that serves as a reference.