All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Product Lifecycle Mgmt (PLM) · Available now

Carry reviewed design changes into controlled production.

Product Lifecycle Mgmt (PLM) runs the handoff from product design evidence to engineering change and inspected production output. Product Engineer submits product-linked files with their revision and document type.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewEngineering change drafts
Product Lifecycle Mgmt (PLM) · Engineering changes

Engineering change drafts

review waits for the product engineer

New engineering change
Engineering changes in view
6
Draft
6
IdChange numberProductFrom revisionTo revisionEffective date
WO-2026-0418EC-83650Cedar control board, revision CRev ARev B11 Oct
ECN-2026-012EC-90750Tern antenna kit, roof mountRev BRev C15 Oct
SO-2026-0831EC-49178Tern gateway, industrial LTERev CRev D15 Oct
PO-2026-0226EC-24960Cedar control board, revision CRev DRev E22 Oct
LOT-26-1048EC-14490Tern gateway, industrial LTERev ERev F24 Oct
6 of 6 records
WO-2026-0418Engineering changes · EC-83650
Draft
ProductCedar control board, revision C
From revisionRev A
To revisionRev B
Effective date11 Oct
Review changeEC-83650 · WO-2026-0418

Engineering Reviewer decides whether the submitted product revision may proceed.

Waiting for Engineering Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
17
Saved views
16
Roles with set permissions
8
Reports and dashboards
8
Features

Design and production in view

Every feature works on the same records. Pick one to see the screen your team works in.

Design documents

Keep product-linked design files, revision identities and reviewer evidence together.

  • Product identity
  • Document identity
  • Reviewer assignment
  • Design documents
  • Items
  • People
  • Users
Explore design documents
OverviewDesign document register
Product Lifecycle Mgmt (PLM) · Design documents

Design document register

Design documents

New
IdProductRevisionDocument typeFileApproved by
WO-2026-0418Marsh mounting bracket, stainlessRev AAssembly drawingalder_sensor_assembly_rev_c.pdfClara Rousseau
ECN-2026-012Marsh mounting bracket, stainlessRev BBill of materialscedar_board_bom_rev_d.xlsxNoah Kim
SO-2026-0831Marsh mounting bracket, stainlessRev CTest proceduretern_gateway_test_rev_b.pdfSofia Haddad
PO-2026-0226Tern gateway, industrial LTERev DInspection planmarsh_bracket_drawing_rev_a.pdfNoah Kim
LOT-26-1048Marsh mounting bracket, stainlessRev EManufacturing instructionalder_housing_inspection_rev_e.pdfPriya Nair
6 of 6 records
WO-2026-0418Design documents · DD-46529
ProductMarsh mounting bracket, stainless
RevisionRev A
Document typeAssembly drawing
Filealder_sensor_assembly_rev_c.pdf
Approved byClara Rousseau
Example screen with sample data
Process

From design change to accepted output

Design change to accepted output ships ready to use. 2 steps need a named approval before the work moves on: Review change (Engineering Reviewer) and Accept output (Quality Inspector).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Capture design

    Submit the product-linked design revision with its file and responsible reviewer.

    WO-2026-0418EC-83650 · Product Engineer
    Capture designBy Product Engineer
  2. Review change

    Review the attributed revision proposal before authorizing implementation.

    WO-2026-0418EC-83650 · Engineering Reviewer
    Review changeBy Engineering Reviewer
    ApprovalEngineering Reviewer decides whether the submitted product revision may proceed.
  3. Implement change

    Apply the approved engineering scope and inspect the operating handoff.

    WO-2026-0418EC-83650 · Production Planner
    Implement changeBy Production Planner
  4. Release production

    Check approved demand, available resource and feasible planned work.

    WO-2026-0418EC-83650 · Production Planner
    Release productionBy Production Planner
  5. Record production

    Capture attributed interval evidence and route output to quality review.

    WO-2026-0418EC-83650 · Operator
    Record productionBy Operator
  6. Accept output

    Release inspected pending output and reconcile accepted finished goods.

    WO-2026-0418EC-83650 · Inventory Controller
    Accept outputBy Inventory Controller
    ApprovalQuality Inspector decides which inspected pending output may be released.
Inside a record

Plan your system connections

Open any engineering change to see the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Product, From revision, To revision and Effective date.

  2. 2
    Linked records

    Records linked to this engineering change.

  3. 3
    Who works on it

    Admin, Product Engineer and Engineering Reviewer, each with their own permissions.

  4. 4
    Process stages

    Prepare change and Implement change, with the role that acts.

  5. 5
    Approvals

    Review change and Accept output, with who decides.

Engineering change draftsWO-2026-0418
Product Lifecycle Mgmt (PLM) · Engineering changes

