Riftur

TXARNG Medical Readiness Proposal Gap Analysis for PWS Compliance

Solicitation NameTexas Army National Guard: Mobile Medical and Dental Readiness Services
Solicitation LinkSAM.gov
IndustryNAICS 62 – Health Care and Social Assistance

This submission supports a mobile, on-site medical and dental readiness mission that depends on strict scheduling, platform capability, and timely data updates across multiple Army systems. The evaluation will turn on whether the technical volume makes clear, testable commitments that match the required services, timelines, and control environment for operating on installations. The results below distinguish areas that are fully committed versus areas where the narrative is present but missing required specificity, artifacts, or clause-driven obligations. The dominant pattern is strong operational framing and event execution language, with several high-impact omissions in post-event deliverables, required clinical elements, and security/IS compliance statements. Those gaps matter because they create evaluability problems, increase performance risk against PRS thresholds, and can trigger “does not meet requirement” findings even when the team can likely perform. The most consequential gap is the missing 24-hour by-name dental case management roster and the associated 30-day case management cap and invoicing logic. That single omission is directly tied to PRS/AQL performance and is scored as critical because it is objective, time-bound, and surveillance-driven. Related case management controls are also incomplete, including required update-on-conversion reporting and the explicit approval chain for offsite dental treatment that includes COR approval. These are not narrative polish issues; they are acceptance and payment-dispute drivers because they define what the Government can verify, when it can verify it, and when the contractor can bill. Leaving these ambiguous increases the likelihood of adverse CPARS/QASP outcomes and creates a clear basis for the Government to assess nonconformance. The next major risk concentration is the mobile platform and station capability set, where multiple required readiness elements are only partially covered or not stated. Missing explicit commitments for items like women’s health surge capability with the 60-day notice trigger, PSA/DRE requirements, DRE/Hemoccult, TITMUS screening, and a detailed CLIA-waived menu creates an inspection and scope-execution risk at the event level. Connectivity and data handling are generally described, but gaps such as barcode scanning capability, explicit ADDR uploads, and explicit live event/Soldier tracking weaken confidence that the workflow meets required throughput and real-time visibility expectations. In dental documentation, the narrative aligns to DENCLASS timeliness, yet it omits required form annotations, STR hardcopy filing practices, and the 8-exams-per-hour feedback mechanism, which can undermine auditability and readiness data integrity. These are the kinds of shortfalls that evaluators treat as “not demonstrated,” because they are tied to specific artifacts, systems, and metrics rather than general clinical competence. Finally, several clause- and policy-driven compliance areas are absent or incomplete in ways that can affect eligibility and contractual risk ratings. The technical volume does not clearly accept key Government IS requirements (AUP, ATCTS registration, annual IA training, marking and safeguarding) and does not state a DFARS 7012/NIST 800-171 safeguarding posture, even though the work inherently touches PII and potentially CDI. The privacy section is strong on controls but does not explicitly accept contractor cost liability for breach notification and credit monitoring when contractor-caused, which is a material contractual exposure. Additional omissions—OCI reporting, holiday non-performance, physical security and key control, utilities conservation, and trafficking-in-persons acknowledgment—are individually small but collectively signal incomplete conformance with non-clinical obligations that the Government can still enforce. Where the proposal is already aligned, it is strongest on mobilization timing, on-site execution constraints (no telework), core training commitments (AT Level 1, iWATCH, OPSEC), and the 4-hour malfunction recovery requirement, which lowers perceived operational risk when paired with more complete deliverable and compliance language.

Output Analysis

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.

Document Meta-Data & Methodology (for gap analysis traceability)

Iteminput_proposal.docx (Draft Document)solicitation_text.docx (Reference Criteria)Notes for Gap Analysis Use

Primary domain

Technical proposal for TXARNG medical/dental readiness IDIQ task orders

PWS + PRS + Deliverables Schedule + FAR/DFARS clauses + proposal instructions

Treat as RFP/PWS requirements-to-response mapping

Timeframe

References 60-month ordering period; event-based timelines (3 days notice; 5 days uploads)

60-month ordering period; PoP 03 Sep 2026–02 Sep 2031; multiple event deliverables with strict due dates

Verify every timeline commitment exists and matches PWS

Service model

Mobile, non-personal services; on-site only

Mobile platforms with optional armory space; telework not authorized

