01
Vault for one product line
CAD files moved off shared drives into check-in and check-out with versions.
Manufacturing / Product Data Management
Product data management software that keeps every revision traceable
When drawings live on shared drives and changes travel by email, the shop floor builds to whatever file it found last. Agnotic Technologies builds product data management software, or extensions around the PDM you already run, so every part, revision and change has one owner and one record.
CAD vault
Check-in, check-out, versions
EBOM to MBOM
Linked by change order
Release
Published to ERP and MES
Trusted by global innovators
Industry Overview
What is product data management software?
Product data management software is the system of record for a manufacturer's engineering data: CAD files, part numbers, revisions, bills of materials and engineering changes. Agnotic Technologies builds custom product data management software, or extensions around an existing PDM, so released designs reach ERP and MES with a change record behind every revision.
Industry Challenges
Where does engineering data go wrong without PDM?
The symptoms show up in production and purchasing, but the cause is usually upstream in how engineering data is stored and released.
Two engineers open the same assembly from a shared drive, and the second save overwrites the first.
Part numbers come from a spreadsheet, so duplicates appear and nobody knows which one purchasing ordered.
The engineering BOM and the manufacturing BOM in ERP drift apart after a few changes, and kits go to the line short.
A change request lives in an email thread, so nobody can list the drawings and assemblies it touched.
Drawings reach the floor as loose PDFs with no link back to the revision they were printed from.
A supplier keeps building to the old revision because the change notice never reached them.
EBOM and MBOM
What is the difference between an engineering BOM and a manufacturing BOM?
Most PDM projects stall on this question first. The engineering BOM describes what the product is; the manufacturing BOM describes how the plant builds it. The software has to keep both and the link between them.
| Question | Engineering BOM (EBOM) | Manufacturing BOM (MBOM) |
|---|---|---|
| Who owns it | Design engineering | Manufacturing engineering and planning |
| How it is structured | By function and design assembly, as the CAD model is built | By build sequence, work centre and kit, as the line assembles it |
| What it contains | Designed and purchased parts, with quantities and revisions | The same parts plus consumables, packaging, phantom assemblies and process items |
| When it changes | When an engineering change order releases a new revision | When engineering changes arrive, and when the process changes with no design change |
| Where it lives | PDM, as the system of record for design data | ERP or MES, as the system of record for production |
| How the two stay aligned | Each released revision publishes an item and BOM event | Planners map each EBOM change into the MBOM and record the effectivity |
Our Approach
Should you replace your PDM, extend it or build your own?
The answer is usually a mix. We decide per object, not per system, so each record has exactly one home.
Extend a commercial PDM where it already works
If the vault and CAD check-in work, we build what is missing around it through its API: change workflows, ERP release, supplier notices or reporting.
Build custom where the process is your own
Part numbering schemes, configurable products or a regulated change process that no packaged workflow fits are where a custom build pays off.
Keep one system of record per object
CAD files and revisions belong to PDM, the item master and MBOM to ERP, and execution to MES. Integrations move released data; they never let two systems edit the same record.
Capabilities
What do our product data management services cover?
We build the engineering data layer. CAPA, audits and document control as quality processes are covered on our quality management system software page, and shop floor execution on our MES integration page.
CAD file vault
Check-in and check-out with locks, versions on every save, and file references kept so an assembly opens with the right part revisions.
Part numbering service
One service issues part numbers to your scheme, checks for duplicates and records who requested each number and why.
Revisions and lifecycle states
Work in progress, in review, released and obsolete states, with revision letters or numbers following the rules your drawings use.
EBOM editor and where-used
Multi-level BOMs built from the CAD structure, with where-used search so an engineer sees every assembly a part sits in.
MBOM derivation
The manufacturing BOM built from the released EBOM, with plant-specific items added and every difference traced to its source.
Engineering change workflow
Change request, impact review, change order approval and change notice, each step with its approvers and records.
Release publishing
Released items, BOMs and drawing references published to ERP and MES as events, with acknowledgements stored back in PDM.
Supplier change notices
A portal or feed that tells each affected supplier about a change and records when they acknowledged it.
How It Works
How does released data move from PDM to ERP and MES?
This is the release path we design first, because most errors on the floor trace back to it. Nothing moves until a revision is released.
Work in progress stays in the vault
Engineers check files in and out freely. ERP and MES never see unreleased versions.
01
1
Release locks the revision
When the change order is approved, the revision moves to released and its files, BOM and metadata are frozen.
02
2
The integration layer publishes events
Item, BOM and revision events go onto a queue with the change order number and effectivity date attached.
03
3
ERP updates the item master and MBOM
Planners see the new revision, map it into the MBOM and confirm effectivity, and ERP sends an acknowledgement back.
04
4
MES gets drawings and instructions by revision
Work instructions reference the released revision, so the operator sees the drawing that matches the order being built.
05
5
Engineering Stack
Formats, standards and tools around a PDM build
We work with the CAD tools your engineers already use and keep neutral formats for exchange and archive.
CAD and exchange
Native CAD files through the CAD vendor's APISTEP AP242 (ISO 10303-242) for neutral 3D exchangePDF drawings tied to a revision
Data and files
PostgreSQL for items, BOMs and changesObject storage for CAD files with versioningSearch index for where-used and metadata
Integration
REST APIsMessage queue for release eventsERP and MES connectors
Standards in view
ASME Y14.35 revision practicesISO 13485 design and development controls for device makers21 CFR Part 11 records and signatures where they apply
Engineering change flow
What record does each step of an engineering change leave?
Our original element for this page: the change flow we build, with the record each step must leave behind. An auditor, a planner or a supplier should be able to answer any question about a change from these records alone.
| Step | What happens | Record it leaves |
|---|---|---|
| 1. Change request (ECR) | Anyone raises a problem or improvement against a part or document | Request with reason, requester, affected items and attachments |
| 2. Impact review | Engineering checks where-used across BOMs, drawings, tooling and stock | Impact list of assemblies, documents, open orders and inventory on hand |
| 3. Change order (ECO) approval | The change board approves, rejects or sends the change back | Approvers, decision, date and any electronic signatures |
| 4. Revision increment | Affected parts and drawings move to the next revision | Old and new revision of each item, with the change order number |
| 5. Effectivity | Planning sets when the change applies: date, serial number or lot | Effectivity rule and the disposition of existing stock |
| 6. Release to ERP and MES | Released data publishes to production systems | Publish events and acknowledgements from each receiving system |
| 7. Change notice (ECN) to suppliers | Each affected supplier is told what changed and from when | Notice sent, supplier acknowledgement and date |
Measured Impact
What should engineering and operations see at a glance?
Status views we build into the PDM dashboard.
Open
Change orders in progress
Changes waiting on review, approval or release, by owner.
Released
Revisions released this period
Items and documents released, with the change orders behind them.
Mismatched
EBOM and MBOM differences
Released engineering changes not yet mapped into the MBOM.
Unacknowledged
Supplier notices
Change notices a supplier has not yet confirmed.
Use Cases
Where do product data management projects usually start?
First releases small enough to prove on one product line.
02
Part number service
One source of part numbers, with duplicates found and merged.
03
Change workflow
ECR to ECO to ECN with approvers and records, around an existing vault.
04
ERP release integration
Released items and BOMs published to ERP instead of retyped.
05
Product data management for startups
A light vault, part numbering and change records for a hardware startup heading into its first production run.
06
Supplier change notices
Affected suppliers told about each change, with acknowledgements tracked.
Integrations
Which systems does PDM connect to?
PDM owns design data and publishes it; these systems consume it or feed it.
Files and structure
CAD tools
Item master and MBOM
ERP
Drawings and work instructions
MES
Change links to CAPA
Quality management system
Change notices
Supplier portal
Specifications
Document management
Sign-in and roles
Identity provider
Reporting
Data warehouse
Compliance-First Development Services Backed by Global Standards
We build secure, scalable products designed for privacy, interoperability, and regulatory readiness from day one across every sector we serve.
Service Organization Control 2
Verified controls for security, availability, and confidentiality of enterprise data systems.
Information Security Management
Adhering to the international gold standard for managing information security risks.
Quality Management Systems
Ensuring consistent quality in software delivery and operational process optimization.
Our Edge
Why Global Leaders Choose Us
We combine deep technical expertise with industry-specific knowledge to deliver solutions that aren't just functional, but transformational.
Enterprise-Grade Security
We implement rigorous security protocols and compliance standards (HIPAA, GDPR, SOC2) across all industrial solutions to protect sensitive data.
High-Performance Scaling
Our architectures are built to handle massive data loads and user bases, keeping performance steady whether you're serving ten or ten million.
Accelerated Time-to-Market
Using our suite of internal tools and proven frameworks, we cut setup work so your first release reaches users sooner.
Embedded AI Integration
Beyond simple wrappers, we build deep-learning integrations and predictive analytics directly into the core of your industry-specific workflows.
Engagement Model
How does a PDM engagement run?
We start with one product line and one change flow. Effort depends on your files and systems, and we agree a fixed first release on the scoping call.
01
Scoping call
CAD tools, part numbering, BOM structure, the change process and the systems downstream.
02
Data inventory
Files, numbers and BOMs sampled, with the duplicates and broken references counted before migration is planned.
03
Fixed-scope first release
The vault or change workflow live for one product line, released data flowing to ERP.
04
Migrate and extend
More product lines, MBOM derivation, MES and supplier notices on the same data model.
05
Support and change control
Fixes, new rules and CAD version upgrades handled under agreed change control.
Facts and sources
Which standards and rules shape PDM software?
Short facts we design around, each linked to its primary source. The FDA rules apply to medical device manufacturers.
ASME Y14.35 defines the practices for revising drawings and associated documents and establishes methods for identifying and recording revisions, for any form of original drawing.
Source: ASME Y14.35-2025, Revision of Engineering Product Definition Datasets and Associated DocumentsISO 10303-242:2025 (STEP AP242, edition 4) covers managed model-based 3D engineering, including product data management breakdown structures, configuration control data for product variants, version tracking with the documentation of the change process, and release and approval data.
Source: ISO 10303-242:2025, Part 242: Application protocol: Managed model-based 3D engineeringUnder the FDA Quality Management System Regulation, manufacturers of class II and class III devices, and of class I devices automated with computer software, must comply with the design and development requirements of ISO 13485 clause 7.3 and its subclauses.
Source: 21 CFR 820.10(c) (eCFR)For closed systems, 21 CFR Part 11 requires secure, computer-generated, time-stamped audit trails that record operator entries and actions that create, modify or delete electronic records, without obscuring previously recorded information.
Source: 21 CFR 11.10(e) (eCFR)
Voice of success
We don't just build products; we forge lasting partnerships. See how we've helped industry leaders transform their vision into technical reality.
“I can clearly see how Agnotic has a unique way of handling end-to-end development. They are always active on quick chat and provide support quickly.”
Aaron Phelan
Founder, Benchmark
“Agnotic combines deep technical expertise with strong domain knowledge. They understand the business context, anticipate challenges, and make collaboration smooth and effective.”
John Pasmore
Founder, Latimer
“Agnotic is the best technical team we evaluated. Their engineering excellence made our work dramatically easier and allowed us to stay focused on what matters most for maternal care outcomes. They took full ownership of the technical execution, and we are always happy to continue working together.”
Kim Smith
Founder, My Lauren
Related pages
Related manufacturing software services
This page covers engineering data and change control. These pages cover the work next to it.
Quality management system software
CAPA, audits and document control as quality processes.
MES integration services
Shop floor execution and the MES and ERP data around it.
Supplier quality management software
Supplier approvals, audits and incoming quality.
Custom manufacturing software development
Our wider custom build practice for plants and production teams.
Manufacturing software
Everything we build for manufacturers.
More in Manufacturing
More Manufacturing Solutions
Explore other production-grade engineering platforms we deliver across manufacturing.
Cross-Industry Reach
The Same Engineering Patterns, Across Other Industries
The technical patterns behind this platform translate naturally into adjacent verticals.
Frequently Asked Questions
PDM manages engineering data: CAD files, part numbers, revisions, BOMs and changes. PLM is the wider practice across a product's life, from requirements through service and retirement, and usually includes PDM. Most manufacturers need reliable PDM before a broader PLM effort is worth it.
Yes, and it is often the better choice. If the vault works, we build the missing parts around it through its API, such as the change workflow, ERP release or supplier notices, and leave your engineers in the tools they know.
We integrate through the CAD vendor's API so check-in and check-out happen from inside the CAD tool, and file references are read from the model itself. For exchange with suppliers and for archive, we export neutral STEP AP242 files tied to the released revision.
The number of CAD tools and file types, the volume and state of legacy files to migrate, how many BOM levels and plants you run, the systems to publish to and whether the change process must meet FDA or other regulated record rules. We size these on the scoping call before any estimate.
Yes. A hardware startup usually needs a vault, a part numbering scheme and change records before its first production run, more than a full PLM suite. We build that small first and keep the data model ready for MBOMs and ERP later.
Design and change records are the evidence. We build approvals with electronic signatures, time-stamped audit trails and linked design history, so your quality team can show how each change was reviewed. Your regulatory team decides what your device class requires.
Yes. We inventory the files, resolve broken references and duplicate numbers, agree which revision is current with your engineers, and load them with their history where it exists. Anything we cannot confirm is flagged for an engineer rather than guessed.
Industries