Mobile work order dispatch vs web console scheduling: which approach for real-time shop floor?

MES Siemens Opcenter Execution
, , , , , , , ,
1

We’re evaluating two different approaches for work order management in our Opcenter Execution 4.1 deployment and would love to hear from others who’ve made this decision.

Option 1: Mobile-First Dispatch Supervisors use tablets to dispatch work orders directly to operators on the shop floor. Works great offline, but we’re concerned about schedule adherence when mobile decisions don’t align with the APS schedule.

Option 2: Web Console Scheduling Planners schedule everything in the web console, and mobile apps are read-only for operators to view and execute assigned work. Better schedule control, but less flexibility for supervisors to react to floor conditions.

Our main concerns are role-based access control (who can change schedules?), mobile-web data synchronization delays, and how real-time status propagation to APS works in each scenario. We have about 50 shop floor users and need offline work order caching for network dead zones.

What’s worked best for others in high-mix manufacturing environments?

2

The offline point is huge for us - we definitely have WiFi dead zones near some equipment. But I’m still worried about schedule chaos if supervisors are making dispatch decisions offline that conflict with the APS plan. How do you handle reconciliation when the mobile app syncs back? Does Opcenter have built-in conflict resolution?

3

After seeing multiple implementations, here’s my expert perspective on this architectural decision:

Hybrid Approach is Optimal for Most Scenarios

Neither pure mobile-first nor pure web console is ideal for real-time shop floor operations. The winning pattern combines both:

Scheduling Layer (Web Console):

  • Production planners create and optimize schedules in web console
  • APS integration drives the master schedule
  • Long-term capacity planning and constraint management
  • Batch rescheduling and what-if analysis

Execution Layer (Mobile):

  • Supervisors dispatch from schedule within defined rules
  • Operators execute and report status
  • Real-time exception handling and priority adjustments
  • Offline capability for execution continuity

Role-Based Access Control Design: Implement three-tier permission model:

  1. Planners (web only): Full scheduling rights, APS integration, capacity analysis
  2. Supervisors (mobile + web): Dispatch within time window (4-8 hours), priority adjustment (±2 levels), work center scope only
  3. Operators (mobile only): Execute assigned work, report status, request supervisor intervention

Critical configuration: Set allowMobileScheduleOverride=false and supervisorDispatchWindow=4h in work order management module.

Mobile-Web Data Synchronization Architecture:

  • Web console pushes schedule changes to mobile every 90 seconds
  • Mobile pushes status updates to web in real-time (when online)
  • Offline work order caching: Download next 8 hours of scheduled work per user
  • Sync conflict resolution: Web schedule takes precedence, mobile dispatch timestamps preserved for traceability
  • Use Opcenter’s WorkOrderSyncService with delta sync enabled

Offline Work Order Caching Strategy: Mobile app should cache:

  • Assigned and available work orders (next 8 hours)
  • Required materials and tooling data
  • Quality inspection plans
  • Previous operation completion status

Cache refresh triggers: User login, schedule change notification, 4-hour interval, manual refresh

Real-Time Status Propagation to APS: Both dispatch methods support APS integration:

  • Work order status changes trigger ProductionEvent publication
  • APS subscribes to events: Started, Completed, Quantity Reported, Exception
  • Propagation latency: <30 seconds for online operations, batched sync for offline
  • Configure APS connector with realTimeSync=true for critical status updates

Implementation Recommendations for High-Mix Manufacturing:

  1. Start with Web Console Scheduling - Establish schedule discipline first
  2. Add Mobile Dispatch Gradually - Enable supervisor dispatch for one work center, measure schedule adherence impact
  3. Monitor Schedule Adherence - Target >85% adherence before expanding mobile dispatch authority
  4. Design for Offline - Assume 20-30% of mobile operations occur offline in dead zones
  5. Audit Trail Critical - Every dispatch decision needs user, timestamp, reason code for analysis

Network Dead Zone Mitigation:

  • Deploy WiFi repeaters near equipment (obviously)
  • Configure mobile app offline timeout: 15 minutes before enabling full offline mode
  • Implement optimistic locking for offline dispatch decisions
  • Queue status updates with automatic retry on reconnection

Schedule Adherence Metrics: Track these KPIs regardless of approach:

  • On-time start rate (target: >90%)
  • Sequence adherence (actual vs. planned order)
  • Supervisor override frequency (should be <15% of dispatches)
  • Mobile-web sync lag time (target: <2 minutes)
  • APS schedule deviation (actual vs. optimized plan)

Common Pitfall to Avoid: Don’t give supervisors unlimited dispatch authority just because mobile enables it. We’ve seen schedule adherence drop from 92% to 67% when supervisors had too much freedom. The mobile tool should enforce the schedule, not replace it.

For your 50-user environment with WiFi dead zones, I recommend the hybrid approach with conservative supervisor dispatch windows (4 hours max). This balances real-time flexibility with schedule integrity while handling offline scenarios gracefully.

4

Don’t forget about the data volume implications. Mobile-first dispatch generates more frequent status updates and synchronization traffic. With 50 users, that’s manageable, but it impacts your server sizing. Also consider reporting - if dispatch decisions are made on mobile, you need good analytics to track schedule adherence and understand why deviations happened. Make sure your reporting-analytics setup can capture mobile dispatch events with proper timestamps and user attribution.

5

We went with Option 1 (mobile-first) and it’s been successful, but you absolutely need tight role-based access control. Not every supervisor should be able to override the schedule. We configured three roles: Planners (full scheduling), Supervisors (dispatch within constraints), Operators (execute only). The key is defining what “constraints” means for your supervisors.

6

The offline work order caching requirement is critical for your decision. Option 1 handles offline scenarios better because the mobile app has full work order data and dispatch logic. Option 2 struggles when network connectivity is lost - operators can execute but supervisors can’t reassign work. We learned this the hard way during a network outage. If you have reliable WiFi coverage, Option 2 is cleaner. If not, you need Option 1’s offline capabilities.

7

I’d argue for Option 2 with some mobile flexibility. Here’s why: schedule adherence drops dramatically when too many people can change the plan. We use web console for primary scheduling, but supervisors can adjust work order priorities within their work center through mobile. This gives real-time flexibility without breaking the overall production plan. Mobile-web data synchronization happens every 2 minutes for status updates.