Look for explicit “contractor furnished” vs “GFP” understanding

Evaluation alignment

Organized by Subfactor 1 and 2; includes many PWS phrases but expanded

Requires avoid copy/paste; demonstrate staffing org chart + reliable equipment source; QC, licensing, staff experience

Proposal currently lacks explicit org chart and explicit supply chain/source narrative

Master Requirement Coverage Matrix (PWS/PRS/Deliverables vs Technical Proposal)

Req ID (Ref)Requirement (Reference Criteria)Draft Document Evidence (input_proposal.docx)Coverage StatusGap / Concern

GEN-1 (1.4.1)

Respond anywhere in Texas with minimum 3 days’ notice; perform at TE3 locations; delivery orders provide addresses

States “respond anywhere in Texas with as little as three days’ notice”; Texas-centric posture; TE3 + additional sites

Covered

Add explicit mention of receiving addresses via task order/delivery order to mirror PWS language (minor)

GEN-2 (1.4.1)

Operating hours in 3-hour blocks up to 4 consecutive blocks/day unless special arrangements

Explicitly states 3-hour blocks up to 4 consecutive blocks/day; staffing for uninterrupted performance

Covered

None

GEN-3 (1.4.1.1)

Telework not authorized

Explicitly acknowledges; commits to on-site workflows and real-time updates

Covered

None

GEN-4 (1.4.1.2)

Unscheduled gate closures; no compensation; vehicles subject to search; moving violations can terminate driving privileges

Addresses gate delays/installation access, no compensation for closures/delays

Partially Covered

Does not address vehicle searches and moving-violation consequence for driving privileges

GEN-5 (1.4.1.3)

Employees obey installation regs; carry ID; restricted areas only with approval; Govt may remove for misconduct/security/communicable disease; removal doesn’t relieve performance

States adherence to installation access/security procedures; acknowledges removal for misconduct/communicable disease risks; performance responsibility retained

Partially Covered

Does not explicitly mention restricted areas entry only with prior approval; always carry proper ID; subject to checks

GEN-6 (1.4.2)

No services on recognized US holidays

Not mentioned

Gap

Add explicit holiday non-performance approach and scheduling coordination

QC-1 (1.4.3 / TE2)

Submit final QCP NLT 10 days after award; address PRS areas; changes require KO acceptance in writing

Explicitly commits to QCP submission NLT 10 days; aligns to PRS/QASP; implies documentation

Partially Covered

Does not explicitly state KO acceptance in writing for QCP changes (only mentions COR review/approval)

QA-1 (1.4.4)

Gov will use QASP; performance standards/AQL/defect rates

Mentions alignment with Gov QA/QASP

Covered

Consider adding how contractor supports surveillance (access to logs, inspection readiness)

LIC-1 (1.4.7 / 5.1 / PRS)

All providers licensed IAW AR 40-68 para 4-8; Texas (state/jurisdiction where providing services); Govt may request verification anytime

Commits to Texas licensure verification, recurring audits, maintain records and produce upon request

Covered

Clarify how out-of-state events (if any) handled; though PWS expects Texas primarily

CM-1 (1.4.9)

Designate Contract Manager + alternate in writing to KO; full authority; works through COR; prevent out-of-scope services without KO mod

Commits to CM/alternate designated in writing to KO; works through COR; avoids out-of-scope without mod

Covered

None

ID-1 (1.4.10 / 1.4.10.1)

Contractor identification: disclose contractor status; badge with company/name/‘contractor’; mark contractor documents; retrieve ID media; return to KO within 14 days

Commits to identify as contractors, wear badges, mark documents; retrieve CACs upon departure with receipts (to TA/COR)

Partially Covered

Does not mention returning badges/vehicle passes to KO within 14 days (non-CAC ID media)

TIP-1 (1.4.11)

Combating trafficking in persons (FAR 22.17) - notify employees; take action for violations

Not mentioned in technical volume

Gap

Even if often in Volume I, adding a brief compliance statement reduces risk of ‘unaddressed requirement’ in narrative

DR-1 (1.4.13)

Government unlimited rights/data rights; products owned by Government; cannot use/sell without KO permission

States Govt holds unlimited rights; deliverables provided without restriction

Covered

Add explicit internal control preventing reuse/sale without KO permission

OCI-1 (1.4.14)

Notify KO immediately of actual/potential OCI; submit mitigation plan; KO discretion

