N6660421Q0286A0001.pdf
PDF 171 KB Posted
- Attached to
- M&SWP 3. 0 Application Configuration Services Federal contract opportunity
- Solicitation number
- N6660421Q0286A0001
About this file
This amendment modifies a solicitation for application configuration services. The amendment extends the proposal due date from August 20, 2021 to August 27, 2021 and provides answers to vendor questions. The solicitation seeks program management, technical services, and configuration support for the M&SWP 3.0 application in accordance with the statement of work. The Naval Sea Systems Command and Department of the Navy are listed as the issuing agencies. Eligible vendors are provided one additional week to submit proposals for these services.
View the file
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
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 purposed of this Amendment is to provide answ ers to vendor questions and to extend the Propsal Due by date. See page 2 for details.
1. CONTRACT ID CODE PAGE OF PAGES
J 1 6
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 19-Aug-2021
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 N6660421Q0286
X 9B. DATED (SEE ITEM 11)
29-Jul-2021
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 X is extended, 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-Aug-2021
CODE
NAVAL UNDERSEA WARFARE CENTER
CHELSEA A ISHERWOOD, CODE 0223
CONTRACTS DEPARTMENT
1176 HOWELL STREET, BLDG. 1258
NEWPORT RI 02841-1708
N66604 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
N6660421Q0286
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION A - SOLICITATION/CONTRACT FORM
The required response date/time has changed from 20-Aug-2021 02:00 PM to 27-Aug-2021 02:00 PM.
The following have been modified:
GENERAL INFORMATION
Distribution: FILE, KR, NUWC 01/115, PI: TBD
NUWCDIVNPT Action Number: 210286
NUWCDIVNPT PID Number: 02-0026
NUWCDIVNPT Requisition Number: 1300945145
NUWCDIVNPT POC: Chelsea Isherwood (Phone: 401-832-4381; Email: chelsea.isherwood@navy.mil)
DELIVERY MARK FOR
SUBMEPP Activity PO Box 2500 Portsmouth Naval Shipyard Portsmouth, NH 03804-2500
The purpose of Amendment 0001 is:
1. Extend the Proposal Due by date.
2. Update the CLIN description for CLINs 0001 and 0002.
3. Provide answers to vendor questions.
SECTION A –
1. The solicitation Proposal Due by date has been extend as follows:
A. From: 20 August 2021, 2:00PM EST B. To: 27 August 2021, 2:00PM EST
SECTION B –
1. Update CLIN 0001 description as follows:
A. From: Program Management and Technical Service in accordance with the Statement of Work (SOW), paragraphs 4.1, 4.3, 4.4, 4.5, 4.7, 4.8, and 4.9 in Section C.
B. To: Program Management and Technical Service in accordance with the Statement of Work (SOW), paragraphs 4.1.1, 4.1.2, 4.1.3, 4.1.5, 4.1.7, 4.1.8, 4.1.9, 4.2, and 4.3 including all subparagraphs of these paragraphs in Section C.
2. Update CLIN 0002 secription as follows:
A. From: Program Management and Technical Service in accordance with the Statement of Work (SOW), paragraphs 4.2 and 4.6 in Section C.
B. To: Program Management and Technical Service in accordance with the Statement of Work (SOW), paragraphs 4.1.4 and 4.1.6 including all subparagraphs of these paragraphs in Section C.
Vendor Questions and Answers -
Q1. In reference to the SOW:
For the purpose of this question, a system configuration work task that does not fit into one of the four defined work unit categories (i.e., BMIDE, Workflow, Report, or Interface) is referred to as an "Other" work unit. Can there be multiple "Other" work units assigned to a Configuration Change Request (CR)? For example, assuming an autoscheduler change and a Teamcenter custom code change are each not considered part of the four work unit categories and both are required to implement a given CR, will two work units be assigned to account for those changes or will only one work unit apply as a combined "Other" category?
A1. Multiple “other” work units may be part of a single configuration change request. In the example provided there would be two “other” work units to support that configuration change request. The government will provide configuration change requests to the contractor clearly stating how many work units the configuration change request will represent. If the contractor does not agree with the government’s assessment of work units they are encouraged to provide their rationale and the team will negotiate and agree on the number of work units for the configuration change request prior to the contractor accepting the configuration change request.
Q2. In reference to the SOW:
Will the Government have sole discretion to assign work unit values to each Configuration Change Request (CR) or will the contractor team have an opportunity to provide input to that determination based on the requirement analysis performed for each CR?
A2. The examples and guidelines provided in Appendix A to the SOW were provided to give a common understanding between the bidder and the government on what a work unit consists of. The government will clearly state on the configuration change request the number of work units based on the methodology outlined in Appendix A of the SOW. If the contractor does not agree with the government’s assessment of the work units they are encouraged to provide their rationale and the team will negotiate and agree on the number of work units for the configuration change request prior to the contractor accepting the configuration change request.
Q3. In reference to the SOW:
The Offeror assumes once a CR and its derived requirements have been approved for implementation by the Government, work has been scheduled, and implementation of the CR has started any changes associated with that CR not identified in the approved derived requirements will be documented within a new CR for requirement derivation and approval. Please confirm this is a correct assumption. If not, please clarify.
A3: This assumption is correct. However, it is imperative that configuration change requests are adequately evaluated, understood, and all derived requirements have been identified prior to implementation of the configuration change request. The government understands that work evolves and unforeseen circumstances occur, however the government wants to emphasize that continuously missing derived requirements resulting in the need for issuing additional configuration change requests will be seen as poor contract performance and will be reflected on the contractor’s CPARS evaluation.
Q4. In reference to Section F of the Solicitation:
The Period of Performance (POP) for CLIN 0002 is identified as 22-NOV-2021 to 22-SEP-2022 while the POP for all other CLINs begins on 23-SEP-2021. The Offeror assumes the POP for all CLINs associated with this RFP is 23- SEP-2021 to 22-SEP-2022. Please confirm the POP for all three CLINs is 23-SEP-2021 to 22-SEP-2022.
A4. The PoP start date for CLIN 0002 is accurate as shown in the solicitation 22-Nov-2021. CLIN 0002 is an Option CLIN that may be a permanent part of the CLIN structure in the award document if the Government does not have enough FY21 funding to cover the services under CLIN 0002. At that point the Government will exercise this Option CLIN 0002 as of 22 November 2021 with a PoP end date of 22 September 2022 to correlate with the other three CLINs and the lifecycle of the purchase order.
If the Government has enough FY21 funding, then the services listed under CLIN 0002 will be merged into CLIN 0001 with a PoP of 23 September 2021 through 22 September 2022.
Q5. In reference to Section B CLIN 0001:
The Offeror assumes paragraphs identified for CLIN 0001 in Section B are meant to refer to SOW paragraphs 4.1.1, 4.1.3, 4.1.4, 4.1.5, 4.1.7, 4.1.8 and 4.1.9 in Section C. Please confirm the assumption is accurate. If not, please clarify.
A5. CLIN 0001 in section B should refer to SOW paragraphs 4.1.1, 4.1.2, 4.1.3, 4.1.5, 4.1.7, 4.1.8, 4.1.9, 4.2, and 4.3 including all subparagraphs of these paragraphs. The CLIN 0001 description has been updated.
Q6. In reference to Section B CLIN 0002:
The Offeror assumes paragraphs identified for CLIN 0002 in Section B are meant to refer to SOW paragraphs 4.1.2 and 4.1.6 in Section C. Please confirm the assumption is correct. If not, please clarify.
A6. CLIN 0002 in section B should refer to SOW paragraphs 4.1.4 and 4.1.6 including all subparagraphs of these paragraphs. The CLIN 0002 description has been updated.
Q7. In reference to the SOW:
The Offeror assumes indented Section C.4.1.3.2.1.1 (PDF p. 13 first reference) should read as follows: "All developed code (eg. C++, JAVA) for the government and not part of the core eQ-Technologic applications for release, will be submitted to and reviewed by the government ISSM." Please confirm the assumption is correct. If not, please clarify.
A7: Paragraph 4.1.3.2.1.1 should read “All developed code (eg. C++, JAVA) for the government and not part of the core eQ-Technologic application for release, will be submitted to and reviewed by the government
ISSM.”
Q8. In reference to the SOW:
The Offeror assumes indented Section C.4.1.3.2.1.2 (PDF p. 13 first reference) should read as follows. "All developed code (eg. C++, JAVA) for the government and not part of the core eQ-Technologic applications for general release will be stored at the government location for configuration control purposes." Please confirm the assumption is correct. If not, please clarify.
A8: Paragraph 4.1.3.2.1.2 should read “All developed code (eg. C++, JAVA) for the government and not part of the core eQ-Technologic application for general release will be stored at the government location for configuration control purposes.”
Q9. In reference to Section L:
The participation % calculation instructs to add Total SB Contract and Subcontract Dollars divided by Total Contract Value. This calculates the Total Planned Subcontracting % and not the SB participation %. Usually the Planned SB Subcontracting % is calculated as Planned SB Subcontracting divided by Total Planned Subcontracting OR Planned SB Subcontracting divided by Total Contract Value. Please advise.
A9. The formula is used to determine the total small business participation for the overall contract: "A small business offeror shall indicate the percentage of work performed by itself, as well as by any Small Business subcontractors. Proposals submitted by Large
Business Concerns shall indicate the percentage of work performed by Small Business Subcontractors."
Therefore, the formula should be interpreted differently based on the size of the prime:
Prime is a large business:
Participation % = Total Small Business [Contract/Task Order] 0$+ Subcontract Dollars to small businesses Total [Contract/Task Order] Value
Prime is a small business:
Participation % = Total Small Business Prime portion [Contract/Task Order] + Subcontract Dollars to small businesses Total [Contract/Task Order] Value
Q10. In reference to Section L:
RFP Section L.1.3.c stipulates Volume II Pass/Fail Requirements with a one page limit. Please confirm the only requirements for Volume II submission are confirmation the Offeror complies with submission instructions in 2.1 and 2.2 (PDF p. 60) and documenting whether or not the Offeror has any OCI or potential OCI issue(s) with associated mitigation (L.2.3).
A10. The Government confirms the only requirements for Pass/Fail Volume II submission is
2.1 Complying with the page limits, formatting requirements, file format requirements, and submittal instructions of Section 1.0 through 1.3.
2.2 Provide responses to all volumes.
2.3 Identify any and all conflict of interest or potential conflict of interest related to this solicitation and provide a mitigation plan to address conflicts/or potential conflicts. If potential conflicts of interest, the offeror shall provide in their mitigation plan narrating how personnel will handle safeguarding information.
If no conflicts of interest or potential conflicts of interest exist, provide a written statement certifying as such.
Q11. In reference to SOW 1.1.3:
Does the 20 days of travel over the period of performance refer to 20 person days (e.g., five resources for four days each at a final test event) or 20 days per resource (e.g., N resources traveling for four-five day trips each)?
A11: The 20 days represents up to 20 total calendar travel days over the period of performance of the contract. The number or resources required to support each of the 20 calendar travel days shall be determined based on the need for the resource to support each of the travel events. Resources required for each travel event shall be reviewed and only the necessary amount of resources shall travel.
Q12. In reference to the SOW:
If a single CR drives changes to five different interfaces, would that correspond to five work units (i.e., one per interface) or just one work unit?
A12: If a single configuration change request impacts five different interfaces that is considered a single work unit. Configuration change requests will be issued to implement a piece of system functionality (e.g correction of a system defect). Therefore, it is considered that if a configuration change request alters 5 different interfaces, the changes to each of the five interfaces will all be similar (e.g. adding the same single new data element to each of the five interface). If a single configuration change request results in multiple interface changes that are dissimilar from each other and the contractor believes the work is greater than a single work unit, the contractor and government will negotiate and agree on the number of work units for the configuration change request prior to the contractor accepting the configuration change request.
Q13. In reference to Section L Given the Government's minimum requirement for 20% small business participation for Volume V, the Offeror respectfully requests an extension by at least one week to allow Offerors the ability to provide adequate time for competitive solicitation of small business subcontractors to respond with price quotes.
A13. The Government will extend the proposal due by date by one week.
SECTION B - SUPPLIES OR SERVICES AND PRICES
CLIN 0001
The CLIN extended description has changed from:
Program Management and Technical Service in accordance with the Statement of Work (SOW), paragraphs 4.1, 4.3, 4.4, 4.5, 4.7, 4.8, and 4.9 in Section C.FY of Funds: 2021Type of Money: O&MNCustomer Code:
SUBMEPPSponsor: SUBMEPPTI #: N/A
To:
Program Management and Technical Service in accordance with the Statement of Work (SOW), paragraphs 4.1.1, 4.1.2, 4.1.3, 4.1.5, 4.1.7, 4.1.8, 4.1.9, 4.2, and 4.3 including all subparagraphs of these paragraphs in Section C.FY of Funds: 2021Type of Money: O&MNCustomer Code: SUBMEPPSponsor: SUBMEPPTI #: N/A
CLIN 0002
The CLIN extended description has changed from:
Program Management and Technical Service in accordance with the Statement of Work (SOW), paragraphs 4.2 and
4.6 in Section C.FY of Funds: TBDType of Money: TBDCustomer Code: TBDSponsor: TBDTI #: N/A
To:
Program Management and Technical Service in accordance with the Statement of Work (SOW), paragraphs 4.1.4 and 4.1.6 including all subparagraphs of these paragraphs in Section C.FY of Funds: TBDType of Money:
TBDCustomer Code: TBDSponsor: TBDTI #: N/A
(End of Summary of Changes)
File details come from the government source that posted it. Updated .