W900KK-24-R-0002-Amend-0001_19Mar2024.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

This amendment is issued to update the RFP Sections I, L, and M:

- Section I clause 252.211-7003, Item Unique Identif ication and Valuation, w as updated.

- Section L 3.1.1.2 is changed from: “The Offeror shall describe their approach having performed or performing a technology refreshment, technology insertion, modernization, or other w ork related to Live Training Range Instrumentation.…” to “The Offeror shall describe their approach having performed, performing, or how they w ould perform a technology refreshment, technology insertion, modernization, or other w ork related to Live Training Range Instrumentation…”

- The last paragraph of Sections M.3.1.1 and M.3.1.2 w ere updated to state: “The Offeror’s description shall demonstrate that they have the requisite know ledge to successfully perform and complete such w ork in a timely manner.”

There are no other changes by reason of this amendment.

1. CONTRACT ID CODE PAGE OF PAGES

Y 1 19

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 19-Mar-2024

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

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

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X W900KK24R0002

X 9B. DATED (SEE ITEM 11)

08-Mar-2024

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offer 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 1 copies of the amendment; (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 APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) 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 date, 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.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

19-Mar-2024

CODE

ARMY CONTRACTING COMMAND - ORLANDO

ATTN: ALPHA DIVISION

12211 SCIENCE DRIVE

ORLANDO FL 32826-3224

W900KK 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W900KK24R0002

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION I - CONTRACT CLAUSES

The following included by full text have been revised:

252.211-7003 ITEM UNIQUE IDENTIFICATION AND VALUATION (JAN 2023)

(a) Definitions. As used in this clause-

Automatic identification device means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media.

Concatenated unique item identifier means--

