What this is
Workflows are the backbone of Next Plus. They define how work is performed, documented, and controlled on the shop floor. As an Editor, your goal isn’t only to digitize instructions—it’s to make them usable, reliable, and auditable.
This guide explains the principles of workflow design, with practical steps and examples you can adapt to your own processes.
How to do it
1. Start with the process, not the tool
Before opening Next Plus:
Write down the phases of your process (Assembly, Testing, Packing, Maintenance).
Identify decision points (e.g., “If temperature > 80°C → stop process”).
Note what needs traceability (signatures, serials, photos).
💡 Tip: A rough sketch on paper saves hours later in the editor.
2. Create the workflow skeleton
Go to Workflow Modeling → All Workflows → ➕ New Workflow.
Give it a clear, process-based name (e.g., Pump Assembly v2).
Add chapters to reflect the phases you mapped.
📌 Value for you: Chapters aren’t only visual—they let operators see progress and give managers clear checkpoints in reporting.
3. Add steps with clarity and context
Each step should include:
Title (what to do: “Install gasket”).
Instruction (how to do it: “Tighten 4 bolts to 5 Nm”).
Media (photo, diagram, video for critical actions).
⚠️ Pitfall to avoid: Don’t overload one step with too many tasks. Keep it one action = one step.
4. Capture the right data
Think about what data you must keep for compliance or quality:
Numeric fields (measurements, torque, weight).
Yes/No checks (inspection points).
Image uploads (before/after photos).
Serial numbers (for traceability).
📌 Value for you: Structured fields let you build reports and dashboards later. Free text notes are harder to use for analytics.
5. Control the flow with conditions
Not every process is linear. Use conditions and show/hide logic to:
Branch based on results (If defect = yes → open deviation form).
Skip steps when not relevant (If product type = B → hide calibration step).
Prevent errors (If weight not between limits → stop workflow).
💡 Pro tip: Always define both sides of a condition (e.g., what happens if it’s OK, and what happens if it’s not).
6. Add accountability with signatures & certifications
Assign signatures to critical steps.
Require certifications for roles (e.g., only trained inspectors can approve a test).
📌 Value for you: This builds digital audit trails that satisfy ISO, FDA, or customer audits without extra paperwork.
7. Link to parts and BOM (when relevant)
Attach a Bill of Materials (BOM) so operators confirm they used the right parts.
Define whether consumption updates inventory.
⚠️ Pitfall to avoid: Don’t attach phantom or placeholder parts unless you’re sure how they behave in ERP.
8. Test before release
Use Preview to check flow and layout.
Then run a Work Order session to test with real data.
💡 Tip: Always test with another user. Something obvious to you as the Editor might confuse an Operator.
Common Issues / FAQs
“Operators skip instructions.” → Split big steps into smaller ones. Add required fields.
“Workflow looks messy.” → Use chapters and align steps logically.
“Work Order won’t close.” → Check for unresolved status-managed forms.
“Too many deviations.” → Review thresholds; maybe the spec is too strict.