DRAFT_-_AIT-6_Section_L_-_DRAFT-_POSTED.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 on behalf of the Offeror to enter into a contract based on the submitted proposal. An Offeror’s proposal shall be written in English language and conform to the solicitation instructions. The proposal shall be valid for a period of not less than 120 days from the required submission date. The validity period of the proposal shall be clearly stated in Volume 4 – Solicitation, Offer and Award Documents and Certifications/ Representations.

L.2. PROPOSAL PREPARATION & ORGANIZATION.

L.2.1. INTRODUCTION

L.2.1.1. IAW Federal Acquisition Regulation (FAR) clause 52.215-1, Instructions to Offerors – Competitive Acquisition (Jan 2004), the Government reserves the right to award without discussions with Offerors. Offerors are encouraged to examine solicitation in its entirety and to ensure that its proposal contains all necessary information, provides all required documentation, and the Offeror’s best terms from a price and technical standpoint. The Government reserves the right to conduct discussions and to permit Offerors to submit revised proposals, if deemed necessary by the PCO.

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 Offeror’s proposal shall consist of four volumes as outlined below:

(a) Volume (Vol.) 1 – Price

(b) Vol. 2 – Technical/Management

(c) Vol. 3 – Past Performance

(d) Vol. 4 – Solicitation, Offer and Award Document (Form SF33) and

Certifications/Representations

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

L.2.1.2. Proposals shall be submitted electronically via email to Julie Lawrence, Procuring Contracting Officer (PCO), at Julie.l.lawrence.civ@mail.mil and Luke Welling, Contract Specialist, at luke.m.welling.civ@mail.mil.

D R A F T mailto:Julie.l.lawrence.civ@mail.mil

The Government can only accept individual emails up to 10 MB in size. If the Offeror’s proposal is larger than 10 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.3. Late Submissions.

An Offeror’s proposal, modification(s), revision(s), or withdrawal will be IAW FAR 52.215-1. Reference FAR 52.215-1(c), 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.4. Communications

L.2.1.4.1. Formal Communications.

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

L.2.1.4.2. Solicitation Amendment.

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

L.2.1.4.3. Solicitation Questions.

All questions pertaining to solicitation shall be addressed to the PCO, Julie Lawrence at julie.l.lawrence.civ@mail.mil and to the Contract Specialist, Luke Welling, at luke.m.welling.civ@mail.mil, and shall be submitted not later than the date indicated on Standard Form 33 (SF33). 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.

L.2.1.4.4. 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

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.

http://fbo.gov/ http://www.fbo.gov/

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

L.2.1.4.6. The Acquisition Source Selection Interactive Support Tool (ASSIST) is the workflow tool that will be used during the Source Selection evaluation process.

L. 2.1.4.7. 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 and low price proposals are evaluated before evaluating the total number of received proposals. Any Offeror eliminated from further consideration, to include proposals not technically evaluated, will be notified officially in writing. The Government may enter into discussions with any Offeror who submits a proposal.

All exchanges (clarifications, communications and discussions) with Offerors are accomplished through the release of Evaluation Notices (ENs). The Army will issue written ENs as part of the exchange. ENs will be issued via ASSIST; however, the Government reserves the right to obtain clarifications; have communications; and/or hold discussions with Offerors outside ASSIST if it is determined to be in the best interest of the Government.

L.2.1.4.8. If discussions are conducted, the Government may use ASSIST to facilitate discussions. ASSIST will allow Offeror(s) to receive and respond to ENs securely on-line.

Definitions are as follows:

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

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

Communications: When award with discussions is contemplated – prior to award.

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.2.1.4.9. A separate tool, the ASSIST2Industry, will be used in conjunction with ASSIST to accomplish all communications with Offerors after receipt of proposals pursuant to Federal Acquisition Regulation (FAR) 12. ASSIST2Industry provides the ability for the Government to issue, and the Offerors to receive and respond to, all ENs in a secure online environment.

In order to initiate the use of ASSIST2Industry, the Government requires the names, company titles, telephone numbers, and email addresses of two (2) individuals that the Offeror has designated as responsible for receiving and responding to Government ENs through ASSIST2Industry. The designation of two (2) individuals is for the purpose of insuring availability of one individual if the other individual is not available. The required information regarding these two (2) individuals must be in the cover letter submitted with Vol. 4 of the Offeror's proposal. The cover letter will not be evaluated.

