⚙️Equipment & Machines

Equipment categories Myncel supports

Myncel is industry-agnostic. The following categories are the ones we have first-class templates for, but you can always pick "Custom" and define your own. A template pre-fills recommended preventive-maintenance intervals, common sensor types, expected failure modes, and a starter checklist.

• CNC machine tools — mills, lathes, machining centers, swiss-style lathes, plasma / waterjet / laser cutters, EDM machines.
• Presses & forming — hydraulic and pneumatic presses, stamping presses, injection-molding machines, blow-molders, extruders.
• Air & fluid handling — air compressors (rotary screw, reciprocating, scroll), vacuum pumps, hydraulic power units, dryers, chillers.
• Material handling — conveyors (belt, roller, chain), AGVs, AS/RS, hoists, cranes, palletizers.
• Welding & fabrication — robotic welding cells, MIG / TIG stations, press brakes, shears.
• Rotating equipment — pumps, motors, gearboxes, fans, blowers, agitators, mixers.
• HVAC & building services — chillers, cooling towers, AHUs, boilers, heat pumps, exhaust fans.
• Electrical — generators, ATS, switchgear, transformers, UPS systems, PDUs.
• Mobile assets — forklifts, scissor lifts, telehandlers, sweepers, yard trucks, fleet vehicles.
• Healthcare equipment — autoclaves, sterilizers, refrigerators / freezers, imaging systems (non-clinical maintenance side), dialysis chairs.
• Hospitality & property — kitchen equipment, ice makers, dishwashers, laundry, elevators, escalators, pool systems.
• Process & utility — boilers, heat exchangers, water-treatment skids, RO systems, dust collectors, scrubbers.
• Telecom & data center — racks, CRAC / CRAH units, generators, UPS, fire-suppression panels.
• Custom — anything not listed above. Pick "Custom" and define the asset class yourself.

How to add a single machine (the 60-second flow)

Adding a machine to Myncel takes well under a minute. The only required field is the machine name — everything else can be filled in later as you have time. To reach the Equipment screen, sign in and click the Equipment tab in the left sidebar of your dashboard.

1. In the left sidebar of /dashboard click Equipment.
2. Click the "+ Add Machine" button. The "Add New Machine" modal opens.
3. Enter the Machine Name (required) — e.g. "CNC Mill #3" or "Genset-Bldg-A".
4. Optionally fill in: Serial Number, Year Installed, Manufacturer, Model, Category (CNC, Compressor, Generator, Pump, …), Status (Operational / Maintenance / Breakdown / Retired), Criticality (Low / Medium / High / Critical), Location (free text — we recommend the format "Site — Building — Line", e.g. "Plant 1 — Bay A — Line 3"), and Notes.
5. Click "+ Create Machine". The new machine appears in your equipment list immediately, ready to receive work orders, schedules, and sensor data.
6. After creation, click into the machine to upload a photo (Machine Image area), create gateway tokens for sensor data, attach work orders, and review history.

Bulk-importing your existing equipment list

If you already have an asset list in a spreadsheet, an old CMMS export, or a SAP / Maximo extract, you do not have to retype every row by hand. Myncel exposes a public REST API that accepts JSON over HTTPS — point a small script at it and your fleet is in within minutes.

• The public API is rate-limited (60 requests/minute per key). For a 500-machine import that means roughly 9 minutes of polite throughput — fine for a one-time migration.
• Common starter script: 25 lines of Python with `requests`. We can share a template — ask in /support and a human will reply with one tailored to your CSV columns.
• Migrating from SAP PM / IBM Maximo / Limble / UpKeep / eMaint / Fiix / MaintainX / Hippo with automatic column mapping is on the roadmap (see the Roadmap chapter).

1. Open /api/docs to view the OpenAPI spec for the Machine endpoints (POST /api/machines).
2. Generate a personal API key in /settings/api-keys.
3. Convert your spreadsheet to JSON (one machine per object) using your tool of choice — Excel "Save as JSON", a 10-line Python script, or any AI assistant.
4. POST each row to /api/machines with header Authorization: Bearer <api-key>. Required field is name; everything else (serialNumber, manufacturer, model, category, criticality, location, yearInstalled, notes) is optional.
5. Verify in /dashboard → Equipment that all machines arrived. Edit individual records inline or in bulk by re-issuing PUT requests.

