Riftur

Additional Use Cases

Public use case

Air Force Fuel Delivery Proposal Compliance Gap Analysis

Solicitation

Air Force Materiel Command Liquid Propane/Diesel Fuel

Industry

NAICS 44-45 - Retail Trade

Executive Summary

This gap analysis maps each explicit performance requirement, constraint, and submittal obligation stated in solicitation_text.docx (PWS Sections 1–2 and appended FAR/DFARS representations/provisions) to evidence provided in input_proposal.docx. Requirements were decomposed at the clause/sub-clause level (e.g., Section 1.4.1 step items; Section 2.2.1 reporting deliverables) to avoid masking partial coverage. Coverage status uses four states: Covered (explicitly addressed with matching intent), Partially Covered (mentioned but missing a required element, threshold, timing, or responsible party), Gap (not addressed), and Conflict (proposal states a different requirement than the PWS). Special attention was applied to operational parameters that commonly trigger noncompliance risk in fuel delivery contracts: hours of operation alignment, access/security procedures, hazardous materials documentation lead-times and forms, distance/vehicle restrictions near facilities, and periodic reporting (quarterly and annual/interim inventory reporting). Risks were assessed based on operational impact (mission disruption), compliance exposure (base access, environmental reporting), and likelihood given the proposal’s current specificity. Recommendations focus on adding missing commitments, correcting conflicting statements, and explicitly adopting PWS language where it is prescriptive (e.g., grounding wire, “driver does not remain in vehicle,” appearance/recognizability, interim/final HAZMAT inventory reports).

Score Breakdown

Review output

Net Score

70%

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

67%

5% recoverable

Estimated from 16 status signals across 2 published compliance tables.

Requirements

76%

4.8% recoverable

Estimated from 69 status signals across 11 published requirements tables.

Evaluation Readiness

69%

4.7% recoverable

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

Requirement Coverage

85

reqs

Covered: 60% (51)

Partially Covered: 29% (25)

Missing: 11% (9)

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

1

2

0

Low

0

0

0

What Would Improve My Score

Unloading SOP completeness

+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

Targeted Recommendations to Enhance Alignment (Actionable, No Timelines)

Finding

Eliminates procedural gaps and reduces safety/compliance ambiguity during inspections.

Completion Standard

Update the proposal so this recommendation is directly evidenced: Unloading SOP completeness

HAZMAT approvals & records

+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

Targeted Recommendations to Enhance Alignment (Actionable, No Timelines)

Finding

Aligns to Section 2.2.1 approval and recordkeeping requirements; reduces risk of disapproved materials.

Completion Standard

Update the proposal so this recommendation is directly evidenced: HAZMAT approvals & records

HAZMAT reporting deliverables

+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

Targeted Recommendations to Enhance Alignment (Actionable, No Timelines)

Finding

Closes explicit PWS reporting gaps and supports contract closeout compliance.

Completion Standard

Update the proposal so this recommendation is directly evidenced: HAZMAT reporting deliverables

Security process specificity

+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

Targeted Recommendations to Enhance Alignment (Actionable, No Timelines)

Finding

Reduces likelihood of access delays and demonstrates precise compliance with PWS security procedures.

Completion Standard

Update the proposal so this recommendation is directly evidenced: Security process specificity

Vehicle restrictions

+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

Targeted Recommendations to Enhance Alignment (Actionable, No Timelines)

Finding

Addresses high-severity site security constraints that can halt performance.

Completion Standard

Update the proposal so this recommendation is directly evidenced: Vehicle restrictions

Requirements

76%

Details

Estimated from 69 status signals across 11 published requirements tables.

Compliance

67%

Details

Estimated from 16 status signals across 2 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

77%

Details

Estimated from 15 status signals across 1 published management table.

Past Performance

69%

Details

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

Risk

58%

Details

Estimated from 37 status signals across 3 published risk tables.

Production

69%

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

  • 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 Metadata & Inferred Methodology

3 rows
Iteminput_proposal.docxsolicitation_text.docx

Primary purpose

Describe contractor approach and compliance commitments for diesel/propane deliveries at RRS/Newport/Stockbridge

Define mandatory performance requirements, procedures, and compliance obligations (PWS) and representations (FAR/DFARS)

Method used

Requirement-by-requirement compliance narrative

Baseline criteria / acceptance standard

Key evaluation lens

Does the proposal explicitly commit to each PWS requirement with correct thresholds, timing, and process details?

Are requirements prescriptive (must/shall) vs guidance (should) and are they met?

Requirements

Authoritative requirement inventory and taxonomy.

11 tables

Requirement Coverage Matrix — PWS Section 1.1 Description of Services

9 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

1.1-a

Provide all management, tools, supplies, equipment, labor necessary to deliver fuel to Government-owned tanks safely

Section 1 states provide all management, labor, tools, equipment, supplies; repeated throughout

Covered

1.1-b

