§01 / Industrial reasoning engine

The schematic is on paper.
The senior engineer is retiring.
Socrate reads both.

Socrate ingests electrical schematics (EPLAN and legacy), mechanical drawings, and operator manuals from any vintage of industrial machine, and binds them into a knowledge graph with traceable, deterministic reasoning. Built for the factories that exist, not the ones in the brochure.

Ingest
EPLAN, DWG, PDF, paper
Binds
Electrical, mechanical, docs
Deploys
On-premise, air-gapped
socrate / bind
3 sources → 1 graph
SHEET 217 / EPLAN K1 M1 eplan / clean DRG-1998-04A / SCAN add -94B1 see §4.7 legacy / annotated MANUAL §4.7 / DE manual / DE -94B1 photo-eye K1 +SK3 M1 B7 §4.7 Y4
eplan legacy.dwg manual.pdf -94B1 bound
~412 ms
Supported by
  • SACMI
  • Trenord
  • Fassi.Gru
  • Smart Capital
  • Bocconi4Innovation
  • S2Capital
§02 / The problem

European industry is brownfield.
The tooling is not.

01 brownfield

The schematics are not in EPLAN.

They are scanned PDFs from 1998, DWG files with no layer hygiene, paper drawings with handwritten corrections, multi-vendor exports that never agreed on a naming convention. A parser that assumes EPLAN gives up here.

02 tacit knowledge

The knowledge is not in the journals.

It is in the heads of the two or three senior engineers who have worked on these machines for twenty years. They will retire in the next five. They do not write things down. A wiki is not a strategy.

03 cross-domain

The domains are not connected.

Electrical schematics, mechanical assemblies, and operator manuals describe the same machine in three different languages. The component -94B1 in the wiring diagram is the same photo-eye drawn in the mechanical layout and referenced in section 4.7 of the manual. Nothing currently binds them together.

§03 / What Socrate is

A reasoning engine,
not a search engine.

Socrate is not a retrieval layer over your documents. It is a deterministic reasoning engine that operates on a knowledge graph built from your real schematics and your engineers' real expertise. Every answer is a reasoning chain you can audit node by node.

A / ingest every format, every vintage

Multi-format ingestion

EPLAN, legacy DWG, scanned PDFs, hand-annotated paper, mechanical assembly drawings, multilingual operator manuals. Ingestion pipelines for the formats no one else has bothered to support.

B / bind one node, many sources

Cross-domain binding

Electrical references, mechanical components, and manual sections resolve to the same physical node in the graph. Ask about -94B1 and Socrate returns the wiring, the mechanical position, the datasheet, and the maintenance history as one answer.

C / encode supervised, by design

Human-in-the-loop graph construction

Our knowledge engineers sit with your senior technicians during onboarding. Their reasoning becomes graph relationships. This is the only honest way to encode tribal knowledge before it walks out the door.

D / reason traced, auditable
trace(fault: conveyor_3.intermittent)
-94B1 / K1.aux / +SK3.F / §4.7
edges: 6 / sources: 3 / ms: 18
caused_by: photo-eye misalignment
confidence: deterministic (graph-derived)
audit_id: 0x4f29a1

Deterministic reasoning

Every answer is a traced chain across the graph. No probabilistic retrieval. No "most likely relevant page." For regulated industries this is non-negotiable.

§04 / How it works

From schematic
to reasoning chain.

Four stages. Nothing in this pipeline depends on a model having memorized your machines. The output of each stage is human-inspectable.

  1. step 01 ingest

    Ingest

    Every format, every vintage. EPLAN, DWG, PDF, paper, manuals.

  2. step 02 validate

    Validate

    Human in the loop. Our knowledge engineers, with your senior technicians.

  3. step 03 bind

    Bind

    One graph across electrical, mechanical, and documentation.

  4. step 04 reason

    Reason

    Traced answers. Auditable end to end. Deterministic by construction.

