Factory network Production runtime
Torque controllers Operator HMI Assembly360 runtime Traceability records Reports / exports Quality review
Local-first deployment
Fit Assembly360 to the line, the controller, and the quality process already in place.
Deployment starts with the actual product structure, controller interfaces, VIN or assembly-ID method, component sequence, approved tools, reporting requirements, and operator response to exceptions.
Plant-side runtime Customer-controlled data Guided implementation
Inside the plant Public website
Public internet Commercial website
Product information Demo requests Resources No controller access No production data Customer education
Deployment boundary
The factory runtime and public website are separate by design.
The boundary is the point of confidence: plant systems stay inside the manufacturing environment, while the public site stays informational and request-driven.
Production runtime
- Production runtime
- Torque-controller communication
- Operator HMI guidance
- Assembly state and progress
- Product-level traceability
- Reports and exports
- Customer-controlled production data
Runtime Controller access Data control
Commercial website
- Product information
- Demo requests
- Customer education
- Resource interest
- No controller access
- No production data
Website Education Requests
Need to explain the deployment boundary internally?
Request a deployment walkthrough Request a deployment walkthrough.
We can help you map the factory boundary, production ownership, and rollout steps before the first implementation meeting.
Deployment approach
Six inputs define a responsible deployment.
Controller scope, product structure, operator workflow, quality rules, access, and reporting are agreed before go-live.
01 Controller
Controller scope
Confirm controller model, number of interfaces, protocol, network location, supported tools, and result-recovery method.
02 Product
Product structure
Define products, components, serial requirements, batches, target values, limits, approved tools, and guidance images.
03 HMI
Operator workflow
Agree how VINs and components are identified, how sequences work, and which HMI states require escalation.
04 Quality
Quality process
Confirm NOK, retry, rework, repair, replacement, overrun, scrap, completion, and release rules with the process owner.
05 Access
Users and permissions
Define who can operate, supervise, review quality, configure, manage, support, and access reports.
06 Evidence
Reporting and retention
Agree required VIN report formats, export needs, data retention, review, and customer-approved disclosure rules.
Implementation flow
Discover → Map → Connect → Configure → Validate → Train → Go live
A guided rollout keeps deployment practical and avoids turning it into a one-size-fits-all project.
Review line flow, controller environment, and quality objectives.
Plant reviewDefine products, components, parameter sets, batches, and reporting needs.
Data mapBring supported torque controllers into the plant-side runtime.
ControllersSet up operator HMI, traceability records, and report views.
SetupTest identification, component selection, OK/NOK capture, completion, reconnection, recovery, and reporting.
AcceptancePrepare operators, supervisors, quality, and support teams.
EnablementStart production traceability with a controlled rollout.
Launch Stakeholder confidence
Built for the people who own production confidence.
Different teams care about different parts of the boundary. These cards make that visible at a glance.
Plant teams
Run close to the line with practical station visibility and a predictable production workflow.
Quality teams
Review product-level evidence, NOK trails, retries, and report-ready history.
Automation teams
Connect supported tightening equipment inside the factory boundary and preserve production continuity.
IT / security teams
Keep production systems, controller access, and data ownership clearly separated from the public website.
Deployment prerequisites
What the local environment needs before implementation.
The exact setup is confirmed during discovery, but the current deployment scope is built around these prerequisites.
Local server
A plant-side server for the Assembly360 runtime.
Local network access
Application access over the customer local network.
SQL Express database
SQL Express for local traceability and reporting data.
Windows 11 Pro
Windows 11 Pro operating system for the deployment environment.
Google Chrome
Google Chrome browser for application access.
A guided plant-side production setup
- A guided plant-side production setup
- A local runtime connected to supported factory workflows
- A customer-controlled traceability environment
- A practical implementation shaped around the real line
A public dashboard with direct controller access
- A public cloud dashboard connected directly to controllers
- A generic online demo with production access
- A one-size-fits-all deployment
- A replacement for plant IT/security review
Resources
Approved resources for your internal review.
Use the operator guide, application overview, and public-safe VIN report sample to support evaluation.
Public-safe Deployment guide
Local deployment overview
For plant, IT, and automation teams that need to review the deployment boundary and runtime ownership model.
Public-safe Product summary
Product overview
For decision-makers who want the value story before the technical review.
Public-safe Report sample
VIN report sample
For quality and operations teams that want to understand the shape of product-level evidence.
Assembly360 resources
Looking for product material?
Register your interest in the upcoming overview and report materials.
Assembly360 product overview
Assembly360 operator workflow guide
VIN report sample
Discuss your environment
Request demo Every factory has constraints. Let’s map yours.
Tell us about your assembly line, controller environment, IT boundary, and traceability goals. We’ll help you explore the right deployment approach.