Riftur

DLA Energy Proposal Gap Analysis for Bulk Fuel Storage Services

Solicitation NameContractor-Owned, Contractor-Operated (COCO) Fuel Storage Services in the Port of Anchorage, Alaska
Solicitation LinkSAM.gov
IndustryNAICS 48-49 - Transportation and Warehousing

This solicitation centers on operating a contractor-owned terminal to receive, store, quality-surveil, and issue bulk military fuels under tight throughput, safety, and accountability rules. Because it is LPTA, the proposal’s primary job is to be clearly acceptable and fully responsive, with no ambiguity about mandatory artifacts, capacities, and clause commitments. The draft shows solid operational understanding across receiving, shipping, additive injection, and inventory controls, and it often aligns to the intent of the supplements. The key weakness is not technical intent but evidentiary completeness and selection of required “either/or” compliance options. Several items that evaluators treat as objective acceptability gates are referenced as “will provide” rather than actually provided or definitively stated. The most consequential LPTA exposure is the missing “Data Requirements (Storage)” package tied to storage capacity acceptability. The narrative commitment to 1,013,000 barrels and interconnected tanks helps, but it does not substitute for tank-by-tank dimensions, type/bottoms, unrecoverable bottoms, and maximum safe fill values with a computation basis. Those data drive whether capacity is real, available at award, and safely usable, and evaluators can score the subfactor unacceptable if they cannot verify it from the submission. The same pattern appears in berthing support where dredging charts and facility schematics are promised but not present; without them, vessel constraints and draft capability are harder to validate and can become a pass/fail blocker. These gaps increase audit risk because the file will not show objective evidence supporting capacity and berth claims. A second high-leverage issue is an evaluability blocker in the sampling/testing supplement where one of three testing options must be selected and supported. The draft discusses testing generally but does not clearly choose an option or describe the required 24-hour transport workflow and responsibilities if a commercial lab approach is used. In LPTA, ambiguity reads as non-responsiveness, and evaluators have little room to infer which commitment the offeror is making. Related operational requirements show smaller but still meaningful precision gaps, such as incomplete mirroring of custody transfer points by mode, detailed deficiency reporting routing, and specific recordkeeping triggers (for example, certain water-bottom and after-rain steps). These are not narrative-strength issues; they affect whether procedures can be inspected, repeated, and defended during surveillance. The third concentration of risk is administrative and clause-driven compliance that can affect eligibility, acceptability, and award timeliness even if operations are strong. Several mandatory proposal elements are missing or not evidenced in the text, including Section F/G/K fill-ins, authorized negotiators, amendment acknowledgments, express warranty terms, and completed pricing forms. In addition, the cybersecurity and supply-chain clauses are largely unaddressed, including basic safeguarding, NIST 800-171/incident reporting, assessment posture (SPRS), and any CMMC-related commitments that may apply. For a DoD fuel storage effort that relies on information systems for inventory/accounting and communications, these omissions can create pre-award clarifications, delays, or post-award noncompliance findings, and they can also undermine evaluator confidence in readiness. Overall, the draft is close on operational approach, but the highest award risk sits in objective artifacts, unselected required options, and missing clause acknowledgments that can trigger an Unacceptable outcome regardless of narrative quality.

Output Analysis

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.

Evaluation Factor 1 (Technical/Management) — Subfactor Compliance Mapping (LPTA Acceptable/Unacceptable Drivers)

Subfactor / Requirement (Reference Criteria)Key Reference Criteria ExcerptDraft Document Evidence (input_proposal.docx)Coverage StatusGap / Risk Notes

Subfactor 1 — Area of Consideration (facility within Port of Anchorage)

“must provide evidence that the offered facility is within the Area of Consideration Port of Anchorage, Alaska.”

States facility is located within Port of Anchorage; commits to provide “required map, schematic facility layout drawing, and related location documentation”.

Partially Covered

Narrative claim is present, but the actual evidentiary attachments (map, schematic) are not included in the provided text; if omitted in submission package, could drive Unacceptable.

Subfactor 2 — Grades of Service (ops detail; inventory accounting per policies)

“must provide understanding… receipt, storage, issue, and transfer… ensure… inventory accounting in accordance with applicable policies and directives.”

Detailed 24/7 readiness; one-business-day transaction input; procedures (shift turnover, line-up verification, sampling/testing ASTM D4057); cites DoDM 4140.25 and DLA P-series.

Covered

Ensure cross-reference to specific solicitation supplements (General Receiving/Storing; General Shipping) and P-series versions.

Subfactor 3 — Storage capacity and tank requirements (1,013,000 bbl; min 2 interconnected tanks; all available at award; provide tank data)

“demonstrate… 1,013,000 barrels… minimum of two tanks interconnected… all storage available upon award at a single facility… provide all data… tank dimensions, tank type, tanks bottoms, calibrated capacity incl safe fill… provide tank cleaning and inspection data.”

Commits to required capacity; “minimum of two interconnected tanks”; says calibrated capacity data, safe fill determinations, certified strapping charts; API 653 history and next dates; cleaning/maintenance/repair history to be provided.

Partially Covered

Does not actually list tank-by-tank dimensions/type/bottoms/safe fill level and computation in the provided text; solicitation warns missing technical data may be unacceptable. Add a tank data table.

Subfactor 4 — Additive injection requirements (conductivity additive, FSII, CI/LI)

“approach to meet all additive injection requirements including purchase, receipt, storage, injection, maintaining additives on specification.”

Conductivity additive: Government-furnished, method to determine quantity; FSII: MIL-DTL-85470B N1 0.01–0.15%, auto adjust, calibrated meter, moisture control, no CO2; CI/LI: MIL-PRF-25017H A1, QPD/QPL, invoice certification and CO approval.

Covered

Add explicit statement that all additive procedures will be incorporated into QCP (already stated) and that equipment meets minimum conductivity system specs (0–114 gph @100 psi; 100-gal blending tanks).

Subfactor 5 — Product receiving requirements (tanker/barge min 10,000 BPH; vessel limits; dredging charts; 24/7 rail/truck)

“capable… 24/7… minimum 10,000 BPH… handle vessels not to exceed 46,000 DWT, 655 ft LOA, min draft 35 ft… include… dredging charts… rail tank car and tank truck… 24/7.”

States 24/7 receiving; 10,000 BPH; vessel limits; will provide schematic/narrative and “current dredging charts”; rail and truck receiving procedures included.

Partially Covered

Text says will provide dredging charts but does not include them; if not attached, risk Unacceptable. Also add explicit statement re Government-furnished rail cars/trucks.

Subfactor 6 — Product shipping requirements (tanker/barge min 5,000 BPH; pipeline to Elmendorf; Scully; temp-comp meters; 24/7 rail/truck)

“capable… 24/7… min 5,000 BPH… pipeline connection… equipped with Scully… temperature compensating meters.”

States all modes 24/7; 5,000 BPH; pipeline connection and custody flange; Scully; temp-comp meters; strainers; seals; DD250 forms; release required.

Covered

Consider adding explicit confirmation that Government-furnished conveyances are used and that placarding per 49 CFR 172.506/.508 will be furnished (if applicable).

Subfactor 7 — Product quality surveillance (MIL-STD-3004-1; sampling/testing requirements)

“maintain… in accordance with MIL-STD-3004-1… meet all laboratory testing and sampling requirements.”

Commits to MIL-STD-3004-1; ASTM D4057 sampling by contractor; testing approach; nonconformance control E35; inspection rights FAR 52.246-4; QCP alignment.

Partially Covered

Does not select/describe which testing option (self-perform vs provide facilities for Gov vs transport to commercial lab within 24h) as required by the supplement checkbox structure. Explicitly state chosen option and capability.

