{"ok":true,"meta":{"page_title":"Vendor Day — executive synthesis","synthesis_note":"Synthesized from in-repo capture artifacts only. Government wording is paraphrased where the portfolio strategy document cites SAM notices, Q&A, and ingested PDF extracts. Items labeled inference reflect slide structure or analyst framing documented in data/outputs/DHA_Portfolio_Strategy_2026.md.","sources_index":["data/outputs/DHA_Portfolio_Strategy_2026.md","data/inputs/dha_strategy.json","data/inputs/dha_pipeline.json","data/inputs/dha_decision_matrix.json"]},"executive_summary":[{"text":"PEO DHMS is planning a competitive Federal EHR award tied to the MHS GENESIS recompete while publicly testing modular contracting (BoS/BoB pillars, multiple potential awards) and an explicit system-integrator hypothesis — not a finalized single-prime model.","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §2 (Customer intent, Contract strategy signals)"]},{"text":"Customer-stated priorities emphasize faster follow-on competitions, VA/Federal interoperability, commercial-speed digital delivery, care outcomes, and (where appropriate) value-based compensation — i.e., capture themes must map to notice language, not generic IT claims.","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §2 (Top 5 DHA priorities from Special Notice)"]},{"text":"Transition and integration risk is elevated: materials reference a planned bridge with the incumbent, on-prem to cloud hosting risk asymmetry, and open Q&A on SPI extension through OCI — timing and governance are still being worked.","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §2 (Incumbent misalignment, System integrator positioning)"]},{"text":"The leadership pipeline differentiates opportunities: strong GO posture where ASRC has technical provenance (e.g., data exchange / DMIX lane) vs. SUB-only on GENESIS-scale sustainment where iron-triangle incumbency dominates narrative.","sources":["data/inputs/dha_decision_matrix.json","data/inputs/dha_pipeline.json"]},{"text":"Working hypothesis (visual deck): Industry Day slides frame a shift from a single prime toward multiple contracts and modular “building blocks” to optimize competition — treat as directional until solicitation language locks.","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §2 (Inference: slide_21.png / slide_22.png)"],"inference":true},{"text":"Portfolio concentration remains the operating rule: prioritize DHMS-core anchors with evidence depth (DMIX/DISS, GENESIS sustainment narrative, Workforce 3.0 as a near-term forcing function per portfolio executive summary) over long-tail GSP slots without a dated path.","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §1","data/inputs/dha_strategy.json (win_strategy)"]}],"signal_blocks":[{"id":"customer","title":"Customer signals","signal":"DHA / PEO DHMS used Industry Day and SAM channels to brief an evolving contract strategy, request structured industry feedback, and manage Q&A on Bidscale with published cadence.","why_it_matters":"Capture must track published answers and draft strategy drops as first-class intelligence — customer is still refining structure, not executing a static RFP.","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §2 (Customer intent, Q&A channel)"]},{"id":"scope_mission","title":"Scope / mission signals","signal":"Federal EHR / MHS GENESIS recompete framing ties delivery to operational health outcomes, interoperability with VA and other Federal partners, and long-term IT sustainability.","why_it_matters":"Win themes should trace to those mission threads (portfolio doc lists notice-aligned win themes).","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §2 (Win themes from notice language)"]},{"id":"acquisition","title":"Acquisition signals","signal":"Draft/strategy materials describe flexible outcome-based relationships, BoS/BoB solution lines, tiered services, Technical Integration (labeled System Integration in draft), and a planned incumbent bridge for transition.","why_it_matters":"Teaming, pricing, and role definitions (prime vs. sub vs. direct vendor) must align to the pillar model the Government is stress-testing.","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §2 (Contract strategy signals; Mar 31 / 22 Dec extracts cited there)"]},{"id":"incumbent_competitor","title":"Incumbent / competitor signals","signal":"Q&A text states the current contract was awarded to Leidos, Inc.; materials discuss transition risk during contractor changes in cloud moves while noting competition can be lower-risk in some pillars.","why_it_matters":"Incumbent narrative is a transition and governance problem, not a generic “avoid Leidos” slogan — ASRC should cite Government risk framing.","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §2 (Incumbent misalignment — Government text only)"],"inference_note":"ManTech DMIX lane context appears in workspace graph/metrics, not in the HCDS Vendor Day PDF extracts list in the portfolio doc — do not attribute ManTech to those PDFs without separate artifacts."},{"id":"integration_transition","title":"Integration / transition signals","signal":"Architecture narrative highlights Med-COI, Rhapsody/integration engines, ATOs, cloud transition (~2027) vs. award timing (~July 2026) tension, and SPI continuity through OCI as an open thread.","why_it_matters":"ASRC’s credible wedge (per dha_strategy.json) sits at integration seams, governance, and transition discipline — align proof points to those seams.","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §2 (Architecture / integration insights)","data/inputs/dha_strategy.json (strategic_key, risks)"]},{"id":"teaming","title":"Teaming signals","signal":"Government asked industry to help define whether system integration is needed, one vs. multiple integrators, and how modular pillars perform — Q&A references Industry Day slide #22.","why_it_matters":"Teaming maps should be modular (who owns BoS/BoB vs. TI/SI vs. services tiers) rather than assuming a single SI-led enterprise wrap.","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §2 (System integrator positioning; Q&A excerpt)"]},{"id":"risks_unknowns","title":"Risks / unknowns","signal":"RFI/planning-only posture, unfinished structure/resourcing, dual operations, SPI extension timing, and prime vs. multiple awards remain explicitly open in Q&A threads cited by the portfolio doc.","why_it_matters":"B&P spend should track evidence depth; avoid over-committing while Government models are still moving.","sources":["data/outputs/DHA_Portfolio_Strategy_2026.md §2 (Open issues, Planning-only status)"]}],"strategy_impact":{"intro":"Align ASRC’s capture plan to the same evidence spine used in this workspace: Vendor Day + contract-strategy artifacts for narrative, pipeline JSON + decision matrix for posture, graph for relationship risk.","statements":["Credible wedge: integration governance, data-exchange / interoperability proof, Rhapsody–Med-COI complexity, and disciplined transition storytelling — consistent with data/inputs/dha_strategy.json (strategic_key, win_strategy).","Avoid over-investing: long-tail opportunities with weak FPDS / requirement signal — leadership matrix marks KILL (NOISE) rows; dha_strategy.json warns against thin-signal bids.","Incumbent vulnerability is situational: transition and cloud moves create asymmetric risk in Government’s own framing — use verbatim risk language in capture, not generic “displace incumbent” claims.","Prime vs. sub: portfolio JSON shows GO on DMIX/DISS and Walter Reed, SELECTIVE on Workforce 3.0 and DENCOM, SUB on HCDS GENESIS sustainment — mirror in gate reviews and teaming maps.","Emphasize in win themes: follow-on speed, VA/Federal interoperability, outcome-based / sustainable IT, and modular accountability where the RFP allows — drawn from notice-aligned list in data/outputs/DHA_Portfolio_Strategy_2026.md §2.","Make integration, transition, and governance central where TI/SI and bridge-period language appear in Government materials; treat SI scope as a competed hypothesis per portfolio doc conclusion."]},"recommended_posture":{"pursuit_posture":"PORTFOLIO (mixed)","pursuit_posture_lines":["GO (invest): DMIX / DISS / Data Exchange; GSP TO #13 (Walter Reed) — per data/inputs/dha_decision_matrix.json","SELECTIVE: Workforce 3.0; DENCOM CDS II","SUB-ONLY: HCDS (GENESIS) Sustainment","KILL (noise): Sync.MD; Care Coordination / EBMS-D — absent stronger FPDS/requirement signal"],"pwin_range":"Approximately 0.15–0.85 across named opportunities in the leadership matrix (see dha_decision_matrix.json rows).","why_now":"Vendor Day and posted contract-strategy artifacts show active restructuring of the Federal EHR acquisition model while the Government is still publishing Q&A — early positioning shapes teammate maps and narrative before solicitations firm up.","key_discriminator":"Evidence-backed integration and governance narrative tied to notice priorities and transition risk — matches data/inputs/dha_strategy.json strategic_key.","biggest_blocker":"Unresolved system-integrator authority, OCI/SPI timing, and final multi-contract vs. prime structure — listed as active risks in dha_strategy.json and portfolio §2.","immediate_next_move":"Run leadership alignment on the same opportunity ordering as data/outputs/DHA_Portfolio_Strategy_2026.md §1 (Workforce 3.0 forcing function, DMIX anchor, GENESIS/TMIP focus, selective GSP) and refresh graph + matrix tabs before major B&P commits.","sources":["data/inputs/dha_decision_matrix.json","data/inputs/dha_pipeline.json","data/outputs/DHA_Portfolio_Strategy_2026.md §1"]},"open_questions":[{"text":"Final vehicle mix and award structure (prime vs. multiple contracts; which pillars are competed together).","basis":"Open in Q&A / strategy threads summarized in data/outputs/DHA_Portfolio_Strategy_2026.md §2."},{"text":"System integrator role: one vs. multiple vs. none — Government explicitly soliciting industry input.","basis":"Q&A excerpt in data/outputs/DHA_Portfolio_Strategy_2026.md §2 (4 Dec 2025)."},{"text":"OCI migration timing vs. award clock; SPI extension through OCI — follow-on questions described as still being worked.","basis":"data/outputs/DHA_Portfolio_Strategy_2026.md §2 (System integrator positioning; architecture insights)."},{"text":"Dual operations, bridge mechanics, and transition governance details pending final solicitation.","basis":"data/outputs/DHA_Portfolio_Strategy_2026.md §2 (Open issues)."},{"text":"DMIX/DISS-specific Government wording in HCDS PDF extracts: portfolio doc states those acronyms do not appear in the six Vendor Day PDF extracts — interop proof remains FPDS/workspace-grounded unless new artifacts link them.","basis":"data/outputs/DHA_Portfolio_Strategy_2026.md §2 (DMIX/DISS note)."}],"next_actions":{"customer":["Monitor Bidscale Q&A drops and SAM-posted contract-strategy PDFs; map new answers to graph edges and matrix evidence columns.","Prepare leadership talking points using notice-aligned win themes from data/outputs/DHA_Portfolio_Strategy_2026.md §2 (not generic capability lists)."],"partner_teaming":["Build modular teammate maps aligned to BoS/BoB + services tiers described in portfolio §2; avoid default single-SI wraps.","For SUB lanes (e.g., GENESIS sustainment per matrix), pre-identify integration seams where ASRC scope is narrow and defensible."],"intel":["Reconcile graph relationships (e.g., DMIX/ManTech context) with source_ref on nodes/edges when Vendor Day JSON is present; flag anything not in HCDS PDF extracts as non–Vendor-Day provenance.","Track FPDS/USAspending rows for opportunities marked GO vs. KILL in dha_decision_matrix.json."],"solution":["Draft transition and governance annex tying Med-COI / Rhapsody / ATO threads (portfolio §2) to ASRC past performance proofs.","Stress-test Workforce 3.0 storyline against Vendor Day Priority 4 / sustainability language per data/outputs/DHA_Portfolio_Strategy_2026.md §3."],"pricing_transition":["Model bridge-period and cloud migration risk in pricing narrative where Government cites asymmetric transition risk.","Where value-based compensation is in scope, prepare optional commercial-structure talking points qualified by “where appropriate” notice language."]},"briefing_cta":{"label":"Submit a Briefing Request","href":"https://www.runaiva.com/","note":"Links to public RunAiVa site; replace with a dedicated briefing intake URL when available."}}