L.2.1.4.10. After the solicitation’s closing date, the Government will establish an account in ASSIST2Industry for each individual identified by the Offeror that has submitted a proposal in response to the Automatic Identification Technology-6 (AIT-6) solicitation.

The two individuals named by the Offeror will be authorized access to that account. Two

(2) separate system generated emails will be sent to each individual. One of the emails will contain the individual's ASSIST2Industry username. The other email will contain the individual's temporary password. Using the provided username and temporary password, each individual can then go to https://ASSIST2Industry.army.mil to access the account. NOTE: The first time a user logs in, the user will be required to change the temporary password before the user can proceed to use the site.

L.3. PROPOSAL FILES.

L.3.1. Format.

L.3.1.1. The proposal submission shall be clearly indexed, logically assembled and comply with the instructions contained herein Section L. Each proposal volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer. A Table of Contents (TOC) shall be created using the TOC feature in MS Word. The title page and table of contents are excluded from the page limitations specified in Table 1.1. 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)

The Government will upload the electronic version of the Offeror’s proposal into ASSIST. Members of the Source Selection Team will use the proposal version in ASSIST to conduct evaluations. The Government reserves the right to adjust the electronic version of an Offeror’s proposal to conform to the guidelines listed throughout paragraph L.3.1. Subsequently, information that exceeds the page counts will be disregarded and not evaluated.

D R https://assist2industry.army.mil/

L.3.1.2. The following additional format restrictions apply:

(a) Paragraphs shall be separated by at least one blank line.

(b) A standard, 12-point minimum font size applies.

(c) Arial font is required.

(d) Tables and illustrations may use a reduced font size not less than 10-point and may be landscape.

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

(f) Tables, charts, figures, etc. should be used for tabular type data and not be used to capture narratives. Narratives are more appropriately placed in the body of the proposal.

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

(h) Offerors shall ensure that the print for the entire proposal is easily readable without magnification. If it is unreadable, it will not be included as part of the evaluation.

