1. Accessing "Edit Solvers"
You don’t have to start from scratch. The best way to learn is to see how the pros do it.
The Steps: Navigate to a report (like the Dispatch History or Spares History Report), click the Execution AI button, and instead of clicking a solver name, click Edit Solvers.
Why it works: This reveals the "under the hood" prompt. You can now edit this existing logic to fit your specific needs.
2. The Golden Rule: Context is King
The AI is only as smart as the data you give it. Before you run a custom prompt, use the L2L Filters on your page to narrow down the data (e.g., specific dates, assets, or priority levels).
Note: The AI scans up to 100 records in your current view. If you filter for "Forklifts" first, your custom solver will be much more accurate.
3. Writing Effective Prompts (The "Better" Way)
When writing a custom solver, specificity is your best friend. Use this table as a guide:
| Goal | Avoid This (Too Vague) | Use This (Specific) |
|---|---|---|
| Root Cause | "Why is this machine breaking?" | "Review the 'Action Taken' notes for the last 10 breakdowns and identify the most frequent mechanical failure." |
| Team Performance | "How is my team doing?" | "Analyze the dispatches from last week. Identify which technicians have the fastest repair times for electrical issues." |
| Inventory | "Do we need more parts?" | "Based on the Spares History, flag any parts that have been used more than 3 times in the last 30 days on Asset [X]." |
4. Pro-Tips for Power Users
Talk, Don't Type: If you're on the shop floor, use the Microphone icon in the chat input. You can dictate a custom solver while standing right at the machine.
The Feedback Loop: If the result isn't quite right, don't give up! Use a follow-up question like, "That's good, but now present that data in a table format with a column for 'Recommended Action'."
Save & Share: If you're a System Manager and you've written a "perfect" custom solver, you can save and share it with your entire team via the Setup menu. This ensures everyone is looking at the data through the same lens.
💡 Quick Challenge
Try this right now: Go to your Machine History page, click Execution AI > Edit Solvers, and add this line to the end of the prompt: "List the top 3 tools a technician should bring to this machine based on previous repairs." Happy Troubleshooting!