NOAA Commercial Data Buy Proposal Compliance Gap Analysis

Direct Temperature Sounding Channels

Must have spectral channels enabling direct temperature sounding

Describes multiple channels in 50–60 GHz O2 and near 118 GHz for temperature profiling and vertical sensitivity

Covered

Would be stronger with explicit channel list/frequencies and mapping to spectral guidance Table 2.

Direct Moisture Sounding Channels

Must have spectral channels enabling direct moisture sounding

Describes multiple channels near 183 GHz water vapor absorption; channel spacing selected for weighting functions

Covered

Would be stronger with explicit channel list/frequencies.

Nadir Horizontal Resolution

≤32 km (temperature); ≤16 km (moisture)

Explicitly states meets Table 3 thresholds ≤32 km / ≤16 km

Covered

No gap.

L1B Latency

≤60 minutes from acquisition to receipt into NCCF

Explicitly states L1B latency at or below 60 minutes to receipt into NCCF; target better nominally

Covered

Consider describing measurement method/clock synchronization and evidence from operational logs.

NEDT Temperature

Better than ATMS-level NEDT x 2

States meets threshold (ATMS NEDT x2) and trends on-orbit

Covered

No numeric NEDT values provided; risk of “assertion-only” without data sheet.

NEDT Moisture

Better than ATMS-level NEDT x 2

States meets threshold (ATMS NEDT x2)

Covered

Same evidence-strength note as above.

Radiometric Calibration Accuracy

1–2 K depending on channels

States meets 1–2 K; describes calibration chain; will provide uncertainty budgets/drift metrics

Covered

Provide per-channel accuracy table and definition (e.g., 1-sigma vs max error) for clarity.

Availability Regional Coverage (>=75%)

Contractor shall provide data covering at least 75% of the region averaged over platform orbital coverage for designated period (stated in SOW narrative around Table 3)

States constellation-level availability >=70% average daily; does not mention 75% region coverage requirement

Gap

Potential major technical compliance risk if evaluator treats 75% coverage as part of threshold expectations; add explicit statement and metric definition/method.

Striping Effect Minimization

Striping should be minimized as much as possible; measurement stability essential

Mentions NOAA emphasis on stability/minimize striping; describes bias monitoring, nonlinearity correction, stability checks; QC flags

Partially Covered

Good narrative, but lacks quantified striping metrics/acceptance criteria and how NOAA can validate.

ATBDs

Provide ATBDs describing rationale, methodology, assumptions

Commits to ATBDs for calibration, geolocation, QC, L1C resampling; includes assumptions/error propagation

Covered

—

Spectral response functions

Provide SRFs

Explicitly included

Covered

—

Polarization information

Provide polarization info

Explicitly included

Covered

—

Limb correction coefficients (if applicable)

Provide limb correction coefficients

States will provide limb correction coefficients if applicable

Covered

Ensure applicability determination is documented.

CRTM coefficients

Provide CRTM coefficients for each sensor

Explicitly included

Covered

—

Pre-launch calibration reports

Provide pre-launch calibration reports

Explicitly included

Covered

—

On-orbit calibration reports

Provide on-orbit calibration reports

Explicitly included

Covered

—

QC flags documentation

Document QC flags & cal/val indicators

States will provide QC flag semantics and stability/bias summaries

Covered

—

User guides

Provide user guides

Explicitly included

Covered

—

Detailed data specification documents

Provide data specification docs defining file contents/fields

Explicitly included

Covered

—

Instrument description & sampling characteristics

Describe instrument(s) and sampling characteristics

Describes constellation/instrument lineage, scan geometry/fields included; not a dedicated instrument spec section

Partially Covered

Add explicit instrument sampling parameters (scan rate, swath width, incidence angles, footprint spacing, polarization per channel).

Stability metrics for each instrument

Provide pre-launch characterization + on-board calibration + stability metrics for each instrument

Mentions stability checks, drift metrics, channel-by-channel bias monitoring; commits to provide summaries

Partially Covered

Add explicit per-instrument metric set and reporting cadence/format.

DR-01

Grant NOAA perpetual, non-exclusive, irrevocable, worldwide license for use/reproduce/create derived/value-added products; authorize others

Explicitly acknowledges and accepts NOAA required data rights; includes perpetual, non-exclusive, irrevocable, worldwide license and authorization to others

Covered

Good.

DR-02

NOAA distribution rights: distribute contractor-provided data to USG, foreign partners, eligible research entities for non-commercial use with no further distribution; NOAA derived/value-added products can be distributed without restriction

Proposal states distribution rights to USG, foreign partners, eligible research entities for non-commercial use with no further distribution of contractor-provided data; acknowledges NOAA rights for derived products