Propane autofill middle and end of each month during winter heating season (Oct–Apr)

Section 1 and 2 explicitly commit to mid-month and end-of-month Oct–Apr

Covered

1.1-c

Fuel deliveries performed between 0700–1600 Mon–Fri excluding Government holidays

Section 2 states 0700–1600 Mon–Fri excluding Federal holidays

Covered

1.1-d

Contractor responsible to notify designated POC to gain access

Section 2 and 8: will notify designated POC prior to arrival to gain access

Covered

1.1-e

Obtain POC signature on delivery ticket; leave copy at site

Section 1/2/8: obtain signature; leave copy on site

Covered

1.1-f

Delivery ticket must include: fuel type, quantity, tank ID and facility number(s), date/time, name of contractor delivering fuel

Section 1 lists all required fields

Covered

1.1-g

Respond to requests for fuel delivery within 72 hours of receipt AND complete delivery within timeframe

Sections 1/2: complete Government-requested deliveries within 72 hours; diesel within 72 hours of receipt

Covered

1.1-h

Authorized requester list provided by CO; updated as necessary

Mentions “authorized Government requester” but does not explicitly acknowledge CO-provided authorized list/updates

Partially Covered

Add commitment to accept/use CO’s authorized requester list and process updates.

1.1-i

Provide means of answering emergency calls on a 24-hour/day basis

Section 2: 24-hour emergency call capability staffed by trained personnel

Covered

Requirement Coverage Matrix — PWS Section 1.2 Fuel Products

2 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

1.2-a

Diesel Fuel Grade DF1 NSN 9140-00-286-5286

Section 1 explicitly states Diesel Fuel Grade DF1 with NSN

Covered

1.2-b

Propane Type II odorized, Federal Specification BBG-110, 95% odorized propane

Section 1 explicitly states Type II odorized propane BBG-110 95%

Covered

Requirement Coverage Matrix — PWS Section 1.3 Tanks to be Serviced (Scope Confirmation)

2 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

1.3-a

Service listed diesel tanks/locations and capacities/usage (Buildings 3 W/E/N; 106; 103; Stockbridge; Irish Hill E/W; Tanner Hill 1609/1610)

Section 3 lists all diesel locations and acknowledges estimated annual usage 2,100 gallons; acknowledges multi-tank at Building 3

Covered

1.3-b

Service listed propane tanks/locations and capacities/usage incl. Stockbridge 1477 below-ground and expose fill pipe in winter

Section 2/3 explicitly mention Bldg 1477 below-ground and exposing fill pipe in winter

Covered

Requirement Coverage Matrix — PWS Section 1.4 Unloading Procedures (Step-by-step)

21 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

1.4-Gen

Personnel prepared to prevent/control spills; familiar with overfill prevention devices

Section 4: trained and periodically re-briefed; familiar with overfill prevention devices

Covered

1.4.1-1

Extinguish all flames/sources of ignition

Section 4: ensure sources of ignition extinguished

Covered

1.4.1-2

Motor and lights off; parking brake set

Section 4: motor and lights turned off where required; parking brake set

Partially Covered

PWS is unconditional; proposal softens with “where required.” Commit to always comply as specified.

1.4.1-3

Attach grounding wire to truck body

Not stated

Gap

Explicitly add grounding/bonding step.

1.4.1-4

Remove ungrounded objects from loading/unloading area

Not stated

Gap

Add commitment to clear ungrounded objects from area.

1.4.1-5

Chock truck wheels

Section 4: wheels chocked

Covered

1.4.1-6

Check hose and connections

Section 4: hoses and connections inspected

Covered

1.4.1-7

Check tank level gauge or stick tank; confirm level and sufficient capacity; note working capacity

Section 4: confirm tank level and sufficient working capacity before transfer

Covered

1.4.1-8

Ensure driver does not remain in vehicle

Section 4 says transfer operator remains present and attentive; does not explicitly state driver not in vehicle

Partially Covered

Add explicit statement: driver does not remain in vehicle during loading/unloading.

1.4.1-9

Cover all storm and sanitary sewer drains prior to dispensing fuel

Section 4: will cover drains prior to dispensing fuel “when required by the PWS”

Partially Covered

PWS is unconditional (“will be covered”). Remove conditional phrasing.

1.4.1-10

Absorbent material out and readily available

Section 4: stage absorbent materials immediately available

Covered

1.4.2-1

Transfer operator present and attentive at all times

Section 4: operator remains present and attentive at all times

Covered

1.4.2-2

Do not fill above level that results in overflow after thermal expansion; fill levels at 90% capacity

Section 3/4: 90% max fill threshold and thermal expansion basis

Covered

1.4.2-3

Inform driver to stop filling once tank reaches 90%

Section 4: positive confirmation of stop-fill at required level

Covered

1.4.3-1

Close loading valves; note spillage; remedial action if necessary

