Engineering management

One record for every part, BOM and change.

Altrevo Systems keeps part numbers, bills of materials, projects, planning, purchasing and inventory in one place, so design, purchasing, stores and the build team all work from the same numbers, with no more copying between spreadsheets.

Altrevo Systems
  • Replaces the spreadsheets
  • Every change on record
  • Tailored to your business

Your operation shouldn't run on copy and paste.

Many engineering companies still run their operations on a patchwork of Excel files: a BOM here, a part list there, a purchasing tracker, a stock sheet, a build checklist. Each one repeats the others, and people keep them in step by hand. It works, until a wrong revision reaches the build floor.

  1. Copy and paste between files

    The same part number, description and quantity are pasted into the BOM, the order tracker and the stock sheet.

    Entered once, used everywhere.

    A part, its revision and its quantities live in one record that every team reads from.

  2. Visual checks

    Two spreadsheets side by side, scrolling line by line to spot what changed.

    Changes tracked, not spotted.

    Every edit is recorded with who and when, and differences between revisions and baselines are shown for you.

  3. Typing the same data again

    Delivery dates from purchasing re-typed into the BOM; stock counts re-typed into the build plan.

    Data flows between teams.

    Orders, stock and dates feed the BOM, the plan and every dashboard automatically.

  4. Which file is the right one?

    v7_FINAL, v7_FINAL_JM, v8_draft. Mistakes show up on the build floor.

    One version of the truth.

    Everyone works on the same live record, with edit rights by role, so the BOM on the shop floor is the BOM in engineering.

Less time keeping spreadsheets in step. More time engineering.

From first sketch to release

Spreadsheets drift apart the moment a second person opens them. Altrevo Systems keeps one record per part and lets every team see it their way.

  1. 01

    Number

    Create the part once.

    Every part gets a number like T20-00102 (project, system, sequence) the moment it is created. Duplicate manufacturer part numbers are caught before they are saved.

  2. 02

    Structure

    Build the BOM.

    Indented or flat, typed like a spreadsheet or pasted straight from Excel. An assembly used in several products is edited once.

  3. 03

    Build

    Order, pick and assemble.

    Purchase orders are raised and stock is tracked in the same system as the BOM. Stores get pick lists checked against the shelf, and the schedule shows which parts will arrive late.

  4. 04

    Change & release

    Control every change.

    Change requests, documents and release gates are built on the same parts and BOMs, so nothing is released with a change still open.

One platform, fourteen modules

Fourteen modules on one data model, all under one roof. Part numbers, BOMs, projects, purchasing, inventory, change control, documentation, release and quality share the same records, so there are no separate tools to keep in step, a change request or a failure mode always points to a real part number, and every role sees what matters to it on its own dashboard.

Group 1

Engineering data

M-01

Part creation

One parts register with automatic numbering, revisions and the history of every change.

  • TTT-NNNNN numbers, safe when many people create parts at once
  • Revisions A to Z, each kept side by side
  • Duplicate manufacturer part numbers caught on entry
  • Batch edit with preview and undo
M-02

Bills of materials

Indented and flat BOMs with design, procurement and build columns on the same lines.

  • Shared assemblies: edit once, used everywhere
  • Paste from Excel, import and export CSV
  • Make, buy, part-in-assembly or carry-over, per project
  • Two people on one cell: the conflict is shown, never overwritten
M-03

Documentation

Drawings, models, specifications and test reports held against the part revision they describe.

  • Document numbers and revisions linked to parts
  • Draft, in review, released, superseded
  • Re-issued through a change request
  • Where-used: every BOM and project a document touches
M-04

Engineering change requests (ECR)

Propose, assess, approve and carry out a change, with its impact worked out from the data.

  • Affected parts, BOMs and projects found from where-used
  • Open orders and stock flagged: use up, rework or scrap
  • Approval by the roles on each affected project
  • New revisions, tasks and documents issued on approval
Group 2

Projects & operations

M-05

Projects

Every project on one line, with its own team, roles, edit rights and dashboards.

  • Status at a glance: late, at risk, on track
  • Weekly page, build readiness and design board
  • Edit rights by role and column group
M-06

Planning

Project stages and delivery dates, measured against when the parts actually arrive.

  • Stages: concept, design, build, test, handover
  • Parts arriving late, counted against the build start
  • Readiness and float to the tightest part
  • Workload by person and role
M-07

Tasks

Who does what by when, with evidence and two-step closing.

  • Tasks, inbox, @mentions and a daily reminder
  • Pick lists sent to stores in shelf order
  • My week: what each person owes, in one place
M-08

Purchasing

