A0001_W9115124R0030_issued 13Nov2024.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

The subject solicitation is amended to: correct Period of Performance dates at Section F, update/replace identif ied solicitation Attachments at Section J, and to replace Sections L and M, as identif ied herein.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 47

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

16C. DATE SIGNED

BY 13-Nov-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 W9115124R0030

X 9B. DATED (SEE ITEM 11)

24-Oct-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

13-Nov-2024

CODE

MICC-FORT CAVAZOS WSMR BRANCH

143 CROZIER ST.

WHITE SANDS MISSILE RANGE NM 88002

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W9115124R0030

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

CONTINUATION SHEET FOR A0001

Amendment 0001 (A0001) is hereby issued to change the following RFP information and requirements “FROM / TO” for each applicable paragraph as shown below. The corresponding Request for Information (RFI) number as posted to the sam.gov notice for this solicitation is referenced to each paragraph change or revision. Duplicate RFIs are not identified herein.

For clarity purposes, a complete replacement of Sections L and M is incorporated into A0001 as well.

FROM:

L.2.4.1 Format. The submission shall be clearly indexed and logically assembled. 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 RFP number in the header and/or footer. A Table of Contents should be created using the Table of Content feature in MS Word. MS Word (doc) files shall use the following page setup parameters:

Margins – Top, Bottom, Left, Right – 1” Gutter – 0” From Edge – Header, Footer 0.5” Page Size, Width – 8.5” Page Size, Height – 11”

TO (see RFI 3):

L.2.4.1 Format. The submission shall be clearly indexed and logically assembled. 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 date and RFP number in the header and/or footer. A Table of Contents should be created using the Table of Content feature in MS Word. MS Word (doc) files shall use the following page setup parameters:

Margins – Top, Bottom, Left, Right – 1” Gutter – 0” From Edge – Header, Footer 0.5” Page Size, Width – 8.5”

Page Size, Height – 11”

FROM:

L.2.4.3 Packaging. All proposal files shall be compressed (zipped) into one file entitled proposal zip using WinZip version 6.2 or later, or as separate uploads in their native format, i.e., doc, xls, ppt, etc. In addition, each file shall be converted to a read-only PDF (note, in the event the native and PDF file differ, the Government will utilize the PDF file for evaluation). All price breakdown information to aide in the cost/price evaluation shall be submitted in Microsoft Office Excel Read/Write format and viewable in Microsoft Excel 2013. **Please note – Self extracting exe files are not acceptable.

TO (see RFI 69):

L.2.4.3 Packaging. All proposal files shall be uploaded in their native format, i.e., doc, xls, ppt, etc. In addition, each file shall be converted to a read-only PDF (note, in the event the native and PDF file differ, the Government will utilize the PDF file for evaluation). All price breakdown information to aide in the cost/price evaluation shall be submitted in Microsoft Office Excel Read/Write format and viewable in Microsoft Excel 2013. **Please note – Self extracting exe files are not acceptable. Each proposal Volume shall be packaged so as to not exceed the email size limitations at L.2.2.2.

FROM:

L.2.5.1 Company logos, pictures or information otherwise that provide company identification or personnel shall NOT be included in Volume I. Additionally, Volume I shall not contain any pictures that identify company or Government personnel. Finally, no quotes or statements made by Government personnel in prior acquisition efforts shall be contained in Volume I.

TO (see RFI 3):

L.2.5.1 Volume I and contents within proposal pages (to include screen shots and/or read-only link data in support of L.3.1.1.5), including appendices, Table of Contents, Title Pages, Glossary, Dividers/Tabs, Blank pages and throughout the digital copies of the Technical / Mission Capability Volume of the proposal shall not contain company logos and/or names, pictures or any information that indicates the Offeror’s (to include all team members) identification or personnel. The Technical / Mission Capability Volume shall not contain any pictures that identify Offeror personnel or Government personnel. No quotes or statements made by Government personnel in prior acquisition efforts shall be contained within Volume I of the Offeror’s proposal. Each proposal Volume (I-Technical / Mission Capability, II-Past Performance, III-Cost / Price, IV- Solicitation, Offer and Award Documents, and Certifications / Representations) shall be submitted as a separate Volume file, and IAW instructions at L.2.2 and its subparts.

FROM:

L.2.5.2 Each Volume of the proposal shall consist of a Title Page (excluded from page limitations at L.2.3), Table of Contents (excluded from page limitations at L.2.3), Summary Section, and the Narrative discussion. The Summary Section shall contain a brief abstract of the file. Proprietary information shall be clearly marked. The following shall be included in the Narrative discussion:

