Attachment_0004_Section_L.pdf

W52P1J-19-R-0054 Attachment 0005

Section L

SECTION L – Instructions, Conditions, and Notices to Offerors

SECTION L

L.1 PROPOSAL SUBMISSION INSTRUCTIONS

L.1.1. GENERAL

Offeror shall submit a proposal in accordance with (IAW) Proposal Submission Instructions provided herein. The Offeror’s proposal shall be signed and submitted by an individual having authority to enter into a contract on the Offeror’s behalf based on the submitted proposal. An Offeror’s proposal shall be written in English language.

L.2. PROPOSAL PREPARATION & ORGANIZATION

L.2.1. INTRODUCTION

L.2.1.1. IAW Federal Acquisition Regulation (FAR) clause 52.212-1, Instructions to Offerors – Commercial Items (Oct 2018), the Government intends to evaluate offers and award a contract without discussions, but the Government reserves the right to conduct discussions if the Contracting Officer later determines that discussions are necessary. Offerors are encouraged to examine the solicitation in its entirety, and to ensure that its proposal contains all necessary information, provides all required documentation, and contains the Offeror’s best terms from a price and technical standpoint.

Notwithstanding FAR clause 52.212-1(e), each Offeror shall submit only one, unique proposal (with required copies IAW Table 1.1) that addresses all Government requirements outlined in the solicitation. The Government will not evaluate more than one proposal from each Offeror. The Offeror’s proposal shall consist of three volumes as outlined below:

(a) Volume (Vol.) 1 – Price

(b) Vol. 2 – Technical

(c) Vol. 3– Solicitation, Offer and Award Document (Form SF33) and

Certifications/Representations

L.2.1.2. Files shall not contain classified data. The use of hyperlinks in proposals is prohibited.

L.2.1.3. Proposals shall be submitted electronically via email to Trisha Mariman, Procuring Contracting Officer (PCO), at trisha.m.mariman.civ@mail.mil and Ashley Griffin, Contract Specialist, atashley.l.griffin20.civ@mail.mil.

mailto:trisha.m.mariman.civ@mail.mil mailto:atashley.l.griffin20.civ@mail.mil

The Government can only accept individual emails up to 20 MB in size, including the email itself plus all attachments. If the Offeror’s proposal is larger than 20 MB, separate emails are permitted. When submitting multiple emails, the Offeror shall sequentially number each email (e.g., 1 of 3, 2 of 3, etc.). It is incumbent on the Offeror to ensure that the Government has received the complete proposal BEFORE the solicitation due date and time.

L.2.1.4. Late Submissions An Offeror’s proposal, modification(s), revision(s), or withdrawal will be IAW FAR 52.212-1. IAW FAR 52.212-1(f), Offerors are responsible for submitting proposals, and any modifications or revisions, so as to reach the Government office designated in the solicitation by the time specified in the solicitation.

L.2.1.5. Communications

L.2.1.5.1. Formal Communications The solicitation, amendments, notices, and other information will be made available on FedBizOpps at http://FBO.gov.

L.2.1.5.2. Offerors are advised to monitor the FedBizOpps website continuously for any new information regarding this solicitation. Offerors are deemed to have knowledge of all documents related to this solicitation that are posted to FedBizOpps.

L.2.1.5.3. Solicitation Amendment Should an amendment be issued against the solicitation, the Offeror shall acknowledge it by signing the Standard Form (SF) 30, entitled Amendment of Solicitation/Modification of Contract, and include it in Vol. 3 of the proposal submission.

L.2.1.5.4. Solicitation Questions.

All questions pertaining to solicitation shall be addressed to the PCO, Trisha Mariman at trisha.m.mariman.civ@mail.mil, and to the Contract Specialist, Ashley Griffin, at ashley.l.griffin20.civ@mail.mil, and shall be submitted no later than three calendar days after the release of the solicitation. The Government is not obligated to provide responses to all questions submitted by Offerors, but will consider questions and incorporate changes into the solicitation as deemed necessary. Government responses to questions will be posted at www.fbo.gov for review by all Offerors; therefore, questions/comments shall not be marked with a restrictive legend, and shall not include proprietary information.

When submitting questions and comments, please refer to the specific text of the solicitation in the following format:

