Riftur

Additional Use Cases

Public use case

NAVSUP RFQ Proposal Compliance Review for Calibration Services

Solicitation

Radio Calibration Testing

Industry

NAICS 81 – Other Services (except Public Administration)

Executive Summary

This gap analysis maps explicit solicitation requirements, instructions to offerors, PWS technical requirements, inspection/acceptance conditions, delivery/performance constraints, cybersecurity eligibility conditions (CMMC/DFARS), and invoicing/payment requirements from solicitation_text.docx to the corresponding responses in input_proposal.docx. Each requirement was normalized into a discrete, testable statement and assessed for coverage: Covered (explicitly addressed), Partially Covered (addressed but missing key specifics or evidence), or Gap (not addressed / contradictory). Emphasis was placed on mandatory submission elements (signed RFQ/amendments, facility address, repair capability statement, CMMC UID submission) and performance constraints (30 days ADC, calibration to Viavi standards, proof valid ≥3 years, inspection/acceptance at vendor site, POP dates). Risks were rated based on award eligibility impact, evaluation sensitivity (price/past performance), and downstream contract administration impacts (acceptance delays, invoice rejection, cybersecurity noncompliance). Recommendations focus on tightening compliance language, adding missing representations/evidence, and aligning specific numeric constraints (e.g., 200-mile pickup note, POP dates, CMMC level/status) without introducing implementation timelines.

Score Breakdown

Review output

Net Score

71%

Top Score Constraints

These are the three stage-level categories costing the most recoverable score percentage. The percentage estimates how much the score could improve if that constraint were fully resolved.

Compliance

61%

5.8% recoverable

Estimated from 24 status signals across 4 published compliance tables.

Evaluation Readiness

69%

4.7% recoverable

No dedicated published table was available, so the overall findings estimate is used.

Evidence

69%

4.7% recoverable

No dedicated published table was available, so the overall findings estimate is used.

Requirement Coverage

40

reqs

Covered: 58% (23)

Partially Covered: 25% (10)

Missing: 18% (7)

Unclear: 0% (0)

Risk Heatmap

Shows how many Risk Register findings fall into each severity and likelihood combination. Likelihood means the estimated chance that the issue will affect evaluation, submission acceptance, or delivery if it is not fixed.

Likelihood

Severity

Low

Medium

High

High

0

3

0

Medium

0

3

0

Low

0

0

0

What Would Improve My Score

REC-1

+5.5% possible

Details

Owner

Proposal team

Requirement

Addendum to 52.212-1 submission instructions; SF1449 note to complete blocks; SF30 amendment instructions

Solicitation Source

Addendum to 52.212-1 submission instructions; SF1449 note to complete blocks; SF30 amendment instructions

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (Consolidated)

Finding

Reduces administrative rejection risk; improves evaluator confidence

Completion Standard

Update the proposal so this recommendation is directly evidenced: REC-1

REC-2

+4.4% possible

Details

Owner

Proposal team

Requirement

DFARS 252.204-7021 and 252.204-7025

Solicitation Source

DFARS 252.204-7021 and 252.204-7025

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (Consolidated)

Finding

Addresses award eligibility and reduces cyber compliance ambiguity

Completion Standard

Update the proposal so this recommendation is directly evidenced: REC-2

REC-3

+3.3% possible

Details

Owner

Proposal team

Requirement

Delivery/Performance page; PWS special note

Solicitation Source

Delivery/Performance page; PWS special note

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (Consolidated)

Finding

Avoids schedule disputes and acceptance arguments

Completion Standard

Update the proposal so this recommendation is directly evidenced: REC-3

REC-4

+2.2% possible

Details

Owner

Proposal team

Requirement

FAR 52.222-41; WD reference; 52.222-42

Solicitation Source

FAR 52.222-41; WD reference; 52.222-42

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (Consolidated)

Finding

Reduces responsibility/contracting admin follow-ups

Completion Standard

Update the proposal so this recommendation is directly evidenced: REC-4

REC-5

+1.5% possible

Details

Owner

Proposal team

Requirement

PWS proof of calibration ≥ 3 years; inspection/acceptance at vendor location

Solicitation Source

PWS proof of calibration ≥ 3 years; inspection/acceptance at vendor location

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (Consolidated)

