Customer inputs remain customer assets
Ownership, derived artifacts and reusable platform improvements are separated contractually.
AI ENGINEER / DEPLOYMENT
Cloud or private deployment. Start with your own models.
Prepare the existing model library in your own PDM for MST to import. Choose cloud access with an account opened by MST, or private deployment with enterprise licensing and implementation fees.
GETTING STARTED
Choose the deployment that fits your team.
Your existing PDM model library is the starting point. MST imports your component models for use in the agreed equipment-design workflow.
| Deployment | How it works |
|---|---|
| Cloud deployment | MST opens an account for your team. We agree on the model-library import and equipment workflow for your deployment. |
| Private deployment | Enterprise license + implementation fees. MST implements the solution in the agreed private environment. The proposal defines the licensing terms and implementation deliverables. |
TOTAL COST / IMPLEMENTATION
How much does design automation really cost?
Compare the full cost of an accepted design task: internal effort, external services, software and operating costs, plus a realistic share of setup and implementation. Use equivalent scope and quality for both alternatives.
Include the work around the software.
- One-time: library preparation, integration, configuration, deployment and training.
- Recurring: license or subscription, agreed usage, infrastructure, maintenance and support.
- Customer effort: input preparation, supervision, engineering review, corrections and administration.
- Remaining delivery work: external services, additional checks and rework, including unsuccessful attempts.
For MST private deployment, the proposal separates enterprise licensing from implementation. Confirm cloud terms, scope, support and customer responsibilities in the proposal; this page is not a price quote.
Compare cost per accepted task.
Planning formula: total comparable cost ÷ number of accepted tasks. Keep rejected work and its costs in the numerator. Allocate setup costs using a stated time horizon and realistic volume.
Illustrative calculation, not MST pricing or measured performance: a current task takes 12 hours valued at $80 per hour: $960. An alternative takes 8 total hours including preparation, review and corrections ($640), plus $40 operating cost and $200 allocated software and setup cost: $880. The modeled difference is $80 per accepted task; capacity released is 4 hours.
Those four hours do not automatically reduce payroll. Identify whether they avoid overtime, outsourcing or planned hiring, or enable additional profitable work. Change the assumptions to your actual costs and volumes before making a purchase decision.
Use the existing ROI evaluation checklist · Separate time saved from an earlier delivery date
HIRING / OUTSOURCING / AUTOMATION
Should you automate design work, hire an engineer or outsource it?
Compare the task, its frequency and the responsibility you need to retain. These options can be combined. A team may automate repeated assembly steps while using its engineers and specialist suppliers for new design and independent review.
| Option | When to consider it | Cost and delivery questions |
|---|---|---|
| Improve the current workflow | Low volume or avoidable errors from unclear inputs, templates or handoffs. | Could better standards and existing CAD functions resolve the bottleneck at lower total cost? |
| Hire engineering capacity | Sustained work requiring broad judgment, ownership and new design. | What are recruitment, onboarding, supervision and fully loaded costs? When will capacity be available? |
| Outsource a work package | A capacity peak or specialist task with clear inputs and acceptance. | Include supplier fees, coordination, IP terms, review and revision cycles. Who accepts the delivered result? |
| Automate a recurring task | Repeated supported work with reusable inputs and measurable acceptance. | Will sufficient accepted volume cover setup and operation after review and correction effort? |
See the decisions for each buying role · Describe your task and cost or delivery objective
IMPLEMENTATION SCOPE
Agree on the work behind the deployment.
For private deployment, the proposal separates the enterprise license from implementation deliverables. Define the equipment workflow, model-library scope, environment and acceptance checks before work begins.
Choose one equipment task.
Start with a recurring assembly or P&ID-to-layout task in supported semiconductor gas equipment. Agree on the inputs, expected editable SOLIDWORKS result and engineering checks.
Prepare your existing PDM models.
Your team provides the existing component models and approved revisions within the agreed PDM scope or controlled export. Define model-library import, part mapping and any preparation work in the implementation plan.
Set up the agreed environment.
For cloud access, MST opens your team account. For private deployment, define the environment, authorized access and SOLIDWORKS setup. Confirm required software licenses and which setup tasks each team owns.
Review the result and hand over.
Agree on evaluation cases, engineer review, user onboarding and support responsibilities. The proposal identifies the deliverables, acceptance criteria, timeline and fees for the selected scope.
For the first conversation, a short description of your equipment, repetitive task and CAD/PDM setup is enough. We agree on scope and a suitable sharing process before requesting models.
01 / DEPLOYMENT PRINCIPLE
Customer engineering truth stays authoritative.
The system is designed around customer-local PDM/model-library access, controlled ingestion, versioned Rulepacks, isolated AI engineering execution and customer production-release authority. Public website inquiries never accept CAD, GDS, PDK or confidential engineering attachments.
Authorized PDM/model-library boundary
A configured customer-local adapter resolves only approved part identities, revisions, lifecycle states and native models inside the authorized scope; an approved controlled export remains an alternative.
Evidence-preserving transformation
Document observations, inferred relationships and formal engineering facts remain distinguishable.
Customer production-release authority
The bounded execution contract is designed to require no engineer operation during the run; customer approval and production release remain outside it.
02 / AGENT AND DATA FLOW
Know what runs where, before sharing engineering data.
SolidWorks is operated by an Agent on a customer-authorized Windows machine. PDM access, planning services, model processing and data transfers are scoped for each deployment. Local CAD execution does not mean that every processing step runs offline.
The deployment data-flow schedule must identify approved data, service providers, locations, access roles, retention and deletion responsibilities. These are deployment-specific decisions, not blanket promises made by this website.
| Layer / location | Data and purpose | Access, transfer and retention boundary |
|---|---|---|
| Customer-local Agent Windows + SolidWorks | Receives approved assembly plans and commands; operates the authorized SolidWorks environment. | Define who can dispatch work and approve execution. Confirm local cache access, cleanup and operational ownership. |
| Authorized PDM / model library | Approved part identities, revisions, native files and extracted geometry/interface information used for planning and assembly. | Limit access to the agreed library or controlled export. Define which files and derived data may leave the source system, and their approved destinations. |
| Deployment-approved control, planning and model services | May process authorized inputs and derived data, and return plans, commands or results. | Document each service, hosting region, transmitted data and provider terms. Confirm retention/deletion and any model-data use before enabling the flow. |
| Native artifacts and review evidence | Local SolidWorks output and configured read-back results; approved copies may be returned to the deployment workspace. | Specify storage location, authorized reviewers and artifact retention. Customer engineering authority decides production release. |
| Operational telemetry | Job status, diagnostics and execution errors needed to operate and support the service. | Define diagnostic fields, redaction, destinations, support access and deletion. Do not assume logs are free of engineering information. |
This is a deployment review framework, not a public field-deployment claim, certification or promise of fully offline operation. The website Privacy Notice covers website inquiries and analytics; it does not replace the product deployment data-flow schedule.
Security and IP diligence
A deployment your engineering and IT teams can review.
Final customer deployments are scoped through NDA, data-flow mapping, access control, retention policy, export/compliance review and an explicit responsibility matrix. The website does not imply certification or customer endorsement.
Private execution boundary
Deployment can be structured around isolated workers, scoped credentials and auditable access.
No silent production handoff
Evidence status and engineering approval are explicit gates, not implied by model confidence.
Private technical review
Discuss deployment without uploading secrets.
Describe the non-confidential workflow, toolchain and desired verification boundary. A human will follow up before any protected engineering material is exchanged.
Request deployment reviewANSWER-READY NEXT STEPS