Supplement Requirements (Section C/F) — Operational Compliance Mapping

Requirement AreaReference Criteria Requirement (solicitation_text.docx)Draft Document Evidence (input_proposal.docx)Coverage StatusNotes / Needed Clarification

Security & Fire Protection

Fence with padlockable gates; visitor/entrance control and visitor register; internal self-powered comms/alarm; water supply & firefighting equipment to NFPA/API; emergency assistance list (ambulance, fire, police, FBI, Secret Service, US Marshals, FEMA).

States fencing, gates padlocked, visitor register; self-powered comms; NFPA/API conformance; will seek local emergency resources; references Federal entities generically.

Partially Covered

List of specific Federal entities (FBI, Secret Service, USMS, FEMA) not explicitly named in proposal text; add explicit commitment mirroring supplement (e) to reduce ambiguity.

Removal of Water Bottoms

Positive water sumps; drain minimum weekly and when gauging indicates water; drain prior to any transfer; drain after 4–24h settling following each receipt; floating roofs: gauge after rain; gauge levels before/after draining; record water gauge each product gauge; fuel/water separation system with capability to return separated product to same tank.

Commits to positive water sumps; weekly drainage minimum + when water present; pre-transfer and post-receipt drainage after settling time; fuel/water separation and return to same tank; implies before/after gauging.

Partially Covered

Does not mention floating roof after-rain requirement; does not explicitly state recording “water gauge each time it is gauged for product” (though implied). Add explicit procedural statements and record forms/logs.

Sampling (Storage)

Contractor provides samples using qualified personnel/facilities/equipment on-site; costs included in monthly service charge; QR not responsible; ASTM D4057/MPMS 8.1.

States contractor responsible; qualified personnel on-site; ASTM D4057; QR not responsible; included as part of service charge (in price narrative).

Covered

Add explicit statement that all associated costs are included in monthly use charge (Volume III) and identify any commercial source arrangements if used.

Testing (Storage) — option selection & 24h transport

Higher order analyses and individual tests required; contractor must choose one of 3 options; if commercial lab option: transport within 24h and reimburse test costs; facilities/equipment must meet OSHA/NFPA/local regs.

States will meet testing requirements and coordinate if Government elects Gov lab; mentions transport responsibilities; does not clearly choose one of the 3 options.

Gap

Must explicitly select an option and describe resources (in-house lab capability OR facilities for Gov personnel OR commercial lab transport workflow) to avoid non-responsiveness.

Facilities/equipment standards for testing

All facilities/equipment provided must conform to OSHA and NFPA or local regs (more stringent).

Mentions OSHA/NFPA conformance in testing context only indirectly; fire protection mentions NFPA/API.

Partially Covered

Add explicit statement that any contractor/commercial-lab testing facilities/equipment comply with OSHA + NFPA/local regs, whichever more stringent.

Responsibility for Government-owned petroleum products — access/witnessing

Gov access to premises at all times; supplier may witness quantity/quality during receipt when FOB destination.

Commits to support Government access and witnessing opportunities for suppliers when applicable.

Covered

Consider adding explicit “Government shall at all times have access” statement to mirror clause language.

Protect & preserve GOPO

Protect/preserve consistent with sound industrial practice.

States protect Government-owned fuel quality; sound industrial practice implied.

Partially Covered

Add explicit commitment to protect/preserve GOPO property consistent with sound industrial practice.

Liability for GOPO loss/damage (negligence/bad faith/willful misconduct; insurance)

Contractor not liable except for negligence/bad faith/willful misconduct; or if risk covered by insurance/reimbursed; reimburse Gov if compensated; assist recovery against third parties.

Not addressed in proposal narrative.

Gap

Add acknowledgment/understanding statement (no exceptions) is helpful, but include explicit acceptance/understanding in contract admin section or compliance matrix to avoid ambiguity.

General Receiving & Storing — demurrage accountability (receipts)