Covered

Ensure your rights statement does not inadvertently limit NOAA’s unrestricted distribution of NOAA-derived/value-added products.

DR-03

Contractors define distribution rights for documentation; proprietary/confidential docs treated as vendor-proprietary; NOAA will protect from unauthorized disclosure

States will mark proprietary/confidential docs; references SOW Section VII handling; will provide distribution rights statements for all documentation

Covered

No gap.

DR-04

Avoid unauthorized restrictive markings; align with FAR 52.227-14 processes

States will structure markings to avoid improper restriction of Government rights

Partially Covered

Add explicit confirmation that any limited rights/restricted markings will follow FAR 52.227-14 Alt II and will not be applied to data where Government has unlimited rights.

SUB-01

3 volumes required: Business, Technical, Price

Proposal is explicitly organized as Volume I Business, Volume II Technical, Volume III Price

Covered

Meets organizational requirement.

SUB-02

Business volume must include reps/certs/acknowledgments, identification of technical data to be withheld, acceptance period (>=90 days), authorized negotiator

Includes FAR/NOAA clause compliance acknowledgments; includes technical data to be withheld section; acceptance period 120 days; authorized negotiator named

Covered

Ensure SF1449/representations referenced are actually included in submission package if required by solicitation.

SUB-03

Technical volume: demonstrate ability; merely restating minimum specs is insufficient; include risks/mitigations; identify all satellite constellations used

Technical narrative provides operational capability statement, detailed performance claims, risks/mitigations, identifies “AstraSound MWS-LEO constellation (2 satellites)”

Covered

Would benefit from more quantitative evidence artifacts (e.g., sample latency/availability metrics) to strengthen “demonstrated” claims.

SUB-04

Technical volume page limit 20 single-spaced pages (excess disregarded)

Page count not verifiable from provided text

Not Verifiable

Packaging/format verification not possible from text-only extract; risk if actual submission exceeds limit (evaluation may disregard excess).

SUB-05

Price volume must include completed Attachment 2 or equivalent; include Level 0 & Level 1 pricing and option for Level 2; price completeness required or may be rejected as non-responsive

States Attachment 2 completed in files; narrative states Level 0/1 priced and Level 2 option included

Partially Covered

No actual price schedule values shown; evaluator will check line-item completeness—ensure Attachment 2 is fully populated and consistent with stated satellites/min ordering quantity.

SUB-06

Submission method: email to CO and CS; subject includes company name + solicitation number; 25MB per email; timely receipt based on email received time; offeror responsible to confirm receipt

Acknowledges email size limitations, electronic submission, timely receipt determined by NOAA received time; communications via email; identifies CO/CS addresses

Partially Covered

Does not explicitly state subject line convention or explicit plan to confirm receipt (though acknowledges responsibility). Minor admin risk.

SUB-07

Provide (minimum) company name, phone, address, UEI, email, price proposal, business proposal, technical proposal

Company name provided; UEI/address/POCs stated will be in executed SF1449 package; technical and business provided; email to CO/CS noted

Partially Covered

UEI/phone/address not included in the provided text (deferred to SF1449). Risk if evaluators expect it within Business Volume itself as per addendum minimums.

SEC-01

Comply with CAR 1352.239-72 (including §i System Accreditation Package obligations)

Commits to comply; references CAR 1352.239-72; describes accreditation package support and baselines

Partially Covered

Proposal does not explicitly commit to the 14-day System Certification Work Plan submission requirement (CAR 1352.239-72(i)(1)) or describe readiness to meet it.

SEC-02

Data delivery to NOAA ingest via HTTPS (preferred) or SFTP; use data integrity method compliant with NESDIS ICD and approved by NOAA

States HTTPS preferred; SFTP alternate; integrity verification consistent with NESDIS ICD

Covered

Would be stronger to name integrity method (e.g., checksum algorithm, signing) subject to NOAA approval.

SEC-03

Personnel screening for user accounts per CAM 1337.70 (as applicable)

Not addressed

Gap

Potential compliance gap if contractor personnel require accounts/access; add statement committing to required screening level and process trigger.

SEC-04

Within 5 days after award: certify initial DOC IT security orientation training; annual refresher thereafter

States will provide certifications within required timelines after award and annual refresher certifications

Covered

Good.

SEC-05

Within 5 days after award: provide signed acknowledgement re CAR 1352.209-72 Restrictions Against Disclosures

Mentions signed acknowledgements required by CAR 1352.239-72 and restrictions against disclosures

Partially Covered

Does not explicitly cite CAR 1352.209-72 nor commit to delivery within 5 days; tighten language.

