Getting Started
Deploy your first Capped AI private AI environment from sign-up to live inference.
Capped AI deploys an air-gapped on-prem appliance inside your plant perimeter in 8 weeks. You keep all data on-site. We ship, rack, and configure the hardware. Your IT team only needs to provide power, a network port, and OPC-UA firewall rules.
Before you start
Confirm you have:
- A signed Capped AI Pilot or Production Agreement
- 1U rack space in the plant control room or server room
- 1× power circuit (standard 220V / 15A minimum)
- 1× 10GbE network port reachable to the DCS historian
- OPC-UA endpoint URL for your historian (Honeywell, AVEVA PI, Yokogawa, etc.)
- IT contact for firewall rule approval (OPC-UA port 4840 inbound to appliance only)
Deployment timeline — 8 weeks
1
Technical kick-off (Week 1)
1-hour call with your plant IT, operations lead, and Capped AI. We confirm the DCS historian endpoint, OPC-UA credentials, rack location, and training schedule. Required attendees: IT contact + shift supervisor.
2
Appliance shipping and rack installation (Week 2–3)
Capped AI ships the pre-configured 1U appliance (Supermicro, 2× NVIDIA H100 80GB, 256 GB RAM, 8 TB NVMe). A Capped AI field engineer travels on-site for rack installation, network cabling, and initial power-on. Duration: typically 1 day on-site.
3
OPC-UA historian integration (Week 3–4)
We configure the read-only OPC-UA connection to your DCS historian. You verify that Capped AI can read alarm logs, trend data, and shift records — and cannot write to or actuate the DCS. Firewall rules are documented and signed off by your IT team.
4
Operator training (Week 4–5)
Half-day training for shift supervisors and operators. Covers: how to start a handover session (voice or typed), how to review the AI draft, how to add corrections, and how to sign the final handover. Arabic and English sessions available.
5
Shadowed production run (Week 5–7)
Operators run Capped AI in parallel with the existing handover process. We monitor handover quality and response times. Any data issues (missing historian tags, wrong alarm IDs) are resolved during this phase. Typical resolution time: 1–3 business days per issue.
6
Go-live and sign-off (Week 8)
Capped AI becomes the official handover system. Paper-based or manual handovers are retired. Your plant manager signs the go-live acceptance checklist. Capped AI Ops Cloud begins receiving aggregate health metrics (no customer data).
What to expect
| Milestone | Timeline |
|---|---|
| Technical kick-off call | Week 1 |
| Appliance shipped from Miami | Week 2 |
| On-site rack installation | Week 2–3 |
| OPC-UA integration complete | Week 3–4 |
| Operator training complete | Week 4–5 |
| Shadowed production run | Week 5–7 |
| Go-live sign-off | Week 8 |
Support
During the pilot, you have a dedicated Capped AI customer success engineer. After go-live, support is via hello@capped.ai (Starter tier) or a dedicated Slack channel (Professional and Enterprise).