W15QKN18R0037-0001.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

0001 2018APR09

W15QKN

ARMY CONTRACTING COMMAND - NJ

PICATINNY ARSENAL, NJ 07806-5000

PAUL GIOVANNOLI

EMAIL: PAUL.GIOVANNOLI.CIV@MAIL.MIL

W15QKN-18-R-0037

2018MAR23

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 13

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: PAUL GIOVANNOLI

Buyer Office Symbol/Telephone Number: ACC-NJ-IC/(973)724-2136

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

The purpose of Amendment 0001 is to answer the following questions. Sections L and J are also updated as a result of these questions:

Question 1: Attachment 2 & Model Contract / The CLIN numbers in Attachment 2 do not match the Model Contract CLIN numbers. Which is correct?

Answer 1: The CLINs in the RFP are set up as a place holder. Agree that the CLINs do not match the CLINs in Attachment 0002 but the pricing should all be added in Attachment 0002. The pricing evaluation will be based on the unit pricing included in Attachment 0002.

Question 2: CDRL 007 & 014 Block 16 / CDRL Block 16 appears to be duplicated for these CDRLs. Please confirm the requirements for the

Technical Manual and IETM, as they are both referenced within Block 16 of both CDRLs.

Answer 2: CDRL 007 is for the Paper TM and CDRL 014 is for the Interactive Electronic Technical Manuals (IETMs), these are not duplicates.

Question 3: CDRL 035 Block 16 / CDRL 035 Block 16 remarks are identical to CDRL 034 Block 16 remarks. Is Block 16 of CDRL 035 correct?

Answer 3: CDRL information for Blocks may be the same for multiple CDRLs however this does not mean that it is a duplicate or incorrect.

Each CDRL is a separate deliverable. These deliverables are linked both are correct as written.

Question 4: CDRL 025 / Please clarify whether deliveries are desired 10 days prior to the end of the quarterly reporting period, or 10 days after.

Answer 4: 10 days after.

Question 5: CDRL 028 / The timing of IPRs may not logically fall in a manner to support regular reviews of the IMS. PMRs, although mentioned in the CDRL, do not appear to be part of the SOW. Will the Government consider that this CDRL be delivered monthly?

Answer 5: IMS shall be submitted initially prior to Program kick-off/start meeting. IMS shall be updated, as necessary, and submitted 15 days prior to Program management reviews and IPRs.

Question 6: CDRLs 018, 020, 021, 024, 027 Block 16 / CDRL language in these five appear to be identical. Please review and confirm requirements in all Block 16s.

Answer 6: CDRL information for Blocks may be the same for multiple CDRLs however this does not mean that it is a duplicate or incorrect.

Each CDRL is a separate deliverable. These deliverables are all part of the overall training support package and development, and should be developed concurrently. The CDRLS are correct.

Question 7: Model Contract / Is it the government's intent that CDRLs 001 - 013, 015 - 017, 022, 023, 025, 026, 028 - 035, 037 be priced within CLIN 4, or as part of the CLIN 2 Services?

Answer 7: It is not the governments intent that CDRLs for NSP requirements be priced within CLIN 4 but rather that per applicability of

CDRL to contract requirement, offeror consider relevance of each NSP requirement (CDRL) to its applicable price proposal.

Question 8: Model Contract / Please clarify which CLINs will be awarded with award of Ordering Period 1.

Answer 8: The Government is only requesting pricing for Ordering Period 1 for CLINs 0001 and 0034-0042 on Hardware Items OP1-5 tab of

Attachment 0002 and for labor categories identified in the Services OP1-5 tab of Attachment 0002. If the cell is blacked out for a particular CLIN for an Ordering Period, the Government is not requesting pricing for that CLIN in that Ordering Period.

Question 9: RFP / What date should be assumed for contract award?

Answer 9: L.2.1.5 requests that proposals be valid through 31 July 2018.

Question 10: Section L - L.4 page 75 / iGov recognizes that narrative being provided within the Technical Volume that is limited to 25 pages must show compliance to all sections of the SOW. How does the narrative section within the Technical Volume get evaluated?

Answer 10: Section M M.2 shows the adjectival rating definitions and Subfactors evaluation criteria. Offeror must acknowledge that they meet all SOW and Specification requirements, and then address the specific areas defined in section L.

Question 11: Section L - L.2.3.1 / How does the Government want the delivered hard copies bound (3-ring binders, spiral bound, etc.)?

Answer 11: The Government has no preference on how the hard copies are bound.

Question 12: Section L - L.2.3.1 a / Is the signed and completed copy of the attached Form 33 (SF 33) and continuation sheets (Sections

A through M) in addition to those being provided in Volume V?

Answer 12: No, those are the same. One copy is sufficient.

2 13

