Solicitation Amendment N6572626R30000001 SF 30.pdf

R

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

(a) By completing items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or electronic communication 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 letter or electronic communication, provided each letter or electronic communication 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 NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

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

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

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

16C. DATE SIGNED

Previous edition unusable STANDARD FORM 30 (REV. 11/2016) Prescribed by GSA FAR (48 CFR) 53.243

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE PAGE OF PAGES

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

6. ISSUED BY CODE 7. ADMINISTERED BY (If other than Item 6) CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBE

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

Section A - Solicitation/Contract Form

The following changes have been made:

Miscellaneous text in this section has been modified to:

QUESTIONS AND ANSWERS1. Question: How many RBS model efforts do you expect per year (new builds vs updates), and what’s the typical number of models “in flight” at once?Answer: Model projection of 800 models per year and 800 in flight at once.2. Question: What are the typical turnaround expectations for (a) initial model execution, (b) re-runs after comments, and (c) final delivery?Answer: Once data is available, typical turnaround expectations 2-4 weeks per model for initial model execution, rerun with comments 1-2 weeks, MARRC-RB final delivery 1 week.3. Question: What usually triggers model rework/re-runs (config changes, allowance list changes, part substitutions), and how frequently does that happen?Answer: Currently NAVSEA is working to determine model reruns and direction will be provided to the successful contractor upon award.4.

Question: What level of contractor responsibility is expected for data cleanup/normalization (e.g., resolving missing part attributes, invalid configs, duplicates), versus the Government correcting the source data?Answer:

Contractor will be responsible for collaborating with the Government to resolve data clean up of source data, with input from the program office, in service engineering agents, and other government stakeholders .5.

Question: Are there any specific versions / configurations / business rules for OPUS/SIMLOX and NCRM that NAVSEALOGCEN requires?Answer: Currently required Navy Enterprise software is OPUS Suite 2024.16.

Question: For the standardized NAVSEALOGCEN RBS Results Spreadsheet + coversheet (CDRL A002), can you provide a “gold standard” sample (redacted if needed) and clarify what fields are mandatory vs optional?

Answer: Results spreadsheet will be provided upon contract award and all fields in the spreadsheet will be mandatory. Training and spreadsheet will be provided upon contract award.7. Question: What is the review /acceptance workflow for model outputs and the results spreadsheet (who reviews, typical number of review cycles, and expected comment turnaround time)?Answer: Models are submitted to the MARRC-RB repository with the following contractor artifacts: results spreadsheet, configuration, OPUS and Simlox Input files, Ao threshold reference. There isn't a typical number of review cycles. Turn around time with comments can vary but is generally within a week. Internally developed NSLC models generally are accepted in 1-2 reviews. Training will be provided to the contractor to ensure alignment with NSLC submission. 8. Question:

For MARRC-RB RBS package submission support, what artifacts are included in the “package” beyond the results spreadsheet (e.g., assumptions memo, data pedigree, run logs, configuration snapshots), and what is the typical iteration count before submission?Answer: Contractor artifacts include: NLSC standardized results spreadsheet, OPUS and Simlox Input files, Ao threshold reference. 9. Question: Can the Government confirm that the 2 years of OPUS suite experience is the only "required" qualification for the Senior Engineer, Key Personnel?Answer: All required and desired qualifications are provided in RFP Attachment 4.10. Question:

Would past performance that the bidder completed as a subcontractor be acceptable to the Government?Answer:

Yes.11. Question: Attachment 4 – Personnel Qualifications, Section B, “Senior Engineer – Key Personnel” (PWS 5.1–5.9) identifies the Senior Engineer as key personnel, and the Recommended Labor Mix (Attachment 4, Section A) shows 3,840 hours per year plus overtime for this labor category. Please clarify whether the Government expects one resume representing a single individual filling the Senior Engineer role across all years, or multiple resumes if more than one individual is proposed to collectively fulfill the Senior Engineer hours.Answer: Per RFP Section L, paragraph 3.1.3, "Offeror shall provide one resume for each individual proposed to fulfill the positions identified as key personnel in accordance with Attachment 4 - Personnel Qualifications. All key personnel positions shall identify a current employee or contingent hire to fulfil the role.

Each resume shall demonstrate the key personnel's qualifications to complete the tasking for which person has been proposed to perform."12. Question: Personnel Qualifications identifies both the Project Manager SR and Senior Engineer as Key Personnel, but the solicitation does not clearly describe the approval process for substitution of key personnel after award. Please confirm whether substitutions for key personnel require prior

N6572626R30000001

Contracting Officer approval, and whether proposed replacements must meet or exceed the stated education and experience requirements (Attachment 4, Section B)Answer: Please see RFP Section C, "C-237-H002 SUBSTITUTION OF KEY PERSONNEL" and Section L, paragraph 3.1.3 for information regarding the post-award substitution of key personnel.13. Question: Personnel Qualifications, Senior Engineer description requires “2+ years of modeling experience using OPUS Suite software.” Please clarify whether experience using functionally equivalent modeling tools is acceptable, or whether OPUS Suite experience is a strict requirement for key personnel eligibility.Answer: Per Attachment 4, at least two years of modeling experience using OPUS Suite software is required experience for the Senior Engineer positions. Experience with OPUS Suite or similar modeling experience is desired for the Engineer II position.14. Question: Attachment 4 – Personnel Qualifications, Section A (Recommended Labor Mix), it states: “It is noted that other labor categories, such as Logisticians or Data Scientists, could be proposed and used depending on the expertise and experience level.”

Would the government clarify whether the Government expects offerors to propose additional FTEs beyond the recommended labor mix to accommodate these roles, or whether offerors are permitted to adjust the existing labor mix by reallocating them to include these additional labor categories?Answer: The labor categories noted (Logisticians or Data Scientists) are those which the Government believes would also be appropriate for the tasking and were provided as potential alternatives. No additional hours beyond the recommended level of effort is expected. Please note, per Attachment 4, paragraph A, "If the proposed labor mix differs from the estimate provided below, the Offeror shall describe how/why the proposed labor mix will result in a high quality, efficient, and cost effective solution." Proposing the alternative labor categories noted (Logisticians or Data Scientists) would be a deviation from the estimate provided and would require an explanation.15.

Question: Is FAR 52.222-41 Applicable to this requirement?Answer: FAR 52.222-41 is incorporated at the SeaPort MAC level. Should SCLS labor categories be proposed, the clause will be applicable.16. Question: Are these services currently being performed by other contractors on other requirements or is this truly a new contract? Answer: Naval Sea Logistics Center is not aware of any contracts or orders under which this work is being performed.

N6572626R30000001

5450 CARLISLE PIKE, MECHANICSBURG PA 17055-2411

MECHANICSBURG, PA 17055-2411

UNITED STATES

Marisa Wirfel, Email: marisa.n.wirfel.civ@us.navy.mil Telephone: 7176056176 AdminBy:

SCD: PAS: