MDES Applications in Connected Manufacturing

The Data Behind the Digital Twin

MDES does not send raw G‑code or the full CAD geometry between CAD/CAM and machine tools. Instead, it focuses on exchanging rich descriptions of manufacturing equipment and setups, so both sides “understand” the same digital twin of the process.

  1. Tool and Tool‑Assembly Data

    MDES describes the cutting tools, holders and full tool assemblies that CAM uses, including

    • Tool part numbers, names, categories and supplier info.
    • Geometry parameters (diameter, length, flute length, shoulder length, corner radius, etc.).
    • Holder and assembly structure (e.g., collet, shank, retention knob) and how tools are mounted together.

    This lets the machine‑tool side know the exact physical makeup of each tool that the CAM program assumes, avoiding mismatches between simulated and real tool lengths/diameters.

  2. Fixtures, Stocks and Workholding

    MDES also carries,

    • Fixture descriptions (clamps, vices, pallets, custom fixtures) and their mounting positions on the machine.
    • Stock or raw-part geometry and how it is positioned relative to the fixture and machine coordinate system.
    • Workholding setups (what fixture where, which side of the part is machined, vise/plate references, etc.).

    This allows the machine control or setup software to visualize the same setup that was planned in the CAM system, which helps avoid collisions and misalignments.

  3. Future Developments

    Further development of MDES is ongoing. In the future, MDES will be able to represent:

    • Machine types and kinematic capabilities (e.g., 3‑axis, 5‑axis, turning‑mill, gantry vs. bridge).
    • Spindle and auxiliary unit definitions (speed, power, coolant, tool‑changer types).
    • How fixtures and tooling are mounted on the machine table or pallet, including offsets and home position.

    This will enable the CAM system and the machine‑tool control to “agree” on the machine layout and kinematics, which is important for trajectory planning and safe motions.

How MDES Streamlines CAD-CAM-Machine Communication

By sending these equipment and setup descriptions in a common MDES format, CAD/CAM and machine tools can:

  • Avoid Manual Re-entry

    Tool and setup information is entered once and reused across CAD, CAM and machine systems.

  • Reduce Manufacturing Errors

    Consistent equipment data minimizes programming mistakes, collisions and setup errors.

  • Reliable Workflows

    Simulation, probing and machining all reference the same trusted equipment model.

The Difference MDES Makes for CAD/CAM Shops

A job shop using a CAM solution, several 5‑axis CNC machines from different builders and a separate tool management system.

With MDES

  • The CAM software outputs the complete tool and setup information in MDES format as part of the NC programming workflow.
  • The tool‑management system and the CNC machine (via the machine builder’s MDES‑aware software) both consume the same MDES description; no retyping or custom scripts.
  • When the shop adds a new CAM or simulation tool that supports MDES, it can plug into the same MDES‑based data flow without building new proprietary bridges.

Without MDES

  • The programmer defines tools and holders in the CAM software.
  • The same tools must be redefined or imported using custom macros in each machine’s control and in the tool‑management database.
  • When a tool changes (length, holder, new supplier), each system must be manually updated, and custom post‑processors or import scripts often break.

Result

Less time spent on data transfer and setup, fewer mismatches between CAM and machine, and easier adoption of new software/hardware over time.

Practical Use‑Case for MDES in a Collision‑Aware Machine Tool

MDES does not send raw G‑code or the full CAD geometry between CAD/CAM and machine tools. Instead, it focuses on exchanging rich descriptions of manufacturing equipment and setups, so both sides “understand” the same digital twin of the process.

There are machine tools with collision deployment systems that can read MDES. Hence, in a world where a machine can protect itself from collisions, importing an MDES file is a fast and easy way to give the system the context of what it is machining along with the inputs related to a part’s geometry.

MDES provides input on the tools used, saving around an hour of setup time for collision avoidance systems on the machine tool.

  • It tells the machine the context of the part (stock, fixture, work holding layout) and the tools and assemblies that will be used in the CAM program.
  • Instead of manually re‑entering or reconstructing this setup, the machine can simply import the MDES file to “understand” the environment that was used in the CAD/CAM software.

  • Saves setup time: Because there is no need to manually configure the collision‑avoidance system (no manual offsets, tool‑length entries, or fixture‑position re‑definition), a one-hour saving in setup time is realistic.
  • Enables self‑protection: With the MDES‑based context, the machine can compare the incoming NC program against the digital twin of the setup and detect or avoid dangerous motions before they happen.

In this world, the purpose of an MDES file is:

  • To give the machine all the context it needs to self‑protect (part geometry, tools, fixtures) in a single, standardized import.
  • To eliminate manual recreation of the setup and drastically cut configuration time for collision‑avoidance and simulation systems on CNC machines.