Additional Use Cases
Executive Summary
This gap analysis maps requirements from solicitation_text.docx (Reference Criteria) to evidence contained in input_proposal.docx (Draft Document). The methodology follows standard RFP-to-proposal compliance mapping: (1) extract explicit “shall/must” requirements, required proposal submissions, and evaluation subfactor criteria from Sections L/M and cited Supplements; (2) locate corresponding commitments, procedures, capacities, or data in the proposal; (3) assign a coverage status (Covered / Partially Covered / Gap) and note risks where noncompliance could drive an Unacceptable rating under LPTA. Because the solicitation incorporates the PWS and Attachment III QAPs by reference, the proposal must either provide explicit procedural detail or clearly commit to comply while also providing the specific “Data Requirements (Storage)” artifacts; missing artifacts can still render the proposal unacceptable per the solicitation. The Draft Document provides strong narrative alignment to the seven Technical/Management subfactors and many of the Supplement requirements (water bottoms, sampling/testing responsibilities, shipping controls, custody transfer points, records retention). The largest exposure areas are proposal-format/administrative fill-ins (Section F/G/K fill-ins, SF-30s, express warranty terms, authorized negotiators, address fill-ins), explicit “Data Requirements (Storage)” itemization (tank dimensions/type/bottoms/safe fill computation, pipeline/manifold fill, ballast water receiving capacity, dredging charts attachment, segregated vs dedicated system declaration), and cybersecurity/supply-chain clauses (FAR 52.204-21, DFARS 252.204-7012/7020/7021) where operational commitments and evidence (SSP, SPRS score, CMMC level) are not addressed in the Draft Document. Recommendations focus on converting narrative into auditable, solicitation-cross-referenced compliance matrices and adding the missing mandatory submissions to avoid an Unacceptable determination.
Score Breakdown
Net Score
52%
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.
Requirements
50%
10% recoverable
No dedicated published table was available, so the overall findings estimate is used.
Evaluation Readiness
50%
7.5% recoverable
No dedicated published table was available, so the overall findings estimate is used.
Evidence
50%
7.5% recoverable
No dedicated published table was available, so the overall findings estimate is used.
Requirement Coverage
20
reqs
Covered: 30% (6)
Partially Covered: 40% (8)
Missing: 30% (6)
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
2
Medium
1
1
0
Low
0
0
0
What Would Improve My Score
Add a Requirements Compliance Matrix (RCM) crosswalking each Subfactor and each Supplement paragraph to proposal sections and appendices
+5.5% possible
Details
Owner
Proposal team
Requirement
See mapped source criteria
Solicitation Source
See the published source table
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable, Solicitation-Cross-Referenced)
Finding
Reduces evaluation ambiguity; improves Acceptable likelihood under LPTA.
Completion Standard
Update the proposal so this recommendation is directly evidenced: Add a Requirements Compliance Matrix (RCM) crosswalking each Subfactor and each Supplement paragraph to proposal sections and appendices
Provide the full “Data Requirements (Storage)” attachment set as appendices
+4.4% possible
Details
Owner
Proposal team
Requirement
See mapped source criteria
Solicitation Source
See the published source table
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable, Solicitation-Cross-Referenced)
Finding
Directly addresses solicitation warning that missing technical data can make proposal technically unacceptable.
Completion Standard
Update the proposal so this recommendation is directly evidenced: Provide the full “Data Requirements (Storage)” attachment set as appendices
Explicitly select and describe the Testing Option (self-perform / Gov uses contractor facility / commercial lab) and include a 24-hour transport workflow if applicable
+3.3% possible
Details
Owner
Proposal team
Requirement
See mapped source criteria
Solicitation Source
See the published source table
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable, Solicitation-Cross-Referenced)
Finding
Eliminates non-responsiveness risk; strengthens Subfactor 7 acceptability.
Completion Standard
Update the proposal so this recommendation is directly evidenced: Explicitly select and describe the Testing Option (self-perform / Gov uses contractor facility / commercial lab) and include a 24-hour transport workflow if applicable
Add explicit custody transfer point statements for each receipt and shipment mode, matching solicitation wording
+2.2% possible
Details
Owner
Proposal team
Requirement
See mapped source criteria
Solicitation Source
See the published source table
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable, Solicitation-Cross-Referenced)
Finding
Shows precise contract understanding; reduces disputes and audit risk.
Completion Standard
Update the proposal so this recommendation is directly evidenced: Add explicit custody transfer point statements for each receipt and shipment mode, matching solicitation wording
Expand shipping conveyance deficiency reporting procedures (tanker/barge, tank car, truck) and add placarding compliance statement
+1.5% possible
Details
Owner
Proposal team
Requirement
See mapped source criteria
Solicitation Source
See the published source table
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable, Solicitation-Cross-Referenced)
Finding
Improves compliance and safety; reduces shipment delays and demurrage exposure.
Completion Standard
Update the proposal so this recommendation is directly evidenced: Expand shipping conveyance deficiency reporting procedures (tanker/barge, tank car, truck) and add placarding compliance statement
Requirements
50%
Details
No dedicated published table was available, so the overall findings estimate is used.
Compliance
58%
Details
Estimated from 20 status signals across 2 published compliance tables.
Evaluation Readiness
50%
Details
No dedicated published table was available, so the overall findings estimate is used.
Strategy
50%
Details
No dedicated published table was available, so the overall findings estimate is used.
Evidence
50%
Details
No dedicated published table was available, so the overall findings estimate is used.
Management
73%
Details
Estimated from 7 status signals across 1 published management table.
Past Performance
50%
Details
No dedicated published table was available, so the overall findings estimate is used.
Risk
37%
Details
Estimated from 23 status signals across 2 published risk tables.
Production
50%
Details
No dedicated published table was available, so the overall findings estimate is used.
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
Compliance
Required documents, instructions, forms, certifications, and package checks.
Supplement Requirements (Section C/F) — Operational Compliance Mapping
Proposal Submission & “Data Requirements (Storage)” — Mandatory Artifacts Checklist
Management
Management approach, staffing, roles, and execution ownership.
Evaluation Factor 1 (Technical/Management) — Subfactor Compliance Mapping (LPTA Acceptable/Unacceptable Drivers)
Risk
Risk register findings, assumptions, exceptions, and deviations.
Cybersecurity / Information Systems / Supply Chain Clauses — Compliance Evidence Gaps (Material Contractual Risk)
Risk Register (LPTA) — Unacceptability Drivers and Performance/Compliance Risks
Recovery
Prioritized fixes, clarification candidates, and recovery actions.
Recommendations to Enhance Alignment (Actionable, Solicitation-Cross-Referenced)
Riftur’s Impact
Riftur surfaced that this submission is strongest where it provides concrete operational procedures, but risk is concentrated in objective, mandatory items that determine evaluability under LPTA. It revealed missing or non-itemized storage data elements such as tank-by-tank dimensions/type/bottoms, tank bottoms volumes, pipeline/manifold line fill, and safe fill values with computation support, which are the core evidence behind the stated capacity commitment. It also flagged evaluability blockers where the proposal does not make required offer-form commitments, including the failure to explicitly select the required testing option and support it with a defined workflow and compliance basis. Riftur further highlighted absent administrative submissions that can cause non-responsiveness, including unfilled Section F/G/K entries, missing amendment acknowledgments, incomplete authorized negotiator information, absent express warranty terms, and incomplete pricing attachments. It identified material clause-evidence gaps for cybersecurity and supply chain, including unaddressed safeguarding and DFARS requirements (SSP/incident reporting, SPRS assessment posture, and any CMMC-related proof), plus missing acknowledgments for prohibitions like covered telecom and covered applications. These items are higher leverage than narrative polish because their presence is often a gate to acceptance, while their absence can prevent scoring, trigger elimination, or reduce auditability of the final contract file. At the same time, Riftur clarified where alignment is already strong—receiving/shipping controls, additive injection approach, and core inventory transaction practices—so the remaining work is concentrated on the specific artifacts and commitments that determine acceptability and awardability.
© 2025 Riftur — All Rights Reserved