Questions and Answers_Amendment 0002.xlsx
XLSX spreadsheet 78 KB Posted
- Attached to
- National Weather Service Commercial Data Program (National Mesonet Program) Federal contract opportunity
- Solicitation number
- 1305M225R0027
About this file
This file is a Questions and Answers document for Amendment 0002 of the National Weather Service Commercial Data Program (National Mesonet Program) Request for Proposal (RFP). The solicitation seeks commercial weather data providers to supply various meteorological data types, including rawinsondes, aerial systems, buoys, ships, and other environmental observations. Key amendments include increasing the technical proposal page limit from 30 to 34 pages, clarifying pricing units and evaluation methods, and modifying past performance submission requirements.
The procurement is issued by the Department of Commerce's National Oceanic and Atmospheric Administration (NOAA), with an estimated contract start date between April and October 2026 and a maximum contract ceiling of $386.5 million. Offerors must submit detailed proposals covering technical capabilities, past performance, pricing for different data rights/licensing categories, and small business subcontracting plans. The government will evaluate proposals using the "Default NOAA Only" unit price and allows for pricing across multiple data distribution categories, with specific requirements for submission formatting, file naming conventions, and proposal content.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 1305M225R0027 Amendment 0003.pdf | ||
| Questions and Answers_Amendment 0003.xlsx | XLSX spreadsheet | |
| RFP_Attachment 3 - Past Performance Form_Amend 0003.docx | DOCX document | |
| 1305M225R0027 Amendment 0002.pdf | ||
| RFP_Attachment 2 - Price Exhibit_Amend 0002.xlsx | XLSX spreadsheet | |
| Questions and Answers_Amendment 0001.xlsx | XLSX spreadsheet | |
| RFP 1305M225R0027_Amendment 0001.pdf | ||
| RFP_Attachment 2 - Price Exhibit_Amend0001.xlsx | XLSX spreadsheet | |
| RFP_Attachment 3 - Past Performance Form_Amend0001.docx | DOCX document | |
| RFP_1305M225R0027.pdf | ||
| RFP_Attachment 1 - SOW.docx | DOCX document | |
| RFP_Attachment 3 - Past Performance Form.docx | DOCX document | |
| RFP_Attachment 2 - Price Exhibit.xlsx | XLSX spreadsheet | |
| RFP_Attachment 5 - Small Business Subcontracting Plan.docx | DOCX document | |
| RFP_Attachment 4 - Past Performance Questionnaire.docx | DOCX document |
Show all 15
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
Sheet1
| # | Answered In | Reference | Question/Comment | Answer |
| 1 | Amendment 0001 - Revised in Amendment 0002 | RFP, FAR 52.212-1(j)(2)(i), Page 67 | Original: Is the requested inventory of networks and infrastructure subject to the page limitation of Volume 2? |
Updated: In your first set of Q&As for the CDP procurement you state that if we felt it is unrealistic to include our inventory of networks and infrastructure in the Volume 2 page limitations, we should "contact the Contracting Officer and Contract Specialist" with rationale as to why it should be excluded or why there should be an increased page limit. Given this direction, we are reaching out directly to you with our rationale (below).
In order to best/compliantly show a detailed geographic distribution of the networks for each and every data type described in SOW 2.1, per RFP instructions, several pages are necessary. We suggest the Government either add additional pages (e.g., 3-4) to the existing 30-page limit for Volume 2, Technical Information or exclude this inventory requirement from page limitations. This will help prevent the incumbent from being penalized from a space perspective for allocating pages to include the existing and future, geographically expansive inventory of providers and platforms across ELINS. Original: Yes. If this is unrealistic, the offeror is instructed to contact the Contracting Officer and Contract Specialist with rationale as to why it should be excluded or increase the page limit.
Updated: The page limit has been increased by 4 pages from 30 pages to 34 pages. Amendment 0002 reflects this change.
| 2 | Amendment 0001 | RFP, FAR 52.212-1(j)(3)(i), Page 68; RFP Attachment 3 – Past Performance Form | The RFP states that Offerors are to provide no more than 5 recent and most relevant contracts; however, RFP Attachment 3 Past Performance Form states that up to 3 references can be used. Please confirm that the Offeror is to provide up to 5 past performance references. | This is a typographical error in the Past Performance Form. The Past Performance Form shall be updated to "5" references |
| 3 | Amendment 0001 | RFP, FAR 52.212-1(j)(4)(i), Page 68; RFP Attachment 2— Price Exhibit | Please confirm that the Offeror does not have to provide Unit Prices for all seven (7) Data Rights/Licensing Categories for each Extended Line Item Number (ELIN)? | Offer shall complete all pricing information. "Completeness is defined as all prices inserted for all unit price(s), amount(s), and total(s) for each ordering period of the attached Price Exhibit. Failure to submit a complete Price Exhibit may result in the offeror being immediately removed from |
further consideration." - 52.212-2, para (d), section (5).
| 4 | Amendment 0001 | RFP, FAR 52.212-1(j)(4)(i), Page 68; RFP Attachment 1— SOW | The RFP instructions and Statement of Work (SOW) do not define the units to be priced on RFP Attachment 2 (Price Exhibit) beyond the description of the Data Requirements in the SOW. Units are usually defined in terms of what is counted (e.g., stations, soundings, observations) and how often they are counted (e.g., daily, monthly). Without defined units, the Government is likely to receive widely disparate pricing that cannot be normalized. Please clarify the definitions of the units to be priced for each ELIN. | This was specified in the Price Exhibit as "Description (per month per data type)". However, the unit of issue has been replaced from "Ea" to the respective price per month for further clarity. This has been updated in the Price Exhibit of Amendment 0001. | |
| 5 | Amendment 0001 | RFP Attachment 1—SOW | SOW Sec. 2.1.4 combines rawinsondes and Uncrewed Aerial Systems (UAS) in one Data Requirements category. Because weather balloons and UAS are such starkly different platforms with significantly different price points, we recommend the Government separates these into separate Data Requirements categories to ensure accurate and balanced pricing. | The Price Exhibit is updated in Amendment 0001 to reflect the separation of those two platforms. | |
| 6 | Amendment 0001 | RFP Attachment 1—SOW | SOW Sec. 2.5.4 requires notification to the Government on requested data rights/licensing categories “beyond NOAA only,” but SOW Appendix B does not contain a NOAA- only category. Historically, National Mesonet Program Data Rights/Licensing Categories have included a NOAA- only option, and many commercial data providers will only provide data to NOAA for its sole use. Suggest the Government consider adding a NOAA-only Data Rights/Licensing Category to Appendix B as the price for this category will be more cost effective for the Government in many cases and if not included a substantial amount of commercial data may not be made available to the Government. | The Appendix B introduction refers to "NOAA only" but has also been clearly broken down in the updated Price Exhibit to distinguish "NOAA only" and that being the default type of data. | |
| 7 | Amendment 0001 | RFP, FAR 52.212-1(j)(iv), Page 67 | The RFP does not provide any suggested small business subcontracting goals. Will the Government provide specific suggested goals or should Offerors develop their own goals using the overall Department of Commerce goals as guidance? | Offerors shall propose their small business subcontracting goals based on the technical solution that is being proposed. | |
| 8 | Amendment 0001 | RFP, NAM 1330-52.208-70, Page 28 | The RFP requires an AbilityOne subcontracting goal. To our knowledge, the AbilityOne Contractor does not provide weather data, which would make meeting any AbilityOne subcontracting goal impossible on this data purchasing contract. Given this, would the Government consider removing the AbilityOne subcontracting goal requirement? | There are no mandatory contractual requirements to subcontract with AbilityOne. The Government encourages the prime contractor to provide subcontracting opportunities to AbilityOne contractors. The Government will review the Offeror’s proposed plan for using AbilityOne contractors and will consider the extent to which qualified AbilityOne contractors are proposed to perform aspects of the requirement, including work associated with the functional requirements of the SOW. | |
| 9 | Amendment 0001 | RFP, FAR 52.212-1(i), Page 66; RFP Attachment 3— Past Performance Form | Per RFP instructions, font sizes must be no smaller than Times New Roman, size 10 type and spacing should be no smaller than single-spaced. Is the Offeror permitted to modify the font and line spacing of the provided Past Performance Form template required in Volume 3, Past Performance Information? Also, is it permissible to add Offeror headers and proprietary footers to the template? | Yes, the offeror is allowed to modify font, spacing, add headers, and proprietary footers on the Past Performance Form as long as the information requested in RFP template is provided. Do not rearrange order or change key elements of the template. | |
| 10 | Amendment 0001 | RFP, FAR 52.212-1(l), Page 71 | Does the Government have preferred or suggested file names for submission files for Volumes 1–4? | Follow the naming convention established in the RFP for each volume but with the offeror's name in front. For example: Contractor Name_Volume 1, Proposal Information. Attachment example: Contractor Name_Volume 1, Proposal Information_Attachment 1 | |
| 11 | Amendment 0001 | RFP, FAR 52.212-1 Instructions to Offerors - Commercial Products and Commercial Services - Addendum(i), Page 66 | To ensure readability and effective communication, would the Government allow any professional, legible font in graphics, rather than restricting to Times New Roman 10 point, which may reduce clarity, distort layout, and impact evaluation? | Proposals must use a font from the following list: Arial, Calibri, or Times New Roman. The minimum font size remains 10-point. This standardization requirement is in place to ensure readability and fair evaluation for all submissions. Arial and Calibri will be added in Amendment 0001 | |
| 12 | Amendment 0001 | RFP, FAR 52.212-1 Instructions to Offerors - Commercial Products and Commercial Services - Addendum(j)(2)(iv), Page 68 | Because the Transition Plan requirement (with schedules, dependencies, and communications process) applies only to non-incumbents, will the Government allow this section to be submitted as an appendix outside the 30-page limit to ensure equal footing for all offerors? | A transition plan is a required element for all offerors, regardless of their incumbent status, as it is listed as an evaluation criterion in the solicitation. An offeror making an assumption to the contrary would be doing so at their own peril, and it could lead to their proposal being deemed non-compliant and being eliminated from consideration. "If applicable" shall be removed in Amendment 0001 within section iv of the reference given. | |
| 13 | Amendment 0002 | RFP Attachment 2— Price Exhibit | For ELIN 1004 – Rawinsondes and ELIN 1005 – Other Aerial Systems, these units have traditionally been quantified either as (A) the number of soundings/vertical profiles or (B) by service month (“balloon-months”). The current listing appears to combine these two measures, making it difficult to price accurately. Could NOAA please clarify the intended unit of measure for these ELINs? | The government has reviewed the entire Price Exhibit and provided revised estimated quantities and units of issue as needed. See Amendment 0002. | |
| 14 | Amendment 0002 | RFP, FAR 52.212-1 Instructions to Offerors - Commercial Products and Commercial Services - Addendum(j)(4)(i) | Regarding evaluation pricing, the RFP states in provision 52.212-1 (j)(4)(i) that the data rights category with the highest price will be used. As currently structured, Category 1 provides for unrestricted redistribution, allowing NOAA to make all data broadly available without limitation. When applied to proprietary private-industry data (which comprises a large portion of the data), this Category 1 level of distribution rights is expected to require substantially higher pricing compared to more limited categories such as “Default NOAA Only.” In practice, this means Category 1 is likely to represent the highest cost, and applying it to proprietary data sets in combination with the stated quantities will almost certainly dramatically exceed the RFP’s $386.5 million contract ceiling. | ||
| Could NOAA clarify whether it would consider using the “Default NOAA Only” price as the basis for evaluation instead of the highest category price? This approach may provide a more realistic and manageable evaluation framework that will stay below the RFP's contract ceiling. | As specified in FAR 52.212-1(g), 52.212-1(j), and CAR 1352.216-75, the government anticipates a maximum contract value at either $386.5M or the best value contractor’s proposed total contract value/price, whichever is higher. |
Clause FAR 52.216-19, Order Limitations, has been updated to include 'or the contractor’s proposed total contract value/price, whichever is higher.' to match all other RFP language.
Total Evaluated Price: For the purposes of establishing a Total Evaluated Price, the Government will utilize the “Default NOAA Only,” unit price (Price Exhibit Column E) multiplied by the estimated quantity (Price Exhibit Column C) to calculate the Extended Amount (Price Exhibit Column F) for each ELIN. The sum of all the ELIN's will be the Total Evaluated Price. The “Default NOAA Only” is historically the most commonly utilized data category.
Total Maximum Contract Ceiling: For the purposes of establishing a Total Maximum Contract Ceiling, the Government will utilize the estimated maximum of $386.5M or the Total Maximum Contract Ceiling, whichever is higher. To determine the Total Maximum Contract Ceiling, the Government will utilize the highest per unit price (Price Exhibit Column E) for each platform multiplied by the estimated quantity (Price Exhibit Column C) to calculate the Extended Amount (Price Exhibit Column F) for each ELIN. The sum of all the ELIN's will be the Total Maximum Contract Ceiling. See Amendment 0002.
15 Amendment 0002 RFP, FAR 52.212-1 Instructions to Offerors - Commercial Products and Commercial Services - Addendum (j)(3) The solicitation requires that if an IDIQ, BPA, or other indefinite delivery vehicle is submitted as a past performance reference, the offeror must provide extensive supplemental details including order numbers, values, FTEs, and a description of the methodology used to ensure timely and quality performance. For large and complex IDIQs with up to 50 task orders, this level of detail can be quite lengthy. Will the Government permit the additional information required for IDIQ/BPA vehicles to be submitted as an attachment outside of the page count limitation for the Past Performance Volume? Volume 3, Past Performance, page limit is increased by 5 pages from 25 to 30 total pages.
In order to not unduly burden offerors, the Past Performance submission information has been updated as follows:
"in addition to the minimum information required in the attached Past Performance Form, the offeror must also provide the total number of orders issued, the associated value of each order, each order number, total average order value, and a list of no more than 10 of the most recent and relevant individual orders, number of full-time equivalents performing under each order, and description of the methodology used to ensure timely and quality performance across all orders. to include identification number (order/call number), dollar value, dates of performance, project/task order title." It is the offeror's responsibility to tell the government how the overall IDIQ/BPA/etc. reference are relevant/recent as relates to the solicitation within the Past Performance Form.
As government agencies vary on how CPARs are reported, either at the order level or at the base contract level, the Past Performance submission narrative within FAR 52.212-1(j)(3) will be updated in Amendment 0002 to include instructions for submitted CPARs for IDIQ/BPA/etc: "For IDIQ, BPA or other indefinite delivery vehicle contracts, provide the completed CPAR for each of most recent and relevant individual orders listed by the offeror in the requested supplemental individual order details."
See Amendment 0002.
| 16 | Amendment 0002 | RFP, FAR 52.212-1(j)(1)(iv), Page 67; RFP, Attachment 5- Small Business Subcontracting Plan | Please confirm that the provided Small Business Subcontracting Plan template is for guidance only and offerors are not required to use the actual template as their Small Business Subcontracting Plan. | The template provided is the NOAA Small Business Subcontracting Plan template from the NOAA Small Business Office. If submitting a Small Subcontracting Plan other than in the template provided, it shall include the required information in FAR 19.704, Subcontracting Plans. See Amendment 0002. |
| 17 | Amendment 0002 | RFP, FAR 52.2121(j)(1)(iv), Page 67; RFP, Attachment 5- Small Business Subcontracting Plan | Please confirm that offerors may submit a DCMA approved Master Subcontracting Plan pursuant to FAR Part 19.704(b) instead of an Individual Subcontracting Plan and instead of the provided Small Business Subcontracting Plan template. | No, we are requesting specific Small Business goals. As Small Business goals are not required within a Master Subcontracting Plan, an Individual Subcontracting Plan is required. |
| 18 | Amendment 0002 | RFP, FAR 52.212-1(h), Page 65-66 | FAR 52.212-1(h) reads: The offeror shall state in their proposal that they agree to hold their offer open until an award is made unless the offeror formally withdraws their proposal via a written notice at any time before award. Question: Considering the opportunity is being bid as fixed unit prices, would the government consider a 180-day validity period instead of an open-ended period in order to allow Offerors an opportunity to validate their price per unit should the award date slip beyond 180 days from proposal submission? | An offeror shall give their "best and final" price under the assumption that no requests for revised proposals will be requested, as the government reserves the right to award without discussions. However, if an award is not made 270 days from solicitation close, and assuming no revised proposals have been sought, the Government will give offerors the opportunity to validate pricing. See Amendment 0002. |
| 19 | Amendment 0002 | RFP Amend 0001; RFP, Attachment 2 - Price Exhibit Amend 0001; RFP, Attachment 1 - SOW | Amendment 1 amended the RFP and the pricing exhibit to add a NOAA-only distribution category and split up rawinsondes and UAS into separate categories and buoys and ships into separate categories, but these remain unchanged in the SOW. Is the Government going to modify the SOW to be in line with these changes, or should offerors rely on just the RFP amendments and amended pricing exhibit to proceed with these changes in their proposals? | The Amendment 0001 pricing exhibit was updated to allow offerors to provide separate prices as requested under Question 5 to ensure accurate and balanced pricing for potentially significantly different price points. The data requirements established by the SOW for these platforms (e.g. rawinsondes, UAS, buoys and ships) remain unchanged regardless of how offerors identify price per platform. Therefore, the government does not anticipate revising the SOW to separate these platforms since the underlying SOW requirements are the same according to each platform. |
20 Amendment 0002 RFP, FAR 52.212-1(j)(3)(i), Page 69 Per RFP instructions, for a past performance reference that is an IDIQ contract, the Offeror is to provide the total number of orders issued, the associated value of each order, each order number, number of full-time equivalents performing under each order, and description of the methodology used to ensure timely and quality performance across all orders. For some IDIQ contracts this could be up to 100+ task orders, with considerable space required to provide all the requested information. Given the considerable space these lists will take away from the rest of the past performance information content, would you consider allowing this information be outside the 25-page limit? If it will not be outside the 25-page limit, is there a specific place in the template where it should be provided? Volume 3, Past Performance, page limit is increased by 5 pages from 25 to 30 total pages.
In order to not unduly burden offerors, the Past Performance submission information has been updated as follows:
"in addition to the minimum information required in the attached Past Performance Form, the offeror must also provide the total number of orders issued, the associated value of each order, each order number, total average order value, and a list of no more than 10 of the most recent and relevant individual orders, number of full-time equivalents performing under each order, and description of the methodology used to ensure timely and quality performance across all orders. to include identification number (order/call number), dollar value, dates of performance, project/task order title." It is the offeror's responsibility to tell the government how the overall IDIQ/BPA/etc. reference are relevant/recent as relates to the solicitation within the Past Performance Form.
As government agencies vary on how CPARs are reported, either at the order level or at the base contract level, the Past Performance submission narrative within FAR 52.212-1(j)(3) will be updated in Amendment 0002 to include instructions for submitted CPARs for IDIQ/BPA/etc: "For IDIQ, BPA or other indefinite delivery vehicle contracts, provide the completed CPAR for each of most recent and relevant individual orders listed by the offeror in the requested supplemental individual order details."
See Amendment 0002.
21 Amendment 0002 RFP, FAR 52.212-1(l), Page, 71 Is there a file size limit for e-mail submission of the proposal volumes and respective attachments? If so, can we submit proposal files in separate e-mails, as/if needed? NOAA has an email size limit of 25MB. If offerors submit their proposal in separate emails to meet email size limitations, it is requested they annotate the email title with "Part 1 of _", "Part 2 of __" etc., or similar identification that clearly identifies the current email number with a total amount of emails to be submitted. See Amendment 0002.
It remains the offeror's responsibility to ensure all proposal information is timely received by Paul Thomas and Jennifer Roesner.
| 22 | Amendment 0002 | N/A | What is the assumed contract start date for purposes of pricing and other aspects of the proposal? | Estimated start date is April 2026 (not including transition) but could extend to October 2026, as needed. These are estimates only, subject to change and dependent upon many factors. |
| 23 | Amendment 0002 | RFP, Attachment 1 – SOW Appendix B | Data Rights/Licensing Categories 2 and 3 contain the clause “but not for further distribution.” This same clause, however, is not reflected in Data Rights/Licensing Category 4. Will the government consider adding that clause to Category 4 to ensure redistribution data rights are applied consistently across the categories and to support development of balanced pricing? | RFP, Attachment 1 – SOW Appendix B remains unchanged. The government notes that data will not be distributed beyond what is stated for any Data Rights/Licensing Categories. Specifically for Category 4, this redistribution includes nonprofit entities and academic entities for non-commercial use, with inherent scientific expectations to allow data sharing for validation purposes. |
File details come from the government source that posted it. Updated .