Finding

Speeds inspection/acceptance and closeout; reduces rework

Completion Standard

Update the proposal so this recommendation is directly evidenced: REC-5

Requirements

86%

Details

Estimated from 16 status signals across 2 published requirements tables.

Compliance

61%

Details

Estimated from 24 status signals across 4 published compliance tables.

Evaluation Readiness

69%

Details

No dedicated published table was available, so the overall findings estimate is used.

Strategy

69%

Details

No dedicated published table was available, so the overall findings estimate is used.

Evidence

69%

Details

No dedicated published table was available, so the overall findings estimate is used.

Management

69%

Details

No dedicated published table was available, so the overall findings estimate is used.

Past Performance

69%

Details

No dedicated published table was available, so the overall findings estimate is used.

Risk

51%

Details

Estimated from 12 status signals across 1 published risk table.

Production

90%

Details

Estimated from 4 status signals across 1 published production table.

Score Equation

Details

The overall score is a weighted average of stage-level proposal categories. Detailed tables are rolled up into Requirements, Compliance, Evaluation Readiness, Strategy, Evidence, Management, Past Performance, Risk, and Production so the summary reflects the full report without duplicating overlapping findings. Each category receives a 0-100 score, that score is weighted by proposal impact, and the weighted results are added and rounded to the final score. The largest weighted influence currently comes from Requirements, Compliance, Evaluation Readiness. Top Score Constraints are the weighted categories with the largest recoverable point loss.

Scoring Caveats

  • Scores reflect the published solicitation and proposal content available to this review.
  • Categories without a dedicated source table use the average of the available status signals.

Intake

Source basis, solicitation structure, and review setup.

1 tables

Document Meta-Data & Role Inference

4 rows
Attributesolicitation_text.docxinput_proposal.docxAlignment Notes

Solicitation / Instrument

SF 1449 RFQ for commercial services; PWS; FAR/DFARS clauses; NAVSUP local clauses; SF30 amendment summary

Vendor quote/proposal narrative with price and compliance statements

Correct pairing for RFQ→quote alignment

Requirement Type Emphasis

Submission instructions, technical service requirements, cybersecurity eligibility (CMMC UID), inspection/acceptance at vendor site, POP, WAWF

Addresses most core technical and admin themes

Some submission/eligibility specifics not evidenced (e.g., signed RFQ/SF30; CMMC level/status/UID list actually provided)

Evaluation Basis

Award on price unless CO considers past performance tradeoff (FAR 52.212-2)

Acknowledges price-first evaluation and willingness to provide references

Aligned

Set-aside context

WOSB/Small business set-aside indicated on SF1449; FAR 52.219-6

States Women-Owned Small Business

Aligned but no formal reps/certs included in narrative

Requirements

Authoritative requirement inventory and taxonomy.

2 tables

PWS Technical Requirements Coverage Matrix (Industry-standard: Requirements Traceability Matrix)

10 rows
Req IDRequirement (solicitation_text.docx)Draft Response (input_proposal.docx)Coverage StatusGap / Clarification NeededRisk if Unresolved

PWS-1

Provide calibration, testing, and diagnosis ONLY; repairs case-by-case

Explicitly states scope is calibration/testing/diagnosis only; repairs separate case-by-case with CO authorization

Covered

None

Low

PWS-2

Provide comprehensive calibration services for fourteen test sets: six IFR 3920N and eight IFR 3515N

Explicitly addresses 6x 3920N + 8x 3515N

Covered

None

Low

PWS-3

Calibrate IFR 3920N sets to meet Viavi (Aeroflex) standards

States calibrations aligned to Viavi/Aeroflex standards and manufacturer methods

Covered

Consider citing specific Viavi procedures/manual references if available

Low/Medium (acceptance scrutiny)

PWS-4

Provide proof of calibration valid for no less than three years (IFR 3920N)

States certificates will clearly state three-year validity; notes shorter OEM intervals as advisory

Covered

Ensure certificate language matches solicitation expectation ("valid for no less than 3 years")

Low

PWS-5

IFR 3920N components calibrated: (1) 3920N unit; (1) 0–69 dB 2W 18 GHz attenuator; (2) 20 dB 25W 4 GHz attenuators; (1) Type N broadband splitter