W15QKN-18-R-0037 0001

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Question 13: Section L - L.2.3.1 b / What is the reference to "Process flows" in regard to?

Answer 13: Process Flows could include but not limited to; price/cost roll-up methodologies or formulas not included in Excel

Spreadsheets, Work Breakdown Structure (WBS) Maps, or traditional flow down charts.

Question 14: Section L - L.2.3.1 c / Is the one hard copy and one electronic copy (on CD) submitted as an .XPS file in addition to the certs/reps being provided in Volume V?

Answer 14: The certs/reps call be submitted as part of Section V. One copy of each is sufficient.

Question 15: SOW - 3.0 page 14 / Please clarify what scope is expected to be requested under the initial Letter of Contemplation.

Answer 15: This solicitation for the base IDIQ has a minimum guarantee for 40 first article test units. The Letters of Contemplation in SOW 3.0 is referring to possible future tasks once the basis IDIQ is awarded.

Question 16: SOW - 3.0 page 14 / Please clarify the anticipated timing of issuance of the initial Letter of Contemplation.

Answer 16: The first delivery order will be for, at minimum, the minimum guarantee of the 40 first article test units. Subsequent

Letters of Contemplation will be issued when the Government has a requirement.

Question 17: SOW - 6.1.6 page 18 / How long should we assume IPRs last?

Answer 17: The length will depend on the level of review.

Question 18: SOW - 6.1.11 page 18-19 / How long should we assume Verification lasts?

Answer 18: The length will depend on the level of review.

Question 19: SOW - 6.1.6, 6.1.1, 6.2.12, 6.2.12.1, 6.2.12.2, 6.2.12.3, 6.2.12.13 / Please clarify which SOW reference is correct, as the

% complete in the multiple references vary, as does the timing of the IPR as compared to the submission of the documents.

Answer 19: 6.1 refers to the Technical Manual and 6.2 refers to the CBT and training package. Both are separate but should be developed jointly as they will feed off each other. The % complete is subjective but the days should set the schedule, IPR#1 120 days after start of work, IPR#2 NLT 45 days after IPR#1, IPR #3, NLT 90 days after IPR#2.

Question 20: SOW - 5.4 page 16-17 / What types of audits does the government anticipate performing, with what frequency, and how long should each audit be estimated to last?

Answer 20: The Government reserves the right to conduct Configuration Audits and Inspections. These audits may be performed on site at contractor facilities, at Government facilities, or at Operational Government sites. Frequency as required and duration will depend.

Question 21: SOW, CDRLs - 6.1.8.2 page 18 / SOW states "Contractor shall notify the government at least two weeks prior to validation with date and location", however CDRL says 20 days prior. Which is correct?

Answer 21: There is no CDRL for a Validation date and location notification. There is a CDRL (029) for the TM Val Plan, which calls for submission 30 days prior to the 30% PTM and updated to 30 days for the 70% PTM and 100% PTM validations. There is also a CDRL for the TM

Val Certificate (CDRL 030) which is due 30 days after the 100% PTM validation.

Question 22: SOW, CDRLs - 6.1.8, 6.1.11 page 18 19 / Please clarify which CDRLs (by CDRL #) need to undergo validation & verification.

Answer 22: Both CDRL 005 and CDRL 013, must have Validation and Verification.

Question 23: SOW - 6.4.3 pg. 23 / How long should the Provisioning & Publications Guidance Conference be planned?

Answer 23: The length will depend on the level of review.

Question 24: SOW - 6.4.14 pg. 24 / How long should the Provisioning Conferences planned?

Answer 24: The length will depend on the level of review.

Question 25: SOW, CDRLs - 6.5 pg. 24 / This SOW paragraph references delivery of an ICD, however this is not a CDRL. Please clarify this requirement.

Answer 25: Should be considered as part of the Engineering Data for Provisioning, CDRL-033

Question 26: SOW - 6.11 pg. 28 / Is the referenced table 1 missing?

Answer 26: Please see Attachment 0001 for the SOW tables.

Question 27: Section L - L4.2.1 pg. 75 Attachment 002 / "Each offeror must propose a firm-fixed price for First Article Test CLINS for all ordering periods". The master contract requires FAT for Ordering Period 1 only. Please confirm FAT is not required for ordering period 2-5.

Answer 27: The Government only requests pricing for FAT in Ordering Period 1.

Question 28: Section L - L.4.5 pg. 79 / Offerors are required to complete Attachment 002, Section B Matrix, which includes pricing for the priced CDRL's. Are we also required to complete Blocks 17 & 18 for these CDRL's?

Answer 28: Yes, please fill in the Blocks 17 and 18 for the priced CDRLs in addition to Attachment 0002.

3 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Question 29: Section L - L.4.5 pg. 79 / CDRLs Block 17 Price Group, can the government clarify what information required for this field?

Answer 29: The Contractor needs to specify the appropriate price from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.

a. Group I. Definition -Data which is not otherwise essential to the contractor's performance of the primary contracted effort

(production, development, testing, and administration) but which is required by DD Form 1423.

Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with

Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the

Government.

b. Group II. Definition -Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.

Estimated Price -Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.

c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.

Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and delivering such data item to the Government.

d. Group IV. Definition -Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.

Estimated Price -Group IV items should normally be shown on the DD Form 1423 at no cost.

Question 30: Model Contract - 3.0 pg. 14 / Does the government anticipate adding a travel/ODC CLIN?

Answer 30: Travel and ODCs will be addressed on a task by task basis and will be evaluated on each individual task.

Question 31: Model Contract - 6.8.2 page 26 / Does the government anticipate adding a shipping/ODC CLIN?

Answer 31: No, the government does not anticipate adding a shipping/ODC CLIN to contract as shipping will be covered under warranty, see last sentence of 6.8.2 The contractor shall be responsible for all warranty repair actions including related transportation costs.

Question 32: Model Contract - 6.8.3 pg. 26 / How are test, troubleshooting, and evaluation costs to be paid (which CLIN)?

Answer 32: Contractor shall notify Government if there is a test, troubleshooting and evaluation (TT&E) costs and the amount of the repair costs. If the Government elects to have the system repaired, the Government may provide required costs to contractor through use of Government Purchase Card or purchase order (provided by Government) to accomplish necessary Non-Warranty Repair Actions (NWRA) support. Task orders for NWRA support will not be issued under this contract. If the Government elects not to have system repaired, then the contractor shall return system to Government at no additional expense.

Question 33: The RFP states that no less than 10-point font be used. Does that apply to tables and graphics, or can those be no smaller than 8- point font?

Answer 33: Yes the 10-point font restriction applies to everything, including foldout pages.

Question 34: In your Instructions to Offerors, questionnaires are sent to the Contracting officer and the Technical Representative. Can we send questionnaires to the PCOs or as a subcontractor to our Prime?

Answer 34: Past Performance questionnaires should only be sent to Contracting Officers and Technical Representatives for actions in which the Offeror was the Prime Contractor.

Question 35: On the Instructions to Offerors, clarifying the page count for the technical volume is 25 pages?

Answer 35: Yes

Question 36: Do test reports or certificate of compliance to the Specification count towards the page count?

Answer 36: No. Section L.3.3.1 has been updated to include test reports or certificate of compliance as not counting towards the page limitations.

Question 37: For items that are internal to our solution that are also called out for pricing in attachment 0002, do you still want a price?

Answer 37: Section L.4.2.1 has been updated to provide proposal instructions for offerors with solutions that include internal components.

Question 38: IUID Reader Kit -the specification describes the requirement extensively, but there is no mentioning of purchasing one. Is this just extra information in the specification, or is the Government asking the contractor to purchase the reader?

Answer 38: No, the IUID Reader Kit was accidentally left off of the price sheet. Please provide a Unit Price for a quantity range of 1-

25 and 26-100 for Ordering Periods 2-5. Attachment 0002 Section B Matrix has been updated to include the IUID Reader Kit.

4 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

*** END OF NARRATIVE A0003 ***

5 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION J - LIST OF ATTACHMENTS

List of Number List of Number

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

Attachment 0002 SECTION B PRICING MATRIX 05-APR-2018 002 EMAIL

6 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L. PROPOSAL SUBMISSION:

L.1 Introduction: This section contains general proposal submissions instructions as well as specific proposal requirements for the

MSD-V4L.

L.2 PROPOSAL INSTRUCTIONS:

L.2.1 General:

L.2.1.1 Offerors shall provide information by addressing each Factor/Subfactor in the format and sequence identified in the solicitation. The Offerors must provide information in sufficient detail to allow the Government to make a best value assessment of the

Offerors capability to support the proposed response to the evaluation criteria. Proposals that do not contain the information requested in the solicitation risk being determined unacceptable by the Government. The Government will not assume the Offeror possesses any capability, understanding, or commitment not specified in the proposal.

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

L.2.1.3 The Government intends to award without discussions (see FAR 52.215-1).

L.2.1.4 Alternate Proposals: Alternate proposals will not be accepted.

L.2.1.5 Proposals shall be valid through 31 July 2018.

L.2.1.6 Bid samples and standard accessories received after the time and date specified will be considered late submissions in accordance with FAR part 52.214-23.

L.2.2 All questions concerning this procurement, either technical or contractual must be submitted in writing to the Contracting

Officer. No direct discussion between the technical representative and a prospective Offeror shall be conducted. Questions and proposals shall be submitted to the following point of contact:

Army Contracting Command New Jersey

ACC-NJ-IC, Bldg. 10

ATTN: Eric Wagner

Telephone: (973)724-2177

Picatinny Arsenal, NJ 07806-5000

E-mail: eric.j.wagner1.civ@mail.mil

Please note that electronic e-mail proposal submissions will not be accepted.

L.2.3 The proposal shall consist of the following:

L.2.3.1 Each proposal shall be submitted in the English language and consist of and include all of the following:

a. One (1) signed and completed paper copy of the attached Standard Form 33 (SF 33) and continuation sheets (Sections A through M) signed by a person authorized to enter into the proposed contract on behalf of the Offeror. Acknowledgment of all amendments to the solicitation and all continuation sheets are to be filled in as directed, i.e., proposed prices in the CLINs/Pricing Matrices in Section

B, any fill-ins required, such as Contract Data Requirements List: DD Form 1423 with Blocks 17 and 18 completed if required, and

Certifications and Representations in Section K. Offerors are directed to thoroughly read the solicitation and fill in the required information in the appropriate solicitation clauses. For any fill-ins that are not applicable, the Offeror must acknowledge by indicating N/A. The proposal must also include computation for the use of Government Property, if applicable.

b. Original and one (1) paper copy and three (3) electronic CD copies of the proposal volumes, as reflected in L.3., shall be compiled using the Microsoft Office for Windows suite of applications, submitted on a single-write CD-ROM to prevent accidental erasure of the data therein, and formatted for an MS Windows compatible computer. The Price Factor shall be contained on a separate CD from non-price

Factors. Price breakdown, when applicable, will include MS Excel spreadsheets with formulae intact. Process flows may be delivered in hard copy if not compatible with the above software. CD copy must mirror the submitted hard copies. If the CD copy and hard copy differ, the CD copy supplied for each Factor will be used for the evaluation. Each CD must be clearly marked with the Offerors Name and the Solicitation Number. Alternatively, files, with the exception of the price breakdown as noted above, may be provided in Portable

Document Format (.pdf).

c. Representations through System for Award Management. The purpose of electronic Representations and Certifications is to provide all

Offerors with a portal in which to submit Reps/Certs in a publicly accessible format, nullifying the requirement to submit identical information in response to each and every Federal contract solicitation. As a requirement under the MSD-V4L solicitation, all Offerors

7 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

must submit Reps/Certs data into the System for Award Management (S.A.M.) at https://www.sam.gov/ and provide one (1) hard copy and one (1) electronic copy (on CD) submitted as an .XPS file. Any Offeror that has previously submitted Reps/Certs data into SAM is reminded to update the data prior to submitting with the proposal.

L.2.3.2 Each Large Business Offeror shall provide a Small Business Subcontracting Plan that contains all the elements required by FAR

52.219-9, alternate II. This plan shall be incorporated into any resultant contract in reference to the RFP.

L.3 FORMAT FOR PROPOSALS

L.3.1 The Offerors proposal shall be submitted in severable volumes based on the Factors as set forth below and all information specific to each Factor shall be confined to that volume. Each proposal must include all volumes and shall be submitted by the closing date and time of the solicitation. Failure to provide any volume may result in the proposal being given an Unacceptable rating.

Information provided shall be specific to each Factor.

Page limitation for each Volume is as follows:

Volume I Technical 25 pages

Volume II Price None

Volume III Past Performance None

Volume IV Small Business Participation None

L.3.2 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 should be created using the Table of Contents feature in MS Word. MS Word (.doc) files shall use the following page setup parameters, however this format does not apply to data being supplied under Subfactor 2 of the Technical Factor:

Margins Top, Bottom, Left, Right - 1

From Edge Header, Footer 0.5

Page Size, Width 8.5

Page Size, Height 11

L.3.3 Length:

L.3.3.1 Each volume shall be as brief as possible, consistent with complete submission. The page count will be made by counting the pages from left to right, consecutively. Pages that exceed the page limitation will be returned to the Offeror and will not be evaluated. Each paragraph shall be separated by at least one blank line. Annexes, documentation and attachments that are submitted by the Offeror, which are not required as part of the RFP, will count against the page limitations. If pages are printed on both sides, each side will count as a separate page. The following will not count against page limitations: volume title pages, table of contents pages, cross-referencing pages, indices, acronym lists, test reports or certificate of compliance documents and page dividers (used to separate proposal sections). Pages should not exceed 8-1/2 inches in width by 11 inches in length; foldout pages depicting such items as sketches, factory floor layouts, etc. may be used, with each fold counted as one additional page. The font used shall not be less than

10 point.

L.3.3.2 Deviation from Requested Format. Request for deviations from the requested format shall be submitted to the Procuring

Contracting Officer (PCO) no later than fifteen (15) days after release of the solicitation. Offerors shall provide an explanation, in a clearly relatable format such as a matrix, of any differences between the manner in which the proposal was requested and the manner in which it is proposed to be submitted.

L.3.3.3 The Offeror is responsible for including sufficient details to permit a complete and accurate evaluation of the proposal.

Offerors shall provide a proposal that, at a minimum, addresses those evaluation Factors and Subfactors required in Section M of the

RFP.

L.3.3.4 File Packaging - All of the proposal files shall be compressed (zipped) into one file using WinZip version 6.2 or later, or as separate uploads in their native format, i.e. doc, xls, ppt, etc. Please note Self extracting .exe files will not be accepted.

L.4 SPECIFIC PROPOSAL INSTRUCTIONS

Offerors are responsible for including sufficient details (i.e. drawings, test data, specification sheets) to permit a complete and accurate evaluation strictly from a technical standpoint. The Technical Volume(s) shall have a separate index, which contains narrative titles that are cross-referenced to both the applicable Statement of Work (SOW) paragraph and page number. This index shall not count against the Page limitation for the Technical Volume. The narrative discussions shall also be related to the applicable SOW paragraph by placing the appropriate SOW number at the beginning of the discussion text. The proposal shall be detailed and clearly stated to allow an assessment by the Government without the need for additional clarifications. The Offeror shall provide detailed narrative discussions that address both the SOW and the CDRLs of the solicitation. All information and data provided shall be specific to the MSD-

8 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

V4L, components and assemblies, except for the area of Past Performance. In the response to the Request for Proposal, the Offeror must address the following Factors and Subfactors:

L.4.1 Volume I FACTOR 1: TECHNICAL

L. 4.1.1 Subfactor 1: Performance

a. The Offerors proposal shall include one (1) bid sample with standard accessories (Battery or Batteries, Alternating

Current (AC) Power Cable, and Adapter Assembly) for the MSD -V4L and a copy of the O&M manual for each, which is due at the same time as the paper proposal submission. The bid sample shall be shipped to the proposal POC as listed in the proposal instructions above. A bid sample is the production or production representative commercial solution that the Offeror plans to present for Government acceptance as the MSD-V4L. The bid sample shall be a released-design product currently in production and manufactured from active production processes under design and manufacturing change control and not a developmental item. The bid sample shall be configured as specified in the MSD-V4L Detail Specification with Windows 10 Enterprise and all drivers necessary to operate, load, and execute PassMark

Software. The bid sample shall not be password protected.

b. Each Offerors bid sample unit will be retained by the Government, without charge, until contract award. Unless otherwise requested, the bid sample unit and O&M manual will be returned to the unsuccessful Offeror(s) at their own expense after contract award. The Government will not be held responsible for the condition of the bid sample returned to any Offeror.

L.4.1.2 Subfactor 2: Display

All proposals shall provide data artifacts in the form of test reports, specification sheets or other documents that show display resolution and brightness requirements of the Detail Specification are met or exceed the threshold/objective.

L.4.2 Volume II FACTOR 2: PRICE

L.4.2.1 Offerors shall not propose pricing on the CLINs in Section B. These contract line items are established to enable the placement of future orders. The Offerors shall submit pricing on Attachment 0002 Section B Matrix for all priced items, including all quantity ranges, when applicable. For any accessory items, included in the Attachment 0002 Section B Matrix, which are internal to an Offerors

MSD-V4L platform/unit, the offeror shall include a unit price of $0 in the pricing matrix for all ordering periods. The proposed price for Hardware shall be inclusive of all fabricating, testing, inspection, packaging and delivery of the solicited item. Each Offeror must propose a firm-fixed-price for First Article Test CLINS for all ordering periods. Failure to provide a price for FAT may result in the offer not being considered for award.

Delivery Orders will be issued in accordance with the procedures and provisions set forth in the Base Contract.

For the Services, Offerors shall submit only one fully loaded labor rate for each labor category for each ordering period in Attachment

0002 Section B Matrix.

For CDRLs, the offerors shall propose a price for every priced CDRL.

L.4.2.2 Any HUBZone Small Business Concern shall provide proof of HUBZone certification with its proposal submission.

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

L.4.3 Volume III FACTOR 3: PAST PERFORMANCE

L.4.3.1 Offerors shall identify pertinent past history, which indicates that similar efforts of equal or greater complexity have been performed using the Offerors existing plant capability and demonstrate satisfaction of customer requirements.

L.4.3.2 Offerors shall submit a list of all recent Government contracts (prime and major subcontracts) in performance or awarded to the

Offeror and any of its major subcontractors within the past three (3) years, or awarded earlier than three (3) years ago, but for which deliveries/performance occurred or were scheduled to occur within the past three (3) years, which are relevant to the effort required by the solicitation. Data concerning the prime Offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order. Offerors are reminded that both independent data and data provided by the Offerors in their proposals may be used to evaluate the Offerors past performance. The Government plans to rely on existing documentation from Federal databases to the maximum extent practicable. Sources of existing information available to the Government include, but are not limited to, Past Performance

Information and Retrieval System (PPIRS), Federal Awardee Performance and Integrity Information System (FAPIIS), and Electronic

Subcontract Reporting System (eSRS). The Government may use past performance information obtained from sources other than those identified by the Offeror. The burden of providing thorough and complete past performance information remains with the Offerors.

Proposals that do not contain the information requested by this paragraph may result in rejection or receipt of a high performance risk evaluation by the Government. This volume shall be organized into the following sections:

9 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(1) Section 1 Contract Descriptions. This section shall include the following information in the following format:

(a) Contractor/Subcontractor place of performance, Commercial and Government Entity (CAGE) Code and Data Universal Numbering System

(DUNS) Number. If the work was performed as a subcontractor, also provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, e-mail address, and telephone and fax numbers). PLEASE NOTE:

While an Offeror may submit past performance information on relevant efforts where they performed as a major subcontractor, the

Government does not have privity with subcontracts and therefore, may not be able to obtain qualitative information.

(b) Government contracting activity, and current address, Procuring Contracting Officer's name, e-mail address, telephone and fax numbers.

(c) Governments technical representative/COR, and current e-mail address, telephone and fax numbers.

(d) Government contract administration activity and the Administrative Contracting Officer's name, and current e-mail address, telephone and fax numbers.

(e) Government contract administration activity's Pre-Award Monitor's name and current e-mail address, telephone and fax numbers.

(f) Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket Purchase Agreements, also include Delivery Order Numbers.

(g) Contract Type (specific type such as Fixed Price (FP), Cost Reimbursement (CR), Time & Materials (T&M), etc.) In the case of

Indefinite Delivery contracts, indicate specific type (Requirements, Definite Quantity, and Indefinite Quantity) and secondary contract type (FP, CR, T&M, etc)).

(h) Awarded price/cost.

(i) Final or projected final price/cost.

(j) Original delivery schedule, including dates of start and completion of work.

(k) Final or projected final, delivery schedule, including dates of start and completion of work.

(2) Section 2 - Performance. Offerors shall provide a specific narrative explanation of each contract listed in Section 1 describing the objectives achieved and detailing how the effort is relevant to the requirements of the solicitation.

