Say what your business is made of: customers and orders, or sites, machines and jobs, how they connect, and the numbers you watch. From that one description, Evalu8 Pro builds your screens, reports and alerts, connects the systems you already use, and keeps watch on every number and reading. Its AI works from the same description, so it knows what a customer or a machine means to you. Your team makes the calls.
No code to start: pick a ready-made model and adjust it with simple forms. Technical teams can work on the model file directly.
In the model
An order is a sale to a customer.
Each one is known by its number.
It records a date, a status and a total.
Every order is placed by a customer.
The list shows number, date, status and total.
In the model
A sensor posts readings from the equipment it is mounted on.
Each one is known by its device ID.
It reports vibration in mm/s. Raise an alert if it goes quiet for 15 minutes, or reads above 7.1.
It reports temperature in °C. Raise an alert above 85 °C.
Your ERP, your maintenance software and each equipment maker’s portal keep their own lists, so nobody is quite sure which numbers are right.
Someone exports, copies and pastes each month, and the answer is out of date by the time it arrives.
Building your own takes months, and every change after that is another project.
Evalu8 Pro keeps one description of your business, the model, and builds everything from it. Your tools keep doing their jobs, their data finally joins up, and AI has something solid to work from.
Everything in between runs by itself: data fetched from your other systems, numbers worked out, readings checked as they arrive, files read and likely causes suggested. Your team steps in where a decision is needed.
Pick a ready-made model or start from nothing, then add what you track with simple forms. Every change is checked before it is saved.
Customers · Orders · Products · Suppliers
Link the systems you use through their APIs and databases, upload spreadsheets and PDFs, and let devices send their readings. Everything lands in the same model.
Warehouse system · maintenance API · PLC historian · statement.csv
Screens, numbers, alerts and documents are ready straight away and update as data arrives. Readings and numbers are watched, likely causes come with their reasons, and AI answers questions and proposes better rules.
Dashboard · Monitoring · Ask · Improvements
Bank matches, likely causes and proposed changes wait for a person. Approve them in a click, or press a control and Evalu8 Pro sends it to the equipment and checks the readings follow.
Approve · Confirm · Run · Undo
Your ERP, warehouse system, maintenance software and equipment each have their own API, database or export, with their own names for everything. For each one, the model holds a connection rule: where to fetch from, which of its fields mean what in your business, and how often to check. Evalu8 Pro does the fetching, paging and matching, so records from different systems arrive as the same customer, order or machine.
The systems you use
Your model
One machine, however many systems know about it.
What you get
APImaintenanceevery 60 minutes
wo_numberwork_order.numberequipment.tagwork_order.assetraisedwork_order.opened_atstatework_order.status4 pages386 work orders12 placeholdersSynced 4 minutes ago
| Equipment | Geared motor, 4 kW | Asset register · file |
|---|---|---|
| Line | Outbound conveyor 3 | Warehouse · API |
| Vibration | 3.4 mm/s · 2 min ago | Sensors · readings |
| Last service | Lubrication · 12 Sep | Maintenance · API |
| Since service | 2,140 running hours | PLC historian · database |
| Next service | Overdue by 140 hours | Calculated |
Nothing in Evalu8 Pro is written for one kind of business. Each capability reads its own part of the model, so adding one is a matter of describing it rather than building it. Your technical team can read every line; you never have to. Most examples are shortened from the ready-made models, and some are shown in plain English.
objects
Customers, orders, sites or machines. Each one gets a list, a page per record, forms to add and edit, and an API.
"order": {
"key": "number",
"properties": {
"total": "number"
}
}relationships
An order belongs to a customer; a sensor is mounted on a drive. Links show on every page and follow your data in from other systems.
"customer": {
"edge": "PLACED_BY",
"direction": "out"
}integrations
Where to fetch from, which fields mean what, and how often. Evalu8 Pro does the fetching, paging and matching.
"shop": { "every": 60,
"generated_objects": {
"order": {
"api_url": "https://…" }}}formulas
Totals and tax worked out whenever a record is saved, like a spreadsheet, and never run as code.
"subtotal":
"sum(lines.line_total)",
"total": "subtotal + tax"kpis
Revenue, minutes stopped, work orders open: a few plain steps, with targets and alerts.
Revenue is the total of every order that is not cancelled. Aim to grow it 5% a month, and alert when it falls by a fifth.
document
An editor, a preview and a PDF, numbered your way.
"title": "Invoice",
"number": "INV-{0000}",
"party": "customer"reconcile
Bank payments matched to the invoices or bills they pay, for a person to approve.
A payment in settles an invoice when its reference, amount and customer agree. Once approved, the invoice is marked paid.
telemetry
Live charts, and alerts when a sensor goes quiet or out of range.
"vibration": {
"unit": "mm/s",
"silent_after": 15,
"high": 7.1
}diagnoses
Rules that weigh the evidence and suggest a cause for a person to confirm.
When a drive’s vibration has been climbing for a day, weigh its temperature, its current and the hours since its last service, and suggest a cause.
aims
The targets you hold yourselves to, and what matters more than what, written in your own words. The AI reads it whenever it works for you: answering questions, suggesting numbers to track, and proposing better rules.
Keep the outbound lines moving: no stoppage longer than 30 minutes, and every drive serviced before it fails. A missed fault costs us a morning; a false alarm costs an engineer an hour.
The two ready-made models run on exactly the same platform, with the same screens, connections, numbers and monitoring. All of the difference is in the model, so yours can describe whatever your business actually does.
Made of
Describes
An invoice with VAT worked out, and how bank payments settle invoices and bills.
Watches
Revenue, margin, money owed each way and net cash flow.
Made of
Describes
Sensor readings with alert limits, which sensor was on which machine and when, the hours left until each service, and why a drive’s vibration might be rising.
Watches
Stoppages, minutes stopped, open work orders, and minutes over the vibration limit.
Start with nothing and let each file and connection add the objects and fields it brings. Or describe what you actually run: projects and timesheets, vehicles and inspections, members and bookings.
The screens, connections and numbers come from the same platform either way.
Start a modelEach one is a model on this same platform, with the connections, hardware and know-how to put it to work.
Sensors, a satellite link and every reading watched, so you know which wells are flowing and what to fix next.
Water monitoring →Invoices, bills, bank matching and who owes what, with the repetitive work done for you.
Business admin →Plant data joined up, drift caught early, and fixes approved by people while your control system stays in charge.
Process monitoring →Software shaped exactly to how you work, that changes as quickly as you do.
Bespoke →Every number on the dashboard is a few plain steps: which records, which relationship, what to add up. Anyone can see how it was worked out and change it.
Set targets and milestones, and get an alert for a sharp change, a threshold crossed or a steady decline.
Order revenue
Invoiced
Target: grow 5% a monthMet
The trading model describes which payments settle which invoices and bills. From that, Evalu8 Pro weighs each bank payment against each open invoice: the reference on the line, the amount, the customer’s name and the dates.
A person approves each match, or every strong one at once. The invoice is marked paid, your figures move straight away, and any match can be undone.
The rule in the model, in plain English
A payment in settles an invoice when its reference, amount and customer agree. Once a person approves, mark the invoice paid on the payment’s date.
FASTER PAYMENT OAK & WAX LTD INV-0142
+£960.00
| Invoice number on the bank line | |
|---|---|
| Amount matches to the penny | |
| Only open invoice for that amount | |
| Customer name on the line | |
| How sure | Strong match |
ApproveNot a match
Describe what a device measures and how often, and its readings arrive through the API: thousands at a time, safe to resend, with late ones slotting into place. You get live charts, and an alert when a sensor goes quiet or out of range.
Diagnoses are described in the model too. When a drive’s vibration starts to climb, Evalu8 Pro weighs the evidence (its temperature, its current draw, the running hours since its last service) and suggests a likely cause for an engineer to confirm. Every answer is kept with the readings behind it.
Drive motor CV3-M2Vibration, last 7 days
Vibration at the drive-end bearing, mm/s
Likely causeBearing wear
ConfirmCorrect it
Write down what you are aiming for, in your own words. Ask, the built-in assistant, weighs every answer against it, and one button has it review how the whole site is doing.
Every diagnosis your engineers confirm or correct is kept with the readings behind it. Every week if you choose, or whenever you ask, Evalu8 Pro studies that history against your aims, tries changes to its own rules, alert limits and numbers, and tests each one against the answers your team has already given.
The changes that hold up are put to you, at most three at a time, each with its test result and the cases it would have called differently. A person applies each one, any of them can be undone, and Evalu8 Pro reports how it has done since.
What you are aiming for, in your words
Keep the outbound lines moving: no stoppage longer than 30 minutes, and every drive serviced before it fails.
Proposed by this week’s study
Count recent work as a sign of misalignmentWhen vibration climbs on a drive serviced in the last 400 running hours, rather than 200, weigh misalignment or looseness before bearing wear.
Agrees with your engineers’ past answers
ApplyDismissCan be undone
Software shaped to your business, without a software project.
One model as the source of truth, in a format you can review.
Interoperability for your customers, without a custom integration for each.
General-purpose AI has to guess what a customer, an order or a machine means to you. Evalu8 Pro’s AI works from your model: your names, how things connect, your numbers and what you are aiming for. It maps files onto your fields, reads bills from photos, answers questions with the records behind them, suggests numbers worth tracking and proposes better rules from your team’s answers. Everything it produces is checked against the model, and a person decides what changes.
The import mappings, KPIs and rule changes AI suggests are data the platform reads, like everything else in your model. None of it can run as a program.
Every import shows what will be added and changed, and every connection can be tested first. Nothing is written until you say so.
Bank matches are approved, diagnoses confirmed and improvements applied by someone on your team, and Evalu8 Pro records who and when. An applied improvement can be undone.
Connections are for bringing data in: API connections request it, and database connections are read-only, whatever the query says.
API keys and passwords are encrypted, kept out of the model, removed from any error message, and only the account owner can change them.
Download the whole model at any time, and read every record, number and reading through the API.
Plain-English guides for the people who run operations: describing a business so software and AI can work from it, joining up its systems, and monitoring that people trust.
Why automation and AI stall without a picture of your business, what a model is in plain English, and how to write yours in an afternoon.
How to join up an asset register, maintenance system, historian and sensors around the same machine, and what to check before you trust the result.
Alerts that mean something, likely causes with their reasons, fixes a person approves and readings confirm, and rules that improve from the answers.
Start from a ready-made model, connect a system or upload a file, and see the software Evalu8 Pro builds from it.