Accountable for demurrage from delay(s) in receipt by tank cars/trucks except beyond control; detailed laytime rules; hoses/loading arms furnished/connected/disconnected by contractor.

Proposal discusses laytime rules and demurrage; commits contractor will furnish/connect/disconnect hoses/loading arms.

Covered

Ensure procedures cover tank car/truck demurrage accountability explicitly.

General Receiving & Storing — custody transfer points

Custody/risk passes at specified points by mode (pipeline flange; truck hose into receiving facilities; tank car at rest; vessel permanent hose connection).

Proposal states custody transfer and risk managed at contractual points; explicitly states pipeline flange in shipping section; implies receipt points.

Partially Covered

Add explicit list of custody transfer points for each receipt mode matching the supplement wording.

Tank stripping & unrecoverable bottoms handling (receiving/storing)

Strip tank to preclude loss; provide QAR unrecoverable amount, reason, and analysis; report unrecoverable bottoms/line fill to PA; contaminated product to QAR; tanks out of service removed from revenue; cleaning governed by E18.

Proposal: notify Gov; estimate unrecoverable tank bottoms for review/approval; manage stripping to preclude loss; does not mention providing analysis of unrecovered fuel quality or “removed from revenue” explicitly.

Partially Covered

Add explicit steps: provide analysis of unrecovered fuel quality to QAR; report unrecoverable quantities to PA for disposition; state tanks out of service removed from revenue until returned.

General Shipping — release requirement & documents

Ship only pursuant to “release” from Product Property Administrator; DD250, DD250-1; contractor certification when QR not present under approved QC program.

Proposal states release requirement; DD250/250-1 usage; certification when QR not present under approved program.

Covered

Include the exact certification text (quoted in solicitation) in an appendix and reference authorization letter mechanics.

General Shipping — conveyance inspections & no delegation to drivers

Contractor inspects all conveyances; tank truck inspection by qualified contractor personnel; may permit driver loading but under surveillance; reporting of unsatisfactory equipment to specified parties.

Proposal states inspect conveyances; tank truck inspection not delegated to drivers; surveillance/direction by contractor personnel.

Partially Covered

Does not include the detailed reporting routing (e.g., tank cars to MTMC address; trucks to Traffic Manager/QR/carrier terminal). Add a reporting matrix.

General Shipping — strainers, records, seals, placards

Use 100-mesh strainers (except barges/tankers/pipeline); inspect/clean/repair and keep written records; affix serially numbered seals and record on shipping docs; furnish placards per 49 CFR 172.506/.508.

Proposal covers 100-mesh strainers and records; seals and recording; does not mention placards.

Partially Covered

Add explicit placarding compliance commitment and responsible role.

Inventory Control — 1 business day transaction entry; daily/monthly/EOY; EPoS; ATG verification; RO/TM checklists; DD1348-8 adjustments; tolerances; retention & 3-day retrieval; scan/upload

Extensive detailed requirements in supplement.

Proposal addresses one business day entry; daily/monthly/EOY and Sept 30 processing; EPoS and APSR upload/reconcile; ATG verification; RO/TM checklists; DD1348-8 explanations; retention on location; 3-day retrieval; scan/upload.

Covered

Add explicit statement that inventory recorded corrected to 60°F for each product, as required.

Inventory Control — Statement of authorized signatures

Contractor must furnish names/handwritten signatures of persons authorized to receive/accept GOPO; notify CO/PA when changes occur.

Not addressed.

Gap

Add as a deliverable/appendix (authorized signature list process and notification workflow).

Inventory Control — SYNCADA shipment transactions & motor carrier performance log

As directed, create electronic shipment transactions using SYNCADA; maintain daily written log of motor carrier performance; forward monthly to Regional office.

Not addressed.

Gap

Add procedures, system access assumptions, and sample log template.

Inventory Control — reporting fuel additives/slop fuel/transmix by NSN; identity change rules