(a) For any contracts that did not/do not meet original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The Offerors shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All Requests for Deviation and Requests for

Waiver shall be addressed with respect to causes and corrective actions. The Offerors shall also provide a copy of any Cure Notices or

Show Cause Letters received on each contract listed and a description of any corrective action implemented by the Offeror or proposed subcontractor. The Offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

(b) For all contracts, the Offeror shall provide data on all manufacturing warranty returns. Data shall delineate total number of warranty returns, number of Could Not Duplicate (CND), number of failures attributable to GFE component failures, and number and nature of failures attributable to the Offerors delivered product.

(3) Section 3 Subcontracts. Offerors shall provide an outline of how the effort required by the solicitation will be assigned for performance within the Offerors corporate entity and among the proposed subcontractors. The information provided for the prime Offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, DUNS Number and type of work to be performed by citing the applicable Government SOW subparagraph number. This includes all major subcontractors who will be providing critical hardware/services or whose subcontract is for more than 25% of the total proposed price.

(4) Section 4 New Corporate Entities. New corporate entities 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 should be included in the files described in the sections above.

(5) Past Performance Questionnaire. For all contracts identified in Section 1, Past Performance Questionnaires must be completed and submitted (Attachment 0005). The Offeror shall complete Part I of the Past Performance Questionnaire and e-mail the questionnaire to both the Government contracting activity and technical representative responsible for the past/current contract. The POCs shall be instructed to electronically complete Part II of the questionnaire and e-mail the entire questionnaire to the Contracting Officer within thirty (30) calendar days of the release of the RFP, to eric.j.wagner1.civ@mail.mil. The Offeror shall also e-mail to the Contracting