Not mentioned

Gap

Add OCI awareness + reporting/mitigation process

GFP-1 (3.1 / 3.1.1)

Government provides parking; contractor must operate with only parking; govt space only when authorized; if using govt space contractor provides tables/chairs/privacy dividers/power/internet/computers etc.

States no dependence on govt space beyond parking; can operate self-contained; acknowledges armory/space may not be available unless told

Partially Covered

Does not explicitly commit to providing all support equipment when govt indoor space authorized/used

UTIL-1 (3.5)

Utilities available; contractor instruct employees on conservation; preclude waste

Not mentioned

Gap

Add utility conservation SOP/training snippet

IT-1 (5.1.3)

Provide in-person or help-desk IT technicians

Commits to in-person or help-desk IT technicians

Covered

None

PLAT-1 (5.2)

Mobile platforms meet OSHA/ADA/Privacy Act/HIPAA; climate control; can operate remote areas

Commits and describes fully self-contained; climate control; remote ranges

Covered

None

PLAT-2 (5.2.1)

Radiation protection; emergency eyewash; distilled water tanks; separate walled operatories; temp-controlled rooms; Safety Program IAW OSHA EAP/Means of Egress

Commits to enclosed private rooms; mentions eyewash readiness in inspections; radiation protection; sterilization separation

Partially Covered

Does not explicitly mention distilled water tanks; does not explicitly describe Safety Program elements (EAP/Means of Egress) beyond inspection checklist

PLAT-3 (5.2.2.*)

Provide required stations/services incl. DRE, Hemoccult, SCT screenings, HIV blood draws, DNA collection, TITMUS screener, specific CLIA-waived panels, urine CT/GC screen, etc.

Mentions many stations (vitals, acuity, immunizations, PPD, tonometry, EKG, PFT, audiometry, phlebotomy, CLIA-waived POC) and shipping HIV/DNA as directed

Partially Covered

Missing explicit commitments to: DRE + Hemoccult; TITMUS visual acuity screener; detailed CLIA-waived menu (lipids/BMP/CHEM12/A1C/UA/Urine HCG/CT-GC); G6PD and RPRa collection; explicit urine CT/GC

PLAT-4 (5.2.2.14)

Women’s Health exams (Pap smear, Chlamydia testing, mammograms; case manage mammography) with ≥60 days notice

Not mentioned

Gap

Must explicitly accept conditional requirement and 60-day notice readiness

PLAT-5 (5.2.2.15)

DRE and PSA testing for males >50 with ≥60 days notice

Mentions DRE as ‘screening support’ earlier? (Draft: DRE not explicitly)

Gap

Add explicit DRE/PSA capability and notice-driven plan

PLAT-6 (5.2.2.16)

Upload audiograms directly into DOEHRS repository

Commits to upload 100% audiograms to DOEHRS within 5 days

Covered

Add explicit ‘direct upload capability’ statement (already implied)

WASTE-1 (5.2.2.17 / 5.2.2.17 / 5.2.2.17, 42 CFR)

Contractor disposes medical waste IAW 42 CFR

Commits to procedures for medical waste handling/disposal IAW 42 CFR without Govt reliance

Covered

None

NET-1 (5.2.3 / 5.2.4)

Internet connectivity for real-time data entry; high-speed broadband/satellite; CAC-enabled PM/providers; barcode scanning; live event & Soldier tracking; upload images to ADDR (Active Duty Dental Repository)

Commits to broadband/satellite sized for systems; CAC-enabled clinicians; mentions SRTS; mentions real-time; does not mention barcode scanning; mentions DENCLASS but not ADDR; mentions daily end-of-day summaries but not live tracking system

Partially Covered

Gaps: barcode scanning capability; explicit ADDR upload; explicit live event/Soldier tracking system and remote tracking; explicit PM role (uses Event Manager/Contract Manager terminology)

SETUP-1 (5.2.5)

Dental equipment setup complete day prior to event; contractor responsible

Commits day-prior setup/validation

Covered

None

REMOVE-1 (5.2.6)

Remove all vendor property within 24 hours post event; emergency offsite within 5 hours notice

Commits to removal within 24 hours; 5 hours emergency departure

Covered

None

EOD-1 (5.2.7 / TE2)

End-of-day email: scheduled/checked-in/checked-out

Commits to daily end-of-day email with those counts

