LOGCAP VI HTRO Matrix.xlsx

Instructions & Scoring Guide

All experience submitted for evaluation must have been performed by the Offeror acting as a Prime Contractor (or as a formal Joint Venture entity). Subcontractor experience will not be evaluated for this iteration of the matrix.

Submitted work samples must be from Federal Government contracts or task orders. Commercial or non-governmental projects will not be evaluated.

tc={043A2E82-5B23-4296-8222-490A00D91959}: [Threaded comment]

Your version of Excel allows you to read this threaded comment; however, any edits to it will get removed if the file is opened in a newer version of Excel. Learn more: https://go.microsoft.com/fwlink/?linkid=870924

Comment:

Pending: All experience submitted for evaluation must have been performed by the Offeror acting as a Prime Contractor (or as a formal Joint Venture entity). Subcontractor experience will not be evaluated for this iteration of the matrix.

EVALUATION STRUCTURE AND COCOM SCORING To accurately capture an Offeror's true global depth and operational footprint, this HTRO Matrix evaluates demonstrated capability independently across six (6) distinct Geographic Combatant Commands (GCCs): AFRICOM, CENTCOM, EUCOM, PACOM, NORTHCOM, and SOUTHCOM.

For each sub-factor, the Offeror shall independently score their demonstrated Prime Contractor experience for each specific GCC in which that capability was executed. The Matrix will apply the designated Weight Factor to each GCC score to generate the Total Sub-Factor Score. Offerors must provide specific, verifiable evidence (Work Samples) that correspond to the exact GCC column where points are claimed.

ELIGIBILITY GATES (Pass/Fail) Two pass/fail gates must be cleared before technical scoring begins:

Gate 1: Adequate Accounting System — DCAA-approved or equivalent; cost segregation at task order level; audit-ready for cost-type contracts.

Gate 2: Financial Capacity — Demonstrated liquidity to sustain $8M/day ($240M/month) in expenditures.

Failure on either gate eliminates the offeror from further evaluation regardless of technical score.

STEP 1 — BASE EXPERIENCE SCORE For each sub-factor, the offeror selects the tier (1000 / 800 / 600 / 400 / 200) that best describes their highest demonstrated experience anywhere in the world on a relevant prior contract. This is the Base Experience Score.

Compound Metrics Rule: Where a scoring tier contains multiple quantitative metrics separated by a semi-colon, the criteria are evaluated as "AND" conditions unless explicitly stated otherwise. The Offeror’s cited Work Sample must meet or exceed all listed quantitative metrics within that tier to claim the corresponding Base Experience Score.

STEP 2 — WEIGHTED SCORE The Weighted Score for each sub-factor is: Offeror Criteria Total Score × Weight Factor.

The Weight Factor reflects the relative operational importance of the sub-factor to LOGCAP VI experience. Higher weight factors are assigned to sub-factors with direct LSCO mission impact.

Pending: All experience submitted for evaluation must have been performed by the Offeror acting as a Prime Contractor (or as a formal Joint Venture entity). Subcontractor experience will not be evaluated for this iteration of the matrix.

HTRO Self-Scoring Matrix

Score (Offeror) CENTCOM Perf Score (Offeror) AFRICOM Perf Score (Offeror) NORTHCOM Perf Score (Offeror) PACOM Perf Score (Offeror) SOUTHCOM Perf Score (Offeror)

EUCOM

Offeror Criteria Total

Validated

Weighted

800: Established and operated a centralized corporate PMO simultaneously managing 2+ Federal prime contracts/task orders across a 2+ GCC portfolio, directing 3+ simultaneous sites.

600: Established and operated a centralized corporate PMO managing 1+ Federal prime OCONUS contract/task order, directing 2+ simultaneous sites.

400: Established and operated a corporate PMO managing 1+ Federal prime contract/task order at a single site, or strictly within CONUS.

800: 2,500–4,999 personnel across 2+ GCCs simultaneously in contingency.

600: 1,000–2,499 personnel across 2 GCCs simultaneously.

400: 100+ personnel in 1 GCC (contingency environment).

800: 20–29 labor vendors (2,500–3,499 personnel); 75+ equipment vendors; partial SCRM documentation.

600: 10–19 labor vendors (1,500–2,499 personnel); 50+ equipment vendors.

400: 1–9 labor vendors (500–1,499 personnel); 25+ equipment vendors.

800: Surge mobilization achieved at 3–4 sites within 72-hour timelines. Executed RSOI utilizing at least 1 alternate POD during simulated or actual primary node disruption.

600: Surge mobilization achieved at 2 sites within defined timelines. Mobilization playbooks include documented alternate RSOI routes for primary node denial (executed surge, planned denial).

400: Surge mobilization achieved at 1 site within defined timelines. Standard permissive environment execution.

800: Established and operated LSAs supporting 5,000–9,999 PAX across 3–4 simultaneous sites. Demonstrated site activation with IOC within 21 days of NTP and FOC within 45 days.

