Start with the transfer task and the work you want the hardware supplier to take on. A robot model name alone does not describe the loaded carrier, the instrument opening or the states your scheduler needs before it can continue.
For the first discussion, start with the transfer task, labware, station access, requested hardware scope and software owner. Use the remaining rows to record what is known and what needs review. Mark unknown items as “to be confirmed” and give each one an owner. Share a non-confidential outline first; agree how restricted drawings will be exchanged before sending them.
| Input | What to provide | Your project information |
|---|---|---|
| Project and revision | Brief reference, date and revision | __________ |
| Your role | Automation company, instrument OEM, software partner, integrator or other role | __________ |
| Transfer task | Source, destination, object and required handoff | __________ |
| Project stage | Concept, prototype, pilot or repeat manufacture | __________ |
| Work package | Components, mechanical assembly or integrated hardware platform | __________ |
| Labware | Supplier, part number/revision, dimensions, loaded mass, lids and permitted variants | __________ |
| Station access | Work height, opening, approach direction, surrounding obstacles and relevant drawings | __________ |
| Mobile base and arm | Selected models, customer-supplied components or requirements still to be reviewed | __________ |
| Gripper and fixtures | Existing tooling, permitted contact surfaces and any parts to develop | __________ |
| Facility constraints | Aisles, thresholds, doors, docking references and relevant environmental requirements | __________ |
| Software boundary | Scheduler owner, instrument communication owner and requested platform functions | __________ |
| Handoff evidence | What confirms arrival, object presence, instrument readiness and completion | __________ |
| Exceptions | Which interrupted or failed transfers must be discussed; who owns recovery | __________ |
| Quantities and timing | Prototype/pilot quantities, indicative repeat demand and requested milestone dates | __________ |
| Acceptance | Proposed test setup, evidence, witness and release authority | __________ |
| Documentation | Requested drawings, interface records, configuration records and service information; any required access or usage rights | __________ |
| Open questions | Item, responsible person and date required | __________ |
Separate a requested feature from an agreed deliverable
Record each requested function as required, optional or outside the proposed scope. Confirm the hardware configuration, interface behavior and acceptance method before treating it as an agreed deliverable. A component specification does not establish the performance of the assembled platform at an instrument handoff.
For a mobile manipulator, review the platform scope alongside the hardware interface to the laboratory scheduler. Keep workflow sequencing and instrument software responsibilities explicit.
Questions to close after the first review
- Which inputs are sufficient for a proposal, and which need a drawing, sample or measurement?
- Which party supplies each component, fixture and software connection?
- What is the proposed acceptance setup, and what remains outside it?
- Which changes would require a revised scope or quotation?
Use the OEM manufacturing overview to discuss the proposed work package. When the brief is ready, send the non-confidential project outline.