Covered

None

DENT-1 (5.3)

Dental exams + digital bitewings/panoramic if clinically indicated; upload all exams+radiographs to DENCLASS; panoramic on file within 5 days; film not accepted

Commits to bitewings/pano imaging; clinically indicated per FDA; ensure pano in DENCLASS when missing; upload workflow within 5 days

Partially Covered

Does not explicitly state ‘film or digitized radiographs not accepted’ (must be digital only per PWS wording)

DENT-2 (5.3.1.*)

Periodic oral eval must include caries risk, PSR, tobacco risk, oral CA screening; SF603/SF5570 annotations; hardcopy STR filing IAW AR 40-66; feedback if cannot process 8 exams/hour; DENCLASS entry within 5 days

Commits to caries risk, PSR, tobacco risk, oral CA screening; mentions FDA guidance; case management; DENCLASS within 5 days

Partially Covered

Missing: explicit SF603/SF5570 annotation; explicit 8 exams/hour throughput monitoring & immediate feedback to OSS POC; explicit STR hardcopy documentation review/file/organization + thermal printer preference

TREAT-1 (5.4)

Provide approved dental treatment only in OSHA & ADA-compliant mobile platform; goal convert 90% Class 3 to Class 1/2 (and guidance about not comprehensive to Class 1)

Commits to authorized treatment; emphasis convert Class 3 to Class 1/2; avoid elective care

Partially Covered

Does not explicitly acknowledge the limitation that comprehensive treatment to Class 1 is not authorized (TE5(b)); proposal states convert to Class 1 or 2 ‘whenever feasible’ which could be read as overreach

TREAT-2 (5.4.2)

Submit treatment plans in DENCLASS to State Dental Officer for approval prior to treatment; then to COR for approval prior to any offsite dental treatment; exceptions coordinated with State Surgeon

Commits SDO approval prior to treatment; mentions coordinate exceptions with State Surgeon

Partially Covered

Does not mention COR approval prior to any offsite dental treatment

CASE-1 (5.4.3 / PRS)

Post-event dental case mgmt not to exceed 30 days; by-name roster within 24 hours post event to OSS; by-name updates upon conversion; invoice after 30 days; network of local providers

Commits to mature post-event dental case mgmt and pre-established provider network; includes roster in End of Event Summary within 5 days

Partially Covered

Missing explicit: by-name roster to OSS within 24 hours; 30-day max; invoice trigger after 30 days; by-name updates upon conversion

RX-1 (5.5.*)

Pharmacy network; arrange Rx fulfillment; provide all prescription meds (analgesia/antibiotics) for dental treatment

Not mentioned

Gap

Add Rx services model, formulary controls, and accountability process

PHA-1 (5.6)

Conduct PHAs per NGB guidance; physicals (Flight/Airborne/Ranger/SF) per AR 40-501; required equipment; ASCVD screening >40; PHAs in MODS MHA day-of

Commits to PHAs day-of in MODS MHA; mentions physical exams generally; has stations incl. tonometry/vitals/labs; does not mention specific special physicals; does not mention ASCVD screening >40

Partially Covered

Add explicit capability for special-duty physicals and ASCVD screening requirement

VISION-1 (5.6.1.*)

Vision screening Snellen + near/far, refraction, PD; OD completes DD771; SRTS/NOSTRA ordering 5 eyewear types; validate/sort/ship within 7 days of receipt; scan DD771 to HRR within 7 days; hard copies to Med Det within 5 days; MEDPROS within 5 days; assign Vision Readiness Classification

Commits OD support, DD771 completion, SRTS/NOSTRA ordering; mentions HRR scanning and STR hard copies generally; but not these timelines and eyewear specifics

Partially Covered

Missing explicit: 5 eyewear types; 7-day ship to unit rep after NOSTRA receipt; ‘current accepted tracking shipping method’; HRR scan/index within 7 days; hard copy DD771 to Med Det within 5 days; Vision readiness classification update in MEDPROS within 5 days

AUD-1 (5.6.2 / TE2)

Audiologist on site; MOHT testing; DOEHRS entry 100% within 5 days; noise-controlled environment; if MOHT required and cannot be on-site case manage within 30 days

Commits DOEHRS-compatible equipment; upload 100% within 5 days; noise-limiting environment; states “requirement to have an audiologist on site”

Partially Covered

