Product lifecycle management Custom PLM & integration BOM · ECO · DPP

Custom PLM system development

Appfront designs, builds and integrates PLM software for manufacturing, fashion, automotive, medical devices and semiconductor. We build custom Product Lifecycle Management where standard platforms fall short, or integrate Siemens Teamcenter, PTC Windchill, Dassault ENOVIA, SAP PLM, Aras Innovator and Centric PLM with ERP, CAD/CAM, MES, supplier portals and Digital Product Passport flows. BOM management, change orders, version control, compliance tracking — all in one controlled flow.

What is PLM and what does a custom PLM system do?

Product Lifecycle Management is the digital backbone a manufacturer or brand uses to manage a product's entire lifecycle — from the very first concept and initial drawing through production and in-service maintenance to end of life. A PLM holds a product's master data: parts, materials, suppliers, drawings, test reports, certificates and revisions. Around it run the processes that keep product changes under control: change orders, validation flows, supplier onboarding, compliance reporting and release gates towards production.

A PLM system is therefore something different from an ERP. The ERP handles orders, inventory, purchasing and accounting; the PLM governs what a product is and how it comes about. An MES (Manufacturing Execution System) controls the shop floor; a PLM supplies that shop floor with the current drawings and BOM revisions. A QMS (Quality Management System) runs audits and non-conformities; the PLM supplies the chain of evidence an audit can draw on. Good integrations between these systems prevent data from fragmenting across spreadsheets, emails and local drives — a pattern we still see often at organisations that have yet to make the move to structured PLM.

Appfront builds both custom PLM software and integrations between existing PLM platforms and the rest of your IT landscape. In traditional manufacturing with deep CAD integrations, such as automotive suppliers, machine building and defence, we often work with or around Siemens Teamcenter, PTC Windchill or Dassault ENOVIA. For fashion brands that centre on collection cycles and material libraries, Centric PLM or Bamboo Rose is a better fit. For brands and manufacturers with very specific compliance requirements, for example around the Digital Product Passport, MDR or unique sustainability claims, we build a lighter, custom PLM that follows exactly the master data and flows that set your product domain apart. This ties in with our broader practice in software for the manufacturing industry.

BOM as a single source of truth

Engineering BOM, manufacturing BOM and service BOM in one structured tree — with revisions, alternatives and supplier integrations. No loose Excel versions drifting out of sync with the shop floor or purchasing every week.

Change orders under control

Engineering Change Requests, Orders and Notices in a controlled workflow with the right reviewers and gates per discipline. A change picked up by production has demonstrably been reviewed by engineering, quality and purchasing.

Compliance evidence in one place

CE, REACH, RoHS, IATF 16949, AS9100, MDR and the upcoming Digital Product Passport: evidence and provenance linked to revisions and BOM levels, ready for audits and EU reporting without spreadsheet archaeology.

Our development process for PLM projects

PLM projects stand or fall on thorough upfront analysis: which domain, which disciplines, which existing systems, which compliance context. We follow an approach that surfaces the complexity of your product domain early and delivers a stable result. From mapping your current PLM-or-spreadsheet reality to a phased go-live and ongoing management, every step is aimed at getting engineering, production, quality and purchasing working from a single source.

1
Domain analysis

We map out how your product domain fits together: which item types, which BOM levels, which disciplines, which compliance regimes and which adjacent systems are involved.

2
Architecture

We design the PLM architecture, including the data model, integration patterns, authorisations and workflows, and together we determine whether a standard platform, an extension of one, or a custom PLM is the best fit.

3
Development

Implementation in sprints with automated tests, structured logging, monitoring and clear demo moments. You see working flows along the way in an acceptance environment.

4
Go-live & maintenance

A controlled go-live with data migration, validation and a safety net, followed by ongoing management, monitoring and further development in step with your release calendar.

What a custom PLM system delivers in practice

Every PLM implementation is tailored to your product domain, disciplines and adjacent systems. Below are the features we deliver most often for manufacturing, fashion, automotive, medical devices and semiconductor suppliers. Whether you are building your own platform, integrating an existing PLM with your ERP and MES, or adding a Digital Product Passport layer, our API experience comes together here with domain knowledge of product data. Also read about our broader approach to smart API integrations.

BOM management

A structured BOM tree with eBOM, mBOM and sBOM in the same context. Revisions, alternative parts, substitutes, supplier integrations and effectivity dates per item. Changes don't silently ripple through to production but go through ECO flows and release gates.

CAD/CAM version control

Native integration with SolidWorks, NX, CATIA, Creo or another CAD system. Drawings, assemblies and NC programs are checked in and out with automatic BOM derivation, revision locks and where-used overviews. STEP, JT or IFC exchange with suppliers runs through controlled file vaults.