Subject: Solicitation No. W52P1J-19-R-0054 http://fbo.gov/ mailto:trisha.m.mariman.civ@mail.mil mailto:ashley.l.griffin20.civ@mail.mil http://www.fbo.gov/

Reference: Solicitation Section ___, Paragraph(s) ____, Page(s) ____.

It is preferred that only one set of questions be submitted by each Offeror, instead of multiple sets of questions.

L. 2.1.5.5. During the evaluation process, the Government may, at its discretion, enter into clarifications or communications, as needed. The Government need not enter into communications or clarifications with all Offerors. In evaluating the proposals, the Government will evaluate the lowest-priced proposals first, and may not evaluate all proposals, if three (3) technically acceptable proposals are received from the lowest-priced proposals. Any Offeror eliminated from further consideration, to include Offerors that submitted proposals that were not technically evaluated, will be notified officially in writing.

L.2.1.5.6.

Definitions are as follows:

Acceptable: Proposal meets the minimum requirements of the solicitation.

Unacceptable: Proposal does not meet the minimum requirements of the solicitation.

Clarifications: Clarifications are limited exchanges, between the Government and Offerors, that may occur when award without discussions is contemplated.

Communications: Communications are exchanges, between the Government and Offerors, after receipt of proposals, leading to establishment of the competitive range.

Discussions: Discussions are negotiations conducted after the establishment of a competitive range that may, at the Contracting Officer’s discretion, result in the offeror being allowed to revise its proposal.

Uncertainty: Any aspect of a non-cost/price factor proposal for which the intent of the offer is unclear (e.g., more than one way to interpret the offer or inconsistencies in the proposal indicating that there may have been an error, omission, and/or mistake).

L.3. PROPOSAL FILES.

L.3.1. GENERAL

Each Offeror is required to submit all three proposal volumes and comply with the instructions contained in Section L. The Offeror shall be held responsible for the validity of all information supplied in its proposal, including information provided by potential subcontractors. The Government does not assume the duty to search for data to cure problems it finds in the proposals. The burden of providing thorough and complete information remains with the Offeror.

L.3.1.1. The Offeror's proposal shall be submitted in separate volumes, as set forth in Table 1.1. All information pertaining to a particular volume shall be confined to that volume to facilitate independent evaluations. The Government will evaluate the information contained in each volume separately; therefore, each volume must stand on its own. No price information shall be presented in any part of the proposal, except in Volume 1 (Price).

To minimize proposal size, duplication of statements within a proposal volume may be avoided by referencing that statement's location after it appears in full text for the first time. The Offeror must not merely re-state the requirements stated in the solicitation. Narratives must establish demonstrable evidence in support of any statements relating to promised capabilities. Unsupported statements to comply with the contractual requirements will not be adequate.

L.3.2. Format.

L.3.2.1. Each volume shall consist of a Title Page, a Table of Contents, and the respective volume’s proposal.

L.3.2.2. The Title Page shall contain the title of the volume, name of the Offeror, and date of submission.

L.3.2.3. The Table of Contents shall include references to the proposal page number and paragraph of all major items. The Table of Contents shall be created using the Microsoft (MS) Word Table of Content feature. MS Word files shall use the following page set-up parameters:

Margins – Top, Bottom, Left, Right –1.0” Gutter – 0” From Edge – Header, Footer – 1.0” Page Size, – 8.5” (Width) x 11” (Height)

L.3.2.4. Consecutive page numbering within each volume is required. The header and/or footer on each page shall include the Offeror’s name, proposal date, and solicitation number.

L.3.2.5. Paragraphs shall be numbered and titled. Paragraphs shall be separated by at least one blank line.

L.3.2.6. The following additional format restrictions apply:

(a) A standard, 12-point Arial minimum font size is required.

(b) Tables and illustrations should be labeled or titled, and referenced.

(c) Tables, charts, figures, etc. should be used for data, and not to capture narratives. Narratives are not to be included in table(s) or chart(s).

(d) Any text, tables, charts, figures, etc. that do not comply with the above restrictions will not be considered and will not, therefore, be evaluated.

L.3.2.7. Digital files shall be compatible with MS Office 2013. Each Offeror shall add its respective company name to the file names listed in Table 1.1, i.e., “Company Name V1A1.docx.”

L.3.2.8. MS Excel worksheets are considered one page each for page count purposes. MS Project GANTT/PERT charts are excluded from the page count restrictions.

L.3.2.9. Page count requirements for each proposal volume are listed in Table