Section 4: close valves; inspect for signs of spillage; remedial action

Covered

1.4.3-2

Close all hatches tightly

Section 4: close hatches

Covered

1.4.3-3

Close internal safety valves

Section 4: close internal safety valves

Covered

1.4.4-1

Before departure: check drains/outlets/connections for leakage

Section 4: final unloading area check before/after departure; does not explicitly list truck drains/outlets/connections

Partially Covered

Add explicit check of truck drains/outlets/connections for leakage prior to departure.

1.4.4-2

Check unloading area for spills; apply absorbent if needed

Section 4: inspect for spillage; stage absorbents; final area check

Covered

1.4.5-1

Upon departure: check valves/caps/drains/connections for closure/leakage; re-lock if necessary

Not explicitly stated (mentions closure and absence of leakage generally)

Partially Covered

Add explicit post-departure closure/leakage/relock check language.

1.4.5-2

Final check of unloading area

Section 4: final unloading area check

Covered

Requirement Coverage Matrix — PWS Section 1.5 Spills

6 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

1.5-a

No intentional discharge/spill/improper disposal; minimize/avoid spills

Section 4 commits to prevention, disciplined procedures, environmental stewardship

Covered

1.5-b

Spill kit sufficient for worst case spill (volume and hazard level)

Section 4: spill kit sufficient for worst case spill scenario appropriate to volumes/hazard level

Covered

1.5-c

Define spill as uncontrolled release to environment

Section 4: treats any uncontrolled release as a spill

Covered

1.5-d

Report spills (excluding clean water) immediately after control to Security Police and Haz Waste Program Manager for evaluation

Section 4: immediately notify Security Police and Haz Waste Program Manager after control; support evaluation

Covered

1.5-e

Contractor shall clean and remediate spills/releases; Govt may clean and seek reimbursement if not done promptly

Section 4: accepts responsibility to clean/remediate; act without delay to avoid govt cleanup/reimbursement

Covered

1.5-f

Provide correct contact numbers during normal duty hours

Section 4 lists both numbers as in PWS

Covered

Requirement Coverage Matrix — PWS Section 1.6 Supplies (Inventory + SDS + CFC prohibition)

7 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

1.6-a

Provide complete list of all supplies anticipated for contract period to CO not later than pre-performance conference for acceptance

Section 5/10: will furnish complete list not later than pre-performance conference

Covered

1.6-b

New supplies after award require acceptance before use on installation

Section 5: will not introduce new supplies without Government acceptance

Covered

1.6-c

Supply inventory list must include (a)-(e): product name, manufacturer, use, disposal procedures, storage provisions

Section 5 includes all elements

Covered

1.6-d

Contractor responsible for proper disposal of all supplies

Section 5: disposal in accordance with regulatory requirements and site rules

Covered

1.6-e

Provide SDS for each supply item; train employees on proper use/disposal

Section 5: provide SDS/PRFs; train employees on use/handling/disposal

Covered

1.6-f

All cleaning and supplies shall be non-flammable

Section 5: ensure all cleaning and supplies are non-flammable

Covered

1.6-g

Products containing CFCs or ozone depleting substances not allowed/approved

Section 5: will not propose or use any products containing CFCs or ozone-depleting substances

Covered

Requirement Coverage Matrix — PWS Section 2.1 Protection of Government Property

1 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

2.1-a

Use reasonable care to avoid damaging buildings, equipment, vegetation; repair/replace at no expense if damage due to contractor failure

Proposal generally states protect Government property (Section 10) but does not explicitly accept repair/replace obligation

Partially Covered

Add explicit acknowledgement of FAR 52.237-2 responsibilities (repair/replace at no cost as directed by CO).

Requirement Coverage Matrix — PWS Section 2.2 Environmental Requirements / HAZMAT Controls & Reporting

12 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

2.2-Gen

Comply with all applicable Federal/State/local environmental codes and additional guidance

Section 5 commits to comply with all applicable laws/regulations

Covered

2.2.1-a

All hazardous materials brought on-site must be approved using AF 3952 and local processes

Section 5 references PRFs and SDS; does not explicitly mention AF Form 3952

Partially Covered

Add explicit commitment to AF Form 3952 approval process (not just PRF/SDS).

2.2.1-b

Government may remove materials containing prohibited ingredients

Not explicitly acknowledged

Gap

Add acknowledgement that Government may disapprove/remove materials and contractor will substitute.

2.2.1-c

Materials requiring EESOH-MIS tracking will be identified; require Contractor HAZMAT PRF incl. fuels for generators/equipment; include non-commodity batteries

Section 5: supports EESOH-MIS tracking where applicable; mentions fuels may require tracking/review

Partially Covered

Add explicit inclusion of non-commodity batteries and acceptance of Government direction on what must be tracked.

2.2.1-d

Anticipate 7–10 business day approval turnaround; if initial submissions >=15, anticipate 20–25 business days