Does not explicitly address MOHT case management within 30 days if cannot be done on-site

LAB-1 (5.6.3)

CLIA-waived labs on-site; ship HIV/DNA to approved DA testing facility; TXARNG provides supplies/labels for HIV/DNA; contractor uses accepted shipping method; notify COR immediately on abnormal values; scan/index HRR; hard copies to Med Det within 7 days of draw; update MEDPROS within 5 days of results

Commits CLIA-waived on-site; HIV/DNA shipping with Med Det supplies/labels; immediate abnormal notification; HRR scan/index; hard copies to Med Det; MEDPROS update within 5 days of receipt

Partially Covered

Does not explicitly state ship to approved DA testing facility; does not explicitly state hard copies within 7 days of draw (draft says ‘within required timelines’)

SCT-1 (5.6.4 / TE2)

Verify SCT annotation in MEDPROS/EMR within 5 days post event; issue red warning tag upon positive results IAW AR 40-66

Commits to verify within 5 days; coordinate issuance of red warning tag per AR 40-66

Covered

None

PM-1 (5.7 / TE2)

Provide Event Manager contact info NLT 5 days prior; Event Managers possess CAC; trained in MEDPROS, E-PHA, E-Profile, DENCLASS and HIPAA (certs when applicable)

Commits provide contact info within 5 days of each event (but states within 5 days of each event; ambiguity pre/post); Event Managers with CAC and system familiarity

Partially Covered

Must explicitly state ‘no later than 5 days prior to the event’ and enumerate required training areas + certificates when applicable

MALF-1 (5.8 / PRS)

Malfunction plan; operational within 4 hours inclusive of troubleshoot/remove/replace

Commits formal malfunction response plan; operational within 4 hours; redundancy and escalation

Covered

None

EOE-1 (5.9 / TE2)

End of Event Summary within 5 days post event; include all listed metrics and by-name rosters (examined; dental case mgmt; BH case mgmt; medical case mgmt)

Commits End of Event Summary within 5 days with essentially all enumerated items + by-name rosters listed

Covered

Ensure report is ‘approved and verified by TXARNG liaison’ (not stated)

PII-1 (1.4.5.10)

Protect PII per DFARS 224.103/DoDD 5400.11/DoD 5400.11-R; if breach due to contractor violation, contractor bears notification/call-center/credit monitoring costs

Commits to protect PII; RBAC, encryption, secure transmission, retention/disposition; cites DFARS 224.103 and DoD privacy refs

Partially Covered

Does not explicitly accept cost liability for breach notifications/credit monitoring if due to contractor violation

IS-1 (1.4.5.6.* / 1.4.5.7 / 1.4.5.8)

Government IS use: sign AUP; IA training initial/annual; ATCTS registration; DoD IA awareness before access and annually; file marking/safeguarding; safe network principles

Mentions role-based access, encryption, secure transmission; but not AUP/ATCTS/annual IA training specifics

Gap

Need explicit compliance narrative for AUP signing, ATCTS registration, IA awareness training cadence, file marking/safeguarding practices

CAC-1 (1.4.5.1.* / TE2)

HSPD-12 PSIP within 5 business days; TASS process; RAPIDS identity docs; CAC renewal notice 10 days; return CAC with receipts; AKO email requirement

Commits to PSIP within 5 business days; manages e-QIP/fingerprints/RAPIDS; renewals with advance notice; return CAC with receipts; mentions lead times

Partially Covered

Does not mention: TASS specifically; RAPIDS I-9 identity document list; CAC validity up to 3 years; AKO email requirement

AT-1 (1.4.5.3 / TE2)

AT Level 1 within 30 days; submit certs within 15 days

Commits to AT Level 1 within 30 days; submit certs within 15 days

Covered

None

IWATCH-1 (1.4.5.4 / TE2)

iWATCH brief within 30 days of award and for new employees; report results NLT 30 days after award

Commits iWATCH within 30 days; reporting completion timelines

Covered

None

OPSEC-1 (1.4.5.11 / TE2)

Level I OPSEC within 30 days and annually; submit certs within 15 days

Commits Level I OPSEC within 30 days and annually; submit certs within 15 days

Covered

None

PHYSSEC-1 (1.4.6)

Safeguard Government property; secure at close of work period

Not mentioned

Gap

Add procedures for securing Govt facilities/equipment/materials when used