1.1. Those pages that exceed the page counts outlined in Table 1.1 will not be evaluated.

Table 1.1*

Volume No. / Title File Name

Maximum # of Pages

Vol. 1 / Price Proposal V-1 Vol. 1 - No page limit;

submit completed

Price Model Vol. 2 / Technical V-2 50 Page Limit

• Hardware Table V-2-1 Not Part of Page Limit

• Hardware Technical Narrative V-2-1TN Part of 50 Page Limit

• Hardware Technical Data Sheets V-2-1DS Not Part of Page Limit

• Software Table V-2-2 Not Part of Page Limit

• Software Technical Narrative V-2-

2TN

Part of 50 Page Limit

• Software Technical Data Sheets V-2-2DS Not Part of Page Limit

• AIT-6 System Requirement V-2-3 Part of 50 Page Limit

• Security Requirements V-2-4 Part of 50 Page Limit

• Methodology Process for Turnkey

Solutions V-2-5 Part of 50 Page Limit

• Bill of Material BOM V-2-6 Not Part of Page Limit

• Technical Proposal Matrix V-2-7 Not Part of Page Limit

• Graphical Technical Interface

Diagrams V-2-8 Not Part of Page Limit

*Each volume’s Title Page and Table of Content requirements are excluded from the page limitations.

L.4. VOLUMES:

L.4.1. VOLUME 1 – PRICE PROPOSAL

L.4.1.1. The Price Model (reference Section J, Attachment 0003 “Price Model”) is for the total price of each Contract Line Item Number/Sub-Line Item Number (CLIN/SLIN), and shall be completed in its entirety to show a Total Evaluation Price (TEP) for evaluation purposes. Offerors are required to propose for all CLINs. An Offeror will be considered non-responsive if all line items are not completed.

L.4.1.2. All prices shall be limited to two decimal places stated in US dollars . The Offeror's proposal may be rejected if the proposed prices provided are not whole numbers. Furthermore, prices must be submitted on a Freight on Board (FOB) Destination basis and in U.S. dollars.

L.4.1.2. The proposed pricing for Expedited Delivery, Incidental Material, and Travel is Non-Fee bearing.

L.4.1.3. Instructions for completion of the Price Model are contained in the tab labeled “Instructions” in Attachment 0003, “Price Model.” Offerors are required to state binding prices. Offerors may not make any changes or add information to the Price Model.

Note that the quantities listed within the “Price Model” (Sect. J, Attachment 0003) are Government estimates for evaluation purposes and do not constitute actual Government requirements.

L.4.2. VOLUME 2 – TECHNICAL

L. 4.2.1.

The Technical approach shall demonstrate the Offeror’s technical capability and understanding of the requirement. The Offeror must demonstrate the ability to provide

Vol. 3 / Solicitation, Offer and Award Document and Certifications / Representations

V-3 Vol. 3 - No page limit;

submit pages as required.

• Standard Form (SF) 33 V-3-1

• Certifications/Representations V-3-2

• Solicitation Amendments (if applicable) V-3-3 hardware and software identified for AIT-6 equipment maintained for Department of Defense (DoD), North Atlantic Treaty Organization (NATO), and Coalition Partners in dynamic, global AIT environments, as stated in the Performance Work Statement (PWS) (reference Section J, Attachment 0001 “PWS AIT-6”).

