About
A standard first, a machine second.
OCM — Open Cell Module — is an open standard: an assembly cell described as machine-readable manifests, in three layers. A component is transcribed from its datasheet. A module declares which components it contains, how they are wired, and what the assembly does. A cell declares which modules are present and how they connect.
Cellwright is Accel Solutions' implementation of that standard — the software that reads the manifests and generates what runs the cell: the collision scene, the robot program, the PLC sequence, the tag list, the cycle-time estimate. Two names, because a standard that shares its name with its only implementation cannot honestly claim to be independently implementable.
The thesis is narrow enough to be tested: if every fact has exactly one home and that home is machine-readable, everything downstream can be generated. If it holds, the cell takes 40 hours instead of 400. If it does not, this is just a nice open frame design — so proving it is job number one, and it is provable on a laptop.
An AI agent is a first-class reader of all three layers, through the same API the GUI uses. Where the manifests are incomplete it gets a refusal rather than a plausible guess — and that refusal is the human's completion list.
That is also why the mechanical design comes fourth. We already know how to build a frame; six months of steel and servos would leave the actual risk completely untouched.
Open by construction
Three licences, three domains, no ambiguity.
Licensing is structural rather than decorative. The spec is independently implementable — you do not need us to build a compatible module.
- The standard — OCM
- Manifest schemas, mechanical, electrical and fieldbus interfaces, PackML profile. Independently implementable.
- The software — Cellwright
- Resolver, generator, API, refusal engine, composer, agent, runtime, viewer.
- The hardware
- Frame, datum plate, gantry, panel and module designs.
- The registries
- Component, module and cell manifests, tested bills of material and measured data.
Status, plainly
Pre-alpha
The software chain is real: manifests validate, a resolved cell builds a collision scene, a collision-checked plan comes out as a robot program with a cycle-time estimate, and the refusal engine is live. The PLC-sequence emitter is not written, the runtime handshake is still simulated I/O, the registries hold 2 components, 8 modules and 1 cell, and no hardware has been built. Everything we learn gets written down in the journal as it happens.