How to publish paper SOP to Android and Web workstations
First, scan the existing paper SOP into a clear document, organize it by product and process, then review it as a valid version in ESOPS, and release it to the workstation along with the production order and production schedule. On-site employees use Android or Web terminals to view the guidance content and report production according to the process.
Which scenarios are suitable and not suitable?
It is suitable for factories that want to unify product, process, and work file versions, and allow on-site execution and feedback based on workstations. You can first select a production line and a product pilot. The need for alternative safety training, equipment safety interlocking, a complete ERP or ensuring real-time synchronization of any network environment needs to be evaluated separately and cannot be accomplished by installing terminals alone.
What do I need to prepare before starting?
| Preparatory items | requirements and boundaries |
|---|---|
| information | Products, processes, existing SOP documents, workshops/production lines/stations, participating employees and role permissions. |
| Android | Choose ARM32 or ARM64 APK based on device CPU. A133 uses ARM32; specific equipment, system versions and peripherals still require trial installation and acceptance. |
| Ubuntu | Currently available for Ubuntu ARM64 DEB; not available for x86_64 Ubuntu. Check the system and display environment before using it on site. |
| Web | Use a browser that supports modern web capabilities and access it from the entrance of the designated terminal in the backend. |
| Network and Capacity | Prepare a network that can access the service. First-time activation, task synchronization and production reporting require an Internet connection; offline capabilities are subject to the actual cache and test results of the terminal. New users get 100 MB of free storage, and attachment formats and single file sizes are subject to upload configuration limits. |
1. Establish products and processes
Establish products and corresponding processes in basic data, and confirm product names, models and operation sequences. Organize a verifiable product first, and do not import unverified historical files in batches at the beginning.
2. Upload and review SOPs
Upload clear scans or existing electronic files as SOPs, associate corresponding products and processes, and check text, pictures, page order, and versions. Use the valid version after review is complete; do not consider unreviewed drafts as released to the site.
3. Set up production lines, workstations and bind terminals
Establish actual workshops, production lines and workstations. Download the installation package that matches the device architecture, and access the workstation according to the key and binding process provided by the admin console. The activation key is not a universal employee password and cannot be used with unmatched hardware models.
4. Create production orders and schedule production
Establish production orders for products, and then arrange production according to process, quantity and workstation. Before publishing, confirm that the workstation has an available binding terminal; check whether the SOP to be distributed is the current valid version.
5. Check tasks at Android or Web workstation
Have authorized employees sign in to the workstation app and verify the company account, production line, workstation, product and task. Check each SOP page and attachment. After changing a task in the admin console, wait for synchronization before checking again; do not assume an offline device has received the latest changes.
6. Submit production reports and review them in the admin console
Submit good products, defective quantities and feedback according to the process, and then check the task progress and production report records in the admin console. Check whether there are duplicate submissions, wrong workstations or inconsistent quantities of processes, and process modifications according to the system authorization and review process.
Pilot acceptance checklist
- Only confirmed valid SOPs are displayed for corresponding products and processes.
- Workstations, terminals, and employees have the same permissions, and unauthorized accounts cannot access corporate information.
- Confirm behavior on actual devices after going offline, reconnecting, restarting and changing task versions.
- After the production report is submitted, it can be reviewed in the admin console, and the quantity is consistent with the process.
- Free quota, additional keys, storage packages and subsequent services have been clarified.
About cases and effects
This site currently displays the actual interface and operation process of the product. No project names, man-hour savings, error rate reductions, or return on investment figures without client authorization are published here.
Free resources and storage upgrades · Download original APK / DEB installation package · Return to product homepage