Lists and addresses each component; indicates integrated system verification where applicable

Covered

Confirm ability to calibrate/verify splitter performance parameters per OEM specs (if required) and document explicitly

Low/Medium

PWS-6

Calibrate IFR 3515N sets to meet Viavi (Aeroflex) standards

States calibrate and functionally verify to applicable standards

Covered

Consider explicitly stating "to meet Viavi (Aeroflex) standards" for 3515N as well (it is implied)

Low

PWS-7

Provide proof of calibration valid for no less than three years (IFR 3515N)

States proof valid for no less than 3 years for each unit/component

Covered

None

Low

PWS-8

IFR 3515N components calibrated: (1) 3515N unit; (1) 20 dB 50W attenuator; (1) 20 dB 150W attenuator

Lists and addresses each component; discusses attenuation accuracy, return loss behavior, power handling verification approach

Covered

None

Low

PWS-9

Perform all necessary calibration, testing, and diagnosis

Describes intake screening, calibration, functional verification, and diagnostic narratives (as-found/as-left)

Covered

None

Low

PWS-10

Special note: radios must be calibrated within 30 days ADC

Explicitly commits to workflow meeting 30 days after ADC and describes process

Covered

Define how ADC is determined/recorded (e.g., intake timestamp/receipt log) to avoid disputes

Medium (schedule acceptance disputes)

Inspection, Acceptance, Logistics, and Place of Performance Alignment

6 rows
Topicsolicitation_text.docx Requirementinput_proposal.docx ResponseCoverage StatusGap / Potential ConflictRisk

Inspection & Acceptance Location

Inspection and Acceptance will occur by Government at awarded vendor location for CLIN 0001 and 0002

Explicitly accepts and describes inspection area, Government access, documentation review

Covered

None

Low

Drop-off / pickup coordination

NAVELSG will coordinate drop-off and pickup with vendor

Explicitly accepts; offers flexible receiving hours and coordinated handoff

Covered

None

Low

Government travel distance for drop/pickup

Amended note indicates up to 200 miles from Cheatham Annex for pickup; earlier text also references 60 miles (in unamended section)

Proposal acknowledges up to 200 miles and will accommodate

Covered

None; proposal aligns to amended max distance

Low

Chain of custody / property control (implied operational need)

Not explicitly required in PWS, but Government-furnished property handled at vendor site

Proposal commits to chain-of-custody documentation, secure access-controlled areas

Covered (value-add)

Ensure process includes signed intake/outtake forms and accessory count reconciliation

Medium (loss/damage disputes)

Period of Performance

29 Jun 2026 to 29 Jan 2027 (for both CLINs)

States will perform within established period of performance but does not cite dates

Partially Covered

Add explicit POP dates acknowledgement to avoid ambiguity

Medium

FOB / delivery terms

SF1449 indicates FOB Destination unless otherwise; but services at vendor location and NAVELSG coordinates transport

Proposal assumes NAVELSG handles drop-off/pickup; no FOB discussion

Partially Covered

Add statement confirming no shipping is included/required and that Government will transport to/from vendor (as per solicitation notes)

Low/Medium

Compliance

Required documents, instructions, forms, certifications, and package checks.

4 tables

Administrative / Submission Instructions Compliance Matrix

7 rows
Req IDInstruction / Requirement (solicitation_text.docx)Draft Response (input_proposal.docx)Coverage StatusMissing Evidence / Actionable GapRisk if Unresolved

SUB-1

Submit quote via email to specified Government addresses (McKay and Olszak)

Does not explicitly state submission method/emails (states "will submit ... with quotation package")

Partially Covered

Add explicit statement that quote will be emailed to both addresses exactly as listed

Medium (administrative nonconformance)

SUB-2

Quote shall include signed copies of RFQ and/or latest amendment(s) (signed SF1449 and SF30 acknowledgements as applicable)

States it will submit signed SF1449 and any applicable SF30 acknowledgements

Partially Covered

Include explicit exhibit/attachment list confirming signed RFQ and each amendment number acknowledged; ensure actual signatures included

High (quote rejection risk)

SUB-3

Quoter shall provide facility address where calibration will be completed

Provides full facility address and describes facility controls

Covered

None

Low

SUB-4