SEC-06

DOC/OIG access for IT inspection/audit; flow down clause to applicable subcontracts

Commits to audit rights; ensures subcontractors bound to equivalent security obligations; mentions flowdowns

Covered

Good.

SEC-07

Alternate accreditation methodologies allowed only with COR approval; provide analysis vs NIST SP 800-53 high impact baseline identifying gaps

States will propose equivalency mapping to NIST SP 800-53 high impact baseline; will not implement without COR approval

Covered

Good.

SEC-08

Maintain logging, access control, vulnerability management, incident response aligned to NIST-based controls

Explicitly states these controls aligned to NIST

Covered

Consider adding whether FedRAMP-authorized cloud services are used (if applicable) and boundary description.

NOAA Sexual Assault & Sexual Harassment Prevention/Response (NOAAAM 1330-52.222-70)

Contractor should develop/enforce policy; must flow down to subcontracts; mandatory training + evidence submission requirements

Not mentioned

Gap

Compliance gap; may be raised post-award as a contractual obligation; include acknowledgement and training evidence submission commitment.

Post-Government employment restrictions notice (NOAAAM 1330-52.203-71)

Contractor acknowledges restrictions; provides notice to former NOAA employees providing service

Not mentioned

Gap

Add acknowledgement to avoid compliance friction.

Electronic submission of payment requests via IPP (NOAAAM 1330-52.232-71)

Must submit payment requests through IPP; exceptions require written request

States will submit via IPP; registration implied

Covered

Consider adding statement that you will register/use IPP and understand exception process.

Submit invoices to COR by 10th day of subsequent month (NOAAAM 1330-52.242-70)

Invoice timing and routing requirements

Explicitly commits to submit by 10th day; route to COR with copy to CO; FAR 52.212-4(g) elements

Covered

—

Organizational Conflict of Interest (CAR 1352.209-74)

OCI clause applies; expect disclosures/mitigation where relevant

Only general acknowledgement of clause list; no OCI statement

Partially Covered

If no OCI exists, add explicit “no OCI” statement; if potential OCI, provide mitigation approach.

Compliance with laws (CAR 1352.209-73)

Comply with laws

General acknowledgement included

Covered

—

Combating Trafficking in Persons (RFO 52.222-50)

Clause applies

Only listed in clause acknowledgements; no narrative

Partially Covered

Add explicit compliance statement and flowdown acknowledgement.

EVAL-01

Only offerors with operational capabilities at time RFP released will be considered; include affirmation statement

States “commercial service offering currently in an operational state as of the RFP release date” and “capabilities… in a current operational state at the time the RFP was released”

Covered

Strong alignment; consider adding concise, explicit compliance statement mirroring solicitation language verbatim for evaluator ease.

EVAL-02

Technical Capability significantly more important than Price; Govt may award other than lowest price

Acknowledges best-value tradeoff and technical more important than price

Covered

No gap.

EVAL-03

Technical volume specs become contract minimums if awarded

Implicitly acknowledges alignment to threshold requirements and SOW; does not explicitly accept incorporation as minimums

Partially Covered

Add explicit statement accepting incorporation of Technical Volume specifications as minimum contract requirements to remove ambiguity.

EVAL-04

Identify risks affecting timely delivery/data quality incl launch/licensing/downlink limits and mitigations

Risk section includes spacecraft anomalies, ground station outages, cloud disruptions, RFI; notes licensing delays for future additions but baseline uses on-orbit assets

Covered

Good; could add quantified residual risk/assumptions (e.g., contact schedule, cloud region).

SCRA cooperation & questionnaire

Provide any info DOC deems necessary incl questionnaire; continuing obligation to amend info

Explicitly acknowledges; commits to questionnaire and updates

Covered

—

Gov right to reject for unacceptable risk

DOC may reject without recourse

Explicitly acknowledges

Covered

—

Non-destructive/destructive testing

DOC may test systems/equipment/software

Explicitly agrees to cooperate

Covered

—

Flowdown to subcontracts

Include SCRA language in all subcontracts involving IT system/hardware/software

States will flow down required SCRA language to applicable subcontractors/suppliers

Covered

—

Provide enumerated SCRA Information set (identity, subs, foreign ownership, officer DOBs, security programs, facility locations, separation of duties, transport, service agreements, disposal)

Government may request; contractor shall submit; must be marked and securely transmitted; accuracy representation

Commits generally to provide information requested about development/manufacturing/packaging/storage/transport; does not address officer DOBs, foreign ownership/control, disposal identity, separation of duties explicitly

Partially Covered