QR codes and asset tagging

Every machine in Myncel automatically gets a unique QR code. Print the QR sticker, apply it to the machine, and any technician with the mobile app can scan it to instantly land on that machine's page — its history, open work orders, attached info, and a one-tap "Create Work Order" button.

QR codes are durable and cheap. We recommend printing on weatherproof polyester labels (3M 7811 or similar). For outdoor or wash-down equipment, laminate them or use stainless-steel etched tags with the same code.

Myncel ships with a built-in QR Label Sheet generator at /equipment/qr-labels. It supports the most common sticker-sheet formats out of the box, prints multiple labels per page aligned to the perforations, and lets you reuse partial sheets without wasting stickers. The generator runs entirely in your browser — there is no upload, no third-party service, and the labels never leave your device until you hit Print.

• Avery 5160 / 5260 — 30 labels per Letter sheet. The cheapest and most-stocked format. Labels are 25.4 × 66.7 mm (1" × 2⅝") — small but enough for the QR plus machine name and S/N.
• Avery 5163 / 5263 — 10 labels per Letter sheet. Labels are 50.8 × 101.6 mm (2" × 4"). Plenty of room for QR + name + manufacturer + model + S/N + location + status badge.
• Avery 5164 / 5264 — 6 labels per Letter sheet. Labels are 84.7 × 101.6 mm (3⅓" × 4"). Best for large outdoor equipment where the label needs to be legible from across a yard.
• Avery L7160 (21 / A4), L7163 (14 / A4), L7165 (8 / A4), L7167 (1 / A4) — the European A4 line. Same idea, different paper size.
• Thermal printers — Brother QL-820NWB, Dymo LabelWriter 550, Zebra ZD420 / GK420. Pick the 50×80 mm or 100×150 mm preset, set your printer to use the correct continuous-roll size, and Myncel emits one label per "page" so the printer cuts cleanly between labels.