Change order workflows

ECR, ECO and ECN flows with escalation rules, parallel reviewers and statutory retention periods. Changes get impact analyses (where-used, cost impact, regulations), approvals are signed and the version history remains forensically reconstructable.

Supplier onboarding & portal

A supplier portal where partners submit their product data, certificates and material declarations, structured enough to land in your PLM automatically. PPAP flows, REACH/RoHS declarations and first article inspections all run through the same portal, with no Excel attachments.

Compliance & certification

CE marking, REACH, RoHS, IATF 16949 (automotive), AS9100 (aerospace), MDR (medical). Compliance evidence, standard references, risk analyses and test reports are linked to the right product revision. In an audit, you pull the chain of evidence from one system instead of six folders.

Digital Product Passport (DPP)

DPP flows for the Ecodesign for Sustainable Products Regulation: material provenance, repairability, CO2 footprint and recycling data linked to a unique product identifier. For brands that want to do more than comply and use the regulation as positioning.

PLM projects in practice

A PLM system plays out very differently from one industry to the next. A handful of scenarios come up again and again, and for each of them we have working patterns that account for the specifics of your product domain, the CAD tools you use, the compliance context and the existing systems PLM has to talk to. Also read how PLM works alongside CAE software on the simulation side and Digital Product Passport software on the sustainability side.

Manufacturing and machine building

Machine builders, OEMs and tier-1 suppliers with deep CAD integrations, complex assemblies and strict configuration management. We connect Siemens Teamcenter or PTC Windchill to SAP S/4HANA for the purchasing and order flow, and build MES bridges so the shop floor always works with the valid revision. Part of our broader software for the manufacturing industry.

Fashion & lifestyle brands

Fast-fashion, sportswear and lifestyle brands that put collection cycles, fabric libraries and seasonal planning at the centre. We work with Centric PLM or Bamboo Rose and integrate them with production factories in Asia, regional distribution centres and e-commerce storefronts, with material traceability that is ready for textile DPP.

Automotive & mobility

OEMs, tier-1 and tier-2 suppliers in the automotive and mobility sector. IATF 16949-compliant traceability, APQP/PPAP flows with suppliers, and integrations between PLM, eBOM/mBOM, MES and quality management. In this context we often work around Teamcenter or ENOVIA.

Medical devices & life sciences

Manufacturers under MDR and IVDR with strict design control, clinical evaluation and UDI registration. We build PLM flows that support the entire design history file (DHF), device master record (DMR) and post-market surveillance, and integrate them with clinical systems via FHIR where that makes sense.

Semiconductor & high-tech

Semiconductor suppliers and high-tech manufacturers with their own process control, recipe management and strict cleanroom requirements. The PLM links designs, process instructions and metrology data so that a delivered part is always traceable to the exact production recipe and wafer lot.

Energy, utilities & defence

Energy companies, grid operators and defence organisations where configuration management, security classification and long product lifecycles are central. PLM environments with strict authorisations, separation rules between classification levels and long archiving obligations that stay compliant over several decades.

DPP frontrunners in retail & consumer goods

Retail and consumer goods brands that see the Digital Product Passport not as a compliance burden but as a brand opportunity. We build a PLM layer in which material origin, repairability and recyclability are recorded in a structured way, and made accessible via QR code to consumers, repairers and recyclers.

Technology we use

PLM projects don't have a fixed stack: the choices depend on your existing systems, the weight of your CAD integrations and the compliance context. We work with the market-leading PLM platforms when they fit, and build custom PLM on a modern service stack where that sets you apart. We always align the stack with your IT landscape, so your own team can keep managing or further developing the solution in the long run.

Siemens Teamcenter PTC Windchill Dassault ENOVIA / 3DEXPERIENCE SAP PLM Aras Innovator Centric PLM & Bamboo Rose SolidWorks / NX / CATIA / Creo STEP (ISO 10303) & JT IFC (BIM) REST / GraphQL / SOAP OSLC FHIR (medical) SAP S/4HANA & Dynamics MES / QMS bridges PostgreSQL & SQL Server Node.js / Python / .NET / Java Azure / AWS / GCP HMAC webhook validation

Why Appfront for your PLM project?

Appfront combines extensive experience in API integrations and custom software with domain knowledge of product data in manufacturing, fashion and highly regulated sectors. A PLM programme is not a standalone project: it touches engineering, production, quality, purchasing and after-sales all at once. We always start with a thorough analysis of your product domain and adjacent systems — a PLM choice has to be technically sound, but it also has to add practical value for the people who work with it every day.

For every integration and every custom component, we write clear documentation and make sure your own team — or a future supplier — can understand and manage what is running. No black box, but transparent code, explicit contracts between systems and clear agreements on monitoring, alerting and maintenance. That way you stay independent and keep control of your product data and your release calendar at all times.