Add explicit commitment to provide each enumerated data element upon request and to mark/transmit per FAR 3.104-4 as required.

R-01

Technical non-compliance concern regarding 75% regional coverage expectation

Proposal addresses 70% availability but does not explicitly commit to “data covering at least 75% of the region averaged over orbital coverage”

Medium

High

Add explicit commitment to 75% regional coverage requirement (define region basis) and provide method/metrics demonstrating compliance from operational data.

R-02

Security accreditation compliance risk (CAR 1352.239-72(i))

No explicit commitment to System Certification Work Plan submission and System Accreditation Package elements required for interconnection/processing DOC data

Medium

High

Add explicit statement of compliance with CAR 1352.239-72(i)(1)-(3), including readiness to provide Certification Work Plan, SSP, and supporting artifacts; clarify system boundary.

R-03

Administrative non-responsiveness risk if UEI/phone/address not present in Business Volume

Proposal defers UEI/address to SF1449 package rather than including within Business Volume as “minimum” detailed information

Low

Medium

Include UEI, business address, phone, and proposal contact email within the Business Volume body to match Section C addendum minimums.

R-04

SCRA evaluation friction due to incomplete acknowledgment of enumerated data elements

Proposal commits generally but not to specific required elements (foreign ownership, officer DOBs, disposal provider, separation of duties, etc.) and secure marking/transmission

Medium

Medium

Add explicit commitment to provide each enumerated SCRA information element and to mark/securely transmit as source selection information per FAR 3.104-4.

R-05

Lower technical confidence due to assertion-only performance claims (NEDT/latency/striping)

No quantitative data sheet, sample metrics, or test evidence included in narrative

Medium

Medium

Add supporting evidence exhibits/appendices (within page-limit rules) summarizing measured NEDT by channel, latency distributions, availability history, and striping/stability metrics.

R-06

Post-award compliance exposure for workforce conduct/training clauses

No mention of NOAA SASH policy/training or post-government employment restrictions notice

Medium

Medium

Add acknowledgements, flowdown commitments, and training evidence submission approach for NOAAAM 1330-52.222-70 and NOAAAM 1330-52.203-71.

DEL-01

Acceptance contingent on continuous 7-day stream with no critical errors/interruptions; if rejected Govt notifies within 5 business days; contractor correct/resubmit within 5 business days at no cost; acceptance upon written confirmation

States accepts 7-day stream acceptance; commits to correct/resubmit within five business days at no additional cost; implement root-cause actions

Covered

Strong.

DEL-02

Follow NESDIS methods/protocols; deliver for secure ingest to NCCF per NESDIS ICD or alternative secure ingest methods

Commits to NESDIS ICD alignment; mentions Innovation Hub cloud services as directed; naming conventions/manifests

Covered

Consider citing specific ICD version and any existing ingest testing performed.

DEL-03

Data descriptor files conform to ISO 19115-1:2014 and ISO 19139-1:2019

Explicit commitment to ISO 19115-1 and ISO 19139-1 conformance and elements

Covered

Add example metadata record excerpt or checklist to demonstrate completeness.

DEL-04

Data only from satellites with WMO identifier or unique internationally recognized identifier (e.g., COSPAR ID)

States WMO assignment in process; will provide COSPAR ID and unique identifier where WMO pending; maintain traceability

Covered

Ensure actual delivery metadata includes the identifier consistently.

DEL-05

Level 1 products compatible with NOAA operational processing/assimilation systems (e.g., ATMS-like)

States designed for NOAA compatibility; coordinate with COR; provides required fields; mentions BUFR option

Partially Covered

Needs explicit statement of which NOAA formats are supported by default (e.g., netCDF conventions, specific ingest schema) and evidence of successful test ingest.

DEL-06

Target >=70% average daily data availability at constellation level

Explicit commitment engineered to meet/exceed 70%; daily reporting planned vs unplanned gaps

Covered

Aligns well.

DEL-07

Maintain continuous & contiguous NRT delivery; minimum: continuous/contiguous along-track for one satellite; one satellite = minimum order qty

Explicitly commits to continuous/contiguous along-track for one satellite; states minimum ordering quantity one satellite

Covered

No gap.

DEL-08

L1B latency meets Table 3

Explicitly commits <=60 minutes to NCCF

Covered

No gap.

DEL-09

Ensure cross-platform data consistency; mix-and-match interoperability

Explicitly commits; single calibration algorithm baseline; inter-satellite checks

Covered

Good.

DEL-10

Provide Level 0 data spanning 1–3 months upon anomaly/request

Explicitly acknowledges; describes Level 0 archive contents and secure delivery coordination

Covered

No gap.

DEL-11

