How to add a mobile app to ECI JobBOSS2
Short answer
A mobile app for JobBOSS2 sits between handhelds or tablets and the database or API. It handles barcode scans for job clock-in, quantity complete and inventory moves, queues entries when Wi-Fi drops, and syncs through a supported route. Check ECI's own shop floor and mobile options before building.
JobBOSS2 is built around a desktop client and shop floor data collection on terminals. Many shops still want something lighter in a machinist's pocket or on a rolling cart: scan the traveler, clock in, report pieces, move material to a rack, or approve a purchase from the floor.
ECI has offered shop floor and mobile-oriented capabilities, and third-party vendors sell data collection and scanning products that integrate with JobBOSS2. The first question is whether one of those already covers your need. A custom app makes sense when your workflow is unusual, like particular inspection steps or approval rules.
The notes below cover what a mobile layer must do well, particularly around connectivity and data integrity, so you can evaluate a product or scope a build.
What teams use it for
Scan to start and stop operations
Scan the job traveler barcode and an operation, record start and stop times, and reflect the activity against the job.
Report quantity complete and scrap
Enter good and scrapped pieces with a reason code at the machine, instead of on paper at shift end.
Inventory moves and cycle counts
Scan a location and an item to move stock or count it, with variances sent for review.
Receiving at the dock
Scan the PO and confirm received quantity on a handheld, and capture a photo of the packing slip.
Supervisor approvals
Approve time exceptions, overtime or purchase requests from a phone with the context displayed.
Inspection checklists
Present a part-specific checklist, collect measurements and photos, and attach results to the job.
ECI JobBOSS2 integration surface
- ECI shop floor and data collection options: confirm which modules your JobBOSS2 license includes and what ECI supports for handhelds or tablets.
- ECI JobBOSS2 API: the supported route for transactions like labor and quantity reporting, where available. Ask what is covered and any rate or licensing limits.
- SQL Server database: good for read lookups such as job details and bin contents. Writing here directly bypasses business rules and is unsafe.
- Barcode and traveler data: job and operation identifiers printed on travelers define what scans can resolve.
- Wi-Fi and network layout: the shop floor often has dead spots, which decides how much the app must work offline.
How it works
- 1
Inventory what exists
List which shop floor modules and APIs your version includes, and which third-party data collection products already integrate with it.
- 2
Pick three transactions
Start with the highest volume actions, such as clock in and out, quantity reporting and receiving. Avoid replicating the whole client.
- 3
Choose the device approach
Decide between a browser-based app on rugged tablets, a progressive web app, or a native app for handheld scanners that have hardware triggers.
- 4
Design the sync layer
Put a small server between devices and JobBOSS2 that validates entries, applies them in order and returns clear errors.
- 5
Handle offline
Queue transactions locally with timestamps and idempotency keys, then replay them when connectivity returns, flagging conflicts.
- 6
Authenticate by employee
Use a badge scan or PIN tied to employee records, and role limits for who can approve or adjust.
- 7
Pilot on one cell
Run one work center for a few weeks, compare against the existing process, and fix scan failures before widening.
Example flows
Machinist reports a finished lot
Trigger: An operator finishes an operation on a job.
- The operator scans the traveler and the operation barcode.
- The app shows job, part, revision and expected quantity.
- The operator enters good and scrap counts and picks a scrap reason.
- The entry syncs; if offline it queues and posts later, preserving the original time.
Result: The planner sees progress as it happens and scrap is captured with a reason.
Cycle count by bin
Trigger: Stores runs a weekly count of a rack.
- The counter scans the bin label and each item.
- The app compares counts to book quantity.
- Differences beyond a threshold go to a supervisor for approval.
- Approved adjustments are posted by a user with the right authority.
Result: Inventory accuracy improves without letting counters alter stock unreviewed.
Keeping data on-prem
A shop floor app fits on-prem naturally. Host the sync server on your network next to SQL Server, serve the app over local Wi-Fi, and keep traffic off the internet. Remote access for managers can go through a VPN. Because the app runs in your facility, data stays local, and there is no dependence on a cloud service for core scanning. If you add AI features, such as reading a photographed packing slip, run the model on a local server so images of documents stay inside the plant.
Security checklist
- Authenticate each user by badge or PIN, and never share a device login across operators.
- Segment shop floor Wi-Fi from the office network and limit what the sync server can reach.
- Validate every transaction server side; the device is not trusted.
- Use device management so lost tablets can be locked and wiped.
- Keep an audit log of every transaction with employee, device and timestamp.
Ways to get it done
ECI shop floor product or a certified data collection partner
Effort: Weeks including hardware, with license cost to verify
Shops that want a supported route with scanning and labor tracking
Build a custom app in-house
Effort: Two to four months for a reliable offline-capable app
Unusual workflows and a developer who can maintain it
Partner build with Netray
Effort: Scoped after confirming your API access and device plan
Custom flows with approvals and local AI features such as document reading
Pitfalls
- !Building a full copy of the desktop client instead of a few high-volume transactions.
- !Writing straight to SQL tables and bypassing JobBOSS2 business logic.
- !No offline plan, so work stops at Wi-Fi dead spots.
- !Duplicate postings after a retry because transactions lacked idempotency keys.
- !Printing travelers with barcodes that cannot be scanned reliably under shop lighting.
Frequently asked questions
Does JobBOSS2 have an official mobile app?
ECI has offered shop floor and mobile-related options in the past, but availability depends on version and license. Ask ECI or your reseller what is current before you commit to a custom build.
Can a mobile app work without the API?
Reading is possible through SQL views, but posting labor or inventory should use a supported route. If none exists, stage entries for a clerk to post rather than writing to tables directly.
What devices work best?
Rugged Android handhelds with hardware scan triggers suit receiving and counts. Tablets mounted at work centers suit labor reporting. Test scanning on your actual travelers and labels.
How do we handle offline use?
Queue entries on the device with timestamps and unique IDs, replay in order when connected, and show conflicts for review. Decide up front which actions are allowed offline.
Can AI help on the shop floor?
Yes in limited ways, like reading a photographed slip or answering where a job is. Keep AI suggestions separate from posted transactions and run any model locally if the content is sensitive.
Want Mobile app working on your ECI JobBOSS2?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment