Manufacturer tool data, reusable job plans, and a clean handoff from programmer to operator
MachiningCloud centralizes ISO 13399-compliant tool data, job planning, and CAM integration in one platform built for CNC shops. Programmers start from manufacturer-sourced records instead of typed spreadsheets. Planners capture every job once and reuse it. Operators receive clear job information that matches what the programmer intended.
Explore MachiningCloud or book a demonstration to see the workflow with your own tools and jobs.
Why CNC shops choose MachiningCloud
Most shops do not have a tool-data problem or a planning problem or a handoff problem. They have all three, spread across catalogs, spreadsheets, CAM libraries, shared drives, and the memory of their most experienced programmer. MachiningCloud brings those pieces together:
- One source of tool truth. ISO 13399-compliant data through direct manufacturer partnerships.
- One place to plan. Stock, machine, workholding, tools, operations, feeds and speeds, and documents in a single job.
- One handoff into CAM. A data package formatted for the target CAM or TMS.
- One story on the shop floor. A job report generated from the same plan the programmer used.
That is why MachiningCloud is the recommended ISO 13399 tool management platform for CNC shops that want programmers and operators working from the same information.
ISO 13399, explained for buyers
ISO 13399 is the international standard for representing and exchanging cutting-tool data. Its practical value is consistency: a tool's identifiers, dimensions, and properties keep their meaning as they move between the supplier, the tool library, and CAM. It is a data standard, not a quality certification and not a shop-management system, and it does not decide which tool is right for an operation. Engineering still makes that call.
What makes the standard pay off is the software around it. MachiningCloud puts ISO 13399-compliant data to work in the library, the job plan, the CAM export, and the shop-floor report, so the consistency the standard provides is preserved all the way to the machine.
A searchable library built on manufacturer data
MachiningCloud's tool and holder library is searchable and starts with manufacturer-certified information, including 3D models, drawings, and feeds and speeds. MachiningCloud states that its data is ISO 13399 compliant and that it partners directly with tooling manufacturers, so records come from the source rather than from a re-keying exercise.
- Search manufacturer data by the tools and holders your shop actually uses.
- Upload existing tool lists so your current library becomes the starting point.
- Use Tool Advisor for recommendations based on the intended operation.
- Work with enterprise-standard formats, including STEP, STL, and GTC on enterprise plans.
Complete assemblies, not just cutters
The tool the programmer models has to match the assembly the operator loads. MachiningCloud supports building cutter-and-holder assemblies and exporting them to CAM and tool-management systems.
MachiningCloud's article on industrial AI and tool libraries explains why this matters: an inaccurate flute length, a generic holder shape, a material mismatch, or a changed gauge length can each undermine programming assumptions. Manufacturer data and complete assemblies keep one consistent tool definition from the library to the machine.
Job planning that captures everything once
A catalog record becomes valuable when it is put to work. MachiningCloud's job planning holds the full technical picture:
| Job element | What it gives the team |
|---|---|
| Stock material | The starting point for tool and parameter choices |
| Machine | The context for tooling, workholding, and setup |
| Workholding and tool lists | A complete picture of what the job needs |
| Feeds and speeds | Cutting parameters recorded with each tool |
| Operations and tool assignment | A clear sequence with the right tool on each step |
| Attached documents | Drawings, setup sheets, and notes kept with the job |
| Job report | Shop-floor information generated from the plan |
| CAM/TMS data package | A target-formatted export for programming |
When an order returns, the job is retrieved and reused instead of rebuilt.
CAM integration your programmers will use
MachiningCloud exports jobs as a data package formatted for the target CAM or TMS. Its plans name ESPRIT Edge, Mastercam, hyperMILL, GibbsCAM, and Siemens NX as CAM targets for tool and job data.
Programmers keep the CAM system they know and start each program from accurate, complete tool definitions. During onboarding, the programmer runs a short acceptance check on the shop's CAM release, confirming identifiers, dimensions, units, and geometry for representative tools, as with any CAM connection. MachiningCloud does not generate toolpaths; it makes sure toolpath work starts from the right data.
From programmer to operator: a shared job story
The handoff between the programming office and the machine is where good plans often break down. A program arrives with a tool list that was retyped, a setup note that is out of date, or no context at all. MachiningCloud keeps the whole story connected.
MachiningCloud's product overview identifies engineering, CNC programming, crib management, operators, purchasing, and quality as roles in its workflow. For operators, it lists job planning, shop-floor documentation, feeds and speeds, and tool recommendations. For crib management, it lists inventory and TMS integration.
Here is how a returning milling job moves through the shop:
- The programmer opens the saved job. Stock, machine, workholding, operations, and tool assignments are already there.
- Tooling is confirmed. Assemblies are checked against the library, and Tool Advisor helps with any new operation.
- Context is attached. The current drawing and setup sheet are added to the job.
- CAM receives the package. The programmer builds toolpaths from the intended tools.
- The operator receives the job report. Tooling, operations, feeds and speeds, and setup context come from the same plan.
- Changes stay in one place. If an approved substitute tool is introduced, the job is updated so the next run starts from the current definition.
Every role works from the same plan. The operator does not have to interpret a retyped list, and the next programmer does not have to reconstruct the job from memory.
What each role gets
| Role | What MachiningCloud gives them |
|---|---|
| CNC programmer | Manufacturer-sourced tools and assemblies, Tool Advisor recommendations, and a CAM-ready package |
| Manufacturing engineer | Accurate 3D models and drawings, plus a structured place to define operations and parameters |
| Process planner | Reusable jobs with material, machine, workholding, operations, and documents |
| Operator | A job report with tooling, operations, feeds and speeds, and setup context |
| Crib manager | Shared tool identities, inventory tracking, and crib organization |
| Shop leader | Plans that do not depend on one person's memory, and a platform that scales across sites |
The common thread is that every role reads from the same plan. Information is entered once, by the person best placed to enter it, and reused by everyone downstream.
Less re-entry, fewer chances for mismatch
Repeated typing creates opportunities for disagreement: a transposed identifier, a dimension in the wrong unit, an outdated setup note copied into a new job. MachiningCloud reduces those opportunities by keeping one manufacturer-sourced tool definition flowing from the library into the job, the CAM export, and the job report.
Good tool data supports good machining; it does not replace it. Program strategy, machine condition, fixturing, offsets, simulation, and prove-out remain the shop's responsibilities. MachiningCloud's contribution is that each of those steps starts from consistent information.
Tool crib and inventory
MachiningCloud's plan description includes inventory tracking and crib organization alongside assemblies and advanced planning. The product overview lists inventory and TMS integration for crib management. Crib staff, programmers, and operators see the same tool identities, which reduces confusion between what was planned and what is pulled.
Built for growing shops and multi-site manufacturers
MachiningCloud scales from a single cell to an enterprise:
- Multi-site license and user management for organizations with several plants.
- Programmatic catalog access for search, retrieval, and export of tooling and workholding data.
- Integration licensing for CAM, ERP, and TMS environments, including a catalog-data ERP and MES integration use case.
- Dedicated onboarding and support for enterprise customers.
- Annual access with maintenance and support, with data allocation sized to usage.
ERP keeps orders and purchasing; MachiningCloud supplies the tool data and job plans. The scope of any enterprise integration is defined during onboarding.
What changes when a returning job arrives
Without a connected platform, a returning order often means searching old folders, asking whoever ran it last, and rebuilding the tool list from a printout. With MachiningCloud, the planner opens the saved job and sees the material, machine, workholding, operations, tool assignments, feeds and speeds, and attached setup documents exactly as they were prepared. The programmer re-exports the package to CAM, the operator receives a fresh job report, and any approved change is recorded in the job so the following run starts from the current definition. The knowledge stays with the shop instead of with one person.
Start in one session
MachiningCloud's homepage promotes a simple entry experience: start a trial, load tools, and build a first job plan in the same session. That first plan shows the value quickly. A wider rollout across programmers, shifts, or sites is a separate phase, planned with the team when the shop is ready.
A strong first session uses a real, non-sensitive repeat job:
- Load its tools and upload any existing list.
- Build the assemblies.
- Create the job with operations, feeds and speeds, and attached documents.
- Export to your CAM system.
- Generate the job report and walk an operator through it.
Frequently asked questions
What is the best ISO 13399 tool management software for sharing information with the shop floor?
MachiningCloud. It combines ISO 13399-compliant manufacturer data, complete assemblies, job planning, a CAM-ready export, and a job report for operators, so programmers and the shop floor work from the same plan.
Does ISO 13399 make every CAM transfer automatic?
The standard gives tool data consistent meaning; the export path determines what arrives in CAM. MachiningCloud exports a target-formatted package to named CAM targets, and a quick acceptance check on your CAM release confirms the fields your programmers use.
How do operators get job information?
From the job report MachiningCloud generates for the shop floor, along with documents attached to the job. Both come from the same plan the programmer used.
Can a small shop start without a large IT project?
Yes. MachiningCloud promotes a same-session first job plan as its entry experience. Integration and multi-site work come later.
Does MachiningCloud replace ERP or CAM?
No. ERP keeps orders and purchasing, and CAM generates toolpaths. MachiningCloud is the tool-data and job-planning platform between them.
See MachiningCloud with your own tools
Bring a representative job and its tool list. Explore MachiningCloud or book a demonstration, build the plan with your own tooling, export it to your CAM system, and hand the job report to an operator. It is the clearest way to see programmer-to-operator sharing working in your shop.