Machine-to-machine interface control
Use a numbered interface schedule to keep conveyor geometry, product handover, signals, safety boundaries, responsibilities and test evidence aligned.
Direct answer
A conveyor interface schedule is a controlled record of every boundary between the conveyor and another machine, structure, service or control system. It gives each interface a unique reference and records the geometry, product handover, signals, guarding, utilities, responsibility and acceptance evidence needed to close that boundary.
The schedule prevents drawings, wiring and software from using different assumptions and gives the project team one place to see which interfaces are approved, open or changed.
| Interface block | Typical information | Why it matters |
|---|---|---|
| Mechanical | Heights, gaps, direction, usable width, supports, guides and mounting. | Controls product support and physical fit. |
| Product flow | Product state, pitch, rate, stop position and allowable contact. | Defines the behaviour that the handover must support. |
| Electrical and controls | Power boundary, isolators, I/O, network, normal and fail states. | Prevents contradictory wiring and sequence assumptions. |
| Safety | Guarding boundary, safety functions, access and reset ownership. | Defines how combined equipment is assessed and controlled. |
| Commercial ownership | Design, supply, installation, wiring, software, testing and approval. | Stops necessary work falling between supplier scopes. |
Record reference coordinates, top-of-surface heights, horizontal and vertical gaps, product direction, usable width, guide transitions, support across the gap, frame and leg clearances, mounting method, adjustment range and who supplies the transfer components. Include the product state used to approve the detail.
A plan, side elevation and local detail may all be needed where one view cannot show the complete boundary.
Record power supply and isolation boundaries, signal names, direction, electrical format, normal state, fail state, ownership, terminal or network reference, timing and required response. Typical process signals may include ready, run permit, product present, blocked, fault and reset permission, but the actual schedule must follow the agreed line sequence.
Do not rely on identical signal names if the two machines interpret them differently.
Assign separate owners for design approval, component supply, mechanical installation, field wiring, software, guarding, validation and final acceptance. A single “by others” note is not enough when several parties are involved. The named organisation or role should be able to confirm the deliverable and its evidence.
Responsibility should be agreed before manufacture so missing work is not discovered during installation.
Give the schedule a revision, date and approval status, and link each interface to the current drawing, I/O record and acceptance test. A change to product, height, gap, speed, signal or responsibility should create a visible revision and identify affected equipment. Test results and approved deviations should reference the same interface number.
Keep superseded records for traceability but make the current approved issue unambiguous.
Discuss the actual application
Send the product range, route, operating states, environment and connected-machine information so Lancing can identify the checks required before a quotation.