May provide BUFR; if provided must conform to WMO standards and NOAA formatting/validation/ingest requirements

States can provide BUFR; will validate prior to cutover

Partially Covered

Clarify whether BUFR is optional deliverable vs on-request, and commit to NOAA-defined templates/messages.

Phase structure

Phase 1 Prep (3 mo), Phase 2 Delivery (6–12 mo), Phase 3 Evaluation (3 mo); period of performance 06/01/2026–05/31/2027

Acknowledges base POP 06/01/2026–05/31/2027; describes Phase 1/2/3 and pricing aligned; assumes Phase 2 12 months unless shortened by NOAA

Partially Covered

SOW indicates vendors not previously evaluated may be considered for 6-month delivery and must complete all phases; proposal should state whether previously evaluated and accept possible 6-month Phase 2 scenario.

Kickoff meeting

Participate in post-award kickoff no later than 2 weeks after award

States ready to participate within two weeks of award

Covered

—

Phase 1 deliverables

Provide necessary tech documentation, format specs, sample data, engineering support; deliver 24 hours of sample data

States Phase 1 covers format specs, sample datasets, engineering support, and required 24 hours sample data

Covered

—

Phase 3 support

Available for limited engineering/technical support during Govt evaluation

States Phase 3 includes limited support, diagnostic questions, Level 0 extraction participation

Covered

—

REC-01

Add an explicit statement committing to the SOW narrative requirement: “provide data covering at least 75% of the region, averaged over the platform’s orbital coverage for the designated period,” including your definition of the region and computation method (and how it differs from/relates to 70% availability).

SOW §II.B/Table 3 narrative (75% coverage) + §III availability target

Removes a potential threshold-compliance ambiguity and strengthens evaluator confidence.

REC-02

Augment the Technical Volume with a concise channel plan: list channel center frequencies/bandwidths/polarization and map them to Table 2 guidance and Table 3 threshold functions (temperature vs moisture).

SOW §II.B, Table 2 & Table 3

Converts qualitative assertions into clear, reviewable compliance evidence.

REC-03

Provide quantitative performance evidence summaries (tables/plots) from the operational system: latency distribution to NCCF, availability statistics, NEDT by channel, calibration accuracy definition (1-sigma/max), and striping/stability metrics.

SOW Table 3; evaluation “demonstrated capability”

Improves technical rating likelihood; reduces perception of unsubstantiated claims.

REC-04

Add explicit commitments to CAR 1352.239-72(i) System Accreditation Package obligations and personnel screening (CAM 1337.70) where accounts/access are required; include a high-level system boundary diagram and interconnection description.

CAR 1352.239-72 (c)-(j) esp. (e) and (i); SOW §VI

Reduces security/compliance risk and supports SCRA/IT security review.

REC-05

Add explicit acknowledgment of CAR 1352.239-72(g) requirement by citing CAR 1352.209-72 Restrictions Against Disclosures and committing to provide signed acknowledgements as required.

CAR 1352.239-72(g)

Eliminates a small but explicit contractual compliance gap.

REC-06

Expand SCRA section to explicitly commit to providing each enumerated “Supply Chain Risk Assessment Information” element (identity tree, subcontractors, foreign ownership/control, officer DOBs, facility locations, separation of duties, transport, service agreements, disposal) and to marking/transmitting securely per FAR 3.104-4.

SCRA “Supply Chain Risk Assessment Information (Sep 2015)” A–E

Streamlines pre-award SCRA review; reduces likelihood of follow-up delays/questions.

REC-07

Add Business Volume entries inline (not only via SF1449) for UEI, company address, phone, and proposal contact email to match the addendum minimum content expectations.

Section C addendum “detailed information… at a minimum”

Reduces administrative non-responsiveness risk.

REC-08

Add acknowledgements and flowdown/training commitments for NOAAAM 1330-52.222-70 (SASH) and NOAAAM 1330-52.203-71 (post-government employment restrictions).

NOAAAM clauses in solicitation

Reduces post-award compliance friction and demonstrates clause awareness.

REC-09

Clarify Phase 2 duration flexibility (6 vs 12 months) and state whether AstraSound has been previously evaluated under NOAA/NESDIS CDP; explicitly accept coordination of start/end with CO/COR.

SOW §V Performance Schedule; Phase 2 description

Aligns expectations and reduces ambiguity in evaluation of schedule realism.

REC-10

Tighten data rights/marking language to explicitly align with FAR 52.227-14 Alt II (avoid unauthorized restrictive markings; commit to form/fit/function data delivery where withholding applies).

FAR 52.227-14 Alt II; SOW §VII

Reduces legal/compliance risk around documentation/data markings.