W52P1J-16-R-0139-0004.pdf

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

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

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

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

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

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

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

12. Accounting And Appropriation Data (If required)

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

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

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

The Contract/Order No. In Item 10A.

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

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

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

D. Other (Specify type of modification and authority)

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

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

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

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

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

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

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

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

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

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

0004 2016AUG31

W52P1J

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

BLDGS 60 & 62

TIMOTHY W. VOLKERT

EMAIL: TIMOTHY.W.VOLKERT.CIV@MAIL.MIL

W52P1J-16-R-0139

2016AUG02

X

X 2016SEP06 08:00am

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 16

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: TIMOTHY W. VOLKERT

Buyer Office Symbol/Telephone Number: CCRC-IT/(309)782-1956

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

The purpose of Amendment 0004 to solicitation W52P1J-16-R-0139 is to extend the proposal closing date and time.

1. The pRFID III solicitaiton proposals closing date and time are extended as listed below:

From

2 September 2016, 3 p.m. Central Time

To

6 September 2016, 8 a.m. Central Time

2. All other terms and conditions of the solicitation are unchanged.

*** END OF NARRATIVE A0005 ***

2 16

W52P1J-16-R-0139 0004

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 AMENDMENTS TO SOLICITATIONS

If this solicitation is amended, all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this solicitation by the date and time specified in the amendment(s). If there are any conflicts between FAR 52.212-1 and instructions stated elsewhere in this solicitation, the instructions shall supersede FAR 52.212-1.

L.2 SUBMISSION, MODIFICATION, REVISION, AND WITHDRAWAL OF PROPOSALS

(1) Proposals and modifications to proposals shall be submitted via E-mail.

(i) Addressed to Contract Specialist Mr. Tim Volkert at timothy.w.volkert.civ@mail.mil with a Carbon Copy (CC) to Contracting Officer, Amanda Struve at amanda.k.struve.civ@mail.mil; and

(ii) Offerors shall identify in the e-mail subject line the RFP number, closing date/time, content, and the offeror's name. For example: W52P1J-16-R-0139, day/time/content, Message 1 of 5, XYZ Company.

(iii) In the body of each e-mail message of the proposal, the Offeror shall provide a brief statement accounting for each e-mail in relation to the entire RFP; e.g., Message 3 of 5, as well as an inventory of attachments, e.g., Attachment 1 of 4. For example, This is message 3 of a total of 5 messages constituting the delivery order proposal of XYZ Company. This message provides attachments 2 and 3 of a total of 6 attachments to our complete Delivery Order Proposal.

(2) The first page of the proposal must show -

(i) The solicitation number W52P1J-16-R-0139;

(ii) The name, address, telephone number and electronic address;

(iii) A statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation and agreement to furnish any or all items upon which prices are offered at the price set opposite each item;

(iv) Names, titles, telephone numbers and electronic addresses of persons authorized to negotiate on the offerors behalf with the

Government in connection with this solicitation; and

(v) Name, title, and signature of person authorized to sign the proposal. Proposals signed by an agent shall be accompanied by evidence of that agents authority, unless that evidence has been previously furnished to the issuing office.

(3) Submission, modification, revision, and withdrawal of proposals.

(i) Offerors are responsible for submitting proposals, and any modification, or revisions, so as to reach the Government office designated in the solicitation by 6 September 2016, 8 a.m. Central Time.

(ii) Offerors are cautioned that e-mail is not instantaneous. We recommend you submit your proposal prior to the closing date, allowing enough time to ensure the entire proposal is received on time to be considered for award. If all portions of any e-mail proposal are not received by the RFP closing deadline, the proposal shall be rejected as late. Offerors are responsible for confirming with the Procuring Contracting Officer and/or Contract Specialist to ensure that the proposal submitted has been received by the

Government. This must be done by the date/time set in the solicitation for receipt of offers.

(iii) Due to government exchange size limitations, we cannot receive individual e-mails that exceed 20 MB, including the e-mail itself plus all attachments. If your electronic proposal, including all attachments, is larger than 20 MB, you shall segment your proposal into a series of two (2) or more separate e-mails that individually are no larger than 20 MB. We cannot receive e-mails if they contain compressed attachments. Our security software blocks these types of e-mails.

(4) Offerors shall submit proposals in response to this solicitation in English and in U.S. dollars.

(5) Offerors may submit modifications to their proposals at any time before the solicitation closing date and time, and may submit modifications in response to an amendment, or to correct a mistake at any time before award.