TO (see RFI 10, 86 and 87):

L.2.5.2 Each Volume of the proposal shall consist of a Title Page, Table of Contents, Summary Section, and the Narrative discussion. The Summary Section shall contain a brief abstract of the file. Proprietary information shall be clearly marked. The Narrative discussion shall include information as required at L.3 and all subparts.

L.2.5.2.1 The following requirements are not subject to the page limitations set forth at L.2.3:

Summary Section per L.2.5.2 Resumes per L.3.1.1.3 Screen shots per L.3.1.1.5 Summary per L.3.2.1 Consent and Letters of Commitment per L.3.2.2.1 Section 3 information per L.3.2.5, but limited as specified therein Letters of Commitment per L.3.2.5 Letters of Commitment per L.3.2.6 PPQs and POC List per L.3.2.7 and L.3.2.7.1

Any proposal requirement omitted from this list that expressly states an exception to page limitations shall also apply. In addition, administrative pages that do not contain proposal content such as Title Pages, Table of Contents, List of Tables / Figures, Acronym & Abbreviation Lists, Section Dividers, and/or Cross Reference Matrices are excluded from page limitations at L.2.3.

FROM:

L.3.1.1.1 The Program Management section shall include an Executive Summary discussing the overall management approach while operating in an operational and developmental testing environment. The discussion shall include the governance, alignment, communication, and improvements that will ensure successful performance of the PWS requirements.

TO (see RFI 13):

L.3.1.1.1 The Program Management section shall include an Executive Summary discussing the overall management approach while operating in an operational and developmental testing environment. The discussion shall include the governance, alignment, communication, improvements, and innovation that will ensure successful performance of the PWS requirements.

FROM:

L.3.1.1.3 The Offeror shall provide resumes for key personnel identified in PWS Section 1.6.15, “Key Personnel.” Resumes are excluded from the page limitations at L.2.3.

TO (see RFI 44):

L.3.1.1.3 The Offeror shall provide resumes for key personnel identified in PWS Section 1.6.15, “Key Personnel.” Resumes are excluded from the page limitations at L.2.3. To ensure compliance with L.5.2.1, resumes shall not identify personnel by name or company affiliation/identification.

FROM:

L.3.1.1.5 The Offeror shall demonstrate a fully functional project cost management system to include functionality, usability, tracking and reporting IAW PWS Section 4.12 and its subparts. The Offeror shall identify processes (or implementation of) to track hours costs, and invoices accurately. Demonstration of such may be through a direct, read-only link to the Offeror’s web-based systems for purpose of evaluation, screen shots* with associated narrative explanation, or detail otherwise to substantiate cost management capability as required by the PWS. If the required cost management system is not currently in place, the Offeror shall provide a detailed implementation plan that includes a clear timeline and associated narrative explanation to substantiate cost management capability-to-execution as required by the PWS. *If screen shots are utilized, the originating system native font and size is acceptable and thus, an exception to the proposal requirements at L.2.4.2 above applies. Additionally, screen shots, but NOT the associated narrative, are excluded from the page limitations at L.2.3 above.

Accordingly, Offerors shall NOT include narrative information on screen shot pages.

TO (see RFI 45, 46):

L.3.1.1.5 The Offeror shall demonstrate a fully functional project cost management system to include functionality, usability, tracking and reporting IAW PWS Section 4.12 and its subparts. The Offeror shall identify processes (or implementation of) to track hours costs, and invoices accurately. Demonstration of such may be through a direct, read-only link to include a read-only video link, to the Offeror’s web-based systems for purpose of evaluation, screen shots* with associated narrative explanation, or detail otherwise to substantiate cost management capability as required by the PWS. If the required cost management system is not currently in place, the Offeror shall provide a detailed implementation plan that includes a clear timeline and associated narrative explanation to substantiate cost management capability-to-execution as required by the PWS. *If screen shots are utilized, the originating system native font and size is acceptable and thus, an exception to the proposal requirements at L.2.4.2 above applies. Additionally, screen shots, but NOT the associated narrative, are excluded from the page limitations at L.2.3 above. Accordingly, Offerors shall NOT include narrative information on screen shot pages but may include figure names/numbers to ensure traceability. Offerors shall ensure the response complies with L.2.5.1.

FROM:

L.3.2.1 This volume shall contain past performance information regarding similar contracts and shall be organized into sections as outlined below. This volume shall not exceed 25 pages of offeror / prime past performance information plus five pages for each major subcontractor, teaming partner, and / or JV partner, with a maximum of three (thus, a maximum allowable page limitation of 40 pages). This volume shall include a summary describing the role of the offeror and each subcontractor, teaming partner, and / or JV. The summary shall also include a reference to the past performance contracts cited for each team member and the associated tasks from the PWS represented by each cited contract.

