There is no single universal “app” that creates work instructions across all plants or systems. In most regulated, brownfield environments, work instructions are created and maintained in one or more of the following:
- MES work instruction modules: Many MES platforms include native electronic work instruction (EWI) or operator guidance modules. These are often used when you need tight linkage to routing, data collection, and e-signatures. The constraint is that format, layout, and reuse across sites or other systems can be limited, and changes must go through MES change control and revalidation.
- PLM or engineering authoring tools: Some organizations create manufacturing work instructions inside PLM (or linked CAD/ECAD/MBOM tools) as part of the manufacturing process plan. This is strong for traceability to design and configuration, but can be harder to consume on the shop floor without a separate viewer, MES integration, or a published derivative (PDF, HTML, etc.).
- DMS/QMS (document management / quality systems): In many regulated plants, the formal, controlled version of a work instruction is a document in a DMS or QMS (e.g., as a SOP, WI, or controlled form). Operators may see a PDF or printed copy, sometimes embedded or linked from MES. This supports document control and audit trails, but is weaker for in-process guidance, rich media, and conditional logic.
- Specialized digital work instruction tools: There are point solutions focused solely on interactive digital work instructions (images, 3D, video, step-by-step guidance, error-proofing). These can be powerful but only work well if they are integrated with your MES/ERP/PLM/QMS and validated appropriately. Without that, they become another silo and can create version control and traceability risks.
- Legacy office tools (Word, PowerPoint, Excel, PDF): In many brownfield environments, authoring still happens in office tools. These files are then stored in a shared drive, DMS, or QMS and referenced by MES or printed to paper. This approach is simple to deploy but increases the risk of inconsistent versions, limited structure, and weaker integration with as-built data.
How to identify “the app” in your environment
In a specific plant, the “app that creates work instructions” is usually whichever system is treated as the authoritative source of the content, not necessarily the system that displays it on the line.
To determine this in your environment:
- Check where change-controlled edits happen (where engineering or manufacturing actually edits steps, images, and sequence).
- Check where approvals, versions, and effective dates are managed (often in a DMS/QMS or PLM, even if the operator UI is in MES).
- Ask which system is considered the “system of record” for work instructions in your quality system and procedures.
- Review which system is validated for GxP or regulated use and how changes are documented.
In many cases, there is a split:
- Authoring and approval in PLM or QMS/DMS.
- Execution and display in MES or a digital work instruction viewer.
Key constraints and tradeoffs
When choosing or standardizing on an app for work instruction creation, you need to weigh:
- Traceability: Can you link each step to design data, BOMs, routings, risk analyses, and training records?
- Version control and governance: Does it support formal review/approval, effective dating, and change history aligned with your QMS?
- Integration with existing systems: Can it coexist with current MES/ERP/PLM/QMS, or will it duplicate data? In brownfield sites, full replacement of MES or PLM is rarely feasible due to validation burden, downtime risk, and integration complexity.
- Validation and change control: How expensive is it to validate the app and maintain it under change control across long equipment lifecycles?
- Usability on the shop floor: Can operators actually follow it under real production constraints (small screens, gloves, intermittent connectivity, language variants)?
Replacing an existing MES or QMS just to change how work instructions are authored is usually high risk and high cost in regulated environments. A more common approach is to:
- Keep the current system of record (often PLM or QMS/DMS).
- Improve templates, structure, and media in that system.
- Integrate or layer a digital work instruction viewer or MES module on top, with careful mapping of versions and change control.
How this coexists with legacy systems
In brownfield plants, multiple generations of systems often coexist:
- Legacy lines may still use printed PDF work instructions sourced from QMS.
- Newer cells may use MES-driven electronic work instructions, with core content still authored in PLM or QMS.
- Some high-variance or prototype areas might use a specialized EWI tool integrated loosely (or manually) with existing systems.
This hybrid reality is normal. The critical point is to make clear in your procedures which system is the authoritative app for creation and change control and how other systems consume that content, so you avoid conflicting versions in front of operators.