Treat additives/slop/transmix as separate items; report gallons under NSN; DD1348-8 identity change for FSII blended/downgraded; no fractions; packaged additives tracked locally log.

Proposal discusses additive usage documentation; does not mention NSN reporting, gallons, no-fractions rule, or packaged additive ledger approach.

Gap

Add explicit compliance procedures aligning to (c)(3) items (i) and (ii).

Storage tank out of service — telephone + written; time/date; unrecoverable estimate approved before submission

Requirement in inventory supplement (c)(1).

Proposal commits to immediate telephone notice and written confirmation; estimate unrecoverable bottoms for review/approval.

Covered

Add explicit inclusion of date/time elements and identify authorized Government representative (QR/PA).

Change in DFSP operator (handover procedures)

Joint gauging; DD2920/2921C; DD1348-8 certification text; mailing copies; etc.

Not addressed.

Gap

Even if future event, include transition plan acknowledgement to show understanding; may be evaluated under management approach.

Proposal Submission & “Data Requirements (Storage)” — Mandatory Artifacts Checklist

Mandatory Submission Item (Reference Criteria Section L / Data Requirements)Reference Criteria RequirementPresent in Draft Document?Gap / RiskRecommendation to Align

Map showing exact facility location

Data Requirements (Storage) (a): proposal accompanied by map.

Mentioned as will provide.

Medium risk if omitted

Include as Appendix A; label with facility address and coordinates; reference Subfactor 1.

Schematic drawing of facility layout & relation to other facilities

Data Requirements (a).

Mentioned as will provide.

Medium risk if omitted

Include as Appendix B; show dock, tanks, manifolds, pipeline tie-in, truck/rail racks, security perimeter.

Description of equipment, line systems, pump capacities

Data Requirements (a).

Partially described (pump rate minima for marine) but not a full equipment list.

Medium risk

Provide equipment register: pumps (type, capacity), meters, strainers, additive skids, manifolds, valves, comms/alarm, firewater system.

Complete cleaning/maintenance/repair history per tank + API 653 last & next dates

Data Requirements (a).

Stated will provide; not itemized in text.

Medium risk

Add tank-by-tank history sheets and API 653 dates; cross-reference E18 where applicable.

Verify certified strapping charts available per tank; provide upon request

Data Requirements (b).

Explicitly stated.

Covered

Add where they are controlled (document control) and certifying authority/date.

Tank bottoms (barrels) for each tank

Data Requirements (c).

Not provided.

High risk

Add a table listing unrecoverable bottoms volume per tank (barrels) and method of determination.

Pipeline and manifold fill (barrels)

Data Requirements (c).

Not provided.

High risk

Provide pipeline/manifold line-fill volumes by segment and how isolated/handled.

Ballast water receiving capacity

Data Requirements (c).

Not provided.

Medium risk

State ballast water handling capacity and environmental compliance approach (permits, containment).

Maximum safe fill capacity for each tank + summary of computation

Data Requirements (c).

States will provide safe fill determinations; computation summary not provided.

High risk

Provide safe fill calculation basis (overfill protection setpoints, freeboard, temp expansion) and values per tank.

Segregated system description (if not dedicated) incl products moved, specs, and flush/drain procedures

Data Requirements (d).

Proposal implies dedicated segregation/grade segregation but does not explicitly state whether system is dedicated vs segregated system in lieu of preferred dedicated system.

Medium risk

Add explicit statement: dedicated system (preferred) OR if segregated, provide full (d)(1)-(2) narrative with product list/specs and line-fill handling procedures.

Dredging charts for berthing evaluation

Subfactor 5/6 require “current dredging charts for evaluation.”

Stated will provide; not included in text.

High risk

Attach current dredging chart(s) and date/source; reference berth depth vs 35 ft draft requirement.

Technical proposal format / page limits / volume separation