Section 5: mentions 7–10 business days and longer lead times for larger initial submissions; does not state 20–25 business day expectation

Partially Covered

Add explicit 20–25 business day lead time commitment for initial submissions of 15+.

2.2.1-e

Retain PRFs for duration of project

Section 5: retain PRFs for duration of project

Covered

2.2.1-f

Submit Contractor Material Usage Data Sheet to COR quarterly for each unique material

Section 5: submit quarterly Contractor Material Usage Data Sheets to COR for each unique material

Covered

2.2.1-g

Remove any HAZMAT not used in entirety from installation; remove by end of each workday unless prior approval granted with amounts/location

Section 5: remove HAZMAT not used in entirety; no unauthorized storage end of workday unless approved with documented amounts/locations

Covered

2.2.1-h

Maintain up-to-date hazmat inventory with SDS copies for all materials used; maintain complete copy of all approved SDS and AF Form 3952s

Section 5: maintain on-site inventory with SDS copies; does not explicitly state maintaining complete copy of approved AF 3952s

Partially Covered

Add explicit recordkeeping for approved AF Form 3952s (and approved SDS set).

2.2.1-i

End of contract: remove all excess hazardous materials

Section 5: remove HAZMAT not used; does not explicitly address end-of-contract excess removal

Partially Covered

Add explicit end-of-contract removal commitment.

2.2.1-j

Submit interim inventory report not later than 10 working days following each contract year of HAZMAT used since last report

Not mentioned

Gap

Add annual interim inventory reporting requirement to CO/COR within 10 working days after each contract year.

2.2.1-k

Submit final inventory report listing all HAZMAT used, total amount used, and disposition of remaining HAZMAT over duration

Not mentioned

Gap

Add final inventory report commitment with required contents.

Requirement Coverage Matrix — PWS Section 2.5 Recognized Holidays

2 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

2.5-a

Not required to provide service on federal holidays except emergencies; if holiday falls on scheduled service day contractor reschedules for first day post observance

Proposal states excluding Federal holidays; does not explicitly commit to rescheduling rule for holidays occurring on scheduled service day

Partially Covered

Add explicit rescheduling commitment: first business day after holiday observance when a scheduled service day is impacted.

2.5-b

Observed holiday rules (Sat=Fri, Sun=Mon)

Not mentioned

Gap

Add acknowledgement that contractor will follow Government observance rules for scheduling.

Requirement Coverage Matrix — PWS Section 2.6 Site Closures

2 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

2.6-a

Site Director may limit access due to emergency; announcements do not authorize time off/payment for work not performed; contractor notifies employees and makes alternate arrangements

Section 2 explicitly recognizes closure announcements do not authorize payment; coordinate and reschedule

Partially Covered

Add explicit commitment to notify employees of closure/delayed reporting and make alternate schedule arrangements.

2.6-b

Facilities remain open for contractors during unscheduled federal closures/non-emergency admin leave; work missed due to emergency closure accomplished ASAP after reopening

Section 2 references emergency closures; does not address non-emergency admin leave situations

Gap

Add statement acknowledging contractors may still be expected to work during non-emergency Government admin leave closures and will coordinate access.

Requirement Coverage Matrix — PWS Sections 2.8–2.11 (Traffic, Weapons, Crisis Performance, Government Interface)

5 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

2.8

Comply with all site traffic regulations

Section 6: comply with site traffic laws

Covered

2.9

Weapons/firearms/ammunition prohibited on person or in vehicles while on site

Section 6: enforce weapons prohibition for employees and vehicles

Covered

2.10

Services not essential during declared crisis

Proposal mentions coordination during heightened conditions but does not acknowledge non-essential designation

Gap

Add acknowledgement that services are not essential during declared crisis and that performance will follow Government direction.

2.11-a

Do not unduly interfere with Government operations

Section 1/2/8: minimize interference; comply with cease-work requests

Covered

2.11-b

If supervisor requests cease work: cease and report instructions incl name to CO immediately; notify CO verbally of disputes and follow up in writing

Section 8: cease immediately and report name to CO expeditiously; follow up in writing when required; does not explicitly mention verbal notification of disputes with customers/other contractors

Partially Covered

Add explicit commitment to verbally notify CO of disputes with customers/other contractors and follow-up in writing.

Compliance

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

2 tables

Requirement Coverage Matrix — PWS Section 2.7 Security (Access, Visit Requests, Vehicle Rules, Badging)

13 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

2.7.1

For estimation access arrangements through Contracting Office; escorted for estimation

Not addressed (proposal is post-award performance focused)

Gap

If applicable, acknowledge pre-award site visit/estimation access is via Contracting Office and escorted.

2.7.2-a

DBIDS pre-enrollment and sending required info to VCC org box (email) including QR/six-digit code, date/length of visit

Proposal generally references DBIDS pre-enrollment and visit request submission; does not include the VCC org box/email process and specific data elements

