Skip to content
Akan Industrial and Automation

AI & Software

On-Premises AI Systems and Industrial Software

Private AI systems, integration with plant and business systems, and custom industrial applications that run on your own hardware. Data stays on site and connections to plant systems are read-only.

On-premises AI systems are language models, retrieval over documents and data, and the software around them, installed on hardware the client owns and run inside the client’s network. Akan Industrial and Automation designs and deploys these systems for process plants and industrial organisations whose data may not leave the premises or the country under their own policy, including fully air-gapped installations. Akan also builds read-only connections to plant and business systems and develops custom industrial applications for one client’s process. Nothing writes to the control system.

Why run AI on your own premises?

  • Data control. Documents, measurement data and the questions your engineers ask stay on hardware you own. Nothing is sent to an external service.
  • Operation without internet. The system works inside a closed network. In an air-gapped installation, models and updates are brought in through a procedure agreed with your IT department.
  • No usage fees. Hardware is sized for a known workload; there are no per-use fees to an external service. Hardware, power and maintenance remain your cost.

What does Akan deliver?

Service What is delivered
Private AI system Open-weight language models on your hardware, retrieval over your documents and data, access control, audit logging and hardware sizing advice. Air-gapped installation where required.
System integration Connections to plant and business systems through accounts with read permission only: OPC UA, historians, laboratory systems, ERP and CMMS. Field devices are read through your existing data acquisition system, not directly.
Custom industrial applications Dashboards, reporting, data pipelines and workflow tools built for one client’s process.
Technical review of a stalled project Review of an AI or software project that has stalled: architecture, data and evaluation, with a written recovery plan.
Integration sprint One integration, confirmed as feasible in the assessment, working end to end. Fixed scope, typically four to six weeks.

Akan specifies, supplies and commissions analyzers, instrumentation and skids, so integration work is done with knowledge of what the signals mean. The work covers systems and equipment of any make, including equipment Akan did not supply.

How does a private AI system work?

Open-weight language models run on servers in your network. A retrieval layer indexes the documents and data you select: specifications, datasheets, manuals, procedures, maintenance records and measurement data. When an engineer asks a question, the system searches that material and writes an answer that cites its source documents. The engineer can open each source and check it.

Access control is set up by user role and by document groups agreed in the assessment. Each question and answer is recorded in an audit log. The system is advisory. Engineers review the answers and decide.

What the system does not do

  • It does not write to a PLC or DCS and does not change setpoints.
  • It does not filter, alter or delay data reported to an authority.
  • It is not a substitute for accredited laboratory tests.
  • It does not send documents or data outside your network.

How does a project run?

Work follows four steps: Assess, Pilot, Deploy, Support.

  1. Assess. A paid assessment reviews the use case, the data sources, the network constraints and the available hardware. The result is a written scope with deliverables and a typical duration.
  2. Pilot. One use case runs on your hardware, with acceptance criteria agreed in advance.
  3. Deploy. The system is opened to its users with access control, audit logging and documentation in place.
  4. Support. Updates and changes are handled under an agreed support scope.

To start, Akan needs technical contacts from IT and from the process or instrumentation side, representative documents or data, your network and information security policy, and details of the available hardware. Where personal data is involved, a data-processing agreement is signed before work starts. The working method is described in Method, Data and Security.

What do you receive at handover?

Documentation and operating instructions are delivered with the system. The systems are built on open-weight models and open-source components, so there is no platform licence fee. Ownership and licence terms of the software written for you are agreed in the contract.

Who is it for?

  • Plants and industrial organisations whose policy keeps data on the premises or in the country
  • Sites with closed or air-gapped networks
  • Engineering and maintenance teams that need answers from their own documents and measurement data
  • Organisations whose AI or software project has stalled and who need a written technical review

To discuss a scope, contact Akan.

Frequently asked questions

Does any data leave our site?

Not from the installed system. Models, document indexes and applications run on your hardware inside your network, including fully air-gapped installations. If sample documents or data are to be reviewed off site during the assessment, this is agreed in writing beforehand.

Is there a platform licence fee?

No. The systems are built on open-weight models and open-source components, so there is no platform licence fee. Ownership and licence terms of the software written for you are agreed in the contract.

Can the system write to our PLC or DCS?

No. Connections to plant systems are read-only and nothing writes to the control system or changes setpoints. The system is advisory: engineers review the answers and decide.

What hardware do we need?

That depends on the number of users, the volume of documents and data, and the models chosen. Akan gives hardware sizing advice during the assessment, and the system is installed on hardware you own.

How long does an integration sprint take?

A fixed-scope integration sprint typically takes four to six weeks and delivers one integration, confirmed as feasible in the assessment, working end to end. Scope and deliverables are stated in writing before work starts.

Request a quote for your project

Tell us about your application and our engineers will get back to you within one business day.

Search