Quoter shall provide a statement/proof of capability/ability to perform repairs if identified and agreed upon

Provides repairs capability statement and CO-authorization constraint

Covered

Consider adding examples of repair types, tooling, OEM relationships (some already included) and whether repairs are in-house vs subcontracted

Low/Medium

SUB-5

Acknowledge amendment: response due time updated to 02:00 PM local time

Explicitly acknowledges updated due time of 02:00 PM local time

Covered

Include amendment identifier/number if present on SF30 in package

Medium

SUB-6

Offeror to complete SF1449 blocks 12, 17, 23, 24, and 30

Narrative mentions submitting signed SF1449; includes pricing amounts in text

Partially Covered

Ensure completed SF1449 blocks are actually filled (discount terms, offeror data, unit price/amount, signature/date)

High (administrative rejection)

SUB-7

Questions deadline noted (08 June 2026 12:00 PM EDT); no questions after

Not addressed

Gap

Optional to acknowledge, but adding a statement of awareness can reduce admin friction (do not add new questions post-deadline)

Low

Cybersecurity & CMMC / DFARS Eligibility Requirement Mapping

5 rows
Req IDRequirement (solicitation_text.docx)Draft Response (input_proposal.docx)Coverage StatusSpecific Gap / Missing ProofEligibility / Performance Risk

CYB-1

DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting (applies as clause)

Proposal states it will comply with DFARS 252.204-7012 and safeguard FCI/CUI

Partially Covered

No description of incident reporting process, 72-hour reporting, or system boundary; add brief compliance statement referencing reporting obligation and points of contact

Medium

CYB-2

DFARS 252.204-7021: maintain current CMMC status at the required level for systems processing/storing/transmitting FCI/CUI; flowdown; annual affirmation; conditional POA&M closeout

Proposal acknowledges CMMC-related provisions, annual affirmation, flowdowns

Partially Covered

Does not state what CMMC level is currently held or how it meets the solicitation’s required level (blank in solicitation text); add statement: "We maintain current CMMC status at Level __ (or higher) for each in-scope system" once level is known

High (award eligibility risk)

CYB-3

DFARS 252.204-7025: Offeror must provide CMMC UID(s) in the proposal for each system that will process/store/transmit FCI/CUI; not eligible without current status + affirmation in SPRS

Proposal states it will provide required CMMC UID(s) in final submission package as discrete section

Partially Covered

UIDs are not actually provided in the draft text; include the actual UID list and map each UID to system name/purpose (even if only one system)

High (award eligibility risk)

CYB-4

DFARS 252.240-7997 NIST SP 800-171 DoD Assessment Requirements (listed)

Not directly addressed

Gap

Add statement that NIST SP 800-171 assessment score is current in SPRS (if applicable) and aligns with flowed requirements; reconcile with CMMC posture

High (eligibility/administrative risk)

CYB-5

Covered defense telecom prohibition (252.204-7018 clause and 252.204-7017 representation in solicitation provisions)

Proposal states it will not provide prohibited covered telecommunications equipment/services

Partially Covered

Representation may need to be made via SAM annual reps/certs or explicit completion; add explicit statement: "Our SAM reps for 252.204-7016/7017 are current" or attach representation

Medium/High

Pricing / CLIN Structure & Completeness Check

6 rows
Itemsolicitation_text.docxinput_proposal.docxAlignment StatusIssue / Missing DetailRisk

Pricing arrangement

Firm Fixed Price for CLIN 0001 and 0002

States Firm Fixed Price and provides unit and extended pricing

Aligned

None

Low

CLIN 0001 quantity/unit

6 Each

$4,850 each; extended $29,100

Aligned

None

Low

CLIN 0002 quantity/unit

8 Each

$3,150 each; extended $25,200

Aligned

None

Low

Total

Not pre-filled on RFQ continuation; offeror provides

$54,300 total

Aligned

None

Low

Assumptions affecting price

Government coordinates drop-off/pickup; inspection at vendor location

Proposal includes assumption NAVELSG coordinates drop/pickup

Aligned

Ensure assumptions do not conflict with any hidden shipping/packaging requirements (none stated in provided text)

Low/Medium

Discount terms / prompt payment discount (SF1449 Block 12)

Offeror to complete Block 12

