Additional Use Cases
Executive Summary
This gap analysis maps the Performance Work Statement and solicitation instructions in solicitation_text.docx (Reference Criteria) to the narrative commitments in input_proposal.docx (Draft Document) for Volume II Technical (Mission Capability and Management Capability). Requirements were decomposed into discrete, testable obligations (e.g., timelines, system updates, deliverables, staffing credentials, platform specifications, security/privacy controls, and reporting). Each requirement was evaluated for evidence of explicit compliance, partial coverage (mentioned but missing required specificity such as timelines, artifacts, metrics, tools, or named standards), or a gap (not addressed / contradicts / ambiguous). Risks were assessed using typical federal acquisition/QASP constructs: performance risk to PRS AQLs, compliance risk (privacy, security, licensure), operational risk (equipment downtime, mobilization, throughput), and contractual risk (data rights, OCI, out-of-scope). Recommendations focus on strengthening traceability to PWS paragraphs/TEs, adding measurable methods (SOPs, checklists, logs), and explicitly addressing solicitation-specific deliverables and clause-driven obligations that are not inherently “technical operations” but can affect acceptability and risk ratings. Packaging-only issues (fonts/page counts) were excluded per instruction.
Score Breakdown
Net Score
63%
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
65%
7% recoverable
Estimated from 5 status signals across 2 published requirements tables.
Compliance
63%
5.5% recoverable
No dedicated published table was available, so the overall findings estimate is used.
Evaluation Readiness
63%
5.5% recoverable
No dedicated published table was available, so the overall findings estimate is used.
Requirement Coverage
5
reqs
Covered: 40% (2)
Partially Covered: 40% (2)
Missing: 20% (1)
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
1
3
1
Medium
0
5
0
Low
0
0
0
What Would Improve My Score
Add explicit compliance with 5.4.3.1 PRS deliverable: by-name roster of Soldiers needing post-event dental case management within 24 hours; include update-on-conversion and 30-day cap/invoicing logic
+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, requirement-linked)
Finding
Add explicit compliance with 5.4.3.1 PRS deliverable: by-name roster of Soldiers needing post-event dental case management within 24 hours; include update-on-conversion and 30-day cap/invoicing logic
Completion Standard
Update the proposal so this recommendation is directly evidenced: Add explicit compliance with 5.4.3.1 PRS deliverable: by-name roster of Soldiers needing post-event dental case management within 24 hours; include update-on-conversion and 30-day cap/invoicing logic
Create a PWS 5.2.2 capability crosswalk table confirming each required station/equipment/service (TITMUS, DRE/Hemoccult, SCT/HIV/DNA/G6PD/RPRa collection, CT/GC screen, detailed CLIA panels) and where delivered (medical vs dental platform)
+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, requirement-linked)
Finding
Create a PWS 5.2.2 capability crosswalk table confirming each required station/equipment/service (TITMUS, DRE/Hemoccult, SCT/HIV/DNA/G6PD/RPRa collection, CT/GC screen, detailed CLIA panels) and where delivered (medical vs dental platform)
Completion Standard
Update the proposal so this recommendation is directly evidenced: Create a PWS 5.2.2 capability crosswalk table confirming each required station/equipment/service (TITMUS, DRE/Hemoccult, SCT/HIV/DNA/G6PD/RPRa collection, CT/GC screen, detailed CLIA panels) and where delivered (medical vs dental platform)
Explicitly address prescription medication requirements: pharmacy network, provision of analgesics/antibiotics, patient instruction, and documentation
+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, requirement-linked)
Finding
Explicitly address prescription medication requirements: pharmacy network, provision of analgesics/antibiotics, patient instruction, and documentation
Completion Standard
Update the proposal so this recommendation is directly evidenced: Explicitly address prescription medication requirements: pharmacy network, provision of analgesics/antibiotics, patient instruction, and documentation
Add DFARS 252.204-7012 / NIST 800-171 / cyber incident reporting posture for any contractor systems used for PII/CDI handling and connectivity at events
+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, requirement-linked)
Finding
Add DFARS 252.204-7012 / NIST 800-171 / cyber incident reporting posture for any contractor systems used for PII/CDI handling and connectivity at events
Completion Standard
Update the proposal so this recommendation is directly evidenced: Add DFARS 252.204-7012 / NIST 800-171 / cyber incident reporting posture for any contractor systems used for PII/CDI handling and connectivity at events
Tighten Event Manager requirements: state ‘contact info NLT 5 days prior’ and list required systems training (MEDPROS, E-PHA, E-Profile, DENCLASS, HIPAA) with cert handling
+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, requirement-linked)
Finding
Tighten Event Manager requirements: state ‘contact info NLT 5 days prior’ and list required systems training (MEDPROS, E-PHA, E-Profile, DENCLASS, HIPAA) with cert handling
Completion Standard
Update the proposal so this recommendation is directly evidenced: Tighten Event Manager requirements: state ‘contact info NLT 5 days prior’ and list required systems training (MEDPROS, E-PHA, E-Profile, DENCLASS, HIPAA) with cert handling
Requirements
65%
Details
Estimated from 5 status signals across 2 published requirements tables.
Compliance
63%
Details
No dedicated published table was available, so the overall findings estimate is used.
Evaluation Readiness
63%
Details
No dedicated published table was available, so the overall findings estimate is used.
Strategy
63%
Details
No dedicated published table was available, so the overall findings estimate is used.
Evidence
63%
Details
Estimated from 0 status signals across 1 published evidence table.
Management
63%
Details
No dedicated published table was available, so the overall findings estimate is used.
Past Performance
63%
Details
No dedicated published table was available, so the overall findings estimate is used.
Risk
51%
Details
Estimated from 20 status signals across 1 published risk table.
Production
67%
Details
Estimated from 67 status signals across 2 published production tables.
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
Requirements
Authoritative requirement inventory and taxonomy.
Document Meta-Data & Methodology (for gap analysis traceability)
PRS / AQL-Driven Control Mapping (Technical Exhibit 1 vs Proposal QC Assertions)
Evidence
Proof support, claim strength, and technical credibility.
Key Gaps & Overlaps (Thematic)
Risk
Risk register findings, assumptions, exceptions, and deviations.
Risk Register (Acquisition/Compliance/Operational)
Production
Final package readiness, attachments, and production cleanup.
Master Requirement Coverage Matrix (PWS/PRS/Deliverables vs Technical Proposal)
Deliverables & Timeliness Compliance Map (Technical Exhibit 2 vs Proposal Commitments)
Recovery
Prioritized fixes, clarification candidates, and recovery actions.
Recommendations to Enhance Alignment (Actionable, requirement-linked)
Riftur’s Impact
Riftur revealed that the highest-leverage weaknesses in this submission are not general approach statements, but missing or incomplete commitments that the Government can objectively check and enforce. It surfaced an evaluability blocker in post-event dental case management: the absent 24-hour by-name roster deliverable, plus missing 30-day cap and invoice trigger language that directly ties to PRS/AQL surveillance and payment legitimacy. It also flagged partial coverage of mandatory clinical and platform elements, including women’s health and PSA/DRE conditional requirements, missing explicit DRE/Hemoccult and TITMUS capabilities, and an incomplete CLIA-waived testing menu that can drive inspection failure determinations. On the compliance side, it identified absent clause-driven acknowledgments and controls, including Government IS artifacts (AUP, ATCTS, annual IA training, file marking/safeguarding) and a missing DFARS 252.204-7012/NIST 800-171 safeguarding posture that affects eligibility and audit defensibility when handling PII/CDI. It further highlighted privacy risk where breach cost responsibility is not explicitly accepted, creating contractual ambiguity that can raise risk ratings even if technical controls are described. These findings matter more than narrative refinements because they affect whether the offer is deemed to meet requirements, whether performance can be verified under the QASP, and whether the submission is auditable and contractually acceptable, while also showing that mobilization, core timeliness items (e.g., DOEHRS/DENCLASS uploads), and malfunction recovery are already comparatively well-aligned.
© 2025 Riftur — All Rights Reserved