Assess feasibility
Workflow, cycle time, variation, site access and existing automation.
Building toward task-specific robot deployment. Today, you can submit a workflow for review and discuss the requirements of a prospective project.
Discuss a prospective project ↗Define the task and operational outcome before selecting hardware or models. A deployment project needs evidence about the environment, physical constraints and performance requirements.
Workflow, cycle time, variation, site access and existing automation.
Required demonstrations, observations and evaluation conditions.
Integration, safety, human assistance and acceptance requirements.
Current stage: project enquiries and requirements discussions. Robot supply, integration, deployment dates and project delivery are not offered as confirmed capabilities on this page.
A prospective Forge project may begin with a Field collection: recording how the task is performed and establishing the data needed for adaptation and evaluation. Collection is scoped separately from robot deployment.
Before a pilot, a project would need an agreed robot and integration plan, representative evaluation conditions, human intervention requirements and assigned safety responsibilities. Describe existing equipment and site constraints in your brief.
Explore the data side →Describe the workflow, operating constraints and desired outcome. We’ll review fit and use your brief to discuss requirements and possible next steps. A commissioned assessment or pilot would need a separate agreed scope.
Your brief is stored for x39 to review and respond. How we handle enquiries. Please avoid confidential documents or personal information about others.
Fields marked * are required. Everything else can be discussed later.