Not stated

Gap

If no discount is offered, explicitly state "No discount" in SF1449 Block 12 (in the actual form)

Medium (admin completeness)

Clause/Provision Awareness & Flowdown Gaps (Non-technical but compliance-relevant)

6 rows
Clause/Provision AreaAppears in solicitation_text.docxAddressed in input_proposal.docx?Coverage StatusPotential Gap / Recommended AdditionRisk

Service Contract Labor Standards (FAR 52.222-41) + WD noted

Yes (clause list + equivalent rates statement + WD reference)

Not explicitly addressed

Gap

Add statement acknowledging compliance with SCLS and applicable WD (even if already legally required) to reduce award/admin questions

Medium

SAM maintenance/registration (FAR 52.204-7 / 52.204-13)

Yes

Mentions SAM current for EFT; not explicit for registration/maintenance clauses

Partially Covered

Add explicit statement: SAM active and will be maintained through performance

Low/Medium

Equal opportunity / disability / labor-related clauses (52.222-36, 52.222-55, 52.222-62, etc.)

Yes

Not addressed

Gap

Optional add: compliance statement confirming adherence to incorporated FAR labor clauses

Low/Medium

Export-controlled items (DFARS 252.225-7048)

Yes

Not addressed

Gap

Add short statement that no export-controlled items/data will be transferred; if encountered, will comply with clause requirements

Low/Medium

AbilityOne release of offeror info for closeout support

Yes (NAVY local text)

Not addressed

Gap

Add acknowledgement/consent statement (or indicate you accept as incorporated) and whether you will seek separate NDA

Medium (post-award friction)

Authorized changes only by CO (local clause 243-9400)

Yes

Explicitly acknowledges only CO can direct changes

Covered

None

Low

Risk

Risk register findings, assumptions, exceptions, and deviations.

1 tables

Key Gaps & Risks Register (Industry-standard: Procurement Risk Register)

6 rows
Risk IDRisk StatementRoot Cause / TriggerLikelihoodImpactOverall RiskMitigation Recommendation (No timelines)

R-01

Award ineligibility due to missing CMMC UID(s) / unclear CMMC status alignment

Draft says UIDs will be provided but does not include them; solicitation requires UIDs in proposal and current status + affirmation in SPRS

Medium

High

High

Add a discrete CMMC compliance annex listing each in-scope information system, its CMMC UID, current status (Final/Conditional), level, and statement that annual affirmation is current in SPRS

R-02

Quote rejection for incomplete SF1449/SF30 execution package

Narrative promises signed forms, but no attachment inventory or completed blocks shown

Medium

High

High

Include a submission checklist and attachment list; ensure SF1449 blocks 12/17/23/24/30 completed and each amendment acknowledged by number/date

R-03

Period of performance misunderstanding

Proposal references POP generally without acknowledging exact POP dates

Low/Medium

Medium

Medium

Add explicit statement accepting POP 29 Jun 2026–29 Jan 2027 and clarifying that 30-days-ADC requirement will be met within that window

R-04

Cyber incident reporting / CDI safeguarding challenge

DFARS 252.204-7012 compliance asserted but operational reporting/handling specifics not stated

Low/Medium

High

Medium/High

Add concise DFARS 7012 operational compliance statement: incident reporting process, responsible official, and confirmation that covered contractor information systems meet safeguarding requirements

R-05

Acceptance delays due to documentation format mismatch

Certificates promised but Government may expect specific data fields/layouts or batch cross-references

Medium

Medium

Medium

Provide a sample certificate template outline and an acceptance package index structure mapping each unit/accessory to certificate IDs and as-found/as-left data

R-06

Labor compliance questions (SCLS/Wage Determination) arise during responsibility review

No explicit acknowledgement of FAR 52.222-41 / WD compliance

Low/Medium

Medium

Medium

Add statement acknowledging SCLS applicability and intent to comply with the incorporated WD and related labor clauses

Production

Final package readiness, attachments, and production cleanup.

1 tables

Invoicing, Payment, and Closeout Requirements Mapping

4 rows
Req IDRequirement (solicitation_text.docx)Draft Response (input_proposal.docx)Coverage StatusGap / Needed ClarificationRisk

PAY-1