(1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or

(2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code; enterprise identifier; original part, lot, or batch number;

and serial number within the original part, lot, or batch number.

Data Matrix means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error Checking and Correction 200 (ECC200) specification found within International Standards Organization (ISO)/International Electrotechnical Commission

(IEC) 16022.

Data qualifier means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows.

DoD recognized unique identification equivalent means a unique identification method that is in commercial use and has been recognized by DoD. All DoD recognized unique identification equivalents are listed at https://www.acq.osd.mil/asda/dpc/ce/ds/unique-id.html.

DoD item unique identification means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier; the original part, lot, or batch number; and the serial number.

Enterprise means the entity (e.g., a manufacturer or vendor) responsible for assigning unique item identifiers to items.

Enterprise identifier means a code that is uniquely assigned to an enterprise by an issuing agency.

Government's unit acquisition cost means--

(1) For fixed-price type line, subline, or exhibit line items, the unit price identified in the contract at the time of delivery;

(2) For cost-type or undefinitized line, subline, or exhibit line items, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery; and

(3) For items produced under a time-and-materials contract, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery.

Issuing agency means an organization responsible for assigning a globally unique identifier to an enterprise, as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.aimglobal.org/?Reg_Authority15459.

Issuing agency code means a code that designates the registration (or controlling) authority for the enterprise identifier.

Item means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts.

Lot or batch number means an identifying number assigned by the enterprise to a designated group of items, usually referred to as either a lot or a batch, all of which were manufactured under identical conditions.

Machine-readable means an automatic identification technology media, such as bar codes, contact memory buttons, radio frequency identification, or optical memory cards.

Original part number means a combination of numbers or letters assigned by the enterprise at item creation to a class of items with the same form, fit, function, and interface.

Parent item means the item assembly, intermediate component, or subassembly that has an embedded item with a unique item identifier or DoD recognized unique identification equivalent.

Serial number within the enterprise identifier means a combination of numbers, letters, or symbols assigned by the enterprise to an item that provides for the differentiation of that item from any other like and unlike item and is never used again within the enterprise.

Serial number within the part, lot, or batch number means a combination of numbers or letters assigned by the enterprise to an item that provides for the differentiation of that item from any other like item within a part, lot, or batch number assignment.

Serialization within the enterprise identifier means each item produced is assigned a serial number that is unique among all the tangible items produced by the enterprise and is never used again. The enterprise is responsible for ensuring unique serialization within the enterprise identifier.

Serialization within the part, lot, or batch number means each item of a particular part, lot, or batch number is assigned a unique serial number within that part, lot, or batch number assignment. The enterprise is responsible for ensuring unique serialization within the part, lot, or batch number within the enterprise identifier.

Type designation means a combination of letters and numerals assigned by the Government to a major end item, assembly or subassembly, as appropriate, to provide a convenient means of differentiating between items having the same basic name and to indicate modifications and changes thereto.

Unique item identifier means a set of data elements marked on items that is globally unique and unambiguous. The term includes a concatenated unique item identifier or a DoD recognized unique identification equivalent.

Unique item identifier type means a designator to indicate which method of uniquely identifying a part has been used. The current list of accepted unique item identifier types is maintained at https://www.acq.osd.mil/asda/dpc/ce/ds/unique-id.html.

(b) The Contractor shall deliver all items under a contract line, subline, or exhibit line item.

(c) Unique item identifier. (1) The Contractor shall provide a unique item identifier for the following:

(i) Delivered items for which the Government's unit acquisition cost is $5,000 or more, except for the following line items:

Contract line, subline, or exhibit line item No. Item description

(ii) Items for which the Government's unit acquisition cost is less than $5,000 that are identified in the Schedule or the following table:

Contract line, subline, or exhibit line item No. Item description

(If items are identified in the Schedule, insert “See Schedule” in this table.)

(iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment Number ----.

(iv) Any item of special tooling or special test equipment as defined in FAR 2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number ----.

(v) Any item not included in paragraphs (c)(1)(i), (ii), (iii), or

(iv) of this clause for which the contractor creates and marks a unique item identifier for traceability.

(2) The unique item identifier assignment and its component data element combination shall not be duplicated on any other item marked or registered in the DoD Item Unique Identification Registry by the contractor.

(3) The unique item identifier component data elements shall be marked on an item using two dimensional data matrix symbology that complies with ISO/IEC International Standard 16022, Information technology--International symbology specification--Data matrix; ECC200 data matrix specification.

(4) Data syntax and semantics of unique item identifiers. The Contractor shall ensure that--

(i) The data elements (except issuing agency code) of the unique item identifier are encoded within the data matrix symbol that is marked on the item using one of the following three types of data qualifiers, as determined by the Contractor:

(A) Application Identifiers (AIs) (Format Indicator 05 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.

(B) Data Identifiers (DIs) (Format Indicator 06 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.

(C) Text Element Identifiers (TEIs) (Format Indicator 12 of ISO/IEC International Standard 15434), in accordance with the Air Transport Association Common Support Data Dictionary; and

(ii) The encoded data elements of the unique item identifier conform to the transfer structure, syntax, and coding of messages and data formats specified for Format Indicators 05, 06, and 12 in ISO/IEC International Standard 15434, Information Technology-Transfer Syntax for High Capacity Automatic Data Capture Media.

(5) Unique item identifier.

(i) The Contractor shall--

(A) Determine whether to--

(1) Serialize within the enterprise identifier;

(2) Serialize within the part, lot, or batch number; or

(3) Use a DoD recognized unique identification equivalent (e.g. Vehicle Identification Number); and

(B) Place the data elements of the unique item identifier (enterprise identifier; serial number; DoD recognized unique identification equivalent; and for serialization within the part, lot, or batch number only: Original part, lot, or batch number) on items requiring marking by paragraph (c)(1) of this clause, based on the criteria provided in MIL- STD-130, Identification Marking of U.S. Military Property, latest version;

(C) Label shipments, storage containers and packages that contain uniquely identified items in accordance with the requirements of MIL-STD-129, Military Marking for Shipment and Storage, latest version; and

(D) Verify that the marks on items and labels on shipments, storage containers, and packages are machine readable and conform to the applicable standards. The contractor shall use an automatic identification technology device for this verification that has been programmed to the requirements of Appendix A, MIL-STD-130, latest version.

(ii) The issuing agency code--

(A) Shall not be placed on the item; and

(B) Shall be derived from the data qualifier for the enterprise identifier.

(d) For each item that requires item unique identification under paragraph (c)(1)(i), (ii), or (iv) of this clause or when item unique identification is provided under paragraph (c)(1)(v), in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the Contractor shall report at the time of delivery, as part of the Material Inspection and Receiving Report, the following information:

(1) Unique item identifier.

(2) Unique item identifier type.

(3) Issuing agency code (if concatenated unique item identifier is used).

(4) Enterprise identifier (if concatenated unique item identifier is used).

(5) Original part number (if there is serialization within the original part number).

(6) Lot or batch number (if there is serialization within the lot or batch number).

(7) Current part number (optional and only if not the same as the original part number).

(8) Current part number effective date (optional and only if current part number is used).

(9) Serial number (if concatenated unique item identifier is used).

(10) Government's unit acquisition cost.

(11) Unit of measure.

(12) Type designation of the item as specified in the contract schedule, if any.

(13) Whether the item is an item of Special Tooling or Special Test Equipment.

(14) Whether the item is covered by a warranty.

(e) For embedded subassemblies, components, and parts that require DoD unique item identification under paragraph (c)(1)(iii) of this clause, the Contractor shall report as part of, or associated with, the Material Inspection and Receiving Report specified elsewhere in this contract, the following information:

(1) Unique item identifier of the parent item under paragraph (c)(1) of this clause that contains the embedded subassembly, component, or part.

(2) Unique item identifier of the embedded subassembly, component, or part.

(3) Unique item identifier type.**

(4) Issuing agency code (if concatenated unique item identifier is used).**

(5) Enterprise identifier (if concatenated unique item identifier is used).**

(6) Original part number (if there is serialization within the original part number).**

(7) Lot or batch number (if there is serialization within the lot or batch number).**

(8) Current part number (optional and only if not the same as the original part number).**

(9) Current part number effective date (optional and only if current part number is used).**

(10) Serial number (if concatenated unique item identifier is used).**

(11) Description.

** Once per item.

(f) The Contractor shall submit the information required by paragraphs (d) and (e) of this clause as follows:

(1) End items shall be reported using the receiving report capability in Wide Area WorkFlow (WAWF) in accordance with the clause at 252.232-7003. If WAWF is not required by this contract, and the contractor is not using WAWF, follow the procedures at http://dodprocurementtoolbox.com/site/uidregistry/.

(2) Embedded items shall be reported by one of the following methods--

(i) Use of the embedded items capability in WAWF;

(ii) Direct data submission to the IUID Registry following the procedures and formats at http://dodprocurementtoolbox.com/site/uidregistry/; or

(iii) Via WAWF as a deliverable attachment for exhibit line item number (fill in) ----, Unique Item Identifier Report for Embedded Items, Contract Data Requirements List, DD Form 1423.

(g) Subcontracts. If the Contractor acquires by subcontract any item(s) for which item unique identification is required in accordance with paragraph (c)(1) of this clause, the Contractor shall include this clause, including this paragraph (g), in the applicable subcontract(s), including subcontracts for commercial products or commercial services.

(End of clause)

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS, CONDITIONS

SECTION L - SUBMISSION INSTRUCTIONS

L.1 GENERAL INFORMATION

a. Proposals shall be compliant with the full solicitation requirements and instructions contained within this section.

Offerors are required to comply with all requirements stated herein.

OFFERORS ARE HEREBY ON NOTICE THAT FAILURE TO SUBMIT ALL THE REQUIRED PROPOSAL

INFORMATION IN EXACTLY THE MANNER (TIMELINESS AND FORMAT) AS SPECIFIED IN THE

SOLICITATION MAY CONSTITUTE A BASIS FOR THE GOVERNMENT TO REJECT A PROPOSAL AS

NON-COMPLIANT AND THEREFORE INELIGIBLE TO BE CONSIDERED FOR AWARD, AT THE SOLE

DISCRETION OF THE PROCURING CONTRACTING OFFICER (PCO).

b. The primary North American Industry Classification System (NAICS) code for this solicitation is 333310, Other Commercial and Service Industry Machinery Manufacturing. The size standard for NAICS 333310 is up to 1,000 employees.

c. In accordance with FAR 52.215-1, Instructions to Offerors - Competitive Acquisition, the Government intends to make award without discussions However, if the PCO determines that discussions are necessary, then discussions may be held with each Offeror in the competitive range IAW FAR 15.306(d) and 15.307(b). The decision to hold discussions is purely at the discretion of the PCO.

d. The Offerors shall ensure that each proposal volume submitted contains only the information relevant to that specific volume. The Offerors are cautioned that each volume of the proposal will be evaluated standalone against the criteria set forth in Section M and the evaluators for one volume may be different than the evaluators of another volume. It is incumbent upon the Offerors to ensure they properly submit their proposals. If the data is not contained in the appropriate volume of the proposal, it will not be evaluated. For example, if Past Performance narratives are submitted under the Technical Volume rather than the volume specified, the proposal will be evaluated as if no Past Performance narratives were submitted at all.

e. Any data previously submitted in response to another solicitation, whether submitted to the Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI), Army Contracting Command-Orlando (ACC- ORL) or another agency, should be assumed to be unavailable during this source selection process. Proposal data shall not be incorporated into the proposal by referring to another proposal or other source.

f. Proposal shall not contain any classified information.

g. An Offeror’s submission of a proposal in response to this solicitation constitutes approval for disclosure of proprietary information contained within the proposal to non-government participants involved in the source selection. If the contractor is not willing to provide this consent, written notification to the PCO is required no later than 15 days prior to the proposal due date.

h. Alternate proposals are not acceptable.

i. The Government will not reimburse Offerors for any cost incurred for the preparation and submission of a proposal in response to this RFP.

j. All proposal information is subject to verification by the Government. Falsification of any proposal submission, documents, or statements may subject the Offeror to civil or criminal prosecution under Section 1001 of Title 18 of the United States Code.

k. Should an Offeror indicate in its proposal that it cannot or will not meet any contract requirement; or include data which prompts the Government to question the Offeror's compliance with contract requirements, the Government may determine at its discretion that the Offeror's proposal is non-compliant and therefore ineligible for award.

l. The proposal shall be valid for 180 calendar days from date of initial proposal submission. The Offeror shall insert the validity date in Block 12 of the SF 33.

m. The Government intends to make multiple awards against this solicitation. The Government anticipates awarding the resulting contracts by 1st Quarter, Fiscal Year 2025.

n. The proposal is due 30 days from the solicitation issued date.

L.1.1 SOLICITATION QUESTIONS

a. All questions regarding the RFP shall be submitted in writing via email to the PCO (Roberto.J.GotayGarcia.civ@army.mil) and the Contract Specialist (Helen.G.Simpson2.civ@army.mil) within 15 calendar days after the RFP is published. Subject of the email shall state “Questions - RFP W900KK24R0002, LTRaC MAC 2.” Offerors shall submit questions using RFP Section J, Attachment 3, Solicitation Question / Comment Form.

b. No phone inquiries regarding the RFP will be received or acknowledged.

c. Offerors will receive an acknowledgement of their question via response to the email submission.

d. The Government will answer all inquiry items via an Amendment to the RFP and post to the System for Award Management (SAM) website (SAM.gov) under the RFP number. Offerors are cautioned not to include proprietary information in the questions because the Government may release it to all Offerors.

e. Answers will be posted without Offeror identification. The Government will not provide responses to questions that would reveal a potential Offeror’s confidential business strategy, technical solution, or any information that is considered unique to a particular Offeror. Questions received after the deadline may not be answered.

L.2 PROPOSAL SUBMISSION REQUIREMENTS

L.2.1 DELIVERY OF PROPOSALS

Proposals shall be submitted only by email to Mr. Roberto GotayGarcia, Contracting Officer, Roberto.J.GotayGarcia.civ@army.mil, AND Ms. Helen G. Simpson, Contract Specialist, Helen.G.Simpson2.civ@army.mil. The subject of each email shall be "W900KK24R0002 – LTRaC MAC 2 Proposal”, Email XX of XXX. Emails shall be numbered to include total sent, for example “Email 2 of 6”. Each attachment within an email shall be numbered to ensure all attachments are received, for example “Attachment 3 of 4”.

L.2.2 FORMAT

a. The Offeror must present its proposal information in a manner that facilitates a one-to-one comparison between the information presented and this Proposal’s Instruction. Proposal information must be structured such that its paragraph number / letter is identical to the Proposal Instructions paragraph number to which it is responding, although the Offeror may add lower tier subparagraphs. The Offeror must provide reasons it will not provide information for a particular paragraph. Any pages that are changed as a result proposal revisions shall be of a different color and have changed information clearly marked by a vertical line in the right margin of the page. The revised pages shall be dated.

b. All files on each volume shall be directly supported by Microsoft Office (MS) 365 and verified to be free of any virus or malware. Data submitted in spreadsheet / workbook format shall be readable by MS Office 365. All files shall be clearly identified with a filename appropriate to the content. Please note, self-extracting ".exe" files are not acceptable.

c. The proposal shall use no smaller than industry standard word processor 12-point proportional font utilizing Arial font. Font size for tables and figures shall be no smaller than 8-point. Use at least 1-inch margins on the top, bottom, left, and right-side margins. Pages shall be numbered sequentially by volume and marked with the Offeror’s name and any applicable data use restrictions as specified in FAR 52.215-1(e). If there are more pages than specified below, the additional pages will be removed from the back of the particular volume and / or individual paper and will not be evaluated.

L.3 PROPOSAL VOLUMES

a. The proposal must consist of Volumes I through III, as follows:

- Volume I: Factor 1 - Technical

- Volume II: Factor 2 - Past Performance

- Volume III: Contracting information

b. The titles and contents of the volumes and books shall be as defined in Table L.1 below:

Table L.1 Volume Titles and Contents

VOLUME VOLUME TITLE PAGE LIMIT

I Factor 1 - Technical 10

II Factor 2 - Past Performance 15

III Contracting Information Unlimited

c. For Past Performance, Letters of Consent and Commitment, Cure Notices, Show Cause Letters, Table of contents, and Summary Sections are excluded from the page count.

L.3.1 VOLUME I: FACTOR 1 - TECHNICAL

Background: MAC 2 is intended to provide the US Army and Marine Corps with a contract vehicle, with a hardware centric focus, needed to perform less-complex Continuous Technology Refreshments (CTRs), modernizations, upgrades, and other less-complex efforts on instrumentation (hardware with integrated software) fielded to Live Training Ranges. Live Training Ranges include the Combat Training Centers and Home Station Ranges around the world.

L.3.1.1 – TECHNICAL SUBFACTORS

The Technical Factor contains two subfactors. The Offeror shall comply with both subfactors’ instructions.

L.3.1.1.1 – TECHNICAL SUBFACTOR 1: LIVE TRAINING RANGE DESCRIPTION

The Offeror shall describe how their products are or could be integrated onto and support Live Training Range Instrumentation related to at least one of the following programs:

a. Future Army System of Integrated Targets (FASIT)

b. Digital Range Training System (DRTS)

c. Homestation Instrumentation Training System (HITS)

d. Joint Pacific Multi-National Readiness Capability - Instrumentation System (JPMRC-IS)

e. Combat Training Centers - Instrumentation Systems (CTC-IS)

f. Synthetic Training Environment - Live Training Systems (STE - LTS)

g. Aviation instrumentation efforts

h. Radio frequency player units with voice, video, or data feeds, at any of the CTCs, DRTS, HITS, or JPMRC

i. United States Marine Corps’ Range Instrumentation System Controller - Training (RISCON-T) and other live ranges

L.3.1.1.2 – TECHNICAL SUBFACTOR 2: LIVE TRAINING RANGE WORK APPROACH

The Offeror shall describe their approach having performed, performing, or how they would perform a technology refreshment, technology insertion, modernization, or other work related to Live Training Range Instrumentation.

The Offeror’s approach shall address at least FOUR of the following areas:

a. Design

b. Development

c. Production / procurement of equipment

d. Integration onto the range

e. Contractor testing and Government testing

f. Fielding

g. Developing documentation

h. New Equipment Training

i. Risk / challenges / issues encountered on Live Training Ranges

j. Schedule constraints on Live Training Ranges

L.3.2 VOLUME II: FACTOR 2 - PAST PERFORMANCE

This volume shall contain recent Past Performance information that is relevant in scope to the appropriate Factor 1, Technical. Relevant scope is defined under the RFP Section M. Offerors shall submit a list of no more than three (3) contracts on which the Offeror served as either the prime contractor, a subcontractor, or as part of a Joint Venture, in performance and / or completed during the past five (5) years from the issue date of this solicitation.

This volume shall be organized into the following sections:

L.3.2.1 SECTION 1 - CONTRACT DESCRIPTION

This section shall include the following information in the following format:

a. Contractor / Subcontractor place of performance, CAGE Code DUNS Number and / or SAM UEI. 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’s organization (name, and current address, email address, telephone, and fax numbers).

b. Government contracting activity, and current address, Procuring Contracting Officer’s name, email address, telephone, and fax numbers.

c. Government’s technical representative / Contracting Officer’s Representative and current email address, telephone, and fax numbers.

d. Government contract administration activity and the Administrative Contracting Officer’s name, and current email address, telephone, and fax number.

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, General Services Administration (GSA) contracts, and Blanket Purchase Agreements, include Delivery Order Numbers.

g. Contract Type (specific type such as Fixed-Price (FP), Cost Reimbursement (CR), Time & Material (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 or work.

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

L.3.2.2 SECTION 2 – PERFORMANCE

Offerors shall provide a specific narrative explanation of each contract listed in Section 1, Contract Description, describing the objectives achieved and detailing how the effort is relevant to the requirement of this RFP in terms of scope, magnitude, and complexity. Merely stating that the submitted effort is relevant in scope, magnitude, or complexity may deem the submitted contract as not relevant 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 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.

L.3.2.3 PAST PERFORMANCE QUESTIONNAIRE

For all contracts identified in Section 1, Contract Descriptions, a Performance Assessment Questionnaire (RFP Section J, Attachment 2) must be completed and submitted. The Offeror shall complete Part I of the Past Performance Questionnaire and email the questionnaire to Mr. Roberto J. GotayGarcia, Contracting Officer, Roberto.J.GotayGarcia.civ@army.mil, AND Ms. Helen G. Simpson, Contract Specialist, Helen.G.Simpson2.civ@army.mil. The POC for the Government contracting activity and the technical representative shall be instructed to electronically complete Part II of the questionnaire and email the entire questionnaire to the Contracting Officer and Contract Specialist listed above no later than the proposal due date. The Offeror shall submit within Volume IV (Past Performance) a list of all the POCs who were sent a questionnaire. 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 Email Address; and Date Email to POC (month / day).

L.3.2.4 SUBMISSIONS

Offerors are discouraged from providing points of contact with another contractors’ facility, i.e., in case an Offeror (or one of his / her team members) is in a subcontract with another contractor who has submitted a proposal on the same requirement. Offerors shall provide and submit the prime contract number and all Governmental agency POCs in lieu of subcontract numbers or prime contract POCs in situations as described above.

L.3.2.5 GOVERNMENT INFORMATION SOURCES

The Government will use information submitted by the Offeror and is free to use other sources such as other Federal Government offices, databases, and commercial sources, to assess past performance. Offerors are strongly cautioned that if the Government is unable to contact past performance references directly associated to any survey; or in the case past performance information is not entered into the Contractor Performance Assessment Reporting System (CPARS) database; or if no record of past performance is available for the project, the Offeror will not be evaluated favorably or unfavorably but will be rated as neutral confidence on past performance for that project.

L.3.2.6 GOVERNMENT’S RIGHT TO USE NON-PROPOSAL INFORMATION

If the Government identifies any recent, relevant contracts not included in the Offeror’s Past Performance volume, the Government reserves the right to include Past Performance information from those contracts in its evaluation.

L.3.3 VOLUME III: CONTRACTING INFORMATION

Offerors shall provide a summary sheet comprised of the information listed below for their entity and each entity identified as a Joint Venture Team Member in the proposal.

a. Business Name

b. Address

c. Principal point of contact for this RFP (Name, title, phone number, email)

d. Secondary point of contact for this RFP (Name, title, phone number, email)

e. Individuals authorized to negotiate with the Government and contractually bind the Offeror (Name, title, phone number, email)

f. Establishment Taxpayer Identification Number (TIN)

g. TIN of Parent Corporation (if applicable)

h. DUNS and / or SAM UEI

i. CAGE code

j. Business size for this effort (large or small)

L.3.3.1 CONTRACTOR’S AUTHORIZED CONTRACT COORDINATOR AND TECHNICAL LIAISON

The contractor shall state below the name and telephone numbers of the contractor’s employees responsible for coordination of contract functions / liaison with the Contracting Officer and / or Contract Specialist, and providing technical assistance as required regarding product specifications, functionality, etc.

CONTRACT COORDINATOR

NAME:

PHONE (BUS):

PHONE (AFTER HOURS):

ALTERNATE

NAME:

PHONE (BUS):

PHONE (AFTER HOURS):

The contractor shall notify the Contracting Officer and / or Contract Specialist in advance, in writing, of any changes in the above listed personnel.

L.3.3.2 JOINT VENTURES

If proposing as a Joint Venture, the Offeror shall provide copies of any approved Joint Venture agreements or Joint Venture agreements submissions not yet approved. Additionally, the Offeror shall clearly indicate if it is proposing as a Populated or Unpopulated Joint Venture, as defined in 13 CFR 124.513.

L.3.3.3 GOVERNMENT AGENCY INFORMATION

Provide the mailing address, telephone, fax numbers, email address, and facility codes for the Offeror’s local Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office. In addition, provide the name, telephone number, fax number, and email address for the Administrative Contracting Officer (ACO) at DCMA.

L.3.3.4 STANDARD FORM 33

The Offeror shall provide a completed and signed SF33. Any amendments to the solicitation shall be acknowledged and accepted. Exceptions, deviations, and waivers to the solicitation will not be accepted with the proposal. If an

Offeror has any issues with the terms and conditions of the solicitation, they shall notify the PCO no later than 15 days prior to the proposal due date.

L.3.3.5 REPRESENTATIONS, CERTIFICATION AND OTHER STATEMENTS OF OFFERORS

Offerors shall provide a complete copy of all certifications within SAM.gov and all additional certifications found in Section K of the RFP. Negative responses are required. If utilizing SAM, Offerors are reminded to complete all certifications annotated in SAM for completion based on individual acquisitions prior to proposal submission.

Offerors shall provide the certification at DFARS 252.227-7017 and 252.227-7028, Identification and Assertion of Use, Release or Disclosure Restrictions as it applies to the basic ID/IQ contract. Offerors asserting that any product is a commercial product must ensure that the product is a commercial item as defined in FAR 2.101 and provide evidence that the commercial item has been purchased by the public or non-governmental entities for purposes other than governmental. This evidence may be in the form of Purchase Orders, Contracts, or the equivalent.

L.3.3.6 ACCOUNTING SYSTEM COMPLIANCES

The Offeror shall submit contact information (name, telephone number and email address) for their cognizant DCMA ACO and cognizant DCAA supervisory auditor. If the Offeror is not assigned to DCMA for contract administration or is not assigned to DCAA for contract audit, the Offeror will identify their cognizant federal agency or agencies (and include the individual contact information). The Offeror shall submit a copy of the most recent ACO letter regarding the status of their accounting system. If that letter is more than a year old and the Offeror has a more current DCAA audit report commenting on the status of their accounting system, a copy of that report shall also be submitted. If the Offeror's accounting system was disapproved or deemed to be not adequate, the Offeror shall identify all deficiencies along with steps taken, or to be taken, to correct the deficiencies and a timeline to include audit by the cognizant audit agency after corrective action has been implemented. If the Offeror's accounting system has never been audited by their cognizant federal audit agency, the Offeror shall state so.

If the Offeror does not have an approved accounting system, the Offeror shall complete RFP Section J, Attachment 4 – Pre-Award Survey of Prospective Contractor Accounting System Checklist and return the documentation as part of the Contracting Information Volume of the proposal.

Please note, while an approved accounting system is not required at the time of proposal submission, it is required at time of award of a Delivery/Task Order with a Cost Contract Line Item Number (CLIN). If an otherwise successful Offeror does not have an approved accounting system at the time of award of an Order with a Cost CLIN, the Offeror will not be awarded that Order. A Contractor cannot receive Progress Payments for a Firm Fixed Price Order until DCMA determines the Contractor’s accounting system and controls adequate for proper administration of progress payments.

L.3.3.7 DISCLOSURE OF POTENTIAL CONFLICT OF INTEREST BY OFFERORS

a. The Offeror agrees to disclose, in writing and prior to the closing date for receipt of offers, any relevant facts pertaining to work previously performed or presently being performed by the Offeror under private and Government contracts wherein the subject matter includes systems, components, technology, or services identical or similar to that encompassed by the proposed contract and which might give rise to the appearance of an organizational conflict of interest. Such disclosure shall set forth all relevant facts including identification of contracts under which work was or is being performed.

b. If any of the contracts identified pursuant to subparagraph a. above contain an Organizational Conflict of Interest Provision, the Offeror may request a waiver of that provision and propose contractual safeguards or job procedures to mitigate conflicting roles that might produce an Organizational Conflict of Interest.

c. Any documentation submitted pursuant to this subparagraph shall identify this procurement by RFP or other appropriate number as a reference and shall be forwarded to the Contracting Officer:

Roberto J. GotayGarcia

U.S. Army Contracting Command-Orlando Alpha Division, CCOR-CDD-A 12211 Science Drive, Orlando, FL 32826-3224 E-mail: Roberto.J.GotayGarcia.civ@army.mil

d. The Contracting Officer will determine whether such interests or contracts present potential organizational conflicts of interest that should preclude award to the Offeror.

L3.3.8 STATEMENT OF COMPLIANCE

Offerors shall include a statement indicating complete compliance with the solicitation or detailed analysis of any objections, exceptions, contingencies, or additions. Any objection, exception, contingency, or addition shall be cross-referenced to the applicable solicitation paragraph(s). As part of this letter, an authorized official shall sign certifying the following:

“Regardless of the involvement in evaluations, all requirements of the Base Contract SOW will be met.”

L.3.3.9 PROPERTY MANAGEMENT PLAN

In accordance with paragraph (f) of FAR 52.245-1, Government Property, and DFARS 252.245-7003, Contractor Property Management System Administration, the Offeror shall provide the Government with a property management plan. When applicable, the plan shall be implemented at the order, program, site, or entity level. The plan shall include the following (not all-inclusive list) and shall delineate and provide the rationale for how the Offeror will manage the property.

a. Acquisition of property documentation

b. Receipt of Government property

c. Government-furnished property

d. Contractor-acquired property

e. Records of Government property

f. Use of a Receipt and Issue System for Government materiel

g. Physical inventory

SECTION M - EVALUATION FACTORS FOR AWARD

The following have been modified:

M.1 BASIS FOR AWARD

a. This solicitation is for the award of the LTRaC MAC 2.

b. Multiple awards may be made as a result of this RFP. In accordance with FAR 15.304(c)(1)(ii), which permits MACs to exclude price/cost as an evaluation factor under certain conditions, the Government intends to make a MAC award to each qualifying Offeror who is a responsible source and submits an acceptable proposal that conforms to the requirements of this solicitation. For the purposes of this RFP, an acceptable proposal is a proposal that is rated as “Acceptable” under the Technical Factor and the Past Performance Factor. Ratings and descriptions are outlined in Table M.1.

c. The Government intends to award contracts without discussions. Initial proposals must contain the best approach / proposal. The Government may conduct clarifications as described in FAR 15.306. The Government reserves the right to conduct discussions in accordance with FAR 15.306, if determined necessary.

d. To be eligible for future LTRaC MAC 2 Delivery Order or Task Order awards, the Offeror must be an LTRaC MAC 2 awardee.

M.2 EVALUATION FACTORS

This is a FAR Part 15 competitive acquisition for a multiple award IDIQ contract, utilizing the Acceptable/Unacceptable rating scheme. The following evaluation factors will be used to evaluate each proposal:

- Factor 1 - Technical

- Factor 2 - Past Performance

Offerors must receive a rating of “Acceptable” in Factor 1 and Factor 2 to be considered for award.

M.3 EVALUATION APPROACH

M.3.1 FACTOR 1 - TECHNICAL

For the Technical Factor, a Technical Rating of “Acceptable” or “Unacceptable” will be assigned to each Offeror based on the Offeror’s proposal’s compliance with the evaluation criteria. Ratings and descriptions are provided in Table M.1.

Table M.1. Technical Acceptable / Unacceptable Rating Method Adjectival Rating Description

Acceptable Proposal meets the requirements of the solicitation

Unacceptable Proposal does not meet the requirements of the solicitation

To receive an “Acceptable” rating in this factor, the Offeror’s proposal must receive an acceptable rating in both subfactors. The Government will evaluate the proposal’s compliance with each technical subfactor.

M.3.1.1 TECHNICAL SUBFACTOR 1: INSTRUMENTATION INTEGRATION

To receive an “Acceptable” rating in this subfactor, the Offeror shall describe how their products are or could be integrated onto and support Live Training Range Instrumentation related to at least one of the following programs:

a. Future Army System of Integrated Targets (FASIT)

b. Digital Range Training System (DRTS)

c. Homestation Instrumentation Training System (HITS)

d. Joint Pacific Multi-National Readiness Capability - Instrumentation System (JPMRC-IS)

e. Combat Training Centers - Instrumentation Systems (CTC-IS)

f. Synthetic Training Environment - Live Training Systems (STE - LTS)

g. Aviation instrumentation efforts

h. Radio frequency player units with voice, video, and data feeds, at any of the CTCs, DRTS, HITS, or JPMRC

i. United States Marine Corps’ Range Instrumentation System Controller - Training (RISCON-T) and other live ranges

The Offeror’s description shall demonstrate that they have the requisite knowledge to successfully perform and complete such work in a timely manner.

M.3.1.2 TECHNICAL SUBFACTOR 2: LIVE TRAINING RANGE WORK APPROACH

To receive an “Acceptable” rating in this subfactor, the Offeror shall describe their approach having performed, performing, or how they would perform a technology refreshment, technology insertion, modernization, or other work related to Live Training Range Instrumentation. The Government will evaluate that at least FOUR of the following areas are addressed:

a. Design

b. Development

c. Production / procurement of equipment

d. Integration onto the range

e. Contractor testing and Government testing

f. Fielding

g. Developing documentation

h. New Equipment Training

i. Risk / challenges / issues encountered on Live Training Ranges

j. Schedule constraints on Live Training Ranges

The Offeror’s description shall demonstrate that they have the requisite knowledge to successfully perform and complete such work in a timely manner.

M.3.2 FACTOR 2 - PAST PERFORMANCE

a. The Government will evaluate the Offeror’s past performance to assess the Offeror’s probability of meeting the solicitation requirements. The past performance evaluation considers the Offeror’s demonstrated recent and relevant record of performance in supplying products and services that meet the contract’s requirements. In accordance with FAR 15.305(a)(2), the recency and relevancy of the information, source of the information, context of the data, and general trends in contractor’s performance will be considered. Past performance will be rated on an acceptable or unacceptable basis using the ratings in Table M.2.

NOTE: Offeror refers to the proposed prime contractor, joint venture entity, affiliate / subsidiary / parent company.

Table M.2. Past Performance Acceptable / Unacceptable Rating Method

Acceptable Based on the Offeror’s performance record, the Government has a reasonable expectation that the Offeror will successfully perform the required effort, or the Offeror’s performance record is unknown.

Unacceptable Based on the Offeror’s performance record, the Government does not have a reasonable expectation that the Offeror will be able to successfully perform the required effort.

b. The Government will evaluate how well an Offeror has performed similar work before. The relevancy of the information, source of the information, context of the data, and general trends in contractor’s performance will be considered. However, only performance on Recent and Relevant contracts will be considered in the evaluation.

c. There are three aspects to the past performance evaluation, which the Government will evaluate in the following order:

1. Recency

2. Relevancy (including context of data), and

3. Quality (including general trends in contractor performance and source of information).

Recency. Recency is the time period during which past performance references are considered relevant and is critical to establishing the relevancy of past performance information. Past Performance within five (5) years prior to the solicitation release date will be considered recent past performance for the purposes of this solicitation.

Relevancy. The Government will assess for relevant past performance in terms of scope.

For LTRaC MAC 2, relevant in scope means contracts performing work on the…