Operational Memory & Lessons
Connect current AOI work with permission-visible prior incidents, lessons, corrective actions and recurring operational gaps. Historical evidence stays clearly labeled and links back to its source record.
Vanguard VEMMilitary Installation readiness governance now includes a leadership risk register, retained governance decision history, review-board dispositions, restoration ownership and due dates, and portfolio views for open exposure, pending or active exceptions, expiring risk acceptances, due reviews and restored controls. Review-board actions do not silently change the authoritative assurance or exception state.
Military Installation readiness assurance now includes leadership escalation and temporary exception governance for non-current controls, with accountable ownership, authorized decisions, compensating controls, expiration and review dates. Approved exceptions remain temporary risk acceptance and do not make a control Current / Assured.
Vanguard VEMFrom Preparedness to Recovery—Connected.
Recovery 35.6.77 adds a universal Workflow bar with Go Back/Home, AOI and incident readiness, My Work and resume guidance, plus unsaved-change protection, required-field focus and explicit prerequisite feedback. Recovery 35.6.76 remains cumulative with zero-dead-end action feedback and a persistent context trail. Recovery 35.6.67 adds the Military Installation Readiness Risk Register, retained Governance Decision Log and Review Board workflow so leadership can track open exposure, temporary exceptions, due reviews, restoration actions and decision history without changing the authoritative Assurance state. Recovery 35.6.64 adds Military Installation Improvement Planning, recurrence analysis, institutionalization targets and readiness validation so verified corrective actions become durable preparedness improvements. Recovery 35.6.63 adds a dedicated Military Installation Corrective Action Tracker and Improvement Dashboard for the improvement work created when closure verification fails or recurs, with ownership, deadlines, priority, verification readiness, effectiveness evidence and source traceability. Recovery 35.6.62 adds post-resolution Military Installation closure verification and a governed feedback path into Continuous Improvement when a civil/community coordination resolution does not hold. Vanguard VEM connects emergency management, VOAD/nonprofit coordination, Tribal government, education systems, faith communities, jurisdiction-specific EOC staffing, Search/Rescue/Recovery, Multi-Agency Resource Centers, position workspaces, forms, intelligence, resources, training, continuous improvement and recovery in one configurable environment. Recovery 35.6.53 — Runtime Build Normalization / Cache Integrity normalizes build identity across active runtime surfaces, advances the Hybrid shell to a fresh v3 asset and adds whole-runtime Release Coherence scanning for stale build tokens. Recovery 35.6.52 remains cumulative with live build verification and the root Release Check; Recovery 35.6.51 remains cumulative with suite-aware Mission Packs and the Military Installations GIS overlay, while Operational Memory continues to connect current AOI work to permission-visible prior incidents, exercises, AARs, corrective actions, recurring gaps, decisions and resource precedent without treating historical evidence as current intelligence. The detailed AOI hierarchy now includes Military Installation immediately after County/Parish; the selected installation follows GIS/COP, Intelligence, Response, Guided Operations, ICS/IAP Readiness, Operational Copilot and Operational Memory while the user’s saved basemap/view remains intact. The cumulative platform retains the governed Operational Copilot, ICS/IAP completeness guidance, current-period ICS staffing, position workspaces, fillable ICS forms, AOI isolation, Live Intelligence source routing, category-specific maps, Workflow Studio, CRM, notifications, forms, contextual Instructions/Training and suite-specific capabilities.
Connect current AOI work with permission-visible prior incidents, lessons, corrective actions and recurring operational gaps. Historical evidence stays clearly labeled and links back to its source record.
Each suite review keeps the same connected AOI, incident, organization, people and operational-record foundation while emphasizing the workflows, terminology and safeguards that matter to that customer.
Common capabilities available across entitled suites: Quick Report, Live Intelligence, GIS/COP, Organizations, CRM, dashboards, reports, forms, Instructions and Training. Shared tools retain the signed-in organization, AOI, incident and permission context.
AOI-aware intelligence: As the selected geography narrows toward a jurisdiction, city or town, Vanguard emphasizes direct local reports. County and state views progressively reduce routine municipal detail while keeping verification confidence visible.
AOI intelligence, planning, EOC/ICS, resources, public information, damage, mitigation, continuity, recovery and documentation. Jurisdiction-specific EOC staffing supports city/municipal, county/parish/borough, and state/commonwealth departments and positions.
Member/partner coordination, capabilities, volunteers, donations, mass care, unmet needs, missions, referrals and long-term recovery.
Tribal government structure, Nation-defined terminology, government-to-government coordination, cultural-resource awareness and data-sharing controls.
Public school districts, schools, colleges, universities, early-childhood systems and Tribal education with facilities, students, staff, continuity and reunification workflows.
Faith-community operations, spiritual-care coordination, facilities, chaplains/volunteers, interfaith coordination, accommodations and community recovery.
Facility and coalition coordination, public health/medical operations, resources, mass care, continuity, communications, exercises and recovery.
Lifelines, facilities, outages, resource dependencies, continuity, restoration priorities, communications, exercises and public-sector coordination.
The interface puts the next operational task in front of the user and keeps underlying modules connected.
The current core registry contains 46 operational modules, supplemented by specialized suite workspaces that are not separate silos.
Every Vanguard VEM application page, module, specialized suite and mission/position workspace provides visible contextual Instructions and Training buttons in the normal page layout. Instructions and Training now include shared Faith & Cultural Community Considerations and content-wide Search practice; jurisdiction-specific EOC organization/staffing for city/municipal, county/parish/borough and state/commonwealth operations; expanded Search, Rescue & Recovery; Red Cross/MARC coordination; MMIR/MMBWG family-centered, privacy, sovereignty and culturally responsive safeguards; Program Schedule/Meetings and persistent meeting actions; Operational Assurance; decision/shift handoffs; resource lifecycle; credential/readiness review; plan-to-operation conversion; Controlled Workflow Templates; Standard Reports by Role/Function; My Organization Reports; form classification; mobile/offline field work; notification/acknowledgment; recovery transition; and accessibility/acceptance evidence.
Quick orientation, step-by-step task guidance, current workflow/report tools, form-classification checks, required context, documentation reminders and safeguards for the active module or workspace.
Quick, General and Specific/Position-level learning with Sandbox practice for Faith/Cultural community considerations and typo-tolerant Search, jurisdiction-specific EOC organization/staffing, expanded SRR operations, MARC coordination, MMIR/MMBWG culturally responsive coordination, Operational Assurance, meeting schedules/actions, decision/handoff logs, resource lifecycle, credential readiness, plan activation, workflow templates, role/organization report selection, mobile/offline operations, notification workflows, recovery handoffs, exercises, accessibility checks and knowledge checks.
Vanguard VEM supports coordination and decision-making; it does not replace incident command, legal authority, professional judgment, source verification, medical authority or local policy.
Choose the customer's suite, use the guided demonstration flow, then open Sandbox or Program when you are ready to show the live environment.
Recovery 35.6.63: Military Installation corrective actions now have a dedicated tracker and improvement dashboard, including focused My Work visibility and direct traceability to the coordination source.
Recovery 35.6.62: Military Installation coordination closure now includes post-resolution verification and Continuous Improvement feedback when a resolution is partial, ineffective, or recurring.
Recovery 35.6.61: Military Installation shift handoff now continues through carry-forward task completion and explicit Civil Coordination source reconciliation.
Institutionalized lessons now enter a sustainment-assurance lifecycle. Authorized users can assign evidence ownership, identify the readiness-control/version reference, record validation evidence and results, set the next review date, and route due or failed revalidation back into My Work. The register remains limited to non-sensitive civil/community coordination readiness information.
Military Installation selection is repaired. Vanguard now queries the current U.S. Census TIGERweb Military Installations layer with valid 2025 fields, uses POST-based server requests to avoid oversized geometry URLs, and automatically falls back to a browser-direct Census request when the hosting server cannot reach TIGERweb. A Retry Census Data control is available on AOI Selection. The existing Military Installations GIS/COP layer remains synchronized with the selected installation.
Military Installation readiness governance now carries Review Board follow-up actions into a dedicated action register with owner, due/checkpoint, progress, dependency, evidence-backed completion, retained action history, My Work routing, and printable/exportable board follow-up packets. Completing an action does not silently restore assurance, approve an exception, or close the Review Board item.
Developer-only commercial administration now preserves a chronological client lifecycle record for activations, pilots, renewals, changed terms, exceptions, suspensions, closures and reopenings. Material entries retain the decision or change, the reason/rationale, authorization, linked subscription, status effect and follow-up. Corrections supersede rather than delete prior entries, while commercial account status remains separate from emergency operational access.
Developer-only subscription administration now adds calendar-based renewal notices at 3 months, 2 months, 1 month and 1 week before the recorded subscription end date. The Renewal Center tracks the responsible renewal owner, dedicated renewal contact, next follow-up, reminder history, current account health, CSV export, host-email delivery with draft fallback, and a CLI scheduler for daily automated checks. Commercial renewal status never silently changes emergency operational access.
Internal Developer administration now connects client purchase history to structured suite/module entitlements, authorized seats, implementation stage, deployment environments, build/version references and seat-utilization review. Commercial entitlement records remain separate from operational CRM and do not automatically suspend emergency access.
Internal Developer administration now includes a protected Client & Subscription Registry for purchase history, subscription periods, renewal tracking and client contacts. Commercial terms remain separated from operational CRM and are not exposed to customer administrators.