KEY-1 (1.4.6.1-1.4.6.2)

Key/key card control; no duplication; report lost keys; re-key cost deductions; lock combination control; include in QCP

Not mentioned

Gap

Even if rarely used, must include in QCP and describe basic method

MEET-1 (1.4.8)

Attend post-award & periodic progress meetings at no additional cost

Not mentioned

Gap

Add commitment to attend meetings and provide agenda/minutes support if desired

SCR-1 (Ordering Procedures)

Service Contract Reporting (SAM.gov) contractor labor hours annually by Oct 31 for TOs >= $3M

Not mentioned

Gap

Add compliance statement (even if in Volume I/management) because it is performance-affecting

SCLS-1 (Ordering Procedures)

Service Contract Labor Standards apply at TO level; comply with WD locations

Not mentioned

Gap

Add high-level compliance acknowledgment (coordination with HR/payroll)

CYBER-1 (DFARS 252.204-7012/7018/7020 etc.)

Safeguarding Covered Defense Information; cyber incident reporting; NIST SP 800-171 assessment requirements; covered telecom prohibitions

Not mentioned

Gap

If any CDI/controlled unclassified info handled, include a concise compliance posture and incident reporting workflow

Deliverables & Timeliness Compliance Map (Technical Exhibit 2 vs Proposal Commitments)

Deliverable (TE2)Due / Frequency (Reference Criteria)Draft Document EvidenceStatusSpecific Gap to Close

Quality Control Plan (1.4.3)

NLT 10 days after award

Explicit commitment NLT 10 days

Covered

Add KO written acceptance for changes

AT Level 1 Certificates (1.4.5.3)

To COR within 15 days after completion

Explicit commitment

Covered

None

iWATCH Training (1.4.5.4)

NLT 30 days after award / new employee; report results

Explicit commitment

Covered

Clarify reporting method and artifact (roster/certs)

Background Investigation PSIP (1.4.5.1)

NLT 5 days after onboarding

Explicit commitment

Covered

Add tracking dashboard and escalation controls (recommended)

OPSEC Certificates (1.4.5.11)

To COR within 15 days after completion

Explicit commitment

Covered

None

End-of-Day Summary (5.2.7)

End of each event day

Explicit commitment

Covered

None

DENCLASS Upload (5.3.1.9)

5 days post event

Explicit commitment (within 5 days; QC check)

Covered

Add metric aligned to PRS ‘no more than 3 late instances per event’

DOEHRS Input 100% (5.6.2)

5 days post event

Explicit commitment 100% within 5 days

Covered

Include MOHT handling

Lab results to OSS & MEDPROS updates (TE2 lists 5.6.4 but content is 5.6.3)

Copy to OSS within 7 days of draw; MEDPROS update within 5 days of receipt

Commits scanning/indexing; hard copies to Med Det; MEDPROS within 5 days

Partially Covered

Add explicit ‘copy of results to OSS within 7 days of draw’

SCT verification (5.6.4)

Verify annotation within 5 days post event (effectively immediately)

Explicit commitment

Covered

None

Positive SCT red tag (TE2 lists 5.6.4.2)

Upon notification of positive result

Explicit commitment

Covered

None

Event Manager contact info (5.7)

5 days prior to event

States within five days of each event (ambiguous)

Partially Covered

Change to explicit ‘NLT 5 days prior to the event’

Event Summary (5.9)

5 days post event

Explicit commitment within 5 days post event, with required contents

Covered

Add ‘approved/verified by TXARNG liaison’ acknowledgment

PRS / AQL-Driven Control Mapping (Technical Exhibit 1 vs Proposal QC Assertions)

PRS ObjectivePerformance Standard / AQL (Reference Criteria)Draft Document QC/Process EvidenceStatusResidual Risk

Licensure requirement (1.4.7/5.1/5.4.1)

100% compliance; 100% inspection

Pre-deployment credential verification + recurring audits; records available immediately

Covered

Low—add named tool/source (state board lookups), cadence, and audit logs

Mobile platform compliance (5.2-5.2.6)

100% compliance; 100% inspection

Pre-event inspections (OSHA/HIPAA/Privacy Act/ADA/radiological) with documented checks (eyewash, ventilation, etc.)

Partially Covered

Medium—missing explicit Safety Program/EAP/Means of Egress and some platform specifics (distilled water tanks, walkthrough widths, barcode scanning)