What every project still has to buy, and where each order stands.

  • Purchase orders, RFQs and approvals raised in the app
  • Buying board: overdue and not booked in
  • Parts needed, combined across projects
  • Open orders brought across once at go-live, so nothing is lost
M-09

Inventory

Stock, shelf locations and shortages for every part, managed in the same system as your BOMs and orders.

  • Built in, so there is no separate stock system to keep in step
  • Stock and location shown on every BOM line
  • Pick lists checked against what is actually on the shelf
  • Shortages flagged before the build starts
  • Goods in, picks and returns recorded as stock movements
Group 3

Release & quality

M-10

Project release

Release gates for each stage, checked against the real state of the project, then frozen as a baseline.

  • Gate checklist: BOM numbered, parts and documents released, no open ECRs
  • Baseline: BOM, revisions and documents frozen together
  • Compare any two baselines line by line
  • Release package for manufacturing and suppliers
M-11

CCAR

Raise, contain and close corrective actions, each tied to the part and BOM where the issue was found.

  • Containment, root cause, action, verification
  • Owners and due dates as tasks
  • Raises an ECR when the design must change
M-12

DFMEA

Design failure modes built from the BOM structure, so every item can be analysed.

  • Severity, occurrence, detection and action priority
  • Actions tracked to closure as tasks
  • Reviewed when an ECR changes the part
M-13

Process FMEA

Failure modes for each manufacturing and assembly step, linked back to the design analysis.

  • Process steps per assembly
  • Rating scales shared with DFMEA
  • Feeds corrective actions and change requests
Across everything

Role dashboards

M-14

Role dashboards

Every role opens on a dashboard built around its own work: what is due, what is late and what needs a decision.

  • Design: parts to number, drawings to release, changes to review
  • Procurement: parts to order, orders overdue, deliveries due
  • Stores: pick lists, shortages and goods expected
  • Quality: open CCARs and FMEA actions
  • Project leads and management: status, readiness and risk across projects
  • Tailored to your roles and KPIs on request

Change control, connected end to end

When a part changes, everything that depends on it should know. The change request, documentation and release modules use the links already in the system — where a part is used, what is on order, what is on the shelf — so the impact of a change is worked out, not guessed.

  1. 01

    Request

    Raised from a part, a BOM line, a task, a CCAR or an FMEA action.

  2. 02

    Impact

    Every BOM and project using the part, open PO lines, stock on the shelf, documents and FMEA rows to review.

  3. 03

    Approve

    Signed off by the roles on each affected project, every decision on the audit trail.

  4. 04

    Implement

    New revisions (A → B), tasks for each team, documents re-issued, purchasing told what to change on order.

  5. 05

    Release

    The project's next release gate checks that no change is left open, then freezes the baseline.

Delivered as your own installation

Each customer gets a separate installation of Altrevo Systems with its own database, on its own servers. Nothing is shared with anyone else.

Your installation

Runs on your Linux server with Docker and PostgreSQL, behind your firewall. IT gets an install guide, nightly backup and restore steps, and versioned upgrades.

Runs on
Linux · Docker · PostgreSQL
Sign-in
Microsoft Entra ID or emailed code
Upgrades
Versioned releases with notes

Your data

Your parts, BOMs and history stay in your database. Every change is on record, and your data can be taken out at any time.

Audit trail
Every change, who and when
Permissions
By role and column group
In and out
Excel and CSV import and export

Built around the way you work.

No two engineering businesses run the same way. You have your own numbering scheme, your own approval chain, the columns your team cares about and the systems you can't switch off. Altrevo Systems adapts to your process, not the other way round.

01

Configured to fit

Part-number format, roles, project stages, columns and edit rights set up for your business from day one.

02

Extended on request

Need a field, a report, a dashboard or a whole workflow that isn't there yet? Tell us, and we'll build it into your installation.

03

Start from your own data

We bring your existing part lists, BOMs, open orders and stock across from your spreadsheets once, at go-live, so the app picks up exactly where you left off.

04

Grows with you

Your changes arrive as tested, versioned updates, so your tailored version keeps improving along with the core product.

From your request to your installation

  1. 01

    Tell us how you work

    Walk us through your process, your spreadsheets and the rules that matter to you.

  2. 02

    We propose the fit

    Configuration or a new feature, scoped and agreed with you.

  3. 03

    We deliver it

    Built, tested and installed in your Altrevo Systems as a versioned update.

Talk to us about your requirements

See it on your own BOM.

Send us a BOM, a part list or the spreadsheets your team runs on today. We'll show you how they look in Altrevo Systems, and what we would tailor for you.

We use your details only to reply to you. Privacy notice

Prefer email? contact@altrevosystems.com