Officer a list of all the POCs who were sent a questionnaire. The Government must receive this list within thirty (30) calendar days after release of the RFP. The POC List shall be submitted in Word for Windows Table Format to include the following fields:

Solicitation Number; Company Name; Contract Number; Government Agency; POC Last Name, First Name; POC Title; POC Telephone Number; POC E-

Mail Address; Date E-Mailed to POC (month/day).

10 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.4.4 Volume IV FACTOR 4: SMALL BUSINESS PARTICIPATION

L.4.4.1 The Small Business Participation Factor Volume is comprised of a single chapter. Offerors are responsible for including sufficient detail to permit a complete evaluation. Any information provided as part of the Small Business Participation Factor Volume may be used to correlate the evaluation of the other proposal volumes.

L.4.4.2 This provision applies to every Offeror (U.S. and non-U.S.), regardless of size status or locations of working facilities or headquarters. For proposal preparation purposes, the Offeror's Small Business Participation proposals shall be consistent with any subcontracting references/identification contained elsewhere in any other Factor Volume. Percentages are calculated using proposed total contract price as calculated in accordance with L.4.2. This price becomes the denominator and include first-tier subcontractors only. For the purpose of evaluating Small Business Participation, the total contract price is determined by multiplying the unit price for a single MSD-V4L from ordering period 2, range 401 2,500 times 19,806 which is the estimated maximum number of MSD-V4Ls to be purchased on this contract. Offerors shall also explain their rationale as to why the percentage of SB participation being utilized for this effort is appropriate for their company. Offerors shall describe their approach and efforts undertaken to utilize small businesses