(6) Offerors may submit revised proposals only if requested or allowed by the Contracting Officer.

L.3 OFFER EXPIRATION DATE

Proposals in response to this solicitation will be valid for 120 days.

3 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.4 CONTRACT AWARD

The Government intends to award a single, decentralized, IDIQ contract resulting from this solicitation to the responsible offeror whose proposal represents the best value after evaluation in accordance with the factors in the solicitation.

The Government may reject any or all proposals if such action is in the Governments interest.

The Government intends to evaluate proposals and award a contract without discussions with offerors. Therefore, the offerors initial proposal should contain the offerors best terms from a cost or price and technical standpoint.

The Government reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary. If the

Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

The Government reserves the right to make multiple awards if, after considering the additional administrative costs, it is in the

Governments best interest to do so. Exchanges with offerors after receipt of a proposal do not constitute a rejection or counteroffer by the Government.

L.5 PROPOSAL INSTRUCTIONS - GENERAL

(1) No classified information shall be included in this solicitation and the use of hyperlinks in proposals is prohibited. If classified material is received it will not be reviewed and the proposal will be removed from the competition.

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

(3) Solicitation Questions/Comments. Questions or comments regarding this solicitation shall be submitted to Tim Volkert, at timothy.w.volkert.civ@mail.mil and the Contracting Officer, Amanda Struve at amanda.k.struve.civ@mail.mil. All questions on the RFP must be submitted no later than ten (10) calendar days after release of the RFP. Questions submitted after this date may not be answered and may not be a basis for amending this Solicitation. Responses, if appropriate, will be posted to the FedBizOpps.

Offerors are advised to continuously monitor the FEDBIZOPPS website for new information. The Offerors are deemed to have knowledge of all documents that are posted to FEDBIZOPPS.

(4) The Government will not reimburse Offerors for incurred costs associated with the preparation of proposals.

(5) Submission of proposals shall be one electronic copy. Proposals shall be structured in six separate volumes as follows:

Volume 1 - Technical

Volume 2 - Management

Volume 3 - Past Performance

Volume 4 - Price

Volume 5 - Small Business Participation

Volume 6 Solicitation, Offer and Award Document and Certifications/Representations

(6) The proposal must not merely repeat the solicitation requirements, but rather must provide the documentary evidence in support of conclusive statements of how contract requirements will be met.

L.6 ACQUISITION SOURCE SELECTION INTERACTIVE SUPPORT TOOL (ASSIST)

(1) The ASSIST Tool is the workflow tool that will be used during the Source Selection evaluation process.

(2) The Army may issue Evaluation Notices (ENs) for this procurement via ASSIST. If discussions are conducted with Offeror(s) in the competitive range, the Government intends to use ASSIST to conduct discussions. ASSIST will allow Offeror(s) to receive and respond to

ENs securely on-line. ENs may be in the form of weaknesses, significant weaknesses, uncertainties, or deficiencies. Definitions are as follows:

(i) Deficiency: A deficiency is a material failure of the proposal to meet a Government requirement or a combination of significant weaknesses in a proposal that increases the risk of unsuccessful contract performance to an unacceptable level.

(ii) Weakness: A weakness means a flaw in the proposal that increases the risk of unsuccessful contract performance.

(iii) Significant Weakness: A significant weakness in the proposal is a flaw that appreciably increases the risk of unsuccessful

4 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

contract performance.

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

(v) Clarifications: Clarifications are limited exchanges between the Government and the Offerors that may occur when award without discussions in contemplated.

(vi) 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 or mistake).