TO (see RFI 16):

L.3.2.1 This volume shall contain past performance information regarding similar contracts and shall be organized into sections as outlined below. This volume shall not exceed 25 pages of offeror / prime past performance information (including past performance of individual JV partners) plus five pages for each major subcontractor or teaming partner, with a maximum of three (thus, a maximum allowable page limitation of 40 pages). This volume shall include a summary, excluded from page limitations herein, describing the role of the offeror and each subcontractor, teaming partner, and / or JV. The summary shall also include a reference to the past performance contracts cited for each team member and the associated tasks from the PWS represented by each cited contract.

FROM:

L.3.2.2 Offerors shall submit up to five (5) Government contracts for the prime offeror and up to three (3) from major subcontractors, teaming partners, and / or JVs in performance or awarded during the past three years, from the issue date of this RFP, which are relevant to the efforts required by this solicitation. Accordingly, recent is defined as contract performance within 3 years of RFP issue date. Relevant efforts are defined as services/efforts that are the same as or similar to the effort in scope, magnitude and complexity (as compared to North American Industry Classification System (NAICS) code 541330) required by the RFP. Data concerning the offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order.

TO (see RFI 47):

L.3.2.2 Offerors shall submit up to five (5) Government contracts for the prime offeror (to include individual JV partners) and up to three (3) from major subcontractors or, teaming partners in performance or awarded during the past three years, from the issue date of this RFP, which are relevant to the efforts required by this solicitation.

Accordingly, recent is defined as contract performance within 3 years of RFP issue date. Relevant efforts are defined as services/efforts that are the same as or similar to the effort in scope, magnitude and complexity (as compared to North American Industry Classification System (NAICS) code 541330) required by the RFP. Data concerning the offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order.

FROM:

L.3.2.5 Section 3: Subcontracts. Offerors shall provide an outline of how the effort required by the RFP will be assigned for performance within the offeror’s corporate entity and among the proposed subcontractors, teaming partner, and / or JV, as required at L.3.2.1. The information provided for the prime Offeror and each proposed major subcontractor, teaming partner, and / or JV, must include the entire company name, company address, CAGE Code, UEI and type of work to be performed by citing the applicable Government PWS subparagraph number. This includes all major subcontractors, previously defined as a member of the Offeror’s team who will provide critical services or whose subcontract is valued at or more than 15% of the total proposed cost. Subcontractor consent and letters of commitment as specified at L.3.2.2.1 shall be included for all subcontractors, teaming partners, and / or JV proposed.

TO (see RFI 15):

L.3.2.5 Section 3: Subcontracts. Offerors shall provide an outline of how the effort required by the RFP will be assigned for performance within the offeror’s corporate entity and among the proposed subcontractors, teaming partner, and / or JV, as required at L.3.2.1. The information provided for the prime Offeror and each proposed major subcontractor, teaming partner, and / or JV, must include the entire company name, company address, CAGE Code, UEI and type of work to be performed by citing the applicable Government PWS subparagraph number. This includes all major subcontractors, previously defined as a member of the Offeror’s team who will provide critical services or whose subcontract is valued at or more than 15% of the total proposed cost. Subcontractor consent and letters of commitment as specified at L.3.2.2.1 shall be included for all subcontractors, teaming partners, and / or JV proposed. Proposal information for Section 3 is excluded from the page limitations at L.3.2.1, however, response to Section 3 shall not exceed five (5) pages, excluding Letters of Commitment, as they are not subject to a page limitation requirement IAW L.3.2.2.1 above.

FROM:

L.3.2.6 Section 4: New Corporate Entities. New corporate entities may submit data on prior contracts involving its offices 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. Past Performance data shall be included as described at L.3.2.3 and L.3.2.4 above. Additionally, Letters of Commitment shall be included in the proposal for these employees in order to be considered.

TO (see RFI 15):