L.3.1.3. Digital files shall be compatible with Microsoft (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.1.4. 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.1.5. “Foldouts” (pages larger than 8 ½” x 11”, but not greater than 11” x 17”), if needed for clarification, may be included within the volumes and will not be included in the page counts. Foldouts shall not exceed five per volume. Any foldouts exceeding page limit will not be considered. Foldouts (i.e., diagrams, charts, graphs) shall not be used as a substitute for narrative text.

L.3.2. File Packaging.

L.3.2.1. To be considered for selection, the Offeror must submit a complete response to the AIT-6 solicitation using the sequence and format instructions provided. The proposal shall be divided into separate volumes as specified below in Table 1.1.

L.3.2.2 Table 1.1

Volume No. / Title File Name Maximum

# of Pages Vol. 1 / Price Proposal V-1 As required.* Vol. 2 / Technical/Management V-2 50

• Hardware Narrative, to include Hardware Table V-2-1 See L.5.2

• Hardware Technical Data Sheets V-2-2 See L.5.2

• Software Narrative, to include Software Table V-2-3 See L.5.2

• Software Technical Data Sheets V-2-4 See L.5.2

• AIT-6 System Requirement, Security Requirements and

Turn Key Solutions Methodology Process Narrative V-2-5 See L.5.2

• Bill of Material BOM V-2-6 See L.5.2

• Technical Proposal Matrix V-2-7 See L.5.2

• Graphical Technical Interface Diagrams V-2-8 See L.5.2 Vol. 3 / Past Performance V-3 As required.*

• Attachment 1 – Questionnaires V-3-1

• Attachment 2 – Subcontractor Consent Letters V-3-1 Vol. 4 / Solicitation, Offer and Award Document and Certifications / Representations

V-4 As required.*

• Solicitation Amendments (if applicable) V-4-1

* No set page count for Vols. 1, 3 and 4.

L.3.2.3. Page Count Exceptions: The following are excluded from respective volume’s page count limitation:

(a) Vol. 2 – Technical/Management: Tables of Contents, Hardware Table, Software Table, CLIN Content List, Technical Proposal Matrix, Graphical Technical Interface Diagrams, and Technical Data Sheets

L.3.4. PAGE COUNT. Those pages that exceed the page counts outlined for each volume will not be evaluated unless otherwise exempted.

L.4. PROPOSAL CONTENT

L.4.1. GENERAL

Each Offeror is required to submit all four proposal volumes as outlined below.

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.4.2. WRITTEN PROPOSAL PREPARATION & ORGANIZATION

L.4.2.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 (Example: price/cost information shall only appear in Vol. 1). The Government will only evaluate the information contained in each volume separately and therefore, each volume must stand on its own. 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. Offerors should confine proposal submissions to essential matters, sufficient to define the proposal and to provide an adequate basis for evaluation. 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 or performance. Unsupported statements to comply with the contractual requirements will not be adequate. Offerors shall provide information by addressing the Factor in the format and sequence identified in the Solicitation.

L.4.2.2. No classified material shall appear anywhere within the proposal.

L.4.2.3. No price information shall be presented in any part of the proposal except Volume 1 (Price) and only IAW the criteria established within that volume.

L.4.2.4. Each volume shall consist of a title page, a table of contents, and a body.

The title page shall contain the title of the volume, name of the Offeror, and date of submission.

L.4.2.5. The Table of Contents shall include references to the proposal page number and paragraph of all major items.

L.4.2.6. Consecutive page numbering within each volume is required.

Paragraphs shall be numbered and titled.

L.5. VOLUMES:

L.5.1. VOLUME 1 – PRICE PROPOSAL

L.5.1.1. The Price Model (Section J, Attachment 0003), 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. Each CLIN and SLIN includes a thorough and detailed description identifying all components and parts that are included with the line item.

L.5.1.2. The Offeror is not to add any CLIN/SLINs without permission of the PCO.

L.5.1.2.1. The Offeror shall NOT provide a separate “Price Notes” page for any written explanation of the prices. Any written explanation of proposed price(s) may be construed as a disqualification and be cause for rejection of the proposal. Making assumptions to the pricing volume or pricing model will be considered as exceptions to requirements, which will make the offeror non-responsive.

L.5.1.3. All prices shall be whole numbers. The Offeror's proposal may be rejected if the proposed prices provided are not whole numbers.

L.5.1.4 The completed Price Model (Section J, Attachment 0003) will become the Offeror’s Volume 1, Price proposal; therefore, a page limit is not applicable for this volume.

L.5.1.5. The proposed pricing for the incidental material, expedited delivery, and travel is Non-Fee bearing.

L.5.1.6. Instructions for completion of the Pricing Model:

a. All information to be filled in by the Offeror is highlighted/annotated in blue on the Pricing Model.

b. The Offeror shall enter its full name in the space provided.

c. Offerors are required to state binding prices.

d. No other information is to be added to the Price Model nor shall Offerors make any changes to the Price Model.

L.5.2. VOLUME 2 – TECHNICAL/MANAGEMENT

Limited to fifty (50) pages. Tables of Contents, Hardware Table, Software Table, Bill of Material (BOM), Technical Proposal Matrix, Graphical Technical Interface Diagrams, and Technical Data Sheets are NOT included in the page count. No executive summary is required for the Technical/Management Volume.

The Technical approach shall demonstrate the Offeror’s technical capability and understanding of the requirement. The Offeror must demonstrate the ability to provide 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.5.2.1. Hardware. The Offeror shall produce a hardware table that replicates all of the requirements for AIT-6 PWS Section 4 (see example #1 below) and indicate if the requirement has been met. Using a narrative the Offeror may inform the Government of any other relevant or significant conditions with regard to the requirements.

Example #1:

Hardware Requirement Met

4.3.4 STATIONARY BAR CODE LABEL PRINTER. Yes/No

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

Yes/No

b. , USB, and Ethernet communications ports; Yes/No

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

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

L.5.2.2. Software. The Offeror shall produce a software table that replicates all of the requirements for AIT-6 PWS Section 5 (see example#2 below) and indicate if the requirement has been met. Using a narrative, the Offeror may inform the Government of any other relevant or significant conditions with regard to the requirements.

Example #2:

Software Requirement Met

5.1.2 BAR CODE PRINTING SOFTWARE. Yes/No

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

L.5.2.3. Bill of Material (BOM). Based on the Price Model (Section J, Attachment 0003), the Offeror shall provide a detailed list for all the items proposed, for each hardware and software CLIN (see example #3 below). Each BOM shall correlate to a Price Model CLIN number and CLIN 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 CLIN, i.e., optional equipment. The Offeror shall provide the requested information in the format shown in the example #3 below.

Example #3:

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.5.2.4. Methodology Process for Turnkey Solutions. The Offeror shall provide a narrative describing the methodology used when implementing 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.5.2.5. AIT-6 System Requirements. The Offeror shall provide a narrative illustrating the methodology and process used when implementing the AIT-6 System Requirements as defined by PWS Section 3 (reference Section J, Attachment 0001 “AIT-6”).

L.5.2.6. Security Requirements. The Offeror shall provide a narrative illustrating the methodology process use when implementing the Security Requirements as defined by PWS Section 6 (reference Section J, Attachment 0001 “AIT-6”).

L.5.2.7. Technical Proposal Matrix. As an attachment, the Offeror shall provide a matrix demonstrating compliance to the requirements in the AIT-6 PWS’ Technical Sections 3 and 6 (reference Section J, Attachment 0001 “PWS AIT-6”). Note: The AIT-6 PWS Sections 4 and 5 requirements are provided 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.).

At a minimum the Offer shall include the following information as outlined in example #4.

Example #4:

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.5.2.8. AIT-6 Product Demonstration Requirements. At the discretion of the Government, all Offerors will be required to perform AIT-6 Product Demonstrations as illustrated in "Product Demonstration Requirements" (Section J, Attachment 0002 “Product Demonstration Requirements”), of solicitation (Note:

paragraph L. 2.1.4.7). 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.5.2.9. Graphical Technical Diagrams. The Offer shall provide graphical technical diagrams for the following CLINs: 0001DA (wireless and batch modes), 0001EA (wireless and batch modes), and 0011AA. The diagrams shall provide graphical depictions of any components that are required to for the product to function (e.g., cables, adaptors, etc.).

L.5.3. VOLUME 3 – PAST PERFORMANCE

The Past Performance Factor, as used for evaluation, will assess the Government’s confidence an Offeror will successfully perform to the solicitation requirements based on an Offeror’s record of recent and relevant contract performance. A reference coversheet sheet shall be included for each proposed Past Performance Reference (example format is provided as enclosure).

L.5.3.1 Contract References: The Offeror shall submit, with its initial proposal, no more than three (3) contract references representing its recent and relevant performance under Government (Federal, state, local) and/or commercial contracts.

L.5.3.1.1 Recent contract references are defined as prime contracts, task orders, delivery orders, or subcontracts where services or deliverables were performed, or still being performed, anytime within three (3) years of issuance of the AIT-6 solicitation release date. The Government reserves the right to consider any significant past performance after the solicitation closing date and prior to award.

L.5.3.1.2 Contracts referenced that were recently started and have limited performance provide little value for determining an Offeror's Past Performance. Submission of contract references with limited performance may or may not impact the Offeror(s)’ overall Past Performance acceptability rating; therefore, it is highly recommended that Offerors submit contract references that demonstrate a minimum of six (6) months performance.

L.5.3.1.3 For the AIT-6 solicitation, Relevant means performance that demonstrates the Offeror has performed work on Recent contracts that have an average annual dollar value of more than $100,000.00 that encompasses the same or similar scope of effort as the AIT-6 solicitation hardware, software, and work-related services. Examples of relevant AIT-6 scope include, but are not limited to the following:

(1) Commercial equipment provided,

(2) Integrated with automated information systems,

(3) Software and middleware provided,

(4) Incidental services (training, warranty, maintenance, technical engineering).

L.5.3.2 The following information is required with respect to each contract reference:

(a) Contract Number/Order Number (include specific task/delivery order number in the case of Indefinite Delivery/Definite Quantity, General Service Association, or Blanket Purchase Agreement type contracts)

(b) Commercial And Government Entity Code (CAGE Code)

(c) Dun & Bradstreet D-U-N-S Number (DUNS)

(d) Narrative description of the Hardware/Software (Supply) and/or Service(s) or deliverables provided under the contract reference to include a description of the contract’s relevance to the current procurement,

(e) Contract Type (fixed price, cost reimbursable, time and materials, etc.),

(f) Identify if reference represents Offeror’s performance as a Prime Contractor or

Subcontractor,

(g) Award date, period of performance, and completion of contract performance date,

(h) Contract award value, annual value, current value, and final projected value,

(i) Identify if reference is predominately Hardware (Supply) or Service related,

(j) Contract Performance Location

(k) Identify Proposal Sections where evaluators can find Offeror’s experience in the following items: Commercial Equipment, Software and Middleware, Incidental Services (to include training, warranty, maintenance, technical, and engineering). Additional hardware, software, and services can be added as necessary.

L.5.3.3 For each contract reference, Offeror is to provide a separate "Past Performance Questionnaire" (reference Section J, Attachment 0004). Only PPQ sections titled “Section A. Contract Identification” and “Section B. Identification of Offeror’s Representative” are to be completed by the Offeror. Ensure point of contact information is current and accurate. The remaining information on the PPQ will be completed by the questionnaire respondent. The Government at its discretion will decide whether a reference(s) is interviewed.

L.5.3.4 For work Offeror performed as a subcontractor; the PPQ shall include the base (prime) contract/order number, name of the prime contractor (CAGE and DUNS numbers), prime contractor organization point of contact(s) information to include name, job title, current address, e-mail address, and telephone number.

L.5.3.5 For work Offeror performed as a prime contractor; the PPQ shall include the customer and mailing address, point of contact(s), including job titles, telephone number, and e-mail addresses.

L.5.3.6 For work Offeror performed under Government contracts, provide the contracting activity name, address, PCO’s and/or the Administrative Contracting Officer's name, e-mail address, and telephone numbers to include the Government Technical Representative/Contracting Officer Representative (COR), and current e-mail address, and telephone numbers.

L.5.3.7 ADVERSE GOVERNMENT CONTRACT PERFORMANCE – In addition to the above contract references, the Offeror shall identify every recent and relevant Government contract(s) it was awarded that experienced any adverse performance problems related to deliverables or services; and every recent contract that was terminated (except those contracts terminated for the convenience of the Government), in whole or in part within the past three (3) years of the AIT-6 solicitation release date.

The number of contract references provided in response to this paragraph (“Adverse Government Contract Performance”) is unlimited. If there are no contracts meeting the adverse performance description above, the Offeror must state as such.

For any contract falling under the adverse performance descriptions above, provide all of the information listed in the preceding paragraph, plus:

(a) Provide a copy of any cure notices or show cause letters received,

(b) Provide a copy of any Contract Deficiency Report (CDR),

(c) Identify the reason for the termination (except those contracts terminated for the convenience of the Government),

(d) State any corrective actions taken to avoid recurrence,

(e) Describe the extent to which the corrective action has been successful, identifying points of contact who can confirm the success of the corrective measures, and

(g) Describe in detail any performance problems that include internal/external customer complaints and/or CDRs. Failure to include this information may result in a lower past performance rating.

L.5.3.8 New Corporate Entities – An Offeror that is a new corporate entity may submit data on prior contracts involving its officers and employees; however, in addition to the other requirements in this section, the Offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information shall be included as described in this section.

L.5.3.9 The Government reserves the right to use data provided in the Offeror's proposal and data obtained from other Government sources such as the Past Performance Information Retrieval System (PPIRS) to assess the Offeror’s Past Performance Acceptability Rating.

NOTE: It is recommended that Offerors limit references to those involving its performance as a prime or first tier subcontractor unless it cannot otherwise be avoided.

L.5.4. VOLUME 4 – SOLICITATION, OFFER AND AWARD (Form SF33)

DOCUMENT AND CERTIFICATIONS/REPRESENTATIONS

L.5.4.1 Certifications and Representations: 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 original signature. An Acrobat PDF file shall be created to capture the signatures for submission. The format specified in paragraph L.3.1.1 does not apply to Vol. 4. Offerors shall complete the following:

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

(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. Also include in this section your 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.

Additional information for Volume 4:

(a) The Offeror shall provide any certification/corporate agreements with participating commercial firms.

(b) 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.5.4.2. 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 4, the Solicitation, Offer and Award Document and Certifications/ Representations volume (no page limit).

Enclosure:

AIT-6 Past Performance Reference Summary Sheet D R A F

T

ENCLOSURE

AIT-6: Past Performance Reference Cover Sheet

Contract Number

Delivery/Task Order Number (if applicable)

Cage Code Duns

Type of Hardware/Software provided

Contract Type (i.e.

fixed price, cost, etc)

Reference represents contractor performance as a Prime Subcontractor

Award Date

Period of Performance Dates

Completion of Contract Performance Date

Contract Award Value Annual Value

Current Value Final Projected

Value

Work effort for this reference is predominately for Services Hardware Software

Performance Location

Proposal Section 1 Commercial Equipment Provided 2 Integrated with Automated Information Systems 3 Software and middleware provided 4 Incidental services (training, warranty, maintenance, technical engineering).

5 (use additional line items, if applicable) 6 (use additional line items, if applicable) 7 (use additional line items, if applicable) 8 (use additional line items, if applicable)

L.2.1.4.6. The Acquisition Source Selection Interactive Support Tool (ASSIST) is the workflow tool that will be used during the Source Selection evaluation process.