worked example / conveyor 3
trace_id: 0x4f29a1
› question

Why does conveyor 3 stop intermittently on the night shift?

Asked by
Field technician, T-2
Machine
Packaging line, 2008
Sources
3 (EPLAN, mech, manual)
Resolved in
18 ms
› reasoning chain
graph-derived 3 sources 6 edges answer: misalignment
§05 / What changes on the floor

Outcomes you can defend
in a quarterly review.

01

Junior technicians answer the questions only senior engineers used to answer.

The reasoning chain is the training material. New hires reach productive diagnosis on machines they have never seen before, without waiting for the one person who remembers the install.

02

Faults stop being individual events.

Socrate surfaces the third time the same relay has stuck across three plants. Patterns the maintenance team could not see become procurement decisions the plant director can defend.

03

Twenty years of legacy schematics become an asset.

The drawer of paper drawings stops being a liability nobody wants to touch and becomes the most accurate map of how your machines actually behave.

§06 / Industries

Built for industries
where the answer must be right.

01

Heavy lifting and cranes

Field service in remote conditions, every minute of downtime billable.

Why it matters here

Schematic access from the cab, not the back office.

02

Rail and rolling stock

Safety-critical, audit-traceable maintenance under regulator scrutiny.

Why it matters here

Every diagnostic comes with the chain of evidence behind it.

03

Defense and aerospace

Air-gapped, classification-aware, reasoning chains that survive an audit.

Why it matters here

Zero outbound traffic. No data leaves the perimeter.

04

Industrial automation OEMs

Multi-vintage installed base, multi-vendor schematics, customers on three continents.

Why it matters here

Service desk answers scale without growing the bench.

05

Advanced packaging

High-speed lines where intermittent faults cost more than the fix.

Why it matters here

Root cause in minutes. Not after a teardown.

06

Energy and oil & gas

Plants whose schematics predate the people currently operating them.

Why it matters here

Paper, scans, and DWG, ingested without rework.

§07 / Deployment

On-premise. Air-gapped.
Your data never leaves.

Socrate runs entirely inside your network. Schematics, graphs, and reasoning chains stay on your hardware. We ship a signed appliance; you control the keys, the updates, and the audit log.

Full on-premise deployment

on-prem

No cloud dependency required. Socrate runs inside your network, on your infrastructure.

Air-gapped option

air-gap

For defense, aerospace, and regulated environments. Zero outbound traffic. Reasoning chains stay on site.

Compliance posture

eu/iso

ISO 27001 in preparation. GDPR by design. EU AI Act aligned. Documentation available on request.

customer network / 10.0.0.0/8
isolated
firewall / DMZ internet denied socrate.appliance signed appliance /api /graph /trace sso saml oidc schematics /mnt/eplan engineers field / bench ticketing / ERP read-only
cpu 16 vCPU
ram 64 GB
disk 500 GB SSD
§08 / Who we are

Engineers building for the industrial base that actually exists.

E-Plato is a team of engineers building Socrate for the industrial base that actually exists. We work directly with our customers' maintenance teams and senior technicians. We deploy on your premises, on your terms, with your data never leaving your network. We are deliberately European, deliberately specialized in industrial reasoning, and not interested in being a general-purpose AI vendor.

Discipline
Industrial reasoning
Footprint
European
Engagement
On site, on premises
Posture
Specialist
team / discipline mix hiring
  • 01 Knowledge engineering
    graph, ontology
  • 02 Schematic parsing
    EPLAN / DWG / OCR
  • 03 Reasoning systems
    deterministic
  • 04 Field deployment
    DACH / IT / FR
  • 05 Open role / Backend engineer
    apply →
§09 / Request a demo

Bring us your dirtiest schematic.

We will run Socrate on your worst legacy machine and show you the reasoning chain in a 90-minute session. No data leaves your premises.

info@e-plato.com / +39 0521 162 7380