You work with a dedicated point of contact who understands both the technical and the functional side of PLM — someone who can talk BOM structures with your engineering managers, MDR or IATF 16949 with your quality team, and the architecture of the integration landscape with IT. This keeps communication lines short, prevents miscommunication with PLM vendors and speeds up decisions when choices have to be made during the build around data models, ECO flows or DPP requirements.

Also take a look at our broader practice around the integrations we build, our work in software for the manufacturing industry and our approach to smart API integrations.

  • Experience with Teamcenter, Windchill, ENOVIA, SAP PLM, Aras and Centric
  • Domain knowledge of manufacturing, fashion, automotive, medical and semiconductor
  • Deep API experience — REST, GraphQL, SOAP, OSLC, STEP, IFC and FHIR
  • Familiar with CAD integrations (SolidWorks, NX, CATIA, Creo)
  • ERP bridges to SAP S/4HANA, Microsoft Dynamics, Oracle and Infor
  • MES and QMS integrations for the shop floor and quality
  • Compliance flows for CE, REACH, RoHS, IATF 16949, AS9100 and MDR
  • Digital Product Passport architecture ready for the ESPR roll-out
  • Secure by default — least privilege, audit trails and signature validation
  • Clear documentation that your engineering and IT teams can read
  • A single point of contact, no passing you between account managers
  • Ongoing maintenance and proactive development in step with your release rhythm

Security, compliance and evidence

Product data is sensitive on several levels at once: intellectual property (drawings, recipes, formulations), customer data in service flows, supplier information and, in some sectors, classified data. Appfront builds PLM environments in line with the OWASP guidelines, with encrypted communication, role-scoped authorisations and strict separation of duties between disciplines. Engineering sees what engineering needs, quality sees the relevant audit data, and an external supplier sees only the parts they are responsible for.

For regulated sectors, we build the evidence chain in from the start. IATF 16949 for automotive calls for structured APQP/PPAP flows and advanced product quality planning; AS9100 for aerospace adds configuration management and counterfeit-part prevention; MDR for medical devices requires a complete design history file with clinical evaluation and post-market surveillance. We document the data flows between PLM, ERP, MES, QMS and supplier portals so that your record of processing activities and your technical file are always up to date and you can demonstrably meet the applicable standards.

For the Digital Product Passport and the broader ESPR regulation, we work with a data model that can aggregate provenance, material composition, repairability and CO2 footprint per component and at assembly level. Supplier evidence arrives through structured declarations — not loose PDFs that you have to read out manually, but machine-readable data that can be traced back to the source. Also read our information security policy and coordinated vulnerability disclosure (CVD) policy.

  • OWASP ASVS as the basis for secure development
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least privilege per discipline
  • Audit trails per BOM revision and per change order
  • IATF 16949-compliant APQP/PPAP flows
  • AS9100-compliant configuration management
  • MDR-compliant design history file and post-market surveillance
  • REACH / RoHS / SVHC declarations aggregated in a structured way
  • DPP-ready data model in line with ESPR requirements
  • Monitoring and alerting for data deviations
  • Documentation for your record of processing activities and technical file

Frequently asked questions about PLM systems

Answers to the questions we get asked most often about custom PLM and PLM integrations.

PLM stands for Product Lifecycle Management: the digital backbone a manufacturer or brand uses to manage a product from the first idea through to end of life. The system maintains the product's master data — components, materials, suppliers, drawings, test results, certificates and revisions — and links it to the processes of R&D, engineering, purchasing, production, quality and after-sales. That makes PLM different from an ERP (which runs orders, inventory and accounting) or an MES (which controls the shop floor). PLM governs what a product is and how it comes about; ERP and MES govern how a specific order moves through the chain.

For traditional manufacturing with deep CAD integrations and standard ECO flows, an established platform such as Siemens Teamcenter, PTC Windchill or Dassault ENOVIA is usually the right choice. A custom PLM is worth considering when your product domain is so specific that a standard package costs more in configuration and workarounds than a dedicated solution, for example a fashion brand centred on collection cycles and fabric libraries, a semiconductor supplier with its own process control, or a niche manufacturer with heavy compliance requirements around the Digital Product Passport. We always start with a sober assessment: buy what fits well, build only what sets you apart.

