Skip to content

AIMS Adept

One connected platform for asset integrity

Inspection, risk, maintenance, reliability, and spare parts share one asset record — so a finding in the field can still be trusted when the work is planned.

Explore featuresRequest a demo

by Petropardaz Arvand · One Step Ahead

7

Connected modules

10

Steps in the RCM study

API 581

Style of risk method

EN + FA

Working languages

How the modules connectTechnical specsIntroduction

Introduction

AIMS Adept is an enterprise platform for asset-intensive industries — oil and gas, petrochemicals, power, utilities, manufacturing, and heavy industry. It follows the asset from registration and inspection through risk analysis, preventive maintenance, reliability engineering, root-cause investigation, and spare-parts standardization. The modules are not separate products. They share one technical foundation, so information created in one place supports decisions everywhere else.

Why the modules belong together

A thickness reading should still be visible when risk is calculated. A justified maintenance task should become a job card, not a report that sits on a shelf. A spare part should be named the same way the warehouse and the planner both understand. AIMS Adept keeps that chain intact, with approvals, history, and engineering judgment still in human hands.

Highlights

  • One asset identity for inspection, RBI, maintenance, and spares
  • AI prepares drafts; engineers review and approve them
  • English and Persian, with configurable scope for each organization

How the work connects

Each module hands something useful to the next, instead of starting from a blank spreadsheet.

  1. 01

    Core

    The shared asset register

  2. 02

    Inspection

    Findings with a place and a history

  3. 03

    RBI

    Risk you can defend

  4. 04

    PM

    Job cards people can run

  5. 05

    RCM

    Strategy, with expert control

  6. 06

    RCA

    Evidence before opinion

  7. 07

    Spares

    One name for each part

Core data and drawings give inspection its context. Inspection strengthens risk. Risk sets priorities. RCM justifies the work, PM makes it executable, RCA learns from what failed, and standardized spares make the job possible.

Features & capabilities

The order follows the engineering path: know the asset, inspect it, judge the risk, and turn that judgment into work.

Foundation

Core — a trusted record for every asset

Facilities, systems, equipment, maintainable parts, documents, and drawings live in one hierarchy. Departments stop keeping their own version of the asset register.

  • Business category → installation → plant or unit → system → asset → subsystem → maintainable part
  • Classes and class types for consistent naming and coding
  • Shared manufacturers, units, and classifications

A plant procedure can sit on an installation, a drawing on an asset, and a thickness reading on the part it actually belongs to.

Documents and engineering markup

Drawings, datasheets, manuals, reports, and photographs stay attached to the level of the plant they describe. The markup tool is for engineering annotation, not text formatting.

  • PDF, Office, images, CSV, SVG, DXF, and supported DWG
  • Thickness and condition locations, corrosion loops, and inventory groups
  • The source drawing is kept; an export is a new flattened copy

Inspection that becomes integrity evidence

Results are structured records, tied to the asset and, where it helps, to a marked-up drawing. Thickness surveys calculate minimum, maximum, and average readings, and flag replacement status.

  • Checklists for vessels, piping, tanks, tube bundles, and relief devices
  • Damage mechanisms from thinning and CUI through cracking and HTHA
  • A direct link into the RBI equipment family

The selected part has to belong to the asset being inspected, so a reading cannot quietly land on the wrong equipment.

API 581 style

Risk-based inspection you can explain

Probability, consequence, damage factors, and inspection effectiveness sit in one auditable workflow. Generic failure frequency, damage factors, and management-system factors feed the probability of failure.

  • Vessels, piping, tanks, tube bundles, and relief devices
  • Area and financial consequence, with configurable risk matrices
  • Batch calculations, validation reports, and inspection plans

Missing or inconsistent data is visible before anyone accepts a risk result.

Preventive maintenance as executable work

Reusable job cards describe the task, the skill, the tools, the parts, and the interval. Approved cards are then assigned to real assets, with the hierarchy and equipment class checked first.

  • Time-based, counter-based, or eventual work
  • Intervals from minutes through years, including shutdown needs
  • Spare parts taken from the governed catalogue

The path from reliability to the workshop is explicit: failure mode, task, package, job card, asset assignment.

Experts decide

RCM with AI assistance and human gates

Studies follow the Moubray RCM II sequence, from asset identification through implementation. Documents attached to the study can help the assistant draft the next step. Nothing moves forward until the previous step is approved.

  • Ten steps, from functions and failure modes to task packaging
  • Drafts stay drafts until a reviewer accepts them
  • Every task traces back to the failure and consequence that justified it

The assistant is asked to separate documented facts from assumptions, and to say when information is missing.

Root-cause analysis with evidence attached

Investigations move through problem definition, evidence, cause analysis, solutions, and a check on whether the action actually worked. Several recognized methods are available in the same case.

  • Fishbone, Five Whys, cause mapping, Apollo-style analysis, and fault trees
  • Conflicting evidence blocks a cause until it is resolved
  • Actions stay tied to confirmed causes, then get an effectiveness review

Spare parts with one engineering name

The spares module is a governed catalogue, not a stock count. Classification, attributes, and codes reduce duplicate materials and vague descriptions.

  • Segment → family → class → concept, with an identification guide
  • AI proposals for class, attributes, and naming — applied only after approval
  • Branded datasheets, and quantities on PM job cards

Technical specifications

PostgreSQL and Django

A modular web platform on Django, Django REST Framework, and PostgreSQL, with browser access for grids, forms, dashboards, and workflows.

Security by design

Role and action permissions, business-category isolation, idle-session expiry, CSRF protection, HTTPS in production, and JWT with refresh-token rotation for the API.

AI you can change

OpenAI, Anthropic, Google, Azure, Cohere, DeepSeek, Qwen, Groq, GitHub Models, local models, or a compatible endpoint. Output is stored as a proposal, with the prompt and the review kept.

Built to be configured

Modules can be switched on or off. Branding, risk references, classifications, and English or Persian can follow the organization without changing the engineering model.

Import, export, and audit

Standard Excel exchange, a versioned REST API with OpenAPI docs, and a history of who changed what, when, and under which business category.

Room to grow

Background jobs for risk and AI work, optional Redis and Celery, structured logging, Prometheus-compatible monitoring, and Docker-based deployment.

See the chain in a live walkthrough

Request a temporary account, or a guided pass from the asset register through risk, maintenance, and spare parts.

Request a demoDownload catalog