(SB). SB targets will be incorporated into any resulting prime contract and contractors will be required to report SB participation.

L.4.4.3 All Offerors, including Offerors who are themselves U.S. small business concerns based on the NAICS code assigned to this requirement, are to identify the extent to which U.S. small business concerns will be utilized as first-tier subcontractors in the performance of this proposed contract. U.S. small business concerns are defined (1) in FAR 19.001 and (2) by the criteria and size standards in FAR 19.102 for the applicable NAICS code. U.S. small business concerns include Small Businesses (SBs), Small Disadvantaged

Businesses (SDBs), Woman-Owned Small Businesses (WOSBs), HUBZone Small Businesses (HUBZone SBs), Veteran-Owned Small Businesses (VOSBs), and Service Disabled Veteran-Owned Small Businesses (SDVOSBs).

L.4.4.4 If the Offeror (to include any U.S. small business concerns who are proposing as part of a joint venture or teaming arrangement) is itself a U.S. small business concern, the Offeror's own participation as a SB, SDB, WOSB, HUBZone SB, VOSB, or SDVOSB will also be considered small business participation for the purpose of this evaluation. In this event, the extent of the Offeror participation as a U.S. small business concern shall be detailed in the same manner as subcontracts to first-tier U.S. small business concerns.

L.4.4.5 Small Business Amounts: All Offerors shall address anticipated U.S. small business concern participation and subcontracting based on the total contract dollars proposed by the Offeror.

L.4.4.6 The Offeror shall provide information for small business participation and subcontracting in a table format in accordance with the following example:

Small Business Participaton Table (in Millions)

Business $ Cost All % of SB Cost Total

Category Contracts Participaton SubK

Contract Total Price $43.00

SB $10.34 24.00% $10.34 of $43.00

SDB $2.86 6.65% $2.86 of $43.00

SDB $2.36 5.50% $2.36 of $43.00

HBCU/MI $0.50 1.15% $0.50 of $43.00

WOSB $1.55 3.60% $1.55 of $43.00

HUBZone SB $1.08 2.50% $1.08 of $43.00

VOSB $1.55 3.60% $1.55 of $43.00

SDVOSB $1.46 3.40% $1.46 of $43.00

L.4.4.6.1 Guidance for filling in the above "Small Business Participation" Table:

(a) Include first-tier subcontractors only. Note that members of a joint venture may be considered the Offeror or the first tier subcontractors, depending on the legal form of the joint venture as defined in its agreement document.

(b) If the Offeror is a U.S. small business concern, detail the extent of the Offeror participation as a U.S. small business concern in the same manner as subcontracts to first tier U.S. small business concerns.

(c) Percentages should be rounded to the nearest tenth of a percent.

L.4.4.6.2 Additional Guidance for particular Business Categories:

(a) For "Contract Total Price": Include the Offeror's proposed Total Contract Price on this line.

11 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(b) For SB: Include U.S. small business concerns from all categories (i.e. SB, SDB, WOSB, HUBZone SB, VOSB, SDVOSB and HBCU/MI) in the dollars and percentage on this line. The SDB, WOSB, HUBZone SB, VOSB and SDVOSB are subcategories of SB and the dollars in each of these may not add to match the total dollars in the SB line due to the following: In some cases the same dollars may be reported in more than one block (i.e., a $10,000 subcontract to a Woman-Owned Small Business that is also a Service-Disabled Veteran-Owned Small Business should be entered on four rows: $10,000 under SB, $10,000 under WOSB, $10,000 under VOSB and $10,000 under SDVOSB). Be sure that the dollars are counted in the SB line only once and not four times (e.g. $40,000 representing the same firm participating at $10,000 in differing categories). Note that the SB percentage is not simply a total of the percentages of each SB subcategory and must be calculated separately as shown in the chart.

