ELARD · Meeting summary

AI that works on your own knowledge

Our meeting at ELARD: summary, IT infrastructure and next steps

Wednesday 18 November 2026, Zalka · Prepared for Ricardo Khoury and the ELARD team · From Rawad and our team

Download the meeting summary (PDF)

Our aim

Support every team at ELARD with AI that works on your own knowledge.

It takes the repetitive work off your engineers. It is built to assist them, not to replace them.

It drafts and searches. Your engineers check, decide and sign.

What we discussed

Eight subjects from our meeting

Reports and studies

Starting a new report from similar past studies; you mentioned four types of studies.

Proposals and tenders

Preparing proposals and answering tenders.

Mail

Reviewing mail, and how incoming questions are handled.

Maps and receptors

Mapping the sensitive receptors around a project.

Research

Gathering information about a site or a facility: what it is, its data, its location.

Trust in the answers

How your engineers can verify what the AI brings back.

Your data

Keeping your data inside ELARD, and your concern about public AI tools.

Your people

Built to assist your engineers and analysts, not to replace them.

What we commit to

1

Your data stays in your company, on your own machine.

Nothing of yours is sent to an outside AI unless you approve it in writing, job by job.

2

Every answer drawn from your documents points to them.

Drafts stay marked as unverified until an engineer confirms each source. Before go-live we measure, on your own studies, how often answers are right.

3

The AI drafts; your people decide.

The system has no means to send mail, sign or issue a price. We show you this in the acceptance test.

4

Built to assist your people, not to replace them.

The AI takes the repetitive part of the work. Staffing decisions remain yours.

5

Your data is yours.

You can export all of it at any time.

Offline and online work

Your material never crosses the wall

Everything with ELARD material stays inside, on your own machine.

Online is optional: only research of a kind you approved in writing goes out.

A checkpoint you control holds back your documents and client names.

Without the online part, everything still works. No checkpoint can stop every copy and paste, so a short ELARD rule covers the rest.

OFFLINE: INSIDE ELARD ONLINE optional THE WALL An engineer, Technical department one login, their own page; two kinds of work, kept apart Work with ELARD material reports, studies, maps, mail: always here ELARD's AI machine: works without internet The AI drafts and searches with your material Open to this engineer the Technical space and the shared library Closed to this engineer other departments' spaces, for example Finance or HR: access by role Record of use every request, offline and online, recorded person by person Checkpoint run by ELARD checks what goes out: research of a kind you approved in writing; your documents and client names held back approved research only Online AI service laws, standards, public data about a site the answer comes back to the engineer, who checks it; it enters your library only if an engineer adds it Never crosses your library department spaces finance and HR files the record of use the online side has no route to any of it If it stops or changes its rules, the checkpoint simply closes. All the offline work continues as normal. It has no route into your library. Without the online part, only the left side exists, and everything above still works. Whether you use an online service at all, and for which jobs, we decide later, together with you.

Why your own system

Rather than a cloud subscription

01

Your data never leaves ELARD.

It stays on your own machines, at your own sites, under your own keys. No cloud contract can say that.

02

It keeps working when online services fail or change.

In 2026, online AI services have had outages, policy changes and retirements.

03

It is built around your own studies, templates and corrections,

by people who come to your office.

What to expect. A system on your own machine is narrower than the largest public assistants. Its strength is that it works on ELARD's own studies. The pilot shows you how well, before you decide.

The first job, and how we prove it

A measured pilot, before anything is bought

1

After the walkthrough

One type of study you choose, before any machine is bought.

2

Your published studies

A handful of your past studies already published, on our own test machine: nothing confidential leaves ELARD.

3

We measure

How often the answers were right, how long a first draft takes, how well it reads Arabic and scanned reports.

4

Every draft checked

Marked unverified until an engineer confirms each source. Maps drawn by your mapping software; your specialist checks.

5

You decide

The result sizes the machine and how many people it serves at once.

How the system sits inside ELARD

One system, every department

Each person has their own login.

Only the people and devices you authorise reach the system, over an encrypted private link.

Encrypted backups in three places; two named people hold the key, and we hold no copy.

Option 1. The people drawn are an illustration only; the real numbers come from your answers.

Online AI services (optional) only research of a kind you approved in writing INSIDE ELARD your departments; each person has their own login (the people drawn are an illustration) Management Business development Marketing and communications Technical departments (studies and reports) Equipment and solutions Finance and accounting HR and administration IT and the archive Encrypted private link: only the people and devices you authorise reach the system ELARD's AI machine, at your main office The AI runs on this machine; works without internet Your library past studies, templates, standards, corrections Department spaces each team sees its own work and the shared library Record of use every use is recorded, person by person Safe room for the machine cooling, two key holders; protected power; clean shutdown if all power fails Your IT contact and a deputy, trained by us; a written guide; export at any time encrypted backups Copy 1 every day Copy 2 every day Copy 3 weekly, unplugged Two named people hold the key; we hold no copy. A full restore is tested in front of you.

The IT infrastructure ELARD will need

Whichever option you choose

One dedicated AI machine

At your main office, specified after the pilot.

A safe place

A small room or cabinet with cooling, and two named key holders.

Power protection

A backup power unit at each site; a clean shutdown and restart if all power fails.

Your internet line

And a second line if possible: your other offices reach the system through it.

An encrypted private link

Only the people and devices you authorise. Tested with you before go-live.

Disks for the backups

Kept in three places of your choice.

Your IT contact and a deputy

Trained by us; every user also gets a short training.

Security updates

On a rhythm agreed in writing; every action is recorded.

