Getting Started: jump to another article
How KeepSpec is organized
Everything in KeepSpec sits inside one nested structure. Once this clicks, the rest of the product follows from it.
Sites → lines → machines → checks
- A site is a physical plant or location — an address, a time zone, and business hours.
- A line is a production line inside a site.
- A machine is a piece of equipment on a line — assigned a fluid, with its own spec ranges.
- A check is a single reading taken on a machine: Brix, pH, refractive index, and whatever calculated concentration and condition notes go with it.
Two shared libraries sit alongside this structure rather than inside it — a Fluid (used by any machine assigned it) and a corrective action (used by any check it’s attached to). See Setting Up Your Organization.
Web console vs. mobile app
The two aren’t different views of the same screen — they’re built for different work. The web console (app.keepspec.com) is where an admin builds out sites, lines, machines, and the Fluids and Corrective Actions libraries, and reviews history and reports. The mobile app is where a technician records checks on the floor — see Recording Checks. Both read and write the same data; which one you reach for depends on what you’re doing, not your role — an Admin can record a check from their phone, and a Technician can read history from the web console.
Where alerts fit in
A check that falls outside a machine’s spec range opens an alert, visible on both platforms and escalated if nobody acknowledges it. See Monitoring & Alerts.