(c) For HUBZone SB: Include only "SBA certified" HubZone SBs. Note that this is different from some of the state HUB certifications.

(d) The term small disadvantaged business, when used in accordance with FAR 52.219-9, includes Historically Black Colleges and

Universities (HBCU) and Minority Institutions (MI), in addition to small disadvantaged business concerns. The percentages for HBCU and

MI shall be separately identifiable but included in the overall SDB percentage.

L.4.4.7 Small Business List: All Offerors shall provide the names and CAGE codes of small business concerns (including the Offeror if a small business concern) who would participate in accomplishing the proposed contract; the small business classification of each U.S.

small business concern (i.e. SB, SDB, WOSB, HUBZone SB, VOSB and SDVOSB); a short description of the specific services to be provided by each small business concern; and the estimated total dollars for each service or product.

a. This data shall be provided in a table format in accordance with the following example:

b. If a small business does not have a CAGE code, insert the word "None" in the table above. Note that during the evaluation, the

Government may request that the Offeror submit a letter from the small business affirming the information provided in your proposal.

c. For SB Classifications(s), list all SB classifications that apply to each concern in the table above.

L.4.4.8 If the Offeror IS NOT a U.S. small business concern and must submit a Small Business Subcontracting Plan under the RFP in accordance with FAR 52.219-9, the Small Business Subcontracting Plan shall be consistent with the Offeror's Small Business Participation proposal information provided in response to L.4.4.5 (recognizing that the Small Business Subcontracting Plan percentages will be different in that the percentage calculation denominator is total subcontracting amount as opposed to this Small Business Participation

Factor where the percentage calculation denominator is the Offeror's proposed Contract Target Price).

L.4.4.9 Compliance with FAR 52.219-9.

L.4.4.9.1 Offerors which are both: (a) other than U.S. small business concerns (as defined by the NAICS code applicable to the RFP), and

(b) have had prior contracts requiring the submission of a Small Business Subcontracting Plan in accordance with FAR 52.219-9 are to:

Provide a description of their performance in complying with the requirements of FAR 52.219-9, including documentation of both their goals and their accomplishment of the goals established under subcontracting plans of prior contracts performed over the past twelve

(12) months (from date of solicitation issuance). This documentation shall include Individual Subcontracting Reports (ISRs/DD Form 294s) which list both goals and accomplishments against individual or master plans. If over the last twelve (12) months from the date of RFP release, the Offeror reported accomplishments against commercial or comprehensive subcontracting plans in lieu of individual or master plans, the Offeror shall submit the plans to document the goals and the Summary Subcontract Reports (SSRs/DD Form 295s) to document the accomplishments. (Note: if the Offeror has not performed a contract over the past twelve (12) months, which included FAR 52.219-9, the

Offeror shall so state).

L.4.4.9.2 Offerors which have had prior contracts requiring a Small Business Subcontracting Plan IAW FAR 52.219-9 and provide the information requested in L.4.4.9.1 above shall not respond to L.4.4.10 below.

L.4.4.9.3 If the reporting entity listed on a subcontracting report is different from the name of the proposing prime, provide an explanation of the legal relationship between the other entity and the proposing prime and a description of how the other entity's small business accomplishments reported are applicable to the current proposal. This explanation should include Business Name, CAGE Code and

DUNS number of the other entity and the proposing prime.

L.4.4.10 Approach to meeting FAR 52.219-8. Offerors which are either U.S. small business concerns, or other than U.S. small business concerns (as defined by the NAICS code applicable to the RFP) having had no prior contracts requiring a Small Business Subcontracting

Plan in accordance with FAR 52.219-9 shall substantiate their proposed approach to meeting the requirement of FAR 52.219-8.

Substantiation may include providing:

(a) A description of the Offeror's performance, over the past twelve (12) months (from date of solicitation issuance), in complying with the requirements of FAR 52.219-8 (Note: if the Offeror has not performed a contract over the past twelve (12) months (from date of

12 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

solicitation issuance), which included FAR 52.219-8, the Offeror shall so state);

(b) A description and available documentation of any methods or techniques used to promote small business participation;

(c) Any listings of U.S. small business concerns who are subcontracting candidates;

(d) Internal procedures used to monitor small business participation during contract performance; and/or

(e) Any other information substantiating that the Offeror will satisfy the requirements of FAR 52.219-8.

L.4.5 Volume V SOLICITATION, OFFER AND AWARD DOCUMENTS AND CERTIFICATIONS/REPRESENTATIONS

L.4.5.1 Each Offeror shall complete (fill-in and signatures) the solicitation sections indicated below using the file (without modification to the file) provided with the solicitation. An authorized official of the firm shall sign the SF 33 and all certifications requiring original signature. An Acrobat PDF file shall be created to capture the signatures for submission.

Section A through M Fill-ins as required

Section A…