The problem
CAM and NC files live on a shared drive with names like part_v3_final_FINAL. Which version is proven on the machine is anyone's guess.
What it does
- Index and version CAM and NC files (pointers, not a blob store)
- Checkout and checkin so two people do not overwrite each other
- Track which version is proven on the machine
- Pairs naturally with the CAM library
Who it's for
CAM programmers and anyone who owns the post-and-prove workflow.
Works with
Works on its own - no other module required.
Recommended companion: CAM
File Management indexes the CAM and NC files that the CAM library's assemblies produce.
Common questions
What does it replace?
CAM and NC files scattered across folders and USB sticks, with no way to know which version actually ran.
Who is it for, and do I actually need it?
CAM programmers and anyone who has cut a part from the wrong revision. You need it if 'which file is the proven one?' is ever a question.
Does it need another module?
No. File Management stands on its own, and pairs naturally with CAM. It points at your files, it is not another place to dump them.
How does it make the rest of TRS better?
It puts a checkout and check-in lifecycle and a proven-version marker over the CAM files the rest of TRS already references, so the assembly, the NC file and the version on the machine all line up.
Does it store my CAM files?
No. It indexes and versions them where they already live. TRS is the orchestration layer, not a blob store, so you keep your files and gain the lifecycle.