DFARS 252.232-7003 Electronic Submission of Payment Requests and Receiving Reports (WAWF)

Commits to electronic invoicing in compliance with DFARS 252.232-7003 and 252.232-7006

Covered

None

Low

PAY-2

DFARS 252.232-7006 WAWF instructions: document type for services no shipment = Invoice 2-in-1 or as specified at award; routing table completed at award

Acknowledges document type will be confirmed with CO; mentions 2-in-1 concept

Covered

None

Low

PAY-3

FAR 52.232-33 EFT via SAM; keep SAM current

Commits to maintaining SAM for EFT

Covered

None

Low

PAY-4

DFARS 252.204-7022 / NAVSUP closeout emphasis; local clause: waive residual ≤ $1,000 at closeout

Proposal acknowledges waiver and will support accurate invoicing

Covered

None

Low

Recovery

Prioritized fixes, clarification candidates, and recovery actions.

1 tables

Recommendations to Enhance Alignment (Consolidated)

7 rows
Recommendation IDRecommended Enhancement to input_proposal.docxMapped Solicitation Driver (solicitation_text.docx)Expected Benefit

REC-1

Add a 'Submission Compliance Checklist' section listing: emailed to both addresses; signed SF1449; each SF30 amendment acknowledged; completed SF1449 blocks 12/17/23/24/30; facility address provided; repair capability statement included

Addendum to 52.212-1 submission instructions; SF1449 note to complete blocks; SF30 amendment instructions

Reduces administrative rejection risk; improves evaluator confidence

REC-2

Add a 'CMMC / SPRS Compliance Annex' including: required CMMC level statement (once known), each contractor information system in scope, CMMC UID(s), status currency, and affirmation currency; include flowdown approach for any subcontractors

DFARS 252.204-7021 and 252.204-7025

Addresses award eligibility and reduces cyber compliance ambiguity

REC-3

Explicitly acknowledge POP dates (29 Jun 2026–29 Jan 2027) and reconcile with 30-days-ADC requirement definition (how ADC/receipt is recorded)

Delivery/Performance page; PWS special note

Avoids schedule disputes and acceptance arguments

REC-4

Include a short 'SCLS/Wage Determination Compliance' acknowledgement statement

FAR 52.222-41; WD reference; 52.222-42

Reduces responsibility/contracting admin follow-ups

REC-5

Provide a sample outline (not necessarily full template) of calibration certificate contents and acceptance package indexing; state electronic file format (PDF) and naming convention

PWS proof of calibration ≥ 3 years; inspection/acceptance at vendor location

Speeds inspection/acceptance and closeout; reduces rework

REC-6

Add explicit statement that SAM is active/current and will be maintained throughout performance; mention WAWF registration readiness

FAR 52.204-7 / 52.204-13; DFARS 252.232-7006

Improves administrative readiness and payment assurance

REC-7

Add acknowledgement/consent regarding AbilityOne support contractor access to proposal info (or state you accept clause as incorporated and whether you will seek NDA)

NAVSUP AbilityOne release of offeror information clause

Reduces post-award closeout friction and data-handling misunderstandings

Riftur’s Impact

Riftur’s output makes clear that the submission’s competitive posture is not limited by technical coverage, but by a small set of compliance artifacts that determine whether the quote can be accepted and verified. It specifically flagged missing pricing/offer-form elements such as the discount terms field on the SF 1449, plus incomplete evidence that required SF 1449 blocks and signed RFQ/SF30 amendment acknowledgments are actually executed and traceable by amendment identifier. It also isolated eligibility threats from absent CMMC UID(s), an unstated current CMMC level/status alignment, and missing acknowledgement of the NIST SP 800-171 assessment requirement embedded in the clause set. These are higher-leverage than general narrative improvements because they directly affect evaluability, eligibility screening, and the Government’s ability to document a compliant award file. Riftur further highlighted acceptance and payment friction points where the proposal is only partially specific, including undefined ADC tracking for the 30-day requirement and limited structure around certificate and acceptance-package indexing that can drive inspection delays or invoice rejection. The result is a clear concentration of risk in cyber attestations and executed submission documents, while the core PWS scope, quantities, inspection location, and WAWF invoicing readiness are already largely aligned.

© 2025 Riftur — All Rights Reserved