ROLO Operations System
Lesson 8: System Rebuild, Validation & Lockdown
This lesson is where everything comes together. After cleanup, ROLO must rebuild the system correctly, test it, and lock it down so it stays clean and scalable.
ROLO Rule
If you don’t lock the system, it will return to chaos. Clean systems only stay clean with rules and enforcement.
Step 1: Rebuild Clean Data into Xcelerator
What to update (in order)
- Addresses (Client Master → Addresses)
- Clients (Client Master)
- Drivers (Operations → Drivers)
- Pricing Schemes (Tariff Builder)
Rules
- Only enter CLEAN, verified data
- Do not re-import duplicates
- Standardize naming formats
- Confirm required fields are complete
Why this matters
This step turns your cleaned spreadsheets into a clean operating system.
Step 2: Validate with Test Orders
What to test
- Create sample orders for:
- Same-day delivery
- White glove
- Medical delivery
- Multi-stop route
- Confirm:
- Correct pricing appears
- Correct service/vehicle defaults
- Addresses load correctly
- Drivers can be assigned properly
Why this matters
Testing ensures the system works BEFORE going live with real orders.
Step 3: Validate Dispatch + Routing
What to check
- Routes build correctly in Route Builder
- Sequencing produces logical stop order
- Drivers receive correct route in MobileTek
- Dispatch board reflects real-time status
Why this matters
This confirms your cleanup improved real-world operations — not just data.
Step 4: Validate Auto-Dispatch (If Enabled)
What to test
- Run Auto-Dispatch in assisted mode
- Compare system suggestions vs dispatcher decisions
- Confirm:
- Correct driver selection
- No bad assignments
- No route disruption
Why this matters
Ensures automation is helping, not hurting operations.
Step 5: Lock Down Data Entry Rules
Where
Delivery Center Options → OE Required Fields / Custom Settings
What to enforce
- Required fields:
- Service type
- Vehicle type
- Pickup address
- Delivery address
- Standard address usage
- Validated service/vehicle combinations
Why this matters
Prevents bad data from entering the system again.
Step 6: Set User Permissions & Roles
Where: Administration → Security
What to control
- Who can:
- Create clients
- Edit pricing
- Add addresses
- Limit high-risk permissions to managers only
Why this matters
Too many users with full access = guaranteed data breakdown.
Step 7: Create Ongoing Maintenance Routine
Weekly Tasks
- Review new addresses
- Check duplicate clients
- Review driver activity
Monthly Tasks
- Audit pricing schemes
- Review performance dashboard
- Clean inactive data
Why this matters
Maintenance prevents another full cleanup project later.
Step 8: Go Live with Clean System
Final checklist
- All test orders successful
- Dispatch workflow confirmed
- Drivers active and visible
- Auto-Dispatch (if used) stable
- Dashboard tracking in place
Why this matters
This marks the transition from cleanup mode → optimized operations.
Lesson 8 Completion Standard
ROLO is fully operational when clean data is live in Xcelerator, dispatch runs efficiently, automation is controlled, and strict data entry rules prevent system degradation.