AI for Engineering Documents and Specifications is a service of Akan Industrial and Automation that compares technical specifications with datasheets and vendor offers, and gives engineers cited answers from their own manuals, procedures and project documents. The software runs on the client’s premises. Every result refers to the clause and page it comes from, and the responsible engineer reviews and decides. The service is part of Akan’s Industrial AI and Software practice.
What does the service cover?
The service has two parts. Both work on documents the client already owns, for equipment of any make, including equipment Akan did not supply.
| Service | Who it is for | What you receive |
|---|---|---|
| Engineering Document Check | Bid, engineering and procurement teams of EPC contractors, package builders and plant projects | A compliance matrix and a deviation list for instrumentation and analyzer packages, with a clause and page reference for every item |
| On-Premises Engineering Document Assistant | Engineering, maintenance and operations teams that work with large document sets | Cited answers from your own manuals, procedures, datasheets and project documents, with role-based access and an audit log |
How does the Engineering Document Check work?
The check reads a technical specification and the datasheets and vendor offers submitted against it for instrumentation and analyzer packages. It breaks the specification into individual requirements and looks for the matching statement in each datasheet or offer.
- Compliance matrix: one row per requirement, with the specification clause and page, the corresponding statement in the vendor document and its page, where one exists, and a proposed status.
- Deviation list: the items where an offer differs from the specification or does not address it, prepared for technical clarification with the vendor.
Clauses outside the agreed scope are passed through unassessed and marked for the client’s responsible engineer, who reviews the matrix, corrects it where needed and signs it. The software proposes; it does not approve or reject an offer.
Akan configures the check; Akan also specifies, supplies and commissions analyzers, instrumentation and skids. Where Akan is itself a bidder for a package, it does not take part in checking the offers for that package.
How does the On-Premises Engineering Document Assistant work?
The assistant answers questions in plain language from the client’s own document set. Each answer cites the document, section and page it relies on, so the engineer can open the source and verify it. Where the indexed documents do not contain an answer, the assistant is set up to say so.
- Role-based access: users receive answers from the documents their role is allowed to see.
- Audit log: questions, answers and cited sources are recorded.
- Languages: Turkish and English documents.
- Location: the system runs on your premises, can use open-weight models and needs no connection to the control network. Where it reads from a document management system, the connection is read-only.
Licensed standards texts are indexed where the client confirms that its licence allows it.
What do we need from you?
| Input | Purpose |
|---|---|
| Technical specification with annexes | Source of the requirements for the check |
| Datasheets and vendor offers for one package family | Documents compared with the specification |
| Sample of manuals, procedures and project documents | Document set for the assistant |
| Test set agreed with you | Requirements and questions with known answers, used to measure accuracy |
| Named responsible engineer | Reviews the results and signs the matrix |
| On-premises computing environment | Defined together during the assessment |
How does an engagement run?
Work follows the practice’s ladder: Assess, Pilot, Deploy, Support.
- Assess. A paid assessment, typically two weeks, on your own documents. Accuracy is measured against the agreed test set before any further commitment. The report states which document families are suitable and which are not.
- Pilot. For the document check, typically a six-week sprint. For the assistant, typically a six-week pilot for one site and one document group. Acceptance criteria are agreed before the pilot starts.
- Deploy. Installation on your premises, user roles, audit log and handover documentation.
- Support. Updates, additional document families and repeat measurement against the test set.
Scope, typical duration and deliverables are stated in Akan’s proposal for each step.
What are the limits?
- Scanned, handwritten or poor-quality documents reduce accuracy. They are evaluated in the assessment and the result is reported openly.
- Results are advisory. They support the engineer’s review and the technical clarification with vendors; they do not replace either.
- Nothing writes to the control system.
- Where documents or the audit log contain personal data, a data-processing agreement is signed.
To discuss a document set or an upcoming bid, use the contact page.