600: Established and operated LSAs supporting 1,000–4,999 PAX across 2+ simultaneous sites. IOC within 30 days of NTP and FOC within 60 days.

400: Established and operated an LSA supporting 250–999 PAX at 1+ site. FOC within 90 days of NTP.

800: 2 qualifying exercises; playbooks address at least one peer-threat RSOI disruption scenario; digital twin capability demonstrated.

600: 1 qualifying exercise with documented contractor participation; formal Contested Logistics Plan or Annex accepted by the USG.

400: No exercise validation. Submitted a formal Contested Logistics Plan or Annex as a required CDRL deliverable on a USG contract; document was accepted by the USG without requiring resubmission for technical deficiency.

800: Executed theater clearance operations in at least one non-SOFA country during a surge or exercise; maintained legal-status tracking and customs contingency plans.

600: Executed routine theater clearance operations in mature SOFA environments; documented contingency plans for non-SOFA access exist but lack exercise validation.

400: Documented country-clearance and legal-status management plan exists; no execution under surge or contested conditions.

800: 5,000–9,999 PAX; 24+ months; 95%+ uptime; 3–4 plans; some distributed generation experience.

600: 1,000–4,999 PAX; 12+ months; 92%+ uptime; 1–2 plans.

400: 250–999 PAX; 9+ months; 90%+ uptime.

800: 20+ horizontal; 20+ vertical; combined >$75M.

600: 15+ horizontal; 15+ vertical; combined >$50M.

400: 10+ horizontal; 10+ vertical; combined >$25M.

800: 4+ FP (750+ PAX); 4+ BEAR (750+ PAX).

600: 3+ FP (500+ PAX); 3+ BEAR (500+ PAX).

400: 2+ FP (250+ PAX); 2+ BEAR (250+ PAX).

800: Executed 3 project types (15,000+ linear ft; 75+ structures). Demonstrated hardening or dispersal execution under simulated or actual threat conditions.

600: Executed 2 project types (10,000+ linear ft; 50+ structures). Force protection designs included contingency plans for air/missile threats.

400: Executed 1 project type (7,500+ linear ft; 30+ structures). Standard perimeter security focus.

tc={A1C0F6DB-E112-4C30-A3DD-0130C07F04D7}: [Threaded comment]

Your version of Excel allows you to read this threaded comment; however, any edits to it will get removed if the file is opened in a newer version of Excel. Learn more: https://go.microsoft.com/fwlink/?linkid=870924

Comment:

Same comment as above for bucket 2 3 3.1 Shelter & Billeting / Occupancy Management 1000: 10,000+ PAX managed; 15+ simultaneous sites; includes demonstrated expeditionary/dispersed billeting at 3+ non-contiguous sites.

800: 5,000–9,999 PAX; 10–15 sites.

600: 1,000–4,999 PAX; 5–10 sites.

400: 250–999 PAX; 2–5 sites.

800: 10–24.9 MW; 10–15 critical facilities; 10–15 microgrids; some distributed generation.

600: 1–9.9 MW; 5–9 critical facilities; 5–9 microgrids.

400: 250 kW–999 kW; 2–4 critical facilities; 1–5 microgrids.

800: 250,000–999,999 GPD; 50,000–249,999 GPD ROWPU.

600: 50,000–249,999 GPD (ROWPU operations primary).

400: 5,000–49,999 GPD (field operations).

800: 15,000–29,999 meals/day; 10–15 DFACs.

600: 5,000–14,999 meals/day; 5–9 DFACs.

400: 1,000–4,999 meals/day; 2–4 DFACs.

800: 50,000–79,999 tons/month.

600: 25,000–49,999 tons/month.

400: 1,000–24,999 tons/month; comprehensive services.

800: 5–6 classes; 1,000,000–9,999,999 lines; 40–49 personnel.

600: 3–4 classes; 500,000–999,999 lines; 30–39 personnel.

400: 1–2 classes; 10,000–499,999 lines; 20–29 personnel.

800: 4 classes at stated standards.

600: 3 classes at stated standards.

400: 2 classes at stated standards.

800: 75,000–99,999 line items or $750M–$999M.

600: 50,000–74,999 line items or $500M–$749M.

400: 25,000–49,999 line items or $250M–$499M.

800: 1,000,000–4,999,999 GPM. Demonstrated dispersed fuel point operations with activation of at least one alternate fuel source or delivery method during a disruption.

600: 500,000–999,999 GPM. Maintained contingency plans for resupply interdiction; execution limited to standard distribution.

400: 25,000–499,999 GPM. Standard permissive fuel operations.

800: Operated ASP and AHA processing 2,000–4,999 lines/month; SAAS proficient (30–49 qualified operators). Demonstrated ammunition operations during a surge event or elevated threat posture.

600: Operated ASP processing 500–1,999 lines/month; SAAS proficient (10–29 qualified operators). Maintained SAAS and AR 190-11 physical security compliance under standard conditions.

