Engineering Intelligence Council | ENGINPILOT
COMMUNITY / ENGINEERING INTELLIGENCE COUNCIL

A discipline is established by practitioners, not by a vendor.

The Engineering Intelligence Council is a body of practising engineers who hold that engineering defines, AI assists and physics validates — and who are willing to put their name to it. Convened by ENGINPILOT in 2026 and open to engineers at any organisation, including those who never become customers.

CONVENED
2026
SIGNATORIES
148
DISCIPLINES
9
COUNCIL SEATS
12
01 — TWO WAYS IN

Signatory is open. Council is elected.

Any practising engineer may sign the manifesto and be listed. From the signatories, twelve seats are elected annually to the Council itself — the group that reviews whitepapers before publication, arbitrates the ontology and holds ENGINPILOT to the principles it published.

SIGNATORYOpen · name, title and organisation published
CONTRIBUTORBy submission · failure cases, constraint models, review notes
COUNCILElected · twelve seats, two-year term, published minutes
MEMBERSHIP STRUCTURE SIGNATORIES · OPEN ENDORSE THE PRINCIPLES · NAME PUBLISHED 148 CONTRIBUTORS · BY SUBMISSION FAILURE CASES · CONSTRAINT MODELS · REVIEW 41 COUNCIL · ELECTED GOVERNS PUBLICATION AND ONTOLOGY 12 FIG 1 / MEMBERSHIP STRUCTURE · NTS EP-CM-001
02 — WHAT THE COUNCIL DOES

Three responsibilities, all of them public

A council that only endorses is a logo wall. This one has work attached, and the output of that work is published whether or not it flatters ENGINPILOT.

REVIEW

Whitepapers before publication

Every paper on /research/ is read by at least two Council members outside ENGINPILOT before release. Reviewer names are printed on the paper. Dissenting notes are published alongside it, unedited.

ARBITRATE

The shared ontology

What counts as an asset, a failure mode, a constraint or a decision record is a discipline-level question, not a product decision. Proposed changes to the ontology go to the Council with a written rationale and a recorded vote, and the ruling binds every ENGINPILOT property that implements it.

HOLD TO ACCOUNT

The principles, against the product

Once a year the Council assesses whether ENGINPILOT still meets the manifesto it published — specifically whether any AI output can reach an engineer without a physics verdict attached. The assessment is published in full.

03 — THE TWELVE SEATS

Seats are allocated by discipline, not by seniority

FOUNDING ELECTION · CLOSES 2026-11-30

A council drawn from one discipline would arbitrate the ontology in that discipline's favour. Each seat is therefore reserved for a named field, with no more than two seats held by any one employer and no seat held by ENGINPILOT.

SEAT 01 NOMINATIONS OPEN
Rotating equipment
SEAT 02 NOMINATIONS OPEN
Thermal and HVAC systems
SEAT 03 NOMINATIONS OPEN
Electrical and critical power
SEAT 04 NOMINATIONS OPEN
Process and chemical
SEAT 05 NOMINATIONS OPEN
Structural integrity
SEAT 06 NOMINATIONS OPEN
Controls, OT and automation
SEAT 07 NOMINATIONS OPEN
Reliability and maintenance strategy
SEAT 08 NOMINATIONS OPEN
Digital twin and simulation
SEAT 09 NOMINATIONS OPEN
Data centre operations
SEAT 10 NOMINATIONS OPEN
Healthcare estates
SEAT 11 NOMINATIONS OPEN
Academia or standards body
SEAT 12 NOMINATIONS OPEN
Academia or standards body

No seat is filled. Members are elected from the signatories and their names, affiliations and declared interests are published here on election — not before, and not by appointment.

SIGN, THEN STAND FOR A SEAT →

04 — SIGNATORIES

Engineers who have put their name to the principles

SHOWING 12 OF 148 · UPDATED WEEKLY
Signatory name
Head of Reliability · Semiconductor fab, Dresden
ROTATING EQUIPMENT
Signatory name
Principal Engineer · Hyperscale data centre operator
THERMAL SYSTEMS
Signatory name
Chief Engineer · Petrochemical complex, Jamnagar
PROCESS SAFETY
Signatory name
Director of Facilities Engineering · Teaching hospital
CRITICAL POWER
Signatory name
Reliability Manager · Automotive assembly, Pune
MAINTENANCE STRATEGY
Signatory name
Professor of Mechanical Engineering · University
TRIBOLOGY
Signatory name
Asset Integrity Lead · Offshore wind operator
STRUCTURAL FATIGUE
Signatory name
Controls Engineer · Pharmaceutical manufacturing
OT ARCHITECTURE
Signatory name
VP Engineering · Grid infrastructure utility
HIGH VOLTAGE ASSETS
Signatory name
Senior Consultant · Independent reliability practice
RCM AND FMEA
Signatory name
Head of Digital Twin · Steel producer
SIMULATION
Signatory name
Standards Committee Member · National body
ASSET MANAGEMENT

Signatories endorse the principles as individuals. Organisation names are shown for context and do not imply institutional endorsement or a commercial relationship with ENGINPILOT.

05 — TERMS OF MEMBERSHIP

What is asked, and what is not

MEMBERS RECEIVE
Whitepapers and architecture papers ahead of publication Access to the shared failure-case library, anonymised A quarterly technical session, recorded and published Attribution on any paper they review or contribute to
MEMBERS ARE NOT ASKED TO
Buy, pilot or evaluate anything Share employer data, drawings or operating history Promote ENGINPILOT or appear in marketing material Pay anything — membership is free and always will be

A signature may be withdrawn at any time by writing to hello@enginpilot.com. Upon a valid withdrawal request, the public signatory entry is removed within five working days, subject to applicable legal and record-retention requirements.

A signature represents the individual's personal endorsement of the manifesto, not an endorsement by their employer or organisation. The signatory record belongs to the individual and remains associated with them if they change employers or roles.

Read the manifesto. If you agree with it, sign it.

Signing takes a name, a title and an organisation. There is no evaluation call attached to it, and no follow-up unless one is requested.