L.3.2.6 Section 4: New Corporate Entities. New corporate entities may submit data on prior contracts involving its offices 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. Past Performance data shall be included as described at L.3.2.3 and L.3.2.4 above and is subject to the page limitations at L.3.2.1 (i.e., a new entity proposing as a prime may address requirements at L.3.2.3, L.3.2.4 and L.3.2.6 through the 25 page limitation at L.3.2.1 or as a major subcontractor, citing up to 3 prior contracts (and requirements at L.3.2.6) at 5 pages each for the total maximum 15 page limitation. Additionally, Letters of Commitment shall be included in the proposal for these employees in order to be considered. Letters of Commitment are excluded from the page limitation requirement.

FROM:

L.3.2.7.1 No later than the proposal due date and time, the Offeror shall e-mail the Contracting Office POCs above, a complete list of all contractor POCs the Offeror sent a questionnaire. The Offeror Questionnaire 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; and Date E-Mail to POC via DD/MMM/YYYY format.

TO (see RFI 15):

L.3.2.7.1 No later than the proposal due date and time, the Offeror shall e-mail the Contracting Office POCs above, a complete list of all contractor POCs the Offeror sent a questionnaire. The Offeror Questionnaire 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; and Date E-Mail to POC via DD/MMM/YYYY format. Past Performance Questionnaires, and the POC List required, are excluded from any page limitations identified in Volume II.

FROM:

L.3.3.4.1.1 Offeror’s may utilize historical data at A12 as deemed appropriate, but the Offeror is responsible for proposing personnel, hours and associated labor rates proposed to meet requirements as set forth herein.

TO (see RFI 21):

L.3.3.4.1.1 Offeror’s should utilize historical data at A12 as deemed appropriate, but the Offeror is responsible for proposing personnel, hours and associated labor rates proposed to meet requirements as set forth herein.

FROM:

M.5.2.1.2 The Government will evaluate the offeror’s adequacy and feasibility of the proposed organizational chart with the types and number of people and rationale for the organizational structure and the portion of work to be performed by each entity (e.g., Offeror, major subcontractors, and/or members of joint ventures or LLC) under the Offeror’s proposed approach to complete the work identified in the PWS for this solicitation.

TO (see RFI 82):

M.5.2.1.2 The Government will evaluate the offeror’s adequacy and feasibility of the proposed organizational and management structure through the chart(s) and associated narrative rationale for the organizational structure identified and the portion of work to be performed by each entity (e.g., Offeror, major subcontractors, and/or members of joint ventures or LLC) under the Offeror’s proposed approach to complete the work identified in the PWS for this solicitation.

FROM:

M.5.3.5 The Past Performance evaluation will assess the relative risk associated with an Offeror’s likelihood of success in performing the required efforts of the PWS.

Performance risk is at the factor level after evaluating aspects of the Offeror’s recent performance and focusing on performance that is first deemed recent, and then relevant to the services being procured under this RFP. Offerors are cautioned that in conducting the performance risk assessment, the Government may use data provided in the Offeror’s proposal and data obtained from other sources, such as the CPARS or similar systems and State Department Watch Lists. The areas of past performance to be reviewed in the evaluation process include:

• Business Relations

• Quality of Service

• Service

• Cost Control

• Customer Satisfaction

TO (see RFI 24):

M.5.3.5 The Past Performance evaluation will assess the relative risk associated with an Offeror’s likelihood of success in performing the required efforts of the PWS.

Performance risk is at the factor level after evaluating aspects of the Offeror’s recent performance and focusing on performance that is first deemed recent, and then relevant to the services being procured under this RFP. Offerors are cautioned that in conducting the performance risk assessment, the Government may use data provided in the Offeror’s proposal and data obtained from other sources, such as the CPARS or similar systems and State Department Watch Lists. The areas of past performance to be reviewed in the evaluation process include:

• Business Relations

• Quality of Service

• Cost Control

• Customer Satisfaction

The following RFP Attachments at Section J have been amended as noted, and attached herein:

Attachment 3: Appendix 1.6.9 Safety Requirements – incorporated to provide a fully legible attachment (RFI 52) Attachment 10: PPQ – incorporated to provide an editable version for Offeror response

(RFI 95)

Attachment 11: Pricing Matrix – incorporated to update the Period of Performance (as a result of RFI 41)

All other terms and conditions of the solicitation remain unchanged.

SECTION F - DELIVERIES OR PERFORMANCE

The following Delivery Schedule item for CLIN 0001 has been changed from:

DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

POP 01-JUN-2025 TO

31-MAY-2026

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

FOB: Destination

W81C39

To:

DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

POP 01-JUN-2025 TO

30-APR-2026

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 0002 has been changed from:

CAGE

POP 01-JUN-2025 TO

31-MAY-2026

N/A COMMANDER, US ARMY WSMR

WHITE SANDS MISSILE RANGE

100 HEADQUARTERS

WHITE SANDS MISSILE RANGE, NM NM

88002

CAGE

POP 01-JUN-2025 TO

30-APR-2026

N/A COMMANDER, US ARMY WSMR

WHITE SANDS MISSILE RANGE

100 HEADQUARTERS

WHITE SANDS MISSILE RANGE, NM NM

88002

The following Delivery Schedule item for CLIN 0003 has been changed from:

CAGE

POP 01-JUN-2025 TO

31-MAY-2026

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-JUN-2025 TO

30-APR-2026

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 1001 has been changed from:

CAGE

POP 01-JUN-2026 TO

31-MAY-2027

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-MAY-2026 TO

30-APR-2027

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 1002 has been changed from:

CAGE

POP 01-JUN-2026 TO

31-MAY-2027

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-MAY-2026 TO

30-APR-2027

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 1003 has been changed from:

POP 01-JUN-2026 TO

31-MAY-2027

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-MAY-2026 TO

30-APR-2027

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 2001 has been changed from:

CAGE

POP 01-JUN-2027 TO

31-MAY-2028

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-MAY-2027 TO

30-APR-2028

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 2002 has been changed from:

CAGE

POP 01-JUN-2027 TO

31-MAY-2028

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-MAY-2027 TO

30-APR-2028

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 2003 has been changed from:

CAGE

POP 01-JUN-2027 TO

31-MAY-2028

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-MAY-2027 TO

30-APR-2028

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 3001 has been changed from:

CAGE

POP 01-JUN-2028 TO

31-MAY-2029

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

POP 01-MAY-2028 TO

30-APR-2029

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 3002 has been changed from:

CAGE

POP 01-JUN-2028 TO

31-MAY-2029

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-MAY-2028 TO

30-APR-2029

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 3003 has been changed from:

CAGE

POP 01-JUN-2028 TO

31-MAY-2029

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-MAY-2028 TO

30-APR-2029

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 4001 has been changed from:

CAGE

POP 01-JUN-2029 TO

31-MAY-2030

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-MAY-2029 TO

30-APR-2030

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 4002 has been changed from:

CAGE

POP 01-JUN-2029 TO

31-MAY-2030

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-MAY-2029 TO

30-APR-2030

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

The following Delivery Schedule item for CLIN 4003 has been changed from:

POP 01-JUN-2029 TO

31-MAY-2030

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

CAGE

POP 01-MAY-2029 TO

30-APR-2030

N/A CDR WHITE SANDS MISSILE RANGE

CDR WHITE SANDS MISSILE RANGE

100 HEADQUARTERS AVENUE

WHITE SANDS NM 88002

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS TO OFFERORS

L.1 Information to Offerors and Instructions for Proposal Preparation

L.1.1 Offerors shall strictly adhere to requirements herein when preparing the proposal submission in response to this RFP. The Government will NOT reimburse any costs incurred in response to this RFP. Proposals that fail to comply with the proposal submittal requirements set forth in this section may be deemed unacceptable, and therefore, ineligible for award. Proposals shall be submitted PRIOR TO THE DATE AND TIME specified within this RFP. Proposals received after the date and time specified for receipt of proposals will be handled in accordance with FAR 15.208.

L.1.2 All RFP documents, to include any amendments issued after RFP issuance, shall be posted to Contract Opportunities at SAM.gov. It is the offeror’s responsibility to monitor the website for any amendments to the solicitation and incorporate any signed amendments within the offeror’s proposal submission.

L.1.3 To ensure timely and equitable evaluation of proposals, offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors and subfactors.

Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale for Government evaluation. The submitted proposal shall consist of four (4) separate volumes as follows:

Volume Volume Title Volume I Technical / Mission Capability Volume II Past Performance Volume III Cost / Price Volume IV Solicitation, Offer and Award Documents, and

Certifications / Representations

L.1.4 Requests for Information (RFI). Offerors may submit RFIs regarding the RFP to the Government Points of Contact (POC) listed herein up to 3:00 PM, Eastern Standard Time (EST) 06 NOV 2024. Depending on the volume of RFIs received, the acquisition team will work to post responses via Contracting Opportunities at SAM.gov by close of business Friday, each week, through the last RFI response posting, 08 NOV 2024. The intent of RFI responses is to provide clarifying information to all Offerors. NOTE: The solicitation will remain unchanged unless specifically amended in writing.

Primary POC: Contract Specialist, Avangela Ligons-Sutton, avangela.y.ligons-sutton.civ@army.mil Secondary POC: Contracting Officer, Ingrid Smith, ingrid.v.smith.civ@army.mil

L.1.5 Proposal Validity. Proposals shall be valid for 270 days from the date of RFP close. The Offeror shall clearly state confirmation of such within Volume IV. An Offeror who fails to confirm proposal validity or proposes a validity period less than the Government’s requirement may be rejected.

L.2. Proposal Submission Requirements

L.2.1 Proposal Due Date. Proposals are due no later than 3:00 PM EST on 26 NOV 2024. Late proposals may be rejected from consideration IAW FAR 15.208. It is the Offeror’s responsibility to confirm the Government has received the proposal prior to the specified due date and time.

L.2.2 Complete proposals (i.e., each Volume as defined above and detailed herein) shall be submitted electronically to the following email address:

usarmy.jbsa.acc-micc.mbx.tsc-div3@army.mil

L.2.2.1 The email subject header shall be RFP W91151-24-R-0030, Offeror Name

L.2.2.2 The maximum size of each email must not exceed 10 megabytes. The Offeror may use multiple email messages for each submission; however, it should annotate the subject lines as described above for each message, and number them in the following manner: Message 1 of 3, 2 of 3, 3 of 3, etc. Emails that exceed 10 megabytes may cause the email to be rejected which may result in the proposal, in its entirety, not being received at the required destination by the Due Date and Time for Receipt of Offers specified in the RFP.

mailto:avangela.y.ligons-sutton.civ@army.mil mailto:ingrid.v.smith.civ@army.mil mailto:usarmy.jbsa.acc-micc.mbx.tsc-div3@army.mil

L.2.2.3 The Offeror shall make every effort to ensure that the proposal is virus free.

Proposals (or portions thereof) submitted which indicate the presence of a virus, or which are otherwise rendered unreadable by damage in electronic transit, shall be treated as “unreadable” as described in FAR 15.207(c).

L.2.3 The following Volumes of material and proposal content shall be submitted:

Volume Volume Title Maximum Pages* Volume I Technical / Mission Capability 50 Volume II Past Performance 40** Volume III Cost / Price No page limitation Volume IV Solicitation, Offer and Award Documents, and Certifications / Representations

No page limitation

* Pages that exceed the established page limitations will NOT be evaluated or considered.

**See L.3.2.1.

L.2.4 Page Format, Size, Packaging

L.2.4.1 Format. The submission shall be clearly indexed and logically assembled. 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 date and RFP number in the header and/or footer. A Table of Contents should be created using the Table of Content feature in MS Word. MS Word (doc) files shall use the following page setup parameters:

Margins – Top, Bottom, Left, Right – 1” Gutter – 0” From Edge – Header, Footer 0.5” Page Size, Width – 8.5” Page Size, Height – 11”

L.2.4.1.1 All proposal information shall be in the English language and U.S. Dollars.

Proposal information not in the English language or U.S. Dollars will not be considered and will be cause for the proposal to be rejected.

L.2.4.2 Size. Each paragraph should be single spaced and shall be separated by at least one blank line. A standard, 12-point minimum font size applies. Arial or New Times Roman fonts are required. Tables and illustrations may use a font size no less than 12-point and may be produced in landscape mode.

L.2.4.3 Packaging. All proposal files shall be uploaded in their native format, i.e., doc, xls, ppt, etc. In addition, each file shall be converted to a read-only PDF (note, in the event the native and PDF file differ, the Government will utilize the PDF file for evaluation). All price breakdown information to aide in the cost/price evaluation shall be submitted in Microsoft Office Excel Read/Write format and viewable in Microsoft Excel

2013. **Please note – Self extracting exe files are not acceptable. Each proposal Volume shall be packaged so as to not exceed the email size limitations at L.2.2.2.

L.2.5 Proposal Content. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the offeror intends to meet those requirements. Offerors shall assume the Government has no prior knowledge of their organization and experience and will base its evaluation on the information presented in the offeror’s proposal.

L.2.5.1 Volume I and contents within proposal pages (to include screen shots and/or read-only link data in support of L.3.1.1.5), including appendices, Table of Contents, Title Pages, Glossary, Dividers/Tabs, Blank pages and throughout the digital copies of the Technical / Mission Capability Volume of the proposal shall not contain company logos and/or names, pictures or any information that indicates the Offeror’s (to include all team members) identification or personnel. The Technical / Mission Capability Volume shall not contain any pictures that identify Offeror personnel or Government personnel. No quotes or statements made by Government personnel in prior acquisition efforts shall be contained within Volume I of the Offeror’s proposal. Each proposal Volume (I-Technical / Mission Capability, II-Past Performance, III-Cost / Price, IV- Solicitation, Offer and Award Documents, and Certifications / Representations) shall be submitted as a separate Volume file, and IAW instructions at L.2.2 and its subparts.

L.2.5.2 Each Volume of the proposal shall consist of a Title Page, Table of Contents, Summary Section, and the Narrative discussion. The Summary Section shall contain a brief abstract of the file. Proprietary information shall be clearly marked. The Narrative discussion shall include information as required at L.3 and all subparts.

L.2.5.2.1 The following requirements are not subject to the page limitations set forth at L.2.3:

Summary Section per L.2.5.2 Resumes per L.3.1.1.3 Screen shots per L.3.1.1.5 Summary per L.3.2.1 Consent and Letters of Commitment per L.3.2.2.1 Section 3 information per L.3.2.5, but limited as specified therein Letters of Commitment per L.3.2.5 Letters of Commitment per L.3.2.6 PPQs and POC List per L.3.2.7 and L.3.2.7.1

Any proposal requirement omitted from this list that expressly states an exception to page limitations shall also apply. In addition, administrative pages that do not contain proposal content such as Title Pages, Table of Contents, List of Tables / Figures, Acronym & Abbreviation Lists, Section Dividers, and/or Cross Reference Matrices are excluded from page limitations at L.2.3.

L.3 Evaluation Factors

L.3.1 Volume I, Factor One: Technical / Mission Capability

Offerors shall provide a proposal that addresses the elements at the Technical / Mission Capability subfactors herein.

L.3.1.1 Subfactor One: Program Management. The Offeror shall detail and describe its program management approach to include its organizational and management structure, to include major subcontractor*, teaming partners, and / or Joint Venture (JV) relationships, key personnel qualifications, quality control process and procedures, cost management system, and continuous process improvement methods. *A major subcontractor, as referenced throughout the proposal requirements is defined as a member of an Offeror’s overall team who will provide critical services or whose subcontract is valued at or more than fifteen (15) percent of the total proposed cost.

L.3.1.1.1 The Program Management section shall include an Executive Summary discussing the overall management approach while operating in an operational and developmental testing environment. The discussion shall include the governance, alignment, communication, improvements, and innovation that will ensure successful performance of the PWS requirements.

L.3.1.1.2 The Offeror shall detail its organizational and management structure in an organizational chart(s), demonstrating teaming arrangements, functional and supervisory lines of control, and roles and responsibilities assigned to successfully accomplish TEAS mission requirements. The Offeror shall demonstrate, through the organizational chart and associated narrative, its approach to prime / subcontract integration, decision-making, managing fluctuations in workload, managing quality control, and problem resolution. Additionally, the Offeror shall substantiate why the organizational and management structure proposed is designed to ensure successful contract performance. Organizational charts may be submitted via 11x17 page format, an exception to the page format specified at L.2.4.2 above. Each 11X17 page counts as one-page toward page limitations at L.2.3.

L.3.1.1.3 The Offeror shall provide resumes for key personnel identified in PWS Section 1.6.15, “Key Personnel.” Resumes are excluded from the page limitations at L.2.3. To ensure compliance with L.5.2.1, resumes shall not identify personnel by name or company affiliation/identification.

L.3.1.1.4 The Offeror shall describe its approach for reducing and controlling costs, business processes, and policies to perform sound fiscal stewardship over funds during contract performance. At a minimum, the Offeror shall address the capabilities required at PWS Section 4.12 “Cost Management and Work Assignment Process” and its subparts, and Attachment 9, “Project Cost Management System.”

L.3.1.1.5 The Offeror shall demonstrate a fully functional project cost management system to include functionality, usability, tracking and reporting IAW PWS Section 4.12 and its subparts. The Offeror shall identify processes (or implementation of) to track hours costs, and invoices accurately. Demonstration of such may be through a direct, read-only link to include a read-only video link, to the Offeror’s web-based systems for purpose of evaluation, screen shots* with associated narrative explanation, or detail otherwise to substantiate cost management capability as required by the PWS. If the required cost management system is not currently in place, the Offeror shall provide a detailed implementation plan that includes a clear timeline and associated narrative explanation to substantiate cost management capability-to-execution as required by the PWS. *If screen shots are utilized, the originating system native font and size is acceptable and thus, an exception to the proposal requirements at L.2.4.2 above applies. Additionally, screen shots, but NOT the associated narrative, are excluded from the page limitations at L.2.3 above. Accordingly, Offerors shall NOT include narrative information on screen shot pages but may include figure names/numbers to ensure traceability. Offerors shall ensure the response complies with L.2.5.1.

L.3.1.2 Subfactor Two: Recruitment and Retention of Technical Expertise. The Offeror shall demonstrate, in detail, the plan for recruiting and retaining a workforce possessing and maintaining the critical skills needed for the successful performance of the requirements of the scope of requirements and services at PWS Section 1.3, Section 4.13 and tasks at Part 5.

L.3.1.2.1 The Offeror shall describe its current business operations that is capable to immediately fulfill services and support requirements with qualified personnel as set forth in PWS Section 1.3, Part 5 and resulting WAO requirements. If not currently in place, the Offeror shall detail its plan to recruit, and subsequently retain qualified personnel.

L.3.1.2.2 The Offeror shall address and detail its training program and how it keeps personnel technically relevant by providing training for new technologies and procedures to maintain relevant expertise to maximize effectiveness of its workforce.

L.3.1.2.3 The Offeror shall describe its plan for ensuring performance as specified at PWS Section 4.13 and responding to fluctuating demands in requirements and expertise required, both surges and decreases.

L.3.1.3 Subfactor Three: Continuity of Operations. The Offeror shall describe its approach, and risk identification and mitigation strategies, for a successful contract phase in and transition as set forth at PWS Section 1.6.22 and its subparts.

Additionally, the Offeror shall describe its approach, and risk identification and mitigation strategies for a successful contract phase out as set forth in PWS Section 1.6.23 and its subparts.

L.3.1.3.1 In detailing the Offeror’s approach to phase-in, at a minimum, the Offeror shall include:

1. The Offeror’s Transition Plan, to include the schedule and staffing and critical milestones.

2. The Offeror’s approach to assuming total contract responsibility without disruption or degradation of performance during the transition period AND initial execution at day one of the 11-Month Base Year.

3. Identification of risks and proposed mitigation strategies.

4. Identification of the Offeror qualified resources available to immediately begin work to support transition efforts and/or at day one of the 11-Month Base Year.

5. When resources are not currently on hand, the Offeror’s approach to ensure availability of trained and qualified personnel.

L.3.1.3.2 In detailing the Offeror’s approach to phase-out, at a minimum, the Offeror shall include:

1. Critical milestones necessary for seamless contract phase-out.

2. Identification of risks and proposed mitigation strategies.

3. Identification of any lessons learned from prior contract phase-out actions and recommendations for Government consideration.

L.3.2 Volume II, Factor Two: Past Performance

L.3.2.1 This volume shall contain past performance information regarding similar contracts and shall be organized into sections as outlined below. This volume shall not exceed 25 pages of offeror / prime past performance information (including past performance of individual JV partners) plus five pages for each major subcontractor or teaming partner, with a maximum of three (thus, a maximum allowable page limitation of 40 pages). This volume shall include a summary, excluded from page limitations herein, describing the role of the offeror and each subcontractor, teaming partner, and / or JV. The summary shall also include a reference to the past performance contracts cited for each team member and the associated tasks from the PWS represented by each cited contract.

L.3.2.2 Offerors shall submit up to five (5) Government contracts for the prime offeror (to include individual JV partners) and up to three (3) from major subcontractors or, teaming partners in performance or awarded during the past three years, from the issue date of this RFP, which are relevant to the efforts required by this solicitation.

Accordingly, recent is defined as contract performance within 3 years of RFP issue date. Relevant efforts are defined as services/efforts that are the same as or similar to the effort in scope, magnitude and complexity (as compared to North American Industry Classification System (NAICS) code 541330) required by the RFP. Data concerning the offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order.

L.3.2.2.1 Consent and Letters of Commitment. The Offeror shall submit written consent of its major subcontractors, team partners, and / or JV to allow disclosure of past performance information to the Offeror. In addition, letters of commitment shall be included for all major subcontractors, teaming partners, and / or JV cited in order for past performance to be considered. Consent and Letters of Commitment are excluded from page limitations specified.

L.3.2.3 Section 1: Contract Descriptions. Contracts cited within the Past Performance proposal shall include the following information:

1. Offeror / Subcontractor place of performance, CAGE Code and Unique Entity Identifier (UEI). If the work was performed as a subcontractor, also provide the name of the prime contractor and POC within the prime contractor organization (name, and current address, email address, and telephone number).

2. Government contracting activity / customer, and current address, email address, and telephone numbers for the following personnel:

a. Procuring Contracting Officer.

b. Government’s technical representative/COR.

c. Administrative Contracting Officer.

d. Pre-Award Monitor.

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

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

5. Awarded price / cost.

6. Final or projected final price / cost.

7. Original delivery schedule, including dates of start and completion of work.

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

L.3.2.4 Section 2: Contract Performance. Offerors shall provide a specific narrative explanation of each contract cited at L.3.2.3, describing the objectives achieved and detailing how the effort is relevant to the TEAS requirement, identifying the specific elements of the PWS herein, by PWS paragraph number, that were performed on the cited contract.

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