Features · Machines
Give every machine a working record.
Build a reliable register of factory equipment, attach the context the team needs, and set up cameras to teach Offsight AI which visible states matter on the floor.
How this is put together
Machines combines the machine register with Vision AI camera setup and state-teaching workflows. Design-file and production tools can provide outputs when a machine workflow needs them.
Operational benefit
Start with the machine record. Then teach the visible states.
- Create a record with the machine name, make, model, type, serial number, asset tag, year, zone, capacity, power and notes.
- Add a profile image so the record is recognizable when the team is working across a busy floor.
- Set up a fixed camera or guided mobile capture for the machine or area you want to understand.
- Define and review examples for states such as On, Off, In Use, Under Repair, Needs Repair or the states that fit your operation.
What is included
Machine records, camera setup, visual-state teaching and design outputs.
Machine register
Keep the name, make, model, type, serial number, asset tag, year and profile image in one equipment record.
Factory context
Record the zone, capacity, power and notes that help the team identify where the machine belongs and how it is used.
Camera setup
Set up installed camera frames for a machine or area as the starting point for visual-state teaching.
Guided mobile capture
Collect examples from the floor through a guided mobile workflow when camera coverage is not the right first step.
Visual-state teaching
Start with familiar states such as On, Off, In Use, Under Repair and Needs Repair, or define states that match the factory.
Design outputs when needed
Use design-file workflows for cut lists, shop drawings and documented machine exports when the equipment workflow calls for them.
With Offsight AI
Teach the model what a useful machine state looks like.
Vision AI guides a structured process for defining states and reviewing examples from cameras or mobile capture before a model is used.
Starts with your language. Name the visible conditions that matter to the team instead of forcing the factory into a generic status list.
Uses real floor examples. Review camera frames or guided mobile captures that show the machine and the state you want to teach.
Keeps review in the setup. The team defines the states and reviews the training examples before relying on the model.
Keeps the equipment identifiable. The machine record gives the visual-state workflow a clear asset, location and operating context.
On the floor
Keep the equipment record close to the work.
See machine integrations running on your factory workflows.
We will walk through the workflows using your products, teams and factory terminology.