(3) A separate tool, the ASSIST2Industry, will be used in conjunction with ASSIST to accomplish all exchanges with Offerors after receipt of proposals pursuant to Federal Acquisition Regulation (FAR) 15.306. ASSIST2Industry provides the ability for the Government to issue, and the Offerors to receive and respond to, all Evaluation Notices (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 submitted with the Offeror's proposal and included in the cover letter.

(4) After the solicitations 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 this solicitation. The two (2) 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.

(5) Whenever the Government issues ENs to the Offeror through ASSIST2Industry, the Government's Contracting Officer will notify the

Offeror through a medium independent of ASSIST2Industry (e.g., e-mail) that the Offeror has ENs in ASSIST2Industry waiting for a response. There will be no ENs in ASSIST2Industry until such notice is issued by the Contracting Officer. Offerors can contact the

ASSIST2Industry helpdesk at (609) 562-7050 or (609) 562-7031 for any technical assistance that may be needed.

THE OFFERORS ARE CAUTIONED THAT THE SYSTEM GENERATED EMAILS REFERRED TO ABOVE ARE INTENDED FOR ADMINISTRATIVE PURPOSES ONLY. RECEIPT OF

THESE EMAILS DOES NOT CONSTITUTE THE COMMENCEMENT OF ANY TYPE OF EXCHANGE WITH THE OFFEROR IN ACCORDANCE WITH FAR 15.306(A), (B), OR (D)

(I.E., CLARIFICATIONS, COMMUNICATIONS, OR DISCUSSIONS). ALSO, RECEIPT OF THESE EMAILS DOES NOT SIGNIFY THAT A COMPETITIVE RANGE

DETERMINATION IN ACCORDANCE WITH FAR 15.306(C) HAS BEEN MADE OR THAT THE OFFEROR'S PROPOSAL WILL BE INCLUDED IN THE COMPETITIVE RANGE

IF/WHEN THAT DETERMINATION IS MADE. ALL NOTIFICATIONS THAT ANY TYPE OF EXCHANGE WITH THE OFFEROR HAS COMMENCED AND THE OFFEROR HAS

EVALUATION NOTICES (ENs) AVAILABLE TO RESPOND TO, OR ANY NOTIFICATION THAT THE OFFEROR'S PROPOSAL HAS BEEN INCLUDED IN OR EXCLUDED FROM

THE COMPETITIVE RANGE, WILL BE SENT TO THE OFFEROR BY THE CONTRACTING OFFICER INDEPENDENTLY OF THE ASSIST2INDUSTRY.

(6) Offerors may be receiving EN questions on-line if they remain in the competitive range and the Government decides to conduct discussions.

(7) Evaluation Notice (EN) Response. Responses to ENs and any resulting proposal revisions must be provided in accordance with the following instructions:

A complete response must be provided within the EN response, including an explanation of any revisions to Offeror's proposal. Please do not simply provide a reference to revisions in the Offeror's proposal. If a response to an EN requires a revision to Offeror's proposal, identify a reference in your response(s) to the location (e.g., Volume #, Section #, paragraph #, etc.) of the revision in the

Offeror's proposal. NOTE: To be considered and evaluated as part of the Offeror's proposal, the changes should be made in the Offeror's proposal submission and the Offeror must conform to the page format/limitation requirements.

Attach the complete resubmission file containing the proposal revisions for each volume as Attached Files with Offeror's reply in the last EN for the respective volume (i.e. one attached file per volume, same file structure as in initially submitted). Do not submit change pages or multiple copies of Offeror's revised proposal. Offerors are requested to limit changes to items identified in the EN.

For clarity purposes, Offerors are required to clearly identify the corresponding changes/additions in Offeror's proposal (e.g. use track changes to show date, vertical line in margin, bold, and/or underline by using the redline and strikeout features).

Each revision on each revised page shall be identified by date (DD/MM/YY) and by revision number, which shall be done by adding a footer to indicate such revision (i.e., date of submission of the revision) for each file affected. Offerors shall also place their names within the header or footer of each page along with the section number.

(8) After all ENs have been issued and responses submitted, and, when instructed by the Contracting Officer, Offerors shall submit

Final Proposal Revisions (FPRs) as specified in the Final Proposal Revision letter.

5 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(9) The Government will upload the electronic version of the Offeror's proposal into the ASSIST tool. Members of the Source Selection

Team will use the version in the ASSIST tool to conduct their evaluations. The Government reserves the right to adjust the electronic version of an Offeror's proposal to conform to the guidelines listed throughout the Proposal Instructions in this section. Those pages that exceed the page count for any volume may be removed and not considered.

(10) Offeror(s) are required to provide two (2) company individuals whose responsibilities will include reading and responding to ENs through ASSIST. For example, the Offeror's Contract Manager, as an agent of the company might be the main agent responsible, but a second agent should be available in case of the main agent's unavailability. The two (2) agents' names, company titles, telephone numbers, facsimile numbers, and e-mail addresses should be provided. This required information is to be submitted with proposals and included in the cover letter for Authorized Offeror Representatives. In order to access ASSIST, these individuals will need an

Interactive Business Opportunities Page username and password. Once the company representatives are provided access to ASSIST, your company will be informed of the specific website where your agent(s) will receive and respond to the ENs. Offerors are cautioned that receipt of the website does NOT constitute official notice that a competitive range determination has been made and that a particular

Offeror remains in the competitive range. The intent of this section is to advise Offeror(s) that they may be receiving EN questions on-line if they remain in the competitive range and the Government decides to conduct discussions.

L.7 PROPOSAL FILES

(1) Format. The submission shall be clearly indexed, logically assembled and comply with the instructions contained in this section.

Each 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 Microsoft (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, Width 8.5

Page Size, Height 11

The Government will upload the electronic version of the Offeror's proposal into the ASSIST tool. Members of the Source Selection Team will use the version in the ASSIST tool to conduct their 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.

The following additional restrictions apply:

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

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

(iii) Arial or Times New Roman fonts are required.

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

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

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

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

(viii) 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.

Digital files shall be compatible with Microsoft (MS) Office 2007. Each Offeror shall add its respective company name to the file names listed in Table 1.1, i.e., Company Name V1A1.docx.

MS Excel worksheets are considered one page each for page count purposes. MS Project Gantt/Program Evaluation and Review Technique

(PERT) charts are excluded from the page count restrictions.

Foldouts (pages larger than 8.5 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 this limit will not be

6 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

considered. Foldouts (i.e., diagrams, charts, graphs) shall not be used as a substitute for narrative text.

(2) To be considered for selection, the Offeror must submit a complete response to this solicitation using the sequence and format instructions provided in this section. The proposal shall be divided into separate volumes and provided with the number of copies specified below in Table 1.1.

Table 1.1

Volume No./Title | File | Maximum #

| Name | of Pages

Vol. 1 / Technical | V-1 | 40

Hardware Narrative, to include Hardware Table | V-1-1 |

Hardware Technical Data Sheets | V-1-2 | Not included

| | in page limit

Software Narrative to include Software Table | V-1-3 |

Software Technical Data Sheets | V-1-4 | Not included

| | in page limit pRFID Equipment Requirements, and Turn Key | V-1-5 |

Solutions Methodology Process Narrative | |

Technical Proposal Matrix | V-1-7 |

Vol. 2 / Management | V-2 | 40

Management Support Plan, Corporate Resources, | V-2-1 |

Management, Technical Engineering Services | |

Managements, Customer Support, Warranty, | |

Configuration Management, and Risk | |

Management narrative | |

Key Personnel Resumes and Management | V-2-2 |

Proposal Matrix | |

Vol. 3 / Past Performance | V-3 | As Required

Attachment 1 - Past Performance Questionnaire | |

Vol. 4 / Price | V-4 | As Required

Vol. 5 / Small Business Participation | V-5 | As Required

Contract Participation Matrix | V-V-5-1 |

Past Small Business Participation | V-5-2 |

Small Business Subcontracting Plan | V-5-3 |

(if applicable) | |

Vol. 6 Certification/ Representations | V-6 | As Required

Solicitation Amendments (if applicable) | V-6-1 |

*No set page count for Vo. 3, 4, 5, and 6.

(3) Page Count Exceptions: The following are excluded from their respective volumes page count limitation:

(i) Volume 1 - Technical: Tables of Contents, Hardware Table, Software Table, CLIN Content List, Technical Proposal Matrix and

Technical Data Sheets.

7 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(ii) Volume 2 - Management: Tables of Contents, Key Personnel Resumes, and the Management Proposal Matrix.

(4) Page Count. Those pages that exceed the page counts in Table 1.1 for each volume will not be evaluated unless otherwise exempted.

L.8 PROPOSAL CONTENT

Each Offeror is required to submit the Technical, Management, Past Performance, Price, and Small Business Participation proposals as outlined below.

The Offeror shall be held responsible for the validity of all information supplied in their 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.

(1) Written Proposal Preparation & Organization. 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. (For example, price/cost information shall only appear in Volumes 4 and 5 as required per the criteria established within each volume.)

(2) The Government will only evaluate the information contained in each volume separately and therefore, each volume must stand on its own.

(3) 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.

(4) Offerors should confine their submissions to essential matters, sufficient to define the proposal and to provide an adequate basis for evaluation. 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.

(5) No price information shall be presented in any part of the proposal except Volume 4 (Price) and Volume 5 (Small Business

Participation) and only in accordance with the criteria established within each volume.

(6) 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.

(7) The Table of Contents shall include references to the proposal page number and paragraph of all major items.

(8) Consecutive page numbering within each volume is required. Paragraphs shall be numbered and titled.

L.9 VOLUMES

(1) VOLUME 1 - TECHNICAL

Limited to forty (40) pages. Tables of Contents, Hardware Table, Software Table, Technical Proposal Matrix and Technical Data Sheets are NOT included in the page count. No executive summary is required for the Technical Volume. The Technical approach shall demonstrate the Offeror's technical capability and understanding of the requirements, feasibility of its approach toward performance and meeting requirements, flexibility in adjusting to changes in technical requirements, completeness/adequacy of response, associated risk.

(i) Adequacy of Response. The proposal shall demonstrate a sound and clear understanding of all pRFID III solicitation technical requirements of the products.

(ii) Feasibility of Approach. The technical approach shall demonstrate a sound and workable technical concept that is capable of meeting all of the requirements of the performance work statement. A strong proposal shall demonstrate a high degree of thoroughness, soundness, and comprehension of the requirements indicating a high likelihood of success.

(iii) Hardware. The Offeror must demonstrate the ability to provide hardware identified for AIT equipment maintained for DoD, NATO, and Coalition Partners in dynamic, global AIT environments as stated in the PWS.

A. The Offeror shall fill out the pRFID III Hardware & Software Table (Attachment 0004), which replicates all of the requirements specified in Section 4 of the PWS (see example below) and indicate if the requirement has been Met or Exceeded. The table shall consist of the proposed items 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 shall describe the actual proposed configuration(s) and shall NOT include items that are not included with the CLIN, i.e. optional equipment.

If the Offeror states it has exceeded a hardware requirement, then the Offeror shall provide, in the narrative portion of the proposal, 8 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

a detailed explanation demonstrating how it has exceeded the requirement and what value this provides to the Government. Using the narrative the Offeror may inform the Government of any other relevant or significant conditions with regard to the requirements.

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).

For example:

PWS | Proposed Model/ | Product |Qty| Met or | Exceed

Requirement | Part Number | Description | | Exceed | Narrative

| | | | Requirement?| Location

4.2.4 pRFID | ABC Company | XTC-100ABC w/ | 1 | | Section(s), Hand-Held | XTC-100ABC | QWERTY-Numeric, | | | page(s), Reader | | NI (includes | | | Paragraph(s)

| | pRFID and oper- | | |

| | ational battery | | |

| | [NO Certified] | | |

| [ABC] | Minimum 2 GB | 1 | | Section(s), | (manufacture | SD Memory Card | | | Page(s)

| name) | | | | paragraph(s)

| ABC DK-240 | Desktop Dock for| 1 | | Section(s), | | XTC-100ABC | | | Page(s)

| | Simultaneously | | | Paragraph(s)

| | charges one XTC-| | |

| | 100ABC and two | | |

| | battery packs | | |

| ABC 123-456-002 | Desktop Dock | 1 | | Section(s), | | Power Supply | | | Page(s)

| | | | | Paragraph(s)

| ABC 123-456-004 | Desktop Dock | 1 | | Section(s), | | Power Cord | | | Page(s)

| | | | | Paragraph(s)

B. The Offerors proposal shall demonstrate the operating characteristics (e.g. temperature ranges) for all Hardware (e.g., Fixed

Readers, Vehicle Mount Readers, Hand Held Readers (HHR), Smart Table, Printers, and Tags) in accordance with the solicitation.

(iv) Software. The Offeror must demonstrate the ability to provide software identified for AIT equipment maintained for DoD, NATO, and

Coalition Partners in dynamic, global AIT environments as stated in the PWS.

The Offeror shall shall fill out the pRFID III Hardware & Software Table (Attachment 0004), which addresses all of the requirements specified in Section 5 of the PWS (see example below) and indicate if the requirement has been Met or Exceeded. The table shall consist of the proposed items 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 shall describe the actual proposed configuration(s) and shall NOT include items that are not included with the CLIN, i.e. optional equipment.

If the Offeror states it has exceeded a software requirement, then the Offeror shall provide, in the narrative portion of the proposal, a detailed explanation demonstrating how it has exceeded the requirement and what value this provides to the Government. Using the narrative the Offeror may inform the Government of any other relevant or significant conditions with regard to the requirements.

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

For example:

PWS |CLIN/SLIN |Proposed |Product |QTY|Met or | Exceed

Requirement | |Model |Description | |Exceed | Narrative

| |Part | | |Requirement?| Location

| |Number | | | |

9 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

5.1.1 |SLIN 0025YE| ABC | | 1 | |Section(s), Environment | | Company | | | |Page(s), | | XTC-100ABC | | | |Paragraph(s)

| |[ABC] | | 1 | |Section(s), | |(manufacture| | | |Page(s), | |name) | | | |Paragraph(s)

| |123-456-xxx | | | |

| |(P/N) | | | |

A. The Offeror shall demonstrate all software capabilities associated with the Configuration/Operational Software for PC, Configuration

Software for the HHR, Application Development Software, and the pRFID Enabled Printer Software, required by this solicitation.

B. The Offeror shall demonstrate the ease of use of the proposed software both from an end user and administrator perspective.

C. The Offeror shall demonstrate the desired Application Development Software features, to include: the ability to download executable code to other devices; tools, libraries, and executive software needed to generate executable code; ASCII file import and export capability; and Structured Query Language capability.

D. The Offeror shall illustrate any development and integration capabilities for all submitted software.

E. Technical Engineering Services (TES). The Offeror shall provide a narrative describing the methodology used and processes followed when implementing a pRFID turnkey solution from its initial approach to final solution. The methodology shall include, but is not limited to the Offerors ability to meet changing technical requirements, support multiple configurations, as well as process and procedures for adhering to and implementing the security requirements identified in section 6 of the PWS. The Offeror shall include all assumptions relevant to the utilization of hardware, software, pRFID architecture, and integration with automated information systems.

(v) pRFID Equipment Requirements. The Offeror shall provide a narrative illustrating the methodology process used when implementing new pRFID Equipment Requirements.

(vi) Proposal Matrix. As an attachment, the Offeror shall provide a matrix demonstrating compliance to the requirements in the PWS

(Technical Sections 3, 4, 5, and 6).

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.).

In a separate column titled Value Added, when the Offeror believes it has exceeded a technical requirement, the Offeror will provide a statement explaining the relevance, applicability and value to the Government.

At a minimum the Offer shall include the following information.

PWS Requirement | Offeror's Proposal | Value Added

(Paragraph Number | Sections that address | and Title) | the PWS Requirement |

3.4 BAR CODE | Section(s), Page(s), | Description explaining the

REQUIREMENTS | Paragraph(s) | relevance, applicability and value

| | to the Government

(vii) pRFID III Product Demonstration Requirements.

All Offerors will be required to perform pRFID III product demonstrations as illustrated in Attachment 0006 (pRFID III Product

Demonstration Requirements. Offerors will be notified within four (4) weeks after the proposal due date as to their demonstration date.

All demonstrations will be completed within eight (8) weeks of proposal due date. Upon review of all proposals, should the Government determine there is no need to perform product demonstrations, then at its discretion, the Government may remove the requirement for

Product Demonstrations. This will only be done in the event that the Government determines it has no concerns about the possible achievability of the proposed hardware configurations of meeting the performance requirements as stated in the PWS. Product

Demonstrations will be held in an all or none basis.

(2) VOLUME 2 - MANAGEMENT

Limited to forty (40) pages. Key Personnel Resumes, the Management Proposal Matrix, and Table of Contents are NOT included in the page

10 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

count.

The management approach shall demonstrate a sound and workable management concept that is capable of meeting all of the requirements of the PWS. A strong proposal shall demonstrate a high degree of thoroughness, soundness, and comprehension of the requirements indicating a high likelihood of success.

(i) Adequacy of Response. The proposal shall demonstrate a sound and clear understanding of all pRFID III solicitation management requirements of the products.

(ii) Feasibility of Approach. The management approach shall demonstrate that the proposed approach is workable and the end results are achievable.

A. The proposal shall describe the Offerors methods and approach to meeting management support requirements in a timely manner and will be evaluated to determine the level of confidence provided to the Government with respect to the likelihood of successful performance within schedule without causing disruptions or additional burdens on the government

B. The proposal shall describe how successful performance will be achieved through use of industry standard frameworks, contingent upon proven processes and techniques; and the extent to which the approach identifies the use of quality management programs and metrics, the use of program risk management and mitigation techniques

(iii) Management Support Plan (MSP). The Offeror shall provide a detailed MSP outlining their management approach and understanding of the requirements. The Offeror must demonstrate the necessary management methods to assure that contract oversight shall be maintained for DoD, NATO, and Coalition Partners in dynamic, global pRFID environments and requirements as stated in Section 7.1a of the PWS. The

Offeror may cite specific examples beyond standard project management practice models that are beneficial and specific to DoD, NATO, and

Coalition Partners.

(iv) Corporate Resources. The Offeror shall clearly and fully demonstrate that the Offeror has resources needed to acquire, train, and maintain required staffing levels to meet the requirements of the PWS. The Offeror shall provide a description of its validated processes and procedures that ensure high quality performance. Current certifications supporting these processes such as the

International Organization for Standards (ISO) 9001, Lean Six Sigma, and Capability Maturity Model Integration (Level 3) and other independent certifications, accreditations and appraisals shall be provided. Copies of certifications, audits, accreditations, and appraisals are not required to be submitted with proposals. A table detailing the pertinent information is sufficient (e.g. type of certification, certification number, expiration date, etc.). The Offeror shall provide its organizational chart listing the management hierarchy and staff responsibilities for key personnel as it applies to this offering. The Offeror shall provide a list of no more than five (5) key personnel that will be involved with this Contract. The Offeror shall explain the rationale for each key person selected for the role identified. Resumes for key personnel shall be provided. Each resume (two-page maximum) should include the following: (1) summary of knowledge, education and experience, (2) practical experience with pRFID, and (3) explanation of relevancy, experience, education as they relate to: the AIT requirement, execution of the contract, and DoD, NATO, and Coalition Partners experience. The

Offeror shall list and explain the methodology, the role and importance of their teaming arrangements (if any) and management of

Subcontractor(s).

(v) Configuration Management. The Offeror shall provide detailed methodology to identifying, implementing, managing, and maintaining

Configuration Management processes for pRFID hardware equipment, software and services. The Offerors proposal shall also discuss its ability to meet changing management requirements and support multiple configurations.

(vi) Technical Engineering Services (TES). Offeror shall provide a narrative illustrating their management approach and methodologies to planning and implementing the turnkey solutions. TES may include but is not limited to the utilization of hardware, software, pRFID architecture, personnel, site surveys, and installation plans to demonstrate the goal of a successful end-to-end solution. The Offeror shall demonstrate their approach to identifying requirements, planning, building, testing, and deploying projects conducted under TES.

In order to demonstrate the goal of a successful end-to-end solution, the narrative shall include Task Order reporting requirements, , technology insertion processes, Information Assurance Plans, Quality Control Plan (QCP), utilization of personnel, site surveys, and installation plans.

(vii) Customer Support. The Offeror shall propose how it plans to provide customer support required by the PWS; specifically detailing the help desk processes and website portal requirements.

(viii) Warranty. The Offeror shall present a solution to address the warranty support requirement as it applies to all products referenced within the PWS to include: the procedures for warranty repairs, repair center(s), locations, and specify the mechanism for affecting communications and workflow through the end-user community and Offeror.

(ix) Maintenance. The Offeror shall describe its methodology and approach for updates and maintenance of equipment as well as its ability to provide worldwide maintenance support, particularly in the US&P, NATO (FMSC#3), NATO-member countries, Afghanistan, Austria, Djibouti, Bahrain, Belgium, Bosnia, Croatia, Egypt, Fyrom, Germany, Honduras, Iraq, Italy, Japan, Kosovo, Kuwait, Kyrgyzstan, Oman, Pakistan, Panama, Qatar, Republic of Korea, Saudi Arabia, Sweden, Switzerland, UAE, United Kingdom, and Uzbekistan.

11 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(x) Risk Management. The Offeror shall provide detailed methodology for identifying, implementing, managing, and maintaining Risk

Management processes to include technology insertion processes to reduce the risk of obsolesce of AIT equipment, software and services for pRFID equipment, software and services.

(xi) Management Proposal Matrix. As an attachment, the Offeror shall provide a matrix demonstrating compliance to the requirements in the Performance Work Statement (PWS) Management Sections 7 thru 16, which are located in the "Descriptions/Specifications/Statement of

Work" section of this Solicitation. 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.).

In a separate column titled Value Added, when the Offeror believes it has exceeded a management requirement, the Offeror will provide a statement explaining the relevance, applicability and value to the Government.

At a minimum, the Offer shall include the following information:

PWS Requirement | Offeror's Proposal Sections | Value Added

(Paragraph Number | that address the PWS | and Title ) | Requirement |

7.4 Configuration | Section(s), Page(s), | Description explaining the

Management | Paragraph(s | relevance, applicability and

| | value to the Government

NOTE: The Management Matrix is NOT counted against the page limit.

(3) VOLUME 3 - PAST PERFORMANCE. The Past Performance Factor 3, as used in this solicitation, assesses the degree of confidence the

Government has that an offeror will successfully perform to the solicitation requirements based the Offerors record of relevant past and current contract performance.

TABLE 1.0

Volume | Title | Maximum Pages | File Naming Structure

3 | Past Performance | Up to 3 pages per reference | CAGE-pRFID-III-Perf-

| | maximum for the Offeror; | docx or .pdf.

| | Up to four (4) references |

| | maximum |

| | No page limit for Adverse |

| | Performance, or PPQs |

(i) Volume 3 shall contain the offerors:

A. Contract References: The offeror shall submit with its initial proposal contract references representing its recent, relevant performance under Government (Federal, state, local) and/or commercial contracts. The offeror shall submit no more than four (4) contract references for itself.

B. Recent definition (see Section M(3)(ii)).

C. Relevant definition (see Section M(3)(iii)).

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

a) Contract Number: (include task/delivery order number in the case of Indefinite Delivery, GSA, or BPA type contract references).

b) Identify if contract is predominately Hardware (Supply) or Service related.

c) Describe the type of Supplies and/or Service(s) or deliverables provided under the contract to include a description of the contracts relevance to the current procurement.

d) Award date, start work date, and completion of performance date.

e) Contract award value, current value, and final projected value.

