Questions and Answers_Amendment 0001.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 document is a Questions and Answers file (Amendment 0001) for the National Weather Service Commercial Data Program (National Mesonet Program) solicitation. The Q&A addresses critical proposal submission details, including clarifications on past performance references (5 references allowed), pricing exhibit requirements, and data rights/licensing categories. Key modifications include separating rawinsondes and Uncrewed Aerial Systems (UAS) into distinct data requirement categories and updating the Price Exhibit to provide more clarity on unit pricing and data rights.
The Q&A also provides guidance on proposal preparation, such as font requirements (Arial, Calibri, or Times New Roman, 10-point minimum), file naming conventions, and small business subcontracting goals. Notable clarifications include the requirement for all offerors to submit a transition plan, encouragement to include AbilityOne subcontractors without mandatory requirements, and flexibility in formatting the past performance form while maintaining the core requested information. The solicitation is issued by the Department of Commerce's National Oceanic and Atmospheric Administration (NOAA) and seeks commercial weather data providers.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| RFP_Attachment 3 - Past Performance Form_Amend 0003.docx | DOCX document | |
| Questions and Answers_Amendment 0003.xlsx | XLSX spreadsheet | |
| 1305M225R0027 Amendment 0003.pdf | ||
| 1305M225R0027 Amendment 0002.pdf | ||
| RFP_Attachment 2 - Price Exhibit_Amend 0002.xlsx | XLSX spreadsheet | |
| Questions and Answers_Amendment 0002.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_Attachment 4 - Past Performance Questionnaire.docx | DOCX document | |
| RFP_Attachment 2 - Price Exhibit.xlsx | XLSX spreadsheet | |
| RFP_Attachment 5 - Small Business Subcontracting Plan.docx | DOCX document | |
| RFP_1305M225R0027.pdf | ||
| RFP_Attachment 1 - SOW.docx | DOCX document | |
| RFP_Attachment 3 - Past Performance Form.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
| # | Reference | Question/Comment | Answer |
| 1 | RFP, FAR 52.212-1(j)(2)(i), Page 67 | Is the requested inventory of networks and infrastructure subject to the page limitation of Volume 2? | 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. |
| 2 | 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 | 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 | 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 | 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 seperation of those two platforms. |
| 6 | 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 | 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 | 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 | 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 | 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 | 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 1 |
| 12 | 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 1 within section iv of the reference given.
File details come from the government source that posted it. Updated .