400: ASP support role; SAAS access demonstrated; <500 lines/month.

800: 18,000–34,999 pieces; 2,000–4,999 fault repairs; some forward/austere maintenance documented.

600: 4,000–17,999 pieces; 400–1,999 fault repairs.

400: 1,000–3,999 pieces; 100–399 fault repairs.

800: 95%+ PMCS compliance; tele-maintenance capability demonstrated; additive manufacturing roadmap in place.

600: 95%+ PMCS compliance; one of tele-maintenance or additive manufacturing demonstrated.

400: 95%+ PMCS compliance; neither tele-maintenance nor additive manufacturing demonstrated.

800: 10,000–19,999 orders; 5,000–12,999 facilities; 5,000,000–19,999,999 sq ft.

600: 2,000–9,999 orders; 1,000–4,999 facilities; 1,000,000–4,999,999 sq ft.

400: 200–1,999 orders; 100–999 facilities; 200,000–999,999 sq ft.

800: 5,000–7,499 requests/month; 1,000–1,999 TMP vehicles; 2,000–3,999 clearances/month. Demonstrated alternate modal transportation or re-routing due to simulated or actual primary route/POD disruption.

600: 2,500–4,999 requests/month; 500–999 TMP vehicles; 500–1,999 clearances/month. Maintained contingency routing plans; standard permissive conditions.

400: 100–2,499 requests/month; 100–499 TMP vehicles; 20–499 clearances/month. Standard permissive movement control.

200: <100 requests/month; <100 TMP vehicles; <20 clearances/month. Standard permissive movement control.

tc={AED96F72-B902-4D48-9050-AA5AA7520176}: [Threaded comment]

Your version of Excel allows you to read this threaded comment; however, any edits to it will get removed if the file is opened in a newer version of Excel. Learn more: https://go.microsoft.com/fwlink/?linkid=870924

Comment:

800: 15,000–24,999 pieces; 3,500–7,499 truck movements; 1,500–2,499 containers.

600: 5,000–14,999 pieces; 1,000–3,499 movements; 500–1,499 containers.

400: 500–4,999 pieces; 50–999 movements; 50–499 containers.

800: Demonstrated credentialing, privileging, and clinical governance of 50–99 healthcare providers across 3–4 medical facilities during a surge, contingency, or mass-mobilization event.

600: Demonstrated credentialing and clinical governance of 25–49 healthcare providers during a surge event; OR steady-state credentialing and clinical governance for 100+ healthcare providers across 2+ medical facilities.

400: Steady-state clinical governance and credentialing for 10–99 healthcare providers across 1+ medical facilities.

800: Operated 4+ Role 1 facilities AND 1+ Role 2 facility. Demonstrated MASCAL incident management under standard MEDEVAC timelines.

600: Operated 3+ Role 1 facilities AND 1+ Role 2 facility. MASCAL plans documented; no executed MASCAL response.

400: Operated 2+ Role 1 facilities OR 1+ Role 2 facility.

200: Operated 1+ Role 1 facility.

tc={C71DDAAB-C105-41BC-8EE6-6AEB458390E5}: [Threaded comment]

Your version of Excel allows you to read this threaded comment; however, any edits to it will get removed if the file is opened in a newer version of Excel. Learn more: https://go.microsoft.com/fwlink/?linkid=870924

Comment:

800: 4 sites each.

600: 3 sites each.

400: 2 sites each.

800: SOC operations demonstrated; High vulnerability patching within 30 days; PACE architecture exists and partially validated.

600: SOC capability demonstrated; IAVM compliance track record documented; PACE plan in place.

400: Cybersecurity program documented; IAVM compliance demonstrated; no PACE validation.

800: Demonstrated a funded, limited-scope technical pilot or demonstration of a predictive logistics (AI/ML) or digital twin capability on a Federal contract, with formal pilot results accepted by the USG.

600: Demonstrated at least one (1) Value Engineering Change Proposal (VECP) or formally approved engineering proposal for a modernization initiative under a Federal contract.

400: Demonstrated a Modernization Roadmap or technology integration plan as a required CDRL deliverable on a Federal contract.

800: Managed data synchronization using scheduled, secure batch flat-file transfers (e.g., CSV/JSON via SFTP) formatted to specific Federal/DoD system specifications.

600: Operated Government-provided systems (e.g., manual direct-entry into GCSS-Army, GFEBS, or equivalent Federal system) as the primary execution method.

400: Provided data primarily via structured electronic deliverables (e.g., formatted Excel reporting); no system-to-system integration or system operation.

800: Demonstrated a technical pilot or demonstration of a UxS or C-UAS capability.

600: Conducted certified UxS operations strictly for site survey or infrastructure inspection (e.g., FAA Part 107 roof/facility inspections).

400: Submitted a UxS or C-UAS integration plan, SOP, or mobilization playbook as a required CDRL deliverable.

Same comment as above for bucket 2

Define contested lines of communication and attrition-resilient routing

Are LSCO-projected casualty rates defined?