Why we cannot name the machine yet. One machine, a larger professional machine, or more than one: the pilot measures the real work first, and the cost comes with our options.

Who can see what

Each person sees only what their role allows

Every request goes through the front door, which checks who you are and your role.

The AI reads only what that person may read.

Our team has no access unless ELARD opens it, and ELARD can close it at any time.

The roles are an example; ELARD's management sets the real ones before go-live, and we test them with you.

A person asks with their own login The front door checks who you are and your role, on every request The AI reads only what that person may read Your data on the machine, in your office Who can see what (an example; ELARD's management sets the real roles) Shared library past studies, templates, standards Own department their team's space Other departments' spaces Restricted files finance, HR, management, client contracts The database itself, stored encrypted An engineer or any employee A head of department for example whole team unless granted only if named Management as ELARD decides Finance and HR team their own files ELARD's IT contact runs the machine Upkeep only: accounts, roles and backups, as management approves every action is recorded, and management can review it Our team No access unless ELARD opens it, for a repair or an update every action is recorded, and ELARD can close the access at any time Employees never open the database directly. Every request goes through the front door, which checks it. Who decides: ELARD's management sets the roles and who is named for restricted files; every change is recorded. Where it is stored: on the machine's encrypted disks, in your office; backups encrypted, the key held by two named people at ELARD. can see cannot see

Two options

The same system, the same commitments

Option 1: One machine

  • One machine at your main office; the pilot tells us how many people it serves at once.
  • Encrypted backups in three places: two copied every day, one of them outside the building; the third copied weekly, then unplugged.
  • If it stops, your teams work as they do today; it is restored from the latest backup.
  • At most, the work done since the last daily backup is lost.

Option 2: Two machines

  • A second machine at a second ELARD site. On a normal day both serve your teams and share the work.
  • If one stops, the other carries everyone; your IT contact or a named deputy handles the switch, rehearsed with both.
  • A small third machine, recommended, makes the switch automatic and safe.
  • Where the second site is, and in which country, we decide together after the legal check.

You can start with the first and add the second machine later: nothing is thrown away.

Option 2

Two machines, both working

All your departments at every office, over your encrypted private link normal day: both machines serve your teams and share the work Site 1: your main office AI machine 1 serves your teams; holds the main copy protected power daily backup copies Site 2: another ELARD site AI machine 2 also serves your teams; keeps a live copy protected power site chosen with you, after the legal check live copy kept in step If one machine stops: the other carries everyone; the main copy moves in one step Recommended: small third machine at a third ELARD office; holds none of your data; makes the switch automatic and safe

On a normal day both machines serve your teams and share the work; machine 1 holds the main copy of your data and machine 2 a live copy.

Side by side

One machine or two

Option 1: One machineOption 2: Two machines
On a normal dayOne machine serves everyoneBoth machines serve your teams and share the work
If a machine stopsWork continues without the AI; the machine is repaired or replaced, then restoredThe other machine carries everyone; if it was machine 1, your IT contact or deputy moves the main copy in one step
Work that can be lostSince the last daily backupVery little: the second machine holds a live copy
Fire or theft at one siteRestored from the daily copy kept outside the buildingThe other site keeps running
What ELARD preparesOne siteTwo sites, and a third office for the small third machine
Costs, time frames, recovery timesWith our options after the walkthrough and the pilotMeasured on a real test before we commit to them

Keeping ELARD running

If this happens, your work is protected

The machine breaks

Teams keep working as today; restored from backup, or the other machine carries everyone.

Fire, flood or theft

A daily copy and the weekly unplugged copy are kept outside the building.

A deleted file or a virus

Several weeks of copies are kept; a copy is checked before it is restored.

A power cut

A backup unit carries short cuts; if all power fails, a clean shutdown and restart.

The internet line goes down

The system keeps working where it sits; a second line reduces the risk.

The office is unreachable

If it keeps its power and its line, authorised people reach it from anywhere. If not, teams work as today, or the second site serves everyone.

Someone outside tries to get in

Only authorised people and devices, over an encrypted private link; every use is recorded.

A mail hides instructions

It can mislead a draft but cannot act: the system cannot send, sign or price.

An urgent security update

Applied as soon as needed; your IT contact opens our access; every action is recorded.

An online AI service stops

Nothing in the system depends on one. It runs on your own machine.

Your IT contact is away

A named deputy, trained in the same way, and the written guide.

We are not available

You own the machine, your data and the keys, and can export everything.

Before go-live we restore a full backup in front of you and show you how long it takes; then we test it regularly.

Next steps

From us

1

Confidentiality agreement

Signed before the walkthrough.

2

Walkthrough

Of your departments, with the people you name.

3

Measured pilot

On one type of study, before any machine is bought.

4

Our options

Time frames, costs, support terms and contract basics.

5

Decide together

What we build, and how.

From you, to prepare the walkthrough

Your contact, and the colleagues who met us

People in each department and office

Where your archive is kept, and who looks after it

Who runs IT, a deputy, and your software

What must stay strictly private

Who approves the budget

Client contract and tender rules on data and AI

For option 2: which site, and in which country

A handful of published studies for the pilot

The languages of your archive, and how much is scanned

Your mail system

The two people who would hold the backup key

ELARD · Next step

Thank you

Rawad leads our team and is your contact.

Before the walkthrough, we sign a confidentiality agreement with you.

If we misunderstood anything, please tell us and we will correct it.

Download the meeting summary (PDF)
Scroll for more

Click, scroll or press the right arrow to turn the page

Turn your phone sideways for the full view

1 / 16