> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vh3.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Data, graph, and search

> What lives in the knowledge graph, how search works, and data export.

## Data, graph, and search

<AccordionGroup>
  <Accordion title="What is in the knowledge graph?">
    Jobs are the central node, connected to customers, engineers, job types, outcomes, worksheets, equipment, and operational history. The graph captures relationships that match field service reality: the same engineer across different customers and locations, the same equipment across different sites, and patterns that cross account boundaries.

    That connected structure makes questions answerable when they involve more than one record, for example repeat failures across a customer estate or engineer performance on one job type.
  </Accordion>

  <Accordion title="What is vector search for?">
    Finding semantically similar past jobs, for example "boiler pressure fault on a commercial site," using intake descriptions and diagnostic outcomes. Results are often combined with keyword search for exact part numbers or fault codes, giving precision and meaning-based discovery in the same query.
  </Accordion>

  <Accordion title="How often is data updated?">
    Job enrichment runs as data lands from your FMS. Customer summaries and some aggregate views refresh on scheduled tasks. The intelligence layer stays current as new jobs, outcomes, and customer activity arrive.
  </Accordion>

  <Accordion title="Can I export my data?">
    Discuss export and portability with your account team. Your operational records remain in your FMS. VH3 holds enriched analytics and the operational graph. On cancellation, export arrangements are handled according to your commercial agreement and data processing terms.
  </Accordion>
</AccordionGroup>