Knowledge base
The document layer underneath the toolkit. Upload the contracts, reports and specifications; the rest of the platform can then cite them.
What Knowledge base does
The knowledge base stores critical project documents, including agreements, technical specifications, and contracts, transforming them into a retrievable asset rather than a static repository.
Uploads are processed into a searchable index with transparent status tracking. A shared taxonomy of categories and tags ensures the library remains structured and navigable as it grows.
You control access, ensuring sensitive project material remains isolated while organisational data remains available. The integrated viewer allows users to open documents in place to verify the evidence behind any citation.
This system serves as the evidence layer for the entire toolkit. It drives the digital technical assistant, the RAG matrix for assessment criteria, and contract review tools, ensuring every insight is grounded in source documentation.
Live · one answer, and its sources
6of 8 cited
Passages retrieved for one answer
Including the two it read and did not use — that is how you tell grounded from confident
What you get with Knowledge base
-
Upload and catalogue project knowledge
Drop in documents, or link to a folder, to build a library of shared project knowledge.
-
Categories and tags from a shared taxonomy
A managed category structure plus custom tags, applied consistently across the organisation, so a library of hundreds of documents is still easy to use.
-
Scoped visibility
Organisation-wide reference material and project-confidential documents live in the same system under different scopes, with ownership stored on each record.
-
Read it in place
An in-app document viewer opens the source alongside the work, so checking a citation does not mean hunting through a shared drive for the right revision.
-
Powers the technical assistant
The digital technical assistant answers from these documents and shows which ones it used, so an answer can be checked against its source in a click.
-
Auto-fill for due diligence
The due diligence tools can read criteria and automatically source evidence from selected knowledge base articles.
Knowledge base in use
Drawn in the product's own interface, and every figure is real: they come from our live Demonstration project — a 288.75 MW floating wind farm in the central North Sea — and its Default Scenario, so anything shown here can be reproduced in front of you. No client or commercial data appears on this page.
Upload is a first-class screen, not a hidden button
The Knowledge base opens on Upload new, because the library only works if putting things in it is easy. Three tabs: what you are adding, what is already there with a count, and the notes that never came from a file at all.
Knowledge Base
Upload and manage documents which then become available to the Digital Technical Assistant
Upload mode
Simple AdvancedUpload files (docx, pdf, xlsx)
Drop files here, or click to browse
"Just store knowledge" is the escape hatch for something that is true but is not in a document — a decision taken on a call, a number somebody confirmed by email. It goes in the same index as the files, so the assistant can use it and cite it.
Documents with a status, not a shared drive
The Uploaded Documents tab. Each upload queues, processes and becomes ready, and you can see which stage it is at. The last column is what reads from each file — which is what would break if it were withdrawn.
Knowledge Base
Upload and manage documents which then become available to the Digital Technical Assistant
Documents in scope for this project
| Document | Category | Visibility | Status | Used by |
|---|---|---|---|---|
| Generic TSA Heads of Terms DOCX | Contracts · Supply agreement | Project only | Ready | RAG matrix, Design basis, Assistant |
| Generic SAA Heads of Terms DOCX | Contracts · Service agreement | Project only | Ready | RAG matrix, Assistant |
| design-basis-considerations-for-the-design-of-floating…pdf PDF · 9 pages | Engineering · Floating foundations | Project only | Ready | Assistant, Design basis |
Nothing in this library is client work. The two Heads of Terms documents are our own generic templates and the floating design-basis paper is a published reference, which is what lets the Demonstration project be shown to anybody.
Check a citation without leaving the work
A real answer from this project's assistant history, with every passage it retrieved listed underneath — including the two it looked at and did not use. Each opens in place at the page it came from, so verifying a conclusion is a click rather than an afternoon in a shared drive looking for the right revision.
Equinor Floating Wind Farm Overview
The project you are referring to is Equinor’s planned floating wind farm in the central North Sea intended to electrify the Troll field, announced in 2022 and put on hold in 2023 due to immature technology and higher-than-expected costs [1][6]. The design would have involved floating turbines connected via AC-to-DC cables to offshore transformer stations, requiring careful mooring and cable design to manage environmental risks [4][7]. Key technical considerations included design currents, wave and soil conditions, safety levels, and abandonment planning, all documented in the project’s design-basis documentation [2][3].
| Ref | Passage | Relevance | Used in the answer |
|---|---|---|---|
| [1] | design-basis-considerations-for-the-design-of-floating…pdf page 2 | 0.5543 | Cited |
| [2] | design-basis-considerations-for-the-design-of-floating…pdf page 1 | 0.5367 | Cited |
| [3] | design-basis-considerations-for-the-design-of-floating…pdf page 2 | 0.5311 | Cited |
| [4] | design-basis-considerations-for-the-design-of-floating…pdf page 6 | 0.4992 | Cited |
| [5] | design-basis-considerations-for-the-design-of-floating…pdf page 9 | 0.4616 | Retrieved, not used |
| [6] | design-basis-considerations-for-the-design-of-floating…pdf page 5 | 0.4559 | Cited |
| [7] | design-basis-considerations-for-the-design-of-floating…pdf page 4 | 0.4357 | Cited |
| [8] | design-basis-considerations-for-the-design-of-floating…pdf page 6 | 0.4336 | Retrieved, not used |
References 5 and 8 are the honest part: the retriever found them, scored them, and the answer did not use them. Showing the passages that were considered and rejected is how you tell a grounded answer from a confident one.
See it on your own project
Book a demo and we will walk through the module with your numbers, not ours.
More of the toolkit
Digital Technical Assistant
An assistant that knows your documents and your open scenario, cites what it used, and drafts changes you approve before anything is written.
CAPEX
Build capital cost from the engineering — foundation, turbine, array, installation — so a design change shows up as a number the same day.
OPEX
Model the cost of running the farm from the things that actually drive it: agreements, vessels, weather windows, technicians and component failures.