L.4.2.2. Hardware. The Offeror shall produce a Hardware Table that replicates all of the requirements for AIT-6 PWS Section 4 (format example shown in Example #1 Hardware Table), indicate if the Offeror’s hardware meets requirement, and lists a location in the Hardware Narrative and/or Technical Data Sheets that this can be verified.

Example #1 – Hardware Table:

Hardware Requirement Offeror’s Hardware

Meets Requirement

Supporting Documentation

4.3.4 STATIONARY BAR CODE LABEL

PRINTER.

Yes/No

a. Built in diagnostic display and keypad for configuration and troubleshooting;

Yes/No V-2-1TN Paragraph x.x

b. USB, and Ethernet communications ports; Yes/No V-2-1DS Page x

c. Delivered with a USB interface cable; Yes/No

d. On-demand printing for at least 16 hours per day;

Yes/No

e. Use a roll of label stock with a diameter of 8 inches;

Yes/No

f. Automatic sensing for different label sizes; Yes/No

g. Minimum print speed of 6 inches-per-second;

and

Yes/No

h. Dispense a self-stripped label on demand for the Stationary Bar Code Label Printer with Installed Take-Up Reel.

Yes/No

L. 4.2.2.1. The Offeror may inform the Government of any relevant or significant conditions with regard to any of the requirements listed in the Hardware Table in its Hardware Narrative. Do NOT include narrative(s) in the Hardware Table.

L. 4.2.2.2. Separate from the Hardware Table, Technical Data Sheets shall be provided for all hardware offered. The Technical Data Sheets shall be labeled with its associated hardware SLIN(s).

L.4.2.3. Software. The Offeror shall produce a Software Table that replicates all of the requirements for AIT-6 PWS Section 5 (format shown in Example #2 Software Table) and indicate if the Offeror’s software meets requirement.

Example #2 – Software Table:

Software Requirement Offeror’s Software

Meets Requirement Supporting

Documentation

5.1.2 BAR CODE PRINTING

SOFTWARE.

Yes/No V-2-2TN Paragraph x.x

L.4.2.3.1. Offeror may inform the Government of any relevant or significant conditions with regard to any of the requirements listed in the Software Table in its Software Narrative. Do NOT include narrative(s) in the Hardware Table.

L.4.2.3.2. Separate from the Software Table, Technical Data Sheets shall be provided for all software offered. The Technical Data Sheets shall be labeled with its associated software SLIN(s).

L.4.2.4. AIT-6 System Requirements. The Offeror shall provide a narrative illustrating the methodology and process to be used to implement the AIT-6 System Requirements, as defined by PWS Section 3 (reference Section J, Attachment 0001 “PWS AIT-6”).

L.4.2.5. Security Requirements. The Offeror shall provide a narrative illustrating the methodology process to be used to implement the Security Requirements, as defined by PWS Section 6 (reference Section J, Attachment 0001 “PWS AIT-6”).

L.4.2.6. Methodology Process for Turnkey Solutions. The Offeror shall provide a narrative describing the methodology to be used to implement an AIT turnkey solution.

The methodology shall include, but is not limited to, all assumptions relevant to the utilization of hardware, software, AIT architecture, and integration with automated information systems to demonstrate the process followed from initial approach to final solution.

L.4.2.7. Bill of Material (BOM). Based on the Price Model (reference Section J, Attachment 0003 “Price Model”), the Offeror shall provide a detailed list of all the items proposed for each hardware and software CLIN (see Example #3 - BOM). Each BOM shall correlate to a Price Model SLIN and SLIN description, and shall consist of the proposed item’s detailed description, name, part number, and name and quantity of all individual subcomponent parts (e.g., number of batteries, RF/Power/Data cable assemblies, battery chargers, adapters, etc.). The Offeror's BOM shall describe the actual proposed configuration(s), and shall NOT include items that are not included with the SLIN, i.e., optional equipment. The Offeror shall provide the requested BOM information in the format shown in Example #3 BOM.

Example #3 – BOM:

CLIN /

SLIN

Products / Services

Model/Part Number

Description Quantity

SLIN

0025 YE

Hand Held Terminal

(HHR-Y) [NI

Certified]

ABC Company

XTC-100ABC

XTC-100ABC w/QWERTY-

NUMERIC, NI

(includes RFID and operational battery)

[ABC]

(manufacture name) 123-456-xxx (P/N)

Minimum 2GB SD Memory Card (installed)

ABC DK-240 Desktop Dock for XTC- 100ABC Simultaneously charges one XTC-100ABC and two battery packs.

ABC 123-456-002 Desktop Dock Power Supply

ABC 123-456-003 Desktop Dock Power Cord 1 ABC 123-456-004 Scan Handle, XTC-

100ABC

ABC 123-456-005 Spare Battery Pack, XTC-

100ABC

ABC 123-456-006 USB Interface Cable 1 N/A CD (DVD), Software and

Documentation

L.4.2.8. Technical Proposal Matrix. The Offeror shall provide a matrix demonstrating compliance with the requirements in the AIT-6 PWS Sections 3 and 6 (reference Section J, Attachment 0001 “PWS AIT-6”). Note: The AIT-6 PWS Sections 4 and 5 requirements are addressed in the Hardware and Software Tables and do not need to be duplicated in the Technical Proposal Matrix.

One column of the matrix shall indicate where each of the PWS requirements is addressed in the Offeror’s proposal (i.e., Section Number, Page Number, Paragraph Number, etc.) (format example shown in Example #4 Technical Proposal Matrix).

Example #4 – Technical Proposal Matrix:

PWS Requirement (Paragraph Number and Title)

Offeror’s Proposal Sections that address the PWS

Requirement

3.8 BAR CODE

SYMBOLOGIES.

Section(s), Page(s), Paragraph(s)

L.4.2.9. Graphical Technical Diagrams. The Offer shall provide graphical technical diagrams for the following SLINs: 0001DA (wireless and batch modes), 0001EA (wireless and batch modes), and 0011AA. The diagrams shall provide graphical depictions of any components that are required for the product to function (e.g., cables, adaptors, etc.).

L.4.2.10. AIT-6 Product Demonstration Requirements. Offerors will be required to perform AIT-6 Product Demonstrations, as illustrated in "Product Demonstration Requirements" (reference Section J, Attachment 0002 “Product Demonstration Requirements”). Offerors will be notified within two (2) weeks after proposals have been received as to a designated demonstration date. All demonstrations will be completed within six (6) weeks of receipt of proposals.

L.4.3. VOLUME 3 – SOLICITATION, OFFER AND AWARD (Form SF33)

DOCUMENT AND CERTIFICATIONS/REPRESENTATIONS

L.4.3.1 Each Offeror shall complete the solicitation sections indicated below using the file document (without modification to the file) provided with the solicitation. An authorized official of the firm shall sign the Standard Form 33 (SF 33) and all certifications requiring an original signature. An Acrobat PDF file shall be created to capture the signatures for submission. The format specified in paragraph L.3.2does not apply to Vol. 3. Offerors shall complete the following:

(a) Solicitation Section A –SF 33, Solicitation, Offer and Award,

(b) Solicitation Section G, Contract Administration Data,

(c) Solicitation Section I, Contract Clauses (Fill-in only clauses)

(d) Solicitation Section K – Representations, Certifications and Other Statements of Offerors. Offerors shall complete the Representations and Certifications in Section K. In the event of a conflict between the Offeror's proposal and the solicitation, the solicitation shall take precedence. Offerors shall also include in this section their signed disclosure agreement with Engility Corporation (reference solicitation Section A narrative in regard to Organization Conflict of Interest).

(e) All solicitation amendments issued, if any.

L.4.3.2 Additional information for Volume 3:

L.4.3.2.1 The proposal shall be valid for a period of not less than 180 days from the required submission date. The Offeror’s proposal validity period shall be clearly stated in Volume 3.

L.4.3.2.2 The Offeror shall provide any certification/corporate agreements with participating commercial firms.

L.4.3.2.3 The Offeror shall provide letters of commitment between the prime and its major subcontractors, as well as joint venture agreements if the prime is a joint venture.

L.4.3.3 Any contractor (or member of its team and/or subcontractor) having a Conflict of Interest, as defined under FAR Part 9.5, must identify the conflict as soon as it is known and provide a recommended mitigation plan. For any potential conflicts of interest known by the Offeror at the time of proposal submission, a mitigation plan shall be submitted in Volume 3 (no page limit).

L.4.3.3.1 Offerors are advised that employees of the firm identified below may serve as non-government advisors in the source selection 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. This firm is expressly prohibited from competing on the subject acquisition.

Engility Corporation 35 New England Business Center Dr Ste #200 Andover, MA 01810-1071 Cage Code: 4A457

In accomplishing their duties related to the source selection process, the aforementioned firm may require access to proprietary information contained in an Offeror's proposal. The identified support contractors will be required to protect an Offeror's information from unauthorized use or disclosure for as long as it remains proprietary and refrain from using the information for any purpose other than that for which it was furnished.

All contractor personnel included in the source selection organization are required to sign a Nondisclosure Agreement (NDA), Conflicts of Interest, and Rules of Conduct Certificates. The agreement requires the participating individuals to protect source selection and proprietary information IAW the Procurement Integrity Act.

IAW FAR 9.505-4(b), each Offeror shall enter into written agreements with Engility Corporation to permit disclosure of the Offeror's proposals to the identified support contractors for the purpose of proposal evaluation. Copies of the executed agreements shall be provided in Volume 3 of the Offeror's proposal.