Common questions before you request access.

Frequently asked questions

What is Know My Parts?

Know My Parts is an electronics operations platform that connects released product data, material control, work packages, builds, quality history, documents, evidence, and access controls in one operating context.

Who is it for?

It is built for electronics teams that manage parts, products, builds, quality, documentation, and follow-up evidence without wanting to force everything into spreadsheets or jump straight into a heavyweight rollout.

Is it an ERP?

No. ERP and MRP systems still make sense for accounting, purchasing, valuation, and broad company planning. Know My Parts focuses on the electronics operating record between released product data and controlled build evidence.

Is it an MES?

Not in the heavyweight factory-program sense. Know My Parts supports practical electronics build control, operator flow, board history, and evidence without positioning itself as a full large-factory MES replacement.

Does it replace PLM?

No. A PLM can remain the formal owner for product lifecycle approvals, change control and engineering release governance. Know My Parts focuses on the operating record after release: BOM management context, material readiness, production traceability, quality history and evidence.

What does inventory include?

Inventory includes more than stock counts. The material-control layer covers receipts, storage units, packages, labels, shortages, reservations, picks, releases, issues, returns, reconciliations, and searchable ledger history tied to builds.

Can we import existing inventory from Excel or CSV?

Yes, import is a normal onboarding topic. The useful first step is to map your current part numbers, manufacturer references, supplier references, quantities, locations, package types, lots, and date codes into a clean starting structure before the first workflow goes live.

Can we import existing BOMs?

Yes. BOM import should preserve part identity, approved alternates, quantities, revision context and where-used relationships so build-readiness checks can compare real demand with available stock instead of treating the BOM as a flat spreadsheet.

How are product revisions handled?

Revision handling should keep released product data separate from later drafts or changes. The goal is for work packages, material reservations, production consumption, quality records and evidence to reference the released revision that was actually built.

Can one component exist across multiple warehouses, sites or storage locations?

Yes. The inventory story is built around material existing across warehouses, locations and storage units, not one flat quantity. A part can have stock in different sites, cabinets, shelves, bins, staging areas or production contexts, with movement history explaining how it got there.

Can we track partial reels, cut tape, trays, tubes, and bulk stock?

That is exactly the kind of electronics-specific inventory problem Know My Parts is meant to handle. The system distinguishes component identity, packaging, package quantity, unit quantity, location, lot, date code, and movement history instead of treating everything as generic warehouse stock.

Can stock be reserved for a specific build or work package?

Yes. Reservations are part of the material-control story: the system should distinguish on-hand material from material that is available, reserved, quarantined, expected, issued, consumed, or returned so teams do not accidentally promise the same stock twice.

Can inventory be traced into production?

Yes. The intended production traceability is receive to reserve, pick, issue, consume and reconcile, with lots, date codes, package quantities and work-package context available for later support, quality review or audit history.

Does it calculate BOM shortages?

BOM demand and material readiness belong together. A useful rollout compares demand with available stock, reservations, quarantined material, expected receipts, and approved alternates so shortages are visible before production is scheduled.

Can we use barcode or QR scanning?

Barcode and QR-supported workflows are part of the intended material-control direction, especially for receiving, labels, movement, picking, and production issue. The exact scanner setup should be confirmed during rollout because hardware, labels, and workflow details vary by site.

Can every adjustment be audited?

Operational changes should preserve who changed what, when, and why. That includes receipts, transfers, reservations, releases, issues, returns, consumption, corrections, reconciliations, and reason-coded adjustments where the workflow requires them.

Can we export all our data?

Data ownership needs to be explicit before adoption. Export scope and exit requirements should be discussed during onboarding, especially for parts, inventory, movements, products, quality history, documents, and evidence packages.

Where is data hosted and how are backups handled?

Hosting, customer isolation, backup expectations, and recovery requirements should be confirmed as part of the deployment conversation. Rollout shapes can include cloud workspace, dedicated instance, or on-premise deployment, without implying a guarantee that has not been agreed for that customer.

How is onboarding handled?

The strongest first rollout starts with one workflow: inventory and material control, a build process, quality traceability, evidence packages, or an integration. Onboarding should cover data import, roles, first records, pilot success criteria, and how the team expands after the first operating record works.

What is an evidence package?

An evidence package is a controlled bundle of release records, documents, as-built context, quality history, and supporting notes that can be handed to customers, auditors, or internal reviewers without rebuilding the story from scratch.

Does Know My Parts automate CRA or ISO 27001 compliance?

No. It supports workflow and evidence preparation for EU CRA, product-security follow-up, ISO 27001 audit readiness, and document packages, but it does not automatically make a product compliant or automatically grant certification.

How do integrations work?

Integrations are scoped by category and rollout path, not by promising every named connector. Each integration discussion should define what data moves, in which direction, and whether the path is native, API-based, CSV-based, or planned.

How do access controls work?

The platform supports users, groups, RBAC, PBAC, product-level scope, temporal access, SSO / MFA options, IP allowlists, and audit history. The exact setup depends on whether the rollout is cloud, dedicated, or on-premise.

What does it do first?

Most teams start with one visible problem: material control, released product data, work packages, board history, document evidence, or an assurance workflow. The platform can expand from there once the first operating record is working well.

Can we start with only one area?

Yes. Teams often start with inventory and material control, a specific build workflow, quality traceability, or evidence packages. The value grows as those records begin sharing the same product and material context.

How do we get help?

Use the contact and deployment inquiry paths for demos, rollout scoping, or integration discussions. Security disclosures should still go through the vulnerability disclosure route and security contact listed in the legal area.