DENCLASS entry within 5 days (5.3.1.7/5.3.1.9)

No more than 3 late instances/event

Daily event-close verification + post-event workflow within 5 days; goal zero late

Partially Covered

Medium—proposal does not explicitly tie to ‘≤3 late instances’ threshold; add QC metric and corrective action triggers

Post-event dental case mgmt roster within 24 hrs (5.4.3.1)

No more than 1 late roster instance per PoP

End of Event report within 5 days includes by-name roster; case mgmt capability described

Gap

High—24-hour roster deliverable is absent; significant risk to PRS compliance

Equipment malfunction plan (5.8)

Operational within 4 hours, 100%

Redundancy, rapid dispatch, escalation; pre-event functional tests/calibration

Covered

Low—add measurement/logging method for ‘start time’ and ‘operational restored’ timestamps

Key Gaps & Overlaps (Thematic)

ThemeOverlaps / Strengths in input_proposal.docxGaps vs solicitation_text.docxRisk if Unaddressed

Mobilization & on-site operations

3-day notice; statewide; no telework; block scheduling; surge roster; self-contained platforms

Holiday non-performance not stated; vehicle search/moving violation policy not addressed

Moderate—operational scheduling and compliance misunderstandings

Mobile platform technical compliance

Private rooms (no open bay), climate control, stations listed, broadband/satellite connectivity

Missing explicit required items (TITMUS, DRE/Hemoccult, detailed CLIA menu, barcode scanning, distilled water tanks, ADDR uploads, walkway widths)

High—inspection failures; ‘does not meet requirements’ risk

Dental screening & data

Caries/PSR/tobacco/oral CA; FDA clinically indicated; pano presence in DENCLASS; 5-day upload QC

Missing SF603/SF5570 annotation; 8 exams/hour feedback requirement; STR filing & thermal printer preference

Moderate—process noncompliance and readiness data integrity

Dental treatment & case mgmt

Treatment plan approval in DENCLASS; fixed-site network for residual care; focus on readiness conversion

Missing COR approval for offsite; missing 24-hour by-name roster; missing 30-day cap and invoicing trigger; Rx meds requirement absent

High—PRS noncompliance and payment/invoicing disputes

Medical PHA/physicals/clinical requirements

MODS MHA day-of; on-site CLIA; abnormal lab notification; DOEHRS uploads

Missing ASCVD screening >40; special duty physicals; women’s health & PSA/DRE conditional requirements

Moderate—scope shortfalls at TO execution

Security/Privacy/IS

PII controls (RBAC/encryption/secure transmission/retention); CAC/AT/iWATCH/OPSEC described

Missing explicit breach cost responsibility; missing AUP/ATCTS/annual IA training; missing DFARS 7012/NIST posture

High—contractual and cyber compliance exposure

Government property & physical security

Acknowledges limited govt space; removal timelines; no compensation for delays

Missing utilities conservation; physical security closing procedures; key control/lock combination controls

Low–Moderate—QCP deficiency; deductions if keys lost

Risk Register (Acquisition/Compliance/Operational)

Risk IDRisk DescriptionRoot Cause (Gap)LikelihoodImpactOverall RiskRecommended Mitigation (No timelines)

R-01

Failure to meet PRS requirement for 24-hour post-event dental case management roster

Proposal omits explicit 24-hour by-name roster commitment and workflow

High

High

Critical

Add explicit roster deliverable, ownership, template, and transmission method to OSS within 24 hours; add QC check and escalation

R-02

Platform inspection failure or inability to perform required medical readiness elements

Several platform-required items not explicitly committed (TITMUS, DRE/Hemoccult, detailed lab panels, barcode scanning, distilled water tanks, walkway widths)

Medium

High

High

Add a compliance matrix listing each PWS 5.2.2.x capability with equipment models and how provided per platform; include inspection checklist artifacts

R-03

Noncompliance with DFARS 252.204-7012 / NIST 800-171 expectations for safeguarding

Technical proposal lacks explicit cybersecurity/CDI handling controls and incident reporting process

Medium

High

High

Add a concise CDI handling posture, system boundary, encryption, MFA, incident reporting steps/points of contact, and NIST assessment status for contractor systems used

R-04

Vision services noncompliance leading to readiness delays (eyewear ordering/HRR/STR deadlines)

