The Problem: Teams Had Outgrown Their Action Plan App
Every shift finds things that need doing: a guard to fix, a check to repeat, a defect to follow up. The plant used a ThingWorx app to plan these actions, but the teams had outgrown the first version.
Everyone saw the same cluttered view
Users had to set their filters again every time they opened the plan.
Triggers set line by line
Quality and safety questions had to be configured for each line separately, even when a whole department worked the same way.
Defects typed in twice
Problems raised in team meetings had to be re-entered as actions by hand.
Upgrades risked the data
Each site held months of actions, so a new version could not simply replace the old database.
Newer ThingWorx broke screens
On ThingWorx 9.3 and later, some screens stopped working and the scheduler could appear empty.
The Solution: Version 2.0 and a Safe Way to Roll It Out
PSPTechHub delivered Ap24 version 2.0 and a safe way to roll it out. The day-to-day flow stayed the same, so teams didn't need retraining; the changes remove clicks and repeat work.
One plan for the next 24 hours
Actions appear on a scheduler by line; unscheduled items sit in a notification bar until someone plans them.
Drag to schedule
Drag a notification onto the scheduler and it becomes a planned action for that time slot.
Share with other departments
Copy, share or unschedule an action in one click when another team needs to act on it.
Save your own view
Filters are saved per user and reload next time, with one button to return to the default.
Readable on any screen
Text size for the notification bar and activities can be changed to suit the screen and the user.
Triggers per department
Quality and safety questions are set once for a department instead of line by line; a live screen shows answers and countermeasures.
Defects straight from team meetings
A defect raised in the team meeting screens can be sent to the action plan in one step.
Upgrade without losing data
A migration tool compares each site's database with the new version and adds only what's missing, after a full backup.
Works on newer ThingWorx
Screens were updated so the scheduler and activity colours work correctly on ThingWorx 9.3 and later.
How It Works: From Problem Found to Action Done
1
Open on desktop or tablet
Users log in from any modern browser; tablets can save the app to the home screen.
2
Capture an action
Add an activity with an owner and status, or send a defect from the team meeting.
3
Plan it
Give it a time, or drag it from the notification bar onto the scheduler.
4
Answer the triggers
Quality and safety questions for the department are answered with a single click; YES answers show the countermeasure.
5
Share and follow up
Share the action with another department or copy it for a repeat job.
6
Upgrade each site safely
Back up, run the migration tool to compare and update the database, then import the new version.
ThingWorx runs the screens and logic; a SQL Server database at each site keeps every action, trigger and setting.
1. Ap24 screens
Scheduler, notification bar, filters, activity and trigger screens
2. Helper and schedule services
Business logic, user views, scheduled refresh of plant orders
3. Database connector
Calls stored procedures to save, share, copy and read actions
4. SQL Server database
Holds actions, notifications, triggers and configuration per site
5. Migration tool
Compares a site's database with the new version and generates the update
Technology responsibilities
Service
Purpose
Activity services
Save, delete, copy, share and unschedule actions
Activity and notification search
Feeds the scheduler and notification bar from the user's filters
Plant order sync
Stores process orders locally so the app opens quickly
Trigger configuration
Sets quality and safety questions per department
Schema validator
Compares tables and procedures before an upgrade, without changing anything
Design decisions
The everyday flow was kept the same so teams didn't need retraining
The migration tool reads and compares first, and only then applies updates, after a backup of data and app
Settings like text sizes and dropdown values are stored as properties, so each site can adjust them without code
Labels use ThingWorx localization, so each site can show its own language and terms
Common site issues, such as an empty scheduler or wrong status colours, are documented with fixes
Less repeat work
Faster setup for new areas
Upgrades without data loss
Ready for newer ThingWorx
Cleaner screens
Shared ownership
This solution fits if you need to…
Run a 24-hour action plan for production lines in ThingWorx
Track quality and safety triggers and countermeasures per department
Upgrade a ThingWorx app database without losing user data
Fix ThingWorx 9.3 compatibility issues in a custom app
Send team meeting defects into a daily action plan



