Approval ≠ release
Approval completes the review, but it does not automatically publish the revision to production.
Technical documents, CNC programs and release control
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.
In active development · working demo · pilot implementations
Outcomes
Control where uncertainty usually enters the process.
The system makes the rules, ownership and current release status visible to the people who need them.
One current version
The operator station displays only the active release and records its acknowledgement.
Verifiable release evidence
A manifest, integrity hashes and activity history show exactly what the released package contained.
60-second product tour
See the complete flow — from a revision to a controlled release.
This short, silent tour uses real application screens with fictional demonstration data.
Core capabilities
From a working change to safe use of the released documentation.
One flow covers files, decisions, the target machine, internal and external releases and verification of stored data.
Parts and revisions
Keep related revision states, drawings, instructions and programs together under a clear part record.
Approval and production release
Separate, controlled stages record who approved the revision and who released it to production, with timestamps.
Release package and integrity evidence
A frozen package, file manifest and integrity hashes preserve the exact content for later verification.
Documents and NC programs
Drawings, instructions, setup sheets, models, CAM files and machining programs share one context.
NC program comparison
See added, removed and changed lines before making the release decision.
Current release for the operator
Operators work with the currently released revision, while the system records its display and required acknowledgement.
Machine profiles
CNC control, default postprocessor and an explicit assignment of the NC program to the correct machine.
Business partner releases
Controlled handovers, acknowledgements, response deadlines and tracking of documentation that needs replacement.
The complete revision lifecycle
Documentation under control from engineering to the recipient.
Revision Manager connects the technical context of each file with where it should be used, who received it and whether its integrity remains verified.
01 / TARGET MACHINE
From CAD and NC program to the correct machine.
Machine profiles store the machine code, CNC control and default postprocessor. A program can be assigned to a specific profile, so the release decision covers both the file version and the environment where it will be used.
- a catalogue of active machines and CNC controls,
- the default postprocessor visible in each profile,
- relationships between drawings, models, NC programs and instructions.
02 / EXTERNAL RELEASES
Controlled releases continue beyond the factory.
Documentation sent to a customer, supplier or subcontractor remains visible as a formal release. The system shows who received the package, whether handover and required acknowledgement were recorded, and when a newer revision calls for replacement documentation.
- recipients and response deadlines in one view,
- handover and acknowledgement status,
- alerts for a newer revision and required replacement.
03 / RELEASE EVIDENCE
The exact content of every release remains verifiable.
Each release retains its file list, manifest, integrity hashes and decision history, making it possible to reconstruct exactly what reached production.
- a frozen list of files and their versions,
- SHA-256 hashes for later integrity verification,
- the decision and activity history behind the release.
See the system
The change is visible. The release is unambiguous.
These screens come from a working demonstration build and contain fictional data only.
Process case study
What can a pilot for one part family look like?
A reference scenario demonstrates the workflow change without assigning unverified outcomes to a named customer.
Document validity has to be confirmed manually.
- drawing, instruction and NC program live in separate folders,
- program copies remain near the machine without a clear status,
- change agreements are scattered across messages and conversations,
- there is no immediate view of which external recipient has an older release.
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 the separate release decision,
- the operator receives the current package and required instructions,
- partner releases show when replacement documentation is needed.
Example pilot acceptance criteria
An engineer creates a new revision and completes the required package.
The approver sees the change scope and NC-program comparison.
The operator accesses the current release while the superseded version remains in history.
File integrity and external-release status can be checked without searching network folders.
This is a reference scenario, not a claim of a completed customer deployment. Actual criteria are agreed for the plant's process and infrastructure.
Pilot workflow
Start with one real revision case.
No need to reorganise every document at once. Begin with a process that can be evaluated together.
Review the current flow
Identify documents, roles, approval points and the way information reaches production.
Configure the process
Agree statuses, permissions, data structure and the required contents of a release package.
Run the pilot
Use one part family, cell or workstation to validate the workflow under real conditions.
Evaluate and extend
Review feedback, refine configuration and plan the next controlled rollout area.
Deployment and support
Aligned with your workflow and IT policy.
Dedicated environment
On-premises or cloud deployment selected around infrastructure, access requirements and pilot scope.
Roles and integrity
Permissions, recorded actions, revision history and checksums support a controlled document flow.
Direct implementation support
Help with process 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.
See it on your workflow
Test the system with one real revision case.
Bring one part, one document package and one typical change. We will show how it can move from preparation to a controlled production release.
Contact
Would you like to test Revision Manager on your documentation flow?
Describe your current revision, approval and production-release process. We will propose a practical demo or pilot scope.