Partially Covered

Add explicit process and data elements (and identify VCC org box email) to show precise compliance.

2.7.2-b

Visit request must contain full name incl middle initial, DOB, DL state issuance, city/state of birth; non-US citizens not allowed; green card handling; no foreign nationals allowed

Proposal states no foreign nationals; all U.S. citizens; can meet visit request and DBIDS requirements; does not enumerate required visit request data elements

Partially Covered

Add explicit list of required visit request data elements to reduce access delays.

2.7.3

Provide contractor phone number and Project Leader/Supervisor/Foreman contact number for Desk Sergeant; desk reachable 24h at 330-2961

Proposal provides 24-hour emergency line and mentions interfacing with Security Police; does not explicitly commit to providing phone numbers for Desk Sergeant use

Partially Covered

Add explicit commitment to provide contractor phone + supervisor contact for Law Enforcement Desk Sergeant.

2.7.4

Building access via proximity badge; DBIDS badge acquired with valid visit request; worn at all times; returned to COR at completion; lost badges reported ASAP

Proposal: obtain/wear DBIDS badges; report lost badges; does not mention returning badges to COR upon final inspection/acceptance

Partially Covered

Add explicit badge return requirement at final inspection/acceptance.

2.7.5

RRS complex access via main gate 304 Brooks Rd; vehicle on access list supported by magnetic media entry badge

Proposal references main gate, vehicle search, and access processes; does not mention magnetic media entry badge/access list mechanics

Partially Covered

Add explicit acknowledgement of access list + magnetic media entry badge if required.

2.7.6

Newport/Stockbridge access follow same visit request; coordinated through RIO Facility Managers

Proposal: coordinate with RIOC and Security forces; mentions Newport/Stockbridge but not explicit RIO Facility Managers

Partially Covered

Add explicit coordination through RIO Facility Managers for Newport/Stockbridge.

2.7.7-a

All commercial vehicles searched; operators aware of pull-off area; non-needed vehicles in visitor parking unless cleared

Proposal: comply with commercial vehicle search and pull-off/inspection process; does not address parking rule for non-needed vehicles

Partially Covered

Add explicit compliance with visitor parking requirement for non-needed vehicles unless cleared.

2.7.7-b

No vehicles (other than mowers) within 25 meters (80 ft) of RRS facilities; one-time deliveries can be escorted

Proposal mentions vehicle placement/access limitations and escort requirements generally; does not explicitly commit to 25m/80ft standoff

Partially Covered

Add explicit commitment to 25m (80 ft) vehicle standoff unless escorted/authorized.

2.7.8

Follow posted signage

Proposal: comply with posted signage

Covered

2.7.9

RRS Police notify of emergencies requiring evacuation/work stoppage such as FP condition increase

Proposal: coordinate with RRS Police on emergencies/evacuation/work stoppage and FP conditions

Covered

2.7.10

Photography/videography strictly prohibited

Proposal: prohibition acknowledged

Covered

2.7.11

Comply with AFFARS 5352.242-9000; required documentation submitted at pre-performance conference

Proposal: commits to comply with access/badging and AFFARS 5352.242-9000; mentions access documentation at pre-performance conference

Covered

FAR/DFARS Provision Alignment — Representations & Telecom Restrictions