12 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

f) Annual average dollar value of the contract and/or task order(s).

g) Geographical Locations of performance.

(ii) For work performed as:

A. Subcontractor: provide the name of the prime contractor (DUNS & CAGE), point of contact within the prime contractor organization

(company name) with a point of contact (POC) name, job title, email address, and telephone number.

B. Prime contractor: for commercial contracts provide the customer, point(s) of contact (POC), including job titles, email addresses, and telephone numbers. For Government contracts: provide the contracting activity name, address, Procurement Contracting Officer's and/or the Administrative Contracting Officers name, email address, and telephone number to include the Government Technical

Representative and/or Contracting Officer Representative (COR), and current email addresses and telephone numbers.

(iii) The contract information to be provided with each contract reference is on the attached Past Performance Questionnaire

(Attachment 0008). Offerors are required to complete a separate questionnaire for each contract reference. Ensure that all point(s) of contact (POC), including names, job titles, telephone and fax numbers, and email addresses are listed on the questionnaire. Only this information is to be completed by the offeror. The remaining information will be completed by the survey respondent. The survey questionnaires are to be provided to the government.

(iv) The Government is not required to interview all points of contact identified by the offeror. It is the responsibility of the

Offeror to provide complete past performance information and thorough explanations as required by Section L. The Government is not obligated to make another request for the required information.

