Deployment

From contract to live picking
in under six weeks

Automcore deployments are designed around your facility's operational schedule. Installation happens during maintenance windows. Production never fully stops.

Standard Deployment

What happens and when

Timeline is structured around 4-arm increment phases so your facility picks throughout the full deployment. Exact scheduling adapts to your maintenance windows.

01

Pre-Installation Assessment

Days 1–3

Automcore's deployment engineer reviews facility network topology, arm model inventory, firmware versions, and physical installation access. Output: deployment plan document with arm-by-arm rollout sequence and maintenance window schedule.

  • Network survey (LAN topology, switch capacity)
  • Arm firmware version audit
  • Physical site access walk-through
  • Maintenance window schedule confirmation
02

Edge Node Installation

Days 4–7

Automcore hardware arrives on-site. The edge node is rack-mounted or floor-mounted in your facility server room or electrical cabinet area. Network cabling from edge node to arm controllers is completed. Edge node is commissioned and connectivity to all arm controllers is verified.

  • Edge node hardware delivered and installed
  • Cabling to arm controllers completed
  • Connectivity test — all arms ping edge node
  • Fleet Manager UI accessible on facility network
03

First Training Session

Days 7–10

First training cohort: 10–15 high-volume SKUs. Operator guides one arm through each SKU's pick sequence while Automcore captures the grasp model. Session runs during or before production shift. No other arms are affected.

  • Operator briefing (30 min)
  • SKU prioritization: high-volume items first
  • Capture sessions per SKU (~45 min each)
  • Model compression and validation
04

Phase 1 Go-Live

Days 10–18

First 4 arms go live on the initial SKU cohort. Each arm receives the model during the next maintenance window, runs local validation, and begins production picking. Automcore deployment engineer is on-site for go-live days.

  • Maintenance window: first fleet propagation
  • Per-arm confidence validation
  • Production picking begins — first 4 arms
  • Live monitoring via Fleet Manager
05

Full Fleet Rollout

Days 18–38

Remaining arms roll out in 4-arm increments over successive maintenance windows. Each cohort validates independently. Training sessions continue in parallel for additional SKUs. By end of this phase, full fleet is live.

  • 4-arm increment rollout per maintenance window
  • Ongoing SKU training (additional cohorts)
  • Fleet Manager showing full fleet health
  • Performance metrics reporting active

Handoff and Steady State

Days 38–42

Deployment engineer hands off to your facility team. Operator training on Fleet Manager administration. Documentation provided. Remote support contract begins. First scheduled SKU propagation set in calendar.

  • Operator training on Fleet Manager (half day)
  • Documentation and runbook delivery
  • Remote monitoring support contract active
  • Next SKU training cohort scheduled

Facility Preparation

What your team handles before Day 1

Network access

Unmanaged switch or VLAN port accessible from the arm controller area. Standard Cat6 cable runs from edge node location to each arm controller. Total cable distance rarely exceeds 30m per arm.

Power outlet

Standard 220V 15A outlet within 3m of the planned edge node location. The edge node draws ~180W under load — less than a standard desktop workstation.

Operator availability

One dedicated operator for training sessions. They guide arm movements during SKU captures — no programming background required. Training time is ~45 minutes per SKU.

Ready to scope a deployment?

We'll walk through your facility configuration and put together a deployment plan with timeline and resource requirements.

Request a Demo Check Arm Compatibility