WO-2026-0418

Cedar control board, revision C · Draft

Log activity
1
Record details
ProductCedar control board, revision C
From revisionRev A
To revisionRev B
Effective date11 Oct
3

Who works on it

  • AdminManage Users, People, Items, Parties, Resources
  • Product EngineerManage design documents, engineering changes
  • Engineering ReviewerView design documents, engineering changes, Items, People, work…
4

Process stages

  • Prepare changeProduct Engineer
  • Implement changeProduction Planner, Product Engineer
5

Approvals

  • Review changeEngineering Reviewer
    Approved
  • Accept outputQuality Inspector
    Waiting
Example screen with sample data
Approvals

Decide changes and accepted output

OverviewApprovals
Product Lifecycle Mgmt (PLM) · Overview

Approvals

Signed in as Engineering Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • EC-51493Rev A
    Alder sensor housing, blackRequested by Admin
    Review2dActions
  • EC-44709Rev B
    Alder field sensor, 24 VRequested by Admin
    Review1dActions
  • EC-14324Rev C
    Marsh mounting bracket, stainlessRequested by Admin
    Review4dActions
  • EC-19126Rev D
    Tern gateway, industrial LTERequested by Admin
    Review4dActions

Who approves what

DecisionApprover
Review changeReview the attributed revision proposal before authorizing implementation.Engineering Reviewer
Accept outputRelease inspected pending output and reconcile accepted finished goods.Quality Inspector
Approve design documents, engineering changesEngineering Reviewer
Approve BatchesQuality Inspector
4 approval rules · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Product Lifecycle Mgmt (PLM) to the work that is theirs. Pick a role to see what it starts with.

Admin

Configures access and reference data while engineering and quality owners retain their decision responsibilities.

  • Manage Users, People, Items, Parties, Resources
  • View design documents, engineering changes, work orders, inventory balances, material issues, production logs, Batches, Orders, order lines, purchase orders, purchase lines, exchange rates
Reports

Explain revision and production state

Compare design state, material postings and production evidence without confusing them with acceptance.

Overview
Product Lifecycle Mgmt (PLM) · Overview

Product Lifecycle Mgmt (PLM) dashboard

This quarter

Work orders in view
6
Total planned quantity
2,480
Released
2
In progress
2

Engineering changes by status

How far records got this quarter

StageReachedStep
Draft31
Review1342%
Approved323%
Implemented133%

Number of engineering changes by status

Sample counts per stage

0
-50Draft
-20Review
0Approved
-40Implemented
-60Rejected
Example screen with sample data
  1. 01Design revisions by product

    Which product revisions have submitted files and responsible reviewers? Inspect the deciding evidence when reviewing approval.

  2. 02Engineering change status

    Which requests await Review, remain Approved or reached Implemented, and which revision transition does each describe?

  3. 03Production plan by resource

    Group work orders by Resource and Status using planned start, planned end and planned quantity alongside resource capacity minutes per day to review planned intervals and resource context.

  4. 04Free stock by lot

    What remains after reservations are subtracted from on-hand quantity for each item, location and lot?

  5. 05Posted material usage

    Sum Quantity from material issues with Status Posted by work order, Item and lot number, displaying Draft and Reversed records separately for follow-up.

  6. 06Recorded good and scrap output

    What did the operator report during a valid interval for the work order?

  7. 07Batch disposition and expiry

    Which lots remain Pending, Held or Rejected, and which dates need attention?

  8. 08Outstanding supplier quantities

    What remains between ordered and received quantities on each supplier commitment?

Controls

Keep stock effects traceable

Each stage of design change to accepted output names the role that acts and the status it records, so a change is never anonymous.

OverviewDesign change to accepted output
Product Lifecycle Mgmt (PLM) · Process

Design change to accepted output

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
2
Roles involved
6
Tables touched
12
Prepare change
Product Engineer
StatusDraft → Review
RecordsEngineering changes
Review changeApproval
Engineering Reviewer
StatusReview → Approved
Implement change
Production Planner, Product Engineer
StatusApproved → Implemented
RecordsEngineering changes, Work orders
Design change to accepted output
  1. Start
    Review design evidenceEngineering Reviewer
    Engineering Reviewer
  2. Step
    Prepare changeDraft → Review
    Engineering changes
  3. Approval
    Review changeReview → Approved
    Engineering Reviewer
  4. Step
    Implement changeApproved → Implemented
    Engineering changes
  5. Step
    Release productionDraft → Released
    Work orders
Example screen with sample data
AI agent

Prepare the next action with Proto

Prepare product-linked evidence, explain operating exceptions and rehearse the permitted workflows with Proto.

