RAKeng

The suite

Seven products, one record carried through the whole of the work

Each part of the work has its own product. What passes between them carries the same name on both sides, so records from two products can be read together without reconciling them by hand.

How it works

One item, from the drawing to the customer

  1. Designed and released Drawings, models and parts under revision control.DocCore
  2. Reviewed and measured Marked up and measured on the drawing itself.MarkCore
  3. Built and inspected Measured against tolerance, with the evidence behind each result.QCore
  4. Sold and invoiced Quoted, ordered, invoiced and paid, in one set of books.RAKNexus
  5. In service Where each unit is, what it has cost, when it is due back.AssetCore
  6. Seen by your customer Their own equipment, documents and reports.PortalCore

Who it is for

Manufacturers, contractors, rental fleets and distributors

The suite is built for companies that design, build, install, rent or service equipment, and for those that trade it: drill bits and downhole tools, power transformers, building services, solar plants, control systems, medical devices, and multi-brand distribution. It controls the drawings, records the inspections, tracks the equipment in service, and runs the commercial side from quotation to payment.

The problem

The same product is recorded in five places, and none of them agree

A product is identified in the design office, on the shop floor, in the quality file, in the fleet register and in the field, and each keeps its own record. The drawing is in a folder on a server. The inspection sheets are in a binder or a spreadsheet. The fleet is in another spreadsheet, weeks out of date. What the equipment did in service is in an email.

None of those records can be queried together. The same part is re-designed from memory, the same failure is found twice, and one engineer is the only person who knows where anything is.

What the software does

One item, one name, at every stage

The item keeps the same identity from design, through manufacture and inspection, into service, so records made at different stages can be read together.

  • Drawn and released. Drawings, models, specifications and procedures under revision control, with the bill of material and part numbers beside them.
  • Built and proved. Inspections against the released drawing, measurements against tolerance, evidence and certificates, all carrying the unit's serial number.
  • Sold and invoiced. Quoted, ordered, invoiced and paid against the same customer and the same item, with the cost of each job in the books.
  • In service. Where each unit is, what state it is in, when it is due back, what has been done to it and what that cost.
  • Learned from. What happened in service is recorded against the same item and the same drawing, so the next revision starts from evidence.

The shape of it

Each stage has an owner

  • What is being made. Drawings, models, specifications and procedures, numbered, revised and released. Part numbers, bills of material, where-used, suppliers. — DocCore
  • The drawing under review. Marked up and measured on screen, with the markup tied to the revision it was made against. — MarkCore
  • What was built, and the proof. Inspection routings, measurements against tolerance, evidence, certificates, and the serial number of every unit made. — QCore
  • Where every unit is now. Location, state, work orders, rentals, certificates with expiry, and the cost of keeping each one. — AssetCore
  • The commercial side. Contacts, the sales pipeline, quotations, orders, invoices and payments, purchasing, stock, accounting and projects. — RAKNexus
  • Who is allowed in. One sign-in for every product, with groups mapped to roles and a second factor for administrators. — IDCore
  • What your customers can see. Their own equipment, documents and reports, and nothing belonging to anybody else. — PortalCore

The products

Four that stand on their own

Each has its own licence, its own manual, and works without the others.

Documents and parts

DocCore

The source of truth for how things are made

One register that holds every drawing, specification, record and certificate at the revision that is current, with a record of who approved it and who holds a copy. Beside them, the parts and their bills of material.

  • Drawings and 3D models in the browser, no CAD licence
  • Requests, approvals and email intake, included
  • Transmittals, and the responses to them
  • A tamper-evident audit trail
What DocCore does →
Quality

QCore

Proof that what you built is what you drew

Inspection routings, measurements against tolerance, photographic evidence, certificates of conformance, and the serial number of every unit you make. Instruments carry their calibration state, and a reading taken with an overdue instrument is marked as such.

  • A phone app for the shop floor that works with no network
  • Measurements shown on the design model
  • Sensors and cameras on the machine, through an edge device
  • Signatures gated by the rules
What QCore does →
Asset management

AssetCore

Every serialised unit, all of its life

Where each unit is, what state it is in, what has been done to it, when it is due back and what its last repair cost. Work orders with parts, labour and checklists. Rentals with delivery notes, certificates and utilisation. Consumables with a minimum level.

  • A movement ledger chained so that a change shows
  • Preventive maintenance on hours, cycles or the calendar
  • Certificates with expiry, so nothing unfit ships
  • A QR label that opens the unit's record on a phone
What AssetCore does →
ERP and CRM

RAKNexus

The commercial side, in English and Arabic

An ERP and CRM for companies in the Gulf and Jordan, installed on your own server or in the cloud, in English and Arabic. Contacts, the sales pipeline, quotations and orders, invoicing and payments, purchasing, inventory, manufacturing, point of sale, accounting, projects, and VAT for KSA, the UAE and Jordan.

  • Tax invoices in ZATCA format, with QR code
  • Multi-company and multi-currency
  • Screens, fields and workflows changed without code
  • Bilingual PDF documents
What RAKNexus does →

ABAR Drilling Analytics is a separate line, not part of the suite. It is drilling analytics and engineering software for oil and gas.

With DocCore

Three companions on DocCore's licence

IDCore is included. PortalCore and MarkCore are optional, switched on when you want them.

Optional

MarkCore

Mark up the drawing, not a printout of it

Open a drawing, measure on it to scale, mark it up and review it with somebody else on the same sheet at the same time. The markup stays attached to the revision it was made against.

  • Measure to scale, in the drawing's own units
  • Two people on one sheet, live
  • Every markup tied to the revision it was made on
What MarkCore does →
Optional

PortalCore

What your customers can see for themselves

Your customers sign in and see their own equipment on hire, their own documents and their own reports, and nothing belonging to anybody else. Editable originals stay yours; they get the issued copy.

  • Branded with your name
  • Customer requests land in your engineers' queue
  • Licensed through DocCore, switched on when you want it
What PortalCore does →
Included

IDCore

One sign-in for the suite

One account per person and one sign-in for every product, with groups mapped to roles per product and a second factor required for administrators.

  • One sign-in for every product
  • Two-factor, required for administrators
  • Included with DocCore
What IDCore does →

What it changes

What changes, day to day

Quote from evidence

What this design did, in these conditions, across everything you have shipped.

Prove quality without a hunt

The process record, the measurements, the calibration and the signature are one click from the serial number, years later.

Know your fleet

What is out, what is due back, what is in the workshop, and what each unit has cost to keep.

Know what each job earned

The quotation, the purchases, the hours and the invoice, in one set of books.

Design the next one properly

Failures show up as a pattern on the model, in the positions your designer named.