Addendum to 52.212-1: volumes; 75-page limit technical; 2-page cover letter; etc.

Draft Document is structured by volumes, but no explicit page count compliance evidence.

Low risk (packaging)

Ensure final submission meets volume/page limit rules; add internal compliance check (no need to discuss fonts in analysis).

Cover letter required fields (RFP #, proposal title, technical POC, authorized negotiators)

Addendum (Cover Letter).

Cover letter includes RFP # and general narrative; does not list required POC details or K33.01 authorized negotiators list.

Medium risk

Add POC block and include authorized negotiators table per solicitation.

Exceptions to terms (affirmative statement if none)

Addendum (Exceptions).

Explicit: “We take no exceptions…”

Covered

Ensure signed company letter as required.

Terms of any express warranty per FAR 52.212-4(o)

Addendum item (3).

Not provided.

Medium risk

Provide warranty terms or state standard commercial warranty (if any) consistent with FAR 52.212-4(o).

Mandatory fill-ins: Section F contractor fill-ins; Section G contractor fill-ins; Section K non-SAM fill-ins

Addendum item (4).

Not included in proposal narrative.

High risk

Complete all solicitation fill-in blanks (addresses, WAWF points of contact blanks, contract period location address line, etc.) and include a completed compliance annex.

Acknowledgement of amendments (signed SF-30)

Addendum item (5).

Not addressed.

Medium risk

Add an amendments log and include executed SF-30s.

Declaration of partnerships / teaming arrangements incl % and roles

Addendum item (6).

Addresses teaming “where teaming arrangements are proposed” but no specific declaration.

Partially Covered

Add explicit statement: no teaming OR provide required summary, percentage, and relationship type.

Past performance: reference list + PPQ handling rules

Volume II instructions.

Proposal states will provide attachment VI and distribute PPQs; states not submit PPQs on behalf.

Covered

Ensure reference list meets required composition (3 relevant + additional DLA/private as applicable).

Price proposal form attachment II; pricing in USD; acceptance period 180 days

Volume III instructions; proposal acceptance period supplement.

Narrative describes evaluation math; states USD; states acceptance at least 180 days.

Partially Covered

Must include completed Attachment II and explicitly state acceptance period value in the offer (e.g., 180+ days).

Cybersecurity / Information Systems / Supply Chain Clauses — Compliance Evidence Gaps (Material Contractual Risk)

Clause / Topic (Reference Criteria)Requirement SummaryDraft Document EvidenceStatusRisk / Recommendation

FAR 52.204-21 Basic Safeguarding of Covered Contractor Information Systems

Implement 15 basic safeguarding controls; flow down to subs where FCI resides.

Not discussed.

Gap

Add IT/security appendix describing how FCI in inventory/accounting systems and proposal communications are safeguarded; include subcontract flowdown commitment.

DFARS 252.204-7012 Safeguarding CDI & Cyber Incident Reporting

Implement NIST SP 800-171; report incidents within 72 hours via DIBNet; preserve media 90 days; malicious software submission; FedRAMP Moderate for cloud; flow down.

Not discussed beyond ADP Level III/NAC for system access.

Gap

High risk for award eligibility/compliance. Provide System Security Plan (SSP) summary, incident response/reporting process, media preservation, and any cloud service posture (FedRAMP Moderate).

DFARS 252.204-7020 NIST SP 800-171 DoD Assessment Requirements + 252.204-7019 notice

Must have current assessment scores in SPRS (<=3 years) for relevant covered systems; Govt may conduct Medium/High assessment; subcontractor assessment requirement.

Not addressed.

Gap

Include SPRS score(s), assessment date, NIST version, CAGE mapping, POA&M completion date; include subcontractor assessment gating process.

DFARS 252.204-7021 CMMC certificate

Maintain current CMMC level required by contract; flow down.

Not addressed.

Gap

Include CMMC level certificate evidence (if required by this solicitation/contract) and plan to maintain during performance; flowdown language.

FAR 52.204-25 / 52.204-26 Section 889 covered telecom; DFARS 252.204-7018 covered defense telecom

Prohibit covered telecom equipment/services; reporting to DIBNet if identified; representations required in Section K/SAM.

Not addressed in technical volume.

Gap

Ensure representations completed in SAM/Section K; add internal supply chain screening process and reporting workflow.

FAR 52.204-27 TikTok/ByteDance prohibition

No covered application on Govt or contractor IT used under contract.

Not addressed.

Gap

Add policy statement and enforcement controls for contractor-furnished devices used for contract work.

DFARS 252.204-7000 Disclosure of Information

No release of unclassified contract info without CO approval; flow down.

Not addressed.

Gap

Add communications/public release procedure and subcontract flowdown acknowledgment.

DFARS 252.204-7003 Government personnel work product control

Cannot require DoD to relinquish work products.

Not addressed.

Gap

Add acknowledgement in management approach.

WAWF (DFARS 252.232-7003 / -7006) invoicing and routing data

Submit invoices/receiving reports via WAWF; use Invoice 2-in-1; routing table; SAM E-Biz POC registration.

Not addressed in proposal.

Gap

Add invoicing/closeout plan: WAWF registration, document type, routing DoDAACs, internal controls.

Risk Register (LPTA) — Unacceptability Drivers and Performance/Compliance Risks

Risk IDRisk DescriptionRoot Cause (Gap)LikelihoodImpact (LPTA/Performance)Recommended Mitigation (No timelines)

R-01

Proposal rated Unacceptable under Subfactor 3 due to missing tank technical data package

Tank dimensions/type/bottoms/safe fill computation not included as required by Section M and Data Requirements (Storage).

High

High (Unacceptable = eliminated)

Add tank-by-tank data table and supporting attachments; explicitly show 1,013,000 bbl available at award and min two interconnected tanks.

R-02

Proposal rated Unacceptable under Subfactor 5/6 due to missing required dredging charts / berthing documentation

Charts and detailed berth schematics not attached; only stated they will be provided.

Medium

High

Attach dredging charts and detailed mooring/berth narrative and diagrams; crosswalk to vessel limits and draft.

R-03

Proposal deemed non-responsive for testing option not selected

Sampling/testing supplement requires selecting one of three testing options; proposal is ambiguous.

High

High

Explicitly choose testing option and provide procedures, resources, and cost treatment consistent with monthly service charge / reimbursement rules.

R-04

Cyber/security compliance concerns create award/administrative delays or noncompliance findings post-award

No explicit FAR/DFARS cyber clause compliance evidence (NIST 800-171, SPRS, CMMC, incident reporting).

Medium

High

Add cybersecurity compliance annex: SSP summary, SPRS scores, incident response, cloud/FedRAMP posture, CMMC certificate, flowdowns.

R-05

Administrative rejection/non-responsiveness due to missing mandatory fill-ins and attachments

Section F/G/K fill-ins, authorized negotiators, SF-30 acknowledgements, warranty terms not shown.

Medium

High

Create a compliance checklist and include completed fill-in pages, signed documents, negotiator list, warranty statement.

R-06

Operational noncompliance risk in inventory control special requirements (SYNCADA, motor carrier logs, slop/additives NSN rules)

Several inventory supplement (c) items not addressed.

Medium

Medium

Add detailed SOPs and templates for SYNCADA shipments, motor carrier performance logs, identity change and additive/slop accounting rules.

R-07

Water bottoms and surveillance program found procedurally incomplete (floating roof after-rain; recordkeeping specificity)

Some detailed supplement steps not explicitly included.

Low

Medium

Add explicit procedural statements and record forms for after-rain gauging (if applicable) and required recording frequency.

Recommendations to Enhance Alignment (Actionable, Solicitation-Cross-Referenced)

RecommendationApplies To (Ref Criteria Section)What to Add/Change in Draft Document (input_proposal.docx)Expected Alignment Benefit

Add a Requirements Compliance Matrix (RCM) crosswalking each Subfactor and each Supplement paragraph to proposal sections and appendices

Section M subfactors; Supplements in Section C/F; Data Requirements (Storage)

Create a table listing every “must/shall” with page/appendix references; include a status column and responsible lead.

Reduces evaluation ambiguity; improves Acceptable likelihood under LPTA.

Provide the full “Data Requirements (Storage)” attachment set as appendices

Supplement: Data Requirements (Storage) (a)-(e)

Appendices: map; facility schematic; equipment/line system/pump capacities; tank history sheets; API 653 last/next; certified strapping chart verification; tank bottoms; pipeline/manifold fill; ballast capacity; maximum safe fill computation summary; segregated vs dedicated system declaration; dredging charts.

Directly addresses solicitation warning that missing technical data can make proposal technically unacceptable.

Explicitly select and describe the Testing Option (self-perform / Gov uses contractor facility / commercial lab) and include a 24-hour transport workflow if applicable

Sampling & Testing Supplement (b)

State selected checkbox option in narrative; identify lab resources/qualifications, QA/QC, chain of custody, sample transport SOP, and reimbursement handling.

Eliminates non-responsiveness risk; strengthens Subfactor 7 acceptability.

Add explicit custody transfer point statements for each receipt and shipment mode, matching solicitation wording

General Receiving & Storing (e)-(h); General Shipping (j)-(m)

Insert a concise table: mode → custody point → metering/documents → risk-of-loss controls.

Shows precise contract understanding; reduces disputes and audit risk.

Expand shipping conveyance deficiency reporting procedures (tanker/barge, tank car, truck) and add placarding compliance statement

General Shipping (c), (f)

Include contact routing, required notification method, and internal escalation; add 49 CFR placard furnishing/affixing procedure.

Improves compliance and safety; reduces shipment delays and demurrage exposure.

Add Inventory Control ‘Other Requirements’ procedures: authorized signatures list, SYNCADA transactions, carrier performance logs, additive/slop/transmix NSN accounting rules, and DFSP operator transition plan

Inventory Control supplement (c)(3)-(7)

Provide SOPs and templates (authorized signature statement, DD1348-8 identity change rules, SYNCADA steps, daily carrier log template, transition checklist).

Closes discrete but material compliance gaps; improves auditability perception.

Add a Cybersecurity & IT Compliance Annex addressing FAR 52.204-21 and DFARS 252.204-7012/7020/7021, plus Section 889 and TikTok prohibitions

Section I clauses; Section L/K representations

Provide SSP summary, NIST 800-171 implementation statement, SPRS score details, incident reporting/preservation process, CMMC certificate (if required), supply chain screening, TikTok device policy, subcontract flowdowns.

Reduces contractual and eligibility risk; demonstrates readiness for DoD cyber compliance.

Add WAWF invoicing/receiving report procedure and identify internal roles; confirm Invoice 2-in-1 document type and routing data usage

Section G DFARS 252.232-7003/-7006

Include WAWF registration confirmation approach, invoice data fields, routing DoDAACs, and internal review controls.

Improves post-award execution confidence; reduces payment processing issues.

Include the exact contractor certification text required when QR not present and QC program approved, and reference authorization letter mechanism

General Shipping (a)

Copy/paste the solicitation’s certification text into an appendix and reference where it will be placed on shipping documents.

Prevents document nonconformance during QR absence.

Add explicit statements mirroring supplement language for Security & Fire Protection emergency assistance entities and GOPO care/liability acknowledgement

Security & Fire Protection (e); GOPO responsibility supplement (b)-(e)

Name FBI, Secret Service, USMS, FEMA; add “sound industrial practice” statement; add acknowledgement of reimbursement/assistance obligations.

Reduces interpretation risk and strengthens compliance posture.

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