It can

  • Product Engineer: List Draft changes by product and revision transition and prepare source evidence for review.
  • Engineering Reviewer: Gather a Review request and its design context for the deciding person to inspect.
  • Production Planner: Find Draft work whose demand, resource or dates need attention before release.
  • Inventory Controller: Explain free stock for the intended item, location and lot before posting an issue.

Stays with a person

  • Proto works through the configured person's authority.
  • Engineering Reviewer decides the design change and Quality Inspector decides accepted output.
  • Account mapping, source evidence and inspection responsibility need agreement with the team before actions run.
  • Ask Proto to prepare the information, then retain the deciding evidence and reconcile the resulting operating effect.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Product Lifecycle Mgmt (PLM)
  • Design authoring and document repository
  • Customer order source
  • Supplier purchasing or receiving source
  • Shop-floor evidence source
  • Finance system
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 17 tables
17tables
  • Design documents4
  • Engineering changes4
  • Production planning6
  • Materials and purchasing8
  • Production execution7
  • Batch acceptance6
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Agree the operating boundary

    Product Engineer and Engineering Reviewer define the design and change evidence. Production Planner identifies demand and the manufacturing instruction handoff. Agree design-repository, receiving or finance connections where your operating cycle needs them.

  2. Map records and identities

    Admin resolves user accounts and people, then maps items, parties and resources. Agree source identity, revision naming, lot locations and units before importing linked operating records.

  3. Configure access and screens

    Set preparing and deciding responsibilities with ordinary accounts. Confirm that Engineering Reviewer can inspect the submitted evidence and Quality Inspector can perform accepted release. Rehearse own-record access for Operator.

  4. Rehearse the complete cycle

    Submit a design, review and implement its change, release feasible work and post an eligible issue. Record an attributed interval and accept inspected Pending output. Include duplicate scope, insufficient stock, invalid dates and Held output.

  5. Reconcile and open the pilot

    Compare material deductions and accepted receipts with their evidence. Keep a Pending sibling to check incomplete work. Preserve the source baseline and agree recovery responsibility before opening the operating cycle to the team.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Product Lifecycle Mgmt (PLM).

All questions
How do I get started?

Click Get started, then use Proto to configure Product Lifecycle Mgmt (PLM) for your business. Pilot a product revision with a responsible reviewer, Approved customer demand, feasible work and reconciled opening lot balances. Rehearse a duplicate refusal and Pending output acceptance before expanding.

What work can the team run?

Prepare product-linked design documents and engineering changes, then follow the operating cycle through work orders, material issues, attributed production intervals and batch disposition. Agree the reviewed manufacturing instruction handoff before affected work is released.

How are design corrections preserved?

The design action checks product, revision and document-type identity and refuses duplicate submissions with a reason. Supported corrections append attributed successor evidence and retain the original basis. Engineering Reviewer can then inspect what changed and explain the decision.

What is the engineering change path?

Eligible attributed scope follows Draft, Review, Approved and Implemented. Engineering Reviewer decides approval; Product Engineer applies the reviewed scope. Invalid, duplicate and already-completed requests are refused. Agree how declined requests are handled with the deciding person during setup.

How do engineering and production agree the handoff?

Product Engineer prepares the reviewed design context. Production Planner inspects the refreshed work-order detail and engineering-change screen, then confirms the instructions needed for affected work. Resolve disagreement with Engineering Reviewer before production release.

What must pass before production release?

The action requires Draft work with Approved demand, positive planned quantity, an Available resource and feasible dates. Success freezes the release input and marks work Released. Batch preparation follows production recording later in the cycle.

How is material availability checked?

The issue action selects eligible stock for the same item and lot and subtracts reserved quantity from on-hand. Success marks the issue Posted and reduces exactly that balance once. Replaying the successful action preserves the original deduction.

What happens when production is recorded?

The action checks a valid interval, finite nonnegative good and scrap quantities and operator account mapping. It routes work to quality review and output to Pending. Material consumption remains with the issue action; finished-goods receiving follows inspected acceptance.

Can held or rejected output be released?

Accepted-output release requires Pending disposition. Held and Rejected are ineligible. Successful inspected release receives accepted finished goods once and completes the work order only when every sibling batch is terminal. Keep outstanding disposition visible when explaining incomplete work.

What should we agree before go-live?

Set the preparing and deciding responsibilities, account mappings, source units and opening stock. Rehearse refused and repeated actions with ordinary accounts. Agree any design-repository, receiving or finance connection your team needs and review implementation and pricing before opening the pilot.

Set up Product Lifecycle Mgmt (PLM) your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appProduct Lifecycle Mgmt (PLM)

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.