Home/Process library/Product files without folders
Process library · Quality managementProduct files that build themselves at a manufacturer
A customer or an auditor asks for the full history of one serial number. Instead of opening folders, the quality manager selects the product and the serial number, and M-Files shows every record that belongs to it.
See product files in M-Files See the process
In short
In this scenario a manufacturer anchors every document and record to a product in M-Files for Quality. A document category marks whether a document belongs to the design file, the technical file with the released specifications, or the production history. Production records also carry the serial or lot number. The three files are not folders but views that assemble themselves from this metadata, so they are always complete and current. Quality events, changes and risks are linked to the same product. SoftAdvice sets up and documents the configuration.
Three files per product, and they must always be complete
A customer reports a problem with one serial number. The file is scattered across design, production and quality.
Customers, certification bodies and regulators want to see how a product was designed, which specifications applied and how each unit or lot was made. In practice the same document often belongs in more than one file.
With folders, documents are copied, versions drift apart, and building the history of one serial number for a complaint or an audit takes days.
- Design file: plans, reviews, tests
- Technical file: released specifications
- Production history per serial or lot
- Linked to quality events and changes
What happens from design to the last unit shipped
The product sets the rhythm. Every document added along the way lands in the right file by its metadata.
During design
Build the design file
Plans, reviews and test reports are tagged as design and linked to the product.
At release
Release the technical file
Released specifications and instructions form the technical file of the product family.
Every lot
Record production
Production records carry the lot or serial number and build the production history.
Every change
Keep the files current
A change to the product updates the technical file at once; history stays visible.
Every question
Show it in minutes
Pick a product and a serial number; the file is there.
From product to audit-ready file, step by step
The work is in tagging documents well when they are created. M-Files does the rest.
Define the product
Engineering creates the product with model, product family, intended use and the standards that apply.
Tag every document
Each controlled document gets the product and a document category: design, technical file or production. The category stays the same for the whole lifecycle.
Record production
Manufacturing adds production records with the serial or lot numbers from a controlled list.
Retrieve
Quality opens the design, technical or production view for a product or serial number, with every linked event and change.
Watch the process run
Every lane is a role. Follow one product from its definition to a customer question about a serial number, and see what M-Files does by itself.
A new product or product family is developed.
Engineering creates the product with model, product family, intended use and the standards that apply.
Each plan, test report or specification gets the product and a category: design, technical file or production.
The document appears in the design or technical file view by itself. Only released versions enter the technical file.
Production adds its records with the serial or lot numbers from a controlled list.
Each record joins the production history of that serial or lot, next to the design and technical file of the product.
A complaint or an audit asks how one unit was made.
Quality picks the product and the serial number and sees design, technical file, production history and every linked event or change.
The answer is ready in minutes, with the evidence attached.
First understand. Then improve. Only then automate.
We design the process and its decisions first. Only then do we let the software carry the routine.
Judgement stays with your team
These steps need knowledge of the client, the product or the risk, so a person owns them.
- Define the product
- Tag document with category
- Record lot or serial number
- Customer asks about a serial
- Open the three files
What the technology carries
These steps run by themselves, and every action is logged.
- Show in the right file
- Add to production history
One product, every record linked
Everything hangs on the product. Follow the chain from design to a single unit, and from there to any issue or change.
From design to unit
The records are controlled. The file is a view.
Every specification, drawing, test report and production record is a controlled record with its own version, approval and history. That is the source the auditor relies on.
The design file, technical file and production history are not copies of those records. They are views that M-Files assembles from the metadata, so a record lives in one place and still appears in every file it belongs to. Change the record, and every file shows the new version.
- Controlled record: versioned, approved, signed
- File: a view built from metadata
- No copies, so no versions drifting apart
- In medtech: DHF, DMR and DHR
From copying documents into folders to files that are always complete
Quality spends audit days answering questions, not collecting paper.
Before
- The same document copied into three folders
- Versions drift apart
- Serial numbers in a separate spreadsheet
- Days to rebuild the history of one unit
Now
- One document, shown in every file it belongs to
- Always the effective version
- Serial and lot numbers as metadata
- The history of a unit in one view
M-Files for Quality, set up for your products
The quality solution from M-Files, configured and documented by SoftAdvice.
Product and process as master data
Every document, event, risk and change is linked to a product, a process or both.
Views instead of folders
The three files are views built from metadata, so one document can appear in several files.
Controlled lifecycle
Only approved, effective documents enter the technical file; every version stays in the history.
Questions about this scenario
Which sectors is this for?
Any manufacturer that has to trace products by serial or lot number: machine building, metal and plastics, electronics, food and packaging, and regulated sectors such as medical devices, where these files are called DHF, DMR and DHR.
Does M-Files run our design control workflow?
The standard configuration assembles the design file from tagged documents. Design inputs, outputs, reviews and transfer as separate workflow objects are not part of it; we look at what you need in the implementation.
Can we link to our ERP or PLM system?
Yes. Product data and serial or lot numbers can come from ERP or PLM, so they are not typed twice. The scope is set during discovery.
Cloud or on-premises?
Both. The solution runs as an M-Files Cloud vault in Microsoft Azure or on your own servers, depending on your validation approach and IT policy.
How long does it take to trace one serial number?
In a one-hour demo we show how product files assemble themselves in M-Files. Want to map your own files first? Discovery is the next step.
