Fragmented context
Files for one part remain in different locations and require manual checking.
NCTune Software
Revision Manager
An approved revision is not yet a production release.
Revision Manager separates approval from controlled production release. Operators receive only the currently released revision, while every decision and package content remains verifiable.
Working product demo · pilot scope agreed individually
The problem
Multiple copies. Multiple locations. No certainty which revision is current.
A drawing, instruction and NC program can circulate between folders, messages and the workstation. Revision Manager makes the rules, ownership and current state visible without pretending that software can replace a sound process.
Copies at the machine
A program left at the workstation may have no unambiguous status as the current version.
Decisions outside the workflow
Change agreements stored in messages and conversations are difficult to reconstruct later.
Superseded external releases
Without one shared view, it is not immediately clear where a newer revision requires replacement documentation.
How it works
From a change to the version actually released for production.
The flow separates preparation, review, approval and release. An approved revision therefore cannot reach production without a separate decision.
- 01Part and documentation
Files, instructions and NC programs form one technical context.
- 02New revision
Each change receives its own status, content and history.
- 03Comparison and review
The scope and NC-program differences are visible before a decision.
- 04Approval
The system records who completed the review stage and when.
- 05Production release
A separate decision makes the correct package available on the shop floor.
- 06History and decision trail
The manifest, integrity hashes and activity history remain verifiable.
Control before the decision
See the change before releasing the program.
The comparison shows added, removed and changed NC-program lines. The approver can review the scope before the separate production-release decision.
- select the baseline and compared revisions,
- review a summary of change blocks,
- distinguish added and removed lines clearly.
See what actually changed between revisions.
Compare two versions of an NC program and move directly between the changed blocks.
Previous
N100 G90 G54Current
N100 G90 G54Previous
N110 T12 M6Current
N110 T12 M6Previous−
N120 S6200 M3Current+
N120 S6800 M3Previous
Line not presentCurrent+
N125 M8Previous
N130 G0 X0 Y0Current
N130 G0 X0 Y0Previous
N140 G0 Z50.Current
N140 G0 Z50.Previous−
N150 G1 Z-8.000 F450Current+
N150 G1 Z-8.500 F450Previous−
N160 G1 X80.000 F1200Current+
N160 G1 X80.000 F1350Previous
N170 G0 Z50.Current
N170 G0 Z50.Previous
N180 M9Current
N180 M9An approved revision does not have to be the version released to production yet.
- Approval
- R04approved
- Production release
- R03currently released
In Revision Manager, production release is a separate, controlled step.
On the shop floor
The operator sees the correct release.
The operator station presents the current package with its status and instructions. The system records display and any required acknowledgement.
- one unambiguous revision currently in force,
- documents and NC program in the released package,
- superseded versions retained in history.
Product scope
What remains controlled in one revision flow.
The correct revision and the decision to use it come first. The wider context then includes files, the target machine, operators and external recipients.
Revision and decision
Part records, successive revisions, statuses and related files form one structure.
Separate stages record who approved the revision and who released it to production, with timestamps.
A frozen file list, manifest and integrity hashes keep the exact release content verifiable.
Added, removed and changed lines are visible before the release decision.
Use context
Drawings, instructions, setup sheets, models, CAM files and machining programs share one revision context.
Operators work with the currently released revision, with display and acknowledgement recorded.
CNC control, default postprocessor and program assignment connect the file to the correct machine.
Recipients, handovers, acknowledgements, response deadlines and replacement requirements remain visible.
A different way of working
From checking copies to one controlled revision record.
This is a reference process scenario, not a claim about a completed deployment for a named customer.
Document validity has to be confirmed manually.
- drawing, instruction and NC program live in separate folders,
- program copies near the machine have no clear status,
- change agreements remain scattered across messages and conversations.
One revision connects the decision with production use.
- part, revision, files and status form one controlled context,
- NC-program differences are visible before approval and release,
- the operator receives the current package and required instructions.
The actual scope, roles and acceptance criteria are agreed for the process and infrastructure of each plant.
View deliveries and reference scenariosReal product
60 seconds from a revision to a controlled release.
This short, silent tour uses real application screens with fictional demonstration data.
Download the PDF product sheetImplementation
You do not need to start with a large rollout.
Begin with one real document flow that can be evaluated together. A pilot may cover one part family, cell or workstation.
- DiscoveryIdentify documents, roles, approval points and the way information reaches production.
- Demo or limited scopeAgree statuses, permissions, data structure, package content and acceptance criteria.
- ImplementationReview the pilot, refine the configuration and agree the next controlled scope.
EnvironmentOn-premises or cloud deployment selected around infrastructure and the plant's IT policy.
ControlRoles, permissions, recorded actions, revision history and release-package integrity.
SupportProcess analysis, configuration, pilot data, user onboarding and evaluation.
FAQ
Questions before the first demo.
Does approving a revision automatically release it to production?
No. Approval completes the review stage, while production release is a separate, controlled action. The revision becomes available to operators only after it has been released.
What types of files can the system manage?
The intended scope includes drawings, work instructions, setup documentation, CNC/NC programs and related production files. Exact formats are confirmed during the pilot.
Is this a replacement for PLM or general document management?
Not necessarily. It focuses on controlled production revisions and releases and may replace fragmented manual work or complement a broader landscape.
What is a released production package?
A preserved snapshot of the files approved together for one revision, making it possible to identify exactly what was issued at that time.
How is an NC program linked to the correct machine?
Machine profiles store the machine code, CNC control and default postprocessor. An NC program can be assigned to the correct profile before release.
Can documentation sent to business partners be controlled?
Yes. The system records recipients, handover, required acknowledgements, response deadlines and whether a newer revision requires replacement documentation.
How is file integrity monitored?
Files and release packages can be verified with SHA-256 checksums. The administration view shows scan results, active deviations and the current backup schedule and status.
How do operators know which revision to use?
The production workspace presents the current released package, its status and any required instruction or acknowledgement. QR access can open the relevant record directly.
Is the product available now?
NCTune Revision Manager is in active development. Guided demonstrations and pilot implementations are available with the scope agreed around the customer's workflow.
Revision Manager
Let’s talk about the document workflow in your plant.
Describe your current revision, approval and production-release process. We will propose a practical demo or pilot scope.