My MX Data
Start free trial

M-TEC Group customer story

How M-TEC manages 20–40 engineering file exchanges a day

M-TEC Group exchanges an average of 20–40 files a day with customers, suppliers and remote teams. It uses MX alongside dedicated customer VPNs, with a designated user overseeing releases from its engineering team.

From growth to a repeatable exchange process

Supporting a growing design team

As the design team grew, so did the number of customers who needed large engineering files.

M-TEC develops interior and exterior products for vehicle manufacturers and Tier 1 suppliers. Rail and medical projects brought further combinations of customers, formats and locations.

The starting point Email and FTP were no longer a sufficient default for heavy engineering files and a widening customer network.

Direct VPNs served some larger customers. For the rest, engineers needed a more practical route than email attachments or individual FTP sites.

01From resourcing to engineering design

M-TEC’s Birmingham business supplied engineering resources for more than two decades. In 2010 it established a separate design and engineering centre in Coventry.

The group grew to 50 programme managers, lead engineers, designers and support staff, taking products from concept into development across automotive, rail and medical projects.

02How a customer introduced M-TEC to MX

During a global project, a customer introduced M-TEC to its branded MX service. Engineers used it to transfer large files through a browser.

M-TEC then worked with Majenta Solutions to set up its own branded access for customers, suppliers and remote offices.

03Browser access alongside customer VPNs

Engineers could connect wherever they had internet access. Neither M-TEC nor its partners had to install and maintain another desktop application.

A team with dedicated client networks can use a controlled corporate file-exchange layer for projects that fall outside those connections.

With secure 256-bit encryption, fast data transmission and the added advantage of no third-party software to install and manage, MX is exactly what we need. With an internet connection we can use it anywhere in the world.
SH
Stephen HansonEngineering and Programme Director, M-TEC Group
What changed in practice

Who manages a release

Designers prepare a release, lead engineers review it and a designated user oversees the transfer.

M-TEC made external file exchange part of its engineering quality process.

Designers request transfers

CAD designers and lead engineers can request a transfer while they are working on the project.

A designated user oversees releases

A designated user checks the outgoing exchange and retains a view of releases across projects.

Adding a project contact

Basic contact details are enough to add a new participant when a customer or supplier joins a project.

Supporting quality management

Checking data before release

The release check begins before the file is sent.

Designers consult their lead engineers about what should leave the team. The designated user then oversees the transfer.

That division of responsibilities gives M-TEC one point of oversight while project engineers remain responsible for the work delivered to customers.

Movement records give the IT manager a current view of transfers across projects.

Engineering transfer workflowControlled handoff
Engineering data reviewedDesigners and lead engineers critique models and confirm the information.
Transfer request raisedAuthorised team members prepare the approved data for external exchange.
Gatekeeper retains oversightA designated user maintains a view of information moving in and out.
The workflow helps M-TEC keep engineering responsibility close to the project team while preserving a controlled, visible route for external data movement.
All that our admin needs is the name and email address of a new user and MX does the rest. The system is very easy to administer and extremely easy to use. It's a cost-effective and truly scalable solution and is a major part of our growth strategy.
SH
Stephen HansonEngineering and Programme Director, M-TEC Group
Engineering teamRequests raised by project specialists
OEM customersProject data delivered externally
SuppliersRemote exchange without extra software
IT oversightCurrent movement details remain visible
20–40 files sent or received each day
A key part of the operating model

Handling 20–40 daily exchanges

An average of 20–40 files a day makes a consistent release process important.

M-TEC continues to use direct VPNs with some larger customers and uses MX for other customers, suppliers and remote teams.

At that volume, a reviewer needs to find the relevant release without asking every engineer which file was sent.

Works alongside dedicated customer systemsMX supports exchanges that do not fit through existing VPN links, rather than replacing every established connection.
Supports large engineering workloadsThe route is used for a sustained daily flow of project information across customers, suppliers and locations.
Provides evidence after the handoffFile-movement tracking helps the business retain a clearer record of what has been sent or received.

See how large-file exchange without public-link workarounds works for engineering packages that include supporting files.

Explore your own workflow

Test an engineering release

Test a sample engineering release with your team or bring your approval process to an MX demo.