Missing explicit 5-eyewear-type ordering, shipping within 7 days of receipt, HRR/STR deliverable timelines, MEDPROS vision classification updates

Medium

Medium

Medium

Add step-by-step vision workflow with deliverable dates, tracking method, and reconciliation of NOSTRA/SRTS orders to unit delivery

R-05

Dental documentation noncompliance (SF603/SF5570, STR hardcopy filing)

Proposal focuses on DENCLASS but does not cite required forms and STR filing requirements/thermal printing preference

Medium

Medium

Medium

Add documentation section: forms used, scanning/indexing steps, hardcopy handling, printer capability, and AR 40-66 conformance

R-06

Breach cost liability misunderstanding

Proposal mentions PII controls but not contractor-paid notification/call center/credit monitoring costs when breach is contractor-caused

Low

High

Medium

Add explicit acknowledgment of PWS 1.4.5.10 cost responsibility and breach response plan summary

R-07

Offsite dental treatment approval chain not fully complied with

Proposal mentions SDO approval but not COR approval prior to offsite treatment

Medium

Medium

Medium

Add explicit approval chain and decision gates in workflow; include exception coordination with State Surgeon

R-08

Failure to provide prescription medications for dental treatment

Rx network and medication provision requirement not addressed

Medium

High

High

Add pharmacy network plan, medication provisioning controls (storage, dispensing, prescribing authority), and documentation/consent process

R-09

Noncompliance with Government IS requirements (AUP, ATCTS, IA annual training)

Proposal includes AT/iWATCH/OPSEC but omits AUP signing and ATCTS/IA annual training specifics

Medium

Medium

Medium

Add IS access compliance subsection with artifacts to be maintained and provided to COR

R-10

Women’s health and PSA/DRE surge requirement not executable on notice

Conditional requirements with 60-day notice not addressed

Medium

Medium

Medium

Add contingency capability statement (staffing, privacy, equipment, referral/case management) triggered by COR notice

Recommendations to Enhance Alignment (Actionable, requirement-linked)

PriorityRecommendationReference Criteria LinkWhat to Add/Change in input_proposal.docx

High

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

PWS 5.4.3.1; PRS TE1; TE2 deliverables

Insert a dedicated ‘Post-Event Dental Case Management’ subsection with deliverables, recipients (OSS), method (secure email/SFTP), QC checks, and escalation

High

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)

PWS 5.2.2.1–5.2.2.35

Add a table plus narrative listing equipment models (or equivalent), quantities per platform, and how throughput is maintained

High

Explicitly address prescription medication requirements: pharmacy network, provision of analgesics/antibiotics, patient instruction, and documentation

PWS 5.5.1–5.5.4

Add an ‘Rx Services’ workflow including coordination with dentists, pharmacy fulfillment, and tracking

High

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

Contract clauses; DFARS 252.204-7012; 252.204-7020/7019

Add a concise cybersecurity subsection: system boundary, encryption, access control, incident reporting, and assessment status

Medium

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

PWS 5.7; TE2

Edit management section to remove ambiguity (‘within five days of each event’) and replace with the exact pre-event requirement

Medium

Add vision services compliance details: eyewear types, shipping SLA after NOSTRA receipt, HRR/STR timelines, MEDPROS vision readiness classification update

PWS 5.6.1.3–5.6.1.5

Add step-by-step workflow and reconciliation logs

Medium

Add explicit acknowledgment and approach for 8 dental exams/hour throughput monitoring and immediate OSS POC notification when risk arises

PWS 5.3.1.8

Add throughput KPI, dashboard/spot report triggers, and communication protocol

Medium

Add Government IS compliance statements: AUP signing, ATCTS registration, IA awareness training annual cadence, marking/safeguarding

PWS 1.4.5.6.1–1.4.5.8

Add a short ‘Gov IS Use’ subsection with artifacts maintained

Medium

Address conditional Women’s Health and PSA/DRE requirements with 60-day notice trigger plan

PWS 5.2.2.14–5.2.2.15

Add contingency staffing/equipment/case management statement

Low

Add physical security, key/lock combo control, utilities conservation, holidays non-performance, meetings attendance, OCI reporting/mitigation

PWS 1.4.2; 1.4.6; 1.4.6.1-1.4.6.2; 3.5; 1.4.8; 1.4.14

Add brief compliance acknowledgments and embed relevant procedures into QCP description

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