We regularly work with Siemens Teamcenter (manufacturing, automotive, defence), PTC Windchill (aerospace, medical devices, industry), Dassault Systèmes ENOVIA / 3DEXPERIENCE (engineering-heavy sectors), SAP PLM (organisations already deeply invested in SAP), Aras Innovator (open-source enterprise PLM), Centric PLM and Bamboo Rose (fashion). We also integrate PLM with ERP systems such as SAP S/4HANA, Microsoft Dynamics, Oracle and Infor, with CAD tools such as SolidWorks, NX, CATIA and Creo, and with MES, QMS and supplier portals. On the custom side, we build lighter PLM layers using PostgreSQL, a service-oriented architecture and REST/OSLC APIs.

BOM stands for Bill of Materials — the structured list of all components, sub-assemblies and materials needed to make one unit of a product. In practice, there are several BOMs per product: an Engineering BOM (eBOM) from design, a Manufacturing BOM (mBOM) from production and a Service BOM (sBOM) for maintenance. A PLM manages these BOMs, tracks revisions, controls where components come from and ensures that a change in one place doesn't quietly break things further down the chain. Good BOM management prevents production from ordering an outdated revision, or the service organisation from no longer being able to trace spare parts.

A PLM connects to CAD systems through plug-ins, file-vault integrations or native connectors. Engineers check their drawings and assemblies in and out, the PLM tracks revisions, manages the relationships between components and ensures the eBOM is derived automatically from the assembly structure. For CAM (production preparation), the PLM does the same with NC programs and machining plans. We work with the native integrations of Teamcenter, Windchill and ENOVIA for SolidWorks, NX, CATIA and Creo, and build custom connectors where needed for less mainstream tools or STEP/IFC-oriented workflows.

A change order (Engineering Change Order, ECO; sometimes also ECR for request, ECN for notice) is a controlled workflow in which a change to a product is proposed, reviewed, approved and implemented. The PLM determines who may request the change, which stakeholders need to review it (engineering, quality, purchasing, production), which documents go with it and how the change lands in the BOM, drawings, supplier agreements and MES instructions. A well-run ECO flow prevents a design change from going wrong on the shop floor, or compliance evidence from being impossible to reconstruct afterwards.

The Digital Product Passport (DPP) is an EU initiative under the Ecodesign for Sustainable Products Regulation (ESPR) that requires manufacturers to provide a digital passport for a growing number of product groups — starting with batteries (in force since February 2027) and gradually extending to textiles, electronics, construction materials and more. The passport contains information on materials, origin, repairability, recyclability and carbon footprint, accessible via a unique identifier (often a QR code) on the product. For PLM, this means that data which currently sits in separate spreadsheets and compliance tools must be brought into the PLM in a structured, verifiable and machine-readable form — including supplier evidence. We build DPP flows as an extension of existing PLM systems or as the core of a custom PLM for brands that want to get ahead of the requirements. Read more on our DPP software page.

PLM integrations almost always combine several protocols. We use REST and GraphQL for modern service-to-service integrations. We come across SOAP services in older Teamcenter installations and SAP PLM. OSLC (Open Services for Lifecycle Collaboration) is the standard for PLM, ALM and CM tools that need to reference each other's artefacts without duplicating data. For CAD data we work with STEP (ISO 10303), JT and IGES, and with IFC for construction-related products. In a medical context, FHIR comes into play for integrations with clinical systems. File-based exchange via shared vaults or SFTP is still a reality in heavily legacy landscapes, and we build it securely with checksum validation.

Compliance is not a separate module but a continuous layer in the PLM data. For REACH and RoHS, we record the material composition and SVHC percentages for each part, fed by supplier declarations and aggregated across assembly levels. For CE marking, we keep the risk assessment, standards references and technical file documents with the correct product revision. For automotive (IATF 16949) and aerospace (AS9100), we build structured traceability from requirements to verification. For medical devices under the MDR, we link PLM to clinical evaluation, UDI registration and post-market surveillance. The goal is always the same: if an audit arrives tomorrow, you can provide evidence within the required deadlines without anyone having to piece spreadsheets together.

Yes. We are regularly brought in on existing Teamcenter, Windchill or Aras implementations that have stalled somewhere — for example, an integration with SAP that keeps generating errors, a supplier portal that doesn't align with the PLM revisions, or a CAD integration that breaks with every release. We carry out an audit of the architecture, the API calls, the error handling and the data quality, document the current setup and draw up improvement proposals. From there, we take over changes, extensions and ongoing maintenance, or work alongside your existing PLM partner where that makes sense.

Talk to us about your PLM project

Tell us about your product domain, your current PLM-or-spreadsheet reality and the systems your PLM needs to talk to — CAD/CAM, ERP, MES, QMS, supplier portals or a DPP flow. We're happy to think along on scope, priorities, data model and alignment with your PLM vendor. A no-obligation first conversation gives you a clear picture within half an hour of the options and the trade-offs that matter.

Would you like to look at this issue from the custom software side? On applatenmaken.com you will find a detailed look at building PLM software.

Edit content