1. Open /equipment/qr-labels (or click "Print QR" from a machine's detail panel).
2. Choose a Sheet Template that matches the sticker sheet you have. The generator includes Avery 5160 / 5260 (30 per Letter sheet, the most common US format), Avery 5163 (10 per page), Avery 5164 (6 per page, largest), and the European A4 equivalents L7160 (21 per A4), L7163 (14 per A4), L7165 (8 per A4), and L7167 (1 per A4 — full-page poster). Single-label thermal printers are also supported (50×80 mm and 100×150 mm presets cover Brother QL-820NWB, Dymo LabelWriter, and Zebra GK420 / ZD420).
3. In the Show on Label panel, toggle the fields you want printed under the QR — Serial Number, Location, Status Badge, and Manufacturer / Model. Less is more on small labels (Avery 5160) — just the machine name and S/N is plenty. On Avery 5164 you can show everything.
4. Set the App URL field. The QR code on each label will encode that URL plus the machine's ID, e.g. https://www.myncel.com/equipment/clx123abc. When a phone camera scans the code it opens that link directly. If your tenant uses a custom domain, paste it here.
5. In the Machines panel, untick any machine you do not want a label for. For each ticked machine you can also set a Quantity (1–99) — useful when you want 5 identical labels for one machine to apply on multiple sides of a large vessel or on its access doors.
6. If you are reusing a sticker sheet that already has some labels missing (very common — you printed 3 last week and 27 are still on the sheet), set Skip first slots to 3. The first 3 grid positions on the first sheet stay blank so the printer skips over them and your new labels land on the still-attached stickers.
7. Inspect the on-screen preview. Every sheet shows in the preview at 60% scale with the exact mm dimensions of the chosen template. The header tells you exactly how many labels and how many sheets you are about to print, e.g. "120 labels on 4 sheets". Click any individual label to enlarge the QR for a quick visual check.
8. Click "🖨️ Print N labels (M sheets)". A new browser tab opens with a print-ready document and the print dialog opens automatically. In the dialog: set Scale to 100% (NOT "Fit to page" — that throws off the perforation alignment), tick Background graphics so the colored status badges print, and pick the right paper size (Letter for 5160 / 5163 / 5164; A4 for L7160 / L7163 / L7165 / L7167).
9. Apply the labels to a flat, clean, eye-level surface on each machine — typically next to the controls or on the maintenance access panel. Test by scanning with the Myncel mobile app from arm's length.

Connecting equipment to Myncel — the three options

You can connect a machine to Myncel in three different ways depending on your budget, the age of the equipment, and your existing network. You can mix and match across your fleet — most customers manually log usage on older machines while streaming live data from the newer or more critical ones.

• Option 1 — Manual logging. No hardware. Operators or technicians punch runtime, cycle counts, and observed issues into Myncel from a phone or tablet.
• Option 2 — IoT sensor retrofit. Wireless vibration, temperature, current, or runtime sensors that mount onto existing equipment and stream to a small Myncel Edge Gateway.
• Option 3 — Direct PLC / SCADA integration. Read straight from the machine's controller using OPC-UA, Modbus TCP, MQTT, Ethernet/IP, or BACnet/IP.

Option 1 — Manual logging (no hardware)

The simplest option requires no hardware at all. Operators or technicians log runtime, cycle counts, and observed issues directly into Myncel using a phone or tablet on the shop floor.

This works great for legacy equipment that has no PLC or network port, for low-criticality assets where sensors are not cost-justified, or simply for getting started while the IT/OT team scopes a sensor rollout.

Schedules trigger based on calendar days or manually-entered runtime hours, and alerts fire whenever someone reports an anomaly. You still get the full power of work orders, PMs, parts, reports, and AI-assisted root-cause analysis.

• Cost: $0 — included on every plan.
• Setup time: zero. Just add the machine and start using it.
• Data quality: depends entirely on operator discipline.
• Best for: machines that lack network connectivity, low-criticality assets, fleets just starting out.

Option 2 — IoT sensor retrofit (recommended for most customers)

For machines that lack a built-in network connection, Myncel supports a range of low-cost wireless IoT sensors that retrofit onto existing equipment. The sensors stream vibration, temperature, current, and runtime data through a small piece of software called the Myncel Edge Gateway, which forwards everything securely to the cloud.

The Edge Gateway is open-source software you run on hardware you already own — a Raspberry Pi 4, a small industrial PC, an ESP32 microcontroller, or even a Linux container on an existing server. It buffers locally if your internet drops, then catches up when the link comes back. Download it from /docs/edge-gateway or /dashboard/gateway-setup. Builds are available as a Python package, a Raspberry Pi image, an ESP32 Arduino sketch, and a Node-RED flow.

• Vibration sensors — three-axis MEMS or piezo accelerometers. Detect bearing wear, imbalance, misalignment, looseness, gear-mesh issues, and cavitation in pumps. Typical range 0–16 g, frequency response to 5 kHz, ISO 10816 compliant.
• Temperature sensors — surface-mount or PT100 RTD. Detect overheating motors, friction, fluid degradation, and cooling-system failures. ±0.5 °C typical accuracy.
• Current sensors — non-invasive split-core CT clamps (no downtime to install). Detect overload, undercurrent, motor degradation, and unbalanced phases.
• Runtime / cycle counters — magnetic, inductive, or optical. Drive PM schedules from actual usage instead of calendar days using the BY_HOURS schedule frequency.
• Pressure / flow / level — for hydraulic, pneumatic, and process systems. 4–20 mA or 0–10 V analog inputs to the gateway.

1. Choose your gateway hardware. A $40 Raspberry Pi 4 covers most small shops; an industrial Linux PC is recommended for plant-scale deployments. For a single piece of equipment with no network, an ESP32 microcontroller is the cheapest option.
2. Add the machine in Myncel (Equipment → "+ Add Machine"). Then click into the machine to open its detail panel.
3. In the detail panel, find the "Edge Gateway Tokens" area and click "Create Gateway Token". Copy the token immediately — Myncel only shows it once. The notice on screen tells you to paste it into your YAML config under "device_token:".
4. Download the gateway package from /docs/edge-gateway → "Download package" (or pick the matching artifact for your hardware: Raspberry Pi image, ESP32 sketch, Node-RED flow).
5. Open the example YAML config that ships with the package. Set device_token: <paste your token>, then add a connector block for each protocol or sensor — see /docs/edge-gateway/<protocol> for ready-to-paste examples (Modbus TCP, OPC UA, MQTT, MTConnect, BACnet/IP, Siemens S7, Rockwell EtherNet/IP, or Beckhoff ADS).
6. Run the agent (`python3 myncel-edge-gateway.py` for the Python package, flash the sketch for ESP32, or import the Node-RED flow). Within 30–60 seconds, live values appear on the machine's detail panel in Myncel.
7. Mount any physical sensors on the target machine following the install guide that ships with the kit (typical install: 5–15 minutes per machine, no downtime needed in most cases).
8. Create a PM schedule in /admin/schedules (or the Schedules sidebar tab). For predictive maintenance, set Task Type = PREDICTIVE — Myncel will baseline from incoming data automatically over the first 7–14 days and start firing predictive alerts after that.

Option 3 — Direct PLC / SCADA integration

Modern PLCs and SCADA systems already produce a wealth of data. Myncel can read directly from them through standard industrial protocols, removing the need for additional sensors. This is usually the lowest-cost option per data point if the machines already have a controller and a network drop.

Configuration uses the same Edge Gateway from Option 2 — you simply add a connector block to the YAML config for the protocol you need. Each protocol has its own page under /docs/edge-gateway with copy-pasteable examples for the most common controllers.

For Starter and Growth plans you can use the Edge Gateway in MQTT-bridge mode, which lets a third-party SCADA system push data through the gateway. Direct OPC UA and proprietary protocols (Siemens S7, Rockwell EtherNet/IP, Beckhoff ADS) are included on Professional and Enterprise plans.

• OPC UA — secure, modern, the industry standard for new installs. Works with Siemens, Beckhoff, B&R, Kepware, Ignition, and most modern PLCs. See /docs/edge-gateway/opcua.
• Modbus TCP / RTU — universal. If a controller is older than 5 years and on Ethernet, it almost certainly speaks Modbus TCP. Read holding registers, input registers, coils, and discrete inputs. See /docs/edge-gateway/modbus.
• MQTT (incl. Sparkplug B) — lightweight, broker-based. Excellent for high-fanout fleets and IIoT use cases. See /docs/edge-gateway/mqtt.
• Rockwell EtherNet/IP (CIP) — Allen-Bradley / Rockwell PLCs (CompactLogix, ControlLogix, MicroLogix). See /docs/edge-gateway/rockwell-ethernet-ip.
• Siemens S7 — direct read from S7-300, S7-400, S7-1200, S7-1500 over ISO-on-TCP. See /docs/edge-gateway/siemens-s7.
• BACnet/IP — building automation systems, HVAC, lighting, energy meters. See /docs/edge-gateway/bacnet.
• MTConnect — pull CNC machine status, execution state, spindle load, alarms, and production data from MTConnect agents. See /docs/edge-gateway/mtconnect.
• Beckhoff ADS — TwinCAT symbols by AMS Net ID and symbol name. See /docs/edge-gateway/beckhoff-ads.
• REST / Webhook — anything that can POST JSON over HTTPS lands via /api/iot/ingest with your API key.
• SNMP v2c / v3 (IT and network gear — UPS, switches, PDUs) is on the roadmap. See the Roadmap chapter for status.

Worked example A — Haas VF-2 CNC mill (sensor + Modbus TCP)

A small machine shop has a Haas VF-2 vertical machining center (3-axis, 7.5 kW spindle, 8,100 RPM). The shop wants to (a) detect spindle-bearing degradation early and (b) bill customers from real spindle-on hours instead of estimates. The VF-2 has a built-in Ethernet port (the Haas Networking option) and the shop already has Wi-Fi on the floor.

Recommended hybrid setup: one wireless triaxial vibration sensor on the spindle housing for predictive diagnostics, plus a Modbus TCP read from the VF-2's NGC control for spindle-load percentage and runtime.

1. Add the Haas VF-2 in Myncel: Equipment → "+ Add Machine" → Name = "Haas VF-2 — Bay A", Manufacturer = "Haas", Model = "VF-2", Category = "CNC Mill", Criticality = "High". Save.
2. Click the new machine to open the detail panel. Find the "Edge Gateway Tokens" area and click "Create Gateway Token". Copy the token (it is shown once).
3. Wire the VF-2 to the shop network (the Haas comes with an RJ45 port on the back of the cabinet). Note the IP address from Setting #900 on the Haas control.
4. On any Linux machine on the same network — a Raspberry Pi 4 is plenty — download the Edge Gateway package from /docs/edge-gateway. Open the YAML config; paste the token under device_token: and add a Modbus TCP connector block following the example at /docs/edge-gateway/modbus.
5. Configure the Modbus block: host = the VF-2 IP, port = 502, unit_id = 1. Add register definitions: holding register 30001 → spindle_load_pct, 30002 → spindle_rpm, 30010 → cycle_time, coil 00001 → in_cycle (drives runtime accumulation).
6. Mount the vibration sensor on the spindle housing with its magnetic base, X-axis aligned to the machine's X. Wire it to the same gateway over USB or BLE (gateway plug-ins are documented under /docs/edge-gateway).
7. Run the gateway agent: `python3 myncel-edge-gateway.py`. Within 30–60 seconds the live spindle-load %, RPM, and vibration RMS appear on the machine's detail panel in Myncel.
8. Create a runtime-based PM in /admin/schedules: Title = "Spindle grease — 500 hr", Task Type = PREVENTIVE, Frequency = BY_HOURS, interval = 500. Because runtime is now live from Modbus coil 00001, the PM fires when actual spindle-on hours hit 500 — never on a fixed calendar day.
9. Create a predictive PM as well: Title = "Spindle bearing health watch", Task Type = PREDICTIVE, Frequency = WEEKLY. The AI baselines from the incoming vibration data over the first 7–14 days; predictive alerts then fire automatically when the signature drifts past ISO 10816-3 zone B/C (4.5 mm/s RMS) or zone C/D (7.1 mm/s RMS).

Worked example B — Cummins 250 kW standby generator (Modbus TCP)

A hospital has a Cummins QSL9-G5 250 kW standby generator with a PowerCommand 2100 controller. The facilities team needs (a) automatic logging of the weekly self-test run, (b) alerts on low-fuel and low-coolant, and (c) compliance evidence for The Joint Commission inspections.

The PowerCommand 2100 has built-in Modbus TCP. Once the controller is on the building network, Myncel can read every parameter the local screen shows — no extra hardware needed.

• Total wiring needed: zero — the controller already has Ethernet.
• Configuration time: typically 45 minutes including PM checklist authoring.
• Compliance bonus: every weekly run is now permanently logged with timestamps, runtime, peak load, and any fault codes — exactly what NFPA 110 inspectors ask for.

1. Confirm the PowerCommand network module is installed and configured (Settings → Network → Modbus on the controller front panel; default port 502).
2. Add the genset in Myncel: Equipment → "+ Add Machine" → Name = "Genset 250kW — Bldg A", Manufacturer = "Cummins", Model = "QSL9-G5 / PowerCommand 2100", Category = "Generator", Criticality = "Critical".
3. Click into the new machine and create a Gateway Token (copy it once).
4. On the BMS server, a Raspberry Pi in the building, or any always-on Linux box on the same network, install the Edge Gateway package (download from /docs/edge-gateway).
5. Edit the YAML config: paste the token under device_token: and add a Modbus TCP connector following /docs/edge-gateway/modbus. host = the PowerCommand IP, port = 502, unit_id = 1.
6. Map the standard PowerCommand registers: 30001 → engine_rpm, 30015 → coolant_temp_f, 30022 → oil_pressure_psi, 30040 → fuel_level_pct, 30050 → battery_voltage, 30100 → fault_bitmask.
7. Run the gateway agent — values appear in the Myncel machine page within 60 seconds.
8. Create three rule-based alerts in /settings/notifications: (1) fuel_level_pct < 30 → email facility manager; (2) coolant_temp_f > 220 OR oil_pressure_psi < 25 while engine_rpm > 0 → SMS to on-call electrician; (3) fault_bitmask != 0 → SMS + Slack #on-call channel.
9. Create a calendar PM in /admin/schedules: Title = "Weekly self-test verification", Task Type = PREVENTIVE, Frequency = WEEKLY. The auto-generated work order each Tuesday includes a checklist asking the technician to confirm the genset ran ≥ 30 minutes the previous Sunday — Myncel auto-fills runtime from the live data so the technician only has to confirm.

Worked example C — 200 hp Atlas Copco GA-160 air compressor (sensor + protocol)

A plant has a 200 hp Atlas Copco GA-160 oil-injected rotary-screw compressor with an Elektronikon Mk5 controller. Compressed air is plant-critical and a failure costs roughly $3,500/hour in downtime. The plant wants early warning on motor and air-end health, plus automatic energy reporting.

Recommended setup: three split-core CT clamps on the motor leads (no downtime to install), one vibration sensor on the air-end, and Modbus TCP to the Elektronikon for pressure, temperature, and load percentage. This combination catches all three failure paths — electrical, mechanical, and process — with zero false negatives in our customer data.

1. Add the compressor in Myncel: Equipment → "+ Add Machine" → Name = "GA-160 #1", Manufacturer = "Atlas Copco", Model = "GA-160", Category = "Compressor", Criticality = "Critical".
2. Click into it and create a Gateway Token (copy once).
3. Install the CT clamps on the three motor phases inside the motor disconnect (qualified electrician; can be done energized with proper PPE in 20 minutes). Wire them to a Raspberry Pi or industrial PC running the Edge Gateway, using the analog or pulse input pattern documented at /docs/edge-gateway.
4. Bond a vibration sensor to the air-end housing on the discharge side, axis aligned with the rotor. Wire it to the same gateway.
5. In the YAML config: paste the token under device_token: and add a Modbus TCP connector following /docs/edge-gateway/modbus, pointing at the Elektronikon Mk5 (the EKOMI protocol module is included on Mk5 controllers from 2017 onward). Map: register 30030 → discharge_pressure, 30040 → element_outlet_temp, 30100 → motor_running_hours, coil 00010 → loaded (drives loaded-hours accumulation).
6. Run the gateway agent. Live current draw, vibration RMS, pressure, temperature, and loaded/unloaded state appear in Myncel.
7. Create predictive and runtime-based PMs in /admin/schedules: (1) "Air-end oil change" — Task Type = PREVENTIVE, Frequency = BY_HOURS, interval = 4000 loaded hours; (2) "Separator element" — same; (3) "Motor grease" — interval = 8000 hours; (4) "Compressor health watch" — Task Type = PREDICTIVE, Frequency = WEEKLY (the AI baselines from the three sensor streams and surfaces bearing wear, valve leaks, and impending element failure 2–6 weeks early).
8. Create a daily energy report from /admin/reports: kWh per Nm³ of delivered air. The report flags any day that runs >10% above the 30-day rolling baseline — usually that means a leak or a stuck unloader.

Worked example D — Hospital UPS, autoclave, and refrigeration (BACnet + SNMP)

A 120-bed hospital uses Myncel to manage three categories of biomedical-adjacent equipment: APC / Eaton UPS systems in IT and the OR; Tuttnauer and Steris autoclaves in CSSD; and walk-in refrigerators / freezers for the pharmacy and lab. All three connect over the existing hospital BMS network.

This example shows how Myncel handles a heterogeneous facility where you do not have one big PLC but many small controllers, each speaking a different dialect.

• UPS systems — most APC and Eaton network management cards (APC AP9641, Eaton Network-M2) expose values over both SNMP v3 and a small REST API. The Edge Gateway can poll the REST endpoint and post the values to /api/iot/ingest with your API key — the same pattern shown in /docs/edge-gateway. Map runtime-on-battery, output load %, battery age, and self-test result. Alert on any "On Battery" event longer than 30 seconds, on battery age > 4 years, and on any failed self-test. (Native SNMP support is on the roadmap.)
• Autoclaves — most modern Tuttnauer and Steris units expose a serial or Ethernet port that streams cycle data (start time, peak temperature, hold time, cycle pass/fail). Myncel ingests via REST webhook: point the autoclave's printer-replacement module at /api/iot/ingest with your API key. Each completed cycle becomes a permanent record attached to the autoclave's machine page — exactly what JCI surveyors ask for.
• Walk-in refrigeration — usually monitored by a building-management system (Johnson Controls Metasys, Honeywell EBI, Schneider EcoStruxure). Myncel reads via BACnet/IP through the Edge Gateway (see /docs/edge-gateway/bacnet) or directly via the BMS's REST API where supported. Critical-temperature alerts (> -15 °C in a freezer for > 10 minutes) escalate via SMS and to your on-call channel via the Webhooks integration.

Worked example E — Forklift and yard-truck fleet (QR + telematics)

A 1.4 million sq ft distribution center runs a fleet of 38 Toyota and Crown sit-down forklifts plus 6 Ottawa yard trucks. There is no single PLC and no Wi-Fi outdoors. The team wants daily pre-shift inspections, runtime-based PM, and a complete event log for OSHA inspections.

Recommended setup: one Myncel QR sticker per truck. Operators do the pre-shift inspection on their phone in under two minutes via the Myncel mobile app; runtime hours are logged through the same checklist (or pulled from telematics via the public REST API for shops that already run Toyota I_Site, Crown InfoLink, Geotab, or Samsara).

• No PLCs touched, no extra hardware on the trucks, no electrician involved.
• OSHA recordkeeping for daily inspections (29 CFR 1910.178(q)(7)) is satisfied automatically — every checklist is timestamped with operator ID and exportable as PDF or CSV.
• Same pattern works for scissor lifts (Genie, JLG), telehandlers, sweepers, and fleet vehicles.

1. Add each truck in Myncel: Equipment → "+ Add Machine". Use a consistent name pattern such as "FORK-001 Toyota 8FGCU25" so search and reports stay clean. (For 38+ trucks, use the public REST API — POST /api/machines — with a small script to import the list in one go; see "Bulk-importing your existing equipment list" earlier in this chapter.)
2. In /equipment/qr-labels, choose label size Small (50×50 mm), select all forklifts, and print. Apply each sticker next to the OEM data plate or on the dashboard.
3. Author one shared "Pre-shift inspection" PM in /admin/schedules: Title = "Pre-shift inspection", Task Type = INSPECTION, Frequency = DAILY. The auto-generated work order each shift includes a checklist (parking brake, horn, forks, mast, leaks, tires, OSHA 1910.178 items). Operators tap through it on their phone.
4. Set runtime-based PMs per OEM schedule: 250-hour service, 500-hour service, 1,000-hour service. Use Frequency = BY_HOURS with the appropriate interval. Hours are logged either by the operator at shift end (through the inspection checklist) or pushed automatically via the shipped telematics importers — Geotab, Samsara, Verizon Connect, Motive, and Fleetio are now native (see /docs/telematics); for Toyota I_Site / Crown InfoLink, pull data via their public APIs into a small scheduled script that POSTs to /api/telematics/import?provider=generic.
5. For impact monitoring: if your telematics provider already detects impacts, POST those events to /api/telematics/import (or /api/iot/ingest) with type = "impact" and severity = the g-force. Myncel auto-creates a Safety work order on the matching truck with the operator and timestamp. (Native I_Site / InfoLink one-click setup is still on the roadmap; Geotab/Samsara/Verizon/Motive/Fleetio are shipped today.)

Organizing equipment with locations

Myncel ships a four-level structured location hierarchy out of the box: Site → Building → Floor → Room. Every level is optional, so you can use as little or as much depth as your operation needs. A single-building manufacturer might only use Site + Building + Room. A multi-campus hospital network will use all four. Each Machine record can be linked to one Site, one Building, one Floor, and one Room — and as you set a deeper level the parents are inferred and locked so the chain stays consistent.

Alongside the structured hierarchy, every machine still has a free-text Location label that you can use as a quick fallback (handy for one-off zones that don't deserve their own Site, like "Shipping Dock 4" inside a building you haven't mapped). Search matches across the structured names AND the free-text label, so either approach works.

• A Site is one physical address (e.g. "Plant 1", "Houston Yard", "Mercy Hospital — Main Campus"). Optional fields: short code, address, timezone.
• A Building lives inside a Site (e.g. "Building A", "Warehouse 3", "ICU Wing"). Buildings inherit the Site's timezone.
• A Floor lives inside a Building. Use the optional level number for sorting (-1 basement, 0 ground, 1 first floor, …).
• A Room lives on a Floor. Use this for bays, lines, mech rooms, OR suites — anywhere a single piece of equipment lives.
• Equipment list filters by any combination of these levels. Pick a Site to see all machines at that site; pick Site + Building + Floor + Room to drill all the way down.
• When you select Room first, Myncel auto-populates the Floor / Building / Site so you never have a Room pointing to the wrong Floor.

1. Go to Settings → Locations.
2. Click "+ Add Site" and give the first site a name (e.g. "Plant 1"). Optionally add a short code, address, and timezone. Save.
3. Click the site row to expand it, then "+ Building". Repeat per building you maintain.
4. Expand a building, click "+ Floor". Repeat per floor.
5. Expand a floor, click "+ Room". Repeat per bay / line / mech room / OR.
6. Open Equipment → "+ Add Machine" (or "Edit" on an existing machine). Use the Site / Building / Floor / Room dropdowns under "Location (structured)" — selecting a Site narrows the Building dropdown, and so on.
7. Optional: keep using the free-text "Location label" field for quick descriptions on top of (or instead of) the structured picker. Every screen displays the structured breadcrumb when set, falling back to the free-text label.

The equipment record — health, history, and details

Every machine has two ways to inspect it. The quick detail modal opens from any equipment row in the dashboard for a fast read-only glance. The full tabbed equipment page lives at /equipment/[id] and is where you go to diagnose a recurring issue, attach manuals, audit parts spend, or prepare for an inspection. Inside the quick modal you will see an "Open detail page →" link that takes you straight to the full page.

The full equipment page is organized into six tabs along the top. The active tab is reflected in the URL hash (e.g. /equipment/abc123#parts), so you can bookmark or share a deep link to any tab. On mobile the tab strip scrolls horizontally — flick left to reach Telemetry without losing your place.

• Overview — identity (name, serial, manufacturer, model, year installed), status and criticality badges, location breadcrumb, notes, and the live equipment image. The header strip shows five live counts: open work orders, schedules, alerts, documents, and total telemetry readings.
• Documents — manuals, drawings, P&IDs, datasheets, certificates, photos. Upload a file (up to 5 MB, stored as a data URL inside Myncel — no S3 setup required) or paste a hosted URL for files you already keep elsewhere. Click any row to preview: PDFs render inline in the browser, images display directly, and CAD files (DWG, DXF, STEP, IGES) drop you to a download link with a friendly "open in your CAD tool" message.
• Parts — every part ever consumed on this machine, aggregated from completed work orders. You see total quantity used, total cost in your org currency, last unit cost, the number of work orders that consumed it, and the date it was last used. Useful for spotting wear-prone components and forecasting next year's parts budget.
• Schedules — the preventive-maintenance schedules attached to this machine, with frequency, last run, next due, and a link to /admin/schedules to edit them.
• Timeline — a unified vertical feed merging work orders (created and completed), alerts, and document uploads in chronological order. Each event is colour-coded by severity. Capped at the 200 most recent events; older history is available via the Reports chapter.
• Telemetry — for machines with sensors or an Edge Gateway, the latest value for every sensor channel and a table of the most recent readings. Empty for machines without telemetry; no setup needed if you do not use it.

1. From the dashboard equipment list, click a machine row to open the quick detail modal.
2. In the modal header, click "Open detail page →" to jump to the full tabbed page (or visit /equipment/[id] directly).
3. Use the tab strip at the top to switch between Overview, Documents, Parts, Schedules, Timeline, and Telemetry. The URL hash updates as you click so your tab choice is shareable.
4. On the Documents tab, click "+ Upload" to add a manual or drawing. Pick a file from disk (up to 5 MB) or paste an external URL, choose a kind (Manual, Drawing, P&ID, Datasheet, Certificate, Photo, Other), and save.
5. Click any document row to preview it. PDFs and images render inline. CAD files offer a download with guidance on opening them in your CAD viewer of choice.
6. On the Parts tab, sort by total cost to find your most expensive consumables on this asset, or by last-used date to spot parts that may need re-ordering.