Choose the unit before reporting the number
| Unit | What it describes | What it does not establish |
|---|---|---|
Files |
Entries within a defined collection |
The same number of separate models or designs |
Native models |
Source files within an identified model group |
Complete assemblies or all their references |
Designs |
Parts or assemblies distinguished under a stated rule |
Consistent complexity or size |
Projects |
Related engineering work grouped together |
Comparable file counts for every project |
Revisions or versions |
Different historical or released states |
Additional independent designs |
Keep the unit beside the number. If file count and design count are both known, report them separately. Adding them together would combine unlike measurements and create a misleading total.
A fictional count, without an extrapolated value
Suppose an internal project folder holds 40 part models, four assembly files, 30 drawings, 30 PDF outputs and 40 STEP exports. That makes 144 files. It does not make 144 independent designs.
The collection might also contain reused components, library items or older versions. Until those distinctions have been checked, a useful statement would be: “144 files across five categories; the number of independent designs has not been verified.” The example does not indicate a typical archive size or a price.
Keep source files, exports and earlier states separate
A native file and its PDF or STEP output may represent the same engineering state. A subsequent revision may show that same part after a change. Both facts matter, but neither should disappear into a single undifferentiated design count.
The native CAD files guide explains the main file groups. Revisions and BOM context covers their relationships to drawings and assemblies.
Storage volume is another separate measure. Gigabytes can describe the space a collection occupies; they do not replace an understanding of its engineering content.
A counting sheet for information already available
For each recognisable archive group, keep a short internal record of:
- Source: project storage, a management-system report or an existing inventory.
- Period: the years or project states covered by the figure.
- Unit: files, models, designs or projects.
- Quantity: a number, an estimate or explicitly “unknown”.
- Confidence: counted, estimated or inferred from a partial collection.
- Repeated material: known exports, revisions, backups and library items.
- Open boundaries: mixed systems, inherited collections or unchecked duplicates.
An estimate should stay labelled as an estimate. Avoid projecting one unusually large or small project across the entire business archive. State the basis and limitations instead.
Counting is not an instruction to clean up
Do not delete apparent duplicates just to prepare an enquiry. Files with the same name or size can belong to different project contexts. Removing or consolidating material needs its own technical and business decision.
You also do not need to share customer names, file lists or storage paths. For the first conversation, describe the known unit, approximate scale and who might answer further questions. A later representative sample is scoped separately. The archive value factors guide explains why quantity is only one part of the picture.