3 rows
Provision / RequirementReference Criteria (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

FAR 52.212-3 Annual Reps & Certs in SAM

Offeror verifies SAM reps current/accurate within last 12 months; incorporated by reference

Section 9: confirms reps/certs current in SAM and incorporated by reference

Covered

FAR 52.204-24 Section 889 representation + reasonable inquiry + SAM excluded parties review

Review SAM excluded parties list; represent whether will provide/use covered telecom

Section 9: will comply; conduct/document reasonable inquiry; review SAM exclusions list; disclose if needed

Partially Covered

Proposal does not include the checkbox-style representations (will/will not; does/does not). If solicitation requires completion, include explicit representation statements consistent with 52.204-24(d)(1)-(2) and disclosure stance.

DFARS 252.204-7017 representation re covered defense telecom

Conditional additional representation if offeror indicated “does provide” in 7016; otherwise not required

Section 9: commits to comply; does not provide the specific representation conditionality

Partially Covered

Add explicit statement aligning to the representation logic (e.g., confirm not providing covered defense telecom, or complete required will/will not statement if applicable).

Management

Management approach, staffing, roles, and execution ownership.

1 tables

Requirement Coverage Matrix — PWS Sections 2.12–2.17 (Safety, Operators, Workmanship, Tools, Contract Manager, Personnel)

15 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

2.12

Comply with OSHA and all safety requirements; industry standards and PPE

Section 7: written safety program; training; PPE; OSHA compliance

Covered

2.12.1.1

Maintain written Safety Program; available for review upon request by CO

Section 7: maintain written Safety Program; available for Government review upon request by CO

Covered

2.12.1.2

Notify CO expeditiously in event of mishap on premises

Section 7: notify CO expeditiously

Covered

2.12.1.3

Mishap documentation must include items (a)-(h)

Section 7 lists all required data elements

Covered

2.13

Operators must possess current appropriate license/cert for equipment utilized

Section 7: operators possess current and appropriate licenses/certificates

Covered

2.14

All work performed by qualified, experienced personnel

Section 7: qualified and experienced; only trained authorized personnel perform unloading

Covered

2.15

All tools furnished by contractor

Section 1: provides tools/equipment; reiterated

Covered

2.16-a

Establish/maintain office through which contract manager/alternate can be contacted during work hours

Section 8: office reachable during normal duty hours

Covered

2.16-b

Contract manager/alternate available within 1 hour during normal duty hours to meet on site

Section 8: available within one hour to meet on site

Covered

2.16-c

Provide CO telephone number(s) for validation results and complaints

Section 8: provide CO primary phone number for validation results and complaints

Covered

2.16-d

Provide names/phone numbers for after-hours POCs; keep updated upon changes

Section 8: provide after-hours POCs; keep current

Covered

2.16-e

Contract manager/alternate has full authority on daily operations matters

Section 8: full authority

Covered

2.17-a

Personnel neat appearance

Not addressed

Gap

Add explicit commitment to neat appearance.

2.17-b

Personnel easily recognizable while on installation in conjunction with contract

Not addressed (no uniform/ID/vehicle marking statement)

Gap

Add plan for recognizability (uniform/shirts/outerwear, company ID, marked vehicles as allowed).

2.17-c

Government may restrict employment of contractor employee deemed threat

Not acknowledged

Gap

Add acknowledgement of Government right to restrict/remove personnel and contractor will replace promptly.

Risk

Risk register findings, assumptions, exceptions, and deviations.

3 tables

Requirement Coverage Matrix — PWS Section 2.4 Hours of Operation (Potential Conflict Check)

2 rows
PWS Requirement IDRequirement (solicitation_text.docx)Proposal Evidence (input_proposal.docx)Coverage StatusGap / Notes

2.4-a

Normal duty hours are 0800–1600 Mon–Fri excluding Federal holidays

Proposal states deliveries between 0700–1600 Mon–Fri excluding Federal holidays

Conflict

PWS Section 1.1 states 0700–1600 for deliveries; Section 2.4 states 0800–1600 for services. Proposal should reconcile and state it will comply with the applicable window(s) as directed by COR/CO (e.g., deliveries per 1.1; other services/admin per 2.4).

2.4-b

May work weekends/holidays if approved in advance; off-hours work must be coordinated with RIOC and RRS Security forces

Section 2: deliveries outside standard hours/weekends/holidays only when approved in advance and coordinated with RIOC/RRS Security

Covered

Gap & Issue Register (Consolidated, Non-duplicative)

24 rows
Gap IDGap AreaMissing / Incorrect ItemWhere Required (solicitation_text.docx)ImpactRecommendation (no timeline)

G-01

Unloading procedure detail

Grounding wire attachment to truck body not stated

1.4.1 step 3

High (spill/fire/static ignition compliance risk; procedural nonconformance)

Add explicit step-by-step commitment mirroring PWS including grounding/bonding before transfer.

G-02

Unloading procedure detail

Remove ungrounded objects from loading/unloading area not stated

1.4.1 step 4

Medium (procedural nonconformance; safety audit finding)

Add explicit housekeeping/area control step per PWS.

G-03

Unloading procedure detail

Driver does not remain in vehicle during loading/unloading not explicitly stated

1.4.1 step 8

Medium (safety noncompliance; training/inspection issue)

Add explicit statement adopting PWS requirement.

G-04

Unloading procedure phrasing

Conditional language for motor/lights off and drain covering (“where required” / “when required”)

1.4.1 steps 2 and 9

Medium (could be read as non-commitment)

Replace conditional language with unconditional compliance to PWS steps.

G-05

Truck departure checks

Explicit checks of drains/outlets/connections; relock requirement not clearly stated

1.4.4, 1.4.5

Medium (leak during transit; compliance finding)

Add explicit before-departure and upon-departure checklist items matching PWS.

G-06

Government property protection

Explicit acceptance of repair/replace at no cost per FAR 52.237-2 not stated

2.1

Medium (liability ambiguity)

Add statement acknowledging FAR 52.237-2 obligations to repair/replace as directed by CO.

G-07

HAZMAT approvals/forms

AF Form 3952 approval process not explicitly cited

2.2.1

High (materials may be denied at gate/site; performance delays)

Explicitly commit to submit/maintain AF Form 3952s as required and keep approved copies.

G-08

HAZMAT governance

Acknowledgement that Government may disapprove/remove materials with prohibited ingredients not stated

2.2.1

Medium (rework/substitution delays)

Add acknowledgement and substitution approach (no prohibited ingredients; prompt replacement).

G-09

HAZMAT lead times

20–25 business day expectation for initial PRF/SDS submissions of 15+ not stated

2.2.1

Low-Medium (planning mismatch)

Add explicit recognition of 20–25 business day lead time for 15+ initial submissions.

G-10

HAZMAT reporting

Annual interim inventory report within 10 working days after each contract year not addressed

2.2.1

Medium (contract deliverable noncompliance)

Add commitment to submit interim inventory report to CO/COR with required timing/content.

G-11

HAZMAT reporting

Final inventory report content and submission not addressed

2.2.1

Medium (closeout noncompliance)

Add commitment to final inventory report listing all HAZMAT, totals, and disposition.

G-12

Hours of operation reconciliation

Potential conflict: 0700–1600 vs 0800–1600 in PWS sections

1.1 vs 2.4

Medium (delivery timing disputes / rejected deliveries)

Add clarifying statement: deliveries per Section 1.1 window unless otherwise directed; other activities per Section 2.4; confirm coordination with COR.

G-13

Holiday observance scheduling

Rescheduling rule (first day post holiday observance) and observed holiday rules not addressed

2.5

Low-Medium (missed scheduled service dates)

Add explicit holiday observance and rescheduling commitments.

G-14

Site closure non-emergency scenarios

Expectation that contractors may still work during non-emergency admin leave closures not addressed

2.6

Low-Medium (availability/access confusion)

Add statement acknowledging and coordinating for non-emergency closures/administrative leave situations.

G-15

Security visit request mechanics

Specific VCC org box email and required fields (QR/six-digit code, date/length) not included

2.7.2

Medium (access delays/denials)

Add explicit visit request submission workflow and data elements per PWS.

G-16

Security contact provisioning

Provide contractor phone + supervisor contact for Law Enforcement Desk Sergeant not explicitly stated

2.7.3

Low-Medium (coordination breakdown)

Add explicit commitment to provide those contact numbers for desk use.

G-17

Badge return

Return DBIDS badges to COR upon completion not stated

2.7.4

Low (administrative noncompliance)

Add explicit badge return and accountability statement.

G-18

Vehicle proximity restriction

No vehicles within 25m/80ft of facilities not explicitly stated

2.7.7

High (security violation; denied access; incident risk)

Add explicit compliance statement and operational method (standoff + escorted one-time deliveries).

G-19

Parking rule for non-needed vehicles

Visitor parking unless cleared by Security Office not stated

2.7.7

Low-Medium (gate/security noncompliance)

Add explicit parking compliance statement.

G-20

Crisis/non-essential services

Acknowledgement that services are not essential during declared crisis not addressed

2.10

Low-Medium (expectation mismatch)

Add statement acknowledging non-essential designation and that performance follows Government direction.

G-21

Government interface disputes

Verbal notification to CO of disputes with customers/other contractors and follow-up in writing not fully stated

2.11

Low (process noncompliance)

Add explicit commitment to verbal + written dispute reporting as specified.

G-22

Personnel standards

Neat appearance and easily recognizable requirement not addressed

2.17

Low-Medium (site access friction; inspection findings)

Add uniform/ID/recognizability plan and neat appearance commitment.

G-23

Personnel restrictions

Acknowledgement Government may restrict/remove personnel deemed a threat not stated

2.17

Medium (operational continuity risk if removal occurs)

Add acknowledgement and replacement commitment to maintain continuity.

G-24

Telecom representations formatting

Explicit 52.204-24 representation selections (will/will not; does/does not) not provided; DFARS 7017 conditional statement not explicit

FAR 52.204-24; DFARS 252.204-7017

Low-Medium (proposal responsiveness/admin rejection risk)

Include explicit representation statements consistent with the provisions (or state they are completed in required solicitation forms).

Risk Assessment (Operational, Compliance, and Performance)

6 rows
Risk IDRiskRoot Cause (Gap/Issue)LikelihoodImpact SeverityMitigation / Strengthening Action

R-01

Safety incident / spill due to incomplete adherence to prescriptive unloading steps

Missing grounding wire step; incomplete explicit departure checks (G-01, G-05)

Medium

High

Embed PWS unloading checklist verbatim in proposal/SOP; train and audit drivers against checklist.

R-02

Access denial or security violation near facilities

No explicit 25m/80ft vehicle standoff and parking rules (G-18, G-19)

Medium

High

Add explicit standoff/parking compliance and describe how routing/staging will meet it.

R-03

Environmental compliance deliverable failure (inventory reporting)

Missing interim/final HAZMAT inventory reporting commitments (G-10, G-11)

Medium

Medium-High

Add reporting commitments and assign responsibility to Contract Manager for submissions/recordkeeping.

R-04

Schedule disputes / rejected deliveries due to inconsistent hours

0700–1600 vs 0800–1600 inconsistency not reconciled (G-12)

Low-Medium

Medium

Clarify precedence and coordination; state deliveries will comply with PWS delivery window and COR direction.

R-05

Gate/access processing delays

Visit request workflow details and required data elements not enumerated (G-15)

Medium

Medium

Add visit request procedure including VCC org box, DBIDS pre-enrollment steps, and required information fields.

R-06

Administrative non-responsiveness finding for FAR/DFARS representations

Checkbox-style representations not explicit in narrative (G-24)

Low

Medium

Provide explicit representations or cross-reference completed solicitation forms.

Recovery

Prioritized fixes, clarification candidates, and recovery actions.

1 tables

Targeted Recommendations to Enhance Alignment (Actionable, No Timelines)

10 rows
Recommendation AreaSpecific Enhancement to input_proposal.docxPurpose / Alignment Benefit

Unloading SOP completeness

Add a PWS-mirroring unloading checklist that explicitly includes: attach grounding wire; remove ungrounded objects; driver not in vehicle; unconditional motor/lights off; unconditional drain covering; explicit before/upon departure leak/closure/relock checks

Eliminates procedural gaps and reduces safety/compliance ambiguity during inspections.

HAZMAT approvals & records

Explicitly state use of AF Form 3952 (AF 3952) in addition to PRF/SDS; commit to maintaining complete approved AF 3952 and SDS sets on-site

Aligns to Section 2.2.1 approval and recordkeeping requirements; reduces risk of disapproved materials.

HAZMAT reporting deliverables

Add commitments for (1) interim annual inventory report within 10 working days after each contract year and (2) final inventory report with totals and disposition of remaining HAZMAT

Closes explicit PWS reporting gaps and supports contract closeout compliance.

Security process specificity

Add the visit request submission mechanics (DBIDS pre-enrollment, VCC org box email, QR/six-digit code, date/length of visit) and the required personal data elements list for visit requests

Reduces likelihood of access delays and demonstrates precise compliance with PWS security procedures.

Vehicle restrictions

Add explicit compliance with 25m/80ft standoff, visitor parking for non-needed vehicles unless cleared, and escort procedures for one-time deliveries

Addresses high-severity site security constraints that can halt performance.

Hours/holidays/site closures

Reconcile hours of operation (deliveries vs general duty hours); add observed-holiday rules and rescheduling to first day post observance; acknowledge non-emergency admin leave closures may still allow contractor access/work

Prevents scheduling disputes and ensures alignment to operational planning requirements.

Personnel requirements

Add statements that personnel will maintain neat appearance, be easily recognizable (uniform/ID), and that contractor will comply with Government direction to restrict/remove personnel deemed a threat

Closes administrative/security-related gaps that commonly become access/acceptance issues.

Telecom representations clarity

Add explicit 52.204-24 representation outcomes (e.g., “will not provide” and “does not use” covered telecom) or clearly state these are completed in the solicitation’s required forms; similarly address DFARS 252.204-7017 conditional representation

Reduces risk of perceived non-responsiveness and ensures alignment with solicitation representation structure.

Authorized requester control

Add statement that deliveries will only be dispatched upon requests from individuals on the CO-provided authorized requester list (and that updates will be implemented immediately upon receipt)

Aligns dispatch control to PWS and reduces unauthorized delivery/payment disputes.

Government property damage clause

Add explicit acknowledgement of FAR 52.237-2 responsibilities to repair/replace at no cost as directed by CO

Clarifies liability acceptance and aligns proposal to incorporated clause expectations.

Riftur’s Impact

Riftur’s findings show that the submission is largely aligned on the core fuel delivery mission, product specifications, routine scheduling, spill response, and emergency availability, which reduces performance risk in the highest-visibility service areas. It also surfaced a small set of high-impact compliance blockers that are easy to miss in narrative form but are decisive for evaluability and day-one acceptance, including missing unloading checklist elements such as grounding/bonding, removal of ungrounded objects, and an explicit “driver does not remain in the vehicle” commitment. The review identified conditional language where the PWS is unconditional (motor/lights off and drain covering), which can be interpreted as an incomplete offer-form commitment rather than a procedural preference. It highlighted installation-specific HAZMAT controls that affect on-site eligibility and auditability, including incomplete acknowledgment of AF Form 3952 requirements and absent interim and final HAZMAT inventory reporting deliverables. It flagged security and access vulnerabilities with direct operational consequences, including partial coverage of DBIDS visit request mechanics and missing explicit adherence to the 25m/80ft vehicle standoff that can result in access denial. It also pinpointed administrative responsiveness risks tied to partial FAR/DFARS telecom representations formatting and other clause-driven acknowledgments, which can affect responsiveness screening more than narrative quality. Together, these insights clarify that risk is concentrated in prescriptive procedural steps, mandatory reporting, and access constraints, while the broader technical approach is already positioned to meet the underlying service intent.

© 2025 Riftur — All Rights Reserved