Supplier geometry
Share the approved model and relevant drawings for the quoted work.
CAD file sharing
Complex geometry.
A complete package.
Exchange CAD files and technical design packages with customers and suppliers.
Named recipients · Defined access · Recorded activity
MX / CONTROLLED EXCHANGE04
Assemble the approved package.
↗
Assembly-Design-Exchange.zipIllustrative file package
MXTHE EXCHANGE IN CONTEXT
Give the handoff some context.
A CAD file may depend on referenced parts, drawings and version-specific settings. Assemble a package the receiving engineer can actually open before starting the exchange.
MX provides a route for sensitive business files between named recipients. Match access conditions to the purpose of the exchange and use the available activity record to support follow-up. Keep the underlying approval and information-handling decisions in your own process.
WHERE THE WORKFLOW HELPS
The moments that need a handoff.
Customer reviews
Deliver an agreed native or neutral format for the recipient's review.
External analysis
Include the geometry and supporting information needed for a specific analysis.
A HANDOFF, IN PRACTICE
The right files.
The full context.
A design team is passing a CAD package to an external specialist. Identify the top-level assembly and the dependencies it needs. Check reference paths and the receiving application's version before release. Where a neutral export is requested, review it as a separate deliverable rather than assuming it preserves every native feature.
Illustrative workflow · Adapt to your approved process
Send a CAD assembly that can be opened
↗Assembly-Design-Exchange.zip
A POSSIBLE PACKAGE
- ✓Approved model or assembly
- ✓Required referenced parts
- ✓Format and units note
INTENDED RECIPIENT
The engineer using the receiving CAD environment
A USEFUL RESULT
The recipient opens the intended assembly, resolves the required references and confirms the expected units and revision.
MAKE THE FIRST EXCHANGE COUNT
Test the details.
Then repeat with confidence.
Use the example package as a starting point for a small, representative trial. Agree the success criteria with the person who will actually receive the files.
Check completeness
Approved model or assembly should be easy to identify in the inventory. Open the delivery copy independently of your working folder to catch missing files or local dependencies.
Walk through access
Test with the intended recipient role and receiving environment. Confirm the access conditions, the instructions and the route for getting help.
Agree what success means
The recipient opens the intended assembly, resolves the required references and confirms the expected units and revision. Record any remaining questions before making the exchange part of routine work.
FROM PREPARATION TO RECEIPT
Give each exchange
a clear sequence.
Use Assembly-Design-Exchange.zip as an example of a defined package. Replace it with the approved files and instructions for your actual task.
Explore the MX feature set ↗- 01
Confirm the purpose and recipient
Check who is entitled to receive the information. Record the business purpose through your normal approval process before assembling the package.
- 02
Prepare an approved package
Choose the required files, check their versions and remove unrelated information. Include concise instructions so the recipient knows what to do next.
- 03
Apply the access conditions
Confirm authentication, availability and any download conditions for your service. MX's existing features include named access, MFA and configurable expiry controls.
- 04
Review the exchange
Check the recorded activity and follow up through the agreed process. Keep the exchange reference with the project or client record it supports.
DEFINE THE BOUNDARY
Check the fit
before the first file.
Check reference paths, units, format versions and intellectual-property permissions. Keep the source model and revision authority in your engineering system.
Assess the controls against a representative package and recipient. Confirm any mandatory capability, contract term or deployment requirement with the MX team before relying on it.
Discuss your exchange requirements ↗PRACTICAL QUESTIONS
What to know
before you begin.
Questions about cad file sharing and the exchange workflow.
How can missing references be caught early?+
Create a test copy of the delivery package and open it outside the working directory. Use the receiving environment where possible, so locally available dependencies do not hide a missing file.
Does MX convert or validate CAD files?+
MX provides file exchange. Confirm the recipient's application and supported formats; conversion and engineering validation remain separate tasks.
How should we prepare the files?+
Share the approved model and relevant drawings for the quoted work. Check the approved version, any required dependencies and the recipient's ability to use the package. Include only the material needed for the purpose.
What should we verify during a trial?+
Test a representative exchange from sender preparation to recipient access. Check authentication, permissions, expiry behaviour and the activity available afterwards. Include the actual file types and recipient environment you expect to use.
Does an access expiry remove downloaded copies?+
Do not assume expiry deletes a recipient's local copy. Agree post-download handling and retention responsibilities, and confirm the precise behaviour of the service configuration you plan to use.
Where can we check product details and commercial terms?+
Use the current MX product information and confirm the proposed service with the team. Review the plans and pricing alongside your actual users, workflow and deployment requirements.
YOUR NEXT EXCHANGE STARTS HERE
Valuable data.
Better protected.
Put better controls around your next sensitive file exchange. See how MX fits your organisation's workflow.
7 days freeUp to 5 usersNo credit card
- Full feature access
- Unlimited file size transfers
- Named recipients and MFA
- Custom branding and upload portals