(v) Adverse Government Contract Performance: In addition to the above contract references, the Offeror shall identify every recent and relevant contract it was awarded that experienced any performance problems related to deliverables or services; and every recent and relevant contract that was terminated, in whole or in part within the past three (3) years of issuance of the pRFID-III solicitation.

For any contract falling under the descriptions above, provide all of the information listed in the preceding paragraph, plus: provide a copy of any cure notices or show cause letters received, a copy of any Contract Deficiency Report (CDR), EPA violations, and identify reason(s) for any termination. Also, state any corrective actions taken to avoid recurrence, describe the extent to which the corrective action has been successful, and identifying points of contact who can confirm the success of the corrective measures taken.

The number of contracts provided in response to this paragraph for Adverse Contract Performance is unlimited.

(vi) The Government reserves the right to use data provided in the Offerors proposal and data obtained from other sources such as the

Federal Past Performance Information System (PPIRS).

(vii) References provided on classified contracts or contracts to foreign entities cannot be verified; therefore, classified and foreign contracts will not be evaluated.

(viii) 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.

(4) VOLUME 4 PRICE

(i) The Offeror shall complete the pRFID III Price Model (Attachment 0009). Each area that requires the Offerors input has been highlighted in Yellow. Failure to complete the pRFID III Price Model in its entirety may deem an Offeror as non-compliant and may not be considered for award.

(ii) The Offeror is required to complete the Contractor Fill-In section of the tabs within the Passive RFID III Price Model. The

Government does not guarantee the purchase of the quantities listed in the quantity column of Attachment 0009. The quantities are for evaluation purposes only.

(iii) For the following Firm Fixed Price CLINs, the Offeror shall complete the Proposed Unit Price column for each line item listed for

Products and Services in Ordering Periods 1 thru 5:

CLIN 0001

CLIN 0003

CLIN 0005

CLIN 0007

CLIN 0009

CLIN 0011

CLIN 0013

CLIN 0015

CLIN 0019

13 16

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(iv) For CLIN 0017, the Government has provided a surrogate in the amount of $10,000.00, which will be used for evaluation…