Knowledge gaps and health
What BooleX knows, how fresh it is, and the questions no plant source could answer.
Knowledge gaps is for experts and administrators. It shows what BooleX has to work with and where it falls short.
Knowledge health
| Panel | Shows |
|---|---|
| Code | The imported project and when its export was imported, and the last import run and who ran it |
| Documents | The last import and the documents in each index status (indexed, indexed by OCR, failed) |
| Work orders | How many are on record and the last import |
| Alarm and trend history | The last import of alarm logs and trend exports |
| Journal | The latest technician journal record |
| Connectors | Each data connector's state (connected, or disconnected since when), from the data gaps of the last 30 days |
A stale import or a disconnected connector is the first thing to check when answers get thinner.
Gap log
When no plant source supports an answer, the technician can Log a knowledge gap from the answer. The gap log lists these questions, newest first, with the asset and who logged them. Close a gap by adding the missing source: a document to the manifest or the watched folder, a work-order export, or a journal record.
Imports and the glossary
Imports are run by an expert or administrator: code exports, documents, work orders and parts lists, and alarm and trend history. See Import code exports and Documents and work orders. The site glossary (the names the floor uses) is set in site.yaml.
Workflow definitions
Experts enable, disable and tune the workflows through the API (PUT /api/workflows/{id}, POST /api/workflows/{id}/enable or /disable); every change is audited.
Planned. Imports, the glossary and workflow definitions edited from this screen, and knowledge-pack import and export from it. Today they are commands and configuration files.